From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Partition modules
Date: Thu, 18 Nov 2004 08:16:54 +0000 [thread overview]
Message-ID: <87oehv4lmx.fsf@marco.marco-g.com> (raw)
In-Reply-To: <FDD576B7-3914-11D9-99D3-000A95A0560C@penguinppc.org> (Hollis Blanchard's message of "Wed, 17 Nov 2004 21:50:30 -0600")
Hollis Blanchard <hollis@penguinppc.org> writes:
> I do have an objection here: members like "bsd_type" don't belong in a
> generic struct, but rather in grub_partition_bsd_type. I believe
> grub_partition should be the abstraction, i.e. what defines a
> partition in the general sense. start, len, and index are obviously
> good; offset is compensating for a DOS issue, though at least it has
> (irrelevant) meaning for an Apple map... but ext_offset and these dos_
> and bsd_ things don't belong here IMHO.
Ok.
> Also, there were a number of whitespace-only lines in your patch; a
> simple regex should show you where.
Ok.
> I'm seeing a crash on both briQ and my G3, so I'm sprinkling printfs
> now...
Does the PC partition map work on the briQ now?
Thanks,
Marco
next prev parent reply other threads:[~2004-11-18 8:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 19:25 Partition modules Marco Gerards
2004-11-18 3:50 ` Hollis Blanchard
2004-11-18 5:09 ` Hollis Blanchard
2004-11-18 8:13 ` Marco Gerards
2004-11-18 8:16 ` Marco Gerards [this message]
2004-11-18 9:32 ` Yoshinori K. Okuji
2004-11-18 10:46 ` Marco Gerards
2004-11-18 11:20 ` Yoshinori K. Okuji
2004-11-18 13:58 ` Marco Gerards
2004-11-18 9:28 ` Yoshinori K. Okuji
2004-11-18 10:40 ` Marco Gerards
2004-11-23 1:29 ` Timothy Baldwin
2004-11-23 15:12 ` Marco Gerards
2004-11-24 19:15 ` Marco Gerards
2004-11-30 17:55 ` Marco Gerards
2004-12-03 17:18 ` Yoshinori K. Okuji
2004-12-04 15:39 ` Marco Gerards
2004-12-04 17:03 ` Yoshinori K. Okuji
[not found] ` <200412041230.17136.mjflick@gnu.org>
2004-12-04 18:41 ` 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=87oehv4lmx.fsf@marco.marco-g.com \
--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.