From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1N3fFj-00013g-F5 for garchives@archives.gentoo.org; Fri, 30 Oct 2009 00:22:05 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BE63AE0B0D; Fri, 30 Oct 2009 00:22:01 +0000 (UTC) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by pigeon.gentoo.org (Postfix) with ESMTP id A0A17E0B0D for ; Fri, 30 Oct 2009 00:22:01 +0000 (UTC) Received: from compute1.internal (compute1.internal [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 74015BDA6E for ; Thu, 29 Oct 2009 20:22:01 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 29 Oct 2009 20:22:01 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:content-transfer-encoding; s=smtpout; bh=kpJVbFMR8pppZ4wzrPwaZMrmk48=; b=My29fJeWAuzfhfwF6t83HGvbMm/bwLi1MpBpPGLy5EllkaeULUWrDiLBY9sr47CM9zVbeKBS5tSX4dhoOAEGwcQMBUc+p2ZfxHW+F/zLTO4Pi0NDK0IhMVHyzkf2NKBLgp8Tr3z1rdb/06YUlW8woWy9JbySbYgG5ekSTHgZSoM= X-Sasl-enc: yzzzh6Zh+sU4xIMzJa8A7emBnPGAXN6Y5wfpHjd0EFb0 1256862121 Received: from [192.168.31.12] (cpe-069-134-183-088.nc.res.rr.com [69.134.183.88]) by www.fastmail.fm (Postfix) with ESMTPSA id 0A9F349C97D for ; Thu, 29 Oct 2009 20:22:00 -0400 (EDT) Subject: Re: [gentoo-user] Re: memory(gray matter) needs jog From: Albert Hopkins To: gentoo-user@lists.gentoo.org In-Reply-To: References: <1256856363.135440.6.camel@centar> Content-Type: text/plain; charset="UTF-8" Date: Thu, 29 Oct 2009 20:21:58 -0400 Message-ID: <1256862118.135440.15.camel@centar> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 51983244-50f0-4f4a-ac69-f22fd32a06ec X-Archives-Hash: a3200e7e6b45262a6930039ed281c72a On Thu, 2009-10-29 at 17:05 -0700, walt wrote: > > I'm not sure why your system needed to be checked for each boot... > > Boy, my 'little gray cells' need a tonic, too. I've been using ext3 > (i.e.with journaling) for so long I can't even remember using ext2. > > Wasn't it normal in the old days to fsck an ext2 fs with every boot? > You should put your drink down. And maybe go for a walk :) No, I'm not aware of it *ever* being standard to fsck on every boot. Perhaps you were using a bad distribution? True, Linux does run fsck on every boot, but fsck exits immediately if it determines your filesystem was unmounted cleanly on the last shutdown. It's only if you force a fsck (e.g. with -f or /forcefsck) that it will run fsck on a clean filesystem. And remember, ext2 has *no* journal, so fsck was always very very slow. To run it every time on a reboot would have been so painful that I believe ext3 would have been invented in the early '90s instead of 2001 :)