Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!malgudi.oar.net!hyperion.wright.edu!echoes.wittenberg.edu!bob.wittenberg.edu!mandrews From: mandrews@bob.Wittenberg.EDU (Mike Andrews) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Why was 2.1.5R pulled back and re-released? Date: 20 Jul 96 21:16:27 GMT Organization: Wittenberg University, Springfield OH Lines: 41 Message-ID: <mandrews.837897387@bob.wittenberg.edu> References: <4sle07$8iq@infoborg.dmacc.cc.ia.us> <31EE8546.167EB0E7@troutmask.apl.washington.edu> NNTP-Posting-Host: bob.wittenberg.edu X-Newsreader: NN version 6.5.0 #8 (NOV) "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> writes: >Charles F. Randall wrote: >> >> A few days ago, there was a file named README.2.1.5 in /pub/FreeBSD on >> ftp.freebsd.org that stated something like (from memory), "The >> permissions on the 2.1.5 directory have been changed to 700 on >> purpose. A few bugs were found just after the release and we've >> decided to fix them quickly and re-release." >> >> It would appear that it has now been re-released. What were the >> reasons for doing this? >> >A few bugs were found that effected the ability to install on >certain popular hardware. Like the 3C509? :-) I caught the KNOWNBUG.TXT file before I upgraded, and was able to work around the problem by just copying it all onto the second hard disk and installing locally, then applied the 509 patch and rebuilt the kernel. Mindly annoying, but not a horrible crisis fortunately... My question: Is this the only difference in the "updated" 2.1.5, or were there any other bugs fixed? I ask because have 5 machines to upgrade total, and I've already done two of them and don't want to have to do them again. One of those two is the ONLY one with a 3C509 in it -- the other four have either 3C503's or NE2000 clones... and if all that's fixed in the re-released 2.1.5 is the 509 driver, it'll save me re-upgrading hassles. If more was fixed than that, what was it, and are there patches? Thanks! -- -- Mike Andrews - mandrews@wittenberg.edu, mandrews@termfrost.org (NeXT) -- Programmer/Analyst, systems/mail/web/netnews guy, Wittenberg University -- http://www.termfrost.org/~mandrews/ "why..."