Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 1 Jul 2002 14:40:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 1 Jul 2002 14:40:37 -0400 Received: from 213-96-124-18.uc.nombres.ttd.es ([213.96.124.18]:12267 "HELO dardhal.mired.net") by vger.kernel.org with SMTP id ; Mon, 1 Jul 2002 14:40:33 -0400 Date: Mon, 1 Jul 2002 20:42:57 +0200 From: Jose Luis Domingo Lopez To: Linux-Kernel Mailing List Subject: Re: [OKS] Module removal Message-ID: <20020701184257.GC1762@localhost> Mail-Followup-To: Linux-Kernel Mailing List References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1357 Lines: 30 On Monday, 01 July 2002, at 13:48:55 -0400, Bill Davidsen wrote: > The suggestion was made that kernel module removal be depreciated or > removed. I'd like to note that there are two common uses for this > capability, and the problems addressed by module removal should be kept in > mind. These are in addition to the PCMCIA issue raised. > >From my non-kernel non-programmer point of view, module removal can be useful under more circunstances than the ones you said. For example, trying some combination of parameters for a module to get you damned piece of hardware working, and having to reboot each time you want to pass it a different set of parameters, doesn't seem reasonable to me. Examples such as network cards (as Bill said), your nice TV capture card, or just setting a "debug=1" for a module that seems not to be working OK. Except there was a way to pass parameters to modules once loaded, and have them "reconfigure" themselves for the new parameters. Just the opinion of a Linux user :) -- Jose Luis Domingo Lopez Linux Registered User #189436 Debian Linux Woody (Linux 2.4.19-pre6aa1) - 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/