-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2008-11-28 at 16:51 -0500, Felix Miata wrote:
On 2008/11/28 22:27 (GMT+0100) Carlos E. R. composed:
On Friday, 2008-11-28 at 16:10 -0500, Felix Miata wrote:
# /boot directory is not mounted. If this is bad detection you can avoid it by 'export PBL_SKIP_BOOT_TEST=1'
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.
I opened a bugzilla that was solved with that hack (export PBL_SKIP_BOOT_TEST=1). The cause was different that yours, but the solution could be the same. If you are interested I'll post the bug number, but now my dinner is waiting :-)
Please? :-)
Bug 440337 It may not be related to your problem, but the solution to my problem was to use that variable because boot partition is not detected on a chroot. But you can report your situation, so that they can alter the code and your /boot is detected.
Why does a new kernel installation require anything to access /etc/grub.conf anyway?
Because it adds a new entry to boot that precise kernel, instead of reusing the "vmlinuz" symlink.
The question remains. Boot with openSUSE Grub happens via /boot/grub/menu.lst, not /etc/grub.conf.
Sorry, I read to fast. I confused the file.
AFAICT, the latter is a config file for installing Grub's stage* files, which has zip todo with configuring new kernels in Grub's menu.
Yes, you are right. It should not be altered, I think. Unless grub itself is reinstalled :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkwhREACgkQtTMYHG2NR9VDJACfei22F42PYm4iwddB5HErxDBm fLIAoJJs6e6+YBo72WkvzBTyvYhdF73i =m+ul -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org