second

https://m.youtube.com/watch?v=rE1lIdtDs2g is a classic of the genre

Or use /* for the path so it globs to all directories under / whilst not triggering the logic which requires --no-preserve-root.

Lonnie Donegan - Rock Island Line

It takes 5 minutes to prepare but you leave it for 12 hours to rise.

You’re not, I like it too.

The aspect ratio of the thumbnails is closer to the aspect ratio of the screen, which makes sense to me.

Also until you reopen each tab, you don’t get a mini screenshot of it. I like the mini screenshots so I can see what the page was without having to read its title.

Originally, rm would merrily nuke your whole filesystem if you told it to. At some point, someone thought that was a pretty stupid default behaviour, so they added that flag to change the default to not nuke your entire filesystem. However, they made the change backwards compatible in case someone still needed the old behaviour. I can imagine in a container or throwaway environment, it might be vaguely reasonable to expect to be able the blat /.

See also:

Unix gives you just enough rope to hang yourself – and then a couple of more feet, just to be sure.

– Eric Allman

rm -rf / needs --no-preserve-root on GNU coreutils, I think.

I assume that’s to build from source.

The times I’ve installed GitLab it’s been a case of dnf install https://.... The rest gets dragged in automatically.

That’s a bit of an unfair comparison - that’s the GitLab instructions to install from source. Most people use a package (rpm, deb) to install GitLab.

The installation instructions for GitLab from prebuilt binaries is https://about.gitlab.com/install/, and that’s significantly shorter.

That said, I think for most home applications, GitLab is hugely overkill.