Rainer Weikusat rainerweiku...@virginmedia.com 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
Rainer Weikusat rainerweiku...@virginmedia.com writes:
Laurent Bercot ska-de...@skarnet.org 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
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
purged PA
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
Laurent Bercot ska-de...@skarnet.org 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
Am 06.08.2015 17:49 schrieb Steve Litt:
Laurent Bercot ska-de...@skarnet.org 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
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
Laurent Bercot ska-de...@skarnet.org 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
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
.. 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
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 is
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
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
Alexey Rochev equ...@gmail.com 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
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 aren't
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: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
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
On Thu, 06 Aug 2015 10:28:47 +0100
Rainer Weikusat rainerweiku...@virginmedia.com 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
On Thu, 6 Aug 2015 16:41:38 +0200
Laurent Bercot ska-de...@skarnet.org 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
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
21 matches
Mail list logo
