On Saturday 14 October 2006 17:43, Marco Gerards wrote:
> Ok, that sounds sane. But it does not address my problem. How would
> one iterate over disks and partitions. And perhaps other things like
> loaded modules, etc. Personally I do not care a lot about syntax, but
> I want the language to b
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
> On Friday 13 October 2006 23:03, Marco Gerards wrote:
>> It's good you mention this, because it's exactly the discussion I want
>> to start. The question here is: How do we want to deal with the
>> `for'?
>>
>> In bash it iterates over all argume
On Friday 13 October 2006 23:03, Marco Gerards wrote:
> It's good you mention this, because it's exactly the discussion I want
> to start. The question here is: How do we want to deal with the
> `for'?
>
> In bash it iterates over all arguments. The wildcards are expanded by
> the shell and thus
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
>> >> =
>> >> for
>> >> =
>> >>
>> >> The for command can be used to iterate over a set of data. I don't
>> >> like the idea of implementing this *exactly* like in bash. Personally
>> >> I am thinking of the following syntax:
>> >>
>> >>
On Friday 13 October 2006 21:52, Marco Gerards wrote:
> > I thought the same thing before, but I didn't, because the effect of
> > setting the root device has a different meaning, that is, to set a boot
> > device for the chainloader. Besides this, the root variable is very
> > similar to the conce
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:
> On Thursday 05 October 2006 15:41, Marco Gerards wrote:
>> It's also one of the features that we all have to talk about before we
>> determine it will not be changed. After GRUB 2 is being used by
>> everyone it will be hard, if not impossible, t
On Thursday 05 October 2006 15:41, Marco Gerards wrote:
> It's also one of the features that we all have to talk about before we
> determine it will not be changed. After GRUB 2 is being used by
> everyone it will be hard, if not impossible, to make changes that make
> different GRUB 2 versions in
Hollis Blanchard <[EMAIL PROTECTED]> writes:
> On Thu, 2006-10-05 at 15:41 +0200, Marco Gerards wrote:
>> I'm looking forwards to your ideas, questions, suggestions, criticism
>> and bug reports. :-)
>
> How hard do you think it will be to implement all these features (and
> handle the bugs)?
Mos
On Thu, 2006-10-05 at 15:41 +0200, Marco Gerards wrote:
> I'm looking forwards to your ideas, questions, suggestions, criticism
> and bug reports. :-)
How hard do you think it will be to implement all these features (and
handle the bugs)?
I wonder if we wouldn't be better served by a simpler scri
Quoting Marco Gerards <[EMAIL PROTECTED]>:
Hi,
a few remarks:
[...]
>
> Menu entries
>
>
> Menu entries are added with `menuentry' (or its alias `@'). It's
> important to notice this is not a command. Because it's part of the
> scripting syntax, it can have unique feat
adrian15 <[EMAIL PROTECTED]> writes:
Hi,
> Marco, my problems comes when I want to load with configfile and
> source many files from a grub2 cdrom. I just want to make sure that I
> am loading from the cdrom but not from another place.
>
> Currently I use something like this in SGD:
>
> configfil
Hi,
- root: The active disk/partition (rw, global)
- prefix: The pathname used to load grub.cfg and the modules (rw, global)
- platform: Set to the platform, eg. EFI, IEEE1275, PCBIOS, etc. (ro, global)
- processor: Processor architecture GRUB was compiled for, eg. PPC, x86 (ro,
global).
- debug:
Marco Gerards <[EMAIL PROTECTED]> writes:
> =
> Variables
> =
>
> - root: The active disk/partition (rw, global)
> ...
What about a 'prompt' variable?
~j
pgpf6nhSSgEl9.pgp
Description: PGP signature
___
Grub-devel mailing list
Grub-de
Marco Gerards <[EMAIL PROTECTED]> writes:
> Iterating over files:
> for x in (hd0,3)/foo/* ; do commands ; done
I must say I would prefer this over the other ("foreach") suggestion,
since I'm more used to it.
Anyhow, is your plan to make expansion available through out the whole
shell, or only
14 matches
Mail list logo
