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.