Re: Tux3 Report: Initial fsck has landed

2013-03-21 Thread Rob Landley
On 03/19/2013 06:00:32 PM, Martin Steigerwald wrote: Am Dienstag, 29. Januar 2013 schrieb Daniel Phillips: On Mon, Jan 28, 2013 at 5:40 PM, Theodore Ts'o ty...@mit.edu wrote: On Mon, Jan 28, 2013 at 04:20:11PM -0800, Darrick J. Wong wrote: On Mon, Jan 28, 2013 at 03:27:38PM -0800, David

Re: Tux3 Report: Initial fsck has landed

2013-03-20 Thread Daniel Phillips
On Tue, Mar 19, 2013 at 11:54 PM, Rob Landley r...@landley.net wrote: I'm confused, http://tux3.org/ lists a bunch of dates from 5 years ago, then nothing. Is this project dead or not? Not. We haven't done much about updating tux3.org lately, however you will find plenty of activity here:

Re: Tux3 Report: Initial fsck has landed

2013-03-19 Thread David Lang
On Wed, 20 Mar 2013, Martin Steigerwald wrote: Am Dienstag, 29. Januar 2013 schrieb Daniel Phillips: On Mon, Jan 28, 2013 at 5:40 PM, Theodore Ts'o ty...@mit.edu wrote: On Mon, Jan 28, 2013 at 04:20:11PM -0800, Darrick J. Wong wrote: On Mon, Jan 28, 2013 at 03:27:38PM -0800, David Lang

Re: Tux3 Report: Initial fsck has landed

2013-03-19 Thread Daniel Phillips
On Tue, Mar 19, 2013 at 9:04 PM, David Lang da...@lang.hm wrote: On Wed, 20 Mar 2013, Martin Steigerwald wrote: Am Dienstag, 29. Januar 2013 schrieb Daniel Phillips: On Mon, Jan 28, 2013 at 5:40 PM, Theodore Ts'o ty...@mit.edu wrote: On Mon, Jan 28, 2013 at 04:20:11PM -0800, Darrick J. Wong

Re: Tux3 Report: Initial fsck has landed

2013-01-28 Thread Theodore Ts'o
On Sun, Jan 27, 2013 at 10:13:37PM -0800, Daniel Phillips wrote: The thing that jumps out at me with this is the question of how you will avoid the 'filesystem image in a file' disaster that reiserfs had (where it's fsck could mix up metadata chunks from the main filesystem with metadata

Re: Tux3 Report: Initial fsck has landed

2013-01-28 Thread Darrick J. Wong
On Mon, Jan 28, 2013 at 03:27:38PM -0800, David Lang wrote: On Mon, 28 Jan 2013, Theodore Ts'o wrote: On Sun, Jan 27, 2013 at 10:13:37PM -0800, Daniel Phillips wrote: The thing that jumps out at me with this is the question of how you will avoid the 'filesystem image in a file' disaster that