All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>,
	Hollis Blanchard <hollisb@us.ibm.com>
Cc: Manoel <mrabran@linux.vnet.ibm.com>,
	Carlos Roberto do Nascimento Costa <crncosta@linux.vnet.ibm.com>
Subject: Re: PPC64
Date: Thu, 23 Oct 2008 12:52:11 -0400	[thread overview]
Message-ID: <1224780731.17766.23.camel@dv> (raw)
In-Reply-To: <1224774409.16720.22.camel@localhost.localdomain>

On Thu, 2008-10-23 at 10:06 -0500, Hollis Blanchard wrote:
> On Thu, 2008-10-23 at 01:25 -0400, Pavel Roskin wrote:
> > 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?

HFS support is marked experimental in Linux 2.6.27, unlike HFSPLUS.  I'm
not sure about the quality of fsck.hfs.  However, it's not that I
distrust any drivers or utilities.  The HFS driver may be missing from
the kernel.  It doesn't even have to be a Linux kernel.

> > 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"?

It would fit.  But it's better to keep modules and grub.cfg on a
filesystem that is easier to access.

> 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.

I can imagine that there are some real issues why the HFS boot partition
is not mounted.  HFS may lack some security mechanisms that other
filesystems have.  It may not have a good fsck.  Anyway, whatever the
reasons, I don't think switching from yaboot to GRUB would change those
reasons.  For GRUB to be a compelling replacement, it would be
beneficial if it could fit the existing systems.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-10-23 16:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 20:52 PPC64 Hollis Blanchard
2008-10-21 22:04 ` PPC64 Pavel Roskin
2008-10-21 22:40   ` PPC64 Hollis Blanchard
2008-10-23  5:25     ` PPC64 Pavel Roskin
2008-10-23 15:06       ` PPC64 Hollis Blanchard
2008-10-23 16:52         ` Pavel Roskin [this message]
2008-10-23 18:00 ` PPC64 Manoel
2008-10-23 19:08   ` PPC64 Hollis Blanchard
2008-10-24 12:10     ` PPC64 Manoel
2008-10-24 14:51       ` PPC64 Hollis Blanchard
2008-10-24 21:53     ` PPC64 Manoel
2008-10-27 17:19       ` PPC64 Pavel Roskin
2008-11-04 16:05         ` PPC64 Manoel
2008-11-04 16:12           ` PPC64 Hollis Blanchard
2008-11-04 18:18             ` PPC64 mlongcall gcc flag Manoel
2008-11-04 18:21               ` Manoel
2008-11-04 19:16               ` Robert Millan
2008-11-04 23:48               ` Pavel Roskin
2008-11-05  9:43                 ` Robert Millan
2008-11-05 15:35                   ` Pavel Roskin
2008-11-05 17:25                 ` Hollis Blanchard
2008-11-05 19:27                   ` Manoel
2008-11-06 15:12                   ` Robert Millan
2008-11-06 17:42                     ` Manoel
  -- strict thread matches above, loose matches on Subject: below --
2008-10-27  8:04 PPC64 rubisher
2008-10-20 19:18 PPC64 Manoel
2008-10-20 19:32 ` PPC64 Hollis Blanchard
2008-10-21 16:43   ` PPC64 Manoel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1224780731.17766.23.camel@dv \
    --to=proski@gnu.org \
    --cc=crncosta@linux.vnet.ibm.com \
    --cc=grub-devel@gnu.org \
    --cc=hollisb@us.ibm.com \
    --cc=mrabran@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.