From owner-freebsd-hackers@freebsd.org  Sun Feb 26 14:20:25 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 A1396CEED22
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Sun, 26 Feb 2017 14:20:25 +0000 (UTC)
 (envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 604101F2
 for <freebsd-hackers@freebsd.org>; Sun, 26 Feb 2017 14:20:24 +0000 (UTC)
 (envelope-from danny@cs.huji.ac.il)
Received: from sgi-2.cs.huji.ac.il ([132.65.80.20])
 by kabab.cs.huji.ac.il with esmtp
 id 1chzSH-000I5y-I2; Sun, 26 Feb 2017 16:05:41 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: kern.ostype - where gets its value?
From: Daniel Braniss <danny@cs.huji.ac.il>
In-Reply-To: <20170226140645.5d3ad3c1@zeta.dino.sk>
Date: Sun, 26 Feb 2017 16:05:41 +0200
Cc: Daniel Shahaf <danielsh@apache.org>,
 freebsd-hackers@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <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>
To: Milan Obuch <freebsd-hackers@dino.sk>
X-Mailer: Apple Mail (2.3259)
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 14:20:25 -0000


> On 26 Feb 2017, at 15:06, Milan Obuch <freebsd-hackers@dino.sk> wrote:
>=20
> On Sun, 26 Feb 2017 12:47:42 +0000
> Daniel Shahaf <danielsh@apache.org> wrote:
>=20
>> Milan Obuch wrote on Sun, Feb 26, 2017 at 13:25:48 +0100:
>>> =46rom 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. =20
>>=20
>> svn can work over nfs provided that locking is supported.
>>=20
>=20
> 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=3Dyes =
in rc.conf)
probably also rpc_statd too.


>=20
>>> 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... =20
>>=20
>> sys/conf/newvers.sh, grep for 'svnversion'.
>=20
> Thanks, I knew it is something like that, I found vers.c file just
> moment ago, it is probably output of this script...
>=20
> Regards,
> Milan
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to =
"freebsd-hackers-unsubscribe@freebsd.org"