Date: Fri, 24 Aug 2001 14:27:58 -0500 From: Mike Meyer <mwm@mired.org> To: Timothy Luoma <luomat@peak.org> Cc: questions@freebsd.org Subject: Re: mount questions continued Message-ID: <15238.43710.765196.737472@guru.mired.org> In-Reply-To: <3870009@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Timothy Luoma <luomat@peak.org> types: > Ok, here is what I have mounted automatically > I've got a FAT32 2nd partition ... would that be > /dev/ad0s2a or /dev/ad0s1a or ??? The correct answer is behind door #3: /dev/ad0s2. > I tried several versions like > mount_msdos /dev/ad0s2d /win > and keep getting > /win does not exist > (Of course it doesn't exist, that's why I'm trying to > mount it there) It's complaining that the directory /win doesn't exist. You have to create it before you can mount something on it. > I'm guessing I have the device name wrong. How can I > figure out the correct device name? By knowing how disk device names are built. There's an entry in the handbook at <URL: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-naming.html >, but it pretty much sucks. The first letters are the driver. The above page covers that quite nicely. The digit(s) following those are the physical disks on that driver(*), starting at 0. About the only time you'll need to deal with devices like ad0 is if you're using dangerously dedicated devices, or mucking with the boot sector on the disk. If the disk has slices, the next letter is s, and the the slice number. Slices follow the MS convention, and start at 1. Slices 1-4 are the physical slices. Logical slices in extended partitions start at 5. If you are dealing with file systems that occupy slices - which means pretty much anything but Unix - that's all you need to specify: ad0s2 in your case. If the slice is being used by a BSD system, then it will have have partitions inside of it. Those are given letters, starting at a. So the first partition in the second slice of the first disk on ad is ad0s2a. If your disk is dangerously dedicated, slice numbers aren't needed. Requests for slice table information get a table with slice 1 describing the entire disk, and unused slices 2-4. <mike *) Note that multiple controllers - even of different physical types - using the same driver have the same initial letters, so the drive numbers will have to be unique across them all. Which is why I've got da0 and da1 on one ahc, da2 is a umass device, and da3 on a second scsi controller. -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15238.43710.765196.737472>