Re: how to remove libsystemd0 from a live-running debian desktop system
On Feb 17 2015, Alastair McKinstry <alastair.mckinstry@sceal.ie> wrote:
> On 17/02/2015 10:55, Vincent Bernat wrote:
>> ❦ 17 février 2015 10:18 GMT, Alastair McKinstry <alastair.mckinstry@sceal.ie> :
>>
>>>>> The breakage of compatibility of existing systems (e.g. with /usr on a
>>>>> separate partition) has left a sour taste. I spent a weekend repairing
>>>> systemd introduces no such breakage. Also, /usr on a separate partition
>>>> was partially broken even before systemd.
>>>>
>>> My system broke. It was fine, I did an upgrade -> jessie. It broke
>>> because of systemd and the fact I had /usr on a separate partition.
>> And no initrd? Mounting /usr is the job of the initrd.
>
> Examination after the fact showed that if I'd had the correct packages
> installed, it would have worked.
> So from a Debian perspective this was 'notabug'.
> (modules that were not needed day-to-day had been deleted by hand to
> make space on /.
> A broken initrd was then built during dist-upgrade. My fault).
>
> But this didn't change the user experience: a system broke badly during
> systemd upgrade due to local changes.
Aeh, what? What you describe above is about as much related to a systemd
upgrade is it is to an ntfs-3g upgrade. Anything that triggers an initrd
rebuild would have had this effect. Blaming systemd is absurd.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
Reply to: