It has always worried me that drivers would read a file. Files are "user space" and drivers are supposed to be "kernel space". But I have to ask, are my worries justified?
In chasing this current problem, I've twisted /etc/chandev.conf several different ways. But other drivers, on other platforms, would have let me supply parameters to the module(s) when loaded. Here, I have to trust some magic within the drivers, I don't know what assumptions the code might be making. With /proc and other pseudo filesystems, we do see a place where "files" have some connection to kernel space. But there the relationship seems clear. The world of /proc is walled off from the world of "user files". Perhaps I'm being a purist. So I pose the question to the group: Is it okay for kernel code to read plain files for config info? -- R; ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
