wget http://launchpadlibrarian.net/17069296/kxsldbg_3.5.10-0ubuntu1_amd64.deb
wget http://launchpadlibrarian.net/17069294/kommander_3.5.10-0ubuntu1_amd64.deb
wget http://launchpadlibrarian.net/17069293/klinkstatus_3.5.10-0ubuntu1_amd64.deb
wget http://launchpadlibrarian.net/17069291/kfilereplace_3.5.10-0ubuntu1_amd64.deb
sudo dpkg -i k*.deb
sudo apt-get install quanta

1. First look up the Printer Name on your Linux box, it is best if it is a single word and under 20 characters. You can typically find this by opening a document, selecting Print and it should be the name in the drop down.
2. Next you will have a script that call rdesktop like so:
   rdesktop -r printer:<YOUR PRINTER NAME ON LINUX>="WINDOWS DRIVER NAME AS IT APPEARS IN ADD PRINTER" <YOUR SERVER IP ADDRESS>
3. Run the rdesktop script and login
4. Go to Printers and Faxes
5. Right-click on the Printer that matches your Linux printer’s name and choose Properties
6. Print a test page!

Note: This only works if you are using a public/private key for authentication via SSH and on a user by user basis. To do this read my post titled, LinkStation Pro Duo, enabling SSH.

To get this to work from a Client machine that runs Linux, you need to install “sshfs”. In short, this allows you to mount a drive/share on your LinkStation Pro Duo onto your client machine. This in turn gives you the opportunity to run rdiff-backup locally which DOES NOT require rdiff-backup –server to be installed on the LinkStation.

Once you have sshfs installed, you will need to create a startup script for your username. Now this will vary depending on the distribution you use, but if you use Ubuntu or one of its derivatives, you can do the following:

1. Setup Directory for Mount Detection
   We need a directory setup on the NAS so that we can tell if the share has already been mounted. This is needed because every time you login via SSH, it will try to mount this drive, and if you are like me and you run your PC 24/7, this could be a problem.
   1. Remote into your NAS via SSH, using ssh <username>@<nas_ip_address>
   2. Create a directory on your NAS that you will put in as the CHECK_FOLDER value in the below script by running
      mkdir <path_to_your_new_folder>
2. Create a .bash_login script
   1. Open your favorite editor (gui, graphical user interface or cli, command line is fine), name it “.bash_login”
   2. Copy the following into the file:
      #!/bin/bash

      CHECK_FOLDER=/mnt/nas-backup/
REMOTE_FOLDER=<username>@<nas_ip_address>:/mnt/array1/Backup
LOCAL_FOLDER=/mnt/nas-backup

      # Check if the NAS Backup Share has been Mounted, if it hasn't mount it
if [ ! -d $CHECK_FOLDER ]; then
sshfs $REMOTE_FOLDER $LOCAL_FOLDER
fi

   3. Replace the values of CHECK_FOLDER, REMOTE_FOLDER, and LOCAL_FOLDER so it suites your setup.
   4. Save the file
3. Logout and log back in
   Your NAS share should be mounted automatically so long as you have a public/private key authentication setup.
4. Setting up your rdiff-backup
   For rdiff-backup, I simply run
   rdiff-backup --exclude-special-files <path_to_directory_to_backup> <mount_location_of_nas_share>
   
   To automate it, I put it as a cronjob that runs every night.

Note on 12/08/2008: I have now started to use rsync as it does not require me to mount the NAS Shares onto my personal computer. It also supports public/private keys allowing me to run it via cronjob daily.

That’s it!

IMPORTANT NOTE: I made a few corrections to the below by adding item 3.6, and updating items 4.4, 5.11, and 5.12. Please read those items over again. If you needed to perform items 5.11 and 5.12 for two PCs, it is important that you use the updated commands.

1. Enable Telnet (temporarily)
   1. Download the acp-commander
   2. Run the .jar file by running
      java -jar acp_commander.jar -t <IP ADDRESS> -o
   3. Login to your LinkStation Pro Duo using (username and password are found on the above link)
      telnet <IP ADDRESS>
2. Enable SSH at Startup
   1. Create an SSH Startup script by typing vi /etc/init.d/sshd.sh
   2. Type ‘i’ to enter Interactive Mode (this enables you to type), then proceed to type the following code:
      #!/bin/sh
test -f /usr/local/sbin/sshd || exit 0

      ACTIVE_FILE=/var/run/active_sshd

      case "$1" in
start) echo -n "Start services: sshd"
/usr/local/sbin/sshd -f /etc/sshd_config 2>/dev/null &
touch $ACTIVE_FILE
;;
stop) echo -n "Stop services: sshd"
killall sshd
rm -f $ACTIVE_FILE
;;
restart) $0 stop
$0 start
;;
*) echo "Usage: $0 start | stop | restart"
exit 1
;;
esac
exit 0

   3. Press the ESC key and type “:wq” to Save and Exit
   4. Make the file executable by running
      chmod +x /etc/init.d/sshd.sh
   5. Backup the original script startup file by running
      cp /etc/init.d/rcS /etc/init.d/rcS.bak
   6. Modify the rcS file to contain the SSH startup script by typing the following:
      vi /etc/init.d/rcS
   7. Press “i” to enter Interactive Mode
   8. Page Down till you see
      echo "** step3 **"
   9. At the end of the next line, add
      sshd.sh
   10. Your change should now look similar to the following:
       for cmd in diskmon.sh drivecheck.sh ftpd.sh atalk.sh httpd.sh smb.sh clientUtil_servd.sh bonjour.sh lsprcvd.sh daemonwatch.sh logrotate_init.sh cron.sh checkconfig.sh ups.sh pwrmgr.sh sshd.sh
   11. Save your changes and exit by pressing the ESC key and typing :wq
   12. Add your SSH script to the Daemon Watch, so if it crashes/closes, it will be started again automatically. Run the following code to edit the list
       vi /etc/daemonwatch.list
   13. Type “i” to enter Interactive Mode
   14. Add the following line to the file
       /var/run/sshd.pid /var/run/active_sshd /etc/init.d/sshd.sh restart
   15. Save your changes and exit bt pressing the ESC key and typing :wq
3. Configure SSH
   1. Backup your original sshd_config file by typing
      cp /etc/sshd_config /etc/sshd_config.bak
   2. Modify the sshd_config file by typing
      vi /etc/sshd_config
   3. Press “i” to enter Interactive Mode
   4. Remove the # in front of the following lines (you need to use the backspace key to do this; you may also need to change some of the ‘no’ values to ‘yes’)
      Port 22
Protocol 2,1

      HostKey /etc/ssh_host_key
HostKey /etc/ssh_host_rsa_key
HostKey /etc/ssh_host_dsa_key

      PermitRootLogin yes
StrictModes yes

      RSAAuthentication yes
PubkeyAuthentication yes

   5. Save the file by pressing the ESC key then typing :wq
   6. Start the SSH Server by running /etc/init.d/sshd.sh start
4. Create new Home folders for each user
   You will need to do the following for every user you have created!
   1. Create the users via the Web Interface first, once the users are created, start Step 2 for each user
   2. Create a directory for the user by typing (replace <username> with the actual username)
      mkdir /home/<username>
   3. Give the user permission to that folder by typing
      chown <username>.<group> /home/<username>
      Now this is a bit tricky, depending how you setup the groups. You want to give the permission to a valid user and a group the user is part of. For example, if you have a user named “matt” and a group named “contributor”, then your command would be
      chown matt.contributor /home/matt
   4. Finally, make sure the directory has the correct permissions by running the following command
      chmod 0755 /home/<username>
   5. Set the user’s home directory by running
      usermod -d /home/<username> <username>
5. Create public/private key pairs for each user
   You will need to do the following for every user you have created!
   I am only going to go over the commands you would use in Linux as I haven’t tried this with PuTTY yet. You will need to do these steps as “each user”. In other words, you will have to logout on your PC, login as the next user and repeat the commands (advanced users can use su <username> to login as an additional user without logging out as their own).
   1. Run the following command in Terminal or Konsole on YOUR PC
      ssh-keygen
   2. Leave the file name as “id_rsa”
   3. If you want a passphrase enter it here, otherwise, leave it blank (I left mine blank)
   4. Next run the following command to generate a SSH 2 key
      ssh-keygen -t dsa
   5. Leave the file name as “id_dsa”
   6. If you want a passphrase enter it here, otherwise, leave it blank (I left mine blank)
   7. Next copy the files to your LinkStation by running
      scp .ssh/*.pub <username>@<IP ADDRESS>:/home/<username>
   8. Next login to the LinkStation via SSH using
      ssh <username>@<IP ADDRESS>
   9. Once login run the following command to create your SSH key directory
      mkdir .ssh
   10. Make sure the permissions are set properly by running
       chmod 0700 .ssh
   11. Load the public key for SSH 1 by running
       cat id_rsa.pub >> .ssh/authorized_keys
   12. Load the public key for SSH 2 by running
       cat id_dsa.pub >> .ssh/authorized_keys2
   13. Make sure the public key entries for SSH have the correct permissions by running
       chmod 0600 .ssh/authorized_keys*
   14. Exit out of the LinkStation by typing “exit”
   15. Try step 8 again and make sure it did not ask for your password this time (if you entered a passphrase, you will be prompted for your passphrase)

Download the sshd_config.zip

So here is the big secret. First get a Linux distrobution that allows you to use a Live CD. Boot up the computer you wish to backup with the Live CD. While that is happening, get on your primary PC (that is hopefully running Linux) and type the following command and run it:
netcat -l -p 1234 | dd of=backup.img bs=16065b

Once the Live CD is booted, start up the terminal/konsole and run the following (must be ran after the prior command):
sudo dd if=<hard drive partition to backup> bs=16065b | netcat <linux PC's IP Address> 1234

That’s it! It will now backup the hard drive partition you selected on the PC running the Live CD. So easy!

Now, the reason I hate how Ubuntu and Kubuntu do this, is it is very easy to fill up the entire drive and not know where the bulk of the data is. With separate partitions, when one fills, you know what caused it, or more specifically, what folder is growing too large. I use several development packages and pull down the source to a lot of packages for experimental use, and so a 160 GB drive can fill up fast. With that said, partitioning things out allows me to quickly identify where I need to allocate more storage, and put in a new drive to handle it.

I wish Ubuntu and Kubuntu would allow the Guided Partioning that Debian allows under expert mode to create a multi-partition setup.

There are a few things you have to do to the machine you wish to login to first before you can use this nice feature. First of all you need to modify the /etc/kde3/kdm/kdmrc file and set make sure you have the following:
[code]
[Xdmcp]
# Whether KDM should listen to incoming XDMCP requests.
# Default is true
Enable=true
# The UDP port on which KDM should listen for XDMCP requests. Do not change.
# Default is 177
Port=177
# File with the private keys of X-terminals. Required for XDM authentication.
# Default is ""
KeyFile=/etc/kde3/kdm/kdmkeys
# XDMCP access control file in the usual XDM-Xaccess format.
# Default is "/etc/kde3/kdm/Xaccess"
Xaccess=/etc/kde3/kdm/Xaccess
# Number of seconds to wait for display to respond after the user has
# selected a host from the chooser.
# Default is 15
#ChoiceTimeout=10
# Strip domain name from remote display names if it is equal to the local
# domain.
# Default is true
#RemoveDomainname=false
# Use the numeric IP address of the incoming connection on multihomed hosts
# instead of the host name.
# Default is false
#SourceAddress=true
# The program which is invoked to dynamically generate replies to XDMCP
# DirectQuery or BroadcastQuery requests.
# If empty, no program is invoked and "Willing to manage" is sent.
# Default is ""
Willing=/etc/kde3/kdm/Xwilling
[/code]

Next you need to modify the /etc/kde3/kdm/Xaccess file. For ease of use, I made it so any host (‘*’) can connect and the CHOOSER BROADCAST was set to ‘*’.

Once you have that finished, you then must restart KDM. From the command line or the TTY login, run “sudo /etc/init.d/kdm restart”.

Now you can login to the remote machine using XDMCP. Enjoy!

After pulling off the side of my case to first figure out what the popping noise was I heard late Monday evening, I really didn’t see anything unusual. I then proceeded to investigate the hard drives since two of them disappeared off my computers radar. Upon investigating and through many tests, I discovered my secondary slave drive (a 120 GB Hitachi Deskstar 7200 RPM P/N 07N9549) died. This sucked! I had a dozen DVDs on that drive in ISO format so I could just quickly play any of them without putting in an actual DVD Disc.

So without any doubt I will be looking for a hard drive to replace my dead one plus a few new fans, as some of them are getting really loud and are annoying the crap out of me.

Then, I decided to browse a few forums I like to visit, and behold I noticed the scroll wheel did not scroll the page up and down…BLAST! I then proceeded to assume it was a configuration issue and search the Internet high and low for solutions that all failed. Using ZAxisMapping of “6 7″ or “8 9″, etc. all of it did not work! Restarted X Server countless times all to find out my latest changes were doing nothing but annoying my wife (as when GAIM starts and she is logged in, it automatically sends her a message, and so she got half a dozen or more tonight alone).

Finally, I reverted my X configuration back to its normal settings and decided to lose my up-time statistics to see if a reboot would help anything. TA DA! Everything worked right out of the box. Why I spent an hour earlier trying 50 dozen things that didn’t work instead of properly installing the mouse is beyond me, but none the less, I am now a much happier person trying to overcome the frantic need to move the mouse physically to move the cursor.

Let this be a lesson learned, no matter how simple the computer part, it is best to install it with the computer powered off. Who would have guessed?

Aside from that though, I also had a lot of things going on at home. I have been prolonging fixing my main system as it continuously frustrated me, but today I decided to give it another try and to get the second power supply to properly control my hard drives, while my main power supply powered the motherboard and video card. FINALLY today it worked! Now my main system finally has all its hard drives running which is sitting at a total of 5 right now, in a while, I will be adding more, but 5 is good.

I also got my secondary system (used for development/testing of Linux updates before preforming them on my main machine) up and running today with a major overhaul. I also have two 120 GB drives in there for storage as well and I am thinking I will mirror them and use it for backups, but that will be decided later. Right now, I have it installing Feisty (https://wiki.kubuntu.org/FeistyFawn/Herd1/Kubuntu) as I want to see what eye candy comes out of it and see if I want it on my main machine.

Also, cpCommerce released v1.0.4 this week! I re-added the MySQLi support. It also has several fixes by other members who spent countless hours learning how to use SVN and contribute to fixing the bugs.

Well, I really do not have anything more to add at this moment. I am looking forward to a 4 day work week and then I will be gone for 8 days as I am going down to TN for Christmas (I may even take Kami – my wife along… hehe).