[Bug 225605] New: Yast installer doesn't create all /dev entries before first reboot
https://bugzilla.novell.com/show_bug.cgi?id=225605 Summary: Yast installer doesn't create all /dev entries before first reboot Product: openSUSE 10.2 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: volker3204@paradise.net.nz QAContact: jsrain@novell.com When installing a system, yast doesn't create disk entries /dev/[hs]da* before the first reboot. If the reboot fails, e.g. because of a faulty boot loader installation, booting the rescue system and chroot into it gives trouble because the disks aren't there. Combined with other bugs (wrong boot loader config, yast module hang) this creates a bit of bother. See #225603 for yast logs, and for a real-world scenario when these missing /dev entries are a problem. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=225605 olh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Comment #1 from olh@novell.com 2006-12-02 05:02 MST ------- this is not a bug. device nodes for physical devices have no meaning. do a 'mount --bind /dev /mnt/dev' before the chroot. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=225605 ------- Comment #2 from volker3204@paradise.net.nz 2006-12-02 05:12 MST ------- I don't think I understand "have no meaning", considering that fdisk -l shows nothing and yast hangs itself by its own neck (#225603) when the nodes are absent. But the mount --bind is a good alternative to cp -a. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com