From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Host filesystem access
Date: Fri, 18 May 2007 08:59:45 +0200 [thread overview]
Message-ID: <874pma39cu.fsf@xs4all.nl> (raw)
In-Reply-To: <20070518064837.GC1783@aragorn> (Robert Millan's message of "Fri, 18 May 2007 08:48:37 +0200")
Robert Millan <rmh@aybabtu.com> writes:
> On Thu, May 17, 2007 at 11:28:12PM +0200, Marco Gerards wrote:
>> + grub_error (GRUB_ERR_BAD_FS, "not a affs filesystem");
>> + grub_error (GRUB_ERR_BAD_FS, "not a hfsplus filesystem");
>> + grub_error (GRUB_ERR_BAD_FS, "not a sfs filesystem");
>
> I think these should be "an" (but not sure about all them, any native English
> speaker around?).
Ehm, yes, I think so :-)
>> diff -u -p -u -p -r1.34 grub-emu.c
>> --- util/grub-emu.c 16 May 2007 21:38:44 -0000 1.34
>> +++ util/grub-emu.c 17 May 2007 21:17:02 -0000
>> @@ -185,6 +185,8 @@ main (int argc, char *argv[])
>> /* XXX: This is a bit unportable. */
>> grub_util_biosdisk_init (args.dev_map);
>>
>> + grub_hostfs_init ();
>> +
>> grub_init_all ();
>
> I find it counter-intuitive that grub_init_all doesn't imply grub_hostfs_init;
> if there's a design reason for this, maybe the function should be renamed ?
> (how about grub_filesystems_init + grub_partmaps_init ?)
The reason why I did this is that hostfs is not a module.
grub_init_all initializes all modules, there is no way you can split
this up in an easy way.
The main thing I had some doubts on was if the dummy disk driver is
way too ugly or not.
--
Marco
next prev parent reply other threads:[~2007-05-18 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 21:28 Host filesystem access Marco Gerards
2007-05-18 6:48 ` Robert Millan
2007-05-18 6:59 ` Marco Gerards [this message]
2007-05-18 16:08 ` Robert Millan
2007-05-18 11:35 ` Bruno Wolff III
2007-05-18 14:08 ` Jan C. Kleinsorge
2007-05-18 16:07 ` Robert Millan
2007-08-02 17:27 ` Marco Gerards
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=874pma39cu.fsf@xs4all.nl \
--to=mgerards@xs4all.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.