I create user manually according the following steps
(1) vi /etc/group ------Guest:x:700:
(2) mkdir /home/peter
(3) vi /etc/passwd----peter:x:555:700::/home/peter:/bin/bash
(4) pwconv
(5) passwd peter---xxx.......
(6) cp -r /etc/skel /home/peter
(7) chown -R peter:Guest /home/peter
But when i try to use peter to login , it fail and show ..........what's that ?

login: peter
Password:
-bash-2.05b$

Your login worked (meaning your account worked). The problem is with step #6:
What that command did was to copy the /etc/skel directory directly to /home/peter. In other words, you made a /home/peter/skel directory. You probably wanted to do this:

cp -r /etc/skel/* /home/peter

With the command originally used, the .bash_profile and other files (used to control the bash prompt and other things) were put in /home/peter/skel, and not /home/peter (where they are expected to be).

Sorry, I also don't know what u mean.
if I show the content of directory /etc/skel, it is nothing.

[root@localhost skel]# pwd
/etc/skel
[root@localhost skel]# ls
[root@localhost skel]#

Also if I type the following command it show................
[root@localhost /]# cp -r /etc/skel/* /home/peter
cp: cannot stat `/etc/skel/*': No such file or directory

Actually, the command I gave before is still lacking. You would probably need two commands:
cp -r /etc/skel/* /home/peter
cp -r /etc/skel/.* /home/peter

Ok, some explanation is in order.

1: "-bash-2.05b$" is the default prompt for bash. Bash will use that command prompt if the user does not have anything specified in his/her configuration files.

2: The configuration files are stored in the user's home directory (/home/peter). There are a few of them, but the ones typically used are .bash_profile and .bashrc. The dot ( . ) at the beginning of those filenames make them hidden; they will not show up on an ls command unless you use the -a or -A argument (for example, ls -al /home/peter).

3: The /etc/skel directory is supposed to contain basic configuration files to help in creating new users. Specifically, it should contain basic versions of .bash_profile and .bashrc. The reason you copy the contents of /etc/skel to the home directory is so the new user gets those basic configuration files. Those files will have the same names as mentioned previously, and that means they will not show up unless you use the -a or -A argument to ls.

If you do this command: ls -al /etc/skel
and you still get no output, then your /etc/skel directory is empty. Either your distribution did not place basic configuration files there or it expects you (as the administrator) to make your own.

The point is, the account you added did work. It's not a problem with the account working, it's a problem with the account having the expected configuration.

Thanks you very much !!!
I get it

Sorry, I have one more question. Is it mean that if I want to copy all hidden files from one directory to another directory. I need to add "." before "*". Otherwise it not work.

cp -r /etc/skel/.* /home/peter

Exactly. When you use * by itself, the command will only copy non-hidden files. You must force it to copy hidden files by putting the dot in front of the *.

The dot in front of the * does not perform the specified task. The command "cp -r /etc/skel/.* /home/peter" will copy all the files in the /etc directory in the /home/peter directory.

Check using the following command:

ls -la /home/peter

Thanks all of you !!!

Not exactly. If there are any files that are not hidden placed into /etc/skel (such as a new user startup guide, basic data for a specific application, or a common non-hidden directory structure), then copying only ".*" will not get all the files in the /etc/skel directory.

By turning dotglobbing on for the current bash shell,

You can set your '*' to expand to all files/directories, even those starting with a '.' character.

Just will tell you whether is currently on or not.