public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: [PATCH 0/2] mounts for buildchroot
Date: Mon,  5 Feb 2018 19:43:45 +0300	[thread overview]
Message-ID: <20180205164347.28375-1-asmirnov@ilbers.de> (raw)

Hi all,

this series introduces my vision, how virtual filsystems (dev, sys, proc)
should be provided to buildchroot.

Currently we use several mounts around some pieces of code, but this
approach can't guarantee that adding new package or feature will not
also require these mounts. So I propose to have permanently mounted the
following systems in buildchroot:

 - /sys
 - /proc
 - /dev (--bind)

Mount is performed very early, the umount is dome via event BuildCompleted.
This approach frees us from handling build fails cases, because this event
occured anytime bitbake finished it's execution.

Alex

Alexander Smirnov (2):
  buildchroot: Do not call 'apt-get update'
  buildchroot: Permanently mount '/dev', '/sys' and '/proc'

 meta/classes/isar-events.bbclass                    |  3 +++
 meta/recipes-devtools/buildchroot/buildchroot.bb    | 21 +++++++--------------
 .../buildchroot/files/configscript.sh               |  5 -----
 .../buildchroot/files/download_dev-random           | 13 -------------
 4 files changed, 10 insertions(+), 32 deletions(-)
 delete mode 100644 meta/recipes-devtools/buildchroot/files/download_dev-random

-- 
2.1.4


             reply	other threads:[~2018-02-05 16:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 16:43 Alexander Smirnov [this message]
2018-02-05 16:43 ` [PATCH 1/2] buildchroot: Do not call 'apt-get update' Alexander Smirnov
2018-02-05 16:51   ` Jan Kiszka
2018-02-05 17:06     ` Alexander Smirnov
2018-02-05 17:25       ` Jan Kiszka
2018-02-06  9:12         ` Alexander Smirnov
2018-02-06  9:13           ` Alexander Smirnov
2018-02-06  9:38             ` Jan Kiszka
2018-02-05 16:43 ` [PATCH 2/2] buildchroot: Permanently mount '/dev', '/sys' and '/proc' Alexander Smirnov
2018-02-05 16:53   ` Jan Kiszka
2018-02-05 17:16     ` Alexander Smirnov
2018-02-05 17:30       ` Jan Kiszka
2018-02-05 17:32         ` Jan Kiszka
2018-02-05 17:50           ` Jan Kiszka
2018-02-05 18:03             ` Jan Kiszka
2018-02-05 18:03             ` Alexander Smirnov
2018-02-05 18:06               ` Jan Kiszka
2018-02-06  9:38                 ` Jan Kiszka
2018-02-06  9:43                   ` Alexander Smirnov

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=20180205164347.28375-1-asmirnov@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /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