On Sat, Sep 30, 2017 at 5:32 PM, Duncan <1i5t5.dun...@cox.net> wrote:
> Walter Dnes posted on Sat, 30 Sep 2017 00:20:31 -0400 as excerpted:
>
>> But, how do we reliably detect the currently running init system? Are
>> there running processes, or entries in /sys/ or /proc/ or /dev that are
>> uniqu
Walter Dnes posted on Sat, 30 Sep 2017 00:20:31 -0400 as excerpted:
> But, how do we reliably detect the currently running init system? Are
> there running processes, or entries in /sys/ or /proc/ or /dev that are
> unique to to each init system?
In theory at least, that's easy enough, just chec
Harald Weiner posted on Fri, 29 Sep 2017 04:47:35 +0200 as excerpted:
> Duncan posted on 09/29/17 2:08 AM as excerpted:
>
>> Or are we going to replace rm, and fdisk, and gdisk, and cfdisk, and
>> cgdisk, and who knows how many other binaries, with "safe"
>> alternatives,
>> because some gentooe
Duncan posted on 09/29/17 2:08 AM as excerpted:
> Or are we going to replace rm, and fdisk, and gdisk, and cfdisk, and
> cgdisk, and who knows how many other binaries, with "safe" alternatives,
> because some gentooer couldn't be bothered to think for a moment whether
> a command in some instr
Austin English posted on Thu, 28 Sep 2017 16:27:31 -0500 as excerpted:
> (Note: serious discussion, please take systemd trolling elsewhere).
>
> While having the pleasure of working with some proprietary software
> recently, I was asked to run `service foo restart`, and was surprised to
> see:
>
