Hi,

Trying to set up a tftp boot server on S10, Have the correct /etc/ethers
and /etc/hosts entries, also tftpd service running and can transfer an
existing file to and from using localhost. The Sun 3
gets it's ip address from the server, but then we get the following
when it asks for the initial boot file:

00:20:46.555764 IP sun150.2046 > 255.255.255.255.tftp: 17 RRQ
"C009C821" octet

E..-......3.. .!.......E......C009C821.octet..
00:20:49.572804 IP darkstar.60471 > sun150.2046: UDP, length 22
E..2..@...... ... .!.7..........Access violation..

Afaics, the permisions in /export/tftpboot look ok and the tftpd is
running fine, though udp6 has transitioned to maintenance:

$ ls -l /export/tftpboot
total 202

lrwxrwxrwx 1 nobody4 nogroup 38 Jun 17 18:39 C009C821 -> /export/tftpboot/boot.sun3.sunos.4.1.1

-rwxrwxrwx 1 nobody4 nogroup 101800 Jun 17 23:15 boot.sun3.sunos.4.1.1

This is a restoration project for an old Sun 3/150 deskside
system, on the to do list for years and a nice little
project for grey Sunday afternoons. Already rebuilt the psu
with new caps throughout and other parts and now to the
system. Cpu board has 4 megs, + another 4 meg board with faults,
+ SCSI and smd disk boards. SunOs should run on 4 megs, at
least enough to get started.

Had diskless boot running on Sun 3's in the old days, but must
be missing something obvious, or are there some other access
configs to do for S10 ?. Don't want to use jumpstart process,
rather do manual configuration so we know where everything is.

Any suggestions ?...

Chris

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2018-06-17, Chris <[email protected]> wrote:

Hi,

Trying to set up a tftp boot server on S10, Have the correct /etc/ethers
and /etc/hosts entries, also tftpd service running and can transfer an existing file to and from using localhost. The Sun 3
gets it's ip address from the server, but then we get the following
when it asks for the initial boot file:

00:20:46.555764 IP sun150.2046 > 255.255.255.255.tftp: 17 RRQ
"C009C821" octet

E..-......3.. .!.......E......C009C821.octet..
00:20:49.572804 IP darkstar.60471 > sun150.2046: UDP, length 22
E..2..@...... ... .!.7..........Access violation..

Afaics, the permisions in /export/tftpboot look ok and the tftpd is
running fine, though udp6 has transitioned to maintenance:

$ ls -l /export/tftpboot
total 202

lrwxrwxrwx 1 nobody4 nogroup 38 Jun 17 18:39 C009C821 -> /export/tftpboot/boot.sun3.sunos.4.1.1

-rwxrwxrwx 1 nobody4 nogroup 101800 Jun 17 23:15 boot.sun3.sunos.4.1.1

This is a restoration project for an old Sun 3/150 deskside
system, on the to do list for years and a nice little
project for grey Sunday afternoons. Already rebuilt the psu
with new caps throughout and other parts and now to the
system. Cpu board has 4 megs, + another 4 meg board with faults,
+ SCSI and smd disk boards. SunOs should run on 4 megs, at
least enough to get started.

Had diskless boot running on Sun 3's in the old days, but must
be missing something obvious, or are there some other access
configs to do for S10 ?. Don't want to use jumpstart process,
rather do manual configuration so we know where everything is.

Any suggestions ?...

Yes -- check /etc/inetd.conf.

At the end, you will probably find:


======================================================================
# TFTPD - tftp server (primarily used for booting)
#tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
======================================================================

The second line is normally commented out, and you will need to uncomment it. *Also*, read this at the beginning of the file:

======================================================================
#
# Copyright 2004 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
#ident "@(#)inetd.conf 1.56 04/10/21 SMI"
#
# Legacy configuration file for inetd(1M). See inetd.conf(4).
#
# This file is no longer directly used to configure inetd.
# The Solaris services which were formerly configured using this file
# are now configured in the Service Management Facility (see smf(5))
# using inetadm(1M).
#
# Any records remaining in this file after installation or upgrade,
# or later created by installing additional software, must be converted
# to smf(5) services and imported into the smf repository using
# inetconv(1M), otherwise the service will not be available. Once
# a service has been converted using inetconv, further changes made to
# its entry here are not reflected in the service.
======================================================================

In earlier versions of Solaris, and older SunOs from the Sun-3
server, all you needed to do is uncomment the line, but things are
different in Solaris 10 -- and some earlier ones, though Solaris 2.6
does it the old way.

So -- you will need to uncomment it, and then run the inetconv.
(Also -- beware that tftp can be easily abused, so make this a system
which can't do much else. :-)

Once this is done, check whether the service is now running:

======================================================================
svcs | grep tftp
======================================================================

And if it shows as disabled, you'll need to enable it as root.
(Read in man page for svcadm"

Chris

Good Luck,
DoN.

--
Remove oil spill source from e-mail
Email: <[email protected]> | (KV4PH) Voice (all times): (703) 938-4564
(too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html
--- Black Holes are where God is dividing by zero ---

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Chris <[email protected]> writes:

Hi,

Trying to set up a tftp boot server on S10, Have the correct /etc/ethers
and /etc/hosts entries, also tftpd service running and can transfer an >existing file to and from using localhost. The Sun 3
gets it's ip address from the server, but then we get the following
when it asks for the initial boot file:

00:20:46.555764 IP sun150.2046 > 255.255.255.255.tftp: 17 RRQ
"C009C821" octet

E..-......3.. .!.......E......C009C821.octet..
00:20:49.572804 IP darkstar.60471 > sun150.2046: UDP, length 22
E..2..@...... ... .!.7..........Access violation..

Afaics, the permisions in /export/tftpboot look ok and the tftpd is
running fine, though udp6 has transitioned to maintenance:

$ ls -l /export/tftpboot
total 202

lrwxrwxrwx 1 nobody4 nogroup 38 Jun 17 18:39 C009C821 -> >/export/tftpboot/boot.sun3.sunos.4.1.1

-rwxrwxrwx 1 nobody4 nogroup 101800 Jun 17 23:15 boot.sun3.sunos.4.1.1

This is a restoration project for an old Sun 3/150 deskside
system, on the to do list for years and a nice little
project for grey Sunday afternoons. Already rebuilt the psu
with new caps throughout and other parts and now to the
system. Cpu board has 4 megs, + another 4 meg board with faults,
+ SCSI and smd disk boards. SunOs should run on 4 megs, at
least enough to get started.

Had diskless boot running on Sun 3's in the old days, but must
be missing something obvious, or are there some other access
configs to do for S10 ?. Don't want to use jumpstart process,
rather do manual configuration so we know where everything is.

Any suggestions ?...

Have you tried tftp by hand; you would see a failure also.

tftpboot tries to run chroot'ed and as a result, symbolic
links cannot be followed.

So try to change the symbolic link to point to
boot.sun3.sunos.4.1.1 and not the full pathname.

Mode 444 would be fine (the tftpboot directory needs to
be mode 555 (minimal). No need to make all the files
writable.

Casper

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 06/18/18 08:42, Casper H.S. Dik wrote:

Have you tried tftp by hand; you would see a failure also.

It worked fine for an empty file, but not for the linked
file.

tftpboot tries to run chroot'ed and as a result, symbolic
links cannot be followed.

That was the clue. Changed the link to:

$ ls -l
total 202
lrwxrwxrwx 1 nobody4 nogroup 23 Jun 18 12:15 C009C821 -> ./boot.sun3.sunos.4.1.1
-r--r--r-- 1 nobody4 nogroup 101800 Jun 17 23:15 boot.sun3.sunos.4.1.1 -r--r--r-- 1 nobody4 nogroup 0 Jun 18 12:07 fred

...and it worked. Spent a few hours on this yesterday, but
sometimes better to ask and also to sleep on the problem. Been
doing this in stages, first rarp, then tftp, then bootparams etc.
Did a complete tar backup of another Sun 3 box to the server
last year, so should be able to point to that to get the system
running. If you are working with a range of older machines, it's
useful to have network boot capability.

Thanks both for the help with this...

Chris

So try to change the symbolic link to point to
boot.sun3.sunos.4.1.1 and not the full pathname.

Mode 444 would be fine (the tftpboot directory needs to
be mode 555 (minimal). No need to make all the files
writable.

Casper

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Not so many years ago, I had net booted a Sun 3/E.

There are a few things that need to work.

First is rarp.
Second is bootparamd.
Third is NFS.

For reasons that I didn't figure out, I had to use three different computers to do that.

The NFS host is a Toshiba Canvio SAN device with a 3TB disk in it.
(SunOS doesn't mind that, though I believe that df gives the wrong size.)

I might have done tftp on an Apple, and bootparamd on some other system.

And then I mostly manually created the root file system, using the files on the install CD, but not the install script.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/13/23 06:52, gah4 wrote:

Not so many years ago, I had net booted a Sun 3/E.

There are a few things that need to work.

First is rarp.
Second is bootparamd.
Third is NFS.

For reasons that I didn't figure out, I had to use three different computers to do that.

The NFS host is a Toshiba Canvio SAN device with a 3TB disk in it.
(SunOS doesn't mind that, though I believe that df gives the wrong size.)

I might have done tftp on an Apple, and bootparamd on some other system.

And then I mostly manually created the root file system, using the files on the
install CD, but not the install script.

Been a while, and no longer have the machine, but did get it working
in the end, from a single sol 10 machine.

You need rarpd, tftpd, bootparamsd and associated files in /etc. That
and an nfs file set in the right order in an an accessable location.

I know it's old hat, but still prefer it for Sun machines, rather than
dhcp / bootp...

Chris

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)