Re: [sisuite-users] eth0 and eth1 reversed on clients- how toprevent that from happening?

2008-09-25 Thread Bas van der Vlies
Bernard Li wrote: Thanks for this! It would be great if you can put this in our Wiki such that it can benefit users in the future: http://wiki.systemimager.org Cheers, Hi Bernard, I shall put this in the Wiki regards --

Re: [sisuite-users] eth0 and eth1 reversed on clients- how toprevent that from happening?

2008-09-24 Thread Brodie, Kent
One simple method is instead of using the SystemImager kernel, use UYOK kernel (which would essentially be your Red Hat kernel). Barring that, there should be a way to use udev to pin down which nic to use. Hmmm. Using UYOK made NO difference. Bah. Maybe I'm having a bad day, I cannot

Re: [sisuite-users] eth0 and eth1 reversed on clients- how toprevent that from happening?

2008-09-24 Thread Bas van der Vlies
On Sep 24, 2008, at 8:39 PM, Brodie, Kent wrote: One simple method is instead of using the SystemImager kernel, use UYOK kernel (which would essentially be your Red Hat kernel). Barring that, there should be a way to use udev to pin down which nic to use. Hmmm. Using UYOK made NO

Re: [sisuite-users] eth0 and eth1 reversed on clients- how toprevent that from happening?

2008-09-24 Thread Bernard Li
Hi Bas: On Wed, Sep 24, 2008 at 1:02 PM, Bas van der Vlies [EMAIL PROTECTED] wrote: We have the same problem at our clusters (DELL 1950) with broadcom network interfaces. We now use udev rules in combination with biosdevname utility and give our network cards logical names instead of