Summary: | Method of listing all available kernel modules cumbersome | ||
---|---|---|---|
Product: | [OLD] Docs on www.gentoo.org | Reporter: | OzoneHole <gkburns> |
Component: | Installation Handbook | Assignee: | Docs Team <docs-team> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=7 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
OzoneHole
2009-03-28 05:12:10 UTC
Or use |less Or use |less Is there any reason why we can't use `modprobe -l` instead of find? That only does it for the currently running kernel. Which is not the one that was just compiled and installed. And since it only works for one kernel, that doesn't help if the user has multiple kernels/versions installed, whereas with "find" you get to pick which kernel version you want to examine. Also, the manpage for modprobe itself suggests using the "find" approach, rather than using "-l", which modprobe says is provided only for compatibility reasons. |