From: Johan Rydberg <jrydberg@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB 1.95 cannot read the ufs filesystem
Date: Mon, 16 Apr 2007 14:28:18 +0200 [thread overview]
Message-ID: <87y7ksqza5.fsf@gnu.org> (raw)
In-Reply-To: <000001c77d36$d27e7f80$030010ac@ozeki> (Hitoshi Ozeki's message of "Fri, 13 Apr 2007 04:14:29 +0900")
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
"Hitoshi Ozeki" <h-ozeki@ck2.so-net.ne.jp> writes:
> Hello, all.
>
> GRUB 1.95 cannot read the ufs filesystem.
> Because, 1.95 mistakes a usage of char pointer.
> This patch fixes this problem, and make it a bit better.
Could you maybe point out the problem for us? Personally, I think the
use of pointers make the code more complex.
~j
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-04-16 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 19:14 GRUB 1.95 cannot read the ufs filesystem Hitoshi Ozeki
2007-04-16 12:26 ` Johan Rydberg
2007-04-16 12:28 ` Johan Rydberg [this message]
2007-04-17 18:31 ` Hitoshi Ozeki
2007-04-18 10:48 ` Johan Rydberg
2007-04-18 10:49 ` Johan Rydberg
2007-04-18 21:13 ` Hitoshi Ozeki
2007-09-03 20:49 ` Yoshinori K. Okuji
2007-09-04 1:57 ` Bean
2007-09-19 2:35 ` Hitoshi Ozeki
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=87y7ksqza5.fsf@gnu.org \
--to=jrydberg@gnu.org \
--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.