kern.ostype - where gets its value?

[Daniel Braniss]

> On 26 Feb 2017, at 15:06, Milan Obuch <freebsd-hackers at dino.sk> wrote:
> 
> On Sun, 26 Feb 2017 12:47:42 +0000
> Daniel Shahaf <danielsh at 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.


> 
>>> 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
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"