kasabali

56 ms·

781.
by kasabali 7y ago
No, cache is reserved as a non-SMR area on platters.
782.
by kasabali 7y ago
> all sequential load Surveillance data is recorded on top of the old one, which means all writes are rewrites and that is the worst case scenario for a SMR drive. A host-managed drive with carefully aligned zones may avoid this issue in
783.
by kasabali 7y ago
Sorry, I meant up to ~1.8TB. When that's possible 1TB is trival. Regarding your side point, there existed 320GB, 750GB and 1.5TB hard drives, so 1.5TB or even a 1.75TB would not be a weird size for a sku.
784.
by kasabali 7y ago
Apparently nothing is sacred if they can squeeze few bucks out of it
785.
by kasabali 7y ago
There are 2TB 7mm SMR drives, so ~1.8TB CMR should be easily doable. I think there were 1TB 7mm CMR drives available as far as 5-6 years ago, although I'm not sure about the 7mm part.
786.
by kasabali 7y ago
> As a result the write speed of the drive is even faster than a non-SMR drive until the cache area fills up I'm interested if there's a benchmark showing that?
787.
by kasabali 7y ago
I wish they were. They're actively pursuing it while discontinuing CMR. 5 years ago 1TB CMR laptop drives were abundant. Nowadays you'd be hard pressed to find a non-SMR one.
788.
by kasabali 7y ago
SMR is such a horrible backwards "technology", I wonder why vendors still push it aggressively on users after all these years. 1. Its performance is noticeably worse than CMR. 2. The density increase SMR provides compared to CMR i
789.
by kasabali 7y ago
Have a look at this paper [0] While there are big gaps of write amplification for metadata writes, on macro benchmarks all filesystems have similar results. btrfs has the biggest WAF, but you can enable compression globally and I suspect th
790.
by kasabali 7y ago
No, because half the vulnerabilities are in device drivers, which are unfortunately device specific binary blobs. Lineage OS has no choice but ship them as is, so they'll not be updated.
791.
by kasabali 7y ago
Ext4 reserved space also helps with fragmentation. To be more specific, reserved space on ext3 helps the fs so that it can be more flexible during allocation and avoid fragmentation. Ext4 has delayed allocation mount option for that purpose
792.
by kasabali 7y ago
Reliability does not only mean data loss. It may not be losing data but crashing every few hours, or locking up the system, or requiring constant monitoring and maintenance etc.
793.
by kasabali 7y ago
LVM snapshots has been good enough for consistent backups for the last 20 years. Then there is also thin snapshots if you feel fancy.
794.
by kasabali 7y ago
Easy, the prototype has been brought from Italy. Nothing has been made yet in Turkey.
795.
by kasabali 7y ago
I think he may have said that about "ELF modules" [1] specifically. Because plain BPF code runs in kernel mode and that wouldn't make it a micro kernel. I don't know if elf modules feature has been merged upstream. 1. h
796.
by kasabali 7y ago
That's a good start. If they'd be able to do 13 tests from a drop of blood from each of my fingers that'd be 130 tests!
797.
by kasabali 7y ago
To be specific, XP has had ingress firewall and SP2 adds the egress counterpart.
798.
by kasabali 7y ago
> Poettering and Dan Walsh come to mind with regard to the elitist attitude in their respective corners Don't forget Drapper
799.
by kasabali 7y ago
> many of its developers refuse to adapt technologies for the sole reason that it "stinks" of Microsoft. I don't where did you get that idea but it is not true at all. Linux developers have a history of ignoring (and rein
800.
by kasabali 7y ago
vm.vfs_cache_pressure I'm not sure if it'll exactly accomplish what you want though.
801.
by kasabali 7y ago
> I guess trying to free up some RAM by moving things to swap (the swap partition was full by this point) In that case, it cannot be moving things the swap since it was alreay full. What did probably happen is that since the swap was alr
802.
by kasabali 7y ago
Try setting vm.oom_kill_allocating_task. I find it more useful than the default behavior and it seems to be closer to what you want.
803.
by kasabali 7y ago
> There _NEEDS_ to be a setting where program pages don't get pushed out for disk cache, peroid, unless approaching a low ram situation, but BEFORE it causes long periods of total crushing unresponsiveness. Did you try different vm.
804.
by kasabali 7y ago
When you need to configuration, best practice is to put only the necessary configuration in a configuration snippet inside /etc/X11/xorg.conf.d/ without creating a full xorg.conf file.
805.
by kasabali 7y ago
I must add ”recent” here means more than 10 years. Last release that required an xorg.conf file was released in 2006 or 2007?
806.
by kasabali 7y ago
Tangential but this is misunderstood widely, so I cannot resist the urge to explain. First of all, modules can not be installed in parallel [1]. Secondly, it is not a new technological development at all. Modules in essence are just a fancy
807.
by kasabali 7y ago
> Can you just not upgrade on your own machine. How can I know which packages and which versions will be incompatible upgrades beforehand? How can I rely on distribution maintainers to know and warn me against incompatibilities with any
808.
by kasabali 7y ago
Not upgrading versions of desktop applications means I won't have to deal with nasty surprises like configuration files changing, defaults changing and requiring changing configuration, disappearing features, incompatibilities with exi
809.
by kasabali 7y ago
Correct me if I'm wrong but EVC targets 4x complexity of AVC with 20% improvement. So it has more to do with being royalty free but nothing to do with inflection point on the complexity / efficiency curve of H264.
810.
by kasabali 8y ago
It is true for everyone. DTrace source was released in Jan 2005, and Mac OS X 10.4 was released in Apr of same year. So they must have ported it immediately and ship it in the next release (10.5)

More ›