[opensuse-factory] what happened to /etc/sysconfig/kernel ?
was it replaced by some other config? -- Per Jessen, Zürich (15.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2014-10-03 19:45, Per Jessen wrote:
was it replaced by some other config?
/etc/modules-load.d/ for MODULES_LOADED_ON_BOOT. Dunno where KMS_NO_INITRD went. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 03/10/14 a las #4, Jan Engelhardt escribió:
Dunno where KMS_NO_INITRD went.
blacklisting the video driver will exclude them from the initrd. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt wrote:
On Friday 2014-10-03 19:45, Per Jessen wrote:
was it replaced by some other config?
/etc/modules-load.d/ for MODULES_LOADED_ON_BOOT. Dunno where KMS_NO_INITRD went.
I was looking for INITRD_MODULES. -- Per Jessen, Zürich (14.2°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 03/10/14 a las #4, Per Jessen escribió:
Jan Engelhardt wrote:
On Friday 2014-10-03 19:45, Per Jessen wrote:
was it replaced by some other config?
/etc/modules-load.d/ for MODULES_LOADED_ON_BOOT. Dunno where KMS_NO_INITRD went.
I was looking for INITRD_MODULES.
What module is failing to be detected automatically as needed ? -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Cristian Rodríguez wrote:
El 03/10/14 a las #4, Per Jessen escribió:
Jan Engelhardt wrote:
On Friday 2014-10-03 19:45, Per Jessen wrote:
was it replaced by some other config? /etc/modules-load.d/ for MODULES_LOADED_ON_BOOT. Dunno where KMS_NO_INITRD went. I was looking for INITRD_MODULES.
What module is failing to be detected automatically as needed ?
Probably nothing, I just just always check INITRD_MODULES before rebuilding the initrd. /Per -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 03.10.2014 um 21:03 schrieb Cristian Rodríguez:
What module is failing to be detected automatically as needed ?
All xen pv guest modules for example. I'm preparing initrds for PV VMs on the dom0 (chrooted into the to-be-installed rootfs), so being able to select the modules in initrd is helpful. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 04/10/14 a las #4, Stefan Seyfried escribió:
Am 03.10.2014 um 21:03 schrieb Cristian Rodríguez:
What module is failing to be detected automatically as needed ?
All xen pv guest modules for example.
That sounds like a bug. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 03/10/14 a las #4, Per Jessen escribió:
was it replaced by some other config?
/etc/sysconfig/kernel was owned by mkinitrd.. but that was replaced by dracut..I 'm not sure that change is intentional.. In any case if you ever need the functionality that file provided, one step is required: - Fill a bug report, the need of that configuration file is a bug in itself. if you really need INITRD_MODULES with dracut, use add_drivers+=" <kernel module> " in /etc/dracut.conf.d as a drop-in file. example /etc/dracut.conf.d/mymodules.conf Note that 99.9% of the time..needing any such thing is a bug that needs fixing. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 03/10/14 a las #4, Cristian Rodríguez escribió: le /etc/dracut.conf.d/mymodules.conf
Note that 99.9% of the time..needing any such thing is a bug that needs fixing.
Also, this file, if exists *IS STILL PARSED* and honoured by mkinitrd so it does not break old setups. however it is not created in new installs. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Cristian Rodríguez wrote:
El 03/10/14 a las #4, Cristian Rodríguez escribió: le /etc/dracut.conf.d/mymodules.conf
Note that 99.9% of the time..needing any such thing is a bug that needs fixing.
Also, this file, if exists *IS STILL PARSED* and honoured by mkinitrd so it does not break old setups. however it is not created in new installs.
Thanks for the explanation. I still have to get used to using dracut. Previously, ISTR always having to amend INITRD_MODULES with the drivers for the disk-controller plus the root file-system. (often filled in automagically by yast/someone). As an aside, do we have a migration guide mkinitrd->dracut ? A lot of the mkinitrd stuff is hard-wired into my fingers :-( -- Per Jessen, Zürich (14.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 03/10/14 a las #4, Per Jessen escribió:
Thanks for the explanation. I still have to get used to using dracut.
Previously, ISTR always having to amend INITRD_MODULES with the drivers for the disk-controller plus the root file-system. (often filled in automagically by yast/someone).
Ahh.. that's what this is about then.. if this still occurs, it is a bug!
As an aside, do we have a migration guide mkinitrd->dracut ? A lot of the mkinitrd stuff is hard-wired into my fingers :-(
mkinitrd continue to work as usual, you do not need to change your workflow unless you want to use dracut specific features, for that refer to https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Cristian Rodríguez -
Jan Engelhardt -
Per Jessen -
Stefan Seyfried