From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: usability
Date: Sun, 1 Aug 2004 13:00:57 +0200 [thread overview]
Message-ID: <200408011300.57636.okuji@enbug.org> (raw)
In-Reply-To: <87fz77eqam.fsf@marco.marco-g.com>
On Sunday 01 August 2004 00:59, Marco Gerards wrote:
> Please do. I know very little about this subject and I think that is
> true for many people. I am Dutch and for Dutch (and English) ASCII
> (or anything ASCII like) is enough.
Done.
> Ok. You already implemented a very simple menu. But when I choose
> an option, nothing happens. It is easy to change it so it actually
> boots the option you have chosen.
Ah, I understand.
> > - Labelling entries
>
> What is a label used for?
I wrote this example in the previous mail:
default hurd-l4
title --label=hurd-l4 Hurd/L4
root=(hd0,0)
...
Or
title Hurd/L4
label hurd-l4
root=(hd0,0)
...
Labels should be able to be used in everywhere you can specify entry
numbers, such as default, savedefault and fallback. If this is
implemented, it could be much easier to modify config files
automatically by shell scripts.
> I think Thomas sent in a patch for this, right? Could you please
> review it? You have more knowledge about module loading.
I think his patch is only for commands. Autoloading filesystem modules
is not implemented, and I want to have commands in the normal mode to
load/unload modules with/without resolving dependencies automatically.
BTW, one problem in his patch is that autocmd.lst is maintained
manually. It is better to generate this file automatically at the
compilation time.
> This is a very good idea. Can you set up a wiki?
Do you know any site which we can use freely (and permanently, if
possible) ?
I can set it up on my server, but I'm afraid that mine is too poor for
dynamic page rendering, because it is an OpenBrick. This may be a good
occasion to get an OpenBrick NG, but I have no money to buy a new
machine at the moment.
One way is to use a hosting service, such as BerliOS or SourceForge.
BerliOS might be a good option, because it has a builtin wiki
interface, while you must set it up manually on SourceForge. It is
unfortunate that Savannah does not have any way to set up a wiki site.
I will talk about this with Savannah hackers.
Okuji
next prev parent reply other threads:[~2004-08-01 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 18:32 usability Yoshinori K. Okuji
2004-07-31 19:50 ` usability Marco Gerards
2004-07-31 22:09 ` usability Yoshinori K. Okuji
2004-07-31 22:59 ` usability Marco Gerards
2004-08-01 11:00 ` Yoshinori K. Okuji [this message]
2004-08-01 15:24 ` wiki Yoshinori K. Okuji
2004-08-01 20:40 ` wiki Marco Gerards
2004-08-02 11:41 ` wiki Yoshinori K. Okuji
2004-08-04 11:14 ` wiki Yoshinori K. Okuji
2004-08-02 15:05 ` usability Tomas Ebenlendr
2004-08-04 11:18 ` usability Yoshinori K. Okuji
2004-07-31 22:34 ` usability Yoshinori K. Okuji
2004-08-01 8:40 ` usability Jeroen Dekkers
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=200408011300.57636.okuji@enbug.org \
--to=okuji@enbug.org \
--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.