From owner-freebsd-current@FreeBSD.ORG Mon May 5 18:23:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03C7137B401 for ; Mon, 5 May 2003 18:23:23 -0700 (PDT) Received: from seed.net.tw (sn14.seed.net.tw [139.175.54.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35F1743F85 for ; Mon, 5 May 2003 18:23:20 -0700 (PDT) (envelope-from leafy@chihiro.leafy.idv.tw) Received: from [210.64.98.90] (port=49155 helo=chihiro.leafy.idv.tw) by seed.net.tw with esmtp (Seednet 4.14:2) id 19CrAt-000KRk-GL for freebsd-current@freebsd.org; Tue, 06 May 2003 09:23:19 +0800 Received: from chihiro.leafy.idv.tw (nobody@localhost [127.0.0.1]) by chihiro.leafy.idv.tw (8.12.9/8.12.9) with ESMTP id h461NHG5000637 for ; Tue, 6 May 2003 09:23:18 +0800 (CST) (envelope-from leafy@chihiro.leafy.idv.tw) Received: (from leafy@localhost) by chihiro.leafy.idv.tw (8.12.9/8.12.9/Submit) id h461NHeF000636 for freebsd-current@freebsd.org; Tue, 6 May 2003 09:23:17 +0800 (CST) Date: Tue, 6 May 2003 09:23:17 +0800 From: leafy To: freebsd-current@freebsd.org Message-ID: <20030506012317.GA610@chihiro.leafy.idv.tw> Mail-Followup-To: freebsd-current@freebsd.org References: <20030505.112625.16415226.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Disposition: inline In-Reply-To: <20030505.112625.16415226.imp@bsdimp.com> User-Agent: Mutt/1.5.4i Subject: Re: Precaution! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 01:23:23 -0000 On Mon, May 05, 2003 at 11:26:25AM -0600, M. Warner Losh wrote: > If you booted a kernel from approximately April 15th through May 3th, > there were a number of small, but critical, vm bugs. This can cause > file system corruption, and leave silent landmines for later. It is > recommended that if you did boot these kernels, you build a newer > kernel, come up in single user and force an fsck on all filesystems. > This is to prevent 'false' panics later that are a result of the > corruption that might be dormant in them now. > > Warner Is there a way to mimick rc.early in rcNG so that I can force a 'fsck -y' remotely? Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming