unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Librem (was: Installation: Load non-free wifi firmware (iwlwifi))
Date: Fri, 04 May 2018 10:15:56 -0500	[thread overview]
Message-ID: <87po2b3103.fsf@dustycloud.org> (raw)
In-Reply-To: <87zi1j2myo.fsf@gmail.com>

Pierre Neidhardt writes:

> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> Another option is to find a system that respects your freedom and does
>> not require proprietary software to run.  I have a LibreBoot laptop I
>> purchased from MiniFree, and I love it!  I know that purchasing a
>> replacement computer that respects your freedom can seem like an
>> expensive option, but if you have the money, then it's an option:
>>
>> https://minifree.org/
>>
>> You may also be interested in looking at:
>>
>> https://www.fsf.org/resources/hw/endorsement/respects-your-freedom
>
> How does it compare to Purism?
>
> 	https://puri.sm/products/
>
> Their Librem 13 looks very attractive indeed!  Compared to my Xiaomi Air
> 13", it's seems to be a bit better while also more expansive, but I
> suppose it's the price to pay for a good cause! :)
>
> Any Librem user out there?

I'm running a LibreM 13.  GuixSD worked perfectly out of the box.  It's
nice to run GNOME again (after not having working OpenGL for ages on my
x200).  The hardware kill switches for wifi / camera / microphone are
also nice.  It's only been a week, but my impression so far is: if you
can afford to fork over the cash for it, it's worth it.

  parent reply	other threads:[~2018-05-04 15:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 17:25 Installation: Load non-free wifi firmware (iwlwifi) 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
2018-05-01 19:30   ` Librem (was: Installation: Load non-free wifi firmware (iwlwifi)) Pierre Neidhardt
2018-05-02 18:07     ` Librem Joshua Branson
2018-05-03  6:47       ` Librem Chris Marusich
2018-05-03  7:44         ` Librem Pierre Neidhardt
2018-05-09  6:07           ` Librem Chris Marusich
2018-05-09 16:58             ` Librem Nils Gillmann
2018-05-04 20:56         ` Librem Joshua Branson
2018-05-04 15:15     ` Christopher Lemmer Webber [this message]
2018-05-04 15:17       ` Librem (was: Installation: Load non-free wifi firmware (iwlwifi)) Pierre Neidhardt
2018-05-04 16:32       ` Librem Mike Gerwitz

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=87po2b3103.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=ambrevar@gmail.com \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).