You might try the experimental UYOK (Use Your Own Kernel) code in 3.6.x.
After running "si_prepareclient" on your golden client, you'll end up
with a kernel and initrd.img in /etc/systemimager/boot. If you use that
kernel and initrd.img to boot, it will be using the same kernel,
modules, and device files that were in use on your golden client when
you ran si_prepareclient.
It will still try to auto-detect any other hardware that might be
present.
When you pull your image with si_getimage, those files will come over to
your imageserver as part of the image (naturally).
Now here's the hack part -- this will be automated in 3.8.x:
* If you manipulate your boot files on your own, just copy those
files into "the right place".
* If you want to use si_mkautoinstallcd, then copy that kernel and
initrd.img over the ones in here...
/usr/share/systemimager/boot/i386/standard/
...then you _may_ be able to run si_mkautoinstallcd like normal.
And of course, let us know of your success or failure.
Cheers!
-Brian
Thus spake ezra resnedan ([EMAIL PROTECTED]):
Anyone is autoinstalling machines like this with system imager? It seems it
does not matter how I compile the 2.6 the qlogic driver gives errors and
cant use the hard disks assigned through this card.. sometimes i even get
"kernel panic".
Any recommendations?
Thx
--
Brian Elliott Finley
Mobile: 630.631.6621
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
