Richard Gooch wrote:
>
> H. Peter Anvin writes:
> > Followup to: <200002222116.IAA03334@mobilix.atnf.CSIRO.AU>
> > By author: Richard Gooch <rgooch@atnf.csiro.au>
> > In newsgroup: linux.dev.kernel
> > >
> > > Tigran Aivazian writes:
> > > > Hi Richard,
> > > >
> > > > I thought of moving /proc/kcore to devfs and there is no obvious
> > > > place to put it. Why not create a /dev/debug/ and put kcore (and
> > > > profile) in there? In the future one can have ktrace (or whatever
> > > > it was called from IKD patches, can't remember).
> > >
> > > How is /proc/kcore different from /dev/kmem or one of those devices,
> > > anyway? (I haven't bothered to look)
> > >
> > > I'm considering moving the "memory" devices to /dev/mem anyway.
> > > /proc/kcore, if it is actally different, would belong there, IMO.
> >
> > The memory devices would be inadvisable to move, since they are
> > "well known" device locations. ALL Unices have them.
>
> Yes, I know. That's why the patch I sent to Linus didn't do that ;-)
> But perhaps /dev/kmem, /dev/mem, /dev/port, /dev/random and
> /dev/urandom could be moved, since only Linux-specific tools would
> need to be modified.
>
> It's really only /dev/full, /dev/null and /dev/zero that are "well
> known".
>
ALL Unices have /dev/mem, /dev/kmem, and several non-Linuxes have
/dev/random and /dev/urandom. Furthermore, these names are already used
by a large number of tools.
There really is nothing to gain by removing them, as they are
one-of-a-kind devices. It's rather different with things that can exist
in N duplicates.
-hpa
-- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:32 EST