Date: Sun, 26 Feb 2017 16:05:41 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: Milan Obuch <freebsd-hackers@dino.sk> Cc: Daniel Shahaf <danielsh@apache.org>, freebsd-hackers@freebsd.org Subject: Re: kern.ostype - where gets its value? Message-ID: <BCF9D145-BFE2-42CF-A03F-8173F6FC742C@cs.huji.ac.il> In-Reply-To: <20170226140645.5d3ad3c1@zeta.dino.sk> References: <20170226132548.69223dcd@zeta.dino.sk> <20170226124742.GA10967@fujitsu.shahaf.local2> <20170226140645.5d3ad3c1@zeta.dino.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BCF9D145-BFE2-42CF-A03F-8173F6FC742C>