Oh no, how terrible!

Not a lawyer, but as far as I got it, the storing isn't the punishable part, the recording is.

You can't have security cameras filming public spaces (like the road in front of your house). Even if its dummies, as people couldn't tell the difference whether the camera actually films them or not.

Illegal in Germany. You may not record conversations, if you try to enter something like that as evidence you'll get punished as well.

I suspect there are many countries with laws like that, and if your phone actually disables the feature when you enter them or just let's you hang to dry...

My thought :)

Federal Republic of Germany, as opposed to the German Democratic Republic.

West and east

Well actshly, rm removes the inode, not the file. If it's still in use it'll stay on the disk until the last fd is closed.

• with most file systems that are usual on linux

Of course they won't, how are they gonna recruit kids for their rightwing batshitism otherwise

Würde nur Datingseiten per https nutzen.

You can lazy umount, which blocks new accesses and actually unmounts when it can

Extremely simplified:

Your file system consists of a whole lot of blocks to write data to. Let's say you have a block size of 512kB, so a 4MB file would span 8 blocks. A 3.7MB file would span 8 blocks, too, as the remaining space can't get used otherwise.

Now to get what file exists on which blocks, there's a large index table, consisting of a number of index nodes (shortened to inode). Each inode saves multiple data fields of a file, like its name, owner, creation data, and the files blocks.

If you link a file to a second name (hard link) a second inode will get created that points to the same blocks.

That's about it. Used to be important to chose the right inode size and count on filesystem creation for the average data you'll save on the filesystem, as inodes have a fixed count, and the index table takes disk space, too. Too many inodes and you waste space that you could use for precious data, too few inodes and you can't save new files even when you have free data blocks. With growing disk sizes people just went with massive indexes, who cares about a few wasted megs.

Modern filesystems (like ext3 and up) introduced journals, which complicate things.

"I'll get to it, eventually" would ruin the meme but be more fitting, in my opinion.

Had multiple occasions where people fought against filling disks and just couldn't see why. Well, that 10 gig log file you deleted two weeks ago? It's 20 gig now, and still being written to.

lsof shows stuff like that.

Yeah, we moved a couple years ago, and now have a built-in fridge, so it has a wood panel in front of the door. I want my whiteboard back :(

Nah, they just throw away the block markings, absolutely.

Overwriting a SSD is difficult as well, better encrypt the drive and trash the key when you decommission.

I placed a "real" small whiteboard in the kitchen. Its not as big and not as well placed as the fridge, but we make do...

I do use German key layout, as I'm used to that for decades.

And German number, currency, date, address formats, as the English are just whack

Aim for the knee

You used Solaris when cortana was already a thing? That's great! :D

My university ditched Solaris like 20 years ago. Still have fond memories of cde lol

Sounds funny, but it'll lead to people saying "look at those 4 years without a president where everything went to shit! We need strong leadership!'

The end key becomes ende. Over 30% increase!

You mean like in your kitchen? Too much metal, you'll damage your magnetron.

You could use thermite and melt it to a pulp. Dangerous as well, though.

Really, just encrypt. Your CPU has AES extensions, performance impact is negligible. Simple, clean, and a protection against involuntary decommission as well.