1 |
On Wed, Sep 17, 2014 at 3:28 PM, James <wireless@×××××××××××.com> wrote: |
2 |
> Linus should make a clear, leadership statement that there will |
3 |
> always be a path for folks to use another mechanism besides systemd |
4 |
> in the linux kernel; This does not have to be a systemd vs cgroups |
5 |
> discussion, but it being presented this way. A clear statement |
6 |
> of multiplicity will put this issue to rest once and for all. By not stating |
7 |
> clearly was is obvious, many technically astute folks are looking for |
8 |
> options. Surely a fork is emminent and it will most likely be |
9 |
> the best thing to happen to linux, as the entire kernel development |
10 |
> process has become tainted by those with billions of dollars. |
11 |
|
12 |
Uh, the only thing the Linux kernel does is spawn a single process as |
13 |
PID 1 and offer a VERY STABLE system call interface for that and |
14 |
future processes to make requests. Nobody is going to break sysvinit |
15 |
if that happens to be the thing you tell Linux to execute as PID 1. |
16 |
|
17 |
Whether anybody else actually supports sysvinit is a different matter. |
18 |
I'm sure it will be around in Gentoo for a long time, and those with |
19 |
official Gentoo support contracts will get the same care they are used |
20 |
to. :) |
21 |
|
22 |
-- |
23 |
Rich |