From: Leo Famulari <leo@famulari.name>
To: Blake Shaw <blake@nonconstructivism.com>
Cc: help-guix@gnu.org
Subject: Re: Guix Home Entertainment SoC Media Server?
Date: Fri, 7 Jan 2022 21:33:12 -0500 [thread overview]
Message-ID: <Ydj36Afg/ZXtg5Dw@jasmine.lan> (raw)
In-Reply-To: <87y23r6hjj.fsf@nonconstructivism.com>
On Fri, Jan 07, 2022 at 04:06:56PM +0700, Blake Shaw wrote:
> I just got a TV and want to put together a little SoC home media server for
> it (perhaps with beaglebone black, as that appears to be the recommended
> SoC for Guix). Has anyone had any experience with this? Thoughts?
> I figure it could be a fun use of `Guix Deploy`, but I've never put
> together a SoC media server before, so I'm not sure what packages to
> peek at, or what "out of the box" (re: raspbian etc) options are
> available.
I think this would be a great project for Guix. It's something that Guix
should be really good at, once all the wrinkles are ironed out.
Although the BeagleBone Black is a very nice computer in many way, I do
recommend against it for Guix System because our build farm support for
its CPU architecture (armhf) is currently sub-par. And the BBB's CPU is
optimized for low-power use, so building packages on it will be slow.
I would search for a 64-bit ARM computer. That is, the "aarch64" CPU
architecture. We have better build farm support and it will probably
continue to improve.
next prev parent reply other threads:[~2022-01-08 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 9:06 Guix Home Entertainment SoC Media Server? Blake Shaw
2022-01-07 13:47 ` Edouard Klein
2022-01-08 2:33 ` Leo Famulari [this message]
2022-01-13 7:56 ` phodina
-- strict thread matches above, loose matches on Subject: below --
2022-01-07 21:13 Blake Shaw
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=Ydj36Afg/ZXtg5Dw@jasmine.lan \
--to=leo@famulari.name \
--cc=blake@nonconstructivism.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).