https://devuan.org/
Devuan will derive its own installer and package repositories from
Debian, modifying them where necessary, with the first goal of removing
systemd, still inheriting the Debian development workflow while
continuing it on a different path: free from bloat as a minimalist
On 11/29/2014 12:13 PM, Richard Pieri wrote:
https://devuan.org/
Devuan will derive its own installer and package repositories from
Debian, modifying them where necessary, with the first goal of
removing systemd, still inheriting the Debian development workflow
while continuing it on a
I don't think that what you ask for is possible. The systemd debate is
outside the realm of anything a suit is likely to understand, even if
you use an entire page.
On Sat, Nov 29, 2014 at 12:45 PM, Bill Horne b...@horne.net wrote:
On 11/29/2014 12:13 PM, Richard Pieri wrote:
I think that's the argument. Simple and proven vs. Complicated and new.
Tim
Sent from my Android phone using TouchDown (www.nitrodesk.com)
-Original Message-
From: Shirley Márquez Dúlcey [m...@buttery.org]
Received: Saturday, 29 Nov 2014, 12:50
To: Bill Horne [b...@horne.net]
CC: BLU
On 11/29/2014 12:49 PM, Shirley Márquez Dúlcey wrote:
I don't think that what you ask for is possible. The systemd debate is
outside the realm of anything a suit is likely to understand, even if
you use an entire page.
Nah... Bill isn't looking for an explanation. He's looking for a
The suit explanation has to focus on business impact, not technical details.
use phrases like:
risk of disruption proven compatibility increased stability
total uptime maintenance cost
(or their inverses)
___
Discuss mailing list
Discuss@blu.org
On 11/29/2014 12:45 PM, Bill Horne wrote:
Someone, please give me a one-sentence answer I can recite to any suit
who asks me what the difference is.
I can't use words like systemd: their eyes will glaze over. TIA.
Tell them you can tweak old sys-v scripts if they break and/or you need
them
On 11/29/2014 1:27 PM, Betsy Schwartz wrote:
The suit explanation has to focus on business impact, not technical details.
use phrases like:
risk of disruption proven compatibility increased stability
total uptime maintenance cost
(or their inverses)
Betsy,
Thanks, that's a good point.
Of
On 11/29/2014 12:49 PM, Shirley Márquez Dúlcey wrote:
I don't think that what you ask for is possible. The systemd debate is
outside the realm of anything a suit is likely to understand, even if
you use an entire page.
That's the problem: I can't try to explain why I might recommend one
From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss-
bounces+blu=nedharvey@blu.org] On Behalf Of Bill Horne
Someone, please give me a one-sentence answer I can recite to any suit
who asks me what the difference is.
Nobody will ask unless they already have an opinion about
From: Edward Ned Harvey (blu)
The arguments about preventing downtime are bunk, unless somebody
shows that systemd causes downtime. Which it doesn't.
There's a reason it's difficult to come up with a concrete argument against
systemd.
___
Discuss
On 11/29/2014 7:50 PM, Edward Ned Harvey (blu) wrote:
The arguments about preventing downtime are bunk, unless somebody
shows that systemd causes downtime. Which it doesn't.
Last major update to my home box, systemd broke Samba. No changes were
made to the Samba configuration; systemd simply
On Sun, 2014-11-30 at 00:52 +, Edward Ned Harvey (blu) wrote:
The arguments about preventing downtime are bunk, unless somebody
shows that systemd causes downtime. Which it doesn't.
There's a reason it's difficult to come up with a concrete argument
against systemd.
YALS - Yet
13 matches
Mail list logo
