From: "Steve French (smfltc)" <smfltc@us.ibm.com>
To: linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org,
jengelh@linux01.gwdg.de
Subject: Re: linux-cifs-client Digest, Vol 42, Issue 1
Date: Tue, 01 May 2007 12:33:08 -0500 [thread overview]
Message-ID: <463779D4.9010507@us.ibm.com> (raw)
In-Reply-To: <20070501101821.44AFA16386A@lists.samba.org>
> what also puzzles me... almost every filesystem that's not at revision 1
> anymore (ext2/3/4, reiser4, smb2) does not have the usually omnipresent "fs"
> suffix anymore (cf. reiserfs, smbfs).
> Maybe it's time to drop all the "fs" suffixes? :)
For the case of cifs (and nfs and afs) the "fs" is part of the name of
the protocol ("common internet file system [protocol]") but for the
other filesystems I agree that it seems redundant to put "fs" in the
name (with a few exceptions e.g. "GFS2" would sound strange if named
"G2" or "global2", and OCFS2 is presumably a product name).
parent reply other threads:[~2007-05-01 17:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070501101821.44AFA16386A@lists.samba.org>]
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=463779D4.9010507@us.ibm.com \
--to=smfltc@us.ibm.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-cifs-client@lists.samba.org \
--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