[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d120d5000609010523n6942d881k19c19a22ea102068@mail.gmail.com>
Date: Fri, 1 Sep 2006 08:23:43 -0400
From: "Dmitry Torokhov" <dmitry.torokhov@...il.com>
To: "Greg KH" <greg@...ah.com>
Cc: "Neil Brown" <neilb@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: RFC - sysctl or module parameters.
On 9/1/06, Greg KH <greg@...ah.com> wrote:
> On Fri, Sep 01, 2006 at 12:02:52PM +1000, Neil Brown wrote:
>
> > Thus we could just have a module option, just add module config
> > information to /etc/modprobe.d and run
> > modprobe --apply-option-to-active-modules
> > at the same time as "sysctl -p" and it would all 'just work'
> > whether the module were compiled in to not.
>
> Ah, you want it after the code is loaded. That's different.
>
> Would probably work just fine, no objection from me. Except you would
> have to hack up the module-init-tools package :)
>
This will be pretty hard to implement in general as quite a few module
parameters do not allow changing once set and so you will have to
virtually reload modules while doing your "modprobe --apply.." trick.
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists