Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #58023
| From | Henrique de Moraes Holschuh <hmh@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#864716: modules and custom kernels |
| Date | 2017-06-13 17:20 +0200 |
| Message-ID | <tRVLP-19S-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
It is recommended that users building their own kernels never configure as a module any driver that Debian doesn't configure as a module. Anyway, essential modules for system operation should preferably be added to /etc/modules. They will be early-loaded by whatever gets to them first (be it the initramfs, or systemd, or sysvinit). Both initramfs-tools and dracut know to always add modules present in /etc/modules to the initramfs, and attempt to manually load them. Adding essential modules to /etc/initramfs-tools/modules works, but it is specific to initramfs-tools. -- Henrique Holschuh
Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread
Bug#864716: modules and custom kernels Henrique de Moraes Holschuh <hmh@debian.org> - 2017-06-13 17:20 +0200
csiph-web