Date: Fri, 25 Oct 2002 10:42:55 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Mark Valentine <mark@thuvia.demon.co.uk> Cc: cvs-all@freebsd.org, cvs-committers@freebsd.org, bde@zeta.org.au, Takahashi Yoshihiro <nyan@jp.FreeBSD.org>, Poul-Henning Kamp <phk@critter.freebsd.dk>, (Bakul Shah) <bakul@bitblocks.com> Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_dis Message-ID: <XFMail.20021025104255.jhb@FreeBSD.org> In-Reply-To: <200210251102.g9PB2jwM066925@dotar.thuvia.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25-Oct-2002 Mark Valentine wrote: >> From: bakul@bitblocks.com (Bakul Shah) >> Date: Thu 24 Oct, 2002 >> Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_disk.c write_i386_disk.c >> write_pc98_disk.c > >> As far as the naming scheme (ad0s1t2u3w4a etc.) is concerned, >> it is all a hack (historical or not)! It does not follow the >> One True Hack (pathnames). Years ago (even before the >> Moronic Boot Record was invented) in a level1 boot I used >> >> <device-name>/<slot>/<partition>/<root-relative-pathname> >> >> or some such syntax to select what to boot. For example, >> >> wd/0/a/kernel >> >> instead of wd(0,a)/kernel. Made perfect sense to me: if you >> have a name-space you name else you index what comes next and >> recurse. Makes even more sense so when you can have a >> stackable disk sub-system. > > /dev/motherboard/pcibus/0/pcib/0/pci/0/7/0/ahc/0/0/0/0/da/0/4/a/kernel, > anyone? :-) /dev/acpi/pcib/0/... :-P -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20021025104255.jhb>