linux-kernel - Re: module parameters versus kernel command line

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Apr 2008 09:14:44 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Tom Horsley <tom.horsley@...r.com>
Cc:	linux-kernel@...r.kernel.org, rusty@...tcorp.com.au
Subject: Re: module parameters versus kernel command line

On Thu, 3 Apr 2008 12:04:25 -0400 Tom Horsley wrote:

> On Thu, 3 Apr 2008 08:39:53 -0700
> Randy Dunlap <randy.dunlap@...cle.com> wrote:

Please use reply-to-all.

> > Module parameters for modules that are built into the kernel image
> > are specified on the kernel command line with the module name plus
> > '.' plus parameter name, with '=' and value if appropriate, such as:
> > 
> > 	usbcore.blinkenlights=1
> 
> I know that part, I'm just wondering if it would be nice to have
> even dynamically loaded modules notice the kernel option
> so that the "usbcore" module would see the "blinkenlights=1"
> parameter from the kernel boot options when dynamically loaded?
> 
> That way, you wouldn't have to stop and figure out if a module
> was static or dynamic to decide if you need to edit the grub boot
> line or the modprobe.conf file.

OK, that makes some sense to me.

Rusty added to cc for his objective viewpoint.

---
~Randy
--
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/