Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!darwin.sura.net!udel!newsserv.cs.sunysb.edu!stark.UUCP!cs.sunysb.edu!newsserv!stark!gene From: newsserv!stark!gene@cs.sunysb.edu (Gene Stark) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD - sio (com) and DOS HD problems Date: 19 Sep 93 08:25:50 Organization: Gene Stark's home system Lines: 23 Distribution: world Message-ID: <NEWSSERV!STARK!GENE.93Sep19082550@stark.uucp> References: <1993Sep16.201358.26183@doug.cae.wisc.edu> <NEWSSERV!STARK!GENE.93Sep17075803@stark.uucp> NNTP-Posting-Host: stark.uucp In-reply-to: newsserv!stark!gene@cs.sunysb.edu's message of 17 Sep 93 07:58:03 In article <NEWSSERV!STARK!GENE.93Sep17075803@stark.uucp> newsserv!stark!gene@cs.sunysb.edu (Gene Stark) writes: > The partitioning scheme used in 386BSD/FreeBSD is bizarre, to say the least. > To the best of my understanding, you will not be able to create a partition > for your DOS area, and then see that area from within FreeBSD, unless that > area lives on cylinders that are inside what has been declared to be the > BSD c partition. If you try to create a partition outside this area, you will > get the "unused partition" messages you describe. When I wrote the above, I had only actually tried to mount a hard-drive pcfs under 386bsd 0.1.2.4, and I had the problems I described. I just tried again this morning under FreeBSD, and it looks like some work has been done on the wd driver and disklabeling scheme since 0.1.2.4. I can now say that mounting a PCFS is simply a matter of: (1) adding a partition of type MSDOS with the proper size and offset to your BSD disklabel. (2) Running the mount command as others have mentioned in this thread. The business about problems if the MSDOS area lies outside the declared BSD area no longer seems to be true. - Gene Stark -- stark@cs.sunysb.edu