On 02/11/13 04:11, Russ Allbery wrote:
I think the right way to put this is that systemd has significant
development resources behind it and is working in fairly close cooperation
with both kernel developers and GNOME developers to make available new
kernel functionality and to provide
Carlos Alberto Lopez Perez clo...@igalia.com writes:
Regarding the development force behind each project, I find the following
comparison at Ohloh very illustrative
https://www.ohloh.net/p/compare?project_0=openrcproject_1=upstartproject_2=systemd
This isn't really a fair comparison since
On Fri, Nov 1, 2013 at 2:51 PM, Russ Allbery r...@debian.org wrote:
Peter Dolding oia...@gmail.com writes:
The one property about systemd unit files that is extremely good is
there are no multi line commands. Every command is a single line.
Yes, that's exactly what I think is obnoxious. I
Peter Dolding oia...@gmail.com writes:
ExecStartPre=, ExecStartPost= can be written many times.
ExecStartPre= rm somewhere
ExecStartPre= touch somewhere
That really doesn't help, because...
In fact lot of cases I see one line entries in systemd and I see bad
form. Unless one line has
Hi,
I just want to raise one issue that I think has not been adequately
addressed by any of the position statements (it has unfortunately been
deleted from the upstart page and been trimmed down a lot on the systemd
page):
I think an important drawback of upstart is the idea of treating
On 10/31/2013 09:51 PM, Russ Allbery wrote:
You can, of course, be
disciplined about this when writing systemd helper scripts by always
exernalizing the shell script into a separate file, but I really like that
upstart lets me inline trivial shell fragments without worrying about
that while
6 matches
Mail list logo
