Date: Sat, 11 Aug 2012 00:48:31 +0700 From: Janne Snabb <snabb@epipe.com> To: freebsd-security@freebsd.org Subject: Re: getting the running patch level Message-ID: <5025496F.5020807@epipe.com> In-Reply-To: <FCF3F936-CC1F-43BB-90A4-7F4A008E18BA@behanna.org> 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> <FCF3F936-CC1F-43BB-90A4-7F4A008E18BA@behanna.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/10/2012 11:55 PM, Chris BeHanna wrote: > Split off a version.ko and update that with each patch? There is often no need to reboot the machine unless the kernel is affected (just restart the affected daemons). Thus the information would not necessarily match the userland status. The userland and kernel versions need to be kept separate because they may not match. I am often struggling to remember if I updated some machine already or not. I now need to compare the time stamps of newvers.sh and installed binaries to find out. IMHO a sensible approach would be something like what most Linux distros do: Have some file in a standard location and put the information there by generating that file from newvers.sh during make buildworld / installworld". Having it only in the source tree is not sufficient as not every machine has the source tree installed. On LSB compliant Linux distributions the proper way to find this out is the lsb_release command. On many Linux distributions there is also a /etc/DISTRONAME-release file which can be checked (for example /etc/debian-release on Debian and /etc/redhat-release on RHEL and clones). How about /etc/freebsd-release? Or freebsd_release command (shell script) which takes the same flags as lsb_release? -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5025496F.5020807>