systemd according to Luke Smith

[rasat]

This thread doesn't lead anywhere when users pull selected sentences out of the content to support their opinion.

[bobbee]

Luke Smith point that people are just uninformed haters, or the argument that, some give is that people are crazy, nothing like that would ever happen. Or somebody would see it and blow the whistle.

These are variations of the same old thing.

But of course the alarmists for the most part always been right, The Riichard Stallman's, Edward Snowden's, and William Binney's, have only confirmed what others what regular alarmists were worried about.

I will reply with one of Luke Smith's own videos.

https://www.youtube.com/watch?v=btHano6wHgA

In the video, He says straight out that he is not that ethical, and the only reason that he uses free software is because it is better, not because he is ethical.
Not because he has principals.

My position is different from Luke's position is that I use free software on principal And in many cases I use it over software that in some cases is better.

I get that for many, the ethics don't come into the picture.

I asked women, if a man gave you a diamond, but you knew it was a blood diamond (where people were killed to get the diamonds), would it matter to you?
I have never gotten an answer, just hmm, that is a good question.

Truth is, most never ask where that diamond came from.

But I am happy that there are some ethical people in the world or we would never have the society that we have.

[Artim]

Pardon my ignorance, but what was wrong with PulseAudio? Was there something that was better than PulseAudio that was in use before?

Good ol' ALSA was fine, and less of a resource hog than PulseAudio, which was buggy at first, and actually still Beta when Ubuntu first foisted it on their users. It didn't happen in Debian Stable until it was pretty much bug-free and well-tested.

[skidoo]

there is no longer a fullstop; however, I may be wrong about the year, might have been earlier.
The point is, I waited over 5 minutes, applied the suggested commands but systemd remained adamant and unyielding.
I am relieved if that particular gotcha has been corrected. At the time I filed the bug report it had not.

Thanks for corroborating, first-hand, the "pain point" I mentioned. I presented it as a sole example of how any of these Tubertalkers could easily find such examples if they bothered (you know, "background research" prior to professing to be authoritative speakers) to visit the user forums of any now systemd-encumbered linux distribution.

Thanks also for the factchecking & reporting that a 90sec timeout is now the (Debian configured?) default

[skidoo]

Links:
http://without-systemd.org/wiki/index.p ... stallation
http://without-systemd.org/wiki/index.p ... variant.29
http://without-systemd.org/wiki/index.p ... stallation

okay, I "nuked" the content of those pages (didn't test whether kriv has wiki page deletion privileges)

contents of this page were more than a year old and, reputely, were no longer accurate.
(still available via the "history" of this page if you care to review them)

Please repost a known/tested accurate set of instructions here.

If anyone discovers additional inaccuracies, post here or send me a PM.
specialPages}}}allPages may still find one or two others that are currently "unlinked" (per the "what links here" info)

[JayM]

Luke mentions in the video that he's only been using Linux for two years, yet he deems it necessary to make a selfie video giving his two cents worth on the systemd controversy as though he's some sort of authority. Why? He seems very full of himself, especially for a newb. I tried to ignore this and pay attention to the content in case he actually had something to contribute and I learned anything useful, but it was pretty much just "hatters gotta hate", Nobody likes change" and "boomers are sticks-in-the-mud." I liked the woods he was strolling in though: pretty country, wherever it is.

[AK-47]

but my main operating system is OpenBSD

I don't really like pre-configured distributions, I prefer a tabula rasa which I can configure myself.

I also use OpenBSD, and if it could run Wine and if vmm could be used to run full-blown VMs with Windows or something on it, I would probably not be using MX Linux. My point is though, that your advice is almost impossible to follow unless you end up being a hermit.

My point was that it is not possible to tamper with the systemd journal without alerting the administrator.

Anybody who manages to compromise a system will want to doctor the logs to conceal their malfeasance — this is possible with syslogd but not possible with the journal, which is a major advantage of the binary format.

And likewise for syslogd. You have to be root to write to the files in /var/log anyway. There's no intrinsic advantage in security of a binary format over a regular text format in this case, it has exactly the same security concerns as any regular file would.

The systemd journal records everything, syslogd doesn't record everything and requires several other logging services to provide full coverage.

That's quite a good setup if you have the journal record the stuff from syslog() as well. At least it's all in the one place then.

The systemd journal collates all the logs and offers an interface by which to filter the results with a variety of methods.

For example, syslogd lacks monotonic or timezone-based timestamps whereas with systemd I can do this:

Code: Select all

shinken:~$ journalctl -u systemd-networkd --since "3 hours ago" --no-p
-- Logs begin at Sun 2019-05-12 08:34:31 BST, end at Sun 2019-05-12 14:26:05 BST. --
May 12 12:20:08 shinken systemd-networkd[355]: wlp2s0: Lost carrier
May 12 12:20:08 shinken systemd-networkd[355]: wlp2s0: DHCP lease lost
May 12 12:20:11 shinken systemd-networkd[355]: wlp2s0: Gained carrier
May 12 12:20:11 shinken systemd-networkd[355]: wlp2s0: DHCPv4 address 192.168.1.212/24 via 192.168.1.254
May 12 12:20:11 shinken systemd-networkd[355]: wlp2s0: Configured
shinken:~$

Neat, eh?

Hopefully Lennart was smart enough to store them all as GMT and you can view them in the local time zone.

I was responding to the allegation of a "fullstop" and the suggestion that the system could not boot, which are both nonsense.

And the timeout can be reduced by editing DefaultTimeout{Start,Stop}Sec /etc/systemd/system.conf

While you're technically right, it's still a ridiculous situation that wasn't there before.

Well I have actually submitted an issue to the systemd team myself I was very pleased with how Lennart dealt with it:

https://github.com/systemd/systemd/issues/6684

I guess each to their own experience, but that still doesn't dismiss cases where users have been blamed for problems developers caused. Honestly I have yet to make up my mind about Lennart, and I'm not keen on jumping to conclusions about him just because everyone else has.

[Head_on_a_Stick]

I also use OpenBSD, and if it could run Wine and if vmm could be used to run full-blown VMs with Windows or something on it

I can't see Windows ever being supported under vmm(4) but I have Debian & Arch running nicely:

https://forum.archlabslinux.com/t/may-2 ... ad/3202/54

My point is though, that your advice is almost impossible to follow unless you end up being a hermit.

That advice was specifically about trusting anything I post — I am horrified by the thought that people might take my words as the gospel truth and I would much rather they think for themselves and seek to independently verify anything I may claim.

Hopefully Lennart was smart enough to store them all as GMT and you can view them in the local time zone.

The journal records timestamps in µseconds from epoch UTC and converts them to the local timezone, as can be seen from the BST (British Summer Time) zone in my posted code snippit.

While you're technically right, it's still a ridiculous situation that wasn't there before.

It's not ridiculous at all, I think it's a useful feature.

Consider this: under sysvinit the user would be blissfully unaware that their swap wasn't working until their system ground to a halt under an intensive workload...

[sunrat]

While you're technically right, it's still a ridiculous situation that wasn't there before.

It's not ridiculous at all, I think it's a useful feature.

Consider this: under sysvinit the user would be blissfully unaware that their swap wasn't working until their system ground to a halt under an intensive workload...

It certainly is a useful feature. A stall during boot is a sure sign that I should look at the journal to find out what the issue is and attempt to fix it.
It's not systemd's fault that another distro's installer reformatted a pre-existing swap file.

[Richard]

Well, at least most installers nowadays,
ask before reformatting the swap area. :)