From: Theodore Ts'o <tytso@mit.edu>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
Eugene Krasnikov <k.eugene.e@gmail.com>,
Kalle Valo <kvalo@adurom.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath9k_htc_fw <ath9k_htc_fw@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Version number policy!
Date: Mon, 8 Apr 2013 20:37:20 -0400 [thread overview]
Message-ID: <20130409003720.GA5145@thunk.org> (raw)
In-Reply-To: <CAJ-VmomksDSNvTpKQpNRRQx+QboSVHpby7V4qq4rngqVkTvf+A@mail.gmail.com>
On Mon, Apr 08, 2013 at 04:12:07PM -0700, Adrian Chadd wrote:
> I'm a FreeBSD user. I know what it's like to have an alternate, out of
> linux implementation of ext2/3 that doesn't implement all of the
> features.
>
> I also know what kinds of crap happens when you try mounting a more
> recent extX filesystem on an earlier kernel. Ie, it doesn't
> necessarily end well. :-)
There shouldn't be any crap; just a an error message indicating that
"the file system has features which this implementation doesn't
understand". At least, if the implementation was competently
coded.... (ext2/3/4 has feature bitmasks that make it very clear what
features are required so that an implementation can mount the file
system read/write or read/only).
- Ted
next prev parent reply other threads:[~2013-04-09 0:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ-Vmo=LVSzdEo6DhfOVT_0JHCTMmdPU1zGfMuBmhmr8QuDmJQ@mail.gmail.com>
2013-04-05 8:19 ` Version number policy! Luis R. Rodriguez
2013-04-05 8:21 ` Adrian Chadd
2013-04-05 16:42 ` Eugene Krasnikov
2013-04-05 17:03 ` Christian Lamparter
2013-04-05 17:23 ` Eugene Krasnikov
2013-04-05 18:08 ` Christian Lamparter
2013-04-05 19:16 ` Adrian Chadd
2013-04-06 5:52 ` Kalle Valo
2013-04-06 7:08 ` Adrian Chadd
2013-04-08 9:10 ` Eugene Krasnikov
2013-04-08 15:33 ` Christian Lamparter
2013-04-08 19:00 ` Adrian Chadd
2013-04-08 20:37 ` Eugene Krasnikov
2013-04-08 22:03 ` Christian Lamparter
2013-04-08 23:12 ` Adrian Chadd
2013-04-09 0:37 ` Theodore Ts'o [this message]
2013-04-09 1:51 ` Adrian Chadd
2013-04-09 11:28 ` Theodore Ts'o
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=20130409003720.GA5145@thunk.org \
--to=tytso@mit.edu \
--cc=adrian@freebsd.org \
--cc=ath9k_htc_fw@lists.infradead.org \
--cc=chunkeey@googlemail.com \
--cc=k.eugene.e@gmail.com \
--cc=kvalo@adurom.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.