[opensuse] No /etc/sysconfig/kernel installed in 13.2. Where did those settings go?
I just installed openSUSE 13.2 Reading posts & docs I find out that adding modules to be loaded on boot to the initrd used to be done with a MODULES_LOADED_ON_BOOT= line in /etc/sysconfig/kernel. The docs at https://activedoc.opensuse.org/book/opensuse-reference/chapter-7-booting-a-l... says that's still true. On this brand new 13.2 install that file, /etc/sysconfig/kernel, does not exist. This post, http://comments.gmane.org/gmane.linux.suse.opensuse.devel/59708, suggests that it's no longer used since 13.1 but instead you use /etc/modules-load.d/MODULES_LOADED_ON_BOOT. Which is correct? In addition to MODULES_LOADED_ON_BOOT=, /etc/sysconfig/kernel contained INITRD_MODULES= DOMU_INITRD_MODULES= ACPI_DSDT= SKIP_RUNNING_KERNEL= NO_KMS_IN_INITRD= Where are those setting managed now? Which are the uptodate docs for setting these params? LT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/25/2015 11:53 AM, lyndat3@your-mail.com wrote:
Where are those setting managed now?
RTFM/Release notes DRAKUT has replaced mkinitrd which used that file. https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracutconf5 I'm curious: has anyone back-ported this to 13.1? How well does it tun there? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
DRAKUT has replaced mkinitrd which used that file.
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracutconf5
RTFM? That didn't take long. I did "RTFM", thanks. The apparently official & current docs at https://activedoc.opensuse.org/book/opensuse-reference/chapter-7-booting-a-l... So the openSUSE docs and that developer post are wrong, and we're supposed to use the dracut.conf file now instead of either the /etc/sysconfig/kernel or /etc/modules-load.d/* files? LT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On March 25, 2015 9:26:52 AM MST, lyndat3@your-mail.com wrote:
DRAKUT has replaced mkinitrd which used that file.
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracutconf5
RTFM? That didn't take long.
I did "RTFM", thanks. The apparently official & current docs at
https://activedoc.opensuse.org/book/opensuse-reference/chapter-7-booting-a-l...
So the openSUSE docs and that developer post are wrong, and we're supposed to use the dracut.conf file now instead of either the /etc/sysconfig/kernel or /etc/modules-load.d/* files?
LT
You just have to learn that official docs trail by two releases, and read me files and release notes always supercede docs. Sad, but not totally unusual. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Mar 25, 2015, at 09:34 AM, John Andersen wrote:
You just have to learn that official docs trail by two releases, and read me files and release notes always supercede docs. Sad, but not totally unusual.
And not at all obvious. The docs refer to both 12.3 and an 'unlabeled' release, and the release notes https://doc.opensuse.org/release-notes/x86_64/openSUSE/13.2/ make no mention of either dracut or mkinitrd. Thanks for pointing it out. It's appreciated. LT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
dracut.conf contains settings for defining, adding or omitting kernel modules from the initrd, dracutmodules+= add_dracutmodules+= omit_dracutmodules+= there's no mention of either of DOMU_INITRD_MODULES= MODULES_LOADED_ON_BOOT= both previously inclued in /etc/sysconfig/kernel the former defines modules to be added only to a kernel-xen instance's initrd the latter defined those modules to be manually loaded at bootup. MODULES_LOADED_ON_BOOT subsequently migrated, http://lists.opensuse.org/opensuse-bugs/2013-09/msg00192.html, to /etc/modules.load.d/MODULES_LOADED_ON_BOOT the original 'response' to my post specifically asking about those oaraneters suggest that dracut.conf now is to be used. where are these two parameters, or their new equivalents, documented for use in dracut? LT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lyndat3@your-mail.com composed on 2015-03-25 11:12 (UTC-0700):
dracut.conf contains settings for defining, adding or omitting kernel modules from the initrd,
dracutmodules+= add_dracutmodules+= omit_dracutmodules+=
there's no mention of either of
DOMU_INITRD_MODULES= MODULES_LOADED_ON_BOOT=
both previously inclued in /etc/sysconfig/kernel
the former defines modules to be added only to a kernel-xen instance's initrd
the latter defined those modules to be manually loaded at bootup.
MODULES_LOADED_ON_BOOT subsequently migrated, http://lists.opensuse.org/opensuse-bugs/2013-09/msg00192.html, to
/etc/modules.load.d/MODULES_LOADED_ON_BOOT
the original 'response' to my post specifically asking about those oaraneters suggest that dracut.conf now is to be used.
where are these two parameters, or their new equivalents, documented for use in dracut?
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracutconf5 explains what to do instead. It's more confusing (aka complicated) but arguably more powerful now using /etc/dracut.conf and/or /etc/dracut.conf.d/: drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to exclusively include in the initramfs. The kernel modules have to be specified without the ".ko" suffix. add_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix. force_drivers+=" <list of kernel modules> " See add_drivers above. But in this case it is ensured that the drivers are tried to be loaded early via modprobe. omit_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules not to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix. I've typically been adding something like 'omit_drivers+="i18n uefi-lib iscsi lvm lvm2 dmraid plymouth resume sata_sil usb_storage "' to dracut.conf on most of my installations since last year some time to reduce initrd size and reduce opportunity for inconsistent resource allocation among multiboot installations and between boot invocations. How valid any particular any of my choices have been are hard to determine, but that's the tradition of documentation trailing behind software evolution. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Even old timers don't expect to have to chase opensuse documentation to kernel.org. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
where are these two parameters, or their new equivalents, documented for use in dracut?
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracutconf5 explains what to do instead. It's more confusing (aka complicated) but arguably more powerful now using /etc/dracut.conf and/or /etc/dracut.conf.d/:
drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to exclusively include in the initramfs. The kernel modules have to be specified without the ".ko" suffix.
add_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix.
force_drivers+=" <list of kernel modules> " See add_drivers above. But in this case it is ensured that the drivers are tried to be loaded early via modprobe.
omit_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules not to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix.
I've typically been adding something like 'omit_drivers+="i18n uefi-lib iscsi lvm lvm2 dmraid plymouth resume sata_sil usb_storage "' to dracut.conf on most of my installations since last year some time to reduce initrd size and reduce opportunity for inconsistent resource allocation among multiboot installations and between boot invocations. How valid any particular any of my choices have been are hard to determine, but that's the tradition of documentation trailing behind software evolution.
None of those address either of the two parameters I specifically asked about, DOMU_INITRD_MODULES= MODULES_LOADED_ON_BOOT= -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 25 Mar 2015 21:03, lyndat3@your-mail.com
where are these two parameters, or their new equivalents, documented for use in dracut?
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracutconf5 explains what to do instead. It's more confusing (aka complicated) but arguably more powerful now using /etc/dracut.conf and/or /etc/dracut.conf.d/:
drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to exclusively include in the initramfs. The kernel modules have to be specified without the ".ko" suffix.
add_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix.
force_drivers+=" <list of kernel modules> " See add_drivers above. But in this case it is ensured that the drivers are tried to be loaded early via modprobe.
omit_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules not to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix.
I've typically been adding something like 'omit_drivers+="i18n uefi-lib iscsi lvm lvm2 dmraid plymouth resume sata_sil usb_storage "' to dracut.conf on most of my installations since last year some time to reduce initrd size and reduce opportunity for inconsistent resource allocation among multiboot installations and between boot invocations. How valid any particular any of my choices have been are hard to determine, but that's the tradition of documentation trailing behind software evolution.
None of those address either of the two parameters I specifically asked about,
DOMU_INITRD_MODULES= MODULES_LOADED_ON_BOOT=
Bzzzzz! Read carefully! One has been answered. "MODULES_LOADED_ON_BOOT=" has its eqiv. in "force_drivers+=" DOMU_xxxx is a xen speciality that I know nothing about at all. Still, as openSUSE user I would expect the docu to the relevant initramfs stuff at openSUSE, SUSE, or Novel and not "out there". And, I have not found a sufficent entry for "modul-loading with darcut" in the release notes, nor a hint to search kernel.org for it. - Yamaban, who goes off to cleanup his initramfs ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Bzzzzz! Read carefully! One has been answered.
The dracut.conf man page states force_drivers+=" <list of kernel modules> " See add_drivers above. But in this case it is ensured that the drivers are tried to be loaded early via modprobe. Referring to add_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to add to the initramfs. The kernel modules have to be specified without the ".ko" suffix. That former clearly refers to the latter, which states that the modules are added to the initramfs. It's unlcear whether the referenced modprobe is exec'd from the initrd or not. As documented at http://www.freedesktop.org/software/systemd/man/modules-load.d.html MODULES_LOADED_ON_BOOT initrd systemd-modules-load.service(8) reads files from the above directories which contain kernel modules to load during boot in a static list. the modules listed therein are NOT added to the initrd, but are loaded by systemd, from disk, at system boot. They are not equivalent. The question remains. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata composed on 2015-03-25 15:55 (UTC-0400):
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracutconf5 ... drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to exclusively include in the initramfs....
lyndat3@your-mail.com composed on 2015-03-25 13:39 (UTC-0700):
The dracut.conf man page states
Which dracut.conf man page? I'd have to guess that on kernel.org to be the more likely newer than any found elsewhere on the Internet. Looking at docs included in an installed system is no guarantee of latest or even applicable info either if the docs as too often happens are lagging the installed reality.
add_drivers+=" <kernel modules> " Specify a space-separated list of kernel modules to add to the initramfs....
That former clearly refers to the latter, which states that the modules are added to the initramfs. It's unlcear whether the referenced modprobe is exec'd from the initrd or not.
If you compare the man page I provided upthread to that you quoted you might see otherwise. Why would drivers be ***exclusively*** included in the initramfs if the expectation wasn't to load them from it?
The question remains.
Asking on the opensuse-kernel list or initramfs@vger.kernel.org or searching their archives might generate a more definitive answer than of this general purpose list. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
The dracut.conf man page states
Which dracut.conf man page?
https://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html#dracutconf5 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Mar 25, 2015 at 11:03 PM,
None of those address either of the two parameters I specifically asked about,
DOMU_INITRD_MODULES= MODULES_LOADED_ON_BOOT=
mkinitrd shim shipped with dracut in 13.2 still interprets DOMU_INITRD_MODULES. I do not know what MODULES_LOADED_ON_BOOT does, it is not present in default /etc/sysconfig/kernel shipped with 13.1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Anton Aylward -
Felix Miata -
John Andersen -
lyndat3＠your-mail.com -
Yamaban