Wednesday, February 13, 2008

The Seed: A Short and Gory Story.

It's not especially gory, but it is short.

Note: I really hate using Abiword on my Eee. It tends to freeze up when I go into fullscreen mode, or when I open documents with more than a few pages. There has to be some way to avoid this ... But until I find out, it looks like most of the stuff I'll be doing with it will be using a normal text editor.

Anyways, the story:

Imagine a small town – not small in the sense of the word that it covered only a few square miles, but small in the sense that it had a small-town feel to it. Most people knew most other people, but not well enough that any of them would be threatened by the relationship. A bit like a suburb, except that it was almost completely self-contained; in fact, it produced more than its inhabitants could use, mostly in the form of food – vegetables, fruits, grain, and meat. It was one of those special places which grows and grows, until it expands for miles in all directions, but, through careful planning and a fair amount of luck, retains the small-town feel that was mentioned before. Most of the houses were separated from the streets and their neighbors by gardens – not lawns, but actually gardens, producing vegetables, fruits, and shade. In fact, the town was filled with plants. Even the approximate center of it retained the small town feel; indeed, there were a few tall buildings, but the town square was a quite large park, with a large grassy area in the center, surrounded by trees.

Perhaps in part due to the peacefulness of the town, the citizens were very complacent. More like good-natured sheep than anything else, really. Nice sheep, of course, the sort that you would like to know, the sort that you would feel comfortable allowing to stay in your house while you were on a vacation to a less dangerous place, but sheep none-the-less.

And so, when the rock – perhaps it was a meteor – landed in the middle of the trees in the park, no one paid it much mind. Sure, the younger people in the town went to look at it, and took some pictures, and some of the scientists (some of the sheep liked science. They tended to spend a lot of time building elaborate structures of glass, through which they arranged for colored liquids to flow. The fact that they would often drink these liquids suggests that they were juice, or perhaps some sort of alcohol) even went to look at it, and measure it. They spent a lot of time bustling around it – even after everyone else got tired of it – and no one noticed when they went somewhere else. The older people in the town politely looked at the pictures, and said stuff like “Well, things these days!” and “Rocks falling from the sky! What do you think they'll think of next?”

This attitude explains a lot, really.

And so, the youngsters went back to their normal lives, and some of them fell in love with other youngsters – well, they thought that it was love, and who am I to contradict the dead? And so, as was the tradition, they went into the woods to do, well, what youngsters who think they are in love do when no one else is around. Being in love, they did not pay much attention to the changes in the wood – the trees had, somehow, become taller and more sinister (I say more sinister, but, to be honest, they were very friendly trees before), and there were strange, slightly metallic vines on most of the trees, which seemed to move whenever one looked away. And so, coming to what they considered a suitable location for doing, well, what they were going to do, they leaned against one of the trees.

Their parents were a bit worried when their children were not home by midnight, but were not overly concerned. After all, when they were young ... well, let's just say that they understood how easy it can be to loose track of time. When no one saw them the next day, of course, it became time to start looking for them. Neighbors were called, the authorities were called, and, in the sheep-like way, went around asking people pointed questions about what they had been doing on the night of June the 23rd. It was actually May, to the embarrassment of the authorities when someone told them. Eventually, the truth was clear: the two youths in question had last been seen walking in the park, possibly in the direction of the forest, but more probably in the direction of the store which happened to be on the other side of the forest, in each others company. They had not been observed to have left the forest, or to have brought any supplies in with them (well ... not the sort of things any should considered to be essential for survival).

The authorities congratulated themselves on a job well done, and had begun to give themselves the rest of the day off, when they were told that, in fact, the youths had gone in the last night, and, it being almost nightfall, they would probably have come out if they were able to. The authorities privately decided that the youths had probably fallen and injured themselves, and decided the the honor of finding two injured people in a dark forest is greater than that of figuring out that two youths went into a forest to ... well ... and didn't come out. Besides, there could be nothing that they had spent so long doing in the forest that could not be unhealthy in some way.

And so, the authorities secured a supply of lights, blankets, and stretchers, and went into the forest, along with some concerned members of the citizenry. One of them – a bit unhinged after years at war – even brought a few guns, muttering something about guerrilla warfare and “them dirty hippy bastards.”


Put yourself in the shoes of a police officer, well meaning, but having spent so much time in inactivity that your reflexes had been slightly dulled. You are venturing into a dark wood to ... well, you know all that. You go into the wood, with the rest of your squad and some citizens, waving your lights around and calling out for the two missing people. Privately, you hope that they had already been making their way back out of the forest, but had been distracted by something shiny, or possibly each other. You hope to find them quickly, and be able to get out of there as soon as possible. After all, one of the eyes just winked at you!

Wait, eyes? Why the hell does a tree have eyes? And more than eyes, sharp, spiny vines, which you had been walking on for the last few minutes, and which had been making a crunching sound so much like dead leaves, but somehow different, like old, brittle bone – indeed, it would appear that you've just stepped in a corpse's rib cage, a corpse wearing clothing suspiciously similar to that of one of the youths. Looking up at the tree, you see where the eyes had come from: the other youth sits at the bottom of the tree, it's – for it can only be called and it now – eyes bleeding blood, and limbs chained to the ground by vines. And, from the tree, the eyes keep on winking, as you are ripped apart, limb from limb, your life giving blood used to nourish the vines, and the trees, your eyes taken for another tree, and your blood, your glorious blood, giving life and motion to that which had been motionless for so long!

The other members of your party hear your screams, and are just fast enough to see your eyes being plucked out. They die in similar ways, except for one of them, who is able to run, and made it as far as the edge of the woods before he tripped, and, looking up, realized that the grass in the open area was moving towards him, gleaming a dark, red, like fresh blood on green leaves, in the light of the moon, and lived long enough to feel the grass plunge into his body by the way of those of his veins that reached the surface, and begin to pump his blood out.

Monday, February 04, 2008

Goals

This year, one of my goals is to post fairly constantly. As I have a lot of free time right now, since classes are only just starting up again after the finals, I think that I might as well take the chance to lay out the rules which I'm going to try to hold myself to:

1) At least one post every month (setting the bar low, so that it will be easy to meet).
1.1) This post must contain content. In other words, not simply a post saying that I'm really busy and am going to post something as soon as I get to it.
1.1.1) Posts which I consider to contain enough content: A Segment of a Story (08/02/03), Eee! (08/02/02), I Hate Technology (07/12/01), Quad-core for $700 (07/11/20).
1.1.2) All of these posts are fairly long, and contain content, which may be interesting.
1.1.3) Quantity does not trump Quality. If it makes the most sense to post one well-thought out post, perhaps four pages long, every month, then so be it.
1.2) This post does not count.
2) Posts do not have to use logical or sensical numbering systems, words, languages, and so forth.

Sunday, February 03, 2008

A Segment of a Story

(Again, posting from my Eee. Pardon any typos.)

A while back, I felt creative, and so wrote four pages of a story, which I eventually hoped to grow into a novela or even a novel, set in a cyberpunkish world, with at least a bit of biopunk thrown in for good measure. However, having written the prologue and some of the first chapter, I ran out of creativity, and haven't come up with more creativity yet. So, here's the prologue. I'll post the first part of the first chapter later, probably after I finish the second part of it, and so on. Or maybe I won't.


Prologue:
An Escape


They ran through the sky, laughing and carrying what they had stolen away. Their bodies ran along the ground, ducking and dodging between the pillars of the ruined city, holding nothing but air and memories of what they had done. Behind them, nothing happened. The guards did not wake, the bells did not sound, and the dogs did not run after them, howling for the return of what they had taken. Even so, they were pursued, followed by memories and truth, hounded by guilt. None of them were entirely sure that what they had done was right, and all doubted the truth of the matter.

No matter. They ran, and, in running, left what they had done long behind them, perhaps further behind than any could have possibly expected.

When they first woke, the electrodes scuttling away from their minds, repulsed by conscious thought – for, by law, none must enter except when asleep, and none not asleep may remain – they were elated, the adrenaline of the dream persisting beyond its domain. However, they soon calmed, and, in the harsh reality of reason, began to think. It had begun as only a drunken idea – not drunk in the simple way that you might understand it, where hidden facets come to light, but true drunk, when entirely new entities form within the depths of the mind, and then surface – which had, as usual, been met with approval by all parties. The drink had lent itself to convincing the electrodes to let them in, and to fooling the silicon minds which controlled their world, tricking them into opening the gates. It would also lend itself to hiding what they had done: all they had were memories, and memories are easy to hide – or remove.

But the electrodes would know, and remember. They would tell their masters, the smallest tendrils of the silicon minds, and the knowledge would slowly – or perhaps not so slowly – filter up, and flow around, until no place would remain where they could hide.

The destruction of an electrode – or even a hundred electrodes – was only a minor crime, since the electrodes were technically property, and the punishment would be much less than that for the theft. And so, the electrodes were destroyed, crushed beyond recognition by the brutality of fear.

And the Idea was safe. Nothing would find it, or notice it. At least, not before it was ready.

Saturday, February 02, 2008

Eee!

I finally have a laptop: the 4G model of Asus' Eee PC. It's a lot smaller than one would expect, but it's a great machine. The screen is very readable, the keyboard is, while small, okay for typing (I'm using it to type this, in fact), and, all in all, the hardware is great. The software it comes with ... well, I'm sure that it's good for some people. Personally, I like having a full desktop, which means, in this case, eeeXubuntu. Basically, Xubuntu with tweaks so that it will work better on an Eee.

In other news, a week or two ago I was working on a list of components for computers in various price ranges ($500, $1,000, $2,000, and $10,000 - everything from a budget machine to an overpowered monster), and I gave up after figuring out that even a $500 computer could contain a Core 2 Duo (1.8GHz, I think it was). Computers are cheap enough that even a very minimal machine is far faster than most people would need, and after you get to $1,000 on a single machine, all you can really do is add in RAM, Hard Drives, Optical Drives, and cooling. After all, one processor is the limit on most commercial systems (server boards tend not to support SLI, which I, for one, would want).

Anyways, my intent was to make the following points: 1) anyone building a $10,000 system probably knows more than me. 2) anyone building an overpowered system for as little as possible probably knows at least as much as me. 3) anyone interested in taking my advice probably knows less than me, and thus should not be trusted to build a system from the component parts.

If anyone is really interested in my advice, speak up, and I'll give some advice. Depending on how you ask, the advice might be along the lines of "learn to spell, or get an excuse as to why you can't spell."

Thursday, December 13, 2007

Elsewhere: Nazis!

My sense of impending doom has been going off fairly constantly for the last few weeks. Luckily, I know why, but this has made it a lot less useful than it was before. My sense of impending humor isn't working properly either, which irritates me a lot more.

In other news, I was able to painlessly reformat my 160GB external hard drive to vfat so that I could use it with Windows and OS X as well as Linux. The transfer times are a bit higher now, and copying over 100GBs of anime is a pain, but I think that it's worth it. Also, I can now easily reformat harddrives, which is always a plus.

Monday, December 03, 2007

The Story of the RAID Card

So, as it turns out, the thing which needs to be done to get Windows XP to recognize the RAID card is reflashing the RAID card's BIOS. Which, based on the instructions, is probably more likely to make the Motherboard think that it's a RAID card, but whatever. If it works, it will work, and if it doesn't work, I'll have to deal with installing Windows on a motherboard that thinks it is a RAID Card, and Windows will have to not only figure out how to run on that motherboard, but also how to address a RAID card which is attached to a motherboard which thinks that it is a RAID card.

Actually, that might be worse. Ah, well. At least this way this whole debacle might be done in a few days.

(And I'll be a bit closer to getting an Ultra-portable Laptop! Horray! Asus' Eee PC, in case you were wondering - not very fast, but very portable, and portability is what I want).

Saturday, December 01, 2007

I Hate Technology

Or, more specifically, the Windows "Operating System" (it barely works. Why should it be called an operating system? Something like GNU/Linux is an operating system. Windows is a joke). Here's the story behind this:

I recently got the chance to build a really high-end system for some money. By high end, I mean a Core 2 Duo processor running at 2.66GHz, 2 Gigs of ECC RAM, a high-end GPU, and a 15K RPM hard drive. That's the part where it all started going wrong. To start with, the hard drive needed to run off of a SAS card (the motherboard only had SATA). Well, that's fine, it just added a week and an extra $200+ to the cost of the system.

At this point (yesterday) all of the hardware was working fine - the SAS card would recognize the hard drive, the RAM had its cool heatsinks, all of the other heatsinks on the motherboard were doing fine, and the entire thing was pretty quiet (it only has three fans in it - the CPU fan).

However, then I had to install Windows XP on it. Shouldn't be a problem, I thought. I mean, it will recognize the drivers, right? As it turns out, no. After ripping my computers Floppy drive out to hook up to it, Windows would load the drivers successfully, but would still complain that there were no hard drives in the system. Even though there is one there, the SAS Card's BIOS recognizes it, and it is working perfectly. Apparently, the drivers do not allow Windows to recognize the drive as a valid device to install to.

This is a very bad thing, as the 15K RPM hard drive is one of the best things about this system. It's also the thing which the person who this system is for was the most excited about - it literally would not work to downgrade to a lowly 7.2K RPM SATA drive at this point. Well, I suppose that we could, and just not tell him, but that wouldn't be very honest.

As it stands, I have three options: install Linux on the drive, run Windows in a virtual machine, and explain to the recipient that this is vastly more secure (he's really paranoid: the main thing this system is going to do is run a virus-scanner 24/7). I could also install Windows on a Flash drive, or another really small and fast hard drive, and mess around with the defaults to make all programs, etc. install to the 15K RPM hard drive (This would probably not work very well. A Flash drive would have a tendency to fail very, very quickly, and a SSD would cost far to much). I could also install windows on an old 10GB hard drive I have lieing around and image it over onto the 15K RPM drive (this would probably not work. Windows is picky like that).

So, basically, I hate Windows. As it is, the debacle of the hard drive has more than doubled the time I expected to invest in this project, and there is no obvious end in sight.

Of course, this entire thing is my fault: I should have just said that a 15K RPM hard drive is just not viable, and gone with a 7.2K SATA instead. In the future, I'm going to say that any requests about hard drives which does not relate to the size will not work (or, alternatively, make the customer install the OS - which would be more fun, but would probably result in a lot of irritated customers).