Fixing “System has not been booted with systemd as init system” Error

So you are following some tutorial on the internet and you used systemd command like sudo systemctl start. .

To your surprise the command results in an error like this.

The reason is that you are trying to use systemd command to manage services on Linux but your system doesn8217t use systemd and most likely using the classic SysV init sysvinit system.

But how is that possible You are using Ubuntu and the tutorial is also for the same version of Ubuntu. How come is it not working for you.

If you are using Ubuntu inside Windows using WSL you will have SysV instead of systemd and your system will complain when you run the systemctl command intended for Linux systems with systemd init system.

How to know which init system you are using You may use this command to know the process name associated with PID 1 the first process that runs on your system.

...

Read Full Post

News Link: https://linuxhandbook.com/system-has-not-been-booted-with-systemd/.
RSS Link: https://linuxhandbook.com/feed/.

Linux Chatter is a news aggregator service that curates some of the best Linux, Cloud, Technical Guides, Hardware and Security news. We display just enough content from the original post to spark your interest. If you like the topic, then click on the 'read full post' button to visit the author's website. Use Linux Chatter to find content from amazing authors!

Note: The content provided has been modified and is not displayed as intended by the author. Any trademarks, copyrights and rights remain with the source.

Disclaimer: Linux Chatter sources content from RSS feeds and personal content submissions. The views and opinions expressed in these articles are those of the authors and do not necessarily reflect those of Linux Chatter.