1 |
On 06/02/2013 08:20 PM, Steven J. Long wrote: |
2 |
> On Sun, Jun 02, 2013 at 11:15:37AM +0200, Luca Barbato wrote: |
3 |
>> On 06/01/2013 11:23 AM, Steven J. Long wrote: |
4 |
>>> That's not an argument for using a symlink switcher or the |
5 |
>>> equivalent across the board, by any means. |
6 |
>> |
7 |
>> Your opinion. |
8 |
> |
9 |
> That's not an argument for it either. |
10 |
|
11 |
Had been explained in the thread, please read it. |
12 |
|
13 |
>>> Firstly, we should be recommending people install Gentoo with enough |
14 |
>>> flexibility to configure and use their system how they choose. In the |
15 |
>>> UEFI arena, why not simply recommend something like rEFIt instead of |
16 |
>>> making everyone go through a load of development effort, to restrict |
17 |
>>> us all to a crippled use-case? |
18 |
>> |
19 |
>> Beside rEFIt being deprecated and rEFInd being in early stage of |
20 |
>> development (thus working great on some platforms and not working at all |
21 |
>> on some other) and with a good chunk of documentation to read before |
22 |
>> being able of deploying it? |
23 |
> |
24 |
> The typical thing Gentoo users get told is "this is a new thing, it will |
25 |
> take some time to work out, bear with us" as their production servers go |
26 |
> tits-up around them. So in this case too, work with upstream to implement |
27 |
> better solutions you, and the wider ecosystem, can all use. |
28 |
|
29 |
I'm afraid you never used those nor you are in one of those situation in |
30 |
which you have less options. |
31 |
|
32 |
> And STILL the best interim solution till your EFI setup has a bootloader. |
33 |
|
34 |
Again you should read the whole thread, please do, the whole eselect |
35 |
init stuff should stay opt-in for the time being so all this discussion |
36 |
is close to pointless. |
37 |
|
38 |
Consider this email a friendly warning, please do not pollute the Gentoo |
39 |
media with pointless email when you had been already politely told that |
40 |
your concern had been addressed in the previous email in the thread. |
41 |
|
42 |
> You're free to work on whatever you want. You just haven't made any |
43 |
> case for why the rest of the ecosystem should be crippled to allow for a |
44 |
> use-case that would be better served by an existing, far more robust |
45 |
> solution. |
46 |
|
47 |
Had it been the case we wouldn't had spent some weeks picking our brains |
48 |
on it. |
49 |
|
50 |
> Then it can be runit or whatever else takes your fancy. You are ignoring |
51 |
> the point of that paragraph though: someone has to put the install together. |
52 |
> |
53 |
> Or it isn't a Gentoo install. |
54 |
|
55 |
And you seem to miss the point that all you are telling had been |
56 |
discussed, taken in consideration and in some part agreed with already... |
57 |
|
58 |
> Wrt to the first, funnily enough the kernel developers have been here before, |
59 |
> just like they had with ethN and wlanN. It's a basic requirement for developing |
60 |
> an OS that you be able to switch init and fallback to other options. |
61 |
|
62 |
Again you didn't ready or you forgot. I said already I don't care about |
63 |
systemd many times, yet you failed to remember that. |
64 |
My specific use-case would require a trip to single mode and a second |
65 |
reboot, the way I want to do spares that. |
66 |
|
67 |
On an EFI-stub only system it would require at least a kernel rebuild or |
68 |
a trip to the efi shell if available. |
69 |
|
70 |
> Honestly, my goal is a saving of time so people can focus on making the |
71 |
> eselect module work properly, and be of real value to an end-user who wants |
72 |
> to switch init. |
73 |
|
74 |
To not make this a waste of time here a summary of the whole thing: |
75 |
|
76 |
- eselect init will be opt-in for the time being, people can be left on |
77 |
their own tools if the want it |
78 |
- the default init will stay sysvinit. Discussion ongoing if is better |
79 |
to have it installed in a secondary fallback path is open (e.g. /bin/init). |
80 |
- I still need to send patches to busybox and sysvinit upstream to add a |
81 |
command line switch to locate the inittab. |
82 |
- people wanting to switch init or enable/disable init addons using |
83 |
eselect init might have to refer to /sbin/einit or such custom path |
84 |
(assuming we fail to come to an agreement regarding /bin/init) |
85 |
|
86 |
The wrapper in /sbin/init is mostly needed to get to the point of a |
87 |
clean reboot. |
88 |
|
89 |
The first time you boot on a new system it is executed picking the new |
90 |
init and just that. |
91 |
|
92 |
For addons such as bootchart2 and e4rat it would do slightly more. |
93 |
|
94 |
Assuming upstream doesn't accept custom paths for the inittab, for my |
95 |
specific usecase I might bake something that would remount r/w and pivot |
96 |
the inittabs. |
97 |
|
98 |
Anybody willing to do something more extreme could even consider having |
99 |
/sbin/init as a symlink and have the boot-time configuration switch the |
100 |
symlink, thus making the whole script run just a single boot per switch. |
101 |
|
102 |
Not necessary but surely feasible. |
103 |
|
104 |
lu |