Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:14974 comp.os.386bsd.bugs:2715 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!news.sprintlink.net!EU.net!ieunet!news.ieunet.ie!jkh From: jkh@whisker.hubbard.ie (Jordan K. Hubbard) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs Subject: December 4th FreeBSD 2.0R installation floppies now available. Followup-To: comp.os.386bsd.questions Date: 05 Dec 1994 02:13:53 GMT Organization: Jordan Hubbard Lines: 37 Message-ID: <JKH.94Dec5021353@whisker.hubbard.ie> NNTP-Posting-Host: whisker.hubbard.ie Well, it looks like we're finally zeroing in on a reasonable state of affairs here! :-) The changes required have been shrinking steadily since I first started rolling these little delta corrections, and this final(?) set should very hopefully fix the last of the problems reported thus far with the 2.0R installation. In actuality, it's probably going to have to be the last set for awhile anyway since I'll be on the road again come Tuesday morning and out of contact with the net for a week or so. If you want to send me feedback on these floppies, PLEASE do so before midnight GMT Monday (the 5th)! Otherwise, I'll get to whatever it was around the 11th or 12th.. This set should fix the last of the tape install problems, removes ppp from the options list since it couldn't work anyway (generic kernel already too big) and corrects the names of a couple of the ftp sites. I didn't add any extra ftp sites since I just didn't have time, sorry.. The TROUBLESHOOTING doc documents how to re-enable the floppy-tape driver, so folks should take care to read it if they're interested in installing this way! I've also renamed the original 2.0R install floppies into the floppies/older directory, since it's pretty much a given at this point that they had a lot of things wrong with them! The "official" 2.0R floppy images now point to the December 4th ones. Please let me know how these go! My biggest remaining fear is that someone broke the GENERIC kernel in -current completely outside my control and that now *that* is going to be what falls over, but all I can say is that I sure hope not! :-) Thanks! Jordan -- Jordan K. Hubbard FreeBSD core team Clams are your friends