Saturday, August 8, 2009

TextMate

Just discovered another great TextMate feature. TODO. Type TODO and add your todo thought, and then you can go to Bundles->ToDo-> Show TODO list and it will consolidate all of the TODOS into a single list regardless where they are in your project. This feature is great for when you're coding, have a concept of something you'd like to add or possibly review or change, but don't currently have the time to do so. Great way to stay more organized and on top of things.

Thursday, May 21, 2009

Putback


I was flipping through my c++ book today, a book I haven't really used since my freshmen year, and discovered a very useful function, putback(char) . When reading in a stream of characters it allows you to put a character back into the stream, could be very useful for certain parsing needs.
-- Post From My iPhone

Sunday, April 19, 2009

Bison

Learning about compilers, I'm finding Bison & flex very interesting. The setup is a bit cryptic at first, but I'm starting to really appreciate the power and simplicity of Bison and lalr(1).


-- Post From My iPhone

Thursday, February 26, 2009

airport extreme basestation and Fedora 10

I'm impressed, on the first try I was able to get my hp psc 750 printer (that is connected to my airport extreme basestation) to work with Fedora 10. All I had to do was (in Fedora) go to printer setup, choose the category "AppSocket/HP JetDirect", I entered in the IP of the airport which for me was 10.0.1.1, the next step asked me for what type of printer, and it was done! Tried to print out a page and it worked perfectly. I was expecting this to be a freagin 10 hour project.

Wednesday, February 11, 2009

Fedora 10 & Radeon x3870x2

Hurrah!! For crappy drivers. I've been using Fedora 10 for some time now, just upgraded to the new ati drivers( ATI Catalyst™ 9.1 Proprietary Linux x86 Display Driver) and now there is an attractive water mark on the bottom right hand of my screen, overlapping everything else. The watermark reads "AMD Unsupported hardware", I reviewed ati's knowledge base, and it indicated that either my hardware was truelly not supported, or I was missing a "control" or "signature" file from /etc/ati. Both files are present on my install, and I chose the ati drivers under the 3xxx model series. So either it wasn't tested with the 3870 x2 or there is something else wrong with the new driver release. Either way I downgraded to the previous 8.12 release, and now the watermark is no more. On a side note, I'm actually very much pleased with the ati catalyst driver installation process now, before you had to turn off x-server before you could install them, now it's a simple gui window, with just a restart required.

Thursday, January 8, 2009

Getting wireless working in Fedora 10

My desktop has a Linksys wireless usb N adapter. After installing Fedora 10 I have having extreme difficulty using the network manager to connect to my wireless network. The alternative was to turn off network manager and use wpa_supplicant. To do this I hade to go through a few steps. First make sure that your wireless adpater is set up correctly with ndiswrapper there are a ton of guides out there for how to do this. If you have my adapter make sure you are using 32 bit Fedora 10, as they're currently aren't any 64 bit driver options. Second you'll need to setup a config file for wpa_supplicant. The config file is usually under something like /etc/wpa_supplicant/wpa_supplicant.conf. My file looks like this

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid="network1"
scan_ssid=1
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="somepassword"
}


The password will be encrypted to do get the encrypted form of your password, you'll need to run a "wpa_passphrase + your network name + your network password". Then copy and pass the encytped passphrase into the .conf file. Now you should be ready to connect to your network. There are two commands neccesary to complete this. The first command to run is

wpa_supplicant -d -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf

The command to run next is

dhclient wlan0

It was wlan0 for me, but that will be the name of whatever your adpater is recognized as. The first command will cause the adapter to connect to the router. The dhclient command will actually retrive an i.p address from the router. Sometimes it takes a few minutes after running the dhclient command for anything to happen. I hope this helps. Also you will probably want to create a startup script for these two commands, so that your computer connects upon startup. Otherwise you'll have to run these manually each time.