From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6540894205872439296 X-Received: by 10.46.144.13 with SMTP id h13mr1053036ljg.22.1522922053539; Thu, 05 Apr 2018 02:54:13 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.151.129 with SMTP id y1ls583370lji.3.gmail; Thu, 05 Apr 2018 02:54:13 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/5lYxPtknVaTosN4ES8KuC6gGYDPwYx566HiFNNdMWFwi4YSqnW18oMkSCmCLM2RJOQic6 X-Received: by 10.46.129.90 with SMTP id t26mr981318ljg.27.1522922053035; Thu, 05 Apr 2018 02:54:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522922052; cv=none; d=google.com; s=arc-20160816; b=BF53HxNZ174T8lFl4BNwdWt+iJ37JrkXUIiBzgyKyohYMRWN1kvoNW7fc53NYNzQgR 9w27n/6OJKWoTydpyhU5/RTn6Md1yBMI6UE8gzS5V4/38V8AxvNEuGgUu9okqlVvsB1W J/EvDQCEitjNUKLqZ9oom9Og9Mkx/eaoO9fquLZ2sn2sNbKAZV6UDrgDgfzNdfktYZsv E3GXc5PK27UdFPgxe+xaByRDpmOsNuJKlB63mPG9q7Mff6uuagDRnlzIyOp2WhJ072Bi CUbOkwb4TcKjbLMnWWIkS75A91NTQHqodP0nbrjhEb1C//nG9FAeu8SCLhzJpz07+GrU /qug== 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=aoX87cgmtDEt9l9guUm/cnJZKvEundG9Sj0fT+9KCI0=; b=qixsZdCibJq5YDiRwiwv6iciLAbAN1LS3bjK4Cthzo0c5TUSxHngKsLMLycbyInPfa HqHQeJp6u6A5MB0cu4Eny4g/l3B5cbYDeTrF+NLlGiusbWEgJoOiNJzt9/8hj5nNq1Ic bmqmJJ0yKz4pz7iTZFQwZazH0z+QHVwM8KRzcmZZgb+TxJwdYSTY1t+XUY2mYHYgxSQP EU6KuEcOZzL0hUTLSHfktXxFEa3k/UEzB8PX+2a1XuOuDTEwgnIZr6j0F12lsBEaLyRp 7lsUsW/Zs4f1EgE0/pjXXcP+2lBsT02BF/2VQhG7Iv3V1L4KE2eVRBZoq8uQu+Z3vL7V bwfA== 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 d22si148763ljg.4.2018.04.05.02.54.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Apr 2018 02:54:12 -0700 (PDT) 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 w359s8Ju013299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 5 Apr 2018 11:54:11 +0200 Subject: Re: Building images without kernel To: Jan Kiszka , isar-users References: <94d6aabf-f2a9-95c1-3827-6da3975f8936@siemens.com> <5a2e722a-9745-a759-a84b-8b11f445b71a@siemens.com> From: Alexander Smirnov Message-ID: Date: Thu, 5 Apr 2018 12:54:02 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <5a2e722a-9745-a759-a84b-8b11f445b71a@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: MJcoeAr2+Hkr On 04/05/2018 12:40 PM, Jan Kiszka wrote: > On 2018-04-05 11:30, Claudius Heine wrote: >> Hi, >> >> my use-case is creating nfs root file systems with isar, so I don't need >> the kernel created by isar. That worked with older isar version. >> Now we have a strong dependency to some kernel. >> >> Using my multiconfig it currently complains about: >>     Nothing PROVIDES 'linux-image-${KERNEL_NAME}' >> >> Sure I can just set `KERNEL_IMAGE` to something, but wouldn't that then >> deploy the kernel to my rfs? > > That hard dependency is encoded into isar-image-base.bb (I think it was > before as well). You could probably do IMAGE_INSTALL_remove, or you > provide a linux-image-none recipe (KERNEL_NAME=none to install nothing > in your image. Maybe we should include such a dummy recipe upstream so > that this case can be handled without boilerplate code. > Another approach could be distro features, like it's done in Yocto via DISTRO_FEATURES. The features could be: kernel, bootloader, debug etc... In general I think it's eventually very useful cascading. Alex