From owner-freebsd-questions Fri Aug 24 12:28:12 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-94-248-46.mmcable.com [24.94.248.46]) by hub.freebsd.org (Postfix) with SMTP id CD63F37B410 for ; Fri, 24 Aug 2001 12:27:59 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 45777 invoked by uid 100); 24 Aug 2001 19:27:58 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15238.43710.765196.737472@guru.mired.org> Date: Fri, 24 Aug 2001 14:27:58 -0500 To: Timothy Luoma Cc: questions@freebsd.org Subject: Re: mount questions continued In-Reply-To: <3870009@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Timothy Luoma 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 , 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. 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