GRUB 1.91 is released

GRUB 1.91 is released

[Yoshinori K. Okuji]

I'm happy to announce the release of GRUB 1.91. This is the second of
our prereleases leading up to GRUB 2.0. We encourage you to try it, as
we have done a significant amount of work towards GRUB 2. Note that this 
release is mainly for developers who are willing to contribute to our 
project. If you need a working solution immediately, you'd better to stick to 
GRUB Legacy at the moment.

The source distribution is available from <ftp://alpha.gnu.org/gnu/grub/>.

Send any questions, ideas, bug reports to <grub-devel@gnu.org>.

Here is the relevant NEWS:

New in 1.91 - 2005-10-15:

* Add support for LZO version 2.

* Support completion in the entry editor.

* Add VBE support.

* New commands, "search", "vbetest" and "vbeinfo".

* The option BOOT_IMAGE is passed to Linux.

* Add support for automatic decompression for gzip.

* Add support for terminfo and serial.

* Add support for x86_64.

* GRUB itself is a Multiboot-compliant kernel.

* Add new filesystems: XFS, SFS, and AFFS.

Thanks,
Okuji

[SFS breaks PPC build] Re: GRUB 1.91 is released

[Cyril Plisko]

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

On 10/15/05, Yoshinori K. Okuji <okuji@enbug.org> wrote:
> I'm happy to announce the release of GRUB 1.91. This is the second of
> our prereleases leading up to GRUB 2.0. We encourage you to try it, as
> we have done a significant amount of work towards GRUB 2. Note that this
> release is mainly for developers who are willing to contribute to our
> project. If you need a working solution immediately, you'd better to stick to
> GRUB Legacy at the moment.
>
> The source distribution is available from <ftp://alpha.gnu.org/gnu/grub/>.
>
> Send any questions, ideas, bug reports to <grub-devel@gnu.org>.
>
> Here is the relevant NEWS:
>
> New in 1.91 - 2005-10-15:
>
> * Add support for LZO version 2.
>
> * Support completion in the entry editor.
>
> * Add VBE support.
>
> * New commands, "search", "vbetest" and "vbeinfo".
>
> * The option BOOT_IMAGE is passed to Linux.
>
> * Add support for automatic decompression for gzip.
>
> * Add support for terminfo and serial.
>
> * Add support for x86_64.
>
> * GRUB itself is a Multiboot-compliant kernel.
>
> * Add new filesystems: XFS, SFS, and AFFS.
>
> Thanks,
> Okuji
>

Hi,

apparently sfs addition breaks PPC build. The attached patch fixed it for me,
but I am not sure I didn't miss something important.

Regards,
         Cyril

[-- Attachment #2: ppc-sfs.patch --]
[-- Type: text/x-patch, Size: 10076 bytes --]

Index: conf/powerpc-ieee1275.mk
===================================================================
RCS file: /cvsroot/grub/grub2/conf/powerpc-ieee1275.mk,v
retrieving revision 1.43
diff -u -r1.43 powerpc-ieee1275.mk
--- conf/powerpc-ieee1275.mk	8 Oct 2005 11:24:47 -0000	1.43
+++ conf/powerpc-ieee1275.mk	15 Oct 2005 22:50:39 -0000
@@ -70,7 +70,7 @@
 	commands/ieee1275/halt.c commands/ieee1275/reboot.c		\
 	disk/loopback.c							\
 	fs/affs.c fs/ext2.c fs/fat.c fs/fshelp.c fs/hfs.c fs/iso9660.c	\
-	fs/jfs.c fs/minix.c fs/ufs.c fs/xfs.c				\
+	fs/jfs.c fs/minix.c fs/sfs.c fs/ufs.c fs/xfs.c				\
 	io/gzio.c							\
 	kern/device.c kern/disk.c kern/dl.c kern/env.c kern/err.c 	\
 	kern/file.c kern/fs.c kern/loader.c kern/main.c kern/misc.c	\
@@ -82,10 +82,10 @@
 	util/console.c util/grub-emu.c util/misc.c			\
 	util/i386/pc/biosdisk.c util/i386/pc/getroot.c			\
 	util/powerpc/ieee1275/misc.c
-CLEANFILES += grub-emu grub_emu-commands_boot.o grub_emu-commands_cat.o grub_emu-commands_cmp.o grub_emu-commands_configfile.o grub_emu-commands_default.o grub_emu-commands_help.o grub_emu-commands_search.o grub_emu-commands_terminal.o grub_emu-commands_ls.o grub_emu-commands_timeout.o grub_emu-commands_ieee1275_halt.o grub_emu-commands_ieee1275_reboot.o grub_emu-disk_loopback.o grub_emu-fs_affs.o grub_emu-fs_ext2.o grub_emu-fs_fat.o grub_emu-fs_fshelp.o grub_emu-fs_hfs.o grub_emu-fs_iso9660.o grub_emu-fs_jfs.o grub_emu-fs_minix.o grub_emu-fs_ufs.o grub_emu-fs_xfs.o grub_emu-io_gzio.o grub_emu-kern_device.o grub_emu-kern_disk.o grub_emu-kern_dl.o grub_emu-kern_env.o grub_emu-kern_err.o grub_emu-kern_file.o grub_emu-kern_fs.o grub_emu-kern_loader.o grub_emu-kern_main.o grub_emu-kern_misc.o grub_emu-kern_partition.o grub_emu-kern_rescue.o grub_emu-kern_term.o grub_emu-normal_arg.o grub_emu-normal_cmdline.o grub_emu-normal_command.o grub_emu-normal_completion.o grub_emu-normal_context.o grub_emu-normal_main.o grub_emu-normal_menu.o grub_emu-normal_menu_entry.o grub_emu-normal_misc.o grub_emu-partmap_amiga.o grub_emu-partmap_apple.o grub_emu-partmap_pc.o grub_emu-partmap_sun.o grub_emu-util_console.o grub_emu-util_grub_emu.o grub_emu-util_misc.o grub_emu-util_i386_pc_biosdisk.o grub_emu-util_i386_pc_getroot.o grub_emu-util_powerpc_ieee1275_misc.o
-MOSTLYCLEANFILES += grub_emu-commands_boot.d grub_emu-commands_cat.d grub_emu-commands_cmp.d grub_emu-commands_configfile.d grub_emu-commands_default.d grub_emu-commands_help.d grub_emu-commands_search.d grub_emu-commands_terminal.d grub_emu-commands_ls.d grub_emu-commands_timeout.d grub_emu-commands_ieee1275_halt.d grub_emu-commands_ieee1275_reboot.d grub_emu-disk_loopback.d grub_emu-fs_affs.d grub_emu-fs_ext2.d grub_emu-fs_fat.d grub_emu-fs_fshelp.d grub_emu-fs_hfs.d grub_emu-fs_iso9660.d grub_emu-fs_jfs.d grub_emu-fs_minix.d grub_emu-fs_ufs.d grub_emu-fs_xfs.d grub_emu-io_gzio.d grub_emu-kern_device.d grub_emu-kern_disk.d grub_emu-kern_dl.d grub_emu-kern_env.d grub_emu-kern_err.d grub_emu-kern_file.d grub_emu-kern_fs.d grub_emu-kern_loader.d grub_emu-kern_main.d grub_emu-kern_misc.d grub_emu-kern_partition.d grub_emu-kern_rescue.d grub_emu-kern_term.d grub_emu-normal_arg.d grub_emu-normal_cmdline.d grub_emu-normal_command.d grub_emu-normal_completion.d grub_emu-normal_context.d grub_emu-normal_main.d grub_emu-normal_menu.d grub_emu-normal_menu_entry.d grub_emu-normal_misc.d grub_emu-partmap_amiga.d grub_emu-partmap_apple.d grub_emu-partmap_pc.d grub_emu-partmap_sun.d grub_emu-util_console.d grub_emu-util_grub_emu.d grub_emu-util_misc.d grub_emu-util_i386_pc_biosdisk.d grub_emu-util_i386_pc_getroot.d grub_emu-util_powerpc_ieee1275_misc.d
+CLEANFILES += grub-emu grub_emu-commands_boot.o grub_emu-commands_cat.o grub_emu-commands_cmp.o grub_emu-commands_configfile.o grub_emu-commands_default.o grub_emu-commands_help.o grub_emu-commands_search.o grub_emu-commands_terminal.o grub_emu-commands_ls.o grub_emu-commands_timeout.o grub_emu-commands_ieee1275_halt.o grub_emu-commands_ieee1275_reboot.o grub_emu-disk_loopback.o grub_emu-fs_affs.o grub_emu-fs_ext2.o grub_emu-fs_fat.o grub_emu-fs_fshelp.o grub_emu-fs_hfs.o grub_emu-fs_iso9660.o grub_emu-fs_jfs.o grub_emu-fs_minix.o grub_emu-fs_sfs.o grub_emu-fs_ufs.o grub_emu-fs_xfs.o grub_emu-io_gzio.o grub_emu-kern_device.o grub_emu-kern_disk.o grub_emu-kern_dl.o grub_emu-kern_env.o grub_emu-kern_err.o grub_emu-kern_file.o grub_emu-kern_fs.o grub_emu-kern_loader.o grub_emu-kern_main.o grub_emu-kern_misc.o grub_emu-kern_partition.o grub_emu-kern_rescue.o grub_emu-kern_term.o grub_emu-normal_arg.o grub_emu-normal_cmdline.o grub_emu-normal_command.o grub_emu-normal_completion.o grub_emu-normal_context.o grub_emu-normal_main.o grub_emu-normal_menu.o grub_emu-normal_menu_entry.o grub_emu-normal_misc.o grub_emu-partmap_amiga.o grub_emu-partmap_apple.o grub_emu-partmap_pc.o grub_emu-partmap_sun.o grub_emu-util_console.o grub_emu-util_grub_emu.o grub_emu-util_misc.o grub_emu-util_i386_pc_biosdisk.o grub_emu-util_i386_pc_getroot.o grub_emu-util_powerpc_ieee1275_misc.o
+MOSTLYCLEANFILES += grub_emu-commands_boot.d grub_emu-commands_cat.d grub_emu-commands_cmp.d grub_emu-commands_configfile.d grub_emu-commands_default.d grub_emu-commands_help.d grub_emu-commands_search.d grub_emu-commands_terminal.d grub_emu-commands_ls.d grub_emu-commands_timeout.d grub_emu-commands_ieee1275_halt.d grub_emu-commands_ieee1275_reboot.d grub_emu-disk_loopback.d grub_emu-fs_affs.d grub_emu-fs_ext2.d grub_emu-fs_fat.d grub_emu-fs_fshelp.d grub_emu-fs_hfs.d grub_emu-fs_iso9660.d grub_emu-fs_jfs.d grub_emu-fs_minix.d grub_emu-fs_sfs.d grub_emu-fs_ufs.d grub_emu-fs_xfs.d grub_emu-io_gzio.d grub_emu-kern_device.d grub_emu-kern_disk.d grub_emu-kern_dl.d grub_emu-kern_env.d grub_emu-kern_err.d grub_emu-kern_file.d grub_emu-kern_fs.d grub_emu-kern_loader.d grub_emu-kern_main.d grub_emu-kern_misc.d grub_emu-kern_partition.d grub_emu-kern_rescue.d grub_emu-kern_term.d grub_emu-normal_arg.d grub_emu-normal_cmdline.d grub_emu-normal_command.d grub_emu-normal_completion.d grub_emu-normal_context.d grub_emu-normal_main.d grub_emu-normal_menu.d grub_emu-normal_menu_entry.d grub_emu-normal_misc.d grub_emu-partmap_amiga.d grub_emu-partmap_apple.d grub_emu-partmap_pc.d grub_emu-partmap_sun.d grub_emu-util_console.d grub_emu-util_grub_emu.d grub_emu-util_misc.d grub_emu-util_i386_pc_biosdisk.d grub_emu-util_i386_pc_getroot.d grub_emu-util_powerpc_ieee1275_misc.d
 
-grub-emu: grub_emu-commands_boot.o grub_emu-commands_cat.o grub_emu-commands_cmp.o grub_emu-commands_configfile.o grub_emu-commands_default.o grub_emu-commands_help.o grub_emu-commands_search.o grub_emu-commands_terminal.o grub_emu-commands_ls.o grub_emu-commands_timeout.o grub_emu-commands_ieee1275_halt.o grub_emu-commands_ieee1275_reboot.o grub_emu-disk_loopback.o grub_emu-fs_affs.o grub_emu-fs_ext2.o grub_emu-fs_fat.o grub_emu-fs_fshelp.o grub_emu-fs_hfs.o grub_emu-fs_iso9660.o grub_emu-fs_jfs.o grub_emu-fs_minix.o grub_emu-fs_ufs.o grub_emu-fs_xfs.o grub_emu-io_gzio.o grub_emu-kern_device.o grub_emu-kern_disk.o grub_emu-kern_dl.o grub_emu-kern_env.o grub_emu-kern_err.o grub_emu-kern_file.o grub_emu-kern_fs.o grub_emu-kern_loader.o grub_emu-kern_main.o grub_emu-kern_misc.o grub_emu-kern_partition.o grub_emu-kern_rescue.o grub_emu-kern_term.o grub_emu-normal_arg.o grub_emu-normal_cmdline.o grub_emu-normal_command.o grub_emu-normal_completion.o grub_emu-normal_context.o grub_emu-normal_main.o grub_emu-normal_menu.o grub_emu-normal_menu_entry.o grub_emu-normal_misc.o grub_emu-partmap_amiga.o grub_emu-partmap_apple.o grub_emu-partmap_pc.o grub_emu-partmap_sun.o grub_emu-util_console.o grub_emu-util_grub_emu.o grub_emu-util_misc.o grub_emu-util_i386_pc_biosdisk.o grub_emu-util_i386_pc_getroot.o grub_emu-util_powerpc_ieee1275_misc.o
+grub-emu: grub_emu-commands_boot.o grub_emu-commands_cat.o grub_emu-commands_cmp.o grub_emu-commands_configfile.o grub_emu-commands_default.o grub_emu-commands_help.o grub_emu-commands_search.o grub_emu-commands_terminal.o grub_emu-commands_ls.o grub_emu-commands_timeout.o grub_emu-commands_ieee1275_halt.o grub_emu-commands_ieee1275_reboot.o grub_emu-disk_loopback.o grub_emu-fs_affs.o grub_emu-fs_ext2.o grub_emu-fs_fat.o grub_emu-fs_fshelp.o grub_emu-fs_hfs.o grub_emu-fs_iso9660.o grub_emu-fs_jfs.o grub_emu-fs_minix.o grub_emu-fs_sfs.o grub_emu-fs_ufs.o grub_emu-fs_xfs.o grub_emu-io_gzio.o grub_emu-kern_device.o grub_emu-kern_disk.o grub_emu-kern_dl.o grub_emu-kern_env.o grub_emu-kern_err.o grub_emu-kern_file.o grub_emu-kern_fs.o grub_emu-kern_loader.o grub_emu-kern_main.o grub_emu-kern_misc.o grub_emu-kern_partition.o grub_emu-kern_rescue.o grub_emu-kern_term.o grub_emu-normal_arg.o grub_emu-normal_cmdline.o grub_emu-normal_command.o grub_emu-normal_completion.o grub_emu-normal_context.o grub_emu-normal_main.o grub_emu-normal_menu.o grub_emu-normal_menu_entry.o grub_emu-normal_misc.o grub_emu-partmap_amiga.o grub_emu-partmap_apple.o grub_emu-partmap_pc.o grub_emu-partmap_sun.o grub_emu-util_console.o grub_emu-util_grub_emu.o grub_emu-util_misc.o grub_emu-util_i386_pc_biosdisk.o grub_emu-util_i386_pc_getroot.o grub_emu-util_powerpc_ieee1275_misc.o
 	$(BUILD_CC) -o $@ $^ $(BUILD_LDFLAGS) $(grub_emu_LDFLAGS)
 
 grub_emu-commands_boot.o: commands/boot.c
@@ -255,6 +255,14 @@
 	set -e; 	  $(BUILD_CC) -Ifs -I$(srcdir)/fs $(BUILD_CPPFLAGS) $(BUILD_CFLAGS) -DGRUB_UTIL=1 $(grub_emu_CFLAGS) -M $< 	  | sed 's,minix\.o[ :]*,grub_emu-fs_minix.o $@ : ,g' > $@; 	  [ -s $@ ] || rm -f $@
 
 -include grub_emu-fs_minix.d
+
+grub_emu-fs_sfs.o: fs/sfs.c
+	$(BUILD_CC) -Ifs -I$(srcdir)/fs $(BUILD_CPPFLAGS) $(BUILD_CFLAGS) -DGRUB_UTIL=1 $(grub_emu_CFLAGS) -c -o $@ $<
+
+grub_emu-fs_sfs.d: fs/sfs.c
+	set -e; 	  $(BUILD_CC) -Ifs -I$(srcdir)/fs $(BUILD_CPPFLAGS) $(BUILD_CFLAGS) -DGRUB_UTIL=1 $(grub_emu_CFLAGS) -M $< 	  | sed 's,sfs\.o[ :]*,grub_emu-fs_sfs.o $@ : ,g' > $@; 	  [ -s $@ ] || rm -f $@
+
+-include grub_emu-fs_sfs.d
 
 grub_emu-fs_ufs.o: fs/ufs.c
 	$(BUILD_CC) -Ifs -I$(srcdir)/fs $(BUILD_CPPFLAGS) $(BUILD_CFLAGS) -DGRUB_UTIL=1 $(grub_emu_CFLAGS) -c -o $@ $<

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Dennis Clarke]

On 10/15/05, Cyril Plisko <cyril.plisko@gmail.com> wrote:
> >
>
> Hi,
>
> apparently sfs addition breaks PPC build. The attached patch fixed it for me,
> but I am not sure I didn't miss something important.
>

Thank you Cyril.  You probably saved me a pile of time scratching my
head and wondering.

Dennis

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Marco Gerards]

Cyril Plisko <cyril.plisko@gmail.com> writes:

> apparently sfs addition breaks PPC build. The attached patch fixed it for me,
> but I am not sure I didn't miss something important.

Right.  I committed a patch that changed powerpc-ieee1275.rmk, but it
seems that powerpc-ieee1275.mk was not regenerated.  If you had ruby
installed that would've happened automatically.

I just committed the regenerated powerpc-ieee1275.mk to CVS.

Thanks,
Marco

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Dennis Clarke]

On 10/16/05, Marco Gerards <metgerards@student.han.nl> wrote:
> Cyril Plisko <cyril.plisko@gmail.com> writes:
>
> > apparently sfs addition breaks PPC build. The attached patch fixed it for me,
> > but I am not sure I didn't miss something important.
>
> Right.  I committed a patch that changed powerpc-ieee1275.rmk, but it
> seems that powerpc-ieee1275.mk was not regenerated.  If you had ruby
> installed that would've happened automatically.
>
> I just committed the regenerated powerpc-ieee1275.mk to CVS.
>

Does this mean that I can pull a new download from CVS and then build
on PowerPC without issue now ?

Dennis

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Cyril Plisko]

On 10/16/05, Dennis Clarke <blastwave@gmail.com> wrote:
> On 10/16/05, Marco Gerards <metgerards@student.han.nl> wrote:
> > Cyril Plisko <cyril.plisko@gmail.com> writes:
> >
> > > apparently sfs addition breaks PPC build. The attached patch fixed it for me,
> > > but I am not sure I didn't miss something important.
> >
> > Right.  I committed a patch that changed powerpc-ieee1275.rmk, but it
> > seems that powerpc-ieee1275.mk was not regenerated.  If you had ruby
> > installed that would've happened automatically.
> >
> > I just committed the regenerated powerpc-ieee1275.mk to CVS.
> >
>
> Does this mean that I can pull a new download from CVS and then build
> on PowerPC without issue now ?
>

Should work [it did for me :) on Peg with Gentoo]

Cyril


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

Re: GRUB 1.91 is released

[Joe Ciccone]

Yoshinori K. Okuji wrote:.

>* Add support for x86_64.
>

I am curious if support for x86_64 still uses -m32 in the build process,
and if so, why?

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Dennis Clarke]

On 10/16/05, Cyril Plisko <cyril.plisko@gmail.com> wrote:
> On 10/16/05, Dennis Clarke <blastwave@gmail.com> wrote:
> > On 10/16/05, Marco Gerards <metgerards@student.han.nl> wrote:
> > > Cyril Plisko <cyril.plisko@gmail.com> writes:
> > >
> > > > apparently sfs addition breaks PPC build. The attached patch fixed it for me,
> > > > but I am not sure I didn't miss something important.
> > >
> > > Right.  I committed a patch that changed powerpc-ieee1275.rmk, but it
> > > seems that powerpc-ieee1275.mk was not regenerated.  If you had ruby
> > > installed that would've happened automatically.
> > >
> > > I just committed the regenerated powerpc-ieee1275.mk to CVS.
> > >
> >
> > Does this mean that I can pull a new download from CVS and then build
> > on PowerPC without issue now ?
> >
>
> Should work [it did for me :) on Peg with Gentoo]
>

Oh .. thank you Cyril !

Which reminds me .. I need to climb back onto the Fedora Core 4 issue
on the ODW.

Dennis

Re: GRUB 1.91 is released

[Marco Gerards]

Joe Ciccone <jciccone@gmail.com> writes:

> Yoshinori K. Okuji wrote:.
>
>>* Add support for x86_64.
>>
>
> I am curious if support for x86_64 still uses -m32 in the build process,
> and if so, why?

It does.  And the reason is that it works like that for me.  My
question: why not?

At the moment GRUB itself (so what you use at boot time) is build as
32 bits binaries.  The utilities to install GRUB are compiled as AMD64
binaries.  So you do not need any 32 bits libraries.

There is a problem, there is a bug in some test that requires 32 bits
binaries.  It's a bug and it will be fixed.

So I do not see a reason why we shouldn't use -m32.

--
Marco

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Marco Gerards]

Cyril Plisko <cyril.plisko@gmail.com> writes:

>> > I just committed the regenerated powerpc-ieee1275.mk to CVS.
>> >
>>
>> Does this mean that I can pull a new download from CVS and then build
>> on PowerPC without issue now ?
>>
>
> Should work [it did for me :) on Peg with Gentoo]

How does it work for you on your pegasos and what kind of pegasos do
you have?  We receive quite little feedback and I don't know many
people using GRUB 2 on the pegasos.  So I'm quite interested in bug
reports, missing features, etc. (also for other systems of course)

Thanks,
Marco

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Cyril Plisko]

On 10/16/05, Marco Gerards <metgerards@student.han.nl> wrote:
> Cyril Plisko <cyril.plisko@gmail.com> writes:
>
> >> > I just committed the regenerated powerpc-ieee1275.mk to CVS.
> >> >
> >>
> >> Does this mean that I can pull a new download from CVS and then build
> >> on PowerPC without issue now ?
> >>
> >
> > Should work [it did for me :) on Peg with Gentoo]
>
> How does it work for you on your pegasos and what kind of pegasos do
> you have?  We receive quite little feedback and I don't know many
> people using GRUB 2 on the pegasos.  So I'm quite interested in bug
> reports, missing features, etc. (also for other systems of course)

It compiles (under Linux) and boots into GRUB prompt. I didn't play
with loading Linux kernel yet. Frankly speaking my primary interest
is loading Solaris (unfortunately we are quite far from it yet), so I never
invested too much time into loadin Linux with it.

I'm think other people from Polaris (Solaris/PPC) community on this
list may be able to provide more feedback.

Regards,
        Cyril

>
> Thanks,
> Marco
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Marco Gerards]

Cyril Plisko <cyril.plisko@gmail.com> writes:

> On 10/16/05, Marco Gerards <metgerards@student.han.nl> wrote:
>> Cyril Plisko <cyril.plisko@gmail.com> writes:
>>
>> >> > I just committed the regenerated powerpc-ieee1275.mk to CVS.
>> >> >
>> >>
>> >> Does this mean that I can pull a new download from CVS and then build
>> >> on PowerPC without issue now ?
>> >>
>> >
>> > Should work [it did for me :) on Peg with Gentoo]
>>
>> How does it work for you on your pegasos and what kind of pegasos do
>> you have?  We receive quite little feedback and I don't know many
>> people using GRUB 2 on the pegasos.  So I'm quite interested in bug
>> reports, missing features, etc. (also for other systems of course)
>
> It compiles (under Linux) and boots into GRUB prompt. I didn't play
> with loading Linux kernel yet. Frankly speaking my primary interest
> is loading Solaris (unfortunately we are quite far from it yet), so I never
> invested too much time into loadin Linux with it.

How is solaris booted?  Are you a solaris developer?  If so it might
be interesting to find a group of people interested in multiboot,
assuming solaris developers are interested in that.

--
Marco

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Cyril Plisko]

On 10/16/05, Marco Gerards <metgerards@student.han.nl> wrote:
> Cyril Plisko <cyril.plisko@gmail.com> writes:
>
> > On 10/16/05, Marco Gerards <metgerards@student.han.nl> wrote:
> >> Cyril Plisko <cyril.plisko@gmail.com> writes:
> >>
> >> >> > I just committed the regenerated powerpc-ieee1275.mk to CVS.
> >> >> >
> >> >>
> >> >> Does this mean that I can pull a new download from CVS and then build
> >> >> on PowerPC without issue now ?
> >> >>
> >> >
> >> > Should work [it did for me :) on Peg with Gentoo]
> >>
> >> How does it work for you on your pegasos and what kind of pegasos do
> >> you have?  We receive quite little feedback and I don't know many
> >> people using GRUB 2 on the pegasos.  So I'm quite interested in bug
> >> reports, missing features, etc. (also for other systems of course)
> >
> > It compiles (under Linux) and boots into GRUB prompt. I didn't play
> > with loading Linux kernel yet. Frankly speaking my primary interest
> > is loading Solaris (unfortunately we are quite far from it yet), so I never
> > invested too much time into loadin Linux with it.
>
> How is solaris booted?  Are you a solaris developer?  If so it might
> be interesting to find a group of people interested in multiboot,
> assuming solaris developers are interested in that.
>

Marco,

yes I am a Solaris developer. [Open]Solaris x86 uses grub legacy to boot.
And our plans for Polaris involve using GRUB2 in order to reuse as much
code as possible. Multiboot naturally is a part of the game. And extending
it to PPC arch is a necessary step. I heard that there are plans to eventually
migrate SPARC boot to GRUB too.

Cyril


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

Re: [SFS breaks PPC build] Re: GRUB 1.91 is released

[Marco Gerards]

Cyril Plisko <cyril.plisko@gmail.com> writes:


Hi Cyril,

> yes I am a Solaris developer. [Open]Solaris x86 uses grub legacy to boot.
> And our plans for Polaris involve using GRUB2 in order to reuse as much
> code as possible. Multiboot naturally is a part of the game. And extending
> it to PPC arch is a necessary step. I heard that there are plans to eventually
> migrate SPARC boot to GRUB too.

As GRUB 2 is ported to the ultra sparc64 it might be wise for us (GRUB
and solaris developers) to talk about multiboot.  Of course other
parties might be interested as well (the Hurd uses multiboot, for
example).

Anyway, what is important for you is that we are thinking about a
portable multiboot and that there is also a sparc port in the making.

--
Marco

Sparc bootblock [Was: SFS breaks PPC build ]

[Bart Grantham]

Marco Gerards wrote:

 > As GRUB 2 is ported to the ultra sparc64 it might be wise for us (GRUB
 > and solaris developers) to talk about multiboot.  Of course other
 > parties might be interested as well (the Hurd uses multiboot, for
 > example).
 >
 > Anyway, what is important for you is that we are thinking about a
 > portable multiboot and that there is also a sparc port in the making.

Speaking of which, after refreshing my forth skills, I've started work 
on the sparc bootloader.  I have it reading data from disk into mem, but 
I'm not sure if I want to share it quite yet.  Before sharing it I'd 
like to:

- have it verify that the file at the configured sector(s) is an ELF file
- follow through and make sure it properly boots an ELF image (right now 
it only gets it into memory)
- clean up the code a bunch

I'll hand it over once I get those done.  After that, the features I'd 
like to work on are:

- support of a sector-sized lookup table indicating the layout of the 
grub image on disk, allowing for more flexible configuration
- support of a sector-sized lookup table indicating additional forth 
bytecode, providing for extensibility just in case.
- verify that the code works on PPC, and if not, try to make it work so 
that there's a unified bootblock [not sure if this is reasonable as I'm 
not as familiar with how PPC OF boots... how similiar is it to Sparc?]
- same for sparc32

BG

Re: Sparc bootblock

[Marco Gerards]

Bart Grantham <bart-grubdevel@bartgrantham.com> writes:

> - verify that the code works on PPC, and if not, try to make it work
> so that there's a unified bootblock [not sure if this is reasonable as
> I'm not as familiar with how PPC OF boots... how similiar is it to
> Sparc?]

On the Open Firmware implementations on the PPC machines I worked with
you can load an ELF file directly.  Open Firmware has support for
reading from block devices, parsing partition maps and it has support
for some filesystems.

So at least of the New World Mac, the Pegasos, etc. this is not
required.  Perhaps we need such bootblock for the old world mac...

--
Marco

Re: Sparc bootblock

[Cyril Plisko]

On 10/17/05, Marco Gerards <metgerards@student.han.nl> wrote:
> Bart Grantham <bart-grubdevel@bartgrantham.com> writes:
>
> > - verify that the code works on PPC, and if not, try to make it work
> > so that there's a unified bootblock [not sure if this is reasonable as
> > I'm not as familiar with how PPC OF boots... how similiar is it to
> > Sparc?]
>
> On the Open Firmware implementations on the PPC machines I worked with
> you can load an ELF file directly.  Open Firmware has support for
> reading from block devices, parsing partition maps and it has support
> for some filesystems.
>
> So at least of the New World Mac, the Pegasos, etc. this is not
> required.  Perhaps we need such bootblock for the old world mac...
>

AFAIK OpenFirmware per se does not require all these fancy filesystems
to be supported. CHRP machines grok some filesystems and Pegasos'
SmartFirmware took it much further adding support for many types
of filesystem. The SPARC OpenBoot (Sun's OpenFirmware implementation)
isn't like that. IIRC it hardly understands UFS. The usual way to boot on SPARC
is to load a bootblock from the known disk position (the first sectors
usually) and
to pass control to it. Much like PC BIOS does.

Cyril

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

Re: Sparc bootblock [Was: SFS breaks PPC build ]

[Andrei Warkentin]

Can OpenBoot directly boot ELF or COFF images? I looked at SILO and  
it seems it uses a 512-byte boot block to load second stage etc.

On Oct 17, 2005, at 2:30 AM, Bart Grantham wrote:

> Marco Gerards wrote:
>
> > As GRUB 2 is ported to the ultra sparc64 it might be wise for us  
> (GRUB
> > and solaris developers) to talk about multiboot.  Of course other
> > parties might be interested as well (the Hurd uses multiboot, for
> > example).
> >
> > Anyway, what is important for you is that we are thinking about a
> > portable multiboot and that there is also a sparc port in the  
> making.
>
> Speaking of which, after refreshing my forth skills, I've started  
> work on the sparc bootloader.  I have it reading data from disk  
> into mem, but I'm not sure if I want to share it quite yet.  Before  
> sharing it I'd like to:
>
> - have it verify that the file at the configured sector(s) is an  
> ELF file
> - follow through and make sure it properly boots an ELF image  
> (right now it only gets it into memory)
> - clean up the code a bunch
>
> I'll hand it over once I get those done.  After that, the features  
> I'd like to work on are:
>
> - support of a sector-sized lookup table indicating the layout of  
> the grub image on disk, allowing for more flexible configuration
> - support of a sector-sized lookup table indicating additional  
> forth bytecode, providing for extensibility just in case.
> - verify that the code works on PPC, and if not, try to make it  
> work so that there's a unified bootblock [not sure if this is  
> reasonable as I'm not as familiar with how PPC OF boots... how  
> similiar is it to Sparc?]
> - same for sparc32
>
> BG
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>

Re: Sparc bootblock

[Andrei Warkentin]

IANA mac guru, but the OF in Old Worlds (OF 1.0.5) has support for  
reading from block devices, parsing *some* filesystems (this but is  
pretty crippled - for example, no fragmentation can occur on a FAT  
floppy, because it just loads data linearly). It can boot from a  
partition 0 boot block (example: first stage QUIK boot block for  
Linux), or from an XCOFF file (example: ofwboot.xcf from NetBSD/ 
OpenBSD). The NetBSD ofwboot page goes into a lot of gory details of  
what the problems are with Old World OF =) - apparently the biggest  
one are rather inconvenient load-base and real-base. It certainly  
understands iso9660 and FAT (somewhat).

On Oct 17, 2005, at 3:20 AM, Marco Gerards wrote:

> Bart Grantham <bart-grubdevel@bartgrantham.com> writes:
>
>
>> - verify that the code works on PPC, and if not, try to make it work
>> so that there's a unified bootblock [not sure if this is  
>> reasonable as
>> I'm not as familiar with how PPC OF boots... how similiar is it to
>> Sparc?]
>>
>
> On the Open Firmware implementations on the PPC machines I worked with
> you can load an ELF file directly.  Open Firmware has support for
> reading from block devices, parsing partition maps and it has support
> for some filesystems.
>
> So at least of the New World Mac, the Pegasos, etc. this is not
> required.  Perhaps we need such bootblock for the old world mac...
>
> --
> Marco
>
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>

Re: Sparc bootblock [Was: SFS breaks PPC build ]

[Vincent Pelletier]

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

Bart Grantham wrote:
> - have it verify that the file at the configured sector(s) is an ELF file

Quite easy if we stick to the header signature.

> - follow through and make sure it properly boots an ELF image (right now
> it only gets it into memory)

I think there are 2 ways :
-write your own Forth ELF relocating code (might be fun, but beside that...)
-have the "init-program" command do this work for you, which require you
to load the image where "boot net" loads it (or maybe other commands,
but for now I only know about boot net as it is the only way to
currently boot grub2 on sparc64 ;) ).

> - verify that the code works on PPC, and if not, try to make it work so
> that there's a unified bootblock [not sure if this is reasonable as I'm
> not as familiar with how PPC OF boots... how similiar is it to Sparc?]

I think this one can't be done without making the FCode grow quite big.

> - same for sparc32

I would be interested if the port could be unified in 32bits. For now I
built it 64bits - don't ask why :) - but if a 32bits build can work both
on sparc32 and sparc64, I think it would be great for maintenance.

Vincent Pelletier

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Sparc bootblock [Was: SFS breaks PPC build ]

[Bart Grantham]

Vincent Pelletier wrote:

> Bart Grantham wrote:
> 
>>- have it verify that the file at the configured sector(s) is an ELF file
> 
> Quite easy if we stick to the header signature.
> 

Well, I was referring to the ELF magic number rather than the multiboot 
magic number.  I'll probably check the first unconditionally and the 
second can be overridden with a boot parameter.

>>- follow through and make sure it properly boots an ELF image (right now
>>it only gets it into memory)
> 
> I think there are 2 ways :
> -write your own Forth ELF relocating code (might be fun, but beside that...)
> -have the "init-program" command do this work for you, which require you
> to load the image where "boot net" loads it (or maybe other commands,
> but for now I only know about boot net as it is the only way to
> currently boot grub2 on sparc64 ;) ).

Heh.  I looked into this and I'm definitely going the init-program 
route.  I don't think that there's a platform independent way of doing 
relocation and I don't really feel that it's in the spirit of OF 
anyways.  Besides, writing F-Code is mind-bending enough as it is.  :)

>>- verify that the code works on PPC, and if not, try to make it work so
>>that there's a unified bootblock [not sure if this is reasonable as I'm
>>not as familiar with how PPC OF boots... how similiar is it to Sparc?]
> 
> I think this one can't be done without making the FCode grow quite big.

Perhaps.  But I'll try for it anyways because if it's possible, I'd like 
to have it as a workable alternative for PPC users who aren't using a 
filesystem their PROM understands.  For example, someone porting ReactOS 
(NTFS) or HaikuOS (BFS) to PPC.  (Hey!  Don't laugh... it could happen! ;) )

>>- same for sparc32
> 
> I would be interested if the port could be unified in 32bits.

Me too.  Or at least try to get the two platforms as close as possible. 
  I'll keep you abreast of what I discover.

Bart

Re: Sparc bootblock

[Marco Gerards]

Bart Grantham <bart-grubdevel@bartgrantham.com> writes:

> Heh.  I looked into this and I'm definitely going the init-program
> route.  I don't think that there's a platform independent way of doing
> relocation and I don't really feel that it's in the spirit of OF
> anyways.  Besides, writing F-Code is mind-bending enough as it is.  :)

For loading grubof you do not need to relocate anything.

>>>- verify that the code works on PPC, and if not, try to make it work so
>>>that there's a unified bootblock [not sure if this is reasonable as I'm
>>>not as familiar with how PPC OF boots... how similiar is it to Sparc?]
>> I think this one can't be done without making the FCode grow quite
>> big.
>
> Perhaps.  But I'll try for it anyways because if it's possible, I'd
> like to have it as a workable alternative for PPC users who aren't
> using a filesystem their PROM understands.  For example, someone
> porting ReactOS (NTFS) or HaikuOS (BFS) to PPC.  (Hey!  Don't
> laugh... it could happen! ;) )

In that case people usually create a filesystem and put GRUB on it.

--
Marco

Re: GRUB 1.91 is released

[Joe Ciccone]

Marco Gerards wrote:

>Joe Ciccone <jciccone@gmail.com> writes:
>
>  
>
>>Yoshinori K. Okuji wrote:.
>>
>>    
>>
>>>* Add support for x86_64.
>>>
>>>      
>>>
>>I am curious if support for x86_64 still uses -m32 in the build process,
>>and if so, why?
>>    
>>
>My question: why not?
>  
>
I just created a simply dummy program and tried to compile it with a
64bit only compiler, cross-compiling or not, the build of grub fails
with -m32, just as the build of this simple program fails with -m32. Now
that you have an example of that happens in a Pure64bit enviorment with
only 64 bit libs available to the compiler. Do you have any ideas on
what can be done to make grub compile and work under these conditions?

lfs:~$ echo "int main () {}" > dummy.c
lfs:~$ $CC -m32 dummy.c
/home/lfs/cross-tools/bin/../lib/gcc/x86_64-pc-linux-gnu/4.0.2/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible
/home/lfs/cross-tools/bin/../lib/gcc/x86_64-pc-linux-gnu/4.0.2/./libgcc.a
when searching for -lgcc
/home/lfs/cross-tools/bin/../lib/gcc/x86_64-pc-linux-gnu/4.0.2/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible
/home/lfs/cross-tools/bin/../lib/gcc/x86_64-pc-linux-gnu/4.0.2/libgcc.a
when searching for -lgcc
/home/lfs/cross-tools/bin/../lib/gcc/x86_64-pc-linux-gnu/4.0.2/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible
/cross-tools/lib/gcc/x86_64-pc-linux-gnu/4.0.2/./libgcc.a when searching
for -lgcc
/home/lfs/cross-tools/bin/../lib/gcc/x86_64-pc-linux-gnu/4.0.2/../../../../x86_64-pc-linux-gnu/bin/ld:
skipping incompatible
/cross-tools/lib/gcc/x86_64-pc-linux-gnu/4.0.2/libgcc.a when searching
for -lgcc
/home/lfs/cross-tools/bin/../lib/gcc/x86_64-pc-linux-gnu/4.0.2/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -lgcc
collect2: ld returned 1 exit status

Re: GRUB 1.91 is released

[Marco Gerards]

Joe Ciccone <jciccone@gmail.com> writes:

>>>I am curious if support for x86_64 still uses -m32 in the build process,
>>>and if so, why?
>>>    
>>>
>>My question: why not?
>>  
>>
> I just created a simply dummy program and tried to compile it with a
> 64bit only compiler, cross-compiling or not, the build of grub fails
> with -m32, just as the build of this simple program fails with -m32. Now
> that you have an example of that happens in a Pure64bit enviorment with
> only 64 bit libs available to the compiler. Do you have any ideas on
> what can be done to make grub compile and work under these conditions?
>
> lfs:~$ echo "int main () {}" > dummy.c
> lfs:~$ $CC -m32 dummy.c

Right, but this is not what I am talking about.  GRUB is not linked to
any library so your test is not relevant.

--
Marco