Subject: **now** I'm confused....
To: email@example.com <firstname.lastname@example.org>
From: TechSupp <email@example.com>
Date: 05/04/1999 02:53:01
Goodgrief....alright, I've got around most of the curley bits,
got rarp/tftpd & bootparamd doing the tango, got the 3/50 booting an
older netboot [one that comes with 1.3.2 seems spooked by md0], have
edlabelled the hdrive, and got to the stage of dd'ing the miniroot
across to /dev/rsd0b , BUT.....
Okay...superfluous dross from bootparamd goes like this;]
[root@hyper /tftpboot]# rpc.bootparamd -d -r 192.168.1.1
whoami got question for 192.168.1.12
This is host xhost.hypermax.net.au
Returning xhost 192.168.1.1
getfile got question for "xhost" and file "root"
returning server:hyper path:/sun address: 192.168.1.1
..that's okay...weirder but none the less working, it also informs to
May 4 02:22:34 hyper tftpd: tftpd: trying to get file: C0A8010C
May 4 02:22:34 hyper tftpd: tftpd: serving file from /tftpboot
May 4 02:22:37 hyper mountd: NFS mount of /sun attempted from
May 4 02:22:37 hyper mountd: /sun has been mounted by 192.168.1.12
May 4 02:25:20 hyper nfsd: NFS request from xhost.hypermax.net.au
originated on insecure port, psychoanalysis suggested
Now...that last line is the result of trying to dd the miniroot across,
although the same error is generated by a plain ls /mnt on the 3/50.
The interesting bit however, is if I do ls or try to dd the miniroot, I
get a 'permission denied' flag on the sun....which is kind-of weird I
thought, because the ramdisk_kernel (already booted by this stage) lives
in the same dir?
On the serving box (the redhat), I get;
[root@hyper /sun]# ls -l
-rw-r--r-- 1 root root 8388608 Apr 22 06:49 miniroot
-rw-r--r-- 1 root root 837481 May 3 20:54 netbsd
Hmmmm...I dunno. The nfs <dir> on the redhat is exported
(rw,no_root_squash), I can't see any permission duress on the redhat
machine, it just **seems** like the 3/50 doesn't believe it has rights
to the miniroot file, though why this is so is beyond my
I have no idea..the cmd fron the Sun side is a vanilla mount -r
192.168.1.1:/sun /mnt, and it's happy to ls the mounted filesys and
show me the contents *except* the miniroot??...pffft!
Any ideas/remedies greatly appreciated, elsewise I might take up
the syslog advice of some mental help B^)
Thanks in advance,
ps: btw, earlier probs with bootparamd seem mooted in the bootparams
file itself, and the fact that merely stating a /etc/exports of root
(/) was not on...exact dir statements were necessary...