Not quite

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Freproducible.archlinux...

For some degree. There is HWE stacks, which provide newer kernel/drivers for older LTS releases.

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwiki.ubuntu.com%2FKernel...

It only matters how long you can use your phone. If Apple does not put as big battery as competition, and loses in battery life because of that, is is not Apple who is winning.

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fbgr.com%2Ftech%2Fthe-galax...

It is in Gnome Advanced Configuration app (gnome-tweaks), which probably is not installed by default.

Can you please list all of those bazillion forks? Because I only know two: Mate and Cinnamon.

And that is not so many after all.

I would like to have an example of case where the debugging is harder in this kind of normal case?

For the some cases I have had, it actually felt easier to debug. Journalctl -b0 shows all entries after last boot, and changing number (-b-1) will show earlier boot. This way it was really easy to compare working boot with non-working one.

systemctl status {servicename} will show status of the service and gives instructions to check logs in case there is problem (even giving exact command line how to see the desired log).

Quite a lot of people are telling that debugging is harder, but from my experience, for average guy, systemd is easier to debug than traditional init.

I haven't seen any missing logs in either with any other init or with systemd. But actually, if there is missing logs on traditional init system, you would not even know it because there is no any kind of checks for log file integrity on. On systemd journal, you would know if the logs are corrupt or something is amiss, but at the end you probably could not do anything for it anyway so it is kind of moot point.

For more advanced user (if that user knows shell scripting) it is of course possible to read the traditional shell scripts and try to debug it that way, but for normal user it does not matter.

According to this (https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.strongtieinsurance.com%2Fcommon-reasons-road-accidents%2F) it is number second. If is still quite a lot.

It is still on discussions. There is EU wide proposal to get rid of time changes. Every country have option to select either time to stay on.
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.timeanddate.com%2Fne...

Here in Finland, it has not been yet decided which time is the one we stay on.

In Finland, we had poll about whether to stay on DST or winter time. Result was 52% in winter time and 48% in DST. Of course because this was a public poll results are only giving a direction, but it is nowhere near 99% vs 1%.

I myself really do not care. If we all go to DST, then slowly and gradually our wake-up hours will shift little bit later and later, until we see that when previously we were living in (for example) 7-22 wake-up hours, then after years of permanent DST wake-up hours shift for 8-23.

It really would not matter. People to tend to go to sleep too late anyway, and wake up with too little sleep.

It is more so that those older operating systems does not implement WPA2 correctly (eg. they do not support retransmission). Newer OSes (and ones which implement standard more tightly) are more vulnerable.

You're fucking kidding me?!?!?

You're using a study done before Y2K when Bill Clinton was President to justify what Gnome is doing with the GUI today?

It was response to earlier post which said that desktop was perfectly usable two decades ago. That study points out that no, it was not perfectly usable back then.

Well, I don't actually doubt the fanless part - I suppose most of the modern cpu's can run fanless - they just throttle quite a lot.... I just doubt that you can run it without heatsink.

Is that true? I really doubt that, E5-2679v4 CPU is 20-core 200W TDP cpu.

Also, its in totally different pricepoint - over $2500 USD, so I do not know where this "closest rival" comes from.

Network interface naming has nothing to do with systemd. Reason why your ethernet adapter was suddently named as enp0s19 is because of this: "udev supports a number of different naming schemes. The default is to assign fixed names based on firmware, topology, and location information. This has the advantage that the names are fully automatic, fully predictable, that they stay fixed even if hardware is added or removed".

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Faccess.redhat.com%2Fdocu...

Yeah, I actually realized now what is the issue.

If you run
>journalctl | less

You will get normal less pager with wordwrap

If you just run
> journalctl

You will get still paginated output, without wordwrap (not sure what this is using as pager, is this something built in?).

Finally
>journalctl --no-pager

Will show you plain output without pager.

Yeah, it seems that defaults are little bit strange, and I do not understand why there must be that default pager (without wordwrap) at all. And I don't know where the pager is choosen from, I do not have either PAGER or SYSTEMD_PAGER set (this is Ubuntu). And actually, setting pager does not seem to help