Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Aug 2012 22:59:17 +0300
From:      Manolis Kiagias <sonic2000gr@gmail.com>
To:        freebsd-security@freebsd.org
Subject:   Re: getting the running patch level
Message-ID:  <50295C95.7020301@gmail.com>
In-Reply-To: <86vcgm7fsw.fsf@ds4.des.no>
References:  <0B65D7562F9DA04FAC3F15C508BF67136B90E09E1F@ESESSCMS0355.eemea.ericsson.se> <001701cd7648$c2520350$46f609f0$@com> <5024f984.45ca320a.1838.4155SMTPIN_ADDED@mx.google.com> <CAC8HS2FU1hrbh_m4P6h%2BSpUAJREfCeynHPD3QnNx6XuzSb3T-g@mail.gmail.com> <86pq6xs0zb.fsf@ds4.des.no> <20120812163448.GA88577@DataIX.net> <86vcgm7fsw.fsf@ds4.des.no>

next in thread | previous in thread | raw e-mail | index | archive | help
On 13/08/2012 22:27, Dag-Erling Smørgrav wrote:
> Jason Hellenthal<jhellenthal@dataix.net>  writes:
>> Could I suggest... the same way that /etc/motd is already updated ?
> You could, but it wouldn't be very helpful, since /etc/rc.d/motd uses
> uname(1), which returns the kernel version.  On the contrary, once
> /etc/issue is in place, we should use that instead of uname(1) to update
> /etc/motd.
>
> DES

One could also set the environment variable UNAME_r to the correct value 
(either in system wide e.g. /etc/profile or to a specific user dot 
files). Only problem of course it would have to be updated to the 
correct value manually.
Or, since the correct value is always in newvers.sh, if src is present 
in the system a periodic script could update it automatically.
The manual updating  will cause more confusion in the long run - people 
tend to forget these things...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50295C95.7020301>