[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Who's locking down the code?



Andrew McGlashan wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 26/10/2014 10:24 PM, Laurent Bigonville wrote:
Andrew McGlashan wrote:
That is 100% true, I couldn't give a rats if it is PID1 or not.  It IS
systemd, that's more than enough for me to want it OUT -- it's a
cancer that is spreading and it needs to be eradicated *before* it is
nigh impossible.
It is an habit in debian to compile the packages with as many options
as possible as long as it's not adding pile of new dependencies or
causing issues to the other packages in the archive.

IMHO, if you have the (non-technical?) requirement to not have any
systemd component on your system, you'll have to either start building
your own packages (you can have a look at apt-build) and maybe propose
sensible patches to make it easier for the debian users to opt-out when
rebuilding packages. Or switch to a distribution that allows you to
select which components are enabled at build time.
You are completely missing the point.  It is not technical, nor
political.  Two main developers cause significant concern about systemd
in particular and also what systemd is in itself brings other concerns
- -- the attack surface/risk also comes in to play.

One lead developer was responsible for the /mess/ that many people
believe to be ... Pulse Audio.... his *vision* for systemd is all about
"Poettering: Revisiting how we put together Linux systems" [1].  Another
developer's code won't even be accepted by Linus as the developer has
been found to be untrustworthy to Linus.

These reasons alone are quite significant and I don't want any of the
systems that I maintain being effected by these risks.


The term you're looking for is "operational risk" - which is also my main problem


--
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


Reply to: