From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: About firmware facilities
Date: Mon, 14 Sep 2009 15:11:37 -0400 [thread overview]
Message-ID: <1252955497.4336.5.camel@mj> (raw)
In-Reply-To: <b1ebdcad0909141157p5d4fb743o14b807f56b35b3d8@mail.gmail.com>
On Tue, 2009-09-15 at 04:27 +0930, Brendan Trotter wrote:
> Hi,
>
> On Tue, Sep 15, 2009 at 1:02 AM, Robert Millan <rmh@aybabtu.com> wrote:
> > Well, you have the freedom to disagree with anything we do and bring your
> > customized GRUB to a different direction :-)
> >
> > Anyhow, my priority for GRUB is strong driver-based support. We could recruit
> > someone to develop the framework in next year's GSoC (unless somebody steps
> > in, of course).
>
> Why stop there?
>
> If proprietory ethernet ROMs aren't good enough, then what about
> proprietory SCSI ROMs, and proprietory firmware/BIOS?
We are already doing it. There is functional ATA support, USB support
is under development. GRUB can serve as BIOS together with Coreboot.
> Surely a boot manager wouldn't be a good manager if it didn't include
> it's own replacements for all of these things; and perhaps it should
> also include it's own replacement for proprietory OS's too...
>
> Why are you worrying about such silly things when the multi-boot
> specification (which actually is relevant) is still severely borked?
Patches are welcome.
> > The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
> > how) you may access your data; but nobody's threatening your freedom: we
> > still allow you to remove your data and not access it at all."
>
> Sigh. I think I understand now - lack of logical thinking leads to
> lack of rational behavior.
Ad hominem arguments are not welcome here.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-09-14 19:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 14:07 PXEgrub development on grub2 Lars Nooden
2009-09-09 14:11 ` Felix Zielcke
2009-09-09 14:13 ` Lars Nooden
2009-09-09 15:04 ` Michal Suchanek
2009-09-09 19:40 ` Seth Goldberg
2009-09-10 12:39 ` Michal Suchanek
2009-09-10 13:01 ` Felix Zielcke
2009-09-10 21:17 ` Seth Goldberg
2009-09-11 13:17 ` Robert Millan
2009-09-11 21:07 ` Seth Goldberg
2009-09-12 0:05 ` Michal Suchanek
2009-09-12 0:20 ` Seth Goldberg
2009-09-12 12:54 ` About firmware facilities Robert Millan
2009-09-13 20:54 ` Seth Goldberg
2009-09-14 15:32 ` Robert Millan
2009-09-14 18:57 ` Brendan Trotter
2009-09-14 19:11 ` Pavel Roskin [this message]
2009-09-14 20:12 ` Brendan Trotter
2009-09-14 20:47 ` Michal Suchanek
2009-09-14 20:49 ` Vladimir 'phcoder' Serbinenko
2009-09-14 23:23 ` Brendan Trotter
2009-09-14 23:43 ` Colin Watson
2009-09-14 23:56 ` Brendan Trotter
2009-09-15 0:28 ` Colin Watson
2009-09-15 1:06 ` Brendan Trotter
2009-09-15 8:59 ` Vladimir 'phcoder' Serbinenko
2009-09-15 16:01 ` Brendan Trotter
2009-09-19 14:06 ` Vladimir 'phcoder' Serbinenko
2009-09-20 9:04 ` Brendan Trotter
2009-09-20 10:38 ` Vladimir 'phcoder' Serbinenko
2009-09-19 21:07 ` Robert Millan
2009-09-10 18:59 ` PXEgrub development on grub2 Robert Millan
2009-09-17 22:39 ` Joey Korkames
2009-09-18 6:19 ` Vladimir 'phcoder' Serbinenko
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=1252955497.4336.5.camel@mj \
--to=proski@gnu.org \
--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.