Slashdot Mirror


The 1-Second Linux Boot

An anonymous reader writes "Less than one second Linux boot! This video shows an OMAP3530 capturing video data from a camera and rendering it to an LCD display — the video appears on the LCD display in less than a second from reset."

156 comments

  1. 1-Second First Post! by Fieryphoenix · · Score: 5, Funny

    Guess Linux is faster than Slashdot.

    1. Re:1-Second First Post! by Anonymous Coward · · Score: 0

      What the hell!

      I spent a week trying to get that damn 3530 to boot faster.

      There better be a wiki.

    2. Re:1-Second First Post! by rjch · · Score: 1

      Even the web site is quick as a flash... I got this in less than a second!

      Unable to connect

      Firefox can't establish a connection to the server at www.embedded-bits.co.uk.

              * The site could be temporarily unavailable or too busy. Try again in a few
                          moments.

              * If you are unable to load any pages, check your computer's network
                          connection.

              * If your computer or network is protected by a firewall or proxy, make sure
                          that Firefox is permitted to access the Web.

    3. Re:1-Second First Post! by Anonymous Coward · · Score: 1, Informative

      The video is also on YouTube (http://www.youtube.com/watch?v=wUWBkIquQaI) - The website seems a bit bogged down.

    4. Re:1-Second First Post! by Anonymous Coward · · Score: 1, Informative

      The video is a YouTube video and can be found here: http://www.youtube.com/watch?v=wUWBkIquQaI The website in this post seems to keep cutting out...

    5. Re:1-Second First Post! by ls671 · · Score: 1

      They said it boots quickly but they never mentioned any capacity to handle load ;-))

      --
      Everything I write is lies, read between the lines.
    6. Re:1-Second First Post! by DaVince21 · · Score: 1

      Even the web site is quick as a flash... I got this in less than a second!

      So you mean not quick at all?

      --
      I am not devoid of humor.
    7. Re:1-Second First Post! by DaVince21 · · Score: 1

      No, but they'll investigate your device on how to speed up its boot time by at least 50% for a measly £4,950 + VAT...

      --
      I am not devoid of humor.
  2. I use Linux by Beardo+the+Bearded · · Score: 1

    Posted from Linux, but surely I have failed.

    --

    ---
    ECHELON is a government program to find words like bomb, jihad, plutonium, assassinate, and anarchy.
    1. Re:I use Linux by biryokumaru · · Score: 3, Funny

      That's not the same kind of POST.

      --
      When you're afraid to download music illegally in your own home, then the terrorists have won!
  3. The Good Ole' /. Effect... by duragnulinux · · Score: 1

    ... is Large and in Charge.

    1. Re:The Good Ole' /. Effect... by DaVince21 · · Score: 1

      The Good Olé?

      --
      I am not devoid of humor.
  4. Re:Link is dead already by Beelzebud · · Score: 5, Funny

    Don't worry, it will be back in a second.

  5. Re:Link is dead already by Metasquares · · Score: 1

    They should reboot it between requests.

  6. Pretty long video though by suso · · Score: 5, Funny

    For a 1 second boot, it takes a 2.5 minute video to demonstrate it.

    1. Re:Pretty long video though by buchner.johannes · · Score: 3, Funny

      Because it's in slow motion, doh

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
  7. Search by Anonymous Coward · · Score: 0

    Search for MontaVista and you can likely find the video. TheRegister has it as well.

  8. The Register also has the story. by Anonymous Coward · · Score: 5, Informative
    1. Re:The Register also has the story. by wrmrxxx · · Score: 2, Insightful

      That video is 2 minutes and 27 seconds long. Long enough to boot 147 times over.

    2. Re:The Register also has the story. by somenickname · · Score: 4, Informative

      I find it disturbing that you have to sit through a 2:30 minute powerpoint presentation accompanied by 1980s porn music in order to see the 1 second boot time. For those looking for just the boot time, it occurs between 1:05 and 1:06 seconds in the video.

    3. Re:The Register also has the story. by martin-boundary · · Score: 4, Funny

      it occurs between 1:05 and 1:06 seconds in the video.

      Which half of 1:05? I don't want to waste my time!

    4. Re:The Register also has the story. by Anonymous Coward · · Score: 0

      I find it disturbing that you have to sit through a 2:30 minute powerpoint presentation accompanied by 1980s porn music in order to see the 1 second boot time. For those looking for just the boot time, it occurs between 1:05 and 1:06 seconds in the video.

      So the timing is just like 1980s porn. Who knew Linux would become a star actor/actress.

    5. Re:The Register also has the story. by frogboyflips · · Score: 1

      This is a different story - The register one was from last year.

    6. Re:The Register also has the story. by subsonic · · Score: 1

      Yes! Here's a helpful hint to all you video uploaders: Just show what you wanna show. Lose the "intro" just cut to the chase. If you've got a one-second boot of linux, show it, then show it in slow mo or with more info if you really want to. Youtube is not your grand theater to present your in depth info (well, it could be...) Just cut to the chase, then follow up. My wasted time still has some value to me.

    7. Re:The Register also has the story. by Antique+Geekmeister · · Score: 1

      No, no, that's not porn. It's the Charlie's Angels theme: where there were plenty of young men who committed self-abuse to that television introduction, the show never really crossed the line into real pornography.

      Porn music gends to have more of a beat, and less flutes than that particular rendition.

    8. Re:The Register also has the story. by boompie · · Score: 1, Redundant

      Lol !!

      --
      http://www.bbflanders.be - Bed & Breakfasts in Belgium
    9. Re:The Register also has the story. by Anonymous Coward · · Score: 0

      The first half of 1:05, then there was a commercial, then it resumed in 1:06.

  9. Re:Take that! by Anonymous Coward · · Score: 0

    i don't give a fuck how fast an os boots if it can't run my apps. without my apps i have no use for a computer.

    my commodore 64 probably boots faster but it doesn't make it the best machine for the job.

  10. One Second Boot? by WrongSizeGlass · · Score: 4, Funny

    It must have been his first time.

  11. Specialized platform... by pushing-robot · · Score: 2, Insightful

    An OS optimized for a single platform being loaded uncompressed from ROM (or in this case flash) is nothing special. Heck, many of the computers of 30 years ago booted up in a second or two for the same reasons.

    --
    How can I believe you when you tell me what I don't want to hear?
    1. Re:Specialized platform... by tepples · · Score: 2, Interesting

      An OS optimized for a single platform being loaded uncompressed from ROM (or in this case flash) is nothing special.

      The popular Atom-based netbooks are so similar that they're almost "a single platform", and a lot of them have flash from which one can load an uncompressed kernel (or one lightly compressed with a cheap codec like LZO).

      Heck, many of the computers of 30 years ago booted up in a second or two for the same reasons.

      So why do computer users let Wirth's law overpower Moore's?

    2. Re:Specialized platform... by marcansoft · · Score: 4, Interesting

      Yup, 1-second embedded boot is fairly is fairly nice but the summary is misleading and this is not even remotely comparable to desktop boot times. They're using an initramfs, no real filesystem, and no real distribution.

      To put things into perspective, I have an OMAP3530 platform in front of me (same as TFA, funny coincidence) and a totally vanilla kernel that I compiled a few days ago boots in 2.5 seconds, not counting the long time wasted by the totally suboptimal bootloader (3-second deliberate boot delay, networking support, loading the kernel from an SD card, all that crap). That time includes mounting an ext3 filesystem from an SD card and starting to run init from it, and the kernel has built-in drivers for all onboard hardware including USB host+OTG, Ethernet, networking (ipv4 and ipv6), HDMI display output, audio, etc. Of course, booting the rest of the (real, full-blown) distro up takes a while as usual, but TFA is basically showing an embedded application that could be as simple as a single binary running from initramfs (I've actually poked a MontaVista Linux system once, and their startup was basically a single shell script - not quite SysV Init!). Remove the sd/ext3 stuff, remove useless drivers, replace the bootloader with a minimal build, use a busybox shell script + a single executable binary for the actual application, and you're probably getting close to 2-second total boot times without even beginning to optimize stuff with DMA and the like.

    3. Re:Specialized platform... by Anonymous Coward · · Score: 1, Funny

      Or you could just get rid of that 3 second delay to get it to boot in -0.5 seconds. It will turn on before you've pressed the button!

    4. Re:Specialized platform... by CastrTroy · · Score: 1

      Exactly. My original Nintendo didn't take any time at all to boot up. Even all the major consoles boot up in a few seconds. When you don't have to explore the system for new hardware and you can just load a preconfigured image into memory, things go a lot faster. I think there should be ROM chips you can flash, and you only have to reflash them if you have a hardware change.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    5. Re:Specialized platform... by Anonymous Coward · · Score: 0

      What impact does your average computer user have on the speed of the software he uses?

    6. Re:Specialized platform... by The+Wild+Norseman · · Score: 2, Funny

      So why do computer users let Wirth's law [wikipedia.org] overpower Moore's?

      Because it's now Wirth/Moore?

      --
      "A government is a body of people usually -- notably -- ungoverned." -Shepherd Book
    7. Re:Specialized platform... by tepples · · Score: 1

      What impact does your average computer user have on the speed of the software he uses?

      On the server side, the more users that use a program, the slower it runs. On the client side, the more programs a user runs at once, the slower they run. And for booting, the user expects the program to be running. Some employers have even found themselves on the business end of lawsuits over the employer requiring the employee to sit there for minutes while a computer starts yet not paying the employee for wasted time.

    8. Re:Specialized platform... by Anonymous Coward · · Score: 0

      An OS optimized for a single platform being loaded uncompressed from ROM (or in this case flash) is nothing special. Heck, many of the computers of 30 years ago booted up in a second or two for the same reasons.

      All personal computers I used 30 years ago booted in less than a second, or at least I think they did, the screen/TV usually took a couple of minutes to warm up.

    9. Re:Specialized platform... by Anonymous Coward · · Score: 0

      Ouch! Please don't do that again!

  12. Misleading summary by cualexander · · Score: 5, Insightful

    This is a linux computer in a car that has very specific hardware and limited functionality. Wake me up when you can get a true desktop machine to boot in 1 second and then we can talk. This is like saying, "My toaster runs linux and it can boot instantly!" Big freaking deal.

    1. Re:Misleading summary by Anonymous Coward · · Score: 0

      Hey, everyone knows toasters are the sole property of BSD!

    2. Re:Misleading summary by aldld · · Score: 1

      My pet rock runs Linux, and it boots up in exactly zero seconds!

    3. Re:Misleading summary by xZgf6xHx2uhoAj9D · · Score: 1, Insightful
      I don't see why the summary is misleading or why a desktop machine would be the only measuring stick worth considering, especially when you think of how seldomly Linux is run on the desktop.

      This is like saying, "My toaster runs linux and it can boot instantly!"

      What would be wrong with that?

      They poured a tonne of work into making this happen. Just because they control the hardware their hard work isn't worth anything? I think it's pretty cool what they've been able to do, someone no one else in the history of Linux has ever been able to do.

    4. Re:Misleading summary by caseih · · Score: 5, Insightful

      Actually it is a pretty big deal. In most embedded systems that need to be instant on, a manufacturer would likely use highly customized code with highly customized hardware. The big deal here is that a (relatively) full linux kernel and system boots in the same time as all that custom code giving a manufacturer a solid, generic, and cheap base to work from. In other words, rather than having to rely on highly customized, specific firmware for the device, a more generic linux-based system platform can be used. This makes everything cheaper and thus must more profitable. This is proof that Linux is flexible and agile enough to be used from the smallest devices all the way up the line. Same kernel-level APIs everywhere. Same tools. A tremendous advantage for embedded device makers rushing to get to market.

    5. Re:Misleading summary by Zemran · · Score: 1

      My Linux runs Linux and has already booted !!!

      --
      I love stacking my barbecues in the shed at the end of summer - you can't beat a bit of grill on grill action.
    6. Re:Misleading summary by Korbeau · · Score: 1

      "My toaster runs linux and it can boot instantly!" Big freaking deal.

      I think that according to the Slashdot crowd, a toaster that runs Linux IS a big freaking deal!

    7. Re:Misleading summary by Anonymous Coward · · Score: 0

      This is like saying, "My toaster runs linux and it can boot instantly!"

      So that's how the Cylons took over.

    8. Re:Misleading summary by Gaardenzwerch · · Score: 1

      This is a linux computer in a car that has very specific hardware and limited functionality.

      So it's just like a Mac in fact...

      Wake me up when you can get a true desktop machine to boot in 1 second and then we can talk. This is like saying, "My toaster runs linux and it can boot instantly!"

      Big freaking deal.

    9. Re:Misleading summary by marcansoft · · Score: 1

      They poured a tonne of work into making this happen. Just because they control the hardware their hard work isn't worth anything? I think it's pretty cool what they've been able to do, someone no one else in the history of Linux has ever been able to do.

      I'm not sure this is a first, nor am I sure this took that much work. Using DMA to optimize the obvious three or four huge RAM copies during boot is hardly a tonne of work. That's more like a week of work.

    10. Re:Misleading summary by Anonymous Coward · · Score: 0

      The big deal here is that a (relatively) full linux kernel and system boots in the same time as all that custom code giving a manufacturer a solid, generic, and cheap base to work from.

      I'm not so sure I'd call a very stripped down embedded system "relatively full". Yes, it's a kernel with some specialized doohickys hanging off it, but I assure you it's been slimmed down to just the bare essentials for its dedicated function.

    11. Re:Misleading summary by Chewbacon · · Score: 1

      My toaster doesn't run linux and has no boot time. Beat that.

      --
      Chewbacon
      The Bible is like Wikipedia: written by a bunch of people and verifiable by questionable sources.
    12. Re:Misleading summary by rsun · · Score: 2, Insightful

      And the number of embedded Linux systems with ludicrous boot times that could be improved by something like this is quite high. Think of that BluRay player that takes 90 seconds to open the tray from power off, or your new LCD TV that takes 30 seconds to produce a picture, or your Tivo that takes minutes to be ready to do anything. The vast majority of these devices run embedded linux and getting the boot times down to sub 10 seconds would go a long way to making customers much happier. I know I'd be much happier with consumer electronics if I didn't have to wait so much for things to boot (and sadly, since I've been doing embedded Linux for the last 8 years, I'm probably responsible for some of it...) Yeah, this demo is certainly a contrived example - I'd guess that they've stripped the kernel and u-boot to the bare minimum, loading from parallel flash instead of serial, no arbitrary delays anywhere and init is probably the application they're demoing.

    13. Re:Misleading summary by complacence · · Score: 1

      hardly a tonne of work. more like a week of work.

      Google failed me. How many weeks is a tonne again?

    14. Re:Misleading summary by ChunderDownunder · · Score: 1

      Linux, meh, toasters have been running NetBSD for 4 1/2 years

    15. Re:Misleading summary by Anonymous Coward · · Score: 0

      I tried to load Ubuntu in my toaster, but it just melted the DVD.

      I'd appreciate a step-by-step guide on how to do it properly.

  13. But by DuChamp+Fitz · · Score: 4, Funny

    does it run crysis?

    1. Re:But by Mitchell314 · · Score: 2, Funny

      It can start it.

      --
      I read TFA and all I got was this lousy cookie
    2. Re:But by marcansoft · · Score: 1

      No, but it does run Quake 3 at a very playable framerate (these things have a 3D accelerator in them) ;)

  14. Ok... I'll take it by Foredecker · · Score: 5, Informative

    Ok, so that is interesting, but only just... This isnt desktop Linux so Im not sure why you are saying "eat that".

    The OS is DMAed directly into system memory. Ok, thats kind of spiffy. That means its been "pre-loaded" which is already located.

    Let me put this in perspective. Back in the mid 90s I worked at AMD. On the ÉlanSC520 system on a chip (133mhz 486 class):

    • Booting of Windows CE, QNX, Psos, VXworks and other real time operating systems to a running state (like these guys) was measured in 100s of milliseconds.
    • Even better, the SC520 supported Execute in Place (XIP) - FLASH was directly conntected and had a controlerl off the CPUs cache - it was fast. This let the OS and applicatoins run right out of flash from reset - no "booting" at all. Systems could easily initialize in 10s of MS and be fully running - with graphics in a few 100ms. This included a running network stack. Pretty spiffy for the old school.
    • There was a company that was doing this with an early version of Linux back then too. Their company name started with an R - but I cannot remember the rest. I think someone bought them. This was fast too.

    So, this really isnt that spectacular - cool yes, ground breaking no.

    -Foredecker

    --
    Jibe!
    1. Re:Ok... I'll take it by Anonymous Coward · · Score: 3, Funny

      Isn't this what Commodore Business Machines were doing back in the 70's? Will everyone ever catch up with their remarkable technology? Not only instant OS but alternative instant OS's by plugging in a new cartridge. Awesome even at 1MHZ.

    2. Re:Ok... I'll take it by paradxum · · Score: 1

      I completely agree, it's not "groundbreaking" but honestly as someone developing a linux based embedded device, I'm glad to see someone doing it today with "modern" systems.

    3. Re:Ok... I'll take it by Foredecker · · Score: 1

      Yes - it is pretty cool. I think that Linux is well suited to the embedded space. Windows is not designed for this. Windows CE was at one time, but the focus on mobile phones took the team away from that market. To be honest, Windows CE was never a very good embedded OS.

      We do have a Windows Embedded product - but it is meant more for stripped down PC applications like kiosks, point of sale termianls and non real time industrial control applcations. Windows was not at all desigined to be a real time OS

      --
      Jibe!
    4. Re:Ok... I'll take it by JoeMerchant · · Score: 1

      And I could get 8 bit micros going from cold to running state in microseconds - just skip the OS and start doing your useful work directly. Yeah, you have to do everything by hand and can't leverage much existing code, but it does switch on like a lightbulb.

    5. Re:Ok... I'll take it by beguyld · · Score: 1

      Which 8-bit micro didn't need the crystal oscillator to stabilize first? Well, you can execute instructions, but for instance a serial port baud rate won't be accurate for at least a few milliseconds. Though something like a MSP430 runs off the 32KHz with a PLL, and can start up very quickly indeed.

      Still, I agree that if you really want to start quick, you don't load a few hundred K of kernel code...

    6. Re:Ok... I'll take it by JoeMerchant · · Score: 1

      I didn't say how many microseconds... but perception wise, by the time your finger is off the power switch, it's up to speed.

      And, yeah, the kernel code needs to be a pre-initialized library, not something that gets "warmed up" every time the system is switched on.

  15. Re:Take that! by trapnest · · Score: 0

    "You're"

  16. Sense? by Hurricane78 · · Score: 1, Interesting

    Apart from the “because I can”, what’s the actual point of this?

    I mean restarting the computer is rather a Windows thing. Why would you reboot a Linux machine? There isn’t a new kernel that often...
    If it’s a desktop, you are going to switch it on in the morning, go take a piss, enter the password, go find something to eat, and then it runs for the day. Same thing when you were away and came home.

    And for anything else (e.g. laptops) there always is hibernation.
    Also the trick to make shutdown actually reboot and go to hibernation, helps with doing actual reboots.

    --
    Any sufficiently advanced intelligence is indistinguishable from stupidity.
    1. Re:Sense? by MichaelSmith · · Score: 1

      Why would you reboot a Linux machine? There isn’t a new kernel that often...

      I walk to the tram stop. Its at the end of the line so the tram stops there for a while. I validate my ticket. Find a seat. Take my eeepc 701 out of its bag. I have to shut it down because hibernation uses the battery and I need that power to last all the way to work. I start to boot it up. A cafe near the tram stop has free wifi so I can check /. from there. But before ubuntu boots up the tram moves off.

      So you see, if linux booted faster I could get free wifi.

    2. Re:Sense? by fuzzyfuzzyfungus · · Score: 4, Interesting

      Embedded systems, I suspect.

      For servers and a fair few desktops, uptime is a virtue. They are rarely or never voluntarily shut down. For that reason, boot time isn't a huge issue(particuarly for servers, you are probably going to spend more time twiddling your thumbs while some RAID card spins up the drives and meditates upon infinity than you are actually booting your OS).

      For laptops, suspend(ie. with RAM still live) is almost always the right thing to do(if the ACPI gods are with you and everything is likely to come out of suspend cleanly) because laptops almost always have at least a bit of power available. Only when the system is unplugged and the battery virtually dead do you need to bother hibernating to disk or shutting down. Again, boot time not a huge deal, though likely to be faster than either of the first two cases, because the hardware is more predictable and there are fewer disks to worry about.

      Embedded stuff, though, particularly embedded stuff in certain consumer electronics, or in hostile, low-power environments, really needs to be able to wake up fast. When joe user turns on his digicam, he wants it to come up now, and he doesn't want it flattening its batteries keeping an image alive in RAM. When some minimalist sensor node with only a solar cell and a trickle-charged capacitor for company needs to wake up and transmit some data back to the mothership, it needs to spend as little energy as possible on booting, and as much as possible on sensing and transmitting.

      Since Montavista is mostly known for embedded stuff, I assume that this is why they care.

    3. Re:Sense? by wagnerrp · · Score: 2, Informative

      I have to shut it down because hibernation uses the battery and I need that power to last all the way to work.

      Standby uses battery to continually refresh the memory. Hibernation dumps the memory to disk and powers down. There is no battery consumption save whatever is needed to run the clock.

    4. Re:Sense? by Anonymous Coward · · Score: 0

      I think fast boot times are essential for a laptop, though. My graphics card and a few other things don't always like hibernating, plus with enough RAM it can sometimes be rather slow (copying 4GB to or from a 5400RPM hard disk quickly is not an easy task for my laptop). That being said, the video is definitely more concerned with embedded systems. I suspect that if linux gets preinstalled on more laptops that we may see some of the same optimizations take place.

    5. Re:Sense? by MichaelSmith · · Score: 1

      I have to shut it down because hibernation uses the battery and I need that power to last all the way to work.

      Standby uses battery to continually refresh the memory. Hibernation dumps the memory to disk and powers down. There is no battery consumption save whatever is needed to run the clock.

      Maybe thats what it is doing then.

    6. Re:Sense? by colonelquesadilla · · Score: 1

      the eeepc 701 has 512 megs of ram (many upgraded to 1gb) and 4 gb of ssd. There is rarely enough disk space available to to suspend to disk with all the space being taken up with a decent linux install and a bunch of apps and maybe some mp3s and a couple movies.

      --
      It's either false dichotomies, or the terrorists win, you decide.
    7. Re:Sense? by Anonymous Coward · · Score: 0

      dude, you need to learn about your power modes. Hibernation flushes a copy of main memory and cpu state to the hard drive and then reloads it when you start back up. The only power consumed is the power to load/unload the drive (unless you want to get pedantic like a lot slashdotters have a knack for). Standby will use up a reduced amount of battery, that's probably what you're using. What it does is stop the hard drive, and put the hardware in a lower power mode.

    8. Re:Sense? by Tubal-Cain · · Score: 1

      It always runs the clock anyways. Shutting it down doesn't change that.

    9. Re:Sense? by McGiraf · · Score: 1

      not that clock

    10. Re:Sense? by Anonymous Coward · · Score: 0

      Security updates, dumbass.

    11. Re:Sense? by Anonymous Coward · · Score: 0

      I have to shut it down because hibernation uses the battery and I need that power to last all the way to work.

      Standby uses battery to continually refresh the memory. Hibernation dumps the memory to disk and powers down. There is no battery consumption save whatever is needed to run the clock.

      No, no, no. You misinterpreted. I have a laptop as main computer at home and clearly got the meaning that GP didn't "clarify" to you sedentary masses. Even though we hibernate to save power, standby barely touches the hard drive. Remember the saying that thousands of memory accesses are equivalent to a single hard drive write?

      Well, here we are, dumping the ENTIRE contents of 2GB RAM to a file on the hard drive. Even with kernel tricks to somehow link to your already-accounted-for pagefile, the process takes 30+ seconds of strong hard drive thrashing even on powerful desktops. Hibernating is so bad that laptop's API calls to hibernate at critical levels tend to die with the last bit of batt. juice before your RAM is cloned to HD.

      Oh, and don't forget that this is only half of the process. Even if disk reads are cheaper (someone please confirm), the un-hibernate sequence has to read all this data back. It's a good thing that at least stand-by is usually supported by distros.

    12. Re:Sense? by Neoprofin · · Score: 1

      Hibernating is so bad that laptop's API calls to hibernate at critical levels tend to die with the last bit of batt. juice before your RAM is cloned to HD.

      I'm sitting across the room from a IBM T41 with a terribly abused battery that has to go into emergency hibernation more times than I've seen it intentionally shut down. My Dell E1505 has never had a problem with it either across XP/Vista/Win7.

      It's certainly a trade off though, for short periods standby is certainly faster and less power intensive, but in my experience the amount of time before that power saving is outweighed by the continual power draw is actually quite short. It's also something to consider if, like me, you frequently leave your laptop plugged in with no battery. Hibernate survives a 3AM power outage, standby loses my work.

    13. Re:Sense? by hitmark · · Score: 1

      the celeron used in the 701 and the 900 (i have one of the latter) have a issue with battery drain even when "fully" powered down.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    14. Re:Sense? by Kuraz · · Score: 1

      Standby uses battery to continually refresh the memory. Hibernation dumps the memory to disk and powers down. There is no battery consumption save whatever is needed to run the clock.

      I have a laptop with broken battery than only runs when plugged-in and strangely, hibernation only works when i keep it plugged-in. if i hibernate, unplug, move it to another room, plug-in again then somehow it has to fully reboot again.

    15. Re:Sense? by Anonymous Coward · · Score: 0

      for stuff such as this:
      http://www.youtube.com/watch?v=-l_DSZe8_F8

      Not saying that's a great example or anything, but for embedded systems, such as in-car instrument clusters, climate controls, BCM's, etc.

    16. Re:Sense? by Anonymous Coward · · Score: 0

      Unless Gnome hangs the entire system...

    17. Re:Sense? by CAIMLAS · · Score: 1

      With a mobile computer (ie one not tethered by a power cable, such as one in a car, a PDA/smartphone, or the like) can benefit quite a bit from being able to go from a power-off state to on-and-usable.

      It doesn't matter if the device has a 10 day "on but not in use" lifetime if it's still draining the battery, and the device gets used once every 5 days for half an hour at a time. That'll lead to a lot of "crap the battery is dead again".

      Also, for automotive use, it would be very useful to actually be able to use your in-dash computer as soon as you turn the ignition key (not having to wait for it to boot) without having the computer 'always on' and draining the car battery (even if it is a marginal drain - it's still a drain).

      Really, what you ask is a silly question. Your supposition of "there's always hibernation" smacks of a hate for progress. Sure, there's hibernation, (and for saving application state, etc., that's really nice). But this has obvious applications and benefits.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  17. Perverting the context much, Timothy? by macraig · · Score: 5, Insightful

    Where's the very relevant word embedded in the Slashdot title? Even TFA's author was honest enough to include it in the original title.

  18. Boot times by fm6 · · Score: 3, Informative

    I just bought a cheap digital TV that takes almost 5 seconds to boot. Sad.

    1. Re:Boot times by Tacvek · · Score: 1

      I just bought a cheap digital TV that takes almost 5 seconds to boot. Sad.

      So? Many older analog televisions took up to 10 seconds to "boot", because thats how long it took to warm up the cathode ray tube.

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
    2. Re:Boot times by feepness · · Score: 2, Funny

      I just bought a cheap digital TV that takes almost 5 seconds to boot. Sad.

      Just imagine! With this you could watch almost 4 more seconds of TV at a time!

    3. Re:Boot times by Lisandro · · Score: 1

      I`m guessing Dynex...

    4. Re:Boot times by bill_mcgonigle · · Score: 2, Informative

      So? Many older analog televisions took up to 10 seconds to "boot", because thats how long it took to warm up the cathode ray tube.

      My grandparents had an early color set that was nearly a minute. But, so what, 5 seconds, a minute, go take a pee and get a snack.

      1-second embedded linux is very significant because some vendors use proprietary OS stacks because they boot faster.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    5. Re:Boot times by Anonymous Coward · · Score: 0

      Powering the filament of the cathode ray directly from mains would have booted it in a flash!

    6. Re:Boot times by Anonymous Coward · · Score: 0

      Big Deal. I've got an old LCD TV that boots in 60 seconds... when I'm lucky.

    7. Re:Boot times by wiredlogic · · Score: 1

      You should be so lucky. I have a DVD recorder that I use as an OTA TV receiver. Unfortunately it has the same video processor as the Xbox 360. If allowed to stay in standby mode it will overheat behave erratically and randomly lock up. When standby is turned off it takes 30 seconds to boot itself up. This is one of many reasons (it can't play an audio CD without crashing) why that POS is the last Panasonic product I'll ever buy.

      --
      I am becoming gerund, destroyer of verbs.
    8. Re:Boot times by moonbender · · Score: 1

      You should be so lucky! I've got to boot my TV blindfolded, with my bare hands, out in the snow, for 60 minutes, up a hill, while strangling a dozen chicken and whistling the tune to the Family Guy theme, etc etc.

      --
      Switch back to Slashdot's D1 system.
    9. Re:Boot times by fm6 · · Score: 1

      You guess right! Fellow victim?

    10. Re:Boot times by fm6 · · Score: 1

      It's not so much the loss of TV time as the gain of thumb-twiddling time....

    11. Re:Boot times by fm6 · · Score: 0, Offtopic

      But don't do both at the same time...

      (Dude we're discussing boot times, not whining. Chill out.)

    12. Re:Boot times by Lisandro · · Score: 1

      Yeah... i'm renting an apparment in the US, and among the furniture we have two of those. You are right about that boot time being damn annoying!

    13. Re:Boot times by fm6 · · Score: 1

      I don't actually find the boot time all that annoying. Certainly not as annoying as the LCD's piss-poor viewing angle and the cruddy tuner.

      The word I used was "sad". I mean, a consumer product that can't turn on as quickly as a computer? Somebody should be ashamed!

    14. Re:Boot times by fm6 · · Score: 1

      You should be so lucky! I live in an alternate continuum where TVs have to be started by rubbing two glass tubes together and the phrase "you should be so lucky" actually means "I should be so lucky".

    15. Re:Boot times by moonbender · · Score: 1

      Now I'm confused. Did I use the phrase wrong? I just repeated what the parent post said. Not a native speaker, just acting like one, eager to learn, etc.

      --
      Switch back to Slashdot's D1 system.
    16. Re:Boot times by fm6 · · Score: 1

      I never would have guessed that English wasn't your first language if you hadn't told me. That's why I made fun of you, I thought you were a native speaker being sloppy. (Very common around here.) The post you were imitating got the expression backwards. This usage of "should" is pretty old, and confusing to the native speaker, never mind someone like you. "I should be so lucky" == "If only I were that lucky."

    17. Re:Boot times by moonbender · · Score: 1

      Makes sense. Don't worry about making fun of my usage, I do it all the time to both native and second language speakers. ;)

      --
      Switch back to Slashdot's D1 system.
  19. Re:is this new? by PopeRatzo · · Score: 1

    This is how i spent my afternoons.

    An honest man at Slashdot.

    I guess god will not destroy us today.

    --
    You are welcome on my lawn.
  20. Re:Take that! by Anonymous Coward · · Score: 0

    Ya know, trying to be all cool and insulting someone *really* doesn't work when YOU'RE not able to have a proper command of the language YOU'RE using... it just makes you look like an ass. Try again after you've gotten some education...

  21. Re:LCD Display? by colonelquesadilla · · Score: 2, Funny

    Let me check in my encyclopedia reference, I just need to find the CD disc.... oh nevermind, doesn't work in my kde desktop environment anyway, I'll just check the wikipedia...

    --
    It's either false dichotomies, or the terrorists win, you decide.
  22. Re:Link is dead already by Benaiah · · Score: 1

    Haha Made me LoL.
    Will probably be back down in a sec too though.

  23. Why not do this for desktop OSs? by bertok · · Score: 4, Interesting

    What I've never quite understood is why most operating systems boot every time like it's the first time. If you look at most operating systems, they run a bunch of scripts, initialize a bunch of things, thrash the hard drive with random read and/or write patterns, and end up.. at exactly the same state every time. Why not just capture that state, and restore it?

    If you think about it, the only differences between typical boots are:

    - The date & time
    - The type of boot (hibernation or cold boot)
    - Some USB type devices that may have been plugged in or unplugged
    - Minor logging events ('successful boot', 'need an fsck/chkdsk', etc...)

    Really, all of that work can be done in milliseconds, not minutes. Operating systems should just read the ~100MB "ready for use" image from a nice contiguous section of the disk, write it straight into memory, and then do a quick sanity check for changed hardware.

    A typical desktop SATA drive can read at 50MB/sec sequentially, so this should take, what, 2 seconds at most? On a good SSD, it should be 500ms!

    I have a high-end laptop with a good SSD, and it still takes 46 seconds to go form "pressed the power button" to "logged on and usable" with Windows 7, and I suspect it wouldn't be much better with Linux.

    The CPU utilization of typical machine booting in a VM with a very fast disk or SSD behind it is interesting to watch. It takes several seconds of 100% CPU time to boot either Windows or Linux. If you think about it, there's no useful computation that the OS can possibly be doing before it's booted. That's 100% wasted time.

    1. Re:Why not do this for desktop OSs? by flyingfsck · · Score: 1

      Well, Hibernate does does that. The only problem is that it is not stable on all machines. It works once in a while on my laptop, usually not.

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    2. Re:Why not do this for desktop OSs? by Korbeau · · Score: 1

      I half agree with you. Well, you can put your computer in hibernation/sleep mode. Works for me and a lot of folks. It does exactly what you describe.

      I even think that nowadays that should be the default option for "shutdown".

      But you still need to shutdown or reboot from time to time. And there's no easy halfway solution there. If you had to reboot for a problem, it means the original image may already be wrong / corrupted and you need to re-do all the testing and scripts. If you had to reboot for a hardware change, or kernel change etc. Well, same thing.

      But yeah, I'm all for sleeping instead of shutdown-ing being the default!

      (Note: on Windows, it should sleep 3/4 of the time and reboot 1/4 of the time, just for safe measures)

    3. Re:Why not do this for desktop OSs? by Anonymous Coward · · Score: 0

      Isn't what the GP proposes exactly the right halfway solution? By always using the same debugged hibernation image to boot up the system, there is no danger of the image getting corrupted... or at least any more danger than any other part of the hard disk getting corrupted. And that would affect the normal boot procedure as badly.

    4. Re:Why not do this for desktop OSs? by pmontra · · Score: 3, Interesting

      Don't know on other OSes but hibernate on Linux stores all the RAM on disk. I've got 4 GB of RAM and restoring them takes about the same time as booting (some 35-40s to login), getting through Gnome/Nautilus startup (so slow) and restarting the apps I need. The real boot time to a useful desktop is about three minutes. Hibernate is not faster than that and a shutdown is much faster than writing those 4 GB to disk. Furthermore hibernate doesn't work well on my laptop. I think it's the video driver not restoring the video card state correctly (the radeon open source driver).

    5. Re:Why not do this for desktop OSs? by Anonymous Coward · · Score: 0

      Do "echo 3 > /proc/sys/vm/drop_caches" before hibernating and you will be amazed. Even better, install tuxonice and select "Compressor lzo" and "ImageSizeLimit nocache" for a much improved performance. You can even play with ImageSizeLimit value, but then you are hitting tradeoff between slower hibernation (because some of the memory is being pushed to the swap) and faster resume, but with the need to unswap some data - at least until compcache works with tuxonice,

    6. Re:Why not do this for desktop OSs? by Anonymous Coward · · Score: 0

      Except that hibernation still drains electricity. If you turn off your computer while it is hibernating (or it drains its battery), you loose loose the "unsaved" information, and have to reboot.

    7. Re:Why not do this for desktop OSs? by Fishchip · · Score: 1

      That still doesn't solve the problem of system changes. Core system program updates, new drivers, whoops, gotta make a new boot image.

      I'm all for hibernation but this restore-from-image booting could only work for people who won't mind constantly making new images.

    8. Re:Why not do this for desktop OSs? by Anonymous Coward · · Score: 1, Insightful

      No, it doesn't.

      Hibernate stores the machine state on HD when you decide to stop working, and then restore it upon reboot.

      What the grand parent post suggests is that a certain machine state, always the same, be restored in the typical boot.

      I can imagine an "Hibernaboot menu" where the user can choose one among several stored machine states.

    9. Re:Why not do this for desktop OSs? by evilviper · · Score: 3, Informative

      What I've never quite understood is why most operating systems boot every time like it's the first time.

      Because you told it to do so. If you didn't want it to reboot, you should have suspended or hibernated the system instead.

      Really, all of that work can be done in milliseconds, not minutes. Operating systems should just read the ~100MB "ready for use" image from a nice contiguous section of the disk, write it straight into memory, and then do a quick sanity check for changed hardware.

      You've reinvented Hibernate mode, with it's existing limitations, and more mistakes you've added... Anyone who's used hibernate know it mostly works, but some devices need to be more fully initialized (like your video card) and starting to use it when it's in a different state than it last was, is a sure recipe for disaster. Despite claims to the contrary, I'd say S3 Suspend is easier to get working CORRECTLY, than Hibernate, and with power requirements less indistinguishable from the "off" load, and boot times of <2 seconds, S3 is far better all around.

      I continue to use this old PC (Socket-A MSI Mobo) as my desktop because S3 Suspend mode works (almost) perfectly with FreeBSD-6.x. The ability sit down at my PC, hit the power button, and have all my apps open where I left them (not just the minimal OS up and running) is incredibly valuable. It's a real shame so few people have had the opportunity to experience it. In addition, it's great to be able to just get up and walk away from my computer at any time, for any reason without giving it a second thought... because in 10 minutes it'll be using no power, and when I come back, it'll be right where I left it. Never mind the implications for a UPS-powered system, like a system left right where it was when you last used it, which can be powered from the smallest battery for hundreds of hours, easily.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    10. Re:Why not do this for desktop OSs? by Anonymous Coward · · Score: 0

      "If you think about it, there's no useful computation that the OS can possibly be doing before it's booted. That's 100% wasted time."

      If you think about it, if you don't boot at all, no computation will be done. How on earth can you believe that a computer is doing _nothing_ while booting?

    11. Re:Why not do this for desktop OSs? by CAIMLAS · · Score: 1

      I have a high-end laptop with a good SSD, and it still takes 46 seconds to go form "pressed the power button" to "logged on and usable" with Windows 7, and I suspect it wouldn't be much better with Linux.

      Wow, seriously? I've got a Hitachi RAID1 (mdraid) in Ubuntu 9.04 and it takes maybe 20s to get to the X login screen from POST. It's a little longer in 10.04 on similar hardware, but then I haven't bothered to prune unneeded services - still no more than 40s or so. I don't have the time to get up and get a glass of water from the kitchen, at any rate (a 25 foot distance from where I sit).

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    12. Re:Why not do this for desktop OSs? by Graff · · Score: 1

      What I've never quite understood is why most operating systems boot every time like it's the first time. If you look at most operating systems, they run a bunch of scripts, initialize a bunch of things, thrash the hard drive with random read and/or write patterns, and end up.. at exactly the same state every time. Why not just capture that state, and restore it?

      Mac OS X pretty much does just this. It uses several files such as BootCache, BootCache.playlist, and Extensions.mkext to store a preset startup state that it can load fairly quickly. There still need to be some sanity checks to make sure that hardware and software haven't changed but overall the Mac OS X boot process is pretty quick.

      Here's a good summary of the boot process for Mac OS X. It's a little old but most of it is still relevant.

    13. Re:Why not do this for desktop OSs? by AlgorithMan · · Score: 1
      --
      The MAFIAA is a bunch of mindless jerks who will be the first up against the wall when the revolution comes
  24. And 800ms of that is clock stabilization. by jthill · · Score: 1

    Of that time, 800 ms are spent just stabilizing the clocks.

    --
    As always, all IMO. Insert "I think" everywhere grammatically possible.
    1. Re:And 800ms of that is clock stabilization. by marcansoft · · Score: 1

      No, of 1.5 seconds. The 1-second mark is a guesstimate based on subtracting power sequencing time from the actual 1.5-second mark, approximately.

  25. Re:Link is dead already by Yvan256 · · Score: 5, Funny

    Way to spoil the ending of the new Zelda game.

  26. Obligatory sov-joke by Anonymous Coward · · Score: 0

    In Soviet Russia - Linux boots you!

  27. Am I the only one.... by Neffirithion · · Score: 1, Offtopic

    ...That found it ironic that the name of the company that appears to specialize in Linux solutions has the word "Vista" in the name of the company? I mean, how old are these guys? was this planned?

    1. Re:Am I the only one.... by Anonymous Coward · · Score: 0

      If you even bothered to waste 2 seconds to google (hell, even run a whois on montavista.com), you'd know MontaVista has been around for almost 15 years.

    2. Re:Am I the only one.... by Ant+P. · · Score: 1

      They've been around since before Longhorn even had a name.

  28. Already done faster... by Anonymous Coward · · Score: 3, Informative

    This is nothing really new. In fact, they boot slower on a faster processor than earlier acheivments. This is mostly an ad for MontaVista.

    See http://elinux.org/Main_Page for a lot more information om bootup.

    I think the record is about 200ms by Sony.

  29. Nah by Colin+Smith · · Score: 1

    Really not so much.

     

    --
    Deleted
  30. How would it know this? by SmallFurryCreature · · Score: 2, Informative

    Typically the only reason my linux machines get rebooted is precisely because the hardware HAS changed. Or the kernel has. What other reason can there be to reboot?

    And as for your assertion that linux wouldn't be any better, I get a cheap netbook with a joke SSD and it boots faster. (Aspire One ZG5)

    Windows boot time is not entirely fair however, it tries to do a lot of things. People think that all a computer does is draw a desktop, but to get all that in order a lot of hardware has to be configured and this includes dealing with delays. For instance spinning up the HD's and allow them time to report. There is often even a bios setting to allow extra delay's so slower hardware has time to respond.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  31. Re:Who cares about this? by amnezick · · Score: 0

    14:33:25 up 26 min, 2 users, load average: 1.39, 1.04, 0.50

    --
    mov ax,4c00h
    int 21h
  32. It's good, but ... by DrogMan · · Score: 2, Interesting
    I'm not convinced it's that big a deal, although if they can sell it for £5K then good luck to them!

    I build little embedded(ish) systems myself - AMD Geode boxards (ALIX) and my custom compiled kernel boots in 1.08 seconds (according to kernel output) If I didn't compile in networking and USB, I'm sure it would be under a second.

    The biggest time is the boards BIOS (5 seconds), then loading the image off flash then the kernel uncompressed and boots - 1.08 seconds.

    If I had more access to the board and had 4MB of flash ram as part of the memory map, then I could eliminate the long BIOS + Load times and jump into kernel on cycle 0. That's where the trick is, I guess - a fast load of the kernel into RAM, or keep it in FLASH that's part of the memory map.

    After the kernel is loaded it's just userspace - I run a cut-down system, but it still takes another 15-20 seconds or so to get time, dns, networking, apache, etc. going. You're probably not doing that with an in-car device or a camera, etc.

    So it's not really hard to make a kernel boot fast and possibly even launch one application - the big savings are going to be on the hardware when you can eliminate BIOS and load times, and the amount of userland you then have to load - which is the real difference between "embedded" and general purpose (e.g. desktop)

    1. Re:It's good, but ... by drinkypoo · · Score: 1

      The biggest time is the boards BIOS (5 seconds),

      AMD Geode and its companion chips are allegedly well-supported by coreboot. I thought PC Engines stuff was supported already? Have you tried coreboot with a linux kernel payload?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:It's good, but ... by DrogMan · · Score: 1
      Not tried it - the board I'm using is the PC Engines one - supported in the depreciated V3 of the code.. (which means it'll be back-ported to the supported V2 version eventually according to the site)

      I currently use the on-board "BIOS" to PXE boot them first time round which I then use to write the image to the compact-flash card, so keeping that around is handy.

      However, I can live with the boot time of my units - little Linux/Asterisk boxes. They boot fast enough for this purpose, ta!

  33. One second boot perfect for ATM machines by noidentity · · Score: 1

    This one second booting will be perfect for ATM machines, so you don't have to wait to enter your PIN number.

    1. Re:One second boot perfect for ATM machines by r_cerq · · Score: 1

      That statement shows a severe lack of understanding on IT Technology... The PIN number doesn't need a boot of the whole OS system to be processed, all relevant information should either be in RAM memory, or contained in the card itself...

    2. Re:One second boot perfect for ATM machines by pv2b · · Score: 1

      ATM machine, PIN number, IT technology, OS system, RAM memory. Oh my. Tell me you and gp did that intentionally. :-)

      You also need to consider the time it takes for data communications over the WAN network (hey! there's another one) to verify that the machine should not - in fact - eat the card, because it's been marked as stolen or lost. Or, check if the card is actually valid. All that kind of stuff takes time when done over whatever ancient network for ATMs is in use in your country.

      Besides: ATMs are booted all the time. It's not like they have a (user-accessible) power switch. You just stick your card in. So boot time is not an issue, except for impatient service personell.

    3. Re:One second boot perfect for ATM machines by r_cerq · · Score: 1

      The first rule of the tautology club is the first rule of the tautology club :)

      And coincidentally, I do have a fair amount of experience with ATMs (probably outdated by now, though). Boot time, at least in my country, isn't a factor: nowadays, most of them actually run a stripped down version of Windows 2000...

    4. Re:One second boot perfect for ATM machines by noidentity · · Score: 1

      Excellent, I forgot about those acronyms as well. I was drawing a blank in my original post.

  34. Re:Take that! by hairyfeet · · Score: 4, Funny

    Now where did I hear something like that? Oh yeah here. Funny how every thread here on /. has at least one section where this would fit.

    --
    ACs don't waste your time replying, your posts are never seen by me.
  35. Idea for Swiftboot by LifesABeach · · Score: 1

    Could the Swiftboot people consider making Ubuntu boot in 1 second? Sweeeeeeeeeeeeeeeeet

  36. You young wippersnappers... by fm6 · · Score: 1

    ...don't know how good you got it. The first computer I learned to boot was a PDP-8 with no boot rom. The only mass storage medium was punched paper tape. Booting consisted of setting the front panel switches so that the first few bytes of RAM contained a program that said "read the paper tape and execute it". Then you loaded the OS tape into the reader, prayed that it wouldn't jam or tear, pressed a button and waited a couple minutes.

    1. Re:You young wippersnappers... by TheHawke · · Score: 1

      And you probably used a teletypewriter to code with too. Put a sock in it old man, at least they are going forward.

      --
      First rule of holes; When in one, stop digging.
    2. Re:You young wippersnappers... by fm6 · · Score: 1

      Of course I used teletype. Except for batch machines, for which I used a keypunch. And of course with punched media, there's no such thing as a delete key. (Shudder.) Don't think for a moment that I'm the teeniest bit nostalgic!

  37. Re:LCD Display? by Anonymous Coward · · Score: 0

    gotta run it in wine if you gotta have windoze. appropriately named but misspelled, I'm certain they had whine in mind. Besides, Linux users don't need an encyclopedia, we already know it all. :)

  38. WoW by Anonymous Coward · · Score: 0

    WoW.... it is cool... damn cool.. mind blowing.
    now, lets get over it....

  39. WinCE boots instantly by Anonymous Coward · · Score: 0

    What's the big deal? Is it because someone made a video, and NOW you can understand?

    I've been using a couple of WinCE portables that boot instantly for almost 10 years.
    They support a version of MS Office, but I use them primarily for browsing, email and Google apps.
    They were made by Sharp and I got them on sale for $100 each.

    The netbook is NOT a new concept!