All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: initrd loading, max size, addr_min, and page_align
Date: Sun, 08 Feb 2015 22:04:27 -0600	[thread overview]
Message-ID: <54D831CB.2030606@gmail.com> (raw)
In-Reply-To: <20150209063050.3d64840f@opensuse.site>

Andrei Borzenkov wrote:
> В Sun, 08 Feb 2015 11:14:28 -0600
> Bruce Dubbs <bruce.dubbs@gmail.com> пишет:
>
>> Andrei Borzenkov wrote:
>>> В Thu, 5 Feb 2015 21:55:54 +0000 Eric Ewanco <Eric.Ewanco@genband.com>
>>> пишет:
>>>
>>>>
>>>> Background: I need to use a really large initrd for x86_64 (Linux 3.4.47),
>>>> and I'm near the limit, so I'm studying grub-core/loader/i386/linux.c to
>>>> find out the whys and wherefores of the GRUB 2.00 size limit.
>>>
>>> GRUB 2.00 is way too old.
>>
>> But as far as I know grub-2.00 is the last "stable" release.  There is the more
>> current grub-2.02~beta2 that was released over a year ago, but some people
>> prefer releases that upstream has designated as stable.
>>
>
> If you want to discuss a problem on development list, you should at
> least verify if this problem exists in current code.

I agree.

> In practice all ditros I'm aware of are using at least 2.02~beta2 or
> what effectively amounts to git snapshot.

Indeed.  We have gone to 2.02~beta2 also, although we prefer it when upstream 
labels a packages as stable.

>> Has grub gone to a policy of git snapshots only and forgone stable releases?
>>
>
> I do not think it is intentional.

There are several packages that do not release stable releases but only 
snapshots (but it is uncommon), however AFAIK grub is one of the very few active 
packages that does not seem to have a regularly scheduled release process.

It would actually help us if you just said that you are not going to designate 
stable, release candidate, beta, etc tarballs any more and it's up to the distro 
or individual to figure out what version to extract from version control.

   -- Bruce Dubbs
      LFS



  reply	other threads:[~2015-02-09  4:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 21:55 initrd loading, max size, addr_min, and page_align Eric Ewanco
2015-02-08 17:02 ` Andrei Borzenkov
2015-02-08 17:14   ` Bruce Dubbs
2015-02-09  3:30     ` Andrei Borzenkov
2015-02-09  4:04       ` Bruce Dubbs [this message]
2015-02-09 14:18       ` Eric Ewanco
2015-02-09  9:37     ` Michael Zimmermann

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=54D831CB.2030606@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=arvidjaar@gmail.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 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.