From: Gregory Shearman <zekeyg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: but cool - NASDAQ is gentoo powered
Date: Thu, 18 Aug 2011 19:35:57 +1000 [thread overview]
Message-ID: <20110818093557.GA19850@pacific.net.au> (raw)
In-Reply-To: <hqKim-7oo-7@gated-at.bofh.it>
In linux.gentoo.user, you wrote:
> On Tuesday 16 August 2011 02:48:30 Michael Mol wrote:
>
> I have a midget server on the LAN (Atom N270) which runs Gentoo, but it's
> too underpowered to do all the compiling itself, so it NFS-exports its
> packages directory to my workstation, where I have a 32-bit chroot set up as
> an image of the Atom. Emerging is done here, making the packages available
> for installation on the Atom. This is a cumbersome operation though.
That's interesting. I run a SheevaPlug with Gentoo onboard. It runs at
1.2G and has half a G of memory. I have no trouble compiling gentoo on
this little server. It works as a file server, backup server, web
server and portage server (distfiles and portage sync for the gentoos on
my network).
Is ARM more efficient than the intel atom?
--
Regards,
Gregory.
next parent reply other threads:[~2011-08-18 9:37 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hqfRg-6nt-9@gated-at.bofh.it>
[not found] ` <hqh6G-8nU-9@gated-at.bofh.it>
[not found] ` <hqKim-7oo-7@gated-at.bofh.it>
2011-08-18 9:35 ` Gregory Shearman [this message]
2011-08-18 16:54 ` [gentoo-user] Re: OT: but cool - NASDAQ is gentoo powered James
2011-08-16 9:48 [gentoo-user] " jdm
-- strict thread matches above, loose matches on Subject: below --
2011-08-16 0:28 Adam Carter
2011-08-16 1:48 ` Michael Mol
2011-08-16 2:12 ` Dale
2011-08-16 2:36 ` Pandu Poluan
2011-08-16 3:37 ` James Wall
2011-08-16 7:29 ` Jens Reinemuth
2011-08-16 3:37 ` Adam Carter
2011-08-16 4:39 ` Matthew Finkel
2011-08-16 6:19 ` Philip Webb
2011-08-16 6:20 ` Walter Dnes
2011-08-16 6:56 ` Joost Roeleveld
2011-08-16 7:43 ` victor romanchuk
2011-08-16 9:10 ` Alan McKinnon
2011-08-16 9:15 ` Joost Roeleveld
2011-08-16 9:30 ` Alan McKinnon
2011-08-16 9:39 ` Joost Roeleveld
2011-08-16 11:25 ` Pandu Poluan
2011-08-18 7:44 ` Neil Bothwick
2011-08-16 9:47 ` Michael Schreckenbauer
2011-08-16 12:14 ` Todd Goodman
2011-08-16 15:35 ` Paul Hartman
2011-08-16 15:48 ` Daniel da Veiga
2011-08-16 17:06 ` Canek Peláez Valdés
2011-08-16 20:58 ` Stefan G. Weichinger
2011-08-16 21:06 ` Paul Hartman
2011-08-16 21:18 ` Stefan G. Weichinger
2011-08-16 23:35 ` Canek Peláez Valdés
2011-08-16 23:24 ` Canek Peláez Valdés
2011-08-17 14:04 ` Stefan G. Weichinger
2011-08-16 23:21 ` Canek Peláez Valdés
2011-08-16 20:27 ` Florian Philipp
2011-08-17 4:45 ` Norman Rieß
2011-08-17 8:59 ` Peter Humphrey
2011-08-17 11:44 ` Joost Roeleveld
2011-08-18 4:45 ` Norman Rieß
2011-08-18 7:11 ` Matthew Finkel
2011-08-18 7:58 ` Dale
2011-08-18 9:07 ` Matthew Finkel
2011-08-18 8:23 ` Norman Rieß
2011-08-18 8:57 ` Matthew Finkel
2011-08-18 10:08 ` James Broadhead
2011-08-18 11:45 ` Norman Rieß
2011-08-18 11:59 ` James Broadhead
2011-08-18 7:50 ` Neil Bothwick
2011-08-18 8:41 ` Norman Rieß
2011-08-18 9:08 ` Neil Bothwick
2011-08-18 9:55 ` Norman Rieß
2011-08-17 10:35 ` Alan Mackenzie
2011-08-16 2:28 ` Pandu Poluan
2011-08-17 12:32 ` James Broadhead
2011-08-17 22:44 ` Sebastian Beßler
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=20110818093557.GA19850@pacific.net.au \
--to=zekeyg@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