Yeah I remember those early days. KDE had a 1.0 version out in the late 90s, which was perfectly usable as a standalone desktop environment, while at the same time Gnome was little more than a panel with a foot. Early Gnome was an unholy mess and remained so until the late 2.x versions in the mid 2000s. Like how many window managers and file managers did they go through? I believe they even had Enlightenment as the default window manager for a while, and then there was that weird Ximian desktop phase.

On my QK80 mechanical keyboard I could do this:

echo 2 > /sys/module/hid_apple/parameters/fnmode

Maybe your keyboard driver has a similar parameter?

See my edit.

I don’t think that’s the case anymore.

I just checked, the time in the UEFI BIOS is in UTC, yet both Linux and Windows 10 display the local time correctly as an offset to UTC. I didn’t have to do anything special for that.

Edit:

So I looked a bit deeper into it, and this is apparently controlled by a registry key called RealTimeIsUniversal in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]. You can paste the text below in a .reg file and then import it to set the parameter:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
"RealTimeIsUniversal"=dword:00000001

I confirmed that this setting exists on my system, but I have no memory of ever manually setting this parameter. It’s documented in the Arch wiki though, so it’s possible that I did set it and forgot about it.

In any case, if you do a fresh Windows install and your time differs between Linux and Windows , this is what you should check.

Should probably also mention that his wife, Telsa Gwynne, was diagnosed with cancer around the time he retired and she sadly passed away in 2015.

tl;dr FrAgMeNtAtIon

There, saved you a click.

What’s a good usecase for TPM in Linux?

Probably not. There are no implementations that I’m aware of that work well on a Linux guest.

Ok, so you don’t know what FUD means.

You can disagree with the comment above, but it’s not “FUD”, it’s just criticism.

That’s just a meme. If you can follow some basic instructions, you can setup arch.

Yeah, I evaluated both when I chose this solution several years ago. Don’t ask me why I chose one over the other though, I don’t remember.

Desktop usage is almost always going to feel laggy in a VM because you don’t have a real GPU inside the VM and it will fallback to some non-accelerated framebuffer mode. There are some GPU virtualization solutions, for example QEMU has virgl that offers 3D acceleration, but in my experience it’s buggy/not ready and doesn’t offer near bare metal performance.

The only way to get near bare metal graphical performance in a VM is by using PCI pass through of an entire GPU, but that requires an extra GPU, is non-trivial to setup and comes with a lot of caveats.

I use deluge mainly because it can easily be run as a daemon inside of a docker container, so I can just let my torrents run unattended on my homeserver, and always protected by a VPN with killswitch.

On my desktop I use the GUI client to connect to the daemon and manage my torrents as if it were local.

It probably wasn’t such a concern back in 1971. I mean, even nowadays you still find programs where you can just add a login password to the command line.

I don’t think “substitute user” is the original meaning, and it’s more like a retroactively applied acronym.

Looking at various old Unix manpages, it said various things in the past. In the HP-UX documentation it even lists three different variants in the same man page: “switch user”, “set user” and “superuser”.

“superuser” is probably the original meaning, because that’s what it says in the Unix Manual 1st edition (1971): http://man.cat-v.org/unix-1st/1/su

NAME	su -- become privileged user
SYNOPSIS	su password
DESCRIPTION	su allows one to become the super--user, who has all sortsof marvelous powers. In order for su to do its magic, the user must pass as an argument a password. If the passwordis correct, su will execute the shell with the UID set to that of the super--user. To restore normal UID privileges,type an end--of--file to the super--user shell

I love Unix archeology :)

I’m blaming it for making it a pain in the ass to debug dependency problems and for having the confusing, non-intuitive, overly verbose and redundant syntax that probably caused the problem in the first place.

Like, who the hell can memorize all the subtle differences in behavior between After=, Requires=, Wants=, Requisite=, BindsTo=, PartOf=, UpHolds= and then all their “reverse” equivalents?

Everybody gangsta until A start job is running for ... (10s / 1min 30s)

Thanks for summarizing my feelings on systemd in a less inflammatory way than if I had written it myself.

I’ve found that most distributions have implemented it properly and for the most part it works quite well and stays out of my way, it’s only when for some reason you have to dive into the minutiae of a unit file and getting into all the dependencies and stuff that it gets annoying quickly.

Pretty much yeah