First, slamd64 is
not Slackware.
Quote:
Originally Posted by mokele
On client; before `setup' I setup nfs manually first
1- `network' command to load eth card
2- ifconfig eht0 192.168.1.15 up
3- /sbin/rpc.portmap
4- mkdir /slamd
5- mount -t nfs 192.168.1.10:/home/share /slamd -o rw,nolock
When I cd to /slamd I can see the installation files and
I can even browse the share.
|
I don't know about the slamd64 installer, but it should function alike the Slackware installer. In Slackware there is a menu after you select "NFS install" where you enter your IP address, that of the NFS server and the exported NFS filesystem, after which Slackware installer will try to mount the NFS export to the correct directory. No manual configuration outside of the installer is required apart from running the command "network".
Also, the directory on the NFS export which you feed to the installer, must show the package set directories, i.e. a,ap,d,e,f....,y. If this is not done (for instance you enter the Slackware root directory below which you find the "slackware" directory) your install will fail similar to what you experience.
Eric