Richard Gooch wrote:
>
> Jeff Garzik writes:
> > Richard Gooch wrote:
> > > > create_proc_read_entry ("driver/rtc", 0, 0, rtc_read_proc, NULL);
> > > >
> > > > in addition to the binary-data device /dev/rtc (which is in
> > > > /dev/misc/rtc of devfs). The /proc/driver/rtc is the human-readable
> > > > dump of RTC data and I thought it should find its proper place in
> > > > devfs instead of /proc for the same reasons why we moved microcode
> > > > from /proc/driver to /dev/cpu.
> > >
> > > Yep, it should just be in devfs.
> >
> > Devfs _is not_ the place for generic, driver-specific text output to
> > userspace.
>
> I don't agree. /proc should be for processes and *nothing* else.
At present you are treading against the tide. :)
> > The RTC data dump is in /proc and is not a /dev device for a
> > reason...
>
> And that is?
Um, maybe that RTC is a standard driver, and devfs is an experimental
driver defaulted to off? :) Once devfs makes it into Mandrake, RedHat,
... then it will be time to consider moving EXISTING interfaces from
/proc -> devfs.
Until then, moving existing interfaces to devfs requires the user to run
devfs for functionality which was previously available without. Since
installing devfs is not a "flip a switch and forget" change, you cannot
move existing interfaces to devfs without due consideration, and giving
devfs time to filter out to the userbase at large.
Patience, grasshopper. :) I agree with you in principle, but late in
the 2.3.x cycle is NOT the time to break existing interfaces.
Jeff
-- Jeff Garzik | Building 1024 | Viva la open source! MandrakeSoft, Inc. |- 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