From: nerdopolis <bluescreen_avenger@verizon.net>
To: linux-unionfs@vger.kernel.org
Subject: Incorrect Overlayfs documentation
Date: Wed, 15 Jul 2020 23:08:47 -0400 [thread overview]
Message-ID: <1750303.WlVpaa6DS8@nerdopolis> (raw)
In-Reply-To: 1750303.WlVpaa6DS8.ref@nerdopolis
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?
Thanks
next parent reply other threads:[~2020-07-16 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1750303.WlVpaa6DS8.ref@nerdopolis>
2020-07-16 3:08 ` nerdopolis [this message]
2020-07-16 17:03 ` Incorrect Overlayfs documentation Amir Goldstein
2020-07-23 3:50 ` nerdopolis
2020-07-29 5:51 ` Amir Goldstein
[not found] ` <CAH2+hP4=9A2fWkJgJhUZps+5gCqZfPSzfNJDXW3FHjDZmk3-vA@mail.gmail.com>
2021-01-04 3:32 ` nerdopolis
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=1750303.WlVpaa6DS8@nerdopolis \
--to=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
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