More pages converted

8 files changed, 326 insertions, 1 deletions

diff --git a/src/Android_Screen_Density.ascii b/src/Android_Screen_Density.ascii
new file mode 100644
index 0000000..2d18cc1
--- /dev/null
+++ b/src/Android_Screen_Density.ascii
@@ -0,0 +1,90 @@
+Android Screen Density
+======================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+
+== {doctitle}
+
+Recently a Droid X owner I know showed me a software that can change the screen
+density on Android phones (I can't remember if it was a part of his rom or
+not). I thought it was cool, so I set out to find a way to manually change
+screen density without installing any additional software since I try to run as
+minimalistic an install on my phone as possible (my fellow Evo users out there,
+you know why).
+
+Just before we start things off here, I'd like to put a disclaimer on this one.
+You likely won't brick your phone (you'd have to try really hard or have really
+bad luck), but you can mess it up pretty bad as we will be editing a system
+configuration file. If you cause some problems, please feel free to ask
+questions about it and I will try my best to help, but I offer no warranty or
+guarantee on this.
+
+With that out of the way, let's get started!
+
+As many things do in Android, this requires root as we will have to remount the
+/system partition.
+
+First things first, crack open your terminal emulator. If you don't have this,
+you can find it on the market, however most roms includes this application by
+default.
+
+Once in terminal emulator, run the following command: 
+
+----
+su
+----
+
+This logs your terminal session in as root(or **S**uper **U**ser so we can
+perform the various operations needed to make the change. Obviously, your
+superuser software will kick in here. Just select Allow.
+
+Now that we are logged in as root, run the following command.
+
+----
+mount -o remount,rw /system
+----
+
+This will remount the /system partition with read/write permissions.  Without
+running this command, we can't save the config file we will be editing in a
+few. The default android has for this on boot is read only permissions, as this
+partition contains some pretty critical stuff (it isn't called system for
+nothing). This is a good security measure to keep programs from changing all
+kinds of stuff on your phone. No worries however, we will only have write
+permissions set up for a few minutes.
+
+Now, open up the build properties file located at /system/build.prop I
+am assuming here that you know how to use VI. If you don't, I am in the
+process of writing up a post on using VI in Android terminal emulator.
+If you know how to use it on a desktop, VI on Android is very similar
+and you should be able to proceed as I detail later how to hit the
+escape key when you don't have one on your phone. 
+
+----
+vi /system/build.prop
+----
+
+Scroll down until you see **ro.sf.lcd_density = 160**. If you change this
+number and reboot your phone, your screen density will change on startup. I
+typically use 120.
+
+Finally, save the file and reboot. For you EVO users who don't have a qwerty
+keyboard with an escape key (who has one of those anyways), press **volume up +
+e**. I believe volume up is the terminal emulator equivalent of ctrl.
+
+Reboot phone for your changes to take effect.
+
+*WARNING (Wik)* : Don't change this value to too small or you won't be able to
+use your phone because everything will be tiny. You have been warned.
+
+*WARNING WARNING (Also Wik)* : When I discovered the build.prop file, I was
+most excited and started poking around. I noticed a lot in there that could
+cause problems for your phone. Be careful when changing the values in this
+file. It can be fun, but you might end up with an unusable phone until you
+reflash it.
+
+
+Category:Android
+
+
+// vim: set syntax=asciidoc:
diff --git a/src/Cool,_Fun,_and_Mostly_Useless_Things_to_do_with_Linux.ascii b/src/Cool,_Fun,_and_Mostly_Useless_Things_to_do_with_Linux.ascii
index 053239e..a9eb9c8 100644
--- a/src/Cool,_Fun,_and_Mostly_Useless_Things_to_do_with_Linux.ascii
+++ b/src/Cool,_Fun,_and_Mostly_Useless_Things_to_do_with_Linux.ascii
@@ -49,7 +49,10 @@ IPs unless they are explicitely requested).
   whoever else uses xmpp) using http://www.ejabberd.im/[ejabberd] or
   http://jabberd2.org/[Jabberd2] (this is the one I use)
 
-* Build a Ventrilo server using http://www.ventrilo.com/[Ventrilo] (duh)
+* Build a Ventrilo server using http://www.ventrilo.com/[Ventrilo] (duh).
+  Useful for gamers who want actual "chat room" functionality where you can
+  talk, and the room can hear you. Not super useful though as a voip
+  application.
 
 * Take webcam photos from command line using the
   http://www.firestorm.cx/fswebcam/[fswebcam] package
@@ -69,6 +72,8 @@ IPs unless they are explicitely requested).
   your music, video, and pictures to your Playstation 3, Windows computer,
   Android phone, or whatever you want that supports UPnP.
 
+* Build a mail server using http://exim.org/[Exim]
+
 
 [[linux-as-a-desktop]]
 === Linux as a Desktop
diff --git a/src/DD-WRT:Change_Root_SSH_Password.ascii b/src/DD-WRT:Change_Root_SSH_Password.ascii
new file mode 100644
index 0000000..b8cb0e8
--- /dev/null
+++ b/src/DD-WRT:Change_Root_SSH_Password.ascii
@@ -0,0 +1,35 @@
+DD-WRT:Change the Root SSH Password
+===================================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+
+== {doctitle}
+
+<obligatory-blog-intro> ... </obligatory-blog-intro>
+
+To change your root password on your DD-WRT router (assuming you already know
+what it currently is set to), log in through SSH. It turns out that DD-WRT
+doesn't use the passwd command to set user passwords like most Linux's.
+Instead, to set your password, run the following command.
+
+----
+setuserpasswd [username] [password]
+----
+
+To give an example here
+
+----
+setuserpasswd root Jimminycr1cket4tehW1n
+----
+
+This may not work on older versions of DD-WRT. I can't say because my router,
+the Buffalo Technology WHR-HP-G300N runs DD-WRT v24-sp2.
+
+
+Category:DD-WRT
+
+Category:Linux
+
+
+// vim: set syntax=asciidoc:
diff --git a/src/Default_Solaris_man_Pager.ascii b/src/Default_Solaris_man_Pager.ascii
new file mode 100644
index 0000000..ee656aa
--- /dev/null
+++ b/src/Default_Solaris_man_Pager.ascii
@@ -0,0 +1,39 @@
+Default Solaris Man Pager
+=========================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+
+== {doctitle}
+
+The title of this should actually say "Default Solaris man Pager Sucks" but in
+the interest of professionalism, I left that last word out.
+
+The Solaris default pager for man pages is "more". It unfortunately doesn't
+support the friendly controls of "less", search highlighting, scrolling one
+line at a time, etc. This is less functional than using "less" for your pager.
+With that, let's have a look at how we fix this.
+
+If you would like to change it,  you need to crack open your *.bashrc* and add
+the following line... 
+
+----
+export PAGER="less"
+----
+
+Tada!
+
+Launch bash and look up a man page.
+
+As a friend of mine said in regards to this, "LESS is more than MORE."
+
+
+One closing notes. This seems to be a very universal variable, so this should
+also work with csh, ksh, sh, etc, though the rc file that needs to be edited
+will be different.
+
+Category:Solaris
+Category:man
+
+
+// vim: set syntax=asciidoc:
diff --git a/src/EXE_Disassociation.ascii b/src/EXE_Disassociation.ascii
new file mode 100644
index 0000000..f17549b
--- /dev/null
+++ b/src/EXE_Disassociation.ascii
@@ -0,0 +1,53 @@
+EXE Disassociation
+==================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+I recently fixed a computer with a problem that I have not seen in several
+years.
+
+As every IT guy knows, files in Windows typically have an extension and that
+extension is what Windows uses to determine which program should be used as the
+default for opening that type of file (.docx Microsoft Word, .txt Notepad, .jpg
+your image program, etc).
+
+That being said, what program is used to open .exe (executables / programs)
+files? I actually am unsure as to the answer for this one. I presume Windows
+sees an executable file and knows to run it as a program rather than a file
+that is loaded by another program.
+
+
+[[the-problem]]
+== The Problem
+
+Unfortunately, Windows can lose the association between a .exe and how the file
+should be run.
+
+This is set in the registry but without the ability to run executable files,
+one can't run regedit to make the changes.
+
+
+[[the-workaround]]
+== The Workaround
+
+Make a .reg file that will correct the problem.
+
+Just open the following link, download the file called EXE File Association
+Fix, and run it.
+
+[http://www.dougknox.com/xp/file_assoc.htm" target="_blank
+http://www.dougknox.com/xp/file_assoc.htm]
+
+Restart your computer after you have run the registry file. After logging in,
+your executable assiciation problems should be fixed.
+
+Many thanks to [http://www.dougknox.com/" Doug Knox] for this fix.
+
+Cheers all!
+
+
+Category:Microsoft
+Category:Windows
+
+
+// vim: set syntax=asciidoc:
diff --git a/src/Empathy_Accounts_Dialog_won't_Launch.ascii b/src/Empathy_Accounts_Dialog_won't_Launch.ascii
new file mode 100644
index 0000000..f1aa6ae
--- /dev/null
+++ b/src/Empathy_Accounts_Dialog_won't_Launch.ascii
@@ -0,0 +1,36 @@
+Empathy Accounts Dialog Won't Launch
+====================================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+
+== {doctitle}
+
+I am currently working on a blog post on how to build a non-linux user
+friendly-ish laptop (something similar to Ubuntu in software sets) using Arch
+Linux (I know, not exactly the best of ideas). In this process, I installed
+Empathy, a multi-medium instant messenger. When I tried to add an account
+however, I ran into a strange issue that gave me very ambiguous errors (which I
+unfortunately forgot to copy). After searching around, I stumbled upon
+https://bbs.archlinux.org/viewtopic.php?id=96918[this] forum thread that solved
+my problem. The issue is that in Arch Linux, installing Empathy doesn't
+automagically install telepathy, a framework for real time conversation (the
+project page can be found http://www.ohloh.net/p/telepathy[here]). To fix this
+issue, we simply need to install telepathy.
+
+----
+pacman -S telepathy
+----
+
+And with that, give Empathy a reboot
+(http://www.youtube.com/watch?v=W8_Kfjo3VjU[three times]). I found
+unfortunately however that Empathy has a process that likes to hang behind even
+after quitting the application. Just run an ol' *ps -ef | grep empathy* and
+kill the pid and you should be golden.
+
+
+Category:Linux
+Category:Linux_Applications
+
+
+// vim: set syntax=asciidoc:
diff --git a/src/Enabling_Colors_in_Ksh88.ascii b/src/Enabling_Colors_in_Ksh88.ascii
new file mode 100644
index 0000000..d0c9e83
--- /dev/null
+++ b/src/Enabling_Colors_in_Ksh88.ascii
@@ -0,0 +1,38 @@
+Enabling Colors in ksh88
+========================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+
+== {doctitle}
+
+I won't lie. I'm a Linux user. At the very least, I'm a semi-up-to-date 'nix
+command line user and I work on AIX far more than I'd like. I intend no offense
+to you AIX guys out there. My frustration with it is primarily korn shell;
+Others fustrations including the fact that every package IBM releases for it is
+between 15 to 25 years old, and its ever-leaning tendancies towards non-Unix
+ways of doing things (eg: smitty, odm, init binaries instead of scripts, etc.).
+
+However, it is what it is. If you like frivolus things such as color in your
+terminal, you may have noticed that putting it in your .profile doesn't work
+super well. It turns out that ksh88 won't recognize the \e or the \033
+characters in place of the actual esc character (no, you're not doing anything
+wrong). What you need to do instead is hit the following key sequence in vi to
+get an actual escape character
+
+* Go into insert mode
+* Press ctrl+v
+* Hit the escape key on your keyboard
+
+You should now see something like **^[**. This represents an escape key
+press. All of your color-set sequences should be the same right after
+this character.
+
+For an example, Creating bold text might look like...
+
+----
+Bold text
+----
+
+
+// vim: set syntax=asciidoc:
diff --git a/src/Expanding_Divs_Containing_Floated_Elements.ascii b/src/Expanding_Divs_Containing_Floated_Elements.ascii
new file mode 100644
index 0000000..a316490
--- /dev/null
+++ b/src/Expanding_Divs_Containing_Floated_Elements.ascii
@@ -0,0 +1,29 @@
+Expanding Divs Containing Floated Elements
+==========================================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+
+== {doctitle}
+
+Today I was working on a site with one center column that contained two columns
+within and I ran into a rather distressing problem (in the most extreme of ways
+of course). When I floated my left column to the left as well as my right
+column, I noticed that the container div shrunk itself to the size of it's
+padding, leaving the internal divs just hanging outside (in the cold). I toyed
+with all the css properties I could think of to no avail. I even consulted the
+plastic green ninja on my desk.  After all else failed, I decided to consult
+the almighty Google. Behold, my findings...
+
+The website I found was a bit outdated since it referenced Firefox 1.5 as well
+as IE 5.0 (and IE 5 for Mac...I didn't know they ever had one of those).
+Despite its apparent obsolescence, the information it gave was still valid for
+this particular article.
+
+I'll spare you the talk and give you http://www.ejeliot.com/blog/59[the link].
+
+The method I ended up using was applying *overflow:auto;* to my div.
+
+
+
+// vim: set syntax=asciidoc: