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] [day] [month] [year] [list]
Message-ID: <CAMOZ1BsENapdSsiaQj9Yo9aUUx0J5_kyHaz7kVTmq+MNAXhj-Q@mail.gmail.com>
Date:	Tue, 10 Apr 2012 18:18:22 +0000
From:	Michael Witten <mfwitten@...il.com>
To:	Thomas Meyer <thomas@...3r.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: How to skip the initramfs?

On Tue, Apr 10, 2012 at 18:14, Michael Witten <mfwitten@...il.com> wrote:
> On Tue, Apr 10, 2012 at 18:04, Thomas Meyer <thomas@...3r.de> wrote:
>> How to skip the execution of the initramfs? option "noinitrd" doesn't
>> seem to work on 3.0 kernel.
>>
>> Or is there an option to build an abootimg without initramfs? I didn't
>> find one.
>>
>> with kind regards
>> thomas
>
> I have always built my kernel without support for initramfs/initrd
> by setting the build configuration variable `CONFIG_BLK_DEV_INITRD'
> to `n'; in a Kconfig set up UI, you can find this option under
> `General setup' as the item:
>
>  Initial RAM filesystem and RAM disk (initramfs/initrd) support
>
> You should probably also tell your boot loader (such as `grub') not
> to bother loading an initial ram disk.
>
> However, I have the vague notion that there have been rumblings about
> requiring initramfs/initrd support in the future; does anybody know if
> this is true?

I should also add that if you do this, it is imperative that you build
into the kernel all of the necessary drivers for completing the boot
process.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ