From: Fred Ollinger <Fred.Ollinger@seescan.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Jeffrey D Boyer <Jeffrey.D.Boyer@jci.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Christopher Larson <clarson@kergoth.com>
Subject: Re: Mounting USB drives on a "read-only-rootfs" based system
Date: Tue, 14 Jun 2016 16:01:52 +0000 [thread overview]
Message-ID: <1465920093479.94024@seescan.com> (raw)
In-Reply-To: <CAJTo0LanVXcMNzpcaeA45L2+1Y1PGDYJt6hxgcJ-Q7k_LV0rbA@mail.gmail.com>
There's also bind mounts as an option.
The bind mounts.
Since Linux 2.4.0 it is possible to remount part of the file hierarchy somewhere else. The call is:
mount --bind olddir newdir
or by using this fstab entry:
/olddir /newdir none bind
After this call the same contents are accessible in two places. One can also remount a single file (on a
single file).
________________________________
From: yocto-bounces@yoctoproject.org <yocto-bounces@yoctoproject.org> on behalf of Burton, Ross <ross.burton@intel.com>
Sent: Tuesday, June 14, 2016 7:28 AM
To: Jeffrey D Boyer
Cc: yocto@yoctoproject.org; Christopher Larson
Subject: Re: [yocto] Mounting USB drives on a "read-only-rootfs" based system
On 14 June 2016 at 14:48, Jeffrey D Boyer <Jeffrey.D.Boyer@jci.com<mailto:Jeffrey.D.Boyer@jci.com>> wrote:
FYI, I'm running 3.14 kernel. Is this a job for aufs? If so, how would I go about configuring it?
If you want to support arbitrary mounts then it's probably simplest to either change /media to be a symlink to /run/media, or put a tmpfs on /media.
Ross
next prev parent reply other threads:[~2016-06-14 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 21:22 Mounting USB drives on a "read-only-rootfs" based system Jeffrey D Boyer
2016-06-13 22:01 ` Christopher Larson
2016-06-14 13:18 ` Mike Looijmans
2016-06-14 13:48 ` Jeffrey D Boyer
2016-06-14 14:28 ` Burton, Ross
2016-06-14 16:01 ` Fred Ollinger [this message]
2016-06-15 8:07 ` Mike Looijmans
2016-06-15 13:14 ` Jeffrey D Boyer
2016-06-14 6:36 ` Richard Leitner
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=1465920093479.94024@seescan.com \
--to=fred.ollinger@seescan.com \
--cc=Jeffrey.D.Boyer@jci.com \
--cc=clarson@kergoth.com \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.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.