I was going to write an article on how to open docx’s and other Office 2007 documents but there are numerous articles out there explaining how to do this on many distributions. They all basically say the same thing, you download the file, extract it and put it in your open office directory. Normally there are a couple of files but the on we are interested in is the main binary. What some people don’t know is that if you want to just quickly open or convert a document you can do so by using the odfconverter binary. (Read on …)
Linux users often like to boast about their awesome bootup times. I thought that there was nothing cooler than getting a wicked fast bootup time, until now. A while back I found this nifty application called bootchart and shoved it in my bookmarks. I was randomly surfing my bookmarks, came across it again and gave it another shot. (Read on …)
Today the KDE User base wiki (http://userbase.kde.org/) went live. If you’ve ever searched for information regarding an issue with KDE, its possible you would have come across the techbase (http://techbase.kde.org) The KDE Techbase is aimed more at developers and has some really good content regarding development. The KDE userbase Wiki also has some great information and you can learn a lot about KDE just by reading it. If you are a developer or an end user the userbase can be of great help, I just learned something new about plasma application launchers, check it out!
Lets say you use subversion on your home PC to keep track of projects and you want to checkout or export your project from a remote location. Here’s the catch, sshd is running on a custom port or forwarded from another. For some reason the command line SVN client does not support a port parameter when using the defacto svn+ssh://
svn co svn+ssh://thelinuxblog.com/owen/svn/project1/trunk project1 ssh: connect to host thelinuxblog.com port 22: Connection refused
Well we know why the error above happens its because I happen to run SSH on port 1337. The following work around requires root privileges, and may mess with your system a bit but if you really need to check something out, then it will work.
As root, login and stop SSH if you run it. With SSH Forward port 22 with a local SSH forwarding connection to the remote host.
[firstname.lastname@example.org]$ sudo su - [email@example.com]$ /sbin/service sshd stop [firstname.lastname@example.org]$ ssh -p 1337 email@example.com-L 22:[internal ip]:1337
Once this is done, your localhost:22 now forwards to your remote host. With another session (on your local machine) you can verify the connection by using ssh localhost. You will probably get warnings about the hosts identity being changed, or not verifying it, but you can ignore then. Once you’ve tested it, just use SVN as normal. When finished, remember to logout of the SSH session, and start SSH back up again if you run it.
Before you ask why your Java applications don’t work, or why your applet doesn’t initialize in Firefox, Seamonkey or Whatever browser you use do you know what version of Java you are using?
“Yes, I installed the JRE 1.6.0_XX”,
Thats nice, but is it running? Now, it may seem as obvious as “Is your computer on?” to some, but to others and I admit myself it isn’t always that obvious. I had installed the Java Runtime /JDK and tested my firefox. Programs worked from the command line, java -version provided me the correct Java version, but why were my applets failing to load?
The firefox plugin is the answer. Open up about:plugins in firefox and take a look at the Java providers. If you don’t see the Java(TM) plugin there then there is a problem. Refer to the Correct Java documentation on how to get this corrected. Basically you symlink a file and disable the other Java providers.
Hard drives are a vital part of system performance. They really are one of the biggest bottle necks in computing. Its nice to know how many MB/s your hard drives are capable of reading. If you perform the tests could share your results with other Linux Blog readers? With advances in hard drive technology I hope to see performance get better, and already see a major increase in performance over the old IDE type drives.
To check your hard drive read times use hdparm like so:
hdparm -t /dev/sdX
replacing sdX with whatever device your distribution assigned. Here are my results:
sda is my internal 80GB SATA drive. /dev/sda: Timing buffered disk reads: 224 MB in 3.02 seconds = 74.07 MB/sec sdb is an internal 80GB IDE Drive [owen@LinuxBlog ~]# hdparm -t /dev/sdb /dev/sdb: Timing buffered disk reads: 62 MB in 3.09 seconds = 20.06 MB/sec sdc is an internal 160GB IDE drive [owen@LinuxBlog ~]# hdparm -t /dev/sdc /dev/sdc: Timing buffered disk reads: 90 MB in 3.03 seconds = 29.70 MB/sec
The next two tests are rather interesting. sde is a brand new freshly formated 1TB external Western Digital MyBook Drive.
[owen@LinuxBlog ~]# hdparm -t /dev/sde /dev/sde: Timing buffered disk reads: 2 MB in 7.69 seconds = 266.25 kB/sec [owen@LinuxBlog ~]# hdparm -t /dev/sde /dev/sde: Timing buffered disk reads: 68 MB in 3.01 seconds = 22.60 MB/sec
The first result was what the read time is like when you first initialize the drive. Since the drive was in power down, the read time was horrendous. This was fixed second time around. You will notice that the transfer rate over USB 2.0 is not all that bad in comparison to the internal IDE. Both IDE drives are not primary drives, and are also on the same channel. I’m not sure if that makes a difference or not. Also when I try to set DMA and 32 bit support I get an IOCTL error indicating that something went wrong, so I don’t think that this is a fair test.
Either way, post your results, if see if you can tweak the hard drive settings then see what the read times are. Check out my: Hard Drive Tuning with hdparm article.
If you follow me on Twitter you would know I asked everyone if there was anything that they wanted me to write about. @Ben_Marvin responded and asked about logging the commands you type to Twitter.At first, I thought that this could be done with history, which it probably can be, but does everything you type really have to be echo’ed to Twitter? I don’t think that you’d have many friends, Twitter would probably hate you and you’d most likely hit your maximum requests per hour pretty quickly.The Script command is another option, and this works quite well for this purpose. Read the script man page to find out more about this program. It basically (when ran) takes the I/O from your terminal and logs it to a file. Its a very handy utility.So, how do we get this data into Twitter? First of all, Twitter doesn’t allow very long posts so echoing out the data that the commands you type is not really practical. The best way to do it is to use script to log the session, exit the session and grep for the “]0\;” string for stuff you typed & not the responses.Here is the code:
script; grep ]0\; typescript
You can then copy and paste it to your favorite Twitter application or pipe it to a scrubbing script to remove the formatting and do the correct HTML stuff, then post it via the http interface. Either way, it can be done even though I don’t think it really should.
TheLinuxBlog.com was intended to be a blog where I could log my thoughts, findings and generally keep track of how to do stuff. Since it was started this is still the goal. Ultimately I’d like to refer to TheLinuxBlog on how to do something just as much as I refer to google for everything else. That being said, one thing that recently came up for me was “How do I change my desktop on Fedora”.
I had done this before but I couldn’t remember the command to do so. Well, since this blog is as much for me as it is for the reader I figure I can post the how to here and kill two birds out with one blog post, I mean stone.
The program I use to change my window manager on Fedora is: switchdesk.
Switchdesk can be installed by Yum or if you installed Fedora from DVD or CD and didn’t fine tune your packages then you probably have it already. All you have to do to run it is type:
Now, if you are in an X session you will get a nice graphical dialog that will help you change your desktop manager. If your at the terminal it will exit and ask you nicely to type either gnome, kde, xfce or any other window manager you may have installed.
Don’t ask me why every distribution has a different named command and interface to achieve the same thing thats just the way it is. Maybe one day I’ll get a list of all of the commands and post them. Alternatively if anyone wants to start a list feel free to post them in comments or by e-mail.
Using proprietary software to some Linux users is considered a sin, right up there with not reading the manual. Not everyone that runs Linux feels this way. I for one don’t mind using a commercial / propriety product if the product serves the purpose well, and perhaps better than an open source implementation.
Take VMWare server for example. Although it does have its problems, it works very well for virtualization. Its pretty stable, has a good interface, works well and most of all is free. I have no problem installing and using this as long as it works. I’ve been using it for a while, its what I’m used to and I have no problems with it. The moment VMWare Server stops working, I’ll try to find another alternative. Be it open source or not.
I don’t get why some people are so into the open source movement. Not tainting a system to me has no clear advantages. If I were to not install any proprietary software I would hardly be able to use my Linux box. Think about it, no Java (ok, I’d have the IcedTea runtime and GCJ), but no supported Java for Tomcat / Eclipse, I’d have no Flash, hardly any video codecs and no 3D accelerated graphics. My virtualization, may or may not work depending on what day of the week it was or if I had supported hardware. There is probably a whole lot more that I am missing that I don’t even know about.
So, I’m just interested to know what is every one else’s take on using proprietary software? Am I alone in being “fine” with installing closed source / proprietary software? Is my computer going to go to robot hell and sing with Bender for eternity? Please let me know your thoughts.
Yakuake – “Pronunciation Key: yuh-kweyk”
Yakuake is a terminal emulator for KDE
“Why do we need another terminal emulator?”
I hear you ask.
Well, the Yakuake terminal emulator resembles the terminal from Quake (hence the name), except the only thing that gets owned when you run Yakuake is your to-do list.
Have you ever been fragged in Quake because you hit the Tilda key by accident?
Ever used this to your advantage while playing two player by pressing your opponents tilda key?
Have no idea what I’m talking about?
envision a terminal that magically pops up when you press a shortcut, hides when your not using it but retains the output / processes and does not show up in the task bar.
Sure there are old school ways of achieving the same thing, but Yakuake is convenient. It is based on Kommander so its highly configurable and customizable but it works right out of the package.
I use it on most of my machines and for quick tasks I find myself using a regular xterm less. If you want a quick easy access to a terminal I’d recommend trying Yakuake out, take a look at all of the keyboard shortcuts and see if there is any way you can make it work better for you.
I have my keyboard shortcuts set up so I can add new sessions, close sessions, rename sessions, move sessions and resize the terminal. It works great with the switch to session shortcuts that I also set up.
Its in the Fedora repositories, I’m sure its included in Debians 18,000 or so packages and probably Gentoo’s too, so give it a shot!
I’ll see what I can do about a video tutorial in the future to demonstrate the power of Yakuake.
If you run into the following problem:
VMware Server is installed, but it has not been (correctly) configured for the running kernel. To (re-)configure it, invoke the following command: /usr/local/bin/vmware-config.pl.
and then try to issue the vmware-config.pl command and get something similar to the following:
/tmp/vmware-config1/vmnet-only/bridge.c: In function ‘VNetBridgeUp’: /tmp/vmware-config1/vmnet-only/bridge.c:949: error: implicit declaration of function ‘sock_valbool_flag’ make: *** [/tmp/vmware-config1/vmnet-only/bridge.o] Error 1 make: *** [_module_/tmp/vmware-config1/vmnet-only] Error 2 make: Leaving directory `/usr/src/kernels/22.214.171.124-47.fc8-i686' make: *** [vmnet.ko] Error 2 make: Leaving directory `/tmp/vmware-config1/vmnet-only' Unable to build the vmnet module.
Then try to use the VMWare any patch from: http://groups.google.com/group/vmkernelnewbies/files
I had used the patch before to get my VMWare Server up and running but did not realize that you had to use the patch after kernel upgrade or your VMWare server will no longer work.