From owner-freebsd-hackers Sun Aug 24 06:00:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA01188 for hackers-outgoing; Sun, 24 Aug 1997 06:00:57 -0700 (PDT) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA01183 for ; Sun, 24 Aug 1997 06:00:49 -0700 (PDT) Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.8.5/8.8.4) id PAA03982 for hackers@freebsd.org; Sun, 24 Aug 1997 15:00:50 +0200 (MESZ) From: Robert Eckardt Message-Id: <199708241300.PAA03982@ghost.mep.ruhr-uni-bochum.de> Subject: Re: amd + linux = permission denied (summary) To: hackers@freebsd.org Date: Sun, 24 Aug 1997 15:00:49 +0200 (MESZ) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just for the records I wanted to summarize how the problem resolved: The Linux server allows NFS accesses only from reserved ports. Amd used a reserved port for the mount operation (by chance ?), but not for the data transfers. (That's why the mount succeeds, but not the data transfers.) Joerg Wunsch pointed me to a new, undocumented option in amd that instructs it to use a reserved port (<1024). Adding opts=...,resvport,... to the mount-map solved it. It was J Wunsch who wrote: > revision 1.2 > date: 1995/02/13 01:56:22; author: wpaul; state: Exp; lines: +10 -1 > Added three line hack to nfs_ops.c to add support for the 'resvport' > mount option: you need this little bugger in environments with facsist > SunOS NFS servers (like mine :). -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de