Greetings,
I've used /usr/sbin/dmu to set up a /var/adm/dms/ris0.alpha area on
an Alpha AXP 3000/300X running DU 3.2D-1. The ris area contains
DU 3.2C upgraded to 3.2D following the Release Notes and Installation
Instructions for Version 3.2D appendix B. It also contains layered
products.
After using dmu to configure the area, and to add a client, the client
fails to boot, giving the message Load of /etc/init failed. Here are the
particulars:
The dms area is exported from the server as
/var/adm/dms/dms0.alpha/root/usr -r=0 -ro
and the individual client area is exported as
/clients/alfco1.harvard.edu -r=0 alfco1.harvard.edu
The clients' fstab is
neptune:/var/adm/dms/dms0.alpha/root/usr /usr nfs ro 1 2
/proc /proc procfs rw 0 0
/dev/rz3b swap1 ufs sw 0 2
When I boot from the ethernet device on the client, it starts out as
below... It says 3.2C even though I followed the instructions on
rebuilding the GENERIC vmunix kernel after adding DU 3.2D-1 to the
dms area.
Alpha boot available memory from 0xbb0000 to 0x4000000
Digital Unix 3.2C (Rev 148) Tue Jul 25 00:24:14 EDT 1995
physicial memory 64 MB
available memory
(etc, etc... )
It finds the ethernet interface and disks all right. And gets as far as
lvm0: configured
lvm1: configured
lvm2: configured
Booted from Network Interface (BOOTP 0 5 0 0 2 CORE-IO)
Warning: clock gained 117 days
vm_swap_init: warning: /sbin/swapdefault device not found
vm_swap_init: in swap over commitment mode
Load of /etc/init failed, errno 2
init program?
Does anyone have any ideas on what's wrong here, either on the question of
why it can't find init, or on why it says it's booting 3.2C instead of
3.2D?
One more question:
Our subnet mask is 255.255.248.0, and broadcast address is 131.142.15.255.
When I add a client using dmu, it only asks for the subnet mask, so the
broadcast doesn't get set at that time.
Is it perhaps the case that the kernel gets loaded by bootp, and that the
broadcast address is not a factor at that point, and then the system fails
to NFS mount / since the broadcast address does matter for NFS? If so,
is there a way to set the broadcast address before / gets mounted?
Best regards,
-Patrick O'Brien
Received on Wed May 29 1996 - 17:58:01 NZST