Bug#422794: Starting is impossible

Robert Millan rmh at aybabtu.com
Wed May 9 07:24:53 UTC 2007


clone 422794
retitle -1 gfxterm breaks boot
tags -1 moreinfo
thanks

Ok, this bug is for discussing customisation now.  For the boot problem,
please use the newly created one (Jonny, please answer my question about
boot failure there).

On Tue, May 08, 2007 at 05:22:43PM -0300, Otavio Salvador wrote:
> Robert Millan <rmh at aybabtu.com> writes:
> 
> >> Please do not perform update-grub compulsorily by postinst. It is very 
> >> unpleasant to overwrite grub.cfg freely.
> >
> > I suppose it doesn't harm to add an option to disable it; perhaps we could
> > even reuse /etc/kernel-img.conf.  Could you file a separate bug for this?
> 
> IMO, /etc/defaults/grub looks like a better place for this setting. We
> can source it and check for:
> 
> if [ "x$AUTORUN_UPDATE_GRUB" = "xyes" ]; then
>     ...
> fi

But that is an upstream file.  Do you think it's feasible to add a variable that
the upstream scripts don't use?

Also, after thinking about it, I'm concerned that if we allow disabling autorun
of update-grub, we won't be able to support changes in the grub.cfg
specification sanely (e.g. users will update grub without updating grub.cfg
and break their systems).  Also, we will receive less input from new features
that *are* intended to be default, and so have less chances to fix them if
they're buggy (like here).  And note that users are already able to add their
custom stuff via /etc/grub.d, just not remove the base lines.

I propose that we add a variable to select terminal, so that user can disable
this feature altogether if he wants.  Jonny, does that work for you?

-- 
Robert Millan

My spam trap is honeypot at aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.




More information about the Pkg-grub-devel mailing list