Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 5 Jul 1998 02:28:10 -0700 (PDT)
From:      "Jason K. Fritcher" <jkf@wolfnet.org>
To:        CyberPeasant <djv@bedford.net>
Cc:        questions@FreeBSD.ORG
Subject:   Re: mountd w/ -alldirs option
Message-ID:  <Pine.BSF.3.96.980705011310.1102A-100000@outreach.wolfnet.org>
In-Reply-To: <199807050641.CAA00526@lucy.bedford.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 5 Jul 1998, CyberPeasant wrote:
> Jason K. Fritcher wrote:
> > Hello. I am trying to export a directory tree to a diskless OpenBSD box from
> > a FreeBSD 2.2.6-stable box, and I am having difficulties with mountd. I need
> > to be able to export a swap file for OBSD, and after reading the man page
> > for mountd(8) and exports(5), and have added this line to my /etc/exports.
> > 
> > /usr/export/rowe -alldirs rowe.wolfnet.org
> > 
> > When I 'kill -HUP' mountd, it syslogs the following error messages.
> > 
> > Jul  4 17:05:49 outreach mountd[124]: Could not remount /usr/export/rowe: Invalid argument
> > Jul  4 17:05:49 outreach mountd[124]: Bad exports list line /usr/export/rowe -alldirs rowe
> > 
> > If I remove the -alldirs flag, mountd does not complain about the line. I've
> > searched through the mailing list for things to try, and there weren't any
> > answers.
> >   
> 	...
> 
> -alldirs only works on the mount point of a filesystem. so unless you
> have  "mount /dev/sdXXXX /usr/export/rowe" somewhere, you can't
> put a -alldirs on the export.  Or so I read the manpage.
> 
> from the -r option of mountd:
> 
>      -r      The -r option allows mount RPCs requests for regular files to be
>              served.  Although this seems to violate the mount protocol speci-
>              fication, some diskless workstations do mount requests for their
>              swapfiles and expect them to be regular files.  Since a regular
>              file cannot be specified in /etc/exports, the entire file system
>              in which the swapfiles resides will have to be exported with the
>              -alldirs flag.
> 
> Assuming that you have a "standard" setup, it seems that you will
> have to export /usr -alldirs rowe.wolfnet.org  If using the "one
> big, happy partition" model, it will be "/ -alldirs rowe.wolfnet.org"

That was it... I guess I was in too much of a rush to get rowe up, and I
didn't read the man page carefully.

> Moreover, you'll probably have to use -maproot=0 (maybe?) I sure
> hope that rowe is a trusted host. I sure hope nobody ever spoofs
> it:  *.wolfnet.org should be trusted, too.  (If you end up doing
> this -- not recommended -- then you may want to diddle the arp
> tables so that mapping rowe's IPA to its ethernet ID is hard-wired.
> This will cut down on spoofing. There's a way to do it, but I don't
> know it [man arp]) NFS on an untrusted LAN sucks anyway. Let's say
> that if you've got a reason to have different root passwords on
> any machine on the LAN, you've got a reason not to export anything
> -maproot=0.  

Rowe is a trusted host, it is sitting right next to me on my lan at home. I
really don't worry about someone getting to my network, since I am using a
firewall on my router, and have those ports blocked from the outside.

Thanx for the help.

--
 Jason K. Fritcher
  jkf@wolfnet.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980705011310.1102A-100000>