| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 26/05/13 07:40 AM, Luca Barbato wrote: |
| 5 |
> On 5/26/13 12:57 PM, Micha³ Górny wrote: |
| 6 |
>> You are telling me that a wrapper, a thing that gets executed |
| 7 |
>> *every* boot needs to do some random magic to know which init |
| 8 |
>> system was in use and which one is supposed to be in use, and |
| 9 |
>> then conditionally move around configuration files necessary for |
| 10 |
>> it to run. This is just *INSANE*. |
| 11 |
> |
| 12 |
> I like to think it normal and the wrapper doesn't need to run every |
| 13 |
> time but only when a switch had been requested. And only if you |
| 14 |
> prefer doing the switch at boot time instead than at shutdown. |
| 15 |
> |
| 16 |
|
| 17 |
The way it's being proposed (and please correct me if i'm wrong), the |
| 18 |
wrapper is a direct replacement binary (small C program) for all init |
| 19 |
systems, and would based on some configuration file or whatnot |
| 20 |
determine and exec the init system it's supposed to -- and make any |
| 21 |
other necessary changes too, such as switching /etc/inittab) |
| 22 |
|
| 23 |
I don't know (outside of a script in the initramfs) how this would |
| 24 |
otherwise be handled to cover all cases. I am curious though, if you |
| 25 |
see a way to do this otherwise, what the implementation would look like? |
| 26 |
|
| 27 |
|
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 30 |
|
| 31 |
iF4EAREIAAYFAlGiIxAACgkQ2ugaI38ACPDrbAD/exZAI4utNuOBAMzdkeYj8JgB |
| 32 |
lmeOg+G892g4yYMa6cIBALEQMH3bliQ0hF3HEtJezdbzG4/XkaEdGIjM+gscxF79 |
| 33 |
=9J3a |
| 34 |
-----END PGP SIGNATURE----- |
Archives