From owner-freebsd-stable Tue Aug 29 2:45:11 2000 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 D669D37B43C for ; Tue, 29 Aug 2000 02:45:04 -0700 (PDT) Received: from castle2.jp.FreeBSD.org (castle2.jp.FreeBSD.org [210.226.20.120]) by updraft.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id SAA40807 for ; Tue, 29 Aug 2000 18:45:03 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by castle2.jp.FreeBSD.org (8.11.0+3.3W/8.11.0) with ESMTP/inet id e7T9j2X82680 for ; Tue, 29 Aug 2000 18:45:03 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) 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.2 (Molpe) 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: 17 From: Makoto MATSUSHITA To: stable@freebsd.org Subject: Three versions of ERRATA.TXT for 4.1-RELEASE Date: Tue, 29 Aug 2000 18:44:58 +0900 Message-Id: <20000829184458V.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a revision 1.2.2.1 of src/release/ERRATA.TXT. It says that there is a bug in boot0. It is commited at Aug/18/2000 (10+ days before). However, we have already have ERRATA.TXT which is available at . It says that fetch(1) will fail in some cases. Moreover, we have also have yet another ERRATA.TXT which is available at . It says nothing about 4.1-RELEASE update information. Hmm, much confusing. What's the truth? fetch(1) is broken only in i386 architecuture? How about boot0? Are there any errata of ERRATA.TXT? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message