ESXi file transfer woes

SO, I recently built an ESXi server. Its nothing special, but she's got it where it counts. A comedy of errors has unfolded as I've tried to upload even a single ISO to the system. It shouldn't be this hard.

First, I tried upload images using the built-in function in vSphere. Unfortunately, VirtualBox OSE so grossly underperformed at this task that the uploads wouldn't complete, ever. For example, I began the 650MB upload of the OpenFiler virtual appliance at 2030, woke-up the next day and the session had STILL not completed. This is over my LAN, not the Internet. That's absurd!

Next, I enabled SSH and tried to use SFTP to upload. For some bizarre reason, I couldn't use the CLI sftp client, so I turned again to my VirtualBox XP install. WinSCP is a brilliant piece of code. It really is. And I suspect it would have worked marvelously if I weren't running it on the feable IP stack made available to it via VirtualBox. As it were, it couldn't maintain a session long enough to transfer even the 650MB virtual appliance for OpenFiler. :-(

At this point, I considered throwing in the towel on the whole network transfer gig and using DVD's to get my data up to the ESXi server, but that would've been too easy. SO, I enabled FTP on my ESXi server using the glorious instructions over at vm-help.com. Now, I can FTP files from my native Linux install, and its blazing fast, like it bloody should be!

The real beauty of all of this is that my foray into ESXi was prompted by my efforts to build a virtualized Hackint0sh. I had heard tell that it was possible using VMware Server, but I didn't have a whole lot of luck with that... so I used a Jedi mind-trick to convince myself that the logical choice was to build a full-out ESXi server. I think it was probably just an excuse.

Now that I'm finally able to upload to the box without serious difficulty, I know I'm not going to have the time to tackle the original Hackint0sh project because a friend sent me a pre-installed Hackint0sh! w00t!

...and this is why I'm Catholic

When I was looking for answers from the Methodist church about all the things I was wondering about as a teenager, I was dismayed to find that their official church doctrine (if you can call it that) would on one hand condemn a thing and on the other bless it. This was true of homosexuality, divorce, abortion, and more. That is what lead me to look elsewhere for spiritual direction... I sought something that was congruent, something consistent both with itself and nature.

When I looked at the Lutheran church and found it to be lacking in congruity, in very much the same way the Methodist church was. Now, the ELCA (Evangelical Lutheran Church of America) has formally acknowledged that homosexuality is not only fine, but its fine to have practicing homosexuals as clergy. This view is inconsistent with Scriputre, Tradition and Nature.

And this is why I'm Catholic -- because there is nothing in the Catholic Church that is in conflict with Scripture, Tradition or Nature.

Pulse Audio == Pure Fail

I don't know what future gains Canonical hopes to see from deploying Pulse Audio in Ubuntu, but I'll tell you this much: I've removed it and won't re-install it until every comment I see about it is positive. Pulse has been nothing but a pure pain in the ass for the last week. Finally, today, I removed every pulse-related package from my system and switched back to ALSA. `apt-get remove pulseaudio*` DO IT!

And what's more, lets write to Canonical and tell them that Pulse Audio is garbage.