From: "Enrico Weigelt, metux IT consult" <weigelt@melag.de>
To: Thiago Farina <tfransosi@gmail.com>, Pavel Machek <pavel@ucw.cz>
Cc: linux list <linux-kernel@vger.kernel.org>
Subject: Re: boot loader
Date: Tue, 12 May 2015 13:11:26 +0200 [thread overview]
Message-ID: <5551DFDE.6040905@melag.de> (raw)
In-Reply-To: <CACnwZYfvr3d6E7=8gg0QcJqnY+5YiPqxewzt1987Au0h2YbxbQ@mail.gmail.com>
Am 12.05.2015 um 02:17 schrieb Thiago Farina:
> Yeah. Maybe it was a right decision from Linus to isolate, focus and work
> solely on kernel and not including everything else (like FreeBSD does)
> that makes a usable system.
Just a little sidenote:
Plan9 uses a trimmed-down Kernel as bootloader, which gives interesting
opportunities (eg. using various services like filesystems, shells, etc
in the bootloader).
With modern bootloaders like Barebox, the need for that IMHO isn't
that huge anymore. OTOH, there're still several things, I'd wish to
have available in the bootloader (eg. iscsi- or bnlkdev support).
Anyone here, who uses a Linux kernel as bootloader / preboot
environment ?
cu
--
Enrico Weigelt, metux IT consult
+49-151-27565287
MELAG Medizintechnik oHG Sitz Berlin Registergericht AG Charlottenburg HRA 21333 B
Wichtiger Hinweis: Diese Nachricht kann vertrauliche oder nur für einen begrenzten Personenkreis bestimmte Informationen enthalten. Sie ist ausschließlich für denjenigen bestimmt, an den sie gerichtet worden ist. Wenn Sie nicht der Adressat dieser E-Mail sind, dürfen Sie diese nicht kopieren, weiterleiten, weitergeben oder sie ganz oder teilweise in irgendeiner Weise nutzen. Sollten Sie diese E-Mail irrtümlich erhalten haben, so benachrichtigen Sie bitte den Absender, indem Sie auf diese Nachricht antworten. Bitte löschen Sie in diesem Fall diese Nachricht und alle Anhänge, ohne eine Kopie zu behalten.
Important Notice: This message may contain confidential or privileged information. It is intended only for the person it was addressed to. If you are not the intended recipient of this email you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you received this email in error please notify the sender by replying and delete this message and any attachments without retaining a copy.
next prev parent reply other threads:[~2015-05-12 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 15:12 boot loader Thiago Farina
2015-04-28 21:49 ` Richard Weinberger
2015-04-28 23:44 ` Thiago Farina
2015-04-29 2:17 ` Ken Moffat
2015-04-29 8:28 ` Geert Uytterhoeven
2015-05-11 22:11 ` Pavel Machek
2015-05-12 0:17 ` Thiago Farina
2015-05-12 11:11 ` Enrico Weigelt, metux IT consult [this message]
2015-05-13 7:02 ` Pavel Machek
2015-05-13 7:53 ` Enrico Weigelt, metux IT consult
2015-05-13 7:56 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5551DFDE.6040905@melag.de \
--to=weigelt@melag.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tfransosi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox