From: Andy Goth <unununium@aircanopy.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: too many commands, "help" output rolls of screen
Date: Mon, 6 Oct 2008 17:00:58 -0500 (CDT) [thread overview]
Message-ID: <1920677820.63551223330458704.JavaMail.root@aczmb1> (raw)
In-Reply-To: <87y711o7z5.fsf@jidanni.org>
jidanni@jidanni.org wrote:
> 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.
You should be able to remove testing commands (like "hello" and "play") from the build. At the moment I don't have the ability to research how.
I recently found a related problem that I'll post more information on after doing some research. It's the opposite issue: scrolling doesn't always happen when I want it to.
> P.S., What if I forget my password and I cannot login to my machine?
Presuming Linux, you can add "init=/bin/sh" to the kernel command line. This will give you a shell without asking for a password. From this shell you can edit your password file.
I sometimes use this trick to give myself an account. :^) Seriously, if you don't password-protect your GRUB or LILO prompt (or anything else that edits the kernel command line), your system is open to anyone who has access to the keyboard. Then again, unless you take extraordinary measures, your system is open to anyone with a screwdriver and physical access to the machine.
Warning 1: If support for your keyboard isn't compiled into the kernel, you won't be able to type, since the init scripts (which would load modules and do other configuration) will be bypassed. I suggest using a PS/2 keyboard in this case.
Warning 2: You won't have job control, so Ctrl-C and so on won't work. Issue a command that takes a long time to complete, and you will have to wait. Issue a command that never completes, and you will have to reboot. I suggest running screen so as to give yourself a workaround.
Warning 3: The root filesystem might be mounted read-only. Test this by using touch to create a file, then use ls to see if the file was created. If not, type "mount" to get a listing of filesystems, then remount / with the device name taken from mount's output and the -oremount,rw option. Or add "rw" to the kernel command line, removing "ro" if it is present.
Warning 4: Initrd scripts might change everything.
> Could you supply ed(1) in the commands perhaps?
I could be wrong, but I don't think grub was, is, or ever will be meant to modify filesystems. Oh wait, I think it can be configured to remember the selected menu item as a new default, but I don't know how that's implemented.
--
Andy Goth | http://andy.junkdrome.org/
unununium@{aircanopy.net,openverse.com}
next prev parent reply other threads:[~2008-10-06 22:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 19:10 too many commands, "help" output rolls of screen jidanni
2008-10-06 22:00 ` Andy Goth [this message]
2008-11-01 12:46 ` Robert Millan
2008-11-02 17:07 ` Jordi Mallach
2008-11-02 18:41 ` pager=1 as default? (Re: too many commands, "help" output rolls of screen) Robert Millan
2008-11-03 4:57 ` peter cros
2008-11-04 15:47 ` Yoshinori K. Okuji
2008-11-03 9:01 ` too many commands, "help" output rolls of screen Matt Sturgeon
2008-11-03 11:45 ` Robert Millan
2008-11-04 20:59 ` jidanni
2008-11-04 21:34 ` Robert Millan
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=1920677820.63551223330458704.JavaMail.root@aczmb1 \
--to=unununium@aircanopy.net \
--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.