Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Feb 2008 14:10:17 -0500
From:      Jerry McAllister <jerrymc@msu.edu>
To:        "Brian A. Seklecki" <bseklecki@collaborativefusion.com>
Cc:        Jerry McAllister <jerrymc@msu.edu>, Jeff Gold <jeff.gold@gmail.com>, freebsd-questions@freebsd.org
Subject:   Re: diskLabelCommit fails within a sysinstall script?
Message-ID:  <20080220191017.GA56942@gizmo.acns.msu.edu>
In-Reply-To: <1203533333.10391.49.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com>
References:  <4bded9640802191245q20832a83j31723763ab21a940@mail.gmail.com> <20080219213254.GB47232@gizmo.acns.msu.edu> <1203533333.10391.49.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 20, 2008 at 01:48:53PM -0500, Brian A. Seklecki wrote:

> 
> On Tue, 2008-02-19 at 16:32 -0500, Jerry McAllister wrote:
> > I don't know about all you ask, but the 'c' partition should always
> > be there and be set to identify the whole slice eg start at 0 and
> > the size be the size of the slice.   The system uses it to identify
> 
> its a damn shame that this is still the case.  defeats / undermines the
> whole purpose of /dev/[as][d##][s#][a-z]
> 
> /dev/[as][d##][s#] alone can represent entire BIOS partitions
> /dev/[as][d##] alone can represent entire disk
> 
> Not sure why we still need a 'c' slice for legacy ?!

Probably.  I don't really know how it gets used, but the system
still seems to expect it somewhere.   

////jerry

> -- 
> Brian A. Seklecki <bseklecki@collaborativefusion.com>
> Collaborative Fusion, Inc.
> 
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080220191017.GA56942>