aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--da_DK.ISO8859-1/articles/Makefile.inc2
-rw-r--r--da_DK.ISO8859-1/share/sgml/catalog2
-rw-r--r--da_DK.ISO8859-1/share/sgml/disclaimer.sgml20
-rw-r--r--da_DK.ISO8859-1/share/sgml/freebsd.dsl8
-rw-r--r--de_DE.ISO8859-1/articles/contributing-ports/article.sgml2
-rw-r--r--de_DE.ISO8859-1/articles/contributing/article.sgml8
-rw-r--r--de_DE.ISO8859-1/articles/solid-state/Makefile2
-rw-r--r--de_DE.ISO8859-1/books/developers-handbook/book.sgml4
-rw-r--r--de_DE.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml6
-rw-r--r--de_DE.ISO8859-1/books/developers-handbook/policies/chapter.sgml76
-rw-r--r--de_DE.ISO8859-1/books/developers-handbook/secure/chapter.sgml14
-rw-r--r--de_DE.ISO8859-1/books/developers-handbook/tools/chapter.sgml18
-rw-r--r--de_DE.ISO8859-1/books/handbook/bsdinstall/chapter.sgml40
-rw-r--r--de_DE.ISO8859-1/books/handbook/config/chapter.sgml2
-rw-r--r--de_DE.ISO8859-1/books/handbook/desktop/chapter.sgml40
-rw-r--r--de_DE.ISO8859-1/books/handbook/disks/chapter.sgml2
-rw-r--r--de_DE.ISO8859-1/books/handbook/dtrace/chapter.sgml4
-rw-r--r--de_DE.ISO8859-1/books/handbook/eresources/chapter.sgml4
-rw-r--r--de_DE.ISO8859-1/books/handbook/mac/chapter.sgml206
-rw-r--r--de_DE.ISO8859-1/books/handbook/multimedia/chapter.sgml14
-rw-r--r--de_DE.ISO8859-1/books/handbook/network-servers/chapter.sgml100
-rw-r--r--de_DE.ISO8859-1/books/handbook/preface/preface.sgml2
-rw-r--r--de_DE.ISO8859-1/books/handbook/txtfiles.ent8
-rw-r--r--de_DE.ISO8859-1/books/handbook/users/chapter.sgml6
-rw-r--r--de_DE.ISO8859-1/htdocs/availability.sgml2
-rw-r--r--de_DE.ISO8859-1/htdocs/news/2004/news.xml24
-rw-r--r--de_DE.ISO8859-1/htdocs/news/2004/press.xml2
-rw-r--r--de_DE.ISO8859-1/htdocs/news/2005/news.xml50
-rw-r--r--de_DE.ISO8859-1/htdocs/news/2005/press.xml18
-rw-r--r--de_DE.ISO8859-1/htdocs/news/2006/news.xml6
-rw-r--r--de_DE.ISO8859-1/htdocs/news/2006/press.xml2
-rw-r--r--de_DE.ISO8859-1/htdocs/news/2008/news.xml10
-rw-r--r--de_DE.ISO8859-1/htdocs/news/2009/news.xml44
-rw-r--r--de_DE.ISO8859-1/htdocs/platforms/x86-64.sgml2
-rw-r--r--de_DE.ISO8859-1/htdocs/projects/Makefile2
-rw-r--r--de_DE.ISO8859-1/share/sgml/catalog2
-rw-r--r--de_DE.ISO8859-1/share/sgml/freebsd.dsl6
-rw-r--r--de_DE.ISO8859-1/share/sgml/news.xml100
-rw-r--r--de_DE.ISO8859-1/share/sgml/trademarks.ent20
-rw-r--r--el_GR.ISO8859-7/articles/compiz-fusion/article.sgml6
-rw-r--r--el_GR.ISO8859-7/articles/dialup-firewall/article.sgml2
-rw-r--r--el_GR.ISO8859-7/articles/formatting-media/article.sgml38
-rw-r--r--el_GR.ISO8859-7/articles/gjournal-desktop/Makefile2
-rw-r--r--el_GR.ISO8859-7/articles/laptop/article.sgml16
-rw-r--r--el_GR.ISO8859-7/articles/new-users/article.sgml8
-rw-r--r--el_GR.ISO8859-7/books/faq/Makefile6
-rw-r--r--el_GR.ISO8859-7/books/faq/book.sgml22
-rw-r--r--el_GR.ISO8859-7/books/handbook/Makefile2
-rw-r--r--el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml10
-rw-r--r--el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml2
-rw-r--r--el_GR.ISO8859-7/books/handbook/disks/chapter.sgml6
-rw-r--r--el_GR.ISO8859-7/books/handbook/eresources/chapter.sgml2
-rw-r--r--el_GR.ISO8859-7/books/handbook/kernelconfig/chapter.sgml8
-rw-r--r--el_GR.ISO8859-7/books/handbook/linuxemu/chapter.sgml4
-rw-r--r--el_GR.ISO8859-7/books/handbook/mac/chapter.sgml6
-rw-r--r--el_GR.ISO8859-7/books/handbook/multimedia/chapter.sgml24
-rw-r--r--el_GR.ISO8859-7/books/handbook/network-servers/chapter.sgml2
-rw-r--r--el_GR.ISO8859-7/books/handbook/security/chapter.sgml444
-rw-r--r--el_GR.ISO8859-7/htdocs/doc/Makefile2
-rw-r--r--el_GR.ISO8859-7/share/sgml/freebsd.dsl4
-rw-r--r--el_GR.ISO8859-7/share/sgml/navibar.l10n.ent4
-rw-r--r--en_US.ISO8859-1/articles/5-roadmap/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/Makefile.inc2
-rw-r--r--en_US.ISO8859-1/articles/bsdl-gpl/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/casestudy-argentina.com/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/committers-guide/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/compiz-fusion/article.sgml4
-rw-r--r--en_US.ISO8859-1/articles/console-server/article.sgml34
-rw-r--r--en_US.ISO8859-1/articles/contributing/article.sgml2
-rw-r--r--en_US.ISO8859-1/articles/contributors/contrib.additional.sgml6
-rw-r--r--en_US.ISO8859-1/articles/contributors/contrib.committers.sgml2
-rw-r--r--en_US.ISO8859-1/articles/custom-gcc/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/cvsup-advanced/article.sgml84
-rw-r--r--en_US.ISO8859-1/articles/dialup-firewall/article.sgml4
-rw-r--r--en_US.ISO8859-1/articles/diskless-x/article.sgml44
-rw-r--r--en_US.ISO8859-1/articles/euro/article.sgml66
-rw-r--r--en_US.ISO8859-1/articles/explaining-bsd/article.sgml6
-rw-r--r--en_US.ISO8859-1/articles/fonts/article.sgml8
-rw-r--r--en_US.ISO8859-1/articles/formatting-media/article.sgml46
-rw-r--r--en_US.ISO8859-1/articles/freebsd-questions/article.sgml50
-rw-r--r--en_US.ISO8859-1/articles/geom-class/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/gjournal-desktop/article.sgml22
-rw-r--r--en_US.ISO8859-1/articles/hubs/article.sgml2
-rw-r--r--en_US.ISO8859-1/articles/laptop/article.sgml52
-rw-r--r--en_US.ISO8859-1/articles/ldap-auth/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/ldap-auth/article.sgml8
-rw-r--r--en_US.ISO8859-1/articles/linux-comparison/article.sgml2
-rw-r--r--en_US.ISO8859-1/articles/linux-emulation/article.sgml82
-rw-r--r--en_US.ISO8859-1/articles/linux-users/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/mailing-list-faq/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/mh/article.sgml24
-rw-r--r--en_US.ISO8859-1/articles/nanobsd/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/new-users/article.sgml2
-rw-r--r--en_US.ISO8859-1/articles/p4-primer/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/portbuild/article.sgml4
-rw-r--r--en_US.ISO8859-1/articles/problem-reports/article.sgml4
-rw-r--r--en_US.ISO8859-1/articles/rc-scripting/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/rc-scripting/article.sgml2
-rw-r--r--en_US.ISO8859-1/articles/relaydelay/article.sgml2
-rw-r--r--en_US.ISO8859-1/articles/releng-packages/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/releng/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/releng/article.sgml6
-rw-r--r--en_US.ISO8859-1/articles/remote-install/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/serial-uart/article.sgml556
-rw-r--r--en_US.ISO8859-1/articles/solid-state/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/solid-state/article.sgml14
-rw-r--r--en_US.ISO8859-1/articles/storage-devices/article.sgml884
-rw-r--r--en_US.ISO8859-1/articles/version-guide/Makefile2
-rw-r--r--en_US.ISO8859-1/articles/version-guide/article.sgml8
-rw-r--r--en_US.ISO8859-1/articles/vinum/article.sgml20
-rw-r--r--en_US.ISO8859-1/articles/vm-design/article.sgml12
-rw-r--r--en_US.ISO8859-1/articles/wp-toolbox/Makefile2
-rw-r--r--en_US.ISO8859-1/books/Makefile.inc2
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/Makefile4
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/book.sgml12
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/chapters.ent6
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.sgml14
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/isa/chapter.sgml14
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/jail/chapter.sgml22
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/locking/chapter.sgml18
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/mac/chapter.sgml1672
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/scsi/chapter.sgml96
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/sound/chapter.sgml44
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.sgml2
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/usb/chapter.sgml10
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/vm/chapter.sgml18
-rw-r--r--en_US.ISO8859-1/books/bibliography/Makefile4
-rw-r--r--en_US.ISO8859-1/books/bibliography/book.sgml8
-rw-r--r--en_US.ISO8859-1/books/corp-net-guide/book.sgml76
-rw-r--r--en_US.ISO8859-1/books/design-44bsd/book.sgml314
-rw-r--r--en_US.ISO8859-1/books/dev-model/book.sgml14
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/Makefile4
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/book.sgml16
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/chapters.ent6
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml12
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml8
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml58
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml38
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml66
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml8
-rw-r--r--en_US.ISO8859-1/books/faq/Makefile6
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/Makefile26
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/chapters.ent12
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml6
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml14
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml2
-rw-r--r--en_US.ISO8859-1/books/handbook/Makefile8
-rw-r--r--en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml10
-rw-r--r--en_US.ISO8859-1/books/handbook/basics/chapter.sgml212
-rw-r--r--en_US.ISO8859-1/books/handbook/book.sgml2
-rw-r--r--en_US.ISO8859-1/books/handbook/chapters.ent6
-rw-r--r--en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml14
-rw-r--r--en_US.ISO8859-1/books/handbook/jails/chapter.sgml4
-rw-r--r--en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml12
-rw-r--r--en_US.ISO8859-1/books/handbook/l10n/chapter.sgml18
-rw-r--r--en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml4
-rw-r--r--en_US.ISO8859-1/books/handbook/mac/chapter.sgml6
-rw-r--r--en_US.ISO8859-1/books/handbook/mail/chapter.sgml4
-rw-r--r--en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml256
-rw-r--r--en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml24
-rw-r--r--en_US.ISO8859-1/books/handbook/ports/chapter.sgml2
-rw-r--r--en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml78
-rw-r--r--en_US.ISO8859-1/books/handbook/preface/preface.sgml6
-rw-r--r--en_US.ISO8859-1/books/handbook/txtfiles.ent8
-rw-r--r--en_US.ISO8859-1/books/handbook/users/chapter.sgml26
-rw-r--r--en_US.ISO8859-1/books/handbook/vinum/chapter.sgml58
-rw-r--r--en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml6
-rw-r--r--en_US.ISO8859-1/books/handbook/x11/chapter.sgml8
-rw-r--r--en_US.ISO8859-1/books/porters-handbook/Makefile4
-rw-r--r--en_US.ISO8859-1/htdocs/FAQ/Makefile2
-rw-r--r--en_US.ISO8859-1/htdocs/applications.sgml16
-rw-r--r--en_US.ISO8859-1/htdocs/art.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/availability.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/copyright/daemon.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.sgml20
-rw-r--r--en_US.ISO8859-1/htdocs/developers/Makefile2
-rw-r--r--en_US.ISO8859-1/htdocs/docproj/Makefile4
-rw-r--r--en_US.ISO8859-1/htdocs/docproj/current.sgml32
-rw-r--r--en_US.ISO8859-1/htdocs/docproj/doc-set.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/docproj/docproj.sgml12
-rw-r--r--en_US.ISO8859-1/htdocs/docproj/sgml.sgml26
-rw-r--r--en_US.ISO8859-1/htdocs/docproj/submitting.sgml18
-rw-r--r--en_US.ISO8859-1/htdocs/docproj/translations.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/docproj/who.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/donations/donors.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/events/2002/bsdcon-devsummit.sgml114
-rw-r--r--en_US.ISO8859-1/htdocs/events/2002/usenix-devsummit.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/features.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/gifs/Makefile12
-rw-r--r--en_US.ISO8859-1/htdocs/gnome/docs/faq210.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/gnome/docs/faq224.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/gnome/docs/faq230.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/gnome/docs/faq232.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/gnome/news.xml22
-rw-r--r--en_US.ISO8859-1/htdocs/handbook/Makefile2
-rw-r--r--en_US.ISO8859-1/htdocs/internal/Makefile4
-rw-r--r--en_US.ISO8859-1/htdocs/internal/machines.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/internal/mirror.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/internal/new-account.sgml16
-rw-r--r--en_US.ISO8859-1/htdocs/internal/statistic.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/internet.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/ipv6/index.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/ipv6/ipv6.ent6
-rw-r--r--en_US.ISO8859-1/htdocs/ipv6/ipv6only.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/ipv6/w6d-www-stats.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/ipv6/w6d.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/ipv6/w6l.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/java/advocacy.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/java/dists/12.sgml18
-rw-r--r--en_US.ISO8859-1/htdocs/java/dists/13.sgml30
-rw-r--r--en_US.ISO8859-1/htdocs/java/dists/14.sgml14
-rw-r--r--en_US.ISO8859-1/htdocs/java/docs/faq.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/java/docs/performance.sgml18
-rw-r--r--en_US.ISO8859-1/htdocs/java/java-rss.xsl2
-rw-r--r--en_US.ISO8859-1/htdocs/java/links/Makefile4
-rw-r--r--en_US.ISO8859-1/htdocs/java/links/api.sgml20
-rw-r--r--en_US.ISO8859-1/htdocs/java/links/development.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/java/links/freebsd.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/java/links/vendor.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/kse/index.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/layout/images/Makefile2
-rw-r--r--en_US.ISO8859-1/htdocs/mailto.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/marketing/index.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/multimedia/multimedia-input.xml66
-rw-r--r--en_US.ISO8859-1/htdocs/news/1996/index.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/news/1997/index.sgml22
-rw-r--r--en_US.ISO8859-1/htdocs/news/1998/index.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/news/1999/index.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/news/2000/index.sgml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/2001/news.xml164
-rw-r--r--en_US.ISO8859-1/htdocs/news/2002/news.xml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/2003/news.xml10
-rw-r--r--en_US.ISO8859-1/htdocs/news/2004/news.xml26
-rw-r--r--en_US.ISO8859-1/htdocs/news/2005/news.xml14
-rw-r--r--en_US.ISO8859-1/htdocs/news/2006/news.xml18
-rw-r--r--en_US.ISO8859-1/htdocs/news/2007/news.xml10
-rw-r--r--en_US.ISO8859-1/htdocs/news/2007/press.xml4
-rw-r--r--en_US.ISO8859-1/htdocs/news/2009/news.xml2
-rw-r--r--en_US.ISO8859-1/htdocs/news/2009/press.xml4
-rw-r--r--en_US.ISO8859-1/htdocs/news/press-rel-2.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/news/press-rel-3.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/news/press-rel-5.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/news/press-rel-6.sgml98
-rw-r--r--en_US.ISO8859-1/htdocs/news/pressreleases.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/news/sou1999.sgml18
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml2
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml2
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml4
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml22
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml20
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml10
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml78
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml12
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml8
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml4
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml22
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml26
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml492
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml118
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml284
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml232
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml102
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml56
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml32
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml52
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml20
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml50
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml30
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml90
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml28
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml18
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml12
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml10
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml12
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml32
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml4
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml24
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml12
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml2
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/report.xsl6
-rw-r--r--en_US.ISO8859-1/htdocs/news/status/status.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/platforms/alpha.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/platforms/arm.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/platforms/mips.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/platforms/pc98.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/platforms/ppc.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/platforms/x86-64.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/portmgr/charter.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/portmgr/index.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/portmgr/policies.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/portmgr/policies_contributors.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/portmgr/qa.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/ports/Makefile.inc2
-rw-r--r--en_US.ISO8859-1/htdocs/projects/acpi/index.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/projects/busdma/index.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/projects/c99/index.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/projects/cvsweb.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml14
-rw-r--r--en_US.ISO8859-1/htdocs/projects/newbies.sgml32
-rw-r--r--en_US.ISO8859-1/htdocs/projects/summerofcode-2007.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/projects/summerofcode-2008.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/projects/summerofcode.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/publish.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.0.5R/notes.sgml14
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.0/install.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.0/notes.sgml12
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.1.5R/notes.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.1.6R/announce.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.1.6R/notes.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.1.6R/security.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.1.7R/notes.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.1R/notes.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.1R/notes.sgml14
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.2R/notes.sgml14
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.5R/errata.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.5R/notes.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.6R/errata.sgml24
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.6R/notes.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.7R/errata.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.7R/notes.sgml44
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.8R/errata.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2.8R/notes.sgml44
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2R/announce.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/releases/2.2R/notes.sgml16
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.0R/errata.sgml12
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.0R/notes.sgml16
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.1R/errata.sgml12
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.1R/notes.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.2R/errata.sgml18
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.2R/notes.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.3R/errata.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.3R/notes.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.4R/announce.sgml18
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.4R/errata.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.4R/notes.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.5R/announce.sgml18
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.5R/errata.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/3.5R/notes.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.0R/announce.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.0R/errata.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.0R/notes.sgml32
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.1.1R/errata.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.1.1R/notes.sgml32
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.1R/errata.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.1R/notes.sgml26
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.2R/errata.sgml6
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.2R/notes.sgml34
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.3R/errata.sgml10
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.5R/qa.sgml12
-rw-r--r--en_US.ISO8859-1/htdocs/releases/4.5R/schedule.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/5.5R/todo.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/6.0R/stress.xsl2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/6.0R/todo.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/6.1R/stress.xsl2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/6.2R/announce.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/6.2R/stress.xsl2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/6.3R/announce.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/releases/7.0R/announce.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/releases/7.0R/stress.xsl2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/7.1R/announce.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releases/7.4R/announce.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/releng/charter.sgml14
-rw-r--r--en_US.ISO8859-1/htdocs/relnotes.sgml8
-rw-r--r--en_US.ISO8859-1/htdocs/search/Makefile2
-rw-r--r--en_US.ISO8859-1/htdocs/search/opensearch/Makefile4
-rw-r--r--en_US.ISO8859-1/htdocs/search/search.sgml106
-rw-r--r--en_US.ISO8859-1/htdocs/smp/index.sgml4
-rw-r--r--en_US.ISO8859-1/htdocs/support/Makefile2
-rw-r--r--en_US.ISO8859-1/htdocs/support/bugreports.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/tutorials/index.sgml2
-rw-r--r--en_US.ISO8859-1/htdocs/y2kbug.sgml70
-rw-r--r--en_US.ISO8859-1/share/sgml/catalog2
-rw-r--r--en_US.ISO8859-1/share/sgml/freebsd.dsl4
-rw-r--r--en_US.ISO8859-1/share/sgml/glossary.ent6
-rw-r--r--en_US.ISO8859-1/slides/20050513-bsdcan-slides/slides.xml2
-rw-r--r--en_US.ISO8859-1/slides/freebsd-general/slides.xml2
-rw-r--r--es_ES.ISO8859-1/articles/Makefile.inc2
-rw-r--r--es_ES.ISO8859-1/articles/casestudy-argentina.com/Makefile4
-rw-r--r--es_ES.ISO8859-1/articles/casestudy-argentina.com/article.sgml226
-rw-r--r--es_ES.ISO8859-1/articles/contributing/Makefile2
-rw-r--r--es_ES.ISO8859-1/articles/contributing/article.sgml666
-rw-r--r--es_ES.ISO8859-1/articles/cvs-freebsd/article.sgml290
-rw-r--r--es_ES.ISO8859-1/articles/dialup-firewall/article.sgml364
-rw-r--r--es_ES.ISO8859-1/articles/euro/article.sgml78
-rw-r--r--es_ES.ISO8859-1/articles/explaining-bsd/Makefile8
-rw-r--r--es_ES.ISO8859-1/articles/explaining-bsd/article.sgml748
-rw-r--r--es_ES.ISO8859-1/articles/fbsd-from-scratch/Makefile2
-rw-r--r--es_ES.ISO8859-1/articles/fbsd-from-scratch/article.sgml686
-rw-r--r--es_ES.ISO8859-1/articles/fdp-es/article.sgml6
-rw-r--r--es_ES.ISO8859-1/articles/laptop/article.sgml504
-rw-r--r--es_ES.ISO8859-1/articles/linux-comparison/article.sgml446
-rw-r--r--es_ES.ISO8859-1/articles/linux-users/Makefile2
-rw-r--r--es_ES.ISO8859-1/articles/linux-users/article.sgml26
-rw-r--r--es_ES.ISO8859-1/articles/mailing-list-faq/Makefile2
-rw-r--r--es_ES.ISO8859-1/articles/mailing-list-faq/article.sgml256
-rw-r--r--es_ES.ISO8859-1/articles/nanobsd/Makefile2
-rw-r--r--es_ES.ISO8859-1/articles/nanobsd/article.sgml26
-rw-r--r--es_ES.ISO8859-1/articles/p4-primer/Makefile2
-rw-r--r--es_ES.ISO8859-1/articles/p4-primer/article.sgml614
-rw-r--r--es_ES.ISO8859-1/articles/problem-reports/article.sgml384
-rw-r--r--es_ES.ISO8859-1/articles/pxe/article.sgml10
-rw-r--r--es_ES.ISO8859-1/articles/releng/Makefile2
-rw-r--r--es_ES.ISO8859-1/articles/releng/article.sgml170
-rw-r--r--es_ES.ISO8859-1/articles/version-guide/Makefile2
-rw-r--r--es_ES.ISO8859-1/articles/version-guide/article.sgml282
-rw-r--r--es_ES.ISO8859-1/articles/zip-drive/article.sgml348
-rw-r--r--es_ES.ISO8859-1/books/Makefile.inc2
-rw-r--r--es_ES.ISO8859-1/books/faq/Makefile6
-rw-r--r--es_ES.ISO8859-1/books/faq/book.sgml4090
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/Makefile10
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/advanced-networking/chapter.sgml7940
-rw-r--r--es_ES.ISO8859-1/books/handbook/audit/chapter.sgml2
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/backups/chapter.sgml616
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/basics/chapter.sgml470
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/bibliography/chapter.sgml202
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/book.sgml12
-rw-r--r--es_ES.ISO8859-1/books/handbook/boot/chapter.sgml144
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/chapters.ent6
-rw-r--r--es_ES.ISO8859-1/books/handbook/colophon.sgml4
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/cutting-edge/chapter.sgml8
-rw-r--r--es_ES.ISO8859-1/books/handbook/desktop/chapter.sgml42
-rw-r--r--es_ES.ISO8859-1/books/handbook/disks/chapter.sgml3232
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/eresources/chapter.sgml660
-rw-r--r--es_ES.ISO8859-1/books/handbook/firewalls/chapter.sgml4
-rw-r--r--es_ES.ISO8859-1/books/handbook/geom/chapter.sgml6
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/install/chapter.sgml772
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/introduction/chapter.sgml112
-rw-r--r--es_ES.ISO8859-1/books/handbook/jails/chapter.sgml10
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/kernelconfig/chapter.sgml80
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/l10n/chapter.sgml136
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/linuxemu/chapter.sgml260
-rw-r--r--es_ES.ISO8859-1/books/handbook/mac/chapter.sgml4
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/mail/chapter.sgml2128
-rw-r--r--es_ES.ISO8859-1/books/handbook/multimedia/chapter.sgml72
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/pgpkeys/chapter.sgml76
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/policies/chapter.sgml212
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/ports/chapter.sgml118
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml454
-rw-r--r--es_ES.ISO8859-1/books/handbook/preface/preface.sgml14
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/printing/chapter.sgml8
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/quotas/chapter.sgml280
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/security/chapter.sgml5732
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/serialcomms/chapter.sgml740
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/staff/chapter.sgml380
-rw-r--r--es_ES.ISO8859-1/books/handbook/txtfiles.ent10
-rw-r--r--es_ES.ISO8859-1/books/handbook/updating/chapter.sgml16
-rw-r--r--es_ES.ISO8859-1/books/handbook/users/chapter.sgml40
-rw-r--r--es_ES.ISO8859-1/books/handbook/vinum/chapter.sgml36
-rw-r--r--es_ES.ISO8859-1/books/handbook/virtualization/chapter.sgml6
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/x11/chapter.sgml98
-rw-r--r--es_ES.ISO8859-1/htdocs/about.sgml58
-rw-r--r--es_ES.ISO8859-1/htdocs/availability.sgml2
-rw-r--r--es_ES.ISO8859-1/htdocs/docproj/Makefile4
-rw-r--r--es_ES.ISO8859-1/htdocs/index.xsl10
-rw-r--r--es_ES.ISO8859-1/htdocs/internal/Makefile4
-rw-r--r--es_ES.ISO8859-1/htdocs/internet.sgml4
-rw-r--r--es_ES.ISO8859-1/htdocs/mailto.sgml6
-rw-r--r--es_ES.ISO8859-1/htdocs/platforms/alpha.sgml2
-rw-r--r--es_ES.ISO8859-1/htdocs/platforms/amd64.sgml2
-rw-r--r--es_ES.ISO8859-1/htdocs/platforms/arm.sgml8
-rw-r--r--es_ES.ISO8859-1/htdocs/platforms/ia64/index.sgml4
-rw-r--r--es_ES.ISO8859-1/htdocs/platforms/mips.sgml4
-rw-r--r--es_ES.ISO8859-1/htdocs/platforms/sun4v.sgml4
-rw-r--r--es_ES.ISO8859-1/htdocs/platforms/xbox.sgml2
-rw-r--r--es_ES.ISO8859-1/htdocs/search/Makefile2
-rw-r--r--es_ES.ISO8859-1/htdocs/search/search-mid.sgml2
-rw-r--r--es_ES.ISO8859-1/htdocs/send-pr.sgml2
-rw-r--r--es_ES.ISO8859-1/htdocs/support.sgml8
-rw-r--r--es_ES.ISO8859-1/share/sgml/catalog2
-rw-r--r--es_ES.ISO8859-1/share/sgml/es-mailing-lists.ent2
-rw-r--r--es_ES.ISO8859-1/share/sgml/freebsd.dsl8
-rw-r--r--es_ES.ISO8859-1/share/sgml/glossary.ent48
-rw-r--r--es_ES.ISO8859-1/share/sgml/navibar.l10n.ent4
-rw-r--r--es_ES.ISO8859-1/share/sgml/trademarks.ent20
-rw-r--r--fr_FR.ISO8859-1/articles/committers-guide/article.sgml122
-rw-r--r--fr_FR.ISO8859-1/articles/contributing-ports/article.sgml2
-rw-r--r--fr_FR.ISO8859-1/articles/contributing/article.sgml4
-rw-r--r--fr_FR.ISO8859-1/articles/contributors/article.sgml144
-rw-r--r--fr_FR.ISO8859-1/articles/cvsup-advanced/Makefile2
-rw-r--r--fr_FR.ISO8859-1/articles/cvsup-advanced/article.sgml178
-rw-r--r--fr_FR.ISO8859-1/articles/dialup-firewall/article.sgml54
-rw-r--r--fr_FR.ISO8859-1/articles/diskless-x/article.sgml44
-rw-r--r--fr_FR.ISO8859-1/articles/euro/article.sgml42
-rw-r--r--fr_FR.ISO8859-1/articles/filtering-bridges/article.sgml274
-rwxr-xr-xfr_FR.ISO8859-1/articles/fonts/article.sgml238
-rwxr-xr-xfr_FR.ISO8859-1/articles/formatting-media/article.sgml146
-rwxr-xr-xfr_FR.ISO8859-1/articles/ip-aliasing/article.sgml82
-rw-r--r--fr_FR.ISO8859-1/articles/ipsec-must/article.sgml86
-rw-r--r--fr_FR.ISO8859-1/articles/java-tomcat/article.sgml184
-rw-r--r--fr_FR.ISO8859-1/articles/laptop/article.sgml196
-rw-r--r--fr_FR.ISO8859-1/articles/linux-users/Makefile2
-rwxr-xr-xfr_FR.ISO8859-1/articles/make-world/article.sgml446
-rw-r--r--fr_FR.ISO8859-1/articles/mh/article.sgml160
-rwxr-xr-xfr_FR.ISO8859-1/articles/multi-os/article.sgml244
-rw-r--r--fr_FR.ISO8859-1/articles/nanobsd/Makefile2
-rwxr-xr-xfr_FR.ISO8859-1/articles/new-users/article.sgml190
-rw-r--r--fr_FR.ISO8859-1/articles/ntfs/article.sgml216
-rwxr-xr-xfr_FR.ISO8859-1/articles/ppp/article.sgml448
-rw-r--r--fr_FR.ISO8859-1/articles/pr-guidelines/article.sgml242
-rw-r--r--fr_FR.ISO8859-1/articles/problem-reports/article.sgml340
-rwxr-xr-xfr_FR.ISO8859-1/articles/programming-tools/article.sgml894
-rw-r--r--fr_FR.ISO8859-1/articles/releng-packages/Makefile2
-rw-r--r--fr_FR.ISO8859-1/articles/releng-packages/article.sgml10
-rw-r--r--fr_FR.ISO8859-1/articles/releng/Makefile2
-rw-r--r--fr_FR.ISO8859-1/articles/zip-drive/article.sgml258
-rw-r--r--fr_FR.ISO8859-1/books/developers-handbook/Makefile6
-rw-r--r--fr_FR.ISO8859-1/books/developers-handbook/chapters.ent4
-rw-r--r--fr_FR.ISO8859-1/books/developers-handbook/locking/chapter.sgml24
-rw-r--r--fr_FR.ISO8859-1/books/developers-handbook/pci/chapter.sgml42
-rw-r--r--fr_FR.ISO8859-1/books/developers-handbook/scsi/chapter.sgml6
-rw-r--r--fr_FR.ISO8859-1/books/developers-handbook/secure/chapter.sgml178
-rw-r--r--fr_FR.ISO8859-1/books/developers-handbook/tools/chapter.sgml272
-rw-r--r--fr_FR.ISO8859-1/books/developers-handbook/usb/chapter.sgml4
-rw-r--r--fr_FR.ISO8859-1/books/faq/Makefile4
-rw-r--r--fr_FR.ISO8859-1/books/faq/book.sgml1694
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/Makefile30
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/book.sgml18
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/chapters.ent12
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/overview/chapter.sgml60
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/psgml-mode/chapter.sgml30
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/see-also/chapter.sgml4
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml456
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml286
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/stylesheets/chapter.sgml8
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/the-faq/chapter.sgml2
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/the-handbook/chapter.sgml32
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/tools/chapter.sgml52
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/translations/chapter.sgml50
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml36
-rw-r--r--fr_FR.ISO8859-1/books/handbook/Makefile2
-rw-r--r--fr_FR.ISO8859-1/books/handbook/advanced-networking/chapter.sgml2
-rw-r--r--fr_FR.ISO8859-1/books/handbook/basics/chapter.sgml2
-rw-r--r--fr_FR.ISO8859-1/books/handbook/book.sgml2
-rw-r--r--fr_FR.ISO8859-1/books/handbook/chapters.ent2
-rw-r--r--fr_FR.ISO8859-1/books/handbook/config/chapter.sgml6
-rwxr-xr-xfr_FR.ISO8859-1/books/handbook/disks/chapter.sgml2
-rw-r--r--fr_FR.ISO8859-1/books/handbook/install/chapter.sgml6
-rw-r--r--fr_FR.ISO8859-1/books/handbook/introduction/chapter.sgml4
-rw-r--r--fr_FR.ISO8859-1/books/handbook/l10n/chapter.sgml2
-rw-r--r--fr_FR.ISO8859-1/books/handbook/mirrors/chapter.sgml6
-rw-r--r--fr_FR.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml6
-rw-r--r--fr_FR.ISO8859-1/books/handbook/serialcomms/chapter.sgml18
-rw-r--r--fr_FR.ISO8859-1/books/handbook/x11/chapter.sgml2
-rw-r--r--fr_FR.ISO8859-1/books/porters-handbook/Makefile4
-rw-r--r--fr_FR.ISO8859-1/books/porters-handbook/book.sgml68
-rw-r--r--fr_FR.ISO8859-1/books/ppp-primer/Makefile8
-rw-r--r--fr_FR.ISO8859-1/books/ppp-primer/book.sgml452
-rw-r--r--fr_FR.ISO8859-1/htdocs/FAQ/Makefile2
-rw-r--r--fr_FR.ISO8859-1/htdocs/Makefile10
-rw-r--r--fr_FR.ISO8859-1/htdocs/applications.sgml6
-rw-r--r--fr_FR.ISO8859-1/htdocs/availability.sgml2
-rw-r--r--fr_FR.ISO8859-1/htdocs/docproj/Makefile4
-rw-r--r--fr_FR.ISO8859-1/htdocs/events/events.css2
-rw-r--r--fr_FR.ISO8859-1/htdocs/features.sgml8
-rw-r--r--fr_FR.ISO8859-1/htdocs/gnome/index.xsl6
-rw-r--r--fr_FR.ISO8859-1/htdocs/gnome/news.xml20
-rw-r--r--fr_FR.ISO8859-1/htdocs/gnome/newsflash.xsl2
-rw-r--r--fr_FR.ISO8859-1/htdocs/gnome/rss.xsl4
-rw-r--r--fr_FR.ISO8859-1/htdocs/handbook/Makefile2
-rw-r--r--fr_FR.ISO8859-1/htdocs/index.xsl4
-rw-r--r--fr_FR.ISO8859-1/htdocs/internal/Makefile6
-rw-r--r--fr_FR.ISO8859-1/htdocs/internet.sgml8
-rw-r--r--fr_FR.ISO8859-1/htdocs/java/index.sgml2
-rw-r--r--fr_FR.ISO8859-1/htdocs/java/links/Makefile4
-rw-r--r--fr_FR.ISO8859-1/htdocs/news/2001/news.xml136
-rw-r--r--fr_FR.ISO8859-1/htdocs/news/2002/news.xml110
-rw-r--r--fr_FR.ISO8859-1/htdocs/news/status/report-july-2002-aug-2002.xml154
-rw-r--r--fr_FR.ISO8859-1/htdocs/news/status/report-sample.xml8
-rw-r--r--fr_FR.ISO8859-1/htdocs/news/status/report.xsl10
-rw-r--r--fr_FR.ISO8859-1/htdocs/platforms/x86-64.sgml2
-rw-r--r--fr_FR.ISO8859-1/htdocs/projects/c99/index.sgml2
-rw-r--r--fr_FR.ISO8859-1/htdocs/projects/mips/index.sgml2
-rw-r--r--fr_FR.ISO8859-1/htdocs/projects/projects.sgml6
-rw-r--r--fr_FR.ISO8859-1/htdocs/relnotes/Makefile2
-rw-r--r--fr_FR.ISO8859-1/htdocs/search/Makefile2
-rw-r--r--fr_FR.ISO8859-1/htdocs/search/search.sgml2
-rw-r--r--fr_FR.ISO8859-1/htdocs/security/mkindex.xsl4
-rw-r--r--fr_FR.ISO8859-1/share/sgml/abstract.ent4
-rw-r--r--fr_FR.ISO8859-1/share/sgml/artheader.ent4
-rw-r--r--fr_FR.ISO8859-1/share/sgml/catalog2
-rw-r--r--fr_FR.ISO8859-1/share/sgml/events.xml30
-rw-r--r--fr_FR.ISO8859-1/share/sgml/freebsd.dsl6
-rw-r--r--fr_FR.ISO8859-1/share/sgml/navibar.l10n.ent4
-rw-r--r--fr_FR.ISO8859-1/share/sgml/news.xml94
-rw-r--r--fr_FR.ISO8859-1/share/sgml/press.xml404
-rw-r--r--fr_FR.ISO8859-1/share/sgml/teams.ent2
-rw-r--r--fr_FR.ISO8859-1/share/sgml/trademarks.ent8
-rw-r--r--fr_FR.ISO8859-1/share/sgml/translators.ent2
-rw-r--r--fr_FR.ISO8859-1/share/sgml/urls.ent4
-rw-r--r--hu_HU.ISO8859-2/Makefile.inc2
-rw-r--r--hu_HU.ISO8859-2/articles/compiz-fusion/article.sgml2
-rw-r--r--hu_HU.ISO8859-2/articles/explaining-bsd/article.sgml12
-rw-r--r--hu_HU.ISO8859-2/articles/gjournal-desktop/article.sgml4
-rw-r--r--hu_HU.ISO8859-2/articles/linux-comparison/article.sgml4
-rw-r--r--hu_HU.ISO8859-2/articles/linux-users/Makefile2
-rw-r--r--hu_HU.ISO8859-2/books/faq/Makefile6
-rw-r--r--hu_HU.ISO8859-2/books/faq/book.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/fdp-primer/Makefile26
-rw-r--r--hu_HU.ISO8859-2/books/fdp-primer/book.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/fdp-primer/chapters.ent12
-rw-r--r--hu_HU.ISO8859-2/books/fdp-primer/sgml-markup/chapter.sgml4
-rw-r--r--hu_HU.ISO8859-2/books/fdp-primer/sgml-primer/chapter.sgml6
-rw-r--r--hu_HU.ISO8859-2/books/fdp-primer/translations/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/Makefile8
-rw-r--r--hu_HU.ISO8859-2/books/handbook/advanced-networking/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/audit/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/basics/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/bibliography/chapter.sgml8
-rw-r--r--hu_HU.ISO8859-2/books/handbook/chapters.ent2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/cutting-edge/chapter.sgml4
-rw-r--r--hu_HU.ISO8859-2/books/handbook/disks/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/geom/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/install/chapter.sgml290
-rw-r--r--hu_HU.ISO8859-2/books/handbook/kernelconfig/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/l10n/chapter.sgml8
-rw-r--r--hu_HU.ISO8859-2/books/handbook/linuxemu/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/mac/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/mirrors/chapter.sgml4
-rw-r--r--hu_HU.ISO8859-2/books/handbook/multimedia/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/ports/chapter.sgml4
-rw-r--r--hu_HU.ISO8859-2/books/handbook/ppp-and-slip/chapter.sgml12
-rw-r--r--hu_HU.ISO8859-2/books/handbook/printing/chapter.sgml12
-rw-r--r--hu_HU.ISO8859-2/books/handbook/security/chapter.sgml2
-rw-r--r--hu_HU.ISO8859-2/books/handbook/txtfiles.ent6
-rw-r--r--hu_HU.ISO8859-2/books/handbook/vinum/chapter.sgml4
-rw-r--r--hu_HU.ISO8859-2/books/handbook/virtualization/chapter.sgml40
-rw-r--r--hu_HU.ISO8859-2/htdocs/about.sgml2
-rw-r--r--hu_HU.ISO8859-2/htdocs/docproj/Makefile2
-rw-r--r--hu_HU.ISO8859-2/htdocs/docproj/sgml.sgml2
-rw-r--r--hu_HU.ISO8859-2/htdocs/platforms/alpha.sgml2
-rw-r--r--hu_HU.ISO8859-2/htdocs/platforms/mips.sgml2
-rw-r--r--hu_HU.ISO8859-2/htdocs/platforms/pc98.sgml2
-rw-r--r--hu_HU.ISO8859-2/htdocs/search/Makefile2
-rw-r--r--hu_HU.ISO8859-2/htdocs/search/search.sgml94
-rw-r--r--hu_HU.ISO8859-2/share/sgml/bibliography.sgml4
-rw-r--r--hu_HU.ISO8859-2/share/sgml/catalog4
-rw-r--r--hu_HU.ISO8859-2/share/sgml/events.xml14
-rw-r--r--hu_HU.ISO8859-2/share/sgml/freebsd.dsl8
-rw-r--r--hu_HU.ISO8859-2/share/sgml/libcommon.xsl2
-rw-r--r--hu_HU.ISO8859-2/share/sgml/navibar.l10n.ent4
-rw-r--r--hu_HU.ISO8859-2/share/sgml/templates.events.xsl4
-rw-r--r--hu_HU.ISO8859-2/share/sgml/templates.news-rdf.xsl4
-rw-r--r--hu_HU.ISO8859-2/share/sgml/templates.news-rss.xsl2
-rw-r--r--hu_HU.ISO8859-2/share/sgml/templates.oldnewsflash.xsl2
-rw-r--r--hu_HU.ISO8859-2/share/sgml/templates.oldpress.xsl4
-rw-r--r--hu_HU.ISO8859-2/share/sgml/templates.press-rss.xsl4
-rw-r--r--hu_HU.ISO8859-2/share/sgml/trademarks.ent2
-rw-r--r--hu_HU.ISO8859-2/slides/common/freebsd-linux-license.xml2
-rw-r--r--hu_HU.ISO8859-2/slides/common/freebsd-users.xml2
-rw-r--r--hu_HU.ISO8859-2/slides/freebsd-general/slides.xml2
-rw-r--r--it_IT.ISO8859-15/articles/explaining-bsd/article.sgml2
-rw-r--r--it_IT.ISO8859-15/articles/multi-os/Makefile2
-rw-r--r--it_IT.ISO8859-15/articles/new-users/Makefile2
-rw-r--r--it_IT.ISO8859-15/books/Makefile.inc4
-rw-r--r--it_IT.ISO8859-15/books/handbook/basics/chapter.sgml118
-rw-r--r--it_IT.ISO8859-15/books/handbook/eresources/chapter.sgml18
-rw-r--r--it_IT.ISO8859-15/books/handbook/geom/chapter.sgml4
-rw-r--r--it_IT.ISO8859-15/books/handbook/install/chapter.sgml2
-rw-r--r--it_IT.ISO8859-15/books/handbook/introduction/chapter.sgml4
-rw-r--r--it_IT.ISO8859-15/books/handbook/jails/chapter.sgml4
-rw-r--r--it_IT.ISO8859-15/books/handbook/l10n/chapter.sgml6
-rw-r--r--it_IT.ISO8859-15/books/handbook/mirrors/chapter.sgml4
-rw-r--r--it_IT.ISO8859-15/books/handbook/ports/chapter.sgml16
-rw-r--r--it_IT.ISO8859-15/books/handbook/security/chapter.sgml4
-rw-r--r--it_IT.ISO8859-15/books/handbook/serialcomms/chapter.sgml24
-rw-r--r--it_IT.ISO8859-15/books/handbook/vinum/chapter.sgml2
-rw-r--r--it_IT.ISO8859-15/books/handbook/x11/chapter.sgml22
-rw-r--r--it_IT.ISO8859-15/books/unix-introduction/command-summary/chapter.sgml314
-rw-r--r--it_IT.ISO8859-15/htdocs/about.sgml2
-rw-r--r--it_IT.ISO8859-15/htdocs/index.xsl6
-rw-r--r--it_IT.ISO8859-15/htdocs/mailto.sgml8
-rw-r--r--it_IT.ISO8859-15/htdocs/releases/4.11R/announce.sgml2
-rw-r--r--it_IT.ISO8859-15/share/sgml/glossary.ent4
-rw-r--r--it_IT.ISO8859-15/share/sgml/header.l10n.ent4
-rw-r--r--it_IT.ISO8859-15/share/sgml/navibar.l10n.ent4
-rw-r--r--it_IT.ISO8859-15/share/sgml/trademarks.ent2
-rw-r--r--ja_JP.eucJP/articles/Makefile.inc2
-rw-r--r--ja_JP.eucJP/articles/contributors/article.sgml16
-rw-r--r--ja_JP.eucJP/articles/dialup-firewall/article.sgml2
-rw-r--r--ja_JP.eucJP/articles/diskless-x/article.sgml40
-rw-r--r--ja_JP.eucJP/articles/fonts/article.sgml20
-rw-r--r--ja_JP.eucJP/articles/ipsec-must/article.sgml2
-rw-r--r--ja_JP.eucJP/articles/multi-os/article.sgml6
-rw-r--r--ja_JP.eucJP/articles/zip-drive/article.sgml12
-rw-r--r--ja_JP.eucJP/books/Makefile.inc2
-rw-r--r--ja_JP.eucJP/books/design-44bsd/book.sgml444
-rw-r--r--ja_JP.eucJP/books/faq/Makefile6
-rw-r--r--ja_JP.eucJP/books/faq/book.sgml4
-rw-r--r--ja_JP.eucJP/books/fdp-primer/Makefile26
-rw-r--r--ja_JP.eucJP/books/fdp-primer/chapters.ent10
-rw-r--r--ja_JP.eucJP/books/fdp-primer/examples/appendix.sgml20
-rw-r--r--ja_JP.eucJP/books/handbook/Makefile8
-rw-r--r--ja_JP.eucJP/books/handbook/advanced-networking/chapter.sgml144
-rw-r--r--ja_JP.eucJP/books/handbook/backups/chapter.sgml36
-rw-r--r--ja_JP.eucJP/books/handbook/basics/chapter.sgml208
-rw-r--r--ja_JP.eucJP/books/handbook/bibliography/chapter.sgml2
-rw-r--r--ja_JP.eucJP/books/handbook/book.sgml4
-rw-r--r--ja_JP.eucJP/books/handbook/chapters.ent4
-rw-r--r--ja_JP.eucJP/books/handbook/config/chapter.sgml48
-rw-r--r--ja_JP.eucJP/books/handbook/contrib/Makefile2
-rw-r--r--ja_JP.eucJP/books/handbook/contrib/chapter.sgml10
-rw-r--r--ja_JP.eucJP/books/handbook/cutting-edge/chapter.sgml98
-rw-r--r--ja_JP.eucJP/books/handbook/desktop/chapter.sgml8
-rw-r--r--ja_JP.eucJP/books/handbook/eresources/chapter.sgml28
-rw-r--r--ja_JP.eucJP/books/handbook/hw/chapter.sgml66
-rw-r--r--ja_JP.eucJP/books/handbook/internals/chapter.sgml612
-rw-r--r--ja_JP.eucJP/books/handbook/jcontrib/chapter.sgml2
-rw-r--r--ja_JP.eucJP/books/handbook/kernelconfig/chapter.sgml20
-rw-r--r--ja_JP.eucJP/books/handbook/kerneldebug/chapter.sgml12
-rw-r--r--ja_JP.eucJP/books/handbook/linuxemu/chapter.sgml32
-rw-r--r--ja_JP.eucJP/books/handbook/mirrors/chapter.sgml8
-rw-r--r--ja_JP.eucJP/books/handbook/multimedia/chapter.sgml10
-rw-r--r--ja_JP.eucJP/books/handbook/policies/chapter.sgml10
-rw-r--r--ja_JP.eucJP/books/handbook/ports/chapter.sgml16
-rw-r--r--ja_JP.eucJP/books/handbook/ppp-and-slip/chapter.sgml480
-rw-r--r--ja_JP.eucJP/books/handbook/security/chapter.sgml10
-rw-r--r--ja_JP.eucJP/books/handbook/staff/chapter.sgml84
-rw-r--r--ja_JP.eucJP/books/handbook/txtfiles.ent8
-rw-r--r--ja_JP.eucJP/books/handbook/users/chapter.sgml12
-rw-r--r--ja_JP.eucJP/books/handbook/x11/chapter.sgml14
-rw-r--r--ja_JP.eucJP/books/porters-handbook/Makefile4
-rw-r--r--ja_JP.eucJP/books/porters-handbook/book.sgml14
-rw-r--r--ja_JP.eucJP/books/ppp-primer/Makefile6
-rw-r--r--ja_JP.eucJP/books/ppp-primer/book.sgml518
-rw-r--r--ja_JP.eucJP/htdocs/FAQ/Makefile2
-rw-r--r--ja_JP.eucJP/htdocs/applications.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/availability.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/community.xsl2
-rw-r--r--ja_JP.eucJP/htdocs/community/irc.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/copyright/license.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/developers/cvs.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/docproj/Makefile4
-rw-r--r--ja_JP.eucJP/htdocs/docproj/current.sgml24
-rw-r--r--ja_JP.eucJP/htdocs/docproj/docproj.sgml6
-rw-r--r--ja_JP.eucJP/htdocs/docproj/sgml.sgml16
-rw-r--r--ja_JP.eucJP/htdocs/docproj/submitting.sgml10
-rw-r--r--ja_JP.eucJP/htdocs/docproj/translations.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/docproj/who.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/docs/books.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/features.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/handbook/Makefile2
-rw-r--r--ja_JP.eucJP/htdocs/index.xsl2
-rw-r--r--ja_JP.eucJP/htdocs/internal/Makefile4
-rw-r--r--ja_JP.eucJP/htdocs/internal/about.sgml6
-rw-r--r--ja_JP.eucJP/htdocs/internal/machines.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/internet.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/jabout.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/java/advocacy.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/java/dists/12.sgml12
-rw-r--r--ja_JP.eucJP/htdocs/java/dists/13.sgml18
-rw-r--r--ja_JP.eucJP/htdocs/java/dists/14.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/java/install.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/java/java-rss.xsl2
-rw-r--r--ja_JP.eucJP/htdocs/java/links/Makefile4
-rw-r--r--ja_JP.eucJP/htdocs/java/links/api.sgml10
-rw-r--r--ja_JP.eucJP/htdocs/java/links/development.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/java/links/index.sgml6
-rw-r--r--ja_JP.eucJP/htdocs/java/links/servlets.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/java/links/vendor.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/mailto.sgml6
-rw-r--r--ja_JP.eucJP/htdocs/news/1996/index.sgml6
-rw-r--r--ja_JP.eucJP/htdocs/news/1997/index.sgml24
-rw-r--r--ja_JP.eucJP/htdocs/news/2001/news.xml100
-rw-r--r--ja_JP.eucJP/htdocs/news/press-rel-5.sgml22
-rw-r--r--ja_JP.eucJP/htdocs/platforms/alpha.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/platforms/arm.sgml6
-rw-r--r--ja_JP.eucJP/htdocs/platforms/ia64/index.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/platforms/ia64/todo.sgml8
-rw-r--r--ja_JP.eucJP/htdocs/platforms/mips.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/platforms/pc98.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/platforms/ppc.sgml6
-rw-r--r--ja_JP.eucJP/htdocs/platforms/x86-64.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/ports/comments.ja12
-rw-r--r--ja_JP.eucJP/htdocs/ports/index.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/projects/Makefile2
-rw-r--r--ja_JP.eucJP/htdocs/projects/cvsweb.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/projects/newbies.sgml40
-rw-r--r--ja_JP.eucJP/htdocs/publish.sgml10
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.1.5R/notes.sgml20
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.1.6R/notes.sgml20
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2.1R/notes.sgml32
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2.2R/errata.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2.2R/notes.sgml32
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2.5R/errata.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2.5R/notes.sgml20
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2.6R/errata.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2.7R/notes.sgml28
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2.8R/notes.sgml20
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2R/install-media.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/2.2R/notes.sgml32
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.0R/notes.sgml110
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.1R/announce.sgml28
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.1R/errata.sgml18
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.1R/notes.sgml18
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.2R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.2R/errata.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.2R/notes.sgml18
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.3R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.3R/errata.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.3R/notes.sgml30
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.4R/announce.sgml16
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.4R/errata.sgml6
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.4R/notes.sgml18
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.5R/announce.sgml36
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.5R/errata.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/3.5R/notes.sgml18
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.0R/announce.sgml16
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.0R/errata.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.0R/notes.sgml20
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.1.1R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.1.1R/errata.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.1.1R/notes.sgml10
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.1R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.1R/errata.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.1R/notes.sgml10
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.2R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.2R/errata.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.2R/notes.sgml18
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.3R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.3R/errata.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.3R/notes.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.4R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.4R/notes.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.5R/contents.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.5R/qa.sgml26
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.5R/schedule.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/releases/4.6.2R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/5.0R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/releases/8.2R/announce.sgml2
-rw-r--r--ja_JP.eucJP/htdocs/relnotes.sgml8
-rw-r--r--ja_JP.eucJP/htdocs/search/Makefile2
-rw-r--r--ja_JP.eucJP/htdocs/search/search.sgml98
-rw-r--r--ja_JP.eucJP/htdocs/security/mkindex.xsl2
-rw-r--r--ja_JP.eucJP/htdocs/smp/index.sgml4
-rw-r--r--ja_JP.eucJP/htdocs/y2kbug.sgml56
-rw-r--r--ja_JP.eucJP/share/sgml/authors.ent2
-rw-r--r--ja_JP.eucJP/share/sgml/catalog2
-rw-r--r--ja_JP.eucJP/share/sgml/freebsd.dsl6
-rw-r--r--ja_JP.eucJP/share/sgml/header.l10n.ent2
-rw-r--r--ja_JP.eucJP/share/sgml/navibar.l10n.ent4
-rw-r--r--ja_JP.eucJP/share/sgml/press.xml6
-rw-r--r--ja_JP.eucJP/share/sgml/teams.ent2
-rw-r--r--ja_JP.eucJP/share/sgml/templates.events.xsl4
-rw-r--r--ja_JP.eucJP/share/sgml/templates.news-rss.xsl4
-rw-r--r--ja_JP.eucJP/share/sgml/templates.oldnewsflash.xsl4
-rw-r--r--ja_JP.eucJP/share/sgml/templates.oldpress.xsl6
-rw-r--r--ja_JP.eucJP/share/sgml/trademarks.ent2
-rw-r--r--mn_MN.UTF-8/books/handbook/Makefile8
-rw-r--r--mn_MN.UTF-8/books/handbook/advanced-networking/chapter.sgml3462
-rw-r--r--mn_MN.UTF-8/books/handbook/audit/chapter.sgml218
-rw-r--r--mn_MN.UTF-8/books/handbook/basics/chapter.sgml840
-rw-r--r--mn_MN.UTF-8/books/handbook/bibliography/chapter.sgml174
-rw-r--r--mn_MN.UTF-8/books/handbook/book.sgml54
-rw-r--r--mn_MN.UTF-8/books/handbook/boot/chapter.sgml608
-rw-r--r--mn_MN.UTF-8/books/handbook/bsdinstall/chapter.sgml1154
-rw-r--r--mn_MN.UTF-8/books/handbook/chapters.ent8
-rw-r--r--mn_MN.UTF-8/books/handbook/colophon.sgml18
-rw-r--r--mn_MN.UTF-8/books/handbook/config/chapter.sgml2502
-rw-r--r--mn_MN.UTF-8/books/handbook/cutting-edge/chapter.sgml2404
-rw-r--r--mn_MN.UTF-8/books/handbook/desktop/chapter.sgml628
-rw-r--r--mn_MN.UTF-8/books/handbook/disks/chapter.sgml2830
-rw-r--r--mn_MN.UTF-8/books/handbook/dtrace/chapter.sgml204
-rw-r--r--mn_MN.UTF-8/books/handbook/eresources/chapter.sgml772
-rw-r--r--mn_MN.UTF-8/books/handbook/filesystems/chapter.sgml572
-rw-r--r--mn_MN.UTF-8/books/handbook/firewalls/chapter.sgml1548
-rw-r--r--mn_MN.UTF-8/books/handbook/geom/chapter.sgml556
-rw-r--r--mn_MN.UTF-8/books/handbook/install/chapter.sgml1664
-rw-r--r--mn_MN.UTF-8/books/handbook/introduction/chapter.sgml560
-rw-r--r--mn_MN.UTF-8/books/handbook/jails/chapter.sgml594
-rw-r--r--mn_MN.UTF-8/books/handbook/kernelconfig/chapter.sgml540
-rw-r--r--mn_MN.UTF-8/books/handbook/l10n/chapter.sgml438
-rw-r--r--mn_MN.UTF-8/books/handbook/linuxemu/chapter.sgml724
-rw-r--r--mn_MN.UTF-8/books/handbook/mac/chapter.sgml1746
-rw-r--r--mn_MN.UTF-8/books/handbook/mail/chapter.sgml1326
-rw-r--r--mn_MN.UTF-8/books/handbook/mirrors/chapter.sgml1360
-rw-r--r--mn_MN.UTF-8/books/handbook/multimedia/chapter.sgml1186
-rw-r--r--mn_MN.UTF-8/books/handbook/network-servers/chapter.sgml3368
-rw-r--r--mn_MN.UTF-8/books/handbook/pgpkeys/chapter.sgml14
-rw-r--r--mn_MN.UTF-8/books/handbook/ports/chapter.sgml608
-rw-r--r--mn_MN.UTF-8/books/handbook/ppp-and-slip/chapter.sgml1684
-rw-r--r--mn_MN.UTF-8/books/handbook/preface/preface.sgml382
-rw-r--r--mn_MN.UTF-8/books/handbook/printing/chapter.sgml3528
-rw-r--r--mn_MN.UTF-8/books/handbook/security/chapter.sgml3112
-rw-r--r--mn_MN.UTF-8/books/handbook/serialcomms/chapter.sgml1714
-rw-r--r--mn_MN.UTF-8/books/handbook/txtfiles.ent8
-rw-r--r--mn_MN.UTF-8/books/handbook/users/chapter.sgml184
-rw-r--r--mn_MN.UTF-8/books/handbook/vinum/chapter.sgml960
-rw-r--r--mn_MN.UTF-8/books/handbook/virtualization/chapter.sgml540
-rw-r--r--mn_MN.UTF-8/books/handbook/x11/chapter.sgml946
-rw-r--r--mn_MN.UTF-8/share/sgml/catalog4
-rw-r--r--mn_MN.UTF-8/share/sgml/freebsd.dsl10
-rw-r--r--mn_MN.UTF-8/share/sgml/glossary.ent368
-rw-r--r--mn_MN.UTF-8/share/sgml/mailing-lists.ent2
-rw-r--r--mn_MN.UTF-8/share/sgml/mirrors-local.xsl4
-rw-r--r--mn_MN.UTF-8/share/sgml/trademarks.ent244
-rw-r--r--mn_MN.UTF-8/share/sgml/transtable.xml6
-rw-r--r--nl_NL.ISO8859-1/Makefile2
-rw-r--r--nl_NL.ISO8859-1/articles/Makefile.inc2
-rw-r--r--nl_NL.ISO8859-1/articles/solid-state/Makefile2
-rw-r--r--nl_NL.ISO8859-1/books/Makefile.inc2
-rw-r--r--nl_NL.ISO8859-1/books/handbook/chapters.ent6
-rw-r--r--nl_NL.ISO8859-1/books/handbook/dtrace/Makefile2
-rw-r--r--nl_NL.ISO8859-1/books/handbook/txtfiles.ent8
-rw-r--r--nl_NL.ISO8859-1/htdocs/availability.sgml2
-rw-r--r--nl_NL.ISO8859-1/share/sgml/freebsd.dsl2
-rw-r--r--nl_NL.ISO8859-1/share/sgml/mirrors-local.xsl2
-rw-r--r--nl_NL.ISO8859-1/share/sgml/navibar.l10n.ent4
-rw-r--r--nl_NL.ISO8859-1/share/sgml/newsgroups.ent2
-rw-r--r--no_NO.ISO8859-1/books/handbook/bibliography/chapter.sgml184
-rw-r--r--no_NO.ISO8859-1/books/handbook/install/chapter.sgml10
-rw-r--r--pl_PL.ISO8859-2/articles/dialup-firewall/article.sgml2
-rw-r--r--pl_PL.ISO8859-2/articles/new-users/article.sgml2
-rw-r--r--pl_PL.ISO8859-2/books/Makefile.inc2
-rw-r--r--pl_PL.ISO8859-2/books/handbook/Makefile8
-rw-r--r--pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.sgml10
-rw-r--r--pl_PL.ISO8859-2/books/handbook/basics/chapter.sgml198
-rw-r--r--pl_PL.ISO8859-2/books/handbook/bibliography/chapter.sgml168
-rw-r--r--pl_PL.ISO8859-2/books/handbook/book.sgml20
-rw-r--r--pl_PL.ISO8859-2/books/handbook/boot/chapter.sgml42
-rw-r--r--pl_PL.ISO8859-2/books/handbook/chapters.ent6
-rw-r--r--pl_PL.ISO8859-2/books/handbook/config/chapter.sgml10
-rw-r--r--pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.sgml148
-rw-r--r--pl_PL.ISO8859-2/books/handbook/desktop/chapter.sgml10
-rw-r--r--pl_PL.ISO8859-2/books/handbook/disks/chapter.sgml4
-rw-r--r--pl_PL.ISO8859-2/books/handbook/geom/chapter.sgml2
-rw-r--r--pl_PL.ISO8859-2/books/handbook/install/chapter.sgml506
-rw-r--r--pl_PL.ISO8859-2/books/handbook/introduction/chapter.sgml70
-rw-r--r--pl_PL.ISO8859-2/books/handbook/kernelconfig/chapter.sgml28
-rw-r--r--pl_PL.ISO8859-2/books/handbook/l10n/chapter.sgml18
-rw-r--r--pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.sgml124
-rw-r--r--pl_PL.ISO8859-2/books/handbook/mac/chapter.sgml6
-rw-r--r--pl_PL.ISO8859-2/books/handbook/mail/chapter.sgml4
-rw-r--r--pl_PL.ISO8859-2/books/handbook/mirrors/chapter.sgml252
-rw-r--r--pl_PL.ISO8859-2/books/handbook/multimedia/chapter.sgml18
-rw-r--r--pl_PL.ISO8859-2/books/handbook/network-servers/chapter.sgml4
-rw-r--r--pl_PL.ISO8859-2/books/handbook/ports/chapter.sgml22
-rw-r--r--pl_PL.ISO8859-2/books/handbook/ppp-and-slip/chapter.sgml90
-rw-r--r--pl_PL.ISO8859-2/books/handbook/preface/preface.sgml2
-rw-r--r--pl_PL.ISO8859-2/books/handbook/printing/chapter.sgml780
-rw-r--r--pl_PL.ISO8859-2/books/handbook/security/chapter.sgml470
-rw-r--r--pl_PL.ISO8859-2/books/handbook/txtfiles.ent8
-rw-r--r--pl_PL.ISO8859-2/books/handbook/users/chapter.sgml18
-rw-r--r--pl_PL.ISO8859-2/books/handbook/vinum/chapter.sgml62
-rw-r--r--pl_PL.ISO8859-2/books/handbook/x11/chapter.sgml2
-rw-r--r--pl_PL.ISO8859-2/share/sgml/entities.ent2
-rw-r--r--pl_PL.ISO8859-2/share/sgml/freebsd.dsl8
-rw-r--r--pl_PL.ISO8859-2/share/sgml/l10n.ent2
-rw-r--r--pl_PL.ISO8859-2/share/sgml/trademarks.ent8
-rw-r--r--pt_BR.ISO8859-1/articles/Makefile.inc2
-rw-r--r--pt_BR.ISO8859-1/articles/contributing/article.sgml10
-rw-r--r--pt_BR.ISO8859-1/books/Makefile.inc2
-rw-r--r--pt_BR.ISO8859-1/books/faq/Makefile6
-rw-r--r--pt_BR.ISO8859-1/books/faq/book.sgml246
-rw-r--r--pt_BR.ISO8859-1/books/handbook/Makefile10
-rw-r--r--pt_BR.ISO8859-1/books/handbook/book.sgml14
-rw-r--r--pt_BR.ISO8859-1/books/handbook/mirrors/chapter.sgml448
-rw-r--r--pt_BR.ISO8859-1/books/handbook/pgpkeys/chapter.sgml8
-rw-r--r--pt_BR.ISO8859-1/share/sgml/catalog2
-rw-r--r--pt_BR.ISO8859-1/share/sgml/freebsd.dsl6
-rw-r--r--pt_BR.ISO8859-1/share/sgml/mailing-lists.ent8
-rw-r--r--pt_BR.ISO8859-1/share/sgml/trademarks.ent22
-rw-r--r--ru_RU.KOI8-R/articles/Makefile.inc2
-rw-r--r--ru_RU.KOI8-R/articles/committers-guide/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/committers-guide/article.sgml18
-rw-r--r--ru_RU.KOI8-R/articles/console-server/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/custom-gcc/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/cvsup-advanced/article.sgml6
-rw-r--r--ru_RU.KOI8-R/articles/dialup-firewall/Makefile4
-rw-r--r--ru_RU.KOI8-R/articles/dialup-firewall/article.sgml24
-rw-r--r--ru_RU.KOI8-R/articles/diskless-x/Makefile4
-rw-r--r--ru_RU.KOI8-R/articles/diskless-x/article.sgml36
-rw-r--r--ru_RU.KOI8-R/articles/fbsd-from-scratch/article.sgml2
-rw-r--r--ru_RU.KOI8-R/articles/fonts/Makefile4
-rw-r--r--ru_RU.KOI8-R/articles/fonts/article.sgml4
-rw-r--r--ru_RU.KOI8-R/articles/formatting-media/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/freebsd-questions/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/freebsd-questions/article.sgml16
-rw-r--r--ru_RU.KOI8-R/articles/geom-class/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/geom-class/article.sgml6
-rw-r--r--ru_RU.KOI8-R/articles/laptop/article.sgml18
-rw-r--r--ru_RU.KOI8-R/articles/linux-comparison/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/mailing-list-faq/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/mh/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/multi-os/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/multi-os/article.sgml12
-rw-r--r--ru_RU.KOI8-R/articles/new-users/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/pam/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/pam/article.sgml6
-rw-r--r--ru_RU.KOI8-R/articles/portbuild/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/portbuild/article.sgml2
-rw-r--r--ru_RU.KOI8-R/articles/releng/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/solid-state/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/solid-state/article.sgml2
-rw-r--r--ru_RU.KOI8-R/articles/version-guide/Makefile4
-rw-r--r--ru_RU.KOI8-R/articles/vm-design/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/vm-design/article.sgml6
-rw-r--r--ru_RU.KOI8-R/articles/zip-drive/Makefile2
-rw-r--r--ru_RU.KOI8-R/articles/zip-drive/article.sgml36
-rw-r--r--ru_RU.KOI8-R/books/Makefile.inc2
-rw-r--r--ru_RU.KOI8-R/books/arch-handbook/locking/chapter.sgml18
-rw-r--r--ru_RU.KOI8-R/books/arch-handbook/sound/chapter.sgml56
-rw-r--r--ru_RU.KOI8-R/books/design-44bsd/book.sgml144
-rw-r--r--ru_RU.KOI8-R/books/developers-handbook/Makefile4
-rw-r--r--ru_RU.KOI8-R/books/developers-handbook/chapters.ent6
-rw-r--r--ru_RU.KOI8-R/books/developers-handbook/introduction/chapter.sgml6
-rw-r--r--ru_RU.KOI8-R/books/developers-handbook/policies/chapter.sgml2
-rw-r--r--ru_RU.KOI8-R/books/developers-handbook/secure/chapter.sgml24
-rw-r--r--ru_RU.KOI8-R/books/faq/Makefile4
-rw-r--r--ru_RU.KOI8-R/books/fdp-primer/Makefile26
-rw-r--r--ru_RU.KOI8-R/books/fdp-primer/book.sgml4
-rw-r--r--ru_RU.KOI8-R/books/fdp-primer/overview/chapter.sgml4
-rw-r--r--ru_RU.KOI8-R/books/fdp-primer/see-also/chapter.sgml2
-rw-r--r--ru_RU.KOI8-R/books/fdp-primer/sgml-markup/chapter.sgml76
-rw-r--r--ru_RU.KOI8-R/books/fdp-primer/the-website/chapter.sgml8
-rw-r--r--ru_RU.KOI8-R/books/fdp-primer/writing-style/chapter.sgml6
-rw-r--r--ru_RU.KOI8-R/books/handbook/bibliography/chapter.sgml2
-rw-r--r--ru_RU.KOI8-R/books/handbook/colophon.sgml2
-rw-r--r--ru_RU.KOI8-R/books/handbook/disks/chapter.sgml2
-rw-r--r--ru_RU.KOI8-R/books/handbook/l10n/chapter.sgml4
-rw-r--r--ru_RU.KOI8-R/books/handbook/linuxemu/chapter.sgml92
-rw-r--r--ru_RU.KOI8-R/books/handbook/mac/chapter.sgml4
-rw-r--r--ru_RU.KOI8-R/books/handbook/mirrors/chapter.sgml2
-rw-r--r--ru_RU.KOI8-R/books/handbook/ports/chapter.sgml6
-rw-r--r--ru_RU.KOI8-R/books/handbook/printing/chapter.sgml138
-rw-r--r--ru_RU.KOI8-R/books/handbook/security/chapter.sgml2
-rw-r--r--ru_RU.KOI8-R/books/handbook/txtfiles.ent6
-rw-r--r--ru_RU.KOI8-R/books/handbook/x11/chapter.sgml56
-rw-r--r--ru_RU.KOI8-R/books/porters-handbook/Makefile2
-rw-r--r--ru_RU.KOI8-R/books/ppp-primer/Makefile6
-rw-r--r--ru_RU.KOI8-R/books/ppp-primer/book.sgml4
-rw-r--r--ru_RU.KOI8-R/htdocs/applications.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/availability.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/community/mailinglists.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/community/webresources.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/developers/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/docproj/Makefile4
-rw-r--r--ru_RU.KOI8-R/htdocs/docproj/handbook.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/docs/books.sgml22
-rw-r--r--ru_RU.KOI8-R/htdocs/docs/webresources.sgml6
-rw-r--r--ru_RU.KOI8-R/htdocs/donations/donors.sgml14
-rw-r--r--ru_RU.KOI8-R/htdocs/donations/index.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/donations/wantlist.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/features.sgml6
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/contact.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/docs/develfaq.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/docs/faq2.sgml14
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/docs/gnome2_porting.sgml20
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/docs/porting.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/includes.xsl6
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/index.xsl8
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/news.xml10
-rw-r--r--ru_RU.KOI8-R/htdocs/gnome/newsflash.xsl8
-rw-r--r--ru_RU.KOI8-R/htdocs/handbook/index.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/internal/Makefile6
-rw-r--r--ru_RU.KOI8-R/htdocs/internal/about.sgml6
-rw-r--r--ru_RU.KOI8-R/htdocs/internal/bylaws.sgml8
-rw-r--r--ru_RU.KOI8-R/htdocs/internal/developer.sgml6
-rw-r--r--ru_RU.KOI8-R/htdocs/internal/internal.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/internal/new-account.sgml8
-rw-r--r--ru_RU.KOI8-R/htdocs/internal/photos.sgml4
-rw-r--r--ru_RU.KOI8-R/htdocs/internet.sgml4
-rw-r--r--ru_RU.KOI8-R/htdocs/java/dists/14.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/java/dists/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/java/install.sgml4
-rw-r--r--ru_RU.KOI8-R/htdocs/java/links/Makefile4
-rw-r--r--ru_RU.KOI8-R/htdocs/java/newsflash.sgml4
-rw-r--r--ru_RU.KOI8-R/htdocs/kse/index.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/mailto.sgml10
-rw-r--r--ru_RU.KOI8-R/htdocs/news/1996/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/news/1997/index.sgml4
-rw-r--r--ru_RU.KOI8-R/htdocs/news/1998/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/news/1998/press.xml4
-rw-r--r--ru_RU.KOI8-R/htdocs/news/1999/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/news/1999/press.xml18
-rw-r--r--ru_RU.KOI8-R/htdocs/news/2000/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/news/2000/press.xml28
-rw-r--r--ru_RU.KOI8-R/htdocs/news/2001/news.xml102
-rw-r--r--ru_RU.KOI8-R/htdocs/news/2001/press.xml12
-rw-r--r--ru_RU.KOI8-R/htdocs/news/2002/news.xml16
-rw-r--r--ru_RU.KOI8-R/htdocs/news/2003/news.xml4
-rw-r--r--ru_RU.KOI8-R/htdocs/news/press-rel-2.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/news/status/status.sgml4
-rw-r--r--ru_RU.KOI8-R/htdocs/platforms/amd64.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/platforms/arm.sgml6
-rw-r--r--ru_RU.KOI8-R/htdocs/platforms/mips.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/platforms/pc98.sgml6
-rw-r--r--ru_RU.KOI8-R/htdocs/platforms/ppc.sgml12
-rw-r--r--ru_RU.KOI8-R/htdocs/platforms/x86-64.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/portmgr/qa.sgml8
-rw-r--r--ru_RU.KOI8-R/htdocs/ports/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/ports/Makefile.inc2
-rw-r--r--ru_RU.KOI8-R/htdocs/projects/busdma/index.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/projects/projects.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/projects/summerofcode.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/publish.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/releases/5.3R/installation.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/releases/5.4R/installation.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/releng/charter.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/relnotes/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/search/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/search/search.sgml16
-rw-r--r--ru_RU.KOI8-R/htdocs/security/Makefile2
-rw-r--r--ru_RU.KOI8-R/htdocs/send-pr.sgml14
-rw-r--r--ru_RU.KOI8-R/htdocs/smp/index.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/snapshots/index.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/support.sgml18
-rw-r--r--ru_RU.KOI8-R/htdocs/support/bugreports.sgml2
-rw-r--r--ru_RU.KOI8-R/htdocs/where.sgml4
-rw-r--r--ru_RU.KOI8-R/share/sgml/events2003.xml2
-rw-r--r--ru_RU.KOI8-R/share/sgml/events2008.xml6
-rw-r--r--ru_RU.KOI8-R/share/sgml/events2009.xml2
-rw-r--r--ru_RU.KOI8-R/share/sgml/freebsd.dsl18
-rw-r--r--ru_RU.KOI8-R/share/sgml/glossary.ent6
-rw-r--r--ru_RU.KOI8-R/share/sgml/header.l10n.ent2
-rw-r--r--ru_RU.KOI8-R/share/sgml/navibar.l10n.ent4
-rw-r--r--ru_RU.KOI8-R/share/sgml/news.xml22
-rw-r--r--ru_RU.KOI8-R/share/sgml/newsgroups.ent2
-rw-r--r--ru_RU.KOI8-R/share/sgml/templates.events.xsl4
-rw-r--r--ru_RU.KOI8-R/share/sgml/templates.usergroups.xsl2
-rw-r--r--ru_RU.KOI8-R/share/sgml/trademarks.ent2
-rw-r--r--ru_RU.KOI8-R/share/sgml/translators.ent2
-rw-r--r--ru_RU.KOI8-R/share/sgml/transtable.xml6
-rw-r--r--ru_RU.KOI8-R/share/sgml/urls.ent2
-rw-r--r--share/images/books/handbook/bsdinstall/bsdinstall-config-components.pngbin5865 -> 5865 bytes
-rw-r--r--share/images/books/handbook/bsdinstall/bsdinstall-part-entire-part.pngbin5287 -> 5287 bytes
-rw-r--r--share/mk/doc.xml.mk2
-rw-r--r--share/openoffice/BSDi.xsl4
-rw-r--r--share/openoffice/BSDi/META-INF/manifest.xml2
-rw-r--r--share/openoffice/BSDi/meta.xml2
-rw-r--r--share/openoffice/BSDi/settings.xml2
-rw-r--r--share/openoffice/BSDi/styles.xml2
-rw-r--r--share/openoffice/include.xsl2
-rw-r--r--share/pgpkeys/pgpkeys-developers.sgml2
-rw-r--r--share/security/advisories/FreeBSD-SA-98:08.fragment.asc4
-rw-r--r--share/security/patches/SA-10:06/nfsclient.patch2
-rw-r--r--share/sgml/bibliography.sgml8
-rw-r--r--share/sgml/catalog10
-rw-r--r--share/sgml/commercial.consult.xml28
-rw-r--r--share/sgml/commercial.hardware.xml10
-rw-r--r--share/sgml/commercial.isp.xml36
-rw-r--r--share/sgml/commercial.misc.xml2
-rw-r--r--share/sgml/commercial.software.xml14
-rw-r--r--share/sgml/events2003.xml2
-rw-r--r--share/sgml/events2004.xml6
-rw-r--r--share/sgml/events2008.xml6
-rw-r--r--share/sgml/events2009.xml2
-rw-r--r--share/sgml/freebsd-common.dsl2
-rw-r--r--share/sgml/freebsd-html.dsl2
-rw-r--r--share/sgml/freebsd-print.dsl18
-rw-r--r--share/sgml/freebsd.dtd6
-rw-r--r--share/sgml/freebsd42.dtd2
-rw-r--r--share/sgml/header.ent2
-rw-r--r--share/sgml/l10n.ent2
-rw-r--r--share/sgml/libcommon.xsl12
-rw-r--r--share/sgml/mirrors.xml2
-rw-r--r--share/sgml/pgp.dsl2
-rw-r--r--share/sgml/spellcheck.dsl2
-rw-r--r--share/sgml/templates.events.xsl4
-rw-r--r--share/sgml/templates.news-rdf.xsl4
-rw-r--r--share/sgml/templates.news-rss.xsl4
-rw-r--r--share/sgml/templates.oldnewsflash.xsl10
-rw-r--r--share/sgml/templates.oldpress.xsl6
-rw-r--r--share/sgml/templates.pastevents.xsl2
-rw-r--r--share/sgml/templates.press-rss.xsl4
-rw-r--r--share/sgml/trademarks.ent20
-rw-r--r--share/sgml/usergroups.xml38
-rw-r--r--share/sgml/xslt10.dtd14
-rw-r--r--share/xsl/freebsd-common.xsl2
-rw-r--r--share/xsl/freebsd-fo.xsl2
-rw-r--r--share/xsl/freebsd-html.xsl6
-rw-r--r--share/xsl/freebsd.xsl4
-rw-r--r--sr_YU.ISO8859-2/articles/dialup-firewall/article.sgml148
-rw-r--r--sr_YU.ISO8859-2/articles/diskless-x/article.sgml62
-rw-r--r--sr_YU.ISO8859-2/books/faq/Makefile4
-rw-r--r--sr_YU.ISO8859-2/share/sgml/catalog2
-rw-r--r--sr_YU.ISO8859-2/share/sgml/freebsd.dsl10
-rw-r--r--zh_CN.GB2312/articles/Makefile.inc2
-rw-r--r--zh_CN.GB2312/articles/contributing/article.sgml6
-rw-r--r--zh_CN.GB2312/articles/linux-users/Makefile2
-rw-r--r--zh_CN.GB2312/articles/linux-users/article.sgml4
-rw-r--r--zh_CN.GB2312/articles/nanobsd/Makefile2
-rw-r--r--zh_CN.GB2312/articles/nanobsd/article.sgml2
-rw-r--r--zh_CN.GB2312/articles/rc-scripting/Makefile2
-rw-r--r--zh_CN.GB2312/articles/rc-scripting/article.sgml18
-rw-r--r--zh_CN.GB2312/articles/remote-install/Makefile2
-rw-r--r--zh_CN.GB2312/articles/remote-install/article.sgml10
-rw-r--r--zh_CN.GB2312/books/Makefile.inc2
-rw-r--r--zh_CN.GB2312/books/arch-handbook/Makefile4
-rw-r--r--zh_CN.GB2312/books/arch-handbook/book.sgml20
-rw-r--r--zh_CN.GB2312/books/arch-handbook/boot/chapter.sgml4
-rw-r--r--zh_CN.GB2312/books/arch-handbook/chapters.ent6
-rw-r--r--zh_CN.GB2312/books/arch-handbook/driverbasics/chapter.sgml18
-rw-r--r--zh_CN.GB2312/books/arch-handbook/isa/chapter.sgml16
-rw-r--r--zh_CN.GB2312/books/arch-handbook/jail/chapter.sgml20
-rw-r--r--zh_CN.GB2312/books/arch-handbook/kobj/chapter.sgml2
-rw-r--r--zh_CN.GB2312/books/arch-handbook/locking/chapter.sgml18
-rw-r--r--zh_CN.GB2312/books/arch-handbook/mac.ent16
-rw-r--r--zh_CN.GB2312/books/arch-handbook/mac/chapter.sgml1692
-rw-r--r--zh_CN.GB2312/books/arch-handbook/newbus/chapter.sgml112
-rw-r--r--zh_CN.GB2312/books/arch-handbook/pccard/chapter.sgml2
-rw-r--r--zh_CN.GB2312/books/arch-handbook/scsi/chapter.sgml188
-rw-r--r--zh_CN.GB2312/books/arch-handbook/sound/chapter.sgml48
-rw-r--r--zh_CN.GB2312/books/arch-handbook/usb/chapter.sgml14
-rw-r--r--zh_CN.GB2312/books/arch-handbook/vm/chapter.sgml18
-rw-r--r--zh_CN.GB2312/books/handbook/advanced-networking/chapter.sgml26
-rw-r--r--zh_CN.GB2312/books/handbook/audit/chapter.sgml2
-rw-r--r--zh_CN.GB2312/books/handbook/basics/chapter.sgml16
-rw-r--r--zh_CN.GB2312/books/handbook/bibliography/chapter.sgml8
-rw-r--r--zh_CN.GB2312/books/handbook/book.sgml6
-rw-r--r--zh_CN.GB2312/books/handbook/boot/chapter.sgml4
-rw-r--r--zh_CN.GB2312/books/handbook/chapters.ent2
-rw-r--r--zh_CN.GB2312/books/handbook/config/chapter.sgml10
-rw-r--r--zh_CN.GB2312/books/handbook/cutting-edge/chapter.sgml8
-rw-r--r--zh_CN.GB2312/books/handbook/desktop/chapter.sgml18
-rw-r--r--zh_CN.GB2312/books/handbook/disks/chapter.sgml72
-rw-r--r--zh_CN.GB2312/books/handbook/dtrace/chapter.sgml4
-rw-r--r--zh_CN.GB2312/books/handbook/eresources/chapter.sgml6
-rw-r--r--zh_CN.GB2312/books/handbook/filesystems/chapter.sgml6
-rw-r--r--zh_CN.GB2312/books/handbook/firewalls/chapter.sgml6
-rw-r--r--zh_CN.GB2312/books/handbook/geom/chapter.sgml6
-rw-r--r--zh_CN.GB2312/books/handbook/install/chapter.sgml130
-rw-r--r--zh_CN.GB2312/books/handbook/introduction/chapter.sgml74
-rw-r--r--zh_CN.GB2312/books/handbook/jails/chapter.sgml4
-rw-r--r--zh_CN.GB2312/books/handbook/kernelconfig/chapter.sgml14
-rw-r--r--zh_CN.GB2312/books/handbook/l10n/chapter.sgml8
-rw-r--r--zh_CN.GB2312/books/handbook/mac/chapter.sgml6
-rw-r--r--zh_CN.GB2312/books/handbook/mail/chapter.sgml4
-rw-r--r--zh_CN.GB2312/books/handbook/mirrors/chapter.sgml228
-rw-r--r--zh_CN.GB2312/books/handbook/multimedia/chapter.sgml22
-rw-r--r--zh_CN.GB2312/books/handbook/network-servers/chapter.sgml10
-rw-r--r--zh_CN.GB2312/books/handbook/ports/chapter.sgml12
-rw-r--r--zh_CN.GB2312/books/handbook/ppp-and-slip/chapter.sgml4
-rw-r--r--zh_CN.GB2312/books/handbook/printing/chapter.sgml554
-rw-r--r--zh_CN.GB2312/books/handbook/security/chapter.sgml48
-rw-r--r--zh_CN.GB2312/books/handbook/txtfiles.ent8
-rw-r--r--zh_CN.GB2312/books/handbook/users/chapter.sgml4
-rw-r--r--zh_CN.GB2312/books/handbook/vinum/chapter.sgml76
-rw-r--r--zh_CN.GB2312/books/handbook/virtualization/chapter.sgml60
-rw-r--r--zh_CN.GB2312/books/handbook/x11/chapter.sgml6
-rw-r--r--zh_CN.GB2312/books/porters-handbook/Makefile4
-rw-r--r--zh_CN.GB2312/books/porters-handbook/book.sgml22
-rw-r--r--zh_CN.GB2312/htdocs/about.sgml6
-rw-r--r--zh_CN.GB2312/htdocs/availability.sgml2
-rw-r--r--zh_CN.GB2312/htdocs/copyright/freebsd-doc-license.sgml2
-rw-r--r--zh_CN.GB2312/htdocs/features.sgml10
-rw-r--r--zh_CN.GB2312/htdocs/internet.sgml42
-rw-r--r--zh_CN.GB2312/htdocs/mailto.sgml8
-rw-r--r--zh_CN.GB2312/htdocs/platforms/amd64.sgml2
-rw-r--r--zh_CN.GB2312/htdocs/platforms/arm.sgml8
-rw-r--r--zh_CN.GB2312/htdocs/releases/index.sgml12
-rw-r--r--zh_CN.GB2312/htdocs/relnotes.sgml6
-rw-r--r--zh_CN.GB2312/htdocs/y2kbug.sgml70
-rw-r--r--zh_CN.GB2312/share/sgml/authors.ent2
-rw-r--r--zh_CN.GB2312/share/sgml/freebsd.dsl22
-rw-r--r--zh_CN.GB2312/share/sgml/glossary.ent8
-rw-r--r--zh_CN.GB2312/share/sgml/libcommon.xsl4
-rw-r--r--zh_CN.GB2312/share/sgml/mailing-lists.ent2
-rw-r--r--zh_CN.GB2312/share/sgml/navibar.l10n.ent4
-rw-r--r--zh_CN.GB2312/share/sgml/news.xml26
-rw-r--r--zh_CN.GB2312/share/sgml/press.xml2
-rw-r--r--zh_CN.GB2312/share/sgml/trademarks.ent24
-rw-r--r--zh_TW.Big5/articles/Makefile.inc2
-rw-r--r--zh_TW.Big5/articles/contributing/article.sgml14
-rw-r--r--zh_TW.Big5/articles/freebsd-questions/article.sgml50
-rw-r--r--zh_TW.Big5/articles/hubs/article.sgml6
-rw-r--r--zh_TW.Big5/articles/mailing-list-faq/Makefile2
-rw-r--r--zh_TW.Big5/articles/mailing-list-faq/article.sgml12
-rw-r--r--zh_TW.Big5/articles/nanobsd/Makefile2
-rw-r--r--zh_TW.Big5/articles/nanobsd/article.sgml4
-rw-r--r--zh_TW.Big5/articles/pr-guidelines/article.sgml2
-rw-r--r--zh_TW.Big5/articles/problem-reports/article.sgml4
-rw-r--r--zh_TW.Big5/articles/remote-install/Makefile2
-rw-r--r--zh_TW.Big5/articles/remote-install/article.sgml4
-rw-r--r--zh_TW.Big5/books/Makefile.inc2
-rw-r--r--zh_TW.Big5/books/developers-handbook/Makefile4
-rw-r--r--zh_TW.Big5/books/developers-handbook/book.sgml20
-rw-r--r--zh_TW.Big5/books/developers-handbook/chapters.ent6
-rw-r--r--zh_TW.Big5/books/developers-handbook/dma/chapter.sgml368
-rw-r--r--zh_TW.Big5/books/developers-handbook/introduction/chapter.sgml8
-rw-r--r--zh_TW.Big5/books/developers-handbook/ipv6/chapter.sgml12
-rw-r--r--zh_TW.Big5/books/developers-handbook/kerneldebug/chapter.sgml2
-rw-r--r--zh_TW.Big5/books/developers-handbook/policies/chapter.sgml60
-rw-r--r--zh_TW.Big5/books/developers-handbook/secure/chapter.sgml38
-rw-r--r--zh_TW.Big5/books/developers-handbook/sockets/chapter.sgml66
-rw-r--r--zh_TW.Big5/books/developers-handbook/tools/chapter.sgml22
-rw-r--r--zh_TW.Big5/books/faq/Makefile6
-rw-r--r--zh_TW.Big5/books/faq/book.sgml338
-rw-r--r--zh_TW.Big5/books/fdp-primer/Makefile26
-rw-r--r--zh_TW.Big5/books/fdp-primer/book.sgml18
-rw-r--r--zh_TW.Big5/books/fdp-primer/chapters.ent12
-rw-r--r--zh_TW.Big5/books/fdp-primer/doc-build/chapter.sgml18
-rw-r--r--zh_TW.Big5/books/fdp-primer/examples/appendix.sgml36
-rw-r--r--zh_TW.Big5/books/fdp-primer/overview/chapter.sgml72
-rw-r--r--zh_TW.Big5/books/fdp-primer/psgml-mode/chapter.sgml28
-rw-r--r--zh_TW.Big5/books/fdp-primer/see-also/chapter.sgml4
-rw-r--r--zh_TW.Big5/books/fdp-primer/sgml-markup/chapter.sgml472
-rw-r--r--zh_TW.Big5/books/fdp-primer/sgml-primer/chapter.sgml236
-rw-r--r--zh_TW.Big5/books/fdp-primer/structure/chapter.sgml46
-rw-r--r--zh_TW.Big5/books/fdp-primer/stylesheets/chapter.sgml8
-rw-r--r--zh_TW.Big5/books/fdp-primer/the-website/chapter.sgml68
-rw-r--r--zh_TW.Big5/books/fdp-primer/tools/chapter.sgml62
-rw-r--r--zh_TW.Big5/books/fdp-primer/translations/chapter.sgml42
-rw-r--r--zh_TW.Big5/books/fdp-primer/writing-style/chapter.sgml50
-rw-r--r--zh_TW.Big5/books/handbook/Makefile6
-rw-r--r--zh_TW.Big5/books/handbook/advanced-networking/chapter.sgml14
-rw-r--r--zh_TW.Big5/books/handbook/basics/chapter.sgml252
-rw-r--r--zh_TW.Big5/books/handbook/bibliography/chapter.sgml170
-rw-r--r--zh_TW.Big5/books/handbook/book.sgml32
-rw-r--r--zh_TW.Big5/books/handbook/boot/chapter.sgml42
-rw-r--r--zh_TW.Big5/books/handbook/chapters.ent6
-rw-r--r--zh_TW.Big5/books/handbook/config/chapter.sgml28
-rw-r--r--zh_TW.Big5/books/handbook/cutting-edge/chapter.sgml150
-rw-r--r--zh_TW.Big5/books/handbook/desktop/chapter.sgml84
-rw-r--r--zh_TW.Big5/books/handbook/disks/chapter.sgml42
-rw-r--r--zh_TW.Big5/books/handbook/eresources/chapter.sgml6
-rw-r--r--zh_TW.Big5/books/handbook/firewalls/chapter.sgml22
-rw-r--r--zh_TW.Big5/books/handbook/geom/chapter.sgml38
-rw-r--r--zh_TW.Big5/books/handbook/install/chapter.sgml598
-rw-r--r--zh_TW.Big5/books/handbook/introduction/chapter.sgml116
-rw-r--r--zh_TW.Big5/books/handbook/jails/chapter.sgml4
-rw-r--r--zh_TW.Big5/books/handbook/kernelconfig/chapter.sgml62
-rw-r--r--zh_TW.Big5/books/handbook/l10n/chapter.sgml20
-rw-r--r--zh_TW.Big5/books/handbook/linuxemu/chapter.sgml130
-rw-r--r--zh_TW.Big5/books/handbook/mac/chapter.sgml2
-rw-r--r--zh_TW.Big5/books/handbook/mail/chapter.sgml4
-rw-r--r--zh_TW.Big5/books/handbook/mirrors/chapter.sgml252
-rw-r--r--zh_TW.Big5/books/handbook/multimedia/chapter.sgml38
-rw-r--r--zh_TW.Big5/books/handbook/network-servers/chapter.sgml4
-rw-r--r--zh_TW.Big5/books/handbook/ports/chapter.sgml136
-rw-r--r--zh_TW.Big5/books/handbook/ppp-and-slip/chapter.sgml90
-rw-r--r--zh_TW.Big5/books/handbook/preface/preface.sgml18
-rw-r--r--zh_TW.Big5/books/handbook/printing/chapter.sgml786
-rw-r--r--zh_TW.Big5/books/handbook/security/chapter.sgml516
-rw-r--r--zh_TW.Big5/books/handbook/serialcomms/chapter.sgml620
-rw-r--r--zh_TW.Big5/books/handbook/txtfiles.ent8
-rw-r--r--zh_TW.Big5/books/handbook/users/chapter.sgml26
-rw-r--r--zh_TW.Big5/books/handbook/vinum/chapter.sgml74
-rw-r--r--zh_TW.Big5/books/handbook/virtualization/chapter.sgml52
-rw-r--r--zh_TW.Big5/books/handbook/x11/chapter.sgml74
-rw-r--r--zh_TW.Big5/books/porters-handbook/Makefile4
-rw-r--r--zh_TW.Big5/books/porters-handbook/book.sgml64
-rw-r--r--zh_TW.Big5/htdocs/Makefile2
-rw-r--r--zh_TW.Big5/htdocs/about.sgml6
-rw-r--r--zh_TW.Big5/htdocs/availability.sgml2
-rw-r--r--zh_TW.Big5/htdocs/docs/books.sgml4
-rw-r--r--zh_TW.Big5/htdocs/docs/webresources.sgml2
-rw-r--r--zh_TW.Big5/htdocs/logo.sgml4
-rw-r--r--zh_TW.Big5/share/sgml/authors.ent2
-rw-r--r--zh_TW.Big5/share/sgml/catalog2
-rw-r--r--zh_TW.Big5/share/sgml/freebsd.dsl8
-rw-r--r--zh_TW.Big5/share/sgml/glossary.ent8
-rw-r--r--zh_TW.Big5/share/sgml/l10n.ent2
-rw-r--r--zh_TW.Big5/share/sgml/libcommon.xsl4
-rw-r--r--zh_TW.Big5/share/sgml/navibar.l10n.ent4
-rw-r--r--zh_TW.Big5/share/sgml/news.xml58
-rw-r--r--zh_TW.Big5/share/sgml/trademarks.ent4
1363 files changed, 63208 insertions, 63208 deletions
diff --git a/da_DK.ISO8859-1/articles/Makefile.inc b/da_DK.ISO8859-1/articles/Makefile.inc
index 3267ee2b8b..1c1f34974a 100644
--- a/da_DK.ISO8859-1/articles/Makefile.inc
+++ b/da_DK.ISO8859-1/articles/Makefile.inc
@@ -1,4 +1,4 @@
-#
+#
# $FreeBSD$
#
diff --git a/da_DK.ISO8859-1/share/sgml/catalog b/da_DK.ISO8859-1/share/sgml/catalog
index 5bc9bbf97b..b44849dbf5 100644
--- a/da_DK.ISO8859-1/share/sgml/catalog
+++ b/da_DK.ISO8859-1/share/sgml/catalog
@@ -1,6 +1,6 @@
-- ...................................................................... --
-- FreeBSD SGML Public Identifiers ...................................... --
-
+
-- $FreeBSD$
--
diff --git a/da_DK.ISO8859-1/share/sgml/disclaimer.sgml b/da_DK.ISO8859-1/share/sgml/disclaimer.sgml
index b14f4b6c2b..634fd29874 100644
--- a/da_DK.ISO8859-1/share/sgml/disclaimer.sgml
+++ b/da_DK.ISO8859-1/share/sgml/disclaimer.sgml
@@ -1,22 +1,22 @@
-<!--
+<!--
The FreeBSD Documentation Project
The FreeBSD Danish Documentation Project
$FreeBSD$
-->
- <para>DENNE DOKUMENTATION ER FORSYNET AF FREEBSD DOKUMENTATIONS
- PROJEKTET "SOM DET ER" OG UDEN NOGLE UDTRYKTE ELLER ANTYDEDE
- GARANTIER, INKLUDERENDE MEN IKKE BEGRNSET TIL: ANTYDEDE GARANTIER
- FOR SALGBARHED OG EGNETHED FOR ET SPECIFIKT FORML. UNDER INGEN
+ <para>DENNE DOKUMENTATION ER FORSYNET AF FREEBSD DOKUMENTATIONS
+ PROJEKTET "SOM DET ER" OG UDEN NOGLE UDTRYKTE ELLER ANTYDEDE
+ GARANTIER, INKLUDERENDE MEN IKKE BEGRNSET TIL: ANTYDEDE GARANTIER
+ FOR SALGBARHED OG EGNETHED FOR ET SPECIFIKT FORML. UNDER INGEN
OMSTNDIGHEDER SKAL FREEBSD DOKUMENTATIONS PROJEKTET VRE
HFTENDE, FOR NOGLE DIREKTE, INDIREKTE, TILFLDIGE,
SPECIELLE, EKSEMPLARISKE, ELLER FLGENDE SKADER (INKLUDERENDE,
- MEN IKKE BEGRNSET TIL:
- FREMSKAFFELSE AF ERSTATNINGS VARER ELLER SERVICEYELSER; TAB AF
- BRUGBARHED, DATA, ELLER UDBYTTE; ELLER AFBRYDELSE AF FORRETNING)
- HVORDAN END DEN ER OPSTET OG UNDER EN HVILKEN SOM HELST TEORI
- OM ANSVARLIGHED, HVAD ENTEN DET ER I KONTRAKT, STRIKS ANSVARLIGHED
+ MEN IKKE BEGRNSET TIL:
+ FREMSKAFFELSE AF ERSTATNINGS VARER ELLER SERVICEYELSER; TAB AF
+ BRUGBARHED, DATA, ELLER UDBYTTE; ELLER AFBRYDELSE AF FORRETNING)
+ HVORDAN END DEN ER OPSTET OG UNDER EN HVILKEN SOM HELST TEORI
+ OM ANSVARLIGHED, HVAD ENTEN DET ER I KONTRAKT, STRIKS ANSVARLIGHED
ELLER TORT (INKLUDERENDE FORSMMELIGHED ELLER P ANDEN VIS)
OPSTENDE P NOGEN MDE UD AF BRUGEN AF DENNE
DOKUMENTATION, SELV HVIS GJORT OPMRKSOM P MULIGHEDEN FOR
diff --git a/da_DK.ISO8859-1/share/sgml/freebsd.dsl b/da_DK.ISO8859-1/share/sgml/freebsd.dsl
index d2dfe66fbc..be8e51cbc7 100644
--- a/da_DK.ISO8859-1/share/sgml/freebsd.dsl
+++ b/da_DK.ISO8859-1/share/sgml/freebsd.dsl
@@ -3,7 +3,7 @@
<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
<!ENTITY freebsd.dsl PUBLIC "-//FreeBSD//DOCUMENT DocBook Language Neutral Stylesheet//EN" CDATA DSSSL>
-<!ENTITY % output.html "IGNORE">
+<!ENTITY % output.html "IGNORE">
<!ENTITY % output.print "IGNORE">
]>
@@ -11,8 +11,8 @@
<style-specification use="docbook">
<style-specification-body>
<!-- HTML only .................................................... -->
-
- <![ %output.html; [
+
+ <![ %output.html; [
(define ($email-footer$)
(make sequence
@@ -26,7 +26,7 @@
(literal ".")))
(make element gi: "p"
attributes: (list (list "align" "center"))
- (make element gi: "small"
+ (make element gi: "small"
(literal "For sprgsml om FreeBSD, ls ")
(create-link
(list (list "HREF" "http://www.FreeBSD.org/docs.html"))
diff --git a/de_DE.ISO8859-1/articles/contributing-ports/article.sgml b/de_DE.ISO8859-1/articles/contributing-ports/article.sgml
index ec7e6520bd..df03c4d72d 100644
--- a/de_DE.ISO8859-1/articles/contributing-ports/article.sgml
+++ b/de_DE.ISO8859-1/articles/contributing-ports/article.sgml
@@ -648,7 +648,7 @@
zu antworten, selbst wenn Sie nur mitteilen knnen,
dass Sie noch etwas Zeit brauchen, bevor Sie den PR
bearbeiten knnen.</para>
-
+
<para>Sollten Sie nicht innerhalb von 14 Tagen geantwortet haben,
darf jeder Committer via <literal>maintainer-timeout</literal>
auf einen PR, den Sie nicht beantwortet haben, reagieren.</para>
diff --git a/de_DE.ISO8859-1/articles/contributing/article.sgml b/de_DE.ISO8859-1/articles/contributing/article.sgml
index 86bf3ab25e..c286b30eab 100644
--- a/de_DE.ISO8859-1/articles/contributing/article.sgml
+++ b/de_DE.ISO8859-1/articles/contributing/article.sgml
@@ -187,7 +187,7 @@
<listitem>
<para>Stellen Sie sicher, dass der Code in
- <filename class="directory">src/contrib</filename> aktuell
+ <filename class="directory">src/contrib</filename> aktuell
ist.</para>
</listitem>
@@ -205,10 +205,10 @@
</listitem>
<listitem>
- <para>Wenn Sie einen Port beigetragen und dabei irgendwelche
- &os;-spezifischen nderungen gettigt haben, senden Sie
+ <para>Wenn Sie einen Port beigetragen und dabei irgendwelche
+ &os;-spezifischen nderungen gettigt haben, senden Sie
Ihre Patches an die ursprnglichen Autoren (das wird ihr Leben
- einfacher machen, wenn die nchste Version des Ports
+ einfacher machen, wenn die nchste Version des Ports
erscheint).</para>
</listitem>
diff --git a/de_DE.ISO8859-1/articles/solid-state/Makefile b/de_DE.ISO8859-1/articles/solid-state/Makefile
index db718c4ce4..c56ffa7d02 100644
--- a/de_DE.ISO8859-1/articles/solid-state/Makefile
+++ b/de_DE.ISO8859-1/articles/solid-state/Makefile
@@ -1,7 +1,7 @@
#
# The FreeBSD Documentation Project
# The FreeBSD German Documentation Project
-#
+#
# $FreeBSD$
# $FreeBSDde: de-docproj/articles/solid-state/Makefile,v 1.2 2011/12/31 12:33:27 bcr Exp $
# basiert auf: 1.5
diff --git a/de_DE.ISO8859-1/books/developers-handbook/book.sgml b/de_DE.ISO8859-1/books/developers-handbook/book.sgml
index 2958788ffc..a2ea1935a8 100644
--- a/de_DE.ISO8859-1/books/developers-handbook/book.sgml
+++ b/de_DE.ISO8859-1/books/developers-handbook/book.sgml
@@ -34,14 +34,14 @@
<year>2007</year>
<year>2008</year>
<year>2009</year>
- <year>2010</year>
+ <year>2010</year>
<holder>The FreeBSD Documentation Project</holder>
</copyright>
<copyright>
<year>2008</year>
<year>2009</year>
- <year>2010</year>
+ <year>2010</year>
<holder>The FreeBSD German Documentation Project</holder>
</copyright>
diff --git a/de_DE.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml b/de_DE.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
index f88fd20e41..4eed26cb93 100644
--- a/de_DE.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
+++ b/de_DE.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
@@ -78,10 +78,10 @@
den gesamten Inhalt des physischen Speichers beinhalten, Miniauszge
(minidumps), die nur die gerade verwendeten Speicherseiten des Kernels
enthalten (&os;&nbsp;6.2 und hhere Versionen) und Textauszge
- (textdumps), welche geskriptete oder Debugger-Ausgaben enthalten
+ (textdumps), welche geskriptete oder Debugger-Ausgaben enthalten
(&os;&nbsp;7.1 und hher). Miniauszge sind der Standardtyp
der Abzge seit &os;&nbsp;7.0 und fangen in den meisten Fllen
- alle ntigen Informationen ein, die in einem kompletten
+ alle ntigen Informationen ein, die in einem kompletten
Kernel-Speicherabzug enthalten sind, da die meisten Probleme nur durch
den Zustand des Kernels isoliert werden knnen.</para>
@@ -570,7 +570,7 @@
Befehl ab:</para>
<screen>&prompt.root; <userinput>sysctl debug.kdb.enter=1</userinput></screen>
-
+
<note>
<para>Um eine schnelle Panic zu erzwingen, geben Sie das folgende
Kommando ein:</para>
diff --git a/de_DE.ISO8859-1/books/developers-handbook/policies/chapter.sgml b/de_DE.ISO8859-1/books/developers-handbook/policies/chapter.sgml
index db6a35eeee..c86a2892d5 100644
--- a/de_DE.ISO8859-1/books/developers-handbook/policies/chapter.sgml
+++ b/de_DE.ISO8859-1/books/developers-handbook/policies/chapter.sgml
@@ -40,7 +40,7 @@
<sect1 id="policies-style">
<title>Stil-Richtlinien</title>
<indexterm><primary>style</primary></indexterm>
-
+
<para>Ein konsistenter Code-Stil ist extrem wichtig, besonders
in einem so grossen Projekt wie &os;. Der Code sollte dem
&os; Code-Stil entsprechen, welcher in &man.style.9; und
@@ -51,7 +51,7 @@
<title><makevar>MAINTAINER</makevar> eines Makefiles</title>
<indexterm><primary>Ports-Maintainer</primary></indexterm>
- <para>Wenn ein bestimmter Bereich der &os;
+ <para>Wenn ein bestimmter Bereich der &os;
<filename>src/</filename>-Distribution von einer Person oder Gruppe
gepflegt wird, kann dies durch einen Eintrag in die Datei
<filename>src/MAINTAINERS</filename> der ffentlichkeit
@@ -59,7 +59,7 @@
knnen ihre Verantwortung ber den Port durch einen Eintrag in
die <makevar>MAINTAINER</makevar>-Zeile im <filename>Makefile</filename>
des Ports der Welt mitteilen.</para>
-
+
<programlisting><makevar>MAINTAINER</makevar>= <replaceable>email-addresses</replaceable></programlisting>
<tip>
@@ -68,10 +68,10 @@
sind, wer der Maintainer ist, sehen Sie sich die Commit-Historie des
betreffenden Ports an. Es ist recht hufig der Fall, dass ein
Maintainer nicht explizit aufgefhrt ist, aber trotzdem diejenigen
- Personen, die den Port seit den letzten paar Jahren aktiv betreuen,
+ Personen, die den Port seit den letzten paar Jahren aktiv betreuen,
daran interessiert sind, nderungen zu begutachten. Selbst wenn
dies nicht explizit in der Dokumentation oder im Quellcode erwhnt
- ist, wird es trotzdem als hfliche Geste angesehen, wenn man
+ ist, wird es trotzdem als hfliche Geste angesehen, wenn man
nach einer berprfung der eigenen nderungen
fragt.</para>
</tip>
@@ -123,7 +123,7 @@
<author>
<firstname>Gavin</firstname>
<surname>Atkinson</surname>
- </author>
+ </author>
</authorgroup>
<!-- June 1996 -->
</sect1info>
@@ -142,7 +142,7 @@
<para>ber die Jahre wurden verschiedene Methoden genutzt,
um solche Software zu verwalten, und jede hat Vor-
- wie auch Nachteile. So hat sich kein eindeutiger Gewinner
+ wie auch Nachteile. So hat sich kein eindeutiger Gewinner
herauskristallisiert.</para>
<para>Es wurde viel ber diesen Umstand diskutiert und
@@ -155,7 +155,7 @@
einfach Diffs bezglich der
<quote>offiziellen</quote> Quelltext-Versionen erzeugen kann
(auch ohne direkten Repository-Zugang). Dies wird es deutlich
- vereinfachen, nderungen an die Hauptentwickler
+ vereinfachen, nderungen an die Hauptentwickler
zurckflieen zu lassen.</para>
<para>Letztendlich kommt es jedoch auf die Menschen an, welche die
@@ -181,7 +181,7 @@
</note>
<sect2 id="vendor-imports-cvs">
-
+
<title>Herstellerimports mit CVS</title>
<para>Das <application>file</application>-Werkzeug soll als Beispiel
@@ -276,19 +276,19 @@
<para>Ein Beispielinhalt von
<filename>src/contrib/groff/FREEBSD-upgrade</filename> ist hier
aufgelistet:</para>
-
+
<programlisting>&dollar;FreeBSD: src/contrib/groff/FREEBSD-upgrade,v 1.5.12.1 2005/11/15 22:06:18 ru Exp $
This directory contains virgin sources of the original distribution files
on a "vendor" branch. Do not, under any circumstances, attempt to upgrade
-the files in this directory via patches and a cvs commit.
+the files in this directory via patches and a cvs commit.
To upgrade to a newer version of groff, when it is available:
1. Unpack the new version into an empty directory.
[Do not make ANY changes to the files.]
2. Use the command:
- cvs import -m 'Virgin import of FSF groff v&lt;version&gt;' \
+ cvs import -m 'Virgin import of FSF groff v&lt;version&gt;' \
src/contrib/groff FSF v&lt;version&gt;
For example, to do the import of version 1.19.2, I typed:
@@ -340,7 +340,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
Import hinzufgen.</para>
</note>
</sect2>
-
+
<sect2 id="vendor-import-svn">
<sect2info>
<authorgroup>
@@ -351,7 +351,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
</author>
</authorgroup>
</sect2info>
-
+
<title>Herstellerimports mit SVN</title>
<para>Dieser Abschnitt beschreibt die Prozedur fr Herstellerimports
@@ -360,18 +360,18 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
<procedure>
<step>
<title>Vorbereiten des Quellbaums</title>
-
+
<para>Wenn dies Ihr erster Import nach dem Wechsel zu
<acronym>SVN</acronym> ist, sollen Sie den Herstellerbaum
aufrumen, verflachen und die Merge-Historie in den Hauptzweig
vorbereiten. Falls das nicht Ihr erster Import ist, knnen
Sie diesen Schritt ohne Probleme berspringen.</para>
-
+
<para>Whrend der Konvertierung von <acronym>CVS</acronym> zu
<acronym>SVN</acronym> wurden Herstellerzweige mit der gleichen
Struktur wie der Hauptzweig importiert. Beispielsweise wurden die
<application>foo</application> Herstellerquellen in
- <filename>vendor/<replaceable>foo</replaceable>/dist/contrib/<replaceable>foo</replaceable></filename>
+ <filename>vendor/<replaceable>foo</replaceable>/dist/contrib/<replaceable>foo</replaceable></filename>
abgelegt, jedoch ist dies unpraktisch und zwecklos. Was wir wirklich
wollen, ist dass die Herstellerquellen direkt in
<filename>vendor/<replaceable>foo</replaceable>/dist</filename>
@@ -424,20 +424,20 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
<step>
<title>Neue Quellen importieren</title>
-
+
<para>Bereiten Sie einen kompletten, sauberen Baum mit
Herstellerquellen vor. Mit <acronym>SVN</acronym> knnen wir
eine komplette Distribution in dem Herstellerzweig aufbewahren, ohne
den Hauptzweig aufzublhen. Importieren Sie alles, aber mergen
Sie nur das, was wirklich bentigt wird.</para>
-
+
<para>Beachten Sie, dass Sie alle Dateien, die seit dem letzten
Herstellerimport hinzugefgt wurden, auch einbeziehen und
diejenigen, welche entfernt wurden, auch lschen
mssen. Um dies zu bewerkstelligen, sollten Sie sortierte
Listen der Bestandteile des Herstellerbaums und von den Quellen,
Sie die vorhaben zu importieren, vorbereiten:</para>
-
+
<screen>&prompt.user; <userinput><command>cd</command> <filename>vendor/<replaceable>foo</replaceable>/dist</filename></userinput>
&prompt.user; <userinput><command>svn list</command> <option>-R</option> | <command>grep</command> <option>-v</option> '/$' | <command>sort</command> > <filename>../<replaceable>old</replaceable></filename></userinput>
&prompt.user; <userinput><command>cd</command> <filename>../<replaceable>foo-9.9</replaceable></filename></userinput>
@@ -446,17 +446,17 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
<para>Mit diesen beiden Dateien, wird Ihnen das folgende Kommando alle
Dateien auflisten, die entfernt wurden (nur die Dateien in
<filename><replaceable>old</replaceable></filename>):</para>
-
+
<screen>&prompt.user; <userinput><command>comm <option>-23</option> <filename>../<replaceable>old</replaceable></filename> <filename>../<replaceable>new</replaceable></filename></command></userinput></screen>
-
+
<para>Der folgende Befehl wird die hinzugefgten Dateien auflisten
(nur diejenigen Dateien in
<filename><replaceable>new</replaceable></filename>):</para>
-
+
<screen>&prompt.user; <userinput><command>comm <option>-13</option> <filename>../<replaceable>old</replaceable></filename> <filename>../<replaceable>new</replaceable></filename></command></userinput></screen>
-
+
<para>Wir fhren dies nun zusammen:</para>
-
+
<screen>&prompt.user; <userinput><command>cd</command> <filename class="directory">vendor/<replaceable>foo</replaceable>/<replaceable>foo-9.9</replaceable></filename></userinput>
&prompt.user; <userinput><command>tar</command> cf - <filename>.</filename> | <command>tar</command> xf - <option>-C</option> <filename>../dist</filename></userinput>
&prompt.user; <userinput><command>cd</command> <filename class="directory">../dist</filename></userinput>
@@ -472,26 +472,26 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
</warning>
<para>Prfen Sie die Eigenschaften jeder neuen Datei:</para>
-
+
<itemizedlist>
<listitem>
<para>Alle Textdateien sollten <literal>svn:eol-style</literal> auf
den Wert <literal>native</literal> gesetzt haben.</para>
</listitem>
-
+
<listitem>
<para>Alle Binrdateien sollten
<literal>svn:mime-type</literal> auf
<literal>application/octet-stream</literal> gesetzt haben,
ausser es existiert ein passenderer Medientyp.</para>
</listitem>
-
+
<listitem>
<para>Ausfhrbare Dateien sollten
<literal>svn:executable</literal> auf <literal>*</literal>
gesetzt haben.</para>
</listitem>
-
+
<listitem>
<para>Es sollten keine anderen Eigenschaften auf den Dateien im
Baum gesetzt sein.</para>
@@ -507,7 +507,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
<para>Sobald Sie den die neue Release-Version des Herstellers
committed haben, sollten Sie Ihn fr zuknftige Referenzen
- taggen. Die beste und schnellste Methode ist, dies direkt im
+ taggen. Die beste und schnellste Methode ist, dies direkt im
Repository zu tun:</para>
<screen>&prompt.user; <userinput><command>svn copy</command> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/<replaceable>9.9</replaceable></filename></userinput></screen>
@@ -523,16 +523,16 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
entfernen.</para>
</note>
</step>
-
+
<step>
<title>Mit <emphasis>-HEAD</emphasis> mergen</title>
-
+
<para>Nachdem Sie Ihren Import vorbereitet haben, wird es Zeit zu
mergen. Die Option <option>--accept=postpone</option> weist
<acronym>SVN</acronym> an, noch keine merge-Konflikte
aufzulsen, weil wir uns um diese manuell kmmern
werden:</para>
-
+
<screen>&prompt.user; <userinput><command>cd</command> <filename class="directory">head/contrib/<replaceable>foo</replaceable></filename></userinput>
&prompt.user; <userinput><command>svn update</command></userinput>
&prompt.user; <userinput><command>svn merge</command> <option>--accept=postpone</option> <filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename></userinput></screen>
@@ -542,13 +542,13 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
wurden, auch sauber im Hauptzweig hinzugefgt bzw. gelscht
wurden. Es ist immer ratsam, diese Unterschiede gegen den
Herstellerbaum zu prfen:</para>
-
+
<screen>&prompt.user; <userinput><command>svn diff</command> <option>--no-diff-deleted</option> <option>--old=</option><filename><replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/dist</filename> <option>--new=</option><filename>.</filename></userinput></screen>
-
+
<para>Die Option <option>--no-diff-deleted</option> weist
<acronym>SVN</acronym> an, keine Dateien zu prfen, die sich
zwar im Herstellerbaum, aber nicht im Hauptzweig befinden.</para>
-
+
<note>
<para>Bei <acronym>SVN</acronym> gibt es das Konzept von innerhalb
und ausserhalb des Herstellerbaums nicht. Wenn eine Datei, die
@@ -557,7 +557,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
Versionstags, damit diese nicht lnger in den diffs gegen
den Herstellerbaum erscheinen.</para>
</note>
-
+
<para>Wenn irgendwelche nderungen notwendig sind, um die Welt
mit den neuen Quellen zu bauen, machen Sie diese jetzt und testen
Sie diese bis Sie sicher sind, dass alles korrekt gebaut wird und
@@ -566,7 +566,7 @@ ru@FreeBSD.org - 20 October 2005</programlisting>
<step>
<title>Commit</title>
-
+
<para>Nun sind Sie bereit fr den Commit. Stellen Sie sicher,
dass Sie alles in einem einzigen Schritt durchfhren.
Idealerweise sollten Sie alle diese Schritte in einem sauberen Baum
diff --git a/de_DE.ISO8859-1/books/developers-handbook/secure/chapter.sgml b/de_DE.ISO8859-1/books/developers-handbook/secure/chapter.sgml
index c4e75cf25e..367f4e4458 100644
--- a/de_DE.ISO8859-1/books/developers-handbook/secure/chapter.sgml
+++ b/de_DE.ISO8859-1/books/developers-handbook/secure/chapter.sgml
@@ -75,7 +75,7 @@
<indexterm><primary>Morris Internetwurm</primary></indexterm>
funktioniert der gleiche grundlegende Angriff noch heute. Die bei weitem
- hufigste Form eines Puffer-berlauf-Angriffs basiert darauf,
+ hufigste Form eines Puffer-berlauf-Angriffs basiert darauf,
den Stack zu korrumpieren.</para>
<indexterm><primary>Stack</primary></indexterm>
@@ -309,7 +309,7 @@ return 0;
Quelltext, der allgemein verwendet wird und blind Speicher
umherkopiert, ohne eine der gerade besprochenen Funktionen,
die Begrenzungen untersttzen, zu verwenden.
- Glcklicherweise gibt es einen Weg, um solche Angriffe zu
+ Glcklicherweise gibt es einen Weg, um solche Angriffe zu
verhindern - berprfung der Grenzen zur Laufzeit, die in
verschiedenen C/C++ Compilern eingebaut ist.</para>
@@ -319,19 +319,19 @@ return 0;
<para>ProPolice ist eine solche Compiler-Eigenschaft und ist in den
&man.gcc.1; Versionen 4.1 und hher integriert. Es ersetzt und
- erweitert die &man.gcc.1; StackGuard-Erweiterung von
+ erweitert die &man.gcc.1; StackGuard-Erweiterung von
frher.</para>
-
- <para>ProPolice schtzt gegen stackbasierte
+
+ <para>ProPolice schtzt gegen stackbasierte
Pufferberlufe und andere Angriffe durch das Ablegen von
Pseudo-Zufallszahlen in Schlsselbereichen des Stacks bevor es
- irgendwelche Funktionen aufruft. Wenn eine Funktion beendet wird,
+ irgendwelche Funktionen aufruft. Wenn eine Funktion beendet wird,
werden diese <quote>Kanarienvgel</quote> berprft
und wenn festgestellt wird, dass diese verndert wurden wird das
Programm sofort abgebrochen. Dadurch wird jeglicher Versuch, die
Rcksprungadresse oder andere Variablen, die auf dem Stack
gespeichert werden, durch die Ausfhrung von Schadcode zu
- manipulieren, nicht funktionieren, da der Angreifer auch die
+ manipulieren, nicht funktionieren, da der Angreifer auch die
Pseudo-Zufallszahlen unberhrt lassen msste.</para>
<indexterm><primary>Puffer-berlauf</primary></indexterm>
diff --git a/de_DE.ISO8859-1/books/developers-handbook/tools/chapter.sgml b/de_DE.ISO8859-1/books/developers-handbook/tools/chapter.sgml
index 44397a3bfc..f25a6c908c 100644
--- a/de_DE.ISO8859-1/books/developers-handbook/tools/chapter.sgml
+++ b/de_DE.ISO8859-1/books/developers-handbook/tools/chapter.sgml
@@ -54,12 +54,12 @@
<title>Zusammenfassung</title>
<para>FreeBSD bietet eine exzellente Entwicklungsumgebung.
- Compiler fr C und C++, sowie ein Assembler sind im
+ Compiler fr C und C++, sowie ein Assembler sind im
Basissystem enthalten. Natrlich finden
- sich auch klassische &unix;-Werkzeuge wie <command>sed</command>
+ sich auch klassische &unix;-Werkzeuge wie <command>sed</command>
und <command>awk</command>. Sollte das nicht genug sein, finden sich
zahlreiche weitere Compiler und Interpreter in der Ports-Sammlung.
- Der folgende Abschnitt, <link
+ Der folgende Abschnitt, <link
linkend="tools-programming">Einfhrung in die Programmierung</link>,
zhlt ein paar der verfgbaren Optionen auf. FreeBSD ist
kompatibel zu vielen Standards wie <acronym>&posix;</acronym>
@@ -167,7 +167,7 @@
fr viele Programmierer die erste
Programmiersprache. <acronym>BASIC</acronym> ist auch
die Grundlage fr Visual Basic.</para>
-
+
<para>Der Bywater Basic Interpreter findet sich in der
Ports-Sammlung unter <filename
role="package">lang/bwbasic</filename> und Phil
@@ -1631,7 +1631,7 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
<para>Falls Sie den textbasierten Kommandozeilen-Stil
abstoend finden gibt es ein graphisches Front-End
- dafr (<filename
+ dafr (<filename
role="package">devel/xxgdb</filename>) in der Ports-Sammlung.</para>
<para>Dieser Abschnitt ist als Einfhrung in die
@@ -1659,9 +1659,9 @@ DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz
<para>Geben Sie in der Eingabeaufforderung des
<command>gdb</command> <userinput>break main</userinput> ein.
Dies weist den Debugger an, dass Sie nicht daran interessiert sind,
- den einleitenden Schritten beim Programmstart zuzusehen und dass
- am Anfang Ihres Codes die Ausfhrung beginnen soll. Geben Sie
- nun <userinput>run</userinput> ein, um das Programm zu starten -
+ den einleitenden Schritten beim Programmstart zuzusehen und dass
+ am Anfang Ihres Codes die Ausfhrung beginnen soll. Geben Sie
+ nun <userinput>run</userinput> ein, um das Programm zu starten -
es wird starten und beim Aufruf von <function>main()</function> vom
Debugger angehalten werden. (Falls Sie sich jemals gewundert haben von
welcher Stelle <function>main()</function> aufgerufen wird, dann
@@ -1994,7 +1994,7 @@ else if (pid == 0) { /* child */
<para>Und zweifelsfrei viele weitere Punkte, die ich
bersehen habe.</para>
- <para>Emacs kann unter &os; ber den <filename
+ <para>Emacs kann unter &os; ber den <filename
role="package">editors/emacs</filename> Port installiert werden.</para>
<para>Sobald er installiert ist starten Sie ihn, und geben
diff --git a/de_DE.ISO8859-1/books/handbook/bsdinstall/chapter.sgml b/de_DE.ISO8859-1/books/handbook/bsdinstall/chapter.sgml
index 96dba4fb4a..652296a845 100644
--- a/de_DE.ISO8859-1/books/handbook/bsdinstall/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/bsdinstall/chapter.sgml
@@ -43,7 +43,7 @@
<surname>Reuschling</surname>
<contrib>bersetzt von </contrib>
</author>
- </authorgroup>
+ </authorgroup>
</chapterinfo>
<title>&os;&nbsp;9.<replaceable>x</replaceable> (und neuer)
@@ -262,7 +262,7 @@
mag etwas unhandlich erscheinen und das ist auch der
Fall.</para>
- <para>Die <firstterm>GUID-Partitionstabelle</firstterm> (<acronym
+ <para>Die <firstterm>GUID-Partitionstabelle</firstterm> (<acronym
role="GUID Partition Table">GPT</acronym>) ist eine neuere und
einfachere Methode zur Partition einer Festplatte. <acronym
role="GUID Partition Table">GPT</acronym> ist weitaus flexibler
@@ -317,14 +317,14 @@
<para>Die Vernderung der Grsse von
&microsoft;&nbsp;Vista-Partitionen kann schwierig sein. Eine
- Vista Installations-CD-ROM kann hilfreich sein, wenn eine solche
+ Vista Installations-CD-ROM kann hilfreich sein, wenn eine solche
Aktion versucht wird.</para>
<example>
<title>Eine existierende Partition verndern</title>
<para>Ein &windows;-Computer besitzt eine einzelne 40&nbsp;GB
- Platte, die in zwei 20&nbsp;GB Partitionen aufgeteilt wurde.
+ Platte, die in zwei 20&nbsp;GB Partitionen aufgeteilt wurde.
&windows; nennt diese <devicename>C:</devicename> und
<devicename>D:</devicename>. Die <devicename>C:</devicename>
Partition enthlt 10&nbsp;GB und the
@@ -527,10 +527,10 @@
<warning>
<para>Das Beispiel unten verwendet <filename
- class="devicefile">/dev/da0</filename> als das
+ class="devicefile">/dev/da0</filename> als das
Zielgert, auf welches das Image geschrieben werden
- soll. Seien Sie vorsichtig, dass das richtige Gert
- als das Ausgabe benutzt wird oder Sie zerstren
+ soll. Seien Sie vorsichtig, dass das richtige Gert
+ als das Ausgabe benutzt wird oder Sie zerstren
wichtige Daten.</para>
</warning>
@@ -538,7 +538,7 @@
<title>Das Image mit &man.dd.1; schreiben</title>
<para>Die <filename>.img</filename>-Datei ist
- <emphasis>keine</emphasis> gewhnliche Datei. Es ist
+ <emphasis>keine</emphasis> gewhnliche Datei. Es ist
ein <emphasis>Image</emphasis> des kompletten
spteren Inhalts des USB-Sticks. Es kann
<emphasis>nicht</emphasis> einfach wie eine
@@ -566,7 +566,7 @@
<para><application>Image Writer fr
&windows;</application> ist eine frei verfgbare
- Anwendung, welche eine Imagedatei korrekt auf einen
+ Anwendung, welche eine Imagedatei korrekt auf einen
SB-Stick schreiben kann. Laden Sie diese von <ulink
url="https://launchpad.net/win32-image-writer/"></ulink>
herunter und entpacken Sie sie in einen Ordner.</para>
@@ -585,7 +585,7 @@
Sie auf das Ordnersymbol und whlen Sie das Image
aus, welches auf den USB-Stick geschrieben werden soll.
Um den Image-Dateinamen zu akzeptieren, klicken Sie auf
- <guibutton>[&nbsp;Save&nbsp;]</guibutton>.
+ <guibutton>[&nbsp;Save&nbsp;]</guibutton>.
berprfen Sie erneut, ob alles stimmt und dass
keine Ordner auf dem USB-Stick in anderen Fenstern
geffnet sind. Sobald alles bereit ist, klicken Sie
@@ -610,7 +610,7 @@
<title>Die Installation starten</title>
<important>
- <para>Es werden durch die Installation keine nderungen an
+ <para>Es werden durch die Installation keine nderungen an
Ihren Festplatten durchgefhrt, so lange Sie nicht die
folgende Meldung sehen:</para>
@@ -795,7 +795,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
<command>BREAK</command>-Kommando (indem Sie z.B.
<command>~#</command> in &man.tip.1; oder &man.cu.1; absetzen)
ber die serielle Konsole senden, um zur <acronym
- role="Programmable Read Only Memory">PROM</acronym>
+ role="Programmable Read Only Memory">PROM</acronym>
Befehlszeile zu gelangen. Es sieht dann so aus:</para>
<screenco>
@@ -835,7 +835,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
<para>Um diesen Puffer anzusehen, drcken Sie
<keycap>Scroll Lock</keycap>. Das bewirkt, dass Sie die
- Bildschirmanzeige hoch und runter bewegen (scrollen) knnen.
+ Bildschirmanzeige hoch und runter bewegen (scrollen) knnen.
Sie knnen dann die Pfeiltasten oder <keycap>PageUp</keycap>
und <keycap>PageDown</keycap> benutzen, um die Meldungen zu
sehen. Drcken Sie <keycap>Scroll Lock</keycap> erneut, um
@@ -1312,7 +1312,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<para>Nachdem das Partitionslayout nun erstellt wurde, sollten Sie
es danach noch einmal auf Korrektheit prfen. Sollten Sie
einen Fehler gemacht haben, knnen Sie durch Auswahl von
- <guibutton>[&nbsp;Revert&nbsp;]</guibutton> wieder die
+ <guibutton>[&nbsp;Revert&nbsp;]</guibutton> wieder die
ursprnglichen Partitionen setzen oder durch
<guibutton>[&nbsp;Auto&nbsp;]</guibutton> die automatischen
&os; Partitionen wiederherstellen. Partitionen knnen
@@ -1346,7 +1346,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
</mediaobject>
</figure>
- <para>Durch hervorheben einer Platte (in diesem Fall
+ <para>Durch hervorheben einer Platte (in diesem Fall
<devicename>ada0</devicename>) und die Auswahl von
<guibutton>[&nbsp;Create&nbsp;]</guibutton>, wird ein Men
zur Wahl des <firstterm>Partitionierungsschemas</firstterm>
@@ -1557,7 +1557,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<entry><filename>/</filename></entry>
<entry><literal>bsprootfs</literal></entry>
</row>
-
+
<row>
<entry><literal>freebsd-swap</literal></entry>
<entry><literal>4G</literal></entry>
@@ -1615,7 +1615,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
<para>Whlen Sie <guibutton>[&nbsp;Commit&nbsp;]</guibutton> und
drcken Sie <keycap>Enter</keycap>, um fortzufahren. Fall noch
- nderungen zu machen sind, whlen Sie
+ nderungen zu machen sind, whlen Sie
<guibutton>[&nbsp;Back&nbsp;]</guibutton>, um zum Partitionseditor
zurck zu gelangen. Mittels
<guibutton>[&nbsp;Revert&nbsp;&amp;&nbsp;Exit&nbsp;]</guibutton>
@@ -2262,7 +2262,7 @@ Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...</screen>
</listitem>
<listitem>
- <para><literal>Home directory permissions</literal> -
+ <para><literal>Home directory permissions</literal> -
Zugriffsrechte auf das Heimatverzeichnis des Benutzers. Die
Vorgabe ist normalerweise die passende.</para>
</listitem>
@@ -2674,7 +2674,7 @@ login:</screen>
<primary>installation</primary>
<secondary>troubleshooting</secondary>
</indexterm>
-
+
<para>Der folgende Abschnitt behandelt einfache Fehlerbehebungen
fr die Installation, wie beispielsweise hufig
auftretende Fehler, die von Anwendern berichtet wurden.</para>
@@ -2755,7 +2755,7 @@ login:</screen>
<screen><userinput>set hint.acpi.0.disabled="1"</userinput></screen>
<para>Dies wird nach jedem Neustart des Systems wieder
- zurckgesetzt, also ist es notwendig, die Zeile
+ zurckgesetzt, also ist es notwendig, die Zeile
<literal>hint.acpi.0.disabled="1"</literal> zu der Datei
<filename>/boot/loader.conf</filename> hinzuzufgen.
Weitere Informationen ber den Bootloader lassen sich
diff --git a/de_DE.ISO8859-1/books/handbook/config/chapter.sgml b/de_DE.ISO8859-1/books/handbook/config/chapter.sgml
index 3f22413913..67d6b05597 100644
--- a/de_DE.ISO8859-1/books/handbook/config/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/config/chapter.sgml
@@ -2634,7 +2634,7 @@ kern.maxvnodes: 100000</screen>
Kernel-Konfigurationsdatei enthalten ist:</para>
<programlisting>device md</programlisting>
-
+
<para>Informationen, wie man einen eigenen Kernel erstellen kann,
erhalten Sie in <xref linkend="kernelconfig"/>.</para>
</listitem>
diff --git a/de_DE.ISO8859-1/books/handbook/desktop/chapter.sgml b/de_DE.ISO8859-1/books/handbook/desktop/chapter.sgml
index 8cc58a104a..560976afaa 100644
--- a/de_DE.ISO8859-1/books/handbook/desktop/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/desktop/chapter.sgml
@@ -174,7 +174,7 @@
<entry>hoch</entry>
<entry><application>KDE</application>-Biliotheken</entry>
</row>
-
+
<row>
<entry><application>Chromium</application></entry>
<entry>mittel</entry>
@@ -454,13 +454,13 @@
url="http://freebsd.kde.org/howtos/konqueror-flash.php"></ulink>
nachlesen.</para>
</sect2>
-
+
<sect2>
<title>Chromium</title>
<indexterm>
<primary><application>Chromium</application></primary>
</indexterm>
-
+
<para><application>Chromium</application> ist ein quelloffenes
Browserprojekt mit dem Ziel ein sicheres, schnelleres und
stabileres Surferlebnis im Web zu ermglichen.
@@ -468,18 +468,18 @@
Tabs, Blockieren von Pop-Ups, Erweiterungen und vieles mehr.
<application>Chromium</application> ist das Open Source Projekt,
welches auf dem Google Chrome Webbrowser basiert.</para>
-
+
<para><application>Chromium</application> kann als Paket durch die Eingabe des folgenden Befehls installiert werden:</para>
-
+
<screen>&prompt.root; <userinput>pkg_add -r chromium</userinput></screen>
-
+
<para>Als Alternative kann <application>Chromium</application>
aus dem Quellcode durch die Ports Collection bersetzt
werden:</para>
-
+
<screen>&prompt.root; <userinput>cd /usr/ports/www/chromium</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
-
+
<note>
<para><application>Chromium</application> wird als
<filename>/usr/local/bin/chrome</filename> installiert und
@@ -487,7 +487,7 @@
<filename>/usr/local/bin/chromium</filename>.</para>
</note>
</sect2>
-
+
<sect2 id="chromium-java-plugin">
<title>Chromium und das &java;-Plug-In</title>
@@ -496,25 +496,25 @@
<application>Chromium</application> bereits installiert
ist.</para>
</note>
-
+
<para>Installieren Sie <application>OpenJDK&nbsp;6</application>
mit Hilfe der Ports Collection durch Eingabe von:</para>
-
+
<screen>&prompt.root; <userinput>cd /usr/ports/java/openjdk6
&prompt.root; make install clean</userinput></screen>
-
+
<para>Als nchstes installieren Sie <filename
role="package">java/icedtea-web</filename> aus der Ports
Collection:</para>
-
+
<screen>&prompt.root; <userinput>cd /usr/ports/java/icedtea-web
&prompt.root; make install clean</userinput></screen>
-
+
<para>Starten Sie <application>Chromium</application> und geben Sie
<literal>about:plugins</literal> in die Addresszeile ein.
IcedTea-Web sollte dort als eines der installierten Plug-Ins
aufgelistet sein.</para>
-
+
<para>Falls <application>Chromium</application> das IcedTea-Web
Plug-In nicht anzeigt, geben Sie das folgende Kommando ein und
starten Sie den Webbrowser anschliessend neu:</para>
@@ -523,16 +523,16 @@
&prompt.root; ln -s /usr/local/lib/IcedTeaPlugin.so \
/usr/local/share/chromium/plugins/</userinput></screen>
</sect2>
-
+
<sect2 id="chromium-flash-plugin">
<title>Chromium und das &adobe;&nbsp;&flash;-Plug-In</title>
-
+
<note>
<para>Dieser Abschnitt setzt voraus, dass
<application>Chromium</application> bereits installiert
ist.</para>
</note>
-
+
<para>Die Konfiguration von <application>Chromium</application>
und &adobe;&nbsp;&flash; ist hnlich zur <link
linkend="moz-flash-plugin">Anleitung fr Firefox</link>.
@@ -541,7 +541,7 @@
Abschnitt. Es sollte keine weitere Konfiguration notwendig
sein, da <application>Chromium</application> in der Lage ist,
Plug-Ins von anderen Browsern mit zu benutzen.</para>
- </sect2>
+ </sect2>
</sect1>
<sect1 id="desktop-productivity">
@@ -569,7 +569,7 @@
</row>
</thead>
- <tbody>
+ <tbody>
<row>
<entry><application>KOffice</application></entry>
<entry>niedrig</entry>
diff --git a/de_DE.ISO8859-1/books/handbook/disks/chapter.sgml b/de_DE.ISO8859-1/books/handbook/disks/chapter.sgml
index e1216d7f0c..33c9ef0db6 100644
--- a/de_DE.ISO8859-1/books/handbook/disks/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/disks/chapter.sgml
@@ -3500,7 +3500,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<para>Seit &os;&nbsp;8.0-RELEASE und dessen Nachfolger fgen
Sie stattdessen die folgende Zeile hinzu:</para>
-
+
<programlisting>quota_enable="YES"</programlisting>
<indexterm>
<primary>Disk Quotas</primary>
diff --git a/de_DE.ISO8859-1/books/handbook/dtrace/chapter.sgml b/de_DE.ISO8859-1/books/handbook/dtrace/chapter.sgml
index f04153a55e..86a540cbe2 100644
--- a/de_DE.ISO8859-1/books/handbook/dtrace/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/dtrace/chapter.sgml
@@ -145,7 +145,7 @@ that might make this chapter too large.
Krze erfahren Sie, wie Sie dies fr den Kernel und den Bau von
&os; aktivieren.</para>
- <para>Einige Provider in &os; unterscheiden sich von der
+ <para>Einige Provider in &os; unterscheiden sich von der
&solaris;-Implementierung. Am deutlichsten wird das beim
<literal>dtmalloc</literal>-Provider, welcher das Aufzeichnen von
<function>malloc()</function> nach Typen im &os;-Kernel
@@ -215,7 +215,7 @@ options DDB_CTF</programlisting>
Korn-Shell hinzugefgt werden. Dies wird bentigt, da die
Sammlung von &dtrace;-Werkzeugen mehrere Dienstprogramme enthlt,
die in <command>ksh</command> implementiert sind. Installieren Sie
- <filename role="package">shells/ksh93</filename>. Es ist auch
+ <filename role="package">shells/ksh93</filename>. Es ist auch
mglich, diese Werkzeuge unter <filename
role="package">shells/pdksh</filename> oder <filename
role="package">shells/mksh</filename> laufen zu lassen.</para>
diff --git a/de_DE.ISO8859-1/books/handbook/eresources/chapter.sgml b/de_DE.ISO8859-1/books/handbook/eresources/chapter.sgml
index 2717ad6eba..a3b6195303 100644
--- a/de_DE.ISO8859-1/books/handbook/eresources/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/eresources/chapter.sgml
@@ -587,7 +587,7 @@
<row>
<entry>&a.zope.name;</entry>
- <entry><application>Zope</application> fr &os; -
+ <entry><application>Zope</application> fr &os; -
Portierung und Wartung</entry>
</row>
</tbody>
@@ -1125,7 +1125,7 @@
<para>Dies ist ein Forum fr Diskussionen um &os; auf dem
Desktop. Es wird primr von Desktop-Portierern und
- Nutzern verwendet, um Probleme und Verbesserungen zu &os;s
+ Nutzern verwendet, um Probleme und Verbesserungen zu &os;s
Einsatz auf dem Desktop zu besprechen.</para>
</listitem>
</varlistentry>
diff --git a/de_DE.ISO8859-1/books/handbook/mac/chapter.sgml b/de_DE.ISO8859-1/books/handbook/mac/chapter.sgml
index 282671ebdc..2f1ffdaec6 100644
--- a/de_DE.ISO8859-1/books/handbook/mac/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/mac/chapter.sgml
@@ -36,17 +36,17 @@
<see>MAC</see>
</indexterm>
- <para> In &os;&nbsp;5.X wurden neue Sicherheits-Erweiterungen
+ <para> In &os;&nbsp;5.X wurden neue Sicherheits-Erweiterungen
verfgbar, die aus dem TrustedBSD-Projekt bernommen wurden
und auf dem Entwurf &posix;.1e basieren. Die beiden
bedeutendsten neuen Sicherheits-Mechanismen sind Berechtigungslisten
(Access Control Lists, <acronym>ACL</acronym>) und die verbindliche
Zugriffskontrolle (Mandatory Access Control, <acronym>MAC</acronym>).
Durch die MAC knnen Module geladen werden, die neue
- Sicherheitsrichtlinien bereitstellen. Mit Hilfe einiger Module kann
+ Sicherheitsrichtlinien bereitstellen. Mit Hilfe einiger Module kann
beispielsweise ein eng umgrenzter Bereich des Betriebssystems gesichert
- werden, indem die Sicherheitsfunktionen spezieller Dienste
- untersttzt bzw. verstrkt werden. Andere Module wiederum
+ werden, indem die Sicherheitsfunktionen spezieller Dienste
+ untersttzt bzw. verstrkt werden. Andere Module wiederum
betreffen in ihrer Funktion das gesamte System - alle vorhandenen
Subjekte und Objekte. Das "Verbindliche" in der Namensgebung
erwchst aus dem Fakt, dass die Kontrolle allein Administratoren
@@ -56,7 +56,7 @@
gar der System V <acronym>IPC</acronym> in &os;, normalerweise umgesetzt
wird.</para>
- <para>Dieses Kapitel wird sich auf die Grundstruktur der Verbindlichen
+ <para>Dieses Kapitel wird sich auf die Grundstruktur der Verbindlichen
Zugriffskontrolle und eine Auswahl der Module, die verschiedenste
Sicherheitsfunktionen zur Verfgung stellen, konzentrieren.</para>
@@ -82,18 +82,18 @@
</listitem>
<listitem>
- <para>Wie die verschiedenen Richtlinienmodule einer MAC konfiguriert
+ <para>Wie die verschiedenen Richtlinienmodule einer MAC konfiguriert
werden.</para>
</listitem>
<listitem>
- <para>Wie mit einer <acronym>MAC</acronym> und den gezeigten Beispielen
+ <para>Wie mit einer <acronym>MAC</acronym> und den gezeigten Beispielen
eine sicherere Umgebung erstellt werden kann.</para>
</listitem>
<listitem>
<para>Wie die Konfiguration einer <acronym>MAC</acronym> auf korrekte
- Einrichtung getestet wird.</para>
+ Einrichtung getestet wird.</para>
</listitem>
</itemizedlist>
@@ -105,12 +105,12 @@
(<xref linkend="basics"/>).</para>
</listitem>
<listitem>
- <para>Mit den Grundzgen der Kernelkonfiguration und -kompilierung
+ <para>Mit den Grundzgen der Kernelkonfiguration und -kompilierung
vertraut sein (<xref linkend="kernelconfig"/>).</para>
</listitem>
<listitem>
- <para>Einige Vorkenntnisse ber Sicherheitskonzepte im Allgemeinen
+ <para>Einige Vorkenntnisse ber Sicherheitskonzepte im Allgemeinen
und deren Umsetzung in &os; im Besonderen mitbringen (<xref
linkend="security"/>).</para>
</listitem>
@@ -118,8 +118,8 @@
<warning>
<para>Der unsachgeme Gebrauch der in diesem Kapitel
- enthaltenen Informationen kann den Verlust des Systemzugriffs,
- rger mit Nutzern oder die Unfhigkeit, grundlegende
+ enthaltenen Informationen kann den Verlust des Systemzugriffs,
+ rger mit Nutzern oder die Unfhigkeit, grundlegende
Funktionen des X-Windows-Systems zu nutzen, verursachen. Wichtiger
noch ist, dass man sich nicht allein auf die <acronym>MAC</acronym>
verlassen sollte, um ein System zu sichern. Die <acronym>MAC</acronym>
@@ -149,7 +149,7 @@
abgedeckt. Einige weitere Module, die im MAC Framework enthalten sind,
haben besondere Charakteristika, die zum Testen und Entwickeln neuer
Module gedacht sind. Dies sind unter anderem &man.mac.test.4;,
- &man.mac.stub.4; und &man.mac.none.4;. Fr weitere Informationen
+ &man.mac.stub.4; und &man.mac.none.4;. Fr weitere Informationen
zu diesen Modulen und den entsprechend angebotenen Funktionen lesen Sie
bitte die Manpages.</para>
</sect2>
@@ -157,10 +157,10 @@
<sect1 id="mac-inline-glossary">
<title>Schlsselbegriffe</title>
-
+
<para>Bevor Sie weiterlesen, mssen noch einige Schlsselbegriffe
geklrt werden. Dadurch soll jegliche auftretende Verwirrung von
- vornherein beseitigt und die pltzliche Einfhrung neuer
+ vornherein beseitigt und die pltzliche Einfhrung neuer
Begriffe und Informationen vermieden werden.</para>
<itemizedlist>
@@ -180,10 +180,10 @@
<para><emphasis>Hochwassermarkierung</emphasis>: Eine solche Richtlinie
erlaubt die Erhhung der Sicherheitsstufe in Abhngigkeit
der Klassifikation der gesuchten bzw. bereitzustellenden Information.
- Normalerweise wird nach Abschluss des Prozesses die
- ursprngliche Sicherheitsstufe wieder hergestellt. Derzeit
- enthlt die <acronym>MAC</acronym> Grundstruktur keine
- Mglichkeit, eine solche Richtlinie umzusetzen, der
+ Normalerweise wird nach Abschluss des Prozesses die
+ ursprngliche Sicherheitsstufe wieder hergestellt. Derzeit
+ enthlt die <acronym>MAC</acronym> Grundstruktur keine
+ Mglichkeit, eine solche Richtlinie umzusetzen, der
Vollstndigkeit halber ist die Definition hier jedoch
aufgefhrt.</para>
</listitem>
@@ -204,7 +204,7 @@
derart gekennzeichnet werden, bezeichnen diese Label die
sicherheitsrelevanten Eigenschaften. Zugriff ist nur noch dann
mglich, wenn das zugreifende Subjekt eine korrespondierende
- Kennzeichnung trgt. Die Bedeutung und Verarbeitung der
+ Kennzeichnung trgt. Die Bedeutung und Verarbeitung der
Label-Werte ist von der Einrichtung der Richtlinie abhngig:
Whrend einige Richtlinien das Label zum Kennzeichnen der
Vertraulichkeit oder Geheimhaltungsstufe eines Objekts nutzen,
@@ -232,7 +232,7 @@
<para><emphasis>Multilabel</emphasis>: Die Eigenschaft
<option>multilabel</option> ist eine Dateisystemoption, die entweder
im Einzelbenutzermodus mit Hilfe des Werkzeugs &man.tunefs.8;,
- whrend des Bootvorgangs in der Datei &man.fstab.5; oder aber
+ whrend des Bootvorgangs in der Datei &man.fstab.5; oder aber
beim Erstellen einen neues Dateisystems aktiviert werden kann. Diese
Option erlaubt einem Administrator, verschiedenen Objekten
unterschiedliche Labels zuzuordnen - kann jedoch nur zusammen mit
@@ -304,7 +304,7 @@
verwendet werden, um das Netzwerk oder Dateisysteme zu schtzen,
Nutzern den Zugang zu bestimmten Ports oder Sockets zu verbieten und
vieles mehr. Die vielleicht beste Weise, die Module zu verwenden, ist,
- sie miteinander zu kombinieren, indem mehrere
+ sie miteinander zu kombinieren, indem mehrere
Sicherheitsrichtlinienmodule gleichzeitig eine mehrschichtige
Sicherheitsumgebung schaffen. Das ist etwas anderes als singulre
Richtlinien wie zum Beispiel die Firewall, die typischerweise Elemente
@@ -316,7 +316,7 @@
<para>Solche Nachteile sind allerdings gering im Vergleich zum bleibenden
Effekt der erstellten Struktur. Die Mglichkeit zum Beispiel,
- fr konkrete Anwendungen genau die passenden Richtlinien
+ fr konkrete Anwendungen genau die passenden Richtlinien
auszuwhlen und einzurichten, senkt gleichzeitig die Arbeitskosten.
Wenn man unntige Richtlinien aussortiert, kann man die
Gesamtleistung des Systems genauso steigern wie auch eine hhere
@@ -330,7 +330,7 @@
Sicherheitsmerkmale nach eigenem Ermessen zu verndern; dass
Arbeitswerkzeuge, Programme und Skripte, innerhalb der
Beschrnkungen arbeiten knnen, welche die Zugriffsregeln der
- ausgewhlten Module dem System auferlegen; und dass die volle
+ ausgewhlten Module dem System auferlegen; und dass die volle
Kontrolle ber die Regeln der <acronym>MAC</acronym> beim
Administrator ist und bleibt.</para>
@@ -383,7 +383,7 @@
Zeile</para>
- <programlisting>options MAC</programlisting>
+ <programlisting>options MAC</programlisting>
<para>der Kernelkonfiguration hinzugefgt und der Kernel neu
bersetzt und installiert werden.</para>
@@ -391,24 +391,24 @@
<caution>
<para>Verschiedenen Anleitungen fr die <acronym>MAC</acronym>
empfehlen, die einzelnen Module direkt in den Kernel einzuarbeiten.
- Dabei ist es jedoch mglich, das System aus dem Netzwerk
+ Dabei ist es jedoch mglich, das System aus dem Netzwerk
auszusperren oder gar schlimmeres. Die Arbeit mit der
<acronym>MAC</acronym> ist hnlich der Arbeit mit einer Firewall -
man mu, wenn man sich nicht selbst aus dem System aussperren
will, genau aufpassen. Man sollte sich eine Mglichkeit
zurechtlegen, wie man eine Implementation einer <acronym>MAC</acronym>
rckgngig machen kann - genauso wie eine Ferninstallation
- ber das Netzwerk nur mit uerster Vorsicht
+ ber das Netzwerk nur mit uerster Vorsicht
vorgenommen werden sollte. Es wird daher empfohlen,
die Module nicht in den Kernel einzubinden, sondern sie beim
Systemstart via <filename>/boot/loader.conf</filename> zu
laden.</para>
- </caution>
+ </caution>
</sect1>
<sect1 id="mac-understandlabel">
<title>MAC Labels verstehen</title>
-
+
<para>MAC Label sind Sicherheitsmerkmale, die, wenn sie zum Einsatz kommen,
allen Subjekten und Objekten im System zugeordnet werden.</para>
@@ -472,7 +472,7 @@
<acronym>DAC</acronym>! Ich dachte, <acronym>MAC</acronym> wrde die
Kontrolle strengstens an den Administrator binden!</emphasis> Diese
Aussage hlt immer noch stand&nbsp; - <username>root</username> ist
- derjenige, der die Kontrolle ausbt und die Richtlinie konfiguriert,
+ derjenige, der die Kontrolle ausbt und die Richtlinie konfiguriert,
so dass Nutzer in die entsprechenden, angemessenen Kategorien /
Zugriffsklassen eingeordnet werden. Nunja, einige Module schrnken
<username>root</username> selbst ein. Die Kontrolle ber Objekte
@@ -507,10 +507,10 @@
bereits (Zugriffs-)Beschrnkungen
unterliegt.<footnote><para>Andere Vorbedingungen fhren
natrlich zu anderen Fehlern. Zum Beispiel wenn das Objekt nicht
- dem Nutzer gehrt, der das Label ndern mchte, das
+ dem Nutzer gehrt, der das Label ndern mchte, das
Objekt vielleicht gar nicht existiert oder es sich um ein nur lesbares
Objekt handelt. Oder eine verbindliche Richtlinie erlaubt dem
- Proze die Vernderung des Labels nicht, weil die
+ Proze die Vernderung des Labels nicht, weil die
Eigenschaften der Datei, die Eigenschaften des Prozesses oder der
Inhalt des neuen Labels nicht akzeptiert werden. Beispiel: Ein
Anwender mit geringer Vertraulichkeit versucht, das Label einer Datei
@@ -519,7 +519,7 @@
zu machen.</para></footnote> Der Systemadministrator kann so eine
Situation mit Hilfe der folgenden Kommandos berwinden:</para>
- <screen>&prompt.root; <userinput>setfmac biba/high test</userinput>
+ <screen>&prompt.root; <userinput>setfmac biba/high test</userinput>
<errorname>Permission denied</errorname>
&prompt.root; <userinput>setpmac biba/low setfmac biba/high test</userinput>
&prompt.root; <userinput>getfmac test</userinput>
@@ -538,15 +538,15 @@ test: biba/high</screen>
not permitted</errorname> durch die Funktion
<function>mac_set_link</function> angezeigt.</para>
- <sect3>
+ <sect3>
<title>bliche Typen von Labeln</title>
<para>Wenn man die Module &man.mac.biba.4;, &man.mac.mls.4; und
&man.mac.lomac.4; verwendet, hat man die Mglichkeit, einfache
- Label zu vergeben. Diese nennen sich <literal>high</literal>,
+ Label zu vergeben. Diese nennen sich <literal>high</literal>,
<literal>low</literal> und <literal>equal</literal>. Es folgt eine
kurze Beschreibung, was diese Labels bedeuten:</para>
-
+
<itemizedlist>
<listitem>
<para>Das Label <literal>low</literal> ist
@@ -556,7 +556,7 @@ test: biba/high</screen>
zugreifen, die das Label <literal>high</literal> tragen.</para>
</listitem>
- <listitem>
+ <listitem>
<para>Das Label <literal>equal</literal> wird Entitten
verliehen, die von der Richtlinie ausgenommen sein sollen.</para>
</listitem>
@@ -576,13 +576,13 @@ test: biba/high</screen>
<sect4>
<title>Fortgeschrittene Label-Konfiguration</title>
-
+
<para>Numerische klassifizierte Labels werden verwendet in der Form
<literal>Klasse:Verbund+Verbund</literal>. Demnach ist das
Label</para>
<programlisting>biba/10:2+3+6(5:2+3-15:2+3+4+5+6)</programlisting>
-
+
<para>folgendermaen zu lesen:</para>
<para><quote>Biba Policy Label</quote>/<quote>effektive Klasse
@@ -616,7 +616,7 @@ test: biba/high</screen>
Der Fall, dass sich beide dominieren, tritt dann ein, wenn die beiden
Labels gleich sind. Wegen der Natur des Informationsflusses in Biba
kann man einem Nutzer Rechte fr einen Reihe von Abteilungen
- zuordnen, die zum Beispiel mit entsprechenden Projekten
+ zuordnen, die zum Beispiel mit entsprechenden Projekten
korrespondieren. Genauso knnen aber auch Objekten mehrere
Abteilungen zugeordnet sein. Die Nutzer mssen eventuell ihre
gegenwrtigen Rechte mithilfe von <command>su</command> or
@@ -686,7 +686,7 @@ test: biba/high</screen>
</note>
<para>Nach einer nderung der Datei
- <filename>login.conf</filename> mu in jedem Fall die
+ <filename>login.conf</filename> mu in jedem Fall die
Befhigungsdatenbank mit dem Kommando
<command>cap_mkdb</command> neu erstellt werden&nbsp;- und das gilt
fr alle im weiteren Verlauf gezeigten Beispiele und
@@ -695,7 +695,7 @@ test: biba/high</screen>
<para>Es ist ntzlich anzumerken, dass viele Einsatzorte eine
groe Anzahl von Nutzern haben, die wiederum viele
verschiedenen Nutzerklassen angehren sollen. Hier ist eine
- Menge Planungsarbeit notwendig, da die Verwaltung sehr
+ Menge Planungsarbeit notwendig, da die Verwaltung sehr
unbersichtlich und schwierig ist.</para>
</sect3>
@@ -741,7 +741,7 @@ test: biba/high</screen>
label</option> und <option>multilabel</option>. In ihrer ureigenen
Weise bieten beide Vor- und Nachteile bezogen auf die Flexibilitt
bei der Modellierung der Systemsicherheit.</para>
-
+
<para>Die Option <option>single label</option> gibt jedem Subjekt oder
Objekt genau ein einziges Label, zum Beispiel
<literal>biba/high</literal>. Mit dieser Option hat man einen
@@ -804,12 +804,12 @@ test: biba/high</screen>
<para>Wenn Richtlinien benutzt werden sollen, die ohne Labels auskommen,
wird die Option <option>multilabel</option> nicht bentigt. Dies
- betrifft die Richtlinien <literal>seeotheruids</literal>,
+ betrifft die Richtlinien <literal>seeotheruids</literal>,
<literal>portacl</literal> und <literal>partition</literal>.</para>
<para>Man sollte sich dessen bewut sein, dass die Verwendung der
Option <option>multilabel</option> auf einer Partition und die
- Erstellung eines Sicherheitsmodells auf der Basis der &os;
+ Erstellung eines Sicherheitsmodells auf der Basis der &os;
<option>multilevel</option> Funktionalitt einen hohen
Verwaltungsaufwand bedeutet, da alles im Dateisystem ein Label bekommt.
Jedes Verzeichnis, jede Datei und genauso jede Schnittstelle.</para>
@@ -889,7 +889,7 @@ test: biba/high</screen>
Konfiguration der einzelnen Module beschreiben; und in einigen
Fllen Einblicke gewhren, fr welche Situationen welche
Module besonders geeignet sind. Zum Beispiel ein Webserver kann von der
- Verwendung der &man.mac.biba.4; oder der &man.mac.bsdextended.4;
+ Verwendung der &man.mac.biba.4; oder der &man.mac.bsdextended.4;
Richtlinie profitieren. In anderen Fllen, an einem Rechner mit nur
wenigen lokalen Benutzern, ist die &man.mac.partition.4; die Richtlinie
der Wahl.</para>
@@ -909,16 +909,16 @@ test: biba/high</screen>
Module und ihre jeweiligen Vor- und Nachteile vorstellen. Auerdem
wird erklrt, wie sie in bestimmte Umgebungen eingearbeitet werden
knnen. Einige Module untersttzen die Verwendung von
- <literal>Labels</literal>, das heit Zugriffskontrolle durch
+ <literal>Labels</literal>, das heit Zugriffskontrolle durch
hinzufgen einer Kennzeichnung in der Art von <quote>dieses ist
erlaubt, jenes aber nicht</quote>. Eine Label-Konfigurationdatei
- kontrolliert unter anderem, wie auf Dateien zugegriffen oder wie
+ kontrolliert unter anderem, wie auf Dateien zugegriffen oder wie
ber das Netzwerk kommuniziert werden darf. Im vorangehenden
Abschnitt wurde bereits erlutert, wie die Option
<option>multilabel</option> auf Dateisysteme angewendet wird, um eine
Zugriffskontrolle auf einzelne Dateien oder ganze Dateisysteme zu
konfigurieren.</para>
-
+
<para>Eine <option>single label</option> Konfiguration erzwingt ein
einzelnes Label fr das gesamte System. Daher wird die
<command>tunefs</command>-Option <option>multilabel</option> genannt.
@@ -926,8 +926,8 @@ test: biba/high</screen>
</sect1>
<sect1 id="mac-seeotheruids">
- <title>Das MAC Modul seeotheruids</title>
-
+ <title>Das MAC Modul seeotheruids</title>
+
<indexterm>
<primary>MAC See Other UIDs Policy</primary>
</indexterm>
@@ -942,7 +942,7 @@ test: biba/high</screen>
<para>Das Modul &man.mac.seeotheruids.4; erweitert die
<command>sysctl</command>-Variablen
- <literal>security.bsd.see_other_uids</literal> und
+ <literal>security.bsd.see_other_uids</literal> und
<literal>security.bsd.see_other_gids</literal>. Diese Optionen
bentigen keine im Vorhinein zu setzenden Labels und knnen
leicht durchschaubar mit den anderen MAC-Modulen zusammenarbeiten.</para>
@@ -958,7 +958,7 @@ test: biba/high</screen>
die ihnen nicht selbst gehen.</para>
</listitem>
- <listitem>
+ <listitem>
<para>
<literal>security.mac.seeotheruids.specificgid_enabled</literal> kann
eine spezifizierte Nutzergruppe von dieser Richtlinie ausnehmen. Die
@@ -1000,12 +1000,12 @@ test: biba/high</screen>
das Dateisystem und ist eine Erweiterung des sonst blichen
Rechtemodells. Es erlaubt einem Administrator einen Regelsatz zum
Schutz von Dateien, Werkzeugen und Verzeichnissen in der
- Dateisystemhierarchie zu erstellen, der einer Firewall hnelt.
+ Dateisystemhierarchie zu erstellen, der einer Firewall hnelt.
Sobald auf ein Objekt im Dateisystem zugegriffen werden soll, wird eine
Liste von Regel abgearbeitet, bis eine passende Regel gefunden wird
oder die Liste zu Ende ist. Das Verhalten kann durch die nderung
- des &man.sysctl.8; Parameters
- <literal>security.mac.bsdextended.firstmatch_enabled</literal>
+ des &man.sysctl.8; Parameters
+ <literal>security.mac.bsdextended.firstmatch_enabled</literal>
eingestellt werden. hnlich wie bei den anderen Firewallmodulen
in &os; wird eine Datei erstellt, welche die Zugriffsregeln
enthlt. Diese wird beim Systemstart durch eine Variable in
@@ -1047,11 +1047,11 @@ test: biba/high</screen>
&prompt.root; <userinput>ugidfw set 3 subject uid <replaceable>user1</replaceable> object gid <replaceable>user2</replaceable> mode n</userinput></screen>
<para>Diese Befehle bewirken, dass <username>user1</username> keinen
- Zugriff mehr auf Dateien und Programme hat, die
+ Zugriff mehr auf Dateien und Programme hat, die
<username><replaceable>user2</replaceable></username> gehren.
Dies schliet das Auslesen von Verzeichniseintrgen ein.
</para>
-
+
<para>Anstelle <option>uid</option> <username>user1</username>
knnte auch <option>not uid
<replaceable>user2</replaceable></option> als Parameter bergeben
@@ -1065,7 +1065,7 @@ test: biba/high</screen>
<para>Dies sollte als berblick ausreichen, um zu verstehen, wie das
Modul &man.mac.bsdextended.4; helfen kann, das Dateisystem
- abzuschotten. Weitere Informationen bieten die Manpages
+ abzuschotten. Weitere Informationen bieten die Manpages
&man.mac.bsdextended.4; und &man.ugidfw.8;.</para>
</sect2>
</sect1>
@@ -1085,9 +1085,9 @@ test: biba/high</screen>
<para>Bootparameter: <literal>mac_ifoff_load="YES"</literal></para>
- <para>Das Modul &man.mac.ifoff.4; ist einzig dazu da,
+ <para>Das Modul &man.mac.ifoff.4; ist einzig dazu da,
Netzwerkschnittstellen im laufenden Betrieb zu deaktivieren oder zu
- verhindern, das Netzwerkschnittstellen whrend der Bootphase
+ verhindern, das Netzwerkschnittstellen whrend der Bootphase
gestartet werden. Dieses Modul bentigt fr seinen Betrieb
weder Labels, die auf dem System eingerichtet werden mssen, noch
hat es Abhngigkeiten zu anderen MAC Modulen.</para>
@@ -1113,11 +1113,11 @@ test: biba/high</screen>
Netzwerkschnittstellen.</para>
</listitem>
</itemizedlist>
-
+
<para>Die wahrscheinlich hufigste Nutzung von &man.mac.ifoff.4; ist
- die berwachung des Netzwerks in einer Umgebung, in der kein
+ die berwachung des Netzwerks in einer Umgebung, in der kein
Netzwerkverkehr whrend des Bootvorgangs erlaubt werden soll. Eine
- andere mgliche Anwendung wre ein Script, das mit Hilfe von
+ andere mgliche Anwendung wre ein Script, das mit Hilfe von
<filename role="package">security/aide</filename> automatisch alle
Schnittstellen blockiert, sobald Dateien in geschtzten
Verzeichnissen angelegt oder verndert werden.</para>
@@ -1132,8 +1132,8 @@ test: biba/high</screen>
<para>Modulname: <filename>mac_portacl.ko</filename></para>
- <para>Parameter fr die Kernelkonfiguration:
- <literal>options MAC_PORTACL</literal></para>
+ <para>Parameter fr die Kernelkonfiguration:
+ <literal>options MAC_PORTACL</literal></para>
<para>Bootparameter: <literal>mac_portacl_load="YES"</literal></para>
@@ -1176,7 +1176,7 @@ test: biba/high</screen>
<para>Die eigentliche Konfiguration der <literal>mac_portacl</literal>
Richtlinie wird der <command>sysctl</command>-Variablen
- <literal>security.mac.portacl.rules</literal> als Zeichenkette der Form
+ <literal>security.mac.portacl.rules</literal> als Zeichenkette der Form
<literal>rule[,rule,...]</literal> bergeben. Jede einzelne Regel
hat die Form <literal>idtype:id:protocol:port</literal>. Der Parameter
<parameter>idtype</parameter> ist entweder <literal>uid</literal> oder
@@ -1188,7 +1188,7 @@ test: biba/high</screen>
<literal>udp</literal> setzt). Und der letzte Parameter,
<parameter>port</parameter>, enthlt die Nummer des Ports, auf den
der angegebene Nutzer bzw. die angegebene Gruppe Zugriff erhalten
- soll.</para>
+ soll.</para>
<note>
<para>Da der Regelsatz direkt vom Kernel ausgewertet wird, knnen
@@ -1201,10 +1201,10 @@ test: biba/high</screen>
privilegierten Prozessen vorbehalten, mssen also mit als/von
<username>root</username> gestartet werden und weiterhin laufen. Damit
&man.mac.portacl.4; die Vergabe von Ports kleiner als 1024 an nicht
- privilegierte Prozesse bernehmen kann, mu die &unix;
+ privilegierte Prozesse bernehmen kann, mu die &unix;
Standardeinstellung deaktiviert werden. Dazu ndert man die
&man.sysctl.8; Variablen
- <literal>net.inet.ip.portrange.reservedlow</literal> und
+ <literal>net.inet.ip.portrange.reservedlow</literal> und
<literal>net.inet.ip.portrange.reservedhigh</literal> auf den Wert
<quote>0</quote>.</para>
@@ -1229,7 +1229,7 @@ test: biba/high</screen>
<literal>security.mac.portacl.suser_exempt</literal> auf einen Wert
ungleich Null. Das Modul &man.mac.portacl.4; ist nun so eingerichtet,
wie es &unix;-artige Betriebssysteme normal ebenfalls tun.</para>
-
+
<screen>&prompt.root; <userinput>sysctl security.mac.portacl.rules=uid:80:tcp:80</userinput></screen>
<para>Nun erlauben wir dem Nutzer mit der <acronym>UID</acronym> 80,
@@ -1240,7 +1240,7 @@ test: biba/high</screen>
<screen>&prompt.root; <userinput>sysctl security.mac.portacl.rules=uid:1001:tcp:110,uid:1001:tcp:995</userinput></screen>
<para>Hier wird dem Nutzer mit der <acronym>UID</acronym> 1001 erlaubt,
- die <acronym>TCP</acronym> Ports 110 (<quote>pop3</quote>) und 995
+ die <acronym>TCP</acronym> Ports 110 (<quote>pop3</quote>) und 995
(<quote>pop3s</quote>) zu verwenden. Dadurch kann dieser Nutzer einen
Server starten, der Verbindungen an diesen beiden Ports annehmen
kann.</para>
@@ -1290,14 +1290,14 @@ test: biba/high</screen>
Partition zugreifen. Das bedeutet unter anderem, das ein Nutzer, der
einer Klasse <literal>insecure</literal> zugeordnet ist, nicht auf das
Kommando <command>top</command> zugreifen kann - wie auch auf viele
- anderen Befehle, die einen eigenen Proze erzeugen.</para>
+ anderen Befehle, die einen eigenen Proze erzeugen.</para>
<para>Um einen Befehl einer Proze-Partition zuzuordnen, mu
dieser durch das Kommando <command>setpmac</command> mit einem Label
versehen werden:</para>
<screen>&prompt.root; <userinput>setpmac partition/13 top</userinput></screen>
-
+
<para>Diese Zeile fgt das Kommando <command>top</command> dem
Labelsatz fr Nutzer der Klasse <literal>insecure</literal> hinzu,
sofern die Partition 13 mit der Klasse <literal>insecure</literal>
@@ -1392,7 +1392,7 @@ test: biba/high</screen>
<listitem>
<para>Das Label <literal>mls/high</literal> verkrpert das
hchstmgliche Freigabe-Level. Objekte, denen dieses Label
- zugeordnet wird, dominieren alle anderen Objekte des Systems.
+ zugeordnet wird, dominieren alle anderen Objekte des Systems.
Trotzdem knnen sie Objekten mit einem niedrigeren
Freigabe-Level keine Informationen zuspielen.</para>
</listitem>
@@ -1512,7 +1512,7 @@ test: biba/high</screen>
<para>Ein Dateiserver, der vertrauliche Informationen einer Firma
oder eines Konzerns speichert</para>
</listitem>
-
+
<listitem>
<para>Umgebungen in Finanzeinrichtungen</para>
</listitem>
@@ -1538,21 +1538,21 @@ test: biba/high</screen>
<para>Bootparameter: <literal>mac_biba_load="YES"</literal></para>
<para>Das Modul &man.mac.biba.4; ldt die <acronym>MAC</acronym> Biba
- Richtlinie. Diese hnelt stark der <acronym>MLS</acronym>
+ Richtlinie. Diese hnelt stark der <acronym>MLS</acronym>
Richtlinie, nur das die Regeln fr den Informationsflu ein
wenig vertauscht sind. Es wird in diesem Fall der absteigende Flu
- sicherheitskritischer Information geregelt, whrend die
+ sicherheitskritischer Information geregelt, whrend die
<acronym>MLS</acronym> Richtlinie den aufsteigenden Flu regelt.
In gewissen Sinne treffen dieses und das vorangegangene Unterkapitel also
auf beide Richtlinien zu.</para>
- <para>In einer Biba-Umgebung wird jedem Subjekt und jedem Objekt ein
+ <para>In einer Biba-Umgebung wird jedem Subjekt und jedem Objekt ein
<quote>Integritts</quote>-Label zugeordnet. Diese Labels sind in
hierarchischen Klassen und nicht-hierarchischen Komponenten geordnet. Je
hher die Klasse, um so hher die Integritt.</para>
<para>Die untersttzten Labels heien
- <literal>biba/low</literal>, <literal>biba/equal</literal> und
+ <literal>biba/low</literal>, <literal>biba/equal</literal> und
<literal>biba/high</literal>. Sie werden im Folgenden
erklrt:</para>
@@ -1613,7 +1613,7 @@ test: biba/high</screen>
<itemizedlist>
<listitem>
- <para><literal>security.mac.biba.enabled</literal> zum
+ <para><literal>security.mac.biba.enabled</literal> zum
Aktivieren/Deaktivieren der Richtlinie auf dem Zielsystem.</para>
</listitem>
@@ -1643,7 +1643,7 @@ test: biba/low</screen>
<para>Integritt garantiert, im Unterschied zu Sensitivitt,
dass Informationen nur durch vertraute Parteien verndert werden
- knnen. Dies schliet Informationen ein, die zwischen
+ knnen. Dies schliet Informationen ein, die zwischen
Subjekten ausgetauscht werden, zwischen Objekt, oder auch zwischen den
beiden. Durch Integritt wird gesichert, das Nutzer nur
Informationen verndern, oder gar nur lesen knnen, die sie
@@ -1664,7 +1664,7 @@ test: biba/low</screen>
<literal>biba/high</literal> sobald das Modul aktiviert wird&nbsp;- und
es liegt allein am Administrator, die verschiedenen Klassen und Stufen
fr die einzelnen Nutzer zu konfigurieren. Anstatt mit Freigaben
- zu arbeiten, wie weiter oben gezeigt wurde, knnte man auch
+ zu arbeiten, wie weiter oben gezeigt wurde, knnte man auch
berbegriffe fr Projekte oder Systemkomponenten entwerfen.
Zum Beispiel, ausschlielich Entwicklern den Vollzugriff auf
Quellcode, Compiler und Entwicklungswerkzeuge gewhren,
@@ -1695,13 +1695,13 @@ test: biba/low</screen>
</indexterm>
<para>Modulname: <filename>mac_lomac.ko</filename></para>
- <para>Parameter fr die Kernelkonfiguration:
+ <para>Parameter fr die Kernelkonfiguration:
<literal>options MAC_LOMAC</literal></para>
- <para>Bootparameter: <literal>mac_lomac_load="YES"</literal></para>
+ <para>Bootparameter: <literal>mac_lomac_load="YES"</literal></para>
<para>Anders als die Biba Richtlinie erlaubt die &man.mac.lomac.4;
- Richtlinie den Zugriff auf Objekte niedrigerer Integritt nur,
+ Richtlinie den Zugriff auf Objekte niedrigerer Integritt nur,
nachdem das Integrittslevel gesenkt wurde. Dadurch wird eine
Strung derIntegrittsregeln verhindert.</para>
@@ -1719,7 +1719,7 @@ test: biba/low</screen>
Integrittslabeln, die Subjekten das Lesen von Objekten niedriger
Integritt gestatten und dann das Label des Subjektes herunterstufen
- um zuknftige Schreibvorgnge auf Objekte hoher
- Integritt zu unterbinden. Dies ist die Funktion der Option
+ Integritt zu unterbinden. Dies ist die Funktion der Option
<literal>[auxgrade]</literal>, die eben vorgestellt wurde. Durch sie
erhlt diese Richtlinie eine bessere Kompatibilitt und die
Initialisierung ist weniger aufwndig als bei der Richtlinie
@@ -1727,7 +1727,7 @@ test: biba/low</screen>
<sect2>
<title>Beispiele</title>
-
+
<para>Wie schon bei den Richtlinien Biba und <acronym>MLS</acronym>
werden die Befehle <command>setfmac</command> und
<command>setpmac</command> verwendet, um die Labels an den
@@ -1836,14 +1836,14 @@ mac_seeotheruids_load="YES"</programlisting>
<screen>&prompt.root; <userinput>for x in `awk -F: '($3 &gt;= 1001) &amp;&amp; ($3 != 65534) { print $1 }' \</userinput>
<userinput>/etc/passwd`; do pw usermod $x -L default; done;</userinput></screen>
- <para>Verschieben Sie die Nutzer <username>nagios</username> und
+ <para>Verschieben Sie die Nutzer <username>nagios</username> und
<username>www</username> in die <literal>insecure</literal>
Klasse:</para>
<screen>&prompt.root; <userinput>pw usermod nagios -L insecure</userinput></screen>
- <screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen>
+ <screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen>
</sect2>
-
+
<sect2>
<title>Die Kontextdatei erstellen</title>
@@ -1927,7 +1927,7 @@ default_labels socket ?biba
<programlisting>security.mac.biba.trust_all_interfaces=1</programlisting>
<para>Und das Folgende gehrt in Datei <filename>rc.conf</filename>
- zu den Optionen fr die Netzwerkkarte. Falls die
+ zu den Optionen fr die Netzwerkkarte. Falls die
Netzwerkverbindung(-en) via <acronym>DHCP</acronym>
konfiguriert werden, mu man dies nach jedem Systemstart
eigenhndig nachtragen:</para>
@@ -1954,7 +1954,7 @@ default_labels socket ?biba
<para>Wenn alles gut aussieht, knnen
<application>Nagios</application>,
- <application>Apache</application> und
+ <application>Apache</application> und
<application>Sendmail</application> gestartet werden - allerdings auf
eine Weise, die unserer Richtlinie gerecht wird. Zum Beispiel durch die
folgenden Kommandos:</para>
@@ -1978,7 +1978,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
<para>Um dies zu vermeiden, werden die Nutzer durch &man.login.conf.5;
eingeschrnkt. Wenn &man.setpmac.8; einen Befehl
- auerhalb der definierten Schranken ausfhren soll, wird
+ auerhalb der definierten Schranken ausfhren soll, wird
ein Fehler zurckgeliefert. In so einem Fall mu
<username>root</username> auf <literal>biba/high(high-high)</literal>
gesetzt werden.</para>
@@ -2033,7 +2033,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
<note>
<para>Wenn ein neuer Benutzer hinzugefgt wird, ist fr diesen
- zunchst keine &man.mac.bsdextended.4; Regel im Regelsatz
+ zunchst keine &man.mac.bsdextended.4; Regel im Regelsatz
vorhanden. Schnelle Abhilfe schafft hier, einfach das Kernelmodul mit
&man.kldunload.8; zu entladen und mit &man.kldload.8; erneut
einzubinden.</para>
@@ -2062,8 +2062,8 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
dieser Fehler auftritt - er kann mit folgender Prozedur behoben
werden:</para>
- <procedure>
- <step>
+ <procedure>
+ <step>
<para>ffnen Sie die Datei <filename>/etc/fstab</filename> und
setzen Sie die Rootpartition auf <option>ro</option> wie
<quote>read-only</quote>.</para>
@@ -2095,8 +2095,8 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
<command>mount</command> um sich zu versichern, dass die
<option>multilabel</option> korrekt fr das root-Dateisystem
gesetzt wurde.</para>
- </step>
- </procedure>
+ </step>
+ </procedure>
</sect2>
@@ -2121,7 +2121,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
<step>
<para>Gehen Sie die Label-Richtlinien Schritt fr Schritt
nocheinmal durch. Achten Sie darauf, dass fr den Nutzer, bei
- dem das Problem auftritt, fr X11 und das Verzeichnis
+ dem das Problem auftritt, fr X11 und das Verzeichnis
<filename class="directory">/dev</filename> alle Einstellungen
korrekt sind.</para>
</step>
@@ -2131,11 +2131,11 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
Fehlermeldung und eine Beschreibung ihrer Arbeitsumgebung an die
(englisch-sprachige) TrustedBSD Diskussionsliste auf der <ulink
url="http://www.TrustedBSD.org">TrustedBSD</ulink> Webseite oder an
- die &a.questions; Mailingliste.</para>
+ die &a.questions; Mailingliste.</para>
</step>
</procedure>
</sect2>
-
+
<sect2>
<title>Error: &man..secure.path.3; cannot stat
<filename>.login_conf</filename></title>
@@ -2157,7 +2157,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
nicht, da das Label sich nicht ndert. Hier haben wir also einen
Fall, in dem das Gewhrleistungsmodell von Biba verhindert, das
der Superuser Objekte einer niedrigeren Integritt betrachten
- kann.</para>
+ kann.</para>
</sect2>
<sect2>
diff --git a/de_DE.ISO8859-1/books/handbook/multimedia/chapter.sgml b/de_DE.ISO8859-1/books/handbook/multimedia/chapter.sgml
index ff29bf174a..9d16235923 100644
--- a/de_DE.ISO8859-1/books/handbook/multimedia/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/multimedia/chapter.sgml
@@ -407,7 +407,7 @@ kld snd_ich (1p/2r/0v channels duplex default)</screen>
</tbody>
</tgroup>
</informaltable>
-
+
<para>Ein weiterer Fall ist der, dass moderne Graphikkarten oft auch
ihre eigenen Soundtreiber mit sich fhren, um
<acronym>HDMI</acronym> oder hnliches zu verwenden. Diese
@@ -444,16 +444,16 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
<literal>hw.snd.default_unit</literal> auf die Einheit,
welche fr das Abspielen benutzt werden soll, wie
folgt:</para>
-
+
<screen>&prompt.root; <userinput>sysctl hw.snd.default_unit=<replaceable>n</replaceable></userinput></screen>
-
+
<para>Hier reprsentiert <literal>n</literal> die Nummer
der Soundkarte, die verwendet werden soll, in diesem Beispiel
also <literal>4</literal>. Sie knnen diese
nderung dauerhaft machen, indem Sie die folgende Zeile
zu der <filename>/etc/sysctl.conf</filename> Datei
hinzufgen:</para>
-
+
<programlisting>hw.snd.default_unit=<replaceable>4</replaceable></programlisting>
</sect3>
</sect2>
@@ -1675,7 +1675,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
werden, weil <application>webcamd</application> eine
<acronym role="Video for Linux">V4L</acronym>-Anwendung zur
Verfgung stellt, die als Benutzerprogramm lft. Jede
- <acronym role="Digital Video Broadcasting">DVB</acronym>-Karte,
+ <acronym role="Digital Video Broadcasting">DVB</acronym>-Karte,
welche von <application>webcamd</application> untersttzt
wird, sollte mit MythTV funktionieren, jedoch gibt es eine Liste
von Karten, die <ulink
@@ -1695,7 +1695,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
<sect2>
<title>Abhngigkeiten</title>
-
+
<para>Da MythTV flexibel und modular aufgebaut ist, ist der Benutzer
in der Lage, das Frontend und Backend auf unterschiedlichen
Rechnern laufen zu lassen.</para>
@@ -1723,7 +1723,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
<title>MythTV einrichten</title>
<para>Um MythTV zu installieren, befolgen Sie die hier
- aufgefhrten Schritte. Zuerst installieren Sie MythTV aus
+ aufgefhrten Schritte. Zuerst installieren Sie MythTV aus
der Ports-Sammlung:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/multimedia/mythtv</userinput>
diff --git a/de_DE.ISO8859-1/books/handbook/network-servers/chapter.sgml b/de_DE.ISO8859-1/books/handbook/network-servers/chapter.sgml
index e4c07154fe..891bd07caa 100644
--- a/de_DE.ISO8859-1/books/handbook/network-servers/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/network-servers/chapter.sgml
@@ -2916,7 +2916,7 @@ nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</
<firstterm>asynchron</firstterm>. Andere Startskripte laufen
weiter, whrend DHCP fertig abgearbeitet wird, was den
Systemstart beschleunigt.</para>
-
+
<para>DHCP im Hintergrund funktioniert gut, wenn der DHCP-Server
schnell auf Anfragen antwortet und der
DHCP-Konfigurationsprozess ebenso schnell abluft.
@@ -2927,21 +2927,21 @@ nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</
<firstterm>asynchronen</firstterm>-Modus wird das Problem
verhindert, so dass die Startskripte pausiert werden, bis
die DHCP-Konfiguration abgeschlossen ist.</para>
-
+
<para>Um sich zu einem DHCP-Server im Hintergrund zu verbinden,
whrend andere Startskripte fortfahren
(asynchroner Modus), benutzen Sie den
<quote><literal>DHCP</literal></quote>-Wert in
<filename>/etc/rc.conf</filename>:</para>
-
+
<programlisting>ifconfig_<replaceable>fxp0</replaceable>="DHCP"</programlisting>
<para>Um den Start zu pausieren, damit DHCP vorher
abgeschlossen werden kann, benutzen Sie den synchronen Modus
mit dem Eintrag
<quote><literal>SYNCDHCP</literal></quote>:</para>
-
- <programlisting>ifconfig_<replaceable>fxp0</replaceable>="SYNCDHCP"</programlisting>
+
+ <programlisting>ifconfig_<replaceable>fxp0</replaceable>="SYNCDHCP"</programlisting>
<note>
<para>Ersetzen Sie <replaceable>fxp0</replaceable>, das
@@ -3749,7 +3749,7 @@ zone "." { type hint; file "/etc/namedb/named.root"; };
To use this mechanism, uncomment the entries below, and comment
the hint zone above.
-
+
As documented at http://dns.icann.org/services/axfr/ these zones:
"." (the root), ARPA, IN-ADDR.ARPA, IP6.ARPA, and ROOT-SERVERS.NET
are availble for AXFR from these servers on IPv4 and IPv6:
@@ -4264,7 +4264,7 @@ www IN CNAME example.org.</programlisting>
<primary>BIND</primary>
<secondary>DNS security extensions</secondary>
</indexterm>
-
+
<para>Domain Name System Security Extensions, oder kurz <acronym
role="Domain Name Security Extensions">DNSSEC</acronym>, ist eine
Sammlung von Spezifikationen, um auflsende Nameserver von
@@ -4290,7 +4290,7 @@ www IN CNAME example.org.</programlisting>
<acronym>DNSSEC</acronym> sind die dazugehrigen
<acronym>RFC</acronym>s ein guter Einstieg in die Thematik. Sehen
Sie sich dazu die Liste in <xref linkend="dns-read"/> an.</para>
-
+
<para>Der folgende Abschnitt wird zeigen, wie man
<acronym>DNSSEC</acronym> fr einen autoritativen
<acronym>DNS</acronym>-Server und einen rekursiven (oder cachenden)
@@ -4310,10 +4310,10 @@ www IN CNAME example.org.</programlisting>
automatisch Zonen signieren zu lassen und Signaturen aktuell zu
halten. Unterschiede zwischen den Versionen 9.6.2 und 9.7 und
hher werden an den betreffenden Stellen angesprochen.</para>
-
+
<sect3>
<title>Rekursive <acronym>DNS</acronym>-Server Konfiguration</title>
-
+
<para>Die Aktivierung der
<acronym>DNSSEC</acronym>-berprfung von Anfragen,
die von einem rekursiven <acronym>DNS</acronym>-Server
@@ -4328,13 +4328,13 @@ www IN CNAME example.org.</programlisting>
durch Abfrage an die Root-Zone erhalten werden, indem man dazu
<application>dig</application> verwendet. Durch Aufruf
von</para>
-
+
<screen>&prompt.user; <userinput>dig +multi +noall +answer DNSKEY . &gt; root.dnskey</userinput></screen>
-
+
<para>wird der Schlssel in
<filename>root.dnskey</filename> abgelegt. Der Inhalt sollte
so hnlich wie folgt aussehen:</para>
-
+
<programlisting>. 93910 IN DNSKEY 257 3 8 (
AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQ
bSEW0O8gcCjFFVQUTf6v58fLjwBd0YI0EzrAcQqBGCzh
@@ -4368,7 +4368,7 @@ www IN CNAME example.org.</programlisting>
role="Zone Signing Key">ZSK</acronym>) bezeichnet. Weitere
Schlsselarten werden spter in <xref
linkend="dns-dnssec-auth"/> erlutert.</para>
-
+
<para>Nun muss der Schlssel verifiziert und so formatiert
werden, dass <acronym>BIND</acronym> diesen verwenden kann.
Um den Schlssel zu verifizieren, erzeugen Sie einen
@@ -4377,16 +4377,16 @@ www IN CNAME example.org.</programlisting>
Datei, welche die <acronym
role="Resource Record">RR</acronym>s enthlt,
mittels</para>
-
+
<screen>&prompt.user; <userinput>dnssec-dsfromkey -f root-dnskey . &gt; root.ds</userinput></screen>
-
+
<para>Diese Eintrge verwenden SHA-1 sowie SHA-256 und
sollten hnlich zu folgendem Beispiel aussehen, in dem
der lngere, SHA-256, benutzt wird.</para>
-
+
<programlisting>. IN DS 19036 8 1 B256BD09DC8DD59F0E0F0D8541B8328DD986DF6E
. IN DS 19036 8 2 49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5</programlisting>
-
+
<para>Der SHA-256 <acronym>RR</acronym> kann nun mit dem Abriss
in <ulink
url="https://data.iana.org/root-anchors/root-anchors.xml">https://data.iana.org/root-anchors/root-anchors.xml</ulink> verglichen werden. Um
@@ -4395,7 +4395,7 @@ www IN CNAME example.org.</programlisting>
wurde, kann die Datei mittels der <acronym>PGP</acronym>
Signatur in <ulink
url="https://data.iana.org/root-anchors/root-anchors.asc">https://data.iana.org/root-anchors/root-anchors.asc</ulink> berprft werden.</para>
-
+
<para>Als nchstes muss der Schlssel in das passende
Format gebracht werden. Dies unterscheidet sich ein bisschen
von den <acronym>BIND</acronym> Versionen 9.6.2 und 9.7 und
@@ -4409,7 +4409,7 @@ www IN CNAME example.org.</programlisting>
werden und die Aktualisierung muss hndisch erfolgen.
In <acronym>BIND</acronym> 9.6.2 sollte das Format
folgendermassen aussehen:</para>
-
+
<programlisting>trusted-keys {
"." 257 3 8
"AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF
@@ -4420,10 +4420,10 @@ www IN CNAME example.org.</programlisting>
Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq
QxA+Uk1ihz0=";
};</programlisting>
-
+
<para>In 9.7 wird das Format stattdessen wie folgt
aussehen:</para>
-
+
<programlisting>managed-keys {
"." initial-key 257 3 8
"AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF
@@ -4434,7 +4434,7 @@ www IN CNAME example.org.</programlisting>
Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq
QxA+Uk1ihz0=";
};</programlisting>
-
+
<para>Der Root-Schlssel kann nun zu
<filename>named.conf</filename> hinzugefgt werden,
entweder direkt oder durch Inkludierung der Datei, die den
@@ -4445,10 +4445,10 @@ www IN CNAME example.org.</programlisting>
<filename>named.conf</filename> bearbeitet und die folgende
<literal>options</literal>-Direktive hinzugefgt
wird:</para>
-
+
<programlisting>dnssec-enable yes;
dnssec-validation yes;</programlisting>
-
+
<para>Um zu prfen, dass es tatschlich funktioniert,
benutzen Sie <application>dig</application>, um eine Anfrage
zu einer signierten Zone durch den Resolver, der gerade
@@ -4456,28 +4456,28 @@ dnssec-validation yes;</programlisting>
wird den <literal>AD</literal>-Eintrag aufweisen, um
anzudeuten, dass die Daten authentisiert sind. Eine Anfrage
wie</para>
-
+
<screen>&prompt.user; <userinput>dig @<replaceable>resolver</replaceable> +dnssec se ds </userinput></screen>
-
+
<para>sollte den <acronym>DS</acronym> <acronym>RR</acronym>
fr die <literal>.se</literal>-Zone zurckgeben. In
dem Abschnitt <literal>flags:</literal> sollte der
<literal>AD</literal>-Eintrag gesetzt sein, wie im folgenden
zu sehen ist:</para>
-
+
<programlisting>...
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
...</programlisting>
-
+
<para>Der Resolver ist nun in der Lage, Anfragen ans
<acronym>DNS</acronym> zu authentisieren.</para>
</sect3>
-
+
<sect3 id="dns-dnssec-auth">
<title>Autoritative <acronym>DNS</acronym>-Server
Konfiguration</title>
-
+
<para>Um einen autoritativen Nameserver dazu zu bringen, als
eine <acronym>DNSSEC</acronym>-signierte Zone zu fungieren,
ist ein wenig mehr Aufwand ntig. Eine Zone ist durch
@@ -4513,7 +4513,7 @@ dnssec-validation yes;</programlisting>
role="Zone Signing Key">ZSK</acronym> wird verwendet, um die
Zone zu signieren und muss nur dort ffentlich
zugnglich gemacht werden.</para>
-
+
<para>Um <acronym>DNSSEC</acronym> fr die <hostid
role="domainname">example.com</hostid>-Zone, welche in den
vorherigen Beispielen verwendet wird, zu aktivieren, muss
@@ -4527,14 +4527,14 @@ dnssec-validation yes;</programlisting>
Um den <acronym>KSK</acronym> fr <hostid
role="domainname">example.com</hostid> zu generieren, geben
Sie</para>
-
+
<screen>&prompt.user; <userinput>dnssec-keygen -f KSK -a RSASHA256 -b 2048 -n ZONE example.com</userinput></screen>
-
+
<para>ein und um den <acronym>ZSK</acronym> zu erzeugen, setzen
Sie folgenden Befehl ab:</para>
-
+
<screen>&prompt.user; <userinput>dnssec-keygen -a RSASHA256 -b 2048 -n ZONE example.com</userinput></screen>
-
+
<para><application>dnssec-keygen</application> gibt zwei
Dateien aus, den ffentlichen und den privaten
Schlssel und zwar in Dateinamen, die hnlich
@@ -4548,31 +4548,31 @@ dnssec-validation yes;</programlisting>
Schlssel in einer Zone vorliegen. Es ist auch
mglich, die Schlssel umzubenennen. Fr
jede <acronym>KSK</acronym>-Datei tun Sie folgendes:</para>
-
+
<screen>&prompt.user; <userinput>mv Kexample.com.+005+nnnnn.key Kexample.com.+005+nnnnn.KSK.key</userinput>
&prompt.user; <userinput>mv Kexample.com.+005+nnnnn.private Kexample.com.+005+nnnnn.KSK.private</userinput></screen>
-
+
<para>Fr die <acronym>ZSK</acronym>-Dateien ersetzen Sie
<literal>KSK</literal> fr <literal>ZSK</literal> wenn
ntig. Die Dateien knnen nun in der Zonendatei
inkludiert werden, indem die <literal>$include</literal>
Anweisung verwendet wird. Es sollte folgendermassen
aussehen:</para>
-
+
<programlisting>$include Kexample.com.+005+nnnnn.KSK.key ; KSK
$include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
-
+
<para>Schliesslich signieren Sie die Zone und weisen
<acronym>BIND</acronym> an, die signierte Zonendatei zu
- benutzen. Um eine Zone zu signieren, wird
+ benutzen. Um eine Zone zu signieren, wird
<application>dnssec-signzone</application> eingesetzt. Der
Befehl, um eine Zone <hostid
role="domainname">example.com</hostid> zu signieren, die in
<filename>example.com.db</filename> liegt, sollte
wie folgt aussehen:</para>
-
+
<screen>&prompt.user; <userinput>dnssec-signzone -o example.com -k Kexample.com.+005+nnnnn.KSK example.com.db Kexample.com.+005+nnnnn.ZSK.key</userinput></screen>
-
+
<para>Der Schlssel, welcher mit dem Argument
<option>-k</option> bergeben wird, ist der
<acronym>KSK</acronym> und die andere Schlsseldatei ist
@@ -4601,7 +4601,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
zwischenspeichern. Es ist mglich, ein Skript und einen
cron-Job zu schreiben, um dies zu erledigen. Lesen Sie dazu
die relevanten Anleitungen, um Details zu erfahren.</para>
-
+
<para>Stellen Sie sicher, dass die privaten Schlssel
vertraulich bleiben, genau wie mit allen anderen
kryptographischen Schlsseln auch. Wenn ein
@@ -4621,11 +4621,11 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
url="http://www.ietf.org/rfc/rfc4641.txt"><acronym>RFC</acronym>
4641: <acronym>DNSSEC</acronym> Operational practices</ulink>.</para>
</sect3>
-
+
<sect3>
<title>Automatisierung mittels <acronym>BIND</acronym> 9.7 oder
hher</title>
-
+
<para>Beginnend mit der Version 9.7 von <acronym>BIND</acronym>
wurde eine neue Eigenschaft vorgestellt, die
<emphasis>Smart Signing</emphasis> genannt wird. Diese zielt
@@ -4648,15 +4648,15 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
role="domainname">example.com</hostid> zu nutzen, fgen
Sie die folgenden Zeilen zur <filename>named.conf</filename>
hinzu:</para>
-
+
<programlisting>zone example.com {
type master;
key-directory "/etc/named/keys";
update-policy local;
auto-dnssec maintain;
file "/etc/named/dynamic/example.com.zone";
-};</programlisting>
-
+};</programlisting>
+
<para>Nachdem diese nderungen durchgefhrt wurden,
erzeugen Sie die Schlssel fr die Zone wie in
<xref linkend="dns-dnssec-auth"/> beschrieben wird, legen
@@ -4774,7 +4774,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key ; ZSK</programlisting>
<para><ulink url="http://tools.ietf.org/html/rfc5011">RFC 5011
- Automated Updates of DNS Security (<acronym>DNSSEC</acronym>)
Trust Anchors</ulink></para>
- </listitem>
+ </listitem>
</itemizedlist>
</sect2>
</sect1>
diff --git a/de_DE.ISO8859-1/books/handbook/preface/preface.sgml b/de_DE.ISO8859-1/books/handbook/preface/preface.sgml
index 7807cf03b6..ca0a061fe9 100644
--- a/de_DE.ISO8859-1/books/handbook/preface/preface.sgml
+++ b/de_DE.ISO8859-1/books/handbook/preface/preface.sgml
@@ -64,7 +64,7 @@
Installation von &os; in verschiedenen
Virtualisierungs-Programmen.</para>
</listitem>
-
+
<listitem>
<para><xref linkend="bsdinstall"/>,
&os;&nbsp;9.<replaceable>x</replaceable> (und neuer) installieren,
diff --git a/de_DE.ISO8859-1/books/handbook/txtfiles.ent b/de_DE.ISO8859-1/books/handbook/txtfiles.ent
index b0d6ddac11..b55ec64919 100644
--- a/de_DE.ISO8859-1/books/handbook/txtfiles.ent
+++ b/de_DE.ISO8859-1/books/handbook/txtfiles.ent
@@ -1,14 +1,14 @@
<?xml version="1.0" encoding="ISO8859-1"?>
-<!--
- Creates entities for each .txt screenshot that is included in the
+<!--
+ Creates entities for each .txt screenshot that is included in the
Handbook.
Each entity is named txt.dir.foo, where dir is the directory in
- which it is stored, and foo is its filename, without the '.txt'
+ which it is stored, and foo is its filename, without the '.txt'
extension.
Entities should be listed in alphabetical order.
-
+
$FreeBSD$
$FreeBSDde: de-docproj/books/handbook/txtfiles.ent,v 1.2 2009/11/26 17:47:10 bcr Exp $
basiert auf: 1.4
diff --git a/de_DE.ISO8859-1/books/handbook/users/chapter.sgml b/de_DE.ISO8859-1/books/handbook/users/chapter.sgml
index 812508a63b..97a6b8ae77 100644
--- a/de_DE.ISO8859-1/books/handbook/users/chapter.sgml
+++ b/de_DE.ISO8859-1/books/handbook/users/chapter.sgml
@@ -1065,14 +1065,14 @@ teamtwo:*:1100:jru</screen>
<filename>/etc/passwd</filename> zu lesen.</para>
<example>
- <title>Hinzufgen eines neuen Gruppenmitglieds mittels
+ <title>Hinzufgen eines neuen Gruppenmitglieds mittels
&man.pw.8;</title>
-
+
<screen>&prompt.root; <userinput>pw groupmod teamtwo -m db</userinput>
&prompt.root; <userinput>pw groupshow teamtwo</userinput>
teamtwo:*:1100:jru,db</screen>
</example>
-
+
<para>Die Argumente zur Option <option>-m</option> ist eine durch Komma
getrennte Liste von Benutzern, die der Gruppe hinzugefgt werden
sollen. Anders als im vorherigen Beispiel werden diese Benutzer in die
diff --git a/de_DE.ISO8859-1/htdocs/availability.sgml b/de_DE.ISO8859-1/htdocs/availability.sgml
index 1f57678a40..f48393a57a 100644
--- a/de_DE.ISO8859-1/htdocs/availability.sgml
+++ b/de_DE.ISO8859-1/htdocs/availability.sgml
@@ -10,7 +10,7 @@
<head>
<meta http-equiv="refresh" content="5;url=&base;/index.html"/>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-
+
<title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
diff --git a/de_DE.ISO8859-1/htdocs/news/2004/news.xml b/de_DE.ISO8859-1/htdocs/news/2004/news.xml
index 0a77f022b4..c31f787e85 100644
--- a/de_DE.ISO8859-1/htdocs/news/2004/news.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2004/news.xml
@@ -484,7 +484,7 @@
<day>
<name>30</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:mezz@FreeBSD.org">Jeremy Messenger</a>
(ports)</p>
</event>
@@ -493,7 +493,7 @@
<day>
<name>19</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:tackerman@FreeBSD.org">Tony Ackerman</a>
(src)</p>
</event>
@@ -502,7 +502,7 @@
<day>
<name>17</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:marius@FreeBSD.org">Marius Strobl</a>
(src)</p>
</event>
@@ -511,7 +511,7 @@
<day>
<name>5</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:dhartmei@FreeBSD.org">Daniel Hartmeier</a>
(src)</p>
</event>
@@ -599,7 +599,7 @@
<day>
<name>26</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:vkashyap@FreeBSD.org">Vinod Kashyap</a>
(src)</p>
</event>
@@ -633,7 +633,7 @@
<day>
<name>17</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:rees@FreeBSD.org">Jim Rees</a>
(src)</p>
</event>
@@ -642,7 +642,7 @@
<day>
<name>15</name>
<event>
- <p>Core-Mitglied zurckgetreten: <a
+ <p>Core-Mitglied zurckgetreten: <a
href="mailto:grog@FreeBSD.org">Greg Lehey</a> </p>
</event>
</day>
@@ -650,7 +650,7 @@
<day>
<name>10</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:mlaier@FreeBSD.org">Max Laier</a>
(src)</p>
</event>
@@ -659,13 +659,13 @@
<day>
<name>2</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:le@FreeBSD.org">Lukas Ertl</a>
(src)</p>
</event>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:pjd@FreeBSD.org">Pawel Jakub Dawidek</a>
(src)</p>
</event>
@@ -691,7 +691,7 @@
<name>21</name>
<event>
- <p>Neuer Committer: <a
+ <p>Neuer Committer: <a
href="mailto:philip@FreeBSD.org">Philip Paeps</a>
(src)</p>
</event>
@@ -701,7 +701,7 @@
href="mailto:cperciva@FreeBSD.org">Colin Percival</a>
(src)</p>
</event>
- </day>
+ </day>
<day>
<name>15</name>
diff --git a/de_DE.ISO8859-1/htdocs/news/2004/press.xml b/de_DE.ISO8859-1/htdocs/news/2004/press.xml
index d7f2ae0600..8d34e79f50 100644
--- a/de_DE.ISO8859-1/htdocs/news/2004/press.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2004/press.xml
@@ -34,7 +34,7 @@
derzeit die sichersten Betriebssysteme im Internet sind.</p>
</story>
</month>
-
+
<month>
<name>9</name>
diff --git a/de_DE.ISO8859-1/htdocs/news/2005/news.xml b/de_DE.ISO8859-1/htdocs/news/2005/news.xml
index 67c765d92b..25a275f076 100644
--- a/de_DE.ISO8859-1/htdocs/news/2005/news.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2005/news.xml
@@ -260,11 +260,11 @@
werden.</p>
</event>
</day>
- </month>
-
+ </month>
+
<month>
<name>10</name>
-
+
<day>
<name>30</name>
@@ -272,7 +272,7 @@
<p>Neuer Committer: <a
href="mailto:aaron@FreeBSD.org">Aaron Dalton</a> (ports)</p>
</event>
- </day>
+ </day>
<day>
<name>18</name>
@@ -281,7 +281,7 @@
<p>Neuer Committer: <a
href="mailto:ariff@FreeBSD.org">Ariff Abdullah</a> (src)</p>
</event>
- </day>
+ </day>
<day>
<name>11</name>
@@ -297,8 +297,8 @@
href="&enbase;/doc/de_DE.ISO8859-1/books/handbook/mirrors-ftp.html">
FreeBSD Spiegelseiten</a> vorhanden.</p>
</event>
- </day>
-
+ </day>
+
<day>
<name>6</name>
@@ -310,8 +310,8 @@
argentina.com</a>, beschreibt einen Internetprovider, der in einem
umkmpften Markt mit Hilfe von FreeBSD erfolgreich ist.</p>
</event>
- </day>
-
+ </day>
+
<day>
<name>5</name>
@@ -327,8 +327,8 @@
Kommentare und Vorschlge zu den neuen Seiten haben, senden
Sie diese bitte an die Mailingliste freebsd-www@FreeBSD.org.</p>
</event>
- </day>
-
+ </day>
+
<day>
<name>3</name>
@@ -347,8 +347,8 @@
href="mailto:az@FreeBSD.org">Andrej Zverev</a> (ports)</p>
</event>
</day>
- </month>
-
+ </month>
+
<month>
<name>9</name>
@@ -359,8 +359,8 @@
<p>Neuer Committer: <a
href="mailto:tmclaugh@FreeBSD.org">Tom McLaughlin</a> (ports)</p>
</event>
- </day>
-
+ </day>
+
<day>
<name>15</name>
@@ -380,7 +380,7 @@
6.0-BETA4-Ankndigung</a>.</p>
</event>
</day>
- </month>
+ </month>
<month>
<name>8</name>
@@ -486,7 +486,7 @@
</month>
<month>
-
+
<name>7</name>
<day>
@@ -639,7 +639,7 @@
<day>
<name>11</name>
-
+
<event>
<title>Code Freeze fr 6.0-RELEASE</title>
@@ -682,7 +682,7 @@
<day>
<name>26</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:thompsa@FreeBSD.org">Andrew Thompson</a> (src)</p>
@@ -759,7 +759,7 @@
</day>
</month>
- <month>
+ <month>
<name>4</name>
<day>
@@ -858,11 +858,11 @@
>FreeBSD Spiegelseiten</a> vorhanden.</p>
</event>
</day>
- </month>
+ </month>
- <month>
+ <month>
<name>3</name>
-
+
<day>
<name>31</name>
@@ -874,7 +874,7 @@
<day>
<name>20</name>
-
+
<event>
<title>FreeBSD&nbsp;5.4-BETA1 ist verfgbar</title>
@@ -906,7 +906,7 @@
der
<a href="&enbase;/snapshots/index.html">Snapshot-Seite</a>.</p>
</event>
- </day>
+ </day>
<day>
<name>12</name>
diff --git a/de_DE.ISO8859-1/htdocs/news/2005/press.xml b/de_DE.ISO8859-1/htdocs/news/2005/press.xml
index ccd65ad453..6fc0728bec 100644
--- a/de_DE.ISO8859-1/htdocs/news/2005/press.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2005/press.xml
@@ -92,7 +92,7 @@
<p>Ein Vergleich der Betriebssicherheit von Windows(r), Linux und
FreeBSD.</p>
</story>
-
+
<story>
<name>A Comparison of Solaris, Linux, and FreeBSD Kernels</name>
<url>http://www.opensolaris.org/os/article/2005-10-14_a_comparison_of_solaris__linux__and_freebsd_kernels/</url>
@@ -118,7 +118,7 @@
von drahtlosen Gerten.</p>
</story>
</month>
-
+
<month>
<name>9</name>
@@ -144,7 +144,7 @@
</story>
</month>
-
+
<month>
<name>8</name>
@@ -155,7 +155,7 @@
<site-url>http://www.zdnet.co.uk/</site-url>
<date>19. August 2005</date>
<author>Ingrid Marson</author>
- <p>Ein Interview mit Scott Long, dem FreeBSD Release Engineer,
+ <p>Ein Interview mit Scott Long, dem FreeBSD Release Engineer,
ber das bevorstehende FreeBSD-Release 6.0.</p>
</story>
</month>
@@ -184,7 +184,7 @@
<date>19. Juli 2005</date>
<author>Frank Pohlmann</author>
<p>Ein kurzer berblick ber die BSD-Familie.</p>
- </story>
+ </story>
<story>
<name>Project Evil: Windows network drivers on FreeBSD</name>
@@ -194,7 +194,7 @@
<date>15. Juli 2005</date>
<author>David Chisnall</author>
<p>Ein Artikel zur Nutzung von Windows(R)-Netzwerktreibern unter FreeBSD.</p>
- </story>
+ </story>
</month>
<month>
@@ -264,7 +264,7 @@
nun die aktuelle FreeBSD Version 5.4.</p>
</story>
</month>
-
+
<month>
<name>4</name>
@@ -277,7 +277,7 @@
<author>Ed Hurst</author>
<p>Ein Artikel ber die Nutzung von FreeBSD 5.4 auf Notebooks.</p>
</story>
-
+
<story>
<name>Large Web Hosting Provider Switches to FreeBSD</name>
<url>http://www.w3reports.com/index.php?itemid=869</url>
@@ -336,5 +336,5 @@
Core Teams, ber die SMPng-Implementierung von FreeBSD.</p>
</story>
</month>
- </year>
+ </year>
</press>
diff --git a/de_DE.ISO8859-1/htdocs/news/2006/news.xml b/de_DE.ISO8859-1/htdocs/news/2006/news.xml
index 84187fd7a7..f5d45270e4 100644
--- a/de_DE.ISO8859-1/htdocs/news/2006/news.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2006/news.xml
@@ -118,7 +118,7 @@
<p>Neuer Committer: <a
href="mailto:nivit@FreeBSD.org">Nicola Vitale</a> (ports)</p>
</event>
-
+
<event>
<title>Neuer Committer: <a
href="mailto:gabor@FreeBSD.org">G&aacute;bor Kvesd&aacute;n</a>
@@ -557,7 +557,7 @@
weitere Informationen lesen Sie bitte die <a
href="http://www.freebsdfoundation.org/press/20060705-PRrelease.shtml">
Presseerklrung</a> der FreeBSD Foundation.</p>
- </event>
+ </event>
</day>
</month>
@@ -902,7 +902,7 @@
href="&enbase;/news/status/report-jan-2006-mar-2006.html">
verfgbar</a>.</p>
</event>
-
+
<event>
<title>Summer of Code 2006</title>
diff --git a/de_DE.ISO8859-1/htdocs/news/2006/press.xml b/de_DE.ISO8859-1/htdocs/news/2006/press.xml
index c941a6ebfc..df45b566fe 100644
--- a/de_DE.ISO8859-1/htdocs/news/2006/press.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2006/press.xml
@@ -50,7 +50,7 @@
<site-url>http://www.openaddict.com/</site-url>
<date>08. Dezember 2006</date>
<author>Rich Morgan</author>
- <p>Eine Anleitung zur Konfiguration von FreeBSD 6.1 als
+ <p>Eine Anleitung zur Konfiguration von FreeBSD 6.1 als
Server mit Apache, Webmin, PHP 5, MySQL 5.0, Sendmail mit
SMTP-AUTH, Bind DNS, SNMP, sowie einem Zeitserver.</p>
</story>
diff --git a/de_DE.ISO8859-1/htdocs/news/2008/news.xml b/de_DE.ISO8859-1/htdocs/news/2008/news.xml
index 801f9d954e..e53e68cf72 100644
--- a/de_DE.ISO8859-1/htdocs/news/2008/news.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2008/news.xml
@@ -394,7 +394,7 @@
Budget von $&nbsp;80.000,-- zur Verfgung. Die
eingereichten
Projekte werden danach im Hinblick auf Notwendigkeit,
- technischen Anspruch und Kosteneffektivitt evaluiert
+ technischen Anspruch und Kosteneffektivitt evaluiert
werden.</p>
<p>Weitere Informationen zu diesem Thema finden Sie in der
@@ -411,7 +411,7 @@
<p>Neuer Committer: <a
href="mailto:rnoland@FreeBSD.org">Robert Noland</a> (ports)</p>
</event>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:vanhu@FreeBSD.org">Yvan Vanhullebus</a> (src)</p>
@@ -489,7 +489,7 @@
Services Division angekndigt, die Enterprise-Level-Support,
-Beratung und -Entwicklung fr &os; sowie PC-BSD bietet.</p>
</event>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:sson@FreeBSD.org">Stacey Son</a> (src)</p>
@@ -516,7 +516,7 @@
<p>Neuer Committer: <a
href="mailto:erik@FreeBSD.org">Erik Cederstrand</a> (projects)</p>
</event>
-
+
<event>
<title>FreeBSD-Technologie in Firefox 3</title>
@@ -683,7 +683,7 @@
href="http://wiki.FreeBSD.org/SummerOfCode2008">
Summer of Code Wiki</a> mit weiteren Informationen.</p>
</event>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:pgj@FreeBSD.org">G&aacute;bor P&aacute;li</a>
diff --git a/de_DE.ISO8859-1/htdocs/news/2009/news.xml b/de_DE.ISO8859-1/htdocs/news/2009/news.xml
index 5cbf3c27d6..cc0445bed6 100644
--- a/de_DE.ISO8859-1/htdocs/news/2009/news.xml
+++ b/de_DE.ISO8859-1/htdocs/news/2009/news.xml
@@ -133,7 +133,7 @@
<event>
<title>&os; 8.0-RC3 verfgbar</title>
-
+
<p>Der dritte Release Candidate des &os;-8.0-Entwicklungszyklusses
ist ab sofort <a
href="http://lists.freebsd.org/pipermail/freebsd-stable/2009-November/052699.html">verfgbar</a>.
@@ -304,7 +304,7 @@
<day>
<name>7</name>
-
+
<event>
<title>&os; 8.0-BETA1 verfgbar</title>
@@ -366,7 +366,7 @@
Martin und Ion-Mihai alles Gute fr ihre neuen Aufgaben.</p>
</event>
</day>
-
+
<day>
<name>3</name>
@@ -399,7 +399,7 @@
href="mailto:kmoore@FreeBSD.org">Kris Moore</a> (ports)</p>
</event>
</day>
-
+
<day>
<name>23</name>
@@ -451,45 +451,45 @@
<ul>
<li><a href="http://wiki.FreeBSD.org/AdityaSarawgi">Aditya Sarawgi</a>, <a href="http://wiki.FreeBSD.org/SOC2009AdityaSarawgi">Improving
Second Extended File system (ext2fs) and making it GPL free</a>
- (Mentor: <a href="http://wiki.FreeBSD.org/UlfLilleengen">Ulf Lilleengen</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/UlfLilleengen">Ulf Lilleengen</a>)
</li><li><a href="http://wiki.FreeBSD.org/AlejandroPulver">Alejandro Pulver</a>, <em>Ports license
infrastructure (part 2: integration)</em>
- (Mentor: <a href="http://wiki.FreeBSD.org/ErwinLansing">Erwin Lansing</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/ErwinLansing">Erwin Lansing</a>)
</li><li><a href="http://wiki.FreeBSD.org/AnaKukec">Ana Kukec</a>, <em>IPv6 Secure Neighbor Discovery
- native kernel APIs for FreeBSD</em>
- (Mentor: <a href="http://wiki.FreeBSD.org/BjoernZeeb">Bjoern Zeeb</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/BjoernZeeb">Bjoern Zeeb</a>)
</li><li><a href="http://wiki.FreeBSD.org/DavidForsythe">David Forsythe</a>, <em><a href="http://wiki.FreeBSD.org/SoC2009DavidForsythe">Package
tools rewrite via a new package library, with new
- features</a></em> (Mentor: <a href="http://wiki.FreeBSD.org/TimKientzle">Tim Kientzle</a>)
+ features</a></em> (Mentor: <a href="http://wiki.FreeBSD.org/TimKientzle">Tim Kientzle</a>)
</li><li><a class="nonexistent"
href="http://wiki.FreeBSD.org/EdwardTomaszNapierala">Edward Tomasz Napierala</a>, <em>Hierarchical
Resource Limits</em>
- (Mentor: <a href="http://wiki.FreeBSD.org/BrooksDavis">Brooks Davis</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/BrooksDavis">Brooks Davis</a>)
</li><li><a href="http://wiki.FreeBSD.org/FabioChecconi">Fabio Checconi</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009FabioChecconi">Geom-based
Disk Schedulers</a></em> (Mentor: <a class="nonexistent"
- href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>)
+ href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>)
</li><li><a href="http://wiki.FreeBSD.org/FangWang">Fang Wang</a>, <em>Implement TCP UTO</em>
- (Mentor: <a href="http://wiki.FreeBSD.org/RuiPaulo">Rui Paulo</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/RuiPaulo">Rui Paulo</a>)
</li><li><a href="http://wiki.FreeBSD.org/G%C3%A1borK%C3%B6vesd%C3%A1n">Gbor Kvesdn</a>, <em><a href="http://wiki.FreeBSD.org/G%C3%A1borSoC2009">BSD-licensed
libiconv in base system</a></em>
- (Mentor: <a href="http://wiki.FreeBSD.org/XinLi">Xin Li</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/XinLi">Xin Li</a>)
</li><li><a href="http://wiki.FreeBSD.org/GlebKurtsov">Gleb Kurtsov</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009GlebKurtsov">In
kernel stackable cryptographic filesystem (pefs)</a></em>
(Mentor: <a class="nonexistent"
- href="http://wiki.FreeBSD.org/StanislavSedov">Stanislav Sedov</a>)
+ href="http://wiki.FreeBSD.org/StanislavSedov">Stanislav Sedov</a>)
</li><li><a href="http://wiki.FreeBSD.org/IliasMarinos">Ilias Marinos</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009IliasMarinos">Application-Specific
Audit Trails</a></em>
- (Mentor: <a href="http://wiki.FreeBSD.org/RobertWatson">Robert Watson</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/RobertWatson">Robert Watson</a>)
</li><li><a href="http://wiki.FreeBSD.org/MartaCarbone">Marta Carbone</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009MartaCarbone">Ipfw
and dummynet improvements</a></em> (Mentor: <a class="nonexistent"
- href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>)
+ href="http://wiki.FreeBSD.org/LuigiRizzo">Luigi Rizzo</a>)
</li><li><a href="http://wiki.FreeBSD.org/NikhilBysani">Nikhil Bysani</a>, <em>Porting <a class="nonexistent"
href="http://wiki.FreeBSD.org/NetworkManager">NetworkManager</a> to FreeBSD</em>
- (Mentor: <a href="http://wiki.FreeBSD.org/EdSchouten">Ed Schouten</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/EdSchouten">Ed Schouten</a>)
</li><li><a href="http://wiki.FreeBSD.org/P%C3%A1liG%C3%A1borJ%C3%A1nos">Pli Gbor Jnos</a>, <em><a href="http://wiki.FreeBSD.org/PGJSoC2009">Design
and Implementation of Subsystem Support Libraries for Monitoring
and Management</a></em>
- (Mentor: <a href="http://wiki.FreeBSD.org/OleksandrTymoshenko">Oleksandr Tymoshenko</a>)
+ (Mentor: <a href="http://wiki.FreeBSD.org/OleksandrTymoshenko">Oleksandr Tymoshenko</a>)
</li><li><a href="http://wiki.FreeBSD.org/PrashantVaibhav">Prashant Vaibhav</a>, <em><a href="http://wiki.FreeBSD.org/SOC2009PrashantVaibhav">Reworking
the callout scheme: towards a tickless kernel</a></em>
(Mentor: <a href="http://wiki.FreeBSD.org/EdMaste">Ed Maste</a>)
@@ -528,7 +528,7 @@
</event>
</day>
- <day>
+ <day>
<name>7</name>
<event>
@@ -540,7 +540,7 @@
</event>
</day>
- <day>
+ <day>
<name>5</name>
<event>
@@ -596,7 +596,7 @@
<event>
<title>DCBSDCon-Videos geposted</title>
-
+
<p>Alle technischen Vortrge der krzlich abgehaltenen <a
href="http://www.dcbsdcon.org">DCBSDCon 2009</a>-Konferenz wurden
aufgezeichnet und sind ab sofort im <a
@@ -725,7 +725,7 @@
<event>
<title>FreeBSD auf Twitter</title>
-
+
<p>Auf Twitter gibt es inzwischen eine Anzahl halb-offizieller
Streams mit aktuellen Nachrichten zum FreeBSD Project. Der
Stream <a
@@ -833,7 +833,7 @@
<event>
<title>Video &quot;FreeBSD Kernel Internals&quot;
verffentlicht</title>
-
+
<p>Die erste Vorlesung von Kirk McKusick's <a
href="http://www.youtube.com/watch?v=nwbqBdghh6E">FreeBSD
Kernel Internals</a> wurde in voller Lnge im <a
diff --git a/de_DE.ISO8859-1/htdocs/platforms/x86-64.sgml b/de_DE.ISO8859-1/htdocs/platforms/x86-64.sgml
index df046c3660..841a5ea77c 100644
--- a/de_DE.ISO8859-1/htdocs/platforms/x86-64.sgml
+++ b/de_DE.ISO8859-1/htdocs/platforms/x86-64.sgml
@@ -10,7 +10,7 @@
<head>
<meta http-equiv="refresh" content="5;url=&base;/platforms/amd64.html"/>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-
+
<title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
diff --git a/de_DE.ISO8859-1/htdocs/projects/Makefile b/de_DE.ISO8859-1/htdocs/projects/Makefile
index 4f96d91bc1..586e288d52 100644
--- a/de_DE.ISO8859-1/htdocs/projects/Makefile
+++ b/de_DE.ISO8859-1/htdocs/projects/Makefile
@@ -3,7 +3,7 @@
#
# $FreeBSD$
# $FreeBSDde: de-www/projects/Makefile,v 1.3 2007/08/29 08:47:34 as Exp $
-# basiert auf: 1.31
+# basiert auf: 1.31
.if exists(../Makefile.conf)
.include "../Makefile.conf"
diff --git a/de_DE.ISO8859-1/share/sgml/catalog b/de_DE.ISO8859-1/share/sgml/catalog
index e034ecc302..7d0e154ffd 100644
--- a/de_DE.ISO8859-1/share/sgml/catalog
+++ b/de_DE.ISO8859-1/share/sgml/catalog
@@ -3,7 +3,7 @@
-- ...................................................................... --
-- German specific ...................................................... --
-
+
-- $FreeBSD$ --
-- $FreeBSDde: de-docproj/share/sgml/catalog,v 1.10 2004/11/28 18:16:45 jkois Exp $ --
-- basiert auf: 1.5 --
diff --git a/de_DE.ISO8859-1/share/sgml/freebsd.dsl b/de_DE.ISO8859-1/share/sgml/freebsd.dsl
index 3a51f0c6bc..74af03800a 100644
--- a/de_DE.ISO8859-1/share/sgml/freebsd.dsl
+++ b/de_DE.ISO8859-1/share/sgml/freebsd.dsl
@@ -10,15 +10,15 @@
<!ENTITY % freebsd.l10n PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN">
%freebsd.l10n;
-<!ENTITY % output.html "IGNORE">
+<!ENTITY % output.html "IGNORE">
<!ENTITY % output.print "IGNORE">
]>
<style-sheet>
<style-specification use="docbook">
<style-specification-body>
-
- <![ %output.html; [
+
+ <![ %output.html; [
(define ($email-footer$)
(make sequence
diff --git a/de_DE.ISO8859-1/share/sgml/news.xml b/de_DE.ISO8859-1/share/sgml/news.xml
index 4b140ce32a..536ce01a08 100644
--- a/de_DE.ISO8859-1/share/sgml/news.xml
+++ b/de_DE.ISO8859-1/share/sgml/news.xml
@@ -50,7 +50,7 @@
</event>
</day>
</month>
-
+
<month>
<name>7</name>
@@ -82,8 +82,8 @@
href="&enbase;/doc/de_DE.ISO8859-1/books/handbook/mirrors-ftp.html">&os;
Spiegelservern</a> vorhanden.</p>
</event>
- </day>
-
+ </day>
+
<day>
<name>11</name>
@@ -117,7 +117,7 @@
</event>
</day>
</month>
-
+
<month>
<name>6</name>
@@ -167,11 +167,11 @@
<p>Neuer Committer: <a
href="mailto:tj@FreeBSD.org">Tom Judge</a> (ports)</p>
</event>
- </day>
+ </day>
<day>
<name>12</name>
-
+
<event>
<title>Statusreport Januar-Mrz 2012</title>
@@ -181,7 +181,7 @@
</event>
</day>
</month>
-
+
<month>
<name>4</name>
@@ -268,7 +268,7 @@
</event>
</day>
</month>
-
+
<month>
<name>3</name>
@@ -313,7 +313,7 @@
</event>
</day>
</month>
-
+
<month>
<name>2</name>
@@ -376,7 +376,7 @@
<p>Neuer Committer: <a
href="mailto:davide@FreeBSD.org">Davide Italiano</a> (src)</p>
</event>
-
+
<event>
<title>Statusreport Oktober-Dezember 2011</title>
@@ -385,13 +385,13 @@
href="&enbase;/news/status/report-2011-10-2011-12.html">verfgbar</a>.</p>
</event>
</day>
-
+
<day>
<name>12</name>
-
+
<event>
<title>&os; 9.0-RELEASE verfgbar</title>
-
+
<p><a href="&enbase;/releases/9.0R/announce.html">FreeBSD
9.0-RELEASE</a> ist verfgbar. Lesen Sie
bitte die <a
@@ -408,7 +408,7 @@
</day>
</month>
</year>
-
+
<year>
<name>2011</name>
@@ -444,7 +444,7 @@
aktualisieren.</p>
</event>
</day>
-
+
<day>
<name>8</name>
@@ -453,7 +453,7 @@
href="mailto:pfg@FreeBSD.org">Pedro Giffuni</a> (src)</p>
</event>
</day>
-
+
<day>
<name>2</name>
@@ -496,7 +496,7 @@
aktualisieren.</p>
</event>
</day>
-
+
<day>
<name>12</name>
@@ -734,7 +734,7 @@
href="mailto:gavin@FreeBSD.org">Gavin Atkinson</a> (src, doc)</p>
</event>
</day>
-
+
<day>
<name>15</name>
@@ -780,7 +780,7 @@
<event>
<title>IPv6-Test-Images fr &os;</title>
-
+
<p>Die &os; Foundation und iXsystems haben reine
IPv6-Test-Images fr &os; und PC-BSD <a
href="http://www.prweb.com/releases/2011/6/prweb8529718.htm">
@@ -831,10 +831,10 @@
<month>
<name>4</name>
-
+
<day>
<name>27</name>
-
+
<event>
<title>Statusreport Januar-Mrz 2011</title>
@@ -859,7 +859,7 @@
<day>
<name>27</name>
-
+
<event>
<title>Das FreeBSD Project nimmt am Google Summer of
Code 2011 teil</title>
@@ -939,7 +939,7 @@
<event>
<title>FreeBSD 8.2-RELEASE verfgbar</title>
-
+
<p><a href="&enbase;/releases/8.2R/announce.html">FreeBSD
8.2-RELEASE</a> wurde verffentlicht. Lesen Sie
bitte die <a
@@ -1142,7 +1142,7 @@
<day>
<name>27</name>
-
+
<event>
<title>Statusreport Juli-September 2010 verfgbar</title>
@@ -1217,7 +1217,7 @@
href="mailto:swills@FreeBSD.org">Steve Wills</a> (ports)</p>
</event>
</day>
- </month>
+ </month>
<month>
<name>8</name>
@@ -1248,7 +1248,7 @@
href="mailto:ohauer@FreeBSD.org">Oliver Hauer</a> (ports)</p>
</event>
</day>
- </month>
+ </month>
<month>
<name>7</name>
@@ -1295,10 +1295,10 @@
<day>
<name>22</name>
-
+
<event>
<title>Statusreport April-Juni 2010 verfgbar</title>
-
+
<p>Der Statusreport fr die Monate April bis Juni 2010
mit 47 Eintrgen ist ab sofort <a
href="&enbase;/news/status/report-2010-04-2010-06.html">verfgbar</a>.</p>
@@ -1335,7 +1335,7 @@
<day>
<name>17</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:tijl@FreeBSD.org">Tijl Coosemans</a> (src)</p>
@@ -1353,7 +1353,7 @@
<day>
<name>14</name>
-
+
<event>
<title>Neues &os; Core Team gewhlt</title>
@@ -1388,20 +1388,20 @@
href="&enbase;/doc/de_DE.ISO8859-1/books/handbook/mirrors-ftp.html">&os;
Spiegelservern</a> vorhanden. Lesen Sie bitte auch die offizielle <a
href="&lists.stable;/2010-July/057552.html">Ankndigung</a>
- fr weitere Informationen zu dieser neuen Version.</p>
+ fr weitere Informationen zu dieser neuen Version.</p>
</event>
</day>
- </month>
+ </month>
<month>
<name>6</name>
<day>
<name>18</name>
-
+
<event>
<title>&os; 8.1-RC1 verfgbar</title>
-
+
<p>Der erste Release Candidate aus dem
&os;-8.1-Releasezyklus ist nun verfgbar. ISO-Images
fr Tier-1-Architekturen finden Sie wie immer auf den
@@ -1433,21 +1433,21 @@
<day>
<name>4</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:mdf@FreeBSD.org">Matthew Fleming</a> (src)</p>
</event>
</day>
-
+
<day>
<name>3</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:ae@FreeBSD.org">Andrey V. Elsukov</a> (src)</p>
</event>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:taras@FreeBSD.org">Taras Korenko</a> (doc/ru, www/ru)</p>
@@ -1506,7 +1506,7 @@
<day>
<name>19</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:jchandra@FreeBSD.org">Jayachandran C.</a> (src)</p>
@@ -1528,7 +1528,7 @@
<day>
<name>22</name>
-
+
<event>
<title>Statusreport Januar-Mrz 2010 verfgbar</title>
@@ -1616,7 +1616,7 @@
<day>
<name>31</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:decke@FreeBSD.org">Bernhard Frhlich</a> (ports)</p>
@@ -1625,7 +1625,7 @@
<day>
<name>23</name>
-
+
<event>
<title>&os; 7.3-RELEASE verfgbar</title>
@@ -1670,7 +1670,7 @@
<day>
<name>4</name>
-
+
<event>
<title>&os; 7.3-RC2 verfgbar</title>
@@ -1686,7 +1686,7 @@
<day>
<name>3</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:neel@FreeBSD.org">Neel Natu</a> (src)</p>
@@ -1718,7 +1718,7 @@
<day>
<name>15</name>
-
+
<event>
<title>&os; 7.3-RC1 verfgbar</title>
@@ -1744,16 +1744,16 @@
<day>
<name>6</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:bschmidt@FreeBSD.org">Bernhard Schmidt</a> (src)</p>
</event>
</day>
-
+
<day>
<name>2</name>
-
+
<event>
<title>Erweiterte Commit-Privilegien: <a
href="mailto:gabor@FreeBSD.org">G&aacute;bor
@@ -1775,7 +1775,7 @@
<day>
<name>30</name>
-
+
<event>
<title>&os; 7.3-BETA1 verfgbar</title>
@@ -1790,7 +1790,7 @@
<day>
<name>29</name>
-
+
<event>
<p>Neuer Committer: <a
href="mailto:brucec@FreeBSD.org">Bruce Cran</a> (src)</p>
diff --git a/de_DE.ISO8859-1/share/sgml/trademarks.ent b/de_DE.ISO8859-1/share/sgml/trademarks.ent
index cd69285367..7131bc6810 100644
--- a/de_DE.ISO8859-1/share/sgml/trademarks.ent
+++ b/de_DE.ISO8859-1/share/sgml/trademarks.ent
@@ -288,16 +288,16 @@
</orderedlist>
<important>
- <para>THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION
- PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
- BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
- THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
- ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
- TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
+ <para>THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION
+ PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
+ BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+ FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
+ THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT,
+ INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+ BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
+ OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
+ TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.</para>
</important>
diff --git a/el_GR.ISO8859-7/articles/compiz-fusion/article.sgml b/el_GR.ISO8859-7/articles/compiz-fusion/article.sgml
index ff572f153b..edbe6f4e09 100644
--- a/el_GR.ISO8859-7/articles/compiz-fusion/article.sgml
+++ b/el_GR.ISO8859-7/articles/compiz-fusion/article.sgml
@@ -11,7 +11,7 @@
Installing and Using compiz-fusion in FreeBSD
The FreeBSD Greek Documentation Project
-
+
%SOURCE% en_US.ISO8859-1/articles/compiz-fusion/article.sgml
%SRCID% 1.6
@@ -66,8 +66,8 @@
<title></title>
<para>H <application>Compiz&nbsp;Fusion</application>
- Ports, .
- , , ,
+ Ports, .
+ , , ,
port.
<application>&xorg;</application> server
, nVidia ,
diff --git a/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml b/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml
index 35b86a48c0..fbc7135377 100644
--- a/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml
+++ b/el_GR.ISO8859-7/articles/dialup-firewall/article.sgml
@@ -213,7 +213,7 @@ fwcmd="/sbin/ipfw"
oif="tun0"
# Define our inside interface. This is usually your network
-# card. Be sure to change this to match your own network
+# card. Be sure to change this to match your own network
# interface.
iif="fxp0"
diff --git a/el_GR.ISO8859-7/articles/formatting-media/article.sgml b/el_GR.ISO8859-7/articles/formatting-media/article.sgml
index d93dac4bbd..f3cdf21090 100644
--- a/el_GR.ISO8859-7/articles/formatting-media/article.sgml
+++ b/el_GR.ISO8859-7/articles/formatting-media/article.sgml
@@ -74,7 +74,7 @@
<para> (modes) :</para>
- <itemizedlist>
+ <itemizedlist>
<listitem>
<para><firstterm> (compatibility
mode)</firstterm>:
@@ -109,7 +109,7 @@
() (partitions) .
.
- root.
+ root.
2-3 <command>sysinstall</command>
.</para>
@@ -128,7 +128,7 @@
<listitem>
<para> (compatibility mode):
(slice table)
- .
+ .
.</para>
</listitem>
@@ -157,8 +157,8 @@
<listitem>
<para> (slice): .
- PC 4 .
- (sectors).
+ PC 4 .
+ (sectors).
<quote> </quote> (slice table)
BIOS .
@@ -175,7 +175,7 @@
.
disklabel.</para>
</listitem>
-
+
<listitem>
<para> (sector): .
512 bytes.</para>
@@ -246,11 +246,11 @@
<procedure>
<step>
- <para> sysinstall root
+ <para> sysinstall root
<informalexample>
<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
- </informalexample>
+ </informalexample>
.</para>
</step>
@@ -271,12 +271,12 @@
<step>
<para> FreeBSD,
<command>A</command>.</para>
- </step>
+ </step>
<step>
<para> (Do you
still want to do this) <command>Yes</command>.</para>
- </step>
+ </step>
<step>
<para> <command>Write</command>.</para>
@@ -359,7 +359,7 @@
<para> disklabel
partitions ( swap) :</para>
-
+
<informalexample>
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/ad2 count=2</userinput>
&prompt.root; <userinput>disklabel /dev/ad2 > /tmp/label</userinput>
@@ -397,7 +397,7 @@
<informalexample>
<screen>&prompt.root; <userinput>/stand/sysinstall</userinput></screen>
- </informalexample>
+ </informalexample>
.</para>
</step>
@@ -418,10 +418,10 @@
<step>
<para> FreeBSD,
<command>A</command>.</para>
- </step>
+ </step>
<step>
- <para> :
+ <para> :
<informalexample>
<screen>Do you want to do this with a true partition entry so as to remain
@@ -454,7 +454,7 @@ drive(s)?</screen>
<step>
<para> <command>Label</command> Index menu.</para>
- </step>
+ </step>
<step>
<para> (
@@ -469,7 +469,7 @@ drive(s)?</screen>
! :
<informalexample>
- <screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
+ <screen>Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory</screen>
</informalexample>
.</para>
@@ -508,7 +508,7 @@ drive(s)?</screen>
</step>
<step>
- <para> newfs , `c'.
+ <para> newfs , `c'.
, swap.</para>
</step>
@@ -519,7 +519,7 @@ drive(s)?</screen>
<informalexample>
<programlisting>/dev/ad0b none swap sw 0 0</programlisting>
</informalexample>
-
+
<para> <filename>/dev/ad0b</filename>
.</para>
</step>
@@ -540,7 +540,7 @@ swapon: added /dev/da0b as swap space</screen>
<sect2>
<title> </title>
<!-- Should have specific tag -->
-
+
<para> : Renaud Waldura
(<email>renaud@softway.com</email>)</para>
diff --git a/el_GR.ISO8859-7/articles/gjournal-desktop/Makefile b/el_GR.ISO8859-7/articles/gjournal-desktop/Makefile
index af8057d21c..bb5ce632fb 100644
--- a/el_GR.ISO8859-7/articles/gjournal-desktop/Makefile
+++ b/el_GR.ISO8859-7/articles/gjournal-desktop/Makefile
@@ -2,7 +2,7 @@
# $FreeBSD$
#
# Article: Implementing UFS journaling on a desktop PC
-#
+#
# %SOURCE% en_US.ISO8859-1/articles/gjournal-desktop/Makefile
# %SRCID% 1.1
#
diff --git a/el_GR.ISO8859-7/articles/laptop/article.sgml b/el_GR.ISO8859-7/articles/laptop/article.sgml
index 7ce757ee5e..f0c2dc0d1c 100644
--- a/el_GR.ISO8859-7/articles/laptop/article.sgml
+++ b/el_GR.ISO8859-7/articles/laptop/article.sgml
@@ -72,9 +72,9 @@
<ulink url="http://tuxmobil.org/mobile_bsd.html"></ulink>.</para>
- <sect1 id="xorg">
+ <sect1 id="xorg">
<title> &xorg;</title>
-
+
<para> <application>&xorg;</application>
. (acceleration)
@@ -119,9 +119,9 @@
<para> <filename>xorg.conf</filename>,
<literal>InputDevice</literal>.</para>
- </sect1>
+ </sect1>
- <sect1 id="modems">
+ <sect1 id="modems">
<title>Modems</title>
<para> (on-board) .
@@ -139,9 +139,9 @@
USB
. , ( win-)
.</para>
- </sect1>
+ </sect1>
- <sect1 id="pcmcia">
+ <sect1 id="pcmcia">
<title> PCMCIA (PC Card)</title>
<para> PCMCIA (
@@ -199,9 +199,9 @@
PCI BIOS).
&os;,
.</para>
- </sect1>
+ </sect1>
- <sect1 id="power-management">
+ <sect1 id="power-management">
<title>Power management</title>
<para>, power management
diff --git a/el_GR.ISO8859-7/articles/new-users/article.sgml b/el_GR.ISO8859-7/articles/new-users/article.sgml
index 6186a0d87d..85876260b0 100644
--- a/el_GR.ISO8859-7/articles/new-users/article.sgml
+++ b/el_GR.ISO8859-7/articles/new-users/article.sgml
@@ -1017,7 +1017,7 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
(single
user mode). <command>su
-m</command> <username>root</username>, <command>tcsh</command>
- <username>root</username>, .
+ <username>root</username>, .
<filename>.tcshrc</filename> </para>
<programlisting>alias su su -m</programlisting>
@@ -1045,7 +1045,7 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
<para>set prompt = "%h %t %~ %# "</para>
<para> set prompt
- , "if($?prompt) then" .
+ , "if($?prompt) then" .
,
prompt .
. tcsh
@@ -1068,12 +1068,12 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
<command>/sbin/umount /cdrom</command>,
,
<command>/sbin/mount_cd9660 /dev/cd0a /cdrom</command>
- <hardware>cd0a</hardware> CDROM.
+ <hardware>cd0a</hardware> CDROM.
FreeBSD CDROM
<command>/sbin/mount /cdrom</command>.</para>
<para> live &mdash; CDROM
- FreeBSD&mdash; .
+ FreeBSD&mdash; .
live .
CDROM.
<command>lndir</command>,
diff --git a/el_GR.ISO8859-7/books/faq/Makefile b/el_GR.ISO8859-7/books/faq/Makefile
index 160d11646b..071210c072 100644
--- a/el_GR.ISO8859-7/books/faq/Makefile
+++ b/el_GR.ISO8859-7/books/faq/Makefile
@@ -1,4 +1,4 @@
-#
+#
# $FreeBSD$
#
# FreeBSD FAQ
@@ -18,8 +18,8 @@ INSTALL_ONLY_COMPRESSED?=
WITH_BIBLIOXREF_TITLE?=YES
-#
-# SRCS SGML .
+#
+# SRCS SGML .
# rebuild.
#
diff --git a/el_GR.ISO8859-7/books/faq/book.sgml b/el_GR.ISO8859-7/books/faq/book.sgml
index a86f0cdcac..376be73920 100644
--- a/el_GR.ISO8859-7/books/faq/book.sgml
+++ b/el_GR.ISO8859-7/books/faq/book.sgml
@@ -5286,7 +5286,7 @@ kern.sched.name: 4BSD</screen>
for both, move the parent partition as described above,
then move the child partition into the empty directory
that the first move created:</para>
-
+
<screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
&prompt.root; <userinput>mount /dev/ad1s1a /mnt</userinput>
&prompt.root; <userinput>cd /mnt</userinput>
@@ -5753,7 +5753,7 @@ C:\="DOS"</programlisting>
<para>Booting &os; using GRUB is very simple. Just
add the following to your configuration file
<filename>/boot/grub/grub.conf</filename>.</para>
-
+
<programlisting>title FreeBSD 6.1
root (hd0,a)
kernel /boot/loader
@@ -5926,7 +5926,7 @@ C:\="DOS"</programlisting>
<para>I burned a CD under FreeBSD and now I can not read it
under any other operating system. Why?</para>
</question>
-
+
<answer>
<para>You most likely burned a raw file to your CD, rather
than creating an ISO 9660 filesystem. Take a look at the
@@ -6022,7 +6022,7 @@ C:\="DOS"</programlisting>
</step>
<step>
- <para>If you are running &os; 5.X or later, you will need to alter
+ <para>If you are running &os; 5.X or later, you will need to alter
<filename>/etc/devfs.conf</filename> to make these changes
permanent across reboots.</para>
@@ -6161,7 +6161,7 @@ perm /dev/acd0 0660</programlisting>
<para>Disk manufacturers calculate gigabytes as a billion bytes
each, whereas &os; calculates them as 1,073,741,824 bytes
each. This explains why, for example, &os;'s boot messages
- will report a disk that supposedly has 80GB as holding
+ will report a disk that supposedly has 80GB as holding
76319MB.</para>
<para>Also note that &os; will (by default)
<link linkend="disk-more-than-full">reserve</link> 8% of the disk
@@ -6910,7 +6910,7 @@ options SYSVMSG # enable for messaging</programlisting>
<answer>
<para>The reason why <filename>.shosts</filename>
authentication does not work by default in more recent
- versions of FreeBSD is because &man.ssh.1;
+ versions of FreeBSD is because &man.ssh.1;
is not installed suid <username>root</username> by default. To
<quote>fix</quote> this, you can do one of the
following:</para>
@@ -7104,7 +7104,7 @@ options SYSVMSG # enable for messaging</programlisting>
period, it was basically only provided as a reference
platform, as it had suffered greatly from bitrot over
the years.</para>
-
+
<para>However, early in 2004, some XFree86 developers left
that project
over issues including the pace of code changes, future
@@ -7715,7 +7715,7 @@ UserConfig&gt; <userinput>quit</userinput></screen>
<application>&xorg;</application>.
If you want to run a different X11 implementation
than the default one, add the following line to
- <filename>/etc/make.conf</filename>, (if you
+ <filename>/etc/make.conf</filename>, (if you
do not have this file, create it):</para>
<programlisting>X_WINDOW_SYSTEM= xorg</programlisting>
@@ -8053,7 +8053,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
<answer>
<para>If the alias is on the same subnet as an address
- already configured on the interface, then add
+ already configured on the interface, then add
<literal>netmask 0xffffffff</literal> to your
&man.ifconfig.8; command-line, as in the following:</para>
@@ -11213,7 +11213,7 @@ raisechar=^^</programlisting>
<para><emphasis>And then I was enlightened :-)</emphasis></para>
</answer>
</qandaentry>
-
+
<qandaentry>
<question id="dev-null">
<para>Where does data written to <filename>/dev/null</filename>
@@ -11286,7 +11286,7 @@ raisechar=^^</programlisting>
<para>At this time, there is only one book on FreeBSD-specific OS
internals, namely <quote>The Design and Implementation of the
FreeBSD Operating System</quote> by Marshall Kirk McKusick and
- George V. Neville-Neil, ISBN 0-201-70245-2, which
+ George V. Neville-Neil, ISBN 0-201-70245-2, which
focuses on version 5.X of FreeBSD.</para>
<para>Additionally, much general &unix; knowledge is directly
diff --git a/el_GR.ISO8859-7/books/handbook/Makefile b/el_GR.ISO8859-7/books/handbook/Makefile
index 0a3c88284f..04f0f7cc7e 100644
--- a/el_GR.ISO8859-7/books/handbook/Makefile
+++ b/el_GR.ISO8859-7/books/handbook/Makefile
@@ -22,7 +22,7 @@
# pgpkeyring This target will read the contents of
# pgpkeys/chapter.sgml and will extract all of
# the pgpkeys to standard out. This output can then
-# be redirected into a file and distributed as a
+# be redirected into a file and distributed as a
# public keyring of FreeBSD developers that can
# easily be imported into PGP/GPG.
#
diff --git a/el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml b/el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml
index 81583a5df6..3a10c8de95 100644
--- a/el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.sgml
@@ -2165,7 +2165,7 @@ hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:
<para>SDP involves communication between a SDP server and a SDP client.
The server maintains a list of service records that describe the
characteristics of services associated with the server. Each service
- record contains information about a single service. A client may
+ record contains information about a single service. A client may
retrieve information from a service record maintained by the SDP server
by issuing a SDP request. If the client, or an application associated
with the client, decides to use a service, it must open a separate
@@ -2179,7 +2179,7 @@ hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:
server's service records without any a priori information about the
services. This process of looking for any offered services is called
<emphasis>browsing</emphasis>.</para>
-
+
<para>The Bluetooth SDP server &man.sdpd.8; and command line client
&man.sdpcontrol.8; are included in the standard &os; installation.
The following example shows how to perform a SDP browse query.</para>
@@ -2595,7 +2595,7 @@ net.link.ether.bridge_cfg=<replaceable>if1</replaceable>,<replaceable>if2</repla
net.link.ether.bridge_ipfw=1</programlisting>
</sect2>
-
+
<sect2>
<title>Other Information</title>
@@ -2610,7 +2610,7 @@ net.link.ether.bridge_ipfw=1</programlisting>
<para>A bridge can add latency to your &man.ping.8; times, especially for
traffic from one segment to another.</para>
-
+
</sect2>
</sect1>
@@ -2743,7 +2743,7 @@ net.link.ether.bridge_ipfw=1</programlisting>
<para>Several operations need to be performed for a successful
bootstrap:</para>
-
+
<itemizedlist>
<listitem>
<para>The machine needs to obtain initial parameters such as its IP
diff --git a/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml b/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
index 80661a68da..73be8185b1 100644
--- a/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
@@ -1272,7 +1272,7 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
</sect3>
</sect2>
-<![ IGNORE [
+<![ IGNORE [
<sect2 id="docsnap">
<sect2info>
<authorgroup>
diff --git a/el_GR.ISO8859-7/books/handbook/disks/chapter.sgml b/el_GR.ISO8859-7/books/handbook/disks/chapter.sgml
index 4519efcdb0..c1c3b63b72 100644
--- a/el_GR.ISO8859-7/books/handbook/disks/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/disks/chapter.sgml
@@ -1288,7 +1288,7 @@ scsibus1:
charset you use with the <option>-C</option> option. For more
information, consult the &man.mount.cd9660.8; manual
page.</para>
-
+
<note>
<para>To be able to do this character conversion with the help
of the <option>-C</option> option, the kernel will require
@@ -3924,7 +3924,7 @@ device crypto</screen>
the data source for key file will be
<filename>/dev/random</filename>. The sector size of
<filename>/dev/da2.eli</filename>, which we call provider,
- will be 4kB.</para>
+ will be 4kB.</para>
<screen>&prompt.root; <userinput>dd if=/dev/random of=/root/da2.key bs=64 count=1</userinput>
&prompt.root; <userinput>geli init -s 4096 -K /root/da2.key /dev/da2</userinput>
@@ -4017,7 +4017,7 @@ geli_da2_flags="-p -k /root/da2.key"</screen>
<link linkend="configtuning-rcd">rc.d</link> section of the
Handbook.</para>
</sect3>
- </sect2>
+ </sect2>
</sect1>
diff --git a/el_GR.ISO8859-7/books/handbook/eresources/chapter.sgml b/el_GR.ISO8859-7/books/handbook/eresources/chapter.sgml
index 3f2f1f19c3..25905ad668 100644
--- a/el_GR.ISO8859-7/books/handbook/eresources/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/eresources/chapter.sgml
@@ -1915,7 +1915,7 @@
<application>Zope</application> &os;.
.
- <application>Zope</application> &os;
+ <application>Zope</application> &os;
.
.</para>
diff --git a/el_GR.ISO8859-7/books/handbook/kernelconfig/chapter.sgml b/el_GR.ISO8859-7/books/handbook/kernelconfig/chapter.sgml
index 8c734dcd0a..df8b91cb37 100644
--- a/el_GR.ISO8859-7/books/handbook/kernelconfig/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/kernelconfig/chapter.sgml
@@ -1086,7 +1086,7 @@ device splash # Splash screen and screen saver support</programlist
<para> (splash) !
().
- </para>
+ </para>
<programlisting># syscons is the default console driver, resembling an SCO console
device sc</programlisting>
@@ -1450,7 +1450,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl
<acronym>KVA</acronym>). , Intel
36bit ,
&pentium; Pro .</para>
-
+
<para> , (Physical Address
Extension, <acronym>PAE</acronym>) &intel; &pentium; Pro
CPU, 64 gigabytes. To &os;
@@ -1465,7 +1465,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl
<para> <acronym>PAE</acronym>
,
:</para>
-
+
<programlisting>options PAE</programlisting>
<note>
@@ -1479,7 +1479,7 @@ device fwe # Ethernet over FireWire (non-standard!)</programl
<para> <acronym>PAE</acronym> &os;
:</para>
-
+
<itemizedlist>
<listitem>
<para> 4
diff --git a/el_GR.ISO8859-7/books/handbook/linuxemu/chapter.sgml b/el_GR.ISO8859-7/books/handbook/linuxemu/chapter.sgml
index 842b07952d..b607aa9951 100644
--- a/el_GR.ISO8859-7/books/handbook/linuxemu/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/linuxemu/chapter.sgml
@@ -1235,7 +1235,7 @@ export PATH</programlisting>
<username>root</username>, shell script
<filename>root.sh</filename>. script
<filename>orainst</filename>.
- patch <filename>root.sh</filename>,
+ patch <filename>root.sh</filename>,
<command>chown</command>. ,
script Linux.</para>
@@ -1314,7 +1314,7 @@ export PATH</programlisting>
<title> ;</title>
<indexterm><primary>execution class loader</primary></indexterm>
- <para> &os; (abstraction)
+ <para> &os; (abstraction)
<quote>execution class loader</quote>.
&man.execve.2;.</para>
diff --git a/el_GR.ISO8859-7/books/handbook/mac/chapter.sgml b/el_GR.ISO8859-7/books/handbook/mac/chapter.sgml
index 158c8e0c63..dc5d148ae3 100644
--- a/el_GR.ISO8859-7/books/handbook/mac/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/mac/chapter.sgml
@@ -712,7 +712,7 @@ test: biba/high</screen>
implement the labeling feature, including the Biba, Lomac,
<acronym>MLS</acronym> and <acronym>SEBSD</acronym>
policies.</para>
-
+
<para>In many cases, the <option>multilabel</option> may not need
to be set at all. Consider the following situation and
security model:</para>
@@ -1586,7 +1586,7 @@ test: biba/low</screen>
utilities. While other users would be grouped into other
categories such as testers, designers, or just ordinary
users and would only be permitted read access.</para>
-
+
<para>With its natural security control, a lower integrity subject
is unable to write to a higher integrity subject; a higher
integrity subject cannot observe or read a lower integrity
@@ -1749,7 +1749,7 @@ mac_seeotheruids_load="YES"</programlisting>
<username>www</username> users into the insecure class:</para>
<screen>&prompt.root; <userinput>pw usermod nagios -L insecure</userinput></screen>
- <screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen>
+ <screen>&prompt.root; <userinput>pw usermod www -L insecure</userinput></screen>
</sect2>
<sect2>
diff --git a/el_GR.ISO8859-7/books/handbook/multimedia/chapter.sgml b/el_GR.ISO8859-7/books/handbook/multimedia/chapter.sgml
index d0202dd637..ea78f30ea7 100644
--- a/el_GR.ISO8859-7/books/handbook/multimedia/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/multimedia/chapter.sgml
@@ -111,7 +111,7 @@
<para> CD
&man.mount.8; '
, <emphasis>kernel
- panic</emphasis>.
+ panic</emphasis>.
ISO.</para>
</warning>
</sect1>
@@ -137,7 +137,7 @@
</sect1info>
<title> </title>
-
+
<sect2 id="sound-device">
<title> </title>
@@ -175,7 +175,7 @@
&soundblaster; Live!. modules
<filename>/boot/defaults/loader.conf</filename>.
-
+
, module
<filename>snd_driver</filename>:</para>
@@ -586,7 +586,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
MP3, CD
. CDDA (CD Digital
Audio) WAV.</para>
-
+
<para> <command>cdda2wav</command>,
<filename role="package">sysutils/cdrtools</filename>
@@ -602,7 +602,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
<para> <application>cdda2wav</application> CDROM
ATAPI (IDE). IDE,
SCSI.
- , 7 IDE:</para>
+ , 7 IDE:</para>
<screen>&prompt.root; <userinput>cdda2wav -D <replaceable>/dev/acd0</replaceable> -t 7</userinput></screen>
<para> <option>-D <replaceable>0,1,0</replaceable></option>
@@ -618,7 +618,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
<para> CD.
,
, :</para>
-
+
<screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 1+7</userinput></screen>
<para>
@@ -875,7 +875,7 @@ screen #0
Adaptor #0: "Savage Streams Engine"
number of ports: 1
port base: 43
- operations supported: PutImage
+ operations supported: PutImage
supported visuals:
depth 16, visualID 0x22
depth 16, visualID 0x23
@@ -1010,7 +1010,7 @@ no adaptors present</screen>
video &os; Linux.
beta.
video &os;
- :</para>
+ :</para>
<orderedlist>
@@ -1058,7 +1058,7 @@ no adaptors present</screen>
Linux.
port,
:</para>
-
+
<orderedlist>
<listitem>
@@ -1318,7 +1318,7 @@ zoom=yes</programlisting>
, .
<application>xine</application> XVideo.
</para>
-
+
<para> , <application>xine</application>
(GUI).
:</para>
@@ -1495,7 +1495,7 @@ WITH_MJPEG=yes -DWITH_XVID=yes</userinput></screen>
<para>,
,
:</para>
-
+
<programlisting>device bktr
device iicbus
device iicbb
@@ -1725,7 +1725,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
<para> , SCSI
USB. ,
.</para>
-
+
<sect3 id="scanners-kernel-usb">
<title> USB</title>
diff --git a/el_GR.ISO8859-7/books/handbook/network-servers/chapter.sgml b/el_GR.ISO8859-7/books/handbook/network-servers/chapter.sgml
index 5f114b42a6..f59c9f271c 100644
--- a/el_GR.ISO8859-7/books/handbook/network-servers/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/network-servers/chapter.sgml
@@ -3463,7 +3463,7 @@ zone "1.168.192.in-addr.arpa" {
<primary>BIND</primary>
<secondary>zone files</secondary>
</indexterm>
-
+
<para>An example master zone file for <hostid
role="domainname">example.org</hostid> (existing within
<filename>/etc/namedb/master/example.org</filename>) is as
diff --git a/el_GR.ISO8859-7/books/handbook/security/chapter.sgml b/el_GR.ISO8859-7/books/handbook/security/chapter.sgml
index fc321742d8..f2fc7a3f6b 100644
--- a/el_GR.ISO8859-7/books/handbook/security/chapter.sgml
+++ b/el_GR.ISO8859-7/books/handbook/security/chapter.sgml
@@ -81,7 +81,7 @@
<para> IPsec
<acronym>VPN</acronym> &os;/&windows;.</para>
</listitem>
-
+
<listitem>
<para> &os;
<acronym>SSH</acronym> <application>OpenSSH</application>
@@ -203,7 +203,7 @@
</indexterm>
<para>A user account compromise is even more common than a DoS
- attack. Many sysadmins still run standard
+ attack. Many sysadmins still run standard
<application>telnetd</application>, <application>rlogind</application>,
<application>rshd</application>,
and <application>ftpd</application> servers on their machines.
@@ -511,7 +511,7 @@
<application>rshd</application> or
<application>rlogind</application>, then turn off those
services!</para>
-
+
<para>&os; now defaults to running
<application>ntalkd</application>,
<application>comsat</application>, and
@@ -622,7 +622,7 @@
</indexterm>
<para>But even if you turn off the <devicename>bpf</devicename>
device, you still have
- <filename>/dev/mem</filename> and
+ <filename>/dev/mem</filename> and
<filename>/dev/kmem</filename>
to worry about. For that matter, the intruder can still write to
raw disk devices. Also, there is another kernel feature called
@@ -709,7 +709,7 @@
<para>When using ssh rather than NFS,
writing the security script is much more difficult. You
- essentially have to <command>scp</command> the scripts to the client
+ essentially have to <command>scp</command> the scripts to the client
box in order to
run them, making them visible, and for safety you also need to
<command>scp</command> the binaries (such as find) that those
@@ -792,7 +792,7 @@
<para>A common DoS attack scenario is attacking a forking server and
making it spawning so many child processes that the host system
eventually runs out of memory, file descriptors, etc. and then
- grinds to a halt. <application>inetd</application>
+ grinds to a halt. <application>inetd</application>
(see &man.inetd.8;) has several
options to limit this sort of attack. It should be noted that
while it is possible to prevent a machine from going down, it is
@@ -801,7 +801,7 @@
page carefully and pay
specific attention to the <option>-c</option>, <option>-C</option>,
and <option>-R</option> options. Note that spoofed-IP attacks
- will circumvent the <option>-C</option> option to
+ will circumvent the <option>-C</option> option to
<application>inetd</application>, so
typically a combination of options must be used. Some standalone
servers have self-fork-limitation parameters.</para>
@@ -887,7 +887,7 @@
Use the <application>sysctl</application>
variable <literal>net.inet.icmp.icmplim</literal> to limit these attacks.
The last major class of springboard
- attacks is related to certain internal
+ attacks is related to certain internal
<application>inetd</application> services such as the
udp echo service. An attacker simply spoofs a UDP packet with the
source address being server A's echo port, and the destination
@@ -895,7 +895,7 @@
on your LAN. The two servers then bounce this one packet back and
forth between each other. The attacker can overload both servers
and their LANs simply by injecting a few packets in this manner.
- Similar problems exist with the internal
+ Similar problems exist with the internal
<application>chargen</application> port. A
competent sysadmin will turn off all of these inetd-internal test
services.</para>
@@ -909,22 +909,22 @@
<command>netstat -rna | fgrep W3</command>. These routes
typically timeout in 1600 seconds or so. If the kernel detects
that the cached route table has gotten too big it will dynamically
- reduce the <varname>rtexpire</varname> but will never decrease it
- to less than <varname>rtminexpire</varname>. There are two
+ reduce the <varname>rtexpire</varname> but will never decrease it
+ to less than <varname>rtminexpire</varname>. There are two
problems:</para>
-
+
<orderedlist>
<listitem>
<para>The kernel does not react quickly enough when a lightly
loaded server is suddenly attacked.</para>
</listitem>
-
+
<listitem>
<para>The <varname>rtminexpire</varname> is not low enough for
the kernel to survive a sustained attack.</para>
</listitem>
</orderedlist>
-
+
<para>If your servers are connected to the Internet via a T3 or
better, it may be prudent to manually override both
<varname>rtexpire</varname> and <varname>rtminexpire</varname>
@@ -1018,11 +1018,11 @@
&unix; came into being was based on DES, the Data Encryption
Standard. This was not such a problem for users resident in
the US, but since the source code for DES could not be exported
- outside the US, &os; had to find a way to both comply with
+ outside the US, &os; had to find a way to both comply with
US law and retain compatibility with all the other &unix;
variants that still used DES.</para>
- <para>The solution was to divide up the encryption libraries
+ <para>The solution was to divide up the encryption libraries
so that US users could install the DES libraries and use
DES but international users still had an encryption method
that could be exported abroad. This is how &os; came to
@@ -1037,7 +1037,7 @@
functions. By default &os; uses MD5 to encrypt
passwords.</para>
- <para>It is pretty easy to identify which encryption method
+ <para>It is pretty easy to identify which encryption method
&os; is set up to use. Examining the encrypted passwords in
the <filename>/etc/master.passwd</filename> file is one way.
Passwords encrypted with the MD5 hash are longer than those
@@ -1180,7 +1180,7 @@ MOS MALL GOAT ARM AVID COED
<sect2>
<title>Insecure Connection Initialization</title>
-
+
<para>To initialize or change your secret password over an
insecure connection, you will need to already have a secure
connection to some place where you can run
@@ -1225,7 +1225,7 @@ GAME GAG WELT OUT DOWN CHAT
<sect2>
<title>Generating a Single One-time Password</title>
- <para>Once you have initialized OPIE and login, you will be
+ <para>Once you have initialized OPIE and login, you will be
presented with a prompt like this:</para>
<screen>&prompt.user; <userinput>telnet example.com</userinput>
@@ -1311,7 +1311,7 @@ Enter secret pass phrase: <userinput>&lt;secret password&gt;</userinput>
Please check &man.opieaccess.5;
for more information on this file and which security considerations
you should be aware of when using it.</para>
-
+
<para>Here is a sample <filename>opieaccess</filename> file:</para>
<programlisting>permit 192.168.0.0 255.255.0.0</programlisting>
@@ -1319,7 +1319,7 @@ Enter secret pass phrase: <userinput>&lt;secret password&gt;</userinput>
<para>This line allows users whose IP source address (which is
vulnerable to spoofing) matches the specified value and mask,
to use &unix; passwords at any time.</para>
-
+
<para>If no rules in <filename>opieaccess</filename> are matched,
the default is to deny non-OPIE logins.</para>
@@ -1340,7 +1340,7 @@ Enter secret pass phrase: <userinput>&lt;secret password&gt;</userinput>
<title>TCP Wrappers</title>
<indexterm><primary>TCP Wrappers</primary></indexterm>
-
+
<para>Anyone familiar with &man.inetd.8; has probably heard
of <acronym>TCP</acronym> Wrappers at some point. But few
individuals seem to fully comprehend its usefulness in a
@@ -1452,7 +1452,7 @@ qpopper : ALL : allow</programlisting>
configuration options known as <literal>wildcards</literal>,
expansion characters and external command execution. The
next two sections are written to cover these situations.</para>
-
+
<sect3>
<title>External Commands</title>
@@ -1613,28 +1613,28 @@ sendmail : PARANOID : deny</programlisting>
<sect2>
<title>Creating the Initial Database</title>
-
+
<para>This is done on the Kerberos server only. First make sure that
you do not have any old Kerberos databases around. You should change
to the directory <filename>/etc/kerberosIV</filename> and check that
only the following files are present:</para>
-
+
<screen>&prompt.root; <userinput>cd /etc/kerberosIV</userinput>
&prompt.root; <userinput>ls</userinput>
README krb.conf krb.realms</screen>
-
+
<para>If any additional files (such as <filename>principal.*</filename>
or <filename>master_key</filename>) exist, then use the
<command>kdb_destroy</command> command to destroy the old Kerberos
database, or if Kerberos is not running, simply delete the extra
files.</para>
-
+
<para>You should now edit the <filename>krb.conf</filename> and
<filename>krb.realms</filename> files to define your Kerberos realm.
In this case the realm will be <literal>EXAMPLE.COM</literal> and the
server is <hostid role="fqdn">grunt.example.com</hostid>. We edit
or create the <filename>krb.conf</filename> file:</para>
-
+
<screen>&prompt.root; <userinput>cat krb.conf</userinput>
EXAMPLE.COM
EXAMPLE.COM grunt.example.com admin server
@@ -1646,11 +1646,11 @@ ATHENA.MIT.EDU kerberos-3.mit.edu
LCS.MIT.EDU kerberos.lcs.mit.edu
TELECOM.MIT.EDU bitsy.mit.edu
ARC.NASA.GOV trident.arc.nasa.gov</screen>
-
+
<para>In this case, the other realms do not need to be there. They are
here as an example of how a machine may be made aware of multiple
realms. You may wish to not include them for simplicity.</para>
-
+
<para>The first line names the realm in which this system works. The
other lines contain realm/host entries. The first item on a line is a
realm, and the second is a host in that realm that is acting as a
@@ -1658,59 +1658,59 @@ ARC.NASA.GOV trident.arc.nasa.gov</screen>
server</literal> following a host's name means that host also
provides an administrative database server. For further explanation
of these terms, please consult the Kerberos manual pages.</para>
-
+
<para>Now we have to add <hostid role="fqdn">grunt.example.com</hostid>
to the <literal>EXAMPLE.COM</literal> realm and also add an entry to
put all hosts in the <hostid role="domainname">.example.com</hostid>
domain in the <literal>EXAMPLE.COM</literal> realm. The
<filename>krb.realms</filename> file would be updated as
follows:</para>
-
+
<screen>&prompt.root; <userinput>cat krb.realms</userinput>
grunt.example.com EXAMPLE.COM
.example.com EXAMPLE.COM
.berkeley.edu CS.BERKELEY.EDU
.MIT.EDU ATHENA.MIT.EDU
.mit.edu ATHENA.MIT.EDU</screen>
-
+
<para>Again, the other realms do not need to be there. They are here as
an example of how a machine may be made aware of multiple realms. You
may wish to remove them to simplify things.</para>
-
+
<para>The first line puts the <emphasis>specific</emphasis> system into
the named realm. The rest of the lines show how to default systems of
a particular subdomain to a named realm.</para>
-
+
<para>Now we are ready to create the database. This only needs to run
on the Kerberos server (or Key Distribution Center). Issue the
<command>kdb_init</command> command to do this:</para>
-
+
<screen>&prompt.root; <userinput>kdb_init</userinput>
<prompt>Realm name [default ATHENA.MIT.EDU ]:</prompt> <userinput>EXAMPLE.COM</userinput>
You will be prompted for the database Master Password.
It is important that you NOT FORGET this password.
-
+
<prompt>Enter Kerberos master key:</prompt> </screen>
-
+
<para>Now we have to save the key so that servers on the local machine
can pick it up. Use the <command>kstash</command> command to do
this:</para>
-
+
<screen>&prompt.root; <userinput>kstash</userinput>
-
+
<prompt>Enter Kerberos master key:</prompt>
Current Kerberos master key version is 1.
Master key entered. BEWARE!</screen>
-
+
<para>This saves the encrypted master password in
<filename>/etc/kerberosIV/master_key</filename>.</para>
</sect2>
-
+
<sect2>
<title>Making It All Run</title>
-
+
<indexterm>
<primary>KerberosIV</primary>
<secondary>initial startup</secondary>
@@ -1721,14 +1721,14 @@ Master key entered. BEWARE!</screen>
Their names are <literal>kpasswd</literal> and <literal>rcmd</literal>.
These two principals are made for each system, with the instance being
the name of the individual system.</para>
-
+
<para>These daemons, <application>kpasswd</application> and
<application>rcmd</application> allow other systems to change Kerberos
passwords and run commands like &man.rcp.1;,
&man.rlogin.1; and &man.rsh.1;.</para>
-
+
<para>Now let us add these entries:</para>
-
+
<screen>&prompt.root; <userinput>kdb_edit</userinput>
Opening database...
@@ -1781,7 +1781,7 @@ Edit O.K.
<sect2>
<title>Creating the Server File</title>
-
+
<para>We now have to extract all the instances which define the
services on each machine. For this we use the
<command>ext_srvtab</command> command. This will create a file
@@ -1818,7 +1818,7 @@ Generating 'grunt-new-srvtab'....</screen>
<screen>&prompt.root; <userinput>mv grumble-new-srvtab srvtab</userinput>
&prompt.root; <userinput>chmod 600 srvtab</userinput></screen>
</sect2>
-
+
<sect2>
<title>Populating the Database</title>
@@ -1857,14 +1857,14 @@ Edit O.K.
<sect2>
<title>Testing It All Out</title>
-
+
<para>First we have to start the Kerberos daemons. Note that if you
have correctly edited your <filename>/etc/rc.conf</filename> then this
will happen automatically when you reboot. This is only necessary on
the Kerberos server. Kerberos clients will automatically get what
they need from the <filename>/etc/kerberosIV</filename>
directory.</para>
-
+
<screen>&prompt.root; <userinput>kerberos &amp;</userinput>
Kerberos server starting
Sleep forever on error
@@ -1883,19 +1883,19 @@ regular kill instead
Current Kerberos master key version is 1.
Master key entered. BEWARE!</screen>
-
+
<para>Now we can try using the <command>kinit</command> command to get a
ticket for the ID <username>jane</username> that we created
above:</para>
-
+
<screen>&prompt.user; <userinput>kinit jane</userinput>
MIT Project Athena (grunt.example.com)
Kerberos Initialization for "jane"
<prompt>Password:</prompt> </screen>
-
+
<para>Try listing the tokens using <command>klist</command> to see if we
really have them:</para>
-
+
<screen>&prompt.user; <userinput>klist</userinput>
Ticket file: /tmp/tkt245
Principal: jane@EXAMPLE.COM
@@ -1904,7 +1904,7 @@ Principal: jane@EXAMPLE.COM
Apr 30 11:23:22 Apr 30 19:23:22 krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen>
<para>Now try changing the password using &man.passwd.1; to
- check if the <application>kpasswd</application> daemon can get
+ check if the <application>kpasswd</application> daemon can get
authorization to the Kerberos database:</para>
<screen>&prompt.user; <userinput>passwd</userinput>
@@ -1918,7 +1918,7 @@ Password changed.</screen>
<sect2>
<title>Adding <command>su</command> Privileges</title>
-
+
<para>Kerberos allows us to give <emphasis>each</emphasis> user
who needs <username>root</username> privileges their own
<emphasis>separate</emphasis> &man.su.1; password.
@@ -1928,7 +1928,7 @@ Password changed.</screen>
associated with a principal. Using <command>kdb_edit</command>
we can create the entry <literal>jane.root</literal> in the
Kerberos database:</para>
-
+
<screen>&prompt.root; <userinput>kdb_edit</userinput>
Opening database...
@@ -1957,27 +1957,27 @@ Principal's new key version = 1
<prompt>Attributes [ 0 ] ?</prompt>
Edit O.K.
<prompt>Principal name:</prompt> &lt;---- null entry here will cause an exit</screen>
-
+
<para>Now try getting tokens for it to make sure it works:</para>
-
+
<screen>&prompt.root; <userinput>kinit jane.root</userinput>
MIT Project Athena (grunt.example.com)
Kerberos Initialization for "jane.root"
<prompt>Password:</prompt></screen>
-
+
<para>Now we need to add the user to <username>root</username>'s
<filename>.klogin</filename> file:</para>
-
+
<screen>&prompt.root; <userinput>cat /root/.klogin</userinput>
jane.root@EXAMPLE.COM</screen>
-
+
<para>Now try doing the &man.su.1;:</para>
-
+
<screen>&prompt.user; <userinput>su</userinput>
<prompt>Password:</prompt></screen>
-
+
<para>and take a look at what tokens we have:</para>
-
+
<screen>&prompt.root; <userinput>klist</userinput>
Ticket file: /tmp/tkt_root_245
Principal: jane.root@EXAMPLE.COM
@@ -1988,7 +1988,7 @@ May 2 20:43:12 May 3 04:43:12 krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen>
<sect2>
<title>Using Other Commands</title>
-
+
<para>In an earlier example, we created a principal called
<literal>jane</literal> with an instance <literal>root</literal>.
This was based on a user with the same name as the principal, and this
@@ -1999,17 +1999,17 @@ May 2 20:43:12 May 3 04:43:12 krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen>
<username>root</username> if the necessary entries are in the
<filename>.klogin</filename> file in <username>root</username>'s
home directory:</para>
-
+
<screen>&prompt.root; <userinput>cat /root/.klogin</userinput>
jane.root@EXAMPLE.COM</screen>
-
+
<para>Likewise, if a user has in their own home directory lines of the
form:</para>
-
+
<screen>&prompt.user; <userinput>cat ~/.klogin</userinput>
jane@EXAMPLE.COM
jack@EXAMPLE.COM</screen>
-
+
<para>This allows anyone in the <literal>EXAMPLE.COM</literal> realm
who has authenticated themselves as <username>jane</username> or
<username>jack</username> (via <command>kinit</command>, see above)
@@ -2017,10 +2017,10 @@ jack@EXAMPLE.COM</screen>
account or files on this system (<hostid>grunt</hostid>) via
&man.rlogin.1;, &man.rsh.1; or
&man.rcp.1;.</para>
-
+
<para>For example, <username>jane</username> now logs into another system using
Kerberos:</para>
-
+
<screen>&prompt.user; <userinput>kinit</userinput>
MIT Project Athena (grunt.example.com)
<prompt>Password:</prompt>
@@ -2030,13 +2030,13 @@ Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
-
+
<para>Or <username>jack</username> logs into <username>jane</username>'s account on the same machine
(<username>jane</username> having
set up the <filename>.klogin</filename> file as above, and the person
in charge of Kerberos having set up principal
<emphasis>jack</emphasis> with a null instance):</para>
-
+
<screen>&prompt.user; <userinput>kinit</userinput>
&prompt.user; <userinput>rlogin grunt -l jane</userinput>
MIT Project Athena (grunt.example.com)
@@ -2952,7 +2952,7 @@ An optional company name []:<userinput><replaceable>Another Name</replaceable></
generate the <acronym>RSA</acronym> key:</para>
<screen>&prompt.root; <userinput>openssl dsaparam -rand -genkey -out <filename>myRSA.key</filename> 1024</userinput></screen>
-
+
<para>Next, generate the <acronym>CA</acronym> key:</para>
<screen>&prompt.root; <userinput>openssl gendsa -des3 -out <filename>myca.key</filename> <filename>myRSA.key</filename></userinput></screen>
@@ -3065,7 +3065,7 @@ Connection closed by foreign host.</screen>
<para>Creating a VPN between two networks, separated by the
Internet, using FreeBSD gateways.</para>
-
+
<sect2>
<sect2info>
<authorgroup>
@@ -3089,7 +3089,7 @@ Connection closed by foreign host.</screen>
IPsec, it is necessary that you are familiar with the concepts
of building a custom kernel (see
<xref linkend="kernelconfig"/>).</para>
-
+
<para><emphasis>IPsec</emphasis> is a protocol which sits on top
of the Internet Protocol (IP) layer. It allows two or more
hosts to communicate in a secure manner (hence the name). The
@@ -3135,12 +3135,12 @@ options FAST_IPSEC # new IPsec (cannot define w/ IPSEC)
options IPSEC_FILTERGIF #filter ipsec packets from a tunnel
</screen>
</note>
-
+
<indexterm>
<primary>IPsec</primary>
<secondary>ESP</secondary>
</indexterm>
-
+
<indexterm>
<primary>IPsec</primary>
<secondary>AH</secondary>
@@ -3166,11 +3166,11 @@ options IPSEC_FILTERGIF #filter ipsec packets from a tunnel
packet to be authenticated.</para>
</listitem>
</itemizedlist>
-
+
<para><acronym>ESP</acronym> and <acronym>AH</acronym> can
either be used together or separately, depending on the
environment.</para>
-
+
<indexterm>
<primary>VPN</primary>
</indexterm>
@@ -3189,7 +3189,7 @@ options IPSEC_FILTERGIF #filter ipsec packets from a tunnel
known as a <emphasis>Virtual Private Network (VPN)</emphasis>.
The &man.ipsec.4; manual page should be consulted for detailed
information on the IPsec subsystem in FreeBSD.</para>
-
+
<para>To add IPsec support to your kernel, add the following
options to your kernel configuration file:</para>
@@ -3223,25 +3223,25 @@ options IPSEC_DEBUG #debug for IP security
<sect2>
<title>The Problem</title>
-
+
<para>There is no standard for what constitutes a VPN. VPNs can
be implemented using a number of different technologies, each of
which have their own strengths and weaknesses. This section
presents a scenario, and the strategies used for implementing a
VPN for this scenario.</para>
</sect2>
-
- <sect2>
+
+ <sect2>
<title>The Scenario: Two networks, connected to the Internet, to
behave as one</title>
-
+
<indexterm>
<primary>VPN</primary>
<secondary>creating</secondary>
</indexterm>
<para>The premise is as follows:</para>
-
+
<itemizedlist>
<listitem>
<para>You have at least two sites</para>
@@ -3270,15 +3270,15 @@ options IPSEC_DEBUG #debug for IP security
configuration nightmare.</para>
</listitem>
</itemizedlist>
-
+
<para>If you find that you are trying to connect two networks,
both of which, internally, use the same private IP address range
(e.g. both of them use <hostid
role="ipaddr">192.168.1.x</hostid>), then one of the networks will
have to be renumbered.</para>
-
+
<para>The network topology might look something like this:</para>
-
+
<mediaobject>
<imageobject>
<imagedata fileref="security/ipsec-network" align="center"/>
@@ -3308,7 +3308,7 @@ Network #2 [ Internal Hosts ]
[ UNIX ]</literallayout>
</textobject>
</mediaobject>
-
+
<para>Notice the two public IP addresses. I will use the letters to
refer to them in the rest of this article. Anywhere you see those
letters in this article, replace them with your own public IP
@@ -3320,35 +3320,35 @@ Network #2 [ Internal Hosts ]
machines on the private networks have been configured to use the
<hostid role="ipaddr">.1</hostid> machine as their default
gateway.</para>
-
+
<para>The intention is that, from a network point of view, each
network should view the machines on the other network as though
they were directly attached the same router -- albeit a slightly
slow router with an occasional tendency to drop packets.</para>
-
+
<para>This means that (for example), machine <hostid
role="ipaddr">192.168.1.20</hostid> should be able to run</para>
-
+
<programlisting>ping 192.168.2.34</programlisting>
-
+
<para>and have it work, transparently. &windows; machines should
be able to see the machines on the other network, browse file
shares, and so on, in exactly the same way that they can browse
machines on the local network.</para>
-
+
<para>And the whole thing has to be secure. This means that
traffic between the two networks has to be encrypted.</para>
-
+
<para>Creating a VPN between these two networks is a multi-step
process. The stages are as follows:</para>
-
+
<orderedlist>
<listitem>
<para>Create a <quote>virtual</quote> network link between the two
networks, across the Internet. Test it, using tools like
&man.ping.8;, to make sure it works.</para>
</listitem>
-
+
<listitem>
<para>Apply security policies to ensure that traffic between
the two networks is transparently encrypted and decrypted as
@@ -3366,7 +3366,7 @@ Network #2 [ Internal Hosts ]
<sect3>
<title>Step 1: Creating and testing a <quote>virtual</quote>
network link</title>
-
+
<para>Suppose that you were logged in to the gateway machine on
network #1 (with public IP address <hostid
role="ipaddr">A.B.C.D</hostid>, private IP address <hostid
@@ -3400,7 +3400,7 @@ Network #2 [ Internal Hosts ]
role="ipaddr">192.168.2.1</hostid>.</para>
</listitem>
</orderedlist>
-
+
<para>You can think of this as requiring a <quote>tunnel</quote>
between the two networks. The two <quote>tunnel mouths</quote> are the IP
addresses <hostid role="ipaddr">A.B.C.D</hostid> and <hostid
@@ -3408,31 +3408,31 @@ Network #2 [ Internal Hosts ]
addresses of the private IP addresses that will be allowed to pass
through it. The tunnel is used to transfer traffic with private
IP addresses across the public Internet.</para>
-
+
<para>This tunnel is created by using the generic interface, or
<devicename>gif</devicename> devices on FreeBSD. As you can
imagine, the <devicename>gif</devicename> interface on each
gateway host must be configured with four IP addresses; two for
the public IP addresses, and two for the private IP
addresses.</para>
-
+
<para>Support for the gif device must be compiled in to the
&os; kernel on both machines. You can do this by adding the
line:</para>
-
+
<programlisting>device gif</programlisting>
-
+
<para>to the kernel configuration files on both machines, and
then compile, install, and reboot as normal.</para>
-
+
<para>Configuring the tunnel is a two step process. First the
tunnel must be told what the outside (or public) IP addresses
are, using &man.ifconfig.8;. Then the private IP addresses must be
configured using &man.ifconfig.8;.</para>
-
+
<para>On the gateway machine on network #1 you would run the
following commands to configure the tunnel.</para>
-
+
<screen>&prompt.root; <userinput>ifconfig <replaceable>gif0</replaceable> create</userinput>
&prompt.root; <userinput>ifconfig <replaceable>gif0</replaceable> tunnel <replaceable>A.B.C.D</replaceable> <replaceable>W.X.Y.Z</replaceable></userinput>
&prompt.root; <userinput>ifconfig <replaceable>gif0</replaceable> inet <replaceable>192.168.1.1</replaceable> <replaceable>192.168.2.1</replaceable> netmask <replaceable>0xffffffff</replaceable></userinput>
@@ -3445,14 +3445,14 @@ Network #2 [ Internal Hosts ]
&prompt.root; <userinput>ifconfig <replaceable>gif0</replaceable> tunnel <replaceable>W.X.Y.Z</replaceable> <replaceable>A.B.C.D</replaceable></userinput>
&prompt.root; <userinput>ifconfig <replaceable>gif0</replaceable> inet <replaceable>192.168.2.1</replaceable> <replaceable>192.168.1.1</replaceable> netmask <replaceable>0xffffffff</replaceable></userinput>
</screen>
-
+
<para>You can then run:</para>
-
+
<programlisting>ifconfig gif0</programlisting>
-
+
<para>to see the configuration. For example, on the network #1
gateway, you would see this:</para>
-
+
<screen>&prompt.root; <userinput>ifconfig gif0</userinput>
gif0: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1280
tunnel inet A.B.C.D --&gt; W.X.Y.Z
@@ -3465,65 +3465,65 @@ gif0: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1280
through the tunnel is that between <hostid
role="ipaddr">192.168.1.1</hostid> and <hostid
role="ipaddr">192.168.2.1</hostid>.</para>
-
+
<para>This will also have added an entry to the routing table
on both machines, which you can examine with the command <command>netstat -rn</command>.
This output is from the gateway host on network #1.</para>
-
+
<screen>&prompt.root; <userinput>netstat -rn</userinput>
Routing tables
-
+
Internet:
Destination Gateway Flags Refs Use Netif Expire
...
192.168.2.1 192.168.1.1 UH 0 0 gif0
...
</screen>
-
+
<para>As the <quote>Flags</quote> value indicates, this is a
host route, which means that each gateway knows how to reach the
other gateway, but they do not know how to reach the rest of
their respective networks. That problem will be fixed
shortly.</para>
-
+
<para>It is likely that you are running a firewall on both
machines. This will need to be circumvented for your VPN
traffic. You might want to allow all traffic between both
networks, or you might want to include firewall rules that
protect both ends of the VPN from one another.</para>
-
+
<para>It greatly simplifies testing if you configure the
firewall to allow all traffic through the VPN. You can always
tighten things up later. If you are using &man.ipfw.8; on the
gateway machines then a command like</para>
<programlisting>ipfw add 1 allow ip from any to any via gif0</programlisting>
-
+
<para>will allow all traffic between the two end points of the
VPN, without affecting your other firewall rules. Obviously
you will need to run this command on both gateway hosts.</para>
-
+
<para>This is sufficient to allow each gateway machine to ping
the other. On <hostid role="ipaddr">192.168.1.1</hostid>, you
should be able to run</para>
-
+
<programlisting>ping 192.168.2.1</programlisting>
-
+
<para>and get a response, and you should be able to do the same
thing on the other gateway machine.</para>
-
+
<para>However, you will not be able to reach internal machines
on either network yet. This is because of the routing --
although the gateway machines know how to reach one another,
they do not know how to reach the network behind each one.</para>
-
+
<para>To solve this problem you must add a static route on each
gateway machine. The command to do this on the first gateway
would be:</para>
-
+
<programlisting>route add 192.168.2.0 192.168.2.1 netmask 0xffffff00
</programlisting>
-
+
<para>This says <quote>In order to reach the hosts on the
network <hostid role="ipaddr">192.168.2.0</hostid>, send the
packets to the host <hostid
@@ -3531,24 +3531,24 @@ Destination Gateway Flags Refs Use Netif Expire
run a similar command on the other gateway, but with the
<hostid role="ipaddr">192.168.1.x</hostid> addresses
instead.</para>
-
+
<para>IP traffic from hosts on one network will now be able to
reach hosts on the other network.</para>
-
+
<para>That has now created two thirds of a VPN between the two
networks, in as much as it is <quote>virtual</quote> and it is a
<quote>network</quote>. It is not private yet. You can test
this using &man.ping.8; and &man.tcpdump.1;. Log in to the
gateway host and run</para>
-
+
<programlisting>tcpdump dst host 192.168.2.1</programlisting>
<para>In another log in session on the same host run</para>
<programlisting>ping 192.168.2.1</programlisting>
-
+
<para>You will see output that looks something like this:</para>
-
+
<programlisting>
16:10:24.018080 192.168.1.1 &gt; 192.168.2.1: icmp: echo request
16:10:24.018109 192.168.1.1 &gt; 192.168.2.1: icmp: echo reply
@@ -3557,16 +3557,16 @@ Destination Gateway Flags Refs Use Netif Expire
16:10:26.028896 192.168.1.1 &gt; 192.168.2.1: icmp: echo request
16:10:26.029112 192.168.1.1 &gt; 192.168.2.1: icmp: echo reply
</programlisting>
-
+
<para>As you can see, the ICMP messages are going back and forth
unencrypted. If you had used the <option>-s</option> parameter to
&man.tcpdump.1; to grab more bytes of data from the packets you
would see more information.</para>
-
+
<para>Obviously this is unacceptable. The next section will
discuss securing the link between the two networks so that
all traffic is automatically encrypted.</para>
-
+
<itemizedlist>
<title>Summary:</title>
<listitem>
@@ -3601,14 +3601,14 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00"
<sect3>
<title>Step 2: Securing the link</title>
-
+
<para>To secure the link we will be using IPsec. IPsec provides
a mechanism for two hosts to agree on an encryption key, and to
then use this key in order to encrypt data between the two
hosts.</para>
-
+
<para>The are two areas of configuration to be considered here.</para>
-
+
<orderedlist>
<listitem>
<para>There must be a mechanism for two hosts to agree on the
@@ -3625,13 +3625,13 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00"
<quote>security policies</quote>.</para>
</listitem>
</orderedlist>
-
+
<para>Security associations and security policies are both
maintained by the kernel, and can be modified by userland
programs. However, before you can do this you must configure the
kernel to support IPsec and the Encapsulated Security Payload
(ESP) protocol. This is done by configuring a kernel with:</para>
-
+
<indexterm>
<primary>kernel options</primary>
<secondary>IPSEC</secondary>
@@ -3640,11 +3640,11 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00"
<programlisting>options IPSEC
options IPSEC_ESP
</programlisting>
-
+
<para>and recompiling, reinstalling, and rebooting. As before
you will need to do this to the kernels on both of the gateway
hosts.</para>
-
+
<indexterm>
<primary>IKE</primary>
</indexterm>
@@ -3654,10 +3654,10 @@ options IPSEC_ESP
which entails choosing the encryption algorithm, encryption keys,
and so forth, or you can use daemons that implement the Internet
Key Exchange protocol (IKE) to do this for you.</para>
-
+
<para>I recommend the latter. Apart from anything else, it is
easier to set up.</para>
-
+
<indexterm>
<primary>IPsec</primary>
<secondary>security policies</secondary>
@@ -3674,13 +3674,13 @@ options IPSEC_ESP
also display the current security associations, and to continue
the analogy further, is akin to <command>netstat -r</command>
in that respect.</para>
-
+
<para>There are a number of choices for daemons to manage
security associations with FreeBSD. This article will describe
how to use one of these, racoon&nbsp;&mdash; which is available from
<filename role="package">security/ipsec-tools</filename> in the &os; Ports
collection.</para>
-
+
<indexterm>
<primary>racoon</primary>
</indexterm>
@@ -3689,7 +3689,7 @@ options IPSEC_ESP
is configured with the IP address of the other end of the VPN,
and a secret key (which you choose, and must be the same on both
gateways).</para>
-
+
<para>The two daemons then contact one another, confirm that they
are who they say they are (by using the secret key that you
configured). The daemons then generate a new secret key, and use
@@ -3698,14 +3698,14 @@ options IPSEC_ESP
of the keys (which is as theoretically close to unfeasible as it
gets) it will not do them much good -- by the time they have cracked
the key the two daemons have chosen another one.</para>
-
+
<para>The configuration file for racoon is stored in
<filename>${PREFIX}/etc/racoon</filename>. You should find a
configuration file there, which should not need to be changed
too much. The other component of racoon's configuration,
which you will need to change, is the <quote>pre-shared
key</quote>.</para>
-
+
<para>The default racoon configuration expects to find this in
the file <filename>${PREFIX}/etc/racoon/psk.txt</filename>. It is important to note
that the pre-shared key is <emphasis>not</emphasis> the key that will be used to
@@ -3716,55 +3716,55 @@ options IPSEC_ESP
remote site you are dealing with. In this example, where there
are two sites, each <filename>psk.txt</filename> file will contain one line (because
each end of the VPN is only dealing with one other end).</para>
-
+
<para>On gateway host #1 this line should look like this:</para>
-
+
<programlisting>W.X.Y.Z secret</programlisting>
-
+
<para>That is, the <emphasis>public</emphasis> IP address of the remote end,
whitespace, and a text string that provides the secret.
Obviously, you should not use <quote>secret</quote> as your key -- the normal
rules for choosing a password apply.</para>
-
+
<para>On gateway host #2 the line would look like this</para>
-
+
<programlisting>A.B.C.D secret</programlisting>
-
+
<para>That is, the public IP address of the remote end, and the
same secret key. <filename>psk.txt</filename> must be mode
<literal>0600</literal> (i.e., only read/write to
<username>root</username>) before racoon will run.</para>
-
+
<para>You must run racoon on both gateway machines. You will
also need to add some firewall rules to allow the IKE traffic,
which is carried over UDP to the ISAKMP (Internet Security Association
Key Management Protocol) port. Again, this should be fairly early in
your firewall ruleset.</para>
-
+
<programlisting>ipfw add 1 allow udp from A.B.C.D to W.X.Y.Z isakmp
ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
</programlisting>
-
+
<para>Once racoon is running you can try pinging one gateway host
from the other. The connection is still not encrypted, but
racoon will then set up the security associations between the two
hosts -- this might take a moment, and you may see this as a
short delay before the ping commands start responding.</para>
-
+
<para>Once the security association has been set up you can
view it using &man.setkey.8;. Run</para>
-
+
<programlisting>setkey -D</programlisting>
-
+
<para>on either host to view the security association information.</para>
-
+
<para>That's one half of the problem. The other half is setting
your security policies.</para>
-
+
<para>To create a sensible security policy, let's review what's
been set up so far. This discussions hold for both ends of the
link.</para>
-
+
<para>Each IP packet that you send out has a header that contains
data about the packet. The header includes the IP addresses of
both the source and destination. As we already know, private IP
@@ -3773,9 +3773,9 @@ ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
Instead, they must first be encapsulated inside another packet.
This packet must have the public source and destination IP
addresses substituted for the private addresses.</para>
-
+
<para>So if your outgoing packet started looking like this:</para>
-
+
<mediaobject>
<imageobject>
<imagedata fileref="security/ipsec-out-pkt" align="center"/>
@@ -3792,10 +3792,10 @@ ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
`----------------------'</literallayout>
</textobject>
</mediaobject>
-
+
<para>Then it will be encapsulated inside another packet, looking
something like this:</para>
-
+
<mediaobject>
<imageobject>
<imagedata fileref="security/ipsec-encap-pkt" align="center"/>
@@ -3818,13 +3818,13 @@ ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
`--------------------------'</literallayout>
</textobject>
</mediaobject>
-
+
<para>This encapsulation is carried out by the
<devicename>gif</devicename> device. As
you can see, the packet now has real IP addresses on the outside,
and our original packet has been wrapped up as data inside the
packet that will be put out on the Internet.</para>
-
+
<para>Obviously, we want all traffic between the VPNs to be
encrypted. You might try putting this in to words, as:</para>
@@ -3832,51 +3832,51 @@ ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
role="ipaddr">A.B.C.D</hostid>, and it is destined for <hostid
role="ipaddr">W.X.Y.Z</hostid>, then encrypt it, using the
necessary security associations.</quote></para>
-
+
<para><quote>If a packet arrives from <hostid
role="ipaddr">W.X.Y.Z</hostid>, and it is destined for <hostid
role="ipaddr">A.B.C.D</hostid>, then decrypt it, using the
necessary security associations.</quote></para>
-
+
<para>That's close, but not quite right. If you did this, all
traffic to and from <hostid role="ipaddr">W.X.Y.Z</hostid>, even
traffic that was not part of the VPN, would be encrypted. That's
not quite what you want. The correct policy is as follows</para>
-
+
<para><quote>If a packet leaves from <hostid
role="ipaddr">A.B.C.D</hostid>, and that packet is encapsulating
another packet, and it is destined for <hostid
role="ipaddr">W.X.Y.Z</hostid>, then encrypt it, using the
necessary security associations.</quote></para>
-
+
<para><quote>If a packet arrives from <hostid
role="ipaddr">W.X.Y.Z</hostid>, and that packet is encapsulating
another packet, and it is destined for <hostid
role="ipaddr">A.B.C.D</hostid>, then decrypt it, using the
necessary security associations.</quote></para>
-
+
<para>A subtle change, but a necessary one.</para>
-
+
<para>Security policies are also set using &man.setkey.8;.
&man.setkey.8; features a configuration language for defining the
policy. You can either enter configuration instructions via
stdin, or you can use the <option>-f</option> option to specify a
filename that contains configuration instructions.</para>
-
+
<para>The configuration on gateway host #1 (which has the public
IP address <hostid role="ipaddr">A.B.C.D</hostid>) to force all
outbound traffic to <hostid role="ipaddr">W.X.Y.Z</hostid> to be
encrypted is:</para>
-
+
<programlisting>
spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require;
</programlisting>
-
+
<para>Put these commands in a file (e.g.
<filename>/etc/ipsec.conf</filename>) and then run</para>
<screen>&prompt.root; <userinput>setkey -f /etc/ipsec.conf</userinput></screen>
-
+
<para><option>spdadd</option> tells &man.setkey.8; that we want
to add a rule to the secure policy database. The rest of this
line specifies which packets will match this policy. <hostid
@@ -3889,7 +3889,7 @@ spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/req
packets. <option>-P out</option> says that this policy applies
to outgoing packets, and <option>ipsec</option> says that the
packet will be secured.</para>
-
+
<para>The second line specifies how this packet will be
encrypted. <option>esp</option> is the protocol that will be
used, while <option>tunnel</option> indicates that the packet
@@ -3899,37 +3899,37 @@ spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/req
association to use, and the final <option>require</option>
mandates that packets must be encrypted if they match this
rule.</para>
-
+
<para>This rule only matches outgoing packets. You will need a
similar rule to match incoming packets.</para>
-
+
<programlisting>spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P in ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require;</programlisting>
-
+
<para>Note the <option>in</option> instead of
<option>out</option> in this case, and the necessary reversal of
the IP addresses.</para>
-
+
<para>The other gateway host (which has the public IP address
<hostid role="ipaddr">W.X.Y.Z</hostid>) will need similar rules.</para>
-
+
<programlisting>spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require;
spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require;</programlisting>
-
+
<para>Finally, you need to add firewall rules to allow ESP and
IPENCAP packets back and forth. These rules will need to be
added to both hosts.</para>
-
+
<programlisting>ipfw add 1 allow esp from A.B.C.D to W.X.Y.Z
ipfw add 1 allow esp from W.X.Y.Z to A.B.C.D
ipfw add 1 allow ipencap from A.B.C.D to W.X.Y.Z
ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
</programlisting>
-
+
<para>Because the rules are symmetric you can use the same rules
on each gateway host.</para>
-
+
<para>Outgoing packets will now look something like this:</para>
-
+
<mediaobject>
<imageobject>
<imagedata fileref="security/ipsec-crypt-pkt" align="center"/>
@@ -3966,34 +3966,34 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
<devicename>gif</devicename> interface, which will unwrap
the second layer, until you are left with the innermost
packet, which can then travel in to the inner network.</para>
-
+
<para>You can check the security using the same &man.ping.8; test from
earlier. First, log in to the
<hostid role="ipaddr">A.B.C.D</hostid> gateway machine, and
run:</para>
-
+
<programlisting>tcpdump dst host 192.168.2.1</programlisting>
-
+
<para>In another log in session on the same host run</para>
-
+
<programlisting>ping 192.168.2.1</programlisting>
-
+
<para>This time you should see output like the following:</para>
-
+
<programlisting>XXX tcpdump output</programlisting>
-
+
<para>Now, as you can see, &man.tcpdump.1; shows the ESP packets. If
you try to examine them with the <option>-s</option> option you will see
(apparently) gibberish, because of the encryption.</para>
-
+
<para>Congratulations. You have just set up a VPN between two
remote sites.</para>
-
+
<itemizedlist>
<title>Summary</title>
<listitem>
<para>Configure both kernels with:</para>
-
+
<programlisting>options IPSEC
options IPSEC_ESP
</programlisting>
@@ -4009,7 +4009,7 @@ options IPSEC_ESP
<listitem>
<para>Add the following lines to
<filename>/etc/rc.conf</filename> on each host:</para>
-
+
<programlisting>ipsec_enable="YES"
ipsec_file="/etc/ipsec.conf"
</programlisting>
@@ -4018,16 +4018,16 @@ ipsec_file="/etc/ipsec.conf"
<para>Create an <filename>/etc/ipsec.conf</filename> on each
host that contains the necessary spdadd lines. On gateway
host #1 this would be:</para>
-
+
<programlisting>
spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec
esp/tunnel/A.B.C.D-W.X.Y.Z/require;
spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P in ipsec
esp/tunnel/W.X.Y.Z-A.B.C.D/require;
</programlisting>
-
+
<para>On gateway host #2 this would be:</para>
-
+
<programlisting>
spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec
esp/tunnel/W.X.Y.Z-A.B.C.D/require;
@@ -4038,7 +4038,7 @@ spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec
<listitem>
<para>Add firewall rules to allow IKE, ESP, and IPENCAP
traffic to both hosts:</para>
-
+
<programlisting>
ipfw add 1 allow udp from A.B.C.D to W.X.Y.Z isakmp
ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
@@ -4054,8 +4054,8 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
running. Machines on each network will be able to refer to one
another using IP addresses, and all traffic across the link will
be automatically and securely encrypted.</para>
- </sect3>
- </sect2>
+ </sect3>
+ </sect2>
</sect1>
<sect1 id="openssh">
@@ -4092,7 +4092,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
<sect2>
<title>Advantages of Using OpenSSH</title>
-
+
<para>Normally, when using &man.telnet.1; or &man.rlogin.1;,
data is sent over the network in an clear, un-encrypted form.
Network sniffers anywhere in between the client and server can
@@ -4108,7 +4108,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
<secondary>enabling</secondary>
</indexterm>
- <para>The
+ <para>The
<application>sshd</application> is an option presented during
a <literal>Standard</literal> install of &os;. To see if
<application>sshd</application> is enabled, check the
@@ -4129,7 +4129,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
<secondary>client</secondary>
</indexterm>
- <para>The &man.ssh.1; utility works similarly to
+ <para>The &man.ssh.1; utility works similarly to
&man.rlogin.1;.</para>
<screen>&prompt.root; <userinput>ssh <replaceable>user@example.com</replaceable></userinput>
@@ -4141,7 +4141,7 @@ user@example.com's password: <userinput>*******</userinput></screen>
<para>The login will continue just as it would have if a session was
created using <command>rlogin</command> or
<command>telnet</command>. SSH utilizes a key fingerprint
- system for verifying the authenticity of the server when the
+ system for verifying the authenticity of the server when the
client connects. The user is prompted to enter
<literal>yes</literal> only when
connecting for the first time. Future attempts to login are all
@@ -4161,7 +4161,7 @@ user@example.com's password: <userinput>*******</userinput></screen>
The version 1 compatibility is maintained in the client for
backwards compatibility with older versions.</para>
</sect2>
-
+
<sect2>
<title>Secure Copy</title>
<indexterm>
@@ -4176,8 +4176,8 @@ user@example.com's password: <userinput>*******</userinput></screen>
<screen>&prompt.root; <userinput> scp <replaceable>user@example.com:/COPYRIGHT COPYRIGHT</replaceable></userinput>
user@example.com's password: <userinput>*******</userinput>
-COPYRIGHT 100% |*****************************| 4735
-00:00
+COPYRIGHT 100% |*****************************| 4735
+00:00
&prompt.root;</screen>
<para>Since the fingerprint was already saved for this host in the
previous example, it is verified when using &man.scp.1;
@@ -4203,8 +4203,8 @@ COPYRIGHT 100% |*****************************| 4735
<application>OpenSSH</application> daemon and client reside
within the <filename>/etc/ssh</filename> directory.</para>
- <para><filename>ssh_config</filename> configures the client
- settings, while <filename>sshd_config</filename> configures the
+ <para><filename>ssh_config</filename> configures the client
+ settings, while <filename>sshd_config</filename> configures the
daemon.</para>
<para>Additionally, the <option>sshd_program</option>
@@ -4312,7 +4312,7 @@ Identity added: /home/user/.ssh/id_dsa (/home/user/.ssh/id_dsa)
<para><application>OpenSSH</application> has the ability to create a tunnel to encapsulate
another protocol in an encrypted session.</para>
- <para>The following command tells &man.ssh.1; to create a tunnel
+ <para>The following command tells &man.ssh.1; to create a tunnel
for <application>telnet</application>:</para>
<screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5023:localhost:23 user@foo.example.com</replaceable></userinput>
@@ -4324,7 +4324,7 @@ Identity added: /home/user/.ssh/id_dsa (/home/user/.ssh/id_dsa)
<variablelist>
<varlistentry>
<term><option>-2</option></term>
-
+
<listitem>
<para>Forces <command>ssh</command> to use version 2 of
the protocol. (Do not use if you are working with older
@@ -4395,7 +4395,7 @@ user@mailserver.example.com's password: <userinput>*****</userinput>
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
-220 mailserver.example.com ESMTP</screen>
+220 mailserver.example.com ESMTP</screen>
<para>This can be used in conjunction with an
&man.ssh-keygen.1; and additional user accounts to create a
@@ -4494,7 +4494,7 @@ user@unfirewalled-system.example.org's password: <userinput>*******</userinput><
<sect2>
<title>Further Reading</title>
<para><ulink url="http://www.openssh.com/">OpenSSH</ulink></para>
- <para>&man.ssh.1; &man.scp.1; &man.ssh-keygen.1;
+ <para>&man.ssh.1; &man.scp.1; &man.ssh-keygen.1;
&man.ssh-agent.1; &man.ssh-add.1; &man.ssh.config.5;</para>
<para>&man.sshd.8; &man.sftp-server.8; &man.sshd.config.5;</para>
</sect2>
@@ -4583,7 +4583,7 @@ user@unfirewalled-system.example.org's password: <userinput>*******</userinput><
users of the system, and re-enabling <acronym>ACL</acronym>s may re-attach the previous
<acronym>ACL</acronym>s to files that have since had their permissions changed,
resulting in other unpredictable behavior.</para></note>
-
+
<para>File systems with <acronym>ACL</acronym>s enabled will show a <literal>+</literal>
(plus) sign in their permission settings when viewed. For example:</para>
@@ -4989,5 +4989,5 @@ VII. References<co id="co-ref"/></programlisting>
&man.lastcomm.1;, &man.acct.5; and &man.sa.8; manual
pages.</para>
</sect2>
- </sect1>
+ </sect1>
</chapter>
diff --git a/el_GR.ISO8859-7/htdocs/doc/Makefile b/el_GR.ISO8859-7/htdocs/doc/Makefile
index f2ffd22813..010cd81d7c 100644
--- a/el_GR.ISO8859-7/htdocs/doc/Makefile
+++ b/el_GR.ISO8859-7/htdocs/doc/Makefile
@@ -1,7 +1,7 @@
#
# $FreeBSD$
#
-#
+#
# The FreeBSD Greek Documentation Project
#
# Build the FreeBSD documentation *outside* of the www tree, and install it
diff --git a/el_GR.ISO8859-7/share/sgml/freebsd.dsl b/el_GR.ISO8859-7/share/sgml/freebsd.dsl
index 5d7a08ee86..1d29906e31 100644
--- a/el_GR.ISO8859-7/share/sgml/freebsd.dsl
+++ b/el_GR.ISO8859-7/share/sgml/freebsd.dsl
@@ -15,7 +15,7 @@
<!ENTITY % freebsd.l10n PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN">
%freebsd.l10n;
-<!ENTITY % output.html "IGNORE">
+<!ENTITY % output.html "IGNORE">
<!ENTITY % output.print "IGNORE">
<!ENTITY % lang.el.dsssl "IGNORE">
]>
@@ -39,7 +39,7 @@
(literal ".")))
(make element gi: "p"
attributes: (list (list "align" "center"))
- (make element gi: "small"
+ (make element gi: "small"
(literal " FreeBSD, ")
(create-link
(list (list "HREF" "http://www.FreeBSD.org/docs.html"))
diff --git a/el_GR.ISO8859-7/share/sgml/navibar.l10n.ent b/el_GR.ISO8859-7/share/sgml/navibar.l10n.ent
index b243f9c750..06b24d59e3 100644
--- a/el_GR.ISO8859-7/share/sgml/navibar.l10n.ent
+++ b/el_GR.ISO8859-7/share/sgml/navibar.l10n.ent
@@ -104,10 +104,10 @@
<li><a href="&u.rel.announce;"> : &rel.current;</a></li>
<li><a href="&u.rel2.announce;"> (Legacy): &rel2.current;</a></li>
<li><a href="&base;/snapshots/"> Snapshot</a></li>
-<![ %beta.testing; [
+<![ %beta.testing; [
<li><a href="&u.betarel.schedule;"> : &betarel.current;</a></li>
]]>
-<![ %beta2.testing; [
+<![ %beta2.testing; [
<li><a href="&u.betarel2.schedule;"> : &betarel2.current;</a></li>
]]>
</ul></li>
diff --git a/en_US.ISO8859-1/articles/5-roadmap/Makefile b/en_US.ISO8859-1/articles/5-roadmap/Makefile
index b3b8bbb0e0..a2a3804255 100644
--- a/en_US.ISO8859-1/articles/5-roadmap/Makefile
+++ b/en_US.ISO8859-1/articles/5-roadmap/Makefile
@@ -1,4 +1,4 @@
-#
+#
# $FreeBSD$
#
# Article: FreeBSD 5-STABLE roadmap
diff --git a/en_US.ISO8859-1/articles/Makefile.inc b/en_US.ISO8859-1/articles/Makefile.inc
index de45c09960..5aae9fcfbf 100644
--- a/en_US.ISO8859-1/articles/Makefile.inc
+++ b/en_US.ISO8859-1/articles/Makefile.inc
@@ -1,4 +1,4 @@
-#
+#
# $FreeBSD$
#
diff --git a/en_US.ISO8859-1/articles/bsdl-gpl/Makefile b/en_US.ISO8859-1/articles/bsdl-gpl/Makefile
index 4bfc9c797f..a221a6dfe5 100644
--- a/en_US.ISO8859-1/articles/bsdl-gpl/Makefile
+++ b/en_US.ISO8859-1/articles/bsdl-gpl/Makefile
@@ -1,4 +1,4 @@
-#
+#
# $FreeBSD$
#
# BSDL vs GPL article.
diff --git a/en_US.ISO8859-1/articles/casestudy-argentina.com/Makefile b/en_US.ISO8859-1/articles/casestudy-argentina.com/Makefile
index 6f9f128635..d07a81bc94 100644
--- a/en_US.ISO8859-1/articles/casestudy-argentina.com/Makefile
+++ b/en_US.ISO8859-1/articles/casestudy-argentina.com/Makefile
@@ -1,4 +1,4 @@
-#
+#
# $FreeBSD$
#
# Article: Casestudy from Argentina.com
diff --git a/en_US.ISO8859-1/articles/committers-guide/Makefile b/en_US.ISO8859-1/articles/committers-guide/Makefile
index 890bd6e2b2..420756adac 100644
--- a/en_US.ISO8859-1/articles/committers-guide/Makefile
+++ b/en_US.ISO8859-1/articles/committers-guide/Makefile
@@ -1,4 +1,4 @@
-#
+#
# $FreeBSD$
#
# Article: The FreeBSD Committers Guide
diff --git a/en_US.ISO8859-1/articles/compiz-fusion/article.sgml b/en_US.ISO8859-1/articles/compiz-fusion/article.sgml
index 9559d457b8..56c0344f5c 100644
--- a/en_US.ISO8859-1/articles/compiz-fusion/article.sgml
+++ b/en_US.ISO8859-1/articles/compiz-fusion/article.sgml
@@ -236,7 +236,7 @@ Option "AddARGBGLXVisuals" "True"</programlisting>
<programlisting>SubSection "Display"
Viewport 0 0
Modes "1280x1024"
-EndSubSection</programlisting>
+EndSubSection</programlisting>
<para>A color depth of 24&nbsp;bits is needed for desktop composition,
change the above subsection to:</para>
@@ -371,7 +371,7 @@ emerald --replace &amp;</programlisting>
<qandaentry>
<question id="xorg-crash">
- <para>When I run the command to start
+ <para>When I run the command to start
<application>Compiz&nbsp;Fusion</application>, the X server
crashes and I am back at the console. What is wrong?</para>
</question>
diff --git a/en_US.ISO8859-1/articles/console-server/article.sgml b/en_US.ISO8859-1/articles/console-server/article.sgml
index 9d565922a7..7833ab5e09 100644
--- a/en_US.ISO8859-1/articles/console-server/article.sgml
+++ b/en_US.ISO8859-1/articles/console-server/article.sgml
@@ -371,13 +371,13 @@
<title>Compiling conserver</title>
<note>
- <para>See the section on <application>conserver</application> versions
+ <para>See the section on <application>conserver</application> versions
<xref linkend="conserver-versions"/>; the version I use is
available in the &os; ports collection; however, it is not the only
one.)</para>
</note>
- <para>There are two ways to install <application>conserver</application>.
+ <para>There are two ways to install <application>conserver</application>.
You can either compile
from the source or use the &os; ports framework.</para>
@@ -398,7 +398,7 @@
is compiled will avoid having to either specify it each time the
program is run on remote hosts or having to maintain a
<filename>conserver.cf</filename> file on every host. This command
- will fetch, patch, configure, compile and install the
+ will fetch, patch, configure, compile and install the
<application>conserver</application> application.</para>
<para>You can then run <command>make package</command> to create a
@@ -424,7 +424,7 @@
<title>From the source tarball</title>
<para>If you prefer, you can download <application>conserver</application>
- and compile it yourself.
+ and compile it yourself.
You might need to do this if you want to install the
console client on non-&os; systems. We run the client on our
&solaris; hosts and it inter-operates with the &os;-hosted server
@@ -560,10 +560,10 @@ $1$VTd27V2G$eFu23iHpLvCBM5nQtNlKj/</screen>
<programlisting>cuaE0 "/usr/local/sbin/conserver" unknown on insecure</programlisting>
- <para>This has two advantages: <application>init</application> will restart
+ <para>This has two advantages: <application>init</application> will restart
the master console
server if it ever crashes for any reason (but we have not noticed any
- crashes so far), and it arranges for standard output of the
+ crashes so far), and it arranges for standard output of the
<application>conserver</application>
process to be directed to the named tty (in this case
<devicename>cuaE0</devicename>). This is useful because you
@@ -574,14 +574,14 @@ $1$VTd27V2G$eFu23iHpLvCBM5nQtNlKj/</screen>
monitoring tool to see if anything is going on. We set this
terminal up in the computer room but visible from the main
office. It is a very handy feature. The downside of running
- <application>conserver</application>
+ <application>conserver</application>
from the ttys file is that it cannot run in daemon
mode (else &man.init.8; would continually restart it). This means
- <application>conserver</application> will not write a PID file,
+ <application>conserver</application> will not write a PID file,
which makes it hard to rotate the log files.</para>
<para>So we start <application>conserver</application> from an rc.d script.
- If you installed <application>conserver</application> via the port,
+ If you installed <application>conserver</application> via the port,
there will be a
<filename>conserver.sh.sample</filename> file installed in
<filename>/usr/local/etc/rc.d</filename>. Copy and/or rename this to
@@ -1217,11 +1217,11 @@ exit 0</programlisting>
<para>Anyone who has turned off a terminal used as a console for a Sun
system will know what happens and why this is a problem. Sun hardware
- recognises a serial <literal>BREAK</literal> as a command to halt the
+ recognises a serial <literal>BREAK</literal> as a command to halt the
OS and return to the ROM monitor prompt. A serial <literal>BREAK</literal>
- is an out-of-band signal on an RS-232 serial port that involves making
- the TX DATA line active (i.e. pulled down to less than -5V) for more than
- two whole character times (or about 2ms on a 9600bps line).
+ is an out-of-band signal on an RS-232 serial port that involves making
+ the TX DATA line active (i.e. pulled down to less than -5V) for more than
+ two whole character times (or about 2ms on a 9600bps line).
Alas, this <literal>BREAK</literal> signal is all to
easily generated by serial hardware during power-on or power-off. And
the Stallion card does, in fact, generate breaks when the power to the
@@ -1232,7 +1232,7 @@ exit 0</programlisting>
<para>Fortunately, Sun have come up with a set of fixes for this. For
&solaris; 2.6 and later, the <command>kbd(1)</command> command can be used
- to disable the <literal>ROM-on-BREAK</literal> behaviour. This is a good start,
+ to disable the <literal>ROM-on-BREAK</literal> behaviour. This is a good start,
but leaves you out of luck in the situation where a break is needed to get into a
broken machine.</para>
@@ -1342,7 +1342,7 @@ exit 0</programlisting>
<application>conserver</application> is not really suitable for use
across untrusted networks (such as the Internet). Use of conserver-only
passwords (in the <filename>conserver.passwd</filename> file) slightly
- mitigate this problem, but anyone sniffing a
+ mitigate this problem, but anyone sniffing a
<application>conserver</application> connection can
easily get console access, and from there prang your machine using the
console break sequence. For operating across the Internet, use
@@ -1370,12 +1370,12 @@ exit 0</programlisting>
idiosyncratic manner (using a preprocessor to generate C code). Version
8.5 is maintained by Kevin S.&nbsp;Braunsdorf
<email>ksb+conserver@sa.fedex.com</email> who did most of the original
- work on <application>conserver</application>,
+ work on <application>conserver</application>,
and whose work Bryan Stansell is building on. The
8.5 version does support one feature not in the 8.1.9 version
(controlling power to remote machines via a specific serial-interfaced
power controller hardware).</para>
-
+
<para>Beginning with December 2001, Brian's version (currently 8.1.9) is
also presented in ports collection at
<filename role="package">comms/conserver-com</filename>. We therefore
diff --git a/en_US.ISO8859-1/articles/contributing/article.sgml b/en_US.ISO8859-1/articles/contributing/article.sgml
index b42ff4fe72..caa4d284ea 100644
--- a/en_US.ISO8859-1/articles/contributing/article.sgml
+++ b/en_US.ISO8859-1/articles/contributing/article.sgml
@@ -482,7 +482,7 @@
information:</para>
<programlisting>Copyright (c) %%proper_years_here%%
- %%your_name_here%%, %%your_state%% %%your_zip%%.
+ %%your_name_here%%, %%your_state%% %%your_zip%%.
All rights reserved.
Redistribution and use in source and binary forms, with or without
diff --git a/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml b/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml
index 90af09b5b2..21245f882d 100644
--- a/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml
+++ b/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml
@@ -330,7 +330,7 @@
</listitem>
<listitem>
- <para>Alex Steiner
+ <para>Alex Steiner
<email>ast@treibsand.com</email></para>
</listitem>
@@ -4558,7 +4558,7 @@
<listitem>
<para>Jesse Kempf
- <email>jessekempf@gmail.com</email></para>
+ <email>jessekempf@gmail.com</email></para>
</listitem>
<listitem>
@@ -8295,7 +8295,7 @@
</listitem>
<listitem>
- <para>Philippe Pepiot
+ <para>Philippe Pepiot
<email>phil@philpep.org</email></para>
</listitem>
diff --git a/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml b/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml
index 2f633051b4..592bf0631f 100644
--- a/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml
+++ b/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml
@@ -567,7 +567,7 @@
<para>&a.chinsan;</para>
</listitem>
- <listitem>
+ <listitem>
<para>&a.davide;</para>
</listitem>
diff --git a/en_US.ISO8859-1/articles/custom-gcc/Makefile b/en_US.ISO8859-1/articles/custom-gcc/Makefile
index b7bd286403..77336c615e 100644
--- a/en_US.ISO8859-1/articles/custom-gcc/Makefile
+++ b/en_US.ISO8859-1/articles/custom-gcc/Makefile
@@ -1,4 +1,4 @@
-#
+#
# $FreeBSD$
#
diff --git a/en_US.ISO8859-1/articles/cvsup-advanced/article.sgml b/en_US.ISO8859-1/articles/cvsup-advanced/article.sgml
index 942328652f..4b7a