From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: How do I boot a standalone program in grub (a password checker via serial input) before allowing grub to continue booting?
Date: Sat, 10 Nov 2007 17:13:51 +0100 [thread overview]
Message-ID: <87ejeygjsw.fsf@xs4all.nl> (raw)
In-Reply-To: <13554502.post@talk.nabble.com> (misfitsskatermonkey@yahoo.com's message of "Sat, 3 Nov 2007 09:58:37 -0700 (PDT)")
CurlyCoconutTree <misfitsskatermonkey@yahoo.com> writes:
> How do I boot a standalone program in grub (1.95) (a password checker via
> serial input) before allowing grub to continue booting? I'm trying to
> develop a program that will run, stand alone or with the libraries Grub
> gives me access to, parse serial data for a password, store the password to
> the MBR, then if valid return to Grub to boot windows... I'm not looking for
> a solution, I'm just looking for a place to start! Grub, is pretty poorly
> documented and I wouldn't be posting this is there was more (or I could find
> more) info on how to develop for GRUB. I guess I'd be a 'noob'... I hate
> using that term... we all have to start from some where.
Noone is using that term. We also value good documentation and will
be very happy if you could work on that.
One way of doing this might be writing a new command. See
hello/hello.c as an example.
--
Marco
prev parent reply other threads:[~2007-11-10 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 16:58 How do I boot a standalone program in grub (a password checker via serial input) before allowing grub to continue booting? CurlyCoconutTree
2007-11-05 15:35 ` Robert Millan
2007-11-05 16:57 ` Andrei E. Warkentin
2007-11-07 20:13 ` Robert Millan
2007-11-05 20:45 ` Christopher Walker
2007-11-10 16:13 ` Marco Gerards [this message]
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=87ejeygjsw.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--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.