Freaky

37 ms·

181.
by Freaky 11y ago
> If all models are identical and have been purchased at the same time, one would expect that the same firmware will allocate the same writes to the same cells Not really, you'd expect them to diverge over time as the cells aren&#x2
182.
by Freaky 11y ago
> Physical drives fail due to physical reasons, but SSDs fail for logical reasons. HDD's also have a long and distinguished history of nasty firmware bugs, and this is only going to get worse as things like drive-managed SMR and hyb
183.
by Freaky 11y ago
> As if both drives do exactly the same writes at the same time, chances are they will fail at the same time. You mean due to exhausting their endurance? This is something you monitor, you should have plenty of time to replace the drive
184.
by Freaky 11y ago
curl -Ro does, however.
185.
by Freaky 11y ago
> The reason is that when ZFS detects corruption, it'll lock down the whole fs... and prevent reading/recovery data from it Depends on what exactly is corrupt, but for file corruption it's generally just a case of warnings
186.
by Freaky 11y ago
Meanwhile fsck on a traditional filesystem will gleefully mangle data that's actually fine in face of transient corruptions. I've had this happen more than once, both with bad RAM and bad IO controllers - previously fine static da
187.
by Freaky 11y ago
As mentioned elsewhere in the thread, this isn't a "you must", this is a "you might as well". Timing attacks depend on an attacker having control over the hash being compared (e.g. they have a HMAC in a cookie they&
188.
by Freaky 11y ago
> base64_encode(hash('sha384', $password, true)) > ... > The above construction may invite theoretical concerns about entropy reduction (i.e. 72 characters of raw binary without any NUL bytes comes out to about 573 bits o
189.
by Freaky 11y ago
Just because I want a less bright background for reading text doesn't mean I want my monitor to be incapable of displaying a bright white - it's not only used for reading text.
190.
by Freaky 11y ago
Also: https://www.dragonflybsd.org/cgi/web-man?command=sys_checkpo...
191.
by Freaky 11y ago
It's notable that the Solaris unexec() implementation[1] is basically a thin wrapper around dldump()[2]. 1: http://git.savannah.gnu.org/cgit/emacs.git/tree/src/unexsol.... 2: https://docs
192.
by Freaky 11y ago
Losing to a Forgotten Beast made out of vomit and pus doesn't sound quite as fun in real life :(
193.
by Freaky 11y ago
The cvsweb links are semi-broken. Relevant SVN commit: http://v4.freshbsd.org/commit/freebsd/src/38520
194.
by Freaky 11y ago
You can use a Yubikey NEO to handle key authentication on your computer's behalf: https://blog.habets.se/2013/02/GPG-and-SSH-with-Yubikey-NEO
195.
by Freaky 11y ago
64-bit is very strongly recommended, but it does work on 32-bit with tuning: https://wiki.freebsd.org/ZFSTuningGuide
196.
by Freaky 11y ago
I wouldn't expect a passphrase that long to be particularly entropy-dense - quite the opposite really. Some people do things like pick phrases from Hamlet and stuff some numbers on the end, so truncating them would seriously compromis
197.
by Freaky 11y ago
> imposing max lengths .. ends up hurting people In that case you'll want to pre-hash your BCrypt-encoded passwords, otherwise you'll be imposing a silent 72 character limit. Remember to encode the hashes, since BCrypt also sil
198.
by Freaky 11y ago
This is why ABX testing is so big in lossy audio circles. People can and do demonstrate their ability to distinguish between lossy and lossless encodings with certain samples in double-blind tests, at all sorts of bitrates. I've done
199.
by Freaky 11y ago
LHA and LZX were the popular pair when my Amiga days came to an end. Being a commercial product the latter kind of occupied a similar position RAR does on Windows. Microsoft ended up adopting LZX for things like CAB and CHM files.
200.
by Freaky 11y ago
You're also describing everyone else's experience: > Really at 320kps you are entering the realm of fantasy if you think you can hear any difference. It depends on the encoder, the track, your equipment, and how good you are at
201.
by Freaky 11y ago
I'm fairly sure bsdtar had automatic compression detection before GNU tar did. Been the default on FreeBSD since version 5.3 (2004). Also works with non-tar formats like Zip, RAR and 7z: https://www.freebsd.org/cgi&#x2
202.
by Freaky 11y ago
I.. would probably have done that before concluding I didn't have any need for it. Even just do a quick one-off mcelog run to see what events have happened recently - you don't have to do some big statistical analysis. I'd e
203.
by Freaky 11y ago
I've had plenty of corrupt JPGs - they're certainly noticable since a single error tends to mess up an entire macroblock, often even the entire rest of the image. Was fun finding a bunch of my own photos like that. Luckily that w
204.
by Freaky 11y ago
> "statistically speaking, most computers in the world do not use ECC". How can both of these things be true? ... most computers aren't particularly reliable. I'm curious - are you not monitoring or at least keeping a
205.
by Freaky 11y ago
You'd probably be better off linking to something like this: http://www.rifters.com/crawl/?p=6116 Or this: http://rifters.com/real/2009/01/iterating-towards-bethlehem.... Less than
206.
by Freaky 11y ago
Yup: https://openconnect.netflix.com/software/ They're actively giving back a lot of their work too: http://v4.freshbsd.org/search?q=netflix
207.
by Freaky 11y ago
See also The Log File Navigator (lnav) if you're in the market for a fancy tail replacement: http://lnav.org/
208.
by Freaky 11y ago
Rogue System looks promising as a semi-realistic combat space sim: http://imagespaceinc.com/rogsys/ Pioneer also exists as an open source Frontier remake, with the same sort of flight model and universe: http:/&#
209.
by Freaky 11y ago
Not to mention how badly stress can screw with memory. If you're used to entering your password in a specific relaxed situation and now you're filled with dread every time you think about it, damn right you might not be able to re
210.
by Freaky 11y ago
My bare Linux repository comes to 1.2GB. A git gc run got it down to 1.1GB.

More ›