From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6489319872694059008 X-Received: by 10.223.154.111 with SMTP id z102mr491688wrb.14.1510914903204; Fri, 17 Nov 2017 02:35:03 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.232.150 with SMTP id f22ls752793wmi.8.gmail; Fri, 17 Nov 2017 02:35:02 -0800 (PST) X-Google-Smtp-Source: AGs4zMam0RPS84W3g0uTH4RwOVS0mxz+VUrIdsg0VvMjsMDsl8fIwSXSZr+MsLqrPAcgaii/jNao X-Received: by 10.223.146.66 with SMTP id 60mr473360wrj.15.1510914902887; Fri, 17 Nov 2017 02:35:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510914902; cv=none; d=google.com; s=arc-20160816; b=X9HZyRGA5+0KIs7DpQS3BIPpQa0EQRpnBbT1hW84n0/6vdeCn8Dk1uBMD/o3sxcJ8S G3JHp/V9JWHeR59co+/bAeCuIp4SzWYDnV5WgrrpDPeWOEkz8/m3/jCo4fALOgNhLzBr 8STQeULWDoA2/3JNnzGPJI985+zWUAsE+O4ZAMNi6TjHnKVVJq3UylU8MA6tsAABng8n /jUNGqE7UuH2N33AuOI567H1DY57maMe4bgXyrDQyCJONXMsXQjRwbVHMcx9Smgfbk6I sTfMa7TDF38cwyoRzhBp+/8+ksaOdkRxeHd2tV2/Ngq32QWVzJzBpQ+9f7uIYLQ6SF8j tXZg== 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=Lh+NXh7GE1jEn0kYIBsTIRhLDlzePH8TtCHVKCnFcbA=; b=hDBQHl33G1JbS2v35KWLlINueNwLUID3p/2fLj+rfNACprA8+eJL8PSGVUDhMsqGwT MorWYnDHaeVVBBymUQ0eEXYenQNyPYhbI4wJ/08TPk7HgyGUS+stkMDj43ufpEJ2uFdq TxJA9sQFkMXCqSv4jyqAcAaP+uz1p4KPpIRS2f0JJNxpbo1XXPhSyfITefABaxxxYHZq XsjGHJUdxL0+D8rrCrSx4lfGBNSRNC+zzrhZljDA2rmiuBowpcKr/6wRYbhRokD8SnfG uzmnAK4n18d6GsTU283auVnHOdboa3eOHyXutfO3N18azfDVrtHlkXQ4V3GVn5FGF0kA G12A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id j13si307705wmh.1.2017.11.17.02.35.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 02:35:02 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of asmirnov@ilbers.de designates 85.214.62.211 as permitted sender) smtp.mailfrom=asmirnov@ilbers.de Received: from [10.0.2.15] ([188.227.110.165]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id vAHAYxT8021154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 17 Nov 2017 11:35:01 +0100 Subject: Re: [PATCH] isar-image-base: fix owner and group of /proc To: isar-users@googlegroups.com References: <20171117101743.ajad3sybehwdvqs6@MD1KR9XC.ww002.siemens.net> From: Alexander Smirnov Message-ID: Date: Fri, 17 Nov 2017 13:34:54 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171117101743.ajad3sybehwdvqs6@MD1KR9XC.ww002.siemens.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: utd525IR11G7 Hi Christian, On 11/17/2017 01:17 PM, Christian Storm wrote: > Hi Alex, > >> On 11/17/2017 12:54 PM, Christian Storm wrote: >>> Signed-off-by: Christian Storm >>> --- >>> meta-isar/recipes-core/images/isar-image-base.bb | 2 +- >>> meta/recipes-devtools/buildchroot/buildchroot.bb | 2 +- >>> 2 files changed, 2 insertions(+), 2 deletions(-) >>> >>> diff --git a/meta-isar/recipes-core/images/isar-image-base.bb b/meta-isar/recipes-core/images/isar-image-base.bb >>> index c2150b1..a6906c6 100644 >>> --- a/meta-isar/recipes-core/images/isar-image-base.bb >>> +++ b/meta-isar/recipes-core/images/isar-image-base.bb >>> @@ -52,7 +52,7 @@ do_rootfs() { >>> -e 's|##ISAR_DISTRO_SUITE##|${DEBDISTRONAME}|g' \ >>> "${WORKDIR}/multistrap.conf.in" > "${WORKDIR}/multistrap.conf" >>> >>> - [ ! -d ${IMAGE_ROOTFS}/proc ] && install -d -m 555 ${IMAGE_ROOTFS}/proc >>> + [ ! -d ${IMAGE_ROOTFS}/proc ] && sudo install -d -o 0 -g 0 -m 555 ${IMAGE_ROOTFS}/proc >> >> What is the requirement for doing so? And what is the benefit? > > In the resulting image, /proc was created with my build user's ownership > != root as it was non-existent. To create the directory belonging to > root, sudo is required here... > Thanks, got it! But I don't think it's also required for buildchroot. Alex