From: "Etienne Lorrain" <etienne.lorrain@masroudeau.com>
To: "Denis Vlasenko" <vda@ilport.com.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Gujin linux.kgz boot format
Date: Tue, 11 Oct 2005 16:23:21 +0100 (BST) [thread overview]
Message-ID: <4960.192.168.201.6.1129044201.squirrel@pc300> (raw)
In-Reply-To: <200510111656.30403.vda@ilport.com.ua>
Vda wrote:
>> This linux-*.kgz format is the "native" format of the Gujin
>> bootloader which can be found here:
>> http://gujin.org
>
> /me looking at the site
> Wow. Isn't this overdesigned by wide margin?
Well, you will see Gujin with its video/mouse interface on the WEB,
because there is no point in just showing the tiny interface which
does not even detect which video mode (or serial interface) is
available. For that just imagine two line of text, the first being
the copyright, the second a set of point indicating the progress
being done loading from BIOS or from DOS.
Now if you want to tell me that it is a lot easier to write code
using GCC compared to an assembler, well I quite agree. The source
code size is approx the same as Grub, with a lot less files.
It is also a lot simpler to use the BIOS than to rewrite everything
to be able to switch to protected mode.
> Apart from shaving a few kb's from kernel image (which are discarded
> anyway after boot, IIRC), what advantages does this bring?
> Do they outweigh effort needed to maintain it?
Don't you think autodetection of the ways to boot a PC is a nice
feature, so that you just have _one_ rescue CDROM/floppy/pen drive
from now on? Also you just test a new Linux distribution without
changing your current bootloader configuration? At least, you do
not end up having 3 or 4 Grub and two LILO configured in 6 different
root filesystems, some of them on removeable HD...
Moreover, there is no need to provide boot floppies to install
distributions on PC which cannot boot CDROMs, just give a way
to make a Gujin floppy. It will load big kernel directly from
the CDROM ISO9660 filesystem, in /boot directory.
Etienne.
next prev parent reply other threads:[~2005-10-11 15:23 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
2005-10-11 13:56 ` Denis Vlasenko
2005-10-11 15:23 ` Etienne Lorrain [this message]
-- 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=4960.192.168.201.6.1129044201.squirrel@pc300 \
--to=etienne.lorrain@masroudeau.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
/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