DVD Backup

May 6th, 2007

With four little kids, you might not be surprised to learn that DVDs get scratched up in our house all the time. I’ve tried d-skin protectors to help protect them, but you’d be surprised just how fast a curious 3 year old can take those off. Anyway, I’d been looking for a “KDE” way to create backup copies of my DVDs.
The option that I’ve found myself liking the most, because it seems to work the best, is dvdbackup. Purely command line, so I guess it might not even be KDE specific. It’s really quite simple. If you don’t have it installed already, do a “sudo aptitude install dbdbackup”; not sure exactly which repository it is in; but it was there for me. Here is example formatting for the command

dvdbackup -F -i/dev/hda -o/mnt/linkstation/Video -n type_DVD_title_here

The “-F” option tells it to go ahead and make an educated guess on what track the featured title is on. If you want to backup a specific title, change -F to the “-t” option, so “-t 3″ would copy just title 3. There is also the -T option, which copies a title set. “-T 4″ would copy the full title set for title 4. If you want to backup the whole shebang (everything on the DVD), switch the option to “-M”. The “-i” option indicates where the DVD is located. For me, it’s /dev/hda/. It may be /dev/dvd or some other location, so figure that out first. The “-o” option indicates to where you want to copy the backup. Notice that in both the -i and -o option there is no space between the option and the directory indicated. Finally, while I don’t think it is always necessary, there is the “-n” option. “-n” followed by a space and then the name of the DVD tells dvdbackup what to label the folder that it is creating this backup under, which will be a subdirectory of the backup location you indicated with option “-o”.
That’s it! Hope it works as well for you as it is for me, and when your little darlings destroy your original copy of your beloved movie, you’ll have a backup plan!

Is (K)Ubuntu your first real experience with Linux?

April 30th, 2007

If you are an Ubuntu or Kubuntu user, go to the Community Cafe on ubuntuforums.org and vote now on whether (K)Ubuntu is your first real experience with Linux, or whether you came from another distro.

I created the poll to gauge whether Ubuntu had a larger proportion of users who are brand new to Linux versus Kubuntu. At this point, we still need more Kubuntu users to vote to make that comparison statistically valid. I’ll post my reasons why that is important to me separately. (hint: I think Kubuntu needs to be brought a little more front and center for those who are looking to try out Linux for the very first time).
However, here is something that has already come out of the poll that is quite interesting and statistically significant. It is especially important in light of DesktopLinux’s survey results, which showed (K)Ubuntu to have a dramatic lead in Linux desktop user share. Of the 124 votes so far, 60 (48%) indicate that (K)Ubuntu is their very first Linux distro. This implies that the tremendous growth seen with (K)Ubuntu isn’t simply a cannibalization of users from other Linux distros. Rather, (K)Ubuntu is generating substantial net new Linux user growth. On the flip side, the fact that 52% are coming from other Linux distros means that more experienced Linux users, who have tried other distros, use (K)Ubuntu because it really is a great distro, simple and plain.

While I’m sure the folks at Canonical have already done, and continue to do some market research on the (K)Ubuntu user base, I think this finding should give them some additional peace of mind, if not joy.

Getting Started with OpenSSH

April 26th, 2007

If you are relatively new to Linux and Ubuntu, you may have heard of ssh but aren’t quite sure what it is. Wikipedia has a reasonably thorough but easy to understand entry on ssh. Basically, ssh is a TCP/IP application layer which provides a secure encrypted channel between a local and remote computer.

You just need to have a ssh server running on the pc to which you want to connect, and an ssh client on the computer from which you are connecting. I found that the ssh client is already installed on all my kubuntu (and ubuntu) feisty machines. For the machine I want to connect to, my main AMD64, I just installed openssh-server. I used Adept Manager, but you could also do so by simply installing from aptitude

sudo aptitude install openssh-server

Now if you follow any how-to’s on running an X graphical application over ssh session, they will tell you that you need to go into the sshd configuration file to allow for X11 Forwarding. Using sudo and your favorite editor open the config file for editing

sudo nano /etc/ssh/sshd_config

then search for the section that references X11Forwarding and make sure it isn’t commented out and is set to “X11Forwarding yes”. I actually found that I didn’t need to edit anything, it was already set to yes. You can confirm whether yours is or not

cat /etc/ssh/sshd_config

At this point, it is time to play! I went over to my kubuntu laptop, also running feisty, yakuaked a terminal open, and simply entered

ssh -X aleska@192.168.1.4

…where -X is the option to enable X11 forwarding, aleska is the user name set up on the computer running the server, to which I’m connecting, and 192.168.1.4 is the IP address of the server pc. It will prompt you for your password, and upon first run it should ask you whether to allow that particular server ip address going forward. Answer yes, and you will be connected.

Now you are at the command line shell for the server pc. You can run graphical applications, commands, etc. just as if you were physically on the server pc. Pretty neat!

I wanted to see if I could ssh over to my kubuntu box, and run a kde app through ssh on my wife’s ubuntu pc, which runs gnome and has none of the kde libraries. Interestingly, amarok seemed to run on my wife ubuntu machine through ssh with no problem, save one. No sound. Or more accurately, there WAS sound, but not coming from my wife’s pc, it was coming from the server pc in my office! For whatever reason, I thought that was particularly cool.

Anyway, I’m just getting my feet wet, literally playing with this stuff tonight for the first time. I’d like to see if and how I could get sound to tunnel through ssh too. This is making me wonder about thin clients and ltsp. Rather than going out and buying a new pc for my sons when they get old enough, maybe I’ll be able to set them up with robust thin clients with some of the older pcs gathering dust in the basement.

Please let me know if you have any insights into getting sound to come through ssh.

Making sure yakuake remembers its history

April 22nd, 2007

“Those who cannot learn from history are doomed to repeat it.” - George Santayana

Ah yes, so true. But what if your history isn’t being saved! In this case, you might actually want to repeat it but can’t easily, because for some reason it isn’t in your history. ??!?! :P
For those of you who aren’t familiar with yakauke, referenced in the post title, you are undoubtedly confused as to where this is going. For those of you familiar with yakuake, you might still be confused. So, I’ll explain.

I have recently become very fond of the kde environment, now preferring it over gnome. One thing I like about it especially, is running yakuake. In a nutshell, yakuake gives you instant, and esthetically pleasing, access to terminal. I believe the ya stands for “yet another” and the kuake is a reference to the game Quake, in which a transparent console of sorts appears from the bottom of the screen (toggling on or off) to enter commands, etc. Similarly, Yakuake toggles a nifty terminal console, for quick command line access.

As much as I love it, I have noticed something, that to me is a little buggy. Yakuake functions just like I would expect a terminal emulator, like konsole, to function. Frankly, the experience is identical. Bash is the default shell. Commands work as expected. So does history, kind of… Enter a series of commands, and then enter history, and as expected, you will see a list of the previous commands you entered. However, I’ve noticed that sometimes when I log out, ending my session, and log back in, many, if not all the commands I entered in yakuake during my last session are missing. I finally found that if I closed the shell within yakuake by typing “exit”, my history would be committed, so that it is available in my history in the next session.

Well, that’s all well and good if you can and will remember to type exit in yakuake before logging out; but that isn’t a great option. Thankfully, Rich Bradshaw over at ubuntuforums.org gave me a simple solution. First, edit your .bashrc file in your home directory.

sudo nano .bashrc

Then go to the end of the file and add the following

shopt -s histappend
PROMPT_COMMAND=’history -a’

Commit changes (save) and close out. Now simply type “bash” at the command line prompt, and every entry from now on should be committed real time to your history, found ~/.bash_history

You can confirm by trying entering some commands in yakuake, then

cat .bash_history

You should see at the end the last commands you entered. Yea! :)

Nvidia Driver on a Fresh Kubuntu Feisty install

April 19th, 2007

Did a fresh install of Kubuntu Feisty on my daughter’s pc.  Everything was looking great until I noticed that the max screen resolution was 800 x 600.  I then remembered that I had used Automatix in the past to install the nvidia proprietary drivers.

Well, of course, I don’t want to do that again.  So, I looked through ubuntuforums for help.  For the record, I love ubuntuforums.  Totally saved my skin so many times.  Of course, when you are racing to get things setup properly, all you want is answers and fast.  Long story short I was getting frustrated because I could find the quick easy answer I was looking for.

Anyway, I wound up going command line and entering

sudo aptitude install nvidia-glx

Then I scratched my head.  What now?  I looked to see if a program had been installed somewhere in my menus.  I tried entering nvidia-glx as a command.  Then after some more forum searching I noticed some people talked about editing their /etc/X11/xorg.conf and changing “nv” to “nvidia”.  So, I backed it up made the edit, restarted, and voila.  Looks like the video driver is working great.
Frankly, it was configuration steps like this that led me to starting this weblog in the first place.  I needed a place to store how I got things working properly, and what I did, so I could come back and reference when needed.  Unfortunately, last time I made notes about setting things up from scratch, my steps included use of automatix.

Ah, one thing to remember.  If you want to know if your video driver is doing direct rendering, type the following:

glxinfo | grep direct

It should come back with “direct rendering: Yes”.  It took me a while to find that command again.

Using Rockbox to Improve my Linux Experience

April 14th, 2007

When I first dove into Ubuntu about 10 months ago, I was making a leap of faith.  I made this leap for a variety of reasons.  I wanted greater control over my computing experience.  I wanted greater reliability, stability and performance than I had experienced with Windows.  And maybe as big a driver as anything, I simply wanted to see what this whole linux thing was about.  I thought it would be fun.  Lucky for me, all those things panned out just as I’d hoped.  I love Ubuntu!  :)   But to be fair, there were implications or ramifications to that decision that I hadn’t fully considered.  How I listen to my music was one of them.

Prior to making the jump to Ubuntu, there were a lot of issues that I had been ignorant about, or just didn’t care about because they didn’t appear to be relevant personally.  While I had been a long time fan and reader of boingboing.net, I had never paid much attention to Cory Doctorow’s postings about the evils of DRM.  If you are someone who has literally bought into the whole iPod / iTunes way of purchasing and listening to music, as I had, DRM doesn’t seem evil.  It is just a reality.  However, when I jumped into the world of Ubuntu, all of a sudden DRM became much more relevant.  I became exposed to the many practical problems DRM creates.

A big problem for me was figuring out what the heck I was going to do about all those DRM’d files I had purchased from iTunes.  Well, I wound up spending some significant time burning those as regular CDs and then ripping them to ogg.  I chose ogg because it is an open format and pound for pound the quality is better than mp3.  Problem solved; right?  Wrong.

What about my iPod?  How was I going to continue to use it given that it doesn’t play ogg formatted files?  I hadn’t fully considered that important point before I spent all that time converting everything to ogg.   So what did I do?  I did what any self-respecting person would, I deluded myself into thinking I really didn’t want my iPod after all.  I mean the battery life was just abysmal; right?  And, how on earth could I hold my head up with a clear conscience, knowing I was carrying around a device made by THE company that single-handedly foisted DRM upon mainstream America.  Sure Steve’s open letter talks about how he hates DRM.  But, come on!  He’s built an infrastructure that all but ensures that consumers are forced to buy HIS products to play the music they bought.  Can he really hate it that much?

So, I started investigating what mp3 players on the market also play ogg formats.  Long story short, I found the pickings slim.  As I wrote about my desire to find an ogg friendly player and posted questions on certain forums, I received a lot of feedback telling me to look into Rockbox.  With Rockbox, I wouldn’t have to throw out the iPod, I could transform it into an open source, customizable bad boy of a music player with all that oggy goodness.

Well, a couple of months ago, I took another leap and installed Rockbox on my iPod.  This was a decision that frankly has had no downsides for me, whatsoever.  Funny thing is that not only does it play ogg files, but the music actually sounds better on it (through cross-feeding).  The battery life is better than it was running the iPod firmware.  It plays nicely with Amarok.  In all it’s great.For those of you who want to check it out, don’t be intimidated.  The install instructions are found in the player model specific manuals.  I had a 2nd gen iPod mini, so I used that one of course.  Also, in each of the manuals, the first installation steps referenced are for Windows users.  Never fear, just keep reading until you get to the linux users section.  Note: when you write the various Rockbox installation files over to your iPod, make sure you go through the proper steps to unmount or “safely remove” your iPod instead of just unplugging it from your pc.  If you don’t, the files you thought you had moved over to your iPod might not actually be written to the device.

A quick note about the cross-feeding feature making for better sound - in layman’s terms.  The theory with cross-feeding is that many studio recordings were optimized for playback on stereos with standard speaker setups, not playback on headphones.  That said, when you are listening to a normal stereo, the music coming from the left speaker, while primarily heard by the left ear, is also heard a bit by the right…and vice versa.  Cross-feeding replicates this experience by allowing a small amount of bleed from one side to the other.  Instead of the music sounding like it is coming from in between your ears, it sounds fuller and it surrounds you.  For the record, real audiophiles come in on both sides of the cross-feeding debate.  The great thing about Rockbox is that it is totally up to you.  You can use cross-feeding, or not, just choose your preference in settings.  Cross-feeding aside, many audiophiles don’t like mp3, aac or ogg files anyway, because they are lossy compression formats.  Instead, they listen to lossless compression formats like FLAC.   Does Rockbox play flac files?  You betcha!

If there is anything I don’t like about Rockbox, it is that I don’t particularly like its playlist creation/management.  I prefer to plan and create my playlists on the desktop, not on the player itself.  While there may be some desktop solutions to manage Rockbox playlists, I haven’t come across them.  However, with some command line magic (thanks Ubuntuforums for the education) I was able to work things out.  Specifically, I use Amarok to move all the songs I want on my player.  This is nice b/c Amarok allows you to define the directory structure / organization of the copied files.  For example, I like to organize them by /artist/album_name/songs(1..n).ogg   Then from terminal, I change directory over to the iPod (cd /media/ipod), and run the following command

find -type f -print > allsongsplaylist.m3u

That creates a playlist ‘allsongsplaylist.m3u’ which I can then edit with any text editor, and simply delete the lines of songs I don’t want in my playlist.  I save the file to the iPod with a new file name (e.g. workoutmix.m3u).  Now I’ve got two playlists on the iPod.  One with all songs, and one with just my workout mix songs.  I find this easy enough especially since the files are all sorted by artist and album.
I hope this post encourages at least a few people out there to try Rockbox.  I am by no means a Rockbox expert.  If you get stuck, try visiting their IRC channel for some help.

In all, Rockbox has helped to improve by overall Ubuntu experience by allowing me to enjoy my non-DRM’ed music, and ogg formated music in particular, anywhere I go and without having to invest in a new music player.

For more information:

Kyles Cheat Sheet for New Ubuntu Users

April 10th, 2007

I really like the straightforward simplicity of Kyle’s cheat sheet for new ubuntu users.  It can be found at http://kyle.monoperative.net/cheat.html.  One thing I’m not sure I agree with is the suggestion to use Automatix2.  Don’t get me wrong, I have used Automatix myself in the past.  In certain flame sessions on ubuntu forums, I’ve weighed in saying that there is nothing wrong with Automatix.  I think it can be a great way for a total newbie to get some much needed/wanted functionality going (especially as it relates to multimedia codec support).

What I don’t like about Automatix, is that the steps it takes to get the codec support etc. really isn’t that difficult.  Both Ubuntu and Kubuntu’s desktop help provides help and links to get codecs for restricted formats up and running.  See the RestrictedFormats section of the Ubuntu Community Documentation site.  Just because its easy enough to do without it, doesn’t explain why not Automatix.  Well, I know from experience that having used Automatix, when upgrading distros, from Dapper to Edgy, or Edgy to Fiesty, it can cause problems with the upgrade.  Those issue may have been ironed out, but I figure why bother with the hassle.  Do it yourself without Automatix and you’ll have nothing to fear when it comes to maintaining and upgrading your system.

Anyway, didn’t mean to get off on such a negative tangent about Automatix.  Overall, nice cheat sheet.  I certainly could have used it when I started out.

Recommended Linux Games

March 16th, 2007

Tristan, over at the Open Source Advocate has put together a list of his favorite Linux games. I haven’t had an opportunity to try all of them out, but I do know that several of them are really good.  Battle for Wesnoth, in particular, I found to be a worthwhile turn based adventure/strategy game.   I tried Planeshift too, the MMORPG, but frankly didn’t think I had enough time to “immerse” myself to make it worth it.

On the gaming note, while I really haven’t played many games recently, I can say that I found Neverwinter Nights to work perfectly, if not better, on Linux than it did on Windows.  So, while I can’t vouch for every windows game running on Linux, NWN is definitely one that you should be able to get working.  So, just b/c you’ve switched from Windows to Linux, doesn’t mean you automatically have to through out every Windows PC game you have purchased.  Google it up,  and you might be surprised to learn just how easy it is to get it working.

To Do List

March 10th, 2007

Things I have been meaning to get around to but haven’t, as it relates to this site.  My goal is to have posts this March about the following:

  • My experience installing and enjoying Rockbox on my second generation (2G) iPod mini.   How to do it, what I like about it, what I don’t like so much, etc.
  • Following Gizmodo’s call to boycott the RIAA and stopping use of iTunes as a source of music purchases.  Specifically, I’ve switched to eMusic and installed a linux specific eMusic download manager.

I have more ideas of things I’d like to spend more time writing about, but for now, this is what is realistic given work and family priorities.

Ubuntu Local Teams LoCos

March 6th, 2007

While is makes perfect sense, it didn’t really occur to me until recently that much of the success of Ubuntu is largely driven by its active and well organized community.  Some would argue that this has been the big difference between Ubuntu and many other distros (see Jono Bacon’s lecture at linux.conf.au called Herding Cats).

Spurred on by many Planet Ubuntu bloggers’ calls to participate in this past weekend’s LoCo Doc Days, I decided to find out when the Colorado LoCo team (CoLoCo) was having its next meeting.  I felt it was time to really join the community, and LoCo teams are one of the best ways to get started.  Like all the various teams that meet, these meetings are held via IRC.  So, I launched XChat, navigated to the appropriate channel (#ubuntu-colorado), and joined my first LoCo meeting.  The team discussed ideas for promoting its upcoming Feisty release party, and a variety of other possible venues and approaches for promoting Ubuntu in general throughout Colorado.  The group was incredibly welcoming and I felt at home immediately!

“What’s the purpose of the Ubuntu LoCo teams?”, you ask.  Simply put, the goal is for Ubuntu fans and enthusiasts to work together in regional teams to help advocate, promote, translate, develop and otherwise improve Ubuntu (from LoCoTeams wiki).
If you are interested is getting involved in the Ubuntu community, I strongly encourage you to take the plunge and join your LoCo.  Find your LoCo team by visiting https://wiki.ubuntu.com/LoCoTeams. You can also find a calendar of upcoming IRC meetings at the Ubuntu Fridge, under Events.