Pages

Monday, January 30, 2012

Birth of a Geek, Part 1











I will always look back on my days as a fledgling computer geek with great fondness. I had clearly marked a line in the sand that represented the absolute limit of my comfort zone at the time, and then dared myself to cross it, unabashed, full of confidence. I wanted to be elite; to be a true computer geek. Sure, I had spent a few months experimenting with an old Compaq Deskpro En business desktop that had been given to me by a close friend. I cut my teeth on that thing, really. I learned how to upgrade my RAM from 64MB to 128 MB; I installed a discrete PCI-based graphics card (the machine had no AGP slot); and I learned everything I could about Windows 2000 Professional simply by tinkering, experimenting, and often breaking it to the point that I had to reinstall and start from scratch. I had a master plan, though, and it began with the research and planning toward building my own computer. To me, at the time, that was the initiation ceremony. In my own mind I could not possibly consider myself to be a true computer geek if I had not built my own rig from my own carefully drawn blueprints.

I began with a copy of the current issue of Maximum PC, back in 2002. That issue was the Holy Grail for me at the time, because the main article was a complete guide to building your own rig, including recommended parts and practices. I planned for weeks. A few months, actually. Cash was tight so instead of going all out for a top-of-the-line case, I went with a simple beige box. I cared little for aesthetics at that time. All that mattered was having my own computer that I had built myself. The one area where I did splurge, however, was in CPU and RAM.

I clearly remember the day when I made the drive to Addison to a "hobbyists" computer parts store where I made my first purchase for the rig: an AMD CPU. It was a Thunderbird 1.1 GHz chip and I put that thing through its paces over the following couple of years. For RAM I went with 256 MB of either Corsair or Kingston (I can't honestly remember, now, it's been so long since then), which was a respectable amount of memory at the time. Hard drive was a Western Digital 40GB drive and I used a 17" Dell CRT monitor that was given to me by a dear friend at work. And, of course, the only operating system I could conceive of using at the time was Windows 2000 Professional, although a few months later I managed to get my hands on a pirated copy of Windows XP.

I'll never forget assembling and testing that computer from those parts. I was on Cloud 9 and I had such an amazing sense of accomplishment. I went on to later add a discrete graphics card and other small, incremental upgrades as necessary. That rig carried me through the "Golden Age" of gaming, as I often refer to it. Others may know it as the time of the Quake 3 engine's reign over the world of computer games. I played and mastered Quake II, Quake 3 Arena, Warcraft 3, Serious Sam 1 & 2, and Neverwinter Nights with the aid of that first "Frankenstein" rig. I also continued to push my knowledge of Windows XP system administration. In fact, I learned all I could about software and operating systems. Those were the good ol' days. Even though I look back on that period with great affection, they were definitely awkward, in a way. And, I was quite aware that an evolution must take place at some point. So, it seemed quite natural to me when, in late 2003 into early 2004, I began to look longingly at Linux. And thus began a new phase in my life as a computer geek, when I pushed myself to the next level again and began an insanely fun pursuit with a very specific purpose and goal in mind.

Check back next week for Part 2 of this ongoing series!

Sunday, September 18, 2011

Custom BASH Prompt in Ubuntu 11.04


Here's a quick tip for anyone who would like to customize their BASH prompt in Terminal. First, open a Terminal session, and list the contents of your home directory, making sure to include the
'-a' option to see hidden files:

    user@hostname:~$ ls -alh


You should see a file named .bashrc. This is your BASH configuration file. Open the file using gedit:

    user@hostname:~$ gedit .bashrc


Note: If, after running 'ls -alh', you don't see a .bashrc file in the results, don't worry! You can still type 'gedit .bashrc' (without the quotes) and it will create a blank .bashrc file in which you can paste the code seen below.

Once open in gedit, scroll down to around line 39, where you should see '#force_color_prompt=yes' without the quotes. Delete the '#', thus uncommenting the line and activating it.

Next, scroll down to around line 50, where you should see a section that looks similar to this:


if [ "$color_prompt" = yes ]; then  
     # PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '  
     PS1='${debian_chroot:+($debian_chroot)}\[\033[01;31m\]\t\[\033[01;31m\] \d\n\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else    
     PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt 
     **The default bash prompt is commented out at the beginning**

As I have noted in italics above, the default BASH prompt is commented out at the beginning, just under the 'if' statement. My own custom BASH prompt is the line below that begins with 'PS1='. You can ignore the second 'PS1=', as long as you uncommented the line I mentioned above. Feel free to copy my BASH prompt and use it, if you wish. If you'd like to construct your own, I recommend taking a look at this article from IBM for reference on the various BASH prompt variables available: http://www.ibm.com/developerworks/linux/library/l-tip-prompt/

That's it! Happy customizing and please feel free to share a screenshot of your custom prompt in the comments below. 

Tuesday, September 6, 2011

Who's that!?

After over half-a-year of inactivity, I have once again reactivated this blog. Back toward the first of the year I was blessed with an opportunity of a lifetime in the form of a job as a graphic designer and web developer at a local, non-profit organization. Score!

Because I am the first ever graphic designer at this organization, I have been insanely busy getting graphics of all shapes and sizes up to speed here, in addition to getting my elbows greasy under the hood of the Moodle Course Management System. The main focus has been to launch an awesome new online school and it has been a fun, arduous, and educational journey but, by God's grace, the school launches in just a few short weeks!

Anyway, I'm ready to get back in the groove here with Socketbrain! My first order of business is two-fold: to build a strong branding and begin offering valuable and insightful content and articles. I may expand on that further in a future post, but the bottom line is that I will strive to update this blog with at least two new posts per week initially, and grow from there.

I'm excited about some of the ideas I have for this blog, as well as the direction in which I wish to go with it, and hope to get many of you involved!

If you're interested in contributing to the blog, please feel free to email me: kenreynolds78-at-gmail-dot-com.

Saturday, January 1, 2011

Geeky New Year

I've been immensely enjoying the Christmas and New Year holiday this year, mostly with family and friends. The biggest highlight was seeing "Tron: Legacy" in IMAX 3D. Awesome experience. Highly recommended! Anyway, today's post will be short, as I am still in the midst of celebrating and kicking back.

I wanted to share a website for all the hardware hackers out there. It's called Circuit Gizmos, and they can be found at the following web address: http://www.circuitgizmos.com/index.shtml Circuit Gizmos is not just about selling cool USB interfaces and motion detectors, home automation products, and electronic devices for hackers and hobbyists, however. They also have a page with some very cool projects, found here: http://www.circuitgizmos.com/wordpress/index.php

I definitely recommend this awesome site to any hardware hackers or hobbyists out there looking for cool products and projects.

Monday, December 20, 2010

Installing VirtualBox in Ubuntu Netbook Edition on an Eee PC 1000H

After being awakened much earlier than I had desired this morning, I decided to make the best of the situation and sit down to install VirtualBox in Ubuntu Netbook Edition on my Eee PC 1000H. My main reason for wanting to install VirtualBox on my netbook was simply so I could install BackTrack 4 in a virtual machine running on my netbook for the ultimate portable pentest/security monitoring setup. Of course, running VirtualBox will allow me to create VMs for anything I need going forward. The process I followed to install VirtualBox on my Eee PC is outlined in detail below.

In order to be able to install VirtualBox via my preferred method of using aptitude at the command line, I had to first add the proper repository to my /etc/apt/sources.list. For my particular installation (Ubuntu Maverick), the repository to be added is:

  deb http://download.virtualbox.org/virtualbox/debian maverick non-free

Once the repository has been added, the next step is to download and add the Oracle public key via the following command:

  ken@hostname:~$ wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -    O- | sudo apt-key add -

The above command will simply return OK if it has completed successfully.

The next step is to update the software repositories, since we added the virtualbox download repository to our sources.list file earlier:

  ken@hostname:~$ sudo aptitude update

The final step is to install VirtualBox via aptitude. One note here: I first installed virtualbox-3.2, as directed on the VirtualBox website. It installed successfully, however, when I looked for the VirtualBox application in my applications list, it was nowhere to be found. Curious, I typed 'virtualbox' at the command line and it advised that VirtualBox was not installed, but, I could install virtualbox-ose-qt if I desired. So, I followed the prompt and did just that:

  ken@hostname:~$ sudo aptitude install virtualbox-ose-qt

This successfully installed VirtualBox and there was now an application icon for VirtualBox in my applications list. Plus, I could now start VirtualBox from the command line via the 'virtualbox' command.

That's all there is to it! In my next post I'll discuss the process of creating a virtual machine in VirtualBox and installing BackTrack 4 on it for the ultimate in portable pentesting and security auditing.