linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: man filesystems(5) doesn't contain Btrfs
Date: Thu, 16 Feb 2017 15:47:58 -0500	[thread overview]
Message-ID: <46520c5e-1c83-efaf-fc3f-a4af4810eb88@gmail.com> (raw)
In-Reply-To: <CAJCQCtSo7nrgU4jkr85vm+4S9iwyoLF_USjZ4DTbd__-a62qGg@mail.gmail.com>

On 2017-02-16 15:36, Chris Murphy wrote:
> Hi,
>
> This man page contains a list for pretty much every other file system,
> with a oneliner description: ext4, XFS is in there, and even NTFS, but
> not Btrfs.
>
> Also, /etc/filesystems doesn't contain Btrfs. Anyone know if either,
> or both, ought to contain an entry for Btrfs?
>
The man-page absolutely should.  Ideally, that should be kept in sync 
with with the mount manpages, but I think they're in separate projects 
(mount is util-linux IIRC, while filesystems(5) is part of the Linux 
man-pages project).

As far as /etc/filesystems, that should be irrelevant.  Of the big 
distros, only SUSE, Fedora/CentOS/OEL, and Gentoo use it (I checked 
Arch, Gentoo, openSUSE, Fedora, Debian, and Ubuntu, which should cover 
at least 80% of users since this is low enough level derivatives won't 
be likely to change it), and all it does is dictate what order 'mount -t 
auto' will try filesystem types in.  All the distros that have it have a 
'*' on the last line, which means to check /proc/filesystems, and 
therefore will automatically try BTRFS if there's a kernel module for it 
(unless the module is blacklisted or prevented from being loaded on boot 
automatically).

  reply	other threads:[~2017-02-16 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 20:36 man filesystems(5) doesn't contain Btrfs Chris Murphy
2017-02-16 20:47 ` Austin S. Hemmelgarn [this message]
2017-02-18  6:02   ` Andrei Borzenkov

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=46520c5e-1c83-efaf-fc3f-a4af4810eb88@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 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).