From: Serbinenko Vova <serbinenko.vova@list.ru>
To: grub-devel@gnu.org
Subject: Re: Grub-devel Digest, Vol 11, Issue 11
Date: Wed, 12 Jan 2005 18:58:46 +0100 [thread overview]
Message-ID: <41E56556.7030409@list.ru> (raw)
In-Reply-To: <E1ColkE-000IdS-00.grub-devel-bounces+serbinenko-vova=list-ru-gnu-org@mx10.mail.ru>
>Date: Wed, 12 Jan 2005 11:44:24 +0200 (EET)
>From: Aki Tossavainen <cmouse@desteem.org>
>Subject: Feature suggestion to grub
>To: grub-devel@gnu.org
>Message-ID: <Pine.LNX.4.58.0501121144040.9263@youzen.ext.b2.fi>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>This is something I've been wondering a while, but would it be possible to
>build a "failsafe" system for grub which would work as follows:
>
>When grub loads an image and starts it, it'll write into a well-known
>location value (say: 0), which means that the boot has not succeeded. Then
>the booted system could write using a tool into the same location a value
>(say: 1), which means that the boot succeeded. If the computer is booted
>before the value has been changed, grub would choose next option or
>failsafe
>option to boot.
>
>Does this sound like something that could be made?
>
>---------------
>Aki Tossavainen
>cmouse@desteem.org
>
>
>
Now I'm writing script engine. In beta version(probably as plans are not
yet fixed) after I'll write hooks and arrays support. I'll write the
savedvars module (variables saved in file) and small C-tool to modify it
from OS. You'll be able to use it to do so. Soon(I think Sunday) I'll
mail my first(pre-alpha I suppose) version and we'll discuss about
priorities for future versions
-------------
Vladimir Serbinenko
serbinenko.vova@list.ru
vovas at irc.gnu.org#grub
parent reply other threads:[~2005-01-12 18:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1ColkE-000IdS-00.grub-devel-bounces+serbinenko-vova=list-ru-gnu-org@mx10.mail.ru>]
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=41E56556.7030409@list.ru \
--to=serbinenko.vova@list.ru \
--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.