[sf-lug] systemd and memory corruption...

[Rick Moen]

Correcting typo, in case it wasn't obvious:

> Sure enough, there were a couple of interesting follow-ups, e.g.,
> Michael P. commented on the core systemd init's carefree assumption
> that the running init must be system _without checking_ that this was
                                ^^^^^^ 'systemd'
> true, leading to 'all hell breaking loose' when the newly arrived
> systemd software shot PID#1 (SysVInit) in the head and took its place
> as PID#1 (grimly amusing to contemplate, albeit ghastly).



And, on another note:

> The only other comment was Ken Shaffer saying a day later tat Ubuntu had
                                                             ^
> security patces out -- but nobody went for the obvious takeaway.
               ^

My laptop's aitch key has become sticky.  Sometimes I notice and fix the
dropped keystrokes; sometimes I don't.