1
0
Fork 0
mirror of git://git.code.sf.net/p/cdesktopenv/code synced 2025-02-13 19:52:20 +00:00

dtksh: remove old ksh from repo

This commit is contained in:
Chase 2020-07-22 20:32:47 -05:00 committed by Jon Trulson
parent 0f3bcae232
commit 0069a6e084
871 changed files with 0 additions and 192840 deletions

View file

@ -1,73 +0,0 @@
XCOMM $XConsortium: Imakefile /main/7 1996/05/09 17:33:38 drk $
LOCAL_LIBRARIES =
SRCS =
SUBCFLAGS = -O
UFLAGS = $(SUBCFLAGS)
ULDFLAGS =
IFFECDEBUGFLAGS = -O0
#ifdef RsArchitecture
CCFLAGS = CCFLAGS=" "
#else
CCFLAGS =
#endif
#ifdef SunArchitecture
.NO_PARALLEL:
#endif /* SunArchitecture */
FORCE_SHIP = -F
MALLOCOBJ =
KSHSRC = ./src/cmd/ksh93
KSHLIBS = \
$(KSHSRC)/../../lib/libcmd/libcmd.a
KSH_OBJS = \
$(KSHSRC)/main.o \
$(KSHSRC)/timers.o \
$(KSHLIBS)
OBJS = $(KSH_OBJS) $(KSH_LIBS)
SUIDEXECDEFINES = \
-DPROFILEPATH=\"$(CDE_CONFIGURATION_TOP)/config/profile\" \
-DSUIDPROFILEPATH=\"$(CDE_CONFIGURATION_TOP)/config/suid_profile\" \
-DSUIDEXECPATH=\"$(CDE_INSTALLATION_TOP)/bin/suid_exec\" \
-DCDE_INSTALLATION_TOP=\"$(CDE_INSTALLATION_TOP)\"
CCFLAGS = $(CDEBUGFLAGS) $(SUIDEXECDEFINES) $(STD_DEFINES) $(ANSI_DEFINES)
ICCFLAGS = $(IFFECDEBUGFLAGS) $(STD_DEFINES) $(ANSI_DEFINES)
all:: ksh93src ksh93.o
XCOMM
XCOMM A temporary hack until we get Imakefiles in the base of ksh-93.
XCOMM
XCOMM We test for presense of /bin/ksh because on HP/UX there is a
XCOMM limitation in the size of environment variables that prevents the
XCOMM ksh-93 build scripts from functioning. That will be worked around
XCOMM in a near future release of ksh-93 as well, but then again this
XCOMM whole target will change anyway.
XCOMM
SHIP_DIR = ship
ALL_SUBS = *
ksh93src:
$(RM) $(SHIP_DIR)/$(ALL_SUBS)/$(ALL_SUBS)/BUILT; \
SHELL=$(KORNSHELL) CC="$(CC)" CCFLAGS="$(CCFLAGS)" ICCFLAGS="$(ICCFLAGS)" $(KORNSHELL) ship/shipin $(FORCE_SHIP)
ksh93.o: $(OBJS)
$(LD) -r -o $@ $(OBJS)
clobber:: clobmine
clobmine:
$(RM) -f libksh93.a
depend::
install::

View file

@ -1,154 +0,0 @@
/* $XConsortium: README /main/2 1996/07/15 14:13:29 drk $ */
Software shipment information. [better documentation forthcoming ...]
All files and directories, except for those in /var/spool/uucppublic,
are rooted at the shipment/installation directory named by
$INSTALLROOT. The $INSTALLROOT hierarchy is similar to the System V
/usr hierarchy.
The $INSTALLROOT/ship subdirectory is automatically maintained by
shipin and shipout. If you expect to receive future shipments then
do not change files in this directory.
pax is the Bell Labs implementation of the proposed POSIX (01/90)
portable archive interchange command. The default output format is
`cpio -c'. The pax delta format is a Bell Labs extension.
The following assumes:
INSTALLROOT=<path name of software installation root directory>
After each shipment:
<follow specific shipment instructions>
cd $INSTALLROOT
ship/shipin
`ship/shipin -n' shows actions but does not unbundle or build.
`ship/shipin -s <dir>' unbundles from <dir> rather than /var/spool/uucppublic.
`ship/shipin -u' unbundles the shipment but does not build.
`ship/shipin -i' copies from spool area but does not unbundle or build.
`ship/shipin -E' rebuild components that failed last time (use after fixes).
Any non-option arguments to shipin are passed as arguments to the
generating make or shell script for each component.
To pass the shipment to another machine (requires ksh):
# rcp # TO=host:ship
# uucp # TO=machine!user
# list of files # TO=%list
# remote dk pull script # TO=%pull
cd $INSTALLROOT
ship/shipin -i # if not installed on this machine
cd ship
shipout $TO
{rcp,uucp} initiate copies whereas {list,pull} generate information on
stdout. {uucp} copies to an intermediate spool area on the other machine
whereas {rcp,list,pull} are relative to $INSTALLROOT on the other machine.
To copy a command <cmd> from $INSTALLROOT to a new root you must copy:
$INSTALLROOT/bin/<cmd>
$INSTALLROOT/lib/<cmd>
to the new root directory for all interdependent <cmd>'s. Depending on
<cmd>, only one of the above files/directories may exist.
Be sure to maintain a different $INSTALLROOT for each machine architecture.
If the same $INSTALLROOT/ship must be reused for a different architecture
then delete everything except ship from $INSTALLROOT and run ship/shipin -F.
An alternative would be to use nmake and optionally 3d to viewpath a new
architecture hierarchy on top of $INSTALLROOT. In this case nmake would
be run from within the $INSTALLROOT/src/(cmd|lib) hierarchy.
The files below may appear on the shipment side, the installation side,
or both. <installer-login> and <shipper-system> are defined in the
shipment mail announcement.
Each shipment is identified by a two part version number [R]YYMMDD
R release -- if specified then it must match for compatibility
YYMMDD shipment year, month and day number
/var/spool/uucppublic/<installer-login>/<shipper-system> directory hierarchy:
<shipper-login>.<YYMMDD> shipment control directory
<shipper-login>.<YYMMDD>/manifest list of all files in shipment
$INSTALLROOT directory hierarchy:
bin/ executable binaries and scripts
include/ common header files
lib/ object archives a common data
man/ man page subtree
man1/ command man pages
man3/ library man pages
man8/ adminstration and maintenance man pages
src/ source subtree
cmd/ command source
lib/ library source
ship/ shipment and installation info
$INSTALLROOT/ship contents:
README installation info
!<mach_user> shipment installation message for machine!user
ship.body optional shipment announcement main body
ship.head optional shipment announcement header
ship.tail optional shipment announcement trailer
shipcost show relative cost of delta/update shipment
shipcrate crate all components for shipout
shipin unbundle, build and install shipment
shiplist shipout using name-tool list
shipop shipin/shipout support executable
shipout split and send shipment
shipslog shipment log and recipient address info
shipswab clean old stuff from the ship area
shipyard shipment support tools component name
lib* library components
* command components
$INSTALLROOT/ship/<component> contents:
<[R]YYMMDD> information for the <[R]YYMMDD> shipment
base link to the newest pax base archive
delta link to the newest pax delta archive
in.log shipin log
items required components (excluding this one)
list optional list of persons to send to
message optional message to include in shipment announcement
owner mail address for installation report
release the the current shipment release number
report optional list of $INSTALLROOT relative files to report
$INSTALLROOT/ship/<component>/<[R]YYMMDD> contents:
<[R]YYMMDD> pax delta archive for ../[R]YYMMDD/base
<[R]YYMMDD>.<NNN> delta archive split for uucp
BUILT present if release build succeeded
ERROR present if release build failed
GENERATED present if base archive was generated from a delta
UNCRATED present if release uncrate succeeded
base pax base archive
base.<NNN> base archive split for uucp
items items for this release
message message for this release
owner owner for this release
report report for this release
Each component $NAME is extracted into either $INSTALLROOT/src/lib/$NAME
or $INSTALLROOT/src/cmd/$NAME. The following are attempted, in order,
to build and install $NAME under $INSTALLROOT:
$INSTALLROOT/bin/nmake -f Makefile install
mamexec install < Mamfile # mamexec is built into ship/shipin
make -f makefile install
sh Makescript
where Mamfile, Makescript and makefile are usually generated from the
corresponding nmake Makefile.
Glenn Fowler ulysses!gsf
David Korn ulysses!dgk

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Advanced Software Technology Department
{ulysses,attmail}!dgk
dgk@ulysses.att.com
David Korn 908-582-7975

View file

@ -1 +0,0 @@
libcmd libast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!dgk

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Advanced Software Technology Department
{ulysses,attmail}!dgk
dgk@ulysses.att.com
David Korn 908-582-7975

View file

@ -1 +0,0 @@
libcmd libast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!dgk

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Advanced Software Technology Department
{research,attmail}!dgk
dgk@research.att.com
David Korn 908-582-7975

View file

@ -1 +0,0 @@
libcmd libast

View file

@ -1,32 +0,0 @@
The is the fourth point release for ksh-93. The RELEASEa
file contains a list of changes since the first release for ksh-93.
The file RELEASE lists the major changes since ksh-88. I have updated
the man page, sh.1, and the introductory memo, sh.memo. I have also
started to write a guideline for adding runtime builtins, builtins.mm.
This release should correspond very closely to the information in the
New KornShell Command and Programming Language book, by Bolsky
and Korn.
This official release is being distributed and supported by the
Software Technology Center. They are the distributor of
ksh93 within AT&T and will provide support. I will only be
supplying ksh93 for research needs and for machine architectures
that are not supported by the Software Technology Center.
You can contact the STC by sending mail to ksh@mozart.att.com.
I have fixed most of the bugs that have been reported in
the previous release. Let me know about any remaining bugs.
There continues to be very few reports of compatibility
problems. The file COMPATIBILITY lists the known incompatibilities.
Please let me know about any script which runs under ksh-88 but
does not run under ksh-93.
Please look at the man page (troff -man) and the sh.memo
file (troff -mm) and let me know what problems you find.
I encourage you to run ksh -n script on each of your scripts
since the -n option produces warning messages for obsolete
features that you are using in the script. The file
OBSOLETE, written by Kevin Wall, contains a list of
obsolete features.

View file

@ -1 +0,0 @@
dgk

View file

@ -1,146 +0,0 @@
.SA 1
.sp 2
.H 1 "KSH-93 - The KornShell Command and Programming Language"
.sp 2
.al
.P
KSH-93 is the most recent version of the KornShell Language
described in
"The KornShell Command and Programming Language,"
by Morris Bolsky and David Korn of AT&T Bell Laboratories.
The KornShell is a shell programming language,
which is upward compatible with "sh" (the Bourne Shell),
and is intended to conform to the IEEE P1003.2/ISO 9945.2 Shell and
Utilities standard.
KSH-93 provides an enhanced programming environment in
addition to the major command-entry features of the BSD
shell "csh". With KSH-93, medium-sized programming tasks can be
performed at shell-level without a significant loss in performance.
In addition, "sh" scripts can be run on KSH-93 without modification.
.P
The code should conform to the IEEE POSIX 1003.1 standard and to the
proposed ANSI-C standard so that it should be portable to all
such systems. Like the previous version, KSH-88,
it is designed to accept eight bit character sets
transparently, thereby making it internationally compatible.
It can support multi-byte characters sets with some characteristics
of the character set given at run time.
.P
KSH-93 provides the following features, many of which were also inherent
in KSH-88:
.BL
.LI
Enhanced Command Re-entry Capability: The KSH-93 history
function records commands entered at any shell level and stores
them, up to a user-specified limit, even after you log off.
This allows you to re-enter long commands with a few keystrokes
- even those commands you entered yesterday.
The history file allows for eight bit characters in
commands and supports essentially unlimited size histories.
.LI
In-line Editing: In "sh", the only way to fix mistyped
commands is to backspace or retype the line. KSH-93 allows you
to edit a command line using a choice of EMACS-TC or "vi"
functions.
You can use the in-line editors to complete filenames as
you type them.
You may also use this editing feature when entering
command lines from your history file.
A user can capture keystrokes and rebind keys to customize the
editing interface.
.LI
Extended I/O Capabilities: KSH-93 provides several I/O
capabilities not available in "sh", including the ability to:
.BL
.LI
specify a file descriptor for input and output
.LI
start up and run co-processes
.LI
produce a prompt at the terminal before a read
.LI
easily format and interpret responses to a menu
.LI
echo lines exactly as output without escape processing
.LI
format output using printf formats.
.LI
read and echo lines ending in "\e".
.LE
.LI
Improved performance: KSH-93 executes many scripts faster
than the System V Bourne shell. A major reason for this is
that many of the standard utilities are built-in.
To reduce the time to initiate a command, KSH-93 allows
commands to be added as built-ins at run time
on systems that support dynamic loading such as System V Release 4.
.LI
Arithmetic: KSH-93 allows you to do integer arithmetic in any
base from two to sixty-four. You can also do double
precision floating point arithmetic.
Almost the complete set of C language operators are available
with the same syntax and precedence.
Arithmetic expressions can be used to as an argument expansion
or as a separate command.
In addition there is an arithmetic for command that works
like the for statement in C.
.LI
Arrays: KSH-93 supports both indexed and associative arrays.
The subscript for an indexed array is an arithmetic expression,
whereas, the subscript for an associative array is a string.
.LI
Shell Functions and Aliases: Two mechanisms - functions and
aliases - can be used to assign a user-selected identifier to
an existing command or shell script.
Functions allow local variables and provide scoping
for exception handling.
Functions can be searched for and loaded on first reference the
way scripts are.
.LI
Substring Capabilities: KSH-93 allows you to create a
substring of any given string either by specifying the starting
offset and length, or by stripping off leading
or trailing substrings during parameter substitution.
You can also specify attributes, such as upper and lower case,
field width, and justification to shell variables.
.LI
More pattern matching capabilities: KSH-93 allows you to specify
extended regular expressions for file and string matches.
.LI
KSH-93 uses a hierarchal name space for variables.
Compound variables can be defined and variables can
be passed by reference. In addition, each variable
can have one or more disciplines associated with
it to intercept assignments and references.
.LI
Improved debugging: KSH-93 can generate line numbers on execution
traces. Also, I/O redirections are now traced.
There is a DEBUG trap that gets evaluated after each command
so that errors can be localized.
.LI
Job Control: On systems that support job control, including
System V Release 4, KSH-93
provides a job-control mechanism almost identical to that of
the BSD "csh", version 4.1.
This feature allows you
to stop and restart programs, and to move programs between the
foreground and the background.
.LI
Added security:
KSH-93 can execute scripts which do not have read permission
and scripts which have the setuid and/or setgid set when
invoked by name, rather than as an argument to the shell.
It is possible to log or control the execution of setuid and/or
setgid scripts.
The noclobber option prevents you from accidentally erasing
a file by redirecting to an existing file.
.LI
KSH-93 can be extended by adding built-in commands at run time.
In addition, KSH-93 can be used as a library that can
be embedded into an application to allow scripting.
.LE
Documentation for KSH-93 consists of an "Introduction to KSH-93",
"Compatibility with the Bourne Shell" and a manual page and a
README file. In addition, the "New KornShell Command and Programming
Language," book is available from Prentice Hall.

View file

@ -1,5 +0,0 @@
src/cmd/ksh93/FEATURE/options
src/cmd/ksh93/FEATURE/ttys
src/cmd/ksh93/FEATURE/dymamic
src/cmd/ksh93/FEATURE/externs
src/cmd/ksh93/FEATURE/poll

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Advanced Software Technology Department
{ulysses,attmail}!dgk
dgk@ulysses.att.com
David Korn 908-582-7975

View file

@ -1,6 +0,0 @@
type=proprietary
corporation=AT&T
company="Bell Laboratories"
organization="Software Engineering Research Department"
license=http://www.research.att.com/orgs/ssr/book/reuse
contact=gsf@research.att.com

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Software Engineering Research Department
advsoft@research.att.com
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Software Engineering Research Department
advsoft@research.att.com
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
libAST

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Software Engineering Research Department
advsoft@research.att.com
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
lib0ast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

View file

@ -1,6 +0,0 @@
type=proprietary
corporation=AT&T
company="Bell Laboratories"
organization="Software Engineering Research Department"
license=http://www.research.att.com/orgs/ssr/book/reuse
contact=gsf@research.att.com

View file

@ -1 +0,0 @@
lib0ast

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Software Engineering Research Department
advsoft@research.att.com
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
libast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Software Engineering Research Department
advsoft@research.att.com
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
libast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

View file

@ -1,6 +0,0 @@
type=proprietary
corporation=AT&T
company="Bell Laboratories"
organization="Software Engineering Research Department"
license=http://www.research.att.com/orgs/ssr/book/reuse
contact=gsf@research.att.com

View file

@ -1 +0,0 @@
lib0ast

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Advanced Software Technology Department
{ulysses,attmail}!advsoft
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
libast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Advanced Software Technology Department
{ulysses,attmail}!advsoft
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
libast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

View file

@ -1,6 +0,0 @@
type=proprietary
corporation=AT&T
company="Bell Laboratories"
organization="Software Engineering Research Department"
license=http://www.research.att.com/orgs/ssr/book/reuse
contact=gsf@research.att.com

View file

@ -1 +0,0 @@
libast

View file

@ -1 +0,0 @@
libast

View file

@ -1,6 +0,0 @@
type=proprietary
corporation=AT&T
company="Bell Laboratories"
organization="Software Engineering Research Department"
license=http://www.research.att.com/orgs/ssr/book/reuse
contact=gsf@research.att.com

View file

@ -1 +0,0 @@
libast

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Software Engineering Research Department
advsoft@research.att.com
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
libodelta libast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

View file

@ -1,5 +0,0 @@
AT&T Bell Laboratories
Software Engineering Research Department
advsoft@research.att.com
Randy Hackbarth 908-582-5245
Dave Belanger 908-582-7427

View file

@ -1 +0,0 @@
libvdelta libodelta libast

View file

@ -1 +0,0 @@
liszt!easy!liszt!easy!usl!att!gryphon!gsf

Some files were not shown because too many files have changed in this diff Show more