Your message dated Sun, 17 Oct 2010 23:12:42 +0200
with message-id <[email protected]>
and subject line grub-script-check is now integrate with grub-mkconfig
has caused the Debian Bug report #572301,
regarding why not check for syntax errors BEFORE they lock one out of ones
computer
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
572301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572301
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
X-debbugs-cc: [email protected]
Package: grub-common
Version: 1.98~experimental.20100120-1
File: /usr/bin/grub-script-check
I have an idea, why not run grub-script-check when grub.cfg is made,
$ grub-script-check /boot/grub/grub.cfg; echo $?
syntax error
1
That way the user would be aware that if they just left things as they
are, he will be in for a unhappy surprise the next time he tries in vain
to boot his computer.
--- End Message ---
--- Begin Message ---
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature
--- End Message ---
