Ubuntu distribution Experiment (CVS + SSH)

Note: If you are using Ubuntu9.04, please refer to the CVS bug in Ubuntu9.04 (Januty) (severe!) here !) ConnectionRefused is always used during login. Solution: IfyouarerunningJauntyJackalope (ornextversionswhentheycome) youmayencountererrorconnec

Note: If you are using Ubuntu 9.04, please refer to here

CVS bug in Ubuntu 9.04 (Januty) (severe !)

Connection Refused is always used during login. solution:

If you are running Jaunty Jackalope (or next versions when they come)
You may encounter error connection refused when trying to connect.
Main cause is different security in new version of system.

Fix: edit config for cvsd

Sudo gedit/etc/cvsd. conf
Change line: Listen * 2401
To this: Listen 0.0.0.0 2401

Then just restart cvsd:
Sudo/etc/init. d/cvsd restart

When performing an experiment on multiple servers, there will always be a code inconsistency problem. After modifying the code on one server, you must synchronize the code on multiple servers. if you copy it with a USB flash drive, it will be too bad .. after multiple attempts, I adopted the following policy:

1. Install the Ubuntu Desktop version on the development server to find information. The experimental server installs the Ubuntu Console version to ensure performance;

2. There will always be file transfer between servers. Consider using tar cfz to package locally and then transfer it to the server through ssh. Related commands:
(1) tar cfz kfs-0.2.2
(2) scp kfs-0.2.2.tar.gz fify@10.0.7.6:/home/fify/packages
(3) tar xfz kfs-0.2.2.tar.gz

3. After the relevant package is transferred, You can compile and install it.

4. The code between different servers must be consistent. This experiment makes sense. To avoid manual transmission for every modification, I use cvs and can also perform version control.

5. Configure CVS on the development machine. The command is as follows:
(1) sudo apt-get install cvs: install
(2) sudo apt-get install cvsd: install cvsd
(3) cd/var/lib/cvsd: Create/myprop
(4) sudo mkdir cvsroot
(5) sudo cvs-d/var/lib/cvsd/cvsroot init
(6) echo "SystemAuth = no \ nPamAuth = no \ nLockDir =/tmp/cvsroot">/var/lib/cvsd/cvsroot/CVSROOT/config
(7) sudo mkdir/var/lib/cvsd/tmp/cvsroot
(8) sudo cvsd-passwd/var/lib/cvsd/cvsroot named Y: create a user
(9) sudo vi/etc/cvsd. conf: keep it default.
(10) sudo chown cvsd: cvsd/var/lib/cvsd-R
(11) sudo/etc/init. d/cvsd restart: restart the cvs service.

6. Use cvs in eclipse: Add resources and set the path to/cvsroot.

7. the test machine uses cvs. Related commands:
(1) cvs-d: pserver: fify@10.0.7.6:/cvsroot login: login
(2) cvs-d: pserver: fify@10.0.7.6:/cvsroot checkout/home/fify/packages: Export files in/cvsroot to the/home/fify/packages directory

8. Each time you modify all the testing machines, you only need to perform an update operation. The command is as follows:
(1) cvs update: You need to go to the corresponding directory.