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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170226140645.5d3ad3c1>