[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: grub-mkconfig fails on every non i386-pc because of gfxterm/vbe

From: Robert Millan
Subject: Re: grub-mkconfig fails on every non i386-pc because of gfxterm/vbe
Date: Wed, 19 Aug 2009 17:18:21 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Tue, Aug 18, 2009 at 07:53:30PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> >
> > I'm sorry, I'm very busy these days.  I don't know what message you are
> > talking about, but I still have a lot of mail to read.
> >
> > I don't insist on changing the default, as long as GRUB behaves
> > correctly.  I have verified that setting GRUB_TERMINAL_OUTPUT=console
> > in /usr/local/etc/default/grub would disable gfxterm, and that should be
> > OK.
> Why not to change default to use console? I understand that distros
> may want background image or other beatiful stuff but IMO mainstream
> should remain simple and reliable and in this case using gfxterm at
> least on some console is less reliable than old and proven console
> approach. I'm ok with providing an option to choose gfxterm but I
> don't see why it would be default in mainstream

The eye candy is nice but not so important.  For me, gfxterm should be
default on platforms where it's available, because it implements UTF-8,
which is necessary to support l10n.

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 via email to

[Prev in Thread] Current Thread [Next in Thread]