From xemacs-m  Wed Jan 29 18:37:34 1997
Received: from draco.jsk.t.u-tokyo.ac.jp (draco.jsk.t.u-tokyo.ac.jp [133.11.96.217])
          by xemacs.org (8.8.4/8.8.4) with SMTP
	  id SAA07363 for <xemacs-beta@xemacs.org>; Wed, 29 Jan 1997 18:37:31 -0600 (CST)
Received: from localhost (hajime@localhost) by draco.jsk.t.u-tokyo.ac.jp (8.6.12+2.5Wb7/3.4Wbeta6-95083023) with SMTP id JAA18764 for <xemacs-beta@xemacs.org>; Thu, 30 Jan 1997 09:36:09 +0900
From: Hajime Saitou <hajime@jsk.t.u-tokyo.ac.jp>
Message-Id: <199701300036.JAA18764@draco.jsk.t.u-tokyo.ac.jp>
X-Authentication-Warning: draco.jsk.t.u-tokyo.ac.jp: Host localhost didn't use HELO protocol
To: xemacs-beta@xemacs.org
Subject: Re: Binary kits...who? when? 
In-reply-to: Your message of "29 Jan 97 16:34:48 PST."
             <m2enf4j907.fsf@altair.xemacs.org> 
Date: Thu, 30 Jan 97 09:36:08 +0900


> > Do you plan to make the binary kits for all linux platforms or just
> > those with internet access?
> 
> > I have had problems running (not compling) xemacs on a standalone
> > linux machine. However this problem can be overcome by #undef-ing
> > HAVE_SOCKETS in config.h. Instead I have HAVE_SYSVIPC set instead. I
> > havn't really looked into this to see if this is a good idea or not.
> 
> > The best way to get by the HAVE_SOCKETS problem on a linux machine is
> > probably to set ethernet as a loopback. But if you consider the fact
> > that most linux distributions do not do this for you, it may be better
> > to either have two binary distributions or change the function
> > get_internet_address in process.c (which is what gives you trouble on
> > a standalone machine).
> 
> Does this fix the ``problem'' with /etc/hosts being
> 
> 127.0.0.1	my-misconfigured-hostname.goes.here

I haven't actually tried it but I think it does. Or have I been "had?"
I don't know that much about ethernet stuff.

Any all I know is that there probably is no /etc/host on the machine I 
have at home. If there is someone running standalone slackware they
can probably tell me whether I have one and whats in it.

But rather than just talk I'll try it over the weekend. Or as soon as I
get hold of a standalone machine somewhere.

But shouldn't the line be

127.0.0.1	localhost

? Or does it get written over?

With localhost adding

/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0

to /etc/rc.d/rc.local should do the trick but then you need the
binaries too.

Hajime Saito

