Mailinglist Archive: opensuse-bugs (5607 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=726836

https://bugzilla.novell.com/show_bug.cgi?id=726836#c10


--- Comment #10 from Michael Chang <mchang@xxxxxxxx> 2011-10-31 15:45:50 UTC ---
(In reply to comment #6)
> I don't believe that it's true for other packages. Does installing a new
> syslinux rpm or a new grub2 rpm actually update the bootloader itself (akin to
> 'grub2 install /dev/sda' or some such)?
>
> The reason that grub was reinstalled in the first place was to meet some
> dependency due to 'zypper dup' -- since I already had grub2 installed and
> working it really surprised me that grub simply installed over it, the result
> being a non-working system.  I would be equally surprised if simply
> /installing/ syslinux or lilo would overwrite an existing bootloader.

Thanks for the explanation .. can you tell what package depends on grub? Anyway
it makes sense to me that the bug was caused by update and dependency, 

> I see that /etc/sysconfig/bootloader has all of the config options I'd expect
> (including LOADER_LOCATION=none to prevent any post-install).  Is grub 
> honoring
> /etc/sysconfig/bootloader? If I set the LOADER_TYPE to grub2 will 
> re-installing
> grub overwrite the boot sector/bootloader ? 

Depends on the tools you deal with the bootloader -- generally if you use
system wide tools like "update-bootloader" or "yast2 bootloader" they would
honor the sysconfig settings. Use package level tools like grub-install would
not ..

set LOADER_TYPE to grub2 is useless for now .. as it's not ready. Only package
level tools provided to work.

> I might suggest that asking grub/grub2/lilo/syslinux/whatever to conform to 
> the
> *user* preferences in /etc/sysconfig/bootloader is ideal.

I agree.

> Furthermore, and this is a bit of a pipe dream, it'd be nifty if
> 'grub2-install' and 'grub-install' (and others) would grump if they are being
> used and /etc/sysconfig/bootloader is *not* the same value (by that I mean if 
> I
> use grub2-install with /etc/sysconfig/bootloader set to use lilo then I'd 
> think
> if nifty to see a warning message: WARNING: /etc/sysconfig/bootloader
> configured to use lilo, not grub2. Continue?" )

As far as I know these package level tools are not visible to sysconfig
settings (They are identical to upstream thus no concepts about "system"), Use
it and break the settings is expected.

> I hope I am expressing myself clearly here.

YES. Thanks. :)

> Thank you for listening.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.