On Wed, 27 Oct 1999, Jeff Garzik wrote:
> Alex,
>
> I now have most of your procfs patch ported to the latest kernels, at
>
>http://gtf.org/garzik/kernel/files/UNTESTED/proc_cleanup_19991026-2.3.24-pre1.patch.gz
>
> Note this is a --cvs patch-- and thus not easily applied by patch.
Thanks. I'll look at it ASAP.
> It compiles against 2.3.24 pre1, and probably(tm) works.
>
> The next step in my plan for feeding patches to Linus is to test the
> cleanup of fs/proc/* and send that to Linus -- EXCEPT temporarily keep
> the proc_net_register function. (it will go away later) If I don't do
> that, I am forced to send all the procfs net code updates too.
>
> After that goes in, the remaining drivers and the networking code will
> be cleaned up. Most of the networking code is already updated as you
> will see from the patch above.
>
> TODO:
> * merge the rest of your procfs patch, mainly drivers/* is left now
>
> * go through and audit each file to make sure a create_xxx is followed
> by remove_xxx. Many times it is not, which will cause an oops as you
> know
>
> * ...the other TODO items you posted about in the "updates to procfs"
> thread
There's actually one more TODO point. And pretty serious one, at it.
We got a severely cluttered namespace under /proc (little gems a-la
/proc/h8 and friends). It's a Bad Thing (tm) for a lot of obvious reasons.
We can move to something saner if
a) we'll agree on a naming policy
b) add a PROC_COMPAT option that would just create a bunch of
static symlinks from old to new locations.
c) for unimportant (== used by a couple of driver-related
utilities) things - remove the links when the utilities will be updated
d) for important stuff - gather the links into proc_compat.o and
make it a module. And ask everybody to use the new locations, so that
folks who are not stuck with old binaries might completely get rid of the
clutter.
(a) is obviously the trickiest ;-/
