3 ms·
> hdparm --fwdownload-mode3 sk060202.ftd --yes-i-know-what-i-am-doing --please-destroy-my-drive /dev/sdb If nothing else, I certainly appreciate `hdparm`'s CLI
by fake-name 2y ago
> hdparm --fwdownload-mode3 sk060202.ftd --yes-i-know-what-i-am-doing --please-destroy-my-drive /dev/sdb
If nothing else, I certainly appreciate `hdparm`'s CLI flags
- 0xcde4c3db 2y agoDocumentation of this seems to have disappeared into the ether, but I'm reminded of the time that glxgears (or a distro package of it?) briefly turned off FPS output by default, with the argument to turn it on being something like --i-acknowledge-that-this-tool-is-not-a-benchmark Basically, people were complaining about "major regressions" in glxgears frame rates that were really just minor fluctuations in how long it took to clear and swap buffers, since glxgears does almost no actual rendering (by modern standards).
- Dwedit 2y agoHdparm's manual is amazing. "This is EXTREMELY DANGEROUS and will very likely cause massive loss of data. DO NOT USE THIS COMMAND." "VERY DANGEROUS, DON'T EVEN THINK ABOUT USING IT." "VERY DANGEROUS, DO NOT USE!!" "This command is EXTREMELY DANGEROUS and could destroy both the drive and all data on it. DO NOT USE THIS COMMAND." "EXCEPTIONALLY DANGEROUS. DO NOT USE THIS OPTION!!" "VERY DANGEROUS." "(DANGEROUS)" There's a reason why TvTropes lists the "hdparm" command under "Schmuck Bait".