From: by403@cleveland.Freenet.Edu (Spiros Triantafyllopoulos)
Newsgroups: soc.culture.greek,soc.culture.turkish,soc.culture.europe,soc.history,talk.politics.mideast,talk.politics.soviet
Subject: The real purpose of Hasan B-) Mutlu explained in paper
Date: 8 Nov 1992 16:44:37 GMT
Organization: DRIVE-MUTLU-OFF-THE-NET, Carmel, IN (USA)
Reply-To: by403@cleveland.Freenet.Edu (Spiros Triantafyllopoulos)
NNTP-Posting-Host: hela.ins.cwru.edu


Finally!

A paper that accurately describes Hasan B-) Mutlu of AT&T, Chicago, IL
and his actions was discovered via extensive online library searches. 
In order to conserve net bandwidth I have included only the title and
abstract, along with a "Usenet Insider's" explanation of the abstract.
First person that can come up with the author wins a valuable prize.

Title:  A Hierarchical modeling of availability in distributed systems
Author: Hasan B-) Mutlu (co-author)

Abstract: 
---------

    A two level hierarchical model is proposed to analyze the
    availability of distributed systems as perceived by their users.
    At the higher level (user level), the availability of the tasks
    (processes) is analyzed in terms of availability of the system
    components. At the lower level (component level), detailed Markov
    models are developed to analyze the component availabilities.
    These models take into account hardware/software failures,
    congestion, and collisions in communication links, allocation of
    resources, and the redundancy level.

Translation by USENET insiders:
-------------------------------

The 'first level' is Mutlu / Argic / whoever is POSTING the crap and
flooding the net. The second level is the ghostwriters (KELLY, Nejat,
'Ottoman Archives', etc)

'Availability' is better defined as "a USENET feed willing and able to
put up with the crap and the volume". Failing that, an 'available
system' is a system thru posts can easily be 'forged', or a system
abused for 'free' (i.e. berkeley's gateway).

The concept of a distributed system is really one in which the same
article is posted from two or three different hosts because of a  Mutlu
/ whoever-was-posting-for-Mutlu screw-up. Who can forget the unimitable
triplicate posts of last summer? One from anadolu, one from ddsw1, one
forged thru berkeley. (Go ahead Mutlu, I got the headers saved for you
from last summer).

Users, of course, include 'sipas', 'greasy palliks', 'x-soviet jews',
'fino cultured people', '*ians', 'wieneramus-es' ('wienerami?'), and
other unfortunate entities whose only desire is to see less crap on
USENET.

Examples of distributed systems and resources include 'sarp.aic.com',
'ddsw1.mcs.com', 'anadolu.michigan.com', 'anatolia.mn.org', 
'ucbvax.berkeley.edu', and, of course, 'zuma.UUCP'.

At the common soc.culture.* reader level, the magnitude, multitude,
size, and intensity of Mutlu crap (articles, or tasks) is analyzed in
terms of availability of hosts in which to either forge articles thru or
one-way-only hosts which can be used to post anonymously.

Processes exist in order to continuously monitor all USENET trafic,
search for keywords ("Mutlu", "Argic", "Turk", "Armenia") and  prepare
appropriate responses thru a variety of automated posting and forging
systems. The various components are really databases of Mutlu quotes and
crap. Ex: "Greeks did so and so to the  Polynesian minority", "Fino
Culture", "Greasy Pallik"...

Tasks include calling 'Turkiye Consulati' and 'Kitapi Ottomani' to 
receive the latest versions of documents, keeping laborious backups, and
determining 'widest coverage' algorithms for best possible net flooding.
This would explain Jewish related material posted to 
soc.culture.australia & soc.culture.bulgaria but not soc.culture.jewish.

That is, where it really counts, at the lowest level of intelligence in
the organization, detailed 'Mutlu' models of how to BEST flood the net
are developed. These models examine the availability of 'bait material'
(anything containing any of several hundrend keywords), and, failing
that, post generic posts about the (10,000 (or 2,000, or 500, or 100))
dead people in some remote place of the world.

The models were intelligent to realize when Mutlu's C-64
(anadolu.michigan.com) crapped out, to get an account in a public access
machine (ddsw1), then when he was about to be canned from there, to
contact other fellow Turks for help with forging/posting articles thru
berkeley, and finally get a real UUNET feed (the MOTHER of all news
feeds). 

Occasionally, problems with the theoretical vs. practical aspect of the
model lead to cases where the same article is posted in 3 copies. This 
was not proven to be a major USENET load  problem (if you post 600
KB/week an extra 10 KB/week won't hurt) and was actually found to
improve Hasan B-) Mutlu's name recognition by quite a margin.

The models also take into account the 'chicken suit' factor, and post
Mutlu articles under assumed names. Redundancy levels were discussed
above so discussing them again would be redundant.

Congestion and collision in communication links, and allocation (abuse) of
(other peoples') resources are of course mainstays in Mutlu-land. What
is surprising is that the scientific basis of why this happens is now
published for the first time.

Conclusions:
------------

This paper describes with great accuracy the various high and low level
processes required to operate a Hasan B-) Mutlu. It is highly
recommended for all Hasan B-) Mutlu wannabes...

It is thusly obvious that Mutlu is there for a purpose. The purpose was
to  generate test data for his paper. 

Spiros


-- 
Spiros Triantafyllopoulos                  by403@cleveland.freenet.edu
OUZO POWER                                 [Not Really In Cleveland]
Newsgroups: soc.culture.greek