From: "David Gartner" <gartnerd@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: Re: devtool question/issue
Date: Sat, 06 Feb 2021 16:57:58 -0800 [thread overview]
Message-ID: <31249.1612659478103525956@lists.yoctoproject.org> (raw)
In-Reply-To: <31249.1612637302602568173@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
After some experimentation it appears that devtool does not like running from a filesystem volume that does not contain my home directory.
My current setup on a virtualized host has the following volumes:
Filesystem Size Used Avail Use% Mounted on
udev 32G 0 32G 0% /dev
tmpfs 6.3G 5.7M 6.3G 1% /run
/dev/sda 25G 11G 13G 46% /
tmpfs 32G 0 32G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 32G 0 32G 0% /sys/fs/cgroup
/dev/sdc 148G 39G 102G 28% /mnt/YB
tmpfs 6.3G 0 6.3G 0% /run/user/1000
My home directory is located on /dev/sda - devtool works for yocto projects on this volume
/dev/sdc - I added this volume so that I'd have more space while using yocto, but devtool complains and doesn't run here. I deleted the contents of /dev/sdc and re-tried following the tutorial given in my initial post. I can reproduce (e.g. create and run qemuarm images) everything upto the step where devtool needs to be used.
The short term solution would be to increase the size of /dev/sdc but this requires moving up to a more expensive plan from my cloud provider.
Any insight as to why this occurs
[-- Attachment #2: Type: text/html, Size: 5666 bytes --]
next prev parent reply other threads:[~2021-02-07 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 1:06 devtool question/issue gartnerd
2021-02-06 12:15 ` [yocto] " gary
2021-02-06 18:48 ` David Gartner
2021-02-07 0:57 ` David Gartner [this message]
2021-02-08 0:01 ` David Gartner
2021-02-08 8:10 ` [yocto] " Josef Holzmayr
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=31249.1612659478103525956@lists.yoctoproject.org \
--to=gartnerd@gmail.com \
--cc=yocto@lists.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.