Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!paladin.american.edu!europa.eng.gtefsd.com!uunet!nih-csl!postman From: crtb@helix.nih.gov (Chuck Bacon) Subject: mount -t pcfs fails in freebsd Message-ID: <1993Nov5.135227.6353@alw.nih.gov> Sender: postman@alw.nih.gov (AMDS Postmaster) Organization: National Institutes of Health, Bethesda Date: Fri, 5 Nov 1993 13:52:27 GMT Lines: 37 I've just built my first full bird kernel for FreeBSD, and have found some pleasant surprises. But I've got a problem with mount -t pcfs /dev/wd1e /D (Yes, I thought it was cute to have directories /C and /D for DOS). Whenever I attempt this mount, I get a panic. The message is so short lived on the screen that I can't copy it. It says something about an address (and gives an 8-digit hex number), and something about dumping RAM, and then vanishes, all in about 1/2 second. I've successfully mounted DOS floppies, copied both ways and rm'd files. I've also been successful with mount -t pcfs /dev/wd0e /C Since /C went well, why doesn't /D? Here is a comparison: wd0 has a primary DOS partition, and a type 165 (BSD) partition. FDISK.EXE creates the primary DOS partition exactly one _track_ into the disk. wd1 has an extended DOS partition and another BSD partition. For some reason FDISK.EXE creates the Extended DOS partition exactly one _cylinder_ into the disk. I've very carefully edited the two disklabels to create e partitions in BSD, to reflect these two offsets (after innumerable struggles!), so I'm fairly confident that I've got 'em right. I got the FreeBSD binaries dated Oct. 1, and perhaps I should upgrade. Or have I overlooked something? E-mail appreciated, though I try to read this newsgroup. -- Chuck Bacon - crtb@helix.nih.gov ( alas, not my 3b1 )-: ABHOR SECRECY - DEFEND PRIVACY