On Mon, Jan 27, 2020 at 06:16:14PM +0100, Svante Signell wrote:
> It is as simple as:
> if ps -p1|grep -q "systemd"; then
This is not the correct way to detect whether systemd is the current
init system. You want:
if test -d /run/systemd/system; then
See https://www.freedesktop.org/software/syst
On 1/30/20 7:02 AM, Thomas Goirand wrote:
This is normally solved if using pre-depends, which ensure that a
package is configured before using it (and not just unpacked).
Having everything using sysusers have versioned Pre-Depends on systemd |
opensysusers would probably minimize the problem,
Le jeudi, 30 janvier 2020, 00.28:36 h CET Thomas Goirand a écrit :
> On 1/29/20 4:31 PM, Didier 'OdyX' Raboud wrote:
> > Software installed as /bin/systemd-* , created within the systemd project,
> > to fulfill systemd's view of the world, takes a reasonable hit on the
> > binaries' namespace: "sys
On 1/30/20 7:16 AM, Anthony DeRobertis wrote:
> There are some more that come to mind:
>
> * if we convert the exiting name to an alternative, there is the
> somewhat interesting work of actually changing a file over from an
> executable shipped in the package to an alternative, which would
Svante Signell writes:
> On Wed, 2020-01-29 at 12:23 -0800, Moritz Mühlenhoff wrote:
>> Simon McVittie wrote:
>> > I think we have a fairly good picture of the costs that would be
>> > incurred from using alternatives:
>>
>> Plus in the case of opentmpfiles; a pile of security issues: systemd-
>>
5 matches
Mail list logo
