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.
Well I have been pulling my hair out trying to get ifrename to work. I put three wireless interfaces in my box so I can repicate someone that has multiple interfaces. From the command line I can rename any interface that is not already up to any name I want. But when I try the same thing from a script, before the interfaces are brought, up I get an err, No such device. Well I get the device name right out of /proc/net/wireless. This is the same place iwconfig gets it from.
I am beginning to think that the problem is with udev. Ifrename came along before udev did. I suspect that the only way I am going to get the interfaces to actually rename is to change udev rules on the fly. I wonder if that can be done? Maybe I will have to change the rules then reboot the machine to get them to take effect, what a pain the the back side.
And by the way if anybody has any ideas I hve an empty /etc/iftab file. Ifrename won't do anything if there isn't an iftab file. Apperantly iftab isn't used now that we have udev. So I just touch it and ifrename is happy. If anybody has any ides as to why I can't get this to work please tell me. Maybe it's a bigger problem then I assumed in the first place and that's why Pat hasn't fixed it. But hey I got nothing better to do with my time so tally ho and all that sort of rot.
The plot thickens!! ... I suspect that the only way I am going to get the interfaces to actually rename is to change udev rules on the fly. I wonder if that can be done? Maybe I will have to change the rules then reboot the machine to get them to take effect, what a pain the the back side.
If you look at Slackware's rc.udev script, you can see that it is possible to have udev re-read the rules, and if you like, look at the adjacent code there that repopulates /dev accordingly.
`udevcontrol rules_reload`
I know this is just a small bit of info, but hope it is something you were looking for.
I took an interest in this thread because I was having a very weird time recently trying to configure two wireless devices on a single desktop machine a week or so ago, and was having similar results to yours, only in my case, wlan0 refused to work, and it kept getting renamed to eth0. Go figure.
I ended up configuring the machine for only ONE of the two wireless devices, and it is still called eth0.
I look forward to seeing your revised rc.inet1 script at some point. While my coding experience is undoubtedly far less than yours, I'll help if I can with the BASH part. C is beyond me.
And by the way if anybody has any ideas I hve an empty /etc/iftab file. Ifrename won't do anything if there isn't an iftab file. Apperantly iftab isn't used now that we have udev. So I just touch it and ifrename is happy.
I'm not sure what you mean by "just touch it" but I guess you haven't read the man page.
Yeah,I guess I should sleep a little every now and then.That said,the truth is that my friend Bash warned me; man sleep!
But,as usual,I didn't listen.It's amazing how sometimes things can look different in the morning...
Thanks anyway!
If you look at Slackware's rc.udev script, you can see that it is possible to have udev re-read the rules, and if you like, look at the adjacent code there that repopulates /dev accordingly.
`udevcontrol rules_reload`
I know this is just a small bit of info, but hope it is something you were looking for.
I took an interest in this thread because I was having a very weird time recently trying to configure two wireless devices on a single desktop machine a week or so ago, and was having similar results to yours, only in my case, wlan0 refused to work, and it kept getting renamed to eth0. Go figure.
I ended up configuring the machine for only ONE of the two wireless devices, and it is still called eth0.
I look forward to seeing your revised rc.inet1 script at some point. While my coding experience is undoubtedly far less than yours, I'll help if I can with the BASH part. C is beyond me.
Good luck,
Sasha
Thank you Sasha!! What is your slackware version? I am using 12.2 and it's different on mine. I have, under reload, udevadm control reload_rules. And that is another head ache I have been dealing with. The udev tools have changed. It appears that they are all now rolled into udevadm. All of the documentation I have been reading on the net uses different names for the tool set. God what a pain. Udev is new and fairly fluid so it's a moving target. But this brings up another of my pet peeves. I think every web page should have a date on it from when it was last edited. This would make life so much easier. And it could be done in Apache. It doesn't have to be done in the page itself. But is it happening??? Of course not. Well it's late and I'm starting to get cranky. I got kids you know and they wear me out.
But thanks again Sasha. (PS I think Sasha is a beautiful name, mine couldn't be simpler. I'm Joe)
Thank you Sasha!! What is your slackware version? I am using 12.2 and it's different on mine. I have, under reload, udevadm control reload_rules. And that is another head ache I have been dealing with. The udev tools have changed. It appears that they are all now rolled into udevadm. All of the documentation I have been reading on the net uses different names for the tool set. God what a pain. Udev is new and fairly fluid so it's a moving target. But this brings up another of my pet peeves. I think every web page should have a date on it from when it was last edited. This would make life so much easier. And it could be done in Apache. It doesn't have to be done in the page itself. But is it happening??? Of course not. Well it's late and I'm starting to get cranky. I got kids you know and they wear me out.
But thanks again Sasha. (PS I think Sasha is a beautiful name, mine couldn't be simpler. I'm Joe)
Hi Joe,
thank you for the compliment and FWIW, my favourite uncle's name is 'Joe'.
Now..
My Slackware installed version is 11.0, however MANY of the packages that come with 11.0 I have upgraded since installation, which was around when Slack-11 was released. Some are upgraded probably beyond Slack 12.x too. Including udev, BASH, iptables, wireless tools, and many many others.
My udev version is 103, and I haven't looked at the loads of different versions of udev lately, but I know there are a lot of them; udev has come a long way and still going strong. I would upgrade it more, but I remember a lot of frigging around even going from default of 097 to 103, so I have been putting it off. I *did* try a version newer than 103 quite some time ago, but it just wouldn't work right so I went back to 103 which works very nicely for me; but, every system is different! Undoubtedly your udev version if worlds apart from mine.
Dial-up internet and/or lack of funds has prevented me from looking into a newer Slackware, though on the other hand, I have my 11.0 so personalized/customized that I am still very happy with it, and it serves me well. I plan to investigate Slamd-64 sometime too.
Best of luck with your ongoing project; I'll be following along.
thank you for the compliment and FWIW, my favourite uncle's name is 'Joe'.
Now..
My Slackware installed version is 11.0, however MANY of the packages that come with 11.0 I have upgraded since installation, which was around when Slack-11 was released. Some are upgraded probably beyond Slack 12.x too. Including udev, BASH, iptables, wireless tools, and many many others.
My udev version is 103, and I haven't looked at the loads of different versions of udev lately, but I know there are a lot of them; udev has come a long way and still going strong. I would upgrade it more, but I remember a lot of frigging around even going from default of 097 to 103, so I have been putting it off. I *did* try a version newer than 103 quite some time ago, but it just wouldn't work right so I went back to 103 which works very nicely for me; but, every system is different! Undoubtedly your udev version if worlds apart from mine.
Dial-up internet and/or lack of funds has prevented me from looking into a newer Slackware, though on the other hand, I have my 11.0 so personalized/customized that I am still very happy with it, and it serves me well. I plan to investigate Slamd-64 sometime too.
Best of luck with your ongoing project; I'll be following along.
Sasha
Oh my GOD you have dial-up. I feel for you. In the past my wife worked for AOL ( she is a teacher and was doing home work help for them). She had dial-up to get on AOL. One day she came into my office when I wasn't home and used my systen that was on a cable modem. As soon as I walked in the door she said "YOU WILL HOOK ME UP TO YOUR NETWORK." Being a wise husband that knows when his head is on the block I said "OK."
Man has this turned out to be a pain. Udev's documentation is out of date. The way slackware is calling udev is out of date, that's with 12.2 by the way. You can check this out yourself by going to the rc.udev script and locating where is says reload ( or something like that I'm on suse now). Then just run that command in a shell. It comes back with an error from udev.
Just when I started to get it figured out I had a hardware problem. I did memtest on my system and came up with a few bad memory locations. Pulled one stick to start the process of locating the bad stick and now the system will not boot or beep or anything. I did find out that on this cpu (AMD Athlon 64 X2 socket 939) the memory controller is internal to the cpu. This means I have no way of telling if the problem is in the cpu or in the mother board. So it's new system time for me.
But I am getting real tried of having stuff fail every two years. I still have the first 386 I bought and it works fine and I have a pile of modern P4s and other mother Boards that are worthless. I think the manufacturing quality of computers has gone way down hill.
But I'm very close to getting this problem solved. Yes I did change the rules in rules.d but all the interfaces are not listed by default. But this is the place where I will be adding my own rule sets. And Sasha the reload in rc.udev doesn't work. And if you run the same command from a shell udev give an error for how the command is called. I guess Pat missed that one. But udev's documentation is a pile and emails for clarification go unanswered.
When I'm back up and running I will get back on this problem and post the solution. I know I'm close. I have gotten a wire interface rule to change. Now I just need to get the wireless interface to change. Roll it all together so it looks nice and submit it to Pat.
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309
Rep:
Quote:
Originally Posted by argon99
I used to live just a couple of houses down from Pat. We weren't really friends, he did invite me out for a beer but I don't drink and we just never found the time to get together.
Living nearby Pat is good reason to start to drink beer.
Man has this turned out to be a pain. Udev's documentation is out of date. The way slackware is calling udev is out of date, that's with 12.2 by the way. You can check this out yourself by going to the rc.udev script and locating where is says reload ( or something like that I'm on suse now). Then just run that command in a shell. It comes back with an error from udev.
Maybe Pat's been reading your e-mails. There's a new 12.2 package (udev-141-i486-2_slack12.2) that came out on April 21, 2009 which has the correct command.
Maybe Pat's been reading your e-mails. There's a new 12.2 package (udev-141-i486-2_slack12.2) that came out on April 21, 2009 which has the correct command.
Well I'm sure I had nothing to do with it. But I'd be way more pleased if changing the IFname in rc.inet1.config actually changed the name. It says it does in rc.inet1.config but it doesn't work. I suspect that it used to but with the addition of udev it broke and nobody, well except me, has put any effort into getting it to work properly.
If someone else fixes it first that's fine but I should be off my laptop and back up in a couple of days. I will then complete my changes. But I fear it will take some additional rc scripts. If I try to do it in rc.inet1 it will take a reboot, even with the correct commands udev doesn't do what it says it will do ( actually reload the rule sets ). So the changes need to be run before udev is run.
...if changing the IFname in rc.inet1.config actually changed the name. It says it does in rc.inet1.config but it doesn't work. I suspect that it used to but with the addition of udev it broke and nobody, well except me, has put any effort into getting it to work properly.
The IFNAME variable was never meant to change the name of an interface. I have no idea where you get this misconception.
The IFNAME[] value must match the name of an actual existing interface name. If the names match, the interface will be configured. If no interface with that name is found, the rc.inet1 script will write "/etc/rc.d/rc.inet1: <name> interface does not exist (yet)" to the message log if you enabled logging.
If you really want to change the interface's name, edit /etc/udev/rules.d/70-persistent-net.rules instead.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.