Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Idea for comp.binaries.ibm.pc
Message-ID: <3666@sixhub.UUCP>
Date: 11 Apr 91 00:42:19 GMT
References: <1991Apr10.024155.11745@sactoh0.sac.ca.us>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 28

In article <1991Apr10.024155.11745@sactoh0.sac.ca.us> mholtz@sactoh0.sac.ca.us (Mark A. Holtz) writes:

|                       However, I have an idea. Instead of all the
| information on the file (including brik codes) as the first portion
| of part one, make all that information part of an informational
| post, seperate from the uuencoded post.

  The brik codes must be in the file for it to work. See the brik man
page for details, but trust me on that one.

  It's interesting that a few months ago we had a suggestion that the
info be on the front of every part so people would be able to tell if
they wanted to look for the other parts, and another suggestion that we
put the info in a seperate part.

  There are some perfectly valid benefits and drawbacks to both these
ideas, although I don't find either of them compelling. The obvious
drawback is that another part is one more to lose and one more set of
headers taking bandwidth.

  I'm willing to listen to discussion, but I suspect a lot of people
will yell, because either change would increase disk space and break
tons of autounpacking scripts on machines everywhere.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me