If you compile using the
source from SVN (branches/3.6.x) and use si_prepareclient, it should generate a
working set of binaries. If you're on a Red Hat system, I got some RPMs
you could use.
In regards to rscync, John
may be referring to the autoinstall master script.
Cheers,
Bernard
P.S. What modules do you
need? Perhaps they are generic enough that we may consider adding in
SystemImager proper?
From: [EMAIL PROTECTED] on behalf of Charles Galpin
Sent: Wed 04/01/2006 21:12
To: [email protected]
Subject: [Sisuite-users] Re: no devfs support when using 3.5.3
Hi All
Ok, I took the plunge and upgraded to 3.5.3 in my
quest to use an
alternate kernel, build my own, or simply add
modules.
I noticed si_mkbootpackage and after a few changes got it to
build me
the boot package. But I get the same /dev issue below when booting
off
my kernel of choice. My questions are
1. John, where is it you are
adding the rsync exactly?
2. Is there another wrapper script that uses
UseYourOwnKernel.pm? The
cvs header shows it as newer than si_mkbootpackage,
but didn't know it
existed.
This seems like the best route to go, but
until then I guess I'll try
building my modules into the systemimager kernel
again :)
thanks
charles
Email Archive: sisuite-users
(read-only) Search
From: John Jolet
<[EMAIL PROTECTED]>
