From: 白い熊＠相撲道 <help-guix_gnu.org@sumou.com>
To: yasu <yasu@yasuaki.com>
Cc: GNU Guix help <help-guix@gnu.org>
Subject: Re: Installation: Load non-free wifi firmware (iwlwifi)
Date: Thu, 12 May 2022 09:37:42 +0200 [thread overview]
Message-ID: <5a1a0ee136c655fd2853c64894da51c2@sumou.com> (raw)
In-Reply-To: <30fa5b18f1c6154d3a93bdae671aa39ef6961d5a.camel@yasuaki.com>
On 2022-05-11 14:31, yasu wrote:
> This is also an old topic, but we need lesser-help-guix@...
> The help-guix@... seems so much against even discussion of such
> things...
>
> So for now (and let me stress, I do not like this situation of self-
> imposed-gagging and would like to help create alternative communication
> forums), let me send you something personally!
Many thanks, Yasu.
I was able to get it working according to the instructions sent
privately, including adding a channel for the kernel source etc.
Seeing as how there might have been criticism in the past here on the
list in discussing topics, which some think are inconducive to promote
software freedom - I don't wish to damage the culture here and fully
describe the solution, if it is indeed frowned upon here.
On the other hand, I feel the same way as Yasu describes above - for
instance for me I think seeing the solution, which I could not have
figured out myself is actually conducive towards learning more guix and
scheme and perhaps developing some snippets in the future that could
help someone else.
For this reason I'd think it'd be beneficial to fully discuss the Guix
solution here. Moderators - can you give guidance on this?
---
Best regards / 宜しく御願い致します / S pozdravem / C уважением / Z poważaniem /
Mit freundlichen Grüßen
白い熊
next prev parent reply other threads:[~2022-05-12 7:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 12:19 Installation: Load non-free wifi firmware (iwlwifi) 白い熊
2022-05-11 12:31 ` yasu
2022-05-12 7:37 ` 白い熊＠相撲道 [this message]
2022-05-12 16:00 ` zimoun
2022-05-12 20:19 ` David Lecompte
2022-05-12 23:53 ` Yasuaki Kudo
2022-05-13 11:59 ` Tobias Geerinckx-Rice
2022-05-13 1:33 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2018-03-02 17:25 Pierre Neidhardt
2018-03-02 17:41 ` Pierre Neidhardt
2018-03-02 20:13 ` Carlo Zancanaro
2018-03-02 18:04 ` Adonay Felipe Nogueira
2018-03-05 12:32 ` Adonay Felipe Nogueira
2018-03-05 14:00 ` Clément Lassieur
2018-03-23 13:29 ` Pierre Neidhardt
2018-03-25 5:34 ` Chris Marusich
2018-03-25 6:14 ` Pierre Neidhardt
2018-03-25 10:21 ` Hartmut Goebel
2018-03-27 9:45 ` Ludovic Courtès
2018-03-27 22:05 ` Mark H Weaver
2018-04-13 11:55 ` Hartmut Goebel
2018-03-25 10:57 ` Marius Bakke
2018-03-29 5:11 ` Chris Marusich
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a1a0ee136c655fd2853c64894da51c2@sumou.com \
--to=help-guix_gnu.org@sumou.com \
--cc=help-guix@gnu.org \
--cc=yasu@yasuaki.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).