>> On 21 May 2020, at 17:31, Steve Litt wrote:
>>
>> On Thu, 21 May 2020 05:13:52 +0100
>> tux...@sapo.pt wrote:
>>
>> Citando Steve Litt :
>>> This whole discussion balances on the definition of "shell aware".
>>> What is "shell aware?"
>>> SteveT
>> Have you tried to write shell script code
On Thu, 21 May 2020 05:13:52 +0100
tux...@sapo.pt wrote:
> Citando Steve Litt :
>
> > This whole discussion balances on the definition of "shell aware".
> > What is "shell aware?"
> >
> > SteveT
> >
> >
>
> Have you tried to write shell script code into the execution command
> of a systemd
Citando Steve Litt :
This whole discussion balances on the definition of "shell aware". What
is "shell aware?"
SteveT
Have you tried to write shell script code into the execution command
of a systemd unit file?
it doesn't work right?!
Why do you think it doesn't work?
For it to work yo
On Tue, 19 May 2020 04:14:05 +0100
tux...@sapo.pt wrote:
> The problem is that this init systems are not shell aware.
I don't know what "shell aware" means. The minute a file begins with:
#!/bin/sh
the rest of the text executes according to the
grammar/syntax/capabilities of /bin/sh.
> yes th
I believe I didn't expressed myself well, and so was badly understood..
Citando Steve Litt :
On Sat, 16 May 2020 22:04:51 +0100
tux...@sapo.pt wrote:
Hello,
Citando Steve Litt :
It's such a shame. Runit and s6 were both there, waiting to be
picked up and used. Both were 10 times easier than
hello,
Citando Dimitris via Dng :
On 5/17/20 12:04 AM, tux...@sapo.pt wrote:
But is a major flaw, being it a init system for a operating system, and
not beign able to run shell scripts( systemd has also this limitation.. )..
you're right about s6, but wrong about systemd.you can run shell
On Sun, 17 May 2020 13:46:28 +0200
Didier Kryn wrote:
> Le 16/05/2020 à 11:30, Steve Litt a écrit :
> > On Fri, 15 May 2020 14:44:06 -1000
> > Joel Roth via Dng wrote:
> >
> >
> >> Reminds me to revisit https://ewontfix.com/14/
> >> for Felker's Broken by Design article on systemd.
> > That
On Sat, 16 May 2020 22:04:51 +0100
tux...@sapo.pt wrote:
> Hello,
>
> Citando Steve Litt :
>
> > It's such a shame. Runit and s6 were both there, waiting to be
> > picked up and used. Both were 10 times easier than sysvinit. But
> > n.
>
> All init systems that want to be taken seriou
Le 16/05/2020 à 11:30, Steve Litt a écrit :
On Fri, 15 May 2020 14:44:06 -1000
Joel Roth via Dng wrote:
Reminds me to revisit https://ewontfix.com/14/
for Felker's Broken by Design article on systemd.
That web page changed my life. When I saw, on that page, how simple PID1
could really be, t
On 5/17/20 12:04 AM, tux...@sapo.pt wrote:
> But is a major flaw, being it a init system for a operating system, and
> not beign able to run shell scripts( systemd has also this limitation.. )..
you're right about s6, but wrong about systemd.
you can run shell scripts with that bloated beast.
s
Hello Steve,
> This enraged me:
> The fact that a Troubleshooting Trainer could make an init in a couple
> weeks, yet the Redhat/Freedesktop/Poettering axis was telling us what a
> complex thing an init was.
They have in mind their own, different from yours and mine,
idea of how the computers ar
Hello,
Citando Steve Litt :
It's such a shame. Runit and s6 were both there, waiting to be picked
up and used. Both were 10 times easier than sysvinit. But n.
All init systems that want to be taken seriously, need to accept also
the system language..
As I understand, and was also
On Sat, 16 May 2020 11:41:29 +0200
Antony Stone wrote:
> On Saturday 16 May 2020 at 11:30:03, Steve Litt wrote:
>
> > You know, runit's or s6's process supervisor could be used, on
> > systemd systems, as a tobacco patch to wean the user off systemd,
> > one process at a time. As each daemon get
Quoting Antony Stone (antony.st...@devuan.open.source.it):
> It may have been sold that way in the early days, but it's now
> infiltrated so many parts of the GNU / Linux system that just telling
> people (or showing them) that they can use something else to manage
> their daemons is no longer eno
On Saturday 16 May 2020 at 11:30:03, Steve Litt wrote:
> You know, runit's or s6's process supervisor could be used, on systemd
> systems, as a tobacco patch to wean the user off systemd, one process
> at a time. As each daemon gets moved to runit or s6, that daemon's unit
> file name gets put in
On Fri, 15 May 2020 14:44:06 -1000
Joel Roth via Dng wrote:
> Reminds me to revisit https://ewontfix.com/14/
> for Felker's Broken by Design article on systemd.
That web page changed my life. When I saw, on that page, how simple PID1
could really be, that was when I really started to despise sy
16 matches
Mail list logo
