Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.nla.gov.au!act.news.telstra.net!newshost.telstra.net!asstdc.scgt.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.com!imci4!newsfeed.internetmci.com!news.mathworks.com!zombie.ncsc.mil!nntp.coast.net!news2.acs.oakland.edu!newshub.gmr.com!news.delcoelect.com!c23peg From: c23peg@mail.delcoelect.com (Perry Grieb) Newsgroups: comp.unix.bsd.freebsd.misc Subject: 2nd 2.1R install by newbie Date: 17 Mar 1996 19:56:10 GMT Organization: Delco Electronics Corp. Lines: 35 Distribution: world Message-ID: <4ihqoq$eo4@kocrsv08.delcoelect.com> NNTP-Posting-Host: koptsy20.delcoelect.com Originator: c23peg@koptsy20 I finally completely torched my linux partition (a 420M IDE drive) to make room for a bigger FreeBSD install. After about 6 hours on my 1x CDROM 20MHz 386 system, I found my /usr filesystem is at 107% with a negative amount of free space available. So now what do I do (I mean besides installing for only 5.5 hours next time)??? After I rebooted, there does not seem to be anything in any log file. Of course, the kernel you run off the boot floppy isn't smart enough to link and log to the hard drive that you just created the FreeBSD filesystem(s) on. And to top it off, I didn`t sit at the monitor for 6 hours to see when & what packages failed to install. Are the pkg_* utilities smart enough to be able to tell me which packages are bad (I assume that something didn't install correctly)? As a suggestion, it would sure be nice to have an extra VC w/ getty (ALT-F3) for the boot floppy kernels, so you could login in as root and monitor a new install (with df and perhaps a small set of binaries) to see how things are progressing. Thanks for listening and for any suggestions that you have. Of course, I could just start over if there isn't a better way... It's not like I spent the last 6 months customizing the system. -- Perry Grieb c23peg@eng.delcoelect.com Unsolicited commercial e-mail will be proofread for $250/hour.