Date: Sat, 26 Oct 2002 10:06:14 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Terry Lambert <tlambert2@mindspring.com> Cc: Mark Valentine <mark@thuvia.demon.co.uk>, Julian Elischer <julian@elischer.org>, 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: <20021026095818.B5924-100000@gamplex.bde.org> In-Reply-To: <3DB9D2A6.5FBF0CE9@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 25 Oct 2002, Terry Lambert wrote: > Mark Valentine wrote: > > > I fail to see how using ad0a makes it play better with other systems. > > > > Because DOS doesn't refer to its partition by its index in the MBR partition > > table, and apparently some tools therefore feel free to reorder the table on > > a whim. This is a bug in the tools, so they belong in the same bin as BIOSes that interpret the MBR. > > /dev/ad0a results in a method of locating the partition which is closer to > > the DOS algorithm, and therefore survives this. > > > > /dev/ad0s1a makes an incorrect assumption about the MBR partition table index > > being fixed, and therefore blows up. > > OK, say we buy this. > > How does the DOS algorithm distiguisch between partitions, if not by > the order in the table? Not. IIRC, it doesn't permit multiple primary DOS partitions, but logical drives just move around if you add one in the middle. Since DOS doesn't have anything like mount, you get to edit C: and D: in numerous config files instead of just in fstab when the drives move. Bruce 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?20021026095818.B5924-100000>