From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-02-04
Date: Fri, 05 Feb 2021 22:41:48 +0100 [thread overview]
Message-ID: <87zh0i5h0j.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210205213453.GZ2384@scaer> (Yann E. MORIN's message of "Fri, 5 Feb 2021 22:34:53 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
>> Ideally the package should be fixed to create those files in
>> $DESTDIR/dev/shm rather than mess around with the host /dev/shm.
>>
>> But as /dev/shm is not persistent, how does this work at runtime? What
>> do those files do exactly?
> They are shared memory.
> From shm_overview(7):
> On Linux, shared memory objects are created in a (tmpfs(5)) virtual
> filesystem, normally mounted under /dev/shm. [...]
That I get.
> There is in fact nothing wrong in creating such shm objects during the
> build.
From the logs it looks like they are created during the installation,
rather than during the build.
> What is wrong, is leaving them lingering about...
Indeed. I don't particular understand why the installation step needs to
fiddle with shared memory objects in the first place, but Ok.
So these objects are only needed temporarily during installation and not
later at runtime?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-02-05 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <601cff45.1c69fb81.945af.db28SMTPIN_ADDED_MISSING@mx.google.com>
2021-02-05 14:42 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2021-02-04 Heiko Thiery
2021-02-05 17:58 ` Peter Seiderer
2021-02-05 18:35 ` Peter Korsgaard
2021-02-05 21:34 ` Yann E. MORIN
2021-02-05 21:41 ` Peter Korsgaard [this message]
2021-02-06 9:36 ` Heiko Thiery
2021-02-05 22:43 ` Peter Seiderer
2021-02-06 9:32 ` Heiko Thiery
2021-02-05 21:32 ` Yann E. MORIN
2021-02-05 23:37 ` Yann E. MORIN
2021-02-06 9:37 ` Heiko Thiery
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=87zh0i5h0j.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.