From owner-mint@fishpool.com  Mon Jun 30 22:21:39 2003
Message-ID: <3F009A8D.90404@ish.de>
Date: Mon, 30 Jun 2003 22:16:13 +0200
From: helmut karlowski <helmut.karlowski@ish.de>
User-Agent: Mozilla/5.0 (Windows; U; Win98; de-DE; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: de-de, de
MIME-Version: 1.0
To: mint list <mint@fishpool.com>
Subject: Re: [MiNT] e2fsck problem (fwd)
References: <Pine.MNT.4.31.0306262119470.129-100000@UNI_MANiac> <Pine.NEB.4.53.0306262328420.425@wh58-508.st.uni-magdeburg.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Delivered-To: mint@fishpool.com
Delivered-To: mint@lists.fishpool.fi
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: helmut.karlowski@ish.de
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-ID: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>

 > Thomas is right except that it's not the e2fsck that avoid the drive
 > locking. It's rather the init and/or syslogd or one of the started
 > daemons with open files.

It could also be the shell from which efsck was called (from a script),
I use `exec fsck.ext2´ on that partition.

-Helmut