| 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
| ||
|
Date: Thu, 3 Apr 2008 08:39:53 -0700 From: Randy Dunlap <randy.dunlap@...cle.com> To: Tom Horsley <tom.horsley@...r.com> Cc: linux-kernel@...r.kernel.org Subject: Re: module parameters versus kernel command line On Thu, 3 Apr 2008 09:00:53 -0400 Tom Horsley wrote: > Just curious: Is there any reason even dynamically loaded > modules shouldn't be able to find module parameters on > the kernel command line? I haven't actually investigated > the code involved (since I have no idea where it is :-), > but it sure seems like it would be convenient to have > a single place to put module parameters where they > would always be found regardless of the module's static > or dynamic build mode (especially when multi-booting > different kernels built different ways). > -- Does this answer your question? from Documentation/kernel-parameters.txt: Module parameters for loadable modules are specified only as the parameter name with optional '=' and value as appropriate, such as: modprobe usbcore blinkenlights=1 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 --- ~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/
Powered by blists - more mailing lists