• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Debian: I upgraded the dist and everything is messed!

S

smp

Diamond Member
Well.. I updated my sources list to woody everything and did a apt-get dist upgrade and everything seemed to work okay.
Next day I decided to reboot the machine....

big mistake.
My LAN card didn't come back up on reboot and my PS2 port is broken so I couldn't log into the machine from my lan, or from console. I had to go to a friends and ssh into it from there 😱.
At least the DHCP client was still working and it got back online.
Now I notice that I can't upload anything VIA FTP and my talk daemon doesn't work.

What do I do to make this better? I guess I could just put a "ifconfig eth1 up 192.168.0.1" in a startup script and do it like that, but I don't want to, because I know there is a machanism in there that is supposed to be doing that that isn't.
Anyone?
Thanks.
 
Did you change the kernel during this?

What kind of connection do you have to the 'net that one card comes up and other doesn't?
 


<< Did you change the kernel during this? >>



Should you change the kernel? I havent seen many docs on this (yes I looked, but sometimes I feel blind 😛).

Are there two different network cards in the machine?
 
There are two network cards in the machine, it is running IPchains and is serving as my gateway here at home.

I did not upgrade the kernel.

I have rogers@home .. cable DHCP
so one card is LAN (192.168.0.1) and the other is DHCP
the internal LAN doesn't come up anymore on boot :\
and neither does LO

I just put a symlink in rc2.d S99 for it
maybe 99 is too late?

this is the contents of the file;

ifconfig eth0 up 192.168.0.1
ifconfig LO up 127.0.0.1

These are the commands that I ran after managing to get back in the machine (from teh friends house)
and everything was working okay after that
so I figured if I just put that in startup it's cool.

I'm probably doing something stupid though
 
I'm using postfix BTW and it doen't look like it's working .. anyone know how I can start it manually?
 
You should use /etc/network/interfaces to configure your network interfaces. Also make sure /etc/modules contains the names of any modules you need loaded at bootup, like NIC drivers.
 
Yup.. that's just how it was working before. /etc/modules is unchanged and so is /etc/networking/interfaces

I don't get it.

Oh yeah!!! Postfix is working .. that was dumbness on my part, disregard that.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top