comparc@twwells.uucp (comp.archives) (11/01/88)
@ADD SITE NM gatekeeper.dec.com EN vixie@decwrl.dec.com (Paul A. Vixie) Tue Oct 25 14:17:17 PDT 1988 AD vixie@decwrl.dec.com (Paul A. Vixie) MA 100 Hamilton Ave, Palo Alto, CA 94301 CO ftp;ftp;gatekeeper.dec.com;128.45.9.52;/pub;0000-2359 DE Gatekeeper is DEC's anonymous FTP machine. Lots of interesting things DE show up here, including the latest version of anything having to do with DE X Windows. @END Another change in the format is shown here: the @END tells us to ignore anything further. This takes care of systems that add junk.
davidsen@steinmetz.ge.com (William E. Davidsen Jr) (11/04/88)
In article <133@twwells.uucp> comparc@twwells.uucp (comp.archives) writes: | @ADD SITE | NM gatekeeper.dec.com | EN vixie@decwrl.dec.com (Paul A. Vixie) Tue Oct 25 14:17:17 PDT 1988 | AD vixie@decwrl.dec.com (Paul A. Vixie) | MA 100 Hamilton Ave, Palo Alto, CA 94301 | CO ftp;ftp;gatekeeper.dec.com;128.45.9.52;/pub;0000-2359 | DE Gatekeeper is DEC's anonymous FTP machine. Lots of interesting things | DE show up here, including the latest version of anything having to do with | DE X Windows. | | @END A few comments about this format before the database gets out of hand. I would like to see a "keywords" field in these, in which some of the major areas covered would be detailed. In the above, for instance, a line of the form KW X-Windows KW X Windows would assist searching. I'm just starting to look at software to support this stuff, and I will be leaving space for this, even if I have to enter it myself. It would also be useful to have a line describing the name(s) of files containing the current contents listing. Perhaps an archive index entry such as: IX /pub/index or something. Again I'm leaving room for this myself, just in case I manage to convince people that it's a good idea. A lot of us didn't get the "welcome to" message, and I may be missing a lot of details by reverse engineering the purpose of this group from replies to the original message, but I suspect I'm not alone. In a new group messages sometimes get expired before the group gets made downstream in the feed. -- bill davidsen (wedu@ge-crd.arpa) {uunet | philabs}!steinmetz!crdos1!davidsen "Stupidity, like virtue, is its own reward" -me
bill@twwells.uucp (T. William Wells) (11/04/88)
In article <12512@steinmetz.ge.com> davidsen@crdos1.UUCP (bill davidsen) writes: : In article <133@twwells.uucp> comparc@twwells.uucp (comp.archives) writes: : | @ADD SITE : | NM gatekeeper.dec.com : | EN vixie@decwrl.dec.com (Paul A. Vixie) Tue Oct 25 14:17:17 PDT 1988 : | AD vixie@decwrl.dec.com (Paul A. Vixie) : | MA 100 Hamilton Ave, Palo Alto, CA 94301 : | CO ftp;ftp;gatekeeper.dec.com;128.45.9.52;/pub;0000-2359 : | DE Gatekeeper is DEC's anonymous FTP machine. Lots of interesting things : | DE show up here, including the latest version of anything having to do with : | DE X Windows. : | : | @END : : A few comments about this format before the database gets out of hand. : I would like to see a "keywords" field in these, in which some of the : major areas covered would be detailed. In the above, for instance, a : line of the form : KW X-Windows : KW X Windows : would assist searching. I'm just starting to look at software to support : this stuff, and I will be leaving space for this, even if I have to : enter it myself. You have a good idea. Consider it added to the database format. The new line is comprised of the letters KW, followed by a semicolon separated list of keywords. Spaces, other than the first, are optional and ignored. : It would also be useful to have a line describing the name(s) of files : containing the current contents listing. Perhaps an archive index entry : such as: : IX /pub/index Another good idea. However, I think it should be a little more general. Suppose that gatekeeper has an index in /pub/INDEX. The index line should look like: IX ftp;INDEX;1988 Oct 25;;index of /pub In other words, it would look like an entry of the content database, except that it is missing the first three fields and has an IX prepended. : A lot of us didn't get the "welcome to" message, and I may be missing a : lot of details by reverse engineering the purpose of this group from : replies to the original message, but I suspect I'm not alone. In a new : group messages sometimes get expired before the group gets made : downstream in the feed. Don't worry about that. I am going to be reposting it shortly, updated with the modifications that I have decided to adopt. --- Bill {uunet|novavax}!proxftl!twwells!bill