> Sheesh, I guess my description was a little bit misunderstandable.
>
> I'm NOT using devfs. The device nodes ARE there where they belong (under the
> /dev directory), BUT they aren't supported by the kernel, i.e. there's no
> kernel code that listens if you attach a process to the 'tty?' file.
>
> Therefore the kernel daemon thread tries to load a suitable module which
> fails (syslog excerpt follows):
>
> modprobe: can't locate module char-major-4
> /sbin/agetty[544]: /dev/tty3: cannot open as standard input: No such
> device
>
> Any other ideas?
You are SOL, unless you want to use some sort of dummy terminal driver.
The kernel has no device to map tty's to, so it can't do anything. It's in
the hands of the admin after that.
Ben
-- -----------=======-=-======-=========-----------=====------------=-=------ / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` bcollins@debian.org -- bcollins@openldap.org -- bmc@visi.net ' `---=========------=======-------------=-=-----=-===-======-------=--=---'- 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 : Fri Mar 31 2000 - 21:00:27 EST