Perhaps I should have been a little more explicit as there are really 2 things going on.  The first is I was trying to image a
system that had perl 5.8.5 installed on it.  SystemConfigurator died when it was run at the end of the installation script because perl couldn't find AppConfig!  Once I found one that would install into the 5.8.5 tree, everything seemed to work just fine.  That caused me to realize that although there may not be any tight coupling between SI and the version of the kernel you're running, there IS a very tight coupling with any perl modules and where they get installed, in this case that turns out to be AppConfig.  I had hoped there might be some mention of this somewhere but there isn't.  OR am I wrong in my assertion and there is way to make SI work in this situation right out-of-the-box with no extra work?

As a related topic, I've had to patch both Label.pm and Grub.pm to make them work with cciss devices on HP/Compaq systems that use SmartArrays and thought it would also be nice to know as versions of SI change whether there have been any changes made to these modules and whether or not the patches I had submitted some time ago were ever incorporated so I wouldn't even have to worry about this.

-mark

Message: 1
Date: Fri, 07 Jan 2005 09:58:51 +0100
From: Bas van der Vlies <[EMAIL PROTECTED]>
To:  [email protected]
Subject: Re: [Systemimager] [Sisuite-users] website/release info question
Reply-To: [email protected]

Mark Seger wrote:
  
As I missing something or is there no information on the SystemImager 
website that describes the features of various releases?  Actually I did 
have a second thought and that was to go to sourceforge (though there's 
no pointer to it from SystemImager.org).  Anyhow I didn't see any 
version descriptions here either.  Is there somewhere to go and get this 
information?

I guess the main reason I'm asking is because I've been happily running 
3.1.8 for awhile now and haven't seen any need to upgrade.  However, I'm 
getting ready to start playing with some 2.6 kernel based systems and am 
wondering where I'm going to get bitten especially with respect to grub 
and can't tell whether an upgrade will increase my pain or reduce it.  8-)

In all seriousness, I've got those grub patches that have been happily 
working with 2.4 systems and don't know whether they'll work with newer 
versions of SI since I've patched Label.pm, Grub.pm and grub-install.  I 
know the easy answer is to try it and see what will happen, which I will 
certainly do (and report back to this list if anyone cares) but I am 
also looking for some early warnings that might save me some time and 
trouble over the coming days.

    
Mark,

  You do not have an 2.6 kernel for systemimager to install 2.6 kernel 
systems. We currently use systemimager 3.2 and we install 2.6 systems 
without any problems and we also uses grub for our 2.6 systems

I do not know what is changed in Label.pm for systemimager 3.2, but you 
can always port your changes.


--__--__--

Message: 2
Date: Fri, 07 Jan 2005 19:55:21 -0800
From: "David N. Lombard" <[EMAIL PROTECTED]>
To:  [email protected]
Subject: Re: [Systemimager] [Sisuite-users] website/release info question
Reply-To: [email protected]

Bas van der Vlies wrote:
  
Mark Seger wrote:

    
...
  
I guess the main reason I'm asking is because I've been happily 
running 3.1.8 for awhile now and haven't seen any need to upgrade.  
However, I'm getting ready to start playing with some 2.6 kernel based 
systems and am wondering where I'm going to get bitten especially with 
respect to grub and can't tell whether an upgrade will increase my 
pain or reduce it.  8-)

      
...
  
Mark,

 You do not have an 2.6 kernel for systemimager to install 2.6 kernel 
systems. We currently use systemimager 3.2 and we install 2.6 systems 
without any problems and we also uses grub for our 2.6 systems
    

Well, yes and no.  If you're building an x86_64 system, you'll have 
problems.  I'm specifically referring the a problem seen when SC was 
running in the chroot after the rsync completed, perl was a 64-bit 
build, and croaked under SIS's 2.4 kernel.

An i386 or ia64 system on the other hand will be just fine and ducky. :-D

  

Reply via email to