Date: Thu, 16 Sep 2004 03:48:41 -0000 From: "Max Laier" <max@love2party.net> To: <pf4freebsd@freelists.org> Subject: [pf4freebsd] Re: 'Version' enhancement request Message-ID: <004001c36e48$591c6680$01000001@max900> References: <006101c36dde$01cb64e0$01000001@max900> <1062160039.3f4f46a77d2d3@mail.fluidhosting.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello,
good point! But we don't want to modify pfctl (or any of the sources) more
than needed to make it work, hence I added another way to get version
information:
1) The kernel modules will printf the following (watch your console or use
dmesg(8)):
pflog: $Name: VERSION_1_63 $
pfsync: $Name: VERSION_1_63 $
pfaltq: $Name: VERSION_1_63 $
pf: $Name: VERSION_1_63 $
2) All binary files can be identified useing RCS ident(1):
$ident /sbin/pfctl
/sbin/pfctl:
(...)
$Name: VERSION_1_63 $
I revised pf_freebsd_1.63.tar.gz new tarball has:
MD5 (pf_freebsd_1.63.tar.gz) = cad275628e25058b6416457417cf93a6
This might not be the cleanest possible way, but it works.
> Hi all,
>
> I've had several people in #pf asking about how to verify that they are in
fact
> on a specific version of pf_freebsd. Since we're basically installing
over the
> top of previous versions and clobbering everything, there's no clean (i.e.
using
> pfctl) way to verify the version.
>
> Would it be possible to add a -V flag to pfctl to show the current
version?
>
> In the meantime, any pointers on how to verify versions using unclean
methods
> would be appreciated, and will be added to the pf-r (I have some updating
to do
> myself, been on holiday)...
>
> -S
>
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004001c36e48$591c6680$01000001>