public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Borgerding <mark@borgerding.net>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OFFTOPIC]   "smack the penguin"  2.4 vs 2.6
Date: Sat, 24 Jan 2004 11:08:56 -0500	[thread overview]
Message-ID: <40129898.6020702@borgerding.net> (raw)
In-Reply-To: <401284CD.7080006@borgerding.net>

Mark Borgerding wrote:

> Eduard Bloch wrote:
>
>> #include <hallo.h>
>> * Chris Friesen [Fri, Jan 23 2004, 02:36:59PM]:
>>  
>>
>>> Diversion for friday afternoon...how far can you get?
>>>
>>> Personal best is 586
>>>   
>>
>>
>> Which means that you are playing it either on a Windows box (what a
>> shame) or cheating somehow or you have a 5Ghz box or something else is
>> wrong on regular Linux systems. I do not any Linux user who got
>> more than 325.5 with the Linux version of the Shockwave plugin.
>>  
>>
>
> Sounds like 3/4 of the programmers I've ever worked with --  if they 
> can't figure out how to do it, then it can't be done and anyone who 
> says otherwise must be lying or cheating.
>
>
> Still, it does seem like the game is much less predictable on some 
> systems.  I have a linux laptop that plays it quite nicely (thus the 
> 593.4 I reported earlier).  I tried it on my desktop at home, and it 
> was very jerky.
>
> The two systems are pretty comparable.
>
> For anyone who cares: here's the main differences with laptop (good) 
> on the left and the desktop (bad) on the right:
>
> Mozilla: 1.5 on both, build dates 20031107 vs 20031007
> Flash Version:    6.0.79.0   vs   6.0.69.0
> CPU:   Pent M 1700   vs Athlon XP 2100+
> Video: ATI Radeon M9 vs Matrox G400      <=== I think this is the problem
> Kernel: 2.4.21 (debian) vs 2.6.1
>
> I am going to reboot to check against the 2.4 kernel. Who knows? Maybe 
> there will be a pingu bug report against the 2.6 kernel series.


... doesn't seem the same.

It appears that 2.4.22 may be better suited to penguin abuse than 2.6.1.

I rebooted my desktop to 2.4.22.  Within a minute,  I tied my record 
from the laptop.
( http://www.borgerding.net/pingu_proof.png )

Still, the results are far from scientific or conclusive.  I need some 
objective smackage.
Maybe I will try a blind study with my nieces tonight.  I'll reboot the 
machine into either 2.4.22 or 2.6.1 and record their scores.

Coming soon to a techie-site near you, "Pingumark 2004".

- Mark Borgerding




  reply	other threads:[~2004-01-24 16:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 19:36 [OFFTOPIC] "smack the penguin" Chris Friesen
2004-01-23 12:02 ` Witukind
2004-01-23 21:20   ` Robert White
2004-01-23 21:38     ` Witukind
2004-01-23 21:55     ` Ingo Oeser
2004-01-23 21:11 ` Omkhar Arasaratnam
2004-01-26 13:10   ` Andrei Mikhailovsky
2004-01-23 21:47 ` Markus Plail
2004-01-23 21:54   ` Kevin P. Fleming
2004-01-23 23:11 ` Mark Borgerding
2004-01-23 23:29 ` Jonathan Higdon
2004-01-24  9:52 ` Eduard Bloch
2004-01-24 10:07   ` Måns Rullgård
2004-01-24 10:16     ` Rus Foster
2004-01-24 10:30     ` Han Boetes
2004-01-24 11:06       ` Måns Rullgård
2004-01-24 21:36       ` Marcos D. Marado Torres
2004-01-24 21:41         ` Marcos D. Marado Torres
2004-01-24 22:19           ` Nuno Alexandre
2004-01-24 23:06             ` Neil Ferguson
2004-01-27 20:28               ` "Fernando O. Korndörfer"
2004-01-24 23:11             ` jdow
2004-01-25  0:00               ` David S. Miller
2004-01-25 10:22           ` Rob
2004-01-24 23:14         ` Kevin P. Fleming
2004-01-24 13:26     ` Witukind
2004-01-24 10:09   ` Jurjen Oskam
2004-01-24 10:13   ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-24 10:33     ` Lionel Bouton
2004-01-24 11:57   ` Tomasz Torcz
2004-01-24 14:44   ` Mark Borgerding
2004-01-24 16:08     ` Mark Borgerding [this message]
2004-01-27 10:13 ` Voicu Liviu
2004-01-27 10:27 ` Voicu Liviu

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=40129898.6020702@borgerding.net \
    --to=mark@borgerding.net \
    --cc=linux-kernel@vger.kernel.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