From: Pixel <[EMAIL PROTECTED]>
Subject: Re: [Future] Re: extended int13 remarks
Date: 24 Mar 2000 23:45:39 +0100
> - simple i18n (aka, without changing the charset). With lilo i used
> message=message-file
> to load a file that was written at install time. What would be the best solution
> to change grub's message "Use the ^ and v keys ..."?
For now, the only way is to rewrite the source code. I don't want to
do an ad hoc solution for I18N like LILO, because I'm Japanese
(namely, I want to use Japanese but that cannot be achieved in a
simple way). Probably I18N will be one of the most important goals in
GNU GRUB 1.0.
> - keyboard translation. I prefer lilo's approach (rather than the "setkey"
> command). It's quite simple: just load a 256 byte translation table
> in memory,
I don't think that the current technique in GRUB is good, but it can
provide the same functionality. If you want to improve it, send a
patch.
Note: You should allow the user to do nearly all things at the
runtime. So just loading binary data from a file is not enough. The
user must be able to modify the translation table in the command-line
interface.
> - password command: i don't quite understand what "new-config-file" must be.
> What i'd like is to reload the same config file *without* the password
> limitation.
For now, the solution could be to prepare two configuration files,
one has the password command line and the other is the same but it
doesn't have the password command line. For example:
1. Create a configuration file with a password.
2. Copy it to another file. The argument to password must be this
filename.
3. Comment out the password line in this file. You can use, for
example, sed.
But it might be better to add the function you suggested into the
command "password". For example, if NEW-CONFIG-FILE is not specified,
GRUB uses the same configuration file. In the future, I'll add some
functions so that the user can control what interfaces could be
allowed. (i.e. you can ``lock'' arbitrary entries.)
Okuji
