Archive for November, 2008
How to find which RPM owns an installed file
Nov 4th
The ‘rpm -q -f’ command can be used to identify RPM to which an installed file belongs to. The following example queries RPM database to find the RPM that own /usr/bin/kompare file.
[neo@techpulp ~]# rpm -q -f /usr/bin/kompare kdesdk-3.5.8-2.fc8 [neo@techpulp ~]#
If the file doesn’t belong to any RPM it displays a message as shown below.
[neo@techpulp ~]# rpm -q -f /home/neo/myfile.txt file /home/neo/myfile.txt is not owned by any package [neo@techpulp ~]#
How to find the list of installed RPMs
Nov 4th
The “rpm -aq” command can be used to query the list of RPMs installed in the system.
[neo@techpulp ~]# rpm -aq gnu-regexp-1.1.4-10jpp.3.fc8 java_cup-manual-0.10-0.k.6jpp.1 ql2200-firmware-2.02.08-1.fc8.1 popt-1.12-3.fc8 freetype-2.3.5-3.fc8 sed-4.1.5-9.fc8 libattr-2.4.38-1.fc8 device-mapper-1.02.22-1.fc8 libIDL-0.8.9-1.fc8 .... python-xlib-0.13-3.fc7 qt-designer-3.3.8b-2.fc8 [neo@techpulp ~]#
You can use ‘grep‘ command to search for a particular RPM in the list as shown below. In this example, we are trying to find if the GIMP package is installed in the system.
[neo@techpulp ~]# rpm -aq | grep gimp gimp-libs-2.4.0-0.rc3.2.fc8 xsane-gimp-0.994-4.fc8 gimp-2.4.0-0.rc3.2.fc8 [neo@techpulp ~]#
Where is my NetMeeting in Windows XP
Nov 3rd
The NetMeeting application is not directly visible in either start-menu shortcut or desktop shortcut. But NetMeeting application will be installed as part of standard Windows XP installation. So there is no need to download NetMeeting from Microsoft Download Center and install. Moreover if you download NM30.EXE from Microsoft Download Center and try to install it on Windows XP it will say that its version is not compatible with this version of Windows. It is because NM30.EXE is intended for Windows 2000 etc.
Basically NetMeeting is already there in your installation and it’s just that you need to configure it before it More >
Why my Unix/Linux VNC session shows only xterm instead of full desktop
Nov 3rd
The default VNC startup script (~/.vnc/xstartup) doesn’t include any commands to start standard desktops like KDE or GNOME. It contains commands to start primitive TWM as window manager and one xterm terminal as application. The following will be the typical startup file for VNC in Fedora systems.
[neo@neo.techpulp.com ~/.vnc]$ cat xstartup #!/bin/sh # Uncomment the following two lines for normal desktop: # unset SESSION_MANAGER # exec /etc/X11/xinit/xinitrc [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic & xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & twm &
You can change the line More >
Recent Comments