Date: Fri, 01 Jul 2005 16:37:13 -0500 From: Jonathan Noack <noackjr@alumni.rice.edu> To: lars <lars@gmx.at> Cc: freebsd-stable@freebsd.org Subject: Re: How is the patchlevel set? Message-ID: <42C5B789.8090202@alumni.rice.edu> In-Reply-To: <42C570F2.8030504@gmx.at> References: <42C45A55.4020303@gmx.at> <6.1.0.6.2.20050630205112.159c9470@cobalt.antimatter.net> <42C570F2.8030504@gmx.at>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0390EB80C131B754DD5521D3
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 7/1/2005 11:36 AM, lars wrote:
> It seems
> src/sys/conf/newvers.sh
> is only triggered by a recompilation of the kernel,
> at least the lines
> i=`${MAKE:-make} -V KERN_IDENT`
> and
> char kern_ident[] = "${i}";
> make me believe that.
>
> I also try to cvsup my src and recompile the kernel and world
> in one go instead of only patching and recompiling the subsystem,
> since that bumps the patchlevel and keeps all synchronised.
> That's not possible in all scenarios, of course.
>
> Again thanks for the answers, but how did you find that out?
I originally suspected as much based on experience. I got curious and
noticed that newvers.sh was one of the files changed with every security
update. From there it was code inspection...
--
Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195
--------------enig0390EB80C131B754DD5521D3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFCxbeOUFz01pkdgZURAnuiAJ9uXMnL3bjkp137nuVUXMN4yYUINACdEhAi
g43VQDVDv8LaMslgZCUsOos=
=g9X3
-----END PGP SIGNATURE-----
--------------enig0390EB80C131B754DD5521D3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42C5B789.8090202>