Of course, its never going to be 100% secure. However if someone has stolen your device and had enough time to go through the process of faffing around making a fingerprint to ulnlock it, presumably you've already wiped it with find my iphone. If someone has physical control of your device, all bets are off.
However, as an unlock to prevent against casual snooping, the fingerprint scanner is convenient, and much less hassle than a passcode. Perhaps having the phone fall-back to passcode security after an hour or two is a good idea, and relegate fingerprint scan to a quick unlock, for a limited duration after you've locked the phone.
I'm in a similar boat - I get to evaluate/use any handset i want and decide what we're likely to purchase. I'm still carrying an iphone. Which is why i had the HTC One for an eval. Didn't find anything i need/want that iOS doesn't do and it didn't actually perform any better in day to day use than my 4s. I'll probably step to a 5s sooner or later, but I seriously see no pressing need to ditch the 4s yet.
What's your point? If you must know it was 16 bit 1024x768. I also had an amiga back in the day which shat on X11 from a great height. However it didn't run on beefy (at the time) PC hardware.
Please inform as to the correct Android hardware. I recently returned an HTC one (quad core) after an eval period of one week to see what I'm missing with Android and to be honest, performance was about the same or worse in daily usage (scrolling, responsiveness, etc) as iOS on my 4s.
So, what is the "correct" hardware that provides this magical superior performance?
I'm willing to bet that I could get Linux running on 15 year old computer hardware just fine. I may not turn on all the whizbang graphics, but it will work.
So could I. It would have no new features. Which brings up the crux of the issue: why bother to support zero new features? Security fixes? Maybe, but again the hardware has been EOL'd for some time now and most likely no longer works due to battery expiry, damage, etc.
Maybe i should clarify - i wasn't referring specifically to the kernel. But a distribution including Kernel + X11 environment. I used to run X11 on my old 486.
Mobile devices are on an accelerated timeline. There's nothing stopping users of old hardware running the old, designed-for-device iOS (or Android, etc.), if their device is still alive. Many well past their use by date in terms of battery, desired feature set, etc.
They already disable new features on old hardware. On even older hardware (3+ years out of warranty, multiple years past expected battery expiry), you still have the old OS.
When i started using Linux, it would run just fine on my 486DX33 with 8 MB of RAM. Now when I try to run it on machines with 50x that spec it is slow.
Newsflash: hardware requirements increase with new features. Supporting end of life hardware that hasn't been made for multiple generations in new platforms holds back said platform. Whether it is iOS, WIndows, Linux or whatever.
That's fine. Seriously, when do you ever have a block in common between two files that are not identical copies of the whole file? Certainly not in the middle of a giant file. By nature, giant files (music, video) are compressed and essentially random. Maybe as the very last block in a file, or in a very small file, in which case out-of-order is a non-issue.
If you move a de-duped block to defragment file X, then the same block referenced by file Y is now not in order. If it is in memory cache the whole concept is moot anyhow - whether it is fragmented on disk or not is irrelevant.
Given that with de-dup, we are dealing with BLOCKS and not complete files, what order do you propose they are sorted in? Or are you talking about just "Defragmenting" by consolidating them all at the start of the disk, which would make more sense?
Slashdot Mirror
Of course, its never going to be 100% secure. However if someone has stolen your device and had enough time to go through the process of faffing around making a fingerprint to ulnlock it, presumably you've already wiped it with find my iphone. If someone has physical control of your device, all bets are off.
However, as an unlock to prevent against casual snooping, the fingerprint scanner is convenient, and much less hassle than a passcode. Perhaps having the phone fall-back to passcode security after an hour or two is a good idea, and relegate fingerprint scan to a quick unlock, for a limited duration after you've locked the phone.
I'm in a similar boat - I get to evaluate/use any handset i want and decide what we're likely to purchase. I'm still carrying an iphone. Which is why i had the HTC One for an eval. Didn't find anything i need/want that iOS doesn't do and it didn't actually perform any better in day to day use than my 4s. I'll probably step to a 5s sooner or later, but I seriously see no pressing need to ditch the 4s yet.
Lol. you're comparing the X11 stack and claiming superiority :)
Put them both on the same hardware and see how they fare. Hardware is getting faster.
Also... i had a pentium pro 180 running squid on debian for 500 ISP users back in the day...
Pentium pro is a lot more powerful than the original boxes Linux ran on like 386sx and up.
What's your point? If you must know it was 16 bit 1024x768. I also had an amiga back in the day which shat on X11 from a great height. However it didn't run on beefy (at the time) PC hardware.
I'm not talking about low level kernel features. And yes I've been running linux for about 20 years now so I do have an idea.
So.... basically like iOS does it then?
Hows the security updates?
Multi-tasking IS hard to do well on a mobile device without chewing the shit out of your battery life.
You realise that iOS is the darwin kernel, which has full pre-emptive multitasking, right?
Please inform as to the correct Android hardware. I recently returned an HTC one (quad core) after an eval period of one week to see what I'm missing with Android and to be honest, performance was about the same or worse in daily usage (scrolling, responsiveness, etc) as iOS on my 4s.
So, what is the "correct" hardware that provides this magical superior performance?
So could I. It would have no new features. Which brings up the crux of the issue: why bother to support zero new features? Security fixes? Maybe, but again the hardware has been EOL'd for some time now and most likely no longer works due to battery expiry, damage, etc.
Maybe i should clarify - i wasn't referring specifically to the kernel. But a distribution including Kernel + X11 environment. I used to run X11 on my old 486.
Mobile devices are on an accelerated timeline. There's nothing stopping users of old hardware running the old, designed-for-device iOS (or Android, etc.), if their device is still alive. Many well past their use by date in terms of battery, desired feature set, etc.
They already disable new features on old hardware. On even older hardware (3+ years out of warranty, multiple years past expected battery expiry), you still have the old OS.
Sure, there are exceptions. But expecting end of sale / end of life hardware to be supported by NEW OS releases is living in fantasy land.
Also, android handsets don't get new OS releases 3 years later to compare.
When i started using Linux, it would run just fine on my 486DX33 with 8 MB of RAM. Now when I try to run it on machines with 50x that spec it is slow.
Newsflash: hardware requirements increase with new features. Supporting end of life hardware that hasn't been made for multiple generations in new platforms holds back said platform. Whether it is iOS, WIndows, Linux or whatever.
Minimum recommended size for adequate performance. There is nothing inherent in ZFS to prevent it from working in less memory.
Very regularly?
Exactly... there is no "order" to de-duped blocks to sort them into for contiguous access.
If you move a de-duped block to defragment file X, then the same block referenced by file Y is now not in order. If it is in memory cache the whole concept is moot anyhow - whether it is fragmented on disk or not is irrelevant.
Given that with de-dup, we are dealing with BLOCKS and not complete files, what order do you propose they are sorted in? Or are you talking about just "Defragmenting" by consolidating them all at the start of the disk, which would make more sense?
ZFS was originally developed on hardware with similar/less horsepower than a raspberry pi (back in the early 2000s... 2001 or so IIRC).