From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6540894205872439296 X-Received: by 10.46.157.215 with SMTP id x23mr980747ljj.35.1522921233977; Thu, 05 Apr 2018 02:40:33 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.46.33.211 with SMTP id h80ls577118lji.13.gmail; Thu, 05 Apr 2018 02:40:33 -0700 (PDT) X-Google-Smtp-Source: AIpwx494gv+aojRPVOPFbU2osRdRtgkmMfDTEIPxLbQBnaI5/98sLZcinMHJ7gHG/+n0MzX5rP6m X-Received: by 10.46.151.3 with SMTP id r3mr1043069lji.39.1522921233355; Thu, 05 Apr 2018 02:40:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522921233; cv=none; d=google.com; s=arc-20160816; b=okekakFe1pBoZwYfMXuPS34Jo1IE4XVGO7WAx1BuHjcj46qlD8PVOogUPjLByrTyqn 4G+gIXgpaqD8p2T09B+IJCSQbERoUntAwlKs9eNjzTmAUXFQpk4aQFTHCcqmmtw9ZHYW JNwv+8GPfQne1UgOLFekz9nshk5nxyYWH85+x1PqoBIvZxiwsSlQ1TELVnyBQEK/WlYV 9ObRAzrC7nLbe6S5ERJxvMGeEic4FQR6BSWliVFdMFA9o0X/z/5GT59LOdJ+IkG1uuWI 5fyvsiq7iCIhU02O+eAibjjOArAtk8fGKFfeTHt3oK53zZyrW+/66uQJ/29zQPpSgBWL 2PtA== 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:openpgp:from:references:to:subject :arc-authentication-results; bh=LP1KB8fmvjUWttOjcQAtekcnNWppN7UKhhtMBQPRho8=; b=yvL4id5IGuXCQiQ5uqULYY8/0FLdCOBdFino7ZvuGcrFsvp0OVlJVSnqPvUeEt53Ls Xkru0W4V+FOj9L3E+yNMn5vzmPNNQgrJeemo0zXTQtEmFUxQ76Q0Jx7+VMcS6zAkM9Z8 6VqLptS6vG8USkPgDJ2MYVoTfXz9UItHGkI8/uxuO4D7akNlLPSVmJgrGBavPDnV69qv 2+yyonAabB+ZCXutlnoDM6LBihwfW/IUs4wkXrnhrI5llMM1Y1pfAM21oYmJHtMwKSLW MkFRcCvJveHxX9u54HTXYQT7nXM+Nsc1tBq2WoGeNOIwTbxys5z4CFVN+5nVlMbJeryG sGCQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id p138-v6si203062lfd.0.2018.04.05.02.40.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Apr 2018 02:40:33 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id w359eWV9007389 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 5 Apr 2018 11:40:32 +0200 Received: from [167.87.31.205] ([167.87.31.205]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w359eVPx012378; Thu, 5 Apr 2018 11:40:32 +0200 Subject: Re: Building images without kernel To: Claudius Heine , isar-users References: <94d6aabf-f2a9-95c1-3827-6da3975f8936@siemens.com> From: Jan Kiszka Openpgp: preference=signencrypt Message-ID: <5a2e722a-9745-a759-a84b-8b11f445b71a@siemens.com> Date: Thu, 5 Apr 2018 11:40:31 +0200 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: <94d6aabf-f2a9-95c1-3827-6da3975f8936@siemens.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: 5yWHbrhaOfhr 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. Jan