public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] borked release media
Date: Sun, 9 Dec 2012 10:59:46 -0800	[thread overview]
Message-ID: <20121209185946.GB6595@kroah.com> (raw)
In-Reply-To: <CAGfcS_kMi1VbnMOmd-GzcfQeN9xMSf+i5J1_QK=sgBcD1pRsgg@mail.gmail.com>

On Sun, Dec 09, 2012 at 01:35:57PM -0500, Rich Freeman wrote:
> On Sun, Dec 9, 2012 at 1:24 PM, Greg KH <gregkh@gentoo.org> wrote:
> >
> > The FSF has already said that using Grub2 and the GPLv3 is just fine
> > with the UEFI method of booting, so there is no problem from that side.
> > There's a statement about this somewhere on their site if you are
> > curious.
> >
> > The only one objecting to GPLv3 and UEFI is the current rules for
> > getting a shim/bootloader signed by Microsoft, but the current
> > implementations we have all have either a GPLv2 or BSD licensed shim
> > which then loads GRUB, so all is fine from a licensing and legal
> > standpoint from everyone involved.
> 
> Makes sense to me, thanks.
> 
> An MS-signed bootloader isn't nearly as critical for Gentoo as it is
> for other distros - we're not really aiming for the
> stick-a-CD-in-and-you're-done  crowd.  If somebody can partition their
> drive, build and install a kernel and grub, configure make.conf, and
> build a system, then I'm not too concerned that they have to run some
> script to generate a key, sign their bootloader, and register that key
> with their firmware, or disable secure boot just to boot the install
> CD (though it sounds like some firmwares just pop up a warning and let
> you proceed, which is what my Chromebook does in dev mode).

The UEFI spec does not allow that mode of operation in secure boot mode,
sorry. You will have to disable it in order to boot a Gentoo image,
which is fine, but there's no reason why Gentoo can't use the MS-signed
shim bootloader like all other distros are using, right?

thanks,

greg k-h


  reply	other threads:[~2012-12-09 18:58 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09 18:07 [gentoo-dev] borked release media Fernando Reyes
2012-12-09 18:13 ` Rich Freeman
2012-12-09 18:24   ` Greg KH
2012-12-09 18:35     ` Rich Freeman
2012-12-09 18:59       ` Greg KH [this message]
2012-12-10  0:24         ` Diego Elio Pettenò
2012-12-10  0:52           ` Rich Freeman
2012-12-10  0:57             ` Diego Elio Pettenò
2012-12-10  1:08               ` Rich Freeman
2012-12-10  2:37                 ` Greg KH
2012-12-10 15:31                   ` Walter Dnes
2012-12-10 18:36                     ` Greg KH
2012-12-10 20:25                       ` Maxim Kammerer
2012-12-10  2:35             ` Greg KH
2012-12-10 12:55             ` Maxim Kammerer
2012-12-10  2:34           ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2012-12-09 18:42 Fernando Reyes
2012-12-09 17:23 Fernando Reyes
2012-12-09 17:45 ` Rich Freeman
2012-12-09 18:46 ` Chí-Thanh Christopher Nguyễn
2012-12-09 18:57   ` Greg KH
2012-12-09 23:21     ` Chí-Thanh Christopher Nguyễn
2012-12-10  2:38       ` Greg KH
2012-12-10 12:53         ` Chí-Thanh Christopher Nguyễn
2012-12-09 20:26   ` likewhoa
2012-12-09 23:21     ` Chí-Thanh Christopher Nguyễn
2012-12-09  5:29 Fernando Reyes
2012-12-09 14:50 ` Chí-Thanh Christopher Nguyễn
2012-12-09  4:57 Fernando Reyes
2012-12-09  5:04 ` Peter Stuge
2012-12-09  9:18   ` Markos Chandras
2012-12-09  9:40     ` Maxim Kammerer
2012-12-09 14:42   ` Chí-Thanh Christopher Nguyễn
2012-12-10  1:07     ` Peter Stuge
2012-12-10 15:22 ` Walter Dnes
2012-12-08  4:55 "Paweł Hajdan, Jr."
2012-12-08  5:25 ` Matt Turner
2012-12-08 11:50   ` Rich Freeman
2012-12-08 16:31     ` Rick "Zero_Chaos" Farina
2012-12-08 16:47   ` Peter Stuge
2012-12-09  3:21 ` Walter Dnes

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=20121209185946.GB6595@kroah.com \
    --to=gregkh@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