On Feb 9, 2015, at 21:02, Ian Lepore <i...@freebsd.org> wrote: > Or... we could consider restoring devd to its original relatively benign > existance handling device-related events, and move handling of crash > dumps into a separate daemon which can shoulder the burden of security > for itself. > > At $work we listen to the devd re-distribute port to handle device > events in our apps, and having an ever-growing flood of stuff that's got > nothing to do with devices is going to have a negative impact on > applications that do such things.
That's perfectly reasonable given that devd handles everything: it gets notified when a new pty is created, when rctls reach their limit, when zfs does "something", when devices show up/disappear, when you unplug the power adapter, when GEOM devices show up/disappear, when your CPU is too hot, when you press the brightness keys, etc. Some of these use cases are fine, others aren't. This is pretty much what happened to udev, if I'm not mistaken. We need a way to avoid reinventing the wheel. I really don't want to duplicate another /dev/devctl in the kernel. -- Rui Paulo _______________________________________________ svn-src-head@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
