From 542cb3c7866b85644bff8e5cc85ffd448660e9af Mon Sep 17 00:00:00 2001 From: Enrico Scholz Date: Fri, 7 Jan 2005 17:40:15 +0000 Subject: [PATCH] fixed typos cleanups + enhancements git-svn-id: http://svn.linux-vserver.org/svn/util-vserver/trunk@1784 94cd875c-1c1d-0410-91d2-eb244daf1a30 --- util-vserver/README | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/util-vserver/README b/util-vserver/README index 702b798..defb36f 100644 --- a/util-vserver/README +++ b/util-vserver/README @@ -151,14 +151,18 @@ a level of the featureset stability but not of the software stability. E.g. 'stable' is not really stable: it has huge security problems and missing functionality. But you can expect that the current configuration -will work in future versions also. +will work in future versions also. This version is untested on author's +side and it will be hard to bring patches/fixes in, since it must be +proofed that they will not break anything. In the opposite, the 'alpha' branch does not have known security issues -and works well on author's system. But it may happen that some behavior -or configuration options change. With 'alpha' you should be still able -to use vservers created with the 'stable' branch, but you may encounter -some oddities -- especially on kernel 2.6 systems (e.g. 'vserver-stat' -will show the names of old vservers). +and works well (at least on author's system ;)). But it may happen +that some behavior or configuration options change. + +With 'alpha' you should be still able to use vservers created with the +'stable' branch, but you may encounter some oddities -- especially on +kernel 2.6 systems (e.g. 'vserver-stat' will not show the names of old +vservers). So let me summarize: -- 1.8.1.5