Post 2861860 by LaH@mastodon.host
(DIR) More posts by LaH@mastodon.host
(DIR) Post #2847075 by gled@mastodon.host
2019-01-10T22:51:36Z
3 likes, 6 repeats
CVE-2018-16864 : exploitable since 2016CVE-2018-16865 : exploitable since 2013CVE-2018-16866 : exploitable since 2015 ( but fixed by mistake on 08/2018 )So:- brick PC bugs ( EFI erase ) ✔️- Many account of unbootable machines after an upgrade: ✔️ - Uncountable vulns since years ✔️ Seriously, what is gonna take for distro to finally put back systemdD(isaster) to the dump trash it belongs ??Oh, and any linux distro lead willing to share the huge hush money they must have won to accept that utter shitty piece of trash in the first place ?I don't see any other reasons now...
(DIR) Post #2848068 by dtluna@leftlibertarian.club
2019-01-10T23:28:08.774132Z
0 likes, 0 repeats
@gled time to migrate to Void I guess
(DIR) Post #2859379 by Ajz@mastodon.nl
2019-01-10T23:37:58Z
0 likes, 0 repeats
@gled There are still Linux distributions that are not using Systemd, like VoidLinux, Gentoo and Devuan. I noticed that newer Systemd versions are also handle the DNS setting for /etc/resolv.conf - an unpleasant development. Is there a comprehensive list of Linux distributions not using Systemd ? #systemd #linux Just read that there's several packages "depending" on Systemd : https://wiki.gentoo.org/wiki/Gentoo_Without_systemd
(DIR) Post #2859380 by gled@mastodon.host
2019-01-11T01:15:15Z
0 likes, 0 repeats
@Ajz artix too for the arch users ;)Systemd is unpleasant whatever angle you look at... got rid of it as soon as it became default, but still... ( yes you can also sysV on debian... just be prepared to ship your own /etc/init.d with your config mgmt )...
(DIR) Post #2859381 by Wolf480pl@niu.moe
2019-01-11T08:56:18Z
0 likes, 0 repeats
@gled @Ajz I'm not a fan of systemd either, but from my experience, sysvinit with LSB init scripts was even worse.Fortunately, even if you use systemd, you don't have to use systemd-resolved, systemd-networkd, etc. which are just incompetent scope creep.I think we should move beyond systemd, but going back to sysvinit with shell scripts is IMO not an answer.
(DIR) Post #2861860 by LaH@mastodon.host
2019-01-11T10:46:03Z
0 likes, 0 repeats
@Wolf480pl @gled @Ajz On top of everything else - ubuntus startup was pretty nice.
(DIR) Post #2861934 by Wolf480pl@niu.moe
2019-01-11T10:51:23Z
0 likes, 0 repeats
@LaH @gled @Ajz >ubuntu>authors of upstartnooooo...!
(DIR) Post #2874644 by Ajz@mastodon.nl
2019-01-11T19:27:40Z
0 likes, 0 repeats
@Wolf480pl @gled OpenRC seems pretty fine to me. https://en.wikipedia.org/wiki/OpenRC "OpenRC is the default init system of TrueOS, Gentoo, Alpine Linux, Hyperbola GNU/Linux-libre, Parabola GNU/Linux-libre, Artix Linux and other unix-like systems, while some others like Devuan offer it as an option." #systemd #openrc #sysvinit
(DIR) Post #2905302 by nicktux@mastodon.host
2019-01-12T17:29:30Z
1 likes, 3 repeats
Recently I upgraded my home server from 16.04 to 18.04. I spent almost 2 hours to find out what the fuck is going on with the network. The solution came when I disabled systemd-networkd and systemd-resolved and installed resolvconf.