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=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 29460 invoked from network); 8 Mar 2021 12:40:16 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 8 Mar 2021 12:40:16 -0000 Received: from mail.typed-hole.org ([199.247.9.36]) by 1ess; Mon Mar 8 07:35:04 -0500 2021 Received: from mail.typed-hole.org (localhost [127.0.0.1]) by mail.typed-hole.org (OpenSMTPD) with ESMTP id b7fc27d5 for <9front@9front.org>; Mon, 8 Mar 2021 12:34:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=typed-hole.org; h= content-type:content-transfer-encoding:from:mime-version:subject :date:message-id:references:in-reply-to:to; s=20190925; bh=sRKPU TYjbW4VmQXArbB/NFgrM2c=; b=tgictgMGhVHPaqUNcXUmhrm7+Jtay9GZv+Gjn /denC2/Vno5GkbjOiWv6+IM6+9CjCTwRTT53zJK4RW6cf3bcYNxzVK1kMrxckmKA XxUGLBXnLD2UUUoRTa6aYNk/rKvrz4818b0oNQSkS1dltgoAcTwsX+1hKnw2Pt+z 6V7uBQ8a40GwWL/+DZzf3mblbIWmbty5WTczY0vHf4Jw144ZOJtuvki2/BfWi0dM OeG9AfvMfPAcha7yfM7lUWbqLLPbmA58f59B0gSwgCfbo1A3tVeelxJUxXO7d5f6 o9d/D8ieQmsnevCt5R0ZqBs8CfdxbVnLCRt2I4US2Iri3USoQ== DomainKey-Signature: a=rsa-sha1; c=nofws; d=typed-hole.org; h= content-type:content-transfer-encoding:from:mime-version:subject :date:message-id:references:in-reply-to:to; q=dns; s=20190925; b= H/TwjEn2lKyzrxMYZqVC3RtceIoRy24csXTxpjTTl8rdUfkK8CA9gDDUtsseWaut /LFS/1UxwHPMEVloaxsVaNgbCiyWnWW/lFEy0cxzLHo89jYt/Jq4FJp2a7qLbMdl JNvsPVVUsL/c4BckLA8+35saP3ktOldLw7EKraKOftM3ery1g9TI2+T1ymb8WdsE 61wIqopmJwu2XyAu9YYBcAhOcL7xxz+LMj13DePIh1f0E9TqBH/neVT6m8EU1vNv /j4Q0c4OmDNlAXxs7MlXgK8eNLNisLhZVyKzfUeSln0fr4pijAFMEap35h8GF/QO 9TLfPJOB8+GbaiWI7iGkKg== Received: from [192.168.0.23] (87-231-19-8.rev.numericable.fr [87.231.19.8]) by mail.typed-hole.org (OpenSMTPD) with ESMTPSA id 5a4a2941 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO) for <9front@9front.org>; Mon, 8 Mar 2021 12:34:58 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Julien Blanchard Mime-Version: 1.0 (1.0) Date: Mon, 8 Mar 2021 13:34:57 +0100 Message-Id: References: <5B363A6921AF13A6394AA2B6B05DB843@gmail.com> In-Reply-To: <5B363A6921AF13A6394AA2B6B05DB843@gmail.com> To: 9front@9front.org X-Mailer: iPhone Mail (18D52) List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: virtual optimized replication Subject: Re: [9front] distproto: include the files in /lib/firmware/* Reply-To: 9front@9front.org Precedence: bulk > Le 8 mars 2021 =C3=A0 13:19, Sigrid Solveig Hafl=C3=ADnud=C3=B3ttir a =C3=A9crit : >=20 > =EF=BB=BFQuoth 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 >>=20 >> I think it is very convenient to have some firmware in the released iso=20= >> images. I wouldn't add them to the repo, adding links to them like the=20= >> fqa already does is good enough, I think. Since we have the /lib/firmware= =20 >> directory and it's basically enough to place the files there I don't=20 >> think too many adjustments are needed, adding mkfile rules for=20 >> downloading the firmware files and packing an iso would be convenient for= =20 >> automatic packing (I am thinking about doing daily iso images on a server= =20 >> as well as providing a mirror for 9front isos. Imagine a rule for the=20 >> bare iso without firmware and another rule for release isos with=20 >> firmware). >>=20 >> (I am not a lawyer.) >>=20 >> Just my two cents. >>=20 >> sirjofri >=20 > 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. >=20 > 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. Maybe something like OpenBSD does where a tool will try to download the firm= wares after installation?