linux-kernel - EFI Boot Stub on Removable Media

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>] [day] [month] [year] [list]

Date:	Fri, 16 Mar 2012 15:30:24 -0400
From:	Shea Levy <shea@...alevy.com>
To:	linux-kernel@...r.kernel.org
Subject: EFI Boot Stub on Removable Media

Hello,

I am currently working on making the live CDs for the NixOS distribution 
EFI-bootable with the EFI boot stub as the bootloader. Is there a 
recommended way to use a boot-stub enabled kernel on a removable device 
(where, AFAIK, there is no way to tell the firmware what params to boot 
with automatically)? Currently, I'm hacking together a really 
quick-and-dirty UEFI application that reads a parameters file at a 
pre-defined location and loads the kernel with those parameters, but I'd 
love a better alternative. Is it possible to embed an initrd in a 
bzImage after the image is built? Or is there some way to have a CD tell 
the firmware what arguments to pass to \EFI\BOOT\BOOT{ARCH}.EFI? Or some 
easy tweak to the kernel source to have it use a set of default 
parameters in absence of explicitly passed ones?

Cheers,
Shea Levy
--
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/