initscripts package on Debian

xenomorph3613 · 08-07-2020, 09:03 PM

Over the years I became accustomed to shutting down my Linux PC simple using the command

Code:

init 0

from a terminal I had open as root. I guess I got lazy but I found that command alone was awesome instead of a GUI click here then there then confirmation dialog in most desktop environments.

Anyway it was always a command in place, out of the box on any distro I ever used. Well recently using Debian buster post installation running that same command gives the bash response

Code:

command not found

.

I believe it then requires the install of the package
initscripts to become a command to use again, but do I need to do any configuration to get the init command functional again. For whatever reason on Debian is like this. Ubuntu, Fedora and others still have it in the command lists as usual. So I just need to know how to implement it in debian after I install it. Anyone know?

mrmazda · 08-07-2020, 09:14 PM

Code:

# inxi -Sx
System:    Host: big31 Kernel: 4.19.0-10-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Trinity R14.0.8
           Distro: Debian GNU/Linux 10 (buster)
# which init
/sbin/init
# ll /sbin/init
lrwxrwxrwx 1 root root 20 Apr 27 13:02 /sbin/init -> /lib/systemd/systemd

Apparently your symlink is missing.

xenomorph3613 · 08-07-2020, 09:21 PM

mrmazda

Thank you for your reply. That seems a simple fix. I will look into this later on my Linux box and see what I see then. Again, much obliged for the info.

HappyTux · 08-07-2020, 10:28 PM

Quote:

Originally Posted by xenomorph3613

Over the years I became accustomed to shutting down my Linux PC simple using the command

Code:

init 0

from a terminal I had open as root. I guess I got lazy but I found that command alone was awesome instead of a GUI click here then there then confirmation dialog in most desktop environments.

Anyway it was always a command in place, out of the box on any distro I ever used. Well recently using Debian buster post installation running that same command gives the bash response

Code:

command not found

.

I believe it then requires the install of the package
initscripts to become a command to use again, but do I need to do any configuration to get the init command functional again. For whatever reason on Debian is like this. Ubuntu, Fedora and others still have it in the command lists as usual. So I just need to know how to implement it in debian after I install it. Anyone know?

I was used to using the halt command, Debian in its wisdom has adopted the systemd method now. Those commands that have been used by the init system were removed in the interest of helping users with their freedom and having it just work. I have made new arrangements.

Code:

root@haswell:~# alias halt
alias halt='systemctl poweroff'
root@haswell:~# alias reboot
alias reboot='systemctl reboot'
root@haswell:~# cat /etc/debian_version 
10.5

Of course the halt was an alias for or link to script containing (not sure which one) shutdown -h now and reboot the shutdown -r now commands. Still I was rather gagged having to search google to find out how to shutdown or reboot my machine upon upgrading to Buster.