On Monday 18 December 2006 18:34, Joshua Cope wrote:
> Oops.. perhaps I was unclear; I think Erich and I are in violent agreement.

Oh, sorry then...

> For a given SystemImager version, I would like the default, non-UYOK 
> kernel to be the same on all Linux distributions. I'd like to create 
> loadable modules for, say, SystemImager 3.7.4-1, without worrying about 
> which distribution the imageserver is running.

This actually shows one weakness of our approach: if you want to produce a
special kernel module for a particular systemimager version, you'll need to
somehow produce the patched kernel source tree and build your module against
it. Having something like a systemimager-kernel-devel package would be helpful
in such cases. Not sure whether a patched and configured kernel tree is just
made with some simple "make" target...

Regards,
Erich

> 
>    - Josh
> 
> 
> Erich Focht wrote:
> > On Monday 18 December 2006 17:57, Joshua Cope wrote:
> >   
> >> Let me add another vote for keeping the kernel version consistent. 
> >>     
> >
> > Not sure what you mean here: do you want to install with the same kernel as 
> > on
> > the target OS? You can do it with UYOK.
> >
> > If you just join in and request systemimager to use the debian kernel, than
> > please have in mind that debian is just one rather unimportant distribution
> > (** me running and hiding ** ;-) . Adopting this strategy means that you 
> > need
> > a kernel per distribution. No, you just need every kernel which was ever 
> > used
> > in any distribution. 
> >
> >   
> >> During installation, I load custom device drivers onto my clients after 
> >> booting. It's nice to know that Systemimager version X.Y.Z always 
> >> creates boot images with kernel version V. I'd rather not have to check 
> >> both the SystemImager version and the imageserver distribution to figure 
> >> out which kernel I'm going to get.
> >>     
> >
> > If your custom module is in the right place inside the image (the correct
> > /lib/modules/... path), all will be fine. systemconfigurator will create
> > initrd images for every kernel it detects in /boot.
> >
> > Erich
> >
> >   
> >>    - Josh
> >>     
> >
> >
> >
> >   
> 
> 
> 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
sisuite-devel mailing list
sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Reply via email to