cck@CUNIXC.COLUMBIA.EDU.UUCP (06/03/87)
Patch file #5 (patch files are numbered sequentially independently of the distributions), the first for CAP distribution 4.00 is now available via: o anonymous FTP from CU20B.COLUMBIA.EDU in the directory US:[US.CCK.CAP.D4] as PAT5.SHAR. o anonymous FTP from Sumex-Aim.Stanford.Edu in the directory PS:<INFO-MAC> as AT-CAP4.PATCH o via BITNET: "tell macserve at pucc get at-cap4.patch" (537 records) This file is approximately 71kilobytes. Included are four main files containing context differences: samples.diffs - patches to lwsrv and lsrv to only "quote" characters that are not "ascii" (e.g. have the high order bit on). The test was "isprint && isascii" before. The orignal problem of Transcript not accepting certain characters was pointed out to us by Santa Wiryaman at RPI (though Bill claims to have known about the problem all along - code in lwsrv seems to indicate he did :-). He suggests that there should be no printing dependencies in lwsrv/lsrv - we agree since lwsrv and lsrv only act as intermediate agents not as "spoolers", but keep the changes since they cause no harm and help in some cases. There are also two additional patches to lwsrv: make it use "-J" and make it update the printer status message after sending the font list. Patch papif to properly handle IDLESTUFF (noted by Evan Schaffer of ucsc). lib.diffs - mostly minor cleanups. Includes a fix to ddp to prevent sending on skts there were closed. aufs.diffs - in afpos.c, oslogin had a bug which could cause aufs to improperly initialize the groups. in aufs.c, we shutdown nbp in the child to reduce the number of open files. The other changes make handling of overlapping volumes work better (still not recommended though) and enforces distinctions between directories in different volumes better (had problems with this in switcher). There were various other problems, including one noted by Scott Comer of Rice. Basically, these changes end up making aufs work a lot better :-) netat.diffs - mods for better volume handling. In addition, we are interested in finding out how who is using CAP and what parts. We would be pleased if you sent mail to one of the following addresses if you are using CAP: bitnet: cck@cuvma uucp: {topaz,seismo}!columbia!cck arpa,nsfnet: cck@columbia.edu with the following information: | |Site: |Contact: |USING: (retain applicable items) | Current distribution in use: (1.0, 2.0, 2.1, 3.0, 4.0) | Libraries: (yes, no) | aufs: (yes, no) | afp client code: (yes, no) | sample programs: (papif, etc.) |Other info: information about what you are using cap for, etc and/or | information about your setup |Comments: any? | Charlie C. Kim, User Services/AISG, Columbia University Bill Schilit