lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 13 Feb 2008 00:25:37 -0800
From:	Greg KH <greg@...ah.com>
To:	Peter Teoh <htmldeveloper@...il.com>
Cc:	Scott Lovenberg <scott.lovenberg@...il.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Mulyadi Santosa <mulyadi.santosa@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	kernelnewbies <kernelnewbies@...linux.org>,
	Rik van Riel <riel@...hat.com>
Subject: Re: Documentation about sysfs/procfs entries

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ