Re: network devices and passing options to kernel

David Woodhouse (David.Woodhouse@mvhi.com)
Fri, 10 Sep 1999 13:16:36 +0100

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Andrea Arcangeli: "Re: Bug#44654: dpkg: seg faults w/2.3.17; problem traced to sysinfo()"
Previous message: Sushil Agrawal: "kernel mem for one socket connection."
Maybe in reply to: Michal Vitecek: "network devices and passing options to kernel"
Next in thread: Lauri Tischler: "Re: network devices and passing options to kernel"

lauri.tischler@efore.fi said:
> Yes, by using 'ip' from package 'iproute2', but the name of interface
> depends on three things, loading order of drivers, pcidevice BIOS
> detection and probing method of driver, you have no control over the
> last two. --

The name that the kernel initially assigns to the interface is fairly random.
However, you can easily write a program which scans all the available
interfaces just after booting, and renames them all to whatever you want.

---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Andrea Arcangeli: "Re: Bug#44654: dpkg: seg faults w/2.3.17; problem traced to sysinfo()"
Previous message: Sushil Agrawal: "kernel mem for one socket connection."
Maybe in reply to: Michal Vitecek: "network devices and passing options to kernel"
Next in thread: Lauri Tischler: "Re: network devices and passing options to kernel"