SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Redhat since 5.2, Slackware since 9.0, Vector since 4.0
Posts: 209
Rep:
Prevent firewire as eth0
Dear all.
I'm using Slack 11 on a notebook.
The notebook has firewire (eth1394) and a nic (sky2).
My problem is, the eth1394 is always configured as eth0
and sky2 as eth1.
I simply want the sky2 to be the eth0,
while the eth1394 as something else (eth1, or fwlan0).
Distribution: Redhat since 5.2, Slackware since 9.0, Vector since 4.0
Posts: 209
Original Poster
Rep:
Quote:
Originally Posted by uselpa
What's wrong with using the MAC address? A simple "ifconfig" will tell you (it's the part after "HWaddr").
I'm a distro developer (Vector Linux to be exact).
I want a global configuration that works on every computer,
not just a particular notebook.
As you may have known, the installation scripts in slack and also VL,
always configure eth0 as the primary network.
I don't want to mess up those scripts, just for this silly thing.
By the way,
I wonder, what is the rationale to give eth0 name for the firewire.
We know that eth means ethernet, doesn't it ?
Firewire is not ethernet, for sure.
If we accept wlan* for wireless network devices,
why not using, for example, fwlan* for the firewire devices ?
On this, did you read read this doc? I don't have a firewire card but udevinfo should help you to find some persistent criteria to use. Pay attention not to mix and match criteria from different sections.
Hi,
My problem was that my wireless card (Cisco Aironet 350) was always assigned eth0 and the 3c59x was always assigned eth1. My default routing always preferred eth0, and the is not the way I wanted it...
The File:
/etc/udev/rules.d/network-devices.rules
has the devices that Slack identified, and there are some instructions on
how to uncomment and modify them to force the eth0 and eth1 swap...
I changed:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.