public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Yao" <ryao@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/genkernel:zfs commit in: defaults/
Date: Wed, 20 Jan 2016 18:58:33 +0000 (UTC)	[thread overview]
Message-ID: <1453316073.255d1f34ef55ee9c83983fec1057c1dde156ea26.ryao@gentoo> (raw)

commit:     255d1f34ef55ee9c83983fec1057c1dde156ea26
Author:     Richard Yao <ryao <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 20 18:54:33 2016 +0000
Commit:     Richard Yao <ryao <AT> gentoo <DOT> org>
CommitDate: Wed Jan 20 18:54:33 2016 +0000
URL:        https://gitweb.gentoo.org/proj/genkernel.git/commit/?id=255d1f34

busybox mount takes -o move instead of --move

Our attempt to move /dev into /newroot/dev fails because busybox's mount
does not understand --move. Instead it requires `-o move`. ZFS /dev/zd*
devices to be lost during the boot process.

At present, there is no nothing in userland that knows how to recreate
them from `/sys/devices/virtual/block`.

Signed-off-by: Richard Yao <ryao <AT> gentoo.org>

 defaults/linuxrc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/defaults/linuxrc b/defaults/linuxrc
index dc129ce..66efda8 100644
--- a/defaults/linuxrc
+++ b/defaults/linuxrc
@@ -998,7 +998,7 @@ for fs in /dev /sys /proc
 do
 	if grep -qs "$fs" /proc/mounts
 	then
-		if ! mount --move $fs "${CHROOT}"$fs
+		if ! mount -o move $fs "${CHROOT}"$fs
 		then
 			umount $fs || \
 			bad_msg "Failed to move and unmount the ramdisk $fs!"


             reply	other threads:[~2016-01-20 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 18:58 Richard Yao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-21 13:13 [gentoo-commits] proj/genkernel:zfs commit in: defaults/ Richard Yao
2015-09-21 13:13 Richard Yao
2015-09-21 13:13 Richard Yao
2015-09-20 19:30 Richard Yao

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=1453316073.255d1f34ef55ee9c83983fec1057c1dde156ea26.ryao@gentoo \
    --to=ryao@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox