Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_SYSOPS    |    Synchronet Multinode BBS Software Suppor    |    33,243 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 30,873 of 33,243    |
|    Digital Man to Grease    |
|    Addfiles problem    |
|    22 Nov 24 12:32:43    |
      TZUTC: -0800       MSGID: 56889.sync_sys@1:103/705 2ba6fea4       REPLY: 56885.sync_sys@1:103/705 2ba64cc8       PID: Synchronet 3.20a-Linux master/51c917d04 Nov 19 202 GCC 12.2.0       TID: SBBSecho 3.23-Linux master/20c4351af Nov 21 2024 01:23 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       NOTE: FSEditor.js v1.105        Re: Addfiles problem        By: Grease to All on Thu Nov 21 2024 10:51 pm               > I'm having a bit of a problem doing addfiles in a directory. I downloaded a        > Nigh Owl disc image and extracted into data/dirs. When I run the addfiles        > program for the directory I'm in, I get this error:        >        > sbbs@Linuxbox:/sbbs/data/dirs/nopv23/001A$ /sbbs/exec/jsexec addfiles -diz        > NOPV23_001A clear              What does "clear" do in this context?               > JSexec v3.20a-Linux master/1b6d5846a - Execute Synchronet JavaScript Module        > Compiled Nov 15 2024 10:12 with GCC 11.4.0        >        > Loading configuration files from /sbbs/ctrl        > JavaScript-C 1.8.5 2011-03-31        > JavaScript: Creating runtime: 167772160 bytes        >        > Reading script from /sbbs/exec/addfiles.js        > /sbbs/exec/addfiles.js compiled in 0.00 seconds        > !Directory 'NOPV23_001A' does not exist in configuration        > 0 files added        > /sbbs/exec/addfiles.js executed in 0.01 seconds        >        > JavaScript: Destroying context        > JavaScript: Destroying runtime        >        > What is the goofy thing that I am doing wrong?        > nopv23_001A is the internal code.              So, normally you wouldn't extract a CD-ROM archive into data/dirs. That could       possibly overwrite important files in that directory (though, not likely). So       that's unusual. Instead, I like to put all my CD-ROMs into a common parent       directory, e.g.:       $ ll /cdrom/       total 60       drwxrwxrwx 19 rswindell rswindell 4096 Mar 27 2021 asp0696       drwxr-xrwx 16 sbbs sbbs 4096 Feb 16 2005 cica95       drwxr-xr-x 65 sbbs sbbs 4096 Feb 16 2005 cyberxpo       drwxr-xrwx 66 sbbs sbbs 4096 Feb 16 2005 mm94       drwxr-xr-x 61 sbbs sbbs 4096 Feb 16 2005 nopv13       ...              And then within that directory, you'll have each CD's directory hierarchy:              $ ll /cdrom/nopv13/       total 344       drwxr-xr-x 2 sbbs sbbs 4096 Mar 30 2021 001A       drwxr-xr-x 2 sbbs sbbs 4096 Jan 28 2011 002A       drwxr-xr-x 2 sbbs sbbs 4096 Feb 16 2005 003A       ...              And then each CD is best created as a *library* in SCFG->File Areas. You can       import a directory list or scan the directory to create the directories within       the library in SCFG.              And *then* you can use 'addfiles -lib= |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca