From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1I1EI1-0006z3-HL for mharc-grub-devel@gnu.org; Thu, 21 Jun 2007 00:29:01 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I1EI0-0006yo-8i for grub-devel@gnu.org; Thu, 21 Jun 2007 00:29:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I1EHu-0006xX-G3 for grub-devel@gnu.org; Thu, 21 Jun 2007 00:28:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I1EHu-0006xT-9n for grub-devel@gnu.org; Thu, 21 Jun 2007 00:28:54 -0400 Received: from ug-out-1314.google.com ([66.249.92.173]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I1EHq-0001i0-Em for grub-devel@gnu.org; Thu, 21 Jun 2007 00:28:52 -0400 Received: by ug-out-1314.google.com with SMTP id 34so558432ugf for ; Wed, 20 Jun 2007 21:28:21 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=nS8XzoTsdQdmPc6+A3b5raDTyXfpJyRG+T5BBlns9aimSQZBqPZYqfQfjVt8gFDvEZ7xAPu5TYxdx5/6Y6yTDpp3/fLkjjQL3vwchVu7XhggHIKDJVP8oSJ8uu1fjYVC2wnZ2zqyyBMK2wK2XbvhsjDAmcToRqDqnztEeJqN93E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=ia333JUHEiF582QblFFDS6TIaSlxjHVJBxlBUMmEElqEt82ZHl2mSoHXy/TXMfc+wZ6XhUDzvx0AOR/vMbcU22s5Gi9Zi3afnGeq+7lWUbEp+YyxqIpBNdGd7ayQCo7UU/2h5R17WtXW64CgCLBixWOSuyIqn7oLt6BO8YGP5gQ= Received: by 10.67.92.9 with SMTP id u9mr1763167ugl.1182400101553; Wed, 20 Jun 2007 21:28:21 -0700 (PDT) Received: from ?87.103.180.35? ( [87.103.180.35]) by mx.google.com with ESMTP id j3sm1744157ugd.2007.06.20.21.28.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 20 Jun 2007 21:28:20 -0700 (PDT) Message-ID: <4679FE60.8070906@gmail.com> Date: Thu, 21 Jun 2007 11:28:16 +0700 From: Mikhail Vorozhtsov User-Agent: Mozilla-Thunderbird 2.0.0.0 (X11/20070601) MIME-Version: 1.0 To: The development of GRUB 2 References: <4678D87D.7040700@gmail.com> <87abuuhmhp.fsf@xs4all.nl> In-Reply-To: <87abuuhmhp.fsf@xs4all.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-detected-kernel: Linux 2.4-2.6 (Google crawlbot) Subject: Re: Multiboot overhaul X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2007 04:29:00 -0000 Marco Gerards wrote: > Mikhail Vorozhtsov 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. Of course, posting the patch was just the shortest way to show people the idea. Otherwise it would've taken many lines of text to describe everything. > 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? Yes, but I think my solution is too different from multiboot to be merged with it. It's just two ways of doing things, both of them will work. To say the truth, if I had found multiboot2 implemented I would've just started to using it. But I didn't, so I said to myself "Let's design a loading scheme, it should be fun" :)