Re: patches not acted upon

OK, thanks for evaluating them, worthy or not. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel

patches not acted upon

I sent patches etc. last month, Subjects: [PATCH] grub-install message should mention --recheck [semi-PATCH] grub.texi: emergency booting without root passwd cmdline.c: ESC at any time exits: only mentioned once but nobody acted on them one way or the other

Re: [PATCH] menu.c clearer instructions

JY> Committed a variant of this patch into the repository. OK, thanks. Say, three semi-patches of mine remain to be resolved. Their subjects were: [PATCH] grub-install message should mention --recheck [semi-PATCH] grub.texi: emergency booting without root passwd cmdline.c: ESC at any time exits: o

Re: [PATCH] menu.c clearer instructions

> "JY" == Jerone Young writes: JY> I'll track your patches. Thanks! JY> What other patches where you going to submit like this? There is a total of four issues, [PATCH] grub-install message should mention --recheck [PATCH] menu.c clearer instructions [semi-PATCH] grub.texi: emergency booting w

Re: [PATCH] menu.c clearer instructions

>>>>> "j" == jidanni writes: j> OK, Pavel Roskin's suggestions sound great. I leave this in your hands. However, will these patches I sent this week be used, or slowly forgotten ? ___ Grub-deve

Re: [PATCH] grub-install message should mention --recheck

All I know is the day I discovered --recheck, I kicked myself for doing it by hand for a month because the message didn't alert me. Do mention it one way or another. OK, I leave this in your hands. ___ Grub-devel mailing list Grub-devel@gnu.org http://l

Re: [PATCH] menu.c clearer instructions

OK, Pavel Roskin's suggestions sound great. I leave this in your hands. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [PATCH] menu.c clearer instructions

2008-12-27 jida...@jidanni.org * normal/menu.c: print clearer instructions on the screen --- menuORIG.c 2008-12-27 02:42:57.0 +0800 +++ menu.c 2008-12-27 02:53:49.0 +0800 @@ -82,8 +82,8 @@ { grub_printf ("\n\ Minimum Emacs-like screen editing is su

[PATCH] grub-install message should mention --recheck

*** grub-installORIG.in 2008-12-27 02:43:09.0 +0800 --- grub-install.in 2008-12-27 04:06:02.0 +0800 *** *** 304,310 # Prompt the user to check if the device map is correct. ! echo "Installation finished. No error reported." ! echo "This is the contents of the

cmdline.c: ESC at any time exits: only mentioned once

Gentlemen, there is a serious usability problem with cmdline.c. At the very start the user sees the message made by grub_printf ("\ [ Minimal BASH-like line editing is supported. For the first word, TAB\n\ lists possible command completions. Anywhere else TAB lists possible\n\ device/fil

[semi-PATCH] grub.texi: emergency booting without root passwd

Please add this somewhere you feel comfortable with in grub.texi. I looked, but cannot find the right place. Thank you. @Chapter Tips @node Forgot the root password One place when grub can come in very handy is when one forgot the root password, and hence cannot boot or even shutdown the system.

[PATCH] menu.c clearer instructions

diff -C 1 menuO*.c menu.c *** menuORIG.c 2008-12-27 02:42:57.0 +0800 --- menu.c 2008-12-27 02:53:49.0 +0800 *** *** 84,87 Minimum Emacs-like screen editing is supported. TAB lists\n\ ! available completions. Press C-x (\'x\' with Ctrl) to boot,\n

Re: too many commands, "help" output rolls of screen

MS> This is another instance ware mouse support would be useful: you MS> could use the scrollbar directly (by clicking on it), Scrollbar... mouse... next thing you know you'll be implementing javascript. One or two are OK, but if this trend continues don't blame me if one day you can't properly bo

Re: grub-install message should mention --recheck

ID> try `grub-install --recheck` (or is it `grub-install --recheck Thanks. I am trying to say that four out of five times "adding --recheck to the invocation" will do what the user wants, instead of needing him to fire up an editor. So please mention it somehow. _

Re: forgot passwd, cannot login, [rd]init=/bin/sh don't work

Can somebody please integrate my patches? For the parent article and the "grub-install message should mention --recheck" article. I am a mere "apt-get install" user. I fear if I learn your whole source code system, and finally make an official patch, it too will fall on deaf ears. As I expect I w

Re: forgot passwd, cannot login, [rd]init=/bin/sh don't work

Ah, no wonder. These need rewording: Use the %C and %C keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting or 'c' for a command-line. Minimum Emacs-like screen editing is supported. TAB lists available completions. Press C-x

grub-install message should mention --recheck

Please implement these changes in making this typical grub-install message. Thanks. # grub-install /dev/hda Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. -Check if this is correct or not. If any of the lines is incorrect,

Re: forgot passwd, cannot login, [rd]init=/bin/sh don't work

AW> If you have a LiveCD or recovery CD which many distros of linux have, then AW> boot under that. Then, when you are in the root shell, you can mount your AW> systems partition, and then you can use the command chroot AW> . That will make the live cd use AW> your systems file system. Then simply

forgot passwd, cannot login, [rd]init=/bin/sh don't work

Gentlemen, last time I forgot my password and couldn't log into my machine here on my far away rural mountaintop, I ended up digging up an old Debian "potato" CDROM and installing it into some free space on my disk, from which I could edit /etc/passwd and zero out the password. These days that woul

too many commands, "help" output rolls of screen

The top two lines of grub> help output will roll off the standard sized console. Please remove some commands so there aren't so many that they roll off the screen. Actually just please use more columns on some of the help lines. (Yes, TAB reveals the missing commands.) P.S., What if I forget my p

say how to get out of grub-emu

On the grub-emu man page please mention the only way to get back out of grub-emu is to use its "reboot" command, adding that it will return you to the shell and not really reboot. By the way, is the bug address on the man pages updated to [EMAIL PROTECTED] Not on Debian's grub2 stuff. __

allow making no timeout

>From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497085 I assume this is an upstream problem. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel

man pages' NAME section wrong

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496706 and say if this is an upstream bug or not. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel

debian upstream bugs

Gentlemen, I submitted some what I thought were downstream bugs: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=grub-pc;[EMAIL PROTECTED] ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel