TAMU-1.0A is the latest release in the TAMU linux series.  Like the
previous release, this one includes both *integrated source* and binary
sets, with the entire binary set created from a single top level source
make. This ensures that all programs are compiled and linked with the
same current tools and libraries, and guarantees availability of working
source for every program in the binary set. 
  In addition, the boot diskette fully automates the installation
process, including partitioning, lilo bootstrapping, and network
configuration.  Installation requires no rebooting, and requires the
user to know only the host's name and IP address.  At every step of
installation, the program provides intelligent defaults, making it
a snap for novices, while allowing experts full flexibility in setting
installation parameters. Reliability has been improved over past TAMU
installation by the addition of checksums to the diskette image labels,
so that the program can detect and recover from bad images or misordered

Key Features:
	full sources available
	fully automatic installation

New in this release:
	ghostscript, fvwm, xdos, seyon, kbd, man-1.0, gprof, ...
	File System Standard Compliant!
	"rawfd" -- a super replacement for rawrite that lets you
		   ftp images directly to floppy, with on the fly
		   formatting, all in one step!

Updated in this release:
	almost everything!
	gcc-2.5.8/libc-4.5.21 (with fixes)
	installation now automatically configures smail

Bug Fixes:
	all reported bugs in the prior release fixed


  The binary and source sets are available in both diskette image and
untarred directories at (, in the directory

  This directory contains a copy of this announcement, along with
readme files "INSTALL.BIN" and "INSTALL.SRC" with respective
installation instructions.  The FTP server supports the automated
retrieval of directory hierarchies, so that any portion of the untarred
sets can be retrieved.  Note: the previous TAMU releases are still
located at  The move to the new server was necessitated to
provide adequate space for the tarred and untarred sources in the new


  The binary set includes 1 boot, and 17 bin diskette images, and the
source set includes 35 diskette images (17 and 42 respectively for 5.25
inch diskettes).  When installed, the binary set needs about 80MB of
disk space (this includes swap and filesystem overhead).  The sources
take an additional 200MB, and need around another 50MB temporarily
during compilation.  Individual packages within the sources can be
compiled independently, so you don't have to retrieve all 200MB to
modify one program.  The source packages have, however, been configured
to compile under the TAMU-1.0 binary set, so there are no guarantees
they will compile on other systems.


  The source release is based on an integrated set of source packages.
This combines the advantages of a BSD style fully integrated release
(single top level make ...), with the flexibility of separate source
packages (it's easy to drop in new versions as they appear).
  As for the religeous arguments related to the One True Directory
Structure, this release balances both esthetic and pragmatic approaches
to the problem.  On the esthetic side, one goal was to move programs
from the root filesystem (ie from /bin and /etc) that are neither
specific to the local host, nor needed for booting.  In addition,
/var is a place to catch things that were in /usr that should be local.
As for the pragmatic aspects, the sources are comprised of some 200MB
of code written by a large number of people, and one goal was to
respect their consensus view. Moving programs out of bin (such as
rm) would break enormous amounts of code, fly in the face of the
majority expectation, and not really gain much.  Many of these
pragmatic considerations are not obvious until you try to make the
stage 2 operating system (ie until you try to compile the full sources
with an operating system made from the sources.)
  One major accomplishment was to move all release programs out of 
/usr/local.  As shipped, /usr/local is empty, so that it is easy to
recognize user installed packages.  If it is in /usr/local, it really
is local.


  The obvious next steps include bug fixes, and the incorporation
of additional software packages.  A major goal for the mythical "1.0"
release will be the integration of a solid package installation/removal
system along the lines of the one in Solaris 2.x.


Please send questions, comments, and bug fixes to:
	dave safford