Date: Fri, 25 Oct 2002 20:09:39 +0100 (BST) From: Mark Valentine <mark@thuvia.demon.co.uk> To: Julian Elischer <julian@elischer.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, "M. Warner Losh" <imp@bsdimp.com>, freebsd-arch@freebsd.org Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_disk.c write_i386_disk.c write_pc98_disk.c Message-ID: <200210251909.g9PJ9d4F078508@dotar.thuvia.org> In-Reply-To: <Pine.BSF.4.21.0210251041050.6512-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Julian Elischer <julian@elischer.org> > Date: Fri 25 Oct, 2002 > Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_disk.c write_i386_disk.c write_pc98_disk.c > On Fri, 25 Oct 2002, Mark Valentine wrote: > > What is the cost of having both? > > You can't have both because the naming scheme gives a particular name to > a partition because of how you get to it.. Thaks for this explanation, Julian, I'm beginning to see some light... > ad0a means: > I openned the disk, found a disklabel and this is the first partition > defined in that disklabel. OK... That is a seriously incompatible change in the interpretation of this device name. It is useful only in the absence of an MBR partition, GPT table, or whatever. It is more of a physical representation of the disk than the current one, which is more of a logical interpretation. The current interpretation is more in line with how other i386 operating systems interpret the MBR partition table, which is why my systems are more likely to boot using this notation than your systems using a naming scheme with a hard-wired partition index which isn't guaranteed to remain constant. The GEOM naming scheme therefore removes my ability to specify the partition in the most natural way for this platform. > If someone doesn't know > what ad0s1a means yet then they haven't been paying attention. It doesn't mean what most people would want it to mean, i.e. their FreeBSD root partition, according to the conventions for the PC platform. > To address some of your concerns > We COULD have a /dev/ad0sBa that always reflects the first BSD slice > "a" partition. that would give the characteristics you have asked for.. > and still abides by the naming convention.. (devfs could make a symlink > or something..) but ad0a is already taken.. Hmm. How about if you use a different name space for the new naming scheme, and we can use the old names to symlink, e.g. da0a -> <geomdisk>0sBa? In actual fact I'm less fussy about using /dev/da0a forever than I am at having _some_ /dev/<simplename>0a do the right thing (which is not /dev/<geomdisk>0s1a). Cheers, Mark. -- Mark Valentine, Thuvia Labs <mark@thuvia.co.uk> <http://www.thuvia.co.uk>; "Tigers will do ANYTHING for a tuna fish sandwich." Mark Valentine uses "We're kind of stupid that way." *munch* *munch* and endorses FreeBSD -- <http://www.calvinandhobbes.com>; <http://www.freebsd.org>; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210251909.g9PJ9d4F078508>