So, I’ve been tossing around the idea for the past while to make is so that screen starts up every time I ssh into my box at the house.  Well, I finally broke down and did it, and it wasn’t that bad at all.  I’ve named my screen session main you can call it whatever you want.  Just add the following to the end or your .bashrc If you don’t put it at the end, you the rest of your .bashrc won’t get evaluated.

if [ $TERM == "screen" ]
# If we are already in a screen do nothing
then
     echo -n ""
elif [ $TERM == "dumb" ]
# If we are using scp do nothing
then
     echo -n ""
else
# Startup screen
screen -Rd main && exit
fi

It works so far with everything I’ve had to do, but we’ll see if I run across any other problems.

I’m all for security.  I believe that in a time like now, you have to be sure that the data you are getting, storing or sending has to be verifiable.  However, there is a time when this is not the case.  When security become a hindrance to everyday work, that’s when it is a problem.  Imagine having to stop your work every 5 minutes to swipe your finger or type your password to prove that you are using the computer, and that someone didn’t tie you up and throw you under your desk.  I know that it seems a bit too much, but the same thing could be said for encrypting every email you send.  I don’t think an email about cats doing something funny needs to be encrypted.  The same holds true for other things that verifying the source doesn’t truly matter.  If I send an email to someone scheduling a meeting, I don’t care if it’s really them sending an email back saying they’ll be there.  It’s not like an axe murder is going to take their place, and if they had encrypted their email, I wouldn’t get killed.  Oh well, looks like I’ll keep having to type my ridiculously long GPG password just to decrypt an email saying ‘ok’. </rant>

Part of my job has now required me to actually start using my gpg key for more than just goofing off, or the occasional one-off.  So, as part of that I wanted to make sure I have all of my work mail clients configured to work with gnupg.  As a I talked about in a previous post this is pretty easy in thunderbird and firefox (for gmail).  And I thought it would be difficult for mutt.  But it’s not.  Pretty much the first link in a google search for ‘gnupg mutt’ lead me to this page.  Which has everything you need.  Then I realized that I already had it in my .muttrc, but it was commented out.  So I’ve updated my .muttrc on dotfiles.org The only thing that wasn’t explained in the documents is how you ecrypt or sign if auto-sign is off.  After commiting the email, before hitting y to send the email, hit p to bring up the gpg.  It’s pretty straight forward from there

First,  I know I’m going to hell for using Ubuntu.  But, I’m too lazy to compile xbmc and boxee on Fedora.  So, now that it’s out of the way.  Here’s the step-by-step:

1. Install Ubuntu 10.4
2. Add the extra boxee repo based on the instructions on boxee.tv
3. Install mingetty and rcconf
   

   apt-get install mingetty rcconf

4. Disable gdm with rcconf
5. Add a boxee user with and add them to the “admin” and “audio” group
   

   useradd -G admin,audio -d /home/boxee boxee

6. Add a .bashrc to /home/boxee
   

   case "`tty`" in
   /dev/tty1) startx
   esac

7. Add .xinitrc to /home/boxee
   

   #!/bin/bash
   while [ 1 ]
   do
   exec /opt/boxee/Boxee --standalone
   done

8. Make it executable
   

   chmod a+x .xinitrc

9. Edit line in /etc/event.d/tty1
   

   #exec /sbin/getty 38400 tty1
   exec /sbin/mingetty --autologin boxee tty1

10. Reboot and pray