All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 2/2] Disable lzo compression, lzma is doing its job just fine
Date: Sat, 18 Jul 2009 20:18:21 +0200	[thread overview]
Message-ID: <20090718181821.GC8867@thorin> (raw)
In-Reply-To: <d7ead6de0907160924i4ed9f791q2905353794368de3@mail.gmail.com>

On Thu, Jul 16, 2009 at 06:24:14PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Thu, Jul 16, 2009 at 1:40 AM, Pavel Roskin<proski@gnu.org> wrote:
> > ChangeLog:
> >
> >        * Makefile.in: Remove LIBLZO and enable_lzo.
> >        * conf/i386-pc.rmk: Remove lzo support.
> >        * configure.ac: Remove checks for lzo, don't define ENABLE_LZMA.
> >        * include/grub/i386/pc/kernel.h: Define ENABLE_LZMA.  Remove lzo
> >        support.
> >        * kern/i386/pc/lzo1x.S: Remove.
> >        * kern/i386/pc/startup.S: Remove lzo support.
> >        * util/i386/pc/grub-mkimage.c: Likewise.
> Is there a reason to remove lzo? I know that lzma performs much better
> in terms of compression but afaik lzo doesn't create any problems nor
> is compiled by default

It doesn't break things, since it's barely modified, and doesn't interact with
the rest of the code, but simply having more code means an added work to
maintain it when we restructure things, etc.  It needs to pay off in some way.

> and may be desirable for some users

Can you give an example?

-- 
Robert Millan

  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."



  reply	other threads:[~2009-07-18 18:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 23:40 [PATCH 1/2] Introduce grub_malloc0() Pavel Roskin
2009-07-15 23:40 ` [PATCH 2/2] Disable lzo compression, lzma is doing its job just fine Pavel Roskin
2009-07-16 16:24   ` Vladimir 'phcoder' Serbinenko
2009-07-18 18:18     ` Robert Millan [this message]
2009-07-19 17:45       ` Pavel Roskin
2009-07-19 18:24         ` Vladimir 'phcoder' Serbinenko
2009-07-19 20:33           ` Pavel Roskin
2009-07-16 15:22 ` [PATCH 1/2] Introduce grub_malloc0() Vladimir 'phcoder' Serbinenko
2009-07-16 15:41   ` Pavel Roskin
2009-07-16 15:53     ` Vladimir 'phcoder' Serbinenko
2009-07-17 15:02       ` Pavel Roskin

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=20090718181821.GC8867@thorin \
    --to=rmh@aybabtu.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.