Hi, On 12/23/2009 06:39 PM, David Lehman wrote:
On Tue, 2009-12-22 at 21:43 +0100, Hans de Goede wrote:We want to move to using dracut in such a way that the initrd only activates the minimum of storage needed to bring up the root fs. This requires us to tell it exactly what storage to activate. --- storage/devices.py | 14 ++++++++++++++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git a/storage/devices.py b/storage/devices.py index 1065a68..b71b669 100644 --- a/storage/devices.py +++ b/storage/devices.py @@ -1555,6 +1555,9 @@ class LUKSDevice(DMCryptDevice): """ This device's backing device. """ return self.parents[0] + def dracutSetupString(self): + return "rd_LUKS_UUID=luks-%s" % self.format.uuidrd_LUKS_UUID wants something formatted like "luks-$UUID" instead of the actual UUID?
It can take both (either one), but the udev rules actually passes in "luks-$UUID" to the script which checks this cmdline option, so I thought it was best to be consistent with that.
" @@ -2786,6 +2796,10 @@ class DMRaidArrayDevice(DMDevice): # Even if teared down we still want to show up in storage.disks return True + def dracutSetupString(self): + return "rd_DM_UUID=%s" % self.nameAgain, rd_DM_UUID does not want a UUID? Brilliant naming if so.
Yes it wants the raid set name, I agree about brilliant naming, although technically dmraid sets do not have a uuid in the xxxx-xxxx-xxxx-etc name and there name is unique, so the name is a unique ID. Regards, Hans _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
