Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
you can skip it. If you happen to know which modules would be critical for your system, you could manually put them in the modules.autoload file, but I've never had a problem and I usually skip that part.
you can skip it. If you happen to know which modules would be critical for your system, you could manually put them in the modules.autoload file, but I've never had a problem and I usually skip that part.
If you wanted, there are two options to view all the modules.
Option1
Code:
find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko' | less
Option2
Once the command is finished, hold down the shift key and press page up. That will scroll back up the screen to see what modules went by to quickly.
you can skip it. If you happen to know which modules would be critical for your system, you could manually put them in the modules.autoload file, but I've never had a problem and I usually skip that part.
If you wanted, there are two options to view all the modules.
Option1
Code:
find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko' | less
Option2
Once the command is finished, hold down the shift key and press page up. That will scroll back up the screen to see what modules went by to quickly.
I totally agree. I usually just know what modules I want loaded, and put them in the autoload file, and forget about it until I need them.
I build almost everything into the kernel though (only things I need though), because I don't much care for modules.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.