Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!ogicse!plains!overby From: overby@plains.NoDak.edu (Glen Overby) Newsgroups: comp.os.minix Subject: Re: comp.os.minix split up Summary: I don't buy it! Keywords: wheat vs chaff, corn vs husks, code vs flamage Message-ID: <9449@plains.NoDak.edu> Date: 6 Apr 91 01:46:56 GMT Article-I.D.: plains.9449 References: <1991Apr02.040413PM.8984@demon.co.uk> <1991Apr5.142156.9792@cs.utk.edu> <32506@mimsy.umd.edu> Organization: SDInet Lines: 29 In article <32506@mimsy.umd.edu> jds@cs.umd.edu (James da Silva) writes: ^^ See this article again for a Few Good Reasons against a .code group >nall@cs.utk.edu (John Nall) writes: >>snowboots@cix.compulink.co.uk (Andrew Bray) writes: [1 good argument for a sources group] >>>Assistance for archive sites. As (Yet Another) archive site maintainer (plains.nodak.edu), the ONLY way I can see a sources group helping the archive maintainers is if it is moderated, in which case the moderator essentially runs the archive (about the only thing I'd do is uudecode postings so they'd suck up less disk space). That's the reason I volunteered as moderator: I do most of the moderation already (just on a somewhat less timely basis). Oh, yeah, there is one other possibility: everything could be encapulated in a nice suit of uuencode armor before it's shiped thru the IBM world. I don't expect that to happen, though (you loose again, Bitnet; you get to hear Bitnet people whine, Internet). I won't put out a campaign add telling everyone which way to go, because I haven't quite decided myself yet :-) As for archiving an unmoderated sources group, I've already got that one figured out: I start the filenames with 1 and go until I catch hell for sucking up all our disk space :-) (at which point I delete old stuff and keep on going). -- Glen Overby uunet!plains!overby (UUCP) overby@plains (Bitnet)