Peter Dolding 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 prefer the upstart
syntax, which avoids the temptation to write unreadable one-line
Russ Allbery (r...@debian.org)
> In general, upstart's integration with arbitrary actions in shell
> fragments is considerably better than systemd's, at least based on the
> documentation I've read. upstart feels like it provides more useful
> flexibility
This is in fact a extremely bad idea how
On Thu, Oct 31, 2013 at 07:20:12AM -0400, Theodore Ts'o wrote:
> On Thu, Oct 31, 2013 at 01:41:53AM -0700, Steve Langasek wrote:
> > I'm surprised by this comment. Very little policy is actually encoded in
> > upstart's C code; in fact, the only policy I can think of offhand that is is
> > some ba
Konstantinos Margaritis writes ("Bug#727708: init system question before the
technical committee"):
> So I think this question should really be added as a con to systemd.
The way that the Debate wiki system works is that the proponents of
any particular answer are in charge of the page on that an
Hi all,
I'd just like to mentioned just a small(big? you decide) issue that I
haven't seen mentioned yet from anyone. Against systemd.
systemd has explicitly mentioned its Linux-only support. Sure, that
affects kFreeBSD/Hurd now. But changing an init system should be done
looking ahead *at least
Ian Jackson writes:
> How long do people think finalising this is going to take ? There are
> some potential problems with setting a hard deadline in advance but
> we're hoping to deal with this matter fairly soon now.
I propose the following approach:
1. Set a date for the first drafts of the
David Härdeman writes ("Bug#727708: tech-ctte: Decide which init system to
default to in Debian."):
> I'm not a DD, just a random contributor, and I haven't been actively
> involved in the init system debate at all, nor do I have any stake in
> it, though I've followed it with some interest.
>
Ian Jackson writes ("Bug#727708: init system question before the technical
committee"):
> Steve Langasek writes[1]:
> > https://wiki.debian.org/Debate/initsystem/systemd
...
> So I would appreciate it if you (and by "you" I mean each side of the
> argument) would make sure that your page represe
* Theodore Ts'o:
> The most basic is the idea that whether you can control (via shell
> scrpit fragments) whether or not a service should start at all, and
> what options or environments should be enabled by pasing some file.
Curiously, a lot of system administrators do not do this correctly
usin
On Thu, Oct 31, 2013 at 01:41:53AM -0700, Steve Langasek wrote:
> I'm surprised by this comment. Very little policy is actually encoded in
> upstart's C code; in fact, the only policy I can think of offhand that is is
> some basic stuff around filesystems, which, aside from some must-have kernel
>
* Russ Allbery (r...@debian.org) [131031 02:19]:
> Theodore Ts'o writes:
> > On Mon, Oct 28, 2013 at 06:21:27PM -0700, Russ Allbery wrote:
>
> >> Well, I've said this before, but I think it's worth reiterating.
> >> Either upstart or systemd configurations are *radically better* than
> >> init sc
Dear Committee members,
I'm not a DD, just a random contributor, and I haven't been actively
involved in the init system debate at all, nor do I have any stake in
it, though I've followed it with some interest.
Now that the question has been referred to the Technical Committee
(which seems r
Op 31-10-13 02:50, Theodore Ts'o schreef:
> On Wed, Oct 30, 2013 at 06:18:29PM -0700, Russ Allbery wrote:
>> I suspect you and I have a root disagreement over the utility of exposing
>> some of those degrees of freedom to every init script author, but if you
>> have some more specific examples of p
On Wed, Oct 30, 2013 at 08:41:10PM -0400, Theodore Ts'o wrote:
> On Mon, Oct 28, 2013 at 06:21:27PM -0700, Russ Allbery wrote:
> > Well, I've said this before, but I think it's worth reiterating. Either
> > upstart or systemd configurations are *radically better* than init scripts
> > on basically
14 matches
Mail list logo
