Saturday, June 24, 2006

An attempt to create a MusicalOS

"Let there be music." - I wished and there was music.

Here we go:

  • 650 MB of code for GUI Applications.
  • 100 MB of code for supporting drivers/libraries.
  • 220 MB of code for Fonts Servers/Network drivers.
  • 300 MB of code for E-Mail clients/SBIN apps.
  • 1 GB of code with other XYZ apps.
Do one require all the above for just playing a list of songs that (s)he wishes to listen?? There's a lot that could be stripped down! This is how it goes the fantasy of making a MusicalOS from scratch.

MuscialOS :: What is it all about?
Its just a distribution, that has minimal features required to play a list of songs that is stored in a secondary storage. GUI support is not provided. The generic we extend our requirements, the bigger the kernel and the loadable module gets. Hence, to be more specific, the requirement goes like this, we just need a keyboard support and a console support in whose command prompt, commands could be invoked to play a list of songs and nothing else. No USB/Floppy/any XYZ devices please. Spare Harddiscs/CD-ROMs.

Minimum requirements
Though, building from the scratch requires a list of files to be build and other stuff to be decided at length, we just make a jot of what are the necessary modules without which our life would be under serious trouble! :)
  1. Sound support - Very Trivial, its where we depend on, isnt?
  2. Filesystems - Trivial, otherwise, no access to data!
  3. Terminals, Console drivers - Trivial, else would be a blindman's box!
  4. Device supports - Keyboard, Mouse, Monitor, CD-Rom drivers - Required.
  5. Anything else??? (Still thinking!)
First Step
As a first step, Kernel v2.6.17-1 is compiled with network support removed and a CRAMfs initrd image is made with modules. And Eureka, the box boots. We've just started :)

No comments: