YAST, you are a bad boy, stop it!
Well, Yast1 decided to drive me nuts. It keeps screwing up my pcmcia network settings! The story: My laptop has a built-in ethernet adapter which I use at work. At work I get the IP address via DHCP. At home, I use a wireless PCMCIA adapter. In this case, I use a fixed IP. What happens is that if I run YAST while at work (i.e. installing a new package), it goes and changes the SEARCH, DNS_1 and DNS_2 entries in /etc/pcmcia/network.opts file. It leaves all other settings intact (IP, GW, etc.) This means that when I get home, I have to edit the file and fix it. Why would YAST touch the pcmcia information when it knows that eth0 is NOT pcmcia (as I entered in the network card set up screen)? Avi -- Avi Schwartz Get a Life, avi@CFFtechnologies.com Get Linux!
On Wednesday 07 March 2001 21:37, Avi Schwartz wrote:
Well, Yast1 decided to drive me nuts. It keeps screwing up my pcmcia network settings!
The story:
My laptop has a built-in ethernet adapter which I use at work. At work I get the IP address via DHCP.
At home, I use a wireless PCMCIA adapter. In this case, I use a fixed IP.
What happens is that if I run YAST while at work (i.e. installing a new package), it goes and changes the SEARCH, DNS_1 and DNS_2 entries in /etc/pcmcia/network.opts file. It leaves all other settings intact (IP, GW, etc.) This means that when I get home, I have to edit the file and fix it.
Why would YAST touch the pcmcia information when it knows that eth0 is NOT pcmcia (as I entered in the network card set up screen)?
Avi
Avi, Without thinking too hard about the specifics you your problem - 'cause I don't know the details of pcmcia & linux - I believe it would be nice to have a "DON'T TOUCH THIS FILE, yAst" switch you could throw in any file that YaST, or other scripts, may potentially edit. I had a similarly joyous adventure when I found the ADSL connection script was changing my resolv.conf to what my ISP thought was a good DNS setting. I run my own DNS thank you. It worked when I hand hacked the resolv.conf, so of course I thought I fixed it. Then it stopped working upon the next connection - days later when my changes were not fresh in my mind. Fun, fun, fun! I believe in many cases they run an MD5 on the file and compare the previous YaST hash to a hash of the current file, if they differ YaST leaves the file alone. Not *always* what we want. You may want to shoot off a mail to the author of the missbehaving script. Steve
Avi Schwartz wrote:
Well, Yast1 decided to drive me nuts. It keeps screwing up my pcmcia network settings!
The story:
My laptop has a built-in ethernet adapter which I use at work. At work I get the IP address via DHCP.
At home, I use a wireless PCMCIA adapter. In this case, I use a fixed IP.
What happens is that if I run YAST while at work (i.e. installing a new package), it goes and changes the SEARCH, DNS_1 and DNS_2 entries in /etc/pcmcia/network.opts file. It leaves all other settings intact (IP, GW, etc.) This means that when I get home, I have to edit the file and fix it.
Why would YAST touch the pcmcia information when it knows that eth0 is NOT pcmcia (as I entered in the network card set up screen)?
Yast does not touch ANY file. See /sbin/conf.d/SuSEconfig.pcmcia for what's happening.
Technicality.... Yast calls SuSEconfig which in turn does the damage....
Avi
--On Wednesday, March 07, 2001 19:39:59 -0800 Michael Hasenstein
Avi Schwartz wrote:
Well, Yast1 decided to drive me nuts. It keeps screwing up my pcmcia network settings!
The story:
My laptop has a built-in ethernet adapter which I use at work. At work I get the IP address via DHCP.
At home, I use a wireless PCMCIA adapter. In this case, I use a fixed IP.
What happens is that if I run YAST while at work (i.e. installing a new package), it goes and changes the SEARCH, DNS_1 and DNS_2 entries in /etc/pcmcia/network.opts file. It leaves all other settings intact (IP, GW, etc.) This means that when I get home, I have to edit the file and fix it.
Why would YAST touch the pcmcia information when it knows that eth0 is NOT pcmcia (as I entered in the network card set up screen)?
Yast does not touch ANY file.
See /sbin/conf.d/SuSEconfig.pcmcia for what's happening.
-- Avi Schwartz Get a Life, avi@CFFtechnologies.com Get Linux!
You can do what I do..and that is just remove the file from this directory of the program you don't want SuSEconfig to touch. It's screwed up my Postfix config a couple times and I REALLY hate debugging what it f**ked up...so I just move the file to a backup directory and SuSEconfig never touchs what I don't want it to. I haven't had time to figure out why it does it even though it's not suppose to..and nor do I care. I don't need certain files even touched..they work and that is all I give a s**t about. :) /sbin/conf.d/ The above directory is where you can find the files that SuSEconfig will look at. Please do not remove or edit these files unless you know WTF your doing. It can cause problems...there that's my disclaimer ;) * Avi Schwartz (avi@CFFtechnologies.com) [010307 19:43]: =>Technicality.... Yast calls SuSEconfig which in turn does the damage.... => -- Ben Rosenberg mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
participants (4)
-
Avi Schwartz -
Ben Rosenberg -
Michael Hasenstein -
Steven T. Hatton