linux-kernel - Re: COMPILING AND CONFIGURING A NEW KERNEL.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 07 Apr 2007 12:42:54 -0400
From:	Valdis.Kletnieks@...edu
To:	johnrobertbanks@...tmail.fm
Cc:	Ignatich <ignatich@...il.com>, reiserfs-list@...esys.com,
	linux-kernel@...r.kernel.org
Subject: Re: COMPILING AND CONFIGURING A NEW KERNEL.

On Fri, 06 Apr 2007 18:26:45 PDT, johnrobertbanks@...tmail.fm said:
>
> YOU SHOULD compile all the drivers necessary to boot your system, into
> the kernel (ie, such drivers should not be built as modules).
> 
> This way you will NOT need an initrd file.

It is quite possible to build a kernel that has all the drivers built-in,
but still require an initrd file.  For instance, if you have a recent
RedHat or Fedora system, '/' may very well be on an LVM partition, which
means you need an initrd to do a 'lvm varyonvg' before mounting your real
root filesystem will work....

Content of type "application/pgp-signature" skipped