Date: Thu, 24 Oct 2002 13:20:55 -0700 From: Bakul Shah <bakul@bitblocks.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Takahashi Yoshihiro <nyan@jp.FreeBSD.org>, bde@zeta.org.au, cvs-committers@FreeBSD.ORG, cvs-all@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: <200210242020.QAA29385@valiant.cnchost.com> In-Reply-To: Your message of "Thu, 24 Oct 2002 19:09:50 %2B0200." <1103.1035479390@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> Make sure you don't have one of the bogus "ad0a" style devices
> listed for your root filesystem.
Yup, that indeed was the problem. Thanks!
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.
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?200210242020.QAA29385>