http://bugzilla.novell.com/show_bug.cgi?id=618514
http://bugzilla.novell.com/show_bug.cgi?id=618514#c4
Jiri Srain changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #4 from Jiri Srain 2010-07-01 06:15:29 UTC ---
make install => you are installing vanilla kernel, not SUSE, right? I don't
think that we will do anything about that. Our tools (e.g. mkinitrd) expect
that kernel is as modular as the SUSE one. (and I don't know why vanilla's
'make install' always calls mkinitrd) If you have kernel compiled differently,
you are on your own. May also be related to different kernel version, I'm not a
kernel geek.
If you don't agree, create a separate bug on mkinitrd.
udev: I'm not sure what causes these error messages, may be incompatibility
with some options in your kernel, maybe kernel version, maybe patches in SUSE
kernel, but I'm only guessing here. I suggest filing a separate bug against
either device mapper or udev, IMHO it is unrelated to warnings regarding some
of your modules which are built-in in your kernel by mkinitrd.
Regarding LILO: There is only one hint I can give you: Find someone who will
maintain LILO itself as well as its support in YaST and other libraries.
openSUSE mailing lists (factory) are the right place for this, not bzilla. Just
be aware that
- LVM operation may move volumes -> system gets unbootable no matter which BL
you use, you need /boot outside LVM to be safe
- XFS is known for moving files under some circumstances even if they are not
changed itself. Therefore even if you successfully install LILO on XFS, at some
point of time it can stop working. Maybe you are just more lucky than others.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.