mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] devfs API
Date: Thu, 14 Nov 2002 10:51:10 -0700	[thread overview]
Message-ID: <200211141751.gAEHpAVm021359@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.GSO.4.21.0211101348350.24061-100000@steklov.math.psu.edu>

Alexander Viro writes:
> 	During the last couple of weeks I'd done a lot of digging in
> devfs-related code.  Results are interesting, and not in a good sense.
> 
> 	1) a _lot_ of functions exported by devfs are never used.  At
> all.
[...]

I don't have time right now do deal with all the points you raised,
I'll deal with each of the points you raise over the next week or
so. However, I'll make a couple of quick points:

- I'm leery of changing the API and breaking compatibility between 2.4
  and 2.5 drivers. I also don't want to break out-of-tree drivers
  without giving maintainers plenty of warning. There are a number
  such out there

- I have far more drastic plans for code reduction in devfs. The plan
  I've mentioned since OLS is to leverage sysfs so that devfsd can be
  used to populate devfs from user-space. For the root FS device, I
  figure on writing a mini devfsd for initramfs. From the perspective
  of user-space, this will provide functional compatibility. From
  kernel-space it will effectively be an API change, so I don't want
  to do this twice.

I'd hoped to get the new major version of devfs ready before the
freeze, but limited time (read: funding) has been available. Oh, well.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2002-11-14 17:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-10 22:19 Alexander Viro
2002-11-10 23:52 ` oops when adding bridge interface, using v2.5.45 Bart De Schuymer
2002-11-10 23:08   ` romieu
2002-11-11  0:49     ` Bart De Schuymer
2002-11-12  1:32 ` [RFC] devfs API Ryan Anderson
2002-11-12  1:49   ` Alexander Viro
2002-11-12  8:04     ` Theodore Ts'o
2002-11-12  8:44       ` Rudmer van Dijk
2002-11-12  9:50         ` Miles Bader
2002-11-12 10:57         ` Helge Hafting
2002-11-12  9:43       ` Alexander Viro
2002-11-12 10:47       ` Helge Hafting
2002-11-12 21:57       ` Jon Portnoy
2002-11-13 15:15       ` Denis Vlasenko
2002-11-12  1:50   ` Robert Love
2002-11-12 11:44 ` William Lee Irwin III
2002-11-14 17:51 ` Richard Gooch [this message]
2002-11-14 18:04   ` Alexander Viro

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=200211141751.gAEHpAVm021359@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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

all inboxes | Powered by JetHome®