On Sat, Jan 28, 2012 at 01:01:41PM -0500, Phillip Susi wrote:
> On 01/28/2012 12:00 PM, Brian C. Lane wrote:
> > Because there may be some situations where users don't want the flag to
> > be set. And there is a small chance that having it set could cause
> > problems.
> 
> Like what?  The only thing that looks at the flag is the microsoft MBR boot 
> code ( which you aren't using anyway with GPT ), and certain broken bioses 
> that insist on there being some partition with the flag set.  Since basically 
> every system out there has some partition with the boot flag set, ( and some 
> bioses require it ) I can't see how it could possibly be a problem.
> 

We can't know for certain that there are not BIOS's that check to make
sure it isn't set. Since that is how the spec was written it is possible
that such a BIOS exists.

It would be alot easier to just set it, but then what do we do if we
find out that there are others expect it to be clear?

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)

Attachment: pgpt7HlfJoEbp.pgp
Description: PGP signature

Reply via email to