linux-kernel - Re: Linux as Bootloader

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:	Tue, 06 Sep 2011 11:18:05 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Christian Gmeiner <christian.gmeiner@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Linux as Bootloader

Christian Gmeiner <christian.gmeiner@...il.com> writes:

> Hi all,
>
> I am using the linux kernel in combination with busybox and a separate
> bootloader app to
> startup a x86 based embedded device. As the used BIOS does only do
> basic hw init, we
> used Linux as a bootloader. Our custom BIOS starts the bootloader
> kernel located in BIOS
> flash. If the kernel and userland is ready our boot application
> searches for the productive kernel
> and executes it via kexec.
>
> Now I run in some troubles as I need to be able to boot a MSDOS
> application stored on
> an usb stick. I have tried grub4linux but I am not able to boot from
> the usb stick - even I
> see the grub command line.
>
> Are there some creative/working solutions for my problem?

There has been some success using a modified bochs bios on real hardware
in the context of coreboot.  That should be loadable from linux and
usable on your setup.  Avoiding the DOS requirement is probably a more
certain path, getting DOS going is probably more fun.

Eric
--
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/