From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: * X-Spam-Status: No, score=1.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,FROM_LOCAL_NOVOWEL,HK_RANDOM_FROM autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 26884 invoked from network); 8 Mar 2021 12:19:42 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 8 Mar 2021 12:19:42 -0000 Received: from mail-lj1-f169.google.com ([209.85.208.169]) by 1ess; Mon Mar 8 07:15:32 -0500 2021 Received: by mail-lj1-f169.google.com with SMTP id m11so15741023lji.10 for <9front@9front.org>; Mon, 08 Mar 2021 04:15:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:content-transfer-encoding:to:subject:from:date :in-reply-to:mime-version:content-transfer-encoding; bh=myvMZucAgAcxmcZ7CbVDm5Lpy0/PL481UtWsbeVFDKE=; b=TSDKMcx0gjvDfDNBn9F9LN1yqzNaXIONBF0G0C9qlSOLqZ4+4ZB2sa5CgU8FxAJwGa cHO7/hD8QRqa4yy0B7iQ7CzImf7rj4VnsvApstBMbq3xt2va9wS1LToyyHErYCyLUvph Rpn/2yX1aY84vMXGgkFV51pw1HsFBKMtzlDEJfxPDZtpydJJtyuHfDpj9IU7S3NJaQFj Cvjth/URISwKtT7PMIqqrbD5txk+sl11V9pC7mchu4yF+/hN6EyNpBTMx7cBjHIJJBwf 6EeFeVWSzyqChhXq1Kwya3RGVNsa10aE9BU8CNNt2e0F3vu31OlBNN88bCJs35esi4By /jJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:content-transfer-encoding:to:subject :from:date:in-reply-to:mime-version:content-transfer-encoding; bh=myvMZucAgAcxmcZ7CbVDm5Lpy0/PL481UtWsbeVFDKE=; b=MuKFe9xIBk74Iu66EK2ww5jb+55fLX6XvhdLkeTXmEGn6Q3bvva8SWVrtsVdg79LAR oOUOgLX9ICxlxVcn39hQ1DbjznXgAKwdzQgd/wyfi2Dx/7F012gYMrY8T4fjwikaNGTF I+xCUoyKjBxkQ8COM6VYNUvlnbOWO67wvTI1HZ2OVd74ShLLcNXW5Xt2Vwd3zRuos2jU V9fhF8aaVx7UOYpq/or2eFGEF5vNkExgBs08vysC4oyFfBuaH73Lsq4MXpJjD7hcTVp7 EeJJ6hdfRg0taJoLN2ZD1fIIaSynz4ACLbV1NVdQOzmO4B/ySYjgErEnDdssu2qvIIFC r4HA== X-Gm-Message-State: AOAM531ENTC+wWOcjh9AX/IVPDSNcJz+do353I7lYafEp6aw4DHox0uO ++XpTxFHrg0ZhsHjawHDHorXcMxnHRE= X-Google-Smtp-Source: ABdhPJxXlB5zRWKNE/FniEeRctgNML/67fkQ/4cfAPEFqscXC927z5i6ug+uVTLInuqu0bO//kPOQg== X-Received: by 2002:a2e:8e78:: with SMTP id t24mr14116875ljk.161.1615205723044; Mon, 08 Mar 2021 04:15:23 -0800 (PST) Return-Path: Received: from localhost (c-adc9e655.027-406-73746f40.bbcust.telenor.se. [85.230.201.173]) by smtp.gmail.com with ESMTPSA id 188sm805067lfo.0.2021.03.08.04.15.22 for <9front@9front.org> (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Mon, 08 Mar 2021 04:15:22 -0800 (PST) Message-ID: <5B363A6921AF13A6394AA2B6B05DB843@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit To: 9front@9front.org From: "Sigrid Solveig Haflínudóttir" Date: Mon, 08 Mar 2021 13:15:20 +0100 In-Reply-To: <6cbbf99c-e422-4183-8954-a794a042d690@sirjofri.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: shared basic hypervisor replication map/reduce hypervisor CSS control Subject: Re: [9front] distproto: include the files in /lib/firmware/* Reply-To: 9front@9front.org Precedence: bulk Quoth sirjofri : > 08.03.2021 12:10:55 hiro <23hiro@gmail.com>: > > the only downside i see is the purity of our distro... > > right now it contains just stuff that can be generated from the > > source, and maybe some fonts or a few small icons/graphics are the > > only binary content > > I think it is very convenient to have some firmware in the released iso > images. I wouldn't add them to the repo, adding links to them like the > fqa already does is good enough, I think. Since we have the /lib/firmware > directory and it's basically enough to place the files there I don't > think too many adjustments are needed, adding mkfile rules for > downloading the firmware files and packing an iso would be convenient for > automatic packing (I am thinking about doing daily iso images on a server > as well as providing a mirror for 9front isos. Imagine a rule for the > bare iso without firmware and another rule for release isos with > firmware). > > (I am not a lawyer.) > > Just my two cents. > > sirjofri Another way would be to have enough space on FAT parition to copy firmware to ("firmware" directory on that partition) and to bind it on top of /lib/firmware during boot process. ISO stays the same, the user is free to copy firmware as they please after writing the ISO to USB flash drive or whatever. I'm against distributing Intel's (or whomever) binary crap in the default ISO. There WILL be a point where it's going to be either old or missing.