All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Multiboot overhaul
Date: Wed, 20 Jun 2007 13:52:02 +0200	[thread overview]
Message-ID: <87abuuhmhp.fsf@xs4all.nl> (raw)
In-Reply-To: <4678D87D.7040700@gmail.com> (Mikhail Vorozhtsov's message of "Wed, 20 Jun 2007 14:34:21 +0700")

Mikhail Vorozhtsov <mikhail.vorozhtsov@gmail.com> writes:

Hi,

> I'm working on a microkernel for x86_64 (with looking forward to ppc64
> and sparc64 ports). As you know, microkernels are quite useless without
> user-space servers that provide "classic" OS services. But microkernels
> are so useless that they even cannot load servers from disk :). That's
> why bootloader need to load servers images directly into memory in
> addition to image of microkernel itself. For i386-pc we have multiboot
> and it "just works". But it's really too i386-pc-specific. We also
> have draft of next multiboot version, but I think it still lacks
> flexibility (e.g. single 'flags' field for all image format, platform,
> and machine related features requests, no versioning). So I've
> implemented new loader (patch attached) focused on exensibility and
> versioning.

Feel free to give feedback on the next multiboot.  I think you
understand we can't just accept a loader for something that is not
discussed and most people are happy with.  What's on the wiki is the
result of discussion, but it is still open for discussion.  Did you
look at the information about this on the wiki?

So I really hope you are willing to participate in this discussion.
Feedback is welcome and so are patches that implement the final
outcome of multiboot2 for any platform supported by GRUB 2.

--
Marco




  reply	other threads:[~2007-06-20 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20  7:34 Multiboot overhaul Mikhail Vorozhtsov
2007-06-20 11:52 ` Marco Gerards [this message]
2007-06-21  4:28   ` Mikhail Vorozhtsov

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=87abuuhmhp.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --cc=grub-devel@gnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.