Title: Re: [Oscar-devel] RFC: UYOK option in "Setup Networking"?
Hi Erich:
 
Actually symlink works fine with /tftpboot - I tested this both with Fedora Core 5 and SUSE Linux 10.0.
 
In regards to SystemImager 3.7.3 and UYOK, I don't think this is the best time to implement what you wanted regarding multiple distro/arch support since "si_prepareclient" just creates one set of boot packages and puts it in /etc/systemimager/boot.
 
si_mkbootpackage is supposed to create bootpackages for multiple flavours and you can have multiple sets co-exist with each other.
 
Unfortunately si_mkbootpackage has not been implemented yet for 3.7.3.
 
We can of course generate the bootpackages and copy them somewhere else for storage to work around this issue...
 
I am not sure whether it's possible to generate UYOK kernel/ramdisk in a chroot, but I can test that...  So far I have just been running si_prepareclient on the headnode.  This only works well if your headnode have similar hardware as your compute nodes - but if the only difference between head and compute are things like network interfaces you can use modprobe to load the module prior to running si_prepareclient - this works.
 
I'm still not clear how exactly we want to implement this for multiple distroes/architectures - I assume each client node will have their own pxelinux.cfg configuration file and they will point to different kernel/initrd.img depending on what distro/arch they are on (if they use UYOK).  So if you press "Setup Network Boot" would it then go through all your images and set up the symlinks accordingly?
 
If you have some idea, it would be great to get this ironed out.
 
Thanks,
 
Bernard


From: Erich Focht [mailto:[EMAIL PROTECTED]
Sent: Mon 26/06/2006 04:10
To: Bernard Li
Cc: [email protected]
Subject: Re: [Oscar-devel] RFC: UYOK option in "Setup Networking"?

Hi Bernard,

> If the "Enable UYOK" radio button is pressed, then when you press "Setup
> Network Boot", si_prepareclient will run in the background to generate the
> kernel/ramdisk, and the UYOK files will be stored in /etc/systemimager/boot
> and they will be symlinked to /tftpboot (instead of
> /usr/share/systemimager/boot/$ARCH/standard).

I'm afraid this will not work. Tftpd will (and should) use /tftpboot as a
chroot directory, so linking in things from outside this tree will render them
invisible. You must have the kernel and initrd inside /tftpboot. Then you can
create symlinks.

Can you please extend the name of the generated kernel and initrd to something
like: install-{kernel|initrd}-${COMPAT_DISTRO}-${ARCH} ? And symlink to
kernel|initrd.gz if you created this on the master?

Is there a chance to create this kernel for another architecture? Chroot into
an image or so?

Regards,
Erich

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to