Live data from Hacker News

Booting Linux in One Second [pdf]

elinux.org

101–110 of 110 posts

Re: Booting Linux in One Second [pdf]

#101
post #87

Earlier quoted context omitted.

QNX was open source for a while, what is surprising is that there doesnt appear to be an easily searcable version of the code available on google.

That was a bait and switch by management that I could tell. They got a bunch of contributions from the community then pulled it. Or just felt that it wasn't worthwhile after little contributions. I can't be sure. Nonetheless, underlying technology is solid with that showing in Blackberry Playbook.

I regret not downloading the source code while it was available.

Re: Booting Linux in One Second [pdf]

#102
post #101

Earlier quoted context omitted.

That was a bait and switch by management that I could tell. They got a bunch of contributions from the community then pulled it. Or just felt that it wasn't worthwhile after little contributions. I can't be sure. Nonetheless, underlying technology is solid with that showing in Blackberry Playbook.

I regret not downloading the source code while it was available.

I lost my copy. Regrets here, too. Minix 3 is fortunately coming along nicely and already resilient against driver faults.

Re: Booting Linux in One Second [pdf]

#103
post #81

Earlier quoted context omitted.

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 fa…

> 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. Or engineers reduce startup time to a point where it feels instant. Compare e.g. startup times of DSLRs and point-n-shoot cameras. With a DSLR you switch it on and it is ready to shoot by the time your finger gets to shutter button.

This is why e.g. go pro uses a hybrid approach with an embedded rtos for the camera stuff and then virtualized Linux on top of this for less critical work where you want to use a stack e.g.http streaming. 3 yrs back I worked in a team which looked at booting Linux for a camera device in < 100ms and couldn't find a solution.

Re: Booting Linux in One Second [pdf]

#104

Linux 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.

Why would a latency of 2ms be considered good unless it was for packets traveling across a country?

Re: Booting Linux in One Second [pdf]

#105
post #84

Earlier quoted context omitted.

My GF's Samsung smart tv has to update at least once per week when you power it on. There're regular warnings for service unavailability. It spends time logging on each time you start it. Sometimes it won't even turn on when you press the button. It's a completely awful machine. I'd honestly rather have a CRT.

Can you not turn off the smart functionality and updates to use it as a monitor/traditional TV?

I'm not sure the Netflix/Hulu/HBO Go applications would work if we did that.

Re: Booting Linux in One Second [pdf]

#106

1 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...

I completely agree with the general idea. Bloat is too high and has far reaching consequences. And it's actually even worse than that. 100ms is nowhere near enough to be sufficient for all applications. For audio applications you need 10ms [ http://superpowered.com/androidaudiopathlatency ] which incidentally is the reason why Android is unusable for any interactive audio applications. Same applies to Virtual Reality…

I'm glad you posted this. Even the 10ms rule of thumb is...well, not always true either!

FWIW, if you are playing virtual drums, drummers need something like under 2ms response time; even 10ms can be easily felt by a drummer and cause their timing to get way off!

On top of that, if you are doing, say, a real-time effect on a vocal track, even a tiny sub 1ms delay causes a weird reverb effect in her monitor vs. the singer hearing herself, which will cause your singer's singing to get out of sync!

Re: Booting Linux in One Second [pdf]

#107
post #37

Has anyone booted the pdf in a minute?

If you use an actual pdf reader instead of the JS-based in-browser crap, it's quite instantaneous.

Interesting - in my experience pdf.js is faster than adobe reader... Didn't measure it though.

Re: Booting Linux in One Second [pdf]

#108

Linux 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.

Why would a latency of 2ms be considered good unless it was for packets traveling across a country?

He is talking about (worst-case) scheduling latency. See https://lwn.net/Articles/404993/.

Re: Booting Linux in One Second [pdf]

#109
post #68

Earlier quoted context omitted.

Have you tried performing using an android app? I used a drum-pad app the other week and the latency makes it unplayable. There's a great explanation here as to why it's so bad: http://superpowered.com/androidaudiopathlatency

This is fixed in newer Android phones: https://source.android.com/devices/audio/latency_measurement...

That's awesome to hear, I just got a new phone so I'm going to try this out :)

Re: Booting Linux in One Second [pdf]

#110
post #40

Presented by Montavista already in 2009: https://youtu.be/-l_DSZe8_F8 There is also some documentation from Montavista from that time. EDIT: The presentation by Montavista from 2008: http://www.freescale.com/files/training_pdf/VFTF09_MONTAVIST...

And QNX before that. But, that's a well-engineered, UNIX-like microkernel rather than Linux. Oh well...

Yeah, I was a fan of QNX for some time. A complete functioning OS with X windows system on a 1.44M 3.5" disk.
Post reply on HN