From owner-freebsd-stable Thu Aug 2 19:41: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id E1CE237B503 for ; Thu, 2 Aug 2001 19:40:50 -0700 (PDT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.3+3.4W/8.11.3) with ESMTP/inet id f732ema02869 for ; Fri, 3 Aug 2001 11:40:48 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <01080300314100.00395@spatula.home> References: <01080300314100.00395@spatula.home> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.5 (alfalfa) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 29 From: Makoto MATSUSHITA To: stable@freebsd.org Subject: Re: RELENG_4_3 calls itself -RELEASE? Date: Fri, 03 Aug 2001 11:40:38 +0900 Message-Id: <20010803114038W.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG andrew> Might it be time to invent a new development branch name like FreeBSD andrew> 4.3-SECURITY or 4.3-PATCHED or something like that? I think changing a version string is not a good idea. 4.3-RELEASE is 4.3-RELEASE and nothing else. The version string available by uname(3) comes from kernel MIB, and have no relationship to userland. How kernel knows that a userland have security-fixed libcrypto? No, no way to do that. Yes, there are much requirements to know "how many patches are applied to a system," but we cannot use version string to accomplish this. The only solution is to create a "patch history" database or file, but it's too hard, since there are lots of ways to update 4.3 box (CVSup sources, apply a patch, install security package, etc). But it's simple that you (a system administrator) record a patch history to your memory or whatever. Note that there are some potential pitfalls if we change a version string from 4.3-RELEASE to 4.3-WHATEVER; some scripts may check a system version's string to know that system is "4.3-RELEASE" or not. Again, changing a version doesn't solve any problems except showing "this system is 4.3-RELEASE but some patch (can't know how many) are applied to somewhere (can't know that libcrypto was fixed or not)." -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message