From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] distproto: include the files in /lib/firmware/*
Date: Mon, 8 Mar 2021 14:28:13 +0100 [thread overview]
Message-ID: <CAFSF3XMCYKh-RbQxTYk15i64S4j14Vd0tYB4=B=eZj+VzeXdnA@mail.gmail.com> (raw)
In-Reply-To: <_iAR0uGb9YWEeNW0Sa8A1mLwPsEi7yVEV5svbUpqWX35oRBbAgT2w2ImQSq_S7hmO1PjdwNlFQ0_3vOjnP7TSgWoVkSAEKm0rviz26TdsQ0=@protonmail.com>
yes and yes.
in terms of being hunted down by powerful rich assholes with money and
lawyers, we're obviously at the mercy of our lack of relevance. that's
the only thing that protects us. and perhaps common decency (i can
never be sure about it but i can hope).
it doesn't matter whether it seems like a modification to YOU.
somebody with enough money can make any court believe that looking
wrongly at the binary is already a violation of somebody's unalienable
human right or similar bullshit.
On 3/8/21, kemal <kemali13@protonmail.com> wrote:
>> the reason i'd want it all built in is bec. then you can netboot over
>> wifi without needing an installation.
>
> Do you mean into to the kernel? Well, that can be a good reason.
>
> Also just realised, is merging the fw in to the kernel is legal?
> License gives you permission to **just** redistribute and use,
> I don't know if building it into the kernel can be count as
> "modification".
>
next prev parent reply other threads:[~2021-03-08 13:33 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
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 [this message]
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='CAFSF3XMCYKh-RbQxTYk15i64S4j14Vd0tYB4=B=eZj+VzeXdnA@mail.gmail.com' \
--to=23hiro@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).