Difference between revisions of "Downloads"

From Linux-VServer

Jump to: navigation, search
Line 5: Line 5:
 
Basically the stable and development releases should be similar in functionality, but the development releases will include features and enhancements not present in the stable branch. Once those features mature (and get well tested), they will be incorporated by the stable branch.
 
Basically the stable and development releases should be similar in functionality, but the development releases will include features and enhancements not present in the stable branch. Once those features mature (and get well tested), they will be incorporated by the stable branch.
  
For example the first stable release (1.00) uses two systemcalls as the previous releases did. However, the vserver system calls have been changed in the first development release (1.1.0). Linus assigned the vserver project a single system call, so a [System Call Switch] has been implemented. Running a development release usually requires using recent (latest) tools from the util-vserver development branch.
+
For example the first stable release (1.00) uses two systemcalls as the previous releases did. However, the vserver system calls have been changed in the first development release (1.1.0). Linus assigned the vserver project a single system call, so a [[System Call Switch]] has been implemented. Running a development release usually requires using recent (latest) tools from the util-vserver development branch.
  
 
1.X.z and 1.Y.z releases are for the 2.4 kernels, while 1.9.x (obsoleted by now) and 2.X.y releases are for the 2.6 series.
 
1.X.z and 1.Y.z releases are for the 2.4 kernels, while 1.9.x (obsoleted by now) and 2.X.y releases are for the 2.6 series.

Revision as of 12:35, 4 August 2006

Choose your version

The Linux-VServer project maintains several branches of the kernel patch. Since version 1.00 the versioning is similar to the kernel versioning scheme. Even numbered releases (a.X.z with even X) are stable, reasonably well tested and expected not to change feature-wise. Odd numbered (a.Y.z with odd Y) releases are development releases. The last digit/number (z) is a subversion identifier. Experimental versions and Release Candidates might add a fourth identifier to that scheme.

Basically the stable and development releases should be similar in functionality, but the development releases will include features and enhancements not present in the stable branch. Once those features mature (and get well tested), they will be incorporated by the stable branch.

For example the first stable release (1.00) uses two systemcalls as the previous releases did. However, the vserver system calls have been changed in the first development release (1.1.0). Linus assigned the vserver project a single system call, so a System Call Switch has been implemented. Running a development release usually requires using recent (latest) tools from the util-vserver development branch.

1.X.z and 1.Y.z releases are for the 2.4 kernels, while 1.9.x (obsoleted by now) and 2.X.y releases are for the 2.6 series.

The latest version of the stable Linux-VServer patch for 2.6.19 is: 2.6.19.7 vs2.2.0.3 ChangeLog
The latest version of the stable Linux-VServer patch for 2.6.20 is: 2.6.20.15 vs2.2.0.3 ChangeLog
The latest version of the stable Linux-VServer patch for 2.6.21 is: 2.6.21.6 vs2.2.0.3 ChangeLog
The latest prepatch version of the stable Linux-VServer patch for 2.6.22 is: 2.6.22.1 vs2.2.0.3-rc1 ChangeLog
The latest version of the stable Linux-VServer + grsecurity patch is: 2.6.21.6 vs2.2.0.3-grsec2.1.10 ChangeLog
The latest version of the old stable Linux-VServer patch is: 2.6.17.13 vs2.0.2.1 ChangeLog
The latest version of the old stable Linux-VServer + grsecurity patch is: 2.6.17.14 vs2.0.2.1-grsec2.1.9 ChangeLog
The latest prepatch version of the old stable Linux-VServer patch is: 2.6.16.52 vs2.0.3-rc3 ChangeLog
The latest prepatch version of the upcoming Linux-VServer development patch is: 2.6.22.1 vs2.3.0.15 ChangeLog
The latest version of the 2.4 Linux-VServer patch is: 2.4.30 vs1.2.10 ChangeLog
The latest prepatch version of the 2.4 Linux-VServer patch is: 2.4.34 vs1.2.11-rc1 ChangeLog


All (previous) downloads are available in the Archives.

Feature Comparision

The following table tries to give an overview of features available in different releases.

Feature 1.00 1.20 1.2.10 1.3.8 0.09 1.9.0 1.9.2 2.0 2.1
Legacy Kernel API (vs1.2x) yes yes yes part part part part part part
Legacy Proc Filesystem yes yes yes part part part part part part
Immutable Link Invert yes yes yes yes yes yes yes yes yes
Initpid and Fakeinit yes yes yes yes yes yes yes yes yes
Syscall Command Switch - yes yes yes yes yes yes yes yes
Syscall vkill commands - yes yes yes yes yes yes yes yes
Syscall rlimit commands - yes yes yes yes yes yes yes yes
Syscall ctx_wait support - - - - - - - yes yes
Syscall iattr commands - - - yes yes yes yes yes yes
Syscall namespace commands - - - yes yes yes yes yes yes
Syscall context flags - - - - yes yes yes yes yes
Syscall context caps - - - - yes yes yes yes yes
Syscall scheduler tuning - - - - - yes yes yes yes
Syscall 32bit compat - - - - - - - yes yes
Next gen. Proc Filesystem - - - yes yes yes yes yes yes
Chroot Barrier Flag - - - yes yes yes yes yes yes
Proc Security Flags - - yes yes yes yes yes yes yes
Userspace Reboot Helper - yes yes yes yes yes yes yes yes
Userspace Startup/Shutdown Helper - - - - - - - yes yes
VRoot Device - yes yes yes - - - yes yes
Advanced IP Selection - - - yes yes yes yes yes yes
Advanced uts_name config - - - yes yes yes yes yes yes
Fake Memory Display - - - - yes yes yes yes yes
Hard CPU limits - - - - - yes yes yes yes
Context File Tagging - - - - - yes yes yes yes
Context ID Propagation - - - - - - - - yes
NFS based File Tagging - - - - - - yes yes yes
Per Context Disk Limits - - - - - - yes yes yes
Network Context Support - - - - - yes yes yes yes
Socket Accounting - - - - - yes yes yes yes
Advanced Sysctl Debug System - - - - - - yes yes yes
Extended proc/devpts Security - - - - - - yes yes yes
Flag: Pause Context - - - - - yes yes yes yes
Flag: Hide proc/mounts - - - - - yes yes yes yes
CCap: Secure Mount - - - - - yes yes yes yes
CCap: Change host/domainname - - - - - yes yes yes yes
CCap: Modify rlimits - - - - - yes yes yes yes
CCap: Raw ICMP for Ping - - - - - - yes yes yes
Bind Mount Extensions - - - - - - - - yes
Copy on Write Link Breaking - - - - - - - - yes
Quota Hashes - - - - - - - - yes
Persistent Context Support - - - - - - - - yes
Personal tools