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 when it happens? We can use sysvinit and
Devuan becau
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 when it happens? We can use sysvinit and Devuan bec
On 05/08/15 23:29, Alexey Rochev wrote:
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 when it hap
Hello!
On 08/06/2015 04:22 AM, Joel Roth wrote:
[...]
What dmix doesn't do (and pulseaudio does) is provide a
separate volume control for each application.
... a feature that I use once per year; then it is quite useful. ;-)
I find ALSA provides really lots of useful tools, such as:
* the pl
Hello again,
just a hint for the resolute ones among us, as I think this hasn't been
mentioned on this list yet: Adding the following lines to e.g. the file
/etc/apt/preferences.d/avoid-systemd should make ultimately sure, that
libsystemd0 will not be accidentally pulled in by some felted packag
Alexey Rochev writes:
> 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.
This would rid the world of a lot of code of very dubi
tilt! wrote:
> Hello!
[summary of ALSA features snipped]
> d Since the setup in asoundrc is static in nature, dynamically
>assigning a multichannel routing, for example through an
>interactive volume control, to a specific application is
>something I would not immediately know how to a
On 08/06/2015 11:28 AM, Rainer Weikusat wrote:
[...]
But a bare-bones init script does really only three things:
1. Execute a command to start something.
2. Execute a command which stops it again.
3. Execute 2) then 1) for a restart.
There are additional actions required by [LSB]; out of these
Hi Joel,
On 08/06/2015 11:39 AM, Joel Roth wrote:
[...]
You don't mention what you want to accomplish specifically,
or why you were using JACK. It may be easier to solve your
specific problems, before trying to generally improve the
configuration of the audio services under Devuan.
I apprecia
* On 2015 05 Aug 21:23 -0500, Joel Roth wrote:
> What dmix doesn't do (and pulseaudio does) is provide a
> separate volume control for each application.
Which is an outstanding feature that I do miss on this desktop that I
purged PA from due to extant SysD dependencies. I would just like to
see
On 06/08/2015 11:45, tilt! wrote:
Thing is, init scripts tend to have problems managing services
that do not offer sufficient commandline interfaces as described
above
There's a simple reason for that: "init scripts" aren't
"managing services". They can more or less start and stop them,
that's
"tilt!" writes:
> On 08/06/2015 11:28 AM, Rainer Weikusat wrote:
>> [...]
>> But a bare-bones init script does really only three things:
>>
>> 1. Execute a command to start something.
>> 2. Execute a command which stops it again.
>> 3. Execute 2) then 1) for a restart.
>
> There are additional act
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
Also, here's is some good information for supporting OSS
.. and what about
https://crunchbangplusplus.org/assets/misc/cbpp-1.0-amd64-20150428.iso.torrent
instead of BunsenLabs? (=
Cheers,
__martin__
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Laurent Bercot writes:
> On 06/08/2015 11:45, tilt! wrote:
>> Thing is, init scripts tend to have problems managing services
>> that do not offer sufficient commandline interfaces as described
>> above
>
> There's a simple reason for that: "init scripts" aren't
> "managing services". They can mo
On Thu, Aug 06, 2015 at 10:47:34AM +0200, tilt! wrote:
>
> As for problem #1, I personally feel that the lack of user
> interface (tools and documentation) of the ALSA built-in
> solutions has been and is the primary motivator for developments
> like Pulseaudio.
The paradigm here is:
Package A
On Thu, Aug 06, 2015 at 02:21:55PM +0200, Laurent Bercot wrote:
> On 06/08/2015 11:45, tilt! wrote:
> >Thing is, init scripts tend to have problems managing services
> >that do not offer sufficient commandline interfaces as described
> >above
>
> There's a simple reason for that: "init scripts" a
On 06/08/2015 16:00, Rainer Weikusat wrote:
That's all nice and dandy but it all boils down to 'the code executed by
the init script was deficient in some way'.
Yes, just like root exploits boil down to "the code executed by the
suid program was deficient in some way".
My point is that you sh
I have noticed that the chief protagonist of Crunchbang, aka Corenominal, is
also a contributing developer on Bunsenlabs- just seems more genuine to me,
with Wheezy in LTS 'til 2018, and Devuan still 'tender', I can wait.
(thanks to this mailing list for allowing this, not very relevant, thread)
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 environment is going to be
hard to debug.
There are tons of those, and you
On Thu, 06 Aug 2015 15:00:20 +0100
Rainer Weikusat wrote:
> 'Winning' against systemd will require getting support of a
> commerically more potent company than RedHat and SuSE combined and one
> willing to sink a sizable amount of money into the task.
The day I believe the preceding sentence
On Thu, 06 Aug 2015 15:00:20 +0100
Rainer Weikusat wrote:
> Laurent Bercot writes:
> > There's a simple reason for that: "init scripts" aren't
> > "managing services". They can more or less start and stop them,
> > that's about it - and they're not even doing the starting and
> > the stopping
On Thu, 06 Aug 2015 10:28:47 +0100
Rainer Weikusat wrote:
> But a bare-bones init script does really only three things:
>
> 1. Execute a command to start something.
> 2. Execute a command which stops it again.
> 3. Execute 2) then 1) for a restart.
Those are easy. The tough part is process depe
On Thu, 6 Aug 2015 16:41:38 +0200
Laurent Bercot wrote:
> I have never said, am not saying, and probably never will say that
> systemd is any good. It's not, and Lennart and Kay should go back to
> engineering school,
:s/engineering school/kindergarten/
/* Litt ducks and runs */
__
Adam Borowski wrote on 23/07/15 07:45:
systemd-shim still means systemd. Devuan is supposed to fix this, but in
the meantime -- or if you prefer staying with Debian proper -- you can use
my repository of deinfested packages:
jessie:
deb http://angband.pl/debian nosystemd main
unstable/stre
Hendrik Boom wrote:
> How many audio systems does Linux have now?
>
> Does any of them have really low latency -- the kind you need if you
> are programming the synthesizer inside a live-performance musical
> instrument?
A lot of people do use Linux for live performance. The
soundcard DAC/ADC a
Laurent Bercot writes:
A leading remark: This is based on an existing system I have implemented
(originally for Debian 5) working in the described way. The code is
proprietary as I'm one of those evil guys who want to (and do) write code
for a living despite the 'free software community' traditio
On 06/08/2015 20:18, Rainer Weikusat wrote:
UNIX(*) and therefore, Linux, provides two system calls named fork and
exec which can be used to create a new process while inheriting certain
parts of the existing environment and to execute a new program in an
existing process, keeping most of the env
Laurent Bercot writes:
> On 06/08/2015 20:18, Rainer Weikusat wrote:
>> UNIX(*) and therefore, Linux, provides two system calls named fork and
>> exec which can be used to create a new process while inheriting certain
>> parts of the existing environment and to execute a new program in an
>> exist
On Thu, Aug 06, 2015 at 12:09:33PM +0200, tilt! wrote:
> I appreciate your kind offer of solving my specific
> technical problems a lot - however, as it stands, I have
> none *fingers crossed* ;-)
>
> What I want to accomplish is sufficiently addressed by my
> listing of problems a, b (grave defec
Rainer Weikusat writes:
> Laurent Bercot writes:
>> On 06/08/2015 20:18, Rainer Weikusat wrote:
>>> UNIX(*) and therefore, Linux, provides two system calls named fork and
>>> exec which can be used to create a new process while inheriting certain
>>> parts of the existing environment and to execu
On Thu, 2015-08-06 at 06:32 -0500, Nate Bargmann wrote:
> * On 2015 05 Aug 21:23 -0500, Joel Roth wrote:
>
> > What dmix doesn't do (and pulseaudio does) is provide a
> > separate volume control for each application.
>
> Which is an outstanding feature that I do miss on this desktop that I
> purg
Rainer Weikusat writes:
[...]
> I'm going to ignore the remainder of this because - while system startup
> is a topic of some interest to me - people warring over the right way to
> replace UNIX(*) because it's broken isn't.
Since this is maybe/ likely a bit harsh (and I'm trying to rid myself
Am 06.08.2015 17:49 schrieb Steve Litt:
Laurent Bercot wrote:
I have never said, am not saying, and probably never will say that
systemd is any good. It's not, and Lennart and Kay should go back to
engineering school,
:s/engineering school/kindergarten/
Hell no, that wouldn't be good for
On 07/08/2015 00:09, Rainer Weikusat wrote:
Since this is maybe/ likely a bit harsh
Not harsh, just unwilling to accept that I'm actually your ally and
not your enemy.
I'm not trying to replace Unix, because Unix is not broken - at least,
not as far as system startup is concerned. There *are
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
only a matter of time when they remove init s
36 matches
Mail list logo
