From owner-freebsd-hackers@freebsd.org  Mon Feb 27 12:01:43 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6891CEE939
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Mon, 27 Feb 2017 12:01:43 +0000 (UTC)
 (envelope-from freebsd-hackers@dino.sk)
Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3982C27B
 for <freebsd-hackers@freebsd.org>; Mon, 27 Feb 2017 12:01:42 +0000 (UTC)
 (envelope-from freebsd-hackers@dino.sk)
Received: from zeta.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan)
 by mailhost.netlabit.sk with ESMTPA; Mon, 27 Feb 2017 13:01:38 +0100
 id 00F4BED1.58B41522.0000A3FF
Date: Mon, 27 Feb 2017 13:01:38 +0100
From: Milan Obuch <freebsd-hackers@dino.sk>
To: Daniel Braniss <danny@cs.huji.ac.il>
Cc: Daniel Shahaf <danielsh@apache.org>, freebsd-hackers@freebsd.org
Subject: Re: kern.ostype - where gets its value?
Message-ID: <20170227130138.778b6571@zeta.dino.sk>
In-Reply-To: <BCF9D145-BFE2-42CF-A03F-8173F6FC742C@cs.huji.ac.il>
References: <20170226132548.69223dcd@zeta.dino.sk>
 <20170226124742.GA10967@fujitsu.shahaf.local2>
 <20170226140645.5d3ad3c1@zeta.dino.sk>
 <BCF9D145-BFE2-42CF-A03F-8173F6FC742C@cs.huji.ac.il>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; i386-portbld-freebsd10.3)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 12:01:43 -0000

On Sun, 26 Feb 2017 16:05:41 +0200
Daniel Braniss <danny@cs.huji.ac.il> wrote:

> > On 26 Feb 2017, at 15:06, Milan Obuch <freebsd-hackers@dino.sk>
> > wrote:
> > 
> > On Sun, 26 Feb 2017 12:47:42 +0000
> > Daniel Shahaf <danielsh@apache.org> wrote:
> >   
> >> Milan Obuch wrote on Sun, Feb 26, 2017 at 13:25:48 +0100:  
> >>> From my experience it looks like this problem is caused by svn not
> >>> being able to be run on nfs mounted directory, no matter the
> >>> architecture - today I tried with both server and client running
> >>> 10.3-STABLE on i386, svn just fails.    
> >> 
> >> svn can work over nfs provided that locking is supported.
> >>   
> > 
> > How could I find whether locking is supported/make sure it is?  
> you need to run rpc_lockd on both server & client
> (rpc_lockd_enable=yes in rc.conf) probably also rpc_statd too.
> 

Thanks, I took another solution - mount /usr/src read only with option
nolockd. I verified 'svnliteversion /usr/src' command gives correct
results on both arm and arm64 (I tested it on my Mac NFS with i386 and
amd64 as well, this was another trouble solvable the same way for me).

So next kernel should have correct svn revision now...

Regards,
Milan