- Reboot and select a rescue mode that was available in lilo.
Code: Select all
mount /boot mount -o remount,rw /dev/sda3 /- add to the default boot image in /etc/lilo.conf
Code: Select all
append="init=/lib/systemd/systemd" Code: Select all
lilo
Code: Select all
mount /boot
mount -o remount,rw /dev/sda3 /Code: Select all
append="init=/lib/systemd/systemd"Code: Select all
lilono initrd? is there not a symlink from a standard init path to that systemd init file?sigra wrote:Today I booted a new kernel version and it did not start the init system. It was not because of the new kernel version. To get into the system again, I had to:I don't know why this change was necessary. If you know, please let us know. If it happens to you too, the steps above might help.
- Reboot and select a rescue mode that was available in lilo.
Code: Select all
mount /boot mount -o remount,rw /dev/sda3 /- add
to the default boot image in /etc/lilo.confCode: Select all
append="init=/lib/systemd/systemd"Code: Select all
lilo
Code: Select all
sys-apps/systemd
Latest version available: 259.4-r1
Latest version installed: 259.4-r1

sigra wrote:There was a inittab file that was changed by something 2 days ago. It seems to be for openrc, not systemd. There is also the directory init.d and inittab.d.
That is a very strange mix of sysvinit + OpenRC and systemd... which shouldn't normally happen on Gentoo.sigra wrote:Code: Select all
sys-apps/systemd Latest version available: 259.4-r1 Latest version installed: 259.4-r1
Ionen wrote:As a packager I just don't want things to get messier with weird build systems and multiple toolchains requirements though

