($INBOX_DIR/description missing)
 help / color / Atom feed
* Incorrect Overlayfs documentation
       [not found] <1750303.WlVpaa6DS8.ref@nerdopolis>
@ 2020-07-16  3:08 ` nerdopolis
  2020-07-16 17:03   ` Amir Goldstein
  0 siblings, 1 reply; 4+ messages in thread
From: nerdopolis @ 2020-07-16  3:08 UTC (permalink / raw)
  To: linux-unionfs

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



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Incorrect Overlayfs documentation
  2020-07-16  3:08 ` Incorrect Overlayfs documentation nerdopolis
@ 2020-07-16 17:03   ` Amir Goldstein
  2020-07-23  3:50     ` nerdopolis
  0 siblings, 1 reply; 4+ messages in thread
From: Amir Goldstein @ 2020-07-16 17:03 UTC (permalink / raw)
  To: nerdopolis; +Cc: overlayfs

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Incorrect Overlayfs documentation
  2020-07-16 17:03   ` Amir Goldstein
@ 2020-07-23  3:50     ` nerdopolis
  2020-07-29  5:51       ` Amir Goldstein
  0 siblings, 1 reply; 4+ messages in thread
From: nerdopolis @ 2020-07-23  3:50 UTC (permalink / raw)
  To: linux-unionfs

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.
> 
> 
Hi.

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"
?

Thanks




^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Incorrect Overlayfs documentation
  2020-07-23  3:50     ` nerdopolis
@ 2020-07-29  5:51       ` Amir Goldstein
  0 siblings, 0 replies; 4+ messages in thread
From: Amir Goldstein @ 2020-07-29  5:51 UTC (permalink / raw)
  To: nerdopolis; +Cc: overlayfs, Miklos Szeredi

On Thu, Jul 23, 2020 at 6:51 AM nerdopolis
<bluescreen_avenger@verizon.net> wrote:
>
> 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.
> >
> >
> Hi.
>
> 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"
> ?
>

That sounds good to me.

CC the maintainer in case he wants to apply this documentation "patch"
himself.

Thanks,
Amir.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1750303.WlVpaa6DS8.ref@nerdopolis>
2020-07-16  3:08 ` Incorrect Overlayfs documentation nerdopolis
2020-07-16 17:03   ` Amir Goldstein
2020-07-23  3:50     ` nerdopolis
2020-07-29  5:51       ` Amir Goldstein

($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