($INBOX_DIR/description missing)
 help / color / Atom feed
From: nerdopolis <bluescreen_avenger@verizon.net>
To: linux-unionfs@vger.kernel.org
Subject: Re: Incorrect Overlayfs documentation
Date: Wed, 22 Jul 2020 23:50:59 -0400
Message-ID: <7866875.n4lXpxAzLT@nerdopolis> (raw)
In-Reply-To: <CAOQ4uxgm8dHd2EQPgD_a7aKwFUQFKGZg9O7K_FsuJGuWH=P8pg@mail.gmail.com>

On Thursday, July 16, 2020 1:03:52 PM EDT Amir Goldstein wrote:
> On Thu, Jul 16, 2020 at 6:09 AM nerdopolis
> <bluescreen_avenger@verizon.net> wrote:
> >
> > Hi
> >
> > A while back I opened up https://bugzilla.kernel.org/show_bug.cgi?id=195113 describing a documentation problem in
> > https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt but for whatever reason, it hasn't been seen.
> >
> >
> > The problem is that it says "The lower filesystem can be any filesystem supported by Linux"
> > however, this is not the case, as Linux supports vfat, and vfat doesn't work as a lower filesystem
> >
> > So there's no way to tell what filesystems are applicable for an overlay lowerfs,
> > and I don't think any existing userspace utilities can detect it.
> >
> > Could it be possible for the .txt file to be updated?
> >
> The way it works usually in this project is you can submit a patch to fix the
> problem:
> https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html
> But if you don't want to go through that process, you can offer a text to
> fix documentation.
> But I myself cannot offer anything better than:
> "The lower filesystem can be one of many filesystem supported by Linux".
> I don't think that we want to start listing the supported filesystems in
> documentation.
> FWIW the description of upper fs isn't uptodate either.
> Thanks,
> Amir.

Yeah, that process might be cumbersome. I guess what you have is good.
Maybe "A wide range of filesystems supported by Linux can be the lower
filesystem, however, not all filesystems that are mountable by Linux have the
features needed for OverlayFS to work"


  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1750303.WlVpaa6DS8.ref@nerdopolis>
2020-07-16  3:08 ` nerdopolis
2020-07-16 17:03   ` Amir Goldstein
2020-07-23  3:50     ` nerdopolis [this message]
2020-07-29  5:51       ` Amir Goldstein

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7866875.n4lXpxAzLT@nerdopolis \
    --to=bluescreen_avenger@verizon.net \
    --cc=linux-unionfs@vger.kernel.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

($INBOX_DIR/description missing)

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-unionfs/0 linux-unionfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-unionfs linux-unionfs/ https://lore.kernel.org/linux-unionfs \
	public-inbox-index linux-unionfs

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git