"Jeroen N. Witmond" <[EMAIL PROTECTED]> writes: > I have searched the mailing list archives for this problem, and I > understand it can be solved by aliasing module char-major-10 to off, but > I would like to understand what is going on. (It is not really a > problem, because in spite of the message everything seems to work.)
[snip] > In human language: The Debian 2.0.34 configured the serial support as a > module, whereas I included it into the 2.0.36 kernel itself. It seems > that, even when the serial support is included into the kernel, > 'somebody' still wants to access it as a module, but I can't find who, > where and why. Serial ports are on char-major-4; see "ls -l /dev/ttyS0": crw-rw---- 1 root dialout 4, 64 Feb 10 1998 /dev/ttyS0 major ^ ^^ minor char-major-10 is misc devices such as psaux, watchdog, apm and nvram - "cat /proc/misc" should list the ones you're using. Presumably something is trying to access one of the misc devices. You might be able to get some idea of what's happening with: $ cd /dev $ ls -ltur [...] crw-rw---- 1 uucp dialout 4, 65 Jan 3 10:32 ttyS1 crw------- 1 root sys 10, 1 Jan 3 11:53 psaux prw-r--r-- 1 root root 0 Jan 3 11:55 xconsole| [...] crw-rw-rw- 1 root root 2, 1 Jan 3 11:58 ptyp1 crw--w---- 1 carey tty 3, 1 Jan 3 11:58 ttyp1 crw--w--w- 1 root root 4, 7 Jan 3 11:58 tty7 $ -- Carey Evans http://home.clear.net.nz/pages/c.evans/ Larry froze. Was the bag a trap? He could see the way in, but the other end appeared to be sealed.