znbtc

1. I was the one who defeated the super warrior, It's mainly xiaote and Wutian plus No.18 plus Colin to play a shrunken version of biochemical Brolli, which is very useless< br />
http://www.tudou.com/programs/view/mYxbtCZnvSs/

2. Zn + 2HCl = = = ZnCl2 + H2 ↑
65 73 136 2
6.5g X Y Z
65 / 6.5g = 73 / x = 136 / y = 2 / Z
x = 7.3g
y = 13.6g
Z = 0.2g1 mass of hydrogen 0.2g
2 mass fraction of solute in dilute hydrochloric acid 7.3g/100g * 100% = 7.3%
3 mass fraction of solute in solution after reaction 13.6g / (6.5g + 100g-0.2g) * 100% = 12.8%

3. Blue blood grows in the sky
http://ke..com/link?url=rIEynLuUh__SOSuWqrXUW0ClzATOK4Ln2VX59dWS_T0c9d3Trch9cWX-l50_su7m

4. Git server construction and client installation under CentOS
time: May 14, 2014 source: blog.51cto.com
Outline:
1. Foreword
2. Git server construction
Yum installation
create a git user to run git service
create client login certificate
initialize git warehouse
disable shell login
clone remote warehouse
3 Installation client
Windows client
linux client
IV. summary
note: CentOS 5.5 x86_ 64, GIT server version: git version 1.8.2.1, client version: git version 1.9.2. Msysgit. 0. All software can be downloaded here: http://msysgit.github.io/ <

I. preface
in the last blog, we mainly explained what Git is, the basic principles of GIT, and some basic knowledge about GIT. Let's have a simple understanding of GIT. Of course, we still have a lot of problems to figure out, hehe! How about management? Before we figure out these problems, we have to have a git server, right? Hehe! OK, let's build a git server< 2. Build git server
1. Yum install git server

2[ root@git ~]# cd src/
[ root@git src]# wget http://dl.fedoraproject.org/pub/epel/5/x86_ 64/epel-release-5-4.noarch.rpm
[ root@git src]# rpm -ivh epel-release-5-4.noarch.rpm
Preparing... ########################################### [100%]
package epel-release-5-4.noarch is already installed
[ root@git ~]# yum list
[ root@git ~]#Yum install - y git

2. Create a git user, It is used to run git service

[ root@git ~]#Adser git

3. Create a client login certificate
note: collect the public keys of all users who need to log in, that is, their own generated IDs_ Rsa.pub file, all public keys to / home / git /. SSH / authorized_ In the keys file, one line at a time. Hey, hey
1)_ The command of rsa.pub file

$SSH keygen - t RSA
$cat. SSH / ID_ rsa.pub
ssh-rsa ++N3wEAQRYDmcYo1wmnm/4NQ+CAN45tqfsRuf58Uba9QNK7/6xSUiIKXQiILz8PMGJ3MnlV+== leo@LEO-PC

note: just press enter all the way to generate the ID_ Rsa.pub is copied to the administrator to help you add it on the server. The next time you use git, you don't need to enter the user name and password
2)_ Keys file

[ root@git ~]# cat /home/git/.ssh/authorized_ keys
ssh-rsa wBVd++YmJFhqwkITNGccrO5sycROs9+Fbjgd6oBSzNuaBtCIbwNNsEyM/henTl2euI3XsnJQ/ITr6c/q0P3WoGl4E2QFQ2kZqs++/+kJzJSKUTKDVSwY3/+Q== root@CHENMINGQIAN
ssh-rsa +PSK9PSg+bwiJ2iQRa39rXck35r+//RiCiYzd3RT/+S/LD3vx2MN+FNOHwvqcE+/5yEqSgAkioa8SVMOsikYJG//RZ54Q== Administrator@WIN2003X323
ssh-rsa ++N3wEAQRYDmcYo1wmnm/4NQ+CAN45tqfsRuf58Uba 9QNK7/6xSUiIKXQiILz8PMGJ3MnlV+== leo@LEO-PC

note: I have three users logging in to the server, so I have three SSH RSA, you can have a look
4. Initialize git warehouse
note: first select a directory as git warehouse, here is / data / git / project.git< br />
[ root@git ~]# cd /data/git/
[ root@git git]# git init --bare project.git
[ root@git Project. Git] # LS
branches config description head hooks index info objects refs

executing the GIT command above will create a bare warehouse, which has no workspace, because the GIT warehouse on the server is purely for sharing, Therefore, users are not allowed to log in to the server directly to change the workspace, and git warehouses on the server usually end with. GIT. Then, change the owner to git:

[ root@git git]# chown -R git.git project.git
[ root@git Git] # LS - L
total 4
drwxr-xr-x 7 git git 4096 05-09 13:50 project. Git

5. Disable shell login
note: for security reasons, GIT users created in the second step are not allowed to log in to the shell, which can be completed by editing the / etc / passwd file. Find a line similar to the following:

[ root@git ~]# cat /etc/passwd | grep git
git:x : 1001:1001: git version control: Home / git: bin / bash

is changed to:

[ root@git ~]# vim /etc/passwd
git:x : 1001:1001: git version control: Home / git: usr / bin / git shell

in this way, GIT users can use git normally through SSH, But we can't log in to the shell, because the GIT Shell we specified for git users will automatically log out every time we log in
6. Clone the remote warehouse
note: now you can clone the remote warehouse through git clone command and run it on your own computers:

note, $git clone [email protected] : / data / git / project.git, where git user name, git.jjhh.com server, / data / git / prguject.git is the warehouse path. Well, here we are, the server is finished. Now let's install the client< 3. Install client
1. Windows client
1). Download client
note: you can download it here http://msysgit.github.io/ . The following is a simple demonstration of the installation process, which is relatively simple:

OK, the installation is completed here. After the installation, there will be an icon on the desktop, you can double-click to open it. As shown in the following figure:

2. Linux client
note: Linux client installation is relatively simple, just use Yum to install it< br />
1

[ root@test ~]#Yum install - y git

here, Git is installed, Let's check the version below:

1
2

[ root@test ~]#Git -- version
git version 1.8.2.

next, we generate the public key and it to the server:

[ root@test ~]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_ rsa):
Created directory '/ root/.ssh'.< br />Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_ rsa.
Your public key has been saved in /root/.ssh/id_ rsa.pub.
The key fingerprint is:
48:3c:22:76:02:f1:a2:e5:27:22:cb:4f:a7:a0:98:9d [email protected]
[ root@test ~]# cat .ssh/id_ rsa.pub
ssh-rsa ++U7zP/hr6HzfqeZU09Ccis4yK3RMwip2f+/ug2M68Z0jQk5DVG8w5+/V7eOkrvBMDh9nDdwvDhPhuhBDSfE++B18MQ== [email protected]

let's ID below_ Public key in rsa.pub to authorized server_ In the keys file< br />
[ root@git ~]# su git
bash-3.2$ cd
bash-3.2$ vim .ssh/authorized_ keys
ssh-rsa wBVd++YmJFhqwkITNGccrO5sycROs9+Fbjgd6oBSzNuaBtCIbwNNsEyM/henTl2euI3XsnJQ/ITr6c/q0P3WoGl4E2QFQ2kZqs++/+kJzJSKUTKDVSwY3/+Q== root@CHENMINGQIAN
ssh-rsa +PSK9PSg+bwiJ2iQRa39rXck35r+//RiCiYzd3RT/+S/LD3vx2MN+FNOHwvqcE+/5yEqSgAkioa8SVMOsikYJG//RZ54Q== Administrator@WIN2003X323
ssh-rsa ++N3wEAQRYDmcYo1wmnm/4NQ+CAN45tqfsRuf58Uba 9QNK7/6xSUiIKXQiILz8PMGJ3MnlV+== leo@LEO-PC
ssh-rsa ++U7zP/hr6HzfqeZU09Ccis4yK3RMwip2f+/ug2M68Z0jQk5DVG8w5+/V7eOkrvBMDh9nDdwvDhPhuhBDSfE++B18MQ== [email protected]

let's clone a warehouse to the local directory< br />
[ root@test ~]# cd /data/dev
[ root@test dev]# git clone [email protected] :/data/git/project.git
Cloning into ' project'...< br />The authenticity of host ' git.jjhh.com (114.112.173.150)' can' t be established.
RSA key fingerprint is ca:ec:a2:7e:e6:89:ca:19:d3:93:7f:4b:c3:c0:c7:fd.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ' git.jjhh.com,114.112.173.150' ( RSA) to the list of known hosts.
remote: Counting objects: 50, done.
remote: Compressing objects: 100% (42/42), done.
remote: Total 50 (delta 21), reused 0 (delta 0)
Receiving objects: 100% (50/50), 4.02 KiB, done.
Resolving deltas: 100% (21/21), done.
[ root@test dev]# ls
project
[ root@test dev]# cd project/
[ root@test Project] # LS
index. HTML

OK, our git client is all installed here.