linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Thu, 3 Apr 2008 09:00:53 -0400
From:	Tom Horsley <tom.horsley@...r.com>
To:	linux-kernel@...r.kernel.org
Subject: module parameters versus kernel command line

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).
--
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/