From owner-freebsd-hackers@freebsd.org  Sun Feb 26 13:06:49 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 DE0A6CED786
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Sun, 26 Feb 2017 13:06:49 +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 616CDBB0
 for <freebsd-hackers@freebsd.org>; Sun, 26 Feb 2017 13:06:48 +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; Sun, 26 Feb 2017 14:06:46 +0100
 id 00F4BCCC.58B2D2E6.0001316A
Date: Sun, 26 Feb 2017 14:06:45 +0100
From: Milan Obuch <freebsd-hackers@dino.sk>
To: Daniel Shahaf <danielsh@apache.org>
Cc: freebsd-hackers@freebsd.org
Subject: Re: kern.ostype - where gets its value?
Message-ID: <20170226140645.5d3ad3c1@zeta.dino.sk>
In-Reply-To: <20170226124742.GA10967@fujitsu.shahaf.local2>
References: <20170226132548.69223dcd@zeta.dino.sk>
 <20170226124742.GA10967@fujitsu.shahaf.local2>
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: Sun, 26 Feb 2017 13:06:50 -0000

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?

> > So I think this is root cause for missing svn revision number,
> > buildkernel process somehow uses svn to fetch svn revision number,
> > fails, and then just omits it. If I undestand it right, this
> > information is put into /sys/kern/kern_mib.c file's kern.version
> > sysctl, maybe via some include or some generated .c file is used for
> > it. Could someone point me to the right direction how is this done?
> > I would like to find at least some workaround for that...  
> 
> sys/conf/newvers.sh, grep for 'svnversion'.

Thanks, I knew it is something like that, I found vers.c file just
moment ago, it is probably output of this script...

Regards,
Milan