From: Phillip Susi <psusi@cfl.rr.com>
To: Colin Watson <cjwatson@ubuntu.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Guidance on conflicts between GNU GRUB and proprietary software
Date: Tue, 28 Sep 2010 13:52:21 -0400 [thread overview]
Message-ID: <4CA22B55.4040307@cfl.rr.com> (raw)
In-Reply-To: <20100928161811.GU21862@riva.ucam.org>
On 9/28/2010 12:18 PM, Colin Watson wrote:
> This is not true. GRUB has an ata module which can be built into
> core.img if necessary to read data from parts of the disk the BIOS can't
> read. It's not really solid enough to use by default, but people do
> occasionally report success with it.
But when it isn't done by default, or automatically when needed, then
you aren't any better off putting the core in the embed area by default.
If they are smart enough to build a custom core with the ata driver,
surely they can also put the core in the embed area as well.
To put that another way, just because an ata core needs to be in the
embed area to get around broken bios, does not mean that a biosdisk core
does.
next prev parent reply other threads:[~2010-09-28 17:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 22:19 Guidance on conflicts between GNU GRUB and proprietary software Colin Watson
2010-09-24 0:27 ` Lennart Sorensen
2010-09-24 14:09 ` Richard Stallman
2010-09-28 4:44 ` richardvoigt
2010-09-28 4:55 ` Bogdan
2010-09-28 8:04 ` Colin Watson
2010-09-28 9:10 ` Bogdan
2010-09-28 9:41 ` Colin Watson
2010-09-28 9:51 ` Bogdan
2010-09-28 10:25 ` Colin Watson
2010-09-28 10:40 ` Bogdan
2010-09-28 11:49 ` Colin Watson
2010-09-28 14:50 ` Lennart Sorensen
2010-09-28 15:05 ` Bogdan
2010-09-28 18:18 ` Grub2 Install Image Dee Sharpe
2010-09-28 21:45 ` Dmitry Ilyin
2010-09-28 15:40 ` Guidance on conflicts between GNU GRUB and proprietary software Phillip Susi
2010-09-28 16:18 ` Colin Watson
2010-09-28 17:52 ` Phillip Susi [this message]
2010-09-28 19:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 19:15 ` Lennart Sorensen
2010-09-28 19:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 20:07 ` Lennart Sorensen
2010-09-28 20:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 21:15 ` Lennart Sorensen
2010-09-28 21:34 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 19:22 ` Phillip Susi
2010-09-28 21:46 ` Grégoire Sutre
2010-09-28 22:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-29 10:00 ` Grégoire Sutre
2010-09-28 19:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 14:57 ` Lennart Sorensen
2010-09-28 9:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-24 10:57 ` Brendan Trotter
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=4CA22B55.4040307@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=cjwatson@ubuntu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).