1 |
On Sun, 26 May 2013 10:58:23 +0200 |
2 |
Robert David <robert.david.public@×××××.com> wrote: |
3 |
|
4 |
> > Increased complexity is never safer. And a wrapper means the |
5 |
> > additional complexity gets there every boot. And considering how |
6 |
> > the discussion goes, the wrapper will grow openrc-size in a few |
7 |
> > months.. |
8 |
> |
9 |
> I agree with this. But changing symlinks is not as easy on running |
10 |
> system (since it can cause inconsistence during rebooot). I think that |
11 |
> safest way not using wrapper is to stop all services and keep only |
12 |
> mounted /, than change things (symlinks,configuration update) and |
13 |
> reboot. |
14 |
> |
15 |
> Thus this "eselect init" will let the user confirm and then trigger |
16 |
> reboot. I do not think that users will change init all the time, thus |
17 |
> make it better safe and more complex in this change is better than |
18 |
> check and wrap in all the boots. |
19 |
> |
20 |
> Otherwise interesting is preinit handler in OpenWrt: |
21 |
> http://wiki.openwrt.org/doc/techref/process.boot |
22 |
> http://wiki.openwrt.org/doc/howto/notuci.config#etcpreinit |
23 |
> http://wiki.openwrt.org/doc/techref/preinit_mount |
24 |
|
25 |
In other words, if you go for the symlink approach you're just moving |
26 |
complexity to your system instead of into the boot; I don't see why a |
27 |
wrapper would grow to openrc size, that's just a bold exaggeration. |
28 |
|
29 |
I'd rather have a clean wrapper that just works than an unclean way to |
30 |
cover the reboot madness that comes along; forcing a reboot, really? |
31 |
|
32 |
-- |
33 |
With kind regards, |
34 |
|
35 |
Tom Wijsman (TomWij) |
36 |
Gentoo Developer |
37 |
|
38 |
E-mail address : TomWij@g.o |
39 |
GPG Public Key : 6D34E57D |
40 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |