Hi,
 
I read some post about mkbootpackage, wrote by Bryan Finley. This tools seems to be a good solution with my trouble.
 
As you can see in my recent post, i have misery with PXE boot processing on client, because, i presume, SIS boot don't detect the SILICON Sata controller onboard Tyan S2885. So, process stop to running and i have a message like "undefined:Disk0". Even so, Front-end and Node hardware are same !
 
In [Oscar-Devel] forum, Jeremy Enos said :
 
<< We already know that using the distributed SI kernel is absolutely prone to failure with hardware which post-dates it. (IMO, it's the most serious problem users encounter with OSCAR today)  Once we're comfortable that mkbootpackage works on all of OSCAR's supported distros, it seems logical to me to use it in every installation automatically. Anything I'm missing? >>
 
And he ask Bryan about progress (May 2004):
<<
No progress since last check.  It's like 95% of the way there, I just need to get a chunk of time carved out to allow me to put in the final tweaks.
Bryan >>
 
Yes, it will be wonderfull to use same Front-End kernel (and module) as my front-end inside the SIS boot package or to build easily a custom boot kernel which fit the client hardware !
I'm not an advanced cluster user, but OSCAR is a fine cluster tool (because Oscar developpers make a very good job and are very dynamic, thanks to them !), but in my mind, at least in the install node stage, his weakness is SIS boot like Jeremy said about.
 
Now, perhaps this tool come with OSCAR 4.0, i don't know yet. But if not, i wish to play with mkbootpackage and built a new boot package like my front-end kernel.
It's seems to be easy, but really ?
How to get it ?
Does anyone test this tool with oscar 4.0 and Fedora core 2 ?
Howto's, Tips, Links, experience ?
 
Many thanks to your feedback
 
Best regard,
 
Jérôme Lefèvre
 
---------------------------
Laboratoire d'Océanographie Physique
IRD - Nouméa - Nouvelle-Calédonie
 
 

Reply via email to