"Brian J. Murrell" <[EMAIL PROTECTED]> writes:
> > do problems with DrakX. Ask pixel :).
> Pixel? What was the problem with it? Just so I understand.
The DrakX code try to get the current kernel with /boot/vmlinuz, if
kernel-linus is installed after kernel-classic the guys will reboot
with the kernel-linus which it's bad by default.
> > i don't think it's too much ''distribution'' to do this.
> Not sure what this means.
A distributions shouldn't call program from /usr/local/bin, when it's
not included we should resolve the problem in our side and
automatically configure for user.
> But why bother? I never touch my lilo.conf, I just fiddle with symlinks
> in /boot (mv <current> <old>; ln <new> <current>) and it has never
> caused problems for me.
after install yes, maybe if pixel set-up a global variable
DRAKX_INSTALL=true and in %post i do the symlinks in case is not true.
> > anyway we can hope with grub to solve this sort of problems.
> What problems?
can point entry on /boot/vmlinuz /boot/vmlinuz don't need to
regenerate a boot.b and even if the symlink is wrong continue to boot
on other entry.
--Chmouel
