Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:1598 comp.unix.bsd:11816 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.questions,comp.unix.bsd Subject: Re: Can't logon after running buildworld.sh (patchkit-0.2.2) Date: 8 Apr 1993 08:44:21 -0500 Organization: Armstrong Lab MIS, Brooks AFB TX Lines: 62 Message-ID: <1q1a7lINNc0v@hrd769.brooks.af.mil> References: <1993Apr6.144035.21705@latcs1.lat.oz.au> <1pt82bINNctv@hrd769.brooks.af.mil> <9304072254.ae10229@gate.demon.co.uk> NNTP-Posting-Host: hrd769.brooks.af.mil In article <9304072254.ae10229@gate.demon.co.uk> damian@centrix.demon.co.uk (damian) writes: }In article <1pt82bINNctv@hrd769.brooks.af.mil> burgess@hrd769.brooks.af.mil (Dave Burgess) writes: }>In article <1993Apr6.144035.21705@latcs1.lat.oz.au> wongm@latcs1.lat.oz.au (M.C. Wong) writes: }>> }>>Hi, }>> Ok, this is the situation : }>> }> }>> 4) Next, I was a bit curious (actually foolish) to try executing }>> buildworld.sh, and hell, that lasted for more than 10 hrs on a 486/33 }>> machine !! The worst thing yet to come! Having waited long for the }>> buildworld.sh, I reboot the system, and then trajedy, I can never login }>> as root or as any other users I created!! }>> I tried to use back the old kernel (the one extracted from }>> kernel-1.2.pccons-fix-1.tar.Z) and it didn't work either. }>> }>> }>> So, in order for me to get an updated version of kernel, is patchkit more }>>recommended, or simple pinch a copy of the latest kernel binary from any site }>>out there , which is prefered ? }>> }> }>I deleted a bunch of your message. Sorry 'bout that. }> }>During boot-up (specifically during the fsck), hit Control-c. }> }>This will interrupt the boot and put you into single user mode as root. } }Don't forget that the root disk is still read-only at this stage, in }addition you have to do:- } }umount -a }mount -a -t nonfs } }to make it writeable. } }It took me a few hours to suss that out! } }Damian } Absolutely right. I apologize for leaving that minor detail out (NOT!) Another way to make the root disk writable (the one I used :-) is: mount -u /dev/[xx]0a / Where [xx] is wd, or as, or whatever disk you are trying to remount. In fact, I have added this line to my /.profile so that, when I interrupt the fsck, it automagically remounts the drive. The "mount -a -t nonfs" is also highly recommended for those folks that are using a 'REAL' disk partitioning scheme... -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX