So very, very true.
Note: This article is part of my Testing stuff with QEMU series.
MenuetOS is an operating system with a monolithic preemptive, real-time kernel, including video drivers, all written in FASM assembly language, for 64-bit and 32-bit x86 architecture computers, by Ville Mikael Turjanmaa.
MenuetOS development has focused on fast, simple, efficient implementation. It has a graphical desktop, games, and networking abilities (TCP/IP stack), yet still fits on one 1.44MB floppy disk. It also facilitates easy, full-featured assembly language programming. This stands in marked contrast to the (as of 2007) widespread view that assembly languages are useful mainly for old and embedded systems.
Testing (the GPL'd) MenuetOS in QEMU is easy:
qemu -fda M32-084.IMG -m 384
There's also Menuet 64, written in 64-bit assembly, but that's not open source'd for some strange reason I don't understand. But you can try that one, too (the binary images, that is), using QEMU:
qemu-system-x86_64 -fda M64-059.IMG
I did not yet perform any long-term tests, i.e. measuring the average consumption over multiple days or so, only some quick ad-hoc checks. I just recorded the number of watts the respective device used when powered on.
Here are the results:
By removing all devices which draw more than 0 watts in stand-by mode, I was able to reduce the overall (useless) energy consumption (and costs!) quite a bit.
I also replaced a bunch of 40 W and 60 W lightbulbs with energy saving lightbulbs which are equally bright, but only consume 8 W or 12 W respectively. On the long run you can save quite some amount of energy (and money) with them. They do cost a little bit more than normal lightbulbs, but save lots of electricity costs and they also last a lot longer (8000-15000 hours vs. 1000 hours according to Wikipedia).
As I recently bought a NSLU2 ("slug") for 24/7 server usage and random ARM-based development (more on that later), I'm looking for a suitable storage device to use as the root filesystem for a complete Debian system.
The requirements are:
The last item is the most important.
The obvious choice is a USB memory stick, but unfortunately those are flash-based and only survive a certain number of write cycles. Thus I'm looking for something which at least survives enough write cycles to make it usable for a few years...
I do know several ways to reduce the number of writes via software, that's not what I'm currently interested in. I'd like to know which storage types will survive the longest amount of time (because of their hardware properties).
Has somebody else done something like this before and can share some experiences as to which storage type is best suited for such a scenario? I suspect my slug will be mostly idle, but there might also be phases where it runs on 100% CPU and heavy disk I/O for multiple days in a row...
We're happy to announce that the LinuxBIOS project will have the possibility to take part in this year's Google Summer of Code™ (GSoC) program. coresystems GmbH was accepted as a mentoring organization for the GSoC and will mentor all LinuxBIOS-related projects.
There is a GSoC page in the LinuxBIOS wiki which collects a few ideas for student projects, among others:
Feel free to post more ideas and wishlist items to the LinuxBIOS mailing list.
If you're interested in applying for a project, you need to hurry up. The deadline is March 24, 2007!