public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@istop.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Joel Becker <Joel.Becker@oracle.com>,
	linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC][PATCH 1 of 4] Configfs is really sysfs
Date: Wed, 31 Aug 2005 09:37:15 +1000	[thread overview]
Message-ID: <200508310937.15344.phillips@istop.com> (raw)
In-Reply-To: <20050830162846.5f6d0a53.akpm@osdl.org>

On Wednesday 31 August 2005 09:28, Andrew Morton wrote:
> Joel Becker <Joel.Becker@oracle.com> wrote:
> > On Wed, Aug 31, 2005 at 08:54:39AM +1000, Daniel Phillips wrote:
> > > But it would be stupid to forbid users from creating directories in
> > > sysfs or to forbid kernel modules from directly tweaking a configfs
> > > namespace.  Why should the kernel not be able to add objects to a
> > > directory a user created? It should be up to the module author to
> > > decide these things.
> >
> > 	This is precisely why configfs is separate from sysfs.  If both
> > user and kernel can create objects, the lifetime of the object and its
> > filesystem representation is very complex.  Sysfs already has problems
> > with people getting this wrong.  configfs does not.
> > 	The fact that sysfs and configfs have similar backing stores
> > does not make them the same thing.
>
> Sure, but all that copying-and-pasting really sucks.  I'm sure there's some
> way of providing the slightly different semantics from the same codebase?

I will have that patch ready later this week.

Regards,

Daniel

  parent reply	other threads:[~2005-08-30 23:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 22:54 [RFC][PATCH 1 of 4] Configfs is really sysfs Daniel Phillips
2005-08-30 22:57 ` [RFC][PATCH 2 " Daniel Phillips
2005-08-30 22:59   ` [RFC][PATCH 3 " Daniel Phillips
2005-08-30 23:03     ` [RFC][PATCH 4 " Daniel Phillips
2005-08-30 23:30       ` Daniel Phillips
2005-08-30 23:06     ` [RFC][PATCH 3 " Stephen Hemminger
2005-08-30 23:18       ` Daniel Phillips
2005-08-30 23:10     ` Daniel Phillips
2005-08-30 23:22   ` [RFC][PATCH 2 " Daniel Phillips
2005-08-30 23:13 ` [RFC][PATCH 1 " Joel Becker
2005-08-30 23:25   ` Daniel Phillips
2005-08-30 23:35     ` Daniel Phillips
2005-08-30 23:28   ` Andrew Morton
2005-08-30 23:34     ` viro
2005-08-30 23:51       ` Daniel Phillips
2005-08-30 23:37     ` Daniel Phillips [this message]
2005-08-31  0:03     ` Joel Becker
2005-09-04  3:53     ` Joel Becker
2005-09-04  4:12       ` Joel Becker
2005-09-04  4:41         ` Joel Becker
2005-09-04  4:54           ` Joel Becker
2005-09-07 20:31             ` Greg KH

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=200508310937.15344.phillips@istop.com \
    --to=phillips@istop.com \
    --cc=Joel.Becker@oracle.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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