Wednesday 13 December 2017

Re: Detecting the init system in use

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdsbkdwQr/phcwiC9nAiiVUQvr/AFAloxbY8ACgkQnAiiVUQv
r/Az9RAAwtNnxoTDVeh5cX4eSQCyZeNcoldVqKZceiPlXeyPkWJi24L/1n6nz1fh
hKzn0qZEcKuRFyNRfQCLRaL+MR6o4DDPyxsS9bFdu1OoPbJorKE8I8dcBasII9ms
UXZI8+w51QXr+e7xBU8OY3bsfVtsXIaT3s6IZarS327knPBWsJcfEmqkDgwPeMBW
jCJmeu5wE3NLK18JBB2iASAWGLE9qKdEi5xPQNSmWFca5rjEvHA0imnF+PZixwVX
GZT/TD409unJp0eTx/pBX6M0Ml/o+/BjssFfU2d70UzQzk62yqIE4TotCL1bXMVJ
KC11+lLPDim0Qe6FppJ7HMvpJdnJDvBUaGOH+Mmz69rOCNCLpa9wis42qhG3QK0Z
r73a8WNx29ZYLnLysblG2WS5Yec7PpXe3UdAqkxOf9MWesSaxWjlLmCTjrD/lDy2
c2QGu4gULmI6jYRbg+t21z9JPiQvbMKRUde8DQUtZoCYVlsSJOU/62uaWQbHGnWU
lG6BQj/bHoJ0NLNXXeYgZtJzVgsdpAFbzcikE6RvdigUsS9tO25nZD7brrGFO53a
hsUyM+UFVfNvueNZ7bj3slc8zvUx4VE8PvKPUJDtRNvNXPnT3J9x8QVMFOHE36+1
JKNIFXWAgDbOrgVZQcnv4+4m3epM6NYYmQAozn5v7JSiOfMnF3g=
=uzr9
-----END PGP SIGNATURE-----
On 13/12/17 17:57, Robie Basak wrote:
> 2) Come up with and agree on some other universal way for testing for
> systemd and make that work everywhere. Then we can SRU that test to MAAS
> in Trusty, and fix any other packages in Trusty affected by the
> behaviour change of the original test.

Possibly too simplistic, but,

On a 14.04 system:

$ file /sbin/init
/sbin/init: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.24,
BuildID[sha1]=7a4c688d009fc1f06ffc692f5f42ab09e68582b2, stripped

On a 16.04 system:

$ file /sbin/init
/sbin/init: symbolic link to /lib/systemd/systemd


Other "pure-systemd" systems (e.g. Arch) use a symlink similar to 16.04
so this should work with later Ubuntu releases too:

$ file /sbin/init
/sbin/init: symbolic link to ../lib/systemd/systemd


J