From owner-freebsd-hackers Sat Oct 21 09:49:44 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA07137 for hackers-outgoing; Sat, 21 Oct 1995 09:49:44 -0700 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA07131 for ; Sat, 21 Oct 1995 09:49:41 -0700 Received: by sovcom.kiae.su id AA26673 (5.65.kiae-1 ); Sat, 21 Oct 1995 19:44:38 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sat, 21 Oct 95 19:44:38 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id TAA00712; Sat, 21 Oct 1995 19:43:28 +0300 To: Warner Losh , "Jordan K. Hubbard" Cc: hackers@freefall.freebsd.org, "Kaleb S. KEITHLEY" References: <22805.814265148@time.cdrom.com> In-Reply-To: <22805.814265148@time.cdrom.com>; from "Jordan K. Hubbard" at Sat, 21 Oct 1995 01:45:48 -0700 Message-Id: Organization: Olahm Ha-Yetzirah Date: Sat, 21 Oct 1995 19:43:28 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: xterm dumps core Lines: 38 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1838 Sender: owner-hackers@FreeBSD.org Precedence: bulk In message <22805.814265148@time.cdrom.com> Jordan K. Hubbard writes: >> Every other FreeBSD upgrade has just worked. 1.0 -> 1.1 -> 1.1.5 -> >> 2.0 -> 2.0.5. (well, modulo the flock problems that were acknowledged >> as a bug). It is my expectation as a user that the 2.0.5 -> 2.1 >> release will go the same way. >Sorry, I came into this late. >Actually, Andrey, a 2.0.5 -> 2.1 upgrade is featured as part of the >2.1 installation and it does indeed assume that backwards >compatibility will be maintained. I have always treated 2.0.5 as a >full release and I don't know where you get the idea that it can >somehow fall outside the "prior release" criteria. Warner is >perfectly correct: 2.0.5 was a full release. Period. Sigh... I plan to make locale aliasing (the same as X locale.alias does) in more comfortable 2.2 schedule... 2.0.5 8859-1 ctype is wrong in several places (fixed now in -current but I don't see this fix passed to 2.1 as I ask!), I doubt that anybody even could use 2.0.5 8859-1 locale efficiently, as its developer I can say that it was added per experimental basis, so I don't expect backward capability to it will even been demanded. Moreover, all 8859-1 links in share/locale are invalid, because fr_FR/LC_TIME != de_DE/LC_TIME f.e. Now I change my mind a bit because parsing locale.alias takes a lot time comparing to filesystem links following, parsing degradates program startup speed. Jordan, expect current links removing and creating a lot more newest ones (they will solve backward capability too). -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849