public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [RFC PATCH 0/6] ISAR SDK root filesystem
Date: Thu, 14 Jun 2018 11:46:23 +0200	[thread overview]
Message-ID: <69362abe-e823-7027-71fe-e35126e32bce@ilbers.de> (raw)
In-Reply-To: <20180614104826.0d954ed7@md1pvb1c.ad001.siemens.net>

On 06/14/2018 10:48 AM, Henning Schild wrote:
<snip>
>> Limitation
>>
>> Only Debian Stretch for SDK root filesystem is supported as only
>> Stretch provides crossbuild environment by default. (Debian Jessie
>> requires some additional preconfiguration steps see
>> https://wiki.debian.org/CrossToolchains#Installation for details).
> 
> Are we ready for buster? Not many people care about the past, but let
> us make sure this will work in the future.

Your patch regarding buster support is still pending as additional
feedback from you is needed (see email below I've sent you a week ago).

8<---
> -------- Forwarded Message --------
> Subject: Re: [PATCHv2 2/2] conf: Add support for new debian distro "buster"
> Date: Thu, 7 Jun 2018 11:53:13 +0200
> From: Maxim Yu. Osipov <mosipov@ilbers.de>
> Organization: ilbers GmbH
> To: Henning Schild <henning.schild@siemens.com>, isar-users@googlegroups.com
> CC: Alexander Smirnov <asmirnov@ilbers.de>
> 
> Hello Henning,
> 
> Did you experience the problem Alexander reported in email below?
> 
> Kind regards,
> Maxim.
> 
> On 05/27/2018 09:54 PM, Alexander Smirnov wrote:
>> Hi Henning,
>> 
>> thank you for the first patch, now there is no problem with trusted 
>> repo. But there is another issue with wic:
>> 
>> 8<--
>> ERROR: mc:qemui386-buster:isar-image-base-1.0-r0 do_wic_image: Function 
>> failed: do_wic_image (log file is located at 
>> /home/builder/isar/build/tmp/work/debian-buster-i386/isar-image-base/temp/log.do_wic_image.6282) 
>> 

8<---


>> Example
>>
>>   - Trigger creation of SDK root filesystem
>>
>>
>> bitbake -c do_isar_sdk multiconfig:qemuarm-stretch:isar-image-base
>>
>>
>>   - Mount the following directories in chroot by passing resulting
>> rootfs as an argument to the script `mount_chroot.sh`:
>>
>>
>> $ cat mount_chroot.sh
>> #!/bin/bash
>> sudo mount /tmp     $1/tmp                 -o bind
>> sudo mount proc     $1/proc    -t proc     -o nosuid,noexec,nodev
>> sudo mount sysfs    $1/sys     -t sysfs    -o nosuid,noexec,nodev
>> sudo mount devtmpfs $1/dev     -t devtmpfs -o mode=0755,nosuid
>> sudo mount devpts   $1/dev/pts -t devpts   -o gid=5,mode=620
>> sudo mount tmpfs    $1/dev/shm -t tmpfs    -o rw,seclabel,nosuid,nodev
>>
>> $ ./mount_chroot.sh ./build/tmp/work/debian-stretch-armhf/sdkchroot/rootfs
> 
> Imagine this being copied over to a totally different Linux-distro or
> into a docker container.
> 
> The "sudos" should not be in the script. So people can choose to not
> use sudo at all or call the script with sudo.

OK.

> Maybe adding a Dockerfile would be a good idea to understand more such
> implications.
> 
> Henning

Kind regards,
Maxim.
-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

  parent reply	other threads:[~2018-06-14  9:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 13:58 Maxim Yu. Osipov
2018-06-13 13:58 ` [RFC PATCH 1/6] isar-bootstrap-helper: Add option --copyrepo to setup_root_file_system() Maxim Yu. Osipov
2018-06-14  8:51   ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 2/6] isar-debootstrap: split into host and target recipes Maxim Yu. Osipov
2018-06-14  8:59   ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 3/6] sdkchroot: Added recipe-devel to create SDK root filesystem Maxim Yu. Osipov
2018-06-14  9:19   ` Henning Schild
2018-06-14 10:46     ` Maxim Yu. Osipov
2018-06-14 11:07       ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 4/6] meta/class/image: Add do_isar task to trigger SDK rootfs creation Maxim Yu. Osipov
2018-06-14  9:23   ` Henning Schild
2018-06-14 11:49     ` Maxim Yu. Osipov
2018-06-18  9:56   ` Baurzhan Ismagulov
2018-06-13 13:58 ` [RFC PATCH 5/6] scripts: Add helper scripts to mount/umount chroot directory Maxim Yu. Osipov
2018-06-14  9:28   ` Henning Schild
2018-06-13 13:58 ` [RFC PATCH 6/6] doc: Add description of ISAR SDK root filesystem creation Maxim Yu. Osipov
2018-06-14  8:48 ` [RFC PATCH 0/6] ISAR SDK root filesystem Henning Schild
2018-06-14  8:51   ` Jan Kiszka
2018-06-14  9:34     ` Henning Schild
2018-06-14  9:46   ` Maxim Yu. Osipov [this message]
2018-06-18  7:08     ` Henning Schild
2018-06-19  7:33       ` Maxim Yu. Osipov

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=69362abe-e823-7027-71fe-e35126e32bce@ilbers.de \
    --to=mosipov@ilbers.de \
    --cc=henning.schild@siemens.com \
    --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