Find executables for missing start menu applications

You will find the most programs in your Start menu. They have search function. Type there the programs name, that's all. But, sometimes it happens that the installer doesn't create start menu entry.
Our freshly installed package called tightvnc. So, if the program isn't there, then you need to find the executable for it. In windows, you go to the place where the program was installed, and double click to the executable. In Linux: you need to open the Terminal, Konsole, whatever - the Command line.
Like in windows you can search for all installed programs in Add Remove programs. Here is the alternative - a bit faster. Type in Command line (CLI) the following:

Code:

rpm -qa | grep tightvnc

the output will be all installed packages containing the name tightvnc. Copy the FULL name (including number) of the tightvnc package, this is what you need. Now type this:

Code:

rpm -q --fileprovide [pasteherethefullname]

This will output the complete list of files installed from this package. The executables are mostly in the /usr/bin/ directory.
My output:

Code:

akoskm@linux-3fx0:~> rpm -q --fileprovide tightvnc-1.3.9-80.41                                                                          
/etc/slp.reg.d                                                                                                                          
/etc/slp.reg.d/vnc.reg                                                                                                                  
/etc/sysconfig/SuSEfirewall2.d/services/vnc-httpd                                                                                       
/etc/sysconfig/SuSEfirewall2.d/services/vnc-server                                                                                      
/etc/xinetd.d/vnc                                                                                                                       
/usr/bin/vnc_inetd_httpd                                                                                                                
/usr/bin/vncconnect                                                                                                                     
/usr/bin/vncpasswd
/usr/bin/vncpasswd.arg
/usr/bin/vncserver
/usr/bin/vncviewer
/usr/share/doc/packages/tightvnc
/usr/share/doc/packages/tightvnc/ChangeLog
/usr/share/doc/packages/tightvnc/LICENCE.TXT
/usr/share/doc/packages/tightvnc/README
/usr/share/doc/packages/tightvnc/WhatsNew
/usr/share/man/man1/vncconnect.1.gz
/usr/share/man/man1/vncpasswd.1.gz
/usr/share/man/man1/vncserver.1.gz
/usr/share/man/man1/vncviewer.1.gz
/usr/share/vnc
/usr/share/vnc/classes
/usr/share/vnc/classes/AuthPanel.class
/usr/share/vnc/classes/ButtonPanel.class
/usr/share/vnc/classes/CapabilityInfo.class
/usr/share/vnc/classes/CapsContainer.class
/usr/share/vnc/classes/ClipboardFrame.class
/usr/share/vnc/classes/DesCipher.class
/usr/share/vnc/classes/InStream.class
/usr/share/vnc/classes/MemInStream.class
/usr/share/vnc/classes/OptionsFrame.class
/usr/share/vnc/classes/RecordingFrame.class
/usr/share/vnc/classes/ReloginPanel.class
/usr/share/vnc/classes/RfbProto.class
/usr/share/vnc/classes/SessionRecorder.class
/usr/share/vnc/classes/SocketFactory.class
/usr/share/vnc/classes/VncCanvas.class
/usr/share/vnc/classes/VncCanvas2.class
/usr/share/vnc/classes/VncViewer.class
/usr/share/vnc/classes/VncViewer.jar
/usr/share/vnc/classes/ZlibInStream.class
/usr/share/vnc/classes/index.vnc

Now you can simple start any of these executables in the /usr/bin/ directory by typing them to the command line.

Creating and mounting ISO images in Linux terminal

There are thousand of applications outside for creating ISO images, and also a thousand for mounting and reading these virtual disks - but, have you ever thought that it's possible through the Linux terminal, by using 2 simple commands? You'll need 2 core applications: dd (DiskDump) and mount. These small applications are core components in every Linux distribution, so you don't need to install anything. So, how to create ISO image with them?
Insert a disk into your optical drive - of course it's also possible to create ISO image from an USB disk. Open the terminal window, and execute:

dd if=/dev/sr0 of=test.iso

where if points to your optical drive (input file), of is the patch, where the ISO image will be created (output file).
Now, our ISO image is done, lets go mount it! The first thing what we need is a mount point for our ISO image. Lets create one:

mkdir isoTmp

this will be the name of the directory where the ISO image will be mounted. Now mount the ISO with the command (only root can mount so you need superuser rights - and his password :)):

sudo mount -o loop test.iso isoTmp/

where the -o specifies that our device is a loop device, after that comes the patch for the .iso file, and finally the directory where we mount this ISO image. After executing this command the image will be mouted, and you can browse it on the local filesystem.
You can unmount it by executing:

sudo umount tmpMnt/

.

For more information about filesystems, and other specific options type:

man mount

in terminal.
Happy hacking! :)

Traffic Limit on Linux

On the Unix-like operating systems the user can choose from many advanced tools to control the network. My opinion is that these tools are too advanced (for an everyday user - no programmers, admins, hackers :) ) - so after some searching I've found a little script what can be easily modified and executed to limit the network speed.
Grab this script from http://lartc.org/wondershaper/. Extract it, then with your favorite text editor open the script called wshaper. Intuitively, these lines:

DOWNLINK=256
UPLINK=64
DEV=eth0

are indicating the upload, download speed (in kilobits!), and the network interface. After modifying these parameters you need to comment out the following two lines:

echo Please read the documentation in 'README' first :-\)
exit

by adding the # sign to the beginning of these lines. Save your script. Open the console window and navigate to the directory which contains the script wshaper, get root powers with

su

and execute the script:

sh wshaper

.

A little speedup.
Use command line for every action. Command line is x10 faster then any GUI application. It's easy to learn and use. Use the edit command for editing the wshaper script (assuming the you can navigate in console with cd command):

edit wshaper

. When the editor loads the script with arrow-keys navigate to the lines what you want to modify. Press A - now you can write into the text - and modify the values. To save, press the : key (SHIFT + ;) and type:

save wshaper

. Use the same commands to execute the script:

su
sh wshaper

.

About HOWTO's

As you can see a new label has been appeared on the side-bar, called HOWTOs. The users need it. When I'm finished with my first how-to on the next week I'm linked it in ~5 forum posts on KDE and openSUSE forums.
Users - came from Windows world - are opening posts about renaming, moving files and they are making longer thread then Fixing your Buggy DST code table. They aren't lames, but the words like permission, user, execute have no meaning in their world, they are calling these things like: ActiveX, I, double-click. I'm absolutely sure that an ordinary people (at least reading and writing skills) who uses computer for browsing the Internet can't figure out anything from manuals like this (part of man mv 1):


NAME
mv - move (rename) files

SYNOPSIS
mv [OPTION]... [-T] SOURCE DEST
mv [OPTION]... SOURCE... DIRECTORY
mv [OPTION]... -t DIRECTORY SOURCE...

. Nobody can say me that working in Linux is hard. No it isn't... actually, my girlfriend (no programming skill, no PC using skill) is using openSuSE. And she is very happy with it. I'm explained a lot of things and now she is using her Laptop as a productive machine. HOWTOs are important, if you are new to Linux and want to learn how to live different, how to live in community, you need just once to read these tutorials after it's going like 1+1, and you'll have more fun!

Laptop extra keys - HOWTO

If you are using laptop your Fn or other extra-function keys are configured automatically. But! If they aren't, then the configuration can became a nightmare where you - the user - want to find out 10 bit hex BIOS interruption codes with blindfolded eyes. Grrr....


Recommended hardware:
At least 1 laptop with broken function keys.
Recommended Software:
keytouch - http://keytouch.sourceforge.net/. It's available from packman repositories, however if you aren't rpm friendly, compile it ;). If you have broken Volume +/- key, there is no need for KMix or other plugins in Keytouch. Amixer will do the work for you.

Start keytouch, and go to the Keyboard screen.



If you can find your laptop model then it would be good idea to select that one, otherwise select some laptop model with Fn keys - Easy to find out, just google for the laptop name. HP worked for me, see the screenshot. So at the Keyboard screen hit the Change button. You'll get a dialog, like this one:



Select one keyboard model and hit OK. After you'll get back the starting screen. Click to Apply, and test your keyboard.



Configuration in Sax2:

Here I'm selected a generic keyboard, because with some laptop keyboard models - Thinkpads, Toshiba Satellite, etc. you common function keys like NumLock, CapsLock won't work.
Good luck!

Unix - Linux - Distro related jokes

ROTFL! There are some really kickass comics from KDE forums:
http://forum.kde.org/best-unix-linux-distro-related-jokes-t-19993.html
Enjoy :D

Gimp 3.0 RC

More Photoshopis for Photoshopers. But it's still Gimp. :)
There was a little discussion about Gimp, and his user-unfriendly attributes. Here i found this picture about 3.0 Release Candidate. The UI looks better... IMHO it is more professional. What do you think?

Level +

The summer has been ended. I have a lot of fun with my friends & family, with my project, with openSUSE and KDE, thanks for everyone. From October 6.
I'm starting with the second year on my faculty, and I have only one exam left from the first year, yey! This year (mostly summer) was full with tech/science related events. First of all, the Large Hadron Collider, and his shut down after two weeks from the the first start...
I'm very happy to see, that KDE community is growing with every single day, together with openSUSE community. My project is heading forward too, after my summer exams I'm improved it a little bit, implemented some new features, fixed some bugs, etc, etc. If anyone interested in database-browsing with Java style, then visit the projects site: http://yami.googlecode.com/. The new Slipknot album All Hope Is Gone is out, and I'm very satisfied with, that's the music what I need ;).
Tomorrow I'll move to my second city Novi Sad, to start my studies. I hope, my second year on the faculty will be great, as this summer was. Thanks for all readers and visitor for following my blog, next time I'll be back with some tech related. :)

ACPI problem solved

Finally, my ACPI problem has been solved by an openSuse Guru on http://forums.opensuse.org.
You can read our discussion about here. I've got 181 views until now :)
So, running from battery is amazing thing, especially in my situation. I'm not used my ACPI functions (like battery, CPU frequencies) after openSuse 10.3 release (about >1 years years).

Your OWN KERNEL.

Nowadays Linux distributions are coming with a built in and precompiled kernel. They are: making the connection between your hardware and software, controlling softwares and resources on your PC/Laptop, they doing everything what is must-to-be for your system.
They have some positive and negative side-effects.
Generally the Linux "newbies" are happy with the precompiled kernel - no command line, no work, everything is up and running automatically. Nice! And you save a lot of time. But! You can compile kernel for your own requirements.
Positive side-effects of the own compiled kernel are:

• it may works faster then the precompiled
• you can save a lot of memory by unloading processes what you don't need
• you are getting complete control of your system
• it is cool

Actually there are no negative side-effects, just some requirements. You need to know how to work under command line, how to compile, etc.
So i don't want to waste your time, here is the link for the best/easiest kernel compiling how-to what I ever read.
It has been written by snake1990, thanks a lot, open-source be with you!
How to compile your own Linux kernel for openSUSE.