Messages in this thread | | | Date | Tue, 22 Feb 2000 22:11:25 -0500 (EST) | From | George <> | Subject | Re: [patch-2.3.47] /proc/driver/microcode -> /dev/cpu/microcode |
| |
On Wed, 23 Feb 2000, 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.
For all these things being moved to /dev from /proc, are major/minors going to be created so people can use on-disk /dev or shall it be a "tough, use devfs" attitude?
-George Greer
- 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/
| |