diff for duplicates of <4A5F0752.1020400@redhat.com> diff --git a/a/1.txt b/N1/1.txt index ea40eae..1424430 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -43,7 +43,7 @@ On 07/14/2009 05:00 PM, David Zeuthen wrote: > > 1. when generating the initramfs image, we leave information in > the kernel command-line about the root filesystem - typically -> the UUID - e.g. root=UUID=786263c4-5e28-4cdc-97b8-1ab6e221c344 +> the UUID - e.g. root=UUIDx6263c4-5e28-4cdc-97b8-1ab6e221c344 > > 2. when the initramfs starts, we trigger all uevents and wait for > things to settle @@ -73,9 +73,9 @@ On 07/14/2009 05:00 PM, David Zeuthen wrote: > the rootfs. So the kernel command-line wouldn't really be "just" the > UUID of rootfs; it would be a whole recipe of actions to do. E.g. > -> ROOTFS=UUID=1234 \ # this the UUID of my rootfs -> MD_ASSEMBLE=UUID=4567 \ # assemble MD array with UUID 4567 -> LUKS_UNLOCK=UUID=89ab # unlock LUKS device with UUID 89ab +> ROOTFS=UUID\x1234 \ # this the UUID of my rootfs +> MD_ASSEMBLE=UUIDE67 \ # assemble MD array with UUID 4567 +> LUKS_UNLOCK=UUID‰ab # unlock LUKS device with UUID 89ab > > which would work for e.g. cases where rootfs is on a LUKS device which > is on a MD array. In other words, we'd need a whole "recipe" passed to diff --git a/a/content_digest b/N1/content_digest index 7bebee4..47261cf 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,7 +5,7 @@ "ref\01247583632.1991.39.camel@localhost.localdomain\0" "From\0Harald Hoyer <harald@redhat.com>\0" "Subject\0Re: RFC: mdadm and bringing up raid sets from initrd (dracut)\0" - "Date\0Thu, 16 Jul 2009 12:56:18 +0200\0" + "Date\0Thu, 16 Jul 2009 10:56:18 +0000\0" "To\0David Zeuthen <david@fubar.dk>\0" "Cc\0Doug Ledford <dledford@redhat.com>" Hans de Goede <hdegoede@redhat.com> @@ -60,7 +60,7 @@ ">\n" "> 1. when generating the initramfs image, we leave information in\n" "> the kernel command-line about the root filesystem - typically\n" - "> the UUID - e.g. root=UUID=786263c4-5e28-4cdc-97b8-1ab6e221c344\n" + "> the UUID - e.g. root=UUIDx6263c4-5e28-4cdc-97b8-1ab6e221c344\n" ">\n" "> 2. when the initramfs starts, we trigger all uevents and wait for\n" "> things to settle\n" @@ -90,9 +90,9 @@ "> the rootfs. So the kernel command-line wouldn't really be \"just\" the\n" "> UUID of rootfs; it would be a whole recipe of actions to do. E.g.\n" ">\n" - "> ROOTFS=UUID=1234 \\ # this the UUID of my rootfs\n" - "> MD_ASSEMBLE=UUID=4567 \\ # assemble MD array with UUID 4567\n" - "> LUKS_UNLOCK=UUID=89ab # unlock LUKS device with UUID 89ab\n" + "> ROOTFS=UUID\02234 \\ # this the UUID of my rootfs\n" + "> MD_ASSEMBLE=UUIDE67 \\ # assemble MD array with UUID 4567\n" + "> LUKS_UNLOCK=UUID\342\200\260ab # unlock LUKS device with UUID 89ab\n" ">\n" "> which would work for e.g. cases where rootfs is on a LUKS device which\n" "> is on a MD array. In other words, we'd need a whole \"recipe\" passed to\n" @@ -167,4 +167,4 @@ " rd_DM_UUID=<dmraid uuid>\n" only activate the raid sets with the given UUID -4598f377d2a98e095e72bcbe88d119afaee057f189b6dc6dd5158e89601e3944 +12a91af65287c2bd77614ae670be29971b91c125fcb7f8054e65da072b9646ac
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.