Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news.bbnplanet.com!cpk-news-hub1.bbnplanet.com!mindspring!uunet!in3.uu.net!136.142.185.26!newsfeed.pitt.edu!jlfox From: jlfox+@pitt.edu (James L Fox) Newsgroups: comp.unix.bsd.freebsd.misc Subject: MAKEDEV problems Date: 30 Jan 1997 17:31:18 GMT Organization: University of Pittsburgh Lines: 33 Message-ID: <5cqlt6$m0t@usenet.srv.cis.pitt.edu> NNTP-Posting-Host: unixs-eval.cis.pitt.edu Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34378 Should have left "well enough alone", but I didn't. I have been running 2.1.0 troublefree for months and wanted to get it to recognize my soundblaster card. Apparently, I should have merely done "MAKEDEV snd0", but I decided to build a new kernel in the process to tidy things up. Following chapter 10 in Inst & Running FreeBSD I got confused at the MAKEDEV section and did a "MAKEDEV all", which I think I will regret. I wasn't worried when I rebooted to try the new kernel since the book says "don't panic" if your new kernel doesn't work, just reboot with kernel.old. Well, here's what I'm getting... (I'm booting from drive 1 of an Ultrastor SCCSI controller) /dev/sd1s1b no such file or directory .. /dev/sd1s1f no such file or directory Can't stat /dev/sd1s1f Automatic file system check failed! Unfortunately, this state puts me into a read-only file system, from which I can't even see /usr/src/sys/i386/conf/MYKERNEL and wouldn't be able to fix it anyway. kernel.old produces the same results. Why is the system looking for sd1s1b and sd1s1f ? What did I do wrong and most importantly, what do I do now? :-( Thanks, --Jim Fox