Date: Fri, 24 Sep 2004 11:35:27 -0500 From: Mike Meyer <mwm@mired.org> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Dangerously dedicated vs. fully dedicated, etc. Message-ID: <16724.19663.372277.880168@guru.mired.org> In-Reply-To: <200301141936.aa93359@salmon.maths.tcd.ie> References: <vvsmvvv9m7.mvv@localhost.localdomain> <200301141936.aa93359@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
In <200301141936.aa93359@salmon.maths.tcd.ie>, Ian Dowse <iedowse@maths.tcd.ie> typed: > In message <vvsmvvv9m7.mvv@localhost.localdomain>, swear@attbi.com writes: > >Mike, I'll pay back your effort in replying to this long thing by > >working up a patch for the "disklabel" manpage (at least) and, if you > >want, I'll CC you so you can veto things you don't like. I do worry > (B) Dedicated format created by sysinstall > > <start of slice 1> > <start of 'a' partition> > sector 0: boot1 and the DOS slice table, where > the slice table contains one slice > (slice 1) covering the entire disk, > including sector 0. > sector 1: disklabel > sector 2-15: boot2 > sectors 16-31: 'a' partition filesystem superblock > > In this case, there is no boot0, and boot1 serves as the boot > loader that is invoked by the BIOS. Here, all of the boot code > is contained within the first slice and also within the first > partition. Again, the 8k reserved at the start of every ffs > filesystem protects the boot code. Sysinstall sets up fstab to > refer to the partitions as e.g. /dev/ad0s1a (I think). This can also be referred to as /dev/ad0a, like your C case. I personally prefer that because it lets you know that the disk is DD. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16724.19663.372277.880168>