Booting Linux in One Second [pdf]
elinux.org
Booting Linux in One Second [pdf]
1–10 of 110 posts
Re: Booting Linux in One Second [pdf]
#2Here's a video of a talk by the author of this particular pdf
https://www.youtube.com/watch?v=KTRA1PRJWH8
Will be interesting to see what impact Intel's 3D Xpoint will have on boot times too.
Re: Booting Linux in One Second [pdf]
#3Re: Booting Linux in One Second [pdf]
#4An OS is recomputing the same functions over and over again when booting, so why not cache all of this, and make it instant?
Re: Booting Linux in One Second [pdf]
#5An OS is recomputing the same functions over and over again when booting, so why not cache all of this, and make it instant?
Re: Booting Linux in One Second [pdf]
#6Re: Booting Linux in One Second [pdf]
#7http://elinux.org/images/f/f7/RightApproachMinimalBootTimes....
Also under 1 second, and the approaches this guy took are seriously impressive. Lots of educational tidbits and "good-to-know"s in here even for non-embedded types. Reads very quickly too.
Re: Booting Linux in One Second [pdf]
#8Linux 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.
I think that proves your point.
Re: Booting Linux in One Second [pdf]
#9Linux 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.
I once had a brief conversation (via Reddit) with a guy using JACK for a commercial (embedded Linux) networked audio system. I wasn't aware of the exact specifics but I understand it was Sonos-style, embedded boards inside speakers. He wasn't particularly interested in talking about the work his team had done :P I think that proves your point.
As in, he tried to keep the secrets secret, or it seemed to be trivial and uninteresting to him?
Re: Booting Linux in One Second [pdf]
#10An OS is recomputing the same functions over and over again when booting, so why not cache all of this, and make it instant?
In the embedded hardware environment if something has changed and if this change is out of specs, then what you say can be adopted.