We will be seriously considering this RFE:
 
 
Perhaps for 5.0...?
 
Cheers,
 
Bernard


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Siadal, Jeremy C
Sent: Monday, October 24, 2005 9:33
To: carlos vasco; [email protected]
Subject: RE: [Oscar-devel] creating nodes with eth1 as default interface

There should be details on this fix in the sourceforge page, but here are the details:

 

Edit /var/lib/systemimager/scripts/oscarmaster. Look for [INTERFACE0] and change eth0 to eth1. I’ve noticed that the oscarmaster script will overwrite settings in the systemconfig.conf file.

 

Maybe it’s time we revisit adding a Default Interface textbox to the Add Client Nodes dialog box (right below the start IP text field).

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of carlos vasco
Sent: Monday, October 24, 2005 5:56 AM
To: [email protected]
Subject: [Oscar-devel] creating nodes with eth1 as default interface

 

I have succeeded creating the image and puting it on the nodes in my oscar 4.2b5 and FC3 amd64 cluster, but now I have the following problem,whe have the nodes with two nics, eth0 (100 Ethernet) and eth1 (1000 Gigabit). We would like to use eth1, but the image always take eth0, even if installing the image through eth1.
I have tried the following lines in /var/lib/systemimager/images/oscarimage/etc/systemconfig/systemconfig.conf
[INTERFACE0]
DEVICE eth1

And (in other trial):

[HARDWARE]
ORDER = e1000 via-rhine

But no success until now.

Any idea?

Thank you very much,

Carlos

PS I am temporally without my regular mail, so I am posting from gmail. My last mail, telling how I did the oscar installation, could have been lost. I will repost it in that case.

Reply via email to