From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] quick installs on older/embedded hardware
Date: Wed, 4 Jun 2014 20:34:48 -0400 [thread overview]
Message-ID: <20140605003448.GA13556@waltdnes.org> (raw)
In-Reply-To: <loom.20140604T204249-435@post.gmane.org>
On Wed, Jun 04, 2014 at 07:16:33PM +0000, James wrote
> Anyway, I'd like to hear all of the ideas, including various
> disciplined (structured) approaches I can take to minimize uniqueness
> in my lab and what I'm currently doing (mostly). I also have usb
> sticks, but I've found booting various offernings on usb, particularly
> older hardware, to be too biosed_burdened.
>
> Bear in mind, I also have dozens of embedded boards, some x86, but
> mostly arm based, that are also in the mix. As soon as some less expensive
> arm64 (aarch64) boards become available, those too will become much more
> prevalent in my lab. I need some new organizational (software and Image)
> ideas. My hardware is very well organied on large, open racks with
> lots of UPS power and easy physical access to each box/board.
You may be interested in buildroot http://buildroot.net/ and
http://buildroot.net/about.html It's nominally aimed at cross-compiling
for embedded systems, but it looks like it handles just about
everything. I'm not a developer, so I don't know if this is what you're
looking for, but it sounds interesting.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2014-06-05 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 19:16 [gentoo-user] quick installs on older/embedded hardware James
2014-06-04 23:24 ` Alan McKinnon
2014-06-06 17:20 ` [gentoo-user] " James
2014-06-06 23:38 ` Alan McKinnon
2014-06-05 0:34 ` Walter Dnes [this message]
2014-06-05 15:41 ` James
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=20140605003448.GA13556@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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