On Thu, Apr 26, 2012 at 12:01:19PM +0200, Harald Hoyer wrote: > Am 25.04.2012 23:50, schrieb Vivek Goyal: > > 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 -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
