Re: [RFR] templates://lxc/{lxc.templates}
Christian PERRIER wrote:
> Template: lxc/auto
> +_Description: Automatically start Linux Containers on boot?
> + Linux Containers can be automatically started during system
> + boot and shut down on reboot/halt.
>
> "on boot" or "at boot"? I have a doubt.
"On boot" sounds fine. The subsequent "on reboot/halt" also sounds
okay. It's only when I think about "on halt" that I begin to have
doubts, and I think it's just that I'm overanalysing it.
We might replace "reboot/halt" with "reboot or halt", though.
> + If you choose this option, the needed symlinks will be created in
> + the /etc/lxc/auto directory.
Another borderline improvement: "the required symlinks".
> +Description: Linux Containers userspace tools
> Containers are insulated areas inside a system, which have their own namespace
> - for filesystem, network, pids, ipc, cpu and memory allocation and which can be
> - created using the Control Group and Namespace features included in recent Linux
> + for file systems, network, PID, ipc, CPU and memory allocation and which can be
> + created using the Control Group and Namespace features included in Linux
> Kernels.
>
> s/filesystem/file system
>
> Capitalize acronyms.
IPC is an acronym (or initialism) too. Plural "PIDs" made sense; I'm
not completely sure about singular "network" and "CPU". I suspect it
means "networking" and "CPUs"... unless maybe it's "CPU- and
memory-allocation". I don't think so. That's an ambiguity caused by
having "memory allocation" last; adding Harvard comma would help avoid
it, but I'd prefer to reshuffle slightly as well:
for memory allocation, file systems, networking, PIDs, IPC, and CPUs, and which can be
I'm tempted to alphabeticise, but never mind. I've changed enough
lines now that I might as well tweak the linebreaks, though.
> I have a doubt for "control group" and "namespace" to be capitalized.
I wasn't sure until I spotted "Linux Kernels"!
> .
> - This package contains the lxc-* tools which can be used to start a single
> + This package provides the lxc-* tools which can be used to start a single
> daemon in a container, or to boot an entire "containerized" system, and to
> successively manage and debug your containers.
Let's have a comma before "which" (since it's describing the tools
rather than defining which ones are provided).
I think by "successively" ("in succession") it means "successfully".
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru old/control new/control
--- old/control 2011-09-23 10:13:04.541949881 +0100
+++ new/control 2011-10-02 12:04:14.417960633 +0100
@@ -12,15 +12,15 @@
Architecture: linux-any
Depends: ${misc:Depends}, ${shlibs:Depends}
Recommends: debootstrap, libcap2-bin
-Description: Linux containers userspace tools
- Containers are insulated areas inside a system, which have their own namespace
- for filesystem, network, pids, ipc, cpu and memory allocation and which can be
- created using the Control Group and Namespace features included in recent Linux
- Kernels.
+Description: Linux Containers userspace tools
+ Containers are insulated areas inside a system, which have their own
+ namespace for memory allocation, file systems, networking, PIDs, IPC, and
+ CPUs, and which can be created using the control group and namespace
+ features included in Linux kernels.
.
- This package contains the lxc-* tools which can be used to start a single
+ This package provides the lxc-* tools, which can be used to start a single
daemon in a container, or to boot an entire "containerized" system, and to
- successively manage and debug your containers.
+ succesfully manage and debug your containers.
Package: lxc-dbg
Section: debug
@@ -28,22 +28,22 @@
Architecture: linux-any
Depends:
${misc:Depends}, lxc (= ${binary:Version}), lxc-dev (= ${binary:Version})
-Description: Linux containers userspace tools (debug)
- Containers are insulated areas inside a system, which have their own namespace
- for filesystem, network, pids, ipc, cpu and memory allocation and which can be
- created using the Control Group and Namespace features included in recent Linux
- Kernels.
+Description: Linux containers userspace tools - debug
+ Containers are insulated areas inside a system, which have their own
+ namespace for memory allocation, file systems, networking, PIDs, IPC, and
+ CPUs, and which can be created using the control group and namespace
+ features included in Linux kernels.
.
- This package contains the debugging symbols.
+ This package provides the debugging symbols for userspace tools.
Package: lxc-dev
Section: libdevel
Architecture: linux-any
Depends: ${misc:Depends}, lxc (= ${binary:Version})
-Description: Linux containers userspace tools (development)
- Containers are insulated areas inside a system, which have their own namespace
- for filesystem, network, pids, ipc, cpu and memory allocation and which can be
- created using the Control Group and Namespace features included in recent Linux
- Kernels.
+Description: Linux containers userspace tools - development files
+ Containers are insulated areas inside a system, which have their own
+ namespace for memory allocation, file systems, networking, PIDs, IPC, and
+ CPUs, and which can be created using the control group and namespace
+ features included in Linux kernels.
.
- This package contains the development files.
+ This package provides the development files.
diff -ru old/lxc.templates new/lxc.templates
--- old/lxc.templates 2011-09-23 10:13:02.869960624 +0100
+++ new/lxc.templates 2011-10-02 11:47:48.213960547 +0100
@@ -9,14 +9,14 @@
Template: lxc/title
Type: title
-_Description: Linux Container (LXC)
+_Description: Linux Containers (LXC) setup
Template: lxc/auto
Type: boolean
Default: true
-_Description: Linux Container: Automatic start and stop
- Linux Containers that have their configuration files copied or symlinked
- to the /etc/lxc/auto directory can be automatically started during system
- boot and shutdown on reboot/halt.
+_Description: Automatically start Linux Containers on boot?
+ Linux Containers can be automatically started during system
+ boot and shut down on reboot or halt.
.
- If unsure, choose yes (default).
+ If you choose this option, the required symlinks will be created in
+ the /etc/lxc/auto directory.
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-english@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: lxc/title
Type: title
_Description: Linux Containers (LXC) setup
Template: lxc/auto
Type: boolean
Default: true
_Description: Automatically start Linux Containers on boot?
Linux Containers can be automatically started during system
boot and shut down on reboot or halt.
.
If you choose this option, the required symlinks will be created in
the /etc/lxc/auto directory.
Source: lxc
Section: admin
Priority: optional
Maintainer: Daniel Baumann <daniel.baumann@progress-technologies.net>
Uploaders: Jonas Genannt <jonas.genannt@capi2name.de>
Build-Depends:
debhelper (>= 8), autotools-dev, docbook-utils, libcap-dev, linux-libc-dev
Standards-Version: 3.9.2
Homepage: http://lxc.sourceforge.net/
Package: lxc
Architecture: linux-any
Depends: ${misc:Depends}, ${shlibs:Depends}
Recommends: debootstrap, libcap2-bin
Description: Linux Containers userspace tools
Containers are insulated areas inside a system, which have their own
namespace for memory allocation, file systems, networking, PIDs, IPC, and
CPUs, and which can be created using the control group and namespace
features included in Linux kernels.
.
This package provides the lxc-* tools, which can be used to start a single
daemon in a container, or to boot an entire "containerized" system, and to
succesfully manage and debug your containers.
Package: lxc-dbg
Section: debug
Priority: extra
Architecture: linux-any
Depends:
${misc:Depends}, lxc (= ${binary:Version}), lxc-dev (= ${binary:Version})
Description: Linux containers userspace tools - debug
Containers are insulated areas inside a system, which have their own
namespace for memory allocation, file systems, networking, PIDs, IPC, and
CPUs, and which can be created using the control group and namespace
features included in Linux kernels.
.
This package provides the debugging symbols for userspace tools.
Package: lxc-dev
Section: libdevel
Architecture: linux-any
Depends: ${misc:Depends}, lxc (= ${binary:Version})
Description: Linux containers userspace tools - development files
Containers are insulated areas inside a system, which have their own
namespace for memory allocation, file systems, networking, PIDs, IPC, and
CPUs, and which can be created using the control group and namespace
features included in Linux kernels.
.
This package provides the development files.
Reply to: