Andrei,
* Date: Wed, 24 Feb 2010 00:07:09 +0200 you wrote,
> Try adding a line like
>
> xxx.xxx.xxx.xxx joule.invalid joule
Right oh. That works.
pe...@joule:~$ cat /etc/hosts | grep 172.23.3.1
172.23.3.1 joule.invalid joule
pe...@joule:~$ host joule
joule has addr
On Mon,22.Feb.10, 09:56:36, peasth...@shaw.ca wrote:
> Andrei,
>
> Date: Sun, 21 Feb 2010 03:35:43 +0200 andreimpope...@gmail.co wrote,
> > What does your /etc/hosts file look like?
>
> Now visible.
> http://carnot.yi.org/joule.hosts
> With the link to the ISP configured by dhcp,
> the only ad
Andrei,
Date: Sun, 21 Feb 2010 03:35:43 +0200 andreimpope...@gmail.co wrote,
> What does your /etc/hosts file look like?
Now visible.
http://carnot.yi.org/joule.hosts
With the link to the ISP configured by dhcp,
the only address for joule is the good old 127.0.0.1.
Incidentally, is there a
On Sat,20.Feb.10, 17:09:53, peasth...@shaw.ca wrote:
> I'm reposting this question with answers to questions
> from Alex Samad organized better. This problem
> appeared after an update of Squeeze on
> February 7 or 8.
>
> Joule is a router with network access by a
> dhcp configured link. d
I'm reposting this question with answers to questions
from Alex Samad organized better. This problem
appeared after an update of Squeeze on
February 7 or 8.
Joule is a router with network access by a
dhcp configured link. dnsmasq and resolvconf
worked for months with no problem. Now the
Alex,
as> ... and maybe cat dnsmasq.conf
Sorry; I was halucinating in the previous reply. The dnsmasq.conf
on Joule is now visible here.
http://carnot.yi.org/joule.dnsmasq.conf
Regards,... Peter E.
--
Google "pathology workshop"
--
To UNSUBSCRIBE, email to debian-user-req
Date: Tue, 16 Feb 2010 18:04:53 +1100, Alex Samad wrote,
as> I presume you are on joule and it has dnsmasq + resolvconf installed on it.
Yes. In this instance, telneted to Joule via an openvpn tunnel.
as> can you
as> cat /etc/resolv.conf*
Last login: Mon Feb 15 17:23:57 PST 2010 on tty1
Linu
On Mon, Feb 15, 2010 at 03:17:50PM -0700, peasth...@shaw.ca wrote:
> This is another problem which appeared after an
> update of Squeeze on February 7 or 8.
>
> Joule is a router. dnsmasq and resolvconf
> have worked for months with no problem.
> Now the machine doesn't recognize its local
The third to last sentence should have been,
/etc/hostname has the name of the machine.
... Peter E.
--
Google "pathology workshop"
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb
This is another problem which appeared after an
update of Squeeze on February 7 or 8.
Joule is a router. dnsmasq and resolvconf
have worked for months with no problem.
Now the machine doesn't recognize its local
name. Other names inside and outside the
LAN are still resolved. For exampl
10 matches
Mail list logo
