Had to once more flog systemd as it that is the only fast alternative to systemv...
Booting Linux in One Second [pdf]
71–80 of 110 posts
Re: Booting Linux in One Second [pdf]
#72Linux can be so amazing when configured especially for some tasks. For example, Jack on linux can deliver audio latencies under 2ms! The problem is that configuring Linux like this almost requires a CS degree.
Pretty sure even most people with CS degrees could not configure Linux. It's pretty specialized knowledge as far as I can tell.
Re: Booting Linux in One Second [pdf]
#73Linux can be so amazing when configured especially for some tasks. For example, Jack on linux can deliver audio latencies under 2ms! The problem is that configuring Linux like this almost requires a CS degree.
Jack is what forced me to from a beginner to an intermediate Linux user as a teenager, and I still don't understand it.
Re: Booting Linux in One Second [pdf]
#741 seconds seems a rather arbitrary measure. In HCI 100ms seems to be the value that's generally taken under which an action seems to be happening instantaneously [1] It's quite sad to see how we hardly use the computing power offered by our modern computers to actually speed up common tasks, but instead bloat it up with all kinds of stuff. [1] http://cogsci.stackexchange.com/questions/1664/what-is-the-t...
One second, ten seconds... The problem isn't that it takes time, it's that the user has to sit there and wait while it takes that time. My desktop takes about two seconds to resume from suspend. I'd sit down, lean down to the floor and press the power button and then wait that two seconds. I fixed the whole problem by moving the case up onto the desk so that I have to walk past it to sit down. Now I press the button…
The problem with anticipation is that nobody except you can truly know your intent. For example, walking up to a car with my keys might just mean I want to grab something out of the trunk; or the car might be in a closed garage and that wouldn't be quite safe at the moment.
The easiest and safest thing is usually still to let people control more of what happens because there's a lot of edge cases that might add up, or have really bad consequences for when they rarely occur.
Re: Booting Linux in One Second [pdf]
#75People are OK with frequently booting their mobile devices to temporarily "fix bugs", which can take up to tens of seconds, but waiting a moment to boot a desktop device? Nuh uh. Of course there might be some market advantage to be had with faster booting and it's a plus for the whole UX. And optimisation is definitely cool, though I think many more problems would be solved if people were forced to think once in a wh…
Seems like this is more about car computers, embedded systems, and replacing "suspend" than just improving the desktop experience. The slowest booting machine I own is my windows Steambox, and it's still faster to boot than my TV or receiver (5-10 seconds) just by virtue of having an SSD.
Re: Booting Linux in One Second [pdf]
#76Earlier quoted context omitted.
One second, ten seconds... The problem isn't that it takes time, it's that the user has to sit there and wait while it takes that time. My desktop takes about two seconds to resume from suspend. I'd sit down, lean down to the floor and press the power button and then wait that two seconds. I fixed the whole problem by moving the case up onto the desk so that I have to walk past it to sit down. Now I press the button…
The problem with anticipation is that nobody except you can truly know your intent. For example, walking up to a car with my keys might just mean I want to grab something out of the trunk; or the car might be in a closed garage and that wouldn't be quite safe at the moment. The easiest and safest thing is usually still to let people control more of what happens because there's a lot of edge cases that might add up, o…
That's not a problem with anticipation as a concept, that's a problem with bad anticipation. Certainly it's possible to detect whether the car is in a closed garage, and it will eventually be possible to predict whether you want to grab something out of the trunk or go for a drive.
Even though it often feels like you do, humans generally don't know their own intents. It's not that high of a bar for a predictive system to clear.
Re: Booting Linux in One Second [pdf]
#77Why isn't any phone doing it? (either smart or feature variety)
The simple answer: Because phones are always-on devices.
Rebooting your phone is an uncommon use case, so it's not optimized.
Re: Booting Linux in One Second [pdf]
#78Earlier quoted context omitted.
With my Nexus 4, rebooting every other day is a pretty good idea. Usually fixes my Wi-Fi, 3G, and all sorts of weird bugs for the moment. Don't know how representative this is for Android phones in general, but most Nexus 4 owners I know tell me this is normal. Oh, usually once a week, sometimes twice a day, the phone will do the rebooting for me. Sometimes when it's in my pocket, sometimes when I try to watch a vide…
I used to have a Nexus 4 and had the same problem. I now have a Samsung Galaxy S3 and still have the same kinds of issues, just not as frequently. From what I've heard from other people I think it's fair to say it's a general problem with Android-based smart phones.
Huh, this thread has been quite an eyeopener, the stuff people put up with.
Re: Booting Linux in One Second [pdf]
#79Linux can be so amazing when configured especially for some tasks. For example, Jack on linux can deliver audio latencies under 2ms! The problem is that configuring Linux like this almost requires a CS degree.
Pretty sure even most people with CS degrees could not configure Linux. It's pretty specialized knowledge as far as I can tell.
>Pretty sure even most people with CS degrees could not configure Linux.
It certainly does not take a degree of any kind to "configure Linux". Not even if you're below average IQ.
Re: Booting Linux in One Second [pdf]
#80Earlier quoted context omitted.
One second, ten seconds... The problem isn't that it takes time, it's that the user has to sit there and wait while it takes that time. My desktop takes about two seconds to resume from suspend. I'd sit down, lean down to the floor and press the power button and then wait that two seconds. I fixed the whole problem by moving the case up onto the desk so that I have to walk past it to sit down. Now I press the button…
The problem with anticipation is that nobody except you can truly know your intent. For example, walking up to a car with my keys might just mean I want to grab something out of the trunk; or the car might be in a closed garage and that wouldn't be quite safe at the moment. The easiest and safest thing is usually still to let people control more of what happens because there's a lot of edge cases that might add up, o…
Wouldn't be safe? I'm talking about starting an on-board computer, not the engine.
Unless you're going to be repeatedly walking too and from your car all day, starting a computer needlessly isn't going to be the end of the world.
Yes, it may mean doing more work but that's the trade off here for "instant on". It's either always on, you wait, or it guesses when you're going to use it and you accept there are a few false positives.