comparc@twwells.uucp (comp.archives) (11/04/88)
Well, things are beginning to move.
It seems that the site entries are going to be the first things to
get into the database. This is probably a good thing, so we should
focus on doing that. Once there is a reasonable database of sites, we
can then go whole hog on creating the other databases. This doesn't
mean that you shouldn't send in data for the other databases,if you
want to.
One random thought: I had thought that just having more than one set
of MA/CO lines would be sufficient to handle the case of more than
one archive maintainer at a site. On second thought, the entry
should have one NM and one EN line; the AD, MA, CO, and DE (and the
new KW and IX lines) should be repeated for each maintainer.
Another random thought: when I have a lot of fairly small things to
say, I think it appropriate to post them in one message. Does anyone
think that it would be more appropriate to post them in lots of small
messages? If so, send me e-mail.
I've now been asked twice for # lines as comments, so I'll give in
and add them to the database format. I view these as meta-information,
not as replacements for DE lines. Does that do what y'all want?
---
Gary L. Crum, crum@lipari.usc.edu, sent:
: Gee, I guess my last message might test the robustness of any program that
: tries to automatically handle submissions. At the time I wrote it I didn't
: think about the fact that the body of the message contains lines beginning
: with "To:" and "Subject:".
It shouldn't cause any problems. An interpreter of the data should
ignore anything before the first line beginning with an @. That way
the submitter can prefix any explanatory information he sees fit.
---
Serge, ucbvax!serge, sent:
: It might be a good idea to avoid any characters interpreted specially
: by the UNIX shells, e.g. semicolons, and use colons instead.
I am certain that I will need three levels of punctuation and there
really aren't a lot of unused punctuation characters around. This
does mean that shell scripts will be to be written with quotes in the
right place, but those are the breaks of the game.
---
John Owens, john@jetson.UPMA.MD.US, sent:
: > BTW, the previous posting is my first attempt at retransmitting a
: > received message. Anyone see any problems?
:
: One problem with
: the retransmitted message (I can't tell if it was in the original
: message or not) - the From: line had no domain. (It should have been
: "pjh@mccc.uucp".)
The problem is that I failed to put a UUCP domain in the message.
You see, the news software gives me a From: line that is a uucp path.
However, it won't let me repost the message unless the From: line
contains something that looks like name@site. It doesn't insist on
site.domain, however; so I didn't think to add it.
BTW, this necessity to fudge the From: line is really irritating, not
to mention error prone. :-) If there is a news guru out there who
knows the right way to get this line set up, would you send me e-mail?
---
Warner@hydrovax.nmt.edu sent:
: Maybe you could have a field indicating where the machine is so that
: people trying to get files can tell if they are trying to snag stuff from
: a machine with real users on it or not. Maybe a time zone field would
: be enough. I just tried to get the gatekeeper.dec.com and found that
: it was heavily loaded and couldn't think about my puny ftp process enough
: to make the xfer worth while. I then looked at the db entry real close
: and noticed that it is in California (or at least the maintainer is in CA).
: Alternatively, you could encourage people to place a comment in the DE
: field if the machine is at a different site than the maintainer (I
: assume that is what the MA field is, I missed the initial format posting.)
The MA address is the Mailing Address for getting help or information.
You are quite right that it should be possible to discover when it is
reasonable to access the machine. Since this isn't particularly
unique to ftp sites, it should be specified somewhere else than in
the CO line for ftp.
My solution would be to add a line:
TM <time_zone>;<text describing access times>
Any comments?
---
It appears that my map entry finally made it out to comp.mail.maps;
however, it was an early map entry I sent in so that everyone would
be able to find me. It is out of date, though using it won't hurt
anything. Anyway, here is my real map entry and the one for proxftl,
the site I am connected through.
#N proxftl
#S Sun 3/280; Sun Unix Release 3.4
#O Proximity Technology Inc.
#C Tom Holroyd
#E proxftl!postmaster
#T +1 305 566 3511
#P 3511 NE 22nd Ave., Ft. Lauderdale, FL 33308
#L 26 11 N / 80 00 W city
#R
#U novavax twwells
#W proxftl!tomh (Tom Holroyd); Mon Oct 3 16:58:19 EDT 1988
#
proxftl novavax(DIRECT), sunvice(DIRECT), twwells(DIRECT), uunet(EVENING)
#N twwells
#S Zenith 386; UNIX System V/386
#O
#C T. William Wells
#E twwells!postmaster
#T +1 305 491 8027
#P 781 W Oakland Park Blvd #208, Ft. Lauderdale FL, 33311
#L 26 11 N / 80 00 W city
#R
#U proxftl
#W twwells!bill (T. William Wells); Mon Oct 3 16:58:19 EDT 1988
#
twwells proxftl(DIRECT)
I'll send these out periodically, until the mapping people are able
to post them in the right place.
---
Bill
{uunet|novavax}!proxftl!twwells!bill
send comp.archives postings to proxftl!twwells!comp-archives
send comp.archives related mail to proxftl!twwells!comp-archives-request