[Bug 450643] New: yast2 bootloader aborts when /proc is not mounted
https://bugzilla.novell.com/show_bug.cgi?id=450643 Summary: yast2 bootloader aborts when /proc is not mounted Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andi-nbz@firstfloor.org QAContact: jsrain@novell.com Found By: --- When /proc is not mounted yast2 bootloader aborts after reading /proc/meminfo It should ignore that error instead. No no yast2 logs, but it's trivial to reproduce. I ran into that while trying to use it inside the rescue cd, but chrooted -- 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=450643 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |jreidinger@novell.com -- 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=450643 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450643#c1 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Josef Reidinger <jreidinger@novell.com> 2008-12-02 05:10:11 MST --- Unmounted /proc is fatal error and really not expected. Lot of program fail if it doesn't have it. If you want work in chroot you must bind it. so mount /dev/... /chroot mount --bind /proc /chroot/proc mount --bind /dev /chroot/dev mount --bind /sys /chroot/sys chroot /chroot this is expected and without /proc a lot of programs doesn't work. -- 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=450643 User andi-nbz@firstfloor.org added comment https://bugzilla.novell.com/show_bug.cgi?id=450643#c2 Andi N Kleen <andi-nbz@firstfloor.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #2 from Andi N Kleen <andi-nbz@firstfloor.org> 2008-12-02 06:35:35 MST --- Yes I know about mount --bind. No I don't type in all of this on a rescue cd session. Sorry, abort() on missing /proc is not expected and just wrong. At least give a proper error message like the proc utils. But really aborting on missing /proc/meminfo (or any missing file) is just bad programming and there's no excuse at all for doing that. Also not reading the available memory is clearly not a fatal error for yast. Just return 128MB in this case. -- 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=450643 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450643#c3 Josef Reidinger <jreidinger@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jreidinger@novell.com |yast2-maintainers@suse.de Status|REOPENED |NEW --- Comment #3 from Josef Reidinger <jreidinger@novell.com> 2008-12-02 06:48:17 MST --- Hmm, perl-Bootloader nor yast2-bootloader doesn't read directly /proc/meminfo. So problem is in yast, here is direct usage of /proc/meminfo: gtk/integrate/YaST2.call:MEM_TOTAL=`awk '/^MemTotal:/{ print $2 }' /proc/meminfo` installation/startup/YaST2.call:MEM_TOTAL=`awk '/^MemTotal:/{ print $2 }' /proc/meminfo` installation/startup/First-Stage/F08-logging: USE=`awk '/^MemFree:/{ n=2 ; printf "%d\n", $n/3 }' /proc/meminfo` repair/data/filenames:/proc/meminfo yast2/library/agents/proc_meminfo.scr: (`File("/proc/meminfo")), // real file name So I reassign it to yast-maintainers and also decrease severity to low, as this is not much expected scenario without /proc. -- 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=450643 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450643#c4 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com Status|NEW |NEEDINFO Info Provider| |jreidinger@novell.com --- Comment #4 from Michael Andres <ma@novell.com> 2008-12-03 09:18:37 MST --- But the problem does not seem to be directly reading /proc/meminfo. Neither YaST2.call nor proc_meminfo.scr abort if the file is not there. Scr read will just return an empty map. YaST2.call will disable qt/gtk if there is to less memory. If bootloader has to abort due to missing input data, maybe there is a message to improve? Otherwise we should close this unless someone is able to reproduce it, or provides some log that reveals what's actually happening. -- 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=450643 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450643#c5 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|ma@novell.com | AssignedTo|yast2-maintainers@suse.de |jsrain@novell.com Status|NEEDINFO |NEW Info Provider|jreidinger@novell.com | --- Comment #5 from Michael Andres <ma@novell.com> 2008-12-09 09:01:49 MST --- Forget about my previous comment. Given that without /proc not just meminfo, but also partitions, mounts, devices and various others are not available, we could also consider not to start at all. Josef is right, there's proably not much working without /proc. We could test for /proc in the startup script, and if it's missing print Josef's advice from comment #1 and exit. -- 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=450643 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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