gno/verbatim/boot
gdr-ftp 61fdf9319e installboot1:
- run the (generated) /tmp/mklinks script so that certain
	  programs are duplicated under different names.  It would be
	  nice to have symlinks instead.
1999-02-15 20:15:34 +00:00
..
gshrc gshrc: 1999-01-28 05:34:38 +00:00
initrc These are all initial checkins. These files go onto the /gno.boot 1998-04-22 04:57:38 +00:00
installboot1 installboot1: 1999-02-15 20:15:34 +00:00
installboot2 README.install: 1998-04-24 06:02:21 +00:00
namespace These are all initial checkins. These files go onto the /gno.boot 1998-04-22 04:57:38 +00:00
README.install README.install: 1999-02-15 18:56:17 +00:00

$Id: README.install,v 1.7 1999/02/15 18:56:17 gdr-ftp Exp $

The install scripts assumes that your _new_ distribution will be installed
on to the two volumes /gno (ProDOS) and /gno-hfs (HFS).  It also assumes
these volumes already exist and are _empty_.  You may use other volume names,
but you will have to edit certain files before you run your distribution.
If your volumes are named something else, replace the names in the cd commands
below with the appropriate name.
 
You should now do the following steps:
	 1.  Set your DOWNLOAD_DIR environment variable to the directory
	     into which you placed the base distribution NuFX archive files
	     (gnoboot.shk, gnohfs.shk, gno.01.shk, and so forth).  For
	     example, if the NuFX files were in /download, you would type:
	     
		     	setenv DOWNLOAD_DIR /download
	     
	     Ensure that you use slashes ("/") rather than colons (":") as the
	     pathname delimiter.  Do not use a trailing slash.
	     
	 2.  Install the majority of the GNO base distribution files by
	     changing directory into your destination directory and running
	     the installboot1 script. Assuming that you will be installing
	     to the partition /gno, the commands would be:
	     
		     	cd /gno
		     	/gno.boot/installboot1
	     
	     This step takes quite a while, even with an accelerated IIgs.
	     Have patience.
	     
	 3.  There are a small number of recommended files that do not follow
	     ProDOS naming conventions.  If you wish to install these files,
	     make sure that you have an HFS or Appleshare disk online. Change
	     directories to that disk (or subdirectory) and run installboot2.
	     Assuming that the HFS disk is /gno-hfs, the commands are:
	     
		     	cd /gno-hfs
		     	/gno.boot/installboot2
	     
	     This step is optional.  It is possible to use the GNO binary
	     distribution without an HFS partition, but some information
	     will be missing.
	     
	 4.  You should now edit the file /gno/etc/namespace.  If your
	     files were extracted onto a volume other than /gno, you will
	     have to replace all the ":gno:" strings with the appropriate
	     path.  Similarily, you will have to replace ":gno-hfs:" if
	     that is not the name of your HFS (or Appleshare) partition
	     where you ran the installboot2 script.  Note that you cannot
	     currently use pathnames in the namespace file that contain spaces.
	     
	     The gno.boot disk includes the vi utility to do these edits.
	     You can also edit the namespace file with any other text editor
	     of your choosing, as long as it is done before you try to run
	     your new GNO distribution.
	     
	     A vi tutorial and quick reference guide may be found at
	     http://www.jaws.umn.edu/~tobkin/vi.
	     
	     For a description of the namespace file, see the kernel
	     reference manual, or the namespace(5) manual page at
	     http://www.gno.org/~gno/man/man5/namespace.5.html
	     
	 5.  During the extraction process, the following files were placed
	     into the /gno/System directory:
	     
		     	/gno/System/Desk.Accs/GNOSnooperII
		     	/gno/System/Desk.Accs/SuspDA
		     	/gno/System/Desk.Accs/TMTerm
		     	/gno/System/Drivers/FilePort
		     	/gno/System/Drivers/FilePort.Data
		     	/gno/System/Drivers/NullPort
		     	/gno/System/System.Setup/GNOBug
		     	/gno/System/System.Setup/SIM
	     
	     It is recommended that these files be copied into the relevent
	     directories in the System folder of your boot partition.  The
	     GNOBug PIF is only required if you have GSBug installed.  If
	     you install GNOBug you should afterward sort the System.Setup
	     directory so that GNOBug appears before GSBug (the latter of
	     which is commonly called "debug.init").
	     
	 6.  If you are not short of disk space, you should create .so links
	     for your manual pages.  (See the mkso(8) man page for an
	     explanation.)  You can do this by executing the following
	     commands:
	     
		     	cd /gno/usr/man
		     	mkso -v -H /gno-hfs/man mkso.data
	     
	     If you installed GNO somewhere other than /gno and /gno-hfs, then
	     edit the above lines accordingly.  If you did not install files
	     onto an HFS (or Appleshare) partition at all, then execute the
	     following commands instead:
	     
		     	cd /gno/usr/man
		     	mkso -v mkso.data
	     
	 7.  You can now return to your program launcher (the Finder,
	     ProSEL-16, or whatever you used to start /gno.boot/kern) by
	     typing "exit" at the prompt.  To startup up your new version
	     of GNO, you should then launch /gno/kern.  You will then see
	     a "login:" prompt.  Enter "root" as the user name; you will
	     not yet need a password.