From owner-svn-src-head@FreeBSD.ORG Tue Feb 10 05:13:20 2015 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CC9C9AB; Tue, 10 Feb 2015 05:13:20 +0000 (UTC) Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtp001.mac.com [17.172.220.236]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1DFE2117; Tue, 10 Feb 2015 05:13:19 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (unknown [73.162.13.215]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014)) with ESMTPSA id <0NJJ00J6SIH6PY20@st11p02mm-asmtp001.mac.com>; Tue, 10 Feb 2015 05:12:45 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-02-10_03:2015-02-09,2015-02-10,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1502100052 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: svn commit: r278494 - head/sys/kern From: Rui Paulo In-reply-to: <1423544566.80968.9.camel@freebsd.org> Date: Mon, 09 Feb 2015 21:12:42 -0800 Content-transfer-encoding: quoted-printable Message-id: References: <201502100434.t1A4YeLr052513@svn.freebsd.org> <7FCF7F90-C1B2-4C1C-8781-F89F8519D47E@me.com> <1423544566.80968.9.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.2070.6) Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Rui Paulo X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 05:13:20 -0000 On Feb 9, 2015, at 21:02, Ian Lepore 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