Re: We need to start thinking about writing kernel cmdline options to grub.conf for dracut

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux