From: Jan Kara <jack@suse.cz>
To: Erik van der Kouwe <vdkouwe@cs.vu.nl>
Cc: Jan Kara <jack@suse.cz>, Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Fam Zheng <famcool@gmail.com>
Subject: Re: [PATCH] fs/minix: bugfix, number of indirect block ptrs per block depends on block size
Date: Thu, 27 May 2010 19:17:05 +0200 [thread overview]
Message-ID: <20100527171705.GC3576@quack.suse.cz> (raw)
In-Reply-To: <4BFEA7CD.6020703@cs.vu.nl>
On Thu 27-05-10 19:11:41, Erik van der Kouwe wrote:
> Dear all,
>
> > Out of curiosity: Are you really using MINIX? The code is dead for a
> >long time...
>
> MINIX is very much alive, see http://www.minix3.org/.
>
> I work in the team developing MINIX. Being able to exchange data
> between Linux and MINIX is very useful for us and there is no other
> filesystem that the two share. We have been aware of (and annoyed
> by) this problem for a long time, but didn't know the cause (and
> didn't have much time to check). Feiran is a GSoC student working on
> our project and he found the issue when setting up his development
> environment so then we decided to bring out a patch.
OK, I was more speaking about the Linux MINIX filesystem driver but it's
good to know someone is still using it :) Thanks for education.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-05-27 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 10:03 [PATCH] fs/minix: bugfix, number of indirect block ptrs per block depends on block size Erik van der Kouwe
2010-05-26 21:54 ` Jan Kara
2010-05-27 16:01 ` Al Viro
2010-05-27 17:11 ` Erik van der Kouwe
2010-05-27 17:17 ` Jan Kara [this message]
2010-05-27 4:35 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100527171705.GC3576@quack.suse.cz \
--to=jack@suse.cz \
--cc=famcool@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vdkouwe@cs.vu.nl \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).