For lack of a better category, I have posted this here:
I have OPENSTEP for Mach 4.2 (no patches yet applied) installed on VMware Workstation 6.0 for Linux. I have gotten everything working, except for the /Net directory. For some weird reason, OPENSTEP will not create /Net upon startup, and I am unable to mount my NFSv2 share from my host Linux box (I later removed that from NFSManager; no dice). TCP/IP and Internet access work fine, but no matter what, it won't create /Net (although it did create it once, when I tried the change before that again, which was changing the domain name in resolv.conf to a real registered one, it didn't work). If anybody can help me with this, please do.
Thanks,
Eric
P.S. The last time I used OS 4.2 on VMware, nothing of this sort happened. However, that install is borked, so I cannot fetch the files from there since nothing can read NS/OS disks.
EDIT: What I am referring to in regard to NFS is that OPENSTEP will not automatically mount the host's export on boot in /Net/(hostip)/srv/nfs/files. However, I can mount it as root after boot.
Quote from: "ericj"For lack of a better category, I have posted this here:
I have OPENSTEP for Mach 4.2 (no patches yet applied) installed on VMware Workstation 6.0 for Linux. I have gotten everything working, except for the /Net directory. For some weird reason, OPENSTEP will not create /Net upon startup, and I am unable to mount my NFSv2 share from my host Linux box (I later removed that from NFSManager; no dice). TCP/IP and Internet access work fine, but no matter what, it won't create /Net (although it did create it once, when I tried the change before that again, which was changing the domain name in resolv.conf to a real registered one, it didn't work). If anybody can help me with this, please do.
Thanks,
Eric
P.S. The last time I used OS 4.2 on VMware, nothing of this sort happened. However, that install is borked, so I cannot fetch the files from there since nothing can read NS/OS disks.
EDIT: What I am referring to in regard to NFS is that OPENSTEP will not automatically mount the host's export on boot in /Net/(hostip)/srv/nfs/files. However, I can mount it as root after boot.
OK, I have gotten /Net to be created on boot (just shut down and started up the VM, then it worked), and the NFS export is mounted on boot, however, I cannot go inside the /Net/192.168.2.5 folder. In the Terminal, it says that the folder's name is 192.168.2.5@ and when I try to change to 192.168.2.5@ via the command line, it says that the directory doesn't exist. Same thing if I try to change to 192.168.2.5 in the Terminal. If I double-click on it in the Workspace Manager, it shows the opening animation with the zoom, but nothing else happens. This is really starting to irritate me, as I am trying to figure out how to share files before I get my slab.
Eric
Quote from: "ericj"
OK, I have gotten /Net to be created on boot (just shut down and started up the VM, then it worked), and the NFS export is mounted on boot, however, I cannot go inside the /Net/192.168.2.5 folder. In the Terminal, it says that the folder's name is 192.168.2.5@ and when I try to change to 192.168.2.5@ via the command line, it says that the directory doesn't exist. Same thing if I try to change to 192.168.2.5 in the Terminal. If I double-click on it in the Workspace Manager, it shows the opening animation with the zoom, but nothing else happens. This is really starting to irritate me, as I am trying to figure out how to share files before I get my slab.
Eric
OK, I have read-write access to the NFS export if I mount after login, but I still have the same problem. Also, if I try to mount using the hostname of the Linux box, OPENSTEP just makes a symlink to its own root directory. I used NFSManager to make the mount entry in NetInfo, if that's any help.
Eric
P.S. Why hasn't anybody responded? I was originally thinking of putting this in NEXTSTEP/OPENSTEP Software, but felt that that has more of an emphasis on third-party software than the OS itself, so AFAIK, there is no more suitable forum for this.
Lack of reply's is probably the niche you are playing with VMware, OpenStep 4.2, NFS issues :). Considering how few of us are playing with the stuff it is no surprise you are off the beaten track. But keep hammering away :D
-Mike
PS - I just did a quick a dirty try at it also [NFS on Fedora 8, /etc/exports created, Openstep 4.2 with patches running under Qemu tried to add via NFSmanager. No luck, could it be that NFS4 is the version that is on the server side?] Also check out /usr/adm/messages on the Openstep box and see if you get a netinfod error about directory permissions.
It's not a general problem with VMWare as in our company we are running our OpenStep server in a VMware WS 5.5 under SuSE linux. And there the "/Net" directory is working.
When I find the time I'll try nfs automounting to "/Net" on my own machine here at home with the same setup. Right now it has only mountings to static directories as all software and data directories beside the basic system are mounted from the linux system to the appropriate places.
I got it to work. Apparently, I had to create a NetInfo entry for the Linux box with HostManager. Afterwards, I can read and write perfectly with automounting on boot.
Eric
Quote from: "ericj"I got it to work. Apparently, I had to create a NetInfo entry for the Linux box with HostManager. Afterwards, I can read and write perfectly with automounting on boot.
Eric
That makes sense, good work!
-Mike
Quote from: "ericj"
I got it to work. Apparently, I had to create a NetInfo entry for the Linux box with HostManager. Afterwards, I can read and write perfectly with automounting on boot.
Eric
Yes, just tested it on my own machine. You need a netinfo entry in "/machines" for your linux box as the automounter will only work with hostnames, not with IP adresses :-)
When mounting directories from your linux box which contain NeXT applications you have to watch out that the "dir_index" option for the ext filesystem you exported from linux is turned off (SuSE enabled it by default for ext3 systems). If this ext3 option is turned on it's likely that you will run into troubles launching the apps as the whole next system relies on the fact that the first two entries in each dir are "." and ".." which is no longer true with "dir_index" turned on (took me several days of fiddling around, reinstalling the VM and wtahcing nfs network traffic until I found that one).
Morgon