From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id uCL3Lb6rwV4QJQAA0tVLHw (envelope-from ) for ; Sun, 17 May 2020 21:25:18 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id CAK4Kb6rwV4pKAAAbx9fmQ (envelope-from ) for ; Sun, 17 May 2020 21:25:18 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 15F44940B0D for ; Sun, 17 May 2020 21:25:18 +0000 (UTC) Received: from localhost ([::1]:57202 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jaQma-0000Lj-Vx for larch@yhetil.org; Sun, 17 May 2020 17:25:17 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:58276) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jaQlF-0008Me-M6 for guix-devel@gnu.org; Sun, 17 May 2020 17:23:53 -0400 Received: from mail-lj1-x232.google.com ([2a00:1450:4864:20::232]:33950) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jaQlD-0006Ad-7o for guix-devel@gnu.org; Sun, 17 May 2020 17:23:53 -0400 Received: by mail-lj1-x232.google.com with SMTP id b6so7762850ljj.1 for ; Sun, 17 May 2020 14:23:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wzjjj3tTkoAlNJceg9Kx9xnnl4FMmypiLU6es+5Y/P0=; b=XbutCQjf++4nuL4+pILegHfbVXIGRFtXE0b6kVFDXrdLMdoIJJrQuyFKvT5DhAYkSc TXVip/CSxCnt/Yna7Mt2xdU5VfHc039x4ZZlWzRN3cRM4vKGKvGP1fAOPqvtd2f95G57 4+vdprPjpJOLzvZEL16OpaqxmyyG3u7A3+Num40XCm+cKW5Xq98+smgke5prz17L6vbn Kssq/7pknrWY9Pnie48aLFon+tvaCfsgZDG3IvDrCQvjR8TireTkgq3AC6e8Foi/MFSj wSi+4nHVontVXOqRic1ARDK8YvbeWMT7/L2XXz+wCB37/c4gled+YrkzafQkScMMGGvn e/rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wzjjj3tTkoAlNJceg9Kx9xnnl4FMmypiLU6es+5Y/P0=; b=N686YnDCTP8PG4V7jBTK+q7Zzj6+WBeR2J4vwf7UAEKrVg4fkvGrumUyKRPsB6lsAI uDURaAAALHHPJL9JJ33Qxg6RjylFu6RIpL/T+G4W/K909/eE+aykxnoA+uUy+19FyBnN aI8cl8R8QzqFZLNifmc4mUtCuIJjwSTz/OlYmlQ9OQD2hlr+RgE3NZXIR+pIprxjnpeu NcV7p6dj2B422z4WVK8K7GpN1ajcD6GvuuvECAC1PkPFg7cYJzdMqf3Y80dAiEZUSwF+ GSTiVW7WNtLc/zekq3hjPZkc3Fxd05huI8QyfRhXezFVW6AfeRkF+d37koZdidJeN10Y BsmQ== X-Gm-Message-State: AOAM533pfBF1x4IbXo0ahLnkqOvXjz00JrNoKYUiwiIHXjKiF9kL8QMH UNDy9s62kx0kqbKIV+OeRQMJr1tEsVX5KCU/zj4= X-Google-Smtp-Source: ABdhPJwtie6Ui7jzoqYUtFLKDU/NTQacECGuP7UwN8niixIltblMVgCTcqn5PGzmBJDi86rNtDAhNBfkrJnrFlH67as= X-Received: by 2002:a2e:3e09:: with SMTP id l9mr1805090lja.260.1589750629354; Sun, 17 May 2020 14:23:49 -0700 (PDT) MIME-Version: 1.0 References: <20200517132043.GE31833@E5400> In-Reply-To: <20200517132043.GE31833@E5400> From: Begley Brothers Inc Date: Mon, 18 May 2020 07:23:12 +1000 Message-ID: Subject: Re: Replacing Yocto with Guix kernel image builds: best practices To: Efraim Flashner Content-Type: multipart/alternative; boundary="0000000000008b51f305a5dea91a" Received-SPF: pass client-ip=2a00:1450:4864:20::232; envelope-from=begleybrothers@gmail.com; helo=mail-lj1-x232.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=XbutCQjf; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -1.71 X-TUID: khAfeJsnF+07 --0000000000008b51f305a5dea91a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, May 17, 2020 at 11:21 PM Efraim Flashner wrote: > On Sun, May 17, 2020 at 09:41:00PM +1000, Begley Brothers Inc wrote: > > Hi, > > We are now looking to build Linux kernels using Guix instead of Yocto. > We > > can't see any reason why the builds wouldn't be linux-libre. Ideally we= 'd > > like our effort to be accepted by upstream guix. > > > > However, being new to Guix we are still coming grips with the best > > practice(s) for what we would like to do. > > We've looked at Guix's linux.scm, and > > Efraim Flashner's post[1] is our primary reference - many thanks Efraim= . > > I'd like to embarrassingly mention that I never actually booted any of > my custom kernels. My machine was a bit too slow to regularly compile > for some guess-and-check. > No worries. Something is better than nothing and that was very useful outline of possible alternatives. > 1) We did wonder if channels[2] were the way to go with each kernel x.y.z > > in its own branch and config files therein. Could anyone point us to > > packages that setup and use package specific channels? > > 2) Should we be aiming to provide a single package with multiple > parameters > > or is it better to provide a package for each kernel x.y.z, or some oth= er > > partitioning. We'd likely want to script the package definition then - > > correct? > > I would probably start with one package each and then see how they could > be made to inherit from one another or grouped together. The way the > current make-linux-libre procedures work has grown quite a bit but they > should still mostly work as a starting point to add/remove bits for > customizing for your needs. > > I don't think I'd go with different branches. If you keep everything in > one branch then it's easier to deduplicate work between the different > variants. > That was our thought too. We're just wondering how best to get that branch content down to the users machine without them having to do anything. Thanks again. > Appreciate any comments suggestions or tips. > > > > [1]: > > > https://guix.gnu.org/blog/2019/creating-and-using-a-custom-linux-kernel-o= n-guix-system/ > > [2]: https://guix.gnu.org/manual/en/guix.html#Channels > > > > -- > > Kind Regards > > > > Begley Brothers Inc. > > > > > > 1. *The content of this email is confidential and intended for the > > recipient specified in message only. It is strictly forbidden to > share any > > part of this message with any third party, without a written consent > of the > > sender. If you received this message by mistake, please reply to thi= s > > message and follow with its deletion, so that we can ensure such a > mistake > > does not occur in the future.* > > 2. *This message has been sent as a part of discussion between Begle= y > > Brothers Inc. and the addressee whose name is specified above. Shoul= d > you > > receive this message by mistake, we would be most grateful if you > informed > > us that the message has been sent to you. In this case, we also ask > that > > you delete this message from your mailbox, and do not forward it or > any > > part of it to anyone else. Thank you for your cooperation and > > understanding.* > > 3. *Begley Brothers Inc. puts the security of the client at a high > > priority. Therefore, we have put efforts into ensuring that the > message is > > error and virus-free. Unfortunately, full security of the email > cannot be > > ensured as, despite our efforts, the data included in emails could b= e > > infected, intercepted, or corrupted. Therefore, the recipient should > check > > the email for threats with proper software, as the sender does not > accept > > liability for any damage inflicted by viewing the content of this > email.* > > 4. *The views and opinions included in this email belong to their > author > > and do not necessarily mirror the views and opinions of the company. > Our > > employees are obliged not to make any defamatory clauses, infringe, = or > > authorize infringement of any legal right. Therefore, the company > will not > > take any liability for such statements included in emails. In case o= f > any > > damages or other liabilities arising, employees are fully responsibl= e > for > > the content of their emails.* > > -- > Efraim Flashner =D7=90=D7=A4=D7=A8=D7=99=D7= =9D =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8 > GPG key =3D A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 > Confidentiality cannot be guaranteed on emails sent or received unencrypt= ed > --=20 Kind Regards Begley Brothers Inc. 1. *The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share a= ny part of this message with any third party, without a written consent of = the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mista= ke does not occur in the future.* 2. *This message has been sent as a part of discussion between Begley Brothers Inc. and the addressee whose name is specified above. Should yo= u receive this message by mistake, we would be most grateful if you inform= ed us that the message has been sent to you. In this case, we also ask that you delete this message from your mailbox, and do not forward it or any part of it to anyone else. Thank you for your cooperation and understanding.* 3. *Begley Brothers Inc. puts the security of the client at a high priority. Therefore, we have put efforts into ensuring that the message = is error and virus-free. Unfortunately, full security of the email cannot b= e ensured as, despite our efforts, the data included in emails could be infected, intercepted, or corrupted. Therefore, the recipient should che= ck the email for threats with proper software, as the sender does not accep= t liability for any damage inflicted by viewing the content of this email.= * 4. *The views and opinions included in this email belong to their author and do not necessarily mirror the views and opinions of the company. Our employees are obliged not to make any defamatory clauses, infringe, or authorize infringement of any legal right. Therefore, the company will n= ot take any liability for such statements included in emails. In case of an= y damages or other liabilities arising, employees are fully responsible fo= r the content of their emails.* --0000000000008b51f305a5dea91a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, May 17, 2020 at 11:21 PM Efra= im Flashner <efraim@flashner.co= .il> wrote:
On Sun, May 17, 2020 at 09:41:00PM +1000, Begley Brothers Inc wrote:
> Hi,
> We are now looking to build Linux kernels using Guix instead of Yocto.= =C2=A0 We
> can't see any reason why the builds wouldn't be linux-libre. I= deally we'd
> like our effort to be accepted by upstream guix.
>
> However, being new to Guix we are still coming grips with the best
> practice(s) for what we would like to do.
> We've looked at Guix's linux.scm, and
> Efraim Flashner's post[1] is our primary reference - many thanks E= fraim.

I'd like to embarrassingly mention that I never actually booted any of<= br> my custom kernels. My machine was a bit too slow to regularly compile
for some guess-and-check.

No worries. S= omething is better than nothing and that was very useful outline of possibl= e alternatives.

<snip>

> 1) We did wonder if channels[2] were the way to go with each kernel x.= y.z
> in its own branch and config files therein. Could anyone point us to > packages that setup and use package specific channels?
> 2) Should we be aiming to provide a single package with multiple param= eters
> or is it better to provide a package for each kernel x.y.z, or some ot= her
> partitioning. We'd likely want to script the package definition th= en -
> correct?

I would probably start with one package each and then see how they could be made to inherit from one another or grouped together. The way the
current make-linux-libre procedures work has grown quite a bit but they
should still mostly work as a starting point to add/remove bits for
customizing for your needs.

I don't think I'd go with different branches. If you keep everythin= g in
one branch then it's easier to deduplicate work between the different variants.
=C2=A0
That was our thought too.= =C2=A0
We're just wondering how best to get that branch = content down to the users machine without them having to do anything.
=

Thanks again.

> Appreciate any comments suggestions or tips.
>
> [1]:
> https://= guix.gnu.org/blog/2019/creating-and-using-a-custom-linux-kernel-on-guix-sys= tem/
> [2]: https://guix.gnu.org/manual/en/guix.html#= Channels
>
> --
> Kind Regards
>
> Begley Brothers Inc.
>
>
>=C2=A0 =C2=A0 1. *The content of this email is confidential and intende= d for the
>=C2=A0 =C2=A0 recipient specified in message only. It is strictly forbi= dden to share any
>=C2=A0 =C2=A0 part of this message with any third party, without a writ= ten consent of the
>=C2=A0 =C2=A0 sender. If you received this message by mistake, please r= eply to this
>=C2=A0 =C2=A0 message and follow with its deletion, so that we can ensu= re such a mistake
>=C2=A0 =C2=A0 does not occur in the future.*
>=C2=A0 =C2=A0 2. *This message has been sent as a part of discussion be= tween Begley
>=C2=A0 =C2=A0 Brothers Inc. and the addressee whose name is specified a= bove. Should you
>=C2=A0 =C2=A0 receive this message by mistake, we would be most gratefu= l if you informed
>=C2=A0 =C2=A0 us that the message has been sent to you. In this case, w= e also ask that
>=C2=A0 =C2=A0 you delete this message from your mailbox, and do not for= ward it or any
>=C2=A0 =C2=A0 part of it to anyone else. Thank you for your cooperation= and
>=C2=A0 =C2=A0 understanding.*
>=C2=A0 =C2=A0 3. *Begley Brothers Inc. puts the security of the client = at a high
>=C2=A0 =C2=A0 priority. Therefore, we have put efforts into ensuring th= at the message is
>=C2=A0 =C2=A0 error and virus-free. Unfortunately, full security of the= email cannot be
>=C2=A0 =C2=A0 ensured as, despite our efforts, the data included in ema= ils could be
>=C2=A0 =C2=A0 infected, intercepted, or corrupted. Therefore, the recip= ient should check
>=C2=A0 =C2=A0 the email for threats with proper software, as the sender= does not accept
>=C2=A0 =C2=A0 liability for any damage inflicted by viewing the content= of this email.*
>=C2=A0 =C2=A0 4. *The views and opinions included in this email belong = to their author
>=C2=A0 =C2=A0 and do not necessarily mirror the views and opinions of t= he company. Our
>=C2=A0 =C2=A0 employees are obliged not to make any defamatory clauses,= infringe, or
>=C2=A0 =C2=A0 authorize infringement of any legal right. Therefore, the= company will not
>=C2=A0 =C2=A0 take any liability for such statements included in emails= . In case of any
>=C2=A0 =C2=A0 damages or other liabilities arising, employees are fully= responsible for
>=C2=A0 =C2=A0 the content of their emails.*

--
Efraim Flashner=C2=A0 =C2=A0<efraim@flashner.co.il>=C2=A0 =C2=A0=D7=90=D7=A4=D7= =A8=D7=99=D7=9D =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8
GPG key =3D A28B F40C 3E55 1372 662D=C2=A0 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted=


--
Kind Regards

Begley Brot= hers Inc.

  1. The content of this email is confiden= tial and intended for the=20 recipient specified in message only. It is strictly forbidden to share=20 any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
  2. This message has been= sent as a part of discussion between Begley Brothers Inc. and the addresse= e whose name is specified above. Should=20 you receive this message by mistake, we would be most grateful if you=20 informed us that the message has been sent to you. In this case, we also ask that you delete this message from your mailbox, and do not forward=20 it or any part of it to anyone else. Thank you for your cooperation and=20 understanding.
  3. Begley Brothers Inc. puts= the security of the client at a high priority.=20 Therefore, we have put efforts into ensuring that the message is error=20 and virus-free. Unfortunately, full security of the email cannot be=20 ensured as, despite our efforts, the data included in emails could be=20 infected, intercepted, or corrupted. Therefore, the recipient should=20 check the email for threats with proper software, as the sender does not accept liability for any damage inflicted by viewing the content of=20 this email.
  4. The views and opinions included in this email be= long to their author and do not necessarily mirror the views and opinions of the company.=20 Our employees are obliged not to make any defamatory clauses, infringe,=20 or authorize infringement of any legal right. Therefore, the company=20 will not take any liability for such statements included in emails. In=20 case of any damages or other liabilities arising, employees are fully=20 responsible for the content of their emails.
--0000000000008b51f305a5dea91a--