|
|
Log in / Subscribe / Register

Restricting automatic kernel-module loading

Restricting automatic kernel-module loading

Posted Dec 5, 2017 11:21 UTC (Tue) by ballombe (subscriber, #9523)
In reply to: Restricting automatic kernel-module loading by nix
Parent article: Restricting automatic kernel-module loading

On the other hand, It is far easier to remember "1" than how to spell "by-capability".


to post comments

Restricting automatic kernel-module loading

Posted Dec 5, 2017 12:00 UTC (Tue) by hrw (subscriber, #44826) [Link]

root@krzys:/sys/devices/platform/ar934x_wmac/leds/ath9k-phy0# cat trigger
none nand-disk switch0 timer default-on netdev usbport phy0rx phy0tx phy0assoc phy0radio [phy0tpt] phy1rx phy1tx phy1assoc phy1radio phy1tpt

$ cat the-switch-controlling-autoload-of-modules
always [by-capability] never

Doable?

Restricting automatic kernel-module loading

Posted Dec 6, 2017 13:59 UTC (Wed) by nix (subscriber, #2304) [Link]

It's far easier to remember how to spell '1', yes, but its meaning is entirely implicit and context-dependent. In practice you're going to have to look it up every time you use it, since this is not a flag you're likely to flip often. Meanwhile, textual strings are self-describing.

(Imagine this with the block layer. It's easy to flip to the deadline scheduler, just echo 1 > /sys/block/$foo/queue/scheduler! The default, cfq, is 3, of course, because it happened to be the third scheduler added. The second scheduler was removed long ago, so 2 is not valid any more, until of course someone adds another scheduler, when 2 is apt to get randomly picked up by that instead...)


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds