kasabali

45 ms·

631.
by kasabali 6y ago
You mean something like this? https://www.unixsheikh.com/articles/battle-testing-data-inte...
632.
by kasabali 6y ago
Client side decorations doesn't necessitate having gigantic buttons with swath of padding.
633.
by kasabali 6y ago
It works but it's fork of 5yo code base and upstream had several releases in the meantime
634.
by kasabali 6y ago
Telemetry data is used for justifying decisions, not making them.
635.
by kasabali 6y ago
I didn't say it was for "road noise". Car stereos was one of the popular places for listening CDs at the height of loudness war. > So the recording and mastering engineers began to produce recordings with limited dynamic r
636.
by kasabali 6y ago
Sure, if you deliberately refuse to interpret the context. Vinyl releases have a different target market and are mastered with more fidelity in mind, while CD releases are mainstream, and have been mastered with small dynamic range for deca
637.
by kasabali 6y ago
search for "loudness war"
638.
by kasabali 6y ago
> The acpi command allows privileged user to load crafted ACPI tables when Secure Boot is enabled > GRUB2 enables the use of the command acpi even when Secure Boot is signaled by the firmware. An attacker with local root privileges to
639.
by kasabali 6y ago
...
640.
by kasabali 6y ago
...
641.
by kasabali 6y ago
> When you upgrade a library, you probably want to restart the running applications that depend upon this. Dynamic linking won't save you. That's an orthogonal issue. You need to restart affected services nevertheless, whether
642.
by kasabali 6y ago
> The day I stop static linking is the day I can compile on one distro and ship to many without worrying about users reporting loader errors. That day is not today. That's completely missing point of the article. You're free to
643.
by kasabali 6y ago
Oh, that's an infamous one, too. Mark Russinovich did a live demo of troubleshooting it in one of his talks. ( I think it was "Case of the unexplained" 2013? https://channel9.msdn.com/events/TechEd/2
644.
by kasabali 6y ago
> If you want a bug-free os, you'll pay an extreme price in features or in dollars. It isn't like Windows division doesn't make billions of dollars every year. Lack of resources is hardly an excuse.
645.
by kasabali 6y ago
> How on earth anyone can press Control in the corner without moving your hand from comfortable row for blind typing? Pressing it with your palm works surprisingly well. It's even doable on shallow laptop keyboards after a while.
646.
by kasabali 6y ago
also might be gif dithering
647.
by kasabali 6y ago
Microsoft is obsessed with GUIDs, Windows is also full of them.
648.
by kasabali 6y ago
Thanks it was probably the FUSE driver. I haven't had a problem with it but I'm not a heavy user. On the other hand I've been a heavy user of exFat formatted sd cards on Samsung phones for long years and had no problems with
649.
by kasabali 6y ago
> It's a bit of a shame Microsoft didn't push and open up exFAT earlier and allowed FAT32 to become an issue again, only with removable flash drives and memory cards this time Erm, because that was the idea? SDXC is a big racke
650.
by kasabali 6y ago
Were you using the FUSE driver?
651.
by kasabali 6y ago
It is still patent encumbered. MS just promised to not give trouble for it being in the Linux kernel.
652.
by kasabali 6y ago
Even then it is actually only a driver or firmware limitation most of the time. My old laptop has Ricoh SDHC card reader. Windows can't read 64GB SD cards (properly formatted with exFAT according to the standard) on it because it'
653.
by kasabali 6y ago
It also conveniently allowed Microsoft to collect license fees from ExFAT patents on all SDXC devices.
654.
by kasabali 6y ago
AFAIK it is built into the memory controller, at least for ECC UDIMM. There's an extra DRAM chip on the module for parity (generally 8+1), but it is memory controllers responsibility to utilize it (that's why not all CPUs support
655.
by kasabali 6y ago
No need to pretend, because it never happened: > Initially, the problem was thought to be in the ext4 filesystem, since that is what the affected users were using...It took until December 4 for Lukáš Krejčí to correctly bisect the proble
656.
by kasabali 6y ago
You claimed there were two critical data corruption bugs in the past 5 years, one which was debunked as a not ext4 bug and the other one you linked is from April 2015, which happened more than 5 years ago. > which was caused by an ex
657.
by kasabali 6y ago
> ext4 had at least two critical data corruption bugs in the past 5 years in stable kernels No it hadn't. Those bugs were lower in the stack in block layer.
658.
by kasabali 6y ago
Xweak keys" didn't have anything to do with backporting fixes to older versions. It was introduced into the version in sid at the time.
659.
by kasabali 6y ago
Not by a long shot. Simply being mounted isn't a problem. A syscall needs to be hung on a network request. I regularly hit this issue. Most recent one was last year on 4.19 kernel when using NFS mount. I found the bug report for that o
660.
by kasabali 6y ago
Wow I forgot it existed. I must've erased it from my mind along with Scientific Linux. Nice to see they've kept it up-to-date so far.

More ›