| 1 |
On Sun, Sep 21, 2014 at 8:26 PM, Frank Peters <frank.peters@×××××××.net> wrote: |
| 2 |
> |
| 3 |
> My system is booted and configured using my own custom scripts and |
| 4 |
> I doubt that anyone would be interested in those. They work very well |
| 5 |
> for me and as a consequence I have no interest in contributing to |
| 6 |
> alternatives that I'll never utilize. (In fact, I would encourage |
| 7 |
> everyone to develop his own set of boot/config routines. It is |
| 8 |
> not that difficult.) |
| 9 |
> |
| 10 |
> The concern is that one day this will no longer be possible due to |
| 11 |
> the hegemony imposed by players such as those already mentioned. |
| 12 |
|
| 13 |
I think you need to relax a bit if that is really your worry. |
| 14 |
|
| 15 |
You can still run a.out executables, and there is no roadmap for ever |
| 16 |
disabling that. You can create device nodes using mknod, and I'd be |
| 17 |
shocked if that ever went away. Just what is it that you actually |
| 18 |
need the kernel to do for you that you don't think will still be |
| 19 |
around in 20 years? Linus is VERY conservative about removing system |
| 20 |
calls. |
| 21 |
|
| 22 |
It isn't like the bits in sysvinit have an expiration date on them. |
| 23 |
|
| 24 |
Sysvinit is only 2900 lines of code, and you could probably cut out |
| 25 |
half of them without losing much. I doubt it will ever stop working, |
| 26 |
but even if it did fixing whatever breaks will probably be trivial. |
| 27 |
|
| 28 |
If the whole world moves to systemd the biggest problem you'll have is |
| 29 |
that you'll have to write your own service startup scripts, but from |
| 30 |
the sound of things you're doing that anyway. Most of the services |
| 31 |
you probably run aren't linux-exclusive either, so while it seems |
| 32 |
likely that many will start reporting their status to systemd it seems |
| 33 |
unlikely that they will refuse to work without it. |
| 34 |
|
| 35 |
-- |
| 36 |
Rich |
Archives