From owner-freebsd-hackers@freebsd.org Sun Feb 26 12:52:23 2017 Return-Path: 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 61E63CED303 for ; Sun, 26 Feb 2017 12:52:23 +0000 (UTC) (envelope-from danielsh@apache.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37885E8D for ; Sun, 26 Feb 2017 12:52:22 +0000 (UTC) (envelope-from danielsh@apache.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 60C5A20792; Sun, 26 Feb 2017 07:52:21 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 26 Feb 2017 07:52:21 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=jiRirI5r6hAHZ9 f/l4WxcqkwfGA=; b=CqQl5Bu2aaGQI2Ncq4xxz3ig6MzJxfv6w5WizdIlfNTaPh YoCxzUsNBn3Qepgg2QjxHCXdncAbeOsHmuVFRHbQF7XaYtj/pCrHWrU10evUbOks wqWqpe7evIHlrbHFY/30CAoFgsZD924VB2Q3o/FjVThKgOUHwYq1OQJ/iEZao= X-ME-Sender: X-Sasl-enc: dslLIDG/z0gvy0pz4SOGEvJG4F2Aw86DQh8PSgYy2xpz 1488113540 Received: from fujitsu.shahaf.local2 (bzq-109-65-57-127.red.bezeqint.net [109.65.57.127]) by mail.messagingengine.com (Postfix) with ESMTPA id E90257E2B2; Sun, 26 Feb 2017 07:52:20 -0500 (EST) Received: by fujitsu.shahaf.local2 (Postfix, from userid 1000) id 3vWPkk5z2Jz21X; Sun, 26 Feb 2017 12:47:42 +0000 (UTC) Date: Sun, 26 Feb 2017 12:47:42 +0000 From: Daniel Shahaf To: Milan Obuch Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ostype - where gets its value? Message-ID: <20170226124742.GA10967@fujitsu.shahaf.local2> References: <20170226132548.69223dcd@zeta.dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170226132548.69223dcd@zeta.dino.sk> User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailman-Approved-At: Sun, 26 Feb 2017 13:19:50 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2017 12:52:23 -0000 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. > 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'.