[Bug 816102] New: lilo not being buillt with lvm
https://bugzilla.novell.com/show_bug.cgi?id=816102
https://bugzilla.novell.com/show_bug.cgi?id=816102#c0
Summary: lilo not being buillt with lvm
Classification: openSUSE
Product: openSUSE Factory
Version: 13.1 Milestone 0
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bootloader
AssignedTo: jsrain@suse.com
ReportedBy: suse@tlinx.org
QAContact: jsrain@suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28)
Gecko/20120306 Firefox/3.6.28
When I run the latest version from factory
aka lilo-23.2-78.1.x86-64, I get errors about it not being built with LVM
configured:
> sudo lilo -v
LILO version 23.2 (released 09-Apr-2011)
* Copyright (C) 1992-1998 Werner Almesberger (until v20)
* Copyright (C) 1999-2007 John Coffman (until v22)
* Copyright (C) 2009-2011 Joachim Wiedorn (since v23)
This program comes with ABSOLUTELY NO WARRANTY. This is free software
distributed under the BSD License (3-clause). Details can be found in
the file COPYING, which is distributed with this software.
Reading boot sector from /dev/sdc
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Warning: device-mapper (254) referenced in /proc/partitions,
but LILO is configured without DEVMAPPER option. Skipping device.
Using MENU secondary loader
Calling map_insert_data
Boot image: /boot/vmlinuz-3.8.4-Isht-Van
Added 384-Isht-Van *
....adds others kernels...
Reproducible: Always
Steps to Reproduce:
1. Anyone testing ability to use lilo these days?
2.
3.
Actual Results:
see above Details...
Expected Results:
When I build it locally, since I have the devel files for lvm installed, it
automatically includes it.
If SuSE built with all it's devel files installed, it would more closely
approximate a fully installed suse Devel system.
Just an idea...
Otherwise, you need to include whatever deps it needs to do it...?
FWIW, if I had to rely on the suse binary lilo for this and it was
failing, I would rate the severity higher than 'normal'...
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c3 Dinar Valeev <dvaleev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse@tlinx.org --- Comment #3 from Dinar Valeev <dvaleev@suse.com> 2013-04-19 13:09:24 UTC --- please try lilo package from http://download.opensuse.org/repositories/home:/k0da:/branches:/Base:/System... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c4 --- Comment #4 from L. A. Walsh <suse@tlinx.org> 2013-04-19 09:17:37 PDT --- Are you sure that is spelled right? Object not found! The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again. If you think this is a server error, please contact the webmaster. Error 404 download.opensuse.org Fri Apr 19 18:16:26 2013 Apache/2.2.12 (Linux/SUSE) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c L. A. Walsh <suse@tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse@tlinx.org | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c5 --- Comment #5 from Dinar Valeev <dvaleev@suse.com> 2013-04-19 16:39:48 UTC --- Created an attachment (id=536149) --> (http://bugzilla.novell.com/attachment.cgi?id=536149) lilo with devmapper support Ah.. still not published. Try attached one. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c Dinar Valeev <dvaleev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse@tlinx.org -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c6 L. A. Walsh <suse@tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse@tlinx.org | --- Comment #6 from L. A. Walsh <suse@tlinx.org> 2013-04-19 14:59:37 PDT --- Note -- the attached lilo works -- but I wasn't questioning the ability to build such -- that's ultra trivial (by that I mean, I just had to install the source and build it in my system's native environment using rpmbuild -- no special setup, no special roots...etc...)... The step that needs to be examined is how the problem happened in the first place? I.e. was it just luck that it built correctly before or was something changed? Also -- isn't it even tested with such -- Note -- I'm not, right now, trying to even boot off an lvm partition -- just had them on my system, so this would crop up if you used lilo at all with any system that had lvm partitions -- including data-only, non-root, non-boot partitions. That it fell through the cracks is more the bug I'm concerned about rather than the actual fixing of the build -- though certainly that solves the immediate issue for this "go round"... ;-)... Anything that can be done to build in auto-safety checks to automatically catch these things? FWIW -- I try to write my code to check for all my "stupid errors" -- in how I all the routines -- cuz, I know over time, I eventually will forget something and if there is _any_ way something *can* break, I'll *eventually* break it (Murphy corollary ;-). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c7 Dinar Valeev <dvaleev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse@tlinx.org --- Comment #7 from Dinar Valeev <dvaleev@suse.com> 2013-04-19 23:09:28 UTC --- Well, isn't bug about lilo built without devmapper? For actual change you could check my branch. I don't know what you are referencing to, but I think lilo was never built with devmapper support. If you could confirm, that my package fixes a problem for you, I'll forward the fix to devel project and then to Factory. I don't use who uses lilo (x86) nowadays, I involved in fixing powerpc part of it. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c8 L. A. Walsh <suse@tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse@tlinx.org | --- Comment #8 from L. A. Walsh <suse@tlinx.org> 2013-04-19 16:29:59 PDT --- I just tried the 12.3 version -- it doesn't show the problem (i.e. it IS build with lvm)... That's why it stood out.... I use lilo -- and, at one time, it was favored among kernel developers, but I don't know if that is still the case. It was developed for linux, where as grub hides linux-isms, that might make it less desirable if your focus was on the internals and mechanics of linux (vs. a consumer who wouldn't notice the difference)..... So your 'fix', repairs the damage that has entered into factory... But that's why I asked "what changed"... since the 12.3 version works. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=816102 https://bugzilla.novell.com/show_bug.cgi?id=816102#c9 Dinar Valeev <dvaleev@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #9 from Dinar Valeev <dvaleev@suse.com> 2013-04-20 09:56:56 UTC --- AFAIK nothing has been changed. lilo (x86) was not touched 18 months. fixed with https://build.opensuse.org/request/show/172614 -- 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.
participants (1)
-
bugzilla_noreply＠novell.com