| Autor |
Nachricht |
|
|
Titel: /etc/resolv.conf gets creamed by latest upgrade?
 Verfasst am: 05.09.2006, 06:13 Uhr
|
|
Anmeldung: 09. Aug 2004
Beiträge: 121
Wohnort: Brisbane Australia
|
|
I just did an aptitude upgrade and I lost my internet because my DNS access failed. I found that my /etc/resolv.conf had been turned into a link pointing to an empty file /etc/ppp/resolv.conf.
I put back a valid /etc/resolv.conf and all came good again. |
|
|
| |
|
|
|
 |
|
|
|
Titel:
Verfasst am: 05.09.2006, 10:11 Uhr
|
|
Team Member
Anmeldung: 04. Apr 2006
Beiträge: 153
Wohnort: Melbourne, Australia
|
|
running from the fish menu or console
"netcardconfig"
also resets the conections
other reports in #kanotix suggest the just by rebooting the connections are reactivated ( bit drastic )
that being said,, good post in tracking pinpointing the culprit
BTW please DO NOT use adept, aptitude, kpackage, synaptic to do an upgrade or dist-upgrade.. you will get caught out and bork yourself, and due to kanotix being debian sid dist-upgrade is the recommended cmd to keep your system current, as a straight upgrade is somewhat depreciated for sid due to "upgrade" often has problems to understand when dependeny libraries change their names, which happens quite often in sid.
A dist-upgrade does a more clever job as it understands the "sid" flow.. and recogisises that it is not a static repositry (unlike some debian forks that's why upgrade is usually not problem there)
The only way to dist-upgrade is as follows
Ctrl+Alt+F1 ; logon as root, type init 3 ; apt-get update ; apt-get dist-upgrade ;run fix-fonts ; run update-scripts-kanotix.sh ; run fglrx or nvidia script if xorg updated [DO NOT DIST-UPGRADE [or UPGRADE] with adept or synaptic] *always* check Current Warnings on http://kanotix.com/News.html |
_________________
Kanotix Easter RC4 on a dual boot P4 and a production box Desktop KDE::
Kanotix 2006 Easter RC4 on a P2 and Production Box , Desktop KDE::
Kanotix EasterRC4 on a MMX 199Mhz lappy
and a Production Box, Desktop ICEWM::
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 05.09.2006, 23:17 Uhr
|
|
Anmeldung: 26. Nov 2005
Beiträge: 22
Wohnort: Toronto, Canada
|
|
I got caught by resolv.conf breakage too... added the nameservers by hand and all is well.
Your observation about using apt-get vs aptitude is interesting... I just started using aptitude, now I will return to using apt-get. |
_________________
:: build-it-yourself biology http://biohackery.com ::
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 06.09.2006, 03:51 Uhr
|
|
Anmeldung: 09. Aug 2004
Beiträge: 121
Wohnort: Brisbane Australia
|
|
|
bluewater hat folgendes geschrieben::
other reports in #kanotix suggest the just by rebooting the connections are reactivated ( bit drastic )
Rebooting didn't fix anything for me. That's when I looked and found the /etc/resolv.conf problem. I'm using a static IP address but I guess if you are using DHCP then a reboot would probably fix the problem.
Zitat:
BTW please DO NOT use adept, aptitude, kpackage, synaptic to do an upgrade or dist-upgrade..
I've been using aptitude since I started with kanotix a couple of years ago and never had a problem (well, other than the sid mess with over xorg, kde, etc which affected us all). Aptitude is just a better apt-get (and it's intended replacement from a user perspective from my understanding). |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 06.09.2006, 03:58 Uhr
|
|
Anmeldung: 12. Mar 2005
Beiträge: 1005
|
|
If you do a dist-upgrade, and you lose your connection, this is all you need to run:
/etc/init.d/networking restart
it will restart networking, and everything should be fine, this also happened to me, but that's all that is required to fix it. My script will also run this automatically if it detects a broken connection when it starts, but it can't help if the connection drops while the script is runninig, after dist-upgrade. But running it again should bring that up after a brief wait.
Easy way to see if your connection dropped is after dist-upgrade finishes, and the fixes are applied etc, simply try to connect to kanotix.com with lynx, like this: lynx kanotix.com
If the connection failed, this probably happened to you, and running the networking restart is all that you need to do. |
_________________
Read more on dist-upgrades using du-fixes-h2.sh script.
New: rdiff-backup script
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 06.09.2006, 08:58 Uhr
|
|
Anmeldung: 05. Okt 2004
Beiträge: 2069
Wohnort: w3
|
|
|
markb hat folgendes geschrieben::
I've been using aptitude since I started with kanotix a couple of years ago and never had a problem (well, other than the sid mess with over xorg, kde, etc which affected us all). Aptitude is just a better apt-get (and it's intended replacement from a user perspective from my understanding).
I've been driving cars since many years without any accident and therefore never was hurt, however, I do understand that my probabilities for surviving such case are much better when using the belts. 
Seriously, aptitude is a nice tool and very well designed suited for stabilized distributions (Debian Stable, Ubuntu, Mepis, ...). But it is not designed for Debian Sid - and that's what Kanotix is all about. And don't believe the marketing speak, there is no "better apt-get".
Greetings,
Chris |
_________________
"An operating system must operate."
|
| |
|
|
|
|
|
|
