Messages in this thread | | | Date | Wed, 23 Nov 2005 18:24:50 +0100 | From | Marc Koschewski <> | Subject | Re: Christmas list for the kernel |
| |
* Jon Smirl <jonsmirl@gmail.com> [2005-11-23 12:13:06 -0500]:
> On 11/23/05, Marc Koschewski <marc@osknowledge.org> wrote: > > * Jon Smirl <jonsmirl@gmail.com> [2005-11-23 11:59:27 -0500]: > > > Another would be to have a little user space daemon that listened to > > > the pty creation, and then mknod the tty nodes as need and pipe the > > > data through. That would be a first step to moving to a user space > > > console implementation. > > > > Shouldn't this be udev then? I hear people scream when 'some deamon' > > created a device in /dev. Was it udev? Was is 'ttydevd'? Even > > 'ondemanddevd'? > > udev listens to /sys/class for it's indications on when to create a node. > > The tty daemon would need to listen for pty creation to tell it when > to create a node. Then after it creates the node it needs to maintain > a pipe between the pty and tty. This is a lot different than what udev > does.
I didn't mean to _say_ that it's the same. I just meant to _ask_ how you are going to tell the users which daemon created what devices in /dev. I would rather do the 'udev appoach' then (extend it in other words) so that there's just one daemon that creates device nodes.
Marc - 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/
| |