Date: Mon, 09 Feb 2015 21:12:42 -0800 From: Rui Paulo <rpaulo@me.com> To: Ian Lepore <ian@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Rui Paulo <rpaulo@FreeBSD.org> Subject: Re: svn commit: r278494 - head/sys/kern Message-ID: <CC990823-C59E-46C8-A35A-9C173B9F0FB1@me.com> In-Reply-To: <1423544566.80968.9.camel@freebsd.org> References: <201502100434.t1A4YeLr052513@svn.freebsd.org> <7FCF7F90-C1B2-4C1C-8781-F89F8519D47E@me.com> <1423544566.80968.9.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 9, 2015, at 21:02, Ian Lepore <ian@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. >=20 > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CC990823-C59E-46C8-A35A-9C173B9F0FB1>