From: Mike Looijmans <mike.looijmans@topic.nl>
To: Christopher Larson <clarson@kergoth.com>,
Jeffrey D Boyer <Jeffrey.D.Boyer@jci.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Mounting USB drives on a "read-only-rootfs" based system
Date: Tue, 14 Jun 2016 15:18:22 +0200 [thread overview]
Message-ID: <5760041E.1010809@topic.nl> (raw)
In-Reply-To: <CABcZANkeE_RumUN=6D8n8zFQW8hEb-nRQgXBbc5ZMPkZniPLjA@mail.gmail.com>
Yup, even mdev based images do that with current OE.
I'd expect "/media" to symlink to "run/media" on most devices (regardless
whether the rootfs is read-only or not). Check if that's the case on your system.
On 14-06-16 00:01, Christopher Larson wrote:
> Afaik usb storage is already automounted by udev on /run/media/, so there's no
> need to use /media for that purpose.
>
> On Mon, Jun 13, 2016 at 2:22 PM, Jeffrey D Boyer <Jeffrey.D.Boyer@jci.com
> <mailto:Jeffrey.D.Boyer@jci.com>> wrote:
>
> Hello,____
>
> __ __
>
> New to the list here, so I’m sorry if this question has been asked before,
> but I couldn’t find a direct answer to it. ____
>
> __ __
>
> I have a yocto image that was built using the following bb script line:
> IMAGE_FEATURES += " read-only-rootfs". ____
>
> __ __
>
> As this image eventually resides on a static flash device, it must be
> read-only. However, the system hardware supports removable media (SD card
> and USB drives), and I’d like to be able to mount and write to those
> removable drives / partitions for data logging purposes. What needs to be
> done in order to make the /media directory auto-mountable when a
> “read-only” image is specified by the build script?____
>
> __ __
>
> Thanks.____
>
> __ __
>
>
> --
>
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
_______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
>
>
next prev parent reply other threads:[~2016-06-14 13:18 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 [this message]
2016-06-14 13:48 ` Jeffrey D Boyer
2016-06-14 14:28 ` Burton, Ross
2016-06-14 16:01 ` Fred Ollinger
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=5760041E.1010809@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=Jeffrey.D.Boyer@jci.com \
--cc=clarson@kergoth.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.