Return to BSD News archive
#! rnews 2568 bsd Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!uunet!in3.uu.net!128.230.129.106!news.maxwell.syr.edu!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!news-feed1.tiac.net!news-in.tiac.net!posterchild!news@tiac.net From: tarbet@swaa.com (Margaret Tarbet) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Mounting DOS partitions: one more time around Piccadilly Circus Date: Sun, 01 Jun 1997 15:33:40 GMT Organization: Software Art & Architecture Incorporated Lines: 48 Message-ID: <33918f6e.32900@news.tiac.net> Reply-To: tarbet@swaa.com NNTP-Posting-Host: momcat.tiac.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Newsreader: Forte Agent 1.0/16.390 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:41991 I'm still pretty foggy on _exactly_ how the slice-naming scheme works, and what's possible or not currently with dos parts, so i'm getting confused and derailed when i try to do certain things that look as tho they should work fine. Here is the setup: 6 scsi disks, partitioned so: dev 0: 500MB FAT16 primary (C:), 300MB FAT16 extended, (D:), 60MB FBSD dev 1: 1004MB FAT16 extended (E: 502MB, F:502MB) 500MB non-dos (an old SysV part with a veritas fs on, i think - having to play musical disks hasn't been the best for my recordkeeping :-) 1280MB FBSD dev 2: 1000MB FAT16 extended (G:500MB, H:250MB, I:250MB) 384MB FBSD dev 3, 4, & 7 [0 on channel 1 of my 2742T]. -- all FAT16 extended parts <= 1023MB, logically subdivided into dos drives with 4K or 8K clusters. Devices 5 and 6 are a jaz and a cdrom drive, resp. 1. Can i mount the primary partition (C:)? What dev is it represented by? 2. I did a MAKEDEV successfully for D: as sd0s5 and for E: and F: as sd1s5 and sd1s6, though i originally supposed from what i'd read that they should have been sd1s5a and s5b, respectively. s5a et seq. do exist, but it's not clear to me what they actually do for a living, now that i know they're not, as i had thought them to be, the avatars of the logical drives in the extended part. 3. I tried to MAKEDEV G: as sd2s5, but failed: no such device. Why not? How do i fix that? I can certainly get at the FBSD part on the device, so it's not the case that FBSD can't see the device. 4. Presumably i'll run into similar problems with devices 4 and 7. If i can solve the problem for G:, will that solution also work for those devices? 5. How stable is msdosfs for clusters <= 8K? Are writes "known" to be safe? =margaret