I’m always hopeful, but there was another state/city in Germany (Munich I think?) that tried to do this a long time ago, then after 10 years of not being able to move entirely over, they moved back to MS, then I think they tried again. Really flip-flopped a lot. I think stuff like this needs to be more organic in its movement rather than big bangs and milestones. Just let it creep in and take over.

First UNIX was QNX, random free CD on a magazine.

First Linux was Mandrake 7.0, then moved to RedHat, then distro hopped for about…20-25 years so far I guess :-p

I feel selinux should be able to do something clever here, like it can manage/block port access.

Pro tip: -z, -j are not needed by tar anymore since many years, tar will autodetect what compression was used if your distro is anything remotely modern.

😵

Give this a try: https://unix.stackexchange.com/questions/543021/broken-bumblebee-on-debian-testing-crashes-with-ee-unw-get-proc-name-failed-n

What’s the advantage of this vs running it in a container? https://github.com/sickcodes/Docker-OSX

You dropped this ’

I wonder, what characters are allowed? $0 would be interesting, or even the fork-bomb classic.

This drove me up the wall. And, I hate to admit it, but I’ve let Apple win. I use Windoze for work so I’ve swapped @ and " to be the same as Apple UK, and if I run Linux I choose the Apple UK layout as well. It’s just…easier rather than having to reset my muscle memory every day.

OK, thanks.

I guess it’s worth confirming if it’s been a logout or a reboot as well. If you open a terminal and type “uptime” does the time match when you booted up or after you left it alone for a while?

Check the output of: dmesg -T and have a look through: /var/log/messages

I would be focussing on errors, warnings and/or terms like “reboot, shutdown, logout, timeout, idle, etc.” to try to narrow it down what is happening and when.

Without sounding rude, are you sure it’s at the login screen and not the unlock screen?

Thanks, you’re the best.

…Can someone share that emoji, please?

I’ll probably not use it until they have a CDKTF equivalent, but it’s good to see progress.

Not going to lie, I think I lost interest after the 3rd reference to “Nix” and there being no guide as to whether it means Unix-like, Nix (the plan9 fork), NixOS (Linux distro), Nix (the package manager) or something referred to as “The Nix Language”

Because UNIX Epoch starts 1970, not 1975 is why I mentioned it.

Wait, there’s a GNU Epoch as well?

I don’t tend to use awk in scripts as I do tend to do them in Python, but I do use awk on almost daily basis in one-liners.

Probably the most common thing for me is so I can read a config file without annoying comments and big line spaces.

grep -v "^#" krb5.conf | awk NF

Which version of stat do you have? I get the same blank result locally on ext4 and btrfs filesystems (not over nfs) using stat 8.30 on an rpi4 (raspbian, 5.10.103-v8+).

Seems to work fine with stat 8.32 on xfs on a spot instance I have, running Rocky 9 (5.14.0-362.13.1.el9_3.x86_64).

I thought there might be more info in the changelog: info coreutils aqstat invocationaq but I’m not seeing it.

That’s surprising, as I think the first Windows TCP/IP stack was ported over from BSD by Spider Systems (pretty sure that’s why it still has things like “/etc/hosts” - albeit under System32). Wonder if the bug was in BSD and never backported (cross ported?).