From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6657472919531159552 X-Received: by 2002:a7b:c190:: with SMTP id y16mr108031wmi.2.1550074532824; Wed, 13 Feb 2019 08:15:32 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6000:149:: with SMTP id r9ls4088567wrx.7.gmail; Wed, 13 Feb 2019 08:15:32 -0800 (PST) X-Google-Smtp-Source: AHgI3IYvVQXZ6s0MOLgNGxCpIjLAKt1slfbpLluaMKYDpKKIrHRGQBYsvO6KHX6OHvVgevOMGK5C X-Received: by 2002:adf:f248:: with SMTP id b8mr103511wrp.9.1550074532296; Wed, 13 Feb 2019 08:15:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550074532; cv=none; d=google.com; s=arc-20160816; b=Tnd3UA39eKKuqWbAZa3vfV6djmktiKHqyzoldqbpTmdIpAK0hOhIUB1Vedrfv4RoA4 HH4ddQA7DPQ3EUxswUbq8MZ4rklnnH5YPKK8C1uwv6AUf0diivSlHgR3zwAFFWi7tvu1 s3tEsOXA/JO9h/97/I3AUpLVfSHtTQrxLvRCAPs3JcV8+Wc3fZzRuAFo5I+2Aez/PKeo hYqwgW13xjqZDiZ6WDTAfz6EA8rDsHFcaJ0TvgwZy5fMACJJq7oJBkcJosyF5uszULxk 8X6FzK9kWuHsKFqZZ/d+oVgGkvhHWs0+Aiqsm+dl5SwNBDpMfzPHZP++cEVQnzfdqkVn 6pAQ== 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:cc:to:subject; bh=FHjeeWAKyGrNmmdr5gulP0zLv7zWfwTGsM12YSFsUM8=; b=sk19JTE2UlOSSCWTJD88GSEkmZTzxA99MkXIy9Kl9DYh3uY7msSYaztgwqEKbl31lx UT/NKFV2H8lwIisyGVST5fkPy0si0/KZWTKEpCxkI7xp81X1dYYM2Gxj4xvrNWP/B/7u uzbw+R29JTnZqgmtrG8wRQgVeMPNA4l6rVfr2+5E33rJ3qtP3/3DA5cI5rIN5hrNOnmg wijIPy7xHMbbBVU4JRzgwvo7pwgXDLY06iHxz7kJaREzAOgFGv9hEksyrsYn0RyOFRwT z1H8NrkCHBkZq+PF93WVAfTen/58nmZInXyrl7I+FBzh4Ip6a3ZfP1NnXkJQLJPaqCUK g21g== 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 l22si324620wmg.4.2019.02.13.08.15.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 08:15:32 -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.sbs.de (mail2.sbs.de [192.129.41.66]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x1DGFVsI026727 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 13 Feb 2019 17:15:31 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x1DGFS9O027925; Wed, 13 Feb 2019 17:15:28 +0100 Subject: Re: multistrap support To: kazuhiro3.hayashi@toshiba.co.jp, isar-users@googlegroups.com Cc: meta-eid@googlegroups.com References: From: Jan Kiszka Message-ID: <84e53e0f-5e6c-3296-a806-463d63772204@siemens.com> Date: Wed, 13 Feb 2019 17:15:27 +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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: P33DytQcLaQ4 On 13.02.19 14:14, kazuhiro3.hayashi@toshiba.co.jp wrote: > Hi, > > I would like to know if isar still has some plans to use multistrap again > (or similar existing tools if exists) to generate target images. > > Multistrap for isar-image-base has been removed by the following commit: > https://github.com/ilbers/isar/commit/19a314559178f7afd93ce3dafe8c8647ca6c8884 > and replaced by setup_root_file_system() in isar-bootstrap-helper.bbclass, > which seems to use (pre-built?) isar-bootstrap-$ROOTFS_DISTRO-$ROOTFS_ARCH > as the base tree instead of running the debootstrap process. > > I guess that the main purposes of quitting multistrap is that > there is no big update for a few years (though the last update is 2.2.10 on Nov. 2018) > Are there any other reasons? > (Some bugs difficult to be fixed, mismatches with isar specification, etc.) Indeed, the key reason (beside some technical issues) for no longer using multistrap in Isar was that the multistrap creator himself explained to us that it's dead and we should rather sooner than later move away from it. We then decided to pick up the most commonly used bootstrapping mechanism for Debian today, simply to reduce the risk of running into problems no one else is seeing - and fixing. > > The current isar-bootstrap based approach would work fine for isar system, > but in that case, it might be difficult to share efforts for > developing and maintaining the functionality with non isar users. > I'm just interested in the future plan of isar. This takes concrete ideas what you consider worth sharing and what interfaces this may imply. Debootstrap is not married to Isar but it would take some use case to make that shareable or replaceable with something else. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux