From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] fix FreeBSD.vfs.root.mountfrom
Date: Fri, 7 Aug 2009 13:55:38 +0200 [thread overview]
Message-ID: <20090807115538.GA7428@thorin> (raw)
In-Reply-To: <20090804191351.GA14651@thorin>
Committed.
On Tue, Aug 04, 2009 at 09:13:51PM +0200, Robert Millan wrote:
> On Tue, Aug 04, 2009 at 08:42:25PM +0200, Robert Millan wrote:
> >
> > FreeBSD.vfs.root.mountfrom expects an absolute path, not just device name.
>
> Actually, both work, but the former is what their loader uses, and it's
> simpler for us to handle, so let's juse use that.
>
> Also, the default setting on FreeBSD is to mount / as writable, for which
> we need vfs.root.mountfrom.options=rw.
>
> See new patch.
>
> --
> 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."
> 2009-08-04 Robert Millan <rmh.grub@aybabtu.com>
>
> * util/grub.d/10_freebsd.in: Use an absolute device path for
> `vfs.root.mountfrom'. Set `vfs.root.mountfrom.options=rw'.
>
> Index: util/grub.d/10_freebsd.in
> ===================================================================
> --- util/grub.d/10_freebsd.in (revision 2466)
> +++ util/grub.d/10_freebsd.in (working copy)
> @@ -50,8 +50,6 @@ if [ "x$kfreebsd" != "x" ] ; then
> devices_rel_dirname=`make_system_path_relative_to_its_root $devices_dirname`
> fi
>
> - root_device=`basename ${GRUB_DEVICE}`
> -
> # For "ufs" it's the same. Do we care about the others?
> kfreebsd_fs=${GRUB_FS}
>
> @@ -69,7 +67,8 @@ EOF
> EOF
> fi
> cat << EOF
> - set FreeBSD.vfs.root.mountfrom=${kfreebsd_fs}:${root_device}
> + set FreeBSD.vfs.root.mountfrom=${kfreebsd_fs}:${GRUB_DEVICE}
> + set FreeBSD.vfs.root.mountfrom.options=rw
> }
> EOF
> fi
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
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."
prev parent reply other threads:[~2009-08-07 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 18:42 [PATCH] fix FreeBSD.vfs.root.mountfrom Robert Millan
2009-08-04 19:13 ` Robert Millan
2009-08-07 11:55 ` Robert Millan [this message]
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=20090807115538.GA7428@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.