The officially official Devuan Forum!

You are not logged in.

#1 2024-01-05 17:48:53

Ermiq
Member
Registered: 2022-02-06
Posts: 8  

[Excalibur/Testing] sed is now in /usr/bin and it breaks runit boot.

After recent upgrade of sed package it is now installed in /usr/bin/sed instead of the /bin/sed and with runit-init it breaks the boot process at runit stage 1 because scripts in /etc/rcS.d/ fail to run due to sed: not found

I get this in boot process output:

- runit: enter stage: /etc/runit/1
/etc/rcS.d/S01mountkernfs.sh: 11: /lib/init/tmpfs.sh: sed: not found
/etc/rcS.d/S01mountkernfs.sh: 19: /lib/init/tmpfs.sh: sed: not found
...
/etc/rcS.d/S02eudev: 84: sed: not found
mkmod: missing operand after 'c!'
/etc/rcS.d/S03mountdevsubfs.sh: 11: /lib/init/tmpfs.sh: sed: not found
/etc/rcS.d/S03mountdevsubfs.sh: 19: /lib/init/tmpfs.sh: sed: not found
...
Setting up keyboard layout...done.
Starting boot logger: bootlogdActivating swap...done.
/etc/rcS.d/S01mountkernfs.sh: 11: /lib/init/tmpfs.sh: sed: not found
/etc/rcS.d/S01mountkernfs.sh: 19: /lib/init/tmpfs.sh: sed: not found
...

As a result everything is broken. X won't start due to no devices found and many other things don't work. 

I fixed it by symlinking sed to /bin/ with

ln -s /usr/bin/sed /bin/sed

Anyhow, I'm interested, is it a consequence of the ongoing "merged /usr" revolution? And is Devuan going to merge /usr in the end or will create workarounds for things like this?

Offline

#2 2024-01-05 17:52:08

steve_v
Member
Registered: 2018-01-11
Posts: 325  

Re: [Excalibur/Testing] sed is now in /usr/bin and it breaks runit boot.


Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.

Offline

Board footer