Attachment #222720 for bug #253760

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





[.programlisting]
....
font8x8="iso-8x8"		# font 8x8 from /usr/share/syscons/fonts/* (or NO).
....

The command to actually switch the mode is man:vidcontrol[1]:

[[type1-fonts-groff]]
== Using Type 1 Fonts with Groff

Now that the new font can be used by both X11 and Ghostscript, how can one use the new font with groff? First of all, since we are dealing with type 1 PostScript(R) fonts, the groff device that is applicable is the _ps_ device. A font file must be created for each font that groff can use. A groff font name is just a file in [.filename]#/usr/share/groff_font/devps#. With our example, the font file could be [.filename]#/usr/share/groff_font/devps/SHOWBOAT#. The file must be created using tools provided by groff.

The first tool is `afmtodit`. This is not normally installed, so it must be retrieved from the source distribution. I found I had to change the first line of the file, so I did:


	tr '\015' '\012' >showboat.afm

Now create the groff font file
% cd /usr/share/groff_font/devps
% /tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT
....


# make -f Makefile.sub afmtodit
....
+
You may also need to copy [.filename]#/usr/contrib/groff/devps/generate/textmap# to [.filename]#/usr/share/groff_font/devps/generate# if it does not already exist.

Once all these utilities are in place, you are ready to commence:



. Create the groff PostScript file:
+ 
Change directories to [.filename]#/usr/share/groff_font/devps# so as to make the following command easier to execute. You will probably need root privileges for this. (Or, if you are paranoid about working there, make sure you reference the files [.filename]#DESC#, [.filename]#text.enc# and [.filename]#generate/textmap# as being in this directory.)
+
[source,bash]
....

% afmtodit -d DESC -e text.enc 3of9.afm generate/textmap 3of9
....
+ 
Ensure that the resulting _PS_font_name_ file (e.g., [.filename]#3of9# in the example above) is located in the directory [.filename]#/usr/share/groff_font/devps# by copying or moving it there.
+ 
Note that if [.filename]#ttf2pf.ps# assigns a font name using the one it finds in the TrueType font file and you want to use a different name, you must edit the [.filename]#.afm# prior to running `afmtodit`. This name must also match the one used in the Fontmap file if you wish to pipe man:groff[1] into man:gs[1].


Lines 271-277 command_args="mock arguments > /dev/null 2>&1" <.> Link Here

(-)b/documentation/content/en/articles/rc-scripting/_index.adoc (-1 / +1 lines)
271		271
272	pidfile="/var/run/${name}.pid" <.>	272	pidfile="/var/run/${name}.pid" <.>
273		273
274	required_files="/etc/${name}.conf /usr/shared/misc/${name}.rules" <.>	274	required_files="/etc/${name}.conf /usr/share/misc/${name}.rules" <.>
275		275
276	sig_reload="USR1" <.>	276	sig_reload="USR1" <.>
277		277

Lines 78-84 The language catalog files have to be compiled into a binary form before they ca Link Here

(-)b/documentation/content/en/books/developers-handbook/l10n/chapter.adoc (-1 / +1 lines)
78	[[nls-using]]	78	[[nls-using]]
79	=== Using the Catalog Files from the Source Code	79	=== Using the Catalog Files from the Source Code
80		80
81	Using the catalog files is simple. To use the related functions, [.filename]#nl_types.h# must be included. Before using a catalog, it has to be opened with man:catopen[3]. The function takes two arguments. The first parameter is the name of the installed and compiled catalog. Usually, the name of the program is used, such as grep. This name will be used when looking for the compiled catalog file. The man:catopen[3] call looks for this file in [.filename]#/usr/shared/nls/locale/catname# and in [.filename]#/usr/local/shared/nls/locale/catname#, where `locale` is the locale set and `catname` is the catalog name being discussed. The second parameter is a constant, which can have two values:	81	Using the catalog files is simple. To use the related functions, [.filename]#nl_types.h# must be included. Before using a catalog, it has to be opened with man:catopen[3]. The function takes two arguments. The first parameter is the name of the installed and compiled catalog. Usually, the name of the program is used, such as grep. This name will be used when looking for the compiled catalog file. The man:catopen[3] call looks for this file in [.filename]#/usr/share/nls/locale/catname# and in [.filename]#/usr/local/shared/nls/locale/catname#, where `locale` is the locale set and `catname` is the catalog name being discussed. The second parameter is a constant, which can have two values:
82		82
83	* `NL_CAT_LOCALE`, which means that the used catalog file will be based on `LC_MESSAGES`.	83	* `NL_CAT_LOCALE`, which means that the used catalog file will be based on `LC_MESSAGES`.
84	* `0`, which means that `LANG` has to be used to open the proper catalog.	84	* `0`, which means that `LANG` has to be used to open the proper catalog.





The secret lies in the last line, which tells `make` to look in the system makefile called [.filename]#bsd.port.mk#. It is easy to overlook this line, but this is where all the clever stuff comes from-someone has written a makefile that tells `make` to do all the things above (plus a couple of other things I did not mention, including handling any errors that may occur) and anyone can get access to that just by putting a single line in their own make file!

If you want to have a look at these system makefiles, they are in [.filename]#/usr/share/mk#, but it is probably best to wait until you have had a bit of practice with makefiles, as they are very complicated (and if you do look at them, make sure you have a flask of strong coffee handy!)

=== More Advanced Uses of `make`

`Make` is a very powerful tool, and can do much more than the simple example above shows. Unfortunately, there are several different versions of `make`, and they all differ considerably. The best way to learn what they can do is probably to read the documentation-hopefully this introduction will have given you a base from which you can do this.

The version of make that comes with FreeBSD is the Berkeley make; there is a tutorial for it in [.filename]#/usr/share/doc/psd/12.make#. To view it, do

[source,bash]
....




The documentation is categorized in a number of different ways. These include:

* The document's name, such as `faq`, or `handbook`.
* The document's language and encoding. These are based on the locale names found under [.filename]#/usr/share/locale# on a FreeBSD system. The current languages and encodings are as follows:
+
[.informaltable]
[cols="1,1", frame="none", options="header"]

MODULES_OVERRIDE= accf_http ipfw
....

Replace _accf_httpd ipfw_ with a list of needed modules. Only the listed modules will be built. This reduces the size of the kernel directory and decreases the amount of time needed to build the kernel. For more information, read [.filename]#/usr/share/examples/etc/make.conf#.

Unneeded devices can be removed from the kernel to further reduce the size. See <<make-kernel>> for more information.


[[daemon-images]]
=== Do you have any BSD daemon images I could use?

Xfig and eps drawings are available under [.filename]#/usr/share/examples/BSD_daemon/#.

[[glossary]]
=== I have seen an acronym or other term on the mailing lists and I do not understand what it means. Where should I look?

Lines 238-244 Note how the commas at the end of the `.Xr` lines have been placed after a space Link Here

(-)b/documentation/content/en/books/fdp-primer/manual-pages/chapter.adoc (-1 / +1 lines)
238	[[manual-pages-markup-important-macros]]	238	[[manual-pages-markup-important-macros]]
239	=== Important Macros	239	=== Important Macros
240		240
241	Some very common macros will be shown here. For more usage examples, see man:mdoc[7], man:groff_mdoc[7], or search for actual use in [.filename]#/usr/shared/man/man*# directories. For example, to search for examples of the `.Bd`_Begin display_ macro:	241	Some very common macros will be shown here. For more usage examples, see man:mdoc[7], man:groff_mdoc[7], or search for actual use in [.filename]#/usr/share/man/man*# directories. For example, to search for examples of the `.Bd`_Begin display_ macro:
242		242
243	[source,bash]	243	[source,bash]
244	....	244	....

Lines 109-115 If you are the only person working on a particular language (or you are responsi Link Here

(-)b/documentation/content/en/books/fdp-primer/translations/chapter.adoc (-1 / +1 lines)
109		109
110	First, make sure your translation is organized properly. This means that it should drop into the existing documentation tree and build straight away.	110	First, make sure your translation is organized properly. This means that it should drop into the existing documentation tree and build straight away.
111		111
112	Currently, the FreeBSD documentation is stored in a top level directory called [.filename]#head/#. Directories below this are named according to the language code they are written in, as defined in ISO639 ([.filename]#/usr/shared/misc/iso639# on a version of FreeBSD newer than 20th January 1999).	112	Currently, the FreeBSD documentation is stored in a top level directory called [.filename]#head/#. Directories below this are named according to the language code they are written in, as defined in ISO639 ([.filename]#/usr/share/misc/iso639# on a version of FreeBSD newer than 20th January 1999).
113		113
114	If your language can be encoded in different ways (for example, Chinese) then there should be directories below this, one for each encoding format you have provided.	114	If your language can be encoded in different ways (for example, Chinese) then there should be directories below this, one for each encoding format you have provided.
115		115

Lines 1851-1857 The following examples use the Net-SNMP software (package:net-mgmt/net-snmp[]) t Link Here

(-)b/documentation/content/en/books/handbook/advanced-networking/_index.adoc (-1 / +1 lines)
1851		1851
1852	[.programlisting]	1852	[.programlisting]
1853	....	1853	....
1854	mibdirs +/usr/shared/snmp/mibs	1854	mibdirs +/usr/share/snmp/mibs
1855	mibs +BRIDGE-MIB:RSTP-MIB:BEGEMOT-MIB:BEGEMOT-BRIDGE-MIB	1855	mibs +BRIDGE-MIB:RSTP-MIB:BEGEMOT-MIB:BEGEMOT-BRIDGE-MIB
1856	....	1856	....
1857		1857

Lines 305-311 FreeBSD provides a variety of different commands to manage user accounts. The mo Link Here

(-)b/documentation/content/en/books/handbook/basics/_index.adoc (-2 / +2 lines)
305	[[users-adduser]]	305	[[users-adduser]]
306	==== `adduser`	306	==== `adduser`
307		307
308	The recommended program for adding new users is man:adduser[8]. When a new user is added, this program automatically updates [.filename]#/etc/passwd# and [.filename]#/etc/group#. It also creates a home directory for the new user, copies in the default configuration files from [.filename]#/usr/shared/skel#, and can optionally mail the new user a welcome message. This utility must be run as the superuser.	308	The recommended program for adding new users is man:adduser[8]. When a new user is added, this program automatically updates [.filename]#/etc/passwd# and [.filename]#/etc/group#. It also creates a home directory for the new user, copies in the default configuration files from [.filename]#/usr/share/skel#, and can optionally mail the new user a welcome message. This utility must be run as the superuser.
309		309
310	The man:adduser[8] utility is interactive and walks through the steps for creating a new user account. As seen in <<users-modifying-adduser>>, either input the required information or press kbd:[Return] to accept the default value shown in square brackets. In this example, the user has been invited into the `wheel` group, allowing them to become the superuser with man:su[1]. When finished, the utility will prompt to either create another user or to exit.	310	The man:adduser[8] utility is interactive and walks through the steps for creating a new user account. As seen in <<users-modifying-adduser>>, either input the required information or press kbd:[Return] to accept the default value shown in square brackets. In this example, the user has been invited into the `wheel` group, allowing them to become the superuser with man:su[1]. When finished, the utility will prompt to either create another user or to exit.
311		311
Lines 921-927 A complete description of the file system hierarchy is available in man:hier[7]. Link Here
921	\|[.filename]#/usr/sbin/#	921	\|[.filename]#/usr/sbin/#
922	\|System daemons and system utilities executed by users.	922	\|System daemons and system utilities executed by users.
923		923
924	\|[.filename]#/usr/shared/#	924	\|[.filename]#/usr/share/#
925	\|Architecture-independent files.	925	\|Architecture-independent files.
926		926
927	\|[.filename]#/usr/src/#	927	\|[.filename]#/usr/src/#

Lines 133-139 An Italian https://www.FreeBSD.org/doc/it_IT.ISO8859-15/books/unix-introduction/ Link Here

(-)b/documentation/content/en/books/handbook/bibliography/_index.adoc (-1 / +1 lines)
133	* Salus, Peter H. _A quarter century of UNIX_. Addison-Wesley Publishing Company, Inc., 1994. ISBN 0-201-54777-5	133	* Salus, Peter H. _A quarter century of UNIX_. Addison-Wesley Publishing Company, Inc., 1994. ISBN 0-201-54777-5
134	* Simon Garfinkel, Daniel Weise, Steven Strassmann. _The UNIX-HATERS Handbook_. IDG Books Worldwide, Inc., 1994. ISBN 1-56884-203-1. Out of print, but available http://www.simson.net/ref/ugh.pdf[online].	134	* Simon Garfinkel, Daniel Weise, Steven Strassmann. _The UNIX-HATERS Handbook_. IDG Books Worldwide, Inc., 1994. ISBN 1-56884-203-1. Out of print, but available http://www.simson.net/ref/ugh.pdf[online].
135	* Don Libes, Sandy Ressler _Life with UNIX_ - special edition. Prentice-Hall, Inc., 1989. ISBN 0-13-536657-7	135	* Don Libes, Sandy Ressler _Life with UNIX_ - special edition. Prentice-Hall, Inc., 1989. ISBN 0-13-536657-7
136	* _The BSD family tree_. https://svnweb.freebsd.org/base/head/shared/misc/bsd-family-tree?view=co[https://svnweb.freebsd.org/base/head/shared/misc/bsd-family-tree?view=co] or link:file://localhost/usr/shared/misc/bsd-family-tree[/usr/shared/misc/bsd-family-tree] on a FreeBSD machine.	136	* _The BSD family tree_. https://svnweb.freebsd.org/base/head/shared/misc/bsd-family-tree?view=co[https://svnweb.freebsd.org/base/head/shared/misc/bsd-family-tree?view=co] or link:file://localhost/usr/share/misc/bsd-family-tree[/usr/share/misc/bsd-family-tree] on a FreeBSD machine.
137	* _Networked Computer Science Technical Reports Library_.	137	* _Networked Computer Science Technical Reports Library_.
138	* _Old BSD releases from the Computer Systems Research group (CSRG)_. http://www.mckusick.com/csrg/[http://www.mckusick.com/csrg/]: The 4CD set covers all BSD versions from 1BSD to 4.4BSD and 4.4BSD-Lite2 (but not 2.11BSD, unfortunately). The last disk also holds the final sources plus the SCCS files.	138	* _Old BSD releases from the Computer Systems Research group (CSRG)_. http://www.mckusick.com/csrg/[http://www.mckusick.com/csrg/]: The 4CD set covers all BSD versions from 1BSD to 4.4BSD and 4.4BSD-Lite2 (but not 2.11BSD, unfortunately). The last disk also holds the final sources plus the SCCS files.
139	* Kernighan, Brian _Unix: A History and a Memoir_. Kindle Direct Publishing, 2020. ISBN 978-169597855-3	139	* Kernighan, Brian _Unix: A History and a Memoir_. Kindle Direct Publishing, 2020. ISBN 978-169597855-3

Lines 501-507 ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP" Link Here

(-)b/documentation/content/en/books/handbook/config/_index.adoc (-2 / +2 lines)
501		501
502	Replace [.filename]#dc0# and [.filename]#dc1# and the IP address information with the correct values for the system. Refer to the man page for the driver, man:ifconfig[8], and man:rc.conf[5] for more details about the allowed options and the syntax of [.filename]#/etc/rc.conf#.	502	Replace [.filename]#dc0# and [.filename]#dc1# and the IP address information with the correct values for the system. Refer to the man page for the driver, man:ifconfig[8], and man:rc.conf[5] for more details about the allowed options and the syntax of [.filename]#/etc/rc.conf#.
503		503
504	If the network is not using DNS, edit [.filename]#/etc/hosts# to add the names and IP addresses of the hosts on the LAN, if they are not already there. For more information, refer to man:hosts[5] and to [.filename]#/usr/shared/examples/etc/hosts#.	504	If the network is not using DNS, edit [.filename]#/etc/hosts# to add the names and IP addresses of the hosts on the LAN, if they are not already there. For more information, refer to man:hosts[5] and to [.filename]#/usr/share/examples/etc/hosts#.
505		505
506	[NOTE]	506	[NOTE]
507	====	507	====
Lines 572-578 PING 192.168.1.2 (192.168.1.2): 56 data bytes Link Here
572	round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms	572	round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms
573	....	573	....
574		574
575	To test network resolution, use the host name instead of the IP address. If there is no DNS server on the network, [.filename]#/etc/hosts# must first be configured. To this purpose, edit [.filename]#/etc/hosts# to add the names and IP addresses of the hosts on the LAN, if they are not already there. For more information, refer to man:hosts[5] and to [.filename]#/usr/shared/examples/etc/hosts#.	575	To test network resolution, use the host name instead of the IP address. If there is no DNS server on the network, [.filename]#/etc/hosts# must first be configured. To this purpose, edit [.filename]#/etc/hosts# to add the names and IP addresses of the hosts on the LAN, if they are not already there. For more information, refer to man:hosts[5] and to [.filename]#/usr/share/examples/etc/hosts#.
576		576
577	==== Troubleshooting	577	==== Troubleshooting
578		578

Lines 456-462 The list of languages and encodings to build and install, such as `en_US.ISO8859 Link Here

(-)b/documentation/content/en/books/handbook/cutting-edge/_index.adoc (-1 / +1 lines)
456	A single format or a list of output formats to be built. Currently, `html`, `html-split`, `txt`, `ps`, and `pdf` are supported.	456	A single format or a list of output formats to be built. Currently, `html`, `html-split`, `txt`, `ps`, and `pdf` are supported.
457		457
458	`DOCDIR`::	458	`DOCDIR`::
459	Where to install the documentation. It defaults to [.filename]#/usr/shared/doc#.	459	Where to install the documentation. It defaults to [.filename]#/usr/share/doc#.
460		460
461	For more `make` variables supported as system-wide options in FreeBSD, refer to man:make.conf[5].	461	For more `make` variables supported as system-wide options in FreeBSD, refer to man:make.conf[5].
462		462

Lines 107-117 This option provides support for `FBT`. While DTrace will work without this opti Link Here

(-)b/documentation/content/en/books/handbook/dtrace/_index.adoc (-2 / +2 lines)
107		107
108	Once the FreeBSD system has rebooted into the new kernel, or the DTrace kernel modules have been loaded using `kldload dtraceall`, the system will need support for the Korn shell as the DTrace Toolkit has several utilities written in `ksh`. Make sure that the package:shells/ksh93[] package or port is installed. It is also possible to run these tools under package:shells/pdksh[] or package:shells/mksh[].	108	Once the FreeBSD system has rebooted into the new kernel, or the DTrace kernel modules have been loaded using `kldload dtraceall`, the system will need support for the Korn shell as the DTrace Toolkit has several utilities written in `ksh`. Make sure that the package:shells/ksh93[] package or port is installed. It is also possible to run these tools under package:shells/pdksh[] or package:shells/mksh[].
109		109
110	Finally, install the current DTrace Toolkit, a collection of ready-made scripts for collecting system information. There are scripts to check open files, memory, `CPU` usage, and a lot more. FreeBSD 10 installs a few of these scripts into [.filename]#/usr/shared/dtrace#. On other FreeBSD versions, or to install the full DTrace Toolkit, use the package:sysutils/DTraceToolkit[] package or port.	110	Finally, install the current DTrace Toolkit, a collection of ready-made scripts for collecting system information. There are scripts to check open files, memory, `CPU` usage, and a lot more. FreeBSD 10 installs a few of these scripts into [.filename]#/usr/share/dtrace#. On other FreeBSD versions, or to install the full DTrace Toolkit, use the package:sysutils/DTraceToolkit[] package or port.
111		111
112	[NOTE]	112	[NOTE]
113	====	113	====
114	The scripts found in [.filename]#/usr/shared/dtrace# have been specifically ported to FreeBSD. Not all of the scripts found in the DTrace Toolkit will work as-is on FreeBSD and some scripts may require some effort in order for them to work on FreeBSD.	114	The scripts found in [.filename]#/usr/share/dtrace# have been specifically ported to FreeBSD. Not all of the scripts found in the DTrace Toolkit will work as-is on FreeBSD and some scripts may require some effort in order for them to work on FreeBSD.
115	====	115	====
116		116
117	The DTrace Toolkit includes many scripts in the special language of DTrace. This language is called the D language and it is very similar to C++. An in depth discussion of the language is beyond the scope of this document. It is covered extensively in the http://www.dtrace.org/guide[Illumos Dynamic Tracing Guide].	117	The DTrace Toolkit includes many scripts in the special language of DTrace. This language is called the D language and it is very similar to C++. An in depth discussion of the language is beyond the scope of this document. It is covered extensively in the http://www.dtrace.org/guide[Illumos Dynamic Tracing Guide].




pf_flags=""                     # additional flags for pfctl startup
....

PF will not start if it cannot find its ruleset configuration file. By default, FreeBSD does not ship with a ruleset and there is no [.filename]#/etc/pf.conf#. Example rulesets can be found in [.filename]#/usr/share/examples/pf/#. If a custom ruleset has been saved somewhere else, add a line to [.filename]#/etc/rc.conf# which specifies the full path to the file:

[.programlisting]
....

# service pflog start
....

By default, PF reads its configuration rules from [.filename]#/etc/pf.conf# and modifies, drops, or passes packets according to the rules or definitions specified in this file. The FreeBSD installation includes several sample files located in [.filename]#/usr/share/examples/pf/#. Refer to the http://www.openbsd.org/faq/pf/[PF FAQ] for complete coverage of PF rulesets.

To control PF, use `pfctl`. <<pfctl>> summarizes some useful options to this command. Refer to man:pfctl[8] for a description of all available options:
[[pfctl]]


=== IPF Rule Syntax

This section describes the IPF rule syntax used to create stateful rules. When creating rules, keep in mind that unless the `quick` keyword appears in a rule, every rule is read in order, with the _last matching rule_ being the one that is applied. 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.


Lines 580-583 Japanese and Korean Language Localization:: Link Here

(-)b/documentation/content/en/books/handbook/l10n/_index.adoc (-1 / +1 lines)
580	For Japanese, refer to http://www.jp.FreeBSD.org/[http://www.jp.FreeBSD.org/], and for Korean, refer to http://www.kr.FreeBSD.org/[http://www.kr.FreeBSD.org/].	580	For Japanese, refer to http://www.jp.FreeBSD.org/[http://www.jp.FreeBSD.org/], and for Korean, refer to http://www.kr.FreeBSD.org/[http://www.kr.FreeBSD.org/].
581		581
582	Non-English FreeBSD Documentation::	582	Non-English FreeBSD Documentation::
583	Some FreeBSD contributors have translated parts of the FreeBSD documentation to other languages. They are available through links on the link:https://www.FreeBSD.org/[FreeBSD web site] or in [.filename]#/usr/shared/doc#.	583	Some FreeBSD contributors have translated parts of the FreeBSD documentation to other languages. They are available through links on the link:https://www.FreeBSD.org/[FreeBSD web site] or in [.filename]#/usr/share/doc#.

Lines 187-193 default:\ Link Here

(-)b/documentation/content/en/books/handbook/mac/_index.adoc (-2 / +2 lines)
187	:welcome=/etc/motd:\	187	:welcome=/etc/motd:\
188	:setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\	188	:setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\
189	:path=~/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:\	189	:path=~/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:\
190	:manpath=/usr/shared/man /usr/local/man:\	190	:manpath=/usr/share/man /usr/local/man:\
191	:nologin=/usr/sbin/nologin:\	191	:nologin=/usr/sbin/nologin:\
192	:cputime=1h30m:\	192	:cputime=1h30m:\
193	:datasize=8M:\	193	:datasize=8M:\
Lines 609-615 insecure:\ Link Here
609	:welcome=/etc/motd:\	609	:welcome=/etc/motd:\
610	:setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\	610	:setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\
611	:path=~/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin	611	:path=~/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
612	:manpath=/usr/shared/man /usr/local/man:\	612	:manpath=/usr/share/man /usr/local/man:\
613	:nologin=/usr/sbin/nologin:\	613	:nologin=/usr/sbin/nologin:\
614	:cputime=1h30m:\	614	:cputime=1h30m:\
615	:datasize=8M:\	615	:datasize=8M:\

Lines 316-322 FreeBSD: { Link Here

(-)b/documentation/content/en/books/handbook/ports/_index.adoc (-3 / +3 lines)
316	url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",	316	url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
317	mirror_type: "srv",	317	mirror_type: "srv",
318	signature_type: "fingerprints",	318	signature_type: "fingerprints",
319	fingerprints: "/usr/shared/keys/pkg",	319	fingerprints: "/usr/share/keys/pkg",
320	enabled: yes	320	enabled: yes
321	}	321	}
322	....	322	....
Lines 1039-1046 The following files will be added as part of updating to Link Here
1039	The following files will be updated as part of updating to	1039	The following files will be updated as part of updating to
1040	11.4-RELEASE-p1:	1040	11.4-RELEASE-p1:
1041	[…]	1041	[…]
1042	Installing updates...Scanning //usr/shared/certs/blacklisted for certificates...	1042	Installing updates...Scanning //usr/share/certs/blacklisted for certificates...
1043	Scanning //usr/shared/certs/trusted for certificates...	1043	Scanning //usr/share/certs/trusted for certificates...
1044	done.	1044	done.
1045	11.4-RELEASE-p1	1045	11.4-RELEASE-p1
1046	[00:04:06] Recording filesystem state for clean... done	1046	[00:04:06] Recording filesystem state for clean... done




+ 
If the ISP has assigned a static IP address and hostname, it should be input into the configuration file. Otherwise, this information will be automatically provided during connection setup.

The rest of this section demonstrates how to configure FreeBSD for common PPP connection scenarios. The required configuration file is [.filename]#/etc/ppp/ppp.conf# and additional files and examples are available in [.filename]#/usr/share/examples/ppp/#.

[NOTE]
====

      add default HISADDR
....

This file is also needed when the default gateway address is "guessed" in a static IP address configuration. In this case, remove line 17 from [.filename]#ppp.conf# and create [.filename]#/etc/ppp/ppp.linkup# with the above two lines. More examples for this file can be found in [.filename]#/usr/share/examples/ppp/#.

By default, `ppp` must be run as `root`. To change this default, add the account of the user who should run `ppp` to the `network` group in [.filename]#/etc/group#.


enable passwdauth
....

To assign some users a static IP number, specify the number as the third argument in [.filename]#/etc/ppp/ppp.secret#. See [.filename]#/usr/share/examples/ppp/ppp.secret.sample# for examples.

[[ppp-troubleshoot]]
== Troubleshooting PPP Connections





Enabling header pages differs depending on whether the printer is connected directly to the computer with a `USB`, parallel, or serial cable, or is connected remotely over a network.

Header pages on directly-connected printers are enabled by removing the `:sh:\` (Suppress Header) line from the entry in [.filename]#/etc/printcap#. These header pages only use line feed characters for new lines. Some printers will need the [.filename]#/usr/share/examples/printing/hpif# filter to prevent stairstepped text. The filter configures `PCL` printers to print both carriage returns and line feeds when a line feed is received.

Header pages for network printers must be configured on the printer itself. Header page entries in [.filename]#/etc/printcap# are ignored. Settings are usually available from the printer front panel or a configuration web page accessible with a web browser.

[[printing-lpd-references]]
=== References

Example files: [.filename]#/usr/share/examples/printing/#.

The _4.3BSD Line Printer Spooler Manual_, [.filename]#/usr/share/doc/smm/07.lpd/paper.ascii.gz#.

Manual pages: man:printcap[5], man:lpd[8], man:lpr[1], man:lpc[8], man:lprm[1], man:lpq[1].


Lines 819-825 When configuring and troubleshooting Kerberos, keep the following points in mind Link Here

(-)b/documentation/content/en/books/handbook/security/_index.adoc (-1 / +1 lines)
819	* With MITKerberos, to allow a principal to have a ticket life longer than the default lifetime of ten hours, use `modify_principal` at the man:kadmin[8] prompt to change the `maxlife` of both the principal in question and the `krbtgt` principal. The principal can then use `kinit -l` to request a ticket with a longer lifetime.	819	* With MITKerberos, to allow a principal to have a ticket life longer than the default lifetime of ten hours, use `modify_principal` at the man:kadmin[8] prompt to change the `maxlife` of both the principal in question and the `krbtgt` principal. The principal can then use `kinit -l` to request a ticket with a longer lifetime.
820	* When running a packet sniffer on the KDC to aid in troubleshooting while running `kinit` from a workstation, the Ticket Granting Ticket (TGT) is sent immediately, even before the password is typed. This is because the Kerberos server freely transmits a TGT to any unauthorized request. However, every TGT is encrypted in a key derived from the user's password. When a user types their password, it is not sent to the KDC, it is instead used to decrypt the TGT that `kinit` already obtained. If the decryption process results in a valid ticket with a valid time stamp, the user has valid Kerberos credentials. These credentials include a session key for establishing secure communications with the Kerberos server in the future, as well as the actual TGT, which is encrypted with the Kerberos server's own key. This second layer of encryption allows the Kerberos server to verify the authenticity of each TGT.	820	* When running a packet sniffer on the KDC to aid in troubleshooting while running `kinit` from a workstation, the Ticket Granting Ticket (TGT) is sent immediately, even before the password is typed. This is because the Kerberos server freely transmits a TGT to any unauthorized request. However, every TGT is encrypted in a key derived from the user's password. When a user types their password, it is not sent to the KDC, it is instead used to decrypt the TGT that `kinit` already obtained. If the decryption process results in a valid ticket with a valid time stamp, the user has valid Kerberos credentials. These credentials include a session key for establishing secure communications with the Kerberos server in the future, as well as the actual TGT, which is encrypted with the Kerberos server's own key. This second layer of encryption allows the Kerberos server to verify the authenticity of each TGT.
821	* Host principals can have a longer ticket lifetime. If the user principal has a lifetime of a week but the host being connected to has a lifetime of nine hours, the user cache will have an expired host principal and the ticket cache will not work as expected.	821	* Host principals can have a longer ticket lifetime. If the user principal has a lifetime of a week but the host being connected to has a lifetime of nine hours, the user cache will have an expired host principal and the ticket cache will not work as expected.
822	* When setting up [.filename]#krb5.dict# to prevent specific bad passwords from being used as described in man:kadmind[8], remember that it only applies to principals that have a password policy assigned to them. The format used in [.filename]#krb5.dict# is one string per line. Creating a symbolic link to [.filename]#/usr/shared/dict/words# might be useful.	822	* When setting up [.filename]#krb5.dict# to prevent specific bad passwords from being used as described in man:kadmind[8], remember that it only applies to principals that have a password policy assigned to them. The format used in [.filename]#krb5.dict# is one string per line. Creating a symbolic link to [.filename]#/usr/share/dict/words# might be useful.
823		823
824	=== Mitigating Kerberos Limitations	824	=== Mitigating Kerberos Limitations
825		825

Return to bug 253760

Lines 152-158 Additional options, described in man:pfctl[8], can be passed to PF when it is st Link Here

(-)b/documentation/content/en/books/handbook/firewalls/_index.adoc (-3 / +3 lines)
152	pf_flags="" # additional flags for pfctl startup	152	pf_flags="" # additional flags for pfctl startup
153	....	153	....
154		154
155	PF will not start if it cannot find its ruleset configuration file. By default, FreeBSD does not ship with a ruleset and there is no [.filename]#/etc/pf.conf#. Example rulesets can be found in [.filename]#/usr/shared/examples/pf/#. If a custom ruleset has been saved somewhere else, add a line to [.filename]#/etc/rc.conf# which specifies the full path to the file:	155	PF will not start if it cannot find its ruleset configuration file. By default, FreeBSD does not ship with a ruleset and there is no [.filename]#/etc/pf.conf#. Example rulesets can be found in [.filename]#/usr/share/examples/pf/#. If a custom ruleset has been saved somewhere else, add a line to [.filename]#/etc/rc.conf# which specifies the full path to the file:
156		156
157	[.programlisting]	157	[.programlisting]
158	....	158	....
Lines 189-195 After saving the needed edits, PF can be started with logging support by typing: Link Here
189	# service pflog start	189	# service pflog start
190	....	190	....
191		191
192	By default, PF reads its configuration rules from [.filename]#/etc/pf.conf# and modifies, drops, or passes packets according to the rules or definitions specified in this file. The FreeBSD installation includes several sample files located in [.filename]#/usr/shared/examples/pf/#. Refer to the http://www.openbsd.org/faq/pf/[PF FAQ] for complete coverage of PF rulesets.	192	By default, PF reads its configuration rules from [.filename]#/etc/pf.conf# and modifies, drops, or passes packets according to the rules or definitions specified in this file. The FreeBSD installation includes several sample files located in [.filename]#/usr/share/examples/pf/#. Refer to the http://www.openbsd.org/faq/pf/[PF FAQ] for complete coverage of PF rulesets.
193		193
194	To control PF, use `pfctl`. <<pfctl>> summarizes some useful options to this command. Refer to man:pfctl[8] for a description of all available options:	194	To control PF, use `pfctl`. <<pfctl>> summarizes some useful options to this command. Refer to man:pfctl[8] for a description of all available options:
195	[[pfctl]]	195	[[pfctl]]
Lines 1604-1610 Refer to man:ipf[8] for details on the other flags available with this command. Link Here
1604		1604
1605	=== IPF Rule Syntax	1605	=== IPF Rule Syntax
1606		1606
1607	This section describes the IPF rule syntax used to create stateful rules. When creating rules, keep in mind that unless the `quick` keyword appears in a rule, every rule is read in order, with the _last matching rule_ being the one that is applied. 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/shared/examples/ipfilter#.	1607	This section describes the IPF rule syntax used to create stateful rules. When creating rules, keep in mind that unless the `quick` keyword appears in a rule, every rule is read in order, with the _last matching rule_ being the one that is applied. 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#.
1608		1608
1609	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.	1609	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.
1610		1610

Lines 734-749 It can be difficult for users to locate their documents in the stack of pages pr Link Here

(-)b/documentation/content/en/books/handbook/printing/_index.adoc (-3 / +3 lines)
734		734
735	Enabling header pages differs depending on whether the printer is connected directly to the computer with a `USB`, parallel, or serial cable, or is connected remotely over a network.	735	Enabling header pages differs depending on whether the printer is connected directly to the computer with a `USB`, parallel, or serial cable, or is connected remotely over a network.
736		736
737	Header pages on directly-connected printers are enabled by removing the `:sh:\` (Suppress Header) line from the entry in [.filename]#/etc/printcap#. These header pages only use line feed characters for new lines. Some printers will need the [.filename]#/usr/shared/examples/printing/hpif# filter to prevent stairstepped text. The filter configures `PCL` printers to print both carriage returns and line feeds when a line feed is received.	737	Header pages on directly-connected printers are enabled by removing the `:sh:\` (Suppress Header) line from the entry in [.filename]#/etc/printcap#. These header pages only use line feed characters for new lines. Some printers will need the [.filename]#/usr/share/examples/printing/hpif# filter to prevent stairstepped text. The filter configures `PCL` printers to print both carriage returns and line feeds when a line feed is received.
738		738
739	Header pages for network printers must be configured on the printer itself. Header page entries in [.filename]#/etc/printcap# are ignored. Settings are usually available from the printer front panel or a configuration web page accessible with a web browser.	739	Header pages for network printers must be configured on the printer itself. Header page entries in [.filename]#/etc/printcap# are ignored. Settings are usually available from the printer front panel or a configuration web page accessible with a web browser.
740		740
741	[[printing-lpd-references]]	741	[[printing-lpd-references]]
742	=== References	742	=== References
743		743
744	Example files: [.filename]#/usr/shared/examples/printing/#.	744	Example files: [.filename]#/usr/share/examples/printing/#.
745		745
746	The _4.3BSD Line Printer Spooler Manual_, [.filename]#/usr/shared/doc/smm/07.lpd/paper.ascii.gz#.	746	The _4.3BSD Line Printer Spooler Manual_, [.filename]#/usr/share/doc/smm/07.lpd/paper.ascii.gz#.
747		747
748	Manual pages: man:printcap[5], man:lpd[8], man:lpr[1], man:lpc[8], man:lprm[1], man:lpq[1].	748	Manual pages: man:printcap[5], man:lpd[8], man:lpr[1], man:lpc[8], man:lprm[1], man:lpq[1].
749		749

Lines 93-99 First, an 8x8 font must be loaded. To do this, [.filename]#/etc/rc.conf# should Link Here

(-)b/documentation/content/en/articles/fonts/_index.adoc (-6 / +6 lines)
93		93
94	[.programlisting]	94	[.programlisting]
95	....	95	....
96	font8x8="iso-8x8" # font 8x8 from /usr/shared/syscons/fonts/* (or NO).	96	font8x8="iso-8x8" # font 8x8 from /usr/share/syscons/fonts/* (or NO).
97	....	97	....
98		98
99	The command to actually switch the mode is man:vidcontrol[1]:	99	The command to actually switch the mode is man:vidcontrol[1]:
Lines 299-305 References: [.filename]#fonts.txt# in the Ghostscript 4.01 distribution Link Here
299	[[type1-fonts-groff]]	299	[[type1-fonts-groff]]
300	== Using Type 1 Fonts with Groff	300	== Using Type 1 Fonts with Groff
301		301
302	Now that the new font can be used by both X11 and Ghostscript, how can one use the new font with groff? First of all, since we are dealing with type 1 PostScript(R) fonts, the groff device that is applicable is the _ps_ device. A font file must be created for each font that groff can use. A groff font name is just a file in [.filename]#/usr/shared/groff_font/devps#. With our example, the font file could be [.filename]#/usr/shared/groff_font/devps/SHOWBOAT#. The file must be created using tools provided by groff.	302	Now that the new font can be used by both X11 and Ghostscript, how can one use the new font with groff? First of all, since we are dealing with type 1 PostScript(R) fonts, the groff device that is applicable is the _ps_ device. A font file must be created for each font that groff can use. A groff font name is just a file in [.filename]#/usr/share/groff_font/devps#. With our example, the font file could be [.filename]#/usr/share/groff_font/devps/SHOWBOAT#. The file must be created using tools provided by groff.
303		303
304	The first tool is `afmtodit`. This is not normally installed, so it must be retrieved from the source distribution. I found I had to change the first line of the file, so I did:	304	The first tool is `afmtodit`. This is not normally installed, so it must be retrieved from the source distribution. I found I had to change the first line of the file, so I did:
305		305
Lines 324-330 We need to convert them to UNIX(R) style ^J delimited lines Link Here
324	tr '\015' '\012' >showboat.afm	324	tr '\015' '\012' >showboat.afm
325		325
326	Now create the groff font file	326	Now create the groff font file
327	% cd /usr/shared/groff_font/devps	327	% cd /usr/share/groff_font/devps
328	% /tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT	328	% /tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT
329	....	329	....
330		330
Lines 430-436 In the work area, you will need to make the utility. Just type: Link Here
430	# make -f Makefile.sub afmtodit	430	# make -f Makefile.sub afmtodit
431	....	431	....
432	+	432	+
433	You may also need to copy [.filename]#/usr/contrib/groff/devps/generate/textmap# to [.filename]#/usr/shared/groff_font/devps/generate# if it does not already exist.	433	You may also need to copy [.filename]#/usr/contrib/groff/devps/generate/textmap# to [.filename]#/usr/share/groff_font/devps/generate# if it does not already exist.
434		434
435	Once all these utilities are in place, you are ready to commence:	435	Once all these utilities are in place, you are ready to commence:
436		436
Lines 469-475 Converting 3of9.ttf to A.pfa and B.afm. Link Here
469		469
470	. Create the groff PostScript file:	470	. Create the groff PostScript file:
471	+	471	+
472	Change directories to [.filename]#/usr/shared/groff_font/devps# so as to make the following command easier to execute. You will probably need root privileges for this. (Or, if you are paranoid about working there, make sure you reference the files [.filename]#DESC#, [.filename]#text.enc# and [.filename]#generate/textmap# as being in this directory.)	472	Change directories to [.filename]#/usr/share/groff_font/devps# so as to make the following command easier to execute. You will probably need root privileges for this. (Or, if you are paranoid about working there, make sure you reference the files [.filename]#DESC#, [.filename]#text.enc# and [.filename]#generate/textmap# as being in this directory.)
473	+	473	+
474	[source,bash]	474	[source,bash]
475	....	475	....
Lines 483-489 Where, [.filename]#file.afm# is the _AFM_name_ created by `ttf2pf.ps` above, and Link Here
483	% afmtodit -d DESC -e text.enc 3of9.afm generate/textmap 3of9	483	% afmtodit -d DESC -e text.enc 3of9.afm generate/textmap 3of9
484	....	484	....
485	+	485	+
486	Ensure that the resulting _PS_font_name_ file (e.g., [.filename]#3of9# in the example above) is located in the directory [.filename]#/usr/shared/groff_font/devps# by copying or moving it there.	486	Ensure that the resulting _PS_font_name_ file (e.g., [.filename]#3of9# in the example above) is located in the directory [.filename]#/usr/share/groff_font/devps# by copying or moving it there.
487	+	487	+
488	Note that if [.filename]#ttf2pf.ps# assigns a font name using the one it finds in the TrueType font file and you want to use a different name, you must edit the [.filename]#.afm# prior to running `afmtodit`. This name must also match the one used in the Fontmap file if you wish to pipe man:groff[1] into man:gs[1].	488	Note that if [.filename]#ttf2pf.ps# assigns a font name using the one it finds in the TrueType font file and you want to use a different name, you must edit the [.filename]#.afm# prior to running `afmtodit`. This name must also match the one used in the Fontmap file if you wish to pipe man:groff[1] into man:gs[1].
489		489

Lines 578-590 Now I think you will agree that is rather impressive for a four line script! Link Here

(-)b/documentation/content/en/books/developers-handbook/tools/chapter.adoc (-2 / +2 lines)
578		578
579	The secret lies in the last line, which tells `make` to look in the system makefile called [.filename]#bsd.port.mk#. It is easy to overlook this line, but this is where all the clever stuff comes from-someone has written a makefile that tells `make` to do all the things above (plus a couple of other things I did not mention, including handling any errors that may occur) and anyone can get access to that just by putting a single line in their own make file!	579	The secret lies in the last line, which tells `make` to look in the system makefile called [.filename]#bsd.port.mk#. It is easy to overlook this line, but this is where all the clever stuff comes from-someone has written a makefile that tells `make` to do all the things above (plus a couple of other things I did not mention, including handling any errors that may occur) and anyone can get access to that just by putting a single line in their own make file!
580		580
581	If you want to have a look at these system makefiles, they are in [.filename]#/usr/shared/mk#, but it is probably best to wait until you have had a bit of practice with makefiles, as they are very complicated (and if you do look at them, make sure you have a flask of strong coffee handy!)	581	If you want to have a look at these system makefiles, they are in [.filename]#/usr/share/mk#, but it is probably best to wait until you have had a bit of practice with makefiles, as they are very complicated (and if you do look at them, make sure you have a flask of strong coffee handy!)
582		582
583	=== More Advanced Uses of `make`	583	=== More Advanced Uses of `make`
584		584
585	`Make` is a very powerful tool, and can do much more than the simple example above shows. Unfortunately, there are several different versions of `make`, and they all differ considerably. The best way to learn what they can do is probably to read the documentation-hopefully this introduction will have given you a base from which you can do this.	585	`Make` is a very powerful tool, and can do much more than the simple example above shows. Unfortunately, there are several different versions of `make`, and they all differ considerably. The best way to learn what they can do is probably to read the documentation-hopefully this introduction will have given you a base from which you can do this.
586		586
587	The version of make that comes with FreeBSD is the Berkeley make; there is a tutorial for it in [.filename]#/usr/shared/doc/psd/12.make#. To view it, do	587	The version of make that comes with FreeBSD is the Berkeley make; there is a tutorial for it in [.filename]#/usr/share/doc/psd/12.make#. To view it, do
588		588
589	[source,bash]	589	[source,bash]
590	....	590	....

Lines 234-240 Yes. The documentation is available in a number of different formats and compres Link Here

(-)b/documentation/content/en/books/faq/_index.adoc (-3 / +3 lines)
234	The documentation is categorized in a number of different ways. These include:	234	The documentation is categorized in a number of different ways. These include:
235		235
236	* The document's name, such as `faq`, or `handbook`.	236	* The document's name, such as `faq`, or `handbook`.
237	* The document's language and encoding. These are based on the locale names found under [.filename]#/usr/shared/locale# on a FreeBSD system. The current languages and encodings are as follows:	237	* The document's language and encoding. These are based on the locale names found under [.filename]#/usr/share/locale# on a FreeBSD system. The current languages and encodings are as follows:
238	+	238	+
239	[.informaltable]	239	[.informaltable]
240	[cols="1,1", frame="none", options="header"]	240	[cols="1,1", frame="none", options="header"]
Lines 926-932 To build and install only the specified modules, list them in [.filename]#/etc/m Link Here
926	MODULES_OVERRIDE= accf_http ipfw	926	MODULES_OVERRIDE= accf_http ipfw
927	....	927	....
928		928
929	Replace _accf_httpd ipfw_ with a list of needed modules. Only the listed modules will be built. This reduces the size of the kernel directory and decreases the amount of time needed to build the kernel. For more information, read [.filename]#/usr/shared/examples/etc/make.conf#.	929	Replace _accf_httpd ipfw_ with a list of needed modules. Only the listed modules will be built. This reduces the size of the kernel directory and decreases the amount of time needed to build the kernel. For more information, read [.filename]#/usr/share/examples/etc/make.conf#.
930		930
931	Unneeded devices can be removed from the kernel to further reduce the size. See <<make-kernel>> for more information.	931	Unneeded devices can be removed from the kernel to further reduce the size. See <<make-kernel>> for more information.
932		932
Lines 2325-2331 In summary, the image can be used in a tasteful manner, for personal use, so lon Link Here
2325	[[daemon-images]]	2325	[[daemon-images]]
2326	=== Do you have any BSD daemon images I could use?	2326	=== Do you have any BSD daemon images I could use?
2327		2327
2328	Xfig and eps drawings are available under [.filename]#/usr/shared/examples/BSD_daemon/#.	2328	Xfig and eps drawings are available under [.filename]#/usr/share/examples/BSD_daemon/#.
2329		2329
2330	[[glossary]]	2330	[[glossary]]
2331	=== I have seen an acronym or other term on the mailing lists and I do not understand what it means. Where should I look?	2331	=== I have seen an acronym or other term on the mailing lists and I do not understand what it means. Where should I look?

Lines 80-86 The following information may be supplied by the ISP, but is not necessary: Link Here

(-)b/documentation/content/en/books/handbook/ppp-and-slip/_index.adoc (-3 / +3 lines)
80	+	80	+
81	If the ISP has assigned a static IP address and hostname, it should be input into the configuration file. Otherwise, this information will be automatically provided during connection setup.	81	If the ISP has assigned a static IP address and hostname, it should be input into the configuration file. Otherwise, this information will be automatically provided during connection setup.
82		82
83	The rest of this section demonstrates how to configure FreeBSD for common PPP connection scenarios. The required configuration file is [.filename]#/etc/ppp/ppp.conf# and additional files and examples are available in [.filename]#/usr/shared/examples/ppp/#.	83	The rest of this section demonstrates how to configure FreeBSD for common PPP connection scenarios. The required configuration file is [.filename]#/etc/ppp/ppp.conf# and additional files and examples are available in [.filename]#/usr/share/examples/ppp/#.
84		84
85	[NOTE]	85	[NOTE]
86	====	86	====
Lines 184-190 provider: Link Here
184	add default HISADDR	184	add default HISADDR
185	....	185	....
186		186
187	This file is also needed when the default gateway address is "guessed" in a static IP address configuration. In this case, remove line 17 from [.filename]#ppp.conf# and create [.filename]#/etc/ppp/ppp.linkup# with the above two lines. More examples for this file can be found in [.filename]#/usr/shared/examples/ppp/#.	187	This file is also needed when the default gateway address is "guessed" in a static IP address configuration. In this case, remove line 17 from [.filename]#ppp.conf# and create [.filename]#/etc/ppp/ppp.linkup# with the above two lines. More examples for this file can be found in [.filename]#/usr/share/examples/ppp/#.
188		188
189	By default, `ppp` must be run as `root`. To change this default, add the account of the user who should run `ppp` to the `network` group in [.filename]#/etc/group#.	189	By default, `ppp` must be run as `root`. To change this default, add the account of the user who should run `ppp` to the `network` group in [.filename]#/etc/group#.
190		190
Lines 429-435 Each user logging in with this method will need to have a username/password in [ Link Here
429	enable passwdauth	429	enable passwdauth
430	....	430	....
431		431
432	To assign some users a static IP number, specify the number as the third argument in [.filename]#/etc/ppp/ppp.secret#. See [.filename]#/usr/shared/examples/ppp/ppp.secret.sample# for examples.	432	To assign some users a static IP number, specify the number as the third argument in [.filename]#/etc/ppp/ppp.secret#. See [.filename]#/usr/share/examples/ppp/ppp.secret.sample# for examples.
433		433
434	[[ppp-troubleshoot]]	434	[[ppp-troubleshoot]]
435	== Troubleshooting PPP Connections	435	== Troubleshooting PPP Connections