Finally Purchased a Domain April 14, 2009
Posted by Michael Pobega in Uncategorized.add a comment
So, I finally got around to purchasing a domain and now I’m trying to move everything over, including my own personal website. From now on I’ll be updating here instead of at wordpress.com
My new blog is located at http://fuzzydev.org/~pobega
Developing a Python WordPress library March 2, 2009
Posted by Michael Pobega in Programming.Tags: PyPress, Python, Wordpress, XMLRPC
add a comment
As an introduction to programming I decided to divulge into a full-fledged project, instead of working on smaller programs. Considering the lack of a good Python WordPress library I decided to combine the features of two separate programs (Vimpress [http://www.vim.org/scripts/script.php?script_id=1953] and a WordPresslib [http://www.blackbirdblog.it/programmazione/progetti/28]) and XML-RPC to create a full-scale WordPress-compatible library and client for Python.
Currently I’m converting these two functional (by that I mean function based as opposed to object oriented) libraries to one complete objective library. I’m still at the beginning steps, defining classes and functions, but it’s functional to the point of being able to post! (see previous blog entry)
Eee-Control and snd_hda_intel Troubles February 3, 2009
Posted by Michael Pobega in EeePC, Linux.Tags: Debian, EeePC, Netbooks
add a comment
Ever since I bought my Eee PC 901 I’ve been trying to find a way to manually control the fan; all of the tools that worked on my Celeron-powered 900 don’t work at all on my Atom-powered 901.
After a bit of Googling I found a program called Eee-Control, which claimed that it could control the Atom’s clock and fan speed. After trying and disliking the software I removed it from my system, but then I noticed a weird problem with my speakers — they kept popping every time I initialized the sound! So after recompiling the drivers and my kernel (and completely borking 2.6.28.2) I found that the problem was a silly script that EeeControl put in /etc/modprobe.d/ setting snd_hda_intel’s power_save parameter to 1.
According to modinfo, parm: power_save:Automatic power-saving timeout (in second, 0 = disable). (int), so the script was turning off my speakers after one second of inactivity. I can only assume that the upstream author thought it was a boolean argument.
Anyway, I contacted upstream and hope to have it fixed … Even a value of 30 would be better.
Introduction; the World’s First Fully Open Netbook February 2, 2009
Posted by Michael Pobega in EeePC, Linux.Tags: Debian, EeePC, FLOSS, Linux
8 comments
The netbook market has become watered down with so many competitors trying to cash in on the new craze, including but not limited to netbooks from companies such as Asus, Acer, Dell, MSI Wind, and Sony. Finally though, one company has decided to release a fully open netbook for those of us who love open stuff. Lemote’s 8.9 inch YeeLoong netbook doesn’t look fantastic by any means, and it sports a processor barely half as powerful as it’s competitors, but it’s definitely a step in the right direction.
The information given on Lemote’s site is very limited, but from what I can tell the YeeLong netbook won’t sport internal wireless or an internal webcam or any of that jazz (though they do offer a USB wifi “extension”, whatever that means), but it will have a competitive price. If the price is cheap enough perhaps I’ll buy one just to support open hardware
Tunneling a connection through SSH February 1, 2009
Posted by Michael Pobega in Dorm Life, Linux.Tags: Debian, Linux, ssh, SUNY IT
add a comment
So I finally arrived at school, only to find that my college has decided to block IRC on the campus wifi. Weirdly enough, they allow AIM/MSN/Jabber/Skype/Ekiga/etc traffic, but not IRC. According to the IT department “IRC is commonly used to spread viruses”. I’m not sure how valid that is, but it didn’t stop me from trying to connect to my usual IRC networks.
Luckily all they did was block the common (6000~7000) IRC ports, which meant that I could still get on any networks that offered alternate ports. But for those odd servers that don’t offer any ports outside of the 6000~7000 range, there is another way to get around this block using an SSH tunnel and a program called tsocks, a program made to simplify the use of a SOCKS proxy connection. After installing tsocks find tsocks.conf and make sure everything else is commented out but:
server = 127.0.0.1
# Server type defaults to 4 so we need to specify it as 5 for this one
server_type = 5
# The port defaults to 1080 but I’ve stated it here for clarity
server_port = 1025
Now when you connect to your SSH server, you use the -D flag followed by the port in your tsocks.conf. For example, if you were using my configuration you would run ssh -D 1025 servername
Another use for this is to achieve wired connection speeds with a wireless connection – you can tunnel wget through tsocks and increase your download speed (considering your SSH server is on the local network)
Have fun and happy chatting!
