Hi Jerome:

I think it is probably easiest to grab the RPM - you can find the link to the 
RPMs here:

http://sourceforge.net/mailarchive/forum.php?thread_id=6229201&forum_id=8921

As long as the new SystemImager kernel has your module, I think it will work.  
The SystemConfigurator issue should hopefully not be a problem for you.

Cheers,

Bernard

> -----Original Message-----
> From: Lefevre Jerome [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, January 23, 2005 15:27
> To: [email protected]; Bernard Li
> Subject: RE: [Oscar-users] Suite : FC2 i386 : mkbootpackage 
> or SystemIamger 3.5 ?
> 
> Hi Bernard,
> 
> I'm trying to install from source SystemImager 3.5.2.
> Yes, your RPM would be interesting, if I don't have succes 
> with source.
> 
> What you said about SystemConfigurator is important, but my 
> target is to boot with a new boel boot package first (with 
> SIL_SATA module).
> This means may be i will have some trouble with 
> SystemConfigurator in the cluster install processing but only 
> with arch x86_64 ?? If i play with i386, i will not bad issue 
> with it. Could you confirm ?
> 
> Cheers
> 
> Jerome
> 
> 
> 
> A 15:06 23/01/2005 -0800, vous avez �crit :
> >Hi Jerome:   There is actually a SystemImager 3.5.x RPM 
> available (not 
> >from the SF website) - if you would like to try it out, let 
> me know and 
> >I will post where to find it (it is actually posted in the 
> >sisuite-devel mailing-list, so you can search in the list as 
> well).  You should be able
> >to simply do a RPM upgrade.   I am not aware of the 
> UseYourOwnKernel.pm - 
> >if this in fact works, it would solve a lot of our SIS related 
> >issues.   Concerning support for x86_64 - the development version of 
> >SystemImager does support x86_64, but that only solves part of the 
> >problem with respect to making it work for OSCAR since we 
> also depend 
> >on SystemConfigurator, which as far as I know, has not been 
> patched to work
> >with 2.6 kernel yet.   Regardless, we would be very 
> interested to hear 
> >about your experience with UseYourOwnKernel.pm.   Thanks,   Bernard
> >----------
> >From: [EMAIL PROTECTED]
> >[mailto:[EMAIL PROTECTED] On Behalf Of jerome 
> >lefevre
> >Sent: Saturday, January 22, 2005 23:04
> >To: [email protected];
> >[EMAIL PROTECTED]
> >Subject: [Oscar-users] Suite : FC2 i386 : mkbootpackage or 
> SystemIamger 3.5 ?
> >An another trick would be to install SystemImager 3.5.2 from 
> CVS. This 
> >new release is 2.6.9 kernel based, support X86_64 (dual 
> opteron tested) 
> >and come with miscellaneous tool from Bryan Finley like 
> UseYourOwnKernel.pm (I
> >think same functions like mkbootpackage).   I hope this new 
> release comes 
> >with Sata_Sil or at least the last libata support for my 
> Silicon sata 
> >drive controler (SIL3114). However, with 2.6 kernel, it's 
> will be much
> >easier to patch it, i think, if necessary.   But, my 
> questions :   1/ What 
> >do you think about these 2 solutions ? 2/ How is easy to install a 
> >newer SystemImager release, in a sytem with FC 2 + Oscar + 
> SystemImager 3.2
> >?   Advices, tips, feedback ?   Bye,   J�r�me Lef�vre
> >----- Original Message ----- From: <mailto:[EMAIL PROTECTED]>jerome 
> >lefevre
> >To: 
> ><mailto:[email protected]>[EMAIL PROTECTED]
> ourceforge
> >.net
> >  ;
> ><mailto:[EMAIL PROTECTED]>oscar-devel-a
> [EMAIL PROTECTED]
> >.sourceforge.net
> >Sent: Sunday, January 23, 2005 2:26 PM Subject: 
> [Oscar-users] FC2 i386 : 
> >mkbootpackage ??
> >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
> 
> 
> 


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Oscar-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to