| 1 |
On 2011-05-15, "Paweł Hajdan, Jr." <phajdan.jr@g.o> wrote: |
| 2 |
> On 5/10/11 10:56 PM, Donnie Berkholz wrote: |
| 3 |
>> The reason non-x86/amd64 architectures are so close to x86/amd64 is that |
| 4 |
>> people using "alternative" archs rarely fail to install. The x86/amd64 |
| 5 |
>> numbers start out about 2–3x higher at the beginning of the handbook, |
| 6 |
>> but most of them don't complete it. |
| 7 |
> |
| 8 |
> I just thought about a different possible explanation. When I'm setting |
| 9 |
> up new chroots or other test installs, I frequently only look up |
| 10 |
> information from the first pages of the handbook, like what's the exact |
| 11 |
> command to unpack the stage or what's the right order of steps. Setting |
| 12 |
> up the logger, cron and so on usually doesn't require referring to the |
| 13 |
> handbook. |
| 14 |
> |
| 15 |
|
| 16 |
... and there are people like me who prints out the handbook once |
| 17 |
every handbook change. I'd use the exact same printout for, let's see, |
| 18 |
7-8 installations. |
| 19 |
|
| 20 |
So, my guess is that every 'handbook read' for x86/amd64 might |
| 21 |
represent more than one installs. |
| 22 |
|
| 23 |
>> It's tough to know how long an installation sticks around, but that many |
| 24 |
>> new installs per day is pretty impressive. |
| 25 |
> |
| 26 |
> Yeah, and also it looks like the interest in arches like sparc, ppc, |
| 27 |
> hppa and so on is much higher than what I expected. That's great! |
| 28 |
> |
| 29 |
> |
| 30 |
|
| 31 |
IMO, the only way to get a precise number is to have a 'call-home' |
| 32 |
script every install. But of course there's this question of ethics |
| 33 |
and privacy... |
| 34 |
|
| 35 |
-- |
| 36 |
Pandu E Poluan - IT Optimizer |
| 37 |
My website: http://pandu.poluan.info/ |
Archives