From: adrian15 <adrian15@raulete.net>
To: grub-devel@gnu.org
Subject: grub2 file browser draft
Date: Wed, 04 Oct 2006 14:21:58 +0200 [thread overview]
Message-ID: <4523A766.5010808@raulete.net> (raw)
Marco Gerards you asked me the other day about scripting. If there was
something missing or any other thing that he could do.
This draft about a grub2 file draft can help him thinking about how
powerful is his scripting or not.
The user sees inside a menu:
Floppy1
Floppy2
HardDisk1
HardDisk2
He selects HardDisk1. He sees another menu:
View
Save as Argument 1
Save as Argument 2
Setup Grub Here
This is Grub Root (Only if the hard disk/device has no partitions)
He selects View. He sees another menu:
hda1
hda2
hda3
hda4
hda5
He selects hda1. He sees another menu:
View
Save as Argument 1
Save as Argument 2
Setup Grub Here
This is Grub Root (Only if partition filesystem is grub readable)
He selects View. He sees another menu:
/boot
/etc
/var
He selects /etc. He sees another menu:
View
Save as Argument 1
Save as Argument 2
He selects View. He sees another menu:
fstab
config1
config2
He select fstab. He sees another menu:
View
Save as Argument 1
Save as Argument 2
Let's say he returns to previous menu where he is seeing /etc folder.
He select my_index.html. He sees another menu:
View inside a web browser (GRUB2 will have a module with basic html
reading I suppose)
View
Save as Argument 1
Save as Argument 2
So Marco Gerards....
Do you think that this can be done with your grub scripting? Or the
grub2 scripting needs more hacking?
adrian15
next reply other threads:[~2006-10-04 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 12:21 adrian15 [this message]
2006-10-05 11:55 ` grub2 file browser draft Marco Gerards
[not found] <200610051534.k95FYart014206@dell01.dinaserver.com>
2006-10-06 7:11 ` adrian15
2006-10-06 7:38 ` Marco Gerards
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=4523A766.5010808@raulete.net \
--to=adrian15@raulete.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.