Xref: utzoo comp.unix.shell:1810 comp.sources.wanted:16143 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!bbn.com!papaya.bbn.com!rsalz From: rsalz@bbn.com (Rich Salz) Newsgroups: comp.unix.shell,comp.sources.wanted Subject: Re: tcsh source without csh source license Message-ID: <3471@litchi.bbn.com> Date: 4 Apr 91 19:32:17 GMT References: <1991Mar29.112634.1244@nestroy.wu-wien.ac.at> <1991Mar31.114804.13952@maverick.ksu.ksu.edu> Followup-To: comp.unix.shell Organization: BBN Systems and Technology, Inc. Lines: 23 tom@itc.univie.ac.at (Tom Kovar) writes: > I remember some time ago I heard about tcsh source which did not require > the csh source for compilation ... In <1991Mar31.114804.13952@maverick.ksu.ksu.edu> tar@math.ksu.edu (Tim Ramsey) writes: >It's not a myth; I use it here. Grab the 4.3bsd-reno csh sources from >wuarchive.wustl.edu (128.252.135.4) or wherever else they are ... I'm not sure what Tim is using, but it isn't the "free'd" Reno distribution. The csh directory in the source tree includes csh.1, pathnames.h and doprnt.c -- hardly enough to build csh! You cannot build tcsh without having csh sources. You currently cannot get csh sources without having an BSD source license. You cannot get a BSD source license without having an ATT source license. It is possible that csh will show up in part of the free'd BSD sources when 4.4 comes out. This will not be a full Unix release, just stuff known to not have AT&T licensing restrictions. /r$ -- Please send comp.sources.unix-related mail to rsalz@uunet.uu.net. Use a domain-based address or give alternate paths, or you may lose out.