From owner-svn-doc-projects@FreeBSD.ORG Mon May 27 20:48:11 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4ADB12D8; Mon, 27 May 2013 20:48:11 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 3CA38BED; Mon, 27 May 2013 20:48:11 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4RKmBiP051880; Mon, 27 May 2013 20:48:11 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4RKmBFF051879; Mon, 27 May 2013 20:48:11 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305272048.r4RKmBFF051879@svn.freebsd.org> From: Tom Rhodes Date: Mon, 27 May 2013 20:48:11 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41757 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 20:48:11 -0000 Author: trhodes Date: Mon May 27 20:48:10 2013 New Revision: 41757 URL: http://svnweb.freebsd.org/changeset/doc/41757 Log: Markup, entities, avoid you, grammar, whitespace. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Mon May 27 20:33:31 2013 (r41756) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Mon May 27 20:48:10 2013 (r41757) @@ -126,9 +126,9 @@ Overview - &man.inetd.8; is sometimes referred to as the + The &man.inetd.8; daemon is sometimes referred to as the Internet Super-Server because it manages - connections for several services. When a connection is + connections for many services. When a connection is received by inetd, it determines which program the connection is destined for, spawns the particular process and delegates the socket to it (the program @@ -175,8 +175,7 @@ &prompt.root; service inetd rcvar - - can be run to display the current effective setting. + can be run to display the current effective setting. Additionally, different command-line options can be passed to inetd via the @@ -202,9 +201,9 @@ Although we mention rate-limiting options below, novice users may be pleased to note that these parameters usually do - not need to be modified. These options may be useful should - you find that you are receiving an excessive amount of - connections. A full list of options can be found in the + not need to be modified. These options may be useful if + an excessive amount of connections are being established. + A full list of options can be found in the &man.inetd.8; manual. @@ -509,7 +508,7 @@ server-program-argumentsmax-connections-per-ip-per-minute, or limitations on certain - daemons if you find that you have too many connections. + daemons if there are too many connections. By default, TCP wrapping is turned on. Consult the &man.hosts.access.5; manual page for more information on @@ -529,8 +528,7 @@ server-program-argumentsinetd. The auth service provides - identity - network services, and is + identity network services, and is configurable to a certain degree, whilst the others are simply on or off. @@ -677,8 +675,8 @@ server-program-argumentsNFS configuration is a relatively straightforward process. The processes that need to be - running can all start at boot time with a few modifications to - your /etc/rc.conf file. + running can all start at boot time with a few modifications + to /etc/rc.conf. On the NFS server, make sure that the following options are configured in the @@ -704,8 +702,8 @@ mountd_flags="-r" system. Along with what machines have access to that file system, access options may also be specified. There are many such options that can be used in this file but only a few will - be mentioned here. You can easily discover other options by - reading over the &man.exports.5; manual page. + be mentioned here. Other options are discussed in + the &man.exports.5; manual page. Here are a few example /etc/exports entries: @@ -717,11 +715,11 @@ mountd_flags="-r" The following examples give an idea of how to export file systems, although the settings may be different depending - on your environment and network configuration. For instance, + on the environment and network configuration. For instance, to export the /cdrom directory to three example machines that have the same domain name as the server (hence the lack of a domain name for each) or have entries in - your /etc/hosts file. The + the /etc/hosts file. The flag makes the exported file system read-only. With this flag, the remote system will not be able to write any changes to the exported file system. @@ -729,7 +727,7 @@ mountd_flags="-r" /cdrom -ro host1 host2 host3 The following line exports /home to - three hosts by IP address. This is a useful setup if you have + three hosts by IP address. This is a useful setup on a private network without a DNS server configured. Optionally the /etc/hosts file could be configured for internal hostnames; please review @@ -755,8 +753,7 @@ mountd_flags="-r" In order for a client to access an exported file system, the client must have permission to do so. Make sure the - client is listed in your /etc/exports - file. + client is listed in /etc/exports. In /etc/exports, each line represents the export information for one file system to one host. A @@ -778,8 +775,9 @@ mountd_flags="-r" The properties of one file system exported to a given host must all occur on one line. Lines without a client specified - are treated as a single host. This limits how you can export - file systems, but for most people this is not an issue. + are treated as a single host. This limits how file systems + may be exported; however, for most environments, this is not + an issue. The following is an example of a valid export list, where /usr and /exports @@ -828,9 +826,8 @@ mountd_flags="-r" Now everything should be ready to actually mount a remote file system. In these examples the server's name will be server and the client's name will be - client. If you only want to temporarily - mount a remote file system or would rather test the - configuration, just execute a command like this as + client. For testing or to temporarily + mount a remote file system execute a command like this as root on the client: @@ -841,11 +838,11 @@ mountd_flags="-r" This will mount the /home directory on the server at /mnt on the client. If - everything is set up correctly you should be able to enter - /mnt on the client and see all the files - that are on the server. + everything is set up correctly, the server's files should be + visible and available in the /mnt + directory. - If you want to automatically mount a remote file system + To permanently mount a remote file system each time the computer boots, add the file system to the /etc/fstab file. Here is an example: @@ -911,10 +908,9 @@ rpc_statd_enable="YES" Several machines could have a common - /usr/ports/distfiles directory. That - way, when you need to install a port on several machines, - you can quickly access the source without downloading it - on each machine. + /usr/ports/distfiles directory. This + allows for quick access to the source files without + downloading them on each machine. @@ -974,10 +970,10 @@ rpc_statd_enable="YES" Mounting an Export with <application>amd</application> - You can view the available mounts of a remote host with - the showmount command. For example, to - view the mounts of a host named foobar, you - can use: + The showmount command shows the + available mounts on a remote host. For example, to + view the mounts of a host named + foobar: &prompt.user; showmount -e foobar Exports list on foobar: @@ -1062,9 +1058,8 @@ Exports list on foobar: It should be noted that there is a different problem, sometimes mistaken for this one, when the NFS servers and clients are on different networks. If that is the case, make - certain that your routers are routing the - necessary UDP information, or you will not - get anywhere, no matter what else you are doing. + certain that the routers are routing the + necessary UDP information. In the following examples, fastws is the host (interface) name of a high-performance workstation, and @@ -1076,7 +1071,7 @@ Exports list on foobar: client for the exported file system. In all cases, note that additional options, such as or and may be desirable - in your application. + in the application. Examples for the FreeBSD system (freebox) as the client in /etc/fstab on @@ -1211,12 +1206,12 @@ Exports list on foobar: - Terms/Processes You Should Know + <acronym>NIS</acronym>Terms and Processes - There are several terms and several important user - processes that you will come across when attempting to - implement NIS on FreeBSD, whether you are trying to create an - NIS server or act as an NIS client: + There are several terms and important user + processes that will be explained while attempting to + implement NIS on FreeBSD, regardless if the system is a + NIS server or a NIS client: rpcbind @@ -1386,18 +1381,17 @@ Exports list on foobar: Planning - Let us assume that you are the administrator of a small - university lab. This lab, which consists of 15 FreeBSD + Let us assume that an administrator of a small + university lab, which consists of 15 FreeBSD machines, currently has no centralized point of - administration; each machine has its own + administration. Each machine has its own /etc/passwd and /etc/master.passwd. These files are kept in sync with each other only through manual - intervention; currently, when you add a user to the lab, you - must run adduser on all 15 machines. - Clearly, this has to change, so you have decided to convert - the lab to use NIS, using two of the machines as - servers. + intervention; currently, a user is added to the lab, the + process must be ran on all 15 machines. + The lab would clearly benefit from the addition of two + NIS servers. Therefore, the configuration of the lab now looks something like: @@ -1446,10 +1440,10 @@ Exports list on foobar: - If you are setting up a NIS scheme for the first time, - it is a good idea to think through how you want to go about - it. No matter what the size of your network, there are a - few decisions that need to be made. + If this is the first time a NIS scheme + is being developed, it should be thoroughly planned ahead of + time. Regardless of network size, several decisions need to + be made as part of the planning process. Choosing a NIS Domain Name @@ -1458,8 +1452,8 @@ Exports list on foobar: NIS domainname - This might not be the domainname that - you are used to. It is more accurately called the + This might not be the normal domainname + for the network. It is more accurately called the NIS domainname. When a client broadcasts its requests for info, it includes the name of the NIS domain that it is part of. This is how multiple servers @@ -1471,19 +1465,19 @@ Exports list on foobar: domainname for their NIS domainname. This is not recommended as it can cause confusion when trying to debug network problems. The NIS domainname should be unique - within your network and it is helpful if it describes the + within the network and it is helpful if it describes the group of machines it represents. For example, the Art department at Acme Inc. might be in the acme-art NIS domain. For this example, - assume you have chosen the name + assume the chosen name will be test-domain. SunOS However, some operating systems (notably &sunos;) use their NIS domain name as their Internet domain name. If - one or more machines on your network have this - restriction, you must use the - Internet domain name as your NIS domain name. + one or more machines on the network have this + restriction, it must be used as the + Internet domain name for the NIS domain name. @@ -1496,16 +1490,15 @@ Exports list on foobar: for its NIS domain, very often the machine becomes unusable. The lack of user and group information causes most systems to temporarily freeze up. With this in mind - you should make sure to choose a machine that will not be - prone to being rebooted regularly, or one that might be + be sure to choose a machine that will not be + prone to being rebooted frequently, or one that might be used for development. The NIS server should ideally be a stand alone machine whose sole purpose in life is to be an - NIS server. If you have a network that is not very + NIS server. If the network is not very heavily used, it is acceptable to put the NIS server on a - machine running other services, just keep in mind that if - the NIS server becomes unavailable, it will affect - all of your NIS clients - adversely. + machine running other services, however; if + the NIS server becomes unavailable, it will adversely affect + all NIS clients. @@ -1540,11 +1533,10 @@ Exports list on foobar: server configuration Setting up a master NIS server can be relatively - straight forward, depending on your needs. FreeBSD comes - with support for NIS out-of-the-box. All you need is to - add the following lines to - /etc/rc.conf, and FreeBSD will do the - rest for you. + straight forward, depending on environmental needs. &os; + comes with support for NIS out-of-the-box. It only needs to + be enabled by adding the following lines to + /etc/rc.conf: @@ -1574,8 +1566,8 @@ Exports list on foobar: - Depending on your NIS setup, you may need to add - further entries. See the Depending on the NIS setup, additional entries may + be required. See the section about NIS servers that are also NIS clients, below, for details. @@ -1583,7 +1575,7 @@ Exports list on foobar: After setting up the above entries, run the command /etc/netstart as superuser. It will - set up everything for you, using the values you defined in + set up everything, using the values defined in /etc/rc.conf. As a last step, before initializing the NIS maps, start the ypserv daemon manually: @@ -1602,44 +1594,44 @@ Exports list on foobar: that are kept in the /var/yp directory. They are generated from configuration files in the /etc directory of the NIS master, - with one exception: the - /etc/master.passwd file. This is for - a good reason, you do not want to propagate passwords to - your root and other administrative + with one exception: /etc/master.passwd. + This is for + a good reason, never propagate passwords for + root and other administrative accounts to all the servers in the NIS domain. Therefore, - before we initialize the NIS maps, you should: + before the the NIS maps are initialized, configure the primary + password files: &prompt.root; cp /etc/master.passwd /var/yp/master.passwd &prompt.root; cd /var/yp &prompt.root; vi master.passwd - You should remove all entries regarding system + It is advisable to remove all entries regarding system accounts (bin, tty, kmem, games, etc), as well as any accounts - that you do not want to be propagated to the NIS clients + that do not need to be propagated to the NIS clients (for example root and any other UID 0 (superuser) accounts). - Make sure the + Ensure the /var/yp/master.passwd is neither - group nor world readable (mode 600)! Use the - chmod command, if + group or world readable (mode 600)! Use the + chmod command, as appropriate. Tru64 UNIX - When you have finished, it is time to initialize the - NIS maps! FreeBSD includes a script named - ypinit to do this for you (see its + When this task has been completed, it is time to + initialize the NIS maps. FreeBSD includes a script named + ypinit to do this (see its manual page for more information). Note that this script is available on most &unix; Operating Systems, but not on all. On Digital UNIX/Compaq Tru64 UNIX it is called ypsetup. Because we are generating maps for an NIS master, we are going to pass the option to ypinit. - To generate the NIS maps, assuming you already performed - the steps above, run: + To generate the NIS maps run: ellington&prompt.root; ypinit -m test-domain Server Type: MASTER Domain: test-domain @@ -1665,14 +1657,14 @@ Is this correct? [y/n: y] y< NIS Map update completed. ellington has been setup as an YP master server without any errors. - ypinit should have created - /var/yp/Makefile from + At this point, ypinit should have + created /var/yp/Makefile from /var/yp/Makefile.dist. - When created, this file assumes that you are operating - in a single server NIS environment with only FreeBSD + When created, this file assumes that the operating + environment is a single server NIS system with only &os; machines. Since test-domain has - a slave server as well, you must edit - /var/yp/Makefile: + a slave server as well, edit + /var/yp/Makefile as well: ellington&prompt.root; vi /var/yp/Makefile @@ -1756,12 +1748,12 @@ ypxfr: Exiting: Map successfully transfe coltrane has been setup as an YP slave server without any errors. Don't forget to update map ypservers on ellington. - You should now have a directory called + There should be a directory called /var/yp/test-domain. Copies of the - NIS master server's maps should be in this directory. You - will need to make sure that these stay updated. The + NIS master server's maps should be in this directory. These + files must always be up to date. The following /etc/crontab entries on - your slave servers should do the job: + the slave servers should do the job: 20 * * * * root /usr/libexec/ypxfr passwd.byname 21 * * * * root /usr/libexec/ypxfr passwd.byuid @@ -1769,7 +1761,7 @@ Don't forget to update map ypservers on These two lines force the slave to sync its maps with the maps on the master server. These entries are not mandatory because the master server automatically attempts - to push any map changes to its slaves. However, due to + to push any map changes to its slaves; however, due to the importance of correct password information on other clients depending on the slave server, it is recommended to specifically force the password map updates frequently. @@ -1785,10 +1777,10 @@ Don't forget to update map ypservers on NIS Clients - An NIS client establishes what is called a binding to a + An NIS client establishes what is called a binding to a particular NIS server using the - ypbind daemon. - ypbind checks the system's default + ypbind daemon. The + ypbind command checks the system's default domain (as set by the domainname command), and begins broadcasting RPC requests on the local network. These requests specify the name of the domain for @@ -1820,9 +1812,9 @@ Don't forget to update map ypservers on - Edit the file /etc/rc.conf + Edit /etc/rc.conf and add the following lines in order to set the NIS - domainname and start ypbind upon + domainname and start ypbind during network startup: nisdomainname="test-domain" @@ -1831,7 +1823,7 @@ nis_client_enable="YES" To import all possible password entries from the - NIS server, remove all user accounts from your + NIS server, remove all user accounts from the /etc/master.passwd file and use vipw to add the following line to the end of the file: @@ -1841,7 +1833,7 @@ nis_client_enable="YES" This line will afford anyone with a valid account in the NIS server's password maps an - account. There are many ways to configure your NIS + account. There are many ways to configure the NIS client by changing this line. See the netgroups @@ -1851,8 +1843,8 @@ nis_client_enable="YES" - You should keep at least one local account (i.e. - not imported via NIS) in your + Keep in mind that at least one local account (i.e. + not imported via NIS) must exist in /etc/master.passwd and this account should also be a member of the group wheel. If there is something @@ -1864,8 +1856,8 @@ nis_client_enable="YES" To import all possible group entries from the NIS - server, add this line to your - /etc/group file: + server, add this line to + /etc/group: +:*:: @@ -1877,18 +1869,19 @@ nis_client_enable="YES" &prompt.root; /etc/netstart &prompt.root; service ypbind start - After completing these steps, you should be able to - run ypcat passwd and see the NIS + After completing these steps, the command, + ypcat passwd, should show the server's passwd map. - + + NIS Security - In general, any remote user can issue an RPC to - &man.ypserv.8; and retrieve the contents of your NIS maps, - provided the remote user knows your domainname. To prevent + In general, any remote user may issue an RPC to + &man.ypserv.8; and retrieve the contents of the NIS maps, + provided the remote user knows the domainname. To prevent such unauthorized transactions, &man.ypserv.8; supports a feature called securenets which can be used to restrict access to a given set of hosts. At startup, @@ -1934,7 +1927,7 @@ nis_client_enable="YES" While both of these access control mechanisms provide some security, they, like the privileged port test, are vulnerable to IP spoofing attacks. All - NIS-related traffic should be blocked at your + NIS-related traffic should be blocked at the firewall. Servers using /var/yp/securenets @@ -1951,15 +1944,15 @@ nis_client_enable="YES" Using /var/yp/securenets on a server with such an archaic implementation of TCP/IP is a really bad idea and will lead to loss of NIS functionality - for large parts of your network. + for large parts of the network. TCP Wrappers - The use of the TCP Wrapper - package increases the latency of your NIS server. The + The use of TCP Wrapper + increases the latency of the NIS server. The additional delay may be long enough to cause timeouts in client programs, especially in busy networks or with slow - NIS servers. If one or more of your client systems - suffers from these symptoms, you should convert the client + NIS servers. If one or more of the client systems + suffers from these symptoms, convert the client systems in question into NIS slave servers and force them to bind to themselves. @@ -1977,21 +1970,21 @@ nis_client_enable="YES" There is a way to bar specific users from logging on to a machine, even if they are present in the NIS database. To do - this, all you must do is add + this, add -username with the correct number of colons like other entries to the end of the /etc/master.passwd file on the client machine, where username is - the username of the user you wish to bar from logging in. + the username of the user to bar from logging in. The line with the blocked user must be before the + line for allowing NIS users. This should preferably be done using vipw, - since vipw will sanity check your changes + since vipw will sanity check the changes to /etc/master.passwd, as well as - automatically rebuild the password database when you finish - editing. For example, if we wanted to bar user + automatically rebuild the password database after + editing. For example, to bar user bill from logging on to - basie we would: + basie: basie&prompt.root; vipw [add -bill::::::::: to the end, exit] @@ -2037,10 +2030,10 @@ basie&prompt.root; netgroups The method shown in the previous section works reasonably - well if you need special rules for a very small number of - users and/or machines. On larger networks, you - will forget to bar some users from - logging onto sensitive machines, or you may even have to + well for special rules in an environment with small numbers of + users and/or machines. On larger networks, administrators + will likely forget to bar some users from + logging onto sensitive machines, or may even have to modify each machine separately, thus losing the main benefit of NIS: centralized administration. @@ -2054,15 +2047,15 @@ basie&prompt.root; Netgroups were developed to handle large, complex networks with hundreds of users and machines. On one hand, this is a - Good Thing if you are forced to deal with such a situation. + Good Thing in such a situation. On the other hand, this complexity makes it almost impossible to explain netgroups with really simple examples. The example used in the remainder of this section demonstrates this problem. - Let us assume that your successful introduction of NIS in - your laboratory caught your superiors' interest. Your next - job is to extend your NIS domain to cover some of the other + Let us assume that the successful introduction of NIS in + the laboratory caught a superiors' interest. The next + task is to extend the NIS domain to cover some of the other machines on campus. The two tables contain the names of the new users and new machines as well as brief descriptions of them. @@ -2121,7 +2114,7 @@ basie&prompt.root; war, death, famine, pollution - Your most important servers. Only the IT + The most important servers deployed. Only the IT employees are allowed to log onto these machines. @@ -2154,37 +2147,36 @@ basie&prompt.root; - If you tried to implement these restrictions by separately - blocking each user, you would have to add one + Attempting to implement these restrictions by separately + blocking each user, there would have to be an addition of the -user line to - each system's passwd for each user who is - not allowed to login onto that system. If you forget just one - entry, you could be in trouble. It may be feasible to do this - correctly during the initial setup, however you - will eventually forget to add the lines - for new users during day-to-day operations. After all, Murphy - was an optimist. + each system's passwd. One for each user + who is not allowed to login onto that system. Forgetting just one + entry, could cause significant trouble. It may be feasible to + do this correctly during the initial setup; however, eventually + someone will forget to add these lines + for new users. Handling this situation with netgroups offers several - advantages. Each user need not be handled separately; you - assign a user to one or more netgroups and allow or forbid - logins for all members of the netgroup. If you add a new - machine, you will only have to define login restrictions for - netgroups. If a new user is added, you will only have to add - the user to one or more netgroups. Those changes are + advantages. Each user need not be handled separately; they + would be assigned to one or more netgroups and allow or forbid + logins for all members of the netgroup. While adding a new + machine, login restrictions must be defined for all + netgroups. If a new user is added, they must be added + to one or more netgroups. Those changes are independent of each other: no more for each combination - of user and machine do... If your NIS setup is planned - carefully, you will only have to modify exactly one central - configuration file to grant or deny access to machines. + of user and machine do... If the NIS setup is planned + carefully, only one central configuration file + needs modified to grant or deny access to machines. The first step is the initialization of the NIS map - netgroup. FreeBSD's &man.ypinit.8; does not create this map - by default, but its NIS implementation will support it once it - has been created. To create an empty map, simply type + netgroup. &os;'s &man.ypinit.8; does not create this map + by default, but its NIS implementation will support it + after creation. To create an empty map, simply type ellington&prompt.root; vi /var/yp/netgroup - and start adding content. For our example, we need at + and begin adding content. For our example, we need at least four netgroups: IT employees, IT apprentices, normal employees and interns. @@ -2202,10 +2194,10 @@ INTERNS (,able,test-domain) (,baker, The name of the host(s) where the following items are - valid. If you do not specify a hostname, the entry is - valid on all hosts. If you do specify a hostname, you - will enter a realm of darkness, horror and utter - confusion. + valid. If a hostname is not specified, the entry is + valid on all hosts. If a hostname is specified, they + will need to be micro-managed within this + configuration. @@ -2214,43 +2206,41 @@ INTERNS (,able,test-domain) (,baker, - The NIS domain for the account. You can import - accounts from other NIS domains into your netgroup if you - are one of the unlucky fellows with more than one NIS - domain. + The NIS domain for the account. Accounts may be + imported from other NIS domains into a netgroup. - Each of these fields can contain wildcards. See + Each of these fields may contain wildcards. See &man.netgroup.5; for details. netgroups Netgroup names longer than 8 characters should not be - used, especially if you have machines running other - operating systems within your NIS domain. The names are - case sensitive; using capital letters for your netgroup + used, especially with machines running other + operating systems within the NIS domain. The names are + case sensitive; using capital letters for netgroup names is an easy way to distinguish between user, machine and netgroup names. - Some NIS clients (other than FreeBSD) cannot handle + Some NIS clients (other than &os;) cannot handle netgroups with a large number of entries. For example, some older versions of &sunos; start to cause trouble if a netgroup contains more than 15 entries. - You can circumvent this limit by creating several - sub-netgroups with 15 users or less and a real netgroup that - consists of the sub-netgroups: + This limit may be circumvented by creating several + sub-netgroups with 15 users or fewer and a real netgroup + consisting of the sub-netgroups: BIGGRP1 (,joe1,domain) (,joe2,domain) (,joe3,domain) [...] BIGGRP2 (,joe16,domain) (,joe17,domain) [...] BIGGRP3 (,joe31,domain) (,joe32,domain) BIGGROUP BIGGRP1 BIGGRP2 BIGGRP3 - You can repeat this process if you need more than 225 - users within a single netgroup. + Repeat this process if more than 225 + users will exist within a single netgroup. - Activating and distributing your new NIS map is + Activating and distributing the new NIS map is easy: ellington&prompt.root; cd /var/yp @@ -2260,7 +2250,7 @@ ellington&prompt.root; makenetgroup, netgroup.byhost and netgroup.byuser. Use &man.ypcat.1; to - check if your new NIS maps are available: + check if the new NIS maps are available: ellington&prompt.user; ypcat -k netgroup ellington&prompt.user; ypcat -k netgroup.byhost @@ -2268,13 +2258,13 @@ ellington&prompt.user; ypcat The output of the first command should resemble the contents of /var/yp/netgroup. The second - command will not produce output if you have not specified - host-specific netgroups. The third command can be used to + command will not produce output without specified + host-specific netgroups. The third command may be used to get the list of netgroups for a user. The client setup is quite simple. To configure the server - war, you only have to start - &man.vipw.8; and replace the line + war, use + &man.vipw.8; to replace the line +::::::::: @@ -2295,8 +2285,8 @@ ellington&prompt.user; ypcat ls -l will show the numerical ID instead of the username and find . -user joe -print will fail with No such user. To fix - this, you will have to import all user entries - without allowing them to login onto your + this, import all user entries + without allowing them to login into the servers. This can be achieved by adding another line to @@ -2306,9 +2296,9 @@ ellington&prompt.user; ypcat +:::::::::/sbin/nologin, meaning Import all entries but replace the shell with /sbin/nologin in the imported - entries. You can replace any field in the + entries. It is possible to replace any field in the passwd entry by placing a default value in - your /etc/master.passwd. + /etc/master.passwd. @@ -2320,9 +2310,9 @@ ellington&prompt.user; ypcat shell. - After this change, you will only have to change one NIS - map if a new employee joins the IT department. You could use - a similar approach for the less important servers by replacing + After this change, the NIS map will only need modified when + a new employee joins the IT department. A similar approach + for the less important servers may be used by replacing the old +::::::::: in their local version of /etc/master.passwd with something like this: @@ -2342,16 +2332,16 @@ ellington&prompt.user; ypcat change a few weeks later: The IT department starts hiring interns. The IT interns are allowed to use the normal workstations and the less important servers; and the IT - apprentices are allowed to login onto the main servers. You - add a new netgroup IT_INTERN, add the new - IT interns to this netgroup and start to change the - configuration on each and every machine... As the old saying + apprentices are allowed to login onto the main servers. + Add a new netgroup IT_INTERN, then add the + new IT interns to this netgroup and start to change the + configuration on each and every machine. As the old saying goes: Errors in centralized planning lead to global mess. NIS' ability to create netgroups from other netgroups can be used to prevent situations like these. One possibility is - the creation of role-based netgroups. For example, you could + the creation of role-based netgroups. For example, one might create a netgroup called BIGSRV to define the login restrictions for the important servers, another netgroup called SMALLSRV for the less @@ -2359,7 +2349,7 @@ ellington&prompt.user; ypcat USERBOX for the normal workstations. Each of these netgroups contains the netgroups that are allowed to login onto these machines. The new - entries for your NIS map netgroup should look like + entries for the NIS map netgroup should look like this: BIGSRV IT_EMP IT_APP @@ -2367,10 +2357,11 @@ SMALLSRV IT_EMP IT_APP ITINTERN USERBOX IT_EMP ITINTERN USERS This method of defining login restrictions works - reasonably well if you can define groups of machines with - identical restrictions. Unfortunately, this is the exception - and not the rule. Most of the time, you will need the ability - to define login restrictions on a per-machine basis. + reasonably well when it is possible to define groups of machines + with identical restrictions. Unfortunately, this is the + exception and not the rule. Most of the time, the ability + to define login restrictions on a per-machine basis is + required. Machine-specific netgroup definitions are the other possibility to deal with the policy change outlined above. In @@ -2386,8 +2377,8 @@ USERBOX IT_EMP ITINTERN USERS+@BOXNAME::::::::: +:::::::::/sbin/nologin - Once you have completed this task for all your machines, - you will not have to modify the local versions of + Once this task is completed on all the machines, + there is no longer a need to modify the local versions of /etc/master.passwd ever again. All further changes can be handled by modifying the NIS map. Here is an example of a possible netgroup map for this @@ -2429,32 +2420,33 @@ ONE SECURITY TWO (,hotel,test-domain) # [...more groups to follow] - If you are using some kind of database to manage your user - accounts, you should be able to create the first part of the - map with your database's report tools. This way, new users + If some kind of database is used to manage the user + accounts, it may be possible to create the first part of the + map using the database's reporting tools. This way, new users will automatically have access to the boxes. One last word of caution: It may not always be advisable - to use machine-based netgroups. If you are deploying a couple + to use machine-based netgroups. When deploying a couple of dozen or even hundreds of identical machines for student - labs, you should use role-based netgroups instead of - machine-based netgroups to keep the size of the NIS map within - reasonable limits. + labs, the use of role-based netgroups instead of + machine-based netgroups may be used to keep the size of the NIS + map within reasonable limits. Important Things to Remember - There are still a couple of things that you will need to - do differently now that you are in an NIS environment. + There are still a couple of things administrators need to + do differently now that machines are in an NIS + environment. - Every time you wish to add a user to the lab, you - must add it to the master NIS server - only, and you must remember - to rebuild the NIS maps. If you forget to do - this, the new user will not be able to login anywhere + Every time a new user is added to the lab, they + must be added to the master NIS server + only, and remember + to rebuild the NIS maps. If this step is + missed, the new user will not be able to login anywhere except on the NIS master. For example, if we needed to add a new user jsmith to the lab, we would: @@ -2463,16 +2455,17 @@ TWO (,hotel,test-domain) &prompt.root; cd /var/yp &prompt.root; make test-domain - You could also run adduser jsmith + The user may also be added using + adduser jsmith instead of pw useradd jsmith. Keep the administration accounts out of the - NIS maps. You do not want to be propagating - administrative accounts and passwords to machines that - will have users that should not have access to those - accounts. + NIS maps. These users and passwords should + not be propagating to all machines. Especially if these + machines will have users whom should not have access to + those accounts. Keep the NIS master and slave secure, and @@ -2482,8 +2475,9 @@ TWO (,hotel,test-domain) login to the lab. This is the chief weakness of any centralized - administration system. If you do not protect your NIS - servers, you will have a lot of angry users! + administration system. If the NIS servers are not + protected, there will be a lot of angry users and + unhappy management! @@ -2491,19 +2485,19 @@ TWO (,hotel,test-domain) NIS v1 Compatibility - FreeBSD's ypserv has some - support for serving NIS v1 clients. FreeBSD's NIS - implementation only uses the NIS v2 protocol, however other + &os;'s ypserv has some + support for serving NIS v1 clients. &os;'s NIS *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Mon May 27 21:46:21 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 48BF8530; Mon, 27 May 2013 21:46:21 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 213FAED5; Mon, 27 May 2013 21:46:21 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4RLkLLm071306; Mon, 27 May 2013 21:46:21 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4RLkKnN071305; Mon, 27 May 2013 21:46:21 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305272146.r4RLkKnN071305@svn.freebsd.org> From: Tom Rhodes Date: Mon, 27 May 2013 21:46:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41761 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 21:46:21 -0000 Author: trhodes Date: Mon May 27 21:46:20 2013 New Revision: 41761 URL: http://svnweb.freebsd.org/changeset/doc/41761 Log: Change "role" to class in to unbreak lint. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Mon May 27 21:43:35 2013 (r41760) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Mon May 27 21:46:20 2013 (r41761) @@ -359,7 +359,7 @@ Info: Lists information about open fil All package installation files are stored in the package database directory, - /var/db/pkg. + /var/db/pkg. Installing a Package @@ -1796,7 +1796,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ configuration file alteration, or perhaps the application will just generate a configuration file. Most applications will have documentation installed into - /usr/local/share/doc and + /usr/local/share/doc and manual pages. This documentation should be consulted before continuing. Some applications run services which must be added to the /etc/rc.conf file before @@ -1820,7 +1820,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ &prompt.root; pkg_info -L foopackage-1.0.0 | less Configuration files are always installed in - /usr/local/etc + /usr/local/etc and should definitely be consulted before attempting to use the new application. From owner-svn-doc-projects@FreeBSD.ORG Mon May 27 22:30:20 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1DE5331F; Mon, 27 May 2013 22:30:20 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 102BF120; Mon, 27 May 2013 22:30:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4RMUJtd085234; Mon, 27 May 2013 22:30:19 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4RMUJwb085233; Mon, 27 May 2013 22:30:19 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201305272230.r4RMUJwb085233@svn.freebsd.org> From: Tom Rhodes Date: Mon, 27 May 2013 22:30:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41763 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 22:30:20 -0000 Author: trhodes Date: Mon May 27 22:30:19 2013 New Revision: 41763 URL: http://svnweb.freebsd.org/changeset/doc/41763 Log: Better section titles. Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Mon May 27 22:11:02 2013 (r41762) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mac/chapter.xml Mon May 27 22:30:19 2013 (r41763) @@ -769,7 +769,7 @@ test: biba/high - The &man.mac.seeotheruids.4; Module + The MAC See Other UIDs Policy MAC See Other UIDs Policy @@ -824,7 +824,7 @@ test: biba/high - The &man.mac.bsdextended.4; Module + The MAC BSD Extended Policy MAC @@ -904,7 +904,7 @@ test: biba/high - The &man.mac.ifoff.4; Module + The MAC Interface Silencing Policy MAC Interface Silencing Policy @@ -955,7 +955,7 @@ test: biba/high - The &man.mac.portacl.4; Module + The MAC Port Access Control List Policy MAC Port Access Control List Policy @@ -1069,7 +1069,7 @@ net.inet.ip.portrange.reservedhigh=0 - The &man.mac.partition.4; Module + The MAC Partition Policy MAC Process Partition Policy From owner-svn-doc-projects@FreeBSD.ORG Tue May 28 20:24:09 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B7FD736B; Tue, 28 May 2013 20:24:09 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.37]) by mx1.freebsd.org (Postfix) with ESMTP id 4007C35E; Tue, 28 May 2013 20:24:08 +0000 (UTC) X-AuditID: 12074425-b7f986d00000082c-13-51a51135051a Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id D6.CA.02092.53115A15; Tue, 28 May 2013 16:19:01 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r4SKJ18V029556; Tue, 28 May 2013 16:19:01 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r4SKIwPo020692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 May 2013 16:19:00 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r4SKIvRE005453; Tue, 28 May 2013 16:18:57 -0400 (EDT) Date: Tue, 28 May 2013 16:18:57 -0400 (EDT) From: Benjamin Kaduk To: Tom Rhodes Subject: Re: svn commit: r41757 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers In-Reply-To: <201305272048.r4RKmBFF051879@svn.freebsd.org> Message-ID: References: <201305272048.r4RKmBFF051879@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsUixCmqrWsquDTQ4OhrC4sfHw8xWSw8s5rZ 4u+GDywOzB4zPs1nCWCM4rJJSc3JLEst0rdL4MqYckmr4JFNxZT3PUwNjJf1uxg5OSQETCQm HZrADGGLSVy4t54NxBYS2Mco8W+ZRRcjF5C9kVHi9qbzLBDOISaJVateMUI4DYwSp6Z2ALVz cLAIaEt0d0aCdLMJqEjMfLMRbJIIkH334GkmEJtZwEZiwoMF7CC2sECexOole1lBbE4BK4lP E9eygYzhFXCQ6D3FDHGEpcSaN28ZQWxRAR2J1funsIDYvAKCEidnPmGBGGkp8W/tL9YJjIKz kKRmIUktYGRaxSibklulm5uYmVOcmqxbnJyYl5dapGuhl5tZopeaUrqJERSk7C6qOxgnHFI6 xCjAwajEwxvwdUmgEGtiWXFl7iFGSQ4mJVHe5bxLA4X4kvJTKjMSizPii0pzUosPMUpwMCuJ 8F5aCVTOm5JYWZValA+TkuZgURLnvZFy019IID2xJDU7NbUgtQgmK8PBoSTBe5ofaKhgUWp6 akVaZk4JQpqJgxNkOA/QcH8BoBre4oLE3OLMdIj8KUZFKXHefSAJAZBERmkeXC8sibxiFAd6 RZh3GkgVDzABwXW/AhrMBDRYnHkxyOCSRISUVANjSmfk2ysC7M4nP91Yx7pb9us0HgErNn9u JtU1m7fNmvG0JXyx/K1/OUG9IXdPHGc7b1R5xvMTk+4rjaq4/v+NAr/dargOrPl8d+33zQti w1MdNnXkm3+6GzXdwPTitXDWLzPOb31c4ra29ER/d8+E0AUiPbGpj26JnY2wyfr7bfOxhyfm sTyfrcRSnJFoqMVcVJwIANSrZyT9AgAA Cc: svn-doc-projects@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 20:24:09 -0000 On Mon, 27 May 2013, Tom Rhodes wrote: > Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml > ============================================================================== > --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Mon May 27 20:33:31 2013 (r41756) > +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Mon May 27 20:48:10 2013 (r41757) > @@ -2154,37 +2147,36 @@ basie&prompt.root; > > > > - If you tried to implement these restrictions by separately > - blocking each user, you would have to add one > + Attempting to implement these restrictions by separately > + blocking each user, there would have to be an addition of the > -user line to I think this sentence is not quite right with these changes -- there is no subject who is doing the attempting. I think referring to "an attempt to implement these restrictions [...] would require [...]" would be better. > - each system's passwd for each user who is > - not allowed to login onto that system. If you forget just one > - entry, you could be in trouble. It may be feasible to do this > - correctly during the initial setup, however you > - will eventually forget to add the lines > - for new users during day-to-day operations. After all, Murphy > - was an optimist. > + each system's passwd. One for each user > + who is not allowed to login onto that system. Forgetting just one This sentence is incomplete as well, it is dependent on the previous one. > + entry, could cause significant trouble. It may be feasible to This comma is not needed. > + do this correctly during the initial setup; however, eventually > + someone will forget to add these lines > + for new users. > > Handling this situation with netgroups offers several > - advantages. Each user need not be handled separately; you > - assign a user to one or more netgroups and allow or forbid > - logins for all members of the netgroup. If you add a new > - machine, you will only have to define login restrictions for > - netgroups. If a new user is added, you will only have to add > - the user to one or more netgroups. Those changes are > + advantages. Each user need not be handled separately; they > + would be assigned to one or more netgroups and allow or forbid > + logins for all members of the netgroup. While adding a new The "allow or forbid logins" clause seems to be dangling, here; a rewrite as "logins would be allowed or forbidden for all members of the netgroup" should help. > + machine, login restrictions must be defined for all > + netgroups. If a new user is added, they must be added > + to one or more netgroups. Those changes are > independent of each other: no more for each combination > - of user and machine do... If your NIS setup is planned > - carefully, you will only have to modify exactly one central > - configuration file to grant or deny access to machines. > + of user and machine do... If the NIS setup is planned > + carefully, only one central configuration file > + needs modified to grant or deny access to machines. s/modified/modification/ > > The first step is the initialization of the NIS map > - netgroup. FreeBSD's &man.ypinit.8; does not create this map > - by default, but its NIS implementation will support it once it > - has been created. To create an empty map, simply type > + netgroup. &os;'s &man.ypinit.8; does not create this map > + by default, but its NIS implementation will support it > + after creation. To create an empty map, simply type > > ellington&prompt.root; vi /var/yp/netgroup > > - and start adding content. For our example, we need at > + and begin adding content. For our example, we need at > least four netgroups: IT employees, IT apprentices, normal > employees and interns. > > @@ -2202,10 +2194,10 @@ INTERNS (,able,test-domain) (,baker, > > > The name of the host(s) where the following items are > - valid. If you do not specify a hostname, the entry is > - valid on all hosts. If you do specify a hostname, you > - will enter a realm of darkness, horror and utter > - confusion. > + valid. If a hostname is not specified, the entry is > + valid on all hosts. If a hostname is specified, they > + will need to be micro-managed within this > + configuration. "a hostname" and "they" have mismatching pluralness. > > > > @@ -2320,9 +2310,9 @@ ellington&prompt.user; ypcat > shell. > > > - After this change, you will only have to change one NIS > - map if a new employee joins the IT department. You could use > - a similar approach for the less important servers by replacing > + After this change, the NIS map will only need modified when s/modified/modification/ > + a new employee joins the IT department. A similar approach > + for the less important servers may be used by replacing > the old +::::::::: in their local version > of /etc/master.passwd with something like > this: > @@ -2429,32 +2420,33 @@ ONE SECURITY > - to use machine-based netgroups. If you are deploying a couple > + to use machine-based netgroups. When deploying a couple > of dozen or even hundreds of identical machines for student > - labs, you should use role-based netgroups instead of > - machine-based netgroups to keep the size of the NIS map within > - reasonable limits. > + labs, the use of role-based netgroups instead of > + machine-based netgroups may be used to keep the size of the NIS "use of [...] may be used" is redundant. > + map within reasonable limits. > [...] > + Every time a new user is added to the lab, they > + must be added to the master NIS server > + only, and remember > + to rebuild the NIS maps. If this step is The person remembering to rebuild the maps is not the new user, but the text here implies that they are one and the same. Probably just ", and the NIS maps must be rebuilt" is consistent with the new style of the document. > + missed, the new user will not be able to login anywhere "missed" is a strange word, here. Perhaps "skipped" or "omitted"? > except on the NIS master. For example, if we needed to > add a new user jsmith to the lab, we > would: > @@ -2463,16 +2455,17 @@ TWO (,hotel,test-domain) > - NIS maps. You do not want to be propagating > - administrative accounts and passwords to machines that > - will have users that should not have access to those > - accounts. > + NIS maps. These users and passwords should > + not be propagating to all machines. Especially if these propagating vs. propagated is an interesting question, here. -Ben > + machines will have users whom should not have access to > + those accounts. > > > Keep the NIS master and slave secure, and > > *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Wed May 29 00:30:48 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F0E02FFC; Wed, 29 May 2013 00:30:47 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id B29C4809; Wed, 29 May 2013 00:30:47 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r4T0UkkW049549; Tue, 28 May 2013 18:30:46 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r4T0UkOi049546; Tue, 28 May 2013 18:30:46 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 28 May 2013 18:30:46 -0600 (MDT) From: Warren Block To: Benjamin Kaduk Subject: Re: svn commit: r41757 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers In-Reply-To: Message-ID: References: <201305272048.r4RKmBFF051879@svn.freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 28 May 2013 18:30:46 -0600 (MDT) Cc: svn-doc-projects@freebsd.org, Tom Rhodes , doc-committers@freebsd.org X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 00:30:48 -0000 On Tue, 28 May 2013, Benjamin Kaduk wrote: > On Mon, 27 May 2013, Tom Rhodes wrote: > >> Modified: >> projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml >> ============================================================================== >> --- >> projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml >> Mon May 27 20:33:31 2013 (r41756) >> +++ >> projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml >> Mon May 27 20:48:10 2013 (r41757) >> + NIS maps. These users and passwords should >> + not be propagating to all machines. Especially if these > > propagating vs. propagated is an interesting question, here. The "should not" is unclear. Does it mean * "it is not supposed to happen, but sometimes does anyway" * "it is undesirable from a security standpoint" From owner-svn-doc-projects@FreeBSD.ORG Wed May 29 04:16:09 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E1384F95 for ; Wed, 29 May 2013 04:16:09 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by mx1.freebsd.org (Postfix) with ESMTP id B2750275 for ; Wed, 29 May 2013 04:16:09 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id u16so24090283iet.28 for ; Tue, 28 May 2013 21:16:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=Ls5/g+N1AHK0bCjyE+UdH2wQcI85vdDrRkleLdfZgGY=; b=FWYksyInQhNRXyGPXinvcA72FKAs0Xd5U7uRxK2asrRxGN33ZwQj1/Gkn0u/+zsFFz rqoTM58wn2oqvK9XWJnsuNNMNC/N6Q6TQWVrPiPcoMMu/2aipJ+BNwYUXqjujErOuf7G gm24PohSUlRtIM0fPuJ5G8Lo+5tc9bAnKT8O5dgGZLEXn5tsDFPCWX131q19uNTbDt+6 ZehJPleqJIkpvOfCdvBWcoV087oJE62tZalJV7SU39YmA59cvjjs/ctGRAUYshCWboeH Suvs0+Xadbikgtwe9D2GhWoQeIK3DUe/e8zIP4tu5og/QmbSbVa1y5aZqC8Zp9HvB8nb LdmA== X-Received: by 10.50.111.233 with SMTP id il9mr2282032igb.103.1369800969457; Tue, 28 May 2013 21:16:09 -0700 (PDT) Received: from [10.0.0.53] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id n5sm21335889igx.1.2013.05.28.21.16.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 21:16:08 -0700 (PDT) Sender: Warner Losh Subject: Re: svn commit: r41757 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Tue, 28 May 2013 22:16:01 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201305272048.r4RKmBFF051879@svn.freebsd.org> To: Warren Block X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQl7/BuEjwYD1EAZIzjWriw1gMXAafZ0ZlgQodDgvVq0OWvnwsbJ8ff1NhNJUdXCY0L5Gvzr Cc: svn-doc-projects@freebsd.org, Tom Rhodes , doc-committers@freebsd.org, Benjamin Kaduk X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 04:16:09 -0000 On May 28, 2013, at 6:30 PM, Warren Block wrote: > On Tue, 28 May 2013, Benjamin Kaduk wrote: >=20 >> On Mon, 27 May 2013, Tom Rhodes wrote: >>=20 >>> Modified: = projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers= /chapter.xml >>> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >>> --- = projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers= /chapter.xml Mon May 27 20:33:31 2013 (r41756) >>> +++ = projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers= /chapter.xml Mon May 27 20:48:10 2013 (r41757) >=20 >>> + NIS maps. These users and passwords should >>> + not be propagating to all machines. Especially if these >>=20 >> propagating vs. propagated is an interesting question, here. >=20 > The "should not" is unclear. Does it mean >=20 > * "it is not supposed to happen, but sometimes does anyway" > * "it is undesirable from a security standpoint" You shouldn't do it (it =3D=3D add them to the NIS master password file) = because it is a security problem if you do. Warner From owner-svn-doc-projects@FreeBSD.ORG Wed May 29 04:45:21 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DA146BB0; Wed, 29 May 2013 04:45:21 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 835B5763; Wed, 29 May 2013 04:45:21 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r4T4jJaM050676; Tue, 28 May 2013 22:45:19 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r4T4jJC7050673; Tue, 28 May 2013 22:45:19 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 28 May 2013 22:45:19 -0600 (MDT) From: Warren Block To: Warner Losh Subject: Re: svn commit: r41757 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers In-Reply-To: Message-ID: References: <201305272048.r4RKmBFF051879@svn.freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 28 May 2013 22:45:19 -0600 (MDT) Cc: svn-doc-projects@freebsd.org, Tom Rhodes , doc-committers@freebsd.org, Benjamin Kaduk X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 04:45:21 -0000 On Tue, 28 May 2013, Warner Losh wrote: > > On May 28, 2013, at 6:30 PM, Warren Block wrote: > >> On Tue, 28 May 2013, Benjamin Kaduk wrote: >> >>> On Mon, 27 May 2013, Tom Rhodes wrote: >>> >>>> Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml >>>> ============================================================================== >>>> --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Mon May 27 20:33:31 2013 (r41756) >>>> +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Mon May 27 20:48:10 2013 (r41757) >> >>>> + NIS maps. These users and passwords should >>>> + not be propagating to all machines. Especially if these >>> >>> propagating vs. propagated is an interesting question, here. >> >> The "should not" is unclear. Does it mean >> >> * "it is not supposed to happen, but sometimes does anyway" >> * "it is undesirable from a security standpoint" > > You shouldn't do it (it == add them to the NIS master password file) because it is a security problem if you do. Right. This is another situation where the imperative is better. Don't tell them they shouldn't do it, just tell them *don't* do it, and why: Do not propagate these users and passwords to all machines... because the sky will open and vast clouds of devious, parachuted weasels will fall upon your ancestral lands, each with sharp teeth, claws, a bitter attitude, and a score to settle, most having failed in business school, or, in a few cases, the fast food industry. From owner-svn-doc-projects@FreeBSD.ORG Wed May 29 19:21:26 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A86FAFB5; Wed, 29 May 2013 19:21:26 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 8925C241; Wed, 29 May 2013 19:21:26 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4TJLQX1015183; Wed, 29 May 2013 19:21:26 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4TJLP5G015180; Wed, 29 May 2013 19:21:25 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305291921.r4TJLP5G015180@svn.freebsd.org> From: Gabor Kovesdan Date: Wed, 29 May 2013 19:21:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41774 - in projects/db5: da_DK.ISO8859-1/share/xml de_DE.ISO8859-1/share/xml el_GR.ISO8859-7/share/xml en_US.ISO8859-1/share/xml es_ES.ISO8859-1/share/xml fr_FR.ISO8859-1/share/xml hu_... X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 19:21:26 -0000 Author: gabor Date: Wed May 29 19:21:25 2013 New Revision: 41774 URL: http://svnweb.freebsd.org/changeset/doc/41774 Log: - Drop SGML catalogs - Drop DSSSL stylesheets - Drop some DSSSL-related comments and Makefile code Deleted: projects/db5/da_DK.ISO8859-1/share/xml/catalog projects/db5/da_DK.ISO8859-1/share/xml/freebsd.dsl projects/db5/de_DE.ISO8859-1/share/xml/catalog projects/db5/de_DE.ISO8859-1/share/xml/freebsd.dsl projects/db5/el_GR.ISO8859-7/share/xml/catalog projects/db5/el_GR.ISO8859-7/share/xml/freebsd.dsl projects/db5/en_US.ISO8859-1/share/xml/catalog projects/db5/en_US.ISO8859-1/share/xml/freebsd.dsl projects/db5/es_ES.ISO8859-1/share/xml/catalog projects/db5/es_ES.ISO8859-1/share/xml/freebsd.dsl projects/db5/fr_FR.ISO8859-1/share/xml/catalog projects/db5/fr_FR.ISO8859-1/share/xml/freebsd.dsl projects/db5/hu_HU.ISO8859-2/share/xml/catalog projects/db5/hu_HU.ISO8859-2/share/xml/freebsd.dsl projects/db5/it_IT.ISO8859-15/share/xml/catalog projects/db5/it_IT.ISO8859-15/share/xml/freebsd.dsl projects/db5/ja_JP.eucJP/share/xml/catalog projects/db5/ja_JP.eucJP/share/xml/freebsd.dsl projects/db5/mn_MN.UTF-8/share/xml/catalog projects/db5/mn_MN.UTF-8/share/xml/freebsd.dsl projects/db5/nl_NL.ISO8859-1/share/xml/catalog projects/db5/nl_NL.ISO8859-1/share/xml/freebsd.dsl projects/db5/pl_PL.ISO8859-2/share/xml/catalog projects/db5/pl_PL.ISO8859-2/share/xml/freebsd.dsl projects/db5/pt_BR.ISO8859-1/share/xml/catalog projects/db5/pt_BR.ISO8859-1/share/xml/freebsd.dsl projects/db5/ru_RU.KOI8-R/share/xml/catalog projects/db5/ru_RU.KOI8-R/share/xml/freebsd.dsl projects/db5/share/xml/catalog projects/db5/share/xml/catalog-cwd.xml projects/db5/share/xml/default.dsl projects/db5/share/xml/freebsd-common.dsl projects/db5/share/xml/freebsd-print.dsl projects/db5/share/xml/freebsd.dsl projects/db5/share/xml/spellcheck.dsl projects/db5/sr_YU.ISO8859-2/share/xml/catalog projects/db5/sr_YU.ISO8859-2/share/xml/freebsd.dsl projects/db5/zh_CN.GB2312/share/xml/catalog projects/db5/zh_CN.GB2312/share/xml/freebsd.dsl projects/db5/zh_TW.Big5/share/xml/catalog projects/db5/zh_TW.Big5/share/xml/freebsd.dsl Modified: projects/db5/share/images/callouts/gen.sh projects/db5/share/mk/doc.docbook.mk projects/db5/share/mk/doc.images.mk Modified: projects/db5/share/images/callouts/gen.sh ============================================================================== --- projects/db5/share/images/callouts/gen.sh Wed May 29 17:50:03 2013 (r41773) +++ projects/db5/share/images/callouts/gen.sh Wed May 29 19:21:25 2013 (r41774) @@ -2,9 +2,6 @@ # $FreeBSD$ -# For more than 30 adjust %callout-graphics-number-limit% -# in doc/share/xml/freebsd-html.dsl - for i in `jot 9 1` do convert -size 101x101 xc:green -transparent green -fill black -draw 'circle 50,50 50' -fill white -stroke none -pointsize 90 -gravity center -kerning -5 -font Helvetica-bold -draw "text 0,5 \"$i\"" -scale '12x12' $i.png Modified: projects/db5/share/mk/doc.docbook.mk ============================================================================== --- projects/db5/share/mk/doc.docbook.mk Wed May 29 17:50:03 2013 (r41773) +++ projects/db5/share/mk/doc.docbook.mk Wed May 29 19:21:25 2013 (r41774) @@ -51,12 +51,6 @@ # CSS_SHEET Full path to a CSS stylesheet suitable for DocBook. # Default is ${DOC_PREFIX}/share/misc/docbook.css # -# -# SPELLCHECK Use the special spellcheck.dsl stylesheet to render -# HTML that is suitable for processing through a -# spellchecker. For example, PGP keys and filenames -# will be omitted from this output. -# # Package building options: # # BZIP2_PACKAGE Use bzip2(1) utility to compress package tarball @@ -76,9 +70,6 @@ RENDERENGINE?= jade XMLDECL?= /usr/local/share/sgml/docbook/dsssl/modular/dtds/decls/xml.dcl -DSLHTML?= ${DOC_PREFIX}/share/xml/spellcheck.dsl -DSLPRINT?= ${DOC_PREFIX}/share/xml/default.dsl - XSLPROF?= /usr/local/share/xsl/docbook/profiling/profile.xsl XSLXHTML?= ${DOC_PREFIX}/${LANGCODE}/share/xsl/freebsd-xhtml.xsl XSLXHTMLCHUNK?= ${DOC_PREFIX}/${LANGCODE}/share/xsl/freebsd-xhtml-chunk.xsl @@ -116,8 +107,6 @@ KNOWN_FORMATS= html html.tar html-split CSS_SHEET?= ${DOC_PREFIX}/share/misc/docbook.css -PRINTOPTS?= -ioutput.print -d ${DSLPRINT} ${PRINTFLAGS} - .if defined(WWWFREEBSDORG) HTMLFLAGS+= -V %html-header-script% .endif Modified: projects/db5/share/mk/doc.images.mk ============================================================================== --- projects/db5/share/mk/doc.images.mk Wed May 29 17:50:03 2013 (r41773) +++ projects/db5/share/mk/doc.images.mk Wed May 29 19:21:25 2013 (r41774) @@ -211,8 +211,7 @@ IMAGES_LIB_DIR?= ${.CURDIR}/../../../sha # The name of the directory *in* the document directory where files and # directory hierarchies should be copied to. "images" is too generic, and # might clash with local document images, so use "imagelib" by default -# instead. If you redefine this then you must also update the -# %callout-graphics-path% variable in the .dsl file. +# instead. # LOCAL_IMAGES_LIB_DIR?= imagelib CLEANDIRS+= ${LOCAL_IMAGES_LIB_DIR} From owner-svn-doc-projects@FreeBSD.ORG Wed May 29 19:26:44 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EA9512A0; Wed, 29 May 2013 19:26:44 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id CC88A27D; Wed, 29 May 2013 19:26:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4TJQi4c016157; Wed, 29 May 2013 19:26:44 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4TJQiDZ016155; Wed, 29 May 2013 19:26:44 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305291926.r4TJQiDZ016155@svn.freebsd.org> From: Gabor Kovesdan Date: Wed, 29 May 2013 19:26:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41775 - projects/db5/share/mk X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 19:26:45 -0000 Author: gabor Date: Wed May 29 19:26:44 2013 New Revision: 41775 URL: http://svnweb.freebsd.org/changeset/doc/41775 Log: - Remove Jade-related code Modified: projects/db5/share/mk/doc.commands.mk projects/db5/share/mk/doc.docbook.mk Modified: projects/db5/share/mk/doc.commands.mk ============================================================================== --- projects/db5/share/mk/doc.commands.mk Wed May 29 19:21:25 2013 (r41774) +++ projects/db5/share/mk/doc.commands.mk Wed May 29 19:26:44 2013 (r41775) @@ -69,13 +69,6 @@ HTML2PDBOPTS?= -y -d0 -Idef ${HTML2PDBFL HTML2TXT?= ${PREFIX}/bin/w3m HTML2TXTOPTS?= -dump ${HTML2TXTFLAGS} -.if exists(${PREFIX}/bin/jade) && !defined(OPENJADE) -JADE?= ${ENV} SP_ENCODING=XML ${PREFIX}/bin/jade -.else -JADE?= ${ENV} SP_ENCODING=XML ${PREFIX}/bin/openjade -JADEFLAGS+= -V openjade -.endif - XMLLINT?= ${PREFIX}/bin/xmllint XSLTPROC?= ${PREFIX}/bin/xsltproc @@ -93,10 +86,6 @@ TEX_CMD?= ${PREFIX}/bin/tex PDFTEX_CMD?= ${PREFIX}/bin/pdftex .endif LATEX_CMD?= ${PREFIX}/bin/latex -JADETEX_CMD?= ${PDFTEX_CMD} "&jadetex" -JADETEX_PREPROCESS?= /bin/cat -PDFJADETEX_CMD?=${PDFTEX_CMD} "&pdfjadetex" -PDFJADETEX_PREPROCESS?= /bin/cat PS2PDF?= ${PREFIX}/bin/ps2pdf FOP_CMD?= ${PREFIX}/share/fop/fop.sh XEP_CMD?= sh ${HOME}/XEP/xep.sh @@ -104,26 +93,6 @@ JAVA_CMD?= ${PREFIX}/bin/javavm SAXON_CMD?= ${JAVA_CMD} -jar ${PREFIX}/share/java/classes/saxon.jar # -# Currently, we have to use the FixRTF utility available as textproc/fixrtf -# to apply several RTF fixups: -# -# 1. Embed PNGs into RTF. (Option: -p) -# 2. Embed FreeBSD-specific information into RTF, such as organization name, -# building time. But unfortunately, so far only Microsoft Word can read -# them. In contrast, Microsoft Word Viewer and OpenOffice even cannot read -# this kind of information from RTF created by Microsoft Word and -# OpenOffice. (Option: -i) -# 3. Do some locale-specific fixing. (Option: -e ) -# -# This is a transitional solution before Jade/OpenJade provides these features. -# -FIXRTF?= ${PREFIX}/bin/fixrtf -FIXRTFOPTS?= -i -p -.if defined(SP_ENCODING) -FIXRTFOPTS+= -e ${SP_ENCODING} -.endif - -# # Image processing # Modified: projects/db5/share/mk/doc.docbook.mk ============================================================================== --- projects/db5/share/mk/doc.docbook.mk Wed May 29 19:21:25 2013 (r41774) +++ projects/db5/share/mk/doc.docbook.mk Wed May 29 19:26:44 2013 (r41775) @@ -31,15 +31,6 @@ # # Variables used by both users and documents: # -# XMLFLAGS Additional options to pass to various XML -# processors (e.g., jade, nsgmls). Typically -# used to define "IGNORE" entities to "INCLUDE" -# with "-i" -# -# JADEFLAGS Additional options to pass to Jade. Typically -# used to set additional variables, such as -# "%generate-article-toc%". -# # EXTRA_CATALOGS Additional catalog files that should be used by # any XML processing applications. # @@ -65,9 +56,6 @@ MASTERDOC?= ${.CURDIR}/${DOC}.xml -# Either jade or fop -RENDERENGINE?= jade - XMLDECL?= /usr/local/share/sgml/docbook/dsssl/modular/dtds/decls/xml.dcl XSLPROF?= /usr/local/share/xsl/docbook/profiling/profile.xsl @@ -82,24 +70,6 @@ XSLSCH?= /usr/local/share/xsl/iso-schema IMAGES_LIB?= SCHEMATRONS?= ${DOC_PREFIX}/share/xml/freebsd.sch - -.if exists(${PREFIX}/bin/jade) && !defined(OPENJADE) -JADECATALOG?= ${PREFIX}/share/sgml/jade/catalog -.else -JADECATALOG?= ${PREFIX}/share/sgml/openjade/catalog -.endif -FREEBSDCATALOG= ${DOC_PREFIX}/share/xml/catalog -LANGUAGECATALOG=${DOC_PREFIX}/${LANGCODE}/share/xml/catalog -DSSSLCATALOG= ${PREFIX}/share/sgml/docbook/dsssl/modular/catalog -.for c in ${LANGUAGECATALOG} ${FREEBSDCATALOG} ${DSSSLCATALOG} ${JADECATALOG} -.if exists(${c}) -CATALOGS+= -c ${c} -.endif -.endfor - -JADEOPTS?= -ijade.compat -w no-valid ${JADEFLAGS} \ - -D ${IMAGES_EN_DIR}/${DOC}s/${.CURDIR:T} -D ${CANONICALOBJDIR} \ - ${CATALOGS} XSLTPROCOPTS?= --nonet KNOWN_FORMATS= html html.tar html-split html-split.tar \ @@ -107,30 +77,6 @@ KNOWN_FORMATS= html html.tar html-split CSS_SHEET?= ${DOC_PREFIX}/share/misc/docbook.css -.if defined(WWWFREEBSDORG) -HTMLFLAGS+= -V %html-header-script% -.endif -.if !defined(WITH_INLINE_LEGALNOTICE) || empty(WITH_INLINE_LEGALNOTICE) -HTMLFLAGS+= -V %generate-legalnotice-link% -.endif -.if defined(WITH_ARTICLE_TOC) && !empty(WITH_ARTICLE_TOC) -HTMLFLAGS+= -V %generate-article-toc% -PRINTFLAGS+= -V %generate-article-toc% -.endif -.if defined(WITH_BIBLIOXREF_TITLE) && !empty(WITH_BIBLIOXREF_TITLE) -HTMLFLAGS+= -V biblio-xref-title -PRINTFLAGS+= -V biblio-xref-title -.endif -.if defined(WITH_DOCFORMAT_NAVI_LINK) && !empty(WITH_DOCFORMAT_NAVI_LINK) -HTMLFLAGS+= -V %generate-docformat-navi-link% -.elif (${FORMATS:Mhtml} == "html") && (${FORMATS:Mhtml-split} == "html-split") -HTMLFLAGS+= -V %generate-docformat-navi-link% -.endif -.if defined(WITH_ALL_TRADEMARK_SYMBOLS) && !empty(WITH_ALL_TRADEMARK_SYMBOLS) -HTMLFLAGS+= -V %show-all-trademark-symbols% -PRINTFLAGS+= -V %show-all-trademark-symbols% -.endif - # # Instruction for bsd.subdir.mk to not to process SUBDIR directive. # It is not necessary since doc.docbook.mk do it too. @@ -298,30 +244,6 @@ CLEANFILES+= ${.CURDIR:T}.${_curformat}. all: ${SRCS} ${_docs} -# put languages which have a problem on rendering printable formats -# by using TeX to NO_TEX_LANG. -NO_TEX_LANG?= ja_JP.eucJP ru_RU.KOI8-R - -# put languages which have a problem on rendering the plain text format -# by using links1 to NO_PLAINTEXT_LANG. -NO_PLAINTEXT_LANG?= ja_JP.eucJP - -# put languages which have a problem on rendering the rtf format -# by using jade to NO_RTF_LANG. -NO_RTF_LANG?= - -.for _L in ${LANGCODE} -.if ${NO_TEX_LANG:M${_L}} != "" -NO_TEX= yes -.endif -.if ${NO_PLAINTEXT_LANG:M${_L}} != "" -NO_PLAINTEXT= yes -.endif -.if ${NO_RTF_LANG:M${_L}} != "" -NO_RTF= yes -.endif -.endfor - .if defined(SCHEMATRONS) .for sch in ${SCHEMATRONS} schxslts+= ${sch}.xsl @@ -419,67 +341,8 @@ ${.CURDIR:T}.pdb.${_curcomp}: ${DOC}.pdb .endfor .endif -# RTF -------------------------------------------------------------------- - -.if !target(${DOC}.rtf) -.if !defined(NO_RTF) -${DOC}.rtf: ${DOC}.parsed.xml ${LOCAL_IMAGES_EPS} ${PRINT_INDEX} \ - ${LOCAL_IMAGES_TXT} ${LOCAL_IMAGES_PNG} - ${JADE} -V rtf-backend ${PRINTOPTS} -ioutput.rtf.images \ - ${JADEOPTS} -t rtf -o ${.TARGET}-nopng ${XMLDECL} \ - ${DOC}.parsed.xml - ${FIXRTF} ${FIXRTFOPTS} < ${.TARGET}-nopng > ${.TARGET} -.else -${DOC}.rtf: - ${TOUCH} ${.TARGET} -.endif -.endif - -# PS/PDF ----------------------------------------------------------------- - -.if ${RENDERENGINE} == "jade" -.if !defined(NO_TEX) -${DOC}.tex: ${SRCS} ${LOCAL_IMAGES_EPS} ${PRINT_INDEX} \ - ${LOCAL_IMAGES_TXT} ${LOCAL_IMAGES_EN} \ - ${DOC}.parsed.xml - ${JADE} -V tex-backend ${PRINTOPTS} \ - ${JADEOPTS} -t tex -o ${.TARGET} ${XMLDECL} ${DOC}.parsed.print.xml - ${SED} -i '' -e 's|{1}\\def\\ScaleY%|{0.5}\\def\\ScaleY%|g' \ - -e 's|{1}\\def\\EntitySystemId%|{0.5}\\def\\EntitySystemId%|g' \ - ${.TARGET} - -.if !target(${DOC}.dvi) -${DOC}.dvi: ${DOC}.tex ${LOCAL_IMAGES_EPS} -.for _curimage in ${LOCAL_IMAGES_EPS:M*share*} - ${CP} -p ${_curimage} ${.CURDIR:H:H}/${_curimage:H:S|${IMAGES_EN_DIR}/||:S|${.CURDIR}||} -.endfor - ${JADETEX_PREPROCESS} < ${DOC}.tex > ${DOC}.tex-tmp - @${ECHO} "==> TeX pass 1/3" - -${JADETEX_CMD} '${TEX_CMDSEQ} \nonstopmode\input{${DOC}.tex-tmp}' - @${ECHO} "==> TeX pass 2/3" - -${JADETEX_CMD} '${TEX_CMDSEQ} \nonstopmode\input{${DOC}.tex-tmp}' - @${ECHO} "==> TeX pass 3/3" - -${JADETEX_CMD} '${TEX_CMDSEQ} \nonstopmode\input{${DOC}.tex-tmp}' -.endif - -.if !target(${DOC}.pdf) -${DOC}.pdf: ${DOC}.ps ${IMAGES_PDF} - ${PS2PDF} ${DOC}.ps ${.TARGET} -.endif +# PS/PDF/RTF ----------------------------------------------------------------- -${DOC}.ps: ${DOC}.dvi - ${DVIPS} ${DVIPSOPTS} -o ${.TARGET} ${.ALLSRC} -.else -# NO_TEX -${DOC}.tex ${DOC}.dvi ${DOC}.ps: - ${TOUCH} ${.TARGET} -.if !target(${DOC}.pdf) -${DOC}.pdf: - ${TOUCH} ${.TARGET} -.endif -.endif - -.elif ${RENDERENGINE} == "fop" ${DOC}.fo: ${DOC}.xml ${LOCAL_IMAGES_LIB} ${LOCAL_IMAGES_PNG} ${DOC}.parsed.xml ${XSLTPROC} ${XSLTPROCOPTS} ${XSLFO} ${DOC}.parsed.print.xml > ${.TARGET} @@ -492,8 +355,6 @@ ${DOC}.ps: ${DOC}.fo ${LOCAL_IMAGES_LIB} ${DOC}.rtf: ${DOC}.fo ${LOCAL_IMAGES_LIB} ${LOCAL_IMAGES_PNG} ${FOP} ${FOPOPTS} ${DOC}.fo ${.TARGET} -.endif - ${DOC}.tar: ${SRCS} ${LOCAL_IMAGES} ${LOCAL_CSS_SHEET} ${TAR} cf ${.TARGET} -C ${.CURDIR} ${SRCS} \ -C ${.OBJDIR} ${IMAGES} ${CSS_SHEET:T} From owner-svn-doc-projects@FreeBSD.ORG Wed May 29 19:29:45 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4E6413B0; Wed, 29 May 2013 19:29:45 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 3F7A52AC; Wed, 29 May 2013 19:29:45 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4TJTjYq016689; Wed, 29 May 2013 19:29:45 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4TJTitq016683; Wed, 29 May 2013 19:29:44 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305291929.r4TJTitq016683@svn.freebsd.org> From: Gabor Kovesdan Date: Wed, 29 May 2013 19:29:44 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41776 - in projects/db5/share: mk xsl X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 19:29:45 -0000 Author: gabor Date: Wed May 29 19:29:43 2013 New Revision: 41776 URL: http://svnweb.freebsd.org/changeset/doc/41776 Log: - Use namespace-aware stylesheets - Drop more legacy stuff Modified: projects/db5/share/mk/doc.docbook.mk projects/db5/share/xsl/freebsd-epub.xsl projects/db5/share/xsl/freebsd-fo.xsl projects/db5/share/xsl/freebsd-xhtml-chunk.xsl projects/db5/share/xsl/freebsd-xhtml.xsl projects/db5/share/xsl/titlepage.templates.xml Modified: projects/db5/share/mk/doc.docbook.mk ============================================================================== --- projects/db5/share/mk/doc.docbook.mk Wed May 29 19:26:44 2013 (r41775) +++ projects/db5/share/mk/doc.docbook.mk Wed May 29 19:29:43 2013 (r41776) @@ -56,9 +56,7 @@ MASTERDOC?= ${.CURDIR}/${DOC}.xml -XMLDECL?= /usr/local/share/sgml/docbook/dsssl/modular/dtds/decls/xml.dcl - -XSLPROF?= /usr/local/share/xsl/docbook/profiling/profile.xsl +XSLPROF?= /usr/local/share/xsl/docbook-ns/profiling/profile.xsl XSLXHTML?= ${DOC_PREFIX}/${LANGCODE}/share/xsl/freebsd-xhtml.xsl XSLXHTMLCHUNK?= ${DOC_PREFIX}/${LANGCODE}/share/xsl/freebsd-xhtml-chunk.xsl XSLEPUB?= ${DOC_PREFIX}/${LANGCODE}/share/xsl/freebsd-epub.xsl Modified: projects/db5/share/xsl/freebsd-epub.xsl ============================================================================== --- projects/db5/share/xsl/freebsd-epub.xsl Wed May 29 19:26:44 2013 (r41775) +++ projects/db5/share/xsl/freebsd-epub.xsl Wed May 29 19:29:43 2013 (r41776) @@ -8,7 +8,7 @@ exclude-result-prefixes="#default"> - + Modified: projects/db5/share/xsl/freebsd-fo.xsl ============================================================================== --- projects/db5/share/xsl/freebsd-fo.xsl Wed May 29 19:26:44 2013 (r41775) +++ projects/db5/share/xsl/freebsd-fo.xsl Wed May 29 19:29:43 2013 (r41776) @@ -9,7 +9,7 @@ exclude-result-prefixes="#default"> - + Modified: projects/db5/share/xsl/freebsd-xhtml-chunk.xsl ============================================================================== --- projects/db5/share/xsl/freebsd-xhtml-chunk.xsl Wed May 29 19:26:44 2013 (r41775) +++ projects/db5/share/xsl/freebsd-xhtml-chunk.xsl Wed May 29 19:29:43 2013 (r41776) @@ -8,7 +8,7 @@ exclude-result-prefixes="#default"> - + Modified: projects/db5/share/xsl/freebsd-xhtml.xsl ============================================================================== --- projects/db5/share/xsl/freebsd-xhtml.xsl Wed May 29 19:26:44 2013 (r41775) +++ projects/db5/share/xsl/freebsd-xhtml.xsl Wed May 29 19:29:43 2013 (r41776) @@ -8,7 +8,7 @@ exclude-result-prefixes="#default"> - + Modified: projects/db5/share/xsl/titlepage.templates.xml ============================================================================== --- projects/db5/share/xsl/titlepage.templates.xml Wed May 29 19:26:44 2013 (r41775) +++ projects/db5/share/xsl/titlepage.templates.xml Wed May 29 19:29:43 2013 (r41776) @@ -10,7 +10,7 @@ Use this template to generate freebsd-xhtml-titlepage.xsl by running: - xsltproc /usr/local/share/xsl/docbook/template/titlepage.xsl titlepage.templates.xml > freebsd-xhtml-titlepage.xsl + xsltproc /usr/local/share/xsl/docbook-ns/template/titlepage.xsl titlepage.templates.xml > freebsd-xhtml-titlepage.xsl --> From owner-svn-doc-projects@FreeBSD.ORG Thu May 30 20:09:46 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0E887BC9; Thu, 30 May 2013 20:09:46 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id F41122B4; Thu, 30 May 2013 20:09:45 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4UK9j8b036221; Thu, 30 May 2013 20:09:45 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4UK9jfP036212; Thu, 30 May 2013 20:09:45 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305302009.r4UK9jfP036212@svn.freebsd.org> From: Gabor Kovesdan Date: Thu, 30 May 2013 20:09:45 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41780 - in projects/db5/share: mk xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 20:09:46 -0000 Author: gabor Date: Thu May 30 20:09:44 2013 New Revision: 41780 URL: http://svnweb.freebsd.org/changeset/doc/41780 Log: - Port some of the customizations to DocBook 5.0 - Add namespace declaration to DocBook elements in entities since DocBook 5.0 uses a namespace - Drop Jade-specific compatibility nits Added: projects/db5/share/xml/freebsd50.dtd - copied, changed from r41725, projects/db5/share/xml/freebsd45.dtd Deleted: projects/db5/share/xml/freebsd45.dtd Modified: projects/db5/share/mk/doc.docbook.mk projects/db5/share/xml/freebsd.ent projects/db5/share/xml/man-refs.ent projects/db5/share/xml/trademarks.ent Modified: projects/db5/share/mk/doc.docbook.mk ============================================================================== --- projects/db5/share/mk/doc.docbook.mk Thu May 30 15:43:27 2013 (r41779) +++ projects/db5/share/mk/doc.docbook.mk Thu May 30 20:09:44 2013 (r41780) @@ -254,21 +254,11 @@ ${sch}.xsl: ${sch} # Parsed XML ------------------------------------------------------- ${DOC}.parsed.xml: ${SRCS} - ${GREP} '^' ${DOC}.xml > ${.TARGET}.tmp -.if ${DOC} == "book" - ${ECHO_CMD} '' >> ${.TARGET}.tmp -.else - ${ECHO_CMD} '' >> ${.TARGET}.tmp -.endif - @${ECHO} "==> Basic validation" - ${XMLLINT} --nonet --noent --valid --xinclude --dropdtd ${MASTERDOC} | \ - ${GREP} -v '^' >> ${.TARGET}.tmp + ${XMLLINT} --nonet --noent --valid --xinclude ${MASTERDOC} > ${.TARGET} .if defined(PROFILING) @${ECHO} "==> Profiling" ${XSLTPROC} ${PROFILING} ${XSLPROF} ${.TARGET}.tmp > ${.TARGET} - ${RM} ${.TARGET}.tmp .else - ${MV} ${.TARGET}.tmp ${.TARGET} ${SED} 's|@@URL_RELPREFIX@@|http://www.FreeBSD.org|g' < ${.TARGET} > ${DOC}.parsed.print.xml ${SED} -i '' 's|@@URL_RELPREFIX@@|../../../..|g' ${.TARGET} .endif @@ -385,15 +375,8 @@ ${DOC}.${_curformat}: # lint validate: ${SRCS} ${schxslts} - @${GREP} '^' ${DOC}.xml > ${DOC}.parsed.xml -.if ${DOC} == "book" - @${ECHO_CMD} '' >> ${DOC}.parsed.xml -.else - @${ECHO_CMD} '' >> ${DOC}.parsed.xml -.endif @${ECHO} "==> Basic validation" - @${XMLLINT} --nonet --noent --valid --xinclude --dropdtd ${MASTERDOC} | \ - ${GREP} -v '^' >>${DOC}.parsed.xml + @${XMLLINT} --nonet --noent --valid --xinclude ${MASTERDOC} > ${DOC}.parsed.xml .if defined(schxslts) @${ECHO} "==> Validating with Schematron constraints" .for sch in ${schxslts} Modified: projects/db5/share/xml/freebsd.ent ============================================================================== --- projects/db5/share/xml/freebsd.ent Thu May 30 15:43:27 2013 (r41779) +++ projects/db5/share/xml/freebsd.ent Thu May 30 20:09:44 2013 (r41780) @@ -11,8 +11,8 @@ used in both environments. -#"> -%"> +#'> +%'> -UNIX"> -NIS"> +UNIX'> +NIS'> -TeX'> -LaTeX'> +TeX'> +LaTeX'> @@ -102,7 +102,7 @@ used in both environments. -[ OK ]"> -[ Cancel ]"> -[ Yes ]"> -[ No ]"> +[ OK ]'> +[ Cancel ]'> +[ Yes ]'> +[ No ]'> Copied and modified: projects/db5/share/xml/freebsd50.dtd (from r41725, projects/db5/share/xml/freebsd45.dtd) ============================================================================== --- projects/db5/share/xml/freebsd45.dtd Thu May 23 15:40:43 2013 (r41725, copy source) +++ projects/db5/share/xml/freebsd50.dtd Thu May 30 20:09:44 2013 (r41780) @@ -1,42 +1,28 @@ - - - + - - - -]]> - - - - - - - - - - - - - - - - - - - + @@ -55,11 +41,14 @@ xmlns:xi CDATA #FIXED "http://www.w3.org/2001/XInclude" > - + %orig-docbook; - +%iso8879.ent; + %authors; @@ -71,51 +60,3 @@ %orig-entities; -]]> - - - - - - - - - - - - - - - - - - - - - - - - -#"> -%"> Modified: projects/db5/share/xml/man-refs.ent ============================================================================== --- projects/db5/share/xml/man-refs.ent Thu May 30 15:43:27 2013 (r41779) +++ projects/db5/share/xml/man-refs.ent Thu May 30 20:09:44 2013 (r41780) @@ -24,5417 +24,5417 @@ $FreeBSD$ --> -[1"> -CC1"> -Mail1"> +[1"> +CC1"> +Mail1"> -X1"> -XFree861"> -Xorg1"> -a2p1"> -addftinfo1"> -addr2line1"> -afmtodit1"> -alias1"> -alloc1"> -apply1"> -apropos1"> -ar1"> -as1"> -asa1"> -at1"> -atq1"> -atrm1"> -auditreduce1"> -awk1"> -b64decode1"> -b64encode1"> -basename1"> -bash1"> -batch1"> -bc1"> -bdes1"> -bg1"> -biff1"> -bindkey1"> -brandelf1"> -break1"> -breaksw1"> -bsdiff1"> -bsdtar1"> -bsnmpd1"> -bspatch1"> -btsockstat1"> -builtin1"> -builtins1"> -byacc1"> -bzegrep1"> -bzfgrep1"> -bzgrep1"> -bzip21"> -c++1"> -c2ph1"> -c891"> -c991"> -cal1"> -calendar1"> -cap_mkdb1"> -case1"> -cat1"> -catman1"> -cc1"> -cccp1"> -cd1"> -cdcontrol1"> -cdrecord1"> -chdir1"> -checknr1"> -chflags1"> -chfn1"> -chgrp1"> -chio1"> -chkey1"> -chmod1"> -chpass1"> -chsh1"> -ci1"> -ckdist1"> -cksum1"> -clear1"> -clang1"> -clang++1"> -clang-cpp1"> -cmp1"> -co1"> -col1"> -colcrt1"> -colldef1"> -colrm1"> -column1"> -comm1"> -command1"> -compile_et1"> -complete1"> -compress1"> -continue1"> -cp1"> -cpio1"> -cpp1"> -cpuset1"> -crontab1"> -crunchgen1"> -crunchide1"> -crypt1"> -csh1"> -csplit1"> -csup1"> -ctags1"> -ctm1"> -ctm_dequeue1"> -ctm_rmail1"> -ctm_smail1"> -cu1"> -cursor1"> -cut1"> -cvs1"> -cvsup1"> -date1"> -dc1"> -dd1"> -default1"> -df1"> -dga1"> -dialog1"> -diff1"> -diff31"> -dig1"> -dirname1"> -dirs1"> -dnskeygen1"> -dnsquery1"> -do1"> -domainname1"> -done1"> -doscmd1"> -dprofpp1"> -dtmfdecode1"> -dtrace1"> -dtruss1"> -du1"> -echo1"> -echotc1"> -ed1"> -edit1"> -ee1"> -egrep1"> -elfdump1"> -elif1"> -else1"> -emacs1"> -end1"> -endif1"> -endsw1"> -enigma1"> -env1"> -eqn1"> -esac1"> -eval1"> -ex1"> -exec1"> -exit1"> -expand1"> -export1"> -expr1"> -f771"> -false1"> -fc1"> -fdformat1"> -fdread1"> -fdwrite1"> -fetch1"> -fg1"> -fgrep1"> -fi1"> -fifolog1"> -file1"> -file2c1"> -filetest1"> -find1"> -finger1"> -flex1"> -flex++1"> -fmt1"> -fold1"> -fontedit1"> -for1"> -foreach1"> -from1"> -fstat1"> -fsync1"> -ftp1"> -g++1"> -g711conv1"> -gasp1"> -gate-ftp1"> -gawk1"> -gcc1"> -gcore1"> -gdb1"> -gdbserver1"> -gencat1"> -getNAME1"> -getconf1"> -getent1"> -getfacl1"> -getopt1"> -getopts1"> -glob1"> -goto1"> -gperf1"> -gprof1"> -grep1"> -grn1"> -grodvi1"> -groff1"> -grog1"> -grohtml1"> -grolbp1"> -grolj41"> -grops1"> -grotty1"> -groups1"> -growisofs1"> -gs1"> -gtar1"> -gunzip1"> -gzcat1"> -gzexe1"> -gzip1"> -h2ph1"> -h2xs1"> -hash1"> -hashstat1"> -hd1"> -head1"> -hesinfo1"> -hexdump1"> -history1"> -host1"> -hostname1"> -hpftodit1"> -hup1"> -id1"> -ident1"> -idprio1"> -if1"> -imake1"> -imwheel1"> -indent1"> -indxbib1"> -info1"> -install1"> -install-info1"> -intro1"> -introduction1"> -ipcrm1"> -ipcs1"> -ipftest1"> -ipnat1"> -ipresend1"> -ipsend1"> -iptest1"> -jobid1"> -jobs1"> -join1"> -jot1"> -kbdcontrol1"> -kbdmap1"> -kcon1"> -kdump1"> -kenv1"> -kerberos1"> -key1"> -keyinfo1"> -keyinit1"> -keylogin1"> -keylogout1"> -kgdb1"> -kill1"> -killall1"> -ksu1"> -ktrace1"> -lam1"> -last1"> -lastcomm1"> -ld1"> -ld-elf.so.11"> -ldd1"> -leave1"> -less1"> -lesskey1"> -lex1"> -lex++1"> -limit1"> -limits1"> -link1"> -lint1"> -lkbib1"> -ln1"> -lndir1"> -loadfont1"> -locale1"> -locate1"> -lock1"> -lockf1"> -log1"> -logger1"> -login1"> -logins1"> -logname1"> -logout1"> -look1"> -lookbib1"> -lorder1"> -lp1"> -lpq1"> -lpr1"> -lprm1"> -lptest1"> -ls1"> -ls-F1"> -lsvfs1"> -lynx1"> -lzcat1"> -lzma1"> -lzmadec1"> -lzmainfo1"> -m41"> -mail1"> -mailq1"> -make1"> -makeinfo1"> -makewhatis1"> -man1"> -manpath1"> -mcon1"> -md51"> -merge1"> -mesg1"> -minigzip1"> -ministat1"> -mk_cmds1"> -mkdep1"> -mkdir1"> -mkfifo1"> -mkfontdir1"> -mklocale1"> -mkstr1"> -mktemp1"> -mmroff1"> -more1"> -mptable1"> -msgs1"> -mt1"> -mv1"> -nc1"> -ncal1"> -ncplist1"> -ncplogin1"> -ncplogout1"> -neqn1"> -netstat1"> -newaliases1"> -newgrp1"> -nex1"> -nfsstat1"> -nice1"> -nl1"> -nm1"> -nohup1"> -notify1"> -nroff1"> -nsgmls1"> -nsupdate1"> -nvi1"> -nview1"> -objcopy1"> -objdump1"> -objformat1"> -od1"> -omshell1"> -onintr1"> -openssl1"> -opieinfo1"> -opiekey1"> -opiepasswd1"> -otp-md41"> -otp-md51"> -pagesize1"> -passwd1"> -paste1"> -patch1"> -pathchk1"> -pawd1"> -pax1"> -perl1"> -perl5004delta1"> -perl5005delta1"> -perlapi1"> -perlapio1"> -perlbc1"> -perlbook1"> -perlboot1"> -perlbot1"> -perlbug1"> -perlcall1"> -perlcc1"> -perlcompile1"> -perldata1"> -perldbmfilter1"> -perldebguts1"> -perldebug1"> -perldelta1"> -perldiag1"> -perldoc1"> -perldsc1"> -perlembed1"> -perlfaq1"> -perlfaq11"> -perlfaq21"> -perlfaq31"> -perlfaq41"> -perlfaq51"> -perlfaq61"> -perlfaq71"> -perlfaq81"> -perlfaq91"> -perlfork1"> -perlform1"> -perlfunc1"> -perlguts1"> -perlhack1"> -perlhist1"> -perlintern1"> -perlipc1"> -perllocale1"> -perllol1"> -perlmod1"> -perlmodinstall1"> -perlmodlib1"> -perlnumber1"> -perlobj1"> -perlop1"> -perlopentut1"> -perlpod1"> -perlport1"> -perlre1"> -perlref1"> -perlreftut1"> -perlrun1"> -perlsec1"> -perlstyle1"> -perlsub1"> -perlsyn1"> -perlthrtut1"> -perltie1"> -perltoc1"> -perltodo1"> -perltoot1"> -perltootc1"> -perltrap1"> -perlvar1"> -perlxs1"> -perlxstut1"> -pfbtops1"> -pftp1"> -pgrep1"> -pic1"> -pim6stat1"> -pkg_add1"> -pkg_check1"> -pkg_create1"> -pkg_delete1"> -pkg_info1"> -pkg_sign1"> -pkg_update1"> -pkg_version1"> -pkgdb1"> -pkill1"> -pl2pm1"> -pod2html1"> -pod2man1"> -popd1"> -portaudit1"> -portlint1"> -portmanager1"> -portupgrade1"> -pr1"> -praudit1"> -printenv1"> -printf1"> -procstat1"> -ps1"> -psbb1"> -psroff1"> -pushd1"> -pwait1"> -pwd1"> -quota1"> -ranlib1"> -rcp1"> -rcs1"> -rcsclean1"> -rcsdiff1"> -rcsfreeze1"> -rcsintro1"> -rcsmerge1"> -rdist1"> -read1"> -readelf1"> -readonly1"> -realpath1"> -red1"> -ree1"> -refer1"> -rehash1"> -repeat1"> -reset1"> -rev1"> -revoke1"> -rfcomm_sppd1"> -rlog1"> -rlogin1"> -rm1"> -rmd1601"> -rmdir1"> -rpcgen1"> -rs1"> -rsh1"> -rsync1"> -rtld1"> -rtprio1"> -rup1"> -ruptime1"> -rusers1"> -rwall1"> -rwho1"> -rxvt1"> -s2p1"> -sane-find-scanner1"> -sasc1"> -scanimage1"> -sccs1"> -sched1"> -scon1"> -scp1"> -script1"> -sdiff1"> -sed1"> -send-pr1"> -sendbug1"> -set1"> -setbuf1"> -setenv1"> -setfacl1"> -setfib1"> -settc1"> -setty1"> -setvar1"> -setxkbmap1"> -sftp1"> -sgmlnorm1"> -sgsc1"> -sh1"> -sha11"> -sha2561"> -shar1"> -shift1"> -shutdown1"> -size1"> -skey1"> -sleep1"> -slogin1"> -smbutil1"> -sockstat1"> -soelim1"> -sort1"> -source1"> -split1"> -ssh1"> -ssh-add1"> -ssh-agent1"> -ssh-keygen1"> -ssh-keyscan1"> -startslip1"> -startx1"> -stat1"> -stop1"> -strings1"> -strip1"> -stty1"> -su1"> -sum1"> -suspend1"> -svn1"> -switch1"> -symorder1"> -systat1"> -tabs1"> -tail1"> -talk1"> -tar1"> -tbl1"> -tcopy1"> -tcpdump1"> -tcpslice1"> -tcsh1"> -tee1"> -telltc1"> -telnet1"> -test1"> -texindex1"> -tfmtodit1"> -tftp1"> -then1"> -time1"> -tip1"> -top1"> -touch1"> -tput1"> -tr1"> -trace1"> -trap1"> -troff1"> -true1"> -truncate1"> -truss1"> -tset1"> -tsort1"> -tty1"> -type1"> -uhsoctl1"> -ul1"> -ulimit1"> -umask1"> -unalias1"> -uname1"> -uncomplete1"> -uncompress1"> -unexpand1"> -unhash1"> -unifdef1"> -uniq1"> -units1"> -unlimit1"> -unlink1"> -unlzma1"> -unset1"> -unsetenv1"> -until1"> -unvis1"> -unxz1"> -unzip1"> -uptime1"> -usbhidaction1"> -usbhidctl1"> -users1"> -uuconv1"> -uucp1"> -uudecode1"> -uuencode1"> -uuidgen1"> -uulog1"> -uuname1"> -uupick1"> -uustat1"> -uuto1"> -uux1"> -vacation1"> -vgrind1"> -vi1"> -vidcontrol1"> -vidfont1"> -view1"> -vim1"> -vis1"> -vt220keys1"> -vttest1"> -w1"> -w3m1"> -wait1"> -wall1"> -wc1"> -what1"> -whatis1"> -where1"> -whereis1"> -which1"> -while1"> -who1"> -whoami1"> -whois1"> -window1"> -write1"> -wtmpcvt1"> -xargs1"> -xdm1"> -xdpyinfo1"> -xf86cfg1"> -xf86config1"> -xfontsel1"> -xlsfonts1"> -xmodmap1"> +X1"> +XFree861"> +Xorg1"> +a2p1"> +addftinfo1"> +addr2line1"> +afmtodit1"> +alias1"> +alloc1"> +apply1"> +apropos1"> +ar1"> +as1"> +asa1"> +at1"> +atq1"> +atrm1"> +auditreduce1"> +awk1"> +b64decode1"> +b64encode1"> +basename1"> +bash1"> +batch1"> +bc1"> +bdes1"> +bg1"> +biff1"> +bindkey1"> +brandelf1"> +break1"> +breaksw1"> +bsdiff1"> +bsdtar1"> +bsnmpd1"> +bspatch1"> +btsockstat1"> +builtin1"> +builtins1"> +byacc1"> +bzegrep1"> +bzfgrep1"> +bzgrep1"> +bzip21"> +c++1"> +c2ph1"> +c891"> +c991"> +cal1"> +calendar1"> +cap_mkdb1"> +case1"> +cat1"> +catman1"> +cc1"> +cccp1"> +cd1"> +cdcontrol1"> +cdrecord1"> +chdir1"> +checknr1"> +chflags1"> +chfn1"> *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 07:46:22 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 43335464; Fri, 31 May 2013 07:46:22 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 33B01B04; Fri, 31 May 2013 07:46:22 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4V7kLpK080872; Fri, 31 May 2013 07:46:21 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4V7kLfL080870; Fri, 31 May 2013 07:46:21 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305310746.r4V7kLfL080870@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 07:46:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41783 - projects/db5/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 07:46:22 -0000 Author: gabor Date: Fri May 31 07:46:21 2013 New Revision: 41783 URL: http://svnweb.freebsd.org/changeset/doc/41783 Log: - Add the full DocBook DTD here, since customization with parameters entities is not possible any more - Apply FreeBSD-specific customizations Added: projects/db5/share/xml/docbook50.dtd (contents, props changed) Modified: projects/db5/share/xml/freebsd50.dtd Added: projects/db5/share/xml/docbook50.dtd ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/db5/share/xml/docbook50.dtd Fri May 31 07:46:21 2013 (r41783) @@ -0,0 +1,4222 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 07:47:03 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 958404BD; Fri, 31 May 2013 07:47:03 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 853D1B12; Fri, 31 May 2013 07:47:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4V7l3M7081038; Fri, 31 May 2013 07:47:03 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4V7l3JC081032; Fri, 31 May 2013 07:47:03 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305310747.r4V7l3JC081032@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 07:47:03 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41784 - in projects/db5: en_US.ISO8859-1/share/xml share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 07:47:03 -0000 Author: gabor Date: Fri May 31 07:47:02 2013 New Revision: 41784 URL: http://svnweb.freebsd.org/changeset/doc/41784 Log: - Convert some ulink elements to link - Add namespace declarations Modified: projects/db5/en_US.ISO8859-1/share/xml/mailing-lists.ent projects/db5/en_US.ISO8859-1/share/xml/teams.ent projects/db5/share/xml/authors.ent Modified: projects/db5/en_US.ISO8859-1/share/xml/mailing-lists.ent ============================================================================== --- projects/db5/en_US.ISO8859-1/share/xml/mailing-lists.ent Fri May 31 07:46:21 2013 (r41783) +++ projects/db5/en_US.ISO8859-1/share/xml/mailing-lists.ent Fri May 31 07:47:02 2013 (r41784) @@ -5,72 +5,72 @@ --> -FreeBSD list server"> -&a.mailman.listinfo;"> +FreeBSD list server"> +&a.mailman.listinfo;"> -FreeBSD ACPI mailing list"> -freebsd-acpi"> +FreeBSD ACPI mailing list"> +freebsd-acpi"> -FreeBSD advocacy mailing list"> -freebsd-advocacy"> +FreeBSD advocacy mailing list"> +freebsd-advocacy"> -FreeBSD AFS porting mailing list"> -freebsd-afs"> +FreeBSD AFS porting mailing list"> +freebsd-afs"> -FreeBSD Adaptec AIC7xxx discussions mailing list"> -freebsd-aic7xxx"> +FreeBSD Adaptec AIC7xxx discussions mailing list"> +freebsd-aic7xxx"> -Porting FreeBSD to AMD64 systems"> -freebsd-amd64"> +Porting FreeBSD to AMD64 systems"> +freebsd-amd64"> -FreeBSD announcements mailing list"> -freebsd-announce"> +FreeBSD announcements mailing list"> +freebsd-announce"> -FreeBSD Apache mailing list"> -freebsd-apache"> +FreeBSD Apache mailing list"> +freebsd-apache"> -FreeBSD architecture and design mailing list"> -freebsd-arch"> +FreeBSD architecture and design mailing list"> +freebsd-arch"> -FreeBSD ARM porting mailing list"> -freebsd-arm"> +FreeBSD ARM porting mailing list"> +freebsd-arm"> -FreeBSD ATM networking mailing list"> -freebsd-atm"> +FreeBSD ATM networking mailing list"> +freebsd-atm"> -FreeBSD Bluetooth mailing list"> -freebsd-bluetooth"> +FreeBSD Bluetooth mailing list"> +freebsd-bluetooth"> -FreeBSD bugbusters mailing list"> -freebsd-bugbusters"> +FreeBSD bugbusters mailing list"> +freebsd-bugbusters"> -FreeBSD problem reports mailing list"> -freebsd-bugs"> +FreeBSD problem reports mailing list"> +freebsd-bugs"> -FreeBSD chat mailing list"> -freebsd-chat"> +FreeBSD chat mailing list"> +freebsd-chat"> -FreeBSD-specific Chromium issues"> -freebsd-chromium"> +FreeBSD-specific Chromium issues"> +freebsd-chromium"> -FreeBSD clustering mailing list"> -freebsd-cluster"> +FreeBSD clustering mailing list"> +freebsd-cluster"> @@ -79,83 +79,83 @@ -&os.current; mailing list"> -freebsd-current"> +&os.current; mailing list"> +freebsd-current"> -CTM announcements"> -ctm-announce"> +CTM announcements"> +ctm-announce"> -CTM 4-STABLE src branch distribution mailing list"> -ctm-src-4"> +CTM 4-STABLE src branch distribution mailing list"> +ctm-src-4"> -CTM 5-STABLE src branch distribution mailing list"> -ctm-src-5"> +CTM 5-STABLE src branch distribution mailing list"> +ctm-src-5"> -CTM 6-STABLE src branch distribution mailing list"> -ctm-src-6"> +CTM 6-STABLE src branch distribution mailing list"> +ctm-src-6"> -CTM 7-STABLE src branch distribution mailing list"> -ctm-src-7"> +CTM 7-STABLE src branch distribution mailing list"> +ctm-src-7"> -CTM 8-STABLE src branch distribution mailing list"> -ctm-src-8"> +CTM 8-STABLE src branch distribution mailing list"> +ctm-src-8"> -CTM 9-STABLE src branch distribution mailing list"> -ctm-src-9"> +CTM 9-STABLE src branch distribution mailing list"> +ctm-src-9"> -CTM -CURRENT src branch distribution mailing list"> -ctm-src-cur"> +CTM -CURRENT src branch distribution mailing list"> +ctm-src-cur"> -CTM user discussion mailing list"> -ctm-users"> +CTM user discussion mailing list"> +ctm-users"> -FreeBSD CVS commit message mailing list"> -cvs-all"> +FreeBSD CVS commit message mailing list"> +cvs-all"> -FreeBSD CVS doc commit list"> -cvs-doc"> +FreeBSD CVS doc commit list"> +cvs-doc"> -FreeBSD CVS ports commit list"> -cvs-ports"> +FreeBSD CVS ports commit list"> +cvs-ports"> -FreeBSD CVS projects commit list"> -cvs-projects"> +FreeBSD CVS projects commit list"> +cvs-projects"> -FreeBSD CVS src commit list"> -cvs-src"> +FreeBSD CVS src commit list"> +cvs-src"> -FreeBSD CVSweb maintenance mailing list"> -freebsd-cvsweb"> +FreeBSD CVSweb maintenance mailing list"> +freebsd-cvsweb"> -FreeBSD based Databases mailing list"> -freebsd-database"> +FreeBSD based Databases mailing list"> +freebsd-database"> -Using and improving &os; on the desktop"> -freebsd-desktop"> +Using and improving &os; on the desktop"> +freebsd-desktop"> -FreeBSD documentation project mailing list"> -freebsd-doc"> +FreeBSD documentation project mailing list"> +freebsd-doc"> @@ -164,190 +164,190 @@ -Writing device drivers for FreeBSD"> -freebsd-drivers"> +Writing device drivers for FreeBSD"> +freebsd-drivers"> -Using and working on DTrace in &os;."> -freebsd-dtrace"> +Using and working on DTrace in &os;."> +freebsd-dtrace"> -FreeBSD users of Eclipse IDE, tools, rich client applications and ports"> -freebsd-eclipse"> +FreeBSD users of Eclipse IDE, tools, rich client applications and ports"> +freebsd-eclipse"> -FreeBSD-embedded mailing list"> -freebsd-embedded"> +FreeBSD-embedded mailing list"> +freebsd-embedded"> -FreeBSD-emulation mailing list"> -freebsd-emulation"> +FreeBSD-emulation mailing list"> +freebsd-emulation"> -FreeBSD-eol mailing list"> -freebsd-eol"> +FreeBSD-eol mailing list"> +freebsd-eol"> -FreeBSD FireWire (IEEE 1394) discussion mailing list"> -freebsd-firewire"> +FreeBSD FireWire (IEEE 1394) discussion mailing list"> +freebsd-firewire"> -FreeBSD file system project mailing list"> -freebsd-fs"> +FreeBSD file system project mailing list"> +freebsd-fs"> -FreeBSD gecko mailing list"> -freebsd-gecko"> +FreeBSD gecko mailing list"> +freebsd-gecko"> -FreeBSD GEOM mailing list"> -freebsd-geom"> +FreeBSD GEOM mailing list"> +freebsd-geom"> -FreeBSD GNOME and GNOME applications mailing list"> -freebsd-gnome"> +FreeBSD GNOME and GNOME applications mailing list"> +freebsd-gnome"> -FreeBSD technical discussions mailing list"> -freebsd-hackers"> +FreeBSD technical discussions mailing list"> +freebsd-hackers"> -FreeBSD hardware and equipment mailing list"> -freebsd-hardware"> +FreeBSD hardware and equipment mailing list"> +freebsd-hardware"> -FreeBSD mirror sites mailing lists"> -freebsd-hubs"> +FreeBSD mirror sites mailing lists"> +freebsd-hubs"> -FreeBSD internationalization mailing list"> -freebsd-i18n"> +FreeBSD internationalization mailing list"> +freebsd-i18n"> -FreeBSD i386-specific issues mailing list"> -freebsd-i386"> +FreeBSD i386-specific issues mailing list"> +freebsd-i386"> -FreeBSD IA32 porting mailing list"> -freebsd-ia32"> +FreeBSD IA32 porting mailing list"> +freebsd-ia32"> -FreeBSD IA64 porting mailing list"> -freebsd-ia64"> +FreeBSD IA64 porting mailing list"> +freebsd-ia64"> -Infiniband on FreeBSD"> -freebsd-infiniband"> +Infiniband on FreeBSD"> +freebsd-infiniband"> -FreeBSD IPFW code mailing list"> -freebsd-ipfw"> +FreeBSD IPFW code mailing list"> +freebsd-ipfw"> -FreeBSD ISDN mailing list"> -freebsd-isdn"> +FreeBSD ISDN mailing list"> +freebsd-isdn"> -FreeBSD Internet service provider's mailing list"> -freebsd-isp"> +FreeBSD Internet service provider's mailing list"> +freebsd-isp"> -FreeBSD jails mailing list"> -freebsd-jail"> +FreeBSD jails mailing list"> +freebsd-jail"> -FreeBSD Java Language mailing list"> -freebsd-java"> +FreeBSD Java Language mailing list"> +freebsd-java"> -FreeBSD related employment mailing list"> -freebsd-jobs"> +FreeBSD related employment mailing list"> +freebsd-jobs"> -FreeBSD KDE/Qt and KDE applications mailing list"> -freebsd-kde"> +FreeBSD KDE/Qt and KDE applications mailing list"> +freebsd-kde"> -FreeBSD LFS porting mailing list"> -freebsd-lfs"> +FreeBSD LFS porting mailing list"> +freebsd-lfs"> -FreeBSD MIPS porting mailing list"> -freebsd-mips"> +FreeBSD MIPS porting mailing list"> +freebsd-mips"> -FreeBSD mirror site administrators"> -mirror-announce"> +FreeBSD mirror site administrators"> +mirror-announce"> -FreeBSD laptop computer mailing list"> -freebsd-mobile"> +FreeBSD laptop computer mailing list"> +freebsd-mobile"> -Mono and C# applications on FreeBSD"> -freebsd-mono"> +Mono and C# applications on FreeBSD"> +freebsd-mono"> -FreeBSD port of the Mozilla browser mailing list"> -freebsd-mozilla"> +FreeBSD port of the Mozilla browser mailing list"> +freebsd-mozilla"> -FreeBSD multimedia mailing list"> -freebsd-multimedia"> +FreeBSD multimedia mailing list"> +freebsd-multimedia"> -FreeBSD networking mailing list"> -freebsd-net"> +FreeBSD networking mailing list"> +freebsd-net"> -FreeBSD new users mailing list"> -freebsd-newbies"> +FreeBSD new users mailing list"> +freebsd-newbies"> -FreeBSD new-bus mailing list"> -freebsd-new-bus"> +FreeBSD new-bus mailing list"> +freebsd-new-bus"> -Discussions of high quality implementation of libm functions"> -freebsd-numerics"> +Discussions of high quality implementation of libm functions"> +freebsd-numerics"> -Office applications on FreeBSD"> -freebsd-office"> +Office applications on FreeBSD"> +freebsd-office"> -Project Infrastructure Announcements"> -freebsd-ops-announce"> +Project Infrastructure Announcements"> +freebsd-ops-announce"> -FreeBSD performance mailing list"> -freebsd-performance"> +FreeBSD performance mailing list"> +freebsd-performance"> -FreeBSD Perl mailing list"> -freebsd-perl"> +FreeBSD Perl mailing list"> +freebsd-perl"> -FreeBSD packet filter mailing list"> -freebsd-pf"> +FreeBSD packet filter mailing list"> +freebsd-pf"> -Binary package management and package tools discussion"> -freebsd-pkg"> +Binary package management and package tools discussion"> +freebsd-pkg"> -FreeBSD non-Intel platforms porting mailing list"> -freebsd-platforms"> +FreeBSD non-Intel platforms porting mailing list"> +freebsd-platforms"> -FreeBSD ports mailing list"> -freebsd-ports"> +FreeBSD ports mailing list"> +freebsd-ports"> -FreeBSD ports announce mailing list"> -freebsd-ports-announce"> +FreeBSD ports announce mailing list"> +freebsd-ports-announce"> -FreeBSD ports bugs mailing list"> -freebsd-ports-bugs"> +FreeBSD ports bugs mailing list"> +freebsd-ports-bugs"> @@ -356,56 +356,56 @@ -FreeBSD PowerPC porting mailing list"> -freebsd-ppc"> +FreeBSD PowerPC porting mailing list"> +freebsd-ppc"> -Technical discussion of FreeBSD on HP ProLiant server platforms"> -freebsd-proliant"> +Technical discussion of FreeBSD on HP ProLiant server platforms"> +freebsd-proliant"> -FreeBSD Python mailing list"> -freebsd-python"> +FreeBSD Python mailing list"> +freebsd-python"> -FreeBSD general questions mailing list"> -freebsd-questions"> +FreeBSD general questions mailing list"> +freebsd-questions"> -FreeBSD boot script system mailing list"> -freebsd-rc"> +FreeBSD boot script system mailing list"> +freebsd-rc"> -FreeBSD realtime extensions mailing list"> -freebsd-realtime"> +FreeBSD realtime extensions mailing list"> +freebsd-realtime"> -FreeBSD Ruby mailing list"> -freebsd-ruby"> +FreeBSD Ruby mailing list"> +freebsd-ruby"> -FreeBSD SCSI subsystem mailing list"> -freebsd-scsi"> +FreeBSD SCSI subsystem mailing list"> +freebsd-scsi"> -FreeBSD security mailing list"> -freebsd-security"> +FreeBSD security mailing list"> +freebsd-security"> -FreeBSD security notifications mailing list"> -freebsd-security-notifications"> +FreeBSD security notifications mailing list"> +freebsd-security-notifications"> -FreeBSD-small mailing list"> -freebsd-small"> +FreeBSD-small mailing list"> +freebsd-small"> -FreeBSD Development Snapshot Announcements"> -freebsd-snapshots"> +FreeBSD Development Snapshot Announcements"> +freebsd-snapshots"> -FreeBSD SPARC porting mailing list"> -freebsd-sparc64"> +FreeBSD SPARC porting mailing list"> +freebsd-sparc64"> @@ -414,185 +414,185 @@ -&os.stable; mailing list"> -freebsd-stable"> +&os.stable; mailing list"> +freebsd-stable"> -FreeBSD C99 and POSIX compliance mailing list"> -freebsd-standards"> +FreeBSD C99 and POSIX compliance mailing list"> +freebsd-standards"> -FreeBSD sun4v porting mailing list"> -freebsd-sun4v"> +FreeBSD sun4v porting mailing list"> +freebsd-sun4v"> -SVN commit messages for the entire doc tree (except for user, projects and translations)"> -svn-doc-all"> +SVN commit messages for the entire doc tree (except for user, projects and translations)"> +svn-doc-all"> -SVN commit messages for the doc tree for head/"> -svn-doc-head"> +SVN commit messages for the doc tree for head/"> +svn-doc-head"> -SVN commit messages for the doc projects tree"> -svn-doc-projects"> +SVN commit messages for the doc projects tree"> +svn-doc-projects"> -SVN commit messages for the doc admin / configuration tree"> -svn-doc-svnadmin"> +SVN commit messages for the doc admin / configuration tree"> +svn-doc-svnadmin"> -SVN commit messages for the entire ports tree"> -svn-ports-all"> +SVN commit messages for the entire ports tree"> +svn-ports-all"> -SVN commit messages for the ports tree for head/"> -svn-ports-head"> +SVN commit messages for the ports tree for head/"> +svn-ports-head"> -SVN commit messages for the ports admin / configuration tree"> -svn-ports-svnadmin"> +SVN commit messages for the ports admin / configuration tree"> +svn-ports-svnadmin"> -SVN commit messages for the entire src tree (except for user and projects)"> -svn-src-all"> +SVN commit messages for the entire src tree (except for user and projects)"> +svn-src-all"> -SVN commit messages for the src tree for head/-current"> -svn-src-head"> +SVN commit messages for the src tree for head/-current"> +svn-src-head"> -SVN commit messages for the src projects tree"> -svn-src-projects"> +SVN commit messages for the src projects tree"> +svn-src-projects"> -SVN commit messages for releases in the src tree"> -svn-src-release"> +SVN commit messages for releases in the src tree"> +svn-src-release"> -SVN commit messages for the release engineering / security commits to the src tree"> -svn-src-releng"> +SVN commit messages for the release engineering / security commits to the src tree"> +svn-src-releng"> -SVN commit messages for all the -stable branches of the src tree"> -svn-src-stable"> +SVN commit messages for all the -stable branches of the src tree"> +svn-src-stable"> -SVN commit messages for only the 6-stable src tree"> -svn-src-stable-6"> +SVN commit messages for only the 6-stable src tree"> +svn-src-stable-6"> -SVN commit messages for only the 7-stable src tree"> -svn-src-stable-7"> +SVN commit messages for only the 7-stable src tree"> +svn-src-stable-7"> -SVN commit messages for only the 8-stable src tree"> -svn-src-stable-8"> +SVN commit messages for only the 8-stable src tree"> +svn-src-stable-8"> -SVN commit messages for only the 9-stable src tree"> -svn-src-stable-9"> +SVN commit messages for only the 9-stable src tree"> +svn-src-stable-9"> -SVN commit messages for the old stable src trees"> -svn-src-stable-other"> +SVN commit messages for the old stable src trees"> +svn-src-stable-other"> -SVN commit messages for the admin / configuration tree"> -svn-src-svnadmin"> +SVN commit messages for the admin / configuration tree"> +svn-src-svnadmin"> -SVN commit messages for the experimental user src tree"> -svn-src-user"> +SVN commit messages for the experimental user src tree"> +svn-src-user"> -SVN commit messages for the vendor work area tree"> -svn-src-vendor"> +SVN commit messages for the vendor work area tree"> +svn-src-vendor"> -Sysinstall development mailing list"> -freebsd-sysinstall"> +Sysinstall development mailing list"> +freebsd-sysinstall"> -FreeBSD-specific Tcl/Tk discussions"> -freebsd-tcltk"> +FreeBSD-specific Tcl/Tk discussions"> +freebsd-tcltk"> -FreeBSD test mailing list"> -freebsd-test"> +FreeBSD test mailing list"> +freebsd-test"> -Testing on &os;"> -freebsd-testing"> +Testing on &os;"> +freebsd-testing"> -Porting TeX and its applications to &os;"> -freebsd-tex"> +Porting TeX and its applications to &os;"> +freebsd-tex"> -FreeBSD threads mailing list"> -freebsd-threads"> +FreeBSD threads mailing list"> +freebsd-threads"> -Porting FreeBSD to the Tilera family of CPUs"> -freebsd-tilera"> +Porting FreeBSD to the Tilera family of CPUs"> +freebsd-tilera"> -FreeBSD tokenring mailing list"> -freebsd-tokenring"> +FreeBSD tokenring mailing list"> +freebsd-tokenring"> -FreeBSD integrated toolchain mailing list"> -freebsd-toolchain"> +FreeBSD integrated toolchain mailing list"> +freebsd-toolchain"> -FreeBSD USB mailing list"> -freebsd-usb"> +FreeBSD USB mailing list"> +freebsd-usb"> -FreeBSD user group coordination mailing list"> -freebsd-user-groups"> +FreeBSD user group coordination mailing list"> +freebsd-user-groups"> -FreeBSD vendors pre-release coordination mailing list"> -freebsd-vendors"> +FreeBSD vendors pre-release coordination mailing list"> +freebsd-vendors"> -Discussion of various virtualization techniques supported by FreeBSD"> -freebsd-virtualization"> +Discussion of various virtualization techniques supported by FreeBSD"> +freebsd-virtualization"> -Discussion on the VuXML -infrastructure"> -freebsd-vuxml"> +Discussion on the VuXML +infrastructure"> +freebsd-vuxml"> -FreeBSD Work-In-Progress Status"> -freebsd-wip-status"> +FreeBSD Work-In-Progress Status"> +freebsd-wip-status"> -Discussions of 802.11 stack, tools, device driver development"> -freebsd-wireless"> +Discussions of 802.11 stack, tools, device driver development"> +freebsd-wireless"> -FreeBSD Webmaster mailing list"> -freebsd-www"> +FreeBSD Webmaster mailing list"> +freebsd-www"> -FreeBSD X11 mailing list"> -freebsd-x11"> +FreeBSD X11 mailing list"> +freebsd-x11"> -FreeBSD port to Xen mailing list"> -freebsd-xen"> +FreeBSD port to Xen mailing list"> +freebsd-xen"> -XFCE for FreeBSD mailing list"> -freebsd-xfce"> +XFCE for FreeBSD mailing list"> +freebsd-xfce"> -Zope for FreeBSD mailing list"> -freebsd-zope"> +Zope for FreeBSD mailing list"> +freebsd-zope"> @@ -607,13 +607,13 @@ infrastructure"> --> -FreeBSD Alpha porting mailing list"> -freebsd-alpha"> +FreeBSD Alpha porting mailing list"> +freebsd-alpha"> -FreeBSD Quality Assurance mailing list"> -freebsd-qa"> +FreeBSD Quality Assurance mailing list"> +freebsd-qa"> -FreeBSD symmetric multiprocessing mailing list"> -freebsd-smp"> +FreeBSD symmetric multiprocessing mailing list"> +freebsd-smp"> Modified: projects/db5/en_US.ISO8859-1/share/xml/teams.ent ============================================================================== --- projects/db5/en_US.ISO8859-1/share/xml/teams.ent Fri May 31 07:46:21 2013 (r41783) +++ projects/db5/en_US.ISO8859-1/share/xml/teams.ent Fri May 31 07:47:02 2013 (r41784) @@ -15,38 +15,38 @@ $FreeBSD$ --> -admins@FreeBSD.org"> +admins@FreeBSD.org"> -bugmeister@FreeBSD.org"> +bugmeister@FreeBSD.org"> -core-secretary@FreeBSD.org"> +core-secretary@FreeBSD.org"> -cvsadm@FreeBSD.org"> +cvsadm@FreeBSD.org"> -cvsup-master@FreeBSD.org"> +cvsup-master@FreeBSD.org"> -doceng@FreeBSD.org"> +doceng@FreeBSD.org"> -donations@FreeBSD.org"> +donations@FreeBSD.org"> -faq@FreeBSD.org"> +faq@FreeBSD.org"> -ftp-master@FreeBSD.org"> +ftp-master@FreeBSD.org"> -mirror-admin@FreeBSD.org"> +mirror-admin@FreeBSD.org"> -ncvs@FreeBSD.org"> +ncvs@FreeBSD.org"> -perforce-admin@FreeBSD.org"> +perforce-admin@FreeBSD.org"> -pcvs@FreeBSD.org"> +pcvs@FreeBSD.org"> -portmgr@FreeBSD.org"> +portmgr@FreeBSD.org"> -portmgr-secretary@FreeBSD.org"> +portmgr-secretary@FreeBSD.org"> -projcvs@FreeBSD.org"> +projcvs@FreeBSD.org"> -re@FreeBSD.org"> +re@FreeBSD.org"> -security-officer@FreeBSD.org"> +security-officer@FreeBSD.org"> Modified: projects/db5/share/xml/authors.ent ============================================================================== --- projects/db5/share/xml/authors.ent Fri May 31 07:46:21 2013 (r41783) +++ projects/db5/share/xml/authors.ent Fri May 31 07:47:02 2013 (r41784) @@ -16,1450 +16,1450 @@ $FreeBSD$ --> -aaron@FreeBSD.org"> +aaron@FreeBSD.org"> -abial@FreeBSD.org"> +abial@FreeBSD.org"> -ache@FreeBSD.org"> +ache@FreeBSD.org"> -achim@FreeBSD.org"> +achim@FreeBSD.org"> -acm@FreeBSD.org"> +acm@FreeBSD.org"> -adam@FreeBSD.org"> +adam@FreeBSD.org"> -adamw@FreeBSD.org"> +adamw@FreeBSD.org"> -ade@FreeBSD.org"> +ade@FreeBSD.org"> -adrian@FreeBSD.org"> +adrian@FreeBSD.org"> -ae@FreeBSD.org"> +ae@FreeBSD.org"> -ahasty@FreeBSD.org"> +ahasty@FreeBSD.org"> -ahd@FreeBSD.org"> +ahd@FreeBSD.org"> -ahze@FreeBSD.org"> +ahze@FreeBSD.org"> *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 07:58:08 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 114D25C1; Fri, 31 May 2013 07:58:08 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 03641B6C; Fri, 31 May 2013 07:58:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4V7w7S1084538; Fri, 31 May 2013 07:58:07 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4V7w7T2084536; Fri, 31 May 2013 07:58:07 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305310758.r4V7w7T2084536@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 07:58:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41785 - projects/db5/en_US.ISO8859-1/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 07:58:08 -0000 Author: gabor Date: Fri May 31 07:58:07 2013 New Revision: 41785 URL: http://svnweb.freebsd.org/changeset/doc/41785 Log: - More namespace declarations and ulink conversions Modified: projects/db5/en_US.ISO8859-1/share/xml/mailing-lists.ent projects/db5/en_US.ISO8859-1/share/xml/newsgroups.ent Modified: projects/db5/en_US.ISO8859-1/share/xml/mailing-lists.ent ============================================================================== --- projects/db5/en_US.ISO8859-1/share/xml/mailing-lists.ent Fri May 31 07:47:02 2013 (r41784) +++ projects/db5/en_US.ISO8859-1/share/xml/mailing-lists.ent Fri May 31 07:58:07 2013 (r41785) @@ -596,10 +596,10 @@ infrastructure"> -bug-followup@FreeBSD.org"> +bug-followup@FreeBSD.org"> -majordomo@FreeBSD.org"> +majordomo@FreeBSD.org"> comp.unix.bsd.freebsd.misc + comp.unix.bsd.freebsd.misc newsgroup"> From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 11:47:00 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D006BC0A; Fri, 31 May 2013 11:47:00 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id C29979DB; Fri, 31 May 2013 11:47:00 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VBl0Hl065309; Fri, 31 May 2013 11:47:00 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VBl0Si065308; Fri, 31 May 2013 11:47:00 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311147.r4VBl0Si065308@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 11:47:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41786 - projects/db5/nl_NL.ISO8859-1/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 11:47:00 -0000 Author: gabor Date: Fri May 31 11:47:00 2013 New Revision: 41786 URL: http://svnweb.freebsd.org/changeset/doc/41786 Log: - Escape & Modified: projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml Modified: projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml ============================================================================== --- projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml Fri May 31 07:58:07 2013 (r41785) +++ projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml Fri May 31 11:47:00 2013 (r41786) @@ -1007,7 +1007,7 @@ Bell System Technical Journal, Unix Time-Sharing System - American Telephone & Telegraph Company + American Telephone & Telegraph Company July-August 1978 Vol 57, No 6, Deel 2 From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 11:53:21 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AA359D58; Fri, 31 May 2013 11:53:21 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 9CB27A5C; Fri, 31 May 2013 11:53:21 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VBrL3r067997; Fri, 31 May 2013 11:53:21 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VBrLxY067996; Fri, 31 May 2013 11:53:21 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311153.r4VBrLxY067996@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 11:53:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41787 - projects/db5/nl_NL.ISO8859-1/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 11:53:21 -0000 Author: gabor Date: Fri May 31 11:53:21 2013 New Revision: 41787 URL: http://svnweb.freebsd.org/changeset/doc/41787 Log: - Fix a closing tag Modified: projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml Modified: projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml ============================================================================== --- projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml Fri May 31 11:47:00 2013 (r41786) +++ projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml Fri May 31 11:53:21 2013 (r41787) @@ -548,7 +548,7 @@ O'Reilly & Associates - 1995 + 1995 ISBN 1-56592-127-5 From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 11:56:04 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E179DF58; Fri, 31 May 2013 11:56:04 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id D245BA8C; Fri, 31 May 2013 11:56:04 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VBu4Bv068688; Fri, 31 May 2013 11:56:04 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VBu4M5068682; Fri, 31 May 2013 11:56:04 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311156.r4VBu4M5068682@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 11:56:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41788 - in projects/db5: de_DE.ISO8859-1/share/xml en_US.ISO8859-1/books/bibliography hu_HU.ISO8859-2/share/xml nl_NL.ISO8859-1/share/xml share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 11:56:04 -0000 Author: gabor Date: Fri May 31 11:56:04 2013 New Revision: 41788 URL: http://svnweb.freebsd.org/changeset/doc/41788 Log: - Convert bibliographies to DB 5.0 Modified: projects/db5/de_DE.ISO8859-1/share/xml/bibliography.xml projects/db5/en_US.ISO8859-1/books/bibliography/book.xml projects/db5/hu_HU.ISO8859-2/share/xml/bibliography.xml projects/db5/nl_NL.ISO8859-1/share/xml/bibliography.xml projects/db5/share/xml/bibliography.xml Modified: projects/db5/de_DE.ISO8859-1/share/xml/bibliography.xml ============================================================================== --- projects/db5/de_DE.ISO8859-1/share/xml/bibliography.xml Fri May 31 11:53:21 2013 (r41787) +++ projects/db5/de_DE.ISO8859-1/share/xml/bibliography.xml Fri May 31 11:56:04 2013 (r41788) @@ -1,19 +1,19 @@ + - - + Bibliographie - + - 4.4BSD System Manager's Manual + 4.4BSD System Manager's Manual - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -25,16 +25,16 @@ 804 Seiten - ISBN 1-56592-080-5 + ISBN 1-56592-080-5 - + - 4.4BSD User's Reference Manual + 4.4BSD User's Reference Manual - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -46,16 +46,16 @@ 905 Seiten - ISBN 1-56592-075-9 + ISBN 1-56592-075-9 - + - 4.4BSD User's Supplementary Documents + 4.4BSD User's Supplementary Documents - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -67,16 +67,16 @@ 712 Seiten - ISBN 1-56592-076-7 + ISBN 1-56592-076-7 - + - 4.4BSD Programmer's Reference Manual + 4.4BSD Programmer's Reference Manual - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -88,16 +88,16 @@ 866 Seiten - ISBN 1-56592-078-3 + ISBN 1-56592-078-3 - + - 4.4BSD Programmer's Supplementary Documents + 4.4BSD Programmer's Supplementary Documents - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -109,45 +109,25 @@ 596 Seiten - ISBN 1-56592-079-1 + ISBN 1-56592-079-1 - + - The Design and Implementation of the 4.4BSD Operating - System + The Design and Implementation of the 4.4BSD Operating + System - - M. K. - - McKusick - - - - Kirk - - Marshall - - - - Keith + M. K.McKusick - Bostic - + KirkMarshall - - Michael J + KeithBostic - Karels - + Michael JKarels - - John - - Quarterman - + JohnQuarterman @@ -161,44 +141,24 @@ 1996 - ISBN 0-201-54979-4 + ISBN 0-201-54979-4 - + - Unix System Administration Handbook + Unix System Administration Handbook - - Evi - - Nemeth - - - - Garth - - Snyder - + EviNemeth - - Scott + GarthSnyder - Seebass - + ScottSeebass - - Trent R. + Trent R.Hein - Hein - - - - John - - Quarterman - + JohnQuarterman @@ -209,19 +169,15 @@ 2000 - ISBN 0-13-020601-6 + ISBN 0-13-020601-6 - + - The Complete FreeBSD + The Complete FreeBSD - - Greg - - Lehey - + GregLehey Walnut Creek @@ -233,15 +189,15 @@ 773 Seiten - ISBN 1-57176-246-9 + ISBN 1-57176-246-9 - + - The FreeBSD Handbook + The FreeBSD Handbook - FreeBSD Documentation Project + FreeBSD Documentation Project BSDi @@ -253,47 +209,27 @@ 489 pages - ISBN 1-57176-241-8 + ISBN 1-57176-241-8 - + McKusick et al, 1994 - Berkeley Software Architecture Manual, 4.4BSD - Edition + Berkeley Software Architecture Manual, 4.4BSD + Edition - - M. K. - - McKusick - - - - M. J. - - Karels - - - - S. J. - - Leffler - + M. K.McKusick - - W. N. + M. J.Karels - Joy - + S. J.Leffler - - R. S. + W. N.Joy - Faber - + R. S.Faber 5:1-42 Modified: projects/db5/en_US.ISO8859-1/books/bibliography/book.xml ============================================================================== --- projects/db5/en_US.ISO8859-1/books/bibliography/book.xml Fri May 31 11:53:21 2013 (r41787) +++ projects/db5/en_US.ISO8859-1/books/bibliography/book.xml Fri May 31 11:56:04 2013 (r41788) @@ -1,20 +1,17 @@ - ]> - - - - + + FreeBSD Bibliography - The FreeBSD Documentation Project + The FreeBSD Documentation Project February 1999 @@ -24,7 +21,7 @@ $FreeBSD$ - + &bibliography; Modified: projects/db5/hu_HU.ISO8859-2/share/xml/bibliography.xml ============================================================================== --- projects/db5/hu_HU.ISO8859-2/share/xml/bibliography.xml Fri May 31 11:53:21 2013 (r41787) +++ projects/db5/hu_HU.ISO8859-2/share/xml/bibliography.xml Fri May 31 11:56:04 2013 (r41788) @@ -7,23 +7,16 @@ %SOURCE% share/xml/bibliography.xml %SRCID% 1.10 --> - - + Irodalomjegyzék - + - FreeBSD Unleashed + FreeBSD Unleashed - - Michael - Urban - - - Brian - Tiemann - + MichaelUrban + BrianTiemann @@ -36,16 +29,16 @@ 2001 október - ISBN 0-67232-206-4 + ISBN 0-67232-206-4 - + - 4.4BSD System Manager's Manual + 4.4BSD System Manager's Manual - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -57,16 +50,16 @@ 804 oldal - ISBN 1-56592-080-5 + ISBN 1-56592-080-5 - + - 4.4BSD User's Reference Manual + 4.4BSD User's Reference Manual - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -78,16 +71,16 @@ 905 oldal - ISBN 1-56592-075-9 + ISBN 1-56592-075-9 - + - 4.4BSD User's Supplementary Documents + 4.4BSD User's Supplementary Documents - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -99,16 +92,16 @@ 712 oldal - ISBN 1-56592-076-7 + ISBN 1-56592-076-7 - + - 4.4BSD Programmer's Reference Manual + 4.4BSD Programmer's Reference Manual - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -120,16 +113,16 @@ 866 oldal - ISBN 1-56592-078-3 + ISBN 1-56592-078-3 - + - 4.4BSD Programmer's Supplementary Documents + 4.4BSD Programmer's Supplementary Documents - Computer Systems Research Group, University of - California, Berkeley + Computer Systems Research Group, University of + California, Berkeley O'Reilly and Associates @@ -141,44 +134,24 @@ 596 oldal - ISBN 1-56592-079-1 + ISBN 1-56592-079-1 - + - The Design and Implementation of the 4.4BSD Operating System + The Design and Implementation of the 4.4BSD Operating System - - M. K. - - McKusick - - - - Kirk - - Marshall - + M. K.McKusick - - Keith + KirkMarshall - Bostic - + KeithBostic - - Michael J + Michael JKarels - Karels - - - - John - - Quarterman - + JohnQuarterman @@ -192,24 +165,18 @@ 1996 - ISBN 0-201-54979-4 + ISBN 0-201-54979-4 - + - The Design and Implementation of the FreeBSD Operating System + The Design and Implementation of the FreeBSD Operating System - - M. K. - McKusick - - - - George V. - Neville-Neil - + M. K.McKusick + + George V.Neville-Neil @@ -221,44 +188,24 @@ 2004 - ISBN 0-201-70245-2 + ISBN 0-201-70245-2 - + - Unix System Administration Handbook + Unix System Administration Handbook - - Evi - - Nemeth - + EviNemeth - - Garth + GarthSnyder - Snyder - + ScottSeebass - - Scott + Trent R.Hein - Seebass - - - - Trent R. - - Hein - - - - John - - Quarterman - + JohnQuarterman @@ -269,19 +216,15 @@ 2000 - ISBN 0-13-020601-6 + ISBN 0-13-020601-6 - + - The Complete FreeBSD + The Complete FreeBSD - - Greg - - Lehey - + GregLehey Walnut Creek @@ -293,16 +236,16 @@ 773 oldal - ISBN 1-57176-246-9 + ISBN 1-57176-246-9 - + - The FreeBSD Handbook + The FreeBSD Handbook - FreeBSD Dokumentációs - Projekt + FreeBSD Dokumentációs + Projekt BSDi @@ -314,47 +257,27 @@ 489 oldal - ISBN 1-57176-241-8 + ISBN 1-57176-241-8 - + McKusick et al, 1994 - Berkeley Software Architecture Manual, 4.4BSD - Edition + Berkeley Software Architecture Manual, 4.4BSD + Edition - - M. K. - - McKusick - - - - M. J. + M. K.McKusick - Karels - + M. J.Karels - - S. J. + S. J.Leffler - Leffler - + W. N.Joy - - W. N. - - Joy - - - - R. S. - - Faber - + R. S.Faber 5:1-42 @@ -364,186 +287,165 @@ - + - FreeBSD for PC 98'ers (Japánul) + FreeBSD for PC 98'ers (Japánul) SHUWA System Co, LTD. - ISBN 4-87966-468-5 C3055 P2900E + ISBN 4-87966-468-5 C3055 P2900E - + - FreeBSD (Japánul) + FreeBSD (Japánul) CUTT - ISBN 4-906391-22-2 + ISBN 4-906391-22-2 - + - Complete Introduction to FreeBSD (Japánul) + Complete Introduction to FreeBSD (Japánul) Shoeisha Co., Ltd - ISBN 4-88135-473-6 P3600E + ISBN 4-88135-473-6 P3600E - + - Personal UNIX Starter Kit FreeBSD (Japánul) + Personal UNIX Starter Kit FreeBSD (Japánul) ASCII - ISBN 4-7561-1733-3 P3000E + ISBN 4-7561-1733-3 P3000E - + - FreeBSD Handbook (Japán - fordítás) + FreeBSD Handbook (Japán + fordítás) ASCII - ISBN 4-7561-1580-2 P3800E + ISBN 4-7561-1580-2 P3800E - + - FreeBSD mit Methode (Németül) + FreeBSD mit Methode (Németül) Computer und Literature Verlag/Vertrieb Hanser 1998 - ISBN 3-932311-31-0 + ISBN 3-932311-31-0 - + - FreeBSD install and Utilization Manual - (Japánul) + FreeBSD install and Utilization Manual + (Japánul) Mainichi Communications Inc. - + - Building Internet Server with FreeBSD (Indonéz - nyelven) + Building Internet Server with FreeBSD (Indonéz + nyelven) Elex Media Komputindo - - Onno W - Purbo - - - - Dodi - Maryanto - - - - Syahrial - Hubbany - - - - Widjil - Widodo - + Onno WPurbo + + DodiMaryanto + + SyahrialHubbany + + WidjilWidodo - + - The FreeBSD Corporate Networker's Guide + The FreeBSD Corporate Networker's Guide Addison-Wesley - + - UNIX in a Nutshell + UNIX in a Nutshell O'Reilly & Associates, Inc. 1990 - ISBN 093717520X + ISBN 093717520X - + - What You Need To Know When You Can't Find Your Unix System Administrator + What You Need To Know When You Can't Find Your Unix System Administrator O'Reilly & Associates, Inc. 1995 - - Linda - Mui - - ISBN 1-56592-104-6 + LindaMui + ISBN 1-56592-104-6 - + - FreeBSD User's Reference Manual (Japán - fordítás) + FreeBSD User's Reference Manual (Japán + fordítás) Mainichi Communications Inc. - Jpman Project, Japan FreeBSD Users Group + Jpman Project, Japan FreeBSD Users Group 1998 - ISBN 4-8399-0088-4 P3800E + ISBN 4-8399-0088-4 P3800E - + - Online Guide - for newcomers to the UNIX environment + Online Guide + for newcomers to the UNIX environment - Edinburgh University + Edinburgh University - + - DNS and BIND + DNS and BIND O'Reilly & Associates, Inc - ISBN 1-56592-512-2 + ISBN 1-56592-512-2 - - Paul Albitz - Albitz - - - - Cricket - Liu - + Paul AlbitzAlbitz + + CricketLiu 1998 @@ -551,211 +453,169 @@ - + - Sendmail + Sendmail O'Reilly & Associates, Inc 1997 második kiadás - *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 12:21:24 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 40A4869C; Fri, 31 May 2013 12:21:24 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 17F0ACC7; Fri, 31 May 2013 12:21:24 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VCLNRb078624; Fri, 31 May 2013 12:21:23 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VCLNun078620; Fri, 31 May 2013 12:21:23 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311221.r4VCLNun078620@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 12:21:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41789 - in projects/db5: en_US.ISO8859-1/articles/fbsd-from-scratch ja_JP.eucJP/articles/fbsd-from-scratch ru_RU.KOI8-R/articles/fbsd-from-scratch X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 12:21:24 -0000 Author: gabor Date: Fri May 31 12:21:23 2013 New Revision: 41789 URL: http://svnweb.freebsd.org/changeset/doc/41789 Log: - abstract should be in articleinfo Modified: projects/db5/en_US.ISO8859-1/articles/fbsd-from-scratch/article.xml projects/db5/ja_JP.eucJP/articles/fbsd-from-scratch/article.xml projects/db5/ru_RU.KOI8-R/articles/fbsd-from-scratch/article.xml Modified: projects/db5/en_US.ISO8859-1/articles/fbsd-from-scratch/article.xml ============================================================================== --- projects/db5/en_US.ISO8859-1/articles/fbsd-from-scratch/article.xml Fri May 31 11:56:04 2013 (r41788) +++ projects/db5/en_US.ISO8859-1/articles/fbsd-from-scratch/article.xml Fri May 31 12:21:23 2013 (r41789) @@ -29,7 +29,6 @@ $FreeBSD$ $FreeBSD$ - This article describes my efforts at &scratch.ap;: a fully @@ -39,6 +38,7 @@ think make world is a wonderful concept, &scratch.ap; extends it to make evenmore. + Introduction Modified: projects/db5/ja_JP.eucJP/articles/fbsd-from-scratch/article.xml ============================================================================== --- projects/db5/ja_JP.eucJP/articles/fbsd-from-scratch/article.xml Fri May 31 11:56:04 2013 (r41788) +++ projects/db5/ja_JP.eucJP/articles/fbsd-from-scratch/article.xml Fri May 31 12:21:23 2013 (r41789) @@ -36,7 +36,6 @@ $FreeBSD$ $FreeBSD$ - ¤³¤Îµ­»ö¤Ï¡¢¡Ö&scratch.ap; (FreeBSD From Scratch)¡×¤È¤¤¤¦¡¢ @@ -51,6 +50,7 @@ make evenmore (¤µ¤é¤Ë¤½¤ÎÀè) ¤Ø¤È¹­¤²¤ë¤â¤Î¤Ë¤Ê¤ë¤³¤È¤Ç¤·¤ç¤¦¡£ + ¤Ï¤¸¤á¤Ë Modified: projects/db5/ru_RU.KOI8-R/articles/fbsd-from-scratch/article.xml ============================================================================== --- projects/db5/ru_RU.KOI8-R/articles/fbsd-from-scratch/article.xml Fri May 31 11:56:04 2013 (r41788) +++ projects/db5/ru_RU.KOI8-R/articles/fbsd-from-scratch/article.xml Fri May 31 12:21:23 2013 (r41789) @@ -41,7 +41,6 @@ $FreeBSD$ $FreeBSD$ - ÷ ÜÔÏÊ ÓÔÁÔØÅ ÏÐÉÓÙ×ÁÀÔÓÑ ÍÏÉ ÄÏÓÔÉÖÅÎÉÑ × ÓÏÚÄÁÎÉÉ &scratch.ap;: @@ -52,6 +51,7 @@ Ñ×ÌÑÅÔÓÑ ÐÒÅËÒÁÓÎÙÍ ÐÏÄÈÏÄÏÍ, ÔÏ &scratch.ap; ÒÁÓÛÉÒÑÅÔ ÜÔÏ ÐÏÎÑÔÉÅ ÄÏ make evenmore. + ÷×ÅÄÅÎÉÅ From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 12:23:35 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D8C6B702; Fri, 31 May 2013 12:23:35 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id B14F3CD7; Fri, 31 May 2013 12:23:35 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VCNZ3H079063; Fri, 31 May 2013 12:23:35 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VCNZcp079062; Fri, 31 May 2013 12:23:35 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311223.r4VCNZcp079062@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 12:23:35 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41790 - projects/db5/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 12:23:35 -0000 Author: gabor Date: Fri May 31 12:23:35 2013 New Revision: 41790 URL: http://svnweb.freebsd.org/changeset/doc/41790 Log: - Add more namespace declarations Modified: projects/db5/share/xml/authors.ent Modified: projects/db5/share/xml/authors.ent ============================================================================== --- projects/db5/share/xml/authors.ent Fri May 31 12:21:23 2013 (r41789) +++ projects/db5/share/xml/authors.ent Fri May 31 12:23:35 2013 (r41790) @@ -46,7 +46,7 @@ akiyama@FreeBSD.org"> -alane@FreeBSD.org"> +alane@FreeBSD.org"> alc@FreeBSD.org"> @@ -230,7 +230,7 @@ ceri@FreeBSD.org"> -cg@FreeBSD.org"> +cg@FreeBSD.org"> charnier@FreeBSD.org"> @@ -574,7 +574,7 @@ itetcu@FreeBSD.org"> -itojun@FreeBSD.org"> +itojun@FreeBSD.org"> ivoras@FreeBSD.org"> @@ -596,7 +596,7 @@ jayanth@FreeBSD.org"> -jb@FreeBSD.org"> +jb@FreeBSD.org"> jcamou@FreeBSD.org"> @@ -680,7 +680,7 @@ jmg@FreeBSD.org"> -jmz@FreeBSD.org"> +jmz@FreeBSD.org"> joe@FreeBSD.org"> From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 12:24:38 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E4F99747; Fri, 31 May 2013 12:24:38 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id BC5A3CDC; Fri, 31 May 2013 12:24:38 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VCOcIk079284; Fri, 31 May 2013 12:24:38 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VCOcMC079283; Fri, 31 May 2013 12:24:38 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311224.r4VCOcMC079283@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 12:24:38 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41791 - projects/db5/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 12:24:39 -0000 Author: gabor Date: Fri May 31 12:24:38 2013 New Revision: 41791 URL: http://svnweb.freebsd.org/changeset/doc/41791 Log: - Allow buildtarget in para Modified: projects/db5/share/xml/docbook50.dtd Modified: projects/db5/share/xml/docbook50.dtd ============================================================================== --- projects/db5/share/xml/docbook50.dtd Fri May 31 12:23:35 2013 (r41790) +++ projects/db5/share/xml/docbook50.dtd Fri May 31 12:24:38 2013 (r41791) @@ -292,7 +292,7 @@ > + revnumber|buildtarget|xi:include)*> Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2C795CB3; Fri, 31 May 2013 12:45:00 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 02E1ADED; Fri, 31 May 2013 12:45:00 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VCix5C086138; Fri, 31 May 2013 12:44:59 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VCixbr086132; Fri, 31 May 2013 12:44:59 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311244.r4VCixbr086132@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 12:44:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41792 - in projects/db5: de_DE.ISO8859-1/articles/freebsd-update-server en_US.ISO8859-1/articles/freebsd-update-server pt_BR.ISO8859-1/articles/freebsd-update-server X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 12:45:00 -0000 Author: gabor Date: Fri May 31 12:44:58 2013 New Revision: 41792 URL: http://svnweb.freebsd.org/changeset/doc/41792 Log: - abstract should be part of articleinfo Modified: projects/db5/de_DE.ISO8859-1/articles/freebsd-update-server/article.xml projects/db5/en_US.ISO8859-1/articles/freebsd-update-server/article.xml projects/db5/pt_BR.ISO8859-1/articles/freebsd-update-server/article.xml Modified: projects/db5/de_DE.ISO8859-1/articles/freebsd-update-server/article.xml ============================================================================== --- projects/db5/de_DE.ISO8859-1/articles/freebsd-update-server/article.xml Fri May 31 12:24:38 2013 (r41791) +++ projects/db5/de_DE.ISO8859-1/articles/freebsd-update-server/article.xml Fri May 31 12:44:58 2013 (r41792) @@ -41,7 +41,6 @@ $FreeBSD$ $FreeBSD$ - Dieser Artikel beschreibt den Bau eines internen &fbus.ap;. @@ -55,6 +54,7 @@ Releases oder über Bereitstellung eines lokalen Mirror, welcher schnellere Updates ermöglicht, erweitern. + Übersetzt von Björn Heidotting. Modified: projects/db5/en_US.ISO8859-1/articles/freebsd-update-server/article.xml ============================================================================== --- projects/db5/en_US.ISO8859-1/articles/freebsd-update-server/article.xml Fri May 31 12:24:38 2013 (r41791) +++ projects/db5/en_US.ISO8859-1/articles/freebsd-update-server/article.xml Fri May 31 12:44:58 2013 (r41792) @@ -34,7 +34,6 @@ $FreeBSD$ $FreeBSD$ - This article describes building an internal &fbus.ap;. @@ -47,6 +46,7 @@ &os; releases or by providing a local mirror that will allow faster updates for a number of machines. + Acknowledgments Modified: projects/db5/pt_BR.ISO8859-1/articles/freebsd-update-server/article.xml ============================================================================== --- projects/db5/pt_BR.ISO8859-1/articles/freebsd-update-server/article.xml Fri May 31 12:24:38 2013 (r41791) +++ projects/db5/pt_BR.ISO8859-1/articles/freebsd-update-server/article.xml Fri May 31 12:44:58 2013 (r41792) @@ -42,7 +42,6 @@ $FreeBSD$ $FreeBSD$ - Este artigo descreve como construir um &fbus.ap; para uso @@ -57,6 +56,7 @@ local o qual permitirá atualizações mais rápidas caso você possua muitos servidores para atualizar. + Agradecimentos From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 12:51:20 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4EB7C114; Fri, 31 May 2013 12:51:20 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 4117CF02; Fri, 31 May 2013 12:51:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VCpKVI088870; Fri, 31 May 2013 12:51:20 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VCpJop088869; Fri, 31 May 2013 12:51:20 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311251.r4VCpJop088869@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 12:51:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41793 - projects/db5/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 12:51:20 -0000 Author: gabor Date: Fri May 31 12:51:19 2013 New Revision: 41793 URL: http://svnweb.freebsd.org/changeset/doc/41793 Log: - Add namespace declarations - id --> xml:id Modified: projects/db5/share/xml/trademarks.ent Modified: projects/db5/share/xml/trademarks.ent ============================================================================== --- projects/db5/share/xml/trademarks.ent Fri May 31 12:44:58 2013 (r41792) +++ projects/db5/share/xml/trademarks.ent Fri May 31 12:51:19 2013 (r41793) @@ -425,7 +425,7 @@ Coverity, Inc."> ® symbol."> + Copyright Redistribution and use in source (XML DocBook) and 'compiled' @@ -467,7 +467,7 @@ Coverity, Inc."> '> + Legal Notice FreeBSD is a registered trademark of The FreeBSD Foundation. From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 12:57:12 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3E4251EB; Fri, 31 May 2013 12:57:12 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 16884F51; Fri, 31 May 2013 12:57:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VCvBmQ089925; Fri, 31 May 2013 12:57:11 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VCvBaO089921; Fri, 31 May 2013 12:57:11 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311257.r4VCvBaO089921@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 12:57:11 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41794 - in projects/db5: en_US.ISO8859-1/articles/pam fr_FR.ISO8859-1/articles/pam ru_RU.KOI8-R/articles/pam X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 12:57:12 -0000 Author: gabor Date: Fri May 31 12:57:11 2013 New Revision: 41794 URL: http://svnweb.freebsd.org/changeset/doc/41794 Log: - bibliography's abstract should be in bibliographyinf Modified: projects/db5/en_US.ISO8859-1/articles/pam/article.xml projects/db5/fr_FR.ISO8859-1/articles/pam/article.xml projects/db5/ru_RU.KOI8-R/articles/pam/article.xml Modified: projects/db5/en_US.ISO8859-1/articles/pam/article.xml ============================================================================== --- projects/db5/en_US.ISO8859-1/articles/pam/article.xml Fri May 31 12:51:19 2013 (r41793) +++ projects/db5/en_US.ISO8859-1/articles/pam/article.xml Fri May 31 12:57:11 2013 (r41794) @@ -1262,12 +1262,14 @@ sshd password required pam_permit.so + Further Reading This is a list of documents relevant to PAM and related issues. It is by no means complete. + Papers Modified: projects/db5/fr_FR.ISO8859-1/articles/pam/article.xml ============================================================================== --- projects/db5/fr_FR.ISO8859-1/articles/pam/article.xml Fri May 31 12:51:19 2013 (r41793) +++ projects/db5/fr_FR.ISO8859-1/articles/pam/article.xml Fri May 31 12:57:11 2013 (r41794) @@ -1256,6 +1256,7 @@ sshd password required pam_permit.so + Lectures complémentaires @@ -1263,6 +1264,7 @@ sshd password required pam_permit.so + Publications Modified: projects/db5/ru_RU.KOI8-R/articles/pam/article.xml ============================================================================== --- projects/db5/ru_RU.KOI8-R/articles/pam/article.xml Fri May 31 12:51:19 2013 (r41793) +++ projects/db5/ru_RU.KOI8-R/articles/pam/article.xml Fri May 31 12:57:11 2013 (r41794) @@ -1310,12 +1310,14 @@ sshd password required p + äÏÐÏÌÎÉÔÅÌØÎÁÑ ÌÉÔÅÒÁÔÕÒÁ üÔÏ ÓÐÉÓÏË ÄÏËÕÍÅÎÔÏ×, ÏÔÎÏÓÑÝÉÈÓÑ Ë PAM É Ó×ÑÚÁÎÎÙÍ ×ÏÐÒÏÓÁÍ. ïÎ, ÎÅÓÏÍÎÅÎÎÏ, ÎÅ Ñ×ÌÑÅÔÓÑ ÐÏÌÎÙÍ. + òÁÂÏÔÙ From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 13:16:55 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1B7E74B6; Fri, 31 May 2013 13:16:55 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id F0F04BD; Fri, 31 May 2013 13:16:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VDGsE8097216; Fri, 31 May 2013 13:16:54 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VDGs4C097212; Fri, 31 May 2013 13:16:54 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311316.r4VDGs4C097212@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 13:16:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41795 - in projects/db5: en_US.ISO8859-1/articles/pr-guidelines ru_RU.KOI8-R/articles/pr-guidelines share/xml zh_TW.Big5/articles/pr-guidelines X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 13:16:55 -0000 Author: gabor Date: Fri May 31 13:16:53 2013 New Revision: 41795 URL: http://svnweb.freebsd.org/changeset/doc/41795 Log: - Move two manpage entities to man-refs.ent Modified: projects/db5/en_US.ISO8859-1/articles/pr-guidelines/article.xml projects/db5/ru_RU.KOI8-R/articles/pr-guidelines/article.xml projects/db5/share/xml/man-refs.ent projects/db5/zh_TW.Big5/articles/pr-guidelines/article.xml Modified: projects/db5/en_US.ISO8859-1/articles/pr-guidelines/article.xml ============================================================================== --- projects/db5/en_US.ISO8859-1/articles/pr-guidelines/article.xml Fri May 31 12:57:11 2013 (r41794) +++ projects/db5/en_US.ISO8859-1/articles/pr-guidelines/article.xml Fri May 31 13:16:53 2013 (r41795) @@ -1,9 +1,6 @@ edit-pr1"> -query-pr1"> -]> + "../../../share/xml/freebsd45.dtd">
Modified: projects/db5/ru_RU.KOI8-R/articles/pr-guidelines/article.xml ============================================================================== --- projects/db5/ru_RU.KOI8-R/articles/pr-guidelines/article.xml Fri May 31 12:57:11 2013 (r41794) +++ projects/db5/ru_RU.KOI8-R/articles/pr-guidelines/article.xml Fri May 31 13:16:53 2013 (r41795) @@ -1,9 +1,6 @@ edit-pr1"> -query-pr1"> -]> + "../../../share/xml/freebsd45.dtd"> From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 14:06:43 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 39EC693D; Fri, 31 May 2013 14:06:43 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 12CD0644; Fri, 31 May 2013 14:06:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VE6g4Q014570; Fri, 31 May 2013 14:06:42 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VE6ghQ014569; Fri, 31 May 2013 14:06:42 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311406.r4VE6ghQ014569@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 14:06:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41796 - projects/db5/share/xml X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 14:06:43 -0000 Author: gabor Date: Fri May 31 14:06:42 2013 New Revision: 41796 URL: http://svnweb.freebsd.org/changeset/doc/41796 Log: - Allow buildtarget in quote Modified: projects/db5/share/xml/docbook50.dtd Modified: projects/db5/share/xml/docbook50.dtd ============================================================================== --- projects/db5/share/xml/docbook50.dtd Fri May 31 13:16:53 2013 (r41795) +++ projects/db5/share/xml/docbook50.dtd Fri May 31 14:06:42 2013 (r41796) @@ -1515,7 +1515,8 @@ > - + Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 17CE3AE6; Fri, 31 May 2013 14:11:11 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 0A288698; Fri, 31 May 2013 14:11:11 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VEBAdG017277; Fri, 31 May 2013 14:11:10 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VEBA7V017276; Fri, 31 May 2013 14:11:10 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311411.r4VEBA7V017276@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 14:11:10 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41797 - projects/db5/en_US.ISO8859-1/articles/fonts X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 14:11:11 -0000 Author: gabor Date: Fri May 31 14:11:10 2013 New Revision: 41797 URL: http://svnweb.freebsd.org/changeset/doc/41797 Log: - trademark is not allowed in screen Modified: projects/db5/en_US.ISO8859-1/articles/fonts/article.xml Modified: projects/db5/en_US.ISO8859-1/articles/fonts/article.xml ============================================================================== --- projects/db5/en_US.ISO8859-1/articles/fonts/article.xml Fri May 31 14:06:42 2013 (r41796) +++ projects/db5/en_US.ISO8859-1/articles/fonts/article.xml Fri May 31 14:11:10 2013 (r41797) @@ -567,7 +567,7 @@ GS>quit Many .afm files are in Mac format… ^M delimited lines -We need to convert them to &unix; style ^J delimited lines +We need to convert them to UNIX™ style ^J delimited lines &prompt.user; cd /tmp &prompt.user; cat /usr/local/share/fonts/type1/showboat.afm | tr '\015' '\012' >showboat.afm From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 14:20:56 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 91F68D5D; Fri, 31 May 2013 14:20:56 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 8491D758; Fri, 31 May 2013 14:20:56 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VEKuBG020761; Fri, 31 May 2013 14:20:56 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VEKu31020760; Fri, 31 May 2013 14:20:56 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201305311420.r4VEKu31020760@svn.freebsd.org> From: Gabor Kovesdan Date: Fri, 31 May 2013 14:20:56 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41798 - projects/db5/ja_JP.eucJP/articles/fonts X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 14:20:56 -0000 Author: gabor Date: Fri May 31 14:20:56 2013 New Revision: 41798 URL: http://svnweb.freebsd.org/changeset/doc/41798 Log: - trademark is not allowed in screen Modified: projects/db5/ja_JP.eucJP/articles/fonts/article.xml Modified: projects/db5/ja_JP.eucJP/articles/fonts/article.xml ============================================================================== --- projects/db5/ja_JP.eucJP/articles/fonts/article.xml Fri May 31 14:11:10 2013 (r41797) +++ projects/db5/ja_JP.eucJP/articles/fonts/article.xml Fri May 31 14:20:56 2013 (r41798) @@ -598,7 +598,7 @@ GS>quit .afm ¥Õ¥¡¥¤¥ë¤Î¿¤¯¤Ï Mac ·Á¼°… ¤¹¤Ê¤ï¤Á¹Ô¤¬ ^M ¤Ç¶èÀÚ¤é¤ì¤Æ¤¤¤Þ¤¹¡£ -¤³¤ì¤ò¹Ô¤ò ^J ¤Ç¶èÀÚ¤ë &unix; ¥¹¥¿¥¤¥ë¤ËÊÑ´¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ +¤³¤ì¤ò¹Ô¤ò ^J ¤Ç¶èÀÚ¤ë UNIX™ ¥¹¥¿¥¤¥ë¤ËÊÑ´¹¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ &prompt.user; cd /tmp &prompt.user; cat /usr/local/share/fonts/type1/showboat.afm | tr '\015' '\012' >showboat.afm From owner-svn-doc-projects@FreeBSD.ORG Fri May 31 15:16:03 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4D5749EB; Fri, 31 May 2013 15:16:03 +0000 (UTC) (envelope-from crees@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 4029EA11; Fri, 31 May 2013 15:16:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4VFG2C5040960; Fri, 31 May 2013 15:16:02 GMT (envelope-from crees@svn.freebsd.org) Received: (from crees@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4VFG2De040959; Fri, 31 May 2013 15:16:02 GMT (envelope-from crees@svn.freebsd.org) Message-Id: <201305311516.r4VFG2De040959@svn.freebsd.org> From: Chris Rees Date: Fri, 31 May 2013 15:16:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41800 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 15:16:03 -0000 Author: crees Date: Fri May 31 15:16:02 2013 New Revision: 41800 URL: http://svnweb.freebsd.org/changeset/doc/41800 Log: MFH (r41782): Clarify the wording on broken ports, and remove uses of "You". Requested by: trhodes Approved by: gjb (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Directory Properties: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/ (props changed) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Fri May 31 14:46:48 2013 (r41799) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ports/chapter.xml Fri May 31 15:16:02 2013 (r41800) @@ -1869,14 +1869,13 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ Dealing with Broken Ports - If you come across a port that does not compile: + When coming across a port that does not build or install: Find out if there is a fix pending for the port in the Problem - Report database. If so, you may be able to use - the proposed fix. + Report database. If so, the proposed fix may work. From owner-svn-doc-projects@FreeBSD.ORG Sat Jun 1 01:32:08 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3897839F; Sat, 1 Jun 2013 01:32:08 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 29E7F6DD; Sat, 1 Jun 2013 01:32:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r511W7xV058636; Sat, 1 Jun 2013 01:32:07 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r511W7SJ058635; Sat, 1 Jun 2013 01:32:07 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201306010132.r511W7SJ058635@svn.freebsd.org> From: Tom Rhodes Date: Sat, 1 Jun 2013 01:32:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41805 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jun 2013 01:32:08 -0000 Author: trhodes Date: Sat Jun 1 01:32:07 2013 New Revision: 41805 URL: http://svnweb.freebsd.org/changeset/doc/41805 Log: Add a generic "get an ldap server running" section. Discussed with: many in #bsddocs Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat Jun 1 00:23:11 2013 (r41804) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat Jun 1 01:32:07 2013 (r41805) @@ -47,6 +47,16 @@ + How to set &os; up to act as an LDAP + server or client + + + + How to set &os; up to act as an LDAP + server or client + + + How to set up automatic network settings using DHCP. @@ -2596,6 +2606,638 @@ nis_client_flags="-S NIS do + + + + + Tom + Rhodes + Written by + + + + &os; and <acronym>LDAP</acronym> + + LDAP + + LDAP, the Lightweight Directory Access + Protocol, is an application layer protocol used to access, + modify, and authenticate (bind) using a distributed directory + information service. Think of it as a phone or record book which + stores several levels of hierarchical, homogeneous information. + It is often used in networks where users often need access to + several levels of internal information utilizing a single + account. For example, email authentication, pulling employee + contact information, and internal website authentication might + all make use of a single user in the LDAP + server's record base. + + This section will not provide a history or the implementation + details of the protocol. These sections were authored to get an + LDAP server and/or client configured both + quickly and securely; however, any information base requires + planning and this is no exception. + + Planning should include what type of information will be + stored, what that information will be used for, whom should + have access to said information, and how to secure this + information from prying eyes. + + + <acronym>LDAP</acronym> Terminology and Structure + + Before continuing, several parts of LDAP + must be explained to prevent confusion. And confusion with + this configuration is relatively simple. To begin, all + directory entries consist of a group of + attributes. Each of these attribute sets + contain a name, a unique identifier known as a + DN or distinguished name normally built from + several other attributes such as the RDN. + The RDN or relative distinguished name, is + a more common name for the attribute. Like directories have + absolute and relative paths, consider a DN + as an absolute path and the RDN as the + relative path. + + As an example, an entry might look like the + following: + + &prompt.user; ldapsearch -xb "uid=trhodes,ou=users,o=example.com" + + # extended LDIF +# +# LDAPv3 +# base <uid=trhodes,ou=users,o=example.com> with scope subtree +# filter: (objectclass=*) +# requesting: ALL +# + +# trhodes, users, example.com +dn: uid=trhodes,ou=users,o=example.com +mail: trhodes@example.com +cn: Tom Rhodes +uid: trhodes +telephoneNumber: (xxx) xxx-xxxx + +# search result +search: 2 +result: 0 Success + +# numResponses: 2 +# numEntries: 1 + + In this example, it is very obvious what the various + attributes are; however, the cn attribute + should be noticed. This is the RDN discussed + previously. In addition, there is a unique user id provided + here. It is common practice to have specific uid or uuids for + entries to ease in any future migration. + + + + Configuring an <acronym>LDAP</acronym> Server + + LDAP Server + + To configure &os; to act as an LDAP + server, the OpenLDAP port needs installed. This may be + accomplished using the pkg_add command + or by installing the + net/openldap24-server + port. Building the port is recommended as the administrator + may select a great deal of options at this time and disable + some options. In most cases, the defaults will be fine; + however, this is the time to enable SQL support if + needed. + + A few directories will be required from this point on, + at minimal, a data directory and a directory to store the + certificates in. Create them both with the following + commands: + + &prompt.root; mkdir /var/db/openldap-data + + &prompt.root; mkdir /usr/local/etc/openldap/private + + Copy over the database configuration file: + + &prompt.root; cp /usr/local/etc/openldap/DB_CONFIG.example /var/db/openldap-data/DB_CONFIG + + The next phase is to configure the SSL + certificates. While creating certificates is discussed in + the OpenSSL section in this + book, a certificate authority is needed so a different method + will be used. It is recommended that this section be reviewed + prior to configuring to ensure correct information is entered + during the certificate creation process below. + + The following commands must be executed in the + + /usr/local/etc/openldap/private directory. This + is important as the file permissions will need to be restrictive + and users should not have access to these files directly. To + create the certificates, issues the following commands. + + &prompt.root; openssl req -days 365 -nodes -new -x509 -keyout ca.key -out ../ca.crt + + The entries for these may be completely generic + except for the + Common Name entry. This entry must have + something different than the system hostname. If the entry + is the hostname, it would be like the hostname is attempting + to verify hostname. In cases with a self signed certificate + like this example, just prefix the hostname with + CA for certificate authority. + + The next task is to create a certificate signing request + and a private key. To do this, issue the following + commands: + + &prompt.root; openssl req -days 365 -nodes -new -keyout server.key -out server.csr + + During the certificate generation process, be sure to + correctly set the common name attribute. After this has + been completed, the key will need signed: + + &prompt.root; openssl x509 -req -days 365 -in server.csr -out ../server.crt -CA ../ca.crt -CAkey ca.key -CAcreateserial + + The final part of the certificate generation process + is to generate and sign the client certificates: + + &prompt.root; openssl req -days 365 -nodes -new -keyout client.key -out client.csr + + &prompt.root; openssl x509 -req -days 3650 -in client.csr -out ../client.crt -CA ../ca.crt -CAkey ca.key + + Remember, again, to respect the common name attribute. This + is a common cause for confusion during the first attempt to + configure LDAP. In addition, ensure that + a total of eight (8) new files have been generated through + the proceeding commands. If so, the next step is to edit + /usr/local/etc/openldap/slapd.conf and add + the following options: + + TLSCipherSuite HIGH:MEDIUM:+SSLv3 +TLSCertificateFile /usr/local/etc/openldap/server.crt +TLSCertificateKeyFile /usr/local/etc/openldap/private/server.key +TLSCACertificateFile /usr/local/etc/openldap/ca.crt + + In addition, edit + /usr/local/etc/openldap/ldap.conf and + add the following lines: + + TLS_CACERT /usr/local/etc/openldap/ca.crt +TLS_CIPHER_SUITE HIGH:MEDIUM:+SSLv3 + + While editing these this file, set the + to the desired values, and uncomment all three of the + , and + options. In addition, set the + to contain + and . + + The resulting file should look similar to the following + shown here: + + BASE dc=example,dc=com +URI ldap:// ldaps:// + +SIZELIMIT 12 +TIMELIMIT 15 +#DEREF never + +TLS_CACERT /usr/local/etc/openldap/ca.crt +TLS_CIPHER_SUITE HIGH:MEDIUM:+SSLv3 + + A password for the server will need to be created as the + default is extremely poor as is normal in this industry. To + do this, issue the following command, sending the output to + slapd.conf: + + &prompt.root; slappasswd -h "{SHA}" >> /usr/local/etc/openldap/slapd.conf + + There will be a prompt for entering the password and, + if the process does not fail, a password hash will be added + to the end of slapd.conf. The + slappasswd understands several hashing + formats, refer to the manual page for more information. + + Edit /usr/local/etc/openldap/slapd.conf + and add the following lines: + + password-hash {sha} +allow bind_v2 + + In addition, the in this file must + be updated to match the from the previous + configuration. The option should + also be set. A good recommendation is something like + . Before saving this file, place + the option in front of the password + output from the slappasswd and delete the + old option above. The end result + should look similar to this: + + TLSCipherSuite HIGH:MEDIUM:+SSLv3 +TLSCertificateFile /usr/local/etc/openldap/server.crt +TLSCertificateKeyFile /usr/local/etc/openldap/private/server.key +TLSCACertificateFile /usr/local/etc/openldap/ca.crt +rootpw {SHA}W6ph5Mm5Pz8GgiULbPgzG37mj9g= + + Finally, enable the OpenLDAP + service in rc.conf. At this time, + setting up a URI and providing the group + and user to run as may be useful. + Edit /etc/rc.conf and add the following + lines: + + slapd_enable="YES" +slapd_flags="-4 -h ldaps:///" + + At this point the server should be ready to be brought + up and tested. To perform this task, issue the following + command: + + &prompt.root; service slapd start + + If everything was configured correctly, a search of the + directory should show a successful connection with a single + response as in this example: + + &prompt.root; ldapsearch -Z + + # extended LDIF +# +# LDAPv3 +# base <dc=example,dc=com> (default) with scope subtree +# filter: (objectclass=*) +# requesting: ALL +# + +# search result +search: 3 +result: 32 No such object + +# numResponses: 1 + + + + + + + + + + Tom + Rhodes + Written by + + + + &os; and <acronym>LDAP</acronym> + + LDAP + + LDAP, the Lightweight Directory Access + Protocol, is an application layer protocol used to access, + modify, and authenticate (bind) using a distributed directory + information service. Think of it as a phone or record book which + stores several levels of hierarchical, homogeneous information. + It is often used in networks where users often need access to + several levels of internal information utilizing a single + account. For example, email authentication, pulling employee + contact information, and internal website authentication might + all make use of a single user in the LDAP + server's record base. + + This section will not provide a history or the implementation + details of the protocol. These sections were authored to get an + LDAP server and/or client configured both + quickly and securely; however, any information base requires + planning and this is no exception. + + Planning should include what type of information will be + stored, what that information will be used for, whom should + have access to said information, and how to secure this + information from prying eyes. + + + <acronym>LDAP</acronym> Terminology and Structure + + Before continuing, several parts of LDAP + must be explained to prevent confusion. And confusion with + this configuration is relatively simple. To begin, all + directory entries consist of a group of + attributes. Each of these attribute sets + contain a name, a unique identifier known as a + DN or distinguished name normally built from + several other attributes such as the RDN. + The RDN or relative distinguished name, is + a more common name for the attribute. Like directories have + absolute and relative paths, consider a DN + as an absolute path and the RDN as the + relative path. + + As an example, an entry might look like the + following: + + &prompt.user; ldapsearch -xb "uid=trhodes,ou=users,o=example.com" + + # extended LDIF +# +# LDAPv3 +# base <uid=trhodes,ou=users,o=example.com> with scope subtree +# filter: (objectclass=*) +# requesting: ALL +# + +# trhodes, users, example.com +dn: uid=trhodes,ou=users,o=example.com +mail: trhodes@example.com +cn: Tom Rhodes +uid: trhodes +telephoneNumber: (xxx) xxx-xxxx + +# search result +search: 2 +result: 0 Success + +# numResponses: 2 +# numEntries: 1 + + In this example, it is very obvious what the various + attributes are; however, the cn attribute + should be noticed. This is the RDN discussed + previously. In addition, there is a unique user id provided + here. It is common practice to have specific uid or uuids for + entries to ease in any future migration. + + + + Configuring an <acronym>LDAP</acronym> Server + + LDAP Server + + To configure &os; to act as an LDAP + server, the OpenLDAP port needs installed. This may be + accomplished using the pkg_add command + or by installing the + net/openldap24-server + port. Building the port is recommended as the administrator + may select a great deal of options at this time and disable + some options. In most cases, the defaults will be fine; + however, this is the time to enable SQL support if + needed. + + A few directories will be required from this point on, + at minimal, a data directory and a directory to store the + certificates in. Create them both with the following + commands: + + &prompt.root; mkdir /var/db/openldap-data + + &prompt.root; mkdir /usr/local/etc/openldap/private + + Copy over the database configuration file: + + &prompt.root; cp /usr/local/etc/openldap/DB_CONFIG.example /var/db/openldap-data/DB_CONFIG + + The next phase is to configure the SSL + certificates. While creating certificates is discussed in + the OpenSSL section in this + book, a certificate authority is needed so a different method + will be used. It is recommended that this section be reviewed + prior to configuring to ensure correct information is entered + during the certificate creation process below. + + The following commands must be executed in the + + /usr/local/etc/openldap/private directory. This + is important as the file permissions will need to be restrictive + and users should not have access to these files directly. To + create the certificates, issues the following commands. + + &prompt.root; openssl req -days 365 -nodes -new -x509 -keyout ca.key -out ../ca.crt + + The entries for these may be completely generic + except for the + Common Name entry. This entry must have + something different than the system hostname. If the entry + is the hostname, it would be like the hostname is attempting + to verify hostname. In cases with a self signed certificate + like this example, just prefix the hostname with + CA for certificate authority. + + The next task is to create a certificate signing request + and a private key. To do this, issue the following + commands: + + &prompt.root; openssl req -days 365 -nodes -new -keyout server.key -out server.csr + + During the certificate generation process, be sure to + correctly set the common name attribute. After this has + been completed, the key will need signed: + + &prompt.root; openssl x509 -req -days 365 -in server.csr -out ../server.crt -CA ../ca.crt -CAkey ca.key -CAcreateserial + + The final part of the certificate generation process + is to generate and sign the client certificates: + + &prompt.root; openssl req -days 365 -nodes -new -keyout client.key -out client.csr + + &prompt.root; openssl x509 -req -days 3650 -in client.csr -out ../client.crt -CA ../ca.crt -CAkey ca.key + + Remember, again, to respect the common name attribute. This + is a common cause for confusion during the first attempt to + configure LDAP. In addition, ensure that + a total of eight (8) new files have been generated through + the proceeding commands. If so, the next step is to edit + /usr/local/etc/openldap/slapd.conf and add + the following options: + + TLSCipherSuite HIGH:MEDIUM:+SSLv3 +TLSCertificateFile /usr/local/etc/openldap/server.crt +TLSCertificateKeyFile /usr/local/etc/openldap/private/server.key +TLSCACertificateFile /usr/local/etc/openldap/ca.crt + + In addition, edit + /usr/local/etc/openldap/ldap.conf and + add the following lines: + + TLS_CACERT /usr/local/etc/openldap/ca.crt +TLS_CIPHER_SUITE HIGH:MEDIUM:+SSLv3 + + While editing these this file, set the + to the desired values, and uncomment all three of the + , and + options. In addition, set the + to contain + and . + + The resulting file should look similar to the following + shown here: + + BASE dc=example,dc=com +URI ldap:// ldaps:// + +SIZELIMIT 12 +TIMELIMIT 15 +#DEREF never + +TLS_CACERT /usr/local/etc/openldap/ca.crt +TLS_CIPHER_SUITE HIGH:MEDIUM:+SSLv3 + + A password for the server will need to be created as the + default is extremely poor as is normal in this industry. To + do this, issue the following command, sending the output to + slapd.conf: + + &prompt.root; slappasswd -h "{SHA}" >> /usr/local/etc/openldap/slapd.conf + + There will be a prompt for entering the password and, + if the process does not fail, a password hash will be added + to the end of slapd.conf. The + slappasswd understands several hashing + formats, refer to the manual page for more information. + + Edit /usr/local/etc/openldap/slapd.conf + and add the following lines: + + password-hash {sha} +allow bind_v2 + + In addition, the in this file must + be updated to match the from the previous + configuration. The option should + also be set. A good recommendation is something like + . Before saving this file, place + the option in front of the password + output from the slappasswd and delete the + old option above. The end result + should look similar to this: + + TLSCipherSuite HIGH:MEDIUM:+SSLv3 +TLSCertificateFile /usr/local/etc/openldap/server.crt +TLSCertificateKeyFile /usr/local/etc/openldap/private/server.key +TLSCACertificateFile /usr/local/etc/openldap/ca.crt +rootpw {SHA}W6ph5Mm5Pz8GgiULbPgzG37mj9g= + + Finally, enable the OpenLDAP + service in rc.conf. At this time, + setting up a URI and providing the group + and user to run as may be useful. + Edit /etc/rc.conf and add the following + lines: + + slapd_enable="YES" +slapd_flags="-4 -h ldaps:///" + + At this point the server should be ready to be brought + up and tested. To perform this task, issue the following + command: + + &prompt.root; service slapd start + + If everything was configured correctly, a search of the + directory should show a successful connection with a single + response as in this example: + + &prompt.root; ldapsearch -Z + + # extended LDIF +# +# LDAPv3 +# base <dc=example,dc=com> (default) with scope subtree +# filter: (objectclass=*) +# requesting: ALL +# + +# search result +search: 3 +result: 32 No such object + +# numResponses: 1 + + Considering the service should now be responding, as it + is above, the directory may be populated using the + ldapadd command. In this example, there + is a file containing a list of users to be added to this + particular directory. First, create a file to be imported + with the following dataset: + + dn: dc=example,dc=com +objectclass: dcObject +objectclass: organization +o: Example +dc: Example + +dn: cn=Manager,dc=example,dc=com +objectclass: organizationalRole +cn: Manager + + + To debug any of the following, stop the + slapd service using the + service command and start it using with + debugging options. To accomplish this, issue the following + command: + + &prompt.root; /usr/local/libexec/slapd -d -1 + + + To import this datafile, issue the following command, + assuming the file is import.ldif: + + &prompt.root; ldapadd -Z -D "cn=Manager,dc=example,dc=com" -W -f import.ldif + + There will be a request for the password specified earlier, + and the output should look like this: + + Enter LDAP Password: +adding new entry "dc=example,dc=com" + +adding new entry "cn=Manager,dc=example,dc=com" + + Verify the data was added by issuing a search on the + server using ldapsearch. In this case + the output should look like this: + + &prompt.user; ldapsearch -Z + + # extended LDIF +# +# LDAPv3 +# base <dc=example,dc=com> (default) with scope subtree +# filter: (objectclass=*) +# requesting: ALL +# + +# example.com +dn: dc=example,dc=com +objectClass: dcObject +objectClass: organization +o: Example +dc: Example + +# Manager, example.com +dn: cn=Manager,dc=example,dc=com +objectClass: organizationalRole +cn: Manager + +# search result +search: 3 +result: 0 Success + +# numResponses: 3 +# numEntries: 2 + + It is of course advisable to read about the structure of + LDAP directories and the various manual + pages mentioned in this section. At this point, the server + should be configured and functioning properly. + + + From owner-svn-doc-projects@FreeBSD.ORG Sat Jun 1 01:45:52 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2FAA3460; Sat, 1 Jun 2013 01:45:52 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 2111C77C; Sat, 1 Jun 2013 01:45:52 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r511jqf5062763; Sat, 1 Jun 2013 01:45:52 GMT (envelope-from trhodes@svn.freebsd.org) Received: (from trhodes@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r511jpHH062761; Sat, 1 Jun 2013 01:45:51 GMT (envelope-from trhodes@svn.freebsd.org) Message-Id: <201306010145.r511jpHH062761@svn.freebsd.org> From: Tom Rhodes Date: Sat, 1 Jun 2013 01:45:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41806 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jun 2013 01:45:52 -0000 Author: trhodes Date: Sat Jun 1 01:45:51 2013 New Revision: 41806 URL: http://svnweb.freebsd.org/changeset/doc/41806 Log: I have no clue how an "svn diff > file; svn revert chapter.xml; aspell -c file; patch chapter.xml < file" caused two sections, but kill the bad one. *sigh* Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat Jun 1 01:32:07 2013 (r41805) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Sat Jun 1 01:45:51 2013 (r41806) @@ -2606,284 +2606,6 @@ nis_client_flags="-S NIS do - - - - - Tom - Rhodes - Written by - - - - &os; and <acronym>LDAP</acronym> - - LDAP - - LDAP, the Lightweight Directory Access - Protocol, is an application layer protocol used to access, - modify, and authenticate (bind) using a distributed directory - information service. Think of it as a phone or record book which - stores several levels of hierarchical, homogeneous information. - It is often used in networks where users often need access to - several levels of internal information utilizing a single - account. For example, email authentication, pulling employee - contact information, and internal website authentication might - all make use of a single user in the LDAP - server's record base. - - This section will not provide a history or the implementation - details of the protocol. These sections were authored to get an - LDAP server and/or client configured both - quickly and securely; however, any information base requires - planning and this is no exception. - - Planning should include what type of information will be - stored, what that information will be used for, whom should - have access to said information, and how to secure this - information from prying eyes. - - - <acronym>LDAP</acronym> Terminology and Structure - - Before continuing, several parts of LDAP - must be explained to prevent confusion. And confusion with - this configuration is relatively simple. To begin, all - directory entries consist of a group of - attributes. Each of these attribute sets - contain a name, a unique identifier known as a - DN or distinguished name normally built from - several other attributes such as the RDN. - The RDN or relative distinguished name, is - a more common name for the attribute. Like directories have - absolute and relative paths, consider a DN - as an absolute path and the RDN as the - relative path. - - As an example, an entry might look like the - following: - - &prompt.user; ldapsearch -xb "uid=trhodes,ou=users,o=example.com" - - # extended LDIF -# -# LDAPv3 -# base <uid=trhodes,ou=users,o=example.com> with scope subtree -# filter: (objectclass=*) -# requesting: ALL -# - -# trhodes, users, example.com -dn: uid=trhodes,ou=users,o=example.com -mail: trhodes@example.com -cn: Tom Rhodes -uid: trhodes -telephoneNumber: (xxx) xxx-xxxx - -# search result -search: 2 -result: 0 Success - -# numResponses: 2 -# numEntries: 1 - - In this example, it is very obvious what the various - attributes are; however, the cn attribute - should be noticed. This is the RDN discussed - previously. In addition, there is a unique user id provided - here. It is common practice to have specific uid or uuids for - entries to ease in any future migration. - - - - Configuring an <acronym>LDAP</acronym> Server - - LDAP Server - - To configure &os; to act as an LDAP - server, the OpenLDAP port needs installed. This may be - accomplished using the pkg_add command - or by installing the - net/openldap24-server - port. Building the port is recommended as the administrator - may select a great deal of options at this time and disable - some options. In most cases, the defaults will be fine; - however, this is the time to enable SQL support if - needed. - - A few directories will be required from this point on, - at minimal, a data directory and a directory to store the - certificates in. Create them both with the following - commands: - - &prompt.root; mkdir /var/db/openldap-data - - &prompt.root; mkdir /usr/local/etc/openldap/private - - Copy over the database configuration file: - - &prompt.root; cp /usr/local/etc/openldap/DB_CONFIG.example /var/db/openldap-data/DB_CONFIG - - The next phase is to configure the SSL - certificates. While creating certificates is discussed in - the OpenSSL section in this - book, a certificate authority is needed so a different method - will be used. It is recommended that this section be reviewed - prior to configuring to ensure correct information is entered - during the certificate creation process below. - - The following commands must be executed in the - - /usr/local/etc/openldap/private directory. This - is important as the file permissions will need to be restrictive - and users should not have access to these files directly. To - create the certificates, issues the following commands. - - &prompt.root; openssl req -days 365 -nodes -new -x509 -keyout ca.key -out ../ca.crt - - The entries for these may be completely generic - except for the - Common Name entry. This entry must have - something different than the system hostname. If the entry - is the hostname, it would be like the hostname is attempting - to verify hostname. In cases with a self signed certificate - like this example, just prefix the hostname with - CA for certificate authority. - - The next task is to create a certificate signing request - and a private key. To do this, issue the following - commands: - - &prompt.root; openssl req -days 365 -nodes -new -keyout server.key -out server.csr - - During the certificate generation process, be sure to - correctly set the common name attribute. After this has - been completed, the key will need signed: - - &prompt.root; openssl x509 -req -days 365 -in server.csr -out ../server.crt -CA ../ca.crt -CAkey ca.key -CAcreateserial - - The final part of the certificate generation process - is to generate and sign the client certificates: - - &prompt.root; openssl req -days 365 -nodes -new -keyout client.key -out client.csr - - &prompt.root; openssl x509 -req -days 3650 -in client.csr -out ../client.crt -CA ../ca.crt -CAkey ca.key - - Remember, again, to respect the common name attribute. This - is a common cause for confusion during the first attempt to - configure LDAP. In addition, ensure that - a total of eight (8) new files have been generated through - the proceeding commands. If so, the next step is to edit - /usr/local/etc/openldap/slapd.conf and add - the following options: - - TLSCipherSuite HIGH:MEDIUM:+SSLv3 -TLSCertificateFile /usr/local/etc/openldap/server.crt -TLSCertificateKeyFile /usr/local/etc/openldap/private/server.key -TLSCACertificateFile /usr/local/etc/openldap/ca.crt - - In addition, edit - /usr/local/etc/openldap/ldap.conf and - add the following lines: - - TLS_CACERT /usr/local/etc/openldap/ca.crt -TLS_CIPHER_SUITE HIGH:MEDIUM:+SSLv3 - - While editing these this file, set the - to the desired values, and uncomment all three of the - , and - options. In addition, set the - to contain - and . - - The resulting file should look similar to the following - shown here: - - BASE dc=example,dc=com -URI ldap:// ldaps:// - -SIZELIMIT 12 -TIMELIMIT 15 -#DEREF never - -TLS_CACERT /usr/local/etc/openldap/ca.crt -TLS_CIPHER_SUITE HIGH:MEDIUM:+SSLv3 - - A password for the server will need to be created as the - default is extremely poor as is normal in this industry. To - do this, issue the following command, sending the output to - slapd.conf: - - &prompt.root; slappasswd -h "{SHA}" >> /usr/local/etc/openldap/slapd.conf - - There will be a prompt for entering the password and, - if the process does not fail, a password hash will be added - to the end of slapd.conf. The - slappasswd understands several hashing - formats, refer to the manual page for more information. - - Edit /usr/local/etc/openldap/slapd.conf - and add the following lines: - - password-hash {sha} -allow bind_v2 - - In addition, the in this file must - be updated to match the from the previous - configuration. The option should - also be set. A good recommendation is something like - . Before saving this file, place - the option in front of the password - output from the slappasswd and delete the - old option above. The end result - should look similar to this: - - TLSCipherSuite HIGH:MEDIUM:+SSLv3 -TLSCertificateFile /usr/local/etc/openldap/server.crt -TLSCertificateKeyFile /usr/local/etc/openldap/private/server.key -TLSCACertificateFile /usr/local/etc/openldap/ca.crt -rootpw {SHA}W6ph5Mm5Pz8GgiULbPgzG37mj9g= - - Finally, enable the OpenLDAP - service in rc.conf. At this time, - setting up a URI and providing the group - and user to run as may be useful. - Edit /etc/rc.conf and add the following - lines: - - slapd_enable="YES" -slapd_flags="-4 -h ldaps:///" - - At this point the server should be ready to be brought - up and tested. To perform this task, issue the following - command: - - &prompt.root; service slapd start - - If everything was configured correctly, a search of the - directory should show a successful connection with a single - response as in this example: - - &prompt.root; ldapsearch -Z - - # extended LDIF -# -# LDAPv3 -# base <dc=example,dc=com> (default) with scope subtree -# filter: (objectclass=*) -# requesting: ALL -# - -# search result -search: 3 -result: 32 No such object - -# numResponses: 1 - - - - - @@ -2895,7 +2617,7 @@ result: 32 No such object &os; and <acronym>LDAP</acronym> - + LDAP LDAP, the Lightweight Directory Access