CVS Installation and Configuration on Linux (Legacy Server and Client Setup)

Concurrent Versions System (CVS) is a legacy source control tool that some teams still operate for older applications. This guide turns the original quick notes into a clearer runbook for installing CVS, configuring a Linux server, and connecting clients with fewer setup mistakes.

Originally published on 2009-04-06; fully revised and updated.

Install CVS packages by Linux distribution

The original post referenced rpm, up2date, yum, and apt-get. The table below keeps that context and adds practical command choices used today on many systems.

# Example installs
sudo yum install cvs
sudo dnf install cvs
sudo apt-get update
sudo apt-get install cvsCode language: PHP (php)

CVS server setup workflow

flowchart TD
    A[Install CVS package] --> B[Create cvs service account]
    B --> C[Initialize repository root]
    C --> D[Configure xinetd pserver]
    D --> E[Restart xinetd service]
    E --> F[Client sets CVSROOT]
    F --> G[cvs login and checkout]

Create a CVS service account and initialize the repository

The original article creates a dedicated cvs user. Keep one repository root path consistent across all commands and configuration files.

# Create service account (example)
sudo useradd -m -d /home/cvsroot -s /sbin/nologin cvs
sudo passwd cvs

# Initialize repository
sudo -u cvs cvs -d /home/cvsroot initCode language: PHP (php)

Configure CVS pserver with xinetd (legacy method)

If your environment still uses xinetd and pserver, create or verify /etc/xinetd.d/cvs with values aligned to your host and repository path.

service cvspserver
{
    disable         = no
    socket_type     = stream
    wait            = no
    user            = cvs
    group           = cvs
    protocol        = tcp
    server          = /usr/bin/cvs
    server_args     = -f --allow-root=/home/cvsroot pserver
    bind            = 192.168.1.100
    port            = 2401
    log_on_failure  += USERID
}Code language: JavaScript (javascript)

After saving the file, restart xinetd:

sudo service xinetd restart
# or, on systemd-based hosts
sudo systemctl restart xinetdCode language: PHP (php)

Client configuration and first login

Use the server IP/hostname and repository path in CVSROOT, then authenticate and checkout a module.

export CVSROOT=:pserver:USERNAME@192.168.1.100:/home/cvsroot
cvs login
cvs checkout MODULE_NAMECode language: JavaScript (javascript)

Access method comparison: pserver vs SSH

About the original Procedure #2

The original post includes manually creating CVS administrative files like Entries, Root, and Repository. In normal usage, CVS manages these files automatically. A cleaner workflow is to initialize the repository once, then use checkout/add/commit from a client working copy.

# Server-side one-time init
sudo -u cvs cvs -d /home/cvsroot init

# Client workflow
export CVSROOT=:pserver:USERNAME@192.168.1.100:/home/cvsroot
cvs checkout MODULE_NAME
cd MODULE_NAME
cvs add new_file.txt
cvs commit -m "Add new file"Code language: PHP (php)

Legacy reference links from the original post

• http://www.taursys.com/howto/cvs/
• http://www.cyberciti.biz/faq/linux-setup-a-concurrent-versioning-system-cvs-howto/
• http://www.cs.brandeis.edu/~guru/cvs.html
• http://defindit.com/readme_files/cvs.html

Common pitfalls and best practices

• Keep one consistent repository root (for example, /home/cvsroot) across CVSROOT, xinetd config, and server commands.
• Do not manually edit CVS admin files in working copies unless troubleshooting a specific corruption case.
• If using pserver, restrict network exposure and monitor port 2401 carefully.
• Prefer SSH-based CVS access where possible for encrypted authentication and transport.
• Document package manager and service manager differences across your Linux estate to reduce operational drift.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.