Hi All,
When we switch to dracut we will need to specify certain kernel commandline options to dracut. For example when / is on iscsi dracut will need information for configuring the nic and about the iscsi target present on the kernel cmdline.
The easiest way to handle this would be to add a new attribute to all devices which returns a list of kernel cmdline options to add to bring up that device (which will be empty in most cases).
The problem here is that we can need (for example) multiple iscsi disks, and the question then becomes how to merge the cmdlines returned from the various devices.
Harald I've included you in the CC, because I think this is something which dracut cannot handle at all atm. The parameters like iscsi_target_name, etc. All only take one value AFAIK, but what then if we need to bring up 2 different iscsi targets, for example for doing a mirror on 2 different iscsi disks ?
I'm thinking that it would be better to have an iscsi= option, which will then contain the rootdev= iscsi syntax from dhcp (so all info for one target in one string) and allow having this option multiple times, does that sound like a plan ?
Regards,
Hans
On Tuesday, June 30 2009, Hans de Goede said:
When we switch to dracut we will need to specify certain kernel commandline options to dracut. For example when / is on iscsi dracut will need information for configuring the nic and about the iscsi target present on the kernel cmdline.
How are we going to have password type information? /proc/cmdline is readable by anyone, so we don't necessarily want them there :)
The easiest way to handle this would be to add a new attribute to all devices which returns a list of kernel cmdline options to add to bring up that device (which will be empty in most cases).
Maybe instead of having it be empty in most cases, it should even be responsible for root= ? Then it'd get tested all the time :-)
Jeremy
On 07/01/2009 12:23 AM, Jeremy Katz wrote:
On Tuesday, June 30 2009, Hans de Goede said:
When we switch to dracut we will need to specify certain kernel commandline options to dracut. For example when / is on iscsi dracut will need information for configuring the nic and about the iscsi target present on the kernel cmdline.
How are we going to have password type information? /proc/cmdline is readable by anyone, so we don't necessarily want them there :)
You can either generate your own dracut initrd or inject config files in the generic dracut initrd with cpio. Though the parser to create config files from the current host state has not yet been written.
The easiest way to handle this would be to add a new attribute to all devices which returns a list of kernel cmdline options to add to bring up that device (which will be empty in most cases).
Maybe instead of having it be empty in most cases, it should even be responsible for root= ? Then it'd get tested all the time :-)
Jeremy
On Wednesday, July 01 2009, Harald Hoyer said:
On 07/01/2009 12:23 AM, Jeremy Katz wrote:
On Tuesday, June 30 2009, Hans de Goede said:
When we switch to dracut we will need to specify certain kernel commandline options to dracut. For example when / is on iscsi dracut will need information for configuring the nic and about the iscsi target present on the kernel cmdline.
How are we going to have password type information? /proc/cmdline is readable by anyone, so we don't necessarily want them there :)
You can either generate your own dracut initrd or inject config files in the generic dracut initrd with cpio. Though the parser to create config files from the current host state has not yet been written.
I wonder if a good way to go here is actually to use a second cpio.gz with any non-version-dependent and host-specific data like iscsi passwords. They then just get exploded and dracut doesn't (necessarily) need to know that it's two actual initramfs files and it keeps anaconda (eg) from having to regen the initramfs itself
Jeremy
On 07/01/2009 03:43 PM, Jeremy Katz wrote:
On Wednesday, July 01 2009, Harald Hoyer said:
On 07/01/2009 12:23 AM, Jeremy Katz wrote:
On Tuesday, June 30 2009, Hans de Goede said:
When we switch to dracut we will need to specify certain kernel commandline options to dracut. For example when / is on iscsi dracut will need information for configuring the nic and about the iscsi target present on the kernel cmdline.
How are we going to have password type information? /proc/cmdline is readable by anyone, so we don't necessarily want them there :)
You can either generate your own dracut initrd or inject config files in the generic dracut initrd with cpio. Though the parser to create config files from the current host state has not yet been written.
I wonder if a good way to go here is actually to use a second cpio.gz with any non-version-dependent and host-specific data like iscsi passwords. They then just get exploded and dracut doesn't (necessarily) need to know that it's two actual initramfs files and it keeps anaconda (eg) from having to regen the initramfs itself
Jeremy
or, as Hans found out:
# chmod 0400 /proc/cmdline
anaconda-devel@lists.fedoraproject.org
-
Hans de Goede -
Harald Hoyer -
Jeremy Katz -
Jon Masters