Michael Brown 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:
>
>--- usr/bin/perl-install/bootloader.pm.orig Tue Jun 5 15:42:30 2001
>+++ usr/bin/perl-install/bootloader.pm Tue Jun 5 19:09:57 2001
>@@ -222,7 +222,7 @@
>
> require c; c::initSilo() if arch() =~ /sparc/;
>
>- my ($onmbr, $unsafe) = $lilo->{crushMbr} ? (1, 0) : suggest_onmbr($hds);
>+ my ($onmbr, $unsafe) = $lilo->{preserveMbr} ? (0, 0) : ( $lilo->{crushMbr} ? (1,
>0) : suggest_onmbr($hds) );
> add2hash_($lilo, arch() =~ /sparc/ ?
> {
> default => "linux",
>
>
>
>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.
>
>Has been tested and does work.
>
>Michael
>
>
>
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.
This would work for c and in an adjusted sense perl, but might require
some sort of modified call delimeter to pull the function in replacement
of whatever variable exists. Alternatively, u could set a patch in a
tidy little self contained executable of its own to gather the proper
variables at the beginning and just call it later. Sort of no longer
auto but then you seem to be willing to modify code on a case by case
basis anyway |-|:P
Pixel the guy I would talk to if u want more specific to mdk code. Been
enoching for a while so im full of philosophy.
p.s. a.c. is upset today. Pissed about the idle loop modification in
some obscure patch. That guy works too hard.
