Date: Sat, 8 Jan 2005 21:58:27 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: Hack to sysctl kern.osreldate, for ports cluster Message-ID: <20050109055827.GA38416@xor.obsecurity.org> In-Reply-To: <200501090653.37252.michaelnottebrock@gmx.net> References: <20050108071324.GA32371@crodrigues.org> <200501090653.37252.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 09, 2005 at 06:53:33AM +0100, Michael Nottebrock wrote: > On Saturday, 8. January 2005 08:13, Craig Rodrigues wrote: > > Hi, > > > > > > On http://pointyhat.freebsd.org/errorlogs/ it states > > that sysctl should not be used to determine the > > version of FreeBSD, and that uname(1) or the OSVERSION > > variable should be used instead. > > > > While a valid thing to do, this is another detail > > for port maintainers to keep track of. >=20 > How exactly is using sysctl directly less of a 'detail to keep track of' = than=20 > using the OSVERSION variable provided by bsd.port.mk? I frankly don't see= any=20 > benefit in being able to call sysctl kern.osreldate from port Makefiles. Well, some third party software already does, and it can be a bit of work for me to explain to port maintainers why their port is broken on pointyhat. Kris --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB4MgCWry0BWjoQKURAi9TAKCC97DLllZ80E5r8Op7XnrUBZucHQCgzFwR jPdNmCKxJKPGpvUN1swCrzs= =w1rD -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050109055827.GA38416>