Date: Fri, 25 Oct 2002 12:46:24 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Mark Valentine <mark@thuvia.demon.co.uk> 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: <Pine.BSF.4.21.0210251230340.7147-100000@InterJet.elischer.org> In-Reply-To: <200210251909.g9PJ9d4F078508@dotar.thuvia.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Oct 2002, Mark Valentine wrote: > > The GEOM naming scheme therefore removes my ability to specify the partition > in the most natural way for this platform. I dispute that. The install code has been using ad0s1a for about 5 years I think. Very few systems have ad0a in /etc/fstab as we specifically have been telling people to not do that for ages.. > > > 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. Most systems other than BSD and Linux only ever see their own partitions. We are trying to set things up so we can read anything anywhere any time. Anyway I had a machine where the -current root partition was ad1s4e. How does the old scheme help me? ad1s3 was also a BSD slice (FBSD3.x) > > > 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). the simplest you're likely to get is ad0s1a if you don't know where your root is you are in trouble. One scheme I played with was: /dev/ad0/whole /dev/ad0/s1 /dev/ad0/s1/a /dev/ad0/bsd0 --> s1 /dev/ad0/s1/whole /dev/ad0/s2 /dev/ad0/s2/whole /dev/ad0/s3 /dev/ad0/s3/whole /dev/ad0/s4 /dev/ad0/s4/whole so that /dev/ad0/bsd0/a would always be the root but I don't know if the new devfs can do that.. This had a lot of advantages but blew POLA right out the window :-) > > 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?Pine.BSF.4.21.0210251230340.7147-100000>