ProTip: the Ubuntu version number includes the year and month of release. 26.04 will be released in April 2026. 26.10 in October 2026.

What they’ll do when they hit 2100 is left as a rollover issue for the next poor sod.

When I did events, I’d wear two pairs of socks, thin pair against my feet, then thick pair over the top of that.

I’ve also used moulded sole inserts from time to time.

In the vast majority of operating systems the person who installs the system is by default the highest privileged user, in the case of some of those systems, that user is called root.

However, the word root is also used to describe the basis of several file systems.

No.

Secure boot is about trusting which (signed) software is running.

On a positive note, a Dev responded to that post indicating that the behaviour of the platform is being reviewed.

See: https://lemmy.radio/post/10006706

WfW 3.1

This is excellent and important. It also serves to highlight that registrars are making an absolute fortune off the back of this effort.

The consortium clearly has too much money.

It means your coffee pod machine just came online and the coffee is currently spewing from the spout … probably.

In Australia:

https://reebelo.com.au/

Between the clickbait, YouTube “enhancements”, exploding AI slop videos and the atrocious search facility, the platform is rapidly becoming completely unusable for finding relevant information when you’re looking for answers.

As an entertainment platform it’s forcing creators to make long form content and making viewers sit through more and more low quality content.

It’s evolving, but I’m pretty sure it’s heading towards extinction, rather than greatness.

Embrace, Extend, Extinguish (Exterminate)

https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

It uses a security feature of Linux called cgroups or control groups to limit access to resources at a kernel level.

It’s used all over the place, including as the basis of Docker.

https://en.wikipedia.org/wiki/Cgroups

Wait until you see our dropbears. .

There’s a common but persistent misconception that Docker is like running a virtual machine. This is understandable but incorrect.

A better way to think of it is as a security wrapper around an untrusted process.

If you look at your running processes whilst a container is running, you’ll see the processes inside the container running on your “host” machine - remember, it’s not a host - guest situation.

There is no relationship between the user inside the container, unless you start mapping the UID and GID.

The only exception to this is the root user which shares the UID/GID with the actual root user.

See: https://www.howtogeek.com/devops/why-processes-in-docker-containers-shouldnt-run-as-root/

Edit: I suspect, but don’t know for sure, that the root user inside the container is actually the same user as the one running the Docker process, which is typically the root user on the “host”.

1. The Docker container should change the user to an internal one (created by the build stage) and the process should run as that user.
2. The uid and gid can be specified at runtime.

See: https://www.docker.com/blog/understanding-the-docker-user-instruction/

Stayin’ Alive - Bee Gees

… and this is why we use YYYY-MM-DD as the date format.

Did you actually read the article you posted?

Not in the Philippines, but what is now Indonesia.