public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Nico Schottelius <nico-mutt@schottelius.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysfs vs. procfs, devfs vs. ufs ?
Date: Sat, 08 Nov 2003 19:28:44 -0500	[thread overview]
Message-ID: <1068337724.27320.217.camel@localhost> (raw)
In-Reply-To: <20031107032856.GS25124@schottelius.org>

On Thu, 2003-11-06 at 22:28, Nico Schottelius wrote:

> what is the intention of sysfs?
> is it a replacement/addition to procfs?

sysfs is a filesystem used to export the device model (a tree of data
structures representing the devices in a system) to user-space in a
clean and efficient way.

procfs is a more generic (and less elegant) filesystem for exporting
anything to user-space.

sysfs only replaces procfs in so far as relevant interfaces, such as
those related to hardware.  process information should remain in procfs.

/proc is not going anywhere.

	Robert Love



      reply	other threads:[~2003-11-09  0:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-07  3:28 sysfs vs. procfs, devfs vs. ufs ? Nico Schottelius
2003-11-09  0:28 ` Robert Love [this message]

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=1068337724.27320.217.camel@localhost \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-mutt@schottelius.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