From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Implentation of password and lock commands
Date: Tue, 24 Jul 2007 16:09:43 +0200 [thread overview]
Message-ID: <20070724140943.GA24390@aragorn> (raw)
In-Reply-To: <46A51FC8.8050402@gmail.com>
On Mon, Jul 23, 2007 at 11:38:16PM +0200, Julien RANC wrote:
> Hi everyone,
>
> I am currently trying to get involved actively in the Grub 2
> development. I decided to start by (re)implementing the commands
> "password" and "lock" from Grub Legacy, that are currently missing in
> Grub 2.
>
> For now, I can successfully set a password in the grub.cfg file, read
> it, retrieve it, and block access to command line and edition mode until
> the password is verified. This seems to me a good start :)
>
> I hope I will have a first patch to propose in the weeks to come.
Nice. Perhaps you could send what you have now so that others (esp the
maintainers) can comment on it?
> As I
> am in the beginning of this implementation, I was wondering if there was
> anything more than what was implemented in Grub Legacy that was
> required, wished, or though about concerning this matter ? All comments
> and suggestions are indeed welcomed.
Debian has a list of things that are needed to replace GRUB Legacy as the
default bootloader:
http://wiki.debian.org/GrubTransition
There's also this command list comparison, which may provide some indication:
http://grub.enbug.org/CommandList
--
Robert Millan
My spam trap is honeypot@aybabtu.com. Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
next prev parent reply other threads:[~2007-07-24 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 14:02 Acer arcade instantOn and grub whites11
2007-07-23 21:38 ` Implentation of password and lock commands Julien RANC
2007-07-24 14:09 ` Robert Millan [this message]
2007-08-02 17:48 ` Acer arcade instantOn and grub adrian15
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=20070724140943.GA24390@aragorn \
--to=rmh@aybabtu.com \
--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.