Spyke

Replies

memes

Comment on

*Permanently Deleted*

Reply in thread

Girl = neutral (das Mädchen)

No idea why lol.

Mädchen is a diminutive, and all diminutives are grammatically neutral.

It's the same in Dutch btw, and my girlfriend who is learning Dutch is frequently abusing this as a cheat code: whenever she doesn't know the gender of a word, she'll just use the diminutive and it will automatically be neutral.

Comment on

Pornhub Sues Texas Over Age Verification Law

Reply in thread

Is it really that bad if kids see a bit of porn? Like really? I grew up before the internet, but even in my day porn mags and VHS tapes got passed around when I was a teenager. Kids are always going to be curious.

Even so on the internet there are much worse things than porn that are harmful for the development of children. There are various groups of questionable morality like incels, or other mysogynistic groups, alt right stuff like neonazis, christofascists, climate deniers, ... If I had children, I would be much more concerned about them falling into one of those ideological traps than them seeing some titties. Hell, even TikTok is probably more harmful for giving them a dopamine addiction and an increasingly short attention span.

So to me, it seems a bit weird to single out porn. It feels like a convenient scapegoat for parents who don't want to spend time raising their kids and paying attention to what they are looking at on the internet.

Comment on

Windows vs Linux

Reply in thread

Deleting your efi partition doesn't brick your board. It just makes your disk unbootable, but you can always install another operating system and create a new efi partition.

I think you're confusing with the special efivarfs file system that is mounted under /sys/firmware/efi/efivars. If you delete stuff under there, you're apparently going to have a bad time, because it directly deletes variables in your UEFI firmware which can prevent your system to POST.

Comment on

Got it running, now how do I back it up?

As a general rule, you should always keep in mind that you're not really looking for a backup solution but rather a restore solution. So think about what you would like to be able to restore, and how you would accomplish that.

For my own use for example, I see very little value in backing up docker containers itself. They're supposed to be ephemeral and easily recreated with build scripts, so I don't use docker save or anything, I just make sure that the build code is safely tucked away in a git repository, which itself is backed up of course. In fact I have a weekly job that tears down and rebuilds all my containers, so my build code is tested and my containers are always up-to-date.

The actual data is in the volumes, so it just lives on a filesystem somewhere. I make sure to have a filesystem backup of that. For data that's in use and which may give inconsistency issues, there are several solutions:

  • docker stop your containers, create simple filesystem backup, docker start your containers.
  • Do an LVM level snapshot of the filesystem where your volumes live, and back up the snapshot.
  • The same but with a btrfs snapshot (I have no experience with this, all my servers just use ext4)
  • If it's something like a database, you can often export with database specific tools that ensure consistency (e.g. pg_dump, mongodump, mysqldump, ... ), and then backup the resulting dump file.
  • Most virtualization software have functionality that lets you to take snapshots of whole virtual disk images

As for the OS itself, I guess it depends on how much configuration and tweaking you have done to it and how easy it would be to recreate the whole thing. In case of a complete disaster, I intend to just spin up a new VM, reinstall docker, restore my volumes and then build and spin up my containers. Nevertheless, I still do a full filesystem backup of / and /home as well. I don't intend to use this to recover from a complete disaster, but it can be useful to recover specific files from accidental file deletions.

linux

Comment on

I F*cked up and I need help.

Reply in thread

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 :)