lblock@almsa-1.ARPA (Laurie A. Block) (09/17/85)
Does anyone know if RCS and NROFF software packages run under System V? If so, how do I get the source code? Laurie lblock@almsa-1
lblock@almsa-1.ARPA (Laurie A. Block) (09/17/85)
Sorry, I forgot to mention that we want the "me" macro package of NROFF. Thanks Laurie
wcs@ho95e.UUCP (Bill.Stewart.4K435.x0705) (09/18/85)
> > Does anyone know if RCS and NROFF software packages run under System V? > > If so, how do I get the source code? > > > > Laurie > lblock@almsa-1 > > RCS is a 4.2BSD package and doesn't come with System V (has anyone done a port?). > Nroff is (originally) an AT&T Bell Labs product; the System V version is > somewhat improved from the version in 4.1BSD (4.2 may have done some > improvements also.) > > The ONLY way to get source code is TO GET A SOURCE LICENSE! If your System V > system is only a binary-licensed system, find out from the vendor about getting > the binaries for nroff. For recent AT&T computers (3B2, UNIX PC 7300), AT&T > has unbundled the UNIX system; you don''t get the Text Processing Utilities > (nroff, (di)troff, etc.) with the operating system - you have to order them > separately. The AT&T UNIX Software Sales people are in North Carolina, phone > number 1-800-828-UNIX. > Bill Stewart (I just saw your followup about wanting -me macros - sorry): The -me macros are a Berkeleyism. I suppose they'd probably work ok on System V nroff. They should be available on a 4.*BSD system, probably in source form under /usr/lib/macros, even if you just have a Binary license. -- ## Bill Stewart, AT&T Bell Labs, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcs
guy@sun.uucp (Guy Harris) (09/20/85)
> Nroff is (originally) an AT&T Bell Labs product; Still is, unless it's considered an AT&T-IS product now. > the System V version is somewhat improved from the version in 4.1BSD (4.2 > may have done some improvements also. The 4.2 version is a minor change from the 4.1 version, which is in turn still pretty much the V7 version. They added some changes that I've been told are necessary to make the "-me" package run (those are the lines flagged with the famous Berkeley comment /* XXX */). They also changed it to keep the temporary "file" in memory. This can be put into the S5 version as well. NOTE: the "INCORE" option for the S5 nroff is *not* what you want. It's for large VM machines which aren't running UNIX; it uses "malloc" instead of "sbrk" and standard I/O instead of read/write. At the time I was playing with it, changing it to use "malloc" made it run *lots* slower - which is the last thing "nroff" needs. I can't speak for the standard I/O vs. UNIX I/O difference. Also, the INCORE option disables "compacted macro packages"; the S5 "nroff" can be told to dump its temporary file with some header glop after reading in a macro package, and then can reload its temporary file. This may speed up loading of macro packages, especially monsters like "mm", so you may not want to eliminate it. (The macro package needs to be hacked up to make this work, so if you want to speed up loading of "me" be prepared to spend some time on it.) > The -me macros are a Berkeleyism. I suppose they'd probably work ok on > System V nroff. They seemed to, after the /* XXX */ stuff was stuck in (I believe we were able to format the Sendmail documentation at CCI). I don't know about vanilla S5 nroff, but you might give it a try. > They should be available on a 4.*BSD system, probably in > source form under /usr/lib/macros, even if you just have a Binary license. They are, but the source is in /usr/lib/me (there is no /usr/lib/macros on 4.xBSD or V7). Guy Harris