Linux greybeards release beta of systemd-free Debian fork

Post by chris_wot » Sat, Apr 30, 2016, 10:20 PM UTC

cm3 wrote: post #130

chris_wot wrote: post #126

Earlier quoted context omitted.

Actually, that's not true. I've had situations where my configurations broke between major releases of Ubuntu. I reported the issue and eventually it got resolved (no idea how I'm afraid), but whatever the issue for me it must have been an edge case as it wasn't widely reported. That seems to be the case for you as well. You have my sympathies, it's most frustrating when it occurs.

> I reported the issue and eventually it got resolved (no idea how I'm afraid), but whatever the issue for me it must have been an edge case as it wasn't widely reported. Recently there have been major regressions in the kernel due to DRM atomic modesetting with bug reports with many confirmations and zero action from the maintainers while not being able to go past kernel 4.1 which is fortunately one of the long-term…

Post by cm3 » Sat, Apr 30, 2016, 10:30 PM UTC

makomk wrote: post #113

cm3 wrote: post #17

One major problem with systemd is that beta software is released as stable and incorporated in distros. I've just realized that systemd-coredumpd is used to save crashes in the journal and write the files somewhere to /var. This has the problem that I have to vacuum or nuke the journal if I want to remove knowledge of past crashes because coredumpctl tool has no delete command. And coredumpctl hard-codes GDB as the d…

Same thing with Lennart's previous project PulseAudio which also has no real stable releases and basically relies on distros to try and take the beta-quality upstream releases and turn them into something that actually works reliably. (My favorite was the PulseAudio release that shipped with a change that was literally incomplete, changing the interal resampling API without changing all the resamplers affected. Crash…

Post by bpchaps » Sat, Apr 30, 2016, 10:37 PM UTC

chris_wot wrote: post #111

bpchaps wrote: post #91

Earlier quoted context omitted.

You must have a machine built for it, since I've had tons and tons of niggling little issues with systemd. Random, unnamed services sometimes fail to start or shutdown. One of systemd's big claim to awesomeness is that the start scripts run simultaneously, yet that's all thrown out the window when "Attempting to start, attempt 55 1m30s remaining" bullshit happens constantly and randomly, without enough information to…

Try installing syslogd then in journald.conf you just change storage to 1 and ForwardToSyslog to 1. That should hopefully get your old text based logs back.

Post by ktRolster » Sat, Apr 30, 2016, 11:07 PM UTC

nine_k wrote: post #24

ktRolster wrote: post #21

Earlier quoted context omitted.

Indeed, trying to get a full understanding of systemd is not easy, it's so large. It's like trying to understand a large piece of corporate software.

Also, the point of switching and studying is not clear. If all you need is service startup and keeping up, a few more polished tools exist with a dramatically ssmaller footprint.

Post by chronid » Sat, Apr 30, 2016, 11:46 PM UTC

chris_wot wrote: post #120

gkya wrote: post #116

Earlier quoted context omitted.

Why waste all that effort of maintaining forks when it can be avoided? Systemd folks are being hostile to the wider community of Linux users with that.

You don't need to - there shouldn't be anything that stops other init systems from using it.