Re: tlug: Japanese extensions on Sparc

[Karl-Max Wagner <karlmax@example.com>]

> [root@example.com /root]# netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 127.0.0.0       0.0.0.0         255.0.0.0       U      3584 0          0
> lo
> 
> Is destination 127.0.0.0 okay?  If so, what could be causing the slowdown
Good question. In fact, this is the "loopback device". In a way
it behaves like a real network device. In others not. It might
well be that emacs flatly considers it a fake and dislikes it.
If so, you need a better fake, in other words the dummy
interface. This is an interface that behaves like an ethernet
interface but just happens to lop back to the same machine. In
order to use it you either have to compile it into your kernel
or you compile it as a loadable module. The latter is - as usual
- the better way.

With my machine here, called "schreyer", and having the address
10.0.1.35, this works as follows:

ifconfig dummy0 schreyer up
route add schreyer

Now a "route" provides the following:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
schreyer.oberla *               255.255.255.255 UH    0      0        0 dummy0
loopback        *               255.0.0.0       U     0      0        3 lo

and a "ifconfig" says:

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:242 errors:0 dropped:0 overruns:0 frame:0
          TX packets:242 errors:0 dropped:0 overruns:0 carrier:0 coll:0

dummy0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:10.0.1.35  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 coll:0

Now emacs should be completely happy.

There is one important difference between having dummy device
support compiled in and having it as a loadable module: in the
first case you only have one dummy device, in the latter case
you have several. Thus, in the latter case you have to state
which one you want, therefore "dummy0" ( this is the first one ).

BTW, this is another trick from the "Linux Network
Administrator's Guide". You should have it already. If not, it's
more than high time to get it NOW !

                                  Karl-Max Wagner
                                  karlmax@example.com
--------------------------------------------------------------
Next Meeting: 8 August, Tokyo Station Yaesu central gate 12:30
featuring Linux on multiple platforms:
i386, Sparc, PA-Risc, Amiga, SGI, Alpha, PalmPilot, ...
Next Nomikai: 18 September, 19:30 Tengu TokyoEkiMae 03-3275-3691
--------------------------------------------------------------
Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp