Tuesday, February 17, 2009

cp: omitting directory linux command error

ok, i've done this so many times, and i just forgot how to overcome this error.

so i am writing this little how to just incase you are also having this problem.

if you are getting this error: cp: omitting directory

this is what you need to do:

cp -r orginal_file new_file


Saturday, February 14, 2009

கவியரசு கண்ணதாசன்

One Hundred Tamils
of the 20th Century

Remembering Kavi Arasu Kannadasan
கவியரசு கண்ணதாசன்
24 - 6 - 1927 to 17-10-1981


Thursday, February 12, 2009

Configuring Fedora Linux Remote Access using SSH


REFER Source it have Clear Screen Shots

Configuring Fedora Linux Remote Access using SSH
From Techotopia
Jump to: navigation, search
Previous Table of Contents Next
Remote Access to the Fedora Linux Desktop Displaying Fedora Linux Applications Remotely (X11 Forwarding)

SSH is a TCP/IP service that provides a secure mechanism for remotely logging into one system over either a local network or the internet into another system. SSH also provides the ability to transfer files between remote systems. When a user logs into a remote system using SSH, they receive a command prompt allowing them to enter commands on the remote system as if they were sitting at the remote system and had opened a terminal session.

In this chapter we will cover the steps necessary to configure a Fedora Linux system to accept SSH connections. This involves installing the SSH server on the local systems and configuring the firewall to allow SSH connections.

* 1 Installing SSH on an Fedora Linux System
* 2 Configuring the Fedora Linux Firewall to Allow SSH Connections
* 3 Using SSH on Fedora Linux
* 4 Copying files using SSH
* 5 Disabling the SSH Server

[edit] Installing SSH on an Fedora Linux System

In order for a system to accept SSH connections the system must first be running the SSH server. By default, Fedora Linux installs the SSH server so it is not usually necessary to install it. To check if it is installed and running use the following command:

/sbin/service sshd status

This will generate output similar to the following if the service is installed and running:

sshd (pid 9488 9486 1850) is running...

If the service is not installed it can be installed as follows:

su -
yum install openssh-server

The installation process with download the SSH server, install it and start the service running in the background. You may now attempt to connect from a remote system (see below for details of how to do this). If you receive a "connection refused" message when you try to connect it you may need to configure the firewall to allow SSH connections to be established to this system.

If the service is installed, but not running, it can be started either from the command-line:

/sbin/service sshd start

or by using the GUI Service Configuration tool accessed via the System->Administration->Services' menu option. Once the tool has loaded, simply scroll down the listy of services until you reach sshd. Check the box so that is starts on system re-boot and then click the Start button.
[edit] Configuring the Fedora Linux Firewall to Allow SSH Connections

If you are using a firewall to protect your system you will need to allow SSH connections before you be able to connect from a remote system. If you are using the basic firewall configuration (see Basic Fedora Linux Firewall Configuration) you can allow SSH connections using the Security Level Configuration tool. This tool is launched from the System->Firewall and SELinux menu option as appears as follows:


If the box next to SSH is not already checked, check it and click Apply

If you have configured your firewall using the Firestarter tool you will need to set up an incoming connection policy to allow connections to the SSH service. Configuring Firestarter is covered in detail in Using Firestarter to Configure a Fedora Linux Firewall.
[edit] Using SSH on Fedora Linux

SSH can be used to log into your system from a remote system. It is also possible to test that the SSH server is running and accessible from the local machine. SSH connections are established using the ssh client utility.

To connect from your local machine back to itself use the following command:

ssh -l username ipaddresss

Where username is the name of the user you wish to log in as and ipaddress is the IP address of your system. You can also substitute the hostname of the system in place of the IP address. If you do not know the IP address run the ipconfig command in a terminal window. This will output information similar to:

eth0 Link encap:Ethernet HWaddr 00:13:72:0B:14:57
inet addr: Bcast: Mask:
inet6 addr: fe80::213:72ff:fe0b:1457/64 Scope:Link
RX packets:4261067 errors:0 dropped:0 overruns:0 frame:0
TX packets:4409081 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2068332349 (1.9 GiB) TX bytes:2408187471 (2.2 GiB)
Base address:0xcce0 Memory:fe3e0000-fe400000

In the above output the IP address is shown as inet addr:, in this case

To connect from a remote system perform the same steps above using either the IP address or host name of the remote host to which you connect. Enter your password when prompted and you will find yourself logged into the remote system.
[edit] Copying files using SSH

The SSH service provides a mechanism for copying files to and from a remote system. Copying is performed using the scp utility. To copy a file to a directory on a remote system, execute the following command:

scp myfile.txt username@

Where myfile.txt is the name of the file to be uploaded to the remote system, username is the name of user account to be used to log into the remote system, is replaced by the real IP address or hostname of the system and /home/demo represents the directory into which the file should be copied.

The above file could similarly be copied from the remote system to the local system as follows:

scp username@ .

The above command will copy the remote file to the current directory on the local system.
[edit] Disabling the SSH Server

Having configured the system to run the SSH server we can now look at how to disable it. As we mentions previously the SSH server runs in the background as a service. In order to disable SSH we need to turn off the SSH service. This can be achieved using the Services tool or from the command line. To disable the sshd service from the command line:

su -
/sbin/service sshd stop

To launch the services tool click on the desktop System menu and select Services from the Administration sub-menu. Enter your password when prompted to do so. The Services tool will appear containing a list of all available services. Scroll down to find the sshd entry as shown below:


Uncheck the box next to the SSH entry and click on the Stop button. The SSH server is now disabled and will not restart if the system is re-booted. To re-enable the server, repeat the above steps and check the box next to sshd to enable the service on re-boot and press Start to immediately start the service.

Thursday, January 22, 2009

error 1355,error 2350,error: -1603

Posted Sat August 05 2006 19:38
**NOTE- I tried this only on Windows XP, may work on other versions- don't know

Hi all,

First time here on this site. I just finished helping my friend to build a pc specifically to play silent hunter 3. Interesting watching someone spend that much money to play a game, especially since he's big on Apple and thinks all things Microsoft are evil...lol. Anyway, we put it together only to watch him have a royal meltdown when he got the following during install: "error 1355. The cabinet file"Data1.cab" required for this installation is corrupt and cannot be used". Once you get this you get 3 options, retry, cancel and ignore...i think. If you hit one (retry I think) it just keeps failing, hit cancel an it's over, but hit ignore and I believe we got an "internal error 2350" followed by an "error: -1603 fatal error during install". We searched through this entire site and found some very interesting answers which unfortunately never worked. The biggest of these was the thought that a new disk might be flawed or that a DVD ROM may be dirty. None of these were the case with us. I ran a google search on this error and found tons of people having the same problem with intensive programs (memory hogs). You guys are not the only ones out there. It's hard to believe that all these people are getting flawed disks and we knew the DVD ROM wasn't dirty because it was new out of the box. There are so many things to try out there, so if what I suggest don't work, try googling a search for yourselves and see what does work. Don't give up. Some people out there thought it might be a memory problem. Though my friend put in a gig and a half of RAM we wanted to be sure it wasn't the RAM DIMMS. I took the DIMMS out of my pc and installed them in his...no help. Mind you we tried this after 5 hours of trying the various tips I spoke of. So I tried fudging with the settings. BINGO!! Again I tried this only on XP, I can't remember how to do this with other versions. Do the following:

1- click "Start"
2- click "RUN"
3- type "msconfig" in the box and click "OK"
4- select "BOOT.INI" from the top tabs
5- select "advanced options" near the bottom center
6- click on the box to the left of "/MAXMEM="
7- change the number that appears to 512
8- click "OK" then click "apply" then exit that box using the OK buton or the X on top.
9- it will probably as you to restart your computer- do it
10- Try to reinstall the game again..it will probably work, but if not, put in 256 for the number instead.

Here's the catch, if you end up using a number lower than the minimum required for the game to run it will give you a screen saying you have too little memory. Don't worry, make sure the game installs first using the low numbers then change the settings back to normal AFTER THE INSTALL IS COMPLETE, by using the same procedure and removing that X by the "/MAXMEM=". Now you have all your available memory back and can run the game without a hitch. Boy was my friend happy... and I gotta say, it looked like a great game and the graphics were awesome.

He was so relieved that he made me promise to sign up here just to post a possible resolution to this problem so that hopefully some of you will be able to play without huge headaches. I promised him, so there you are guys...good luck

Dark Wolf

Monday, January 5, 2009

Removing non-empty directory in LINUX

rm -rf
rm -rf /path/to/directory