All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Peter Teoh <htmldeveloper@gmail.com>
Cc: Scott Lovenberg <scott.lovenberg@gmail.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Mulyadi Santosa <mulyadi.santosa@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernelnewbies <kernelnewbies@nl.linux.org>,
	Rik van Riel <riel@redhat.com>
Subject: Re: Documentation about sysfs/procfs entries
Date: Wed, 13 Feb 2008 00:25:37 -0800	[thread overview]
Message-ID: <20080213082537.GA14098@kroah.com> (raw)
In-Reply-To: <804dabb00802122340t555e3c26ma903ef97991dd13@mail.gmail.com>

On Wed, Feb 13, 2008 at 03:40:32PM +0800, Peter Teoh wrote:
> some questions:
> 
> a.   the list of parameters can presumably be extracted from existing
> file via "procname" search.....not sure if it is correct (as per
> attached, complete?)

I don't see anything attached :(

> b.   what is the diff between /proc and /sys?   in
> Documentation/filesystems/proc.txt....it is mentioned that /proc
> information will be published into a book...where is it?   I can never
> understand this.

/proc is for process information originally, it grew to take lots of
other different things over the years.

/sys is a tree representation of the devices in the system, as well as a
location for a lot of other kernel specific information.  The rules for
/sys are much more strict (one value per file, if the file isn't there,
the userspace program must be able to handle it, etc.)

> c.   in Doc/sysctl are all the explanation for /proc/sys/* .... as a
> start i think we shall contribute fixing here....but according to your
> email, we should fix Doc/ABI...so I supposed some migration is needed?

Yes, migration of this information to the ABI/ directory would be very
good to have.

> d.   In networking/ip-sysctl.txt a lot of the explanation for the
> attached procname's parameters are explained, may be we can relocate
> it to ABI?

Sounds good to me, but be sure to verify this with the networking
developers as well.

thanks,

greg k-h

  reply	other threads:[~2008-02-13  8:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <804dabb00802112123t774623b2n3e1e0a4addde1512@mail.gmail.com>
     [not found] ` <b1fc6a560802112217j57ab3fa1h611864a6a2423943@mail.gmail.com>
2008-02-12  6:24   ` Documentation about sysfs/procfs entries Scott Lovenberg
2008-02-12  7:46   ` Peter Teoh
     [not found]     ` <47B15DD2.3090706@gmail.com>
2008-02-13  2:08       ` Mulyadi Santosa
2008-02-13  4:43         ` Randy Dunlap
2008-02-13  5:48           ` Peter Teoh
     [not found]           ` <47B2874F.5000805@gmail.com>
2008-02-13  6:03             ` Manish Katiyar
2008-02-13  7:31             ` Greg KH
2008-02-13  7:40               ` Peter Teoh
2008-02-13  8:25                 ` Greg KH [this message]
2008-02-13  9:00                   ` Peter Teoh

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=20080213082537.GA14098@kroah.com \
    --to=greg@kroah.com \
    --cc=htmldeveloper@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulyadi.santosa@gmail.com \
    --cc=randy.dunlap@oracle.com \
    --cc=riel@redhat.com \
    --cc=scott.lovenberg@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.