From: Dominik Kubla <dominik.kubla@uni-mainz.de>
To: "H. Peter Anvin" <hpa@transmeta.com>
Cc: Dominik Kubla <dominik.kubla@uni-mainz.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: ext3 vs. JFS file locations...
Date: Sun, 5 Nov 2000 13:39:28 +0100 [thread overview]
Message-ID: <20001105133928.A25131@uni-mainz.de> (raw)
In-Reply-To: <3A02D150.E7E87398@usa.net> <200011031725.eA3HPwP12932@webber.adilger.net> <8tv3tm$iqg$1@cesium.transmeta.com> <20001105024621.A29327@uni-mainz.de> <3A04CA8F.D19535B1@transmeta.com>
In-Reply-To: <3A04CA8F.D19535B1@transmeta.com>; from hpa@transmeta.com on Sat, Nov 04, 2000 at 06:48:47PM -0800
On Sat, Nov 04, 2000 at 06:48:47PM -0800, H. Peter Anvin wrote:
> Because -fs is usually used by filesystems itself. Since the journaling
> layer doesn't really have a publically visible name, it's easy to change.
Oh i understood that fine. But VFS = "virtual filesystem switch" is also
not a filesystem per se. And why give the generic term to an IBM "product"?
So i say leave jfs for generic code and call the IBM jfs "ibmjfs".
Just my 2 cents,
Dominik Kubla
--
http://petition.eurolinux.org/index_html - No Software Patents In Europe!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-05 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 14:53 ext3 vs. JFS file locations Michael Boman
2000-11-03 15:38 ` Alan Cox
2000-11-03 17:30 ` Andrea Arcangeli
2000-11-03 17:25 ` Andreas Dilger
2000-11-03 19:33 ` H. Peter Anvin
2000-11-05 1:46 ` Dominik Kubla
2000-11-05 2:48 ` H. Peter Anvin
2000-11-05 12:39 ` Dominik Kubla [this message]
2000-11-05 2:53 ` Albert D. Cahalan
2000-11-05 10:49 ` James Sutherland
2000-11-06 11:51 ` Stephen C. Tweedie
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=20001105133928.A25131@uni-mainz.de \
--to=dominik.kubla@uni-mainz.de \
--cc=hpa@transmeta.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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