File: templates

package info (click to toggle)
totd 1.4-3
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 660 kB
  • ctags: 512
  • sloc: ansic: 5,840; sh: 2,826; perl: 111; makefile: 110
file content (94 lines) | stat: -rw-r--r-- 3,234 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
Template: totd/manage_with_debconf
Type: boolean
Default: true
_Description: Manage totd configuration file with debconf?
 The /etc/totd.conf file can be handled automatically by debconf, or
 manually by you.
 .
 Note that only specific, marked sections of the configuration file will be
 handled by debconf if you select this option; if those markers are absent,
 the configuration file will not be updated automatically, and you will
 have to update the file manually, or move or delete the file.

Template: totd/move_existing_nondebconf_config
Type: boolean
Default: true
_Description: Replace existing totd configuration file?
 The existing /etc/totd.conf file currently on the system does not contain
 a marked section for debconf to write its data.
 .
 If you select this option, the existing totd configuration file will be
 backed up to /etc/totd.conf.debconf-backup, and a new file written to
 /etc/totd.conf.  If you do not select this option, the existing
 configuration file will not be managed by debconf, and no further
 questions about totd configuration will be asked.

Template: totd/support_ipv6_prefix
Type: boolean
Default: false
_Description: Support mapping IPv4 address to IPv6 address?
 Totd supports IPv6 only hosts/networks that communicate with the IPv4
 world using some translation mechanism.
 .
 Translator translate map IPv4 to IPv6 connections and back in some way. In
 order for an application to connect through such a translator to the world
 beyond it needs to use fake or fabricated addresses that are routed to
 this translator. These fake addresses don't exist in the DNS.
 .
 If you select this question, all your IPv4 connections are forwarded to
 translator, so some problem can be occurred.
 .
 If unsure, leave it.

Template: totd/ipv6_prefix
Type: string
_Description: IPv6 prefix?
 Specify IPv6 prefix.
 .
 Example: 3ffe:abcd:1234:9876::

Template: totd/dns_server
Type: string
_Description: DNS Server?
 Specify a DNS server's IPv4 address or IPv6 address.
 .
 You can select multiple DNS servers, each address must be separated by
 space.
 .
 Example: 192.168.1.1 fe80::203:47ff:fe8a:13cb

Template: totd/bad_dns_server
Type: note
_Description: Invalid DNS server
 DNS server's address you enter is invalid. Please try again.
 .
 "${enteredstring}"

Template: totd/rewrite_resolv_conf
Type: boolean
Default: false
_Description: Rewrite resolv.conf?
 You can use totd as local DNS server. It is convenient for some
 applications which call res_init(3) only once. These application cannot
 search new DNS server when resolv.conf is changed by DHCP or PPP.
 .
 If unsure, leave it.

Template: totd/rewrite_dhcp_script
Type: note
_Description: Rewrite /etc/dhclient-enter-hooks
 To use totd as local DNS server, totd redefines make_resolv_conf in
 /etc/dhclient-script. This script does not rewrite /etc/resolv.conf in
 DHCP process. /etc/totd.conf will be rewrited from DHCP informations
 instead.
 .
 If you already have /etc/dhclient-enter-hooks, old file is backuped to
 /etc/dhclient-enter-hooks.totd.old

Template: totd/use_ipv6
Type: boolean
Default: false
_Description: Support IPv6?
 You can use totd under both IPv4 and IPv6. Do you want to support IPv6?
 .
 If unsure, leave it.