On 2014-07-27 02:16, ignatius999 wrote:
>
> I forgot to add a bit of pertinent information. Here is “rcnfs status”:
>
That shows that the server is running. But why does it want to resolve
those addresses?
And you do not show errors or messages from the client side (mount -v
…, for instance)
Why do you export “/usr/local/”? It is a system directory, I hope you
are not replacing contents with something else. Or are you just using it
for testing nfs export?
I have no idea why it’s looking for those addresses. The problem is, while attempting to mount the NFS directories, it hangs. No output is given. And, yes, /usr/local is just for testing purposes. I changed it to /usr/nfs, and it still hangs.
On 2014-07-27 04:36, ignatius999 wrote:
>
> I have no idea why it’s looking for those addresses. The problem is,
> while attempting to mount the NFS directories, it hangs.
What is “it”? The client? The server?
I say again: try mount -v whatever on client and wait at least 15
minutes (I don’t remember if timeout is 3).
> No output is
> given. And, yes, /usr/local is just for testing purposes. I changed it
> to /usr/nfs, and it still hangs.
Did you use YaST > System > Services Manager to switch on nfs (the nfs client service)?
And please, while it is very good that you post computer text between CODE tags, why do you add stories like “Here is my /etc/exports”? Just post prompt, command, output and next prompt. Apart from the many advantages it has, in this case the pormpt will at leasts how us what you do on which system. Like:
On 2014-07-27 12:26, ignatius999 wrote:
>
> I’m sorry for not being more assertive. I’ll remember to be more
> assertive next time. But, yes, I did enable NFS in YaST.
But you see, it is not clear at all where you see that message:
Configuring ethernet card...
Configuring your gateway...
Running /sbin/rpc.portmap...
Mount NFS...
Mount: RPC: Timed out
You say that “trying to access the NFS share”, but… how exactly? What
commands are you using?
You see, to you all that may seem obvious, but you have to understand
that we are not sitting besides you looking at what you do, and we all
do things differently. So we have to fill the gaps with guesses, and
they may usually be wrong
Ok. Here’s the issue: i’m trying to install Slackware off of the boot disk, since I don’t have access to a (working) CD-ROM drive. I’m using the “setup” command, and am selecting an “NFS” install. It’s all pretty much automated. I’d install openSuSE if I had it came with a boot disk. Basically, it first asks for an IP address, then a netmask, then a gateway, and then, the IP address of the NFS server, and then finally, the path to the Slackware files.
Sorry for barging into the thread but something to think about in the future;
You could setup a PXE server and install openSUSE via that method ->
https://en.opensuse.org/SDB:PXE_boot_installation
Also another dumb suggestions from me; have you tried using NFS3 and not NFS4? ( /etc/sysconfig/nfs -> NFS4_SUPPORT=“no” ) - perhaps the Slackware installer is having issues with it (need to restart the nfs server afterwards).
On 2014-07-27 13:16, ignatius999 wrote:
>
> Ok. Here’s the issue: i’m trying to install Slackware off of the boot
> disk, since I don’t have access to a (working) CD-ROM drive. I’m using
> the “setup” command, and am selecting an “NFS” install. It’s all pretty
> much automated. I’d install openSuSE if I had it came with a boot disk.
> Basically, it first asks for an IP address, then a netmask, then a
> gateway, and then, the IP address of the NFS server, and then finally,
> the path to the Slackware files.
Ok, but… that is not very relevant - unless it is that slackware that does not connect, while openSUSE does.
What I typically do when creating an NFS server is to try both server and client on the same machine. Only after this works, I attempt to connect from a different machine.
