On Wed, Jul 14, 2004 at 12:08:39AM +0100, Steven Satelle wrote:
> On Tue, 13 Jul 2004 20:28:56 +0300, Micha Feigin wrote:
>
> > Same behavior (I am using wdm and no xdmcp and the no listen on tcp
> > switch). It seems like /usr/X11R6/bin/X is whats causing the trouble,
> > running tcpdump when X s
On Tue, 13 Jul 2004 20:28:56 +0300, Micha Feigin wrote:
> Same behavior (I am using wdm and no xdmcp and the no listen on tcp
> switch). It seems like /usr/X11R6/bin/X is whats causing the trouble,
> running tcpdump when X startx shows the name lookup BTW:
>
you know, I think we're barking up the
On Tue, Jul 13, 2004 at 01:49:29AM +0100, Steven Satelle wrote:
> On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote:
>
> >
> > BTW I got the following reply after I tried reporting a bug on netbase
> > on this:
> >
> > [...] this is how it's supposed to work. host(1) is an
> > interface to
Incoming from Steven Satelle:
> On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote:
> >
> > [...] this is how it's supposed to work. host(1) is an
> > interface to the resolver library, which does not use /etc/hosts by design.
> >
> > The problem is that it seems that a few other things seem
On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote:
>
> BTW I got the following reply after I tried reporting a bug on netbase
> on this:
>
> [...] this is how it's supposed to work. host(1) is an
> interface to the resolver library, which does not use /etc/hosts by design.
>
> The problem
On Mon, Jul 12, 2004 at 12:06:41AM +0100, Steven Satelle wrote:
> > Ping uses the hosts file but host seems to ignore it. So if the
> > nameserver is not reachable then ping works but
> > host returns
> > 192.168.0.1 connect: Network is unreachable
> > Nameserver not reachable
> > litshi.luna.loc
> Ping uses the hosts file but host seems to ignore it. So if the
> nameserver is not reachable then ping works but
> host returns
> 192.168.0.1 connect: Network is unreachable
> Nameserver not reachable
> litshi.luna.local A record not found, try again
> my /etc/hosts has the following lines:
>
On Sun, 11 Jul 2004 22:53:09 +0200, Otto Wyss wrote:
>> On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote:
>>
>> no, its caused by the machine trying to resolve its name over eth0
>> AFAIR. If the network is up. If you've configured the network, you've
>> set a hostname, so it is trying to re
On Sun, Jul 11, 2004 at 08:33:15PM +0100, Steven Satelle wrote:
> On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote:
>
> > --- Micha Feigin <[EMAIL PROTECTED]> wrote: >
> >
> >> I'm not sure yet on what package to report this bug, but was wondering
> >> if anyone else experiences it too.
> >
On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote:
> --- Micha Feigin <[EMAIL PROTECTED]> wrote: >
>
>> I'm not sure yet on what package to report this bug, but was wondering
>> if anyone else experiences it too.
>
> Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed
> ther
--- Micha Feigin <[EMAIL PROTECTED]> wrote: >
> I'm not sure yet on what package to report this bug, but was wondering
> if anyone else experiences it too.
Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed
there, then maybe consider filing one.
-- Thomas Adam
=
"The Linux
11 matches
Mail list logo
