Sure, although the proper way to test it would be to write a lot of data to the drive, issue an fsync, and cut power in the middle of the operation. Rinse and repeat a (few) hundred times for each drive.
There's a guy on btrfs' LKML (also the author of [0]) who is diligent enough to do these tests on much of the hardware he gets, and his experience does not sound good for consumer drives.
It's worthy of note that log-structured and copy-on-write filesystems (which I've seen described as two types of journaling) like btrfs and F2FS log data as part of their normal operation without any performance loss, so you always get a consistent view of the filesystem (barring bugs in the FS code or fsync-is-not-really-an-fsync treachery from your hardware).
This does not answer your question, but wouldn't it be easier to get a cheap UPS with enough battery life to get your machine through additional 5 minutes of uptime?
Although I've had problems with hardware hanging so completely that it does not respond to the reset button, and the only option is to cut power, so UPS does not provide full protection.
Journaling cannot guarantee data or filesystem integrity if your hardware is lying to you. If you send flush to an SSD and it reports "ok, your data is on the persistent storage", while actually keeping it in DRAM buffers (to get higher numbers on benchmarks), and your power goes down, shit ensues. This is surprisingly common behavior.
The main problem I have with it is it does not keep key combinations stable — if you press F → Esc → F → … (or Alt+F), it assigns different combinations for each link each time.
Don't forget a keyboard-driven navigation plugin for your browser, like vimium. I have a desktop PC and use my mouse maybe once or twice a day, mostly for JS-heavy crap (which also probably presents enormous problems for the blind folk).
Honest question: is there any reason for using RSA for new keys these days, if you are not working with extremely legacy systems? My ed25519 works fine with at least CentOS 7, and thankfully that's the oldest system I have to touch.
Maybe only if you want to store the key on a separate physical device, and it only supports RSA?
At least Indian authorities seem to be relatively open about the censorship. Here in Kazakhstan they simply block everything they want, taking down many "innocent" sites as collateral damage, and write it off as "temporary networking problems" and "works for me, what are you talking about?".
For the past week I've had numerous problems connecting to TLS directly, without using a VPN. I still update my system directly from a mirror to avoid wasting limited data on a remote VM, that's how I discovered it personally. I worry they're trying to implement something nefarious behind the scenes, again.
From glancing at the source code I believe this uses the same algorithm as df from coreutils. It outputs pretty much useless data for btrfs, which needs to be handled differently. See:
As much as I like to crap on nvidia, they have supported a relatively high quality Linux driver when it barely registered as a desktop platform. Hell, they even have a FreeBSD driver.
Why would you have a separate machine just for that? I thought one of the strongest points of PCs (as opposed to phones/game consoles) was their wide applicability to pretty much every task?
I was expecting you to say "I immediately mark it as spam". Do it, treat unsolicited newsletters like the spam they are. If enough people do this, it creates significant problems for the authors of such email.
>withdrawing over-the-counter paracetamol while continuing to allow over-the-counter ibuprofen
Paracetamol is not an NSAID (unlike ibuprofen) and has a lot less negative effect on my gastritis. There are not many painkillers available OTC which are not also NSAIDs and so don't destroy your stomach lining. I'd rather not develop stomach ulcers to prevent some random lunatic from gorging himself on paracetamol into the grave.
There's a guy on btrfs' LKML (also the author of [0]) who is diligent enough to do these tests on much of the hardware he gets, and his experience does not sound good for consumer drives.
[0]: https://github.com/Zygo/bees/