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.
You can lazy umount, which blocks new accesses and actually unmounts when it can
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
“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.
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.
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.
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
The end key becomes ende. Over 30% increase!
Aim for the knee
Don’t know what your mobile OS is, I set my Android to English and use HeliBoard for the keyboard app. It even remembers what app should get Swedish, German, English layout and word suggestions.
Dunno, isn’t logo older, with the whole frigging language translated?
When I started computering, there where no localised systems. When they started translating, the German was often misleading, incomplete, or just didn’t fit in the button or whatever. So I stuck with English. Somewhere along the line I switched to en_UK, though.
And yeah, in this day and age I have no clue how good the translations are, because I never checked them.
Yes, the clients (Desktop, Web, Browser, Mobile, CLI) are published by Bitwarden under GPL3 license, so you can always fork them.
Bitwarden could delete the repos, but the code is out there.
I have fiber in my basement and could book gbit. Upstream is still nerfed, currently I have 250mbits down, 50 up
Edit: disregard that, just checked with my ISP and apparently I have an old plan, and could book 1 gig symmetric. For thrice the cost, though
Over here breathalysers are admissible, but you can reject to use them. Police then has to decide wether to call a doctor to draw blood.
Switched from keepassxc to vaultwarden a while ago (mostly due to the horrible syncing experience, and to use the same password manager as my family so I could help out better).
It’s a selfhosted and open source version of the Bitwarden server, you’ll use the (open source) Bitwarden clients. So its all features of Bitwarden plus full transparency
When I gave a shit, I don’t give a shit about the toilet paper
Nice to meet you gay, I’m moved
Expenses. Have none when you can’t pay
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.