1 |
On 06/29/11 17:14, Olivier Crête wrote: |
2 |
> On Wed, 2011-06-29 at 11:08 +0200, Patrick Lauer wrote: |
3 |
>> On 06/29/11 03:07, Olivier Crête wrote: |
4 |
>>> Hi, |
5 |
>>> |
6 |
>>> On Tue, 2011-06-28 at 17:10 -0500, William Hubbs wrote: |
7 |
>>>> The background is that /etc/init.d/functions.sh is a link to |
8 |
>>>> /lib/rc/functions.sh, which is part of openrc. |
9 |
>>>> |
10 |
>>>> Other init systems, like systemd, are coming along which completely |
11 |
>>>> replace sysvinit and do not use openrc's init scripts at all. However, |
12 |
>>>> since things other than init scripts are using /etc/init.d/functions.sh, |
13 |
>>>> all gentoo users are forced to have openrc on their systems whether they |
14 |
>>>> use its init scripts or not. |
15 |
>>>> |
16 |
>>>> As you can see in the bug, I am working on creating a |
17 |
>>>> minimalist version of openrc that can be installed to allow users to |
18 |
>>>> have access to the functions that are in functions.sh regardless of |
19 |
>>>> whether or not they are using openrc's init system. |
20 |
>>>> |
21 |
>>>> I'm not convinced that this is the best approach, so any input would be |
22 |
>>>> greatly appreciated. |
23 |
>>> |
24 |
>>> As long as we have Gentoo-style init scripts in the tree, we will need |
25 |
>>> these functions to be available. So yes, they should probably be in a |
26 |
>>> separate package from openrc itself to ease the transition to the bright |
27 |
>>> systemd future. |
28 |
>>> |
29 |
>> We tolerate the systemd madness as long as it doesn't interfere with |
30 |
>> other things. |
31 |
>> |
32 |
>> But as OpenRC has some rare features ("being able to start and stop |
33 |
>> stuff" and "being reasonably fast" among them) and there's no |
34 |
>> replacement at the moment I see no reason to add a convoluted mess of |
35 |
>> insanity just to feel good. |
36 |
> |
37 |
> I think you're missing how systemd is above and beyond OpenRC (and all |
38 |
> other init systems). It has stuff like using cgroups to guarantee that |
39 |
> all the processes associated with a service have stopped (openrc doesn't |
40 |
> do that), |
41 |
I've started playing around with it. Pretty tiny feature, I expect it to |
42 |
end up as <200 lines of shell. Once I finish that openrc will support it |
43 |
too, but without the Lennartizing that makes people so very joyful happy. |
44 |
|
45 |
|
46 |
> it provides very fast boot (openrc doesn't do that), |
47 |
Hmm, the comparisons I've seen are very mixed, with the performance |
48 |
difference between 0 and 50% in favour of OpenRC. I haven't seen |
49 |
anything catch OpenRC yet, but at least there's now an equivalent for |
50 |
rc-status ... |
51 |
|
52 |
> it can |
53 |
> activate services on demand (openrc doesn't do that), etc.. |
54 |
|
55 |
What's the usecase for that? Sounds more like an antifeature (either |
56 |
it's started or not, determinism rocks), and then there's things like |
57 |
xinetd that tend to get deprecated and rediscovered every 5 years ... |
58 |
|
59 |
What systemd can't do is run more than one command for a service, so ... |
60 |
hmm ... that's a rather funny riddle. And it hides things behind an |
61 |
opaque layer, so as soon as you need to edit internals (which I tend to |
62 |
do about 2-3 times a year with OpenRC) you're going to have to stab |
63 |
around in bad C instead of changing a simple shell script. |
64 |
|
65 |
But - having seen the horrors that others do in shell I *understand* why |
66 |
some people still think that shell-free startup is a good idea. It's |
67 |
not. Leg-free humans are a good way to avoid broken toes ... |
68 |
|
69 |
> And you also underestimate the amount of momentum that Lennart has |
70 |
> managed to amass behind systemd. I expect that much sooner than you |
71 |
> think, we won't have a choice but to switch to systemd as many core |
72 |
> components will start depending on it. |
73 |
> |
74 |
You underestimate the amount of "positive feelings" that Lennart has |
75 |
managed to create. Also for almost everyone else it adds functionality, |
76 |
but we've had that for a long time. I mean, Upstart is still unable to |
77 |
reliably start, stop or restart services. So migrating to systemd is |
78 |
good. OpenRC has been doing that since the beginning, so we don't gain |
79 |
anything. We just lose our flexible human-readable init scripts for no |
80 |
gain at all - hey, why doesn't that sound like a bonus to me? |
81 |
|
82 |
And you can bet that if anyone is so, how to say this politely, retarded |
83 |
to think that depending on systemd is a good idea will discover that |
84 |
people will patch around the stupid very fast. |
85 |
|
86 |
Plus there's some of us that will never be able to use systemd because |
87 |
it has artificial limitations in the kernels it supports. That's not a |
88 |
good idea. |
89 |
|
90 |
As much as I like your optimism, it's pretty much misguided and trying |
91 |
to make my life more difficult. I hope you don't mind if I try to stop |
92 |
you from creating work for me :) |
93 |
|
94 |
-- |
95 |
Patrick Lauer http://service.gentooexperimental.org |
96 |
|
97 |
Gentoo Council Member and Evangelist |
98 |
Part of Gentoo Benchmarks, Forensics, PostgreSQL, KDE herds |