| 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
| ||
|
Date: Thu, 11 Jan 2007 22:08:12 +0100 (CET) From: Stefan Richter <stefanr@...6.in-berlin.de> To: Sunil Naidu <akula2.shark@...il.com> cc: linux-kernel@...r.kernel.org Subject: Re: Linux-2.6.20-rc4 - Kernel panic! Sunil Naidu wrote: > compiling a driver as module has same affect (while > loading/booting of kernel) compare to compiling a driver as kernel > builtin feature? LKML is not the place for such questions. Modules have to be loaded from a filesystem while built-in features are available from the start. The bootloader only loads the kernel image and optionally an initrd. The initrd is used as a preliminary root filesystem which may contain kernel modules to load to make the real root filesystem accessible. That's what distributors do because they don't know in advance which drivers their users will actually need. Endusers who build their own kernels might as well compile all drivers that are needed for access to the root filesystem into the kernel image and work without initrd. -- Stefan Richter -=====-=-=== ---= -=-== http://arcgraph.de/sr/ - 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/
Powered by blists - more mailing lists