public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: Arch teams Resources (round 2) - General issues
Date: Sun, 15 May 2011 12:29:41 +0200	[thread overview]
Message-ID: <4DCFAB15.3070901@gentoo.org> (raw)
In-Reply-To: <20110510205612.GD30373@comet.mayo.edu>

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

On 5/10/11 10:56 PM, Donnie Berkholz wrote:
> The reason non-x86/amd64 architectures are so close to x86/amd64 is that 
> people using "alternative" archs rarely fail to install. The x86/amd64 
> numbers start out about 2–3x higher at the beginning of the handbook, 
> but most of them don't complete it.

I just thought about a different possible explanation. When I'm setting
up new chroots or other test installs, I frequently only look up
information from the first pages of the handbook, like what's the exact
command to unpack the stage or what's the right order of steps. Setting
up the logger, cron and so on usually doesn't require referring to the
handbook.

> It's tough to know how long an installation sticks around, but that many 
> new installs per day is pretty impressive.

Yeah, and also it looks like the interest in arches like sparc, ppc,
hppa and so on is much higher than what I expected. That's great!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  reply	other threads:[~2011-05-15 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D73AB04.8050301@gentoo.org>
2011-05-10 19:02 ` [gentoo-project] Re: Arch teams Resources (round 2) - General issues Jorge Manuel B. S. Vicetto
2011-05-10 20:30   ` David Abbott
2011-05-10 20:56   ` Donnie Berkholz
2011-05-15 10:29     ` "Paweł Hajdan, Jr." [this message]
2011-05-15 13:13       ` Pandu Poluan

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=4DCFAB15.3070901@gentoo.org \
    --to=phajdan.jr@gentoo.org \
    --cc=gentoo-project@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