O.K. Most of the interesting things should be found in the /proc. But sometimes it is easier to use a program like sensors for collecting and formatting the informations. For the shell you mean this wiki: http://wiki.winehq.org/Shell32 ? It is not so easy to understand the difference between the kernel drivers for the parallel port. At least all kernel-drivers seem to access the parport driver. With lsmod i can see that the kerneldriver parport is used by ppdev, lp, parport_pc Additional i had found some links that helps understanding the stuff: http://www.mjmwired.net/kernel/Documentation/parport.txt 152 modes Parallel port's hardware modes, comma-separated, 153 meaning: 154 155 PCSPP PC-style SPP registers are available. 156 TRISTATE Port is bidirectional. 157 COMPAT Hardware acceleration for printers is 158 available and will be used. 159 EPP Hardware acceleration for EPP protocol 160 is available and will be used. 161 ECP Hardware acceleration for ECP protocol 162 is available and will be used. 163 DMA DMA is available and will be used. http://www.mjmwired.net/kernel/Documentation/parport-lowlevel.txt 155 PARPORT_MODE_TRISTATE The data drivers may be turned off. 156 This allows the data lines to be used 157 for reverse (peripheral to host) 158 transfers. http://parapin.sourceforge.net/ Parapin makes it easy to write C code under Linux that controls individual pins on a PC parallel port. This kind of control is very useful for electronics projects that use the PC's parallel port as a generic digital I/O interface. http://gramlich.net/projects/parallel_server/index.html The state of this project that it is totally and completely dead!
