Date: Fri, 25 Oct 2002 05:30:05 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: John Baldwin <jhb@FreeBSD.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, <cvs-all@FreeBSD.org>, <cvs-committers@FreeBSD.org>, Takahashi Yoshihiro <nyan@jp.FreeBSD.org>, Bakul Shah <bakul@bitblocks.com> Subject: Re: cvs commit: src/lib/libdisk Makefile chunk.c write_alpha_dis Message-ID: <20021025052110.M1456-100000@gamplex.bde.org> In-Reply-To: <XFMail.20021024144015.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 24 Oct 2002, John Baldwin wrote:
> On 24-Oct-2002 Poul-Henning Kamp wrote:
> > In message <20021025041846.B1170-100000@gamplex.bde.org>, Bruce Evans writes:
> >>On Thu, 24 Oct 2002, Poul-Henning Kamp wrote:
> >>>
> >>> Make sure you don't have one of the bogus "ad0a" style devices
> >>> listed for your root filesystem.
> >>
> >>Yes, standard slice names are now decreed bogus. You have to use
> >>i386-centric names like ad0s4a, at least on i386's with disks that
> >>actually have slices.
> >
> > Please stop the FUD Bruce.
> >
> > First of all, this is no longer architecture dependent. You can
> > use MBR's on your sparc64 if you for some reason feel like it.
It never was arch-dependent, except for hacks in some arches. You can use
MBR's on md devies or even on regular files if you want.
> > Second, the names follow what is on the disk.
> >
> > If your disk has only a BSD disklabel, then the names will be
> > constructed by appending a single letter and we get:
> > ${disk}[a-h]
Same as before.
> > If your disk has an MBR, then the slices are named by appending
> > "s%d" so the names become:
> > ${disk}s[1-N]
> >
> > If you put a BSD disklabel in one of the slices, the name
> > will still be constructed by appending a single letter, so the
> > names become:
> > ${slice}[a-h]
> > or if you like
> > ${disk}s[1-N][a-h]
I.e., the support for the compatibility slice which people have been
happily using for 7 years is dropped because you don't like it.
> And all i386 disks have MBR's cause the BIOS basically wants them
> there and won't work without them. Pretending that they don't
> exist is just nonsense.
Only boot drives on systems with broken BIOSes have this requirement.
Bruce
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?20021025052110.M1456-100000>