($INBOX_DIR/description missing)
 help / color / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: nerdopolis <bluescreen_avenger@verizon.net>
Cc: overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: Incorrect Overlayfs documentation
Date: Thu, 16 Jul 2020 20:03:52 +0300
Message-ID: <CAOQ4uxgm8dHd2EQPgD_a7aKwFUQFKGZg9O7K_FsuJGuWH=P8pg@mail.gmail.com> (raw)
In-Reply-To: <1750303.WlVpaa6DS8@nerdopolis>

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.

  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 [this message]
2020-07-23  3:50     ` nerdopolis
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:
  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='CAOQ4uxgm8dHd2EQPgD_a7aKwFUQFKGZg9O7K_FsuJGuWH=P8pg@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=bluescreen_avenger@verizon.net \
    --cc=linux-unionfs@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

($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 \
		linux-unionfs@vger.kernel.org
	public-inbox-index linux-unionfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-unionfs


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