13.01.2018 16:07, Paul Neuwirth пишет:
On Sat, 13 Jan 2018 12:12:37 +0300 Andrei Borzenkov <arvidjaar@gmail.com> wrote:
13.01.2018 12:10, Paul Neuwirth пишет:
On Sat, 13 Jan 2018 11:24:19 +0300 Andrei Borzenkov <arvidjaar@gmail.com> wrote:
13.01.2018 10:57, Paul Neuwirth пишет:
Hello,
first, what seems to be a bug for me, installing a new bootloader, respectivly creating a new initrd using "yast bootloader" results in an initrd creation, which ignores my config I placed into /etc/dracut.conf.d/: # ls -l /etc/dracut.conf.d/ total 12 -rw-r--r-- 1 root root 22 22. Dez 14:13 02-early-microcode.conf -rw-r--r-- 1 root root 41 13. Jan 08:32 10-iscsi.conf -rw-r--r-- 1 root root 487 22. Dez 14:13 99-debug.conf drwxr-xr-x 1 root root 12 12. Jan 08:39 modules.d # cat /etc/dracut.conf.d/10-iscsi.conf add_dracutmodules+="debug network iscsi"
The correct syntax is
add_dracutmodules+=" debug network iscsi "
(note extra spaces around value) and it works using "mkinitrd" here.
fixed that.. but as mentioned, it works running the command manually..
Does it work when running mkinitrd?
that also worked.
YaST calls mkinitrd. It is very unlikely that it will fail if it works when called manually.
but config is not getting applied if it's called from yast bootloader.
YaST bootloader should not create any initrd at all.
the message "Create initrd" is misleading then.
2018-01-13 10:05:15 <1> alif(9203) [Ruby] modules/Progress.rb:344 Progress::New(Saving Boot Loader Configuration, 2, ["Create initrd", "Save boot loader configuration"])
Yes, initrd may be regenerated at this point, but should not on x86. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org