Mailinglist Archive: opensuse-factory (1233 mails)
| < Previous | Next > |
[opensuse-factory] GRUB, instead of gfxmenu
- From: Felix Miata <mrmazda@xxxxxx>
- Date: Fri, 28 Nov 2008 16:10:03 -0500
- Message-id: <49305E2B.80202@xxxxxx>
I did updates via zypper dup from download.opensuse.org/factory this AM on
one system, and subject was the result. MBR is standard code. Grub is on
(hd0,0). Why would any updates have found it necessary to mess with the
installed Grub on (hd0,0)? Which update did it? How do I prevent it from
happening again?
Possible related matter:
I use a /boot which is shared between Fedora and openSUSE. As a consequence,
I try to avoid letting either mess with Grub at all. To that end, I don't
normally mount the /boot partition on /boot. Instead, I automount it on
/disks/hda/boot, and when I know something needs (hd0,0) it to actually be on
/boot, I remount it there, as when running mkinitrd or installing a new kernel.
Also to that end, I've renamed /etc/grub.conf to /etc/grub.conf- to prevent
scripts that use that file from tampering with the real boot partition. As a
consequence of that, lately the kernel installations have been hampered by
e.g what is show here:
# Bootsplash: openSUSE (1024x768)
# 14840 blocks
# 2008-11-20 19:47:51 ERROR: Core::ReadFiles: Failed to open /etc/grub.conf
# /boot directory is not mounted. If this is bad detection you can avoid it
by 'export PBL_SKIP_BOOT_TEST=1'
# error: %post(kernel-pae-base-2.6.27.5-3.2.i586) scriptlet failed, exit status
1
#
# 2008-11-20 19:51:55 kernel-pae-base-2.6.27.5-3.2.i586.rpm install failed
(Full /var/log/zypp/history at
http://fm.no-ip.com/tmp/SUSE/Factory/zypp-history-kt880 )
Note that the "# /boot directory is not mounted..." above is a lie. It may
say in /etc/fstab that that should have been the case, but it was not the
actual state while the new kernel was being installed. Why does a new kernel
installation require anything to access /etc/grub.conf anyway?
--
"Love is not easily angered. Love does not demand
its own way." 1 Corinthians 13:5 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
one system, and subject was the result. MBR is standard code. Grub is on
(hd0,0). Why would any updates have found it necessary to mess with the
installed Grub on (hd0,0)? Which update did it? How do I prevent it from
happening again?
Possible related matter:
I use a /boot which is shared between Fedora and openSUSE. As a consequence,
I try to avoid letting either mess with Grub at all. To that end, I don't
normally mount the /boot partition on /boot. Instead, I automount it on
/disks/hda/boot, and when I know something needs (hd0,0) it to actually be on
/boot, I remount it there, as when running mkinitrd or installing a new kernel.
Also to that end, I've renamed /etc/grub.conf to /etc/grub.conf- to prevent
scripts that use that file from tampering with the real boot partition. As a
consequence of that, lately the kernel installations have been hampered by
e.g what is show here:
# Bootsplash: openSUSE (1024x768)
# 14840 blocks
# 2008-11-20 19:47:51 ERROR: Core::ReadFiles: Failed to open /etc/grub.conf
# /boot directory is not mounted. If this is bad detection you can avoid it
by 'export PBL_SKIP_BOOT_TEST=1'
# error: %post(kernel-pae-base-2.6.27.5-3.2.i586) scriptlet failed, exit status
1
#
# 2008-11-20 19:51:55 kernel-pae-base-2.6.27.5-3.2.i586.rpm install failed
(Full /var/log/zypp/history at
http://fm.no-ip.com/tmp/SUSE/Factory/zypp-history-kt880 )
Note that the "# /boot directory is not mounted..." above is a lie. It may
say in /etc/fstab that that should have been the case, but it was not the
actual state while the new kernel was being installed. Why does a new kernel
installation require anything to access /etc/grub.conf anyway?
--
"Love is not easily angered. Love does not demand
its own way." 1 Corinthians 13:5 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |