| 1 |
On Fri, Feb 21, 2014 at 12:46 PM, EBo <ebo@×××××××.com> wrote: |
| 2 |
> Recently Debian decided to accept and migrate over to systemd to be |
| 3 |
> compatible with SysV and LSB init scripts. |
| 4 |
|
| 5 |
More exactly, Debian chose systemd as the default for their next |
| 6 |
release. This means it may not be the default in future releases. |
| 7 |
Also, it is only the default. Just like Gentoo, Debian is not limited |
| 8 |
to one init system. |
| 9 |
|
| 10 |
> I cannot remember if Gentoo was |
| 11 |
> originally based on Debian, Slackware, or some other distro, but it seems a |
| 12 |
> lot of the distros are starting to migrate to unified systemd init. |
| 13 |
|
| 14 |
Gentoo is not based on any other Linux distributions. At most you can |
| 15 |
say that some ideas of its original concept were borrowed from |
| 16 |
FreeBSD. Gentoo is a base distribition with its own set of |
| 17 |
derivatives, just like Debian and Slackware. |
| 18 |
|
| 19 |
Most distributions choose to only support one init system. Either |
| 20 |
because the way they operate make it necessary or because they want to |
| 21 |
simplify their workload. It is very unlikely such a thing happens to |
| 22 |
Gentoo. It is even debatable that there is a default in Gentoo. Most |
| 23 |
users seem to be attached to OpenRC, but the fact that systemd is a |
| 24 |
hard requirement of Gnome blurs the picture. |
| 25 |
|
| 26 |
> forget where Arch-Linux came into this, but I think they helped move Debian |
| 27 |
> to accepting systemd. |
| 28 |
|
| 29 |
As far as I know, Arch had nothing at all to do with Debian's decision. |
| 30 |
|
| 31 |
Denis. |
Archives