Linux: concerns over systemd adoption and Debian's decision to switch

Tue Oct 21 17:17:09 UTC 2014

I was actually not aware of this. I've been told that systemd also
includes fsck's functionality (or is planning to?). That just seems
absurd to me.

I didn't really have a strong opinion on either side of this yet. Seeing
the replies from other people here, though, and reading some more about
it, this seems to be a very bad idea.

The binary logs for example worry me, especially corruption issues:

http://www.reddit.com/r/linux/comments/1y6q0l/systemds_binary_logs_and_corruption/
https://bbs.archlinux.org/viewtopic.php?id=169966

On 21-10-2014 14:40, Valdis.Kletnieks at vt.edu wrote:
> On Tue, 21 Oct 2014 14:44:57 +0900, Randy Bush said:
>> systemd is insanity.  one would have hoped that deb and others would
>> know better.  sigh.
> It started as a replacement init system.  I suspected it had jumped
> the shark when it sprouted an entirely new DHCP and NTP service.  And this
> was confirmed when I saw this:
>
> "Leading up to this has been cursor rendering support, keyboard mapping
> support, screen renderer, DRM back-end, input interface, and dozens of other
> commits."
>
> http://www.phoronix.com/scan.php?page=news_item&px=MTgwNzQ
>
> When your init system is worrying about cursor rendering, you have truly
> fallen victim to severe feature bloat.  I guess Jamie Zawinski was right:
> "Every program attempts to expand until it can read mail."

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20141021/cecad154/attachment.sig>