From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Gujin linux.kgz boot format
Date: Tue, 11 Oct 2005 04:35:06 +0900 [thread overview]
Message-ID: <diefs3$v2s$1@sea.gmane.org> (raw)
In-Reply-To: <3768.192.168.201.6.1128954688.squirrel@pc300>
Etienne Lorrain wrote:
>>>>It seems to work okay here. Now, rewriting current boot system into C
>>>>may be good goal...
>>>
>>> At least that is a way which does not involve modifying assembler
>>> files. Slowly everybody switches to the C version which continue
>>> to evolve (i.e. removing old BIOS calls), then the tree under
>>> arch/i386/boot is removed and we can begin to rearrange the mapping
>>> of "struct linux_param".
>>
>>Will your C version work with lilo and grub?
>
>
> Tricky question. In short no, it cannot.
[snip a long explaination of why this is practically impossible]
> Sorry I cannot be compatible with them, please note that
> Gujin is also GPL.
So you are saying: "Dump GRUB and lilo, use Gujin!" ??
I don't think anybody will agree with that even if it is a better way in some way.
Until some level of compatibility is guaranteed with the currently de facto loaders, at least I
cannot support this idea in any way. Discussing that with GRUB and lilo devs, might be an idea, but
who knows.
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
next prev parent reply other threads:[~2005-10-10 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 9:46 [PATCH 1/3] Gujin linux.kgz boot format Etienne Lorrain
2005-10-07 14:46 ` Pavel Machek
2005-10-10 11:23 ` Etienne Lorrain
2005-10-10 11:56 ` Pavel Machek
2005-10-10 13:09 ` Etienne Lorrain
2005-10-10 13:19 ` Pavel Machek
2005-10-10 14:31 ` Etienne Lorrain
2005-10-10 19:21 ` Pavel Machek
2005-10-10 19:35 ` Kalin KOZHUHAROV [this message]
2005-10-11 13:56 ` Denis Vlasenko
2005-10-11 15:23 ` Etienne Lorrain
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 13:39 Etienne Lorrain
2005-10-11 13:16 Etienne Lorrain
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='diefs3$v2s$1@sea.gmane.org' \
--to=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.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.