Re: grub-1.97

[Colin Watson]

On Tue, Oct 27, 2009 at 08:59:15PM -0500, Bruce Dubbs wrote:
> I do have a question.  After building a package, we like to test it for 
> those packages that have tests built in.  When I tried `make test`, I got 
> an error about missing m2c.  I then went to the Debian repository and 
> built m2c.  Now I get the error:

I don't see the string "m2c" anywhere in GRUB. This is part of the
default 'make' rule for building Modula-2 programs, which is irrelevant
here; it's an accident of how files happen to be named that it's used at
all.

GRUB does not have a regression test suite.

-- 
Colin Watson   [cjwat...@ubuntu.com]


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: os-prober incorrectly generates stanza - wrong root= device.

[Felix Zielcke]

Am Dienstag, den 27.10.2009, 23:23 -0400 schrieb Chris Jones:
> While detecting other kernels, update-grub generates the following:
> 
> menuentry "Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-686 (on /dev/sda12)" { 
>
> insmod ext2   
>
> set root=(hd0,12) 
>
> search --no-floppy --fs-uuid --set 
> 042b6b67-5464-426e-a60a-21b71dfbcb74  
> linux /boot/vmlinuz-2.6.24-etchnhalf.1-686 root=/dev/hda5 ro  
>
> initrd /boot/initrd.img-2.6.24-etchnhalf.1-686
>
> } 
>
> menuentry "Debian GNU/Linux, kernel 2.6.24-etchnhalf.1-686 (single-user mode) 
> (on /dev/sda12)" { 
> insmod ext2   
>
> set root=(hd0,12) 
>
> search --no-floppy --fs-uuid --set 
> 042b6b67-5464-426e-a60a-21b71dfbcb74  
> linux /boot/vmlinuz-2.6.24-etchnhalf.1-686 root=/dev/hda5 ro single   
>
> initrd /boot/initrd.img-2.6.24-etchnhalf.1-686
>
> } 
>
> 
> /dev/sda12 is the correct partition, which is correctly reported in the
> menuentry and set root= statements, but not on the linux statement.
> 
> The result, when trying to boot these entries, is that another system
> which has its /root & /root/boot on /dev/sda5 is booted instead.
> 
> This happens with grub 1.97 as shipped by ubuntu 9.10.
> 
> Not sure this qualifies as a bug, or just incorrect setup my end.
> 

os-prober is a seperate package. It has nothing to do with us, except
that we call it to generate menuentries, if it's avaible.
It takes the root= value for the Linux kernel out of lilo.conf, menu.lst
or grub.cfg depending what you have on that partition installed.
So you have to change the bootloader configuration of your Debian etch.



-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: powerpc/sparc problems

[Felix Zielcke]

Am Montag, den 12.10.2009, 10:55 +0200 schrieb Felix Zielcke:
> David are you still there?
> And also anyone who has access to a powerpc machine (and experience)?
> 
> In Debian we the problem that the `__ashldi3' and `__bswapsi2' symbols
> can't be found in the grub-ieee1275 build on powerpc and also sparc.

Ok the internal gcc symbols for sparc have been fixed now.
But now there's another problem on sparc:

  ok boot
  Boot device: disk  File and args: 
  GRUB Illegal Instruction
  ok 

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: powerpc/sparc problems

[David Miller]

From: Felix Zielcke 
Date: Wed, 28 Oct 2009 11:24:58 +0100

> Am Montag, den 12.10.2009, 10:55 +0200 schrieb Felix Zielcke:
>> David are you still there?
>> And also anyone who has access to a powerpc machine (and experience)?
>> 
>> In Debian we the problem that the `__ashldi3' and `__bswapsi2' symbols
>> can't be found in the grub-ieee1275 build on powerpc and also sparc.
> 
> Ok the internal gcc symbols for sparc have been fixed now.
> But now there's another problem on sparc:
> 
>   ok boot
>   Boot device: disk  File and args: 
>   GRUB Illegal Instruction
>   ok 

Like I said, I won't be able to look into these kinds of things
for at least a month or so and I doubt anyone else here has the
sparc knowledge necessary to help you diagnose this.

Sorry.


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub-1.97

[Michal Suchanek]

2009/10/28 Bruce Dubbs :
> I am putting grub2 into the Linux From Scratch book and have built/tested it
> and it works quite well for us.  Thank you.
>
> I do have a question.  After building a package, we like to test it for
> those packages that have tests built in.  When I tried `make test`, I got an
> error about missing m2c.  I then went to the Debian repository and built
> m2c.  Now I get the error:
>
> bdu...@core2:/usr/src/grub/grub-1.97$ make test
> m2c    -o test -e test test.mod
> m2c: unknown flag `-e'
> make: *** [test] Error 1
>
> What version of m2c are you using and where is it available?  Is this a
> valid way to run a regression test for grub-1.97?
>
> I'd also like to make a comment.  It may be useful if you split up the build
> into subdirectories by component.  When I extracted the tarball, there were
> 57 files/directories in the top of the build tree.  After configure it was
> 64.  So far so good.  However, after make it was over 2400 files, many with
> very long file names.  This makes it almost impossible to navigate form the
> command line, even on a very big screen.  If you split it up, you could also
> shorten the filenames.  I would think that would be an advantage to
> encourage programmers to read the code and contribute to the project.
>

I guess it's meant to be used like this:

tar -jxvf grub-version.tar.bz2
cd grub-version
mkdir build
cd build
../configure --prefix=/some_prefix --options
make
make install

Now you have 2k files in the build directory but the ones that are
useful can be found under /some_prefix

You can find the files installed under /some_prefix in the build
directory so you can use them directly as well.

Many of the object files are replicated numerous times because of the
way grub links its modules. This may be addressed at later time, there
were some patches for simplifying this process.

I have no problems navigating the directory from command line although
the layout does seem a bit odd. Maybe it's related to the fact I have
some 700 files (excluding .files) in ~.

Thanks

Michal


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub-1.97

[Bruce Dubbs]

Colin Watson wrote:

On Tue, Oct 27, 2009 at 08:59:15PM -0500, Bruce Dubbs wrote:
I do have a question.  After building a package, we like to test it for 
those packages that have tests built in.  When I tried `make test`, I got 
an error about missing m2c.  I then went to the Debian repository and 
built m2c.  Now I get the error:


I don't see the string "m2c" anywhere in GRUB. This is part of the
default 'make' rule for building Modula-2 programs, which is irrelevant
here; it's an accident of how files happen to be named that it's used at
all.

GRUB does not have a regression test suite.


Thanks for the confirmation.  I had checked to see where m2c was used and 
couldn't find it either.


  -- Bruce




___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: os-prober incorrectly generates stanza - wrong root= device.

[Chris Jones]

On Wed, Oct 28, 2009 at 05:55:29AM EDT, Felix Zielcke wrote:
> Am Dienstag, den 27.10.2009, 23:23 -0400 schrieb Chris Jones:

[..]

> > Not sure this qualifies as a bug, or just incorrect setup my end.
> > 

> os-prober is a seperate package. It has nothing to do with us, except
> that we call it to generate menuentries, if it's avaible.  It takes
> the root= value for the Linux kernel out of lilo.conf, menu.lst or
> grub.cfg depending what you have on that partition installed.  So you
> have to change the bootloader configuration of your Debian etch.

Ouch..!

These legacy systems were restored from backups when moving to a larger
hard drive and the grub-legacy configuration files are therefore
obsolete.

Rather than changing these retired configuration files, I will remove
os-prober and add my other systems manually to 40_custom.

Thanks much for prompt response.

CJ





___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub-1.97

[Bruce Dubbs]

Michal Suchanek wrote:

2009/10/28 Bruce Dubbs :



I'd also like to make a comment.  It may be useful if you split up the build
into subdirectories by component.  When I extracted the tarball, there were
57 files/directories in the top of the build tree.  After configure it was
64.  So far so good.  However, after make it was over 2400 files, many with
very long file names.  This makes it almost impossible to navigate form the
command line, even on a very big screen.  If you split it up, you could also
shorten the filenames.  I would think that would be an advantage to
encourage programmers to read the code and contribute to the project.



I guess it's meant to be used like this:

tar -jxvf grub-version.tar.bz2
cd grub-version
mkdir build
cd build
../configure./configure --prefix=/usr \

--sysconfdir=/etc \
--disable-largefile \
--disable-grub-emu  \
--disable-grub-emu-usb  \
--disable-grub-fstest   \
--disable-efiemu --prefix=/some_prefix --options

make
make install


Yes, that is exactly what we are doing.  Right now the configure line is

./configure --prefix=/usr   \
--sysconfdir=/etc   \
--disable-largefile \
--disable-grub-emu  \
--disable-grub-emu-usb  \
--disable-grub-fstest   \
--disable-efiemu


Now you have 2k files in the build directory but the ones that are
useful can be found under /some_prefix


Right and 1200 of them are *.lst files, many of which have 30+ character 
filenames.  Doing an ls puts everything in one column.  Even if I expand my 
terminal to 269 characters, I only get 4 columns of files.  It's just hard to 
navigate.



You can find the files installed under /some_prefix in the build
directory so you can use them directly as well.


Yes, but you have to do `ls -l|grep ^d` just to find out what the directories 
are.


Many of the object files are replicated numerous times because of the
way grub links its modules. This may be addressed at later time, there
were some patches for simplifying this process.


Since there is only one Makefile, I could take a shot at creating a patch to 
address this problem.  Would you be interested in such a patch?


  -- Bruce


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub-1.97

[Felix Zielcke]

Am Mittwoch, den 28.10.2009, 11:02 -0500 schrieb Bruce Dubbs:
> Since there is only one Makefile, I could take a shot at creating a
> patch to 
> address this problem.  Would you be interested in such a patch? 

That's wrong that there is just one Makefile. Well it's true that there
is just one file named like that, but the main Makefiles are the
conf/*.mk files generated from conf/*.rmk by genmk.rb.

There wasn't yet much talk about improving our build system.
Bean just made it less complex in his lib branch (IIRC he called it
something like that)
But except of this nobody had much interest/time to improve or even
directly replace our build system by something better.
Okuji already objected against automake because according to him it
doestn't satisfy the needs for our build system.

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Any tutorial to configure grub menu interface ?

[J. Bakshi]

On Wed, 28 Oct 2009 04:01:05 +0800
Bean  wrote:

> On Tue, Oct 27, 2009 at 10:41 PM, J. Bakshi 
> wrote:
> > I wonder if there is any tutorial to crate cool grub menu
> > interface. Can we use the grub2 2009 summer project to get those
> > fancy interfaces ?
> 
> Hi,
> 
> There are actually two menu system. Colin has written a fancy menu
> patch as part of gsoc project, you can still get the code from
> http://grub.gibibit.com/, there are also some docs there. It looks
> good, but a little slow, and some feature like edit boot command
> hasn't been implemented.
> 
> Recently, I have rewritten the menu system and it's almost done by
> now. The project is hosted at https://launchpad.net/burg, you can also
> follow this post in ubuntu forum:
> 
> http://ubuntuforums.org/showthread.php?t=1248647
> 
> I plans to add some doc on menu config soon.
> 

Hello Bean,

It is nice to know about your project. I hope it can be in main line grub soon. 
Eagerly waiting for that and also for your doc.  

With best wishes


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub-1.97

[Felix Zielcke]

Am Mittwoch, den 28.10.2009, 17:39 +0100 schrieb Felix Zielcke:
> Am Mittwoch, den 28.10.2009, 11:02 -0500 schrieb Bruce Dubbs:
> > Since there is only one Makefile, I could take a shot at creating a
> > patch to 
> > address this problem.  Would you be interested in such a patch? 
> 
> That's wrong that there is just one Makefile. Well it's true that there
> is just one file named like that, but the main Makefiles are the
> conf/*.mk files generated from conf/*.rmk by genmk.rb.
> 
> There wasn't yet much talk about improving our build system.
> Bean just made it less complex in his lib branch (IIRC he called it
> something like that)
> But except of this nobody had much interest/time to improve or even
> directly replace our build system by something better.
> Okuji already objected against automake because according to him it
> doestn't satisfy the needs for our build system.

Uhm correction: I totally forgot about Vladimirs one Makefile
implementation.
Sorry Vladimir.

But IIRC even about this there wasn't much talk about.


-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub-1.97

[Bruce Dubbs]

Felix Zielcke wrote:

Am Mittwoch, den 28.10.2009, 11:02 -0500 schrieb Bruce Dubbs:

Since there is only one Makefile, I could take a shot at creating a
patch to 
address this problem.  Would you be interested in such a patch? 


That's wrong that there is just one Makefile. Well it's true that there
is just one file named like that, but the main Makefiles are the
conf/*.mk files generated from conf/*.rmk by genmk.rb.


Yes I see that now.  Obviously I spoke before reviewing the internals of the 
build system.  I'll review it in a bit more detail and see if I can contribute 
something useful.



There wasn't yet much talk about improving our build system.


Yes, that and documentation are generally the last things to be considered in a 
project.



But except of this nobody had much interest/time to improve or even
directly replace our build system by something better.


I have some interest, but I'm not sure of the time.  I can at least look at it 
and possibly make some suggestions/patches.



Okuji already objected against automake because according to him it
doestn't satisfy the needs for our build system.


I'm not a great fan of automake either.

  -- Bruce


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Bazaar repo reconstruction

[Robert Millan]

Hi,

Due to a problem with an old version of bzr-svn, our Bazaar repository
will have to be reconstructed.

After it has been, some manual work will be needed in order to reinstate
the branches (including experimental and personal branches).  I don't
expect that any data will be lost, but it may take a few days untill
every bit of the old repository is available again.

Please don't push anything to them untill they have been recovered.

-- 
Robert Millan


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [Announce] Initial GRUB2 on Yeeloong

[Vladimir 'phcoder' Serbinenko]

Vladimir 'phcoder' Serbinenko wrote:
>> What already works: booting as ELF from pmon, loading modules, graphics
>> output if gfx card is already inited (is a case when booted from pmon),
>> platform-independent parts
>> What doesn't work: keyboard and disks
>>   
>> 
> Now keyboard works
>   
Another update: Now internal disk and Linux loading work. Because of bzr
reconstruction I can't push it on it. Interested persons can just mail
me and I'll send you a tarball
>> ./autogen.sh
>> ./configure --target=mipsel --with-platform=yeeloong
>> make
>> Create a font.bin as explained here: http://grub.enbug.org/gfxterm
>> ./grub-mkimage  -O elf -o grub.elf -d . -f font.bin sm712 gfxterm sh normal
>>   
>> 
> Now it's:
>
> ./grub-mkimage  -O elf -o grub.elf -d . -f font.bin sm712 gfxterm sh normal 
> at_keyboard
>
>   
./grub-mkimage -O elf -o grub.elf -d . -f font.bin sm712 gfxterm sh
normal at_keyboard ata linux part_msdos ext2

-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [GITGRUB] New menu interface (implementation)

[Bean]

Hi,

Update:

Add timeout, progressbar and savedefault.

savedefault:

Variable savedefault set the system default value. If savedefault=1,
save the current boot item.

You can also overwrite the default value for individual items, in
menuentry statement --save option always save this item, and --nosave
never save the item. If neither --save nor --nosave is specified, the
system default in savedefault variable is checked.

In the menu section, use property save=1 or save=0 to achieve the same
effect as --save and --nosave.

You also need to set the environment file, default value is
${prefix}/env, you can also use envfile variable to overwrite it.

timeout:

Use timeout variable to control auto boot. For example:

set timeout=5

it would boot the default item if no key is pressed in 5 seconds. If
timeout=0, boot the default item immediately, although you can press a
key at startup to halt the auto boot. If timeout is not set, auto boot
is disabled.

progressbar:

This works in conjunction with timeout. When a timeout value is set,
you can see the process bar at bottom of screen.

As with this version, all feature from grub legacy has been
implemented. There is a grub.cfg inside the menu directory that shows
some usage:

set superusers=admin
password admin admin
password user user

set timeout=5

set envfile=/menu/env
set savedefault=1
load_env

menuentry Item1 --users user --nosave --class image_tools {
  true
}

menuentry Item2 --save --class image_about {
  true
}

. /menu/menu_efi.cfg


-- 
Bean

My repository: https://launchpad.net/burg


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Bazaar repo reconstruction

[Robert Millan]

A backup copy of the old repository is available here:

  http://people.debian.org/~rmh/grub/bzr-backup/

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [GITGRUB] New menu interface (implementation)

[Vladimir 'phcoder' Serbinenko]

Bean wrote:
> Hi,
>
> Update:
>
> Add timeout, progressbar and savedefault.
>
> savedefault:
>
> Variable savedefault set the system default value. If savedefault=1,
> save the current boot item.
>
> You can also overwrite the default value for individual items, in
> menuentry statement --save option always save this item, and --nosave
> never save the item. If neither --save nor --nosave is specified, the
> system default in savedefault variable is checked.
>
>   
Why do you need this over having a normal save_env? I don't see any
reason to prefer an ad-hoc here over general solution
> In the menu section, use property save=1 or save=0 to achieve the same
> effect as --save and --nosave.
>
> You also need to set the environment file, default value is
> ${prefix}/env, you can also use envfile variable to overwrite it.
>
> timeout:
>
> Use timeout variable to control auto boot. For example:
>
> set timeout=5
>
> it would boot the default item if no key is pressed in 5 seconds. If
> timeout=0, boot the default item immediately, although you can press a
> key at startup to halt the auto boot. If timeout is not set, auto boot
> is disabled.
>
> progressbar:
>
> This works in conjunction with timeout. When a timeout value is set,
> you can see the process bar at bottom of screen.
>
> As with this version, all feature from grub legacy has been
> implemented. There is a grub.cfg inside the menu directory that shows
> some usage:
>
> set superusers=admin
> password admin admin
> password user user
>
> set timeout=5
>
> set envfile=/menu/env
> set savedefault=1
> load_env
>
> menuentry Item1 --users user --nosave --class image_tools {
>   true
> }
>
> menuentry Item2 --save --class image_about {
>   true
> }
>
> . /menu/menu_efi.cfg
>
>
>   


-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Any tutorial to configure grub menu interface ?

[Vladimir 'phcoder' Serbinenko]

J. Bakshi wrote:
> On Wed, 28 Oct 2009 04:01:05 +0800
> Bean  wrote:
>
>   
>> On Tue, Oct 27, 2009 at 10:41 PM, J. Bakshi 
>> wrote:
>> 
>>> I wonder if there is any tutorial to crate cool grub menu
>>> interface. Can we use the grub2 2009 summer project to get those
>>> fancy interfaces ?
>>>   
>> Hi,
>>
>> There are actually two menu system. Colin has written a fancy menu
>> patch as part of gsoc project, you can still get the code from
>> http://grub.gibibit.com/, there are also some docs there. It looks
>> good, but a little slow, and some feature like edit boot command
>> hasn't been implemented.
>>
>> Recently, I have rewritten the menu system and it's almost done by
>> now. The project is hosted at https://launchpad.net/burg, you can also
>> follow this post in ubuntu forum:
>>
>> http://ubuntuforums.org/showthread.php?t=1248647
>>
>> I plans to add some doc on menu config soon.
>>
>> 
>
> Hello Bean,
>
> It is nice to know about your project. I hope it can be in main line grub 
> soon. Eagerly waiting for that and also for your doc.  
>
>   
Till now Bean ignored all our requests to work on merging these changes
in the mainline or experimental. Unless he collaborates on merging there
is nothing we can do.
> With best wishes
>
>
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>   


-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub as coreboot payload

[Robert Millan]

It appears there's a regression in coreboot-v2.  I'll trace that down.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Problem building Grub2 on OSX

[André Lopes]

Hi all,

I'm trying to build Grub2 in my Macbook5,1. The OSX version is 10.5.8, and
the Grub2 source code was obtained from the SVN trunk

So, after the ./configure --with-platform=efi --target=i386 i get this:
***
GRUB2 will be compiled with following components:
Platform: i386-efi
grub-emu: Yes
USB support for grub-emu: Yes
With memory debugging: No
efiemu runtime: No (cannot compile with -m64 -mcmodel=large -mno-red-zone
-nostdlib)
grub-fstest: Yes
grub-mkfont: Yes
***

Everything looks fine, so i issue a make command, that gives me this error:
cc1: warnings being treated as errors
kern/misc.c:62: warning: no previous prototype for ‘memcpy’
kern/misc.c:66: warning: no previous prototype for ‘memmove’
make: *** [kernel_mod-kern_misc.o] Error 1

I've tryied also to configure with the argument --disable-werror, but on the
make the error is similar:
gcc -I. -I./. -I. -I./include -I./include -Wall -W  -Wall -W -Wshadow
-Wpointer-arith -Wmissing-prototypes  -Wundef
-Wstrict-prototypes -g -Os -falign-jumps=1 -falign-loops=1
-falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow -DAPPLE_CC=1
-fnested-functions -m32 -fno-stack-protector -mno-stack-arg-probe
-fno-builtin -m32 -MD -c -o kernel_mod-symlist.o symlist.c
symlist.c: In function ‘grub_register_exported_symbols’:
symlist.c:219: error: ‘memcmp’ undeclared (first use in this function)
symlist.c:219: error: (Each undeclared identifier is reported only once
symlist.c:219: error: for each function it appears in.)
symlist.c:219: warning: missing initializer
symlist.c:219: warning: (near initialization for ‘tab[157].addr’)
symlist.c:220: error: ‘memcpy’ undeclared (first use in this function)
symlist.c:220: warning: missing initializer
symlist.c:220: warning: (near initialization for ‘tab[158].addr’)
symlist.c:221: error: ‘memmove’ undeclared (first use in this function)
symlist.c:221: warning: missing initializer
symlist.c:221: warning: (near initialization for ‘tab[159].addr’)
symlist.c:222: error: ‘memset’ undeclared (first use in this function)
symlist.c:222: warning: missing initializer
symlist.c:222: warning: (near initialization for ‘tab[160].addr’)
symlist.c:226: error: duplicate case value
symlist.c:226: error: previously used here
make: *** [kernel_mod-symlist.o] Error 1

Can anyone help me on this issue?

Many thanks,
-- 
André Lopes
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Problem building Grub2 on OSX

[Vladimir 'phcoder' Serbinenko]

André Lopes wrote:
> Hi all,
>
> I'm trying to build Grub2 in my Macbook5,1. The OSX version is 10.5.8,
> and the Grub2 source code was obtained from the SVN trunk
>
> So, after the ./configure --with-platform=efi --target=i386 i get this:
> ***
> GRUB2 will be compiled with following components:
> Platform: i386-efi
> grub-emu: Yes
> USB support for grub-emu: Yes
> With memory debugging: No
> efiemu runtime: No (cannot compile with -m64 -mcmodel=large
> -mno-red-zone -nostdlib)
> grub-fstest: Yes
> grub-mkfont: Yes
> ***
>
> Everything looks fine, so i issue a make command, that gives me this
> error:
> cc1: warnings being treated as errors
> kern/misc.c:62: warning: no previous prototype for ‘memcpy’
> kern/misc.c:66: warning: no previous prototype for ‘memmove’
> make: *** [kernel_mod-kern_misc.o] Error 1
>
> I've tryied also to configure with the argument --disable-werror, but
> on the make the error is similar:
> gcc -I. -I./. -I. -I./include -I./include -Wall -W  -Wall -W -Wshadow
> -Wpointer-arith -Wmissing-prototypes  -Wundef
> -Wstrict-prototypes -g -Os -falign-jumps=1 -falign-loops=1
> -falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow
> -DAPPLE_CC=1 -fnested-functions -m32 -fno-stack-protector
> -mno-stack-arg-probe -fno-builtin -m32 -MD -c -o kernel_mod-symlist.o
> symlist.c
> symlist.c: In function ‘grub_register_exported_symbols’:
> symlist.c:219: error: ‘memcmp’ undeclared (first use in this function)
> symlist.c:219: error: (Each undeclared identifier is reported only once
> symlist.c:219: error: for each function it appears in.)
> symlist.c:219: warning: missing initializer
> symlist.c:219: warning: (near initialization for ‘tab[157].addr’)
> symlist.c:220: error: ‘memcpy’ undeclared (first use in this function)
> symlist.c:220: warning: missing initializer
> symlist.c:220: warning: (near initialization for ‘tab[158].addr’)
> symlist.c:221: error: ‘memmove’ undeclared (first use in this function)
> symlist.c:221: warning: missing initializer
> symlist.c:221: warning: (near initialization for ‘tab[159].addr’)
> symlist.c:222: error: ‘memset’ undeclared (first use in this function)
> symlist.c:222: warning: missing initializer
> symlist.c:222: warning: (near initialization for ‘tab[160].addr’)
> symlist.c:226: error: duplicate case value
> symlist.c:226: error: previously used here
> make: *** [kernel_mod-symlist.o] Error 1
>  
> Can anyone help me on this issue?
>
It seems to be caused by following commit:
  2009-10-25  Robert Millan  
 
  * include/grub/misc.h: Fix wrong evaluation of APPLE_CC.
  (memset): Fix function prototype.
In particular by following part:
--- include/grub/misc.h 2009-10-24 23:22:14 +
+++ include/grub/misc.h 2009-10-25 15:14:08 +
@@ -75,11 +75,11 @@
 }
 
 /* Prototypes for aliases.  */
-#if !defined (GRUB_UTIL) || !defined (APPLE_CC)
+#if !defined (GRUB_UTIL) && !defined (APPLE_CC)
 int EXPORT_FUNC(memcmp) (const void *s1, const void *s2, grub_size_t n);
 void *EXPORT_FUNC(memmove) (void *dest, const void *src, grub_size_t n);
 void *EXPORT_FUNC(memcpy) (void *dest, const void *src, grub_size_t n);

It should have been
-#if !defined (GRUB_UTIL) || !defined (APPLE_CC)
+#if !defined (GRUB_UTIL)
Try this way and report back


> Many thanks,
> -- 
> André Lopes
> 
>
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>   


-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Repost: ~3TB ext4 volume not read correctly by ext2-fs driver in GRUB2

[Tony Vroon]

Ladies and gentlemen,

Reposting as this went unanswered.
It would appear that the ext2-fs driver is not reliably able to read
directories on my ~3TB / filesystem:
/dev/root 3.4T  1.7T  1.6T  52% /
/dev/root on / type ext4 (rw,noatime,barrier=1,data=ordered)

Whilst doing some troubleshooting over IRC, I was given a debug patch.
With this patch applied, I'll show you a working directory entry (/etc)
and a non-working directory entry (/boot):
prometheus ~ # grub-fstest -d ext2 -v /dev/sda3 ls /etc
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:651: iterating inode size=4096 mode=0x41ed
fs/ext2.c:688: got filename: '.', type 2
fs/ext2.c:862: grub_fshelp_dir returning: 0
fs/ext2.c:651: iterating inode size=4096 mode=0x41ed
fs/ext2.c:688: got filename: '.', type 2
fs/ext2.c:688: got filename: '..', type 2
fs/ext2.c:688: got filename: 'lost+found', type 2
fs/ext2.c:688: got filename: 'lib', type 7
fs/ext2.c:688: got filename: '.config', type 1
fs/ext2.c:688: got filename: 'sbin', type 2
fs/ext2.c:688: got filename: 'root', type 2
fs/ext2.c:688: got filename: 'mnt', type 2
fs/ext2.c:688: got filename: 'opt', type 2
fs/ext2.c:688: got filename: 'var', type 2
fs/ext2.c:688: got filename: 'usr', type 2
fs/ext2.c:688: got filename: 'dev', type 2
fs/ext2.c:688: got filename: 'lib32', type 2
fs/ext2.c:688: got filename: 'home', type 2
fs/ext2.c:688: got filename: 'tmp', type 2
fs/ext2.c:688: got filename: 'media', type 2
fs/ext2.c:688: got filename: 'sys', type 2
fs/ext2.c:688: got filename: 'cvs', type 2
fs/ext2.c:688: got filename: 'proc', type 2
fs/ext2.c:688: got filename: 'etc', type 2
fs/ext2.c:651: iterating inode size=0 mode=0x0
fs/ext2.c:862: grub_fshelp_dir returning: 0

prometheus ~ # grub-fstest -d ext2 -v /dev/sda3 ls /boot
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:862: grub_fshelp_dir returning: 9
fs/ext2.c:651: iterating inode size=4096 mode=0x41ed
fs/ext2.c:688: got filename: '.', type 2
fs/ext2.c:862: grub_fshelp_dir returning: 0
fs/ext2.c:651: iterating inode size=4096 mode=0x41ed
fs/ext2.c:688: got filename: '.', type 2
fs/ext2.c:688: got filename: '..', type 2
fs/ext2.c:688: got filename: 'lost+found', type 2
fs/ext2.c:688: got filename: 'lib', type 7
fs/ext2.c:688: got filename: '.config', type 1
fs/ext2.c:688: got filename: 'sbin', type 2
fs/ext2.c:688: got filename: 'root', type 2
fs/ext2.c:688: got filename: 'mnt', type 2
fs/ext2.c:688: got filename: 'opt', type 2
fs/ext2.c:688: got filename: 'var', type 2
fs/ext2.c:688: got filename: 'usr', type 2
fs/ext2.c:688: got filename: 'dev', type 2
fs/ext2.c:688: got filename: 'lib32', type 2
fs/ext2.c:688: got filename: 'home', type 2
fs/ext2.c:688: got filename: 'tmp', type 2
fs/ext2.c:688: got filename: 'media', type 2
fs/ext2.c:688: got filename: 'sys', type 2
fs/ext2.c:688: got filename: 'cvs', type 2
fs/ext2.c:688: got filename: 'proc', type 2
fs/ext2.c:688: got filename: 'etc', type 2
fs/ext2.c:688: got filename: 'lib64', type 2
fs/ext2.c:688: got filename: 'boot', type 2
fs/ext2.c:651: iterating inode size=0 mode=0x0
fs/ext2.c:862: grub_fshelp_dir returning: 0

In order to help troubleshoot this, I can apply patches on top of
current SVN, run fstest & test booting for you. Please note that making
images of a 3TB drive is not practical and will not reflect the real
situation to you.
Sorry, but I am not comfortable offering SSH access to random internet
strangers.

Regards,
Tony V.
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


signature.asc
Description: This is a digitally signed message part
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

[PATCH] try to reread partition table in 10_linux

[Felix Zielcke]

/dev/disk/by-uuid seems to be only created when the partition table gets
reread after a new filesystem has been created.
So here's a patch which does it with sfdisk.

I wasn't sure if some devices like e.g. /dev/mapper/* should be ignored.
mdraid devices can have partitions so they should be tried too.

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
2009-10-28  Felix Zielcke  

	* util/grub.d/10_linux.in: Try to reread partition table with 
	sfdisk before we check if UUIDs can be used.

Index: util/grub.d/10_linux.in
===
--- util/grub.d/10_linux.in	(revision 2668)
+++ util/grub.d/10_linux.in	(working copy)
@@ -35,6 +35,13 @@ case ${GRUB_DEVICE} in
   ;;
 esac
 
+# Try to reread partition table.  In case a fresh filesystem has been created
+# /dev/disk/by-uuid doestn't yet exist.
+if which sfdisk /dev/null ; then
+  GRUB_DEVICE_DISK=`echo ${GRUB_DEVICE} | sed -e "s/[0-9]*$//"`
+  sfdisk -R ${GRUB_DEVICE_DISK} 2>/dev/null
+fi
+
 if [ "x${GRUB_DEVICE_UUID}" = "x" ] || [ "x${GRUB_DISABLE_LINUX_UUID}" = "xtrue" ] \
 || ! test -e "/dev/disk/by-uuid/${GRUB_DEVICE_UUID}" ; then
   LINUX_ROOT_DEVICE=${GRUB_DEVICE}
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: Problem building Grub2 on OSX

[André Lopes]

Yes it was that. Now it builds almost fine!

Now it just gives an ignored error building the docs, i think:

Updating ./docs/version.texi
./install-sh -c -d docs
/usr/bin/makeinfo -P ./docs --no-split --force docs/grub.texi -o docs/
grub.info
./docs/grub.texi:1552: Prev reference to nonexistent node `Internals'
(perhaps incorrect sectioning?).

...

./docs/grub.texi:81: Menu reference to nonexistent node `Network' (perhaps
incorrect sectioning?).
./docs/grub.texi:80: Menu reference to nonexistent node `Configuration'
(perhaps incorrect sectioning?).
./docs/grub.texi:964: warning: unreferenced node `Menu entry editor'.
make: [docs/grub.info] Error 1 (ignored)

Many thanks for the help!


On Wed, Oct 28, 2009 at 10:15 PM, Vladimir 'phcoder' Serbinenko <
phco...@gmail.com> wrote:

> André Lopes wrote:
> > Hi all,
> >
> > I'm trying to build Grub2 in my Macbook5,1. The OSX version is 10.5.8,
> > and the Grub2 source code was obtained from the SVN trunk
> >
> > So, after the ./configure --with-platform=efi --target=i386 i get this:
> > ***
> > GRUB2 will be compiled with following components:
> > Platform: i386-efi
> > grub-emu: Yes
> > USB support for grub-emu: Yes
> > With memory debugging: No
> > efiemu runtime: No (cannot compile with -m64 -mcmodel=large
> > -mno-red-zone -nostdlib)
> > grub-fstest: Yes
> > grub-mkfont: Yes
> > ***
> >
> > Everything looks fine, so i issue a make command, that gives me this
> > error:
> > cc1: warnings being treated as errors
> > kern/misc.c:62: warning: no previous prototype for ‘memcpy’
> > kern/misc.c:66: warning: no previous prototype for ‘memmove’
> > make: *** [kernel_mod-kern_misc.o] Error 1
> >
> > I've tryied also to configure with the argument --disable-werror, but
> > on the make the error is similar:
> > gcc -I. -I./. -I. -I./include -I./include -Wall -W  -Wall -W -Wshadow
> > -Wpointer-arith -Wmissing-prototypes  -Wundef
> > -Wstrict-prototypes -g -Os -falign-jumps=1 -falign-loops=1
> > -falign-functions=1 -mno-mmx -mno-sse -mno-sse2 -mno-3dnow
> > -DAPPLE_CC=1 -fnested-functions -m32 -fno-stack-protector
> > -mno-stack-arg-probe -fno-builtin -m32 -MD -c -o kernel_mod-symlist.o
> > symlist.c
> > symlist.c: In function ‘grub_register_exported_symbols’:
> > symlist.c:219: error: ‘memcmp’ undeclared (first use in this function)
> > symlist.c:219: error: (Each undeclared identifier is reported only once
> > symlist.c:219: error: for each function it appears in.)
> > symlist.c:219: warning: missing initializer
> > symlist.c:219: warning: (near initialization for ‘tab[157].addr’)
> > symlist.c:220: error: ‘memcpy’ undeclared (first use in this function)
> > symlist.c:220: warning: missing initializer
> > symlist.c:220: warning: (near initialization for ‘tab[158].addr’)
> > symlist.c:221: error: ‘memmove’ undeclared (first use in this function)
> > symlist.c:221: warning: missing initializer
> > symlist.c:221: warning: (near initialization for ‘tab[159].addr’)
> > symlist.c:222: error: ‘memset’ undeclared (first use in this function)
> > symlist.c:222: warning: missing initializer
> > symlist.c:222: warning: (near initialization for ‘tab[160].addr’)
> > symlist.c:226: error: duplicate case value
> > symlist.c:226: error: previously used here
> > make: *** [kernel_mod-symlist.o] Error 1
> >
> > Can anyone help me on this issue?
> >
> It seems to be caused by following commit:
>  2009-10-25  Robert Millan  
>
>  * include/grub/misc.h: Fix wrong evaluation of APPLE_CC.
>  (memset): Fix function prototype.
> In particular by following part:
> --- include/grub/misc.h 2009-10-24 23:22:14 +
> +++ include/grub/misc.h 2009-10-25 15:14:08 +
> @@ -75,11 +75,11 @@
>  }
>
>  /* Prototypes for aliases.  */
> -#if !defined (GRUB_UTIL) || !defined (APPLE_CC)
> +#if !defined (GRUB_UTIL) && !defined (APPLE_CC)
>  int EXPORT_FUNC(memcmp) (const void *s1, const void *s2, grub_size_t n);
>  void *EXPORT_FUNC(memmove) (void *dest, const void *src, grub_size_t n);
>  void *EXPORT_FUNC(memcpy) (void *dest, const void *src, grub_size_t n);
>
> It should have been
> -#if !defined (GRUB_UTIL) || !defined (APPLE_CC)
> +#if !defined (GRUB_UTIL)
> Try this way and report back
>
>
> > Many thanks,
> > --
> > André Lopes
> > 
> >
> > ___
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > http://lists.gnu.org/mailman/listinfo/grub-devel
> >
>
>
> --
> Regards
> Vladimir 'phcoder' Serbinenko
> Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
>
>
>
> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>



-- 
André Lopes
Joan Crawford
- "I, Joan Crawford, I believe in the d

Re: Problem building Grub2 on OSX

[Robert Millan]

On Wed, Oct 28, 2009 at 10:35:23PM +, André Lopes wrote:
> Yes it was that. Now it builds almost fine!

Fixed in SVN, thank you.

> Now it just gives an ignored error building the docs, i think:
> 
> [...]
> make: [docs/grub.info] Error 1 (ignored)

This is to be expected.  Patches welcome.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [PATCH] try to reread partition table in 10_linux

[Robert Millan]

On Wed, Oct 28, 2009 at 11:33:51PM +0100, Felix Zielcke wrote:
> +if which sfdisk /dev/null ; then
> +  GRUB_DEVICE_DISK=`echo ${GRUB_DEVICE} | sed -e "s/[0-9]*$//"`
> +  sfdisk -R ${GRUB_DEVICE_DISK} 2>/dev/null
> +fi

s/[0-9]*$// doesn't catch all partition path layouts.  More heuristic
is needed for that (we have this in util/hostdisk.c), but duplicating it
doesn't sound like a good idea.

Can this be avoided altogether?  E.g. by telling Linux the partition path
instead, or by using another interface.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [PATCH] Add -nostdinc to TARGET_CFLAGS

[Robert Millan]

Committed then.

On Mon, Oct 26, 2009 at 05:16:38PM +0100, Robert Millan wrote:
> 
> It should be pretty obvious that we don't want to use system headers when
> building target, but we've been for so long without this flag that I want
> to make sure.
> 
> Does anyone see a problem with it?
> 
> -- 
> Robert Millan
> 
>   The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
>   how) you may access your data; but nobody's threatening your freedom: we
>   still allow you to remove your data and not access it at all."

> 
> $ bzr diff -r 1768..1769 
> bzr+ssh://bzr.savannah.gnu.org/grub/people/robertmh/lib-linux/Makefile.in
> 
> 2009-10-26  Robert Millan  
> 
>   * Makefile.in (TARGET_CPPFLAGS): Add `-nostdinc'.
> 
> === modified file 'Makefile.in'
> --- Makefile.in   2009-10-06 00:04:32 +
> +++ Makefile.in   2009-10-23 13:31:15 +
> @@ -75,7 +75,7 @@
>  TARGET_MODULE_FORMAT = @TARGET_MODULE_FORMAT@
>  TARGET_APPLE_CC = @TARGET_APPLE_CC@
>  OBJCONV = @OBJCONV@
> -TARGET_CPPFLAGS = @TARGET_CPPFLAGS@ -I$(builddir) -I$(builddir)/include 
> -I$(srcdir)/include \
> +TARGET_CPPFLAGS = @TARGET_CPPFLAGS@ -nostdinc -I$(builddir) 
> -I$(builddir)/include -I$(srcdir)/include \
>   -Wall -W
>  TARGET_LDFLAGS = @TARGET_LDFLAGS@
>  TARGET_IMG_LDSCRIPT = @TARGET_IMG_LDSCRIPT@
> 

> ___
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel


-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [PATCH] try to reread partition table in 10_linux

[Felix Zielcke]

Am Donnerstag, den 29.10.2009, 00:00 +0100 schrieb Robert Millan:
> On Wed, Oct 28, 2009 at 11:33:51PM +0100, Felix Zielcke wrote:
> > +if which sfdisk /dev/null ; then
> > +  GRUB_DEVICE_DISK=`echo ${GRUB_DEVICE} | sed -e "s/[0-9]*$//"`
> > +  sfdisk -R ${GRUB_DEVICE_DISK} 2>/dev/null
> > +fi
> 
> s/[0-9]*$// doesn't catch all partition path layouts.  More heuristic
> is needed for that (we have this in util/hostdisk.c), but duplicating it
> doesn't sound like a good idea.

Oh right I forgot about e.g. the hardware RAID controllers.
Hm if grub-probe would accept a GRUB device, we could use 2 grub-probe
calls to do that.
i.e. something like
 tmp_drive=`grub-probe -t drive -d ${GRUB_DEVICE} | sed -e 's/,[a-z0-9]//g'`
 GRUB_DEVICE_DISK=`grub-probe -t device ${tmp_drive}`

> Can this be avoided altogether?  E.g. by telling Linux the partition path
> instead, or by using another interface.

I don't think we can:
$ LANG=C sudo sfdisk -R /dev/hda2
BLKRRPART: Invalid argument
I doubt the kernel provides more then one way to reread the partition
table.
Hm but maybe libparted or something else has a wrapper for this.

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer



___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub as coreboot payload

[Robert Millan]

On Mon, Oct 26, 2009 at 09:20:53PM +0100, Andreas B. Mundt wrote:
> Hi,
> 
> first, congratulations to the 1.97-release!
> 
> I vainly tried to run the latest grub2 (Revision: 2663) as payload to
> coreboot (Revision: 4852) following the wikipage: 
> 
> http://grub.enbug.org/CoreBoot
> 
> Is this page still up to date and does anybody use grub2 as payload
> successfully? How? 

Hi,

It appears that since r4534 (move to Kconfig), Multiboot information is no
longer built in by default.  You have to enable it in "System tables" /
"Generate Multiboot tables (for GRUB2)", then GRUB works fine (at least
on QEMU, which I just tested).

Coreboot developers: would you consider enabling it again?  The overhead
is minimal, and it would make this less confusing for users.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

Signed-off-by: Robert Millan 

Index: src/Kconfig
===
--- src/Kconfig	(revision 4887)
+++ src/Kconfig	(working copy)
@@ -319,7 +319,7 @@
 
 config MULTIBOOT
 	bool "Generate Multiboot tables (for GRUB2)"
-	default n
+	default y
 
 config GENERATE_ACPI_TABLES
 	depends on HAVE_ACPI_TABLES
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: [GITGRUB] New menu interface (implementation)

[Bean]

On Thu, Oct 29, 2009 at 5:12 AM, Vladimir 'phcoder' Serbinenko
 wrote:
> Bean wrote:
>> Hi,
>>
>> Update:
>>
>> Add timeout, progressbar and savedefault.
>>
>> savedefault:
>>
>> Variable savedefault set the system default value. If savedefault=1,
>> save the current boot item.
>>
>> You can also overwrite the default value for individual items, in
>> menuentry statement --save option always save this item, and --nosave
>> never save the item. If neither --save nor --nosave is specified, the
>> system default in savedefault variable is checked.
>>
>>
> Why do you need this over having a normal save_env? I don't see any
> reason to prefer an ad-hoc here over general solution

Hi,

This is more convenient than adding a save_env command to every entry.
Users can just set savedefault=1 and all items are saved by default,
remove it and it's not saved anymore. They can also config each item
individually with --save and --nosave option, which is similar to
adding a save_env command at the beginning, but easier to edit.

-- 
Bean

My repository: https://launchpad.net/burg


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub-1.97

[richardvo...@gmail.com]

On Wed, Oct 28, 2009 at 11:02 AM, Bruce Dubbs  wrote:
> Michal Suchanek wrote:
>>
>> 2009/10/28 Bruce Dubbs :
>
>>> I'd also like to make a comment.  It may be useful if you split up the
>>> build
>>> into subdirectories by component.  When I extracted the tarball, there
>>> were
>>> 57 files/directories in the top of the build tree.  After configure it
>>> was
>>> 64.  So far so good.  However, after make it was over 2400 files, many
>>> with
>>> very long file names.  This makes it almost impossible to navigate form
>>> the
>>> command line, even on a very big screen.  If you split it up, you could
>>> also
>>> shorten the filenames.  I would think that would be an advantage to
>>> encourage programmers to read the code and contribute to the project.
>>>
>>
>> I guess it's meant to be used like this:
>>
>> tar -jxvf grub-version.tar.bz2
>> cd grub-version
>> mkdir build
>> cd build
>> ../configure./configure --prefix=/usr \
>
>            --sysconfdir=/etc \
>            --disable-largefile     \
>            --disable-grub-emu      \
>            --disable-grub-emu-usb  \
>            --disable-grub-fstest   \
>            --disable-efiemu --prefix=/some_prefix --options
>>
>> make
>> make install
>
> Yes, that is exactly what we are doing.  Right now the configure line is

Not "exactly", and the difference is important.Michal suggested
running "../configure" with a double-dot meaning parent directory.
Your line has only a single dot, meaning current directory.  As a
result your files are all mixed together instead of separated as
intended.

>
> ./configure --prefix=/usr           \
>            --sysconfdir=/etc       \
>            --disable-largefile     \
>            --disable-grub-emu      \
>            --disable-grub-emu-usb  \
>            --disable-grub-fstest   \
>            --disable-efiemu


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Re: grub-1.97

[Bruce Dubbs]

richardvo...@gmail.com wrote:

On Wed, Oct 28, 2009 at 11:02 AM, Bruce Dubbs  wrote:

Michal Suchanek wrote:



I guess it's meant to be used like this:

tar -jxvf grub-version.tar.bz2
cd grub-version
mkdir build
cd build
../configure./configure --prefix=/usr \

   --sysconfdir=/etc \
   --disable-largefile \
   --disable-grub-emu  \
   --disable-grub-emu-usb  \
   --disable-grub-fstest   \
   --disable-efiemu --prefix=/some_prefix --options

make
make install

Yes, that is exactly what we are doing.  Right now the configure line is


Not "exactly", and the difference is important.Michal suggested
running "../configure" with a double-dot meaning parent directory.
Your line has only a single dot, meaning current directory.  As a
result your files are all mixed together instead of separated as
intended.


./configure --prefix=/usr   \
   --sysconfdir=/etc   \
   --disable-largefile \
   --disable-grub-emu  \
   --disable-grub-emu-usb  \
   --disable-grub-fstest   \
   --disable-efiemu


Ah yes.  Thank you Richard.  Either systems works, but using a separate build 
directory keeps all the 2400 generated files out of the main directory.  I'll 
change to that in LFS.


  -- Bruce


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel