[comp.sys.next] Is this a bug with exportfs?

flur@duke.gatech.edu (Peter W. Flur) (03/01/90)

I seem to have found an interesting quirk.  I have a SparcSTation/1
trying to mount a partition of my NeXT machine.  Both machines
are running off a nameserver, and hence really don't have any
entries in their hosts file (ni database on the next).  I figured
out by trial and error that the host that is mounting the NeXT 
partition can only mount if its host name is in the hosts file
and the ni database on the NeXT.  

Is this supposed to work this way?

Peter
  ----------------------------Peter Flur----------------------------
			  USMAIL: Box 32500
  Georgia Tech, School of Electrical Engineering, Atlanta, GA  30332
     USENET: ...!{allegra,hplabs,ihnp4,ulysses}!gatech!duke!flur
       INTERNET: flur@duke.gatech.edu, gt2500a@prism.gatech.edu
			PHONE: (404) 853-9355
				    

eps@toaster.SFSU.EDU (Eric P. Scott) (03/01/90)

In article <6537@hydra.gatech.EDU> flur@duke.gatech.edu (Peter W. Flur) writes:
|I seem to have found an interesting quirk.  I have a SparcSTation/1
|trying to mount a partition of my NeXT machine.  Both machines
|are running off a nameserver, and hence really don't have any
|entries in their hosts file (ni database on the next).  I figured
|out by trial and error that the host that is mounting the NeXT 
|partition can only mount if its host name is in the hosts file
|and the ni database on the NeXT.  
|
|Is this supposed to work this way?

Nope.  I've done exactly what you've described with DNS alone.
Are you using a fully-qualified domain name in /etc/exports?
(If not, try it.)

					-=EPS=-