Re: PPC64

[Hollis Blanchard]

On Thu, 2008-10-23 at 01:25 -0400, Pavel Roskin wrote:
> Quoting Hollis Blanchard <address@hidden>:
> > On IBM POWER servers, there is no HFS partition at all. Instead, there
> > is a "raw" partition onto which you dd an ELF file. Firmware loads the
> > whole thing into memory and jumps at offset 0. Traditionally, yaboot is
> > installed there, and when it runs it does a shoddy job of trying to walk
> > the (DOS) partition table, searching for /etc/yaboot.conf.
> >
> > Once GRUB replaces yaboot/ybin we can happily wave both of these
> > anachronisms goodbye. Firmware on both systems is fully capable of
> > loading ELF files from a filesystem, and since it's on a filesystem
> > there is no need to embed anything or search anywhere: all files
> > (grub.cfg and the modules) should be placed adjacent to the executable.
> 
> Actually, I would prefer all files that don't have to be on HFS or on  
> the raw partition to be on the native partition, so that they can be  
> easily accessed.  That includes grub.cfg.

FWIW, I ran for years with an HFS partition "natively" mounted
on /boot/grub, and I never experienced any instability. Do you have
reason (other than hearsay) to mistrust the Linux HFS driver?

> > As for embedding the path in the executable itself, that's a nice idea
> > until you copy the executable to another system or move your hard disk
> > to another system where devices have different Open Firmware paths and
> > aliases. Another big pain point is building bootable CDs, since these
> > also unfortunately cannot make assumptions about the Open Firmware
> > devices available.
> 
> We can use UUIDs now.  That should alleviate most issues.

Agreed.

> > Just put all the files in the same directory on a real filesystem and be
> > happy. I know I am. :)
> 
> I'm afraid I'm missing something.
> 
> Anyway, I think it's too much to ask from users to change the existing  
> partitioning or mount points.  GRUB can be more compatible with both  
> its i386 implementation and with yaboot by keeping modules in  
> /boot/grub on ext2 or another native filesystem and placing the  
> minimal core to the machine specific boot partition (whether it's HFS  
> or raw or something else).

Actually I don't remember if I had to change the partitioning scheme at
all: isn't GRUB + modules small enough to fit into the typical "ybin
boot partition"?

I don't think asking the user to add an entry to /etc/fstab is an
onerous restriction. After all, they are trying to replace their
distribution's bootloader in the first place, so they almost certainly
have some familiarity with the boot process. Once distributions use
GRUB2 of course, no user intervention would be required.

My basic point is that requiring grub-install and this mystical "hidden
partition in the mist" is just silly. It's completely unnecessary on
systems with filesystem support in firmware, and it's silly to
artificially limit those systems by imposing historical x86 restrictions
onto them.

-- 
Hollis Blanchard
IBM Linux Technology Center