6 Sep
2003
6 Sep
'03
4:23 p.m.
I've been trying to netboot a Sun 3/60. It was manuafactured in 88, so
hopefully it qualifies as "Classic".
Anyway, I'd like to get SonOS4.1.1 running, but I don't have any information
on how to get it to netboot. As a first step, I've tried to netboot NetBSD,
but had very little success and no help from the NetBSD mailing list. I've got
rarpd, bootparam and tftpd running on a linux server.
With NetBSD, the sun gets an ip address from rarpd, gets a bootloader from
tftp but then times out:
root on le0
nfs_boot: trying RARP (and RFC/bootparam)
nfs_boot: client_addr=192.0.0.10 (RARP from 192.0.0.1)
nfs_boot: timeout
Has anyone out there got this to work? On either OS?
7 Sep
7 Sep
12:26 a.m.
On Thu, 4 Sep 2003, David Coolbear wrote:
With NetBSD, the sun gets an ip address from rarpd,
gets a bootloader from
tftp but then times out:
root on le0
nfs_boot: trying RARP (and RFC/bootparam)
nfs_boot: client_addr=192.0.0.10 (RARP from 192.0.0.1)
nfs_boot: timeout
Has anyone out there got this to work? On either OS?
Yes. Make sure you also have
the Linux box export a root file
system over NFS, which is where the install files are. Your Sun
is trying to mount that directory as its root, so it can move
on to installing on the disk :)
For Netbooting xBSD, you need:
- rarpd (/etc/ethers) for giving it an IP address
- bootparamd (/etc/bootparams) for telling it where to find the
root fisk (over NFS)
- mountd (/etc/exports) for mounting the NFS disk
- nfsd (no config files) for actual NFS I/O
I usually have something called /export/OpenBSD/ on my server,
where all the OpenBSD files live:
/export/OpenBSD
/vax
/i386
/sparc
and point the clients to that in bootparams with a line line:
testvax root=vaxlab:/export/OpenBSD/vax
where 'vaxlab' is a VAX serving things here. So, the client gets an
IP address, and then tries to mount the above. When succeeded, it
will continue to load, usually the "bsd.rd" kernel which includes a
RAM disk image with just enough brains to set up things.
The above is OpenBSD, but since they all share the same code base, I
kind of assume this part of them is the same for all.
Cheers,
Fred
--
Fred N. van Kempen, DEC (Digital Equipment Corporation) Collector/Archivist
Visit the VAXlab Project at http://www.pdp11.nl/VAXlab/
Visit the Archives at http://www.pdp11.nl/
Email: waltje(a)pdp11.nl BUSSUM, THE NETHERLANDS / Sunnyvale, CA, USA
19 Sep
19 Sep
3:44 a.m.
New subject: IBM 129 keypunch in Orange Calif
I am just passing this on, please contact the Bruce directly, the items are
located in Orange, Calif.
From: Bruce Pilch <bpilch_vva(a)hotmail.com>
>Do you have any interest in an IBM 129 keypunch in
working order;
>also, new/boxed 5081 keypunch cards.
3:59 a.m.
New subject: IBM 129 keypunch in Orange Calif
If that weren't so far for me, I'd pick it up.
Peace... Sridhar
On Fri, 19 Sep 2003, Mike Ford wrote:
I am just passing this on, please contact the Bruce
directly, the items are
located in Orange, Calif.
From: Bruce Pilch <bpilch_vva(a)hotmail.com>
>>Do you have any interest in an IBM 129 keypunch in working order;
>>also, new/boxed 5081 keypunch cards.
9:37 a.m.
New subject: IBM 129 keypunch in Orange Calif
On Fri, 19 Sep 2003, Mike Ford wrote:
I am just passing this on, please contact the Bruce
directly, the items are
located in Orange, Calif.
I've already been in touch with Bruce (he contacted me directly) and am
making arrangements to pick it up ;)
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
7 Sep
7 Sep
10:06 a.m.
On 2003.09.04 11:35 David Coolbear wrote:
With NetBSD, the sun gets an ip address from rarpd,
gets a bootloader
from tftp but then times out:
root on le0
nfs_boot: trying RARP (and RFC/bootparam)
nfs_boot: client_addr=192.0.0.10 (RARP from 192.0.0.1)
nfs_boot: timeout
I had (possibly) the same error when I netbooted a SPARCstation
1+ from
a FreeBSD machine. It was quite simple. The primitive IP stack of the
netloader on the client machine can't answer arp requests. But the
server broadcasts a arp (arp, not rarp) when the tftp or NFS action is
starting. Solution was simple: Set the arp information for the client
on the host paermanent. Somthing like
arp -s 192.0.0.10 00:11:22:33:44:55 permanent
on the boot server.
I successfully installed NetBSD via netboot on a 3/60 back in the
NetBSD 1.3 days. It should still work. Did you check the NetBSD
diskless HOWTO?
SunOS, did you check http://www.sun3arc.org/ and http://www.sun3zoo.de/
If you have speciffic problems with SunOS on Sun3, ask Peter, the man
behind the Sun3 Zoo. He is very kind and helpfull.
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz
16 Sep
16 Sep
2:03 a.m.
On Sun, 7 Sep 2003, Jochen Kunz wrote:
This is why non-broken rarpd servers do this themselves :)
--f
root on le0
nfs_boot: trying RARP (and RFC/bootparam)
nfs_boot: client_addr=192.0.0.10 (RARP from 192.0.0.1)
nfs_boot: timeout
I had (possibly) the same error when I netbooted a SPARCstation
1+ from
a FreeBSD machine. It was quite simple. The primitive IP stack of the
netloader on the client machine can't answer arp requests. But the
server broadcasts a arp (arp, not rarp) when the tftp or NFS action is
starting. Solution was simple: Set the arp information for the client
on the host paermanent. Somthing like
arp -s 192.0.0.10 00:11:22:33:44:55 permanent
on the boot server.
7647
days inactive
7660
days old
6 comments
6 participants
participants (6)
-
david＠thecoolbears.org -
jkunz＠unixag-kl.fh-kl.de -
mikeford＠socal.rr.com -
vance＠neurotica.com -
vcf＠siconic.com -
waltje＠pdp11.nl