From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517147827419742208 X-Received: by 10.28.54.200 with SMTP id y69mr3329202wmh.14.1517400930895; Wed, 31 Jan 2018 04:15:30 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.167.75 with SMTP id q72ls1077620wme.0.gmail; Wed, 31 Jan 2018 04:15:30 -0800 (PST) X-Google-Smtp-Source: AH8x226BTrMwzEAuMtvPfHFP07ONkpZUbtMgx+3xf7MJ1Cob033LgaXrXDICJx0vK1Jouzhudx4w X-Received: by 10.28.124.24 with SMTP id x24mr3566214wmc.1.1517400929607; Wed, 31 Jan 2018 04:15:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517400929; cv=none; d=google.com; s=arc-20160816; b=cVVju8hTU5hNVhrzhdJPkA2HFVn4qH4OMRUDJE6uxSMLXTlw0SpEnZCdDik+p7QTKu I3B5eG7Og8qJyEpx5U0U0H8fzDab48heXJ6Jb6TqOQ22scFd43r5oa8ry9uspiKiz8XU b5/6dlq0rCpMRwgaZDJwyxbaCHgaoGHMRA/vQM0hA4ZFhiwh8ddjHJWeUKaIVs3bFs34 NMHQzA0YyCCT+W5/kNFBHb4WOPlIXpu+4RgAVn9LfRlSRvDsx09f3sVlsYCu8ZkUgg/l ZxeBozAdx8uvJcw0EdPNToTeFBe4A4Dt/9QesxXGr2QpsMtdXbEitTY1RG/AUT87K7bQ ieAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=3Djhu5spMK/6VwklqAZ0PSLFPqGT8iTfxCp00d5AiAA=; b=hO9Bnf7E5H3ufPQTxgC/whtgbhsWV4altsPup75IlQoJLv3vYCUeDKOF/j8iopeXYo lauLsxhAEiKAf+uOZbE7OCcBD0N+BZX1dH1h+2dL1BOPe0+X3nsuMP0i9l8y9a5FpJ99 lGy6FNK/Za62aukqCSTRMn4Potj5govyOEO73ertb7h29ch8xoW73bb0oSfo7L+L8cuj zjAp63MyTjPjbZloiw/8Y735ts7cPVFaNHSdLbES2lcTtMg8Kzhf6XWIaoxbK4yJZGEA eb3kOByHJEqwIR6xlTVGBmeOQNW6bM+DB68B6rN3DyrOwldmTknO5K+HPhr6oK1fiwbO IDWg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id k21si1615790wrd.1.2018.01.31.04.15.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 04:15:29 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w0VCFTxx014000 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 31 Jan 2018 13:15:29 +0100 Received: from [167.87.8.100] ([167.87.8.100]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id w0VCFSZD021401 for ; Wed, 31 Jan 2018 13:15:29 +0100 Subject: Re: [PATCH 0/9] first wic integration To: isar-users@googlegroups.com References: <20180131111253.49011346@mmd1pvb1c.ad001.siemens.net> <20180131112421.GA6508@yssyq.radix50.net> <675eeef9-1e24-4784-b894-4ce665da26fb@siemens.com> <20180131120245.GC6508@yssyq.radix50.net> From: Jan Kiszka Message-ID: <1a55fba5-e089-5bbe-4f14-e1931dea38dd@siemens.com> Date: Wed, 31 Jan 2018 13:15:28 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20180131120245.GC6508@yssyq.radix50.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: K8Dzq7nlQuJU On 2018-01-31 13:02, Baurzhan Ismagulov wrote: > On Wed, Jan 31, 2018 at 12:47:08PM +0100, Jan Kiszka wrote: >>>> If the manual non-root call did work before, i will look into that. >>> >>> Yes. Yes, please do. >>> >>> In Yocto, manual non-root call works. The same is our vision for Isar. For now, >>> it has been workarounded with sudo. We have a working PoC based on PRoot in the >>> pipeline. So I don't support the idea of changing the user experience because >>> of this issue. >> >> While I agree we should try to get whole Isar unprivileged, let's not >> invest too much into this when it's complex. We are currently far away >> from that goal (as you know, proot has several open issues as well), and >> this here solves the problem of having to run wic manually at all. > > No effort whatsoever. This is already workarounded in master in the following > commit: > > bf873d3 wic: Use sudo instead of pseudo > This hacks in wic, and that has to go in order to keep maintainability. We need to solve that differently, for sure. > My suggestion is not to revert that. I agree with Henning that we should cover > that in CI. I'll provide an initial testing framework, then we should sync who > does what. The other mcopy and fsck issues are not covered, either. > > > Regarding the PRoot PoC, I don't agree we are far away. Everything works > except mounting. We've just postponed the work due to higher-prio issues. I'm happy to discuss the effort you see in resolving that last issue and will re-prioritize. > > >>> b1511ec wic: Work around mcopy error This issue is not understood yet, thus the commit not ready for upstream. Furthermore, the log does not describe how to reproduce the issue. So - how to clarify if we still need it? >>> 17f9196 wic: Introduce the `WicExecError` exception class Can you explain why fsck should return an error at all on a freshly built file system image? This seems to paper over some issue to me. >>> >>> All of them are not related to the bitbake core and fix concrete issues with >>> image generation that were not addressed in the baseline bitbake. Did you >>> address those issues in your new changes? >> >> Good points, should be clarified. Maybe an update of the upstream wic >> import is the answer if we are about to lose something. Better than >> patching locally in Isar, as so far. > > Do you mean we should initiate upstreaming that to OE? If yes, I agree with > you. The only question is point of time. My idea was to wait till Henning > completes the lifecycle with his OE contribution and learn from his experience. > If you think we should do that now, please let me know. Local hacks can save some time for a while but will shoot back with more effort eventually. I think we are already at that point, so let's move forward. We can help you with this. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux