From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: partition layouts
Date: Tue, 05 Apr 2005 09:00:55 +0200 [thread overview]
Message-ID: <87sm25aes8.fsf@student.han.nl> (raw)
In-Reply-To: <78d5a6962754dbc4b0f64fb15ffd7b79@penguinppc.org> (Hollis Blanchard's message of "Mon, 4 Apr 2005 19:38:29 -0500")
Hollis Blanchard <hollis@penguinppc.org> writes:
> 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.
Sounds fine to me, assuming things work like we discussed about.
> Can we have a shortcut to avoid specifying that "(hd,7)/" part
> repeatedly? I think that was the "root" command in GRUB Legacy, which
> was replaced by the "prefix" environment variable? But as I mentioned,
> "prefix" doesn't have the meaning we're looking for here...
There is the root variable, but IIRC there were some problems or so.
Anyway, it is how it will work. :)
> The other possibility is to have all of /boot as a firmware-native
> filesystem. I think that's not ideal though, because those filesystems
> (HFS+, FAT) might not support features like symlinks or Unix-style
> permissions, or may not be as well-tested as Linux-native filesystems.
HFS+ supports symlinks, FAT does not (unless you use UMSDOS, which is
not supported). For every symlink capable filesystem GRUB 2 supports,
symlink support was implemented.
Personally I do not care very much how it will work in practise. The
main important thing for me is that we can support both of your
proposals. I think we just have to try both, when possible on many
different machines.
Thanks,
Marco
next prev parent reply other threads:[~2005-04-05 6:39 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
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 ` Marco Gerards [this message]
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=87sm25aes8.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--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.