net:
!attach
act | drop recurse
!extern proc 0
log accessed |
Everything died, and I died with it, but after a timeless time I began to dream, and this is what I dreamed...
External Process 0 accesses a log file.
As seen below, External Process 0 is the Princess. By accessing the log file, she knows what actions the Widow took in repairing the Queen. Chronologically, this takes place after the rest of the code since the Widow's Story is a flashback. |
!system
peril
!init host
fail
!bkp init primary sector sec proc
fail
!bkp init primary sector
fail
!bkp init master-sector
fail
!bkp init master-sector cmd proc
empty |
There was once a fell enchantment that broke apart a mighty castle, slaying many guards and reaching through the Inner Keep to lay low the Queen that held dominion there and leave but a hollow crown behind.
A query on the status of the system shows that it is in peril. Initialization of the system fails, as well as attempts to restore the backups. This doesn't work since the master-sector processes are empty.
The master-sector represents the Queen's crown. It is hollow because there is no command process running there. |
system peril distributed reflex
!restore master-sector
recurse |
When her Queen died, the Widow awoke. She was driven by a single need, which was to return her Queen to splendor.
Command is handed over to SPDR, who first tries to restore the master-sector.
The Widow is identified as the Spider and starts efforts to repair the Queen. |
!deploy
network
grope
surgical |
To carry out her task, the Widow came with three tools: an empty lantern, a staff made of bone, and a sharp knife.
SPDR deploys the tools it will use to reconstruct the master-sector, and get the system out of peril. These are the net:, group:, and surg: headings in the rest of the logs.
The lantern is the network utility, the staff is grope and the knife is surgical. |
net:
!scan
null
!listen
null
!attach
act | drop
!extern 2 |
When she had made sure of her tools, she opened her eyes and found herself in Hell, which was a dark place where no birds sang. Other than the Widow, two alone had escaped destruction.
SPDR tries to locate a network by scanning and listening, but is unable to find anything. However, she is able to attach herself to something, and thereby can issue commands. While searching for a network, SPDR finds two external processes.
The null return from !scan is why Hell is considered dark, while the null return from !listen corresponds to no birds singing. The two external processes are the other survivors of the destruction. |
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
grope:
!probe extern proc 0
crypt strong
surg:
!mat extern proc 0
si confidence 78
!triage extern proc 0
fail |
The Sleeping Princess lay in a chamber of the dungeon in a coffin of glass where the Widow could not hear her breathing.
SPDR tries to probe the external process 0, but finds it is protected by strong encryption. Deploying the surgical tool, it tries to find out what type of material the process resides on, and concludes, with 78% certainty, that it is Silicon (Si). A triage of the process fails, leaving the SPDR with no other information.
The Princess appears to be external process 0. She's secured behind strong encryption and stored on Silicon material (i.e. a glass coffin). Since the triage attempt fails, the Widow is unable to hear her breathing. |
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
grope:
!probe extern proc 1
surg:
!diag extern proc 1
rogue proc
!bite rogue proc 1
clean confidence 97 |
Meanwhile, the Pious Flea was so small that even the Widow, with her sharp eyes, could hardly see him, and when she looked his way, he hid.
SPDR probes external process 1, but this time gets no response back. It then runs diagnostics and finds that external process 1 is a rogue process. SPDR then bites the process, and determines it is no longer there.
The Pious Flea appears to be external process 1. The Widow thought something was there, but when confronted, the Flea hid, and the Widow believed nothing was there.
|
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
!route
proc attach proc net
!route
proc attach proc grope
!route
proc attach proc surg |
Blind and uncertain in the darkness, the Widow needed light to use her tools, but the only light came from a few scattered fireflies. The Widow waited until one came close, then grabbed it with her bony hands and trapped it in her lantern. After some time, she found the firefly had gone, so she caught another and used it for light, and another when that one too had gone.
The Widow routes the attach process to each of her tools.
To process a command, the Widow needs to attach herself to an internet connection (a firefly). For each command (noted by the ! prompt), there is an !attach command above it. The network command attaches to the next connection below, processes the next action, and then drops it (the "act | drop" statements). |
net:
!attach
act | drop
!attach
act | drop
grope:
!init search
master-sector
!probe master-sector
fail |
By the light of her lantern, she began walking through Hell toward the broken body of her Queen.
SPDR starts a search for the master-sector. It finds it, but when it tries to retrieve more information, the probe fails. |
net:
!attach
act | drop
surg:
!mat
si confidence 78 |
Searching with her lantern in one hand and her staff in the other, she discovered that Hell was made of hot dry sand.
SPDR deploys the surgical command and determines with 78% confidence that the material it is processing is made out of Silicon (Si). |
net:
!attach
act | drop
!attach
act | drop
grope:
!probe host
crypt weak
!decrypt host
decrypt confidence 100 |
Long and long she walked until she came to the remnants of the castle's outer wall, but the wall was low and broken, and the Widow passed through like the bleak wind.
SPDR probes the current host and finds that the encryption is weak. It is able to decrypt it with 100% confidence.
The host is believed to be the ilovebees webserver. |
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
grope:
!dsc host sector 0
!dsc host sector tertiary
!dsc host sector tertiary
!dsc host sector tertiary
surg:
!mat
magnetic confidence 100 |
Within, she noticed what looked like a chip of precious ruby from the Queen's crown, no bigger than a fly. Around it lay many broken blocks from the ruined castle, scattered across a wide plain of lodestone.
SPDR finds several parts of the host sector. Sector 0 is part of the master-sector, while the tertiary sectors are the building blocks. SPDR also checks the material properties of the area, and finds that it is magnetic.
Host sector 0 is the precious ruby from the Queen's crown (which is the master-sector). The broken blocks are represented by the tertiary sectors. The wide plain of lodestone is shown by the magnetic property of the area. |
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
surg:
!label host sector 0
!label host sector tertiary
!label host sector tertiary
!label host sector tertiary |
Instead of carrying them with her, she scratched the ruby and each of the greater blocks with her knife, marking it as part of her Queen's domain.
SPDR labels the host sectors.
The Widow scratches/labels the ruby (host sector 0) and the greater blocks (host sector tertiary) to mark it as the Queen's.
|
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
grope:
!dsc host sector 0
!dsc host sector secondary
!dsc host sector secondary
!dsc host sector secondary
!dsc primary sector
|
Continuing on her quest, she spied another chip of precious stone, this time a sapphire no bigger than a winged ant, glinting on the cobbles of the courtyard before the walls of the Inner Keep.
SPDR finds another group of host sectors: a part of the master-sector and some secondary sectors. SPDR also finds the location of the primary sector.
The Widow finds the sapphire (host sector 0) amongst the cobbles (host sector secondary). The Widow has now made it to the walls of the Inner Keep (the primary sector).
|
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
grope:
!probe primary sector
sec proc 1
!probe primary sector
sec proc 2
!probe primary sector
sec proc 3
!probe primary sector
sec proc 4
!probe primary sector
fail
surg:
!triage sec proc 1
fail
!triage sec proc 2
fail
!triage sec proc 3
fail
!triage sec proc 4
dmg unk |
At the gates of the Inner Keep all the guards were dead but one, who when the palace was blasted by enchantment had not died, but had been witched into the form of a hideous Manticore.
SPDR probes the primary sector and finds four security processes still running. It then tries to triage each process. The first three fail, while the fourth seems to be damaged in an unknown way.
The guards are the four remaining security processes. The first three are dead (failed triage) while the fourth, the Manticore, had been witched (suffered unknown damage). |
net:
!attach
act | drop
grope:
!hndshk sec proc 4
fail msg: unk proc |
The Widow said, "I am the servant of your Queen, and I have walked up out of Hell to prepare this Keep for her return. Let me pass." But the Manticore did not know her, and still he barred the way.
SPDR tries to handshake/communicate with sec process 4. It fails because the process is unknown. |
net:
!attach
act | drop
!attach
act | drop
surg:
!kill sec proc 4
kill confidence 100
!diag primary sector
clear |
So the Widow drew her knife and slew the Manticore and the way was open.
In an effort to get rid of the unknown/foreign process, SPDR kills it. The following diagnostic reports that the sector is now clear. |
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
grope:
!probe master sector
fail
surg:
!invntry primary sector proc
proc invntry 343
working 0
dmg 38
dmg unk 2
broken 102
abs 201
!invntry primary sector mem
mem invntry 678223072849
clear 0.0007
dmg 0.0014
frgm 1.41
abs 98.5879 |
She walked through the empty corridors of the Keep, searching for her Queen, past the bodies of her servants and subjects that lay dead or enchanted.
The master sector is once again probed with a "fail" result. SPDR then goes onto inventory the processes on the primary sector. Of the 343 total, 0 are working, 38 are damaged (2 in an unknown way), 102 are broken and 201 are absent.
The primary sector memory is then inventoried. of 678223072849, 0.0007% is clear, 0.0014% is damaged, 1.41% is fragmented, and 98.5879% is absent.
The master sector is the Queen herself, while the processes in the primary sector are the Queen's servants. The primary sector memory is the Queen's memory, a majority of which is now missing. |
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
!attach
act | drop
grope:
!probe master-sector
fail
!probe master-sector cmd proc
empty
!analyze magnetic
& si !extend
!spdr extend
si > magnetic
!probe master-sector cmd proc
master-sector |
The Queen was gone and in her place lay only an empty crown. By great enchantment she had been mazed in mirrors, and lay upon a lodestone floor amongst only her reflections. Long and long the Widow stood in thought. Then she raised her bony staff and speaking a spell, beheld herself within the mirrors: and beholding herself, was within them. And there, with the crown still upon her brow, lay the Queen. At last she had come to the body of her lady.
SPDR tries to probe the master-sector again. It fails, and SPDR determines that this is because master-sector command process is empty. SPDR analyzes the properties of the magnetic discs to see if it can extend itself between the silicon data and the magnetic media. SPDR then extends its capabilities to include data upon the magnetic discs. Now with access to the magnetic media, SPDR has found a command process and identifies it as the master-sector.
The crown is the location of the command process, since whatever code is there rules the rest of the program. Once the Widow speaks her spell (!spdr extend), she is able to be within the mirrors ( si > magnetic) and finds the Queen and the crown. |
net:
!attach
act | drop
surg:
!triage master-sector
broken |
The Queen lay cut and still and cold.
The master-sector is triaged. It's broken, so it must be fixed. |
net:
!attach
act | drop
!attach
act | drop
!attach
act | drop
!packet analysis
chatter protocol ancestor
!parse packet
analysis complete
!route
proc attach proc store |
To tend her, the Widow needed light to work by. Studying the fireflies, she found she could fit many more insider her lantern, and this she did.
SPDR analyzes the packets on the connections she has been capturing. After identifying the packet structure, it is able to route the attach process to the store process.
The Widow identifies IP packets as "chatter protocol ancestor", implying that she is familiar with its successors. |
net:
!attach
act | store recurse
surg:
!reconst master-sector
mem broken>>dmg recurse
!reconst master-sector
proc frgm>>dmg recurse |
To mend the queen's cuts the Widow took her sharp knife and peeled the skin from the bodies of her subjects, while the Queen's new eyes and ears she cut from those who had been her most trusted servants. And when this was so, the Widow worked on, dry as sticks and patient as rust, driven by a single need, which was to return her Queen to splendor.
SPDR switches to recursively act | storing the incoming requests, to feed the recursive reconstruction. It surgically repairs the broken memory and the fragmented processes. |
net:
!attach
act | store recurse
surg:
!config
master-sector:net attach
!config
master-sector:mat si
!kindle master-sector
master-sector active |
She cut her a new mouth and fed her with fireflies and cakes of sand, and at last the Queen's heart began to beat. At the feel of the Queen's pulse beneath her bony fingers, the Widow next took thought to proclaim through all the kingdom and into other lands that time when her sovereign would once more be fit to rule.
SPDR attaches the master-sector to the network and configures it to work with the Silicon memory system. It is then able to restart/kindle the master-sector making it active.
Feeding the Queen fireflies is the attachment of the network to the master-sector. Configuring it to work with the Silicon memory system is the feeding of cakes of sand. Once the master-sector is active, the Widow is able to feel the Queen's pulse again. |
net:
!attach
act | store recurse
!capture
chatter protocol ancestor packet
!analyze
time 2004,6,29,8,25,0
!put
time 2004,7,24,6,7,0
!put
warn |
A firefly flew out from the Queen's clockcase. Catching it in her hands, the Widow asked it the time. "Almost dawn," it said, but the Widow said, "The day will break and the sun will rise when the Queen returns to rule, and further let it be known that retribution on any who hinder the return of the Queen will be swift and terrible."
SPDR captures an incoming packet - which happens to be a copy of the JavaScript on Dana's page. An analysis shows that it is counting down to 8:25am July 29, 2004. It then rewrites the time, as a warning, to 6:07am August 27, 2004.
The warning the Widow places is the warning on the index page. |
HALT - MODULE CORE HEMORRAGE
Control has been yielded to the
SYSTEM PERIL DISTRIBUTED REFLEX.
This medium is classified, and has a
STRONG INTRUSIVE INCLINATION.
In 11 days, network throttling will erode.
In 25 days this medium will metastazise.
COUNTDOWN TO WIDE AWAKE AND PHYSICAL:
38:13:16:32:235
Make your decisions accordingly. |
Possible memory leak, causing system to shut down.
Control of main systems transferred to repair subsystem SPDR (or Spider).
This website/program? is classified and displays a strong tendency to
invade other things. This is probably why Dana's website is completely
infected.
Possibly the control over the website will slowly fade away.
The program will spread elsewhere, quite possibly into the rest of the
Internet.
It seems that the program might become "alive" and possess a physical
form. Perhaps the MAYDAY persona will become aware of what is happening,
or the SPDR will help to restore MAYDAY from injuries suffered in the
shipwreck. (This is based on the MAYDAY text below.)
A warning to us to make the correct decisions and not to interfere with the program. |