Mailinglist Archive: opensuse-bugs (4664 mails)

< Previous Next >
[Bug 533782] after changing filesystem label system doesn't boot
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 4 Feb 2010 16:03:33 +0000
  • Message-id: <20100204160333.758A0CC7CD@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=533782

http://bugzilla.novell.com/show_bug.cgi?id=533782#c1


Jozef Uhliarik <juhliarik@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P3 - Medium
Status|NEW |ASSIGNED

--- Comment #1 from Jozef Uhliarik <juhliarik@xxxxxxxxxx> 2010-02-04 16:03:32
UTC ---
During installation yast2-bootloader uses kernel device names and device names
are finally convert (during writting) to persistent device names. You have no
change to see your changes.

yast2-bootloader during installation checks Storage::GetTargetChangeTime() and
if the time is changed it tries to change proposal of bootloader. Usually it
leads to complete new proposal of bootloader settings. If there are some
troubles with changes of bootloader settings there is some pop-message which
inform user about manual checking of bootloader settings but it is not about
using persistent device names.

next changes of mount-by on installed system has not effect to bootloader
settings. It is necessary to run yast2-bootloader after changes in disk
configuration manually. IMHO it is OK.

After running of yast2-bootloader all device names are converted to actual
persistent device names instead of option resume.

--
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.

< Previous Next >