perm filename INFO.TXT[S,NET] blob sn#696042
filedate 1983-01-12 generic text, type C, neo UTF8
COMMENT ⊗ VALID 00002 PAGES
C REC PAGE DESCRIPTION
C00002 00002 ∂12-Jan-83 0223 ME new programmer name for network files
∂12-Jan-83 0223 ME new programmer name for network files
To: TVR at SU-AI, MRC at SU-AI, BH at SU-AI, REG at SU-AI,
JJW at SU-AI, "#INFO.TXT[S,NET]" at SU-AI
I have created a new SAIL programmer name called NET for use in storing
all the files related to networks. Although I don't expect to instantly
move all such files to *,NET areas, I do plan to move them all there
eventually. Initially, I have created three areas:
S,NET for source files of network software (area named like S,SYS);
most of NET,MRC should end up here plus other scattered files.
DMP,NET for .DMP files of network servers;
this will take over for NET,SYS.
HST,NET for files having to do with host information.
Other areas can be created as needed. I would like to know what problems
you think exist wrt moving network files to new areas; in particular, what
programs, batch jobs, etc., "know" where to find certain of these files.
There are a couple of obvious such PPN dependencies, like the servers all
coming from NET,SYS, but I need to know all such info before moving files
that might become "lost" to some programs as a result.
Files that have no such "compiled-in" PPNs can be moved immediately.
Probably most of Tovar's new source files are prime candidates, and
most of [NET,MRC] I assume, plus a few files from [CSP,SYS].
Let me particuarly say that I'm also renaming TELNET[CSP,SYS] to
FTP[S,NET], since it has nothing to do with Telnet, as everybody knows.
Of course, that file is also the source for DIAL and PTYJOB and who knows
how many other hacks, but it's current main use in the network world is as
the FTP source.
There will be some duplications, like TELNET[S,TVR]&[NET,MRC]. The new
versions of such should be appropriately named on [S,NET], with the
older versions bearing the extension .OLD, naturally.
One of the things I'd like to get cleaned up is the transition to TVR's
new version of NETWRK, already used by certain programs. If the new
version is compatible with the old, then maybe it can just be put up (I
guess the official version lives on [SUB,SYS] although only the old
version is there now). If it isn't entirely compatible, then remaining
unconverted programs should be converted to use the new version.
Alternatively, the new version could be called NE2WRK or something equally
silly (better, name the old one NE0WRK and just change the reference to it
in programs that use it, eventually fixing such programs to use the new
stuff). I don't like to have system programs that use files from
individual users areas, such as where the new NETWRK is now.
I hope that this shuffling around of the files to new areas won't be
either messy or prolonged, and I think it will simplify life a little.
I'll try to keep some information in INFO.TXT[S,NET] about what's where.
The use of *,NET also will make it easier to create new mnemonic disk area
names when needed. Pardon me for being fairly verbose in this message,
but I do want to get these things done. I'd appreciate your cooperation.
∂12-Jan-83 0229 ME The following renamings have been done.
File Ext PPN Pro Size Date Time Writer Using Reference % Dumped
******* Rename Page: 7 files (112 blocks) ******* N
FTP SNET 005 23.0 10-Jan-83 2354 1 ME E 12-Jan-83 50
TELNET CSPSYS 005 23.0 10-Jan-83 2354 1 ME E 12-Jan-83 50
FTP OLD SNET 005 22.9 4-Jan-83 0331 1 ME E 8-Jan-83 13 9-Jan-83P 1
TELNET OLD CSPSYS 005 22.9 4-Jan-83 0331 1 ME E 8-Jan-83 13 9-Jan-83P 1
SMTPSR FAI SNET 000 12.4 2-Jan-83 0455 1 ME E 2-Jan-83 0 9-Jan-83P 1
SMTPSR FAI CSPSYS 000 12.4 2-Jan-83 0455 1 ME E 2-Jan-83 0 9-Jan-83P 1
FTP BAD SNET 005 23.4 13-Dec-82 1354 1JJW E 8-Jan-83 7 9-Jan-83P 1
TELNET BAD CSPSYS 005 23.4 13-Dec-82 1354 1JJW E 8-Jan-83 7 9-Jan-83P 1
NETGRF FAI SNET 000 13.8 23-Sep-82 1419 1TVR E 23-Sep-82 0 18-Oct-82P 2
NETGRF FAI CSPSYS 000 13.8 23-Sep-82 1419 1TVR E 23-Sep-82 0 18-Oct-82P 2
FTPSER FAI SNET 000 11.7 24-Jan-82 1259 1 ME E 2-Jan-83 2 7-Feb-82P 2
FTPSER FAI CSPSYS 000 11.7 24-Jan-82 1259 1 ME E 2-Jan-83 2 7-Feb-82P 2
EFTP FAI SNET 000 2.5 26-Jan-81 1228 CSDREG COPY 4-Jan-83 1 9-Feb-81P 2
EFTP FAI CSPSYS 000 2.5 26-Jan-81 1228 CSDREG COPY 4-Jan-83 1 9-Feb-81P 2
∂12-Jan-83 2256 Mark Crispin <Admin.MRC@SU-SCORE.ARPA> Re: new programmer name for network files
Date: Wed 12 Jan 83 13:11:54-PST
From: Mark Crispin <Admin.MRC@SU-SCORE.ARPA>
Subject: Re: new programmer name for network files
cc: TVR@SU-AI.ARPA, MRC@SU-AI.ARPA, BH@SU-AI.ARPA, REG@SU-AI.ARPA, JJW@SU-AI.ARPA,
Postal-Address: 725 Mariposa Ave. #103; Mountain View, CA 94041
Phone: (415) 497-1407 (Stanford); (415) 968-1052 (residence)
In-Reply-To: Your message of Wed 12 Jan 83 02:23:00-PST
I think that all of [NET,MRC] with the exception of HOSTS1.BIN and
HOSTS2.BIN can/should be moved immediately.
Look at NETGEN on that area. It alleges to recompile everything
that uses NETWRK, so it says here that if you fix NETWRK to reference
the new directory instead of [NET,MRC] it should work. Perhaps it
doesn't recompile MAIL though.
Copy HOSTS1.BIN and HOSTS2.BIN. If the read date for [NET,MRC]'s
copy doesn't get updated, then we can eventually flush that entire
Thank you. This move is long overdue.
-- Mark --