From owner-freebsd-chat Wed Jul 24 12:26:47 1996 Return-Path: owner-chat Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08828 for chat-outgoing; Wed, 24 Jul 1996 12:26:47 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA08817 for ; Wed, 24 Jul 1996 12:26:45 -0700 (PDT) Received: from xsvr2.cup.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA071886403; Wed, 24 Jul 1996 12:26:44 -0700 Received: by xsvr2.cup.hp.com (1.39.111.2/15.5+ECS 3.3) id AA221876403; Wed, 24 Jul 1996 12:26:43 -0700 From: "Josef C. Grosch" Message-Id: <9607241226.ZM22185@xsvr2.cup.hp.com> Date: Wed, 24 Jul 1996 12:26:43 -0700 In-Reply-To: Poul-Henning Kamp "Beatles does UNIX :-)" (Jul 24, 1:23am) References: <270.838164218@critter.tfs.com> X-Mailer: Z-Mail (3.2.1 10apr95) To: Poul-Henning Kamp Subject: Re: Beatles does UNIX :-) Cc: chat@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jul 24, 1:23am, Poul-Henning Kamp wrote: > Subject: Beatles does UNIX :-) > > Forwarded: > > Eleanor Rigby > - ------------- > Eleanor Rigby > Sits at the keyboard > And waits for a line on the screen > Lives in a dream > Waits for a signal > Finding some code > That will make the machine do some more. > What is it for? > > All the lonely users, where do they all come from? > All the lonely users, why does it take so long? > > Guru MacKenzie > Typing the lines of a program that no one will run; > Isn't it fun? > Look at him working, > Munching some chips as he waits for the code to compile; > It takes a while... > > All the lonely users, where do they all come from? > All the lonely users, why does it take so long? > > Eleanor Rigby > Crashes the system and loses 6 hours of work; > Feels like a jerk. > Guru MacKenzie > Wiping the crumbs off the keys as he types in the code; > Nothing will load. > > All the lonely users, where do they all come from? > All the lonely users, why does it take so long? > ================================================= > > Unix Man > - -------- > He's a real UNIX Man > Sitting in his UNIX LAN > Making all his UNIX .plans > For nobody. > > Knows the blocksize from du(1) > Cares not where /dev/null goes to > Isn't he a bit like you > And me? > > UNIX Man, please listen(2) > My lpd(8) is missin' > UNIX Man > The wo-o-o-orld is at(1) your command. > > He's as wise as he can be > Uses lex and yacc and C > UNIX Man, can you help me > At all? > > UNIX Man, don't worry > Test with time(1), don't hurry > UNIX Man > The new kernel boots, just like you had planned. > > He's a real UNIX Man > Sitting in his UNIX LAN > Making all his UNIX .plans > For nobody ... > Making all his UNIX .plans > For nobody. > ================================================= > > Write in C > - ---------- > When I find my code in tons of trouble, > Friends and colleagues come to me, > Speaking words of wisdom: > "Write in C." > > As the deadline fast approaches, > And bugs are all that I can see, > Somewhere, someone whispers: > "Write in C." > > Write in C, Write in C, > Write in C, oh, Write in C. > LOGO's dead and buried, > Write in C. > > I used to write a lot of FORTRAN, > For science it worked flawlessly. > Try using it for graphics! > Write in C. > > If you've just spent nearly 30 hours, > Debugging some assembly, > Soon you will be glad to > Write in C. > > Write in C, Write in C, > Write in C, yeah, Write in C. > BASIC's not the answer. > Write in C. > > Write in C, Write in C > Write in C, oh, Write in C. > Pascal won't quite cut it. > Write in C. > ================================================= > > Something > - --------- > Something in the way it fails, > Defies the algorithm's logic! > Something in the way it coredumps... > > I don't want to leave it now > I'll fix this problem somehow > > Somewhere in the memory I know, > A pointer's got to be corrupted. > Stepping in the debugger will show me... > > I don't want to leave it now > I'm too close to leave it now > > You're asking me can this code go? > I don't know, I don't know... > What sequence causes it to blow? > I don't know, I don't know... > > Something in the initializing code? > And all I have to do is think of it! > Something in the listing will show me... > > I don't want to leave it now > I'll fix this tonight I vow! > > >-- End of excerpt from Poul-Henning Kamp Very good! Poul-Henning, you have way too much free time on your hands. :-) Josef -- Josef Grosch, 47LG4 | "Laugh while you can, | My opinions are mine, not jgrosch@cup.hp.com | monkey boy!" | HPs. They have'nt paid for (408) 447-0467 | - John Warfin - | them yet ! :-)