From mboxrd@z Thu Jan 1 00:00:00 1970 From: teg@redhat.com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) Date: Mon, 02 Apr 2001 02:56:06 +0000 Subject: Re: (remove) event not supported. Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org David Hinds writes: > On Sun, Apr 01, 2001 at 06:53:01AM +1000, Brad Hards wrote: >=20 > > Also a good point, but in general, you don't want to do this. If there > > is a device still "connected" to the system, you don't want to remove > > the driver. For development, you might like to simulate a disconnection, > > but the normal approach is that you want support for every device that = is > > connected to the system. Why remove a module for a device you are using? >=20 > Why? >=20 > Well the capability was one of the original reasons for creating > modules in the first place; they were not created for dynamic loading > of drivers for hot plug devices. What's cool about modules, is that you can support everything from the same sets of bootdisk or the same kernel: Compare that to the state of Slackware in 1995. Being able to add support by modules is important, unloading them to save a few kilobytes much less so. --=20 Trond Eivind Glomsr=F8d Red Hat, Inc. _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel