Attachment #237246 for bug #267002

View | Details | Raw Unified | Return to bug 267002
Collapse All | Expand All





Et cetera, et cetera, et cetera.

Secondly, I like the `+#+` character to denote the start of a comment which extends to the end of the line.
This does not take too much effort to code, and lets me treat input files for my software as executable scripts.

In our case, we also need to decide what units the input should come in: We choose _millimeters_ because that is how most photographers measure the focus length.

* If the counter grows above 18, we stop appending to the buffer. We continue reading the digits and sending them to the output.
* If, or rather _when_, the next input character is not a digit, we are done inputting for now.
+
Incidentally, we can simply discard the non-digit, unless it is a `+#+`, which we must return to the input stream.
It starts a comment, so we must see it after we are done producing output and start looking for more input.

That still leaves one possibility uncovered: If all the user enters is a zero (or several zeros), we will never find a non-zero to display.

[[x86-pinhole-scripting]]
=== Scripting

Because we have chosen the `+#+` character to denote the start of a comment, we can treat our pinhole software as a _scripting language_.

You have probably seen shell _scripts_ that start with:





#. type: Plain text
#: documentation/content/en/books/developers-handbook/x86/_index.adoc:2903
msgid ""
"Secondly, I like the `+#+` character to denote the start of a comment which "
"extends to the end of the line.  This does not take too much effort to code, "
"and lets me treat input files for my software as executable scripts."
msgstr ""

#. type: Plain text
#: documentation/content/en/books/developers-handbook/x86/_index.adoc:3068
msgid ""
"Incidentally, we can simply discard the non-digit, unless it is a `+#+`, which "
"we must return to the input stream.  It starts a comment, so we must see it "
"after we are done producing output and start looking for more input."
msgstr ""

#. type: Plain text
#: documentation/content/en/books/developers-handbook/x86/_index.adoc:4111
msgid ""
"Because we have chosen the `+#+` character to denote the start of a comment, "
"we can treat our pinhole software as a _scripting language_."
msgstr ""


Lines 2131-2137 For example, to read the input from four network interfaces as one stream: Link Here

(-)b/documentation/content/en/books/handbook/advanced-networking/_index.adoc (-2 / +2 lines)
2131	The bridge interface and STP parameters can be monitored via man:bsnmpd[1] which is included in the FreeBSD base system.	2131	The bridge interface and STP parameters can be monitored via man:bsnmpd[1] which is included in the FreeBSD base system.
2132	The exported bridge MIBs conform to IETF standards so any SNMP client or monitoring package can be used to retrieve the data.	2132	The exported bridge MIBs conform to IETF standards so any SNMP client or monitoring package can be used to retrieve the data.
2133		2133
2134	To enable monitoring on the bridge, uncomment this line in [.filename]#/etc/snmpd.config# by removing the beginning `#` symbol:	2134	To enable monitoring on the bridge, uncomment this line in [.filename]#/etc/snmpd.config# by removing the beginning `+#+` symbol:
2135		2135
2136	[.programlisting]	2136	[.programlisting]
2137	....	2137	....
Lines 2581-2587 nfs_server_enable="YES" Link Here
2581	inetd_enable="YES"	2581	inetd_enable="YES"
2582	....	2582	....
2583		2583
2584	. Uncomment the following line in [.filename]#/etc/inetd.conf# by making sure it does not start with a `#` symbol:	2584	. Uncomment the following line in [.filename]#/etc/inetd.conf# by making sure it does not start with a `+#+` symbol:
2585	+	2585	+
2586	[.programlisting]	2586	[.programlisting]
2587	....	2587	....

Lines 4153-4159 msgstr "" Link Here

(-)b/documentation/content/en/books/handbook/advanced-networking/_index.po (-2 / +2 lines)
4153	#: documentation/content/en/books/handbook/advanced-networking/_index.adoc:2135	4153	#: documentation/content/en/books/handbook/advanced-networking/_index.adoc:2135
4154	msgid ""	4154	msgid ""
4155	"To enable monitoring on the bridge, uncomment this line in [.filename]#/etc/"	4155	"To enable monitoring on the bridge, uncomment this line in [.filename]#/etc/"
4156	"snmpd.config# by removing the beginning `#` symbol:"	4156	"snmpd.config# by removing the beginning `+#+` symbol:"
4157	msgstr ""	4157	msgstr ""
4158		4158
4159	#. type: delimited block . 4	4159	#. type: delimited block . 4
Lines 4956-4962 msgstr "" Link Here
4956	#: documentation/content/en/books/handbook/advanced-networking/_index.adoc:2585	4956	#: documentation/content/en/books/handbook/advanced-networking/_index.adoc:2585
4957	msgid ""	4957	msgid ""
4958	"Uncomment the following line in [.filename]#/etc/inetd.conf# by making sure "	4958	"Uncomment the following line in [.filename]#/etc/inetd.conf# by making sure "
4959	"it does not start with a `#` symbol:"	4959	"it does not start with a `+#+` symbol:"
4960	msgstr ""	4960	msgstr ""
4961		4961
4962	#. type: delimited block . 4	4962	#. type: delimited block . 4

Lines 96-102 Then enter the password associated with the username and press kbd:[Enter]. Link Here

(-)b/documentation/content/en/books/handbook/basics/_index.adoc (-3 / +3 lines)
96	The password is _not echoed_ for security reasons.	96	The password is _not echoed_ for security reasons.
97		97
98	Once the correct password is input, the message of the day (MOTD) will be displayed followed by a command prompt.	98	Once the correct password is input, the message of the day (MOTD) will be displayed followed by a command prompt.
99	Depending upon the shell that was selected when the user was created, this prompt will be a `#`, `$`, or `%` character.	99	Depending upon the shell that was selected when the user was created, this prompt will be a `+#+`, `$`, or `%` character.
100	The prompt indicates that the user is now logged into the FreeBSD system console and ready to try the available commands.	100	The prompt indicates that the user is now logged into the FreeBSD system console and ready to try the available commands.
101		101
102	[[consoles-virtual]]	102	[[consoles-virtual]]
Lines 138-145 ttyv7 "/usr/libexec/getty Pc" xterm on secure Link Here
138	ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure	138	ttyv8 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure
139	....	139	....
140		140
141	To disable a virtual console, put a comment symbol (`\#`) at the beginning of the line representing that virtual console.	141	To disable a virtual console, put a comment symbol (`+#+`) at the beginning of the line representing that virtual console.
142	For example, to reduce the number of available virtual consoles from eight to four, put a `#` in front of the last four lines representing virtual consoles [.filename]#ttyv5# through [.filename]#ttyv8#.	142	For example, to reduce the number of available virtual consoles from eight to four, put a `+#+` in front of the last four lines representing virtual consoles [.filename]#ttyv5# through [.filename]#ttyv8#.
143	_Do not_ comment out the line for the system console [.filename]#ttyv0#.	143	_Do not_ comment out the line for the system console [.filename]#ttyv0#.
144	Note that the last virtual console ([.filename]#ttyv8#) is used to access the graphical environment if Xorg has been installed and configured as described in crossref:x11[x11,The X Window System].	144	Note that the last virtual console ([.filename]#ttyv8#) is used to access the graphical environment if Xorg has been installed and configured as described in crossref:x11[x11,The X Window System].
145		145

Lines 168-174 PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <.> Link Here

(-)b/documentation/content/en/books/handbook/config/_index.adoc (-1 / +1 lines)
168	/5 * * * root /usr/libexec/atrun <.>	168	/5 * * * root /usr/libexec/atrun <.>
169	....	169	....
170		170
171	<.> Lines that begin with the `#` character are comments. A comment can be placed in the file as a reminder of what and why a desired action is performed. Comments cannot be on the same line as a command or else they will be interpreted as part of the command; they must be on a new line. Blank lines are ignored.	171	<.> Lines that begin with the `+#+` character are comments. A comment can be placed in the file as a reminder of what and why a desired action is performed. Comments cannot be on the same line as a command or else they will be interpreted as part of the command; they must be on a new line. Blank lines are ignored.
172		172
173	<.> The equals (`=`) character is used to define any environment settings. In this example, it is used to define the `SHELL` and `PATH`. If the `SHELL` is omitted, cron will use the default Bourne shell. If the `PATH` is omitted, the full path must be given to the command or script to run.	173	<.> The equals (`=`) character is used to define any environment settings. In this example, it is used to define the `SHELL` and `PATH`. If the `SHELL` is omitted, cron will use the default Bourne shell. If the `PATH` is omitted, the full path must be given to the command or script to run.
174		174

Lines 329-335 msgstr "" Link Here

(-)b/documentation/content/en/books/handbook/config/_index.po (-1 / +1 lines)
329	#. type: Plain text	329	#. type: Plain text
330	#: documentation/content/en/books/handbook/config/_index.adoc:172	330	#: documentation/content/en/books/handbook/config/_index.adoc:172
331	msgid ""	331	msgid ""
332	"Lines that begin with the `#` character are comments. A comment can be "	332	"Lines that begin with the `+#+` character are comments. A comment can be "
333	"placed in the file as a reminder of what and why a desired action is "	333	"placed in the file as a reminder of what and why a desired action is "
334	"performed. Comments cannot be on the same line as a command or else they "	334	"performed. Comments cannot be on the same line as a command or else they "
335	"will be interpreted as part of the command; they must be on a new line. "	335	"will be interpreted as part of the command; they must be on a new line. "

Lines 1775-1781 The asterisk `*` indicates that the user is currently over the quota limit. Link Here

(-)b/documentation/content/en/books/handbook/disks/_index.adoc (-1 / +1 lines)
1775	Quotas are enforced by the quota subsystem on the NFS server.	1775	Quotas are enforced by the quota subsystem on the NFS server.
1776	The man:rpc.rquotad[8] daemon makes quota information available to `quota` on NFS clients, allowing users on those machines to see their quota statistics.	1776	The man:rpc.rquotad[8] daemon makes quota information available to `quota` on NFS clients, allowing users on those machines to see their quota statistics.
1777		1777
1778	On the NFS server, enable `rpc.rquotad` by removing the `#` from this line in [.filename]/etc/inetd.conf:	1778	On the NFS server, enable `rpc.rquotad` by removing the `+#+` from this line in [.filename]/etc/inetd.conf:
1779		1779
1780	[.programlisting]	1780	[.programlisting]
1781	....	1781	....

Lines 3387-3393 msgstr "" Link Here

(-)b/documentation/content/en/books/handbook/disks/_index.po (-1 / +1 lines)
3387	#. type: Plain text	3387	#. type: Plain text
3388	#: documentation/content/en/books/handbook/disks/_index.adoc:1779	3388	#: documentation/content/en/books/handbook/disks/_index.adoc:1779
3389	msgid ""	3389	msgid ""
3390	"On the NFS server, enable `rpc.rquotad` by removing the `#` from this line "	3390	"On the NFS server, enable `rpc.rquotad` by removing the `+#+` from this line "
3391	"in [.filename]/etc/inetd.conf:"	3391	"in [.filename]/etc/inetd.conf:"
3392	msgstr ""	3392	msgstr ""
3393		3393




The installation of package:mail/spamd[] includes a sample configuration file ([.filename]#/usr/local/etc/spamd.conf.sample#) and a man page for [.filename]#spamd.conf#.
Refer to these for additional configuration options beyond those shown in this example.
+
One of the first lines in the configuration file that does not begin with a `+#+` comment sign contains the block which defines the `all` list, which specifies the lists to use:
+
[.programlisting]
....

When creating an IPFW rule, keywords must be written in the following order.
Some keywords are mandatory while other keywords are optional.
The words shown in uppercase represent a variable and the words shown in lowercase must precede the variable that follows it.
The `+#+` symbol is used to mark the start of a comment and may appear at the end of a rule or on its own line.
Blank lines are ignored.

`_CMD RULE_NUMBER set SET_NUMBER ACTION log LOG_AMOUNT PROTO from SRC SRC_PORT to DST DST_PORT OPTIONS_`

This means that even if the first rule to match a packet is a `pass`, if there is a later matching rule that is a `block`, the packet will be dropped.
Sample rulesets can be found in [.filename]#/usr/share/examples/ipfilter#.

When creating rules, a `+#+` character is used to mark the start of a comment and may appear at the end of a rule, to explain that rule's function, or on its own line.
Any blank lines are ignored.

The keywords which are used in rules must be written in a specific order, from left to right.




#: documentation/content/en/books/handbook/firewalls/_index.adoc:855
msgid ""
"One of the first lines in the configuration file that does not begin with a "
"`+#+` comment sign contains the block which defines the `all` list, which "
"specifies the lists to use:"
msgstr ""


"When creating an IPFW rule, keywords must be written in the following "
"order.  Some keywords are mandatory while other keywords are optional.  The "
"words shown in uppercase represent a variable and the words shown in "
"lowercase must precede the variable that follows it.  The `+#+` symbol is used "
"to mark the start of a comment and may appear at the end of a rule or on its "
"own line.  Blank lines are ignored."
msgstr ""

#. type: Plain text
#: documentation/content/en/books/handbook/firewalls/_index.adoc:1929
msgid ""
"When creating rules, a `+#+` character is used to mark the start of a comment "
"and may appear at the end of a rule, to explain that rule's function, or on "
"its own line.  Any blank lines are ignored."
msgstr ""

Lines 195-203 The default editor is vi, though an easier editor for beginners, called ee, is a Link Here

(-)b/documentation/content/en/books/handbook/kernelconfig/_index.adoc (-3 / +3 lines)
195		195
196	The format of the kernel configuration file is simple.	196	The format of the kernel configuration file is simple.
197	Each line contains a keyword that represents a device or subsystem, an argument, and a brief description.	197	Each line contains a keyword that represents a device or subsystem, an argument, and a brief description.
198	Any text after a `#` is considered a comment and ignored.	198	Any text after a `+#+` is considered a comment and ignored.
199	To remove kernel support for a device or subsystem, put a `#` at the beginning of the line representing that device or subsystem.	199	To remove kernel support for a device or subsystem, put a `+#+` at the beginning of the line representing that device or subsystem.
200	Do not add or remove a `#` for any line that you do not understand.	200	Do not add or remove a `+#+` for any line that you do not understand.
201		201
202	[WARNING]	202	[WARNING]
203	====	203	====

Lines 386-395 msgstr "" Link Here

(-)b/documentation/content/en/books/handbook/kernelconfig/_index.po (-3 / +3 lines)
386	msgid ""	386	msgid ""
387	"The format of the kernel configuration file is simple. Each line contains a "	387	"The format of the kernel configuration file is simple. Each line contains a "
388	"keyword that represents a device or subsystem, an argument, and a brief "	388	"keyword that represents a device or subsystem, an argument, and a brief "
389	"description. Any text after a `#` is considered a comment and ignored. To "	389	"description. Any text after a `+#+` is considered a comment and ignored. To "
390	"remove kernel support for a device or subsystem, put a `#` at the beginning "	390	"remove kernel support for a device or subsystem, put a `+#+` at the beginning "
391	"of the line representing that device or subsystem. Do not add or remove a "	391	"of the line representing that device or subsystem. Do not add or remove a "
392	"`#` for any line that you do not understand."	392	"`+#+` for any line that you do not understand."
393	msgstr ""	393	msgstr ""
394		394
395	#. type: delimited block = 4	395	#. type: delimited block = 4

Lines 175-181 Examples of using these options for both IPv4 and IPv6 addresses can be found in Link Here

(-)b/documentation/content/en/books/handbook/mail/_index.adoc (-1 / +1 lines)
175	#Connect:[IPv6:1:2:3:4:5:6:7:8] OK	175	#Connect:[IPv6:1:2:3:4:5:6:7:8] OK
176	....	176	....
177	+	177	+
178	To configure the access database, use the format shown in the sample to make entries in [.filename]#/etc/mail/access#, but do not put a comment symbol (`#`) in front of the entries.	178	To configure the access database, use the format shown in the sample to make entries in [.filename]#/etc/mail/access#, but do not put a comment symbol (`+#+`) in front of the entries.
179	Create an entry for each host or network whose access should be configured.	179	Create an entry for each host or network whose access should be configured.
180	Mail senders that match the left side of the table are affected by the action on the right side of the table.	180	Mail senders that match the left side of the table are affected by the action on the right side of the table.
181	+	181	+

Lines 380-386 msgstr "" Link Here

(-)b/documentation/content/en/books/handbook/mail/_index.po (-1 / +1 lines)
380	msgid ""	380	msgid ""
381	"To configure the access database, use the format shown in the sample to make "	381	"To configure the access database, use the format shown in the sample to make "
382	"entries in [.filename]#/etc/mail/access#, but do not put a comment symbol "	382	"entries in [.filename]#/etc/mail/access#, but do not put a comment symbol "
383	"(`#`) in front of the entries. Create an entry for each host or network "	383	"(`+#+`) in front of the entries. Create an entry for each host or network "
384	"whose access should be configured. Mail senders that match the left side of "	384	"whose access should be configured. Mail senders that match the left side of "
385	"the table are affected by the action on the right side of the table."	385	"the table are affected by the action on the right side of the table."
386	msgstr ""	386	msgstr ""





Configuration of inetd is done by editing [.filename]#/etc/inetd.conf#.
Each line of this configuration file represents an application which can be started by inetd.
By default, every line starts with a comment (`+#+`), meaning that inetd is not listening for any applications.
To configure inetd to listen for an application's connections, remove the `+#+` at the beginning of the line for that application.

After saving your edits, configure inetd to start at system boot by editing [.filename]#/etc/rc.conf#:



====

Typically, the default entry for an application does not need to be edited beyond removing the `+#+`.
In some situations, it may be appropriate to edit the default entry.

As an example, this is the default entry for man:ftpd[8] over IPv4:


This will create [.filename]#/var/yp/Makefile# from [.filename]#/var/yp/Makefile.dist#.
By default, this file assumes that the environment has a single NIS server with only FreeBSD clients.
Since `test-domain` has a slave server, edit this line in [.filename]#/var/yp/Makefile# so that it begins with a comment (`+#+`):

[.programlisting]
....

To prevent unauthorized transactions, man:ypserv[8] supports a feature called "securenets" which can be used to restrict access to a given set of hosts.
By default, this information is stored in [.filename]#/var/yp/securenets#, unless man:ypserv[8] is started with `-p` and an alternate path.
This file contains entries that consist of a network specification and a network mask separated by white space.
Lines starting with `+#+` are considered to be comments.
A sample [.filename]#securenets# might look like this:

[.programlisting]

=== Configuring and Starting Apache

In FreeBSD, the main Apache HTTP Server configuration file is installed as [.filename]#/usr/local/etc/apache2x/httpd.conf#, where _x_ represents the version number.
This ASCII text file begins comment lines with a `+#+`.
The most frequently modified directives are:

`ServerRoot "/usr/local"`::




msgid ""
"Configuration of inetd is done by editing [.filename]#/etc/inetd.conf#.  "
"Each line of this configuration file represents an application which can be "
"started by inetd.  By default, every line starts with a comment (`+#+`), "
"meaning that inetd is not listening for any applications.  To configure "
"inetd to listen for an application's connections, remove the `+#+` at the "
"beginning of the line for that application."
msgstr ""


#: documentation/content/en/books/handbook/network-servers/_index.adoc:129
msgid ""
"Typically, the default entry for an application does not need to be edited "
"beyond removing the `+#+`.  In some situations, it may be appropriate to edit "
"the default entry."
msgstr ""


"Makefile.dist#.  By default, this file assumes that the environment has a "
"single NIS server with only FreeBSD clients.  Since `test-domain` has a "
"slave server, edit this line in [.filename]#/var/yp/Makefile# so that it "
"begins with a comment (`+#+`):"
msgstr ""

#. type: delimited block . 4

"hosts.  By default, this information is stored in [.filename]#/var/yp/"
"securenets#, unless man:ypserv[8] is started with `-p` and an alternate "
"path.  This file contains entries that consist of a network specification "
"and a network mask separated by white space.  Lines starting with `+#+` are "
"considered to be comments.  A sample [.filename]#securenets# might look like "
"this:"
msgstr ""

msgid ""
"In FreeBSD, the main Apache HTTP Server configuration file is installed as [."
"filename]#/usr/local/etc/apache2x/httpd.conf#, where _x_ represents the "
"version number.  This ASCII text file begins comment lines with a `+#+`.  The "
"most frequently modified directives are:"
msgstr ""


Lines 166-172 Sets the idle timeout for the link in seconds. Link Here

(-)b/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc (-1 / +1 lines)
166		166
167	Line 9:::	167	Line 9:::
168	Instructs the peer to confirm the DNS settings.	168	Instructs the peer to confirm the DNS settings.
169	If the local network is running its own DNS server, this line should be commented out, by adding a `#` at the beginning of the line, or removed.	169	If the local network is running its own DNS server, this line should be commented out, by adding a `+#+` at the beginning of the line, or removed.
170		170
171	Line 10:::	171	Line 10:::
172	A blank line for readability. Blank lines are ignored by man:ppp[8].	172	A blank line for readability. Blank lines are ignored by man:ppp[8].

Lines 350-356 msgstr "" Link Here

(-)b/documentation/content/en/books/handbook/ppp-and-slip/_index.po (-1 / +1 lines)
350	msgid ""	350	msgid ""
351	"Instructs the peer to confirm the DNS settings. If the local network is "	351	"Instructs the peer to confirm the DNS settings. If the local network is "
352	"running its own DNS server, this line should be commented out, by adding a "	352	"running its own DNS server, this line should be commented out, by adding a "
353	"`#` at the beginning of the line, or removed."	353	"`+#+` at the beginning of the line, or removed."
354	msgstr ""	354	msgstr ""
355		355
356	#. type: Labeled list	356	#. type: Labeled list

Lines 277-283 The `default` login class contains an example: Link Here

(-)b/documentation/content/en/books/handbook/security/_index.adoc (-1 / +1 lines)
277	# :passwordtime=90d:\	277	# :passwordtime=90d:\
278	....	278	....
279		279
280	So, to set an expiry of 90 days for this login class, remove the comment symbol (`#`), save the edit, and run `cap_mkdb /etc/login.conf`.	280	So, to set an expiry of 90 days for this login class, remove the comment symbol (`+#+`), save the edit, and run `cap_mkdb /etc/login.conf`.
281		281
282	To set the expiration on individual users, pass an expiration date or the number of days to expiry and a username to `pw`:	282	To set the expiration on individual users, pass an expiration date or the number of days to expiry and a username to `pw`:
283		283

Lines 547-553 msgstr "" Link Here

(-)b/documentation/content/en/books/handbook/security/_index.po (-1 / +1 lines)
547	#: documentation/content/en/books/handbook/security/_index.adoc:281	547	#: documentation/content/en/books/handbook/security/_index.adoc:281
548	msgid ""	548	msgid ""
549	"So, to set an expiry of 90 days for this login class, remove the comment "	549	"So, to set an expiry of 90 days for this login class, remove the comment "
550	"symbol (`#`), save the edit, and run `cap_mkdb /etc/login.conf`."	550	"symbol (`+#+`), save the edit, and run `cap_mkdb /etc/login.conf`."
551	msgstr ""	551	msgstr ""
552		552
553	#. type: Plain text	553	#. type: Plain text

Lines 1100-1106 freebsd 1 1024 1 -b---- 663.9 Link Here

(-)b/documentation/content/en/books/handbook/virtualization/_index.adoc (-1 / +1 lines)
1100		1100
1101	To begin the installation of the base operating system, start the VNC client, directing it to the main network address of the host or to the IP address defined on the `vnclisten` line of [.filename]#freebsd.cfg#.	1101	To begin the installation of the base operating system, start the VNC client, directing it to the main network address of the host or to the IP address defined on the `vnclisten` line of [.filename]#freebsd.cfg#.
1102	After the operating system has been installed, shut down the DomU and disconnect the VNC viewer.	1102	After the operating system has been installed, shut down the DomU and disconnect the VNC viewer.
1103	Edit [.filename]#freebsd.cfg#, removing the line with the `cdrom` definition or commenting it out by inserting a `#` character at the beginning of the line.	1103	Edit [.filename]#freebsd.cfg#, removing the line with the `cdrom` definition or commenting it out by inserting a `+#+` character at the beginning of the line.
1104	To load this new configuration, it is necessary to remove the old DomU with `xl destroy`, passing either the name or the id as the parameter.	1104	To load this new configuration, it is necessary to remove the old DomU with `xl destroy`, passing either the name or the id as the parameter.
1105	Afterwards, recreate it using the modified [.filename]freebsd.cfg.	1105	Afterwards, recreate it using the modified [.filename]freebsd.cfg.
1106		1106

Lines 2143-2149 msgid "" Link Here

(-)b/documentation/content/en/books/handbook/virtualization/_index.po (-1 / +1 lines)
2143	"address defined on the `vnclisten` line of [.filename]#freebsd.cfg#. After "	2143	"address defined on the `vnclisten` line of [.filename]#freebsd.cfg#. After "
2144	"the operating system has been installed, shut down the DomU and disconnect "	2144	"the operating system has been installed, shut down the DomU and disconnect "
2145	"the VNC viewer. Edit [.filename]#freebsd.cfg#, removing the line with the "	2145	"the VNC viewer. Edit [.filename]#freebsd.cfg#, removing the line with the "
2146	"`cdrom` definition or commenting it out by inserting a `#` character at the "	2146	"`cdrom` definition or commenting it out by inserting a `+#+` character at the "
2147	"beginning of the line. To load this new configuration, it is necessary to "	2147	"beginning of the line. To load this new configuration, it is necessary to "
2148	"remove the old DomU with `xl destroy`, passing either the name or the id as "	2148	"remove the old DomU with `xl destroy`, passing either the name or the id as "
2149	"the parameter. Afterwards, recreate it using the modified [."	2149	"the parameter. Afterwards, recreate it using the modified [."

Return to bug 267002

Lines 5408-5414 msgstr "" Link Here

(-)b/documentation/content/en/books/developers-handbook/x86/_index.po (-3 / +3 lines)
5408	#. type: Plain text	5408	#. type: Plain text
5409	#: documentation/content/en/books/developers-handbook/x86/_index.adoc:2903	5409	#: documentation/content/en/books/developers-handbook/x86/_index.adoc:2903
5410	msgid ""	5410	msgid ""
5411	"Secondly, I like the `#` character to denote the start of a comment which "	5411	"Secondly, I like the `+#+` character to denote the start of a comment which "
5412	"extends to the end of the line. This does not take too much effort to code, "	5412	"extends to the end of the line. This does not take too much effort to code, "
5413	"and lets me treat input files for my software as executable scripts."	5413	"and lets me treat input files for my software as executable scripts."
5414	msgstr ""	5414	msgstr ""
Lines 5834-5840 msgstr "" Link Here
5834	#. type: Plain text	5834	#. type: Plain text
5835	#: documentation/content/en/books/developers-handbook/x86/_index.adoc:3068	5835	#: documentation/content/en/books/developers-handbook/x86/_index.adoc:3068
5836	msgid ""	5836	msgid ""
5837	"Incidentally, we can simply discard the non-digit, unless it is a `#`, which "	5837	"Incidentally, we can simply discard the non-digit, unless it is a `+#+`, which "
5838	"we must return to the input stream. It starts a comment, so we must see it "	5838	"we must return to the input stream. It starts a comment, so we must see it "
5839	"after we are done producing output and start looking for more input."	5839	"after we are done producing output and start looking for more input."
5840	msgstr ""	5840	msgstr ""
Lines 7700-7706 msgstr "" Link Here
7700	#. type: Plain text	7700	#. type: Plain text
7701	#: documentation/content/en/books/developers-handbook/x86/_index.adoc:4111	7701	#: documentation/content/en/books/developers-handbook/x86/_index.adoc:4111
7702	msgid ""	7702	msgid ""
7703	"Because we have chosen the `#` character to denote the start of a comment, "	7703	"Because we have chosen the `+#+` character to denote the start of a comment, "
7704	"we can treat our pinhole software as a _scripting language_."	7704	"we can treat our pinhole software as a _scripting language_."
7705	msgstr ""	7705	msgstr ""
7706		7706

Lines 1719-1725 msgstr "" Link Here

(-)b/documentation/content/en/books/handbook/firewalls/_index.po (-3 / +3 lines)
1719	#: documentation/content/en/books/handbook/firewalls/_index.adoc:855	1719	#: documentation/content/en/books/handbook/firewalls/_index.adoc:855
1720	msgid ""	1720	msgid ""
1721	"One of the first lines in the configuration file that does not begin with a "	1721	"One of the first lines in the configuration file that does not begin with a "
1722	"`#` comment sign contains the block which defines the `all` list, which "	1722	"`+#+` comment sign contains the block which defines the `all` list, which "
1723	"specifies the lists to use:"	1723	"specifies the lists to use:"
1724	msgstr ""	1724	msgstr ""
1725		1725
Lines 2428-2434 msgid "" Link Here
2428	"When creating an IPFW rule, keywords must be written in the following "	2428	"When creating an IPFW rule, keywords must be written in the following "
2429	"order. Some keywords are mandatory while other keywords are optional. The "	2429	"order. Some keywords are mandatory while other keywords are optional. The "
2430	"words shown in uppercase represent a variable and the words shown in "	2430	"words shown in uppercase represent a variable and the words shown in "
2431	"lowercase must precede the variable that follows it. The `#` symbol is used "	2431	"lowercase must precede the variable that follows it. The `+#+` symbol is used "
2432	"to mark the start of a comment and may appear at the end of a rule or on its "	2432	"to mark the start of a comment and may appear at the end of a rule or on its "
2433	"own line. Blank lines are ignored."	2433	"own line. Blank lines are ignored."
2434	msgstr ""	2434	msgstr ""
Lines 3982-3988 msgstr "" Link Here
3982	#. type: Plain text	3982	#. type: Plain text
3983	#: documentation/content/en/books/handbook/firewalls/_index.adoc:1929	3983	#: documentation/content/en/books/handbook/firewalls/_index.adoc:1929
3984	msgid ""	3984	msgid ""
3985	"When creating rules, a `#` character is used to mark the start of a comment "	3985	"When creating rules, a `+#+` character is used to mark the start of a comment "
3986	"and may appear at the end of a rule, to explain that rule's function, or on "	3986	"and may appear at the end of a rule, to explain that rule's function, or on "
3987	"its own line. Any blank lines are ignored."	3987	"its own line. Any blank lines are ignored."
3988	msgstr ""	3988	msgstr ""

Lines 2898-2904 Syntax error: best Link Here

(-)b/documentation/content/en/books/developers-handbook/x86/_index.adoc (-3 / +3 lines)
2898		2898
2899	Et cetera, et cetera, et cetera.	2899	Et cetera, et cetera, et cetera.
2900		2900
2901	Secondly, I like the `#` character to denote the start of a comment which extends to the end of the line.	2901	Secondly, I like the `+#+` character to denote the start of a comment which extends to the end of the line.
2902	This does not take too much effort to code, and lets me treat input files for my software as executable scripts.	2902	This does not take too much effort to code, and lets me treat input files for my software as executable scripts.
2903		2903
2904	In our case, we also need to decide what units the input should come in: We choose _millimeters_ because that is how most photographers measure the focus length.	2904	In our case, we also need to decide what units the input should come in: We choose _millimeters_ because that is how most photographers measure the focus length.
Lines 3063-3069 Now, while we are taking these three steps, we also need to watch out for one of Link Here
3063	* If the counter grows above 18, we stop appending to the buffer. We continue reading the digits and sending them to the output.	3063	* If the counter grows above 18, we stop appending to the buffer. We continue reading the digits and sending them to the output.
3064	* If, or rather _when_, the next input character is not a digit, we are done inputting for now.	3064	* If, or rather _when_, the next input character is not a digit, we are done inputting for now.
3065	+	3065	+
3066	Incidentally, we can simply discard the non-digit, unless it is a `#`, which we must return to the input stream.	3066	Incidentally, we can simply discard the non-digit, unless it is a `+#+`, which we must return to the input stream.
3067	It starts a comment, so we must see it after we are done producing output and start looking for more input.	3067	It starts a comment, so we must see it after we are done producing output and start looking for more input.
3068		3068
3069	That still leaves one possibility uncovered: If all the user enters is a zero (or several zeros), we will never find a non-zero to display.	3069	That still leaves one possibility uncovered: If all the user enters is a zero (or several zeros), we will never find a non-zero to display.
Lines 4107-4113 We have found that while for the focal length of 150, our pinhole diameter shoul Link Here
4107	[[x86-pinhole-scripting]]	4107	[[x86-pinhole-scripting]]
4108	=== Scripting	4108	=== Scripting
4109		4109
4110	Because we have chosen the `#` character to denote the start of a comment, we can treat our pinhole software as a _scripting language_.	4110	Because we have chosen the `+#+` character to denote the start of a comment, we can treat our pinhole software as a _scripting language_.
4111		4111
4112	You have probably seen shell _scripts_ that start with:	4112	You have probably seen shell _scripts_ that start with:
4113		4113

Lines 851-857 SMTP traffic from an address listed in `<spamd>` but not in `<spamd-white>` is r Link Here

(-)b/documentation/content/en/books/handbook/firewalls/_index.adoc (-3 / +3 lines)
851	The installation of package:mail/spamd[] includes a sample configuration file ([.filename]#/usr/local/etc/spamd.conf.sample#) and a man page for [.filename]#spamd.conf#.	851	The installation of package:mail/spamd[] includes a sample configuration file ([.filename]#/usr/local/etc/spamd.conf.sample#) and a man page for [.filename]#spamd.conf#.
852	Refer to these for additional configuration options beyond those shown in this example.	852	Refer to these for additional configuration options beyond those shown in this example.
853	+	853	+
854	One of the first lines in the configuration file that does not begin with a `#` comment sign contains the block which defines the `all` list, which specifies the lists to use:	854	One of the first lines in the configuration file that does not begin with a `+#+` comment sign contains the block which defines the `all` list, which specifies the lists to use:
855	+	855	+
856	[.programlisting]	856	[.programlisting]
857	....	857	....
Lines 1170-1176 Refer to man:ipfw[8] for details on how these keywords affect rule processing. Link Here
1170	When creating an IPFW rule, keywords must be written in the following order.	1170	When creating an IPFW rule, keywords must be written in the following order.
1171	Some keywords are mandatory while other keywords are optional.	1171	Some keywords are mandatory while other keywords are optional.
1172	The words shown in uppercase represent a variable and the words shown in lowercase must precede the variable that follows it.	1172	The words shown in uppercase represent a variable and the words shown in lowercase must precede the variable that follows it.
1173	The `#` symbol is used to mark the start of a comment and may appear at the end of a rule or on its own line.	1173	The `+#+` symbol is used to mark the start of a comment and may appear at the end of a rule or on its own line.
1174	Blank lines are ignored.	1174	Blank lines are ignored.
1175		1175
1176	`_CMD RULE_NUMBER set SET_NUMBER ACTION log LOG_AMOUNT PROTO from SRC SRC_PORT to DST DST_PORT OPTIONS_`	1176	`_CMD RULE_NUMBER set SET_NUMBER ACTION log LOG_AMOUNT PROTO from SRC SRC_PORT to DST DST_PORT OPTIONS_`
Lines 1924-1930 When creating rules, keep in mind that unless the `quick` keyword appears in a r Link Here
1924	This means that even if the first rule to match a packet is a `pass`, if there is a later matching rule that is a `block`, the packet will be dropped.	1924	This means that even if the first rule to match a packet is a `pass`, if there is a later matching rule that is a `block`, the packet will be dropped.
1925	Sample rulesets can be found in [.filename]#/usr/share/examples/ipfilter#.	1925	Sample rulesets can be found in [.filename]#/usr/share/examples/ipfilter#.
1926		1926
1927	When creating rules, a `#` character is used to mark the start of a comment and may appear at the end of a rule, to explain that rule's function, or on its own line.	1927	When creating rules, a `+#+` character is used to mark the start of a comment and may appear at the end of a rule, to explain that rule's function, or on its own line.
1928	Any blank lines are ignored.	1928	Any blank lines are ignored.
1929		1929
1930	The keywords which are used in rules must be written in a specific order, from left to right.	1930	The keywords which are used in rules must be written in a specific order, from left to right.

Lines 93-100 This section covers the basics of configuring inetd. Link Here

(-)b/documentation/content/en/books/handbook/network-servers/_index.adoc (-6 / +6 lines)
93		93
94	Configuration of inetd is done by editing [.filename]#/etc/inetd.conf#.	94	Configuration of inetd is done by editing [.filename]#/etc/inetd.conf#.
95	Each line of this configuration file represents an application which can be started by inetd.	95	Each line of this configuration file represents an application which can be started by inetd.
96	By default, every line starts with a comment (`#`), meaning that inetd is not listening for any applications.	96	By default, every line starts with a comment (`+#+`), meaning that inetd is not listening for any applications.
97	To configure inetd to listen for an application's connections, remove the `#` at the beginning of the line for that application.	97	To configure inetd to listen for an application's connections, remove the `+#+` at the beginning of the line for that application.
98		98
99	After saving your edits, configure inetd to start at system boot by editing [.filename]#/etc/rc.conf#:	99	After saving your edits, configure inetd to start at system boot by editing [.filename]#/etc/rc.conf#:
100		100
Lines 124-130 Once inetd is started, it needs to be notified whenever a modification is made t Link Here
124		124
125	====	125	====
126		126
127	Typically, the default entry for an application does not need to be edited beyond removing the `#`.	127	Typically, the default entry for an application does not need to be edited beyond removing the `+#+`.
128	In some situations, it may be appropriate to edit the default entry.	128	In some situations, it may be appropriate to edit the default entry.
129		129
130	As an example, this is the default entry for man:ftpd[8] over IPv4:	130	As an example, this is the default entry for man:ftpd[8] over IPv4:
Lines 760-766 ellington has been setup as an YP master server without any errors. Link Here
760		760
761	This will create [.filename]#/var/yp/Makefile# from [.filename]#/var/yp/Makefile.dist#.	761	This will create [.filename]#/var/yp/Makefile# from [.filename]#/var/yp/Makefile.dist#.
762	By default, this file assumes that the environment has a single NIS server with only FreeBSD clients.	762	By default, this file assumes that the environment has a single NIS server with only FreeBSD clients.
763	Since `test-domain` has a slave server, edit this line in [.filename]#/var/yp/Makefile# so that it begins with a comment (`#`):	763	Since `test-domain` has a slave server, edit this line in [.filename]#/var/yp/Makefile# so that it begins with a comment (`+#+`):
764		764
765	[.programlisting]	765	[.programlisting]
766	....	766	....
Lines 922-928 Since RPC is a broadcast-based service, any system running ypbind within the sam Link Here
922	To prevent unauthorized transactions, man:ypserv[8] supports a feature called "securenets" which can be used to restrict access to a given set of hosts.	922	To prevent unauthorized transactions, man:ypserv[8] supports a feature called "securenets" which can be used to restrict access to a given set of hosts.
923	By default, this information is stored in [.filename]#/var/yp/securenets#, unless man:ypserv[8] is started with `-p` and an alternate path.	923	By default, this information is stored in [.filename]#/var/yp/securenets#, unless man:ypserv[8] is started with `-p` and an alternate path.
924	This file contains entries that consist of a network specification and a network mask separated by white space.	924	This file contains entries that consist of a network specification and a network mask separated by white space.
925	Lines starting with `#` are considered to be comments.	925	Lines starting with `+#+` are considered to be comments.
926	A sample [.filename]#securenets# might look like this:	926	A sample [.filename]#securenets# might look like this:
927		927
928	[.programlisting]	928	[.programlisting]
Lines 2017-2023 For more detailed information about Apache 2.X and its configuration directives, Link Here
2017	=== Configuring and Starting Apache	2017	=== Configuring and Starting Apache
2018		2018
2019	In FreeBSD, the main Apache HTTP Server configuration file is installed as [.filename]#/usr/local/etc/apache2x/httpd.conf#, where _x_ represents the version number.	2019	In FreeBSD, the main Apache HTTP Server configuration file is installed as [.filename]#/usr/local/etc/apache2x/httpd.conf#, where _x_ represents the version number.
2020	This ASCII text file begins comment lines with a `#`.	2020	This ASCII text file begins comment lines with a `+#+`.
2021	The most frequently modified directives are:	2021	The most frequently modified directives are:
2022		2022
2023	`ServerRoot "/usr/local"`::	2023	`ServerRoot "/usr/local"`::