| 1 |
On Sat, 25 May 2013 12:25:03 +0200 |
| 2 |
Peter Stuge <peter@×××××.se> wrote: |
| 3 |
|
| 4 |
> I would actually expect the change to take effect immediately. |
| 5 |
|
| 6 |
Then how would you be able to shutdown / reboot your system in a clean |
| 7 |
way? The premise here is that when you boot with an init system you |
| 8 |
must shutdown with that same init system, you can't just start one init |
| 9 |
system and expect the other init system to cleanly shut down its |
| 10 |
services. Therefore implementing this would either be unclean or way to |
| 11 |
complex. |
| 12 |
|
| 13 |
From all the methods discussed doing it on boot sounds the most sane. |
| 14 |
|
| 15 |
> On boot could work, except that it does add more steps (= more |
| 16 |
> fragility) to the boot process, which I think everyone wants to avoid. |
| 17 |
|
| 18 |
If it is implemented properly, it really isn't that fragile as you |
| 19 |
would think; it doesn't take much input, so there is barely any |
| 20 |
implementation and bug fixing needed and it will work everywhere. |
| 21 |
|
| 22 |
Users that manage to break this will often know how to fix, unless we |
| 23 |
messed up from the Portage tree; but well, this mostly boils down to a |
| 24 |
proper news item and documentation _before_ bringing this out such that |
| 25 |
users are at least aware of this crucial boot process change. |
| 26 |
|
| 27 |
Anyhow, users need to be aware anyway for when they ever decide to try |
| 28 |
or switch another init system in the future. |
| 29 |
|
| 30 |
-- |
| 31 |
With kind regards, |
| 32 |
|
| 33 |
Tom Wijsman (TomWij) |
| 34 |
Gentoo Developer |
| 35 |
|
| 36 |
E-mail address : TomWij@g.o |
| 37 |
GPG Public Key : 6D34E57D |
| 38 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives