From: "Sigrid Solveig HaflÃnudóttir" <ftrvxmtrx@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] distproto: include the files in /lib/firmware/*
Date: Mon, 08 Mar 2021 13:15:20 +0100 [thread overview]
Message-ID: <5B363A6921AF13A6394AA2B6B05DB843@gmail.com> (raw)
In-Reply-To: <6cbbf99c-e422-4183-8954-a794a042d690@sirjofri.de>
Quoth sirjofri <sirjofri+ml-9front@sirjofri.de>:
> 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.
next prev parent reply other threads:[~2021-03-08 12:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 17:02 kemal
2021-03-07 17:20 ` ori
2021-03-07 17:36 ` kemal
2021-03-07 18:20 ` ori
2021-03-07 18:58 ` kemal
2021-03-07 19:11 ` kemal
2021-03-08 10:59 ` kemal
2021-03-08 11:10 ` hiro
2021-03-08 11:58 ` sirjofri
2021-03-08 12:15 ` Sigrid Solveig Haflínudóttir [this message]
2021-03-08 12:34 ` Julien Blanchard
2021-03-08 12:44 ` kemal
2021-03-08 12:55 ` hiro
2021-03-08 13:18 ` kemal
2021-03-08 13:28 ` hiro
2021-03-08 13:58 ` kemal
2021-03-08 14:03 ` hiro
2021-03-08 15:32 ` Stanley Lieber
2021-03-08 16:07 ` cinap_lenrek
2021-03-08 17:58 ` kemal
2021-03-08 15:29 ` Stanley Lieber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5B363A6921AF13A6394AA2B6B05DB843@gmail.com \
--to=ftrvxmtrx@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).