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

Re: how to remove libsystemd0 from a live-running debian desktop system



On 02/17/2015 11:49 AM, The Wanderer wrote:
You only harm your case by misusing and confusing terminology in that
way.

>russ writes:
>
>>Alas, the resulting distribution is still hopelessly compromised by
>>the NSA, who might be even worse than Lennart Poettering.  To see
>>how deep the tendrils of US government infiltration go, just try
>>removing libselinux1, and marvel at how much concerted malevolent
>>effort has gone into destroying your freedom.
>
>and:
>
>>Or, alternately, you could research how and why one would use
>>shared libraries in a binary distribution to support optional
>>features.  But that's boring, prosaic, and nowhere near as much fun
>>to write about.
>
>ahhh russ - good maaan:)   here we have a hint of a possible
>solution, one where i'm going to need to speak to the systemd team
>for a feature request / design decision (and can i ask you and anyone
>else to do the same?).  you've hit on what i believe is*the*  perfect
>and acceptable decision that is hinted at by the ridiculousness of
>the drastic demonstration that i made [to modify and recompile debian
>packages]. of*course*  libsystemd0 should be dynamically loaded, and
>the userspace applications make the decision*at runtime*  as to what
>to do!
libsystemd0_is_  dynamically loaded, precisely so that userspace
applications can make the decision at runtime as to what to do.

What about dynamically linked? Maybe Luke means dynamic linking (necessitating dynamic loading) instead?

--
Nate


Reply to: