On 10.09.2014 10:28, P J P wrote:
Hi,
> On Wednesday, 10 September 2014 12:28 PM, poma wrote:
> dr. acut?
Can't say for sure. I added "rdshell rd.debug" parameters to the boot
command line, again it throws a long list of debug messages from - /lib/dracut-lib.sh@xxx.
Messages are about trying to setup /etc/sysconfig/network-scripts and dhclient(8)
configurations it seems. It has snippets like
for f in '"/$_dir"/*.sh'
'[' -e //lib/dracut/hooks/cleanup/10-kill-dhclient.sh ']'
. //lib/dracut/hooks/cleanup/10-kill-dhclient.sh
for f in '/tmp/dhclient.*.pid'
'[' -e '/tmp/dhclient.*.pid ' ']'
continue
...
/bin/dracut-pre-pivot@29(): exit 0
systemd-journald[2842]: Received SIGTERM
systemd-journal (2842) used greatest stack depth: 12920 bytes left
Note:- Systemd(1)/dracut(8) debug logs are serious information overload. They zoom past
through the screen inundating it with thousands of lines, you can not even see them all.
What's the point?
Anyway...any clue?
Depending on what is installed and what is actually used,
$ ls /usr/lib/dracut/modules.d/
$ man 1 lsinitrd
try exclude certain modules e.g.
/etc/dracut.conf.d/omit_dracut-modules.conf
#
# SEE man dracut.conf(5)
#
# turn off modules
omit_dracutmodules+=" <module1> <module2> ... e.g. <systemd>
"
# dracut [--verbose --force --kver <kernel version>]
$ man 8 dracut
poma