All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Next release?
Date: Thu, 24 Jul 2008 13:18:43 -0400	[thread overview]
Message-ID: <1216919923.22586.29.camel@dv> (raw)
In-Reply-To: <871w1jrz9u.fsf@xs4all.nl>

On Thu, 2008-07-24 at 19:02 +0200, Marco Gerards wrote:
> Hi,
> 
> Pavel Roskin <proski@gnu.org> writes:
> 
> > Now that we have lzma compression, we should probably consider making
> > another release in a week or two.
> >
> > Before it happens, I'd like to add a configure test for working target
> > compiler, so that users of pure x86_64 machines are not surprised by a
> > message that "start" and "_start" are not found.

Done.

> > By the way, that check could be generalized to allow more symbols, such
> > as "Ltext0" on Cygwin.  It would be great if GRUB 1.97 compiled on
> > Cygwin out-of-box.  Cygwin lacked some lzo development files, but we
> > don't need them anymore.

I was wrong here, but the progress is being made.  I'm just not sure it
should be in 1.97.

> > All warnings for i386-pc have been fixed, but perhaps I'll look at other
> > targets if I have time.  Also, Valgrind finds some memory leaks, that we
> > may want to fix now.

The absolute majority of warnings have been fixed, including all for
i386-pc.  There are some hard warnings for other architectures.  The can
be suppressed, but they indicate that we need e.g. some reorganization
of the include files.  So it's better to keep them for now.

I was unable to check sparc64-ieee1275.  I'm afraid it's broken.  I
don't have hardware to test it on, but the real problem is lack of time.
But with x86_64-efi, I guess most issues with 64-bit bootloaders have
been resolved.

> Did all this happen?  Is NEWS and distlist and whatever is required
> for a release up-to-date?  In that case, Okuji, do you object to a
> release?
> 
> Bean suggested we release before we continue with his ideas regarding
> the modularity of the code.  Okuji (and others), can you please review
> the patch I sent in for handlers in the thread related to the
> elimination of normal mode?

We need at least a simple fix for cross-drive installs.  Perhaps we need
a PC specific function to translate device names like hd1 into BIOS IDs
like 0x81.

Also it would be nice to make grub-install ask users to check only
relevant entries from device map.  By showing the whole file, the risk
is that everybody would just ignore the message.  I think grub-setup
should have a "semi-verbose" mode, in which it would print something
like:

device.map: /dev/sda is (hd0)

And then grub-setup would ask the user to verify those assumptions.

We can make a more fundamental fix later, unless it's already
implemented, tested and meets no objections.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-07-24 17:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 13:03 Next release? Pavel Roskin
2008-07-14 16:55 ` Christian Franke
2008-07-14 20:27   ` Pavel Roskin
2008-07-15  5:40     ` Christian Franke
2008-07-20 21:10     ` Christian Franke
2008-07-15 13:49   ` Robert Millan
2008-07-15 15:07     ` Patrick Georgi
2008-07-15 18:39       ` Christian Franke
2008-07-15 18:32     ` Christian Franke
2008-07-15 21:04 ` Yoshinori K. Okuji
2008-07-15 22:31   ` Pavel Roskin
2008-07-15 23:15     ` Yoshinori K. Okuji
2008-07-15 23:21       ` Pavel Roskin
2008-07-15 23:32         ` Yoshinori K. Okuji
2008-07-15 23:52           ` Pavel Roskin
2008-07-16 14:11             ` Colin D Bennett
2008-07-16 14:17               ` Javier Martín
2008-07-16 16:17                 ` Pavel Roskin
2008-07-16 16:28                   ` Javier Martín
2008-07-16 16:08               ` Pavel Roskin
2008-07-19 15:14                 ` device.map (Re: Next release?) Robert Millan
2008-07-21 21:26                   ` Pavel Roskin
2008-07-22 21:36                     ` Robert Millan
2008-07-22 21:57                       ` Pavel Roskin
2008-07-22 22:08                         ` Robert Millan
2008-07-22 22:46                           ` Pavel Roskin
2008-07-19 15:06           ` Next release? Robert Millan
2008-07-19 20:16             ` Yoshinori K. Okuji
2008-07-19 20:59               ` Robert Millan
2008-07-21 20:48               ` Pavel Roskin
2008-07-22 21:37                 ` Robert Millan
2008-07-22 22:01                   ` Pavel Roskin
2008-07-22 22:09                     ` Robert Millan
2008-07-22 22:41                       ` Pavel Roskin
2008-07-24 17:02 ` Marco Gerards
2008-07-24 17:18   ` Pavel Roskin [this message]
2008-07-24 21:47     ` Christian Franke
  -- strict thread matches above, loose matches on Subject: below --
2008-07-16  0:22 chaac

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=1216919923.22586.29.camel@dv \
    --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.