public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Killing UEFI Secure Boot
Date: Thu, 21 Jun 2012 18:51:58 -0400	[thread overview]
Message-ID: <CAGfcS_kgPykciFouchNo0jmBe2dRuZKF7476sJJB4JhfH3VkgQ@mail.gmail.com> (raw)
In-Reply-To: <20120621191009.662.qmail@stuge.se>

On Thu, Jun 21, 2012 at 3:10 PM, Peter Stuge <peter@stuge.se> wrote:
> Roy Bamford wrote:
>
>> So when you build a dud kernel and flash your BIOS with it, and we
>> all build the odd dud, your motherboard is bricked.
>
> Any firmware modification has potential to brick, and shouldn't be
> done unless you are comfortable with the modification, or with
> solving a brick problem. :)

So, why are we still going back and forth about this?  If people want
to work on coreboot they can do so (I'm sure they have a list).  If
people want to fork coreboot or redo it from scrach they can do so and
start their own list.

When it is shiny and perfect and has a following of hundreds of linux
users we can always discuss whether we recommend using it in the
handbook on -dev then.  Otherwise it seems about as on-topic as
debating whether grub or systemd or openrc should have feature A/B/C -
we're a DISTRO - we integrate and ship what upstream gives us...

Rich



  reply	other threads:[~2012-06-21 22:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 22:11 [gentoo-dev] Killing UEFI Secure Boot Richard Yao
2012-06-20  0:22 ` Rich Freeman
2012-06-20  1:10   ` Richard Yao
2012-06-20  1:25     ` Rich Freeman
2012-06-20  1:33       ` Richard Yao
2012-06-20  1:51         ` Rich Freeman
2012-06-20  3:27     ` Peter Stuge
     [not found]     ` <1a28c6af40914cf5b6b5559bd0195a1b@HUBCAS1.cs.stonybrook.edu>
2012-06-20 22:16       ` Richard Yao
2012-06-21  8:08         ` [gentoo-dev] " Duncan
2012-06-21  9:33           ` Richard Yao
2012-06-21 15:00             ` Ian Stakenvicius
2012-06-21 15:05               ` Richard Yao
2012-06-21 18:55                 ` Roy Bamford
2012-06-21 19:10                   ` Peter Stuge
2012-06-21 22:51                     ` Rich Freeman [this message]
     [not found]                     ` <2279549d74ab41acb17b7207aa1478f6@HUBCAS2.cs.stonybrook.edu>
2012-06-22  0:24                       ` Richard Yao
2012-06-22 13:02                         ` Ian Stakenvicius
2012-06-22  5:02             ` Duncan
2012-06-22  5:10               ` Richard Yao
2012-06-22  5:30                 ` Richard Yao
2012-06-20 20:08 ` [gentoo-dev] " Greg KH
2012-06-20 20:13   ` Richard Yao
2012-06-20 20:20     ` Greg KH
2012-06-20 20:35       ` Richard Yao
2012-06-20 21:09         ` Greg KH
     [not found]         ` <01ed9c34e80e4f66b9f5c9fbcdede39e@HUBCAS2.cs.stonybrook.edu>
2012-06-20 21:56           ` Richard Yao
2012-06-20 22:27             ` Greg KH

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=CAGfcS_kgPykciFouchNo0jmBe2dRuZKF7476sJJB4JhfH3VkgQ@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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