What is Linux 2.6.x and why the delay ?

Linux 2.4.x was stable at 2.4.22, because it is an intranet operating system. Modifications since were added to use Linux 2.6.x package addition.

Linux 2.6.x is an enterprised system to work on internet with distributed data in grids, blades and portals(virtual desktops). It pulls data from the distributed network and process them locally in ramdisks. This speeds up distributed data processing.

Fortunately, Linux 2.4.22 with livecd can use ramdisk entirely if dram size is sufficient. So, Linux 2.6.x uses udev and hotplug on the hardware and unionfs to store data on repositories based on copy on write principle.

But in realtime, Linux 2.6.x has to have unionfs supervise new data download from repositories to update the ramdisk data locally. this means unionfs on repository will download to local unionfs automatically by copy on write to synchronize data locally and on the network.

Until unionfs has been programmed correctly on servers as well as desktops, Linux 2.6.x will be fumbling along for another year.

Unionfs is two parts on the network. first it must find the repositories and the ramdisks to synchronize data.

This delay is caused by lack of understang of cron jobs and synchronization of distributed data(xml database or packet storage) structure.

Hope this explaination will speed up unionfs development quickly with plug-ins of synchronization(file manager) and cron jobs(batch processing tasks) in addition to use search engine(finding repositories or ramdisks) properly at the beginning of a session for coupling of ramdisks to repositories.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Unionfs and file manager in compressed drives ?

Unionfs is a file system that offers the automation of data synchronization, but still lacks batch jobs dirctives in repositories. Which ramdisks to send the new data, copy on write.

The importance of unionfs managing fiel manager is the key, to use write back instruction to keep dynamic FAT tables accurate. This means we have to use compressed drive(tgz). Compresed drives in hdd or ramdisks can handle dynamic FAT table without overflow of data storage in hdd or ramdisks. Oh, yes, repositories will also be run on ramdisks, overflow-ed into hdd or USB drives into swap files. Hotplug 127 USB drives(terabyte flash) will be a quick fix on emergency memory(dram) shortages developed during any session.

Now the unionfs is more or less designed correctly if search engine can extablish the Enterprise distributed network of any Linux 2.6.x operating system at the beginning of any session.......updating data from repositories..............

What is Unionfs without XML databases ?

If unionfs ia design properly and can transfer data. It still has to transfer data in the database formats.

So, are we taking care of DB2, Oracal, first; or SQL, Mysql, etc. by Linux defaults ?

It depends on how big an enterprise system your computer is networked.

After all, unionfs is slave to the databases. We are back to the 1 year time table for Linux 2.6.x stable version, unless Knopper talks to IBM and Oracle to have help with some proprietary codes security related?

What is unionfs without security(trust and credentials) ?

The unionfs data transfer involves many security issues related to sensitive data.

Unionfs has to establish cookies to verify trust and certification or credentials. Since certification can be duplicated, credentials or qualification would be more dynamically suitable.

Quality control is traceability. Traceability in cookies is just a part of trust. There are many other data specific in a computer operating system that gives credentials. email, application software, IP address, etc. You add whatever makes you happy, but since computers and people are dynamic, you have to use weighted fuzzy logic to keep out the good guys and luckily the bad guys too.

Trust is credentials not certification. You have to earn your trust. Eventually, we will get the security issues qualified.

What is Linux 2.8.x and unionfs ?

Linux 2.8.x is now prposed to ride on Prex(microkernels) for its role in cellphone and Linux operating system. So, we can have threads on the cheap.

Once threads can be dynamically added by Mosix. Unionfs will have dedicated threads for any last minute copy on write data transfer in segmented packets. This approach will enable massive parallel computer network system on virtual networks.

So, the development of unionfs can be in parallel on Linux 2.6.x package as well as working transparently in Linux 2.8.x with Prex package using modified Mosix to balance thread loads.