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?"
Linux + hibernate (swsusp, TuxOnIce) functionality.
No sig, sorry.
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.
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
DSL linux is really fast when installed on a Hdd.
Just to be clear: You intend to have old machines sitting around unpowered and then someone WALKS UP TO THEM and presses the power button. The user then waits for the OS to boot and does his thing. Correct?v
So what are these systems being used for? Kiosks? This is critical to determining what you need. For example, QNX boots very quickly but it's an embedded Unix system. But QNX probably won't run whatever app it is you want to run on these systems.
Basically, you said they are going to be application appliances. WHAT application?
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
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.
Buy Text Processing in Python
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.
Can you afford the extra electricity to power the old PC, and the extra air conditioning to get rid of the massive amounts of heat that old thing is going to put out?
The old things don't put off heat... Listen to yourself. I can't tell you how many Pentiums/K6/Cryix based systems I've seen with no fan but the one in the PSU. Oh and the PSU's, when's the last time you've opened an old computer and found anything higher then 250-300watts max? Can't say that I have, ever. In fact when I received 6 Pentium D's a few weeks ago from an office upgrading all there kit all they came equipped with mere 250w PSU, and those are somewhat modern systems based on an architecture that was known for reaching up to 115 W in 3.6-3.8 GHz Prescotts. So yeah I think your point is moot and your talking out your ass. But we'll never know :) He didn't specify the hardware.
On the Oregon Cost born and raised, On the beach is where I spent most of my days
Why do good posts like this so often get modded badly, while FALSE posts like those contradicting it get modded insightful.
Read:
"Splashtop is preinstalled on the hard drive or in the on-board Flash memory of new PCs and motherboards by their manufacturers. Splashtop is a software-only solution that requires no additional hardware. A small component of Splashtop is embedded in the BIOS of the PC - that's the part that runs as soon as you press the power button."
This should make it obvious, along with the couple intelligent posters who noted that it can boot from an HD.
Maybe Slashdot needs to start restricting mod points to those who aren't idiots?
I disagree.. he wants a complete OS/environment.
http://www.qnx.com/
you can get it's complete kit free nfor non commercial use. is INSANE FAST at booting if you do it right and is small.
Do not look at laser with remaining good eye.
All well and good he wants to "save money" and re-use existing hardware, but changing an OS is going to mean a LOT of time, testing, and likely new software. The cost of this will FAR out shadow the costs of a new piece of compatible hardware...
Of course, before you can ask what OS to run, we might want to know what applications it's being used for... and why exactly would an application appliance be powered off? this obviously isn't a database that gets regular attention, or any kind of security device, backup system, or other management system. so...
I'm assuming we're talking about legacy apps here then. In that case, I'm CERTAIN you have idle space and CPU time on existing servers. Throw a VM in there, and use that. When idle (hibernate, wake on LAN) it should use no more energy that the host would be when idle by itself, and if that host is a machine that DOES have to be on 24/7, then you're effectively using 0 additional power. It will wake on LAN in 15-30 seconds, maybe faster, and can auto hibernate again when idle. Simple, clean, and as a bonus, you can move the old hardware to your DR or testing lab.
There is no contest in life for which the unprepared have the advantage.