Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucsd!ogccse!blake!ndsuvax!ncoverby From: ncoverby@ndsuvax.UUCP (Glen Overby) Newsgroups: comp.os.minix Subject: Re: makepost Summary: too much work, too little gain. Message-ID: <2998@ndsuvax.UUCP> Date: 12 Oct 89 05:05:53 GMT References: <3493@ast.cs.vu.nl> <15538@bcsaic.UUCP> Reply-To: ncoverby@ndsuvax.UUCP (Glen Overby) Organization: North Dakota State University, Fargo Lines: 28 In article <15538@bcsaic.UUCP> paula@bcsaic.UUCP (Paul Allen) writes: >[...] Is there any way that the 1.4b stuff can go out to the >mainstream Usenet in clear-text and get uuencoded by the bitnet >gateway? Well, yes, but another list should really be set up for that and *everything* posted would have to go thru it (a blind encoder). Right now, I dont think we're set up to do the gatewaying here. I have tried to maintain an archive containing files which should be usable with no problems to anybody on Bitnet (the are not expanded). A few people have had problems, but in the end I think most of them worked out OK. I don't know of anybody who had to give up because of transport problems. So Bitnet *is* usable, just not easily. By the way, I do intend to place copies of the 1.4b postings on vm1.nodak.edu (aka ndsuvm1 on bitnet) as soon as I get them via News, so anybody who misses a piece can get it from there rather than asking the entire net to mail them a copy. Other caveats about Bitnet postings: uuencode will use (0x20) as a clear character. This is not so at the end of a line since RSCS (the bitnet transport protocol, etc. machine) will remove them. There was a fix posted to the net soon after 1.3d came out. All the Bitneters will need to have that. -- Glen Overby uunet!ndsuvax!ncoverby (UUCP) ncoverby@ndsuvax (Bitnet)