[alt.hackers] Now I'm annoyed.

newton@ARISTOTLE.ILS.NWU.EDU (David Newton) (02/20/91)

Oh!  So MANY dumb things to point out!!!!

#1
From Mark Bradford:
> Au contraire, m'sieur.  Access to this newsgroup is restricted only to those
> so lazy or unobservant that they can't FIGURE IT OUT.  I did so without

   "can't"...  I hardly think this is a matter of ability, but choice of
focus.  If you can figure out, chances are a billion to one for that I could
too.

#2
From Mark Bradford:
> Or that you're not hacking anything.  What's yer point?  Why did you
> bother in the first place?

   Hmm, I've been flamed a couple times for not posting the ObHack, even though
I've already explained why.  So.
   ObHack: Dropping down from the ceiling at IIT into a room with a bunch of
people in uniforms and pulsing lasers (the people didn't have the lasers,
silly, they were on a table (the lasers, not the people)).
   ObHack: I design and build little control computers.  I design and code
little multitasking (pre-emptive and non-pre-emptive depending on my frame
of mind) to do little neat things, like parallel process the mandelbrot set
(sort of like Ciarcia's design)
   ObHack: I write user-interface code in Lisp on a Mac.  'nuff said on that
one.
   ObHack: Interactive 8085 disassembler/emulator.  Sure, anyone can write a
disassembler, but I'll bet most people haven't.  (Sorta like hacking news
stuff, eh?)  Also has an auto-disassemble mode that will get every instruction
in the data space.  Extensible to disassemble any micro.  Windows (written on
Atari ST, also 'nuff said).
   ObHack: Virtual micrcoded microprocessor.  Dump in a microcode source file,
dump in a list of assembler instructions and their microcode routine labels,
and an assembler file.  Assembles microcode, "macro"code, then proceeds to
run it.  Features: breakpoints (both in microcode and "macro"code, variable
trace, memory window.  Also on atari ST.  Kinda cool

   Must I go one?  There _are_ more.  I just don't feel a need to prove myself
to anybody.

Still from Mark Bradford:
> No.  But I s'pose you'd have the FSF accept code from every Tom, Dick,
> and Sally, regardless of whether or not it was written by someone who
> knew what they were doing?

   Umm, I don't know how much GNU stuff you've looked over.  I've seen better
code, sorry to say.  Not that I'm knocking them, nor am I saying that I could
do better (I still haven't finished my linker yet, so I don't know how they
work really.  gimme a few more weeks.), or that I even wanna try to do better.

Yet more:
> Ob. hack: Minutes after I got a PC C compiler, I wrote a replacement
> for cd that understood forward slashes and CDPATH.  Felt good.

   You stud.  There is a DOS call that will deal with the slashes...  Of 
course, software has to check...  This will also deal with command-line 
argument things (i.e. replace "/" with "-".

From Leo Bicknell:
> [paper clip hack]

   We're getting ridiculous here, if this is a "hack"...  I almost don't
feel bad about calling my "hey look, when I touch the end of my homemade
Tesla coil, I fly across the basement" a neat-o hack.


   Well, fine.  Since opinion is turning against me, I won't post anymore.
I still think the majority of folx in this group are lame...  What makes
you all so awesome?  _I_ certainly haven't figured it out, and I'll stack
my "hackitude" against any one of my flamerz any day of the weeks.

   Seeya.

  (To the dudes who are on my side...  sorry, but I don't have time for this,
I'm sure people will be happy to here that in this group.)



-- 
David L. Newton	    |  Work: (708) 467-1015  | newton@ils.nwu.edu -or- 
ILS, Room 135       |  Home: (708) 332-2321  | dnewton@carroll1.cc.edu, but
1890 Maple St.      |------------------------| this just is forwarded to the
Evanston, IL  60201 |__Dr. Seuss is a god.___| top address, so don't bother.

daveh@ccwf.cc.utexas.edu (David H. Huang) (02/20/91)

In article <9102200204.AA05525@aristotle.ils.nwu.edu> newton@ARISTOTLE.ILS.NWU.EDU (David Newton) writes:
>   "can't"...  I hardly think this is a matter of ability, but choice of
>focus.  If you can figure out, chances are a billion to one for that I could
>too.

Yes, posting to this group (without using rutgers) is very easy to do
if you want to take the time to figure it out. If you're observant, it
should only take a few minutes to figure it out...

>#2
>   Hmm, I've been flamed a couple times for not posting the ObHack, even though
>I've already explained why.  So.
>   ObHack: Dropping down from the ceiling at IIT into a room with a bunch of
>people in uniforms and pulsing lasers (the people didn't have the lasers,
>silly, they were on a table (the lasers, not the people)).

So. Exactly how is that a hack?

[ other things that are probably hacks deleted ]

>From Leo Bicknell:
>> [paper clip hack]
>
>   We're getting ridiculous here, if this is a "hack"...  I almost don't
>feel bad about calling my "hey look, when I touch the end of my homemade
>Tesla coil, I fly across the basement" a neat-o hack.

I don't consider the paper clip thing as a hack either. It sounds more
like resourcefulness.

>-- 
>David L. Newton	    |  Work: (708) 467-1015  | newton@ils.nwu.edu -or- 
>ILS, Room 135       |  Home: (708) 332-2321  | dnewton@carroll1.cc.edu, but
>1890 Maple St.      |------------------------| this just is forwarded to the
>Evanston, IL  60201 |__Dr. Seuss is a god.___| top address, so don't bother.


-- 
David Huang                                 |
Internet: daveh@ccwf.cc.utexas.edu          | "Slight accidents with funny rays
UUCP: ...!ut-emx!ccwf.cc.utexas.edu!daveh   |   can have serious consequences"
America Online: DrWho29                     |

jb3o+@andrew.cmu.edu (Jon Allen Boone) (02/21/91)

Testing....


Can't think of an ob hack right now, sorry.... :(

apm@HPOPD.PWD.HP.COM (Andrew Merritt) (02/22/91)

What is the problem with posting to this group?

Ob. Hack: someone had done an 'rm -rf /', but managed to kill it before it
removed everything.  However, most of /dev had gone, as had /etc/mknod.
Luckily cc was still present, so I wrote a short C program to recreate the 
device file for the backup device, and then recovered the system.

Andrew