On Wednesday 06 June 2001 10:56, you wrote:
> Michael Brown <[EMAIL PROTECTED]> writes:
> > Forget it if you want; it's just an option that I came across a need for
> > yesterday (for boring reasons that I won't go in to), and I thought I may
> > as well contribute the patch that implements it, since it's such a simple
> > change.
>
> We will add a onMbr flag and keep (as obsolete but for compability)
> crushMbr, define it to force onMbr property so that only one is defined...
Would this still allow me to force lilo on the MBR, regardless of what was on
the disk?
What about: unsafe?
The silo code has 'use_partition' which does this, now the lilo code will
have 'onMbr'; any chance that the same term can be used in both places for
consistancy?
>
> Fran�ois.
Dave
