From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Reimplement 10_freebsd.in using 10_linux.in
Date: Mon, 17 Aug 2009 16:01:11 +0200 [thread overview]
Message-ID: <20090817140111.GO32551@thorin> (raw)
In-Reply-To: <d7ead6de0908161229k5e3129bfpc8f741f77294820d@mail.gmail.com>
On Sun, Aug 16, 2009 at 09:29:08PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> As discussed on IRC this patch has problems on FreeBSD.
> Among them
> 1) stat and readlink are different. Does anyone have an idea how to
> make scripts always use right syntax?
AFAIK a custom autoconf snippet is the only way. Do you know how to reliably
identify GNU-incompatible readlink? I'm not sure what "readlink -f /" will do
on FreeBSD.
> - if path=`readlink -f $path` ; then : ; else
> + if path=`realpath $path` ; then : ; else
Note that this introduces an external dependency on GNU systems (readlink is
part of coreutils), which better be avoided (specially since the version of
realpath commonly used there has a problematic license).
> 2) "FreeBSD, kFreeBSD ..." isn't what FreeBSD user expects.
Ok.
> 3) Version isn't detected correctly.
Since this part is not in your patch, can you explain the problem?
> 5) device.hints are forgotten
Ok.
> 4) Doesn't use UUID
> 6) Doesn't support ZFS
These two are in the previous version too, so I'd fix/merge them separately
(increasing commit granularity is a good thing).
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-08-17 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 12:12 [PATCH] Reimplement 10_freebsd.in using 10_linux.in Robert Millan
2009-08-16 19:29 ` Vladimir 'phcoder' Serbinenko
2009-08-17 14:01 ` Robert Millan [this message]
2009-08-17 14:27 ` Vladimir 'phcoder' Serbinenko
2009-08-19 15:31 ` Robert Millan
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=20090817140111.GO32551@thorin \
--to=rmh@aybabtu.com \
--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.