From mint-bounce@lists.fishpool.fi Mon May 10 16:54:22 2010 Message-ID: <4BE87209.5080004@abbuc.de> Date: Mon, 10 May 2010 22:52:25 +0200 From: Stefan Niestegge User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] double-click crash References: <00087f93.0180b2621d37@smtp.freeola.net> In-Reply-To: <00087f93.0180b2621d37@smtp.freeola.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: beetle@abbuc.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Am 10.05.2010 20:16, schrieb Peter Slegg: > On Mon, 10 May 2010 21:58:57 , "Helmut Karlowski" wrote: > >> Am 10.05.2010, 16:31 Uhr, schrieb Peter Slegg: >> >> >>> Has anyone ever looked at ext3 ? >>> >> Is it good? >> >> > AFAIK it keeps a journal and so if there is a crash and the system > has to reboot it doesn't have to check the filesystem. Otherwise > it is the same as ext2. > > http://en.wikipedia.org/wiki/Ext3 > > I think Ubuntu uses ext3 or possibly ext4 by now > > Peter > > Exactly, and with help of that journal, filesystem errors (that in fact occur with ext3 as well) can be more safe recovered. I just happen to exprience a FS check. Some stuff was bound to lost&found during that, now my MiNT moans about some folders in /etv/var and similar not found. I will have to reinstall. Ext3 most probably would have saved me from that. So, if someone thinks, ext3 could be possible to port for our MiNT system, i vote for it. Greetings, Stefan