RAQCOP = IPCop + Cobalt Raq, Cobalt Raq Firewall Applicance Software, Velociraptor Software Upgrade.

No, not by a long shot. Since all the activity is with IPCop 2 svn, I have been quietly keeping a Cobalt Friendly build tree along with what is in SVN and uploading images for Cobalts as well as the diff file from svn. I also have a nice Raqcop 1.4.23 tree going should the 1.4.22/23 pair ever get released as an update in IPCop. The 1.4 branch will likely go away sooner than we think.

Despite recent surgeries, I have gotten a lot of work done in the area of kernel patching. For 2.6.39 I had to make a LOT of changes to the Cobalt drivers due to unbeknownst to me, deprecated definitions and calls that were completely forced out by 2.6.39 yet had been deprecated in previous versions, but now have it down to one warning in lcd and i2c. IPCop is still using 2.6.32 so I am way ahead of the game there. My Debian server on my Raq XTR is running 2.6.39 now. It is also my Squeezebox server for Logitech nee Slim Devices streaming music products.

The next thing to go is the old IDE drivers we have been using and the same ones used in the rom kernel, they are deprecated in 2.6.39 but still there. I just redid a 1.9.20 Cobalt build of IPCop with the new PATA drivers embedded. The rom sees the first partition as hda1, the kernel used to run IPCop sees it as sda1 so I was able to set the root as sda1 in the rom and the boot as hda1. Once the rom sees where the kernel is and loads it, then the rom looks for the root device based on how the kernel you just loaded from boot sees it. Of course if root and boot are md0 no changes need to be made. I'll have detailed instructions on the next upload I do. I still need to test on two other machines.