I've got a really weird question:

I have Windows system A, with a share named "files".

I have a Linux server B, mounting the share in /opt/files

I want my other Linux computers C through F to mount /opt on B and have access to the files directory.

The SMB mount works fine on B. All files are accessable.

I can NFS mount the B:/opt directory just fine from C-F, but the /opt/files directory is empty.

Somehow NFS is not letting the SMB share pass through.

Any ideas?

Thanks,
Mutiny

Why not map the /opt directory on the windows box, thereby removing the need for local storage and reducing the links by one? That way both the windows machine and the other machines c-f could all mount the /opt directory on the server.

Unfortunately, I'm not allowed to do that in this situation.

Also, the Windows machine will change quite often, along with the content of the shared directory.

The original plan was to make only one of the Linux systems have to change it's mount and look for the new Windows share. The Linux terminals would have a constant mount point.

It makes sense when you figure in the fact that eventually there will be MANY terminals.

After much research, a fellow on the HardOCP OS forum pointed out that kernel NFS does not allow this action. I would need the older user space NFS.

The solution I came up with is that since this is an OpenMosix cluster, I can use MFS to mount the shared folder and get a speed increase over NFS. I made a symlink through /mfs to the server. (/mfs/1/opt/files --> /opt/files)

Being a cluster this is the solution I should have used in the first place.

Thanks for the suggestions,
Mutiny