linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: wharms-fPG8STNUNVg@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] proc.5: /proc/fs is not empty directory
Date: Thu, 12 Jun 2014 13:45:12 +0200	[thread overview]
Message-ID: <539992C8.5020809@redhat.com> (raw)
In-Reply-To: <53917DD5.5090708-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>


On 06/06/2014 10:37 AM, Jan Chaloupka wrote:
> On 06/05/2014 04:54 PM, walter harms wrote:
>> Am 05.06.2014 16:02, schrieb jchaloup:
>>> Man page for proc says:
>>> /proc/fs
>>>           Empty subdirectory.
>>>
>>> But ls says something else:
>>> $ ls /proc/fs/
>>> ext4  jbd2  nfs  nfsd
>>>
>>> In addition from 
>>> https://www.kernel.org/doc/Documentation/filesystems/proc.txt, 
>>> caption: 1.9 Ext4 file system parameters:
>>>
>>> Information about mounted ext4 file systems can be found in
>>> /proc/fs/ext4.
>>>
>>> This patch gives better description for the content. Open to give 
>>> more description if someone knows more or where to find it.
>>>
>>> Signed-off-by: jchaloup <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>>> ---
>>>   man5/proc.5 |    2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/man5/proc.5 b/man5/proc.5
>>> index 8fd7b19..956760c 100644
>>> --- a/man5/proc.5
>>> +++ b/man5/proc.5
>>> @@ -1805,7 +1805,7 @@ Then filesystems contained in this file are tried
>>>   (excepted those that are marked with "nodev").
>>>   .TP
>>>   .I /proc/fs
>>> -Empty subdirectory.
>>> +Directory shows which file systems are exported.
>>>   .TP
>>>   .I /proc/ide
>>>   This directory
>> hi,
>> exported sounds for me like nfs export. what is about:
>> "Information about mounted file systems" (copied and ajusted from 
>> proc.txt)
> Fine for me.

Ping Michael

>> re,
>>   wh
>>
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-man" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-06-12 11:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 14:02 [PATCH] proc.5: /proc/fs is not empty directory jchaloup
     [not found] ` <20140605140204.25995.48033.stgit-/v0jm+aXwyk2pP1PFFXgSPXAX3CI6PSWQQ4Iyu8u01E@public.gmane.org>
2014-06-05 14:54   ` walter harms
     [not found]     ` <539084A4.30301-fPG8STNUNVg@public.gmane.org>
2014-06-06  8:37       ` Jan Chaloupka
     [not found]         ` <53917DD5.5090708-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-06-12 11:45           ` Jan Chaloupka [this message]
2014-06-12 13:16           ` Michael Kerrisk (man-pages)

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=539992C8.5020809@redhat.com \
    --to=jchaloup-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=wharms-fPG8STNUNVg@public.gmane.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;
as well as URLs for NNTP newsgroup(s).