This patch adds a cpp definition HAVE_SYSV_COMPAT that is used to
isolate code dealing with /etc/init.d and /etc/rcN.d for systems where
it does not make sense (one that does not use sysv or one that is fully
systemd native).
The patch tries to be as little intrusive as possible, however in
order
This patch adds a cpp definition HAVE_SYSV_COMPAT that is used to
isolate code dealing with /etc/init.d and /etc/rcN.d for systems where
it does not make sense (one that does not use sysv or one that is fully
systemd native).
The patch tries to be as little intrusive as possible, however in
order
On Wed, Sep 8, 2010 at 1:32 AM, Gustavo Sverzut Barbieri
wrote:
> This patch adds a cpp definition HAVE_SYSV_COMPAT that is used to
> isolate code dealing with /etc/init.d and /etc/rcN.d for systems where
> it does not make sense (one that does not use sysv or one that is fully
> systemd native).
From: Fabiano Fidencio
This patch adds a cpp definition HAVE_SYSV_COMPAT that is used to
isolate code dealing with /etc/init.d and /etc/rcN.d for systems where
it does not make sense (one that does not use sysv or one that is fully
systemd native).
The patch tries to be as little intrusive as po
On Wed, 08.09.10 11:35, Gustavo Sverzut Barbieri (barbi...@profusion.mobi)
wrote:
> This patch adds a cpp definition HAVE_SYSV_COMPAT that is used to
> isolate code dealing with /etc/init.d and /etc/rcN.d for systems where
> it does not make sense (one that does not use sysv or one that is fully
On Tue, 21.09.10 00:23, Gustavo Sverzut Barbieri (barbi...@profusion.mobi)
wrote:
> From: Fabiano Fidencio
>
> This patch adds a cpp definition HAVE_SYSV_COMPAT that is used to
> isolate code dealing with /etc/init.d and /etc/rcN.d for systems where
> it does not make sense (one that does not u