On Tue, 5 Jun 2001, Blue Lizard wrote:
> >Is there any way to tell DrakX's auto-install mode to install LILO onto
> >/dev/hda1 instead of /dev/hda ? I've looked through the code and the
> >nearest option I can find seems to be
> >$o -> {bootloader}{crushMbr}
> >which, if set to 1, causes LILO to install onto /dev/hda but if set to 0
> >causes LILO to "intelligently" decide whether to install onto the MBR or
> >the partition.
> >How about the following patch:
> > <snip>
> >This adds an extra option
> >$o -> {bootloader}{preserveMbr}
> >which, if set to 1, will force LILO to leave the MBR intact. This
> >auto-install option must obviously be used with care because if the MBR is
> >not valid to start with then the resulting system will not boot.
> so wait...im slower than normal people...im special
> Did u check through the expert install reference to observe the function
> passed to on the bootloader install graphic signal? Then just recreate
> the call in your autoinstall mode. almost cut&paste but following
> whatever signal recognition scheme is used in the autoinstall code.
> Honestly that is the philosophy i would use but then im not quite
> familiar with any of the drakx code, just the guy that wishes for more
> features but doesnt get em.
> <snip>
> Sort of no longer auto but then you seem to be willing to modify code
> on a case by case basis anyway |-|:P
The point is that I don't want to hack the install code for a specific
case: I want to add an extra option so that the whole thing becomes
configurable via the normal mechanism for auto-installs.
I spent over an hour going through the code and this was the cleanest
change I could find: it's a one-line patch, it adds one extra option and
it won't affect anything else (previous auto-install files will continue
to function as before). If you can find something cleaner, please do!
Michael
