| 1 |
On Sat, Nov 19, 2016 at 2:06 PM, Ian Zimmerman <itz@×××××××.net> wrote: |
| 2 |
> On 2016-11-19 10:21, Kai Krakow wrote: |
| 3 |
> |
| 4 |
>> Well, let's wait for the argument "but this is not the unix way". ;-) |
| 5 |
> |
| 6 |
> No, that is not my argument. |
| 7 |
> |
| 8 |
> My argument is: I want _control_. As in the GNU Manifesto. And that |
| 9 |
> means no huge subsystems dipping their claws into everything, and |
| 10 |
> starting obscure daemons behind my back. |
| 11 |
> |
| 12 |
|
| 13 |
Presumably if you sent a dbus message to your service manager asking |
| 14 |
it to start a daemon that doesn't count as being behind your back. |
| 15 |
|
| 16 |
If you're talking about something starting at boot time, I've yet to |
| 17 |
hear of a service manager that doesn't let you tell it what services |
| 18 |
you want, or one that doesn't come with some set of defaults. As I |
| 19 |
recall sysvinit went spawning gettys on first boot and I don't recall |
| 20 |
having to tell it to do that, fortunately. :) |
| 21 |
|
| 22 |
-- |
| 23 |
Rich |
Archives