From: Vernon Mauery <vernon-grub@mauery.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: partition layouts
Date: Mon, 04 Apr 2005 21:55:38 -0700 [thread overview]
Message-ID: <42521A4A.6040409@mauery.com> (raw)
In-Reply-To: <78d5a6962754dbc4b0f64fb15ffd7b79@penguinppc.org>
Hollis Blanchard wrote:
> I've been thinking about how to install grub2 on an Open Firmware
> system. Here's one possibility:
> /boot -- Linux-native filesystem (e.g. ext3)
> holds kernels, initrd, etc
> /boot/grub -- firmware-native filesystem (on Mac HFS+, on others
> FAT, etc)
> holds grub executable, grub.cfg, modules
>
> The grub ELF file must live on a firmware-native filesystem. When run,
> it can find out what partition it was booted from, so that is a natural
> place to load grub.cfg from as well (and why not modules while we're at
> it?). Thus this is the value of the "prefix" GRUB environment variable.
Putting a restraint that says /boot/grub must be a separate partition doesn't sound like a good idea. It just clutters the partition table with another small partition.
If all it gains us is that we know where we booted from, we still need to know where /boot is. I don't see what this gains us -- the root command or prefix variable is still required. It sounds to me that if you want to have a firmware native partition type, having all of /boot be that type would be preferred.
--Vernon
next prev parent reply other threads:[~2005-04-05 4:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 0:38 partition layouts Hollis Blanchard
2005-04-05 4:55 ` Vernon Mauery [this message]
2005-04-05 7:02 ` Marco Gerards
2005-04-05 13:40 ` Vernon Mauery
2005-04-05 13:50 ` Marco Gerards
2005-04-05 15:50 ` Hollis Blanchard
2005-04-05 15:47 ` partition layouts - separate /boot Hollis Blanchard
2005-04-05 5:41 ` partition layouts Yoshinori K. Okuji
2005-04-05 16:01 ` Hollis Blanchard
2005-04-05 16:45 ` Marco Gerards
2005-04-05 22:53 ` partition layouts - "root" Hollis Blanchard
2005-04-06 6:32 ` Marco Gerards
2005-04-06 14:52 ` Hollis Blanchard
2005-04-06 15:43 ` Antoine Terrienne
2005-04-07 0:02 ` Hollis Blanchard
2005-04-07 14:17 ` Yoshinori K. Okuji
2005-04-07 14:37 ` Marco Gerards
2005-04-07 16:46 ` Yoshinori K. Okuji
2005-04-08 6:39 ` Marco Gerards
2005-04-12 10:15 ` Yoshinori K. Okuji
2005-04-12 11:13 ` Marco Gerards
2005-04-14 3:46 ` Hollis Blanchard
2005-04-14 12:15 ` Yoshinori K. Okuji
2005-04-14 16:30 ` Marco Gerards
2005-04-05 7:00 ` partition layouts Marco Gerards
2005-04-05 15:38 ` partition layouts - symlinks Hollis Blanchard
2005-04-05 7:58 ` partition layouts Tomas 'Ebik' Ebenlendr
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=42521A4A.6040409@mauery.com \
--to=vernon-grub@mauery.com \
--cc=grub-devel@gnu.org \
/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.