LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-05-2009, 06:23 PM   #16
argon99
Member
 
Registered: Mar 2009
Posts: 37

Original Poster
Rep: Reputation: 16

The plot thickens!!

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.

Last edited by argon99; 04-05-2009 at 06:26 PM.
 
Old 04-05-2009, 06:53 PM   #17
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 555Reputation: 555Reputation: 555Reputation: 555Reputation: 555Reputation: 555
Quote:
Originally Posted by argon99 View Post
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.

Good luck,

Sasha
 
Old 04-05-2009, 07:21 PM   #18
alan_ri
Senior Member
 
Registered: Dec 2007
Location: Croatia
Distribution: Debian GNU/Linux
Posts: 1,733
Blog Entries: 5

Rep: Reputation: 127Reputation: 127
Quote:
Originally Posted by argon99 View Post
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.
 
Old 04-05-2009, 08:06 PM   #19
Quakeboy02
Senior Member
 
Registered: Nov 2006
Distribution: Debian Linux 11 (Bullseye)
Posts: 3,407

Rep: Reputation: 141Reputation: 141
Quote:
Originally Posted by alan_ri View Post
I'm not sure what you mean by "just touch it" but I guess you haven't read the man page.
Code:
man touch
 
Old 04-06-2009, 04:06 AM   #20
alan_ri
Senior Member
 
Registered: Dec 2007
Location: Croatia
Distribution: Debian GNU/Linux
Posts: 1,733
Blog Entries: 5

Rep: Reputation: 127Reputation: 127
Quote:
Originally Posted by Quakeboy02 View Post
Code:
man touch
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!

Last edited by alan_ri; 04-06-2009 at 04:10 AM.
 
Old 04-08-2009, 11:52 PM   #21
argon99
Member
 
Registered: Mar 2009
Posts: 37

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by GrapefruiTgirl View Post
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)

Last edited by argon99; 04-08-2009 at 11:55 PM.
 
Old 04-09-2009, 01:57 PM   #22
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 555Reputation: 555Reputation: 555Reputation: 555Reputation: 555Reputation: 555
Lightbulb Slackware pieces..

Quote:
Originally Posted by argon99 View Post
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.

Sasha
 
Old 04-11-2009, 07:51 AM   #23
argon99
Member
 
Registered: Mar 2009
Posts: 37

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by GrapefruiTgirl View Post
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.

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."

Last edited by argon99; 04-11-2009 at 07:52 AM.
 
Old 04-12-2009, 02:20 AM   #24
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Did you try changing the entries in /etc/udev/rules.d/70-persistent-net.rules?
 
Old 04-22-2009, 01:23 AM   #25
argon99
Member
 
Registered: Mar 2009
Posts: 37

Original Poster
Rep: Reputation: 16
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.

Joseph
 
Old 04-22-2009, 09:30 AM   #26
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware (personalized Window Maker), Mint (customized MATE)
Posts: 1,309

Rep: Reputation: 234Reputation: 234Reputation: 234
Quote:
Originally Posted by argon99 View Post
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.
 
Old 04-23-2009, 03:58 AM   #27
argon99
Member
 
Registered: Mar 2009
Posts: 37

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by w1k0 View Post
Living nearby Pat is good reason to start to drink beer.
Well now I live about a thousand miles away. Bt emails great.
 
Old 04-24-2009, 02:54 AM   #28
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
Quote:
Originally Posted by argon99 View Post
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.
 
Old 04-26-2009, 10:09 PM   #29
argon99
Member
 
Registered: Mar 2009
Posts: 37

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by Richard Cranium View Post
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.
 
Old 04-27-2009, 02:46 AM   #30
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105Reputation: 8105
Quote:
Originally Posted by argon99 View Post
...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.

Eric
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
dhcp bug or bug in my head belda Linux - Networking 2 01-26-2008 08:46 AM
LXer: 2008 CES: Bug Labs Introduces BUG, BUGbase. So Cool! LXer Syndicated Linux News 0 01-09-2008 01:21 AM
2038 bug-Is Debian Bug-Proof? deepclutch Debian 1 08-02-2007 10:59 AM
Firefox bug? Fedora 7 bug? or what? hawke Fedora 8 07-22-2007 07:00 PM
Free86 bug or nVidia bug?? ProtoformX Linux - Software 2 05-12-2004 02:38 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration