[175397] in North American Network Operators' Group
Re: Linux: concerns over systemd adoption and Debian's decision to
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Oct 21 15:59:20 2014
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <54469515.5020104@lugosys.com>
Date: Tue, 21 Oct 2014 12:55:02 -0700
To: "Israel G. Lugo" <israel.lugo@lugosys.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Wait=85 Let me see if I understand this correctly=85
1. Move fsck functionality into systemd
2. Have it generate opaque binary logs
3. If your filesystem is corrupted in a way that systems can=92t =
repair, you can=92t even read the logs of what systemd saw or did?
Yeah, that sounds like a very definite =93bad thing=94.
Owen
On Oct 21, 2014, at 10:17 AM, Israel G. Lugo <israel.lugo@lugosys.com> =
wrote:
> 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.
>=20
> 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.
>=20
> The binary logs for example worry me, especially corruption issues:
>=20
> =
http://www.reddit.com/r/linux/comments/1y6q0l/systemds_binary_logs_and_cor=
ruption/
> https://bbs.archlinux.org/viewtopic.php?id=3D169966
>=20
>=20
>=20
> On 21-10-2014 14:40, Valdis.Kletnieks@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:
>>=20
>> "Leading up to this has been cursor rendering support, keyboard =
mapping
>> support, screen renderer, DRM back-end, input interface, and dozens =
of other
>> commits."
>>=20
>> http://www.phoronix.com/scan.php?page=3Dnews_item&px=3DMTgwNzQ
>>=20
>> 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."
>=20
>=20
