Are we using systemd now?

[lcorken]

I noticed a package called systemd-shim was updated today and there is a folder /etc/systemd with stuff in it. Didn't see it in announcement for Kubuntu 14.10. Release notes only had a vague reference to systemd. I don't know how to tell otherwise.

Ken.

[Feathers McGraw]

I think so, because if you do:

man init

You get a manpage for systemd. Not certain though.

[OneLine]

http://irclogs.ubuntu.com/2014/10/29...el.html#t11:48

BluesKaj a user wants to remove systemd from 14.10 is this possible without breakage? 11:48
Riddell um, it's not in 14.10 11:49
Riddell but the bits of systemd which are in will be used so they'd be very much on their own 11:49
shadeslayer BluesKaj: why? 11:50
BluesKaj yeah, I know the boot section isn't enabled unless set up manually in grub and it's used by udev otherwise 11:53
BluesKaj shadeslayer, a user was asking in $kubuntu 11:53
BluesKaj err #kubuntu 11:54
...

http://irclogs.ubuntu.com/2014/10/29...tu.html#t11:40

kolp hi, how do I update from 14.04 to 14.10 without installing systemd? 11:40
BluesKaj Hi folks 11:40
BluesKaj kolp, systemd will install, but won't be used unless you set it up in grub 11:47
kolp BluesKaj: why is it installed then? 11:49
BluesKaj not my decision, that's canonical's 11:49
kolp BluesKaj: right, thanks for the info 11:50
lordievader kolp: In 14.10 systemd is only used by udev. 11:50
kolp so 14.10 on't work without systemd? 11:51
shadeslayer kolp: I do believe its installed so that people who want to try it out can do so easily 11:51
kolp I thought that's what repositories are for 11:51
...

How can I replace upstart with systemd?: http://askubuntu.com/questions/42091...t-with-systemd

[GreyGeek]

I think so, because if you do:

man init

You get a manpage for systemd. Not certain though.

When I run man init I get:

init(8) System Manager's Manual init(8)

NAME
init - Upstart process management daemon

But, I have systemd-logind, systemd-udevd and systemd-shim running in my processes under root. At least my updated version of 14.04 appears to be a hybrid between Upstart and a little systemd.

[NoWorries]

I am on Utopic and muon gives:



So like GG, systemd is alive and well and I understand that it helps with a fast boot time.

[kubicle]

On Utopic, /sbin/init still links to upstart by default (installing systemd-sysv package will change it to systemd...note that there might still be issues with systemd on *buntus).

But Greygeek is right in that some parts of systemd are already used.

systemd will likely be the default init system in 15.04.

[ronw]

FWIW - I installed systemd-sysv per the askubuntu article linked in post #3 on my Vivid virtualbox.

It wanted to remove upstart, and whoopsie, which I allowed it to do. On reboot, it stalled at the the plymouth splash screen. I went to tty1 and reinstalled upstart, which removed systemd-sysv, and all was good on reboot. Not enough free time to look into where it stalled with systemd-sysv installed.

[lcorken]

Thanks guys. Just curious.

Sounds like some sort of a bastardized morphodite of a hybrid at this point. Baby steps? Whatever, it seems to work fine for my desktop unit, so far.

Man init does show systemd here (14.10 upgraded from 14.04).

Ken.

[bendy]

Well Debian is going with systemd (albeit not a universally popular decision) so I'm sure it is inevitable for Ubuntu too. It would be a lot of extra work for Canonical to maintain a different init system to the Debian default.

[GreyGeek]

I could be wrong but I believe that Debian will default to Systemd but allow you to install sysv instead.

[SteveRiley]

While Utopic includes a number of systemd elements, PID 1 (the system's init process is always PID 1) is still Upstart:

steve@t520:~$ [B]ps -p 1[/B]
  PID TTY          TIME CMD
    1 ?        00:00:01 init

steve@t520:~$ [B]which init[/B]
/sbin/init

steve@t520:~$ [B]ll /sbin/init[/B]
lrwxrwxrwx 1 root root 7 Sep 30 01:26 /sbin/init -> upstart*

[GreyGeek]

But Trusty (14.04) does not:

jerry@jerry-Aspire-V3-771:~$ ps -p 1
  PID TTY          TIME CMD
    1 ?        00:00:02 init
jerry@jerry-Aspire-V3-771:~$ which init
/sbin/init
jerry@jerry-Aspire-V3-771:~$ ll /sbin/init
-rwxr-xr-x 1 root root 265848 Jul 18 04:46 /sbin/init*
jerry@jerry-Aspire-V3-771:~$ whereis upstart
upstart: /usr/lib/upstart /usr/share/upstart /usr/share/man/man7/upstart.7.gz
jerry@jerry-Aspire-V3-771:~$ ll /usr/lib/upstart
total 4
drwxr-xr-x 1 root root    36 Jul 23 11:06 ./
drwxr-xr-x 1 root root 45700 Nov 19 21:41 ../
-rwxr-xr-x 1 root root  3412 Jul 18 04:42 migrate-inittab.pl*

initd is an ELF executable.

[kubicle]

But Trusty (14.04) does not:

jerry@jerry-Aspire-V3-771:~$ ps -p 1
  PID TTY          TIME CMD
    1 ?        00:00:02 init
jerry@jerry-Aspire-V3-771:~$ which init
/sbin/init
jerry@jerry-Aspire-V3-771:~$ ll /sbin/init
-rwxr-xr-x 1 root root 265848 Jul 18 04:46 /sbin/init*
jerry@jerry-Aspire-V3-771:~$ whereis upstart
upstart: /usr/lib/upstart /usr/share/upstart /usr/share/man/man7/upstart.7.gz
jerry@jerry-Aspire-V3-771:~$ ll /usr/lib/upstart
total 4
drwxr-xr-x 1 root root    36 Jul 23 11:06 ./
drwxr-xr-x 1 root root 45700 Nov 19 21:41 ../
-rwxr-xr-x 1 root root  3412 Jul 18 04:42 migrate-inittab.pl*

initd is an ELF executable.

On Trusty /sbin/init is upstart (there is no symlinking, upstart package just installs it's [upstart version] of /sbin/init)

[GreyGeek]

On Trusty /sbin/init is upstart (there is no symlinking, upstart package just installs it's [upstart version] of /sbin/init)

Ah, so it is. I looked at it with Oketa and found 5 occurrences of "upstart" related to significant actions.