Hi John:
 
I think so, you'll just have to specify with --kernel and --initrd:
 
 --kernel FILE
    Optionally specify an alternate autoinstall kernel.
 
 --initrd FILE
    Optionally specify an alternate autoinstall ramdisk.
 
(from si_mkautoinstallcd)
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 5:52
To: [email protected]
Subject: Re: [Sisuite-users] UYOK and si_prepareclient


Bernard,

Can you use the kernel/ramdisk pair to create a boot cd for systemimager?

-John



"Bernard Li" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

06/13/2006 03:19 AM

Please respond to
[email protected]

To
<[email protected]>, <[email protected]>
cc
Subject
Re: [Sisuite-users] UYOK and si_prepareclient





Hi Kristina:
 
I have written up a small document explaining a bit about UYOK:

http://svn.oscar.openclustergroup.org/trac/oscar/wiki/SystemImager
 
Regarding disabling UYOK, at least with version 3.7.3, you can pass --no-uyok with si_prepareclient to disable it:

--no-uyok
   Don't create a UYOK (Use Your Own Kernel) boot package.  This option
   is advantageous if you know you don't need a UYOK kernel, and you
   want this command to complete faster.

 
I am not sure if this option is present in 3.6.3, though.
 
Hope this helps.
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] on behalf of Kristina Clair
Sent:
Mon 12/06/2006 10:47
To:
[email protected]
Subject:
[Sisuite-users] UYOK and si_prepareclient

Hello,

I just upgraded from Systemimager 3.4.1 to 3.6.3, and there seems to be
a new component to Systemimager - UseYourOwnKernel.  I am trying to
figure out the role of UYOK, but the docs on the website are for 3.4.1,
so they don't cover it.  Is UYOK documented anywhere?

I'm also getting a UYOK related error with si_prepareclient:
>>> mount /etc/systemimager/boot/initrd /tmp/.systemimager.2 -o loop -t
ext2
mount: could not find any device /dev/loop#
>>> rm -fr /tmp/.systemimager.1 /tmp/.systemimager.2

FAILED: mount /etc/systemimager/boot/initrd /tmp/.systemimager.2 -o loop
-t ext2 at /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm
line 723.


This is running on Fedora Core 3.

We don't actually let Systemimager deal with our kernels anyway, so I'm
wondering if there is a way to have Systemimager not use UYOK?

Thanks!
Kristina


_______________________________________________
Sisuite-users mailing list
[email protected]

https://lists.sourceforge.net/lists/listinfo/sisuite-users_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to