| 1 |
On 05/25/2013 02:13 PM, hasufell wrote: |
| 2 |
> Isn't eselect for cases where I might want to reconfigure something or |
| 3 |
> add configuration values such as for bash-completion, do testing with |
| 4 |
> java-vm or python implementations during development, switch opengl |
| 5 |
> implementation depending on the graphics driver loaded and whatnot. |
| 6 |
> |
| 7 |
> I don't see any of this applying to init system, nor do I see a reason |
| 8 |
> to randomly switch between those. It's rather something to configure |
| 9 |
> during installation, so I'd rather expect proper documentation. |
| 10 |
|
| 11 |
Beside switching completely init system (since there is this itch to try |
| 12 |
new toys here), you also have addons such as benchmarks such bootchart, |
| 13 |
fs layout mappers/optimizers such as ureadahead and e4rat. |
| 14 |
|
| 15 |
Some are something you want to run on-off. |
| 16 |
|
| 17 |
All this started because Fabio had enough people pestering him about |
| 18 |
systemd and he wanted some simple way so people could try it and get |
| 19 |
back once burnt or vice-versa. |
| 20 |
|
| 21 |
I have my uses for it since beside using bb-init to shave some time |
| 22 |
spent spawning ephemeral processes on complex runscript, there is also |
| 23 |
the runit integration in openrc that would feel bad having it rotting in |
| 24 |
a branch w/out making it available and it has the very same issues you |
| 25 |
have with systemd. |
| 26 |
|
| 27 |
So having an eselect applet for this kind of purposes makes sense. |
| 28 |
|
| 29 |
lu |
Archives