Messages in this thread | | | Date | Wed, 18 Aug 2004 08:22:10 +0200 | From | Olaf Hering <> | Subject | Re: 2.6.8.1-mm1 Tty problems? |
| |
On Tue, Aug 17, Paul Fulghum wrote:
> ismail dönmez wrote: > > >>That does not look right. > >>Char dev 3 is the pty major. > >>This could be left over from running with the controlling-tty patch. > >> > >>Try recreating /dev/tty as a char special file: > >>mknod -m 666 /dev/tty c 5 0 > > > > > >Hmm I use udev and /dev/tty dir is created again at startup. So > >something else is broken too I think. > > This is almost certainly related to the addition > of pty devices to devfs in bk-driver-core.patch > Change is by olh@suse.de > > This explains why you are seein pty major devices > created in a /dev/tty directory.
/dev/tty is supposed to be char c 5 0, /class/tty/tty/dev will tell udev how to create it, see man 4 tty. No idea who came up with the bright idea to put legacy bsd devices in a subdir. Documentation/devices.txt shows that my patch is ok, it handles up to 256 device nodes. If you are using udev, file a bugreport for your distros package. In the meantime, remove the offending line from your udev.rules file.
-- USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |