From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6489319872694059008 X-Received: by 10.28.108.26 with SMTP id h26mr469767wmc.27.1510913938650; Fri, 17 Nov 2017 02:18:58 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.188.132 with SMTP id m126ls741050wmf.7.gmail; Fri, 17 Nov 2017 02:18:58 -0800 (PST) X-Google-Smtp-Source: AGs4zMbpQpoYqqxPejFzeXBePexvczOA2mn0BCWsakK+dNMw89813I/uIm/wZy0gYJkYopstjDS2 X-Received: by 10.223.139.198 with SMTP id w6mr481919wra.4.1510913938396; Fri, 17 Nov 2017 02:18:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510913938; cv=none; d=google.com; s=arc-20160816; b=NfMxO+qPRuKHrTD8+7M05LXYEdRCKyYs6rwxStIIh5lNaS0jIuUgJ5smhsawqldT1K IraEYsy+lMjV+oDv20KAIQD1TzH2WoSeBIfaub8ApWf62saymO/wmBXRFEe99pBQUXar VlNLj1sXszklHjb1+LV4r1GDZgz1n1MOkVP1VlAdQEkCyIVM/oLOa0DrMcTBxuwoU6qv Y8vB8I85N8dDVCBjXuYgwzxY4FhQ9SlujHjSV4PRblva9s+aCSrl2smz1QGbSJOLEulj cCb7fIfCjJkGY5GO2tsS9lGurPwNMKNTL3PYHpVhEp8hdiScMqrYZYlSGjrofse+Fm70 An0A== 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=fOzFG+EsFtntLVLfGTLYOOyyJoklwVnJzR3UG7bLjzc=; b=CvSx8xXCUDQdx7p9Qp2JtfYLZ2fq3nXT/2bXSxlqwWWENV+db8KTy0CooVt5Ghf6zS 2mfZx76lEowGa6h/HtQcGeDswyX5oSxlzJwlzPmei5dDOW70g8NTKcDufkNv2dvUYNw5 w8LOmv0lvikBQv41JnWbvSL9x/o2CefJq1mQdXNwYHuwwpUtU4r2O9O78q54vaTFPAL8 ed6cXP8zzCLK7zXyIQd77Q+WaCyvZD5dg6X+LYzi0z3yG+kWLx1OeYt5LETWVW6tzVtv Y6ZMCgr/oNdGH+B+GzU8rpXdrMXj4ZuQFjz3J4CZ7JbDnDi4xJchVhc0H1NeSU52XD4P 1wMA== 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 i76si290972wmd.0.2017.11.17.02.18.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 02:18:58 -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 mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id vAHAIv1L024415 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 17 Nov 2017 11:18:58 +0100 Received: from localhost ([139.25.69.251]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTPS id vAHAIvdQ030604 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 17 Nov 2017 11:18:57 +0100 Date: Fri, 17 Nov 2017 11:17:43 +0100 From: Christian Storm To: isar-users@googlegroups.com Subject: Re: [PATCH] isar-image-base: fix owner and group of /proc Message-ID: <20171117101743.ajad3sybehwdvqs6@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: <38c5b090-d220-cd90-b215-aa0487086f51@ilbers.de> User-Agent: Mutt/20170113 (1.7.2) X-TUID: bDi3b5Ujcdnu 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... Kind regards, Christian -- Dr. Christian Storm Siemens AG, Corporate Technology, CT RDA ITP SES-DE Otto-Hahn-Ring 6, 81739 M�nchen, Germany