How to finish Linux kernel 2.6.x ?
Linux kernel 2.4.32 is a network operating system. But you have to use repositories in the grid to run data. Linux 2.6.x is a local preferenced distributed data operating system. Its been three years since the birth of Linux kernel 2.6.x and no finish line in sight. The reason is confusion.
Linux 2.4.x is a hdd virtual memory operating system, which is not usable for local preference database, Kernel 2.6.x has to use large ramdisk for data for speed.
Linux kernel 2.4.x has all the generic drivers, but they can no longer be used. Kernel 2.6.x uses udev and /usr drivers beyonf drivers used in bios. Mepis took the first step to make 2.6.x an event to provide correct drivers.
Kernel 2.4.x has Dhcp and dhcpcd for network operating system, but kernel 2.6.x has to have unionfs to synchronize mysql data in the ramdisk to the microsecond for data accuracy. 2.4.x still uses synaptic for software update.
All the major linux distros have to use official kernels released by Linus to conform to partition, directory and file name so languages, scripts and design tool kits and emulations can not be broken in bindings.
With tiny Linux distros, this is not difficult; but for major distros who changes kernels, the number of bugs to be fixed is not worth the troubles. As it is Linus kernels are already moving targets, difficult to comply to keep dependency compatible.
We can see Novell still has work to do on script binding maintainence. Fedora is just blowing the wind. Mandiva is lost in the forest.
Hopefully, all three major look at Slackware codes and see how to integrate 2.6.x into 2.4.x kernels. Then work out the minimum requirement of partitions, directories and file names to keep all the bindings along with all the hardware ports. Scritps amy have to be updated with Linus kernels. Terminals may have to include complete linux commands as each new kernels appear.
This is just a start(first step in the 10,000 mile journey) in the right direction to keep sanity in the Linux world.
- Login or register to post comments
- Printer friendly version
- 1857 reads
Kernels 2.6.x needs work ?
Udev is to provide drivers and functions of chipsets beyond what is provided in bios already. Vista has componentized driver functions. It uses a template to guide the assembly of componentized drivers. It can do XP into Vista but not yet have templates for other Microsoft operating systems. Udev has to be componentized to add svga driver components on top of VGA in bios.
Unionfs is more difficult to comprehend. Its a server feature. Since database is so large now a days. The data is stored in grids or blades of repositories. They are in localities that the datbase knows. Kernel 2.6.x will use unionfs to sunchronize database from all the repositories of the latest data; so that in kernel 2.6.x the latest data is in your computer's ramdisk. You computer has constant feeds from all the repositories you desire to keep data fresh.
Ramdisk memory allocation needs work because of hdd virtual memory being slow is now treated as a repository as well. Unionfs has to keep the data no lomger fresh in the USB terabyte hdd downloaded for permanent storage.
These three areas had to be addressed before we can sign off the kernel 2.6.x project. It seems we will take another year, perhaps. Linus and Andrew have to focus on udev and unionfs(input and output) before any other distractions.
Fortunately, udev and unionfs are preplanned ?
They reside in your install script?
You can use hal to get all the repository feeds once you boot into browser?
You can use schedule to download old data in your ramdisk by garbage collection and dump into USB terabyte hdd.
Do we still need one year to overcome all that confusion?
Unfortunately, udev and unionfs require Rtos ?
If udev DSP, soundchip, asic, fpga, etc., firmware and operating system are componentized; you may have less than 100% compliance. Reduced instructions if you will. Then you can operate the device in threads, each thread cover one function. This give us the opportunity of choosing our performance in realtime. The same reason that Vista is in realtime.
Unionfs is the same way. The feeds and garbage collection to and from ramdisk resources had to be in realtime and massive parallel operation. Rtos can handle this function much better than Linux kernels.
This leads to Linux 2.8.x, microkernel development. Small files of machine language to setup one function and process data in threads for multitasking. Never windows only for multitasking.
So, people do not use udev or unionfs in desktop is perfectly ok(Slackware advocates). They are server applications. Back to tiny Linux, here we come.