Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    DBRIDGE    |    D'Bridge Support Echo    |    10,398 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,735 of 10,398    |
|    CHRIS CRANFORD to All    |
|    Re: Cleanup Util    |
|    31 Jan 19 19:10:38    |
      Date: Wed, 27 Nov 2002 09:54:05 -0400       From: CHRIS CRANFORD       To: BRIAN CAOUETTE       Subject: Re: Cleanup Util       Newsgroups: win.server.wish.list       Message-ID: <1038409286.33.1038329799@winserver.com>       References: <1038329799.33.0@winserver.com>       X-WcMsg-Attr: Rcvd       X-Mailer: Wildcat! Interactive Net Server v7.0.454.5       Lines: 52              I think it would be useful to provide custom paths for things such as:               + Logs (activity.*, *.log)        + WCX (*.wcx)              The following suggestion would require sysops to rewrite/modify batch files;       however for those of us who would like to clean up our installation       directory much easier, maybe offering a way to set these paths if we wish to       use them for seperate directories; otherwise default them to the standard       \wc5 directory.               + Executables (*.exe, *.hlp, *.cnt, *.chm) put in \wc5\bin        + Library Files (*.dll) put in \wc5\lib              I'm not sure what Hector's plans are for the wcLISTSERVE data files when the       wcLISTSERVE is moved to using an ODBC type connection instead of using the       current data file format. Maybe the wcLISTSERVE data files and mailing list       files could be moved from the \wc5 directory to either \wc5\config or       \wc5\data along with the other data/config files for Wildcat! (same could       be applied to wcnews configuration too being moved to \wc5\config) ...              I'm just used to having an application folder that really don't contain much       of anything and all parts of a program are seperated into their component       type directories (binary files in \bin, library files in \lib, etc); however       making such a change like this would potentially mean a large architectural       change to Wildcat! which isn't all too important at the moment based on some       of the other things I'd like to see available (such as multi-web virtual       domain support and other HTTP/1.1 compatible functionality).              But I'm sure that over time Hector's going to continue to move us in the       right direction in order to keep Wildcat! on top :-)              Chris               |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca