[cAos-devel] My recent spate of commits

[Tim Leger]

Hi Mike,
>> Granted version 2.2b was released at the end of October last year,
>> but the kernel in the release is almost a year old.
>>     
>
> Now let's be fair.  2.6.17.11-103.caos is the kernel on the 2.2b
> install image, and 2.6.17.11 was not released until August 23rd of
> last year.  So "almost a year old" is a 6-month exaggeration. :)
>
>   
Yes, my mistake, the kernel in 2.2b is at most 6 months old.
>> That said, the 430 MCP chipset has been on the market for more than
>> a year.  That's why I was so surprised the the cAos 3 (beta 3) was
>> able to detect and use everything on the motherboard without any
>> issues first time.
>>     
>
> Perhaps Greg has been making updates to sidekick/detect which need to
> be backported to caos2....  :)
>
>   
>> I have not seen a newer version for cAos 2 than 2.2b on any of the
>> mirror websites.  Is there another version being hosted somewhere
>> else?
>>     
>
> Only if you count my hard drive. ;-)  As I said, I've been waiting for
> the libxml2 update which Martyn so graciously provided; now that it's
> been pushed into the core, new ISO's will be forthcoming.
>
>   
Fantastic, can't wait to try them out.
>> For me personally, a package called systemimager is a must.  Under
>> cAos 2.2b I was able to just use the RPM's available for it and
>> everything worked fine.
>>     
>
> We do have a systemimager package in our repository as I was the
> original packager for SI back when Brian and I worked at VA together.
> My involvement died out when VA laid us off as I no longer had the
> equipment to handle SI any longer.
>
> If you'd like to take a look at the failures and maybe help get them
> resolved, the autobuilder log is here:
>
> http://mirror.caosity.org/cAos-2/ext/autobuilder/i386/00_LOGS/cluster/systemimager/systemimager.log.broken
>
>   
I noticed the autobuilder is using a somewhat older version, 3.2.2.  
According to the systemimager wiki, the latest stable version is 3.6.3 
(released March 6, 2006) and works fine under cAos 2.2b, just not under 
cAos 3.  I can put up a short howto on installing the 3.6.3 version 
under cAos 2.2b on the wiki if you like.  While I can't get the 3.6.3 
version of systemimager to build properly under cAos 3, I was able to 
get the latest "unstable" version 3.7.6 released last month to build ok 
under cAos 3.  However, while using the si_prepareclient  tool, it fails 
with this:
>  >> mount /etc/systemimager/boot/initrd /tmp/.systemimager.1 -o loop 
> -t ext2
> mount: could not find any device /dev/loop#
>  >> rm -fr /tmp/.systemimager.0 /tmp/.systemimager.1
>
> FAILED: mount /etc/systemimager/boot/initrd /tmp/.systemimager.1 -o 
> loop -t ext2 at 
> /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm line 921.
Sadly, I have not had time to look into this further yet.
>> I'll have to get you a report on this (what I tried and what went
>> wrong), maybe you can figure it out or possibly even work in
>> conjunction with the systemimager folk, just my 2 cents.
>>     
>
> Mention my name to Brian Finley and/or CC me in on your conversations;
> we've worked together numerous times before to resolve SI packaging
> issues.
>
>
>   
Will do, as soon as I get some time to work on this again.  Thanks again 
for all your help!