To maintain ease of readbility as well as some form of order to the submissions of source code for the U4X distribution. We ask that all developer please read the 'Coding Style' referance for kernel submissions. This document can be found in your /usr/src/linux/Documentation/, listed as 'CodingStyle' or can be downloaded through our ftp site at ftp://ftp.u4x.org/pub/u4x/documentation/CodingStyle
Also, please take note that we ask the developers to place a header in each of their source code files, stating certain things such as copyrights, a desciption, and some extra legal jargon. A template for this format can be grabbed via FTP at ftp://ftp.u4x.org/pub/u4x/documentation/headertemplate.txt
Lethal has once again done amazing work as he has submitted a new patch for the kernel to me this afternoon. It seems he has changed around some of the modifications and included a few more patches (more details will follow after final stress testing). Listed below are the speeds (in minutes and seconds) that were acquired through the use of 'time' on updated.
On an unpatched 2.2.10 kernel, real (0m56.668s) user (0m9.080s), and sys (0m7.660s). On a 2.2.15 (above kernel with the modifications), real (0m22.916s), user (0m12.801s), sys (0m9.965s).... read more
Lethal amazed us all last night, Tuesday May 23rd, as he was able to complete the miraculous feat of compiling AND BOOTING the U4X / Linux Kernel (with its added modifications) on the VERY FIRST TRY. After running a small amount of tests Lethal estimated that we were at a possible 15% performance increase (goals have been established at 20%, as of last night). Profiling, and the proverbial 'fat-trimming' will be begin later this week.