[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[LCFC] templates://nbd/{nbd-client.templates,nbd-server.templates}



This is the last call for comments for the review of debconf
templates for nbd.

The reviewed templates will be sent on Tuesday, May 12, 2009 to the package
maintainer as a bug report and a mail will be sent to this list with
"[BTS]" as a subject tag.


-- 


Template: nbd-client/no-auto-config
Type: error
_Description: AUTO_GEN is set to "n" in /etc/nbd-client
 The /etc/nbd-client file contains a line that sets the AUTO_GEN variable
 to "n". The file will therefore not be regenerated automatically.
 .
 If that's wrong, remove the line and call "dpkg-reconfigure nbd-client"
 afterwards.

Template: nbd-client/number
Type: string
Default: 0
_Description: Number of nbd-client connections to use:
 nbd-client can handle multiple concurrent connections. Please specify the
 number of connections you'd like this configuration script to set up.
 .
 Note that if something has already been specified in /etc/nbd-client, the
 current configuration will be used as defaults in these dialogs.

Template: nbd-client/type
Type: select
_Choices: swap, filesystem, raw
Default: raw
_Description: Intended use of the network block device number ${number}:
 The network block device can serve multiple purposes. One of the most
 interesting is to provide swap space over the network for diskless clients,
 but you can store a filesystem on it, or do other things with it for which
 a block device is interesting.
 .
 If you intend to use the network block device as a swap device, choose
 "swap". If you intend to use it as a filesystem, add a line to /etc/fstab,
 give it the option "_netdev" (else init will try to mount it before it's
 usable), and choose "filesystem". For all other purposes, choose "raw".
 The only thing the nbd-client boot script will do then is start an
 nbd-client process; you will have to set it up manually.

Template: nbd-client/host
Type: string
_Description: Hostname of the server (number: ${number})?
 Please enter the network name or IP address of the machine on which
 the nbd-server process is running.

Template: nbd-client/port
Type: string
_Description: Port on which the nbd-server is running (number: ${number})?
 Please enter the TCP port number to access nbd-server.

Template: nbd-client/device
Type: string
_Description: /dev entry for this nbd-client (number: ${number})?
 Every nbd-client process needs to be associated with a /dev entry with
 major mode 43. Please enter the name of the /dev entry you want to use for
 this nbd-client. Note that this needs to be the full path to that entry,
 not just the last part.
 .
 If the /dev entry specified does not exist, it will be created with minor
 number ${number}.

Template: nbd-client/killall
Type: boolean
Default: true
_Description: Disconnect all NBD devices on "stop"?
 When the nbd-client init script is called to stop the nbd-client service,
 there are two things that can be done: either it can disconnect all
 nbd-client devices (which are assumed not to be in use), or it can
 disconnect only those nbd-client devices that it knows about in its
 config file.
 .
 The default (and the traditional behavior) is to disconnect all
 nbd-client devices. If the root device or other critical file systems
 are on NBD this will cause data loss and should not be accepted.
Template: nbd-server/number
Type: string
Default: 0
_Description: Number of nbd-server instances to run:
 Multiple nbd-server processes may run to export multiple files or
 block devices. Please specify how many configurations for such servers you
 want to generate.
 .
 Note that you can always add extra servers by adding them to
 /etc/nbd-server/config, or by running "dpkg-reconfigure nbd-server".

Template: nbd-server/port
Type: string
_Description: TCP Port for server number ${number}:
 Please specify the TCP port this instance of nbd server will use for
 listening. As NBD is likely to use more than one port, no dedicated
 port has been assigned in IANA lists.
 .
 Therefore, NBD does not have a standard port number, which means you need
 to provide one. You should make sure this port is not already in use.

Template: nbd-server/filename
Type: string
_Description: File to export (server number ${number}):
 Please specify a file name or block device that should be exported
 over the network. You can export a real block device (for instance
 "/dev/hda1"); a normal file (such as "/export/nbd/bl1"); or a
 bunch of files all at once. For the third option, you can
 use "%s" in the filename, which will be expanded to the
 IP-address of the connecting client. An example would be
 "/export/swaps/swp%s".
 .
 Note that it is possible to tune the way in which the IP address will
 be substituted in the file name. See "man 5 nbd-server" for details.

Template: nbd-server/autogen
Type: error
_Description: AUTO_GEN is set to "n" in /etc/nbd-server
 The /etc/nbd-server file contains a line that sets the AUTO_GEN variable
 to "n". The file will therefore not be regenerated automatically.
 .
 Note that the current version of the nbd-server package no longer uses
 /etc/nbd-server. Instead it uses a new configuration file, read by
 nbd-server itself (rather than the init script), which supports more
 options. See "man 5 nbd-server" for details.
 .
 If you remove or comment out the AUTO_GEN line, a file
 /etc/nbd-server/config in the new format may be generated based on the
 current configuration. Until then, the nbd-server installation will be
 broken.

Template: nbd-server/convert
Type: boolean
Default: true
_Description: Convert old-style nbd-server configuration file?
 A pre-2.9 nbd-server configuration file has been found on this system.
 The current nbd-server package no longer supports this file and will
 not work if it is kept as is.
 .
 If you choose this
 option, the system will generate a new style configuration file based
 upon the old-style configuration file, which will be removed. Otherwise,
 configuration questions will be asked and the system will generate a new configuration file.
 .
 If a new-style configuration file already exists and you choose this
 option, you will shortly see a "modified configuration file" prompt, as
 usual.
Source: nbd
Section: admin
Priority: optional
Maintainer: Wouter Verhelst <wouter@debian.org>
Build-Depends: debhelper (>> 4.1.16), libglib2.0-dev
Standards-Version: 3.8.0

Package: nbd-server
Architecture: any
Depends: ${shlibs:Depends}, debconf (>= 1.2.9) | debconf-2.0, ucf, adduser, ${misc:Depends}
Description: Network Block Device protocol - server
 Network Block Device (NBD) is a client/server protocol that
 emulates a block device (such as a hard disk, a floppy, or a CD-ROM)
 over the network, thus giving the system the ability to swap over the
 network, or to use raw network disk space for other purposes.
 .
 However, writing to one Network Block Device from different clients
 simultaneously is not recommended, and would probably result in data
 loss. If you want multiple clients to share a remote resource, use a
 network file system such as NFS or Coda.
 .
 This package provides the server binary for NBD.

Package: nbd-client
Architecture: alpha amd64 arm armeb armel hppa i386 ia64 lpia m32r m68k mips mipsel powerpc ppc64 s390 sh3 sh3eb sh4 sh4eb sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf | debconf-2.0
Description: Network Block Device protocol - client
 Network Block Device (NBD) is a client/server protocol that
 emulates a block device (such as a hard disk, a floppy, or a CD-ROM)
 over the network, thus giving the system the ability to swap over the
 network, or to use raw network disk space for other purposes.
 .
 However, writing to one Network Block Device from different clients
 simultaneously is not recommended, and would probably result in data
 loss. If you want multiple clients to share a remote resource, use a
 network file system such as NFS or Coda.
 .
 This package provides the client binary for NBD.

Package: nbd-client-udeb
Section: debian-installer
Priority: optional
Depends: ${shlibs:Depends}
XC-Package-Type: udeb
Architecture: alpha amd64 arm armeb armel hppa i386 ia64 lpia m32r m68k mips mipsel powerpc ppc64 s390 sh3 sh3eb sh4 sh4eb sparc
Description: Network Block Device protocol - client for Debian Installer
 Network Block Device (NBD) is a client/server protocol that
 emulates a block device (such as a hard disk, a floppy, or a CD-ROM)
 over the network, thus giving the system the ability to swap over the
 network, or to use raw network disks pace for other purposes.
 .
 This package provides the client binary for NBD.
 .
 It is a minimal version meant for use in the installer only.

Attachment: signature.asc
Description: Digital signature


Reply to: