From 2e51ec7022b39b6fb3524de08669b20d0d436285 Mon Sep 17 00:00:00 2001 From: Gabor Kovesdan Date: Tue, 21 Aug 2012 19:16:02 +0000 Subject: - Strip unnecessary trailing spaces Approved by: doceng (implicit) --- en_US.ISO8859-1/articles/5-roadmap/Makefile | 2 +- en_US.ISO8859-1/articles/Makefile.inc | 2 +- en_US.ISO8859-1/articles/bsdl-gpl/Makefile | 2 +- .../articles/casestudy-argentina.com/Makefile | 2 +- en_US.ISO8859-1/articles/committers-guide/Makefile | 2 +- .../articles/compiz-fusion/article.sgml | 4 +- .../articles/console-server/article.sgml | 34 +- en_US.ISO8859-1/articles/contributing/article.sgml | 2 +- .../articles/contributors/contrib.additional.sgml | 6 +- .../articles/contributors/contrib.committers.sgml | 2 +- en_US.ISO8859-1/articles/custom-gcc/Makefile | 2 +- .../articles/cvsup-advanced/article.sgml | 84 +- .../articles/dialup-firewall/article.sgml | 4 +- en_US.ISO8859-1/articles/diskless-x/article.sgml | 44 +- en_US.ISO8859-1/articles/euro/article.sgml | 66 +- .../articles/explaining-bsd/article.sgml | 6 +- en_US.ISO8859-1/articles/fonts/article.sgml | 8 +- .../articles/formatting-media/article.sgml | 46 +- .../articles/freebsd-questions/article.sgml | 50 +- en_US.ISO8859-1/articles/geom-class/Makefile | 2 +- .../articles/gjournal-desktop/article.sgml | 22 +- en_US.ISO8859-1/articles/hubs/article.sgml | 2 +- en_US.ISO8859-1/articles/laptop/article.sgml | 52 +- en_US.ISO8859-1/articles/ldap-auth/Makefile | 2 +- en_US.ISO8859-1/articles/ldap-auth/article.sgml | 8 +- .../articles/linux-comparison/article.sgml | 2 +- .../articles/linux-emulation/article.sgml | 82 +- en_US.ISO8859-1/articles/linux-users/Makefile | 2 +- en_US.ISO8859-1/articles/mailing-list-faq/Makefile | 2 +- en_US.ISO8859-1/articles/mh/article.sgml | 24 +- en_US.ISO8859-1/articles/nanobsd/Makefile | 2 +- en_US.ISO8859-1/articles/new-users/article.sgml | 2 +- en_US.ISO8859-1/articles/p4-primer/Makefile | 2 +- en_US.ISO8859-1/articles/portbuild/article.sgml | 4 +- .../articles/problem-reports/article.sgml | 4 +- en_US.ISO8859-1/articles/rc-scripting/Makefile | 2 +- en_US.ISO8859-1/articles/rc-scripting/article.sgml | 2 +- en_US.ISO8859-1/articles/relaydelay/article.sgml | 2 +- en_US.ISO8859-1/articles/releng-packages/Makefile | 2 +- en_US.ISO8859-1/articles/releng/Makefile | 2 +- en_US.ISO8859-1/articles/releng/article.sgml | 6 +- en_US.ISO8859-1/articles/remote-install/Makefile | 2 +- en_US.ISO8859-1/articles/serial-uart/article.sgml | 556 +++---- en_US.ISO8859-1/articles/solid-state/Makefile | 2 +- en_US.ISO8859-1/articles/solid-state/article.sgml | 14 +- .../articles/storage-devices/article.sgml | 884 +++++------ en_US.ISO8859-1/articles/version-guide/Makefile | 2 +- .../articles/version-guide/article.sgml | 8 +- en_US.ISO8859-1/articles/vinum/article.sgml | 20 +- en_US.ISO8859-1/articles/vm-design/article.sgml | 12 +- en_US.ISO8859-1/articles/wp-toolbox/Makefile | 2 +- en_US.ISO8859-1/books/Makefile.inc | 2 +- en_US.ISO8859-1/books/arch-handbook/Makefile | 4 +- en_US.ISO8859-1/books/arch-handbook/book.sgml | 12 +- en_US.ISO8859-1/books/arch-handbook/chapters.ent | 6 +- .../books/arch-handbook/driverbasics/chapter.sgml | 14 +- .../books/arch-handbook/isa/chapter.sgml | 14 +- .../books/arch-handbook/jail/chapter.sgml | 22 +- .../books/arch-handbook/locking/chapter.sgml | 18 +- .../books/arch-handbook/mac/chapter.sgml | 1672 ++++++++++---------- .../books/arch-handbook/scsi/chapter.sgml | 96 +- .../books/arch-handbook/sound/chapter.sgml | 44 +- .../books/arch-handbook/sysinit/chapter.sgml | 2 +- .../books/arch-handbook/usb/chapter.sgml | 10 +- .../books/arch-handbook/vm/chapter.sgml | 18 +- en_US.ISO8859-1/books/bibliography/Makefile | 4 +- en_US.ISO8859-1/books/bibliography/book.sgml | 8 +- en_US.ISO8859-1/books/corp-net-guide/book.sgml | 76 +- en_US.ISO8859-1/books/design-44bsd/book.sgml | 314 ++-- en_US.ISO8859-1/books/dev-model/book.sgml | 14 +- en_US.ISO8859-1/books/developers-handbook/Makefile | 4 +- .../books/developers-handbook/book.sgml | 16 +- .../books/developers-handbook/chapters.ent | 6 +- .../books/developers-handbook/ipv6/chapter.sgml | 12 +- .../developers-handbook/kerneldebug/chapter.sgml | 8 +- .../developers-handbook/policies/chapter.sgml | 58 +- .../books/developers-handbook/secure/chapter.sgml | 38 +- .../books/developers-handbook/sockets/chapter.sgml | 66 +- .../books/developers-handbook/tools/chapter.sgml | 8 +- en_US.ISO8859-1/books/faq/Makefile | 6 +- en_US.ISO8859-1/books/fdp-primer/Makefile | 26 +- en_US.ISO8859-1/books/fdp-primer/chapters.ent | 12 +- .../books/fdp-primer/examples/appendix.sgml | 6 +- .../books/fdp-primer/sgml-markup/chapter.sgml | 14 +- .../books/fdp-primer/writing-style/chapter.sgml | 2 +- en_US.ISO8859-1/books/handbook/Makefile | 8 +- .../handbook/advanced-networking/chapter.sgml | 10 +- en_US.ISO8859-1/books/handbook/basics/chapter.sgml | 212 +-- en_US.ISO8859-1/books/handbook/book.sgml | 2 +- en_US.ISO8859-1/books/handbook/chapters.ent | 6 +- .../books/handbook/filesystems/chapter.sgml | 14 +- en_US.ISO8859-1/books/handbook/jails/chapter.sgml | 4 +- .../books/handbook/kernelconfig/chapter.sgml | 12 +- en_US.ISO8859-1/books/handbook/l10n/chapter.sgml | 18 +- .../books/handbook/linuxemu/chapter.sgml | 4 +- en_US.ISO8859-1/books/handbook/mac/chapter.sgml | 6 +- en_US.ISO8859-1/books/handbook/mail/chapter.sgml | 4 +- .../books/handbook/mirrors/chapter.sgml | 256 +-- .../books/handbook/multimedia/chapter.sgml | 24 +- en_US.ISO8859-1/books/handbook/ports/chapter.sgml | 2 +- .../books/handbook/ppp-and-slip/chapter.sgml | 78 +- .../books/handbook/preface/preface.sgml | 6 +- en_US.ISO8859-1/books/handbook/txtfiles.ent | 8 +- en_US.ISO8859-1/books/handbook/users/chapter.sgml | 26 +- en_US.ISO8859-1/books/handbook/vinum/chapter.sgml | 58 +- .../books/handbook/virtualization/chapter.sgml | 6 +- en_US.ISO8859-1/books/handbook/x11/chapter.sgml | 8 +- en_US.ISO8859-1/books/porters-handbook/Makefile | 4 +- en_US.ISO8859-1/htdocs/FAQ/Makefile | 2 +- en_US.ISO8859-1/htdocs/applications.sgml | 16 +- en_US.ISO8859-1/htdocs/art.sgml | 2 +- en_US.ISO8859-1/htdocs/availability.sgml | 2 +- en_US.ISO8859-1/htdocs/copyright/daemon.sgml | 4 +- .../htdocs/copyright/freebsd-doc-license.sgml | 20 +- en_US.ISO8859-1/htdocs/developers/Makefile | 2 +- en_US.ISO8859-1/htdocs/docproj/Makefile | 4 +- en_US.ISO8859-1/htdocs/docproj/current.sgml | 32 +- en_US.ISO8859-1/htdocs/docproj/doc-set.sgml | 2 +- en_US.ISO8859-1/htdocs/docproj/docproj.sgml | 12 +- en_US.ISO8859-1/htdocs/docproj/sgml.sgml | 26 +- en_US.ISO8859-1/htdocs/docproj/submitting.sgml | 18 +- en_US.ISO8859-1/htdocs/docproj/translations.sgml | 4 +- en_US.ISO8859-1/htdocs/docproj/who.sgml | 4 +- en_US.ISO8859-1/htdocs/donations/donors.sgml | 2 +- .../htdocs/events/2002/bsdcon-devsummit.sgml | 114 +- .../htdocs/events/2002/usenix-devsummit.sgml | 2 +- en_US.ISO8859-1/htdocs/features.sgml | 8 +- en_US.ISO8859-1/htdocs/gifs/Makefile | 12 +- en_US.ISO8859-1/htdocs/gnome/docs/faq210.sgml | 2 +- en_US.ISO8859-1/htdocs/gnome/docs/faq224.sgml | 2 +- en_US.ISO8859-1/htdocs/gnome/docs/faq230.sgml | 6 +- en_US.ISO8859-1/htdocs/gnome/docs/faq232.sgml | 8 +- en_US.ISO8859-1/htdocs/gnome/news.xml | 22 +- en_US.ISO8859-1/htdocs/handbook/Makefile | 2 +- en_US.ISO8859-1/htdocs/internal/Makefile | 4 +- en_US.ISO8859-1/htdocs/internal/machines.sgml | 8 +- en_US.ISO8859-1/htdocs/internal/mirror.sgml | 6 +- en_US.ISO8859-1/htdocs/internal/new-account.sgml | 16 +- en_US.ISO8859-1/htdocs/internal/statistic.sgml | 2 +- en_US.ISO8859-1/htdocs/internet.sgml | 6 +- en_US.ISO8859-1/htdocs/ipv6/index.sgml | 6 +- en_US.ISO8859-1/htdocs/ipv6/ipv6.ent | 6 +- en_US.ISO8859-1/htdocs/ipv6/ipv6only.sgml | 6 +- en_US.ISO8859-1/htdocs/ipv6/w6d-www-stats.sgml | 6 +- en_US.ISO8859-1/htdocs/ipv6/w6d.sgml | 10 +- en_US.ISO8859-1/htdocs/ipv6/w6l.sgml | 4 +- en_US.ISO8859-1/htdocs/java/advocacy.sgml | 2 +- en_US.ISO8859-1/htdocs/java/dists/12.sgml | 18 +- en_US.ISO8859-1/htdocs/java/dists/13.sgml | 30 +- en_US.ISO8859-1/htdocs/java/dists/14.sgml | 14 +- en_US.ISO8859-1/htdocs/java/docs/faq.sgml | 8 +- en_US.ISO8859-1/htdocs/java/docs/performance.sgml | 18 +- en_US.ISO8859-1/htdocs/java/java-rss.xsl | 2 +- en_US.ISO8859-1/htdocs/java/links/Makefile | 4 +- en_US.ISO8859-1/htdocs/java/links/api.sgml | 20 +- en_US.ISO8859-1/htdocs/java/links/development.sgml | 2 +- en_US.ISO8859-1/htdocs/java/links/freebsd.sgml | 4 +- en_US.ISO8859-1/htdocs/java/links/vendor.sgml | 2 +- en_US.ISO8859-1/htdocs/kse/index.sgml | 6 +- en_US.ISO8859-1/htdocs/layout/images/Makefile | 2 +- en_US.ISO8859-1/htdocs/mailto.sgml | 8 +- en_US.ISO8859-1/htdocs/marketing/index.sgml | 2 +- .../htdocs/multimedia/multimedia-input.xml | 66 +- en_US.ISO8859-1/htdocs/news/1996/index.sgml | 6 +- en_US.ISO8859-1/htdocs/news/1997/index.sgml | 22 +- en_US.ISO8859-1/htdocs/news/1998/index.sgml | 4 +- en_US.ISO8859-1/htdocs/news/1999/index.sgml | 4 +- en_US.ISO8859-1/htdocs/news/2000/index.sgml | 24 +- en_US.ISO8859-1/htdocs/news/2001/news.xml | 164 +- en_US.ISO8859-1/htdocs/news/2002/news.xml | 24 +- en_US.ISO8859-1/htdocs/news/2003/news.xml | 10 +- en_US.ISO8859-1/htdocs/news/2004/news.xml | 26 +- en_US.ISO8859-1/htdocs/news/2005/news.xml | 14 +- en_US.ISO8859-1/htdocs/news/2006/news.xml | 18 +- en_US.ISO8859-1/htdocs/news/2007/news.xml | 10 +- en_US.ISO8859-1/htdocs/news/2007/press.xml | 4 +- en_US.ISO8859-1/htdocs/news/2009/news.xml | 2 +- en_US.ISO8859-1/htdocs/news/2009/press.xml | 4 +- en_US.ISO8859-1/htdocs/news/press-rel-2.sgml | 6 +- en_US.ISO8859-1/htdocs/news/press-rel-3.sgml | 6 +- en_US.ISO8859-1/htdocs/news/press-rel-5.sgml | 2 +- en_US.ISO8859-1/htdocs/news/press-rel-6.sgml | 98 +- en_US.ISO8859-1/htdocs/news/pressreleases.sgml | 4 +- en_US.ISO8859-1/htdocs/news/sou1999.sgml | 18 +- .../htdocs/news/status/report-2001-06.xml | 2 +- .../htdocs/news/status/report-2001-07.xml | 2 +- .../htdocs/news/status/report-2001-08.xml | 4 +- .../htdocs/news/status/report-2001-09.xml | 22 +- .../htdocs/news/status/report-2001-11.xml | 20 +- .../htdocs/news/status/report-2001-12-2002-01.xml | 10 +- .../htdocs/news/status/report-2002-02-2002-04.xml | 24 +- .../htdocs/news/status/report-2002-05-2002-06.xml | 78 +- .../htdocs/news/status/report-2002-07-2002-08.xml | 12 +- .../htdocs/news/status/report-2002-09-2002-10.xml | 8 +- .../htdocs/news/status/report-2002-11-2002-12.xml | 4 +- .../htdocs/news/status/report-2003-01-2003-02.xml | 22 +- .../htdocs/news/status/report-2003-03-2003-09.xml | 26 +- .../htdocs/news/status/report-2003-10-2003-12.xml | 492 +++--- .../htdocs/news/status/report-2004-01-2004-02.xml | 118 +- .../htdocs/news/status/report-2004-03-2004-04.xml | 284 ++-- .../htdocs/news/status/report-2004-05-2004-06.xml | 232 +-- .../htdocs/news/status/report-2004-07-2004-12.xml | 102 +- .../htdocs/news/status/report-2005-01-2005-03.xml | 56 +- .../htdocs/news/status/report-2005-03-2005-06.xml | 32 +- .../htdocs/news/status/report-2005-07-2005-10.xml | 52 +- .../htdocs/news/status/report-2005-10-2005-12.xml | 20 +- .../htdocs/news/status/report-2006-01-2006-03.xml | 24 +- .../htdocs/news/status/report-2006-04-2006-06.xml | 50 +- .../htdocs/news/status/report-2006-06-2006-10.xml | 30 +- .../htdocs/news/status/report-2006-10-2006-12.xml | 90 +- .../htdocs/news/status/report-2007-01-2007-03.xml | 28 +- .../htdocs/news/status/report-2007-04-2007-06.xml | 18 +- .../htdocs/news/status/report-2007-07-2007-10.xml | 12 +- .../htdocs/news/status/report-2007-10-2007-12.xml | 10 +- .../htdocs/news/status/report-2008-01-2008-03.xml | 12 +- .../htdocs/news/status/report-2008-04-2008-06.xml | 24 +- .../htdocs/news/status/report-2008-07-2008-09.xml | 24 +- .../htdocs/news/status/report-2008-10-2008-12.xml | 24 +- .../htdocs/news/status/report-2009-01-2009-03.xml | 32 +- .../htdocs/news/status/report-2009-04-2009-09.xml | 4 +- .../htdocs/news/status/report-2009-10-2009-12.xml | 24 +- .../htdocs/news/status/report-2010-01-2010-03.xml | 24 +- .../htdocs/news/status/report-2010-04-2010-06.xml | 12 +- .../htdocs/news/status/report-2011-01-2011-03.xml | 2 +- en_US.ISO8859-1/htdocs/news/status/report.xsl | 6 +- en_US.ISO8859-1/htdocs/news/status/status.sgml | 6 +- en_US.ISO8859-1/htdocs/platforms/alpha.sgml | 2 +- en_US.ISO8859-1/htdocs/platforms/arm.sgml | 8 +- en_US.ISO8859-1/htdocs/platforms/mips.sgml | 2 +- en_US.ISO8859-1/htdocs/platforms/pc98.sgml | 2 +- en_US.ISO8859-1/htdocs/platforms/ppc.sgml | 4 +- en_US.ISO8859-1/htdocs/platforms/x86-64.sgml | 2 +- en_US.ISO8859-1/htdocs/portmgr/charter.sgml | 2 +- en_US.ISO8859-1/htdocs/portmgr/index.sgml | 2 +- en_US.ISO8859-1/htdocs/portmgr/policies.sgml | 2 +- .../htdocs/portmgr/policies_contributors.sgml | 2 +- en_US.ISO8859-1/htdocs/portmgr/qa.sgml | 6 +- en_US.ISO8859-1/htdocs/ports/Makefile.inc | 2 +- en_US.ISO8859-1/htdocs/projects/acpi/index.sgml | 6 +- en_US.ISO8859-1/htdocs/projects/busdma/index.sgml | 10 +- en_US.ISO8859-1/htdocs/projects/c99/index.sgml | 2 +- en_US.ISO8859-1/htdocs/projects/cvsweb.sgml | 2 +- en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml | 14 +- en_US.ISO8859-1/htdocs/projects/newbies.sgml | 32 +- .../htdocs/projects/summerofcode-2007.sgml | 6 +- .../htdocs/projects/summerofcode-2008.sgml | 2 +- en_US.ISO8859-1/htdocs/projects/summerofcode.sgml | 6 +- en_US.ISO8859-1/htdocs/publish.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/2.0.5R/notes.sgml | 14 +- en_US.ISO8859-1/htdocs/releases/2.0/install.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/2.0/notes.sgml | 12 +- en_US.ISO8859-1/htdocs/releases/2.1.5R/notes.sgml | 6 +- .../htdocs/releases/2.1.6R/announce.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/2.1.6R/notes.sgml | 8 +- .../htdocs/releases/2.1.6R/security.sgml | 4 +- en_US.ISO8859-1/htdocs/releases/2.1.7R/notes.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/2.1R/notes.sgml | 4 +- en_US.ISO8859-1/htdocs/releases/2.2.1R/notes.sgml | 14 +- en_US.ISO8859-1/htdocs/releases/2.2.2R/notes.sgml | 14 +- en_US.ISO8859-1/htdocs/releases/2.2.5R/errata.sgml | 10 +- en_US.ISO8859-1/htdocs/releases/2.2.5R/notes.sgml | 10 +- en_US.ISO8859-1/htdocs/releases/2.2.6R/errata.sgml | 24 +- en_US.ISO8859-1/htdocs/releases/2.2.6R/notes.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/2.2.7R/errata.sgml | 4 +- en_US.ISO8859-1/htdocs/releases/2.2.7R/notes.sgml | 44 +- en_US.ISO8859-1/htdocs/releases/2.2.8R/errata.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/2.2.8R/notes.sgml | 44 +- en_US.ISO8859-1/htdocs/releases/2.2R/announce.sgml | 10 +- en_US.ISO8859-1/htdocs/releases/2.2R/notes.sgml | 16 +- en_US.ISO8859-1/htdocs/releases/3.0R/errata.sgml | 12 +- en_US.ISO8859-1/htdocs/releases/3.0R/notes.sgml | 16 +- en_US.ISO8859-1/htdocs/releases/3.1R/errata.sgml | 12 +- en_US.ISO8859-1/htdocs/releases/3.1R/notes.sgml | 8 +- en_US.ISO8859-1/htdocs/releases/3.2R/errata.sgml | 18 +- en_US.ISO8859-1/htdocs/releases/3.2R/notes.sgml | 10 +- en_US.ISO8859-1/htdocs/releases/3.3R/errata.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/3.3R/notes.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/3.4R/announce.sgml | 18 +- en_US.ISO8859-1/htdocs/releases/3.4R/errata.sgml | 8 +- en_US.ISO8859-1/htdocs/releases/3.4R/notes.sgml | 10 +- en_US.ISO8859-1/htdocs/releases/3.5R/announce.sgml | 18 +- en_US.ISO8859-1/htdocs/releases/3.5R/errata.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/3.5R/notes.sgml | 10 +- en_US.ISO8859-1/htdocs/releases/4.0R/announce.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/4.0R/errata.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/4.0R/notes.sgml | 32 +- en_US.ISO8859-1/htdocs/releases/4.1.1R/errata.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/4.1.1R/notes.sgml | 32 +- en_US.ISO8859-1/htdocs/releases/4.1R/errata.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/4.1R/notes.sgml | 26 +- en_US.ISO8859-1/htdocs/releases/4.2R/errata.sgml | 6 +- en_US.ISO8859-1/htdocs/releases/4.2R/notes.sgml | 34 +- en_US.ISO8859-1/htdocs/releases/4.3R/errata.sgml | 10 +- en_US.ISO8859-1/htdocs/releases/4.5R/qa.sgml | 12 +- en_US.ISO8859-1/htdocs/releases/4.5R/schedule.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/5.5R/todo.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/6.0R/stress.xsl | 2 +- en_US.ISO8859-1/htdocs/releases/6.0R/todo.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/6.1R/stress.xsl | 2 +- en_US.ISO8859-1/htdocs/releases/6.2R/announce.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/6.2R/stress.xsl | 2 +- en_US.ISO8859-1/htdocs/releases/6.3R/announce.sgml | 8 +- en_US.ISO8859-1/htdocs/releases/7.0R/announce.sgml | 4 +- en_US.ISO8859-1/htdocs/releases/7.0R/stress.xsl | 2 +- en_US.ISO8859-1/htdocs/releases/7.1R/announce.sgml | 2 +- en_US.ISO8859-1/htdocs/releases/7.4R/announce.sgml | 2 +- en_US.ISO8859-1/htdocs/releng/charter.sgml | 14 +- en_US.ISO8859-1/htdocs/relnotes.sgml | 8 +- en_US.ISO8859-1/htdocs/search/Makefile | 2 +- en_US.ISO8859-1/htdocs/search/opensearch/Makefile | 4 +- en_US.ISO8859-1/htdocs/search/search.sgml | 106 +- en_US.ISO8859-1/htdocs/smp/index.sgml | 4 +- en_US.ISO8859-1/htdocs/support/Makefile | 2 +- en_US.ISO8859-1/htdocs/support/bugreports.sgml | 2 +- en_US.ISO8859-1/htdocs/tutorials/index.sgml | 2 +- en_US.ISO8859-1/htdocs/y2kbug.sgml | 70 +- en_US.ISO8859-1/share/sgml/catalog | 2 +- en_US.ISO8859-1/share/sgml/freebsd.dsl | 4 +- en_US.ISO8859-1/share/sgml/glossary.ent | 6 +- .../slides/20050513-bsdcan-slides/slides.xml | 2 +- en_US.ISO8859-1/slides/freebsd-general/slides.xml | 2 +- 321 files changed, 4822 insertions(+), 4822 deletions(-) (limited to 'en_US.ISO8859-1') 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" SubSection "Display" Viewport 0 0 Modes "1280x1024" -EndSubSection +EndSubSection A color depth of 24 bits is needed for desktop composition, change the above subsection to: @@ -371,7 +371,7 @@ emerald --replace & - When I run the command to start + When I run the command to start Compiz Fusion, the X server crashes and I am back at the console. What is wrong? 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 @@ Compiling conserver - See the section on conserver versions + See the section on conserver versions ; the version I use is available in the &os; ports collection; however, it is not the only one.) - There are two ways to install conserver. + There are two ways to install conserver. You can either compile from the source or use the &os; ports framework. @@ -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 conserver.cf file on every host. This command - will fetch, patch, configure, compile and install the + will fetch, patch, configure, compile and install the conserver application. You can then run make package to create a @@ -424,7 +424,7 @@ From the source tarball If you prefer, you can download conserver - 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/ cuaE0 "/usr/local/sbin/conserver" unknown on insecure - This has two advantages: init will restart + This has two advantages: init 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 conserver process to be directed to the named tty (in this case cuaE0). This is useful because you @@ -574,14 +574,14 @@ $1$VTd27V2G$eFu23iHpLvCBM5nQtNlKj/ 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 - conserver + conserver from the ttys file is that it cannot run in daemon mode (else &man.init.8; would continually restart it). This means - conserver will not write a PID file, + conserver will not write a PID file, which makes it hard to rotate the log files. So we start conserver from an rc.d script. - If you installed conserver via the port, + If you installed conserver via the port, there will be a conserver.sh.sample file installed in /usr/local/etc/rc.d. Copy and/or rename this to @@ -1217,11 +1217,11 @@ exit 0 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 BREAK as a command to halt the + recognises a serial BREAK as a command to halt the OS and return to the ROM monitor prompt. A serial BREAK - 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 BREAK 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 Fortunately, Sun have come up with a set of fixes for this. For &solaris; 2.6 and later, the kbd(1) command can be used - to disable the ROM-on-BREAK behaviour. This is a good start, + to disable the ROM-on-BREAK 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. @@ -1342,7 +1342,7 @@ exit 0 conserver is not really suitable for use across untrusted networks (such as the Internet). Use of conserver-only passwords (in the conserver.passwd file) slightly - mitigate this problem, but anyone sniffing a + mitigate this problem, but anyone sniffing a conserver 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 idiosyncratic manner (using a preprocessor to generate C code). Version 8.5 is maintained by Kevin S. Braunsdorf ksb+conserver@sa.fedex.com who did most of the original - work on conserver, + work on conserver, 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). - + Beginning with December 2001, Brian's version (currently 8.1.9) is also presented in ports collection at comms/conserver-com. 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: 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 @@ - Alex Steiner + Alex Steiner ast@treibsand.com @@ -4558,7 +4558,7 @@ Jesse Kempf - jessekempf@gmail.com + jessekempf@gmail.com @@ -8295,7 +8295,7 @@ - Philippe Pepiot + Philippe Pepiot phil@philpep.org 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 @@ &a.chinsan; - + &a.davide; 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..4b7aaa1032 100644 --- a/en_US.ISO8859-1/articles/cvsup-advanced/article.sgml +++ b/en_US.ISO8859-1/articles/cvsup-advanced/article.sgml @@ -32,7 +32,7 @@ The present article assumes a basic understanding of CVSup - operation. It documents several delicate issues connected with + operation. It documents several delicate issues connected with source synchronization via CVSup, viz. effective solutions to the problem of stale files as well as special source updating cases; which issues are likely to cause apparently inexplicable @@ -42,17 +42,17 @@ Preface - - This document is the fruit of the author's attempts to + + This document is the fruit of the author's attempts to fully understand the niceties of CVSup & source updating. :-) - While the author has made every effort to make these pages - as informative and correct as possible, he is only human and + While the author has made every effort to make these pages + as informative and correct as possible, he is only human and may have made all sorts of typos, mistakes, etc. He will be very grateful for any comments and/or suggestions you send to his e-mail address, bartequi@neomedia.it. - + Introduction @@ -63,7 +63,7 @@ FAQ, you may have noticed Question 12 & 13. - When updating any collection of sources (eg + When updating any collection of sources (eg /usr/ports), &man.cvsup.1; makes use of the related checkouts file in order to perform the updating process in the most efficient and correct way. In this example @@ -72,12 +72,12 @@ FAQ, your base is /usr. A checkouts file contains information on the current status - of your sources—in a way, a sort of photograph. This + of your sources—in a way, a sort of photograph. This significant information enables cvsup to retrieve updates most effectively. Further, and maybe more important, it enables cvsup to correctly manage your sources by locally deleting any files no longer present in the repository, thus leaving no stale files - on your system. In fact, without a checkouts file, cvsup would + on your system. In fact, without a checkouts file, cvsup would not know which files your collection was composed of (cf &man.cvsup.1; and the fallback method for details); as a result, it could not delete on your system those files no longer present @@ -95,9 +95,9 @@ FAQ, A useful python script: <command>cvsupchk</command> - Alternatively, in order to examine your sources for - inconsistencies, you may wish to utilize the cvsupchk python - script; which script is currently found in + Alternatively, in order to examine your sources for + inconsistencies, you may wish to utilize the cvsupchk python + script; which script is currently found in /usr/ports/net/cvsup/work/cvsup-16.1/contrib/cvsupchk, together with a nice README. Prerequisites: @@ -127,9 +127,9 @@ FAQ, &prompt.user; /path/to/cvsupchk -d /usr -c /usr/sup/src-all/checkouts.cvs:RELENG_4 | more - In each case, cvsupchk will inspect your sources for - inconsistencies by utilizing the information contained in the - related checkouts file. Such anomalies as deleted files being + In each case, cvsupchk will inspect your sources for + inconsistencies by utilizing the information contained in the + related checkouts file. Such anomalies as deleted files being present (aka stale files), missing checked-out files, extra RCS files, and dead directories will be printed to standard output. @@ -147,15 +147,15 @@ FAQ, src-all If you specify eg tag=A in your supfile, cvsup will create - a checkouts file called checkouts.cvs:A: + a checkouts file called checkouts.cvs:A: for instance, if tag=RELENG_4, a checkouts file called - checkouts.cvs:RELENG_4 is generated. + checkouts.cvs:RELENG_4 is generated. This file will be used to retrieve and/or store information identifying your 4-STABLE sources. When tracking src-all, if you wish to - pass from tag=A to tag=B (A less/greater than B not making - any difference) and if your checkouts file is + pass from tag=A to tag=B (A less/greater than B not making + any difference) and if your checkouts file is checkouts.cvs:A, the following actions should be performed: @@ -178,8 +178,8 @@ checkouts.cvs:B The cvsup utility will look for checkouts.cvs:B—in - that the target is B; that is, cvsup will make use of - the information contained therein to correctly manage your + that the target is B; that is, cvsup will make use of + the information contained therein to correctly manage your sources. The benefits: @@ -191,17 +191,17 @@ checkouts.cvs:B - less load is placed on the server, in that cvsup + less load is placed on the server, in that cvsup operates in the most efficient way. - For example, A=RELENG_4, B=.. The period in B=. means - -CURRENT. This is a rather typical update, from 4-STABLE - to -CURRENT. While it is straightforward to downgrade your - sources (e.g., from -CURRENT to -STABLE), downgrading a system - is quite another matter. You are STRONGLY advised not to + For example, A=RELENG_4, B=.. The period in B=. means + -CURRENT. This is a rather typical update, from 4-STABLE + to -CURRENT. While it is straightforward to downgrade your + sources (e.g., from -CURRENT to -STABLE), downgrading a system + is quite another matter. You are STRONGLY advised not to attempt such an operation, unless you know exactly what you are doing. @@ -209,8 +209,8 @@ checkouts.cvs:B Updating to the same tag as of a different date - If you wish to switch from tag=A to tag=A as of a - different GMT date (say, date=D), you will execute the + If you wish to switch from tag=A to tag=A as of a + different GMT date (say, date=D), you will execute the following: @@ -225,25 +225,25 @@ checkouts.cvs:B Whether the new date precedes that of the last sync - operation with tag=A or not, it is immaterial. For example, - in order to specify the date August 27, 2000, 10:00:00 GMT + operation with tag=A or not, it is immaterial. For example, + in order to specify the date August 27, 2000, 10:00:00 GMT you write the line: src-all tag=RELENG_4 date=2000.08.27.10.00.00 - The format of a date is rigid. You have to specify - all the components of the date: century (20, i.e., the 21st - century, must be supplied whereas 19, the past century, can - be omitted), year, month, day, hour, minutes, seconds—as - shown in the above example. For more information, please + The format of a date is rigid. You have to specify + all the components of the date: century (20, i.e., the 21st + century, must be supplied whereas 19, the past century, can + be omitted), year, month, day, hour, minutes, seconds—as + shown in the above example. For more information, please see &man.cvsup.1;. - Whether or not a date is specified, the checkouts file + Whether or not a date is specified, the checkouts file is called checkouts.cvs:A (e.g., checkouts.cvs:RELENG_4). As a result, - no particular action is needed in order to revert to the - previous state: you have to modify the date in the supfile, + no particular action is needed in order to revert to the + previous state: you have to modify the date in the supfile, and run csvup again. @@ -264,9 +264,9 @@ checkouts.cvs:B ports-all tag=. All subsequent updates will be carried out smoothly. - If you have been reading the apparently nit-picking - remarks in these sections, you will probably have recognized - the potential for trouble in a source updating process. + If you have been reading the apparently nit-picking + remarks in these sections, you will probably have recognized + the potential for trouble in a source updating process. A number of people have actually run into problems. You have been warned. :-) diff --git a/en_US.ISO8859-1/articles/dialup-firewall/article.sgml b/en_US.ISO8859-1/articles/dialup-firewall/article.sgml index bc604f144c..1135edfa27 100644 --- a/en_US.ISO8859-1/articles/dialup-firewall/article.sgml +++ b/en_US.ISO8859-1/articles/dialup-firewall/article.sgml @@ -72,7 +72,7 @@ support. &os; 4.X users should consult the &man.ipfw.8; manual page for more information on using IPFW2 on their systems, and should pay particular attention to the - USING IPFW2 IN FreeBSD-STABLE + USING IPFW2 IN FreeBSD-STABLE section. @@ -180,7 +180,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/en_US.ISO8859-1/articles/diskless-x/article.sgml b/en_US.ISO8859-1/articles/diskless-x/article.sgml index 198cb53a03..843d1640ee 100644 --- a/en_US.ISO8859-1/articles/diskless-x/article.sgml +++ b/en_US.ISO8859-1/articles/diskless-x/article.sgml @@ -14,7 +14,7 @@
Diskless X Server: a how to guide - + Jerry @@ -25,16 +25,16 @@ - + 28-December-1996 $FreeBSD$ - + 1996 Jerry Kendall - + &tm-attrib.freebsd; &tm-attrib.3com; @@ -56,15 +56,15 @@ system is a 486DX2-66. I set up a diskless FreeBSD (complete) that uses no local disk. The server in that case is a Sun 670MP running &sunos; 4.1.3. The same setup configuration was needed for both. - + I am sure that there is stuff that needs to be added to this. Please send me any comments. - + Creating the boot floppy (On the diskless system) - + Since the network boot loaders will not work with some of the TSR's and such that &ms-dos; uses, it is best to create a dedicated boot floppy or, if you can, create an &ms-dos; menu that will (via the @@ -72,7 +72,7 @@ ask what configuration to load when the system starts. The later is the method that I use and it works great. My &ms-dos; (6.x) menu is below. - + <filename>config.sys</filename> @@ -105,10 +105,10 @@ nb8390.com :end - + Getting the network boot programs (On the server) - + Compile the net-boot programs that are located in /usr/src/sys/i386/boot/netboot. You should read the comments at the top of the Makefile. Adjust as @@ -119,10 +119,10 @@ nb8390.com server. It will load the kernel from the boot server. At this point, put both programs on the &ms-dos; boot floppy created earlier. - + Determine which program to run (On the diskless system) - + If you know the chipset that your Ethernet adapter uses, this is easy. If you have the NS8390 chipset, or a NS8390 based chipset, use nb8390.com. If you have a &tm.3com; 509 based chipset, @@ -134,13 +134,13 @@ nb8390.com Booting across the network - + Boot the diskless system with out any config.sys/autoexec.bat files. Try running the boot program for your Ethernet adapter. My Ethernet adapter is running in WD8013 16bit mode so I run nb8390.com - + C:> cd \netboot C:> nb8390 @@ -165,18 +165,18 @@ Searching for server... message, verify that you did indeed set the compile time defines in the Makefile correctly. - + Allowing systems to boot across the network (On the server) - + Make sure the /etc/inetd.conf file has entries for tftp and bootps. Mine are listed below: - + tftp dgram udp wait nobody /usr/libexec/tftpd tftpd /tftpboot # # Additions by who ever you are bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab - + If you have to change the /etc/inetd.conf file, send a HUP signal to &man.inetd.8;. To do this, get the process ID of inetd with ps -ax | grep inetd | grep -v @@ -200,7 +200,7 @@ bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab - + The lines are as follows: @@ -280,10 +280,10 @@ hostname altair.example.com The NFS mounted root filesystem will be mounted read only. - + The hierarchy for the diskless system can be re-mounted allowing read-write operations if required. - + I use my spare 386DX-40 as a dedicated X terminal. The hierarchy for altair is: @@ -314,7 +314,7 @@ hostname altair.example.com -r-xr-xr-x 1 root bin 73728 Dec 13 22:38 ./sbin/mount -r-xr-xr-x 1 root wheel 1992 Jun 10 1995 ./dev/MAKEDEV.local -r-xr-xr-x 1 root wheel 24419 Jun 10 1995 ./dev/MAKEDEV - + If you are not using &man.devfs.5; (which is the default in FreeBSD 5.X), you should make sure that you do not forget to run MAKEDEV all in the diff --git a/en_US.ISO8859-1/articles/euro/article.sgml b/en_US.ISO8859-1/articles/euro/article.sgml index e5057bfc97..e52d0d63a2 100644 --- a/en_US.ISO8859-1/articles/euro/article.sgml +++ b/en_US.ISO8859-1/articles/euro/article.sgml @@ -7,7 +7,7 @@
- The Euro symbol on + <title>The Euro symbol on <systemitem class="osname">FreeBSD</systemitem> @@ -29,7 +29,7 @@ 2003 The FreeBSD Documentation Project - + &tm-attrib.freebsd; &tm-attrib.general; @@ -46,7 +46,7 @@ will first focus on the more important parts like being able to correctly display the symbol on the console. Later sections will deal with configuring particular programs like - X11. + X11. Lots of helpful input came from Oliver Fromme, Tom Rhodes and @@ -59,16 +59,16 @@ The Euro in a nutshell - If you already feel comfortable with - localization as - described in the FreeBSD - Handbook you might be only interested in the following facts which - will get you started quickly: + If you already feel comfortable with + localization as + described in the FreeBSD + Handbook you might be only interested in the following facts which + will get you started quickly: ISO8859-15 - + This is a slight modification of the commonly used ISO8859-1 character map. It includes the Euro symbol. Used for the @@ -89,8 +89,8 @@ /usr/share/syscons/keymaps/*.iso.kbd - Appropriate keyboard maps depending on your language. Set your - keymap entry in rc.conf to + Appropriate keyboard maps depending on your language. Set your + keymap entry in rc.conf to one of these. @@ -124,7 +124,7 @@ A general remark - + In the following sections we will often refer to ISO8859-15. This is the standard notation starting with FreeBSD 4.5. In older @@ -132,23 +132,23 @@ ISO_8859-15 or DIS_8859-15. - If you are using an older version of - FreeBSD, be sure to take a + If you are using an older version of + FreeBSD, be sure to take a look at /usr/share/locale/ in order to find out which naming convention is in place. The console - + Setting up your console font Depending on your console resolution and size you will need one of the following lines in rc.conf: - font8x16="iso15-8x16.fnt" # from /usr/share/syscons/fonts/* -font8x14="iso15-8x14.fnt" + font8x16="iso15-8x16.fnt" # from /usr/share/syscons/fonts/* +font8x14="iso15-8x14.fnt" font8x8="iso15-8x8.fnt" This will effectively select the ISO8859-15 also known as Latin-9 @@ -200,8 +200,8 @@ BEGIN { combination is necessary (e.g.: Alt Gre) to decimal value 164. If running into problems, the best way to check is to take a look at - /usr/share/syscons/keymaps/*.kbd. The format of - the key mapping files is described in &man.keyboard.4;. + /usr/share/syscons/keymaps/*.kbd. The format of + the key mapping files is described in &man.keyboard.4;. &man.kbdcontrol.1; can be used to load a custom keymap. Once the correct keyboard map is selected, it should be added to @@ -210,13 +210,13 @@ BEGIN { keymap="german.iso" # or another map As stated above, this step has most probably already been taken - by you at installation time (with - sysinstall). If not, either reboot or + by you at installation time (with + sysinstall). If not, either reboot or load the new keymap via &man.kbdcontrol.1;. - To verify the keyboard mapping, switch to a new console and at + To verify the keyboard mapping, switch to a new console and at the login prompt, instead of logging in, try to - type the Euro key. If it is not working, either + type the Euro key. If it is not working, either file a bug report via &man.send-pr.1; or make sure you in fact chose the right keyboard map. @@ -226,13 +226,13 @@ BEGIN { tcsh. - + Fixing the environment variables - The shells (bash, tcsh) revert to the &man.readline.3; library - which in turn respects the LC_CTYPE environment - variable. LC_CTYPE must be set before the shell is + The shells (bash, tcsh) revert to the &man.readline.3; library + which in turn respects the LC_CTYPE environment + variable. LC_CTYPE must be set before the shell is completely running. Luckily it suffices to add the line: export LC_CTYPE=de_DE.ISO8859-15 @@ -250,11 +250,11 @@ BEGIN { however. - An alternative to modifying .login and + An alternative to modifying .login and .bash_profile is to set the environment variables through the &man.login.conf.5; mechanism. This approach has the advantage of assigning login classes to certain users (e.g. - French users, Italian users, etc) in one + French users, Italian users, etc) in one place. @@ -294,14 +294,14 @@ variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15 /usr/X11R6/lib/X11/app-defaults and add the correct font. Let us demonstrate this with xterm. - + &prompt.root; cd /usr/X11R6/lib/X11/app-defaults/ &prompt.root; vi XTerm Add the following line to the beginning of the file: *font: -misc-fixed-medium-r-normal-*-*-120-*-*-c-*-iso8859-15 - + Finally, restart X and make sure, fonts can be displayed by executing the above awk script. All major applications should respect the keyboard mapping and the font @@ -310,7 +310,7 @@ variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15 Open problems - + Of course, the author would like to receive feedback. In addition, at least let me know if you have fixes for one of these open problems: @@ -320,7 +320,7 @@ variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-15 Describe alternative way of setting up Xorg: x11/xkeycaps - + Settings in GNOME diff --git a/en_US.ISO8859-1/articles/explaining-bsd/article.sgml b/en_US.ISO8859-1/articles/explaining-bsd/article.sgml index 68618c73ec..7b963700f6 100644 --- a/en_US.ISO8859-1/articles/explaining-bsd/article.sgml +++ b/en_US.ISO8859-1/articles/explaining-bsd/article.sgml @@ -118,9 +118,9 @@ - + - What, a real &unix;? + What, a real &unix;? The BSD operating systems are not clones, but open source derivatives of AT&T's Research &unix; operating system, which is also @@ -189,7 +189,7 @@ DragonFlyBSD split off from FreeBSD. - + Why is BSD not better known? diff --git a/en_US.ISO8859-1/articles/fonts/article.sgml b/en_US.ISO8859-1/articles/fonts/article.sgml index 6cf7a5c96a..c24d60e074 100644 --- a/en_US.ISO8859-1/articles/fonts/article.sgml +++ b/en_US.ISO8859-1/articles/fonts/article.sgml @@ -539,7 +539,7 @@ GS>quit Using type 1 fonts with Groff Now that the new font can be used by both X11 and - Ghostscript, how can one use the new font + Ghostscript, how can one use the new font with groff? First of all, since we are dealing with type 1 &postscript; fonts, the groff device that is applicable is the ps @@ -852,7 +852,7 @@ Converting 3of9.ttf to A.pfa and B.afm. fonts available in this format. Unfortunately, there are few applications that I am aware of - that can use this format: Ghostscript + that can use this format: Ghostscript and Povray come to mind. Ghostscript's support, according to the documentation, is rudimentary and the results are likely to be inferior to type 1 @@ -879,7 +879,7 @@ Converting 3of9.ttf to A.pfa and B.afm. - xfstt is another font server for + xfstt is another font server for X11, available under . @@ -916,7 +916,7 @@ Converting 3of9.ttf to A.pfa and B.afm. - Checkout the fonts that come with the Ports Collection in + Checkout the fonts that come with the Ports Collection in x11-fonts/ diff --git a/en_US.ISO8859-1/articles/formatting-media/article.sgml b/en_US.ISO8859-1/articles/formatting-media/article.sgml index 7a695160ec..eacc599bba 100644 --- a/en_US.ISO8859-1/articles/formatting-media/article.sgml +++ b/en_US.ISO8859-1/articles/formatting-media/article.sgml @@ -65,7 +65,7 @@ There are two possible modes of disk formatting: - + compatibility mode: Arranging a disk so that it has a slice table for use with other @@ -95,7 +95,7 @@ allowing access to the Label and Partition editors and a Write feature which will update just the selected disk and slice without affecting other disks. The other method is running - the tools manually from a root command line. For + the tools manually from a root command line. For dedicated mode, only three or four commands are involved while sysinstall requires some manipulation. @@ -155,7 +155,7 @@ now. --> Each filesystem and swap area on a disk resides in a partition. Maintained using the disklabel utility. - + sector: Smallest subdivision of a disk. One sector usually represents 512 bytes of data. @@ -188,7 +188,7 @@ now. --> to the system and a disk placed in the drive during startup, so the kernel can determine the drive's geometry. Check the dmesg output and make sure your device and - the disk's size is listed. If the kernel reports + the disk's size is listed. If the kernel reports Can't get the size @@ -224,11 +224,11 @@ now. --> - Start sysinstall as root by typing + Start sysinstall as root by typing &prompt.root; /stand/sysinstall - + from the command prompt. @@ -249,12 +249,12 @@ now. --> If you are using this entire disk for FreeBSD, select A. - + When asked if you still want to do this, answer Yes. - + Select Write. @@ -263,7 +263,7 @@ now. --> When warned about writing on installed systems, answer Yes. - + When asked about installing a boot loader, select @@ -293,13 +293,13 @@ now. --> C to Create a partition, accept the default size, partition type Filesystem, and a mountpoint (which is not used). - + Enter W when done and confirm to continue. The filesystem will be newfs'd for you, unless you select otherwise (for new partitions you will want to - do this!). You will get the error: + do this!). You will get the error: Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory @@ -330,7 +330,7 @@ now. --> If you need to edit the disklabel to create multiple partitions (such as swap), use the following: - + &prompt.root; dd if=/dev/zero of=/dev/ad2 count=2 &prompt.root; disklabel /dev/ad2 > /tmp/label @@ -363,11 +363,11 @@ now. --> - Start sysinstall as root by typing + Start sysinstall as root by typing &prompt.root; /stand/sysinstall - + from the command prompt. @@ -388,10 +388,10 @@ now. --> If you are using this entire disk for FreeBSD, select A. - + - When asked: + When asked: Do you want to do this with a true partition entry so as to remain @@ -419,18 +419,18 @@ drive(s)? You will be asked about the boot manager, select None again. - + Select Label from the Index menu. - + Label as desired. For a single partition, accept the default size, type filesystem, and a mountpoint (which is not used). - + The filesystem will be newfs'd for you, unless you @@ -438,7 +438,7 @@ drive(s)? this!). You will get the error: - Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory + Error mounting /mnt/dev/ad2s1e on /mnt/blah : No such file or directory Ignore. @@ -479,7 +479,7 @@ drive(s)? When newfsing the drive, do NOT newfs the `c' partition. Instead, newfs the partition where the non-swap space lies. - + Add an entry to /etc/fstab as @@ -489,7 +489,7 @@ drive(s)? /dev/ad0b none swap sw 0 0 - + Change /dev/ad0b to the device of the newly added space. @@ -510,7 +510,7 @@ swapon: added /dev/da0b as swap space Copying the Contents of Disks - + Submitted By: Renaud Waldura (renaud@softway.com) diff --git a/en_US.ISO8859-1/articles/freebsd-questions/article.sgml b/en_US.ISO8859-1/articles/freebsd-questions/article.sgml index 25768fbc07..9d73bd5a53 100644 --- a/en_US.ISO8859-1/articles/freebsd-questions/article.sgml +++ b/en_US.ISO8859-1/articles/freebsd-questions/article.sgml @@ -42,10 +42,10 @@ list. - + Introduction - + FreeBSD-questions is a mailing list maintained by the FreeBSD project to help people who have questions about the normal use of FreeBSD. Another group, FreeBSD-hackers, @@ -62,7 +62,7 @@ url="http://www.catb.org/~esr/faqs/hacker-howto.html">How To Become A Hacker - + This is a regular posting aimed to help both those seeking advice from FreeBSD-questions (the newcomers), and also those who answer the questions (the hackers). @@ -80,7 +80,7 @@ FreeBSD-questions. In the following section, I recommend how to submit a question; after that, we will look at how to answer one. - + How to subscribe to FreeBSD-questions @@ -107,7 +107,7 @@ If you ever should want to leave the list, you will need the information there. See the next section for more details. - + How to unsubscribe from FreeBSD-questions @@ -129,7 +129,7 @@ General information about the mailing list is at: If you ever want to unsubscribe or change your options (e.g., switch to or from digest mode, change your password, etc.), visit your subscription page at: - + http://lists.freebsd.org/mailman/options/freebsd-questions/grog%40lemsi.de You can also make such adjustments via email by sending a message to: @@ -175,7 +175,7 @@ your options page that will email your current password to you. FreeBSD-hackers. In some cases, it is not really clear which group you should ask. The following criteria should help for 99% of all questions, however: - + If the question is of a general nature, ask @@ -183,13 +183,13 @@ your options page that will email your current password to you. about installing FreeBSD or the use of a particular &unix; utility. - + If you think the question relates to a bug, but you are not sure, or you do not know how to look for it, send the message to FreeBSD-questions. - + If the question relates to a bug, and you are sure that it is a bug (for example, you can @@ -216,7 +216,7 @@ your options page that will email your current password to you. Before submitting a question - + You can (and should) do some things yourself before asking a question on one of the mailing lists: @@ -260,10 +260,10 @@ your options page that will email your current password to you. - + How to submit a question - + When submitting a question to FreeBSD-questions, consider the following points: @@ -280,7 +280,7 @@ your options page that will email your current password to you. you do not. In the rest of this document, we will look at how to get the most out of your question to FreeBSD-questions. - + Not everybody who answers FreeBSD questions reads every message: they look at the subject line and decide whether it interests them. @@ -297,7 +297,7 @@ your options page that will email your current password to you. speak English as their first language, and we try to make allowances for that, but it is really painful to try to read a message written full of typos or without any line breaks. - + Do not underestimate the effect that a poorly formatted mail message has, not just on the FreeBSD-questions mailing list. Your mail message is all people see of you, and if it is poorly @@ -347,7 +347,7 @@ your options page that will email your current password to you. use mailers which do not get on very well with MIME. - + Make sure your time and time zone are set correctly. This may seem a little silly, since your message still gets there, but many @@ -377,7 +377,7 @@ your options page that will email your current password to you. sources, though of course you should not be sending questions about -CURRENT to FreeBSD-questions. - + With any problem which could be hardware related, tell us about your hardware. In case of doubt, assume it is possible that it is hardware. What kind of @@ -389,7 +389,7 @@ your options page that will email your current password to you. tells not just what hardware you are running, but what version of FreeBSD as well. - + If you get error messages, do not say I get error messages, say (for example) I get the error @@ -435,7 +435,7 @@ your options page that will email your current password to you. This redirects the information to the file /tmp/dmesg.out. - + If you do all this, and you still do not get an answer, there could be other reasons. For example, the problem is so complicated @@ -447,7 +447,7 @@ your options page that will email your current password to you. only make you unpopular. - + To summarize, let's assume you know the answer to the following question (yes, it is the same one in each case). You choose which of these two questions you would be more prepared to @@ -490,7 +490,7 @@ fine, but when I try to reboot the system, I get the message you are talking about. Do not forget to trim unnecessary text out, though. - + The text in the subject line stays the same (you did remember to put one in, did you not?). Many mailers will sort messages by @@ -506,7 +506,7 @@ fine, but when I try to reboot the system, I get the message - + How to answer a question @@ -524,7 +524,7 @@ fine, but when I try to reboot the system, I get the message check this is to sort your incoming mail by subject: then (hopefully) you will see the question followed by any answers, all together. - + If somebody has already answered it, it does not automatically mean that you should not send another answer. But it makes sense to read all the other answers first. @@ -570,14 +570,14 @@ fine, but when I try to reboot the system, I get the message send messages with hundreds of CCs. If this is the case, be sure to trim the Cc: lines appropriately. - + Include relevant text from the original message. Trim it to the minimum, but do not overdo it. It should still be possible for somebody who did not read the original message to understand what you are talking about. - + Use some technique to identify which text came from the original message, and which text you add. I personally find that prepending @@ -599,7 +599,7 @@ fine, but when I try to reboot the system, I get the message text such as Re: . If your mailer does not do it automatically, you should do it manually. - + If the submitter did not abide by format conventions (lines too long, inappropriate subject line), please fix diff --git a/en_US.ISO8859-1/articles/geom-class/Makefile b/en_US.ISO8859-1/articles/geom-class/Makefile index 58e659e2a9..80e7914137 100644 --- a/en_US.ISO8859-1/articles/geom-class/Makefile +++ b/en_US.ISO8859-1/articles/geom-class/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: Writing a GEOM Class diff --git a/en_US.ISO8859-1/articles/gjournal-desktop/article.sgml b/en_US.ISO8859-1/articles/gjournal-desktop/article.sgml index c1535e5f29..4557dfb241 100644 --- a/en_US.ISO8859-1/articles/gjournal-desktop/article.sgml +++ b/en_US.ISO8859-1/articles/gjournal-desktop/article.sgml @@ -69,7 +69,7 @@ system and data). It should be followed during a fresh installation of &os;. The steps are simple enough and do not require overly complex interaction with the command line. - + After reading this article, you will know: @@ -77,7 +77,7 @@ How to reserve space for journaling during a new installation of &os;. - + How to load and enable the geom_journal module (or build support for it in your custom kernel). @@ -194,7 +194,7 @@ For more information about journaling, please read the manual - page of &man.gjournal.8;. + page of &man.gjournal.8;. @@ -221,7 +221,7 @@ In our example, an 80 GB disk is used. The following screenshot shows the default partitions created by Disklabel during installation: - + @@ -250,7 +250,7 @@ on a typical desktop will cause no harm. If the file system is lightly used (quite probable for a desktop) you may wish to allocate less disk space for its journal. - + In our example, we journal both /usr and /var. You may of course adjust the procedure to your own needs. @@ -283,7 +283,7 @@ partitions to provide for the journals of /usr and /var. The final result is shown in the following screenshot: - + @@ -470,7 +470,7 @@ GEOM_JOURNAL: Journal ad0s1f clean. was created. Creating the journal would be as simple as: &prompt.root; gjournal label ad1s1d - + The journal size will be 1 GB by default. You may adjust it by using the option. The value can be given in bytes, or appended by K, M or @@ -500,7 +500,7 @@ GEOM_JOURNAL: Journal ad0s1f clean. options UFS_GJOURNAL # Note: This is already in GENERIC options GEOM_JOURNAL # You will have to add this one - + Rebuild and reinstall your kernel following the relevant instructions in the &os; Handbook. @@ -586,7 +586,7 @@ GEOM_JOURNAL: Journal ad0s1f clean. can then be used for other purposes, if you so wish. Login as root and switch to single user mode: - + &prompt.root; shutdown now Unmount the journaled partitions: @@ -639,7 +639,7 @@ tunefs: soft updates set - + @@ -659,7 +659,7 @@ tunefs: soft updates set This post in &a.current.name; by &man.gjournal.8;'s developer, &a.pjd;. - + This post in &a.questions.name; by &a.ivoras;. diff --git a/en_US.ISO8859-1/articles/hubs/article.sgml b/en_US.ISO8859-1/articles/hubs/article.sgml index 9e4a95f06f..0702bd0e16 100644 --- a/en_US.ISO8859-1/articles/hubs/article.sgml +++ b/en_US.ISO8859-1/articles/hubs/article.sgml @@ -512,7 +512,7 @@ cvspserver stream tcp nowait root /usr/bin/cvs cvs -f -l -R -T /anoncvstmp --all Please have look at the CVSup documentation like &man.cvsup.1; and consider using the option. This reduces I/O operations by assuming the - recorded information about each file is correct. + recorded information about each file is correct. diff --git a/en_US.ISO8859-1/articles/laptop/article.sgml b/en_US.ISO8859-1/articles/laptop/article.sgml index 73e9e968c7..4f33c72f89 100644 --- a/en_US.ISO8859-1/articles/laptop/article.sgml +++ b/en_US.ISO8859-1/articles/laptop/article.sgml @@ -56,7 +56,7 @@ &xorg; - + Recent versions of &xorg; work with most display adapters available on laptops these days. Acceleration may not be supported, but a generic SVGA configuration should work. @@ -81,9 +81,9 @@ hardware. Most laptops come with two buttons on their pointing - devices, which is rather problematic in X (since the middle - button is commonly used to paste text); you can map a - simultaneous left-right click in your X configuration to + devices, which is rather problematic in X (since the middle + button is commonly used to paste text); you can map a + simultaneous left-right click in your X configuration to a middle button click with the line @@ -92,24 +92,24 @@ in the xorg.conf file in the InputDevice section. - + Modems - + Laptops usually come with internal (on-board) modems. - Unfortunately, this almost always means they are + Unfortunately, this almost always means they are winmodems whose functionality is implemented in software, for which only &windows; - drivers are normally available (though a few drivers are beginning + drivers are normally available (though a few drivers are beginning to show up for other operating systems; for example, if your modem has a Lucent LT chipset it might be supported by the comms/ltmdm port). If that is the case, you need to buy an external modem: the most compact option is - probably a PC Card (PCMCIA) modem, discussed below, but - serial or USB modems may be cheaper. Generally, regular - modems (non-winmodems) should work fine. + probably a PC Card (PCMCIA) modem, discussed below, but + serial or USB modems may be cheaper. Generally, regular + modems (non-winmodems) should work fine. - + PCMCIA (PC Card) devices @@ -124,24 +124,24 @@ &os; 4.X supports 16-bit PCMCIA cards, and &os; 5.X supports both 16-bit and - 32-bit (CardBus) cards. A database of supported - cards is in the file /etc/defaults/pccard.conf. + 32-bit (CardBus) cards. A database of supported + cards is in the file /etc/defaults/pccard.conf. Look through it, and preferably buy cards listed there. Cards not - listed may also work as generic devices: in - particular most modems (16-bit) should work fine, provided they - are not winmodems (these do exist even as PC Cards, so watch out). + listed may also work as generic devices: in + particular most modems (16-bit) should work fine, provided they + are not winmodems (these do exist even as PC Cards, so watch out). If your card is recognised as a generic modem, note that the default pccard.conf file specifies a delay time of 10 seconds (to avoid freezes on certain modems); this may well be over-cautious for your modem, so you may want to play with it, reducing it or removing it totally. - Some parts of pccard.conf may need - editing. Check the irq line, and be sure to remove any number - already being used: in particular, if you have an on board sound - card, remove irq 5 (otherwise you may experience hangs when you - insert a card). Check also the available memory slots; if your - card is not being detected, try changing it to one of the other + Some parts of pccard.conf may need + editing. Check the irq line, and be sure to remove any number + already being used: in particular, if you have an on board sound + card, remove irq 5 (otherwise you may experience hangs when you + insert a card). Check also the available memory slots; if your + card is not being detected, try changing it to one of the other allowed values (listed in the manual page &man.pccardc.8;). @@ -156,8 +156,8 @@ (including ISA routing of interrupts, for machines where &os; is not able to use the PCI BIOS) before the &os; 4.4 release. If you have problems, try upgrading your system. - - + + @@ -294,7 +294,7 @@ apm_event NORMRESUME, STANDBYRESUME { The X window system (&xorg;) also includes display power management (look at the &man.xset.1; manual page, and search for - dpms there). You may want to investigate this. However, this, + dpms there). You may want to investigate this. However, this, too, works inconsistently on laptops: it often turns off the display but does not turn off the backlight. diff --git a/en_US.ISO8859-1/articles/ldap-auth/Makefile b/en_US.ISO8859-1/articles/ldap-auth/Makefile index c0266a09d6..df0bcdb4d8 100644 --- a/en_US.ISO8859-1/articles/ldap-auth/Makefile +++ b/en_US.ISO8859-1/articles/ldap-auth/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: LDAP Authentication diff --git a/en_US.ISO8859-1/articles/ldap-auth/article.sgml b/en_US.ISO8859-1/articles/ldap-auth/article.sgml index bdc3562cac..2167ef324e 100644 --- a/en_US.ISO8859-1/articles/ldap-auth/article.sgml +++ b/en_US.ISO8859-1/articles/ldap-auth/article.sgml @@ -52,7 +52,7 @@ explanation of net/nss_ldap and security/pam_ldap for use with client machines services for use with the LDAP server. - + When finished, the reader should be able to configure and deploy a &os; server that can host an LDAP directory, and to configure and deploy a &os; server which can authenticate against @@ -397,7 +397,7 @@ cn: tuser security/pam_ldap is configured via /usr/local/etc/ldap.conf. - + This is a different file than the OpenLDAP library functions' @@ -616,7 +616,7 @@ ldappasswd -D uid="$USER",ou=people,dc=example,dc=org \ Ruby script for changing passwords - + MAC - MAC, + MAC, or Mandatory Access Control, provides fine-tuned access to files and is meant to augment traditional operating system authorization provided by file permissions. Since MAC is diff --git a/en_US.ISO8859-1/articles/linux-emulation/article.sgml b/en_US.ISO8859-1/articles/linux-emulation/article.sgml index b5b65e07d3..7a8e6ee92e 100644 --- a/en_US.ISO8859-1/articles/linux-emulation/article.sgml +++ b/en_US.ISO8859-1/articles/linux-emulation/article.sgml @@ -106,7 +106,7 @@ SysV interprocess communication primitives, copy-on-write, etc. &unix; itself does not exist any more but its ideas have been used by many other operating systems world wide thus forming the so called &unix;-like - operating systems. These days the most influential ones are &linux;, + operating systems. These days the most influential ones are &linux;, Solaris, and possibly (to some extent) &os;. There are in-company &unix; derivatives (AIX, HP-UX etc.), but these have been more and more migrated to the aforementioned systems. Let us summarize typical @@ -345,7 +345,7 @@ ERESTART and EJUSTRETURN errors). Finally an userret() is scheduled, switching the process back to the users-pace. The parameters to - the actual syscall handler are passed in the form of + the actual syscall handler are passed in the form of struct thread *td, struct syscall args * arguments where the second parameter is a pointer to the copied in structure of @@ -627,17 +627,17 @@ program. The code that implements &man.pthread.create.3; in NPTL defines - the clone flags like this: + the clone flags like this: int clone_flags = (CLONE_VM | CLONE_FS | CLONE_FILES | CLONE_SIGNAL - | CLONE_SETTLS | CLONE_PARENT_SETTID + | CLONE_SETTLS | CLONE_PARENT_SETTID -| CLONE_CHILD_CLEARTID | CLONE_SYSVSEM -#if __ASSUME_NO_CLONE_DETACHED == 0 +| CLONE_CHILD_CLEARTID | CLONE_SYSVSEM +#if __ASSUME_NO_CLONE_DETACHED == 0 -| CLONE_DETACHED -#endif +| CLONE_DETACHED +#endif | 0); @@ -1223,7 +1223,7 @@ ... AUE_FORK STD { int linux_fork(void); } -... +... AUE_CLOSE NOPROTO { int close(int fd); } ... @@ -1257,15 +1257,15 @@ The linux_proto.h contains structure definitions of arguments to every syscall, e.g.: - struct linux_fork_args { - register_t dummy; + struct linux_fork_args { + register_t dummy; }; And finally, linux_sysent.c contains structure describing the system entry table, used to actually dispatch a syscall, e.g.: - { 0, (sy_call_t *)linux_fork, AUE_FORK, NULL, 0, 0 }, /* 2 = linux_fork */ + { 0, (sy_call_t *)linux_fork, AUE_FORK, NULL, 0, 0 }, /* 2 = linux_fork */ { AS(close_args), (sy_call_t *)close, AUE_CLOSE, NULL, 0, 0 }, /* 6 = close */ As you can see linux_fork is implemented @@ -1349,7 +1349,7 @@ instruction or between system entries (syscalls and traps). &man.ptrace.2; also lets you set various information in the traced process (registers etc.). &man.ptrace.2; is a &unix;-wide standard - implemented in most &unix;es around the world. + implemented in most &unix;es around the world. &linux; emulation in &os; implements the &man.ptrace.2; facility in linux_ptrace.c. The routines for converting @@ -1379,11 +1379,11 @@ trap is so this is dealt with here. The code is actually very short: - static int -translate_traps(int signal, int trap_code) -{ + static int +translate_traps(int signal, int trap_code) +{ - if (signal != SIGBUS) + if (signal != SIGBUS) return signal; switch (trap_code) { @@ -1394,9 +1394,9 @@ translate_traps(int signal, int trap_code) case T_PAGEFLT: return SIGSEGV; - default: - return signal; - } + default: + return signal; + } } @@ -1523,17 +1523,17 @@ translate_traps(int signal, int trap_code) emulation specific structure attached to the process. The structure attached to the process looks like: - struct linux_emuldata { - pid_t pid; + struct linux_emuldata { + pid_t pid; - int *child_set_tid; /* in clone(): Child.s TID to set on clone */ - int *child_clear_tid;/* in clone(): Child.s TID to clear on exit */ + int *child_set_tid; /* in clone(): Child.s TID to set on clone */ + int *child_clear_tid;/* in clone(): Child.s TID to clear on exit */ - struct linux_emuldata_shared *shared; + struct linux_emuldata_shared *shared; - int pdeath_signal; /* parent death signal */ + int pdeath_signal; /* parent death signal */ - LIST_ENTRY(linux_emuldata) threads; /* list of linux threads */ + LIST_ENTRY(linux_emuldata) threads; /* list of linux threads */ }; The PID is used to identify the &os; process that attaches this @@ -1547,13 +1547,13 @@ translate_traps(int signal, int trap_code) to the list of threads. The linux_emuldata_shared structure looks like: - struct linux_emuldata_shared { + struct linux_emuldata_shared { - int refs; + int refs; - pid_t group_pid; + pid_t group_pid; - LIST_HEAD(, linux_emuldata) threads; /* head of list of linux threads */ + LIST_HEAD(, linux_emuldata) threads; /* head of list of linux threads */ }; The refs is a reference counter being used @@ -1860,8 +1860,8 @@ void * child_tidptr); counter, which is very fast, as presented by the following example: - pthread_mutex_lock(&mutex); -.... + pthread_mutex_lock(&mutex); +.... pthread_mutex_unlock(&mutex); 1:1 threading forces us to perform two syscalls for those mutex @@ -1908,7 +1908,7 @@ pthread_mutex_unlock(&mutex); FUTEX_WAKE_OP - + FUTEX_WAIT @@ -1952,7 +1952,7 @@ pthread_mutex_unlock(&mutex); This operation does the same as FUTEX_REQUEUE but it checks that val3 equals to val - first. + first. @@ -2017,13 +2017,13 @@ pthread_mutex_unlock(&mutex); And the structure waiting_proc is: - struct waiting_proc { + struct waiting_proc { - struct thread *wp_t; + struct thread *wp_t; - struct futex *wp_new_futex; + struct futex *wp_new_futex; - TAILQ_ENTRY(waiting_proc) wp_list; + TAILQ_ENTRY(waiting_proc) wp_list; }; @@ -2135,7 +2135,7 @@ pthread_mutex_unlock(&mutex); AT_FDCWD. So for example the openat syscall can be like this: - file descriptor 123 = /tmp/foo/, current working directory = /tmp/ + file descriptor 123 = /tmp/foo/, current working directory = /tmp/ openat(123, /tmp/bah\, flags, mode) /* opens /tmp/bah */ openat(123, bah\, flags, mode) /* opens /tmp/foo/bah */ @@ -2246,7 +2246,7 @@ openat(stdio, bah\, flags, mode) /* returns error because stdio is not a directo sysctl). For printing we have LMSG and ARGS macros. Those are used for altering a printable string for uniform debugging messages. - + diff --git a/en_US.ISO8859-1/articles/linux-users/Makefile b/en_US.ISO8859-1/articles/linux-users/Makefile index 82fc436564..4c0ac44d24 100644 --- a/en_US.ISO8859-1/articles/linux-users/Makefile +++ b/en_US.ISO8859-1/articles/linux-users/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: FreeBSD Quickstart for Linux Users diff --git a/en_US.ISO8859-1/articles/mailing-list-faq/Makefile b/en_US.ISO8859-1/articles/mailing-list-faq/Makefile index 09f7ccb2f7..a089bd63c7 100644 --- a/en_US.ISO8859-1/articles/mailing-list-faq/Makefile +++ b/en_US.ISO8859-1/articles/mailing-list-faq/Makefile @@ -12,7 +12,7 @@ INSTALL_ONLY_COMPRESSED?= WITH_ARTICLE_TOC?=YES -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # diff --git a/en_US.ISO8859-1/articles/mh/article.sgml b/en_US.ISO8859-1/articles/mh/article.sgml index 82e18373bc..06ce3754de 100644 --- a/en_US.ISO8859-1/articles/mh/article.sgml +++ b/en_US.ISO8859-1/articles/mh/article.sgml @@ -278,7 +278,7 @@ Incorporating new mail into inbox... 36+ 01/19 Stephen L. Lange Request...<<Please remove me as contact for pind 37 01/19 Matt Thomas Re: kern/950: Two PCI bridge chips fail (multipl - 38 01/19 Amancio Hasty Jr Re: FreeBSD and VAT<<>>> Bill Fenner said: > In + 38 01/19 Amancio Hasty Jr Re: FreeBSD and VAT<<>>> Bill Fenner said: > In &prompt.user; @@ -310,10 +310,10 @@ X-Authentication-Warning: whydos.lkg.dec.com: Host localhost didn't use HELO pro tocol To: hsu@clinet.fi Cc: hackers@FreeBSD.org -Subject: Re: kern/950: Two PCI bridge chips fail (multiple multiport ethernet - boards) +Subject: Re: kern/950: Two PCI bridge chips fail (multiple multiport ethernet + boards) In-Reply-To: Your message of "Fri, 19 Jan 1996 00:18:36 +0100." - <199601182318.AA11772@Sysiphos> + <199601182318.AA11772@Sysiphos> X-Mailer: exmh version 1.5omega 10/6/94 Date: Fri, 19 Jan 1996 17:56:40 +0000 From: Matt Thomas <matt@lkg.dec.com> @@ -332,16 +332,16 @@ which I am probably the guilty party). &prompt.user; scan last:10 - 26 01/16 maddy Re: Testing some stuff<<yeah, well, Trinity has + 26 01/16 maddy Re: Testing some stuff<<yeah, well, Trinity has 27 01/17 Automatic digest NET-HAPPENINGS Digest - 16 Jan 1996 to 17 Jan 19 - 28 01/17 Evans A Criswell Re: Hey dude<<>From matt@tempest.garply.com Tue + 28 01/17 Evans A Criswell Re: Hey dude<<>From matt@tempest.garply.com Tue 29 01/16 Karl Heuer need configure/make volunteers<<The FSF is looki 30 01/18 Paul Stephanouk Re: [alt.religion.scientology] Raw Meat (humor)< 31 01/18 Bill Lenherr Re: Linux NIS Solaris<<--- On Thu, 18 Jan 1996 1 34 01/19 John Fieber Re: Stuff for the email section?<<On Fri, 19 Jan 35 01/19 support@foo.garpl [garply.com #1138] parlor<<Hello. This is the Ne 37+ 01/19 Matt Thomas Re: kern/950: Two PCI bridge chips fail (multipl - 38 01/19 Amancio Hasty Jr Re: FreeBSD and VAT<<>>> Bill Fenner said: > In + 38 01/19 Amancio Hasty Jr Re: FreeBSD and VAT<<>>> Bill Fenner said: > In &prompt.user; @@ -508,7 +508,7 @@ which I am probably the guilty party). - + This allows you to do things like @@ -551,7 +551,7 @@ which I am probably the guilty party). necessary as in the following example - &prompt.user; pick -lbrace -to freebsd-hackers -and + &prompt.user; pick -lbrace -to freebsd-hackers -and -not -cc freebsd-questions -rbrace -and -subject pci @@ -618,7 +618,7 @@ which I am probably the guilty party). TOTAL= 199 messages in 13 folders. - + The refile command is what you use to move messages between folders. When you do something like refile 23 +netfuture message number 23 is moved @@ -799,13 +799,13 @@ X-Home-Page: http://www.FreeBSD.org/ original message. So that might be translated this way: - %<if {reply-to} the original message has a reply-to + %<if {reply-to} the original message has a reply-to then give that to formataddr, %? else {from} take the from address, %? else {sender} take the sender address, %? else {return-path} take the return-path from the original message, %> endif. - + As you can tell MH formatting can get rather involved. You can probably decipher what most of the other functions and variables mean. All of the diff --git a/en_US.ISO8859-1/articles/nanobsd/Makefile b/en_US.ISO8859-1/articles/nanobsd/Makefile index 4b9cf79584..1b3baa6fe3 100644 --- a/en_US.ISO8859-1/articles/nanobsd/Makefile +++ b/en_US.ISO8859-1/articles/nanobsd/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: Introduction to NanoBSD diff --git a/en_US.ISO8859-1/articles/new-users/article.sgml b/en_US.ISO8859-1/articles/new-users/article.sgml index 95045ea05d..1ca4b054f9 100644 --- a/en_US.ISO8859-1/articles/new-users/article.sgml +++ b/en_US.ISO8859-1/articles/new-users/article.sgml @@ -431,7 +431,7 @@ the long run the text editor vi is worth learning. There is an excellent tutorial on vi in /usr/src/contrib/nvi/docs/tutorial, if you - have the system sources installed. + have the system sources installed. Before you edit a file, you should probably back it up. Suppose you want to edit /etc/rc.conf. You diff --git a/en_US.ISO8859-1/articles/p4-primer/Makefile b/en_US.ISO8859-1/articles/p4-primer/Makefile index 9f80f4fa05..cb9bac7f12 100644 --- a/en_US.ISO8859-1/articles/p4-primer/Makefile +++ b/en_US.ISO8859-1/articles/p4-primer/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Perforce in FreeBSD Development article. diff --git a/en_US.ISO8859-1/articles/portbuild/article.sgml b/en_US.ISO8859-1/articles/portbuild/article.sgml index 85d102bc47..aee1650fa6 100644 --- a/en_US.ISO8859-1/articles/portbuild/article.sgml +++ b/en_US.ISO8859-1/articles/portbuild/article.sgml @@ -2670,7 +2670,7 @@ ln -s ../arch/archive/errorlogs arch(Only necessary for old codebase): Only after the first time a dopackages has been run for the - arch: add the arch to + arch: add the arch to /var/portbuild/scripts/dopackagestats. @@ -2908,7 +2908,7 @@ Use smartctl -X to abort test. after it finishes: # SMART Self-test log structure revision number 1 -# Num Test_Description Status Remaining +# Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 80% 15252 319286 diff --git a/en_US.ISO8859-1/articles/problem-reports/article.sgml b/en_US.ISO8859-1/articles/problem-reports/article.sgml index 70a6323b9e..e37649d56a 100644 --- a/en_US.ISO8859-1/articles/problem-reports/article.sgml +++ b/en_US.ISO8859-1/articles/problem-reports/article.sgml @@ -123,13 +123,13 @@ committer, or you might be asked to provide a patch to update the port; providing it upfront will greatly improve your chances that the port will get updated in a timely manner. - + If the port is maintained, PRs announcing new upstream releases are usually not very useful since they generate supplementary work for the committers, and the maintainer likely knows already there is a new version, they have probably worked with the developers on it, they are probably testing to see there is no regression, etc. - + In either case, following the process described in Porter's Handbook will yield the best results. (You might diff --git a/en_US.ISO8859-1/articles/rc-scripting/Makefile b/en_US.ISO8859-1/articles/rc-scripting/Makefile index 92886d6ba7..586196f69f 100644 --- a/en_US.ISO8859-1/articles/rc-scripting/Makefile +++ b/en_US.ISO8859-1/articles/rc-scripting/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: Practical rc.d scripting in BSD diff --git a/en_US.ISO8859-1/articles/rc-scripting/article.sgml b/en_US.ISO8859-1/articles/rc-scripting/article.sgml index d763a65c2a..944028dffd 100644 --- a/en_US.ISO8859-1/articles/rc-scripting/article.sgml +++ b/en_US.ISO8859-1/articles/rc-scripting/article.sgml @@ -1232,7 +1232,7 @@ run_rc_command "$1" Fortunately, &man.rc.subr.8; allows for passing any number of arguments to script's methods (within the system limits). Due to that, the changes in the script itself can be minimal. - + How can &man.rc.subr.8; gain access to the extra command-line arguments. Should it just grab them directly? Not by any means. Firstly, an &man.sh.1; diff --git a/en_US.ISO8859-1/articles/relaydelay/article.sgml b/en_US.ISO8859-1/articles/relaydelay/article.sgml index a0331570af..144e27ba2b 100644 --- a/en_US.ISO8859-1/articles/relaydelay/article.sgml +++ b/en_US.ISO8859-1/articles/relaydelay/article.sgml @@ -68,7 +68,7 @@ set. The current version of perl may need to be removed first; errors will be reported by the install process if this is necessary. - + This will require all ports which require perl to be rebuilt and reinstalled; diff --git a/en_US.ISO8859-1/articles/releng-packages/Makefile b/en_US.ISO8859-1/articles/releng-packages/Makefile index d47d0b2e9a..78b5446bc3 100644 --- a/en_US.ISO8859-1/articles/releng-packages/Makefile +++ b/en_US.ISO8859-1/articles/releng-packages/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: FreeBSD Release Engineering of Third Party Software Packages diff --git a/en_US.ISO8859-1/articles/releng/Makefile b/en_US.ISO8859-1/articles/releng/Makefile index 9cb2ff4114..59137dbad0 100644 --- a/en_US.ISO8859-1/articles/releng/Makefile +++ b/en_US.ISO8859-1/articles/releng/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: FreeBSD Release Engineering diff --git a/en_US.ISO8859-1/articles/releng/article.sgml b/en_US.ISO8859-1/articles/releng/article.sgml index f1d842816d..09392d38d6 100644 --- a/en_US.ISO8859-1/articles/releng/article.sgml +++ b/en_US.ISO8859-1/articles/releng/article.sgml @@ -788,11 +788,11 @@ applicable. &man.sysinstall.8; and &man.release.7; must be updated to include installation instructions. The relevant code is contained in src/release and src/usr.sbin/sysinstall. - Specifically, the file src/release/Makefile, and + Specifically, the file src/release/Makefile, and dist.c, dist.h, - menus.c, install.c, and + menus.c, install.c, and Makefile will need to be updated under - src/usr.sbin/sysinstall. Optionally, you may choose + src/usr.sbin/sysinstall. Optionally, you may choose to update sysinstall.8. diff --git a/en_US.ISO8859-1/articles/remote-install/Makefile b/en_US.ISO8859-1/articles/remote-install/Makefile index d7db2cc2e0..388906f144 100644 --- a/en_US.ISO8859-1/articles/remote-install/Makefile +++ b/en_US.ISO8859-1/articles/remote-install/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # diff --git a/en_US.ISO8859-1/articles/serial-uart/article.sgml b/en_US.ISO8859-1/articles/serial-uart/article.sgml index 37f3f5deb6..0485c37050 100644 --- a/en_US.ISO8859-1/articles/serial-uart/article.sgml +++ b/en_US.ISO8859-1/articles/serial-uart/article.sgml @@ -8,18 +8,18 @@
Serial and UART Tutorial - + Frank Durda - +
uhclem@FreeBSD.org
 - + &tm-attrib.freebsd; &tm-attrib.microsoft; @@ -34,7 +34,7 @@ This article talks about using serial hardware with FreeBSD. - + The UART: What it is and how it works @@ -47,11 +47,11 @@ transmits the individual bits in a sequential fashion. At the destination, a second UART re-assembles the bits into complete bytes. - + Serial transmission is commonly used with modems and for non-networked communication between computers, terminals and other devices. - + There are two primary forms of serial transmission: Synchronous and Asynchronous. Depending on the modes that are supported by the hardware, the name of the communication @@ -59,13 +59,13 @@ supports Asynchronous communications, and a S if it supports Synchronous communications. Both forms are described below. - + Some common acronyms are: - +
UART Universal Asynchronous Receiver/Transmitter
- +
USART Universal Synchronous-Asynchronous Receiver/Transmitter @@ -73,7 +73,7 @@ Synchronous Serial Transmission - + Synchronous serial transmission requires that the sender and receiver share a clock with one another, or that the sender provide a strobe or other timing signal so that the @@ -87,7 +87,7 @@ synchronous communication can be more costly if extra wiring and circuits are required to share a clock signal between the sender and receiver. - + A form of Synchronous transmission is used with printers and fixed disk devices in that the data is sent on one set of wires while a clock or strobe is sent on a different @@ -96,7 +96,7 @@ send an entire word of data for each clock or strobe signal by using a separate wire for each bit of the word. In the PC industry, these are known as Parallel devices. - + The standard serial communications hardware in the PC does not support Synchronous operations. This mode is described here for comparison purposes only. @@ -104,14 +104,14 @@ Asynchronous Serial Transmission - + Asynchronous transmission allows data to be transmitted without the sender having to send a clock signal to the receiver. Instead, the sender and receiver must agree on timing parameters in advance and special bits are added to each word which are used to synchronize the sending and receiving units. - + When a word is given to the UART for Asynchronous transmissions, a bit called the "Start Bit" is added to the beginning of each word that is to be transmitted. The Start @@ -123,7 +123,7 @@ the remaining bits in the word. (This requirement was set in the days of mechanical teleprinters and is easily met by modern electronic equipment.) - + After the Start Bit, the individual bits of the word of data are sent, with the Least Significant Bit (LSB) being sent first. Each bit in the transmission is transmitted for @@ -137,18 +137,18 @@ 0 after one second has passed, then it will wait two seconds and then examine the value of the next bit, and so on. - + The sender does not know when the receiver has looked at the value of the bit. The sender only knows when the clock says to begin transmitting the next bit of the word. - + When the entire data word has been sent, the transmitter may add a Parity Bit that the transmitter generates. The Parity Bit may be used by the receiver to perform simple error checking. Then at least one Stop Bit is sent by the transmitter. - + When the receiver has received all of the bits in the data word, it may check for the Parity Bits (both sender and receiver must agree on whether a Parity Bit is to be used), @@ -159,16 +159,16 @@ usual cause of a Framing Error is that the sender and receiver clocks were not running at the same speed, or that the signal was interrupted. - + Regardless of whether the data was received correctly or not, the UART automatically discards the Start, Parity and Stop bits. If the sender and receiver are configured identically, these bits are not passed to the host. - + If another word is ready for transmission, the Start Bit for the new word can be sent as soon as the Stop Bit for the previous word has been sent. - + Because asynchronous data is self synchronizing, if there is no data to transmit, the transmission line can be idle. @@ -176,7 +176,7 @@ Other UART Functions - + In addition to the basic job of converting data from parallel to serial for transmission and from serial to parallel on reception, a UART will usually provide @@ -194,23 +194,23 @@ The RS232-C and V.24 Standards - + In most computer systems, the UART is connected to circuitry that generates signals that comply with the EIA RS232-C specification. There is also a CCITT standard named V.24 that mirrors the specifications included in RS232-C. - + RS232-C Bit Assignments (Marks and Spaces) - + In RS232-C, a value of 1 is called a Mark and a value of 0 is called a Space. When a communication line is idle, the line is said to be Marking, or transmitting continuous 1 values. - + The Start bit always has a value of 0 (a Space). The Stop Bit always has a value of 1 (a Mark). This means that @@ -220,12 +220,12 @@ sender and receiver can resynchronize their clocks regardless of the content of the data bits that are being transmitted. - + The idle time between Stop and Start bits does not have to be an exact multiple (including zero) of the bit rate of the communication link, but most UARTs are designed this way for simplicity. - + In RS232-C, the "Marking" signal (a 1) is represented by a voltage between -2 VDC and -12 VDC, and a "Spacing" signal (a @@ -238,24 +238,24 @@ acceptable to a RS232-C receiver, provided that the cable lengths are short. - + RS232-C Break Signal - + RS232-C also specifies a signal called a Break, which is caused by sending continuous Spacing values (no Start or Stop bits). When there is no electricity present on the data circuit, the line is considered to be sending Break. - + The Break signal must be of a duration longer than the time it takes to send a complete byte plus Start, Stop and Parity bits. Most UARTs can distinguish between a Framing Error and a Break, but if the UART cannot do this, the Framing Error detection can be used to identify Breaks. - + In the days of teleprinters, when numerous printers around the country were wired in series (such as news services), any unit could cause a Break @@ -263,7 +263,7 @@ current flowed. This was used to allow a location with urgent news to interrupt some other location that was currently sending information. - + In modern systems there are two types of Break signals. If the Break is longer than 1.6 seconds, it is considered a "Modem Break", and some modems can be @@ -275,7 +275,7 @@ is used as an Attention or Interrupt signal and sometimes is accepted as a substitute for the ASCII CONTROL-C character. - + Marks and Spaces are also equivalent to Holes and No Holes in paper tape systems. @@ -288,10 +288,10 @@ a special command from the host processor. - + RS232-C DTE and DCE Devices - + The RS232-C specification defines two types of equipment: the Data Terminal Equipment (DTE) and the Data Carrier Equipment (DCE). Usually, the DTE device is the @@ -301,7 +301,7 @@ is connected to that modem is a DTE device. The DCE device receives signals on the pins that the DTE device transmits on, and vice versa. - + When two devices that are both DTE or both DCE must be connected together without a modem or a similar media translator between them, a NULL modem must be used. The @@ -311,34 +311,34 @@ are performed on all of the control signals so that each device will see what it thinks are DCE (or DTE) signals from the other device. - + The number of signals generated by the DTE and DCE devices are not symmetrical. The DTE device generates fewer signals for the DCE device than the DTE device receives from the DCE. - + RS232-C Pin Assignments - + The EIA RS232-C specification (and the ITU equivalent, V.24) calls for a twenty-five pin connector (usually a DB25) and defines the purpose of most of the pins in that connector. - + In the IBM Personal Computer and similar systems, a subset of RS232-C signals are provided via nine pin connectors (DB9). The signals that are not included on the PC connector deal mainly with synchronous operation, and this transmission mode is not supported by the UART that IBM selected for use in the IBM PC. - + Depending on the computer manufacturer, a DB25, a DB9, or both types of connector may be used for RS232-C communications. (The IBM PC also uses a DB25 connector for the parallel printer interface which causes some confusion.) - + Below is a table of the RS232-C signal assignments in the DB25 and DB9 connectors. @@ -353,7 +353,7 @@ Description - + 1 @@ -364,7 +364,7 @@ - Frame/Protective Ground - + 2 3 @@ -374,7 +374,7 @@ DTE Transmit Data - + 3 2 @@ -384,7 +384,7 @@ DCE Receive Data - + 4 7 @@ -394,7 +394,7 @@ DTE Request to Send - + 5 8 @@ -404,7 +404,7 @@ DCE Clear to Send - + 6 6 @@ -414,7 +414,7 @@ DCE Data Set Ready - + 7 5 @@ -424,7 +424,7 @@ - Signal Ground - + 8 1 @@ -434,7 +434,7 @@ DCE Data Carrier Detect - + 9 - @@ -444,7 +444,7 @@ - Reserved for Test - + 10 - @@ -454,7 +454,7 @@ - Reserved for Test - + 11 - @@ -464,7 +464,7 @@ - Reserved for Test - + 12 - @@ -474,7 +474,7 @@ DCE Sec. Recv. Line Signal Detector - + 13 - @@ -484,7 +484,7 @@ DCE Secondary Clear to Send - + 14 - @@ -494,7 +494,7 @@ DTE Secondary Transmit Data - + 15 - @@ -504,7 +504,7 @@ DCE Trans. Sig. Element Timing - + 16 - @@ -514,7 +514,7 @@ DCE Secondary Received Data - + 17 - @@ -524,7 +524,7 @@ DCE Receiver Signal Element Timing - + 18 - @@ -534,7 +534,7 @@ DTE Local Loopback - + 19 - @@ -544,7 +544,7 @@ DTE Secondary Request to Send - + 20 4 @@ -554,7 +554,7 @@ DTE Data Terminal Ready - + 21 - @@ -564,7 +564,7 @@ DTE Remote Digital Loopback - + 22 9 @@ -574,7 +574,7 @@ DCE Ring Indicator - + 23 - @@ -584,7 +584,7 @@ DTE Data Signal Rate Selector - + 24 - @@ -594,7 +594,7 @@ DTE Trans. Sig. Element Timing - + 25 - @@ -612,12 +612,12 @@ Bits, Baud and Symbols - + Baud is a measurement of transmission speed in asynchronous communication. Because of advances in modem communication technology, this term is frequently misused when describing the data rates in newer devices. - + Traditionally, a Baud Rate represents the number of bits that are actually being sent over the media, not the amount of data that is actually moved from one DTE device to the @@ -629,12 +629,12 @@ per second from one place to another can normally only move 30 7-bit words if Parity is used and one Start and Stop bit are present. - + If 8-bit data words are used and Parity bits are also used, the data rate falls to 27.27 words per second, because it now takes 11 bits to send the eight-bit words, and the modem still only sends 300 bits per second. - + The formula for converting bytes per second into a baud rate and vice versa was simple until error-correcting modems came along. These modems receive the serial stream of bits @@ -650,7 +650,7 @@ bits to the words, converts them to a serial format and then sends them to the receiving UART in the remote computer, who then strips the Start, Stop and Parity bits. - + The reason all these extra conversions are done is so that the two modems can perform error correction, which means that the receiving modem is able to ask the sending @@ -658,7 +658,7 @@ the correct checksum. This checking is handled by the modems, and the DTE devices are usually unaware that the process is occurring. - + By striping the Start, Stop and Parity bits, the additional bits of data that the two modems must share between themselves to perform error-correction are mostly @@ -669,14 +669,14 @@ will be able to add 30 bits of its own information that the receiving modem can use to do error-correction without impacting the transmission speed of the real data. - + The use of the term Baud is further confused by modems that perform compression. A single 8-bit word passed over the telephone line might represent a dozen words that were transmitted to the sending modem. The receiving modem will expand the data back to its original content and pass that data to the receiving DTE. - + Modern modems also include buffers that allow the rate that bits move across the phone line (DCE to DCE) to be a different speed than the speed that the bits move between @@ -684,7 +684,7 @@ the speed between the DTE and DCE is higher than the DCE to DCE speed because of the use of compression by the modems. - + Because the number of bits needed to describe a byte varied during the trip between the two machines plus the differing bits-per-seconds speeds that are used present on @@ -697,7 +697,7 @@ connection is made between two systems with a wired connection, or if a modem is in use that is not performing error-correction or compression. - + Modern high speed modems (2400, 9600, 14,400, and 19,200bps) in reality still operate at or below 2400 baud, or more accurately, 2400 Symbols per second. High speed @@ -712,17 +712,17 @@ The IBM Personal Computer UART - + Starting with the original IBM Personal Computer, IBM selected the National Semiconductor INS8250 UART for use in the IBM PC Parallel/Serial Adapter. Subsequent generations of compatible computers from IBM and other vendors continued to use the INS8250 or improved versions of the National Semiconductor UART family. - + National Semiconductor UART Family Tree - + There have been several versions and subsequent generations of the INS8250 UART. Each major version is described below. @@ -738,7 +738,7 @@ \ \ \-> NS16550 -> NS16550A -> PC16550D - + INS8250 @@ -748,7 +748,7 @@ IBM PC/XT. The original name for this part was the INS8250 ACE (Asynchronous Communications Element) and it is made from NMOS technology. - + The 8250 uses eight I/O ports and has a one-byte send and a one-byte receive buffer. This original UART has several race conditions and other @@ -759,20 +759,20 @@ original IBM PC or IBM PC/XT. - + INS8250-B - + This is the slower speed of the INS8250 made from NMOS technology. It contains the same problems as the original INS8250. - + INS8250A - + An improved version of the INS8250 using XMOS technology with various functional flaws @@ -784,20 +784,20 @@ INS8250B. - + INS82C50A - + This is a CMOS version (low power consumption) of the INS8250A and has similar functional characteristics. - + NS16450 - + Same as NS8250A with improvements so it can be used with faster CPU bus designs. IBM used this @@ -805,29 +805,29 @@ longer rely on the bugs in the INS8250. - + NS16C450 - + This is a CMOS version (low power consumption) of the NS16450. - + NS16550 - + Same as NS16450 with a 16-byte send and receive buffer but the buffer design was flawed and could not be reliably be used. - + NS16550A - + Same as NS16550 with the buffer flaws corrected. The 16550A and its successors have become @@ -837,19 +837,19 @@ interrupt response times. - + NS16C552 - + This component consists of two NS16C550A CMOS UARTs in a single package. - + PC16550D - + Same as NS16550A with subtle flaws corrected. This is revision D of the 16550 family @@ -859,10 +859,10 @@ - + The NS16550AF and the PC16550D are the same thing - + National reorganized their part numbering system a few years ago, and the NS16550AFN no longer exists by that name. (If you have a NS16550AFN, look at the date code on @@ -871,12 +871,12 @@ year, and the last two digits are the week in that year when the part was packaged. If you have a NS16550AFN, it is probably a few years old.) - + The new numbers are like PC16550DV, with minor differences in the suffix letters depending on the package material and its shape. (A description of the numbering system can be found below.) - + It is important to understand that in some stores, you may pay $15(US) for a NS16550AFN made in 1990 and in the next bin are the new PC16550DN parts with minor fixes @@ -885,27 +885,27 @@ six months and it costs half (as low as $5(US) in volume) as much as the NS16550AFN because they are readily available. - + As the supply of NS16550AFN chips continues to shrink, the price will probably continue to increase until more people discover and accept that the PC16550DN really has the same function as the old part number. - + National Semiconductor Part Numbering System - + The older NSnnnnnrqp part numbers are now of the format PCnnnnnrgp. - + The r is the revision field. The current revision of the 16550 from National Semiconductor is D. - + The p is the package-type field. The types are: - + @@ -914,7 +914,7 @@ QFP (quad flat pack) L lead type - + "N" DIP @@ -930,7 +930,7 @@ - + The g is the product grade field. If an I precedes the package-type letter, it indicates an @@ -938,7 +938,7 @@ specs than a standard part but not as high as Military Specification (Milspec) component. This is an optional field. - + So what we used to call a NS16550AFN (DIP Package) is now called a PC16550DN or PC16550DIN. @@ -946,7 +946,7 @@ Other Vendors and Similar UARTs - + Over the years, the 8250, 8250A, 16450 and 16550 have been licensed or copied by other chip vendors. In the case of the 8250, 8250A and 16450, the exact circuit (the @@ -954,7 +954,7 @@ including Western Digital and Intel. Other vendors reverse-engineered the part or produced emulations that had similar behavior. - + In internal modems, the modem designer will frequently emulate the 8250A/16450 with the modem microprocessor, and the emulated UART will frequently have a hidden buffer @@ -965,18 +965,18 @@ 8250A or 16450, and may not make effective use of the extra buffering present in the emulated UART unless special drivers are used. - + Some modem makers are driven by market forces to abandon a design that has hundreds of bytes of buffer and instead use a 16550A UART so that the product will compare favorably in market comparisons even though the effective performance may be lowered by this action. - + A common misconception is that all parts with 16550A written on them are identical in performance. There are differences, and in some cases, outright flaws in most of these 16550A clones. - + When the NS16550 was developed, the National Semiconductor obtained several patents on the design and they also limited licensing, making it harder for other @@ -988,7 +988,7 @@ computer and modem makers want to buy but are sometimes unwilling to pay the price required to get the genuine part. - + Some of the differences in the clone 16550A parts are unimportant, while others can prevent the device from being used at all with a given operating system or driver. These @@ -1002,7 +1002,7 @@ different operating system is used, problems could appear due to subtle differences between the clones and genuine components. - + National Semiconductor has made available a program named COMTEST that performs compatibility tests independent of any OS drivers. It @@ -1011,7 +1011,7 @@ competition, so the program will report major as well as extremely subtle differences in behavior in the part being tested. - + In a series of tests performed by the author of this document in 1994, components made by National Semiconductor, TI, StarTech, and CMD as well as megacells and emulations @@ -1020,7 +1020,7 @@ below. Because these tests were performed in 1994, they may not reflect the current performance of the given product from a vendor. - + It should be noted that COMTEST normally aborts when an excessive number or certain types of problems have been detected. As part of this testing, COMTEST was modified so @@ -1036,51 +1036,51 @@ Errors (aka "differences" reported) - + National (PC16550DV) 0 - + National (NS16550AFN) 0 - + National (NS16C552V) 0 - + TI (TL16550AFN) 3 - + CMD (16C550PE) 19 - + StarTech (ST16C550J) 23 - + Rockwell Reference modem with internal 16550 or an emulation (RC144DPi/C3000-25) 117 - + Sierra Modem with an internal 16550 @@ -1090,7 +1090,7 @@ - + To date, the author of this document has not found any non-National parts that report zero differences using the @@ -1105,7 +1105,7 @@ bugs in the A, B and C revisions of the parts, so this bias in COMTEST must be taken into account. - + It is important to understand that a simple count of differences from COMTEST does not reveal a lot about what differences are important and which are not. For example, @@ -1119,7 +1119,7 @@ particularly those with error-correction and compression capabilities. This means that the differences related to five- and six-bit character modes can be discounted. - + Many of the differences COMTEST reports have to do with timing. In many of the clone designs, when the host reads from one port, the status bits in some other port may not @@ -1132,12 +1132,12 @@ faster or slower than the reference part (that would probably never affect the operation of a properly written driver) could have dozens of differences reported. - + COMTEST can be used as a screening tool to alert the administrator to the presence of potentially incompatible components that might cause problems or have to be handled as a special case. - + If you run COMTEST on a 16550 that is in a modem or a modem is attached to the serial port, you need to first issue a ATE0&W command to the modem so that the modem @@ -1150,7 +1150,7 @@ 8250/16450/16550 Registers - + The 8250/16450/16550 UART occupies eight contiguous I/O port addresses. In the IBM PC, there are two defined locations for these eight ports and they are known @@ -1159,13 +1159,13 @@ and COM4, but these extra COM ports conflict with other hardware on some systems. The most common conflict is with video adapters that provide IBM 8514 emulation. - + COM1 is located from 0x3f8 to 0x3ff and normally uses IRQ 4. COM2 is located from 0x2f8 to 0x2ff and normally uses IRQ 3. COM3 is located from 0x3e8 to 0x3ef and has no standardized IRQ. COM4 is located from 0x2e8 to 0x2ef and has no standardized IRQ. - + A description of the I/O ports of the 8250/16450/16550 UART is provided below. @@ -1178,7 +1178,7 @@ Description - + +0x00 @@ -1188,7 +1188,7 @@ treated as data words and will be transmitted by the UART. - + +0x00 read (DLAB==0) @@ -1197,7 +1197,7 @@ accessed by the host by reading this port. - + +0x00 write/read (DLAB==1) @@ -1208,7 +1208,7 @@ register holds bits 0 thru 7 of the divisor. - + +0x01 write/read (DLAB==1) @@ -1219,7 +1219,7 @@ register holds bits 8 thru 15 of the divisor. - + +0x01 write/read (DLAB==0) @@ -1244,27 +1244,27 @@ to determine the true cause(s) of the interrupt. - + Bit 7 Reserved, always 0. - + Bit 6 Reserved, always 0. - + Bit 5 Reserved, always 0. - + Bit 4 Reserved, always 0. - + Bit 3 Enable Modem Status Interrupt (EDSSI). Setting @@ -1272,7 +1272,7 @@ interrupt when a change occurs on one or more of the status lines. - + Bit 2 Enable Receiver Line Status Interrupt (ELSI) @@ -1280,7 +1280,7 @@ an interrupt when the an error (or a BREAK signal) has been detected in the incoming data. - + Bit 1 Enable Transmitter Holding Register Empty @@ -1289,7 +1289,7 @@ for one or more additional characters that are to be transmitted. - + Bit 0 Enable Received Data Available Interrupt @@ -1303,7 +1303,7 @@ - + +0x02 write @@ -1314,7 +1314,7 @@ - + FIFO Control Register (FCR) @@ -1326,7 +1326,7 @@ Bit 7 Receiver Trigger Bit #1 - + Bit 6 Receiver Trigger Bit @@ -1334,48 +1334,48 @@ point the receiver is to generate an interrupt when the FIFO is active. - + 7 6 How many words are received before an interrupt is generated - + 0 0 1 - + 0 1 4 - + 1 0 8 - + 1 1 14 - + Bit 5 Reserved, always 0. - + Bit 4 Reserved, always 0. - + Bit 3 DMA Mode Select. If Bit 0 is @@ -1383,7 +1383,7 @@ the operation of the -RXRDY and -TXRDY signals from Mode 0 to Mode 1. - + Bit 2 Transmit FIFO Reset. When a @@ -1392,7 +1392,7 @@ will be sent intact. This function is useful in aborting transfers. - + Bit 1 Receiver FIFO Reset. When a @@ -1413,7 +1413,7 @@ - + +0x02 read @@ -1438,34 +1438,34 @@ FIFOs enabled. On the 8250/16450 UART, this bit is zero. - + Bit 6 FIFOs enabled. On the 8250/16450 UART, this bit is zero. - + Bit 5 Reserved, always 0. - + Bit 4 Reserved, always 0. - + Bit 3 Interrupt ID Bit #2. On the 8250/16450 UART, this bit is zero. - + Bit 2 Interrupt ID Bit #1 - + Bit 1 Interrupt ID Bit #0.These @@ -1481,7 +1481,7 @@ interrupts will be generated. (This is a limitation of the PC architecture.) - + 2 1 @@ -1489,7 +1489,7 @@ Priority Description - + 0 1 @@ -1498,7 +1498,7 @@ Received Error (OE, PE, BI, or FE) - + 0 1 @@ -1506,7 +1506,7 @@ Second Received Data Available - + 1 1 @@ -1515,7 +1515,7 @@ Trigger level identification (Stale data in receive buffer) - + 0 0 @@ -1524,7 +1524,7 @@ Transmitter has room for more words (THRE) - + 0 0 @@ -1533,7 +1533,7 @@ Modem Status Change (-CTS, -DSR, -RI, or -DCD) - + Bit 0 Interrupt Pending Bit. If this @@ -1543,7 +1543,7 @@ - + +0x03 write/read @@ -1562,7 +1562,7 @@ Line Control Register (LCR) - + Bit 7 Divisor Latch Access Bit @@ -1574,7 +1574,7 @@ the Divisor Registers, and clearing DLAB should be done with interrupts disabled. - + Bit 6 Set Break. When set to "1", @@ -1583,14 +1583,14 @@ overrides any bits of characters that are being transmitted. - + Bit 5 Stick Parity. When parity is enabled, setting this bit causes parity to always be "1" or "0", based on the value of Bit 4. - + Bit 4 Even Parity Select (EPS). When @@ -1598,7 +1598,7 @@ causes even parity to be transmitted and expected. Otherwise, odd parity is used. - + Bit 3 Parity Enable (PEN). When set @@ -1607,7 +1607,7 @@ also expect parity to be present in the received data. - + Bit 2 Number of Stop Bits (STB). If @@ -1617,53 +1617,53 @@ transmitted and expected. When this bit is set to "0", one Stop Bit is used on each data word. - + Bit 1 Word Length Select Bit #1 (WLSB1) - + Bit 0 Word Length Select Bit #0 (WLSB0) - + Together these bits specify the number of bits in each data word. - + 1 0 Word Length - + 0 0 5 Data Bits - + 0 1 6 Data Bits - + 1 0 7 Data Bits - + 1 1 @@ -1673,7 +1673,7 @@ - + +0x04 write/read @@ -1687,22 +1687,22 @@ Modem Control Register (MCR) - + Bit 7 Reserved, always 0. - + Bit 6 Reserved, always 0. - + Bit 5 Reserved, always 0. - + Bit 4 Loop-Back Enable. When set to "1", the UART @@ -1714,7 +1714,7 @@ connected to RI, and OUT 2 is connected to DCD. - + Bit 3 OUT 2. An auxiliary output that the host @@ -1723,21 +1723,21 @@ tri-state (disable) the interrupt signal from the 8250/16450/16550 UART. - + Bit 2 OUT 1. An auxiliary output that the host processor may set high or low. This output is not used on the IBM PC serial adapter. - + Bit 1 Request to Send (RTS). When set to "1", the output of the UART -RTS line is Low (Active). - + Bit 0 Data Terminal Ready (DTR). When set to "1", @@ -1747,7 +1747,7 @@ - + +0x05 write/read @@ -1761,7 +1761,7 @@ Line Status Register (LSR) - + Bit 7 Error in Receiver FIFO. On the 8250/16450 @@ -1769,7 +1769,7 @@ any of the bytes in the FIFO have one or more of the following error conditions: PE, FE, or BI. - + Bit 6 Transmitter Empty (TEMT). When set to "1", @@ -1777,7 +1777,7 @@ or the transmit shift register. The transmitter is completely idle. - + Bit 5 Transmitter Holding Register Empty (THRE). @@ -1786,13 +1786,13 @@ transmit. The transmitter may still be transmitting when this bit is set to "1". - + Bit 4 Break Interrupt (BI). The receiver has detected a Break signal. - + Bit 3 Framing Error (FE). A Start Bit was detected @@ -1800,13 +1800,13 @@ time. The received word is probably garbled. - + Bit 2 Parity Error (PE). The parity bit was incorrect for the word received. - + Bit 1 Overrun Error (OE). A new word was received @@ -1816,7 +1816,7 @@ holding register is discarded and the newly- arrived word is put in the holding register. - + Bit 0 Data Ready (DR) One or more words are in the @@ -1828,7 +1828,7 @@ - + +0x06 write/read @@ -1842,31 +1842,31 @@ Modem Status Register (MSR) - + Bit 7 Data Carrier Detect (DCD). Reflects the state of the DCD line on the UART. - + Bit 6 Ring Indicator (RI). Reflects the state of the RI line on the UART. - + Bit 5 Data Set Ready (DSR). Reflects the state of the DSR line on the UART. - + Bit 4 Clear To Send (CTS). Reflects the state of the CTS line on the UART. - + Bit 3 Delta Data Carrier Detect (DDCD). Set to "1" @@ -1874,7 +1874,7 @@ time since the last time the MSR was read by the host. - + Bit 2 Trailing Edge Ring Indicator (TERI). Set to @@ -1882,7 +1882,7 @@ since the last time the MSR was read by the host. - + Bit 1 Delta Data Set Ready (DDSR). Set to "1" if the @@ -1890,7 +1890,7 @@ since the last time the MSR was read by the host. - + Bit 0 Delta Clear To Send (DCTS). Set to "1" if the @@ -1901,7 +1901,7 @@ - + +0x07 write/read @@ -1917,7 +1917,7 @@ Beyond the 16550A UART - + Although National Semiconductor has not offered any components compatible with the 16550 that provide additional features, various other vendors have. Some of these @@ -1926,7 +1926,7 @@ have to be provided by the chip vendor since most of the popular operating systems do not support features beyond those provided by the 16550. - + ST16650 @@ -1937,20 +1937,20 @@ enabled. Made by StarTech. - + TIL16660 - + By default this part behaves similar to the NS16550A, but an extended 64-byte send and receive buffer can be optionally enabled. Made by Texas Instruments. - + Hayes ESP - + This proprietary plug-in card contains a 2048-byte send and receive buffer, and supports data rates to @@ -1958,7 +1958,7 @@ - + In addition to these dumb UARTs, many vendors produce intelligent serial communication boards. This type of design usually provides a microprocessor that interfaces with @@ -1971,28 +1971,28 @@ performance characteristics. - + Configuring the <devicename>sio</devicename> driver - + The sio driver provides support for NS8250-, NS16450-, NS16550 and NS16550A-based EIA RS-232C (CCITT V.24) communications interfaces. Several multiport cards are supported as well. See the &man.sio.4; manual page for detailed technical documentation. - + Digi International (DigiBoard) PC/8 - + Contributed by &a.awebster;. 26 August 1995. - + Here is a config snippet from a machine with a Digi International PC/8 with 16550. It has 8 modems connected to these 8 lines, and they work just great. Do not forget to add options COM_MULTIPORT or it will not work very well! - + device sio4 at isa? port 0x100 flags 0xb05 device sio5 at isa? port 0x108 flags 0xb05 device sio6 at isa? port 0x110 flags 0xb05 @@ -2001,7 +2001,7 @@ device sio8 at isa? port 0x120 flags 0xb05 device sio9 at isa? port 0x128 flags 0xb05 device sio10 at isa? port 0x130 flags 0xb05 device sio11 at isa? port 0x138 flags 0xb05 irq 9 - + The trick in setting this up is that the MSB of the flags represent the last SIO port, in this case 11 so flags are 0xb05. @@ -2009,14 +2009,14 @@ device sio11 at isa? port 0x138 flags 0xb05 irq 9 Boca 16 - + Contributed by &a.whiteside;. 26 August 1995. - + The procedures to make a Boca 16 port board with FreeBSD are pretty straightforward, but you will need a couple things to make it work: - + You either need the kernel sources installed so you @@ -2026,21 +2026,21 @@ device sio11 at isa? port 0x138 flags 0xb05 irq 9 multiport support enabled and you will need to add a device entry for each port anyways. - + Two, you will need to know the interrupt and IO setting for your Boca Board so you can set these options properly in the kernel. - + One important note — the actual UART chips for the Boca 16 are in the connector box, not on the internal board itself. So if you have it unplugged, probes of those ports will fail. I have never tested booting with the box unplugged and plugging it back in, and I suggest you do not either. - + If you do not already have a custom kernel configuration file set up, refer to Kernel @@ -2048,16 +2048,16 @@ device sio11 at isa? port 0x138 flags 0xb05 irq 9 general procedures. The following are the specifics for the Boca 16 board and assume you are using the kernel name MYKERNEL and editing with vi. - + - Add the line - + Add the line + options COM_MULTIPORT to the config file. - + Where the current device sion lines are, you @@ -2092,7 +2092,7 @@ device sio16 at isa? port 0x178 flags 0x1005 irq 3 1C indicates the minor number of the master port. Do not change the 05 setting. - + Save and complete the kernel configuration, recompile, install and reboot. Presuming you have @@ -2101,7 +2101,7 @@ device sio16 at isa? port 0x178 flags 0x1005 irq 3 should indicate the successful probe of the Boca ports as follows: (obviously the sio numbers, IO and IRQ could be different) - + sio1 at 0x100-0x107 flags 0x1005 on isa sio1: type 16550A (multiport) sio2 at 0x108-0x10f flags 0x1005 on isa @@ -2140,7 +2140,7 @@ sio16: type 16550A (multiport master) &prompt.root; dmesg | more will show you the boot messages. - + Next, appropriate entries in /dev for the devices must be made @@ -2148,27 +2148,27 @@ sio16: type 16550A (multiport master) script. This step can be omitted if you are running FreeBSD 5.X with a kernel that has &man.devfs.5; support compiled in. - + If you do need to create the /dev entries, run the following as root: - + &prompt.root; cd /dev &prompt.root; ./MAKEDEV tty1 &prompt.root; ./MAKEDEV cua1 (everything in between) &prompt.root; ./MAKEDEV ttyg &prompt.root; ./MAKEDEV cuag - + If you do not want or need call-out devices for some reason, you can dispense with making the cua* devices. - + If you want a quick and sloppy way to make sure the devices are working, you can simply plug a modem into each port and (as root) - + &prompt.root; echo at > ttyd* for each device you have made. You should see the RX lights flash for each @@ -2183,11 +2183,11 @@ sio16: type 16550A (multiport master) Contributed by Helge Oldach hmo@sep.hamburg.com, September 1999 - + Ever wondered about FreeBSD support for your 20$ multi-I/O card with two (or more) COM ports, sharing IRQs? Here is how: - + Usually the only option to support these kind of boards is to use a distinct IRQ for each port. For example, if your CPU board has an on-board COM1 @@ -2202,7 +2202,7 @@ sio16: type 16550A (multiport master) basically possible to run both extension board ports using a single IRQ with the COM_MULTIPORT configuration described in the previous sections. - + Such cheap I/O boards commonly have a 4 by 3 jumper matrix for the COM ports, similar to the following: @@ -2296,13 +2296,13 @@ sio2: type 16550A (multiport master) likely there is something wrong with your wiring. - + Configuring the <devicename>cy</devicename> driver - + Contributed by Alex Nash. 6 June 1996. - + The Cyclades multiport cards are based on the cy driver instead of the usual sio driver used by other multiport @@ -2313,39 +2313,39 @@ sio2: type 16550A (multiport master) Add the cy device to your kernel configuration (note that your irq and iomem settings may differ). - + device cy0 at isa? irq 10 iomem 0xd4000 iosiz 0x2000 - + Rebuild and install the new kernel. - + Make the device nodes by typing (the following example assumes an 8-port board) You can omit this part if you are running FreeBSD 5.X with &man.devfs.5;. : - + &prompt.root; cd /dev &prompt.root; for i in 0 1 2 3 4 5 6 7;do ./MAKEDEV cuac$i ttyc$i;done - + If appropriate, add dialup entries to /etc/ttys by duplicating serial device (ttyd) entries and using ttyc in place of ttyd. For example: - + ttyc0 "/usr/libexec/getty std.38400" unknown on insecure ttyc1 "/usr/libexec/getty std.38400" unknown on insecure ttyc2 "/usr/libexec/getty std.38400" unknown on insecure … ttyc7 "/usr/libexec/getty std.38400" unknown on insecure - + Reboot with the new kernel. @@ -2357,7 +2357,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure Contributed by &a.nsayer;. 25 March 1998. - + The Specialix SI/XIO and SX multiport cards use the si driver. A single machine can have up to 4 host cards. The following host cards are @@ -2386,11 +2386,11 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure SI 4 or 8 port modules. Up to 57600 bps on each port supported. - + XIO 8 port modules. Up to 115200 bps on each port supported. One type of XIO module has 7 serial and 1 parallel port. - + SXDC 8 port modules. Up to 921600 bps on each port supported. Like XIO, a module is available with one parallel port as well. @@ -2399,19 +2399,19 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure To configure an ISA host card, add the following line to your kernel configuration file, changing the numbers as appropriate: - + device si0 at isa? iomem 0xd0000 irq 11 Valid IRQ numbers are 9, 10, 11, 12 and 15 for SX ISA host cards and 11, 12 and 15 for SI/XIO ISA host cards. - + To configure an EISA or PCI host card, use this line: - + device si0 After adding the configuration entry, rebuild and install your new kernel. - + The following step, is not necessary if you are using &man.devfs.5; in FreeBSD 5.X. @@ -2421,19 +2421,19 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure device nodes in /dev. The MAKEDEV script will take care of this for you. Count how many total ports you have and type: - + &prompt.root; cd /dev &prompt.root; ./MAKEDEV ttyAnn cuaAnn - + (where nn is the number of ports) - + If you want login prompts to appear on these ports, you will need to add lines like this to /etc/ttys: ttyA01 "/usr/libexec/getty std.9600" vt100 on insecure - + Change the terminal type as appropriate. For modems, dialup or unknown is fine. diff --git a/en_US.ISO8859-1/articles/solid-state/Makefile b/en_US.ISO8859-1/articles/solid-state/Makefile index 9dfb36fb9d..6861fab294 100644 --- a/en_US.ISO8859-1/articles/solid-state/Makefile +++ b/en_US.ISO8859-1/articles/solid-state/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: FreeBSD and Solid State Devices diff --git a/en_US.ISO8859-1/articles/solid-state/article.sgml b/en_US.ISO8859-1/articles/solid-state/article.sgml index 0f8750d882..ae1617bb6e 100644 --- a/en_US.ISO8859-1/articles/solid-state/article.sgml +++ b/en_US.ISO8859-1/articles/solid-state/article.sgml @@ -51,7 +51,7 @@ - + 2001 2009 @@ -68,11 +68,11 @@ $FreeBSD$ $FreeBSD$ - + This article covers the use of solid state disk devices in &os; to create embedded systems. - + Embedded systems have the advantage of increased stability due to the lack of integral moving parts (hard drives). Account must be taken, however, for the generally low disk space available in the @@ -291,7 +291,7 @@ pseudo-device md # memory disk Mount the newly prepared flash media: &prompt.root; mount /dev/ad0a /flash - + Bring this machine up on the network so we may transfer our tar file and explode it onto our flash media filesystem. One example of how to do this is: @@ -417,7 +417,7 @@ pseudo-device md # memory disk /var/db/pkg. An example: &prompt.root; ln -s /etc/pkg /var/db/pkg - + Now, any time that you mount your filesystems as read-write and install a package, the make install will work, and package information @@ -431,7 +431,7 @@ pseudo-device md # memory disk Apache Web Server - The steps in this section are only necessary if Apache is + The steps in this section are only necessary if Apache is set up to write its pid or log information outside of /var. By default, Apache keeps its pid file in First, add the directory log/apache to the list of directories to be created in /etc/rc.d/var. - + Second, add these commands to /etc/rc.d/var after the directory creation section: diff --git a/en_US.ISO8859-1/articles/storage-devices/article.sgml b/en_US.ISO8859-1/articles/storage-devices/article.sgml index 94b7529fa7..c58a646b99 100644 --- a/en_US.ISO8859-1/articles/storage-devices/article.sgml +++ b/en_US.ISO8859-1/articles/storage-devices/article.sgml @@ -8,18 +8,18 @@
Storage Devices - + Wilko Bulte - +
wilko@FreeBSD.org
 - + &tm-attrib.freebsd; &tm-attrib.general; @@ -33,18 +33,18 @@ This article talks about storage devices with FreeBSD. - + Using ESDI hard disks - + Copyright © 1995, &a.wilko;. 24 September 1995. - + ESDI is an acronym that means Enhanced Small Device Interface. It is loosely based on the good old ST506/412 interface originally devised by Seagate Technology, the makers of the first affordable 5.25" Winchester disk. - + The acronym says Enhanced, and rightly so. In the first place the speed of the interface is higher, 10 or 15 Mbits/second instead of the 5 Mbits/second of ST412 interfaced @@ -52,33 +52,33 @@ the ESDI interface somewhat smarter to the operating system driver writers. It is by no means as smart as SCSI by the way. ESDI is standardized by ANSI. - + Capacities of the drives are boosted by putting more sectors on each track. Typical is 35 sectors per track, high capacity drives I have seen were up to 54 sectors/track. - + Although ESDI has been largely obsoleted by IDE and SCSI interfaces, the availability of free or cheap surplus drives makes them ideal for low (or now) budget systems. - + Concepts of ESDI Physical connections - + The ESDI interface uses two cables connected to each drive. One cable is a 34 pin flat cable edge connector that carries the command and status signals from the controller to the drive and vice-versa. The command cable is daisy chained between all the drives. So, it forms a bus onto which all drives are connected. - + The second cable is a 20 pin flat cable edge connector that carries the data to and from the drive. This cable is radially connected, so each drive has its own direct connection to the controller. - + To the best of my knowledge PC ESDI controllers are limited to using a maximum of 2 drives per controller. This is compatibility feature(?) left over from the WD1003 standard that reserves only a @@ -87,12 +87,12 @@ Device addressing - + On each command cable a maximum of 7 devices and 1 controller can be present. To enable the controller to uniquely identify which drive it addresses, each ESDI device is equipped with jumpers or switches to select the devices address. - + On PC type controllers the first drive is set to address 0, the second disk to address 1. Always make sure you set each disk to an unique address! So, on a @@ -102,12 +102,12 @@ Termination - + The daisy chained command cable (the 34 pin cable remember?) needs to be terminated at the last drive on the chain. For this purpose ESDI drives come with a termination resistor network that can be removed or disabled by a jumper when it is not used. - + So, one and only one drive, the one at the farthest end of the command cable has its terminator installed/enabled. The controller automatically terminates the @@ -116,7 +116,7 @@ not in the middle. - + Using ESDI disks with FreeBSD @@ -127,18 +127,18 @@ developed a profound sense of frustration. A combination of factors works against you to produce effects that are hard to understand when you have never seen them before. - + This has also led to the popular legend ESDI and FreeBSD is a plain NO-GO. The following sections try to list all the pitfalls and solutions. - + ESDI speed variants - + As briefly mentioned before, ESDI comes in two speed flavors. The older drives and controllers use a 10 Mbits/second data transfer rate. Newer stuff uses 15 Mbits/second. - + It is not hard to imagine that 15 Mbits/second drive cause problems on controllers laid out for 10 Mbits/second. As always, consult your controller and drive @@ -147,18 +147,18 @@ Stay on track - + Mainstream ESDI drives use 34 to 36 sectors per track. Most (older) controllers cannot handle more than this number of sectors. Newer, higher capacity, drives use higher numbers of sectors per track. For instance, I own a 670 MB drive that has 54 sectors per track. - + In my case, the controller could not handle this number of sectors. It proved to work well except that it only used 35 sectors on each track. This meant losing a lot of disk space. - + Once again, check the documentation of your hardware for more info. Going out-of-spec like in the example might or might not work. Give it a try or get another more capable @@ -167,13 +167,13 @@ Hard or soft sectoring - + Most ESDI drives allow hard or soft sectoring to be selected using a jumper. Hard sectoring means that the drive will produce a sector pulse on the start of each new sector. The controller uses this pulse to tell when it should start to write or read. - + Hard sectoring allows a selection of sector size (normally 256, 512 or 1024 bytes per formatted sector). FreeBSD uses 512 byte sectors. The number of sectors per track also varies while @@ -184,12 +184,12 @@ track of course gives you more usable space, but might give problems if your controller needs more bytes than the drive offers. - + In case of soft sectoring, the controller itself determines where to start/stop reading or writing. For ESDI hard sectoring is the default (at least on everything I came across). I never felt the urge to try soft sectoring. - + In general, experiment with sector settings before you install FreeBSD because you need to re-run the low-level format after each change. @@ -197,21 +197,21 @@ Low level formatting - + ESDI drives need to be low level formatted before they are usable. A reformat is needed whenever you figgle with the number of sectors/track jumpers or the physical orientation of the drive (horizontal, vertical). So, first think, then format. The format time must not be underestimated, for big disks it can take hours. - + After a low level format, a surface scan is done to find and flag bad sectors. Most disks have a manufacturer bad block list listed on a piece of paper or adhesive sticker. In addition, on most disks the list is also written onto the disk. Please use the manufacturer's list. It is much easier to remap a defect now than after FreeBSD is installed. - + Stay away from low-level formatters that mark all sectors of a track as bad as soon as they find one bad sector. Not only does this waste space, it also and more importantly causes you grief @@ -220,13 +220,13 @@ Translations - + Translations, although not exclusively a ESDI-only problem, might give you real trouble. Translations come in multiple flavors. Most of them have in common that they attempt to work around the limitations posed upon disk geometries by the original IBM PC/AT design (thanks IBM!). - + First of all there is the (in)famous 1024 cylinder limit. For a system to be able to boot, the stuff (whatever operating system) must be in the first 1024 cylinders of a disk. Only 10 bits are @@ -234,7 +234,7 @@ sectors the limit is 64 (0-63). When you combine the 1024 cylinder limit with the 16 head limit (also a design feature) you max out at fairly limited disk sizes. - + To work around this problem, the manufacturers of ESDI PC controllers added a BIOS prom extension on their boards. This BIOS extension handles disk I/O for booting (and for some @@ -245,7 +245,7 @@ and is therefore usable by the system without problems. It is noteworthy to know that FreeBSD does not use the BIOS after its kernel has started. More on this later. - + A second reason for translations is the fact that most older system BIOSes could only handle drives with 17 sectors per track (the old ST412 standard). Newer system BIOSes usually have a @@ -257,7 +257,7 @@ keep in mind that if you have multiple operating systems on the same disk, all must use the same translation - + While on the subject of translations, I have seen one controller type (but there are probably more like this) offer the option to logically split a drive in multiple partitions as a BIOS @@ -266,29 +266,29 @@ info and presented itself to the system based on the info from the disk. - + Spare sectoring - + Most ESDI controllers offer the possibility to remap bad sectors. During/after the low-level format of the disk bad sectors are marked as such, and a replacement sector is put in place (logically of course) of the bad one. - + In most cases the remapping is done by using N-1 sectors on each track for actual data storage, and sector N itself is the spare sector. N is the total number of sectors physically available on the track. The idea behind this is that the operating system sees a perfect disk without bad sectors. In the case of FreeBSD this concept is not usable. - + The problem is that the translation from bad to good is performed by the BIOS of the ESDI controller. FreeBSD, being a true 32 bit operating system, does not use the BIOS after it has been booted. Instead, it has device drivers that talk directly to the hardware. - + So: do not use spare sectoring, bad block remapping or whatever it may be called by the controller manufacturer when you want to use the disk for FreeBSD. @@ -296,7 +296,7 @@ Bad block handling - + The preceding section leaves us with a problem. The controller's bad block handling is not usable and still FreeBSD's filesystems assume perfect media without any flaws. To solve this @@ -305,14 +305,14 @@ scans a FreeBSD slice for bad blocks. Having found these bad blocks, it writes a table with the offending block numbers to the end of the FreeBSD slice. - + When the disk is in operation, the disk accesses are checked against the table read from the disk. Whenever a block number is requested that is in the bad144 list, a replacement block (also from the end of the FreeBSD slice) is used. In this way, the bad144 replacement scheme presents perfect media to the FreeBSD filesystems. - + There are a number of potential pitfalls associated with the use of bad144. First of all, the slice cannot have more than 126 bad sectors. If your drive has a high number @@ -322,7 +322,7 @@ sector of a track as bad when they find a flaw on the track. As you can imagine, the 126 limit is quickly reached when the low-level format is done this way. - + Second, if the slice contains the root filesystem, the slice should be within the 1024 cylinder BIOS limit. During the boot process the bad144 list is read using the BIOS and this only @@ -338,20 +338,20 @@ Kernel configuration - + ESDI disks are handled by the same wddriver as IDE and ST412 MFM disks. The wd driver should work for all WD1003 compatible interfaces. - + Most hardware is jumperable for one of two different I/O address ranges and IRQ lines. This allows you to have two wd type controllers in one system. - + When your hardware allows non-standard strappings, you can use these with FreeBSD as long as you enter the correct info into the kernel config file. An example from the kernel config file (they live in /sys/i386/conf BTW). - + # First WD compatible controller controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 @@ -362,17 +362,17 @@ disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 - + Particulars on ESDI hardware Adaptec 2320 controllers - + I successfully installed FreeBSD onto a ESDI disk controlled by a ACB-2320. No other operating system was present on the disk. - + To do so I low level formatted the disk using NEFMT.EXE (ftpable from www.adaptec.com) and answered NO to @@ -380,20 +380,20 @@ disk wd3 at wdc1 drive 1 sector on each track. The BIOS on the ACD-2320 was disabled. I used the free configurable option in the system BIOS to allow the BIOS to boot it. - + Before using NEFMT.EXE I tried to format the disk using the ACB-2320 BIOS built-in formatter. This proved to be a show stopper, because it did not give me an option to disable spare sectoring. With spare sectoring enabled the FreeBSD installation process broke down on the bad144 run. - + Please check carefully which ACB-232xy variant you have. The x is either 0 or 2, indicating a controller without or with a floppy controller on board. - + The y is more interesting. It can either be a blank, a A-8 or a D. A blank indicates a plain 10 Mbits/second controller. An @@ -401,18 +401,18 @@ disk wd3 at wdc1 drive 1 capable of handling 52 sectors/track. A D means a 15 Mbits/second controller that can also handle drives with > 36 sectors/track (also 52?). - + All variations should be capable of using 1:1 interleaving. Use 1:1, FreeBSD is fast enough to handle it. Western Digital WD1007 controllers - + I successfully installed FreeBSD onto a ESDI disk controlled by a WD1007 controller. To be precise, it was a WD1007-WA2. Other variations of the WD1007 do exist. - + To get it to work, I had to disable the sector translation and the WD1007's onboard BIOS. This implied I could not use the low-level formatter built into this BIOS. Instead, I grabbed @@ -423,34 +423,34 @@ disk wd3 at wdc1 drive 1 Ultrastor U14F controllers - + According to multiple reports from the net, Ultrastor ESDI boards work OK with FreeBSD. I lack any further info on particular settings. - + Further reading - + If you intend to do some serious ESDI hacking, you might want to have the official standard at hand: - + The latest ANSI X3T10 committee document is: Enhanced Small Device Interface (ESDI) [X3.170-1990/X3.170a-1991] [X3T10/792D Rev 11] - + On Usenet the newsgroup comp.periphs is a noteworthy place to look for more info. - + The World Wide Web (WWW) also proves to be a very handy info source: For info on Adaptec ESDI controllers see . For info on Western Digital controllers see . - + Thanks to... @@ -458,20 +458,20 @@ disk wd3 at wdc1 drive 1 disk for testing. - + What is SCSI? - + Copyright © 1995, &a.wilko;. July 6, 1996. - + SCSI is an acronym for Small Computer Systems Interface. It is an ANSI standard that has become one of the leading I/O buses in the computer industry. The foundation of the SCSI standard was laid by Shugart Associates (the same guys that gave the world the first mini floppy disks) when they introduced the SASI bus (Shugart Associates Standard Interface). - + After some time an industry effort was started to come to a more strict standard allowing devices from different vendors to work together. This effort was recognized in the ANSI SCSI-1 standard. @@ -479,7 +479,7 @@ disk wd3 at wdc1 drive 1 current standard is SCSI-2 (see Further reading), with SCSI-3 on the drawing boards. - + In addition to a physical interconnection standard, SCSI defines a logical (command set) standard to which disk devices must adhere. This standard is called the Common Command Set (CCS) and was developed @@ -487,7 +487,7 @@ disk wd3 at wdc1 drive 1 (revised) CCS as part of the standard itself. The commands are dependent on the type of device at hand. It does not make much sense of course to define a Write command for a scanner. - + The SCSI bus is a parallel bus, which comes in a number of variants. The oldest and most used is an 8 bit wide bus, with single-ended signals, carried on 50 wires. (If you do not know what @@ -501,13 +501,13 @@ disk wd3 at wdc1 drive 1 is 40 million transfers per second (40 Mbytes/sec on a 8 bit bus). Most hard drives sold today are single-ended Ultra SCSI (8 or 16 bits). - + Of course the SCSI bus not only has data lines, but also a number of control signals. A very elaborate protocol is part of the standard to allow multiple devices to share the bus in an efficient manner. In SCSI-2, the data is always checked using a separate parity line. In pre-SCSI-2 designs parity was optional. - + In SCSI-3 even faster bus types are introduced, along with a serial SCSI busses that reduces the cabling overhead and allows a higher maximum bus length. You might see names like SSA and @@ -515,7 +515,7 @@ disk wd3 at wdc1 drive 1 in widespread use (especially not in the typical FreeBSD environment). For this reason the serial bus types are not discussed any further. - + As you could have guessed from the description above, SCSI devices are intelligent. They have to be to adhere to the SCSI standard (which is over 2 inches thick BTW). So, for a hard disk drive for @@ -523,12 +523,12 @@ disk wd3 at wdc1 drive 1 particular block, but simply the number of the block you want. Elaborate caching schemes, automatic bad block replacement etc are all made possible by this intelligent device approach. - + On a SCSI bus, each possible pair of devices can communicate. Whether their function allows this is another matter, but the standard does not restrict it. To avoid signal contention, the 2 devices have to arbitrate for the bus before using it. - + The philosophy of SCSI is to have a standard that allows older-standard devices to work with newer-standard ones. So, an old SCSI-1 device should normally work on a SCSI-2 bus. I say Normally, @@ -537,7 +537,7 @@ disk wd3 at wdc1 drive 1 new bus. Modern devices are usually more well-behaved, because the standardization has become more strict and is better adhered to by the device manufacturers. - + Generally speaking, the chances of getting a working set of devices on a single bus is better when all the devices are SCSI-2 or newer. This implies that you do not have to dump all your old stuff @@ -548,7 +548,7 @@ disk wd3 at wdc1 drive 1 devices however. This is especially advantageous if you have an Ultra160 host adapter where you should separate your U160 devices from the Fast and Wide SCSI-2 devices. - + Components of SCSI @@ -561,16 +561,16 @@ disk wd3 at wdc1 drive 1 their hardware particulars. FreeBSD uses this capability during boot to check out what devices are connected and whether they need any special treatment. - + The advantage of intelligent devices is obvious: the device drivers on the host can be made in a much more generic fashion, there is no longer a need to change (and qualify!) drivers for every odd new device that is introduced. - + For cabling and connectors there is a golden rule: get good stuff. With bus speeds going up all the time you will save yourself a lot of grief by using good material. - + So, gold plated connectors, shielded cabling, sturdy connector hoods with strain reliefs etc are the way to go. Second golden rule: do no use cables longer than necessary. I once spent 3 days hunting @@ -578,7 +578,7 @@ disk wd3 at wdc1 drive 1 the SCSI bus by 1 meter solved the problem. And the original bus length was well within the SCSI specification. - + SCSI bus types @@ -589,27 +589,27 @@ disk wd3 at wdc1 drive 1 converter hardware to transform a single-ended bus into a differential one (and vice versa). The differences between the bus types are explained in the next sections. - + In lots of SCSI related documentation there is a sort of jargon in use to abbreviate the different bus types. A small list: - + FWD: Fast Wide Differential - + FND: Fast Narrow Differential - + SE: Single Ended - + FN: Fast Narrow - + etc. @@ -618,11 +618,11 @@ disk wd3 at wdc1 drive 1 With a minor amount of imagination one can usually imagine what is meant. - + Wide is a bit ambiguous, it can indicate 16 or 32 bit buses. As far as I know, the 32 bit variant is not (yet) in use, so wide normally means 16 bit. - + Fast means that the timing on the bus is somewhat different, so that on a narrow (8 bit) bus 10 Mbytes/sec are possible instead of 5 Mbytes/sec for slow SCSI. As discussed before, bus speeds of 20 @@ -640,7 +640,7 @@ disk wd3 at wdc1 drive 1 Single ended buses - + A single-ended SCSI bus uses signals that are either 5 Volts or 0 Volts (indeed, TTL levels) and are relative to a COMMON ground reference. A singled ended 8 bit SCSI bus has @@ -650,7 +650,7 @@ disk wd3 at wdc1 drive 1 maximum length allowed drops to 3 meters. Fast-SCSI means that instead of 5Mbytes/sec the bus allows 10Mbytes/sec transfers. - + Fast-20 (Ultra SCSI) and Fast-40 allow for 20 and 40 million transfers/second respectively. So, F20 is 20 Mbytes/second on a 8 bit bus, 40 Mbytes/second on a 16 bit bus etc. For F20 the max @@ -663,16 +663,16 @@ disk wd3 at wdc1 drive 1 bus must adhere to the length restrictions for fast buses! - + It is obvious that with the newer fast-SCSI devices the bus length can become a real bottleneck. This is why the differential SCSI bus was introduced in the SCSI-2 standard. - + For connector pinning and connector types please refer to the SCSI-2 standard (see Further reading) itself, connectors etc are listed there in painstaking detail. - + Beware of devices using non-standard cabling. For instance Apple uses a 25pin D-type connecter (like the one on serial ports and parallel printers). Considering that the official SCSI bus @@ -685,7 +685,7 @@ disk wd3 at wdc1 drive 1 Differential buses - + A differential SCSI bus has a maximum length of 25 meters. Quite a difference from the 3 meters for a single-ended fast-SCSI bus. The idea behind differential signals is that each bus signal @@ -695,7 +695,7 @@ disk wd3 at wdc1 drive 1 or de-asserted. To a certain extent the voltage difference between ground and the signal wire pair is not relevant (do not try 10 kVolts though). - + It is beyond the scope of this document to explain why this differential idea is so much better. Just accept that electrically seen the use of differential signals gives a much @@ -703,7 +703,7 @@ disk wd3 at wdc1 drive 1 use for inter-cabinet connections. Because of the lower cost single ended is mostly used for shorter buses like inside cabinets. - + There is nothing that stops you from using differential stuff with FreeBSD, as long as you use a controller that has device driver support in FreeBSD. As an example, Adaptec marketed the @@ -714,7 +714,7 @@ disk wd3 at wdc1 drive 1 Terminators - + Terminators in SCSI terminology are resistor networks that are used to get a correct impedance matching. Impedance matching is important to get clean signals on the bus, without reflections or @@ -722,7 +722,7 @@ disk wd3 at wdc1 drive 1 line you probably know what reflections are. With 20Mbytes/sec traveling over your SCSI bus, you do not want signals echoing back. - + Terminators come in various incarnations, with more or less sophisticated designs. Of course, there are internal and external variants. Many SCSI devices come with a number of sockets in @@ -736,7 +736,7 @@ disk wd3 at wdc1 drive 1 onto a flat cable bus. Others look like external connectors, or a connector hood without a cable. So, lots of choice as you can see. - + There is much debate going on if and when you should switch from simple resistor (passive) terminators to active terminators. Active terminators contain slightly more elaborate circuit to give @@ -745,11 +745,11 @@ disk wd3 at wdc1 drive 1 buses and/or fast devices. If you ever have problems with your SCSI buses you might consider trying an active terminator. Try to borrow one first, they reputedly are quite expensive. - + Please keep in mind that terminators for differential and single-ended buses are not identical. You should not mix the two variants. - + OK, and now where should you install your terminators? This is by far the most misunderstood part of SCSI. And it is by far the simplest. The rule is: every single line on the SCSI @@ -759,7 +759,7 @@ disk wd3 at wdc1 drive 1 grief, because wrong termination has the potential to introduce highly mysterious bugs. (Note the potential here; the nastiest part is that it may or may not work.) - + A common pitfall is to have an internal (flat) cable in a machine and also an external cable attached to the controller. It seems almost everybody forgets to remove the terminators from the @@ -774,13 +774,13 @@ disk wd3 at wdc1 drive 1 bits of the bus on the adapter (as well as the last devices on each bus, of course). - + What I did myself is remove all terminators from my SCSI devices and controllers. I own a couple of external terminators, for both the Centronics-type external cabling and for the internal flat cable connectors. This makes reconfiguration much easier. - + On modern devices, sometimes integrated terminators are used. These things are special purpose integrated circuits that can be enabled or disabled with a control pin. It is not necessary to @@ -794,25 +794,25 @@ disk wd3 at wdc1 drive 1 Terminator power - + The terminators discussed in the previous chapter need power to operate properly. On the SCSI bus, a line is dedicated to this purpose. So, simple huh? - + Not so. Each device can provide its own terminator power to the terminator sockets it has on-device. But if you have external terminators, or when the device supplying the terminator power to the SCSI bus line is switched off you are in trouble. - + The idea is that initiators (these are devices that initiate actions on the bus, a discussion follows) must supply terminator power. All SCSI devices are allowed (but not required) to supply terminator power. - + To allow for un-powered devices on a bus, the terminator power must be supplied to the bus via a diode. This prevents the backflow of current to un-powered devices. - + To prevent all kinds of nastiness, the terminator power is usually fused. As you can imagine, fuses might blow. This can, but does not have to, lead to a non functional bus. If multiple @@ -820,18 +820,18 @@ disk wd3 at wdc1 drive 1 you out of business. A single supplier with a blown fuse certainly will. Clever external terminators sometimes have a LED indication that shows whether terminator power is present. - + In newer designs auto-restoring fuses that reset themselves after some time are sometimes used. Device addressing - + Because the SCSI bus is, ehh, a bus there must be a way to distinguish or address the different devices connected to it. - + This is done by means of the SCSI or target ID. Each device has a unique target ID. You can select the ID to which a device must respond using a set of jumpers, or a dip switch, or something @@ -839,12 +839,12 @@ disk wd3 at wdc1 drive 1 from the boot menu. (Yet some others will not let you change the ID from 7.) Consult the documentation of your device for more information. - + Beware of multiple devices configured to use the same ID. Chaos normally reigns in this case. A pitfall is that one of the devices sharing the same ID sometimes even manages to answer to I/O requests! - + For an 8 bit bus, a maximum of 8 targets is possible. The maximum is 8 because the selection is done bitwise using the 8 data lines on the bus. For wide buses this increases to the @@ -857,7 +857,7 @@ disk wd3 at wdc1 drive 1 something higher than 7 (or your CDROM will stop working). - + The higher the SCSI target ID, the higher the priority the devices has. When it comes to arbitration between devices that want to use the bus at the same time, the device that has the @@ -868,7 +868,7 @@ disk wd3 at wdc1 drive 1 on a wide-SCSI system. (If you are wondering why the lower 8 have higher priority, read the previous paragraph for a hint.) - + For a further subdivision, the standard allows for Logical Units or LUNs for short. A single target ID may have multiple LUNs. For example, a tape device including a tape changer may @@ -876,10 +876,10 @@ disk wd3 at wdc1 drive 1 changer. In this way, the host system can address each of the functional units of the tape changer as desired. - + Bus layout - + SCSI buses are linear. So, not shaped like Y-junctions, star topologies, rings, cobwebs or whatever else people might want to invent. One of the most common mistakes is for people with @@ -889,31 +889,31 @@ disk wd3 at wdc1 drive 1 really lucky, but I can almost guarantee that your system will stop functioning at the most unfortunate moment (this is also known as Murphy's law). - + You might notice that the terminator issue discussed earlier becomes rather hairy if your bus is not linear. Also, if you have more connectors than devices on your internal SCSI cable, make sure you attach devices on connectors on both ends instead of using the connectors in the middle and let one or both ends dangle. This will screw up the termination of the bus. - + The electrical characteristics, its noise margins and ultimately the reliability of it all are tightly related to linear bus rule. - + Stick to the linear bus rule! - + Using SCSI with FreeBSD About translations, BIOSes and magic... - + As stated before, you should first make sure that you have a electrically sound bus. - + When you want to use a SCSI disk on your PC as boot disk, you must aware of some quirks related to PC BIOSes. The PC BIOS in its first incarnation used a low level physical interface to the @@ -922,20 +922,20 @@ disk wd3 at wdc1 drive 1 involved stating number of heads, number of cylinders, number of sectors per track, obscure things like precompensation and reduced write current cylinder etc. - + One might be inclined to think that since SCSI disks are smart you can forget about this. Alas, the arcane setup issue is still present today. The system BIOS needs to know how to access your SCSI disk with the head/cyl/sector method in order to load the FreeBSD kernel during boot. - + The SCSI host adapter or SCSI controller you have put in your AT/EISA/PCI/whatever bus to connect your disk therefore has its own on-board BIOS. During system startup, the SCSI BIOS takes over the hard disk interface routines from the system BIOS. To fool the system BIOS, the system setup is normally set to No hard disk present. Obvious, is it not? - + The SCSI BIOS itself presents to the system a so called translated drive. This means that a fake drive table is constructed that allows the PC to boot the drive. @@ -945,37 +945,37 @@ disk wd3 at wdc1 drive 1 size. It is useful to note that 32 * 64 / 2 = the size of your drive in megabytes. The division by 2 is to get from disk blocks that are normally 512 bytes in size to Kbytes. - + Right. All is well now?! No, it is not. The system BIOS has another quirk you might run into. The number of cylinders of a bootable hard disk cannot be greater than 1024. Using the translation above, this is a show-stopper for disks greater than 1 GB. With disk capacities going up all the time this is causing problems. - + Fortunately, the solution is simple: just use another translation, e.g. with 128 heads instead of 32. In most cases new SCSI BIOS versions are available to upgrade older SCSI host adapters. Some newer adapters have an option, in the form of a jumper or software setup selection, to switch the translation the SCSI BIOS uses. - + It is very important that all operating systems on the disk use the same translation to get the right idea about where to find the relevant partitions. So, when installing FreeBSD you must answer any questions about heads/cylinders etc using the translated values your host adapter uses. - + Failing to observe the translation issue might lead to un-bootable systems or operating systems overwriting each others partitions. Using fdisk you should be able to see all partitions. - + You might have heard some talk of lying devices? Older FreeBSD kernels used to report the geometry of SCSI disks when booting. An example from one of my systems: - + aha0 targ 0 lun 0: <MICROP 1588-15MB1057404HSP4> da0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512 @@ -984,9 +984,9 @@ da0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512(bt0:0:0): "SEAGATE ST41651 7574" type 0 fixed SCSI 2 da0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) - + Why has this changed? - + This info is retrieved from the SCSI disk itself. Newer disks often use a technique called zone bit recording. The idea is that on the outer cylinders of the drive there is more space so more @@ -1003,13 +1003,13 @@ da0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) SCSI subsystem design - + FreeBSD uses a layered SCSI subsystem. For each different controller card a device driver is written. This driver knows all the intimate details about the hardware it controls. The driver has a interface to the upper layers of the SCSI subsystem through which it receives its commands and reports back any status. - + On top of the card drivers there are a number of more generic drivers for a class of devices. More specific: a driver for tape devices (abbreviation: sa, for serial access), @@ -1017,7 +1017,7 @@ da0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) In case you are wondering where you can find this stuff, it all lives in /sys/cam/scsi. See the man pages in section 4 for more details. - + The multi level design allows a decoupling of low-level bit banging and more high level stuff. Adding support for another piece of hardware is a much more manageable problem. @@ -1025,7 +1025,7 @@ da0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) Kernel configuration - + Dependent on your hardware, the kernel configuration file must contain one or more lines describing your host adapter(s). This includes I/O addresses, interrupts etc. Consult the manual page for @@ -1035,7 +1035,7 @@ da0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) possible option you can dream of. It does not imply LINT will actually get you to a working kernel at all. - + Although it is probably stating the obvious: the kernel config file should reflect your actual hardware setup. So, interrupts, I/O addresses etc must match the kernel config file. During @@ -1050,11 +1050,11 @@ da0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors) adapters themselves at boot time; thus, you just need to write, for instance, controller ahc0. - + An example loosely based on the FreeBSD 2.2.5-Release kernel config file LINT with some added comments (between []): - + # SCSI host adapters: `aha', `ahb', `aic', `bt', `nca' # # aha: Adaptec 154x @@ -1091,14 +1091,14 @@ disk da2 at scbus1 target 3 [SCSI disk on the uha0] disk da3 at scbus2 target 4 [SCSI disk on the ncr0] tape sa1 at scbus0 target 6 [SCSI tape at target 6] device cd0 at scbus? [the first ever CDROM found, no wiring] - + The example above tells the kernel to look for a ahc (Adaptec 274x) controller, then for an NCR/Symbios board, and so on. The lines following the controller specifications tell the kernel to configure specific devices but only attach them when they match the target ID and LUN specified on the corresponding bus. - + Wired down devices get first shot at the unit numbers so the first non wired down device, is allocated the unit number one greater than the highest @@ -1116,26 +1116,26 @@ device cd0 at scbus? [the first ever CDROM found, no wiring]< no relationship with its target ID on the SCSI bus. - + Below is another example of a kernel config file as used by FreeBSD version < 2.0.5. The difference with the first example is that devices are not wired down. Wired down means that you specify which SCSI target belongs to which device. - + A kernel built to the config file below will attach the first SCSI disk it finds to da0, the second disk to da1 etc. If you ever removed or added a disk, all other devices of the same type (disk in this case) would move around. This implies you have to change /etc/fstab each time. - + Although the old style still works, you are strongly recommended to use this new feature. It will save you a lot of grief whenever you shift your hardware around on the SCSI buses. So, when you re-use your old trusty config file after upgrading from a pre-FreeBSD2.0.5.R system check this out. - + [driver for Adaptec 174x] controller ahb0 at isa? bio irq 11 vector ahbintr @@ -1152,14 +1152,14 @@ device sa0 [support for 2 SCSI tapes] [for the CDROM] device cd0 #Only need one of these, the code dynamically grows - + Both examples support SCSI disks. If during boot more devices of a specific type (e.g. da disks) are found than are configured in the booting kernel, the system will simply allocate more devices, incrementing the unit number starting at the last number wired down. If there are no wired down devices then counting starts at unit 0. - + Use man 4 scsi to check for the latest info on the SCSI subsystem. For more detailed info on host adapter drivers use e.g., man 4 ahc for info on the @@ -1168,19 +1168,19 @@ device cd0 #Only need one of these, the code dynamically grows Tuning your SCSI kernel setup - + Experience has shown that some devices are slow to respond to INQUIRY commands after a SCSI bus reset (which happens at boot time). An INQUIRY command is sent by the kernel on boot to see what kind of device (disk, tape, CDROM etc.) is connected to a specific target ID. This process is called device probing by the way. - + To work around the slow response problem, FreeBSD allows a tunable delay time before the SCSI devices are probed following a SCSI bus reset. You can set this delay time in your kernel configuration file using a line like: - + options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device This line sets the delay time to 15 seconds. On my own system @@ -1192,29 +1192,29 @@ device cd0 #Only need one of these, the code dynamically grows Rogue SCSI devices - + Although the SCSI standard tries to be complete and concise, it is a complex standard and implementing things correctly is no easy task. Some vendors do a better job then others. - + This is exactly where the rogue devices come into view. Rogues are devices that are recognized by the FreeBSD kernel as behaving slightly (...) non-standard. Rogue devices are reported by the kernel when booting. An example for two of my cartridge tape units: - + Feb 25 21:03:34 yedi /kernel: ahb0 targ 5 lun 0: <TANDBERG TDC 3600 -06:> Feb 25 21:03:34 yedi /kernel: sa0: Tandberg tdc3600 is a known rogue Mar 29 21:16:37 yedi /kernel: aha0 targ 5 lun 0: <ARCHIVE VIPER 150 21247-005> Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue - + For instance, there are devices that respond to all LUNs on a certain target ID, even if they are actually only one device. It is easy to see that the kernel might be fooled into believing that there are 8 LUNs at that particular target ID. The confusion this causes is left as an exercise to the reader. - + The SCSI subsystem of FreeBSD recognizes devices with bad habits by looking at the INQUIRY response they send when probed. Because the INQUIRY response also includes the version number of @@ -1223,12 +1223,12 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue /sys/cam/scsi/scsi_sa.c and /sys/cam/scsi/scsi_all.c for more info on how this is done. - + This scheme works fine, but keep in mind that it of course only works for devices that are known to be weird. If you are the first to connect your bogus Mumbletech SCSI CDROM you might be the one that has to define which workaround is needed. - + After you got your Mumbletech working, please send the required workaround to the FreeBSD development team for inclusion in the next release of FreeBSD. Other Mumbletech owners will be @@ -1237,18 +1237,18 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Multiple LUN devices - + In some cases you come across devices that use multiple logical units (LUNs) on a single SCSI ID. In most cases FreeBSD only probes devices for LUN 0. An example are so called bridge boards that connect 2 non-SCSI hard disks to a SCSI bus (e.g. an Emulex MD21 found in old Sun systems). - + This means that any devices with LUNs != 0 are not normally found during device probe on system boot. To work around this problem you must add an appropriate entry in /sys/cam/scsi and rebuild your kernel. - + Look for a struct that is initialized like below: (FIXME: which file? Do these entries still exist in this form now that we use CAM?) @@ -1257,16 +1257,16 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue T_DIRECT, T_FIXED, "MAXTOR", "XT-4170S", "B5A", "mx1", SC_ONE_LU } - + For your Mumbletech BRIDGE2000 that has more than one LUN, acts as a SCSI disk and has firmware revision 123 you would add something like: - + { T_DIRECT, T_FIXED, "MUMBLETECH", "BRIDGE2000", "123", "da", SC_MORE_LUS } - + The kernel on boot scans the inquiry data it receives against the table and acts accordingly. See the source for more info. @@ -1274,10 +1274,10 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Tagged command queuing - + Modern SCSI devices, particularly magnetic disks, support what is called tagged command queuing (TCQ). - + In a nutshell, TCQ allows the device to have multiple I/O requests outstanding at the same time. Because the device is intelligent, it can optimize its operations (like head @@ -1285,12 +1285,12 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue like RAID (Redundant Array of Independent Disks) arrays the TCQ function is indispensable to take advantage of the device's inherent parallelism. - + Each I/O request is uniquely identified by a tag (hence the name tagged command queuing) and this tag is used by FreeBSD to see which I/O in the device drivers queue is reported as complete by the device. - + It should be noted however that TCQ requires device driver support and that some devices implemented it not quite right in their firmware. This problem bit me once, and it @@ -1300,84 +1300,84 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Bus-master host adapters - + Most, but not all, SCSI host adapters are bus mastering controllers. This means that they can do I/O on their own without putting load onto the host CPU for data movement. - + This is of course an advantage for a multitasking operating system like FreeBSD. It must be noted however that there might be some rough edges. - + For instance an Adaptec 1542 controller can be set to use different transfer speeds on the host bus (ISA or AT in this case). The controller is settable to different rates because not all motherboards can handle the higher speeds. Problems like hang-ups, bad data etc might be the result of using a higher data transfer rate then your motherboard can stomach. - + The solution is of course obvious: switch to a lower data transfer rate and try if that works better. - + In the case of a Adaptec 1542, there is an option that can be put into the kernel config file to allow dynamic determination of the right, read: fastest feasible, transfer rate. This option is disabled by default: - + options "TUNE_1542" #dynamic tune of bus DMA speed - + Check the manual pages for the host adapter that you use. Or better still, use the ultimate documentation (read: driver source). - + Tracking down problems The following list is an attempt to give a guideline for the most common SCSI problems and their solutions. It is by no means complete. - + Check for loose connectors and cables. - + Check and double check the location and number of your terminators. - + Check if your bus has at least one supplier of terminator power (especially with external terminators. - + Check if no double target IDs are used. - + Check if all devices to be used are powered up. - + Make a minimal bus config with as little devices as possible. - + If possible, configure your host adapter to use slow bus speeds. - + Disable tagged command queuing to make things as simple as possible (for a NCR host adapter based system see man ncrcontrol) - + If you can compile a kernel, make one with the SCSIDEBUG option, and try accessing the @@ -1395,16 +1395,16 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue - + Further reading If you intend to do some serious SCSI hacking, you might want to have the official standard at hand: - + Approved American National Standards can be purchased from ANSI at - +
13th Floor 11 West 42nd Street @@ -1431,7 +1431,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Many X3T10 draft documents are available electronically on the SCSI BBS (719-574-0424) and on the ncrinfo.ncr.com anonymous FTP site. - + Latest X3T10 committee documents are: @@ -1439,22 +1439,22 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue AT Attachment (ATA or IDE) [X3.221-1994] (Approved) - + ATA Extensions (ATA-2) [X3T10/948D Rev 2i] - + Enhanced Small Device Interface (ESDI) [X3.170-1990/X3.170a-1991] (Approved) - + Small Computer System Interface — 2 (SCSI-2) [X3.131-1994] (Approved) - + SCSI-2 Common Access Method Transport and SCSI Interface Module (CAM) [X3T10/792D Rev 11] @@ -1471,33 +1471,33 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Prentice Hall, Englewood Cliffs, NJ, 07632 Phone: (201) 767-5937 ISBN 0-13-796855-8 - + Basics of SCSI, a SCSI tutorial written by Ancot Corporation Contact Ancot for availability information at: Phone: (415) 322-5322 Fax: (415) 322-0455 - + SCSI Interconnection Guide Book, an AMP publication (dated 4/93, Catalog 65237) that lists the various SCSI connectors and suggests cabling schemes. Available from AMP at (800) 522-6752 or (717) 564-0100 - + Fast Track to SCSI, A Product Guide written by Fujitsu. Available from: Prentice Hall, Englewood Cliffs, NJ, 07632 Phone: (201) 767-5937 ISBN 0-13-307000-X - + The SCSI Bench Reference, The SCSI Encyclopedia, and the SCSI Tutor, ENDL Publications, 14426 Black Walnut Court, Saratoga CA, 95070 Phone: (408) 867-6642 - + Zadian SCSI Navigator (quick ref. book) and Discover the Power of SCSI (First book along with @@ -1518,38 +1518,38 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue information about the devices you own. - + * Disk/tape controllers - + * SCSI - + * IDE - + * Floppy - + Hard drives - + SCSI hard drives Contributed by &a.asami;. 17 February 1998. - + As mentioned in the SCSI section, virtually all SCSI hard drives sold today are SCSI-2 compliant and thus will work fine as long as you connect them to a supported SCSI @@ -1563,7 +1563,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Rotational speed - + Rotational speeds of SCSI drives sold today range from around 4,500RPM to 15,000RPM. Most of them are either 7,200RPM or 10,000RPM, with 15,000RPM becoming affordable (June 2002). @@ -1572,7 +1572,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue counterparts. A large fraction of today's disk drive malfunctions are heat-related. If you do not have very good cooling in your PC case, you may want to stick with 7,200RPM or slower drives. - + Note that newer drives, with higher areal recording densities, can deliver much more bits per rotation than older ones. Today's top-of-line 7,200RPM drives can sustain a throughput comparable to @@ -1581,13 +1581,13 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue (or transfer) rate. It is usually in megabits/sec so divide it by 8 and you will get the rough approximation of how much megabytes/sec you can get out of the drive. - + (If you are a speed maniac and want a 15,000RPM drive for your cute little PC, be my guest; however, those drives become extremely hot. Do not even think about it if you do not have a fan blowing air directly at the drive or a properly ventilated disk enclosure.) - + Obviously, the latest 15,000RPM drives and 10,000RPM drives can deliver more data than the latest 7,200RPM drives, so if absolute bandwidth is the necessity for your applications, you have little @@ -1606,7 +1606,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue similar or even better results by using the ccd (concatenated disk) driver to create a striped disk array out of multiple slower drives for comparable overall cost. - + Make sure you have adequate air flow around the drive, especially if you are going to use a fast-spinning drive. You generally need at least 1/2” (1.25cm) of spacing above and below a @@ -1615,7 +1615,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue where the air flows in, and put the drive where it will have the largest volume of cool air flowing around it. You may need to seal some unwanted holes or add a new fan for effective cooling. - + Another consideration is noise. Many 10,000 or faster drives generate a high-pitched whine which is quite unpleasant to most people. That, plus the extra fans often required for cooling, may @@ -1625,7 +1625,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Form factor - + Most SCSI drives sold today are of 3.5” form factor. They come in two different heights; 1.6” (half-height) or 1” (low-profile). The half-height drive is the same @@ -1637,7 +1637,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Interface - + The majority of SCSI hard drives sold today are Ultra, Ultra-wide, or Ultra160 SCSI. As of this writing (June 2002), the first Ultra320 host adapters and devices become available. @@ -1649,7 +1649,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue bus integrity problems. Unless you have a well-designed disk enclosure, it is not easy to make more than 5 or 6 Ultra SCSI drives work on a single bus. - + On the other hand, if you need to connect many drives, going for Fast-wide SCSI may not be a bad idea. That will have the same max bandwidth as Ultra (narrow) SCSI, while electronically it is @@ -1659,7 +1659,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue cost a little more but it may save you down the road. (Besides, if you can not afford the cost difference, you should not be building a disk array.) - + There are two variant of wide SCSI drives; 68-pin and 80-pin SCA (Single Connector Attach). The SCA drives do not have a separate 4-pin power connector, and also read the SCSI ID settings @@ -1675,20 +1675,20 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue LED lines). - + * IDE hard drives - + Tape drives - + Contributed by &a.jmb;. 2 July 1996. - + General tape access commands @@ -1697,7 +1697,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue erase, and status. See the &man.mt.1; manual page for a detailed description. - + Controller Interfaces @@ -1708,7 +1708,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue linkend="hw-storage-controllers">Disk/tape controllers. - + SCSI drives @@ -1725,153 +1725,153 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue 4mm (DAT: Digital Audio Tape) - + Archive Python 28454 Archive Python 04687 - + HP C1533A - + HP C1534A - + HP 35450A - + HP 35470A - + HP 35480A - + SDT-5000 - + Wangtek 6200 8mm (Exabyte) - + EXB-8200 - + EXB-8500 - + EXB-8505 QIC (Quarter-Inch Cartridge) - + Archive Anaconda 2750 - + Archive Viper 60 - + Archive Viper 150 - + Archive Viper 2525 - + Tandberg TDC 3600 Tandberg TDC 3620 - + Tandberg TDC 3800 - + Tandberg TDC 4222 - + Wangtek 5525ES DLT (Digital Linear Tape) - + Digital TZ87 Mini-Cartridge - + Conner CTMS 3200 - + Exabyte 2501 Autoloaders/Changers - + Hewlett-Packard HP C1553A Autoloading DDS2 - + * IDE drives - + Floppy drives Conner 420R - + * Parallel port drives - + Detailed Information Archive Anaconda 2750 - + The boot message identifier for this drive is ARCHIVE ANCDA 2750 28077 -003 type 1 removable SCSI 2 - + This is a QIC tape drive. - + Native capacity is 1.35GB when using QIC-1350 tapes. This drive will read and write QIC-150 (DC6150), QIC-250 (DC6250), and QIC-525 (DC6525) tapes as well. - + Data transfer rate is 350kB/s using &man.dump.8;. Rates of 530kB/s have been reported when using Amanda Production of this drive has been discontinued. - + The SCSI bus connector on this tape drive is reversed from that on most other SCSI devices. Make sure that you have enough SCSI cable to twist the cable one-half turn before and after the Archive Anaconda tape drive, or turn your other SCSI devices upside-down. - + Two kernel code changes are required to use this drive. This drive will not work as delivered. - + If you have a SCSI-2 controller, short jumper 6. Otherwise, the drive behaves are a SCSI-1 device. When operating as a SCSI-1 device, this drive, locks the SCSI bus during some tape operations, including: fsf, rewind, and rewoffl. - + If you are using the NCR SCSI controllers, patch the file /usr/src/sys/pci/ncr.c (as shown below). Build and install a new kernel. - + *** 4831,4835 **** }; - + ! if (np->latetime>4) { /* ** Although we tried to wake it up, @@ -1881,29 +1881,29 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue ! if (np->latetime>1200) { /* ** Although we tried to wake it up, - + Reported by: &a.jmb; Archive Python 28454 - + The boot message identifier for this drive is ARCHIVE Python 28454-XXX4ASB type 1 removable SCSI 2 density code 0x8c, 512-byte blocks - + This is a DDS-1 tape drive. - + Native capacity is 2.5GB on 90m tapes. - + Data transfer rate is XXX. - + This drive was repackaged by Sun Microsystems as model 595-3067. - + Reported by: Bob Bishop rb@gid.co.uk - + Throughput is in the 1.5 MByte/sec range, however this will drop if the disks and tape drive are on the same SCSI controller. @@ -1915,7 +1915,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Archive Python 04687 - The boot message identifier for this drive is ARCHIVE + The boot message identifier for this drive is ARCHIVE Python 04687-XXX 6580 Removable Sequential Access SCSI-2 device @@ -1930,7 +1930,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Parity is controlled by switch 5. Switch 5 on to enable parity control. Compression is - enabled with Switch 6 off. It is possible to + enabled with Switch 6 off. It is possible to override compression with the SCSI MODE SELECT command (see &man.mt.1;). @@ -1939,117 +1939,117 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Archive Viper 60 - + The boot message identifier for this drive is ARCHIVE VIPER 60 21116 -007 type 1 removable SCSI 1 - + This is a QIC tape drive. - + Native capacity is 60MB. - + Data transfer rate is XXX. - + Production of this drive has been discontinued. - + Reported by: Philippe Regnauld regnauld@hsc.fr Archive Viper 150 - + The boot message identifier for this drive is ARCHIVE VIPER 150 21531 -004 Archive Viper 150 is a known rogue type 1 removable SCSI 1. A multitude of firmware revisions exist for this drive. Your drive may report different numbers (e.g 21247 -005. - + This is a QIC tape drive. - + Native capacity is 150/250MB. Both 150MB (DC6150) and 250MB (DC6250) tapes have the recording format. The 250MB tapes are approximately 67% longer than the 150MB tapes. This drive can read 120MB tapes as well. It can not write 120MB tapes. - + Data transfer rate is 100kB/s - + This drive reads and writes DC6150 (150MB) and DC6250 (250MB) tapes. - + This drives quirks are known and pre-compiled into the SCSI tape device driver (&man.st.4;). - + Under FreeBSD 2.2-CURRENT, use mt blocksize 512 to set the blocksize. (The particular drive had firmware revision 21247 -005. Other firmware revisions may behave differently) Previous versions of FreeBSD did not have this problem. - + Production of this drive has been discontinued. - + Reported by: Pedro A M Vazquez vazquez@IQM.Unicamp.BR - + &a.msmith; - + Archive Viper 2525 - + The boot message identifier for this drive is ARCHIVE VIPER 2525 25462 -011 type 1 removable SCSI 1 - + This is a QIC tape drive. - + Native capacity is 525MB. - + Data transfer rate is 180kB/s at 90 inches/sec. - + The drive reads QIC-525, QIC-150, QIC-120 and QIC-24 tapes. Writes QIC-525, QIC-150, and QIC-120. - + Firmware revisions prior to 25462 -011 are bug ridden and will not function properly. - + Production of this drive has been discontinued. Conner 420R - + The boot message identifier for this drive is Conner tape. - + This is a floppy controller, mini cartridge tape drive. - + Native capacity is XXXX - + Data transfer rate is XXX - + The drive uses QIC-80 tape cartridges. - + Reported by: Mark Hannon mark@seeware.DIALix.oz.au Conner CTMS 3200 - + The boot message identifier for this drive is CONNER CTMS 3200 7.00 type 1 removable SCSI 2. - + This is a mini cartridge tape drive. - + Native capacity is XXXX - + Data transfer rate is XXX - + The drive uses QIC-3080 tape cartridges. - + Reported by: Thomas S. Traylor tst@titan.cs.mci.com @@ -2057,156 +2057,156 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue <ulink url="http://www.digital.com/info/Customer-Update/931206004.txt.html">DEC TZ87</ulink> - + The boot message identifier for this drive is DEC TZ87 (C) DEC 9206 type 1 removable SCSI 2 density code 0x19 - + This is a DLT tape drive. - + Native capacity is 10GB. - + This drive supports hardware data compression. - + Data transfer rate is 1.2MB/s. - + This drive is identical to the Quantum DLT2000. The drive firmware can be set to emulate several well-known drives, including an Exabyte 8mm drive. - + Reported by: &a.wilko; <ulink url="http://www.Exabyte.COM:80/Products/Minicartridge/2501/Rfeatures.html">Exabyte EXB-2501</ulink> - + The boot message identifier for this drive is EXABYTE EXB-2501 - + This is a mini-cartridge tape drive. - + Native capacity is 1GB when using MC3000XL mini cartridges. - + Data transfer rate is XXX - + This drive can read and write DC2300 (550MB), DC2750 (750MB), MC3000 (750MB), and MC3000XL (1GB) mini cartridges. - + WARNING: This drive does not meet the SCSI-2 specifications. The drive locks up completely in response to a SCSI MODE_SELECT command unless there is a formatted tape in the drive. Before using this drive, set the tape blocksize with - + &prompt.root; mt -f /dev/st0ctl.0 blocksize 1024 - + Before using a mini cartridge for the first time, the mini cartridge must be formatted. FreeBSD 2.1.0-RELEASE and earlier: - + &prompt.root; /sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0" - + (Alternatively, fetch a copy of the scsiformat shell script from FreeBSD 2.1.5/2.2.) FreeBSD 2.1.5 and later: - + &prompt.root; /sbin/scsiformat -q -w /dev/rst0.ctl - + Right now, this drive cannot really be recommended for FreeBSD. - + Reported by: Bob Beaulieu ez@eztravel.com Exabyte EXB-8200 - + The boot message identifier for this drive is EXABYTE EXB-8200 252X type 1 removable SCSI 1 - + This is an 8mm tape drive. - + Native capacity is 2.3GB. - + Data transfer rate is 270kB/s. - + This drive is fairly slow in responding to the SCSI bus during boot. A custom kernel may be required (set SCSI_DELAY to 10 seconds). - + There are a large number of firmware configurations for this drive, some have been customized to a particular vendor's hardware. The firmware can be changed via EPROM replacement. - + Production of this drive has been discontinued. - + Reported by: &a.msmith; Exabyte EXB-8500 - + The boot message identifier for this drive is EXABYTE EXB-8500-85Qanx0 0415 type 1 removable SCSI 2 - + This is an 8mm tape drive. - + Native capacity is 5GB. - + Data transfer rate is 300kB/s. - + Reported by: Greg Lehey grog@lemis.de <ulink url="http://www.Exabyte.COM:80/Products/8mm/8505XL/Rfeatures.html">Exabyte EXB-8505</ulink> - + The boot message identifier for this drive is EXABYTE EXB-85058SQANXR1 05B0 type 1 removable SCSI 2 - + This is an 8mm tape drive which supports compression, and is upward compatible with the EXB-5200 and EXB-8500. - + Native capacity is 5GB. - + The drive supports hardware data compression. - + Data transfer rate is 300kB/s. - + Reported by: Glen Foster gfoster@gfoster.com Hewlett-Packard HP C1533A - + The boot message identifier for this drive is HP C1533A 9503 type 1 removable SCSI 2. - + This is a DDS-2 tape drive. DDS-2 means hardware data compression and narrower tracks for increased data capacity. - + Native capacity is 4GB when using 120m tapes. This drive supports hardware data compression. - + Data transfer rate is 510kB/s. - + This drive is used in Hewlett-Packard's SureStore 6000eU and 6000i tape drives and C1533A DDS-2 DAT drive. - + The drive has a block of 8 dip switches. The proper settings for FreeBSD are: 1 ON; 2 ON; 3 OFF; 4 ON; 5 ON; 6 ON; 7 ON; 8 ON. - + @@ -2216,7 +2216,7 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Result - + On @@ -2224,21 +2224,21 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue Compression enabled at power-on, with host control - + On Off Compression enabled at power-on, no host control - + Off On Compression disabled at power-on, with host control - + Off Off @@ -2248,46 +2248,46 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue - + Switch 3 controls MRS (Media Recognition System). MRS tapes have stripes on the transparent leader. These identify the tape as DDS (Digital Data Storage) grade media. Tapes that do not have the stripes will be treated as write-protected. Switch 3 OFF enables MRS. Switch 3 ON disables MRS. - + See HP SureStore Tape Products and Hewlett-Packard Disk and Tape Technical Information for more information on configuring this drive. - + Warning: Quality control on these drives varies greatly. One FreeBSD core-team member has returned 2 of these drives. Neither lasted more than 5 months. - + Reported by: &a.se; Hewlett-Packard HP 1534A - + The boot message identifier for this drive is HP HP35470A T503 type 1 removable SCSI 2 Sequential-Access density code 0x13, variable blocks. - + This is a DDS-1 tape drive. DDS-1 is the original DAT tape format. - + Native capacity is 2GB when using 90m tapes. - + Data transfer rate is 183kB/s. - + The same mechanism is used in Hewlett-Packard's SureStore 2000i tape drive, C35470A DDS format DAT drive, C1534A DDS format DAT drive and HP C1536A DDS format DAT drive. - + The HP C1534A DDS format DAT drive has two indicator lights, one green and one amber. The green one indicates tape action: slow flash during load, steady when loaded, fast flash during @@ -2295,40 +2295,40 @@ Mar 29 21:16:37 yedi /kernel: sa1: Archive Viper 150 is a known rogue flash when cleaning is required or tape is nearing the end of its useful life, steady indicates an hard fault. (factory service required?) - + Reported by Gary Crutcher gcrutchr@nightflight.com Hewlett-Packard HP C1553A Autoloading DDS2 - + The boot message identifier for this drive is "". - + This is a DDS-2 tape drive with a tape changer. DDS-2 means hardware data compression and narrower tracks for increased data capacity. - + Native capacity is 24GB when using 120m tapes. This drive supports hardware data compression. - + Data transfer rate is 510kB/s (native). - + This drive is used in Hewlett-Packard's SureStore 12000e tape drive. - + The drive has two selectors on the rear panel. The selector closer to the fan is SCSI id. The other selector should be set to 7. - + There are four internal switches. These should be set: 1 ON; 2 ON; 3 ON; 4 OFF. - + At present the kernel drivers do not automatically change tapes at the end of a volume. This shell script can be used to change tapes: - + #!/bin/sh PATH="/sbin:/usr/sbin:/bin:/usr/bin"; export PATH @@ -2369,80 +2369,80 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Hewlett-Packard HP 35450A - + The boot message identifier for this drive is HP HP35450A -A C620 type 1 removable SCSI 2 Sequential-Access density code 0x13 - + This is a DDS-1 tape drive. DDS-1 is the original DAT tape format. - + Native capacity is 1.2GB. - + Data transfer rate is 160kB/s. - + Reported by: Mark Thompson mark.a.thompson@pobox.com Hewlett-Packard HP 35470A - + The boot message identifier for this drive is HP HP35470A 9 09 type 1 removable SCSI 2 - + This is a DDS-1 tape drive. DDS-1 is the original DAT tape format. - + Native capacity is 2GB when using 90m tapes. - + Data transfer rate is 183kB/s. - + The same mechanism is used in Hewlett-Packard's SureStore 2000i tape drive, C35470A DDS format DAT drive, C1534A DDS format DAT drive, and HP C1536A DDS format DAT drive. - + Warning: Quality control on these drives varies greatly. One FreeBSD core-team member has returned 5 of these drives. None lasted more than 9 months. - + Reported by: David Dawes dawes@rf900.physics.usyd.edu.au (9 09) - + Hewlett-Packard HP 35480A - + The boot message identifier for this drive is HP HP35480A 1009 type 1 removable SCSI 2 Sequential-Access density code 0x13. - + This is a DDS-DC tape drive. DDS-DC is DDS-1 with hardware data compression. DDS-1 is the original DAT tape format. - + Native capacity is 2GB when using 90m tapes. It cannot handle 120m tapes. This drive supports hardware data compression. Please refer to the section on HP C1533A for the proper switch settings. - + Data transfer rate is 183kB/s. - + This drive is used in Hewlett-Packard's SureStore 5000eU and 5000i tape drives and C35480A DDS format DAT drive.. - + This drive will occasionally hang during a tape eject operation (mt offline). Pressing the front panel button will eject the tape and bring the tape drive back to life. - + WARNING: HP 35480-03110 only. On at least two occasions this tape drive when used with FreeBSD 2.1.0, an IBM Server 320 and an 2940W SCSI controller resulted in all SCSI disk partitions being @@ -2453,68 +2453,68 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" <ulink url="http://www.sel.sony.com/SEL/ccpg/storage/tape/t5000.html">Sony SDT-5000</ulink> - + There are at least two significantly different models: one is a DDS-1 and the other DDS-2. The DDS-1 version is SDT-5000 3.02. The DDS-2 version is SONY SDT-5000 327M. The DDS-2 version has a 1MB cache. This cache is able to keep the tape streaming in almost any circumstances. - + The boot message identifier for this drive is SONY SDT-5000 3.02 type 1 removable SCSI 2 Sequential-Access density code 0x13 - + Native capacity is 4GB when using 120m tapes. This drive supports hardware data compression. - + Data transfer rate is depends upon the model or the drive. The rate is 630kB/s for the SONY SDT-5000 327M while compressing the data. For the SONY SDT-5000 3.02, the data transfer rate is 225kB/s. - + In order to get this drive to stream, set the blocksize to 512 bytes (mt blocksize 512) reported by Kenneth Merry ken@ulc199.residence.gatech.edu. - + SONY SDT-5000 327M information reported by Charles Henrich henrich@msu.edu. - + Reported by: &a.jmz; Tandberg TDC 3600 - + The boot message identifier for this drive is TANDBERG TDC 3600 =08: type 1 removable SCSI 2 - + This is a QIC tape drive. - + Native capacity is 150/250MB. - + This drive has quirks which are known and work around code is present in the SCSI tape device driver (&man.st.4;). Upgrading the firmware to XXX version will fix the quirks and provide SCSI 2 capabilities. - + Data transfer rate is 80kB/s. - + IBM and Emerald units will not work. Replacing the firmware EPROM of these units will solve the problem. - + Reported by: &a.msmith; Tandberg TDC 3620 - + This is very similar to the Tandberg TDC 3600 drive. - + Reported by: &a.joerg; @@ -2524,56 +2524,56 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" The boot message identifier for this drive is TANDBERG TDC 3800 =04Y Removable Sequential Access SCSI-2 device - + This is a QIC tape drive. - + Native capacity is 525MB. - + Reported by: &a.jhs; Tandberg TDC 4222 - + The boot message identifier for this drive is TANDBERG TDC 4222 =07 type 1 removable SCSI 2 - + This is a QIC tape drive. - + Native capacity is 2.5GB. The drive will read all cartridges from the 60 MB (DC600A) upwards, and write 150 MB (DC6150) upwards. Hardware compression is optionally supported for the 2.5 GB cartridges. - + This drives quirks are known and pre-compiled into the SCSI tape device driver (&man.st.4;) beginning with FreeBSD 2.2-CURRENT. For previous versions of FreeBSD, use mt to read one block from the tape, rewind the tape, and then execute the backup program (mt fsr 1; mt rewind; dump ...) - + Data transfer rate is 600kB/s (vendor claim with compression), 350 KB/s can even be reached in start/stop mode. The rate decreases for smaller cartridges. - + Reported by: &a.joerg; Wangtek 5525ES - + The boot message identifier for this drive is WANGTEK 5525ES SCSI REV7 3R1 type 1 removable SCSI 1 density code 0x11, 1024-byte blocks - + This is a QIC tape drive. - + Native capacity is 525MB. - + Data transfer rate is 180kB/s. - + The drive reads 60, 120, 150, and 525MB tapes. The drive will not write 60MB (DC600 cartridge) tapes. In order to overwrite 120 and 150 tapes reliably, first erase (mt erase) @@ -2582,13 +2582,13 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" previous tracks is not overwritten, as a result the new data lies in a band surrounded on both sides by the previous data unless the tape have been erased. - + This drives quirks are known and pre-compiled into the SCSI tape device driver (&man.st.4;). - + Other firmware revisions that are known to work are: M75D - + Reported by: Marc van Kempen marc@bowtie.nl REV73R1 Andrew Gordon Andrew.Gordon@net-tel.co.uk @@ -2597,35 +2597,35 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" Wangtek 6200 - + The boot message identifier for this drive is WANGTEK 6200-HS 4B18 type 1 removable SCSI 2 Sequential-Access density code 0x13 - + This is a DDS-1 tape drive. - + Native capacity is 2GB using 90m tapes. - + Data transfer rate is 150kB/s. - + Reported by: Tony Kimball alk@Think.COM - + * Problem drives - + CDROM drives - + Contributed by &a.obrien;. 23 November 1997. - + Generally speaking those in The FreeBSD Project prefer SCSI CDROM drives over IDE CDROM drives. However not all SCSI CDROM drives are equal. Some @@ -2635,7 +2635,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5" found displeasure with the 12x speed XM-5701TA as its volume (when playing audio CDROMs) is not controllable by the various audio player software. - + Another area where SCSI CDROM manufacturers are cutting corners is adherence to the SCSI specification. Many SCSI CDROMs will respond to Choosing the FreeBSD Version That Is Right For You - + The FreeBSD Documentation Project - + &tm-attrib.freebsd; - + 2005 The FreeBSD Documentation Project @@ -28,7 +28,7 @@ $FreeBSD$ $FreeBSD$ - + So you have chosen to install &os;. Welcome! This document is designed to help you to decide which version to diff --git a/en_US.ISO8859-1/articles/vinum/article.sgml b/en_US.ISO8859-1/articles/vinum/article.sgml index 118e9a9af4..f3905df3e9 100644 --- a/en_US.ISO8859-1/articles/vinum/article.sgml +++ b/en_US.ISO8859-1/articles/vinum/article.sgml @@ -552,7 +552,7 @@ performance disk server at a very reasonable cost. However, you can indeed get started with - Vinum very simply. + Vinum very simply. A minimum system can be as simple as an old CPU (even a 486 is fine) and a pair of drives that are 500 MB or more. They need not be the same size or @@ -594,7 +594,7 @@ for the server against available resources and make design tradeoffs. We will plan the transition from no - Vinum to + Vinum to Vinum on just one spindle, to Vinum on two spindles. @@ -1075,7 +1075,7 @@ Not to scale allocations as described above in . For this example on a 2 GB spindle, I will use 200,000 blocks for root, 200,265 blocks for swap, - 1,000,000 blocks for /home, and + 1,000,000 blocks for /home, and the rest of the spindle (2,724,408 blocks) for /usr. (/stand/sysinstall @@ -1239,7 +1239,7 @@ Not to scale We now need to install new spindle partitioning for /dev/ad0. - This requires that + This requires that /dev/ad0s1b not be in use for swapping so we have to reboot in single-user mode. @@ -1575,7 +1575,7 @@ expected next file 492, got 491 Vinum may automatically avoid failed hardware in a way that users do not notice. - You must watch for such failures and get them repaired before a + You must watch for such failures and get them repaired before a second failure results in data loss. You may see Vinum noting damaged objects @@ -1610,7 +1610,7 @@ expected next file 492, got 491 sd name hope.p0.s0 drive UpWindow plex hope.p0 len 0 - Specifying a length of 0 for + Specifying a length of 0 for the hope.p0.s0 subdisk asks Vinum to use whatever space is left available on the underlying @@ -1672,7 +1672,7 @@ expected next file 492, got 491 For each scenario, there is a subsection on how to configure your server for degraded mode operation, how to recover from the failure, how to exit degraded mode, and how to simulate the failure. - + Make a hard copy of these instructions and leave them inside the CPU case, being careful not to interfere with ventilation. @@ -1812,7 +1812,7 @@ ok boot -as Simulation This kind of failure can be simulated by shutting down to - single-user mode and then booting as shown above in + single-user mode and then booting as shown above in . @@ -1876,7 +1876,7 @@ ok boot -s We assume here that your server is up and running multi-user in - degraded mode on just + degraded mode on just /dev/ad0 and that you have a new spindle now on /dev/ad2 ready to go. @@ -2096,7 +2096,7 @@ use strict; use FileHandle; my $config_tag1 = '$Id: article.sgml,v 1.17 2012-03-20 08:56:30 pluknet Exp $'; -# Copyright (C) 2001 Robert A. Van Valzah +# Copyright (C) 2001 Robert A. Van Valzah # # Bootstrap Vinum # diff --git a/en_US.ISO8859-1/articles/vm-design/article.sgml b/en_US.ISO8859-1/articles/vm-design/article.sgml index 2f2ed46c84..9d64b3cd05 100644 --- a/en_US.ISO8859-1/articles/vm-design/article.sgml +++ b/en_US.ISO8859-1/articles/vm-design/article.sgml @@ -56,7 +56,7 @@ - This article was originally published in the January 2000 issue of + This article was originally published in the January 2000 issue of DaemonNews. This version of the article may include updates from Matt and other authors to reflect changes in &os;'s VM implementation. @@ -190,7 +190,7 @@ - + +---------------+ | A | @@ -215,7 +215,7 @@ +---------------+ -| B | +| B | +---------------+ | A | +---------------+ @@ -232,7 +232,7 @@ - + +-------+-------+ | C1 | C2 | @@ -337,7 +337,7 @@ However, the swap management structure has had problems historically: - + Under &os; 3.X the swap management structure preallocates an array that encompasses the entire object requiring swap backing @@ -365,7 +365,7 @@ The problem is further exacerbated by holes created due to the interleaving algorithm. - + Also, the swap block map can become fragmented fairly easily resulting in non-contiguous allocations. diff --git a/en_US.ISO8859-1/articles/wp-toolbox/Makefile b/en_US.ISO8859-1/articles/wp-toolbox/Makefile index d19a1dc514..efcf23ead2 100644 --- a/en_US.ISO8859-1/articles/wp-toolbox/Makefile +++ b/en_US.ISO8859-1/articles/wp-toolbox/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Article: Casestudy about FreeBSD as a Software Testing Toolbox diff --git a/en_US.ISO8859-1/books/Makefile.inc b/en_US.ISO8859-1/books/Makefile.inc index 3c93e4c451..2bcfd06112 100644 --- a/en_US.ISO8859-1/books/Makefile.inc +++ b/en_US.ISO8859-1/books/Makefile.inc @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # diff --git a/en_US.ISO8859-1/books/arch-handbook/Makefile b/en_US.ISO8859-1/books/arch-handbook/Makefile index c9c829547e..5a10c604cd 100644 --- a/en_US.ISO8859-1/books/arch-handbook/Makefile +++ b/en_US.ISO8859-1/books/arch-handbook/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Build the FreeBSD Architecture Handbook. @@ -15,7 +15,7 @@ HAS_INDEX= true INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # diff --git a/en_US.ISO8859-1/books/arch-handbook/book.sgml b/en_US.ISO8859-1/books/arch-handbook/book.sgml index e705fcef69..84b9abf00f 100644 --- a/en_US.ISO8859-1/books/arch-handbook/book.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/book.sgml @@ -18,11 +18,11 @@ &os; Architecture Handbook - + The FreeBSD Documentation Project - + August 2000 - + 2000 2001 @@ -38,7 +38,7 @@ &legalnotice; $FreeBSD$ - + Welcome to the &os; Architecture Handbook. This manual is a work in progress and is the work of many @@ -70,7 +70,7 @@ &chap.smp; - + Device Drivers @@ -85,7 +85,7 @@ &chap.pccard; - + diff --git a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.sgml index dad882a6a0..3eed9ff2cd 100644 --- a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.sgml @@ -56,13 +56,13 @@ associated device driver. Most device nodes on the system are created by running MAKEDEV. - Device drivers can roughly be broken down into two + Device drivers can roughly be broken down into two categories; character and network device drivers. - Dynamic Kernel Linker Facility - KLD + Dynamic Kernel Linker Facility - KLD kernel linkingdynamic kernel loadable modules (KLD) @@ -99,12 +99,12 @@ #include <sys/types.h> #include <sys/module.h> -#include <sys/systm.h> /* uprintf */ +#include <sys/systm.h> /* uprintf */ #include <sys/errno.h> #include <sys/param.h> /* defines used in kernel.h */ #include <sys/kernel.h> /* types used in module initialization */ -/* +/* * Load handler that deals with the loading and unloading of a KLD. */ @@ -112,7 +112,7 @@ static int skel_loader(struct module *m, int what, void *arg) { int err = 0; - + switch (what) { case MOD_LOAD: /* kldload */ uprintf("Skeleton KLD loaded.\n"); @@ -133,7 +133,7 @@ static moduledata_t skel_mod = { "skel", skel_loader, NULL -}; +}; DECLARE_MODULE(skeleton, skel_mod, SI_SUB_KLD, SI_ORDER_ANY); @@ -595,7 +595,7 @@ Test Data to be accessed. Their selection is based on other decisions made inside the kernel and instead of calling open(), use of a network device is generally introduced by using the system call - socket(2). + socket(2). For more information see ifnet(9), the source of the loopback device, and Bill Paul's network drivers. diff --git a/en_US.ISO8859-1/books/arch-handbook/isa/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/isa/chapter.sgml index 9357468fda..e4cd99da08 100644 --- a/en_US.ISO8859-1/books/arch-handbook/isa/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/isa/chapter.sgml @@ -1032,7 +1032,7 @@ Free the memory allocated by - bus_dmamem_alloc(). At present, + bus_dmamem_alloc(). At present, freeing of the memory allocated with ISA restrictions is not implemented. Because of this the recommended model of use is to keep and re-use the allocated areas for as @@ -1889,7 +1889,7 @@ possible ports, like this: - + /* table of all possible base I/O port addresses for this device */ static struct xxx_allports { u_short port; /* port address */ @@ -1956,9 +1956,9 @@ have this information in the configuration file. - + if(pnperror /* only for non-PnP devices */ - && bus_set_resource(dev, SYS_RES_IOPORT, 0, sc->port0, + && bus_set_resource(dev, SYS_RES_IOPORT, 0, sc->port0, XXX_PORT_COUNT)<0) return ENXIO; @@ -1970,7 +1970,7 @@ sc->port0_rid = 0; - sc->port0_r = bus_alloc_resource(dev, SYS_RES_IOPORT, + sc->port0_r = bus_alloc_resource(dev, SYS_RES_IOPORT, &sc->port0_rid, /*start*/ 0, /*end*/ ~0, /*count*/ 0, RF_ACTIVE); @@ -2005,7 +2005,7 @@ interrupts too. But that is not recommended. - + /* implemented in some very device-specific way */ if(error = xxx_probe_ports(sc)) goto bad; /* will deallocate the resources before returning */ @@ -2046,7 +2046,7 @@ they are doing and this one should take precedence. An example of implementation could be: - + /* try to find out the config address first */ sc->mem0_p = bus_get_resource_start(dev, SYS_RES_MEMORY, 0 /*rid*/); if(sc->mem0_p == 0) { /* nope, not specified by user */ diff --git a/en_US.ISO8859-1/books/arch-handbook/jail/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/jail/chapter.sgml index 4f4e567c30..d64af98185 100644 --- a/en_US.ISO8859-1/books/arch-handbook/jail/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/jail/chapter.sgml @@ -85,7 +85,7 @@ The definition of the jail structure is: -/usr/include/sys/jail.h: +/usr/include/sys/jail.h: struct jail { u_int32_t version; @@ -122,8 +122,8 @@ j.hostname = argv[1]; j (the jail structure). /usr/src/usr.sbin/jail/jail.c: -struct in_addr in; -... +struct in_addr in; +... if (inet_aton(argv[2], &in) == 0) errx(1, "Could not make sense of ip-number: %s", argv[2]); j.ip_number = ntohl(in.s_addr); @@ -146,8 +146,8 @@ j.ip_number = ntohl(in.s_addr); process itself and then executes the command given using &man.execv.3;. /usr/src/usr.sbin/jail/jail.c -i = jail(&j); -... +i = jail(&j); +... if (execv(argv[3], argv + 3) != 0) err(1, "execv: %s", argv[3]); @@ -243,8 +243,8 @@ SYSCTL_INT(_security_jail, OID_AUTO, mount_allowed, CTLFLAG_RW, * struct jail_args { * struct jail *jail; * }; - */ -int + */ +int jail(struct thread *td, struct jail_args *uap) Therefore, uap->jail can be used to @@ -345,9 +345,9 @@ struct thread { struct proc *td_proc; ... }; -struct proc { +struct proc { ... - struct ucred *p_ucred; + struct ucred *p_ucred; ... }; /usr/include/sys/ucred.h @@ -443,7 +443,7 @@ if (jailed(td->td_ucred)) System V IPC is based on messages. Processes can send each other these messages which tell them how to act. The functions - which deal with messages are: + which deal with messages are: &man.msgctl.3;, &man.msgget.3;, &man.msgsnd.3; and &man.msgrcv.3;. Earlier, I mentioned that there were certain sysctls you could turn on or off in order to affect the behavior of @@ -620,7 +620,7 @@ socreate(int dom, struct socket **aso, int type, int proto, that doesn't belong to the jail in which the calling process exists. - /usr/src/sys/netinet/in_pcb.c: + /usr/src/sys/netinet/in_pcb.c: int in_pcbbind_setup(struct inpcb *inp, struct sockaddr *nam, in_addr_t *laddrp, u_short *lportp, struct ucred *cred) diff --git a/en_US.ISO8859-1/books/arch-handbook/locking/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/locking/chapter.sgml index 34e07a0f2c..4e80544ad3 100644 --- a/en_US.ISO8859-1/books/arch-handbook/locking/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/locking/chapter.sgml @@ -38,7 +38,7 @@ to be held for a short period of time. Specifically, one may not sleep while holding a mutex. If you need to hold a lock across a sleep, use a &man.lockmgr.9; lock. - + Each mutex has several properties of interest: @@ -116,16 +116,16 @@ Mutex List locks - sched_lock + sched_lock locks - vm86pcb_lock + vm86pcb_lock locks - Giant + Giant locks - callout_lock + callout_lock @@ -137,7 +137,7 @@ Dependent Functions - + @@ -278,14 +278,14 @@ and may be held by a sleeping process. Currently they are backed by &man.lockmgr.9;. locks - shared exclusive + shared exclusive Shared Exclusive Lock Listlocks - allproc_lock + allproc_locklocks - proctree_lock + proctree_lock diff --git a/en_US.ISO8859-1/books/arch-handbook/mac/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/mac/chapter.sgml index 53b15eb5ea..80f6b8c453 100644 --- a/en_US.ISO8859-1/books/arch-handbook/mac/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/mac/chapter.sgml @@ -2,13 +2,13 @@ @@ -39,17 +39,17 @@ Chris Costello - + TrustedBSD Project
chris@FreeBSD.org
 - + Robert Watson - + TrustedBSD Project
rwatson@FreeBSD.org
@@ -57,7 +57,7 @@ - + The TrustedBSD MAC Framework @@ -109,10 +109,10 @@ IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - + Synopsis - + FreeBSD includes experimental support for several mandatory access control policies, as well as a framework for kernel security extensibility, the TrustedBSD MAC @@ -127,11 +127,11 @@ This chapter introduces the MAC policy framework and provides documentation for a sample MAC policy module. - - + + Introduction - + The TrustedBSD MAC framework provides a mechanism to allow the compile-time or run-time extension of the kernel access control model. New system policies may be implemented as @@ -179,10 +179,10 @@ discretionary policies, as policy modules are given substantial flexibility in how they authorize protections. - + MAC Framework Kernel Architecture - + The TrustedBSD MAC Framework permits kernel modules to extend the operating system security policy, as well as providing infrastructure functionality required by many @@ -198,7 +198,7 @@ Framework management interfaces - Concurrency and synchronization + Concurrency and synchronization primitives. Policy registration Extensible security label for kernel @@ -620,7 +620,7 @@ Policy Declaration - + Modules may be declared using the MAC_POLICY_SET() macro, which names the policy, provides a reference to the MAC entry point vector, @@ -629,17 +629,17 @@ allocation of label state by the framework. static struct mac_policy_ops mac_policy_ops = -{ +{ .mpo_destroy = mac_policy_destroy, .mpo_init = mac_policy_init, - .mpo_init_bpfdesc_label = mac_policy_init_bpfdesc_label, + .mpo_init_bpfdesc_label = mac_policy_init_bpfdesc_label, .mpo_init_cred_label = mac_policy_init_label, /* ... */ .mpo_check_vnode_setutimes = mac_policy_check_vnode_setutimes, .mpo_check_vnode_stat = mac_policy_check_vnode_stat, .mpo_check_vnode_write = mac_policy_check_vnode_write, }; - + The MAC policy entry point vector, mac_policy_ops in this example, associates functions defined in the module with specific entry points. A @@ -660,7 +660,7 @@ be changed, but in the mean time, policies should be careful about what kernel primitives they invoke so as to avoid lock ordering or sleeping problems. - + The policy declaration's module name field exists so that the module may be uniquely identified for the purposes of module dependencies. An appropriate string should be selected. @@ -672,12 +672,12 @@ Policy Flags - + The policy declaration flags field permits the module to provide the framework with information about its capabilities at the time the module is loaded. Currently, three flags are defined: - + MPC_LOADTIME_FLAG_UNLOADOK @@ -691,10 +691,10 @@ runtime. - + MPC_LOADTIME_FLAG_NOTLATE - + This flag indicates that the policy module must be loaded and initialized early in the boot @@ -724,7 +724,7 @@ - + Policies using the MPC_LOADTIME_FLAG_LABELMBUFS without the MPC_LOADTIME_FLAG_NOTLATE flag set @@ -739,7 +739,7 @@ Policy Entry Points - + Four classes of entry points are offered to policies registered with the framework: entry points associated with the registration and management of policies, entry points @@ -750,7 +750,7 @@ addition, a mac_syscall() entry point is provided so that policies may extend the kernel interface without registering new system calls. - + Policy module writers should be aware of the kernel locking strategy, as well as what object locks are available during which entry points. Writers should attempt to avoid @@ -762,7 +762,7 @@ object or its label may not be present for all entry points. Locking information for arguments is documented in the MAC framework entry point document. - + Policy entry points will pass a reference to the object label along with the object itself. This permits labeled policies to be unaware of the internals of the object yet @@ -774,27 +774,27 @@ MAC Policy Entry Point Reference - + General-Purpose Module Entry Points - + <function>&mac.mpo;_init</function> - + void &mac.mpo;_init - + struct mac_policy_conf *conf - + &mac.thead; - + conf @@ -803,7 +803,7 @@ - + Policy load event. The policy list mutex is held, so sleep operations cannot be performed, and calls out to other kernel subsystems must be made with caution. If potentially @@ -811,24 +811,24 @@ initialization, they should be made using a separate module SYSINIT(). - + <function>&mac.mpo;_destroy</function> - + void &mac.mpo;_destroy - + struct mac_policy_conf *conf - + &mac.thead; - + conf @@ -837,7 +837,7 @@ - + Policy load event. The policy list mutex is held, so caution should be applied. @@ -897,7 +897,7 @@ copyin() of the syscall data on their own. - + <function>&mac.mpo;_thread_userret</function> @@ -953,21 +953,21 @@ <function>&mac.mpo;_init_bpfdesc_label</function> - + void &mac.mpo;_init_bpfdesc_label - + struct label *label - + &mac.thead; - + label @@ -976,28 +976,28 @@ - + Initialize the label on a newly instantiated bpfdesc (BPF descriptor). Sleeping is permitted. <function>&mac.mpo;_init_cred_label</function> - + void &mac.mpo;_init_cred_label - + struct label *label - + &mac.thead; - + label @@ -1006,28 +1006,28 @@ - + Initialize the label for a newly instantiated user credential. Sleeping is permitted. <function>&mac.mpo;_init_devfsdirent_label</function> - + void &mac.mpo;_init_devfsdirent_label - + struct label *label - + &mac.thead; - + label @@ -1036,28 +1036,28 @@ - + Initialize the label on a newly instantiated devfs entry. Sleeping is permitted. <function>&mac.mpo;_init_ifnet_label</function> - + void &mac.mpo;_init_ifnet_label - + struct label *label - + &mac.thead; - + label @@ -1066,29 +1066,29 @@ - + Initialize the label on a newly instantiated network interface. Sleeping is permitted. - + <function>&mac.mpo;_init_ipq_label</function> - + void &mac.mpo;_init_ipq_label - + struct label *label int flag - + &mac.thead; - + label @@ -1103,7 +1103,7 @@ - + Initialize the label on a newly instantiated IP fragment reassembly queue. The flag field may be one of M_WAITOK and M_NOWAIT, @@ -1118,29 +1118,29 @@ <function>&mac.mpo;_init_mbuf_label</function> - + void &mac.mpo;_init_mbuf_label - + int flag struct label *label - + &mac.thead; - + flag Sleeping/non-sleeping &man.malloc.9;; see below - + label Policy label to initialize @@ -1148,7 +1148,7 @@ - + Initialize the label on a newly instantiated mbuf packet header (mbuf). The flag field may be one of @@ -1161,34 +1161,34 @@ is permitted to fail resulting in the failure to allocate the mbuf header. - + <function>&mac.mpo;_init_mount_label</function> - + void &mac.mpo;_init_mount_label - + struct label *mntlabel struct label *fslabel - + &mac.thead; - + mntlabel Policy label to be initialized for the mount itself - + fslabel Policy label to be initialized for the file @@ -1197,7 +1197,7 @@ - + Initialize the labels on a newly instantiated mount point. Sleeping is permitted. @@ -1261,31 +1261,31 @@ Initialize a label for a newly instantiated pipe. Sleeping is permitted. - + <function>&mac.mpo;_init_socket_label</function> - + void &mac.mpo;_init_socket_label - + struct label *label int flag - + &mac.thead; - + label New label to initialize - + flag &man.malloc.9; flags @@ -1293,9 +1293,9 @@ - + Initialize a label for a newly instantiated - socket. The flag field may be one of + socket. The flag field may be one of M_WAITOK and M_NOWAIT, and should be employed to avoid performing a sleeping &man.malloc.9; during this initialization call. @@ -1334,29 +1334,29 @@ Initialize the peer label for a newly instantiated - socket. The flag field may be one of + socket. The flag field may be one of M_WAITOK and M_NOWAIT, and should be employed to avoid performing a sleeping &man.malloc.9; during this initialization call. - + <function>&mac.mpo;_init_proc_label</function> - + void &mac.mpo;_init_proc_label - + struct label *label - + &mac.thead; - + label @@ -1365,7 +1365,7 @@ - + Initialize the label for a newly instantiated process. Sleeping is permitted. @@ -1373,21 +1373,21 @@ <function>&mac.mpo;_init_vnode_label</function> - + void &mac.mpo;_init_vnode_label - + struct label *label - + &mac.thead; - + label @@ -1396,7 +1396,7 @@ - + Initialize the label on a newly instantiated vnode. Sleeping is permitted. @@ -1431,24 +1431,24 @@ with label so that it may be destroyed. - + <function>&mac.mpo;_destroy_cred_label</function> - + void &mac.mpo;_destroy_cred_label - + struct label *label - + &mac.thead; - + label @@ -1457,7 +1457,7 @@ - + Destroy the label on a credential. In this entry point, a policy module should free any internal storage associated with label so that it may be @@ -1467,21 +1467,21 @@ <function>&mac.mpo;_destroy_devfsdirent_label</function> - + void &mac.mpo;_destroy_devfsdirent_label - + struct label *label - + &mac.thead; - + label @@ -1490,30 +1490,30 @@ - + Destroy the label on a devfs entry. In this entry point, a policy module should free any internal storage associated with label so that it may be destroyed. - + <function>&mac.mpo;_destroy_ifnet_label</function> - + void &mac.mpo;_destroy_ifnet_label - + struct label *label - + &mac.thead; - + label @@ -1522,26 +1522,26 @@ - + Destroy the label on a removed interface. In this entry point, a policy module should free any internal storage associated with label so that it may be destroyed. - + <function>&mac.mpo;_destroy_ipq_label</function> - + void &mac.mpo;_destroy_ipq_label - + struct label *label - + &mac.thead; @@ -1554,30 +1554,30 @@ - + Destroy the label on an IP fragment queue. In this entry point, a policy module should free any internal storage associated with label so that it may be destroyed. - + <function>&mac.mpo;_destroy_mbuf_label</function> - + void &mac.mpo;_destroy_mbuf_label - + struct label *label - + &mac.thead; - + label @@ -1586,30 +1586,30 @@ - + Destroy the label on an mbuf header. In this entry point, a policy module should free any internal storage associated with label so that it may be destroyed. - + <function>&mac.mpo;_destroy_mount_label</function> - + void &mac.mpo;_destroy_mount_label - + struct label *label - + &mac.thead; - + label @@ -1618,7 +1618,7 @@ - + Destroy the labels on a mount point. In this entry point, a policy module should free the internal storage associated with mntlabel so that they @@ -1627,29 +1627,29 @@ <function>&mac.mpo;_destroy_mount_label</function> - + void &mac.mpo;_destroy_mount_label - + struct label *mntlabel struct label *fslabel - + &mac.thead; - + mntlabel Mount point label being destroyed - + fslabel File system label being destroyed> @@ -1657,28 +1657,28 @@ - + Destroy the labels on a mount point. In this entry point, a policy module should free the internal storage associated with mntlabel and fslabel so that they may be destroyed. - + <function>&mac.mpo;_destroy_socket_label</function> - + void &mac.mpo;_destroy_socket_label - + struct label *label - + &mac.thead; @@ -1692,7 +1692,7 @@ - + Destroy the label on a socket. In this entry point, a policy module should free any internal storage associated with label so that it may be @@ -1827,29 +1827,29 @@ <function>&mac.mpo;_copy_mbuf_label</function> - + void &mac.mpo;_copy_mbuf_label - + struct label *src struct label *dest - + &mac.thead; - + src Source label - + dest Destination label @@ -1857,7 +1857,7 @@ - + Copy the label information in src into dest. @@ -1865,29 +1865,29 @@ <function>&mac.mpo;_copy_pipe_label</function> - + void &mac.mpo;_copy_pipe_label - + struct label *src struct label *dest - + &mac.thead; - + src Source label - + dest Destination label @@ -1895,7 +1895,7 @@ - + Copy the label information in src into dest. @@ -1903,29 +1903,29 @@ <function>&mac.mpo;_copy_vnode_label</function> - + void &mac.mpo;_copy_vnode_label - + struct label *src struct label *dest - + &mac.thead; - + src Source label - + dest Destination label @@ -1933,7 +1933,7 @@ - + Copy the label information in src into dest. @@ -1941,261 +1941,261 @@ <function>&mac.mpo;_externalize_cred_label</function> - + int &mac.mpo;_externalize_cred_label - + &mac.externalize.paramdefs; - + &mac.thead; - + &mac.externalize.tbody; - + &mac.externalize.para; <function>&mac.mpo;_externalize_ifnet_label</function> - + int &mac.mpo;_externalize_ifnet_label - + &mac.externalize.paramdefs; - + &mac.thead; - + &mac.externalize.tbody; - + &mac.externalize.para; - + <function>&mac.mpo;_externalize_pipe_label</function> - + int &mac.mpo;_externalize_pipe_label - + &mac.externalize.paramdefs; - + &mac.thead; - + &mac.externalize.tbody; - + &mac.externalize.para; - + <function>&mac.mpo;_externalize_socket_label</function> - + int &mac.mpo;_externalize_socket_label - + &mac.externalize.paramdefs; - + &mac.thead; - + &mac.externalize.tbody; - + &mac.externalize.para; - + <function>&mac.mpo;_externalize_socket_peer_label</function> - + int &mac.mpo;_externalize_socket_peer_label - + &mac.externalize.paramdefs; - + &mac.thead; - + &mac.externalize.tbody; - + &mac.externalize.para; - + <function>&mac.mpo;_externalize_vnode_label</function> - + int &mac.mpo;_externalize_vnode_label - + &mac.externalize.paramdefs; - + &mac.thead; - + &mac.externalize.tbody; - + &mac.externalize.para; - + <function>&mac.mpo;_internalize_cred_label</function> - + int &mac.mpo;_internalize_cred_label - + &mac.internalize.paramdefs; - + &mac.thead; - + &mac.internalize.tbody; - + &mac.internalize.para; <function>&mac.mpo;_internalize_ifnet_label</function> - + int &mac.mpo;_internalize_ifnet_label - + &mac.internalize.paramdefs; - + &mac.thead; - + &mac.internalize.tbody; - + &mac.internalize.para; - + <function>&mac.mpo;_internalize_pipe_label</function> - + int &mac.mpo;_internalize_pipe_label - + &mac.internalize.paramdefs; - + &mac.thead; - + &mac.internalize.tbody; - + &mac.internalize.para; - + <function>&mac.mpo;_internalize_socket_label</function> - + int &mac.mpo;_internalize_socket_label - + &mac.internalize.paramdefs; - + &mac.thead; - + &mac.internalize.tbody; - + &mac.internalize.para; <function>&mac.mpo;_internalize_vnode_label</function> - + int &mac.mpo;_internalize_vnode_label - + &mac.internalize.paramdefs; - + &mac.thead; - + &mac.internalize.tbody; - + &mac.internalize.para; - + Label Events - + This class of entry points is used by the MAC framework to permit policies to maintain label information on kernel objects. For each labeled kernel object of interest to a MAC @@ -2207,7 +2207,7 @@ events, such as label events associated with IP reassembly. A typical labeled object will have the following life cycle of entry points: - + Label initialization o (object-specific wait) \ Label creation o @@ -2217,13 +2217,13 @@ Various object-specific, | | Access control events ~-->--o \ Label destruction o - + Label initialization permits policies to allocate memory and set initial values for labels without context for the use of the object. The label slot allocated to a policy will be zeroed by default, so some policies may not need to perform initialization. - + Label creation occurs when the kernel structure is associated with an actual kernel object. For example, Mbufs may be allocated and remain unused in a pool until they are @@ -2239,7 +2239,7 @@ Label destruction o occur in performance sensitive ports of the kernel; in addition, creation calls are not permitted to fail so a failure to allocate memory cannot be reported. - + Object specific events do not generally fall into the other broad classes of label events, but will generally provide an opportunity to modify or update the label on an @@ -2247,15 +2247,15 @@ Label destruction o an IP fragment reassembly queue may be updated during the MAC_UPDATE_IPQ entry point as a result of the acceptance of an additional mbuf to that queue. - + Access control events are discussed in detail in the following section. - + Label destruction permits policies to release storage or state associated with a label during its association with an object so that the kernel data structures supporting the object may be reused or released. - + In addition to labels associated with specific kernel objects, an additional class of labels exists: temporary labels. These labels are used to store update information @@ -2263,7 +2263,7 @@ Label destruction o destroyed as with other label types, but the creation event is MAC_INTERNALIZE, which accepts a user label to be converted to an in-kernel representation. - + File System Object Labeling Event Operations @@ -2454,12 +2454,12 @@ Label destruction o <function>&mac.mpo;_create_devfs_device</function> - + void &mac.mpo;_create_devfs_device - + dev_t dev struct devfs_dirent *devfs_dirent @@ -2467,23 +2467,23 @@ Label destruction o *label - + &mac.thead; - + dev Device corresponding with devfs_dirent - + devfs_dirent Devfs directory entry to be labeled. - + label Label for devfs_dirent @@ -2492,21 +2492,21 @@ Label destruction o - + Fill out the label on a devfs_dirent being created for the passed device. This call will be made when the device file system is mounted, regenerated, or a new device is made available. - + <function>&mac.mpo;_create_devfs_directory</function> - + void &mac.mpo;_create_devfs_directory - + char *dirname int dirnamelen struct devfs_dirent @@ -2515,23 +2515,23 @@ Label destruction o *label - + &mac.thead; - + dirname Name of directory being created - + namelen Length of string dirname - + devfs_dirent Devfs directory entry for directory being @@ -2540,7 +2540,7 @@ Label destruction o - + Fill out the label on a devfs_dirent being created for the passed directory. This call will be made when the device file system is mounted, regenerated, or a new device @@ -2614,7 +2614,7 @@ Label destruction o Fill in the label (delabel) for a newly created &man.devfs.5; symbolic link entry. - + <function>&mac.mpo;_create_vnode_extattr</function> @@ -2702,12 +2702,12 @@ Label destruction o <function>&mac.mpo;_create_mount</function> - + void &mac.mpo;_create_mount - + struct ucred *cred struct mount @@ -2718,28 +2718,28 @@ Label destruction o *fslabel - + &mac.thead; - + cred Subject credential - + mp Object; file system being mounted - + mntlabel Policy label to be filled in for mp - + fslabel Policy label for the file system @@ -2748,20 +2748,20 @@ Label destruction o - + Fill out the labels on the mount point being created by the passed subject credential. This call will be made when a new file system is mounted. - + <function>&mac.mpo;_create_root_mount</function> - + void &mac.mpo;_create_root_mount - + struct ucred *cred struct mount @@ -2772,11 +2772,11 @@ Label destruction o *fslabel - + &mac.thead; - + See - + Fill out the labels on the mount point being created by the passed subject credential. This call will be made when the root file system is mounted, after @@ -2794,12 +2794,12 @@ Label destruction o <function>&mac.mpo;_relabel_vnode</function> - + void &mac.mpo;_relabel_vnode - + struct ucred *cred struct vnode @@ -2810,28 +2810,28 @@ Label destruction o *newlabel - + &mac.thead; - + cred Subject credential - + vp vnode to relabel - + vnodelabel Existing policy label for vp - + newlabel New, possibly partial label to replace @@ -2840,7 +2840,7 @@ Label destruction o - + Update the label on the passed vnode given the passed update vnode label and the passed subject credential. @@ -2906,7 +2906,7 @@ Label destruction o void &mac.mpo;_update_devfsdirent - + struct devfs_dirent *devfs_dirent struct label @@ -2917,30 +2917,30 @@ Label destruction o *vnodelabel - + &mac.thead; - + devfs_dirent Object; devfs directory entry - + direntlabel Policy label for devfs_dirent to be updated. - + vp Parent vnode Locked - + vnodelabel Policy label for @@ -2949,7 +2949,7 @@ Label destruction o - + Update the devfs_dirent label from the passed devfs vnode label. This call will be made when a devfs vnode has been successfully relabeled to commit @@ -2960,19 +2960,19 @@ Label destruction o initialize the vnode label. - + IPC Object Labeling Event Operations - + <function>&mac.mpo;_create_mbuf_from_socket</function> - + void &mac.mpo;_create_mbuf_from_socket - + struct socket *so struct label @@ -2982,29 +2982,29 @@ Label destruction o *mbuflabel - + &mac.thead; - + socket Socket Socket locking WIP - + socketlabel Policy label for socket - + m Object; mbuf - + mbuflabel Policy label to fill in for @@ -3013,7 +3013,7 @@ Label destruction o - + Set the label on a newly created mbuf header from the passed socket label. This call is made when a new datagram or message is generated by the socket and stored in the @@ -3065,15 +3065,15 @@ Label destruction o subject credential. This call is made when a new pipe is created. - + <function>&mac.mpo;_create_socket</function> - + void &mac.mpo;_create_socket - + struct ucred *cred struct socket @@ -3082,23 +3082,23 @@ Label destruction o *socketlabel - + &mac.thead; - + cred Subject credential Immutable - + so Object; socket to label - + socketlabel Label to fill in for @@ -3107,7 +3107,7 @@ Label destruction o - + Set the label on a newly created socket from the passed subject credential. This call is made when a socket is created. @@ -3222,12 +3222,12 @@ Label destruction o <function>&mac.mpo;_relabel_socket</function> - + void &mac.mpo;_relabel_socket - + struct ucred *cred struct socket @@ -3238,29 +3238,29 @@ Label destruction o *newlabel - + &mac.thead; - + cred Subject credential Immutable - + so Object; socket - + oldlabel Current label for so - + newlabel Label update for @@ -3269,19 +3269,19 @@ Label destruction o - + Update the label on a socket from the passed socket label update. - + <function>&mac.mpo;_set_socket_peer_from_mbuf</function> - + void &mac.mpo;_set_socket_peer_from_mbuf - + struct mbuf *mbuf struct label @@ -3292,27 +3292,27 @@ Label destruction o *newlabel - + &mac.thead; - + mbuf First datagram received over socket - + mbuflabel Label for mbuf - + oldlabel Current label for the socket - + newlabel Policy label to be filled out for the @@ -3321,21 +3321,21 @@ Label destruction o - + Set the peer label on a stream socket from the passed mbuf label. This call will be made when the first datagram is received by the stream socket, with the exception of Unix domain sockets. - + <function>&mac.mpo;_set_socket_peer_from_socket</function> - + void &mac.mpo;_set_socket_peer_from_socket - + struct socket *oldsocket struct label @@ -3346,28 +3346,28 @@ Label destruction o *newsocketpeerlabel - + &mac.thead; - + oldsocket Local socket - + oldsocketlabel Policy label for oldsocket - + newsocket Peer socket - + newsocketpeerlabel Policy label to fill in for @@ -3376,7 +3376,7 @@ Label destruction o - + Set the peer label on a stream UNIX domain socket from the passed remote socket endpoint. This call will be made @@ -3384,18 +3384,18 @@ Label destruction o endpoints. - + Network Object Labeling Event Operations - + <function>&mac.mpo;_create_bpfdesc</function> - + void &mac.mpo;_create_bpfdesc - + struct ucred *cred struct bpf_d @@ -3404,23 +3404,23 @@ Label destruction o *bpflabel - + &mac.thead; - + cred Subject credential Immutable - + bpf_d Object; bpf descriptor - + bpf Policy label to be filled in for @@ -3429,38 +3429,38 @@ Label destruction o - + Set the label on a newly created BPF descriptor from the passed subject credential. This call will be made when a BPF device node is opened by a process with the passed subject credential. - + <function>&mac.mpo;_create_ifnet</function> - + void &mac.mpo;_create_ifnet - + struct ifnet *ifnet struct label *ifnetlabel - + &mac.thead; - + ifnet Network interface - + ifnetlabel Policy label to fill in for @@ -3469,21 +3469,21 @@ Label destruction o - + Set the label on a newly created interface. This call may be made when a new physical interface becomes available to the system, or when a pseudo-interface is instantiated during the boot or as a result of a user action. - + <function>&mac.mpo;_create_ipq</function> - + void &mac.mpo;_create_ipq - + struct mbuf *fragment struct label @@ -3494,28 +3494,28 @@ Label destruction o *ipqlabel - + &mac.thead; - + fragment First received IP fragment - + fragmentlabel Policy label for fragment - + ipq IP reassembly queue to be labeled - + ipqlabel Policy label to be filled in for @@ -3524,20 +3524,20 @@ Label destruction o - + Set the label on a newly created IP fragment reassembly queue from the mbuf header of the first received fragment. - + <function>&mac.mpo;_create_datagram_from_ipq</function> - + void &mac.mpo;_create_create_datagram_from_ipq - + struct ipq *ipq struct label @@ -3548,28 +3548,28 @@ Label destruction o *datagramlabel - + &mac.thead; - + ipq IP reassembly queue - + ipqlabel Policy label for ipq - + datagram Datagram to be labeled - + datagramlabel Policy label to be filled in for @@ -3578,20 +3578,20 @@ Label destruction o - + Set the label on a newly reassembled IP datagram from the IP fragment reassembly queue from which it was generated. - + <function>&mac.mpo;_create_fragment</function> - + void &mac.mpo;_create_fragment - + struct mbuf *datagram struct label @@ -3602,28 +3602,28 @@ Label destruction o *fragmentlabel - + &mac.thead; - + datagram Datagram - + datagramlabel Policy label for datagram - + fragment Fragment to be labeled - + fragmentlabel Policy label to be filled in for @@ -3632,20 +3632,20 @@ Label destruction o - + Set the label on the mbuf header of a newly created IP fragment from the label on the mbuf header of the datagram it was generate from. - + <function>&mac.mpo;_create_mbuf_from_mbuf</function> - + void &mac.mpo;_create_mbuf_from_mbuf - + struct mbuf *oldmbuf struct label @@ -3656,28 +3656,28 @@ Label destruction o *newmbuflabel - + &mac.thead; - + oldmbuf Existing (source) mbuf - + oldmbuflabel Policy label for oldmbuf - + newmbuf New mbuf to be labeled - + newmbuflabel Policy label to be filled in for @@ -3686,21 +3686,21 @@ Label destruction o - + Set the label on the mbuf header of a newly created datagram from the mbuf header of an existing datagram. This call may be made in a number of situations, including when an mbuf is re-allocated for alignment purposes. - + <function>&mac.mpo;_create_mbuf_linklayer</function> - + void &mac.mpo;_create_mbuf_linklayer - + struct ifnet *ifnet struct label @@ -3711,28 +3711,28 @@ Label destruction o *mbuflabel - + &mac.thead; - + ifnet Network interface - + ifnetlabel Policy label for ifnet - + mbuf mbuf header for new datagram - + mbuflabel Policy label to be filled in for @@ -3741,22 +3741,22 @@ Label destruction o - + Set the label on the mbuf header of a newly created datagram generated for the purposes of a link layer response for the passed interface. This call may be made in a number of situations, including for ARP or ND6 responses in the IPv4 and IPv6 stacks. - + <function>&mac.mpo;_create_mbuf_from_bpfdesc</function> - + void &mac.mpo;_create_mbuf_from_bpfdesc - + struct bpf_d *bpf_d struct label @@ -3767,28 +3767,28 @@ Label destruction o *mbuflabel - + &mac.thead; - + bpf_d BPF descriptor - + bpflabel Policy label for bpflabel - + mbuf New mbuf to be labeled - + mbuflabel Policy label to fill in for @@ -3797,21 +3797,21 @@ Label destruction o - + Set the label on the mbuf header of a newly created datagram generated using the passed BPF descriptor. This call is made when a write is performed to the BPF device associated with the passed BPF descriptor. - + <function>&mac.mpo;_create_mbuf_from_ifnet</function> - + void &mac.mpo;_create_mbuf_from_ifnet - + struct ifnet *ifnet struct label @@ -3822,28 +3822,28 @@ Label destruction o *mbuflabel - + &mac.thead; - + ifnet Network interface - + ifnetlabel Policy label for ifnetlabel - + mbuf mbuf header for new datagram - + mbuflabel Policy label to be filled in for @@ -3852,19 +3852,19 @@ Label destruction o - + Set the label on the mbuf header of a newly created datagram generated from the passed network interface. - + <function>&mac.mpo;_create_mbuf_multicast_encap</function> - + void &mac.mpo;_create_mbuf_multicast_encap - + struct mbuf *oldmbuf struct label @@ -3879,40 +3879,40 @@ Label destruction o *newmbuflabel - + &mac.thead; - + oldmbuf mbuf header for existing datagram - + oldmbuflabel Policy label for oldmbuf - + ifnet Network interface - + ifnetlabel Policy label for ifnet - + newmbuf mbuf header to be labeled for new datagram - + newmbuflabel Policy label to be filled in for @@ -3921,22 +3921,22 @@ Label destruction o - + Set the label on the mbuf header of a newly created datagram generated from the existing passed datagram when it is processed by the passed multicast encapsulation interface. This call is made when an mbuf is to be delivered using the virtual interface. - + <function>&mac.mpo;_create_mbuf_netlayer</function> - + void &mac.mpo;_create_mbuf_netlayer - + struct mbuf *oldmbuf struct label @@ -3947,28 +3947,28 @@ Label destruction o *newmbuflabel - + &mac.thead; - + oldmbuf Received datagram - + oldmbuflabel Policy label for oldmbuf - + newmbuf Newly created datagram - + newmbuflabel Policy label for @@ -3977,22 +3977,22 @@ Label destruction o - + Set the label on the mbuf header of a newly created datagram generated by the IP stack in response to an existing received datagram (oldmbuf). This call may be made in a number of situations, including when responding to ICMP request datagrams. - + <function>&mac.mpo;_fragment_match</function> - + int &mac.mpo;_fragment_match - + struct mbuf *fragment struct label @@ -4003,28 +4003,28 @@ Label destruction o *ipqlabel - + &mac.thead; - + fragment IP datagram fragment - + fragmentlabel Policy label for fragment - + ipq IP fragment reassembly queue - + ipqlabel Policy label for @@ -4033,7 +4033,7 @@ Label destruction o - + Determine whether an mbuf header containing an IP datagram (fragment) fragment matches the label of the passed IP fragment reassembly queue @@ -4048,15 +4048,15 @@ Label destruction o policy does not permit them to be reassembled based on the label or other information. - + <function>&mac.mpo;_relabel_ifnet</function> - + void &mac.mpo;_relabel_ifnet - + struct ucred *cred struct ifnet @@ -4067,28 +4067,28 @@ Label destruction o *newlabel - + &mac.thead; - + cred Subject credential - + ifnet Object; Network interface - + ifnetlabel Policy label for ifnet - + newlabel Label update to apply to @@ -4097,21 +4097,21 @@ Label destruction o - + Update the label of network interface, ifnet, based on the passed update label, newlabel, and the passed subject credential, cred. - + <function>&mac.mpo;_update_ipq</function> - + void &mac.mpo;_update_ipq - + struct mbuf *fragment struct label @@ -4122,28 +4122,28 @@ Label destruction o *ipqlabel - + &mac.thead; - + mbuf IP fragment - + mbuflabel Policy label for mbuf - + ipq IP fragment reassembly queue - + ipqlabel Policy label to be updated for @@ -4152,42 +4152,42 @@ Label destruction o - + Update the label on an IP fragment reassembly queue (ipq) based on the acceptance of the passed IP fragment mbuf header (mbuf). - + Process Labeling Event Operations - + <function>&mac.mpo;_create_cred</function> - + void &mac.mpo;_create_cred - + struct ucred *parent_cred struct ucred *child_cred - + &mac.thead; - + parent_cred Parent subject credential - + child_cred Child subject credential @@ -4195,22 +4195,22 @@ Label destruction o - + Set the label of a newly created subject credential from the passed subject credential. This call will be made when &man.crcopy.9; is invoked on a newly created struct ucred. This call should not be confused with a process forking or creation event. - + <function>&mac.mpo;_execve_transition</function> - + void &mac.mpo;_execve_transition - + struct ucred *old struct ucred @@ -4221,29 +4221,29 @@ Label destruction o *vnodelabel - + &mac.thead; - + old Existing subject credential Immutable - + new New subject credential to be labeled - + vp File to execute Locked - + vnodelabel Policy label for @@ -4252,7 +4252,7 @@ Label destruction o - + Update the label of a newly created subject credential (new) from the passed existing subject credential (old) based on a @@ -4270,15 +4270,15 @@ Label destruction o implement mpo_execve_will_transition. - + <function>&mac.mpo;_execve_will_transition</function> - + int &mac.mpo;_execve_will_transition - + struct ucred *old struct vnode @@ -4287,11 +4287,11 @@ Label destruction o *vnodelabel - + &mac.thead; - + old @@ -4299,12 +4299,12 @@ Label destruction o &man.execve.2; Immutable - + vp File to execute - + vnodelabel Policy label for @@ -4313,7 +4313,7 @@ Label destruction o - + Determine whether the policy will want to perform a transition event as a result of the execution of the passed vnode by the passed subject credential. Return @@ -4325,24 +4325,24 @@ Label destruction o happen as a result of another policy requesting a transition. - + <function>&mac.mpo;_create_proc0</function> - + void &mac.mpo;_create_proc0 - + struct ucred *cred - + &mac.thead; - + cred @@ -4351,28 +4351,28 @@ Label destruction o - + Create the subject credential of process 0, the parent of all kernel processes. - + <function>&mac.mpo;_create_proc1</function> - + void &mac.mpo;_create_proc1 - + struct ucred *cred - + &mac.thead; - + cred @@ -4381,36 +4381,36 @@ Label destruction o - + Create the subject credential of process 1, the parent of all user processes. - + <function>&mac.mpo;_relabel_cred</function> - + void &mac.mpo;_relabel_cred - + struct ucred *cred struct label *newlabel - + &mac.thead; - + cred Subject credential - + newlabel Label update to apply to @@ -4419,17 +4419,17 @@ Label destruction o - + Update the label on a subject credential from the passed update label. - + Access Control Checks - + Access control entry points permit policy modules to influence access control decisions made by the kernel. Generally, although not always, arguments to an access control @@ -4446,14 +4446,14 @@ Label destruction o following precedence, implemented by the error_select() function in kern_mac.c: - + Most precedence EDEADLK - + EINVAL @@ -4473,22 +4473,22 @@ Label destruction o - + If none of the error values returned by all modules are listed in the precedence chart then an arbitrarily selected value from the set will be returned. In general, the rules provide precedence to errors in the following order: kernel failures, invalid arguments, object not present, access not permitted, other. - + <function>&mac.mpo;_check_bpfdesc_receive</function> - + int &mac.mpo;_check_bpfdesc_receive - + struct bpf_d *bpf_d struct label @@ -4499,28 +4499,28 @@ Label destruction o *ifnetlabel - + &mac.thead; - + bpf_d Subject; BPF descriptor - + bpflabel Policy label for bpf_d - + ifnet Object; network interface - + ifnetlabel Policy label for @@ -4529,7 +4529,7 @@ Label destruction o - + Determine whether the MAC framework should permit datagrams from the passed interface to be delivered to the buffers of the passed BPF descriptor. Return @@ -4665,7 +4665,7 @@ Label destruction o cred Subject credential - + name Kernel environment variable name @@ -5078,12 +5078,12 @@ Label destruction o <function>&mac.mpo;_check_socket_bind</function> - + int &mac.mpo;_check_socket_bind - + struct ucred *cred struct socket @@ -5094,28 +5094,28 @@ Label destruction o *sockaddr - + &mac.thead; - + cred Subject credential - + socket Socket to be bound - + socketlabel Policy label for socket - + sockaddr Address of @@ -5124,18 +5124,18 @@ Label destruction o - + - - + + <function>&mac.mpo;_check_socket_connect</function> - + int &mac.mpo;_check_socket_connect - + struct ucred *cred struct socket @@ -5146,37 +5146,37 @@ Label destruction o *sockaddr - + &mac.thead; - + cred Subject credential - + socket Socket to be connected - + socketlabel Policy label for socket - + sockaddr Address of socket - + - + Determine whether the subject credential (cred) can connect the passed socket (socket) to the passed socket address @@ -5278,32 +5278,32 @@ Label destruction o information across the socket so. - + <function>&mac.mpo;_check_cred_visible</function> - + int &mac.mpo;_check_cred_visible - + struct ucred *u1 struct ucred *u2 - + &mac.thead; - + u1 Subject credential - + u2 Object credential @@ -5311,7 +5311,7 @@ Label destruction o - + Determine whether the subject credential u1 can see other subjects with the passed subject credential @@ -5325,15 +5325,15 @@ Label destruction o inter-process status sysctl's used by ps, and in procfs lookups. - + <function>&mac.mpo;_check_socket_visible</function> - + int &mac.mpo;_check_socket_visible - + struct ucred *cred struct socket @@ -5342,22 +5342,22 @@ Label destruction o *socketlabel - + &mac.thead; - + cred Subject credential - + socket Object; socket - + socketlabel Policy label for @@ -5366,17 +5366,17 @@ Label destruction o - + - + <function>&mac.mpo;_check_ifnet_relabel</function> - + int &mac.mpo;_check_ifnet_relabel - + struct ucred *cred struct ifnet @@ -5387,28 +5387,28 @@ Label destruction o *newlabel - + &mac.thead; - + cred Subject credential - + ifnet Object; network interface - + ifnetlabel Existing policy label for ifnet - + newlabel Policy label update to later be applied to @@ -5417,19 +5417,19 @@ Label destruction o - + Determine whether the subject credential can relabel the passed network interface to the passed label update. - + <function>&mac.mpo;_check_socket_relabel</function> - + int &mac.mpo;_check_socket_relabel - + struct ucred *cred struct socket @@ -5440,28 +5440,28 @@ Label destruction o *newlabel - + &mac.thead; - + cred Subject credential - + socket Object; socket - + socketlabel Existing policy label for socket - + newlabel Label update to later be applied to @@ -5470,36 +5470,36 @@ Label destruction o - + Determine whether the subject credential can relabel the passed socket to the passed label update. - + <function>&mac.mpo;_check_cred_relabel</function> - + int &mac.mpo;_check_cred_relabel - + struct ucred *cred struct label *newlabel - + &mac.thead; - + cred Subject credential - + newlabel Label update to later be applied to @@ -5508,7 +5508,7 @@ Label destruction o - + Determine whether the subject credential can relabel itself to the passed label update. @@ -5516,12 +5516,12 @@ Label destruction o <function>&mac.mpo;_check_vnode_relabel</function> - + int &mac.mpo;_check_vnode_relabel - + struct ucred *cred struct vnode @@ -5532,30 +5532,30 @@ Label destruction o *newlabel - + &mac.thead; - + cred Subject credential Immutable - + vp Object; vnode Locked - + vnodelabel Existing policy label for vp - + newlabel Policy label update to later be applied to @@ -5564,18 +5564,18 @@ Label destruction o - + Determine whether the subject credential can relabel the passed vnode to the passed label update. - + <function>&mac.mpo;_check_mount_stat</function> - + int &mac.mpo;_check_mount_stat - + struct ucred *cred struct mount @@ -5584,22 +5584,22 @@ Label destruction o *mountlabel - + &mac.thead; - + cred Subject credential - + mp Object; file system mount - + mountlabel Policy label for @@ -5608,7 +5608,7 @@ Label destruction o - + Determine whether the subject credential can see the results of a statfs performed on the file system. Return @@ -5621,33 +5621,33 @@ Label destruction o determine what file systems to exclude from listings of file systems, such as when &man.getfsstat.2; is invoked. - + <function>&mac.mpo;_check_proc_debug</function> - + int &mac.mpo;_check_proc_debug - + struct ucred *cred struct proc *proc - + &mac.thead; - + cred Subject credential Immutable - + proc Object; process @@ -5655,7 +5655,7 @@ Label destruction o - + Determine whether the subject credential can debug the passed process. Return 0 for success, or an errno value for failure. @@ -5667,15 +5667,15 @@ Label destruction o &man.ktrace.2; APIs, as well as for some types of procfs operations. - + <function>&mac.mpo;_check_vnode_access</function> - + int &mac.mpo;_check_vnode_access - + struct ucred *cred struct vnode @@ -5685,28 +5685,28 @@ Label destruction o int flags - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + flags &man.access.2; flags @@ -5714,7 +5714,7 @@ Label destruction o - + Determine how invocations of &man.access.2; and related calls by the subject credential should return when performed on the passed vnode using the passed access flags. This @@ -5726,15 +5726,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_chdir</function> - + int &mac.mpo;_check_vnode_chdir - + struct ucred *cred struct vnode @@ -5743,22 +5743,22 @@ Label destruction o *dlabel - + &mac.thead; - + cred Subject credential - + dvp Object; vnode to &man.chdir.2; into - + dlabel Policy label for @@ -5767,7 +5767,7 @@ Label destruction o - + Determine whether the subject credential can change the process working directory to the passed vnode. Return 0 for success, or an @@ -5822,15 +5822,15 @@ Label destruction o &man.chroot.2; into the specified directory (dvp). - + <function>&mac.mpo;_check_vnode_create</function> - + int &mac.mpo;_check_vnode_create - + struct ucred *cred struct vnode @@ -5843,34 +5843,34 @@ Label destruction o *vap - + &mac.thead; - + cred Subject credential - + dvp Object; vnode - + dlabel Policy label for dvp - + cnp Component name for dvp - + vap vnode attributes for vap @@ -5878,7 +5878,7 @@ Label destruction o - + Determine whether the subject credential can create a vnode with the passed parent directory, passed name information, and passed attribute information. Return @@ -5891,15 +5891,15 @@ Label destruction o O_CREAT, &man.mknod.2;, &man.mkfifo.2;, and others. - + <function>&mac.mpo;_check_vnode_delete</function> - + int &mac.mpo;_check_vnode_delete - + struct ucred *cred struct vnode @@ -5913,39 +5913,39 @@ Label destruction o *cnp - + &mac.thead; - + cred Subject credential - + dvp Parent directory vnode - + dlabel Policy label for dvp - + vp Object; vnode to delete - + label Policy label for vp - + cnp Component name for @@ -5954,7 +5954,7 @@ Label destruction o - + Determine whether the subject credential can delete a vnode from the passed parent directory and passed name information. Return 0 for @@ -5969,45 +5969,45 @@ Label destruction o deletion of objects as a result of being the target of a rename. - + <function>&mac.mpo;_check_vnode_deleteacl</function> - + int &mac.mpo;_check_vnode_deleteacl - + struct ucred *cred struct vnode *vp struct label *label acl_type_t type - + &mac.thead; - + cred Subject credential Immutable - + vp Object; vnode Locked - + label Policy label for vp - + type ACL type @@ -6015,7 +6015,7 @@ Label destruction o - + Determine whether the subject credential can delete the ACL of passed type from the passed vnode. Return 0 for success, or an @@ -6024,15 +6024,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_exec</function> - + int &mac.mpo;_check_vnode_exec - + struct ucred *cred struct vnode @@ -6041,22 +6041,22 @@ Label destruction o *label - + &mac.thead; - + cred Subject credential - + vp Object; vnode to execute - + label Policy label for @@ -6065,7 +6065,7 @@ Label destruction o - + Determine whether the subject credential can execute the passed vnode. Determination of execute privilege is made separately from decisions about any transitioning event. @@ -6075,15 +6075,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_getacl</function> - + int &mac.mpo;_check_vnode_getacl - + struct ucred *cred struct vnode @@ -6094,28 +6094,28 @@ Label destruction o type - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + type ACL type @@ -6123,7 +6123,7 @@ Label destruction o - + Determine whether the subject credential can retrieve the ACL of passed type from the passed vnode. Return 0 for success, or an @@ -6132,15 +6132,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_getextattr</function> - + int &mac.mpo;_check_vnode_getextattr - + struct ucred *cred struct vnode @@ -6155,38 +6155,38 @@ Label destruction o *uio - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + attrnamespace Extended attribute namespace - + name Extended attribute name - + uio I/O structure pointer; see &man.uio.9; @@ -6194,7 +6194,7 @@ Label destruction o - + Determine whether the subject credential can retrieve the extended attribute with the passed namespace and name from the passed vnode. Policies implementing labeling using @@ -6621,15 +6621,15 @@ Label destruction o existing file to overwrite, vp and label will be NULL. - + <function>&mac.mpo;_check_socket_listen</function> - + int &mac.mpo;_check_socket_listen - + struct ucred *cred struct socket @@ -6638,22 +6638,22 @@ Label destruction o *socketlabel - + &mac.thead; - + cred Subject credential - + socket Object; socket - + socketlabel Policy label for @@ -6662,7 +6662,7 @@ Label destruction o - + Determine whether the subject credential can listen on the passed socket. Return 0 for success, or an errno value for failure. @@ -6670,15 +6670,15 @@ Label destruction o mismatch, or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_lookup</function> - + int &mac.mpo;_check_vnode_lookup - + struct ucred *cred struct vnode @@ -6689,28 +6689,28 @@ Label destruction o *cnp - + &mac.thead; - + cred Subject credential - + dvp Object; vnode - + dlabel Policy label for dvp - + cnp Component name being looked up @@ -6718,7 +6718,7 @@ Label destruction o - + Determine whether the subject credential can perform a lookup in the passed directory vnode for the passed name. Return 0 for success, or an @@ -6727,15 +6727,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_open</function> - + int &mac.mpo;_check_vnode_open - + struct ucred *cred struct vnode @@ -6746,28 +6746,28 @@ Label destruction o acc_mode - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + acc_mode &man.open.2; access mode @@ -6775,7 +6775,7 @@ Label destruction o - + Determine whether the subject credential can perform an open operation on the passed vnode with the passed access mode. Return 0 for success, or @@ -6783,15 +6783,15 @@ Label destruction o EACCES for label mismatch, or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_readdir</function> - + int &mac.mpo;_check_vnode_readdir - + struct ucred *cred struct vnode @@ -6800,22 +6800,22 @@ Label destruction o *dlabel - + &mac.thead; - + cred Subject credential - + dvp Object; directory vnode - + dlabel Policy label for @@ -6824,7 +6824,7 @@ Label destruction o - + Determine whether the subject credential can perform a readdir operation on the passed directory vnode. Return 0 for @@ -6833,15 +6833,15 @@ Label destruction o mismatch, or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_readlink</function> - + int &mac.mpo;_check_vnode_readlink - + struct ucred *cred struct vnode @@ -6850,22 +6850,22 @@ Label destruction o *label - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for @@ -6874,7 +6874,7 @@ Label destruction o - + Determine whether the subject credential can perform a readlink operation on the passed symlink vnode. Return 0 for @@ -6887,15 +6887,15 @@ Label destruction o readlink during a name lookup by the process. - + <function>&mac.mpo;_check_vnode_revoke</function> - + int &mac.mpo;_check_vnode_revoke - + struct ucred *cred struct vnode @@ -6904,22 +6904,22 @@ Label destruction o *label - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for @@ -6928,7 +6928,7 @@ Label destruction o - + Determine whether the subject credential can revoke access to the passed vnode. Return 0 for success, or an @@ -6937,15 +6937,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_setacl</function> - + int &mac.mpo;_check_vnode_setacl - + struct ucred *cred struct vnode @@ -6958,33 +6958,33 @@ Label destruction o *acl - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + type ACL type - + acl ACL @@ -6992,7 +6992,7 @@ Label destruction o - + Determine whether the subject credential can set the passed ACL of passed type on the passed vnode. Return 0 for success, or an @@ -7001,15 +7001,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_setextattr</function> - + int &mac.mpo;_check_vnode_setextattr - + struct ucred *cred struct vnode @@ -7024,37 +7024,37 @@ Label destruction o *uio - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + attrnamespace Extended attribute namespace - + name Extended attribute name - + uio I/O structure pointer; see &man.uio.9; @@ -7062,7 +7062,7 @@ Label destruction o - + Determine whether the subject credential can set the extended attribute of passed name and passed namespace on the passed vnode. Policies implementing security labels @@ -7079,15 +7079,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_setflags</function> - + int &mac.mpo;_check_vnode_setflags - + struct ucred *cred struct vnode @@ -7097,28 +7097,28 @@ Label destruction o u_long flags - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + flags File flags; see &man.chflags.2; @@ -7126,7 +7126,7 @@ Label destruction o - + Determine whether the subject credential can set the passed flags on the passed vnode. Return 0 for success, or an @@ -7135,15 +7135,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_setmode</function> - + int &mac.mpo;_check_vnode_setmode - + struct ucred *cred struct vnode @@ -7153,27 +7153,27 @@ Label destruction o mode_t mode - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + mode File mode; see &man.chmod.2; @@ -7181,7 +7181,7 @@ Label destruction o - + Determine whether the subject credential can set the passed mode on the passed vnode. Return 0 for success, or an @@ -7190,15 +7190,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_setowner</function> - + int &mac.mpo;_check_vnode_setowner - + struct ucred *cred struct vnode @@ -7209,32 +7209,32 @@ Label destruction o gid_t gid - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for vp - + uid User ID - + gid Group ID @@ -7242,7 +7242,7 @@ Label destruction o - + Determine whether the subject credential can set the passed uid and passed gid as file uid and file gid on the passed vnode. The IDs may be set to (-1) @@ -7252,15 +7252,15 @@ Label destruction o for label mismatch, or EPERM for lack of privilege. - + <function>&mac.mpo;_check_vnode_setutimes</function> - + int &mac.mpo;_check_vnode_setutimes - + struct ucred *cred struct vnode @@ -7273,33 +7273,33 @@ Label destruction o mtime - + &mac.thead; - + cred Subject credential - + vp Object; vp - + label Policy label for vp - + atime Access time; see &man.utimes.2; - + mtime Modification time; see &man.utimes.2; @@ -7307,7 +7307,7 @@ Label destruction o - + Determine whether the subject credential can set the passed access timestamps on the passed vnode. Return 0 for success, or an @@ -7316,32 +7316,32 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_proc_sched</function> - + int &mac.mpo;_check_proc_sched - + struct ucred *ucred struct proc *proc - + &mac.thead; - + cred Subject credential - + proc Object; process @@ -7349,7 +7349,7 @@ Label destruction o - + Determine whether the subject credential can change the scheduling parameters of the passed process. Return 0 for success, or an @@ -7357,18 +7357,18 @@ Label destruction o failure: EACCES for label mismatch, EPERM for lack of privilege, or ESRCH to limit visibility. - + See &man.setpriority.2; for more information. - + <function>&mac.mpo;_check_proc_signal</function> - + int &mac.mpo;_check_proc_signal - + struct ucred *cred struct proc @@ -7376,22 +7376,22 @@ Label destruction o int signal - + &mac.thead; - + cred Subject credential - + proc Object; process - + signal Signal; see &man.kill.2; @@ -7399,7 +7399,7 @@ Label destruction o - + Determine whether the subject credential can deliver the passed signal to the passed process. Return 0 for success, or an @@ -7408,15 +7408,15 @@ Label destruction o EPERM for lack of privilege, or ESRCH to limit visibility. - + <function>&mac.mpo;_check_vnode_stat</function> - + int &mac.mpo;_check_vnode_stat - + struct ucred *cred struct vnode @@ -7425,22 +7425,22 @@ Label destruction o *label - + &mac.thead; - + cred Subject credential - + vp Object; vnode - + label Policy label for @@ -7449,7 +7449,7 @@ Label destruction o - + Determine whether the subject credential can stat the passed vnode. Return 0 for success, or an @@ -7457,18 +7457,18 @@ Label destruction o failure: EACCES for label mismatch, or EPERM for lack of privilege. - + See &man.stat.2; for more information. - + <function>&mac.mpo;_check_ifnet_transmit</function> - + int &mac.mpo;_check_ifnet_transmit - + struct ucred *cred struct ifnet @@ -7481,33 +7481,33 @@ Label destruction o *mbuflabel - + &mac.thead; - + cred Subject credential - + ifnet Network interface - + ifnetlabel Policy label for ifnet - + mbuf Object; mbuf to be sent - + mbuflabel Policy label for @@ -7516,7 +7516,7 @@ Label destruction o - + Determine whether the network interface can transmit the passed mbuf. Return 0 for success, or an errno value for failure. @@ -7524,15 +7524,15 @@ Label destruction o mismatch, or EPERM for lack of privilege. - + <function>&mac.mpo;_check_socket_deliver</function> - + int &mac.mpo;_check_socket_deliver - + struct ucred *cred struct ifnet @@ -7545,33 +7545,33 @@ Label destruction o *mbuflabel - + &mac.thead; - + cred Subject credential - + ifnet Network interface - + ifnetlabel Policy label for ifnet - + mbuf Object; mbuf to be delivered - + mbuflabel Policy label for @@ -7580,7 +7580,7 @@ Label destruction o - + Determine whether the socket may receive the datagram stored in the passed mbuf header. Return 0 for success, or an @@ -7589,15 +7589,15 @@ Label destruction o or EPERM for lack of privilege. - + <function>&mac.mpo;_check_socket_visible</function> - + int &mac.mpo;_check_socket_visible - + struct ucred *cred struct socket @@ -7606,23 +7606,23 @@ Label destruction o *socketlabel - + &mac.thead; - + cred Subject credential Immutable - + so Object; socket - + socketlabel Policy label for @@ -7631,7 +7631,7 @@ Label destruction o - + Determine whether the subject credential cred can "see" the passed socket (socket) using system monitoring functions, such as those employed by @@ -7901,10 +7901,10 @@ Label destruction o the specified &man.sysctl.3; transaction. - + Label Management Calls - + Relabel events occur when a user process has requested that the label on an object be modified. A two-phase update occurs: first, an access control check will be performed to @@ -7915,13 +7915,13 @@ Label destruction o Memory allocation during relabel is discouraged, as relabel calls are not permitted to fail (failure should be reported earlier in the relabel check). - + - + Userland Architecture - + The TrustedBSD MAC Framework includes a number of policy-agnostic elements, including MAC library interfaces for abstractly managing labels, modifications to the system @@ -8003,7 +8003,7 @@ Label destruction o Conclusion - + The TrustedBSD MAC framework permits kernel modules to augment the system security policy in a highly integrated manner. They may do this based on existing object properties, diff --git a/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.sgml index 38a747401d..3d9715a6bf 100644 --- a/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.sgml @@ -40,7 +40,7 @@ Wolfgang Stanglmeier and Stefan Esser sym (/sys/dev/sym/sym_hipd.c) by - Gerard Roudier + Gerard Roudier aic7xxx (/sys/dev/aic7xxx/aic7xxx.c) by Justin @@ -145,7 +145,7 @@ struct cam_sim *sim; if(( sim = cam_sim_alloc(action_func, poll_func, driver_name, - softc, unit, max_dev_transactions, + softc, unit, max_dev_transactions, max_tagged_dev_transactions, devq) )==NULL) { cam_simq_free(devq); error; /* some code to handle the error */ @@ -563,7 +563,7 @@ tag_action - the kind of tag to use: - + CAM_TAG_ACTION_NONE - do not use tags for this transaction @@ -717,10 +717,10 @@ implemented, it is actively used by CAM. int rv; - + initialize_hcb_for_data(hcb); - if((!(ccb_h->flags & CAM_SCATTER_VALID)) { + if((!(ccb_h->flags & CAM_SCATTER_VALID)) { /* single buffer */ if(!(ccb_h->flags & CAM_DATA_PHYS)) { rv = add_virtual_chunk(hcb, csio->data_ptr, csio->dxfer_len, dir); @@ -739,7 +739,7 @@ } else if (!(ccb_h->flags & CAM_DATA_PHYS)) { /* SG buffer pointers are virtual */ for (i = 0; i < csio->sglist_cnt; i++) { - rv = add_virtual_chunk(hcb, segs[i].ds_addr, + rv = add_virtual_chunk(hcb, segs[i].ds_addr, segs[i].ds_len, dir); if (rv != CAM_REQ_CMP) break; @@ -747,7 +747,7 @@ } else { /* SG buffer pointers are physical */ for (i = 0; i < csio->sglist_cnt; i++) { - rv = add_physical_chunk(hcb, segs[i].ds_addr, + rv = add_physical_chunk(hcb, segs[i].ds_addr, segs[i].ds_len, dir); if (rv != CAM_REQ_CMP) break; @@ -780,7 +780,7 @@ to the hardware and return, the rest will be done by the interrupt handler (or timeout handler). - ccb_h->timeout_ch = timeout(xxx_timeout, (caddr_t) hcb, + ccb_h->timeout_ch = timeout(xxx_timeout, (caddr_t) hcb, (ccb_h->timeout * hz) / 1000); /* convert milliseconds to ticks */ put_hcb_into_hardware_queue(hcb); return; @@ -803,7 +803,7 @@ } free_hcb(hcb); /* also removes hcb from any internal lists */ } - ccb->ccb_h.status = status | + ccb->ccb_h.status = status | (ccb->ccb_h.status & ~(CAM_STATUS_MASK|CAM_SIM_QUEUED)); xpt_done(ccb); } @@ -880,7 +880,7 @@ xpt_free_path(path); } - for(lun=0; lun <= OUR_MAX_SUPPORTED_LUN; lun++) + for(lun=0; lun <= OUR_MAX_SUPPORTED_LUN; lun++) for(h = softc->first_discon_hcb[targ][lun]; h != NULL; h = hh) { hh=h->next; free_hcb_and_ccb_done(h, h->ccb, CAM_SCSI_BUS_RESET); @@ -933,7 +933,7 @@ hcb = NULL; /* We assume that softc->first_hcb is the head of the list of all - * HCBs associated with this bus, including those enqueued for + * HCBs associated with this bus, including those enqueued for * processing, being processed by hardware and disconnected ones. */ for(h = softc->first_hcb; h != NULL; h = h->next) { @@ -945,7 +945,7 @@ if(hcb == NULL) { /* no such CCB in our queue */ - ccb->ccb_h.status = CAM_PATH_INVALID; + ccb->ccb_h.status = CAM_PATH_INVALID; xpt_done(ccb); return; } @@ -965,7 +965,7 @@ int hstatus; /* shown as a function, in case special action is needed to make - * this flag visible to hardware + * this flag visible to hardware */ set_hcb_flags(hcb, HCB_BEING_ABORTED); @@ -996,7 +996,7 @@ case HCB_BEING_TRANSFERRED: untimeout(xxx_timeout, (caddr_t) hcb, abort_ccb->ccb_h.timeout_ch); - abort_ccb->ccb_h.timeout_ch = + abort_ccb->ccb_h.timeout_ch = timeout(xxx_timeout, (caddr_t) hcb, 10 * hz); abort_ccb->ccb_h.status = CAM_REQ_ABORTED; /* ask the controller to abort that HCB, then generate @@ -1017,7 +1017,7 @@ case HCB_DISCONNECTED: untimeout(xxx_timeout, (caddr_t) hcb, abort_ccb->ccb_h.timeout_ch); - abort_ccb->ccb_h.timeout_ch = + abort_ccb->ccb_h.timeout_ch = timeout(xxx_timeout, (caddr_t) hcb, 10 * hz); put_abort_message_into_hcb(hcb); put_hcb_at_the_front_of_hardware_queue(hcb); @@ -1051,7 +1051,7 @@ } if(xxx_abort_ccb(abort_ccb, CAM_REQ_ABORTED) < 0) /* no such CCB in our queue */ - ccb->ccb_h.status = CAM_PATH_INVALID; + ccb->ccb_h.status = CAM_PATH_INVALID; else ccb->ccb_h.status = CAM_REQ_CMP; xpt_done(ccb); @@ -1061,7 +1061,7 @@ XPT_SET_TRAN_SETTINGS - explicitly set values of SCSI transfer settings - The arguments are transferred in the instance struct ccb_trans_setting cts + The arguments are transferred in the instance struct ccb_trans_setting cts of the union ccb: @@ -1078,10 +1078,10 @@ of the union ccb: - bus width CCB_TRANS_DISC_VALID - - set enable/disable disconnection + set enable/disable disconnection CCB_TRANS_TQ_VALID - set - enable/disable tagged queuing + enable/disable tagged queuing flags - consists of two parts, binary arguments and identification of @@ -1177,10 +1177,10 @@ of the union ccb: } if(flags & CCB_TRANS_CURRENT_SETTINGS) { if(flags & CCB_TRANS_SYNC_RATE_VALID) - softc->goal_sync_period[targ] = + softc->goal_sync_period[targ] = max(cts->sync_period, OUR_MIN_SUPPORTED_PERIOD); if(flags & CCB_TRANS_SYNC_OFFSET_VALID) - softc->goal_sync_offset[targ] = + softc->goal_sync_offset[targ] = min(cts->sync_offset, OUR_MAX_SUPPORTED_OFFSET); if(flags & CCB_TRANS_BUS_WIDTH_VALID) softc->goal_bus_width[targ] = min(cts->bus_width, OUR_BUS_WIDTH); @@ -1451,7 +1451,7 @@ CCB as done. gets just the device unit number. So the poll routine would normally look as: -static void +static void xxx_poll(struct cam_sim *sim) { xxx_intr((struct xxx_softc *)cam_sim_softc(sim)); /* for PCI device */ @@ -1459,7 +1459,7 @@ xxx_poll(struct cam_sim *sim) or -static void +static void xxx_poll(struct cam_sim *sim) { xxx_intr(cam_sim_unit(sim)); /* for ISA device */ @@ -1539,7 +1539,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< section. To make sure that the interrupt level will be always restored a wrapper function can be defined, like: - static void + static void xxx_action(struct cam_sim *sim, union ccb *ccb) { int s; @@ -1548,7 +1548,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< splx(s); } - static void + static void xxx_action1(struct cam_sim *sim, union ccb *ccb) { ... process the request ... @@ -1609,7 +1609,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< xpt_free_path(path); } - for(lun=0; lun <= OUR_MAX_SUPPORTED_LUN; lun++) + for(lun=0; lun <= OUR_MAX_SUPPORTED_LUN; lun++) for(h = softc->first_discon_hcb[targ][lun]; h != NULL; h = hh) { hh=h->next; if(fatal) @@ -1628,9 +1628,9 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< * it is really fast */ if(!fatal) { - reinitialize_controller_without_scsi_reset(softc); + reinitialize_controller_without_scsi_reset(softc); } else { - reinitialize_controller_with_scsi_reset(softc); + reinitialize_controller_with_scsi_reset(softc); } schedule_next_hcb(softc); return; @@ -1690,7 +1690,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< calculate_residue(hcb); if( (hcb->ccb->ccb_h.flags & CAM_DIS_AUTOSENSE)==0 - && ( scsi_status == CHECK_CONDITION + && ( scsi_status == CHECK_CONDITION || scsi_status == COMMAND_TERMINATED) ) { /* start auto-SENSE */ hcb->flags |= DOING_AUTOSENSE; @@ -1717,7 +1717,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< /* revert to 8-bit bus */ softc->current_bus_width[targ] = softc->goal_bus_width[targ] = 8; /* report the event */ - neg.bus_width = 8; + neg.bus_width = 8; neg.valid = CCB_TRANS_BUS_WIDTH_VALID; xpt_async(AC_TRANSFER_NEG, hcb->ccb.ccb_h.path_id, &neg); continue_current_hcb(softc); @@ -1727,9 +1727,9 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< int wd; wd = get_target_bus_width_request(softc); - if(wd <= softc->goal_bus_width[targ]) { + if(wd <= softc->goal_bus_width[targ]) { /* answer is acceptable */ - softc->current_bus_width[targ] = + softc->current_bus_width[targ] = softc->goal_bus_width[targ] = neg.bus_width = wd; /* report the event */ @@ -1751,7 +1751,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< if(wd != softc->current_bus_width[targ]) { /* the bus width has changed */ - softc->current_bus_width[targ] = + softc->current_bus_width[targ] = softc->goal_bus_width[targ] = neg.bus_width = wd; /* report the event */ @@ -1779,10 +1779,10 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< case UNEXPECTED_DISCONNECT: if(requested_abort(hcb)) { - /* abort affects all commands on that target+LUN, so + /* abort affects all commands on that target+LUN, so * mark all disconnected HCBs on that target+LUN as aborted too */ - for(h = softc->first_discon_hcb[hcb->target][hcb->lun]; + for(h = softc->first_discon_hcb[hcb->target][hcb->lun]; h != NULL; h = hh) { hh=h->next; free_hcb_and_ccb_done(h, h->ccb, CAM_REQ_ABORTED); @@ -1791,12 +1791,12 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< } else if(requested_bus_device_reset(hcb)) { int lun; - /* reset affects all commands on that target, so + /* reset affects all commands on that target, so * mark all disconnected HCBs on that target+LUN as reset */ - for(lun=0; lun <= OUR_MAX_SUPPORTED_LUN; lun++) - for(h = softc->first_discon_hcb[hcb->target][lun]; + for(lun=0; lun <= OUR_MAX_SUPPORTED_LUN; lun++) + for(h = softc->first_discon_hcb[hcb->target][lun]; h != NULL; h = hh) { hh=h->next; free_hcb_and_ccb_done(h, h->ccb, CAM_SCSI_BUS_RESET); @@ -1806,10 +1806,10 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< xpt_async(AC_SENT_BDR, hcb->ccb->ccb_h.path_id, NULL); /* this was the CAM_RESET_DEV request itself, it is completed */ - ccb_status = CAM_REQ_CMP; + ccb_status = CAM_REQ_CMP; } else { calculate_residue(hcb); - ccb_status = CAM_UNEXP_BUSFREE; + ccb_status = CAM_UNEXP_BUSFREE; /* request the further code to freeze the queue */ hcb->ccb->ccb_h.status |= CAM_DEV_QFRZN; lun_to_freeze = hcb->lun; @@ -1821,11 +1821,11 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< case TAGS_REJECTED: /* report the event */ - neg.flags = 0 & ~CCB_TRANS_TAG_ENB; + neg.flags = 0 & ~CCB_TRANS_TAG_ENB; neg.valid = CCB_TRANS_TQ_VALID; xpt_async(AC_TRANSFER_NEG, hcb->ccb.ccb_h.path_id, &neg); - ccb_status = CAM_MSG_REJECT_REC; + ccb_status = CAM_MSG_REJECT_REC; /* request the further code to freeze the queue */ hcb->ccb->ccb_h.status |= CAM_DEV_QFRZN; lun_to_freeze = hcb->lun; @@ -1835,21 +1835,21 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< basically limited to setting the CCB status: case SELECTION_TIMEOUT: - ccb_status = CAM_SEL_TIMEOUT; + ccb_status = CAM_SEL_TIMEOUT; /* request the further code to freeze the queue */ hcb->ccb->ccb_h.status |= CAM_DEV_QFRZN; lun_to_freeze = CAM_LUN_WILDCARD; break; case PARITY_ERROR: - ccb_status = CAM_UNCOR_PARITY; + ccb_status = CAM_UNCOR_PARITY; break; case DATA_OVERRUN: case ODD_WIDE_TRANSFER: - ccb_status = CAM_DATA_RUN_ERR; + ccb_status = CAM_DATA_RUN_ERR; break; default: /* all other errors are handled in a generic way */ - ccb_status = CAM_REQ_CMP_ERR; + ccb_status = CAM_REQ_CMP_ERR; /* request the further code to freeze the queue */ hcb->ccb->ccb_h.status |= CAM_DEV_QFRZN; lun_to_freeze = CAM_LUN_WILDCARD; @@ -1868,7 +1868,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< for(h = softc->first_queued_hcb; h != NULL; h = hh) { hh = h->next; - if(targ == h->targ + if(targ == h->targ && (lun_to_freeze == CAM_LUN_WILDCARD || lun_to_freeze == h->lun) ) free_hcb_and_ccb_done(h, h->ccb, CAM_REQUEUE_REQ); } @@ -1901,7 +1901,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)< this resource would be some intra-controller hardware resource for which the controller does not generate an interrupt when it becomes available. - + CAM_UNCOR_PARITY - unrecovered parity error occurred diff --git a/en_US.ISO8859-1/books/arch-handbook/sound/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/sound/chapter.sgml index 2f7089b164..ce578f7228 100644 --- a/en_US.ISO8859-1/books/arch-handbook/sound/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/sound/chapter.sgml @@ -18,12 +18,12 @@ Sound subsystem - + Introduction sound subsystem - + The FreeBSD sound subsystem cleanly separates generic sound handling issues from device-specific ones. This makes it easier to add support for new hardware. @@ -53,7 +53,7 @@ Additional support for some common hardware interfaces (ac97), or shared hardware-specific code (ex: ISA DMA - routines). + routines). @@ -103,7 +103,7 @@ linkend="isa-driver"> ISA or PCI specific sections of the handbook for more information. - + However, sound drivers differ in some ways: @@ -169,7 +169,7 @@ resources. - + There are two possible methods to handle non-PnP devices: @@ -205,7 +205,7 @@ There are two main interfaces that a sound driver will usually provide: CHANNEL and either MIXER or AC97. - + The AC97 interface is a very small hardware access (register read/write) interface, implemented by drivers for hardware with an AC97 codec. In this case, the @@ -250,7 +250,7 @@ sndbuf_getsize() and is divided into fixed size blocks of sndbuf_getblksz() bytes. - + When playing, the general transfer mechanism is as follows (reverse the idea for recording): @@ -294,9 +294,9 @@ are initiated from the sound driver attach routine. (See the probe and attach section). - + static void * - xxxchannel_init(kobj_t obj, void *data, + xxxchannel_init(kobj_t obj, void *data, struct snd_dbuf *b, struct pcm_channel *c, int dir) { struct xxx_info *sc = data; @@ -343,7 +343,7 @@ xxxchannel_setformat() should set up the hardware for the specified channel for the specified sound format. - + static int xxxchannel_setformat(kobj_t obj, void *data, u_int32_t format) { @@ -395,7 +395,7 @@ Most sound drivers only take note of the block size here, to be used when an actual transfer will be started. - + static int xxxchannel_setblocksize(kobj_t obj, void *data, u_int32_t blocksize) { @@ -409,7 +409,7 @@ The function returns the possibly adjusted block size. In case the block size is indeed changed, sndbuf_resize() should be called to - adjust the buffer. + adjust the buffer. @@ -421,8 +421,8 @@ xxxchannel_trigger() is called by pcm to control data transfer - operations in the driver. - + operations in the driver. + static int xxxchannel_trigger(kobj_t obj, void *data, int go) { @@ -461,7 +461,7 @@ - + If the driver uses ISA DMA, @@ -480,7 +480,7 @@ be called by chn_intr(), and this is how pcm knows where it can transfer new data. - + @@ -491,7 +491,7 @@ unloaded, and should be implemented if the channel data structures are dynamically allocated or if sndbuf_alloc() was not used for buffer - allocation. + allocation. @@ -536,7 +536,7 @@ The MIXER interface - + mixer_init @@ -557,7 +557,7 @@ [Set appropriate bits in v for record mixers] mix_setrecdevs(m, v) - return 0; + return 0; } @@ -583,7 +583,7 @@ level for one mixer device. static int - xxxmixer_set(struct snd_mixer *m, unsigned dev, + xxxmixer_set(struct snd_mixer *m, unsigned dev, unsigned left, unsigned right) { struct sc_info *sc = mix_getdevinfo(m); @@ -614,7 +614,7 @@ xxxmixer_setrecsrc() sets the recording source device. - + static int xxxmixer_setrecsrc(struct snd_mixer *m, u_int32_t src) { @@ -650,7 +650,7 @@ xxxmixer_reinit() should ensure that the mixer hardware is powered up and any settings not controlled by mixer_set() or - mixer_setrecsrc() are restored. + mixer_setrecsrc() are restored. diff --git a/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.sgml index 7f0a8db63e..e208d6c3ca 100644 --- a/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.sgml @@ -68,7 +68,7 @@ sysinit_elem_order. pseudo-devices - + There are currently two uses for SYSINIT. Function dispatch at system startup and kernel module loads, and function dispatch at system shutdown and kernel module unload. Kernel subsystems diff --git a/en_US.ISO8859-1/books/arch-handbook/usb/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/usb/chapter.sgml index e51b9dc83d..32aeecd6f7 100644 --- a/en_US.ISO8859-1/books/arch-handbook/usb/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/usb/chapter.sgml @@ -93,7 +93,7 @@ stack in FreeBSD/NetBSD. It is recommended however to read it together with the relevant specifications mentioned in the references below. - + Structure of the USB Stack @@ -112,7 +112,7 @@ resource management. This services layer also controls the default pipes and the device requests transferred over them. - + The top layer contains the individual drivers supporting specific (classes of) devices. These drivers implement the protocol that is used over the pipes other than the default @@ -241,7 +241,7 @@ OHCI - USBOHCI + USBOHCI Programming an OHCI host controller is much simpler. The controller assumes that a set of endpoints is available, and is aware of scheduling priorities and the ordering of the @@ -468,7 +468,7 @@ Device probe and attach - USBprobe + USBprobe After the notification by the hub that a new device has been connected, the service layer switches on the port, providing the device with 100 mA of current. At this point the device is in @@ -508,7 +508,7 @@ Device disconnect and detach - USBdisconnect + USBdisconnect A device driver should expect to receive errors during any transaction with the device. The design of USB supports and encourages the disconnection of devices at any point in diff --git a/en_US.ISO8859-1/books/arch-handbook/vm/chapter.sgml b/en_US.ISO8859-1/books/arch-handbook/vm/chapter.sgml index be9c3d728c..d70bd33557 100644 --- a/en_US.ISO8859-1/books/arch-handbook/vm/chapter.sgml +++ b/en_US.ISO8859-1/books/arch-handbook/vm/chapter.sgml @@ -85,7 +85,7 @@ actually is. This leads to better decisions being made as to when to launder or swap-out a page. - + The unified buffer cache—<literal>vm_object_t</literal> @@ -112,10 +112,10 @@ implements the perceived sharing of the same page across multiple instances. - + Filesystem I/O—<literal>struct buf</literal> - + vnode vnode-backed VM objects, such as file-backed objects, generally need to maintain their own clean/dirty info independent from the VM @@ -148,10 +148,10 @@ few thousand filesystem buffers available, this is not usually a problem. - + Mapping Page Tables—<literal>vm_map_t, vm_entry_t</literal> - + page tables FreeBSD separates the physical page table topology from the VM system. All hard per-process page tables can be reconstructed on the @@ -175,10 +175,10 @@ vm_page_t and thus give us buffer cache unification across the board. - + KVM Memory Mapping - + FreeBSD uses KVM to hold various kernel structures. The single largest entity held in KVM is the filesystem buffer cache. That is, mappings relating to struct buf entities. @@ -197,10 +197,10 @@ of structure. You can use vmstat -m to get an overview of current KVM utilization broken down by zone. - + Tuning the FreeBSD VM system - + A concerted effort has been made to make the FreeBSD kernel dynamically tune itself. Typically you do not need to mess with anything beyond the and diff --git a/en_US.ISO8859-1/books/bibliography/Makefile b/en_US.ISO8859-1/books/bibliography/Makefile index e0e4b1ed5e..2152970d57 100644 --- a/en_US.ISO8859-1/books/bibliography/Makefile +++ b/en_US.ISO8859-1/books/bibliography/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # @@ -12,7 +12,7 @@ FORMATS?= html INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # diff --git a/en_US.ISO8859-1/books/bibliography/book.sgml b/en_US.ISO8859-1/books/bibliography/book.sgml index 4209646f40..2159cad5fc 100644 --- a/en_US.ISO8859-1/books/bibliography/book.sgml +++ b/en_US.ISO8859-1/books/bibliography/book.sgml @@ -15,11 +15,11 @@ FreeBSD Bibliography - + The FreeBSD Documentation Project - + February 1999 - + 2001 The FreeBSD Documentation Project @@ -27,6 +27,6 @@ $FreeBSD$ - + &bibliography; diff --git a/en_US.ISO8859-1/books/corp-net-guide/book.sgml b/en_US.ISO8859-1/books/corp-net-guide/book.sgml index b1651a7f75..6ae99faa49 100644 --- a/en_US.ISO8859-1/books/corp-net-guide/book.sgml +++ b/en_US.ISO8859-1/books/corp-net-guide/book.sgml @@ -29,7 +29,7 @@ ENGLISH LANGUAGE EDITION ISBN: 0-201-70481-1 JAPANESE LANGUAGE EDITION ISBN: 4-89471-464-7 - + The eighth chapter of the book, The FreeBSD Corporate Networker's Guide is excerpted here with the permission @@ -291,7 +291,7 @@ | ======= | Server | ======= | +---------------------+ ,-----. +-----------+ | +---------------+ | | | -| Printer [ ]------------[ ] | Printserver | | |_____| +| Printer [ ]------------[ ] | Printserver | | |_____| +-----------+ Parallel | | Software | [ ]------_________ Cable | +---------------+ | / ::::::: \ +---------------------+ `---------' @@ -325,7 +325,7 @@ - + Fileserver ,----------------. @@ -525,7 +525,7 @@ `---------' Spool - Printserver + Printserver ,---------. PC | ======= | ,-----. | ======= | | | @@ -550,7 +550,7 @@ - + FreeBSD is an excellent platform to implement centralized printserving and print spooling. The rest of this chapter concentrates on the centralized print spooler model. Note that @@ -650,7 +650,7 @@ . This program must be active during client printing, and is usually placed in the Startup group. - + Organizations that want to use UNIX as a printserver to a group of Win31 clients without using a commercial or shareware LPR program have another option. The Microsoft Networking client for DOS used @@ -719,7 +719,7 @@ If you have vlm121_2.exe in a temporary directory, run it. This will extract a number of files. - + One of the files extracted is LSL.CO_ extract this file with the command nwunpack @@ -959,7 +959,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET For the protocol, leave the default of BSD LPR/LPD selected. - + Click on the Queue Properties, and make sure that the Print unfiltered is @@ -979,7 +979,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET Panel/Printers to bring up the Printers control panel of Windows. - + Make sure that the Use Print Manager button is checked, then highlight the printer driver and click @@ -991,7 +991,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET for the spool that was built and highlight this. Click OK. - + Minimize the Windows LPR Spooler. Copy the Windows LPR Spooler icon to the Startup group. Click @@ -1051,7 +1051,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET printer port monitor. The program is called ACITS LPR Remote Printing for Windows 95 and it is located at . - + ACITS stands for Academic Computing and Instructional Technologies Services. The ACITS LPR client includes software developed by the University of Texas at Austin and its contributors, @@ -1135,7 +1135,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET installation and then presents a Help screen that explains how to configure an LPR port. - + After the help screen closes, the program asks to reboot the system. Ensure that Yes is checked and @@ -1171,7 +1171,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET UNIX system that the client spools through— mainprinter.ayedomain.com. - + Type in the Printer/Queue name and click OK. (Some versions have a "Verify Printer @@ -1190,7 +1190,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET hosts.lpd. - + If the printer is PostScript and cannot print ASCII, make sure that the "No banner page control flag" is checked to turn @@ -1220,7 +1220,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET unchecked. This option is used only in rare mainframe spooling circumstances. - + Click OK, then click the Spool Settings button at the properties @@ -1281,7 +1281,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET Printing" should be listed as well as "TCP/IP Protocol". If it is, stop here; otherwise continue. - + Click the Add Software button to get the Add Network Software dialog box @@ -1291,14 +1291,14 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET Click the down arrow and select TCP/IP Protocol and related components. Click Continue. - + Check the "TCP/IP Network Printing Support" box and click Continue. LPR printing is now installed. Follow the instructions to reboot to save changes. - + To install the LPR client and daemon program under Windows NT 4, use the following instructions. The TCP/IP protocol should be installed beforehand and you must be logged in to the NT system as @@ -1312,7 +1312,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET Panel, and double-click on Network to open it up. - + Click on the Services tab. Microsoft TCP/IP Printing should be listed. @@ -1335,7 +1335,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET - + Once LPR printing has been installed, the Printer icon or icons must be created on the NT system so that applications can print. Since this printer driver does all job formatting before passing the @@ -1400,7 +1400,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET Double-click Add Printer to start the wizard. - + Select the My Computer radio button, not the Network Print Server button and click Next. (The @@ -1408,7 +1408,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET managed on the local NT system. Microsoft used confusing terminology here. - + Click Add Port and select LPR Port, then click New Port. @@ -1418,7 +1418,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET Enter the hostname and print queue for the FreeBSD printserver and click OK. - + Click Next and select the correct printer driver. Continue until the printer is set up. @@ -1464,7 +1464,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET Run Registry Editor (REGEDT32.EXE) - + From the HKEY_LOCAL_MACHINE subtree, go to the following key: @@ -1507,7 +1507,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET - + Under Windows NT 3.51, the change is: @@ -1562,7 +1562,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET Create an LPD key at the same level as the LPDSVC key. - + Click the LPDSVC Key, click Save Key from the Registry menu, @@ -1692,7 +1692,7 @@ Bind 3C5X9 #1 Ethernet_II LAN_NET OK. - + This could also have been printed with /usr/bin/lpr on a UNIX command prompt. The file prints Test Page and some printer statistics @@ -1861,7 +1861,7 @@ NEC|NEC Silentwriter 95 PostScript printer:\ &prompt.user; su root &prompt.root; cd /var/spool/output &prompt.root; mkdir NEC -&prompt.root; chown bin NEC +&prompt.root; chown bin NEC &prompt.root; chgrp daemon NEC &prompt.root; chmod 755 NEC @@ -1906,11 +1906,11 @@ NEC|NEC Silentwriter 95 PostScript printer:\ /usr/var. - + In addition to spools, the following other capabilities are usually placed in a production /etc/printcap file. - + The entry fo prints a form feed when the printer is opened. It is handy for HPPCL (HP LaserJets) or other non-PostScript printers that are located behind electronic print @@ -1950,7 +1950,7 @@ NEC|NEC Silentwriter 95 PostScript printer:\ Printing to hardware print server boxes or remote print servers. - + Hardware print server boxes, such as the HP JetDirect internal and external cards, need some additional capabilities defined in the /etc/printcap entry; rp, for @@ -2203,7 +2203,7 @@ lp|local line printer:\ The <literal>pr</literal> filter - + Although most filters are built by scripts or programs and are added to the UNIX machine by the administrator, there is one filter that is supplied with the FreeBSD operating system is very @@ -2465,7 +2465,7 @@ lpnobanner|local line printer, PostScript, no banner:\ or pits one department against another. - + The only justification I've ever seen for running accounting on corporate printers is using the accounting system to automate reminders to the administrator to replace paper, or toner. Aside from @@ -2524,7 +2524,7 @@ lpnobanner|local line printer, PostScript, no banner:\ | ======= | FreeBSD Server | ======= | +---------------------+ ,-----. +-----------+ | +---------------+ | | | -| Printer [ ]------------[ ] | Samba | | |_____| +| Printer [ ]------------[ ] | Samba | | |_____| +-----------+ Parallel | | Software | [ ]------_________ Cable | +---------------+ | / ::::::: \ | | `---------' @@ -2561,7 +2561,7 @@ lpnobanner|local line printer, PostScript, no banner:\ through Samba are the "raw" print queues that are set up by the administrator to allow incoming preformatted print jobs. - + Windows clients that print to Samba print queues on the UNIX system can view and cancel print jobs in the print queue. They cannot pause them, however, which is a difference between Novell and @@ -2933,7 +2933,7 @@ disable turn a spooling queue off lpc> help status status show status of daemon and queue lpc> exit - + In the second mode of operation the lpc command is just run by itself, followed by the command and the print queue name. Following is a sample output: @@ -3047,7 +3047,7 @@ Rank Owner Job Files Total Size will also want to get the file , and unzip and untar it into a temporary directory. - + Extracting the archive file creates a directory structure under the gs5.03 subdirectory. To install ghostscript in the /etc/printcap file, read the @@ -3105,7 +3105,7 @@ Rank Owner Job Files Total Size example, the following line is for a monochrome LaserJet: ") | gs -q -dNOPAUSE -sDEVICE=${device} \" - + Don't remove anything else. Exit the editor, and save the unix-lpr.sh file. diff --git a/en_US.ISO8859-1/books/design-44bsd/book.sgml b/en_US.ISO8859-1/books/design-44bsd/book.sgml index 2ffc52abec..47a1050be3 100644 --- a/en_US.ISO8859-1/books/design-44bsd/book.sgml +++ b/en_US.ISO8859-1/books/design-44bsd/book.sgml @@ -11,7 +11,7 @@ The Design and Implementation of the 4.4BSD Operating System - + Marshall @@ -36,12 +36,12 @@ Quarterman - + 1996 Addison-Wesley Longman, Inc - + @@ -65,13 +65,13 @@ $FreeBSD$ - + Design Overview of 4.4BSD - + 4.4BSD Facilities and the Kernel - + The 4.4BSD kernel provides four basic facilities: processes, a filesystem, @@ -79,7 +79,7 @@ system startup. This section outlines where each of these four basic services is described in this book. - + Processes constitute a thread of control in an address space. @@ -91,7 +91,7 @@ this memory management is discussed in Chapter 5. - + The user interface to the filesystem and devices is similar; common aspects are discussed in @@ -110,7 +110,7 @@ the subject of Chapter 10. - + Communication mechanisms provided by traditional UNIX systems include simplex reliable byte streams between related processes (see pipes, @@ -132,7 +132,7 @@ Chapter 13 describes a particular networking implementation in detail. - + Any real operating system has operational issues, such as how to start it running. @@ -146,7 +146,7 @@ We shall define terms, mention basic system calls, and explore historical developments. Finally, we shall give the reasons for many major design decisions. - + The Kernel @@ -191,7 +191,7 @@ this division of functionality is more than just a logical one. Services such as filesystems and networking protocols are implemented as client application processes of the nucleus or kernel. - + The 4.4BSD kernel is not partitioned into multiple processes. This basic design decision was made in the earliest versions of UNIX. @@ -209,7 +209,7 @@ The current trend in operating-systems research is to reduce the kernel size by placing such services in user space. - + Users ordinarily interact with the system through a command-language interpreter, called a shell, @@ -217,7 +217,7 @@ Such programs and the shell are implemented with processes. Details of such programs are beyond the scope of this book, which instead concentrates almost exclusively on the kernel. - + Sections 2.3 and 2.4 describe the services provided by the 4.4BSD kernel, and give an overview of the latter's design. @@ -225,65 +225,65 @@ services as they appear in 4.4BSD. - + Kernel Organization - + In this section, we view the organization of the 4.4BSD kernel in two ways: - + As a static body of software, categorized by the functionality offered by the modules that make up the kernel - + By its dynamic operation, categorized according to the services provided to users - + The largest part of the kernel implements the system services that applications access through system calls. In 4.4BSD, this software has been organized according to the following: - + Basic kernel facilities: timer and system-clock handling, descriptor management, and process management - + Memory-management support: paging and swapping - + Generic system interfaces: the I/O, control, and multiplexing operations performed on descriptors - + The filesystem: files, directories, pathname translation, file locking, and I/O buffer management - + Terminal-handling support: the terminal-interface driver and terminal line disciplines - + Interprocess-communication facilities: sockets - + Support for network communication: communication protocols and @@ -301,7 +301,7 @@ Percentage of kernel - + total machine independent @@ -309,50 +309,50 @@ 80.4 - + headers 9,393 4.6 - + initialization 1,107 0.6 - + kernel facilities 8,793 4.4 - + generic interfaces 4,782 2.4 - + interprocess communication 4,540 2.2 - + terminal handling 3,911 1.9 - + virtual memory 11,813 5.8 - + vnode management 7,954 @@ -364,67 +364,67 @@ 6,550 3.2 - + fast filestore 4,365 2.2 - + log-structure filestore 4,337 2.1 - + memory-based filestore 645 0.3 - + cd9660 filesystem 4,177 2.1 - + miscellaneous filesystems (10) 12,695 6.3 - + network filesystem 17,199 8.5 - + network communication 8,630 4.3 - + internet protocols 11,984 5.9 - + ISO protocols 23,924 11.8 - + X.25 protocols 10,626 5.3 - + XNS protocols 5,192 @@ -433,10 +433,10 @@
- + Most of the software in these categories is machine independent and is portable across different hardware architectures. - + The machine-dependent aspects of the kernel are isolated from the mainstream code. In particular, none of the machine-independent code contains @@ -445,16 +445,16 @@ the machine-independent code calls an architecture-dependent function that is located in the machine-dependent code. The software that is machine dependent includes - + Low-level system-startup actions - + Trap and fault handling - + Low-level manipulation of the run-time context of a process @@ -463,16 +463,16 @@ Configuration and initialization of hardware devices - + Run-time support for I/O devices - + Machine-dependent software for the HP300 in the 4.4BSD kernel - + @@ -496,7 +496,7 @@ 1,562 0.8 - + device driver headers 3,495 @@ -508,25 +508,25 @@ 17,506 8.7 - + virtual memory 3,087 1.5 - + other machine dependent 6,287 3.1 - + routines in assembly language 3,014 1.5 - + HP/UX compatibility 4,683 @@ -535,7 +535,7 @@
- + summarizes the machine-independent software that constitutes the 4.4BSD kernel for the HP300. The numbers in column 2 are for lines of C source code, @@ -549,7 +549,7 @@ HP/UX and device support, accounts for a minuscule 6.9 percent of the kernel. - + Only a small part of the kernel is devoted to initializing the system. This code is used when the system is @@ -570,10 +570,10 @@ scattered throughout, and it usually appears in places logically associated with what is being initialized. - + Kernel Services - + The boundary between the kernel- and user-level code is enforced by hardware-protection facilities provided by the underlying hardware. The kernel operates in a separate address space that is inaccessible to @@ -600,7 +600,7 @@ from the user process to a kernel buffer while the process waits, but will usually return from the system call before the kernel buffer is written to the disk. - + A system call usually is implemented as a hardware trap that changes the CPU's execution mode and the current address-space mapping. @@ -625,7 +625,7 @@ is stored in the global variable errno, and the function that executed the system call returns the value -1. - + User applications and the kernel operate independently of each other. 4.4BSD does not store I/O control blocks or other @@ -637,7 +637,7 @@ such as suspending a process while another is running, invisible to the processes involved. - + Process Management @@ -663,7 +663,7 @@ This value is used by the kernel to identify a process when reporting status changes to a user, and by a user when referencing a process in a system call. - + The kernel creates a process by duplicating the context of another process. The new process is termed a child process @@ -674,10 +674,10 @@ the process's system state managed by the kernel. Important components of the kernel state are described in Chapter 4. - +
Process lifecycle - + @@ -694,13 +694,13 @@ | child process |------->| child process |------->| zombie process | +----------------+ +----------------+ +----------------+ - + Process-management system calls
- + The process lifecycle is depicted in . A process may create a new process that is a copy of the original by using the @@ -740,7 +740,7 @@ or use an intermediate file. Interprocess communication is discussed extensively in Chapter 11. - + A process can suspend execution until any of its child processes terminate using the wait @@ -761,7 +761,7 @@ init: see Sections 3.1 and 14.6). - + The details of how the kernel creates and destroys processes are given in Chapter 5. @@ -798,7 +798,7 @@ (perhaps after setting a global variable). If the handler returns, the signal is unblocked and can be generated (and caught) again. - + Alternatively, a process may specify that a signal is to be ignored, or that a default action, as determined by the kernel, is to be taken. @@ -807,7 +807,7 @@ core file that contains the current memory image of the process for use in postmortem debugging. - + Some signals cannot be caught or ignored. These signals include SIGKILL, @@ -838,7 +838,7 @@ The detailed design and implementation of signals is described in Section 4.7. - + Process Groups and Sessions @@ -853,7 +853,7 @@ Creating a new process group is easy; the value of a new process group is ordinarily the process identifier of the creating process. - + The group of processes in a process group is sometimes referred to as a job @@ -872,7 +872,7 @@ A process in a specific process group may receive software interrupts affecting the group, causing the group to suspend or resume execution, or to be interrupted or terminated. - + A terminal has a process-group identifier assigned to it. This identifier is normally set to the identifier of a process group associated with the terminal. @@ -891,7 +891,7 @@ job control and is described, with process groups, in Section 4.8. - + Just as a set of related processes can be collected into a process group, a set of process groups can be collected into a session. @@ -901,7 +901,7 @@ and the jobs that that shell spawns. - + Memory Management @@ -947,7 +947,7 @@ done by the system are effectively transparent to processes. A process may, however, advise the system about expected future memory utilization as a performance aid. - + BSD Memory-Management Design Decisions @@ -975,7 +975,7 @@ . Several of the companies have implemented the revised interface . - + Once again, time pressure prevented 4.3BSD from providing an implementation of the interface. Although the latter could have been built into the existing @@ -1022,7 +1022,7 @@ Processes can also request private mappings of a file, which prevents any changes that they make from being visible to other processes mapping the file or being written back to the file itself. - + Another issue with the virtual-memory system is the way that information is passed into the kernel when a system call is made. 4.4BSD always copies data from the process address space @@ -1039,14 +1039,14 @@ Often, the user data are not page aligned and are not a multiple of the hardware page length. - + If the page is taken away from the process, it will no longer be able to reference that page. Some programs depend on the data remaining in the buffer even after those data have been written. - + If the process is allowed to keep a copy of the page (as it is in current 4.4BSD semantics), @@ -1061,7 +1061,7 @@ try to write new data to its output buffer, forcing the data to be copied anyway. - + When pages are remapped to new virtual-memory addresses, most memory-management hardware requires that the hardware @@ -1080,10 +1080,10 @@ interface provides a way for both of these tasks to be done without copying. - + Memory Management Inside the Kernel - + The kernel often does allocations of memory that are needed for only the duration of a single system call. In a user process, such short-term @@ -1099,7 +1099,7 @@ and thus could not be allocated on the stack even if there was space. An example is protocol-control blocks that remain throughout the duration of a network connection. - + Demands for dynamic memory allocation in the kernel have increased as more services have been added. A generalized memory allocator reduces the complexity @@ -1122,7 +1122,7 @@ of the piece of memory being freed. - + I/O System @@ -1159,7 +1159,7 @@ System V, Release 3 STREAMS, both of which can be accessed as traditional I/O streams.) - + Descriptors and I/O @@ -1186,12 +1186,12 @@ The close system call can be used to deallocate any descriptor. - + Descriptors represent underlying objects supported by the kernel, and are created by system calls specific to the type of object. In 4.4BSD, three kinds of objects can be represented by descriptors: files, pipes, and sockets. - + A @@ -1205,7 +1205,7 @@ system call. I/O devices are accessed as files. - + A pipe @@ -1232,7 +1232,7 @@ FIFO: One opens it for reading, the other for writing. - + A socket @@ -1252,7 +1252,7 @@ In systems before 4.2BSD, pipes were implemented using the filesystem; when sockets were introduced in 4.2BSD, pipes were reimplemented as sockets. - + The kernel keeps for each process a descriptor table, which is a table that the kernel uses @@ -1281,7 +1281,7 @@ system call. Ordinary files permit random access, and some devices do, as well. Pipes and sockets do not. - + When a process terminates, the kernel reclaims all the descriptors that were in use by that process. If the process was holding the final reference to an object, @@ -1289,7 +1289,7 @@ necessary cleanup actions, such as final deletion of a file or deallocation of a socket. - + Descriptor Management @@ -1338,7 +1338,7 @@ The resulting set of two processes and the connecting pipe is known as a pipeline. Pipelines can be arbitrarily long series of processes connected by pipes. - + The open, pipe, @@ -1370,10 +1370,10 @@ dup2 closes it before reusing it). - + Devices - + Hardware devices have filenames, and may be accessed by the user via the same system calls used for regular files. The kernel can distinguish a @@ -1423,7 +1423,7 @@ Familiar unstructured devices are communication lines, raster plotters, and unbuffered magnetic tapes and disks. Unstructured devices typically support large block I/O transfers. - + Unstructured files are called character devices because the first of these to be implemented were terminal device drivers. @@ -1445,10 +1445,10 @@ instead of there being a special or modified version of write. - + Socket IPC - + The 4.2BSD kernel introduced an IPC mechanism more flexible than pipes, based on @@ -1523,10 +1523,10 @@ sendmsg, respectively. - + Scatter/Gather I/O - + In addition to the traditional read and @@ -1585,10 +1585,10 @@ are used so much more frequently that the added cost of simulating them would not have been worthwhile. - + Multiple Filesystem Support - + With the expansion of network computing, it became desirable to support both local and remote filesystems. To simplify the support of multiple filesystems, @@ -1599,29 +1599,29 @@ appear much like the filesystem operations previously supported by the local filesystem. However, they may be supported by a wide range of filesystem types: - + Local disk-based filesystems - + Files imported using a variety of remote filesystem protocols - + Read-only CD-ROM filesystems - + Filesystems providing special-purpose interfaces -- for example, the /proc filesystem - + A few variants of 4.4BSD, such as FreeBSD, allow filesystems to be loaded dynamically when the filesystems are first referenced by the @@ -1635,7 +1635,7 @@ Section 6.7. - + Filesystems @@ -1668,7 +1668,7 @@ - + +-------+ | | @@ -1693,13 +1693,13 @@ +-------+ | | | | +-------+ +-------+ +-------+ - + A small filesystem tree - + a small one is shown in . Directories may contain subdirectories, and there is no inherent limitation to the depth with which directory nesting may occur. @@ -2021,7 +2021,7 @@ long filenames first introduced in 4.2BSD practically eliminate it. - + Filestores @@ -2080,7 +2080,7 @@ the storage packed as compactly as possible to minimize the usage of virtual-memory resources. - + Network Filesystem @@ -2138,7 +2138,7 @@ Chapter 9. - + Terminals @@ -2161,7 +2161,7 @@ input is processed to provide standard line-oriented editing functions, and input is presented to a process on a line-by-line basis. - + Screen editors and programs that communicate with other computers generally run in noncanonical mode @@ -2185,7 +2185,7 @@ generate signals and enable output flow control, but otherwise run in noncanonical mode; all other characters would be passed through to the process uninterpreted. - + On output, the terminal handler provides simple formatting services, including @@ -2199,11 +2199,11 @@ Inserting delays after certain standard control characters - + Expanding tabs - + Displaying echoed nongraphic ASCII @@ -2221,12 +2221,12 @@ Each of these formatting services can be disabled individually by a process through control requests. - + - + Interprocess Communication - + Interprocess communication in 4.4BSD is organized in communication domains. Domains currently supported include the @@ -2301,7 +2301,7 @@ must be presented with each send call. - + Another benefit is that the new interface is highly portable. Shortly after a test release was available from Berkeley, the socket interface had been ported to System III @@ -2317,10 +2317,10 @@ More recently, the socket interface was used as the basis for Microsoft's Winsock networking interface for Windows. - + Network Communication - + Some of the communication domains supported by the socket IPC @@ -2352,7 +2352,7 @@ over the same physical network as is used by newer applications running with a newer network protocol. - + Network Implementation @@ -2410,7 +2410,7 @@ arbitrary levels of routing with variable-length addresses and network masks. - + System Operation @@ -2437,13 +2437,13 @@ login shell is created from which the user can run additional processes. - + References Accetta et al, 1986 - + Mach: A New Kernel Foundation for UNIX Development" @@ -2487,13 +2487,13 @@ June 1986 - + Cheriton, 1988 - + The V Distributed System - + D. R. Cheriton @@ -2504,14 +2504,14 @@ Comm ACM, 31, 3 - + March 1988 Ewens et al, 1985 - + Tunis: A Distributed Multiprocessor Operating System @@ -2549,7 +2549,7 @@ Gingell et al, 1987 - + Virtual Memory Architecture in SunOS @@ -2579,10 +2579,10 @@ June 1987 - + Kernighan & Pike, 1984 - + The UNIX Programming Environment @@ -2590,7 +2590,7 @@ B. W. Kernighan - + R. Pike @@ -2604,13 +2604,13 @@ NJ
- + 1984 - + Macklem, 1994 - + The 4.4BSD NFS Implementation @@ -2639,7 +2639,7 @@ McKusick & Karels, 1988 - + Design of a General Purpose Memory Allocator for the 4.3BSD UNIX Kernel @@ -2665,10 +2665,10 @@ June 1998 - + McKusick et al, 1994 - + Berkeley Software Architecture Manual, 4.4BSD Edition @@ -2719,10 +2719,10 @@ Ritchie, 1988 - + Early Kernel Design private communication - + D. M. Ritchie @@ -2733,7 +2733,7 @@ Rosenblum & Ousterhout, 1992 - + The Design and Implementation of a Log-Structured File System @@ -2749,7 +2749,7 @@ Ousterhout - + 26-52 @@ -2763,7 +2763,7 @@ Rozier et al, 1988 - + Chorus Distributed Operating Systems @@ -2835,11 +2835,11 @@ Tevanian, 1987 - + Architecture-Independent Virtual Memory Management for Parallel and Distributed Environments: The Mach Approach Technical Report CMU-CS-88-106, - + A. Tevanian @@ -2854,7 +2854,7 @@ PA - + December 1987 diff --git a/en_US.ISO8859-1/books/dev-model/book.sgml b/en_US.ISO8859-1/books/dev-model/book.sgml index c7dcf42d30..db5625ebeb 100644 --- a/en_US.ISO8859-1/books/dev-model/book.sgml +++ b/en_US.ISO8859-1/books/dev-model/book.sgml @@ -147,8 +147,8 @@ During the Core elections in 2002, Mark Murray stated - I am opposed to a long rule-book, as that satisfies - lawyer-tendencies, and is counter to the technocentricity that + I am opposed to a long rule-book, as that satisfies + lawyer-tendencies, and is counter to the technocentricity that the project so badly needs. . @@ -317,7 +317,7 @@ - @@ -959,7 +959,7 @@ Hat currently held by: Robert Watson rwatson@FreeBSD.org. - +
@@ -2181,7 +2181,7 @@ .0 releases go into their own branch and are aimed mainly at early adopters. The branch then goes through a period of stabilisation, and it is not until the - decides the demands to stability have been satisfied that + decides the demands to stability have been satisfied that the branch becomes -STABLE and -CURRENT targets the next major version. While this for the majority has been with .1 versions, this is not a demand. diff --git a/en_US.ISO8859-1/books/developers-handbook/Makefile b/en_US.ISO8859-1/books/developers-handbook/Makefile index d9909550cc..ddc2582db4 100644 --- a/en_US.ISO8859-1/books/developers-handbook/Makefile +++ b/en_US.ISO8859-1/books/developers-handbook/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Build the FreeBSD Developers' Handbook. @@ -18,7 +18,7 @@ INSTALL_ONLY_COMPRESSED?= # Images IMAGES_EN= sockets/layers.eps sockets/sain.eps sockets/sainfill.eps sockets/sainlsb.eps sockets/sainmsb.eps sockets/sainserv.eps sockets/serv.eps sockets/serv2.eps sockets/slayers.eps -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # diff --git a/en_US.ISO8859-1/books/developers-handbook/book.sgml b/en_US.ISO8859-1/books/developers-handbook/book.sgml index 9324ad59fb..488bd04658 100644 --- a/en_US.ISO8859-1/books/developers-handbook/book.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/book.sgml @@ -15,11 +15,11 @@ FreeBSD Developers' Handbook - + The FreeBSD Documentation Project - + August 2000 - + 2000 2001 @@ -51,7 +51,7 @@ $FreeBSD$ - + Welcome to the Developers' Handbook. This manual is a work in progress and is the work of many @@ -73,7 +73,7 @@ Basics - &chap.introduction; + &chap.introduction; &chap.tools; &chap.secure; &chap.l10n; @@ -83,7 +83,7 @@ Interprocess Communication - + &chap.sockets; &chap.ipv6; @@ -96,14 +96,14 @@ &chap.kerneldebug; - + Architectures &chap.x86; - + Appendices diff --git a/en_US.ISO8859-1/books/developers-handbook/chapters.ent b/en_US.ISO8859-1/books/developers-handbook/chapters.ent index 4dea07bac3..936cb206c3 100644 --- a/en_US.ISO8859-1/books/developers-handbook/chapters.ent +++ b/en_US.ISO8859-1/books/developers-handbook/chapters.ent @@ -1,12 +1,12 @@ - diff --git a/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml index 04fd0928f0..4330107a73 100644 --- a/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml @@ -19,7 +19,7 @@ - + IPv6/IPsec Implementation This section should explain IPv6 and IPsec related implementation @@ -57,7 +57,7 @@ first try RFC2428, then RFC1639 if failed. - + RFC1886: DNS Extensions to support IPv6 @@ -366,7 +366,7 @@ sys/netinet6/nd6.c. If there are high demands we may provide sysctl knob for the variable. - + Scope Index @@ -1139,7 +1139,7 @@ FreeBSD 4.x configurable supported a interface, that interface has to be patched. - + If any of the drivers do not support the requirements, then the drivers can not be used for IPv6 and/or IPsec communication. If you find any problem with your card using IPv6/IPsec, then, please @@ -1208,7 +1208,7 @@ FreeBSD 4.x configurable supported | IPv6 TCP toward 2001:0DB8:0200:ffff::163.221.202.12 source IPv6 node - + &man.faithd.8; must be invoked on FAITH-relay dual stack node. @@ -1322,7 +1322,7 @@ FreeBSD 4.x configurable supported "old IPsec" specification documented in rfc182[5-9].txt - + "new IPsec" specification documented in rfc240[1-6].txt, rfc241[01].txt, rfc2451.txt diff --git a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml index 05730d6781..ad4dc2ccbd 100644 --- a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml @@ -23,7 +23,7 @@ - + Kernel Debugging @@ -63,7 +63,7 @@ cases will capture all necessary information present in a full memory dump, as most problems can be isolated only using kernel state. - + Configuring the Dump Device @@ -81,7 +81,7 @@ AUTO in HEAD, and changed to NO on RELENG_* branches (except for RELENG_7, which was left set to AUTO). - On &os; 9.0-RELEASE and later versions, + On &os; 9.0-RELEASE and later versions, bsdinstall will ask whether crash dumps should be enabled on the target system during the install process. @@ -813,7 +813,7 @@ Debugger (msg=0xf01b0383 "Boot flags requested debugger") but want the system to come back up unless you're on-hand to use the debugger for diagnostics, use this option. - + options KDB_TRACE: change the default value of the debug.trace_on_panic sysctl to 1, which diff --git a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml index f5c9ae75cb..7a1d5eb749 100644 --- a/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml @@ -22,7 +22,7 @@ Source Tree Guidelines and Policies - + This chapter documents various guidelines and policies in force for the FreeBSD source tree. @@ -35,11 +35,11 @@ styles described in &man.style.9; and &man.style.Makefile.5;. - + <makevar>MAINTAINER</makevar> on Makefiles ports maintainer - + If a particular portion of the &os; src/ distribution is being maintained by a person or group of persons, this is communicated through an entry in the @@ -90,7 +90,7 @@ - + @@ -112,9 +112,9 @@ Contributed Software - + contributed software - + Some parts of the FreeBSD distribution consist of software that is actively being maintained outside the FreeBSD project. For historical reasons, we call this contributed software. Some @@ -151,7 +151,7 @@ The repository bloat impact from a single character change can be rather dramatic. - + Vendor Imports with CVS @@ -182,7 +182,7 @@ FreeBSD-specific changes as possible. If there are any doubts on how to go about it, it is imperative that you ask first and not blunder ahead and hope it works out. - + Because of the previously mentioned design limitations with vendor branches, it is required that official patches from the vendor be applied to the original distributed sources and the result @@ -197,7 +197,7 @@ interest to FreeBSD in order to save space. Files containing copyright notices and release-note kind of information applicable to the remaining files shall not be removed. - + If it seems easier, the bmake Makefiles can be produced from the dist tree automatically by some utility, something which would hopefully make it @@ -209,27 +209,27 @@ In the src/contrib/file level directory, a file called FREEBSD-upgrade should be added and it should state things like: - + Which files have been left out. - + Where the original distribution was obtained from and/or the official master site. - + Where to send patches back to the original authors. - + Perhaps an overview of the FreeBSD-specific changes that have been made. - + Example wording from src/contrib/groff/FREEBSD-upgrade is below: @@ -260,7 +260,7 @@ Do not, under any circumstances, deviate from this procedure. To make local changes to groff, simply patch and commit to the main branch (aka HEAD). Never make local changes on the FSF branch. -All local changes should be submitted to Werner Lemberg <wl@gnu.org> or +All local changes should be submitted to Werner Lemberg <wl@gnu.org> or Ted Harding <ted.harding@nessie.mcc.ac.uk> for inclusion in the next vendor release. @@ -530,7 +530,7 @@ ru@FreeBSD.org - 20 October 2005 It might occasionally be necessary to include an encumbered file in the FreeBSD source tree. For example, if a device requires a small piece of binary code to be loaded to it before the device will operate, - and we do not have the source to that code, then the binary file is said + and we do not have the source to that code, then the binary file is said to be encumbered. The following policies apply to including encumbered files in the FreeBSD source tree. @@ -553,7 +553,7 @@ ru@FreeBSD.org - 20 October 2005 - Any encumbered file requires specific approval from the + Any encumbered file requires specific approval from the Core Team before it is added to the repository. @@ -564,7 +564,7 @@ ru@FreeBSD.org - 20 October 2005 - The entire module should be kept together. There is no point in + The entire module should be kept together. There is no point in splitting it, unless there is code-sharing with non-encumbered code. @@ -584,9 +584,9 @@ ru@FreeBSD.org - 20 October 2005 - Should always be in LINT, but the + Should always be in LINT, but the Core Team decides per case if it - should be commented out or not. The + should be commented out or not. The Core Team can, of course, change their minds later on. @@ -607,7 +607,7 @@ ru@FreeBSD.org - 20 October 2005 The Core team decides if the code should be part of make world. - + release engineering The Release Engineering @@ -617,7 +617,7 @@ ru@FreeBSD.org - 20 October 2005 - + @@ -646,26 +646,26 @@ ru@FreeBSD.org - 20 October 2005 the release version of the software. The three principles of shared library building are: - + Start from 1.0 - + If there is a change that is backwards compatible, bump minor number (note that ELF systems ignore the minor number) - + If there is an incompatible change, bump major number - + For instance, added functions and bugfixes result in the minor version number being bumped, while deleted functions, changed function call syntax, etc. will force the major version number to change. - + Stick to version numbers of the form major.minor (x.y). Our a.out dynamic linker does not handle version numbers of the form @@ -681,7 +681,7 @@ ru@FreeBSD.org - 20 October 2005 libfoo.so.3.(anything >= 3).(highest available). - + ld.so will always use the highest minor revision. For instance, it will use @@ -694,7 +694,7 @@ ru@FreeBSD.org - 20 October 2005 numbers at all. However, one should still specify a major and minor version number as our Makefiles do the right thing based on the type of system. - + For non-port libraries, it is also our policy to change the shared library version number only once between releases. In addition, it is our policy to change the major shared library version number only once diff --git a/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml index f0c09a9b2d..068850d379 100644 --- a/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml @@ -17,9 +17,9 @@ Secure Programming - + Synopsis - + This chapter describes some of the security issues that have plagued &unix; programmers for decades and some of the new tools available to help programmers avoid writing exploitable @@ -45,12 +45,12 @@ operations are rarely atomic. - Buffer Overflows + Buffer Overflows Buffer Overflows have been around since the very beginnings of the Von-Neuman architecture. - buffer overflow + buffer overflow Von-Neuman They first gained widespread notoriety in 1988 with the Morris @@ -62,14 +62,14 @@ By far the most common type of buffer overflow attack is based on corrupting the stack. - stack - arguments + stack + arguments Most modern computer systems use a stack to pass arguments to procedures and to store local variables. A stack is a last in first out (LIFO) buffer in the high memory area of a process image. When a program invokes a function a new "stack frame" is - + LIFO process image @@ -90,12 +90,12 @@ variables can more easily be addressed relative to this value. The return address for function - frame pointer + frame pointer process image frame pointer - return address + return address stack-overflow calls is also stored on the stack, and this is the cause of @@ -171,7 +171,7 @@ int main() { int i=0; while ((buffer[i++] = getchar()) != '\n') {}; - + i=1; manipulate(buffer); i=2; @@ -181,7 +181,7 @@ int main() { Let us examine what the memory image of this process would look like if we were to input 160 spaces into our little program - before hitting return. + before hitting return. [XXX figure here!] @@ -199,11 +199,11 @@ int main() { string copy functions strncpy - + string copy functions strncat - + These functions accept a length value as a parameter which should be no larger than the size of the destination buffer. @@ -255,11 +255,11 @@ int main() { using any of the bounded copy routines we just discussed. Fortunately, there is a way to help prevent such attacks — run-time bounds checking, which is implemented by several - C/C++ compilers. + C/C++ compilers. - ProPolice - StackGuard - gcc + ProPolice + StackGuard + gcc ProPolice is one such compiler feature, and is integrated into &man.gcc.1; versions 4.1 and later. It replaces and @@ -368,7 +368,7 @@ int main() { attaching a debugger to a process outside of the &man.chroot.8; environment, or in many other creative ways. - + The behavior of the chroot() system call can be controlled somewhat with the kern.chroot_allow_open_directories sysctl @@ -440,7 +440,7 @@ int main() { information labeling, and mandatory access control. This is a work in progress and is the focus of the TrustedBSD project. Some - of the initial work has been committed to &os.current; + of the initial work has been committed to &os.current; (cap_set_proc(3)). diff --git a/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml index a7d5dadfb6..2d27f16d61 100644 --- a/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml @@ -15,12 +15,12 @@ - + Sockets Synopsis - + BSD sockets take interprocess communications to a new level. It is no longer necessary for the communicating processes to run on the same machine. They still @@ -108,12 +108,12 @@ inside of an onion: You have to peel off several layers of skin to get to the data. This is best illustrated with a picture: - + - + +----------------+ | Ethernet | @@ -134,7 +134,7 @@ |+--------------+| +----------------+ - + Protocol Layers @@ -142,11 +142,11 @@ In this example, we are trying to get an image from a web page we are connected to via an Ethernet. - + The image consists of raw data, which is simply a sequence of RGB values that our software can process, i.e., convert into an image and display on our monitor. - + Alas, our software has no way of knowing how the raw data is organized: Is it a sequence of RGB values, or a sequence of grayscale intensities, or perhaps of @@ -154,16 +154,16 @@ by 8-bit quanta, or are they 16 bits in size, or perhaps 4 bits? How many rows and columns does the image consist of? Should certain pixels be transparent? - + I think you get the picture... - + To inform our software how to handle the raw data, it is encoded as a PNG file. It could be a GIF, or a JPEG, but it is a PNG. - + And PNG is a protocol. - + At this point, I can hear some of you yelling, No, it is not! It is a file format! @@ -290,7 +290,7 @@ - + +----------------+ |xxxxEthernetxxxx| @@ -311,7 +311,7 @@ |+--------------+| +----------------+ - + Sockets Covered Protocol Layers @@ -563,7 +563,7 @@ struct sockaddr_in { - + 0 1 2 3 +--------+--------+-----------------+ @@ -576,7 +576,7 @@ struct sockaddr_in { 12 | 0 | +-----------------------------------+ - + sockaddr_in @@ -607,7 +607,7 @@ struct sockaddr_in { - + 0 1 2 3 +--------+--------+-----------------+ @@ -620,7 +620,7 @@ struct sockaddr_in { 12 | 0 | +-----------------------------------+ - + Specific example of sockaddr_in @@ -671,7 +671,7 @@ struct in_addr { - + 0 1 2 3 +--------+--------+--------+--------+ @@ -684,7 +684,7 @@ struct in_addr { 12 | 0 | +-----------------------------------+ - + sockaddr_in on an Intel system @@ -697,7 +697,7 @@ struct in_addr { - + 0 1 2 3 +--------+--------+--------+--------+ @@ -710,7 +710,7 @@ struct in_addr { 12 | 0 | +-----------------------------------+ - + sockaddr_in on an MSB system @@ -791,7 +791,7 @@ struct in_addr { - + 0 1 2 3 +--------+--------+--------+--------+ @@ -804,7 +804,7 @@ struct in_addr { 12 | 0 | +-----------------------------------+ - + Host byte order on an Intel system @@ -818,7 +818,7 @@ struct in_addr { - + 0 1 2 3 +--------+--------+--------+--------+ @@ -831,7 +831,7 @@ struct in_addr { 12 | 0 | +-----------------------------------+ - + Network byte order @@ -1009,7 +1009,7 @@ int main() { &prompt.user; cc -O3 -o daytime daytime.c &prompt.user; ./daytime -52079 01-06-19 02:29:25 50 0 1 543.9 UTC(NIST) * +52079 01-06-19 02:29:25 50 0 1 543.9 UTC(NIST) * &prompt.user; In this case, the date was June 19, 2001, the time was @@ -1075,7 +1075,7 @@ int bind(int s, const struct sockaddr *addr, socklen_t addrlen); - + 0 1 2 3 +--------+--------+--------+--------+ @@ -1088,7 +1088,7 @@ int bind(int s, const struct sockaddr *addr, socklen_t addrlen); 12 | 0 | +-----------------------------------+ - + Example Server sockaddr_in @@ -1338,7 +1338,7 @@ int main() { - + +-----------------+ | Create Socket | @@ -1367,7 +1367,7 @@ int main() { | | Close | |<--------+ - + Sequential Server @@ -1626,7 +1626,7 @@ int main(int argc, char *argv[]) { &prompt.user; daytime ; daytime localhost -52080 01-06-20 04:02:33 50 0 0 390.2 UTC(NIST) * +52080 01-06-20 04:02:33 50 0 0 390.2 UTC(NIST) * 2001-06-20T04:02:35Z &prompt.user; @@ -1695,7 +1695,7 @@ struct servent * getservbyname(const char *name, const char *proto); - + +-----------------+ | Create Socket | @@ -1731,7 +1731,7 @@ struct servent * getservbyname(const char *name, const char *proto); | Exit | +------------------+ - + Concurrent Server diff --git a/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml index e1125bbd16..a16e96c96d 100644 --- a/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml @@ -115,7 +115,7 @@ Interpreters available with FreeBSD - Here is a list of interpreters that are available from + Here is a list of interpreters that are available from the &os; Ports Collection, with a brief discussion of some of the more popular interpreted languages. @@ -184,7 +184,7 @@ scripts; also often used on World Wide Web servers for writing CGI scripts. - Perl is available in the Ports Collection as + Perl is available in the Ports Collection as lang/perl5.8 for all &os; releases, and is installed as /usr/bin/perl in the base system 4.X releases. @@ -269,7 +269,7 @@ programs. Ruby is available from the Ports Collection as - lang/ruby18. + lang/ruby18. @@ -284,7 +284,7 @@ Tk, a GUI toolkit) fully-fledged, featureful programs. - Various versions of Tcl are available as ports + Various versions of Tcl are available as ports for &os;. The latest version, Tcl 8.5, can be found in lang/tcl85. diff --git a/en_US.ISO8859-1/books/faq/Makefile b/en_US.ISO8859-1/books/faq/Makefile index b7394a4876..e6ce1b9f5f 100644 --- a/en_US.ISO8859-1/books/faq/Makefile +++ b/en_US.ISO8859-1/books/faq/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Build the FreeBSD FAQ @@ -15,13 +15,13 @@ INSTALL_ONLY_COMPRESSED?= WITH_BIBLIOXREF_TITLE?=YES -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # # SGML content -SRCS= book.sgml +SRCS= book.sgml URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. diff --git a/en_US.ISO8859-1/books/fdp-primer/Makefile b/en_US.ISO8859-1/books/fdp-primer/Makefile index ecc7ebc217..81d365c81a 100644 --- a/en_US.ISO8859-1/books/fdp-primer/Makefile +++ b/en_US.ISO8859-1/books/fdp-primer/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Build the FreeBSD Documentation Project Primer. @@ -13,25 +13,25 @@ FORMATS?= html-split html INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # # SGML content -SRCS= book.sgml -SRCS+= overview/chapter.sgml -SRCS+= psgml-mode/chapter.sgml -SRCS+= see-also/chapter.sgml -SRCS+= sgml-markup/chapter.sgml -SRCS+= sgml-primer/chapter.sgml -SRCS+= stylesheets/chapter.sgml +SRCS= book.sgml +SRCS+= overview/chapter.sgml +SRCS+= psgml-mode/chapter.sgml +SRCS+= see-also/chapter.sgml +SRCS+= sgml-markup/chapter.sgml +SRCS+= sgml-primer/chapter.sgml +SRCS+= stylesheets/chapter.sgml SRCS+= structure/chapter.sgml SRCS+= doc-build/chapter.sgml -SRCS+= the-website/chapter.sgml -SRCS+= tools/chapter.sgml +SRCS+= the-website/chapter.sgml +SRCS+= tools/chapter.sgml SRCS+= translations/chapter.sgml -SRCS+= writing-style/chapter.sgml +SRCS+= writing-style/chapter.sgml SRCS+= examples/appendix.sgml @@ -43,7 +43,7 @@ IMAGES_LIB+= callouts/4.png IMAGES_LIB+= callouts/5.png # Entities -SRCS+= chapters.ent +SRCS+= chapters.ent URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. diff --git a/en_US.ISO8859-1/books/fdp-primer/chapters.ent b/en_US.ISO8859-1/books/fdp-primer/chapters.ent index cc88f5f668..88c3d22646 100644 --- a/en_US.ISO8859-1/books/fdp-primer/chapters.ent +++ b/en_US.ISO8859-1/books/fdp-primer/chapters.ent @@ -1,12 +1,12 @@ - @@ -20,7 +20,7 @@ - + diff --git a/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml b/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml index c70f5e87ab..eaa899d2ae 100644 --- a/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml @@ -65,7 +65,7 @@ An Example Book - + Your first name Your surname @@ -90,7 +90,7 @@ Your book may have a preface, in which case it should be placed here. - + My First Chapter @@ -145,7 +145,7 @@ My First Sub-Section This is the first sub-section in my article. - +
]]> diff --git a/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml index 8848531401..8f00e11b6b 100644 --- a/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml @@ -471,7 +471,7 @@ - + Middle right cell @@ -832,7 +832,7 @@ <book> <bookinfo> <title>Your Title Here</title> - + <author> <firstname>Your first name</firstname> <surname>Your surname</surname> @@ -882,7 +882,7 @@ <article> <articleinfo> <title>Your title here</title> - + <author> <firstname>Your first name</firstname> <surname>Your surname</surname> @@ -1089,12 +1089,12 @@ Use: A small excerpt from the US Constitution: - +
Preamble to the Constitution of the United States Copied from a web site somewhere - + We the People of the United States, in Order to form a more perfect Union, establish Justice, insure domestic Tranquility, provide for the common defence, promote the general Welfare, and secure the Blessings @@ -1739,7 +1739,7 @@ This is the file called 'foo2' Use: - To switch to the second virtual terminal, press + To switch to the second virtual terminal, press Alt F1. @@ -2359,7 +2359,7 @@ This is the file called 'foo2' Use: - Panic: cannot mount root ]]> diff --git a/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml index c8746c2ec2..065be0307f 100644 --- a/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml @@ -245,7 +245,7 @@ V regardless of the indentation level of the file which might contain this one. - ... + ... ]]> diff --git a/en_US.ISO8859-1/books/handbook/Makefile b/en_US.ISO8859-1/books/handbook/Makefile index 9107db6d1e..1babfa56b1 100644 --- a/en_US.ISO8859-1/books/handbook/Makefile +++ b/en_US.ISO8859-1/books/handbook/Makefile @@ -12,13 +12,13 @@ # fingerprints by default. If you would like for the # entire key to be displayed, then set this variable. # This option has no affect on the HTML formats. -# +# # Handbook-specific targets # # 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. # @@ -242,7 +242,7 @@ IMAGES_LIB+= callouts/13.png IMAGES_LIB+= callouts/14.png IMAGES_LIB+= callouts/15.png -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # @@ -289,7 +289,7 @@ SRCS+= virtualization/chapter.sgml SRCS+= x11/chapter.sgml # Entities -SRCS+= chapters.ent +SRCS+= chapters.ent SYMLINKS= ${DESTDIR} index.html handbook.html diff --git a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml index c43896a855..3636631328 100644 --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml @@ -3507,10 +3507,10 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2 To see the port status on the switch, use show lacp neighbor: - switch# show lacp neighbor -Flags: S - Device is requesting Slow LACPDUs + switch# show lacp neighbor +Flags: S - Device is requesting Slow LACPDUs F - Device is requesting Fast LACPDUs - A - Device is in Active mode P - Device is in Passive mode + A - Device is in Active mode P - Device is in Passive mode Channel group 1 neighbors @@ -3518,7 +3518,7 @@ Partner's information: LACP port Oper Port Port Port Flags Priority Dev ID Age Key Number State -Fa0/1 SA 32768 0005.5d71.8db8 29s 0x146 0x3 0x3D +Fa0/1 SA 32768 0005.5d71.8db8 29s 0x146 0x3 0x3D Fa0/2 SA 32768 0005.5d71.8db8 29s 0x146 0x4 0x3D For more detail use the show lacp neighbor @@ -3614,7 +3614,7 @@ ifconfig_lagg0="laggproto failover bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4> ether 00:21:70:da:ae:37 - inet6 fe80::221:70ff:feda:ae37%bge0 prefixlen 64 scopeid 0x2 + inet6 fe80::221:70ff:feda:ae37%bge0 prefixlen 64 scopeid 0x2 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active diff --git a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml index 6486844996..f1de10ee82 100644 --- a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml @@ -18,7 +18,7 @@ UNIX Basics - + Synopsis @@ -794,7 +794,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd end of the set. - + Directory Structure directory hierarchy @@ -841,70 +841,70 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd / Root directory of the file system. - + /bin/ User utilities fundamental to both single-user and multi-user environments. - + /boot/ Programs and configuration files used during operating system bootstrap. - + /boot/defaults/ Default bootstrapping configuration files; see &man.loader.conf.5;. - + /dev/ Device nodes; see &man.intro.4;. - + /etc/ System configuration files and scripts. - + /etc/defaults/ Default system configuration files; see &man.rc.8;. - + /etc/mail/ Configuration files for mail transport agents such as &man.sendmail.8;. - + /etc/namedb/ named configuration files; see &man.named.8;. - + /etc/periodic/ Scripts that are run daily, weekly, and monthly, via &man.cron.8;; see &man.periodic.8;. - + /etc/ppp/ ppp configuration files; see &man.ppp.8;. - + /mnt/ - Empty directory commonly used by system administrators as a + Empty directory commonly used by system administrators as a temporary mount point. - + /proc/ Process file system; see &man.procfs.5;, @@ -928,8 +928,8 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd System programs and administration utilities fundamental to both single-user and multi-user environments. - - + + /tmp/ Temporary files. The contents of @@ -941,40 +941,40 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd &man.rc.conf.5; (or with an entry in /etc/fstab; see &man.mdmfs.8;). - - + + /usr/ The majority of user utilities and applications. - + /usr/bin/ Common utilities, programming tools, and applications. - + /usr/include/ Standard C include files. - + /usr/lib/ Archive libraries. - - + + /usr/libdata/ Miscellaneous utility data files. - + /usr/libexec/ System daemons & system utilities (executed by other programs). - + /usr/local/ @@ -991,40 +991,40 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd share/doc/port. - + /usr/obj/ Architecture-specific target tree produced by building the /usr/src tree. - + /usr/ports/ The FreeBSD Ports Collection (optional). - + /usr/sbin/ System daemons & system utilities (executed by users). - + /usr/share/ Architecture-independent files. - + /usr/src/ BSD and/or local source files. - + /usr/X11R6/ X11R6 distribution executables, libraries, etc (optional). - + /var/ Multi-purpose log, temporary, transient, and spool files. @@ -1034,24 +1034,24 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd &man.rc.conf.5; (or with an entry in /etc/fstab; see &man.mdmfs.8;). - - + + /var/log/ Miscellaneous system log files. - + /var/mail/ User mailbox files. - + /var/spool/ Miscellaneous printer and mail system spooling directories. - + /var/tmp/ Temporary files. @@ -1059,7 +1059,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd unless /var is a memory-based file system. - + /var/yp/ NIS maps. @@ -1157,7 +1157,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd / - | + | +--- A1 | | | +--- B1 @@ -1208,7 +1208,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd - + / | @@ -1266,7 +1266,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd Benefits of Multiple File Systems - + Different file systems can have different mount options. For example, with careful planning, the @@ -1288,7 +1288,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd fewer, larger files. By having one big file system this optimization breaks down. - + FreeBSD's file systems are very robust should you lose power. However, a power loss at a critical point could still damage the @@ -1310,12 +1310,12 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd FreeBSD features the &man.growfs.8; - command, which makes it possible to increase the size of + command, which makes it possible to increase the size of file system on the fly, removing this limitation. - + File systems are contained in partitions. This does not have the same meaning as the common usage of the term partition (for example, &ms-dos; partition), because of &os;'s &unix; heritage. Each partition is @@ -1402,7 +1402,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd extended slices are numbered starting at 5, so ad0s5 is the first extended slice on the first IDE disk. These devices are used by file - systems that expect to occupy a slice. + systems that expect to occupy a slice. Slices, dangerously dedicated physical drives, and other drives contain @@ -1413,11 +1413,11 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd the first da drive, which is dangerously dedicated. ad1s3e is the fifth partition in the third slice of the second IDE disk drive. - + Finally, each disk on the system is identified. A disk name starts with a code that indicates the type of disk, and then a number, indicating which disk it is. Unlike slices, disk numbering starts at - 0. Common codes that you will see are listed in + 0. Common codes that you will see are listed in . When referring to a partition FreeBSD requires that you also name @@ -1425,7 +1425,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd a slice you must also refer to the disk name. Thus, you refer to a partition by listing the disk name, s, the slice number, and then the - partition letter. Examples are shown in + partition letter. Examples are shown in . shows a conceptual @@ -1446,7 +1446,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd Code - + Meaning @@ -1460,34 +1460,34 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd da - + SCSI direct access disk - + acd - + ATAPI (IDE) CDROM - + cd - + SCSI CDROM - + fd - + Floppy disk - + Sample Disk, Slice, and Partition Names - + @@ -1496,15 +1496,15 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd Name - + Meaning - + ad0s1a - + The first partition (a) on the first slice (s1) on the first IDE disk (ad0). @@ -1512,7 +1512,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd da1s2e - + The fifth partition (e) on the second slice (s2) on the second SCSI disk (da1). @@ -1542,7 +1542,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd - + .-----------------. --. | | | @@ -1559,7 +1559,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd | | > referred to as ad0s2b | | | | | :-----------------: ==: | Partition c, no -| | | Partition e, used as /var > file system, all +| | | Partition e, used as /var > file system, all | | > referred to as ad0s2e | of FreeBSD slice, | | | | ad0s2c :-----------------: ==: | @@ -1631,24 +1631,24 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd mount-point - + A directory (which should exist), on which to mount the file system. - + fstype - + The file system type to pass to &man.mount.8;. The default FreeBSD file system is ufs. - + options - + Either for read-write file systems, or for read-only file systems, followed by any other options that may be @@ -1657,10 +1657,10 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd Other options are listed in the &man.mount.8; manual page. - + dumpfreq - + This is used by &man.dump.8; to determine which file systems require dumping. If the field is missing, a value of zero is assumed. @@ -1696,10 +1696,10 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd file systems mounting - + The &man.mount.8; command is what is ultimately used to mount file systems. - + In its most basic form, you use: @@ -1714,7 +1714,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd - + Mount all the file systems listed in /etc/fstab. Except those @@ -1723,10 +1723,10 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd mounted. - + - + Do everything except for the actual mount system call. This option is useful in conjunction with the @@ -1734,7 +1734,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd &man.mount.8; is actually trying to do. - + @@ -1745,10 +1745,10 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd read-write to read-only. - + - + Mount the file system read-only. This is identical to using the @@ -1756,7 +1756,7 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd option. - + fstype @@ -1765,53 +1765,53 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd Mount the given file system as the given file system type, or mount only file systems of the given type, if given the option. - + ufs is the default file system type. - + - + Update mount options on the file system. - + - + Be verbose. - + - + Mount the file system read-write. - + The option takes a comma-separated list of the options, including the following: - + noexec - + Do not allow execution of binaries on this file system. This is also a useful security option. - + nosuid - + Do not interpret setuid or setgid flags on the file system. This is also a useful security option. @@ -1826,17 +1826,17 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd file systems unmounting - + The &man.umount.8; command takes, as a parameter, one of a mountpoint, a device name, or the or option. - + All forms take to force unmounting, and for verbosity. Be warned that is not generally a good idea. Forcibly unmounting file systems might crash the computer or damage data on the file system. - + and are used to unmount all mounted file systems, possibly modified by the file system types listed after . @@ -2059,7 +2059,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse standard way to respond to these signals, different daemons will have different behavior, so be sure and read the documentation for the daemon in question. - + Signals are sent using the &man.kill.1; command, as this example shows. @@ -2147,16 +2147,16 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse from the input channel and execute them. A lot of shells also have built in functions to help with everyday tasks such as file management, file globbing, command line editing, command macros, and environment - variables. FreeBSD comes with a set of shells, such as - sh, the Bourne Shell, and tcsh, + variables. FreeBSD comes with a set of shells, such as + sh, the Bourne Shell, and tcsh, the improved C-shell. Many other shells are available from the FreeBSD Ports Collection, such as zsh and bash. Which shell do you use? It is really a matter of taste. If you are a C programmer you might feel more comfortable with a C-like shell - such as tcsh. If you have come from Linux or are new - to a &unix; command line interface you might try bash. + such as tcsh. If you have come from Linux or are new + to a &unix; command line interface you might try bash. The point is that each shell has unique properties that may or may not work with your preferred working environment, and that you have a choice of what @@ -2273,7 +2273,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse bash, you would use export to set your current environment variables. For example, to set or modify the - EDITOR environment variable, under csh or + EDITOR environment variable, under csh or tcsh a command like this would set EDITOR to /usr/local/bin/emacs: @@ -2319,11 +2319,11 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse You can also give chsh the option; this will set your shell for you, - without requiring you to enter an editor. + without requiring you to enter an editor. For example, if you wanted to change your shell to bash, the following should do the trick: - + &prompt.user; chsh -s /usr/local/bin/bash @@ -2333,7 +2333,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse collection, then this should have been done for you already. If you installed the shell by hand, you must do this. - + For example, if you installed bash by hand and placed it into /usr/local/bin, you would want to: @@ -2368,7 +2368,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse line ee filename where filename is the name of the file to be edited. For example, to edit /etc/rc.conf, type in - ee /etc/rc.conf. Once inside of + ee /etc/rc.conf. Once inside of ee, all of the commands for manipulating the editor's functions are listed at the top of the display. The caret ^ character represents diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index 1fea20521a..6e6c853e23 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -300,7 +300,7 @@ Appendices - + &chap.mirrors; &chap.bibliography; &chap.eresources; diff --git a/en_US.ISO8859-1/books/handbook/chapters.ent b/en_US.ISO8859-1/books/handbook/chapters.ent index 42b4024070..eecc4a2281 100644 --- a/en_US.ISO8859-1/books/handbook/chapters.ent +++ b/en_US.ISO8859-1/books/handbook/chapters.ent @@ -1,12 +1,12 @@ - diff --git a/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml b/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml index 12e186855f..2e5ad728e4 100644 --- a/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml @@ -715,7 +715,7 @@ errors: No known data errors Reservations of any sort are useful in many situations, for example planning and testing the suitability of disk space - allocation in a new system, or ensuring that enough space is + allocation in a new system, or ensuring that enough space is available on file systems for system recovery procedures and files. @@ -750,7 +750,7 @@ errors: No known data errors &linux; Filesystems - + This section will describe some of the &linux; filesystems supported by &os;. @@ -758,13 +758,13 @@ errors: No known data errors Ext2FS The &man.ext2fs.5; file system kernel implementation was - written by Godmar Back, and the driver first appeared in + written by Godmar Back, and the driver first appeared in &os; 2.2. In &os; 8 and earlier, the code is licensed under the GNU Public License, however under &os; 9, the code has been rewritten and it is now licensed under the BSD license. - The &man.ext2fs.5; driver will allow the &os; kernel + The &man.ext2fs.5; driver will allow the &os; kernel to both read and write to ext2 file systems. First, load the kernel loadable module: @@ -783,8 +783,8 @@ errors: No known data errors written by SGI for the IRIX operating system, and they ported it to &linux;. The source code has been released under the - GNU Public License. See - this page + GNU Public License. See + this page for more details. The &os; port was started by Russel Cattelan, &a.kan;, and &a.rodrigc;. @@ -803,7 +803,7 @@ errors: No known data errors &prompt.root; mount -t xfs /dev/as1s1 /mnt - Also useful to note is that the + Also useful to note is that the sysutils/xfsprogs port contains the mkfs.xfs utility which enables creation of XFS filesystems, plus utilities diff --git a/en_US.ISO8859-1/books/handbook/jails/chapter.sgml b/en_US.ISO8859-1/books/handbook/jails/chapter.sgml index 3ca4a23e2e..9909ba93d2 100644 --- a/en_US.ISO8859-1/books/handbook/jails/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/jails/chapter.sgml @@ -559,7 +559,7 @@ jail_www_devfs_ruleset="www_rulesetSMTP server, and so forth. - The goals of the setup described in this section + The goals of the setup described in this section are: @@ -763,7 +763,7 @@ jail_www_devfs_ruleset="www_ruleset - + Partitions marked with a 0 pass number are not checked by &man.fsck.8; during boot, and partitions diff --git a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml index 59336ff9fc..4f263bd1ff 100644 --- a/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml @@ -141,7 +141,7 @@ Finding the System Hardware - + Before venturing into kernel configuration, it would be wise to get an inventory of the machine's hardware. In cases where &os; is not the primary operating system, the inventory list may @@ -343,7 +343,7 @@ following line in &man.loader.conf.5;: &prompt.root; cd /usr/src/sys/i386/conf &prompt.root; mkdir /root/kernels -&prompt.root; cp GENERIC /root/kernels/MYKERNEL +&prompt.root; cp GENERIC /root/kernels/MYKERNEL &prompt.root; ln -s /root/kernels/MYKERNEL @@ -432,7 +432,7 @@ following line in &man.loader.conf.5;: /boot/kernel.old - + The new kernel will be copied to the /boot/kernel directory as @@ -1368,7 +1368,7 @@ device fwe # Ethernet over FireWire (non-standard!)KVA) space. Due to this limitation, Intel added support for 36-bit physical address space access in the &pentium; Pro and later line of CPUs. - + The Physical Address Extension (PAE) capability of the &intel; &pentium; Pro and later CPUs allows memory configurations of up to 64 gigabytes. @@ -1383,7 +1383,7 @@ device fwe # Ethernet over FireWire (non-standard!)To enable PAE support in the kernel, simply add the following line to your kernel configuration file: - + options PAE @@ -1395,7 +1395,7 @@ device fwe # Ethernet over FireWire (non-standard!) PAE support in &os; has a few limitations: - + A process is not able to access more than 4 diff --git a/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml b/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml index 38cbbd2c93..637cecaeb3 100644 --- a/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml @@ -68,7 +68,7 @@ internationalization localization - localization + localization Developers shortened internationalization into the term I18N, counting the number of letters between the first and the last @@ -169,7 +169,7 @@ usually do recognize 8-bit characters. Depending on the implementation, users may be required to compile an application with wide or multibyte characters support, or configure it correctly. - To be able to input and process wide or multibyte characters, the FreeBSD Ports Collection has provided each language with different programs. Refer to the I18N documentation in the respective FreeBSD Port. @@ -281,7 +281,7 @@ :lang=de_DE.ISO8859-1: Traditional ChineseBIG-5 encoding - Here is an example of a + Here is an example of a .login_conf that sets the variables for Traditional Chinese in BIG-5 encoding. Notice the many more variables set because some software does not respect @@ -292,14 +292,14 @@ me:\ :lang=zh_TW.Big5:\ :setenv=LC_ALL=zh_TW.Big5:\ - :setenv=LC_COLLATE=zh_TW.Big5:\ + :setenv=LC_COLLATE=zh_TW.Big5:\ :setenv=LC_CTYPE=zh_TW.Big5:\ :setenv=LC_MESSAGES=zh_TW.Big5:\ :setenv=LC_MONETARY=zh_TW.Big5:\ :setenv=LC_NUMERIC=zh_TW.Big5:\ :setenv=LC_TIME=zh_TW.Big5:\ :charset=big5:\ - :xmodifiers="@im=gcin": #Set gcin as the XIM Input Server + :xmodifiers="@im=gcin": #Set gcin as the XIM Input Server See Administrator Level Setup and &man.login.conf.5; for more details. @@ -364,7 +364,7 @@ me:\ An alternative variant is answering the specified - language each time that + language each time that Enter login class: default []: appears from &man.adduser.8;. @@ -470,7 +470,7 @@ font8x8=font_name scrnmap=screenmap_name keymap=keymap_name keychange="fkey_number sequence" - + The screenmap_name here is taken from the /usr/share/syscons/scrnmaps directory, without the .scm suffix. A @@ -678,7 +678,7 @@ keychange="fkey_number sequence" MySQL - However, some applications such as + However, some applications such as MySQL need to have their Makefile configured with the specific charset. This is usually done in the @@ -686,7 +686,7 @@ keychange="fkey_number sequence" configure in the source. - + Localizing FreeBSD to Specific Languages diff --git a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml index 41203925f4..c6fb8c9571 100644 --- a/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml @@ -731,7 +731,7 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \ Installing &matlab; - To install &matlab;, do the + To install &matlab;, do the following: @@ -796,7 +796,7 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \ &prompt.root; ln -s $MATLAB/etc/lmboot /usr/local/etc/lmboot_TMW &prompt.root; ln -s $MATLAB/etc/lmdown /usr/local/etc/lmdown_TMW - + Create a startup file at /usr/local/etc/rc.d/flexlm.sh. The diff --git a/en_US.ISO8859-1/books/handbook/mac/chapter.sgml b/en_US.ISO8859-1/books/handbook/mac/chapter.sgml index 8deaa34875..efa55e49b4 100644 --- a/en_US.ISO8859-1/books/handbook/mac/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/mac/chapter.sgml @@ -697,7 +697,7 @@ test: biba/high implement the labeling feature, including the Biba, Lomac, MLS and SEBSD policies. - + In many cases, the may not need to be set at all. Consider the following situation and security model: @@ -1562,7 +1562,7 @@ test: biba/low 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. - + 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 @@ -1725,7 +1725,7 @@ mac_seeotheruids_load="YES" www users into the insecure class: &prompt.root; pw usermod nagios -L insecure - &prompt.root; pw usermod www -L insecure + &prompt.root; pw usermod www -L insecure diff --git a/en_US.ISO8859-1/books/handbook/mail/chapter.sgml b/en_US.ISO8859-1/books/handbook/mail/chapter.sgml index 094b8e2a0f..989b9761f2 100644 --- a/en_US.ISO8859-1/books/handbook/mail/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/mail/chapter.sgml @@ -254,7 +254,7 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org Once mail has been stored, it may either be read locally using applications such as &man.mail.1; or mutt, or remotely accessed and - collected using protocols such as + collected using protocols such as POP or IMAP. This means that should you only wish to read mail locally, you are not required to install a @@ -322,7 +322,7 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org courier-imap; - + dovecot; diff --git a/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml b/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml index c458ffe084..0f866c57b7 100644 --- a/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml @@ -322,7 +322,7 @@ SSH2 HostKey: 1024 02:ed:1b:17:d6:97:2b:58:5e:5c:e2:da:3b:89:88:26 /etc/ssh/ssh_host_rsa_key.pub SSH2 HostKey: 1024 e8:3b:29:7b:ca:9f:ac:e9:45:cb:c8:17:ae:9b:eb:55 /etc/ssh/ssh_host_dsa_key.pub - + 204.152.186.171 netmask 0xffffffff - + Using mpd is the recommended way to connect to an ADSL service with &os;. - + Using pptpclient - + It is also possible to use FreeBSD to connect to other PPPoA services using net/pptpclient. - + To use net/pptpclient to connect to a DSL service, install the port or package and edit your /etc/ppp/ppp.conf. You will need to be @@ -2494,7 +2494,7 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500 end of the previous command because pptp will not return your prompt to you otherwise. - + A tun virtual tunnel device will be created for interaction between the pptp and ppp processes. Once you have been @@ -2504,7 +2504,7 @@ ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500 &prompt.user; ifconfig tun0 tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 - inet 216.136.204.21 --> 204.152.186.171 netmask 0xffffff00 + inet 216.136.204.21 --> 204.152.186.171 netmask 0xffffff00 Opened by PID 918 If you are unable to connect, check the configuration of @@ -2580,7 +2580,7 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 Make sure you have the following in your kernel configuration file: - + device sl It is included in the GENERIC kernel, so @@ -2617,7 +2617,7 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500 Set your hostname by editing the line that says: - + hostname="myname.my.domain" Your machine's full Internet hostname should be @@ -2655,7 +2655,7 @@ nameserver 128.32.136.12 - Set the password for root and + Set the password for root and toor (and any other accounts that do not have a password). @@ -2722,7 +2722,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a If you are able to ping hosts on the other side of the router, you are connected! If it does not work, you might want to try instead of - as an argument to + as an argument to slattach. @@ -2740,8 +2740,8 @@ output ***\x0d, echo \x0aCONNECTED\x0a kermit (by running fg if you suspended it) and exit from it (q). - The &man.slattach.8; manual page says you have - to use ifconfig sl0 down + The &man.slattach.8; manual page says you have + to use ifconfig sl0 down to mark the interface down, but this does not seem to make any difference. (ifconfig sl0 reports the same thing.) @@ -2949,7 +2949,7 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438 change the setting of the gateway_enable variable to . This will make sure that setting the routing option will be persistent after a reboot. - + To apply the settings immediately you can execute the following command as root: @@ -3012,7 +3012,7 @@ water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438 this: # -# login local-addr remote-addr mask opt1 opt2 +# login local-addr remote-addr mask opt1 opt2 # (normal,compress,noicmp) # Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp @@ -3111,7 +3111,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp @@ -3218,7 +3218,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp If you are not using the proxy ARP method for routing packets between your SLIP clients and the rest of your - network (and perhaps the Internet), you will probably + network (and perhaps the Internet), you will probably have to add static routes to your closest default router(s) to route your SLIP clients subnet via your SLIP server. diff --git a/en_US.ISO8859-1/books/handbook/preface/preface.sgml b/en_US.ISO8859-1/books/handbook/preface/preface.sgml index ec02ab3256..ef19a8b1fa 100644 --- a/en_US.ISO8859-1/books/handbook/preface/preface.sgml +++ b/en_US.ISO8859-1/books/handbook/preface/preface.sgml @@ -5,7 +5,7 @@ Preface - + Intended Audience @@ -95,7 +95,7 @@ , Mandatory Access Control (MAC), is a new chapter with this edition. It explains what MAC is - and how this mechanism can be used to secure a &os; + and how this mechanism can be used to secure a &os; system. @@ -346,7 +346,7 @@ - , Configuring the &os; + , Configuring the &os; Kernel Explains why you might need to configure a new kernel diff --git a/en_US.ISO8859-1/books/handbook/txtfiles.ent b/en_US.ISO8859-1/books/handbook/txtfiles.ent index 0ad1fecbd6..c3111a11fc 100644 --- a/en_US.ISO8859-1/books/handbook/txtfiles.ent +++ b/en_US.ISO8859-1/books/handbook/txtfiles.ent @@ -1,14 +1,14 @@ - diff --git a/en_US.ISO8859-1/books/handbook/users/chapter.sgml b/en_US.ISO8859-1/books/handbook/users/chapter.sgml index 3b0f588d73..4315ba4dec 100644 --- a/en_US.ISO8859-1/books/handbook/users/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/users/chapter.sgml @@ -18,10 +18,10 @@ Users and Basic Account Management - + Synopsis - + FreeBSD allows multiple users to use the computer at the same time. Obviously, only one of those users can be sitting in front of the screen and keyboard at any one time @@ -31,7 +31,7 @@ , but any number of users can log in through the network to get their work done. To use the system every user must have an account. - + After reading this chapter, you will know: @@ -224,10 +224,10 @@ users run services. Finally, user accounts are used by real people, who log on, read mail, and so forth. - + The Superuser Account - + accounts superuser (root) @@ -237,7 +237,7 @@ system administration, and should not be used for day-to-day tasks like sending and receiving mail, general exploration of the system, or programming. - + This is because the superuser, unlike normal user accounts, can operate without limits, and misuse of the superuser account may result in spectacular disasters. User accounts are unable @@ -257,7 +257,7 @@ accounts, and how to change between the normal user and superuser. - + System Accounts @@ -479,7 +479,7 @@ Goodbye! Finally, removes the username from all groups to which it belongs in /etc/group. - + If a group becomes empty and the group name is the same as the username, the group is removed; this @@ -523,7 +523,7 @@ Removing files belonging to jru from /var/tmp/vi.recover: done. information. Only system administrators, as the superuser, may change - other users' information and passwords with + other users' information and passwords with &man.chpass.1;. When passed no options, aside from an optional username, @@ -574,7 +574,7 @@ Other information: &man.chfn.1; and &man.chsh.1; are - just links to &man.chpass.1;, as + just links to &man.chpass.1;, as are &man.ypchpass.1;, &man.ypchfn.1;, and &man.ypchsh.1;. NIS support is automatic, so @@ -695,7 +695,7 @@ passwd: done string processed accordingly depending on the name. Setting up login classes and capabilities is rather straight-forward and is also described in &man.login.conf.5;. - + The system does not normally read the configuration in /etc/login.conf directly, but reads the database @@ -797,7 +797,7 @@ passwd: done running. This includes foreground and background processes alike. For obvious reasons, this may not be larger than the system limit specified by the kern.maxproc - &man.sysctl.8;. Also note that setting this + &man.sysctl.8;. Also note that setting this too small may hinder a user's productivity: it is often useful to be logged in multiple times or execute pipelines. Some tasks, such as @@ -920,7 +920,7 @@ passwd: done Remember that many limits apply to individual processes, not - the user as a whole. For example, setting + the user as a whole. For example, setting openfiles to 50 means that each process the user runs may open up to 50 files. Thus, the gross amount of files a user may open is the value of diff --git a/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml b/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml index 88158545ad..b5f9cec39e 100644 --- a/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml @@ -239,7 +239,7 @@ RAID-1 - + The traditional way to approach this problem has been mirroring, keeping two copies of the data on different physical hardware. Since the advent of the @@ -249,9 +249,9 @@ both locations; a read can be satisfied from either, so if one drive fails, the data is still available on the other drive. - + Mirroring has two problems: - + The price. It requires twice as much disk storage as @@ -333,7 +333,7 @@ subdisks, which it uses as building blocks for plexes. - + Subdisks reside on Vinum drives, currently &unix; partitions. Vinum drives can @@ -355,7 +355,7 @@ an individual drive does not limit the size of a plex, and thus of a volume. - + Redundant Data Storage Vinum implements mirroring by attaching multiple plexes to @@ -371,7 +371,7 @@ provide the data for the complete address range of the volume, the volume is fully functional. - + Performance Issues @@ -397,7 +397,7 @@ Which Plex Organization? The version of Vinum supplied with &os; &rel.current; implements two kinds of plex: - + Concatenated plexes are the most flexible: they can @@ -426,10 +426,10 @@ indistinguishable from a concatenated plex. - + summarizes the advantages and disadvantages of each plex organization. - + Vinum Plex Organizations @@ -452,7 +452,7 @@ Large data storage with maximum placement flexibility and moderate performance - + striped 2 @@ -466,7 +466,7 @@
- + Some Examples @@ -479,7 +479,7 @@ Vinum calls a device) under its control. This database is updated on each state change, so that a restart accurately restores the state of each Vinum object. - + The Configuration File The configuration file describes individual Vinum objects. The @@ -545,13 +545,13 @@ Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 1 (16 configured) - + D a State: up Device /dev/da3h Avail: 2061/2573 MB (80%) - + V myvol State: up Plexes: 1 Size: 512 MB - + P myvol.p0 C State: up Subdisks: 1 Size: 512 MB - + S myvol.p0.s0 State: up PO: 0 B Size: 512 MB This output shows the brief listing format of &man.gvinum.8;. It @@ -607,21 +607,21 @@ Volumes: 2 (4 configured) Plexes: 3 (8 configured) Subdisks: 3 (16 configured) - + D a State: up Device /dev/da3h Avail: 1549/2573 MB (60%) D b State: up Device /dev/da4h Avail: 2061/2573 MB (80%) V myvol State: up Plexes: 1 Size: 512 MB V mirror State: up Plexes: 2 Size: 512 MB - + P myvol.p0 C State: up Subdisks: 1 Size: 512 MB P mirror.p0 C State: up Subdisks: 1 Size: 512 MB P mirror.p1 C State: initializing Subdisks: 1 Size: 512 MB - + S myvol.p0.s0 State: up PO: 0 B Size: 512 MB S mirror.p0.s0 State: up PO: 0 B Size: 512 MB S mirror.p1.s0 State: empty PO: 0 B Size: 512 MB - + shows the structure graphically. @@ -669,21 +669,21 @@ Volumes: 3 (4 configured) Plexes: 4 (8 configured) Subdisks: 7 (16 configured) - + D a State: up Device /dev/da3h Avail: 1421/2573 MB (55%) D b State: up Device /dev/da4h Avail: 1933/2573 MB (75%) D c State: up Device /dev/da5h Avail: 2445/2573 MB (95%) D d State: up Device /dev/da6h Avail: 2445/2573 MB (95%) - + V myvol State: up Plexes: 1 Size: 512 MB V mirror State: up Plexes: 2 Size: 512 MB V striped State: up Plexes: 1 Size: 512 MB - + P myvol.p0 C State: up Subdisks: 1 Size: 512 MB P mirror.p0 C State: up Subdisks: 1 Size: 512 MB P mirror.p1 C State: initializing Subdisks: 1 Size: 512 MB P striped.p1 State: up Subdisks: 1 Size: 512 MB - + S myvol.p0.s0 State: up PO: 0 B Size: 512 MB S mirror.p0.s0 State: up PO: 0 B Size: 512 MB S mirror.p1.s0 State: empty PO: 0 B Size: 512 MB @@ -744,7 +744,7 @@ - + Object Naming @@ -815,7 +815,7 @@ /dev/vinum/plex: total 0 crwxr-xr-- 1 root wheel 25, 0x10000002 Apr 13 16:46 s64.p0 - + /dev/vinum/sd: total 0 crwxr-xr-- 1 root wheel 91, 0x20000002 Apr 13 16:46 s64.p0.s0 @@ -855,7 +855,7 @@ &prompt.root; newfs /dev/gvinum/concat - + Configuring Vinum @@ -897,7 +897,7 @@ sd name bigraid.p0.s1 drive b plex bigraid.p0 state initializing len 4194304b dr sd name bigraid.p0.s2 drive c plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 8388608b sd name bigraid.p0.s3 drive d plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 12582912b sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 16777216b - + The obvious differences here are the presence of explicit location information and naming (both of which are also allowed, but discouraged, for use by the user) and the @@ -908,7 +908,7 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr label. This enables Vinum to identify drives correctly even if they have been assigned different &unix; drive IDs. - + Automatic Startup diff --git a/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml b/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml index 6a904673cf..f3e6f10933 100644 --- a/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml @@ -520,7 +520,7 @@ FreeBSD demo.freebsd.org 7.0-CURRENT FreeBSD 7.0-CURRENT #113: Wed Jan 4 06:25: kmacy@freebsd7.gateway.2wire.net:/usr/home/kmacy/p4/freebsd7_xen3/src/sys/i386-xen/compile/XENCONF i386 The network can now be configured on the domU. The - &os; domU will use a specific interface called + &os; domU will use a specific interface called xn0: &prompt.root; ifconfig xn0 10.10.10.200 netmask 255.0.0.0 @@ -534,7 +534,7 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet 127.0.0.1 netmask 0xff000000 On dom0 Slackware, some - &xen; dependant network + &xen; dependant network interfaces should show up: &prompt.root; ifconfig @@ -1124,7 +1124,7 @@ EndSection for most operating systems including &windows;, &macos;, &linux; and &os;. It is equally capable at running &windows; or &unix; like guests. It is released as open source software, but with - closed-source components available in a separate extension pack. + closed-source components available in a separate extension pack. These components include support for USB 2.0 devices, among others. More information may be found on the Downloads page of the &virtualbox; wiki, at diff --git a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml index ba9cf67779..c644981a23 100644 --- a/en_US.ISO8859-1/books/handbook/x11/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/x11/chapter.sgml @@ -928,7 +928,7 @@ EndSection All fonts in X11 that are found in /usr/local/lib/X11/fonts/ and - ~/.fonts/ are automatically + ~/.fonts/ are automatically made available for anti-aliasing to Xft-aware applications. Most recent applications are Xft-aware, including KDE, GNOME, and @@ -1054,9 +1054,9 @@ EndSection with the </fontconfig> tag. Not doing this will cause your changes to be ignored. - Finally, users can add their own settings via their personal - .fonts.conf files. To do this, each user should - simply create a ~/.fonts.conf. This file must + Finally, users can add their own settings via their personal + .fonts.conf files. To do this, each user should + simply create a ~/.fonts.conf. This file must also be in XML format. LCD screen diff --git a/en_US.ISO8859-1/books/porters-handbook/Makefile b/en_US.ISO8859-1/books/porters-handbook/Makefile index bbc0248516..3ea1b0637a 100644 --- a/en_US.ISO8859-1/books/porters-handbook/Makefile +++ b/en_US.ISO8859-1/books/porters-handbook/Makefile @@ -1,4 +1,4 @@ -# +# # $FreeBSD$ # # Build the FreeBSD Porter's Handbook. @@ -13,7 +13,7 @@ FORMATS?= html-split INSTALL_COMPRESSED?= gz INSTALL_ONLY_COMPRESSED?= -# +# # SRCS lists the individual SGML files that make up the document. Changes # to any of these files will force a rebuild # diff --git a/en_US.ISO8859-1/htdocs/FAQ/Makefile b/en_US.ISO8859-1/htdocs/FAQ/Makefile index 0d9cd7ac04..2804c67452 100644 --- a/en_US.ISO8859-1/htdocs/FAQ/Makefile +++ b/en_US.ISO8859-1/htdocs/FAQ/Makefile @@ -7,6 +7,6 @@ .include "../Makefile.inc" .endif -DATA= index.html +DATA= index.html .include "${DOC_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/applications.sgml b/en_US.ISO8859-1/htdocs/applications.sgml index a9771b7e1c..2a89fb4e27 100644 --- a/en_US.ISO8859-1/htdocs/applications.sgml +++ b/en_US.ISO8859-1/htdocs/applications.sgml @@ -14,13 +14,13 @@

Experience the possibilities with FreeBSD

- +

FreeBSD can handle nearly any task you would expect of a &unix; workstation, as well as many you might not expect:

- +

FreeBSD is a true open system with full source code.

- +

There is no doubt that so-called open systems are the requirement for today's computing applications. But no commercial vendor-supplied solution is more open than one which includes full @@ -32,11 +32,11 @@

With its generous licensing policy, you can use FreeBSD as the basis for any number of free or - commercial applications.

+ commercial applications.

FreeBSD runs thousands of applications.

- +

Because FreeBSD is based on 4.4BSD, an industry-standard version of UNIX, it is easy to compile and run programs. FreeBSD also includes an extensive packages collection and - +

FreeBSD is an operating system that will grow with your needs.

@@ -126,9 +126,9 @@ and the team keeps a special eye out for problems which affect system stability. FreeBSD users are quite proud of not only how fast but how reliable their systems are.

- +

What experts have to say . . .

- +

``FreeBSD handles [our] heavy load quite well and it is nothing short of amazing. Salutations to the FreeBSD team.''

diff --git a/en_US.ISO8859-1/htdocs/art.sgml b/en_US.ISO8859-1/htdocs/art.sgml index 34577ea7dd..a9926a7de0 100644 --- a/en_US.ISO8859-1/htdocs/art.sgml +++ b/en_US.ISO8859-1/htdocs/art.sgml @@ -128,7 +128,7 @@ href="http://www.freebsdfoundation.org">FreeBSD Foundation holds several FreeBSD related trademarks (among them the trademark for the term FreeBSD itself). For more - information about these trademarks read the FreeBSD Trademark Usage Terms and Conditions.

diff --git a/en_US.ISO8859-1/htdocs/availability.sgml b/en_US.ISO8859-1/htdocs/availability.sgml index e3f5c1065e..fefd29c072 100644 --- a/en_US.ISO8859-1/htdocs/availability.sgml +++ b/en_US.ISO8859-1/htdocs/availability.sgml @@ -8,7 +8,7 @@ - + &title; $FreeBSD$ diff --git a/en_US.ISO8859-1/htdocs/copyright/daemon.sgml b/en_US.ISO8859-1/htdocs/copyright/daemon.sgml index 27e4b61382..46613bcc0e 100644 --- a/en_US.ISO8859-1/htdocs/copyright/daemon.sgml +++ b/en_US.ISO8859-1/htdocs/copyright/daemon.sgml @@ -44,8 +44,8 @@ The copyright holder and creator of the daemon image is Marshall Kirk McKusick. A short pictorial - history is also available. There is a gallery of FreeBSD related -publications that use + history is also available. There is a gallery of FreeBSD related +publications that use variations of the daemon graphic.

Various size stuffed and beanie daemons are available from diff --git a/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.sgml b/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.sgml index 5749378927..70c7b2dfe4 100644 --- a/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.sgml +++ b/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.sgml @@ -38,16 +38,16 @@ -

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 +

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.

diff --git a/en_US.ISO8859-1/htdocs/developers/Makefile b/en_US.ISO8859-1/htdocs/developers/Makefile index a10df9a87f..51f47e016e 100644 --- a/en_US.ISO8859-1/htdocs/developers/Makefile +++ b/en_US.ISO8859-1/htdocs/developers/Makefile @@ -9,4 +9,4 @@ DOCS= cvs.sgml -.include "${DOC_PREFIX}/share/mk/web.site.mk" \ No newline at end of file +.include "${DOC_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/docproj/Makefile b/en_US.ISO8859-1/htdocs/docproj/Makefile index 6a6a8b94fd..6a61571c35 100644 --- a/en_US.ISO8859-1/htdocs/docproj/Makefile +++ b/en_US.ISO8859-1/htdocs/docproj/Makefile @@ -7,13 +7,13 @@ .include "../Makefile.inc" .endif -DOCS= current.sgml +DOCS= current.sgml DOCS+= doc-set.sgml DOCS+= handbook.sgml DOCS+= handbook3.sgml DOCS+= sgml.sgml DOCS+= submitting.sgml -DOCS+= who.sgml +DOCS+= who.sgml DOCS+= translations.sgml DOCS+= docproj.sgml DOCS+= todo.sgml diff --git a/en_US.ISO8859-1/htdocs/docproj/current.sgml b/en_US.ISO8859-1/htdocs/docproj/current.sgml index fcd1e8e128..bafcf569e8 100644 --- a/en_US.ISO8859-1/htdocs/docproj/current.sgml +++ b/en_US.ISO8859-1/htdocs/docproj/current.sgml @@ -22,7 +22,7 @@ - +

Here are the projects currently under way (or being actively contemplated on the freebsd-doc mailing list).

@@ -58,7 +58,7 @@ documentation set you should, at first, choose to work on one of the TODO list items.

- +

Open documentation problem reports

Current FreeBSD problems reports are tracked using the GNATS @@ -68,7 +68,7 @@ href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?category=docs&responsible=.">view the open documentation problem reports.

- +

Improve Handbook Index

Responsible: FreeBSD-doc < - +

Contribute Advocacy Slides/Presentations

Responsible: FreeBSD-doc @@ -119,7 +119,7 @@ improved as the default DocBook Slides XSL-FO stylesheets produce very spartan slides.

- +

Write a section in the Handbook and/or FAQ

Responsible: No one

@@ -129,25 +129,25 @@ these documents to complete a task, and found them lacking, please find the time to write up your experiences as a possible replacement.

- +

Alternatively, if you have just had to do something that had no entry in the FAQ and/or Handbook, please consider writing a new section. Then submit it as outlined above.

- - + +

Write some new Papers

The New SCSI layer for FreeBSD (CAM)

Responsible: - <doc@FreeBSD.org>, + <doc@FreeBSD.org>, <scsi@FreeBSD.org>

Synopsis: See The Design and Implementation of the FreeBSD SCSI Subsystem for a first snapshot.

- +

CGI Scripts

-

Responsible: +

Responsible: <doc@FreeBSD.org>, Wolfram Schneider <wosch@FreeBSD.org>

@@ -156,10 +156,10 @@ href="http://people.FreeBSD.org/~tom/portpm/">FreeBSD::Ports modules. These modules also need thorough testing.

- +

Multilingual Web scripts

-

Responsible: +

Responsible: <doc@FreeBSD.org>

@@ -184,10 +184,10 @@ - - + +

Translations of the FreeBSD Documentation

-

Responsible: +

Responsible: <doc@FreeBSD.org>

Translate the FreeBSD documentation (Web pages, FAQ, diff --git a/en_US.ISO8859-1/htdocs/docproj/doc-set.sgml b/en_US.ISO8859-1/htdocs/docproj/doc-set.sgml index 77d9860464..0cdc648a68 100644 --- a/en_US.ISO8859-1/htdocs/docproj/doc-set.sgml +++ b/en_US.ISO8859-1/htdocs/docproj/doc-set.sgml @@ -42,7 +42,7 @@ projects.

- +

FreeBSD Documentation Project Home diff --git a/en_US.ISO8859-1/htdocs/docproj/docproj.sgml b/en_US.ISO8859-1/htdocs/docproj/docproj.sgml index dabec1d4d0..078eb99349 100644 --- a/en_US.ISO8859-1/htdocs/docproj/docproj.sgml +++ b/en_US.ISO8859-1/htdocs/docproj/docproj.sgml @@ -17,7 +17,7 @@

Overview

Getting to grips with a new and complex operating system is always a - difficult task, no matter how pretty the GUI is. FreeBSD is no different + difficult task, no matter how pretty the GUI is. FreeBSD is no different in this respect.

While there are a vast number of BSD Unix (and general &unix;) books @@ -46,7 +46,7 @@

Current projects

- +

There are a number of projects currently in progress as part of the documentation effort. Please take the time to look over this list and see if there is anything you can help @@ -54,7 +54,7 @@ - +

Who we are, how to join

This page explains who makes up the Documentation Project, and how @@ -62,7 +62,7 @@

The FreeBSD Documentation Set

-

This page outlines the components of the FreeBSD Documentation Set, and +

This page outlines the components of the FreeBSD Documentation Set, and the sort of work that the Documentation Project does with them.

SGML and the Documentation Project

@@ -78,9 +78,9 @@ best way to submit documentation so that it gets looked at as soon as possible.

-

Translation

+

Translation

Translations of the FreeBSD documentation, Web pages, - Handbook, Manual pages and FAQ.

+ Handbook, Manual pages and FAQ.

diff --git a/en_US.ISO8859-1/htdocs/docproj/sgml.sgml b/en_US.ISO8859-1/htdocs/docproj/sgml.sgml index 994d0fee89..c19b6d4074 100644 --- a/en_US.ISO8859-1/htdocs/docproj/sgml.sgml +++ b/en_US.ISO8859-1/htdocs/docproj/sgml.sgml @@ -34,7 +34,7 @@ tags (the markers of the form <tag content>) to describe technical documentation for subsequent formatting. The FreeBSD Documentation Project adopted it and defined some new elements to make it more precise.

- +

For example, this is how you might write a brief paragraph in HTML (do not worry about the content, just look at the tags):

@@ -43,7 +43,7 @@ this file you should use vipw. However, if you just want to add a new user you can use adduser.

]]> - +

The same paragraph, marked up using DocBook, looks like

vipw. However, if you just want to add a new user
       you can use adduser.
 ]]>
- +

As you can see, DocBook is much more 'expressive' than HTML. In the HTML example the filename is marked up as being displayed in a 'typewriter' font. In the DocBook example the filename is marked up as being a @@ -94,7 +94,7 @@

  • Because the number of tags you can use is much larger, it takes longer to learn all of them, and how to use them effectively.

    - +

    A good way to learn SGML and DocBook is to read the source version of lots of example documents, seeing how other authors have written similar information.

    • @@ -104,7 +104,7 @@

    What if you do not know DocBook? Can you still contribute?

    - +

    Yes you can. Quite definitely. Any documentation is better than no documentation. If you have documentation to contribute and it is not marked up in DocBook, do not worry.

    @@ -123,13 +123,13 @@

    More information about SGML and DocBook?

    -

    First read the Documentation Project - Primer. This aims to be a comprehensive explanation of - everything you need to know in order to work with the FreeBSD +

    First read the Documentation Project + Primer. This aims to be a comprehensive explanation of + everything you need to know in order to work with the FreeBSD documentation. This is a long document, split into many smaller pages. You can - also view it as one large page.

    @@ -143,10 +143,10 @@
    http://www-sul.stanford.edu/tools/tutorials/html2.0/gentle.html
    -

    The "Gentle Introduction to SGML". Recommended reading for anyone +

    The "Gentle Introduction to SGML". Recommended reading for anyone who wants to learn more about SGML from a beginner's perspective.

    - +
    http://www.oasis-open.org/docbook/
    @@ -155,7 +155,7 @@ who want to learn DocBook.

    - +

    FreeBSD Documentation Project Home diff --git a/en_US.ISO8859-1/htdocs/docproj/submitting.sgml b/en_US.ISO8859-1/htdocs/docproj/submitting.sgml index c23579c925..e5c41a2a5b 100644 --- a/en_US.ISO8859-1/htdocs/docproj/submitting.sgml +++ b/en_US.ISO8859-1/htdocs/docproj/submitting.sgml @@ -25,20 +25,20 @@ the documentation and the pointer to its location, and solicit feedback.

    -

    If, for some reason, you cannot put the documentation up for FTP or on +

    If, for some reason, you cannot put the documentation up for FTP or on a web site somewhere you can send it directly to the FreeBSD-doc mailing list. If you do this, please only send plain-text documents.

    - +

    You should probably cc: this request for comments to other appropriate mailing lists. For example, something that relates to how to use CVSup to - keep your source tree up to date would be of interest to the subscribers + keep your source tree up to date would be of interest to the subscribers of the FreeBSD-current and FreeBSD-stable mailing lists.

    - +

    After people have looked over your documentation, and you have had the chance to incorporate any of their suggestions, you are ready to submit it.

    - +

    To do this, wrap it up into a tar file. If your documentation consists of three files, one, two, and three, and you want it all to go into doc.tar, do

    @@ -78,7 +78,7 @@ with some special formatting to a particular address. When you run send-pr you will be put into your editor (probably vi or emacs) with a template to fill out, and some instructions on how - to fill it out.

    + to fill it out.

    Make sure the "Category" is set to "docs" and that the "Class" is set to one of "change-request". You should include the .uue file @@ -110,7 +110,7 @@ 

         % cp foo.sgml foo.sgml.old
    - +

  • Then, make your changes to foo.sgml

    @@ -129,9 +129,9 @@
 	
    This looks at the difference between the two files, and writes them
 	  to the file foo.diff.
    • - +

    You can then send foo.diff back to the project. Send a PR as - described earlier, but include the foo.diff file in the body of the + described earlier, but include the foo.diff file in the body of the PR.

    FreeBSD Documentation Project Home diff --git a/en_US.ISO8859-1/htdocs/docproj/translations.sgml b/en_US.ISO8859-1/htdocs/docproj/translations.sgml index 79aa503767..93824d349b 100644 --- a/en_US.ISO8859-1/htdocs/docproj/translations.sgml +++ b/en_US.ISO8859-1/htdocs/docproj/translations.sgml @@ -203,7 +203,7 @@ http://www.bsd.ee/tolge.php

    The FreeBSD German Documentation Project

    -Web: https://doc.bsdgroup.de
    +Web: https://doc.bsdgroup.de
    E-Mail: de-bsd-translators@de.FreeBSD.org
    IRC: Server: irc.freenode.net, Channel: #FreeBSD-Doc.de
    @@ -343,7 +343,7 @@ http://www.bsd.ee/tolge.php

    The FreeBSD Korean Documentation Project

    -Web: http://www.kr.FreeBSD.org/projects/doc-kr/
    +Web: http://www.kr.FreeBSD.org/projects/doc-kr/
    E-Mail: doc@kr.FreeBSD.org
    diff --git a/en_US.ISO8859-1/htdocs/docproj/who.sgml b/en_US.ISO8859-1/htdocs/docproj/who.sgml index c21a78f0ed..9bceec5002 100644 --- a/en_US.ISO8859-1/htdocs/docproj/who.sgml +++ b/en_US.ISO8859-1/htdocs/docproj/who.sgml @@ -24,13 +24,13 @@ list of the principal committers for the FreeBSD Documentation Project.

    - +

    Others do not have commit privileges, but they write and submit documentation nonetheless. Once the documentation has been submitted according to the Submit Documentation page, one of the committers will then review it and include it in the documentation set.

    - +

    If you want to help out with the documentation project (and I fervently hope you do) all you have to do is subscribe to the mailing list and participate. As soon as you have done that, you're a member of the diff --git a/en_US.ISO8859-1/htdocs/donations/donors.sgml b/en_US.ISO8859-1/htdocs/donations/donors.sgml index c427b7c7f1..a576edce95 100644 --- a/en_US.ISO8859-1/htdocs/donations/donors.sgml +++ b/en_US.ISO8859-1/htdocs/donations/donors.sgml @@ -2687,7 +2687,7 @@ 6 SuperMicro servers brd (firewalls and infrastructure servers
    for the new NYC FreeBSD co-location) - Received + Received diff --git a/en_US.ISO8859-1/htdocs/events/2002/bsdcon-devsummit.sgml b/en_US.ISO8859-1/htdocs/events/2002/bsdcon-devsummit.sgml index 6040647032..58934503b6 100644 --- a/en_US.ISO8859-1/htdocs/events/2002/bsdcon-devsummit.sgml +++ b/en_US.ISO8859-1/htdocs/events/2002/bsdcon-devsummit.sgml @@ -258,7 +258,7 @@ munging you could have.

    Gnn : Have you looked at COM?

    - +

    Warner : I have a few comments. There are several problems in one here. I like the multiple inheritance. The versioning seems orthogonal. The multipath is @@ -307,7 +307,7 @@ script?

    Justin : No manually.

    - +

    Julian : The problem is the requirement where you can't break things. Perhaps we should have official breakage. For instance for a week.

    @@ -344,7 +344,7 @@ our own pre-processors.

    Robert : Let's move on.

    - +

    Nectar : COM does work its in Mozilla we can use this kind of technology. We don't need C++ to do those things.

    @@ -360,7 +360,7 @@ should not be in the fast path.

    Robert : Lets not go there.

    - +

    Warner : The other issue is the softc issue. Only one can own it.

    @@ -377,7 +377,7 @@ because we have no docs.

    Robert : Lets go to the phone.

    - +

    Robert : No technical questions on the phone.

    @@ -404,13 +404,13 @@ engineering later.

    David : Is everything in CVS?

    - +

    Benno : Not everything yet, but things have to be cleaned up. Some time in the next week after the invariants problem is fixed.

    PoulHK : What hardware?

    - +

    Benno : Right now on pSim which is in ports. Once that's working the first hardware will be new world apple hardware. Some old world apple hardware and then a Motorola @@ -440,9 +440,9 @@ boards.

    Justin : How different are these?

    - +

    Gnn : Very different.

    - +

    Anon : Have you had any help from Apple or hardware vendors?

    @@ -500,11 +500,11 @@

    Anon : What is the bootstrapping?

    - +

    Jake : TFTP.

    - +

    Robert : Bootloader?

    - +

    Jake : We can mount Solaris disks.

    @@ -527,18 +527,18 @@ kernel.

    Terry : Do you document that?

    - +

    Jake : It's mostly pmap.

    - +

    Anon : SBUS support?

    - +

    Jake : Ultra 2 has sbus support.

    Benno : Have you got the gem ethernet driver working?

    Jake : Yes.

    - +

    Robert : Any questions on the phone?

    @@ -558,7 +558,7 @@ this?

    David : Someone in Canada.

    - +

    Robert : Is the person who's doing this work willing to go all the way to maintain it etc.

    @@ -589,7 +589,7 @@

    John : What are the plans 5.0?

    - +

    David : Interest is in new ports. For instance C++ will lag. Like you say we need gcc3.1 and binutils. Will commit to get kernel and interesting parts of user @@ -731,7 +731,7 @@ further we should look at NetBSD.

    PoulHK : Is there interest?

    - +

    Gnn : Removable media is reason enough to do it.

    @@ -846,7 +846,7 @@ issues?

    Justin : What is the name space?

    - +

    PoulHK : The control will be sysctl. I want to remove the ioctls from these. I haven't really decided on the name space. I want to make sure that /dev does not @@ -949,7 +949,7 @@ evaluating the recent SACK implementation?

    Luigi : That broke standard TCP.

    - +

    Alfred : Actually SACK is out of style now. One other thing on performance is that the drivers do a mget/mclget at once.

    @@ -964,7 +964,7 @@ doing. Julian will you own that?

    Julian : Yes.

    - +

    Anon : Impact of polling scheme on SMP?

    @@ -989,7 +989,7 @@ FreeBSD at all?

    Gnn : ATM is necessary for DSL

    - +

    Justin : What about DAFS? That uses ATM.

    @@ -1047,7 +1047,7 @@ hierarchy of device drivers.

    Terry : Virtual interfaces.

    - +

    PoulHK : This ties into another issue about how we look at our interfaces. No one notices when I unplug my device.

    @@ -1059,7 +1059,7 @@ dhclient.

    Gnn : Need new routing messages.

    - +

    Paul Richards : Wants activities brought up to userland for devd.

    @@ -1070,7 +1070,7 @@ routing socket event.

    All : Discuss on mailing list.

    - +

    Jonathan L : If we're talking about doing this with cables this works with MII but it's only in kevent and not in routing sockets.

    @@ -1081,12 +1081,12 @@

    PoulHK : Re raise netgraph issue. What is the future of netgraph in the tree right now. We have very few users now.

    - +

    Julian : What parts are not done?

    - +

    PoulHK : Configuration etc.

    - +

    Alfred : Netgraph is extremely useful. It needs to be documented and a bit more bolted down.

    @@ -1106,7 +1106,7 @@ with having ppp take over mpd.

    Gnn : Can we use netgraph for SMP?

    - +

    Peter W : I'm a refugee from a streams based system. It's scary. Be a little bit careful.

    @@ -1236,7 +1236,7 @@ a better system.

    Alfred : m_aux

    - +

    Robert : sounds expensive because of the list stuff

    @@ -1359,7 +1359,7 @@ me as an Nth or an N+1.

    Alfred : OK.

    - +

    Peter W : It works just like fork except instead of retuning just once in the parent/child it returns over and over again.

    @@ -1411,7 +1411,7 @@ blocking syscall and blocks.

    Julian : That thread is blocked.

    - +

    Nick S : What happens when there is nothing to do?

    @@ -1424,7 +1424,7 @@ implications?

    Julian : None.

    - +

    Peter W : For disk performance it will be great.

    @@ -1481,12 +1481,12 @@ overview?

    John : I'm working on that.

    - +

    Greg : What about light weight interrupts?

    John : No real need.

    - +

    Greg : I think we're going to fail unless we have a good theoretical base.

    @@ -1502,16 +1502,16 @@ either. I don't believe that can we make a full map.

    Greg : I think we can.

    - +

    PoulHK : We're talking about redoing sections of code.

    John : What key milestones?

    - +

    Greg : Light weight threads.

    - +

    Peter/John : Already done.

    - +

    Justin : Having been at the SMPng meeting the general consensus was to come up with a framework. LWT is an optimization. Maybe only to 2 CPUs at 5.0

    @@ -1576,7 +1576,7 @@ get us out from giant.

    PoulHK : I need documentation.

    - +

    Anon : I will be happy to help you with words.

    @@ -1596,12 +1596,12 @@ locks are just null right?

    John : Yes on spin locks.

    - +

    Nick S : Nevermind.

    - +

    Luigi : Do we care about performance on uniprocessors on 5.0?

    - +

    John : One thing that SMPng may help buy is that if you have two network interfaces then you can handle more stuff.

    @@ -1610,7 +1610,7 @@ uniprocessor on 5.0.

    John : Yes

    - +

    Julian : In the uniprocessor case KSE degrades down to forkeed processors.

    @@ -1653,7 +1653,7 @@

    John : That might be pushing it.

    - +

    Anon : Can we push Usenix back a bit? (Laughter)

    @@ -1667,7 +1667,7 @@ multiple release branches?

    Robert : Good to have around.

    - +

    Alfred : Could we reach a consensus on what sort of debugging will be in 5.0?

    @@ -1728,7 +1728,7 @@ ALTERNATE to give us?

    Murray : Wide spread testing.

    - +

    Alfred : I think the sooner the better.

    @@ -1761,12 +1761,12 @@ ALTERNATE it that on a daily basis that things suck so bad?

    David : Why does it suck so bad?

    - +

    Justin : Because people don't get shat on for breaking things.

    Robert : Why does it suck?

    - +

    Justin : I put it on my server and its slow. Instead of fixing PCI interrupts.

    @@ -1778,7 +1778,7 @@ ALTERNATE date and roll your CD.

    Gnn : These are different issues.

    - +

    Justin : The people that used to complain about it but don't anymore.

    @@ -1795,7 +1795,7 @@ ALTERNATE a cool project. So just giving up and saying it is hard is BS.

    Gnn : Process, process, process...

    - +

    Julian : Breaking the build is not as bad as breaking the kernel. What's harder is committing a subsystem that affects another subsystem. In terms of the process @@ -1886,9 +1886,9 @@ ALTERNATE

    Murray : Any issues with the name?

    - +

    PoulHK : Why not snapshot?

    - +

    Warner : I think the dates look good but I would pick a different.

    @@ -1905,13 +1905,13 @@ ALTERNATE these at Usenix?

    All : Yes.

    - +

    John : 2 days?

    - +

    Robert : What could we do better?

    - +

    Sundry : parking validation, connectivity, projector, catered lunch, ...

    diff --git a/en_US.ISO8859-1/htdocs/events/2002/usenix-devsummit.sgml b/en_US.ISO8859-1/htdocs/events/2002/usenix-devsummit.sgml index f3ecab65cc..348a2349f3 100644 --- a/en_US.ISO8859-1/htdocs/events/2002/usenix-devsummit.sgml +++ b/en_US.ISO8859-1/htdocs/events/2002/usenix-devsummit.sgml @@ -754,7 +754,7 @@ UP.

    obrien : Are we heading for a release?

    murray : yes.

    - +

    obrien : Then we have to stop having major commits.

    diff --git a/en_US.ISO8859-1/htdocs/features.sgml b/en_US.ISO8859-1/htdocs/features.sgml index e6e47d3b83..7396d2efd6 100644 --- a/en_US.ISO8859-1/htdocs/features.sgml +++ b/en_US.ISO8859-1/htdocs/features.sgml @@ -12,9 +12,9 @@ - +

    FreeBSD offers many advanced features.

    - +

    No matter what the application, you want your system's resources performing at their full potential. FreeBSD's focus on performance, networking, and storage combine with easy system @@ -107,11 +107,11 @@ disk cache. As a result, programs receive both excellent memory management and high performance disk access, and the system administrator is freed from the task of tuning cache sizes. - +

  • Compatibility modules enable programs for other operating systems to run on FreeBSD, including programs for Linux, SCO UNIX, and System V Release 4.
    • - +
  • Soft Updates allows improved filesystem performance without sacrificing safety and reliability. It analyzes meta-data filesystem operations to avoid having diff --git a/en_US.ISO8859-1/htdocs/gifs/Makefile b/en_US.ISO8859-1/htdocs/gifs/Makefile index 5a2dbec3eb..116dd8b9be 100644 --- a/en_US.ISO8859-1/htdocs/gifs/Makefile +++ b/en_US.ISO8859-1/htdocs/gifs/Makefile @@ -22,12 +22,12 @@ DATA+= jp.jpg jpb.jpg kr.jpg krb.jpg las5.jpg las5b.jpg las512.jpg DATA+= las512b.jpg las523.jpg las523b.jpg wc-docs.jpg wc-docsb.jpg DATA+= pc98-jp.jpg pc98-jpb.jpg pht.jpg phtb.jpg running.jpg DATA+= runningb.jpg starkit.jpg starkitb.jpg tw.jpg twb.jpg -DATA+= unixuser.jpg unixuserb.jpg wc-10.jpg wc-10b.jpg wc-11.jpg wc-11b.jpg -DATA+= wc-200.jpg wc-200b.jpg wc-205.jpg wc-205b.jpg wc-21.jpg wc-215.jpg -DATA+= wc-215b.jpg wc-216.jpg wc-216b.jpg wc-216jp.jpg wc-216jpb.jpg -DATA+= wc-217.jpg wc-217b.jpg wc-21b.jpg wc-221.jpg wc-221b.jpg -DATA+= wc-222.jpg wc-222b.jpg wc-22snap.jpg wc-22snapb.jpg -DATA+= wc-44lite2.jpg wc-44lite2b.jpg wc-blun.jpg wc-blunb.jpg +DATA+= unixuser.jpg unixuserb.jpg wc-10.jpg wc-10b.jpg wc-11.jpg wc-11b.jpg +DATA+= wc-200.jpg wc-200b.jpg wc-205.jpg wc-205b.jpg wc-21.jpg wc-215.jpg +DATA+= wc-215b.jpg wc-216.jpg wc-216b.jpg wc-216jp.jpg wc-216jpb.jpg +DATA+= wc-217.jpg wc-217b.jpg wc-21b.jpg wc-221.jpg wc-221b.jpg +DATA+= wc-222.jpg wc-222b.jpg wc-22snap.jpg wc-22snapb.jpg +DATA+= wc-44lite2.jpg wc-44lite2b.jpg wc-blun.jpg wc-blunb.jpg DATA+= wc-30snab.jpg wc-30sna.jpg newsletb.jpg newslett.jpg DATA+= newslet2b.jpg newslet2.jpg DATA+= banner1.gif banner2.gif banner3.gif banner4.gif diff --git a/en_US.ISO8859-1/htdocs/gnome/docs/faq210.sgml b/en_US.ISO8859-1/htdocs/gnome/docs/faq210.sgml index bbe377d331..af1957ef60 100644 --- a/en_US.ISO8859-1/htdocs/gnome/docs/faq210.sgml +++ b/en_US.ISO8859-1/htdocs/gnome/docs/faq210.sgml @@ -160,7 +160,7 @@ $ tail -f /path/to/logfile
  • #167934: [gnome-menus] Any .desktop file in share/gnome/apps without a Categories entry will not work. This is due - to a + to a LegacyDir bug that is supposed to be fixed in next release (2.10.1). The workaround is to add a Categories entry in the .desktop file in question.
    • diff --git a/en_US.ISO8859-1/htdocs/gnome/docs/faq224.sgml b/en_US.ISO8859-1/htdocs/gnome/docs/faq224.sgml index fce9ac107c..a61fc264f9 100644 --- a/en_US.ISO8859-1/htdocs/gnome/docs/faq224.sgml +++ b/en_US.ISO8859-1/htdocs/gnome/docs/faq224.sgml @@ -112,7 +112,7 @@ gdm.) -CURRENT. If you try to use hal with usb2, the hald daemon will take up 100% of the CPU. Work is underway to fix this. - +
  • Session management is broken in GNOME &gnomever;. See http://np237.livejournal.com/22014.html for more details. A diff --git a/en_US.ISO8859-1/htdocs/gnome/docs/faq230.sgml b/en_US.ISO8859-1/htdocs/gnome/docs/faq230.sgml index 89190cbaa6..50ff1b26c9 100644 --- a/en_US.ISO8859-1/htdocs/gnome/docs/faq230.sgml +++ b/en_US.ISO8859-1/htdocs/gnome/docs/faq230.sgml @@ -110,11 +110,11 @@ within FreeBSD. Some of the more visible issues are:

      -
    • Clutter based applications like mutter and a number of - gnome-games, will crash when using Software Rasterizer rendering. +
    • Clutter based applications like mutter and a number of + gnome-games, will crash when using Software Rasterizer rendering. You can check it with glxinfo | grep render. A solution is being worked on.
      • -
    • Brasero has a bug that it crashes when creating new burn projects. +
    • Brasero has a bug that it crashes when creating new burn projects. Premade iso burning works as expected.
    • PackageKit where ported to FreeBSD. It does have some rough edges still.
    diff --git a/en_US.ISO8859-1/htdocs/gnome/docs/faq232.sgml b/en_US.ISO8859-1/htdocs/gnome/docs/faq232.sgml index bfa976c654..7736f25cfb 100644 --- a/en_US.ISO8859-1/htdocs/gnome/docs/faq232.sgml +++ b/en_US.ISO8859-1/htdocs/gnome/docs/faq232.sgml @@ -46,7 +46,7 @@

    To build GNOME &gnomever;, you need to obtain the latest ports tree skeleton. This is most easily accomplished with portsnap(8) or CVSup. + href="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html">CVSup. Simply obtain the latest ports tree, and you are ready to go.

    If you are a portupgrade(1) users, Then do the following:

    @@ -96,11 +96,11 @@ within FreeBSD. Some of the more visible issues are:

      -
    • Clutter based applications like mutter and a number of - gnome-games, will crash when using Software Rasterizer rendering. +
    • Clutter based applications like mutter and a number of + gnome-games, will crash when using Software Rasterizer rendering. You can check it with glxinfo | grep render. A solution is being worked on.
      • -
    • Brasero has a bug that it crashes when creating new burn projects. +
    • Brasero has a bug that it crashes when creating new burn projects. Premade iso burning works as expected.
    • PackageKit where ported to FreeBSD. It does have some rough edges still.
    diff --git a/en_US.ISO8859-1/htdocs/gnome/news.xml b/en_US.ISO8859-1/htdocs/gnome/news.xml index f05a5dcadb..10ca13efae 100644 --- a/en_US.ISO8859-1/htdocs/gnome/news.xml +++ b/en_US.ISO8859-1/htdocs/gnome/news.xml @@ -36,12 +36,12 @@ News//EN" http://library.gnome.org/misc/release-notes/2.32/

    -

    This will be the last release of the GNOME 2.x series, mainly a bugfix +

    This will be the last release of the GNOME 2.x series, mainly a bugfix and bridge release to the first release of the GNOME 3.x series.

    This release features commits by avl, marcus, mezz and myself.

    -

    The FreeBSD GNOME Team would like to thank the following contributors +

    The FreeBSD GNOME Team would like to thank the following contributors and testers for there help with this release:

    @@ -80,33 +80,33 @@ News//EN" Announcing GNOME 2.30.1. for FreeBSD!

    Presenting GNOME 2.30.1 for FreeBSD. The official release - notes for this release can be found at + notes for this release can be found at http://library.gnome.org/misc/release-notes/2.30/

    -

    This release brings initial PackageKit support, Upower (replaces +

    This release brings initial PackageKit support, Upower (replaces power management part of hal), cuse4bsd integration with HAL and cheese, and a faster Evolution.

    Sadly GNOME 2.30.x will be the last release with FreeBSD 6.X support. - This will also be the last of the 2.x releases. The next release will - be the highly-anticipated GNOME 3.0 which will bring with it a new UI + This will also be the last of the 2.x releases. The next release will + be the highly-anticipated GNOME 3.0 which will bring with it a new UI experience.

    -

    Currently, there are a few bugs with GNOME 2.30 that may be of note - for our users. Be sure to consult the 2.30 upgrade FAQ at +

    Currently, there are a few bugs with GNOME 2.30 that may be of note + for our users. Be sure to consult the 2.30 upgrade FAQ at http://www.freebsd.org/gnome/docs/faq230.html> - for specific upgrading instructions, and the up-to-date list of known + for specific upgrading instructions, and the up-to-date list of known issues.

    -

    This release features commits by: avl, ahze, bland, marcus, mezz +

    This release features commits by: avl, ahze, bland, marcus, mezz and myself.

    The FreeBSD GNOME Team would like to thank Anders F Bjorklund for doing the initial packagekit porting.

    -

    And the following contributors and testers for there help with this +

    And the following contributors and testers for there help with this release:

    diff --git a/en_US.ISO8859-1/htdocs/handbook/Makefile b/en_US.ISO8859-1/htdocs/handbook/Makefile index 0d9cd7ac04..2804c67452 100644 --- a/en_US.ISO8859-1/htdocs/handbook/Makefile +++ b/en_US.ISO8859-1/htdocs/handbook/Makefile @@ -7,6 +7,6 @@ .include "../Makefile.inc" .endif -DATA= index.html +DATA= index.html .include "${DOC_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/internal/Makefile b/en_US.ISO8859-1/htdocs/internal/Makefile index 8a78b19615..34f2c1ca39 100644 --- a/en_US.ISO8859-1/htdocs/internal/Makefile +++ b/en_US.ISO8859-1/htdocs/internal/Makefile @@ -17,7 +17,7 @@ DOCS+= expire-bits.sgml DOCS+= fortunes.sgml DOCS+= hats.sgml DOCS+= i18n.sgml -DOCS+= internal.sgml +DOCS+= internal.sgml DOCS+= machines.sgml DOCS+= mirror.sgml DOCS+= new-account.sgml @@ -28,7 +28,7 @@ DOCS+= statistic.sgml INDEXLINK= internal.html -# build the list of personal homepages of FreeBSD developers only +# build the list of personal homepages of FreeBSD developers only # on the main FreeBSD machines hostname!= hostname .if ${hostname} == "hub.freebsd.org" || ${hostname} == "freefall.freebsd.org" || ${hostname} == "www.freebsd.org" diff --git a/en_US.ISO8859-1/htdocs/internal/machines.sgml b/en_US.ISO8859-1/htdocs/internal/machines.sgml index 7589848a94..83ced05141 100644 --- a/en_US.ISO8859-1/htdocs/internal/machines.sgml +++ b/en_US.ISO8859-1/htdocs/internal/machines.sgml @@ -283,7 +283,7 @@ this file.

    freefall Intel x86 2x dual-core 2.80GHz Xeon (Pentium-IV family), 2GB Memory, -Compaq Smart Array 5i SCSI RAID controller, 138 GB SCSI local storage, +Compaq Smart Array 5i SCSI RAID controller, 138 GB SCSI local storage, Broadcom-based Compaq NC7781 Gigabit Server Adapter NIC. @@ -412,12 +412,12 @@ this includes changes to user accounts or filesystem layout.

    All new user accounts must be cleared with the admin staff, and are given only to FreeBSD developers, either in the docs, ports or general -src hacking category. Accounts may be given to non-project developers -if they have a specific need to test something of a truly experimental +src hacking category. Accounts may be given to non-project developers +if they have a specific need to test something of a truly experimental nature and need access to a FreeBSD machine for the purpose. See New Account Creation Procedure page for details on new accounts. Accounts -are not given to the general public for "vanity domain" mail or +are not given to the general public for "vanity domain" mail or other such uses. It would be a waste of time to ask. Thanks.

    FreeBSD Internal Home diff --git a/en_US.ISO8859-1/htdocs/internal/mirror.sgml b/en_US.ISO8859-1/htdocs/internal/mirror.sgml index 4617930b7b..276e3c3dc4 100644 --- a/en_US.ISO8859-1/htdocs/internal/mirror.sgml +++ b/en_US.ISO8859-1/htdocs/internal/mirror.sgml @@ -13,11 +13,11 @@ -

    You can (and are encouraged to) mirror the FreeBSD web pages -www.FreeBSD.org. +

    You can (and are encouraged to) mirror the FreeBSD web pages +www.FreeBSD.org. To do this, you need to obtain and install -a program called cvsup on your web server. +a program called cvsup on your web server. CVSup is a software package for distributing and updating collections of files across a network.

    diff --git a/en_US.ISO8859-1/htdocs/internal/new-account.sgml b/en_US.ISO8859-1/htdocs/internal/new-account.sgml index 2566a25064..b2fa9f426d 100644 --- a/en_US.ISO8859-1/htdocs/internal/new-account.sgml +++ b/en_US.ISO8859-1/htdocs/internal/new-account.sgml @@ -30,7 +30,7 @@

    Any commit bit requests that do not follow the guidelines outlined above will be delayed (at best) or earn you negative vibrations from the respective team / team secretary. -

    +

    Responsible party for this procedure is:

      @@ -63,7 +63,7 @@

      NOTE: New account requests from anyone other than these entities or requests signed with PGP keys other than from these - entities will not be acted upon. No exceptions. In case of + entities will not be acted upon. No exceptions. In case of a new ports or doc committer the account request email should be CC:-ed to core.

      @@ -106,7 +106,7 @@ the new committer will start to work in. For src and doc commit bits, an entry should also be added to the mentors file in the respective Subversion repository to indicate - the mentor relationship. Having done all that, + the mentor relationship. Having done all that, the new committer and mentor jointly go through the first commit operations.

      @@ -118,20 +118,20 @@ and Traditions section.

      End Of Mentorship

      - +

      There is no pre-set duration for a mentorship. Once the mentor feels - the mentee is ready to 'fly solo' the mentor notifies the developer + the mentee is ready to 'fly solo' the mentor notifies the developer community by removing the entry from the mentors file in SVN, - or via a forced commit to access in CVS with an appropriate + or via a forced commit to access in CVS with an appropriate commit message.

      Transfer Of Mentorship

      - +

      Should a need arise to transfer mentorship for a committer please email the responsible party, as described for a new account proposal. Typically this request is rubberstamped as-is. In Subversion, the mentors file should be updated. - In CVS, a forced commit to access with an appropriate commit + In CVS, a forced commit to access with an appropriate commit message is to be used to inform the world of the transfer.

      diff --git a/en_US.ISO8859-1/htdocs/internal/statistic.sgml b/en_US.ISO8859-1/htdocs/internal/statistic.sgml index 090ffb71ef..5c38754b5c 100644 --- a/en_US.ISO8859-1/htdocs/internal/statistic.sgml +++ b/en_US.ISO8859-1/htdocs/internal/statistic.sgml @@ -35,7 +35,7 @@

      FTP traffic at ftp.FreeBSD.org

      -We set a new traffic record for +We set a new traffic record for TeraSolutions and Lightning Internet Services at 29-Sep-2000, over 2TB.
      Previous record was set for diff --git a/en_US.ISO8859-1/htdocs/internet.sgml b/en_US.ISO8859-1/htdocs/internet.sgml index 9de0d7099f..e05a4de53a 100644 --- a/en_US.ISO8859-1/htdocs/internet.sgml +++ b/en_US.ISO8859-1/htdocs/internet.sgml @@ -12,9 +12,9 @@ - +

      FreeBSD was designed for the Internet

      - +

      FreeBSD includes what many consider the reference implementation for TCP/IP software, the 4.4 BSD TCP/IP protocol stack, thereby making it ideal for network applications and the Internet. @@ -46,7 +46,7 @@

    • Route packets between multiple interfaces, including PPP and SLIP lines
      • - +
    • Use IP Multicast services (the MBONE)
    • Provide services over IPv6
      • diff --git a/en_US.ISO8859-1/htdocs/ipv6/index.sgml b/en_US.ISO8859-1/htdocs/ipv6/index.sgml index c129791916..c1c6c35704 100644 --- a/en_US.ISO8859-1/htdocs/ipv6/index.sgml +++ b/en_US.ISO8859-1/htdocs/ipv6/index.sgml @@ -3,10 +3,10 @@ "http://www.FreeBSD.org/XML/doc/share/sgml/xhtml10-freebsd.dtd" [ + --> OpenBSD 4.5 Release Songs - Games @@ -11474,7 +11474,7 @@ FreeBSD Portsnap http://www.daemonology.net/papers/ - "FreeBSD Portsnap - + "FreeBSD Portsnap - What (it is), Why (it was written), and How (it works)" by Colin Percival (cperciva@FreeBSD.org)
      (Note: use ^L to get back in non-fullscreen mode) @@ -11526,7 +11526,7 @@ Server deployment in mass-hosting environment using FreeBSD Ports system by Stanislav Sedov (in russian) http://blog.springdaemons.com/freebsd/ - +

      Recently I have been attending Hostobzor 12th, the Russian conference of hosting providers, beeing @@ -11549,7 +11549,7 @@ much... At least, some people was interested a lot and asked interesting questions.

      - +       hostobzor,hostobzor12,freebsd,ports,stanislav sedov,russian @@ -11659,7 +11659,7 @@ team en is momenteel 1 van de meest actieve developers binnen het team.

      - +       nllgg,freebsd,documentation,nederlands,remko lodder @@ -11695,7 +11695,7 @@ dergelijke onderzoeken maakt hij ook regelmatig gebruik van op BSD* gebaseerde systemen.

      - + nllgg,bsd,history,hans van de looy diff --git a/en_US.ISO8859-1/htdocs/news/1996/index.sgml b/en_US.ISO8859-1/htdocs/news/1996/index.sgml index 33613d4904..5a818cf317 100644 --- a/en_US.ISO8859-1/htdocs/news/1996/index.sgml +++ b/en_US.ISO8859-1/htdocs/news/1996/index.sgml @@ -14,7 +14,7 @@

      December 1996

      - +

      • 24-Dec-1996 FreeBSD Release Notes for more information.

        • - +

      • 13-Dec-1996 FreeBSD 2.2-RELEASE will not support installation on machines with less than 5MB of RAM or 1.2MB floppy @@ -33,7 +33,7 @@

      November 1996

      - + - +

      October 1997

        @@ -104,7 +104,7 @@ code for the Myrinet driver, are available from the CCCI's WWW page.

        - +

      • 03-Aug-97 Netscape Communications has released a beta version of Netscape Communicator v4.0 for FreeBSD. It can be @@ -112,7 +112,7 @@ href="ftp://ftp.netscape.com/pub/communicator/4.03/4.03b8/english/unix/freebsd/base_install/">ftp.netscape.com or its mirrors.

      - +

      July 1997

      @@ -122,7 +122,7 @@ FreeBSD, is in beta testing. To get the latest version, see http://www.promo.de/pub/people/stefan/netatalk/ or ftp://ftp.promo.de/pub/people/stefan/netatalk/.

      - +

    • 17-Jul-97 The first issue of the FreeBSD Newsletter is now available in Adobe PDF @@ -145,7 +145,7 @@ in stock; subscription customers should receive them shortly.

    - +

    May 1997

      @@ -165,7 +165,7 @@ kept for a minimum of one week.

    - +

    April 1997

    February 1997

    - +

    • 20-Feb-1997 FreeBSD 2.1.7-RELEASE is now available. Read the @@ -233,7 +233,7 @@ the README.TXT file for more information about this release.

      • - +

    • 06-Feb-1997 A serious security problem affecting FreeBSD 2.1.6 and earlier systems was found. The problem has been corrected @@ -243,7 +243,7 @@ solution from the FreeBSD-SA-97:01.setlocale security announcement.

      • - +

    • 06-Feb-1997 The final pre-release version of FreeBSD 2.2-GAMMA, is now available. The README.TXT file has more @@ -268,7 +268,7 @@ more information.

    - + News Home diff --git a/en_US.ISO8859-1/htdocs/news/1998/index.sgml b/en_US.ISO8859-1/htdocs/news/1998/index.sgml index 334dca8f27..4a26fb5746 100644 --- a/en_US.ISO8859-1/htdocs/news/1998/index.sgml +++ b/en_US.ISO8859-1/htdocs/news/1998/index.sgml @@ -179,7 +179,7 @@ viewer. Article submissions, advertisements, and letters to the editor should be sent to newsletter@FreeBSD.org.

    • - +

  • 01-May-98 The FreeBSD Project set up Anonymous CVS for the @@ -238,7 +238,7 @@ binary release snapshots from current.FreeBSD.org

- + News Home diff --git a/en_US.ISO8859-1/htdocs/news/1999/index.sgml b/en_US.ISO8859-1/htdocs/news/1999/index.sgml index bc16e08381..266e43e81c 100644 --- a/en_US.ISO8859-1/htdocs/news/1999/index.sgml +++ b/en_US.ISO8859-1/htdocs/news/1999/index.sgml @@ -205,7 +205,7 @@ CDs soon. Anyone who wishes to order 3.2-RELEASE or to subscribe may do so via The FreeBSD Mall.

- +

  • 08-Jun-1999 A new Australian FreeBSD Web Mirror now exists. Thanks to Hidetoshi Shimokawa (Alpha/Ports)

    • - + News Home diff --git a/en_US.ISO8859-1/htdocs/news/2000/index.sgml b/en_US.ISO8859-1/htdocs/news/2000/index.sgml index dfb9246430..46d660d774 100644 --- a/en_US.ISO8859-1/htdocs/news/2000/index.sgml +++ b/en_US.ISO8859-1/htdocs/news/2000/index.sgml @@ -99,7 +99,7 @@ New FreeBSD Core Team Elected! Read the official press release for more information.

    - +

  • 16-Oct-2000 A new committer: Jonathan Chen (newcard cardbus)

    • @@ -230,15 +230,15 @@

    June 2000

    - +

    • 30-June-2000 http://freshports.org/ has - been upgraded to FreshPorts 1.1. The FreshPorts website contains - the latest details of which ports have been create/updated/removed. + been upgraded to FreshPorts 1.1. The FreshPorts website contains + the latest details of which ports have been create/updated/removed. This upgrade, the first since FreshPorts was release in early May, - gives you an improved home page, which together with a commit - history means you can find out about your ports faster and + gives you an improved home page, which together with a commit + history means you can find out about your ports faster and easier.

    • 29-June-2000 @@ -262,7 +262,7 @@ A new committer: MIHIRA Sanpei Yoshiro (PC-Card)

      -

      A new committer: Coleman +

      A new committer: Coleman Kane (3dfx voodoo for glide/Mesa)

    • 19-June-2000 @@ -270,14 +270,14 @@ Junho (Ports)

    • 08-June-2000 - Jordan Hubbard and Warner Losh will be in Japan during the first - part of June 2000. They will be giving talks at: the BSD BOF at + Jordan Hubbard and Warner Losh will be in Japan during the first + part of June 2000. They will be giving talks at: the BSD BOF at Networld+Interop 2000 Tokyo (8th), the JUS seminor at Tokyo (9th), - the NBUG event at Nagoya (10th), and, the K*BUG seminor at Osaka + the NBUG event at Nagoya (10th), and, the K*BUG seminor at Osaka (10th). Please see http://www.jp.FreeBSD.org/.

      -

      A new article is available, explaining how to A new article is available, explaining how to use PPP, natd, and ipfw to implement a firewall with a PPP dialup connection.

      @@ -344,7 +344,7 @@ Bill Swingle has written an article on the Ports and Packages System for 32bitsonline.com

      • + href="http://www.32bitsonline.com/">32bitsonline.com

    • 20-Mar-2000 A new committer: Will diff --git a/en_US.ISO8859-1/htdocs/news/2001/news.xml b/en_US.ISO8859-1/htdocs/news/2001/news.xml index a96fa771e5..9187d602b8 100644 --- a/en_US.ISO8859-1/htdocs/news/2001/news.xml +++ b/en_US.ISO8859-1/htdocs/news/2001/news.xml @@ -4,16 +4,16 @@ @@ -75,9 +75,9 @@ FreeBSD-stable tree frozen in preparation for 4.5

      The FreeBSD-stable branch of the source tree has now been - frozen in preparation for the release of FreeBSD 4.5. This means - that any new commits to the -stable source tree must be approved - by the release engineering team first. Our expected "ship" date + frozen in preparation for the release of FreeBSD 4.5. This means + that any new commits to the -stable source tree must be approved + by the release engineering team first. Our expected "ship" date for 4.5 is January 20th, 2002.

      @@ -90,20 +90,20 @@ - "Backports" site, with patches for older FreeBSD + <title>"Backports" site, with patches for older FreeBSD releases

      The - FreeBSD Backports Collection is a new site created by - D J Hawkey Jr. It contains patches that appeared in - FreeBSD-stable that have not yet been merged in to older + FreeBSD Backports Collection is a new site created by + D J Hawkey Jr. It contains patches that appeared in + FreeBSD-stable that have not yet been merged in to older releases. Wider testing of these patches makes it more likely that they will be committed to earlier FreeBSD releases. So if your site relies on earlier releases of FreeBSD, and, for whatever reason, you do not wish to update to the most recent release, you are encouraged to visit this site frequently.

      - + 20 @@ -166,14 +166,14 @@ Writing FreeBSD Problem Reports - +

      Dag-Erling Smørgrav has written an article about writing FreeBSD problem reports.

             - + 20 @@ -184,7 +184,7 @@ Core Appoints Bugmeister - +

      The FreeBSD Core Team has appointed Dag-Erling Smørgrav as Bugmeister.

      @@ -244,7 +244,7 @@ 2 -

      New committer: MANTANI +

      New committer: MANTANI Nobutaka (Ports)

       @@ -283,7 +283,7 @@ 26 -

      New committer: Makoto +

      New committer: Makoto Matsushita (release building)

             @@ -293,8 +293,8 @@ Bootstrapping Vinum: A Foundation for Reliable Servers -

      Bob Van Valzah has submitted - an article introducing Bob Van Valzah has submitted + an article introducing failure-resilient servers and step-by-step instructions for building one with Vinum.

      @@ -333,7 +333,7 @@ 17 -

      New committer: Akio +

      New committer: Akio Morita (PC98)

       @@ -379,7 +379,7 @@ August 2001 Status Report -

      The August 2001 Status Report is now available; see the +

      The August 2001 Status Report is now available; see the Status Reports Web Page.

       @@ -410,7 +410,7 @@ FreeBSD 5.0 delayed until November 2002

      FreeBSD 5.0 has been delayed until November 2002. The - complete announcement from Jordan is available here.

       @@ -440,10 +440,10 @@ New-user focused FreeBSD book available

      Annelise Anderson, a frequent contributor to the FreeBSD mailing - lists, has written "FreeBSD: An Open-Source Operating System - for Your PC", an introduction to FreeBSD aimed at the new user. + lists, has written "FreeBSD: An Open-Source Operating System + for Your PC", an introduction to FreeBSD aimed at the new user. Published by The Bit Tree Press, the ISBN is 0971204500, and it - can be ordered from, amongst other places, the + can be ordered from, amongst other places, the DaemonNews Mall.

      @@ -454,10 +454,10 @@ Installation documentation substantially improved -

      The +

      The Installing FreeBSD - section of the - Handbook + section of the + Handbook has been substantially improved and updated. The new documentation features "screenshots" of almost every stage of the installation process, and expanded text detailing what each stage @@ -465,7 +465,7 @@ Randy Pratt.

       - + 14 @@ -500,8 +500,8 @@

      An RDF file of the last 10 news headlines on the FreeBSD site is now available. The URL is http://www.FreeBSD.org/news/news.rdf. You can use this file to syndicate FreeBSD news headlines on to your own web - site (as Daily - DaemonNews and the + site (as Daily + DaemonNews and the FreeBSD Diary do), or on to your desktop, using applications such as KNewsTicker.

      @@ -514,7 +514,7 @@ Pandaemonium User Group -

      Pandaemonium, +

      Pandaemonium, the BSD Users Group of Western Australia, has been added to the Support page.

       @@ -529,7 +529,7 @@       - + 7 @@ -540,8 +540,8 @@ FreeBSD Handbook task list now available

      A second edition of The FreeBSD - Handbook will be in production shortly. A - task list has been + Handbook will be in production shortly. A + task list has been published for anyone who wants to help contribute to the state of available printed documentation about FreeBSD.

      @@ -557,12 +557,12 @@ 16 - +

      New committer: Rob Braun

       - +

      New committer: Dave Zarzycki

      @@ -572,10 +572,10 @@

      New committer: Mike Barcroft

             - + 13 - +

      New committer: Chern Lee (Docs)

      @@ -601,8 +601,8 @@ Using FreeBSD with Solid State Media -

      John Kozubik has submitted - an article explaining +

      John Kozubik has submitted + an article explaining How to use FreeBSD with solid state media.

       @@ -639,7 +639,7 @@ (Ports)

             - + 13 @@ -647,7 +647,7 @@ FreeBSD Status Report Available

      Robert Watson has - compiled a + compiled a status report for the FreeBSD Project. These reports are scheduled to continue on a monthly basis.

       @@ -677,7 +677,7 @@ 1 - +

      New committer: Crist J. Clark (Networking, security)

      @@ -690,7 +690,7 @@ 24 - + ftp.FreeBSD.org back up @@ -705,7 +705,7 @@ 16 - +

      New committer: Jim Pirzyk

      @@ -714,11 +714,11 @@ 2 - + New FreeBSD 'zine issue out -

      The first May 2001 issue of the +

      The first May 2001 issue of the FreeBSD 'zine is now available. Starting this month, there will be two issues per month; one on the 1st, and one on the 15th.

      @@ -731,7 +731,7 @@ 27 - + SMP Alpha now works @@ -745,23 +745,23 @@ 25 - + -

      New committer: Takuya +

      New committer: Takuya SHIOZAKI (Internationalization)

       - + -

      New committer: Udo Erdelhoff +

      New committer: Udo Erdelhoff (Docs)

             18 - + -

      The +

      The Developer's Handbook is now available on the web site. This is an evolving resource for people wanting to develop software for @@ -774,11 +774,11 @@ 17 - + -

      Addison Wesley have allowed us to republish +

      Addison Wesley have allowed us to republish Chapter - 8 of the + 8 of the FreeBSD Corporate Networker's Guide. Chapter 8 provides an in-depth look at providing printing services to Windows, NT, and Novell @@ -788,9 +788,9 @@ 16 - + -

      Yet another new committer: +

      Yet another new committer: Jens Schweikhardt (Standards compliance)

       @@ -798,7 +798,7 @@ 12 - +

      The April issue of The FreeBSD 'zine is now available.

      @@ -807,7 +807,7 @@ 10 - +

      The Ports Collection now contains more than 5,000 individual entries!

      @@ -816,7 +816,7 @@ 5 - +

      New committer: George Reid (Sound support, ports)

      @@ -825,10 +825,10 @@ 4 - -

      Wind River to Acquire BSDi Software Assets. Please read the + +

      Wind River to Acquire BSDi Software Assets. Please read the Wind River - Press Release, the announcement from + Press Release, the announcement from Jordan K. Hubbard, and the FreeBSD Core Team statement.

       @@ -840,7 +840,7 @@ 25 - +

      New committer: Yar Tikhiy (Networking)

      @@ -849,7 +849,7 @@ 24 - +

      New committer: Eric Melville (System tools)

      @@ -858,7 +858,7 @@ 13 - +

      The March issue of The FreeBSD 'zine is now available.

      @@ -867,7 +867,7 @@ 9 - +

      New committer: Dima Dorfman (Docs)

      @@ -876,7 +876,7 @@ 7 - +

      New committer: Michael C. Wu (Internationalization, porting efforts)

      @@ -885,12 +885,12 @@ 6 - + -

      New committer: Thomas +

      New committer: Thomas M&ouml;stl (POSIX.1e extensions)

      -       - +       +

      New committer: Orion Hodson (Sound support)

      @@ -903,7 +903,7 @@ 20 - +

      New committer: Jesper Skriver

      @@ -912,7 +912,7 @@ 16 - +

      The February issue of The FreeBSD 'zine is now available.

      @@ -921,7 +921,7 @@ 5 - +

      New committer: Mike Heffner (Audit project)

      @@ -934,16 +934,16 @@ 24 - + -

      New committer: Jimmy +

      New committer: Jimmy Olgeni (Ports)

             23 - +

      New committer: Dirk Meyer (Ports)

      @@ -952,9 +952,9 @@ 20 - + -

      New committer: Ying-chieh +

      New committer: Ying-chieh Liao (Ports)

             diff --git a/en_US.ISO8859-1/htdocs/news/2002/news.xml b/en_US.ISO8859-1/htdocs/news/2002/news.xml index 93b66a9a58..00154dad44 100644 --- a/en_US.ISO8859-1/htdocs/news/2002/news.xml +++ b/en_US.ISO8859-1/htdocs/news/2002/news.xml @@ -105,7 +105,7 @@ (Documentation Project)

             - +       @@ -188,7 +188,7 @@ href="&base;/releases/index.html">Release Information page for more details. Also be sure to check the release errata - after installation for any late-breaking news and/or + after installation for any late-breaking news and/or issues with 4.7.

      @@ -200,7 +200,7 @@

      New committer: Eric Moore

      - + 4 @@ -210,7 +210,7 @@ href="mailto:mheinen@FreeBSD.org">Martin Heinen (Documentation Project)

      -       + 3 @@ -236,7 +236,7 @@ href="mailto:grehan@FreeBSD.org">Peter Grehan (PowerPC)

      -       + 2 @@ -314,7 +314,7 @@ href="&base;/releases/index.html">Release Information page for more details. Also be sure to check the release errata - after installation for any late-breaking news and/or + after installation for any late-breaking news and/or issues with 4.6.2.

      @@ -352,7 +352,7 @@ href="mailto:njl@FreeBSD.org">Nate Lawson

       - + 1 @@ -371,7 +371,7 @@ 7 - + 19 @@ -435,7 +435,7 @@ href="&base;/releases/index.html">Release Information page for more details. Also be sure to check the release errata - after installation for any late-breaking news and/or + after installation for any late-breaking news and/or issues with 4.6.

       @@ -661,7 +661,7 @@ 12 - + Updated release schedule now available @@ -676,7 +676,7 @@ 9 - + SMP sparc64 now works @@ -808,7 +808,7 @@ New tutorial: "The Euro symbol on FreeBSD"

      Aaron Kaplan has submitted a new article explaining how to - adjust your system configuration to use the new Euro symbol on FreeBSD.

       diff --git a/en_US.ISO8859-1/htdocs/news/2003/news.xml b/en_US.ISO8859-1/htdocs/news/2003/news.xml index cf488467bd..7715553b89 100644 --- a/en_US.ISO8859-1/htdocs/news/2003/news.xml +++ b/en_US.ISO8859-1/htdocs/news/2003/news.xml @@ -114,7 +114,7 @@ href="&base;/releases/index.html">Release Information page for more details. Also be sure to check the release errata - after installation for any late-breaking news and/or + after installation for any late-breaking news and/or issues with 4.9.

             @@ -224,7 +224,7 @@ native support for JDK 1.3.1 on FreeBSD

       - + 18 @@ -312,7 +312,7 @@ 21 - +

      New committer: Kirill Ponomarew (Ports)

      @@ -494,7 +494,7 @@ href="&base;/releases/index.html">Release Information page for more details. Also be sure to check the release errata - after installation for any late-breaking news and/or + after installation for any late-breaking news and/or issues with 4.8.

             @@ -576,7 +576,7 @@ href="&base;/releases/index.html">Release Information page for more details. Also be sure to check the release errata - after installation for any late-breaking news and/or + after installation for any late-breaking news and/or issues with 5.0.

             diff --git a/en_US.ISO8859-1/htdocs/news/2004/news.xml b/en_US.ISO8859-1/htdocs/news/2004/news.xml index f1811fc5d4..17577cd2d9 100644 --- a/en_US.ISO8859-1/htdocs/news/2004/news.xml +++ b/en_US.ISO8859-1/htdocs/news/2004/news.xml @@ -38,7 +38,7 @@ has granted permission to the FreeBSD Gnome Team for use of the Firefox and Thunderbird names, - official icons, and permission to do + official icons, and permission to do officially branded builds.

      @@ -217,7 +217,7 @@ href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=219950+0+current/freebsd-current">here.

       - + 29 @@ -468,7 +468,7 @@ 30 -

      New committer: New committer: Jeremy Messenger (ports)

       @@ -477,7 +477,7 @@ 19 -

      New committer: New committer: Tony Ackerman (src)

       @@ -486,7 +486,7 @@ 17 -

      New committer: New committer: Marius Strobl (src)

       @@ -495,7 +495,7 @@ 5 -

      New committer: New committer: Daniel Hartmeier (src)

       @@ -586,7 +586,7 @@ 26 -

      New committer: New committer: Vinod Kashyap (src)

       @@ -620,7 +620,7 @@ 17 -

      New committer: New committer: Jim Rees (src)

       @@ -629,7 +629,7 @@ 15 -

      Core member resigned: Core member resigned: Greg Lehey

      @@ -637,7 +637,7 @@ 10 -

      New committer: New committer: Max Laier (src)

       @@ -646,13 +646,13 @@ 2 -

      New committer: New committer: Lukas Ertl (src)

       -

      New committer: New committer: Pawel Jakub Dawidek (src)

       @@ -678,7 +678,7 @@ 21 -

      New committer: New committer: Philip Paeps (src)

       diff --git a/en_US.ISO8859-1/htdocs/news/2005/news.xml b/en_US.ISO8859-1/htdocs/news/2005/news.xml index eb47a33352..99b48acd8c 100644 --- a/en_US.ISO8859-1/htdocs/news/2005/news.xml +++ b/en_US.ISO8859-1/htdocs/news/2005/news.xml @@ -291,7 +291,7 @@

      A new website has been launched. We hope you find the new design easier to navigate. The site was implemented - by Emily Boyd as part of + by Emily Boyd as part of Google's Summer of Code program. A copy of the old site for @@ -475,11 +475,11 @@ (ports)

       - + 18 -

      New committer: New committer: Bruno Ducrot (src)

       @@ -538,7 +538,7 @@ -

      New committer: New committer: Renato Botelho (ports)

       @@ -547,7 +547,7 @@ 6 -

      New committer: New committer: Jung-uk Kim (src)

       @@ -594,7 +594,7 @@ -

      New committer: New committer: Kip Macy (src)

       @@ -633,7 +633,7 @@ -

      New committer: New committer: Brad Davis (doc)

       diff --git a/en_US.ISO8859-1/htdocs/news/2006/news.xml b/en_US.ISO8859-1/htdocs/news/2006/news.xml index 234a043980..1fd42fefff 100644 --- a/en_US.ISO8859-1/htdocs/news/2006/news.xml +++ b/en_US.ISO8859-1/htdocs/news/2006/news.xml @@ -94,7 +94,7 @@ 5 -

      New committer: Nicola Vitale +

      New committer: Nicola Vitale (ports)

       @@ -132,7 +132,7 @@ 29 -

      New committer: David Thiel +

      New committer: David Thiel (ports)

       @@ -200,7 +200,7 @@ -

      New committer: Jeremy Chadwick +

      New committer: Jeremy Chadwick (ports)

             @@ -208,12 +208,12 @@ 7 -

      New committer: Babak Farrokhi +

      New committer: Babak Farrokhi (ports)

       -

      New committer: Frank J. Laszlo +

      New committer: Frank J. Laszlo (ports)

             @@ -603,7 +603,7 @@ href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2006">Summer of Code wiki is complete. A log file of the boot process can be found here.

      -       +       17 @@ -771,7 +771,7 @@ href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2006">Summer of Code wiki href="&base;/news/status/report-2006-01-2006-03.html">now available with 29 entries.

      - + Summer of Code @@ -820,7 +820,7 @@ href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2006">Summer of Code wiki FreeBSD Foundation press release.

      -       +       @@ -957,7 +957,7 @@ href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2006">Summer of Code wiki       - + 1 diff --git a/en_US.ISO8859-1/htdocs/news/2007/news.xml b/en_US.ISO8859-1/htdocs/news/2007/news.xml index 205530712e..327043e7e2 100644 --- a/en_US.ISO8859-1/htdocs/news/2007/news.xml +++ b/en_US.ISO8859-1/htdocs/news/2007/news.xml @@ -189,7 +189,7 @@ The FreeBSD Foundation auctions the first copy of the book "Absolute &os;, 2nd Edition" - +

      The &os; Foundation has started its Fall Fund-Raising Campaign with an auction of the first copy of the book "Absolute &os;, 2nd Edition" which was graciously @@ -215,7 +215,7 @@ New committer: <a href="mailto:lulf@FreeBSD.org">Ulf Lilleengen</a> (src). SoC2007 alumnus. - +

      Ulf Lilleengen is now a src/ committer. He participated in the Summer of Code program, where he worked on gvinum. In FreeBSD, Ulf will continue to work on gvinum, @@ -318,7 +318,7 @@ FreeBSD Foundation August 2007 newsletter -

      The FreeBSD Foundation has published their +

      The FreeBSD Foundation has published their August 2007 newsletter which summarizes their activities so far this year.

      @@ -485,7 +485,7 @@ (ports)

       - + 25 @@ -650,7 +650,7 @@ of Code wiki is also available with additional information.

      successful student from last year's Summer of Code program, has continued working with the FreeBSD Project and is now a full src/ committer.

      -       +       diff --git a/en_US.ISO8859-1/htdocs/news/2007/press.xml b/en_US.ISO8859-1/htdocs/news/2007/press.xml index b7a015a95b..806d911dda 100644 --- a/en_US.ISO8859-1/htdocs/news/2007/press.xml +++ b/en_US.ISO8859-1/htdocs/news/2007/press.xml @@ -24,7 +24,7 @@ http://www.netcraft.com/ 19 November 2007 Paul Mutton -

      FreeBSD using web hosting provider DataPipe was ranked the +

      FreeBSD using web hosting provider DataPipe was ranked the most reliable provider in October 2007 by Netcraft.

       @@ -438,7 +438,7 @@ 16 January 2007 Thom Holwerda

      A new release of FreeSBIE, a FreeBSD Live-CD, has been - released after two years of development.

      + released after two years of development.

      diff --git a/en_US.ISO8859-1/htdocs/news/2009/news.xml b/en_US.ISO8859-1/htdocs/news/2009/news.xml index ebb312ac8e..55401cc156 100644 --- a/en_US.ISO8859-1/htdocs/news/2009/news.xml +++ b/en_US.ISO8859-1/htdocs/news/2009/news.xml @@ -362,7 +362,7 @@ 3

      New bugmeister members: - Gavin Atkinson, + Gavin Atkinson, Volker Werth

      diff --git a/en_US.ISO8859-1/htdocs/news/2009/press.xml b/en_US.ISO8859-1/htdocs/news/2009/press.xml index 54cc3e1700..eb32aea1cb 100644 --- a/en_US.ISO8859-1/htdocs/news/2009/press.xml +++ b/en_US.ISO8859-1/htdocs/news/2009/press.xml @@ -137,7 +137,7 @@ 4 - + Great Bay Software Switches to BSD from Linux http://www.marketwire.com/press-release/Great-Bay-Software-975478.html @@ -149,7 +149,7 @@ has switched to &os; from Linux for all of its appliances including the Beacon Endpoint Profiler 3.0.

       - + First look at PC-BSD 7.1 http://distrowatch.com/weekly.php?issue=20090413#feature diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-2.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-2.sgml index cb3b1380d7..e9a2ada1da 100644 --- a/en_US.ISO8859-1/htdocs/news/press-rel-2.sgml +++ b/en_US.ISO8859-1/htdocs/news/press-rel-2.sgml @@ -21,8 +21,8 @@

      Complete XML Development System Integrated with FreeBSD

      -

      Concord, CA, April 29, 1999: Included with FreeBSD 3.1 is a -complete, integrated SGML/XML development system that installs with a +

      Concord, CA, April 29, 1999: Included with FreeBSD 3.1 is a +complete, integrated SGML/XML development system that installs with a simple, easy to use command sequence.

      FreeBSD's Ports system and multitasking architecture makes it easy for an @@ -56,7 +56,7 @@ http://www.FreeBSD.org/tutorials/primer/

      • Features of the Document Project SGML/XML System include:

        -
      • James Clark's Jade 1.2.1 and SP suite version 1.3.3, enabling +
      • James Clark's Jade 1.2.1 and SP suite version 1.3.3, enabling formatting and validation of SGML and XML documents.
      • A complete set of 19 ISO SGML character set entities
      • The DocBook (v2.4.1, v3.0, v3.1), HTML (all versions), and diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-3.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-3.sgml index 0991d77d63..9a15759bce 100644 --- a/en_US.ISO8859-1/htdocs/news/press-rel-3.sgml +++ b/en_US.ISO8859-1/htdocs/news/press-rel-3.sgml @@ -20,9 +20,9 @@

        BSD Community Welcomes Apple's New Open Source Operating System

        -

        Concord, CA, June 7, 1999: Today, at the start of the UNIX -development community's annual Usenix convention, operating system -influentials embraced Apple Computer's Darwin (www.apple.com/darwin) +

        Concord, CA, June 7, 1999: Today, at the start of the UNIX +development community's annual Usenix convention, operating system +influentials embraced Apple Computer's Darwin (www.apple.com/darwin) as a new member of the Berkeley Software Distribution (BSD) operating system family.

        diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-5.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-5.sgml index 6fb653ca1d..b1101bede4 100644 --- a/en_US.ISO8859-1/htdocs/news/press-rel-5.sgml +++ b/en_US.ISO8859-1/htdocs/news/press-rel-5.sgml @@ -128,7 +128,7 @@ The FreeBSD Project
        jkh@FreeBSD.org

        # # #

        - +

        BSD is a registered trademark of Berkeley Software Design, Inc. Other trademarks are property of their respective owners. BSD technologies were originally developed by the University of California, Berkeley and its diff --git a/en_US.ISO8859-1/htdocs/news/press-rel-6.sgml b/en_US.ISO8859-1/htdocs/news/press-rel-6.sgml index 9ed62f1959..d4512fc591 100644 --- a/en_US.ISO8859-1/htdocs/news/press-rel-6.sgml +++ b/en_US.ISO8859-1/htdocs/news/press-rel-6.sgml @@ -17,77 +17,77 @@

        The Daemon of the Opera: Opera Software Releases Version for FreeBSD

        -

        Oslo, Norway, October 31, 2002: Opera Software is proud to -announce the first golden release of its new port to the UNIX variance -FreeBSD. With FreeBSD joining the Opera family, Opera is now available on +

        Oslo, Norway, October 31, 2002: Opera Software is proud to +announce the first golden release of its new port to the UNIX variance +FreeBSD. With FreeBSD joining the Opera family, Opera is now available on eight different operating systems.

        -

        The BSD (Berkeley Software Distribution) operating system has its origins -at the University of California, Berkeley. It started out as a supplement to -UNIX, but over time it evolved into several operating systems. Of the -different BSD flavors available, the most widely distributed is FreeBSD, -popular among high-end users like system administrators who are looking for a +

        The BSD (Berkeley Software Distribution) operating system has its origins +at the University of California, Berkeley. It started out as a supplement to +UNIX, but over time it evolved into several operating systems. Of the +different BSD flavors available, the most widely distributed is FreeBSD, +popular among high-end users like system administrators who are looking for a fast, reliable operating system.

        -

        "Opera and FreeBSD´s users are alike in that they emphasize and -expect stability and reliability. The match between FreeBSD and Opera should -strike a cord with many enterprise customers," says Jon S. von -Tetzchner, CEO, Opera Software ASA. "On a personal level, I'm also happy -to welcome FreeBSD users into the Opera family. FreeBSD is strictly not only -an operating system, but also a community and a philosophy with values I know +

        "Opera and FreeBSD´s users are alike in that they emphasize and +expect stability and reliability. The match between FreeBSD and Opera should +strike a cord with many enterprise customers," says Jon S. von +Tetzchner, CEO, Opera Software ASA. "On a personal level, I'm also happy +to welcome FreeBSD users into the Opera family. FreeBSD is strictly not only +an operating system, but also a community and a philosophy with values I know resonate well with our own."

        -

        The FreeBSD community is enthusiastic to finally be able to surf with +

        The FreeBSD community is enthusiastic to finally be able to surf with Opera.

        -

        "With the release of Opera for FreeBSD, FreeBSD users who download -Opera for FreeBSD can browse the Web with one of the fastest browsers -available on the market," says Robert Watson, FreeBSD Core Team member. -"FreeBSD´s reputation as a reliable and fast desktop operating system is -becoming widely known, and we are glad to see that Opera Software is helping +

        "With the release of Opera for FreeBSD, FreeBSD users who download +Opera for FreeBSD can browse the Web with one of the fastest browsers +available on the market," says Robert Watson, FreeBSD Core Team member. +"FreeBSD´s reputation as a reliable and fast desktop operating system is +becoming widely known, and we are glad to see that Opera Software is helping us create a more complete desktop environment."

        -

        Opera 6.1 for FreeBSD can be downloaded from +

        Opera 6.1 for FreeBSD can be downloaded from www.opera.com.

        About Opera Software

        -

        Opera Software ASA is an industry leader in the development of Web -browsers for the desktop and embedded markets, partnering with companies -such as IBM, AMD, Symbian, Canal+ Technologies, Ericsson, Sharp and Lineo -(now a division of Embedix). The Opera browser has received international -recognition from end users and the industry press for being faster, -smaller and more standards-compliant than other browsers. Opera is -available on Windows, Mac, Linux, Solaris, FreeBSD, OS/2, Symbian OS and -QNX. Opera Software ASA is a privately held company headquartered in Oslo, -Norway. Learn more about Opera at +

        Opera Software ASA is an industry leader in the development of Web +browsers for the desktop and embedded markets, partnering with companies +such as IBM, AMD, Symbian, Canal+ Technologies, Ericsson, Sharp and Lineo +(now a division of Embedix). The Opera browser has received international +recognition from end users and the industry press for being faster, +smaller and more standards-compliant than other browsers. Opera is +available on Windows, Mac, Linux, Solaris, FreeBSD, OS/2, Symbian OS and +QNX. Opera Software ASA is a privately held company headquartered in Oslo, +Norway. Learn more about Opera at www.opera.com.

        About the Berkeley Software Distribution Operating System

        -

        Berkeley Software Distribution operating system technologies were -originally developed from 1979 to 1992 by the Computer Systems Research -Group (CSRG) at the University of California at Berkeley. Berkeley-derived -operating system and networking technologies are at the heart of most modern -Unix and Unix-like operating systems. Today, virtually every major Internet -infrastructure provider uses BSD operating systems. BSD operating system -technologies are used by leading mission- critical network computing -environments and are embedded in Internet appliance platforms that require +

        Berkeley Software Distribution operating system technologies were +originally developed from 1979 to 1992 by the Computer Systems Research +Group (CSRG) at the University of California at Berkeley. Berkeley-derived +operating system and networking technologies are at the heart of most modern +Unix and Unix-like operating systems. Today, virtually every major Internet +infrastructure provider uses BSD operating systems. BSD operating system +technologies are used by leading mission- critical network computing +environments and are embedded in Internet appliance platforms that require advanced Internet functionality, reliability and security.

        About the FreeBSD Project

        -

        FreeBSD is a popular open source operating system developed by the FreeBSD -Project and its worldwide team, consisting of more than 5,000 developers -funneling their work to 185 "committer" developers. It is available free of -charge from ftp.FreeBSD.org and also -distributed as a shrink-wrap software product through CompUSA, Fry's, Borders, -Ingram, FreeBSDmall.com and others. FreeBSD includes thousands of ported -applications, including office automation, groupware and multimedia -applications, and is widely used in companies all over the world as a web -server, file server, firewall and router. FreeBSD is distributed under the -Berkeley Software Distribution license, which means that it can be copied and -modified freely or commercially. For more information about the FreeBSD +

        FreeBSD is a popular open source operating system developed by the FreeBSD +Project and its worldwide team, consisting of more than 5,000 developers +funneling their work to 185 "committer" developers. It is available free of +charge from ftp.FreeBSD.org and also +distributed as a shrink-wrap software product through CompUSA, Fry's, Borders, +Ingram, FreeBSDmall.com and others. FreeBSD includes thousands of ported +applications, including office automation, groupware and multimedia +applications, and is widely used in companies all over the world as a web +server, file server, firewall and router. FreeBSD is distributed under the +Berkeley Software Distribution license, which means that it can be copied and +modified freely or commercially. For more information about the FreeBSD Project, visit www.FreeBSD.org.

        Press Contact

        diff --git a/en_US.ISO8859-1/htdocs/news/pressreleases.sgml b/en_US.ISO8859-1/htdocs/news/pressreleases.sgml index 8e10d60667..d53cfac9f7 100644 --- a/en_US.ISO8859-1/htdocs/news/pressreleases.sgml +++ b/en_US.ISO8859-1/htdocs/news/pressreleases.sgml @@ -73,14 +73,14 @@ BSD Community Welcomes Apple's New Open Source Operating System.
        April 29, 1999
        -Complete XML Development System Integrated +Complete XML Development System Integrated with FreeBSD.

        April 22, 1999: The Matrix
        -FreeBSD Used to Generate Spectacular Special +FreeBSD Used to Generate Spectacular Special Effects for the Warner Brothers film The Matrix.

        diff --git a/en_US.ISO8859-1/htdocs/news/sou1999.sgml b/en_US.ISO8859-1/htdocs/news/sou1999.sgml index 796028d21f..657b5151b6 100644 --- a/en_US.ISO8859-1/htdocs/news/sou1999.sgml +++ b/en_US.ISO8859-1/htdocs/news/sou1999.sgml @@ -28,7 +28,7 @@ next. Neither one of those is really me, basically, so perhaps I'll just cut to the chase and focus on the most pertinent lessons (and objectives) to come out of the year 1998 for me.

        - +

        1998 was, of course, the year that the Internet got bigger (no surprise), various "internetpraneurs" (gag) got richer and FreeBSD's user base, as measured by the ftp download stats grew at its usual @@ -60,7 +60,7 @@ are well past the point where we can do everything that needs to be done as a serious and "grown up" solution just on good will and volunteerism alone.

        - +

        With that in mind, sites like the FreeBSD Mall have been set up to try and market a wider variety of FreeBSD-related @@ -164,7 +164,7 @@ it represent as diverse a set of hard-core FreeBSD evangelist/developers as we knew how to find and we've continued to add people using the same criteria.

        - +

        In bringing someone into core, we don't look at whether they've been winning popularity contests lately or won the Programming Olympiad 3 times in a row, we ask ourselves: "Does this person bring a unique @@ -197,9 +197,9 @@ whether or not to bring in some new member(s) at this time. That discussion is ongoing and I'll do my best to keep everyone up to date on that as things progress.

        - +

        Release numbering:

        - +

        Other decisions on the horizon concern returning to our former practice of using "major" version numbers for branches and "minor" numbers for releases, the revision number field only being used to @@ -243,7 +243,7 @@ boot time. These are both powerful new mechanisms and, coupled with some new stuff which will be coming in 1999, should give us a far more dynamic and extensible system than we've ever had before.

        - +

        Not to be overlooked is also our new SCSI CAM system, giving us more robust behavior with large drive arrays and supporting more of the high-end SCSI controllers, or the support for multiple processors on @@ -301,7 +301,7 @@ Those looking for actual FreeBSD employees should send mail to jobs@FreeBSD.org and indicate how much money they're willing to pay, otherwise don't do it.

        - +

        I don't mean to come across so harshly here that people don't even bother asking us for help, I'm simply saying that those users who avail themselves of the various FreeBSD volunteer tech support @@ -330,7 +330,7 @@ older and hopefully a little wiser, needs to continue keeping a light but steady hand on the tiller, relying on our developers as usual to provide much of the actual motive force behind FreeBSD.

        - +

        Our users also need to become more involved and I'm hoping that 1999 will be the year when a lot more local user groups and other self-help type of organizations are formed. The Handbook and FAQ are documents @@ -371,7 +371,7 @@ just a few of the many things that can be done if you're truly interested in putting some energy into FreeBSD and ideas for what to do will be the least of your worries if you're truly motivated.

        - +

        Executive Summary: 1999, rah rah rah, let's do it! :)

        diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml index aa9bf80ecf..0275fd24c6 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml @@ -120,7 +120,7 @@ or perform the most simple of upgrades but many features are absent. In particular, the client is in its infancy and much work remains to be done. We need additional developers so please get - in touch with us at + in touch with us at updater@osd.bsdi.com if you are interested in spending some cycles on this.

        diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml index 7b52884b55..58451ec310 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml @@ -1082,7 +1082,7 @@ and appears to be holding up well. Prior to committing it, preliminary performance measurements were done merely to ensure that it is not significantly worse than the old allocator, even - with Giant still in place. Results were promising + with Giant still in place. Results were promising [http://people.FreeBSD.org/~bmilekic/code/mb_alloc/results.html] diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml index c8eb7f40e6..ce59884f0b 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml @@ -1255,7 +1255,7 @@ -

        Updates to things from last month: +

        Updates to things from last month:

        • The ast() fixes were committed last month.
          • @@ -1264,7 +1264,7 @@

        -

        New stuff since last month: +

        New stuff since last month:

        • sx locks now support upgrades and downgrades.
          • diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml index b679cc03ae..2e6b63766d 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml @@ -812,45 +812,45 @@ that were imported from NetBSD a long time ago and just sat in the tree.

          -

          M1 (Patch included) +

          M1 (Patch included)
          - Setup infrastructure + Setup infrastructure
          - Make rcorder compile + Make rcorder compile
          - Hook rc.subr into the distribution (and mergemaster) + Hook rc.subr into the distribution (and mergemaster)
          - Hook rcorder into the world + Hook rcorder into the world
          Add toggle in rc.conf to switch between rc_ng and current boot scripts

          -

          M2 +

          M2
          - Get FreeBSD to boot with the new boot scripts + Get FreeBSD to boot with the new boot scripts
          Rewrite the /etc/rc.d scripts to work with FreeBSD

          -

          M3 +

          M3
          Add some FreeBSD specific support into rc.subr

          -

          M4 +

          M4
          Add true dependency checking to the infrastructure so that - starting nfsd will start mountd and rpcbind + starting nfsd will start mountd and rpcbind
          - add support into rc.subr + add support into rc.subr
          Add dependencies into rc.d scripts

          diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml index c56e05adb7..f93286c19b 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml @@ -183,36 +183,36 @@

          On the code side, a number of libpam bugs have been fixed; a - new PAM module, + new PAM module, pam_self(8) , has been written; and preparations have been made for - the transition from + the transition from /etc/pam.conf - to + to /etc/pam.d .

          On the documentation side, new manual pages have been written - for + for pam_ssh(8) - , + , pam_get_item(3) - and + and pam_set_item(3) , and work has started on a longer article about PAM which is expected to be finished by the end of the year.

          A lot of work still remains to be done to integrate PAM more - tightly with the FreeBSD base system—particularly the + tightly with the FreeBSD base system—particularly the passwd(1) - , + , chpass(1) etc. utilities—and ports collection.

          @@ -858,13 +858,13 @@ Initialization and Services Control - <-- from http://groups.yahoo.com/group/FreeBSD-rc/ --> + <-- from http://groups.yahoo.com/group/FreeBSD-rc/ -->

          This group is for discussion about the startup scripts in FreeBSD, primarily the scripts in /etc/rc*. Primary focus will be on improvements and importation of NetBSD's excellent work on this topic.

          - <-- from Gordon Tetlow's ranting --> + <-- from Gordon Tetlow's ranting -->

          Due to personal commitments by the folks working on this project we have been unable to spend much time porting the rc.d infrastructure into the FreeBSD boot framework.

          diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml b/en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml index 3131517faa..77b4ec6789 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml @@ -479,7 +479,7 @@ It also hosts a mailing list for discussions of FreeBSD in Bulgarian, stable@FreeBSD-bg.org. For more information about the mailing - list, send an e-mail with "help" in the message body to + list, send an e-mail with "help" in the message body to majordomo@FreeBSD-bg.org.

          @@ -685,22 +685,22 @@ SMPng - + smp@FreeBSD.org - + smp@FreeBSD.org - + SMPng project website - +

          Alfred Perlstein committed file descriptor locking code which was definitely a good push towards trying to lock down diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml index 89b5413d24..c25432ec92 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml @@ -140,7 +140,7 @@ - + Zero copy patches and information. @@ -171,13 +171,13 @@ -

          I'm slowly making progress. The second engineering release is +

          I'm slowly making progress. The second engineering release is available for download at http://www.geocities.com/m_evmenkin/ngbt-fbsd-20020506.tar.gz

          This release includes support for H4 UART transport layer, Host Controller Interface (HCI), Link Layer Control and Adaptation - Protocol (L2CAP) and Bluetooth sockets layer. It also comes + Protocol (L2CAP) and Bluetooth sockets layer. It also comes with several user space utilities that can be used to configure and test Bluetooth devices.

          @@ -268,7 +268,7 @@ - + Introduction to NgAtm @@ -306,10 +306,10 @@

          The GNOME project has seen quite a few changes lately. For one, - the author of this update has recently been given "The Bit." + the author of this update has recently been given "The Bit." Joe Marcus Clarke now has CVS access, and is working primarily on the GNOME project. Joe has been closing a good deal of GNOME - PRs, as well as patching some of the existing GNOME 1.4 + PRs, as well as patching some of the existing GNOME 1.4 components.

          The GNOME 2 porting effort continues on. We have completed porting @@ -471,7 +471,7 @@

          KAME Project has been extended until March 2004, and we decided the project - roadmap for these two years. The first one year is for implementation, and the + roadmap for these two years. The first one year is for implementation, and the remaining year is for feedback of our results into other BSD projects (please refer to the above URL for further detail). Great change is lack of NAT-PT support due to a lack of human resource, although @@ -518,7 +518,7 @@ main web page approaches to the where the records will be dumped -- whether that is to a local disk or fed up to userland and then dealt with. After that, the goal will be to expand the number of events that - are being audited, while also working in some performance testing + are being audited, while also working in some performance testing procedures. I will be posting to trustedbsd-audit about the recent changes shortly.

          @@ -744,7 +744,7 @@ main web page - + Project Status Page. @@ -1111,9 +1111,9 @@ messages. -

          libradius now supports RADIUS vendor attribute extensions and - user-ppp is now capable of doing MS-CHAP authentication via a RADIUS - server. A new net/freeradius port has been created for support of +

          libradius now supports RADIUS vendor attribute extensions and + user-ppp is now capable of doing MS-CHAP authentication via a RADIUS + server. A new net/freeradius port has been created for support of MS-CHAP in a RADIUS server.

          MS-CHAPv2 support will be added soon.

          diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml index aa8da93612..c0eab75fe6 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml @@ -37,14 +37,14 @@ - TCP Hostcache + TCP Hostcache - Andre - Oppermann + Andre + Oppermann - oppermann@pipeline.ch + oppermann@pipeline.ch @@ -65,21 +65,21 @@ - IP Routing Table Replacement + IP Routing Table Replacement - Andre - Oppermann + Andre + Oppermann - oppermann@pipeline.ch + oppermann@pipeline.ch - Claudio - Jeker + Claudio + Jeker - jeker@n-r-g.com + jeker@n-r-g.com @@ -101,21 +101,21 @@ - TCP Metrics Measurement + TCP Metrics Measurement - Andre - Oppermann + Andre + Oppermann - oppermann@pipeline.ch + oppermann@pipeline.ch - Olivier - Mueller + Olivier + Mueller - omueller@8304.ch + omueller@8304.ch @@ -146,17 +146,17 @@ method.

          - Claudio - Jeker + Claudio + Jeker - jeker@n-r-g.com + jeker@n-r-g.com - Andre - Oppermann + Andre + Oppermann - oppermann@pipeline.ch + oppermann@pipeline.ch @@ -242,7 +242,7 @@ September.

          - libh + libh new development web page. First snapshots of the diskeditor in action @@ -250,17 +250,17 @@ September.

          Max has been busy cleaning up the user interface dark side, and has - come up with a plan to improve the build system (using an automated + come up with a plan to improve the build system (using an automated Makefile dependency generator); the UI design and the TCL glue magic - (using Swig). A development page has been created on usw4, publishing + (using Swig). A development page has been created on usw4, publishing a lot of information about the current project status, a Changelog, - screenshots, documentation, etc. A new listbox widget has been + screenshots, documentation, etc. A new listbox widget has been implemented, making diskeditor look nicer and more usable. The package system backend is being inspected and redesigned to conform to a standard that is itself being re-thought. Indeed, the old sysinstall2.txt text has - been SGML-ized and enhanced and now provides a good (although rough) overview + been SGML-ized and enhanced and now provides a good (although rough) overview of libh package system. This allowed the document to be enhanced with diagrams - of how different procedures work. We are therefore getting closer to a + of how different procedures work. We are therefore getting closer to a real pkgAPI specification document. The package management tools have been slightly enhanced and should be a bit more usable, and we started committing regression test suites in the tree, mostly to test and maintain pkg API @@ -334,7 +334,7 @@ additional work is planned on the OLDCARD system.

          - +

          A devd daemon, to replace pccardd and usbd, has been designed. A few minor bugs have been fixed in NEWCARD. NEWCARD is now the default in -current. There is an experimental pci/cardbus bus code @@ -386,7 +386,7 @@ non-root pci bridges.

          Things are going well with the FreeBSD GNOME Project. We have just finished porting the GNOME 2.0 Final development platform and desktop - to FreeBSD! We hope to be able to make GNOME 2.0 the default for + to FreeBSD! We hope to be able to make GNOME 2.0 the default for 5.0-DP2 and 4.7-RELEASE. In the meantime, we're working to port more GNOME 2.0 applications.

          @@ -436,7 +436,7 @@ non-root pci bridges.

        • Progress continues with the TCK compliance testing. The current status has the JDK down to 19 compiler failures and 183 runtime failures. As we edge closer to compliance - its hoped that example code will be released to allow the + its hoped that example code will be released to allow the community to pull together through the final few bugs.
        • A new patchset for JDK 1.3.1 is imminent. This patchset will include HotSpot for the first time.
          • @@ -467,8 +467,8 @@ non-root pci bridges.

           -

          I'm afraid KAME Project does not work actively with regard to FreeBSD in these two month, since - we are too busy with the demonstration of our IPv6 implementation at Networld+Interop 2002 Tokyo. +

          I'm afraid KAME Project does not work actively with regard to FreeBSD in these two month, since + we are too busy with the demonstration of our IPv6 implementation at Networld+Interop 2002 Tokyo. (Thanks to a great effort, the demonstration was quite successful)

          We are aware of netinet6-related bug reports regarding socket handling, fine-grain locking, ip6fw etc. @@ -698,9 +698,9 @@ includes porting this facility to the -current tree.

          The project took a major step at the beginning of July when Milestone-III was committed. Milestone-III allows a simple test program (available at /usr/src/tools/KSE/ksetest/) - to run multiple threads, using kernel support. It does not yet + to run multiple threads, using kernel support. It does not yet allow the ability to allow these threads to run on different CPUs - simultaneously. Milestone IV will be to allow this, however + simultaneously. Milestone IV will be to allow this, however Milestone-III should allow Dan to start (with any interested parties) to start prototyping the userland part of the system. Milestone-III is only currently usable on x86, and @@ -1074,7 +1074,7 @@ includes porting this facility to the -current tree.

          mb_alloc updates - + @@ -1424,7 +1424,7 @@ and it might take some time to resolve these issues.

          Improve support for sockets: provide a peerlabel maintained for - stream sockets (unix domain, tcp), entry points for accept, + stream sockets (unix domain, tcp), entry points for accept, bind, connect, listen. Improve support for IPv4 and IPv6 by labeling IP fragment reassembly queues, and providing entry points to instrument fragment matching, update, reassembly, etc. diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml index b0fd7ef4b3..d279b653a2 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml @@ -24,7 +24,7 @@ to: additional 5.0 developer preview snapshots, additional locking and threading improvements, and many cleanups on the new supported architectures. Firewire support has been imported into the main tree, and - substantial cleanup of the ACPI/legacy PCI code is also in the works. + substantial cleanup of the ACPI/legacy PCI code is also in the works. Also, expect the import of new IPsec hardware acceleration support in the near future.

          When new developer previews are posted, please give them a try! While we @@ -116,7 +116,7 @@ devices now appear as disc# instead of ds#. Some work is still needed on pppd to make it understand cloning though it should work as long as the devices are created beforehand.

          -

          On the API front, management of mandatory interfaces (i.e. lo0) +

          On the API front, management of mandatory interfaces (i.e. lo0) is handled by the generic cloning code so if_clone_destroy has the same API as NetBSD again and <if>_modevent doesn't need to create the necessary devices manually.

          @@ -549,7 +549,7 @@

          Work is in progress to MFC a number of bug fixes related to vm_map corruption into -stable. This work is probably too involved to make it into the 4.7 release but is expected to - be committed just after the freeze is lifted. The corruption + be committed just after the freeze is lifted. The corruption in question typically occurs in large-memory systems under heavy loads and typically panics or KPFs (kernel-page-fault's) the machine in a vm_map related function.

          @@ -724,7 +724,7 @@ KSE - + @@ -748,11 +748,11 @@ deischen@FreeBSD.org - + poor description - +

          David Xu and I have been working on cleaning up some of the work done in KSE-III and Jonathon and Dan have been working on the userland diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml index 1e50776510..6ac7f85553 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml @@ -375,7 +375,7 @@

          These last two months have seen quite a lot of GNOME activity. GNOME has started releasing development snapshots of the upcoming GNOME 2.2 desktop. FreeBSD porting has begun outside of the - main ports tree in the + main ports tree in the MarcusCom CVS repository. If you are interested in testing the new desktop, follow the instructions on the aforementioned cvsweb @@ -723,9 +723,9 @@ -

          The PowerPC port has been running diskless on NewWorld G3/G4 - machines for a while now. A GEOM module to support Apple Partition - Maps is being written. There should be an installable ISO image +

          The PowerPC port has been running diskless on NewWorld G3/G4 + machines for a while now. A GEOM module to support Apple Partition + Maps is being written. There should be an installable ISO image available in the near future.

           diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml index 4277a240c5..331369ec5a 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml @@ -18,7 +18,7 @@ work on other things too. IA64 took some major steps towards working on the Itanium2 platform, an effort was started to convert all drivers to use busdma and ban vtophys(), hardware - crypto support and DEVD hit the tree, NewReno was fixed and + crypto support and DEVD hit the tree, NewReno was fixed and effort began on locking down the network layer of the kernel. Also high performance, modular scheduler started taking shape and will be a welcome addition to the kernel soon.

          @@ -775,7 +775,7 @@ used to send out notifications to port maintainers when their port fails to build 5 times in a row. This feature is currently experimental, and further code changes will be needed to - stabilize it.

          + stabilize it.

           diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml b/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml index 8e5ef346d1..ba8aab7bd1 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml @@ -328,7 +328,7 @@

          We have the first disk device driver (aac) out from under Giant now, and in certain scenarios it gives improvements up to 20%. The device driver API was pruned to reflect that NO_GEOM - compatibility is unnecessary, this resulted in approx 1000 + compatibility is unnecessary, this resulted in approx 1000 lines less source code, the majority of which were removed from the device drivers. The new API for cdevsw is a lot simpler and hopefully less likely to confuse people. The ability to @@ -458,25 +458,25 @@ -

          FreeBSD 4.8-RELEASE will continue in the tradition of +

          FreeBSD 4.8-RELEASE will continue in the tradition of 5.0-RELEASE, and include GNOME 2 as the default GNOME desktop. This means that 4.8 will ship with GNOME 2.2.

          Following on the heels of the recent GNOME 2.2 release, GNOME 2.3 - snapshots are gearing up. The development schedule is + snapshots are gearing up. The development schedule is available from http://www.gnome.org/start/2.3/. Ports will be made available the same way they were for the 2.1 development releases. Stay tuned to freebsd-gnome@ for more details.

          -

          We are currently in another ports freeze in preparation for +

          We are currently in another ports freeze in preparation for 4.8-RELEASE. Following the freeze, a new bsd.gnome.mk will be committed that effectively removes the USE_GNOMENG macro. - This new version will add support for GNOME 2 as well as + This new version will add support for GNOME 2 as well as setup backward compatibility for ports that have not yet been converted to the new GNOME infrastructure. People - interested in testing this new Mk file, can check out - the ``ports'' module following the instructions at + interested in testing this new Mk file, can check out + the ``ports'' module following the instructions at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.

          @@ -552,11 +552,11 @@

          Most of the file system buffer cache has been reviewed and protected. - The vnode interlock was extended to cover some buffer flag fields so + The vnode interlock was extended to cover some buffer flag fields so that a separate interlock was not required. The global buffer queue data structures were locked and counters were converted to atomic ops. The BUF_*LOCK functions grew an interlock argument so that buffers - could be safely removed from the vnode clean and dirty lists. The + could be safely removed from the vnode clean and dirty lists. The lockmgr lock is now required for all access to buf fields. This was not strictly followed before because splbio provided the needed protection.

          @@ -664,12 +664,12 @@ and correctness of the BSD networking stack by adding support for new standards and standards track proposals while maintaining compliance with existing specifications. The upcoming 4.8 and 5.1 releases will - be the first ones using the new NewReno logic. Recently, we + be the first ones using the new NewReno logic. Recently, we implemented the Limited Transmit algorithm (RFC 3042) which benefits connections with small congestion windows, as happens, for example, on many short web connections. We also recently added support for larger sized starting congestion windows as described in RFC 3390. This helps - short TCP connections as well as those with large round-trip delays, + short TCP connections as well as those with large round-trip delays, such as those over satellite links.

           diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml index b2596aafab..e7c3db97e0 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml @@ -507,16 +507,16 @@ -

          The FreeBSD ports were updated to KDE 3.1.4, another bug- and - security-fixes release. With this update, the QT port was updated +

          The FreeBSD ports were updated to KDE 3.1.4, another bug- and + security-fixes release. With this update, the QT port was updated to version 3.2. Both will be included in FreeBSD 4.9. - Significant work was spent to fix KDE on FreeBSD-CURRENT after the - removal of the gcc -pthread Option. Automatic package builds from - KDE CVS continued to ensure and improve the quality of the upcoming + Significant work was spent to fix KDE on FreeBSD-CURRENT after the + removal of the gcc -pthread Option. Automatic package builds from + KDE CVS continued to ensure and improve the quality of the upcoming KDE 3.2 release.

          Future: Work is in progress to setup a new server for hosting the - KDE-FreeBSD Website, Repository and another KDE CVS mirror. With + KDE-FreeBSD Website, Repository and another KDE CVS mirror. With help from Marcel Moolenaar the project will try to make KDE compile and working on the Intel IA64. And last but not least efforts are being made to fix the currently broken kdesu program.

          @@ -616,7 +616,7 @@ problems have been reported over the last week. One appears to be a stuck interrupt, but all that code has been redone for SMP support.

          - +           @@ -855,16 +855,16 @@ -

          Support for several new crypto devices was added. The SafeNet 1141 is a +

          Support for several new crypto devices was added. The SafeNet 1141 is a medium performance part that is not yet available on retail products. The - Hifn 7955 and 7956 parts are starting to appear on retail products that - should be available by the end of the year. Both devices support AES + Hifn 7955 and 7956 parts are starting to appear on retail products that + should be available by the end of the year. Both devices support AES encryption. Support for public key operations for the SafeNet devices was recently done for OpenBSD and will be backported. Public key support for the Hifn parts is planned.

          -

          A paper about the performance work done on the cryptographic subsystem - was presented at the Usenix BSDCon 2003 conference and received the best +

          A paper about the performance work done on the cryptographic subsystem + was presented at the Usenix BSDCon 2003 conference and received the best paper award.

          NetBSD recently imported the cryptographic subsystem.

          @@ -914,7 +914,7 @@ -

          Numerous bugs have been fixed since the last status report (and of +

          Numerous bugs have been fixed since the last status report (and of course a few new ones added). Progress on improved security has been slowed by other work. But new features and fixes are coming in from other groups that are now sharing the code. In particular NetBSD diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml index 9e05550f39..4c9159c027 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml @@ -27,10 +27,10 @@

          Scott Long, Robert Watson

          - + libarchive, bsdtar - + @@ -40,11 +40,11 @@ kientzle@FreeBSD.org - + - +

          The libarchive library, which reads and writes tar and cpio archives, is about ready to commit to the tree. The bsdtar @@ -52,7 +52,7 @@ should soon be a worthwhile successor to our aging GNU tar. I plan a gradual transition during which "bsdtar" and "gtar" will coexist in the tree.

          - +

          Oddly enough, libarchive and bsdtar are the first fruits of a project to completely rewrite the pkg tools. I've started architecting a libpkg library for handling routine package @@ -60,26 +60,26 @@ than the current version.

           - + Publications Page Update - + Josef - + El-Rayes - + josef@daemon.li - + Updated Publications Page - +

          I did a xml/xslt conversion of the html files to make maintaining of the page more comfortable. I removed the cdsets, which might be @@ -91,28 +91,28 @@ links to books to add.

           - + DVB-ASI Support - + Vincent - + Jardin - + Vincent.Jardin@6wind.com - + Home page and source code Computer Modules - +

          DVB ASI stands for Digital Video Broadcast - Asynchronous Serial Interface. It is the standard defined to send and receive DVB stream @@ -120,10 +120,10 @@ (DVB-C). This standard was developed in Europe to transport 188-byte MPEG cells and 204-byte MPEG cells. However it can be used to carry IP over DVB too.

          - +

          The FreeBSD driver uses the newbus amd the bus-dma API. It means that it could be easily ported to all the BSD flavors (NetBSD, OpenBSD).

          - +

          It uses the same API than the Linux DVB ASI support from ComputerModules that is based on the following devices:

            @@ -134,35 +134,35 @@
          It means that software such as Videolan that support DVB-ASI broadcasting could be supported by this driver.

          - +

          Special thanks to Tom Thorsteinson from Computer Modules who helped 6WIND to port their driver. It is used by 6WIND in order to provide IPv4, IPv6, Ethernet and our network services over DVB.

          - +

          Copyright 2003-2004, 6WIND

           - + FreeBSD ports monitoring system - + Mark - + Linimon - + linimon_at_lonesome_dot_com - + FreeBSD ports monitoring system - +

          Enhancements continue to be made to the system. Several, including improvements to the PR classification algorithm, the @@ -177,7 +177,7 @@ of effort. (Some SQL performance was sacrificed to this goal, leading to some pages to load more slowly; this needs to be fixed.)

          - +

          The other work has been on an email back-end to allow the occasional sending of email to maintainers. Two functions are currently available: "remind maintainers of their ports that @@ -188,7 +188,7 @@ false positives. However, work remains to try to find out why a few allegedly broken ports only fail in certain environments (including the bento cluster).

          - +

          The next plan is to use the proposed DEPRECATED Makevar (see ports/59362) to create a new report to allow querying of "ports currently slated to be removed". This report could also be @@ -197,26 +197,26 @@ to be much more visible to the general FreeBSD user community.

           - + Compile FreeBSD with Intels C compiler (icc) - + Alexander - + Leidinger - + netchild@FreeBSD.org - + Some patches - +

          The FreeBSD kernel now builds and runs fine with icc v7 (only GENERIC and a custom kernel tested so far). A review on arch@ revealed no @@ -247,12 +247,12 @@ in the gcc and "-O2" in the icc case. No package is tested for correct run-time behavior so far.

          - +           - + Porting OpenBSD's pf - + @@ -269,13 +269,13 @@ yongari@kt-is.co.kr - + PF homepage PF FAQ - +

          Much work has been invested into getting release 2.00 stable. It provides the complete OpenBSD 3.4 function set, as well as fine @@ -292,39 +292,39 @@ OpenBSD-Current tracking again as soon as possible.

           - + Binary security updates for FreeBSD - + Colin - + Percival - + cperciva@daemonology.net - + - +

          Thanks to recent donations, I am now building binary security updates for FreeBSD {4.7, 4.8, 4.9, 5.0, 5.1, 5.2}-RELEASE. (Note that FreeBSD 4.7 and 5.0 are no longer officially supported; any advisories which are not reflected in the CVS tree will likewise not result in binary updates.)

          - +

          The current version (1.5) of FreeBSD Update will warn about locally modified files and will, by default, leave them untouched; if a "distribution branch", (i.e. crypto, nocrypto, krb4, or krb5) is specified, FreeBSD Update can be forced to "update" files which have been compiled locally.

          - +

          The only major issue remaining with FreeBSD Update is the single-point-of-failure of the update building process; I would like to resolve this in the future by having several @@ -333,108 +333,108 @@ wait until I've finished writing my DPhil thesis.

           - + SGI XFS port for FreeBSD - + Alexander - + Kabaev - + kan@FreeBSD.org Russell - + Cattelan - + cattelan@thebarn.com - +

          A project was started to revive a stalled effort to port SGI XFS - journaling filesystem to FreeBSD. The project is based on Linux + journaling filesystem to FreeBSD. The project is based on Linux development sources from SGI and is currently being kept in a private Perforce repository. The work is progressing slowly due - to lack of free time. At the moment we have XFS kernel module + to lack of free time. At the moment we have XFS kernel module which is capable of mounting XFS filesystems read-only, with a panic or two happening infrequently, that need to be isolated and fixed. Semi-working metadata updates with full transaction support are there too, but will probably have to be rewritten to minimize the amount of custom kernel changes required.

          - +

          We seek volunteers to help with userland part of the port. Namely, existing xfsprogs port needs to be cleaned up, incompletely ported utilities brought into a working shape. xfs_dump/xfs_restore and as much from xfstests suite as possible need to be ported too. We do not need testers for now, so please to not ask for module sources just yet.

          - +           - + Bluetooth stack for FreeBSD (Netgraph implementation) - + Maksim - + Yevmenkin - + m_evmenkin@yahoo.com - +

          Not much to report. Bluetooth code was integrated into the FreeBSD source tree. Bluetooth kernel modules appear to be stable. I have received few success stories from the users.

          - +

          During last few months the efforts were to make Bluetooth code more user friendly. Bluetooth Service Discovery Procotol daemon sdpd was reimplemented under BSD-style license and committed. The next step is to integrate existing Bluetooth utilities with SDP.

          - +

          Thanks to Matt Peterson <matt at peterson dot org> I now have Bluetooth keyboard and mouse for development. I'm currently working on Bluetooth HID profile implementation.

          - +

          Dave Sainty <dave at dtsp dot co dot nz> from NetBSD project offered his help in porting Bluetooth stack to NetBSD.

           - + Network interface naming changes - + Brooks - + Davis - + brooks@FreeBSD.org - +

          At the end of October, the if_name and if_unit members of struct ifnet were replaced with if_xname from NetBSD and if_dname and @@ -444,7 +444,7 @@ vendor branch, this change went quite well. A few ports needed minor changes, but otherwise nothing changed from the user perspective.

          - +

          The purpose of this change was the lay the groundwork for support for network interface renaming and to allow the implementation of more interesting pseudo interface cloning support. An example of @@ -456,7 +456,7 @@ device cloning is still in the planing stage.

           - + Kernel Tunables Documentation Project @@ -468,12 +468,12 @@ trhodes@FreeBSD.org - + The problem report which kicked this project in action - +

          FreeBSD has well over a few hundred tunables without documentation. This project aims at designing an @@ -488,104 +488,104 @@ work is requested to get in contact with me.

           - + jpman project - + Kazuo Horikawa - + horikawa@FreeBSD.org - + jpman project - +

          We have been updating existing Japanese translations of manual pages to meet the 5.2-RELEASE schedule. Also, 22 new translations were complete during this period.

           - + FreeBSD MIDI - + Mathew - + Kanner - + matk@FreeBSD.org - +

          This project aims to update the current MIDI implementation. We are currently looking at removing the current code sometime in February and importing the new version soon after. I'm currently working on a kernel/timidity bridge for those without external hardware.

          - +           - + The FreeBSD Russian Documentation Project - + Andrey - + Zakhvatov - + andy@FreeBSD.org - + The FreeBSD Project [Russian] - +

          The FreeBSD Russian Documentation Project aims to provide FreeBSD Documentation translated to Russian. Already done: FAQ, Porters Handbook, WWW (partially synched with English version), some articles.

          - +

          We working at Handbook (and more docs) translation and synchronization with English versions and need more translators (or financial aid to continue our work. If you can help, please, contact us at ru-cvs-committers@FreeBSD.org.ua (or andy@FreeBSD.org).

           - + KSE - + Daniel - + Eischen - + deischen@FreeBSD.org - +

          The libkse library will shortly be renamed to libpthread and be made the default thread library. This includes making the @@ -596,26 +596,26 @@ with GDB 6.0 which marcel has imported into the perforce tree.

           - + Donations Team - + Michael - + Lucas - + donations@FreeBSD.org - + FreeBSD Donations Project - +

          2003 was quite successful for the Donations team. We shepherded over 200 items from donors into the hands of @@ -625,40 +625,40 @@ cluster we were able to replace 8 DEC Miata machines with 6 Alpha DS10s (21264). Every committer doing SMP work now has multi-processor testing hardware.

          - +

          We have smoothed out the tax deduction process with the FreeBSD Foundation, and can ship donated items directly to the recipients instead of tying up Foundation time handling shipping.

          - +

          Current team membership is: Michael Lucas, David O'Brien, and Tom Rhodes. Wilko Bulte has replaced Robert Watson as the Core Team representative.

           - + ACPI - + Nate - + Lawson - + njl@FreeBSD.org - + ACPI TODO ACPI-JP Mailing List - + - +

          The updated acpi_cpu driver was committed in November. Work is ongoing to finish support for _CST re-evaluation, which makes it @@ -669,20 +669,20 @@ now be done through rc.conf(5) settings for the /etc/power_profile script, which switches between performance/economy levels when the AC status changes.

          - +

          One huge task underway is the cpufreq project, a framework for detecting and controlling various frequency/voltage technologies (SpeedStep, LongRun, ACPI Performance states, etc.) The ACPI performance states driver is working and the framework is being implemented. It requires newbus attachments for CPUs so some ground work needs to go in before the driver can be committed.

          - +

          ACPI-CA was updated to 20031203 in early December and with a few patches is reasonably stable. An ACPI debugging how-to has been written and is being DocBooked by trhodes@. Ongoing work on fixing interrupt storms due to various ways of setting up the SCI is being done by jhb@.

          - +

          I'd like to welcome Philip Paeps (philip@) to the FreeBSD team. Philip has written an ACPI ASUS driver that will be committed soon and has been very helpful on the mailing lists. We've also had @@ -693,58 +693,58 @@ see the ACPI TODO and send us an email.

           - + kgi4BSD Status Report - + Nicholas - + Souchu - + nsouch@FreeBSD.org - + - +

          Most of the console blocks are in place with nice results (see screenshots on the site). Boot console and virtual terminals are working with 8bit rendering and perfect integration of true graphic drivers in the kernel.

          - +

          Now it is time to bring it to end user and a precompiled R5.2 GENERIC kernel is available for this (see the site news). In parallel, after providing a last tarball/patch for R5.2, everything will move to Perforce.

          - +

          As always, volunteers are welcome. The task is huge but very exciting.

           - + FreeBSD/powerpc on PPCBug-based embedded boards - + Rafal - + Jaworowski - + rafal.jaworowski@motorola.com - +

          The direct objective is to make FreeBSD/powerpc work on Motorola MCP750 and similar (single board computer that is compliant with @@ -757,7 +757,7 @@ (compact flash) support needs to be done one day. The loader is the only piece that relies onPPCBug system calls - once the kernel starts it doesn't need firmware support any longer.

          - +

          2. kernel: it is now divorced from OpenFirmware dependencies; most of the groundwork finished includes: nexus stuff is sorted out (resources management is ok except interrupts assignment); host to PCI bridge low @@ -766,45 +766,45 @@ (Raven MPIC part is done, but the board has the second PIC, 8259-compatible that needs to be set up, but here the existing code from x86 arch will be adopted).

          - +

          Once the IRQ management is cleared out, most of the devices on board would work straight away since they are pretty standard chips with drivers already implemented in the tree (e.g. if_de).

          - +

          At the moment work is on hold (don't have physical access to the device) but will resume when I'm back home (late Feb).

          - +           - + TrustedBSD Mandatory Access Control (MAC) - + Robert - + Watson - + rwatson@FreeBSD.org - + TrustedBSD Discussion Mailing List - + trustedbsd-discuss@TrustedBSD.org - + TrustedBSD MAC page - +

          The TrustedBSD Mandatory Access Control (MAC) Framework permits the FreeBSD kernel and userspace access control @@ -815,20 +815,20 @@ control policy modules. Sample modules include Biba, MLS, and Type Enforcement, as well as a variety of system hardening policies.

          - +

          TrustedBSD MAC development branch in Perforce integrated to 5.2-RELEASE.

          - +

          The TrustedBSD MAC Framework now enforces protections on System V IPC objects and methods. Shared memory, semaphores, and message queues are labeled, and most operations are controlled. The Biba, MLS, Test, and Stub policies have been updated for System V IPC. (Not yet merged)

          - +

          The TrustedBSD MAC Framework now enforces protections on POSIX semaphore objects and methods. The Biba, MLS, Test, and Stub policies have been updated. (Not yet merged)

          - +

          The TrustedBSD MAC Framework's central kernel implementation previously existed in one large file, src/sys/kern/kern_mac.c. It is now broken out into a series of by-service files in @@ -837,7 +837,7 @@ across the different parts of the framework. System calls and registration still occur in kern_mac.c. This permits more easy maintenance of locally added object types. (Merged)

          - +

          Break out mac_policy_list into two different lists, one to hold "static" policy modules -- ones loaded prior to kernel initialization, and that may not be loaded, and one for @@ -845,24 +845,24 @@ boot, or may be unloaded. Perform less synchronization when using static modules only, reducing overhead for entering the framework when not using dynamic modules. (Merged)

          - +

          Introduced a kernel option, MAC_STATIC, which permits only statically registered policy modules to be loaded at boot or compiled into the kernel. When running with MAC_STATIC, no internal synchronization is required in the MAC Framework, lowering the cost of MAC Framework entry points. (Not yet merged)

          - +

          Make mac.h userland API definition C++-happy. (Merged)

          - +

          Created mac_support.4, a declaration of what kernel and userspace features are (and aren't) supported with MAC. (Not yet merged)

          - +

          Stale SEBSD module deleted from MAC branch; SEBSD module will solely be developed in the SEBSD branch from now on. See the TrustedBSD SEBSD report for more detail.

          - +

          Use only pointers to 'struct label' in various kernel objects outside the MAC Framework, and use a zone allocator to allocate label storage. This permits label structures to have their @@ -873,7 +873,7 @@ outside of the Framework, such as in execve(). Include files outside of the Framework are substantially simplified and now frequently no longer require _label.h. (Merged)

          - +

          Giant pushed down into the MAC Framework in a number of MAC related system calls, as it is not required for almost all of the MAC Framework. The exceptions are areas where the @@ -883,16 +883,16 @@ in quite a bit past label internalization/externalization/ storage allocation/deallocation. This substantially simplifies file descriptor-based MAC label system calls. (Merged)

          - +

          Remove unneeded mpo_destroy methods for Biba, LOMAC, and MLS since they cannot be unloaded. (Merged)

          - +

          Biba and MLS now use UMA zones for label allocation, which improves storage efficiency and enhances performance. (Merged)

          - +

          Bug fix for mac_prepare_type() to better support arbitrary object label definitions in /etc/mac.conf. (Merged)

          - +

          Labels added to 'struct inpcb', which represents TCP and UDP connections at the network layer. These labels cache socket labels at the application layer so that the labels may be @@ -900,10 +900,10 @@ is changed on the socket, it is pushed down to the network layer through additional entry points. Biba, MLS policies updated to reflect this change. (Merged)

          - +

          SO_PEERLABEL socket option fixed so that peer socket labels may be retrieved. (Merged)

          - +

          mac_get_fd() learns to retrieve local socket labels, providing a simpler API than SO_LABEL with getsockopt(). mac_set_fd() learns about local socket labels, providing a simpler API than @@ -911,60 +911,60 @@ embedding a struct label in the socket option arguments, instead using the copyin/copyout routine for labels used for other object types. (Merged)

          - +

          Some function names simplified relating to socket options. (Merged)

          - +

          Library call mac_get_peer() implemented in terms of getsockopt() with SO_PEERLABEL to improve API/ABI for networked applications that speak MAC. (Merged)

          - +

          mac_create_cred() renamed to mac_cred_copy(), similar to other label copying methods, allowing policies to implement all the label copying method with a single function, if desired. This also provides a better semantic match for the crdup() behavior. (Merged)

          - +

          Support "id -M", similar to Trusted IRIX. (Not yet merged)

          - +

          TCP now uses the inpcb label when responding in timed wait, avoiding reaching up to the socket layer for label information in otherwise network-centric code.

          - +

          Numerous bug fixes, including assertion fixes in the MAC test policy relating to execution and relabeling. (Merged)

           - + TrustedBSD Access Control Lists (ACLs) - + Robert - + Watson - + rwatson@FreeBSD.org - + TrustedBSD Discussion Mailing List - + - + trustedbsd-discuss@TrustedBSD.org - + TrustedBSD ACLs page - +

          TrustedBSD Access Control Lists (ACLs) provide extended discretionary access control support for the UFS and UFS2 @@ -973,42 +973,42 @@ requirements. Most ACL-related work is complete, with remaining tasks associated with userspace integration, third party applications, and compatibility

          - +

          Prototyped Solaris/Linux semantics for combining ACLs and the umask: if an default ACL mask is defined, substitute that mask for the umask, permitting ACLs to override umasks. (Not merged)

           - + TrustedBSD "Security-Enhanced BSD" -- FLASK/TE Port - + Robert - + Watson - + rwatson@FreeBSD.org - + TrustedBSD Discussion Mailing List - + trustedbsd-discuss@TrustedBSD.org - + TrustedBSD SEBSD page - +

          TrustedBSD "Security-Enhanced BSD" (SEBSD) is a port of NSA's SELinux FLASK security architecture, Type Enforcement (TE) @@ -1022,13 +1022,13 @@ required; these changes are developed in the SEBSD development branch, then merged to the MAC branch as they mature, and then to the FreeBSD development tree.

          - +

          Unlike other MAC Framework policy modules, the SEBSD module falls under the GPL, as it is derived from NSA's implementation. However, the eventual goal is to support plugging SEBSD into a base FreeBSD install without any modifications to FreeBSD itself.

          - +

          TrustedBSD SEBSD development branch in Perforce integrated to 5.2-RELEASE. Other changes in the MAC branch, including restructuring of MAC Framework files also integrated, and a @@ -1040,25 +1040,25 @@ module can create pty's with the label of the process trying to access them. Improves compatibility with the SELinux sample policy. (Not yet merged)

          - +

          SEBSD now loads its initial policy in the boot loader rather than using a dummy policy until the root file system is mounted, and then loading it using VFS operations. This avoids initial labeling and access control conditions during the boot.

          - +

          security_load_policy() now passes a memory buffer and length to the kernel, permitting the policy reload mechanisms to be shared between the early boot load and late reloads. The kernel SEBSD code now no longer needs to perform direct file I/O relating to reading the policy. checkpolicy now mmap's the policy before making the system call.

          - +

          SEBSD now enforces protections on System V IPC objects and methods. Shared memory, semaphores, and message queues are labeled, and most operations are controlled. The sample policy has been updated.

          - +

          The TrustedBSD MAC Framework now controls mount, umount, and remount operations. A new MAC system call, mac_get_fs() can be used to query the mountpoint label. lmount() system call @@ -1066,64 +1066,64 @@ time. The SEBSD policy module has been updated to reflect this functionality, and sample TE policy has been updated. (Not yet merged)

          - +

          SEBSD now enforces protections on POSIX semaphores; the sample policy has been updated to demonstrate how to label and control sempahores. This includes sample rules for PostgreSQL.

          - +

          The SEBSD sample policy, policy syntax, and policy tools have been updated to the SELinux code drop from August. Bmake these pieces so we don't need gmake.

          - +

          Provide file ioctl() MAC Framework entry point and SEBSD implementation.

          - +

          A large number of sample policy tweaks and fixes. The policy has been updated to permit cron to operate properly. It has been updated for FreeBSD 5.2 changes, including dynamically linked root. Teach the sample policy about FreeBSD's sendmail wrapper.

          - +

          Adapt sysinstall and install process for SEBSD pieces. Teach sysinstall, newfs, et al, about multilabel file systems, install SEBSD sample policy pieces, build policy. Automatically load the SEBSD module on first boot after install.

          - +

          Allow "ls -Z" to print out labels without long format.

           - + TrustedBSD Audit - + Robert - + Watson - + rwatson@FreeBSD.org - + TrustedBSD Audit Discussion List - + trustedbsd-audit@TrustedBSD.org - + TrustedBSD Audit Page - + - + - +

          The TrustedBSD Project is producing an implementation of CAPP compliant Audit support for use with FreeBSD. Little progress was made on this implementation between October and December @@ -1133,74 +1133,74 @@ the next report; more information is available on the TrustedBSD audit discussion list. Perforce messages may be seen on the trustedbsd-cvs mailing list.

          - +           - + TrustedBSD Documentation - + Robert - + Watson - + rwatson@FreeBSD.org - + TrustedBSD Discussion Mailing List - + - + trustedbsd-discuss@TrustedBSD.org - + TrustedBSD Documentation Page - +

          The TrustedBSD Project is implementing many new features for the FreeBSD Project. It also provides documentation for users, administrators, and developers.

          - +

          mac_support.4 added -- documents TrustedBSD MAC Framework feature compatibility. See also the MAC Framework report.

          - +

          FreeBSD security architecture updated and corrections/additions made.

          - +

          A variety of documentation updates relating to API changes, including the socket-related API changes in libc/mac(3).

           - + FreeBSD/MIPS Status Report - + Juli - + Mallett - + jmallett@FreeBSD.org - + - +

          TLB support code and PMAP have come along nicely. GCC and related have been kept up to date with the main tree. An evaluation board @@ -1211,22 +1211,22 @@ there are still bugs even before that milestone.

           - + AGP 3.0 Support - + John - + Baldwin - + jhb@FreeBSD.org - +

          Simple support AGP 3.0 including support for AGP 8x mode was added. The support is simple in that it still assumes only one @@ -1234,30 +1234,30 @@ 8x with drm modules that support it.

           - + Network Subsystem Locking and Performance - + Sam - + Leffler - + sam@FreeBSD.org - + -

          The purpose of this project is to improve performance of the network +

          The purpose of this project is to improve performance of the network subsystem. A major part of this work is to complete the locking of the networking subsystem so that it no longer depends on the "Giant lock" for proper operation. Removing the use of Giant will improve performance and permit multiple instances of the network stack to operate concurrently on multiprocessor systems.

          - +

          Locking of the network subsystem is largely complete. Network drivers, middleware layers (e.g. ipfw, dummynet, bridge, etc.), the routing tables, IPv4, NFS, and sockets are locked and operating @@ -1268,34 +1268,34 @@ that are not locked). The code can be obtained now from the Perforce database. A variety of test and production systems have been running this code for several months without any obvious issues.

          - +

          Performance analysis and tuning is ongoing. Initial results indicate SMP performance is already better than 4.x systems but UP performance is still lagging (though improved over -current). The removal of Giant from the network subsystem has reduced contention on Giant and highlighted performance bottlenecks in other parts of the system.

          - +

          This work was supported by the FreeBSD Foundation.

           - + Wireless Networking Support - + Sam - + Leffler - + sam@FreeBSD.org - + -

          Work to merge the NetBSD and MADWIFI code bases is almost complete. +

          Work to merge the NetBSD and MADWIFI code bases is almost complete. This brings in new features and improves sharing which will enable future development. Support was added for 802.1x client authentication (using the open1x xsupplicant program) and for shared @@ -1305,9 +1305,9 @@ hardware multi-rate retry. Kismet now works with the device-independent radiotap capture format. All of this work is still in Perforce but should be committed to CVS soon.

          - +

          Work has begun on full 802.1x and WPA support.

          - +           diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml b/en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml index 0a8e30706c..11fdbaccad 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml @@ -27,7 +27,7 @@ Disk and device I/O - + @@ -37,7 +37,7 @@ phk@FreeBSD.org - +

          In the overall area of disk and device I/O, a significant milestone was reached with the implementation of proper @@ -81,7 +81,7 @@ Weekly cvs-src summaries - + @@ -95,7 +95,7 @@ Polish translations - +

          I have been producing weekly summaries of commits and the surrounding discussions as reported on the cvs-src mailing list. @@ -126,7 +126,7 @@ and bsdtar will both be available in the base system. Once bsdtar is in the tree, I hope to resume work on libpkg and my pkg_add rewrite.

          - +

          Note that bsdtar is not an exact replacement for gtar: it does some things better (reads/writes standard formats, archive ACLs and file flags, detects format and compression automatically), @@ -140,36 +140,36 @@ Network interface naming changes - + Brooks - + Davis - + brooks@FreeBSD.org - + - +

          The first actual feature related to the if_xname conversion was committed in early February. Network interfaces can now be renamed with "ifconfig <if> name <newname>".

          - +

          Work is slowly progressing on a new network interface cloning API - to enable interesting cloners like auto-configurating vlans. + to enable interesting cloners like auto-configurating vlans. This work is taking place in the perforce repository under: //depot/user/brooks/xname/...

           PowerPC Port - + @@ -179,14 +179,14 @@ grehan@FreeBSD.org - +

          After a slow time at the end of last year due to a disk crash, the project is moving along rapidly. The loader is fully functional with Forth support. Syscons has been integrated. New Powerbook models are supported. Work is starting on a G5 port.

          - +

          There's still lots to do, so as usual volunteers are most welcome.

          @@ -269,7 +269,7 @@ any not versrcreach recv fxp0

           - + Move ARP out of routing table @@ -326,7 +326,7 @@ progress.

           - + Testbed for testing and qualification of TCP performance @@ -353,7 +353,7 @@ FreeBSD ports monitoring system - + @@ -363,12 +363,12 @@ linimon_at_lonesome_dot_com - + FreeBSD ports monitoring system - +

          Thanks to the loan of a box by Will Andrews, the system has been moved into production. The previous installation @@ -466,20 +466,20 @@ Project URL - +

          Move to Perforce is done. I spent some time on building a common compilation tree with Linux: until now drivers were build in a FreeBSD makefile tree, not compatible with Linux.

          - +

          The next priorities are ANSI support and keymaps in the KGC Kernel Graphic Console system.

           - + FreeBSD/ia64 - + @@ -489,12 +489,12 @@ marcel@FreeBSD.org - + Home page. - +

          Work on the PMAP overhaul has been put into gear. A lot of issues will be addressed, including support for sparse physical memory @@ -508,7 +508,7 @@ FreeBSD Package Grid - + @@ -518,9 +518,9 @@ kris@FreeBSD.org - + - +

          Distributed package builds are currently done using a set of home-grown shell scripts for managing, scheduling and dispatching of package builds on the client machines. This has @@ -530,7 +530,7 @@ GridEngine (ports/sysutils/sge), as a client application of a "FreeBSD package grid". Some of the design goals for the new system are:

          - +
          • Better robustness against machine failure, and more efficient scheduling of build jobs
            • @@ -540,7 +540,7 @@
          • Ability for other committers to submit port build jobs to the system, for testing of changes, new ports, etc.
          - +           @@ -554,23 +554,23 @@ le@FreeBSD.org - + - +

          The "geomification" of vinum has made some progress. I now have all basic setups working (concatenated plexes, striped plexes, RAID5 plexes, and RAID1), but I still have to implement correct - error handling and status change handling.

          + error handling and status change handling.

          Still missing is a userland tool, so currently you still have to use "old-style" vinum to configure your setup.

           NanoBSD - + @@ -580,7 +580,7 @@ phk@FreeBSD.org - +

          NanoBSD, src/tools/tools/nanobsd, is a tool for stuffing FreeBSD onto small disk media (like CompactFlash) for embedded @@ -588,7 +588,7 @@ for software images and one for configuration files. Having two software partitions means that new software can be uploaded to the non-active partition while running off the active partition.

          -

          The first really public version has been committed and many +

          The first really public version has been committed and many suggestions and offers of patches have started pouring in.

           @@ -610,14 +610,14 @@ yongari@kt-is.co.kr - + PF homepage PF FAQ ALTQ - +

          The sources were imported from OpenBSD 3.4R and patched with diffs obtained from the port. Since March the 8th it is linked @@ -642,7 +642,7 @@ cognet@FreeBSD.org - +

          Development goes reasonably fast, right now it boots single user. It is still very simics-centric, and it deserves a huge cleanup @@ -671,7 +671,7 @@ cattelan@thebarn.com - +

          Not much has changed since last report was submitted. The read-only access XFS volumes is quite stable now. The work is @@ -683,7 +683,7 @@ Compile FreeBSD with Intels C compiler (icc) - + @@ -693,17 +693,17 @@ netchild@FreeBSD.org - + Some patches. - +

          If nothing bad happened, the icc patches got committed around the date of the deadline for submissions of this report. Please search the archives of -current and/or cvs-all for more information.

          - +

          The next steps in this project are to

          • fix the kernel to also run without problems when compiled @@ -719,7 +719,7 @@ Bluetooth stack for FreeBSD (Netgraph implementation) - + @@ -729,7 +729,7 @@ m_evmenkin@yahoo.com - +

            Not much to report. Bluetooth Service Discovery Procotol daemon sdpd was integrated with existing Bluetooth utilities. From now @@ -741,7 +741,7 @@ FreeBSD GNOME Project Report - + @@ -751,12 +751,12 @@ gnome@FreeBSD.org - + FreeBSD GNOME Project Site. - +

            It has been a year since our last status report, but we haven't slowed down. Since the last report, Alexander @@ -765,7 +765,7 @@ 2003, followed by 2.4.1 and 2.4.2. We are actively working on getting GNOME 2.6.0 out the door at the end of March. GNOME 2.6 Beta releases can be obtained via the project URL above.

            - +

            To help make GNOME 2.6.0 our best release to date, we have created a script to automate the upgrade from GNOME 2.4. We also have a new GNOME @@ -774,7 +774,7 @@ that builds and serves i386 packages for all supported FreeBSD releases. We plan on having the GNOME 2.6.0 packages available the moment 2.6.0 hits the ports tree.

            - +

            Included in the release of GNOME 2.6 is GTK+ 2.4, the next installment in the GTK+ 2 series. Because GTK+ 2 has become very stable over the past few years, the FreeBSD GNOME Team is @@ -787,7 +787,7 @@ Network Stack Locking - + @@ -796,7 +796,7 @@ sam@FreeBSD.org - + Robert @@ -805,10 +805,10 @@ rwatson@FreeBSD.org - + - +

            This project is aimed at converting the FreeBSD network stack from running under the single Giant kernel lock to permitting it to @@ -820,7 +820,7 @@ 5.2, it was possible to run low level network functions, as well as the IP filtering and forwarding plane, without the Giant lock, as well as "process to completion" in the interrupt handler.

            - +

            Work continues to improve the maturity and completeness of the locking (and performance) of the network stack for 5.3. The network stack locking development branch has been updated to the @@ -852,7 +852,7 @@ begun, IPX/SPX analysis begun, PPP timeouts converted to callouts, Netgraph analysis begun. Many of these changes have not yet been merged to the main FreeBSDtree, but this is a work in progress.

            - +

            In related work on Pipe IPC (not quite network stack locking), substantial time was invested in diagnosing an increase in the cost of pipe allocation since FreeBSD 4.x, as well as coalescing @@ -860,7 +860,7 @@ to slab allocation so as to amortize the cost of pipe initialization. Future work here will include caching the VM structures supporting pipe buffers.

            - +

            Recent contributors include Robert Watson, Sam Leffler, MaxLaier, Maurycy Pawlowski-Wieronski, Brooks Davis, and many others who are omitted here only by accident.

            diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml b/en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml index c08523bc5d..54990c2cb8 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml @@ -9,10 +9,10 @@ March-April 2004 - +
            Introduction - +

            2004 continues on with wonderful progress. Work continues on locking down the network stack, ACPI made more great strides, an ARM port appeared in the tree, and the FreeBSD 4.10 release cycle wrapped up. @@ -26,10 +26,10 @@

            Thanks,

            Scott Long

            - + OpenOffice.org porting status - + @@ -39,7 +39,7 @@ maho@FreeBSD.org - +

            After almost three years efforts for porting OpenOffice.org 1.0.x and 1.1.0 for FreeBSD by Martin Blapp (mbr@FreeBSD.org) and other @@ -47,65 +47,65 @@ tree. 1.1.1: stable version, 1.1.2: next stable, 2.0: developer and 1.0.3: legacy.

            - +

            Stable version 1.1.1 in /usr/ports/editors/openoffice-1.1/ builds/installs/works fine for 5.2.1-RELEASE. Packages for 5.2.1-RELEASE, 26 localized versions and 4.10-PRELEASE only English version, are available at http://oootranslation.services.openoffice.org/pub/OpenOffice.org/ooomisc/ (note: source of OOo 1.1.1.RC3 is identical OOo 1.1.1)

            - +

            Patches needed to build are currently 18 for 1.1.1, and 161 for 1.0.3 the number of patches are greatly reduced.

            - +

            OOo 1.1.2, the next stable version in /usr/ports/editors/openoffice-1.1-devel is also builds/installs/works fine for 5.2.1-RELEASE. We are planning to upgrade this port as soon as 1.1.2 will be released.

            - +

            Next major release, 2.0 (planned to be released at January 2005 according to http://development.openoffice.org/releases/OpenOffice_org_trunk.html), /usr/ports/editors/openoffice-2.0-devel, now compiles for 5.2.1-RELEASE but have big problem that prohibits to remove BROKEN.

            - +

            Legacy version, OOo 1.0.3: /usr/ports/editors/openoffice-1.0/ I'm not interested in this port. We hope someone else will maintain this.

            - +

            For builds, my main environment is 5.2.1-RELEASE, and I have no access to 4-series, so several build problems had been reported for 5-current and 4-stable, however, they now seems to be fixed. Please make sure your Java and/or kernel are up-to-date.

            - +

            For version 1.1.1, yet we have serious reproducible core dumps, this means OOo cannot pass the Quality Assurance protocol of OpenOffice.org (http://qa.openoffice.org), so we cannot release OOo as quality assured package. It seems to be FreeBSD's userland bug, since some reports show that there are no problem for 4-stable but we still searchingthe reason.

            - +

            Note that developers should sign JCA (Joint Copyright Assignment) before submitting patches via PR or e-mail, otherwise patches won't be integrated to OOo's source tree. We seriously need more developers, testers and builders.

             - + Network interface naming changes - + Brooks - + Davis - + brooks@FreeBSD.org - +

            An enhanced network interface cloning API has been created. It allows interfaces to support more complex names than the current @@ -118,7 +118,7 @@ under: //depot/user/brooks/xname/...

             - + FreeBSD Dutch Documentation Project @@ -130,11 +130,11 @@ remko@elvandar.org - + Status and download of the documentation (not yet complete) - +

            The FreeBSD Dutch Documentation Project is a ongoing project in translating the handbook and other documentation to the Dutch @@ -149,10 +149,10 @@ publishing.

             - + ACPI - + @@ -162,13 +162,13 @@ njl@FreeBSD.org - + ACPI TODO ACPI Mailing List - +

            Much of the ACPI project is waiting for architectural changes to be completed. For instance, the cpufreq driver requires newbus @@ -179,22 +179,22 @@ including PCI powerstate support and APIC support have been invaluable in improving ACPI on modern platforms. Thanks go to Warner Losh and John Baldwin for this work.

            - +

            Code which is mostly completed and will go in once the groundwork is finished includes the cpufreq framework, an ACPI floppy controller driver, and full support for dynamic Cx states.

            - +

            ACPI-CA was updated to 20040402 in early April. This has some GPE issues that persist in 20040427 that will hopefully be resolved by the date of publication.

            - +

            I'd like to welcome Mark Santcroos (marks@) to the FreeBSD team. He has helped in the past with debugging ACPI issues. If any developers are interested in assisting with ACPI, please see the ACPI TODO and send us an email.

             - + Verify source reachability option for ipfw2 @@ -216,7 +216,7 @@ links above.

             - + Convert ipfw2 to use PFIL_HOOKS mechanism @@ -245,7 +245,7 @@ that is work in progress too.

             - + Move ARP out of routing table @@ -280,7 +280,7 @@ implementation for comments on 25. April 2004 (see link).

             - + Automatic sizing of TCP send buffers @@ -309,7 +309,7 @@ ip_input/ip_output cleanups).

             - + libarchive/bsdtar @@ -321,11 +321,11 @@ kientzle@FreeBSD.org - + - +

            Both bsdtar and libarchive are now part of -CURRENT. A few minor problems have been reported and addressed, @@ -335,7 +335,7 @@ Those who would like to use bsdtar as the default system tar can define WITH_BSDTAR to make "tar" be an alias for "bsdtar."

            - +

            My current plan is to make bsdtar be the default in -CURRENT in about another month, probably after the 5-STABLE split, and remove gtar from -CURRENT sometime later. It's still open if and when @@ -343,25 +343,25 @@ potential problems if 5-STABLE and 6-CURRENT have different tar commands; on the other hand, switching could be disruptive for some users.

            - +             - + GEOM Gate - + Pawel Jakub - + Dawidek - + pjd@FreeBSD.org - +

            GEOM Gate class is now committed as well as ggatec(8), ggated(8) and ggatel(8) utilities. It makes distribution of disk devices @@ -370,7 +370,7 @@ level).

             - + Improved Multibyte/Wide Character Support @@ -411,10 +411,10 @@ on performance. Localedef needs to be finished.

             - + ATA project Status Report - + @@ -424,7 +424,7 @@ sos@FreeBSD.org - + There is finally support (except for RAID5) for the Promise SX4/SX4000 line of controllers. The support is rudimentary still, and doesn't @@ -439,10 +439,10 @@

            formats (Intel, AMI) is also in the works.

             - + Porting OpenBSD's packet filter - + @@ -466,14 +466,14 @@ yongari@kt-is.co.kr - + - +

            The two months after the import was done were actually rather quiet. We imported a couple of minor fixes from the OpenBSD stable branch. @@ -482,7 +482,7 @@ pflogd(8) and provide rc.d linkage for it. Tcpdump now understandsthe pflog(4) pseudo-NIC packet format and can be used to read the log-files.

            - +

            There has also been work behind the scenes to prepare an import of the OpenBSD 3.5 sources. The patches are quite stable already andwill be posted shortly. Altq is in the making as well and going alongquite @@ -491,21 +491,21 @@ thoroughly it needs more time.

             - + The FreeBSD Simplified Chinese Project - + Xin LI - + delphij@frontfree.net - + The FreeBSD Simplified Chinese Project (In Simplified Chinese) @@ -516,7 +516,7 @@ Translated Website Snapshot - +

            We have finished about 75% of the Handbook translation work. In the last two months we primarily worked on bringing the @@ -526,11 +526,11 @@ translation which has been done last year by several volunteers.

             - - + + Cronyx Tau-ISA driver - + @@ -540,18 +540,18 @@ rik@FreeBSD.org - + Cronyx WAN Adapters. - +

            ctau(4) driver for Cronyx Tau-ISA was added. Cronyx Tau-ISA is family of synchronous WAN adapters with various set of interfaces such as V.35, RS-232, RS-530(449), E1 (both framed and unframed). This is a second family of Cronyx adapters that is supported by FreeBSD now. The first one was Cronyx Sigma-ISA, cx(4).

            - +

            Cronyx Tau-PCI family will become a third one. The peculiarity of this driver that it contains private code. This code is distributed as obfuscated source code with usual open source license agreement.Since @@ -561,11 +561,11 @@ will become a real alternative to object form.

             - - + + Sync protocols (Netgraph and SPPP) - + @@ -575,7 +575,7 @@ rik@FreeBSD.org - +

            As part of my work on synchronous protocol stack a ng_sppp driver was added to the system. This driver allows to use sppp as a Netgraph @@ -589,7 +589,7 @@ contact me.

             - + FreeBSD threading support @@ -629,31 +629,31 @@ deischen@FreeBSD.org - + basic data on TLS basic threads page - +

            Threading developers have been active behind the scenes though not much has been visible. Real Life(TM) has been hard on us as a group however.

            Marcel and Davidxu have both (individually) - been looking at the support + been looking at the support for debugging threaded programs. David has a set of - patches that allow gdb to correctly handle KSE programs and + patches that allow gdb to correctly handle KSE programs and patches are being considered for libthr based processes. Marcel added a Thread ID to allow debugging code to unambiguously specify a thread to debug. He has also been looking at corefile support. Both sets of patches are preliminary.

            -

            Dan Eischen continues to support people migrating to +

            Dan Eischen continues to support people migrating to libpthreads and it seems to be going well.

            -

            Doug Rabson has done his usual miracle work and produced - a set of preliminary patches to implement TLS (Thread +

            Doug Rabson has done his usual miracle work and produced + a set of preliminary patches to implement TLS (Thread Local Storage) for the i386 platform.

            Julian Elischer is investigating some refactoring of the kernel support code.

            @@ -674,11 +674,11 @@ cperciva@daemonology.net - + - +

            Having recently passed its first birthday, FreeBSD Update is now being used on about 170 machines every day; on a typical @@ -687,11 +687,11 @@ updated on over 4200 machines.

             - - + + PCI Powerstates and Resource - + @@ -701,18 +701,18 @@ imp@FreeBSD.org - +

            Lazy allocation of pci resources has been merged into the main tree. These changes allow FreeBSD to run on computers where PnP OS is set to true. In addition, the saving and restoring of the resources across suspend/resume has helped some devices come back from suspend.

            - +

            Future work will focus on bus numbering.

             - + Book: The Design and Implementation of the FreeBSD Operating System @@ -749,7 +749,7 @@ in early August 2004. The ISBN is 0-201-70245-2.

             - + Status Report @@ -761,22 +761,22 @@ the_mip_rvl@myrealbox.com - + - +

            This patch if for if_wi current. It enables you to disable the ssid broadcasting and it also allows you to disable clients connecting with a blank ssid.

             - + SMPng Status Report - + @@ -785,16 +785,16 @@ jhb@FreeBSD.org - + smp@FreeBSD.org - + - +

            Several folks continue to work on the locking the network stack as noted elsewhere in this report. Outside of the network stack, @@ -803,7 +803,7 @@ calls as far as possible. Alan Cox (alc@) continues to lock the VM subsystem and push down Giant where appropriate. A few system calls and callouts were marked MP safe as well.

            - +

            A few changes were made to the interrupt thread infrastructure. Interrupt thread preemption was finally enabled on the Alpha architecture with the help of the recently added support to the @@ -812,10 +812,10 @@ as well as rudimentary interrupt storm protection.

             - + FreeBSD/arm - + @@ -825,7 +825,7 @@ cognet@FreeBSD.org - +

            FreeBSD/arm is now in the FreeBSD CVS tree. Dynamic libraries now work, and NO_CXX=true NO_RESCUE=true buildworld works too (with patches for @@ -833,10 +833,10 @@ should be on xscale support.

             - + CAM lockdown and threading - + @@ -846,7 +846,7 @@ scottl@FreeBSD.org - +

            Work has begun on locking down the CAM subsystem. The project is divided into several steps: @@ -860,22 +860,22 @@

          • Locking one or more SIMs and devising a way for non-locked drivers to function.
          - +

          While the immediate goal of this work is to lock CAM, it also points us in the direction of separating out the SCSI-specific knowledgefrom the core. This will allow other transports to be written, such as SAS, iSCSI, and ATA.

          - +

          Progress is being tracked in the FreeBSD Perforce server in the camlock branch. I will make public patches available once it has progressed far enough for reasonable testing. So far, the first two items are being worked on.

          - + Network Stack Locking - + @@ -885,13 +885,13 @@ rwatson@FreeBSD.org - + SMPng Web Page Robert's Network Stack Locking Page - +

          This project is aimed at converting the FreeBSD network stack from running under the single Giant kernel lock to permitting it to run @@ -903,12 +903,12 @@ run low level network functions, as well as the IP filtering and forwarding plane, without the Giant lock, as well as "process to completion" in the interrupt handler.

          - +

          Work continues to improve the maturity and completeness of the locking (and performance) of the network stack for 5.3. The network stack development branch has been updated to the latest CVS HEAD, as well as the following and more:

          - +
          • Review of socket flag and socket buffer flag locking; so_state broken out into multiple fields covered by different @@ -985,10 +985,10 @@ elements required continued refinement (especially socket locking).

            - + TrustedBSD Mandatory Access Control (MAC) - + @@ -997,7 +997,7 @@ rwatson@FreeBSD.org - + TrustedBSD Discussion List @@ -1005,11 +1005,11 @@ trustedbsd-discuss@TrustedBSD.org - + TrustedBSD Project - +

            The TrustedBSD Mandatory Access Control (MAC) Framework permits the FreeBSD kernel and userspace access control @@ -1020,35 +1020,35 @@ control policy modules. Sample modules include Biba, MLS, and Type Enforcement, as well as a variety of system hardening policies.

            - +

            The TrustedBSD MAC development branch in Perforce was integrated to the most recent 5-CURRENT.

            - +

            mdmfs(8) -l to create multi-label mdmfs file systems (merged).

            - +

            Diskless boot updated to support MAC.

            - +

            Re-arrangement of MAC Framework code to break out mac_net.c into mac_net.c, mac_inet.c, mac_socket.c (merged).

            - +

            libugidfw(3) grows bsde_add_rule(3) to automatically allocate rule numbers (merged). ugidfw(8) grows 'add' to use this (merged).

            - +

            pseudofs(4) no longer requires MAC localizations.

            - +

            BPF fine-grained locking now used to protect BPD descriptor labels instead of Giant (merged).

            - +

            Prefer inpcb's as the source of labels over sockets when - creating new mbufs throughout the network stack, reducing + creating new mbufs throughout the network stack, reducing socket locking issues for labels.

             - + TrustedBSD Security-Enhanced BSD (SEBSD) port - + @@ -1057,7 +1057,7 @@ rwatson@FreeBSD.org - + TrustedBSD Discussion List @@ -1065,13 +1065,13 @@ trustedbsd-discuss@TrustedBSD.org - + TrustedBSD Project - + - +

            TrustedBSD "Security-Enhanced BSD" (SEBSD) is a port of NSA's SELinux FLASK security architecture, Type Enforcement (TE) policy engine and language, and sample policy to FreeBSD using @@ -1084,26 +1084,26 @@ required; these changes are developed in the SEBSD development branch, then merged to the MAC branch as they mature, and then to the FreeBSD development tree.

            - +

            Unlike other MAC Framework policy modules, the SEBSD module falls under the GPL, as it is derived from NSA's implementation. However, the eventual goal is to support plugging SEBSD into a base FreeBSD install without any modifications to FreeBSD itself.

            - +

            Integrated to latest FreeBSD CVS and MAC branch.

            - +

            New FreeBSD code drop updated for capabilities in preference to superuser checks.

            - +

            Installation instructions now available!

            - +             - + TrustedBSD Audit - + @@ -1112,7 +1112,7 @@ rwatson@FreeBSD.org - + TrustedBSD Discussion List @@ -1120,37 +1120,37 @@ trustedbsd-discuss@TrustedBSD.org - + TrustedBSD Project - +

            The TrustedBSD Project is producing an implementation of CAPP compliant Audit support for use with FreeBSD based on the Apple Darwin implementation.

            - +

            Experimentally integrated the XNU audit implementation from Apple's Darwin 7.2 into Perforce.

            - +

            Adapted audit framework to compile into FreeBSD -- required modifying memory allocation and synchronization to use FreeBSD SMPng primitives instead of Mach primitives. Pushed down the Giant lock out of most of the audit code, various other FreeBSD adaptations such as suser() API changes, using BSD threads, td->td_ucred, etc.

            - +

            Adapted per-thread audit data to map to FreeBSD threads

            - +

            Cleaned up userspace/kernel API interactions, including udev_t/ dev_t inconsistencies between Darwin and FreeBSD.

            - +

            Use vn_fullpath() instead of vn_getpath(), which is a less complete solution we'll need to address in the future.

            - +

            Basic kernel framework now operates on FreeBSD; praudit tool written that can parse FreeBSD BSM and Solaris BSM.

            - +             diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml index 12f4525a51..104f2f3b8d 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml @@ -8,10 +8,10 @@ May-June 2004 - +
            Introduction - +

            This installment of the Bi-Monthly Status Report is a few days late, but I'm pleased to say that it is chocked full of over 30 articles. May and June were yet again busy months; the Netperf project passed @@ -37,10 +37,10 @@

            Thanks,

            Scott Long

            - + Network Stack Locking - + @@ -50,12 +50,12 @@ rwatson@FreeBSD.org - + FreeBSD SMPng Web Page Netperf Web Page - +

            This project is aimed at converting the FreeBSD network stack from running under the single Giant kernel lock to permitting it to @@ -69,7 +69,7 @@ "process to completion" in the interrupt handler. This permitted both inbound and outbound traffic to run in parallel across multiple interfaces and CPUs.

            - +

            Work continues to improve the maturity and completeness of the locking (and performance) of the network stack for 5.3. The network stack development branch has been updated to the latest CVS HEAD, @@ -77,7 +77,7 @@ changes have been merged to the FreeBSD CVS tree as of the writing of this report. Complete details and more minor changes are documented in the README file on the netperf web page.

            - +
            • Addition of hard-coded WITNESS lock orders for socket-related locks, route locks, interface locks, file descriptor locks, @@ -194,10 +194,10 @@
            - + FreeBSD/MIPS Status Report - + @@ -207,12 +207,12 @@ jmallett@FreeBSD.org - + mips64emul - +

            In the past two months, opportunities to perform a good chunk of work on FreeBSD/MIPS have arisen and significant issues with @@ -224,7 +224,7 @@ Due to toolchain issues in progress, current kernels are no longer bootable on real hardware.

            A 64-bit MIPS emulator has arisen giving the ability to test and - debug in an emulator, and much testing has taken place in it. + debug in an emulator, and much testing has taken place in it. It has been added to the FreeBSD ports tree, and the port will be actively tracking the main codebase as possible. In general, FreeBSD/MIPS kernels should run fine in it.

            @@ -233,21 +233,21 @@ boot to a mountroot prompt.

             - + PowerPC Port - + Peter Grehan - + grehan@FreeBSD.org - +

            The port has been moving along steadily. There have been reports of buildworld running natively. Works is almost complete @@ -255,7 +255,7 @@ future.

             - + IPFilter Upgraded to 3.4.35 @@ -274,10 +274,10 @@ (post 4.10) from version 3.4.31 to 3.4.35.

             - + Low-overhead performance monitoring for FreeBSD - + @@ -287,14 +287,14 @@ jkoshy@FreeBSD.org - + A best-in-class performance monitoring system for FreeBSD built over the hardware performance monitoring facilities of modern CPUs. - +

            The current design attempts to support both per-process and system-wide statistical profiling and per-process "virtual" @@ -303,31 +303,31 @@ handle MP better. Initial development is targeting the AMD Athlon CPUs, but the intent is to support all the CPUs that FreeBSD runs on.

            - +

            An early prototype is available under Perforce [under //depot/user/jkoshy/projects/pmc/].

             - + FreeBSD profile.sh - + Tobias - + Roth - + ports@fsck.ch - + - +

            FreeBSD profile.sh is an enhancement to the FreeBSD 5 rcng boot system, targeted at laptops. One can configure multiple network @@ -340,10 +340,10 @@ will happen automatically.

             - + Sync protocols (Netgraph and SPPP) - + @@ -353,11 +353,11 @@ rik@FreeBSD.org - + Current code, ideas, problems. - +

            Currently I work on two directions: if_spppfr.c and sppp locking (on behalf of netperf). At the moment of writing this sppp locking @@ -366,22 +366,22 @@ netperf code (Only that I was able to catch while world compilation. If you know some others let me know and I'll try to fix them too).

            - +

            Since sppp code is quite big and state machine is very complicated, it would be difficult to test all code paths. I will glad to get any help in testing all this stuff. More tester more probability to test all possible cases.

            - +

            Work on FRF.12 (ng_frf12) is frozen since of low interest and lack of time. Current state of stable code: support of FRF.12 End-to-End fragmentation. Support of FRF.12 Interface (UNI and NNI) fragmentation is not tested.

             - + Cronyx Adapters Drivers - + @@ -391,11 +391,11 @@ rik@FreeBSD.org - + Cronyx WAN Adapters. - +

            cp(4) driver for Cronyx Tau-PCI was added. Cronyx Tau-PCI is family of synchronous WAN adapters with various set of interfaces such as @@ -408,10 +408,10 @@ my other report for additional information).

             - + Network interface naming changes - + @@ -421,7 +421,7 @@ brooks@FreeBSD.org - +

            An enhanced network interface cloning API has been committed. It allows interfaces to support more complex names then the current @@ -432,10 +432,10 @@

            Work on userland support for this functionality is ongoing.

             - + SMPng Status Report - + @@ -448,11 +448,11 @@ smp@FreeBSD.org - + - +

            Not a lot happened on the SMPng front outside of the work on locking the network stack (which is a large amount of work). @@ -468,10 +468,10 @@ table sizes or the hash algorithm.

             - + i386 Interrupt Code & PCI Interrupt Routing - + @@ -481,7 +481,7 @@ jhb@FreeBSD.org - +

            Support for programming the polarity and trigger mode of interrupt sources at runtime was added. This includes a @@ -494,23 +494,23 @@ non-ACPI systems also force any ISA interrupts used to route PCI interrupts to use active-low polarity and level trigger.

            - +

            Support for suspend and resume on i386 was also slightly improved. Suspend and resume support was added to the ELCR, $PIR, and apic drivers.

            - +

            The ACPI PCI-PCI bridge driver was fixed to fall back to the PCI-PCI bridge swizzle method for routing interrupts when a routing table was not provided by the BIOS.

            - +

            Mixed mode can now be disabled or enabled at boot time via a loader tunable.

             - + KDE on FreeBSD - + @@ -520,16 +520,16 @@ lofi@FreeBSD.org - + - +

            The work on converting the build switches/OPTIONS currently present in the ports of the main KDE modules into separate ports in order to make packages available for the - software/features they provide is progressing. Porting of + software/features they provide is progressing. Porting of KOffice 1.3.2 are nearly completed. The Swedish FreeBSD snapshot server http://snapshots.se.freebsd.org, @@ -539,10 +539,10 @@ soon.

             - + Various GEOM classes and geom(8) utility - + @@ -552,7 +552,7 @@ pjd@FreeBSD.org - +

            I'm working on various GEOM classes. Some of them are already committed and ready for use (GATE, CONCAT, STRIPE, LABEL, NOP). The @@ -562,10 +562,10 @@ the tree.

             - + FreeBSD Handbook, 3rd Edition, Volume II: Administrator Guide - + @@ -575,11 +575,11 @@ murray@FreeBSD.org - + FreeBSD Handbook 3rd Edition Task List. - +

            The Third Edition of the FreeBSD Handbook has been split into two volumes. The first volume, the User Guide, has been @@ -593,10 +593,10 @@ output assumptions in the document need to be corrected.

             - + VuXML and portaudit - + @@ -606,13 +606,13 @@ trhodes@FreeBSD.org - + VuXML DTD and more information Rendered contents of FreeBSD VuXML Rendered version of portaudit.txt - +

            The portaudit utility is currently an add-on to FreeBSD designed to give administrators and users a heads up @@ -625,7 +625,7 @@ it find vulnerable software installed the administrator or user is notified during the daily run output of the periodic scripts.

            - +

            These utilities are considered to be of production quality and discussion is taking place over whether or not they should be included as part of the base system. All @@ -634,12 +634,12 @@ eik@ or myself.

             - + Bluetooth stack for FreeBSD (Netgraph implementation) - + @@ -649,7 +649,7 @@ m_evmenkin@yahoo.com - +

            Bluetooth code was marked as non-i386 specific. It is now possible to build it on all supported platforms. Please help with testing. @@ -657,7 +657,7 @@ I've been very busy with Real Life.

             - + FreeBSD Dutch Documentation Project @@ -679,15 +679,15 @@ translating the FreeBSD handbook {and others} to the dutch language. We are still on the look for translators and people that are willing to check the current html documentation. - If you are interested, contact me at the email address shown + If you are interested, contact me at the email address shown above. We currently are reading for some checkups and then insert the first documents into the documentation tree.

             - + FreeBSD Brazilian Documentation Project - + @@ -697,13 +697,13 @@ doc@fugspbr.org - + - +

            The FreeBSD Brazilian Documentation Project is an effort of the Brazilian FreeBSD Users Group (FUG-BR) to translate the @@ -718,10 +718,10 @@ welcome!

             - + Packet Filter - pf - + @@ -738,11 +738,11 @@ dhartmei@FreeBSD.org - + The pf homepage. - +

            We imported pf as of OpenBSD 3.5 stable on June, 17th which will be the base for 5-STABLE pf (according to the current schedule). The @@ -751,12 +751,12 @@ hot-pluggable devices and pseudo cloning devices, before they exist. The import of the ALTQ framework enabled us to finally provide the related pf functions as well.

            - +

            Before 5-STABLE we will import some bug fixes from OpenBSD-current, which have not been merged to their stable branch, as well as some FreeBSD specific features. The planned ALTQ API make-over will also affect pf.

            - +

            We are (desperately) looking for non-manpage documentation for FreeBSD pf and somebody to write it. Few things have changed so a port of the excellent "PF FAQ" on the OpenBSD homepage should @@ -767,10 +767,10 @@ since the pf module now plugs into GENERIC without modifications.

             - + ALTQ import - + @@ -780,14 +780,14 @@ mlaier@FreeBSD.org - + ALTQ homepage. ALTQ integration in FreeBSD project. ALTQ merged into pf. - +

            The ALTQ framework is part of KAME for more than 4 years and has been adopted by Net- and OpenBSD since more than 3 years. It @@ -795,20 +795,20 @@ limitations. OpenBSD developed a different way to interact with ALTQ using pf, which was adopted by KAME as the "default for everyday use".

            - +

            The Romanian FreeBSD Users Group has had a project to work towards integration of ALTQ into FreeBSD, which provided a very good starting point for the final import. The import only provides the "pf mode" configuration and classification API as the older ALTQ3 API does not suit to our SMP approach.

            - +

            A reworked configuration API (decoupled from pf) is in the making as are additional driver modifications. Both should be done before 5-STABLE is branched, although additional drivers can be imported during the lifetime of 5-STABLE as well.

             - + HP Network Scanjet 5 @@ -833,10 +833,10 @@ non Microsoft PC in the building. http://berklix.com/scanjet/

             - + EuroBSDCon 2004 registration now open - + @@ -846,11 +846,11 @@ hausen@punkt.de - + EuroBSDCon 2004 official website - +

            Registration for EuroBSDCon 2004 taking place in Karlsruhe, Germany, from Oct. 29th to 31st has just opened. An early bird discount will @@ -858,10 +858,10 @@ conference website for details.

             - + Buf Junta project - + @@ -871,7 +871,7 @@ phk@FreeBSD.org - +

            The buf-junta project is underway, I am trying to bisect the code such that we get a struct bufobj which is the handle and method @@ -880,10 +880,10 @@ which do not have an associated vnode. The work is ongoing.

             - + TTY subsystem realignment - + @@ -893,7 +893,7 @@ phk@FreeBSD.org - +

            An effort to get the tty subsystem out from under Giant has morphed into an more general effort to eliminate a lot of @@ -904,10 +904,10 @@ must be reached. The work is ongoing.

             - + kgi4BSD - + @@ -917,43 +917,43 @@ nsouch@FreeBSD.org - + Project URL - +

            KGI is going slowly but surely. The port of the KGI/Linux accel to FreeBSD is in progress. It's no more than a double buffering API for graphic command passing to the HW engine.

            - +

            Most of the work in the past months was about console management and more especially dual head console. Otherwise a new driver building tree is now ready to compile Linux and FreeBSD drivers in the same tree.

            - +

            Documentation about KGI design is in progress.

             - + FreeBSD ports monitoring system - + Mark Linimon - + linimon_at_lonesome_dot_com - + FreeBSD ports monitoring system - +

            The system continues to function well. The accuracy of the automatic classification algorithm has been improved by @@ -1004,7 +1004,7 @@

          - + Improved Multibyte/Wide Character Support @@ -1028,10 +1028,10 @@ and tr are two important ones still remaining).

           - + FreeBSD/arm - + @@ -1041,7 +1041,7 @@ cognet@FreeBSD.org - + Not much to report, Xscale support is in progress, and should boot at least single user really soon on an Intel IQ31244 diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml index d91fc0fbc7..4a4a3815f1 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml @@ -17,7 +17,7 @@ 6-CURRENT development branch started, and EuroBSDCon 2004 was a huge success, just to name a few events. This report is packed with an impressive 44 submissions, the most of any report ever!

          - +

          It's also my pleasure to welcome Max Laier and Tom Rhodes to the status report team. They kindly volunteered to help keep the reports on time and help improve their quality. Max in particular is responsible for @@ -659,7 +659,7 @@ personalized, such as X.Org 6.7, XFCE 4.2RC1, Firefox 1.0 and Thunderbird 0.9.2.

          -

          For a complete list of the included software, please consult: +

          For a complete list of the included software, please consult: http://www.freesbie.org/doc/1.1/FreeSBIE-1.1-i386.pkg_info.txt @@ -766,7 +766,7 @@ working on the GNOME 2.9 development branch with is slated to become 2.10 on March 9 of this year.

          -

          The +

          The GNOME Tinderbox @@ -775,7 +775,7 @@ of FreeBSD.

          Thanks to Michael Johnson, the FreeBSD GNOME team has recently - been given + been given permission to use the Firefox and Thunderbird names @@ -793,27 +793,27 @@ - Need help porting + Need help porting HAL - to FreeBSD (contact + to FreeBSD (contact marcus@FreeBSD.org ) - Need help porting + Need help porting libburn - to FreeBSD (contact + to FreeBSD (contact bland@FreeBSD.org ) - Anyone interested in reviving + Anyone interested in reviving Gnome Meeting - should contact + should contact kwm@FreeBSD.org @@ -978,7 +978,7 @@ a consequence it's no longer just a 'browse & edit', but you have to sign up and let someone who is already in the ACL group 'developers' add you to the group. So it is a 'developers-only' - resource now. The old wiki is found at + resource now. The old wiki is found at http://wiki2.daemon.li

          @@ -1011,7 +1011,7 @@

          The project was very quiet (but still alive!) and mostly - dedicated to testing by volunteers. New documentation at + dedicated to testing by volunteers. New documentation at http://wiki.daemon.li/moin.cgi/KGI @@ -1051,19 +1051,19 @@ -

          OpenOffice.org 2.0 status +

          OpenOffice.org 2.0 status

          - OpenOffice.org 1.1 status + OpenOffice.org 1.1 status - General + General
          • Invoking OpenOffice.org from command line has been changed. Now `.org' is mandatory. e.g. openoffice-1.1.4 -> @@ -1115,7 +1115,7 @@ symbol in obj_from_addr_end, unfortunately this seem to induce hard-to-solve errors. A great progress has been made kan, rtld now do not depend on _end. A fix was committed 2004/02/25 - 17:06:16, + 17:06:16, http://www.freebsd.org/cgi/cvsweb.cgi/src/libexec/rtld-elf/rtld.c.diff?r1=1.91&r2=1.92&f=h @@ -1124,7 +1124,7 @@
          • Benchmark test! Building OOo requires huge resources. We just would like to know the build timings, so that how your machine is - well tuned for demanding jobs. + well tuned for demanding jobs. http://porting.openoffice.org/freebsd/benchmark.html @@ -1132,18 +1132,18 @@ build fastest. Just 1h25m22.42s for second build of OOo 1.1.4, using ccache.
            • -
          • SDK tutorial is available at +
          • SDK tutorial is available at http://porting.openoffice.org/freebsd/sdk.html
          • Still implementation test and quality assurance have not yet been done. Even systematic documentations are not yet available - for FreeBSD. + for FreeBSD. http://porting.openoffice.org/freebsd/testing.html - and + and http://porting.openoffice.org/freebsd/QA.html @@ -1396,16 +1396,16 @@

            Additionally, several sweeps through the ports tree were made to bring more uniformity in variables used in the different ports and - their values, e.g. + their values, e.g. BROKEN - , + , IGNORE - , + , DEPRECATED - , + , USE_GCC , and others.

            @@ -1422,7 +1422,7 @@ and the Java framework. Further, there were some updates to the Porter's Handbook, but more sections are still in need of updates to include recent changes in practices. Also, during this time, - Bill Fenner was able to fix a bug in his + Bill Fenner was able to fix a bug in his distfile survey @@ -1440,7 +1440,7 @@

            Ports QA reminders -- portmgr team members are now sending out periodic email about problems in the Ports Collection. The current - set includes: + set includes:

            • a public list of all ports to be removed due to security problems, build failures, or general obsolescence, unless they @@ -1449,10 +1449,10 @@
            • private email to all maintainers of the affected ports (including ports dependent on the above)
              • -
            • private email to all maintainers of ports that are marked +
            • private email to all maintainers of ports that are marked BROKEN - and/or + and/or FORBIDDEN
              • @@ -1460,7 +1460,7 @@ PRs filed against their ports (to flag PRs that might never have been Cc:ed to them) -
            • public email about port commits that break building of +
            • public email about port commits that break building of INDEX
              • @@ -1484,7 +1484,7 @@ The next highest number of build errors are caused by code that does not build on our 64-bit architectures due to the - assumption that "all the world's a PC." + assumption that "all the world's a PC." Here is the entire list @@ -1495,7 +1495,7 @@ A lot of progress has been meed to crack down on ports that install files outside the approved directories and/or do not - de-install cleanly (see "Extra files not listed in PLIST" on + de-install cleanly (see "Extra files not listed in PLIST" on pointyhat ) and this will remain a focus area. @@ -1994,10 +1994,10 @@ structural improvements, assertions, and locking fixes; cleanup of the IPX/SPX code in preparation for locking; additional locking and locking assertions for the TCP implementation; bug fixes for - locking and memory allocation in raw IP; + locking and memory allocation in raw IP; netatalk cleanup and locking merged to FreeBSD CVS - ; + ; locking for many netgraph nodes merged to FreeBSD CVS ; SLIP structural improvements; experimental locking for netatalk @@ -2008,7 +2008,7 @@ optimizations to improve pipe allocation performance; Giant no longer required for fstat on sockets and pipes (merged); Giant no longer required for socket and pipe file descriptor closes - (merged); + (merged); IFF_NEEDSGIANT interface flag added to support compatibility operation for unlocked device drivers (merged) @@ -2018,16 +2018,16 @@

              August, 2004: UMA KTR tracing (merged); UDP broadcast receive locking optimizations (merged); TCP locking cleanup and documentation; IPv6 inpcb locking, cleanup, and structural - improvements; + improvements; IPv6 inpcb locking merged to FreeBSD CVS - ; KTR for systems calls added to i386; + ; KTR for systems calls added to i386; substantial optimizations of entropy harvesting synchronization (merged) ; callout(9) sampling converted to KTR (merged); inpcb socket option locking (merged); GIANT_REQUIRED removed from netatalk in - FreeBSD CVS; + FreeBSD CVS; merged ADAPTIVE_GIANT to FreeBSD CVS, resulting in substantial performance improvements in many kernel IPC-intensive benchmarks @@ -2035,11 +2035,11 @@ ; prepend room for link layer headers to the UDP header mbuf to avoid one allocation per UDP send (merged); a variety of UDP bug fixes (merged); additional network interfaces marked MPSAFE; UNIX - domain socket locking reformulated to protect so_pcb pointers; + domain socket locking reformulated to protect so_pcb pointers; MP_WATCHDOG, a facility to dedicate additional HTT logical CPUs as watchdog CPUs developed (merged) - ; annotation of UNIX domain socket locking merged to FreeBSD CVS; + ; annotation of UNIX domain socket locking merged to FreeBSD CVS; kqueue locking developed and merged by John-Mark Gurney ; task list for netinet6 locking created; conditional locking @@ -2047,7 +2047,7 @@ server locking bugfixes (merged); in6_prefix code removed from netinet6 by George Neville-Neil, lowering the work load for netinet6 (merged); unused random tick code in netinet6 removed - (merged); + (merged); ng_tty, IPX, KAME IPSEC now declare dependence on Giant using compile-time declaration NET_NEEDS_GIANT("component") permitting the kernel to detect unsafe components and automatically acquire @@ -2057,7 +2057,7 @@ disabled by default in the netperf development branch (merged).

              September, 2004: bugs fixed relating to Netgraph's use of the - kernel linker while not holding Giant (merged); + kernel linker while not holding Giant (merged); merged removal of Giant over the network stack by default to FreeBSD CVS @@ -2075,22 +2075,22 @@ entering the ioctls of non-MPSAFE network interfaces.

              November, 2004: cleanup of UDPv6 static global variables - (merged); + (merged); FreeBSD 5.3 released! First release of FreeBSD with an MPSAFE and Giant-free network stack as the default configuration! - ; additional TCP locking documentation and cleanup (merged); + ; additional TCP locking documentation and cleanup (merged); optimization to use file descriptor reference counts instead of socket reference counts for frequent operations results in substantial performance optimizations for high-volume send/receive (merged) ; an accept bug is fixed (merged) experimental network polling - locking introduced; + locking introduced; substantial measurement and optimization of mutex and locking primitives (merged) - ; + ; experimental modifications to UMA to use critical sections to protect per-CPU caches instead of mutexes yield substantial micro-benchmark benefits when combined with experimental critical @@ -2100,7 +2100,7 @@ micro-benchmarks benchmarks reveal IP forwarding latency in 5.x is measurably better than 4.x on UP when combined with optional network stack direct dispatch; several NFS server locking bugfixes - (merged); + (merged); development of new mbufqueue primitives and substantial experimentation with them permits development of amortized cost locking APIs for handoff between the network stack and network @@ -2120,7 +2120,7 @@ alllocks" added to DDB (merged); IPX locking bugfixes (merged); IPX/SPX __packed fixes (merged); IPX/SPX moved to queue(9) (merged); TCP locking fixes and annotations merged to FreeBSD CVS; - IPX/SPX globals and pcb locking (merged); + IPX/SPX globals and pcb locking (merged); IPX/SPX marked MPSAFE (merged) ; IP socket options locking merged to FreeBSD; SPPP locked by Roman diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml index 86e3a63a41..2b12d6d323 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml @@ -251,7 +251,7 @@ Refactoring the common RPM code into bsd.rpm.mk. Determining which up-to-date Linux distribution to use as the - next default Linux base. Important criteria: + next default Linux base. Important criteria:

              • RPM based (to be able to use the existing infrastructure)
                • @@ -475,7 +475,7 @@ Currently we have translated almost the entire handbook, and more to come. If you want to help out by review the Dutch documents, or you want to help translating the remainders of the handbook or - other documents, feel free to contact me at + other documents, feel free to contact me at remko@FreeBSD.org

                @@ -582,7 +582,7 @@

                Big thanks to all users who provided testing and reported bugs to Max and Gleb. Daniel Seuffert has donated hardware to Max for - this project. Gleb's work was sponsored by + this project. Gleb's work was sponsored by Rambler .

                @@ -718,10 +718,10 @@

                Several storage drivers have been taken out from under the Giant - mutex in the past few months. Thanks to sponsorship from + mutex in the past few months. Thanks to sponsorship from FreeBSD Systems, Inc - and + and ImproWare, AG, Switzerland , the LSI MegaRAID (AMR) and IBM/Adaptec ServeRAID (IPS) drivers @@ -1005,7 +1005,7 @@

              • The driver has a new firmware image bundled, the new features of which include Online Capacity Expansion and multi-lun support, among others. More details about 3ware's 9.2 release can be found - here: + here: http://www.3ware.com/download/Escalade9000Series/9.2/9.2_Release_Notes_Web.pdf @@ -1282,19 +1282,19 @@ started in early 2000 and now contains over 170,000 commits. FreshPorts is primarily concerned with port commits, but actually processes and records all commits to the FreeBSD source tree. Its - sister site, + sister site, FreshSource uses the same database as FreshPorts but has a wider reporting scope. In recent months, FreshPorts has been enhanced to process - and include + and include VuXML information. In addition, RESTRICTED and NO_CDROM have been added to list of things that FreshPorts keeps track of. For unmaintained - ports, we recently added this message: + ports, we recently added this message:

                - There is no maintainer for this port. + There is no maintainer for this port.
                Any concerns regarding this port should be directed to the @@ -1340,13 +1340,13 @@ -

                BSDCan made a strong debut in +

                BSDCan made a strong debut in 2004 - . The favorable reception gave us a strong incentive for + . The favorable reception gave us a strong incentive for 2005 - . We have been rewarded with a very interesting + . We have been rewarded with a very interesting program and a higher rate of registrations. Percentage-wise, we have more @@ -1418,7 +1418,7 @@ Further progress has been made in cracking down on ports that install files outside the approved directories and/or do not - deinstall cleanly (see "Extra files not listed in PLIST" on + deinstall cleanly (see "Extra files not listed in PLIST" on pointyhat ) and this will remain a focus area. We appreciate everyone who has @@ -1481,10 +1481,10 @@ -

                OpenBSD is about to release +

                OpenBSD is about to release version 3.7 - . There are + . There are patches available to catch up with the development done in OpenBSD 3.6 and @@ -1989,16 +1989,16 @@ 127 entries have been added in 2005 bringing the FreeBSD VuXML file up to a total of 422 entries.

                -

                In the past months both the +

                In the past months both the VuXML web site - and the + and the FreshPorts VuXML integration have been improved. The VuXML web site has had a face lift and, among other things, each package now has a separate web page which lists all documented vulnerabilities for the - particular package. + particular package. CVE information is now also included directly on the VuXML web @@ -2087,44 +2087,44 @@

                ipw - : driver for Intel PRO/Wireless 2100 adapters (MiniPCI). + : driver for Intel PRO/Wireless 2100 adapters (MiniPCI).
                iwi : driver for Intel PRO/Wireless 2200BG/2225BG/2915ABG adapters (PCI - or MiniPCI). + or MiniPCI).
                ral - : driver for Ralink RT2500 wireless adapters (PCI or CardBus). + : driver for Ralink RT2500 wireless adapters (PCI or CardBus).
                ural : driver for Ralink RT2500USB wireless USB 2.0 adapters.

                -

                The ipw and iwi drivers require firmwares to operate. +

                The ipw and iwi drivers require firmwares to operate.
                These firmwares can't be redistributed with the base system due to - license restrictions. + license restrictions.
                - See firmware licensing terms here: + See firmware licensing terms here: http://ipw2100.sourceforge.net/firmware.php?fid=4 - . + .

                Ports which include the firmware images as well as the firmware - loader are being worked on. + loader are being worked on.
                - A list of adapters supported by ral and ural can be found here: + A list of adapters supported by ral and ural can be found here: http://ralink.rapla.net/ .

                diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml index 2c8d5cb64b..64b36a2034 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml @@ -24,7 +24,7 @@ to redesigning the venerable www.FreeBSD.org website. We are quite pleased to be working with so many talented students, and eagerly await the results of their work. More information and status can be - found at the Wiki site at + found at the Wiki site at http://wiki.freebsd.org/moin.cgi/SummerOfCode2005 @@ -126,7 +126,7 @@ -

                The second annual +

                The second annual BSDCan conference was well presented, well attended, and everyone went @@ -240,7 +240,7 @@ I've noticed that FreshPorts is incorrectly reporting - vulnerabilities under a + vulnerabilities under a very specific situation @@ -719,7 +719,7 @@ -

                We are currently working on an updated implementation of +

                We are currently working on an updated implementation of Juan Navarro's transparent support for superpages in FreeBSD.

                @@ -772,7 +772,7 @@ supplicant and authenticator).

                A presentation on the forthcoming multi-bss support was given at - BSDCan 2005. The slides from the talk are available at + BSDCan 2005. The slides from the talk are available at http://www.freebsd.org/~sam/BSDCan2005.pdf. @@ -819,10 +819,10 @@ architecture. The built filesystem can now boot from almost every media, from DVD to compact flash or hard disk. Also on i386 it is now possible to include the BSD Installer on the livefs. We've received - reports that our toolkit is successfully used for the install CD of + reports that our toolkit is successfully used for the install CD of pfSense - and + and PC-BSD projects.

                @@ -894,7 +894,7 @@ writes data); sendtd, which sends finished requests to ggatec. The new ggate has been committed to 6.x.

                -

                The work was sponsored by +

                The work was sponsored by Wheel Sp. z o.o.

                @@ -1093,7 +1093,7 @@ functionality and stability to work as a drop-in replacement for IP6FW, we won't remove IP6FW.

                -

                In order to get the new code to that point we +

                In order to get the new code to that point we really need more testers with real world IPv6 deployment and interest in @@ -1295,7 +1295,7 @@ -

                The +

                The nsswitch / caching daemon project is being developed within the Google's Summer Of Code @@ -1312,10 +1312,10 @@ - Implement set of patches to make nsswitch support + Implement set of patches to make nsswitch support globus grid security files - , + , MAC and audit related configuration files databases. @@ -1604,7 +1604,7 @@ x11-toolkits/linux-gtk/Makefile into bsd.rpm.mk. Determining which up-to-date Linux distribution to use as the - next default Linux base. Important criteria: + next default Linux base. Important criteria:

                • RPM based (to be able to use the existing infrastructure)
                  • @@ -1768,10 +1768,10 @@
                • Test a simple policy configuration for vsftpd.
                  • -
                • Writing a HOWTO document +
                • Writing a HOWTO document Getting Started with SEBSD HOWTO - by deriving the existing + by deriving the existing Getting Started with SELinux HOWTO.
                  • @@ -1867,7 +1867,7 @@ 25).

                  The program committee is looking for tutorial and paper - submissions. For details, please see: The + submissions. For details, please see: The call for papers online.

                  diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml b/en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml index 5bfc496289..307fbf46f1 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml @@ -295,7 +295,7 @@ A great deal of progress has been made in cracking down on ports that install files outside the approved directories and/or do - not deinstall cleanly (see "Extra files not listed in PLIST" on + not deinstall cleanly (see "Extra files not listed in PLIST" on pointyhat ). These ports are now a small minority thanks to the dedicated @@ -341,7 +341,7 @@

                  The project met all the scheduled goals, and following are the - new features implemented in libalias: + new features implemented in libalias:

                  • integration with IPFW in kernel land
                    • @@ -388,14 +388,14 @@ website. For each of your Watch Lists, you will also have a news feed just for that watch list. Any commit to any port in your watch list will turn up on your newsfeed. This fantastic new feature is - available now for your RSS pleasure at + available now for your RSS pleasure at the BETA site . I've also been doing some work in the area of supporting multiple platforms and architectures. This will allow FreshPorts to correctly report that a port is broken, for example, on i386, but not the other platforms. This feature will take note of BROKEN, - FORBIDDEN, and IGNORE for the following architectures: + FORBIDDEN, and IGNORE for the following architectures:
                    • alpha
                      • @@ -409,7 +409,7 @@
                    And the following OSVERSIONS (subject to upgrade as new releases - come along): + come along):
                    • 492100
                      • @@ -420,7 +420,7 @@
                    • 700001
                    - Upcoming changes, in addition to the above, include: + Upcoming changes, in addition to the above, include:
                    1. NOT_FOR_ARCHS
                      2. @@ -467,7 +467,7 @@ filesystem for FreeBSD" SoC project.

                      The kernel interface for the comprehensive userspace filesystem - API provided by the ( + API provided by the ( Fuse project ) has been implemented for FreeBSD (6.x and 7.x), under the BSD @@ -475,13 +475,13 @@ porting the rich collection of Fuse based filesystems to FreeBSD.

                      -

                      Now it's ready for consumption by a broader audience. The +

                      Now it's ready for consumption by a broader audience. The sysutils/fusefs-kmod - , + , sysutils/fusefs-libs - , + , sysutils/fusefs-sshfs ports can be expected to be integrated into the FreeBSD ports tree @@ -1188,12 +1188,12 @@

                      The FreeBSD developers will hold a DevSummit on Nov 24 and 25, so several developers will be at the conference.

                      -

                      The program is available for +

                      The program is available for Saturday - and + and Sunday @@ -1236,7 +1236,7 @@

                      Since our last status report, we have added a new member to the - team: Jean-Yves Lefort (jylefort). We have even spiced up our + team: Jean-Yves Lefort (jylefort). We have even spiced up our contact page @@ -1248,11 +1248,11 @@ the ports slush in preparation for 6.0-RELEASE, the update has not been merged into the official ports tree. If people are eager to try out GNOME 2.12 while waiting for the ports tree to fully thaw, - we have + we have instructions - on our website. GNOME 2.12 will be the first FreeBSD GNOME release + on our website. GNOME 2.12 will be the first FreeBSD GNOME release not to include support for FreeBSD 4.X. While 4.X is still a very @@ -1266,7 +1266,7 @@

                      The FreeBSD GNOME Project is also committed to providing our users with a solid package experience. To that end, we have - extended our + extended our Tinderbox @@ -1277,23 +1277,23 @@ - FreeBSD needs a + FreeBSD needs a HAL port. HAL will be vital for both GNOME and KDE in providing FreeBSD users with a smooth, elegant desktop experience. Once GNOME 2.12 has been merged into the ports tree, work will begin on making HAL - on FreeBSD a reality. Contact + on FreeBSD a reality. Contact gnome@FreeBSD.org if you are interested in helping. We need help with project documentation. In particular, we - need help auditing the + need help auditing the FAQ to make sure the content is still relevant, and we are not missing - any key items. If you're interested, please contact + any key items. If you're interested, please contact gnome@FreeBSD.org . @@ -1787,7 +1787,7 @@

                    2. HOST-RESOURCES-MIB - ( + ( http://www.ietf.org/rfc/rfc2790.txt @@ -1797,7 +1797,7 @@
                    3. TCP-MIB with combined IPv4 & IPv6 support - ( + ( http://www.ietf.org/rfc/rfc4022.txt @@ -1809,7 +1809,7 @@
                    4. UDP-MIB with combined IPv4 & IPv6 support - ( + ( http://www.ietf.org/rfc/rfc4113.txt @@ -1927,7 +1927,7 @@

                      This work is not integrated into 6.0-RELEASE because of some lose ends (see 'sndctl' below).

                      -

                      You can help by looking at +

                      You can help by looking at sound related PR's in GNATS @@ -1965,7 +1965,7 @@ Close a lot of PR's. - Document the sound system in the + Document the sound system in the FreeBSD Architecture Handbook @@ -2027,7 +2027,7 @@ At this point, we really need help with documentation. Work has begun on creating man pages for the various Tinderbox commands, but we need help to churn them out at as faster rate. If you have - strong mdoc fu, and interested in helping us out, please contact + strong mdoc fu, and interested in helping us out, please contact marcus@marcuscom.com . diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml index c3e261a62b..bd614965fc 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml @@ -691,7 +691,7 @@ won't be included in the release anyway. Developers hope to enter the BETA state on February 1st, to release an -RC image around February 15th and the RELEASE around March 1st. We need more people - to test the images we provide. Torrents for them are available at + to test the images we provide. Torrents for them are available at torrent.freesbie.org .

                      @@ -723,7 +723,7 @@ -

                      The port of DragonFly's variant symlinks ( +

                      The port of DragonFly's variant symlinks ( project ideas @@ -768,26 +768,26 @@

                      We are well into the process of selecting the talks for BSDCan - 2006. Our new + 2006. Our new program committee has a hard selection task over the new few weeks. The deadline for - the + the Call For Papers has passed, but it's not too late to submit a talk. Please see the - above URL for details. After the success of the + above URL for details. After the success of the Work in Progress last year , we are going to do it again this year. If you are working on something you'd like to tell the world about, considering giving a - 5 minute talk at BSDCan. The + 5 minute talk at BSDCan. The registration prices for BSDCan 2006 - will be the same as they were for + will be the same as they were for 2005 . We will be again in the SITE building at University of Ottawa and @@ -832,7 +832,7 @@ considerably.

                      You can read all about the new hardware on the recently - introduced + introduced FreshPorts Blog . This blog will include technical discussions about ports and the @@ -893,13 +893,13 @@ help, please contact Siebrand or me so that we can divide the work amongst us.

                      -

                      Recent publications: +

                      Recent publications:
                      Recently the Printing and the Serial Communications chapters were added to the FreeBSD Dutch Handbook.

                      -

                      Recently started items: +

                      Recently started items:
                      We started with the translation of the PPP and SLIP chapter and the diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml index 74d7ce8226..44f8034a5d 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml @@ -13,7 +13,7 @@ Introduction

                      The highlights of this quarters report certainly include the - availability of native Java binaries thanks to the + availability of native Java binaries thanks to the FreeBSD Foundation , as well as progress has been made with Xen support and Sun's @@ -21,17 +21,17 @@ TrustedBSD audit support has been imported into FreeBSD 7-CURRENT. All in all, a very exiting start to 2006.

                      -

                      In just under a month the developers will be gathering at +

                      In just under a month the developers will be gathering at BSDCan 2006 for, FreeBSD Dev Summit, a two day meeting of FreeBSD developers. - Once again the + Once again the BSDCan schedule is filled with many interesting talks.

                      We hope you enjoy reading and look forward to hear from you for - the next round. Consult the list of + the next round. Consult the list of projects and ideas @@ -208,13 +208,13 @@ -

                      The +

                      The schedule for BSDCan 2006 demonstrates just how strong and popular BSDCan has become in a very short time. Three concurrent streams of talks make sure that there is something for everyone. We provide high quality - talks at very affordable + talks at very affordable prices .

                      @@ -311,7 +311,7 @@ We need help getting back to our modern low of 500 PRs. - We have over 4,000 unmaintained ports (see, for instance, + We have over 4,000 unmaintained ports (see, for instance, the list on portsmon @@ -396,7 +396,7 @@ not show any glaring issues.

                      Moving on to making IPv6 work in FAST_IPSEC including being able - to run the kernel with the following variations: + to run the kernel with the following variations:

                      • FAST_IPSEC in v4 only
                        • @@ -455,7 +455,7 @@

                        The project is alive and plans to release an ISO image of FreeSBIE 2.0 based on FreeBSD 6.1-RELEASE few day after the same has been release. FreeSBIE 2.0 will be available for i386 and amd64 - archs. Tests images can be download via BitTorrent from + archs. Tests images can be download via BitTorrent from torrent.freesbie.org .

                        @@ -636,7 +636,7 @@

                        The FreeBSD Foundation released official certified JDK and JRE 1.5 binaries for the official FreeBSD 5.4 and FreeBSD 6.0 releases - on the i386 platform. + on the i386 platform.
                        We were able to accomplish this by hiring a contractor to run the @@ -1022,7 +1022,7 @@ Protocol which supersedes STP. RSTP has a much faster link failover time of around one second compared to 30-60 seconds for STP, this is very important on modern networks. Some progress has been made - but a RSTP capable switch will be needed soon to proceed, see + but a RSTP capable switch will be needed soon to proceed, see http://www.freebsd.org/donations/wantlist.html @@ -1112,7 +1112,7 @@ (performance, compatibility, a new driver, 24/32bit samples support, ...) have been merged to RELENG_6. FreeBSD 6.1 is the first release which ships with the much improved sound system. - Additionally there's work underway: + Additionally there's work underway:

                        • To make the sound system API endianess clean. This should make it easier (for a developer) to make the sound drivers usable diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml index a8f03d9ce9..b54b024047 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml @@ -43,7 +43,7 @@

                          Please read below for more detailed news on the projects that happened in FreeBSD during the last three months. If you are interested in helping, consider the "Open Tasks lists" provided with - some reports. In addition we would like to point you at the + some reports. In addition we would like to point you at the list of projects and ideas for volunteers @@ -141,7 +141,7 @@ from 14 different countries.

                          Our sponsorship pool continues to grow. This year we had - sponsorship from: + sponsorship from:

                          • USENIX @@ -176,7 +176,7 @@
                            - The + The t-shirts @@ -313,18 +313,18 @@ -

                            Some +

                            Some FPU system - and + and kernel memcpy/copyin/copyout changes have been performed. In particular, a per-CPU save area has been introduced (protected with an interlock) in order to assure a - stable saving mechanism. + stable saving mechanism. copyout/copyin - have changed in order to use vectorised version of + have changed in order to use vectorised version of memcpy and an xmm version of memcpy has been provided.

                            @@ -447,7 +447,7 @@

                            There are several projects moving forward in the embedded area. For now the main location for new information is - www.embeddedfreebsd.org. We have also created a new mailing list, + www.embeddedfreebsd.org. We have also created a new mailing list, freebsd-embedded@freebsd.org @@ -586,7 +586,7 @@ -

                            FreshPorts has seen several new features recently: +

                            FreshPorts has seen several new features recently:

                            • caching implemented at web application level to reduce load on the database server and to serve pages faster
                              • @@ -600,16 +600,16 @@ Most of the work lately has been optimisation, either at the database level or at the web application level.

                              -

                              A 2U server was recently donated to the +

                              A 2U server was recently donated to the FreshPorts - / + / FreshSource - / + / FreeBSD Diary - / + / BSDCan group. We have also received a RAID card. Now we're looking for @@ -620,17 +620,17 @@ will need a new home as I don't really want it running in my basement all the time (it's really loud!).

                              -

                              Thanks to +

                              Thanks to iXsystems - and + and 3Ware for their contributions to this project.

                              - We would like some more hardware (CPUs and HDD). Details + We would like some more hardware (CPUs and HDD). Details here @@ -702,7 +702,7 @@ -

                              The purpose of +

                              The purpose of gvirstor module is to provide the ability to create a virtual storage device @@ -800,7 +800,7 @@ -

                              Initial changes include: +

                              Initial changes include:

                              • Changed ip6_sprintf to no longer return a static buffer.
                                • @@ -1143,11 +1143,11 @@

                                The changes need some more testing but basically things work.

                                -

                                This is not considered to be the right thing todo so do +

                                This is not considered to be the right thing todo so do not ask for official support or if this will be committed to the - FreeBSD source repository. + FreeBSD source repository.
                                After some more cleanup of non-jail related IPv6 changes I will @@ -1465,7 +1465,7 @@ We need help getting back to our modern low of 500 PRs. - We have over 4,000 unmaintained ports (see, for instance, + We have over 4,000 unmaintained ports (see, for instance, the list on portsmon @@ -1474,7 +1474,7 @@ a few ports. We can always use help with infrastructural enhancements. See - the ports section of + the ports section of the list of projects and ideas @@ -1932,7 +1932,7 @@ -

                                With the help of Jim Thompson of Netgate ( +

                                With the help of Jim Thompson of Netgate ( http://www.netgate.com/ ) the FreeBSD Foundation arranged a purchase of xscale-based boards @@ -1981,7 +1981,7 @@ place I'll compare the performance of filters, against all the previous models: pre-SMPng(4.x), ithread and polling.

                                -

                                The most important modifications to the src tree so far were: +

                                The most important modifications to the src tree so far were:

                                • made PPC accept more than one FAST handler per irq line (previously INTR_FAST implied INTR_EXCL)
                                  • @@ -2089,7 +2089,7 @@

                                  TrustedBSD Audit provides fine-grained security event auditing in FreeBSD 7.x, with a planned merge to 6.x for FreeBSD 6.2. Work - performed in the last three months: + performed in the last three months:

                                  • Per audit pipe preselection allows IDS applications to configure audit record selection per-pipe, new auditpipe.4 diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml b/en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml index 3c29283132..076d206a05 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml @@ -20,17 +20,17 @@ Report//EN" ranks, kept working on their projects, and improving FreeBSD in general.

                                    -

                                    This year's +

                                    This year's EuroBSDCon in Milan, Italy has meanwhile published an exciting program. Many developers will be there to discuss these current and future projects at the Developer Summit prior the conference. Next year's conference calendar has a new entry - in addition to the now well - established + established BSDCan - in Ottawa - + in Ottawa - AsiaBSDCon will take place in Tokyo at the beginning of March.

                                    @@ -650,7 +650,7 @@ Report//EN" - The code still needs plenty of testing. See patches on + The code still needs plenty of testing. See patches on sctp.org and in -CURRENT soon. @@ -771,7 +771,7 @@ Report//EN"

                                    Ideas and comments with regard to the new USB API are welcome at: - + freebsd-usb@freebsd.org.

                                    @@ -881,7 +881,7 @@ Report//EN"

                                    Web site is up and we're soliciting papers and presentations. - Some tutorials are already scheduled. Email + Some tutorials are already scheduled. Email secretary@asiabsdcon.org @@ -1320,7 +1320,7 @@ Report//EN"

                                    As a participant of Google's Summer of Code 2006, I am focusing - on porting + on porting Xen @@ -1478,7 +1478,7 @@ Report//EN" We still need help getting back to our modern low of 500 PRs. - We have nearly 4400 unmaintained ports (see, for instance, + We have nearly 4400 unmaintained ports (see, for instance, the list on portsmon @@ -2378,7 +2378,7 @@ Report//EN"

                                    I've created a patch of all my work that is not in HEAD yet here (this is a snapshot of my development branch, so how thing's are - done might be changed quite fast): + done might be changed quite fast): http://folk.ntnu.no/lulf/patches/freebsd/gvinum/gvinum_all_current.diff @@ -2516,13 +2516,13 @@ Report//EN" -

                                    The dates for +

                                    The dates for BSDCan 2007 have been set: 11-12 May 2007. As is usual, BSDCan will be held at University of Ottawa, with two days of tutorials prior to the conference starting.

                                    -

                                    The +

                                    The call for papers will go out in mid December. Start thinking about your submissions @@ -2561,20 +2561,20 @@ Report//EN" June. Some highlights include:

                                      -
                                    • New news feed +
                                    • New news feed formats, including newsfeeds for your watch list.
                                    • Better pages caching for faster response.
                                      • -
                                    • Sanity Test Failures now available +
                                    • Sanity Test Failures now available online.
                                      • -
                                    • Ability to +
                                    • Ability to search for all commits @@ -2582,7 +2582,7 @@ Report//EN" (ports, doc, src, etc) under a given point in the tree.
                                    -

                                    For more detail, please review the +

                                    For more detail, please review the FreshPorts Blog .

                                    diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml index 117e4dc765..7b049976a8 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml @@ -20,13 +20,13 @@ Report//EN" tree. Many projects need your help with testing and otherwise. Please see the "Open tasks" sections for more information.

                                    -

                                    The BSD crowd will meet at +

                                    The BSD crowd will meet at AsiaBSDCon March 8-10th in Tokyo and a two day FreeBSD developer summit will be - held at + held at BSDCan - May 16-19th in Ottawa. Finally, + May 16-19th in Ottawa. Finally, EuroBSDCon September 14-15th in Copenhagen is already looking for papers.

                                    @@ -143,24 +143,24 @@ Report//EN"

                                    There have been a number of improvements to FreshPorts over the last quarter of 2006. The following are just a few of them. The - links take you to the relevant article within the + links take you to the relevant article within the FreshPorts News website - . + .

                                      -
                                    • Better +
                                    • Better pagination of larger result sets
                                      • -
                                    • Listing of +
                                    • Listing of sanity test failures
                                      • -
                                    • Inclusion of +
                                    • Inclusion of latest vulnerabilities @@ -168,17 +168,17 @@ Report//EN" on the front page
                                    • Started working on adding tools to make - FreshSource/FreshPorts more useful as a + FreshSource/FreshPorts more useful as a developer tool
                                      • -
                                    • The new +
                                    • The new dual opteron server - has been + has been deployed! @@ -216,28 +216,28 @@ Report//EN" -

                                      Folks! +

                                      Folks!
                                      - It is that time of year. You may have missed the + It is that time of year. You may have missed the call for papers , but please put in your proposal right away. This is often a busy time of year, but please take the time to consider presenting at BSDCan.

                                      -

                                      Please read the +

                                      Please read the submission instructions and send in your proposal today!

                                      You may be interested in our sister conference: PGCon. If you - have an interest in + have an interest in PostgreSQL , a leading relational database, which just happens to be open - source, then we have the conference for you! + source, then we have the conference for you! PGCon 2007 will be held immediately after BSDCan 2007, at the same venue, and @@ -518,7 +518,7 @@ Report//EN"

                                      X.org 7.2 release has been delayed more than a month, which gave us more time to fix build failures, to work on a few runtime issues and to determine the easiest way to upgrade from 6.9 to 7.2 (mostly - with the help of people on the + with the help of people on the freebsd-x11@ mailing list @@ -584,7 +584,7 @@ Report//EN" date.

                                      Ideas and comments with regard to the new USB API are welcome at - + freebsd-usb@FreeBSD.org @@ -634,7 +634,7 @@ Report//EN" internal handling have been fixed. Performance has been increased and system requirements reduced.

                                      -

                                      Many new features have been implemented: +

                                      Many new features have been implemented:

                                      • IPv6 support
                                        • @@ -646,7 +646,7 @@ Report//EN"

                                      -

                                      Some historically broken features have been reimplemented: +

                                      Some historically broken features have been reimplemented:

                                      • TCP and UDP link types
                                        • @@ -746,7 +746,7 @@ Report//EN"

                                        We need some more testers and bug reporters. So if you have a little bit of time and a favorite Linux application, please play around with it on -CURRENT. If there is a problem, have a look at - the wiki if we already know about it and report on + the wiki if we already know about it and report on emulation@ @@ -1003,7 +1003,7 @@ Report//EN" -

                                        Platform summary: +

                                        Platform summary:

                                        • PowerQuiccIII integrated controller
                                          • @@ -1019,7 +1019,7 @@ Report//EN"

                                          Currently the machine is booting FreeBSD 6.1-RELEASE-p10 and operating both single- and multi-user modes; below are highlights - of available functionality: + of available functionality:

                                          1. Low-level support
                                            2. @@ -1277,13 +1277,13 @@ Report//EN" implemented.
                                          2. Some major work is currently going on in the main BSNMP - tree: + tree:
                                            • SNMP transports have been factored out into loadable modules. The old port tables are still there and will remain at least for the next release. Later they will be removed. The following modules and transports are already implemented - as loadable modules: + as loadable modules:
                                              • snmp_trans_udp: SNMP over UDP over IPv4, IPv6 and scoped IPv6
                                                • @@ -1471,7 +1471,7 @@ Report//EN"

                                                Where have we been?! Not doing status reports, that's for sure. But the FreeBSD GNOME project has been very busy with regular GNOME releases, and other side projects. We are currently shipping GNOME - 2.16.2 in the ports tree, and we are testing GNOME 2.17.5 in the + 2.16.2 in the ports tree, and we are testing GNOME 2.17.5 in the MarcusCom @@ -1483,11 +1483,11 @@ Report//EN" version is currently being tested in the MarcusCom tree, and will make it into the FreeBSD ports tree along with GNOME 2.18.

                                                -

                                                The GStreamer framework has been taken out of direct +

                                                The GStreamer framework has been taken out of direct gnome@ - maintainership, and put under a new + maintainership, and put under a new multimedia@ @@ -1497,7 +1497,7 @@ Report//EN" other important audio and video components.

                                                The biggest accomplishment of 2006 for the FreeBSD GNOME team - had to have been the port of + had to have been the port of HAL . This effort was started to give FreeBSD users a richer desktop @@ -1515,13 +1515,13 @@ Report//EN" Now that HAL has been ported to FreeBSD, there is a strong - desire to see + desire to see NetworkManager ported. The big parts will be porting NM to use our 80211 framework, and extending some of the base utilities such as - ifconfig. Contact + ifconfig. Contact marcus@FreeBSD.org if you are interested in helping. @@ -1529,22 +1529,22 @@ Report//EN" Our system-tools-backends module needs some attention. This module is responsible for system configuration tasks in GNOME such as user management, network shares administration, etc. A knowledge - of Perl is highly recommended. Contact + of Perl is highly recommended. Contact marcus@FreeBSD.org if you are interested in helping. - We need good documentation writers to help update our + We need good documentation writers to help update our FAQ and other documentation. If you would like to take on the responsibility full-time, or just contribute some pieces, please - notify + notify gnome@FreeBSD.org . - We are always in need of GNOME development testers. See our + We are always in need of GNOME development testers. See our development branch FAQ @@ -1636,7 +1636,7 @@ Report//EN" into 2 parts: the filter (that checks if the actual interrupt belongs to a device) and a private per-handler ithread (that is scheduled in case some blocking work has to be done). The main - benefits of this work are: + benefits of this work are:

                                                • Feedback from filters (the operating system finally knows what's the state of an event and can react consequently).
                                                  • @@ -1725,7 +1725,7 @@ Report//EN" to resolve the old tickets and get the best feedback that is needed for the open tickets.

                                                  -

                                                  Please contact +

                                                  Please contact FreeBSD-bugbusters@FreeBSD.org @@ -1765,7 +1765,7 @@ Report//EN" Fundraiser. We fell short of our goal of raising $200,000. But, we are working hard to fill this gap, early in 2007, so we can continue with the same level of support for the project and - community. Please go to + community. Please go to http://www.freebsdfoundation.org/donate/ @@ -1785,7 +1785,7 @@ Report//EN" solicited so that we can do interoperability testing.

                                                  For more information on what we've been up to, check out our - end-of-year newsletter at + end-of-year newsletter at http://www.freebsdfoundation.org/press/2006Dec-newsletter.shtml @@ -2064,7 +2064,7 @@ Report//EN"

                                                  The ZFS file system works quite well on FreeBSD now. The first - patchset has already been published on the + patchset has already been published on the freebsd-fs@FreeBSD.org mailing list @@ -2177,7 +2177,7 @@ Report//EN"

                                                  Most work on the MAC Framework during this period, other than as relates to the priv(9) project described in a separate status - report, has been in refinement of the structure of the framework. + report, has been in refinement of the structure of the framework.

                                                  • Add two new entry points allowing MAC Framework policy modules to grant or limit fine-grained system privileges.
                                                    • @@ -2408,7 +2408,7 @@ Report//EN" 35ms from that FTP.FreeBSD.ORG and connected through a moderately loaded 100Mbit Internet link.

                                                    -

                                                    New sysctls are: +

                                                    New sysctls are:

                                                    • net.inet.tcp.sendbuf_auto=1 (enabled)
                                                      • @@ -2525,16 +2525,16 @@ Report//EN" -

                                                      The sixth EuroBSDCon will take place in Copenhagen, Denmark on +

                                                      The sixth EuroBSDCon will take place in Copenhagen, Denmark on Friday the 14th and Saturday 15th of September 2007 - . The conference will be held at + . The conference will be held at Symbion Science Park . Sunday the 16th there will be an optional tour to LEGOland.

                                                      -

                                                      The +

                                                      The call for papers was sent out right after EuroBSDCon 2006 in Milan in November and diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml index ec8e398220..767712ed3c 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml @@ -95,16 +95,16 @@ Report//EN" -

                                                      The +

                                                      The Schedule - and the + and the Tutorials have been released. Once again, we have a very strong collection of - + Speakers @@ -175,22 +175,22 @@ Report//EN" -

                                                      The sixth EuroBSDCon will take place at +

                                                      The sixth EuroBSDCon will take place at Symbion in Copenhagen, Denmark on Friday the 14th and Saturday 15th of September 2007.

                                                      -

                                                      The +

                                                      The estimated - price for the two day conference is 200EUR, excluding + price for the two day conference is 200EUR, excluding Legoland trip and social event. The whole-day trip to Legoland is expected to cost around 130EUR including transportation, some food on the way, and entry fee. Arrangements have been made with a newly - renovated + renovated Hostel @@ -209,13 +209,13 @@ Report//EN"

                                                      We are still looking for more sponsors.

                                                      -

                                                      A public IRC channel +

                                                      A public IRC channel #eurobsdcon on EFnet has been created for discussion and questions about the conference.

                                                      -

                                                      More details will follow on the +

                                                      More details will follow on the EuroBSDCon 2007 web site as they become available.

                                                      @@ -301,7 +301,7 @@ Report//EN" BSD Rootkits."

                                                      For more information on what we've been up to, check out our - website at + website at http://www.freebsdfoundation.org @@ -377,15 +377,15 @@ Report//EN" device driver to be built on FreeBSD with as little as possible modifications. Initially the project focused on USB webcams, a category of devices for which there was basically no support so - far. The emulation layer, available as a port ( + far. The emulation layer, available as a port ( devel/linux-kmod-compat ) simulates enough of the Linux USB stack to let us build, from unmodified Linux sources, two webcam drivers, also available as - ports ( + ports ( multimedia/linux-gspca-kmod - and + and multimedia/linux-ov511-kmod ), with the former supporting over 200 different cameras.

                                                      @@ -831,7 +831,7 @@ Report//EN" contact me if you are interested in helping. As part of this general effort, work is progressing steadily on removing the last remaining Giant-locked code from the kernel. A complete list of - remaining Giant-locked code is found here: + remaining Giant-locked code is found here: http://wiki.freebsd.org/SMPTODO diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml index 9a260c8e00..c058356cdc 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml @@ -15,10 +15,10 @@ Status Report//EN"

                                                      This report covers FreeBSD related projects between April and June 2007. Again an exciting quarter for FreeBSD. In May we saw one - of the biggest developers summits to date at + of the biggest developers summits to date at BSDCan - , our 25 Google Summer of Code students started working on + , our 25 Google Summer of Code students started working on their projects @@ -26,13 +26,13 @@ Status Report//EN" cycle was started three weeks ago.

                                                      If your are curious about what's new in FreeBSD 7.0 we suggest - reading Ivan Voras' excellent summary at: + reading Ivan Voras' excellent summary at: http://ivoras.sharanet.org/freebsd/freebsd7.html and of course these reports.

                                                      -

                                                      The next gathering of the BSD community will be at +

                                                      The next gathering of the BSD community will be at EuroBSDCon in Copenhagen , September 14-15. More details about the conference and the @@ -433,7 +433,7 @@ Status Report//EN"

                                                      The programme is ready and online at the webpage. Registration is open. Details about tutorials and Legoland trip are ready too. - +
                                                      The keynote will be John Hartman: Real men's pipes

                                                      @@ -1759,7 +1759,7 @@ Status Report//EN" the driver.
                                                    • Constructed a framework for logging Mandatory Access - Control hooks which is got called during a period of time. + Control hooks which is got called during a period of time.
                                                      • In kernel, every non-null label is got externalized into human readable string and recorded in a tail queue together @@ -1906,7 +1906,7 @@ Status Report//EN" optimization of both the FreeBSD operating system and applications running on it.

                                                        -

                                                        To learn more about what we're doing, go to our website at +

                                                        To learn more about what we're doing, go to our website at http://www.FreeBSDFoundation.org/ @@ -2622,12 +2622,12 @@ Status Report//EN"

                                                      • Via Rhine (if_vr, only VT6102 and up chips support WOL)
                                                        • -
                                                      • Nvidia nForce (if_nve, +
                                                      • Nvidia nForce (if_nve, needs testing )
                                                        • -
                                                      • 3Com Etherlink XL and Fast Etherlink XL (if_xl, +
                                                      • 3Com Etherlink XL and Fast Etherlink XL (if_xl, needs testing , only 3c905B type adapters support WOL)
                                                        • diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml b/en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml index c4e2862b2c..bf88d5ef70 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml @@ -22,7 +22,7 @@ Report//EN"

                                                        The bugs in the FreeBSD HEAD branch are being shaked out and it is being prepared for the FreeBSD 7 branching. If your are curious about what's new in FreeBSD 7.0 we suggest reading Ivan Voras' excellent - summary + summary here .

                                                        @@ -245,7 +245,7 @@ Report//EN" for their fantastic talks.

                                                        Also over 300 pictures from the conference has been uploaded to - Flickr with the tag + Flickr with the tag EuroBSDCon2007

                                                        @@ -739,13 +739,13 @@ Report//EN" -

                                                        The +

                                                        The GSoC2007/cnst-sensors - project was about porting the + project was about porting the sysctl hw.sensors - framework from OpenBSD to FreeBSD. The project was + framework from OpenBSD to FreeBSD. The project was successfully completed, @@ -759,7 +759,7 @@ Report//EN" storing, registering and accessing information about hardware monitoring sensors. Sensor types include, but are not limited to, temperature, voltage, fan RPM, time offset and logical drive - status. In the OpenBSD base system, the framework spans + status. In the OpenBSD base system, the framework spans sensor_attach(9), sysctl(3), sysctl(8), systat(1), sensorsd(8), ntpd(8) and more than 50 drivers, ranging from I2C temperature sensors and diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml index 2478eb3a62..796d8c1d3a 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml @@ -14,12 +14,12 @@ Report//EN" Introduction

                                                        This report covers FreeBSD related projects between October and - December 2007. + December 2007. AsiaBSDCon 2008 is approaching and will be held at the Tokyo University of Science in Tokyo, Japan on the 27th - 30th of March 2008. The FreeBSD Foundation - has released a + has released a Newsletter @@ -27,7 +27,7 @@ Report//EN" detailing their activities over the past few months.

                                                        FreeBSD 7.0 is nearing release and the 2nd Release Candidate is - ready for testing and is available for + ready for testing and is available for download now.

                                                        Thanks to all the reporters for the excellent work! We hope you @@ -929,7 +929,7 @@ Report//EN" Kritikakos, Vaggelis Typaldos, Stylianos Sideridis and others. Manolis has started translating the FAQ too, and we also tagged most of the Greek documents with their original, English revision - ID. There are also plans for a translation of + ID. There are also plans for a translation of www/en , but these may have to be deferred until we find the time to @@ -1028,7 +1028,7 @@ Report//EN" network stack or network card, is tracked and exposed to user space so that work associated with that connection can be performed on or close to the CPU where the kernel will be processing input for the - connection. Software work placement has been done using the + connection. Software work placement has been done using the netisr2 implementation, which creates per-CPU netisr threads and assigns diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml index c308c1978e..5ba9a7a0b5 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml @@ -14,7 +14,7 @@ Report//EN" Introduction

                                                        This Status Report covers FreeBSD related projects between January - and March 2008. During this time FreeBSD 7.0 was released. + and March 2008. During this time FreeBSD 7.0 was released. BSDCan is upon us with the Developer Summit starting the 14th and the @@ -198,7 +198,7 @@ Report//EN" licensed (it is provided with GCC 4.2.1) but since libc includes the mandatory symbols, programs won't be linked against GNU libssp. A new knob USE_SSP has been also added for the ports - infrastructure, you can set it to "yes" in make.conf(5) and use + infrastructure, you can set it to "yes" in make.conf(5) and use USE_SSP= on command-line to disable ProPolice for some ports. The patch has @@ -355,11 +355,11 @@ Report//EN" provided.

                                                      -

                                                      The code is checked into perforce under +

                                                      The code is checked into perforce under //depot/user/murray/www/apps/django/ideas/... and I would eventually like to see this hosted on FreeBSD.org - hardware, linked from the main website, and checked into + hardware, linked from the main website, and checked into www/apps/django/ideas.

                                                      @@ -679,7 +679,7 @@ Report//EN"

                                                      Our implementation of UnionFS has been merged into HEAD, 7-stable and 6-stable already. Now we are working on UnionFS stability improvement. We have developed the following 5 patches. - If you are interested, please try them and report your results.

                                                      + If you are interested, please try them and report your results.

                                                      • Currently the USB P4 project is under review.

                                                        Ideas and comments with regard to the new USB API are welcome on - the FreeBSD + the FreeBSD USB Mailing List diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml index c1edb378b2..a759e097a8 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml @@ -240,13 +240,13 @@ Report//EN"

                                                        We continue to make good progress in categorizing PRs as they arrive with 'tags' that correspond to manpages. (Special thanks go to Dylan Cochran for the help.) As a result, we now have created - some prototype reports that allow browsing the database + some prototype reports that allow browsing the database by manpage.

                                                        In addition, another new report, oriented towards PR submitters, - summarizes the + summarizes the most commonly reported issues. @@ -256,11 +256,11 @@ Report//EN"

                                                        Mark Linimon summarized the good technical suggestions from the bugathons so far this year to the wiki. As a part of this, he rearranged the wiki pages, so if you have not seen them for a - while, please see + while, please see BugBusting. In particular, the Resources page is much more complete.

                                                        -

                                                        Jeremy Chadwick (koitsu@) is now maintaining a +

                                                        Jeremy Chadwick (koitsu@) is now maintaining a page @@ -533,26 +533,26 @@ Report//EN" -

                                                        Hungarian translation of the +

                                                        Hungarian translation of the FreeBSD Handbook has been finally committed to the doc repository. The translation - of the + of the FreeBSD FAQ has also been started, however, the original document needed to be brought up to date first. Two other article translations has been - added, + added, compiz-fusion - and + and linux-users.

                                                        Our Perforce depot was reorganized for the better layout, giving - newcomers more space to play. The + newcomers more space to play. The checkupdate @@ -607,7 +607,7 @@ Report//EN" they are committed to the FreeBSD ports tree. We have already had the first Call for Public Testing on July 17th, 2008 with KDE 4.1 beta2. The feedback has been positive so far. If you want to help - to test them to speed up the process, please visit the + to test them to speed up the process, please visit the Wiki page and provide feedback.

                                                        @@ -727,7 +727,7 @@ Report//EN" building tools, including moving as a default to ZFS, which allows quick cloning of src and ports directories. It is now much easier to manage and monitor the builds. Work on this is continuing. See - the commits to + the commits to Tools/portbuild/scripts @@ -745,7 +745,7 @@ Report//EN"

                                                        Although a number of PRs have been closed, we are still at 57 portmgr PRs, the same as the last report.

                                                        -

                                                        The following large changes are in the pipeline: +

                                                        The following large changes are in the pipeline:

                                                        • Introduction of Perl 5.10
                                                        diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml index 9f6146d7f7..46678e1d65 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml @@ -215,10 +215,10 @@ Report//EN" -

                                                        In July, +

                                                        In July, pgj - gave a + gave a presentation @@ -227,29 +227,29 @@ Report//EN" Debrecen, Hungary.

                                                        Based on the checkupdate script mentioned in our previous status - report, we launched our + report, we launched our Translation Checking Service to help to schedule periodic updates for Hungarian doc/www translations. Moreover, a small bug in EPS images blocking - automatic generation of the Handbook PDF version + automatic generation of the Handbook PDF version was corrected - , therefore it is now available for + , therefore it is now available for download .

                                                        Shortly after the renovation of its source, translation of the - FAQ has also become part of Hungarian documentations. Both + FAQ has also become part of Hungarian documentations. Both online - and + and offline @@ -257,10 +257,10 @@ Report//EN" ( gjournal-desktop) has also been added.

                                                        -

                                                        Hungarian translation of the +

                                                        Hungarian translation of the FreeBSD Documentation Project Primer for New Contributors - has been + has been started . We hope this will encourage others to help our work. There is @@ -461,7 +461,7 @@ Report//EN"

                                                        Earlier this year I put efforts into the creation of a new layout - for the FreeBSD mailinglists. The following issues were tackled: + for the FreeBSD mailinglists. The following issues were tackled:

                                                        • Display which mailinglists are active and are visited often.
                                                          • @@ -616,7 +616,7 @@ Report//EN" specification see: http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC8572E This work is extending our (single core) MPC85XX port already - available in the SVN tree. Currently the MPC8572 support covers: + available in the SVN tree. Currently the MPC8572 support covers:
                                                          • all existing functionality of FreeBSD/MPC85XX (console, e500 interrupts/exceptions, networking, etc.)
                                                            • @@ -656,7 +656,7 @@ Report//EN"
                                                          • I2C controller
                                                          - High level functional summary: + High level functional summary:
                                                          • stable multiuser SMP operation
                                                            • diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml index 00df28e047..5f7e46457b 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml @@ -96,10 +96,10 @@ Report//EN" 23 videos are available from MeetBSD and NYCBSDCon, with more from BSDCan and AsiaBSDCon coming soon.

                                                            -

                                                            We are currently looking for more videos from - BSDCan, - EuroBSDCon, - AsiaBSDCon, +

                                                            We are currently looking for more videos from + BSDCan, + EuroBSDCon, + AsiaBSDCon, etc to upload to the channel. We also need help in creating subtitles for each video in various languages. If you would like to help out in generating subtitles for your language or if you have @@ -276,13 +276,13 @@ Report//EN"

                                                            We continue to make good progress in categorizing PRs as they arrive with 'tags' that correspond to manpages. As a result, we now have created some prototype reports that allow browsing the - database + database by manpage.

                                                            In addition, another new report, oriented towards PR submitters, - summarizes the + summarizes the most commonly reported issues. Many of these issues persist @@ -384,13 +384,13 @@ Report//EN" -

                                                            Hungarian translation of the +

                                                            Hungarian translation of the FreeBSD Documentation Project Primer for New Contributors - has been finished and now it is available both + has been finished and now it is available both online - and + and for download.

                                                            @@ -402,7 +402,7 @@ Report//EN"

                                                            Beside the continuous maintenance of the Hungarian documentation and web pages, a new article translation has been added to the - Hungarian Documentation Set, + Hungarian Documentation Set, CUPS.

                                                            @@ -486,7 +486,7 @@ Report//EN"

                                                            Three projects were started that are being funded by the foundation. They are Safe Removal of Active Disk Devices, Improvements to the FreeBSD TCP Stack, and Network Stack - Virtualization Projects. + Virtualization Projects. Click here @@ -497,7 +497,7 @@ Report//EN" developer to attend this conference. We also handed out a few limited edition foundation vests for developer recognition.

                                                            -

                                                            Read our +

                                                            Read our end-of-year newsletter, to find out what else we've done to diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml index 8d139b0470..3d358dd1cb 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml @@ -21,7 +21,7 @@ Report//EN" supports multi-IPv4/IPv6/noIP and much more. Lots of FreeBSD Developers are in Ottawa, Canada attending the FreeBSD Developer Summit that is before BSDCan. BSDCan officially starts tomorrow and - should cover lots of interesting topics, see the + should cover lots of interesting topics, see the BSDCan Website for more information.

                                                            @@ -100,31 +100,31 @@ Report//EN"

                                                            We continue to classify PRs as they arrive, with 'tags' corresponding to the kernel subsystem, or man page references for userland PRs. These tags, in turn, produce lists of PRs sorted both - + by tag - and + and by manpage

                                                            -

                                                            Mark Linimon (linimon@) has created +

                                                            Mark Linimon (linimon@) has created special reports for the Release Engineering Team to help focus on regressions and other areas of interest relating to the release of FreeBSD 7.2 in the coming weeks. This is a - refinement of the + refinement of the 'customized reports for developers' announced in the last status report.

                                                            -

                                                            A full list of all the +

                                                            A full list of all the automatically generated reports @@ -135,7 +135,7 @@ Report//EN" problem and investigating possible new work flow models, and will be presenting on the subject at BSDCan.

                                                            -

                                                            The list of +

                                                            The list of PRs recommended for committer evaluation @@ -312,14 +312,14 @@ Report//EN"

                                                          • Security advisories (HTML, RSS)
                                                          -

                                                          We are still hoping that having the +

                                                          We are still hoping that having the FDP Primer translated will encourage others to help our work. Feel free to contribute, every submitted line of translation or feedback is appreciated and is highly welcome. For more information on how to - contribute, please read the project's + contribute, please read the project's introduction @@ -466,7 +466,7 @@ Report//EN"

                                                          The TrustedBSD Project has now released OpenBSM 1.1, the second production release of the OpenBSM code base. OpenBSM 1.1 has been merged to FreeBSD 8-CURRENT, and will be merged to 7-STABLE before - FreeBSD 7.3. Major changes since OpenBSM 1.0 include: + FreeBSD 7.3. Major changes since OpenBSM 1.0 include:

                                                          • Trail files now include the host where the trail is generated. Crash recovery has been improved. Trail expiration @@ -605,7 +605,7 @@ Report//EN"

                                                            The translation of the Handbook was completed last January. It is kept up-to-date with the English version. Furthermore five - articles and the + articles and the flyer have been translated.

                                                            @@ -666,14 +666,14 @@ Report//EN"

                                                            It has been written as part of my Bachelor thesis and its development is a work in progress. Therefore, I would appreciate if you could provide me with some feedback as I will defend my thesis - soon. Your feedback is welcome at the + soon. Your feedback is welcome at the forums , or alternatively you can send me a private email.

                                                            The tool itself can now be installed using the Ports tree from - the + the sysutils/sysinfo @@ -721,7 +721,7 @@ Report//EN"

                                                            There is on-going work to allow "options MAC" to be included in the GENERIC kernel for 8.0. This primarily consists of performance work to reduce overhead when policies are used, and eliminate when - none are configured. Work to date includes: + none are configured. Work to date includes:

                                                            • The MAC Framework now detects which object types are labeled by policies, and MAC label storage is not allocated when it won't @@ -807,7 +807,7 @@ Report//EN"

                                                              A new DTrace provider, dtnfsclient, has been added to the FreeBSD 8.x kernel, and will be merged to 7.x before 7.3. The - following probes are available: + following probes are available:

                                                              • nfsclient:{nfs2,nfs3}:{procname}:start - NFSv2 and NFSv3 RPC start probes
                                                                • @@ -822,7 +822,7 @@ Report//EN" flush/hit/miss/done
                                                              - In addition, a number of VFS probes have been added: + In addition, a number of VFS probes have been added:
                                                              • vfs:vop:{vopname}:entry - VOP entry probe
                                                                • diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml index 139bc24cb0..6c9f04b8ec 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml @@ -552,7 +552,7 @@ Report//EN" from being modified to use libdispatch. - + VirtualBox on FreeBSD @@ -654,7 +654,7 @@ Report//EN"

                                                                The current translations (Handbook and some articles) are kept up to date with the English versions. Some parts of the website - have been + have been translated, more work is in progress.

                                                                diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml b/en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml index a1320fde1d..2b04ca3bb0 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml @@ -1235,7 +1235,7 @@ Report//EN"

                                                                Development of the &os; 802.11s stack continues. The code in &os; HEAD has been updated to comply with draft 4.0. Merge to &os; 8-STABLE will be done soon.

                                                                - +

                                                                The developer is looking for funding to be able to implement mesh link security algorithms and/or coordinated channel access (performance improvement).

                                                                @@ -1337,7 +1337,7 @@ Report//EN" Send patches upstream. -                                                                 + BSD-licensed iconv @@ -1504,7 +1504,7 @@ Report//EN" most of the PRs that refer to supported versions of &os; have been converted, and we are keeping up as new ones come in. We hope that this is making it easier to browse the PR database.

                                                                - +

                                                                The overall PR count jumped to over 6,200 during the 8.0-RELEASE release cycle but seems to have stabilized at around 6,100. As in the past, we have a fairly good clearance rate for ports PRs but @@ -1517,7 +1517,7 @@ Report//EN" closing PRs that the team has already analyzed. - + &os;/ia64 @@ -1556,7 +1556,7 @@ Report//EN" Continue to try to understand why multiple simultaneous package builds bring the machines down. - + Upgrade the firmware on the two machines at Yahoo! to see if that helps the problem. @@ -1649,7 +1649,7 @@ Report//EN" November 26th, 2009. With 8.0-RELEASE completed planning has begun for 7.3-RELEASE. The schedule has been set with the release date planned for early March 2010.

                                                                - +

                                                                The Release Engineering Team would like to thank George Neville-Neil (gnn@) for his service on the team. George continues to work with the &os; Project but has stepped down @@ -1702,7 +1702,7 @@ Report//EN" on an up-to-date unified zlib version in the kernel, which would also fix the last occasional IPcomp hiccups. - + The &os; Foundation Status Report @@ -1823,7 +1823,7 @@ Report//EN" to e.g. protect guests from messing with the lan's ARP tables; a tap + routing + proxy arp example is in the above freebsd-emulation@ posting.) - +

                                                              • Enable vbox's shared MAC feature when using bridged mode on a Wifi interface, together with the virtualbox-ose-kmod change this should fix bridged mode for Wifi users.
                                                                • @@ -1928,10 +1928,10 @@ Report//EN" NetBSD and OpenBSD. Afer the special California edition, meetBSD Wintercamp in Livigno, this year we are back to Krakow, Poland.

                                                                - +

                                                                In 2010, meetBSD will be held on 2-3 July at the Jagiellonian University.

                                                                - +

                                                                See the conference main web site for more details.

                                                                 @@ -2001,9 +2001,9 @@ Report//EN" Help with ARM/MIPS/sparc64. - + More testing of clang on 3rd party apps (ports). - + Discussion on integrating LLVM/clang into &os;. diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml index ca57a03482..154da486ec 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml @@ -369,12 +369,12 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

                                                                We continued our work on infrastructure projects to beef up hardware for package-building, network-testing, etc.

                                                                -

                                                                Follow us on +

                                                                Follow us on Twitter now!

                                                                -

                                                                We are fund-raising for 2010 now! Find out more at +

                                                                We are fund-raising for 2010 now! Find out more at http://www.FreeBSDFoundation.org/donate/.

                                                                @@ -751,11 +751,11 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> - Looking for help fixing + Looking for help fixing ports broken on CURRENT. - Looking for help with + Looking for help with Tier-2 architectures. @@ -1004,7 +1004,7 @@ geom sched insert ad4

                                                                &os;/mips has been ported to D-Link DIR-320, wireless router based on BCM5354 SoC. Project aims to providing several working images - tailored for different purposes (profiles). So far + tailored for different purposes (profiles). So far racoon based router-ipsec image is available.

                                                                @@ -1184,14 +1184,14 @@ geom sched insert ad4 subscriptions pay for development that is kept closed for at most 1 year, after which all patches used in a build are released to subscribers under the same BSD license as Chromium. Also, parts of - the closed patches are continually pushed upstream, + the closed patches are continually pushed upstream, the BSD i386 fix has already been committed upstream. The goal is to fund Chromium development on BSD while continually pushing patches back to the BSD-licensed Chromium project. I will spin off a Chromium port for ports soon, for those who do not mind using an older, stable build that does not have all the paid features - in the subscriber builds. You can read about + in the subscriber builds. You can read about the issues that a subscription would pay for, such as replacing the ALSA audio backend with OSS, and @@ -1787,7 +1787,7 @@ geom sched insert ad4

                                                                &os; is currently lacking support of LDAP based authentication and user identity.

                                                                -

                                                                We have integrated a stripped down +

                                                                We have integrated a stripped down OpenLDAP library (renamed to avoid conflict with ports OpenLDAP libraries), as well as some changes to OpenSSH as well as plugins for PAM, NSS and @@ -2280,7 +2280,7 @@ tank dedupratio 4.00x - which has CPU affinity and aligns with RSS-selected queues in high-end 1gbps and most 10gbps implementations. The following tasks have been completed:

                                                                - +
                                                                • Teach libkvm to handle dynamic per-cpu storage (DPCPU) to improve crashdump analysis of per-CPU data.
                                                                  • @@ -2293,9 +2293,9 @@ tank dedupratio 4.00x - bindings.
                                                                • Write new TCP/UDP connection and binding regression tests.
                                                                - +

                                                                The following tasks remain:

                                                                - +
                                                                • Migrate from naive work assignment algorithm to RSS assignment.
                                                                  • @@ -2309,7 +2309,7 @@ tank dedupratio 4.00x - to be explicitly migrated using a socket option.
                                                                • Detailed performance evaluation and optimization.
                                                                - +

                                                                This work is being performed in the &os; Perforce repository, and is sponsored by Juniper Networks. Connection groups and related features are slated for inclusion in &os; 9.0 (with possible diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml b/en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml index b398bbb826..8ec66e8875 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml @@ -833,7 +833,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> This is our 6th year of participation and we hope to once again see great results from our 18 students. Coding officially began May 24th, and we are in the middle of the mid-term evaluation period. - You can see and comment on weekly status reports on the mailing list or on the wiki.

                                                                @@ -1325,7 +1325,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">

                                                                The old ata(4) driver is believed to be going away sometime in - the future, to be replaced with ATA_CAM + the future, to be replaced with ATA_CAM [1]. However, ATA pseudo-RAID support in &os;, ataraid(4), is implemented as part of said ata(4) driver, which means that it, @@ -2309,15 +2309,15 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd"> policy decisions as needed. The core team has been elected by &os; developers every 2 years since 2000, and this marks our 6th democratically elected core team.

                                                                - +

                                                                The new core team would like to thank outgoing members Kris Kennaway, Giorgos Keramidas, George V. Neville-Neil, Murray Stokely, and Peter Wemm for their service over the past two (and in some cases, many more) years.

                                                                - +

                                                                The core team would also especially like to thank Dag-Erling Smøgrav for running the election.

                                                                - +

                                                                The newly elected core team members are:

                                                                  @@ -2327,7 +2327,7 @@ Report//EN" "http://www.FreeBSD.org/XML/www/share/sgml/statusreport.dtd">
                                                                • Pav Lucistnik
                                                                • Colin Percival
                                                                - +

                                                                The returning core team members are:

                                                                  diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml b/en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml index 286a40b1bd..07cf921845 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml @@ -1728,7 +1728,7 @@ Status Report//EN"

                                                                  HAST development is progressing nicely. Mikolaj Golub who contributes to HAST is now a &os; src committer. Some changes worth noting since the last report:

                                                                  - +
                                                                  • Compression of the data being sent over the network. This can speed up especially synchronization process.
                                                                    • diff --git a/en_US.ISO8859-1/htdocs/news/status/report.xsl b/en_US.ISO8859-1/htdocs/news/status/report.xsl index a77dc5e874..98e3d268c0 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report.xsl +++ b/en_US.ISO8859-1/htdocs/news/status/report.xsl @@ -66,11 +66,11 @@ - News Home | Status Home + News Home | Status Home - + @@ -138,6 +138,6 @@
                                                                    • -
                                          +
                    diff --git a/en_US.ISO8859-1/htdocs/news/status/status.sgml b/en_US.ISO8859-1/htdocs/news/status/status.sgml index b1fe65c8cf..709eae0847 100644 --- a/en_US.ISO8859-1/htdocs/news/status/status.sgml +++ b/en_US.ISO8859-1/htdocs/news/status/status.sgml @@ -27,7 +27,7 @@ maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over - the entire system, covering issues ranging from architecture to style. + the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all @@ -168,9 +168,9 @@ - +

                    What is CVSweb?

                    diff --git a/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml b/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml index 5fdbaa1f4b..6a73ac122f 100644 --- a/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml +++ b/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml @@ -672,7 +672,7 @@ these buses to be a subclass of this new base class.

                    This was done through an in-kernel emulation layer, which implements part of the linux kernel API on top of the FreeBSD kernel API. The initial implementation was good enough to - support a few USB webcam drivers, and is documented + support a few USB webcam drivers, and is documented here. The code is actually available as a port, devel/linux-kmod-compat, @@ -1979,10 +1979,10 @@ clean.

                    - - Improve cron(8) and atrun(8) + + Improve cron(8) and atrun(8) - +

                    Currently, cron(8) and atrun(8) are outdated in their implementation. Here are some directions for improvement:

                      @@ -1991,17 +1991,17 @@ clean.

                      as it was done in NetBSD.
                    -

                    Requirements:

                    +

                    Requirements:

                    • Strong knowledge of the C language and Unix API.
                     -                     +                     Improve Wine support in FreeBSD -

                    Technical contact: +

                    Technical contact: Kris Moore

                    In 2008, Tijl Coosemans did excellent work diff --git a/en_US.ISO8859-1/htdocs/projects/newbies.sgml b/en_US.ISO8859-1/htdocs/projects/newbies.sgml index 5082d9595d..0b504f1ea5 100644 --- a/en_US.ISO8859-1/htdocs/projects/newbies.sgml +++ b/en_US.ISO8859-1/htdocs/projects/newbies.sgml @@ -14,7 +14,7 @@ - +

                    The following resources are some of those which &os; newbies have found most helpful when learning to use &os;. Please send corrections and additions to @@ -31,19 +31,19 @@

                    Using the &os; web site

                    - +

                    This web site is the main source of up to date information about &os;. Newbies have found the following pages particularly helpful:

                    • Search the Handbook and FAQ, the whole web site, or the &os; mailing list archives.

                      • - +

                    • The Documentation page has links to the Handbook and FAQ, tutorials, information about contributing to the Documentation Project, documents in languages other than English, online manual pages, and much more.

                      • - +

                    • The Support page contains a wealth of information about &os;, including mailing lists, user groups, web and FTP sites, release information, and links to some sources of @@ -74,7 +74,7 @@ People New to Both &os; and Unix, is popular with absolute beginners. You do not have to know much about anything to enjoy this one.

                      • - +

                    • There is a lot of documentation to help for setting up ppp. You might start with the PPP and SLIP @@ -88,7 +88,7 @@ beginner step by step through each stage from installation to everything you need to know to set up and run a &os; system. You also get to understand what you are doing and why.

                      • - +

                    • The &os; Handbook and Frequently Asked Questions (FAQ) are the main documents for &os;. Essential reading, they contain a lot of @@ -97,7 +97,7 @@ contains the installation instructions and also provides lists of books and on-line resources, and the FAQ has a troubleshooting section.

                      • - +

                    • Join the &os;-Questions mailing list to see the questions you were too afraid to ask, and their answers. Subscribe by filling out the following form: @@ -105,13 +105,13 @@ You can look up old questions and answers via the search page.

                      • - +

                    • The main newsgroup for &os; is comp.unix.bsd.freebsd.misc. You might want to keep an eye on comp.unix.bsd.freebsd.announce as well.

                      • - +

                    • Manual pages are good for reference but not always the best introduction for a novice. The more you work with man pages @@ -165,13 +165,13 @@ what is available and pick one that seems to speak your language. Pretty soon you will want to move on to a book that gives more coverage.

                      • - +

                    • One book mentioned frequently by newbies is UNIX for the Impatient by Paul W. Abrahams and Bruce R. Larson, published by Addison-Wesley. It is intended both as a book for learning UNIX and a reference, and includes an introduction to UNIX concepts and handy chapter on using the X Window System.

                      • - +

                    • Another popular book is UNIX Power Tools by Jerry Peek, Tim O'Reilly and Mike Loukides, published by O'Reilly and Associates. It is organized as a series of short articles each of @@ -198,26 +198,26 @@ for Users is another introductory guide which is available in HTML at a mirror site near you, or can be installed on your own system.

                      • - +

                    • UNIX questions are dealt with in the newsgroup comp.unix.questions and the associated FAQ from the RMIT FTP site. Newbies are likely to be most interested in sections 1 and 2 initially.

                      • - +

                    • Another interesting newsgroup is comp.unix.user-friendly. Although this newsgroup is for discussing user-friendliness, it can contain some good information for newbies. The FAQ is also available by FTP.

                      • - +

                    • Many other web sites hold lists of UNIX tutorials and reference material. One of the best places to start looking is the UNIX page at Yahoo!.

                      • - +

                    Learning about the X Window System

                    @@ -268,7 +268,7 @@

                    User groups are good places to meet other &os; users. If there is no one nearby, you might consider starting one!

                    - +

                    Before talking to real humans about your new skills, you might want to check the Jargon File.

                    diff --git a/en_US.ISO8859-1/htdocs/projects/summerofcode-2007.sgml b/en_US.ISO8859-1/htdocs/projects/summerofcode-2007.sgml index f174d75396..183bab66d1 100644 --- a/en_US.ISO8859-1/htdocs/projects/summerofcode-2007.sgml +++ b/en_US.ISO8859-1/htdocs/projects/summerofcode-2007.sgml @@ -17,7 +17,7 @@ href="http://code.google.com/soc">Summer of Code 2007. We received more high quality applications this year than ever before. In the end it was a very tough decision to narrow it - down to the 25 students selected for funding by Google. + down to the 25 students selected for funding by Google. These student projects included security research, improved installation tools, new utilities, and more. Many of the students have continued working on their FreeBSD projects even after @@ -423,7 +423,7 @@
                  • Project: FreeBSD 'safety net' IO logging utility
                    Student: Sonja Milicic
                    Mentor: &a.le;
                    - Summary: + Summary:

                    Some administrative operations like filesystem or partition table debugging/repair would benefit from an "Undo" function, @@ -443,7 +443,7 @@

                  • Project: Provide an audit log analysis tool
                    Student: Liu Dongmei
                    Mentor: &a.rwatson;
                    - Summary: + Summary:

                    A GUI audit log analysis tool which can display audit log in tree view and list view and analyze audit log lively. It is important to provide a intuitionistic and visualize audit log to diff --git a/en_US.ISO8859-1/htdocs/projects/summerofcode-2008.sgml b/en_US.ISO8859-1/htdocs/projects/summerofcode-2008.sgml index c8e5321c30..0a3a14a556 100644 --- a/en_US.ISO8859-1/htdocs/projects/summerofcode-2008.sgml +++ b/en_US.ISO8859-1/htdocs/projects/summerofcode-2008.sgml @@ -17,7 +17,7 @@ href="http://code.google.com/soc">Summer of Code 2008. We received more high quality applications this year than ever before. In the end it was a very tough decision to narrow it - down to the 21 students selected for funding by Google. + down to the 21 students selected for funding by Google. These student projects included security research, improved installation tools, new utilities, and more. Many of the students have continued working on their FreeBSD projects even after diff --git a/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml b/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml index 9028941757..3525189c8a 100644 --- a/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml +++ b/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml @@ -69,7 +69,7 @@ conferences to present on their work, and a significant number go on to become FreeBSD developers. It's also a great job networking opportunity!

                    - +

                    Past Student Projects

                    @@ -97,7 +97,7 @@ href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2008">2008, 2007, 2006, and +href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2006">2006, and 2005].

                    @@ -218,7 +218,7 @@ href="http://wiki.freebsd.org/moin.cgi/SummerOfCode2005">2005].

                    Mentors

                    - +

                    A number of FreeBSD committers are willing to mentor students. A good place to start is the 'Technical contacts' listed with the example projects on the Fultus web site alt="FreeBSD 6 Unleashed" width="150" height="150"/> - FreeBSD 6 Unleashed covers everything you need to know to use + FreeBSD 6 Unleashed covers everything you need to know to use FreeBSD to its fullest potential. Jun 7, 2006, diff --git a/en_US.ISO8859-1/htdocs/releases/2.0.5R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.0.5R/notes.sgml index 9ea3d1669c..c3ff3660b5 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.0.5R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.0.5R/notes.sgml @@ -143,7 +143,7 @@ Name cache optimization ----------------------- The name-cache would cache all files of the same name to the same bucket, which would put for instance all ".." entries in the same bucket. We added -the parent directory version to frustrate the hash, and improved the +the parent directory version to frustrate the hash, and improved the management of the cache in various other ways while we were at it. Owner: Poul-Henning Kamp (phk@FreeBSD.org) @@ -218,7 +218,7 @@ Matsushita/Panasonic (Creative) CD-ROM driver The Matsushita/Panasonic CR-562 and CR-563 drives are now supported when connected to a Sound Blaster or 100% compatible host adapter. Up to four host adapters are supported for a total of 16 CD-ROM drives. -The audio functions are supported, along with access to the raw (2352 byte) +The audio functions are supported, along with access to the raw (2352 byte) data frames of any compact disc. Audio discs may be played using Karoke variable speed functions. @@ -277,7 +277,7 @@ Cronyx/Sigma sync/async serial driver ------------------------------------- Owner: core Submitted by: Serge Vakulenko -Sources involved: isa/cronyx.c +Sources involved: isa/cronyx.c @@ -293,7 +293,7 @@ and Novell ethernet cards are currently supported. DEC DC21140 Fast Ethernet driver -------------------------------- -This driver supports any of the numerous NICs using the DC21140 chipset +This driver supports any of the numerous NICs using the DC21140 chipset including the 100Mb DEC DE-500-XA and SMC 9332. Owner: core @@ -485,7 +485,7 @@ Buslogic 946c PCI SCSI controller Buslogic 956c PCI SCSI controller NCR 53C810 and 53C825 PCI SCSI controller. -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -501,7 +501,7 @@ DAT) and CD ROM drives. The following CD-ROM type systems are supported at this time: (cd) SCSI (also includes ProAudio Spectrum and SoundBlaster SCSI) -(mcd) Mitsumi proprietary interface +(mcd) Mitsumi proprietary interface (matcd) Matsushita/Panasonic (Creative) proprietary interface (scd) Sony proprietary interface @@ -760,7 +760,7 @@ mentioned, and we sincerely hope you enjoy this release of FreeBSD! The FreeBSD Core Team -Id: RELNOTES.FreeBSD,v 1.7 1995/05/28 19:49:57 jkh Exp +Id: RELNOTES.FreeBSD,v 1.7 1995/05/28 19:49:57 jkh Exp

                    Release Home diff --git a/en_US.ISO8859-1/htdocs/releases/2.0/install.sgml b/en_US.ISO8859-1/htdocs/releases/2.0/install.sgml index 5b32f4039f..e532380ba9 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.0/install.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.0/install.sgml @@ -288,7 +288,7 @@ actual filesystems. We also see that partition h points conveniently to the DOS slice, which we can also assign to a location in our filesystem hierarchy -to conveniently share files between FreeBSD and DOS. More on this in +to conveniently share files between FreeBSD and DOS. More on this in a moment. A typical filesystem layout might look like this: diff --git a/en_US.ISO8859-1/htdocs/releases/2.0/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.0/notes.sgml index a7021d9900..451021dc03 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.0/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.0/notes.sgml @@ -127,11 +127,11 @@ Loadable filesystems Most filesystems are now dynamically loadable on demand, with the exception of the UFS family (FFS, LFS, and MFS). With the exception of NFS, all such filesystems can be unloaded when all references are -unmounted. To support this functionality, the +unmounted. To support this functionality, the getvfsbyname(3) -family of functions has been added to the C library and the +family of functions has been added to the C library and the lsvfs(1) command provides the same information at the shell level. Be aware of @@ -239,10 +239,10 @@ Device configuration database ----------------------------- The kernel now keeps better track of which device drivers are active and where the devices are attached; this information is made available to -user programs via the new +user programs via the new sysctl(3) management interface. Current -applications include +applications include lsdev(8), which lists the currently configured devices. In the future, we expect to use this code to automatically @@ -260,7 +260,7 @@ series of kernel variables and parameters which were previously manipulated by reading and writing /dev/kmem. Many programs have been rewritten to use this interface, although many old-style programs still remain. Some variables which were never accessible before are now available through -the +the sysctl(1) program. In addition to the standard 4.4BSD MIB variables, we have added support for YP/NIS domains (kern.domainname), controlling @@ -652,7 +652,7 @@ hope you enjoy this release of FreeBSD! The FreeBSD Core Team -Id: RELNOTES.FreeBSD,v 1.21 1994/12/02 20:27:11 jkh Exp +Id: RELNOTES.FreeBSD,v 1.21 1994/12/02 20:27:11 jkh Exp diff --git a/en_US.ISO8859-1/htdocs/releases/2.1.5R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.1.5R/notes.sgml index 759edca802..9313a77bb2 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.1.5R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.1.5R/notes.sgml @@ -68,7 +68,7 @@ Kernel features: Various VM system enhancements and more than a few bugs fixed. A concatenated disk driver for simple types of RAID applications. -See the man page for +See the man page for ccd(4)> for more information. @@ -222,7 +222,7 @@ Buslogic 946c PCI SCSI controller Buslogic 956c PCI SCSI controller NCR 53C810 and 53C825 PCI SCSI controller. -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -516,7 +516,7 @@ The FreeBSD Development Team, excluding core team members Additional FreeBSD helpers and beta testers: - Coranth Gryphon Dave Rivers + Coranth Gryphon Dave Rivers Kaleb S. Keithley Michael Smith Terry Lambert David Dawes Troy Curtis diff --git a/en_US.ISO8859-1/htdocs/releases/2.1.6R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/2.1.6R/announce.sgml index 96d488733e..6c81d36351 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.1.6R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.1.6R/announce.sgml @@ -12,7 +12,7 @@ -

                    Please read an important security +

                    Please read an important security announcement regarding FreeBSD 2.1.6

                    FreeBSD 2.1.6 is now available in:

                    diff --git a/en_US.ISO8859-1/htdocs/releases/2.1.6R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.1.6R/notes.sgml index 49624fdccc..f028a69e43 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.1.6R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.1.6R/notes.sgml @@ -62,7 +62,7 @@ Kernel features: Various VM system enhancements and more than a few bugs fixed. A concatenated disk driver for simple types of RAID applications. -See the man page for +See the man page for ccd(4)> for more information. @@ -218,7 +218,7 @@ Buslogic 946c PCI SCSI controller Buslogic 956c PCI SCSI controller NCR 53C810 and 53C825 PCI SCSI controller. -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -516,10 +516,10 @@ The FreeBSD Development Team, excluding core team members Additional FreeBSD helpers and beta testers: - Coranth Gryphon Dave Rivers + Coranth Gryphon Dave Rivers Kaleb S. Keithley Don Lewis Terry Lambert David Dawes - Troy Curtis + Troy Curtis Special mention to: diff --git a/en_US.ISO8859-1/htdocs/releases/2.1.6R/security.sgml b/en_US.ISO8859-1/htdocs/releases/2.1.6R/security.sgml index a301c9ceaf..28eb2f9ce8 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.1.6R/security.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.1.6R/security.sgml @@ -18,9 +18,9 @@ earlier systems was found. The problem has been corrected within the -stable, -current, and RELENG_2_2 source trees. As an additional precaution, FreeBSD 2.1.6 is no longer - available from the FTP distribution sites. An update release + available from the FTP distribution sites. An update release (provisionally "FreeBSD 2.1.7") is expected shortly. -

                    +

                    You can read more about the problem and solution from the diff --git a/en_US.ISO8859-1/htdocs/releases/2.1.7R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.1.7R/notes.sgml index 113f1f1b76..7d7a145997 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.1.7R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.1.7R/notes.sgml @@ -72,7 +72,7 @@ Kernel features: Various VM system enhancements and more than a few bugs fixed. A concatenated disk driver for simple types of RAID applications. -See the man page for +See the man page for ccd(4)> for more information. @@ -227,7 +227,7 @@ Buslogic 946c PCI SCSI controller Buslogic 956c PCI SCSI controller NCR 53C810 and 53C825 PCI SCSI controller. -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -524,7 +524,7 @@ The FreeBSD Development Team, excluding core team members Additional FreeBSD helpers and beta testers: - Coranth Gryphon Dave Rivers + Coranth Gryphon Dave Rivers Kaleb S. Keithley Michael Smith Terry Lambert David Dawes Troy Curtis diff --git a/en_US.ISO8859-1/htdocs/releases/2.1R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.1R/notes.sgml index f69828d7cc..1990c2da20 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.1R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.1R/notes.sgml @@ -138,7 +138,7 @@ Buslogic 946c PCI SCSI controller Buslogic 956c PCI SCSI controller NCR 53C810/15/25/60/75 PCI SCSI controller. -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -329,7 +329,7 @@ Special mention to: Additional FreeBSD helpers and beta testers: - Atsushi Murai Coranth Gryphon + Atsushi Murai Coranth Gryphon Dave Rivers Frank Durda IV Guido van Rooij Jeffrey Hsu John Hay Julian Elischer diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.1R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.1R/notes.sgml index 00117362d4..7ba1394a9d 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.1R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.1R/notes.sgml @@ -75,7 +75,7 @@ in 2.2. The number of EISA slots to probe is now a fully supported option, including the ability to save the value from a UserConfig session -with +with dset(8)>. This helps owners of HP NetServer LC machines to install the system on their hardware. @@ -112,7 +112,7 @@ The syscons and psm drivers now have a new underlying shared keyboard driver, eliminating many of the previously existing problems with their mutual interaction. -Syscons now supports cut & paste in textmode using the +Syscons now supports cut & paste in textmode using the moused(8)> utility. @@ -190,10 +190,10 @@ The kernel configuration option handling has been largely moved away from the old -D Makefile kludges, towards a system of "opt_foo.h" kernel include files, allowing Makefile dependencies to work again. We expect the old hack that blows the entire compile directory away -on each run of +on each run of config(8)> to go away anytime soon. Unless you're changing -weird options, you might now consider using the -n option to +weird options, you might now consider using the -n option to config(8)>, or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for you. See also the comments in the handbook about how it works. @@ -260,7 +260,7 @@ controllers: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -398,7 +398,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your @@ -516,7 +516,7 @@ or, if you've loaded the doc distribution: Additional FreeBSD helpers and beta testers: - Coranth Gryphon Dave Rivers + Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.2R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.2R/notes.sgml index 85f03f8431..f97a7e6b67 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.2R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.2R/notes.sgml @@ -90,7 +90,7 @@ in 2.2. The number of EISA slots to probe is now a fully supported option, including the ability to save the value from a UserConfig session -with +with dset(8)>. This helps owners of HP NetServer LC machines to install the system on their hardware. @@ -127,7 +127,7 @@ The syscons and psm drivers now have a new underlying shared keyboard driver, eliminating many of the previously existing problems with their mutual interaction. -Syscons now supports cut & paste in textmode using the +Syscons now supports cut & paste in textmode using the moused(8)> utility. @@ -205,10 +205,10 @@ The kernel configuration option handling has been largely moved away from the old -D Makefile kludges, towards a system of "opt_foo.h" kernel include files, allowing Makefile dependencies to work again. We expect the old hack that blows the entire compile directory away -on each run of +on each run of config(8)> to go away anytime soon. Unless you're changing -weird options, you might now consider using the -n option to +weird options, you might now consider using the -n option to config(8)>, or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for you. See also the comments in the handbook about how it works. @@ -275,7 +275,7 @@ controllers: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -413,7 +413,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your @@ -531,7 +531,7 @@ or, if you've loaded the doc distribution: Additional FreeBSD helpers and beta testers: - Coranth Gryphon Dave Rivers + Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.5R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.5R/errata.sgml index 0f011c23fe..024abb34a6 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.5R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.5R/errata.sgml @@ -41,7 +41,7 @@ o FreeBSD-SA- You may also simply remove /dev/io as a quick work-around if you're not running an X server or some other specialized utility which requires access to the I/O instructions. - + ---- System Update Information: o The appletalk stack was broken in 2.2.5. @@ -63,8 +63,8 @@ o Intel "F00F bug" enables users to hang machines with Pentium processors if they have access to the machine and can execute programs. Fix: Update to the 2.2-stable version of the kernel or apply the patch - found in: - + found in: + ftp://ftp.FreeBSD.org/pub/FreeBSD/updates/2.2.5-RELEASE/f00f.diff.2.2.gz @@ -82,12 +82,12 @@ o A bug in XF86Setup causes it to fail to create a symbolic link from displayed: xinit: No such file or directory (errno 2): no server "X" found in PATH - + Fix: Execute the following commands (as root) and re-run XF86Setup. # cd /usr/X11R6/bin # ln -s XF86_VGA16 X - + If XF86Setup asks you if you want to use the existing XF86Config for defaults choose no. When it asks you if you want to create an 'X' link to the server choose yes. diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.5R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.5R/notes.sgml index a158f03770..ac7bc3264f 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.5R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.5R/notes.sgml @@ -21,8 +21,8 @@ o For information about the layout of the release directory, see o It is also important to check the ERRATA.TXT file for any late-breaking issues with this release. This file contains the - latest information on significant bugs, security problems or - other similar issues which an administrator should be aware of. + latest information on significant bugs, security problems or + other similar issues which an administrator should be aware of. o For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. @@ -159,7 +159,7 @@ controllers: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -304,7 +304,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your @@ -422,7 +422,7 @@ or, if you've loaded the doc distribution: Additional FreeBSD helpers and beta testers: - Coranth Gryphon Dave Rivers + Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.6R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.6R/errata.sgml index f7cf98191c..c8d911a8c8 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.6R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.6R/errata.sgml @@ -64,7 +64,7 @@ For FreeBSD 2.2.6 and later, this format changes so that the device for # Device Mountpoint FStype Options Dump Pass# /dev/wd0s2b none swap sw 0 0 /dev/wd0s2a / ufs rw 1 1 -/dev/wd0s2f /local0 ufs rw 1 1 +/dev/wd0s2f /local0 ufs rw 1 1 /dev/wd0s2e /usr ufs rw 1 1 If /etc/fstab is not updated manually in this case, the system will @@ -73,34 +73,34 @@ indicating the change that must be made. In addition, trouble may be experienced if the root filesystem is not correctly unmounted, whereby the root filesystem will not be marked clean at the next reboot. -This change should be made as soon as the upgraded system has been +This change should be made as soon as the upgraded system has been successfully rebooted. o The ppp program fails to work, citing a missing shared library called "libdes.so.3.0". -Fix: There are three possible fixes: - -1. The easiest fix is to simply install the des distribution with +Fix: There are three possible fixes: + +1. The easiest fix is to simply install the des distribution with /stand/sysinstall, remembering to pick a site that will allow you to export it if you're outside the United States and Canada (ftp.FreeBSD.org and ftp.internat.FreeBSD.org both fall into this category). - -2. Purely as a work-around, and what you may need to do if ppp + +2. Purely as a work-around, and what you may need to do if ppp also constitutes your only way of getting to the net, is to simply do the following (as root): - cp /usr/lib/libcrypt.so.2.0 /usr/lib/libdes.so.3.0 + cp /usr/lib/libcrypt.so.2.0 /usr/lib/libdes.so.3.0 ldconfig -m /usr/lib -3. Another fix, and one which doesn't involve having to fetch the DES +3. Another fix, and one which doesn't involve having to fetch the DES bits, is to install the ppp sources in /usr/src/usr.sbin/ppp and rebuild them. The sources are "smart" enough to know that the DES library isn't on the system and won't create a binary which depends on it. -NOTE: If you choose the 2nd or 3rd fixes, you also will not be able to +NOTE: If you choose the 2nd or 3rd fixes, you also will not be able to use MSCHAP (Microsoft Win*) style authentication. @@ -120,14 +120,14 @@ The patch itself can also be obtained from the port itself: ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/ports/x11/XFree86/patches/patch-ag -o The older Matsushita (Panasonic), Sony CDU-31 and Mitsumi (non-IDE) +o The older Matsushita (Panasonic), Sony CDU-31 and Mitsumi (non-IDE) CDROM drives no longer permit CDROM installs. Fix: Fetch an updated boot floppy from the updates/ directory, e.g.: ftp://ftp.FreeBSD.org/pub/FreeBSD/updates/2.2.6-RELEASE/boot.flp -And use it to install 2.2.6 instead. This problem is fixed in 2.2-stable +And use it to install 2.2.6 instead. This problem is fixed in 2.2-stable and will not be a problem with the next FreeBSD release. diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.6R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.6R/notes.sgml index 76ec1031d7..339d50b954 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.6R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.6R/notes.sgml @@ -47,7 +47,7 @@ o The psm, mse and sysmouse drivers are improved to provide various mice with a ``wheel''. It also automatically recognizes mice which support the PnP COM device standard so that the user is no longer required to supply a mouse protocol - type on the command line. + type on the command line. Userland features: diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.7R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.7R/errata.sgml index fc47b9bd88..85771b9217 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.7R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.7R/errata.sgml @@ -52,7 +52,7 @@ o Release notes state that Texas Instruments ThunderLAN PCI NICs are supported in 2.2.7. Fix: This was an embarrassing mis-merge from the 3.0 release notes and, - indeed, those cards are only supported in 3.0-current. Please ignore + indeed, those cards are only supported in 3.0-current. Please ignore this section of the release notes and any other docs which claim that the ThunderLAN NICs are supported in 2.2.7. @@ -61,7 +61,7 @@ o rshd was broken during -Wall cleanup, as noted in PR#7500 Fix: This was fixed in the 2.2-stable branch as of 1998/07/24 04:32:21 in revision 1.9.2.9 of /usr/src/libexec/rshd/rshd.c. Obtain the - fixed version via CVSup (see instructions in handbook or simply + fixed version via CVSup (see instructions in handbook or simply ``pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz'' and follow the instructions) or get it from FTP at: ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/src/libexec/rshd/rshd.c diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.7R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.7R/notes.sgml index 87408d4b41..7daccdead2 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.7R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.7R/notes.sgml @@ -155,7 +155,7 @@ controllers: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -314,7 +314,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your @@ -376,34 +376,34 @@ watch out for. If, for some reason, you are unable to use the send-pr command to submit a bug report, you can try to send it to: - + freebsd-bugs@FreeBSD.org - + Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. - + Otherwise, for any questions or tech support issues, please send mail to: - + freebsd-questions@FreeBSD.org - + Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: - + freebsd-hackers@FreeBSD.org - + Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: - + freebsd-announce@FreeBSD.org - + All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This @@ -411,32 +411,32 @@ will give you more information on joining the various lists, accessing archives, etc. There are a number of mailing lists targeted at special interest groups not mentioned here, so send mail to majordomo and ask about them! - + 5. Acknowledgements ------------------- - + FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: - + http://www.FreeBSD.org/handbook/staff.html - + or, if you've loaded the doc distribution: - + file:/usr/share/doc/handbook/staff.html - + Special mention to: - + The donors listed at http://www.FreeBSD.org/handbook/donors.html - + Everyone at Montana State University for their initial support. - + And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. - + We sincerely hope you enjoy this release of FreeBSD! - + The FreeBSD Project

                    Release Home diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.8R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.8R/errata.sgml index 486fd70230..d17f7747fd 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.8R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.8R/errata.sgml @@ -43,9 +43,9 @@ Fix: sysctl(8) has actually moved to /sbin/sysctl. Simply create a symbolic link for compatability purposes as follows: ln -sf /sbin/sysctl /usr/sbin - + or syncronize your sources with 2.2-stable and rebuild/install - from /usr/src/usr.bin/whereis/ and just rm /usr/sbin/sysctl + from /usr/src/usr.bin/whereis/ and just rm /usr/sbin/sysctl o /usr/share/doc/FAQ is in spanish. @@ -57,7 +57,7 @@ Fix: This was a build failure which affected only the FAQ and has since to get an english FAQ. o getpwnam(3) semantics are incorrect in some cases. - + Fix: If passed a string longer than the maximum allowed for a user name, getpwnam will incorrectly return an entry for a user that matches the initial characters in the string up to the maximum length allowed for a diff --git a/en_US.ISO8859-1/htdocs/releases/2.2.8R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.2.8R/notes.sgml index 9d351e7edf..d111e2fa10 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2.8R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2.8R/notes.sgml @@ -119,7 +119,7 @@ controllers: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -277,7 +277,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. @@ -331,34 +331,34 @@ watch out for. If, for some reason, you are unable to use the send-pr command to submit a bug report, you can try to send it to: - + freebsd-bugs@FreeBSD.org - + Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. - + Otherwise, for any questions or tech support issues, please send mail to: - + freebsd-questions@FreeBSD.org - + Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: - + freebsd-hackers@FreeBSD.org - + Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: - + freebsd-announce@FreeBSD.org - + All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This @@ -366,32 +366,32 @@ will give you more information on joining the various lists, accessing archives, etc. There are a number of mailing lists targeted at special interest groups not mentioned here, so send mail to majordomo and ask about them! - + 5. Acknowledgements ------------------- - + FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: - + http://www.FreeBSD.org/handbook/staff.html - + or, if you've loaded the doc distribution: - + file:/usr/share/doc/handbook/staff.html - + Special mention to: - + The donors listed at http://www.FreeBSD.org/handbook/donors.html - + Everyone at Montana State University for their initial support. - + And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. - + We sincerely hope you enjoy this release of FreeBSD! - + The FreeBSD Project diff --git a/en_US.ISO8859-1/htdocs/releases/2.2R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/2.2R/announce.sgml index d067abafe7..a4d1ce2761 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2R/announce.sgml @@ -16,16 +16,16 @@ long-awaited first release of our 2.2 branch technology following lengthy ALPHA, BETA and GAMMA testing cycles.

                    -

                    FreeBSD 2.2-RELEASE is now available on -ftp.FreeBSD.org and +

                    FreeBSD 2.2-RELEASE is now available on +ftp.FreeBSD.org and various FTP mirror sites -throughout the world. It can also be ordered on CD from -Walnut Creek CDROM, from +throughout the world. It can also be ordered on CD from +Walnut Creek CDROM, from where it will be shipping shortly.

                    FreeBSD 2.2 represents a rather large leap in functionality from the 2.1.x releases, everyone being is strongly encouraged to read the -release notes for a list +release notes for a list of new features.

                    Release Home diff --git a/en_US.ISO8859-1/htdocs/releases/2.2R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/2.2R/notes.sgml index eceb05120d..1d4b54445c 100644 --- a/en_US.ISO8859-1/htdocs/releases/2.2R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/2.2R/notes.sgml @@ -47,8 +47,8 @@ in 2.2. The number of EISA slots to probe is now a fully supported option, including the ability to save the value from a UserConfig session -with -dset(8). +with +dset(8). This helps owners of HP NetServer LC machines to install the system on their hardware. @@ -81,7 +81,7 @@ The syscons and psm drivers now have a new underlying shared keyboard driver, eliminating many of the previously existing problems with their mutual interaction. -Syscons now supports cut & paste in textmode using the +Syscons now supports cut & paste in textmode using the moused(8) utility. @@ -159,10 +159,10 @@ The kernel configuration option handling has been largely moved away from the old -D Makefile kludges, towards a system of "opt_foo.h" kernel include files, allowing Makefile dependencies to work again. We expect the old hack that blows the entire compile directory away -on each run of +on each run of config(8) to go away anytime soon. Unless you're changing -weird options, you might now consider using the -n option to +weird options, you might now consider using the -n option to config(8), or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for you. See also the comments in the handbook about how it works. @@ -229,7 +229,7 @@ controllers: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. @@ -367,7 +367,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your @@ -485,7 +485,7 @@ or, if you've loaded the doc distribution: Additional FreeBSD helpers and beta testers: - Coranth Gryphon Dave Rivers + Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis diff --git a/en_US.ISO8859-1/htdocs/releases/3.0R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/3.0R/errata.sgml index 54c8bdd4dc..2d66295078 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.0R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.0R/errata.sgml @@ -50,17 +50,17 @@ o The GPL_MATH_EMULATE kernel option causes a fatal trap during system Fix: Replace the GPL_MATH_EMULATE option with the default math emulation option MATH_EMULATE. This will only affect users who have modified their kernel configuration file. The problem is - corrected in revision 1.16 of the file + corrected in revision 1.16 of the file /usr/src/sys/gnu/i386/fpemul/fpu_entry.c. o DOS partition installs fail to find the installation bits. - -Fix: Rename C:\FREEBSD to C:\3.0-RELEASE and retry the installation. - The naming syntax was changed to make DOS more like the other - types of installation media but the docs on DOS installation - were not updated properly to reflect this. The current sysinstall + +Fix: Rename C:\FREEBSD to C:\3.0-RELEASE and retry the installation. + The naming syntax was changed to make DOS more like the other + types of installation media but the docs on DOS installation + were not updated properly to reflect this. The current sysinstall now accepts both locations, as it should have to begin with. diff --git a/en_US.ISO8859-1/htdocs/releases/3.0R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/3.0R/notes.sgml index c01efc177c..b6eb79189d 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.0R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.0R/notes.sgml @@ -66,7 +66,7 @@ specifically marked as [MERGED] features. 1.1. KERNEL CHANGES ------------------- -o The 2.2.x SCSI subsystem has been almost entirely replaced with +o The 2.2.x SCSI subsystem has been almost entirely replaced with a new "CAM" (Common Access Method) SCSI system which offers improved performance, better error recovery and support for more SCSI controllers. @@ -94,7 +94,7 @@ o ATAPI/IDE tape drive support (BETA). o Support for using VESA video modes. It is now possible to select and use the modes provided by the BIOS on modern videocards. This enables fx. 132x60 sized consoles and highres graphics in a generic manner on - hardware that supports it. There is also support for running the + hardware that supports it. There is also support for running the console in rastermode, which allows XFree86 to run a simple 16color server in 800x600 on otherwise unsupported video hardware. @@ -114,7 +114,7 @@ o The ed0 (wd8xxxx, 3c503, NE2000, HP Lan+) Ethernet device's default IRQ o The code responsible for maintaining time of day has been rewritten. New features are: true support for nanoseconds in both kernel and userland, continuous rather than stepwise adjustment - by NTPD and support for synchronizing to high precision external time + by NTPD and support for synchronizing to high precision external time signals. o Support for the PPS API described in draft-mogul-pps-api-02.txt for @@ -139,7 +139,7 @@ o The UPAGES are gone from the per-process address space which allows o Newly forked child processes return directly to user mode rather than return up through the fork() syscall tree. This eliminates the kernel - stack copy at fork time and simplifies certain other internal operations. + stack copy at fork time and simplifies certain other internal operations. It is also needed to support the removal of the UPAGES. (The idea for this originally came from NetBSD, but we did it for different reasons.) @@ -226,7 +226,7 @@ o An interrupt driven configuration hook mechanism has been implemented. o The timeout(9) system in the kernel has been overhauled. This gives O(1) insertion and removal of callouts and an O(hash chain length) amount of work to be performed in softclock. The original paper is at: - http://www.cs.berkeley.edu/~amc/research/timer/ + http://www.cs.berkeley.edu/~amc/research/timer/ o Changes in driver buffer queuing to deal with ordered transactions. This is intended for sequencing data and metadata writes in the filesystem code @@ -372,7 +372,7 @@ commands. moused(8) has been modified to support various mice with a ``wheel''. It also automatically recognizes mice which support the PnP COM device -standard, so that the user is no longer required to supply a mouse +standard, so that the user is no longer required to supply a mouse protocol type on the command line. [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch] @@ -485,7 +485,7 @@ NOT YET supported under the new CAM SCSI subsystem: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -666,7 +666,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your diff --git a/en_US.ISO8859-1/htdocs/releases/3.1R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/3.1R/errata.sgml index abc9fc232b..7bcdaf310a 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.1R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.1R/errata.sgml @@ -55,19 +55,19 @@ Fix: The problem here is that though the compatibility a.out libraries directly) to re-install the failing package(s). -o Kernel change information is not saved in the new kernel, even +o Kernel change information is not saved in the new kernel, even though this is claimed to work in the docs. -Fix: The change information is being written out, in fact, but to the +Fix: The change information is being written out, in fact, but to the wrong location. move /kernel.config to /boot/kernel.conf (if it - exists, otherwise there were no changes to save) and add the + exists, otherwise there were no changes to save) and add the following lines to /boot/loader.rc: - + load /kernel load -t userconfig_script /boot/kernel.conf autoboot 5 - + This will cause the kernel change information to be read in and used properly (and you just learned a little about the new 3-stage loader in the process, so the exercise wasn't a total loss). @@ -78,7 +78,7 @@ o DOS installation fails when you actually follow the instructions Fix: The instructions are correct but the code was wrong in 3.1-RELEASE, - sysinstall looking instead directly under C:\ (e.g. C:\BIN\...) + sysinstall looking instead directly under C:\ (e.g. C:\BIN\...) or under C:\RELEASES\ (C:\RELEASES\BIN\... and so on). Fixed in 3.1-STABLE. diff --git a/en_US.ISO8859-1/htdocs/releases/3.1R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/3.1R/notes.sgml index b74afb9577..6c58a97e2c 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.1R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.1R/notes.sgml @@ -68,7 +68,7 @@ Added driver support for Lite-On PNIC-based fast ethernet cards including the LinkSys LNE100TX, NetGear FA310TX Rev. D1 and Matrox FastNIC 10/100. -Added driver support for fast ethernet adapters based on the +Added driver support for fast ethernet adapters based on the Macronix 98713, 98713A, 98715, 98715A and 98725 chips. Added driver support for fast ethernet adapters based on the @@ -118,7 +118,7 @@ constructs that make maintenance easier. Support for PAM (Pluggable Authentication Modules) including modules for radius, TACACS, S/Key, Kerberos, Unix (passwd) and other authentication methods. - + Sendmail upgraded to version 8.9.2. AMD, texinfo, global and many other various utilities updated. @@ -210,7 +210,7 @@ NOT YET supported under the new CAM SCSI subsystem: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -430,7 +430,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your diff --git a/en_US.ISO8859-1/htdocs/releases/3.2R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/3.2R/errata.sgml index 4d77881992..e972a09300 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.2R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.2R/errata.sgml @@ -41,7 +41,7 @@ Current active security advisories for 3.2: None /usr/lib/compat. The compat20/compat21 distributions are a.out libraries, thus they should live in /usr/lib/compat/aout to match the "ldconfig_paths_aout" configuration in /etc/defaults/rc.conf. - + Fix: cd /usr/lib/compat mkdir -p aout mv lib*.so.*.* aout @@ -52,24 +52,24 @@ Fix: This was corrected in revision 1.3.2.2 of solib.c. Obtain the fixed version via CVSup (see instructions in handbook) or apply the patch from our CVSweb service. -o While booting the install floppy, user sees the following message +o While booting the install floppy, user sees the following message and nothing seems to happen, nor can anything be entered from the keyboard: - + Keyboard: no -Fix: Due to a lack of space, full support for old XT/AT (84-key) keyboards +Fix: Due to a lack of space, full support for old XT/AT (84-key) keyboards is no longer available in the bootblocks. Some notebook computers may - also have this type of keyboard and if you are still using this kind of + also have this type of keyboard and if you are still using this kind of hardware, you will see the above message about no keyboard being found when you boot from an installation CD-ROM or floppy. - + As soon as you see the message, hit the space bar and you will see the following prompt: - + >> FreeBSD/i386 BOOT - Default: x:xx(x,x)/boot/loader + Default: x:xx(x,x)/boot/loader boot: - + Then enter `-Dh', and things should proceed normally with your keyboard type. This only happens once at initial installation time and will not be a problem afterwards. diff --git a/en_US.ISO8859-1/htdocs/releases/3.2R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/3.2R/notes.sgml index 3e339b28d9..7c985f4db5 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.2R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.2R/notes.sgml @@ -87,14 +87,14 @@ Ports that use the devstat interface include xsysinfo and xperfmon. 1.2. SECURITY FIXES ------------------- Descriptor leak bug which was potentially open to a denial of service attack -(by local users) was closed. REF: KKIS.05051999.003b +(by local users) was closed. REF: KKIS.05051999.003b 1.3. USERLAND CHANGES --------------------- -The Internet Software Consortium's DHCP client has been added to the +The Internet Software Consortium's DHCP client has been added to the base system. - + Sendmail upgraded to version 8.9.3. Tar now supports compressing via bzip2 with the new @@ -213,7 +213,7 @@ NOT YET supported under the new CAM SCSI subsystem: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -446,7 +446,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. 3.2. CDROM diff --git a/en_US.ISO8859-1/htdocs/releases/3.3R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/3.3R/errata.sgml index 66a895bf19..2b5a30a614 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.3R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.3R/errata.sgml @@ -38,7 +38,7 @@ Current active security advisories for 3.3: None ---- System Update Information: The fvwm desktop choice in the X Desktops menu doesn't work. - + Fix: Install fvwm from /usr/ports/x11-wm/fvwm2 instead of using the desktop menu item and put "fvwm" in your $HOME/.xinitrc and $HOME/.xsession files for use by startx/xdm. You can also build @@ -70,7 +70,7 @@ Fix: Either install using boot floppies (see floppies/README.TXT) you have the "old" or new image - some mirrors may be slow in picking up the uncompressed and gzipped versions of the ISO 9660 installation image. As always, Walnut Creek CDROM will also provide - replacement CDs (once they become available) on request to purchasers + replacement CDs (once they become available) on request to purchasers of the 3.3-RELEASE product. This problem was caused by a bug in mkisofs which we're still @@ -107,7 +107,7 @@ diff -u -r1.77.2.8 -r1.77.2.9 + + if (!sc->initialized) + return; - + switch (state) { case PMST_SUSPEND: diff --git a/en_US.ISO8859-1/htdocs/releases/3.3R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/3.3R/notes.sgml index aeb59f74c1..f1f41e0e93 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.3R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.3R/notes.sgml @@ -254,7 +254,7 @@ NOT YET supported under the new CAM SCSI subsystem: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -347,7 +347,7 @@ SysKonnect SK-984x PCI gigabit Ethernet cards including the following: SK-9842 1000baseSX multi-mode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multi-mode fiber, dual port - + Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP @@ -518,7 +518,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your diff --git a/en_US.ISO8859-1/htdocs/releases/3.4R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/3.4R/announce.sgml index aa48325d07..54ad2f66bd 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.4R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.4R/announce.sgml @@ -15,7 +15,7 @@

                    Date: Mon, 20 Dec 1999 10:45:47 -0800
                    From: "Jordan K. Hubbard" <jkh@freebsd.org>
                    Subject:FreeBSD 3.4-RELEASE is now available.

                    - +

                    Just in under the wire for the current millenium, I'm happy to announce the availability of FreeBSD 3.4-RELEASE, the very latest in 3.x-STABLE branch technology. Following the release of FreeBSD 3.3 in Sept, 1999, @@ -33,7 +33,7 @@ (3.4-RELEASE for the Alpha architecture is available from the FTP site and will also be available on CDROM several weeks after the x86 product is released).

                    - +

                    NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project! We are also continuing our new tradition (started with 3.3-RELEASE) of making disc #1 from Walnut Creek CDROM's @@ -53,25 +53,25 @@

                    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.4-install.iso

                    - +

                    along with the more traditional 3.4-RELEASE bits. If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from Walnut Creek CDROM.

                    - +

                    The official FTP distribution site for FreeBSD is:

                    ftp://ftp.FreeBSD.org/pub/FreeBSD/
                    - +

                    Or via the WEB pages at:

                    http://www.FreeBSDMall.com/ and
                    http://www.cdrom.com
                    - +

                    And directly from Walnut Creek CDROM:

                    Walnut Creek CDROM
                    @@ -82,7 +82,7 @@ Tech Support: +1 925 603-1234
                    Email: info@cdrom.com
                    WWW: http://www.cdrom.com/
                    - +

                    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, @@ -96,7 +96,7 @@ mirror(s) first by going to:

                    ftp://ftp.<yourdomain>.freebsd.org/pub/FreeBSD

                    - +

                    Any additional mirror sites will be labeled ftp2, ftp3 and so on.

                    The latest versions of export-restricted code for FreeBSD (2.0C or @@ -114,7 +114,7 @@

                    Finland

                    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

                    - +

                    Thanks!

                    - Jordan

                    diff --git a/en_US.ISO8859-1/htdocs/releases/3.4R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/3.4R/errata.sgml index f14010b38f..db4243ee2d 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.4R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.4R/errata.sgml @@ -22,12 +22,12 @@ problems which have already been found and fixed. This http://www.FreeBSD.org/releases/ - 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). + 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT + (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: @@ -55,7 +55,7 @@ Fix: Both the "Novice" and "Express" install paths still work and you can invoke the custom installation from the "Index" menu (Installation, Custom) along with the Configuration option. You can also just download a fixed mfsroot.flp floppy image (or boot.flp - if you need 2.88MB boot media) from the following URL: + if you need 2.88MB boot media) from the following URL: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.4-RELEASE/floppies/updates/ diff --git a/en_US.ISO8859-1/htdocs/releases/3.4R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/3.4R/notes.sgml index a28e226fef..0a23c83550 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.4R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.4R/notes.sgml @@ -202,7 +202,7 @@ The following CD-ROM type systems are supported at this time: The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -212,8 +212,8 @@ NOT YET supported under the new CAM SCSI subsystem: WD7000 SCSI controller. - [ Note: There is work-in-progress to port the UltraStor driver to - the new CAM SCSI framework, but no estimates on when or if it will + [ Note: There is work-in-progress to port the UltraStor driver to + the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: @@ -296,7 +296,7 @@ SysKonnect SK-984x PCI gigabit Ethernet cards including the following: SK-9842 1000baseSX multi-mode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multi-mode fiber, dual port - + Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP @@ -465,7 +465,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your diff --git a/en_US.ISO8859-1/htdocs/releases/3.5R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/3.5R/announce.sgml index c84a168edb..9e97cabc96 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.5R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.5R/announce.sgml @@ -15,7 +15,7 @@

                    Date: Sat, 24 Jun 2000 18:23:01 -0700
                    From: "Jordan K. Hubbard" <jkh@freebsd.org>
                    Subject:FreeBSD 3.5 now available for x86

                    - +

                    I'm pleased to announce the availability of FreeBSD 3.5-RELEASE, the very LAST in 3.x-STABLE branch technology. Following the release of FreeBSD 3.4 in December, 1999, many bugs were fixed, important @@ -31,31 +31,31 @@ from where it will be shipping soon on a 4 CD set containing installation bits for x86 architecture, as well as a lot of other material of general interest to programmers and end-users alike

                    - +

                    We can't promise that all the mirror sites will carry the rather large installation (660MB) image, but it will at least be available from:

                    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.5-install.iso

                    - +

                    along with the more traditional 3.5-RELEASE bits. If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi.

                    - +

                    The official FTP distribution site for FreeBSD is:

                    ftp://ftp.FreeBSD.org/pub/FreeBSD/
                    - +

                    Or via the WEB pages at:

                    http://www.FreeBSDMall.com/ and
                    http://www.freebsd.org
                    - +

                    And directly from BSDi:

                    BSDi
                    @@ -65,7 +65,7 @@ Fax: +1 925 674-0821
                    Email: info@cdrom.com
                    WWW: http://www.cdrom.com/
                    - +

                    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Elbonia, Estonia, Finland, France, @@ -79,7 +79,7 @@ mirror(s) first by going to:

                    ftp://ftp.<yourdomain>.freebsd.org/pub/FreeBSD

                    - +

                    Any additional mirror sites will be labeled ftp2, ftp3 and so on.

                    The latest versions of export-restricted code for FreeBSD (2.0C or @@ -97,7 +97,7 @@

                    Finland

                    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

                    - +

                    Thanks!

                    - Jordan

                    diff --git a/en_US.ISO8859-1/htdocs/releases/3.5R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/3.5R/errata.sgml index 1447064b00..748403f900 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.5R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.5R/errata.sgml @@ -22,12 +22,12 @@ problems which have already been found and fixed. This http://www.FreeBSD.org/releases/ - 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). + 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT + (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: diff --git a/en_US.ISO8859-1/htdocs/releases/3.5R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/3.5R/notes.sgml index 2c29a62d24..fc0f4dc673 100644 --- a/en_US.ISO8859-1/htdocs/releases/3.5R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/3.5R/notes.sgml @@ -220,7 +220,7 @@ The following CD-ROM type systems are supported at this time: The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -230,8 +230,8 @@ NOT YET supported under the new CAM SCSI subsystem: WD7000 SCSI controller. - [ Note: There is work-in-progress to port the UltraStor driver to - the new CAM SCSI framework, but no estimates on when or if it will + [ Note: There is work-in-progress to port the UltraStor driver to + the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: @@ -314,7 +314,7 @@ SysKonnect SK-984x PCI gigabit Ethernet cards including the following: SK-9842 1000baseSX multi-mode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multi-mode fiber, dual port - + Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP @@ -483,7 +483,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your diff --git a/en_US.ISO8859-1/htdocs/releases/4.0R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/4.0R/announce.sgml index 7374848f14..6afb33c8fe 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.0R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.0R/announce.sgml @@ -61,7 +61,7 @@

                    http://www.freebsdmall.com/
                    http://www.wccdrom.com/

                    - +

                    And directly from Walnut Creek CDROM:

                    @@ -74,7 +74,7 @@
   Email: info@wccdrom.com
   WWW: http://www.wccdrom.com/
                    - +

                    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, @@ -88,7 +88,7 @@ mirror(s) first by going to:

                    ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

                    - +

                    Any additional mirror sites will be labeled ftp2, ftp3 and so on.

                    The latest versions of export-restricted code for FreeBSD (2.0C or diff --git a/en_US.ISO8859-1/htdocs/releases/4.0R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/4.0R/errata.sgml index e2e0f9ffbc..adc9c8975c 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.0R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.0R/errata.sgml @@ -22,12 +22,12 @@ problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of -the errata are located at: +the errata are located at: 1. http://www.FreeBSD.org/releases/ - 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). + 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT + (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: diff --git a/en_US.ISO8859-1/htdocs/releases/4.0R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/4.0R/notes.sgml index 969cd91a90..a4ceadf484 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.0R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.0R/notes.sgml @@ -64,7 +64,7 @@ specifically marked as [MERGED] features. NFS has been immensely improved with bug fixes and performance tuning. -Support for more than 32 signals has been added. +Support for more than 32 signals has been added. POSIX 1003.1 conformant SA_SIGINFO signal handlers are now supported. SIGFPE signal handlers (both SA_SIGINFO and traditional BSD handlers) @@ -78,7 +78,7 @@ Jail(8) aware sysctl(8) variables have been added for Linux mode. A large number of bug fixes and performance improvements have been made to the VM system, including and most especially to mmap() and -related functions. The MAP_NOSYNC option has been added to better support +related functions. The MAP_NOSYNC option has been added to better support the use of shared files as an IPC mechanism. The VM system's swapper has been completely rewritten and performance has been greatly enhanced, especially when swapping over NFS. @@ -95,13 +95,13 @@ A new ATA/ATAPI driver has been implemented. The aim of this new subsystem is to maximise performance on modern ATA/ATAPI based systems. The "ata" driver supports all major chipsets including those used on PCI card based controllers like the Promise and the -Abit/SIIG. There is support for busmaster DMA transfers upto and +Abit/SIIG. There is support for busmaster DMA transfers upto and including the new ATA/66 mode. The 'ata' driver automatically setup the hardware for the maximum possible transfer mode to maximise system throughput. Supported devices are all ATA compliant -disks and ATAPI CDROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, LS120, ZIP -and tape drives. The ata driver also support PCCARD ATA devices. -The 'ata' driver also sports error handling and timeout code, to +disks and ATAPI CDROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, LS120, ZIP +and tape drives. The ata driver also support PCCARD ATA devices. +The 'ata' driver also sports error handling and timeout code, to avoid the problems of "hung" ATA/ATAPI devices. A new utility 'burncd' has been written to facilitate easy control @@ -114,7 +114,7 @@ the Alteon AceNIC, 3Com 3c985 and Netgear GA620. [MERGED] Driver support has been added for IEEE 802.11 PCMCIA wireless network adapters based on the Lucent Hermes chipset, including the Lucent -WaveLAN/IEEE 802.11, the Cabletron RoamAbout and Melco Aireconnect. +WaveLAN/IEEE 802.11, the Cabletron RoamAbout and Melco Aireconnect. Both 2Mbps and 6Mbps Turbo adapters are supported. [MERGED] Driver support has been added for PCI fast ethernet cards based @@ -303,7 +303,7 @@ The following applications have been updated to support IPv6: Many ports have been updated to support IPv6. See the 'ipv6' virtual ports category for a list. -Sysinstall enables PC-card controllers and pccardd(8) for PC-card +Sysinstall enables PC-card controllers and pccardd(8) for PC-card installation media. @@ -400,7 +400,7 @@ The following CD-ROM type systems are supported at this time: The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -410,8 +410,8 @@ NOT YET supported under the new CAM SCSI subsystem: WD7000 SCSI controller. - [ Note: There is work-in-progress to port the UltraStor driver to - the new CAM SCSI framework, but no estimates on when or if it will + [ Note: There is work-in-progress to port the UltraStor driver to + the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: @@ -570,7 +570,7 @@ Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C507 Etherlink 16/TP -3Com 3C509, 3C529 (MCA), 3C579, +3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL @@ -700,9 +700,9 @@ Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes -(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco -Airconnect). Note: the ISA versions of these adapters are actually PCMCIA -cards combined with an ISA to PCMCIA bridge card, so both kinds of +(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco +Airconnect). Note: the ISA versions of these adapters are actually PCMCIA +cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, @@ -724,7 +724,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your diff --git a/en_US.ISO8859-1/htdocs/releases/4.1.1R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/4.1.1R/errata.sgml index 613a02a370..cd2cfe23d1 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.1.1R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.1.1R/errata.sgml @@ -22,12 +22,12 @@ problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of -the errata are located at: +the errata are located at: 1. http://www.FreeBSD.org/releases/ - 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). + 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT + (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: diff --git a/en_US.ISO8859-1/htdocs/releases/4.1.1R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/4.1.1R/notes.sgml index 3f173c3200..ca19855b11 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.1.1R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.1.1R/notes.sgml @@ -60,7 +60,7 @@ Table of contents: 1.1. KERNEL CHANGES ------------------- -The tap driver, a virtual Ethernet device driver for bridged +The tap driver, a virtual Ethernet device driver for bridged configurations, has been added. accept_filters, a kernel feature to reduce overheads when accepting @@ -72,7 +72,7 @@ when they are mmap(2)ed. The ata(4) driver now has support for ATA100 controllers. -The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit +The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit Ethernet and Netgear GA620T 1000baseT Gigabit Ethernet cards. The ng_bridge(4) node type has been added to the netgraph subsystem. @@ -101,7 +101,7 @@ of files, has been added. syslogd(8) can take a -n option to disable DNS queries for every request. -kenv(1), a command to dump the kernel environment, has been added. +kenv(1), a command to dump the kernel environment, has been added. The behavior of periodic(8) is now controlled by /etc/defaults/periodic.conf and /etc/periodic.conf. @@ -136,9 +136,9 @@ Binutils have been upgraded to 2.10.0. libreadline has been upgraded to 4.1. -The ifconfig(8) command can set the link-layer address of an interface. +The ifconfig(8) command can set the link-layer address of an interface. -bktr(4) driver update to 2.1.5. New tuner types have been added, +bktr(4) driver update to 2.1.5. New tuner types have been added, and improvememts to the KLD module and to memory allocation have been made. @@ -199,7 +199,7 @@ The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F Microchannel (MCA) bus adapters are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and -SmartRAID IV SCSI/RAID controllers are supported. +SmartRAID IV SCSI/RAID controllers are supported. DPT SmartRAID V/VI and Adaptec SCSI RAID 2100, 3200, and 3400 cards are supported. @@ -219,7 +219,7 @@ AMI MegaRAID Express and Enterprise family RAID controllers: Some HP NetRAID controllers are OEM versions of AMI designs, and these are also supported. Booting from these controllers is supported. -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x +Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware: DAC960P DAC960PD @@ -230,7 +230,7 @@ firmware: AcceleRAID 150 AcceleRAID 250 eXtremeRAID 1100 -Booting from these controllers is supported. EISA adapters are not +Booting from these controllers is supported. EISA adapters are not supported. 3ware Escalade ATA RAID controllers. All members of the 5000 and @@ -270,7 +270,7 @@ The following CD-ROM type systems are supported at this time: The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -280,8 +280,8 @@ NOT YET supported under the new CAM SCSI subsystem: WD7000 SCSI controller. - [ Note: There is work-in-progress to port the UltraStor driver to - the new CAM SCSI framework, but no estimates on when or if it will + [ Note: There is work-in-progress to port the UltraStor driver to + the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: @@ -442,7 +442,7 @@ Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C507 Etherlink 16/TP -3Com 3C509, 3C529 (MCA), 3C579, +3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI, 3C556/556B MiniPCI, @@ -579,9 +579,9 @@ Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes -(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco -Airconnect). Note: the ISA versions of these adapters are actually PCMCIA -cards combined with an ISA to PCMCIA bridge card, so both kinds of +(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco +Airconnect). Note: the ISA versions of these adapters are actually PCMCIA +cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, @@ -603,7 +603,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your diff --git a/en_US.ISO8859-1/htdocs/releases/4.1R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/4.1R/errata.sgml index a43da4bb1f..b06c1981f9 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.1R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.1R/errata.sgml @@ -22,12 +22,12 @@ problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of -the errata are located at: +the errata are located at: 1. http://www.FreeBSD.org/releases/ - 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). + 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT + (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: diff --git a/en_US.ISO8859-1/htdocs/releases/4.1R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/4.1R/notes.sgml index f5b0c2f986..515ced6dbe 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.1R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.1R/notes.sgml @@ -105,7 +105,7 @@ versions are not supported. This allow network booting using DHCP. For the alpha release of FreeBSD, the following specifics also apply: - FreeBSD/alpha now posseses a loader with FICL (Forth support) builtin. + FreeBSD/alpha now posseses a loader with FICL (Forth support) builtin. Parallel ports are now supported. @@ -113,13 +113,13 @@ apply: check HARDWARE.TXT for details. AlphaServer 4100 (Rawhide) does not want to allow installation using - floppies or cdrom. Workaround is to install using another Alpha machine and + floppies or cdrom. Workaround is to install using another Alpha machine and move the disk to the AS4100. Once installed FreeBSD runs fine. AlphaServer 2100A (Lynx) is not supported in this release. Note that AlphaServer 2100 (Sable) works fine. - Machines that have onboard IDE interfaces that their SRM can boot from + Machines that have onboard IDE interfaces that their SRM can boot from are now supported with the IDE disk being the root/boot device. See HARDWARE.TXT for machine specifics like speed, use of DMA etc. @@ -267,7 +267,7 @@ AMI MegaRAID Express and Enterprise family RAID controllers: Some HP NetRAID controllers are OEM versions of AMI designs, and these are also supported. Booting from these controllers is supported. -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x +Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware: DAC960P DAC960PD @@ -278,7 +278,7 @@ firmware: AcceleRAID 150 AcceleRAID 250 eXtremeRAID 1100 -Booting from these controllers is supported. EISA adapters are not +Booting from these controllers is supported. EISA adapters are not supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, @@ -315,7 +315,7 @@ The following CD-ROM type systems are supported at this time: The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -325,8 +325,8 @@ NOT YET supported under the new CAM SCSI subsystem: WD7000 SCSI controller. - [ Note: There is work-in-progress to port the UltraStor driver to - the new CAM SCSI framework, but no estimates on when or if it will + [ Note: There is work-in-progress to port the UltraStor driver to + the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: @@ -484,7 +484,7 @@ Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C507 Etherlink 16/TP -3Com 3C509, 3C529 (MCA), 3C579, +3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL @@ -620,9 +620,9 @@ Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes -(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco -Airconnect). Note: the ISA versions of these adapters are actually PCMCIA -cards combined with an ISA to PCMCIA bridge card, so both kinds of +(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco +Airconnect). Note: the ISA versions of these adapters are actually PCMCIA +cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, @@ -644,7 +644,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. 3.2. CDROM diff --git a/en_US.ISO8859-1/htdocs/releases/4.2R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/4.2R/errata.sgml index c1df3fe57a..023fd9080c 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.2R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.2R/errata.sgml @@ -22,12 +22,12 @@ problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of -the errata are located at: +the errata are located at: 1. http://www.FreeBSD.org/releases/ - 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). + 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT + (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: diff --git a/en_US.ISO8859-1/htdocs/releases/4.2R/notes.sgml b/en_US.ISO8859-1/htdocs/releases/4.2R/notes.sgml index 0c626914cf..4c5d0462a4 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.2R/notes.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.2R/notes.sgml @@ -113,7 +113,7 @@ set to the cache size in kilobytes. The old options are still supported for backwards compatibility. The NCPU, NAPIC, NBUS, and NINTR kernel configuration options, -for configuring SMP kernels, have been removed. NCPU is now set to a +for configuring SMP kernels, have been removed. NCPU is now set to a maximum of 16, and the other, aforementioned options are now dynamic. The ahc(4) driver has been updated. @@ -170,7 +170,7 @@ possibility of buffer overflow-related exploits. A security hole in Linux emulation was fixed (see security advisory FreeBSD-SA-00:42). [4.1.1] -TCP now uses stronger randomness in choosing its initial sequence +TCP now uses stronger randomness in choosing its initial sequence numbers (see security advisory FreeBSD-SA-00:52). A bug in finger(1) that could allow remote users to view @@ -210,9 +210,9 @@ weeks before the patent was due to expire). As a result, the native OpenSSL implementation of the RSA algorithm is now activated by default, and the rsaref port and librsaUSA are no longer required for USA residents. [4.1.1] - + sshd is now enabled by default on new installs. [4.1.1] - + Version numbers of installed packages have a new (backward-compatible) syntax, which supports the "PORTREVISION" and "PORTEPOCH" variables in ports collection makefiles. These changes help keep track of changes @@ -279,18 +279,18 @@ kenv(1), a command to dump the kernel environment, has been added. The behavior of periodic(8) is now controlled by /etc/defaults/periodic.conf and /etc/periodic.conf. [4.1.1] - + logger(1) can now send messages directly to a remote syslog. [4.1.1] - + OpenSSL has been upgraded to 0.9.5a, which includes numerous bugfixes and enhancements. [4.1.1] - + finger(1) now has the ability to support fingering aliases, via the finger.conf(5) file. [4.1.1] - + The xl(4) driver now supports the 3Com 3C556 and 3C556B MiniPCI adapters used on some laptops. [4.1.1] - + killall(1) is now a C program, rather than a Perl script. As a result, killall's -m option now uses the regular expression syntax of regex(3), rather than that of perl(1). [4.1.1] @@ -419,7 +419,7 @@ AMI MegaRAID Express and Enterprise family RAID controllers: Some HP NetRAID controllers are OEM versions of AMI designs, and these are also supported. Booting from these controllers is supported. -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x +Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware: DAC960P DAC960PD @@ -430,7 +430,7 @@ firmware: AcceleRAID 150 AcceleRAID 250 eXtremeRAID 1100 -Booting from these controllers is supported. EISA adapters are not +Booting from these controllers is supported. EISA adapters are not supported. Mylex PCI to SCSI RAID controllers with 6.x firmware: @@ -499,7 +499,7 @@ The following CD-ROM type systems are supported at this time: The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. + NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. @@ -509,8 +509,8 @@ NOT YET supported under the new CAM SCSI subsystem: WD7000 SCSI controller. - [ Note: There is work-in-progress to port the UltraStor driver to - the new CAM SCSI framework, but no estimates on when or if it will + [ Note: There is work-in-progress to port the UltraStor driver to + the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: @@ -544,7 +544,7 @@ chipsets, including the following: Silicon Graphics Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) -AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, +AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA. SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, @@ -681,7 +681,7 @@ Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C507 Etherlink 16/TP -3Com 3C509, 3C529 (MCA), 3C579, +3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI, 3C556/556B MiniPCI, @@ -882,7 +882,7 @@ You can ftp FreeBSD and any or all of its optional packages from For other locations that mirror the FreeBSD software see the file MIRROR.SITES. Please ftp the distribution from the site closest (in networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to +Contact freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. 3.2. CDROM diff --git a/en_US.ISO8859-1/htdocs/releases/4.3R/errata.sgml b/en_US.ISO8859-1/htdocs/releases/4.3R/errata.sgml index b8a8b48f55..2553f08874 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.3R/errata.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.3R/errata.sgml @@ -22,12 +22,12 @@ problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of -the errata are located at: +the errata are located at: 1. http://www.FreeBSD.org/releases/ - 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). + 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT + (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: @@ -60,8 +60,8 @@ A remote buffer overflow in tcpdump(1) could be triggered by sending certain packets at a target machine. More details, as well as a fix, can be found in security advisory FreeBSD-SA-01:48. -A remote buffer overflow in telnetd(8) could result in arbitrary code -running on a target machine. More details, as well as a fix, can be +A remote buffer overflow in telnetd(8) could result in arbitrary code +running on a target machine. More details, as well as a fix, can be found in security advisory FreeBSD-SA-01:49. A vulnerability whereby a remote attacker could exhaust a target's diff --git a/en_US.ISO8859-1/htdocs/releases/4.5R/qa.sgml b/en_US.ISO8859-1/htdocs/releases/4.5R/qa.sgml index 802f4ca5ac..a3d235c557 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.5R/qa.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.5R/qa.sgml @@ -55,28 +55,28 @@ On the other hand, Yahoo! is now deploying this code, and that should help test it a great deal.

                    • - +
                  • VFS/VM/NFS fixes. We need to continue to test performance, correctness, and interoperability. In particular, I'd like to see a lot of inter-platform performance testing (FreeBSD->Solaris, vice versa, etc). We'd also like careful investigation of low-memory situations.

                    • - +
                  • FFS fixes. We had some reports of deadlocks in FFS; it sounds like Matt Dillon has caught most of them, but combinations I'd particular - like to see tested involve Quotas, Chroot, and NFS, under load, and + like to see tested involve Quotas, Chroot, and NFS, under load, and involving memory mapping and heavy directory operations.

                  • NTP 4.1. This is probably reasonable safe, but it doesn't hurt to do interop testing, especially on the Alpha platform.

                    • - +
                  • SMBfs. We need stability testing, mostly, I suspect. Performance is probably not a large focus. While SMBfs support has been available on - -STABLE through a port previously, determining that the integration + -STABLE through a port previously, determining that the integration with the base system (especially the boot process) was done correctly is important. Attempting to use SMBfs in /etc/fstab in a diskless environment might be one thing to explore, for example.

                    • - +
                  • Once the man page change goes in (which I think it should) we'll want some basic testing of the man command. Update: This change proved too controversial for introduction this late in diff --git a/en_US.ISO8859-1/htdocs/releases/4.5R/schedule.sgml b/en_US.ISO8859-1/htdocs/releases/4.5R/schedule.sgml index b6c8cd8e35..c61aa171ea 100644 --- a/en_US.ISO8859-1/htdocs/releases/4.5R/schedule.sgml +++ b/en_US.ISO8859-1/htdocs/releases/4.5R/schedule.sgml @@ -111,7 +111,7 @@ site administrators have frequently requested advance notice for new ISOs. - + First release candidate 09 Jan 2002 diff --git a/en_US.ISO8859-1/htdocs/releases/5.5R/todo.sgml b/en_US.ISO8859-1/htdocs/releases/5.5R/todo.sgml index a3e1f89fba..4c60cd3125 100644 --- a/en_US.ISO8859-1/htdocs/releases/5.5R/todo.sgml +++ b/en_US.ISO8859-1/htdocs/releases/5.5R/todo.sgml @@ -48,7 +48,7 @@
                  • Documentation Items
                  • Testing foci
                  - +

                  Show stopper defects for &local.rel;-RELEASE

                  diff --git a/en_US.ISO8859-1/htdocs/releases/6.0R/stress.xsl b/en_US.ISO8859-1/htdocs/releases/6.0R/stress.xsl index aa89681763..1c1f042416 100644 --- a/en_US.ISO8859-1/htdocs/releases/6.0R/stress.xsl +++ b/en_US.ISO8859-1/htdocs/releases/6.0R/stress.xsl @@ -6,7 +6,7 @@ xmlns="http://www.w3.org/1999/xhtml" exclude-result-prefixes="rdf" version="1.0"> - diff --git a/en_US.ISO8859-1/htdocs/releases/6.0R/todo.sgml b/en_US.ISO8859-1/htdocs/releases/6.0R/todo.sgml index 74d6dc2099..f532442bb7 100644 --- a/en_US.ISO8859-1/htdocs/releases/6.0R/todo.sgml +++ b/en_US.ISO8859-1/htdocs/releases/6.0R/todo.sgml @@ -49,7 +49,7 @@
                • Testing foci
                • Problems Discovered by Kernel Stress Test Suite
                - +

                Show stopper defects for 6.0-RELEASE

                diff --git a/en_US.ISO8859-1/htdocs/releases/6.1R/stress.xsl b/en_US.ISO8859-1/htdocs/releases/6.1R/stress.xsl index aa89681763..1c1f042416 100644 --- a/en_US.ISO8859-1/htdocs/releases/6.1R/stress.xsl +++ b/en_US.ISO8859-1/htdocs/releases/6.1R/stress.xsl @@ -6,7 +6,7 @@ xmlns="http://www.w3.org/1999/xhtml" exclude-result-prefixes="rdf" version="1.0"> - diff --git a/en_US.ISO8859-1/htdocs/releases/6.2R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/6.2R/announce.sgml index 86f3c3bdb4..e2571ee15f 100644 --- a/en_US.ISO8859-1/htdocs/releases/6.2R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/6.2R/announce.sgml @@ -123,7 +123,7 @@ Korea, Latvia, Lithuania, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom.

                -

                Before trying the central FTP site, please check your regional +

                Before trying the central FTP site, please check your regional mirror(s) first by going to:

                ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

                diff --git a/en_US.ISO8859-1/htdocs/releases/6.2R/stress.xsl b/en_US.ISO8859-1/htdocs/releases/6.2R/stress.xsl index aa89681763..1c1f042416 100644 --- a/en_US.ISO8859-1/htdocs/releases/6.2R/stress.xsl +++ b/en_US.ISO8859-1/htdocs/releases/6.2R/stress.xsl @@ -6,7 +6,7 @@ xmlns="http://www.w3.org/1999/xhtml" exclude-result-prefixes="rdf" version="1.0"> - diff --git a/en_US.ISO8859-1/htdocs/releases/6.3R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/6.3R/announce.sgml index f321f4dcc3..223f706ff9 100644 --- a/en_US.ISO8859-1/htdocs/releases/6.3R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/6.3R/announce.sgml @@ -101,7 +101,7 @@ The primary mirror site is:

                ftp://ftp.freebsd.org/pub/FreeBSD/

                -

                However, before trying the central FTP site, please check your regional +

                However, before trying the central FTP site, please check your regional mirror(s) first by going to:

                ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

                @@ -135,7 +135,7 @@ recommended.

                # fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz.asc

                # gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz

                - + The new freebsd-update(8) can then be extracted and run as follows:

                # tar -xf freebsd-update-upgrade.tgz

                @@ -264,7 +264,7 @@ MD5 (6.3-RELEASE-alpha-disc1.iso) = 4a5fd2fd27f966b3b65717ee79d0bf09 MD5 (6.3-RELEASE-alpha-disc2.iso) = c1d05f366160f1a7b760cd92b2368158 MD5 (6.3-RELEASE-alpha-disc3.iso) = aa3884eec1b62fba1c2f407ed5568d52 MD5 (6.3-RELEASE-alpha-docs.iso) = c8f663a537e62668e7f26d4ba262d879 - + MD5 (6.3-RELEASE-amd64-bootonly.iso) = 5ded1d6f91da4d872aef8c2ddba24dde MD5 (6.3-RELEASE-amd64-disc1.iso) = a8d41ea26769919db6c0c672fa8f8c4f MD5 (6.3-RELEASE-amd64-disc2.iso) = a243076fb99b011d9b0771a6f7f9a977 @@ -297,7 +297,7 @@ SHA256 (6.3-RELEASE-amd64-disc1.iso) = 6ee1c2f00f8a1bc9d38b04b058b0549df9904ded5 SHA256 (6.3-RELEASE-amd64-disc2.iso) = f69e3ab103f4be34fea7b9dde4a34d5279948b4539dfe88c53e6b371d7962301 SHA256 (6.3-RELEASE-amd64-disc3.iso) = cf6820b81eb1a1705d6294eb0bfa884bb6bad88c3be0e94c895283235c675abd SHA256 (6.3-RELEASE-amd64-docs.iso) = 1b7d78bb94902f15609c60332d4cfc534479ade5f5f72b9e52fc61ce48410cc4 - + SHA256 (6.3-RELEASE-i386-bootonly.iso) = 124c340c1c54dc3f29c8d77e321205d47eec682bc147384dabe3fa2ae9e148f2 SHA256 (6.3-RELEASE-i386-disc1.iso) = 15081a56d184a18c7cc3a5c3cd0d7d5b7d9304c9cc1d5fc40d875b0fd3047721 SHA256 (6.3-RELEASE-i386-disc2.iso) = 7aabc815455f4ab80121071c5eb17c41dc355c2e45444b42a06158de4f9e482a diff --git a/en_US.ISO8859-1/htdocs/releases/7.0R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/7.0R/announce.sgml index c3eb86be97..87a87286a9 100644 --- a/en_US.ISO8859-1/htdocs/releases/7.0R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/7.0R/announce.sgml @@ -132,7 +132,7 @@ The primary mirror site is:

                ftp://ftp.freebsd.org/pub/FreeBSD/

                -

                However, before trying the central FTP site, please check your regional +

                However, before trying the central FTP site, please check your regional mirror(s) first by going to:

                ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

                @@ -191,7 +191,7 @@ recommended.

                # fetch http://people.freebsd.org/~cperciva/freebsd-update-upgrade.tgz.asc

                # gpg --verify freebsd-update-upgrade.tgz.asc freebsd-update-upgrade.tgz

                - + The new freebsd-update(8) can then be extracted and run as follows:

                # tar -xf freebsd-update-upgrade.tgz

                diff --git a/en_US.ISO8859-1/htdocs/releases/7.0R/stress.xsl b/en_US.ISO8859-1/htdocs/releases/7.0R/stress.xsl index 6cd842a659..a75d540c10 100644 --- a/en_US.ISO8859-1/htdocs/releases/7.0R/stress.xsl +++ b/en_US.ISO8859-1/htdocs/releases/7.0R/stress.xsl @@ -6,7 +6,7 @@ xmlns="http://www.w3.org/1999/xhtml" exclude-result-prefixes="rdf" version="1.0"> - diff --git a/en_US.ISO8859-1/htdocs/releases/7.1R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/7.1R/announce.sgml index 2491579584..35dcf8bac0 100644 --- a/en_US.ISO8859-1/htdocs/releases/7.1R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/7.1R/announce.sgml @@ -79,7 +79,7 @@ documentation, and supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.

                - +
                disc1, disc2, disc3, livefs, docs:

                disc1 contains the base FreeBSD system and a few pre-built packages. disc2 and disc3 contain diff --git a/en_US.ISO8859-1/htdocs/releases/7.4R/announce.sgml b/en_US.ISO8859-1/htdocs/releases/7.4R/announce.sgml index 17fc9dcc9d..beee831f71 100644 --- a/en_US.ISO8859-1/htdocs/releases/7.4R/announce.sgml +++ b/en_US.ISO8859-1/htdocs/releases/7.4R/announce.sgml @@ -199,7 +199,7 @@ before continuing.

                # shutdown -r now
                - +

                After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again:

                diff --git a/en_US.ISO8859-1/htdocs/releng/charter.sgml b/en_US.ISO8859-1/htdocs/releng/charter.sgml index 6d79a519c2..6da883f57f 100644 --- a/en_US.ISO8859-1/htdocs/releng/charter.sgml +++ b/en_US.ISO8859-1/htdocs/releng/charter.sgml @@ -19,18 +19,18 @@

                • Setting and publishing the release schedule for Official Project releases of FreeBSD.

                  • - +

                • Documenting and formalizing the RE procedures, so that the process can continually be reviewed and improved. This includes more documentation about the ports cluster and package split procedures.

                  • - +

                • Setting and publishing "Code Freeze" dates, and acting as a change-review committee to decide which changes may be made to a branch during a code freeze. This includes freezes for HEAD when approaching a .0 release as well as the traditional RELENG_* code freeze pending a -STABLE release.

                  • - +

                • Creation and maintenance of RELENG_* branches of the src/ tree. This include final authority over what commits are made (and remain in) the -STABLE branch prior to the @@ -40,7 +40,7 @@ set of guidelines that vendors must meet if they are to be allowed to call a product "FreeBSD", or an "Official FreeBSD release".

                  • - +

                • Testing and integrating required packages from the ports collection onto the official project release media. Portmgr@ is responsible for managing the ports/ code freeze and @@ -50,13 +50,13 @@ ultimately responsible for ensuring that all of the required packages are available on the FreeBSD release media, but portmgr@ cooperation is essential.

                  • - +

                • Coordinating with the FreeBSD Documentation Project, to ensure that a consistent set of documentation is provided for the release. This includes the ability to request that large disruptive changes not be made to the documentation set in the weeks leading up to a release.

                  • - +

                • Coordinating with the security officer team to ensure that pending FreeBSD releases are not affected by recently disclosed vulnerabilities. Also, approximately 1 week after a release, @@ -65,7 +65,7 @@ team. The exact transfer date is to be worked out by the two parties once it is clear that the release was a success. A heads up message should be sent to developers@ at that time.

                  • - +

                • Sending out messages to announce@FreeBSD.org on behalf of the project to announce new releases of FreeBSD.

                diff --git a/en_US.ISO8859-1/htdocs/relnotes.sgml b/en_US.ISO8859-1/htdocs/relnotes.sgml index da794e28cc..d7985c547a 100644 --- a/en_US.ISO8859-1/htdocs/relnotes.sgml +++ b/en_US.ISO8859-1/htdocs/relnotes.sgml @@ -12,9 +12,9 @@ - + BSD daemon reading documentation - +

                Each distribution of FreeBSD includes several documentation files describing the particular distribution (RELEASE, SNAPSHOTs, etc.). These files typically include:

                @@ -43,7 +43,7 @@

                RELEASE versions of FreeBSD

                The release documentation for each -RELEASE version of FreeBSD - (for example, &rel.current;-RELEASE) can be found on the + (for example, &rel.current;-RELEASE) can be found on the releases page of the FreeBSD Web site, as well as its mirrors.

                @@ -94,7 +94,7 @@
              • README
              • Release Notes
                • - +
              • Hardware Notes
              • Errata
                • diff --git a/en_US.ISO8859-1/htdocs/search/Makefile b/en_US.ISO8859-1/htdocs/search/Makefile index 68e5060ab2..634661661c 100644 --- a/en_US.ISO8859-1/htdocs/search/Makefile +++ b/en_US.ISO8859-1/htdocs/search/Makefile @@ -7,7 +7,7 @@ .include "../Makefile.inc" .endif -DOCS+= search.sgml +DOCS+= search.sgml DOCS+= searchhints.sgml DOCS+= search-mid.sgml diff --git a/en_US.ISO8859-1/htdocs/search/opensearch/Makefile b/en_US.ISO8859-1/htdocs/search/opensearch/Makefile index bfd6d3a7e8..074f6f9c10 100644 --- a/en_US.ISO8859-1/htdocs/search/opensearch/Makefile +++ b/en_US.ISO8859-1/htdocs/search/opensearch/Makefile @@ -7,7 +7,7 @@ .include "../Makefile.inc" .endif -DOCS+= opensearch.sgml +DOCS+= opensearch.sgml INDEXLINK= opensearch.html DATA= @@ -15,7 +15,7 @@ DATA+= opensearch.js DATA+= man.xml DATA+= man-freebsd-release-ports.xml -DATA+= ports.xml +DATA+= ports.xml DATA+= query-pr.xml DATA+= web.xml DATA+= web-all.xml diff --git a/en_US.ISO8859-1/htdocs/search/search.sgml b/en_US.ISO8859-1/htdocs/search/search.sgml index e5790ff497..2c18f76f22 100644 --- a/en_US.ISO8859-1/htdocs/search/search.sgml +++ b/en_US.ISO8859-1/htdocs/search/search.sgml @@ -61,7 +61,7 @@ - + @@ -98,7 +98,7 @@ list archive (note that this archive only carries messages from March 2003 onward).

                -

                The mailing lists (as well as many others) have also been archived by The mailing lists (as well as many others) have also been archived by MarkMail.

                @@ -248,19 +248,19 @@
                - - - @@ -278,115 +278,115 @@ - - - - - - - - - - - - - - - - - - - @@ -398,20 +398,20 @@ - - - @@ -429,7 +429,7 @@ - @@ -465,13 +465,13 @@ - - @@ -489,7 +489,7 @@ - @@ -501,19 +501,19 @@ - - - @@ -543,37 +543,37 @@ - - - - - - @@ -591,13 +591,13 @@ - - @@ -609,43 +609,43 @@ - - - - - - - @@ -657,7 +657,7 @@ - @@ -679,7 +679,7 @@
                ACPI ACPI and power management development
                Afs Porting and using AFS (the Andrew File System) from CMU/Transarc
                Alpha Porting FreeBSD to the DEC Alpha
                Arch Architecture and design discussions
                ARM Porting FreeBSD to the StrongArm
                ATM Using ATM networking with FreeBSD
                Audit Source code audit project
                Binup Design and development of the binary update system
                Bluetooth Discussion about FreeBSD support for Bluetooth
                Chromium FreeBSD-specific Chromium issues
                Bugbusters Coordination of the Problem Report handling effort
                Commit (all) All Changes made to all FreeBSD source trees
                Commit (doc) Changes made to the FreeBSD documents source tree
                Commit (ports) Changes made to the FreeBSD ports source tree
                Commit (projects) Changes made to the FreeBSD projects source tree
                Commit (src) Changes made to the FreeBSD main source tree
                Config Development of FreeBSD installation and configuration tools
                Current Use of FreeBSD-current sources
                CVSweb Technical discussions about use, development and maintenance of FreeBSD-CVSweb
                Database Discussing database use and development under FreeBSD
                Doc Discussions concerning documentation
                Drivers Writing device drivers for FreeBSD
                Emulation Emulating other systems on FreeBSD
                Firewire Design and implementation of a Firewire (aka IEEE 1394 aka iLink) subsystem for FreeBSD
                Fs Discussions concerning FreeBSD filesystems
                Hackers General technical discussions
                ISDN Development of ISDN support for FreeBSD
                &java; JDK porting and application development
                Multimedia Discussions about FreeBSD as a multimedia platform
                Mozilla Porting mozilla to FreeBSD
                Net Networking discussion and TCP/IP source code
                New Bus Technical discussions on Bus Architecture
                Platforms Cross-platform FreeBSD issues (non-Intel FreeBSD ports)
                Policy FreeBSD core team policy decisions
                Ports Bugs Bug reports concerning FreeBSD's ports collection
                Ports Discussions concerning FreeBSD's ports collection
                PPC Porting FreeBSD to the PowerPC
                Python FreeBSD-specific Python issues
                Realtime Development of realtime extensions to FreeBSD
                SCSI Discussions about FreeBSD's SCSI support
                SMP FreeBSD on multi-processor platforms
                SPARC64 Porting FreeBSD to the SPARC64
                Standards FreeBSD Conformance to the C99 and the &posix; standards
                Threads Discussion about threading models in FreeBSD, including KSE and others
                Tilera Porting FreeBSD to the Tilera family of CPUs
                Tokenring Support Token Ring in FreeBSD
                Toolchain Maintenance of FreeBSD's integrated toolchain
                VuXML Discussion on VuXML infrastructure
                - @@ -691,13 +691,13 @@ - - diff --git a/en_US.ISO8859-1/htdocs/smp/index.sgml b/en_US.ISO8859-1/htdocs/smp/index.sgml index 4182ecb5b9..6d598dd075 100644 --- a/en_US.ISO8859-1/htdocs/smp/index.sgml +++ b/en_US.ISO8859-1/htdocs/smp/index.sgml @@ -618,7 +618,7 @@ - + @@ -2603,7 +2603,7 @@

                • &a.grog; submitted a - FreeBSD SMPng paper + FreeBSD SMPng paper to the Asian Enterprise Open Source Conference in Singapore. The paper presents a historical view of SMPng development through 2001, but omits discussion of more recent diff --git a/en_US.ISO8859-1/htdocs/support/Makefile b/en_US.ISO8859-1/htdocs/support/Makefile index 526060483a..f289e8e059 100644 --- a/en_US.ISO8859-1/htdocs/support/Makefile +++ b/en_US.ISO8859-1/htdocs/support/Makefile @@ -9,4 +9,4 @@ DOCS= bugreports.sgml webresources.sgml -.include "${DOC_PREFIX}/share/mk/web.site.mk" \ No newline at end of file +.include "${DOC_PREFIX}/share/mk/web.site.mk" diff --git a/en_US.ISO8859-1/htdocs/support/bugreports.sgml b/en_US.ISO8859-1/htdocs/support/bugreports.sgml index 73b597de3c..870b921de1 100644 --- a/en_US.ISO8859-1/htdocs/support/bugreports.sgml +++ b/en_US.ISO8859-1/htdocs/support/bugreports.sgml @@ -41,7 +41,7 @@

                How to Submit A Problem Report

                - +

                Problem reports may be submitted to the development team using the send-pr(1) command on a &os; system. Another way to submit a problem report is diff --git a/en_US.ISO8859-1/htdocs/tutorials/index.sgml b/en_US.ISO8859-1/htdocs/tutorials/index.sgml index 6b1c471404..2b539489ca 100644 --- a/en_US.ISO8859-1/htdocs/tutorials/index.sgml +++ b/en_US.ISO8859-1/htdocs/tutorials/index.sgml @@ -13,7 +13,7 @@ -

                A complete list of documentation pertaining to FreeBSD is now +

                A complete list of documentation pertaining to FreeBSD is now available at ../docs.html. Please see that list for further information.

                diff --git a/en_US.ISO8859-1/htdocs/y2kbug.sgml b/en_US.ISO8859-1/htdocs/y2kbug.sgml index 4bc3fb77f1..2b16bad6e4 100644 --- a/en_US.ISO8859-1/htdocs/y2kbug.sgml +++ b/en_US.ISO8859-1/htdocs/y2kbug.sgml @@ -12,7 +12,7 @@ - +

                As management understanding of the Year 2000 problem (aka, "The Millennium Bug") increases, more and more companies are demanding official statements from the vendors of their hardware and software as @@ -23,11 +23,11 @@ properly maintain time long after year 2000 passes.

                Background information

                - +

                (This section based on the text from the Linux Y2K compliance page)

                - +

                As with all Unix and Unix-like operating systems, time and dates in FreeBSD are represented internally as the number of seconds since the 1st of January 1970 (the Unix "epoch"). Currently, that figure is @@ -57,25 +57,25 @@ millennium approaches.

                FreeBSD Year 2000 Statement

                - +

                "After extensive analysis and testing, we believe that FreeBSD is 100% Y2K compliant. In the unlikely event that something has been overlooked, we will do our best to fix it as soon as possible."

                - +

                David Greenman
                Principal Architect, The FreeBSD project

                Fixed problems

                - +

                The following Y2K problems have been identified and fixed in FreeBSD.

                - +
                misc/1380
                - +
                Several programs have a hardcoded 19%d in responses for the year. Affected programs include: yacc, ftpd, and make. [Fixed: yacc v1.2 1999/01/18; ftpd v1.7 1996/08/05; make v1.4 1996/10/06; fixes in @@ -83,14 +83,14 @@
                conf/1382
                - +
                The sed script in /etc/rc.local that builds the host/kernel ID line for the message of the day relies on the year not going past 1999. [Fixed v1.21 1996/10/24; fixes in FreeBSD-2.2 and above]
                misc/3465
                - +
                The etc/namedb/make-localhost command generates the DNS serial number as YYMMDD. In the year 2000, this will be generated as 1YYMMDD. [Fixed v1.2 1997/08/11; fixes in FreeBSD-2.2.5 and @@ -100,7 +100,7 @@ href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=4930">gnu/4930 and gnu/8321 - +
                groff tmac macros have hardcoded 19 for generating some dates. [Fixed: tmac.e v1.3 1998/12/06; doc-common v1.10 1999/01/19; fixes in FreeBSD-3.1 and above]
                @@ -108,7 +108,7 @@
                bin/9323
                - +
                In its obsolescent form, touch doesn't treat the two digit year specification correctly. Years in the range 00-68 are treated as 1900-1968 instead of 2000-2068. [Fixed v1.7 1999/01/05; fixes in @@ -116,7 +116,7 @@
                xntpd/parse/util/dcfd.c
                - +
                The leap year calculations for the number of days in a year, and the conversion of DCF77 time to seconds since the Epoch were wrong. These errors affected all years. [Fixed v1.6 1999/01/12; fixes in @@ -124,7 +124,7 @@
                tar/getdate.y
                - +
                Function Convert() was hard-coded for two digit years in range 70-99. Now adjusted to allow two digit years for 1970-2069. The function does not allow for century non-leap years - y2k1 alert! [Fixed v1.4 @@ -133,7 +133,7 @@
                fetch/http.c
                - +
                The HTTP protocol includes an obsolete date format which uses a two-digit year. Previous versions of fetch would interpret all such dates in the 1900s; subsequent to this revision, the pivot described @@ -147,21 +147,21 @@
                misc/9500
                - +
                The `edithook' script in the CVSROOT directory uses a raw tm_year and will therefore display 01/01/100 for 2000-JAN-01. [Fixed v1.2 1999/01/17; not relevant to FreeBSD releases]
                - +
                bin/9501
                - +
                Several cvs contrib files are not Y2K compliant. The log.pl and sccs2rcs.csh scripts prepend `19' to the year resulting in a display of 19100 for 2000. The log_accum.pl script uses a two digit year in one place and in another place assumes that the tm_year is year within century rather than years since 1900. [Fixed: log.pl v1.2 1999/01/15; sccs2rcs.csh v1.3 1999/01/15; fixes in FreeBSD-3.1 and above]
                - +
                bin/9502
                The groff number register `yr' is assigned from a (struct @@ -169,30 +169,30 @@ not the year within the century (see definition in troff/input.cc). [Fixed, now set mod 100, troff/input.cc V1.2 1999/06/03; fixed in FreeBSD-3.3]
                - +
                bin/9503
                - +
                PicoBSD's simple_httpd uses a raw tm_year and will therefore display 01/01/100 for 2000-JAN-01. [Fixed v1.2 1999/01/16; fixes in FreeBSD-3.1 and above]
                - +
                bin/9505
                - +
                Adduser uses a raw tm_year and will therefore display 100/01/01 for 2000-JAN-01. [Fixed v1.42 1999/01/15; fixes in FreeBSD-3.1 and above]
                - +
                bin/9506
                - +
                Cron uses a raw tm_year and will therefore display 100 for 2000. [Fixed v1.7 1999/01/16; fixes in FreeBSD-3.1 and above]
                - +
                bin/9507
                - +
                tcpslice(8) uses a raw tm_year and will therefore display 100y01m01d... for 2000-JAN-01. For compatibility, use a two-digit year until 2000.[Fixed v1.8 1999/01/20; fixes in FreeBSD-3.1 and @@ -200,13 +200,13 @@
                bin/14472
                - +
                Date command does not take thousand/hundred digits. [Fixed v1.31 1999/11/10]
                misc/14511
                - +
                Chpass has a problem using 00 for expiration year.
                @@ -217,31 +217,31 @@ bin/16207 - +
                Groff predefined \*(DT [\*(td] string has Y2K bug. [Fixed with import of version 1.15 2000/01/12]
                bin/15872
                - +
                at(1) has a problem with valid time specifications if tm_year is 100, reports `garbled time'.
                misc/16238
                - +
                KerberosIV install does not work properly because there is a hard-wired expiration date of 12/31/99 in the Kerberos source for the ticket granter. [Fixed v1.24 1999/09/19]
                - +

                More information

                - +

                If you have further questions about FreeBSD's year 2000 compliance, or - you have discovered an application running under FreeBSD that is not Y2K + you have discovered an application running under FreeBSD that is not Y2K compliant, please contact the project at freebsd-bugs@FreeBSD.org.

                diff --git a/en_US.ISO8859-1/share/sgml/catalog b/en_US.ISO8859-1/share/sgml/catalog index 914cc29920..c198a039f4 100644 --- a/en_US.ISO8859-1/share/sgml/catalog +++ b/en_US.ISO8859-1/share/sgml/catalog @@ -1,6 +1,6 @@ -- ...................................................................... -- -- FreeBSD SGML Public Identifiers ...................................... -- - + -- $FreeBSD$ -- diff --git a/en_US.ISO8859-1/share/sgml/freebsd.dsl b/en_US.ISO8859-1/share/sgml/freebsd.dsl index a90677e05f..a6e8b41aea 100644 --- a/en_US.ISO8859-1/share/sgml/freebsd.dsl +++ b/en_US.ISO8859-1/share/sgml/freebsd.dsl @@ -6,7 +6,7 @@ %freebsd.l10n; - + ]> @@ -16,6 +16,6 @@ - + diff --git a/en_US.ISO8859-1/share/sgml/glossary.ent b/en_US.ISO8859-1/share/sgml/glossary.ent index b271daad7f..4e2b6290b1 100644 --- a/en_US.ISO8859-1/share/sgml/glossary.ent +++ b/en_US.ISO8859-1/share/sgml/glossary.ent @@ -649,7 +649,7 @@ both single-processor and multi-processor machines. - + Graphical User Interface GUI @@ -1632,7 +1632,7 @@ - + repocopy @@ -1667,7 +1667,7 @@ so forth. See www.rfc-editor.org. - + Also used as a general term when someone has a suggested change and wants feedback. diff --git a/en_US.ISO8859-1/slides/20050513-bsdcan-slides/slides.xml b/en_US.ISO8859-1/slides/20050513-bsdcan-slides/slides.xml index a33d07ebcb..0fdd6c7071 100644 --- a/en_US.ISO8859-1/slides/20050513-bsdcan-slides/slides.xml +++ b/en_US.ISO8859-1/slides/20050513-bsdcan-slides/slides.xml @@ -171,7 +171,7 @@ <?xml version='1.0'?> <!DOCTYPE slides SYSTEM "/usr/.../schema/dtd/slides.dtd" [ -<!ENTITY % freebsd SYSTEM +<!ENTITY % freebsd SYSTEM "../../../share/sgml/freebsd.ent"> %freebsd; ]> diff --git a/en_US.ISO8859-1/slides/freebsd-general/slides.xml b/en_US.ISO8859-1/slides/freebsd-general/slides.xml index 8fe95d1363..3e19cde9d0 100644 --- a/en_US.ISO8859-1/slides/freebsd-general/slides.xml +++ b/en_US.ISO8859-1/slides/freebsd-general/slides.xml @@ -9,7 +9,7 @@ - -- cgit v1.2.3
                Hubs People running mirror sites (infrastructural support)
                Wireless 802.11 stack, tools, device driver development
                WWW Web site maintainers
                18 December 2000 &status.done;
                Implement condition variables. &a.jake;, &a.jasone;