From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB2: *BSD and more patch
Date: Sun, 21 Mar 2004 17:11:52 +0100 [thread overview]
Message-ID: <200403211711.52377.okuji@enbug.org> (raw)
In-Reply-To: <405CED3B.4090407@ciam.ru>
On Sunday 21 March 2004 02:17, Sergey Matveychuk wrote:
> @@ -716,9 +773,6 @@ pupa_util_biosdisk_get_pupa_dev (const c
> return 0;
> }
>
> - if (! S_ISBLK (st.st_mode))
> - return make_device_name (drive, -1, -1);
> -
This part is not good. The problem here is that we want to support
installing GRUB into a normal file as well as a device file.
So what I said to you was wrong. The check about a block device is
sometimes very important. In FreeBSD, what is the right way to
distinguish a device file from a normal file?
> +#ifdef HAVE_MEMALIGN
> p = memalign (align, size);
> +#else
> + p = malloc(size);
> +#endif
I don't agree on this one. Please implement memalign correctly. It's not
so difficult. Probably it can be like this (not tested):
p = malloc((size + align - 1) & ~(align - 1));
if (! p)
return 0;
return (p + align - 1) & ~(align - 1);
It might be possible to find a better implementation, if you see glibc.
BTW, I confirmed that you haven't assigned your copyright on GRUB to the
FSF yet. For a GNU project, it is a custom to assign your copyright to
the FSF, so that the FSF can fight instead of you in a court when
someone claims that our software is illegal. Also, this step of a
copyright assignment makes sure that your contribution will be free in
freedom forever. So, would you like to sign a copyright assignment for
GRUB? If you need more information, don't hesitate to ask me. We can
talk privately if you want.
Okuji
next prev parent reply other threads:[~2004-03-21 16:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 8:15 GRUB2: *BSD and more patch Sergey Matveychuk
2004-03-18 12:31 ` Yoshinori K. Okuji
2004-03-19 21:24 ` Sergey Matveychuk
2004-03-19 21:34 ` Johan Rydberg
2004-03-19 21:42 ` Marco Gerards
2004-03-19 21:56 ` Sergey Matveychuk
2004-03-19 22:22 ` Marco Gerards
2004-03-19 23:24 ` Sergey Matveychuk
2004-03-19 23:55 ` Marco Gerards
2004-03-20 0:45 ` Sergey Matveychuk
2004-03-20 10:29 ` Jeroen Dekkers
2004-03-20 18:30 ` Sergey Matveychuk
2004-03-20 19:43 ` Marco Gerards
2004-03-21 1:17 ` Sergey Matveychuk
2004-03-21 1:45 ` Marco Gerards
2004-03-21 2:18 ` Sergey Matveychuk
2004-03-21 3:30 ` Marco Gerards
2004-03-21 16:11 ` Yoshinori K. Okuji [this message]
2004-03-22 8:20 ` Sergey Matveychuk
2004-03-22 13:49 ` Yoshinori K. Okuji
2004-03-22 14:26 ` Jeroen Dekkers
2004-03-22 15:23 ` Yoshinori K. Okuji
2004-03-22 21:05 ` Sergey Matveychuk
2004-03-22 22:03 ` Sergey Matveychuk
2004-03-22 22:10 ` Sergey Matveychuk
2004-09-01 22:00 ` Marco Gerards
2004-09-02 10:50 ` Yoshinori K. Okuji
2004-09-05 9:26 ` Marco Gerards
2004-09-07 10:46 ` Yoshinori K. Okuji
2004-12-29 17:27 ` Marco Gerards
2005-01-11 13:32 ` Yoshinori K. Okuji
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=200403211711.52377.okuji@enbug.org \
--to=okuji@enbug.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.