Dotan Cohen wrote:
On 1 April 2010 20:40, Wayne wrote:
When the servers are back up install the 'debian-reference' package.
Read it. Â It has a section on networking - read it. Â You would not have
started this if you had done this.
Most if not all problems can be solved by reading through th
On 1 April 2010 20:40, Wayne wrote:
> When the servers are back up install the 'debian-reference' package.
>
> Read it. It has a section on networking - read it. You would not have
> started this if you had done this.
>
> Most if not all problems can be solved by reading through that manual.
>
peasth...@shaw.ca wrote:
Wayne,
From: Wayne
Date: Thu, 01 Apr 2010 13:40:50 -0400
install the 'debian-reference' package.
Read it.
Can't the instructions be read on a Web page?
Don't know, I never looked on the web for it. Just install the package
along with the dwww package and you c
Wayne,
From: Wayne
Date: Thu, 01 Apr 2010 13:40:50 -0400
> install the 'debian-reference' package.
>
> Read it.
Can't the instructions be read on a Web page?
Thanks, ... Peter E.
--
Google "pathology workshop".
In ETHNO click here -> Desktops.OpenDoc "http://carnot.yi.org";.
--
Dotan Cohen wrote:
Adding lo to /etc/network/interfaces fixed the problem.
I'd wonder why there wasn't a lo in the first place...
I broke it trying to force the computer to take a specific IP address.
One of those issues that I decided to learn by doing, rather than
bugging the list about. On
On 2010-04-01 12:24, Dotan Cohen wrote:
Adding lo to /etc/network/interfaces fixed the problem.
I'd wonder why there wasn't a lo in the first place...
I broke it trying to force the computer to take a specific IP address.
One of those issues that I decided to learn by doing, rather than
buggi
Dotan Cohen wrote:
Adding lo to /etc/network/interfaces fixed the problem. You are a genius!
Well now we know at what level we have to start at when Dotan has a problem.
I never claimed not to be slow! Actually, I don't know if that was
meant to offend, but I am not offended.
It was not me
>> Adding lo to /etc/network/interfaces fixed the problem.
>
> I'd wonder why there wasn't a lo in the first place...
>
I broke it trying to force the computer to take a specific IP address.
One of those issues that I decided to learn by doing, rather than
bugging the list about. Only when I got s
>> Adding lo to /etc/network/interfaces fixed the problem. You are a genius!
>
> Well now we know at what level we have to start at when Dotan has a problem.
>
I never claimed not to be slow! Actually, I don't know if that was
meant to offend, but I am not offended. I learn a lot from this list.
G
On 2010-04-01 11:20, Dotan Cohen wrote:
Is there actually a "lo"? Presumably that non-Debian machine is running
Network Mangler.
Adding lo to /etc/network/interfaces fixed the problem.
I'd wonder why there wasn't a lo in the first place...
Dotan Cohen wrote:
Is there actually a "lo"? Â Presumably that non-Debian machine is running
Network Mangler.
Adding lo to /etc/network/interfaces fixed the problem. You are a genius!
Well now we know at what level we have to start at when Dotan has a problem.
Google didn't help with that
> Is there actually a "lo"? Presumably that non-Debian machine is running
> Network Mangler.
>
Adding lo to /etc/network/interfaces fixed the problem. You are a genius!
--
Dotan Cohen
http://bido.com
http://what-is-what.com
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
wit
> Is there actually a "lo"? Presumably that non-Debian machine is running
> Network Mangler.
>
Thank you Ron! That was it!
--
Dotan Cohen
http://bido.com
http://what-is-what.com
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
On 2010-04-01 11:03, Dotan Cohen wrote:
One problematic machine running a Debian-based distro (ubuntu 9.10)
will answer to pings from other computers, but will not answer to
pings on 127.0.0.1 from itself. Likewise, it will not answer to pings
to localhost nor to its own IP address (pings to it's
One problematic machine running a Debian-based distro (ubuntu 9.10)
will answer to pings from other computers, but will not answer to
pings on 127.0.0.1 from itself. Likewise, it will not answer to pings
to localhost nor to its own IP address (pings to it's own IP address
are answered if I try from
15 matches
Mail list logo