What are the semantics of --mount option
Hi Harald,
What are the semantics of --mount option. If I call dracut with --mount option, can I expect that resulting initramfs will mount that filesystem (including network file system) by the time pre-pivot hook of a module is called?
Thanks
Vivek
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am 25.04.2012 23:50, schrieb Vivek Goyal:
Quoted 6 lines
Hi Harald,
What are the semantics of --mount option. If I call dracut with --mount option, can I expect that resulting initramfs will mount that filesystem (including network file system) by the time pre-pivot hook of a module is called?
yes, but network setup has to be crafted on the kernel cmdline or in a /etc/cmdline.d/*.conf
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Harald Hoyer
Am 25.04.2012 23:50, schrieb Vivek Goyal:
Quoted 6 lines
Hi Harald,
What are the semantics of --mount option. If I call dracut with --mount option, can I expect that resulting initramfs will mount that filesystem (including network file system) by the time pre-pivot hook of a module is called?
yes, but network setup has to be crafted on the kernel cmdline or in a
/etc/cmdline.d/*.conf
This is interesting. General theme of dracut seems to be that for networking, iscsi etc, we will include relevant tools (binaries/config files etc) but will not store the specific configuration of target and expect the configuration either on command line (iscsiroot, netroot etc) or in /etc/cmdline.d/*.conf.
I am confused why that's the case. I mean I can understand this for generic initramfs. But for hostonly initramfs, don't we want to bring up all the devices encountered in root path by default? Why a user is supposed to specify specific iscsi, network configuration on the command line again. dracut has access to alll this information while traversing the device stack and should be able to store it in initramfs.
IOW, will it make sense that in hostonly mode, various modules also starting saving associated configuration of device (as needed) and by default try to bring up those devices on boot (in addition to honoring any command line options passed)?
Thanks
Vivek
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am 26.04.2012 13:40, schrieb Vivek Goyal:
Quoted 25 lines · Harald Hoyer
Quoted 10 lines
Am 25.04.2012 23:50, schrieb Vivek Goyal:
Quoted 6 lines
Hi Harald,
What are the semantics of --mount option. If I call dracut with --mount option, can I expect that resulting initramfs will mount that filesystem (including network file system) by the time pre-pivot hook of a module is called?
yes, but network setup has to be crafted on the kernel cmdline or in a
/etc/cmdline.d/*.confThis is interesting. General theme of dracut seems to be that for networking, iscsi etc, we will include relevant tools (binaries/config files etc) but will not store the specific configuration of target and expect the configuration either on command line (iscsiroot, netroot etc) or in
/etc/cmdline.d/*.conf.I am confused why that's the case. I mean I can understand this for generic initramfs. But for hostonly initramfs, don't we want to bring up all the devices encountered in root path by default? Why a user is supposed to specify specific iscsi, network configuration on the command line again. dracut has access to alll this information while traversing the device stack and should be able to store it in initramfs.
Quoted 7 lines
IOW, will it make sense that in hostonly mode, various modules also starting saving associated configuration of device (as needed) and by default try to bring up those devices on boot (in addition to honoring any command line options passed)?
Thanks
Vivek
Network setup and network devices have not yet been ported to host-only self-configuration.