and link. However, it does not work yet and thus still needs work.
The *.asm files have had the following common changes:
- 'keep' lines were eliminated
- the 'mcopy' now takes the macro from the /obj/gno/bin/gsh
directory. This is in anticipation of having the macro
files generated from a single source file; there is a large
amount of duplication. For the moment, the makefile merely
copies the old macro files from the "M" directory to the
/obj/gno/bin/gsh directory.
- start each file with a dummy routine so that the source
code winds up in the *.o rather than the *.root file.
- added the 'setcom 60' directive; there were many source
lines that were otherwise getting truncated.
The makefile is a complete rewrite.
- corrected mkso command line
- explained what to do after install is complete
gshrc:
- make problem report comment more explanatory
installboot1:
- fixed up initial message
- create the /lang/orca/utilities directory
installboot2:
- fixed up initial message
- create a man hierarchy in /gno-hfs
- generalized the release target so that it can also be used
for chapter 8 programs. This is done by defining the CHAPTER
macro to be 8.
- if HAS_MKLINK_DATA or HAS_MKSO_DATA macros are set, then the
appropriate data files are copied when the 'release' target
is made.
disk, without modification.
README.install:
Installation instructions for the user.
gshrc, initrc, namespace:
For the boot disk.
installboot1, installboot2:
Installation scripts for the user to run.
Initial checkin; this script creates the installation boot
disk, /gno.boot
mkdisk1, mkdisk2:
Initial checkin; these scripts assist in the creation of the
*.shk files for the binary distribution.
fudgeinstall:
- added verbose flag to install(1) calls
- don't "fudge" install gettytab or getty any more
- make sure the mkso data files are copied over
Replaced "\(dg" with "***"; neither the current GNO nroff program
nor groff used by Linux (on which the web versions of the man
pages is generated) use "\(dg", which is supposed to be a dagger.
I did some formatting changes to make it easier for a perl
script to parse this file and create a web page showing current
status. No change to content.
The last fix wasn't quite correct in that (for copying only data
forks) the rez fork was still created but with zero length.
This fix doesn't create the rez fork at all under those
circumstances.
tar v2.0.1 binary distributed on the 'net that claimed to have fixed
an unspecified bug in this version, but neither the sources nor
the originator of that fix are available.
It may be appropriate to completely replace this implementation.
However, judging from the comments at the top of the source file,
the v2.0 changes were based on more v1.31 rather than 1.4. When
this program is updated, these diffs should be evaluated. (Unless,
of course, the current version is tossed in favor of a recent BSD
derivative.)
Here are the comments for the changes from v1.31 to v1.4 that may have
been dropped while moving to v2.0. See the cvs diffs for details:
> v1.4 - Termcap support has been added and tested. Look for a soon to be
> faster version coming soon to a ~/bin directory near you!
>
> v1.32 - uses isatty(x) instead of fstat. more portable (opinion).
> soon to be added, TERMCAP support, won't that be nice?
- use install(1) instead of cp(1) for now, since cp has been
observed to trash files.
- changed installation locations to make use of /gno and /gno-hfs
partitions.
- various changes to reflect which files have been updated
since the last time fudgeinstall was used.
