From: "Hunter Jozwiak" <hunter.t.joz@gmail.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] System76 Hardware
Date: Fri, 2 Oct 2015 18:07:15 -0400 [thread overview]
Message-ID: <00a801d0fd5e$b2c14c70$1843e550$@gmail.com> (raw)
In-Reply-To: <CAGfcS_mTMbAep5ijWE2xJME2k6hNib174xcUnj71PBiKzO+D9A@mail.gmail.com>
-----Original Message-----
From: freemanrich@gmail.com [mailto:freemanrich@gmail.com] On Behalf Of Rich Freeman
Sent: Friday, October 2, 2015 18:02
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System76 Hardware
On Fri, Oct 2, 2015 at 4:28 AM, Nuno Magalhães <nunomagalhaes@eu.ipp.pt> wrote:
> I'd say the method is the same as with any other laptop: pick one
> specific model, look into its hardware (this[1] and a liveCD may be
> handy), search for drivers, search "gento" + <specific hardware>,
> follow the handbook.
> You have the slight assurance those laptops are built with linux in
> mind; anything else is just business as usual.
Unless they or Ubuntu are carrying out-of-mainline drivers I'd say your assurance is more than slight, but I'm not reimbursing you if for some reason it doesn't work. :)
If you want to run a 2.6-series kernel on it you could have problems, but if you don't mind running a recent stable (ie what Gentoo ships by default anyway) I suspect you'll be fine. Worst case you'll just run closer to bleeding-edge on ~arch for the kernel for a few months until longterm catches up, and lots of people around here run ~arch anyway.
--
Rich
I will be running to ~arch on install anyways.
prev parent reply other threads:[~2015-10-02 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 20:00 [gentoo-user] System76 Hardware Hunter Jozwiak
2015-10-02 8:28 ` Nuno Magalhães
2015-10-02 8:55 ` Emanuele Rusconi
2015-10-03 15:41 ` Nuno Magalhães
2015-10-02 22:02 ` Rich Freeman
2015-10-02 22:07 ` Hunter Jozwiak [this message]
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='00a801d0fd5e$b2c14c70$1843e550$@gmail.com' \
--to=hunter.t.joz@gmail.com \
--cc=gentoo-user@lists.gentoo.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