| 1 |
On Mon, Feb 24, 2014 at 3:11 PM, Yuri K. Shatroff <yks-uno@××××××.ru> wrote: |
| 2 |
> 24.02.2014 02:32, Alan McKinnon wrote: |
| 3 |
>> [1] For lack of a better term, let's just call systemd here a "system |
| 4 |
>> controller". What is this ONE thing a system controller should do and do |
| 5 |
>> it well? |
| 6 |
> |
| 7 |
> |
| 8 |
> An init daemon generally does one thing well. |
| 9 |
|
| 10 |
it's obvious you haven't thought this through. |
| 11 |
|
| 12 |
consider, for a moment, that the "one thing well" that an init daemon |
| 13 |
is supposed to do is |
| 14 |
"run programs that do arbitrary things to get the system to an arbitrary state". |
| 15 |
|
| 16 |
do you not see a problem? |
| 17 |
-- |
| 18 |
This email is: [ ] actionable [ ] fyi [x] social |
| 19 |
Response needed: [ ] yes [ ] up to you [x] no |
| 20 |
Time-sensitive: [ ] immediate [ ] soon [x] none |
Archives