Stefhen Hovland wrote: >i think ifrename will do what you are asking, you can specify that >eth0 always be bound to x, and eth1 always bound to y, etc.. > > >http://packages.debian.org/unstable/net/ifrename > >stefhen > >On 12/29/05, Svante Signell <[EMAIL PROTECTED]> wrote: > > >>With the new way of device creation and module loading (udev, discover >>etc) my ethernet modules (3c59x,8139too) are loaded in different order >>with kernels 2.6.12 and 2.6.14. For 2.6.14 3c59x is loaded first >>corresponding to eth0 and then 8139too corresponding to eth1. With >>kernel 2.6.12 they are loaded in reverse order, giving the wrong names >>on my interfaces, and the interfaces defined in /etc/network/interfaces >>becomes wrong. How to bind modules to eth interface numbers? Any hints >>on which of the /etc/modules, /etc/modules.conf etc should be used, and >>which are obsolete? >> >>
udev should work here. you can set it up. You can set up devices to have certain names (e.g. you camera as /dev/camera) with it , and I heard this works with network interfaces too. google is your friend if you want more informtion, I hope. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
