Subject: Re: install.sh fails for 1.1 alpha
To: Robin Cutshaw <robin@intercore.com>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: port-sparc
Date: 11/08/1995 18:53:51
On Wed, 8 Nov 1995 20:24:24 -0500 (EST) 
 Robin Cutshaw <robin@intercore.com> wrote:

 > During the "Making devices...", I get:
 > chgrp: kmem: illegal group name  (3 times)
 > chgrp: bin: illegal group name   (once)
 > chgrp: operator: illegal group name  (many times)
 > chown: wheel: illegal group name  (many times)
 > chown: operator: illegal group name  (many times)
 > chown: kmem: illegal group name  (once)

Looks like /etc/group is missing in the miniroot, or whatever the SPARC uses.

 > Also, this script is very confusing.  In the section where one defines the
 > root partition/disk, it doesn't mention that if you are using a /usr that
 > you should edit the fstab and add it (luckily, I guessed right).  The
 > network config section asks for an IP address and "Symbolic name?".  I
 > think hostname is much better than "Symbolic name".  The /etc/hosts
 > ends up with IP symbolicname symbolicname.domainname.

Um, actually, in at least the hp300 version that Paul based the SPARC 
version on, you are promted for additional filesystems.  The script 
displays a message like:

-----cut here-----

You will now have the opportunity to enter filesystem information.
You will be prompted for device name and mount point (full path,
including the prepending '/' character).

Note that these do not have to be in any particular order.  You will
be given the opportunity to edit the resulting 'fstab' file before
any of the filesystems are mounted.  At that time you will be able
to resolve any filesystem order dependencies.

-----cut here-----

You enter something like "sd0g" or "/dev/sd0g" (the script is smart 
enough to DTRT with either) and a mount point, and it's added to a temp 
file.  Later, an fstab is gleaned from this temp file, and you're given 
the opportunity to edit it, to resolve ordering dependencies and/or add 
NFS mounts.

As for "Symbolic name", I chose that term because, quite frankly, on 
systems with more than one network interface (like one I tested it on for 
the hp300), the name of the network interface does not necessarily match 
the hostname for the machine.  Really, you are mapping a symbolic name to 
the IP address assigned to that interface, hence the term.

Ciao.

--------------------------------------------------------------------------
Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939