Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!mstar!mstar.morningstar.com!bob From: bob@MorningStar.Com (Bob Sutterfield) Newsgroups: news.admin Subject: Re: alt.sys.sun???? Message-ID: Date: 6 Oct 89 14:04:46 GMT References: <12@dynasys.UUCP> Sender: @MorningStar.COM Reply-To: bob@MorningStar.com (Bob Sutterfield) Followup-To: news.admin Organization: Morning Star Technologies Lines: 31 In-reply-to: tadguy@cs.odu.edu's message of 5 Oct 89 23:27:40 GMT In article tadguy@cs.odu.edu (Tad Guy) writes: In article bob@MorningStar.Com (Bob Sutterfield) writes: In article <12@dynasys.UUCP> jessea@dynasys.UUCP ( Sysadmin.) writes: ...I will not permit alt.sys.sun on my system or any systems that get a feed from me. You have no power to do that unless you buy those systems and pay their administrators' salaries. Wrong. He is welcome to not feed a newsgroup to any of his downstream neighbors just as he is welcome to not carry a newsgroup himself. It's his system (to manage), and he can choose what it carries/feeds, regardless of what his downstream neighbors want. Right - that's what I said. But he has no control over whether those neighbors decide to remain strictly "downstream", or prefer to establish other feeds so that they can receive a group. Sites that care should establish sufficient redundant connectivity that no single point of failure can cause them grief or make decisions for them. You do it with your power supplies, LAN configurations, ECC memory, and other engineering concerns, right? Why not with news? No one system can control any other, unless perhaps the "upstream" administrator is able to persuade every other administrator in the world to blacklist the "downstream" site in question, and deny them feeds. This approach isn't even working in Europe, but that's a whole nother kettle of fish. Alas, this doesn't have anything to do with Suns... ...which is why the discussion has migrated to news.admin now.