On 02.07.2012, at 10:39, Manuel Reimer <manuel.rei...@gmx.de> wrote:
> Gerald Dachs wrote:
>>> That's the current state. I can't think of a good reason why it has to
>>> stay that way though. VDR itself could have a menu that allows to enable,
>>> disable and configure plugins.
>> I can't see a benefit of this approach. At least for distributors it would
>> more complicated to install plugins with a specific default configuration,
>> because that would mean all configuration informations would go into the
>> setup.conf and it is no good idea to manipulate this file from outside.
> Again: systemd ist *one of many* init solutions and I guess, that Klaus
> doesn't use a distribution with systemd.
No, I don't.
VDR (and me, too ;-) doesn't care in what way a particular system boots
or starts its services.
The 'runvdr' script that comes with the VDR source is merely a suggestion
of how to create an environment in which VDR can be (re-)started.
vdr mailing list