Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!grumpy.fl.net.au!news.webspan.net!ix.netcom.com!howland.erols.net!vixen.cso.uiuc.edu!news.sprintlink.net!news-peer.sprintlink.net!news-pull.sprintlink.net!news.sprintlink.net!news-ana-24.sprintlink.net!newsie.dmc.com!news.ziplink.net!rtfm.ziplink.net!mi
From: mi@rtfm.ziplink.net (Mikhail Teterin)
Newsgroups: neosoft.users.freebsd,comp.unix.bsd.freebsd.misc
Subject: Re: Free BSD trouble
Date: 30 Jan 1997 15:28:08 GMT
Organization: Aldan at Newton Upper Falls
Lines: 28
Message-ID: <5cqem8$1sn$1@news.ziplink.net>
References: <32EAF919.17A0@neosoft.com> <5cflae$gal@bonkers.taronga.com>
<5cpfsk$fqk@uuneo.neosoft.com>
Reply-To: mi@ALDAN.ziplink.net..remove-after-`net'
NNTP-Posting-Host: 199.232.255.52
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34784
Honorable Conrad Sabatier
wrote on 30 Jan (in article <5cpfsk$fqk@uuneo.neosoft.com>):
=o <sigh> As usual, the same as with every previous version of FreeBSD I've
= used (since 2.1.0), still refuses to recognize the same IDE CD-ROM drive
= that Windows 95 has no problem whatsoever dealing with (thanks to a
= vendor-supplied driver, of course). In earlier versions I did manage to
= tweak the kernel config later, *after* installing, but *during* the
= install the CD-ROM was useless
Perhaps, if contributed your tweaks back to FreeBSD, they would have
a chance to get into the distribution for you and all others with the
similar hardware.
=Frankly, I find the latest release a major letdown. And I do mean *major*.
=After jumping through more hoops than you'd care to imagine just to get
=anything at all in the way of an upgrade to occur with this latest release,
=what happened? After installing XFree86 3.2, my system was most
=unceremoniously rebooted, after which I discovered, much to my unpleasant
=surprise, that my kernel (along with bin, sbin, etc, and a few other things)
=could no longer be found in the root slice.
Never happened to me... Despite my continuing upgrades (right now
I'm running the 3.0-snapshot).
-mi
--
"Windows for dummies"