On 08/07/2015 09:31 PM, Miles Fidelman wrote:
Trivial as in, somebody has to do it. The whole point of packaging is
to automate a lot of the routine things involved in installation.
And, because Debian (and presumeably Devuan) don't put stuff in
default locations, packaging involves chang
Rainer Weikusat wrote:
Miles Fidelman writes:
Rainer Weikusat wrote:
Miles Fidelman writes:
Alexey Rochev wrote
*Date: *2015-08-05 07:29 -400
*To: *dng
*Subject: *[DNG] Init scripts in packages
Currently Debian packages contains both systemd units and init scripts.
However, Debian develope
On Friday, August 07, 2015 06:13:10 PM Gregory Nowak wrote:
>
> I actually don't mind dropping gnome. It does depend on systemd by
> defacto, and is bulky. I did try xfce in a fresh install of debian
> jessie, and found it gave me speech when I rebooted after the
> install.
I'm sorry, I don't k
On Thu, Aug 06, 2015 at 05:14:28PM +0200, Laurent Bercot wrote:
> On 06/08/2015 16:31, Isaac Dunham wrote:
> >If differences in environment can cause problems, it's a problem with
> >design. A program that changes what it does just due to differences
> >between the init environment and a login envi
On Fri, Aug 07, 2015 at 07:53:37PM -0500, T.J. Duchene wrote:
> =( Bummer!
>
> There must be a way to get what you want, although I honestly do not know
> enough about systemd to help you out. Like yourself, I am more familiar with
> the System 5 way of doing things.
>
> Wish I could be mor
On Friday, August 07, 2015 05:46:00 PM Gregory Nowak wrote:
>
> I also did do an aptitude search sysv when I had debian jessie freshly
> installed, but didn't get a match. If I could have installed sysvinit
> or sysvinit-core in a fresh installed, I might have tried that just to
> see what I got.
On Fri, Aug 07, 2015 at 07:25:50PM -0500, T.J. Duchene wrote:
> I am just curious, but did you try installing sysvinit and systemd-shim?
> Theoretically, it should give you System 5 startup and shutdown, while
> keeping
> compatibility with things that depend on systemd, like Gnome.
No. If it
On Friday, August 07, 2015 05:06:14 PM Gregory Nowak wrote:
> 2. I want ctrl+alt+del to do shutdown -h, instead of shutdown -r
> (another real use case on another virtual system). I couldn't figure
> out a way to do this in debian jessie.
>
> Now, what you proposed above from what I understand s
On Fri, Aug 07, 2015 at 01:58:19PM +0100, Rainer Weikusat wrote:
> As someone else pointed out, the control flow code could be abstracted
> away into some kind of 'universal init script' and individual ones would
> just need to define the start and stop commands. And there's nothing
> horrible abou
Roger,
I haven't had a chance, but I wanted to thank you for your insights regarding
C++ last month. I've not used it as a "main language" in some time.
I was coding in C++ long before smart pointers were introduced. Old habits
die hard I suppose.
Your comments made me reconsider many thin
>James Powell Thu, 06 Aug 2015 01:02:56 -0700
>Currently Debian packages contains both systemd units and init scripts.
>However, Debian developers refused to support several init systems. So it's
>only a matter of time when they remove init scripts from packages.What will
>Devuan developers do
If I might add my two cents a few days late,
I really do not think that kdbus matters overly much and that people
(including myself in the past) have assigned too much concern to the topic.
Kdbus is little more than an implementation of dbus, which is a fairly neutral
protocol. The concern o
richard white wrote:
> I have use OSS4 on a few machine and have been very satisfied, but not a
> lot with multichannel. I appreciate the separate volume controls for each
> application,
>
> Maybe this could help:
> http://manuals.opensound.com/developer/multichannel.html
Glad to hear that OSS4 w
- Original Message -
> From: "Rainer Weikusat"
> Miles Fidelman writes:
>> Worse, if "refuse to support multiple init systems" means that the
>> Debian packagers start stripping out the init scripts from Debian
>> packages, those, those packages become useless in Devuan.
>
> This is act
Miles Fidelman writes:
> Rainer Weikusat wrote:
>> Miles Fidelman writes:
>>
>>> Alexey Rochev wrote
*Date: *2015-08-05 07:29 -400
*To: *dng
*Subject: *[DNG] Init scripts in packages
Currently Debian packages contains both systemd units and init scripts.
However, Debian d
Good grief . . . this is turning into some sort of battle of the titans . . .
would be nice to take the egos down a notch . . .
On Fri, 8/7/15, Rainer Weikusat wrote:
Subject: Re: [DNG] ideas for system startup
To: dng@lists.dyne.org
Date: Friday,
tilt! writes:
[...]
> Laurent Bercot wrote on 06/08/2015 at 14:21 CEST:
>> [...]
>> And "status". This is very service-dependent: since there is no
>> global API, no service manager, scripts will query the daemon's
>> status in a daemon-specific way. More vagueness again, because
>> "status" d
Laurent Bercot writes:
[...]
>> 1) Keep a relatively simple init which kicks off execution of commands in
>> response to 'change the system state' request and nothing else (get
>> rid of as much of /etc/inittab as possible at some point in time)
[...]
> You keep hammering that down a
Rainer Weikusat wrote:
Miles Fidelman writes:
Alexey Rochev wrote
*Date: *2015-08-05 07:29 -400
*To: *dng
*Subject: *[DNG] Init scripts in packages
Currently Debian packages contains both systemd units and init scripts.
However, Debian developers refused to support several init
systems. So it
I'm not sure how systemd does it, but in my vision, there should be
two different states for the service: the *wanted* state, and the
*current* state.
The wanted state is what is set by the administrator when she runs
a command such as "rc thisrunlevel". The command should set all the
services
On 07/08/2015 14:58, Rainer Weikusat wrote:
There's obviously a TOCTOU race here because "A is ready now" doesn't
mean "A is still ready" at any later time.
Of course. That's why you need a supervisor to receive death notifications
and publish them to whomever subscribes.
If there's somethi
Apologies, a typo:
I wrote myself on 07/08/2015 at 15:21 CEST:
[...]
* the status is "failed" (the service is *NOT* alive, and this
is due to it having failed to start on a previous attempt
to do so).
My question is, did I understand that correctly?
[...]
Kind regards.
Hi,
sorry for picking up on this edge while the thread's general
discussion has advanced further.
The "status" command matters to me; that is why I would like
to address its handling in a more detailed manner.
Laurent Bercot wrote on 06/08/2015 at 14:21 CEST:
[...]
And "status". This is very
Miles Fidelman writes:
> Alexey Rochev wrote
>> *Date: *2015-08-05 07:29 -400
>> *To: *dng
>> *Subject: *[DNG] Init scripts in packages
>> Currently Debian packages contains both systemd units and init scripts.
>> However, Debian developers refused to support several init
>> systems. So it's
>> o
Simplification of init scripts can be done by replacing them with a
text file containing the following:
a) preliminary logic tests to verify whether daemon can be started
b) command to start daemon together with parameters
c) command to stop daemon with parameters if applicable
Only two lines will
25 matches
Mail list logo
