From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6489319872694059008 X-Received: by 10.28.182.9 with SMTP id g9mr598376wmf.5.1510936563022; Fri, 17 Nov 2017 08:36:03 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.197.15 with SMTP id v15ls967127wmf.2.canary-gmail; Fri, 17 Nov 2017 08:36:02 -0800 (PST) X-Google-Smtp-Source: AGs4zMZkm796cUE3qIUY1lfbHit83EyolH6jVqPINMSKxPGG2UDonY+MdlqibIlqWBnwxU3L40vu X-Received: by 10.28.167.83 with SMTP id q80mr685130wme.1.1510936562728; Fri, 17 Nov 2017 08:36:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510936562; cv=none; d=google.com; s=arc-20160816; b=SFHK4Y7dX8ZeqB6VCuWl99001dKFchLRU0BKM4aIEaea0hrSjl3za7cad8sSjUxJql AFLhuolX9/CWX3KX0m+1H4V6Sg8CfUUALOK5vzHe4OA9KkNDZ6Dd9ToSdVPQAH/Dvq/P a5CruU3TssHe7mIjWNxPawE1o3x00RR2Mv8hb8jk5xvZpgbSjfInMZGvA94iHO4cCEnA PA9n+oqdU1f0GyGVeDBpzgMzh7ysyBFZ4Vj4uoV6smEOM7NrU1ghJFGywKRDcJ+lKFJP JwmyC2+qxqbMWRqIvLxFCwMCsGZU77bb9mP5zBIpgCNWyVRX44jNVW6TXOjBU001kuRp QOdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:mail-followup-to:message-id :subject:to:from:date:arc-authentication-results; bh=8gwQFCoWBf7/cvtIQiAyp3sWHp65VNgsKC6gdLnq5F4=; b=rq6Lxj61WZYDlCYwq4KTWGI6qiIPoXZpT2pjfW98RfqQLMMfgnrPHmERqXV/LhXgCW CixI1VpLLp2qFkf+qWfPJsG6ZXJLb4SJLrX6ajc/+1iQOlWpxJwD6XAlHrQ/MzRTcRZw oGih9MnKdEJc3fit0uJCP6KzGKTEWU/+Sj0JMDpBCOh0KxxSxtWuDvxShPAajmKjN5aX EGSDnufGsmmrPPsND6UIwz8CCFe1xRZzq4CPt+VrL0NBqh6pW6VOyAzpHAMowqWan6J4 CenRetpWYvdxiiTbsNIxQK2zEomjw/rJSJWi/0vc0Nu4ubDPWjqUOYNaVfbA7amDYq6b AnGw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of christian.storm@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=christian.storm@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id r70si337684wmg.2.2017.11.17.08.36.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 08:36:02 -0800 (PST) Received-SPF: pass (google.com: domain of christian.storm@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 christian.storm@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=christian.storm@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id vAHGa2ea025852 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 17 Nov 2017 17:36:02 +0100 Received: from localhost ([139.25.69.251]) by mail1.siemens.de (8.15.2/8.15.2) with ESMTPS id vAHGa22s003486 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 17 Nov 2017 17:36:02 +0100 Date: Fri, 17 Nov 2017 17:34:48 +0100 From: Christian Storm To: isar-users@googlegroups.com Subject: Re: [PATCH] isar-image-base: fix owner and group of /proc Message-ID: <20171117163448.7rzepplfu6npug72@MD1KR9XC.ww002.siemens.net> Mail-Followup-To: isar-users@googlegroups.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/20170113 (1.7.2) X-TUID: fIoT0ec0Mi2E > >>> 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. Nope, not strictly required but for cosmetics and symmetry reasons I put it in there as well. Doesn't do harm either.. Kind regards, Christian -- Dr. Christian Storm Siemens AG, Corporate Technology, CT RDA ITP SES-DE Otto-Hahn-Ring 6, 81739 M�nchen, Germany