Slashdot Mirror


Fast-Booting OS for Usually-Off Appliance PCs?

An anonymous reader writes "I have some older computer equipment at work that I want to re-purpose as application appliances. The machines will sit, unpowered, until needed, then powered up. No way around the 'sitting powered off' — company directive. What is the quickest-booting OS I could use for them? I know about LinuxBIOS, but that would require new hardware, which does not go along which the re-purposing theme. Some of them do not need to be connected to a network, so an old version of Linux or Windows 98 are possible. DOS is too old to consider. So what are my options?"

6 of 523 comments (clear)

  1. BeOS? by Chonine · · Score: 5, Informative
    Back in the day, BeOS booted in 6 seconds to a fully usable desktop (6 seconds after the POST). I don't think that is what you are looking for though, and I don't know how far the Free clone, Haiku, has come.

    More realistically, there is this interesting Linux distribution, Webconverger:

    http://webconverger.com/

    I've used it for a few web-only systems. Boots up fast enough. Use it as a starting point to tweak. Basically, firefox becomes your operating system and UI. Neat idea.

  2. re by JohnVanVliet · · Score: 5, Informative

    there is " damn small linux " http://www.damnsmalllinux.org/ you could even install it in the /boot partition of fedora as a backup os

    --
    "I don't pitch OpenSUSE Linux to my friends, i let Microsoft do it for me
  3. DSL and Puppy by steveha · · Score: 5, Informative

    Take a look at DSL and Puppy Linux. Both are tiny and would boot quickly from a CompactFlash. DSL is probably better for all-around appliance use; Puppy is intended for use as a desktop OS.

    http://www.damnsmalllinux.org/

    http://www.puppylinux.org/

    steveha

    --
    lf(1): it's like ls(1) but sorts filenames by extension, tersely
  4. BeOS by Lulu+of+the+Lotus-Ea · · Score: 5, Informative

    BeOS really was pretty amazing in this respect, and some others. Multithreading was far ahead of anything else at the time, and probably since, as well. On some older machine (P3-ish; much slower HDD than nowadays) I clocked boot time at 15 seconds, OS/2 and Linux distros of the time were more like 1-1.5 minutes on the same hardware.

    The way it booted so fast was largely by deferring a lot of the "initialization" stuff until the system was "booted". This is nothing like the awful way Windows (and to a lesser extent KDE/Gnome desktops) keep loading stuff for a good while, letting you see the desktop for a minute before you can really do anything. Under BeOS, said multithreading was well utilized to give you a responsive GUI right at that 15 seconds, but still do background loads of various background processes that you didn't *really* need immediately.

    Of course, if you immediately launched something that *did* need the services of something loading in a background thread, you'd obviously have to wait a few more seconds. But even all that background loading was very efficient, and practically, by the time you could make a few clicks, it was loaded.
     

    1. Re:BeOS by blueapples · · Score: 5, Informative

      we'll never know what could have been.

      Maybe we will - http://www.haiku-os.org/

      --
      www.blueapples.org
  5. Re:Splashtop by hairyfeet · · Score: 5, Informative

    Use either DSL or puppy. I have used both on older hardware and installed on the HDD the boot is very fast. You could probably speed up the process even more if you compiled it for the specific hardware.

    --
    ACs don't waste your time replying, your posts are never seen by me.