🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: cu.slug
Article #223

Re: Almost there; networking the XL....

#223
From: Luca Pisati
Date: Thu, 03 Jun 1999 00:00
178 lines
7166 bytes
I used to do this "renaming" all the time, but ...

I believe your problem is that you must rebuild your
incremental world that contains your namespace.

Try booting from the General world without your namespace,
then do the classic namespace loading procedure (I forgot
the commands), then save the world.

The problem you have is that the incremental has the
previous version of your namespace loaded in memory,
that's why it gets confused.


"Christopher R. Barry" wrote:
> 
> Ever since I sent my second message to this list the machine had been
> running non-stop and perfectly for over a day. I bought all the
> networking hardware I needed yesterday and decided to go for it and
> power down the machine so that I could hook up the transceiver and
> connect it to the Linux box. When I powered it back up, the keyboard
> was working perfectly, and has been. So I guess the problem magically
> disappeared (well, I did pray a lot that it would...).
> 
> Anyways, I've spent many hours reading the networking docs and trying
> to get things working and I haven't had too much luck (especially
> since my changes to things were making the docs unreachable and I had
> to use the less searchable hardcopy stuff....).
> 
> Basically, here is my setup: I've got a Linux 2.2.x box with a modem
> that connects to the internet via PPP and has one ethernet card. The
> XL is the only other machine on the network. The network is
> 192.168.0.0, the Linux box is host HAL, 192.168.0.1. The Symbolics is
> host TRILOGY, 192.168.0.2.
> 
> When I first set things up this way, I changed a line in
> FEP0:>Local.boot from
> 
>   Set Boot Options :Network Address internet|192.42.172.3
> 
> to
> 
>   Set Boot Options :Network Address internet|192.168.0.2
> 
> and then in the Namspace Editor I edited all the various objects and
> whenever I saw 192.42.172.3 I changed it to 192.168.0.2, and
> 192.42.172.0 to 192.168.0.0. When I first rebooted, I was able to ping
> the Symbolics from the Linux box. The login screen looked something
> like this though:
> 
>   This machine is Home INTERNET|192.168.0.2, a Symbolics XL1200.
> 
> instead of
> 
>   This machine is Home Trilogy, a Symbolics XL1200.
> 
> Also, I got a notification at this time (or maybe it hadn't come yet,
> but eventually I got this notification)
> 
>   [6/2 14:22:27 Namespace Home is unloaded:
>                 No longer server for this namespace.]
> 
> and sometimes the variation (from memory):
> 
>   [6/2 xx:xx:xx Namespace Home is unloaded:
>                 No longer server for this namespace.
>                 Recent servers contacted: Trilogy]
> 
> I did a lot of Find String commands to replace every last occurance of
> the old IPs with the new yet whenever I tried to use host TRILOGY like
> e.g. Edit File TRILOGY:>cbarry>whatever I would get a window about
> "Host Trilogy (192.42.172.3)" being unreachable. The old IP was
> somehow persisting despite my attempts to replace every last trace of
> it. So in order to access files I would have to do
> INTERNET|192.168.0.2:>....
> 
> Eventually, I was able to reverse all the changes I had made but it
> took a number of reboots and now the machine is back to displaying
> Host Trilogy on startup and working good with the docs online, though
> still stand-alone. I'm unable to ping it again even if I try to do
> what I remembered doing the last time I got pinging from the Linux box
> to work.
> 
> Host Trilogy was previously configured to talk to a NeXT box and a
> Mac. I've attached most of TRILOGY:>sys>site>home-objects.text to the
> bottom of this email. I think things would be much easier if none of
> the network stuff was configured so that I could start from scratch
> instead of trying to migrate the in-place settings which have mystical
> persistance properties, but I don't know how to do this. I'm pretty
> stumped.
> 
> Oh yeah, in the course of playing with all this stuff I always
> rebooted like:
> 
>   Command: Halt Machine
>   FEP Command: Clear Machine
>   FEP Command: Hello
>   FEP Command: Boot
> 
> To try to clear any persistant low-level network configuration
> stuff.
> 
> Thank you for any pointers,
> Christopher
> 
> [Most of TRILOGY:>sys>site>home-objects.text (hopefully nothing
> relevent has been elided). Don't forget, I'm typing all of this out by
> hand because the boxes aren't talking yet. Also, some lines were
> removed from some records like LPD printer stuff etc.... Ultimately,
> I'd like the setup below to work with my site, Host Tarkus becoming
> Host HAL, my Linux machine.]
> 
> NAMESPACE HOME
> PRIMARY-NAME-SERVER TRILOGY
> SEARCH-RULES HOME
> DESCRIPTOR-FILE TRILOGY:>sys>site>HOME-namespace.text
> 
> SITE HOME
> PRETTY NAME Home
> LOCAL-NAMESPACE HOME
> SITE-DIRECTORY TRILOGY:>sys>site>
> TIMEZONE PDT
> HOST-FOR BUG-REPORTS TRILOGY
> SECURE-SUBNETS INTERNET 192.42.172.0
> STANDALONE YES
> 
> NETWORK INTERNET
> SITE HOME
> TYPE INTERNET
> 
> HOST TRILOGY
> SERVICE BAND-TRANSFER TCP BAND-TRANSFER
> SERVICE CONFIGURATION TCP CONFIGURATION
> SERVICE FILE TCP TCP-FTP
> SERVICE FILE TCP NFILE
> SERVICE LISPM-FINGER UDP LISPM-FINGER
> SERVICE LOGIN TCP 3600-LOGIN
> SERVICE NAMESPACE TCP NAMESPACE
> SERVICE NAMESPACE-TIMESTAMP UDP NAMESPACE-TIMESTAMP
> SERVICE NOTIFY UDP NOTIFY
> SERVICE SEND TCP SMTP
> SERVICE SHOW-USERS TCP ASCII-NAME
> SERVICE TIME UDP TIME-SIMPLE-MSB
> SERVICE TIME TCP TIME-MSB
> SERVICE UNIX-REXEC TCP UNIX-REXEC
> PRETTY-NAME Trilogy
> ADDRESS INTERNET 192.42.172.3
> SYSTEM-TYPE LISPM
> MACHINE-TYPE XL1200
> NICKNAME TRILOGY
> SITE HOME
> 
> HOST TARKUS
> USER-PROPERTY RPC-HOSTS-FILE- NILL
> USER-PROPERTY RPC-USE-YELLOW-PAGES NILL
> SERVICE FILE TCP TCP-FTP
> SERVICE FILE UDP NFS
> SERVICE LOGIN TCP TELNET
> SERVICE RPC TCP TCP-RPC
> SERVICE RPC UDP UDP-RPC
> SERVICE RPC TCP RPC
> SERVICE SEND TCP SMTP
> SERVICE SHOW-USERS TCP ASCII-NAME
> SERVICE UNIX-REXEC TCP UNIX-REXEC
> SERVICE X-WINDOW-SYSTEM TCP X-WINDOW-SYSTEM
> PRETTY-NAME Tarkus
> ADDRESS INTERNET 192.42.172.1
> SYSTEM-TYPE UNIX42
> MACHINE-TYPE NEXT
> NICKNAME TARKUS
> SITE HOME

--
Luca Pisati
Director, Software Development	Voice:	(310) 577-0518
Nichimen Graphics		Fax:	(310) 577-0577
12555 W. Jefferson #285		EMail:	mailto:pisati@nichimen.com
Los Angeles, CA 90066		Web:	http://www.nichimen.com
Technical Details
Message-ID: <928455218.22715@news.Colorado.EDU>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <87d7zczz69.fsf@2xtreme.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10077e,c64f58e62bb28955
X-Google-Attributes: gid10077e,public
From: Luca Pisati <pisati@nichimen.com>
Subject: Re: Almost there; networking the XL....
Date: 1999/06/03
Message-ID: <928455218.22715@news.Colorado.EDU>
X-Deja-AN: 485469952
Distribution: cu
Content-Transfer-Encoding: 7bit
Sender: daemon@peabody.colorado.edu
References: <87d7zczz69.fsf@2xtreme.net>
X-Accept-Language: fr
Content-Type: text/plain; charset=us-ascii
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <375716CD.7E68946A@nichimen.com>
Organization: Nichimen Graphics
Mime-Version: 1.0
Newsgroups: cu.slug
NNTP-Posting-User: daemon