Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Mar 2002 21:35:07 -0500
From:      Garance A Drosihn <drosih@rpi.edu>
To:        bmah@FreeBSD.ORG
Cc:        freebsd-sparc@FreeBSD.ORG
Subject:   Re: DP1 release candidate 1
Message-ID:  <p05101531b8c18d0ae98e@[128.113.24.47]>
In-Reply-To: <200203230002.g2N02k072474@bmah.dyndns.org>
References:  <20020321195254.N90182@locore.ca> <p0510152cb8c161daca4b@[128.113.24.47]> <200203230002.g2N02k072474@bmah.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help

At 4:02 PM -0800 3/22/02, Bruce A. Mah wrote:
>If memory serves me right, Garance A Drosihn wrote:
>
>  > Should I send along a few lines describing the exact
>  > steps that I went thru?  Anything I write would only cover
>  > the cdrom-install, not the network install (although I
>  > imagine it would also apply there).
>
>Sure...this would be great.

The following may be a bit specific to my situation, so I will
describe that.  I have an ultra-10 which I was going to use
just for freebsd (no solaris install, no dual-boot).  Still,
I think it helps to have at least one specific example, and
tell people that they need to know the difference between that
example and what they intend to do.

Some early section, like "1.1 Preparation", might want to note
that it is very convenient to have some other machine around
which is running freebsd (i386 or alpha), just for reference
purposes and for man pages.  The sparc64 image doesn't seem to
include man pages.

Section 1.4 might want to suggest that the user make at least
four partitions:
     a: for /       (I went with ~150 meg, but ~100 would do fine)
     b: for swap    (~300 meg, because it was twice 150 :-)
     e: for /var    (~150 again)
     f: for /usr    (> 2.5gig)

Other than suggesting a size for /, the notes probably shouldn't
say too much about sizes.  People not used to current might think
40-50meg would be plenty for /, and I think that's too small...

The disklabel step might be a place to mention the user should
check stty settings.  It's the first time someone would be in vi,
and I was fairly confused about vi's behavior when I went to add
some lines until it occurred to me that it wasn't using the whole
screen.  On the other hand, that might be too nit-picky of a detail.

Once the user has a disk label, they need to newfs the partitions.
My disk was 'ad0' (on an ultra-10), and I was using the entire
disk for freebsd, so I did:
     newfs /dev/ad0a
     newfs /dev/ad0e
     newfs /dev/ad0f

(I don't know if we want to mention 'newfs -U' for softupdates,
either to suggest it or to recommend against it).

With the newfs's done, you then want to get the files on it.  While
still running on the bootup from the cdrom, I went with:
     mount /dev/ad0a /mnt

     mkdir /mnt/usr /mnt/var
     mount /dev/ad0e /mnt/var
     mount /dev/ad0f /mnt/usr

     cd /mnt
     ls               # just to make sure I was in the right spot
     tar xpf /root/distrib-20020320.tar
     cd /mnt/etc
     vi /etc/fstab
             #  add the appropriate entries.
             #  this is where it'd be nice to have a
             #  sample fstab.ad0 on the image.
     shutdown -h now

The shutdown will get you back to the prom prompt.  The prom is
going to remember that you booted up off the cdrom.  There is a
'help' command in the prom to find out what options it has, but
in my case I typed in the prom command:
     boot disk0:a

This boots up the system, with a null password set for root.  The
first thing you should do is run passwd to set a password!  Then
you might want to add the appropriate network-config lines to your
/etc/rc.conf file, add DNS information in /etc/resolv.conf, and
reboot again.  (this is another case where it's convenient to have
another freebsd machine around, so you can see what *it* has in
it's /etc/rc.conf and /etc/resolv.conf for network setup).

At this point, you should have a freebsd/sparc64 system up and
running on the network.  I was able to ping other hosts, and was
able to add:  enable_sshd="YES"
to /etc/rc.conf so I could ssh in from my other machines.

-- 
Garance Alistair Drosehn            =   gad@eclipse.acs.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-sparc" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101531b8c18d0ae98e>