[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Network problem



I was staring at the same problem this morning trying to recall exactly
which packages I'd installed in the last couple of days.  I figured it would
be easy to back out if I could ask dpkg to give me the date the packages had
been installed on.  I read through the man page but was unable to find any
such option.  Is this possible with dkpg?  In not, is there another program
which could give me this information?  Granted this time around its an easy
enough fix to just replace the file, but I'm still curious.

Wil


----- Original Message -----
From: "Chris Matta" <chris@coolass.net>
To: "Jason Davies" <jason@www1.kc.aoindustries.com>;
<debian-user@lists.debian.org>
Sent: Monday, February 12, 2001 8:02 PM
Subject: Re: Network problem


> This seems to be an issue with ifconfig in the latest nettools package of
> Sid(unstable), this can be fixed if you have a debian cd, like potato, i
had
> this happen today, and just untared the base package into my tmp dir, and
> replaced the ifconfig binary.  This should be fixed eventually.
>
> -c
> ----- Original Message -----
> From: "Jason Davies" <jason@www1.kc.aoindustries.com>
> To: <debian-user@lists.debian.org>
> Sent: Monday, February 12, 2001 1:08 PM
> Subject: Network problem
>
>
> > Hi,
> >
> > Has anyone seen this problem before? When I try and enable the network
(on
> bootup) I get error messages. Here is what I get when typing these
commands:
> >
> > ifconfig lo 127.0.0.1
> > SIOCSIFADDR: Bad file descriptor
> > lo: unknown interface: Bad file descriptor
> >
> > ifconfig eth0 up
> > eth0: unknown interface: Bad file descriptor
> >
> > This is really annoying because the local loopback doesn't work, and
> obviously I can't get onto the network. Pinging anything (including
> 127.0.0.1) simply says the network is unreachable.
> >
> > The modules for the network card seem to load fine. The problem must
have
> stemmed from upgrading some packages to the latest versions (in the
unstable
> distribution) because everything was working fine until I rebooted. I am
> using kernel 2.4.1 and I've tried using an older kernel but the same
things
> happen, so any suggestions on how to fix this or where to look for
problems?
> >
> > I would be very grateful for any help you could provide,
> > Jason Davies.
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> >
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




Reply to: