From 38df6f51c644b63d9f0adce4cd6a7c2481f35fc9 Mon Sep 17 00:00:00 2001 From: John Fieber Date: Tue, 24 Sep 1996 17:46:04 +0000 Subject: [PATCH] Web pages, may I introduce you to CVS. CVS, these are the web pages. Yes, this is supposed to be a new top level in the repository. For the moment any changes to this area must be cleared by myself or Jordan. Once the kinks are worked out, the policy will probably be relaxed. --- data/COPYING | 339 +++++ data/COPYING.LIB | 481 +++++++ data/Makefile | 27 + data/Makefile.inc | 1 + data/README.mirror | 24 + data/about.sgml | 48 + data/cgi/Makefile | 11 + data/cgi/cgi-lib.pl | 119 ++ data/cgi/cgi-style.pl | 36 + data/cgi/ftp.cgi | 35 + data/cgi/ftp.mirrors | 64 + data/cgi/gallery.cgi | 131 ++ data/cgi/mirror.cgi | 16 + data/cgi/search.cgi | 257 ++++ data/commercial.sgml | 283 ++++ data/daemon.sgml | 62 + data/doc.ftr | 8 + data/doc.hdr | 0 data/docproj.sgml | 176 +++ data/docs.sgml | 60 + data/gallery.sgml | 879 ++++++++++++ data/gifs/Makefile | 5 + data/includes.sgml | 39 + data/index-site.sgml | 98 ++ data/index.sgml | 99 ++ data/license.sgml | 99 ++ data/mailto.sgml | 32 + data/newsflash.sgml | 585 ++++++++ data/ports/Makefile | 21 + data/ports/portindex | 163 +++ data/ports/ports.inc | 34 + data/releases/1.1.5/CONTRIB.386BSD | 196 +++ data/releases/1.1.5/CONTRIB.FreeBSD | 191 +++ data/releases/1.1.5/COPYRIGHT.386BSD | 131 ++ data/releases/1.1.5/COPYRIGHT.FreeBSD | 122 ++ data/releases/1.1.5/COPYRIGHT.USL | 45 + data/releases/1.1.5/KNOWNBUGS | 73 + data/releases/1.1.5/MIRROR.SITES | 59 + data/releases/1.1.5/Makefile | 6 + data/releases/1.1.5/PERSONAL.ACKS | 17 + data/releases/1.1.5/REGISTER.FreeBSD | 86 ++ data/releases/1.1.5/RELNOTES.FreeBSD | 313 ++++ data/releases/1.1.5/ROSTER.FreeBSD | 127 ++ data/releases/1.1.5/SUPPORT.TXT | 89 ++ data/releases/1.1.5/TODO-1.1.5 | 38 + data/releases/1.1/CONTRIB.386BSD | 196 +++ data/releases/1.1/CONTRIB.FreeBSD | 185 +++ data/releases/1.1/COPYRIGHT.386BSD | 131 ++ data/releases/1.1/COPYRIGHT.FreeBSD | 121 ++ data/releases/1.1/MIRROR.SITES | 59 + data/releases/1.1/Makefile | 4 + data/releases/1.1/PERSONAL.ACKS | 17 + data/releases/1.1/RELNOTES.FreeBSD | 303 ++++ data/releases/1.1/SUPPORT.TXT | 89 ++ data/releases/2.0.5A/Makefile | 3 + data/releases/2.0.5A/announce.sgml | 158 +++ data/releases/2.0.5A/notes.sgml | 738 ++++++++++ data/releases/2.0.5R/Makefile | 3 + data/releases/2.0.5R/announce.sgml | 112 ++ data/releases/2.0.5R/notes.sgml | 760 ++++++++++ data/releases/2.0/Makefile | 4 + data/releases/2.0/announce.sgml | 155 ++ data/releases/2.0/credits.sgml | 210 +++ data/releases/2.0/install.sgml | 493 +++++++ data/releases/2.0/notes.sgml | 641 +++++++++ data/releases/2.0A/Makefile | 3 + data/releases/2.0A/announce.sgml | 114 ++ data/releases/2.1.5R/Makefile | 3 + data/releases/2.1.5R/announce.sgml | 269 ++++ data/releases/2.1.5R/notes.sgml | 544 +++++++ data/releases/2.1R/Makefile | 3 + data/releases/2.1R/announce.sgml | 58 + data/releases/2.1R/notes.sgml | 349 +++++ data/releases/Makefile | 5 + data/releases/Makefile.inc | 2 + data/releases/index.sgml | 104 ++ data/releases/snapshots.sgml | 73 + data/robots.txt | 4 + data/search.sgml | 112 ++ data/searchhints.sgml | 50 + data/support.sgml | 252 ++++ data/tutorials/Makefile | 4 + data/tutorials/Makefile.inc | 1 + data/tutorials/ddwg/Makefile | 5 + data/tutorials/ddwg/ddwg.sgml | 1128 +++++++++++++++ data/tutorials/devel/Makefile | 6 + data/tutorials/devel/devel.sgml | 1738 +++++++++++++++++++++++ data/tutorials/disklessx/Makefile | 3 + data/tutorials/disklessx/disklessx.sgml | 264 ++++ data/tutorials/doc.ftr | 8 + data/tutorials/doc.hdr | 0 data/tutorials/fonts/Makefile | 6 + data/tutorials/fonts/fonts.sgml | 517 +++++++ data/tutorials/index.sgml | 35 + data/tutorials/mh/Makefile | 6 + data/tutorials/mh/mh.sgml | 572 ++++++++ data/tutorials/multios/Makefile | 6 + data/tutorials/multios/multios.sgml | 436 ++++++ data/tutorials/newuser/Makefile | 5 + data/tutorials/newuser/newuser.sgml | 537 +++++++ data/web.mk | 256 ++++ data/welcome.sgml | 65 + data/where.sgml | 111 ++ en/Makefile | 27 + en/Makefile.inc | 1 + en/cgi/Makefile | 11 + en/cgi/cgi-lib.pl | 119 ++ en/cgi/cgi-style.pl | 36 + en/cgi/ftp.cgi | 35 + en/cgi/ftp.mirrors | 64 + en/cgi/gallery.cgi | 131 ++ en/cgi/mirror.cgi | 16 + en/cgi/search.cgi | 257 ++++ en/commercial/commercial.sgml | 283 ++++ en/copyright/COPYING | 339 +++++ en/copyright/COPYING.LIB | 481 +++++++ en/copyright/daemon.sgml | 62 + en/copyright/license.sgml | 99 ++ en/doc.ftr | 8 + en/doc.hdr | 0 en/docproj/docproj.sgml | 176 +++ en/docs.sgml | 60 + en/gallery/gallery.sgml | 879 ++++++++++++ en/gifs/Makefile | 5 + en/includes.sgml | 39 + en/index.sgml | 99 ++ en/internal/README.mirror | 24 + en/internal/about.sgml | 48 + en/mailto.sgml | 32 + en/news/newsflash.sgml | 585 ++++++++ en/ports/Makefile | 21 + en/ports/portindex | 163 +++ en/ports/ports.inc | 34 + en/releases/1.1.5/CONTRIB.386BSD | 196 +++ en/releases/1.1.5/CONTRIB.FreeBSD | 191 +++ en/releases/1.1.5/COPYRIGHT.386BSD | 131 ++ en/releases/1.1.5/COPYRIGHT.FreeBSD | 122 ++ en/releases/1.1.5/COPYRIGHT.USL | 45 + en/releases/1.1.5/KNOWNBUGS | 73 + en/releases/1.1.5/MIRROR.SITES | 59 + en/releases/1.1.5/Makefile | 6 + en/releases/1.1.5/PERSONAL.ACKS | 17 + en/releases/1.1.5/REGISTER.FreeBSD | 86 ++ en/releases/1.1.5/RELNOTES.FreeBSD | 313 ++++ en/releases/1.1.5/ROSTER.FreeBSD | 127 ++ en/releases/1.1.5/SUPPORT.TXT | 89 ++ en/releases/1.1.5/TODO-1.1.5 | 38 + en/releases/1.1/CONTRIB.386BSD | 196 +++ en/releases/1.1/CONTRIB.FreeBSD | 185 +++ en/releases/1.1/COPYRIGHT.386BSD | 131 ++ en/releases/1.1/COPYRIGHT.FreeBSD | 121 ++ en/releases/1.1/MIRROR.SITES | 59 + en/releases/1.1/Makefile | 4 + en/releases/1.1/PERSONAL.ACKS | 17 + en/releases/1.1/RELNOTES.FreeBSD | 303 ++++ en/releases/1.1/SUPPORT.TXT | 89 ++ en/releases/2.0.5A/Makefile | 3 + en/releases/2.0.5A/announce.sgml | 158 +++ en/releases/2.0.5A/notes.sgml | 738 ++++++++++ en/releases/2.0.5R/Makefile | 3 + en/releases/2.0.5R/announce.sgml | 112 ++ en/releases/2.0.5R/notes.sgml | 760 ++++++++++ en/releases/2.0/Makefile | 4 + en/releases/2.0/announce.sgml | 155 ++ en/releases/2.0/credits.sgml | 210 +++ en/releases/2.0/install.sgml | 493 +++++++ en/releases/2.0/notes.sgml | 641 +++++++++ en/releases/2.0A/Makefile | 3 + en/releases/2.0A/announce.sgml | 114 ++ en/releases/2.1.5R/Makefile | 3 + en/releases/2.1.5R/announce.sgml | 269 ++++ en/releases/2.1.5R/notes.sgml | 544 +++++++ en/releases/2.1R/Makefile | 3 + en/releases/2.1R/announce.sgml | 58 + en/releases/2.1R/notes.sgml | 349 +++++ en/releases/Makefile | 5 + en/releases/Makefile.inc | 2 + en/releases/index.sgml | 104 ++ en/releases/snapshots.sgml | 73 + en/robots.txt | 4 + en/search/index-site.sgml | 98 ++ en/search/search.sgml | 112 ++ en/search/searchhints.sgml | 50 + en/support.sgml | 252 ++++ en/usergroups.sgml | 252 ++++ en/web.mk | 256 ++++ en/welcome.sgml | 65 + en/where.sgml | 111 ++ share/mk/web.site.mk | 256 ++++ 189 files changed, 30753 insertions(+) create mode 100644 data/COPYING create mode 100644 data/COPYING.LIB create mode 100644 data/Makefile create mode 100644 data/Makefile.inc create mode 100644 data/README.mirror create mode 100644 data/about.sgml create mode 100644 data/cgi/Makefile create mode 100644 data/cgi/cgi-lib.pl create mode 100644 data/cgi/cgi-style.pl create mode 100755 data/cgi/ftp.cgi create mode 100644 data/cgi/ftp.mirrors create mode 100755 data/cgi/gallery.cgi create mode 100755 data/cgi/mirror.cgi create mode 100755 data/cgi/search.cgi create mode 100644 data/commercial.sgml create mode 100644 data/daemon.sgml create mode 100644 data/doc.ftr create mode 100644 data/doc.hdr create mode 100644 data/docproj.sgml create mode 100644 data/docs.sgml create mode 100644 data/gallery.sgml create mode 100644 data/gifs/Makefile create mode 100644 data/includes.sgml create mode 100644 data/index-site.sgml create mode 100644 data/index.sgml create mode 100644 data/license.sgml create mode 100644 data/mailto.sgml create mode 100644 data/newsflash.sgml create mode 100644 data/ports/Makefile create mode 100755 data/ports/portindex create mode 100644 data/ports/ports.inc create mode 100644 data/releases/1.1.5/CONTRIB.386BSD create mode 100644 data/releases/1.1.5/CONTRIB.FreeBSD create mode 100644 data/releases/1.1.5/COPYRIGHT.386BSD create mode 100644 data/releases/1.1.5/COPYRIGHT.FreeBSD create mode 100644 data/releases/1.1.5/COPYRIGHT.USL create mode 100644 data/releases/1.1.5/KNOWNBUGS create mode 100644 data/releases/1.1.5/MIRROR.SITES create mode 100644 data/releases/1.1.5/Makefile create mode 100644 data/releases/1.1.5/PERSONAL.ACKS create mode 100644 data/releases/1.1.5/REGISTER.FreeBSD create mode 100644 data/releases/1.1.5/RELNOTES.FreeBSD create mode 100644 data/releases/1.1.5/ROSTER.FreeBSD create mode 100644 data/releases/1.1.5/SUPPORT.TXT create mode 100644 data/releases/1.1.5/TODO-1.1.5 create mode 100644 data/releases/1.1/CONTRIB.386BSD create mode 100644 data/releases/1.1/CONTRIB.FreeBSD create mode 100644 data/releases/1.1/COPYRIGHT.386BSD create mode 100644 data/releases/1.1/COPYRIGHT.FreeBSD create mode 100644 data/releases/1.1/MIRROR.SITES create mode 100644 data/releases/1.1/Makefile create mode 100644 data/releases/1.1/PERSONAL.ACKS create mode 100644 data/releases/1.1/RELNOTES.FreeBSD create mode 100644 data/releases/1.1/SUPPORT.TXT create mode 100644 data/releases/2.0.5A/Makefile create mode 100644 data/releases/2.0.5A/announce.sgml create mode 100644 data/releases/2.0.5A/notes.sgml create mode 100644 data/releases/2.0.5R/Makefile create mode 100644 data/releases/2.0.5R/announce.sgml create mode 100644 data/releases/2.0.5R/notes.sgml create mode 100644 data/releases/2.0/Makefile create mode 100644 data/releases/2.0/announce.sgml create mode 100644 data/releases/2.0/credits.sgml create mode 100644 data/releases/2.0/install.sgml create mode 100644 data/releases/2.0/notes.sgml create mode 100644 data/releases/2.0A/Makefile create mode 100644 data/releases/2.0A/announce.sgml create mode 100644 data/releases/2.1.5R/Makefile create mode 100644 data/releases/2.1.5R/announce.sgml create mode 100644 data/releases/2.1.5R/notes.sgml create mode 100644 data/releases/2.1R/Makefile create mode 100644 data/releases/2.1R/announce.sgml create mode 100644 data/releases/2.1R/notes.sgml create mode 100644 data/releases/Makefile create mode 100644 data/releases/Makefile.inc create mode 100644 data/releases/index.sgml create mode 100644 data/releases/snapshots.sgml create mode 100644 data/robots.txt create mode 100644 data/search.sgml create mode 100644 data/searchhints.sgml create mode 100644 data/support.sgml create mode 100644 data/tutorials/Makefile create mode 100644 data/tutorials/Makefile.inc create mode 100644 data/tutorials/ddwg/Makefile create mode 100644 data/tutorials/ddwg/ddwg.sgml create mode 100644 data/tutorials/devel/Makefile create mode 100644 data/tutorials/devel/devel.sgml create mode 100644 data/tutorials/disklessx/Makefile create mode 100644 data/tutorials/disklessx/disklessx.sgml create mode 100644 data/tutorials/doc.ftr create mode 100644 data/tutorials/doc.hdr create mode 100644 data/tutorials/fonts/Makefile create mode 100644 data/tutorials/fonts/fonts.sgml create mode 100644 data/tutorials/index.sgml create mode 100644 data/tutorials/mh/Makefile create mode 100644 data/tutorials/mh/mh.sgml create mode 100644 data/tutorials/multios/Makefile create mode 100644 data/tutorials/multios/multios.sgml create mode 100644 data/tutorials/newuser/Makefile create mode 100644 data/tutorials/newuser/newuser.sgml create mode 100644 data/web.mk create mode 100644 data/welcome.sgml create mode 100644 data/where.sgml create mode 100644 en/Makefile create mode 100644 en/Makefile.inc create mode 100644 en/cgi/Makefile create mode 100644 en/cgi/cgi-lib.pl create mode 100644 en/cgi/cgi-style.pl create mode 100755 en/cgi/ftp.cgi create mode 100644 en/cgi/ftp.mirrors create mode 100755 en/cgi/gallery.cgi create mode 100755 en/cgi/mirror.cgi create mode 100755 en/cgi/search.cgi create mode 100644 en/commercial/commercial.sgml create mode 100644 en/copyright/COPYING create mode 100644 en/copyright/COPYING.LIB create mode 100644 en/copyright/daemon.sgml create mode 100644 en/copyright/license.sgml create mode 100644 en/doc.ftr create mode 100644 en/doc.hdr create mode 100644 en/docproj/docproj.sgml create mode 100644 en/docs.sgml create mode 100644 en/gallery/gallery.sgml create mode 100644 en/gifs/Makefile create mode 100644 en/includes.sgml create mode 100644 en/index.sgml create mode 100644 en/internal/README.mirror create mode 100644 en/internal/about.sgml create mode 100644 en/mailto.sgml create mode 100644 en/news/newsflash.sgml create mode 100644 en/ports/Makefile create mode 100755 en/ports/portindex create mode 100644 en/ports/ports.inc create mode 100644 en/releases/1.1.5/CONTRIB.386BSD create mode 100644 en/releases/1.1.5/CONTRIB.FreeBSD create mode 100644 en/releases/1.1.5/COPYRIGHT.386BSD create mode 100644 en/releases/1.1.5/COPYRIGHT.FreeBSD create mode 100644 en/releases/1.1.5/COPYRIGHT.USL create mode 100644 en/releases/1.1.5/KNOWNBUGS create mode 100644 en/releases/1.1.5/MIRROR.SITES create mode 100644 en/releases/1.1.5/Makefile create mode 100644 en/releases/1.1.5/PERSONAL.ACKS create mode 100644 en/releases/1.1.5/REGISTER.FreeBSD create mode 100644 en/releases/1.1.5/RELNOTES.FreeBSD create mode 100644 en/releases/1.1.5/ROSTER.FreeBSD create mode 100644 en/releases/1.1.5/SUPPORT.TXT create mode 100644 en/releases/1.1.5/TODO-1.1.5 create mode 100644 en/releases/1.1/CONTRIB.386BSD create mode 100644 en/releases/1.1/CONTRIB.FreeBSD create mode 100644 en/releases/1.1/COPYRIGHT.386BSD create mode 100644 en/releases/1.1/COPYRIGHT.FreeBSD create mode 100644 en/releases/1.1/MIRROR.SITES create mode 100644 en/releases/1.1/Makefile create mode 100644 en/releases/1.1/PERSONAL.ACKS create mode 100644 en/releases/1.1/RELNOTES.FreeBSD create mode 100644 en/releases/1.1/SUPPORT.TXT create mode 100644 en/releases/2.0.5A/Makefile create mode 100644 en/releases/2.0.5A/announce.sgml create mode 100644 en/releases/2.0.5A/notes.sgml create mode 100644 en/releases/2.0.5R/Makefile create mode 100644 en/releases/2.0.5R/announce.sgml create mode 100644 en/releases/2.0.5R/notes.sgml create mode 100644 en/releases/2.0/Makefile create mode 100644 en/releases/2.0/announce.sgml create mode 100644 en/releases/2.0/credits.sgml create mode 100644 en/releases/2.0/install.sgml create mode 100644 en/releases/2.0/notes.sgml create mode 100644 en/releases/2.0A/Makefile create mode 100644 en/releases/2.0A/announce.sgml create mode 100644 en/releases/2.1.5R/Makefile create mode 100644 en/releases/2.1.5R/announce.sgml create mode 100644 en/releases/2.1.5R/notes.sgml create mode 100644 en/releases/2.1R/Makefile create mode 100644 en/releases/2.1R/announce.sgml create mode 100644 en/releases/2.1R/notes.sgml create mode 100644 en/releases/Makefile create mode 100644 en/releases/Makefile.inc create mode 100644 en/releases/index.sgml create mode 100644 en/releases/snapshots.sgml create mode 100644 en/robots.txt create mode 100644 en/search/index-site.sgml create mode 100644 en/search/search.sgml create mode 100644 en/search/searchhints.sgml create mode 100644 en/support.sgml create mode 100644 en/usergroups.sgml create mode 100644 en/web.mk create mode 100644 en/welcome.sgml create mode 100644 en/where.sgml create mode 100644 share/mk/web.site.mk diff --git a/data/COPYING b/data/COPYING new file mode 100644 index 0000000000..a43ea2126f --- /dev/null +++ b/data/COPYING @@ -0,0 +1,339 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 675 Mass Ave, Cambridge, MA 02139, USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/data/COPYING.LIB b/data/COPYING.LIB new file mode 100644 index 0000000000..eb685a5ec9 --- /dev/null +++ b/data/COPYING.LIB @@ -0,0 +1,481 @@ + GNU LIBRARY GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1991 Free Software Foundation, Inc. + 675 Mass Ave, Cambridge, MA 02139, USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the library GPL. It is + numbered 2 because it goes with version 2 of the ordinary GPL.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Library General Public License, applies to some +specially designated Free Software Foundation software, and to any +other libraries whose authors decide to use it. You can use it for +your libraries, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if +you distribute copies of the library, or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link a program with the library, you must provide +complete object files to the recipients so that they can relink them +with the library, after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + Our method of protecting your rights has two steps: (1) copyright +the library, and (2) offer you this license which gives you legal +permission to copy, distribute and/or modify the library. + + Also, for each distributor's protection, we want to make certain +that everyone understands that there is no warranty for this free +library. If the library is modified by someone else and passed on, we +want its recipients to know that what they have is not the original +version, so that any problems introduced by others will not reflect on +the original authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that companies distributing free +software will individually obtain patent licenses, thus in effect +transforming the program into proprietary software. To prevent this, +we have made it clear that any patent must be licensed for everyone's +free use or not licensed at all. + + Most GNU software, including some libraries, is covered by the ordinary +GNU General Public License, which was designed for utility programs. This +license, the GNU Library General Public License, applies to certain +designated libraries. This license is quite different from the ordinary +one; be sure to read it in full, and don't assume that anything in it is +the same as in the ordinary license. + + The reason we have a separate public license for some libraries is that +they blur the distinction we usually make between modifying or adding to a +program and simply using it. Linking a program with a library, without +changing the library, is in some sense simply using the library, and is +analogous to running a utility program or application program. However, in +a textual and legal sense, the linked executable is a combined work, a +derivative of the original library, and the ordinary General Public License +treats it as such. + + Because of this blurred distinction, using the ordinary General +Public License for libraries did not effectively promote software +sharing, because most developers did not use the libraries. We +concluded that weaker conditions might promote sharing better. + + However, unrestricted linking of non-free programs would deprive the +users of those programs of all benefit from the free status of the +libraries themselves. This Library General Public License is intended to +permit developers of non-free programs to use free libraries, while +preserving your freedom as a user of such programs to change the free +libraries that are incorporated in them. (We have not seen how to achieve +this as regards changes in header files, but we have achieved it as regards +changes in the actual functions of the Library.) The hope is that this +will lead to faster development of free libraries. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, while the latter only +works together with the library. + + Note that it is possible for a library to be covered by the ordinary +General Public License rather than by this special one. + + GNU LIBRARY GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library which +contains a notice placed by the copyright holder or other authorized +party saying it may be distributed under the terms of this Library +General Public License (also called "this License"). Each licensee is +addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also compile or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + c) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + d) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the source code distributed need not include anything that is normally +distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Library General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Library General Public + License as published by the Free Software Foundation; either + version 2 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Library General Public License for more details. + + You should have received a copy of the GNU Library General Public + License along with this library; if not, write to the Free + Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + , 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! diff --git a/data/Makefile b/data/Makefile new file mode 100644 index 0000000000..70dd1a26fd --- /dev/null +++ b/data/Makefile @@ -0,0 +1,27 @@ +DOCS= about.sgml commercial.sgml daemon.sgml docproj.sgml docs.sgml +DOCS+= gallery.sgml index-site.sgml index.sgml license.sgml +DOCS+= mailto.sgml newsflash.sgml searchhints.sgml support.sgml +DOCS+= welcome.sgml where.sgml search.sgml + +# These will be directly installed. + +DATA= COPYING COPYING.LIB README.mirror robots.txt + +# Files or targets listed here are defined in this file. + +LOCAL= stats.html stats-img.html + +stats.html: /home/www/server/logs/access_log + (cd /usr/local/www/server/logs;zcat access_log.*.gz;cat access_log) | \ + egrep -iv '\.(gif|jpg|jpeg|au) ' | \ + /usr/local/www/bin/analog +i0 +R500 -o > ${.TARGET} + +stats-img.html: /home/www/server/logs/access_log + (cd /usr/local/www/server/logs;zcat access_log.*.gz;cat access_log) | \ + /usr/local/www/bin/analog +i0 +R500 -o > ${.TARGET} + +SUBDIR= cgi gifs ports releases tutorials +DOCSUBDIR= FAQ handbook +WEBDIR= data + +.include "web.mk" diff --git a/data/Makefile.inc b/data/Makefile.inc new file mode 100644 index 0000000000..76793234c0 --- /dev/null +++ b/data/Makefile.inc @@ -0,0 +1 @@ +WEBBASE= /data diff --git a/data/README.mirror b/data/README.mirror new file mode 100644 index 0000000000..180b30dd49 --- /dev/null +++ b/data/README.mirror @@ -0,0 +1,24 @@ +You can (and are encouraged to) mirror the pages with sup. +If you are running apache as installed from the ports collection the +following should make a copy of www.freebsd.org available from +http://yourhost/www.freebsd.org/. Of course, there are possible +variations on the method... + +1) The supfile to get the WWW pages: + +www release=current host=freefall.cdrom.com hostbase=/home base=/usr/local/www/data/www.freebsd.org delete old + + +2) Add to /usr/local/www/server/conf/access.conf: + + +Options FollowSymLinks Includes +XBitHack Full + + +3) Add to /usr/local/www/server/conf/srm.conf + +Alias /www.freebsd.org /usr/local/www/data/www.freebsd.org/data + +4) Create a directory /usr/local/www/counters that is writable by the +httpd daemon, then compile pagecount.C and install in /usr/local/www/cgi-bin. diff --git a/data/about.sgml b/data/about.sgml new file mode 100644 index 0000000000..99c67561d1 --- /dev/null +++ b/data/about.sgml @@ -0,0 +1,48 @@ + + + %includes; +]> + +&header; + +

The Machine

+ +

The + machine, www.freebsd.org, otherwise known as + freefall.cdrom.com, is 90MHz Pentium machine with + a PCI motherboard, 48 megabytes of RAM and about 5.4 + gigabytes of disk space. Naturally, the system runs under + the FreeBSD operating system. The hardware and network + connection have been generously provided by Walnut Creek CDROM.

+ +

The Software

+ +

+ These pages are served up by the versatile and efficient Apache http server. In + addition, there are a few locally crafted CGI scripts. + Indexing of these pages and the mailing list archive are + provided by freewais-sf, a derivative of the CNIDR freewais. + +

The Pages

+ +

These Web pages have been put together by John Fieber + <jfieber@freebsd.org> + with input from the FreeBSD community and you. + +

Usage statistics for this server are updated daily:

+ + + + &footer; + + + diff --git a/data/cgi/Makefile b/data/cgi/Makefile new file mode 100644 index 0000000000..f632feea24 --- /dev/null +++ b/data/cgi/Makefile @@ -0,0 +1,11 @@ +DATA= ftp.mirrors +CGI= ftp.cgi gallery.cgi mirror.cgi cgi-lib.pl cgi-style.pl +CGI+= search.cgi + +.SUFFIXES: .C .cgi + +.C.cgi: + ${CXX} ${CFLAGS} -o ${.TARGET} ${.IMPSRC} + +.include "../web.mk" + diff --git a/data/cgi/cgi-lib.pl b/data/cgi/cgi-lib.pl new file mode 100644 index 0000000000..172154de15 --- /dev/null +++ b/data/cgi/cgi-lib.pl @@ -0,0 +1,119 @@ +#!/usr/bin/perl -- -*- C -*- +# Perl Routines to Manipulate CGI input +# S.E.Brenner@bioc.cam.ac.uk +# $Header: /home/ncvs/www/data/cgi/cgi-lib.pl,v 1.1.1.1 1996-09-24 17:45:57 jfieber Exp $ +# +# Copyright 1994 Steven E. Brenner +# Unpublished work. +# Permission granted to use and modify this library so long as the +# copyright above is maintained, modifications are documented, and +# credit is given for any use of the library. +# +# Thanks are due to many people for reporting bugs and suggestions +# especially Meng Weng Wong, Maki Watanabe, Bo Frese Rasmussen, +# Andrew Dalke, Mark-Jason Dominus and Dave Dittrich. +# For more information, see: +# http://www.bio.cam.ac.uk/web/form.html +# http://www.seas.upenn.edu/~mengwong/forms/ +# Minimalist http form and script (http://www.bio.cam.ac.uk/web/minimal.cgi): +# +# require "cgi-lib.pl"; +# if (&ReadParse(*input)) { +# print &PrintHeader, &PrintVariables(%input); +# } else { +# print &PrintHeader,'
Data: '; +#} +# ReadParse +# Reads in GET or POST data, converts it to unescaped text, and puts +# one key=value in each member of the list "@in" +# Also creates key/value pairs in %in, using '\0' to separate multiple +# selections +# Returns TRUE if there was input, FALSE if there was no input +# UNDEF may be used in the future to indicate some failure. +# Now that cgi scripts can be put in the normal file space, it is useful +# to combine both the form and the script in one place. If no parameters +# are given (i.e., ReadParse returns FALSE), then a form could be output. +# If a variable-glob parameter (e.g., *cgi_input) is passed to ReadParse, +# information is stored there, rather than in $in, @in, and %in. +sub ReadParse { + local (*in) = @_ if @_; + local ($i, $key, $val); + # Read in text + if (&MethGet) { + $in = $ENV{'QUERY_STRING'}; + } elsif ($ENV{'REQUEST_METHOD'} eq "POST") { + read(STDIN,$in,$ENV{'CONTENT_LENGTH'}); + } + @in = split(/&/,$in); + foreach $i (0 .. $#in) { + # Convert plus's to spaces + $in[$i] =~ s/\+/ /g; + # Split into key and value. + ($key, $val) = split(/=/,$in[$i],2); # splits on the first =. + # Convert %XX from hex numbers to alphanumeric + $key =~ s/%(..)/pack("c",hex($1))/ge; + $key =~ tr/[^A-Za-z0-9\-\_\$\+\=\~\.\,]//; # allow only safe chars + $val =~ s/%(..)/pack("c",hex($1))/ge; + $val =~ tr/[^A-Za-z0-9\-\_\$\+\=\~\.\,]//; # allow only safe chars + # Associate key and value + $in{$key} .= "\0" if (defined($in{$key})); # \0 is the multiple separator + $in{$key} .= $val; + } + return length($in); +} +# PrintHeader +# Returns the magic line which tells WWW that we're an HTML document +sub PrintHeader { + return "Content-type: text/html\n\n"; +} +# MethGet +# Return true if this cgi call was using the GET request, false otherwise +sub MethGet { + return ($ENV{'REQUEST_METHOD'} eq "GET"); +} +# MyURL +# Returns a URL to the script +sub MyURL { + return 'http://' . $ENV{'SERVER_NAME'} . $ENV{'SCRIPT_NAME'}; +} +# CgiError +# Prints out an error message which which containes appropriate headers, +# markup, etcetera. +# Parameters: +# If no parameters, gives a generic error message +# Otherwise, the first parameter will be the title and the rest will +# be given as different paragraphs of the body +sub CgiError { + local (@msg) = @_; + local ($i,$name); + if (!@msg) { + $name = &MyURL; + @msg = ("Error: script $name encountered fatal error"); + }; + print &PrintHeader; + print "$msg[0]\n"; + print "

$msg[0]

\n"; + foreach $i (1 .. $#msg) { + print "

$msg[$i]

\n"; + } + print "\n"; +} +# PrintVariables +# Nicely formats variables in an associative array passed as a parameter +# And returns the HTML string. +sub PrintVariables { + local (%in) = @_; + local ($old, $out, $output); + $old = $*; $* =1; + $output .= "
"; + foreach $key (sort keys(%in)) { + foreach (split("\0", $in{$key})) { + ($out = $_) =~ s/\n/
/g; + $output .= "
$key
$out
"; + } + } + $output .= "
"; + $* = $old; + return $output; +} +1; diff --git a/data/cgi/cgi-style.pl b/data/cgi/cgi-style.pl new file mode 100644 index 0000000000..53252af9bd --- /dev/null +++ b/data/cgi/cgi-style.pl @@ -0,0 +1,36 @@ +# $Id: cgi-style.pl,v 1.1.1.1 1996-09-24 17:45:57 jfieber Exp $ +# +# Perl routines to encapsulate various elements of HTML page style. + +# For future reference, when is now? +($se,$mn,$hr,$md,$mo,$yr,$wd,$yd,$dst) = localtime(time); +$yr += 1900; +$timestamp = "$mo-$md-$yr"; + +# Colors for the body +$t_body = ""; + +if ($hsty_base eq "") { + $hsty_base = ".."; +} +if ($hsty_author eq "") { + $hsty_author = "www\@freebsd.org"; +} + +$i_daemon = "\"\""; + +if ($hsty_home eq "") { + $hsty_home = "\"FreeBSD"; +} + +sub html_header { + local ($title) = @_; + + return &PrintHeader . "\n$title\n\n$t_body\n" . + "

$i_daemon $title

\n"; +} + +sub html_footer { + return "
$hsty_home
$hsty_author
$hsty_date
\n"; +} diff --git a/data/cgi/ftp.cgi b/data/cgi/ftp.cgi new file mode 100755 index 0000000000..0cca755978 --- /dev/null +++ b/data/cgi/ftp.cgi @@ -0,0 +1,35 @@ +#!/usr/bin/perl + +require 'cgi-lib.pl'; +require 'cgi-style.pl'; + + +$newloc = "http://www.freebsd.org/"; + +print &html_header("FTP Download"); + +open (MIRRORS, "ftp.mirrors"); + +print "

Download $ARGV[0] from one of the following mirror sites:

\n"; + +$oldplace = ""; + +while () { + if (/.*:.*:/ && !/^#/) { + ($place, $site, $root) = split(':',$_); + chop $root; $root =~ s/ *$//; + if ($place ne $oldplace) { + if ($oldplace ne "") { + print "\n"; + } + print "$place\n
    \n"; + $oldplace = $place; + } + print "
  • $site
    • \n"; + } +} + +close (MIRRORS); + +print "
\n"; +print &html_footer; diff --git a/data/cgi/ftp.mirrors b/data/cgi/ftp.mirrors new file mode 100644 index 0000000000..d0952db86c --- /dev/null +++ b/data/cgi/ftp.mirrors @@ -0,0 +1,64 @@ +#testing +Australia:ftp.au.freebsd.org:/pub/FreeBSD +Australia:ftp2.au.freebsd.org:/pub/FreeBSD +Australia:ftp3.au.freebsd.org:/pub/FreeBSD + +Brazil:ftp.br.freebsd.org:/pub/FreeBSD + +Canada:ftp.ca.freebsd.org:/pub/FreeBSD + +Czech Republic:sunsite.mff.cuni.cz:/OS/FreeBSD + +Finland:nic.funet.fi:/pub/unix/FreeBSD + +France:ftp.ibp.fr:/pub/FreeBSD + +Germany:ftp.de.freebsd.org:/pub/FreeBSD +Germany:ftp2.de.freebsd.org:/pub/FreeBSD +Germany:ftp3.de.freebsd.org:/pub/FreeBSD +Germany:ftp4.de.freebsd.org:/pub/FreeBSD +Germany:ftp5.de.freebsd.org:/pub/FreeBSD +Germany:ftp6.de.freebsd.org:/pub/FreeBSD + +Hong Kong:ftp.hk.super.net:/pub/FreeBSD + +Ireland:ftp.internet-eireann.ie:/pub/FreeBSD + +Israel:orgchem.weizmann.ac.il:/pub/FreeBSD + +Japan:ftp.jp.freebsd.org:/pub/FreeBSD +Japan:ftp2.jp.freebsd.org:/pub/FreeBSD +Japan:ftp3.jp.freebsd.org:/pub/FreeBSD +Japan:ftp4.jp.freebsd.org:/pub/FreeBSD +Japan:ftp5.jp.freebsd.org:/pub/FreeBSD +Japan:ftp6.jp.freebsd.org:/pub/FreeBSD + +Korea:ftp.kr.freebsd.org:/pub/FreeBSD +Korea:ftp2.kr.freebsd.org:/pub/FreeBSD + +Netherlands:ftp.nl.net:/pub/os/FreeBSD + +Portugal:ftp.ua.pt:/pub/misc/FreeBSD + +Russia:ftp.kiae.su:/FreeBSD + +South Africa:ftp.za.freebsd.org:/pub/FreeBSD +South Africa:ftp2.za.freebsd.org:/pub/FreeBSD + +Sweden:ftp.luth.se:/pub/FreeBSD + +Taiwan:NCTUCCCA.edu.tw:/Operating-Systems/FreeBSD +Taiwan:netbsd.csie.nctu.edu.tw:/pub/FreeBSD + +Thailand:ftp.nectec.or.th:/pub/FreeBSD + +United States:ftp.freebsd.org:/pub/FreeBSD +United States:ftp2.freebsd.org:/pub/FreeBSD +United States:ftp3.freebsd.org:/pub/FreeBSD +United States:ftp4.freebsd.org:/pub/FreeBSD +United States:ftp5.freebsd.org:/pub/FreeBSD +United States:ftp6.freebsd.org:/pub/FreeBSD + +United Kingdom:ftp.uk.freebsd.org:/packages/unix/FreeBSD +United Kingdom:ftp2.uk.freebsd.org:/pub/walnut.creek/FreeBSD +United Kingdom:ftp3.uk.freebsd.org:/pub/BSD/FreeBSD diff --git a/data/cgi/gallery.cgi b/data/cgi/gallery.cgi new file mode 100755 index 0000000000..61de211ce6 --- /dev/null +++ b/data/cgi/gallery.cgi @@ -0,0 +1,131 @@ +#!/usr/bin/perl +################################################################## +# A CGI form processor for FreeBSD Gallery submissions +# +# John Fieber +# August 9 1996 +################################################################## + +$curator = "jfieber@indiana.edu"; +#$curator = "jkh@freebsd.org"; +$subject = "Another gallery submission..."; + +require 'cgi-lib.pl'; +&ReadParse; + +#$d_date = "$Date: 1996-09-24 17:45:57 $"; +#$h_base = ".."; +#$d_author = " +require 'cgi-style.pl'; + +# Construct the gallery entry in HTML form +$entry = "
  • $in{'organization'} " . + "-- $in{'description'}
    • "; + +# Try and figure out where the person came from so we can provide +# links back to the correct place. +$return = ""; +if ($in{'return'} eq "") { + if ($ENV{'HTTP_REFERER'} ne "") { + $in{'return'} = $ENV{'HTTP_REFERER'}; + } +} +if ($in{'return'} ne "") { + $return = "Return to the Gallery"; +} + + +# This is the form where the user enters the information. +$forma = &html_header("Gallery Submission") . +" + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Organization:
    Description:
    URL:
    Category: + Commercial
    + Non-Profit
    + Personal +
    Email Contact:
    + +

    $return

    +" . &html_footer(); + +# This is the form where the user CHECKS the information they typed +$formb = &html_header("Your Gallery Submission") . +"

    Here is your entry as it will appear in the +FreeBSD Gallery page.

    +

    Please check that the category and your e-mail +address are correct, and that the link actually works. +If anything is wrong, use your +browser's back button and correct it. +If everything is okay, press the submit button +below.

    +

    Contact person: $in{'contact'}

    +

    $in{'category'}

    +
      +$entry +
    +
    +
    + + + + + + + + +
    +

    $return

    +" . &html_footer(); + +# And this is where we thank them for submitting an entry. +$formc = &html_header("Thank You!") . +"

    Please allow a few days for your entry to be added +to the Gallery.

    +

    $return

    +" . &html_footer(); + + +if ($in{'action'} eq "preview") { + print $formb; +} +elsif ($in{'action'} eq "submit") { + print $formc; +# close(STDOUT); + + open(M, "| mail -s \"$subject\" $curator"); + print M "$in{'contact'} submitted the following to be added under\n"; + print M "\"$in{'category'}\" in the gallery:\n\n"; + print M "<-- from $in{'contact'} on $timestamp -->\n"; + print M "$entry\n"; + close(M); +} +else { + print $forma; +} + +exit 0; diff --git a/data/cgi/mirror.cgi b/data/cgi/mirror.cgi new file mode 100755 index 0000000000..d92d59bb0f --- /dev/null +++ b/data/cgi/mirror.cgi @@ -0,0 +1,16 @@ +#!/usr/bin/perl +# (c) Wolfram Schneider, Berlin. June 1996. Public domain. +# +# FreeBSD WWW mirror redirect +# +# $Id: mirror.cgi,v 1.1.1.1 1996-09-24 17:45:57 jfieber Exp $ + +$_ = $ENV{'QUERY_STRING'}; + +s/^[^=]+=//; # 'variable=value' -> 'value' +s/\+/ /g; # '+' -> space +s/%(..)/pack("c",hex($1))/ge; # '%ab' -> char ab + +print "Location: $_\nContent-type: text/plain\n\n"; + +exit 0; diff --git a/data/cgi/search.cgi b/data/cgi/search.cgi new file mode 100755 index 0000000000..c22293d650 --- /dev/null +++ b/data/cgi/search.cgi @@ -0,0 +1,257 @@ +#!/usr/bin/perl +# +# mail-archive.pl -- a CGI interface to a wais indexed maling list archive. +# +# Origin: +# Tony Sanders , Nov 1993 +# +# Hacked beyond recognition by: +# John Fieber , Nov 1994 +# +# Format the mail messages a little nicer. +# Add code to check database status before searching. +# John Fieber , Aug 1996 +# +# Disclaimer: +# This is pretty ugly in places. + + +$server_root = '/usr/local/www'; +$waisq = "/usr/local/www/bin/waisq"; +$sourcepath = "/f/jfieber/index"; +$hints = "/searchhints.html"; +$myurl = "/cgi/search.cgi"; + +require "open2.pl"; +require "cgi-lib.pl"; +require "cgi-style.pl"; + +@months = ('Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'); + +sub do_wais { + &ReadParse; + + @FORM_words = split(/ /, $in{"words"}); + @FORM_source = split(/\0/, $in{"source"}); + $FORM_max = $in{"max"}; + $FORM_docnum = $in{"docnum"}; + + @AVAIL_source = &checksource(@FORM_source); + if ($#FORM_source != $#AVAIL_source) { + $j = 0; + $k = 0; + foreach $i (0 .. $#FORM_source) { + if ($FORM_source[$i] ne $AVAIL_source[$j]) { + $badsource[$k] = $FORM_source[$i]; + $k++; + } else { + $j++; + } + } + $badsource = join(", ", @badsource); + $badsource =~ s/,([^,]*)$/ and $1/; + if ($#FORM_source - $#AVAIL_source > 1) { + $availmsg = "

    [The $badsource archives are currently unavailable.]

    "; + } else { + $availmsg = "

    [The $badsource archive is currently unavailable.]

    "; + } + } + if ($#AVAIL_source < 0) { + $i = join("    , ", @FORM_source); + $i =~ s/,([^,]*)$/ and $1/; + print &html_header("Mail Archive Search") . + "

    None of the archives you requested ($i) are available at " . + "this time.

    \n"; + print "

    Please try again later, or return to the " . + "search page and select a different archive.

    \n"; + print &html_footer; + exit 0; + } + + # Now we formulate the question to ask the server + foreach $i (@AVAIL_source) { + $w_sources .= "(:source-id\n :filename \"$i.src\"\n ) "; + } + $w_question = "\n (:question + :version 2 + :seed-words \"@FORM_words\" + :relevant-documents + ( ) + :sourcepath \"$sourcepath/:\" + :sources + ( $w_sources ) + :maximum-results $FORM_max + :result-documents + ( ) + )\n"; + + + # + # First case, no document number so this is a regular search + # + if (length($FORM_docnum) == 0) { + print &html_header("Search Results"); + print $availmsg; + if ($#AVAIL_source > 0) { + $src = join("    , ", @AVAIL_source); + $src =~ s/,([^,]*)$/ and $1/; + print "

    The archives $src contain "; + } + else { + print "The archive @AVAIL_source contains "; + } + print " the following items relevant to \`@FORM_words\':\n"; + print "

      \n"; + + &open2(WAISOUT, WAISIN, $waisq, "-g"); + print WAISIN $w_question; + + local($hits, $score, $headline, $lines, $bytes, $type, $date, $file); + while () { + /:score\s+(\d+)/ && ($score = $1); + /:filename "(.*)"/ && ($file = $1); + /:number-of-lines\s+(\d+)/ && ($lines = $1); + /:number-of-bytes\s+(\d+)/ && ($bytes = $1); + /:type "(.*)"/ && ($type = $1); + /:headline "(.*)"/ && ($headline = $1); # XXX + /:date "(\d+)"/ && ($date = $1, $hits++, &docdone); + } + print "
    \n"; + + print "

    Didn't get what you expected? "; + print "Look here for searching hints."; + + if ($hits == 0) { + print "Nothing found.\n"; + } + + print &html_footer; + close(WAISOUT); + close(WAISIN); + + } + +# +# Second Case, a document number was supplied +# + + else { + print &html_header("Search Results: Document"); + &open2(WAISOUT, WAISIN, $waisq, "-g"); + print WAISIN $w_question; + + while () { + s/search_word: boolean \`and\' scored//g; + $w_result .= $_; + } + close(WAISOUT); + close(WAISIN); + + &open2(WAISOUT, WAISIN, $waisq, "-v", $FORM_docnum); + print WAISIN $w_result; + + while () { + $foo .= $_; + } + &printdoc($foo); + + print &html_footer; + close(WAISOUT); + close(WAISIN); + } +} + +# Given an array of sources (sans .src extension), this routine +# checks to see if they actually exist, and if they do, if they +# are currently available (ie, not being updated). It returns +# an array of sources that are actually available. + +sub checksource { + local (@sources) = @_; + + $j = 0; + foreach $i (@sources) { + if (stat("$sourcepath/$i.src")) { + if (!stat("$sourcepath/$i.update.lock")) { + $goodsources[$j] = $i; + $j++; + } + } + } + return(@goodsources); +} + + +# Print a mail message in HTML form + +sub printdoc { + local ($doc) = @_; + + ($header, $body) = split(/\n\n/, $doc, 2); + + $body = &htmlescape($body); + + $header = &htmlescape($header); + $header =~ s/\n */ /g; + + foreach $i (split(/\n/, $header)) { + ($field, $data) = split(/ /, $i, 2); + $hdr{$field} = $data; + } + + print "\n

    \n";
+    if (length($hdr{'Date:'}) > 0) {
+    	print "Date:      $hdr{'Date:'}\n";
+    }
+    if (length($hdr{'From:'}) > 0) {
+    	print "From:      $hdr{'From:'}\n";
+    }
+    if (length($hdr{'To:'}) > 0) {
+    	print "To:        $hdr{'To:'}\n";
+    }
+    if (length($hdr{'Cc:'}) > 0) {
+    	print "Cc:        $hdr{'Cc:'}\n";
+    }
+    if (length($hdr{'Sender:'}) > 0) {
+    	print "Sender:    $hdr{'Sender:'}\n";
+    }
+    if (length($hdr{'Subject:'}) > 0) {
+    	print "Subject:   $hdr{'Subject:'}\n";
+    }
+    print "
    \n"; + + print "
    \n
    \n$body\n
    \n"; +} + +sub htmlescape { + local ($data) = @_; + $data =~ s/&/&/g; + $data =~ s/The archive $file contains no relevant documents.

    " + } else { + $headline = &htmlescape($headline); + $headline =~ s/\\"/\"/g; + print "
  • $headline\n"; + print "
    "; +# print ""; + print "Score: $score; "; + $_ = $date; + /(..)(..)(..)/ && ($yr = $1 + 1900, $mo = $months[$2 - 1], $dy = $3); + print "Lines: $lines; "; + print "${dy}-${mo}-${yr}; "; + print "Archive: $file"; + print "

    • \n"; + } + $score = $headline = $lines = $bytes = $type = $date = $file = ''; +} + +$| = 1; +open (STDERR,"> /dev/null"); +eval '&do_wais'; + diff --git a/data/commercial.sgml b/data/commercial.sgml new file mode 100644 index 0000000000..62b90e0844 --- /dev/null +++ b/data/commercial.sgml @@ -0,0 +1,283 @@ + + + %includes; +]> + +&header; + +

    In addition to the demos of commercial software available + in the FreeBSD distribution, a number of other commercial + vendors offer software products specifically for FreeBSD. + If you know of other companies supporting FreeBSD that + should be added to this page, please notify us.

    + +

    Software

    + +
      +
    • AstroArch + Consulting, Inc. develops and licenses its + ISP Billing and Tracking System or BATS + for FreeBSD as well as thirteen other Operating + Systems. For more information, check out the web pages http://www.tpoint.net/astroarch, + send email to elh@astroarch.com or + call (512) 990-1064.

      +
      • + +
    • + Communication + Systems Research Corp. - Business + applications and consulting for Unix systems including + BSD. Specializing in analysis and development of high + performance solutions for networking problems. Located in + Portland Oregon, consulting internationally for over 12 + years. Telephone: (503) 291-1345

      +
      • + +
    • BRU from + Enhanced Software Technologies is a very powerful and reliable + tape backup system. It offers per-file compression, an improved + tape format with three different kinds of verification, and many safety + checks to insure data integrity. The "BSD/OS 1.1" version works well + with FreeBSD. +

      +
      • + +
    • Conetic + Software is offering a FREE + copy of C/BASE 4GL for the FreeBSD 2.0.5 + operating system. C/BASE 4GL features a + powerful application development tool and database + engine. Featuring a easy to user visual development + environment, a scripting language, and application + libraries with a C language (API) interface. The + best thing about C/BASE 4GL is that it is + fully portable across hardware and operating system + platforms. FreeBSD to DOS, DOS to SOLARIS, SOLARIS + to AIX, etc.... Your free copy of C/BASE 4GL + is set to run for a maximum of 2 concurrent users and + 1,000 records. Please contact us at info@conetic.com + if you'd like a taste of even more power and + programming fun.

      +
      • + +
    • + + Inlab Software GmbH offers binaries of Inlab-Scheme + for FreeBSD and Linux which are free for personal or educational + use. Inlab-Scheme is a R4RS compliant Scheme which is capable + of reading and writing TIFF and XBM-bitmaps to and from a special + internal bitmap type. With built-in primitives for image + processing, Inlab-Scheme can be a general tool for tasks like + optical character recognition and general analysis and processing + of bitmap data.

      +
      • + +
    • + NetCon Corporation + established in 1985, with over 10,000 installed servers, is the leading + supplier of NetWare compatible operating systems and Internet Gateways + for standard UNIX platforms. NetCon offers a complete line of systems + for FreeBSD, SUN Solaris, SCO UNIX/ODT and IBM AIX RS6000 serving from + 5 to 1000 users. Services include; Full Internet access from + NetWare/WIN95/Windows workstations over IPX/SPX, X Windows over + IPX/SPX, NetWare file and print services, NetWare Client services for + UNIX, High-performance, DOS/Windows Terminal Emulation. +

      +
      • + +
    • + Perforce Software + produces + PERFORCE -- the FAST Software + Configuration Management System for many UNIX platforms + and NT. More capable than freeware tools, more applicable + than solutions from academia, and more usable than available + commercial products, PERFORCE manages + software projects comprising thousands of source files + shared by dozens of engineers across many heterogeneous + platforms and geographically distributed locations. + Documentation and fully functional versions (but limited + to two client workspaces) can be downloaded from the Web + pages. For non-commercial users on FreeBSD, we offer + servers with unlimited client workspaces for $1. Perforce + Software can be reached at + info@perforce.com or 1 (510) 865-8720.

      +
      • + +
    • + Progresive Networks, Inc. + offers both its RealAudio + player + and server + for FreeBSD. + The free player allows you to play live and on-demand audio + over 14.4Kps and faster connections. + All you have to do is click on a RealAudio link from your Web browser + and audio begins playing instantly. Check out + The RealAudio Guide to access + hundreds of sites offering music, news, live radio stations, live + events etc. The server allows your website to deliver live and + on-demand audio over the Internet or your company network.

      +
      • + +
    • + RTD provides an ISP billing + package for ISPs using FreeBSD called + UTA

      +
      • + +
    • + Coolworld.Com, Inc. + provides a billing package for ISP's called Internet Billing. + This package was designed to handle all the billing needs for + Internet service providers. It runs under MS-Windows. One + piece of the software is a client/server set with a daemen that + runs on a UNiX server (including FreeBSD) that allows the client + to do all for their user management under a windows frontend.

      +
      • + +
    • X Inside, Inc. + offers software enhancements for FreeBSD. + Accelerated-X Server completely supports 356 + graphics adapters from over 40 vendors, including many + partially supported or not included with XFree86. + Download + a free demonstration from + ftp.xinside.com. Utilize 3D graphics with Accelerated-X + OpenGL. Accelerated-X Multi-Head allows 8 monitors + from a single server. Full Motif 2.0 runtime and development kits + are also available. For more information email info@xinside.com + or call +1 (303) 298-7478.

      +
      • + +
    • XVScan + allows you to use your HP ScanJet scanner under FreeBSD. It is a + commercial product based on John Bradley's xv. +

      +
      • + +
    • Zeus Technology Limited + offer Zeus Server for FreeBSD. Zeus Server is + an advanced, powerful full-featured commercial grade webserver + designed with exceptional performance, minimal machine resource + requirements and ease of administration in mind. Free + evaluation copies may be + downloaded. +

      • + +
    + +

    Hardware and complete systems

    + +
      + +
    • + Apache Digital + Corporation creates custom high-performance PC + based systems optimized for the FreeBSD operating system. + We have many standard + systems to choose from as well as an on-line custom + system design form to help you create your custom + dream system. Please feel free to contact info@apache.com for + more information.

      +
      • + +
    • Cyclades Corporation + sells a variety of high performance, multiport serial + cards which FreeBSD supports in its standard releases (due largely + to their generous cooperation in providing us with hardware and + technical assistance). +

      • + +
    • Emerging Technologies, + Inc. has high speed serial communications adapters + allowing FreeBSD systems to utilize leased lines at + speeds from 56k to T1. The adapters include a complete + set of drivers and utilities that allow a FreeBSD machine + to communicate directly with virtually any IP router via + synchronous PPP, Frame Relay or X.25, and directly to + CISCO brand routers with CISCO serial encapsulation. Full + documentation and support are included. Several hardware + choices are available ranging from an economical single + port adapter card to a dual T1 line model with dual 25mhz + dedicated processors. To contact Emerging Techologies, + send E-mail to info@etinc.com. +

      +
      • + +
    • Geli + Engineering offers economical Pentium + workstation clusters that use the FreeBSD operating system.

      • + +
    • The Init Organization + specializes in Intranet networking servers running FreeBSD. We can + custom design and construct high performance servers to fill any need. + The Init Organization also provides network support and management, + IS support and training, corporate-wide e-mail gateways, domain name + registration and hosting, world wide web site development, and more. + Please send e-mail to info@init.org, + or visit + http://www.tioga.com/~Init/. +

      • + +
    • MOXA makes + economically priced multi-port serial cards which are compatible with + FreeBSD's sio serial driver. The C104 / C168 family of 2/4/8 serial + port cards feature custom ASIC design, speeds up to 921.6Kbps, surge + protection, independent and software configurable I/O ports and IRQs. +

      • + +
    • Stallion Technolgies + Inc offers a range of multiport serial boards for the ISA, + EISA, MCA and PCI buses. Although Stallion does not officially support + drivers for FreeBSD, there is an unsupported, freely available driver + available from their + FTP site. + This driver supports the Stallion EasyIO and EasyConnection 8/32 + multiport boards. For local pricing and availability information, + contact Stallion via their WWW page. +

      • + +
    • SW Technology + offers quality Pentium machines with FreeBSD pre-installed. +

      • + +
    • Zyzzyva Enterprises + presents the Z-Router + as an affordable alternative for businesses and organizations seeking + cost-effective router and webserver solutions that provide + ease-of-maintenance and flexibility to meet changing connection demands. + Our industrial quality systems run on the FreeBSD operating system. + The Z-Router provides a secure web interface to system maintenance + through a convenient online + configuration management tool.
      + Email: + info@zyzzyva.com. Voice: 402.438.1848. FAX: 402.438.1869. +

      • +
    + +

    Documentation and miscellaneous accessories

    +
      +
    • The Bookpool offers + 30% discounts on the new edition of + The Design and Implementation of the 4.4BSD Operating System, + a must-have for any FreeBSD bookshelf. +
      • +
    + +&footer; + + + diff --git a/data/daemon.sgml b/data/daemon.sgml new file mode 100644 index 0000000000..363b6e8636 --- /dev/null +++ b/data/daemon.sgml @@ -0,0 +1,62 @@ + + + %includes; +]> + +&header; + +

    The little red fellow that graces many of these pages is + the BSD Daemon. In the context of Unix systems, daemons + are process that run in the background attending to various + tasks without human intervention. In the general sense, + daemon is an older form of the word demon. In the Unix + System Administration Handbook, Evi Nemeth has this to + say about daemons:

    + +
    "Many people equate the word ``daemon'' with the + word ``demon,'' implying some kind of Satanic connection + between UNIX and the underworld. This is an egregious + misunderstanding. ``Daemon'' is actually a much older form + of ``demon''; daemons have no particular bias towards good + or evil, but rather serve to help define a person's + character or personality. The ancient Greeks' concept of a + ``personal daemon'' was similar to the modern concept of a + ``guardian angel'' --- ``eudaemonia'' is the state of being + helped or protected by a kindly spirit. As a rule, UNIX + systems seem to be infested with both daemons and demons." + (p403) +
    + +

    The earliest (and most popular) renditions of the BSD Daemon were + created by John Lassiter. More recent FreeBSD-specific + renditions have done by + + Tatsumi Hosokawa, but the basic inspiration was definitely John's. + + The copyright holder and creator of the daemon image is + Marshall Kirk McKusick. + A short pictorial + history is also available.

    + +

    Finally, it should also be noted that, despite Kirk's professed aversion + to this fact, there is close to unanimous agreement that the daemon's + name, should he have one at all, is Chuck. Don't ask + me how that name was arrived at, it just stuck. + +

    BSD Daemon Copyright 1988 by Marshall Kirk McKusick. All + Rights Reserved.

    + +

    Permission to use the daemon may be obtained from:

    + +
    Marshall Kirk McKusick
    1614 Oxford St
    + Berkeley, CA 94709-1608
    USA
    + +

    or via email at mckusick@mckusick.com. +

    + +&footer; + + + diff --git a/data/doc.ftr b/data/doc.ftr new file mode 100644 index 0000000000..38b0c7b771 --- /dev/null +++ b/data/doc.ftr @@ -0,0 +1,8 @@ +
    +FreeBSD Home + Page +
    + @@UPDATE@@
    + www@freebsd.org +
    + diff --git a/data/doc.hdr b/data/doc.hdr new file mode 100644 index 0000000000..e69de29bb2 diff --git a/data/docproj.sgml b/data/docproj.sgml new file mode 100644 index 0000000000..28f1ed0c0c --- /dev/null +++ b/data/docproj.sgml @@ -0,0 +1,176 @@ + + + %includes; +]> + +&header; + +

    Goals

    + +

    Unix has frequently, and rightfully so, been criticized + for being difficult to learn. While the tool based + approach to a computing system is powerful, users are often + stymied by the terse style of the manual pages that + describe each tool in detail but rarely provide hints about + how, when or why the tool can be used in day to day + operations. Many excellent books have been written to show + the tools in a context and a number are highly recommended + for anyone using FreeBSD. However, since every Unix system + has its own quirks, a number of gaps exist in the + documentation as a whole.

    + +

    The mission of the FreeBSD Documentation Project is to + fill this documentation gap. Specifically:

    + +
      +
    1. To cover features, procedures, and other quirks that + are unique to FreeBSD and thus not to be found in + commonly available Unix user, administrator and + programmer guides available on the market. The most + important of these are:

      +
        +
      • Installation

        • +
      • Hardware support and troubleshooting

        • +
      • System configuration and tuning

        • +
      +
      2. + +
    2. To provide documentation covering the most commonly + used aspects of FreeBSD, whether or not the topics are + covered in other user, administrator and programmer + guides. This includes topics such as:

      +
        +
      • Network configuration and troubleshooting

        • +
      • ISP services

        • +
      • General system adminstration

        • +
      +
      3. +
    + +

    Projects

    + +

    To realize the above goals, the Documentation Project is + focused on two specific pieces of documentation:

    +
      +
    1. The + FAQ
      2. +
    2. The + FreeBSD Handbook
      3. +
    + +

    The goal of the FAQ is to address in a + short question and answer format the most common questions + that are asked, or should be asked on the various + mailing lists and newsgroups devoted to the discussion of + FreeBSD. The format does not permit long winded and + comprehensive answers.

    + +

    Topics that need a more in depth discussion than the FAQ + can provide are addressed in the FreeBSD Handbook. + The current incarnation of the handbook is largely a + skeletal framework with many empty chapters and sections + waiting to be filled by words of wisdom.

    + +

    Contributing to the project

    + +

    Like the rest of the FreeBSD project, the documentation + project depends on the tireless contributions of users. To + facilitate the project, a mailing list has been created for + the discussion of documentation issues and communication + among authors. Anyone wishing to contribute to materials + or editorial time should subscribe by sending mail to majordomo@freebsd.org + with a message body of:

    + +
    subscribe freebsd-doc
    + +

    (See Mailing + lists in the handbook for complete information on the + FreeBSD mailing lists.)

    + +

    We welcome both corrections and additions to existing + documentation as well as submissions of entirely new + sections. All documents should reflect the state of + FreeBSD 2.0.5R unless there is a compelling reason to cover + a different release. In such a case, the version to which + the information applies must be clearly stated.

    + +

    Submitting corrections

    + +

    When providing corrections or additions to existing + documentation, the preferred method is context + diff relative to the text as it appears in + FreeBSD-current. (see the diff(1) manual page + for details on generating a context diff). The + FreeBSD-current text for the handbook can be found in:

    + +
    ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/doc/handbook
    + +

    while the FAQ can be found at:

    + +
    ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/doc/FAQ
    + +

    Diffs should be directed to doc@freebsd.org for + review.

    + +

    Submitting new material

    + +

    If you can claim expertise on some topic of interest to + other FreeBSD users and the topic is not covered by either + the FAQ or the Handbook, we would love to incorporate your + wisdom into one or the other. If you wish to contribute + but are not sure what is needed, have a good look through + the handbook and the + FAQ and see what + you think is missing. In particular, the handbook + has a fairly complete outline but sections marked with an + asterisk (*) are currently empty and waiting for an eager + author.

    + +

    At this time, the preferred format for submitting new + materials is SGML conforming to the linuxdoc DTD. The DTD + and tools for converting appropriately tagged documents + into LaTeX, HTML and ascii text are available in FreeBSD + 2.1 and -current. See the sgmlfmt(1) manual + page for details. Due to shortcomings of the linuxdoc DTD, + the project hopes to move to a more flexible DTD such as + DocBook in the future. Any changes will be announced on + the freebsd-doc mailing + list.

    + +

    If you do not feel comfortable with SGML, the next best + format is LaTeX because it can be converted to SGML with a + minimum of hassle. Failing that, plain ASCII submissions + are always welcome.

    + +

    Some general editorial guidelines:

    + +
      +
    • Do not use contractions.

      • + +
    • Provide concrete examples.

      • + +
    • Use cross references. In the HTML version of the + document, these become hypertext links.

      • + +
    • Do not duplicate other sections of the document, even + if they have yet to be written. If you feel the existing + section provides insufficient information to support your + topic, think about whether the additional information + should go in the section you are writing, or if it should + be added to the other end of the cross reference. + Contact the author of the referenced section if you + suspect the latter.

      • + +
    + +&footer + + diff --git a/data/docs.sgml b/data/docs.sgml new file mode 100644 index 0000000000..277e8963ce --- /dev/null +++ b/data/docs.sgml @@ -0,0 +1,60 @@ + + + %includes; +]> + +&header; + +

    The FreeBSD Handbook

    + +

    This is an evolving, comprehensive on-line resource for + FreeBSD users. Please address comments and contributions + to <doc@freebsd.org>. + +

    Frequently Asked Questions (FAQ)

    + +

    If you have a question, chances are that someone else has + the same question. The most common of these have been + compiled here in a brief question-answer format.

    + +

    Tutorials &i.new;

    + +

    Here lie assorted documents about FreeBSD and FreeBSD related + software and hardware.

    + +

    Books

    + +

    Online documentation is useful, but any serious FreeBSD + user should consider getting some of the books + listed here. Most books that cover BSD systems apply well + to FreeBSD.

    + +

    Manual + Pages

    + +

    The manual pages for FreeBSD 2.0 and XFree86 release 3.1, + courtesy of Hinrich + Eilts.

    + +

    The Source Code

    + +

    If you like digging your fingers into source code, here is + a hypetext version of the FreeBSD kernel source. + This is brought to you courtesy of Warren + Toomey.

    + +

    The FreeBSD Documentation Project

    + +

    Like FreeBSD itself, this documentation is the product of + a volunteer effort. The goals of the project are outlined + here, as are the procedures for submitting corrections and + new material.

    + +&footer; + + + diff --git a/data/gallery.sgml b/data/gallery.sgml new file mode 100644 index 0000000000..381ec51273 --- /dev/null +++ b/data/gallery.sgml @@ -0,0 +1,879 @@ + + + %includes; +]> + + +&header; + + + + +

    All over the world, FreeBSD is powering innovative + Internet applications and services. This gallery is a + showcase of organizations and individuals who have put + FreeBSD to work for them. Browse and find out more about + what FreeBSD can do for you! + +

    To have your site added to this list, simply fill out this form. + +

    The "Powered by FreeBSD" logos above may be downloaded and displayed + on personal or commercial home pages served by FreeBSD + machines. Use of this logo or the likeness of the + BSD + Daemons for profitable gain requires the consent of + Brian Tao (creator of the "power" + logo) and Marshall + Kirk McKusick's (trademark holder for the BSD Daemon image). + +

    Commercial organizations

    + + +

    Non-commercial organizations

    + + + +

    Personal sites

    + + + +&footer; + + diff --git a/data/gifs/Makefile b/data/gifs/Makefile new file mode 100644 index 0000000000..5a39c268e2 --- /dev/null +++ b/data/gifs/Makefile @@ -0,0 +1,5 @@ +DATA= apache.gif apachepower.gif daemon.gif dir.gif doc.gif +DATA+= freebsd-advert.gif home.gif littlelogo.gif new.gif power-button.gif +DATA+= powerlogo.gif ugu_icon.gif wclogo.gif + +.include "../web.mk" diff --git a/data/includes.sgml b/data/includes.sgml new file mode 100644 index 0000000000..7ec9333880 --- /dev/null +++ b/data/includes.sgml @@ -0,0 +1,39 @@ + + + + + +'> +'> + + + + + +www@freebsd.org
    + ©right;'> + +FreeBSD Home Page'> + + +&title; +

    &i.daemon; + &title;

    '> +&home;
    &author;
    &date;
    '> + + +'> +'> diff --git a/data/index-site.sgml b/data/index-site.sgml new file mode 100644 index 0000000000..fa7a0308f1 --- /dev/null +++ b/data/index-site.sgml @@ -0,0 +1,98 @@ + + + %includes; +]> + +&header; + + + + +&footer; + + + + + diff --git a/data/index.sgml b/data/index.sgml new file mode 100644 index 0000000000..62b15c6b4c --- /dev/null +++ b/data/index.sgml @@ -0,0 +1,99 @@ + + + + FreeBSD Inc. + + + +
    + The FreeBSD Home Page +
    + +

    + + + + + + + + + + + + + + + +
    +

    +About FreeBSD

    +

    +Latest FreeBSD Information

    +

    +Obtaining and Installing FreeBSD

    +

    +Release Information

    +

    +Application Software

    +

    +Documentation

    +

    +Support

    +

    +Commercial Products and Vendors

    +

    +The FreeBSD Gallery

    +

    +Search Mailing List Archives...

    + +

    +Quick Index

    +    		 +
    +Select a server near you:
    + +
    +
    +
    Sponsored By Walnut Creek CDROM / +
    Sponsored by UGU / +
    Powered By Apache +
    +
    + +
    +
    + Copyright © 1995, 1996 FreeBSD Inc. All rights reserved.
    + www@freebsd.org +
    +    		 + +
    + + + diff --git a/data/license.sgml b/data/license.sgml new file mode 100644 index 0000000000..bd077a6e89 --- /dev/null +++ b/data/license.sgml @@ -0,0 +1,99 @@ + + + %includes; +]> + +&header; + +

    All of the documentation and software included in the + 4.4BSD and 4.4BSD-Lite Releases is copyrighted by The + Regents of the University of California. + +

    Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, + 1993, 1994 The Regents of the University of California. + All rights reserved. + +

    Redistribution and use in source and binary forms, with or + without modification, are permitted provided that the + following conditions are met: + +

      + +
    1. Redistributions of source code must retain the above + copyright notice, this list of conditions and the + following disclaimer. + +
    2. Redistributions in binary form must reproduce the + above copyright notice, this list of conditions and the + following disclaimer in the documentation and/or other + materials provided with the distribution. + +
    3. All advertising materials mentioning features or use + of this software must display the following + acknowledgement: + +
      This product includes software developed by + the University of California, Berkeley and its + contributors.
      + +
    4. Neither the name of the University nor the names of its + contributors may be used to endorse or promote products + derived from this software without specific prior written + permission. +
      5. +
    + +

    THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS + ``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 REGENTS OR CONTRIBUTORS + 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 + SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH + DAMAGE. + +

    The Institute of Electrical and Electronics Engineers and + the American National Standards Committee X3, on + Information Processing Systems have given us permission to + reprint portions of their documentation. + +

    In the following statement, the phrase ``this text'' + refers to portions of the system documentation. + +

    Portions of this text are reprinted and reproduced in + electronic form in the second BSD Networking Software + Release, from IEEE Std 1003.1-1988, IEEE Standard Portable + Operating System Interface for Computer Environments + (POSIX), copyright C 1988 by the Institute of Electrical + and Electronics Engineers, Inc. In the event of any + discrepancy between these versions and the original IEEE + Standard, the original IEEE Standard is the referee + document. + +

    In the following statement, the phrase ``This material'' + refers to portions of the system documentation. + +

    This material is reproduced with permission from American + National Standards Committee X3, on Information Processing + Systems. Computer and Business Equipment Manufacturers + Association (CBEMA), 311 First St., NW, Suite 500, + Washington, DC 20001-2178. The developmental work of + Programming Language C was completed by the X3J11 Technical + Committee. + +

    The views and conclusions contained in the software and + documentation are those of the authors and should not be + interpreted as representing official policies, either + expressed or implied, of the Regents of the University of + California. + +&footer; + + diff --git a/data/mailto.sgml b/data/mailto.sgml new file mode 100644 index 0000000000..fbde8303fc --- /dev/null +++ b/data/mailto.sgml @@ -0,0 +1,32 @@ + + + %includes; +]> + +&header; + +

    Questions about this WWW server...

    + +

    Questions regarding this World Wide Web server should be + addressed to www@freebsd.org.

    + +

    Questions about the contents of this WWW server...

    + +

    Questions or suggestions about our documentation + (Handbook, FAQ, + Tutorials) should be addressed to doc@freebsd.org.

    + +

    Questions about FreeBSD...

    + +

    Questions regarding FreeBSD should be addressed to questions@freebsd.org. + For general information about FreeBSD, send a message to + info@freebsd.org and + you will recieve an automatic reply.

    + +&footer; + + diff --git a/data/newsflash.sgml b/data/newsflash.sgml new file mode 100644 index 0000000000..e654333022 --- /dev/null +++ b/data/newsflash.sgml @@ -0,0 +1,585 @@ + + + %includes; +]> + +&header; + +

    FreeBSD is a is a rapidly developing operating system. + Keeping up on the latest developments can be a chore! To + keep on top of things, be sure and check this page + periodically. Also, you may wish to subscribe to the freebsd-announce + mailing list.

    + +

    August 1996

    + + +

    July 1996

    + + +

    June 1996

    +
      +
    • 27-June-1996 + The + 2.1-960627 + snapshot has been released. + It is equivalent to a 2.1.5-BETA release.

      + +
    • 25-June-1996
      + The stuffed daemon plushies are now shipping from + Liebscher & Partner. + Please contact the company via email for more details. A picture + of an early prototype is here. Do note that + this is a prototype and that the final, shipping version has + had some improvements made to it.

      + +
    • 12-June-1996
      + The + 2.2-960612 + snapshot + has been released. The new features of this snapshot are:

      +
        +
      • A considerable number of changes to the VM system have been made + to increase the stability under certain types of load. If you + had panics under the last snapshot, try this one and see if they + persist.
        • + +
      • The AHC driver now does considerably more in the way of handling + error conditions gracefully.
        • + +
      • More cosmetic work on the installation, /stand/sysinstall now + genuinely useful after installation time (though still missing a man + page - urk!).
        • + +
      • Basically, lots-o-fixes. If you're trying to use the 2.2 SNAPs + in more serious applications, please upgrade to this version.
        • +
      + + [Note: This release will not be made available on CDROM to 2.2-SNAP + subscribers]. +
    + +

    May 1996

    +
      +
    • 1-May-1996
      + The + 2.2-960501 + snapshot + has been released. The new features of this snapshot are:

      +
        +
      • Early support for APM (automated power management) and PCCARD + (formerly PCMCIA) features of laptops. Many PCCARD devices + are supported, from modems to ethernet cards to SCSI adaptors.
        • + +
      • Adaptec AIC7850 support has been added.
        • + +
      • The Yellow Pages (NIS) support has had many optimizations made + and no longer has portions copyright under the GPL.
        • + +
      • Various VM system enhancements and a few bugs fixed (gzip'd + binaries now work again, for example).
        • + +
      • The system installation tool has been revamped with slightly + different menu behavior and a number of bugs have been fixed. + It's hoped that this installation will be more intuitive for new + users than previous ones (feedback welcomed, of course).
        • + +
      • Much miscellaneous cleanup work with the header files and sources. +
        • +
      +
    + +

    April 1996

    + +
      +
    • 15-Apr-1996
      A new + FreeBSD-emulation + mailing list has been created for discussing ongoing development efforts + for DOS, Windows, Linux and other forms of binary emulation.

      • + +
    • 14-Apr-1996
      + Berkeley Software Design, Inc. has donated their DOS emulator + rundos to the BSD community! Work is now ongoing in integrating + this into FreeBSD, and interested parties can + join the + FreeBSD-emulation mailing list to find out more about how + this work is progressing.

      • +
    + +

    March 1996

    + +
      +
    • 23-Mar-1996
      + The + 2.2-960323 + snapshot + has been released. The new features of this snapshot are:

      +
        +
      • The Intel EtherExpress Pro/100B PCI ethernet card is now + supported.
        • + +
      • The 3COM 3C590 and 3C595 ethernet cards are now supported.
        • + +
      • The ARNET (now Digiboard) Sync 570i high-speed serial card is + now supported.
        • + +
      • The Linux emulation is now good enough to run the Linux version + of Netscape, with JAVA support (as well as a number of other Linux + utilities).
        • + +
      • The Matrox Meteor frame grabber card is better supported.
        • + +
      • It is now possible to burn CDROMs using the Plasmon or HP 4080i + CDR drives (see `wormcontrol(1)').
        • + +
      • The pipe code has been substantially sped up, as have some + components of the VM system.
        • + +
      • A /dev/random device (and associated "pool of entropy") has + been added for applications which require more unpredicatable + sequences of random numbers for security. See the random(4) + man page for more info.
        • + +
      • Early NFS v3 support (not enabled by default).
        • + +
      • An early implementation of the Device Filesystem (devfs) + is available (see mount_devfs). Device switch tables are now + also dynamically built.
        • + +
      • Early IPX routing support.
        • +
      +
    + +

    November 1995

    + +
      +
    • 19-Nov-1995
      FreeBSD 2.1 is now available at + ftp sites all around the world. See the Release information for + details.

      • + +
    • 4-Nov-1995
      Snapshot 2.1.0-951104 is now + available. The purpose of this snapshot is:

      +
        +
      • To incorporate changes based on all the feedback + and bug reports received for the previous + snapshot's installation.
        • + +
      • To incorporate the latest XFree86 release (3.1.2-S) + with security enhancements. There may be more fairly + minor changes here before 2.1 is put on CD, but this + is basically what will be shipping.
        • + +
      • To get feedback on the new ``Novice Install'' split + out of the Express installation (which now truly is + an express installation).
        • + +
      • To give folks something a little less buggy to load on new + systems while they are waiting for 2.1 to come out.
        • + +
      • To fold in the latest versions of the FreeBSD + Handbook, updated for 2.1.
        • + +
      • To correct some slight whiffy english in the online help.
        • + +
      • To go back to the previous approach of just + uncommenting the ATAPI and wcd0 entries in GENERIC + for building atapi.flp. The idea of commenting out + the wd2 and wd3 entries in an effort to make things + better seems to have only made them worse in the last + SNAP. If this atapi.flp image works for you, great! + If not, I'm afraid that it's far too late to do + anything about at this stage so any failure reports + will be simply filed for post-2.1 analysis. Sorry + IDE CDROM hackers, but you had your chance!
        • +
      +
      • +
    + +

    October 1995

    + +
      + +
    • 30-Oct-1995
      The 2.1.0-951026 Snapshot has been + re-released with several bugfixes:

      + +
        +
      • Atapi boot floppy now assumes it's alone by itself + on the second IDE controller - this seems to work a + lot better for most folks who were provided with + dedicated controllers when they purchased their IDE + CDROMS. People with IDE disks on multiple IDE + controllers should NOT use this floppy image. Stick + with boot.flp and build a custom kernel or something.
        • + +
      • The apache WEB server installation makes fewer assumptions about + where you'll be putting things.
        • + +
      • Installing the secure dist no longer requires that you also + install Kerberos in order to get things like telnet to work.
        • + +
      • Boot floppy should now support the Adaptec 2940 ULTRA (this was + a side-effect more than a bug fix).
        • +
      +

      However, there are some outstanding bugs you should know + about:

      +
        +
      • sysinstall seems to croak in certain situations + if you run it after the system is installed.
        • + +
      • The FTP retry code still isn't 100% there - + apparently it now doesn't handle reselection very + well. Sigh. I'm so truly sick of looking at that + part of the code that if somebody else wanted to have + a look, I wouldn't fight them off! It seems like + every time I fix one thing, I break something else.
        • + +
      • The media selection screen protects itself from + re-entry in some situations when you'd really like it + to be allowed. Whoops!
        • +
      • Using more than one FreeBSD ``slice'' can cause problems.
        • +
      +

      • + +
    • 26-Oct-1995
      Snapshot + 2.1.0-951026 is now available. New fixes/features + include:

      +
        +
      • All /etc/sysconfig information now written correctly.
        • + +
      • WEB server option now works properly.
        • + +
      • The package installation menu now works.
        • + +
      • All the auto-installation instrumentation + (installation by config file) now works. It's + possible to install everything from start to finish + on a new system in a fully-automated fashion (if you + install a lot of systems, this is a big help).
        • + +
      • You may now read the HTML Handbook and FAQ + documents directly from the boot floppy after + installation (as well as visit any other WEB site).
        • + +
      • Failure to create a /usr is no longer an error, + just a warning.
        • + +
      • The matcd driver was shrunk down some more, + possibly resulting in a return to 4MB + operation (please test this).
        • + +
      • The latest ATAPI CDROM changes were merged in and + another atapi.flp boot image generated. Again, + please test.
        • +
      +

      • + +
    • 22-Oct-1995
      Updated floppies for snapshot + 2.1.0-951020 are now available.

      • + +
    • 20-Oct-1995
      Release cannidate snapshot + 2.1.0-951020 is now available.

      • + +
    • 06-Oct-1995
      Updateded floppies for snapshot + 2.1.0-951005 are now available.

      • + +
    • 05-Oct-1995
      Snapshot + 2.1.0-951005 is now available.

      • + +
    + +

    September 1995

    + +
      + +
    • 29-Sep-1995
      Snapshot + 2.1.0-950928 is now available.
      • + +
    + +

    August 1995

    + +
      + +
    • 19th: An IDE CD-ROM driver has been added to + FreeBSD-current, thanks to Serge Vakulenko. If you are + running -current, the driver can be enabled by + adding:
      options ATAPI
      device + wcd0
      to your kernel configuration file, + rebuilding the kernel and rebooting. Please let us know + if you have problems by sending a message to bugs@freebsd.org.
      • + +
    + +

    July 1995

    + +
      + +
    • 27-Jul-1995
      Snapshot 950726 is + now available.
      • + +
    + +

    June 1995

    + +
      + +
    • 23-Jun-1995
      Snapshot 950622 is + now available. Bugs fixed and new features include:

      +
        +
      • SLIP installation didn't ``ifconfig sl0'' + properly.
        • + +
      • It was not possible to do certain operations + atomically, e.g. just write out fdisk information, + or just extract distributions. This can now be done + from the Custom Install menu.
        • + +
      • There is now an Express Install menu that + leads you through all the necessary steps.
        • + +
      • /usr/src/bin is now properly extracted as + part of the source distribution.
        • + +
      • A couple of panics in the kernel are now fixed.
        • + +
      • DOS filesystems are now mounted read-only by + default until we figure out what it is about R/W DOS + filesystems that clobbers some systems. +
        • +
      + +

      As always, this snapshot is offered as a complete + replacement for the previous release and is aimed at + new users installing the system from scratch. Still no + update mechanism yet, but there are rumors of a project + being formed to deal with this soon. If you've any + interest in being part of it, then please send mail to + hackers@freebsd.org. + I'll also be getting involved in the whole update + mechanism issue since it's been a gaping hole for far + too long now and I'd like to see a solution sooner + rather than later. I'm sure that many of our users + feel the same way!

      +
      • + +
    • 12-Jun-1995
      Because of some glitches in the + 2.0.5 RELEASE boot disks, an update has been provide at + ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-RELEASE/UPDATES

      • + + +
    • 10-Jun-1995
      FreeBSD 2.0.5 RELEASE has been + released! See the announcement + and release notes for more details.

      • + +
    • 5-Jun-1995
      Even more installation bugs have been + fixed. Please check + ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-ALPHA/UPDATES/ + for the latest installation disks if you encounter + problems.

      • + +
    • 1-Jun-1995
      Following extensive feedback from + the ALPHA release, A new installation disk has been + generated with numerous bug fixes and enhancements. It + is available via anonymous ftp from + ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-ALPHA/UPDATES/
      • +
    + +

    May 1995

    + + + +

    April 1995

    + +
      +
    • 14-Apr-1995
      Snapshot 950412 is now + available. New features include:

      +
        +
      • Even more bugs fixed.
        • +
      • Driver for Matsushita CDROM ("Sound blaster" CDROM) in second + revision - it now supports audio commands.
        • +
      • Driver for Adaptec 294x improved.
        • +
      • FDDI network interface support (DEC cards) improved.
        • +
      • Support for DEC 100Mbit "FAST" ethernet cards (DE 500-XA).
        • +
      • /etc files revamped fairly significantly - most customization + done through one file now, /etc/sysconfig.
        • +
      • Performance improvements to networking code (connection + information now hashed rather than being stored in a linear linked + list).
        • +
      • Package code improved - now supports package dependencies.
        • +
      • New version of "libforms".
        • +
      + +

      Known problems:

      +
        +
      • If you want to run programs linked under 2.0, you + will need the file libgcc.so.261.0 which can be found + in the same directory as the snapshot release. The + file should be placed in in /usr/lib once you have + installed the release.
        • +
      • The hostname still isn't being set properly in + /etc/sysconfig for some reason - you should edit this + file after the initial installation and customize it + for your system. The comments in the file should + make the fields you need/want to change pretty + self-explanatory.
        • +
      • +
    + +

    March 1995

    + +
      +
    • 22-Mar-1995
      Snapshot 950322 is now + available. New features include:

      + +
        +
      • NIS (YP) server/client support for FreeBSD much + improved.
        • +
      • A number of panic bugs fixed.
        • +
      • Merged VM/Buffer cache much improved - hopefully last of the bugs + fixed!
        • +
      • Faster wd.c driver
        • +
      • Driver for Intel EtherExpress card
        • +
      • Driver for Matsushita CDROM ("Sound blaster" CDROM)
        • +
      • Better disk access algorithms ("clustering").
        • +
      • PCI support much improved. Interrupt sharing now works.
        • +
      • Driver for Adaptec 294x much improved
        • +
      • Boot -c writeback/save program (customized info saved across + reboots)
        • +
      • Soundcard support greatly cleaned up
        • +
      • Prototype support for ISDN
        • +
      • Support for the Creative Labs Video Spigot(tm) video card.
        • +
      • FDDI network interface support (DEC cards).
        • +
      • TCP/IP Firewall code much improved.
        • +
      • GCC 2.6.3 integrated
        • +
      + +

      If you want to run programs linked under 2.0, you will need + the file libgcc.so.261.0 which can be found in the same + directory as the snapshot release. The file should be placed + in in /usr/lib once you have installed the release.

      • + +
    + +

    February 1995

    + +
      +
    • 10-Feb-1995
      + Snapshot 950210 is now + available. New features include:

      + +
        +
      • Screen swapping bug with syscons fixed
        • +
      • XFree86 3.1.1
        • +
      • NIS (YP) support for FreeBSD much improved
        • +
      • A number of panic bugs fixed.
        • +
      • Everything listed in the February 2nd SNAP README but + much improved!
        • +
      +

      • + +
    • 2-Feb-1995:
      Snapshot + 950202 is now available. New features include:

      + +
        +
      • Merged VM/Buffer cache much improved! General + stability now approaching 2.1 quality levels.
        • +
      • Lots more bug fixes
        • +
      • Syscons now supports scrollback - use scroll lock and + arrow/travel keys to move around in your scroll-back buffer.
        • +
      • NIS (YP) support for FreeBSD as server and client.
        • +
      • First cut at on-demand ppp dialing. Docs still in + Japanese, but we're working on that! See /usr/bin/ppp + for more details.
        • +
      • IP Firewall code much improved
        • +
      • AHA294x controller support now added
        • +
      • Sony CDU33a CDROM drive support added
        • +
      • Source distribution now split into logical pieces
        • +
      • Install much improved - still not what will be + in 2.1, but a lot easier to use nonetheless.
        • +
      +
      • +
    + +

    January 1995

    + +
      +
    • 12-Jan-1995
      Snapshot + 950112 is now available. New features include:

      +
        +
      • Merged VM/Buffer cache! Does it work? Is it + faster? Find out! This is the culmination of over 6 + months of careful hacking.
        • +
      • Lots-o-bug fixes
        • +
      • Lots-o-bugs (probably)
        • +
      • Fixes to floppy driver - may fix some of the reported + problems.
        • +
      • Genius GS-4500 Scanner driver; scan pictures from FreeBSD!
        • +
      • Fixes for U24F SCSI controller
        • +
      • Many fixes to Seagate driver - Future Domain people please + test!
        • +
      • GNU Info files resurrected from the dead (see infodist)
        • +
      • share/doc now quite a bit more functional.
        • +
      • A number of new syscons features - software settable cursor, + more modes for LCD displays, dynamic console allocation, woo + doggies.
        • +
      • Still no kernel srcdist, just one big srcdist still. + Sorry.
        • +
      • Lots of changes to the installation - hopefully this one even + mostly works for once.
        • +
      • A billion other things I've forgotten for now but will + remember right after I save this document.
        • +
      +
      • +
    + +

    December 1994

    + +
      +
    • 7-Dec-1994
      If you are having trouble with + installing Release 2.0 please check + + ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE/floppies + to see if you have the most recent installation floppies. + The all new installation procedure for 2.0 brought with + it a whole set of all new bugs. With the latest + installation floppies, we hope that these bugs are fixed. +
      • +
    + +&footer; + + diff --git a/data/ports/Makefile b/data/ports/Makefile new file mode 100644 index 0000000000..09cc722be8 --- /dev/null +++ b/data/ports/Makefile @@ -0,0 +1,21 @@ +PORTINDEX= ./portindex + +.if exists(Makefile.gen) +.include "Makefile.gen" +CLEANFILES+= ${DOCS} Makefile.gen +COOKIE= Makefile.gen +.include "../web.mk" +.else +foo .DEFAULT: + ${MAKE} ${MAKEFLAGS} Makefile.gen + ${MAKE} ${MAKEFLAGS} ${.IMPSRC} +.endif + +Makefile.gen: index.sgml .NOTMAIN + if [ -f Makefile.gen ]; then mv Makefile.gen Makefile.gen.bak; fi + echo DOCS= *.sgml > Makefile.gen + +index.sgml: ports/INDEX .NOTMAIN + rm -f *.sgml + ${PORTINDEX} ports/INDEX + diff --git a/data/ports/portindex b/data/ports/portindex new file mode 100755 index 0000000000..3890433595 --- /dev/null +++ b/data/ports/portindex @@ -0,0 +1,163 @@ +#!/usr/bin/perl + +# convert a ports INDEX file to HTML +# +# by John Fieber +# Mon May 13 10:31:58 EST 1996 + +############################################################ + +# This is the base of where we ftp stuff from +$base = "ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current"; + +$today = &getdate; + +&main; + +sub getdate { + @months = ("January", "February", "March", "April", "May","June", + "July", "August", "September", "October", "November", "December"); + ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); + $year += 1900; + return "Updated $months[$mon] $mday, $year"; +} + +sub header { + local ($fh, $htext) = @_; + print $fh ""; + print $fh "$today    \">\n"; + print $fh ""; + print $fh "\n"; + print $fh "\n"; + print $fh "%includes;\n"; + print $fh "]>\n"; + print $fh "&header;\n"; +} + +sub footer { + local ($fh, $ftext) = @_; + print $fh "\n$ftext\n"; + print $fh "&footer;\n"; + print $fh "\n\n"; +} + +sub main { + + while (<>) { + chop; + s//>/g; + + ($name, $loc, $prefix, $desc, $ldesc, $owner, $cats, + $keys, $bdep, $rdep) = split('\|'); + + @cat = split(" ", $cats); + + $catkey{$name} = $cat[0]; + + $sep = ":"; + + foreach $i (@cat) { + + $stats{$i}++; + + # figure out the FTP url + $loc =~ s/\/usr/$base/; +# $loc =~ s/\/$name$//; + $ldesc =~ s/\/usr/$base/; + + # The name description and maintainer + $data{$i} .= "
    $name
    $desc
    "; + $ownerurl = $owner; + $ownerurl =~ s/<//g; + $data{$i} .= + "Maintained by: $owner
    "; + + # If there are any dependencies, list them + if ($bdep ne "" || $rdep ne "") { + $data{$i} .= "Requires: "; + @dep = split(/ /, "$bdep $rdep"); + foreach $j (@dep) { + $data{$i} .= " $j,"; + } + # remove the trailing comma + chop $data{$i}; + $data{$i} .= "
    "; + } + + # Links for browsing and downloading + $data{$i} .= "Description $sep "; + $data{$i} .= "Browse $sep "; + $data{$i} .= "Download"; + + # If the port is listed in more than one category, throw + # in some cross references + if ($#cat > 1) { + $data{$i} .= "
    Also listed in: "; + foreach $j (@cat) { + if ($j ne $i) { + $data{$i} .= " \u$j,"; + } + } + # remove the trailing comma + chop($data{$i}); + } + $data{$i} .= "

    \n" + } + + # Add an entry to the master index + $master[$portnumber] = + "$name " . + " -- $desc
    \n"; + $portnumber++; + } + + open(MOUTF, ">index.sgml"); + + &header(MOUTF, "FreeBSD Ports"); +# print MOUTF "\n"; + print MOUTF "&blurb;"; + print MOUTF "

    There are currently $portnumber ports is the +FreeBSD Ports Collection.
    Download +a gzip'd tar file of all $portnumber ports (about 2 megabytes) or +browse the following categories:\n"; + + print MOUTF "

      \n"; + + @foos = sort(keys %stats); + foreach $key (@foos) { + # For the master file... + print MOUTF + "
    • \u$key ($stats{$key})
      • "; + + # Create the category file + open(OUTF, ">$key.sgml"); + &header(OUTF, "FreeBSD Ports: \u$key"); + print OUTF "
      \n"; + $d = join("\n", sort(split(/\n/, $data{$key}))); + $d =~ s/##([^#]*)##/$catkey{$1}/g; + print OUTF $d; + print OUTF "
      \n"; + &footer(OUTF, "
      Port Categories" . + " -- Index"); + close(OUTF); + + } + print MOUTF "
    \n"; + print MOUTF + "\n"; + &footer(MOUTF, ""); + close(MOUTF); + + # Create the master index file + open(MINDEX, ">master-index.sgml"); + &header(MINDEX, "FreeBSD Ports Collection Index"); + print MINDEX "

    \n"; + print MINDEX sort @master; + print MINDEX "

    "; + &footer(MINDEX, "
    Port Categories"); + close(MINDEX); + +} diff --git a/data/ports/ports.inc b/data/ports/ports.inc new file mode 100644 index 0000000000..0dfe1ee34c --- /dev/null +++ b/data/ports/ports.inc @@ -0,0 +1,34 @@ +

    The FreeBSD Ports Collection offers a simple way for users and +administrators to install applications. Each ``port'' listed here +contains any patches necessary to make the original application source +code compile and run on FreeBSD. Installing an application is as +simple as downloading the port, unpacking it and typing make +in the port directory. The Makefile automatically fetches the +application source code, either from a local disk or via ftp, +unpacks it on your system, applies the patches, and compiles. If +all goes well, simply type make install to install the +application.

    + +

    Below are the listings of ports currently available, arranged +by application type. Four links are available for each port listed:

    + +
    +
    Description
    This fetches a description +of the application from the FTP archive (ftp.freebsd.org).
    + +
    Browse
    This is a link to the FTP archive directory +for the port where you can examine the Makefile and patches.
    + +
    Download
    This is a link to a gzip'd tar file +containing the port. Be sure to tell your browser to save +rather than display!
    + +
    Maintainer
    The person responsible for maintaining +the port. If you have problems with a specific port, +contact this person.
    +
    + +

    For more information, see The +ports collection and Porting applications in the FreeBSD Handbook.

    diff --git a/data/releases/1.1.5/CONTRIB.386BSD b/data/releases/1.1.5/CONTRIB.386BSD new file mode 100644 index 0000000000..a99b527c48 --- /dev/null +++ b/data/releases/1.1.5/CONTRIB.386BSD @@ -0,0 +1,196 @@ + + + + + + + + 386BSD Release 0.1 + Contributor List + + Lynne Greer Jolitz + William F. Jolitz + + +_H_a_r_d_w_a_r_e _a_n_d _M_o_n_e_t_a_r_y _C_o_n_t_r_i_b_u_t_o_r_s + +Many people and firms have provided hardware and/or money to +try and keep this unfunded project going despite a recession +and hard times -- usually by digging into their own pockets. +Each of these contributors gave, not only because they +believed that the continuation of 386BSD is vital to the +health of the research, educational, and development commun- +ities, but also because they realize that an individual can +and does make a difference! + +Without the help of the people listed here, this release +would simply not have been possible. We would especially +like to thank Thos Sumner, whose loan of a 486/50 SCSI PC +made development go more rapidly. The rest of the 386BSD +user community should make special note of all these people +and firms and commend them for their generosity and +foresight. + +We hope that their leadership and vision will serve as shin- +ing examples to the entire 386BSD user community, and serve +to encourage others to actively participate in 386BSD. + + Jan van den Bosch + Compaq Computer Corporation + Cyrix Corporation + Dixon Dick + Steven P. Donegan + Jon Erickson + Eric J. Haug + Bob McGhee + Jesus Monroy Jr. + Andrew Moore + Rich Murphey + Mark Ng + Kenji Okamoto + John Plocher + Mark R. Riordan + John B. Scalia + Steve Sizemore + Thos Sumner + David E. Tweten + + + + + +386BSD CONTRIB LIST 1 July 1992 + + + + + + + + + + +_S_o_f_t_w_a_r_e _C_o_n_t_r_i_b_u_t_o_r_s + +The following people have contributed key software programs, +modules and fixes, including novel work and ports of popular +public domain user programs. Some of this software was +directly contributed to us, while other items were made +available to all users via the network. Occasionally, +several people came up with a variety of approaches for a +single item. In this instance, we tried to choose the one +which we felt would best serve the rest of the 386BSD user +base for this release. However, the creativity and persever- +ance of all the software contributors trying to make 386BSD +better for the entire 386BSD user community was consider- +able. Each individual effort is worthy of pride. + +We wish to personally thank all of these people, as they +have helped make 386BSD Release 0.1 a reality. We hope that +these contributors and all the rest of the 386BSD user com- +munity will continue to actively participate to make future +releases even better! + + James Van Artsdalen + Scott Burris + Randall Dean + Chris Demetriou + Mark Eichin + Bruce Evans + Steve Ferguson + Jeffrey Goh + David Greenman + Amancio Hasty Jr + John W. Hatley + Eric J. Haug + Tom Ivar Helbekkmo + John D. Irwin + Peter Klingebiel + Paul Kranenburg + Daniel Lanciani + Karl Lehenbauer + Lee M. J. McLoughlin + Andrew J. Michael + Jesus Monroy Jr. + Daniel A. Muntz + Richard Murphey + Glen Overby + Brad Parker + Herb Pereyl + Ken Raeburn + Paul Richards + Guido van Rooij + Peng-Toh Sim + Wolfgang Solfrank + Dave Stanhope + + +386BSD CONTRIB LIST 2 July 1992 + + + + + + + + + + + Mark Tinguely + Linus Torvalds + Richard Tobin + Rob Warnock + Christian Wiedmann + Pace Willisson + Joerg Wunsch + + And all of the other 386BSD Software Contributors. + + +_S_u_p_p_o_r_t _a_n_d _A_d_v_i_c_e _C_o_n_t_r_i_b_u_t_o_r_s + +Many people have continually encouraged us over the course +of these releases, and provided us with technical advice and +guidance. These people have also spent considerable time and +energy getting this software out to the rest of the 386BSD +community. While it is impossible for us to list everyone +who has been supportive of 386BSD, we wish to personally +thank some of the people who have been of special assistance +to us directly over the course of getting 386BSD out the +door. + + Bruce Blakely + Dave Campbell + Free Software Foundation + Paul Fromberg + Tom Genereaux + John Gilmore + Dave Harris + Jim Joyce + Dan Kionka + Dory Leifer + Per Lindqvist + Marshall Midden + Rich Morin + Silicon Valley Computer Society + John Sokol + Thos Sumner + Karen Trocki + Rob Warnock + + and a special thanks to: + John Erickson, Tami Zemel, Ray Valdez, Monica Berg, Michael Floyd + and everyone else at Dr. Dobbs Journal. + Juergen Fey, Rainer Huttenloher, Gerd Oskar Bausewein + and everyone else at UNIX Magazin. + + And all of the 386BSD User Community. + + + + + +386BSD CONTRIB LIST 3 July 1992 + + + diff --git a/data/releases/1.1.5/CONTRIB.FreeBSD b/data/releases/1.1.5/CONTRIB.FreeBSD new file mode 100644 index 0000000000..37bae9cb03 --- /dev/null +++ b/data/releases/1.1.5/CONTRIB.FreeBSD @@ -0,0 +1,191 @@ + FreeBSD 1.1.5 + Contributor List + + + +Derived Software Contributors: + +This software was originally derived from William F. Jolitz's 386BSD +release 0.1, though very little of the original 386BSD specific code +remains. + +Please see the file CONTRIB.386BSD for the list of contributors from +386BSD. + +Included in this release are some of the patches from the old 386BSD +patch kit version 0.2.4, and therefore the names of contributors from the +patch kit are also listed below. + +Finally, there are portions of NetBSD that have been integrated into +FreeBSD as well, and we would therefore like to thank all the contributors +to NetBSD for their work. + + +Hardware Contributors: + +A special thanks to Robert Bruce and Jack Velte of Walnut Creek CDROM +for providing a 486/DX2-66 EISA/VL system that is being used for the +development work. It would have been impossible to do this release +with out their support. + +Dermot McDonnell for his donation of a Toshiba XM3401B CDROM +drive. + + +The FreeBSD Core Team (in alphabetical order): + +Andrew A. Chernov +John Dyson +David Greenman +Rodney W. Grimes +Jordan K. Hubbard +Scott Mace +Andrew Moore +Rich Murphey +Geoff Rehmet +Paul Richards +Andreas Schulz +Nate Williams +Garrett A. Wollman + + +Additional FreeBSD Contributors (no particular order): + +Atsushi Murai +Keith Moore +Adam Glass +Andrew Herbert +Bob Wilcox +Bruce Evans +Charles Hannum +Chris G. Demetriou +Chris Torek +Christoph Robitschko +Curt Mayer +Dave Burgess +Dave Rivers +David Dawes +Frank Maclachlan +Gary A. Browning +Gary Clark II +Guido van Rooij +Havard Eidnes +Holger Veit +Ishii Masahiro, R. Kym Horsell +J.T. Conklin +James Clark +James da Silva et al +Jim Wilson +Joerg Wunsch +Julian Elischer +Julian Stacey > +Keith Bostic +Marc Frajola +Mark Tinguely +Martin Birgmeier +Paul Kranenburg +Paul Mackerras +Poul-Henning Kamp +Rob Shady +Sascha Wildner +Sean Eric Fagan +Serge V. Vakulenko +Steven Wallace +Søren Schmidt +Terry Lee +Theo Deraadt +Yuval Yarom + + +Patch kit patch contributors (no particular order): + +Adam Glass +Adrian Hall +Andrew A. Chernov +Andrew Herbert +Andrew Moore +Andy Valencia +Arne Henrik Juul +Bakul Shah +Barry Lustig +Bob Wilcox +Branko Lankester +Brett Lymn +Bruce Evans +Charles Hannum +Chris G. Demetriou +Chris Torek +Christoph Robitschko +Daniel Poirot +Dave Burgess +Dave Rivers +David Dawes +David Greenman +Eric J. Haug +Felix Gaehtgens +Frank Maclachlan +Gary A. Browning +Geoff Rehmet +Goran Hammarback +Guido van Rooij +Guy Harris +Havard Eidnes +Herb Peyerl +Ishii Masahiro, R. Kym Horsell +J.T. Conklin +Jagane D Sundar < jagane@netcom.com > +James Clark +James Jegers +James W. Dolter +James da Silva et al +Jay Fenlason +Jim Wilson +Joerg Lohse +Joerg Wunsch +John Dyson - +John Woods +Jordan K. Hubbard +Julian Elischer +Julian Stacey > +Karl Lehenbauer +Keith Bostic +Ken Hughes +Kent Talarico +Kevin Lahey +Marc Frajola +Mark Tinguely +Martin Renters +Michael Galassi +Mike Durkin +Nate Williams +Nick Handel +Pace Willisson +Paul Kranenburg +Paul Mackerras +Paul Popelka +Peter da Silva +Phil Sutherland +Poul-Henning Kamp +Ralf Friedl +Rich Murphey +Rick Macklem +Robert D. Thrush +Rodney W. Grimes +Rog Egge +Sascha Wildner +Scott Burris +Scott Reynolds +Sean Eric Fagan +Simon J Gerraty +Stephen McKay +Terry Lambert +Terry Lee +Warren Toomey +Wiljo Heinen +William Jolitz +Wolfgang Solfrank +Wolfgang Stanglmeier +Yuval Yarom + +$Id: CONTRIB.FreeBSD,v 1.1.1.1 1996-09-24 17:45:48 jfieber Exp $ diff --git a/data/releases/1.1.5/COPYRIGHT.386BSD b/data/releases/1.1.5/COPYRIGHT.386BSD new file mode 100644 index 0000000000..c53cb8865b --- /dev/null +++ b/data/releases/1.1.5/COPYRIGHT.386BSD @@ -0,0 +1,131 @@ + + + + + + + + 386BSD Release 0.1 + Copyright + + + /* + * Copyright (c) 1989, 1990, 1991, 1992 William F. Jolitz, TeleMuse + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. All advertising materials mentioning features or use of this software + * must display the following acknowledgement: + * This software is a component of "386BSD" developed by + * William F. Jolitz, TeleMuse. + * 4. Neither the name of the developer nor the name "386BSD" + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * 386BSD WAS DEVELOPED BY WILLIAM F. JOLITZ. + * 386BSD IS INTENDED FOR RESEARCH AND EDUCATIONAL PURPOSES. + * THIS SOFTWARE SHOULD NOT BE CONSIDERED TO BE A COMMERCIAL PRODUCT. + * THE DEVELOPER URGES THAT USERS WHO REQUIRE A COMMERCIAL PRODUCT + * NOT MAKE USE OF THIS WORK. + * + * FOR USERS WHO WISH TO UNDERSTAND THE 386BSD SYSTEM DEVELOPED + * BY WILLIAM F. JOLITZ, WE RECOMMEND THE USER STUDY WRITTEN + * REFERENCES SUCH AS THE "PORTING UNIX TO THE 386" SERIES + * (BEGINNING JANUARY 1991 "DR. DOBBS JOURNAL", USA AND BEGINNING + * JUNE 1991 "UNIX MAGAZIN", GERMANY) BY WILLIAM F. JOLITZ AND + * LYNNE GREER JOLITZ, AS WELL AS OTHER BOOKS ON UNIX AND THE + * ON-LINE 386BSD USER MANUAL BEFORE USE. A BOOK DISCUSSING THE INTERNALS + * OF 386BSD ENTITLED "386BSD FROM THE INSIDE OUT" WILL BE AVAILABLE LATE 1992. + * + * THIS SOFTWARE IS PROVIDED BY THE DEVELOPER ``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 DEVELOPER 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 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + */ + + + 386BSD Copyright 1 July 1992 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 386BSD Copyright 2 July 1992 + + + + diff --git a/data/releases/1.1.5/COPYRIGHT.FreeBSD b/data/releases/1.1.5/COPYRIGHT.FreeBSD new file mode 100644 index 0000000000..58c827bcd2 --- /dev/null +++ b/data/releases/1.1.5/COPYRIGHT.FreeBSD @@ -0,0 +1,122 @@ +This software contains software developed by the University of +California, Berkeley, and its contributors; by the Free Software +Foundation; by the University of Illinois; by the Massachusetts +Institute of Technology; by the University of Vermont and State +Agricultural College; by Carnegie Mellon University; and by a large +number of contributors, whose names are listed in the notices below. + +Portions of this software are subject to one or more of the following +copyright notices. Please see the individual files for the terms and +conditions. + + +Copyright (C) 1980, 1983, 1986, 1988, 1990, 1991, Regents of the + University of California +Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, Free + Software Foundation, Inc. +Copyright (C) 1976, Board of Trustees of the University of Illinois +Copyright (C) 1980, 1981, Ken Harrenstien +Copyright (C) 1982, 1988, 1989, Walter Tichy +Copyright (C) 1983, 1986, 1992, 1993, Eric P. Allman +Copyright (C) 1983, Kenneth L. Greer +Copyright (C) 1984, 1985, 1986, 1987, 1992, Sun Microsystems, Inc. +Copyright (C) 1984, 1987, Stephen L. Moshier +Copyright (C) 1984, 1989, 1990, Bob Corbett and Richard Stallman +Copyright (C) 1984, University of British Columbia +Copyright (C) 1985, 1986, Wayne A. Christopher +Copyright (C) 1985, 1987, 1988, 1989, Adobe Systems, Inc. +Copyright (C) 1985, Stichting Mathematisch Centrum +Copyright (C) 1986, 1987, 1989, 1990, 1991, 1992, Ian F. Darwin +Copyright (C) 1986, 1987, 1989, Frame Technology, Inc. +Copyright (C) 1986, 1987, 1992, Daniel D. Lanciani +Copyright (C) 1986, 1987, Ed James +Copyright (C) 1986, Breslow +Copyright (C) 1986, Gary S. Brown +Copyright (C) 1986, Larry Wall +Copyright (C) 1986, Noah Morgan +Copyright (C) 1986, Stephen Satchell +Copyright (C) 1987, 1988, 1989, 1990, 1991, 1992, Carnegie Mellon University +Copyright (C) 1987, 1988, 1989, Sony Corp. +Copyright (C) 1987, 1988, John Stanback +Copyright (C) 1987, 1988, Ronald S. Karr and Landon Curt Noll +Copyright (C) 1987, 1989, 1990, 1991, Massachusetts Institute of Technology +Copyright (C) 1987, David C. Elliott. +Copyright (C) 1987, IBM Corporation +Copyright (C) 1987, Stuart Cracraft +Copyright (C) 1987, United States Army +Copyright (C) 1988, 1989, 1990, 1993, 1994, Paul A. Vixie +Copyright (C) 1988, 1989, Adam de Boor +Copyright (C) 1988, 1990, University of Utah +Copyright (C) 1988, Julian Onions +Copyright (C) 1988, Mark Nudleman +Copyright (C) 1988, Rayan S. Zachariassen +Copyright (C) 1989, 1990, 1991, 1992, 1993, Frank Kardel +Copyright (C) 1989, 1990, 1991, 1992, 1993, William S. Jolitz +Copyright (C) 1989, 1990, 1991, 1992, Brian Berliner +Copyright (C) 1989, Berkeley Softworks +Copyright (C) 1989, Dale Schumacher +Copyright (C) 1989, Dave Taylor +Copyright (C) 1989, Kenneth Almquist +Copyright (C) 1989, Matthew Self +Copyright (C) 1989, Robert V. Baron +Copyright (C) 1990, 1991, 1992, 1993, AT&T Bell Laboratories and Bellcore +Copyright (C) 1990, 1991, John W. Eaton +Copyright (C) 1990, 1991, Paul Eggert +Copyright (C) 1990, 1993, Andrew Moore +Copyright (C) 1990, John Robert LoVerso +Copyright (C) 1990, Open Software Foundation, Inc. +Copyright (C) 1990, RSA Data Security, Inc. +Copyright (C) 1991, 1992, 1993, 1994, Chris Provenzano +Copyright (C) 1991, 1992, 1993, Ian Lance Taylor +Copyright (C) 1991, 1992, Per Bothner +Copyright (C) 1991, 1992, Per Cederqvist +Copyright (C) 1991, Gregory M. Christy +Copyright (C) 1991, Inge Wallin +Copyright (C) 1991, Joseph Friedman +Copyright (C) 1992, 1993, 1994, David L. Mills +Copyright (C) 1992, 1993, Christopher G. Demetriou +Copyright (C) 1992, 1993, Garrett A. Wollman +Copyright (C) 1992, 1993, HD Associates +Copyright (C) 1992, 1993, Holger Veit +Copyright (C) 1992, 1993, Jean-Loup Gailly +Copyright (C) 1992, 1993, 1994 Joerg Wunsch +Copyright (C) 1992, 1993, John Brezak +Copyright (C) 1992, 1993, Motorola, Inc. +Copyright (C) 1993, 1994, Jordan Hubbard +Copyright (C) 1992, 1993, Soeren Schmidt +Copyright (C) 1992, 1993, Theo de Raadt +Copyright (C) 1992, 1993, University of Vermont and State Agricultural College +Copyright (C) 1992, Cygnus Support +Copyright (C) 1992, Diomidis Spinellis +Copyright (C) 1992, Henry Spencer +Copyright (C) 1992, Jeff Polk +Copyright (C) 1992, Terrence R. Lambert +Copyright (C) 1992, University of Guelph +Copyright (C) 1993, 1994, Andrew A. Chernov +Copyright (C) 1993, 1994, David Greenman +Copyright (C) 1993, 1994, John S. Dyson +Copyright (C) 1993, Adam Glass +Copyright (C) 1993, Atsushi Murai +Copyright (C) 1993, Brian Moore +Copyright (C) 1993, Daniel Boulet and RTMX Inc. +Copyright (C) 1993, David Muir Sharnoff +Copyright (C) 1993, David Parsons +Copyright (C) 1993, Gary Clark II +Copyright (C) 1993, Hannu Savolainen +Copyright (C) 1993, Herb Peyerl +Copyright (C) 1993, Herve Schauer Consultants +Copyright (C) 1993, Julian Elischer +Copyright (C) 1993, Julian Stacey +Copyright (C) 1993, K. J. Dryllerakis +Copyright (C) 1993, Martin Birgmeier +Copyright (C) 1993, Paul Kranenburg +Copyright (C) 1993, Paul Richards +Copyright (C) 1993, Thomas Koenig +Copyright (C) 1993, Winning Strategies, Inc. +Copyright (C) 1994, Christoph M. Robitschko +Copyright (C) 1994, University of Maryland +Copyright (C) 1993, 1994, jc@irbs.UUCP (John Capo), + vak@zebub.msk.su (Serge Vakulenko), + ache@astral.msk.su (Andrew A. Chernov) + +$Id: COPYRIGHT.FreeBSD,v 1.1.1.1 1996-09-24 17:45:48 jfieber Exp $ diff --git a/data/releases/1.1.5/COPYRIGHT.USL b/data/releases/1.1.5/COPYRIGHT.USL new file mode 100644 index 0000000000..5f3f151c5c --- /dev/null +++ b/data/releases/1.1.5/COPYRIGHT.USL @@ -0,0 +1,45 @@ +Copyright (c) UNIX System Laboratories, Inc. +All or some portions of this software are derived from +material licensed to the University of California by +American Telephone and Telegraph Co. or UNIX System Laboratories, Inc. +and are reproduced herein with the permission of +UNIX System Laboratories, Inc. + +Additionally, the following files contained herein constitute +trade secrets of UNIX System Laboratories, Inc. and their contents +are not to be disclosed to any third party: + +sys/kern/init_main.c +sys/kern/kern_clock.c +sys/kern/kern_exec.c [*] +sys/kern/kern_exit.c +sys/kern/kern_physio.c [**] +sys/kern/kern_sig.c +sys/kern/kern_synch.c +sys/kern/subr_rmap.c [*] +sys/kern/sys_generic.c +sys/kern/sys_process.c +sys/kern/sysv_shm.c +sys/kern/tty.c +sys/kern/tty_subr.c [*] +sys/kern/vfs_bio.c [*] +sys/kern/vfs_syscalls.c +sys/sys/buf.h +sys/sys/proc.h +sys/sys/shm.h +sys/sys/tty.h +sys/ufs/dinode.h +sys/ufs/inode.h +sys/ufs/ufs_bmap.c +sys/ufs/ufs_disksubr.c +sys/ufs/ufs_inode.c +sys/ufs/ufs_vnops.c +usr.bin/cpio/cpio.c [*] + +[*] These file are NOT contained in FreeBSD + +[**] The version of this file in FreeBSD is belived to be clear of any USL + copyright and/or trade secret. + + +$Id: COPYRIGHT.USL,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/data/releases/1.1.5/KNOWNBUGS b/data/releases/1.1.5/KNOWNBUGS new file mode 100644 index 0000000000..42b730b985 --- /dev/null +++ b/data/releases/1.1.5/KNOWNBUGS @@ -0,0 +1,73 @@ +This file lists known problems with this release of FreeBSD + +'hanging keyboard' +------------------ +There are still problems with certain machines appearing to 'hang' on +bootup even though a prompt is there. The most common machines that +exhibit these problems are Gateway 2000 machines with PHOENIX bios's but +other machines with PHOENIX bios also exhibit this behavior. + The temporary solution until you can get the distribution +installed on your hard-drive is to 'bounce' on a key like shift or +num-lock (which works well since you can see when the keyboard comes +back to life) until the boot sequence is finished. The keyboard will +work fine for installing FreeBSD onto the hard-drive. + +/usr/bin/gdb: + The gdb in the release will not work on shared objects nor will it + work with C++ executables. Please use the gdb in the ports area for + debugging shared and/or C++ code. This is just a work-around until + we can transition to the new version of gdb completely. See below. + +/usr/gnu/bin/gdb: + This is the gdb from the ports area (if installed), also known as + gdb-4.11. There is a problem using gdb-4.11 to debug a core-file + generated by a binary which uses shared libraries. The problem is + basically due to the fact that the shared libraries are mmap'ed at + addresses in the memory space of the binary which are not accessible + to gdb-4.11 at the time that it tries to examine the core-file. This + usually manifests itself in "Cannot access memory at address " + messages at startup and "#0 in end ()" when you try to do + a backtrace ("bt"). + + Workaround: start gdb-4.11 without reference to the core-file, + e.g. "gdb fubar". Set a breakpoint in main and run the inferior + so that gdb-4.11 can resolve references to the shared libraries. + After this, use the "core-file" command to force gdb-4.11 to + load the core-file, e.g. "core-file fubar.core". Since all + shared library references were previously resolved gdb-4.11 can + now access the shared libraries and things like "bt" now work. + You will also be able to reference items previously on the stack + (from the core file), but all globals will show up as zero'd. + All these problems may be avoided if you compile the application + with -static. + +/sys/i386/isa/if_ep.c + The 3c509 driver will hang under heavy network loads and take your + machine off the network. (Though the machine will continue to run with + no network facilities) + + Workaround: Try a "ifconfig ep0 down" and a "ifconfig ep0 up" + to get it running again. + +/sys/i386/isa/bt742a.c + The Bt445S and Bt747 controllers can cause problems when ISA DMA + is selected as an option. With the EISA controller the remedy is + easy - simply turn it off using your EISA configuration utility. + With the Bt445S, which is a VLB card, you must switch the undocumented + "SW10" on "SB2" to the off position. Also note that certain revisions + of the Buslogic board (Revision C or earlier, firmware revision <3.37) + will cause DATA CORRUPTION with systems containing more than 16MB of + memory. If you find this to be the case, temporarily remove your + extra memory and contact Buslogic for an upgrade! + +fsck: + fsck can go into an endless loop in the repair/fsck cycle on + a corrupted filesystem. The message "VALUES IN SUPER BLOCK + DISAGREE WITH THOSE IN FIRST ALTERNATE" is very misleading. + fsck compares the superblock with the alternate in the last + cylinder group? So if this block is corrupt, you have no chance + to get the filesystem repaired. You can answer on the question + "UPDATE STANDARD SUPERBLOCK" with yes and get always the same + error message on the next fsck. + +$Id: KNOWNBUGS,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/data/releases/1.1.5/MIRROR.SITES b/data/releases/1.1.5/MIRROR.SITES new file mode 100644 index 0000000000..a3e9669787 --- /dev/null +++ b/data/releases/1.1.5/MIRROR.SITES @@ -0,0 +1,59 @@ + +The FreeBSD software is being mirrored at the following locations: + +Country Site/Directory/Maintainer +======= ========================================================= + +Australia minnie.cs.adfa.oz.au:/BSD/FreeBSD-1.1-RELEASE + + +Australia ftp.physics.su.oz.au:/FreeBSD + David Dawes + +Australia ftp.une.edu.au:/pub/FreeBSD + Gordon Smith + +Austria ftp.tu-graz.ac.at:/pub/FreeBSD + + +Finland ftp.funet.fi:/pub/unix/FreeBSD + + +France ftp.ibp.fr:/pub/FreeBSD + + +Germany ftp.informatik.tu-muenchen.de:/pub/comp/os/bsd/FreeBSD + + +Germany ftp.uni-duisburg.de:/pub/unix/FreeBSD + + +Germany gil.physik.rwth-aachen.de:/pub/FreeBSD + + +Hong Kong ftp.cs.cuhk.hk:/pub/FreeBSD + + +Israel orgchem.weizmann.ac.il:/pub/FreeBSD + + +Netherlands ftp.nl.net:/pub/os/FreeBSD + + +Russia ftp.kiae.su:/FreeBSD + + +UK src.doc.ic.ac.uk:/packages/FreeBSD + + +USA gatekeeper.dec.com:/pub/BSD/FreeBSD + + +USA freebsd.uml.edu:/FreeBSD + + +USA wuarchive.wustl.edu:/systems/unix/FreeBSD + + + +$Id: MIRROR.SITES,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/data/releases/1.1.5/Makefile b/data/releases/1.1.5/Makefile new file mode 100644 index 0000000000..1340175acd --- /dev/null +++ b/data/releases/1.1.5/Makefile @@ -0,0 +1,6 @@ +DATA= CONTRIB.386BSD CONTRIB.FreeBSD COPYRIGHT.386BSD +DATA+= COPYRIGHT.FreeBSD COPYRIGHT.USL KNOWNBUGS MIRROR.SITES +DATA+= PERSONAL.ACKS REGISTER.FreeBSD RELNOTES.FreeBSD ROSTER.FreeBSD +DATA+= SUPPORT.TXT TODO-1.1.5 + +.include "../../web.mk" diff --git a/data/releases/1.1.5/PERSONAL.ACKS b/data/releases/1.1.5/PERSONAL.ACKS new file mode 100644 index 0000000000..d80896428b --- /dev/null +++ b/data/releases/1.1.5/PERSONAL.ACKS @@ -0,0 +1,17 @@ +The following contributors would like to make these personal +acknowledgements (in no particular order): + +Garrett Wollman would like to thank Gary Barbour and Steve Ackerman of +Utah; Tim Raymond, Jim White, and Jim Ertle of UVM; Malcolm Carlock at +UNR; and John Wroclawski of MIT. + +Nate Williams would like to thank Jaye Mathisen and the entire Computer +Science department of Montana State University for their help, hardware +and encouragement. + +Jordan Hubbard would like to thank IEUNET for bringing the INTERNET to +Ireland, thus making his participation possible at all (albeit expensive) +and his Mom, who would probably be pleased if only she understood any of +this. Hi Mom. + +$Id: PERSONAL.ACKS,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/data/releases/1.1.5/REGISTER.FreeBSD b/data/releases/1.1.5/REGISTER.FreeBSD new file mode 100644 index 0000000000..a7814005ff --- /dev/null +++ b/data/releases/1.1.5/REGISTER.FreeBSD @@ -0,0 +1,86 @@ +In the absence of any other mechanism for counting the number of users +of FreeBSD, we like to as kindly suggest that you take a few minutes +to please register with the counter set up by +. + +The justification for such "registration" is twofold: First, we sincerely do +wish to know just what the size and demographics of our user-base are +in order to better support its needs. Second, it's a sad fact that many +people rely on counters and statistics (even when highly dubious) rather +than actual experience when chosing an operating system, and the best we +can hope to do in such circumstances is to at least try to provide some +indication of how popular we are (or are not). This is not how we recommend +that people go about chosing an operating system, but the necessity of +"marketing" remains an undeniable fact of life. + +The FreeBSD team does not necessarily feel that Harald's counter represents +the best approach to such statistics gathering, and its accuracy will only +be as good as people's willingness to register with it (which may not reflect +the actual OS population at any single point in time), but in the total absence +of any other mechanism for providing such useful statistics, it's certainly a +start and we thank Harald for his efforts in providing this service. +It's a community service, and of potential benefit to everyone (all *BSD +users), so let's see if we can't make it work! + +Included below is the standard blurb from the counter. + +Thanks in advance, + + The FreeBSD team. + + +How to get registered +===================== + +In brief: + + [To register a running installation of FreeBSD] + Send E-mail to bsd-counter@uninett.no with the SUBJECT line + + "I use FreeBSD at " + +Introduction +============ +The intention of this counting project is to count all users of UNIXes +that are: + + - BSD-derived + - Freely available + +The variants NetBSD, 386BSD and FreeBSD are currently distinguished. + +(NOTE: Linux is NOT BSD-derived. If you use that, send mail to +linux-counter@uninett.no instead!!!) + +The information is *not* used for any purpose but statistics, and unless +you request it, information about single persons are *never* made public. +(A list of users who have requested publication is available from the +FTP file ftp://aun.uninett.no/pub/misc/386bsd/persons) + +How to register +=============== +Send E-mail to bsd-counter@uninett.no + +The subject should be + + I use FreeBSD|NetBSD|386BSD at + +Where FreeBSD, NetBSD or 386BSD is the particular variant you're using +and "place" can be school, work or home, or a combination of these. + +You will get back a letter with 3 things: + + - An acknowledgement + - A form that you can fill out and send in with more information + about yourself, your machine, and your 386bsd-using friends + - A report giving the current status of the counter + +You can update your "vote" at any time, by sending an E-mail message +from the same account. Duplicates will be weeded out. + +The current report, available by anonymous FTP to aun.uninett.no, +directory pub/misc/386bsd-counter, file "short", is given below. + +For all questions, contact Harald.T.Alvestrand@uninett.no! + +$Id: REGISTER.FreeBSD,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/data/releases/1.1.5/RELNOTES.FreeBSD b/data/releases/1.1.5/RELNOTES.FreeBSD new file mode 100644 index 0000000000..3707fc26a9 --- /dev/null +++ b/data/releases/1.1.5/RELNOTES.FreeBSD @@ -0,0 +1,313 @@ + RELEASE NOTES + FreeBSD + Release 1.1.5 + +1. Technical overview +--------------------- + +FreeBSD is a freely available, full source 4.3 (+4.4 enhancements) BSD +release for Intel i386/i486 (or compatable) based PC's. It is based +on Bill Jolitz's 386BSD 0.1, with additions from "the patchkit", +NetBSD, CSRG, and the Free Software Foundation. + +Since our first release of FreeBSD 1.0, many hundreds of bugs have been +fixed, features added, and the overall quality of the system improved +almost imeasurably. FreeBSD 1.1.5 represents the culmination of almost +18 months of work and many thousands of man hours put in by our all-volunteer +working group. We hope you enjoy it! + +Many packages have also been upgraded or added, such as XFree86 2.1, +xview 3.2, elm, nntp, mh, InterViews and dozens of other miscellaneous +utilities have been ported and are now available as add-ons. See the next +section of this document for more details. + +For a list of contributors, please see the files "CONTRIB.FreeBSD" and +"CONTRIB.386BSD", which should be bundled with your distribution. + +Also see the new "REGISTER.FreeBSD" file for information on registering +with the "Free BSD user counter". We've also provided a list of who's +responsible for what (so that you may query them directly) in the +"ROSTER.FreeBSD" file; use of this file is encouraged to ensure faster +resolution of an problems you may have! + +The core of FreeBSD does not contain DES code which would inhibit its +being exported outside the United States. There is an add-on package +to the core distribution, for use only in the United States, that +contains the programs that normally use DES. The auxilliary packages +provided separately can be used by anyone. A freely (from outside the U.S.) +exportable European distribution of DES for our non U.S. users also exists +and is described in the FreeBSD FAQ. + + +2. Supported Configurations +--------------------------- + +FreeBSD currently runs on a wide variety of ISA, EISA and PCI bus based +PC's, ranging from 386sx to Pentium class machines (though the 386sx is +not recommended). Support for generic IDE or ESDI drive configurations, +various SCSI controller, network and serial cards is also provided. + +Following is a list of all currently known disk controllers and +ethernet cards known to work with FreeBSD. Other configurations may +very well work, and we have simply not received any indication of +this. + + +2.1. Disk Controllers + +WD1003 (any generic MFM/RLL) +WD1007 (any generic IDE/ESDI) + +Adaptec 154x series ISA SCSI controller (as long as you have less than +16MB of main memory). + +Adaptec 174x series EISA SCSI controller in standard and enhanced mode. + +[Note that Buslogic was formerly known as "Bustec"] +Buslogic 545S. +Buslogic 445S VLB SCSI controller +Buslogic 742A and 747. +Buslogic 942A PCI + +Please see special notes in /usr/src/KNOWNBUGS (filed under bt742a.c) for +details concerning possible buggy firmware and undocumented switch settings +that may be necessary for proper operation of your Bt445S controller. + +DTC 3290 EISA SCSI controller in 1542 emulation mode. + +Ultra Store 14F and 34F. + +Seagate ST01/02 SCSI controllers. + +Future Domain 8xx/950 series SCSI controllers. + +With all supported SCSI controllers, full support is provided for +SCSI-I & SCSI-II peripherals, including Disks, tape drives (including +DAT) and CD ROM drives. Note: This and the mcd driver (Mitsumi CDROM +interface card) is the only way a CD ROM drive may be currently +attached to a FreeBSD system; we do not support SoundBlaster CDROM +interface, or other "mini SCSI" adapters. + +Some controllers have limitations with the way they deal with >16MB of memory, +due to the fact that the ISA bus only has a DMA address space of 24 bits. +If you do your arithmetic, you'll see that this makes it impossible to do +direct DMA to any address >16MB. This limitation is even true of some +EISA controllers (which are normally 32 bit) when they're configured to +emulate an ISA card, which they then do in *all* respects. This problem +is avoided entirely by IDE controllers (which do not use DMA), true EISA +controllers (like the UltraStor or Adaptec 1742A) and most VLB (local bus) +controllers. In the cases where it's necessary, the system will use +"bounce buffers" to to talk to the controller so that you can still use +more than 16Mb of memory without difficulty. + + +2.2. Ethernet cards + +SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, +WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT +based clones. + +Isolan AT 4141-0 (16 bit) + +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, and NE2100 ethernet interface. + +3Com 3C503 Etherlink II + +3Com 3C509 Ethernet cards + +Toshiba ethernet cards + +SMC Elite Ultra + + +2.3. Misc + +AST 4 port serial card using shared IRQ. + +ARNET 8 port serial card using shared IRQ. + +BOCA ATIO66 6 port serial card using shared IRQ. + +STB 4 port card using shared IRQ. + +Mitsumi (all models) CDROM interface and drive. + +Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound +and Roland MPU-401 sound cards. + +FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but +support is apparently close to materializing. Details will be posted +as the situation develops. + + +3. Obtaining FreeBSD. +--------------------- + +You may obtain FreeBSD in a variety of ways: + +1. FTP/Mail + +You can ftp FreeBSD and any or all of its optional packages from +`freebsd.cdrom.com' - the offical FreeBSD release site. + +For other locations that mirror the FreeBSD software see the file +MIRROR.SITES. Please ftp the distribution from the nearest site +to you netwise. + +If you do not have access to the internet and electronic mail is your +only recourse, then you may still fetch the files by sending mail to +`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message +to get more information on how to fetch files from freebsd.cdrom.com. +Note: This approach will end up sending many *tens of megabytes* +through the mail, and should only be employed as an absolute LAST +resort! + + +2. CDROM + +FreeBSD 1.1 may be ordered on CDROM from: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) + +Or via the internet from orders@cdrom.com. There current catalog can +be obtained via ftp as ftp.cdrom.com:/cdrom/catalog. + +Cost is $39.95. Shipping (per order not per disc) is $5 in the US, Canada, +or Mexico and $10.00 overseas. They accept Visa, Mastercard, American +Express, and ship COD to the United States. California residents please +add 8.25% sales tax. + +Should you be dissatisfied for any reason, the CD comes with an +unconditional return policy. + +Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD, +you need to contact the FreeBSD team for that. Please see section 4 for +more information. + + +It should be noted, lest you get the wrong impression that "FreeBSD" +is anything but, that almost no one in the "core team" makes money +from distributions or anything else connected with FreeBSD. We simply +provide this information as a public service for those wishing to get +their releases from somewhere other than the net (and the easier it +is for you to obtain our software, the happier we are). + + +4. Reporting problems, making suggestions, submitting code. +----------------------------------------------------------- + +Your suggestions, bug reports and contributions of code are always +valued - please do not hesitate to report any problems you may find +(preferably with a fix attached if you can!). + +The prefered method to submit bug reports from a machine with internet +mail connectivity is to use the sendbug command. Bug reports will be +dutifully filed by our faithful bugfiler program and you can be sure +that we'll do our best to respond to all reported bugs as soon as +possible. + +If, for some reason, you are unable to use the sendbug command to +submit a bug report, you can try to send it to: + + FreeBSD-bugs@freefall.cdrom.com + + +Otherwise, for any questions or suggestions, please send mail to: + + FreeBSD-questions@freefall.cdrom.com + +Additionally, being a volunteer effort, we are always happy to have +extra hands willing to help - there are already far more enhancements +to be done than we can ever manage to do by ourselves! To contact us +on technical matters, or with offers of help, you may send mail to: + + FreeBSD-hackers@freefall.cdrom.com + +Since these mailing lists can experience significant amounts of +traffic, if you've got slow or expensive mail access and you're +only interested in keeping up with significant FreeBSD events, you may +find it preferable to subscribe to: + + FreeBSD-announce@freefall.cdrom.com + + +All but the FreeBSD-bugs groups can be freely joined by anyone wishing to +do so. Send mail to MajorDomo@freefall.cdrom.com and include the keyword +`help' on a line by itself somewhere in the body of the message. This +will give you more information on joining the various lists, accessing +archives, etc. + + +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. It would be very difficult, if not +impossible, to enumerate everyone who's contributed to FreeBSD, but +nonetheless we shall try (in alphabetical order, of course). If your +name is not mentioned, please be assured that its omission is entirely +accidental. + + +The Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, for his extensive work with 386BSD. + +The FreeBSD "core" team: + + Andrew A. Chernov + John Dyson + David Greenman + Rodney W. Grimes + Jordan K. Hubbard + Scott Mace + Andrew Moore + Rich Murphey + Geoff Rehmet + Paul Richards + Andreas Schulz + Nate Williams + Garrett A. Wollman + + +Special mention to: + + Robert Bruce and Jack Velte of Walnut Creek CDROM, without + whose help (and continuing support) this release would never + have been possible. + + Dermot McDonnell for his donation of a Toshiba XM3401B CDROM + drive. + + The NetBSD group for their frequent assistance and commentary. + + Additional FreeBSD helpers and beta testers: + + Gary Browing Jon Cargille + J.T. Conklin Chris Demetriou + Julian Elischer Bruce Evans + Sean Eric Fagan Guy Helmer + Jeffrey Hsu Terry Lambert + Gary Moyer Jaye Mathisen + Curt Mayer L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Rick Weldon Terry Williams + Atsushi Murai + + And everyone at Montana State University for their initial support. + + +Thanks to everyone, especially those not mentioned, and we sincerely +hope you enjoy this release of FreeBSD! + + + The FreeBSD Core Team + +$Id: RELNOTES.FreeBSD,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/data/releases/1.1.5/ROSTER.FreeBSD b/data/releases/1.1.5/ROSTER.FreeBSD new file mode 100644 index 0000000000..9972cf4fee --- /dev/null +++ b/data/releases/1.1.5/ROSTER.FreeBSD @@ -0,0 +1,127 @@ +This file attempts to document just who is `responsible' for what in +the FreeBSD world. Since we're an all-volunteer group, the whole +concept of `responsibility' must, of course, be taken with a grain of +salt since the folks here may not always have time to deal with your +problem right away. With that in mind, you are encouraged to contact +these folks directly when your problem or suggestion clearly falls +into their area of responsibility. If your queries don't net any +positive results in, say, 48 hours, THEN you should try and contact +the group at large. In most cases, however, using these folks as +first-contacts will both cut down on our mail-overload and give you +faster service. + +Thank you! + + The FreeBSD Team + freebsd-hackers@freefall.cdrom.com + +--- + + +Legend: +------- +contrib = Contributed +doc = Documentation +lib = User-land library +misc = Misc user-land utility (contrib, other) +ports = Ported software in /usr/ports +prog = User-land program +share = Support data files +sys = Kernel and system code +tools = DOS support utilities + +Category Person Email address +=============================================================================== +contrib/xntpd Garrett Wollman wollman@lcs.mit.edu +doc/FAQ FAQ Team freebsd-faq@freefall.cdrom.com +lib/libF77 L. Jonas Olsson ljo@po.cwru.edu +lib/libc Garrett Wollman wollman@lcs.mit.edu +lib/libcrypt (non-US) Geoff Rehmet csgr@cs.ru.ac.za +lib/libcurses Andrew Chernov ache@astral.msk.su +lib/libkrb Garrett Wollman wollman@lcs.mit.edu +lib/libm Andrew Moore alm@netcom.com +lib/libpthread Chris Provenzano proven@mit.edu +lib/libskey Guido van Rooij guido@gvr.win.tue.nl +lib/libtelnet Garrett Wollman wollman@lcs.mit.edu +misc/addit Gary Clark II gclarkii@freefall.cdrom.com +misc/configit Gary Clark II gclarkii@freefall.cdrom.com +misc/gnats Andrew Moore alm@netcom.com +misc/manctl Geoff Rehmet csgr@cs.ru.ac.za +ports/{not below} Andrew Moore alm@freefall.cdrom.com +ports/aXe Jordan Hubbard jkh@freefall.cdrom.com +ports/archivers Scott Mace smace@freefall.cdrom.com +ports/bash Jordan Hubbard jkh@freefall.cdrom.com +ports/blt Jordan Hubbard jkh@freefall.cdrom.com +ports/cpm Joerg Wunsch joerg_wunsch@uriah.sax.de +ports/dgd Adam David adam@veda.is +ports/elm Scott Mace smace@freefall.cdrom.com +ports/emacs Jordan Hubbard jkh@freefall.cdrom.com +ports/exmh Jordan Hubbard jkh@freefall.cdrom.com +ports/ezd Jeffrey Hsu hsu@freefall.cdrom.com +ports/franz Jordan Hubbard jkh@freefall.cdrom.com +ports/fvwm Geoff Rehmet csgr@cs.ru.ac.za +ports/golddig Jeffrey Hsu hsu@freefall.cdrom.com +ports/ile Jordan Hubbard jkh@freefall.cdrom.com +ports/ispell Piero Serini piero@strider.st.dsi.unimi.it +ports/jpeg Scott Mace smace@freefall.cdrom.com +ports/kermit Scott Mace smace@freefall.cdrom.com +ports/ksh Sean Vickery seanv@cs.uq.edu.au +ports/kterm Satoshi Asami asami@cs.berkeley.edu +ports/lynx Serge V.Vakulenko vak@cronyx.msk.su +ports/mprof Jeffrey Hsu hsu@freefall.cdrom.com +ports/mtools Steven Wallace swallace@freefall.cdrom.com +ports/netaudio Jeffrey Hsu hsu@freefall.cdrom.com +ports/nethack Sean Vickery seanv@cs.uq.edu.au +ports/pcvt J"org Wunsch joerg_wunsch@uriah.sax.de +ports/piewm Satoshi Asami asami@cs.berkeley.edu +ports/pkg_install Jordan Hubbard jkh@freefall.cdrom.com +ports/popper Andreas Schulz ats@g386bsd.first.gmd.de +ports/point Jordan Hubbard jkh@freefall.cdrom.com +ports/sather Jeffrey Hsu hsu@freefall.cdrom.com +ports/schemetoc Jeffrey Hsu hsu@freefall.cdrom.com +ports/scm Jeffrey Hsu hsu@freefall.cdrom.com +ports/seahaven Jeffrey Hsu hsu@freefall.cdrom.com +ports/sml Jeffrey Hsu hsu@freefall.cdrom.com +ports/sup Jordan Hubbard jkh@freefall.cdrom.com +ports/tcl Jordan Hubbard jkh@freefall.cdrom.com +ports/tcl-dp Jordan Hubbard jkh@freefall.cdrom.com +ports/tclX Jordan Hubbard jkh@freefall.cdrom.com +ports/tcsh Scott Mace smace@freefall.cdrom.com +ports/tk Jordan Hubbard jkh@freefall.cdrom.com +ports/vile Jordan Hubbard jkh@freefall.cdrom.com +ports/vim Jordan Hubbard jkh@freefall.cdrom.com +ports/wine Jeffrey Hsu hsu@freefall.cdrom.com +ports/wu-ftpd Justin T. Gibbs gibbs@freefall.cdrom.com +ports/xcdplayer Steven Wallace swallace@freefall.cdrom.com +ports/xjewel Jeffrey Hsu hsu@freefall.cdrom.com +ports/xlock Scott Mace smace@freefall.cdrom.com +ports/xmine J"org Wunsch joerg_wunsch@uriah.sax.de +ports/xphoon Satoshi Asami asami@cs.berkeley.edu +ports/xv Scott Mace smace@freefall.cdrom.com +ports/ytalk Geoff Rehmet csgr@cs.ru.ac.za +ports/zircon Jordan Hubbard jkh@freefall.cdrom.com +ports/zsh Scott Mace smace@freefall.cdrom.com +prog/cc Poul-Henning Kamp phk@freefall.cdrom.com +prog/cc25 Poul-Henning Kamp phk@freefall.cdrom.com +prog/gdb Gary Jennejohn gj@pcs.dec.com +prog/man Jordan Hubbard jkh@freefall.cdrom.com +prog/telnet Garrett Wollman wollman@lcs.mit.edu +sys/fd J"org Wunsch joerg_wunsch@uriah.sax.de +sys/fd Serge V.Vakulenko vak@cronyx.msk.su +sys/i386 David Greenman davidg@root.com +sys/i386/isa/seagate Sean Vickery seanv@cs.uq.edu.au +sys/i386/isa/sound Steven Wallace swallace@freefall.cdrom.com +sys/i386/isa/bt742*.c Atsushi Murai amurai@spec.co.jp +sys/kern David Greenman davidg@root.com +sys/kern/ntp Garrett Wollman wollman@lcs.mit.edu +sys/lpt Geoff Rehmet csgr@cs.ru.ac.za +sys/net* David Greenman davidg@root.com +sys/netboot Martin Renters martin@innovus.com +sys/netinet Garrett Wollman wollman@lcs.mit.edu +sys/pcmcia Poul-Henning Kamp phk@freefall.cdrom.com +sys/scheduler John Dyson dyson@freefall.cdrom.com +sys/syscons So/ren Schmidt sos@freefall.cdrom.com +sys/vm David Greenman davidg@root.com +sys/vm John Dyson dyson@freefall.cdrom.com +sys/wt Serge V.Vakulenko vak@cronyx.msk.su +tools/booteasy Serge V.Vakulenko vak@cronyx.msk.su diff --git a/data/releases/1.1.5/SUPPORT.TXT b/data/releases/1.1.5/SUPPORT.TXT new file mode 100644 index 0000000000..8bf8a92c82 --- /dev/null +++ b/data/releases/1.1.5/SUPPORT.TXT @@ -0,0 +1,89 @@ + +Technical support for this product is NOT provided by Walnut Creek CDROM. + +You need to contact one of the following companies and/or people for +technical support. + +Accurate Automation Company +6005 S.E. Laurel Street +Milwaukie, OR 97222 +Telephone: +1-503-653-7376 +Email: rgrimes@agora.rain.com + +Accurate Automation provides support for FreeBSD including installation, +system configuration, hardware and software trouble shooting, and related +issues. Rates depend upon the type of work being done. Hours are from +10:00 am to 10:00pm PST. + + +Gary Clark II +GB Data Consulting +3801 Polk +Houston, Texas 77003 USA +Telephone: +1-713-587-1644 +Email: gclarkii@radon.gbdata.com + +GB Data Consulting provides support for FreeBSD including installation, usage +and system administration. We also provide classes, on-site service and +distribution sets on floppy. Please email info@radon.gbdata.com or call for +rates and information. + + +Cronyx Ltd. +Research Computer Center, +Moscow State University, +Moscow 199899, Russia +Phone: +7-095-939-5678 +Email: info@cronyx.msk.su + +Cronyx Ltd. provides support for FreeBSD including installation, +configuration, Relcom network connection via UUCP, dialup and leased +line IP. We also provide X Windows configuration and localization, +as well as additional packages installation. Distribution sets on +floppies and tape cartridges available. System software development +including drivers for non-standard equipment. + + +Jordan Hubbard +Timberline Associates (est 1978) +Dublin, Ireland [And soon Boston / San Francisco] +Support hours: 1000 - 2300 GMT +Tel #: 00353-1-332796 +Email: jkh@al.org + +Telephone (or Internet) and on-site consulting for FreeBSD in Ireland, +the United States, United Kingdom and most parts of Europe. Services include +installation, system configuration, networking and custom software +projects, graphical user interfaces a specialty (actively involved with +The X Window System since Version 9 and contributor to the X Consortium). +Reasonable and flexible rates comensurate with location and duration of +assignment. Internet assignments are welcomed, and generally billed at +lower rates. + + +Vector Systems Ltd, Julian H. Stacey. +Post: Holz Strasse 27d, D 80469, Munich (Muenchen), Germany (Deutschland). +Tel.: +49 89 268616 09:00-22:00 TZ=GMT+1 +Email: stacey@freefall.cdrom.com + +Custom designs & support using FreeBSD + X-Windows + FSF/GNU, + own Unix & DOS +C tools. Systems engineering, hardware interfacing, multi lingual systems +(European, Cyrillic, Chinese), communications, scientific, industrial real +time programming. Source Tapes: QIC 525M, 150M, 60M. +Deutsch: Man kann mir in Deutsch schreiben, (oder mich anrufen). +Francais: Je comprend Francais, mais je n'ecris pas des responses en Francais. + + +Sean Vickery +2/449 Milton Road +Auchenflower Qld 4066 +Australia +Telephone: +61 (0)7 870 5241 + Email: seanv@cs.uq.edu.au + +Sean offers support in most FreeBSD matters, including installation +and configuration. His rates are reasonable. As well as on-site +help, support is available over the phone and the net. + + +$Id: SUPPORT.TXT,v 1.1.1.1 1996-09-24 17:45:50 jfieber Exp $ diff --git a/data/releases/1.1.5/TODO-1.1.5 b/data/releases/1.1.5/TODO-1.1.5 new file mode 100644 index 0000000000..66d1777a13 --- /dev/null +++ b/data/releases/1.1.5/TODO-1.1.5 @@ -0,0 +1,38 @@ +This is my current TODO list for 1.1.5. Please feel free to add to +it, assuming that you've actually got some confidence that you or +someone else will be able to actually get to whatever it is (or it's +so critical that you don't think 1.1.5 could/should be released +without it). + +Also, please bear in mind the following milestones we have to hit: + +June 5th Feature Freeze (bug fixes and cleanup work only). +June 16th Code Freeze +June 20th Roll binaries - begin initial testing +June 23rd Announce availability of 1.1.5. + +(*) = Task is completed +(@) = Task is abandoned + +Task Urgency Who +------------------------------------------------------------------------------- +Floppy driver fixes Low * Joerg Wunsch +Sound driver (GUS/Multicast/cleanup) Medium Steven W/Andrew C. +Curses library problems Medium * Steven W. +SIO driver - reported problems High * Andrew C/Bruce E/??? +Syscons integration / new features High * Soren Schmidt/Jordan +Update FT driver Medium * Javier R/Steven G. +Update gdb High * Paul +Make pcfs less dangerous Low @ ??? +Bruce's disklabel and bad144 fixes Medium * Andrew C. +Misc NetBSD drivers for weird devices Low @ Geoff +Multicast Support Medium * Jordan +Bounce Buffer fixes High * John/David +VM panics and assorted lossage High * John/David +Secure Key support Low * Guido +Install script enhancements Medium * Andrew M/Jordan +Fsck/umount cooperation with dirty bit Low @ Paul R. +PCFS data corruption with cp Medium * Steven W./ATS +PCFS extended DOS partition support Low @ ??? +ISOFS over NSF fix Medium/High * ??? +Libcompat Low * Joerg Wunsch diff --git a/data/releases/1.1/CONTRIB.386BSD b/data/releases/1.1/CONTRIB.386BSD new file mode 100644 index 0000000000..a99b527c48 --- /dev/null +++ b/data/releases/1.1/CONTRIB.386BSD @@ -0,0 +1,196 @@ + + + + + + + + 386BSD Release 0.1 + Contributor List + + Lynne Greer Jolitz + William F. Jolitz + + +_H_a_r_d_w_a_r_e _a_n_d _M_o_n_e_t_a_r_y _C_o_n_t_r_i_b_u_t_o_r_s + +Many people and firms have provided hardware and/or money to +try and keep this unfunded project going despite a recession +and hard times -- usually by digging into their own pockets. +Each of these contributors gave, not only because they +believed that the continuation of 386BSD is vital to the +health of the research, educational, and development commun- +ities, but also because they realize that an individual can +and does make a difference! + +Without the help of the people listed here, this release +would simply not have been possible. We would especially +like to thank Thos Sumner, whose loan of a 486/50 SCSI PC +made development go more rapidly. The rest of the 386BSD +user community should make special note of all these people +and firms and commend them for their generosity and +foresight. + +We hope that their leadership and vision will serve as shin- +ing examples to the entire 386BSD user community, and serve +to encourage others to actively participate in 386BSD. + + Jan van den Bosch + Compaq Computer Corporation + Cyrix Corporation + Dixon Dick + Steven P. Donegan + Jon Erickson + Eric J. Haug + Bob McGhee + Jesus Monroy Jr. + Andrew Moore + Rich Murphey + Mark Ng + Kenji Okamoto + John Plocher + Mark R. Riordan + John B. Scalia + Steve Sizemore + Thos Sumner + David E. Tweten + + + + + +386BSD CONTRIB LIST 1 July 1992 + + + + + + + + + + +_S_o_f_t_w_a_r_e _C_o_n_t_r_i_b_u_t_o_r_s + +The following people have contributed key software programs, +modules and fixes, including novel work and ports of popular +public domain user programs. Some of this software was +directly contributed to us, while other items were made +available to all users via the network. Occasionally, +several people came up with a variety of approaches for a +single item. In this instance, we tried to choose the one +which we felt would best serve the rest of the 386BSD user +base for this release. However, the creativity and persever- +ance of all the software contributors trying to make 386BSD +better for the entire 386BSD user community was consider- +able. Each individual effort is worthy of pride. + +We wish to personally thank all of these people, as they +have helped make 386BSD Release 0.1 a reality. We hope that +these contributors and all the rest of the 386BSD user com- +munity will continue to actively participate to make future +releases even better! + + James Van Artsdalen + Scott Burris + Randall Dean + Chris Demetriou + Mark Eichin + Bruce Evans + Steve Ferguson + Jeffrey Goh + David Greenman + Amancio Hasty Jr + John W. Hatley + Eric J. Haug + Tom Ivar Helbekkmo + John D. Irwin + Peter Klingebiel + Paul Kranenburg + Daniel Lanciani + Karl Lehenbauer + Lee M. J. McLoughlin + Andrew J. Michael + Jesus Monroy Jr. + Daniel A. Muntz + Richard Murphey + Glen Overby + Brad Parker + Herb Pereyl + Ken Raeburn + Paul Richards + Guido van Rooij + Peng-Toh Sim + Wolfgang Solfrank + Dave Stanhope + + +386BSD CONTRIB LIST 2 July 1992 + + + + + + + + + + + Mark Tinguely + Linus Torvalds + Richard Tobin + Rob Warnock + Christian Wiedmann + Pace Willisson + Joerg Wunsch + + And all of the other 386BSD Software Contributors. + + +_S_u_p_p_o_r_t _a_n_d _A_d_v_i_c_e _C_o_n_t_r_i_b_u_t_o_r_s + +Many people have continually encouraged us over the course +of these releases, and provided us with technical advice and +guidance. These people have also spent considerable time and +energy getting this software out to the rest of the 386BSD +community. While it is impossible for us to list everyone +who has been supportive of 386BSD, we wish to personally +thank some of the people who have been of special assistance +to us directly over the course of getting 386BSD out the +door. + + Bruce Blakely + Dave Campbell + Free Software Foundation + Paul Fromberg + Tom Genereaux + John Gilmore + Dave Harris + Jim Joyce + Dan Kionka + Dory Leifer + Per Lindqvist + Marshall Midden + Rich Morin + Silicon Valley Computer Society + John Sokol + Thos Sumner + Karen Trocki + Rob Warnock + + and a special thanks to: + John Erickson, Tami Zemel, Ray Valdez, Monica Berg, Michael Floyd + and everyone else at Dr. Dobbs Journal. + Juergen Fey, Rainer Huttenloher, Gerd Oskar Bausewein + and everyone else at UNIX Magazin. + + And all of the 386BSD User Community. + + + + + +386BSD CONTRIB LIST 3 July 1992 + + + diff --git a/data/releases/1.1/CONTRIB.FreeBSD b/data/releases/1.1/CONTRIB.FreeBSD new file mode 100644 index 0000000000..9fd13fdcec --- /dev/null +++ b/data/releases/1.1/CONTRIB.FreeBSD @@ -0,0 +1,185 @@ + FreeBSD 1.1 + Contributor List + + + +Derived Software Contributors: + +This software was derived from William F. Jolitz's 386BSD release 0.1. +Please see the file CONTRIB.386BSD for the list of contributors from +386BSD. + +Included in this release are the patches from the patch kit version +0.2.4. The names of contributors from the patch kit are listed below. + +There are portions of NetBSD that has been intergraged into FreeBSD +as well. We would like to thank all the contributors to NetBSD for +their work. + + +Hardware Contributors: + +A special thanks to Robert Bruce and Jack Velte of Walnut Creek CDROM +for providing a 486/DX2-66 EISA/VL system that is being used for the +development work. It would have been impossible to do this release +with out their support. + +Dermot McDonnell for his donation of a Toshiba XM3401B CDROM +drive. + + +FreeBSD core: + +Andrew A. Chernov +Andrew Moore +Andreas Schulz +John Dyson +Geoff Rehmet +David Greenman +Jordan K. Hubbard +Nate Williams +Paul Richards +Rich Murphey +Rodney W. Grimes +Scott Mace +Garrett A. Wollman + + +Additional FreeBSD Contributors: + +Adam Glass +Andrew Herbert +Bob Wilcox +Bruce Evans +Charles Hannum +Chris G. Demetriou +Chris Torek +Christoph Robitschko +Curt Mayer +Dave Burgess +Dave Rivers +David Dawes +Frank Maclachlan +Gary A. Browning +Gary Clark II +Guido van Rooij +Havard Eidnes +Holger Veit +Ishii Masahiro, R. Kym Horsell +J.T. Conklin +James Clark +James da Silva et al +Jim Wilson +Joerg Wunsch +Julian Elischer +Julian Stacey > +Keith Bostic +Marc Frajola +Mark Tinguely +Martin Birgmeier +Paul Kranenburg +Paul Mackerras +Poul-Henning Kamp +Rob Shady +Sascha Wildner +Sean Eric Fagan +Serge V. Vakulenko +Steven Wallace +Søren Schmidt +Terry Lee +Theo Deraadt +Yuval Yarom + + +Patch kit patch contributors: + +Adam Glass +Adrian Hall +Andrew A. Chernov +Andrew Herbert +Andrew Moore +Andy Valencia +Arne Henrik Juul +Bakul Shah +Barry Lustig +Bob Wilcox +Branko Lankester +Brett Lymn +Bruce Evans +Charles Hannum +Chris G. Demetriou +Chris Torek +Christoph Robitschko +Daniel Poirot +Dave Burgess +Dave Rivers +David Dawes +David Greenman +Eric J. Haug +Felix Gaehtgens +Frank Maclachlan +Gary A. Browning +Geoff Rehmet +Goran Hammarback +Guido van Rooij +Guy Harris +Havard Eidnes +Herb Peyerl +Ishii Masahiro, R. Kym Horsell +J.T. Conklin +Jagane D Sundar < jagane@netcom.com > +James Clark +James Jegers +James W. Dolter +James da Silva et al +Jay Fenlason +Jim Wilson +Joerg Lohse +Joerg Wunsch +John Dyson - +John Woods +Jordan K. Hubbard +Julian Elischer +Julian Stacey > +Karl Lehenbauer +Keith Bostic +Ken Hughes +Kent Talarico +Kevin Lahey +Marc Frajola +Mark Tinguely +Martin Renters +Michael Galassi +Mike Durkin +Nate Williams +Nick Handel +Pace Willisson +Paul Kranenburg +Paul Mackerras +Paul Popelka +Peter da Silva +Phil Sutherland +Poul-Henning Kamp +Ralf Friedl +Rich Murphey +Rick Macklem +Robert D. Thrush +Rodney W. Grimes +Rog Egge +Sascha Wildner +Scott Burris +Scott Reynolds +Sean Eric Fagan +Simon J Gerraty +Stephen McKay +Terry Lambert +Terry Lee +Warren Toomey +Wiljo Heinen +William Jolitz +Wolfgang Solfrank +Wolfgang Stanglmeier +Yuval Yarom + +$Id: CONTRIB.FreeBSD,v 1.1.1.1 1996-09-24 17:45:50 jfieber Exp $ diff --git a/data/releases/1.1/COPYRIGHT.386BSD b/data/releases/1.1/COPYRIGHT.386BSD new file mode 100644 index 0000000000..c53cb8865b --- /dev/null +++ b/data/releases/1.1/COPYRIGHT.386BSD @@ -0,0 +1,131 @@ + + + + + + + + 386BSD Release 0.1 + Copyright + + + /* + * Copyright (c) 1989, 1990, 1991, 1992 William F. Jolitz, TeleMuse + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. All advertising materials mentioning features or use of this software + * must display the following acknowledgement: + * This software is a component of "386BSD" developed by + * William F. Jolitz, TeleMuse. + * 4. Neither the name of the developer nor the name "386BSD" + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * 386BSD WAS DEVELOPED BY WILLIAM F. JOLITZ. + * 386BSD IS INTENDED FOR RESEARCH AND EDUCATIONAL PURPOSES. + * THIS SOFTWARE SHOULD NOT BE CONSIDERED TO BE A COMMERCIAL PRODUCT. + * THE DEVELOPER URGES THAT USERS WHO REQUIRE A COMMERCIAL PRODUCT + * NOT MAKE USE OF THIS WORK. + * + * FOR USERS WHO WISH TO UNDERSTAND THE 386BSD SYSTEM DEVELOPED + * BY WILLIAM F. JOLITZ, WE RECOMMEND THE USER STUDY WRITTEN + * REFERENCES SUCH AS THE "PORTING UNIX TO THE 386" SERIES + * (BEGINNING JANUARY 1991 "DR. DOBBS JOURNAL", USA AND BEGINNING + * JUNE 1991 "UNIX MAGAZIN", GERMANY) BY WILLIAM F. JOLITZ AND + * LYNNE GREER JOLITZ, AS WELL AS OTHER BOOKS ON UNIX AND THE + * ON-LINE 386BSD USER MANUAL BEFORE USE. A BOOK DISCUSSING THE INTERNALS + * OF 386BSD ENTITLED "386BSD FROM THE INSIDE OUT" WILL BE AVAILABLE LATE 1992. + * + * THIS SOFTWARE IS PROVIDED BY THE DEVELOPER ``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 DEVELOPER 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 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + */ + + + 386BSD Copyright 1 July 1992 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 386BSD Copyright 2 July 1992 + + + + diff --git a/data/releases/1.1/COPYRIGHT.FreeBSD b/data/releases/1.1/COPYRIGHT.FreeBSD new file mode 100644 index 0000000000..7c0c19c4e1 --- /dev/null +++ b/data/releases/1.1/COPYRIGHT.FreeBSD @@ -0,0 +1,121 @@ +This software contains software developed by the University of +California, Berkeley, and its contributors; by the Free Software +Foundation; by the University of Illinois; by the Massachusetts +Institute of Technology; by the University of Vermont and State +Agricultural College; by Carnegie Mellon University; and by a large +number of contributors, whose names are listed in the notices below. + +Portions of this software are subject to one or more of the following +copyright notices. Please see the individual files for the terms and +conditions. + + +Copyright (C) 1980, 1983, 1986, 1988, 1990, 1991, Regents of the + University of California +Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, Free + Software Foundation, Inc. +Copyright (C) 1976, Board of Trustees of the University of Illinois +Copyright (C) 1980, 1981, Ken Harrenstien +Copyright (C) 1982, 1988, 1989, Walter Tichy +Copyright (C) 1983, 1986, 1992, 1993, Eric P. Allman +Copyright (C) 1983, Kenneth L. Greer +Copyright (C) 1984, 1985, 1986, 1987, 1992, Sun Microsystems, Inc. +Copyright (C) 1984, 1987, Stephen L. Moshier +Copyright (C) 1984, 1989, 1990, Bob Corbett and Richard Stallman +Copyright (C) 1984, University of British Columbia +Copyright (C) 1985, 1986, Wayne A. Christopher +Copyright (C) 1985, 1987, 1988, 1989, Adobe Systems, Inc. +Copyright (C) 1985, Stichting Mathematisch Centrum +Copyright (C) 1986, 1987, 1989, 1990, 1991, 1992, Ian F. Darwin +Copyright (C) 1986, 1987, 1989, Frame Technology, Inc. +Copyright (C) 1986, 1987, 1992, Daniel D. Lanciani +Copyright (C) 1986, 1987, Ed James +Copyright (C) 1986, Breslow +Copyright (C) 1986, Gary S. Brown +Copyright (C) 1986, Larry Wall +Copyright (C) 1986, Noah Morgan +Copyright (C) 1986, Stephen Satchell +Copyright (C) 1987, 1988, 1989, 1990, 1991, 1992, Carnegie Mellon University +Copyright (C) 1987, 1988, 1989, Sony Corp. +Copyright (C) 1987, 1988, John Stanback +Copyright (C) 1987, 1988, Ronald S. Karr and Landon Curt Noll +Copyright (C) 1987, 1989, 1990, 1991, Massachusetts Institute of Technology +Copyright (C) 1987, David C. Elliott. +Copyright (C) 1987, IBM Corporation +Copyright (C) 1987, Stuart Cracraft +Copyright (C) 1987, United States Army +Copyright (C) 1988, 1989, 1990, 1993, 1994, Paul A. Vixie +Copyright (C) 1988, 1989, Adam de Boor +Copyright (C) 1988, 1990, University of Utah +Copyright (C) 1988, Julian Onions +Copyright (C) 1988, Mark Nudleman +Copyright (C) 1988, Rayan S. Zachariassen +Copyright (C) 1989, 1990, 1991, 1992, 1993, Frank Kardel +Copyright (C) 1989, 1990, 1991, 1992, 1993, William S. Jolitz +Copyright (C) 1989, 1990, 1991, 1992, Brian Berliner +Copyright (C) 1989, Berkeley Softworks +Copyright (C) 1989, Dale Schumacher +Copyright (C) 1989, Dave Taylor +Copyright (C) 1989, Kenneth Almquist +Copyright (C) 1989, Matthew Self +Copyright (C) 1989, Robert V. Baron +Copyright (C) 1990, 1991, 1992, 1993, AT&T Bell Laboratories and Bellcore +Copyright (C) 1990, 1991, John W. Eaton +Copyright (C) 1990, 1991, Paul Eggert +Copyright (C) 1990, 1993, Andrew Moore +Copyright (C) 1990, John Robert LoVerso +Copyright (C) 1990, Open Software Foundation, Inc. +Copyright (C) 1990, RSA Data Security, Inc. +Copyright (C) 1991, 1992, 1993, 1994, Chris Provenzano +Copyright (C) 1991, 1992, 1993, Ian Lance Taylor +Copyright (C) 1991, 1992, Per Bothner +Copyright (C) 1991, 1992, Per Cederqvist +Copyright (C) 1991, Gregory M. Christy +Copyright (C) 1991, Inge Wallin +Copyright (C) 1991, Joseph Friedman +Copyright (C) 1992, 1993, 1994, David L. Mills +Copyright (C) 1992, 1993, Christopher G. Demetriou +Copyright (C) 1992, 1993, Garrett A. Wollman +Copyright (C) 1992, 1993, HD Associates +Copyright (C) 1992, 1993, Holger Veit +Copyright (C) 1992, 1993, Jean-Loup Gailly +Copyright (C) 1992, 1993, 1994 Joerg Wunsch +Copyright (C) 1992, 1993, John Brezak +Copyright (C) 1992, 1993, Motorola, Inc. +Copyright (C) 1992, 1993, Soeren Schmidt +Copyright (C) 1992, 1993, Theo de Raadt +Copyright (C) 1992, 1993, University of Vermont and State Agricultural College +Copyright (C) 1992, Cygnus Support +Copyright (C) 1992, Diomidis Spinellis +Copyright (C) 1992, Henry Spencer +Copyright (C) 1992, Jeff Polk +Copyright (C) 1992, Terrence R. Lambert +Copyright (C) 1992, University of Guelph +Copyright (C) 1993, 1994, Andrew A. Chernov +Copyright (C) 1993, 1994, David Greenman +Copyright (C) 1993, 1994, John S. Dyson +Copyright (C) 1993, Adam Glass +Copyright (C) 1993, Atsushi Murai +Copyright (C) 1993, Brian Moore +Copyright (C) 1993, Daniel Boulet and RTMX Inc. +Copyright (C) 1993, David Muir Sharnoff +Copyright (C) 1993, David Parsons +Copyright (C) 1993, Gary Clark II +Copyright (C) 1993, Hannu Savolainen +Copyright (C) 1993, Herb Peyerl +Copyright (C) 1993, Herve Schauer Consultants +Copyright (C) 1993, Julian Elischer +Copyright (C) 1993, Julian Stacey +Copyright (C) 1993, K. J. Dryllerakis +Copyright (C) 1993, Martin Birgmeier +Copyright (C) 1993, Paul Kranenburg +Copyright (C) 1993, Paul Richards +Copyright (C) 1993, Thomas Koenig +Copyright (C) 1993, Winning Strategies, Inc. +Copyright (C) 1994, Christoph M. Robitschko +Copyright (C) 1994, University of Maryland +Copyright (C) 1993, 1994, jc@irbs.UUCP (John Capo), + vak@zebub.msk.su (Serge Vakulenko), + ache@astral.msk.su (Andrew A. Chernov) + +$Id: COPYRIGHT.FreeBSD,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/data/releases/1.1/MIRROR.SITES b/data/releases/1.1/MIRROR.SITES new file mode 100644 index 0000000000..57d9a907a7 --- /dev/null +++ b/data/releases/1.1/MIRROR.SITES @@ -0,0 +1,59 @@ + +The FreeBSD software is being mirrored at the following locations: + +Country Site/Directory/Maintainer +======= ========================================================= + +Australia minnie.cs.adfa.oz.au:/BSD/FreeBSD-1.1-RELEASE + + +Australia ftp.physics.su.oz.au:/FreeBSD + David Dawes + +Australia ftp.une.edu.au:/pub/FreeBSD + Gordon Smith + +Austria ftp.tu-graz.ac.at:/pub/FreeBSD + + +Finland ftp.funet.fi:/pub/unix/FreeBSD + + +France ftp.ibp.fr:/pub/FreeBSD + + +Germany ftp.informatik.tu-muenchen.de:/pub/comp/os/bsd/FreeBSD + + +Germany ftp.uni-duisburg.de:/pub/unix/FreeBSD + + +Germany gil.physik.rwth-aachen.de:/pub/FreeBSD + + +Hong Kong ftp.cs.cuhk.hk:/pub/FreeBSD + + +Israel orgchem.weizmann.ac.il:/pub/FreeBSD + + +Netherlands ftp.nl.net:/pub/os/FreeBSD + + +Russia ftp.kiae.su:/FreeBSD + + +UK src.doc.ic.ac.uk:/packages/FreeBSD + + +USA gatekeeper.dec.com:/pub/BSD/FreeBSD + + +USA freebsd.uml.edu:/FreeBSD + + +USA wuarchive.wustl.edu:/systems/unix/FreeBSD + + + +$Id: MIRROR.SITES,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/data/releases/1.1/Makefile b/data/releases/1.1/Makefile new file mode 100644 index 0000000000..39794b4e32 --- /dev/null +++ b/data/releases/1.1/Makefile @@ -0,0 +1,4 @@ +DATA= CONTRIB.386BSD CONTRIB.FreeBSD COPYRIGHT.386BSD COPYRIGHT.FreeBSD +DATA+= MIRROR.SITES PERSONAL.ACKS RELNOTES.FreeBSD SUPPORT.TXT + +.include "../../web.mk" diff --git a/data/releases/1.1/PERSONAL.ACKS b/data/releases/1.1/PERSONAL.ACKS new file mode 100644 index 0000000000..9388fecd37 --- /dev/null +++ b/data/releases/1.1/PERSONAL.ACKS @@ -0,0 +1,17 @@ +The following contributors would like to make these personal +acknowledgements (in no particular order): + +Garrett Wollman would like to thank Gary Barbour and Steve Ackerman of +Utah; Tim Raymond, Jim White, and Jim Ertle of UVM; Malcolm Carlock at +UNR; and John Wroclawski of MIT. + +Nate Williams would like to thank Jaye Mathisen and the entire Computer +Science department of Montana State University for their help, hardware +and encouragement. + +Jordan Hubbard would like to thank IEUNET for bringing the INTERNET to +Ireland, thus making his participation possible at all (albeit expensive) +and his Mom, who would probably be pleased if only she understood any of +this. Hi Mom. + +$Id: PERSONAL.ACKS,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/data/releases/1.1/RELNOTES.FreeBSD b/data/releases/1.1/RELNOTES.FreeBSD new file mode 100644 index 0000000000..46b5c322e4 --- /dev/null +++ b/data/releases/1.1/RELNOTES.FreeBSD @@ -0,0 +1,303 @@ + RELEASE NOTES + FreeBSD + Release 1.1 + +1. Technical overview +--------------------- + +FreeBSD is a freely available, full source 4.3 (+4.4 enhancements) BSD +release for Intel i386/i486 (or compatable) based PC's. It is based +heavily on Bill Jolitz's 386BSD 0.1, with additions from "the patchkit", +NetBSD, CSRG, and the Free Software Foundation. + +Many hundreds of bugs from the 386BSD 0.1 distribution were fixed, +and many out-of-date pieces of software were upgraded to their current +releases in the GAMMA distribution. This 1.1 distribution fixes +many of the first-run problems our BETA and GAMMA users reported back +to us. + +Additionally, many packages such as XFree86 2.1, xview 3.2, elm, nntp, +mh, InterViews and dozens of other miscellaneous utilities have been ported +and are now available as add-ons. See then next section of this document +for more details. + +For a list of contributors, please see the files "CONTRIB.FreeBSD" and +"CONTRIB.386BSD", which should be bundled with your distribution. + +The core of FreeBSD does not contain DES code which would inhibit its +being exported outside the United States. There is an add-on package +to the core distribution, for use only in the United States, that +contains the programs that normally use DES. The auxilliary packages +provided separately can be used by anyone. A freely (from outside the U.S.) +exportable European distribution of DES for our non U.S. users also exists +and is described in the FreeBSD FAQ. + + +2. Supported Configurations +--------------------------- + +FreeBSD currently runs on a wide variety of ISA and EISA bus based +PC's, ranging from 386sx to 486 class machines (though the 386sx is +not recommended). Support for generic IDE or ESDI drive configurations, +various SCSI controller, network and serial cards is also provided. + +Following is a list of all currently known disk controllers and +ethernet cards known to work with FreeBSD. Other configurations may +very well work, and we have simply not received any indication of +this. + + +2.1. Disk Controllers + +WD1003 (any generic MFM/RLL) +WD1007 (any generic IDE/ESDI) + +Adaptec 154x series ISA SCSI controller (as long as you have less than +16MB of main memory). + +Adaptec 174x series EISA SCSI controller in standard and enhanced mode. + +[Note that Buslogic was formerly known as "Bustec"] +Buslogic 545S. +Buslogic 445S VLB SCSI controller +Buslogic 742A and 747. +Please see special notes in /usr/src/KNOWNBUGS (filed under bt742a.c) for +details concerning possible buggy firmware and undocumented switch settings +that may be necessary for proper operation of your controller. + +DTC 3290 EISA SCSI controller in 1542 emulation mode. + +Ultra Store 14F and 34F. + +Seagate ST01/02 SCSI controllers. + +Future Domain 8xx/950 series SCSI controllers. + +With all supported SCSI controllers, full support is provided for +SCSI-I & SCSI-II peripherals, including Disks, tape drives (including +DAT) and CD ROM drives. Note: This and the mcd driver (Mitsumi CDROM +inteface card) is the only way a CD ROM drive may be currently +attached to a FreeBSD system; we do not support SoundBlaster CDROM +interface, or other "mini SCSI" adapters. + +Some controllers have limitations with the way they deal with >16MB of memory, +due to the fact that the ISA bus only has a DMA address space of 24 bits. +If you do your arithmetic, you'll see that this makes it impossible to do +direct DMA to any address >16MB. This limitation is even true of some +EISA controllers (which are normally 32 bit) when they're configured to +emulate an ISA card, which they then do in *all* respects. This problem +is avoided entirely by IDE controllers (which do not use DMA), true EISA +controllers (like the UltraStor or Adaptec 1742A) and most VLB (local bus) +controllers. In these cases, the system will use "bounce buffers" to +to talk to the controller, and is generally the default. + + +2.2. Ethernet cards + +SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, +WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT +based clones. + +Isolan AT 4141-0 (16 bit) + +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, and NE2100 ethernet interface. + +3Com 3C503 Etherlink II + +3Com 3C509 Ethernet cards + +Toshiba ethernet cards + +SMC Elite Ultra + + +2.3. Misc + +AST 4 port serial card using shared IRQ. + +ARNET 8 port serial card using shared IRQ. + +BOCA ATIO66 6 port serial card using shared IRQ. + +STB 4 port card using shared IRQ. + +Mitsumi (all models) CDROM interface and drive. + +Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound +and Roland MPU-401 sound cards. + +FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but +support is apparently close to materializing. Details will be posted +as they develop. + + +3. Obtaining FreeBSD. +--------------------- + +You may obtain FreeBSD in a variety of ways: + +1. FTP/Mail + +You can ftp FreeBSD and any or all of its optional packages from +`freebsd.cdrom.com' - the offical FreeBSD release site. + +For other locations that mirror the FreeBSD software see the file +MIRROR.SITES. Please ftp the distribution from the nearest site +to you netwise. + +If you do not have access to the internet and electronic mail is your +only recourse, then you may still fetch the files by sending mail to +`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message +to get more information on how to fetch files from freebsd.cdrom.com. +Note: This approach will end up sending many *tens of megabytes* +through the mail, and should only be employed as an absolute LAST +resort! + + +2. CDROM + +FreeBSD may be ordered on CDROM from: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) + +Or via the internet from orders@cdrom.com. There current catalog can +be obtained via ftp as ftp.cdrom.com:/cdrom/catalog. + +Cost is $39.95. Shipping (per order not per disc) is $5 in the US, Canada, +or Mexico and $10.00 overseas. They accept Visa, Mastercard, American +Express, and ship COD to the United States. California residents please +add 8.25% sales tax. + +Should you be dissatisfied for any reason, the CD comes with an +unconditional return policy. + +Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD, +you need to contact the FreeBSD team for that. Please see section 4 for +more information. + + +It should be noted, lest you get the wrong impression that "FreeBSD" +is anything but, that almost no one in the "core team" makes money +from distributions or anything else connected with FreeBSD. We simply +provide this information as a public service for those wishing to get +their releases from somewhere other than the net (and the easier it +is for you to obtain our software, the happier we are). + + +4. Reporting problems, making suggestions, submitting code. +----------------------------------------------------------- + +Your suggestions, bug reports and contributions of code are always +valued - please do not hesitate to report any problems you may find +(preferably with a fix attached if you can!). + +The prefered method to submit bug reports from a machine with internet +mail connectivity is to use the sendbug command. Bug reports will be +dutifully filed by our faithful bugfiler program and you can be sure +that we'll do our best to respond to all reported bugs as soon as +possible. + +If, for some reason, you are unable to use the sendbug command to +submit a bug report, you can try to send it to: + + FreeBSD-bugs@freefall.cdrom.com + + +Otherwise, for any questions or suggestions, please send mail to: + + FreeBSD-questions@freefall.cdrom.com + +Additionally, being a volunteer effort, we are always happy to have +extra hands willing to help - there are already far more enhancements +to be done than we can ever manage to do by ourselves! To contact us +on technical matters, or with offers of help, you may send mail to: + + FreeBSD-hackers@freefall.cdrom.com + +Since these mailing lists can experience significant amounts of +traffic, if you've got slow or expensive mail access and you're +only interested in keeping up with significant FreeBSD events, you may +find it preferable to subscribe to: + + FreeBSD-announce@freefall.cdrom.com + + +All but the FreeBSD-bugs groups can be freely joined by anyone wishing to +do so. Send mail to MajorDomo@freefall.cdrom.com and include the keyword +`help' on a line by itself somewhere in the body of the message. This +will give you more information on joining the various lists, accessing +archives, etc. + + +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. It would be very difficult, if not +impossible, to enumerate everyone who's contributed to FreeBSD, but +nonetheless we shall try (in alphabetical order, of course). If your +name is not mentioned, please be assured that its omission is entirely +accidental. + + +The Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, for his extensive work with 386BSD. + +The FreeBSD "core" group: + + Andrew A. Chernov + John Dyson + David Greenman + Rodney W. Grimes + Jordan K. Hubbard + Scott Mace + Andrew Moore + Rich Murphey + Geoff Rehmet + Paul Richards + Andreas Schulz + Nate Williams + Garrett A. Wollman + + +Special mention to: + + Robert Bruce and Jack Velte of Walnut Creek CDROM, without + whose help (and continuing support) this release would never + have been possible. + + Dermot McDonnell for his donation of a Toshiba XM3401B CDROM + drive. + + The NetBSD group for their frequent assistance and commentary. + + Additional FreeBSD helpers and beta testers: + + Gary Browing Jon Cargille + J.T. Conklin Chris Demetriou + Julian Elischer Bruce Evans + Sean Eric Fagan Guy Helmer + Jeffrey Hsu Terry Lambert + Gary Moyer Jaye Mathisen + Curt Mayer L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Rick Weldon Terry Williams + + And everyone at Montana State University for their initial support. + + +Thanks to everyone, especially those not mentioned, and we sincerely +hope you enjoy this release of FreeBSD! + + + The FreeBSD Core Group + +$Id: RELNOTES.FreeBSD,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/data/releases/1.1/SUPPORT.TXT b/data/releases/1.1/SUPPORT.TXT new file mode 100644 index 0000000000..9d01d1e95d --- /dev/null +++ b/data/releases/1.1/SUPPORT.TXT @@ -0,0 +1,89 @@ + +Technical support for this product is NOT provided by Walnut Creek CDROM. + +You need to contact one of the following companies and/or people for +technical support. + +Accurate Automation Company +6005 S.E. Laurel Street +Milwaukie, OR 97222 +Telephone: +1-503-653-7376 +Email: rgrimes@agora.rain.com + +Accurate Automation provides support for FreeBSD including installation, +system configuration, hardware and software trouble shooting, and related +issues. Rates depend upon the type of work being done. Hours are from +10:00 am to 10:00pm PST. + + +Gary Clark II +GB Data Consulting +3801 Polk +Houston, Texas 77003 USA +Telephone: +1-713-587-1644 +Email: gclarkii@radon.gbdata.com + +GB Data Consulting provides support for FreeBSD including installation, usage +and system administration. We also provide classes, on-site service and +distribution sets on floppy. Please email info@radon.gbdata.com or call for +rates and information. + + +Cronyx Ltd. +Research Computer Center, +Moscow State University, +Moscow 199899, Russia +Phone: +7-095-939-5678 +Email: info@cronyx.msk.su + +Cronyx Ltd. provides support for FreeBSD including installation, +configuration, Relcom network connection via UUCP, dialup and leased +line IP. We also provide X Windows configuration and localization, +as well as additional packages installation. Distribution sets on +floppies and tape cartridges available. System software development +including drivers for non-standard equipment. + + +Jordan Hubbard +Timberline Associates (est 1978) +Dublin, Ireland [And soon Boston / San Francisco] +Support hours: 1000 - 2300 GMT +Tel #: 00353-1-332796 +Email: jkh@al.org + +Telephone (or Internet) and on-site consulting for FreeBSD in Ireland, +the United States, United Kingdom and most parts of Europe. Services include +installation, system configuration, networking and custom software +projects, graphical user interfaces a specialty (actively involved with +The X Window System since Version 9 and contributor to the X Consortium). +Reasonable and flexible rates comensurate with location and duration of +assignment. Internet assignments are welcomed, and generally billed at +lower rates. + + +Vector Systems Ltd, Julian H. Stacey. +Post: Holz Strasse 27d, D 80469, Munich (Muenchen), Germany (Deutschland). +Tel.: +49 89 268616 09:00-22:00 TZ=GMT+1 +Email: stacey@freefall.cdrom.com + +Custom designs & support using FreeBSD + X-Windows + FSF/GNU, + own Unix & DOS +C tools. Systems engineering, hardware interfacing, multi lingual systems +(European, Cyrillic, Chinese), communications, scientific, industrial real +time programming. Source Tapes: QIC 525M, 150M, 60M. +Deutsch: Man kann mir in Deutsch schreiben, (oder mich anrufen). +Francais: Je comprend Francais, mais je n'ecris pas des responses en Francais. + + +Sean Vickery +2/449 Milton Road +Auchenflower Qld 4066 +Australia +Telephone: +61 (0)7 870 5241 + Email: seanv@cs.uq.edu.au + +Sean offers support in most FreeBSD matters, including installation +and configuration. His rates are reasonable. As well as on-site +help, support is available over the phone and the net. + + +$Id: SUPPORT.TXT,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/data/releases/2.0.5A/Makefile b/data/releases/2.0.5A/Makefile new file mode 100644 index 0000000000..517e40e9d3 --- /dev/null +++ b/data/releases/2.0.5A/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml notes.sgml + +.include "../../web.mk" diff --git a/data/releases/2.0.5A/announce.sgml b/data/releases/2.0.5A/announce.sgml new file mode 100644 index 0000000000..b3adb4b50a --- /dev/null +++ b/data/releases/2.0.5A/announce.sgml @@ -0,0 +1,158 @@ + + + + %includes; +]> + +&header; + +

    + Date: Tue, 30 May 1995 01:44:26 -0700
    + From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
    + To: announce@FreeBSD.org
    + Subject: Announcing FreeBSD 2.0.5 ALPHA! +

    + +

    It gives me great pleasure to announce the release of FreeBSD 2.0.5-ALPHA! + +

    2.0.5A represents a significant improvement over FreeBSD 2.0R and is our +release-candidate for 2.0.5R later on this week. We're doing a short ALPHA +release in order to shake out any glaring bugs before rolling 2.0.5R and +moving on to 2.1R, which is the bigger goal. If you're looking for 2.1R, +then THIS ISN'T IT. It's an interim release aimed at people who want +something newer and better than 2.0R to run and don't feel like waiting +for late July, which is when 2.1R is scheduled to go into BETA test. + +

    That said, I think most people will enjoy 2.0.5 quite a bit, and while +it's not up to the "full release quality" we hope to have for 2.1R, it's +certainly more stable and generally nicer to use than 2.0R! + +

    2.0.5A is currently available on the following sites: + +

    +
    Primary: +
    ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-ALPHA + +
    Secondary:
    ftp://freefall.cdrom.com/pub/FreeBSD/2.0.5-ALPHA +
    + +

    And should be up on the following MIRROR sites shortly: + +

    +
    Australia
    ftp://ftp.physics.usyd.edu.au/FreeBSD + <dawes@xfree86.org> + +
    Finland
    ftp://nic.funet.fi/pub/unix/FreeBSD + <ftp@nic.funet.fi> + +
    France
    ftp://ftp.ibp.fr/pub/FreeBSD + <Remy.Card@ibp.fr> + +
    Germany
    ftp://ftp.fb9dv.uni-duisburg.de/pub/unix/FreeBSD + <ftp@ftp.fb9dv.uni-duisburg.de> + +
    Germany
    ftp://gil.physik.rwth-aachen.de/pub/FreeBSD + <kuku@gil.physik.rwth-aachen.de> + +
    Germany
    ftp://ftp.uni-paderborn.de/freebsd + <ftp@uni-paderborn.de> + +
    Israel
    ftp://orgchem.weizmann.ac.il/pub/FreeBSD + <serg@klara.weizmann.ac.il> + +
    Hong Kong
    ftp://ftp.hk.super.net/pub/FreeBSD + <ftp-admin@HK.Super.NET> + +
    Korea
    ftp://ftp.cau.ac.kr/pub/FreeBSD + <ftpadm@ftp.cau.ac.kr> + +
    Netherlands
    ftp://ftp.nl.net/pub/os/FreeBSD + <archive@nl.net> + +
    Russia
    ftp://ftp.kiae.su/FreeBSD + <ftp@ftp.kiae.su> + +
    Sweden
    ftp://ftp.luth.se/pub/FreeBSD + <ragge@ludd.luth.se> + +
    Taiwan
    ftp://netbsd.csie.nctu.edu.tw/pub/FreeBSD + <ftp@netbsd.csie.nctu.edu.tw> + +
    Thailand
    ftp://ftp.nectec.or.th/pub/FreeBSD + <ftpadmin@ftp.nectec.or.th> + +
    USA
    ftp://gatekeeper.dec.com/pub/BSD/FreeBSD + <hubbard@gatekeeper.dec.com> + +
    USA
    ftp://ftp.cybernetics.net/pub/FreeBSD + <michael@Cybernetics.NET> + +
    USA
    ftp://ftp.neosoft.com/systems/FreeBSD + <smace@NeoSoft.COM> + +
    USA
    ftp://kryten.atinc.com/pub/FreeBSD + <jmb@kryten.atinc.com> + +
    USA
    ftp://ftp.dataplex.net/pub/FreeBSD + <rkw@dataplex.net> + +
    Japan
    ftp://ftp.tokyonet.ad.jp/pub/FreeBSD + <ftpadmin@TokyoNet.AD.JP> + +
    Japan
    ftp://ftp.tut.ac.jp/FreeBSD + Ashida Hiroyuki <ashida@ftp.tut.ac.jp> + +
    Japan
    ftp://ftp.sra.co.jp/pub/os/FreeBSD + <ftp-admin@sra.co.jp> + +
    Japan
    ftp://ftp.ee.uec.ac.jp/pub/os/mirror/ftp.freebsd.org + <ftp-admin@ftp.ee.uec.ac.jp> + +
    Japan
    ftp://ftp.mei.co.jp/free/PC-UNIX/FreeBSD + TANIGUCHI Syuuhei <tanig@isl.mei.co.jp> + +
    Japan
    ftp://ftp.waseda.ac.jp/pub/FreeBSD + <ftp-admin@waseda.ac.jp> + +
    Japan
    ftp://ftp.pu-toyama.ac.jp/pub/FreeBSD + Yoshihiko USUI <usui@pu-toyama.ac.jp> + +
    Japan
    ftp://ftpsv1.u-aizu.ac.jp/pub/os/FreeBSD + <ftp-admin@u-aizu.ac.jp> + +
    UK
    ftp://src.doc.ic.ac.uk/packages/unix/FreeBSD + <wizards@doc.ic.ac.uk> + +
    UK
    ftp://unix.hensa.ac.uk/pub/walnut.creek/FreeBSD + <archive-admin@unix.hensa.ac.uk> + +
    UK
    ftp://ftp.demon.co.uk/pub/BSD/FreeBSD + <uploads@demon.net> +
    + +
    + +

    NOTE: If you're installing directly from ftp you can simply grab the +boot.flp image from the floppies directory, write it to a floppy +and go from there. There is no need to grab any of the other files; +the installation will perform this step automatically! + +

    Please also read the various README and RELNOTES files in the release for +more information on 2.0.5 - no sense in repeating it all here if most +of you are simply going to download and read it anyway! + +

    I'd like to also extend special thanks to Poul-Henning Kamp & Gary Palmer +for exerting an especially large amount of effort this time in helping +me get the new installation together. Thanks also to Rod Grimes for +playing "source tree pit bull" when I needed him to, thus keeping the +number of headaches I had to suffer in pulling in various last-minute +changes to an absolute minimum. Thanks, guys! This couldn't have +been done without you! + +

    Jordan
    + for the FreeBSD Project. + +&footer; + + diff --git a/data/releases/2.0.5A/notes.sgml b/data/releases/2.0.5A/notes.sgml new file mode 100644 index 0000000000..5970a6ea5f --- /dev/null +++ b/data/releases/2.0.5A/notes.sgml @@ -0,0 +1,738 @@ + + + + %includes; +]> + +&header; + +

    +                                 RELEASE NOTES
+                                    FreeBSD
+                                 Release 2.0.5
+
+1. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our release of FreeBSD 2.0 some 8 months ago, the performance,
+feature set, and stability of FreeBSD has improved dramatically.  The
+largest change is a revamped VM system with a merged VM/file buffer
+cache that not only increases performance, but reduces FreeBSD's
+memory footprint, making a 4MB configuration a more acceptible
+minimum.  Other enhancements include full NIS client and server
+support, transaction TCP support, dial-on-demand PPP, an improved SCSI
+subsystem, early ISDN support, support for FDDI and Fast Ethernet
+(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
+narrow) and many hundreds of bug fixes.
+
+We've also taken the comments and suggestions of many of our users to
+heart and have attempted to provide what we hope is a more sane and
+easily understood installation process.  Your feedback on this
+(constantly evolving) process is especially welcome!
+
+In addition to the base distributions, FreeBSD offers a new ported
+software collection with some 270 commonly sought-after programs.  The
+list of ports ranges from http (WWW) servers, to games, languages,
+editors and almost everything in between.  The entire ports collection
+requires only 10MB of storage, all ports being expressed as "deltas"
+to their original sources.  This makes it much easier for us to update
+ports, and greatly reduces the disk space demands made by the older
+1.0 ports collection.  To compile a port, you simply change to the
+directory of the program you wish to install, type make and let the
+system do the rest.  The full original distribution for each port you
+build is retrieved dynamically off of CDROM or a local ftp site, so
+you need only enough disk space to build the ports you want.  Each
+port is also provided as a pre-compiled "package" which can be
+installed with a simple command (pkg_add) by those who do not wish to
+compile their own ports from source.  See the file:
+        /usr/share/FAQ/Text/ports.FAQ
+for a more complete description of the ports collection.
+
+
+Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD
+has changed almost entirely.  A new port from the Berkeley 4.4 code
+base was done, which brought the legal status of the system out of the
+shadows with the blessing of Novell (the new owners of USL and UNIX).  The
+port to 4.4 has also brought in a host of new features, filesystems
+and enhanced driver support.  With our new unencumbered code base, we
+have every reason to hope that we'll be able to release quality
+operating systems without further legal encumbrance for some time to
+come!
+
+FreeBSD 2.0.5 represents the culmination of 2 years of work and many
+thousands of man hours put in by an international development team.
+We hope you enjoy it!
+
+For a list of contributors and a general project description, please see
+the file "CONTRIB.FreeBSD" which should be bundled with your binary
+distribution.
+
+Also see the "REGISTER.FreeBSD" file for information on registering
+with the "Free BSD user counter".   This counter is for ALL freely
+available variants of BSD, not just FreeBSD, and we urge you to register
+yourself with it.
+
+The core of FreeBSD does not contain DES code which would inhibit its
+being exported outside the United States.  There is an add-on package
+to the core distribution, for use only in the United States, that
+contains the programs that normally use DES.  The auxiliary packages
+provided separately can be used by anyone.   A freely (from outside the
+U.S.) exportable European distribution of DES for our non-U.S. users also
+exists and is described in the FreeBSD FAQ.
+
+If password security for FreeBSD is all you need, and you have no
+requirement for copying encrypted passwords from different hosts
+(Suns, DEC machines, etc) into FreeBSD password entries, then
+FreeBSD's MD5 based security may be all you require!  We feel that our
+default security model is more than a match for DES, and without any
+messy export issues to deal with.  If you're outside (or even inside)
+the U.S., give it a try!
+
+
+1.1 What's new in 2.0.5?
+----------------------
+
+The following features were added or substantially improved between
+the release of 2.0 and this 2.0.5 release.  In order to facilitate
+better communication, the person, or persons, responsible for each
+enhancement is noted.  Any questions regarding the new functionality
+should be directed to them first.
+
+KERNEL:
+
+Merged VM-File Buffer Cache
+---------------------------
+A merged VM/buffer cache design greatly enhances overall system
+performance and makes it possible to do a number of more optimal
+memory allocation strategies that were not possible before.
+
+Owner:                  David Greenman (davidg@FreeBSD.org) and
+                        John Dyson (dyson@implode.root.com)
+
+
+Network PCB hash optimization
+-----------------------------
+For systems with a great number of active TCP connections (WEB and ftp
+servers, for example), this greatly speeds up the lookup time required
+to match an incoming packet up to its associated connection.
+
+Owner:                  David Greenman (davidg@FreeBSD.org)
+
+
+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 
+management of the cache in various other ways while we were at it.
+
+Owner:			Poul-Henning Kamp (phk@FreeBSD.org)
+			David GreenMan (davidg@FreeBSD.org)
+
+
+Less restrictive swap-spaces
+----------------------------
+The need to compile the names of the swap devices into the kernel has been
+removed.  Now swapon will accept any block devices, up to the maximum
+number of swap devices configured in the kernel.
+
+Owner:			Poul-Henning Kamp (phk@FreeBSD.org)
+			David GreenMan (davidg@FreeBSD.org)
+
+
+Hard Wired SCSI Devices
+-----------------------
+Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers
+to SCSI devices as they were probed, allowing a SCSI device failure to
+possibly change unit number assignment and prevent filesystems on
+still functioning disks from mounting.  Hard wiring allows static
+allocation of unit numbers (and hence device names) to scsi devices
+based on SCSI ID and bus.  SCSI configuration occurs in the kernel
+config file.  Samples of the configuration syntax can be found in the
+scsi(4) man page or the LINT kernel config file.
+
+Owner:                  Peter Dufault (dufault@hda.com)
+Sources involved:       sys/scsi/* usr.sbin/config/*
+
+
+Slice Support
+-------------
+FreeBSD now supports a "slice" abstraction which makes it more
+completely interoperable with other operating system partitions.  This
+support will allow FreeBSD to inhabit DOS extended partitions.
+
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+Sources involved:       sys/disklabel.h sys/diskslice.h sys/dkbad.h
+                        kern/subr_diskslice.c kern/subr_dkbad.c
+                        i386/isa/diskslice_machdep.c
+                        i386/isa/wd.c scsi/sd.c dev/vn/vn.c
+
+
+Support for Ontrack Disk Manager Version 6.0
+--------------------------------------------
+Support has been added for disks which use Ontrack Disk Manager.  The
+fdisk program does NOT know about it however, so make all changes
+using the install program on the boot.flp or the Ontrack Disk Manager
+tool under DOS.
+
+Owner:			Poul-Henning Kamp (phk@FreeBSD.org)
+
+
+Bad144 is back and working
+--------------------------
+Bad144 works again, though the semantics are slightly different than
+before in that the bad-spots are kept relative to the slice rather
+than absolute on the disk.
+
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+			Poul-Henning Kamp (phk@FreeBSD.org)
+
+
+NEW DEVICE SUPPORT:
+
+                        SCSI and CDROM Devices
+
+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 with the Karoke variable speed
+playback.
+
+Owner:                  Frank Durda IV   bsdmail@nemesis.lonestar.org
+Sources involved:       isa/matcd
+
+
+Adaptec 2742/2842/2940 SCSI driver
+-----------------------------
+The original 274x/284x driver has evolved considerably since the 2.0
+release.  We now offer full support for the 2940 series as well as the
+Wide models of these cards.  The arbitration bug (as well as many
+others) that caused the driver problems with fast devices has been
+corrected and there is even experimental tagged queuing support
+(kernel option "AHC_TAGENABLE").  John Aycock has also released the
+sequencer code under a "Berkeley style" copyright making the driver
+entirely clean of the GPL.
+
+Owner:                  Justin Gibbs (gibbs@FreeBSD.org)
+Sources involved:       isa/aic7770.c pci/aic7870.c i386/scsi/*
+                        sys/dev/aic7xxx/*
+
+
+NCR5380/NCR53400 SCSI ("ProAudio Spectrum") driver
+--------------------------------------------------
+Owner:                  core
+Submitted by:           Serge Vakulenko (vak@cronyx.ru)
+Sources involved:       isa/ncr5380.c
+
+
+Sony CDROM driver
+-----------------
+Owner:                  core
+Submitted by:           Mikael Hybsch (micke@dynas.se)
+Sources involved:       isa/scd.c
+
+
+                        Serial Devices
+
+SDL Communications Riscom/8 Serial Board Driver
+-----------------------------------------------
+Owner:                  Andrey Chernov (ache@FreeBSD.org)
+Sources involved:       isa/rc.c isa/rcreg.h
+
+
+Cyclades Cyclom-y Serial Board Driver
+-------------------------------------
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+Submitted by:           Andrew Werple (andrew@werple.apana.org.au) and
+                        Heikki Suonsivu (hsu@cs.hut.fi)
+Obtained from:          NetBSD
+Sources involved:       isa/cy.c
+
+
+Cronyx/Sigma sync/async serial driver
+-------------------------------------
+Owner:                  core
+Submitted by:           Serge Vakulenko
+Sources involved:       isa/cronyx.c            
+
+
+
+                        Networking
+
+Diskless booting
+----------------
+Diskless booting in 2.0.5 is much improved.  The boot-program is in
+src/sys/i386/boot/netboot, and can be run from an MSDOS system or
+burned into an EPROM.  Local swapping is also possible.  WD, SMC, 3COM
+and Novell ethernet cards are currently supported.
+
+
+DEC DC21140 Fast Ethernet driver
+--------------------------------
+This driver supports any of the numerous NICs using the DC21140 chipset 
+including the 100Mb DEC DE-500-XA and SMC 9332.
+
+Owner:                  core
+Submitted by:           Matt Thomas (thomas@lkg.dec.com)
+Sources involved:       pci/if_de.c pci/dc21040.h
+
+
+DEC FDDI (DEFPA/DEFEA) driver
+-----------------------------
+Owner:                  core
+Submitted by:           Matt Thomas (thomas@lkg.dec.com)
+Sources involved:       pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h
+
+
+3Com 3c505 (Etherlink/+) NIC driver
+-----------------------------------
+Owner:                  core
+Submitted by:           Dean Huxley (dean@fsa.ca)
+Obtained from:          NetBSD
+Sources involved:       isa/if_eg.c
+
+
+Fujitsu MB86960A family of NICs driver
+-------------------------------------
+Owner:                  core
+Submitted by:           M.S. (seki@sysrap.cs.fujitsu.co.jp)
+Sources involved:       isa/if_fe.c
+
+
+Intel EtherExpress driver
+-------------------------
+Owner:                  Rodney W. Grimes (rgrimes@FreeBSD.org)
+Sources involved:       isa/if_ix.c isa/if_ixreg.h
+
+
+3Com 3c589 driver
+-----------------
+Owner:                  core
+Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
+                        Seiji Murata (seiji@mt.cs.keio.ac.jp) and
+                        Noriyuki Takahashi (hor@aecl.ntt.jp)
+Sources involved:       isa/if_zp.c
+
+
+IBM Credit Card Adapter driver
+------------------------------
+Owner:                  core
+Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
+Sources involved:       isa/pcic.c isa/pcic.h
+
+
+EDSS1 and 1TR6 ISDN interface driver
+------------------------------------
+Owner:                  core
+Submitted by:           Dietmar Friede (dfriede@drnhh.neuhaus.de) and
+                        Juergen Krause (jkr@saarlink.de)
+Sources involved:       gnu/isdn/*
+
+
+                        Miscellaneous Drivers
+
+Joystick driver
+---------------
+Owner:                  Jean-Marc Zucconi (jmz@FreeBSD.org)
+Sources involved:       isa/joy.c
+
+
+National Instruments "LabPC" driver
+-----------------------------------
+Owner:                  Peter Dufault (dufault@hda.com)
+Sources involved:       isa/labpc.c
+
+
+WD7000 driver
+-------------
+Owner:                  Olof Johansson (offe@ludd.luth.se)
+
+
+Pcvt Console driver
+-------------------
+Owner:                  Joerg Wunsch (joerg@FreeBSD.org)
+Submitted by:           Hellmuth Michaelis (hm@altona.hamburg.com)
+Sources involved:       isa/pcvt/*
+
+
+BSD-audio emulator for VAT driver
+---------------------------------
+Owner:                  Amancio Hasty (ahasty@FreeBSD.org) and
+                        Paul Traina (pst@FreeBSD.org)
+Sources involved:       isa/sound/vat_audio.c isa/sound/vat_audioio.h
+
+
+National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver
+--------------------------------------------------------
+Owner:                  core
+Submitted by:           Fred Cawthorne (fcawth@delphi.umd.edu)
+Sources involved:       isa/gpib.c isa/gpib.h isa/gpibreg.h
+
+
+Genius GS-4500 hand scanner driver
+----------------------------------
+Owner:                  core
+Submitted by:           Gunther Schadow (gusw@fub46.zedat.fu-berlin.de)
+Sources involved:       isa/gsc.c isa/gscreg.h
+
+
+CORTEX-I Frame Grabber
+----------------------
+Owner:                  core
+Submitted by:           Paul S. LaFollette, Jr. (
+Sources involved:       isa/ctx.c isa/ctxreg.h
+
+
+Video Spigot video capture card
+-------------------------------
+Owner:                  Jim Lowe
+
+
+
+1.2 Experimental features
+---------------------------------------------
+
+The unionfs and LFS file systems are known to be severely broken in
+2.0.5.  This is in part due to old bugs that we haven't had time to
+resolve yet and the need to update these file systems to deal with the
+new VM system.  We hope to address these issues in a later release of
+FreeBSD.
+
+FreeBSD now supports running iBCS2 compatible binaries (currently SCO
+UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).  The iBCS2
+emulator is in its early stages, but it is functional, we haven't been
+able to do exhaustive testing (lack of commercial apps), but almost
+all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10
+for SCO. Further testing is nessesary to complete this project. There
+is also work under way for ELF & XOUT loaders, and most of the svr4
+syscall wrappers have been written.
+
+Owner:                  Soren Schmidt (sos) & Sean Eric Fagan (sef)
+Sources involved:       sys/i386/ibcs2/* + misc kernel changes.
+=======
+
+
+2. Supported Configurations
+---------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+Following is a list of all disk controllers and ethernet cards currently
+known to work with FreeBSD.  Other configurations may very well work, and
+we have simply not received any indication of this.
+
+
+2.1. Disk Controllers
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+WD7000
+IDE
+ATA
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards
+as they have no on-board BIOS, which is necessary for mapping
+the boot device into the system BIOS I/O vectors.
+They're perfectly usable for external tapes, CDROMs, etc,
+however.  The same goes for any other AIC-6x60 based card
+without a boot ROM.  Some systems DO have a boot ROM, which
+is generally indicated by some sort of message when the system
+is first powered up or reset.  Check your system/board documentation
+for more details.
+
+[Note that Buslogic was formerly known as "Bustec"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+Buslogic 956c PCI SCSI controller
+
+NCR 53C810 and 53C825 PCI SCSI controller.
+NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+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 
+(matcd) Matsushita/Panasonic (Creative) proprietary interface
+(scd)   Sony proprietary interface
+
+Note: CD-Drives with IDE interfaces are not supported at this time.
+
+Some controllers have limitations with the way they deal with >16MB of
+memory, due to the fact that the ISA bus only has a DMA address space
+of 24 bits.  If you do your arithmetic, you'll see that this makes it
+impossible to do direct DMA to any address >16MB.  This limitation is
+even true of some EISA controllers (which are normally 32 bit) when
+they're configured to emulate an ISA card, which they then do in *all*
+respects.  This problem is avoided entirely by IDE controllers (which
+do not use DMA), true EISA controllers (like the UltraStor, Adaptec
+1742A or Adaptec 2742) and most VLB (local bus) controllers.  In the
+cases where it's necessary, the system will use "bounce buffers" to
+talk to the controller so that you can still use more than 16Mb of
+memory without difficulty.
+
+
+2.2. Ethernet cards
+
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21140 based NICs (SMC???? DE???)
+DEC FDDI (DEFPA/DEFEA) NICs
+
+Fujitsu MB86960A family of NICs
+
+Intel EtherExpress
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+
+2.3. Misc
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+Mitsumi (all models) CDROM interface and drive.
+
+SDL Communications Riscom/8 Serial Board.
+
+Soundblaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
+
+Matsushita/Panasonic (Creative SoundBlaster) CDROM interface and drive.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
+support is apparently close to materializing.  Details will be posted
+as the situation develops.
+
+
+3. Obtaining FreeBSD.
+---------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+1. FTP/Mail
+
+You can ftp FreeBSD and any or all of its optional packages from
+`ftp.freebsd.org' - the offical FreeBSD release site.
+
+For other locations that mirror the FreeBSD software see the file
+MIRROR.SITES.  Please ftp the distribution from the nearest site
+to you netwise.
+
+If you do not have access to the internet and electronic mail is your
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
+to get more information on how to fetch files from freebsd.cdrom.com.
+Note: This approach will end up sending many *tens of megabytes*
+through the mail, and should only be employed as an absolute LAST
+resort!
+
+
+2. CDROM
+
+FreeBSD 2.0.5 may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
+
+Or via the internet from orders@cdrom.com or http://www.cdrom.com.
+Their current catalog can be obtained via ftp as:
+        ftp://ftp.cdrom.com/cdrom/catalog.
+
+Cost is $39.95.  Shipping (per order not per disc) is $5 in the US,
+Canada, or Mexico and $10.00 overseas.  They accept Visa, Mastercard,
+American Express, and ship COD within the United States.  California
+residents please add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+
+Reporting problems, making suggestions, submitting code.
+-----------------------------------------------------------
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached if you can!).
+
+The preferred method to submit bug reports from a machine with
+internet mail connectivity is to use the send-pr command.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.
+
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                questions@FreeBSD.org
+
+Additionally, being a volunteer effort, we are always happy to have
+extra hands willing to help - there are already far more enhancements
+to be done than we can ever manage to do by ourselves!  To contact us
+on technical matters, or with offers of help, you may send mail to:
+
+                hackers@FreeBSD.org
+
+Since these mailing lists can experience significant amounts of
+traffic, if you have slow or expensive mail access and you are
+only interested in keeping up with significant FreeBSD events, you may
+find it preferable to subscribe to:
+
+                announce@FreeBSD.org
+
+
+All but the freebsd-bugs groups 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
+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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If your
+name is not mentioned, please be assured that its omission is entirely
+accidental.
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his initial work with 386BSD.
+
+The FreeBSD Core Team
+(in alphabetical order by first name):
+
+        Andreas Schulz <ats@FreeBSD.org>
+        Andrey A. Chernov <ache@FreeBSD.org>
+        Bruce Evans <bde@FreeBSD.org>
+        David Greenman <davidg@FreeBSD.org>
+        Garrett A. Wollman <wollman@FreeBSD.org>
+        Gary Palmer <gpalmer@FreeBSD.org>
+        Geoff Rehmet <csgr@FreeBSD.org>
+        Jack Vogel <jackv@FreeBSD.org>
+        John Dyson <dyson@FreeBSD.org>
+        Jordan K. Hubbard <jkh@FreeBSD.org>
+        Justin Gibbs <gibbs@FreeBSD.org>
+        Paul Richards <paul@FreeBSD.org>
+        Poul-Henning Kamp <phk@FreeBSD.org>
+        Rich Murphey <rich@FreeBSD.org>
+        Rodney W. Grimes <rgrimes@FreeBSD.org>
+        Satoshi Asami <asami@FreeBSD.org>
+        Søren Schmidt <sos@FreeBSD.org>
+
+Special mention to:
+
+        Walnut Creek CDROM, without whose help (and continuing support)
+        this release would never have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        Additional FreeBSD helpers and beta testers:
+
+        J.T. Conklin                            Julian Elischer
+        Frank Durda IV                          Peter Dufault
+        Sean Eric Fagan                         Jeffrey Hsu
+        Terry Lambert                           L Jonas Olsson
+        Chris Provenzano                        Dave Rivers
+        Guido van Rooij                         Steven Wallace
+        Atsushi Murai                           Scott Mace
+        Nate Williams
+
+        And everyone at Montana State University for their initial support.
+
+
+Jordan would also like to give special mention to Poul-Henning Kamp
+and Gary Palmer, both of whom put in long hours helping him to
+construct the new installation utility.  Poul, being a proud new
+father, was especially pressed for time yet somehow managed to put in
+significant amount of effort anyway and this release could not have
+happened without him.  Thank you both!
+
+Thanks also to everyone else who helped, especially those not
+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 
+
    + +&footer; + + diff --git a/data/releases/2.0.5R/Makefile b/data/releases/2.0.5R/Makefile new file mode 100644 index 0000000000..517e40e9d3 --- /dev/null +++ b/data/releases/2.0.5R/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml notes.sgml + +.include "../../web.mk" diff --git a/data/releases/2.0.5R/announce.sgml b/data/releases/2.0.5R/announce.sgml new file mode 100644 index 0000000000..c4f06a3015 --- /dev/null +++ b/data/releases/2.0.5R/announce.sgml @@ -0,0 +1,112 @@ + + + + %includes; +]> + +&header; + +

    + Date: Sat, 10 Jun 1995 13:01:12 -0700
    + From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
    + To: announce@freefall.cdrom.com, hackers@freefall.cdrom.com
    + Subject: Announcing FreeBSD 2.0.5 RELEASE! + +

    It is my usual pleasure (and, to a small degree, relief! + :) to announce the release of FreeBSD 2.0.5R - the final + release in the 2.0.5 series. + +

    This release provides both what I hope will be an exciting + glimpse of some of the new technologies and directions we + have planned for 2.1R and a stable and much + easier-to-install alternative to 2.0R. + +

    Highlights of this release are: + +

      +
    • Multi-lingual documentation files. +
    • Completely menu driven installation. +
    • More installation media types. +
    • Support for a much larger range of PC hardware. +
    • Easy mounting of DOS partitions and CD devices + mounted automatically. +
    • "Canned" installation types for easy installs. +
    • Easy post-configuration menu +
    + +

    And many other new features and bug fixes. + +

    The ports and packages collection has also been bundled + with 2.0.5R to prevent synchronization errors. While this + does result in a larger overall distribution, it at least + ensures more consistent results when installing ports and + packages. + +

    More information on the release may be found in the + RELNOTES and README files, so I'll simply leave you all to + see for yourself! + +

    The usual locations: + +

    + +

    As well as the usual mirrors, once they pick it up. + +

    It is also available on CD from Walnut Creek CDROM, the + project's principle sponsors. Please see the release notes + for ordering information. + +

    Any feedback should be sent to hackers@freebsd.org. + I will be leaving the country shortly (about 3 hours :) and + will try to read my email as often as possible, but for + quicker replies please send to the mailing list. + +

    Thank you! + +

    Jordan + +

    + +

    Date: Mon, 12 Jun 1995 00:33:07 -0700
    + From: Gary Palmer <gpalmer@westhill.cdrom.com>
    + To: announce@FreeBSD.ORGD
    + Subject: 2.0.5-RELEASE update + +

    Yes, you have guessed it. As a result of the recent + feedback we have had about the origional 2.0.5-RELEASE, we + have gone poking and found a couple of bugs on the + origional boot.flp image. There is now a + /pub/FreeBSD/2.0.5-RELEASE/UPDATES directory on ftp.cdrom.com + and freefall.cdrom.com + with a version of boot.flp which will fix the following + problems: + +

      +
    • The kernel was too big to boot on 4Mb machines. + +
    • It was possible to specify the filesystem mount points + in such a way that the program would mount the filesystem + before the parent filesystem was mounted (e.g. it would + mount /usr/local and then /usr) +
    + +

    As the CDROM has not gone to replication yet, this updated + floppy image will be appearing on the CDROM. + +

    Sorry to all those who had problems with the first boot + floppy set - I will personally nail Jordan to his chair and + nail the chair to the floor in front of his computer the + next time we roll a release! + +

    Gary + +&footer; + + diff --git a/data/releases/2.0.5R/notes.sgml b/data/releases/2.0.5R/notes.sgml new file mode 100644 index 0000000000..d70b6514f7 --- /dev/null +++ b/data/releases/2.0.5R/notes.sgml @@ -0,0 +1,760 @@ + + + + %includes; +]> + +&header; + +

    +                                 RELEASE NOTES
+                                    FreeBSD
+                                 Release 2.0.5
+
+1. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our release of FreeBSD 2.0 some 8 months ago, the performance,
+feature set, and stability of FreeBSD has improved dramatically.  The
+largest change is a revamped VM system with a merged VM/file buffer
+cache that not only increases performance, but reduces FreeBSD's
+memory footprint, making a 4MB configuration a more acceptable
+minimum.  Other enhancements include full NIS client and server
+support, transaction TCP support, dial-on-demand PPP, an improved SCSI
+subsystem, early ISDN support, support for FDDI and Fast Ethernet
+(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
+narrow) and many hundreds of bug fixes.
+
+We've also taken the comments and suggestions of many of our users to
+heart and have attempted to provide what we hope is a more sane and
+easily understood installation process.  Your feedback on this
+(constantly evolving) process is especially welcome!
+
+In addition to the base distributions, FreeBSD offers a new ported
+software collection with some 270 commonly sought-after programs.  The
+list of ports ranges from http (WWW) servers, to games, languages,
+editors and almost everything in between.  The entire ports collection
+requires only 10MB of storage, all ports being expressed as "deltas"
+to their original sources.  This makes it much easier for us to update
+ports, and greatly reduces the disk space demands made by the older
+1.0 ports collection.  To compile a port, you simply change to the
+directory of the program you wish to install, type make and let the
+system do the rest.  The full original distribution for each port you
+build is retrieved dynamically off of CDROM or a local ftp site, so
+you need only enough disk space to build the ports you want.  (Almost)
+every port is also provided as a pre-compiled "package" which can be
+installed with a simple command (pkg_add) by those who do not wish to
+compile their own ports from source.  See the file:
+        /usr/share/FAQ/Text/ports.FAQ
+for a more complete description of the ports collection.
+
+
+Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD
+has changed almost entirely.  A new port from the Berkeley 4.4 code
+base was done, which brought the legal status of the system out of the
+shadows with the blessing of Novell (the new owners of USL and UNIX).  The
+port to 4.4 has also brought in a host of new features, filesystems
+and enhanced driver support.  With our new unencumbered code base, we
+have every reason to hope that we'll be able to release quality
+operating systems without further legal encumbrance for some time to
+come!
+
+FreeBSD 2.0.5 represents the culmination of 2 years of work and many
+thousands of man hours put in by an international development team.
+We hope you enjoy it!
+
+A number of additional documents which you may find very helpful in
+the process of installing and using FreeBSD may also be found in
+the "FAQ" directory, either under /usr/share/FAQ on an installed
+system or at the top level of the CDROM or FTP distribution from
+where you're reading this file.  Please consult FAQ/Text/ROADMAP
+for a brief description of the resources provided by the FAQ directory.
+
+For a list of contributors and a general project description, please see
+the file "CONTRIB.FreeBSD" which should be bundled with your binary
+distribution.
+
+Also see the "REGISTER.FreeBSD" file for information on registering
+with the "Free BSD user counter".   This counter is for ALL freely
+available variants of BSD, not just FreeBSD, and we urge you to register
+yourself with it.
+
+The core of FreeBSD does not contain DES code which would inhibit its
+being exported outside the United States.  There is an add-on package
+to the core distribution, for use only in the United States, that
+contains the programs that normally use DES.  The auxiliary packages
+provided separately can be used by anyone.   A freely (from outside the
+U.S.) exportable European distribution of DES for our non-U.S. users also
+exists and is described in the FreeBSD FAQ.
+
+If password security for FreeBSD is all you need, and you have no
+requirement for copying encrypted passwords from different hosts
+(Suns, DEC machines, etc) into FreeBSD password entries, then
+FreeBSD's MD5 based security may be all you require!  We feel that our
+default security model is more than a match for DES, and without any
+messy export issues to deal with.  If you're outside (or even inside)
+the U.S., give it a try!
+
+
+1.1 What's new in 2.0.5?
+------------------------
+
+The following features were added or substantially improved between
+the release of 2.0 and this 2.0.5 release.  In order to facilitate
+better communication, the person, or persons, responsible for each
+enhancement is noted.  Any questions regarding the new functionality
+should be directed to them first.
+
+KERNEL:
+
+Merged VM-File Buffer Cache
+---------------------------
+A merged VM/buffer cache design greatly enhances overall system
+performance and makes it possible to do a number of more optimal
+memory allocation strategies that were not possible before.
+
+Owner:                  David Greenman (davidg@FreeBSD.org) and
+                        John Dyson (dyson@implode.root.com)
+
+
+Network PCB hash optimization
+-----------------------------
+For systems with a great number of active TCP connections (WEB and ftp
+servers, for example), this greatly speeds up the lookup time required
+to match an incoming packet up to its associated connection.
+
+Owner:                  David Greenman (davidg@FreeBSD.org)
+
+
+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 
+management of the cache in various other ways while we were at it.
+
+Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
+                        David Greenman (davidg@FreeBSD.org)
+
+
+Less restrictive swap-spaces
+----------------------------
+The need to compile the names of the swap devices into the kernel has been
+removed.  Now swapon will accept any block devices, up to the maximum
+number of swap devices configured in the kernel.
+
+Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
+                        David Greenman (davidg@FreeBSD.org)
+
+
+Hard Wired SCSI Devices
+-----------------------
+Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers
+to SCSI devices as they were probed, allowing a SCSI device failure to
+possibly change unit number assignment and prevent filesystems on
+still functioning disks from mounting.  Hard wiring allows static
+allocation of unit numbers (and hence device names) to scsi devices
+based on SCSI ID and bus.  SCSI configuration occurs in the kernel
+config file.  Samples of the configuration syntax can be found in the
+scsi(4) man page or the LINT kernel config file.
+
+Owner:                  Peter Dufault (dufault@hda.com)
+Sources involved:       sys/scsi/* usr.sbin/config/*
+
+
+Slice Support
+-------------
+FreeBSD now supports a "slice" abstraction which makes it more
+completely interoperable with other operating system partitions.  This
+support will allow FreeBSD to inhabit DOS extended partitions.
+
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+Sources involved:       sys/disklabel.h sys/diskslice.h sys/dkbad.h
+                        kern/subr_diskslice.c kern/subr_dkbad.c
+                        i386/isa/diskslice_machdep.c
+                        i386/isa/wd.c scsi/sd.c dev/vn/vn.c
+
+
+Support for Ontrack Disk Manager Version 6.0
+--------------------------------------------
+Support has been added for disks which use Ontrack Disk Manager.  The
+fdisk program does NOT know about it however, so make all changes
+using the install program on the boot.flp or the Ontrack Disk Manager
+tool under DOS.
+
+Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
+
+
+Bad144 is back and working
+--------------------------
+Bad144 works again, though the semantics are slightly different than
+before in that the bad-spots are kept relative to the slice rather
+than absolute on the disk.
+
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+                        Poul-Henning Kamp (phk@FreeBSD.org)
+
+
+NEW DEVICE SUPPORT:
+
+                        SCSI and CDROM Devices
+
+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) 
+data frames of any compact disc.  Audio discs may be played using Karoke
+variable speed functions.
+
+Owner:                  Frank Durda IV   bsdmail@nemesis.lonestar.org
+Sources involved:       isa/matcd
+
+
+Adaptec 2742/2842/2940 SCSI driver
+----------------------------------
+The original 274x/284x driver has evolved considerably since the 2.0
+release.  We now offer full support for the 2940 series as well as the
+Wide models of these cards.  The arbitration bug (as well as many
+others) that caused the driver problems with fast devices has been
+corrected and there is even experimental tagged queuing support
+(kernel option "AHC_TAGENABLE").  John Aycock has also released the
+sequencer code under a "Berkeley style" copyright making the driver
+entirely clean of the GPL.
+
+Owner:                  Justin Gibbs (gibbs@FreeBSD.org)
+Sources involved:       isa/aic7770.c pci/aic7870.c i386/scsi/*
+                        sys/dev/aic7xxx/*
+
+
+NCR5380/NCR53400 SCSI ("ProAudio Spectrum") driver
+--------------------------------------------------
+Owner:                  core
+Submitted by:           Serge Vakulenko (vak@cronyx.ru)
+Sources involved:       isa/ncr5380.c
+
+
+Sony CDROM driver
+-----------------
+Owner:                  core
+Submitted by:           Mikael Hybsch (micke@dynas.se)
+Sources involved:       isa/scd.c
+
+
+                        Serial Devices
+
+SDL Communications Riscom/8 Serial Board Driver
+-----------------------------------------------
+Owner:                  Andrey Chernov (ache@FreeBSD.org)
+Sources involved:       isa/rc.c isa/rcreg.h
+
+
+Cyclades Cyclom-y Serial Board Driver
+-------------------------------------
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+Submitted by:           Andrew Werple (andrew@werple.apana.org.au) and
+                        Heikki Suonsivu (hsu@cs.hut.fi)
+Obtained from:          NetBSD
+Sources involved:       isa/cy.c
+
+
+Cronyx/Sigma sync/async serial driver
+-------------------------------------
+Owner:                  core
+Submitted by:           Serge Vakulenko
+Sources involved:       isa/cronyx.c            
+
+
+
+                        Networking
+
+Diskless booting
+----------------
+Diskless booting in 2.0.5 is much improved.  The boot-program is in
+src/sys/i386/boot/netboot, and can be run from an MSDOS system or
+burned into an EPROM.  Local swapping is also possible.  WD, SMC, 3COM
+and Novell ethernet cards are currently supported.
+
+
+DEC DC21140 Fast Ethernet driver
+--------------------------------
+This driver supports any of the numerous NICs using the DC21140 chipset 
+including the 100Mb DEC DE-500-XA and SMC 9332.
+
+Owner:                  core
+Submitted by:           Matt Thomas (thomas@lkg.dec.com)
+Sources involved:       pci/if_de.c pci/dc21040.h
+
+
+DEC FDDI (DEFPA/DEFEA) driver
+-----------------------------
+Owner:                  core
+Submitted by:           Matt Thomas (thomas@lkg.dec.com)
+Sources involved:       pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h
+
+
+3Com 3c505 (Etherlink/+) NIC driver
+-----------------------------------
+Owner:                  core
+Submitted by:           Dean Huxley (dean@fsa.ca)
+Obtained from:          NetBSD
+Sources involved:       isa/if_eg.c
+
+
+Fujitsu MB86960A family of NICs driver
+-------------------------------------
+Owner:                  core
+Submitted by:           M.S. (seki@sysrap.cs.fujitsu.co.jp)
+Sources involved:       isa/if_fe.c
+
+
+Intel EtherExpress driver
+-------------------------
+Owner:                  Rodney W. Grimes (rgrimes@FreeBSD.org)
+Sources involved:       isa/if_ix.c isa/if_ixreg.h
+
+
+3Com 3c589 driver
+-----------------
+Owner:                  core
+Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
+                        Seiji Murata (seiji@mt.cs.keio.ac.jp) and
+                        Noriyuki Takahashi (hor@aecl.ntt.jp)
+Sources involved:       isa/if_zp.c
+
+
+IBM Credit Card Adapter driver
+------------------------------
+Owner:                  core
+Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
+Sources involved:       isa/pcic.c isa/pcic.h
+
+
+EDSS1 and 1TR6 ISDN interface driver
+------------------------------------
+Owner:                  core
+Submitted by:           Dietmar Friede (dfriede@drnhh.neuhaus.de) and
+                        Juergen Krause (jkr@saarlink.de)
+Sources involved:       gnu/isdn/*
+
+
+                        Miscellaneous Drivers
+
+Joystick driver
+---------------
+Owner:                  Jean-Marc Zucconi (jmz@FreeBSD.org)
+Sources involved:       isa/joy.c
+
+
+National Instruments "LabPC" driver
+-----------------------------------
+Owner:                  Peter Dufault (dufault@hda.com)
+Sources involved:       isa/labpc.c
+
+
+WD7000 driver
+-------------
+Owner:                  Olof Johansson (offe@ludd.luth.se)
+
+
+Pcvt Console driver
+-------------------
+Owner:                  Joerg Wunsch (joerg@FreeBSD.org)
+Submitted by:           Hellmuth Michaelis (hm@altona.hamburg.com)
+Sources involved:       isa/pcvt/* usr.sbin/pcvt/*
+
+
+BSD-audio emulator for VAT driver
+---------------------------------
+Owner:                  Amancio Hasty (ahasty@FreeBSD.org) and
+                        Paul Traina (pst@FreeBSD.org)
+Sources involved:       isa/sound/vat_audio.c isa/sound/vat_audioio.h
+
+
+National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver
+--------------------------------------------------------
+Owner:                  core
+Submitted by:           Fred Cawthorne (fcawth@delphi.umd.edu)
+Sources involved:       isa/gpib.c isa/gpib.h isa/gpibreg.h
+
+
+Genius GS-4500 hand scanner driver
+----------------------------------
+Owner:                  core
+Submitted by:           Gunther Schadow (gusw@fub46.zedat.fu-berlin.de)
+Sources involved:       isa/gsc.c isa/gscreg.h
+
+
+CORTEX-I Frame Grabber
+----------------------
+Owner:                  core
+Submitted by:           Paul S. LaFollette, Jr.
+Sources involved:       isa/ctx.c isa/ctxreg.h
+
+
+Video Spigot video capture card
+-------------------------------
+Owner:                  Jim Lowe
+
+
+
+1.2 Experimental features
+-------------------------
+
+The unionfs and LFS file systems are known to be severely broken in
+2.0.5.  This is in part due to old bugs that we haven't had time to
+resolve yet and the need to update these file systems to deal with the
+new VM system.  We hope to address these issues in a later release of
+FreeBSD.
+
+FreeBSD now supports running iBCS2 compatible binaries (currently SCO
+UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).  The iBCS2
+emulator is in its early stages, but it is functional, we haven't been
+able to do exhaustive testing (lack of commercial apps), but almost
+all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10
+for SCO. Further testing is nessesary to complete this project. There
+is also work under way for ELF & XOUT loaders, and most of the svr4
+syscall wrappers have been written.
+
+FreeBSD also implements enough of its Linux compatibility that we
+can now run Linux DOOM!  See the ``xperimnt'' directory (on your local
+FTP server or CDROM) for full docs on how to set this up.
+
+Owner:                  Soren Schmidt (sos) & Sean Eric Fagan (sef)
+Sources involved:       sys/i386/ibcs2/* + misc kernel changes.
+
+
+2. Supported Configurations
+---------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+Following is a list of all disk controllers and ethernet cards currently
+known to work with FreeBSD.  Other configurations may very well work, and
+we have simply not received any indication of this.
+
+
+2.1. Disk Controllers
+---------------------
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+WD7000
+IDE
+ATA
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards as they have no
+   on-board BIOS, which is necessary for mapping the boot device into the
+   system BIOS I/O vectors.  They're perfectly usable for external tapes,
+   CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
+   without a boot ROM.  Some systems DO have a boot ROM, which is generally
+   indicated by some sort of message when the system is first powered up
+   or reset.  Check your system/board documentation for more details.
+
+[Note that Buslogic was formerly known as "Bustec"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+Buslogic 956c PCI SCSI controller
+
+NCR 53C810 and 53C825 PCI SCSI controller.
+NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+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 
+(matcd) Matsushita/Panasonic (Creative) proprietary interface
+(scd)   Sony proprietary interface
+
+Note: CD-Drives with IDE interfaces are not supported at this time.
+
+Some controllers have limitations with the way they deal with >16MB of
+memory, due to the fact that the ISA bus only has a DMA address space
+of 24 bits.  If you do your arithmetic, you'll see that this makes it
+impossible to do direct DMA to any address >16MB.  This limitation is
+even true of some EISA controllers (which are normally 32 bit) when
+they're configured to emulate an ISA card, which they then do in *all*
+respects.  This problem is avoided entirely by IDE controllers (which
+do not use DMA), true EISA controllers (like the UltraStor, Adaptec
+1742A or Adaptec 2742) and most VLB (local bus) controllers.  In the
+cases where it's necessary, the system will use "bounce buffers" to
+talk to the controller so that you can still use more than 16Mb of
+memory without difficulty.
+
+
+2.2. Ethernet cards
+-------------------
+
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21140 based NICs (SMC???? DE???)
+DEC FDDI (DEFPA/DEFEA) NICs
+
+Fujitsu MB86960A family of NICs
+
+Intel EtherExpress
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+
+2.3. Misc
+---------
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+Mitsumi (all models) CDROM interface and drive.
+
+SDL Communications Riscom/8 Serial Board.
+
+SoundBlaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
+
+Matsushita/Panasonic (Creative SoundBlaster) CDROM interface and drive.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
+support is apparently close to materializing.  Details will be posted
+as the situation develops.
+
+
+3. Obtaining FreeBSD
+--------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+1. FTP/Mail
+
+You can ftp FreeBSD and any or all of its optional packages from
+`ftp.freebsd.org' - the official FreeBSD release site.
+
+For other locations that mirror the FreeBSD software see the file
+MIRROR.SITES.  Please ftp the distribution from the nearest site
+to you netwise.
+
+If you do not have access to the internet and electronic mail is your
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
+to get more information on how to fetch files from ftp.freebsd.org.
+Note: This approach will end up sending many *tens of megabytes*
+through the mail, and should only be employed as an absolute LAST
+resort!
+
+
+2. CDROM
+
+FreeBSD 2.0.5 may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
+
+Or via the internet from orders@cdrom.com or http://www.cdrom.com.
+Their current catalog can be obtained via ftp as:
+        ftp://ftp.cdrom.com/cdrom/catalog.
+
+Cost per CD is $39.95, or $24.95 with a FreeBSD subscription.  With
+a subscription, you will automatically receive updates as they
+are released.  Your credit card will be billed when each disk is shipped
+and you may cancel your subscription at any time without further obligation.
+
+Walnut Creek CDROM also sells a full line of FreeBSD related merchandise such
+as T-shirts ($14.95, available in "child", Large and XL sizes), coffee mugs
+($9.95), tattoos ($0.25 each) and posters ($3.00).
+
+Shipping (per order not per disc) is $5 in the US, Canada or
+Mexico and $9.00 overseas.  They accept Visa, Mastercard, Discover,
+American Express or checks in U.S. Dollars and ship COD within the
+United States.  California residents please add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+
+Reporting problems, making suggestions, submitting code
+-------------------------------------------------------
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached if you can!).
+
+The preferred method to submit bug reports from a machine with
+internet mail connectivity is to use the send-pr command.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.
+
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                questions@FreeBSD.org
+
+Additionally, being a volunteer effort, we are always happy to have
+extra hands willing to help - there are already far more enhancements
+to be done than we can ever manage to do by ourselves!  To contact us
+on technical matters, or with offers of help, you may send mail to:
+
+                hackers@FreeBSD.org
+
+Since these mailing lists can experience significant amounts of
+traffic, if you have slow or expensive mail access and you are
+only interested in keeping up with significant FreeBSD events, you may
+find it preferable to subscribe to:
+
+                announce@FreeBSD.org
+
+
+All but the freebsd-bugs groups 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
+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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If your
+name is not mentioned, please be assured that its omission is entirely
+accidental.
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his initial work with 386BSD.
+
+The FreeBSD Core Team
+(in alphabetical order by first name):
+
+        Andreas Schulz <ats@FreeBSD.org>
+        Andrey A. Chernov <ache@FreeBSD.org>
+        Bruce Evans <bde@FreeBSD.org>
+        David Greenman <davidg@FreeBSD.org>
+        Garrett A. Wollman <wollman@FreeBSD.org>
+        Gary Palmer <gpalmer@FreeBSD.org>
+        Geoff Rehmet <csgr@FreeBSD.org>
+        Jack Vogel <jackv@FreeBSD.org>
+        John Dyson <dyson@FreeBSD.org>
+        Jordan K. Hubbard <jkh@FreeBSD.org>
+        Justin Gibbs <gibbs@FreeBSD.org>
+        Paul Richards <paul@FreeBSD.org>
+        Poul-Henning Kamp <phk@FreeBSD.org>
+        Rich Murphey <rich@FreeBSD.org>
+        Rodney W. Grimes <rgrimes@FreeBSD.org>
+        Satoshi Asami <asami@FreeBSD.org>
+        Søren Schmidt <sos@FreeBSD.org>
+
+Special mention to:
+
+        Walnut Creek CDROM, without whose help (and continuing support)
+        this release would never have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        Additional FreeBSD helpers and beta testers:
+
+        J.T. Conklin                            Julian Elischer
+        Frank Durda IV                          Peter Dufault
+        Sean Eric Fagan                         Jeffrey Hsu
+        Terry Lambert                           L Jonas Olsson
+        Chris Provenzano                        Dave Rivers
+        Guido van Rooij                         Steven Wallace
+        Atsushi Murai                           Scott Mace
+        Nate Williams
+
+        And everyone at Montana State University for their initial support.
+
+
+Jordan would also like to give special thanks to Poul-Henning Kamp and
+Gary Palmer, both of whom put in long hours helping him to construct
+the new installation utility.  Poul, being a proud new father, was
+especially pressed for time and yet somehow managed to put in
+a significant amount of effort anyway.  This release could not have
+happened without him!  Thank you both!
+
+Thanks also to everyone else who helped, especially those not
+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 
+
    + +&footer; + + diff --git a/data/releases/2.0/Makefile b/data/releases/2.0/Makefile new file mode 100644 index 0000000000..8955b2ea3e --- /dev/null +++ b/data/releases/2.0/Makefile @@ -0,0 +1,4 @@ +DOCS= announce.sgml credits.sgml install.sgml notes.sgml + +.include "../../web.mk" + diff --git a/data/releases/2.0/announce.sgml b/data/releases/2.0/announce.sgml new file mode 100644 index 0000000000..5a9fce45e5 --- /dev/null +++ b/data/releases/2.0/announce.sgml @@ -0,0 +1,155 @@ + + + + %includes; +]> + +&header; + +

    +To: announce@freefall.cdrom.com
    +Subject: 2.0 RELEASE is now available on ftp.freebsd.org!
    +Date: Tue, 22 Nov 1994 06:35:37 -0800
    +From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com> +

    + +

    +The FreeBSD Project team is very pleased to announce their release of +FreeBSD 2.0; a full 32 bit 4.4 BSD Lite based operating system for +Intel PCs (i386, i486 and Pentium class). + +

    +Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD has +changed almost entirely. A new port from the Berkeley 4.4 code base +was done, which brought the legal status of the system out of the +shadows with the blessing of Novell (new owners of USL and UNIX). The +port to 4.4 also brought in a host of new features, filesystems and +enhanced driver support. With our new unencumbered code base, we have +every reason to hope that we'll be able to release quality operating +systems without further legal encumbrance for some time to come! + +

    +FreeBSD 2.0 represents the culmination of almost 2 years of work and +many thousands of man hours put in by an international development +team. We hope you enjoy it! + +

    +FreeBSD 2.0 also features an advanced installation that enables one to +install from tape, CD, NFS or FTP over SLIP, ethernet or the parallel +port, and DOS floppies or hard disk partitions. This is, we feel, our +easiest to use installation yet! Many many suggestions from the +previous 2.0 ALPHA release were incorporated, and RELEASE is now far +less dangerous [we hope :-)]than ALPHA was! + +

    +FreeBSD 2.0 also supports more friendly co-habitation with other +operating systems, allowing you to easily mount DOS filesystems and +install a multi-OS boot manager without having to leave the +installation utility. All planned installation methods are now also +supported. A trouble-shooting guide for those in, well, trouble may +also be of help and is featured on the boot floppy. + +

    +For more information on what's new with FreeBSD, or what general +features it offers, we strongly suggest that you simply download our +boot floppy and boot from it. You can easily read the release notes +on it using a simple menu, and with no danger to the contents of your +hard disk (unless you deliberately chose "proceed with installation", +in which case your fate is in your own hands! :-). + +

    +An upgrade path from ALPHA->RELEASE will also be provided shortly for +the benefit of those who were kind enough to help us test the early +snapshot of 2.0. Watch the announce list for its availability, or +simply be impatient and extract the 2.0R bindist over your ALPHA one! +:-) + +

    +Those wishing to obtain this version of 2.0 on CDROM should contact +our sponsors, Walnut Creek CDROM (info@cdrom.com) or any of the other +CD vendors who will, no doubt, be doing their own releases. + +

    +If you're currently running 1.x and are looking for an upgrade path, +we're sorry to say that only full installations are supported at this +time. Simply back up your password and user files before reinstalling +from the 2.0 media, then bring them back. If public demand is high +enough, and we can figure out a way of easily doing it, we'll offer +something, but it should be understood that the differences between +1.x and 2.0 are *large*, and it's not certain that we'll be able to do +it at all. + +

    +Those unable or unwilling to download the boot floppy may also get the +release notes by mail - send mail to <info@FreeBSD.org> for an +automated reply. Updated information will also be provided on a more +or less continuous basis in our WEB pages: + + http://www.freebsd.org + +

    +FreeBSD 2.0 RELEASE is or will be available for ftp in the following +locations: + +

      +
    • Primary ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE +
    • U.S-2 ftp://ftp.dataplex.net/pub/FreeBSD/2.0-RELEASE +
    • U.S-3 ftp://kryten.atinc.com/pub/FreeBSD/2.0-RELEASE +
    • U.S-4 ftp://ref.tfs.com/pub/FreeBSD/2.0-RELEASE +
    • Taiwan ftp://netbsd.csie.nctu.edu.tw/pub/FreeBSD/2.0-RELEASE +
    • Australia ftp://ftp.physics.usyd.edu.au/FreeBSD/2.0-RELEASE +
    • France ftp://ftp.ibp.fr/pub/freeBSD/2.0-RELEASE +
    • Finland ftp://nic.funet.fi:/pub/unix/FreeBSD/2.0-RELEASE +
    • Russia ftp://ftp.kiae.su/FreeBSD/2.0-RELEASE +
    + +

    +(Translated for the non-URL literate: FreeBSD is available for anonymous + ftp on ftp.freebsd.org in the pub/FreeBSD/2.0-RELEASE directory) + +

    +It will also, no doubt, be available on a number of mirror sites as +soon as they pick it up. However, ftp.freebsd.org is on a T3 line and +supports 300 simultaneous users (it's a FreeBSD machine :-), so it's +unlikely that you'll have too much trouble getting it from this site +until the mirrors do so. + +

    +If you are directly Internet connected, it is also NOT necessary to +load the bindist from this site! Simply download the 2 boot floppies, +begin the installation, and select the FTP installation method - it +will do the rest for you, transparently. + +

    +Finally, we'd like to publically *thank* Walnut Creek CDROM, without +whos continuing support and extreme generousity, we'd probably be long +gone! They've been of immense help to us. + +

    +Thanks must also go to Poul-Henning Kamp, our fearless and long +suffering release engineer for 2.0. While all of us have sacrificed +much sleep to the cause, he has a new wife but has somehow managed to +do so as well! :-) + +

    +And to all of our users (this is probably starting to sound like the +academy awards :-), a similar thank you! We couldn't have done it +without your constant flow of commentary, patches, donations of code +and moral support. As corny as it sounds, we do it all for you folks! +[Though the ego gratification is nice too :-)] + +

    +Thanks to all, and we sincerely hope you enjoy this release! + +

    +Comments, as always, to hackers@FreeBSD.org. + + +

    + Jordan
    + [on behalf of the FreeBSD Project team] + +&footer; + + diff --git a/data/releases/2.0/credits.sgml b/data/releases/2.0/credits.sgml new file mode 100644 index 0000000000..98c88724de --- /dev/null +++ b/data/releases/2.0/credits.sgml @@ -0,0 +1,210 @@ + + + + %includes; +]> + +&header; + +

    +			   FreeBSD 2.0
+		         Contributor List
+
+
+
+Derived Software Contributors:
+
+This software was originally derived from William F. Jolitz's 386BSD
+release 0.1, though almost none of the original 386BSD specific code
+remains.  This software has been essentially reimplemented on top of
+4.4 BSD Lite, from the Computer Science Research Group (CSRG) at
+the University of California, Berkeley and associated academic
+contributors.
+
+There are also portions of NetBSD that have been integrated into FreeBSD
+as well, and we would therefore like to thank all the contributors
+to NetBSD for their work.  Despite some occasionally rocky moments in
+the relations between the two groups, we both want essentially the same
+thing:  More BSD based operating systems on people's computers!  We
+wish the NetBSD group every success in their endevors.
+
+
+Hardware Contributors:
+
+A special thank-you to Walnut Creek CDROM for providing the 486/DX2-66 EISA/VL
+system that is being used for our development work, to say nothing of
+the network access and other donations of hardware resources.  It would have
+been impossible to do this release without their support.
+
+Thanks also to Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+drive.  It's been most useful!
+
+
+The FreeBSD Core Team (in alphabetical order):
+
+	Andreas Schulz <ats@g386bsd.first.bmd.de>
+	Andrew A. Chernov <ache@astral.msk.su>
+	Bruce Evans <bde@FreeBSD.org>
+	David Greenman <davidg@Root.COM>
+	Garrett A. Wollman <wollman@freefall.cdrom.com>
+	Gary Palmer <gpalmer@FreeBSD.org>
+	Geoff Rehmet <csgr@cs.ru.ac.za>
+	Jack Vogel <jackv@FreeBSD.org>
+	John Dyson <dyson@implode.rain.com>
+	Jordan K. Hubbard <jkh@FreeBSD.org>
+	Paul Richards <paul@isl.cf.ac.uk>
+	Poul-Henning Kamp <phk@FreeBSD.org>
+	Rich Murphey <rich@lamprey.utmb.edu>
+	Rodney W. Grimes <rgrimes@cdrom.com>
+	Soren Schmidt <sos@FreeBSD.org>
+
+
+Additional FreeBSD Contributors (no particular order):
+
+Adam Glass <glass@postgres.berkeley.edu>
+Andrew Herbert <andrew@werple.apana.org.au>
+Andrew Moore <alm@FreeBSD.org>
+Atsushi Murai <amurai@spec.co.jp>
+Bob Wilcox <bob@obiwan.uucp>
+Bruce Evans <bde@kralizec.zeta.org.au>
+Charles Hannum <mycroft@ai.mit.edu>
+Chris G. Demetriou <cgd@postgres.berkeley.edu>
+Chris Torek <torek@ee.lbl.gov>
+Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
+Curt Mayer <curt@toad.com>
+Dave Burgess <burgess@hrd769.brooks.af.mil>
+Dave Rivers <rivers@ponds.uucp>
+David Dawes <dawes@physics.su.OZ.AU>
+Frank Maclachlan <fpm@crash.cts.com>
+Gary A. Browning <gab10@griffcd.amdahl.com>
+Gary Clark II <gclarkii@radon.gbdata.com>
+Guido van Rooij <guido@gvr.win.tue.nl>
+Havard Eidnes <Havard.Eidnes@runit.sintef.no>
+Holger Veit <Holger.Veit@gmd.de>
+Ishii Masahiro, R. Kym Horsell
+J.T. Conklin <jtc@winsey.com>
+James Clark <jjc@jclark.com>
+James da Silva <jds@cs.umd.edu> et al
+Jim Wilson <wilson@moria.cygnus.com>
+Joerg Wunsch <joerg_wunsch@uriah.sax.de>
+Julian Elischer <julian@dialix.oz.au>
+Julian Stacey <stacey@guug.de> <fallback: <julian@meepmeep.pcs.com>>
+Keith Bostic <bostic@toe.CS.Berkeley.EDU>
+Keith Moore <?>
+Marc Frajola <marc@escargot.rain.com>
+Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
+Martin Birgmeier
+Paul Kranenburg <pk@cs.few.eur.nl>
+Paul Mackerras <paulus@cs.anu.edu.au>
+Poul-Henning Kamp <phk@login.dkuug.dk>
+Rob Shady <rls@id.net>
+Sascha Wildner <swildner@channelz.GUN.de>
+Scott Mace <smace@FreeBSD.org>
+Sean Eric Fagan <sef@kithrup.com>
+Serge V. Vakulenko <vak@zebub.msk.su>
+Steven Wallace <swallace@ece.uci.edu>
+Søren Schmidt <sos@login.dkuug.dk>
+Terry Lee <terry@uivlsi.csl.uiuc.edu>
+Theo Deraadt <deraadt@fsa.ca>
+Ugen J.S.Antsilevich <ugen@NetVision.net.il>
+Yuval Yarom <yval@cs.huji.ac.il>
+
+
+386BSD Patch kit patch contributors (no particular order):
+
+Adam Glass <glass@postgres.berkeley.edu>
+Adrian Hall <adrian@ibmpcug.co.uk>
+Andrew A. Chernov <ache@astral.msk.su>
+Andrew Herbert <andrew@werple.apana.org.au>
+Andrew Moore <alm@netcom.com>
+Andy Valencia <ajv@csd.mot.com> <jtk@netcom.com>
+Arne Henrik Juul <arnej@Lise.Unit.NO>
+Bakul Shah <bvs@bitblocks.com>
+Barry Lustig <barry@ictv.com>
+Bob Wilcox <bob@obiwan.uucp>
+Branko Lankester
+Brett Lymn <blymn@mulga.awadi.com.AU>
+Bruce Evans <bde@kralizec.zeta.org.au>
+Charles Hannum <mycroft@ai.mit.edu>
+Chris G. Demetriou <cgd@postgres.berkeley.edu>
+Chris Torek <torek@ee.lbl.gov>
+Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
+Daniel Poirot <poirot@aio.jsc.nasa.gov>
+Dave Burgess <burgess@hrd769.brooks.af.mil>
+Dave Rivers <rivers@ponds.uucp>
+David Dawes <dawes@physics.su.OZ.AU>
+David Greenman <davidg@Root.COM>
+Eric J. Haug <ejh@slustl.slu.edu>
+Felix Gaehtgens <felix@escape.vsse.in-berlin.de>
+Frank Maclachlan <fpm@crash.cts.com>
+Gary A. Browning <gab10@griffcd.amdahl.com>
+Geoff Rehmet <csgr@alpha.ru.ac.za>
+Goran Hammarback <goran@astro.uu.se>
+Guido van Rooij <guido@gvr.win.tue.nl>
+Guy Harris <guy@auspex.com>
+Havard Eidnes <Havard.Eidnes@runit.sintef.no>
+Herb Peyerl <hpeyerl@novatel.cuc.ab.ca
+Holger Veit <Holger.Veit@gmd.de>
+Ishii Masahiro, R. Kym Horsell
+J.T. Conklin <jtc@winsey.com>
+Jagane D Sundar < jagane@netcom.com >
+James Clark <jjc@jclark.com>
+James Jegers <jimj@miller.cs.uwm.edu>
+James W. Dolter
+James da Silva <jds@cs.umd.edu> et al
+Jay Fenlason <hack@datacube.com>
+Jim Wilson <wilson@moria.cygnus.com>
+Joerg Lohse <lohse@tech7.informatik.uni-hamburg.de>
+Joerg Wunsch <joerg_wunsch@uriah.sax.de>
+John Dyson - <formerly dyson@ref.tfs.com>
+John Woods <jfw@eddie.mit.edu>
+Jordan K. Hubbard <jkh@whisker.hubbard.ie>
+Julian Elischer <julian@dialix.oz.au>
+Julian Stacey <stacey@guug.de> <fallback: <julian@meepmeep.pcs.com>>
+Karl Lehenbauer <karl@NeoSoft.com> <karl@one.neosoft.com>
+Keith Bostic <bostic@toe.CS.Berkeley.EDU>
+Ken Hughes
+Kent Talarico <kent@shipwreck.tsoft.net>
+Kevin Lahey <kml%rokkaku.UUCP@mathcs.emory.edu> <kml@mosquito.cis.ufl.edu>
+Marc Frajola <marc@escargot.rain.com>
+Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
+Martin Renters <martin@innovus.com>
+Michael Galassi <nerd@percival.rain.com>
+Mike Durkin <mdurkin@tsoft.sf-bay.org>
+Nate Williams <nate@bsd.coe.montana.edu>
+Nick Handel <nhandel@NeoSoft.com> <nick@madhouse.neosoft.com>
+Pace Willisson <pace@blitz.com>
+Paul Kranenburg <pk@cs.few.eur.nl>
+Paul Mackerras <paulus@cs.anu.edu.au>
+Paul Popelka <paulp@uts.amdahl.com>
+Peter da Silva <peter@NeoSoft.com>
+Phil Sutherland <philsuth@mycroft.dialix.oz.au>
+Poul-Henning Kamp <phk@login.dkuug.dk>
+Ralf Friedl <friedl@informatik.uni-kl.de>
+Rich Murphey <rich@lamprey.utmb.edu>
+Rick Macklem <root@snowhite.cis.uoguelph.ca>
+Robert D. Thrush <rd@phoenix.aii.com>
+Rodney W. Grimes <rgrimes@cdrom.com>
+Rog Egge <?>
+Sascha Wildner <swildner@channelz.GUN.de>
+Scott Burris <scott@pita.cns.ucla.edu>
+Scott Reynolds <scott@clmqt.marquette.mi.us>
+Sean Eric Fagan <sef@kithrup.com>
+Simon J Gerraty <sjg@melb.bull.oz.au> <sjg@zen.void.oz.au>
+Stephen McKay <robert@psych.psy.uq.oz.au>
+Terry Lambert <terry@icarus.weber.edu>
+Terry Lee <terry@uivlsi.csl.uiuc.edu>
+Warren Toomey <wkt@csadfa.cs.adfa.oz.au>
+Wiljo Heinen <wiljo@freeside.ki.open.de>
+William Jolitz <withheld>
+Wolfgang Solfrank <ws@tools.de>
+Wolfgang Stanglmeier <wolf@dentaro.GUN.de>
+Yuval Yarom <yval@cs.huji.ac.il>
+
+Id: CONTRIB.FreeBSD,v 1.1 1994/11/18 12:03:25 jkh Exp
+
    + +&footer; + + diff --git a/data/releases/2.0/install.sgml b/data/releases/2.0/install.sgml new file mode 100644 index 0000000000..a0672eccb9 --- /dev/null +++ b/data/releases/2.0/install.sgml @@ -0,0 +1,493 @@ + + + + %includes; +]> + +&header; + +
    +Welcome to FreeBSD 2.0, the complete 4.4 BSD Lite based OS for Intel (or
+compatible) based PCs.
+
+There are several documents on the floppy and a couple of on-line help
+screens that will greatly assist you in installing your system as you go
+along.  Nonetheless, initial user testing has shown that some of the
+terminology used may be difficult for newcomers to UN*X to understand, so
+we've prepared this step-by-step guide explaining a typical installation.
+You may find it useful to print this out and keep it handy as you go
+through the installation, or at least read through it once carefully so
+that some of the prompts and questions you encounter do not come as
+complete surprises.
+
+Before you do anything, make two 1.44MB floppies from the two image files
+you'll find in the floppies/ directory - boot.flp and cpio.flp.  If you're
+reading this under DOS, you can do it in 1 easy step, or 3 in case this
+doesn't (for some weird reason) work:
+
+1. If you're reading this file after typing "go", simply ESC back out for
+   a moment and select the "makeflp" batch file to make the two floppies.
+   This will invoke the DOS formatter to format the floppies and then
+   attempt to write the two disk images onto them.  If this doesn't work,
+   follow steps 2 through 4:
+
+2. Use the DOS format command to format 2 NEW floppies.  A lot of problems
+   have been caused by people using old and defective floppies, and much
+   grief can often be saved by simply using new, or at least trusted,
+   media.
+
+3. Insert the first floppy and type:
+
+		tools\dos-tool\rawrite floppies\boot.flp a:
+
+4. Insert the second floppy and type
+
+		tools\dos-tool\rawrite floppies\cpio.flp a:
+
+You're now prepared to boot from the boot floppy and begin the installation.
+
+
+The installation starts with the following screen:
+
+  +-------------------------- Welcome to FreeBSD! ---------------------------+
+  | Use ALT-F2 and ALT-F1 to toggle between debugging                        |
+  | information screen (ALT-F2) or this dialog screen (ALT-F1)               |
+  |                                                                          |
+  | Please select one of the following options:                              |
+  | +----------------------------------------------------------------------+ |
+  | | 1. README               READ THIS FIRST.                             | |
+  | | 2. Release Notes        Read the 2.0 Release Notes (recommended).    | |
+  | | 3. Troubleshooting      Read this in case of trouble.                | |
+  | | 4. Partitions and MBRs  Verbose description of how these work.       | |
+  | | 5. COPYRIGHT            Read FreeBSD Copyright Information.          | |
+  | | 6. Install              Proceed with full installation.              | |
+  | | 7. Fixit                Repair existing installation (`fixit' mode). | |
+  | | 8. Quit                 Don't do anything, just reboot.              | |
+  | +----------------------------------------------------------------------+ |
+  +--------------------------------------------------------------------------+
+  |                          <  OK  >      <Cancel>                          |
+  +--------------------------------------------------------------------------+
+
+
+You can move the arrow keys up and down to highlight the various options,
+selecting an option by hitting return when its line is highlighted.  You
+can also type the number of the option you want (1 - 7) and hit return.
+It's recommended that you read the README at a minimum, though the Release
+Notes are also helpful.  This may seem a like a lot to read, but if you are
+new to FreeBSD then these notes are invaluable for explaining the system
+and are highly recommended.
+
+When you're done reading docs, select Install (5) to proceed to the next
+screen.
+
+This next screen is the disk editor screen, which looks like this:
+
+------------------------------------------------------------------------------
+FreeBSD 2.0-RELEASE Installation -- Diskspace editor
+
+Disks         Total   FreeBSD                    |You should now assign some
+                                                 |space to root, swap, and
+ 0: sd0     2006 MB      0 MB                    |(optionally) /usr partitions
+ 1: sd1      496 MB      0 MB                    |Root (/) should be a minimum
+                                                 |of 18MB with a 30MB /usr
+Filesystems  Type        Size  Action Mountpoint |or 50MB without a /usr.
+                                                 |Swap space should be a
+                                                 |minimum of 12MB or RAM * 2
+                                                 |Be sure to also (A)ssign a
+                                                 |mount point to each one or
+                                                 |it will NOT be enabled.
+                                                 |
+                                                 |We suggest that you invoke
+                                                 |(F)disk, (W)rite the bootcode
+                                                 |then (D)isklabel your disk.
+                                                 |If installing on a drive
+                                                 |other than 0, also read the
+                                                 |TROUBLESHOOTING doc first
+Commands available:
+(H)elp  (T)utorial  (F)disk  (D)isklabel  (P)roceed  (Q)uit
+
+Enter Command>
+
+------------------------------------------------------------------------------
+
+As we can see, this system has two drives, sd0 and sd1.  On an IDE system,
+these would show up as "wd0" and "wd1" (or, on a single drive system, just
+sd0 or wd0).  We can see that neither of them has any space assigned to
+FreeBSD (they each show 0MB under the FreeBSD column), so we follow the
+instructions on the right hand side of the screen and invoke the (F)disk
+editor by typing `f':
+
+Enter Command> F
+
+We're now prompted with the drive number to (F)disk, so we enter 0 for
+the first drive:
+
+Enter number of disk to Fdisk> 0
+
+This now brings us to the FDISK editor screen, which looks like this:
+
+------------------------------------------------------------------------------
+FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- FDISK
+
+Disk: sd0   Geometry:  2006 Cyl * 32 Hd * 64 Sect = 2006Mb = 4108600 Sect
+
+1 Boot?=No    Type=Primary 'big' DOS (> 32MB)
+  Phys=(c0/h1/s1..c299/h63/s32)   Sector=(32..614399)
+  Size=300 MB, 299 Cylinders + 31 Tracks + 32 Sectors
+
+2 Unused
+
+
+3 Unused
+
+
+4 Unused
+
+
+Commands available:
+(H)elp   (T)utorial   (D)elete   (E)dit   (R)eread   (W)rite MBR   (Q)uit
+(U)se entire disk for FreeBSD   (G)eometry   Write MBR (B)ootcode
+Enter Command>
+
+------------------------------------------------------------------------------
+
+We see that drive 0 has a DOS partition (also called a "slice" in FreeBSD
+parlance, to distinguish it from a FreeBSD partition) on it which is 300MB
+in size (don't worry if the numbers you see are much smaller than these - I
+have a pretty large 2.1GB disk! :-).  Let's also say we want to allocate
+the rest to FreeBSD, so to do this we want to (E)dit one of the existing
+slices.  We can see that 2, 3, and 4 are unused so let's pick the first
+unused one, which is 2 (if we wanted to replace an existing operating
+system slice with FreeBSD, we'd pick its number instead).  We first type
+`E' to edit a slice entry:
+
+Enter Command> E
+
+And we're prompted for a slice to edit.  We type 2:
+
+Edit which Slice> 2
+
+Now we're prompted for the size of the new slice, the default for which is
+all remaining space on the disk.  Let's say that we don't want to allocate
+ALL the space on the disk, but want to reserve 400MB for some other future
+OS.  The total amount of free space left is 1706MB, which is the default
+value selected for us, so we backspace over it and enter 1306:
+
+Size of slice in MB> 1306
+
+Now we're asked for the type of the slice.  The type is what tells the PC
+what sort of slice this is.  DOS primary slices are, for example, type 6.
+FreeBSD slices are type 0xa5 (hexadecimal).  If we wanted to reserve space
+at this time for some other type of OS like Linux or OS/2, and we knew
+their slice type (0x82 for Linux and 0x0A for OS/2, just in case you're
+interested), we could also do that from this editor, but we're only
+interested in FreeBSD for now so we accept the default.
+
+Type of slice (0xa5=FreeBSD)> 0xa5
+
+The next prompt asks if we want to make this slice bootable by
+default, which we do so we accept the default:
+
+Bootflag (0x80 for YES)> 0x80
+
+At this point we come back to the main screen, which now shows a new entry
+for slice 2:
+
+------------------------------------------------------------------------------
+FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- FDISK
+
+Disk: sd0   Geometry:  2006 Cyl * 32 Hd * 64 Sect = 2006Mb = 4108600 Sect
+
+1 Boot?=No    Type=Primary 'big' DOS (> 32MB)
+  Phys=(c0/h1/s1..c299/h63/s32)   Sector=(32..614399)
+  Size=300 MB, 299 Cylinders + 31 Tracks + 32 Sectors
+
+2 Boot?=Yes   Type=FreeBSD/NetBSD/386BSD
+  Phys=(c300/h0/s1..c1023/h31/s0)   Sector=(614400..3289087)
+  Size=1306 MB, 1306 Cylinders
+
+3 Unused
+
+
+
+4 Unused
+
+
+
+Commands available:
+(H)elp   (T)utorial   (D)elete   (E)dit   (R)eread   (W)rite MBR   (Q)uit
+(U)se entire disk for FreeBSD   (G)eometry   Write MBR (B)ootcode
+Enter Command>
+
+------------------------------------------------------------------------------
+
+At this point we're happy with the slices on the first drive, so we type
+`w' to write the new information out.  It also prompts to make *sure* we
+really want to do this, so we backspace over the default of `N' and type
+`y'<return>.  And this point, we also can decide whether or not we want a
+"boot manager" installed.  A boot manager is a little utility that prompts
+you for the operating system you want to boot every time you reset or power
+on your PC, and can be a very handy way of sharing your computer between
+FreeBSD and some other OS, like Linux or DOS.  We decide that we want to
+have this feature, so we `b' to write the special MBR (B)ootcode out to the
+disk.  This does not harm any of the other operating systems on the disk,
+as it's written to a special area.  Now we exit this screen by typing `q',
+for (Q)uit.
+
+This brings us back to the main prompt.  If we wanted to allocate any
+additional slices on other drives, we also could re-invoke the (F)disk
+editor by typing `f' again and giving a different drive number at the
+prompt, but we'll assume for now that we've only got one disk and want to
+go on.  Typing `d' now enters the (D)isklabel screen, which prompts us for
+the drive to write a disklabel onto, like the FDISK editor.  We type `0'
+for the first drive and hit return.  This brings us to the DISKLABEL editor
+screen, which looks like this:
+
+------------------------------------------------------------------------------
+FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- DISKLABEL
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a         0         0         0      0  unused
+b         0         0         0      0  unused
+c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
+d         0   4108599   4108600   2006  unused          <Entire Disk>
+e         0         0         0      0  unused
+f         0         0         0      0  unused
+g         0         0         0      0  unused
+h        32    614399    614368    300  MSDOS
+
+
+
+
+
+
+Total size:       2674688 blocks   1306Mb
+Space allocated:        0 blocks      0Mb
+
+Commands available:
+(H)elp  (T)utorial  (E)dit  (A)ssign  (D)elete  (R)eread  (W)rite  (Q)uit
+(P)reserve  (S)lice
+Enter Command>
+
+------------------------------------------------------------------------------
+
+The BSD partitions, a - h, are FreeBSD's way of dividing up a physical
+slice into multiple file systems.  Every FreeBSD system should have, at
+minimum, a root file system and a swap partition allocated.  The root
+file system is called "/", and is generally put on partition `a' by
+convention.  Swap partitions always go on `b', and the `c' and `d'
+partitions are special and point to the entire FreeBSD slice and the entire
+disk, respectively.  `c' and `d' cannot and should not be allocated to
+actual file systems.
+
+We also see that partition h points conveniently to the DOS slice,
+which we can also assign to a location in our file system hierarchy
+to conveniently share files between FreeBSD and DOS.  More on this in 
+a moment.
+
+A typical file system layout might look like this:
+
+/	20MB
+swap	32MB
+/usr	120MB
+
+/, or the root file system, contains system files and some temporary space.
+It should be at least 18MB in size, though a little extra doesn't hurt.
+Swap space is one of those "it never hurts to have too much" sorts of
+items, though if your system isn't too heavily used then it's probably not
+that important to have lots and lots of it.  A good rule of thumb for swap
+is that you want a minimum of 12MB of it, and the overall calculation
+should be the amount of memory you have multiplied by two.  That is to
+say that if you have 16MB of memory, then 32MB of swap is good.
+
+If you've got several drives, you can also allocate some swap on each one
+and spread the load out a little.  On my personal system, I've got 32MB of
+main memory and 64MB of swap on both drives for a total of 128MB of swap.
+This gives me 4X memory for total program swapping, which gives me the
+ability to run some pretty big programs!  Emacs and the X Window System, in
+particular, can be real swap hogs.
+
+In any case, we'll assume for the moment that we're still configuring the
+ideal system and we'll allocate 64MB of swap space, using the MEM * 2
+equation.  If you only had 8MB of memory, you'd allocate 16MB of swap
+instead.
+
+The second file system of importance is /usr, which contains further system
+binaries and all of the bundled user binaries.  /usr should be at least
+80MB in size to hold all of the important binaries, though if you plan on
+having a big /usr/local or on loading the X Window System (also known as
+XFree86 3.1) distribution then you should either create separate
+file systems for them, or you should make /usr a lot bigger.
+
+It's also possible to skip making /usr altogether and simply make a large
+root (/) file system.  Since /usr fits "underneath" /, a missing /usr won't
+cause any problems if / is large enough to hold the contents for both.  In
+any case, it's a user decision and tends to be driven by convention more
+than anything else.  For the purposes of this installation guide, we'll
+assume a 200MB /usr, 100MB of space allocated for local binaries, which
+we'll mount on /usr/local, and the rest for user home directories, which
+we'll mount on /usr/users.  Don't be put off by the size of these numbers!
+You can make a system fit into less space, but since we're dividing up the
+ideal 2GB dream disk, we might as well do it right! ;-)
+
+Getting back to the relevant part of the DISKLABEL screen again, we remember
+that it looked like this:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a         0         0         0      0  unused
+b         0         0         0      0  unused
+c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
+d         0   4108599   4108600   2006  unused          <Entire Disk>
+e         0         0         0      0  unused
+f         0         0         0      0  unused
+g         0         0         0      0  unused
+h        32    614399    614368    300  MSDOS
+
+So we'll first allocate some space on partition `a' for that root partition
+by typing `e', for (E)dit partition.  This asks us which partition we want
+to change the size of, so we type `a':
+
+Change size of which partition> a
+
+And it prompts us for the amount of space, so we'll pick 20MB for a nice
+comfortable root file system:
+
+Size of partition in MB> 20
+
+Now we see the display change to:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a   1433600   1474559     40960     20  4.2BSD
+...
+
+The system shows us where the partition starts and stops and indicates that
+it's a 4.2BSD file system, which is correct (it's really a 4.4 BSD file
+system, in actuality, but the two are similar enough to share the same
+label).
+
+We do the same for swap by typing `e' again and modify the `b' partition
+by filling in 64 for the size, to allocate 64MB of swap.
+
+Finally, remembering that `c' and `d' are special, and not for our use, we
+change the size of `e' to 200 for our future /usr, `f' to 100 for our
+/usr/local, and `g' to the rest of the disk for /usr/users.  When we're
+done, the top of the disklabel screen should look like this:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a   1433600   1474559     40960     20  4.2BSD
+b   1474560   1605631    131072     64  swap
+c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
+d         0   4108599   4108600   2006  unused          <Entire Disk>
+e   1605632   2015231    409600    200  4.2BSD
+f   2015232   2220031    204800    100  4.2BSD
+g   2220032   4108287   1888256    922  4.2BSD
+h        32    614399    614368    300  MSDOS
+
+We left `h' alone, since we actually want to be able to share files with
+our DOS partition.  At this point, we want to type `w' for (W)rite to write
+out the new size information to disk.
+
+You probably also noticed by now that "/", "/usr" and the other file system
+names we've been talking about don't appear anywhere in the above list.
+Where are they?  This brings us to the next stage, which is to (A)ssign the
+new partitions to actual file system mount points.  A file system in
+FreeBSD doesn't actually appear anywhere until we "mount" it someplace, a
+convention from the old days when disks were actually large removable packs
+that a system operator physically mounted on a large washing-machine sized
+disk drive spindle!  As you can see, not much has changed today! :-)
+
+We'll proceed then by starting at the top with the first partition and
+assigning it to the root file system (/) by typing `a', for (A)ssign, and
+then typing `a' again, for partition a:
+
+Assign which partition> a
+
+When it asks us for the name of the mount point, we type /:
+
+Directory mountpoint> /
+
+And the display adjusts accordingly to show us the new state of affairs:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a   1433600   1474559     40960     20  4.2BSD  newfs   /
+..
+
+The Action field also now shows "newfs", which means that the partition
+will be created anew.  For root file systems, this is the default and cannot
+be changed, but other partitions can be optionally "Preserved" by typing
+`p' for (P)reserve.  There are very few situations in which we'd want to do
+this, but if, say, we were actually installing a disk from an older FreeBSD
+machine which we wanted to mount into our new system but NOT erase, we
+could do it this way.  For now, let's assume that this is a new
+installation and we want all the file systems to be created from scratch.
+We thus go through and assign the rest of the file systems to their
+respective /usr, /usr/local and /usr/users mountpoints.  We also assign the
+`b' partition, which doesn't take a mountpoint (and won't prompt for one
+when we (A)ssign it), but needs us to tell it that we're ready to use it
+for swap.
+
+When we're done, the top of the screen should look something like this:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a   1433600   1474559     40960     20  4.2BSD  newfs   /
+b   1474560   1605631    131072     64  swap    swap    swap
+c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
+d         0   4108599   4108600   2006  unused          <Entire Disk>
+e   1605632   2015231    409600    200  4.2BSD  newfs   /usr
+f   2015232   2220031    204800    100  4.2BSD  newfs	/usr/local
+g   2220032   4108287   1888256    922  4.2BSD  newfs	/usr/users
+h        32    614399    614368    300  MSDOS
+
+As a final bonus, we'll assign the DOS partition to be mounted on /dos.  We
+do this with (A)ssign as we did the others, and we also notice that the
+system is smart enough to see that it's not a FreeBSD partition and we
+DON'T want to newfs it, we want to simply mount it:
+
+h        32    614399    614368    300  MSDOS   mount   /dos
+
+At this point, our system is all set up and ready to go!
+
+We type `q' to go back to the main menu and then type `p' to (P)roceed to
+the next phase of installation.
+
+We're now given one last chance to back out of the install, and we hit
+return if we're sure, otherwise we type <Tab> to select "No" and hit return
+to consider our settings again before going on.
+
+The rest of the installation is pretty much self-explanatory.  After the
+file systems are initially created and populated, you'll be prompted to
+reboot from the hard disk.  Do so and provide the cpio floppy when asked.
+
+When the initial flurry of welcome and informational prompts has died down,
+you'll come to a screen asking you to load one or more distributions.  At
+the minimum, select "bindist" to load the basic system.  If you're loading
+from other than CDROM media, follow the appropriate paths through the
+installation process.
+
+If you're loading from CDROM, select CDROM as the media type and select the
+type of CDROM you've got (SCSI or Mitsumi).  When it asks you for an
+installation subdirectory, simply hit return if you've got the 2.0 CD from
+Walnut Creek CDROM.  You may select additional optional packages to load
+after the bindist extracts, provided that you've got the space for it.  Use
+the "?diskfree" menu option from time to time to keep an eye on your free
+space.  When you're done, you'll be asked a few more basic questions and
+then that's it!  You've got FreeBSD on your hard disk.
+
+If you should need to partition another drive or install other packages
+later, you may re-invoke the sysinstall program by typing /sbin/sysinstall.
+The same familiar prompts will then come up.
+
+Good luck!
+
+					Jordan Hubbard
+					for Walnut Creek CDROM
+					and the FreeBSD Project.
+
+
+
+
    + +&footer; + + diff --git a/data/releases/2.0/notes.sgml b/data/releases/2.0/notes.sgml new file mode 100644 index 0000000000..c9fb2a36e5 --- /dev/null +++ b/data/releases/2.0/notes.sgml @@ -0,0 +1,641 @@ + + + + %includes; +]> + +&header; + +
    +
+                                 RELEASE NOTES
+                                    FreeBSD
+                                  Release 2.0
+
+1. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD
+has changed almost entirely.  A new port from the Berkeley 4.4 code
+base was done, which brought the legal status of the system out of the
+shadows with the blessing of Novell (new owners of USL and UNIX).  The
+port to 4.4 has also brought in a host of new features, filesystems
+and enhanced driver support.  With our new unencumbered code base, we
+have every reason to hope that we'll be able to release quality
+operating systems without further legal encumbrance for some time to
+come!
+
+FreeBSD 2.0 represents the culmination of almost 2 years of work and
+many thousands of man hours put in by an international development team.
+We hope you enjoy it!
+
+Many packages have also been upgraded or added, such as XFree86 3.1,
+xview 3.2, elm, nntp, mh, InterViews and dozens of other miscellaneous
+utilities have been ported and are now available as add-ons.  See the
+ports collection (or the package collection) for a complete summary.
+
+For a list of contributors, please see the file "CONTRIB.FreeBSD",
+which should be bundled with your bindist distribution.
+
+Also see the new "REGISTER.FreeBSD" file for information on registering
+with the "Free BSD user counter".  We've also provided a list of who's
+responsible for what (so that you may query them directly) in the
+"ROSTER.FreeBSD" file; use of this file is encouraged to ensure faster
+resolution of any problems you may have!
+
+The core of FreeBSD does not contain DES code which would inhibit its
+being exported outside the United States.  There is an add-on package
+to the core distribution, for use only in the United States, that
+contains the programs that normally use DES.  The auxilliary packages
+provided separately can be used by anyone.   A freely (from outside the
+U.S.) exportable European distribution of DES for our non U.S. users also
+exists and is described in the FreeBSD FAQ.
+
+If password security for FreeBSD is all you need, and you have no
+requirement for copying encrypted passwords from different hosts (Suns,
+DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5
+based security may be all you require!  We feel that our default security
+model is more than a match for DES, and without any messy export issues
+to deal with.  If you're outside (or even inside) the U.S., give it a try!
+
+
+1.1 What's new in 2.0?
+----------------------
+
+4.4 Lite
+--------
+As previously stated, this release is based entirely on CSRG's
+latest (and last) BSD release - 4.4 Lite.  This features a number
+of improvements over 4.2BSD (Net/2), not least of which are:
+
+o       Legal approval of Novell & U.C. Berkeley.  After the settlement
+        of the longstanding lawsuit between USL/UCB/Novell/BSDI, all
+        parties were (strongly) encouraged to move to 4.4 Lite in order
+        to avoid future legal entanglements.  The fact that we've now done
+        so should make this release much more attractive to potential
+        commercial users.
+
+o       Many new filesystem types, such as stackable filesystems, union
+        filesystems, "portals", kernfs, a simple log-structured filesystem, a
+        new version of NFS (NQNFS), etc.  While some of these new filesystems
+        are also rather unpolished and will require significant additional
+        work to be truly robust, they're a good start.
+
+o       64bit offsets, allowing filesystems of up to 2^63 bytes in size.
+
+o       Further work towards full POSIX compliance.
+
+IP multicast support
+--------------------
+The IP multicast support has been upgraded from the woefully ancient
+1.x code in 4.4-Lite to the most current and up-to-date 3.3 release
+from Steve D. and Ajit.  The non-forwarding code is known to work (for
+some limited test cases).  The multicast forwarder and user-mode
+multicast routing process are known to compile, but have not been
+significantly tested (hopefully this will happen before 2.0 release).
+
+Owner:                  wollman
+Sources involved:       sys/netinet, usr.sbin/mrouted
+
+Loadable Kernel Modules
+-----------------------
+David Greenman incorporated NetBSD's port of Terry Lambert's loadable
+kernel module support.  Garrett Wollman wrote the support for loadable
+file systems, and Søren Schmidt did the same for loadable execution
+classes.
+
+Owner:                  core
+Sources involved:       sys/kern, sbin/modload, sbin/modunload,
+                        usr.bin/modstat
+
+
+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 getvfsbyname(3)
+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
+the following current restrictions:
+
+        - /usr/bin may not reside on a dynamically loaded filesystem.
+        - There must be a writable /tmp directory available
+          before filesystems are loaded (moving / to the top of your
+          /etc/fstab file will accomplish this).
+        - Some of the more esoteric filesystems simply don't work when loaded
+          dynamically (though they often don't work "static", either.)
+
+Owner:                  wollman
+Sources involved:       sys/*fs, lkm/*fs, usr.bin/lsvfs, lib/libc/gen
+
+
+S/Key
+-----
+Since version 1.1.5, FreeBSD has supported the S/Key one time password
+scheme.  The version used is derived from the logdaemon package of Wietse
+Venema.
+Some of the features new in 2.0 are:
+        - New access control table format to impose the use of S/Keys
+          based on: hostname, ip address, port, username, group id.
+        - S/Key support can be disabled by not having the access control
+          table.
+The second item explains the absence of skey.access in the installed /etc.
+To enable S/Key support, create a file skey.access in /etc and fill it
+according to your needs. See also skey.access(5) and the example in
+/usr/share/examples/etc/skey.access.
+
+Owner:                  pst, guido
+Sources involved:       lib/libskey, usr.bin/key* (plus patches to others)
+
+
+TCP/IP over parallel (printer) port
+-----------------------------------
+You can now run TCP/IP over a standard LapLink(tm) cable, if both ends
+have an interrupt-driven printerport.  The interface is named "lp0"
+where '0' is the same as the lpt# unit number.  This is not compatible
+with PLIP.  If you run NFS, try setting MTU to 9180, otherwise leave
+it at 1500 unless you have a good reason to change it.  Speed varies
+with the CPU-type, with up to 70 kbyte/sec having been seen and 50
+kbyte/sec being the norm.
+
+Owner:                  phk
+Sources involved:       isa/lpt.c
+
+
+ProAudioSpectrum SCSI driver
+----------------------------
+If you have a PAS board with a CD-ROM, and the MS-DOS driver is called
+TSLCDR.SYS, then the "pas" driver should work on your card.  You can
+attach disks, cdroms and tapes, but due to the nature of the hardware
+involved, the transfer rate is limited to < 690 kbyte/sec.  For CD-ROM
+use, this is generally more than enough.
+
+Owner:                  phk
+Sources involved:       isa/pas.c
+
+
+Adaptec 2742/2842 SCSI driver
+-----------------------------
+Despite the non-cooperation of Adaptec in providing technical
+information, we now have a driver for the AHA-274x and AHA-284x
+series SCSI controller family.  This driver uses the GPL'd
+Linux sequencer code, so until we find an alternative, this
+will be part of the kernel that requires source code to be
+distributed with it at all times.  This shouldn't be a problem
+for any of FreeBSD's current users.
+
+Owner:                  gibbs
+Sources involved:       isa/aic7770.c sys/gnu/misc/*
+
+
+Gzip'd binaries
+----------------
+We have an experimental implementation for direct execution of gzip'ed
+binaries in this release.  When enabled, it allows you to simply gzip
+your binaries, remove the '.gz' extension and make the file
+executable.  There is a big speed and memory consumption penalty for
+doing this, but for laptop users it may be worthwhile.  The maximum
+savings are generally around 10 Mb of disk space.
+
+Owner:                  phk
+Sources involved:       kern/imgact_gzip.c kern/inflate.c
+
+
+Diskless booting
+----------------
+
+Diskless booting in 2.0 is much improved since 1.1.5.  The
+boot-program is in src/sys/i386/boot/netboot, and can be run from an
+MSDOS system or burned into an EPROM.  Local swapping is also
+possible.  WD, SMC, 3COM and Novell ethernet cards are currently
+supported.
+
+Owner:                  Martin Renters & phk
+Sources involved:       i386/boot/netboot, sys/nfs/nfs_vfsops.h
+
+
+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 sysctl(3) management interface.  Current
+applications include lsdev(8), which lists the currently configured
+devices.  In the future, we expect to use this code to automatically
+generate a configuration file for you at installation time.
+
+Owner:                  wollman
+Sources involved:       sys/i386, sys/scsi, sys/kern/kern_devconf.c,
+                        sys/sys/devconf.h, usr.sbin/lsdev
+
+
+Kernel management interface
+---------------------------
+With 4.4-Lite, we now have a better management interface for the endless
+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 sysctl(1) program.  In addition to the standard 4.4BSD MIB variables,
+we have added support for YP/NIS domains (kern.domainname), controlling
+the update daemon (kern.update), retrieving the OS release date
+(kern.osreldate), determining the name of the booted kernel (kern.bootfile),
+and checking for hardware floating-point support (hw.floatingpoint).
+We have also added support to make management queries of devices and
+filesystems.
+
+Owner:                  core
+Sources involved:       sys, usr.bin/sysctl
+
+
+iBCS2 support
+-------------
+FreeBSD now supports running iBCS2 compatible binaries (currently
+SCO UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).
+The iBCS2 emulator is in its early stages, but it is functional, we
+haven't been able to do exhaustive testing (lack of commercial apps),
+but almost all of SCO's 3.2.2 binaries are working, so is an old
+INFORMIX-2.10 for SCO. Further testing is nessesary to complete this
+project. There is also work under way for ELF & XOUT loaders, and
+most of the svr4 syscall wrappers have been written.
+
+Owner:                  Soren Schmidt (sos) & Sean Eric Fagan (sef)
+Sources involved:       sys/i386/ibcs2/* + misc kernel changes.
+
+
+2. Supported Configurations
+---------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+Following is a list of all currently known disk controllers and
+ethernet cards known to work with FreeBSD.  Other configurations may
+very well work, and we have simply not received any indication of
+this.
+
+
+2.1. Disk Controllers
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+[Note: the new Extended IDE controllers in newer PC's work, although no
+extended features are used.]
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 2742/2842 series ISA/EISA SCSI controllers
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the Soundblaster cards
+as they have no on-board BIOS, which is necessary for mapping
+the boot device into the system BIOS I/O vectors.
+They're perfectly usable for external tapes, CDROMs, etc,
+however.  The same goes for any other AIC-6x60 based card
+without a boot ROM.  Some systems DO have a boot ROM, which
+is generally indicated by some sort of message when the system
+is first powered up or reset.  Check your system/board documentation
+for more details.
+
+[Note that Buslogic was formerly known as "Bustec"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+
+NCR 53C810 and 53C825 PCI SCSI controller.
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+DAT) and CD ROM drives.  Note: This and the mcd driver (Mitsumi CDROM
+interface card) are the only way a CD ROM drive may be currently
+attached to a FreeBSD system; we do not support SoundBlaster
+(non-SCSI) CDROM interface, or other "non-SCSI" adapters.  The
+ProAudio Spectrum SCSI and SoundBlaster SCSI controllers are
+supported.
+
+Some controllers have limitations with the way they deal with >16MB of
+memory, due to the fact that the ISA bus only has a DMA address space of
+24 bits.  If you do your arithmetic, you'll see that this makes it
+impossible to do direct DMA to any address >16MB.  This limitation is
+even true of some EISA controllers (which are normally 32 bit) when
+they're configured to emulate an ISA card, which they then do in *all*
+respects.  This problem is avoided entirely by IDE controllers (which do
+not use DMA), true EISA controllers (like the UltraStor or Adaptec
+1742A) and most VLB (local bus) controllers.  In the cases where it's
+necessary, the system will use "bounce buffers" to talk to the
+controller so that you can still use more than 16Mb of memory without
+difficulty.
+
+
+2.2. Ethernet cards
+
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509 and 3C579 Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+2.3. Misc
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+STB 4 port card using shared IRQ.
+
+Mitsumi (all models) CDROM interface and drive.
+
+Soundblaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
+
+Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
+support is apparently close to materializing.  Details will be posted
+as the situation develops.
+
+
+3. Obtaining FreeBSD.
+---------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+1. FTP/Mail
+
+You can ftp FreeBSD and any or all of its optional packages from
+`freebsd.cdrom.com' - the offical FreeBSD release site.
+
+For other locations that mirror the FreeBSD software see the file
+MIRROR.SITES.  Please ftp the distribution from the nearest site
+to you netwise.
+
+If you do not have access to the internet and electronic mail is your
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
+to get more information on how to fetch files from freebsd.cdrom.com.
+Note: This approach will end up sending many *tens of megabytes*
+through the mail, and should only be employed as an absolute LAST
+resort!
+
+
+2. CDROM
+
+FreeBSD 2.0 may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
+
+Or via the internet from orders@cdrom.com.  Their current catalog can
+be obtained via ftp as ftp.cdrom.com:/cdrom/catalog.
+
+Cost is $39.95.  Shipping (per order not per disc) is $5 in the US, Canada,
+or Mexico and $10.00 overseas.  They accept Visa, Mastercard, American
+Express, and ship COD to the United States.  California residents please
+add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD,
+you need to contact the FreeBSD team for that.  Please see section 5 for
+more information.
+
+
+4. Preparing for the installation.
+----------------------------------
+
+1. Floppy Installation
+
+If you must install from floppy disks, either due to space contraints
+on your hard disk or just because you enjoy doing things the hard
+way, you must first prepare some floppies for the install.
+
+You will need either 10 1.44MB floppies or 12 1.2MB floppies to
+store just the bindist (binary distribution).  These *must* be
+formatted using MS-DOS, using either the FORMAT command in MS-DOS
+or the File Manager in Microsoft Windows to prepare the floppies
+(though factory preformatted floppies will also well well, provided
+that they haven't been previously used for something else).
+
+After you've formatted the floppy disks, you'll need to copy the
+files onto them.  There are 56 total files for the bindist itself,
+plus three small files (CKSUMS, do_cksum.sh, and extract.sh) for
+the install program to use.  ALL of these files must be copies onto
+the floppies.  Each of the bindist files are named "bindist.??",
+where the "??" is replaced by the letter sequence aa through cd.
+Copy these files onto the floppies, placing the three small install
+files onto the final floppy.  The order in which you copy the files
+to floppy is not important, but it makes labelling the disks easier
+if you go in some sort of alphabetical order.
+
+After you've done this, the floppy disks are ready for the install
+program to use.
+
+Later on, after you get the binary distribution installed and everything
+is going great, the same instructions will apply for the other
+distributions, such as the manpages distribution or the XFree86 distribution.
+The number of floppies required will, of course, change for bigger or
+smaller distributions.
+
+
+2. Hard Disk Installation
+
+To prepare for installation from an MS-DOS partition, you should simply
+copy the files from the distribution into a directory with the same
+name as the distribution.  For example, if you are preparing to
+install the bindist set, then make a directory on your C: drive named
+C:\BINDIST and copy the files there.  This will allow the installation
+program to find the files automatically.
+
+
+3. QIC/SCSI Tape Installation.
+
+Installing from tape is probably the easiest method, short of an
+on-line install using ftp or installing from a CDROM.  The installation
+program expects the files to be simply tar'red onto the tape, so after
+getting all of the files for distribution you're interested in, simply
+tar them onto the tape with something like:
+
+        cd <where the *.?? files are>
+        tar cvf /dev/rwt0 (or /dev/rst0) .
+
+from a directory with just the distribution files in it.  Make sure
+that you remember to put CKSUMS, do_cksum.sh, and extract.sh files
+in this directory as well!
+
+If you wish to install multiple *dist releases from one tape, do the
+following:
+
+1. cd to the parent directory of the distributions and put them on tape
+   like so:
+                tar cvf /dev/rwt0 (or /dev/rst0) bindist srcdist ...
+
+2. Install the first distribution on the tape using the tape installation
+   method as normal.  Afterwards, *do not* erase the contents of the temporary
+   directory.  Get a shell with ESC-ESC and cd to the temporary directory
+   yourself.  For each additional *dist you want to load, cd to its
+   subdirectory and type `sh ./extract.sh'.
+
+
+5. Reporting problems, making suggestions, submitting code.
+-----------------------------------------------------------
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached if you can!).
+
+The preferred method to submit bug reports from a machine with internet
+mail connectivity is to use the send-pr command.  Bug reports will be
+dutifully filed by our faithful bugfiler program and you can be sure
+that we'll do our best to respond to all reported bugs as soon as
+possible.
+
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                questions@FreeBSD.org
+
+Additionally, being a volunteer effort, we are always happy to have
+extra hands willing to help - there are already far more enhancements
+to be done than we can ever manage to do by ourselves!  To contact us
+on technical matters, or with offers of help, you may send mail to:
+
+                hackers@FreeBSD.org
+
+Since these mailing lists can experience significant amounts of
+traffic, if you've got slow or expensive mail access and you're
+only interested in keeping up with significant FreeBSD events, you may
+find it preferable to subscribe to:
+
+                announce@FreeBSD.org
+
+
+All but the FreeBSD-bugs groups 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
+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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If your
+name is not mentioned, please be assured that its omission is entirely
+accidental.
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his extensive work with 386BSD.
+
+The FreeBSD "core" team:
+
+        Andrew A. Chernov
+        John Dyson
+        Bruce Evans
+        David Greenman
+        Rodney W. Grimes
+        Jordan K. Hubbard
+        Poul-Henning Kamp
+        Rich Murphey
+        Gary Palmer
+        Geoff Rehmet
+        Paul Richards
+        Soren Schmidt
+        Andreas Schulz
+        Jack Vogel
+        Garrett A. Wollman
+
+
+Special mention to:
+
+        Robert Bruce and Jack Velte of Walnut Creek CDROM, without
+        whose help (and continuing support) this release would never
+        have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        The NetBSD group for their frequent assistance and commentary.
+
+        Additional FreeBSD helpers and beta testers:
+
+        J.T. Conklin                            Julian Elischer
+        Sean Eric Fagan                         Jeffrey Hsu
+        Terry Lambert                           L Jonas Olsson
+        Chris Provenzano                        Dave Rivers
+        Guido van Rooij                         Steven Wallace
+        Atsushi Murai                           Scott Mace
+        Andrew Moore                            Nate Williams
+
+        And everyone at Montana State University for their initial support.
+
+
+Thanks to everyone, especially those not mentioned, and we sincerely
+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 
+
+
    + +&footer; + + diff --git a/data/releases/2.0A/Makefile b/data/releases/2.0A/Makefile new file mode 100644 index 0000000000..4881405b5a --- /dev/null +++ b/data/releases/2.0A/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml + +.include "../../web.mk" diff --git a/data/releases/2.0A/announce.sgml b/data/releases/2.0A/announce.sgml new file mode 100644 index 0000000000..bc27a6cc51 --- /dev/null +++ b/data/releases/2.0A/announce.sgml @@ -0,0 +1,114 @@ + + + + %includes; +]> + +&header; + +

    To: hackers@freefall.cdrom.com
    +Subject: For those that didn't see this in announce - 2.0 ALPHA is released!
    +Date: Thu, 10 Nov 1994 01:31:42 -0800
    +From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>

    + +

    The FreeBSD Project team is very pleased to announce their release of +FreeBSD 2.0 ALPHA; a full 32 bit 4.4 BSD Lite based operating system +for Intel PCs (i386, i486 and Pentium class).

    + +

    Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD has +changed almost entirely. A new port from the Berkeley 4.4 code base +was done, which brought the legal status of the system out of the +shadows with the blessing of Novell (new owners of USL and UNIX). The +port to 4.4 also brought in a host of new features, filesystems and +enhanced driver support. With our new unencumbered code base, we have +every reason to hope that we'll be able to release quality operating +systems without further legal encumbrance for some time to come!

    + +

    FreeBSD 2.0 represents the culmination of almost 2 years of work and +many thousands of man hours put in by an international development +team. We hope you enjoy it!

    + +

    FreeBSD 2.0 ALPHA also features an advanced installation that enables +one to install from tape, CD, SLIP or ethernet (NFS or FTP). FreeBSD +2.0 BETA, planned for the 2nd week of November, will also support +installation from floppy or DOS partition (sorry, it didn't quite make +the ALPHA!) and offer even more "plug-n-play" features for editing +disklabels and such. This is, nonetheless, our easiest to use +installation yet, and we hope that with your feedback and suggestions, +our final 2.0 Release version will be even nicer still!

    + +

    For more information on what's new with FreeBSD, or what general +features it offers, we strongly suggest that you simply download our +boot floppy and boot from it. You can easily read the release notes +on it using a simple menu, and with no danger to the contents of your +hard disk (unless you deliberately chose "proceed with installation", +in which case your fate is in your own hands! :-).

    + +

    Those truly wishing to wait for the final release version of 2.0 are, +of course, encouraged to do so, but I think that many of you will find +this to be our most polished "ALPHA" release yet! Give it a try! An +upgrade path from ALPHA->RELEASE will also be provided, and we do NOT +plan any major changes between now and the final release in December. +We generally try to err on the side of conservatism in our releases, +and the 2.0 release cycle is no exception. Those wishing to obtain +2.0 on CDROM will have to wait until the 2.0 Release date, at which +point it will be made available by Walnut Creek CDROM (info@cdrom.com) +and other CDROM publishers.

    + +

    If you're currently running 1.x and are looking for an upgrade path, +we're sorry to say that only full installations are supported at this +time. Simply back up your password and user files before reinstalling +from the 2.0 media, then bring them back. If public demand is high +enough, and we can figure out a way of easily doing it, we'll offer +something, but it should be understood that the differences between +1.x and 2.0 are large, and it's not certain that we'll be able to do +it at all.

    + +

    Those unable or unwilling to download the boot floppy may also get the +release notes by mail - send mail to <info@FreeBSD.org> for an +automated reply. Updated information will also be provided on a more +or less continuous basis in our WEB pages

    + +

    FreeBSD 2.0A is available for ftp in ftp://ftp.freebsd.org/pub/FreeBSD/2.0-ALPHA/

    + +

    It will also, no doubt, be available on a number of mirror sites as +soon as they pick it up. However, ftp.freebsd.org is on a T3 line and +supports 300 simultaneous users (it's a FreeBSD machine :-), so it's +unlikely that you'll have too much trouble getting it from this site +until the mirrors do so.

    + +

    If you are directly Internet connected, it is also NOT necessary to +load the bindist from this site! Simply download the 2 boot floppies, +begin the installation, and select the FTP installation method - it +will do the rest for you, transparently.

    + +

    Finally, we'd like to publically thank Walnut Creek CDROM, without whos +continuing support and extreme generousity, we'd probably be long +gone! They've been of immense help to us. Thank you, Walnut +Creek CDROM!

    + +

    Thanks must also go to Poul-Henning Kamp, our fearless and long +suffering release engineer for 2.0. While all of us have sacrificed +much sleep to the cause, he has a new wife but has somehow managed to +do so as well! :-)

    + +

    And to all of our users (this is probably starting to sound like the +academy awards :-), a similar thank you! We couldn't have done it +without your constant flow of commentary, patches, donations of code +and moral support. As corny as it sounds, we do it all for you folks! +[Though the ego gratification is nice too :-)]

    + +

    Thanks to all, and we sincerely hope you enjoy this release!

    + +

    Comments, as always, to hackers@FreeBSD.org.

    + + +

    Jordan
    + [on behalf of the FreeBSD Project team] +

    + +&footer; + + diff --git a/data/releases/2.1.5R/Makefile b/data/releases/2.1.5R/Makefile new file mode 100644 index 0000000000..517e40e9d3 --- /dev/null +++ b/data/releases/2.1.5R/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml notes.sgml + +.include "../../web.mk" diff --git a/data/releases/2.1.5R/announce.sgml b/data/releases/2.1.5R/announce.sgml new file mode 100644 index 0000000000..d90dc6c9c7 --- /dev/null +++ b/data/releases/2.1.5R/announce.sgml @@ -0,0 +1,269 @@ + + + + %includes; +]> + +&header; + +

    FreeBSD +2.1.5-RELEASE is now available on ftp.freebsd.org and various +FTP mirror sites throughout the world. It can also be ordered on +CD from +from Walnut Creek CDROM.

    + +

    FreeBSD 2.1.5 represents the culmination of over a year's worth of +work on the 2.1-STABLE branch of +FreeBSD since it began with FreeBSD 2.0.5. In the 7 months since 2.1 +was released, many many bug fixes, updates and careful enhancements +have been made, the results of which you now see here.

    + +

    The STABLE branch was conceived out of the need to allow FreeBSD to +grow and support long-term development projects (like devfs, NFSv3, +IPX, PCCARD, etc.) while at the same time not jeopardizing the +stability of its existing user base. FreeBSD 2.1.5 marks the finishing +point for that effort and, barring any small "slipstream" releases done +to solve significant problems, no further releases along the 2.1-STABLE +branch are anticipated. The concept of "stable" and "experimental" +tracks is not being abandoned, we'll simply be doing this somewhat +differently in the future.

    + +

    For more information on the 2.1.5 release itself, please consult the +Release Notes. + +

    The official sources for FreeBSD are available via anonymous FTP from: + + ftp.freebsd.org. + +Or via the WEB at: + + www.freebsd.org. + +And on CD-ROM from Walnut Creek CDROM: + +

    +     Walnut Creek CDROM
+     4041 Pike Lane, #D
+     Concord CA, 94520 USA
+     Phone: +1 510 674-0783
+     Fax: +1 510 674-0821
+     Tech Support: +1 510 603-1234
+     Email: info@cdrom.com
+     WWW: http://www.cdrom.com
+
    + + +

    Additionally, FreeBSD is available via anonymous FTP from the +following mirror sites. If you choose to obtain FreeBSD via anonymous +FTP, please try to use a site near you:

    + +

    Australia

    +

    In case of problems, please contact hostmaster@au.freebsd.org. +

    + +

    Brazil

    +

    In case of problems, please contact hostmaster@br.freebsd.org. +

    + +

    Canada

    +

    In case of problems, please contact hostmaster@ca.freebsd.org +

    + + +

    Czech Republic

    + + +

    Estonia

    +

    In case of problems, please contact hostmaster@ee.freebsd.org. +

    + + +

    Finland

    +

    In case of problems, please contact hostmaster@fi.freebsd.org. +

    + +

    France

    + + + +

    Germany

    +

    In case of problems, please contact hostmaster@de.freebsd.org. +

    + +

    Hong Kong

    + + +

    Ireland

    +

    In case of problems, please contact hostmaster@ie.freebsd.org. +

    + + +

    Israel

    + + + +

    Japan

    +

    In case of problems, please contact hostmaster@jp.freebsd.org. +

    + +

    Korea

    +

    In case of problems, please contact hostmaster@kr.freebsd.org. +

    + +

    Netherlands

    +

    In case of problems, please contact hostmaster@nl.freebsd.org. +

    + +

    Poland

    + + + +

    Portugal

    + + + +

    Russia

    +

    In case of problems, please contact hostmaster@ru.freebsd.org. +

    + +

    South Africa

    +

    In case of problems, please contact hostmaster@za.freebsd.org. +

    + +

    Sweden

    +

    In case of problems, please contact the hostmaster@se.freebsd.org. +

    + +

    Taiwan

    +

    In case of problems, please contact hostmaster@tw.freebsd.org. +

    + +

    Thailand

    + + + +

    USA

    +

    In case of problems, please contact hostmaster@freebsd.org. +

    + + +

    UK

    +

    In case of problems, please contact hostmaster@uk.freebsd.org. +

    + + +

    The latest versions of export-restricted code for FreeBSD (2.0C or +later) (eBones and secure) are being made available at the following +locations. If you are outside the U.S. or Canada, please get secure +(DES) and eBones (Kerberos) from one of the following foreign +distribution sites: + +

    South Africa

    + + +

    Brazil

    + + +

    Finland

    + + +&footer; + + diff --git a/data/releases/2.1.5R/notes.sgml b/data/releases/2.1.5R/notes.sgml new file mode 100644 index 0000000000..e17341b9b0 --- /dev/null +++ b/data/releases/2.1.5R/notes.sgml @@ -0,0 +1,544 @@ + + + + %includes; +]> + +&header; + +
    +                                 RELEASE NOTES
+                             FreeBSD 2.1.5 RELEASE
+
+0. What is this release?
+------------------------
+FreeBSD 2.1.5R is the follow-on release to 2.1R and focuses primarily
+on fixing bugs, closing security holes and conservative enhancements.
+For more information on bleeding-edge development, please see
+http://www.freebsd.org/handbook/current.html.
+
+
+1. What's New since 2.1.0-RELEASE?
+----------------------------------
+Quite a few things have changed since the last major release
+of FreeBSD.  To make it easier to identify specific changes,
+we've broken them into several major categories:
+
+
+Device Drivers:
+---------------
+Support for the Adaptec AIC7850 on-board SCSI adapter.
+
+Support for Specialix SI and XIO serial cards.
+
+Support for the Stallion EasyIO, EasyConnection 8/32 and
+EasyConnection 8/64, as well as the older Onboard and Brumby serial
+cards.
+
+Support for the Intel EtherExpress Pro/100B PCI ethernet card.
+
+Real PCI Buslogic support (new driver and probing order).
+
+Support for the ARNET (now Digiboard) Sync 570i high-speed serial card.
+
+Better support for the Matrox Meteor frame grabber card.
+
+Support for the Connectix Quickcam (parallel port camera).
+
+Worm driver - it is now possible to burn CDROMs using the Plasmon or
+HP 4080i CDR drives (see `wormcontrol(1)').  NOTE: If your drive
+probes as a CD rather than a WORM, some additional patches may be
+required from -current to get it working for you.  We decided not to
+bring these changes over by default as they make too many changes to
+the SCSI subsystem (not necessarily bad changes, but more risky).
+
+
+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 ccd(4) for more information.
+
+Real PCI bus probing (before ISA) and support for various PCI bridges.
+
+The Linux emulation is now good enough to run the Linux version of
+Netscape, with JAVA support (as well as a number of other Linux
+utilities).
+
+
+
+Userland code updates:
+----------------------
+
+The system installation tool has been revamped with slightly different
+menu behavior and a number of bugs have been fixed.  It's hoped that
+this installation will be more intuitive for new users than previous
+ones (feedback welcomed, of course) as well as more useful in the
+post-install scenario (I know, I keep saying this :-).
+
+Many improvements to the NIS code.
+
+The ncftp program is no longer part of the default system - it has been
+replaced by a library (/usr/src/lib/libftpio) and a more powerful program
+which uses it called ``fetch'' (/usr/src/usr.bin/fetch).  You may find
+ncftp as part of the ports collection (in /usr/ports/net/ncftp) if you
+still wish to use it, though fetch is slightly more capable in that
+it can fetch from both FTP and HTTP servers (ftp://... or http://... URLs).
+See the man page for more details.
+
+
+2. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our release of FreeBSD 2.0 over a year ago, the performance,
+feature set and stability of FreeBSD has improved dramatically.  The
+largest change is a revamped VM system with a merged VM/file buffer
+cache that not only increases performance but reduces FreeBSD's memory
+footprint, making a 5MB configuration a more acceptable minimum.
+Other enhancements include full NIS client and server support,
+transaction TCP support, dial-on-demand PPP, an improved SCSI
+subsystem, early ISDN support, support for FDDI and Fast Ethernet
+(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
+narrow) and 3940 SCSI adaptors along with many hundreds of bug fixes.
+
+We've taken the comments and suggestions of many of our users to
+heart and have attempted to provide what we hope is a more sane and
+easily understood installation process.  Your feedback on this
+(constantly evolving) process is especially welcome!
+
+In addition to the base distributions, FreeBSD offers a new ported
+software collection with over 450 commonly sought-after programs.  The
+list of ports ranges from http (WWW) servers, to games, languages,
+editors and almost everything in between.  The entire ports collection
+requires only 10MB of storage, all ports being expressed as "deltas"
+to their original sources.  This makes it much easier for us to update
+ports and greatly reduces the disk space demands made by the ports
+collection.  To compile a port, you simply change to the directory of
+the program you wish to install, type make and let the system do the
+rest.  The full original distribution for each port you build is
+retrieved dynamically off of CDROM or a local ftp site, so you need
+only enough disk space to build the ports you want.  (Almost) every
+port is also provided as a pre-compiled "package" which can be
+installed with a simple command (pkg_add).  See also the new Packages
+option in the Configuration menu for an especially convenient interface
+to the package collection.
+
+
+A number of additional documents which you may find helpful in the
+process of installing and using FreeBSD may now also be found in the
+/usr/share/doc directory.  You may view the manuals with any HTML
+capable browser by saying:
+
+  To read the handbook:
+      <browser> file:/usr/share/doc/handbook/handbook.html
+
+  To read the FAQ:
+      <browser> file:/usr/share/doc/FAQ/freebsd-faq.html
+
+You can also visit the master (and most frequently updated) copies at
+http://www.freebsd.org.
+
+The export version of FreeBSD does not contain DES code which would
+inhibit its being exported outside the United States.  There is an
+add-on package to the core distribution which contains the programs
+and libraries that normally use DES.  A freely exportable (from
+outside the U.S.)  distribution of DES for our non-U.S. users also
+exists at ftp://ftp.internat.freebsd.org/pub/FreeBSD.
+
+If password security for FreeBSD is all you need and you have no
+requirement for copying encrypted passwords from different hosts
+(Suns, DEC machines, etc) into FreeBSD password entries, then
+FreeBSD's MD5 based security may be all you require!  We feel that our
+default security model is more than a match for DES, and without any
+messy export issues to deal with.  If you're outside (or even inside)
+the U.S., give it a try!  This snapshot also includes support for
+mixed password files - either DES or MD5 passwords will be accepted,
+making it easier to transition from one scheme to the other.
+
+
+3. Supported Configurations
+---------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium Pro class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+What follows is a list of all disk controllers and ethernet cards
+currently known to work with FreeBSD.  Other configurations may also
+work, but we have simply not received any confirmation of this.
+
+
+3.1. Disk Controllers
+---------------------
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+IDE
+ATA
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
+controllers.
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+Adaptec AIC7850 on-board SCSI controllers.
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards as they have no
+   on-board BIOS, such being necessary for mapping the boot device into the
+   system BIOS I/O vectors.  They're perfectly usable for external tapes,
+   CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
+   without a boot ROM.  Some systems DO have a boot ROM, which is generally
+   indicated by some sort of message when the system is first powered up
+   or reset, and in such cases you *will* also be able to boot from them.
+   Check your system/board documentation for more details.
+
+[Note that Buslogic was formerly known as "Bustec"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+Buslogic 956c PCI SCSI controller
+
+NCR 53C810 and 53C825 PCI SCSI controller.
+NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+WD7000 SCSI controller.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+DAT) and CD ROM drives.
+
+The following CD-ROM type systems are supported at this time:
+(cd)    SCSI interface (also includes ProAudio Spectrum and
+        SoundBlaster SCSI)
+(mcd)   Mitsumi proprietary interface (all models)
+(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
+        interface (562/563 models)
+(scd)   Sony proprietary interface (all models)
+(wcd)   ATAPI IDE interface (experimental and should be considered ALPHA
+        quality!).
+
+
+3.2. Ethernet cards
+-------------------
+
+Allied-Telesis AT1700 and RE2000 cards
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21040, DC21041, or DC21140 based NICs (SMC???? DE???)
+DEC FDDI (DEFPA/DEFEA) NICs
+Fujitsu MB86960A/MB86965A
+
+Intel EtherExpress (not recommended due to driver instability)
+Intel EtherExpress Pro/100B PCI Fast Ethernet
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+Note that NO token ring cards are supported at this time as we're
+still waiting for someone to donate a driver for one of them.  Any
+takers?
+
+
+3.3. Misc
+---------
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+ARNET (now Digiboard) Sync 570/i high-speed serial.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+SDL Communications Riscom/8 Serial Board.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
+
+
+
+4. Obtaining FreeBSD
+--------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+4.1. FTP/Mail
+
+You can ftp FreeBSD and any or all of its optional packages from
+`ftp.freebsd.org' - the official FreeBSD release site.
+
+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 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
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
+to get more information on how to fetch files using this mechanism.
+Please do note, however, that this will end up sending many *tens of
+megabytes* through the mail and should only be employed as an absolute
+LAST resort!
+
+
+4.2. CDROM
+
+FreeBSD 2.1-RELEASE and these 2.2 SNAPSHOT CDs may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
+
+Or via the internet from orders@cdrom.com or http://www.cdrom.com.
+Their current catalog can be obtained via ftp as:
+        ftp://ftp.cdrom.com/cdrom/catalog.
+
+Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
+FreeBSD 2.2-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription
+(-RELEASE and -SNAP subscriptions are entirely seperate).  With a
+subscription, you will automatically receive updates as they are released.
+Your credit card will be billed when each disk is shipped and you may cancel
+your subscription at any time without further obligation.
+
+Walnut Creek CDROM also sells a full line of FreeBSD related
+merchandise such as T-shirts ($14.95, available in "child", Large and
+XL sizes), coffee mugs ($9.95), tattoos ($0.25 each) and posters
+($3.00).
+
+Shipping (per order not per disc) is $5 in the US, Canada or Mexico
+and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
+Express or checks in U.S. Dollars and ship COD within the United
+States.  California residents please add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+
+Reporting problems, making suggestions, submitting code
+-------------------------------------------------------
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached, if you can!).
+
+The preferred method to submit bug reports from a machine with
+internet mail connectivity is to use the send-pr command.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.  Bugs filed in this way are also visible on our WEB site
+in the support section and are therefore valuable both as bug reports
+and as "signposts" for other users concerning potential problems to
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                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:
+
+                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:
+
+                announce@FreeBSD.org
+
+
+All but the freebsd-bugs groups 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
+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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If you've
+contributed something substantive to us and your name is not mentioned
+here, please be assured that its omission is entirely accidental.
+Please contact hackers@FreeBSD.org for any desired updates to the
+lists that follow:
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his initial work with 386BSD.
+
+The FreeBSD Core Team
+(in alphabetical order by last name):
+
+        Satoshi Asami <asami@FreeBSD.org>
+        Andrey A. Chernov <ache@FreeBSD.org>
+        John Dyson <dyson@FreeBSD.org>
+        Bruce Evans <bde@FreeBSD.org>
+        Justin Gibbs <gibbs@FreeBSD.org>
+        David Greenman <davidg@FreeBSD.org>
+        Jordan K. Hubbard <jkh@FreeBSD.org>
+        Poul-Henning Kamp <phk@FreeBSD.org>
+        Rich Murphey <rich@FreeBSD.org>
+        Gary Palmer <gpalmer@FreeBSD.org>
+        Søren Schmidt <sos@FreeBSD.org>
+        Peter Wemm <peter@FreeBSD.org>
+        Garrett A. Wollman <wollman@FreeBSD.org>
+        Jörg Wunsch <joerg@FreeBSD.org>
+
+
+The FreeBSD Development Team, excluding core team members
+(in alphabetical order by last name):
+
+        Ugen J.S. Antsilevich <ugen@FreeBSD.org>
+        Torsten Blum <torstenb@FreeBSD.org>
+        Gary Clark II <gclarkii@FreeBSD.org>
+        Adam David <adam@FreeBSD.org>
+        Peter Dufault <dufault@FreeBSD.org>
+        Frank Durda IV <uhclem@FreeBSD.org>
+        Julian Elischer <julian@FreeBSD.org>
+        Sean Eric Fagan <sef@FreeBSD.org>
+        Stefan Esser <se@FreeBSD.org>
+        Bill Fenner <fenner@FreeBSD.org>
+        John Fieber <jfieber@FreeBSD.org>
+	Marc G. Fournier <scrappy@FreeBSD.org>
+        Lars Fredriksen <lars@freeBSD.org>
+        Thomas Gellekum <tg@FreeBSD.org>
+        Thomas Graichen <graichen@FreeBSD.org>
+        Rod Grimes <rgrimes@FreeBSD.org>
+	John Hay <jhay@FreeBSD.org>
+        Eric L. Hernes <erich@FreeBSD.org>
+        Jeffrey Hsu <hsu@FreeBSD.org>
+        Gary Jennejohn <gj@FreeBSD.org>
+	Andreas Klemm <andreas@FreeBSD.org>
+        L Jonas Olsson <ljo@FreeBSD.org>
+        Scott Mace <smace@FreeBSD.org>
+        Atsushi Murai <amurai@FreeBSD.org>
+        Mark Murray <markm@FreeBSD.org>
+	Alex Nash <alex@FreeBSD.org>
+	Sujal Patel <smpatel@FreeBSD.org>
+        Bill Paul <wpaul@FreeBSD.org>
+        Joshua Peck Macdonald <jmacd@FreeBSD.org>
+        John Polstra <jdp@FreeBSD.org>
+        Mike Pritchard <mpp@FreeBSD.org>
+        Doug Rabson <dfr@FreeBSD.org>
+	James Raynard <jraynard@FreeBSD.org>
+        Geoff Rehmet <csgr@FreeBSD.org>
+        Martin Renters <martin@FreeBSD.org>
+        Paul Richards <paul@FreeBSD.org>
+        Ollivier Robert <roberto@FreeBSD.org>
+        Dima Ruban <dima@FreeBSD.org>
+        Wolfram Schneider <wosch@FreeBSD.org>
+        Andreas Schulz <ats@FreeBSD.org>
+        Karl Strickland <karl@FreeBSD.org>
+        Paul Traina <pst@FreeBSD.org>
+        Guido van Rooij <guido@FreeBSD.org>
+        Steven Wallace <swallace@FreeBSD.org>
+        Nate Williams <nate@FreeBSD.org>
+        Jean-Marc Zucconi <jmz@FreeBSD.org>
+
+
+Additional FreeBSD helpers and beta testers:
+
+        Coranth Gryphon            Dave Rivers 
+        Kaleb S. Keithley	   Michael Smith
+        Terry Lambert		   David Dawes
+        Troy Curtis
+
+
+Special mention to:
+
+        Walnut Creek CDROM, without whose help (and continuing support)
+        this release would never have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        Chuck Robey for his donation of a floppy tape streamer for
+        testing.
+
+        Larry Altneu and Wilko Bulte for providing us with Wangtek
+        and Archive QIC-02 tape drives for testing and driver hacking.
+
+        CalWeb Internet Services for the loan of a P6/200 machine for
+        speedy package building.
+
+        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 Core Team
+
    + +&footer; + + + diff --git a/data/releases/2.1R/Makefile b/data/releases/2.1R/Makefile new file mode 100644 index 0000000000..517e40e9d3 --- /dev/null +++ b/data/releases/2.1R/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml notes.sgml + +.include "../../web.mk" diff --git a/data/releases/2.1R/announce.sgml b/data/releases/2.1R/announce.sgml new file mode 100644 index 0000000000..72f2ec9cce --- /dev/null +++ b/data/releases/2.1R/announce.sgml @@ -0,0 +1,58 @@ + + + + %includes; +]> + +&header; + +

    +Date: Sun, 19 Nov 1995 14:48:46 -0800
    +From: "Jordan K. Hubbard" <jkh@freebsd.org>
    +To: announce@freefall.cdrom.com
    +Subject: 2.1.0-RELEASE now available! +

    + +

    Could it be? Could the long-awaited release of FreeBSD + 2.1 truly have arrived?

    + +

    It gives me great pleasure to answer those questions with + a ``yes!''

    + +

    FreeBSD 2.1.0-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 + where it will be shipping shortly.

    + +

    FreeBSD 2.1 represents the culmination of 6 months worth + of work on the 2.1-STABLE branch of FreeBSD since the + previous release (FreeBSD 2.0.5).

    + +

    The STABLE branch was conceived out of the need to allow + FreeBSD to grow and support long-term development projects + like devfs, NFSv3, IPX, PCCARD, etc. while at the same time + not jeopardizing the stability of its existing user base. + Experimental or high-impact changes are allowed into FreeBSD-current, + which represents a sort of shared group development tree, + and only well tested or obvious fixes are allowed into + STABLE. In a few rare cases, where some bit of + functionality was entirely missing before, we've supplied + an ALPHA test quality version in STABLE on the premise that + some functionality is better than none at all (a good + example being the IDE CDROM driver).

    + +

    For more information on the 2.1 release itself, please + consult the documentation that accompanies the installation + procedure.

    + +

    Jordan

    + +&footer; + + diff --git a/data/releases/2.1R/notes.sgml b/data/releases/2.1R/notes.sgml new file mode 100644 index 0000000000..23ee084198 --- /dev/null +++ b/data/releases/2.1R/notes.sgml @@ -0,0 +1,349 @@ + + + + %includes; +]> + +&header; + +
    +
+                                 RELEASE NOTES
+                                    FreeBSD
+                                  Release 2.1
+
+1. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our release of FreeBSD 2.0 over a year ago, the performance,
+feature set and stability of FreeBSD has improved dramatically.  The
+largest change is a revamped VM system with a merged VM/file buffer
+cache that not only increases performance but reduces FreeBSD's memory
+footprint, making a 5MB configuration a more acceptable minimum.
+Other enhancements include full NIS client and server support,
+transaction TCP support, dial-on-demand PPP, an improved SCSI
+subsystem, early ISDN support, support for FDDI and Fast Ethernet
+(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
+narrow) and 3940 SCSI adaptors along with many hundreds of bug fixes.
+
+We've also taken the comments and suggestions of many of our users to
+heart and have attempted to provide what we hope is a more sane and
+easily understood installation process.  Your feedback on this
+(constantly evolving) process is especially welcome!
+
+In addition to the base distributions, FreeBSD offers a new ported
+software collection with over 350 commonly sought-after programs.  The
+list of ports ranges from http (WWW) servers, to games, languages,
+editors and almost everything in between.  The entire ports collection
+requires only 10MB of storage, all ports being expressed as "deltas"
+to their original sources.  This makes it much easier for us to update
+ports and greatly reduces the disk space demands made by the ports
+collection.  To compile a port, you simply change to the directory of
+the program you wish to install, type make and let the system do the
+rest.  The full original distribution for each port you build is
+retrieved dynamically off of CDROM or a local ftp site, so you need
+only enough disk space to build the ports you want.  (Almost) every
+port is also provided as a pre-compiled "package" which can be
+installed with a simple command (pkg_add).  See also the new Packages
+option in the Configuration menu for an especially convenient interface
+to the package collection.
+
+
+A number of additional documents which you may find helpful in the
+process of installing and using FreeBSD may now also be found in the
+/usr/share/doc directory.  You may view the manuals with any HTML
+capable browser by saying:
+
+  To read the handbook:
+      <browser> file:/usr/share/doc/handbook/handbook.html
+
+  To read the FAQ:
+      <browser> file:/usr/share/doc/FAQ/freebsd-faq.html
+
+You can also visit the master (and most frequently updated) copies at
+http://www.freebsd.org.
+
+The core of FreeBSD does not contain DES code which would inhibit its
+being exported outside the United States.  There is an add-on package
+to the core distribution, for use only in the United States, that
+contains the programs that normally use DES.  The auxiliary packages
+provided separately can be used by anyone.  A freely (from outside the
+U.S.) exportable distribution of DES for our non-U.S. users also
+exists at ftp://ftp.internat.freebsd.org/pub/FreeBSD.
+
+If password security for FreeBSD is all you need and you have no
+requirement for copying encrypted passwords from different hosts
+(Suns, DEC machines, etc) into FreeBSD password entries, then
+FreeBSD's MD5 based security may be all you require!  We feel that our
+default security model is more than a match for DES, and without any
+messy export issues to deal with.  If you're outside (or even inside)
+the U.S., give it a try!
+
+
+Supported Configurations
+------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+What follows is a list of all disk controllers and ethernet cards
+currently known to work with FreeBSD.  Other configurations may also
+work, but we have simply not received any confirmation of this.
+
+
+	Disk Controllers
+	----------------
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+IDE
+ATA
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
+controllers.
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards as they have no
+   on-board BIOS, such being necessary for mapping the boot device into the
+   system BIOS I/O vectors.  They're perfectly usable for external tapes,
+   CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
+   without a boot ROM.  Some systems DO have a boot ROM, which is generally
+   indicated by some sort of message when the system is first powered up
+   or reset, and in such cases you *will* also be able to boot from them.
+   Check your system/board documentation for more details.
+
+[Note that Buslogic was formerly known as "Bustek"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+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. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+WD7000 SCSI controller.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+DAT) and CD ROM drives.
+
+The following CD-ROM type systems are supported at this time:
+(cd)    SCSI interface (also includes ProAudio Spectrum and
+        SoundBlaster SCSI)
+(mcd)   Mitsumi proprietary interface (all models)
+(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
+        interface (562/563 models)
+(scd)   Sony proprietary interface (all models)
+(wcd)   ATAPI IDE interface (experimental and should be considered ALPHA
+        quality!).
+
+
+	Ethernet cards
+	--------------
+
+Allied-Telesis AT1700 and RE2000 cards
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21140 based NICs (SMC???? DE???)
+DEC FDDI (DEFPA/DEFEA) NICs
+
+Fujitsu FMV-181 and FMV-182
+
+Intel EtherExpress
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+Note that NO token ring cards are supported at this time as we're
+still waiting for someone to donate a driver for one of them.  Any
+takers?
+
+
+	Misc Hardware
+	-------------
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+SDL Communications Riscom/8 Serial Board.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
+
+---
+
+
+Reporting problems, making suggestions and submitting code:
+===========================================================
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached, if you can!).
+
+The preferred method to submit bug reports from a machine with
+internet mail connectivity is to use the send-pr command.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.  Bugs filed in this way are also visible on our WEB site
+in the support section and are therefore valuable both as bug reports
+and as "signposts" for other users concerning potential problems to
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                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:
+
+                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:
+
+                announce@FreeBSD.org
+
+
+Any of the groups 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 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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If you've
+contributed something substantive to us and your name is not mentioned
+here, please be assured that its omission is entirely accidental.
+Please contact hackers@FreeBSD.org for any desired updates to the
+lists that follow:
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his initial work with 386BSD.
+
+The FreeBSD Core Team
+(in alphabetical order by first name):
+
+        Andrey A. Chernov <ache@FreeBSD.org>
+        Bruce Evans <bde@FreeBSD.org>
+        David Greenman <davidg@FreeBSD.org>
+        Garrett A. Wollman <wollman@FreeBSD.org>
+        Gary Palmer <gpalmer@FreeBSD.org>
+        Jörg Wunsch <joerg@FreeBSD.org>
+        John Dyson <dyson@FreeBSD.org>
+        Jordan K. Hubbard <jkh@FreeBSD.org>
+        Justin Gibbs <gibbs@FreeBSD.org>
+        Peter Wemm <peter@FreeBSD.org>
+        Poul-Henning Kamp <phk@FreeBSD.org>
+        Rich Murphey <rich@FreeBSD.org>
+        Satoshi Asami <asami@FreeBSD.org>
+        Søren Schmidt <sos@FreeBSD.org>
+
+Special mention to:
+
+        Walnut Creek CDROM, without whose help (and continuing support)
+        this release would never have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        Additional FreeBSD helpers and beta testers:
+
+        Atsushi Murai               Coranth Gryphon    
+        Dave Rivers                 Frank Durda IV
+        Guido van Rooij             Jeffrey Hsu
+        John Hay                    Julian Elischer
+        Kaleb S. Keithley           Michael Smith
+        Nate Williams               Peter Dufault
+        Rod Grimes                  Scott Mace
+        Stefan Esser                Steven Wallace
+        Terry Lambert               Wolfram Schneider
+
+        And 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 Core Team
+
    + +&footer; + + diff --git a/data/releases/Makefile b/data/releases/Makefile new file mode 100644 index 0000000000..32f4f68c0d --- /dev/null +++ b/data/releases/Makefile @@ -0,0 +1,5 @@ +DOCS= index.sgml snapshots.sgml + +SUBDIR= 1.1 1.1.5 2.0 2.0.5A 2.0.5R 2.0A 2.1R 2.1.5R + +.include "../web.mk" diff --git a/data/releases/Makefile.inc b/data/releases/Makefile.inc new file mode 100644 index 0000000000..0e4f1d8520 --- /dev/null +++ b/data/releases/Makefile.inc @@ -0,0 +1,2 @@ +WEBBASE= /data/releases + diff --git a/data/releases/index.sgml b/data/releases/index.sgml new file mode 100644 index 0000000000..570f143d31 --- /dev/null +++ b/data/releases/index.sgml @@ -0,0 +1,104 @@ + + + + %includes; +]> + +&header; + +

    Newsflash!

    +

    Recent announcement about FreeBSD Releases

    + +

    Current Release

    + +
      +
    • Release 2.1.5 RELEASE (July 14, 1996) + + &a.latest.ann;Announcement : + &a.latest.not;Release Notes. + +
      + If you wish to obtain this release, please see Obtaining and Installing + FreeBSD for details. +
      • +
    + +

    Future Releases

    + +
      + +
    • The next official release will be + 2.2 which will be derived from the + FreeBSD-current + branch of the development tree. Periodic + snapshot releases + will be made available before the release.
      • + +
    • The FreeBSD-stable + branch is also being loosely supported, with critical bug fixes + and installation system changes being brought in from time to time. + A 2.1.6 release will probably occur on this branch some + time in the next 2-3 months, just to clean up a last few remaining + nits from 2.1.5.
      • +
    + +

    Past Releases

    + + + +&footer; + + diff --git a/data/releases/snapshots.sgml b/data/releases/snapshots.sgml new file mode 100644 index 0000000000..66375890b4 --- /dev/null +++ b/data/releases/snapshots.sgml @@ -0,0 +1,73 @@ + + + + %includes; +]> + +&header; + +

    What are snapshots?

    + + +

    As part of an ongoing effort to improve the overall + release process before a release actually slips + out the door with problems that make folks mad, we are now + periodically producing interim test releases + called snapshots. These snapshots will be very similar to + full releases, except that they'll be somewhat more + minimal. In particular, before getting and installing a + snapshot release, be aware of following: + +

      + +
    • We generally will not, for example, produce new + XFree86 distributions or worry much about the tools + directory, unless either of those two things are affected + by the changes being tested. + +
    • The major release number will not be changed in the + main distribution for each snapshot. It will + only be changed on the boot floppies so that you + know when the snapshot was made. These are not + releases, these are snapshots, and it's + important that this distinction be preserved. People can + and will, of course, refer to snapshots by date in mail + or netnews, we just don't want them to start thinking + that Christmas came early and the next release is already + out! + +
    • Finally, we will not necessarily update the + documentation. If a README still refers to a previous release, + well, that's much less important to than getting the + real bug fixes and new features out for testing. Complaints + about that kind of thing will be quietly ignored. Again, + these are snapshots, not releases! +
    + +

    Your feedback on these snapshots is, of course, greatly + welcome. They're not just for our benefit - those who are + coming to rely on FreeBSD for mission critical + applications should welcome a chance to get at more updated + bits in a structured fashion. You can also use these + snapshots as tangible evidence that your feedback is + getting incorporated and that you (hopefully) won't have + any unpleasant surprises in the next release. On the other hand, if + you do send us hate mail next release and it turns out that you + never even tried the snapshots, well, it cuts both ways! + +

    Where to find snapshots

    + +

    Snapshots are available via anonymous from ftp://ftp.freebsd.org/pub/FreeBSD/. + The snapshot releases are in directories named in the + format REL-YYMMDD-SNAP where `REL' is the + release number, `YY' is the year, `MM' is + the month, and `DD' is the day the snapshot was + released. Each snapshot directory contains a + `README' file which outlines the changes for the + particular snapshot.

    + +&footer; + + diff --git a/data/robots.txt b/data/robots.txt new file mode 100644 index 0000000000..20fd53e7c1 --- /dev/null +++ b/data/robots.txt @@ -0,0 +1,4 @@ +User-agent: * +Disallow: /cgi-bin/ +Disallow: /cgi/ +Disallow: ~/jfieber/data/cgi/ diff --git a/data/search.sgml b/data/search.sgml new file mode 100644 index 0000000000..84ca910409 --- /dev/null +++ b/data/search.sgml @@ -0,0 +1,112 @@ + + + %includes; +]> + +&header; + +

    FreeBSD Mailing List Archives

    + +
    + +

    Search for:

    + +

    Note: Use the operators AND or NOT to limit your + search. Look here + for more hints.

    + +

    + +

    In archive(s):

    + +

    Note: Searching more than three or four archives at once may +yield inaccurate results.

    + +

    + + Questions: General questions
    + + + Announce: Important events / milestones
    + + + Bugs: Reports and discussion of bugs
    + + + Chat: Random topics (sometimes) related to FreeBSD
    + + + Commit: Changes made to the FreeBSD source tree
    + + + Current: Discussions concerning the use of + FreeBSD-current sources
    + + + Doc: Discussions concerning documentation
    + + + Emulation: Emulating other systems on FreeBSD
    + + + Fs: Discussions concerning FreeBSD filesystems
    + + + Hackers: Technical discussions and suggestions
    + + + Hardware: Discussions concerning hardware as it + relates to FreeBSD
    + + + Install: Discussions concerning the installation + process
    + + + ISP: Discussions for ISPs using FreeBSD
    + + + Mobile: Using FreeBSD in a mobile environment
    + + + Multimedia: Discussions about FreeBSD as a + multimedia platform
    + + + Platforms: Cross-platform FreeBSD issues + (non-Intel FreeBSD ports)
    + + + Ports: Discussions concerning FreeBSD's ports collection
    + + + SCSI: Discussions about FreeBSD's SCSI support
    + + + Security: FreeBSD computer security + issues (DES, Kerberos, etc.)
    + + + SMP: FreeBSD on multi-processor platforms
    + + + Stable: Discussion of the FreeBSD-stable branch + of the development tree.
    + + + User-Groups: A forum for FreeBSD user groups

    + +

    Limit the number of results to

    + +

    + +
    + +&footer; + + + + diff --git a/data/searchhints.sgml b/data/searchhints.sgml new file mode 100644 index 0000000000..6436021e34 --- /dev/null +++ b/data/searchhints.sgml @@ -0,0 +1,50 @@ + + + %includes; +]> + +&header; + +

    If you got lots of irrelevant results...

    + +
      +
    1. If you search for several words such as "quantum + hard drives", an OR is implied meaning that to be + counted as relevant, only one of the word has to appear + in a message. To find only messages with all three + words, change the search to "quantum and hard and + drives"

      2. + +
    2. If you still get lots of irrelevant messages, see if + they have something in common. If so, you can exclude + them with the not operator. For example + "quantum and hard and drives not ide" will + exclude any messages about ide quantum hard drives.
      3. +
    + +

    If you don't think you got everything you should have...

    + +
      +
    1. If one of your keywords has variant forms, be sure to + enter all relevant forms. If you are searching for + "buslogic", you might change it to "buslogic + or bustek".

      2. + +
    2. Words with varying suffixes can be wildcarded. + Searching for "drive*" will pick up words such + as drive, drives, driver, + drivers and so on.

      3. + +
    3. Try discarding words that could be implied by the + context of the message. For example "quantum and + hard and drive" might miss some relevant messages + that "quantum and drive" would get.
      4. +
    + +
    +Return to the search page + +&footer; + + diff --git a/data/support.sgml b/data/support.sgml new file mode 100644 index 0000000000..4c1de50906 --- /dev/null +++ b/data/support.sgml @@ -0,0 +1,252 @@ + + + %includes; +]> + +&header; + +

    Mailing lists

    + +

    Mailing list are the primary support channel for FreeBSD + users, with numerous mailing list covering different + topic areas. When in doubt about what list to post a + question to, post to questions@freebsd.org.

    + +

    You can search the mailing list + archives at www.freebsd.org.

    + +

    For speakers of German, there are some german language mailing + lists available. See + http://www.de.freebsd.org/de/ or send mail to + majordomo@de.freebsd.org + to join or find out more information about the lists. + +

    For speakers of Portuguese, there are some portuguese language mailing + lists available. See + http://www.br.freebsd.org/list.html + or send mail to + listproc@br.freebsd.org to join or find out more information about + the list. + +

    For speakers of Japanese, there are some japanese language mailing + lists available. See + http://www.jp.freebsd.org/ or send mail to + majordomo@jp.freebsd.org + to join or find out more information about the lists. + +

    Newsgroups

    + +

    There are a few FreeBSD specific newsgroups, along with + numerous other newsgroups on topics of interest to FreeBSD + users, though the mailing lists remain the most reliable way to + get in touch with the FreeBSD developers. For miscellaneous + FreeBSD discussion, see + comp.unix.bsd.freebsd.misc. For important announcements, + see + comp.unix.bsd.freebsd.announce. + +

    WEB Resources

    + + Our WEB pages remain one of the best sources of information, + and are also mirrored at many sites around the world. Most countries + also now have subdomains set up under freebsd.org to make such + local resources easier to find - when in doubt, try connecting to + www.yourcountry.freebsd.org (e.g. + www.de.freebsd.org for + Germany or www.au.freebsd.org + for Australia). The same is also true for FTP servers, by + the way. + +

    For information on recent FreeBSD progress and releases, + see the Newsflash page. + +

    GNATS + Problem Report Database

    + + + +

    Problem reports may also be submitted to the + development team using the + send-pr(1) command on a FreeBSD system or by sending an email + message to bugs@freebsd.org. + Please note that + send-pr is preferred since messages sent to the mailing list are + not tracked as official problem reports! + +

    CVS Repository

    + +

    CVS (the Concurrent Version System) is the tool we use for + keeping our sources under control. Every change (with + accompanying log message explaining its purpose) from + FreeBSD 2.0 to the present is stored here, and can be + easily viewed from here (click on the link). To obtain a + complete copy of the FreeBSD CVS respository, please use + either the sup or CTM tools or simply FTP it + from here. + +

    User Groups

    + +
      +
    • BAFUG (Bay Area FreeBSD User Group) (contact info?)

      • + +
    • BUG/HH (BSD user group Hamburg) meets on the last + Tuesday of the month at 7.00pm in the Chinese restaurant + Lotus Bluete, Loewenstrasse 22 in Hamburg + Eppendorf. Most members are FreeBSD users, although + users of all BSD flavors are welcome. Interested people + should send mail to bsdhh@elbe.desy.de. +
      FAQ File + (in German)       +

      • + +
    • The Brainstorm + users group meets in Wuerzburg, Germany and welcomes all users of + Unix, with some emphasis on helping new users of FreeBSD. They + meet every monday at 8.00pm in the "Cafe Klug", Muenzstrasse, + Wuerzburg. Mail + bs@rak.franken.de + for more information or follow the Brainstorm link. +

      • + +
    • FUUNM (Free Unix Users of New Mexico) meets on the 2nd + Saturday of the month from 4:30-6:00pm at the Farris + Engineering Center, room 141, University of new Mexico. + This is not specifically a FreeBSD user group, but if you + are in the area, your presence is welcome. The group + operates a mailing list (fuunm@astro.phys.unm.edu). + Contact Alan + Lundin for more information.

      • + +
    • FreeBSD-Milwaukee + Wisconson meets occasionaly and has a mailing list: freebsd-mke-l@ns.sol.net. send + mail to freebsd-mke-l-request@ns.sol.net + to subscribe.

      • + +
    • RUUG (Reno Unix Users Group) meets monthly in Reno + Nevada and discusses the use of FreeBSD and Linux. + Contact Eric Blood + or Todd + Crenshaw for more information.

      • + +
    • Washington DC (contact info?)

      • +
    + + +

    General UNIX Information

    + + + +

    The X Window System

    + +
      +
    • The XFree86 + Project provides users of a variety of Intel based + Unix systems, including FreeBSD, with an excellent X + Window system.
      • + +
    • The WINE project is working to provide the ability to + run MS-Windows software on Intel based Unix systems such + as FreeBSD, NetBSD and Linux. More information is + available from http://daedalus.dra.hmg.gb/gale/wine/wine.html.
      • +
    + +

    Hardware

    + + +

    Multimedia

    + + + + +

    Related Operating System Projects

    +
      + +
    • NetBSD + is a very close relative of FreeBSD.
      • + +
    • OpenBSD + is derived from NetBSD and supported by a group of former + NetBSD developers.
      • + +
    • Linux is + another free Unix-like system.
      • + +
    • Lites + is a 4.4 BSD Lite based server and emulation library that + provides free unix functionality to a Mach based + system.
      • + +
    • The GNU + HURD project is another effort to develop a free + Unix-like operating system.
      • +
    + +&footer; + + + + diff --git a/data/tutorials/Makefile b/data/tutorials/Makefile new file mode 100644 index 0000000000..7f32f2a5d2 --- /dev/null +++ b/data/tutorials/Makefile @@ -0,0 +1,4 @@ +DOCS= index.sgml +SUBDIR= disklessx +DOCSUBDIR= ddwg devel fonts mh multios newuser +.include "../web.mk" diff --git a/data/tutorials/Makefile.inc b/data/tutorials/Makefile.inc new file mode 100644 index 0000000000..378ca4b280 --- /dev/null +++ b/data/tutorials/Makefile.inc @@ -0,0 +1 @@ +WEBBASE?= /data/tutorials diff --git a/data/tutorials/ddwg/Makefile b/data/tutorials/ddwg/Makefile new file mode 100644 index 0000000000..5fb92d5a76 --- /dev/null +++ b/data/tutorials/ddwg/Makefile @@ -0,0 +1,5 @@ +DOC= ddwg +SRCS= ddwg.sgml +SGMLOPTS= -ssi + +.include diff --git a/data/tutorials/ddwg/ddwg.sgml b/data/tutorials/ddwg/ddwg.sgml new file mode 100644 index 0000000000..a9c40d5c5b --- /dev/null +++ b/data/tutorials/ddwg/ddwg.sgml @@ -0,0 +1,1128 @@ + + + + +
    + +FreeBSD Device Driver Writer's Guide +<author>Eric L. Hernes, <tt/erich@rrnet.com/ +<date>Wednesday, May 29, 1996 + +<abstract> + +This document describes how to add a device driver to FreeBSD. It is +<it/not/ intended to be a tutorial on unix device drivers in general. +It is intended for device driver authors, familiar with the unix +device driver model, to work on FreeBSD. + +</abstract> + +<toc> + +<sect> Overview + +<p> <it> +The FreeBSD kernel is very well documented, unfortunately it's all +in `C'. +</it> + +<sect> Types of drivers. + +<sect1> Character + +<sect2> Data Structures +<p> <tt/struct cdevsw/ Structure + +<sect2> Entry Points +<sect3> d_open() +<p> +d_open() takes several arguments, the formal list looks something like: +<code> +int +d_open(dev_t dev, int flag, int mode, struct proc *p) +</code> +d_open() is called on <em/every/ open of the device. +<p> + +The <tt/dev/ argument contains the major and minor number of the +device opened. These are available through the macros <tt/major()/ and +<tt/minor()/ +<p> + +The <tt/flag/ and <tt/mode/ arguments are as described in the open(2) +manual page. It is recommended that you check these for access modes +in <sys/fcntl.h> and do what is required. For example if <tt/flag/ +is (O_NONBLOCK | O_EXLOCK) the open should fail if either it would +block, or exclusive access cannot be granted. +<p> + +The <tt/p/ argument contains all the information about the current +process. + +<sect3> d_close() +<p> +d_close() takes the same argument list as d_open(): +<code> +int +d_close(dev_t dev , int flag , int mode , struct proc *p) +</code> + +d_close() is only called on the last close of your device (per minor +device). For example in the following code fragment, d_open() is called +3 times, but d_close() is called only once. +<code> + ... + fd1=open("/dev/mydev", O_RDONLY); + fd2=open("/dev/mydev", O_RDONLY); + fd3=open("/dev/mydev", O_RDONLY); + ... + <useful stuff with fd1, fd2, fd3 here> + ... + close(fd1); + close(fd2); + close(fd3); + ... +</code> + +The arguments are similar to those described above for +d_open(). + +<sect3> d_read() and d_write() +<p> +d_read() and d_write take the following argument lists: +<code> +int +d_read(dev_t dev, struct uio *uio, int flat) +int +d_write(dev_t dev, struct uio *uio, int flat) +</code> + +The d_read() and d_write() entry points are called when read(2) and +write(2) are called on your device from user-space. The transfer +of data can be handled through the kernel support routine uiomove(). + +<sect3> d_ioctl() +<p> +It's argument list is as follows: +<code> +int +d_ioctl(dev_t dev, int cmd, caddr_t arg, int flag, struct proc *p) +</code> + +d_ioctl() is a catch-all for operations which don't make sense in +a read/write paradigm. Probably the most famous of all ioctl's is on +tty devices, through stty(1). The ioctl entry point is called from +ioctl() in sys/kern/sys_generic.c<p> + +There are four different types of ioctl's which can be implemented. +<sys/ioccom.h> contains convenience macros for defining these ioctls. + +<tt/_IO(g,n)/ for control type operations. &nl; + +<tt/_IOR(g,n,t)/ for operations that read data from a device. &nl; + +<tt/_IOW(g,n,t)/ for operations that write data to a device. &nl; + +<tt/_IOWR(g,n,t)/ for operations that write to a device, and then +read data back. &nl; + +Here <tt/g/ refers to a <em/group/. This is an 8-bit value, typically +indicative of the device; for example, 't' is used in tty ioctls. +<tt/n/ refers to the number of the ioctl within the group. On SCO, this +number alone denotes the ioctl. <tt/t/ is the data type which will +get passed to the driver; this gets handed to a sizeof() operator in +the kernel. The ioctl() system call will either copyin() or copyout() +or both for your driver, then hand you a pointer to the data structure +in the <tt/arg/ argument of the d_ioctl call. Currently the data size +is limited to one page (4k on the i386). + +<sect3> d_stop() +<sect3> d_reset() +<sect3> d_devtotty() +<sect3> d_select() +<sect3> d_mmap() +<sect3> d_strategy() +<p> +d_strategy()'s argument list is as follows: +<code> +void +d_strategy(struct buf *bp) +</code> + +<p> d_strategy() is used for devices which use some form of scatter-gather +io. It is most common in a block device. This is significantly different +than the System V model, where only the block driver performs scatter-gather +io. Under BSD, character devices are sometimes requested to perform +scatter-gather io via the readv() and writev() system calls. + +<sect2> Header Files + +<sect1> Block +<sect2> Data Structures +<p> <tt/struct bdevsw/ Structure +<p> <tt/struct buf/ Structure + +<sect2> Entry Points +<sect3> d_open() +<p> Described in the Character device section. + +<sect3> d_close() +<p> Described in the Character device section. + +<sect3> d_strategy() +<p> Described in the Character device section. + +<sect3> d_ioctl() +<p> Described in the Character device section. + +<sect3> d_dump() + +<sect3> d_psize() + +<sect2> Header Files + +<sect1> Network +<sect2> Data Structures +<p> <tt/struct ifnet/ Structure + +<sect2> Entry Points +<sect3> if_init() +<sect3> if_output() +<sect3> if_start() +<sect3> if_done() +<sect3> if_ioctl() +<sect3> if_watchdog() + +<sect2> Header Files + +<sect1> Line Discipline +<sect2> Data Structures + +<p> <tt/struct linesw/ Structure + +<sect2> Entry Points +<sect3> l_open() +<sect3> l_close() +<sect3> l_read() +<sect3> l_write() +<sect3> l_ioctl() +<sect3> l_rint() +<sect3> l_start() +<sect3> l_modem() + +<sect2> Header Files + +<sect> Supported Busses + +<sect1> ISA -- Industry Standard Architecture +<sect2> Data Structures + +<sect3> <tt/struct isa_device/ Structure +<p> +This structure is required, but generally it is created by config(8) +from the kernel configuration file. It is required on a per-device +basis, meaning that if you have a driver which controls two serial +boards, you will have two isa_device structures. If you build a +device as an LKM, you must create your own isa_device structure to +reflect your configuration. (lines 85 - 131 in pcaudio_lkm.c) There is +nearly a direct mapping between the config file and the isa_device +structure. The definition from /usr/src/sys/i386/isa/isa_device.h is: +<code> +struct isa_device { + int id_id; /* device id */ + struct isa_driver *id_driver; + int id_iobase; /* base i/o address */ + u_short id_irq; /* interrupt request */ + short id_drq; /* DMA request */ + caddr_t id_maddr; /* physical i/o memory address on bus (if any)*/ + int id_msize; /* size of i/o memory */ + inthand2_t *id_intr; /* interrupt interface routine */ + int id_unit; /* unit number */ + int id_flags; /* flags */ + int id_scsiid; /* scsi id if needed */ + int id_alive; /* device is present */ +#define RI_FAST 1 /* fast interrupt handler */ + u_int id_ri_flags; /* flags for register_intr() */ + int id_reconfig; /* hot eject device support (such as PCMCIA) */ + int id_enabled; /* is device enabled */ + int id_conflicts; /* we're allowed to conflict with things */ + struct isa_device *id_next; /* used in isa_devlist in userconfig() */ +}; +</code> + +<!-- XXX add stuff here --> +<sect3> <tt/struct isa_driver/ Structure + +<p> +This structure is defined in ``/usr/src/sys/i386/isa/isa_device.h''. +These are required on a per-driver basis. The definition is: +<code> +struct isa_driver { + int (*probe) __P((struct isa_device *idp)); + /* test whether device is present */ + int (*attach) __P((struct isa_device *idp)); + /* setup driver for a device */ + char *name; /* device name */ + int sensitive_hw; /* true if other probes confuse us */ +}; +</code> + +This is the structure used by the probe/attach code to detect and +initialize your device. The <tt/probe/ member is a pointer to your +device probe function; the <tt/attach/ member is a pointer to your +attach function. The <tt/name/ member is a character pointer to the +two or three letter name for your driver. This is the name reported +during the probe/attach process (and probably also in lsdev(8)). The +<tt/sensitive_hw/ member is a flag which helps the probe code +determine probing order. + +A typical instantiation is: +<code> +struct isa_driver mcddriver = { mcd_probe, mcd_attach, "mcd" }; +</code> + +<sect2> Entry Points + +<sect3> probe() +<p> +probe() takes a <tt/struct isa_device/ pointer as an argument and returns +an int. The return value is ``zero'' or ``non-zero'' as to the absence +or presence of your device. This entry point may (and probably should) +be declared as <tt/static/ because it is accessed via the <tt/probe/ member +of the <tt/struct isa_driver/ structure. This function is intended +to detect the presence of your device only; it should not do any +configuration of the device itself. + +<sect3> attach() +<p> +attach() also takes a <tt/struct isa_device/ pointer as an argument and +returns an int. The return value is also ``zero'' or ``non-zero'' indicating +whether or not the attach was successful. This function is intended +to do any special initialization of the device as well as confirm that +the device is usable. It too should be declared <tt/static/ because +it is accessed through the <tt/attach/ member of the <tt/isa_driver/ +structure. + +<sect2> Header Files + +<sect1> EISA -- Extended Industry Standard Architecture + +<sect2> Data Structures + +<p> <tt/struct eisa_dev/ Structure +<p> <tt/struct isa_driver/ Structure + +<sect2> Entry Points + +<sect3> probe() +<p> Described in the ISA device section. + +<sect3> attach() +<p> Described in the ISA device section. + +<sect2> Header Files + +<sect1> PCI -- Peripheral Computer Interconnect +<sect2> Data Structures + +<p> <tt/struct pci_device/ Structure + + name: The short device name. + + probe: Checks if the driver can support a device + with this type. The tag may be used to get + more info with pci_read_conf(). See below. + It returns a string with the device's name, + or a NULL pointer, if the driver cannot + support this device. + + attach: Allocate a control structure and prepare + it. This function may use the PCI mapping + functions. See below. + (configuration id) or type. + + count: A pointer to a unit counter. + It's used by the PCI configurator to + allocate unit numbers. + +<sect2> Entry Points + +<sect3> probe() + +<sect3> attach() + +<sect3> shutdown() + +<sect2> Header Files + +<sect1> SCSI -- Small Computer Systems Interface +<sect2> Data Structures + +<p> <tt/struct scsi_adapter/ Structure +<p> <tt/struct scsi_device/ Structure +<p> <tt/struct scsi_ctlr_config/ Structure +<p> <tt/struct scsi_device_config/ Structure +<p> <tt/struct scsi_link/ Structure + +<sect2> Entry Points +<sect3> attach() +<sect3> init() + +<sect2> Header Files + +<sect1> PCCARD (PCMCIA) +<sect2> Data Structures +<p> <tt/struct slot_cont/ Structure +<p> <tt/struct pccard_drv/ Structure +<p> <tt/struct pccard_dev/ Structure +<p> <tt/struct slot/ Structure + +<sect2> Entry Points +<sect3> handler() +<sect3> unload() +<sect3> suspend() +<sect3> init() + +<sect2> Header Files + a. <pccard/slot.h> + +<sect> Linking Into the Kernel. + +<p> +In FreeBSD, support for the ISA and EISA busses is i386 specific. +While FreeBSD itself is presently available on the i386 platform, +some effort has been made to make the PCI, PCCARD, and SCSI code +portable. The ISA and EISA specific code resides in +/usr/src/sys/i386/isa and /usr/src/sys/i386/eisa respectively. +The machine independent PCI, PCCARD, and SCSI code reside in +/usr/src/sys/{pci,pccard,scsi}. The i386 specific code for these +reside in /usr/src/sys/i386/{pci,pccard,scsi}. + +<p> +In FreeBSD, a device driver can be either binary or source. There is +no ``official'' place for binary drivers to reside. BSD/OS uses +something like sys/i386/OBJ. Since most drivers are distributed +in source, the following discussion refers to a source driver. +Binary only drivers are sometimes provided by hardware vendors +who wish to maintain the source as proprietary. + +<p> +A typical driver has the source code in one c-file, say dev.c. The +driver also can have some include files; devreg.h typically contains +public device register declarations, macros, and other driver +specific declarations. Some drivers call this devvar.h instead. +Some drivers, such as the dgb (for the Digiboard PC/Xe), +require microcode to be loaded onto the board. For the dgb driver +the microcode is compiled and dumped into a header file ala file2c(1). + +<p> +If the driver has data structures and ioctl's which are specific to +the driver/device, and need to be accessible from user-space, they +should be put in a separate include file which will reside in +/usr/include/machine/ (some of these reside in /usr/include/sys/). +These are typically named something like ioctl_dev.h or devio.h. + +<p> +If a driver is being written which, from user space is +identical to a device which already exists, care should be taken to +use the same ioctl interface and data structures. For example, from +user space, a SCSI cdrom drive should be identical to an IDE cdrom +drive; or a serial line on an intelligent multiport card (Digiboard, +Cyclades, ...) should be identical to the sio devices. These devices +have a fairly well defined interface which should be used. + +<p> +There are two methods for linking a driver into the kernel, static and +the LKM model. The first method is fairly standard across the +*BSD family. The other method was originally developed by Sun +(I believe), and has been implemented into BSD using the Sun model. +I don't believe that the current implementation uses any Sun code. + +<sect1> Standard Model + +<p> +The steps required to add your driver to the standard FreeBSD kernel are +<itemize> +<item> Add to the driver list +<item> Add an entry to the [bc]devsw +<item> Add the driver entry to the kernel config file +<item> config(8), compile, and install the kernel +<item> make required nodes. +<item> reboot. +</itemize> + +<sect2> Adding to the driver list. +<p> +The standard model for adding a device driver to the Berkeley kernel +is to add your driver to the list of known devices. This list is +dependant on the cpu architecture. If the device is not i386 specific +(PCCARD, PCI, SCSI), the file is in ``/usr/src/sys/conf/files''. +If the device is i386 specific, use ``/usr/src/sys/i386/conf/files.i386''. +A typical line looks like: +<tscreen><code> +i386/isa/joy.c optional joy device-driver +</code></tscreen> + +The first field is the pathname of the driver module relative to +/usr/src/sys. For the case of a binary driver the path would be +something like ``i386/OBJ/joy.o''. + +The second field tells config(8) that this is an optional driver. Some +devices are required for the kernel to even be built. + +The third field is the name of the device. + +The fourth field tells config that it's a device driver (as opposed to +just optional). This causes config to create entries for the device +in some structures in /usr/src/sys/compile/KERNEL/ioconf.c. + +It is also possible to create a file +``/usr/src/sys/i386/conf/files.KERNEL'' whose contents will override +the default files.i386, but only for the kernel ``KERNEL''. + +<sect2>Make room in conf.c +<p> +Now you must edit ``/usr/src/sys/i386/i386/conf.c'' to make an entry +for your driver. Somewhere near the top, you need to declare your +entry points. The entry for the joystick driver is: +<code> +#include "joy.h" +#if NJOY > 0 +d_open_t joyopen; +d_close_t joyclose; +d_rdwr_t joyread; +d_ioctl_t joyioctl; +#else +#define joyopen nxopen +#define joyclose nxclose +#define joyread nxread +#define joyioctl nxioctl +#endif +</code> + +This either defines your entry points, or null entry points which +will return ENXIO when called (the #else clause). + +The include file ``joy.h'' is automatically generated by config(8) when +the kernel build tree is created. This usually has only one line like: +<code> +#define NJOY 1 +</code> +or +<code> +#define NJOY 0 +</code> +which defines the number of your devices in your kernel. + +You must additionally add a slot to either cdevsw[&rsqb, or to +bdevsw[&rsqb, depending on whether it is a character device or +a block device, or both if it is a block device with a raw interface. +The entry for the joystick driver is: + +<code> +/* open, close, read, write, ioctl, stop, reset, ttys, select, mmap, strat */ +struct cdevsw cdevsw[] = +{ + ... + { joyopen, joyclose, joyread, nowrite, /*51*/ + joyioctl, nostop, nullreset, nodevtotty,/*joystick */ + seltrue, nommap, NULL}, + ... +} +</code> + +Order is what determines the major number of your device. Which is why +there will always be an entry for your driver, either null entry +points, or actual entry points. It is probably worth noting that this +is significantly different from SCO and other system V derivatives, +where any device can (in theory) have any major number. This is +largely a convenience on FreeBSD, due to the way device nodes are +created. More on this later. + +<sect2>Adding your device to the config file. +<p> +This is simply adding a line describing your device. +The joystick description line is: +<verb> +device joy0 at isa? port "IO_GAME" +</verb> +This says we have a device called ``joy0'' on the isa bus using +io-port ``IO_GAME'' (IO_GAME is a macro defined in +/usr/src/sys/i386/isa/isa.h). + +A slightly more complicated entry is for the ``ix'' driver: +<verb> +device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixintr +</verb> +This says that we have a device called `ix0' on the ISA bus. It uses +io-port 0x300. It's interrupt will be masked with other devices in +the network class. It uses interrupt 10. It uses +32k of shared memory at physical address 0xd0000. It also defines +it's interrupt handler to be ``ixintr()'' + +<sect2>config(8) the kernel. +<p> +Now with our config file in hand, we can create a kernel compile directory. +This is done by simply typing: +<verb> +# config KERNEL +</verb> +where KERNEL is the name of your config file. Config creates a +compile tree for you kernel in /usr/src/sys/compile/KERNEL. It +creates the Makefile, some .c files, and some .h files with macros +defining the number of each device in your kernel. + +Now you can go to the compile directory and build. Each time you run +config, your previous build tree will be removed, unless you config +with a -n. If you have config'ed and compiled a GENERIC kernel, you can +``make links'' to avoid compiling a few files on each iteration. I typically +run +<verb> +# make depend links all +</verb> +followed by a ``make install'' when the kernel is done to my liking. + +<sect2>Making device nodes. +<p> +On FreeBSD, you are responsible for making your own device nodes. The +major number of your device is determined by the slot number in the +device switch. Minor number is driver dependent, of course. You can +either run the mknod's from the command line, or add a section to +/dev/MAKEDEV.local, or even /dev/MAKEDEV to do the work. I sometimes +create a MAKEDEV.dev script that can be run stand-alone or pasted +into /dev/MAKEDEV.local + +<sect2>Reboot. +<p> +This is the easy part. There are a number of ways to do this, reboot, +fastboot, shutdown -r, cycle the power, etc. Upon bootup you should +see your XXprobe() called, and if all is successful, your XXattach() +too. + +<sect1> Loadable Kernel Module (LKM) + +<p> +There are really no defined procedures for writing an LKM driver. The +following is my own conception after experimenting with the LKM device +interface and looking at the standard device driver model, this is one +way of adding an LKM interface to an existing driver without touching +the original driver source (or binary). It is recommended though, +that if you plan to release source to your driver, the LKM specific +parts should be part of the driver itself, conditionally compiled +on the LKM macro (i.e. #ifdef LKM). + +This section will focus on writing the LKM specific part of the driver. We +will assume that we have written a driver which will drop into the standard +device driver model, which we would now like to implement as an LKM. We will +use the pcaudio driver as a sample driver, and develop an LKM front-end. The +source and makefile for the pcaudio LKM, ``pcaudio_lkm.c'' and ``Makefile'', +should be placed in /usr/src/lkm/pcaudio. What follows is a breakdown of +pcaudio_lkm.c. + +Lines 17 - 26 + + -- This includes the file ``pca.h'' and conditionally compiles the rest +of the LKM on whether or not we have a pcaudio device defined. This +mimics the behavior of config. In a standard device driver, config(8) +generates the pca.h file from the number pca devices in the config file. +<code> + 17 /* + 18 * figure out how many devices we have.. + 19 */ + 20 + 21 #include "pca.h" + 22 + 23 /* + 24 * if we have at least one ... + 25 */ + 26 #if NPCA > 0 +</code> + +Lines 27 - 37 + + -- Includes required files from various include directories. +<code> + 27 #include <sys/param.h> + 28 #include <sys/systm.h> + 29 #include <sys/exec.h> + 30 #include <sys/conf.h> + 31 #include <sys/sysent.h> + 32 #include <sys/lkm.h> + 33 #include <sys/errno.h> + 34 #include <i386/isa/isa_device.h> + 35 #include <i386/isa/isa.h> + 36 + 37 +</code> + +Lines 38 - 51 + + -- Declares the device driver entry points as external. +<code> + 38 /* + 39 * declare your entry points as externs + 40 */ + 41 + 42 extern int pcaprobe(struct isa_device *); + 43 extern int pcaattach(struct isa_device *); + 44 extern int pcaopen(dev_t, int, int, struct proc *); + 45 extern int pcaclose(dev_t, int, int, struct proc *); + 46 extern int pcawrite(dev_t, struct uio *, int); + 47 extern int pcaioctl(dev_t, int, caddr_t); + 48 extern int pcaselect(dev_t, int, struct proc *); + 49 extern void pcaintr(struct clockframe *); + 50 extern struct isa_driver pcadriver; + 51 +</code> + +Lines 52 - 70 + + -- This is creates the device switch entry table for your driver. +This table gets swapped wholesale into the system device switch at +the location specified by your major number. In the standard model, +these are in /usr/src/sys/i386/i386/conf.c. NOTE: you cannot pick a +device major number higher than what exists in conf.c, for example at +present, conf.c rev 1.85, there are 67 slots for character devices, +you cannot use a (character) major device number 67 or greater, +without first reserving space in conf.c. +<code> + 52 /* + 53 * build your device switch entry table + 54 */ + 55 + 56 static struct cdevsw pcacdevsw = { + 57 (d_open_t *) pcaopen, /* open */ + 58 (d_close_t *) pcaclose, /* close */ + 59 (d_rdwr_t *) enodev, /* read */ + 60 (d_rdwr_t *) pcawrite, /* write */ + 61 (d_ioctl_t *) pcaioctl, /* ioctl */ + 62 (d_stop_t *) enodev, /* stop?? */ + 63 (d_reset_t *) enodev, /* reset */ + 64 (d_ttycv_t *) enodev, /* ttys */ + 65 (d_select_t *) pcaselect, /* select */ + 66 (d_mmap_t *) enodev, /* mmap */ + 67 (d_strategy_t *) enodev /* strategy */ + 68 }; + 69 + 70 +</code> + +Lines 71 - 131 + + -- This section is analogous to the config file declaration of your +device. The members of the isa_device structure are filled in by what +is known about your device, I/O port, shared memory segment, etc. We +will probably never have a need for two pcaudio devices in the kernel, +but this example shows how multiple devices can be supported. +<code> + 71 /* + 72 * this lkm arbitrarily supports two + 73 * instantiations of the pc-audio device. + 74 * + 75 * this is for illustration purposes + 76 * only, it doesn't make much sense + 77 * to have two of these beasts... + 78 */ + 79 + 80 + 81 /* + 82 * these have a direct correlation to the + 83 * config file entries... + 84 */ + 85 struct isa_device pcadev[NPCA] = { + 86 { + 87 11, /* device id */ + 88 &pcadriver, /* driver pointer */ + 89 IO_TIMER1, /* base io address */ + 90 -1, /* interrupt */ + 91 -1, /* dma channel */ + 92 (caddr_t)-1, /* physical io memory */ + 93 0, /* size of io memory */ + 94 pcaintr , /* interrupt interface */ + 95 0, /* unit number */ + 96 0, /* flags */ + 97 0, /* scsi id */ + 98 0, /* is alive */ + 99 0, /* flags for register_intr */ + 100 0, /* hot eject device support */ + 101 1 /* is device enabled */ + 102 }, + 103 #if NPCA >1 + 104 { + 105 + 106 /* + 107 * these are all zeros, because it doesn't make + 108 * much sense to be here + 109 * but it may make sense for your device + 110 */ + 111 + 112 0, /* device id */ + 113 &pcadriver, /* driver pointer */ + 114 0, /* base io address */ + 115 -1, /* interrupt */ + 116 -1, /* dma channel */ + 117 -1, /* physical io memory */ + 118 0, /* size of io memory */ + 119 NULL, /* interrupt interface */ + 120 1, /* unit number */ + 121 0, /* flags */ + 122 0, /* scsi id */ + 123 0, /* is alive */ + 124 0, /* flags for register_intr */ + 125 0, /* hot eject device support */ + 126 1 /* is device enabled */ + 127 }, + 128 #endif + 129 + 130 }; + 131 +</code> + +Lines 132 - 139 + + -- This calls the C-preprocessor macro MOD_DEV, which sets up an LKM device +driver, as opposed to an LKM filesystem, or an LKM system call. +<code> + 132 /* + 133 * this macro maps to a funtion which + 134 * sets the LKM up for a driver + 135 * as opposed to a filesystem, systemcall, or misc + 136 * LKM. + 137 */ + 138 MOD_DEV("pcaudio_mod", LM_DT_CHAR, 24, &pcacdevsw); + 139 +</code> + +Lines 140 - 168 + + -- This is the function which will be called when the driver is +loaded. This function tries to work like sys/i386/isa/isa.c +which does the probe/attach calls for a driver at boot time. The +biggest trick here is that it maps the physical address of the shared +memory segment, which is specified in the isa_device structure to a +kernel virtual address. Normally the physical address is put in the +config file which builds the isa_device structures in +/usr/src/sys/compile/KERNEL/ioconf.c. The probe/attach sequence of +/usr/src/sys/isa/isa.c translates the physical address to a virtual +one so that in your probe/attach routines you can do things like +<verb> +(int *)id->id_maddr = something; +</verb> +and just refer to the shared memory segment via pointers. +<code> + 140 /* + 141 * this function is called when the module is + 142 * loaded; it tries to mimic the behavior + 143 * of the standard probe/attach stuff from + 144 * isa.c + 145 */ + 146 int + 147 pcaload(){ + 148 int i; + 149 uprintf("PC Audio Driver Loaded\n"); + 150 for (i=0; i<NPCA; i++){ + 151 /* + 152 * this maps the shared memory address + 153 * from physical to virtual, to be + 154 * consistant with the way + 155 * /usr/src/sys/i386/isa.c handles it. + 156 */ + 157 pcadev[i].id_maddr -=0xa0000; + 158 pcadev[i].id_maddr += atdevbase; + 159 if ((*pcadriver.probe)(pcadev+i)) { + 160 (*(pcadriver.attach))(pcadev+i); + 161 } else { + 162 uprintf("PC Audio Probe Failed\n"); + 163 return(1); + 164 } + 165 } + 166 return 0; + 167 } + 168 +</code> + +Lines 169 - 179 + + -- This is the function called when your driver is unloaded; it just displays +a message to that effect. +<code> + 169 /* + 170 * this function is called + 171 * when the module is unloaded + 172 */ + 173 + 174 int + 175 pcaunload(){ + 176 uprintf("PC Audio Driver Unloaded\n"); + 177 return 0; + 178 } + 179 +</code> + +Lines 180 - 190 + + -- This is the entry point which is specified on the command line of the +modload. By convention it is named <dev>_mod. This is how it is +defined in bsd.lkm.mk, the makefile which builds the LKM. If you name your +module following this convention, you can do ``make load'' and ``make +unload'' from /usr/src/lkm/pcaudio. <p> +Note: this has gone through <em/many/ revisions from release 2.0 to 2.1. +It may or may not be possible to write a module which is portable across +all three releases. <p> +<code> + 180 /* + 181 * this is the entry point specified + 182 * on the modload command line + 183 */ + 184 + 185 int + 186 pcaudio_mod(struct lkm_table *lkmtp, int cmd, int ver) + 187 { + 188 DISPATCH(lkmtp, cmd, ver, pcaload, pcaunload, nosys); + 189 } + 190 + 191 #endif /* NICP > 0 */ +</code> + +<sect1> Device Type Idiosyncrasies +<sect2> Character +<sect2> Block +<sect2> Network +<sect2> Line Discipline + +<sect1> Bus Type Idiosyncrasies +<sect2> ISA +<sect2> EISA +<sect2> PCI +<sect2> SCSI +<sect2> PCCARD + +<sect> Kernel Support + +<sect1> Data Structures + +<sect2> <tt/struct kern_devconf/ Structure +<p> + +This structure contains some information about the state of the device +and driver. It is defined in /usr/src/sys/sys/devconf.h as: +<code> +struct devconf { + char dc_name[MAXDEVNAME]; /* name */ + char dc_descr[MAXDEVDESCR]; /* description */ + int dc_unit; /* unit number */ + int dc_number; /* unique id */ + char dc_pname[MAXDEVNAME]; /* name of the parent device */ + int dc_punit; /* unit number of the parent */ + int dc_pnumber; /* unique id of the parent */ + struct machdep_devconf dc_md; /* machine-dependent stuff */ + enum dc_state dc_state; /* state of the device (see above) */ + enum dc_class dc_class; /* type of device (see above) */ + size_t dc_datalen; /* length of data */ + char dc_data[1]; /* variable-length data */ +}; +</code> + +<sect2> <tt/struct proc/ Structure +<p> + +This structure contains all the information about a process. +It is defined in /usr/src/sys/sys/proc.h: +<code> +/* + * Description of a process. + * + * This structure contains the information needed to manage a thread of + * control, known in UN*X as a process; it has references to substructures + * containing descriptions of things that the process uses, but may share + * with related processes. The process structure and the substructures + * are always addressable except for those marked "(PROC ONLY)" below, + * which might be addressable only on a processor on which the process + * is running. + */ +struct proc { + struct proc *p_forw; /* Doubly-linked run/sleep queue. */ + struct proc *p_back; + struct proc *p_next; /* Linked list of active procs */ + struct proc **p_prev; /* and zombies. */ + + /* substructures: */ + struct pcred *p_cred; /* Process owner's identity. */ + struct filedesc *p_fd; /* Ptr to open files structure. */ + struct pstats *p_stats; /* Accounting/statistics (PROC ONLY). */ struct plimit *p_limit; /* Process limits. */ + struct vmspace *p_vmspace; /* Address space. */ + struct sigacts *p_sigacts; /* Signal actions, state (PROC ONLY). */ + +#define p_ucred p_cred->pc_ucred +#define p_rlimit p_limit->pl_rlimit + + int p_flag; /* P_* flags. */ + char p_stat; /* S* process status. */ + char p_pad1[3]; + + pid_t p_pid; /* Process identifier. */ + struct proc *p_hash; /* Hashed based on p_pid for kill+exit+... */ + struct proc *p_pgrpnxt; /* Pointer to next process in process group. */ + struct proc *p_pptr; /* Pointer to process structure of parent. */ + struct proc *p_osptr; /* Pointer to older sibling processes. */ + +/* The following fields are all zeroed upon creation in fork. */ +#define p_startzero p_ysptr + struct proc *p_ysptr; /* Pointer to younger siblings. */ + struct proc *p_cptr; /* Pointer to youngest living child. */ + pid_t p_oppid; /* Save parent pid during ptrace. XXX */ + int p_dupfd; /* Sideways return value from fdopen. XXX */ + + /* scheduling */ + u_int p_estcpu; /* Time averaged value of p_cpticks. */ + int p_cpticks; /* Ticks of cpu time. */ + fixpt_t p_pctcpu; /* %cpu for this process during p_swtime */ + void *p_wchan; /* Sleep address. */ + char *p_wmesg; /* Reason for sleep. */ + u_int p_swtime; /* Time swapped in or out. */ + u_int p_slptime; /* Time since last blocked. */ + + struct itimerval p_realtimer; /* Alarm timer. */ + struct timeval p_rtime; /* Real time. */ + u_quad_t p_uticks; /* Statclock hits in user mode. */ + u_quad_t p_sticks; /* Statclock hits in system mode. */ + u_quad_t p_iticks; /* Statclock hits processing intr. */ + + int p_traceflag; /* Kernel trace points. */ + struct vnode *p_tracep; /* Trace to vnode. */ + + int p_siglist; /* Signals arrived but not delivered. */ + + struct vnode *p_textvp; /* Vnode of executable. */ + + char p_lock; /* Process lock (prevent swap) count. */ + char p_pad2[3]; /* alignment */ + +/* End area that is zeroed on creation. */ +#define p_endzero p_startcopy + +/* The following fields are all copied upon creation in fork. */ +#define p_startcopy p_sigmask + + sigset_t p_sigmask; /* Current signal mask. */ + sigset_t p_sigignore; /* Signals being ignored. */ + sigset_t p_sigcatch; /* Signals being caught by user. */ + + u_char p_priority; /* Process priority. */ + u_char p_usrpri; /* User-priority based on p_cpu and p_nice. */ + char p_nice; /* Process "nice" value. */ + char p_comm[MAXCOMLEN+1]; + + struct pgrp *p_pgrp; /* Pointer to process group. */ + + struct sysentvec *p_sysent; /* System call dispatch information. */ + + struct rtprio p_rtprio; /* Realtime priority. */ +/* End area that is copied on creation. */ +#define p_endcopy p_addr + struct user *p_addr; /* Kernel virtual addr of u-area (PROC ONLY). */ + struct mdproc p_md; /* Any machine-dependent fields. */ + + u_short p_xstat; /* Exit status for wait; also stop signal. */ + u_short p_acflag; /* Accounting flags. */ + struct rusage *p_ru; /* Exit information. XXX */ +}; +</code> + +<sect2> <tt/struct buf/ Structure +<p> +The <tt/struct buf/ structure is used to interface with the buffer cache. +It is defined in /usr/src/sys/sys/buf.h: + +<code> +/* + * The buffer header describes an I/O operation in the kernel. + */ +struct buf { + LIST_ENTRY(buf) b_hash; /* Hash chain. */ + LIST_ENTRY(buf) b_vnbufs; /* Buffer's associated vnode. */ + TAILQ_ENTRY(buf) b_freelist; /* Free list position if not active. */ + struct buf *b_actf, **b_actb; /* Device driver queue when active. */ + struct proc *b_proc; /* Associated proc; NULL if kernel. */ + volatile long b_flags; /* B_* flags. */ + int b_qindex; /* buffer queue index */ + int b_error; /* Errno value. */ + long b_bufsize; /* Allocated buffer size. */ + long b_bcount; /* Valid bytes in buffer. */ + long b_resid; /* Remaining I/O. */ + dev_t b_dev; /* Device associated with buffer. */ + struct { + caddr_t b_addr; /* Memory, superblocks, indirect etc. */ + } b_un; + void *b_saveaddr; /* Original b_addr for physio. */ + daddr_t b_lblkno; /* Logical block number. */ + daddr_t b_blkno; /* Underlying physical block number. */ + /* Function to call upon completion. */ + void (*b_iodone) __P((struct buf *)); + /* For nested b_iodone's. */ + struct iodone_chain *b_iodone_chain; + struct vnode *b_vp; /* Device vnode. */ + int b_pfcent; /* Center page when swapping cluster. */ + int b_dirtyoff; /* Offset in buffer of dirty region. */ + int b_dirtyend; /* Offset of end of dirty region. */ + struct ucred *b_rcred; /* Read credentials reference. */ + struct ucred *b_wcred; /* Write credentials reference. */ + int b_validoff; /* Offset in buffer of valid region. */ + int b_validend; /* Offset of end of valid region. */ + daddr_t b_pblkno; /* physical block number */ + caddr_t b_savekva; /* saved kva for transfer while bouncing + */ + void *b_driver1; /* for private use by the driver */ + void *b_driver2; /* for private use by the driver */ + void *b_spc; + struct vm_page *b_pages[(MAXPHYS + PAGE_SIZE - 1)/PAGE_SIZE]; + int b_npages; +}; +</code> + +<sect2> <tt/struct uio/ Structure +<p> +This structure is used for moving data between the kernel and user spaces +through read() and write() system calls. It is defined in +/usr/src/sys/sys/uio.h: +<code> +struct uio { + struct iovec *uio_iov; + int uio_iovcnt; + off_t uio_offset; + int uio_resid; + enum uio_seg uio_segflg; + enum uio_rw uio_rw; + struct proc *uio_procp; +}; + +</code> + +<sect1> Functions +lots of 'em + +<sect> References. + +<p> FreeBSD Kernel Sources http://www.freebsd.org +<p> NetBSD Kernel Sources http://www.netbsd.org +<p> Writing Device Drivers: Tutorial and Reference; +Tim Burke, Mark A. Parenti, Al, Wojtas; +Digital Press, ISBN 1-55558-141-2. + +<p> Writing A Unix Device Driver; +Janet I. Egan, Thomas J. Teixeira; +John Wiley & Sons, ISBN 0-471-62859-X. + +<p> Writing Device Drivers for SCO Unix; +Peter Kettle; + +</article> diff --git a/data/tutorials/devel/Makefile b/data/tutorials/devel/Makefile new file mode 100644 index 0000000000..1e48dd92a3 --- /dev/null +++ b/data/tutorials/devel/Makefile @@ -0,0 +1,6 @@ +DOC= devel +SRCS= devel.sgml +SGMLOPTS= -ssi + +.include <bsd.sgml.mk> + diff --git a/data/tutorials/devel/devel.sgml b/data/tutorials/devel/devel.sgml new file mode 100644 index 0000000000..e9d8fbf560 --- /dev/null +++ b/data/tutorials/devel/devel.sgml @@ -0,0 +1,1738 @@ +<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN"> + +<!-- + ++++++++++++++++++++++++++++++++++++++++++++++++++ + ++ file: /home/james/docs/devel.sgml + ++ + ++ Copyright James Raynard, Thursday 30th May 1996 + ++ + ++ Sgml doc for programming under FreeBSD. + --> + +<article> + +<title>A User's Guide to FreeBSD Programming Tools +<author>James Raynard, <tt /jraynard@freebsd.org/ +<date>30th May 1996 + +<abstract> + +This document is an introduction to using some of the programming +tools supplied with FreeBSD, although much of it will be applicable to +many other versions of Unix. It does <it /not/ attempt to describe +coding in any detail. Most of the document assumes little or no +previous programming knowledge, although it is hoped that most +programmers will find something of value in it + +</abstract> + +<sect><heading>Introduction</heading> +<p> + +FreeBSD offers an excellent development environment. Compilers for C, +C++, and Fortran and an assembler come with the basic system, not to +mention a Perl interpreter and classic Unix tools such as sed and awk. +If that isn't enough, there are many more compilers and interpreters +in the Ports collection. FreeBSD is very compatible with standards +such as POSIX and ANSI C, as well with its own BSD heritage, so it is +possible to write applications that will compile and run with little +or no modification on a wide range of platforms. +<p> +However, all this power can be rather overwhelming at first if you've +never written programs on a Unix platform before. This document aims +to help you get up and running, without getting too deeply into more +advanced topics. The intention is that this document should give you +enough of the basics to be able to make some sense of the +documentation. +<p> +Most of the document requires little or no knowledge of programming, +although it does assume a basic competence with using Unix and a +willingness to learn! + +<sect><heading>Introduction to Programming</heading> +<p> +A program is a set of instructions that tell the computer to do +various things; sometimes the instruction it has to perform depends on +what happened when it performed a previous instruction. This section +gives an overview of the two main ways in which you can give these +instructions, or ``commands'' as they're usually called. One way uses +an interpreter, the other a compiler. As human languages are too +difficult for a computer to understand in an unambiguous way, commands +are usually written in one or other languages specially designed for +the purpose. + +<sect1><heading>Interpreters</heading> +<p> +With an interpreter, the language comes as an environment, where you +type in commands at a prompt and the environment executes them for +you. For more complicated programs, you can type the commands into a +file and get the interpreter to load the file and execute the commands +in it. If anything goes wrong, many interpreters will drop you into a +debugger to help you track down the problem. +<P> +The advantage of this is that you can see the results of your commands +immediately, and mistakes can be corrected readily. The biggest +disadvantage comes when you want to share your programs with +someone. They must have the same interpreter (or you must have some +way of giving it to them) and they need to understand how to use +it. Also users may not appreciate being thrown into a debugger if they +press the wrong key! From a performance point of view, interpreters +can use up a lot of memory, and generally do not generate code as +efficiently as compilers. +<p> +In my opinion, interpreted languages are the best way to start if you +haven't done any programming before. This kind of environment is +typically found with languages like Lisp, Smalltalk, Perl and +Basic. It could also be argued that the Unix shell (sh, csh) is itself +an interpreter, and many people do in fact write shell `scripts' to +help with various ``housekeeping'' tasks on their machine. Indeed, +part of the original Unix philosophy was to provide lots of small +utility programs that could be linked together in shell scripts to +perform useful tasks. +<p> +<sect1><heading>Interpreters available with FreeBSD</heading> +<p> +Here is a list of interpreters that are available as <htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/" name="FreeBSD +packages">, with a brief discussion of some of the more popular +interpreted languages. +<p> +To get one of these packages, all you need to do is to click on the +hotlink for the package, then run + +<tscreen><verb> + pkg_add <package name> +</verb></tscreen> + +as root. Obviously, you'll need to have a fully-functional FreeBSD +2.1.0 system for the package to work! + +<descrip> +<tag>Basic</tag> + +Short for Beginner's All-purpose Symbolic Instruction Code. Developed +in the 1950s for teaching University students to program and provided +with every self-respecting personal computer in the 1980s, BASIC has +been the first programming language for many programmers. It's also +the foundation for Visual Basic. + +The <htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/bwbasic-2.10.tgz" +name="Bywater Basic Interpreter"> and the <htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/pbasic-2.0.tgz" +name="Phil Cockroft's Basic Interpreter"> (formerly Rabbit Basic) are +available as FreeBSD <htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/" name="FreeBSD +packages"> + +<tag>Lisp</tag> + +A language that was developed in the late 1950s as an alternative to +the ``number-crunching'' languages that were popular at the time. +Instead of being based on numbers, Lisp is based on `lists'; in fact +the name is short for "List Processing". Very popular in AI +(Artificial Intelligence) circles. + +Lisp is an extremely powerful and sophisticated language, but can be +rather large and unwieldy. + +FreeBSD has <htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/gcl-2.0.tgz" name="GNU +Common Lisp"> available as a package. + +<tag>Perl</tag> + +Very popular with system administrators for writing scripts; also +often used on World Wide Web servers for writing CGI scripts. + +Version 4, which is probably still the most widely-used version, comes +with FreeBSD; the newer +<htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/perl-5.001.tgz" +name="Perl Version 5"> is available as a package. + +<tag>Scheme</tag> + +A dialect of Lisp that is rather more compact and cleaner than Common +Lisp. Popular in Universities as it's simple enough to teach to +undergraduates as a first language, while it has a high enough level +of abstraction to be used in research work. + +FreeBSD has packages of the +<htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/elk-3.0.tgz" +name="Elk Scheme Interpreter">, the +<htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/mit-scheme-7.3.tgz" +name="MIT Scheme Interpreter"> and the +<htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/scm-4e1.tgz" +name="SCM Scheme Interpreter">. +<!-- +<tag>TCL and Tk</tag> + +Programming with the X windowing system can best be described as +rather character-forming. As someone once said, if they designed cars +the way X was designed, each car would have five steering wheels, all +following completely different conventions, but you can use the +radio-cassette player to change gears, which is a really useful +feature when you think about it. Or perhaps not. +<p> +Fortunately, it doesn't have to be like that. A number of people have +written "toolkits" for X, where all the interaction with X is hidden +inside toolkit routines and you can just say, in effect, ``pop up a +window and draw a line from point A to point B''. Many of these are +`libraries' that have to be called from inside a C program, but one of +the best known toolkits, John Ousterhout's Tk, provides a +straightforward way to write GUI programs using a scripted +language. And by one of those remarkable coincidences, he also happens +to have written an embeddable language, TCL (Tool Command Language) +which is very suitable for the purpose, although it is possible to use +other interpreted languages such as Perl or Scheme to send commands to +Tk. + +FreeBSD has a <htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/tcl-7.4.2.tgz" +name="Tool Command Language"> package. +--> +<tag>Icon</tag> + +<htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/icon-9.0.tgz" +name="The Icon Programming Language">. + +<tag>Logo</tag> + +<htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/ucblogo-3.3.tgz" +name="Brian Harvey's LOGO Interpreter">. + +<tag>Python</tag> +<htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/lang/python-1.2" +name="The Python Object-Oriented Programming Language"> + +</descrip> + +<sect1><heading>Compilers</heading> +<p> +Compilers are rather different. First of all, you write your code in a +file (or files) using an editor. You then run the compiler and see if +it accepts your program. If it didn't compile, grit your teeth and go +back to the editor; if it did compile and gave you a program, you can +run it either at a shell command prompt or in a debugger to see if it +works properly. (If you run it in the shell, you may get a core dump). +<p> +Obviously, this is not quite as direct as using an interpreter. +However it allows you to do a lot of things which are very difficult +or even impossible with an interpreter, such as writing code which +interacts with the operating system - or even writing your own +operating system! It's also useful if you need to write very efficient +code, as the compiler can take its time and optimise the code, which +wouldn't be acceptable in an interpreter. And distributing a program +written for a compiler is usually more straightforward than one +written for an interpreter - you can just give them a copy of the +executable (assuming they have the same operating system as you). +<p> +Compiled languages include Pascal, C and C++. C and C++ are rather +unforgiving languages, and best suited to more experienced +programmers; Pascal, on the other hand, was designed as an educational +language, and is quite a good language to start with. Unfortunately, +FreeBSD doesn't have any Pascal support, except for a Pascal-to-C +converter in the ports. +<p> +As the edit-compile-run-debug cycle is rather tedious when using +separate programs, many commercial compiler makers have produced +Integrated Development Environments (IDEs for short). FreeBSD doesn't +have an IDE as such; however it's possible to use Emacs for this +purpose. This is discussed under Emacs. + +<sect><heading>Compiling with cc</heading> +<p> +This section deals only with the GNU compiler for C and C++, since +that comes with the base FreeBSD system. It can be invoked by either +`cc' or `gcc'. The details of producing a program with an interpreter +vary considerably between interpreters, and are usually well covered +in the documentation and on-line help for the interpreter. +<p> +Once you've written your masterpiece, the next step is to convert it +into something that will (hopefully!) run on FreeBSD. This usually +involves several steps, each of which is done by a separate program. + +<enum> + +<item> Pre-process your source code to remove comments and do other +tricks like expanding `macros' in C. + +<item> Check the syntax of your code to see if you have obeyed the +rules of the language. If you haven't, it will complain! + +<item> Convert the source code into assembler - this is very close to +machine code, but still understandable by humans. Allegedly. (To be +strictly accurate, cc converts the source code into its own, +machine-independent p-code instead of assembler at this stage). + +<item> Convert the assembler into machine code - yep, we're talking +bits and bytes, ones and zeros here. + +<item> Check that you've used things like functions and global +variables in a consistent way (eg if you've called a non-existent +function, it'll complain). + +<item> If you're trying to produce an executable from several source +code files, work out how to fit them all together. + +<item> Work out how to produce something that the system's run-time +loader will be able to load into memory and run. + +<item> (Finally!) Write the executable on the file system. +</enum> + +The word ``compiling'' is often used to refer to just steps 1 to 4 - +the others are referred to as ``linking''. Sometimes step 1 is +referred to as ``pre-processing'' and steps 3-4 as ``assembling''. +<p> +Fortunately, almost all this detail is hidden from you, as cc is a +front end that manages calling all these programs with the right +arguments for you; simply typing + +<tscreen><verb> + cc foobar.c +</verb></tscreen> + +will cause foobar.c to be compiled by all the steps above. If you have +more than one file to compile, just do something like + +<tscreen><verb> + cc foo.c bar.c +</verb></tscreen> + +Note that the syntax checking is just that - checking the syntax. It +won't check for any logical mistakes you may have made, like putting +the program into an infinite loop, or using a bubble sort when you +meant to use a binary sort. {In case you didn't know, a +binary sort is an efficient way of sorting things into order and a +bubble sort isn't.} +<p> +There are lots and lots of options for cc, which are all in the man +page. Here are a few of the most important ones, with examples of how +to use them. + +<descrip> +<tag/-o/ + The output name of the file. If you don't use this option, cc will + produce an executable called `a.out' (the reasons for this are buried + in the mists of history). + + Example:- +<tscreen><verb> + cc foobar.c executable is a.out + cc -o foobar foobar.c executable is foobar +</verb></tscreen> + +<tag/-c/ + Just compile the file, don't link it. Useful for toy programs where + you just want to check the syntax, or if you're using a Make file. + + Example:- + +<tscreen><verb> + cc -c foobar.c +</verb></tscreen> + + This will produce an ``object file'' (not an executable) called + `foobar.o'. This can be linked together with other object files + into an executable. + +<tag/-g/ + + Create a debug version of the executable. This makes the compiler + put information into the executable about which line of which + source file corresponds to which function call. A debugger can use + this information to show the source code as you step through the + program, which is <it /very/ useful; the disadvantage is that all + this extra information makes the program much bigger. Normally, + you compile with -g while you're developing a program and then + compile a ``release version'' without -g when you're satisfied it + works properly. + + Example:- + +<tscreen><verb> + cc -g foobar.c +</verb></tscreen> + + This will produce a debug version of the program. (Note, we didn't use + the -o flag to specify the executable name, so we'll get an executable + called `a.out'. Producing a debug version called `foobar' is left as an + exercise for the reader!) + +<tag/-O/ + Create an optimised version of the executable. The compiler performs + various clever tricks to try and produce an executable that runs faster + than normal. You can add a number after the `O' to specify a higher + level of optimisation, but this often exposes bugs in the compiler's + optimiser. For instance, the version of cc that comes with the 2.1.0 + release of FreeBSD is known to produce bad code with the `-O2' + option in some circumstances. + + Optimisation is usually only turned on when compiling a release version. + + Example:- + +<tscreen><verb> + cc -O -o foobar foobar.c +</verb></tscreen> + + This will produce an optimised version of `foobar'. +<p> + The following three flags will force cc to check that your code + complies to the relevant international standard (often referred to + as the ``ANSI'' standard, though strictly speaking it's an ISO + standard). + +<tag/-Wall/ + Enable all the warnings which the authors of cc believe are + worthwhile. Despite the name, it will not enable all the warnings + cc is capable of. + +<tag/-ansi/ + Turn off most (but not all) of the non-standard features provided + by cc. Despite the name, it does not guarantee strictly that your + code will comply to the standard. + +<tag/-pedantic/ + Turn off <it /all/ cc's non-standard features. +<p> + Without these flags, cc will allow you to use some of its + non-standard extensions to the standard. Some of these are very + useful, but will not work with other compilers - in fact, one of + the main aims of the standard is to allow people to write code + that will work with any compiler on any system. (This is known as + ``portable code''). +<p> + Generally, you should try to make your code as portable as + possible, as otherwise you may have to completely re-write the + program later to get it to work somewhere else - and who knows + what you may be using in a few years time? + + Example:- +<tscreen><verb> + cc -Wall -ansi -pedantic -o foobar foobar.c +</verb></tscreen> + will produce an executable `foobar' after checking foobar.c for standard + compliance. + +<tag/-l/ + Specify a library to be used during when linking. +<p> + The most common example of this is when compiling a program that + uses some of the mathematical functions in C. Unlike most other + platforms, these are in a separate library from the standard C one + and you have to tell the compiler to add it. +<p> + The rule is that if the library is called `libsomething.a', you + give cc the argument `-lsomething'. For example, the maths library + is `libm.a', so you give cc the argument `-lm'. A common + ``gotcha'' with the maths library is that it has to be the last + library on the command line. +<p> + Example:- +<tscreen><verb> + cc -o foobar foobar.c -lm +</verb></tscreen> + will link the maths library functions into `foobar'. +<p> + If you're compiling C++ code, you need to add `-lg++' to the + command line argument, to link the C++ library functions. + Alternatively, you can run c++ instead of cc, which does this for + you. +<p> + Example:- +<tscreen><verb> + cc -o foobar foobar.cc -lg++ + c++ -o foobar foobar.cc +</verb></tscreen> + will both produce an executable `foobar' from the C++ source file + `foobar.cc'. Note that, on Unix systems, C++ source files + traditionally end in `.C', `.cxx' or `.cc', rather than the + DOS-style `.cpp' (which was already used for something else). gcc + used to rely on this to work out what kind of compiler to use on + the source file; however, this restriction no longer applies, so + you may now call your C++ files `.cpp' with impunity! + {c++ can also be invoked as g++ on FreeBSD.} +</descrip> + +<sect1><heading>Common cc Queries and Problems</heading> +<p> +Q. I'm trying to write a program which uses the sin() function and I get + an error like this. What does it mean? + +<tscreen><verb> + /var/tmp/cc0143941.o: Undefined symbol `_sin' referenced from text segment +</verb></tscreen> + +A. When using mathematical functions like sin(), you have to tell cc to link + in the maths library, like so:- +<tscreen><verb> + cc -o foobar foobar.c -lm +</verb></tscreen> +Q. All right, I wrote this simple program to practice using -lm. All +it does is raise 2.1 to the power of 6. +<code> +#include <stdio.h> + +int main() { + float f; + + f = pow(2.1, 6); + printf("2.1 ^ 6 = %f\n", f); + return 0; +} +</code> +and I compiled it as + +<tscreen><verb> +gcc temp.c -lm +</verb></tscreen> + +like you said I should, but I get this when I run it:- +<tscreen><verb> +$ ./a.out +2.1 ^ 6 = 1023.000000 +</verb></tscreen> + +This is <it /not/ the right answer! What the %$&#'s going on? +<p> +A. When the compiler sees you call a function, it checks if it's +already seen a prototype for it. If it hasn't, it assumes the function +returns an int, which is definitely not what you want here. +<p> +Q. So how do I fix this? +<p> +A. The prototypes for the mathematical functions are in math.h. If you +include this file, the compiler will be able to find the prototype and +it'll stop doing strange things to your calculation! + +<code> +#include <math.h> +#include <stdio.h> + +int main() { +... +</code> +<p> +<tscreen><verb> +$ ./a.out +2.1 ^ 6 = 85.766121 +</verb></tscreen> + +Morale: if you're using any of the mathematical functions, always +include math.h and remember to link in the maths library. + +Q. I've compiled a file called `foobar.c' and I can't find an executable + called `foobar'. Where's it gone? +<p> +A. cc will call the executable `a.out' unless you tell it differently. Use + the -o option, eg +<tscreen><verb> + cc -o foobar foobar.c +</verb></tscreen> +Q. OK, I've got an executable called `foobar', I can see it when I do + `ls', but when I type in 'foobar' at the command prompt it tells me + there's no such file. Why can't it find it? +<p> +A. Unlike DOS, Unix won't look in the current directory when it's + trying to find out which executable you want it to run, unless you + tell it to. Either type `./foobar', which means ``run the file + called `foobar' in the current directory'', or change your PATH + environment variable so that it looks something like +<tscreen><verb> + bin:/usr/bin:/usr/local/bin:. +</verb></tscreen> + (The dot at the end means ``look in the current directory if it's not in + any of the others'') +<p> +Q. I called my executable `test', but nothing happens when I run + it. What's going on? +<p> +A. Most Unix systems have a program called `test' in /usr/bin and the + shell's picking that one up before it gets to checking the current + directory. Either type + +<tscreen><verb> + ./test +</verb></tscreen> + + or choose a better name for your program! +<p> +Q. I compiled my program and it seemed to run all right at first, then + there was an error and it said something about ``core + dumped''. What does that mean? +<p> +A. The name ``core dump'' dates back to the very early days of Unix, + when the machines used core memory for storing data. Basically, if + the program failed under certain conditions, the system would write + the contents of core memory to disk in a file called ``core'', + which the programmer could then pore over to find out what went + wrong. +<p> +Q. Fascinating stuff, but what I am supposed to do now? +<p> +A. Use gdb to analyse the core (see Debugging). +<p> +Q. When my program dumped core, it said something about a segmentation + fault. What's that? +<p> +A. This basically means that your program tried to perform some sort + of illegal operation on memory; Unix is designed to protect the + operating system and other programs from ``rogue'' programs. +<p> + Common causes for this are:- +<itemize> + <item> Trying to write to a NULL pointer, eg +<code> + char *foo = NULL; + strcpy(foo, "bang!"); +</code> + <item> Using a pointer that hasn't been initialised, eg +<code> + char *foo; + strcpy(foo, "bang!"); +</code> + The pointer will have some random value that, with luck, + will point into an area of memory that isn't available to + your program and the kernel will kill your program before + it can do any damage. If you're unlucky, it'll point + somewhere inside your own program and corrupt one of your + data structures, causing the program to fail mysteriously. +<p> + <item> Trying to access past the end of an array, eg +<code> + int bar[20]; + bar[27] = 6; +</code> + <item> Trying to store something in read-only memory, eg +<code> + char *foo = "My string"; + strcpy(foo, "bang!"); +</code> + (Unix compilers often put string literals like ``My string'' into + read-only areas of memory). + + <item> Doing naughty things with malloc() and free(), eg +<code> + char bar[80]; + free(bar); +</code> + or +<code> + char *foo = malloc(27); + free(foo); + free(foo); +</code> +</itemize> + (Note making one of these mistakes will not always lead to an + error, but they are always bad practice. Some systems and + compilers are more tolerant than others, which is why programs + that ran well on one system can crash when you try them on an + another) +<p> +Q. Sometimes when I get a core dump it says ``bus error''. It says in + my Unix book that this means a hardware problem, but the computer + still seems to be working. Is this true? +<p> +A. No, fortunately not (unless of course you really do have a hardware + problem...). This is usually another way of saying that you + accessed memory in a way you shouldn't have. +<p> +Q. This dumping core business sounds as though it could be quite + useful, if I can make it happen when I want to. Can I do this, or + do I have to wait until there's an error? +<p> +A. Yes, just go to another console or xterm, do + +<tscreen><verb> + ps +</verb></tscreen> + +to find out the process ID of your program, and do + +<tscreen><verb> + kill -ABRT <pid> +</verb></tscreen> + + This is useful if your program has got stuck in an infinite loop, + for instance. (If your program traps SIGABRT, there are several + other signals which have a similar effect). + +<sect><heading>Make</heading> +<p> +<sect1><heading>What is make?</heading> +<p> +When you're working on a simple program with only one or two source +files, typing in + +<tscreen><verb> + cc file1.c file2.c +</verb></tscreen> + +is not too bad, but it quickly becomes very tedious when there are +several files - and it can take a while to compile, too. +<p> +One way to get around this is to use object files and only recompile +the source file if the source code has changed. So we could have +something like:- + +<tscreen><verb> + cc file1.o file2.o ... file37.c ... +</verb></tscreen> + +if we'd changed file37.c, but not any of the others, since the last +time we compiled. +<p> +This may speed up the compilation quite a bit, but doesn't solve the +typing problem. +<p> +Or we could write a shell script to solve the typing problem, but it +would have to re-compile everything, making it very inefficient on a +large project. +<p> +What happens if we have hundreds of source files lying about? What if +we're working in a team with other people who forget to tell us when +they've changed one of their source files that we use? +<p> +Perhaps we could put the two solutions together and write something +like a shell script that would contain some kind of magic rule saying +when a source file needs compiling. Now all we need now is a program +that can understand these rules, as it's a bit too complicated for the +shell. +<p> +This program is called <tt /make/. It reads in a file, called a make +file, that tells it how different files depend on each other, and +works out which files need to be re-compiled and which ones don't. For +example, a rule could say something like ``if fromboz.o is older than +fromboz.c, that means someone must have changed fromboz.c, so it needs +to be re-compiled.'' The make file also has rules telling make <it +/how/ to re-compile the source file, making it a much more powerful +tool. +<p> +Make files are typically kept in the same directory as the source they +apply to, and can be called `makefile', `Makefile' or `MAKEFILE'. Most +programmers use the name 'Makefile', as this puts it near the top of a +directory listing, where it can easily be seen (they don't use the +`MAKEFILE' form as block capitals are often used for documentation +files like `README'). + +<sect1><heading>Example of using make</heading> +<p> +Here's a very simple make file:- +<tscreen><verb> +foo: foo.c + cc -o foo foo.c +</verb></tscreen> +It consists of two lines, a dependency line and a creation line. +<p> +The dependency line here consists of the name of the program (known as +``the target''), followed by a colon, then a gap, then the name of the +source file. When make reads this line, it looks to see if `foo' +exists; if it exists, it compares the time 'foo' was last modified to +the time `foo.c' was last modified. If 'foo' does not exist, or is +older than `foo.c', it then looks at the creation line to find out +what to do. In other words, this is the rule for working out when +foo.c needs to be re-compiled. +<p> +The creation line starts with a tab (press the tab key) and then the +command you would type to create `foo' if you were doing it at a +command prompt. If `foo' is out of date, or does not exist, `make' +then executes this command to create it. In other words, this is the +rule which tells make how to re-compile foo.c. +<p> +So, when you type `make', it will make sure that `foo' is up to date +with respect to your latest changes to `foo.c'. This principle can be +extended to Makefiles with hundreds of targets - in fact, on FreeBSD, +it is possible to compile the entire operating system just by typing +`make world' in the appropriate directory! +<p> +Another useful property of make files is that the targets don't have +to be programs. For instance, we could have a make file that looks +like this:- + +<tscreen><verb> +foo: foo.c + cc -o foo foo.c + +install: + cp foo /home/me +</verb></tscreen> + +We can tell make which target we want to make by typing + +<tscreen><verb> + make <target> +</verb></tscreen> + +make will then only look at that target and ignore any +others. For example, if we type `make foo' with the make file above, +make will ignore the 'install' target. +<p> +If we just type `make' on its own, make will always look at the first +target and then stop without looking at any others. So if we typed +`make' here, it will just go to the `foo' target, re-compile `foo' if +necessary, and then stop without going on to the `install' target. +<p> +Notice that the `install' target doesn't actually depend on anything! +This means that the command on the following line is always executed +when we try to make that target by typing `make install'. In this +case, it will copy `foo' into the user's home directory. This is often +used by application make files, so that the application can be +installed in the correct directory when it has been correctly +compiled. +<p> +This is a slightly confusing subject to try and explain. If you don't +quite understand how make works, the best thing to do is to write a +simple program like ``hello world'' and a make file like the one above +and experiment. Then progress to using more than one source file, or +having the source file include a header file. (The `touch' command is +very useful here - it changes the date on a file without you having to +edit it). + +<sect1><heading>FreeBSD Make Files</heading> +<p> +Make files can be rather complicated to write. Fortunately, BSD-based +systems like FreeBSD come with some very powerful ones as part of the +system. +<p> +One very good example of this is the FreeBSD ports system. Here's the +essential part of a typical ports Makefile:- + +<code> +MASTER_SITES= ftp://freefall.cdrom.com/pub/FreeBSD/LOCAL_PORTS/ +DISTFILES= scheme-microcode+dist-7.3-freebsd.tgz + +.include <bsd.port.mk> +</code> + +Now, if we go to the directory for this port and type make, the +following happens:- + +<enum> + +<item> A check is made to see if the source code for this port is +already on the system. + +<item> If it isn't, an FTP connection to the URL in ``MASTER_SITES'' +is set up to download the source. + +<item> The checksum for the source is calculated and compared it with +one for a known, good, copy of the source. This is to make sure that +the source was not corrupted while in transit. + +<item> Any changes required to make the source work on FreeBSD are +applied - this is known as ``patching''. + +<item> Any special configuration needed for the source is done. (Many +Unix program distributions try to work out which version of Unix they +are being compiled on and which optional Unix features are present - +this is where they are given the information in the FreeBSD ports +scenario). + +<item> The source code for the program is compiled. In effect, we +change to the directory where the source was unpacked and do 'make' - +the program's own make file has the necessary information to build the +program. + +<item> We now have a compiled version of the program. If we wish, we +can test it now; when we feel confident about the program, we can type +'make install'. This will cause the program and any supporting files +it needs to be copied into the correct location; an entry is also made +into a ``package database'', so that the port can easily be +uninstalled later if we change our mind about it. + +</enum> + +Now I think you'll agree that's rather impressive for a four line +script! +<p> +The secret lies in the last line, which tells make to look in the +system make file called `bsd.port.mk'. It's easy to overlook this +line, but this is where all the clever stuff comes from - someone has +written a make file that tells make to do all the things above (plus a +couple of other things I didn't mention, not to mention handling any +errors that may occur) and anyone can get access to that just by +putting a single line in their own make file! +<p> +If you want to have a look at these system make files, they're in +/usr/share/mk, but it's probably best to wait until you've had a bit +of practice with make files, as they are very complicated (and if you +do look at them, make sure you have a flask of strong coffee handy!) + +<sect1><heading>More advanced uses of make</heading> +<p> +Make is a very powerful tool, and can do much more than the simple +example above shows. Unfortunately, there are several different +versions of make, and they all differ considerably. The best way to +learn what they can do is probably to read the documentation - +hopefully this introduction will have given you a base from which you +can do this. +<p> +The version of make that comes with FreeBSD is the Berkeley make; +there is a tutorial for it in /usr/share/doc/psd/12.make. To view it, +do + +<tscreen><verb> + zmore paper.ascii.gz +</verb></tscreen> + +in that directory. +<p> +Many applications in the ports use GNU make, which has a very good set +of `info' pages. If you have installed any of these ports, GNU make +will automatically have been installed as `gmake'. It's also available +as a port and package in it's own right. +<p> +To view the info pages for GNU make, you will have to edit the `dir' +file in the /usr/local/info directory to add an entry for it. This +involves adding a line like + +<tscreen><verb> + * Make: (make). The GNU Make utility. + </verb></tscreen> + +to the file. Once you have done this, you can type `info' and then +select make from the menu (or in Emacs, do C-h i). + +<sect><heading>Debugging</heading> +<p> +<sect1><heading>The Debugger</heading> +<p> +The debugger that comes with FreeBSD is called `gdb' (GNU debugger). You +start it up by typing + +<tscreen><verb> + gdb <progname> +</verb></tscreen> + +although most people prefer to run it inside Emacs. You can do this by + +<tscreen><verb> + M-x gdb RET <progname> RET. +</verb></tscreen> + +Using a debugger allows you to run the program under more controlled +circumstances. Typically, you can step through the program a line at a +time, inspect the value of variables, change them, tell the debugger to run +up to a certain point and then stop, and so on. You can even attach to a +program that's already running, or load a core file to investigate why the +program crashed. +<p> +It's even possible to debug the kernel, though that's a little trickier +than the user applications we'll be discussing in this section. +<p> +gdb has quite good on-line help, as well as a set of info pages, so this +section will concentrate on a few of the basic commands. +<p> +Finally, if you find its text-based command-prompt style off-putting, +there's a graphical front-end for it <htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/ports/devel/xxgdb.tgz" +name="xxgdb"> in the ports. +<p> +This section is intended to be an introduction to using gdb and does +not cover specialised topics such as debugging the kernel. + +<sect1><heading>Running a program in the debugger</heading> +<p> +You'll need to have compiled the program with the `-g' option to get the +most out of using gdb. It will work without, but you'll only see the name +of the function you're in, instead of the source code. If you see a line +like + +<tscreen><verb> + ...(no debugging symbols found)... +</verb></tscreen> + +when gdb starts up, you'll know that the program wasn't compiled with +the `-g' option. +<p> +At the gdb prompt, type `break main'. This will tell the debugger to +skip over the preliminary set-up code in the program and start at the +beginning of your code. Now type `run' to start the program - it will +start at the beginning of the set-up code and then get stopped by the +debugger when it calls main(). (If you've ever wondered where main() +gets called from, now you know!). +<p> +You can now step through the program, a line at a time, by pressing +`n'. If you get to a function call, you can step into it by pressing +`s'. Once you're in a function call, you can return from stepping into +a function call by pressing `f'. You can also use `up' and `down' to +take a quick look at the caller. +<p> +Here's a simple example of how to spot a mistake in a program with +gdb. This is our program (with a deliberate mistake):- + +<code> +#include <stdio.h> + +int bazz(int anint); + +main() { + int i; + + printf("This is my program\n"); + bazz(i); + return 0; +} + +int bazz(int anint) { + printf("You gave me %d\n", anint); + return anint; +} +</code> + +This program sets i to be 5 and passes it to a function bazz() which prints +out the number we gave it. +<p> +When we compile and run the program we get + +<tscreen><verb> + cc -g -o temp temp.c + ./temp + This is my program + anint = 4231 +</verb></tscreen> + +That wasn't what we expected! Time to see what's going on! + +<tscreen><verb> +Current directory is ~/tmp/ +GDB is free software and you are welcome to distribute copies of it + under certain conditions; type "show copying" to see the conditions. +There is absolutely no warranty for GDB; type "show warranty" for details. +GDB 4.13 (i386-unknown-freebsd), +Copyright 1994 Free Software Foundation, Inc... +(gdb) break main # Skip the set-up code +Breakpoint 1 at 0x160f: file temp.c, line 9. # gdb puts breakpoint at main() +(gdb) run # Run as far as main() +Starting program: /home/james/tmp/temp # Program starts running + +Breakpoint 1, main () at temp.c:9 # gdb stops at main() +(gdb) n # Go to next line +This is my program # Program prints out "This .." +(gdb) s # step into bazz() +bazz (anint=4231) at temp.c:17 # gdb displays stack frame +</verb></tscreen> + +Hang on a minute! How did anint get to be 4231? Didn't we set it to be 5 +in main()? Let's move up to main() and have a look. + +<tscreen><verb> +(gdb) up # Move up call stack +#1 0x1625 in main () at temp.c:11 # gdb displays stack frame +(gdb) p i # Show us the value of i +$1 = 4231 # gdb displays 4231 +</verb></tscreen> + +Oh dear! Looking at the code, we forgot to initialise i. We meant to put + +<code> +... +main() { + int i; + + i = 5; + printf("This is my program\n"); +... +</code> + +but we missed the `i=5;' line out. As we didn't initialise i, it had +whatever number happened to be in that area of memory when the program +ran, which in this case happened to be 4231. +<p> +Note that gdb displays the stack frame every time we go into or out of +a function, even if we're using `up' and `down' to move around the +call stack. This shows the name of the function and the values of its +arguments, which helps us keep track of where we are and what's going +on. (The stack is a storage area where the program stores information +about the arguments passed to functions and where to go when it +returns from a function call). + +<sect1><heading>Examining a core file</heading> +<p> +A core file is basically a file which contains the complete state of +the process when it crashed. In ``the good old days'', programmers had +to print out hex listings of core files and sweat over machine code +manuals, but now life is a bit easier. Incidentally, under FreeBSD and +other 4.4BSD systems, a core file is called ``progname.core'' instead +of just core, to make it clearer which program a core file belongs to. +<p> +To examine a core file, start up gdb in the usual way. Instead of +typing `break' or `run', type + +<tscreen><verb> + core progname.core +</verb></tscreen> + +(if you're not in the same directory as the core file, you'll have to +do `dir /path/to/core/file' first). +<p> +You should see something like this:- + +<tscreen><verb> +Current directory is ~/tmp/ +GDB is free software and you are welcome to distribute copies of it + under certain conditions; type "show copying" to see the conditions. +There is absolutely no warranty for GDB; type "show warranty" for details. +GDB 4.13 (i386-unknown-freebsd), +Copyright 1994 Free Software Foundation, Inc... +(gdb) core a.out.core +Core was generated by `a.out'. +Program terminated with signal 11, Segmentation fault. +Cannot access memory at address 0x7020796d. +#0 0x164a in foobar (some_arg=0x5) at temp.c:17 +</verb></tscreen> + +In this case, the program was called `a.out', so the core file is +called `a.out.core'. We can see that the program crashed due to trying +to access an area in memory that was not available to it in a function +called `bazz'. +<p> +Sometimes it's useful to be able to see how a function was called, as +the problem could have occurred a long way up the call stack in a +complex program. The `bt' command causes gdb to print out a back-trace +of the call stack:- + +<tscreen><verb> +(gdb) bt +#0 0x164a in bazz (anint=0x5) at temp.c:17 +#1 0xefbfd888 in end () +#2 0x162c in main () at temp.c:11 +</verb></tscreen> + +The end() function is called when a program crashes; in this case, the +bazz() function was called from main(). + +<sect1><heading>Attaching to a running program</heading> +<p> +One of the neatest features about gdb is that it can attach to a +program that's already running. (Of course, that assumes you have +sufficient permissions to do so). A common problem is when you are +stepping through a program that forks, and you want to trace the +child, but the debugger will only let you trace the parent. +<p> +What you do is start up another gdb, use `ps' to find the process ID +for the child, and do + +<tscreen><verb> + attach <pid> +</verb></tscreen> + +in gdb, and then debug as usual. +<p> +``That's all very well,'' you're probably thinking, ``but by the time +I've done that, the child process will be over the hill and far +away''. Fear not, gentle reader, here's how to do it (courtesy of the +gdb info pages):- + +<tscreen><verb> +... +if ((pid = fork()) < 0) /* _Always_ check this */ + error(); +else if (pid == 0) { /* child */ + int PauseMode = 1; + + while (PauseMode) + sleep(10); /* Wait until someone attaches to us */ + ... +} else { /* parent */ + ... +</verb></tscreen> + +Now all you have to do is attach to the child, set PauseMode to 0, and +wait for the sleep() call to return! + +<sect><heading>Using Emacs as a Development Environment</heading> +<p> +<sect1><heading>Emacs</heading> +<p> +Unfortunately, Unix systems don't come with the kind of +everything-you-ever-wanted-and-lots-more-you-didn't-in-one-gigantic-package +integrated development environments that other systems have (at least, +not unless you pay out very large sums of money). However, it is +possible to set up your own environment. It may not be as pretty, and +it may not be quite as integrated, but you can set it up the way you +want it. And it's free. And you have the source to it. +<p> +The key to it all is Emacs. Now there are some people who loathe it, +but many who love it. If you're one of the former, I'm afraid this +section will hold little of interest to you. Also, you'll need a fair +amount of memory to run it - I'd recommend 8MB in text mode and 16MB +in X as the bare minimum to get reasonable performance. +<p> +Emacs is basically a highly customisable editor - indeed, it has been +customised to the point where it's more like an operating system than +an editor! (Many developers and sysadmins do in fact spend practically +all their time working inside Emacs, leaving it only to log out). +<p> +It's impossible even to summarise everything Emacs can do here, but +here are some of the features of interest to developers:- + +<itemize> +<item> Very powerful editor, allowing search-and-replace on both + strings and regular expressions (patterns), jumping to start/end of + block expression, etc, etc. + +<item> Pull-down menus and online help. + +<item> Language-dependent syntax highlighting and indentation. + +<item> Completely customisable. + +<item> You can compile and debug programs within Emacs. + +<item> On a compilation error, you can jump to the offending line of source + code. + +<item> Friendly-ish front-end to the `info' program used for reading GNU + hypertext documentation (including the documentation on Emacs). + +<item> Friendly front-end to GDB, allowing you to look at the source code + as you step through your program. + +<item> You can read Usenet news and mail while your program is compiling ;-) +</itemize> + +And doubtless many more that I've overlooked. +<p> +Emacs can be installed on FreeBSD using <htmlurl +url="ftp://ftp.freebsd.org:pub/FreeBSD/packages/editors/emacs" +name="the Emacs package">. +<p> +Once it's installed, start it up and do C-h t to read an Emacs +tutorial - that means hold down the control key, press `h', let go of +the control key, and then press t. (Alternatively, you can you use +the mouse to select ``Emacs Tutorial'' from the ``Help'' menu). +<p> +Although Emacs does have menus, it's well worth learning the key +bindings, as it's much quicker when you're editing something to press +a couple of keys than to try and find the mouse and then click on the +right place. And, when you're talking to seasoned Emacs users, you'll +find they often casually throw around expressions like + +<tscreen><verb> + M-x replace-s RET foo RET bar RET +</verb></tscreen> + +so it's useful to know what they mean. And in any case, Emacs has far +too many useful functions for them to all fit on the menu bars. +<p> +Fortunately, it's quite easy to pick up the key-bindings, as they're +displayed next to the menu item. (My advice is to use the menu item +for, say, opening a file until you understand how it works and feel +confident with it, then try doing C-x C-f. When you're happy with +that, move on to another menu command). +<p> +If you can't remember what a particular combination of keys does, +select ``Describe Key'' from the ``Help'' menu and type it in - Emacs +will tell you what it does. You can also use the ``Command Apropos'' +menu item to find out all the commands which contain a particular word +in them, with the key binding next to it. +<p> +By the way, the expression above means hold down the Meta key, press +`x', release the Meta key, type replace-s (short for ``replace-string'' +- another feature of Emacs is that you can abbreviate commands), press +the return key, type foo (the string you want replaced), press the +return key, type bar (the string you want to replace ``foo'' with) and +press return again. Emacs will then do the search-and-replace +operation you've just requested. +<p> +If you're wondering what on earth the Meta key is, it's a special key +that many Unix workstations have. Unfortunately, PC's don't have one, +so it's usually the ``alt'' key (or if you're unlucky, the ``escape'' +key). +<p> +Oh, and to get out of Emacs, do C-c C-x (that means hold down the +control key, press `c', press `x' and release the control key). If you +have any unsaved files open, Emacs will ask you if you want to save +them. (Ignore the bit in the documentation where it says C-z is the +usual way to leave Emacs - that leaves Emacs hanging around in the +background, and is only really useful if you're on a system which +doesn't have virtual terminals). + +<sect1><heading>Configuring Emacs</heading> +<p> +Emacs does many wonderful things, some of them are built in, some of +them need to be configured. +<p> +Instead of using a proprietary macro language for configuration, Emacs +uses a version of Lisp specially adapted for editors, known as Emacs +Lisp. This can be quite useful if you want to go on and learn +something like Common Lisp, as it's considerably smaller than Common +Lisp (although still quite big!). +<p> +The best way to learn Emacs Lisp is to download the <htmlurl +url="ftp://prep.ai.mit.edu:pub/gnu/elisp-manual-19-2.4.tar.gz" +name="Emacs Tutorial"> +<p> +However, there's no need to actually know any Lisp to get started with +configuring Emacs, as I've included a sample ``.emacs'' file, which +should be enough to get you started. Just copy it into your home +directory and restart Emacs if it's already running; it will read the +commands from the file and (hopefully) give you a useful basic setup. + +<sect1><heading>A sample .emacs file</heading> +<p> +Unfortunately, there's far too much here to explain it in detail; +however there are one or two points worth mentioning. + +<itemize> +<item> Everything beginning with a `;' is a comment and is ignored by Emacs. + +<item> In the first line, the -*- Emacs-Lisp -*- is so that we can edit +the .emacs file itself within Emacs and get all the fancy features for +editing Emacs Lisp (Emacs usually tries to guess this based on the +filename, and may not get it right for .emacs). + +<item> The `tab' key is bound to an indentation function in some modes, so +when you press the tab key, it will indent the current line of +code. If you want to put a tab character in whatever you're writing, +hold the control key down while you're pressing the tab key. + +<item> This file supports syntax highlighting for C, C++, Perl, Lisp and +Scheme (by guessing the language from the filename). + +<item> Emacs already has a pre-defined function called ``next-error''. +In a compilation output window, this allows you to move from one +compilation error to the next by doing M-n; we define a complementary +function, ``previous-error'', that allows you to go to a previous +error by doing M-p. The nicest feature of all is that C-c C-c will +open up the source file in which the error occurred and jump to the +appropriate line. + +<item> We enable Emacs's ability to act as a server, so that if you're doing +something outside Emacs and you want to edit a file, you can just +type in +<tscreen><verb> + emacsclient <filename> +</verb></tscreen> + +and then you can edit the file in your Emacs! (Many Emacs users set +their EDITOR environment to `emacsclient' so this happens every time +they need to edit a file). +</itemize> + +<tscreen><verb> +;; -*-Emacs-Lisp-*- + +;; This file is designed to be re-evaled; use the variable first-time +;; to avoid any problems with this. +(defvar first-time t + "Flag signifying this is the first time that .emacs has been evaled") + +;; Meta +(global-set-key "\M- " 'set-mark-command) +(global-set-key "\M-\C-h" 'backward-kill-word) +(global-set-key "\M-\C-r" 'query-replace) +(global-set-key "\M-r" 'replace-string) +(global-set-key "\M-g" 'goto-line) +(global-set-key "\M-h" 'help-command) + +;; Function keys +(global-set-key [f1] 'manual-entry) +(global-set-key [f2] 'info) +(global-set-key [f3] 'repeat-complex-command) +(global-set-key [f4] 'advertised-undo) +(global-set-key [f5] 'eval-current-buffer) +(global-set-key [f6] 'buffer-menu) +(global-set-key [f7] 'other-window) +(global-set-key [f8] 'find-file) +(global-set-key [f9] 'save-buffer) +(global-set-key [f10] 'next-error) +(global-set-key [f11] 'compile) +(global-set-key [f12] 'grep) +(global-set-key [C-f1] 'compile) +(global-set-key [C-f2] 'grep) +(global-set-key [C-f3] 'next-error) +(global-set-key [C-f4] 'previous-error) +(global-set-key [C-f5] 'display-faces) +(global-set-key [C-f8] 'dired) +(global-set-key [C-f10] 'kill-compilation) + +;; Keypad bindings +(global-set-key [up] "\C-p") +(global-set-key [down] "\C-n") +(global-set-key [left] "\C-b") +(global-set-key [right] "\C-f") +(global-set-key [home] "\C-a") +(global-set-key [end] "\C-e") +(global-set-key [prior] "\M-v") +(global-set-key [next] "\C-v") +(global-set-key [C-up] "\M-\C-b") +(global-set-key [C-down] "\M-\C-f") +(global-set-key [C-left] "\M-b") +(global-set-key [C-right] "\M-f") +(global-set-key [C-home] "\M-<") +(global-set-key [C-end] "\M->") +(global-set-key [C-prior] "\M-<") +(global-set-key [C-next] "\M->") + +;; Mouse +(global-set-key [mouse-3] 'imenu) + +;; Misc +(global-set-key [C-tab] "\C-q\t") ; Control tab quotes a tab. +(setq backup-by-copying-when-mismatch t) + +;; Treat 'y' or <CR> as yes, 'n' as no. +(fset 'yes-or-no-p 'y-or-n-p) + (define-key query-replace-map [return] 'act) + (define-key query-replace-map [?\C-m] 'act) + +;; Load packages +(require 'desktop) +(require 'tar-mode) + +;; Pretty diff mode +(autoload 'ediff-buffers "ediff" "Intelligent Emacs interface to diff" t) +(autoload 'ediff-files "ediff" "Intelligent Emacs interface to diff" t) +(autoload 'ediff-files-remote "ediff" + "Intelligent Emacs interface to diff") +</verb></tscreen> +<tscreen><verb> +(if first-time + (setq auto-mode-alist + (append '(("\\.cpp$" . c++-mode) + ("\\.hpp$" . c++-mode) + ("\\.lsp$" . lisp-mode) + ("\\.scm$" . scheme-mode) + ("\\.pl$" . perl-mode) + ) auto-mode-alist))) + +;; Auto font lock mode +(defvar font-lock-auto-mode-list + (list 'c-mode 'c++-mode 'c++-c-mode 'emacs-lisp-mode 'lisp-mode 'perl-mode 'scheme-mode) + "List of modes to always start in font-lock-mode") + +(defvar font-lock-mode-keyword-alist + '((c++-c-mode . c-font-lock-keywords) + (perl-mode . perl-font-lock-keywords)) + "Associations between modes and keywords") + +(defun font-lock-auto-mode-select () + "Automatically select font-lock-mode if the current major mode is +in font-lock-auto-mode-list" + (if (memq major-mode font-lock-auto-mode-list) + (progn + (font-lock-mode t)) + ) + ) + +(global-set-key [M-f1] 'font-lock-fontify-buffer) + +;; New dabbrev stuff +;(require 'new-dabbrev) +(setq dabbrev-always-check-other-buffers t) +(setq dabbrev-abbrev-char-regexp "\\sw\\|\\s_") +(add-hook 'emacs-lisp-mode-hook + '(lambda () + (set (make-local-variable 'dabbrev-case-fold-search) nil) + (set (make-local-variable 'dabbrev-case-replace) nil))) +(add-hook 'c-mode-hook + '(lambda () + (set (make-local-variable 'dabbrev-case-fold-search) nil) + (set (make-local-variable 'dabbrev-case-replace) nil))) +(add-hook 'text-mode-hook + '(lambda () + (set (make-local-variable 'dabbrev-case-fold-search) t) + (set (make-local-variable 'dabbrev-case-replace) t))) + +;; C++ and C mode... +(defun my-c++-mode-hook () + (setq tab-width 4) + (define-key c++-mode-map "\C-m" 'reindent-then-newline-and-indent) + (define-key c++-mode-map "\C-ce" 'c-comment-edit) + (setq c++-auto-hungry-initial-state 'none) + (setq c++-delete-function 'backward-delete-char) + (setq c++-tab-always-indent t) + (setq c-indent-level 4) + (setq c-continued-statement-offset 4) + (setq c++-empty-arglist-indent 4)) + +(defun my-c-mode-hook () + (setq tab-width 4) + (define-key c-mode-map "\C-m" 'reindent-then-newline-and-indent) + (define-key c-mode-map "\C-ce" 'c-comment-edit) + (setq c-auto-hungry-initial-state 'none) + (setq c-delete-function 'backward-delete-char) + (setq c-tab-always-indent t) +;; BSD-ish indentation style + (setq c-indent-level 4) + (setq c-continued-statement-offset 4) + (setq c-brace-offset -4) + (setq c-argdecl-indent 0) + (setq c-label-offset -4)) + +;; Perl mode +(defun my-perl-mode-hook () + (setq tab-width 4) + (define-key c++-mode-map "\C-m" 'reindent-then-newline-and-indent) + (setq perl-indent-level 4) + (setq perl-continued-statement-offset 4)) + +;; Scheme mode... +(defun my-scheme-mode-hook () + (define-key scheme-mode-map "\C-m" 'reindent-then-newline-and-indent)) + +;; Emacs-Lisp mode... +(defun my-lisp-mode-hook () + (define-key lisp-mode-map "\C-m" 'reindent-then-newline-and-indent) + (define-key lisp-mode-map "\C-i" 'lisp-indent-line) + (define-key lisp-mode-map "\C-j" 'eval-print-last-sexp)) + +;; Add all of the hooks... +(add-hook 'c++-mode-hook 'my-c++-mode-hook) +(add-hook 'c-mode-hook 'my-c-mode-hook) +(add-hook 'scheme-mode-hook 'my-scheme-mode-hook) +(add-hook 'emacs-lisp-mode-hook 'my-lisp-mode-hook) +(add-hook 'lisp-mode-hook 'my-lisp-mode-hook) +(add-hook 'perl-mode-hook 'my-perl-mode-hook) + +;; Complement to next-error +(defun previous-error (n) + "Visit previous compilation error message and corresponding source code." + (interactive "p") + (next-error (- n))) +</verb></tscreen> +<tscreen><verb> +;; Misc... +(transient-mark-mode 1) +(setq mark-even-if-inactive t) +(setq visible-bell nil) +(setq next-line-add-newlines nil) +(setq compile-command "make") +(setq suggest-key-bindings nil) +(put 'eval-expression 'disabled nil) +(put 'narrow-to-region 'disabled nil) +(put 'set-goal-column 'disabled nil) + +;; Elisp archive searching +(autoload 'format-lisp-code-directory "lispdir" nil t) +(autoload 'lisp-dir-apropos "lispdir" nil t) +(autoload 'lisp-dir-retrieve "lispdir" nil t) +(autoload 'lisp-dir-verify "lispdir" nil t) + +;; Font lock mode +(defun my-make-face (face colour &optional bold) + "Create a face from a colour and optionally make it bold" + (make-face face) + (copy-face 'default face) + (set-face-foreground face colour) + (if bold (make-face-bold face)) + ) + +(if (eq window-system 'x) + (progn + (my-make-face 'blue "blue") + (my-make-face 'red "red") + (my-make-face 'green "dark green") + (setq font-lock-comment-face 'blue) + (setq font-lock-string-face 'bold) + (setq font-lock-type-face 'bold) + (setq font-lock-keyword-face 'bold) + (setq font-lock-function-name-face 'red) + (setq font-lock-doc-string-face 'green) + (add-hook 'find-file-hooks 'font-lock-auto-mode-select) + + (setq baud-rate 1000000) + (global-set-key "\C-cmm" 'menu-bar-mode) + (global-set-key "\C-cms" 'scroll-bar-mode) + (global-set-key [backspace] 'backward-delete-char) + ; (global-set-key [delete] 'delete-char) + (standard-display-european t) + (load-library "iso-transl"))) + +;; X11 or PC using direct screen writes +(if window-system + (progn + ;; (global-set-key [M-f1] 'hilit-repaint-command) + ;; (global-set-key [M-f2] [?\C-u M-f1]) + (setq hilit-mode-enable-list + '(not text-mode c-mode c++-mode emacs-lisp-mode lisp-mode + scheme-mode) + hilit-auto-highlight nil + hilit-auto-rehighlight 'visible + hilit-inhibit-hooks nil + hilit-inhibit-rebinding t) + (require 'hilit19) + (require 'paren)) + (setq baud-rate 2400) ; For slow serial connections + ) + +;; TTY type terminal +(if (and (not window-system) + (not (equal system-type 'ms-dos))) + (progn + (if first-time + (progn + (keyboard-translate ?\C-h ?\C-?) + (keyboard-translate ?\C-? ?\C-h))))) + +;; Under UNIX +(if (not (equal system-type 'ms-dos)) + (progn + (if first-time + (server-start)))) + +;; Add any face changes here +(add-hook 'term-setup-hook 'my-term-setup-hook) +(defun my-term-setup-hook () + (if (eq window-system 'pc) + (progn +;; (set-face-background 'default "red") + ))) + +;; Restore the "desktop" - do this as late as possible +(if first-time + (progn + (desktop-load-default) + (desktop-read))) + +;; Indicate that this file has been read at least once +(setq first-time nil) + +;; No need to debug anything now +(setq debug-on-error nil) + +;; All done +(message "All done, %s%s" (user-login-name) ".") + +</verb></tscreen> + +<sect1><heading>Extending the Range of Languages Emacs Understands</heading> +<p> +Now, this is all very well if you only want to program in the +languages already catered for in the .emacs file (C, C++, Perl, Lisp +and Scheme), but what happens if a new language called "whizbang" +comes out, full of exciting features? +<p> +The first thing to do is find out if "whizbang" comes with any files +that tell Emacs about the language. These usually end in ".el", short +for "Emacs Lisp". For example, if "whizbang" is a FreeBSD port, we can +locate these files by doing + +<tscreen><verb> + find /usr/ports/lang/whizbang -name *.el -print +</verb></tscreen> + +and install them by copying them into Emac's site Lisp directory. On +FreeBSD 2.1.0-RELEASE, this is /usr/local/share/emacs/site-lisp. + +So for example, if the output from the find command was + +<tscreen><verb> + /usr/ports/lang/whizbang/work/misc/whizbang.el +</verb></tscreen> + +we would do + +<tscreen><verb> + cp /usr/ports/lang/whizbang/work/misc/whizbang.el /usr/local/share/emacs/site-lisp +</verb></tscreen> + +Next, we need to decide what extension whizbang source files +have. Let's say for the sake of argument that they all end in +`.wiz'. We need to add an entry to our .emacs file to make sure Emacs +will be able to use the information in whizbang.el. +<p> +Find the auto-mode-alist entry in .emacs and add a line for whizbang, +such as:- + +<tscreen><verb> + ... + ("\\.lsp$" . lisp-mode) + ("\\.wiz$" . whizbang-mode) + ("\\.scm$" . scheme-mode) + ... +</verb></tscreen> + +This means that Emacs will automatically go into whizbang-mode when +you edit a file ending in .wiz. +<p> +Just below this, you'll find the font-lock-auto-mode-list entry. Add +whizbang-mode to it like so:- + +<tscreen><verb> +;; Auto font lock mode +(defvar font-lock-auto-mode-list + (list 'c-mode 'c++-mode 'c++-c-mode 'emacs-lisp-mode 'whizbang-mode 'lisp-mode 'perl-mode 'scheme-mode) + "List of modes to always start in font-lock-mode") +</verb></tscreen> + +This means that Emacs will always enable font-lock-mode (ie syntax +highlighting) when editing a .wiz file. +<p> +And that's all that's needed. If there's anything else you want done +automatically when you open up a .wiz file, you can add a +whizbang-mode hook (see my-scheme-mode-hook for a simple example that +adds auto-indent). + +<sect><heading>Further Reading</heading> +<sect1><heading>Bibliography</heading> +<p> +<itemize> +<item> +Brian Harvey and Matthew Wright +<em>Simply Scheme</em> +MIT 1994. +<newline>ISBN 0-262-08226-8 +</item> + +<item> +Randall Schwartz +<em>Learning Perl</em> +O'Reilly 1993 +<newline>ISBN 1-56592-042-2 +</item> + +<item> +Patrick Henry Winston and Berthold Klaus Paul Horn +<em>Lisp (3rd Edition)</em> +Addison-Wesley 1989 +<newline>ISBN 0-201-08319-1 +</item> + +<item> +Brian W. Kernighan and Rob Pike +<em>The Unix Programming Environment</em> +Prentice-Hall 1984 +<newline>ISBN 0-13-937681-X +</item> + +<item> +Brian W. Kernighan and Dennis M. Ritchie +<em>The C Programming Language (2nd Edition)</em> +Prentice-Hall 1988 +<newline>ISBN 0-13-110362-8 +</item> + +<item> +Bjarne Stroustrup +<em>The C++ Programming Language</em> +Addison-Wesley 1991 +<newline>ISBN 0-201-53992-6 +</item> + +<item> +W. Richard Stevens +<em>Advanced Programming in the Unix Environment</em> +Addison-Wesley 1992 +<newline>ISBN 0-201-56317-7 +</item> + +<item> +W. Richard Stevens +<em>Unix Network Programming</em> +Prentice-Hall 1990 +<newline>ISBN 0-13-949876-1 +</item> +</itemize> +</article> diff --git a/data/tutorials/disklessx/Makefile b/data/tutorials/disklessx/Makefile new file mode 100644 index 0000000000..d1f593b516 --- /dev/null +++ b/data/tutorials/disklessx/Makefile @@ -0,0 +1,3 @@ +DOCS= disklessx.sgml + +.include "../../web.mk" diff --git a/data/tutorials/disklessx/disklessx.sgml b/data/tutorials/disklessx/disklessx.sgml new file mode 100644 index 0000000000..94a8b62c87 --- /dev/null +++ b/data/tutorials/disklessx/disklessx.sgml @@ -0,0 +1,264 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [ +<!ENTITY base CDATA "../.."> +<!ENTITY date "$Date: 1996-09-24 17:46:00 $"> +<!ENTITY title "Diskless X Server: a how to guide"> +<!ENTITY copyright " "> +<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes; +]> +<html> +&header; + +<H3>By Jerry Kendall</H3> +<H3>(<a href="mailto:jerry@kcis.com">jerry@kcis.com</a>)</H3> + +<p>With the help of some 'friends' on the FreeBSD-hackers list, I have +been able to create a diskless X terminal... The creation of the X terminal +required first creating a diskless system with minimal utilities mounted +via NFS. These same steps were used to create 2 seperate diskless systems. +The first is 'altair.kcis.com'. A diskless X terminal that I run on my +old 386DX-40. It has a 340Meg hard disk but, I did not want to change it. +So, it boots from 'antares.kcis.com' across a ethernet. The second system +is a 486DX2-66. I setup 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.</p> + +<hr> +NOTE: I am sure that there is stuff that needs to be added to this. Please send me any comments.... +<hr> + +<h2>Creating the boot floppy (On the diskless system)</h2> + +<p>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 config.sys/autoexec.bat files) 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.</p> +<pre> + ---- config.sys ---- + [menu] + menuitem=normal, normal + menuitem=unix, unix + [normal] + .... + normal config.sys stuff + ... + [unix] + ---- + + ---- autoexec.bat ---- + @ECHO OFF + goto %config% + + :normal + ... + normal autoexec.bat stuff + ... + goto end + + :unix + cd \netboot + nb8390.com + + :end + ----</pre> + +<h2>Getting the network boot programs (On the server)</h2> + +<p>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 required. !!!! make a +backup of the original in case it gets fobar'd !!! When the build +is done, there should be 2 MS-DOS executables, 'nb8390.com' and +'nb3c509.com'. One of these two programs will be what you need +to run on the diskless server. It will load the kernel from the +boot server. At this point, put both programs on the MS-DOS +boot floppy created earlier. + +<h2>Determine which program to run (On the diskless system)</h2> + +<p>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 3Com 509 based chipset, use the +NB3C509.COM boot program. If you are not sure which you have, +try using one, if it says 'No adapter found', try the other. +Beyond that, you are pretty much on your own. + +<h2>Booting across the network</h2> + +<p>Boot the diskless system with out any config.sys/autoexec.bat +files. try running the boot program for your ethernet adapter.</p> +<pre> + My ethernet adapter is running in WD8013 16bit mode so + I run NB8390.COM + + C:> cd \netboot + C:> nb8390 + + Boot from Network (Y/N) ? Y + + BOOTP/TFTP/NFS bootstrap loader ESC for menu + + Searching for adapter.. + WD8013EBT base 0x0300, memory 0x000D8000, addr 00:40:01:43:26:66 + + Searching for server..</pre> + +<p>At this point, my diskless system is trying to find a machine to act +as a boot server. Make note of the addr line above, you will need this +number later. Reset the diskless system and modify your config.sys and +autoexec.bat files to do these steps automatically for you. Perhaps in +a menu. If you had to run 'nb3c509.com' instead of 'nb8390.com' the +output is the same as above. If you got 'No adapter found' at the +'Searching for adapter..' message, verify that you did indeed set the +compile time defines in the makefile correctly.</p> + +<h2>Allowing systems to boot across the network (On the + server)</h2> + +<p>Make sure the /etc/inetd.conf file has entries for tftp and bootps. +Mine are listed below:</p> +<pre> + ---- /etc/inetd.conf ---- + tftp dgram udp wait nobody /usr/libexec/tftpd tftpd + # + # Additions by who ever you are + bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab + ---- +</pre> +<p>If you have to change the /etc/inetd.conf file, send a HUP signal to +inetd. To do this, get the process ID of inetd with 'ps -ax | grep +inetd | grep -v grep'. Once you have it, send it a HUP signal. Do this +by 'kill -HUP <pid>'. This will force inetd to re-read its config file.</p> + +<p>Did you remember to note the 'addr' line from the output of the boot +loader on the diskless system???? Guess what, here is where you need it.</p> + +<p>Add an entry to /etc/bootptab (maybe creating the file). It should be +laid out identical to this:</p> + +<pre> + altair:\ + :ht=ether:\ + :ha=004001432666:\ + :sm=255.255.255.0:\ + :hn:\ + :ds=199.246.76.1:\ + :ip=199.246.76.2:\ + :gw=199.246.76.1:\ + :vm=rfc1048: + + The lines are as follows: + 'altair' the diskless systems name without the domain name. + 'ht=ether' the hardware type of 'ethernet'. + 'ha=004001432666' the hardware address (the number noted above). + 'sm=255.255.255.0' the subnet mask. + 'hn' tells server to send client's hostname to the client. + 'ds=199.246.76.1' tells the client who the domain server is. + 'ip=199.246.76.2' tells the client what it's IP address is. + 'gw=199.246.76.1' tells the client what the default gateway is. + 'vm=...' just leave it there... +</pre> +<p>NOTE: +****** Be sure to setup the IP addresses correctly, the addresses +above are my own......</p> + +<p>Create the directory '/tftpboot' on the server it will contain the +configuration files for the diskless systems that the server will +serve. These files will be named 'cfg.<ip>' where <ip> is the IP +address of the diskless system. The config file for 'altair' is +/tftpboot/cfg.199.246.76.2. The contents is:</p> + +<pre> + ---- /tftpboot/cfg.199.246.76.2 ---- + rootfs 199.246.76.1:/DiskLess/rootfs/altair + hostname altair.kcis.com + ---- +</pre> +<p>The line 'hostname altair.kcis.com' simply tells the diskless +system what its fully qualified domain name is.</p> + +<p>The line 'rootfs 199.246.76.1:/DiskLess/rootfs/altair' tells the +diskless system where its NFS mountable root filesystem is located.</p> + +<p>NOTE:!!!!! The NFS mounted root filesystem will be mounted READ ONLY.</p> + +<p>The hierarchy for the diskless system can be re-mounted allowing +read-write operations if required.</p> + +<p>I use my spare 386DX-40 as a dedicated X terminal...</p> + +<p>The hierarchy for 'altair' is:</p> + +<pre> + / + /bin + /etc + /tmp + /sbin + /dev + /dev/fd + /usr + /var + /var/run +</pre> + +<p>The actual list of files is:</p> + +<pre> + -r-xr-xr-x 1 root wheel 779984 Dec 11 23:44 ./kernel + -r-xr-xr-x 1 root bin 299008 Dec 12 00:22 ./bin/sh + -rw-r--r-- 1 root wheel 499 Dec 15 15:54 ./etc/rc + -rw-r--r-- 1 root wheel 1411 Dec 11 23:19 ./etc/ttys + -rw-r--r-- 1 root wheel 157 Dec 15 15:42 ./etc/hosts + -rw-r--r-- 1 root bin 1569 Dec 15 15:26 ./etc/XF86Config.altair + -r-x------ 1 bin bin 151552 Jun 10 1995 ./sbin/init + -r-xr-xr-x 1 bin bin 176128 Jun 10 1995 ./sbin/ifconfig + -r-xr-xr-x 1 bin bin 110592 Jun 10 1995 ./sbin/mount_nfs + -r-xr-xr-x 1 bin bin 135168 Jun 10 1995 ./sbin/reboot + -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 +</pre> +<p>Don't forget to 'MAKEDEV all' in the 'dev' directory.</p> + +<p>My /etc/rc for 'altair' is:</p> + +<pre> + #!/bin/sh + # + PATH=/bin:/sbin + export PATH + # + # configure the localhost + /sbin/ifconfig lo0 127.0.0.1 + # + # configure the ethernet card + /sbin/ifconfig ed0 199.246.76.2 netmask 0xffffff00 + # + # mount the root filesystem via NFS + /sbin/mount antares:/DiskLess/rootfs/altair / + # + # mount the /usr filesystem via NFS + /sbin/mount antares:/DiskLess/usr /usr + # + /usr/X11R6/bin/XF86_SVGA -query antares -xf86config /etc/XF86Config.altair > /dev/null 2>&1 + # + # Reboot after X exits + /sbin/reboot + # + # We blew up.... + exit 1 +</pre> + +<hr> +<p>Any comments and ALL questions welcome....</p> + +<address> +Jerry Kendall<br> +<a href="mailto:jerry@kcis.com">jerry@kcis.com</a> +</address> + +&footer; +</body> +</html> diff --git a/data/tutorials/doc.ftr b/data/tutorials/doc.ftr new file mode 100644 index 0000000000..fed9c481ca --- /dev/null +++ b/data/tutorials/doc.ftr @@ -0,0 +1,8 @@ +<hr> +<a href="../../"><img src="../../gifs/home.gif" alt="FreeBSD Home + Page" border="0" align="right"></a> +<address> + @@UPDATE@@<br> + <a href="../../mailto.html">www@freebsd.org</a> +</address> + diff --git a/data/tutorials/doc.hdr b/data/tutorials/doc.hdr new file mode 100644 index 0000000000..e69de29bb2 diff --git a/data/tutorials/fonts/Makefile b/data/tutorials/fonts/Makefile new file mode 100644 index 0000000000..1778c80e93 --- /dev/null +++ b/data/tutorials/fonts/Makefile @@ -0,0 +1,6 @@ +DOC= fonts +SRCS= fonts.sgml +SGMLOPTS= -ssi + +.include <bsd.sgml.mk> + diff --git a/data/tutorials/fonts/fonts.sgml b/data/tutorials/fonts/fonts.sgml new file mode 100644 index 0000000000..b205cbf8fc --- /dev/null +++ b/data/tutorials/fonts/fonts.sgml @@ -0,0 +1,517 @@ +<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN"> + +<!-- Recently, I wanted to figure out how to use some additional fonts that + I had accumulated. I finally figured out *how to do it* from the various + man pages and documentation. Since it might be of use to other users, + and I didn't see any reference to this topic in the FAQ or handbook, I + thought I'd try my hand at a simple cookbook tutorial addressing the + use of fonts. I have included my unanswered questions at the end of + the document. + + Anyway, here's what I put together. This is my present understanding of + fonts and how to use them with FreeBSD. I am sure that there are errors or + misunderstandings, but it contains enough valid information to allow the + use of additional fonts with Ghostscript, X11 and Groff. This is my first + attempt to write anything along the lines of a tutorial/FAQ, so I am sure + it is pretty raw. There are probably better ways to do some of this stuff, + and I would welcome being corrected. + --> + +<article> + +<title>Fonts and FreeBSD — A Tutorial +<author>Dave Bodenstab, <imdave@synet.net> +<date>Wed Aug 7, 1996 +<abstract> +This document contains a description of the various font files that may +be used with FreeBSD and the syscons driver, X11, Ghostscript and Groff. +Cookbook examples are provided for switching the syscons display to +80x60 mode, and for using type 1 fonts with the above application programs. +</abstract> + +<sect>Introduction + +<p> +There are many sources of fonts available, and one might ask how they might +be used with FreeBSD. +The answer can be found by carefully searching the documentation for the +component that one would like to use. +This is very time consuming, so this tutorial is an attempt to provide a shortcut +for others who might be interested. + +<sect>Basic terminology + +<p> +There are many different font formats and associated font file suffixes. +A few that will be addressed here are: + +<descrip> + +<tag/.pfa .pfb/ Postscript type 1 fonts. The <em/.pfa/ is the <bf/A/scii form +and <em/.pfb/ the <bf/B/inary form. +<tag/.afm/ The font metrics associated with a type 1 font. +<tag/.pfm/ The printer font metrics associated with a type 1 font. +<tag/.ttf/ A TrueType font +<tag/.fot/ An indirect reference to a TrueType font (not an actual font) +<tag/.fon .fnt/ Bitmapped screen fonts + +</descrip> + +<p> +The <em/.fot/ file is used by Windows as sort of a symbolic link to the actual +TrueType font (<em/.ttf/) file. The <em/.fon/ font files are also used by Windows. +I know of no way to use this font format with FreeBSD. + +<sect>What font formats can I use? + +<p> +Which font file format is useful depends on the application being used. +FreeBSD by itself uses no fonts. Application programs and/or drivers may +make use of the font files. Here is a small cross reference of +application/driver to the font type suffixes: + +<descrip> +<tag/Driver/ +<descrip> +<tag/syscons/ .fnt +</descrip> + +<tag/Application/ +<descrip> +<tag/Ghostscript/ <em/.pfa/ <em/.pfb/ <em/.ttf/ +<tag/X11/ <em/.pfa/ <em/.pfb/ +<tag/Groff/ <em/.pfa/ <em/.afm/ +<tag/Povray/ <em/.ttf/ +</descrip> +</descrip> + +<p> +The <em/.fnt/ suffix is used quite frequently. I suspect that whenever someone +wanted to create a specialized font file for their application, more often +than not they chose this suffix. Therefore, it is likely that files with +this suffix are not all the same format; specifically, the <em/.fnt/ files used +by syscons under FreeBSD may not be the same format as a <em/.fnt/ file one +encounters in the MSDOS/Windows environment. I have not made any attempt +at using other <em/.fnt/ files other than those provided with FreeBSD. + +<sect>Setting a virtual console to 80x60 line mode + +<p> +First, a 8x8 font must be loaded. <tt>/etc/sysconfig</tt> should contain the lines: +<tscreen><verb> +# Choose font 8x8 from /usr/share/syscons/fonts/* (or NO for default) +font8x8=/usr/share/syscons/fonts/cp437-8x8.fnt +</verb></tscreen> + +<p> +The command to actually switch the mode is <em/vidcontrol/(1): + +<tscreen><verb> +bash$ vidcontrol VGA_80x60 +</verb></tscreen> + +<p> +Various screen orientated programs, such as <em/vi/(1), must be able to determine +the current screen dimensions. These can be set with <em/stty/(1): + +<tscreen><verb> +bash$ stty crt rows 60 columns 80 +</verb></tscreen> + +<p> +To make this more seamless, one can embed these commands in the startup +scripts so it takes place when the system boots. One way to do this is: + +<enum> +<item> Modify <tt>/etc/sysconfig</tt> as above +<item> Add to <tt>/etc/rc.local</tt>: + +<tscreen><verb> +for tty in /dev/ttyv? +do + vidcontrol VGA_80x60 <$tty >/dev/null 2>&1 +done +</verb></tscreen> + +<item> Add to <tt>/etc/profile</tt>: + +<tscreen><verb> +TTYNAME=`basename \`tty\`` +if expr "$TTYNAME" : 'ttyv' >/dev/null +then + stty crt rows 60 columns 80 +fi +</verb></tscreen> +</enum> + +<p> +References: <em/stty/(1), <em/vidcontrol/(1) + +<sect>Using type 1 fonts with X11 + +<p> +X11 can use either the <em/.pfa/ or the <em/.pfb/ format fonts. The X11 fonts are +located in various subdirectories under <tt>/usr/X11R6/lib/X11/fonts</tt>. Each +font file is cross referenced to +its X11 name by the contents of the <tt/fonts.dir/ file in each directory. +<p> +There is already a directory named <tt/Type1/. +The most straight forward way to add a +new font is to put it into this directory. A better way is to keep all new +fonts in a separate directory and use a symbolic link to the additional +font. This allows one to more easily keep track of ones fonts without +confusing them with the fonts that were originally provided. For example: + +<tscreen><verb> +# Create a directory to contain the font files +bash$ mkdir -p /usr/local/share/fonts/type1 +bash$ cd /usr/local/share/fonts/type1 + +# Place the .pfa, .pfb and .afm files here +# One might want to keep readme files, and other documentation +# for the fonts here also +bash$ cp /cdrom/fonts/atm/showboat/showboat.pfb . +bash$ cp /cdrom/fonts/atm/showboat/showboat.afm . + +# Maintain an index to cross reference the fonts +bash$ echo showboat - InfoMagic CICA, Dec 1994, /fonts/atm/showboat >>INDEX +</verb></tscreen> + +<p> +Now, to use a new font with X11, one must make the font file available and +update the font name files. The X11 font names look like: + +<tscreen><verb> + -bitstream-charter-medium-r-normal-xxx-0-0-0-0-p-0-iso8859-1 + | | | | | | | | | | | | \ \ + | | | | | \ \ \ \ \ \ \ +----+- character set + | | | | \ \ \ \ \ \ \ +- average width + | | | | \ \ \ \ \ \ +- spacing + | | | \ \ \ \ \ \ +- vertical res. + | | | \ \ \ \ \ +- horizontal res. + | | | \ \ \ \ +- points + | | | \ \ \ +- pixels + | | | \ \ \ + foundry family weight slant width additional style +</verb></tscreen> + +<p> +A new name needs to be created for each new font. If you have some information +from the documentation that accompanied the font, then it could serve as the basis +for creating the name. If there is no information, then you can get some idea +by using <em/strings/(1) on the font file. For example: + +<tscreen><verb> +bash$ strings showboat.pfb | more +%!FontType1-1.0: Showboat 001.001 +%%CreationDate: 1/15/91 5:16:03 PM +%%VMusage: 1024 45747 +% Generated by Fontographer 3.1 +% Showboat + 1991 by David Rakowski. Alle Rechte Vorbehalten. +FontDirectory/Showboat known{/Showboat findfont dup/UniqueID known{dup +/UniqueID get 4962377 eq exch/FontType get 1 eq and}{pop false}ifelse +{save true}{false}ifelse}{false}ifelse +12 dict begin +/FontInfo 9 dict dup begin + /version (001.001) readonly def + /FullName (Showboat) readonly def + /FamilyName (Showboat) readonly def + /Weight (Medium) readonly def + /ItalicAngle 0 def + /isFixedPitch false def + /UnderlinePosition -106 def + /UnderlineThickness 16 def + /Notice (Showboat + 1991 by David Rakowski. Alle Rechte Vorbehalten.) readonly def +end readonly def +/FontName /Showboat def +--stdin-- +</verb></tscreen> + +<p> +Using this information, a possible name might be: + +<tscreen><verb> +-type1-Showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1 +</verb></tscreen> + +The components of our name are: +<itemize> +<item>Foundry - lets just name all the new fonts <tt/type1/. +<item>Family - the name of the font. +<item>Weight - normal, bold, medium, semibold, etc. From the <em/strings/(1) output +above, it appears that this font has a weight of <em/medium/. +<item>Slant - <bf/r/oman, <bf/i/talic, <bf/o/blique, etc. Since the <em/ItalicAngle/ +is zero, <em/roman/ will be used. +<item>Width - normal, wide, condensed, extended, etc. Until it can be examined, +the assumption will be <em/normal/. +<item>Additional style - usually omitted, but this will indicate that +the font contains decorative capital letters. +<item>Spacing - proportional or monospaced. <em/Proportional/ is used since <em/isFixedPitch/ is false. +</itemize> + +<p> +All of these names are arbitrary, but one should strive to be compatible +with the existing conventions. A font is referenced by name with possible +wild cards by an X11 program, so the name chosen should make some sense. +One might begin by simply using +<descrip> +<tt/...-normal-r-normal-...-p-.../ +</descrip> +as the name, +and then use <em/xfontsel/(1) to examine it and adjust the name based on +the appearance of the font. + +<p> +So, to complete our example: + +<tscreen><verb> +# Make the font accessible to X11 +bash$ cd /usr/X11R6/lib/X11/fonts/Type1 +bash$ ln -s /usr/local/share/fonts/type1/showboat.pfb . + +# Edit fonts.dir and fonts.scale, adding the line describing the font +# and incrementing the number of fonts which is found on the first line. +bash$ ex fonts.dir +:1p +25 +:1c +26 +. +:$a +showboat.pfb -type1-showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1 +. +:wq + +# fonts.scale seems to be identical to fonts.dir... +bash$ cp fonts.dir fonts.scale + +# Tell X11 that things have changed +bash$ xset fp rehash + +# Examine the new font +bash$ xfontsel -pattern -type1-* +</verb></tscreen> + +<p> +References: <em/xfontsel/(1), <em/xset/(1), <em/The X Windows System in a Nutshell/, +O'Reilly & Associates + +<sect>Using type 1 fonts with Ghostscript + +<p> +Ghostscript references a font via its <tt/Fontmap/ file. This must be modified +in a similar way to the X11 <tt/fonts.dir/ file. Ghostscript can use either the +<em/.pfa/ or the <em/.pfb/ format fonts. Using the font from the previous example, +here is how to use it with Ghostscript: + +<tscreen><verb> +# Put the font in Ghostscript's font directory +bash$ cd /usr/local/share/ghostscript/fonts +bash$ ln -s /usr/local/share/fonts/type1/showboat.pfb . + +# Edit Fontmap so Ghostscript knows about the font +bash$ cd /usr/local/share/ghostscript/4.01 +bash$ ex Fontmap +:$a +/Showboat (showboat.pfb) ; % From CICA /fonts/atm/showboat +. +:wq + +# Use Ghostscript to examine the font +bash$ gs prfont.ps +Aladdin Ghostscript 4.01 (1996-7-10) +Copyright (C) 1996 Aladdin Enterprises, Menlo Park, CA. All rights +reserved. +This software comes with NO WARRANTY: see the file PUBLIC for details. +Loading Times-Roman font from /usr/local/share/ghostscript/fonts/tir_____.pfb... + /1899520 581354 1300084 13826 0 done. +GS>Showboat DoFont +Loading Showboat font from /usr/local/share/ghostscript/fonts/showboat.pfb... + 1939688 565415 1300084 16901 0 done. +>>showpage, press <return> to continue<< +>>showpage, press <return> to continue<< +>>showpage, press <return> to continue<< +GS>quit +</verb></tscreen> + +<p> +References: <tt/fonts.txt/ in the Ghostscript 4.01 distribution + +<sect>Using type 1 fonts with Groff + +<p> +Now that the new font can be used by both X11 and Ghostscript, how can one +use the new font with groff? First of all, since we are dealing with type 1 +postscript fonts, the groff device that is applicable is the <em/ps/ device. +A font file must be created for each font that groff can use. A groff font +name is just a file in <tt>/usr/share/groff_font/devps</tt>. With our example, the +font file could be <tt>/usr/share/groff_font/devps/SHOWBOAT</tt>. The file must be +created using tools provided by groff. + +<p> +The first tool is <em/afmtodit/. This is not normally installed, so it must be +retrieved from the source distribution. I found I had to change the first +line of the file, so I did: + +<tscreen><verb> +bash$ cp /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.pl /tmp +bash$ ex /tmp/afmtodit.pl +:1c +#!/usr/bin/perl -P- +. +:wq +</verb></tscreen> + +<p> +This tool will create the groff font file from the metrics file (<em/.afm/ suffix.) +Continuing with our example: + +<tscreen><verb> +# Many .afm files are in Mac format... ^M delimited lines +# We need to convert them to unix style ^J delimited lines +bash$ cd /tmp +bash$ cat /usr/local/share/fonts/type1/showboat.afm | + tr '\015' '\012' >showboat.afm + +# Now create the groff font file +bash$ cd /usr/share/groff_font/devps +bash$ /tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT +</verb></tscreen> + +<p> +The font can now be referenced with the name SHOWBOAT. + +<p> +If ghostscript is used to drive the printers on the system, then nothing +more needs to be done. However, if true postscript printers are used, then +the font must be down loaded to the printer in order for the font to be used +(unless the printer happens to have the showboat font built in or on an +accessible font disk.) The final step is to create a down loadable font. +The <em/pfbtops/ tool is used to create the <em/.pfa/ format of the font, and the +<tt/download/ file is modified to reference the new font. The <tt/download/ file +must reference the internal name of the font. This can easily be determined +from the groff font file as illustrated: + +<tscreen><verb> +# Create the .pfa font file +bash$ pfbtops /usr/local/share/fonts/type1/showboat.pfb >showboat.pfa +</verb></tscreen> + +<p> +Of course, if the <em/.pfa/ file is already available, just use a symbolic link +to reference it. + +<tscreen><verb> +# Get the internal font name +bash$ fgrep internalname SHOWBOAT +internalname Showboat + +# Tell groff that the font must be down loaded +bash$ ex download +:$a +Showboat showboat.pfa +. +:wq +</verb></tscreen> + +<p> +To test the font: + +<tscreen><verb> +bash$ cd /tmp +bash$ cat >example.t <<EOF +.sp 5 +.ps 16 +This is an example of the Showboat font: +.br +.ps 48 +.vs (\n(.s+2)p +.sp +.ft SHOWBOAT +ABCDEFGHI +.br +JKLMNOPQR +.br +STUVWXYZ +.sp +.ps 16 +.vs (\n(.s+2)p +.fp 5 SHOWBOAT +.ft R +To use it for the first letter of a paragraph, it will look like: +.sp 50p +\s(48\f5H\s0\fRere is the first sentence of a paragraph that uses the +showboat font as its first letter. +Additional vertical space must be used to allow room for the larger +letter. +EOF +bash$ groff -Tps example.t >example.ps + +# To use ghostscript/ghostview +bash$ ghostview example.ps + +# To print it +bash$ lpr -Ppostscript example.ps +</verb></tscreen> + +<p> +References: <tt>/usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.man</tt>, <em/groff_font/(1), +<em/groff_char/(1), <em/pfbtops/(1) + +<sect>Can TrueType fonts be used? + +<p> +The TrueType font format is used by Windows, Windows 95, Mac's,... It is +quite popular and there are a great number of fonts available in this format. +Unfortunately, there are only two applications that I am aware of that can +use this format: Ghostscript and povray. Ghostscript's support, according +to the documentation, is rudimentary and the results are likely to be inferior +to type 1 fonts. + +<p> +However, groff would need a font description file, and I know of no tools +to construct the metrics from a TrueType font. In addition, the font would +have to be down loaded to postscript printers in the appropriate format, +and again, groff cannot handle TrueType fonts in this fashion. + +<p> +X11 has no support for TrueType fonts that I am aware of. + +<p> +The only program that I know of that has the ability to use TrueType fonts +is povray version 3, but I rather doubt many people will be creating documents +as a series of raytraced pages! :-) + +<sect>Where can additional fonts be obtained? + +<p> +Many fonts are available on the Internet. They are either entirely +free, or are share-ware. In addition, there are many inexpensive CDROMs +available that contain many fonts. Some Internet locations (as of August +1996) are: + +<tscreen><verb> +ftp://ftp.winsite.com (Formerly CICA) +http://www.simtel.net/simcgi-bin/dosfind.cgi +ftp://ftp.coast.net/ +http://af-pc-plloyd.ecel.uwa.edu.au/fonts/index.html +http://www.esselte.com/letraset/index.html +http://www.inil.com/users/elfring/esf.htm +</verb></tscreen> + +<sect>Additional questions + +<p> +<itemize> +<item>What use are the <em/.pfm/ files? +<item>Can one generate the <em/.afm/ file from a <em/.pfa/ or <em/.pfb/? +<item>How to generate the groff character mapping files for postscript fonts +with non-standard character names? +<item>Can xditview and devX?? devices be setup to access all the new fonts? +<item>It would be good to have examples of using TrueType fonts with povray and +ghostscript. +</itemize> + +</article> diff --git a/data/tutorials/index.sgml b/data/tutorials/index.sgml new file mode 100644 index 0000000000..d7d92a795f --- /dev/null +++ b/data/tutorials/index.sgml @@ -0,0 +1,35 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [ +<!ENTITY base CDATA ".."> +<!ENTITY date "$Date: 1996-09-24 17:45:57 $"> +<!ENTITY title "FreeBSD Tutorials"> +<!ENTITY % includes SYSTEM "../includes.sgml"> %includes; +]> +<html> +&header; + + <p>Here lie assorted documents on various aspects of FreeBSD, + FreeBSD software, and hardare. If you have comments or + would like to contribute a document, please contact us at + <a href="mailto:doc@freebsd.org">doc@FreeBSD.org</a>.</p> + + <ul> + <li><a href="newuser/newuser.html">For People New to Both FreeBSD <em>and</em> Unix</a> + (<a href="newuser/newuser-html.tar.gz">gzipd tar file</a>)</li> + <li><a href="mh/mh.html">An introduction to the MH mail software</a> + (<a href="mh/mh-html.tar.gz">gzipd tar file</a>)</li> + <li><a href="devel/devel.html">A User's Guide to FreeBSD Programming Tools</a> + (<a href="devel/devel-html.tar.gz">gzipd tar file</a>)</li> + <li><a href="ddwg/ddwg.html">Writing device drivers for FreeBSD</a> + (<a href="ddwg/ddwg-html.tar.gz">gzipd tar file</a>)</li> + <li><a href="multios/multios.html">Using FreeBSD with other operating systems</a> + (<a href="multios/multios-html.tar.gz">gzipd tar file</a>)</li> + <li><a href="fonts/fonts.html">Fonts and FreeBSD</a> + (<a href="fonts/fonts-html.tar.gz">gzipd tar file</a>)</li> + <li><a href="http://www.cypher.net/~black/ipalias.html">IP Aliasing</a></li> + </ul> + + +&footer; +</body> +</html> + diff --git a/data/tutorials/mh/Makefile b/data/tutorials/mh/Makefile new file mode 100644 index 0000000000..e39a8c273f --- /dev/null +++ b/data/tutorials/mh/Makefile @@ -0,0 +1,6 @@ +DOC= mh +SRCS= mh.sgml +SGMLOPTS= -ssi + +.include <bsd.sgml.mk> + diff --git a/data/tutorials/mh/mh.sgml b/data/tutorials/mh/mh.sgml new file mode 100644 index 0000000000..cea321165a --- /dev/null +++ b/data/tutorials/mh/mh.sgml @@ -0,0 +1,572 @@ +<!-- +From matt@garply.com Wed May 22 08:25:18 1996 +Date: Tue, 23 Jan 1996 11:02:50 -0600 +From: Matt Midboe <matt@garply.com> +To: jfieber@freebsd.org +Subject: Introduction to MH for FreeBSD Handbook + +Okay I've diverged from my original plan on the handbook and condensed it a +bit. If I find some time I am going to start working on something about how +to use sendmail, since I imagine that would be a bit more useful. Here is my +guide to using mh on freebsd. Let me know what changes it might need or +things that need to be clearer or shorter. +--> +<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN"> + +<!-- This document explains some about the MUA MH --> + +<article> +<title>An MH Primer +<author>Matt Midboe, <url url="mailto:matt@garply.com" +name="matt@garply.com"> +<date>v1.0, 16 January 1996 +<abstract>This document contains an introduction to using MH on +FreeBSD</abstract> +<toc> + +<sect>Introduction<label id="mhintro"> + +<p> +<!-- This section is here to explain the philosophy behind MH Also + make sure that the user has installed the mh package --> +MH started back in 1977 at the RAND Corporation, where the initial +philosophies behind MH were developed. MH isn't so much a monolithic +email program but a philosophy about how best to develop tools for +reading email. The MH developers have done a great job adhering to the +KISS principle: Keep It Simple Stupid. Rather than have one large +program for reading, sending and handling email they have written +specialized programs for each part of your email life. One might liken +MH to the specialization that one finds in insects and nature. Each +tool in MH does one thing, and does it very well. + +Beyond just the various tools that one uses to handle their email MH +has done an excellent job keeping the configuration of each of these +tools consistent and uniform. In fact, if you are not quite sure how +something is supposed to work or what the arguments for some command +are supposed to be then you can generally guess and be right. Each MH +command is consistent about how it handles reading the configuration +files and how it takes arguments on the command line. One useful thing +to remember is that you can always add a <tt/-help/ to the command to +have it display the options for that command. + +The first thing that you need to do is to make sure that you have +installed the MH package on your FreeBSD machine. If you installed +from CDROM you should be able to execute the following to load mh: +<tscreen><verb> +pkg_add /cdrom/packages/mh-6.8.3.tgz +</verb></tscreen> +You will notice that it created a /usr/local/lib/mh directory for you +as well as adding several binaries to the /usr/local/bin directory. If +you would prefer to compile it yourself then you can anonymous ftp it +from <url url="ftp://ftp.ics.uci.edu/" name="ftp.ics.uci.edu"> or <url +url="ftp://louie.udel.edu/" name="louie.udel.edu">. + +This primer is not a full comprehensive explanation of how MH +works. This is just intended to get you started on the road to +happier, faster mail reading. You should read the man pages for the +various commands. Also you might want to read the <url +url="news:comp.mail.mh" name="comp.mail.mh"> newsgroup. Also you can +read the <url +url="http://www.cis.ohio-state.edu/hypertext/faq/usenet/mh-faq/part1/faq.html" +name="FAQ"> for MH. The best resource for MH is the O'Reilly and +Associates book written by Jerry Peek. + +<sect>Reading Mail +<p> +<!-- This section covers how to use inc, msgchk, next, prev, rmm, and rmf --> +This section covers how to use <tt/inc/, <tt/show/, <tt/scan/, +<tt/next/, <tt/prev/, <tt/rmm/, <tt/rmf/, and <tt/msgchk/. +One of the best things about MH is the consistent interface between +programs. A few things to keep in mind when using these commands is +how to specify message lists. In the case of <em/inc/ this doesn't +really make any sense but with commands like <em/show/ it is useful to +know. + +A message list can consist of something like <tt/23 20 16/ which will +act on messages 23, 20 and 16. This is fairly simple but you can do +more useful things like <tt/23-30/ which will act on all the messages +between 23 and 30. You can also specify something like <tt/cur:10/ +which will act on the current message and the next 9 messages. The +<tt/cur/, <tt/last/, and <tt/first/ messages are special messages that +refer to the current, last or first message in the folder. + +<sect1><heading>inc, msgchk - read in your new email or check it<label id="inc"></> +<p> +If you just type in <em>inc</em> and hit return you will be well on your +way to getting started with MH. The first time you run <em>inc</em> it +will setup your account to use all the MH defaults and ask you about +creating a Mail directory. If you have mail waiting to be downloaded +you will see something that looks like: +<tscreen><verb> + 29 01/15 Doug White Re: Another Failed to boot problem<<On Mon, 15 J + 30 01/16 "Jordan K. Hubbar Re: FBSD 2.1<<> Do you want a library instead of + 31 01/16 Bruce Evans Re: location of bad144 table<<>> >It would appea + 32 01/16 "Jordan K. Hubbar Re: video is up<<> Anyway, mrouted won't run, ev + 33 01/16 Michael Smith Re: FBSD 2.1<<Nate Williams stands accused of sa +</verb></tscreen> +This is the same thing you will see from a ``<ref id="scan">''. If you +just run <em>inc</em> with no arguments it will look on your computer for email +that is supposed to be coming to you. + +A lot of people like to use POP for grabbing their email. MH can do +POP to grab your email. You will need to give <em>inc</em> a few command +line arguments. +<tscreen><verb> +inc -host mail.pop.org -user username -norpop +</verb></tscreen> +That tells <em>inc</> to go to <bf/mail.pop.org/ to download your +email, and that your username on their system is <bf/username/. The +<tt>-norpop</tt> option tells <em>inc</em> to use plain POP3 for +downloading your email. MH has support for a few different dialects of +POP. More than likely you will never ever need to use them +though. While you can do more complex things with inc such as audit +files and scan format files this will get you going. + +The <em/msgchk/ command is used to get information on whether or not +you have new email. <em/msgchk/ takes the same <tt/-host/ and +<tt/-user/ options that <em/inc/ takes. + +<sect1><heading>show, next and prev - displaying and moving through emails +<label id="show"></> +<p> +<em/show/ is to show a letter in your current folder. Like inc, +<em/show/ is a fairly straightfoward command. If you just type +<em/show/ and hit return then it displays the current message. You can +also give specific message numbers to show: +<tscreen><verb> +show 32 45 56 +</verb></tscreen> +This would display message numbers 32, 45 and 56 right after each +other. Unless you change the default behavior <em/show/ basically just +does a more on the email message. + +<em/next/ is used to move onto the next message and <em/prev/ will go +to the previous message. Both commands have an implied <em/show/ +command so that when you go to the next message it automatically +displays it. + +<sect1><heading>scan - shows you a scan of your messages<label id="scan"></> +<p> + +<em/scan/ will display a brief listing of the messages in your current +folder. This is an example of what the <em/scan/ command will give you. +<tscreen><verb> + 30+ 01/16 "Jordan K. Hubbar Re: FBSD 2.1<<> Do you want a library instead of + 31 01/16 Bruce Evans Re: location of bad144 table<<>> >It would appea + 32 01/16 "Jordan K. Hubbar Re: video is up<<> Anyway, mrouted won't run, ev + 33 01/16 Michael Smith Re: FBSD 2.1<<Nate Williams stands accused of sa +</verb></tscreen> +Like just about everything in MH this display is very +configurable. This is the typical default display. It gives you the +message number, the date on the email, the sender, the subject line, +and a sentence fragment from the very beginning of the email if it can +fit it. The + means that message is the current message, so if you do +a <em/show/ it will display that message. + +One useful option for scan is the <tt/-reverse/ option. This will list +your messages with the highest message number first and lowest message +number last. Another useful option with <em/scan/ is to to have it +read from a file. If you want to scan your incoming mailbox on FreeBSD +without having to <em/inc/ it you can do <tt>scan -file +/var/mail/username</tt>. This can be used with any file that is in the +<bf/mbox/ format. + +<sect1><heading>rmm and rmf - remove the current message or folder +<label id="rmm"></> +<p> +<em/rmm/ is used to remove a mail message. The default is typically to +not actually remove the message but to rename the file to one that is +ignored by the MH commands. You will need to through periodically and +physically delete the "removed" messages. + +The <em/rmf/ command is used to remove folders. This doesn't just +rename the files but actually removes the from the hard drive so you +should be careful when you use this command. + +<sect1><heading>A typical session of reading with MH<label id="samplereading"></> +<p> +The first thing that you will want to do is <em/inc/ your new mail. So +at a shell prompt just type in <em/inc/ and hit return. +<tscreen><verb> +tempest% inc +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 +tempest% +</verb></tscreen> +This shows you the new email that has been added to your mailbox. So +the next thing to do is <em/show/ the email and move around. +<tscreen><verb> +tempest% show +Received: by sashimi.wwa.com (Smail3.1.29.1 #2) + id m0tdMZ2-001W2UC; Fri, 19 Jan 96 13:33 CST +Date: Fri, 19 Jan 1996 13:33:31 -0600 (CST) +From: "Stephen L. Lange" <stvlange@wwa.com> +To: matt@garply.com +Subject: Request... +Message-Id: <Pine.BSD.3.91.960119133211.824A-100000@sashimi.wwa.com> +Mime-Version: 1.0 +Content-Type: TEXT/PLAIN; charset=US-ASCII + + +Please remove me as contact for pindat.com + +tempest% rmm +tempest% next +Received: from localhost (localhost [127.0.0.1]) by whydos.lkg.dec.com (8.6.11/8 +.6.9) with SMTP id RAA24416; Fri, 19 Jan 1996 17:56:48 GMT +Message-Id: <199601191756.RAA24416@whydos.lkg.dec.com> +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) +In-Reply-To: Your message of "Fri, 19 Jan 1996 00:18:36 +0100." + <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> +Sender: owner-hackers@FreeBSD.org +Precedence: bulk + + +This is due to a typo in pcireg.h (to +which I am probably the guilty party). +</verb></tscreen> +The <em/rmm/ removed the current message and the <em/next/ command +moved me on to the next message. Now if I wanted to look at ten most +recent messages so I could read one of them here is what I would do: +<tscreen><verb> +tempest% scan last:10 + 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 + 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 +tempest% +</verb></tscreen> +Then if I wanted to read message number 27 I would do a <tt/show 27/ +and it would be displayed. As you can probably tell from this sample +session MH is pretty easy to use and looking through emails and +displaying them is fairly intuitive and easy. + +<sect>Folders and Mail Searching +<p> +Anybody who gets lots of email definately wants to be able to +prioritize, stamp, brief, de-brief, and number their emails in a +variety of different ways. MH can do this better than just about +anything. One thing that we haven't really talked about is the concept +of folders. You have undoubtedly come across the folders concept using +other email programs. MH has folders too. MH can even do sub-folders +of a folder. One thing you should keep in mind with MH is that when +you ran <em/inc/ for the first time and it asked you if it could +create a Mail directory it began storing everything in that +directory. If you look at that directory you will find a directory +named <bf/inbox/. The <bf/inbox/ directory houses all of your incoming +mail that hasn't been thrown anywhere else. + +Whenever you create a new folder a new directory is going to be +created underneath your MH Mail directory, and messages in that folder +are going to be stored in that directory. When new email comes in that +new email is thrown into your inbox directory with a file name that is +equivalent to the message number. So even if you didn't have any of +the MH tools to read your email you could still use standard unix +commands to munge around in those directories and just more your +files. It's this simplicity that really gives you a lot of power with +what you can do with your email. + +Just as you can use message lists like <tt/23 16 42/ with most MH +commands there is a folder option you can specify with just about +every MH command. If you do a <tt/scan +freebsd/ it will scan your +freebsd folder, and your current folder will be changed to freebsd. If +you do a <tt/show +freebsd 23 16 42/ <em/show/ is going to switch to +your freebsd folder and display messages 23, 16 and 42. So remember +that +folder syntax. You will need to make sure you use it to make +commands process different folders. Remember you default folder for +mail is inbox so doing a <tt/folder +inbox/ should always get you back +to your mail. Of course, in MH's infinite flexibility this can be +changed but most places have probably left it as inbox. + +<!-- This section covers how to use pick, folder{s}, and slocal +This needs to cover the general +folder format and an overview on the +directory structure here. --> +<sect1>pick - search email that matches certain criteria +<p> +<em/pick/ is one of the more complex commands in the MH system. So you +might want to read the pick man page for a more thorough +understanding. At its simplest level you can do something like +<tscreen><verb> +tempest% pick -search pci +15 +42 +55 +56 +57 +</verb></tscreen> +This will tell <em/pick/ to look through every single line in every +message in your current folder and tell you which message numbers it +found the word pci in. You can then <em/show/ those messages and read +them if you wish or <em/rmm/ them. You would have to specify something +like <tt/show 15 42 55-57/ to display them though. A slightly more +useful thing to do is this: +<tscreen><verb> +tempest% pick -search pci -seq pick +5 hits +tempest% show pick +</verb></tscreen> +This will show you the same messages you just didn't have to work as +hard to do it. The <tt/-seq/ option is really an abbreviation of +<tt/-sequence/ and <bf/pick/ is just a sequence which contains the +message numbers that matched. You can use sequences with just about +any MH command. So you could have done an <tt/rmm pick/ and all those +messages would be removed instead. You sequence can be named +anything. If you run pick again it will overwrite the old sequence if +you use the same name. + +Doing a <tt/pick -search/ can be a bit more time consuming than just +searching for message from someone, or to someone. So <em/pick/ allows +you to use the following predefined search criteria: +<itemize> +<item><tt/-to/ search based upon who the message is to +<item><tt/-cc/ search based on who is in the cc list +<item><tt/-from/ search for who sent the message +<item><tt/-subject/ search for emails with this subject +<item><tt/-date/ find emails with a matching dat +<item><tt>--<em>component</em></tt> search for any other component in +the header. (i.e. --reply-to to find all emails with a certain +reply-to in the header) +</itemize> + +This allows you to do things like +<tscreen><verb> +pick -to freebsd-hackers@freebsd.org -seq hackers +</verb></tscreen> +to get a list of all the email send to the FreeBSD hackers mailing +list. <em/pick/ also allows you to group these criteria in differents +ways using the following options: +<itemize> +<item>... <tt/-and/ ... +<item>... <tt/-or/ ... +<item><tt/-not/ ... +<item><tt/-lbrace/ ... <tt/-rbrace/ +</itemize> +These commands allow you to do things like +<tscreen><verb> +pick -to freebsd-hackers -and -cc freebsd-hackers +</verb></tscreen> +That will grab all the email in your inbox that was sent to +freebsd-hackers or cc'd to that list. The brace options allow you to +group search criteria together. This is sometimes very necessary as +in the following example +<tscreen><verb> +pick -lbrace -to freebsd-hackers -and -not -cc freebsd-questions -rbrace +-and -subject pci +</verb></tscreen> +Basically this says pick (to freebsd-hackers and not cc'd on +freebsd-questions) and the subject is pci. It should look through your +folder and find all messages send to the freebsd-hackers list that +aren't cc'd to the freebsd-questions list that contain something on +pci in the subject line. Ordinarily you might have to worry about +something called operator precedence. Remember in math how you +evaluate from left to right and you do multiplication and division +first and addition and subtraction second? MH has the same type of +rules for <em/pick/. It's fairly complex so you might want to study +the man page. This document is just to help you get acquainted with +MH. + +<sect1>folder, folders, refile - three useful programs for folder maintenance +<p> +There are three programs which are primarily just for manipulating +your folders. The <em/folder/ program is used to switch between +folders, pack them, and list them. At its simplest level you can do a +<tt/folder +newfolder/ and you will be switched into +<bf/newfolder/. From there on out all your MH commands like <em/comp/, +<em/repl/, <em/scan/, and <em/show/ will act on that <bf/newfolder/ +folder. Sometimes when you are reading and deleting messages you will +develop ``holes'' in your folders. + +If you do a <em/scan/ you might just see messages +34, 35, 36, 43, 55, 56, 57, 80. If you do a <tt/folder -pack/ this +will renumber all your messages so that there are no holes. It doesn't +actually delete any messages though. So you may need to periodically +go through and physically delete <em/rmm/'d messages. + +If you need statistics on your folders you can do a <em/folders/ or +<tt/folder -all/ to list all your folders, how many messages they +have, what the current message is in each one and so on. This line of +stats it displays for all your folders is the same one you get when +you change to a folder with <tt/folder +foldername/. A <em/folders/ +command looks like this: +<tscreen><verb> + Folder # of messages ( range ); cur msg (other files) + announce has 1 message ( 1- 1). + drafts has no messages. + f-hackers has 43 messages ( 1- 43). + f-questions has 16 messages ( 1- 16). + inbox+ has 35 messages ( 1- 38); cur= 37. + lists has 8 messages ( 1- 8). + netfuture has 1 message ( 1- 1). + out has 31 messages ( 1- 31). + personal has 6 messages ( 1- 6). + todo has 58 messages ( 1- 58); cur= 1. + + TOTAL= 199 messages in 13 folders. + +</verb></tscreen> + +The <em/refile/ command is what you use to move messages between +folders. When you do something like <tt/refile 23 +netfuture/ message +number 23 is moved into the netfuture folder. You could also do +something like <tt/refile 23 +netfuture/latest/ which would put +message number 23 in a subfolder called latest under the netfuture +folder. If you want to keep a message in the current folder and link +it you can do a <tt/refile -link 23 +netfuture/ which would keep 23 in +your current inbox but also list in your netfuture folder. You are +probably beginning to realize some of the really powerful things you +can do with MH. + +<sect>Sending Mail +<p> +<!-- This section covers how to use comp, repl and forw --> +Email is a two way street for most people so you want to be able to +send something back. The way MH handles sending mail can be a bit +difficult to follow at first, but it allows for incredible +flexibility. The first thing MH does is to copy a components file into +your outgoing email. A components file is basically a skeleton email +letter with stuff like the To: and Subject: headers already in it. +You are then sent into your editor where you fill in the header +information and then type the body of your message below the dashed +lines in the message. Then to the <em/whatnow/ program. When you are at the +``What now?'' prompt you can tell it to <bf/send/, <bf/list/, +<bf/edit/, <bf/edit/, <bf/push/, and <bf/quit/. Most of these commands +are self-explanatory. So the message sending process involves copying +a component file, editing your email, and then telling the +<em/whatnow/ program what to do with your email. + +<sect1><heading>comp, forw, reply - compose, forward or reply to a message to someone</> +<p> +The <em/comp/ program has a few useful command line options. The most +important one to know right now is the <tt/-editor/ option. When MH is +installed the default editor is usually a program called <em/prompter/ +which comes with MH. It's not a very exciting editor and basically +just gets the job done. So when you go to compose a message to someone +you might want to use <tt/comp -editor /usr/bin/vi/ or <tt/comp +-editor /usr/local/bin/pico/ instead. Once you have run <em/comp/ you +are in your editor and you see something that looks like this: +<tscreen><verb> +To: +cc: +Subject: +-------- + +</verb></tscreen> +You need to put the person you are sending the mail to after the To: +line. It works the same way for the other headers also, so you would +need to put your subject after the Subject: line. Then you would just +put the body of your message after the dashed lines. It may seem a bit +simplistic since a lot of email programs have special requesters that +ask you for this information but there really isn't any point to +that. Plus this really gives you excellent flexibility. +<tscreen><verb> +To:freebsd-rave@freebsd.org +cc: +Subject:And on the 8th day God created the FreeBSD core team +-------- +Wow this is an amazing operating system. Thanks! +</verb></tscreen> +You can now save this message and exit your editor. You will see the +<tt/What now?/ prompt and you can type in <tt/send/ or <tt/s/ and hit +return. Then the freebsd core team will receive their just rewards. As +I mentioned earlier you can also send other commands, for example +<tt/quit/ if you don't want to send the message. + +The <em/forw/ command is stunningly similar. The big difference +being that the message you are forwarding is automatically included in +the outgoing message. When you run <em/forw/ it will forward your +current message. You can always tell it to forward something else by +doing something like <tt/forw 23/ and then message number 23 will be +put in your outgoing message instead of the current message. Beyond +those small differences <em/forw/ functions exactly the same as +<em/comp/. You go through the exact same message sending process. + +The <em/repl/ command will reply to whatever your current message is, +unless you give it a different message to reply to. <em/repl/ will do +its best to go ahead and fill in some of the email headers already. So +you will notice that the To: header already has the address of the +recipient in there. Also the Subject: line will already be filled +in. You then go about the normal message composition process and you +are done. One useful command line option to know here is the <tt/-cc/ +option. You can use <bf/all/, <bf/to/, <bf/cc/, <bf/me/ after the +<tt/-cc/ option to have <em/repl/ automatically add the various +addresses to the cc list in the message. You have probably noticed +that the original message isn't included. This is because most MH +setups are configured to do this from the start. + +<sect1> components, and replcomps - components files for comp and repl +<p> +The <em/components/ file is usually in <tt>/usr/local/lib/mh</tt>. You +can copy that file into your MH Mail directory and edit to contain +what you want it to contain. It is a fairly basic file. You have +various email headers at the top, a dashed line and then nothing. The +<em/comp/ command just copies this <em/components/ file and then edits +it. You can any kind of valid RFC822 header you want. For instance you +could have something like this in your <em/components/ file: +<tscreen><verb> +To: +Fcc: out +Subject: +X-Mailer: MH 6.8.3 +X-Home-Page: http://www.freebsd.org/ +------- +</verb></tscreen> +MH would then copy this components file and throw you into your +editor. The <em/components/ file is fairly simple. If you wanted to +have a signature on those messages you would just put your signature +in that <em/components/ file. + +The <em/replcomps/ file is a bit more complex. The default +<em/replcomps/ looks like this: +<tscreen><verb> +%(lit)%(formataddr %<{reply-to}%?{from}%?{sender}%?{return-path}%>)\ +%<(nonnull)%(void(width))%(putaddr To: )\n%>\ +%(lit)%(formataddr{to})%(formataddr{cc})%(formataddr(me))\ +%<(nonnull)%(void(width))%(putaddr cc: )\n%>\ +%<{fcc}Fcc: %{fcc}\n%>\ +%<{subject}Subject: Re: %{subject}\n%>\ +%<{date}In-reply-to: Your message of "\ +%<(nodate{date})%{date}%|%(pretty{date})%>."%<{message-id} + %{message-id}%>\n%>\ +-------- + +</verb></tscreen> +It's in the same basic format as the <em/components/ file but it +contains quite a few extra formatting codes. The %(lit) command makes +room for the address. The %(formataddr is a function that returns a +proper email address. The next part is %< which means if and the +{reply-to} means the reply-to field in the original message. So that +might be translated this way: + +<tscreen> +%<<bf/if/ {reply-to} <bf/the original message has a reply-to/ +then give that to formataddr, %? <bf/else/ {from} <bf/take the +from address/, %? <bf/else/ {sender} <bf/take the sender address/, %? +<bf/else/ {return-path} <bf/take the return-path from the original +message/, %> <bf/endif/. +</tscreen> + +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 information on writing these format strings is in the +MH-Format man page. The really nice thing is that once you have built +your customized <em/replcomps/ file you won't need to touch it +again. No other email program really gives you the power and +flexibility that MH gives you. +</article> diff --git a/data/tutorials/multios/Makefile b/data/tutorials/multios/Makefile new file mode 100644 index 0000000000..f884339423 --- /dev/null +++ b/data/tutorials/multios/Makefile @@ -0,0 +1,6 @@ +DOC= multios +SRCS= multios.sgml +SGMLOPTS= -ssi + +.include <bsd.sgml.mk> + diff --git a/data/tutorials/multios/multios.sgml b/data/tutorials/multios/multios.sgml new file mode 100644 index 0000000000..8841ffe82d --- /dev/null +++ b/data/tutorials/multios/multios.sgml @@ -0,0 +1,436 @@ +<!-- LinuxDoc file was created by LyX 0.8 (C) 1995 by Matthias Ettrich --> +<!-- Export filter v0.5 by Pascal Andre --> + +<!doctype linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN"> + +<article> + +<title>Installing and Using FreeBSD With Other Operating Systems +<author><url name="Jay Richmond (jayrich@in.net)" url= +"http://www.in.net/~jayrich/doc/mailme.html"> +<date>08/06/96 +<abstract>This document discusses how to make FreeBSD coexist nicely with +other popular operating systems such as <BF>Linux</BF>, <BF>MS-DOS</BF>, +<BF>OS/2</BF>, and <BF>Windows 95</BF>. Special thanks to: Annelise +Anderson <htmlurl url="andrsn@stanford.edu" name="<andrsn@stanford.edu>"> Randall Hopper +<htmlurl url="rhh@ct.picker.com" name="<rhh@ct.picker.com>">and Jordan K. +Hubbard <htmlurl url="jkh@time.cdrom.com" name="<jkh@time.cdrom.com>"> +</abstract> +<toc> + +<sect>Overview + +<p>Most people can't fit these operating systems together comfortably +without having a larger hard disk, so special information on large EIDE drives is included. Because there are so many combinations of possible operating systems and hard disk configurations, the <ref name="examples section" id="5"> may be of the most use to you. It contains descriptions of specific working computer setups that use multiple operating systems. +<p>This document assumes that you have already made room on your hard disk +for an additional operating system. Any time you repartition your hard +drive, you run the risk of destroying the data on the original partitions. However, if your hard drive is completely occupied by DOS, you might find the FIPS utility (included on the FreeBSD CD-ROM in the \TOOLS directory or via ftp at <htmlurl +url="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE/tools" name="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE/tools">) useful. It lets you repartition your hard disk without destroying the data already on it. There is also a commercial program available called +Partition Magic, which lets you size and delete partitions without consequence. + +<sect>Overview of Boot Managers + +<label id="2"><p>These are just brief descriptions of some of the different boot managers you may encounter. Depending on your computer setup, you may find it useful to use more than one of them on the same system. +<p>Boot Easy: This is the default boot manager used with FreeBSD. It has +the ability to boot most anything, including BSD, OS/2 (HPFS), Windows 95 (FAT and FAT32**), and Linux. Partitions are selected with the function keys. +<p>OS/2 Boot Manager: This will boot FAT, HPFS, FFS (FreeBSD), and EXT2 +(Linux). It will also boot FAT32** partitions. Partitions are selected using arrow keys. The OS/2 Boot Manager is the only one to use its own separate partition, unlike the others which +use the master boot record (MBR). Therefore, it must be installed below the 1024th cylinder to avoid booting problems. It can boot Linux using LILO when it is part of the boot sector, not the MBR. Go to +<htmlurl url="http://www.ssc.com/linux/howto.html" name="http://www.ssc.com/linux/howto.html"> on the World Wide Web for more information on booting Linux with OS/2's boot manager. +<p>OS-BS: This is an alternative to Boot Easy. It gives you more control +over the booting process, with the ability to set the default partition to boot and the booting timeout. The 'beta' version of this programs allows you to boot by selecting the OS with +your arrow keys. It is included on the FreeBSD CD in the \TOOLS directory, and via ftp at <htmlurl url="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE/tools" name="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE/tools"> +<p>LILO, or LInux LOader: This is a limited boot manager. Will boot +FreeBSD, though some customization work is required in the LILO configuration file. +<p>** FAT32 is the replacement to the FAT filesystem included in +Microsoft's OEM SR2 Beta release, which is expected to utilitized on computers pre-loaded with Windows 95 towards the end of 1996. It converts the normal FAT file system and allows you to use smaller cluster sizes for larger hard drives. FAT32 also modifies the traditional FAT boot sector and allocation table, +making it incompatible with some boot managers. + +<sect>A Typical Installation + +<label id="3"><P>Let's say I have two large EIDE hard drives, and I want to install FreeBSD, Linux, and Windows 95 on them. +<P>Here's how I might do it using these hard disks: +<enum> +<item>/dev/wd0 (first physical hard disk) +<item>/dev/wd1 (second hard disk) +</enum> +<P>Both disks have 1416 cylinders. +<P>1. I boot from a MS-DOS or Windows 95 boot disk that contains the +FDISK.EXE utility and make a small 50 meg primary partition (35-40 for +Windows 95, plus a little breathing room) on the first disk. Also create +a larger partition on the second hard disk for my Windows applications +and data. +<P>2. I reboot and install Windows 95 (easier said than done) :) on the +"C:" partition. +<P>3. The next thing I do is install Linux. I'm not sure about all the +distributions of Linux, but slackware includes LILO (see <ref name="section 2" id="2">). When I am partitioning out my hard disk with Linux "fdisk," I would put all of Linux on +the first drive (maybe 300 megs for a nice root partition and some +swap space). +<P>4. After I install Linux, and are prompted about installing LILO, +make SURE that I install it on the boot sector of my root Linux +partition, not in the MBR (master boot record). +<P>5. The remaining hard disk space can go to FreeBSD. I also make +sure that my FreeBSD root slice does not go beyond the 1024th +cylinder. (The 1024th cylinder is 528 megs into the disk with our +hypothetical 720MB disks). I will use the rest of the hard drive +(about 270 megs) for the "/usr" and "/" slices if I wish. The rest +of the second hard disk (size depends on the amount of my +Windows application/data partition that I created in step 1 can go +to the "/usr/src" slice and swap space. +<P><VERB> + --------------------------------------------------------------------- + When viewed with the Windows 95 "fdisk" utility, my hard drives + should now look something like this: + + Display Partition Information + + Current fixed disk drive: 1 + + Partition Status Type Volume_Label Mbytes System Usage + C: 1 A PRI DOS 50 FAT** 7% + 2 A Non-DOS (Linux) 300 43% + + Total disk space is 696 Mbytes (1 Mbyte = 1048576 bytes) + + Press Esc to continue + + --------------------------------------------------------------------- + + Display Partition Information + + Current fixed disk drive: 2 + + Partition Status Type Volume_Label Mbytes System Usage + D: 1 A PRI DOS 420 FAT** 60% + + Total disk space is 696 Mbytes (1 Mbyte = 1048576 bytes) + + Press Esc to continue + + ** May say FAT16 or FAT32 if you are using the OEM SR2 update + (see <ref name="section 2" id="2">). + --------------------------------------------------------------------- +</VERB> +<P>6. Install FreeBSD. I make sure to boot with my first hard disk +set at "NORMAL" in the BIOS. If it is not, I'll have the enter my +true disk geometry at boot time (to get this, boot Windows 95 and +consult Microsoft Diagnostics (MSD.EXE), or check your BIOS) with +the parameter "hd0=1416,16,63" where 1416 is the number of +cylinders on my hard disk, 16 is the number of heads per track, +and 63 is the number of sectors per track on the drive. +<P>7. When partitioning out the hard disk, I make sure to install +"Boot Easy" on the first disk. I don't worry about the second disk, +nothing is booting off of it. +<P>8. When I reboot, "Boot Easy" should recognize my three +bootable partitions as DOS (Windows 95), Linux, and BSD (FreeBSD). + +<sect>Special Considerations + +<label id="4"><P>Most operating systems are very picky about where and how they are +placed on the hard disk. Windows 95 and DOS need to be on the first +primary partition on the first hard disk. OS/2 is the exception. It +can be installed on the first or second disk in a primary or extended +partition. If you are not sure, keep the beginning of the bootable +partitions below the 1024th cylinder. +<P>If you install Windows 95 on an existing BSD system, it will "destroy" +the MBR, and you will have to reinstall your previous boot manager. +Boot Easy can be reinstalled by using the BOOTINST.EXE utility +included in the \TOOLS directory on the CD-ROM, and via ftp at <htmlurl +url="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE/tools" +name="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE/tools">. You can also +re-start the installation process and go to the partition editor. +>From there, mark the FreeBSD partition as bootable, select Boot Manager, +and then type W to (W)rite out the information to the MBR. You can now reboot, and +"Boot Easy" should then recognize Windows 95 as "DOS." +<P>Please keep in mind that OS/2 can read FAT and HPFS partitions, +but not FFS (FreeBSD) or EXT2 (Linux) partitions. Likewise, +Windows 95 can only read and write to FAT and FAT32 (see <ref name="section 2" id="2">) partitions. +FreeBSD can read most file systems, but currently cannot read HPFS +partitions. Linux can read HPFS partitions, but can't write to them. +Recent versions of the Linux kernel (2.x) can read and write to +Windows 95 VFAT partitions (VFAT is what gives Windows 95 +long file names - it's pretty much the same as FAT). Linux can read and write to +most file systems. Got that? I hope so. + +<sect>Examples + +<label id="5"><P><EM>(section needs work, please send your example to <htmlurl +url="mailto:jayrich@in.net" name="jayrich@in.net">)</EM>. +<P>FreeBSD+Win95: If you installed FreeBSD after Windows 95, you +should see 'DOS' on the "Boot Easy" menu. This is Windows 95. +If you installed Windows 95 after FreeBSD, read <ref name="section 4" id="4"> above. +As long as your hard disk does not have 1024 cylinders you should not +have a problem booting. If one of your partitions goes beyond the +1024th cylinder however, and you get messages like "invalid system +disk" under DOS (Windows 95) and FreeBSD will not boot, try looking +for a setting in your BIOS called "> 1024 cylinder support" or +"NORMAL/LBA" mode. DOS may need LBA (Logical Block Addressing) in +order to boot correctly. If the idea of switching BIOS settings every +time you boot up doesn't appeal to you, you can boot FreeBSD through +DOS via the FBSDBOOT.EXE utility on the CD (It should find your FreeBSD +partition and boot it.) +<P>FreeBSD+OS/2+Win95: Nothing new here. OS/2's boot manger +can boot all of these operating systems, so that shouldn't be a +problem. +<P>FreeBSD+Linux: You can also use "Boot Easy" to boot both operating +systems. +<P>FreeBSD+Linux+Win95: (see <ref name="section 3" id="3">) + +<label id="sources"><sect>Other Sources of Help + +<P>There are many Linux HOW-TO's that deal with multiple operating +systems on the same hard disk. They are available on the World +Wide Web at <htmlurl url="http://www.ssc.com/linux/howto.html" +name="http://www.ssc.com/linux/howto.html">. +<P>The Linux+OS/2+DOS Mini-HOWTO offers help on configuring the +OS/2 boot manager. It is also available on the WWW at: +<htmlurl url="http://sunsite.unc.edu/mdw/HOWTO/mini/Linux+OS2+DOS" +name="http://sunsite.unc.edu/mdw/HOWTO/mini/Linux+OS2+DOS">. +And the <htmlurl url="http://www.in.net/~jkatz/win95/Linux-HOWTO.html" name="http://www.in.net/~jkatz/Linux-HOWTO.html"> is also helpful. +<P>The NT Loader Hacking Guide provides good information on multibooting +Windows NT, '95, and DOS with other operating systems. It's available at +<htmlurl url="http://www.dorsai.org/~dcl/publications/NTLDR_Hacking" +name="http://www.dorsai.org/~dcl/publications/NTLDR_Hacking">. +<P>And Hale Landis's "How It Works" document pack contains some good info +on all sorts of disk geometry and booting related topics. Here are a few +links that might help you find it: <htmlurl +url="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip" +name="ftp://fission.dt.wdc.com/pub/otherdocs/pc_systems/how_it_works/allhiw.zip">, +<htmlurl url="http://www.cs.yorku.ca/People/frank/docs/" +name="http://www.cs.yorku.ca/People/frank/docs/">. +<P>Finally, don't overlook FreeBSD's kernel documentation on the booting +procedure, available in the kernel source distribution (it unpacks to +<htmlurl url="file:/usr/src/sys/i386/boot/biosboot/README.386BSD" +name="file:/usr/src/sys/i386/boot/biosboot/README.386BSD">. + +<sect>Technical Details + +<P><EM>(Contributed by Randall Hopper <htmlurl +url="rhh@ct.picker.com" name="<rhh@ct.picker.com>">)</EM> +<P>This section attempts to give you enough basic information about +your hard disks and the disk booting process so that you can +troubleshoot most problems you might encounter when getting set up to +boot several operating systems. It starts in pretty basic terms, so you may want +to skim down in this section until it begins to look unfamiliar and then start +reading. + +<sect1>Disk Primer + +<P>Three fundamental terms are used to describe the location of +data on your hard disk: Cylinders, Heads, and Sectors. It's not +particularly important to know what these terms relate to except to +know that, together, they identify where data is physically on your +disk. +<P>Your disk has a particular number of cylinders, number of heads, +and number of sectors per cylinder-head (a cylinder-head also known +nown as a track). Collectively this information defines the +"physical disk geometry" for your hard disk. There are typically 512 +bytes per sector, and 63 sectors per track, with the number of +cylinders and heads varying widely from disk to disk. Thus you can +figure the number of bytes of data that'll fit on your own disk by +calculating: +<VERB> + (# of cylinders) * (# heads) * (63 sectors/track) * (512 bytes/sect) + +</VERB> +<P>For example, on my 1.6 Gig Western Digital AC31600 EIDE hard disk,that's: +<VERB> + (3148 cyl) * (16 heads) * (63 sectors/track) * (512 bytes/sect) + +</VERB> +<P>which is 1,624,670,208 bytes, or around 1.6 Gig. +<P>You can find out the physical disk geometry (number of +cylinders, heads, and sectors/track counts) for your hard disks using +ATAID or other programs off the net. Your hard disk probably came +with this information as well. Be careful though: if you're using +BIOS LBA (see <ref name="section 7.3" id="limits">), you +can't use just any program to get the physical geometry. This is because +many programs (e.g. MSD.EXE or FreeBSD fdisk) don't identify the physical +disk geometry; they instead report the "translated geometry" (virtual +numbers from using LBA). Stay tuned for what that means. +<P>One other useful thing about these terms. Given 3 numbers -- a +cylinder number, a head number, and a sector-within-track number -- +you identify a specific absolute sector (a 512 byte block of data) on +your disk. Cylinders and Heads are numbered up from 0, and Sectors +are numbered up from 1. +<P>For those that are interested in more technical details, information on +disk geometry, boot sectors, BIOSes, etc. can be found all over the net. +Query Lycos, Yahoo, etc. for "boot sector" or "master boot record". +Among the useful info you'll find are Hale Landis's "How It Works" +document pack. See the <ref name="Other Sources of Help" id="sources"> +section for a few pointers to this pack. + +<P>Ok, enough terminology. We're talking about booting here. + +<sect1><heading>The Booting Process<label id="booting"></heading> + +<P>On the first sector of your disk (Cyl 0, Head 0, Sector 1) lives +the Master Boot Record (MBR). It contains a map of your disk. It +identifies up to 4 "partitions", each of which is a contiguous chunk +of that disk. FreeBSD calls partitions "slices" to avoid confusion +with it's own partitions, but we won't do that here. Each partition +can contain its own operating system. +<P>Each partition entry in the MBR has a "Partition ID", a "Start +Cylinder/Head/Sector", and an "End Cylinder/Head/Sector". The +Partition ID tells what type of partition it is (what OS) and the +Start/End tells where it is. Here's a smattering of some common +Partition IDs: +<VERB> + ID (hex) DESCRIPTION + 01 ...... Primary DOS12 (12-bit FAT) + 04 ...... Primary DOS16 (16-bit FAT) + 05 ...... Extended DOS + 06 ...... Primary big DOS (> 32MB) + 0A ...... OS/2 + 83 ...... Linux (EXT2FS) + A5 ...... FreeBSD, NetBSD, 386BSD (UFS) +</VERB> +<P>Note that not all partitions are bootable (e.g. Extended DOS). +Some are -- some aren't. What makes a partition bootable is the +configuration of the "Partition Boot Sector" that exists at the +beginning of each partition. +<P>When you configure your favorite boot manager, it looks up the entries +in the MBR partition tables of all your hard disks and lets you name the +entries in that list. Then when you boot, the boot manager is invoked by +special code in the Master Boot Sector of the first probed hard disk on +your system. It looks at the MBR partition table entry corresponding to +the partition choice you made, uses the Start Cylinder/Head/Sector +information for that partition, loads up the Partition Boot Sector for that +partition, and gives it control. That Boot Sector for the partition itself +contains enough information to start loading the operating system on that +partition. +<P>One thing we just brushed past that's important to know. All of your +hard disks have MBRs. However, the one that's important is the one on the +disk that's first probed by the BIOS. If you have only IDE hard disks, its +the first IDE disk (e.g. primary disk on first controller). Similarly for +SCSI only systems. If you have both IDE and SCSI hard disks though, the +IDE disk is typically probed first by the BIOS, so the first IDE disk is +the first probed disk. The boot manager you will install will be hooked into +the MBR on this first probed hard disk that we've just described. + + +<sect1>Booting Limitations and Warnings + +<label id="limits"><P>Now the interesting stuff that you need to watch out for. +<P><BF>1. The dreaded 1024 cylinder limit and how BIOS LBA helps</BF> +<P>The first part of the booting process is all done through the +BIOS, (if that's a new term to you, the BIOS is a software chip on +your system motherboard which provides startup code for your +computer). As such, this first part of the process is subject to the +limitations of the BIOS interface. +<P>The BIOS interface used to read the hard disk during this period +(INT 13H, Subfunction 2) allocates 10 bits to the Cylinder Number, 8 +bits to the Head Number, and 6 bits to the Sector Number. This +restricts users of this interface (i.e. boot managers hooked into +your disk's MBR as well as OS loaders hooked into the Boot Sectors) +to the following limits: +<VERB> + 1024 cylinders, max + 256 heads , max + 64 cylinders, max (actually 63 -- "0" isn't available) +</VERB> +<P>Now big hard disks have lots of cylinders but not a lot of +heads, so invariably with big hard disks the number of cylinders is +greater than 1024. Given this and the BIOS interface as is, you +can't boot off just anywhere on your hard disk. The boot code (the +boot manager and the OS loader hooked into all bootable partitions' +Boot Sectors) has to reside below cylinder 1024. In fact, if your +hard disk is typical and has 16 heads, this equates to: +<VERB> + 1024 cyl/disk * 16 heads/disk * 63 sect/(cyl-head) * 512 bytes/sector +</VERB> +<P>which is around the often-mentioned 528MB limit. +<P>This is where BIOS LBA (Logical Block Addressing) comes in. BIOS LBA +gives the user of the BIOS API calls access to physical cylinders above +1024 though the BIOS interfaces by "redefining" a cylinder. That is, it +remaps your cylinders and heads, making it appear through the BIOS as +though the disk has "fewer" cylinders and "more" heads than it actually +does. In other words, it takes advantage of the fact that hard disks have +relatively few heads and lots of cylinders by shifting the balance between +number of cylinders and number of heads so that both numbers lie below the +above-mentioned limits (1024 cylinders, 256 heads). + +<P>With BIOS LBA, the hard disk size limitation is virtually +removed (well, pushed up to 8 Gigabytes anyway). If you have an LBA +BIOS, you can put FreeBSD or any OS anywhere you want and not hit the +1024 cylinder limit. + +<P>To use my my 1.6 Gig Western Digital as an example again, it's +physical geometry is: +<VERB> + (3148 cyl, 16 heads, 63 sectors/track, 512 bytes/sector) +</VERB> +<P>However, my BIOS LBA remaps this to: +<VERB> + ( 787 cyl, 64 heads, 63 sectors/track, 512 bytes/sector) +</VERB> +<P>giving the same effective size disk, but with cylinder and head +counts within the BIOS API's range (Incidentally, I have both Linux and +FreeBSD existing on one of my hard disks above the 1024th physical +cylinder, and both operating systems boot fine, thanks to BIOS LBA). +<P><BF>2. Boot Managers and Disk Allocation</BF> +<P>Another gotcha to watch out when installing boot managers is +allocating space for your boot manager. It's best to be aware of +this issue up front to save yourself from having to reinstall one or +more of your OSs. +<P>If you followed the discussion in <ref name="section 7.2" id="booting"> +about the Master Boot Sector (where the MBR is), Partition Boot Sectors, and the booting +process, you may have been wondering just exactly where on your hard +disk that nifty boot manager is going to live. Well, some boot +managers are small enough to fit entirely within the Master Boot +Sector (Cylinder 0, Head 0, Sector 0) along with the partition table. +Others need a bit more room and actually extend a few sectors past +the Master Boot Sector in the Cylinder 0 Head 0 track, since that's +typically free...typically. +<P>That's the catch. Some operating systems (FreeBSD included) let +you start their partitions right after the Master Boot Sector at +Cylinder 0, Head 0, Sector 2 if you want. In fact, if you give +FreeBSD's sysinstall a disk with an empty chunk up front or the whole +disk empty, that's where it'll start the FreeBSD partition by default +(at least it did when I fell into this trap :-). Then when you go to +install your boot manager, if it's one that occupies a few extra +sectors after the MBR, it'll overwrite the front of the first +partition's data. In the case of FreeBSD, this overwrites the +disk label, and renders your FreeBSD partition unbootable. +<P>The easy way to avoid this problem (and leave yourself the +flexibility to try different boot managers later) is just to always +leave the first full track on your disk unallocated when you +partition your disk. That is, leave the space from Cylinder 0, Head +0, Sector 2 through Cylinder 0, Head 0, Sector 63 unallocated, and +start your first partition at Cylinder 0, Head 1, Sector 1. +For what it's worth, when you create a DOS partition at the +front of your disk, DOS leaves this space open by default (this is +why some boot managers assume it's free). So creating a DOS +partition up at the front of your disk avoids this problem +altogether. I like to do this myself, creating 1 Meg DOS partition +up front, because it also avoids my primary DOS drive letters +shifting later when I repartition. +<P>For reference, the following boot managers use the +Master Boot Sector to store their code and data: +<itemize> +<item>OS-BS 1.35 +<item>Boot Easy +<item>LILO +</itemize> +<P>These boot managers use a few additional sectors after the +Master Boot Sector: +<itemize> +<item>OS-BS 2.0 Beta 8 (sectors 2-5) +<item>OS/2's boot manager +</itemize> +<P><BF>3. What if your machine won't boot?</BF> +<P>At some point when installing boot managers, you might leave the +MBR in a state such that your machine won't boot. This is unlikely, +but possible when re-FDISKing underneath an already-installed boot +manager. +<P>If you have a bootable DOS partition on your disk, you can boot +off a DOS floppy, and run: +<VERB> + FDISK /MBR +</VERB> +<P>to put the original, simple DOS boot code back into the system. You can +then boot DOS (and DOS only) off the hard drive. Alternatively, just +re-run your boot manager installation program off a bootable floppy. + +</article> + diff --git a/data/tutorials/newuser/Makefile b/data/tutorials/newuser/Makefile new file mode 100644 index 0000000000..d8d8509284 --- /dev/null +++ b/data/tutorials/newuser/Makefile @@ -0,0 +1,5 @@ +DOC= newuser +SRCS= newuser.sgml + +.include <bsd.sgml.mk> + diff --git a/data/tutorials/newuser/newuser.sgml b/data/tutorials/newuser/newuser.sgml new file mode 100644 index 0000000000..081910225b --- /dev/null +++ b/data/tutorials/newuser/newuser.sgml @@ -0,0 +1,537 @@ +<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN"> + +<article> +<title>For People New to Both FreeBSD <em>and</em> Unix +<author>Annelise Anderson + <htmlurl url="mailto:andrsn@hoover.stanford.edu" + name="<andrsn@hoover.stanford.edu>"> +<date>June 30, 1996 + +<abstract>Congratulations on installing FreeBSD! +This introduction is for people new to both FreeBSD +<em>and</em> Un*x---so it starts with basics. It assumes you're using +version 2.0.5 or later of FreeBSD as distributed by Walnut Creek +or FreeBSD.ORG, your system (for now) has a single user +(you)---and you're probably pretty good with DOS/Windows or OS/2. +</abstract> + +<toc> + +<!-- ************************************************************ --> +<sect>Logging in and Getting Out + +<p>Log in (when you see <tt>login:</tt>) as a user you created during +installation or as <em>root</em>. (Your FreeBSD installation will already +have an account for root; root can go anywhere and do anything, +including deleting essential files, so be careful!) + +To log out (and get a new <tt>login</tt> prompt) type +<tscreen> +exit +</tscreen> +as often as necessary. Yes, press <em>enter</em> after commands, and remember +that Unix is case-sensitive---<tt>exit</tt>, not <tt>EXIT</tt>. + +To shut down the machine type: +<tscreen> +/sbin/shutdown -h now +</tscreen> +Or to reboot type +<tscreen> +/sbin/shutdown -r now +</tscreen> +or +<tscreen> +/sbin/reboot +</tscreen> +You can also reboot with +<tt>Ctrl-Alt-Delete</tt>. Give it a little time to do its work. This is +equivalent to <tt>/sbin/reboot</tt> in recent releases of FreeBSD, and is +much, much better than hitting the reset button. You don't want to +have to reinstall this thing, do you? + +<!-- ************************************************************ --> +<sect>Adding A User with Root Privileges + +<p>If you didn't create any users when you installed the system and +are thus logged in as root, you should probably create a user now with +<tscreen> +adduser +</tscreen> +Don't use the <tt>-verbose</tt> option; the defaults are what you +want. Suppose you create a user <em>jack</em> with full name +<em>Jack Benimble</em>. Give jack a password if security (even +kids around who might pound on the keyboard) is an issue. When +it asks you if you want to invite jack into other groups, type +<tscreen> +wheel +</tscreen> +This will make it possible to log in as <em>jack</em> and use the <tt>su</tt> command to +become root. Then you won't get scolded any more for logging in as +root, and as root you'll have the same environment as jack +(this is good). + +You can quit <tt>adduser</tt> any time by typing <tt>Ctrl-C</tt>, and at the end +you'll have a chance to approve your new user or simply type <tt>n</tt> for no. +You might want to create a second newuser (jill?) so that when you edit +jack's login files, you'll have a hot spare in case something goes wrong. + +Once you've done this, use <tt>exit</tt> to get back to a login prompt and log +in as <em>jack</em>. In general, it's a good idea to do as +much work as possible as an ordinary user who doesn't have the +power---and risk---of root. + +If you already created a user and you want the user to be able to <tt>su</tt> +to root, you can log in as root and edit the file <tt>/etc/group</tt>, adding +jack to the first line (the group wheel). But first you need to +practice <tt>vi</tt>, the text editor. + +<!-- ************************************************************ --> +<sect>Looking Around + +<p>Logged in as an ordinary user, look around and try out some commands that +will access the sources of help and information within FreeBSD. + +Here are some commands and what they do: +<descrip> +<tag/<tt>id</tt>/ Tells you who you are! +<tag/<tt>pwd</tt>/ Shows you where you are---the current + working directory. +<tag/<tt>ls</tt>/ Lists the files in the current directory. +<tag/<tt>ls -F</tt>/ Lists the files in the current directory + with a * after + executables, a / after directories, and an @ after symbolic + links. +<tag/<tt>ls -l</tt>/ Lists the files in long format---size, + date, permissions. +<tag/<tt>ls -a</tt>/ Lists hidden (unless you're root) ``dot'' + files with the others. +<tag/<tt>cd</tt>/ Changes directories. <tt>cd ..</tt> backs up + one level; note the + space after <tt>cd</tt>. <tt>cd /usr/local</tt> + goes there. <tt>cd ~</tt> goes to + the home directory of the person logged in---e.g., + <tt>/usr/home/jack</tt>. Try <tt>cd /cdrom</tt>, + and then <tt>ls</tt>, to find out + if your cdrom is mounted and working. +<tag/<tt>view <em>filename</em></tt>/ + Lets you look at a file (named <em>filename</em> + without changing + it. Try <tt>view /etc/fstab</tt>. <tt>:q</tt> to quit. +<tag/<tt>cat <em>filename</em></tt>/ + Displays <em>filename</em> on screen. If it's too long and you + can see only the end of it, press <tt>ScrollLock</tt> and use + the <tt>up-arrow</tt> to move backward; you can + use <tt>ScrollLock</tt> with + man pages too. Press <tt>ScrollLock</tt> again + to quit scrolling. + You might want to try <tt>cat</tt> on some of the + dot files in your + home directory---<tt>cat .cshrc</tt>, <tt>cat .login</tt>, + <tt>cat .profile</tt>. +</descrip> +You'll notice aliases in <tt>.cshrc</tt> +for some of the <tt>ls</tt> commands (they're very convenient). You can create +other aliases by editing <tt>.cshrc</tt>. You can make these aliases +available to all users on the system by putting them in the system-wide +csh configuration file, <em>/etc/csh.cshrc</em>. + +<!-- ************************************************************ --> +<sect>Getting Help and Information + +<p>Here are some useful sources of help. ``text'' stands for something of +your choice that you type in---usually a command or filename. +<descrip> +<tag/<tt>apropos <em>text</em></tt>/ + Everything containing string <em>text</em> + in the whatis database. +<tag/<tt>man <em>text</em></tt>/ + The man page for <em>text</em>. + The major source of documentation + for Un*x systems. <tt>man ls</tt> will tell you + all the ways to + use the <tt>ls</tt> command. Press <tt>Enter</tt> to + move through text, <tt>Ctrl-b</tt> + to go back a page, <tt>Ctrl-f</tt> to go forward, + <tt>q</tt> or <tt>Ctrl-c</tt> to quit. +<tag/<tt>which <em>text</em></tt>/ + Tells you where in the user's path the command + <em>text</em> is found. +<tag/<tt>locate <em>text</em></tt>/ + All the paths where the string <tt>text</tt> is found. +<tag/<tt>whatis <em>text</em></tt>/ + Tells you what the command <tt>text</tt> does and its man page. +<tag/<tt>whereis <em>text</em></tt>/ + Finds the file <em>text</em>, giving its full path. +</descrip> + +You might want to try using <tt>whatis</tt> on some common useful +commands like <tt>cat</tt>, <tt>more</tt>, <tt>grep</tt>, +<tt>mv</tt>, <tt>find</tt>, <tt>tar</tt>, <tt>chmod</tt>, +<tt>chown</tt>, <tt>date</tt>, and <tt>script</tt>. +<tt>more</tt> lets you read a page at a time as it does in DOS, +e.g., <tt>ls -l | more</tt> or <tt>more <em>filename</em></tt>. The +<tt>*</tt> works as a wildcard---e.g., <tt>ls w*</tt> will show +you files beginning with w. + +Are some of these not working very well? Both <tt>locate</tt> +and <tt>whatis</tt> depend on a database that's rebuilt weekly. +If your machine isn't going to be left on over the weekend (and +running FreeBSD), you might want to run the commands for daily, +weekly, and monthly maintenance now and then. Run them as root +and give each one time to finish before you start the next one, +for now. +<tscreen> +/etc/daily<newline> +/etc/weekly<newline> +/etc/monthly +</tscreen> +If you get tired waiting, press <tt>Alt-F2</tt> to get another +virtual console, and log in again. After all, it's a multi-user, +multi-tasking system. Nevertheless these commands will probably +flash messages on your screen while they're running; you can type +<tt>clear</tt> at the prompt to clear the screen. Once they've run, you +might want to look at <tt>/var/mail/root</tt> and +<tt>/var/log/messages</tt>. + +Basically running such commands is part of system administration---and as +a single user of a Unix system, you're your own system administrator. +Virtually everything you need to be root to do is system administration. +Such responsibilities aren't covered very well even in those big fat books +on Unix, which seem to devote a lot of space to pulling down menus in +windows managers. You might want to get one of the two leading books +on systems administration, either Evi Nemeth et.al.'s <em>UNIX System +Administration Handbook</em> (Prentice-Hall, 1995, ISBN 0-13-15051-7)---the +second edition with the red cover; or Æleen Frisch's <em>Essential System +Administration</em> (O'Reilly & Associates, 1993, ISBN 0-937175-80-3). +I used Nemeth. + +<!-- ************************************************************ --> +<sect>Editing Text + +<p>To configure your system, you need to edit text files. Most +of them will be in the <tt>/etc</tt> directory; and you'll need +to <tt>su</tt> to root to be able to change them. The text +editor is <tt>vi</tt>. Before you edit a file, you should +probably back it up. Suppose you want to edit +<tt>/etc/sysconfig</tt>. You could just use <tt>cd /etc</tt> to +get to the <tt>/etc</tt> directory and do: +<tscreen> +cp sysconfig sysconfig.orig +</tscreen> +This would copy <tt>sysconfig</tt> to <tt>sysconfig.orig</tt>, +and you could later copy <tt>sysconfig.orig</tt> to +<tt>sysconfig</tt> to recover the original. But even better +would be moving (renaming) and then copying back: +<tscreen> +mv sysconfig sysconfig.orig<newline> +cp sysconfig.orig sysconfig +</tscreen> +because the <tt>mv</tt> command preserves the original date and +owner of the file. You can now edit <tt>sysconfig</tt>. If you +want the original back, you'd then <tt>mv sysconfig syconfig.myedit</tt> +(assuming you want to preserve your edited version) and then +<tscreen> +mv sysconfig.orig sysconfig +</tscreen> +to put things back the way they were. + +To edit a file, type +<tscreen> +vi filename +</tscreen> +Move through the text with the arrow keys. <tt>Esc</tt> (the +escape key) puts <tt>vi</tt> in command mode. Here are some +commands: +<descrip> + <tag/<tt>x</tt>/ delete letter the cursor is on + <tag/<tt>dd</tt>/ delete the entire line (even if + it wraps on the screen) + <tag/<tt>i</tt>/ insert text at the cursor + <tag/<tt>a</tt>/ insert text after the cursor +</descrip> +Once you type <tt>i</tt> or <tt>a</tt>, you can enter text. +<tt>Esc</tt> puts you back in command mode where you can type +<descrip> + <tag/<tt>:w</tt>/ to write your changes to disk and continue editing + <tag/<tt>:wq</tt>/ to write and quit + <tag/<tt>:q!</tt>/ to quit without saving changes + <tag><tt>/<em>text</em></tt></tag> to move the cursor + to <em>text</em>; <tt>/Enter</tt> (the enter + key) to find the next instance of <em>text</em>. + <tag/<tt>G</tt>/ to go to the end of the file + <tag/<tt><em>n</em>G</tt>/ to go to line <em>n</em> in + the file, where <em>n</em> is a number + <tag/<tt>Ctrl-L</tt>/ to redraw the screen + <tag/<tt>Ctrl-b</tt> and <tt>Ctrl-f</tt>/ go back + and forward a screen, as they + do with <tt>more</tt> and <tt>view</tt>. +</descrip> + +Practice with <tt>vi</tt> in your home directory by creating a +new file with <tt>vi filename</tt> and adding and deleting text, +saving the file, and calling it up again. <tt>vi</tt> delivers +some surprises because it's really quite complex, and sometimes +you'll inadvertently issue a command that will do something you +don't expect. (Some people actually like <tt>vi</tt>---it's more +powerful than DOS EDIT---find out about the <tt>:r</tt> command.) +Use <tt>Esc</tt> one or more times to be sure you're in command +mode and proceed from there when it gives you trouble, save often +with <tt>:w</tt>, and use <tt>:q!</tt> to get out and start over +(from your last <tt>:w</tt>) when you need to. + +Now you can <tt>cd</tt> to <tt>/etc</tt>, <tt>su</tt> to root, +use <tt>vi</tt> to edit the file <tt>/etc/group</tt>, and add a +user to wheel so the user has root privileges. Just add a comma +and the user's login name to the end of the first line in the +file, press <tt>Esc</tt>, and use <tt>:wq</tt> to write the file +to disk and quit. Instantly effective. (You didn't put a space +after the comma, did you?) + +<!-- ************************************************************ --> +<sect>Printing Files from DOS + +<p>At this point you probably don't have the printer working, so here's a +way to create a file from a man page, move it to a floppy, and then +print it from DOS. Suppose you want to read carefully about changing +permissions on files (pretty important). You can use the command +man chmod to read about it. The command +<tscreen> +man chmod > chmod.txt +</tscreen> +will send the man page to the <tt>chmod.txt</tt> file instead of showing it on +your screen. Now put a dos-formatted diskette in your floppy drive a, +<tt>su</tt> to root, and type +<tscreen> +/sbin/mount -t msdos /dev/fd0 /mnt +</tscreen> +to mount the floppy drive on <tt>/mnt</tt>. + +Now (you no longer need to be root, and you can type <tt>exit</tt> to get +back to being user jack) you can go to the directory where you created +chmod.txt and copy the file to the floppy with: +<tscreen> +cp chmod.txt /mnt +</tscreen> +and use <tt>ls /mnt</tt> to get a directory listing of +<tt>/mnt</tt>, which should show the file <tt>chmod.txt</tt>. + +You might especially want to make a file from <tt>/sbin/dmesg</tt> by typing +<tscreen> +/sbin/dmesg > dmesg.txt +</tscreen> +and copying <tt>dmesg.txt</tt> to the floppy. <tt>/sbin/dmesg</tt> is the boot + log record, +and it's useful to understand it because it shows what FreeBSD found +when it booted up. If you ask questions on questions@freebsd.org or on +a USENET group---like ``FreeBSD isn't finding my tape drive, what do I +do?''---people will want to know what <tt>dmesg</tt> has to say. + +You can now dismount the floppy drive (as root) to get the disk out with +<tscreen> +/sbin/umount /mnt +</tscreen> +or reboot to go to DOS. Copy these files to a DOS directory, call them +up with DOS EDIT, Windows Notepad, or a word processor, make a minor +change so the file has to be saved, and print as you normally would +from DOS or Windows. Hope it works! man pages come out best if printed +with the dos <tt>print</tt> command. (Copying files from FreeBSD to a mounted +dos partition is in some cases still a little risky.) + +Getting the printer printing from FreeBSD involves +creating an appropriate entry in <tt>/etc/printcap</tt> and creating +a matching spool directory in <tt>/var/spool/output</tt>. If your +printer is on lpt0 (what dos calls LPT1), you may only need to +go to <tt>/var/spool/output</tt> and (as root) create the directory +lpd by typing: + +<tscreen> +mkdir lpd +</tscreen> +Then the printer should respond if it's turned on when the +system is booted, and lp or lpr should send a file to the printer. +Whether or not the file actually prints depends on configuring it, which is +covered in the FreeBSD handbook. +<!-- ************************************************************ --> +<sect>Other Useful Commands + +<p><descrip> +<tag/<tt>df</tt>/ shows file space and mounted systems. +<tag/<tt>ps aux</tt>/ shows processes running. <tt>ps ax</tt> is a narrower form. +<tag/<tt>lsdev</tt>/ lists configured devices +<tag/<tt>devmenu</tt>/ a menu of devices---in color! +<tag/<tt>rm <em>filename</em></tt>/ remove <tt>filename</tt> +<tag/<tt>rm -R <em>dir</em></tt>/ removes a directory <tt>dir</tt> and all + subdirectories---careful! +<tag/<tt>ls -R</tt>/ lists files in the current + directory and all subdirectories; + I used a variant, <tt>ls -AFR > where.txt</tt>, + to get a list of all + the files in <tt>/</tt> and (separately) + <tt>/usr</tt> before I found better + ways to find files. +<tag/<tt>passwd</tt>/ to change user's password (or root's password) +<tag/<tt>man hier</tt>/ man page on the Unix file system +</descrip> +Use find to locate filename in <tt>/usr</tt> or any of its subdirectories with +<tscreen> +find /usr -name "<em>filename</em>" +</tscreen> +You can use <tt>*</tt> as a wildcard in <tt>"<em>filename</em>"</tt> +(which should be in quotes). If you tell find to search in +<tt>/</tt> instead of <tt>/usr</tt> it will look for the file(s) +on all mounted file systems, including the cdrom and the dos +partition. + +An excellent book that explains Unix commands and utilities is +Abrahams & Larson, <em>Unix for the Impatient</em> (2nd ed., +Addison-Wesley, 1996). There's also a lot of Unix information on +the Internet. Try the <url +url="http://www.eecs.nwu.edu/unix.html" name="Unix Reference +Desk">. + +<!-- ************************************************************ --> +<sect>Next Steps + +<p>You should now have the tools you need to get around and edit +files, so you can get everything up and running. There is a +great deal of information in the FreeBSD handbook (which is +probably on your hard drive) and <url +url="http://www.freebsd.org" name="FreeBSD's web site">. A wide +variety of packages and ports are on the <htmlurl +url="http://www.cdrom.com" name="Walnut Creek"> cdrom as well as +the web site. The handbook tells you more about how to use them +(get the package if it exists, with <tt>pkg_add +/cdrom/packages/All/<em>packagename</em></tt>, where +<em>packagename</em> is the filename of the package). The cdrom +has lists of the packages and ports with brief descriptions in +<tt>cdrom/packages/index</tt>, <tt>cdrom/packages/index.txt</tt>, +and <tt>cdrom/ports/index</tt>, with fuller descriptions in +<tt>/cdrom/ports/*/*/pkg/DESCR</tt>, where the <tt>*</tt>s +represent subdirectories of kinds of programs and program names +respectively. + +If you find the handbook too sophisticated (what with +<tt>lndir</tt> and all) on installing ports from the cdrom, +here's what usually works: + +Find the port you want, say <tt>kermit</tt>. There will be a directory +for it on the cdrom. Copy the subdirectory to +<tt>/usr/local</tt> (a good place for software you add that +should be available to all users) with: +<tscreen> +cp -R /cdrom/ports/comm/kermit /usr/local +</tscreen> +This should result in a <tt>/usr/local/kermit</tt> subdirectory +that has all the files that the <tt>kermit</tt> subdirectory on +the cdrom has. + +Next, check <tt>/cdrom/ports/distfiles</tt> for a file with a name +that indicates it's the port you want. Copy that file to +<tt>/usr/ports/distfiles</tt>. (Create <tt>/usr/ports/distfiles</tt> +if it doesn't exist using <em>mkdir</em>.) In the case of <tt>kermit</tt>, +there is no distfile. + +Then <tt>cd</tt> to the subdirectory of +<tt>/usr/local/kermit</tt> that has the file Makefile. Type +<tscreen> +make all install +</tscreen> + +During this process the port will ftp to get any compressed files it +needs that it didn't find in <tt>/usr/ports/distfiles</tt>. If you +don't have your network running yet and there was no file for the +port in <tt>/cdrom/ports/distfiles</tt>, you will have to get the +distfile using another machine and copy it to +<tt>/usr/ports/distfiles</tt> from a floppy or your dos partition. +Read <tt>Makefile</tt> (with <tt>cat</tt> or <tt>more</tt> or +<tt>view</tt>) to find out where to go (the master distribution site) +to get the file and what its name is. Its name will be truncated +when downloaded to DOS, and after you get it into +<tt>/usr/ports/distfiles</tt> you'll have to rename it (with the +<tt>mv</tt> command) to its original name so it can be found. (Use +binary file transfers!) Then go back to <tt>/usr/local/kermit</tt>, +find the directory with <tt>Makefile</tt>, and type <tt>make all +install</tt>. + +The other thing that happens when installing ports or packages is that +some other program is needed. If the installation stops with a message +"can't find unzip" or whatever, you might need to install the package +or port for unzip before you continue. + +Once it's installed type <tt>rehash</tt> to make FreeBSD +<tt>reread</tt> the files in the path so it knows what's there. +(If you get a lot of "path not found" messages when you use +<tt>whereis</tt> or which, you might want to make additions to +the list of directories in the path statement in <tt>.cshrc</tt> +in your home directory. The path statement in Unix does the same +kind of work it does in DOS, except the current directory is not +(by default) in the path for security reasons; if +the command you want is in the directory you're in, you need to +type <tt>./</tt> before the command to make it work; no space after the +slash.) + +You might want to get the most recent version of Netscape from their +<url url="ftp://ftp.netscape.com" name="ftp site">. (Netscape +requires the X window sytem.) The version you want is the "unknown +bsd" version. Just use <tt>gunzip <em>filename</em></tt> and <tt>tar +xvf <em>filename</em></tt> on it, move the binary to +<tt>/usr/local/bin</tt> or some other place binaries are kept, +<tt>rehash</tt>, and then put the following lines in <tt>.cshrc</tt> +in each user's home directory or (easier) in +<tt>/etc/csh.cshrc</tt>, the system-wide csh start-up file: +<tscreen> +setenv XKEYSYMDB /usr/X11R6/lib/X11/XKeysymDB<newline> +setenv XNLSPATH /usr/X11R6/lib/X11/nls +</tscreen> +This assumes that the file <tt>XKeysymDB</tt> and the directory +<tt>nls</tt> are in +<tt>/usr/X11R6/lib/X11</tt>; if they're not, find them and put them there. + +If you originally got Netscape as a port using the cdrom (or ftp), +don't replace <tt>/usr/local/bin/netscape</tt> with the new netscape binary; +this is just a shell script that sets up the environmental variables +for you. Instead rename the new binary to <tt>netscape.bin</tt> and replace the + old +binary, which is <tt>/usr/local/lib/netscape/netscape.bin</tt>. + + +<!-- ************************************************************ --> +<sect>Other + +<p>As root, you can dismount the cdrom with <tt>/sbin/umount +/cdrom</tt>, take it out of the drive, insert another one, and +mount it with <tt>/sbin/mount_cd9660 /dev/cd0a /cdrom</tt> +assuming <tt>cd0a</tt> is the device name for your cdrom drive. + +Using the live file system---the second of FreeBSD's cdrom disks---is +useful if you've got limited space. You might try using +<tt>emacs</tt> or playing games from the cdrom. This involves using +<tt>lndir</tt>, which gets installed with the X Window System, to tell the +program(s) where to find the necessary files, because they're in the +<tt>/cdrom</tt> file system instead of in <tt>/usr</tt> and its +subdirectories, which is where they're expected to be. Read <tt>man +lndir</tt>. + +You can delete a user (say, jack) by using the command <tt>vipw</tt> +to bring up the <tt>master.passwd</tt> file (do not use vi directly +on master.passwd); delete the line for jack and save the file. Then +edit <tt>/etc/group</tt>, eliminating jack wherever it appears. +Finally, go to <tt>/usr/home</tt> and use <tt>rm -R</tt> jack (to +get rid of user jack's home directory files). + +<!-- ************************************************************ --> +<sect>Comments Welcome + +<p>If you use this guide I'd be interested in knowing where it was +unclear and what was left out that you think should be included, and +if it was helpful. My thanks to Eugene W. Stark, professor of +computer science at SUNY-Stony Brook, and John Fieber for helpful +comments. + +Annelise Anderson <htmlurl url="mailto:andrsn@hoover.stanford.edu" + name="<andrsn@hoover.stanford.edu>"> + +</article> + + diff --git a/data/web.mk b/data/web.mk new file mode 100644 index 0000000000..993ec606d1 --- /dev/null +++ b/data/web.mk @@ -0,0 +1,256 @@ +# bsd.web.mk +# $Id: web.mk,v 1.1.1.1 1996-09-24 17:45:45 jfieber Exp $ + +# +# Build and install a web site. +# +# Basic targets: +# +# all (default) -- performs batch mode processing necessary +# install -- Installs everything +# clean -- remove anything generated by processing +# +# Transformations: +# +# copy -- no processing, simply copy the file to install +# spam -- run the file through spam for processing and validation +# m4 -- run through the m4 macro processor +# + +.if exists(${.CURDIR}/../Makefile.inc) +.include "${.CURDIR}/../Makefile.inc" +.endif + +WEBDIR?= ${.CURDIR:T} +CGIDIR?= ${.CURDIR:T} +DESTDIR?= ${HOME}/public_html + +WEBOWN?= ${USER} +WEBGRP?= ${USER} +WEBMODE?= ${NOBINMODE} + +CGIOWN?= ${USER} +CGIGRP?= ${USER} +CGIMODE?= ${BINMODE} + +# +# Install dirs derived from the above. +# +DOCINSTALLDIR= ${DESTDIR}${WEBBASE}/${WEBDIR} +CGIINSTALLDIR= ${DESTDIR}${WEBBASE}/${CGIDIR} + +# +# The orphan list contains sources specified in DOCS that there +# is no transform rule for. We start out with all of them, and +# each rule below removes the ones it knows about. If any are +# left over at the end, the user is warned about them. +# +ORPHANS:= ${DOCS} + +COPY= -c + +################################################################## +# Transformation rules + +### +# file.sgml --> file.html +# +# Runs file.sgml through spam to validate and expand some entity +# references are expanded. file.html is added to the list of +# things to install. + +.SUFFIXES: .sgml .html +SGMLNORM= sgmlnorm +CATALOG?= /usr/local/share/sgml/HTML/catalog +SGMLNORMFLAGS= -d ${SGMLNORMOPTS} -c ${CATALOG} +GENDOCS+= ${DOCS:M*.sgml:S/.sgml$/.html/g} +ORPHANS:= ${ORPHANS:N*.sgml} + +.sgml.html: + ${SGMLNORM} ${SGMLNORMFLAGS} ${.IMPSRC} > ${.TARGET} + +### +# file.java --> file.class +# +# Uses javac to compile java source. Note: since we cannot tell +# what classes will come out of a java file, we have install all +# .class files. The .if construction is there so that *.class +# is only put in if there are actually java files in the DOCS. +# Generally speaking, make and java were not made for each other. + +.SUFFIXES: .java .class +JAVAC?= javac +JAVAFLAGS= ${JAVAOPTS} +_TMP:= ${DOCS:M*.java} +.if !empty(_TMP) +GENDOCS+= ${DOCS:M*.java:S/.java$/.class/g} *.class +.endif +ORPHANS:= ${ORPHANS:N*.java} + +.java.class: + ${JAVAC} ${JAVAFLAGS} ${.IMPSRC} + + +### +# file.m4 --> file.html +# +# Runs file.m4 through the m4 preprocessor, generating file.sgml, +# which is then taken care of by the .sgml to .html rule. + +.SUFFIXES: .m4 +M4?= m4 +M4FLAGS?= ${M4OPTS} +GENDOCS+= ${DOCS:M*.m4:S/.m4$/.html/g} +CLEANFILES+= ${DOCS:M*.m4:S/.m4$/.sgml/g} +ORPHANS:= ${ORPHANS:N*.m4} + +.m4.sgml: + ${M4} ${M4OPTS} < ${.IMPSRC} > ${.TARGET} + + +################################################################## +# Targets + +# +# If no target is specified, .MAIN is made +# +.MAIN: all + +# +# Build most everything +# +all: orphans cvsdirs ${GENDOCS} ${DATA} ${LOCAL} ${CGI} _PROGSUBDIR + +# +# Warn about anything in DOCS that has no translation +# +.if !empty(ORPHANS) +orphans: + @echo Warning! I don\'t know what to do with: ${ORPHANS} +.else +orphans: +.endif + +# +# Check these things out from cvs +# +cvsdirs: +.if defined{CVSDIRS} && !empty{CVSDIRS} + for i in ${CVSDIRS}; do \ + cvs co -P $$i; \ + done +.endif + +# +# Clean things up +# +.if !target(clean) +clean: _PROGSUBDIR + rm -f Errs errs mklog ${GENDOCS} ${LOCAL} ${CLEANFILES} +.endif + +# +# Really clean things up +# +.if !target(cleandir) +cleandir: clean _PROGSUBDIR + rm -f ${.CURDIR}/tags .depend + cd ${.CURDIR}; rm -rf obj; +.endif + +# +# Install targets: before, real, and after. +# +.if !target(install) +.if !target(beforeinstall) +beforeinstall: +.endif +.if !target(afterinstall) +afterinstall: +.endif + +_ALLINSTALL= ${GENDOCS} ${DATA} ${LOCAL} + +realinstall: ${COOKIE} ${GENDOCS} ${DATA} ${LOCAL} ${CGI} _PROGSUBDIR +.if !empty(_ALLINSTALL) + @mkdir -p ${DOCINSTALLDIR} + for entry in ${_ALLINSTALL}; do \ + ${INSTALL} ${COPY} -o ${WEBOWN} -g ${WEBGRP} -m ${WEBMODE} \ + ${INSTALLFLAGS} $${entry} ${DOCINSTALLDIR}; \ + done +.endif +.if defined(CGI) && !empty(CGI) + @mkdir -p ${CGIINSTALLDIR} + for entry in ${CGI}; do \ + ${INSTALL} ${COPY} -o ${CGIOWN} -g ${CGIGRP} -m ${CGIMODE} \ + ${INSTALLFLAGS} $${entry} ${CGIINSTALLDIR}; \ + done +.endif +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + for entry in ${DOCSUBDIR}; do \ + mkdir -p ${DOCINSTALLDIR}/$$entry; \ + done +.endif + +realinstall2: +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + for entry in ${DOCSUBDIR}; do \ + (cd ${DOCINSTALLDIR}/$$entry; \ + tar czf $$entry-html.tar.gz $${entry}.html $${entry}_toc.html \ + $$entry[0-9]*.html; \ + ${BATCHSSI} $$entry ${HDR} ${FTR} \ + $${entry}.html $${entry}_toc.html $$entry[0-9]*.html); \ + done +.endif + +# Set up install dependencies so they happen in the correct order. +install: afterinstall +afterinstall: realinstall2 +realinstall: beforeinstall +realinstall2: realinstall +.endif + +# +# This recursively calls make in subdirectories. +# +#SUBDIR+=${DOCSUBDIR} +_PROGSUBDIR: .USE +.if defined(SUBDIR) && !empty(SUBDIR) + @for entry in ${SUBDIR}; do \ + (${ECHODIR} "===> ${DIRPRFX}$$entry"; \ + cd ${.CURDIR}/$${entry}; \ + ${MAKE} ${.TARGET:S/realinstall/install/:S/.depend/depend/} DIRPRFX=${DIRPRFX}$$entry/); \ + done +.endif +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + @for entry in ${DOCSUBDIR}; do \ + (${ECHODIR} "===> ${DIRPRFX}$$entry"; \ + cd ${.CURDIR}/$${entry}; \ + ${MAKE} ${.TARGET:S/realinstall/install/:S/.depend/depend/} DIRPRFX=${DIRPRFX}$$entry/ ${PARAMS}); \ + done +.endif + + +# +# cruft for generating linuxdoc stuff +# + +.if defined (DOCSUBDIR) && !empty(DOCSUBDIR) + +FORMATS?= "html ascii latin1 ps" +PARAMS= DESTDIR=${DESTDIR} DOCDIR=${WEBBASE}/${WEBDIR} +PARAMS+= DOCOWN=${WEBOWN} DOCGRP=${WEBGRP} +PARAMS+= SGMLOPTS="-ssi -links" FORMATS=${FORMATS} COPY="${COPY}" +#DOCDIR= ${WEBBASE}/${WEBDIR} +#DOCOWN= ${WEBOWN} +#DOCGRP= ${WEBGRP} +#MANMODE= ${WEBMODE} +#PARAMS+= MANGRP=${CGIGRP} MANMODE=${MANMODE} MANOWN=${CGIOWN} + +BATCHSSI= batchssi +HDR= ${.CURDIR}/doc.hdr +FTR= ${.CURDIR}/doc.ftr + +.endif + +# THE END diff --git a/data/welcome.sgml b/data/welcome.sgml new file mode 100644 index 0000000000..0cad06d6e2 --- /dev/null +++ b/data/welcome.sgml @@ -0,0 +1,65 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [ +<!ENTITY date "$Date: 1996-09-24 17:45:44 $"> +<!ENTITY title "About FreeBSD"> +<!ENTITY % includes SYSTEM "includes.sgml"> %includes; +]> + +<HTML> +<HEAD> + <TITLE>About FreeBSD + + + + + +

    What is FreeBSD?

    + +

    FreeBSD is an advanced BSD UNIX operating system for "PC-compatible" +computers. It offers an exceptional combination of features:

    + +
    FreeBSD +specializes in TCP/IP networking. + +

    FreeBSD makes an ideal Internet server or +desktop system. It provides robust network services, even under the heaviest +of loads, and uses memory efficiently to maintain good response times for +hundreds, or even thousands, of simultaneous user processes

    + + +
    FreeBSD +provides advanced technical features. + +

    FreeBSD offers many features today which are still missing in other +operating systems, even some of the best commercial ones. Advanced +features for performance, security, and even binary compatibility with +other popular operating systems.

    + +
    FreeBSD +can run a variety of applications. + +

    The quality of FreeBSD combined with today's low-cost, high-speed PC hardware +makes FreeBSD a very economical alternative to commercial UNIX workstations. +It's suited for a great number of applications.

    + + +
    FreeBSD +is easy to install. + +

    FreeBSD can be installed from a variety of media including CD-ROM, floppy +disk, magnetic tape, an MS-DOS partition, or if you have a network connection +(even a dial-up PPP to an Internet provider), you can install it directly +over anonymous FTP or NFS. All you need is a single 1.44MB boot floppy +and these directions.

    + + +
    FreeBSD +is free. + +

    While you might expect an operating system with these features to sell +for a high price, FreeBSD is available free of charge and comes with full +source code. If you'd like to try it out, more +information is available.

    + +&footer; + + diff --git a/data/where.sgml b/data/where.sgml new file mode 100644 index 0000000000..64f260aeae --- /dev/null +++ b/data/where.sgml @@ -0,0 +1,111 @@ + + + %includes; +]> + +&header; + +

    Installing FreeBSD

    + +

    There are many options for installing FreeBSD, including + installation from CDROM, floppy disk, an MS-DOS partition, + magnetic tape, anonymous ftp, and NFS. Please read through + the installation guide + before downloading the entire FreeBSD distribution. If you + are installing on a machine connected to the Internet, you + may only need to download a single installation disk image!

    + +

    FreeBSD Distribution Sites

    + +

    The official sources for FreeBSD are: +

    + +

    If you plan on getting FreeBSD via ftp, please check the + listing of mirror + sites in the handbook to see if there is a site closer + to you. For more information about past, present and + future releases in general, please visit the release information page. + +

    Applications and Utility Software

    + +

    The Packages collection

    + +

    The FreeBSD packages are a diverse collection of utility + and application software that has been ported to FreeBSD. + The packages are pre-compiled binaries ready to drop into + your system and run.

    + + + +

    The Ports collection

    + +

    The Ports collection is like the packages collection but + instead of compiled binaries, the necessary patches and + makefiles to compile the source code are provided. For + software with important configuration that must be done at + compile time, the "port" version may be more useful than + the "package" version.

    + + + +

    For information about how you can contribute + your favorite piece of software to the port + collection, have a look at Porting + applications and Contributing to + FreeBSD in the FreeBSD handbook. + +

    Commercial software

    + +

    Beginning with FreeBSD Release + 2.0.5, FreeBSD includes demo versions of some + commercial as well as some shareware products. In + addition to the demos available in the FreeBSD + distribution, a number of other commercial vendors offer + software products specifically for FreeBSD.

    + + + +&footer; + + diff --git a/en/Makefile b/en/Makefile new file mode 100644 index 0000000000..70dd1a26fd --- /dev/null +++ b/en/Makefile @@ -0,0 +1,27 @@ +DOCS= about.sgml commercial.sgml daemon.sgml docproj.sgml docs.sgml +DOCS+= gallery.sgml index-site.sgml index.sgml license.sgml +DOCS+= mailto.sgml newsflash.sgml searchhints.sgml support.sgml +DOCS+= welcome.sgml where.sgml search.sgml + +# These will be directly installed. + +DATA= COPYING COPYING.LIB README.mirror robots.txt + +# Files or targets listed here are defined in this file. + +LOCAL= stats.html stats-img.html + +stats.html: /home/www/server/logs/access_log + (cd /usr/local/www/server/logs;zcat access_log.*.gz;cat access_log) | \ + egrep -iv '\.(gif|jpg|jpeg|au) ' | \ + /usr/local/www/bin/analog +i0 +R500 -o > ${.TARGET} + +stats-img.html: /home/www/server/logs/access_log + (cd /usr/local/www/server/logs;zcat access_log.*.gz;cat access_log) | \ + /usr/local/www/bin/analog +i0 +R500 -o > ${.TARGET} + +SUBDIR= cgi gifs ports releases tutorials +DOCSUBDIR= FAQ handbook +WEBDIR= data + +.include "web.mk" diff --git a/en/Makefile.inc b/en/Makefile.inc new file mode 100644 index 0000000000..76793234c0 --- /dev/null +++ b/en/Makefile.inc @@ -0,0 +1 @@ +WEBBASE= /data diff --git a/en/cgi/Makefile b/en/cgi/Makefile new file mode 100644 index 0000000000..f632feea24 --- /dev/null +++ b/en/cgi/Makefile @@ -0,0 +1,11 @@ +DATA= ftp.mirrors +CGI= ftp.cgi gallery.cgi mirror.cgi cgi-lib.pl cgi-style.pl +CGI+= search.cgi + +.SUFFIXES: .C .cgi + +.C.cgi: + ${CXX} ${CFLAGS} -o ${.TARGET} ${.IMPSRC} + +.include "../web.mk" + diff --git a/en/cgi/cgi-lib.pl b/en/cgi/cgi-lib.pl new file mode 100644 index 0000000000..666674643a --- /dev/null +++ b/en/cgi/cgi-lib.pl @@ -0,0 +1,119 @@ +#!/usr/bin/perl -- -*- C -*- +# Perl Routines to Manipulate CGI input +# S.E.Brenner@bioc.cam.ac.uk +# $Header: /home/ncvs/www/en/cgi/cgi-lib.pl,v 1.1.1.1 1996-09-24 17:45:57 jfieber Exp $ +# +# Copyright 1994 Steven E. Brenner +# Unpublished work. +# Permission granted to use and modify this library so long as the +# copyright above is maintained, modifications are documented, and +# credit is given for any use of the library. +# +# Thanks are due to many people for reporting bugs and suggestions +# especially Meng Weng Wong, Maki Watanabe, Bo Frese Rasmussen, +# Andrew Dalke, Mark-Jason Dominus and Dave Dittrich. +# For more information, see: +# http://www.bio.cam.ac.uk/web/form.html +# http://www.seas.upenn.edu/~mengwong/forms/ +# Minimalist http form and script (http://www.bio.cam.ac.uk/web/minimal.cgi): +# +# require "cgi-lib.pl"; +# if (&ReadParse(*input)) { +# print &PrintHeader, &PrintVariables(%input); +# } else { +# print &PrintHeader,'
    Data: '; +#} +# ReadParse +# Reads in GET or POST data, converts it to unescaped text, and puts +# one key=value in each member of the list "@in" +# Also creates key/value pairs in %in, using '\0' to separate multiple +# selections +# Returns TRUE if there was input, FALSE if there was no input +# UNDEF may be used in the future to indicate some failure. +# Now that cgi scripts can be put in the normal file space, it is useful +# to combine both the form and the script in one place. If no parameters +# are given (i.e., ReadParse returns FALSE), then a form could be output. +# If a variable-glob parameter (e.g., *cgi_input) is passed to ReadParse, +# information is stored there, rather than in $in, @in, and %in. +sub ReadParse { + local (*in) = @_ if @_; + local ($i, $key, $val); + # Read in text + if (&MethGet) { + $in = $ENV{'QUERY_STRING'}; + } elsif ($ENV{'REQUEST_METHOD'} eq "POST") { + read(STDIN,$in,$ENV{'CONTENT_LENGTH'}); + } + @in = split(/&/,$in); + foreach $i (0 .. $#in) { + # Convert plus's to spaces + $in[$i] =~ s/\+/ /g; + # Split into key and value. + ($key, $val) = split(/=/,$in[$i],2); # splits on the first =. + # Convert %XX from hex numbers to alphanumeric + $key =~ s/%(..)/pack("c",hex($1))/ge; + $key =~ tr/[^A-Za-z0-9\-\_\$\+\=\~\.\,]//; # allow only safe chars + $val =~ s/%(..)/pack("c",hex($1))/ge; + $val =~ tr/[^A-Za-z0-9\-\_\$\+\=\~\.\,]//; # allow only safe chars + # Associate key and value + $in{$key} .= "\0" if (defined($in{$key})); # \0 is the multiple separator + $in{$key} .= $val; + } + return length($in); +} +# PrintHeader +# Returns the magic line which tells WWW that we're an HTML document +sub PrintHeader { + return "Content-type: text/html\n\n"; +} +# MethGet +# Return true if this cgi call was using the GET request, false otherwise +sub MethGet { + return ($ENV{'REQUEST_METHOD'} eq "GET"); +} +# MyURL +# Returns a URL to the script +sub MyURL { + return 'http://' . $ENV{'SERVER_NAME'} . $ENV{'SCRIPT_NAME'}; +} +# CgiError +# Prints out an error message which which containes appropriate headers, +# markup, etcetera. +# Parameters: +# If no parameters, gives a generic error message +# Otherwise, the first parameter will be the title and the rest will +# be given as different paragraphs of the body +sub CgiError { + local (@msg) = @_; + local ($i,$name); + if (!@msg) { + $name = &MyURL; + @msg = ("Error: script $name encountered fatal error"); + }; + print &PrintHeader; + print "$msg[0]\n"; + print "

    $msg[0]

    \n"; + foreach $i (1 .. $#msg) { + print "

    $msg[$i]

    \n"; + } + print "\n"; +} +# PrintVariables +# Nicely formats variables in an associative array passed as a parameter +# And returns the HTML string. +sub PrintVariables { + local (%in) = @_; + local ($old, $out, $output); + $old = $*; $* =1; + $output .= "
    "; + foreach $key (sort keys(%in)) { + foreach (split("\0", $in{$key})) { + ($out = $_) =~ s/\n/
    /g; + $output .= "
    $key
    $out
    "; + } + } + $output .= "
    "; + $* = $old; + return $output; +} +1; diff --git a/en/cgi/cgi-style.pl b/en/cgi/cgi-style.pl new file mode 100644 index 0000000000..53252af9bd --- /dev/null +++ b/en/cgi/cgi-style.pl @@ -0,0 +1,36 @@ +# $Id: cgi-style.pl,v 1.1.1.1 1996-09-24 17:45:57 jfieber Exp $ +# +# Perl routines to encapsulate various elements of HTML page style. + +# For future reference, when is now? +($se,$mn,$hr,$md,$mo,$yr,$wd,$yd,$dst) = localtime(time); +$yr += 1900; +$timestamp = "$mo-$md-$yr"; + +# Colors for the body +$t_body = ""; + +if ($hsty_base eq "") { + $hsty_base = ".."; +} +if ($hsty_author eq "") { + $hsty_author = "www\@freebsd.org"; +} + +$i_daemon = "\"\""; + +if ($hsty_home eq "") { + $hsty_home = "\"FreeBSD"; +} + +sub html_header { + local ($title) = @_; + + return &PrintHeader . "\n$title\n\n$t_body\n" . + "

    $i_daemon $title

    \n"; +} + +sub html_footer { + return "
    $hsty_home
    $hsty_author
    $hsty_date
    \n"; +} diff --git a/en/cgi/ftp.cgi b/en/cgi/ftp.cgi new file mode 100755 index 0000000000..0cca755978 --- /dev/null +++ b/en/cgi/ftp.cgi @@ -0,0 +1,35 @@ +#!/usr/bin/perl + +require 'cgi-lib.pl'; +require 'cgi-style.pl'; + + +$newloc = "http://www.freebsd.org/"; + +print &html_header("FTP Download"); + +open (MIRRORS, "ftp.mirrors"); + +print "

    Download $ARGV[0] from one of the following mirror sites:

    \n"; + +$oldplace = ""; + +while () { + if (/.*:.*:/ && !/^#/) { + ($place, $site, $root) = split(':',$_); + chop $root; $root =~ s/ *$//; + if ($place ne $oldplace) { + if ($oldplace ne "") { + print "\n"; + } + print "$place\n
      \n"; + $oldplace = $place; + } + print "
    • $site
      • \n"; + } +} + +close (MIRRORS); + +print "
    \n"; +print &html_footer; diff --git a/en/cgi/ftp.mirrors b/en/cgi/ftp.mirrors new file mode 100644 index 0000000000..d0952db86c --- /dev/null +++ b/en/cgi/ftp.mirrors @@ -0,0 +1,64 @@ +#testing +Australia:ftp.au.freebsd.org:/pub/FreeBSD +Australia:ftp2.au.freebsd.org:/pub/FreeBSD +Australia:ftp3.au.freebsd.org:/pub/FreeBSD + +Brazil:ftp.br.freebsd.org:/pub/FreeBSD + +Canada:ftp.ca.freebsd.org:/pub/FreeBSD + +Czech Republic:sunsite.mff.cuni.cz:/OS/FreeBSD + +Finland:nic.funet.fi:/pub/unix/FreeBSD + +France:ftp.ibp.fr:/pub/FreeBSD + +Germany:ftp.de.freebsd.org:/pub/FreeBSD +Germany:ftp2.de.freebsd.org:/pub/FreeBSD +Germany:ftp3.de.freebsd.org:/pub/FreeBSD +Germany:ftp4.de.freebsd.org:/pub/FreeBSD +Germany:ftp5.de.freebsd.org:/pub/FreeBSD +Germany:ftp6.de.freebsd.org:/pub/FreeBSD + +Hong Kong:ftp.hk.super.net:/pub/FreeBSD + +Ireland:ftp.internet-eireann.ie:/pub/FreeBSD + +Israel:orgchem.weizmann.ac.il:/pub/FreeBSD + +Japan:ftp.jp.freebsd.org:/pub/FreeBSD +Japan:ftp2.jp.freebsd.org:/pub/FreeBSD +Japan:ftp3.jp.freebsd.org:/pub/FreeBSD +Japan:ftp4.jp.freebsd.org:/pub/FreeBSD +Japan:ftp5.jp.freebsd.org:/pub/FreeBSD +Japan:ftp6.jp.freebsd.org:/pub/FreeBSD + +Korea:ftp.kr.freebsd.org:/pub/FreeBSD +Korea:ftp2.kr.freebsd.org:/pub/FreeBSD + +Netherlands:ftp.nl.net:/pub/os/FreeBSD + +Portugal:ftp.ua.pt:/pub/misc/FreeBSD + +Russia:ftp.kiae.su:/FreeBSD + +South Africa:ftp.za.freebsd.org:/pub/FreeBSD +South Africa:ftp2.za.freebsd.org:/pub/FreeBSD + +Sweden:ftp.luth.se:/pub/FreeBSD + +Taiwan:NCTUCCCA.edu.tw:/Operating-Systems/FreeBSD +Taiwan:netbsd.csie.nctu.edu.tw:/pub/FreeBSD + +Thailand:ftp.nectec.or.th:/pub/FreeBSD + +United States:ftp.freebsd.org:/pub/FreeBSD +United States:ftp2.freebsd.org:/pub/FreeBSD +United States:ftp3.freebsd.org:/pub/FreeBSD +United States:ftp4.freebsd.org:/pub/FreeBSD +United States:ftp5.freebsd.org:/pub/FreeBSD +United States:ftp6.freebsd.org:/pub/FreeBSD + +United Kingdom:ftp.uk.freebsd.org:/packages/unix/FreeBSD +United Kingdom:ftp2.uk.freebsd.org:/pub/walnut.creek/FreeBSD +United Kingdom:ftp3.uk.freebsd.org:/pub/BSD/FreeBSD diff --git a/en/cgi/gallery.cgi b/en/cgi/gallery.cgi new file mode 100755 index 0000000000..61de211ce6 --- /dev/null +++ b/en/cgi/gallery.cgi @@ -0,0 +1,131 @@ +#!/usr/bin/perl +################################################################## +# A CGI form processor for FreeBSD Gallery submissions +# +# John Fieber +# August 9 1996 +################################################################## + +$curator = "jfieber@indiana.edu"; +#$curator = "jkh@freebsd.org"; +$subject = "Another gallery submission..."; + +require 'cgi-lib.pl'; +&ReadParse; + +#$d_date = "$Date: 1996-09-24 17:45:57 $"; +#$h_base = ".."; +#$d_author = " +require 'cgi-style.pl'; + +# Construct the gallery entry in HTML form +$entry = "
  • $in{'organization'} " . + "-- $in{'description'}
    • "; + +# Try and figure out where the person came from so we can provide +# links back to the correct place. +$return = ""; +if ($in{'return'} eq "") { + if ($ENV{'HTTP_REFERER'} ne "") { + $in{'return'} = $ENV{'HTTP_REFERER'}; + } +} +if ($in{'return'} ne "") { + $return = "Return to the Gallery"; +} + + +# This is the form where the user enters the information. +$forma = &html_header("Gallery Submission") . +" + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Organization:
    Description:
    URL:
    Category: + Commercial
    + Non-Profit
    + Personal +
    Email Contact:
    + +

    $return

    +" . &html_footer(); + +# This is the form where the user CHECKS the information they typed +$formb = &html_header("Your Gallery Submission") . +"

    Here is your entry as it will appear in the +FreeBSD Gallery page.

    +

    Please check that the category and your e-mail +address are correct, and that the link actually works. +If anything is wrong, use your +browser's back button and correct it. +If everything is okay, press the submit button +below.

    +

    Contact person: $in{'contact'}

    +

    $in{'category'}

    +
      +$entry +
    +
    +
    + + + + + + + + +
    +

    $return

    +" . &html_footer(); + +# And this is where we thank them for submitting an entry. +$formc = &html_header("Thank You!") . +"

    Please allow a few days for your entry to be added +to the Gallery.

    +

    $return

    +" . &html_footer(); + + +if ($in{'action'} eq "preview") { + print $formb; +} +elsif ($in{'action'} eq "submit") { + print $formc; +# close(STDOUT); + + open(M, "| mail -s \"$subject\" $curator"); + print M "$in{'contact'} submitted the following to be added under\n"; + print M "\"$in{'category'}\" in the gallery:\n\n"; + print M "<-- from $in{'contact'} on $timestamp -->\n"; + print M "$entry\n"; + close(M); +} +else { + print $forma; +} + +exit 0; diff --git a/en/cgi/mirror.cgi b/en/cgi/mirror.cgi new file mode 100755 index 0000000000..d92d59bb0f --- /dev/null +++ b/en/cgi/mirror.cgi @@ -0,0 +1,16 @@ +#!/usr/bin/perl +# (c) Wolfram Schneider, Berlin. June 1996. Public domain. +# +# FreeBSD WWW mirror redirect +# +# $Id: mirror.cgi,v 1.1.1.1 1996-09-24 17:45:57 jfieber Exp $ + +$_ = $ENV{'QUERY_STRING'}; + +s/^[^=]+=//; # 'variable=value' -> 'value' +s/\+/ /g; # '+' -> space +s/%(..)/pack("c",hex($1))/ge; # '%ab' -> char ab + +print "Location: $_\nContent-type: text/plain\n\n"; + +exit 0; diff --git a/en/cgi/search.cgi b/en/cgi/search.cgi new file mode 100755 index 0000000000..c22293d650 --- /dev/null +++ b/en/cgi/search.cgi @@ -0,0 +1,257 @@ +#!/usr/bin/perl +# +# mail-archive.pl -- a CGI interface to a wais indexed maling list archive. +# +# Origin: +# Tony Sanders , Nov 1993 +# +# Hacked beyond recognition by: +# John Fieber , Nov 1994 +# +# Format the mail messages a little nicer. +# Add code to check database status before searching. +# John Fieber , Aug 1996 +# +# Disclaimer: +# This is pretty ugly in places. + + +$server_root = '/usr/local/www'; +$waisq = "/usr/local/www/bin/waisq"; +$sourcepath = "/f/jfieber/index"; +$hints = "/searchhints.html"; +$myurl = "/cgi/search.cgi"; + +require "open2.pl"; +require "cgi-lib.pl"; +require "cgi-style.pl"; + +@months = ('Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'); + +sub do_wais { + &ReadParse; + + @FORM_words = split(/ /, $in{"words"}); + @FORM_source = split(/\0/, $in{"source"}); + $FORM_max = $in{"max"}; + $FORM_docnum = $in{"docnum"}; + + @AVAIL_source = &checksource(@FORM_source); + if ($#FORM_source != $#AVAIL_source) { + $j = 0; + $k = 0; + foreach $i (0 .. $#FORM_source) { + if ($FORM_source[$i] ne $AVAIL_source[$j]) { + $badsource[$k] = $FORM_source[$i]; + $k++; + } else { + $j++; + } + } + $badsource = join(", ", @badsource); + $badsource =~ s/,([^,]*)$/ and $1/; + if ($#FORM_source - $#AVAIL_source > 1) { + $availmsg = "

    [The $badsource archives are currently unavailable.]

    "; + } else { + $availmsg = "

    [The $badsource archive is currently unavailable.]

    "; + } + } + if ($#AVAIL_source < 0) { + $i = join("    , ", @FORM_source); + $i =~ s/,([^,]*)$/ and $1/; + print &html_header("Mail Archive Search") . + "

    None of the archives you requested ($i) are available at " . + "this time.

    \n"; + print "

    Please try again later, or return to the " . + "search page and select a different archive.

    \n"; + print &html_footer; + exit 0; + } + + # Now we formulate the question to ask the server + foreach $i (@AVAIL_source) { + $w_sources .= "(:source-id\n :filename \"$i.src\"\n ) "; + } + $w_question = "\n (:question + :version 2 + :seed-words \"@FORM_words\" + :relevant-documents + ( ) + :sourcepath \"$sourcepath/:\" + :sources + ( $w_sources ) + :maximum-results $FORM_max + :result-documents + ( ) + )\n"; + + + # + # First case, no document number so this is a regular search + # + if (length($FORM_docnum) == 0) { + print &html_header("Search Results"); + print $availmsg; + if ($#AVAIL_source > 0) { + $src = join("    , ", @AVAIL_source); + $src =~ s/,([^,]*)$/ and $1/; + print "

    The archives $src contain "; + } + else { + print "The archive @AVAIL_source contains "; + } + print " the following items relevant to \`@FORM_words\':\n"; + print "

      \n"; + + &open2(WAISOUT, WAISIN, $waisq, "-g"); + print WAISIN $w_question; + + local($hits, $score, $headline, $lines, $bytes, $type, $date, $file); + while () { + /:score\s+(\d+)/ && ($score = $1); + /:filename "(.*)"/ && ($file = $1); + /:number-of-lines\s+(\d+)/ && ($lines = $1); + /:number-of-bytes\s+(\d+)/ && ($bytes = $1); + /:type "(.*)"/ && ($type = $1); + /:headline "(.*)"/ && ($headline = $1); # XXX + /:date "(\d+)"/ && ($date = $1, $hits++, &docdone); + } + print "
    \n"; + + print "

    Didn't get what you expected? "; + print "Look here for searching hints."; + + if ($hits == 0) { + print "Nothing found.\n"; + } + + print &html_footer; + close(WAISOUT); + close(WAISIN); + + } + +# +# Second Case, a document number was supplied +# + + else { + print &html_header("Search Results: Document"); + &open2(WAISOUT, WAISIN, $waisq, "-g"); + print WAISIN $w_question; + + while () { + s/search_word: boolean \`and\' scored//g; + $w_result .= $_; + } + close(WAISOUT); + close(WAISIN); + + &open2(WAISOUT, WAISIN, $waisq, "-v", $FORM_docnum); + print WAISIN $w_result; + + while () { + $foo .= $_; + } + &printdoc($foo); + + print &html_footer; + close(WAISOUT); + close(WAISIN); + } +} + +# Given an array of sources (sans .src extension), this routine +# checks to see if they actually exist, and if they do, if they +# are currently available (ie, not being updated). It returns +# an array of sources that are actually available. + +sub checksource { + local (@sources) = @_; + + $j = 0; + foreach $i (@sources) { + if (stat("$sourcepath/$i.src")) { + if (!stat("$sourcepath/$i.update.lock")) { + $goodsources[$j] = $i; + $j++; + } + } + } + return(@goodsources); +} + + +# Print a mail message in HTML form + +sub printdoc { + local ($doc) = @_; + + ($header, $body) = split(/\n\n/, $doc, 2); + + $body = &htmlescape($body); + + $header = &htmlescape($header); + $header =~ s/\n */ /g; + + foreach $i (split(/\n/, $header)) { + ($field, $data) = split(/ /, $i, 2); + $hdr{$field} = $data; + } + + print "\n

    \n";
+    if (length($hdr{'Date:'}) > 0) {
+    	print "Date:      $hdr{'Date:'}\n";
+    }
+    if (length($hdr{'From:'}) > 0) {
+    	print "From:      $hdr{'From:'}\n";
+    }
+    if (length($hdr{'To:'}) > 0) {
+    	print "To:        $hdr{'To:'}\n";
+    }
+    if (length($hdr{'Cc:'}) > 0) {
+    	print "Cc:        $hdr{'Cc:'}\n";
+    }
+    if (length($hdr{'Sender:'}) > 0) {
+    	print "Sender:    $hdr{'Sender:'}\n";
+    }
+    if (length($hdr{'Subject:'}) > 0) {
+    	print "Subject:   $hdr{'Subject:'}\n";
+    }
+    print "
    \n"; + + print "
    \n
    \n$body\n
    \n"; +} + +sub htmlescape { + local ($data) = @_; + $data =~ s/&/&/g; + $data =~ s/The archive $file contains no relevant documents.

    " + } else { + $headline = &htmlescape($headline); + $headline =~ s/\\"/\"/g; + print "
  • $headline\n"; + print "
    "; +# print ""; + print "Score: $score; "; + $_ = $date; + /(..)(..)(..)/ && ($yr = $1 + 1900, $mo = $months[$2 - 1], $dy = $3); + print "Lines: $lines; "; + print "${dy}-${mo}-${yr}; "; + print "Archive: $file"; + print "

    • \n"; + } + $score = $headline = $lines = $bytes = $type = $date = $file = ''; +} + +$| = 1; +open (STDERR,"> /dev/null"); +eval '&do_wais'; + diff --git a/en/commercial/commercial.sgml b/en/commercial/commercial.sgml new file mode 100644 index 0000000000..62b90e0844 --- /dev/null +++ b/en/commercial/commercial.sgml @@ -0,0 +1,283 @@ + + + %includes; +]> + +&header; + +

    In addition to the demos of commercial software available + in the FreeBSD distribution, a number of other commercial + vendors offer software products specifically for FreeBSD. + If you know of other companies supporting FreeBSD that + should be added to this page, please notify us.

    + +

    Software

    + +
      +
    • AstroArch + Consulting, Inc. develops and licenses its + ISP Billing and Tracking System or BATS + for FreeBSD as well as thirteen other Operating + Systems. For more information, check out the web pages http://www.tpoint.net/astroarch, + send email to elh@astroarch.com or + call (512) 990-1064.

      +
      • + +
    • + Communication + Systems Research Corp. - Business + applications and consulting for Unix systems including + BSD. Specializing in analysis and development of high + performance solutions for networking problems. Located in + Portland Oregon, consulting internationally for over 12 + years. Telephone: (503) 291-1345

      +
      • + +
    • BRU from + Enhanced Software Technologies is a very powerful and reliable + tape backup system. It offers per-file compression, an improved + tape format with three different kinds of verification, and many safety + checks to insure data integrity. The "BSD/OS 1.1" version works well + with FreeBSD. +

      +
      • + +
    • Conetic + Software is offering a FREE + copy of C/BASE 4GL for the FreeBSD 2.0.5 + operating system. C/BASE 4GL features a + powerful application development tool and database + engine. Featuring a easy to user visual development + environment, a scripting language, and application + libraries with a C language (API) interface. The + best thing about C/BASE 4GL is that it is + fully portable across hardware and operating system + platforms. FreeBSD to DOS, DOS to SOLARIS, SOLARIS + to AIX, etc.... Your free copy of C/BASE 4GL + is set to run for a maximum of 2 concurrent users and + 1,000 records. Please contact us at info@conetic.com + if you'd like a taste of even more power and + programming fun.

      +
      • + +
    • + + Inlab Software GmbH offers binaries of Inlab-Scheme + for FreeBSD and Linux which are free for personal or educational + use. Inlab-Scheme is a R4RS compliant Scheme which is capable + of reading and writing TIFF and XBM-bitmaps to and from a special + internal bitmap type. With built-in primitives for image + processing, Inlab-Scheme can be a general tool for tasks like + optical character recognition and general analysis and processing + of bitmap data.

      +
      • + +
    • + NetCon Corporation + established in 1985, with over 10,000 installed servers, is the leading + supplier of NetWare compatible operating systems and Internet Gateways + for standard UNIX platforms. NetCon offers a complete line of systems + for FreeBSD, SUN Solaris, SCO UNIX/ODT and IBM AIX RS6000 serving from + 5 to 1000 users. Services include; Full Internet access from + NetWare/WIN95/Windows workstations over IPX/SPX, X Windows over + IPX/SPX, NetWare file and print services, NetWare Client services for + UNIX, High-performance, DOS/Windows Terminal Emulation. +

      +
      • + +
    • + Perforce Software + produces + PERFORCE -- the FAST Software + Configuration Management System for many UNIX platforms + and NT. More capable than freeware tools, more applicable + than solutions from academia, and more usable than available + commercial products, PERFORCE manages + software projects comprising thousands of source files + shared by dozens of engineers across many heterogeneous + platforms and geographically distributed locations. + Documentation and fully functional versions (but limited + to two client workspaces) can be downloaded from the Web + pages. For non-commercial users on FreeBSD, we offer + servers with unlimited client workspaces for $1. Perforce + Software can be reached at + info@perforce.com or 1 (510) 865-8720.

      +
      • + +
    • + Progresive Networks, Inc. + offers both its RealAudio + player + and server + for FreeBSD. + The free player allows you to play live and on-demand audio + over 14.4Kps and faster connections. + All you have to do is click on a RealAudio link from your Web browser + and audio begins playing instantly. Check out + The RealAudio Guide to access + hundreds of sites offering music, news, live radio stations, live + events etc. The server allows your website to deliver live and + on-demand audio over the Internet or your company network.

      +
      • + +
    • + RTD provides an ISP billing + package for ISPs using FreeBSD called + UTA

      +
      • + +
    • + Coolworld.Com, Inc. + provides a billing package for ISP's called Internet Billing. + This package was designed to handle all the billing needs for + Internet service providers. It runs under MS-Windows. One + piece of the software is a client/server set with a daemen that + runs on a UNiX server (including FreeBSD) that allows the client + to do all for their user management under a windows frontend.

      +
      • + +
    • X Inside, Inc. + offers software enhancements for FreeBSD. + Accelerated-X Server completely supports 356 + graphics adapters from over 40 vendors, including many + partially supported or not included with XFree86. + Download + a free demonstration from + ftp.xinside.com. Utilize 3D graphics with Accelerated-X + OpenGL. Accelerated-X Multi-Head allows 8 monitors + from a single server. Full Motif 2.0 runtime and development kits + are also available. For more information email info@xinside.com + or call +1 (303) 298-7478.

      +
      • + +
    • XVScan + allows you to use your HP ScanJet scanner under FreeBSD. It is a + commercial product based on John Bradley's xv. +

      +
      • + +
    • Zeus Technology Limited + offer Zeus Server for FreeBSD. Zeus Server is + an advanced, powerful full-featured commercial grade webserver + designed with exceptional performance, minimal machine resource + requirements and ease of administration in mind. Free + evaluation copies may be + downloaded. +

      • + +
    + +

    Hardware and complete systems

    + +
      + +
    • + Apache Digital + Corporation creates custom high-performance PC + based systems optimized for the FreeBSD operating system. + We have many standard + systems to choose from as well as an on-line custom + system design form to help you create your custom + dream system. Please feel free to contact info@apache.com for + more information.

      +
      • + +
    • Cyclades Corporation + sells a variety of high performance, multiport serial + cards which FreeBSD supports in its standard releases (due largely + to their generous cooperation in providing us with hardware and + technical assistance). +

      • + +
    • Emerging Technologies, + Inc. has high speed serial communications adapters + allowing FreeBSD systems to utilize leased lines at + speeds from 56k to T1. The adapters include a complete + set of drivers and utilities that allow a FreeBSD machine + to communicate directly with virtually any IP router via + synchronous PPP, Frame Relay or X.25, and directly to + CISCO brand routers with CISCO serial encapsulation. Full + documentation and support are included. Several hardware + choices are available ranging from an economical single + port adapter card to a dual T1 line model with dual 25mhz + dedicated processors. To contact Emerging Techologies, + send E-mail to info@etinc.com. +

      +
      • + +
    • Geli + Engineering offers economical Pentium + workstation clusters that use the FreeBSD operating system.

      • + +
    • The Init Organization + specializes in Intranet networking servers running FreeBSD. We can + custom design and construct high performance servers to fill any need. + The Init Organization also provides network support and management, + IS support and training, corporate-wide e-mail gateways, domain name + registration and hosting, world wide web site development, and more. + Please send e-mail to info@init.org, + or visit + http://www.tioga.com/~Init/. +

      • + +
    • MOXA makes + economically priced multi-port serial cards which are compatible with + FreeBSD's sio serial driver. The C104 / C168 family of 2/4/8 serial + port cards feature custom ASIC design, speeds up to 921.6Kbps, surge + protection, independent and software configurable I/O ports and IRQs. +

      • + +
    • Stallion Technolgies + Inc offers a range of multiport serial boards for the ISA, + EISA, MCA and PCI buses. Although Stallion does not officially support + drivers for FreeBSD, there is an unsupported, freely available driver + available from their + FTP site. + This driver supports the Stallion EasyIO and EasyConnection 8/32 + multiport boards. For local pricing and availability information, + contact Stallion via their WWW page. +

      • + +
    • SW Technology + offers quality Pentium machines with FreeBSD pre-installed. +

      • + +
    • Zyzzyva Enterprises + presents the Z-Router + as an affordable alternative for businesses and organizations seeking + cost-effective router and webserver solutions that provide + ease-of-maintenance and flexibility to meet changing connection demands. + Our industrial quality systems run on the FreeBSD operating system. + The Z-Router provides a secure web interface to system maintenance + through a convenient online + configuration management tool.
      + Email: + info@zyzzyva.com. Voice: 402.438.1848. FAX: 402.438.1869. +

      • +
    + +

    Documentation and miscellaneous accessories

    +
      +
    • The Bookpool offers + 30% discounts on the new edition of + The Design and Implementation of the 4.4BSD Operating System, + a must-have for any FreeBSD bookshelf. +
      • +
    + +&footer; + + + diff --git a/en/copyright/COPYING b/en/copyright/COPYING new file mode 100644 index 0000000000..a43ea2126f --- /dev/null +++ b/en/copyright/COPYING @@ -0,0 +1,339 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 675 Mass Ave, Cambridge, MA 02139, USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/en/copyright/COPYING.LIB b/en/copyright/COPYING.LIB new file mode 100644 index 0000000000..eb685a5ec9 --- /dev/null +++ b/en/copyright/COPYING.LIB @@ -0,0 +1,481 @@ + GNU LIBRARY GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1991 Free Software Foundation, Inc. + 675 Mass Ave, Cambridge, MA 02139, USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + +[This is the first released version of the library GPL. It is + numbered 2 because it goes with version 2 of the ordinary GPL.] + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. + + This license, the Library General Public License, applies to some +specially designated Free Software Foundation software, and to any +other libraries whose authors decide to use it. You can use it for +your libraries, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if +you distribute copies of the library, or if you modify it. + + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link a program with the library, you must provide +complete object files to the recipients so that they can relink them +with the library, after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. + + Our method of protecting your rights has two steps: (1) copyright +the library, and (2) offer you this license which gives you legal +permission to copy, distribute and/or modify the library. + + Also, for each distributor's protection, we want to make certain +that everyone understands that there is no warranty for this free +library. If the library is modified by someone else and passed on, we +want its recipients to know that what they have is not the original +version, so that any problems introduced by others will not reflect on +the original authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that companies distributing free +software will individually obtain patent licenses, thus in effect +transforming the program into proprietary software. To prevent this, +we have made it clear that any patent must be licensed for everyone's +free use or not licensed at all. + + Most GNU software, including some libraries, is covered by the ordinary +GNU General Public License, which was designed for utility programs. This +license, the GNU Library General Public License, applies to certain +designated libraries. This license is quite different from the ordinary +one; be sure to read it in full, and don't assume that anything in it is +the same as in the ordinary license. + + The reason we have a separate public license for some libraries is that +they blur the distinction we usually make between modifying or adding to a +program and simply using it. Linking a program with a library, without +changing the library, is in some sense simply using the library, and is +analogous to running a utility program or application program. However, in +a textual and legal sense, the linked executable is a combined work, a +derivative of the original library, and the ordinary General Public License +treats it as such. + + Because of this blurred distinction, using the ordinary General +Public License for libraries did not effectively promote software +sharing, because most developers did not use the libraries. We +concluded that weaker conditions might promote sharing better. + + However, unrestricted linking of non-free programs would deprive the +users of those programs of all benefit from the free status of the +libraries themselves. This Library General Public License is intended to +permit developers of non-free programs to use free libraries, while +preserving your freedom as a user of such programs to change the free +libraries that are incorporated in them. (We have not seen how to achieve +this as regards changes in header files, but we have achieved it as regards +changes in the actual functions of the Library.) The hope is that this +will lead to faster development of free libraries. + + The precise terms and conditions for copying, distribution and +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, while the latter only +works together with the library. + + Note that it is possible for a library to be covered by the ordinary +General Public License rather than by this special one. + + GNU LIBRARY GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License Agreement applies to any software library which +contains a notice placed by the copyright holder or other authorized +party saying it may be distributed under the terms of this Library +General Public License (also called "this License"). Each licensee is +addressed as "you". + + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. + + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. + + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices + stating that you changed the files and the date of any change. + + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. + + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Library, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Library, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote +it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Library. + +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. + + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. + + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. + + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. + + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not +compelled to copy the source along with the object code. + + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. + + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also compile or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + c) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + d) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the source code distributed need not include anything that is normally +distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Library or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Library or works based on it. + + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 11. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Library. + +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 12. If the distribution and/or use of the Library is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. + + 13. The Free Software Foundation may publish revised and/or new +versions of the Library General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. + + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. + + NO WARRANTY + + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. + + END OF TERMS AND CONDITIONS + + Appendix: How to Apply These Terms to Your New Libraries + + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). + + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Library General Public + License as published by the Free Software Foundation; either + version 2 of the License, or (at your option) any later version. + + This library is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Library General Public License for more details. + + You should have received a copy of the GNU Library General Public + License along with this library; if not, write to the Free + Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + +Also add information on how to contact you by electronic and paper mail. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the library, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. + + , 1 April 1990 + Ty Coon, President of Vice + +That's all there is to it! diff --git a/en/copyright/daemon.sgml b/en/copyright/daemon.sgml new file mode 100644 index 0000000000..363b6e8636 --- /dev/null +++ b/en/copyright/daemon.sgml @@ -0,0 +1,62 @@ + + + %includes; +]> + +&header; + +

    The little red fellow that graces many of these pages is + the BSD Daemon. In the context of Unix systems, daemons + are process that run in the background attending to various + tasks without human intervention. In the general sense, + daemon is an older form of the word demon. In the Unix + System Administration Handbook, Evi Nemeth has this to + say about daemons:

    + +
    "Many people equate the word ``daemon'' with the + word ``demon,'' implying some kind of Satanic connection + between UNIX and the underworld. This is an egregious + misunderstanding. ``Daemon'' is actually a much older form + of ``demon''; daemons have no particular bias towards good + or evil, but rather serve to help define a person's + character or personality. The ancient Greeks' concept of a + ``personal daemon'' was similar to the modern concept of a + ``guardian angel'' --- ``eudaemonia'' is the state of being + helped or protected by a kindly spirit. As a rule, UNIX + systems seem to be infested with both daemons and demons." + (p403) +
    + +

    The earliest (and most popular) renditions of the BSD Daemon were + created by John Lassiter. More recent FreeBSD-specific + renditions have done by + + Tatsumi Hosokawa, but the basic inspiration was definitely John's. + + The copyright holder and creator of the daemon image is + Marshall Kirk McKusick. + A short pictorial + history is also available.

    + +

    Finally, it should also be noted that, despite Kirk's professed aversion + to this fact, there is close to unanimous agreement that the daemon's + name, should he have one at all, is Chuck. Don't ask + me how that name was arrived at, it just stuck. + +

    BSD Daemon Copyright 1988 by Marshall Kirk McKusick. All + Rights Reserved.

    + +

    Permission to use the daemon may be obtained from:

    + +
    Marshall Kirk McKusick
    1614 Oxford St
    + Berkeley, CA 94709-1608
    USA
    + +

    or via email at mckusick@mckusick.com. +

    + +&footer; + + + diff --git a/en/copyright/license.sgml b/en/copyright/license.sgml new file mode 100644 index 0000000000..bd077a6e89 --- /dev/null +++ b/en/copyright/license.sgml @@ -0,0 +1,99 @@ + + + %includes; +]> + +&header; + +

    All of the documentation and software included in the + 4.4BSD and 4.4BSD-Lite Releases is copyrighted by The + Regents of the University of California. + +

    Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, + 1993, 1994 The Regents of the University of California. + All rights reserved. + +

    Redistribution and use in source and binary forms, with or + without modification, are permitted provided that the + following conditions are met: + +

      + +
    1. Redistributions of source code must retain the above + copyright notice, this list of conditions and the + following disclaimer. + +
    2. Redistributions in binary form must reproduce the + above copyright notice, this list of conditions and the + following disclaimer in the documentation and/or other + materials provided with the distribution. + +
    3. All advertising materials mentioning features or use + of this software must display the following + acknowledgement: + +
      This product includes software developed by + the University of California, Berkeley and its + contributors.
      + +
    4. Neither the name of the University nor the names of its + contributors may be used to endorse or promote products + derived from this software without specific prior written + permission. +
      5. +
    + +

    THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS + ``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 REGENTS OR CONTRIBUTORS + 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 + SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH + DAMAGE. + +

    The Institute of Electrical and Electronics Engineers and + the American National Standards Committee X3, on + Information Processing Systems have given us permission to + reprint portions of their documentation. + +

    In the following statement, the phrase ``this text'' + refers to portions of the system documentation. + +

    Portions of this text are reprinted and reproduced in + electronic form in the second BSD Networking Software + Release, from IEEE Std 1003.1-1988, IEEE Standard Portable + Operating System Interface for Computer Environments + (POSIX), copyright C 1988 by the Institute of Electrical + and Electronics Engineers, Inc. In the event of any + discrepancy between these versions and the original IEEE + Standard, the original IEEE Standard is the referee + document. + +

    In the following statement, the phrase ``This material'' + refers to portions of the system documentation. + +

    This material is reproduced with permission from American + National Standards Committee X3, on Information Processing + Systems. Computer and Business Equipment Manufacturers + Association (CBEMA), 311 First St., NW, Suite 500, + Washington, DC 20001-2178. The developmental work of + Programming Language C was completed by the X3J11 Technical + Committee. + +

    The views and conclusions contained in the software and + documentation are those of the authors and should not be + interpreted as representing official policies, either + expressed or implied, of the Regents of the University of + California. + +&footer; + + diff --git a/en/doc.ftr b/en/doc.ftr new file mode 100644 index 0000000000..38b0c7b771 --- /dev/null +++ b/en/doc.ftr @@ -0,0 +1,8 @@ +

    +FreeBSD Home + Page +
    + @@UPDATE@@
    + www@freebsd.org +
    + diff --git a/en/doc.hdr b/en/doc.hdr new file mode 100644 index 0000000000..e69de29bb2 diff --git a/en/docproj/docproj.sgml b/en/docproj/docproj.sgml new file mode 100644 index 0000000000..28f1ed0c0c --- /dev/null +++ b/en/docproj/docproj.sgml @@ -0,0 +1,176 @@ + + + %includes; +]> + +&header; + +

    Goals

    + +

    Unix has frequently, and rightfully so, been criticized + for being difficult to learn. While the tool based + approach to a computing system is powerful, users are often + stymied by the terse style of the manual pages that + describe each tool in detail but rarely provide hints about + how, when or why the tool can be used in day to day + operations. Many excellent books have been written to show + the tools in a context and a number are highly recommended + for anyone using FreeBSD. However, since every Unix system + has its own quirks, a number of gaps exist in the + documentation as a whole.

    + +

    The mission of the FreeBSD Documentation Project is to + fill this documentation gap. Specifically:

    + +
      +
    1. To cover features, procedures, and other quirks that + are unique to FreeBSD and thus not to be found in + commonly available Unix user, administrator and + programmer guides available on the market. The most + important of these are:

      +
        +
      • Installation

        • +
      • Hardware support and troubleshooting

        • +
      • System configuration and tuning

        • +
      +
      2. + +
    2. To provide documentation covering the most commonly + used aspects of FreeBSD, whether or not the topics are + covered in other user, administrator and programmer + guides. This includes topics such as:

      +
        +
      • Network configuration and troubleshooting

        • +
      • ISP services

        • +
      • General system adminstration

        • +
      +
      3. +
    + +

    Projects

    + +

    To realize the above goals, the Documentation Project is + focused on two specific pieces of documentation:

    +
      +
    1. The + FAQ
      2. +
    2. The + FreeBSD Handbook
      3. +
    + +

    The goal of the FAQ is to address in a + short question and answer format the most common questions + that are asked, or should be asked on the various + mailing lists and newsgroups devoted to the discussion of + FreeBSD. The format does not permit long winded and + comprehensive answers.

    + +

    Topics that need a more in depth discussion than the FAQ + can provide are addressed in the FreeBSD Handbook. + The current incarnation of the handbook is largely a + skeletal framework with many empty chapters and sections + waiting to be filled by words of wisdom.

    + +

    Contributing to the project

    + +

    Like the rest of the FreeBSD project, the documentation + project depends on the tireless contributions of users. To + facilitate the project, a mailing list has been created for + the discussion of documentation issues and communication + among authors. Anyone wishing to contribute to materials + or editorial time should subscribe by sending mail to majordomo@freebsd.org + with a message body of:

    + +
    subscribe freebsd-doc
    + +

    (See Mailing + lists in the handbook for complete information on the + FreeBSD mailing lists.)

    + +

    We welcome both corrections and additions to existing + documentation as well as submissions of entirely new + sections. All documents should reflect the state of + FreeBSD 2.0.5R unless there is a compelling reason to cover + a different release. In such a case, the version to which + the information applies must be clearly stated.

    + +

    Submitting corrections

    + +

    When providing corrections or additions to existing + documentation, the preferred method is context + diff relative to the text as it appears in + FreeBSD-current. (see the diff(1) manual page + for details on generating a context diff). The + FreeBSD-current text for the handbook can be found in:

    + +
    ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/doc/handbook
    + +

    while the FAQ can be found at:

    + +
    ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/doc/FAQ
    + +

    Diffs should be directed to doc@freebsd.org for + review.

    + +

    Submitting new material

    + +

    If you can claim expertise on some topic of interest to + other FreeBSD users and the topic is not covered by either + the FAQ or the Handbook, we would love to incorporate your + wisdom into one or the other. If you wish to contribute + but are not sure what is needed, have a good look through + the handbook and the + FAQ and see what + you think is missing. In particular, the handbook + has a fairly complete outline but sections marked with an + asterisk (*) are currently empty and waiting for an eager + author.

    + +

    At this time, the preferred format for submitting new + materials is SGML conforming to the linuxdoc DTD. The DTD + and tools for converting appropriately tagged documents + into LaTeX, HTML and ascii text are available in FreeBSD + 2.1 and -current. See the sgmlfmt(1) manual + page for details. Due to shortcomings of the linuxdoc DTD, + the project hopes to move to a more flexible DTD such as + DocBook in the future. Any changes will be announced on + the freebsd-doc mailing + list.

    + +

    If you do not feel comfortable with SGML, the next best + format is LaTeX because it can be converted to SGML with a + minimum of hassle. Failing that, plain ASCII submissions + are always welcome.

    + +

    Some general editorial guidelines:

    + +
      +
    • Do not use contractions.

      • + +
    • Provide concrete examples.

      • + +
    • Use cross references. In the HTML version of the + document, these become hypertext links.

      • + +
    • Do not duplicate other sections of the document, even + if they have yet to be written. If you feel the existing + section provides insufficient information to support your + topic, think about whether the additional information + should go in the section you are writing, or if it should + be added to the other end of the cross reference. + Contact the author of the referenced section if you + suspect the latter.

      • + +
    + +&footer + + diff --git a/en/docs.sgml b/en/docs.sgml new file mode 100644 index 0000000000..277e8963ce --- /dev/null +++ b/en/docs.sgml @@ -0,0 +1,60 @@ + + + %includes; +]> + +&header; + +

    The FreeBSD Handbook

    + +

    This is an evolving, comprehensive on-line resource for + FreeBSD users. Please address comments and contributions + to <doc@freebsd.org>. + +

    Frequently Asked Questions (FAQ)

    + +

    If you have a question, chances are that someone else has + the same question. The most common of these have been + compiled here in a brief question-answer format.

    + +

    Tutorials &i.new;

    + +

    Here lie assorted documents about FreeBSD and FreeBSD related + software and hardware.

    + +

    Books

    + +

    Online documentation is useful, but any serious FreeBSD + user should consider getting some of the books + listed here. Most books that cover BSD systems apply well + to FreeBSD.

    + +

    Manual + Pages

    + +

    The manual pages for FreeBSD 2.0 and XFree86 release 3.1, + courtesy of Hinrich + Eilts.

    + +

    The Source Code

    + +

    If you like digging your fingers into source code, here is + a hypetext version of the FreeBSD kernel source. + This is brought to you courtesy of Warren + Toomey.

    + +

    The FreeBSD Documentation Project

    + +

    Like FreeBSD itself, this documentation is the product of + a volunteer effort. The goals of the project are outlined + here, as are the procedures for submitting corrections and + new material.

    + +&footer; + + + diff --git a/en/gallery/gallery.sgml b/en/gallery/gallery.sgml new file mode 100644 index 0000000000..381ec51273 --- /dev/null +++ b/en/gallery/gallery.sgml @@ -0,0 +1,879 @@ + + + %includes; +]> + + +&header; + + + + +

    All over the world, FreeBSD is powering innovative + Internet applications and services. This gallery is a + showcase of organizations and individuals who have put + FreeBSD to work for them. Browse and find out more about + what FreeBSD can do for you! + +

    To have your site added to this list, simply fill out this form. + +

    The "Powered by FreeBSD" logos above may be downloaded and displayed + on personal or commercial home pages served by FreeBSD + machines. Use of this logo or the likeness of the + BSD + Daemons for profitable gain requires the consent of + Brian Tao (creator of the "power" + logo) and Marshall + Kirk McKusick's (trademark holder for the BSD Daemon image). + +

    Commercial organizations

    + + +

    Non-commercial organizations

    + + + +

    Personal sites

    + + + +&footer; + + diff --git a/en/gifs/Makefile b/en/gifs/Makefile new file mode 100644 index 0000000000..5a39c268e2 --- /dev/null +++ b/en/gifs/Makefile @@ -0,0 +1,5 @@ +DATA= apache.gif apachepower.gif daemon.gif dir.gif doc.gif +DATA+= freebsd-advert.gif home.gif littlelogo.gif new.gif power-button.gif +DATA+= powerlogo.gif ugu_icon.gif wclogo.gif + +.include "../web.mk" diff --git a/en/includes.sgml b/en/includes.sgml new file mode 100644 index 0000000000..7ec9333880 --- /dev/null +++ b/en/includes.sgml @@ -0,0 +1,39 @@ + + + + + +'> +'> + + + + + +www@freebsd.org
    + ©right;'> + +FreeBSD Home Page'> + + +&title; +

    &i.daemon; + &title;

    '> +&home;
    &author;
    &date;
    '> + + +'> +'> diff --git a/en/index.sgml b/en/index.sgml new file mode 100644 index 0000000000..62b15c6b4c --- /dev/null +++ b/en/index.sgml @@ -0,0 +1,99 @@ + + + + FreeBSD Inc. + + + +
    + The FreeBSD Home Page +
    + +

    + + + + + + + + + + + + + + + +
    +

    +About FreeBSD

    +

    +Latest FreeBSD Information

    +

    +Obtaining and Installing FreeBSD

    +

    +Release Information

    +

    +Application Software

    +

    +Documentation

    +

    +Support

    +

    +Commercial Products and Vendors

    +

    +The FreeBSD Gallery

    +

    +Search Mailing List Archives...

    + +

    +Quick Index

    +    		 +
    +Select a server near you:
    + +
    +
    +
    Sponsored By Walnut Creek CDROM / +
    Sponsored by UGU / +
    Powered By Apache +
    +
    + +
    +
    + Copyright © 1995, 1996 FreeBSD Inc. All rights reserved.
    + www@freebsd.org +
    +    		 + +
    + + + diff --git a/en/internal/README.mirror b/en/internal/README.mirror new file mode 100644 index 0000000000..180b30dd49 --- /dev/null +++ b/en/internal/README.mirror @@ -0,0 +1,24 @@ +You can (and are encouraged to) mirror the pages with sup. +If you are running apache as installed from the ports collection the +following should make a copy of www.freebsd.org available from +http://yourhost/www.freebsd.org/. Of course, there are possible +variations on the method... + +1) The supfile to get the WWW pages: + +www release=current host=freefall.cdrom.com hostbase=/home base=/usr/local/www/data/www.freebsd.org delete old + + +2) Add to /usr/local/www/server/conf/access.conf: + + +Options FollowSymLinks Includes +XBitHack Full + + +3) Add to /usr/local/www/server/conf/srm.conf + +Alias /www.freebsd.org /usr/local/www/data/www.freebsd.org/data + +4) Create a directory /usr/local/www/counters that is writable by the +httpd daemon, then compile pagecount.C and install in /usr/local/www/cgi-bin. diff --git a/en/internal/about.sgml b/en/internal/about.sgml new file mode 100644 index 0000000000..99c67561d1 --- /dev/null +++ b/en/internal/about.sgml @@ -0,0 +1,48 @@ + + + %includes; +]> + +&header; + +

    The Machine

    + +

    The + machine, www.freebsd.org, otherwise known as + freefall.cdrom.com, is 90MHz Pentium machine with + a PCI motherboard, 48 megabytes of RAM and about 5.4 + gigabytes of disk space. Naturally, the system runs under + the FreeBSD operating system. The hardware and network + connection have been generously provided by Walnut Creek CDROM.

    + +

    The Software

    + +

    + These pages are served up by the versatile and efficient Apache http server. In + addition, there are a few locally crafted CGI scripts. + Indexing of these pages and the mailing list archive are + provided by freewais-sf, a derivative of the CNIDR freewais. + +

    The Pages

    + +

    These Web pages have been put together by John Fieber + <jfieber@freebsd.org> + with input from the FreeBSD community and you. + +

    Usage statistics for this server are updated daily:

    + + + + &footer; + + + diff --git a/en/mailto.sgml b/en/mailto.sgml new file mode 100644 index 0000000000..fbde8303fc --- /dev/null +++ b/en/mailto.sgml @@ -0,0 +1,32 @@ + + + %includes; +]> + +&header; + +

    Questions about this WWW server...

    + +

    Questions regarding this World Wide Web server should be + addressed to www@freebsd.org.

    + +

    Questions about the contents of this WWW server...

    + +

    Questions or suggestions about our documentation + (Handbook, FAQ, + Tutorials) should be addressed to doc@freebsd.org.

    + +

    Questions about FreeBSD...

    + +

    Questions regarding FreeBSD should be addressed to questions@freebsd.org. + For general information about FreeBSD, send a message to + info@freebsd.org and + you will recieve an automatic reply.

    + +&footer; + + diff --git a/en/news/newsflash.sgml b/en/news/newsflash.sgml new file mode 100644 index 0000000000..e654333022 --- /dev/null +++ b/en/news/newsflash.sgml @@ -0,0 +1,585 @@ + + + %includes; +]> + +&header; + +

    FreeBSD is a is a rapidly developing operating system. + Keeping up on the latest developments can be a chore! To + keep on top of things, be sure and check this page + periodically. Also, you may wish to subscribe to the freebsd-announce + mailing list.

    + +

    August 1996

    + + +

    July 1996

    + + +

    June 1996

    +
      +
    • 27-June-1996 + The + 2.1-960627 + snapshot has been released. + It is equivalent to a 2.1.5-BETA release.

      + +
    • 25-June-1996
      + The stuffed daemon plushies are now shipping from + Liebscher & Partner. + Please contact the company via email for more details. A picture + of an early prototype is here. Do note that + this is a prototype and that the final, shipping version has + had some improvements made to it.

      + +
    • 12-June-1996
      + The + 2.2-960612 + snapshot + has been released. The new features of this snapshot are:

      +
        +
      • A considerable number of changes to the VM system have been made + to increase the stability under certain types of load. If you + had panics under the last snapshot, try this one and see if they + persist.
        • + +
      • The AHC driver now does considerably more in the way of handling + error conditions gracefully.
        • + +
      • More cosmetic work on the installation, /stand/sysinstall now + genuinely useful after installation time (though still missing a man + page - urk!).
        • + +
      • Basically, lots-o-fixes. If you're trying to use the 2.2 SNAPs + in more serious applications, please upgrade to this version.
        • +
      + + [Note: This release will not be made available on CDROM to 2.2-SNAP + subscribers]. +
    + +

    May 1996

    +
      +
    • 1-May-1996
      + The + 2.2-960501 + snapshot + has been released. The new features of this snapshot are:

      +
        +
      • Early support for APM (automated power management) and PCCARD + (formerly PCMCIA) features of laptops. Many PCCARD devices + are supported, from modems to ethernet cards to SCSI adaptors.
        • + +
      • Adaptec AIC7850 support has been added.
        • + +
      • The Yellow Pages (NIS) support has had many optimizations made + and no longer has portions copyright under the GPL.
        • + +
      • Various VM system enhancements and a few bugs fixed (gzip'd + binaries now work again, for example).
        • + +
      • The system installation tool has been revamped with slightly + different menu behavior and a number of bugs have been fixed. + It's hoped that this installation will be more intuitive for new + users than previous ones (feedback welcomed, of course).
        • + +
      • Much miscellaneous cleanup work with the header files and sources. +
        • +
      +
    + +

    April 1996

    + +
      +
    • 15-Apr-1996
      A new + FreeBSD-emulation + mailing list has been created for discussing ongoing development efforts + for DOS, Windows, Linux and other forms of binary emulation.

      • + +
    • 14-Apr-1996
      + Berkeley Software Design, Inc. has donated their DOS emulator + rundos to the BSD community! Work is now ongoing in integrating + this into FreeBSD, and interested parties can + join the + FreeBSD-emulation mailing list to find out more about how + this work is progressing.

      • +
    + +

    March 1996

    + +
      +
    • 23-Mar-1996
      + The + 2.2-960323 + snapshot + has been released. The new features of this snapshot are:

      +
        +
      • The Intel EtherExpress Pro/100B PCI ethernet card is now + supported.
        • + +
      • The 3COM 3C590 and 3C595 ethernet cards are now supported.
        • + +
      • The ARNET (now Digiboard) Sync 570i high-speed serial card is + now supported.
        • + +
      • The Linux emulation is now good enough to run the Linux version + of Netscape, with JAVA support (as well as a number of other Linux + utilities).
        • + +
      • The Matrox Meteor frame grabber card is better supported.
        • + +
      • It is now possible to burn CDROMs using the Plasmon or HP 4080i + CDR drives (see `wormcontrol(1)').
        • + +
      • The pipe code has been substantially sped up, as have some + components of the VM system.
        • + +
      • A /dev/random device (and associated "pool of entropy") has + been added for applications which require more unpredicatable + sequences of random numbers for security. See the random(4) + man page for more info.
        • + +
      • Early NFS v3 support (not enabled by default).
        • + +
      • An early implementation of the Device Filesystem (devfs) + is available (see mount_devfs). Device switch tables are now + also dynamically built.
        • + +
      • Early IPX routing support.
        • +
      +
    + +

    November 1995

    + +
      +
    • 19-Nov-1995
      FreeBSD 2.1 is now available at + ftp sites all around the world. See the Release information for + details.

      • + +
    • 4-Nov-1995
      Snapshot 2.1.0-951104 is now + available. The purpose of this snapshot is:

      +
        +
      • To incorporate changes based on all the feedback + and bug reports received for the previous + snapshot's installation.
        • + +
      • To incorporate the latest XFree86 release (3.1.2-S) + with security enhancements. There may be more fairly + minor changes here before 2.1 is put on CD, but this + is basically what will be shipping.
        • + +
      • To get feedback on the new ``Novice Install'' split + out of the Express installation (which now truly is + an express installation).
        • + +
      • To give folks something a little less buggy to load on new + systems while they are waiting for 2.1 to come out.
        • + +
      • To fold in the latest versions of the FreeBSD + Handbook, updated for 2.1.
        • + +
      • To correct some slight whiffy english in the online help.
        • + +
      • To go back to the previous approach of just + uncommenting the ATAPI and wcd0 entries in GENERIC + for building atapi.flp. The idea of commenting out + the wd2 and wd3 entries in an effort to make things + better seems to have only made them worse in the last + SNAP. If this atapi.flp image works for you, great! + If not, I'm afraid that it's far too late to do + anything about at this stage so any failure reports + will be simply filed for post-2.1 analysis. Sorry + IDE CDROM hackers, but you had your chance!
        • +
      +
      • +
    + +

    October 1995

    + +
      + +
    • 30-Oct-1995
      The 2.1.0-951026 Snapshot has been + re-released with several bugfixes:

      + +
        +
      • Atapi boot floppy now assumes it's alone by itself + on the second IDE controller - this seems to work a + lot better for most folks who were provided with + dedicated controllers when they purchased their IDE + CDROMS. People with IDE disks on multiple IDE + controllers should NOT use this floppy image. Stick + with boot.flp and build a custom kernel or something.
        • + +
      • The apache WEB server installation makes fewer assumptions about + where you'll be putting things.
        • + +
      • Installing the secure dist no longer requires that you also + install Kerberos in order to get things like telnet to work.
        • + +
      • Boot floppy should now support the Adaptec 2940 ULTRA (this was + a side-effect more than a bug fix).
        • +
      +

      However, there are some outstanding bugs you should know + about:

      +
        +
      • sysinstall seems to croak in certain situations + if you run it after the system is installed.
        • + +
      • The FTP retry code still isn't 100% there - + apparently it now doesn't handle reselection very + well. Sigh. I'm so truly sick of looking at that + part of the code that if somebody else wanted to have + a look, I wouldn't fight them off! It seems like + every time I fix one thing, I break something else.
        • + +
      • The media selection screen protects itself from + re-entry in some situations when you'd really like it + to be allowed. Whoops!
        • +
      • Using more than one FreeBSD ``slice'' can cause problems.
        • +
      +

      • + +
    • 26-Oct-1995
      Snapshot + 2.1.0-951026 is now available. New fixes/features + include:

      +
        +
      • All /etc/sysconfig information now written correctly.
        • + +
      • WEB server option now works properly.
        • + +
      • The package installation menu now works.
        • + +
      • All the auto-installation instrumentation + (installation by config file) now works. It's + possible to install everything from start to finish + on a new system in a fully-automated fashion (if you + install a lot of systems, this is a big help).
        • + +
      • You may now read the HTML Handbook and FAQ + documents directly from the boot floppy after + installation (as well as visit any other WEB site).
        • + +
      • Failure to create a /usr is no longer an error, + just a warning.
        • + +
      • The matcd driver was shrunk down some more, + possibly resulting in a return to 4MB + operation (please test this).
        • + +
      • The latest ATAPI CDROM changes were merged in and + another atapi.flp boot image generated. Again, + please test.
        • +
      +

      • + +
    • 22-Oct-1995
      Updated floppies for snapshot + 2.1.0-951020 are now available.

      • + +
    • 20-Oct-1995
      Release cannidate snapshot + 2.1.0-951020 is now available.

      • + +
    • 06-Oct-1995
      Updateded floppies for snapshot + 2.1.0-951005 are now available.

      • + +
    • 05-Oct-1995
      Snapshot + 2.1.0-951005 is now available.

      • + +
    + +

    September 1995

    + +
      + +
    • 29-Sep-1995
      Snapshot + 2.1.0-950928 is now available.
      • + +
    + +

    August 1995

    + +
      + +
    • 19th: An IDE CD-ROM driver has been added to + FreeBSD-current, thanks to Serge Vakulenko. If you are + running -current, the driver can be enabled by + adding:
      options ATAPI
      device + wcd0
      to your kernel configuration file, + rebuilding the kernel and rebooting. Please let us know + if you have problems by sending a message to bugs@freebsd.org.
      • + +
    + +

    July 1995

    + +
      + +
    • 27-Jul-1995
      Snapshot 950726 is + now available.
      • + +
    + +

    June 1995

    + +
      + +
    • 23-Jun-1995
      Snapshot 950622 is + now available. Bugs fixed and new features include:

      +
        +
      • SLIP installation didn't ``ifconfig sl0'' + properly.
        • + +
      • It was not possible to do certain operations + atomically, e.g. just write out fdisk information, + or just extract distributions. This can now be done + from the Custom Install menu.
        • + +
      • There is now an Express Install menu that + leads you through all the necessary steps.
        • + +
      • /usr/src/bin is now properly extracted as + part of the source distribution.
        • + +
      • A couple of panics in the kernel are now fixed.
        • + +
      • DOS filesystems are now mounted read-only by + default until we figure out what it is about R/W DOS + filesystems that clobbers some systems. +
        • +
      + +

      As always, this snapshot is offered as a complete + replacement for the previous release and is aimed at + new users installing the system from scratch. Still no + update mechanism yet, but there are rumors of a project + being formed to deal with this soon. If you've any + interest in being part of it, then please send mail to + hackers@freebsd.org. + I'll also be getting involved in the whole update + mechanism issue since it's been a gaping hole for far + too long now and I'd like to see a solution sooner + rather than later. I'm sure that many of our users + feel the same way!

      +
      • + +
    • 12-Jun-1995
      Because of some glitches in the + 2.0.5 RELEASE boot disks, an update has been provide at + ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-RELEASE/UPDATES

      • + + +
    • 10-Jun-1995
      FreeBSD 2.0.5 RELEASE has been + released! See the announcement + and release notes for more details.

      • + +
    • 5-Jun-1995
      Even more installation bugs have been + fixed. Please check + ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-ALPHA/UPDATES/ + for the latest installation disks if you encounter + problems.

      • + +
    • 1-Jun-1995
      Following extensive feedback from + the ALPHA release, A new installation disk has been + generated with numerous bug fixes and enhancements. It + is available via anonymous ftp from + ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-ALPHA/UPDATES/
      • +
    + +

    May 1995

    + + + +

    April 1995

    + +
      +
    • 14-Apr-1995
      Snapshot 950412 is now + available. New features include:

      +
        +
      • Even more bugs fixed.
        • +
      • Driver for Matsushita CDROM ("Sound blaster" CDROM) in second + revision - it now supports audio commands.
        • +
      • Driver for Adaptec 294x improved.
        • +
      • FDDI network interface support (DEC cards) improved.
        • +
      • Support for DEC 100Mbit "FAST" ethernet cards (DE 500-XA).
        • +
      • /etc files revamped fairly significantly - most customization + done through one file now, /etc/sysconfig.
        • +
      • Performance improvements to networking code (connection + information now hashed rather than being stored in a linear linked + list).
        • +
      • Package code improved - now supports package dependencies.
        • +
      • New version of "libforms".
        • +
      + +

      Known problems:

      +
        +
      • If you want to run programs linked under 2.0, you + will need the file libgcc.so.261.0 which can be found + in the same directory as the snapshot release. The + file should be placed in in /usr/lib once you have + installed the release.
        • +
      • The hostname still isn't being set properly in + /etc/sysconfig for some reason - you should edit this + file after the initial installation and customize it + for your system. The comments in the file should + make the fields you need/want to change pretty + self-explanatory.
        • +
      • +
    + +

    March 1995

    + +
      +
    • 22-Mar-1995
      Snapshot 950322 is now + available. New features include:

      + +
        +
      • NIS (YP) server/client support for FreeBSD much + improved.
        • +
      • A number of panic bugs fixed.
        • +
      • Merged VM/Buffer cache much improved - hopefully last of the bugs + fixed!
        • +
      • Faster wd.c driver
        • +
      • Driver for Intel EtherExpress card
        • +
      • Driver for Matsushita CDROM ("Sound blaster" CDROM)
        • +
      • Better disk access algorithms ("clustering").
        • +
      • PCI support much improved. Interrupt sharing now works.
        • +
      • Driver for Adaptec 294x much improved
        • +
      • Boot -c writeback/save program (customized info saved across + reboots)
        • +
      • Soundcard support greatly cleaned up
        • +
      • Prototype support for ISDN
        • +
      • Support for the Creative Labs Video Spigot(tm) video card.
        • +
      • FDDI network interface support (DEC cards).
        • +
      • TCP/IP Firewall code much improved.
        • +
      • GCC 2.6.3 integrated
        • +
      + +

      If you want to run programs linked under 2.0, you will need + the file libgcc.so.261.0 which can be found in the same + directory as the snapshot release. The file should be placed + in in /usr/lib once you have installed the release.

      • + +
    + +

    February 1995

    + +
      +
    • 10-Feb-1995
      + Snapshot 950210 is now + available. New features include:

      + +
        +
      • Screen swapping bug with syscons fixed
        • +
      • XFree86 3.1.1
        • +
      • NIS (YP) support for FreeBSD much improved
        • +
      • A number of panic bugs fixed.
        • +
      • Everything listed in the February 2nd SNAP README but + much improved!
        • +
      +

      • + +
    • 2-Feb-1995:
      Snapshot + 950202 is now available. New features include:

      + +
        +
      • Merged VM/Buffer cache much improved! General + stability now approaching 2.1 quality levels.
        • +
      • Lots more bug fixes
        • +
      • Syscons now supports scrollback - use scroll lock and + arrow/travel keys to move around in your scroll-back buffer.
        • +
      • NIS (YP) support for FreeBSD as server and client.
        • +
      • First cut at on-demand ppp dialing. Docs still in + Japanese, but we're working on that! See /usr/bin/ppp + for more details.
        • +
      • IP Firewall code much improved
        • +
      • AHA294x controller support now added
        • +
      • Sony CDU33a CDROM drive support added
        • +
      • Source distribution now split into logical pieces
        • +
      • Install much improved - still not what will be + in 2.1, but a lot easier to use nonetheless.
        • +
      +
      • +
    + +

    January 1995

    + +
      +
    • 12-Jan-1995
      Snapshot + 950112 is now available. New features include:

      +
        +
      • Merged VM/Buffer cache! Does it work? Is it + faster? Find out! This is the culmination of over 6 + months of careful hacking.
        • +
      • Lots-o-bug fixes
        • +
      • Lots-o-bugs (probably)
        • +
      • Fixes to floppy driver - may fix some of the reported + problems.
        • +
      • Genius GS-4500 Scanner driver; scan pictures from FreeBSD!
        • +
      • Fixes for U24F SCSI controller
        • +
      • Many fixes to Seagate driver - Future Domain people please + test!
        • +
      • GNU Info files resurrected from the dead (see infodist)
        • +
      • share/doc now quite a bit more functional.
        • +
      • A number of new syscons features - software settable cursor, + more modes for LCD displays, dynamic console allocation, woo + doggies.
        • +
      • Still no kernel srcdist, just one big srcdist still. + Sorry.
        • +
      • Lots of changes to the installation - hopefully this one even + mostly works for once.
        • +
      • A billion other things I've forgotten for now but will + remember right after I save this document.
        • +
      +
      • +
    + +

    December 1994

    + +
      +
    • 7-Dec-1994
      If you are having trouble with + installing Release 2.0 please check + + ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE/floppies + to see if you have the most recent installation floppies. + The all new installation procedure for 2.0 brought with + it a whole set of all new bugs. With the latest + installation floppies, we hope that these bugs are fixed. +
      • +
    + +&footer; + + diff --git a/en/ports/Makefile b/en/ports/Makefile new file mode 100644 index 0000000000..09cc722be8 --- /dev/null +++ b/en/ports/Makefile @@ -0,0 +1,21 @@ +PORTINDEX= ./portindex + +.if exists(Makefile.gen) +.include "Makefile.gen" +CLEANFILES+= ${DOCS} Makefile.gen +COOKIE= Makefile.gen +.include "../web.mk" +.else +foo .DEFAULT: + ${MAKE} ${MAKEFLAGS} Makefile.gen + ${MAKE} ${MAKEFLAGS} ${.IMPSRC} +.endif + +Makefile.gen: index.sgml .NOTMAIN + if [ -f Makefile.gen ]; then mv Makefile.gen Makefile.gen.bak; fi + echo DOCS= *.sgml > Makefile.gen + +index.sgml: ports/INDEX .NOTMAIN + rm -f *.sgml + ${PORTINDEX} ports/INDEX + diff --git a/en/ports/portindex b/en/ports/portindex new file mode 100755 index 0000000000..3890433595 --- /dev/null +++ b/en/ports/portindex @@ -0,0 +1,163 @@ +#!/usr/bin/perl + +# convert a ports INDEX file to HTML +# +# by John Fieber +# Mon May 13 10:31:58 EST 1996 + +############################################################ + +# This is the base of where we ftp stuff from +$base = "ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current"; + +$today = &getdate; + +&main; + +sub getdate { + @months = ("January", "February", "March", "April", "May","June", + "July", "August", "September", "October", "November", "December"); + ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); + $year += 1900; + return "Updated $months[$mon] $mday, $year"; +} + +sub header { + local ($fh, $htext) = @_; + print $fh ""; + print $fh "$today    \">\n"; + print $fh ""; + print $fh "\n"; + print $fh "\n"; + print $fh "%includes;\n"; + print $fh "]>\n"; + print $fh "&header;\n"; +} + +sub footer { + local ($fh, $ftext) = @_; + print $fh "\n$ftext\n"; + print $fh "&footer;\n"; + print $fh "\n\n"; +} + +sub main { + + while (<>) { + chop; + s//>/g; + + ($name, $loc, $prefix, $desc, $ldesc, $owner, $cats, + $keys, $bdep, $rdep) = split('\|'); + + @cat = split(" ", $cats); + + $catkey{$name} = $cat[0]; + + $sep = ":"; + + foreach $i (@cat) { + + $stats{$i}++; + + # figure out the FTP url + $loc =~ s/\/usr/$base/; +# $loc =~ s/\/$name$//; + $ldesc =~ s/\/usr/$base/; + + # The name description and maintainer + $data{$i} .= "
    $name
    $desc
    "; + $ownerurl = $owner; + $ownerurl =~ s/<//g; + $data{$i} .= + "Maintained by: $owner
    "; + + # If there are any dependencies, list them + if ($bdep ne "" || $rdep ne "") { + $data{$i} .= "Requires: "; + @dep = split(/ /, "$bdep $rdep"); + foreach $j (@dep) { + $data{$i} .= " $j,"; + } + # remove the trailing comma + chop $data{$i}; + $data{$i} .= "
    "; + } + + # Links for browsing and downloading + $data{$i} .= "Description $sep "; + $data{$i} .= "Browse $sep "; + $data{$i} .= "Download"; + + # If the port is listed in more than one category, throw + # in some cross references + if ($#cat > 1) { + $data{$i} .= "
    Also listed in: "; + foreach $j (@cat) { + if ($j ne $i) { + $data{$i} .= " \u$j,"; + } + } + # remove the trailing comma + chop($data{$i}); + } + $data{$i} .= "

    \n" + } + + # Add an entry to the master index + $master[$portnumber] = + "$name " . + " -- $desc
    \n"; + $portnumber++; + } + + open(MOUTF, ">index.sgml"); + + &header(MOUTF, "FreeBSD Ports"); +# print MOUTF "\n"; + print MOUTF "&blurb;"; + print MOUTF "

    There are currently $portnumber ports is the +FreeBSD Ports Collection.
    Download +a gzip'd tar file of all $portnumber ports (about 2 megabytes) or +browse the following categories:\n"; + + print MOUTF "

      \n"; + + @foos = sort(keys %stats); + foreach $key (@foos) { + # For the master file... + print MOUTF + "
    • \u$key ($stats{$key})
      • "; + + # Create the category file + open(OUTF, ">$key.sgml"); + &header(OUTF, "FreeBSD Ports: \u$key"); + print OUTF "
      \n"; + $d = join("\n", sort(split(/\n/, $data{$key}))); + $d =~ s/##([^#]*)##/$catkey{$1}/g; + print OUTF $d; + print OUTF "
      \n"; + &footer(OUTF, "
      Port Categories" . + " -- Index"); + close(OUTF); + + } + print MOUTF "
    \n"; + print MOUTF + "\n"; + &footer(MOUTF, ""); + close(MOUTF); + + # Create the master index file + open(MINDEX, ">master-index.sgml"); + &header(MINDEX, "FreeBSD Ports Collection Index"); + print MINDEX "

    \n"; + print MINDEX sort @master; + print MINDEX "

    "; + &footer(MINDEX, "
    Port Categories"); + close(MINDEX); + +} diff --git a/en/ports/ports.inc b/en/ports/ports.inc new file mode 100644 index 0000000000..0dfe1ee34c --- /dev/null +++ b/en/ports/ports.inc @@ -0,0 +1,34 @@ +

    The FreeBSD Ports Collection offers a simple way for users and +administrators to install applications. Each ``port'' listed here +contains any patches necessary to make the original application source +code compile and run on FreeBSD. Installing an application is as +simple as downloading the port, unpacking it and typing make +in the port directory. The Makefile automatically fetches the +application source code, either from a local disk or via ftp, +unpacks it on your system, applies the patches, and compiles. If +all goes well, simply type make install to install the +application.

    + +

    Below are the listings of ports currently available, arranged +by application type. Four links are available for each port listed:

    + +
    +
    Description
    This fetches a description +of the application from the FTP archive (ftp.freebsd.org).
    + +
    Browse
    This is a link to the FTP archive directory +for the port where you can examine the Makefile and patches.
    + +
    Download
    This is a link to a gzip'd tar file +containing the port. Be sure to tell your browser to save +rather than display!
    + +
    Maintainer
    The person responsible for maintaining +the port. If you have problems with a specific port, +contact this person.
    +
    + +

    For more information, see The +ports collection and Porting applications in the FreeBSD Handbook.

    diff --git a/en/releases/1.1.5/CONTRIB.386BSD b/en/releases/1.1.5/CONTRIB.386BSD new file mode 100644 index 0000000000..a99b527c48 --- /dev/null +++ b/en/releases/1.1.5/CONTRIB.386BSD @@ -0,0 +1,196 @@ + + + + + + + + 386BSD Release 0.1 + Contributor List + + Lynne Greer Jolitz + William F. Jolitz + + +_H_a_r_d_w_a_r_e _a_n_d _M_o_n_e_t_a_r_y _C_o_n_t_r_i_b_u_t_o_r_s + +Many people and firms have provided hardware and/or money to +try and keep this unfunded project going despite a recession +and hard times -- usually by digging into their own pockets. +Each of these contributors gave, not only because they +believed that the continuation of 386BSD is vital to the +health of the research, educational, and development commun- +ities, but also because they realize that an individual can +and does make a difference! + +Without the help of the people listed here, this release +would simply not have been possible. We would especially +like to thank Thos Sumner, whose loan of a 486/50 SCSI PC +made development go more rapidly. The rest of the 386BSD +user community should make special note of all these people +and firms and commend them for their generosity and +foresight. + +We hope that their leadership and vision will serve as shin- +ing examples to the entire 386BSD user community, and serve +to encourage others to actively participate in 386BSD. + + Jan van den Bosch + Compaq Computer Corporation + Cyrix Corporation + Dixon Dick + Steven P. Donegan + Jon Erickson + Eric J. Haug + Bob McGhee + Jesus Monroy Jr. + Andrew Moore + Rich Murphey + Mark Ng + Kenji Okamoto + John Plocher + Mark R. Riordan + John B. Scalia + Steve Sizemore + Thos Sumner + David E. Tweten + + + + + +386BSD CONTRIB LIST 1 July 1992 + + + + + + + + + + +_S_o_f_t_w_a_r_e _C_o_n_t_r_i_b_u_t_o_r_s + +The following people have contributed key software programs, +modules and fixes, including novel work and ports of popular +public domain user programs. Some of this software was +directly contributed to us, while other items were made +available to all users via the network. Occasionally, +several people came up with a variety of approaches for a +single item. In this instance, we tried to choose the one +which we felt would best serve the rest of the 386BSD user +base for this release. However, the creativity and persever- +ance of all the software contributors trying to make 386BSD +better for the entire 386BSD user community was consider- +able. Each individual effort is worthy of pride. + +We wish to personally thank all of these people, as they +have helped make 386BSD Release 0.1 a reality. We hope that +these contributors and all the rest of the 386BSD user com- +munity will continue to actively participate to make future +releases even better! + + James Van Artsdalen + Scott Burris + Randall Dean + Chris Demetriou + Mark Eichin + Bruce Evans + Steve Ferguson + Jeffrey Goh + David Greenman + Amancio Hasty Jr + John W. Hatley + Eric J. Haug + Tom Ivar Helbekkmo + John D. Irwin + Peter Klingebiel + Paul Kranenburg + Daniel Lanciani + Karl Lehenbauer + Lee M. J. McLoughlin + Andrew J. Michael + Jesus Monroy Jr. + Daniel A. Muntz + Richard Murphey + Glen Overby + Brad Parker + Herb Pereyl + Ken Raeburn + Paul Richards + Guido van Rooij + Peng-Toh Sim + Wolfgang Solfrank + Dave Stanhope + + +386BSD CONTRIB LIST 2 July 1992 + + + + + + + + + + + Mark Tinguely + Linus Torvalds + Richard Tobin + Rob Warnock + Christian Wiedmann + Pace Willisson + Joerg Wunsch + + And all of the other 386BSD Software Contributors. + + +_S_u_p_p_o_r_t _a_n_d _A_d_v_i_c_e _C_o_n_t_r_i_b_u_t_o_r_s + +Many people have continually encouraged us over the course +of these releases, and provided us with technical advice and +guidance. These people have also spent considerable time and +energy getting this software out to the rest of the 386BSD +community. While it is impossible for us to list everyone +who has been supportive of 386BSD, we wish to personally +thank some of the people who have been of special assistance +to us directly over the course of getting 386BSD out the +door. + + Bruce Blakely + Dave Campbell + Free Software Foundation + Paul Fromberg + Tom Genereaux + John Gilmore + Dave Harris + Jim Joyce + Dan Kionka + Dory Leifer + Per Lindqvist + Marshall Midden + Rich Morin + Silicon Valley Computer Society + John Sokol + Thos Sumner + Karen Trocki + Rob Warnock + + and a special thanks to: + John Erickson, Tami Zemel, Ray Valdez, Monica Berg, Michael Floyd + and everyone else at Dr. Dobbs Journal. + Juergen Fey, Rainer Huttenloher, Gerd Oskar Bausewein + and everyone else at UNIX Magazin. + + And all of the 386BSD User Community. + + + + + +386BSD CONTRIB LIST 3 July 1992 + + + diff --git a/en/releases/1.1.5/CONTRIB.FreeBSD b/en/releases/1.1.5/CONTRIB.FreeBSD new file mode 100644 index 0000000000..37bae9cb03 --- /dev/null +++ b/en/releases/1.1.5/CONTRIB.FreeBSD @@ -0,0 +1,191 @@ + FreeBSD 1.1.5 + Contributor List + + + +Derived Software Contributors: + +This software was originally derived from William F. Jolitz's 386BSD +release 0.1, though very little of the original 386BSD specific code +remains. + +Please see the file CONTRIB.386BSD for the list of contributors from +386BSD. + +Included in this release are some of the patches from the old 386BSD +patch kit version 0.2.4, and therefore the names of contributors from the +patch kit are also listed below. + +Finally, there are portions of NetBSD that have been integrated into +FreeBSD as well, and we would therefore like to thank all the contributors +to NetBSD for their work. + + +Hardware Contributors: + +A special thanks to Robert Bruce and Jack Velte of Walnut Creek CDROM +for providing a 486/DX2-66 EISA/VL system that is being used for the +development work. It would have been impossible to do this release +with out their support. + +Dermot McDonnell for his donation of a Toshiba XM3401B CDROM +drive. + + +The FreeBSD Core Team (in alphabetical order): + +Andrew A. Chernov +John Dyson +David Greenman +Rodney W. Grimes +Jordan K. Hubbard +Scott Mace +Andrew Moore +Rich Murphey +Geoff Rehmet +Paul Richards +Andreas Schulz +Nate Williams +Garrett A. Wollman + + +Additional FreeBSD Contributors (no particular order): + +Atsushi Murai +Keith Moore +Adam Glass +Andrew Herbert +Bob Wilcox +Bruce Evans +Charles Hannum +Chris G. Demetriou +Chris Torek +Christoph Robitschko +Curt Mayer +Dave Burgess +Dave Rivers +David Dawes +Frank Maclachlan +Gary A. Browning +Gary Clark II +Guido van Rooij +Havard Eidnes +Holger Veit +Ishii Masahiro, R. Kym Horsell +J.T. Conklin +James Clark +James da Silva et al +Jim Wilson +Joerg Wunsch +Julian Elischer +Julian Stacey > +Keith Bostic +Marc Frajola +Mark Tinguely +Martin Birgmeier +Paul Kranenburg +Paul Mackerras +Poul-Henning Kamp +Rob Shady +Sascha Wildner +Sean Eric Fagan +Serge V. Vakulenko +Steven Wallace +Søren Schmidt +Terry Lee +Theo Deraadt +Yuval Yarom + + +Patch kit patch contributors (no particular order): + +Adam Glass +Adrian Hall +Andrew A. Chernov +Andrew Herbert +Andrew Moore +Andy Valencia +Arne Henrik Juul +Bakul Shah +Barry Lustig +Bob Wilcox +Branko Lankester +Brett Lymn +Bruce Evans +Charles Hannum +Chris G. Demetriou +Chris Torek +Christoph Robitschko +Daniel Poirot +Dave Burgess +Dave Rivers +David Dawes +David Greenman +Eric J. Haug +Felix Gaehtgens +Frank Maclachlan +Gary A. Browning +Geoff Rehmet +Goran Hammarback +Guido van Rooij +Guy Harris +Havard Eidnes +Herb Peyerl +Ishii Masahiro, R. Kym Horsell +J.T. Conklin +Jagane D Sundar < jagane@netcom.com > +James Clark +James Jegers +James W. Dolter +James da Silva et al +Jay Fenlason +Jim Wilson +Joerg Lohse +Joerg Wunsch +John Dyson - +John Woods +Jordan K. Hubbard +Julian Elischer +Julian Stacey > +Karl Lehenbauer +Keith Bostic +Ken Hughes +Kent Talarico +Kevin Lahey +Marc Frajola +Mark Tinguely +Martin Renters +Michael Galassi +Mike Durkin +Nate Williams +Nick Handel +Pace Willisson +Paul Kranenburg +Paul Mackerras +Paul Popelka +Peter da Silva +Phil Sutherland +Poul-Henning Kamp +Ralf Friedl +Rich Murphey +Rick Macklem +Robert D. Thrush +Rodney W. Grimes +Rog Egge +Sascha Wildner +Scott Burris +Scott Reynolds +Sean Eric Fagan +Simon J Gerraty +Stephen McKay +Terry Lambert +Terry Lee +Warren Toomey +Wiljo Heinen +William Jolitz +Wolfgang Solfrank +Wolfgang Stanglmeier +Yuval Yarom + +$Id: CONTRIB.FreeBSD,v 1.1.1.1 1996-09-24 17:45:48 jfieber Exp $ diff --git a/en/releases/1.1.5/COPYRIGHT.386BSD b/en/releases/1.1.5/COPYRIGHT.386BSD new file mode 100644 index 0000000000..c53cb8865b --- /dev/null +++ b/en/releases/1.1.5/COPYRIGHT.386BSD @@ -0,0 +1,131 @@ + + + + + + + + 386BSD Release 0.1 + Copyright + + + /* + * Copyright (c) 1989, 1990, 1991, 1992 William F. Jolitz, TeleMuse + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. All advertising materials mentioning features or use of this software + * must display the following acknowledgement: + * This software is a component of "386BSD" developed by + * William F. Jolitz, TeleMuse. + * 4. Neither the name of the developer nor the name "386BSD" + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * 386BSD WAS DEVELOPED BY WILLIAM F. JOLITZ. + * 386BSD IS INTENDED FOR RESEARCH AND EDUCATIONAL PURPOSES. + * THIS SOFTWARE SHOULD NOT BE CONSIDERED TO BE A COMMERCIAL PRODUCT. + * THE DEVELOPER URGES THAT USERS WHO REQUIRE A COMMERCIAL PRODUCT + * NOT MAKE USE OF THIS WORK. + * + * FOR USERS WHO WISH TO UNDERSTAND THE 386BSD SYSTEM DEVELOPED + * BY WILLIAM F. JOLITZ, WE RECOMMEND THE USER STUDY WRITTEN + * REFERENCES SUCH AS THE "PORTING UNIX TO THE 386" SERIES + * (BEGINNING JANUARY 1991 "DR. DOBBS JOURNAL", USA AND BEGINNING + * JUNE 1991 "UNIX MAGAZIN", GERMANY) BY WILLIAM F. JOLITZ AND + * LYNNE GREER JOLITZ, AS WELL AS OTHER BOOKS ON UNIX AND THE + * ON-LINE 386BSD USER MANUAL BEFORE USE. A BOOK DISCUSSING THE INTERNALS + * OF 386BSD ENTITLED "386BSD FROM THE INSIDE OUT" WILL BE AVAILABLE LATE 1992. + * + * THIS SOFTWARE IS PROVIDED BY THE DEVELOPER ``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 DEVELOPER 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 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + */ + + + 386BSD Copyright 1 July 1992 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 386BSD Copyright 2 July 1992 + + + + diff --git a/en/releases/1.1.5/COPYRIGHT.FreeBSD b/en/releases/1.1.5/COPYRIGHT.FreeBSD new file mode 100644 index 0000000000..58c827bcd2 --- /dev/null +++ b/en/releases/1.1.5/COPYRIGHT.FreeBSD @@ -0,0 +1,122 @@ +This software contains software developed by the University of +California, Berkeley, and its contributors; by the Free Software +Foundation; by the University of Illinois; by the Massachusetts +Institute of Technology; by the University of Vermont and State +Agricultural College; by Carnegie Mellon University; and by a large +number of contributors, whose names are listed in the notices below. + +Portions of this software are subject to one or more of the following +copyright notices. Please see the individual files for the terms and +conditions. + + +Copyright (C) 1980, 1983, 1986, 1988, 1990, 1991, Regents of the + University of California +Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, Free + Software Foundation, Inc. +Copyright (C) 1976, Board of Trustees of the University of Illinois +Copyright (C) 1980, 1981, Ken Harrenstien +Copyright (C) 1982, 1988, 1989, Walter Tichy +Copyright (C) 1983, 1986, 1992, 1993, Eric P. Allman +Copyright (C) 1983, Kenneth L. Greer +Copyright (C) 1984, 1985, 1986, 1987, 1992, Sun Microsystems, Inc. +Copyright (C) 1984, 1987, Stephen L. Moshier +Copyright (C) 1984, 1989, 1990, Bob Corbett and Richard Stallman +Copyright (C) 1984, University of British Columbia +Copyright (C) 1985, 1986, Wayne A. Christopher +Copyright (C) 1985, 1987, 1988, 1989, Adobe Systems, Inc. +Copyright (C) 1985, Stichting Mathematisch Centrum +Copyright (C) 1986, 1987, 1989, 1990, 1991, 1992, Ian F. Darwin +Copyright (C) 1986, 1987, 1989, Frame Technology, Inc. +Copyright (C) 1986, 1987, 1992, Daniel D. Lanciani +Copyright (C) 1986, 1987, Ed James +Copyright (C) 1986, Breslow +Copyright (C) 1986, Gary S. Brown +Copyright (C) 1986, Larry Wall +Copyright (C) 1986, Noah Morgan +Copyright (C) 1986, Stephen Satchell +Copyright (C) 1987, 1988, 1989, 1990, 1991, 1992, Carnegie Mellon University +Copyright (C) 1987, 1988, 1989, Sony Corp. +Copyright (C) 1987, 1988, John Stanback +Copyright (C) 1987, 1988, Ronald S. Karr and Landon Curt Noll +Copyright (C) 1987, 1989, 1990, 1991, Massachusetts Institute of Technology +Copyright (C) 1987, David C. Elliott. +Copyright (C) 1987, IBM Corporation +Copyright (C) 1987, Stuart Cracraft +Copyright (C) 1987, United States Army +Copyright (C) 1988, 1989, 1990, 1993, 1994, Paul A. Vixie +Copyright (C) 1988, 1989, Adam de Boor +Copyright (C) 1988, 1990, University of Utah +Copyright (C) 1988, Julian Onions +Copyright (C) 1988, Mark Nudleman +Copyright (C) 1988, Rayan S. Zachariassen +Copyright (C) 1989, 1990, 1991, 1992, 1993, Frank Kardel +Copyright (C) 1989, 1990, 1991, 1992, 1993, William S. Jolitz +Copyright (C) 1989, 1990, 1991, 1992, Brian Berliner +Copyright (C) 1989, Berkeley Softworks +Copyright (C) 1989, Dale Schumacher +Copyright (C) 1989, Dave Taylor +Copyright (C) 1989, Kenneth Almquist +Copyright (C) 1989, Matthew Self +Copyright (C) 1989, Robert V. Baron +Copyright (C) 1990, 1991, 1992, 1993, AT&T Bell Laboratories and Bellcore +Copyright (C) 1990, 1991, John W. Eaton +Copyright (C) 1990, 1991, Paul Eggert +Copyright (C) 1990, 1993, Andrew Moore +Copyright (C) 1990, John Robert LoVerso +Copyright (C) 1990, Open Software Foundation, Inc. +Copyright (C) 1990, RSA Data Security, Inc. +Copyright (C) 1991, 1992, 1993, 1994, Chris Provenzano +Copyright (C) 1991, 1992, 1993, Ian Lance Taylor +Copyright (C) 1991, 1992, Per Bothner +Copyright (C) 1991, 1992, Per Cederqvist +Copyright (C) 1991, Gregory M. Christy +Copyright (C) 1991, Inge Wallin +Copyright (C) 1991, Joseph Friedman +Copyright (C) 1992, 1993, 1994, David L. Mills +Copyright (C) 1992, 1993, Christopher G. Demetriou +Copyright (C) 1992, 1993, Garrett A. Wollman +Copyright (C) 1992, 1993, HD Associates +Copyright (C) 1992, 1993, Holger Veit +Copyright (C) 1992, 1993, Jean-Loup Gailly +Copyright (C) 1992, 1993, 1994 Joerg Wunsch +Copyright (C) 1992, 1993, John Brezak +Copyright (C) 1992, 1993, Motorola, Inc. +Copyright (C) 1993, 1994, Jordan Hubbard +Copyright (C) 1992, 1993, Soeren Schmidt +Copyright (C) 1992, 1993, Theo de Raadt +Copyright (C) 1992, 1993, University of Vermont and State Agricultural College +Copyright (C) 1992, Cygnus Support +Copyright (C) 1992, Diomidis Spinellis +Copyright (C) 1992, Henry Spencer +Copyright (C) 1992, Jeff Polk +Copyright (C) 1992, Terrence R. Lambert +Copyright (C) 1992, University of Guelph +Copyright (C) 1993, 1994, Andrew A. Chernov +Copyright (C) 1993, 1994, David Greenman +Copyright (C) 1993, 1994, John S. Dyson +Copyright (C) 1993, Adam Glass +Copyright (C) 1993, Atsushi Murai +Copyright (C) 1993, Brian Moore +Copyright (C) 1993, Daniel Boulet and RTMX Inc. +Copyright (C) 1993, David Muir Sharnoff +Copyright (C) 1993, David Parsons +Copyright (C) 1993, Gary Clark II +Copyright (C) 1993, Hannu Savolainen +Copyright (C) 1993, Herb Peyerl +Copyright (C) 1993, Herve Schauer Consultants +Copyright (C) 1993, Julian Elischer +Copyright (C) 1993, Julian Stacey +Copyright (C) 1993, K. J. Dryllerakis +Copyright (C) 1993, Martin Birgmeier +Copyright (C) 1993, Paul Kranenburg +Copyright (C) 1993, Paul Richards +Copyright (C) 1993, Thomas Koenig +Copyright (C) 1993, Winning Strategies, Inc. +Copyright (C) 1994, Christoph M. Robitschko +Copyright (C) 1994, University of Maryland +Copyright (C) 1993, 1994, jc@irbs.UUCP (John Capo), + vak@zebub.msk.su (Serge Vakulenko), + ache@astral.msk.su (Andrew A. Chernov) + +$Id: COPYRIGHT.FreeBSD,v 1.1.1.1 1996-09-24 17:45:48 jfieber Exp $ diff --git a/en/releases/1.1.5/COPYRIGHT.USL b/en/releases/1.1.5/COPYRIGHT.USL new file mode 100644 index 0000000000..5f3f151c5c --- /dev/null +++ b/en/releases/1.1.5/COPYRIGHT.USL @@ -0,0 +1,45 @@ +Copyright (c) UNIX System Laboratories, Inc. +All or some portions of this software are derived from +material licensed to the University of California by +American Telephone and Telegraph Co. or UNIX System Laboratories, Inc. +and are reproduced herein with the permission of +UNIX System Laboratories, Inc. + +Additionally, the following files contained herein constitute +trade secrets of UNIX System Laboratories, Inc. and their contents +are not to be disclosed to any third party: + +sys/kern/init_main.c +sys/kern/kern_clock.c +sys/kern/kern_exec.c [*] +sys/kern/kern_exit.c +sys/kern/kern_physio.c [**] +sys/kern/kern_sig.c +sys/kern/kern_synch.c +sys/kern/subr_rmap.c [*] +sys/kern/sys_generic.c +sys/kern/sys_process.c +sys/kern/sysv_shm.c +sys/kern/tty.c +sys/kern/tty_subr.c [*] +sys/kern/vfs_bio.c [*] +sys/kern/vfs_syscalls.c +sys/sys/buf.h +sys/sys/proc.h +sys/sys/shm.h +sys/sys/tty.h +sys/ufs/dinode.h +sys/ufs/inode.h +sys/ufs/ufs_bmap.c +sys/ufs/ufs_disksubr.c +sys/ufs/ufs_inode.c +sys/ufs/ufs_vnops.c +usr.bin/cpio/cpio.c [*] + +[*] These file are NOT contained in FreeBSD + +[**] The version of this file in FreeBSD is belived to be clear of any USL + copyright and/or trade secret. + + +$Id: COPYRIGHT.USL,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/en/releases/1.1.5/KNOWNBUGS b/en/releases/1.1.5/KNOWNBUGS new file mode 100644 index 0000000000..42b730b985 --- /dev/null +++ b/en/releases/1.1.5/KNOWNBUGS @@ -0,0 +1,73 @@ +This file lists known problems with this release of FreeBSD + +'hanging keyboard' +------------------ +There are still problems with certain machines appearing to 'hang' on +bootup even though a prompt is there. The most common machines that +exhibit these problems are Gateway 2000 machines with PHOENIX bios's but +other machines with PHOENIX bios also exhibit this behavior. + The temporary solution until you can get the distribution +installed on your hard-drive is to 'bounce' on a key like shift or +num-lock (which works well since you can see when the keyboard comes +back to life) until the boot sequence is finished. The keyboard will +work fine for installing FreeBSD onto the hard-drive. + +/usr/bin/gdb: + The gdb in the release will not work on shared objects nor will it + work with C++ executables. Please use the gdb in the ports area for + debugging shared and/or C++ code. This is just a work-around until + we can transition to the new version of gdb completely. See below. + +/usr/gnu/bin/gdb: + This is the gdb from the ports area (if installed), also known as + gdb-4.11. There is a problem using gdb-4.11 to debug a core-file + generated by a binary which uses shared libraries. The problem is + basically due to the fact that the shared libraries are mmap'ed at + addresses in the memory space of the binary which are not accessible + to gdb-4.11 at the time that it tries to examine the core-file. This + usually manifests itself in "Cannot access memory at address " + messages at startup and "#0 in end ()" when you try to do + a backtrace ("bt"). + + Workaround: start gdb-4.11 without reference to the core-file, + e.g. "gdb fubar". Set a breakpoint in main and run the inferior + so that gdb-4.11 can resolve references to the shared libraries. + After this, use the "core-file" command to force gdb-4.11 to + load the core-file, e.g. "core-file fubar.core". Since all + shared library references were previously resolved gdb-4.11 can + now access the shared libraries and things like "bt" now work. + You will also be able to reference items previously on the stack + (from the core file), but all globals will show up as zero'd. + All these problems may be avoided if you compile the application + with -static. + +/sys/i386/isa/if_ep.c + The 3c509 driver will hang under heavy network loads and take your + machine off the network. (Though the machine will continue to run with + no network facilities) + + Workaround: Try a "ifconfig ep0 down" and a "ifconfig ep0 up" + to get it running again. + +/sys/i386/isa/bt742a.c + The Bt445S and Bt747 controllers can cause problems when ISA DMA + is selected as an option. With the EISA controller the remedy is + easy - simply turn it off using your EISA configuration utility. + With the Bt445S, which is a VLB card, you must switch the undocumented + "SW10" on "SB2" to the off position. Also note that certain revisions + of the Buslogic board (Revision C or earlier, firmware revision <3.37) + will cause DATA CORRUPTION with systems containing more than 16MB of + memory. If you find this to be the case, temporarily remove your + extra memory and contact Buslogic for an upgrade! + +fsck: + fsck can go into an endless loop in the repair/fsck cycle on + a corrupted filesystem. The message "VALUES IN SUPER BLOCK + DISAGREE WITH THOSE IN FIRST ALTERNATE" is very misleading. + fsck compares the superblock with the alternate in the last + cylinder group? So if this block is corrupt, you have no chance + to get the filesystem repaired. You can answer on the question + "UPDATE STANDARD SUPERBLOCK" with yes and get always the same + error message on the next fsck. + +$Id: KNOWNBUGS,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/en/releases/1.1.5/MIRROR.SITES b/en/releases/1.1.5/MIRROR.SITES new file mode 100644 index 0000000000..a3e9669787 --- /dev/null +++ b/en/releases/1.1.5/MIRROR.SITES @@ -0,0 +1,59 @@ + +The FreeBSD software is being mirrored at the following locations: + +Country Site/Directory/Maintainer +======= ========================================================= + +Australia minnie.cs.adfa.oz.au:/BSD/FreeBSD-1.1-RELEASE + + +Australia ftp.physics.su.oz.au:/FreeBSD + David Dawes + +Australia ftp.une.edu.au:/pub/FreeBSD + Gordon Smith + +Austria ftp.tu-graz.ac.at:/pub/FreeBSD + + +Finland ftp.funet.fi:/pub/unix/FreeBSD + + +France ftp.ibp.fr:/pub/FreeBSD + + +Germany ftp.informatik.tu-muenchen.de:/pub/comp/os/bsd/FreeBSD + + +Germany ftp.uni-duisburg.de:/pub/unix/FreeBSD + + +Germany gil.physik.rwth-aachen.de:/pub/FreeBSD + + +Hong Kong ftp.cs.cuhk.hk:/pub/FreeBSD + + +Israel orgchem.weizmann.ac.il:/pub/FreeBSD + + +Netherlands ftp.nl.net:/pub/os/FreeBSD + + +Russia ftp.kiae.su:/FreeBSD + + +UK src.doc.ic.ac.uk:/packages/FreeBSD + + +USA gatekeeper.dec.com:/pub/BSD/FreeBSD + + +USA freebsd.uml.edu:/FreeBSD + + +USA wuarchive.wustl.edu:/systems/unix/FreeBSD + + + +$Id: MIRROR.SITES,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/en/releases/1.1.5/Makefile b/en/releases/1.1.5/Makefile new file mode 100644 index 0000000000..1340175acd --- /dev/null +++ b/en/releases/1.1.5/Makefile @@ -0,0 +1,6 @@ +DATA= CONTRIB.386BSD CONTRIB.FreeBSD COPYRIGHT.386BSD +DATA+= COPYRIGHT.FreeBSD COPYRIGHT.USL KNOWNBUGS MIRROR.SITES +DATA+= PERSONAL.ACKS REGISTER.FreeBSD RELNOTES.FreeBSD ROSTER.FreeBSD +DATA+= SUPPORT.TXT TODO-1.1.5 + +.include "../../web.mk" diff --git a/en/releases/1.1.5/PERSONAL.ACKS b/en/releases/1.1.5/PERSONAL.ACKS new file mode 100644 index 0000000000..d80896428b --- /dev/null +++ b/en/releases/1.1.5/PERSONAL.ACKS @@ -0,0 +1,17 @@ +The following contributors would like to make these personal +acknowledgements (in no particular order): + +Garrett Wollman would like to thank Gary Barbour and Steve Ackerman of +Utah; Tim Raymond, Jim White, and Jim Ertle of UVM; Malcolm Carlock at +UNR; and John Wroclawski of MIT. + +Nate Williams would like to thank Jaye Mathisen and the entire Computer +Science department of Montana State University for their help, hardware +and encouragement. + +Jordan Hubbard would like to thank IEUNET for bringing the INTERNET to +Ireland, thus making his participation possible at all (albeit expensive) +and his Mom, who would probably be pleased if only she understood any of +this. Hi Mom. + +$Id: PERSONAL.ACKS,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/en/releases/1.1.5/REGISTER.FreeBSD b/en/releases/1.1.5/REGISTER.FreeBSD new file mode 100644 index 0000000000..a7814005ff --- /dev/null +++ b/en/releases/1.1.5/REGISTER.FreeBSD @@ -0,0 +1,86 @@ +In the absence of any other mechanism for counting the number of users +of FreeBSD, we like to as kindly suggest that you take a few minutes +to please register with the counter set up by +. + +The justification for such "registration" is twofold: First, we sincerely do +wish to know just what the size and demographics of our user-base are +in order to better support its needs. Second, it's a sad fact that many +people rely on counters and statistics (even when highly dubious) rather +than actual experience when chosing an operating system, and the best we +can hope to do in such circumstances is to at least try to provide some +indication of how popular we are (or are not). This is not how we recommend +that people go about chosing an operating system, but the necessity of +"marketing" remains an undeniable fact of life. + +The FreeBSD team does not necessarily feel that Harald's counter represents +the best approach to such statistics gathering, and its accuracy will only +be as good as people's willingness to register with it (which may not reflect +the actual OS population at any single point in time), but in the total absence +of any other mechanism for providing such useful statistics, it's certainly a +start and we thank Harald for his efforts in providing this service. +It's a community service, and of potential benefit to everyone (all *BSD +users), so let's see if we can't make it work! + +Included below is the standard blurb from the counter. + +Thanks in advance, + + The FreeBSD team. + + +How to get registered +===================== + +In brief: + + [To register a running installation of FreeBSD] + Send E-mail to bsd-counter@uninett.no with the SUBJECT line + + "I use FreeBSD at " + +Introduction +============ +The intention of this counting project is to count all users of UNIXes +that are: + + - BSD-derived + - Freely available + +The variants NetBSD, 386BSD and FreeBSD are currently distinguished. + +(NOTE: Linux is NOT BSD-derived. If you use that, send mail to +linux-counter@uninett.no instead!!!) + +The information is *not* used for any purpose but statistics, and unless +you request it, information about single persons are *never* made public. +(A list of users who have requested publication is available from the +FTP file ftp://aun.uninett.no/pub/misc/386bsd/persons) + +How to register +=============== +Send E-mail to bsd-counter@uninett.no + +The subject should be + + I use FreeBSD|NetBSD|386BSD at + +Where FreeBSD, NetBSD or 386BSD is the particular variant you're using +and "place" can be school, work or home, or a combination of these. + +You will get back a letter with 3 things: + + - An acknowledgement + - A form that you can fill out and send in with more information + about yourself, your machine, and your 386bsd-using friends + - A report giving the current status of the counter + +You can update your "vote" at any time, by sending an E-mail message +from the same account. Duplicates will be weeded out. + +The current report, available by anonymous FTP to aun.uninett.no, +directory pub/misc/386bsd-counter, file "short", is given below. + +For all questions, contact Harald.T.Alvestrand@uninett.no! + +$Id: REGISTER.FreeBSD,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/en/releases/1.1.5/RELNOTES.FreeBSD b/en/releases/1.1.5/RELNOTES.FreeBSD new file mode 100644 index 0000000000..3707fc26a9 --- /dev/null +++ b/en/releases/1.1.5/RELNOTES.FreeBSD @@ -0,0 +1,313 @@ + RELEASE NOTES + FreeBSD + Release 1.1.5 + +1. Technical overview +--------------------- + +FreeBSD is a freely available, full source 4.3 (+4.4 enhancements) BSD +release for Intel i386/i486 (or compatable) based PC's. It is based +on Bill Jolitz's 386BSD 0.1, with additions from "the patchkit", +NetBSD, CSRG, and the Free Software Foundation. + +Since our first release of FreeBSD 1.0, many hundreds of bugs have been +fixed, features added, and the overall quality of the system improved +almost imeasurably. FreeBSD 1.1.5 represents the culmination of almost +18 months of work and many thousands of man hours put in by our all-volunteer +working group. We hope you enjoy it! + +Many packages have also been upgraded or added, such as XFree86 2.1, +xview 3.2, elm, nntp, mh, InterViews and dozens of other miscellaneous +utilities have been ported and are now available as add-ons. See the next +section of this document for more details. + +For a list of contributors, please see the files "CONTRIB.FreeBSD" and +"CONTRIB.386BSD", which should be bundled with your distribution. + +Also see the new "REGISTER.FreeBSD" file for information on registering +with the "Free BSD user counter". We've also provided a list of who's +responsible for what (so that you may query them directly) in the +"ROSTER.FreeBSD" file; use of this file is encouraged to ensure faster +resolution of an problems you may have! + +The core of FreeBSD does not contain DES code which would inhibit its +being exported outside the United States. There is an add-on package +to the core distribution, for use only in the United States, that +contains the programs that normally use DES. The auxilliary packages +provided separately can be used by anyone. A freely (from outside the U.S.) +exportable European distribution of DES for our non U.S. users also exists +and is described in the FreeBSD FAQ. + + +2. Supported Configurations +--------------------------- + +FreeBSD currently runs on a wide variety of ISA, EISA and PCI bus based +PC's, ranging from 386sx to Pentium class machines (though the 386sx is +not recommended). Support for generic IDE or ESDI drive configurations, +various SCSI controller, network and serial cards is also provided. + +Following is a list of all currently known disk controllers and +ethernet cards known to work with FreeBSD. Other configurations may +very well work, and we have simply not received any indication of +this. + + +2.1. Disk Controllers + +WD1003 (any generic MFM/RLL) +WD1007 (any generic IDE/ESDI) + +Adaptec 154x series ISA SCSI controller (as long as you have less than +16MB of main memory). + +Adaptec 174x series EISA SCSI controller in standard and enhanced mode. + +[Note that Buslogic was formerly known as "Bustec"] +Buslogic 545S. +Buslogic 445S VLB SCSI controller +Buslogic 742A and 747. +Buslogic 942A PCI + +Please see special notes in /usr/src/KNOWNBUGS (filed under bt742a.c) for +details concerning possible buggy firmware and undocumented switch settings +that may be necessary for proper operation of your Bt445S controller. + +DTC 3290 EISA SCSI controller in 1542 emulation mode. + +Ultra Store 14F and 34F. + +Seagate ST01/02 SCSI controllers. + +Future Domain 8xx/950 series SCSI controllers. + +With all supported SCSI controllers, full support is provided for +SCSI-I & SCSI-II peripherals, including Disks, tape drives (including +DAT) and CD ROM drives. Note: This and the mcd driver (Mitsumi CDROM +interface card) is the only way a CD ROM drive may be currently +attached to a FreeBSD system; we do not support SoundBlaster CDROM +interface, or other "mini SCSI" adapters. + +Some controllers have limitations with the way they deal with >16MB of memory, +due to the fact that the ISA bus only has a DMA address space of 24 bits. +If you do your arithmetic, you'll see that this makes it impossible to do +direct DMA to any address >16MB. This limitation is even true of some +EISA controllers (which are normally 32 bit) when they're configured to +emulate an ISA card, which they then do in *all* respects. This problem +is avoided entirely by IDE controllers (which do not use DMA), true EISA +controllers (like the UltraStor or Adaptec 1742A) and most VLB (local bus) +controllers. In the cases where it's necessary, the system will use +"bounce buffers" to to talk to the controller so that you can still use +more than 16Mb of memory without difficulty. + + +2.2. Ethernet cards + +SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, +WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT +based clones. + +Isolan AT 4141-0 (16 bit) + +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, and NE2100 ethernet interface. + +3Com 3C503 Etherlink II + +3Com 3C509 Ethernet cards + +Toshiba ethernet cards + +SMC Elite Ultra + + +2.3. Misc + +AST 4 port serial card using shared IRQ. + +ARNET 8 port serial card using shared IRQ. + +BOCA ATIO66 6 port serial card using shared IRQ. + +STB 4 port card using shared IRQ. + +Mitsumi (all models) CDROM interface and drive. + +Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound +and Roland MPU-401 sound cards. + +FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but +support is apparently close to materializing. Details will be posted +as the situation develops. + + +3. Obtaining FreeBSD. +--------------------- + +You may obtain FreeBSD in a variety of ways: + +1. FTP/Mail + +You can ftp FreeBSD and any or all of its optional packages from +`freebsd.cdrom.com' - the offical FreeBSD release site. + +For other locations that mirror the FreeBSD software see the file +MIRROR.SITES. Please ftp the distribution from the nearest site +to you netwise. + +If you do not have access to the internet and electronic mail is your +only recourse, then you may still fetch the files by sending mail to +`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message +to get more information on how to fetch files from freebsd.cdrom.com. +Note: This approach will end up sending many *tens of megabytes* +through the mail, and should only be employed as an absolute LAST +resort! + + +2. CDROM + +FreeBSD 1.1 may be ordered on CDROM from: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) + +Or via the internet from orders@cdrom.com. There current catalog can +be obtained via ftp as ftp.cdrom.com:/cdrom/catalog. + +Cost is $39.95. Shipping (per order not per disc) is $5 in the US, Canada, +or Mexico and $10.00 overseas. They accept Visa, Mastercard, American +Express, and ship COD to the United States. California residents please +add 8.25% sales tax. + +Should you be dissatisfied for any reason, the CD comes with an +unconditional return policy. + +Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD, +you need to contact the FreeBSD team for that. Please see section 4 for +more information. + + +It should be noted, lest you get the wrong impression that "FreeBSD" +is anything but, that almost no one in the "core team" makes money +from distributions or anything else connected with FreeBSD. We simply +provide this information as a public service for those wishing to get +their releases from somewhere other than the net (and the easier it +is for you to obtain our software, the happier we are). + + +4. Reporting problems, making suggestions, submitting code. +----------------------------------------------------------- + +Your suggestions, bug reports and contributions of code are always +valued - please do not hesitate to report any problems you may find +(preferably with a fix attached if you can!). + +The prefered method to submit bug reports from a machine with internet +mail connectivity is to use the sendbug command. Bug reports will be +dutifully filed by our faithful bugfiler program and you can be sure +that we'll do our best to respond to all reported bugs as soon as +possible. + +If, for some reason, you are unable to use the sendbug command to +submit a bug report, you can try to send it to: + + FreeBSD-bugs@freefall.cdrom.com + + +Otherwise, for any questions or suggestions, please send mail to: + + FreeBSD-questions@freefall.cdrom.com + +Additionally, being a volunteer effort, we are always happy to have +extra hands willing to help - there are already far more enhancements +to be done than we can ever manage to do by ourselves! To contact us +on technical matters, or with offers of help, you may send mail to: + + FreeBSD-hackers@freefall.cdrom.com + +Since these mailing lists can experience significant amounts of +traffic, if you've got slow or expensive mail access and you're +only interested in keeping up with significant FreeBSD events, you may +find it preferable to subscribe to: + + FreeBSD-announce@freefall.cdrom.com + + +All but the FreeBSD-bugs groups can be freely joined by anyone wishing to +do so. Send mail to MajorDomo@freefall.cdrom.com and include the keyword +`help' on a line by itself somewhere in the body of the message. This +will give you more information on joining the various lists, accessing +archives, etc. + + +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. It would be very difficult, if not +impossible, to enumerate everyone who's contributed to FreeBSD, but +nonetheless we shall try (in alphabetical order, of course). If your +name is not mentioned, please be assured that its omission is entirely +accidental. + + +The Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, for his extensive work with 386BSD. + +The FreeBSD "core" team: + + Andrew A. Chernov + John Dyson + David Greenman + Rodney W. Grimes + Jordan K. Hubbard + Scott Mace + Andrew Moore + Rich Murphey + Geoff Rehmet + Paul Richards + Andreas Schulz + Nate Williams + Garrett A. Wollman + + +Special mention to: + + Robert Bruce and Jack Velte of Walnut Creek CDROM, without + whose help (and continuing support) this release would never + have been possible. + + Dermot McDonnell for his donation of a Toshiba XM3401B CDROM + drive. + + The NetBSD group for their frequent assistance and commentary. + + Additional FreeBSD helpers and beta testers: + + Gary Browing Jon Cargille + J.T. Conklin Chris Demetriou + Julian Elischer Bruce Evans + Sean Eric Fagan Guy Helmer + Jeffrey Hsu Terry Lambert + Gary Moyer Jaye Mathisen + Curt Mayer L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Rick Weldon Terry Williams + Atsushi Murai + + And everyone at Montana State University for their initial support. + + +Thanks to everyone, especially those not mentioned, and we sincerely +hope you enjoy this release of FreeBSD! + + + The FreeBSD Core Team + +$Id: RELNOTES.FreeBSD,v 1.1.1.1 1996-09-24 17:45:49 jfieber Exp $ diff --git a/en/releases/1.1.5/ROSTER.FreeBSD b/en/releases/1.1.5/ROSTER.FreeBSD new file mode 100644 index 0000000000..9972cf4fee --- /dev/null +++ b/en/releases/1.1.5/ROSTER.FreeBSD @@ -0,0 +1,127 @@ +This file attempts to document just who is `responsible' for what in +the FreeBSD world. Since we're an all-volunteer group, the whole +concept of `responsibility' must, of course, be taken with a grain of +salt since the folks here may not always have time to deal with your +problem right away. With that in mind, you are encouraged to contact +these folks directly when your problem or suggestion clearly falls +into their area of responsibility. If your queries don't net any +positive results in, say, 48 hours, THEN you should try and contact +the group at large. In most cases, however, using these folks as +first-contacts will both cut down on our mail-overload and give you +faster service. + +Thank you! + + The FreeBSD Team + freebsd-hackers@freefall.cdrom.com + +--- + + +Legend: +------- +contrib = Contributed +doc = Documentation +lib = User-land library +misc = Misc user-land utility (contrib, other) +ports = Ported software in /usr/ports +prog = User-land program +share = Support data files +sys = Kernel and system code +tools = DOS support utilities + +Category Person Email address +=============================================================================== +contrib/xntpd Garrett Wollman wollman@lcs.mit.edu +doc/FAQ FAQ Team freebsd-faq@freefall.cdrom.com +lib/libF77 L. Jonas Olsson ljo@po.cwru.edu +lib/libc Garrett Wollman wollman@lcs.mit.edu +lib/libcrypt (non-US) Geoff Rehmet csgr@cs.ru.ac.za +lib/libcurses Andrew Chernov ache@astral.msk.su +lib/libkrb Garrett Wollman wollman@lcs.mit.edu +lib/libm Andrew Moore alm@netcom.com +lib/libpthread Chris Provenzano proven@mit.edu +lib/libskey Guido van Rooij guido@gvr.win.tue.nl +lib/libtelnet Garrett Wollman wollman@lcs.mit.edu +misc/addit Gary Clark II gclarkii@freefall.cdrom.com +misc/configit Gary Clark II gclarkii@freefall.cdrom.com +misc/gnats Andrew Moore alm@netcom.com +misc/manctl Geoff Rehmet csgr@cs.ru.ac.za +ports/{not below} Andrew Moore alm@freefall.cdrom.com +ports/aXe Jordan Hubbard jkh@freefall.cdrom.com +ports/archivers Scott Mace smace@freefall.cdrom.com +ports/bash Jordan Hubbard jkh@freefall.cdrom.com +ports/blt Jordan Hubbard jkh@freefall.cdrom.com +ports/cpm Joerg Wunsch joerg_wunsch@uriah.sax.de +ports/dgd Adam David adam@veda.is +ports/elm Scott Mace smace@freefall.cdrom.com +ports/emacs Jordan Hubbard jkh@freefall.cdrom.com +ports/exmh Jordan Hubbard jkh@freefall.cdrom.com +ports/ezd Jeffrey Hsu hsu@freefall.cdrom.com +ports/franz Jordan Hubbard jkh@freefall.cdrom.com +ports/fvwm Geoff Rehmet csgr@cs.ru.ac.za +ports/golddig Jeffrey Hsu hsu@freefall.cdrom.com +ports/ile Jordan Hubbard jkh@freefall.cdrom.com +ports/ispell Piero Serini piero@strider.st.dsi.unimi.it +ports/jpeg Scott Mace smace@freefall.cdrom.com +ports/kermit Scott Mace smace@freefall.cdrom.com +ports/ksh Sean Vickery seanv@cs.uq.edu.au +ports/kterm Satoshi Asami asami@cs.berkeley.edu +ports/lynx Serge V.Vakulenko vak@cronyx.msk.su +ports/mprof Jeffrey Hsu hsu@freefall.cdrom.com +ports/mtools Steven Wallace swallace@freefall.cdrom.com +ports/netaudio Jeffrey Hsu hsu@freefall.cdrom.com +ports/nethack Sean Vickery seanv@cs.uq.edu.au +ports/pcvt J"org Wunsch joerg_wunsch@uriah.sax.de +ports/piewm Satoshi Asami asami@cs.berkeley.edu +ports/pkg_install Jordan Hubbard jkh@freefall.cdrom.com +ports/popper Andreas Schulz ats@g386bsd.first.gmd.de +ports/point Jordan Hubbard jkh@freefall.cdrom.com +ports/sather Jeffrey Hsu hsu@freefall.cdrom.com +ports/schemetoc Jeffrey Hsu hsu@freefall.cdrom.com +ports/scm Jeffrey Hsu hsu@freefall.cdrom.com +ports/seahaven Jeffrey Hsu hsu@freefall.cdrom.com +ports/sml Jeffrey Hsu hsu@freefall.cdrom.com +ports/sup Jordan Hubbard jkh@freefall.cdrom.com +ports/tcl Jordan Hubbard jkh@freefall.cdrom.com +ports/tcl-dp Jordan Hubbard jkh@freefall.cdrom.com +ports/tclX Jordan Hubbard jkh@freefall.cdrom.com +ports/tcsh Scott Mace smace@freefall.cdrom.com +ports/tk Jordan Hubbard jkh@freefall.cdrom.com +ports/vile Jordan Hubbard jkh@freefall.cdrom.com +ports/vim Jordan Hubbard jkh@freefall.cdrom.com +ports/wine Jeffrey Hsu hsu@freefall.cdrom.com +ports/wu-ftpd Justin T. Gibbs gibbs@freefall.cdrom.com +ports/xcdplayer Steven Wallace swallace@freefall.cdrom.com +ports/xjewel Jeffrey Hsu hsu@freefall.cdrom.com +ports/xlock Scott Mace smace@freefall.cdrom.com +ports/xmine J"org Wunsch joerg_wunsch@uriah.sax.de +ports/xphoon Satoshi Asami asami@cs.berkeley.edu +ports/xv Scott Mace smace@freefall.cdrom.com +ports/ytalk Geoff Rehmet csgr@cs.ru.ac.za +ports/zircon Jordan Hubbard jkh@freefall.cdrom.com +ports/zsh Scott Mace smace@freefall.cdrom.com +prog/cc Poul-Henning Kamp phk@freefall.cdrom.com +prog/cc25 Poul-Henning Kamp phk@freefall.cdrom.com +prog/gdb Gary Jennejohn gj@pcs.dec.com +prog/man Jordan Hubbard jkh@freefall.cdrom.com +prog/telnet Garrett Wollman wollman@lcs.mit.edu +sys/fd J"org Wunsch joerg_wunsch@uriah.sax.de +sys/fd Serge V.Vakulenko vak@cronyx.msk.su +sys/i386 David Greenman davidg@root.com +sys/i386/isa/seagate Sean Vickery seanv@cs.uq.edu.au +sys/i386/isa/sound Steven Wallace swallace@freefall.cdrom.com +sys/i386/isa/bt742*.c Atsushi Murai amurai@spec.co.jp +sys/kern David Greenman davidg@root.com +sys/kern/ntp Garrett Wollman wollman@lcs.mit.edu +sys/lpt Geoff Rehmet csgr@cs.ru.ac.za +sys/net* David Greenman davidg@root.com +sys/netboot Martin Renters martin@innovus.com +sys/netinet Garrett Wollman wollman@lcs.mit.edu +sys/pcmcia Poul-Henning Kamp phk@freefall.cdrom.com +sys/scheduler John Dyson dyson@freefall.cdrom.com +sys/syscons So/ren Schmidt sos@freefall.cdrom.com +sys/vm David Greenman davidg@root.com +sys/vm John Dyson dyson@freefall.cdrom.com +sys/wt Serge V.Vakulenko vak@cronyx.msk.su +tools/booteasy Serge V.Vakulenko vak@cronyx.msk.su diff --git a/en/releases/1.1.5/SUPPORT.TXT b/en/releases/1.1.5/SUPPORT.TXT new file mode 100644 index 0000000000..8bf8a92c82 --- /dev/null +++ b/en/releases/1.1.5/SUPPORT.TXT @@ -0,0 +1,89 @@ + +Technical support for this product is NOT provided by Walnut Creek CDROM. + +You need to contact one of the following companies and/or people for +technical support. + +Accurate Automation Company +6005 S.E. Laurel Street +Milwaukie, OR 97222 +Telephone: +1-503-653-7376 +Email: rgrimes@agora.rain.com + +Accurate Automation provides support for FreeBSD including installation, +system configuration, hardware and software trouble shooting, and related +issues. Rates depend upon the type of work being done. Hours are from +10:00 am to 10:00pm PST. + + +Gary Clark II +GB Data Consulting +3801 Polk +Houston, Texas 77003 USA +Telephone: +1-713-587-1644 +Email: gclarkii@radon.gbdata.com + +GB Data Consulting provides support for FreeBSD including installation, usage +and system administration. We also provide classes, on-site service and +distribution sets on floppy. Please email info@radon.gbdata.com or call for +rates and information. + + +Cronyx Ltd. +Research Computer Center, +Moscow State University, +Moscow 199899, Russia +Phone: +7-095-939-5678 +Email: info@cronyx.msk.su + +Cronyx Ltd. provides support for FreeBSD including installation, +configuration, Relcom network connection via UUCP, dialup and leased +line IP. We also provide X Windows configuration and localization, +as well as additional packages installation. Distribution sets on +floppies and tape cartridges available. System software development +including drivers for non-standard equipment. + + +Jordan Hubbard +Timberline Associates (est 1978) +Dublin, Ireland [And soon Boston / San Francisco] +Support hours: 1000 - 2300 GMT +Tel #: 00353-1-332796 +Email: jkh@al.org + +Telephone (or Internet) and on-site consulting for FreeBSD in Ireland, +the United States, United Kingdom and most parts of Europe. Services include +installation, system configuration, networking and custom software +projects, graphical user interfaces a specialty (actively involved with +The X Window System since Version 9 and contributor to the X Consortium). +Reasonable and flexible rates comensurate with location and duration of +assignment. Internet assignments are welcomed, and generally billed at +lower rates. + + +Vector Systems Ltd, Julian H. Stacey. +Post: Holz Strasse 27d, D 80469, Munich (Muenchen), Germany (Deutschland). +Tel.: +49 89 268616 09:00-22:00 TZ=GMT+1 +Email: stacey@freefall.cdrom.com + +Custom designs & support using FreeBSD + X-Windows + FSF/GNU, + own Unix & DOS +C tools. Systems engineering, hardware interfacing, multi lingual systems +(European, Cyrillic, Chinese), communications, scientific, industrial real +time programming. Source Tapes: QIC 525M, 150M, 60M. +Deutsch: Man kann mir in Deutsch schreiben, (oder mich anrufen). +Francais: Je comprend Francais, mais je n'ecris pas des responses en Francais. + + +Sean Vickery +2/449 Milton Road +Auchenflower Qld 4066 +Australia +Telephone: +61 (0)7 870 5241 + Email: seanv@cs.uq.edu.au + +Sean offers support in most FreeBSD matters, including installation +and configuration. His rates are reasonable. As well as on-site +help, support is available over the phone and the net. + + +$Id: SUPPORT.TXT,v 1.1.1.1 1996-09-24 17:45:50 jfieber Exp $ diff --git a/en/releases/1.1.5/TODO-1.1.5 b/en/releases/1.1.5/TODO-1.1.5 new file mode 100644 index 0000000000..66d1777a13 --- /dev/null +++ b/en/releases/1.1.5/TODO-1.1.5 @@ -0,0 +1,38 @@ +This is my current TODO list for 1.1.5. Please feel free to add to +it, assuming that you've actually got some confidence that you or +someone else will be able to actually get to whatever it is (or it's +so critical that you don't think 1.1.5 could/should be released +without it). + +Also, please bear in mind the following milestones we have to hit: + +June 5th Feature Freeze (bug fixes and cleanup work only). +June 16th Code Freeze +June 20th Roll binaries - begin initial testing +June 23rd Announce availability of 1.1.5. + +(*) = Task is completed +(@) = Task is abandoned + +Task Urgency Who +------------------------------------------------------------------------------- +Floppy driver fixes Low * Joerg Wunsch +Sound driver (GUS/Multicast/cleanup) Medium Steven W/Andrew C. +Curses library problems Medium * Steven W. +SIO driver - reported problems High * Andrew C/Bruce E/??? +Syscons integration / new features High * Soren Schmidt/Jordan +Update FT driver Medium * Javier R/Steven G. +Update gdb High * Paul +Make pcfs less dangerous Low @ ??? +Bruce's disklabel and bad144 fixes Medium * Andrew C. +Misc NetBSD drivers for weird devices Low @ Geoff +Multicast Support Medium * Jordan +Bounce Buffer fixes High * John/David +VM panics and assorted lossage High * John/David +Secure Key support Low * Guido +Install script enhancements Medium * Andrew M/Jordan +Fsck/umount cooperation with dirty bit Low @ Paul R. +PCFS data corruption with cp Medium * Steven W./ATS +PCFS extended DOS partition support Low @ ??? +ISOFS over NSF fix Medium/High * ??? +Libcompat Low * Joerg Wunsch diff --git a/en/releases/1.1/CONTRIB.386BSD b/en/releases/1.1/CONTRIB.386BSD new file mode 100644 index 0000000000..a99b527c48 --- /dev/null +++ b/en/releases/1.1/CONTRIB.386BSD @@ -0,0 +1,196 @@ + + + + + + + + 386BSD Release 0.1 + Contributor List + + Lynne Greer Jolitz + William F. Jolitz + + +_H_a_r_d_w_a_r_e _a_n_d _M_o_n_e_t_a_r_y _C_o_n_t_r_i_b_u_t_o_r_s + +Many people and firms have provided hardware and/or money to +try and keep this unfunded project going despite a recession +and hard times -- usually by digging into their own pockets. +Each of these contributors gave, not only because they +believed that the continuation of 386BSD is vital to the +health of the research, educational, and development commun- +ities, but also because they realize that an individual can +and does make a difference! + +Without the help of the people listed here, this release +would simply not have been possible. We would especially +like to thank Thos Sumner, whose loan of a 486/50 SCSI PC +made development go more rapidly. The rest of the 386BSD +user community should make special note of all these people +and firms and commend them for their generosity and +foresight. + +We hope that their leadership and vision will serve as shin- +ing examples to the entire 386BSD user community, and serve +to encourage others to actively participate in 386BSD. + + Jan van den Bosch + Compaq Computer Corporation + Cyrix Corporation + Dixon Dick + Steven P. Donegan + Jon Erickson + Eric J. Haug + Bob McGhee + Jesus Monroy Jr. + Andrew Moore + Rich Murphey + Mark Ng + Kenji Okamoto + John Plocher + Mark R. Riordan + John B. Scalia + Steve Sizemore + Thos Sumner + David E. Tweten + + + + + +386BSD CONTRIB LIST 1 July 1992 + + + + + + + + + + +_S_o_f_t_w_a_r_e _C_o_n_t_r_i_b_u_t_o_r_s + +The following people have contributed key software programs, +modules and fixes, including novel work and ports of popular +public domain user programs. Some of this software was +directly contributed to us, while other items were made +available to all users via the network. Occasionally, +several people came up with a variety of approaches for a +single item. In this instance, we tried to choose the one +which we felt would best serve the rest of the 386BSD user +base for this release. However, the creativity and persever- +ance of all the software contributors trying to make 386BSD +better for the entire 386BSD user community was consider- +able. Each individual effort is worthy of pride. + +We wish to personally thank all of these people, as they +have helped make 386BSD Release 0.1 a reality. We hope that +these contributors and all the rest of the 386BSD user com- +munity will continue to actively participate to make future +releases even better! + + James Van Artsdalen + Scott Burris + Randall Dean + Chris Demetriou + Mark Eichin + Bruce Evans + Steve Ferguson + Jeffrey Goh + David Greenman + Amancio Hasty Jr + John W. Hatley + Eric J. Haug + Tom Ivar Helbekkmo + John D. Irwin + Peter Klingebiel + Paul Kranenburg + Daniel Lanciani + Karl Lehenbauer + Lee M. J. McLoughlin + Andrew J. Michael + Jesus Monroy Jr. + Daniel A. Muntz + Richard Murphey + Glen Overby + Brad Parker + Herb Pereyl + Ken Raeburn + Paul Richards + Guido van Rooij + Peng-Toh Sim + Wolfgang Solfrank + Dave Stanhope + + +386BSD CONTRIB LIST 2 July 1992 + + + + + + + + + + + Mark Tinguely + Linus Torvalds + Richard Tobin + Rob Warnock + Christian Wiedmann + Pace Willisson + Joerg Wunsch + + And all of the other 386BSD Software Contributors. + + +_S_u_p_p_o_r_t _a_n_d _A_d_v_i_c_e _C_o_n_t_r_i_b_u_t_o_r_s + +Many people have continually encouraged us over the course +of these releases, and provided us with technical advice and +guidance. These people have also spent considerable time and +energy getting this software out to the rest of the 386BSD +community. While it is impossible for us to list everyone +who has been supportive of 386BSD, we wish to personally +thank some of the people who have been of special assistance +to us directly over the course of getting 386BSD out the +door. + + Bruce Blakely + Dave Campbell + Free Software Foundation + Paul Fromberg + Tom Genereaux + John Gilmore + Dave Harris + Jim Joyce + Dan Kionka + Dory Leifer + Per Lindqvist + Marshall Midden + Rich Morin + Silicon Valley Computer Society + John Sokol + Thos Sumner + Karen Trocki + Rob Warnock + + and a special thanks to: + John Erickson, Tami Zemel, Ray Valdez, Monica Berg, Michael Floyd + and everyone else at Dr. Dobbs Journal. + Juergen Fey, Rainer Huttenloher, Gerd Oskar Bausewein + and everyone else at UNIX Magazin. + + And all of the 386BSD User Community. + + + + + +386BSD CONTRIB LIST 3 July 1992 + + + diff --git a/en/releases/1.1/CONTRIB.FreeBSD b/en/releases/1.1/CONTRIB.FreeBSD new file mode 100644 index 0000000000..9fd13fdcec --- /dev/null +++ b/en/releases/1.1/CONTRIB.FreeBSD @@ -0,0 +1,185 @@ + FreeBSD 1.1 + Contributor List + + + +Derived Software Contributors: + +This software was derived from William F. Jolitz's 386BSD release 0.1. +Please see the file CONTRIB.386BSD for the list of contributors from +386BSD. + +Included in this release are the patches from the patch kit version +0.2.4. The names of contributors from the patch kit are listed below. + +There are portions of NetBSD that has been intergraged into FreeBSD +as well. We would like to thank all the contributors to NetBSD for +their work. + + +Hardware Contributors: + +A special thanks to Robert Bruce and Jack Velte of Walnut Creek CDROM +for providing a 486/DX2-66 EISA/VL system that is being used for the +development work. It would have been impossible to do this release +with out their support. + +Dermot McDonnell for his donation of a Toshiba XM3401B CDROM +drive. + + +FreeBSD core: + +Andrew A. Chernov +Andrew Moore +Andreas Schulz +John Dyson +Geoff Rehmet +David Greenman +Jordan K. Hubbard +Nate Williams +Paul Richards +Rich Murphey +Rodney W. Grimes +Scott Mace +Garrett A. Wollman + + +Additional FreeBSD Contributors: + +Adam Glass +Andrew Herbert +Bob Wilcox +Bruce Evans +Charles Hannum +Chris G. Demetriou +Chris Torek +Christoph Robitschko +Curt Mayer +Dave Burgess +Dave Rivers +David Dawes +Frank Maclachlan +Gary A. Browning +Gary Clark II +Guido van Rooij +Havard Eidnes +Holger Veit +Ishii Masahiro, R. Kym Horsell +J.T. Conklin +James Clark +James da Silva et al +Jim Wilson +Joerg Wunsch +Julian Elischer +Julian Stacey > +Keith Bostic +Marc Frajola +Mark Tinguely +Martin Birgmeier +Paul Kranenburg +Paul Mackerras +Poul-Henning Kamp +Rob Shady +Sascha Wildner +Sean Eric Fagan +Serge V. Vakulenko +Steven Wallace +Søren Schmidt +Terry Lee +Theo Deraadt +Yuval Yarom + + +Patch kit patch contributors: + +Adam Glass +Adrian Hall +Andrew A. Chernov +Andrew Herbert +Andrew Moore +Andy Valencia +Arne Henrik Juul +Bakul Shah +Barry Lustig +Bob Wilcox +Branko Lankester +Brett Lymn +Bruce Evans +Charles Hannum +Chris G. Demetriou +Chris Torek +Christoph Robitschko +Daniel Poirot +Dave Burgess +Dave Rivers +David Dawes +David Greenman +Eric J. Haug +Felix Gaehtgens +Frank Maclachlan +Gary A. Browning +Geoff Rehmet +Goran Hammarback +Guido van Rooij +Guy Harris +Havard Eidnes +Herb Peyerl +Ishii Masahiro, R. Kym Horsell +J.T. Conklin +Jagane D Sundar < jagane@netcom.com > +James Clark +James Jegers +James W. Dolter +James da Silva et al +Jay Fenlason +Jim Wilson +Joerg Lohse +Joerg Wunsch +John Dyson - +John Woods +Jordan K. Hubbard +Julian Elischer +Julian Stacey > +Karl Lehenbauer +Keith Bostic +Ken Hughes +Kent Talarico +Kevin Lahey +Marc Frajola +Mark Tinguely +Martin Renters +Michael Galassi +Mike Durkin +Nate Williams +Nick Handel +Pace Willisson +Paul Kranenburg +Paul Mackerras +Paul Popelka +Peter da Silva +Phil Sutherland +Poul-Henning Kamp +Ralf Friedl +Rich Murphey +Rick Macklem +Robert D. Thrush +Rodney W. Grimes +Rog Egge +Sascha Wildner +Scott Burris +Scott Reynolds +Sean Eric Fagan +Simon J Gerraty +Stephen McKay +Terry Lambert +Terry Lee +Warren Toomey +Wiljo Heinen +William Jolitz +Wolfgang Solfrank +Wolfgang Stanglmeier +Yuval Yarom + +$Id: CONTRIB.FreeBSD,v 1.1.1.1 1996-09-24 17:45:50 jfieber Exp $ diff --git a/en/releases/1.1/COPYRIGHT.386BSD b/en/releases/1.1/COPYRIGHT.386BSD new file mode 100644 index 0000000000..c53cb8865b --- /dev/null +++ b/en/releases/1.1/COPYRIGHT.386BSD @@ -0,0 +1,131 @@ + + + + + + + + 386BSD Release 0.1 + Copyright + + + /* + * Copyright (c) 1989, 1990, 1991, 1992 William F. Jolitz, TeleMuse + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. All advertising materials mentioning features or use of this software + * must display the following acknowledgement: + * This software is a component of "386BSD" developed by + * William F. Jolitz, TeleMuse. + * 4. Neither the name of the developer nor the name "386BSD" + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * 386BSD WAS DEVELOPED BY WILLIAM F. JOLITZ. + * 386BSD IS INTENDED FOR RESEARCH AND EDUCATIONAL PURPOSES. + * THIS SOFTWARE SHOULD NOT BE CONSIDERED TO BE A COMMERCIAL PRODUCT. + * THE DEVELOPER URGES THAT USERS WHO REQUIRE A COMMERCIAL PRODUCT + * NOT MAKE USE OF THIS WORK. + * + * FOR USERS WHO WISH TO UNDERSTAND THE 386BSD SYSTEM DEVELOPED + * BY WILLIAM F. JOLITZ, WE RECOMMEND THE USER STUDY WRITTEN + * REFERENCES SUCH AS THE "PORTING UNIX TO THE 386" SERIES + * (BEGINNING JANUARY 1991 "DR. DOBBS JOURNAL", USA AND BEGINNING + * JUNE 1991 "UNIX MAGAZIN", GERMANY) BY WILLIAM F. JOLITZ AND + * LYNNE GREER JOLITZ, AS WELL AS OTHER BOOKS ON UNIX AND THE + * ON-LINE 386BSD USER MANUAL BEFORE USE. A BOOK DISCUSSING THE INTERNALS + * OF 386BSD ENTITLED "386BSD FROM THE INSIDE OUT" WILL BE AVAILABLE LATE 1992. + * + * THIS SOFTWARE IS PROVIDED BY THE DEVELOPER ``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 DEVELOPER 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 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + */ + + + 386BSD Copyright 1 July 1992 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 386BSD Copyright 2 July 1992 + + + + diff --git a/en/releases/1.1/COPYRIGHT.FreeBSD b/en/releases/1.1/COPYRIGHT.FreeBSD new file mode 100644 index 0000000000..7c0c19c4e1 --- /dev/null +++ b/en/releases/1.1/COPYRIGHT.FreeBSD @@ -0,0 +1,121 @@ +This software contains software developed by the University of +California, Berkeley, and its contributors; by the Free Software +Foundation; by the University of Illinois; by the Massachusetts +Institute of Technology; by the University of Vermont and State +Agricultural College; by Carnegie Mellon University; and by a large +number of contributors, whose names are listed in the notices below. + +Portions of this software are subject to one or more of the following +copyright notices. Please see the individual files for the terms and +conditions. + + +Copyright (C) 1980, 1983, 1986, 1988, 1990, 1991, Regents of the + University of California +Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, Free + Software Foundation, Inc. +Copyright (C) 1976, Board of Trustees of the University of Illinois +Copyright (C) 1980, 1981, Ken Harrenstien +Copyright (C) 1982, 1988, 1989, Walter Tichy +Copyright (C) 1983, 1986, 1992, 1993, Eric P. Allman +Copyright (C) 1983, Kenneth L. Greer +Copyright (C) 1984, 1985, 1986, 1987, 1992, Sun Microsystems, Inc. +Copyright (C) 1984, 1987, Stephen L. Moshier +Copyright (C) 1984, 1989, 1990, Bob Corbett and Richard Stallman +Copyright (C) 1984, University of British Columbia +Copyright (C) 1985, 1986, Wayne A. Christopher +Copyright (C) 1985, 1987, 1988, 1989, Adobe Systems, Inc. +Copyright (C) 1985, Stichting Mathematisch Centrum +Copyright (C) 1986, 1987, 1989, 1990, 1991, 1992, Ian F. Darwin +Copyright (C) 1986, 1987, 1989, Frame Technology, Inc. +Copyright (C) 1986, 1987, 1992, Daniel D. Lanciani +Copyright (C) 1986, 1987, Ed James +Copyright (C) 1986, Breslow +Copyright (C) 1986, Gary S. Brown +Copyright (C) 1986, Larry Wall +Copyright (C) 1986, Noah Morgan +Copyright (C) 1986, Stephen Satchell +Copyright (C) 1987, 1988, 1989, 1990, 1991, 1992, Carnegie Mellon University +Copyright (C) 1987, 1988, 1989, Sony Corp. +Copyright (C) 1987, 1988, John Stanback +Copyright (C) 1987, 1988, Ronald S. Karr and Landon Curt Noll +Copyright (C) 1987, 1989, 1990, 1991, Massachusetts Institute of Technology +Copyright (C) 1987, David C. Elliott. +Copyright (C) 1987, IBM Corporation +Copyright (C) 1987, Stuart Cracraft +Copyright (C) 1987, United States Army +Copyright (C) 1988, 1989, 1990, 1993, 1994, Paul A. Vixie +Copyright (C) 1988, 1989, Adam de Boor +Copyright (C) 1988, 1990, University of Utah +Copyright (C) 1988, Julian Onions +Copyright (C) 1988, Mark Nudleman +Copyright (C) 1988, Rayan S. Zachariassen +Copyright (C) 1989, 1990, 1991, 1992, 1993, Frank Kardel +Copyright (C) 1989, 1990, 1991, 1992, 1993, William S. Jolitz +Copyright (C) 1989, 1990, 1991, 1992, Brian Berliner +Copyright (C) 1989, Berkeley Softworks +Copyright (C) 1989, Dale Schumacher +Copyright (C) 1989, Dave Taylor +Copyright (C) 1989, Kenneth Almquist +Copyright (C) 1989, Matthew Self +Copyright (C) 1989, Robert V. Baron +Copyright (C) 1990, 1991, 1992, 1993, AT&T Bell Laboratories and Bellcore +Copyright (C) 1990, 1991, John W. Eaton +Copyright (C) 1990, 1991, Paul Eggert +Copyright (C) 1990, 1993, Andrew Moore +Copyright (C) 1990, John Robert LoVerso +Copyright (C) 1990, Open Software Foundation, Inc. +Copyright (C) 1990, RSA Data Security, Inc. +Copyright (C) 1991, 1992, 1993, 1994, Chris Provenzano +Copyright (C) 1991, 1992, 1993, Ian Lance Taylor +Copyright (C) 1991, 1992, Per Bothner +Copyright (C) 1991, 1992, Per Cederqvist +Copyright (C) 1991, Gregory M. Christy +Copyright (C) 1991, Inge Wallin +Copyright (C) 1991, Joseph Friedman +Copyright (C) 1992, 1993, 1994, David L. Mills +Copyright (C) 1992, 1993, Christopher G. Demetriou +Copyright (C) 1992, 1993, Garrett A. Wollman +Copyright (C) 1992, 1993, HD Associates +Copyright (C) 1992, 1993, Holger Veit +Copyright (C) 1992, 1993, Jean-Loup Gailly +Copyright (C) 1992, 1993, 1994 Joerg Wunsch +Copyright (C) 1992, 1993, John Brezak +Copyright (C) 1992, 1993, Motorola, Inc. +Copyright (C) 1992, 1993, Soeren Schmidt +Copyright (C) 1992, 1993, Theo de Raadt +Copyright (C) 1992, 1993, University of Vermont and State Agricultural College +Copyright (C) 1992, Cygnus Support +Copyright (C) 1992, Diomidis Spinellis +Copyright (C) 1992, Henry Spencer +Copyright (C) 1992, Jeff Polk +Copyright (C) 1992, Terrence R. Lambert +Copyright (C) 1992, University of Guelph +Copyright (C) 1993, 1994, Andrew A. Chernov +Copyright (C) 1993, 1994, David Greenman +Copyright (C) 1993, 1994, John S. Dyson +Copyright (C) 1993, Adam Glass +Copyright (C) 1993, Atsushi Murai +Copyright (C) 1993, Brian Moore +Copyright (C) 1993, Daniel Boulet and RTMX Inc. +Copyright (C) 1993, David Muir Sharnoff +Copyright (C) 1993, David Parsons +Copyright (C) 1993, Gary Clark II +Copyright (C) 1993, Hannu Savolainen +Copyright (C) 1993, Herb Peyerl +Copyright (C) 1993, Herve Schauer Consultants +Copyright (C) 1993, Julian Elischer +Copyright (C) 1993, Julian Stacey +Copyright (C) 1993, K. J. Dryllerakis +Copyright (C) 1993, Martin Birgmeier +Copyright (C) 1993, Paul Kranenburg +Copyright (C) 1993, Paul Richards +Copyright (C) 1993, Thomas Koenig +Copyright (C) 1993, Winning Strategies, Inc. +Copyright (C) 1994, Christoph M. Robitschko +Copyright (C) 1994, University of Maryland +Copyright (C) 1993, 1994, jc@irbs.UUCP (John Capo), + vak@zebub.msk.su (Serge Vakulenko), + ache@astral.msk.su (Andrew A. Chernov) + +$Id: COPYRIGHT.FreeBSD,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/en/releases/1.1/MIRROR.SITES b/en/releases/1.1/MIRROR.SITES new file mode 100644 index 0000000000..57d9a907a7 --- /dev/null +++ b/en/releases/1.1/MIRROR.SITES @@ -0,0 +1,59 @@ + +The FreeBSD software is being mirrored at the following locations: + +Country Site/Directory/Maintainer +======= ========================================================= + +Australia minnie.cs.adfa.oz.au:/BSD/FreeBSD-1.1-RELEASE + + +Australia ftp.physics.su.oz.au:/FreeBSD + David Dawes + +Australia ftp.une.edu.au:/pub/FreeBSD + Gordon Smith + +Austria ftp.tu-graz.ac.at:/pub/FreeBSD + + +Finland ftp.funet.fi:/pub/unix/FreeBSD + + +France ftp.ibp.fr:/pub/FreeBSD + + +Germany ftp.informatik.tu-muenchen.de:/pub/comp/os/bsd/FreeBSD + + +Germany ftp.uni-duisburg.de:/pub/unix/FreeBSD + + +Germany gil.physik.rwth-aachen.de:/pub/FreeBSD + + +Hong Kong ftp.cs.cuhk.hk:/pub/FreeBSD + + +Israel orgchem.weizmann.ac.il:/pub/FreeBSD + + +Netherlands ftp.nl.net:/pub/os/FreeBSD + + +Russia ftp.kiae.su:/FreeBSD + + +UK src.doc.ic.ac.uk:/packages/FreeBSD + + +USA gatekeeper.dec.com:/pub/BSD/FreeBSD + + +USA freebsd.uml.edu:/FreeBSD + + +USA wuarchive.wustl.edu:/systems/unix/FreeBSD + + + +$Id: MIRROR.SITES,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/en/releases/1.1/Makefile b/en/releases/1.1/Makefile new file mode 100644 index 0000000000..39794b4e32 --- /dev/null +++ b/en/releases/1.1/Makefile @@ -0,0 +1,4 @@ +DATA= CONTRIB.386BSD CONTRIB.FreeBSD COPYRIGHT.386BSD COPYRIGHT.FreeBSD +DATA+= MIRROR.SITES PERSONAL.ACKS RELNOTES.FreeBSD SUPPORT.TXT + +.include "../../web.mk" diff --git a/en/releases/1.1/PERSONAL.ACKS b/en/releases/1.1/PERSONAL.ACKS new file mode 100644 index 0000000000..9388fecd37 --- /dev/null +++ b/en/releases/1.1/PERSONAL.ACKS @@ -0,0 +1,17 @@ +The following contributors would like to make these personal +acknowledgements (in no particular order): + +Garrett Wollman would like to thank Gary Barbour and Steve Ackerman of +Utah; Tim Raymond, Jim White, and Jim Ertle of UVM; Malcolm Carlock at +UNR; and John Wroclawski of MIT. + +Nate Williams would like to thank Jaye Mathisen and the entire Computer +Science department of Montana State University for their help, hardware +and encouragement. + +Jordan Hubbard would like to thank IEUNET for bringing the INTERNET to +Ireland, thus making his participation possible at all (albeit expensive) +and his Mom, who would probably be pleased if only she understood any of +this. Hi Mom. + +$Id: PERSONAL.ACKS,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/en/releases/1.1/RELNOTES.FreeBSD b/en/releases/1.1/RELNOTES.FreeBSD new file mode 100644 index 0000000000..46b5c322e4 --- /dev/null +++ b/en/releases/1.1/RELNOTES.FreeBSD @@ -0,0 +1,303 @@ + RELEASE NOTES + FreeBSD + Release 1.1 + +1. Technical overview +--------------------- + +FreeBSD is a freely available, full source 4.3 (+4.4 enhancements) BSD +release for Intel i386/i486 (or compatable) based PC's. It is based +heavily on Bill Jolitz's 386BSD 0.1, with additions from "the patchkit", +NetBSD, CSRG, and the Free Software Foundation. + +Many hundreds of bugs from the 386BSD 0.1 distribution were fixed, +and many out-of-date pieces of software were upgraded to their current +releases in the GAMMA distribution. This 1.1 distribution fixes +many of the first-run problems our BETA and GAMMA users reported back +to us. + +Additionally, many packages such as XFree86 2.1, xview 3.2, elm, nntp, +mh, InterViews and dozens of other miscellaneous utilities have been ported +and are now available as add-ons. See then next section of this document +for more details. + +For a list of contributors, please see the files "CONTRIB.FreeBSD" and +"CONTRIB.386BSD", which should be bundled with your distribution. + +The core of FreeBSD does not contain DES code which would inhibit its +being exported outside the United States. There is an add-on package +to the core distribution, for use only in the United States, that +contains the programs that normally use DES. The auxilliary packages +provided separately can be used by anyone. A freely (from outside the U.S.) +exportable European distribution of DES for our non U.S. users also exists +and is described in the FreeBSD FAQ. + + +2. Supported Configurations +--------------------------- + +FreeBSD currently runs on a wide variety of ISA and EISA bus based +PC's, ranging from 386sx to 486 class machines (though the 386sx is +not recommended). Support for generic IDE or ESDI drive configurations, +various SCSI controller, network and serial cards is also provided. + +Following is a list of all currently known disk controllers and +ethernet cards known to work with FreeBSD. Other configurations may +very well work, and we have simply not received any indication of +this. + + +2.1. Disk Controllers + +WD1003 (any generic MFM/RLL) +WD1007 (any generic IDE/ESDI) + +Adaptec 154x series ISA SCSI controller (as long as you have less than +16MB of main memory). + +Adaptec 174x series EISA SCSI controller in standard and enhanced mode. + +[Note that Buslogic was formerly known as "Bustec"] +Buslogic 545S. +Buslogic 445S VLB SCSI controller +Buslogic 742A and 747. +Please see special notes in /usr/src/KNOWNBUGS (filed under bt742a.c) for +details concerning possible buggy firmware and undocumented switch settings +that may be necessary for proper operation of your controller. + +DTC 3290 EISA SCSI controller in 1542 emulation mode. + +Ultra Store 14F and 34F. + +Seagate ST01/02 SCSI controllers. + +Future Domain 8xx/950 series SCSI controllers. + +With all supported SCSI controllers, full support is provided for +SCSI-I & SCSI-II peripherals, including Disks, tape drives (including +DAT) and CD ROM drives. Note: This and the mcd driver (Mitsumi CDROM +inteface card) is the only way a CD ROM drive may be currently +attached to a FreeBSD system; we do not support SoundBlaster CDROM +interface, or other "mini SCSI" adapters. + +Some controllers have limitations with the way they deal with >16MB of memory, +due to the fact that the ISA bus only has a DMA address space of 24 bits. +If you do your arithmetic, you'll see that this makes it impossible to do +direct DMA to any address >16MB. This limitation is even true of some +EISA controllers (which are normally 32 bit) when they're configured to +emulate an ISA card, which they then do in *all* respects. This problem +is avoided entirely by IDE controllers (which do not use DMA), true EISA +controllers (like the UltraStor or Adaptec 1742A) and most VLB (local bus) +controllers. In these cases, the system will use "bounce buffers" to +to talk to the controller, and is generally the default. + + +2.2. Ethernet cards + +SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, +WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT +based clones. + +Isolan AT 4141-0 (16 bit) + +Isolink 4110 (8 bit) + +Novell NE1000, NE2000, and NE2100 ethernet interface. + +3Com 3C503 Etherlink II + +3Com 3C509 Ethernet cards + +Toshiba ethernet cards + +SMC Elite Ultra + + +2.3. Misc + +AST 4 port serial card using shared IRQ. + +ARNET 8 port serial card using shared IRQ. + +BOCA ATIO66 6 port serial card using shared IRQ. + +STB 4 port card using shared IRQ. + +Mitsumi (all models) CDROM interface and drive. + +Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound +and Roland MPU-401 sound cards. + +FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but +support is apparently close to materializing. Details will be posted +as they develop. + + +3. Obtaining FreeBSD. +--------------------- + +You may obtain FreeBSD in a variety of ways: + +1. FTP/Mail + +You can ftp FreeBSD and any or all of its optional packages from +`freebsd.cdrom.com' - the offical FreeBSD release site. + +For other locations that mirror the FreeBSD software see the file +MIRROR.SITES. Please ftp the distribution from the nearest site +to you netwise. + +If you do not have access to the internet and electronic mail is your +only recourse, then you may still fetch the files by sending mail to +`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message +to get more information on how to fetch files from freebsd.cdrom.com. +Note: This approach will end up sending many *tens of megabytes* +through the mail, and should only be employed as an absolute LAST +resort! + + +2. CDROM + +FreeBSD may be ordered on CDROM from: + + Walnut Creek CDROM + 4041 Pike Lane, Suite D + Concord CA 94520 + 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) + +Or via the internet from orders@cdrom.com. There current catalog can +be obtained via ftp as ftp.cdrom.com:/cdrom/catalog. + +Cost is $39.95. Shipping (per order not per disc) is $5 in the US, Canada, +or Mexico and $10.00 overseas. They accept Visa, Mastercard, American +Express, and ship COD to the United States. California residents please +add 8.25% sales tax. + +Should you be dissatisfied for any reason, the CD comes with an +unconditional return policy. + +Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD, +you need to contact the FreeBSD team for that. Please see section 4 for +more information. + + +It should be noted, lest you get the wrong impression that "FreeBSD" +is anything but, that almost no one in the "core team" makes money +from distributions or anything else connected with FreeBSD. We simply +provide this information as a public service for those wishing to get +their releases from somewhere other than the net (and the easier it +is for you to obtain our software, the happier we are). + + +4. Reporting problems, making suggestions, submitting code. +----------------------------------------------------------- + +Your suggestions, bug reports and contributions of code are always +valued - please do not hesitate to report any problems you may find +(preferably with a fix attached if you can!). + +The prefered method to submit bug reports from a machine with internet +mail connectivity is to use the sendbug command. Bug reports will be +dutifully filed by our faithful bugfiler program and you can be sure +that we'll do our best to respond to all reported bugs as soon as +possible. + +If, for some reason, you are unable to use the sendbug command to +submit a bug report, you can try to send it to: + + FreeBSD-bugs@freefall.cdrom.com + + +Otherwise, for any questions or suggestions, please send mail to: + + FreeBSD-questions@freefall.cdrom.com + +Additionally, being a volunteer effort, we are always happy to have +extra hands willing to help - there are already far more enhancements +to be done than we can ever manage to do by ourselves! To contact us +on technical matters, or with offers of help, you may send mail to: + + FreeBSD-hackers@freefall.cdrom.com + +Since these mailing lists can experience significant amounts of +traffic, if you've got slow or expensive mail access and you're +only interested in keeping up with significant FreeBSD events, you may +find it preferable to subscribe to: + + FreeBSD-announce@freefall.cdrom.com + + +All but the FreeBSD-bugs groups can be freely joined by anyone wishing to +do so. Send mail to MajorDomo@freefall.cdrom.com and include the keyword +`help' on a line by itself somewhere in the body of the message. This +will give you more information on joining the various lists, accessing +archives, etc. + + +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. It would be very difficult, if not +impossible, to enumerate everyone who's contributed to FreeBSD, but +nonetheless we shall try (in alphabetical order, of course). If your +name is not mentioned, please be assured that its omission is entirely +accidental. + + +The Computer Systems Research Group (CSRG), U.C. Berkeley. + +Bill Jolitz, for his extensive work with 386BSD. + +The FreeBSD "core" group: + + Andrew A. Chernov + John Dyson + David Greenman + Rodney W. Grimes + Jordan K. Hubbard + Scott Mace + Andrew Moore + Rich Murphey + Geoff Rehmet + Paul Richards + Andreas Schulz + Nate Williams + Garrett A. Wollman + + +Special mention to: + + Robert Bruce and Jack Velte of Walnut Creek CDROM, without + whose help (and continuing support) this release would never + have been possible. + + Dermot McDonnell for his donation of a Toshiba XM3401B CDROM + drive. + + The NetBSD group for their frequent assistance and commentary. + + Additional FreeBSD helpers and beta testers: + + Gary Browing Jon Cargille + J.T. Conklin Chris Demetriou + Julian Elischer Bruce Evans + Sean Eric Fagan Guy Helmer + Jeffrey Hsu Terry Lambert + Gary Moyer Jaye Mathisen + Curt Mayer L Jonas Olsson + Chris Provenzano Dave Rivers + Guido van Rooij Steven Wallace + Rick Weldon Terry Williams + + And everyone at Montana State University for their initial support. + + +Thanks to everyone, especially those not mentioned, and we sincerely +hope you enjoy this release of FreeBSD! + + + The FreeBSD Core Group + +$Id: RELNOTES.FreeBSD,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/en/releases/1.1/SUPPORT.TXT b/en/releases/1.1/SUPPORT.TXT new file mode 100644 index 0000000000..9d01d1e95d --- /dev/null +++ b/en/releases/1.1/SUPPORT.TXT @@ -0,0 +1,89 @@ + +Technical support for this product is NOT provided by Walnut Creek CDROM. + +You need to contact one of the following companies and/or people for +technical support. + +Accurate Automation Company +6005 S.E. Laurel Street +Milwaukie, OR 97222 +Telephone: +1-503-653-7376 +Email: rgrimes@agora.rain.com + +Accurate Automation provides support for FreeBSD including installation, +system configuration, hardware and software trouble shooting, and related +issues. Rates depend upon the type of work being done. Hours are from +10:00 am to 10:00pm PST. + + +Gary Clark II +GB Data Consulting +3801 Polk +Houston, Texas 77003 USA +Telephone: +1-713-587-1644 +Email: gclarkii@radon.gbdata.com + +GB Data Consulting provides support for FreeBSD including installation, usage +and system administration. We also provide classes, on-site service and +distribution sets on floppy. Please email info@radon.gbdata.com or call for +rates and information. + + +Cronyx Ltd. +Research Computer Center, +Moscow State University, +Moscow 199899, Russia +Phone: +7-095-939-5678 +Email: info@cronyx.msk.su + +Cronyx Ltd. provides support for FreeBSD including installation, +configuration, Relcom network connection via UUCP, dialup and leased +line IP. We also provide X Windows configuration and localization, +as well as additional packages installation. Distribution sets on +floppies and tape cartridges available. System software development +including drivers for non-standard equipment. + + +Jordan Hubbard +Timberline Associates (est 1978) +Dublin, Ireland [And soon Boston / San Francisco] +Support hours: 1000 - 2300 GMT +Tel #: 00353-1-332796 +Email: jkh@al.org + +Telephone (or Internet) and on-site consulting for FreeBSD in Ireland, +the United States, United Kingdom and most parts of Europe. Services include +installation, system configuration, networking and custom software +projects, graphical user interfaces a specialty (actively involved with +The X Window System since Version 9 and contributor to the X Consortium). +Reasonable and flexible rates comensurate with location and duration of +assignment. Internet assignments are welcomed, and generally billed at +lower rates. + + +Vector Systems Ltd, Julian H. Stacey. +Post: Holz Strasse 27d, D 80469, Munich (Muenchen), Germany (Deutschland). +Tel.: +49 89 268616 09:00-22:00 TZ=GMT+1 +Email: stacey@freefall.cdrom.com + +Custom designs & support using FreeBSD + X-Windows + FSF/GNU, + own Unix & DOS +C tools. Systems engineering, hardware interfacing, multi lingual systems +(European, Cyrillic, Chinese), communications, scientific, industrial real +time programming. Source Tapes: QIC 525M, 150M, 60M. +Deutsch: Man kann mir in Deutsch schreiben, (oder mich anrufen). +Francais: Je comprend Francais, mais je n'ecris pas des responses en Francais. + + +Sean Vickery +2/449 Milton Road +Auchenflower Qld 4066 +Australia +Telephone: +61 (0)7 870 5241 + Email: seanv@cs.uq.edu.au + +Sean offers support in most FreeBSD matters, including installation +and configuration. His rates are reasonable. As well as on-site +help, support is available over the phone and the net. + + +$Id: SUPPORT.TXT,v 1.1.1.1 1996-09-24 17:45:51 jfieber Exp $ diff --git a/en/releases/2.0.5A/Makefile b/en/releases/2.0.5A/Makefile new file mode 100644 index 0000000000..517e40e9d3 --- /dev/null +++ b/en/releases/2.0.5A/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml notes.sgml + +.include "../../web.mk" diff --git a/en/releases/2.0.5A/announce.sgml b/en/releases/2.0.5A/announce.sgml new file mode 100644 index 0000000000..b3adb4b50a --- /dev/null +++ b/en/releases/2.0.5A/announce.sgml @@ -0,0 +1,158 @@ + + + + %includes; +]> + +&header; + +

    + Date: Tue, 30 May 1995 01:44:26 -0700
    + From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
    + To: announce@FreeBSD.org
    + Subject: Announcing FreeBSD 2.0.5 ALPHA! +

    + +

    It gives me great pleasure to announce the release of FreeBSD 2.0.5-ALPHA! + +

    2.0.5A represents a significant improvement over FreeBSD 2.0R and is our +release-candidate for 2.0.5R later on this week. We're doing a short ALPHA +release in order to shake out any glaring bugs before rolling 2.0.5R and +moving on to 2.1R, which is the bigger goal. If you're looking for 2.1R, +then THIS ISN'T IT. It's an interim release aimed at people who want +something newer and better than 2.0R to run and don't feel like waiting +for late July, which is when 2.1R is scheduled to go into BETA test. + +

    That said, I think most people will enjoy 2.0.5 quite a bit, and while +it's not up to the "full release quality" we hope to have for 2.1R, it's +certainly more stable and generally nicer to use than 2.0R! + +

    2.0.5A is currently available on the following sites: + +

    +
    Primary: +
    ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-ALPHA + +
    Secondary:
    ftp://freefall.cdrom.com/pub/FreeBSD/2.0.5-ALPHA +
    + +

    And should be up on the following MIRROR sites shortly: + +

    +
    Australia
    ftp://ftp.physics.usyd.edu.au/FreeBSD + <dawes@xfree86.org> + +
    Finland
    ftp://nic.funet.fi/pub/unix/FreeBSD + <ftp@nic.funet.fi> + +
    France
    ftp://ftp.ibp.fr/pub/FreeBSD + <Remy.Card@ibp.fr> + +
    Germany
    ftp://ftp.fb9dv.uni-duisburg.de/pub/unix/FreeBSD + <ftp@ftp.fb9dv.uni-duisburg.de> + +
    Germany
    ftp://gil.physik.rwth-aachen.de/pub/FreeBSD + <kuku@gil.physik.rwth-aachen.de> + +
    Germany
    ftp://ftp.uni-paderborn.de/freebsd + <ftp@uni-paderborn.de> + +
    Israel
    ftp://orgchem.weizmann.ac.il/pub/FreeBSD + <serg@klara.weizmann.ac.il> + +
    Hong Kong
    ftp://ftp.hk.super.net/pub/FreeBSD + <ftp-admin@HK.Super.NET> + +
    Korea
    ftp://ftp.cau.ac.kr/pub/FreeBSD + <ftpadm@ftp.cau.ac.kr> + +
    Netherlands
    ftp://ftp.nl.net/pub/os/FreeBSD + <archive@nl.net> + +
    Russia
    ftp://ftp.kiae.su/FreeBSD + <ftp@ftp.kiae.su> + +
    Sweden
    ftp://ftp.luth.se/pub/FreeBSD + <ragge@ludd.luth.se> + +
    Taiwan
    ftp://netbsd.csie.nctu.edu.tw/pub/FreeBSD + <ftp@netbsd.csie.nctu.edu.tw> + +
    Thailand
    ftp://ftp.nectec.or.th/pub/FreeBSD + <ftpadmin@ftp.nectec.or.th> + +
    USA
    ftp://gatekeeper.dec.com/pub/BSD/FreeBSD + <hubbard@gatekeeper.dec.com> + +
    USA
    ftp://ftp.cybernetics.net/pub/FreeBSD + <michael@Cybernetics.NET> + +
    USA
    ftp://ftp.neosoft.com/systems/FreeBSD + <smace@NeoSoft.COM> + +
    USA
    ftp://kryten.atinc.com/pub/FreeBSD + <jmb@kryten.atinc.com> + +
    USA
    ftp://ftp.dataplex.net/pub/FreeBSD + <rkw@dataplex.net> + +
    Japan
    ftp://ftp.tokyonet.ad.jp/pub/FreeBSD + <ftpadmin@TokyoNet.AD.JP> + +
    Japan
    ftp://ftp.tut.ac.jp/FreeBSD + Ashida Hiroyuki <ashida@ftp.tut.ac.jp> + +
    Japan
    ftp://ftp.sra.co.jp/pub/os/FreeBSD + <ftp-admin@sra.co.jp> + +
    Japan
    ftp://ftp.ee.uec.ac.jp/pub/os/mirror/ftp.freebsd.org + <ftp-admin@ftp.ee.uec.ac.jp> + +
    Japan
    ftp://ftp.mei.co.jp/free/PC-UNIX/FreeBSD + TANIGUCHI Syuuhei <tanig@isl.mei.co.jp> + +
    Japan
    ftp://ftp.waseda.ac.jp/pub/FreeBSD + <ftp-admin@waseda.ac.jp> + +
    Japan
    ftp://ftp.pu-toyama.ac.jp/pub/FreeBSD + Yoshihiko USUI <usui@pu-toyama.ac.jp> + +
    Japan
    ftp://ftpsv1.u-aizu.ac.jp/pub/os/FreeBSD + <ftp-admin@u-aizu.ac.jp> + +
    UK
    ftp://src.doc.ic.ac.uk/packages/unix/FreeBSD + <wizards@doc.ic.ac.uk> + +
    UK
    ftp://unix.hensa.ac.uk/pub/walnut.creek/FreeBSD + <archive-admin@unix.hensa.ac.uk> + +
    UK
    ftp://ftp.demon.co.uk/pub/BSD/FreeBSD + <uploads@demon.net> +
    + +
    + +

    NOTE: If you're installing directly from ftp you can simply grab the +boot.flp image from the floppies directory, write it to a floppy +and go from there. There is no need to grab any of the other files; +the installation will perform this step automatically! + +

    Please also read the various README and RELNOTES files in the release for +more information on 2.0.5 - no sense in repeating it all here if most +of you are simply going to download and read it anyway! + +

    I'd like to also extend special thanks to Poul-Henning Kamp & Gary Palmer +for exerting an especially large amount of effort this time in helping +me get the new installation together. Thanks also to Rod Grimes for +playing "source tree pit bull" when I needed him to, thus keeping the +number of headaches I had to suffer in pulling in various last-minute +changes to an absolute minimum. Thanks, guys! This couldn't have +been done without you! + +

    Jordan
    + for the FreeBSD Project. + +&footer; + + diff --git a/en/releases/2.0.5A/notes.sgml b/en/releases/2.0.5A/notes.sgml new file mode 100644 index 0000000000..5970a6ea5f --- /dev/null +++ b/en/releases/2.0.5A/notes.sgml @@ -0,0 +1,738 @@ + + + + %includes; +]> + +&header; + +

    +                                 RELEASE NOTES
+                                    FreeBSD
+                                 Release 2.0.5
+
+1. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our release of FreeBSD 2.0 some 8 months ago, the performance,
+feature set, and stability of FreeBSD has improved dramatically.  The
+largest change is a revamped VM system with a merged VM/file buffer
+cache that not only increases performance, but reduces FreeBSD's
+memory footprint, making a 4MB configuration a more acceptible
+minimum.  Other enhancements include full NIS client and server
+support, transaction TCP support, dial-on-demand PPP, an improved SCSI
+subsystem, early ISDN support, support for FDDI and Fast Ethernet
+(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
+narrow) and many hundreds of bug fixes.
+
+We've also taken the comments and suggestions of many of our users to
+heart and have attempted to provide what we hope is a more sane and
+easily understood installation process.  Your feedback on this
+(constantly evolving) process is especially welcome!
+
+In addition to the base distributions, FreeBSD offers a new ported
+software collection with some 270 commonly sought-after programs.  The
+list of ports ranges from http (WWW) servers, to games, languages,
+editors and almost everything in between.  The entire ports collection
+requires only 10MB of storage, all ports being expressed as "deltas"
+to their original sources.  This makes it much easier for us to update
+ports, and greatly reduces the disk space demands made by the older
+1.0 ports collection.  To compile a port, you simply change to the
+directory of the program you wish to install, type make and let the
+system do the rest.  The full original distribution for each port you
+build is retrieved dynamically off of CDROM or a local ftp site, so
+you need only enough disk space to build the ports you want.  Each
+port is also provided as a pre-compiled "package" which can be
+installed with a simple command (pkg_add) by those who do not wish to
+compile their own ports from source.  See the file:
+        /usr/share/FAQ/Text/ports.FAQ
+for a more complete description of the ports collection.
+
+
+Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD
+has changed almost entirely.  A new port from the Berkeley 4.4 code
+base was done, which brought the legal status of the system out of the
+shadows with the blessing of Novell (the new owners of USL and UNIX).  The
+port to 4.4 has also brought in a host of new features, filesystems
+and enhanced driver support.  With our new unencumbered code base, we
+have every reason to hope that we'll be able to release quality
+operating systems without further legal encumbrance for some time to
+come!
+
+FreeBSD 2.0.5 represents the culmination of 2 years of work and many
+thousands of man hours put in by an international development team.
+We hope you enjoy it!
+
+For a list of contributors and a general project description, please see
+the file "CONTRIB.FreeBSD" which should be bundled with your binary
+distribution.
+
+Also see the "REGISTER.FreeBSD" file for information on registering
+with the "Free BSD user counter".   This counter is for ALL freely
+available variants of BSD, not just FreeBSD, and we urge you to register
+yourself with it.
+
+The core of FreeBSD does not contain DES code which would inhibit its
+being exported outside the United States.  There is an add-on package
+to the core distribution, for use only in the United States, that
+contains the programs that normally use DES.  The auxiliary packages
+provided separately can be used by anyone.   A freely (from outside the
+U.S.) exportable European distribution of DES for our non-U.S. users also
+exists and is described in the FreeBSD FAQ.
+
+If password security for FreeBSD is all you need, and you have no
+requirement for copying encrypted passwords from different hosts
+(Suns, DEC machines, etc) into FreeBSD password entries, then
+FreeBSD's MD5 based security may be all you require!  We feel that our
+default security model is more than a match for DES, and without any
+messy export issues to deal with.  If you're outside (or even inside)
+the U.S., give it a try!
+
+
+1.1 What's new in 2.0.5?
+----------------------
+
+The following features were added or substantially improved between
+the release of 2.0 and this 2.0.5 release.  In order to facilitate
+better communication, the person, or persons, responsible for each
+enhancement is noted.  Any questions regarding the new functionality
+should be directed to them first.
+
+KERNEL:
+
+Merged VM-File Buffer Cache
+---------------------------
+A merged VM/buffer cache design greatly enhances overall system
+performance and makes it possible to do a number of more optimal
+memory allocation strategies that were not possible before.
+
+Owner:                  David Greenman (davidg@FreeBSD.org) and
+                        John Dyson (dyson@implode.root.com)
+
+
+Network PCB hash optimization
+-----------------------------
+For systems with a great number of active TCP connections (WEB and ftp
+servers, for example), this greatly speeds up the lookup time required
+to match an incoming packet up to its associated connection.
+
+Owner:                  David Greenman (davidg@FreeBSD.org)
+
+
+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 
+management of the cache in various other ways while we were at it.
+
+Owner:			Poul-Henning Kamp (phk@FreeBSD.org)
+			David GreenMan (davidg@FreeBSD.org)
+
+
+Less restrictive swap-spaces
+----------------------------
+The need to compile the names of the swap devices into the kernel has been
+removed.  Now swapon will accept any block devices, up to the maximum
+number of swap devices configured in the kernel.
+
+Owner:			Poul-Henning Kamp (phk@FreeBSD.org)
+			David GreenMan (davidg@FreeBSD.org)
+
+
+Hard Wired SCSI Devices
+-----------------------
+Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers
+to SCSI devices as they were probed, allowing a SCSI device failure to
+possibly change unit number assignment and prevent filesystems on
+still functioning disks from mounting.  Hard wiring allows static
+allocation of unit numbers (and hence device names) to scsi devices
+based on SCSI ID and bus.  SCSI configuration occurs in the kernel
+config file.  Samples of the configuration syntax can be found in the
+scsi(4) man page or the LINT kernel config file.
+
+Owner:                  Peter Dufault (dufault@hda.com)
+Sources involved:       sys/scsi/* usr.sbin/config/*
+
+
+Slice Support
+-------------
+FreeBSD now supports a "slice" abstraction which makes it more
+completely interoperable with other operating system partitions.  This
+support will allow FreeBSD to inhabit DOS extended partitions.
+
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+Sources involved:       sys/disklabel.h sys/diskslice.h sys/dkbad.h
+                        kern/subr_diskslice.c kern/subr_dkbad.c
+                        i386/isa/diskslice_machdep.c
+                        i386/isa/wd.c scsi/sd.c dev/vn/vn.c
+
+
+Support for Ontrack Disk Manager Version 6.0
+--------------------------------------------
+Support has been added for disks which use Ontrack Disk Manager.  The
+fdisk program does NOT know about it however, so make all changes
+using the install program on the boot.flp or the Ontrack Disk Manager
+tool under DOS.
+
+Owner:			Poul-Henning Kamp (phk@FreeBSD.org)
+
+
+Bad144 is back and working
+--------------------------
+Bad144 works again, though the semantics are slightly different than
+before in that the bad-spots are kept relative to the slice rather
+than absolute on the disk.
+
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+			Poul-Henning Kamp (phk@FreeBSD.org)
+
+
+NEW DEVICE SUPPORT:
+
+                        SCSI and CDROM Devices
+
+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 with the Karoke variable speed
+playback.
+
+Owner:                  Frank Durda IV   bsdmail@nemesis.lonestar.org
+Sources involved:       isa/matcd
+
+
+Adaptec 2742/2842/2940 SCSI driver
+-----------------------------
+The original 274x/284x driver has evolved considerably since the 2.0
+release.  We now offer full support for the 2940 series as well as the
+Wide models of these cards.  The arbitration bug (as well as many
+others) that caused the driver problems with fast devices has been
+corrected and there is even experimental tagged queuing support
+(kernel option "AHC_TAGENABLE").  John Aycock has also released the
+sequencer code under a "Berkeley style" copyright making the driver
+entirely clean of the GPL.
+
+Owner:                  Justin Gibbs (gibbs@FreeBSD.org)
+Sources involved:       isa/aic7770.c pci/aic7870.c i386/scsi/*
+                        sys/dev/aic7xxx/*
+
+
+NCR5380/NCR53400 SCSI ("ProAudio Spectrum") driver
+--------------------------------------------------
+Owner:                  core
+Submitted by:           Serge Vakulenko (vak@cronyx.ru)
+Sources involved:       isa/ncr5380.c
+
+
+Sony CDROM driver
+-----------------
+Owner:                  core
+Submitted by:           Mikael Hybsch (micke@dynas.se)
+Sources involved:       isa/scd.c
+
+
+                        Serial Devices
+
+SDL Communications Riscom/8 Serial Board Driver
+-----------------------------------------------
+Owner:                  Andrey Chernov (ache@FreeBSD.org)
+Sources involved:       isa/rc.c isa/rcreg.h
+
+
+Cyclades Cyclom-y Serial Board Driver
+-------------------------------------
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+Submitted by:           Andrew Werple (andrew@werple.apana.org.au) and
+                        Heikki Suonsivu (hsu@cs.hut.fi)
+Obtained from:          NetBSD
+Sources involved:       isa/cy.c
+
+
+Cronyx/Sigma sync/async serial driver
+-------------------------------------
+Owner:                  core
+Submitted by:           Serge Vakulenko
+Sources involved:       isa/cronyx.c            
+
+
+
+                        Networking
+
+Diskless booting
+----------------
+Diskless booting in 2.0.5 is much improved.  The boot-program is in
+src/sys/i386/boot/netboot, and can be run from an MSDOS system or
+burned into an EPROM.  Local swapping is also possible.  WD, SMC, 3COM
+and Novell ethernet cards are currently supported.
+
+
+DEC DC21140 Fast Ethernet driver
+--------------------------------
+This driver supports any of the numerous NICs using the DC21140 chipset 
+including the 100Mb DEC DE-500-XA and SMC 9332.
+
+Owner:                  core
+Submitted by:           Matt Thomas (thomas@lkg.dec.com)
+Sources involved:       pci/if_de.c pci/dc21040.h
+
+
+DEC FDDI (DEFPA/DEFEA) driver
+-----------------------------
+Owner:                  core
+Submitted by:           Matt Thomas (thomas@lkg.dec.com)
+Sources involved:       pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h
+
+
+3Com 3c505 (Etherlink/+) NIC driver
+-----------------------------------
+Owner:                  core
+Submitted by:           Dean Huxley (dean@fsa.ca)
+Obtained from:          NetBSD
+Sources involved:       isa/if_eg.c
+
+
+Fujitsu MB86960A family of NICs driver
+-------------------------------------
+Owner:                  core
+Submitted by:           M.S. (seki@sysrap.cs.fujitsu.co.jp)
+Sources involved:       isa/if_fe.c
+
+
+Intel EtherExpress driver
+-------------------------
+Owner:                  Rodney W. Grimes (rgrimes@FreeBSD.org)
+Sources involved:       isa/if_ix.c isa/if_ixreg.h
+
+
+3Com 3c589 driver
+-----------------
+Owner:                  core
+Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
+                        Seiji Murata (seiji@mt.cs.keio.ac.jp) and
+                        Noriyuki Takahashi (hor@aecl.ntt.jp)
+Sources involved:       isa/if_zp.c
+
+
+IBM Credit Card Adapter driver
+------------------------------
+Owner:                  core
+Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
+Sources involved:       isa/pcic.c isa/pcic.h
+
+
+EDSS1 and 1TR6 ISDN interface driver
+------------------------------------
+Owner:                  core
+Submitted by:           Dietmar Friede (dfriede@drnhh.neuhaus.de) and
+                        Juergen Krause (jkr@saarlink.de)
+Sources involved:       gnu/isdn/*
+
+
+                        Miscellaneous Drivers
+
+Joystick driver
+---------------
+Owner:                  Jean-Marc Zucconi (jmz@FreeBSD.org)
+Sources involved:       isa/joy.c
+
+
+National Instruments "LabPC" driver
+-----------------------------------
+Owner:                  Peter Dufault (dufault@hda.com)
+Sources involved:       isa/labpc.c
+
+
+WD7000 driver
+-------------
+Owner:                  Olof Johansson (offe@ludd.luth.se)
+
+
+Pcvt Console driver
+-------------------
+Owner:                  Joerg Wunsch (joerg@FreeBSD.org)
+Submitted by:           Hellmuth Michaelis (hm@altona.hamburg.com)
+Sources involved:       isa/pcvt/*
+
+
+BSD-audio emulator for VAT driver
+---------------------------------
+Owner:                  Amancio Hasty (ahasty@FreeBSD.org) and
+                        Paul Traina (pst@FreeBSD.org)
+Sources involved:       isa/sound/vat_audio.c isa/sound/vat_audioio.h
+
+
+National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver
+--------------------------------------------------------
+Owner:                  core
+Submitted by:           Fred Cawthorne (fcawth@delphi.umd.edu)
+Sources involved:       isa/gpib.c isa/gpib.h isa/gpibreg.h
+
+
+Genius GS-4500 hand scanner driver
+----------------------------------
+Owner:                  core
+Submitted by:           Gunther Schadow (gusw@fub46.zedat.fu-berlin.de)
+Sources involved:       isa/gsc.c isa/gscreg.h
+
+
+CORTEX-I Frame Grabber
+----------------------
+Owner:                  core
+Submitted by:           Paul S. LaFollette, Jr. (
+Sources involved:       isa/ctx.c isa/ctxreg.h
+
+
+Video Spigot video capture card
+-------------------------------
+Owner:                  Jim Lowe
+
+
+
+1.2 Experimental features
+---------------------------------------------
+
+The unionfs and LFS file systems are known to be severely broken in
+2.0.5.  This is in part due to old bugs that we haven't had time to
+resolve yet and the need to update these file systems to deal with the
+new VM system.  We hope to address these issues in a later release of
+FreeBSD.
+
+FreeBSD now supports running iBCS2 compatible binaries (currently SCO
+UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).  The iBCS2
+emulator is in its early stages, but it is functional, we haven't been
+able to do exhaustive testing (lack of commercial apps), but almost
+all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10
+for SCO. Further testing is nessesary to complete this project. There
+is also work under way for ELF & XOUT loaders, and most of the svr4
+syscall wrappers have been written.
+
+Owner:                  Soren Schmidt (sos) & Sean Eric Fagan (sef)
+Sources involved:       sys/i386/ibcs2/* + misc kernel changes.
+=======
+
+
+2. Supported Configurations
+---------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+Following is a list of all disk controllers and ethernet cards currently
+known to work with FreeBSD.  Other configurations may very well work, and
+we have simply not received any indication of this.
+
+
+2.1. Disk Controllers
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+WD7000
+IDE
+ATA
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards
+as they have no on-board BIOS, which is necessary for mapping
+the boot device into the system BIOS I/O vectors.
+They're perfectly usable for external tapes, CDROMs, etc,
+however.  The same goes for any other AIC-6x60 based card
+without a boot ROM.  Some systems DO have a boot ROM, which
+is generally indicated by some sort of message when the system
+is first powered up or reset.  Check your system/board documentation
+for more details.
+
+[Note that Buslogic was formerly known as "Bustec"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+Buslogic 956c PCI SCSI controller
+
+NCR 53C810 and 53C825 PCI SCSI controller.
+NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+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 
+(matcd) Matsushita/Panasonic (Creative) proprietary interface
+(scd)   Sony proprietary interface
+
+Note: CD-Drives with IDE interfaces are not supported at this time.
+
+Some controllers have limitations with the way they deal with >16MB of
+memory, due to the fact that the ISA bus only has a DMA address space
+of 24 bits.  If you do your arithmetic, you'll see that this makes it
+impossible to do direct DMA to any address >16MB.  This limitation is
+even true of some EISA controllers (which are normally 32 bit) when
+they're configured to emulate an ISA card, which they then do in *all*
+respects.  This problem is avoided entirely by IDE controllers (which
+do not use DMA), true EISA controllers (like the UltraStor, Adaptec
+1742A or Adaptec 2742) and most VLB (local bus) controllers.  In the
+cases where it's necessary, the system will use "bounce buffers" to
+talk to the controller so that you can still use more than 16Mb of
+memory without difficulty.
+
+
+2.2. Ethernet cards
+
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21140 based NICs (SMC???? DE???)
+DEC FDDI (DEFPA/DEFEA) NICs
+
+Fujitsu MB86960A family of NICs
+
+Intel EtherExpress
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+
+2.3. Misc
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+Mitsumi (all models) CDROM interface and drive.
+
+SDL Communications Riscom/8 Serial Board.
+
+Soundblaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
+
+Matsushita/Panasonic (Creative SoundBlaster) CDROM interface and drive.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
+support is apparently close to materializing.  Details will be posted
+as the situation develops.
+
+
+3. Obtaining FreeBSD.
+---------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+1. FTP/Mail
+
+You can ftp FreeBSD and any or all of its optional packages from
+`ftp.freebsd.org' - the offical FreeBSD release site.
+
+For other locations that mirror the FreeBSD software see the file
+MIRROR.SITES.  Please ftp the distribution from the nearest site
+to you netwise.
+
+If you do not have access to the internet and electronic mail is your
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
+to get more information on how to fetch files from freebsd.cdrom.com.
+Note: This approach will end up sending many *tens of megabytes*
+through the mail, and should only be employed as an absolute LAST
+resort!
+
+
+2. CDROM
+
+FreeBSD 2.0.5 may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
+
+Or via the internet from orders@cdrom.com or http://www.cdrom.com.
+Their current catalog can be obtained via ftp as:
+        ftp://ftp.cdrom.com/cdrom/catalog.
+
+Cost is $39.95.  Shipping (per order not per disc) is $5 in the US,
+Canada, or Mexico and $10.00 overseas.  They accept Visa, Mastercard,
+American Express, and ship COD within the United States.  California
+residents please add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+
+Reporting problems, making suggestions, submitting code.
+-----------------------------------------------------------
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached if you can!).
+
+The preferred method to submit bug reports from a machine with
+internet mail connectivity is to use the send-pr command.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.
+
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                questions@FreeBSD.org
+
+Additionally, being a volunteer effort, we are always happy to have
+extra hands willing to help - there are already far more enhancements
+to be done than we can ever manage to do by ourselves!  To contact us
+on technical matters, or with offers of help, you may send mail to:
+
+                hackers@FreeBSD.org
+
+Since these mailing lists can experience significant amounts of
+traffic, if you have slow or expensive mail access and you are
+only interested in keeping up with significant FreeBSD events, you may
+find it preferable to subscribe to:
+
+                announce@FreeBSD.org
+
+
+All but the freebsd-bugs groups 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
+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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If your
+name is not mentioned, please be assured that its omission is entirely
+accidental.
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his initial work with 386BSD.
+
+The FreeBSD Core Team
+(in alphabetical order by first name):
+
+        Andreas Schulz <ats@FreeBSD.org>
+        Andrey A. Chernov <ache@FreeBSD.org>
+        Bruce Evans <bde@FreeBSD.org>
+        David Greenman <davidg@FreeBSD.org>
+        Garrett A. Wollman <wollman@FreeBSD.org>
+        Gary Palmer <gpalmer@FreeBSD.org>
+        Geoff Rehmet <csgr@FreeBSD.org>
+        Jack Vogel <jackv@FreeBSD.org>
+        John Dyson <dyson@FreeBSD.org>
+        Jordan K. Hubbard <jkh@FreeBSD.org>
+        Justin Gibbs <gibbs@FreeBSD.org>
+        Paul Richards <paul@FreeBSD.org>
+        Poul-Henning Kamp <phk@FreeBSD.org>
+        Rich Murphey <rich@FreeBSD.org>
+        Rodney W. Grimes <rgrimes@FreeBSD.org>
+        Satoshi Asami <asami@FreeBSD.org>
+        Søren Schmidt <sos@FreeBSD.org>
+
+Special mention to:
+
+        Walnut Creek CDROM, without whose help (and continuing support)
+        this release would never have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        Additional FreeBSD helpers and beta testers:
+
+        J.T. Conklin                            Julian Elischer
+        Frank Durda IV                          Peter Dufault
+        Sean Eric Fagan                         Jeffrey Hsu
+        Terry Lambert                           L Jonas Olsson
+        Chris Provenzano                        Dave Rivers
+        Guido van Rooij                         Steven Wallace
+        Atsushi Murai                           Scott Mace
+        Nate Williams
+
+        And everyone at Montana State University for their initial support.
+
+
+Jordan would also like to give special mention to Poul-Henning Kamp
+and Gary Palmer, both of whom put in long hours helping him to
+construct the new installation utility.  Poul, being a proud new
+father, was especially pressed for time yet somehow managed to put in
+significant amount of effort anyway and this release could not have
+happened without him.  Thank you both!
+
+Thanks also to everyone else who helped, especially those not
+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 
+
    + +&footer; + + diff --git a/en/releases/2.0.5R/Makefile b/en/releases/2.0.5R/Makefile new file mode 100644 index 0000000000..517e40e9d3 --- /dev/null +++ b/en/releases/2.0.5R/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml notes.sgml + +.include "../../web.mk" diff --git a/en/releases/2.0.5R/announce.sgml b/en/releases/2.0.5R/announce.sgml new file mode 100644 index 0000000000..c4f06a3015 --- /dev/null +++ b/en/releases/2.0.5R/announce.sgml @@ -0,0 +1,112 @@ + + + + %includes; +]> + +&header; + +

    + Date: Sat, 10 Jun 1995 13:01:12 -0700
    + From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
    + To: announce@freefall.cdrom.com, hackers@freefall.cdrom.com
    + Subject: Announcing FreeBSD 2.0.5 RELEASE! + +

    It is my usual pleasure (and, to a small degree, relief! + :) to announce the release of FreeBSD 2.0.5R - the final + release in the 2.0.5 series. + +

    This release provides both what I hope will be an exciting + glimpse of some of the new technologies and directions we + have planned for 2.1R and a stable and much + easier-to-install alternative to 2.0R. + +

    Highlights of this release are: + +

      +
    • Multi-lingual documentation files. +
    • Completely menu driven installation. +
    • More installation media types. +
    • Support for a much larger range of PC hardware. +
    • Easy mounting of DOS partitions and CD devices + mounted automatically. +
    • "Canned" installation types for easy installs. +
    • Easy post-configuration menu +
    + +

    And many other new features and bug fixes. + +

    The ports and packages collection has also been bundled + with 2.0.5R to prevent synchronization errors. While this + does result in a larger overall distribution, it at least + ensures more consistent results when installing ports and + packages. + +

    More information on the release may be found in the + RELNOTES and README files, so I'll simply leave you all to + see for yourself! + +

    The usual locations: + +

    + +

    As well as the usual mirrors, once they pick it up. + +

    It is also available on CD from Walnut Creek CDROM, the + project's principle sponsors. Please see the release notes + for ordering information. + +

    Any feedback should be sent to hackers@freebsd.org. + I will be leaving the country shortly (about 3 hours :) and + will try to read my email as often as possible, but for + quicker replies please send to the mailing list. + +

    Thank you! + +

    Jordan + +

    + +

    Date: Mon, 12 Jun 1995 00:33:07 -0700
    + From: Gary Palmer <gpalmer@westhill.cdrom.com>
    + To: announce@FreeBSD.ORGD
    + Subject: 2.0.5-RELEASE update + +

    Yes, you have guessed it. As a result of the recent + feedback we have had about the origional 2.0.5-RELEASE, we + have gone poking and found a couple of bugs on the + origional boot.flp image. There is now a + /pub/FreeBSD/2.0.5-RELEASE/UPDATES directory on ftp.cdrom.com + and freefall.cdrom.com + with a version of boot.flp which will fix the following + problems: + +

      +
    • The kernel was too big to boot on 4Mb machines. + +
    • It was possible to specify the filesystem mount points + in such a way that the program would mount the filesystem + before the parent filesystem was mounted (e.g. it would + mount /usr/local and then /usr) +
    + +

    As the CDROM has not gone to replication yet, this updated + floppy image will be appearing on the CDROM. + +

    Sorry to all those who had problems with the first boot + floppy set - I will personally nail Jordan to his chair and + nail the chair to the floor in front of his computer the + next time we roll a release! + +

    Gary + +&footer; + + diff --git a/en/releases/2.0.5R/notes.sgml b/en/releases/2.0.5R/notes.sgml new file mode 100644 index 0000000000..d70b6514f7 --- /dev/null +++ b/en/releases/2.0.5R/notes.sgml @@ -0,0 +1,760 @@ + + + + %includes; +]> + +&header; + +

    +                                 RELEASE NOTES
+                                    FreeBSD
+                                 Release 2.0.5
+
+1. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our release of FreeBSD 2.0 some 8 months ago, the performance,
+feature set, and stability of FreeBSD has improved dramatically.  The
+largest change is a revamped VM system with a merged VM/file buffer
+cache that not only increases performance, but reduces FreeBSD's
+memory footprint, making a 4MB configuration a more acceptable
+minimum.  Other enhancements include full NIS client and server
+support, transaction TCP support, dial-on-demand PPP, an improved SCSI
+subsystem, early ISDN support, support for FDDI and Fast Ethernet
+(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
+narrow) and many hundreds of bug fixes.
+
+We've also taken the comments and suggestions of many of our users to
+heart and have attempted to provide what we hope is a more sane and
+easily understood installation process.  Your feedback on this
+(constantly evolving) process is especially welcome!
+
+In addition to the base distributions, FreeBSD offers a new ported
+software collection with some 270 commonly sought-after programs.  The
+list of ports ranges from http (WWW) servers, to games, languages,
+editors and almost everything in between.  The entire ports collection
+requires only 10MB of storage, all ports being expressed as "deltas"
+to their original sources.  This makes it much easier for us to update
+ports, and greatly reduces the disk space demands made by the older
+1.0 ports collection.  To compile a port, you simply change to the
+directory of the program you wish to install, type make and let the
+system do the rest.  The full original distribution for each port you
+build is retrieved dynamically off of CDROM or a local ftp site, so
+you need only enough disk space to build the ports you want.  (Almost)
+every port is also provided as a pre-compiled "package" which can be
+installed with a simple command (pkg_add) by those who do not wish to
+compile their own ports from source.  See the file:
+        /usr/share/FAQ/Text/ports.FAQ
+for a more complete description of the ports collection.
+
+
+Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD
+has changed almost entirely.  A new port from the Berkeley 4.4 code
+base was done, which brought the legal status of the system out of the
+shadows with the blessing of Novell (the new owners of USL and UNIX).  The
+port to 4.4 has also brought in a host of new features, filesystems
+and enhanced driver support.  With our new unencumbered code base, we
+have every reason to hope that we'll be able to release quality
+operating systems without further legal encumbrance for some time to
+come!
+
+FreeBSD 2.0.5 represents the culmination of 2 years of work and many
+thousands of man hours put in by an international development team.
+We hope you enjoy it!
+
+A number of additional documents which you may find very helpful in
+the process of installing and using FreeBSD may also be found in
+the "FAQ" directory, either under /usr/share/FAQ on an installed
+system or at the top level of the CDROM or FTP distribution from
+where you're reading this file.  Please consult FAQ/Text/ROADMAP
+for a brief description of the resources provided by the FAQ directory.
+
+For a list of contributors and a general project description, please see
+the file "CONTRIB.FreeBSD" which should be bundled with your binary
+distribution.
+
+Also see the "REGISTER.FreeBSD" file for information on registering
+with the "Free BSD user counter".   This counter is for ALL freely
+available variants of BSD, not just FreeBSD, and we urge you to register
+yourself with it.
+
+The core of FreeBSD does not contain DES code which would inhibit its
+being exported outside the United States.  There is an add-on package
+to the core distribution, for use only in the United States, that
+contains the programs that normally use DES.  The auxiliary packages
+provided separately can be used by anyone.   A freely (from outside the
+U.S.) exportable European distribution of DES for our non-U.S. users also
+exists and is described in the FreeBSD FAQ.
+
+If password security for FreeBSD is all you need, and you have no
+requirement for copying encrypted passwords from different hosts
+(Suns, DEC machines, etc) into FreeBSD password entries, then
+FreeBSD's MD5 based security may be all you require!  We feel that our
+default security model is more than a match for DES, and without any
+messy export issues to deal with.  If you're outside (or even inside)
+the U.S., give it a try!
+
+
+1.1 What's new in 2.0.5?
+------------------------
+
+The following features were added or substantially improved between
+the release of 2.0 and this 2.0.5 release.  In order to facilitate
+better communication, the person, or persons, responsible for each
+enhancement is noted.  Any questions regarding the new functionality
+should be directed to them first.
+
+KERNEL:
+
+Merged VM-File Buffer Cache
+---------------------------
+A merged VM/buffer cache design greatly enhances overall system
+performance and makes it possible to do a number of more optimal
+memory allocation strategies that were not possible before.
+
+Owner:                  David Greenman (davidg@FreeBSD.org) and
+                        John Dyson (dyson@implode.root.com)
+
+
+Network PCB hash optimization
+-----------------------------
+For systems with a great number of active TCP connections (WEB and ftp
+servers, for example), this greatly speeds up the lookup time required
+to match an incoming packet up to its associated connection.
+
+Owner:                  David Greenman (davidg@FreeBSD.org)
+
+
+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 
+management of the cache in various other ways while we were at it.
+
+Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
+                        David Greenman (davidg@FreeBSD.org)
+
+
+Less restrictive swap-spaces
+----------------------------
+The need to compile the names of the swap devices into the kernel has been
+removed.  Now swapon will accept any block devices, up to the maximum
+number of swap devices configured in the kernel.
+
+Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
+                        David Greenman (davidg@FreeBSD.org)
+
+
+Hard Wired SCSI Devices
+-----------------------
+Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers
+to SCSI devices as they were probed, allowing a SCSI device failure to
+possibly change unit number assignment and prevent filesystems on
+still functioning disks from mounting.  Hard wiring allows static
+allocation of unit numbers (and hence device names) to scsi devices
+based on SCSI ID and bus.  SCSI configuration occurs in the kernel
+config file.  Samples of the configuration syntax can be found in the
+scsi(4) man page or the LINT kernel config file.
+
+Owner:                  Peter Dufault (dufault@hda.com)
+Sources involved:       sys/scsi/* usr.sbin/config/*
+
+
+Slice Support
+-------------
+FreeBSD now supports a "slice" abstraction which makes it more
+completely interoperable with other operating system partitions.  This
+support will allow FreeBSD to inhabit DOS extended partitions.
+
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+Sources involved:       sys/disklabel.h sys/diskslice.h sys/dkbad.h
+                        kern/subr_diskslice.c kern/subr_dkbad.c
+                        i386/isa/diskslice_machdep.c
+                        i386/isa/wd.c scsi/sd.c dev/vn/vn.c
+
+
+Support for Ontrack Disk Manager Version 6.0
+--------------------------------------------
+Support has been added for disks which use Ontrack Disk Manager.  The
+fdisk program does NOT know about it however, so make all changes
+using the install program on the boot.flp or the Ontrack Disk Manager
+tool under DOS.
+
+Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
+
+
+Bad144 is back and working
+--------------------------
+Bad144 works again, though the semantics are slightly different than
+before in that the bad-spots are kept relative to the slice rather
+than absolute on the disk.
+
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+                        Poul-Henning Kamp (phk@FreeBSD.org)
+
+
+NEW DEVICE SUPPORT:
+
+                        SCSI and CDROM Devices
+
+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) 
+data frames of any compact disc.  Audio discs may be played using Karoke
+variable speed functions.
+
+Owner:                  Frank Durda IV   bsdmail@nemesis.lonestar.org
+Sources involved:       isa/matcd
+
+
+Adaptec 2742/2842/2940 SCSI driver
+----------------------------------
+The original 274x/284x driver has evolved considerably since the 2.0
+release.  We now offer full support for the 2940 series as well as the
+Wide models of these cards.  The arbitration bug (as well as many
+others) that caused the driver problems with fast devices has been
+corrected and there is even experimental tagged queuing support
+(kernel option "AHC_TAGENABLE").  John Aycock has also released the
+sequencer code under a "Berkeley style" copyright making the driver
+entirely clean of the GPL.
+
+Owner:                  Justin Gibbs (gibbs@FreeBSD.org)
+Sources involved:       isa/aic7770.c pci/aic7870.c i386/scsi/*
+                        sys/dev/aic7xxx/*
+
+
+NCR5380/NCR53400 SCSI ("ProAudio Spectrum") driver
+--------------------------------------------------
+Owner:                  core
+Submitted by:           Serge Vakulenko (vak@cronyx.ru)
+Sources involved:       isa/ncr5380.c
+
+
+Sony CDROM driver
+-----------------
+Owner:                  core
+Submitted by:           Mikael Hybsch (micke@dynas.se)
+Sources involved:       isa/scd.c
+
+
+                        Serial Devices
+
+SDL Communications Riscom/8 Serial Board Driver
+-----------------------------------------------
+Owner:                  Andrey Chernov (ache@FreeBSD.org)
+Sources involved:       isa/rc.c isa/rcreg.h
+
+
+Cyclades Cyclom-y Serial Board Driver
+-------------------------------------
+Owner:                  Bruce Evans (bde@FreeBSD.org)
+Submitted by:           Andrew Werple (andrew@werple.apana.org.au) and
+                        Heikki Suonsivu (hsu@cs.hut.fi)
+Obtained from:          NetBSD
+Sources involved:       isa/cy.c
+
+
+Cronyx/Sigma sync/async serial driver
+-------------------------------------
+Owner:                  core
+Submitted by:           Serge Vakulenko
+Sources involved:       isa/cronyx.c            
+
+
+
+                        Networking
+
+Diskless booting
+----------------
+Diskless booting in 2.0.5 is much improved.  The boot-program is in
+src/sys/i386/boot/netboot, and can be run from an MSDOS system or
+burned into an EPROM.  Local swapping is also possible.  WD, SMC, 3COM
+and Novell ethernet cards are currently supported.
+
+
+DEC DC21140 Fast Ethernet driver
+--------------------------------
+This driver supports any of the numerous NICs using the DC21140 chipset 
+including the 100Mb DEC DE-500-XA and SMC 9332.
+
+Owner:                  core
+Submitted by:           Matt Thomas (thomas@lkg.dec.com)
+Sources involved:       pci/if_de.c pci/dc21040.h
+
+
+DEC FDDI (DEFPA/DEFEA) driver
+-----------------------------
+Owner:                  core
+Submitted by:           Matt Thomas (thomas@lkg.dec.com)
+Sources involved:       pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h
+
+
+3Com 3c505 (Etherlink/+) NIC driver
+-----------------------------------
+Owner:                  core
+Submitted by:           Dean Huxley (dean@fsa.ca)
+Obtained from:          NetBSD
+Sources involved:       isa/if_eg.c
+
+
+Fujitsu MB86960A family of NICs driver
+-------------------------------------
+Owner:                  core
+Submitted by:           M.S. (seki@sysrap.cs.fujitsu.co.jp)
+Sources involved:       isa/if_fe.c
+
+
+Intel EtherExpress driver
+-------------------------
+Owner:                  Rodney W. Grimes (rgrimes@FreeBSD.org)
+Sources involved:       isa/if_ix.c isa/if_ixreg.h
+
+
+3Com 3c589 driver
+-----------------
+Owner:                  core
+Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
+                        Seiji Murata (seiji@mt.cs.keio.ac.jp) and
+                        Noriyuki Takahashi (hor@aecl.ntt.jp)
+Sources involved:       isa/if_zp.c
+
+
+IBM Credit Card Adapter driver
+------------------------------
+Owner:                  core
+Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
+Sources involved:       isa/pcic.c isa/pcic.h
+
+
+EDSS1 and 1TR6 ISDN interface driver
+------------------------------------
+Owner:                  core
+Submitted by:           Dietmar Friede (dfriede@drnhh.neuhaus.de) and
+                        Juergen Krause (jkr@saarlink.de)
+Sources involved:       gnu/isdn/*
+
+
+                        Miscellaneous Drivers
+
+Joystick driver
+---------------
+Owner:                  Jean-Marc Zucconi (jmz@FreeBSD.org)
+Sources involved:       isa/joy.c
+
+
+National Instruments "LabPC" driver
+-----------------------------------
+Owner:                  Peter Dufault (dufault@hda.com)
+Sources involved:       isa/labpc.c
+
+
+WD7000 driver
+-------------
+Owner:                  Olof Johansson (offe@ludd.luth.se)
+
+
+Pcvt Console driver
+-------------------
+Owner:                  Joerg Wunsch (joerg@FreeBSD.org)
+Submitted by:           Hellmuth Michaelis (hm@altona.hamburg.com)
+Sources involved:       isa/pcvt/* usr.sbin/pcvt/*
+
+
+BSD-audio emulator for VAT driver
+---------------------------------
+Owner:                  Amancio Hasty (ahasty@FreeBSD.org) and
+                        Paul Traina (pst@FreeBSD.org)
+Sources involved:       isa/sound/vat_audio.c isa/sound/vat_audioio.h
+
+
+National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver
+--------------------------------------------------------
+Owner:                  core
+Submitted by:           Fred Cawthorne (fcawth@delphi.umd.edu)
+Sources involved:       isa/gpib.c isa/gpib.h isa/gpibreg.h
+
+
+Genius GS-4500 hand scanner driver
+----------------------------------
+Owner:                  core
+Submitted by:           Gunther Schadow (gusw@fub46.zedat.fu-berlin.de)
+Sources involved:       isa/gsc.c isa/gscreg.h
+
+
+CORTEX-I Frame Grabber
+----------------------
+Owner:                  core
+Submitted by:           Paul S. LaFollette, Jr.
+Sources involved:       isa/ctx.c isa/ctxreg.h
+
+
+Video Spigot video capture card
+-------------------------------
+Owner:                  Jim Lowe
+
+
+
+1.2 Experimental features
+-------------------------
+
+The unionfs and LFS file systems are known to be severely broken in
+2.0.5.  This is in part due to old bugs that we haven't had time to
+resolve yet and the need to update these file systems to deal with the
+new VM system.  We hope to address these issues in a later release of
+FreeBSD.
+
+FreeBSD now supports running iBCS2 compatible binaries (currently SCO
+UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).  The iBCS2
+emulator is in its early stages, but it is functional, we haven't been
+able to do exhaustive testing (lack of commercial apps), but almost
+all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10
+for SCO. Further testing is nessesary to complete this project. There
+is also work under way for ELF & XOUT loaders, and most of the svr4
+syscall wrappers have been written.
+
+FreeBSD also implements enough of its Linux compatibility that we
+can now run Linux DOOM!  See the ``xperimnt'' directory (on your local
+FTP server or CDROM) for full docs on how to set this up.
+
+Owner:                  Soren Schmidt (sos) & Sean Eric Fagan (sef)
+Sources involved:       sys/i386/ibcs2/* + misc kernel changes.
+
+
+2. Supported Configurations
+---------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+Following is a list of all disk controllers and ethernet cards currently
+known to work with FreeBSD.  Other configurations may very well work, and
+we have simply not received any indication of this.
+
+
+2.1. Disk Controllers
+---------------------
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+WD7000
+IDE
+ATA
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards as they have no
+   on-board BIOS, which is necessary for mapping the boot device into the
+   system BIOS I/O vectors.  They're perfectly usable for external tapes,
+   CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
+   without a boot ROM.  Some systems DO have a boot ROM, which is generally
+   indicated by some sort of message when the system is first powered up
+   or reset.  Check your system/board documentation for more details.
+
+[Note that Buslogic was formerly known as "Bustec"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+Buslogic 956c PCI SCSI controller
+
+NCR 53C810 and 53C825 PCI SCSI controller.
+NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+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 
+(matcd) Matsushita/Panasonic (Creative) proprietary interface
+(scd)   Sony proprietary interface
+
+Note: CD-Drives with IDE interfaces are not supported at this time.
+
+Some controllers have limitations with the way they deal with >16MB of
+memory, due to the fact that the ISA bus only has a DMA address space
+of 24 bits.  If you do your arithmetic, you'll see that this makes it
+impossible to do direct DMA to any address >16MB.  This limitation is
+even true of some EISA controllers (which are normally 32 bit) when
+they're configured to emulate an ISA card, which they then do in *all*
+respects.  This problem is avoided entirely by IDE controllers (which
+do not use DMA), true EISA controllers (like the UltraStor, Adaptec
+1742A or Adaptec 2742) and most VLB (local bus) controllers.  In the
+cases where it's necessary, the system will use "bounce buffers" to
+talk to the controller so that you can still use more than 16Mb of
+memory without difficulty.
+
+
+2.2. Ethernet cards
+-------------------
+
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21140 based NICs (SMC???? DE???)
+DEC FDDI (DEFPA/DEFEA) NICs
+
+Fujitsu MB86960A family of NICs
+
+Intel EtherExpress
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+
+2.3. Misc
+---------
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+Mitsumi (all models) CDROM interface and drive.
+
+SDL Communications Riscom/8 Serial Board.
+
+SoundBlaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
+
+Matsushita/Panasonic (Creative SoundBlaster) CDROM interface and drive.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
+support is apparently close to materializing.  Details will be posted
+as the situation develops.
+
+
+3. Obtaining FreeBSD
+--------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+1. FTP/Mail
+
+You can ftp FreeBSD and any or all of its optional packages from
+`ftp.freebsd.org' - the official FreeBSD release site.
+
+For other locations that mirror the FreeBSD software see the file
+MIRROR.SITES.  Please ftp the distribution from the nearest site
+to you netwise.
+
+If you do not have access to the internet and electronic mail is your
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
+to get more information on how to fetch files from ftp.freebsd.org.
+Note: This approach will end up sending many *tens of megabytes*
+through the mail, and should only be employed as an absolute LAST
+resort!
+
+
+2. CDROM
+
+FreeBSD 2.0.5 may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
+
+Or via the internet from orders@cdrom.com or http://www.cdrom.com.
+Their current catalog can be obtained via ftp as:
+        ftp://ftp.cdrom.com/cdrom/catalog.
+
+Cost per CD is $39.95, or $24.95 with a FreeBSD subscription.  With
+a subscription, you will automatically receive updates as they
+are released.  Your credit card will be billed when each disk is shipped
+and you may cancel your subscription at any time without further obligation.
+
+Walnut Creek CDROM also sells a full line of FreeBSD related merchandise such
+as T-shirts ($14.95, available in "child", Large and XL sizes), coffee mugs
+($9.95), tattoos ($0.25 each) and posters ($3.00).
+
+Shipping (per order not per disc) is $5 in the US, Canada or
+Mexico and $9.00 overseas.  They accept Visa, Mastercard, Discover,
+American Express or checks in U.S. Dollars and ship COD within the
+United States.  California residents please add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+
+Reporting problems, making suggestions, submitting code
+-------------------------------------------------------
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached if you can!).
+
+The preferred method to submit bug reports from a machine with
+internet mail connectivity is to use the send-pr command.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.
+
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                questions@FreeBSD.org
+
+Additionally, being a volunteer effort, we are always happy to have
+extra hands willing to help - there are already far more enhancements
+to be done than we can ever manage to do by ourselves!  To contact us
+on technical matters, or with offers of help, you may send mail to:
+
+                hackers@FreeBSD.org
+
+Since these mailing lists can experience significant amounts of
+traffic, if you have slow or expensive mail access and you are
+only interested in keeping up with significant FreeBSD events, you may
+find it preferable to subscribe to:
+
+                announce@FreeBSD.org
+
+
+All but the freebsd-bugs groups 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
+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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If your
+name is not mentioned, please be assured that its omission is entirely
+accidental.
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his initial work with 386BSD.
+
+The FreeBSD Core Team
+(in alphabetical order by first name):
+
+        Andreas Schulz <ats@FreeBSD.org>
+        Andrey A. Chernov <ache@FreeBSD.org>
+        Bruce Evans <bde@FreeBSD.org>
+        David Greenman <davidg@FreeBSD.org>
+        Garrett A. Wollman <wollman@FreeBSD.org>
+        Gary Palmer <gpalmer@FreeBSD.org>
+        Geoff Rehmet <csgr@FreeBSD.org>
+        Jack Vogel <jackv@FreeBSD.org>
+        John Dyson <dyson@FreeBSD.org>
+        Jordan K. Hubbard <jkh@FreeBSD.org>
+        Justin Gibbs <gibbs@FreeBSD.org>
+        Paul Richards <paul@FreeBSD.org>
+        Poul-Henning Kamp <phk@FreeBSD.org>
+        Rich Murphey <rich@FreeBSD.org>
+        Rodney W. Grimes <rgrimes@FreeBSD.org>
+        Satoshi Asami <asami@FreeBSD.org>
+        Søren Schmidt <sos@FreeBSD.org>
+
+Special mention to:
+
+        Walnut Creek CDROM, without whose help (and continuing support)
+        this release would never have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        Additional FreeBSD helpers and beta testers:
+
+        J.T. Conklin                            Julian Elischer
+        Frank Durda IV                          Peter Dufault
+        Sean Eric Fagan                         Jeffrey Hsu
+        Terry Lambert                           L Jonas Olsson
+        Chris Provenzano                        Dave Rivers
+        Guido van Rooij                         Steven Wallace
+        Atsushi Murai                           Scott Mace
+        Nate Williams
+
+        And everyone at Montana State University for their initial support.
+
+
+Jordan would also like to give special thanks to Poul-Henning Kamp and
+Gary Palmer, both of whom put in long hours helping him to construct
+the new installation utility.  Poul, being a proud new father, was
+especially pressed for time and yet somehow managed to put in
+a significant amount of effort anyway.  This release could not have
+happened without him!  Thank you both!
+
+Thanks also to everyone else who helped, especially those not
+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 
+
    + +&footer; + + diff --git a/en/releases/2.0/Makefile b/en/releases/2.0/Makefile new file mode 100644 index 0000000000..8955b2ea3e --- /dev/null +++ b/en/releases/2.0/Makefile @@ -0,0 +1,4 @@ +DOCS= announce.sgml credits.sgml install.sgml notes.sgml + +.include "../../web.mk" + diff --git a/en/releases/2.0/announce.sgml b/en/releases/2.0/announce.sgml new file mode 100644 index 0000000000..5a9fce45e5 --- /dev/null +++ b/en/releases/2.0/announce.sgml @@ -0,0 +1,155 @@ + + + + %includes; +]> + +&header; + +

    +To: announce@freefall.cdrom.com
    +Subject: 2.0 RELEASE is now available on ftp.freebsd.org!
    +Date: Tue, 22 Nov 1994 06:35:37 -0800
    +From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com> +

    + +

    +The FreeBSD Project team is very pleased to announce their release of +FreeBSD 2.0; a full 32 bit 4.4 BSD Lite based operating system for +Intel PCs (i386, i486 and Pentium class). + +

    +Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD has +changed almost entirely. A new port from the Berkeley 4.4 code base +was done, which brought the legal status of the system out of the +shadows with the blessing of Novell (new owners of USL and UNIX). The +port to 4.4 also brought in a host of new features, filesystems and +enhanced driver support. With our new unencumbered code base, we have +every reason to hope that we'll be able to release quality operating +systems without further legal encumbrance for some time to come! + +

    +FreeBSD 2.0 represents the culmination of almost 2 years of work and +many thousands of man hours put in by an international development +team. We hope you enjoy it! + +

    +FreeBSD 2.0 also features an advanced installation that enables one to +install from tape, CD, NFS or FTP over SLIP, ethernet or the parallel +port, and DOS floppies or hard disk partitions. This is, we feel, our +easiest to use installation yet! Many many suggestions from the +previous 2.0 ALPHA release were incorporated, and RELEASE is now far +less dangerous [we hope :-)]than ALPHA was! + +

    +FreeBSD 2.0 also supports more friendly co-habitation with other +operating systems, allowing you to easily mount DOS filesystems and +install a multi-OS boot manager without having to leave the +installation utility. All planned installation methods are now also +supported. A trouble-shooting guide for those in, well, trouble may +also be of help and is featured on the boot floppy. + +

    +For more information on what's new with FreeBSD, or what general +features it offers, we strongly suggest that you simply download our +boot floppy and boot from it. You can easily read the release notes +on it using a simple menu, and with no danger to the contents of your +hard disk (unless you deliberately chose "proceed with installation", +in which case your fate is in your own hands! :-). + +

    +An upgrade path from ALPHA->RELEASE will also be provided shortly for +the benefit of those who were kind enough to help us test the early +snapshot of 2.0. Watch the announce list for its availability, or +simply be impatient and extract the 2.0R bindist over your ALPHA one! +:-) + +

    +Those wishing to obtain this version of 2.0 on CDROM should contact +our sponsors, Walnut Creek CDROM (info@cdrom.com) or any of the other +CD vendors who will, no doubt, be doing their own releases. + +

    +If you're currently running 1.x and are looking for an upgrade path, +we're sorry to say that only full installations are supported at this +time. Simply back up your password and user files before reinstalling +from the 2.0 media, then bring them back. If public demand is high +enough, and we can figure out a way of easily doing it, we'll offer +something, but it should be understood that the differences between +1.x and 2.0 are *large*, and it's not certain that we'll be able to do +it at all. + +

    +Those unable or unwilling to download the boot floppy may also get the +release notes by mail - send mail to <info@FreeBSD.org> for an +automated reply. Updated information will also be provided on a more +or less continuous basis in our WEB pages: + + http://www.freebsd.org + +

    +FreeBSD 2.0 RELEASE is or will be available for ftp in the following +locations: + +

      +
    • Primary ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE +
    • U.S-2 ftp://ftp.dataplex.net/pub/FreeBSD/2.0-RELEASE +
    • U.S-3 ftp://kryten.atinc.com/pub/FreeBSD/2.0-RELEASE +
    • U.S-4 ftp://ref.tfs.com/pub/FreeBSD/2.0-RELEASE +
    • Taiwan ftp://netbsd.csie.nctu.edu.tw/pub/FreeBSD/2.0-RELEASE +
    • Australia ftp://ftp.physics.usyd.edu.au/FreeBSD/2.0-RELEASE +
    • France ftp://ftp.ibp.fr/pub/freeBSD/2.0-RELEASE +
    • Finland ftp://nic.funet.fi:/pub/unix/FreeBSD/2.0-RELEASE +
    • Russia ftp://ftp.kiae.su/FreeBSD/2.0-RELEASE +
    + +

    +(Translated for the non-URL literate: FreeBSD is available for anonymous + ftp on ftp.freebsd.org in the pub/FreeBSD/2.0-RELEASE directory) + +

    +It will also, no doubt, be available on a number of mirror sites as +soon as they pick it up. However, ftp.freebsd.org is on a T3 line and +supports 300 simultaneous users (it's a FreeBSD machine :-), so it's +unlikely that you'll have too much trouble getting it from this site +until the mirrors do so. + +

    +If you are directly Internet connected, it is also NOT necessary to +load the bindist from this site! Simply download the 2 boot floppies, +begin the installation, and select the FTP installation method - it +will do the rest for you, transparently. + +

    +Finally, we'd like to publically *thank* Walnut Creek CDROM, without +whos continuing support and extreme generousity, we'd probably be long +gone! They've been of immense help to us. + +

    +Thanks must also go to Poul-Henning Kamp, our fearless and long +suffering release engineer for 2.0. While all of us have sacrificed +much sleep to the cause, he has a new wife but has somehow managed to +do so as well! :-) + +

    +And to all of our users (this is probably starting to sound like the +academy awards :-), a similar thank you! We couldn't have done it +without your constant flow of commentary, patches, donations of code +and moral support. As corny as it sounds, we do it all for you folks! +[Though the ego gratification is nice too :-)] + +

    +Thanks to all, and we sincerely hope you enjoy this release! + +

    +Comments, as always, to hackers@FreeBSD.org. + + +

    + Jordan
    + [on behalf of the FreeBSD Project team] + +&footer; + + diff --git a/en/releases/2.0/credits.sgml b/en/releases/2.0/credits.sgml new file mode 100644 index 0000000000..98c88724de --- /dev/null +++ b/en/releases/2.0/credits.sgml @@ -0,0 +1,210 @@ + + + + %includes; +]> + +&header; + +

    +			   FreeBSD 2.0
+		         Contributor List
+
+
+
+Derived Software Contributors:
+
+This software was originally derived from William F. Jolitz's 386BSD
+release 0.1, though almost none of the original 386BSD specific code
+remains.  This software has been essentially reimplemented on top of
+4.4 BSD Lite, from the Computer Science Research Group (CSRG) at
+the University of California, Berkeley and associated academic
+contributors.
+
+There are also portions of NetBSD that have been integrated into FreeBSD
+as well, and we would therefore like to thank all the contributors
+to NetBSD for their work.  Despite some occasionally rocky moments in
+the relations between the two groups, we both want essentially the same
+thing:  More BSD based operating systems on people's computers!  We
+wish the NetBSD group every success in their endevors.
+
+
+Hardware Contributors:
+
+A special thank-you to Walnut Creek CDROM for providing the 486/DX2-66 EISA/VL
+system that is being used for our development work, to say nothing of
+the network access and other donations of hardware resources.  It would have
+been impossible to do this release without their support.
+
+Thanks also to Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+drive.  It's been most useful!
+
+
+The FreeBSD Core Team (in alphabetical order):
+
+	Andreas Schulz <ats@g386bsd.first.bmd.de>
+	Andrew A. Chernov <ache@astral.msk.su>
+	Bruce Evans <bde@FreeBSD.org>
+	David Greenman <davidg@Root.COM>
+	Garrett A. Wollman <wollman@freefall.cdrom.com>
+	Gary Palmer <gpalmer@FreeBSD.org>
+	Geoff Rehmet <csgr@cs.ru.ac.za>
+	Jack Vogel <jackv@FreeBSD.org>
+	John Dyson <dyson@implode.rain.com>
+	Jordan K. Hubbard <jkh@FreeBSD.org>
+	Paul Richards <paul@isl.cf.ac.uk>
+	Poul-Henning Kamp <phk@FreeBSD.org>
+	Rich Murphey <rich@lamprey.utmb.edu>
+	Rodney W. Grimes <rgrimes@cdrom.com>
+	Soren Schmidt <sos@FreeBSD.org>
+
+
+Additional FreeBSD Contributors (no particular order):
+
+Adam Glass <glass@postgres.berkeley.edu>
+Andrew Herbert <andrew@werple.apana.org.au>
+Andrew Moore <alm@FreeBSD.org>
+Atsushi Murai <amurai@spec.co.jp>
+Bob Wilcox <bob@obiwan.uucp>
+Bruce Evans <bde@kralizec.zeta.org.au>
+Charles Hannum <mycroft@ai.mit.edu>
+Chris G. Demetriou <cgd@postgres.berkeley.edu>
+Chris Torek <torek@ee.lbl.gov>
+Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
+Curt Mayer <curt@toad.com>
+Dave Burgess <burgess@hrd769.brooks.af.mil>
+Dave Rivers <rivers@ponds.uucp>
+David Dawes <dawes@physics.su.OZ.AU>
+Frank Maclachlan <fpm@crash.cts.com>
+Gary A. Browning <gab10@griffcd.amdahl.com>
+Gary Clark II <gclarkii@radon.gbdata.com>
+Guido van Rooij <guido@gvr.win.tue.nl>
+Havard Eidnes <Havard.Eidnes@runit.sintef.no>
+Holger Veit <Holger.Veit@gmd.de>
+Ishii Masahiro, R. Kym Horsell
+J.T. Conklin <jtc@winsey.com>
+James Clark <jjc@jclark.com>
+James da Silva <jds@cs.umd.edu> et al
+Jim Wilson <wilson@moria.cygnus.com>
+Joerg Wunsch <joerg_wunsch@uriah.sax.de>
+Julian Elischer <julian@dialix.oz.au>
+Julian Stacey <stacey@guug.de> <fallback: <julian@meepmeep.pcs.com>>
+Keith Bostic <bostic@toe.CS.Berkeley.EDU>
+Keith Moore <?>
+Marc Frajola <marc@escargot.rain.com>
+Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
+Martin Birgmeier
+Paul Kranenburg <pk@cs.few.eur.nl>
+Paul Mackerras <paulus@cs.anu.edu.au>
+Poul-Henning Kamp <phk@login.dkuug.dk>
+Rob Shady <rls@id.net>
+Sascha Wildner <swildner@channelz.GUN.de>
+Scott Mace <smace@FreeBSD.org>
+Sean Eric Fagan <sef@kithrup.com>
+Serge V. Vakulenko <vak@zebub.msk.su>
+Steven Wallace <swallace@ece.uci.edu>
+Søren Schmidt <sos@login.dkuug.dk>
+Terry Lee <terry@uivlsi.csl.uiuc.edu>
+Theo Deraadt <deraadt@fsa.ca>
+Ugen J.S.Antsilevich <ugen@NetVision.net.il>
+Yuval Yarom <yval@cs.huji.ac.il>
+
+
+386BSD Patch kit patch contributors (no particular order):
+
+Adam Glass <glass@postgres.berkeley.edu>
+Adrian Hall <adrian@ibmpcug.co.uk>
+Andrew A. Chernov <ache@astral.msk.su>
+Andrew Herbert <andrew@werple.apana.org.au>
+Andrew Moore <alm@netcom.com>
+Andy Valencia <ajv@csd.mot.com> <jtk@netcom.com>
+Arne Henrik Juul <arnej@Lise.Unit.NO>
+Bakul Shah <bvs@bitblocks.com>
+Barry Lustig <barry@ictv.com>
+Bob Wilcox <bob@obiwan.uucp>
+Branko Lankester
+Brett Lymn <blymn@mulga.awadi.com.AU>
+Bruce Evans <bde@kralizec.zeta.org.au>
+Charles Hannum <mycroft@ai.mit.edu>
+Chris G. Demetriou <cgd@postgres.berkeley.edu>
+Chris Torek <torek@ee.lbl.gov>
+Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
+Daniel Poirot <poirot@aio.jsc.nasa.gov>
+Dave Burgess <burgess@hrd769.brooks.af.mil>
+Dave Rivers <rivers@ponds.uucp>
+David Dawes <dawes@physics.su.OZ.AU>
+David Greenman <davidg@Root.COM>
+Eric J. Haug <ejh@slustl.slu.edu>
+Felix Gaehtgens <felix@escape.vsse.in-berlin.de>
+Frank Maclachlan <fpm@crash.cts.com>
+Gary A. Browning <gab10@griffcd.amdahl.com>
+Geoff Rehmet <csgr@alpha.ru.ac.za>
+Goran Hammarback <goran@astro.uu.se>
+Guido van Rooij <guido@gvr.win.tue.nl>
+Guy Harris <guy@auspex.com>
+Havard Eidnes <Havard.Eidnes@runit.sintef.no>
+Herb Peyerl <hpeyerl@novatel.cuc.ab.ca
+Holger Veit <Holger.Veit@gmd.de>
+Ishii Masahiro, R. Kym Horsell
+J.T. Conklin <jtc@winsey.com>
+Jagane D Sundar < jagane@netcom.com >
+James Clark <jjc@jclark.com>
+James Jegers <jimj@miller.cs.uwm.edu>
+James W. Dolter
+James da Silva <jds@cs.umd.edu> et al
+Jay Fenlason <hack@datacube.com>
+Jim Wilson <wilson@moria.cygnus.com>
+Joerg Lohse <lohse@tech7.informatik.uni-hamburg.de>
+Joerg Wunsch <joerg_wunsch@uriah.sax.de>
+John Dyson - <formerly dyson@ref.tfs.com>
+John Woods <jfw@eddie.mit.edu>
+Jordan K. Hubbard <jkh@whisker.hubbard.ie>
+Julian Elischer <julian@dialix.oz.au>
+Julian Stacey <stacey@guug.de> <fallback: <julian@meepmeep.pcs.com>>
+Karl Lehenbauer <karl@NeoSoft.com> <karl@one.neosoft.com>
+Keith Bostic <bostic@toe.CS.Berkeley.EDU>
+Ken Hughes
+Kent Talarico <kent@shipwreck.tsoft.net>
+Kevin Lahey <kml%rokkaku.UUCP@mathcs.emory.edu> <kml@mosquito.cis.ufl.edu>
+Marc Frajola <marc@escargot.rain.com>
+Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
+Martin Renters <martin@innovus.com>
+Michael Galassi <nerd@percival.rain.com>
+Mike Durkin <mdurkin@tsoft.sf-bay.org>
+Nate Williams <nate@bsd.coe.montana.edu>
+Nick Handel <nhandel@NeoSoft.com> <nick@madhouse.neosoft.com>
+Pace Willisson <pace@blitz.com>
+Paul Kranenburg <pk@cs.few.eur.nl>
+Paul Mackerras <paulus@cs.anu.edu.au>
+Paul Popelka <paulp@uts.amdahl.com>
+Peter da Silva <peter@NeoSoft.com>
+Phil Sutherland <philsuth@mycroft.dialix.oz.au>
+Poul-Henning Kamp <phk@login.dkuug.dk>
+Ralf Friedl <friedl@informatik.uni-kl.de>
+Rich Murphey <rich@lamprey.utmb.edu>
+Rick Macklem <root@snowhite.cis.uoguelph.ca>
+Robert D. Thrush <rd@phoenix.aii.com>
+Rodney W. Grimes <rgrimes@cdrom.com>
+Rog Egge <?>
+Sascha Wildner <swildner@channelz.GUN.de>
+Scott Burris <scott@pita.cns.ucla.edu>
+Scott Reynolds <scott@clmqt.marquette.mi.us>
+Sean Eric Fagan <sef@kithrup.com>
+Simon J Gerraty <sjg@melb.bull.oz.au> <sjg@zen.void.oz.au>
+Stephen McKay <robert@psych.psy.uq.oz.au>
+Terry Lambert <terry@icarus.weber.edu>
+Terry Lee <terry@uivlsi.csl.uiuc.edu>
+Warren Toomey <wkt@csadfa.cs.adfa.oz.au>
+Wiljo Heinen <wiljo@freeside.ki.open.de>
+William Jolitz <withheld>
+Wolfgang Solfrank <ws@tools.de>
+Wolfgang Stanglmeier <wolf@dentaro.GUN.de>
+Yuval Yarom <yval@cs.huji.ac.il>
+
+Id: CONTRIB.FreeBSD,v 1.1 1994/11/18 12:03:25 jkh Exp
+
    + +&footer; + + diff --git a/en/releases/2.0/install.sgml b/en/releases/2.0/install.sgml new file mode 100644 index 0000000000..a0672eccb9 --- /dev/null +++ b/en/releases/2.0/install.sgml @@ -0,0 +1,493 @@ + + + + %includes; +]> + +&header; + +
    +Welcome to FreeBSD 2.0, the complete 4.4 BSD Lite based OS for Intel (or
+compatible) based PCs.
+
+There are several documents on the floppy and a couple of on-line help
+screens that will greatly assist you in installing your system as you go
+along.  Nonetheless, initial user testing has shown that some of the
+terminology used may be difficult for newcomers to UN*X to understand, so
+we've prepared this step-by-step guide explaining a typical installation.
+You may find it useful to print this out and keep it handy as you go
+through the installation, or at least read through it once carefully so
+that some of the prompts and questions you encounter do not come as
+complete surprises.
+
+Before you do anything, make two 1.44MB floppies from the two image files
+you'll find in the floppies/ directory - boot.flp and cpio.flp.  If you're
+reading this under DOS, you can do it in 1 easy step, or 3 in case this
+doesn't (for some weird reason) work:
+
+1. If you're reading this file after typing "go", simply ESC back out for
+   a moment and select the "makeflp" batch file to make the two floppies.
+   This will invoke the DOS formatter to format the floppies and then
+   attempt to write the two disk images onto them.  If this doesn't work,
+   follow steps 2 through 4:
+
+2. Use the DOS format command to format 2 NEW floppies.  A lot of problems
+   have been caused by people using old and defective floppies, and much
+   grief can often be saved by simply using new, or at least trusted,
+   media.
+
+3. Insert the first floppy and type:
+
+		tools\dos-tool\rawrite floppies\boot.flp a:
+
+4. Insert the second floppy and type
+
+		tools\dos-tool\rawrite floppies\cpio.flp a:
+
+You're now prepared to boot from the boot floppy and begin the installation.
+
+
+The installation starts with the following screen:
+
+  +-------------------------- Welcome to FreeBSD! ---------------------------+
+  | Use ALT-F2 and ALT-F1 to toggle between debugging                        |
+  | information screen (ALT-F2) or this dialog screen (ALT-F1)               |
+  |                                                                          |
+  | Please select one of the following options:                              |
+  | +----------------------------------------------------------------------+ |
+  | | 1. README               READ THIS FIRST.                             | |
+  | | 2. Release Notes        Read the 2.0 Release Notes (recommended).    | |
+  | | 3. Troubleshooting      Read this in case of trouble.                | |
+  | | 4. Partitions and MBRs  Verbose description of how these work.       | |
+  | | 5. COPYRIGHT            Read FreeBSD Copyright Information.          | |
+  | | 6. Install              Proceed with full installation.              | |
+  | | 7. Fixit                Repair existing installation (`fixit' mode). | |
+  | | 8. Quit                 Don't do anything, just reboot.              | |
+  | +----------------------------------------------------------------------+ |
+  +--------------------------------------------------------------------------+
+  |                          <  OK  >      <Cancel>                          |
+  +--------------------------------------------------------------------------+
+
+
+You can move the arrow keys up and down to highlight the various options,
+selecting an option by hitting return when its line is highlighted.  You
+can also type the number of the option you want (1 - 7) and hit return.
+It's recommended that you read the README at a minimum, though the Release
+Notes are also helpful.  This may seem a like a lot to read, but if you are
+new to FreeBSD then these notes are invaluable for explaining the system
+and are highly recommended.
+
+When you're done reading docs, select Install (5) to proceed to the next
+screen.
+
+This next screen is the disk editor screen, which looks like this:
+
+------------------------------------------------------------------------------
+FreeBSD 2.0-RELEASE Installation -- Diskspace editor
+
+Disks         Total   FreeBSD                    |You should now assign some
+                                                 |space to root, swap, and
+ 0: sd0     2006 MB      0 MB                    |(optionally) /usr partitions
+ 1: sd1      496 MB      0 MB                    |Root (/) should be a minimum
+                                                 |of 18MB with a 30MB /usr
+Filesystems  Type        Size  Action Mountpoint |or 50MB without a /usr.
+                                                 |Swap space should be a
+                                                 |minimum of 12MB or RAM * 2
+                                                 |Be sure to also (A)ssign a
+                                                 |mount point to each one or
+                                                 |it will NOT be enabled.
+                                                 |
+                                                 |We suggest that you invoke
+                                                 |(F)disk, (W)rite the bootcode
+                                                 |then (D)isklabel your disk.
+                                                 |If installing on a drive
+                                                 |other than 0, also read the
+                                                 |TROUBLESHOOTING doc first
+Commands available:
+(H)elp  (T)utorial  (F)disk  (D)isklabel  (P)roceed  (Q)uit
+
+Enter Command>
+
+------------------------------------------------------------------------------
+
+As we can see, this system has two drives, sd0 and sd1.  On an IDE system,
+these would show up as "wd0" and "wd1" (or, on a single drive system, just
+sd0 or wd0).  We can see that neither of them has any space assigned to
+FreeBSD (they each show 0MB under the FreeBSD column), so we follow the
+instructions on the right hand side of the screen and invoke the (F)disk
+editor by typing `f':
+
+Enter Command> F
+
+We're now prompted with the drive number to (F)disk, so we enter 0 for
+the first drive:
+
+Enter number of disk to Fdisk> 0
+
+This now brings us to the FDISK editor screen, which looks like this:
+
+------------------------------------------------------------------------------
+FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- FDISK
+
+Disk: sd0   Geometry:  2006 Cyl * 32 Hd * 64 Sect = 2006Mb = 4108600 Sect
+
+1 Boot?=No    Type=Primary 'big' DOS (> 32MB)
+  Phys=(c0/h1/s1..c299/h63/s32)   Sector=(32..614399)
+  Size=300 MB, 299 Cylinders + 31 Tracks + 32 Sectors
+
+2 Unused
+
+
+3 Unused
+
+
+4 Unused
+
+
+Commands available:
+(H)elp   (T)utorial   (D)elete   (E)dit   (R)eread   (W)rite MBR   (Q)uit
+(U)se entire disk for FreeBSD   (G)eometry   Write MBR (B)ootcode
+Enter Command>
+
+------------------------------------------------------------------------------
+
+We see that drive 0 has a DOS partition (also called a "slice" in FreeBSD
+parlance, to distinguish it from a FreeBSD partition) on it which is 300MB
+in size (don't worry if the numbers you see are much smaller than these - I
+have a pretty large 2.1GB disk! :-).  Let's also say we want to allocate
+the rest to FreeBSD, so to do this we want to (E)dit one of the existing
+slices.  We can see that 2, 3, and 4 are unused so let's pick the first
+unused one, which is 2 (if we wanted to replace an existing operating
+system slice with FreeBSD, we'd pick its number instead).  We first type
+`E' to edit a slice entry:
+
+Enter Command> E
+
+And we're prompted for a slice to edit.  We type 2:
+
+Edit which Slice> 2
+
+Now we're prompted for the size of the new slice, the default for which is
+all remaining space on the disk.  Let's say that we don't want to allocate
+ALL the space on the disk, but want to reserve 400MB for some other future
+OS.  The total amount of free space left is 1706MB, which is the default
+value selected for us, so we backspace over it and enter 1306:
+
+Size of slice in MB> 1306
+
+Now we're asked for the type of the slice.  The type is what tells the PC
+what sort of slice this is.  DOS primary slices are, for example, type 6.
+FreeBSD slices are type 0xa5 (hexadecimal).  If we wanted to reserve space
+at this time for some other type of OS like Linux or OS/2, and we knew
+their slice type (0x82 for Linux and 0x0A for OS/2, just in case you're
+interested), we could also do that from this editor, but we're only
+interested in FreeBSD for now so we accept the default.
+
+Type of slice (0xa5=FreeBSD)> 0xa5
+
+The next prompt asks if we want to make this slice bootable by
+default, which we do so we accept the default:
+
+Bootflag (0x80 for YES)> 0x80
+
+At this point we come back to the main screen, which now shows a new entry
+for slice 2:
+
+------------------------------------------------------------------------------
+FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- FDISK
+
+Disk: sd0   Geometry:  2006 Cyl * 32 Hd * 64 Sect = 2006Mb = 4108600 Sect
+
+1 Boot?=No    Type=Primary 'big' DOS (> 32MB)
+  Phys=(c0/h1/s1..c299/h63/s32)   Sector=(32..614399)
+  Size=300 MB, 299 Cylinders + 31 Tracks + 32 Sectors
+
+2 Boot?=Yes   Type=FreeBSD/NetBSD/386BSD
+  Phys=(c300/h0/s1..c1023/h31/s0)   Sector=(614400..3289087)
+  Size=1306 MB, 1306 Cylinders
+
+3 Unused
+
+
+
+4 Unused
+
+
+
+Commands available:
+(H)elp   (T)utorial   (D)elete   (E)dit   (R)eread   (W)rite MBR   (Q)uit
+(U)se entire disk for FreeBSD   (G)eometry   Write MBR (B)ootcode
+Enter Command>
+
+------------------------------------------------------------------------------
+
+At this point we're happy with the slices on the first drive, so we type
+`w' to write the new information out.  It also prompts to make *sure* we
+really want to do this, so we backspace over the default of `N' and type
+`y'<return>.  And this point, we also can decide whether or not we want a
+"boot manager" installed.  A boot manager is a little utility that prompts
+you for the operating system you want to boot every time you reset or power
+on your PC, and can be a very handy way of sharing your computer between
+FreeBSD and some other OS, like Linux or DOS.  We decide that we want to
+have this feature, so we `b' to write the special MBR (B)ootcode out to the
+disk.  This does not harm any of the other operating systems on the disk,
+as it's written to a special area.  Now we exit this screen by typing `q',
+for (Q)uit.
+
+This brings us back to the main prompt.  If we wanted to allocate any
+additional slices on other drives, we also could re-invoke the (F)disk
+editor by typing `f' again and giving a different drive number at the
+prompt, but we'll assume for now that we've only got one disk and want to
+go on.  Typing `d' now enters the (D)isklabel screen, which prompts us for
+the drive to write a disklabel onto, like the FDISK editor.  We type `0'
+for the first drive and hit return.  This brings us to the DISKLABEL editor
+screen, which looks like this:
+
+------------------------------------------------------------------------------
+FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- DISKLABEL
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a         0         0         0      0  unused
+b         0         0         0      0  unused
+c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
+d         0   4108599   4108600   2006  unused          <Entire Disk>
+e         0         0         0      0  unused
+f         0         0         0      0  unused
+g         0         0         0      0  unused
+h        32    614399    614368    300  MSDOS
+
+
+
+
+
+
+Total size:       2674688 blocks   1306Mb
+Space allocated:        0 blocks      0Mb
+
+Commands available:
+(H)elp  (T)utorial  (E)dit  (A)ssign  (D)elete  (R)eread  (W)rite  (Q)uit
+(P)reserve  (S)lice
+Enter Command>
+
+------------------------------------------------------------------------------
+
+The BSD partitions, a - h, are FreeBSD's way of dividing up a physical
+slice into multiple file systems.  Every FreeBSD system should have, at
+minimum, a root file system and a swap partition allocated.  The root
+file system is called "/", and is generally put on partition `a' by
+convention.  Swap partitions always go on `b', and the `c' and `d'
+partitions are special and point to the entire FreeBSD slice and the entire
+disk, respectively.  `c' and `d' cannot and should not be allocated to
+actual file systems.
+
+We also see that partition h points conveniently to the DOS slice,
+which we can also assign to a location in our file system hierarchy
+to conveniently share files between FreeBSD and DOS.  More on this in 
+a moment.
+
+A typical file system layout might look like this:
+
+/	20MB
+swap	32MB
+/usr	120MB
+
+/, or the root file system, contains system files and some temporary space.
+It should be at least 18MB in size, though a little extra doesn't hurt.
+Swap space is one of those "it never hurts to have too much" sorts of
+items, though if your system isn't too heavily used then it's probably not
+that important to have lots and lots of it.  A good rule of thumb for swap
+is that you want a minimum of 12MB of it, and the overall calculation
+should be the amount of memory you have multiplied by two.  That is to
+say that if you have 16MB of memory, then 32MB of swap is good.
+
+If you've got several drives, you can also allocate some swap on each one
+and spread the load out a little.  On my personal system, I've got 32MB of
+main memory and 64MB of swap on both drives for a total of 128MB of swap.
+This gives me 4X memory for total program swapping, which gives me the
+ability to run some pretty big programs!  Emacs and the X Window System, in
+particular, can be real swap hogs.
+
+In any case, we'll assume for the moment that we're still configuring the
+ideal system and we'll allocate 64MB of swap space, using the MEM * 2
+equation.  If you only had 8MB of memory, you'd allocate 16MB of swap
+instead.
+
+The second file system of importance is /usr, which contains further system
+binaries and all of the bundled user binaries.  /usr should be at least
+80MB in size to hold all of the important binaries, though if you plan on
+having a big /usr/local or on loading the X Window System (also known as
+XFree86 3.1) distribution then you should either create separate
+file systems for them, or you should make /usr a lot bigger.
+
+It's also possible to skip making /usr altogether and simply make a large
+root (/) file system.  Since /usr fits "underneath" /, a missing /usr won't
+cause any problems if / is large enough to hold the contents for both.  In
+any case, it's a user decision and tends to be driven by convention more
+than anything else.  For the purposes of this installation guide, we'll
+assume a 200MB /usr, 100MB of space allocated for local binaries, which
+we'll mount on /usr/local, and the rest for user home directories, which
+we'll mount on /usr/users.  Don't be put off by the size of these numbers!
+You can make a system fit into less space, but since we're dividing up the
+ideal 2GB dream disk, we might as well do it right! ;-)
+
+Getting back to the relevant part of the DISKLABEL screen again, we remember
+that it looked like this:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a         0         0         0      0  unused
+b         0         0         0      0  unused
+c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
+d         0   4108599   4108600   2006  unused          <Entire Disk>
+e         0         0         0      0  unused
+f         0         0         0      0  unused
+g         0         0         0      0  unused
+h        32    614399    614368    300  MSDOS
+
+So we'll first allocate some space on partition `a' for that root partition
+by typing `e', for (E)dit partition.  This asks us which partition we want
+to change the size of, so we type `a':
+
+Change size of which partition> a
+
+And it prompts us for the amount of space, so we'll pick 20MB for a nice
+comfortable root file system:
+
+Size of partition in MB> 20
+
+Now we see the display change to:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a   1433600   1474559     40960     20  4.2BSD
+...
+
+The system shows us where the partition starts and stops and indicates that
+it's a 4.2BSD file system, which is correct (it's really a 4.4 BSD file
+system, in actuality, but the two are similar enough to share the same
+label).
+
+We do the same for swap by typing `e' again and modify the `b' partition
+by filling in 64 for the size, to allocate 64MB of swap.
+
+Finally, remembering that `c' and `d' are special, and not for our use, we
+change the size of `e' to 200 for our future /usr, `f' to 100 for our
+/usr/local, and `g' to the rest of the disk for /usr/users.  When we're
+done, the top of the disklabel screen should look like this:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a   1433600   1474559     40960     20  4.2BSD
+b   1474560   1605631    131072     64  swap
+c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
+d         0   4108599   4108600   2006  unused          <Entire Disk>
+e   1605632   2015231    409600    200  4.2BSD
+f   2015232   2220031    204800    100  4.2BSD
+g   2220032   4108287   1888256    922  4.2BSD
+h        32    614399    614368    300  MSDOS
+
+We left `h' alone, since we actually want to be able to share files with
+our DOS partition.  At this point, we want to type `w' for (W)rite to write
+out the new size information to disk.
+
+You probably also noticed by now that "/", "/usr" and the other file system
+names we've been talking about don't appear anywhere in the above list.
+Where are they?  This brings us to the next stage, which is to (A)ssign the
+new partitions to actual file system mount points.  A file system in
+FreeBSD doesn't actually appear anywhere until we "mount" it someplace, a
+convention from the old days when disks were actually large removable packs
+that a system operator physically mounted on a large washing-machine sized
+disk drive spindle!  As you can see, not much has changed today! :-)
+
+We'll proceed then by starting at the top with the first partition and
+assigning it to the root file system (/) by typing `a', for (A)ssign, and
+then typing `a' again, for partition a:
+
+Assign which partition> a
+
+When it asks us for the name of the mount point, we type /:
+
+Directory mountpoint> /
+
+And the display adjusts accordingly to show us the new state of affairs:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a   1433600   1474559     40960     20  4.2BSD  newfs   /
+..
+
+The Action field also now shows "newfs", which means that the partition
+will be created anew.  For root file systems, this is the default and cannot
+be changed, but other partitions can be optionally "Preserved" by typing
+`p' for (P)reserve.  There are very few situations in which we'd want to do
+this, but if, say, we were actually installing a disk from an older FreeBSD
+machine which we wanted to mount into our new system but NOT erase, we
+could do it this way.  For now, let's assume that this is a new
+installation and we want all the file systems to be created from scratch.
+We thus go through and assign the rest of the file systems to their
+respective /usr, /usr/local and /usr/users mountpoints.  We also assign the
+`b' partition, which doesn't take a mountpoint (and won't prompt for one
+when we (A)ssign it), but needs us to tell it that we're ready to use it
+for swap.
+
+When we're done, the top of the screen should look something like this:
+
+Part  Start       End    Blocks     MB  Type    Action  Mountpoint
+a   1433600   1474559     40960     20  4.2BSD  newfs   /
+b   1474560   1605631    131072     64  swap    swap    swap
+c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
+d         0   4108599   4108600   2006  unused          <Entire Disk>
+e   1605632   2015231    409600    200  4.2BSD  newfs   /usr
+f   2015232   2220031    204800    100  4.2BSD  newfs	/usr/local
+g   2220032   4108287   1888256    922  4.2BSD  newfs	/usr/users
+h        32    614399    614368    300  MSDOS
+
+As a final bonus, we'll assign the DOS partition to be mounted on /dos.  We
+do this with (A)ssign as we did the others, and we also notice that the
+system is smart enough to see that it's not a FreeBSD partition and we
+DON'T want to newfs it, we want to simply mount it:
+
+h        32    614399    614368    300  MSDOS   mount   /dos
+
+At this point, our system is all set up and ready to go!
+
+We type `q' to go back to the main menu and then type `p' to (P)roceed to
+the next phase of installation.
+
+We're now given one last chance to back out of the install, and we hit
+return if we're sure, otherwise we type <Tab> to select "No" and hit return
+to consider our settings again before going on.
+
+The rest of the installation is pretty much self-explanatory.  After the
+file systems are initially created and populated, you'll be prompted to
+reboot from the hard disk.  Do so and provide the cpio floppy when asked.
+
+When the initial flurry of welcome and informational prompts has died down,
+you'll come to a screen asking you to load one or more distributions.  At
+the minimum, select "bindist" to load the basic system.  If you're loading
+from other than CDROM media, follow the appropriate paths through the
+installation process.
+
+If you're loading from CDROM, select CDROM as the media type and select the
+type of CDROM you've got (SCSI or Mitsumi).  When it asks you for an
+installation subdirectory, simply hit return if you've got the 2.0 CD from
+Walnut Creek CDROM.  You may select additional optional packages to load
+after the bindist extracts, provided that you've got the space for it.  Use
+the "?diskfree" menu option from time to time to keep an eye on your free
+space.  When you're done, you'll be asked a few more basic questions and
+then that's it!  You've got FreeBSD on your hard disk.
+
+If you should need to partition another drive or install other packages
+later, you may re-invoke the sysinstall program by typing /sbin/sysinstall.
+The same familiar prompts will then come up.
+
+Good luck!
+
+					Jordan Hubbard
+					for Walnut Creek CDROM
+					and the FreeBSD Project.
+
+
+
+
    + +&footer; + + diff --git a/en/releases/2.0/notes.sgml b/en/releases/2.0/notes.sgml new file mode 100644 index 0000000000..c9fb2a36e5 --- /dev/null +++ b/en/releases/2.0/notes.sgml @@ -0,0 +1,641 @@ + + + + %includes; +]> + +&header; + +
    +
+                                 RELEASE NOTES
+                                    FreeBSD
+                                  Release 2.0
+
+1. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD
+has changed almost entirely.  A new port from the Berkeley 4.4 code
+base was done, which brought the legal status of the system out of the
+shadows with the blessing of Novell (new owners of USL and UNIX).  The
+port to 4.4 has also brought in a host of new features, filesystems
+and enhanced driver support.  With our new unencumbered code base, we
+have every reason to hope that we'll be able to release quality
+operating systems without further legal encumbrance for some time to
+come!
+
+FreeBSD 2.0 represents the culmination of almost 2 years of work and
+many thousands of man hours put in by an international development team.
+We hope you enjoy it!
+
+Many packages have also been upgraded or added, such as XFree86 3.1,
+xview 3.2, elm, nntp, mh, InterViews and dozens of other miscellaneous
+utilities have been ported and are now available as add-ons.  See the
+ports collection (or the package collection) for a complete summary.
+
+For a list of contributors, please see the file "CONTRIB.FreeBSD",
+which should be bundled with your bindist distribution.
+
+Also see the new "REGISTER.FreeBSD" file for information on registering
+with the "Free BSD user counter".  We've also provided a list of who's
+responsible for what (so that you may query them directly) in the
+"ROSTER.FreeBSD" file; use of this file is encouraged to ensure faster
+resolution of any problems you may have!
+
+The core of FreeBSD does not contain DES code which would inhibit its
+being exported outside the United States.  There is an add-on package
+to the core distribution, for use only in the United States, that
+contains the programs that normally use DES.  The auxilliary packages
+provided separately can be used by anyone.   A freely (from outside the
+U.S.) exportable European distribution of DES for our non U.S. users also
+exists and is described in the FreeBSD FAQ.
+
+If password security for FreeBSD is all you need, and you have no
+requirement for copying encrypted passwords from different hosts (Suns,
+DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5
+based security may be all you require!  We feel that our default security
+model is more than a match for DES, and without any messy export issues
+to deal with.  If you're outside (or even inside) the U.S., give it a try!
+
+
+1.1 What's new in 2.0?
+----------------------
+
+4.4 Lite
+--------
+As previously stated, this release is based entirely on CSRG's
+latest (and last) BSD release - 4.4 Lite.  This features a number
+of improvements over 4.2BSD (Net/2), not least of which are:
+
+o       Legal approval of Novell & U.C. Berkeley.  After the settlement
+        of the longstanding lawsuit between USL/UCB/Novell/BSDI, all
+        parties were (strongly) encouraged to move to 4.4 Lite in order
+        to avoid future legal entanglements.  The fact that we've now done
+        so should make this release much more attractive to potential
+        commercial users.
+
+o       Many new filesystem types, such as stackable filesystems, union
+        filesystems, "portals", kernfs, a simple log-structured filesystem, a
+        new version of NFS (NQNFS), etc.  While some of these new filesystems
+        are also rather unpolished and will require significant additional
+        work to be truly robust, they're a good start.
+
+o       64bit offsets, allowing filesystems of up to 2^63 bytes in size.
+
+o       Further work towards full POSIX compliance.
+
+IP multicast support
+--------------------
+The IP multicast support has been upgraded from the woefully ancient
+1.x code in 4.4-Lite to the most current and up-to-date 3.3 release
+from Steve D. and Ajit.  The non-forwarding code is known to work (for
+some limited test cases).  The multicast forwarder and user-mode
+multicast routing process are known to compile, but have not been
+significantly tested (hopefully this will happen before 2.0 release).
+
+Owner:                  wollman
+Sources involved:       sys/netinet, usr.sbin/mrouted
+
+Loadable Kernel Modules
+-----------------------
+David Greenman incorporated NetBSD's port of Terry Lambert's loadable
+kernel module support.  Garrett Wollman wrote the support for loadable
+file systems, and Søren Schmidt did the same for loadable execution
+classes.
+
+Owner:                  core
+Sources involved:       sys/kern, sbin/modload, sbin/modunload,
+                        usr.bin/modstat
+
+
+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 getvfsbyname(3)
+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
+the following current restrictions:
+
+        - /usr/bin may not reside on a dynamically loaded filesystem.
+        - There must be a writable /tmp directory available
+          before filesystems are loaded (moving / to the top of your
+          /etc/fstab file will accomplish this).
+        - Some of the more esoteric filesystems simply don't work when loaded
+          dynamically (though they often don't work "static", either.)
+
+Owner:                  wollman
+Sources involved:       sys/*fs, lkm/*fs, usr.bin/lsvfs, lib/libc/gen
+
+
+S/Key
+-----
+Since version 1.1.5, FreeBSD has supported the S/Key one time password
+scheme.  The version used is derived from the logdaemon package of Wietse
+Venema.
+Some of the features new in 2.0 are:
+        - New access control table format to impose the use of S/Keys
+          based on: hostname, ip address, port, username, group id.
+        - S/Key support can be disabled by not having the access control
+          table.
+The second item explains the absence of skey.access in the installed /etc.
+To enable S/Key support, create a file skey.access in /etc and fill it
+according to your needs. See also skey.access(5) and the example in
+/usr/share/examples/etc/skey.access.
+
+Owner:                  pst, guido
+Sources involved:       lib/libskey, usr.bin/key* (plus patches to others)
+
+
+TCP/IP over parallel (printer) port
+-----------------------------------
+You can now run TCP/IP over a standard LapLink(tm) cable, if both ends
+have an interrupt-driven printerport.  The interface is named "lp0"
+where '0' is the same as the lpt# unit number.  This is not compatible
+with PLIP.  If you run NFS, try setting MTU to 9180, otherwise leave
+it at 1500 unless you have a good reason to change it.  Speed varies
+with the CPU-type, with up to 70 kbyte/sec having been seen and 50
+kbyte/sec being the norm.
+
+Owner:                  phk
+Sources involved:       isa/lpt.c
+
+
+ProAudioSpectrum SCSI driver
+----------------------------
+If you have a PAS board with a CD-ROM, and the MS-DOS driver is called
+TSLCDR.SYS, then the "pas" driver should work on your card.  You can
+attach disks, cdroms and tapes, but due to the nature of the hardware
+involved, the transfer rate is limited to < 690 kbyte/sec.  For CD-ROM
+use, this is generally more than enough.
+
+Owner:                  phk
+Sources involved:       isa/pas.c
+
+
+Adaptec 2742/2842 SCSI driver
+-----------------------------
+Despite the non-cooperation of Adaptec in providing technical
+information, we now have a driver for the AHA-274x and AHA-284x
+series SCSI controller family.  This driver uses the GPL'd
+Linux sequencer code, so until we find an alternative, this
+will be part of the kernel that requires source code to be
+distributed with it at all times.  This shouldn't be a problem
+for any of FreeBSD's current users.
+
+Owner:                  gibbs
+Sources involved:       isa/aic7770.c sys/gnu/misc/*
+
+
+Gzip'd binaries
+----------------
+We have an experimental implementation for direct execution of gzip'ed
+binaries in this release.  When enabled, it allows you to simply gzip
+your binaries, remove the '.gz' extension and make the file
+executable.  There is a big speed and memory consumption penalty for
+doing this, but for laptop users it may be worthwhile.  The maximum
+savings are generally around 10 Mb of disk space.
+
+Owner:                  phk
+Sources involved:       kern/imgact_gzip.c kern/inflate.c
+
+
+Diskless booting
+----------------
+
+Diskless booting in 2.0 is much improved since 1.1.5.  The
+boot-program is in src/sys/i386/boot/netboot, and can be run from an
+MSDOS system or burned into an EPROM.  Local swapping is also
+possible.  WD, SMC, 3COM and Novell ethernet cards are currently
+supported.
+
+Owner:                  Martin Renters & phk
+Sources involved:       i386/boot/netboot, sys/nfs/nfs_vfsops.h
+
+
+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 sysctl(3) management interface.  Current
+applications include lsdev(8), which lists the currently configured
+devices.  In the future, we expect to use this code to automatically
+generate a configuration file for you at installation time.
+
+Owner:                  wollman
+Sources involved:       sys/i386, sys/scsi, sys/kern/kern_devconf.c,
+                        sys/sys/devconf.h, usr.sbin/lsdev
+
+
+Kernel management interface
+---------------------------
+With 4.4-Lite, we now have a better management interface for the endless
+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 sysctl(1) program.  In addition to the standard 4.4BSD MIB variables,
+we have added support for YP/NIS domains (kern.domainname), controlling
+the update daemon (kern.update), retrieving the OS release date
+(kern.osreldate), determining the name of the booted kernel (kern.bootfile),
+and checking for hardware floating-point support (hw.floatingpoint).
+We have also added support to make management queries of devices and
+filesystems.
+
+Owner:                  core
+Sources involved:       sys, usr.bin/sysctl
+
+
+iBCS2 support
+-------------
+FreeBSD now supports running iBCS2 compatible binaries (currently
+SCO UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).
+The iBCS2 emulator is in its early stages, but it is functional, we
+haven't been able to do exhaustive testing (lack of commercial apps),
+but almost all of SCO's 3.2.2 binaries are working, so is an old
+INFORMIX-2.10 for SCO. Further testing is nessesary to complete this
+project. There is also work under way for ELF & XOUT loaders, and
+most of the svr4 syscall wrappers have been written.
+
+Owner:                  Soren Schmidt (sos) & Sean Eric Fagan (sef)
+Sources involved:       sys/i386/ibcs2/* + misc kernel changes.
+
+
+2. Supported Configurations
+---------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+Following is a list of all currently known disk controllers and
+ethernet cards known to work with FreeBSD.  Other configurations may
+very well work, and we have simply not received any indication of
+this.
+
+
+2.1. Disk Controllers
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+[Note: the new Extended IDE controllers in newer PC's work, although no
+extended features are used.]
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 2742/2842 series ISA/EISA SCSI controllers
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the Soundblaster cards
+as they have no on-board BIOS, which is necessary for mapping
+the boot device into the system BIOS I/O vectors.
+They're perfectly usable for external tapes, CDROMs, etc,
+however.  The same goes for any other AIC-6x60 based card
+without a boot ROM.  Some systems DO have a boot ROM, which
+is generally indicated by some sort of message when the system
+is first powered up or reset.  Check your system/board documentation
+for more details.
+
+[Note that Buslogic was formerly known as "Bustec"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+
+NCR 53C810 and 53C825 PCI SCSI controller.
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+DAT) and CD ROM drives.  Note: This and the mcd driver (Mitsumi CDROM
+interface card) are the only way a CD ROM drive may be currently
+attached to a FreeBSD system; we do not support SoundBlaster
+(non-SCSI) CDROM interface, or other "non-SCSI" adapters.  The
+ProAudio Spectrum SCSI and SoundBlaster SCSI controllers are
+supported.
+
+Some controllers have limitations with the way they deal with >16MB of
+memory, due to the fact that the ISA bus only has a DMA address space of
+24 bits.  If you do your arithmetic, you'll see that this makes it
+impossible to do direct DMA to any address >16MB.  This limitation is
+even true of some EISA controllers (which are normally 32 bit) when
+they're configured to emulate an ISA card, which they then do in *all*
+respects.  This problem is avoided entirely by IDE controllers (which do
+not use DMA), true EISA controllers (like the UltraStor or Adaptec
+1742A) and most VLB (local bus) controllers.  In the cases where it's
+necessary, the system will use "bounce buffers" to talk to the
+controller so that you can still use more than 16Mb of memory without
+difficulty.
+
+
+2.2. Ethernet cards
+
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509 and 3C579 Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+2.3. Misc
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+STB 4 port card using shared IRQ.
+
+Mitsumi (all models) CDROM interface and drive.
+
+Soundblaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
+
+Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
+support is apparently close to materializing.  Details will be posted
+as the situation develops.
+
+
+3. Obtaining FreeBSD.
+---------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+1. FTP/Mail
+
+You can ftp FreeBSD and any or all of its optional packages from
+`freebsd.cdrom.com' - the offical FreeBSD release site.
+
+For other locations that mirror the FreeBSD software see the file
+MIRROR.SITES.  Please ftp the distribution from the nearest site
+to you netwise.
+
+If you do not have access to the internet and electronic mail is your
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
+to get more information on how to fetch files from freebsd.cdrom.com.
+Note: This approach will end up sending many *tens of megabytes*
+through the mail, and should only be employed as an absolute LAST
+resort!
+
+
+2. CDROM
+
+FreeBSD 2.0 may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
+
+Or via the internet from orders@cdrom.com.  Their current catalog can
+be obtained via ftp as ftp.cdrom.com:/cdrom/catalog.
+
+Cost is $39.95.  Shipping (per order not per disc) is $5 in the US, Canada,
+or Mexico and $10.00 overseas.  They accept Visa, Mastercard, American
+Express, and ship COD to the United States.  California residents please
+add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD,
+you need to contact the FreeBSD team for that.  Please see section 5 for
+more information.
+
+
+4. Preparing for the installation.
+----------------------------------
+
+1. Floppy Installation
+
+If you must install from floppy disks, either due to space contraints
+on your hard disk or just because you enjoy doing things the hard
+way, you must first prepare some floppies for the install.
+
+You will need either 10 1.44MB floppies or 12 1.2MB floppies to
+store just the bindist (binary distribution).  These *must* be
+formatted using MS-DOS, using either the FORMAT command in MS-DOS
+or the File Manager in Microsoft Windows to prepare the floppies
+(though factory preformatted floppies will also well well, provided
+that they haven't been previously used for something else).
+
+After you've formatted the floppy disks, you'll need to copy the
+files onto them.  There are 56 total files for the bindist itself,
+plus three small files (CKSUMS, do_cksum.sh, and extract.sh) for
+the install program to use.  ALL of these files must be copies onto
+the floppies.  Each of the bindist files are named "bindist.??",
+where the "??" is replaced by the letter sequence aa through cd.
+Copy these files onto the floppies, placing the three small install
+files onto the final floppy.  The order in which you copy the files
+to floppy is not important, but it makes labelling the disks easier
+if you go in some sort of alphabetical order.
+
+After you've done this, the floppy disks are ready for the install
+program to use.
+
+Later on, after you get the binary distribution installed and everything
+is going great, the same instructions will apply for the other
+distributions, such as the manpages distribution or the XFree86 distribution.
+The number of floppies required will, of course, change for bigger or
+smaller distributions.
+
+
+2. Hard Disk Installation
+
+To prepare for installation from an MS-DOS partition, you should simply
+copy the files from the distribution into a directory with the same
+name as the distribution.  For example, if you are preparing to
+install the bindist set, then make a directory on your C: drive named
+C:\BINDIST and copy the files there.  This will allow the installation
+program to find the files automatically.
+
+
+3. QIC/SCSI Tape Installation.
+
+Installing from tape is probably the easiest method, short of an
+on-line install using ftp or installing from a CDROM.  The installation
+program expects the files to be simply tar'red onto the tape, so after
+getting all of the files for distribution you're interested in, simply
+tar them onto the tape with something like:
+
+        cd <where the *.?? files are>
+        tar cvf /dev/rwt0 (or /dev/rst0) .
+
+from a directory with just the distribution files in it.  Make sure
+that you remember to put CKSUMS, do_cksum.sh, and extract.sh files
+in this directory as well!
+
+If you wish to install multiple *dist releases from one tape, do the
+following:
+
+1. cd to the parent directory of the distributions and put them on tape
+   like so:
+                tar cvf /dev/rwt0 (or /dev/rst0) bindist srcdist ...
+
+2. Install the first distribution on the tape using the tape installation
+   method as normal.  Afterwards, *do not* erase the contents of the temporary
+   directory.  Get a shell with ESC-ESC and cd to the temporary directory
+   yourself.  For each additional *dist you want to load, cd to its
+   subdirectory and type `sh ./extract.sh'.
+
+
+5. Reporting problems, making suggestions, submitting code.
+-----------------------------------------------------------
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached if you can!).
+
+The preferred method to submit bug reports from a machine with internet
+mail connectivity is to use the send-pr command.  Bug reports will be
+dutifully filed by our faithful bugfiler program and you can be sure
+that we'll do our best to respond to all reported bugs as soon as
+possible.
+
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                questions@FreeBSD.org
+
+Additionally, being a volunteer effort, we are always happy to have
+extra hands willing to help - there are already far more enhancements
+to be done than we can ever manage to do by ourselves!  To contact us
+on technical matters, or with offers of help, you may send mail to:
+
+                hackers@FreeBSD.org
+
+Since these mailing lists can experience significant amounts of
+traffic, if you've got slow or expensive mail access and you're
+only interested in keeping up with significant FreeBSD events, you may
+find it preferable to subscribe to:
+
+                announce@FreeBSD.org
+
+
+All but the FreeBSD-bugs groups 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
+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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If your
+name is not mentioned, please be assured that its omission is entirely
+accidental.
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his extensive work with 386BSD.
+
+The FreeBSD "core" team:
+
+        Andrew A. Chernov
+        John Dyson
+        Bruce Evans
+        David Greenman
+        Rodney W. Grimes
+        Jordan K. Hubbard
+        Poul-Henning Kamp
+        Rich Murphey
+        Gary Palmer
+        Geoff Rehmet
+        Paul Richards
+        Soren Schmidt
+        Andreas Schulz
+        Jack Vogel
+        Garrett A. Wollman
+
+
+Special mention to:
+
+        Robert Bruce and Jack Velte of Walnut Creek CDROM, without
+        whose help (and continuing support) this release would never
+        have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        The NetBSD group for their frequent assistance and commentary.
+
+        Additional FreeBSD helpers and beta testers:
+
+        J.T. Conklin                            Julian Elischer
+        Sean Eric Fagan                         Jeffrey Hsu
+        Terry Lambert                           L Jonas Olsson
+        Chris Provenzano                        Dave Rivers
+        Guido van Rooij                         Steven Wallace
+        Atsushi Murai                           Scott Mace
+        Andrew Moore                            Nate Williams
+
+        And everyone at Montana State University for their initial support.
+
+
+Thanks to everyone, especially those not mentioned, and we sincerely
+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 
+
+
    + +&footer; + + diff --git a/en/releases/2.0A/Makefile b/en/releases/2.0A/Makefile new file mode 100644 index 0000000000..4881405b5a --- /dev/null +++ b/en/releases/2.0A/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml + +.include "../../web.mk" diff --git a/en/releases/2.0A/announce.sgml b/en/releases/2.0A/announce.sgml new file mode 100644 index 0000000000..bc27a6cc51 --- /dev/null +++ b/en/releases/2.0A/announce.sgml @@ -0,0 +1,114 @@ + + + + %includes; +]> + +&header; + +

    To: hackers@freefall.cdrom.com
    +Subject: For those that didn't see this in announce - 2.0 ALPHA is released!
    +Date: Thu, 10 Nov 1994 01:31:42 -0800
    +From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>

    + +

    The FreeBSD Project team is very pleased to announce their release of +FreeBSD 2.0 ALPHA; a full 32 bit 4.4 BSD Lite based operating system +for Intel PCs (i386, i486 and Pentium class).

    + +

    Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD has +changed almost entirely. A new port from the Berkeley 4.4 code base +was done, which brought the legal status of the system out of the +shadows with the blessing of Novell (new owners of USL and UNIX). The +port to 4.4 also brought in a host of new features, filesystems and +enhanced driver support. With our new unencumbered code base, we have +every reason to hope that we'll be able to release quality operating +systems without further legal encumbrance for some time to come!

    + +

    FreeBSD 2.0 represents the culmination of almost 2 years of work and +many thousands of man hours put in by an international development +team. We hope you enjoy it!

    + +

    FreeBSD 2.0 ALPHA also features an advanced installation that enables +one to install from tape, CD, SLIP or ethernet (NFS or FTP). FreeBSD +2.0 BETA, planned for the 2nd week of November, will also support +installation from floppy or DOS partition (sorry, it didn't quite make +the ALPHA!) and offer even more "plug-n-play" features for editing +disklabels and such. This is, nonetheless, our easiest to use +installation yet, and we hope that with your feedback and suggestions, +our final 2.0 Release version will be even nicer still!

    + +

    For more information on what's new with FreeBSD, or what general +features it offers, we strongly suggest that you simply download our +boot floppy and boot from it. You can easily read the release notes +on it using a simple menu, and with no danger to the contents of your +hard disk (unless you deliberately chose "proceed with installation", +in which case your fate is in your own hands! :-).

    + +

    Those truly wishing to wait for the final release version of 2.0 are, +of course, encouraged to do so, but I think that many of you will find +this to be our most polished "ALPHA" release yet! Give it a try! An +upgrade path from ALPHA->RELEASE will also be provided, and we do NOT +plan any major changes between now and the final release in December. +We generally try to err on the side of conservatism in our releases, +and the 2.0 release cycle is no exception. Those wishing to obtain +2.0 on CDROM will have to wait until the 2.0 Release date, at which +point it will be made available by Walnut Creek CDROM (info@cdrom.com) +and other CDROM publishers.

    + +

    If you're currently running 1.x and are looking for an upgrade path, +we're sorry to say that only full installations are supported at this +time. Simply back up your password and user files before reinstalling +from the 2.0 media, then bring them back. If public demand is high +enough, and we can figure out a way of easily doing it, we'll offer +something, but it should be understood that the differences between +1.x and 2.0 are large, and it's not certain that we'll be able to do +it at all.

    + +

    Those unable or unwilling to download the boot floppy may also get the +release notes by mail - send mail to <info@FreeBSD.org> for an +automated reply. Updated information will also be provided on a more +or less continuous basis in our WEB pages

    + +

    FreeBSD 2.0A is available for ftp in ftp://ftp.freebsd.org/pub/FreeBSD/2.0-ALPHA/

    + +

    It will also, no doubt, be available on a number of mirror sites as +soon as they pick it up. However, ftp.freebsd.org is on a T3 line and +supports 300 simultaneous users (it's a FreeBSD machine :-), so it's +unlikely that you'll have too much trouble getting it from this site +until the mirrors do so.

    + +

    If you are directly Internet connected, it is also NOT necessary to +load the bindist from this site! Simply download the 2 boot floppies, +begin the installation, and select the FTP installation method - it +will do the rest for you, transparently.

    + +

    Finally, we'd like to publically thank Walnut Creek CDROM, without whos +continuing support and extreme generousity, we'd probably be long +gone! They've been of immense help to us. Thank you, Walnut +Creek CDROM!

    + +

    Thanks must also go to Poul-Henning Kamp, our fearless and long +suffering release engineer for 2.0. While all of us have sacrificed +much sleep to the cause, he has a new wife but has somehow managed to +do so as well! :-)

    + +

    And to all of our users (this is probably starting to sound like the +academy awards :-), a similar thank you! We couldn't have done it +without your constant flow of commentary, patches, donations of code +and moral support. As corny as it sounds, we do it all for you folks! +[Though the ego gratification is nice too :-)]

    + +

    Thanks to all, and we sincerely hope you enjoy this release!

    + +

    Comments, as always, to hackers@FreeBSD.org.

    + + +

    Jordan
    + [on behalf of the FreeBSD Project team] +

    + +&footer; + + diff --git a/en/releases/2.1.5R/Makefile b/en/releases/2.1.5R/Makefile new file mode 100644 index 0000000000..517e40e9d3 --- /dev/null +++ b/en/releases/2.1.5R/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml notes.sgml + +.include "../../web.mk" diff --git a/en/releases/2.1.5R/announce.sgml b/en/releases/2.1.5R/announce.sgml new file mode 100644 index 0000000000..d90dc6c9c7 --- /dev/null +++ b/en/releases/2.1.5R/announce.sgml @@ -0,0 +1,269 @@ + + + + %includes; +]> + +&header; + +

    FreeBSD +2.1.5-RELEASE is now available on ftp.freebsd.org and various +FTP mirror sites throughout the world. It can also be ordered on +CD from +from Walnut Creek CDROM.

    + +

    FreeBSD 2.1.5 represents the culmination of over a year's worth of +work on the 2.1-STABLE branch of +FreeBSD since it began with FreeBSD 2.0.5. In the 7 months since 2.1 +was released, many many bug fixes, updates and careful enhancements +have been made, the results of which you now see here.

    + +

    The STABLE branch was conceived out of the need to allow FreeBSD to +grow and support long-term development projects (like devfs, NFSv3, +IPX, PCCARD, etc.) while at the same time not jeopardizing the +stability of its existing user base. FreeBSD 2.1.5 marks the finishing +point for that effort and, barring any small "slipstream" releases done +to solve significant problems, no further releases along the 2.1-STABLE +branch are anticipated. The concept of "stable" and "experimental" +tracks is not being abandoned, we'll simply be doing this somewhat +differently in the future.

    + +

    For more information on the 2.1.5 release itself, please consult the +Release Notes. + +

    The official sources for FreeBSD are available via anonymous FTP from: + + ftp.freebsd.org. + +Or via the WEB at: + + www.freebsd.org. + +And on CD-ROM from Walnut Creek CDROM: + +

    +     Walnut Creek CDROM
+     4041 Pike Lane, #D
+     Concord CA, 94520 USA
+     Phone: +1 510 674-0783
+     Fax: +1 510 674-0821
+     Tech Support: +1 510 603-1234
+     Email: info@cdrom.com
+     WWW: http://www.cdrom.com
+
    + + +

    Additionally, FreeBSD is available via anonymous FTP from the +following mirror sites. If you choose to obtain FreeBSD via anonymous +FTP, please try to use a site near you:

    + +

    Australia

    +

    In case of problems, please contact hostmaster@au.freebsd.org. +

    + +

    Brazil

    +

    In case of problems, please contact hostmaster@br.freebsd.org. +

    + +

    Canada

    +

    In case of problems, please contact hostmaster@ca.freebsd.org +

    + + +

    Czech Republic

    + + +

    Estonia

    +

    In case of problems, please contact hostmaster@ee.freebsd.org. +

    + + +

    Finland

    +

    In case of problems, please contact hostmaster@fi.freebsd.org. +

    + +

    France

    + + + +

    Germany

    +

    In case of problems, please contact hostmaster@de.freebsd.org. +

    + +

    Hong Kong

    + + +

    Ireland

    +

    In case of problems, please contact hostmaster@ie.freebsd.org. +

    + + +

    Israel

    + + + +

    Japan

    +

    In case of problems, please contact hostmaster@jp.freebsd.org. +

    + +

    Korea

    +

    In case of problems, please contact hostmaster@kr.freebsd.org. +

    + +

    Netherlands

    +

    In case of problems, please contact hostmaster@nl.freebsd.org. +

    + +

    Poland

    + + + +

    Portugal

    + + + +

    Russia

    +

    In case of problems, please contact hostmaster@ru.freebsd.org. +

    + +

    South Africa

    +

    In case of problems, please contact hostmaster@za.freebsd.org. +

    + +

    Sweden

    +

    In case of problems, please contact the hostmaster@se.freebsd.org. +

    + +

    Taiwan

    +

    In case of problems, please contact hostmaster@tw.freebsd.org. +

    + +

    Thailand

    + + + +

    USA

    +

    In case of problems, please contact hostmaster@freebsd.org. +

    + + +

    UK

    +

    In case of problems, please contact hostmaster@uk.freebsd.org. +

    + + +

    The latest versions of export-restricted code for FreeBSD (2.0C or +later) (eBones and secure) are being made available at the following +locations. If you are outside the U.S. or Canada, please get secure +(DES) and eBones (Kerberos) from one of the following foreign +distribution sites: + +

    South Africa

    + + +

    Brazil

    + + +

    Finland

    + + +&footer; + + diff --git a/en/releases/2.1.5R/notes.sgml b/en/releases/2.1.5R/notes.sgml new file mode 100644 index 0000000000..e17341b9b0 --- /dev/null +++ b/en/releases/2.1.5R/notes.sgml @@ -0,0 +1,544 @@ + + + + %includes; +]> + +&header; + +
    +                                 RELEASE NOTES
+                             FreeBSD 2.1.5 RELEASE
+
+0. What is this release?
+------------------------
+FreeBSD 2.1.5R is the follow-on release to 2.1R and focuses primarily
+on fixing bugs, closing security holes and conservative enhancements.
+For more information on bleeding-edge development, please see
+http://www.freebsd.org/handbook/current.html.
+
+
+1. What's New since 2.1.0-RELEASE?
+----------------------------------
+Quite a few things have changed since the last major release
+of FreeBSD.  To make it easier to identify specific changes,
+we've broken them into several major categories:
+
+
+Device Drivers:
+---------------
+Support for the Adaptec AIC7850 on-board SCSI adapter.
+
+Support for Specialix SI and XIO serial cards.
+
+Support for the Stallion EasyIO, EasyConnection 8/32 and
+EasyConnection 8/64, as well as the older Onboard and Brumby serial
+cards.
+
+Support for the Intel EtherExpress Pro/100B PCI ethernet card.
+
+Real PCI Buslogic support (new driver and probing order).
+
+Support for the ARNET (now Digiboard) Sync 570i high-speed serial card.
+
+Better support for the Matrox Meteor frame grabber card.
+
+Support for the Connectix Quickcam (parallel port camera).
+
+Worm driver - it is now possible to burn CDROMs using the Plasmon or
+HP 4080i CDR drives (see `wormcontrol(1)').  NOTE: If your drive
+probes as a CD rather than a WORM, some additional patches may be
+required from -current to get it working for you.  We decided not to
+bring these changes over by default as they make too many changes to
+the SCSI subsystem (not necessarily bad changes, but more risky).
+
+
+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 ccd(4) for more information.
+
+Real PCI bus probing (before ISA) and support for various PCI bridges.
+
+The Linux emulation is now good enough to run the Linux version of
+Netscape, with JAVA support (as well as a number of other Linux
+utilities).
+
+
+
+Userland code updates:
+----------------------
+
+The system installation tool has been revamped with slightly different
+menu behavior and a number of bugs have been fixed.  It's hoped that
+this installation will be more intuitive for new users than previous
+ones (feedback welcomed, of course) as well as more useful in the
+post-install scenario (I know, I keep saying this :-).
+
+Many improvements to the NIS code.
+
+The ncftp program is no longer part of the default system - it has been
+replaced by a library (/usr/src/lib/libftpio) and a more powerful program
+which uses it called ``fetch'' (/usr/src/usr.bin/fetch).  You may find
+ncftp as part of the ports collection (in /usr/ports/net/ncftp) if you
+still wish to use it, though fetch is slightly more capable in that
+it can fetch from both FTP and HTTP servers (ftp://... or http://... URLs).
+See the man page for more details.
+
+
+2. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our release of FreeBSD 2.0 over a year ago, the performance,
+feature set and stability of FreeBSD has improved dramatically.  The
+largest change is a revamped VM system with a merged VM/file buffer
+cache that not only increases performance but reduces FreeBSD's memory
+footprint, making a 5MB configuration a more acceptable minimum.
+Other enhancements include full NIS client and server support,
+transaction TCP support, dial-on-demand PPP, an improved SCSI
+subsystem, early ISDN support, support for FDDI and Fast Ethernet
+(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
+narrow) and 3940 SCSI adaptors along with many hundreds of bug fixes.
+
+We've taken the comments and suggestions of many of our users to
+heart and have attempted to provide what we hope is a more sane and
+easily understood installation process.  Your feedback on this
+(constantly evolving) process is especially welcome!
+
+In addition to the base distributions, FreeBSD offers a new ported
+software collection with over 450 commonly sought-after programs.  The
+list of ports ranges from http (WWW) servers, to games, languages,
+editors and almost everything in between.  The entire ports collection
+requires only 10MB of storage, all ports being expressed as "deltas"
+to their original sources.  This makes it much easier for us to update
+ports and greatly reduces the disk space demands made by the ports
+collection.  To compile a port, you simply change to the directory of
+the program you wish to install, type make and let the system do the
+rest.  The full original distribution for each port you build is
+retrieved dynamically off of CDROM or a local ftp site, so you need
+only enough disk space to build the ports you want.  (Almost) every
+port is also provided as a pre-compiled "package" which can be
+installed with a simple command (pkg_add).  See also the new Packages
+option in the Configuration menu for an especially convenient interface
+to the package collection.
+
+
+A number of additional documents which you may find helpful in the
+process of installing and using FreeBSD may now also be found in the
+/usr/share/doc directory.  You may view the manuals with any HTML
+capable browser by saying:
+
+  To read the handbook:
+      <browser> file:/usr/share/doc/handbook/handbook.html
+
+  To read the FAQ:
+      <browser> file:/usr/share/doc/FAQ/freebsd-faq.html
+
+You can also visit the master (and most frequently updated) copies at
+http://www.freebsd.org.
+
+The export version of FreeBSD does not contain DES code which would
+inhibit its being exported outside the United States.  There is an
+add-on package to the core distribution which contains the programs
+and libraries that normally use DES.  A freely exportable (from
+outside the U.S.)  distribution of DES for our non-U.S. users also
+exists at ftp://ftp.internat.freebsd.org/pub/FreeBSD.
+
+If password security for FreeBSD is all you need and you have no
+requirement for copying encrypted passwords from different hosts
+(Suns, DEC machines, etc) into FreeBSD password entries, then
+FreeBSD's MD5 based security may be all you require!  We feel that our
+default security model is more than a match for DES, and without any
+messy export issues to deal with.  If you're outside (or even inside)
+the U.S., give it a try!  This snapshot also includes support for
+mixed password files - either DES or MD5 passwords will be accepted,
+making it easier to transition from one scheme to the other.
+
+
+3. Supported Configurations
+---------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium Pro class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+What follows is a list of all disk controllers and ethernet cards
+currently known to work with FreeBSD.  Other configurations may also
+work, but we have simply not received any confirmation of this.
+
+
+3.1. Disk Controllers
+---------------------
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+IDE
+ATA
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
+controllers.
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+Adaptec AIC7850 on-board SCSI controllers.
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards as they have no
+   on-board BIOS, such being necessary for mapping the boot device into the
+   system BIOS I/O vectors.  They're perfectly usable for external tapes,
+   CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
+   without a boot ROM.  Some systems DO have a boot ROM, which is generally
+   indicated by some sort of message when the system is first powered up
+   or reset, and in such cases you *will* also be able to boot from them.
+   Check your system/board documentation for more details.
+
+[Note that Buslogic was formerly known as "Bustec"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+Buslogic 946c PCI SCSI controller
+Buslogic 956c PCI SCSI controller
+
+NCR 53C810 and 53C825 PCI SCSI controller.
+NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+WD7000 SCSI controller.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+DAT) and CD ROM drives.
+
+The following CD-ROM type systems are supported at this time:
+(cd)    SCSI interface (also includes ProAudio Spectrum and
+        SoundBlaster SCSI)
+(mcd)   Mitsumi proprietary interface (all models)
+(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
+        interface (562/563 models)
+(scd)   Sony proprietary interface (all models)
+(wcd)   ATAPI IDE interface (experimental and should be considered ALPHA
+        quality!).
+
+
+3.2. Ethernet cards
+-------------------
+
+Allied-Telesis AT1700 and RE2000 cards
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21040, DC21041, or DC21140 based NICs (SMC???? DE???)
+DEC FDDI (DEFPA/DEFEA) NICs
+Fujitsu MB86960A/MB86965A
+
+Intel EtherExpress (not recommended due to driver instability)
+Intel EtherExpress Pro/100B PCI Fast Ethernet
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+Note that NO token ring cards are supported at this time as we're
+still waiting for someone to donate a driver for one of them.  Any
+takers?
+
+
+3.3. Misc
+---------
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+ARNET (now Digiboard) Sync 570/i high-speed serial.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+SDL Communications Riscom/8 Serial Board.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
+
+
+
+4. Obtaining FreeBSD
+--------------------
+
+You may obtain FreeBSD in a variety of ways:
+
+4.1. FTP/Mail
+
+You can ftp FreeBSD and any or all of its optional packages from
+`ftp.freebsd.org' - the official FreeBSD release site.
+
+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 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
+only recourse, then you may still fetch the files by sending mail to
+`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
+to get more information on how to fetch files using this mechanism.
+Please do note, however, that this will end up sending many *tens of
+megabytes* through the mail and should only be employed as an absolute
+LAST resort!
+
+
+4.2. CDROM
+
+FreeBSD 2.1-RELEASE and these 2.2 SNAPSHOT CDs may be ordered on CDROM from:
+
+        Walnut Creek CDROM
+        4041 Pike Lane, Suite D
+        Concord CA  94520
+        1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
+
+Or via the internet from orders@cdrom.com or http://www.cdrom.com.
+Their current catalog can be obtained via ftp as:
+        ftp://ftp.cdrom.com/cdrom/catalog.
+
+Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
+FreeBSD 2.2-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription
+(-RELEASE and -SNAP subscriptions are entirely seperate).  With a
+subscription, you will automatically receive updates as they are released.
+Your credit card will be billed when each disk is shipped and you may cancel
+your subscription at any time without further obligation.
+
+Walnut Creek CDROM also sells a full line of FreeBSD related
+merchandise such as T-shirts ($14.95, available in "child", Large and
+XL sizes), coffee mugs ($9.95), tattoos ($0.25 each) and posters
+($3.00).
+
+Shipping (per order not per disc) is $5 in the US, Canada or Mexico
+and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
+Express or checks in U.S. Dollars and ship COD within the United
+States.  California residents please add 8.25% sales tax.
+
+Should you be dissatisfied for any reason, the CD comes with an
+unconditional return policy.
+
+
+Reporting problems, making suggestions, submitting code
+-------------------------------------------------------
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached, if you can!).
+
+The preferred method to submit bug reports from a machine with
+internet mail connectivity is to use the send-pr command.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.  Bugs filed in this way are also visible on our WEB site
+in the support section and are therefore valuable both as bug reports
+and as "signposts" for other users concerning potential problems to
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                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:
+
+                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:
+
+                announce@FreeBSD.org
+
+
+All but the freebsd-bugs groups 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
+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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If you've
+contributed something substantive to us and your name is not mentioned
+here, please be assured that its omission is entirely accidental.
+Please contact hackers@FreeBSD.org for any desired updates to the
+lists that follow:
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his initial work with 386BSD.
+
+The FreeBSD Core Team
+(in alphabetical order by last name):
+
+        Satoshi Asami <asami@FreeBSD.org>
+        Andrey A. Chernov <ache@FreeBSD.org>
+        John Dyson <dyson@FreeBSD.org>
+        Bruce Evans <bde@FreeBSD.org>
+        Justin Gibbs <gibbs@FreeBSD.org>
+        David Greenman <davidg@FreeBSD.org>
+        Jordan K. Hubbard <jkh@FreeBSD.org>
+        Poul-Henning Kamp <phk@FreeBSD.org>
+        Rich Murphey <rich@FreeBSD.org>
+        Gary Palmer <gpalmer@FreeBSD.org>
+        Søren Schmidt <sos@FreeBSD.org>
+        Peter Wemm <peter@FreeBSD.org>
+        Garrett A. Wollman <wollman@FreeBSD.org>
+        Jörg Wunsch <joerg@FreeBSD.org>
+
+
+The FreeBSD Development Team, excluding core team members
+(in alphabetical order by last name):
+
+        Ugen J.S. Antsilevich <ugen@FreeBSD.org>
+        Torsten Blum <torstenb@FreeBSD.org>
+        Gary Clark II <gclarkii@FreeBSD.org>
+        Adam David <adam@FreeBSD.org>
+        Peter Dufault <dufault@FreeBSD.org>
+        Frank Durda IV <uhclem@FreeBSD.org>
+        Julian Elischer <julian@FreeBSD.org>
+        Sean Eric Fagan <sef@FreeBSD.org>
+        Stefan Esser <se@FreeBSD.org>
+        Bill Fenner <fenner@FreeBSD.org>
+        John Fieber <jfieber@FreeBSD.org>
+	Marc G. Fournier <scrappy@FreeBSD.org>
+        Lars Fredriksen <lars@freeBSD.org>
+        Thomas Gellekum <tg@FreeBSD.org>
+        Thomas Graichen <graichen@FreeBSD.org>
+        Rod Grimes <rgrimes@FreeBSD.org>
+	John Hay <jhay@FreeBSD.org>
+        Eric L. Hernes <erich@FreeBSD.org>
+        Jeffrey Hsu <hsu@FreeBSD.org>
+        Gary Jennejohn <gj@FreeBSD.org>
+	Andreas Klemm <andreas@FreeBSD.org>
+        L Jonas Olsson <ljo@FreeBSD.org>
+        Scott Mace <smace@FreeBSD.org>
+        Atsushi Murai <amurai@FreeBSD.org>
+        Mark Murray <markm@FreeBSD.org>
+	Alex Nash <alex@FreeBSD.org>
+	Sujal Patel <smpatel@FreeBSD.org>
+        Bill Paul <wpaul@FreeBSD.org>
+        Joshua Peck Macdonald <jmacd@FreeBSD.org>
+        John Polstra <jdp@FreeBSD.org>
+        Mike Pritchard <mpp@FreeBSD.org>
+        Doug Rabson <dfr@FreeBSD.org>
+	James Raynard <jraynard@FreeBSD.org>
+        Geoff Rehmet <csgr@FreeBSD.org>
+        Martin Renters <martin@FreeBSD.org>
+        Paul Richards <paul@FreeBSD.org>
+        Ollivier Robert <roberto@FreeBSD.org>
+        Dima Ruban <dima@FreeBSD.org>
+        Wolfram Schneider <wosch@FreeBSD.org>
+        Andreas Schulz <ats@FreeBSD.org>
+        Karl Strickland <karl@FreeBSD.org>
+        Paul Traina <pst@FreeBSD.org>
+        Guido van Rooij <guido@FreeBSD.org>
+        Steven Wallace <swallace@FreeBSD.org>
+        Nate Williams <nate@FreeBSD.org>
+        Jean-Marc Zucconi <jmz@FreeBSD.org>
+
+
+Additional FreeBSD helpers and beta testers:
+
+        Coranth Gryphon            Dave Rivers 
+        Kaleb S. Keithley	   Michael Smith
+        Terry Lambert		   David Dawes
+        Troy Curtis
+
+
+Special mention to:
+
+        Walnut Creek CDROM, without whose help (and continuing support)
+        this release would never have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        Chuck Robey for his donation of a floppy tape streamer for
+        testing.
+
+        Larry Altneu and Wilko Bulte for providing us with Wangtek
+        and Archive QIC-02 tape drives for testing and driver hacking.
+
+        CalWeb Internet Services for the loan of a P6/200 machine for
+        speedy package building.
+
+        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 Core Team
+
    + +&footer; + + + diff --git a/en/releases/2.1R/Makefile b/en/releases/2.1R/Makefile new file mode 100644 index 0000000000..517e40e9d3 --- /dev/null +++ b/en/releases/2.1R/Makefile @@ -0,0 +1,3 @@ +DOCS= announce.sgml notes.sgml + +.include "../../web.mk" diff --git a/en/releases/2.1R/announce.sgml b/en/releases/2.1R/announce.sgml new file mode 100644 index 0000000000..72f2ec9cce --- /dev/null +++ b/en/releases/2.1R/announce.sgml @@ -0,0 +1,58 @@ + + + + %includes; +]> + +&header; + +

    +Date: Sun, 19 Nov 1995 14:48:46 -0800
    +From: "Jordan K. Hubbard" <jkh@freebsd.org>
    +To: announce@freefall.cdrom.com
    +Subject: 2.1.0-RELEASE now available! +

    + +

    Could it be? Could the long-awaited release of FreeBSD + 2.1 truly have arrived?

    + +

    It gives me great pleasure to answer those questions with + a ``yes!''

    + +

    FreeBSD 2.1.0-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 + where it will be shipping shortly.

    + +

    FreeBSD 2.1 represents the culmination of 6 months worth + of work on the 2.1-STABLE branch of FreeBSD since the + previous release (FreeBSD 2.0.5).

    + +

    The STABLE branch was conceived out of the need to allow + FreeBSD to grow and support long-term development projects + like devfs, NFSv3, IPX, PCCARD, etc. while at the same time + not jeopardizing the stability of its existing user base. + Experimental or high-impact changes are allowed into FreeBSD-current, + which represents a sort of shared group development tree, + and only well tested or obvious fixes are allowed into + STABLE. In a few rare cases, where some bit of + functionality was entirely missing before, we've supplied + an ALPHA test quality version in STABLE on the premise that + some functionality is better than none at all (a good + example being the IDE CDROM driver).

    + +

    For more information on the 2.1 release itself, please + consult the documentation that accompanies the installation + procedure.

    + +

    Jordan

    + +&footer; + + diff --git a/en/releases/2.1R/notes.sgml b/en/releases/2.1R/notes.sgml new file mode 100644 index 0000000000..23ee084198 --- /dev/null +++ b/en/releases/2.1R/notes.sgml @@ -0,0 +1,349 @@ + + + + %includes; +]> + +&header; + +
    +
+                                 RELEASE NOTES
+                                    FreeBSD
+                                  Release 2.1
+
+1. Technical overview
+---------------------
+
+FreeBSD is a freely available, full source 4.4 BSD Lite based release
+for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
+primarily on software from U.C. Berkeley's CSRG group, with some
+enhancements from NetBSD, 386BSD, and the Free Software Foundation.
+
+Since our release of FreeBSD 2.0 over a year ago, the performance,
+feature set and stability of FreeBSD has improved dramatically.  The
+largest change is a revamped VM system with a merged VM/file buffer
+cache that not only increases performance but reduces FreeBSD's memory
+footprint, making a 5MB configuration a more acceptable minimum.
+Other enhancements include full NIS client and server support,
+transaction TCP support, dial-on-demand PPP, an improved SCSI
+subsystem, early ISDN support, support for FDDI and Fast Ethernet
+(100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
+narrow) and 3940 SCSI adaptors along with many hundreds of bug fixes.
+
+We've also taken the comments and suggestions of many of our users to
+heart and have attempted to provide what we hope is a more sane and
+easily understood installation process.  Your feedback on this
+(constantly evolving) process is especially welcome!
+
+In addition to the base distributions, FreeBSD offers a new ported
+software collection with over 350 commonly sought-after programs.  The
+list of ports ranges from http (WWW) servers, to games, languages,
+editors and almost everything in between.  The entire ports collection
+requires only 10MB of storage, all ports being expressed as "deltas"
+to their original sources.  This makes it much easier for us to update
+ports and greatly reduces the disk space demands made by the ports
+collection.  To compile a port, you simply change to the directory of
+the program you wish to install, type make and let the system do the
+rest.  The full original distribution for each port you build is
+retrieved dynamically off of CDROM or a local ftp site, so you need
+only enough disk space to build the ports you want.  (Almost) every
+port is also provided as a pre-compiled "package" which can be
+installed with a simple command (pkg_add).  See also the new Packages
+option in the Configuration menu for an especially convenient interface
+to the package collection.
+
+
+A number of additional documents which you may find helpful in the
+process of installing and using FreeBSD may now also be found in the
+/usr/share/doc directory.  You may view the manuals with any HTML
+capable browser by saying:
+
+  To read the handbook:
+      <browser> file:/usr/share/doc/handbook/handbook.html
+
+  To read the FAQ:
+      <browser> file:/usr/share/doc/FAQ/freebsd-faq.html
+
+You can also visit the master (and most frequently updated) copies at
+http://www.freebsd.org.
+
+The core of FreeBSD does not contain DES code which would inhibit its
+being exported outside the United States.  There is an add-on package
+to the core distribution, for use only in the United States, that
+contains the programs that normally use DES.  The auxiliary packages
+provided separately can be used by anyone.  A freely (from outside the
+U.S.) exportable distribution of DES for our non-U.S. users also
+exists at ftp://ftp.internat.freebsd.org/pub/FreeBSD.
+
+If password security for FreeBSD is all you need and you have no
+requirement for copying encrypted passwords from different hosts
+(Suns, DEC machines, etc) into FreeBSD password entries, then
+FreeBSD's MD5 based security may be all you require!  We feel that our
+default security model is more than a match for DES, and without any
+messy export issues to deal with.  If you're outside (or even inside)
+the U.S., give it a try!
+
+
+Supported Configurations
+------------------------
+
+FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
+based PC's, ranging from 386sx to Pentium class machines (though the
+386sx is not recommended).  Support for generic IDE or ESDI drive
+configurations, various SCSI controller, network and serial cards is
+also provided.
+
+What follows is a list of all disk controllers and ethernet cards
+currently known to work with FreeBSD.  Other configurations may also
+work, but we have simply not received any confirmation of this.
+
+
+	Disk Controllers
+	----------------
+
+WD1003 (any generic MFM/RLL)
+WD1007 (any generic IDE/ESDI)
+IDE
+ATA
+
+Adaptec 152x series ISA SCSI controllers
+Adaptec 154x series ISA SCSI controllers
+Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
+Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
+controllers.
+Adaptec AIC-6260 and AIC-6360 based boards, which includes
+the AHA-152x and SoundBlaster SCSI cards.
+
+** Note: You cannot boot from the SoundBlaster cards as they have no
+   on-board BIOS, such being necessary for mapping the boot device into the
+   system BIOS I/O vectors.  They're perfectly usable for external tapes,
+   CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
+   without a boot ROM.  Some systems DO have a boot ROM, which is generally
+   indicated by some sort of message when the system is first powered up
+   or reset, and in such cases you *will* also be able to boot from them.
+   Check your system/board documentation for more details.
+
+[Note that Buslogic was formerly known as "Bustek"]
+Buslogic 545S & 545c
+Buslogic 445S/445c VLB SCSI controller
+Buslogic 742A, 747S, 747c EISA SCSI controller.
+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. 
+
+DTC 3290 EISA SCSI controller in 1542 emulation mode.
+
+UltraStor 14F, 24F and 34F SCSI controllers.
+
+Seagate ST01/02 SCSI controllers.
+
+Future Domain 8xx/950 series SCSI controllers.
+
+WD7000 SCSI controller.
+
+With all supported SCSI controllers, full support is provided for
+SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
+DAT) and CD ROM drives.
+
+The following CD-ROM type systems are supported at this time:
+(cd)    SCSI interface (also includes ProAudio Spectrum and
+        SoundBlaster SCSI)
+(mcd)   Mitsumi proprietary interface (all models)
+(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
+        interface (562/563 models)
+(scd)   Sony proprietary interface (all models)
+(wcd)   ATAPI IDE interface (experimental and should be considered ALPHA
+        quality!).
+
+
+	Ethernet cards
+	--------------
+
+Allied-Telesis AT1700 and RE2000 cards
+SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
+WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
+based clones.  SMC Elite Ultra is also supported.
+
+DEC EtherWORKS III NICs (DE203, DE204, and DE205)
+DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
+DEC DC21140 based NICs (SMC???? DE???)
+DEC FDDI (DEFPA/DEFEA) NICs
+
+Fujitsu FMV-181 and FMV-182
+
+Intel EtherExpress
+
+Isolan AT 4141-0 (16 bit)
+Isolink 4110     (8 bit)
+
+Novell NE1000, NE2000, and NE2100 ethernet interface.
+
+3Com 3C501 cards
+
+3Com 3C503 Etherlink II
+
+3Com 3c505 Etherlink/+
+
+3Com 3C507 Etherlink 16/TP
+
+3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
+
+Toshiba ethernet cards
+
+PCMCIA ethernet cards from IBM and National Semiconductor are also
+supported.
+
+Note that NO token ring cards are supported at this time as we're
+still waiting for someone to donate a driver for one of them.  Any
+takers?
+
+
+	Misc Hardware
+	-------------
+
+AST 4 port serial card using shared IRQ.
+
+ARNET 8 port serial card using shared IRQ.
+
+BOCA ATIO66 6 port serial card using shared IRQ.
+
+Cyclades Cyclom-y Serial Board.
+
+STB 4 port card using shared IRQ.
+
+SDL Communications Riscom/8 Serial Board.
+
+Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
+and Roland MPU-401 sound cards.
+
+FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
+
+---
+
+
+Reporting problems, making suggestions and submitting code:
+===========================================================
+
+Your suggestions, bug reports and contributions of code are always
+valued - please do not hesitate to report any problems you may find
+(preferably with a fix attached, if you can!).
+
+The preferred method to submit bug reports from a machine with
+internet mail connectivity is to use the send-pr command.  Bug reports
+will be dutifully filed by our faithful bugfiler program and you can
+be sure that we'll do our best to respond to all reported bugs as soon
+as possible.  Bugs filed in this way are also visible on our WEB site
+in the support section and are therefore valuable both as bug reports
+and as "signposts" for other users concerning potential problems to
+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:
+
+                bugs@FreeBSD.org
+
+
+Otherwise, for any questions or suggestions, please send mail to:
+
+                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:
+
+                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:
+
+                announce@FreeBSD.org
+
+
+Any of the groups 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 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!
+
+
+6. 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.  It would be very difficult, if not
+impossible, to enumerate everyone who's contributed to FreeBSD, but
+nonetheless we shall try (in alphabetical order, of course). If you've
+contributed something substantive to us and your name is not mentioned
+here, please be assured that its omission is entirely accidental.
+Please contact hackers@FreeBSD.org for any desired updates to the
+lists that follow:
+
+
+The Computer Systems Research Group (CSRG), U.C. Berkeley.
+
+Bill Jolitz, for his initial work with 386BSD.
+
+The FreeBSD Core Team
+(in alphabetical order by first name):
+
+        Andrey A. Chernov <ache@FreeBSD.org>
+        Bruce Evans <bde@FreeBSD.org>
+        David Greenman <davidg@FreeBSD.org>
+        Garrett A. Wollman <wollman@FreeBSD.org>
+        Gary Palmer <gpalmer@FreeBSD.org>
+        Jörg Wunsch <joerg@FreeBSD.org>
+        John Dyson <dyson@FreeBSD.org>
+        Jordan K. Hubbard <jkh@FreeBSD.org>
+        Justin Gibbs <gibbs@FreeBSD.org>
+        Peter Wemm <peter@FreeBSD.org>
+        Poul-Henning Kamp <phk@FreeBSD.org>
+        Rich Murphey <rich@FreeBSD.org>
+        Satoshi Asami <asami@FreeBSD.org>
+        Søren Schmidt <sos@FreeBSD.org>
+
+Special mention to:
+
+        Walnut Creek CDROM, without whose help (and continuing support)
+        this release would never have been possible.
+
+        Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
+        drive.
+
+        Additional FreeBSD helpers and beta testers:
+
+        Atsushi Murai               Coranth Gryphon    
+        Dave Rivers                 Frank Durda IV
+        Guido van Rooij             Jeffrey Hsu
+        John Hay                    Julian Elischer
+        Kaleb S. Keithley           Michael Smith
+        Nate Williams               Peter Dufault
+        Rod Grimes                  Scott Mace
+        Stefan Esser                Steven Wallace
+        Terry Lambert               Wolfram Schneider
+
+        And 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 Core Team
+
    + +&footer; + + diff --git a/en/releases/Makefile b/en/releases/Makefile new file mode 100644 index 0000000000..32f4f68c0d --- /dev/null +++ b/en/releases/Makefile @@ -0,0 +1,5 @@ +DOCS= index.sgml snapshots.sgml + +SUBDIR= 1.1 1.1.5 2.0 2.0.5A 2.0.5R 2.0A 2.1R 2.1.5R + +.include "../web.mk" diff --git a/en/releases/Makefile.inc b/en/releases/Makefile.inc new file mode 100644 index 0000000000..0e4f1d8520 --- /dev/null +++ b/en/releases/Makefile.inc @@ -0,0 +1,2 @@ +WEBBASE= /data/releases + diff --git a/en/releases/index.sgml b/en/releases/index.sgml new file mode 100644 index 0000000000..570f143d31 --- /dev/null +++ b/en/releases/index.sgml @@ -0,0 +1,104 @@ + + + + %includes; +]> + +&header; + +

    Newsflash!

    +

    Recent announcement about FreeBSD Releases

    + +

    Current Release

    + +
      +
    • Release 2.1.5 RELEASE (July 14, 1996) + + &a.latest.ann;Announcement : + &a.latest.not;Release Notes. + +
      + If you wish to obtain this release, please see Obtaining and Installing + FreeBSD for details. +
      • +
    + +

    Future Releases

    + +
      + +
    • The next official release will be + 2.2 which will be derived from the + FreeBSD-current + branch of the development tree. Periodic + snapshot releases + will be made available before the release.
      • + +
    • The FreeBSD-stable + branch is also being loosely supported, with critical bug fixes + and installation system changes being brought in from time to time. + A 2.1.6 release will probably occur on this branch some + time in the next 2-3 months, just to clean up a last few remaining + nits from 2.1.5.
      • +
    + +

    Past Releases

    + + + +&footer; + + diff --git a/en/releases/snapshots.sgml b/en/releases/snapshots.sgml new file mode 100644 index 0000000000..66375890b4 --- /dev/null +++ b/en/releases/snapshots.sgml @@ -0,0 +1,73 @@ + + + + %includes; +]> + +&header; + +

    What are snapshots?

    + + +

    As part of an ongoing effort to improve the overall + release process before a release actually slips + out the door with problems that make folks mad, we are now + periodically producing interim test releases + called snapshots. These snapshots will be very similar to + full releases, except that they'll be somewhat more + minimal. In particular, before getting and installing a + snapshot release, be aware of following: + +

      + +
    • We generally will not, for example, produce new + XFree86 distributions or worry much about the tools + directory, unless either of those two things are affected + by the changes being tested. + +
    • The major release number will not be changed in the + main distribution for each snapshot. It will + only be changed on the boot floppies so that you + know when the snapshot was made. These are not + releases, these are snapshots, and it's + important that this distinction be preserved. People can + and will, of course, refer to snapshots by date in mail + or netnews, we just don't want them to start thinking + that Christmas came early and the next release is already + out! + +
    • Finally, we will not necessarily update the + documentation. If a README still refers to a previous release, + well, that's much less important to than getting the + real bug fixes and new features out for testing. Complaints + about that kind of thing will be quietly ignored. Again, + these are snapshots, not releases! +
    + +

    Your feedback on these snapshots is, of course, greatly + welcome. They're not just for our benefit - those who are + coming to rely on FreeBSD for mission critical + applications should welcome a chance to get at more updated + bits in a structured fashion. You can also use these + snapshots as tangible evidence that your feedback is + getting incorporated and that you (hopefully) won't have + any unpleasant surprises in the next release. On the other hand, if + you do send us hate mail next release and it turns out that you + never even tried the snapshots, well, it cuts both ways! + +

    Where to find snapshots

    + +

    Snapshots are available via anonymous from ftp://ftp.freebsd.org/pub/FreeBSD/. + The snapshot releases are in directories named in the + format REL-YYMMDD-SNAP where `REL' is the + release number, `YY' is the year, `MM' is + the month, and `DD' is the day the snapshot was + released. Each snapshot directory contains a + `README' file which outlines the changes for the + particular snapshot.

    + +&footer; + + diff --git a/en/robots.txt b/en/robots.txt new file mode 100644 index 0000000000..20fd53e7c1 --- /dev/null +++ b/en/robots.txt @@ -0,0 +1,4 @@ +User-agent: * +Disallow: /cgi-bin/ +Disallow: /cgi/ +Disallow: ~/jfieber/data/cgi/ diff --git a/en/search/index-site.sgml b/en/search/index-site.sgml new file mode 100644 index 0000000000..fa7a0308f1 --- /dev/null +++ b/en/search/index-site.sgml @@ -0,0 +1,98 @@ + + + %includes; +]> + +&header; + + + + +&footer; + + + + + diff --git a/en/search/search.sgml b/en/search/search.sgml new file mode 100644 index 0000000000..84ca910409 --- /dev/null +++ b/en/search/search.sgml @@ -0,0 +1,112 @@ + + + %includes; +]> + +&header; + +

    FreeBSD Mailing List Archives

    + +
    + +

    Search for:

    + +

    Note: Use the operators AND or NOT to limit your + search. Look here + for more hints.

    + +

    + +

    In archive(s):

    + +

    Note: Searching more than three or four archives at once may +yield inaccurate results.

    + +

    + + Questions: General questions
    + + + Announce: Important events / milestones
    + + + Bugs: Reports and discussion of bugs
    + + + Chat: Random topics (sometimes) related to FreeBSD
    + + + Commit: Changes made to the FreeBSD source tree
    + + + Current: Discussions concerning the use of + FreeBSD-current sources
    + + + Doc: Discussions concerning documentation
    + + + Emulation: Emulating other systems on FreeBSD
    + + + Fs: Discussions concerning FreeBSD filesystems
    + + + Hackers: Technical discussions and suggestions
    + + + Hardware: Discussions concerning hardware as it + relates to FreeBSD
    + + + Install: Discussions concerning the installation + process
    + + + ISP: Discussions for ISPs using FreeBSD
    + + + Mobile: Using FreeBSD in a mobile environment
    + + + Multimedia: Discussions about FreeBSD as a + multimedia platform
    + + + Platforms: Cross-platform FreeBSD issues + (non-Intel FreeBSD ports)
    + + + Ports: Discussions concerning FreeBSD's ports collection
    + + + SCSI: Discussions about FreeBSD's SCSI support
    + + + Security: FreeBSD computer security + issues (DES, Kerberos, etc.)
    + + + SMP: FreeBSD on multi-processor platforms
    + + + Stable: Discussion of the FreeBSD-stable branch + of the development tree.
    + + + User-Groups: A forum for FreeBSD user groups

    + +

    Limit the number of results to

    + +

    + +
    + +&footer; + + + + diff --git a/en/search/searchhints.sgml b/en/search/searchhints.sgml new file mode 100644 index 0000000000..6436021e34 --- /dev/null +++ b/en/search/searchhints.sgml @@ -0,0 +1,50 @@ + + + %includes; +]> + +&header; + +

    If you got lots of irrelevant results...

    + +
      +
    1. If you search for several words such as "quantum + hard drives", an OR is implied meaning that to be + counted as relevant, only one of the word has to appear + in a message. To find only messages with all three + words, change the search to "quantum and hard and + drives"

      2. + +
    2. If you still get lots of irrelevant messages, see if + they have something in common. If so, you can exclude + them with the not operator. For example + "quantum and hard and drives not ide" will + exclude any messages about ide quantum hard drives.
      3. +
    + +

    If you don't think you got everything you should have...

    + +
      +
    1. If one of your keywords has variant forms, be sure to + enter all relevant forms. If you are searching for + "buslogic", you might change it to "buslogic + or bustek".

      2. + +
    2. Words with varying suffixes can be wildcarded. + Searching for "drive*" will pick up words such + as drive, drives, driver, + drivers and so on.

      3. + +
    3. Try discarding words that could be implied by the + context of the message. For example "quantum and + hard and drive" might miss some relevant messages + that "quantum and drive" would get.
      4. +
    + +
    +Return to the search page + +&footer; + + diff --git a/en/support.sgml b/en/support.sgml new file mode 100644 index 0000000000..4c1de50906 --- /dev/null +++ b/en/support.sgml @@ -0,0 +1,252 @@ + + + %includes; +]> + +&header; + +

    Mailing lists

    + +

    Mailing list are the primary support channel for FreeBSD + users, with numerous mailing list covering different + topic areas. When in doubt about what list to post a + question to, post to questions@freebsd.org.

    + +

    You can search the mailing list + archives at www.freebsd.org.

    + +

    For speakers of German, there are some german language mailing + lists available. See + http://www.de.freebsd.org/de/ or send mail to + majordomo@de.freebsd.org + to join or find out more information about the lists. + +

    For speakers of Portuguese, there are some portuguese language mailing + lists available. See + http://www.br.freebsd.org/list.html + or send mail to + listproc@br.freebsd.org to join or find out more information about + the list. + +

    For speakers of Japanese, there are some japanese language mailing + lists available. See + http://www.jp.freebsd.org/ or send mail to + majordomo@jp.freebsd.org + to join or find out more information about the lists. + +

    Newsgroups

    + +

    There are a few FreeBSD specific newsgroups, along with + numerous other newsgroups on topics of interest to FreeBSD + users, though the mailing lists remain the most reliable way to + get in touch with the FreeBSD developers. For miscellaneous + FreeBSD discussion, see + comp.unix.bsd.freebsd.misc. For important announcements, + see + comp.unix.bsd.freebsd.announce. + +

    WEB Resources

    + + Our WEB pages remain one of the best sources of information, + and are also mirrored at many sites around the world. Most countries + also now have subdomains set up under freebsd.org to make such + local resources easier to find - when in doubt, try connecting to + www.yourcountry.freebsd.org (e.g. + www.de.freebsd.org for + Germany or www.au.freebsd.org + for Australia). The same is also true for FTP servers, by + the way. + +

    For information on recent FreeBSD progress and releases, + see the Newsflash page. + +

    GNATS + Problem Report Database

    + + + +

    Problem reports may also be submitted to the + development team using the + send-pr(1) command on a FreeBSD system or by sending an email + message to bugs@freebsd.org. + Please note that + send-pr is preferred since messages sent to the mailing list are + not tracked as official problem reports! + +

    CVS Repository

    + +

    CVS (the Concurrent Version System) is the tool we use for + keeping our sources under control. Every change (with + accompanying log message explaining its purpose) from + FreeBSD 2.0 to the present is stored here, and can be + easily viewed from here (click on the link). To obtain a + complete copy of the FreeBSD CVS respository, please use + either the sup or CTM tools or simply FTP it + from here. + +

    User Groups

    + +
      +
    • BAFUG (Bay Area FreeBSD User Group) (contact info?)

      • + +
    • BUG/HH (BSD user group Hamburg) meets on the last + Tuesday of the month at 7.00pm in the Chinese restaurant + Lotus Bluete, Loewenstrasse 22 in Hamburg + Eppendorf. Most members are FreeBSD users, although + users of all BSD flavors are welcome. Interested people + should send mail to bsdhh@elbe.desy.de. +
      FAQ File + (in German)       +

      • + +
    • The Brainstorm + users group meets in Wuerzburg, Germany and welcomes all users of + Unix, with some emphasis on helping new users of FreeBSD. They + meet every monday at 8.00pm in the "Cafe Klug", Muenzstrasse, + Wuerzburg. Mail + bs@rak.franken.de + for more information or follow the Brainstorm link. +

      • + +
    • FUUNM (Free Unix Users of New Mexico) meets on the 2nd + Saturday of the month from 4:30-6:00pm at the Farris + Engineering Center, room 141, University of new Mexico. + This is not specifically a FreeBSD user group, but if you + are in the area, your presence is welcome. The group + operates a mailing list (fuunm@astro.phys.unm.edu). + Contact Alan + Lundin for more information.

      • + +
    • FreeBSD-Milwaukee + Wisconson meets occasionaly and has a mailing list: freebsd-mke-l@ns.sol.net. send + mail to freebsd-mke-l-request@ns.sol.net + to subscribe.

      • + +
    • RUUG (Reno Unix Users Group) meets monthly in Reno + Nevada and discusses the use of FreeBSD and Linux. + Contact Eric Blood + or Todd + Crenshaw for more information.

      • + +
    • Washington DC (contact info?)

      • +
    + + +

    General UNIX Information

    + + + +

    The X Window System

    + +
      +
    • The XFree86 + Project provides users of a variety of Intel based + Unix systems, including FreeBSD, with an excellent X + Window system.
      • + +
    • The WINE project is working to provide the ability to + run MS-Windows software on Intel based Unix systems such + as FreeBSD, NetBSD and Linux. More information is + available from http://daedalus.dra.hmg.gb/gale/wine/wine.html.
      • +
    + +

    Hardware

    + + +

    Multimedia

    + + + + +

    Related Operating System Projects

    +
      + +
    • NetBSD + is a very close relative of FreeBSD.
      • + +
    • OpenBSD + is derived from NetBSD and supported by a group of former + NetBSD developers.
      • + +
    • Linux is + another free Unix-like system.
      • + +
    • Lites + is a 4.4 BSD Lite based server and emulation library that + provides free unix functionality to a Mach based + system.
      • + +
    • The GNU + HURD project is another effort to develop a free + Unix-like operating system.
      • +
    + +&footer; + + + + diff --git a/en/usergroups.sgml b/en/usergroups.sgml new file mode 100644 index 0000000000..4c1de50906 --- /dev/null +++ b/en/usergroups.sgml @@ -0,0 +1,252 @@ + + + %includes; +]> + +&header; + +

    Mailing lists

    + +

    Mailing list are the primary support channel for FreeBSD + users, with numerous mailing list covering different + topic areas. When in doubt about what list to post a + question to, post to questions@freebsd.org.

    + +

    You can search the mailing list + archives at www.freebsd.org.

    + +

    For speakers of German, there are some german language mailing + lists available. See + http://www.de.freebsd.org/de/ or send mail to + majordomo@de.freebsd.org + to join or find out more information about the lists. + +

    For speakers of Portuguese, there are some portuguese language mailing + lists available. See + http://www.br.freebsd.org/list.html + or send mail to + listproc@br.freebsd.org to join or find out more information about + the list. + +

    For speakers of Japanese, there are some japanese language mailing + lists available. See + http://www.jp.freebsd.org/ or send mail to + majordomo@jp.freebsd.org + to join or find out more information about the lists. + +

    Newsgroups

    + +

    There are a few FreeBSD specific newsgroups, along with + numerous other newsgroups on topics of interest to FreeBSD + users, though the mailing lists remain the most reliable way to + get in touch with the FreeBSD developers. For miscellaneous + FreeBSD discussion, see + comp.unix.bsd.freebsd.misc. For important announcements, + see + comp.unix.bsd.freebsd.announce. + +

    WEB Resources

    + + Our WEB pages remain one of the best sources of information, + and are also mirrored at many sites around the world. Most countries + also now have subdomains set up under freebsd.org to make such + local resources easier to find - when in doubt, try connecting to + www.yourcountry.freebsd.org (e.g. + www.de.freebsd.org for + Germany or www.au.freebsd.org + for Australia). The same is also true for FTP servers, by + the way. + +

    For information on recent FreeBSD progress and releases, + see the Newsflash page. + +

    GNATS + Problem Report Database

    + + + +

    Problem reports may also be submitted to the + development team using the + send-pr(1) command on a FreeBSD system or by sending an email + message to bugs@freebsd.org. + Please note that + send-pr is preferred since messages sent to the mailing list are + not tracked as official problem reports! + +

    CVS Repository

    + +

    CVS (the Concurrent Version System) is the tool we use for + keeping our sources under control. Every change (with + accompanying log message explaining its purpose) from + FreeBSD 2.0 to the present is stored here, and can be + easily viewed from here (click on the link). To obtain a + complete copy of the FreeBSD CVS respository, please use + either the sup or CTM tools or simply FTP it + from here. + +

    User Groups

    + +
      +
    • BAFUG (Bay Area FreeBSD User Group) (contact info?)

      • + +
    • BUG/HH (BSD user group Hamburg) meets on the last + Tuesday of the month at 7.00pm in the Chinese restaurant + Lotus Bluete, Loewenstrasse 22 in Hamburg + Eppendorf. Most members are FreeBSD users, although + users of all BSD flavors are welcome. Interested people + should send mail to bsdhh@elbe.desy.de. +
      FAQ File + (in German)       +

      • + +
    • The Brainstorm + users group meets in Wuerzburg, Germany and welcomes all users of + Unix, with some emphasis on helping new users of FreeBSD. They + meet every monday at 8.00pm in the "Cafe Klug", Muenzstrasse, + Wuerzburg. Mail + bs@rak.franken.de + for more information or follow the Brainstorm link. +

      • + +
    • FUUNM (Free Unix Users of New Mexico) meets on the 2nd + Saturday of the month from 4:30-6:00pm at the Farris + Engineering Center, room 141, University of new Mexico. + This is not specifically a FreeBSD user group, but if you + are in the area, your presence is welcome. The group + operates a mailing list (fuunm@astro.phys.unm.edu). + Contact Alan + Lundin for more information.

      • + +
    • FreeBSD-Milwaukee + Wisconson meets occasionaly and has a mailing list: freebsd-mke-l@ns.sol.net. send + mail to freebsd-mke-l-request@ns.sol.net + to subscribe.

      • + +
    • RUUG (Reno Unix Users Group) meets monthly in Reno + Nevada and discusses the use of FreeBSD and Linux. + Contact Eric Blood + or Todd + Crenshaw for more information.

      • + +
    • Washington DC (contact info?)

      • +
    + + +

    General UNIX Information

    + + + +

    The X Window System

    + +
      +
    • The XFree86 + Project provides users of a variety of Intel based + Unix systems, including FreeBSD, with an excellent X + Window system.
      • + +
    • The WINE project is working to provide the ability to + run MS-Windows software on Intel based Unix systems such + as FreeBSD, NetBSD and Linux. More information is + available from http://daedalus.dra.hmg.gb/gale/wine/wine.html.
      • +
    + +

    Hardware

    + + +

    Multimedia

    + + + + +

    Related Operating System Projects

    +
      + +
    • NetBSD + is a very close relative of FreeBSD.
      • + +
    • OpenBSD + is derived from NetBSD and supported by a group of former + NetBSD developers.
      • + +
    • Linux is + another free Unix-like system.
      • + +
    • Lites + is a 4.4 BSD Lite based server and emulation library that + provides free unix functionality to a Mach based + system.
      • + +
    • The GNU + HURD project is another effort to develop a free + Unix-like operating system.
      • +
    + +&footer; + + + + diff --git a/en/web.mk b/en/web.mk new file mode 100644 index 0000000000..993ec606d1 --- /dev/null +++ b/en/web.mk @@ -0,0 +1,256 @@ +# bsd.web.mk +# $Id: web.mk,v 1.1.1.1 1996-09-24 17:45:45 jfieber Exp $ + +# +# Build and install a web site. +# +# Basic targets: +# +# all (default) -- performs batch mode processing necessary +# install -- Installs everything +# clean -- remove anything generated by processing +# +# Transformations: +# +# copy -- no processing, simply copy the file to install +# spam -- run the file through spam for processing and validation +# m4 -- run through the m4 macro processor +# + +.if exists(${.CURDIR}/../Makefile.inc) +.include "${.CURDIR}/../Makefile.inc" +.endif + +WEBDIR?= ${.CURDIR:T} +CGIDIR?= ${.CURDIR:T} +DESTDIR?= ${HOME}/public_html + +WEBOWN?= ${USER} +WEBGRP?= ${USER} +WEBMODE?= ${NOBINMODE} + +CGIOWN?= ${USER} +CGIGRP?= ${USER} +CGIMODE?= ${BINMODE} + +# +# Install dirs derived from the above. +# +DOCINSTALLDIR= ${DESTDIR}${WEBBASE}/${WEBDIR} +CGIINSTALLDIR= ${DESTDIR}${WEBBASE}/${CGIDIR} + +# +# The orphan list contains sources specified in DOCS that there +# is no transform rule for. We start out with all of them, and +# each rule below removes the ones it knows about. If any are +# left over at the end, the user is warned about them. +# +ORPHANS:= ${DOCS} + +COPY= -c + +################################################################## +# Transformation rules + +### +# file.sgml --> file.html +# +# Runs file.sgml through spam to validate and expand some entity +# references are expanded. file.html is added to the list of +# things to install. + +.SUFFIXES: .sgml .html +SGMLNORM= sgmlnorm +CATALOG?= /usr/local/share/sgml/HTML/catalog +SGMLNORMFLAGS= -d ${SGMLNORMOPTS} -c ${CATALOG} +GENDOCS+= ${DOCS:M*.sgml:S/.sgml$/.html/g} +ORPHANS:= ${ORPHANS:N*.sgml} + +.sgml.html: + ${SGMLNORM} ${SGMLNORMFLAGS} ${.IMPSRC} > ${.TARGET} + +### +# file.java --> file.class +# +# Uses javac to compile java source. Note: since we cannot tell +# what classes will come out of a java file, we have install all +# .class files. The .if construction is there so that *.class +# is only put in if there are actually java files in the DOCS. +# Generally speaking, make and java were not made for each other. + +.SUFFIXES: .java .class +JAVAC?= javac +JAVAFLAGS= ${JAVAOPTS} +_TMP:= ${DOCS:M*.java} +.if !empty(_TMP) +GENDOCS+= ${DOCS:M*.java:S/.java$/.class/g} *.class +.endif +ORPHANS:= ${ORPHANS:N*.java} + +.java.class: + ${JAVAC} ${JAVAFLAGS} ${.IMPSRC} + + +### +# file.m4 --> file.html +# +# Runs file.m4 through the m4 preprocessor, generating file.sgml, +# which is then taken care of by the .sgml to .html rule. + +.SUFFIXES: .m4 +M4?= m4 +M4FLAGS?= ${M4OPTS} +GENDOCS+= ${DOCS:M*.m4:S/.m4$/.html/g} +CLEANFILES+= ${DOCS:M*.m4:S/.m4$/.sgml/g} +ORPHANS:= ${ORPHANS:N*.m4} + +.m4.sgml: + ${M4} ${M4OPTS} < ${.IMPSRC} > ${.TARGET} + + +################################################################## +# Targets + +# +# If no target is specified, .MAIN is made +# +.MAIN: all + +# +# Build most everything +# +all: orphans cvsdirs ${GENDOCS} ${DATA} ${LOCAL} ${CGI} _PROGSUBDIR + +# +# Warn about anything in DOCS that has no translation +# +.if !empty(ORPHANS) +orphans: + @echo Warning! I don\'t know what to do with: ${ORPHANS} +.else +orphans: +.endif + +# +# Check these things out from cvs +# +cvsdirs: +.if defined{CVSDIRS} && !empty{CVSDIRS} + for i in ${CVSDIRS}; do \ + cvs co -P $$i; \ + done +.endif + +# +# Clean things up +# +.if !target(clean) +clean: _PROGSUBDIR + rm -f Errs errs mklog ${GENDOCS} ${LOCAL} ${CLEANFILES} +.endif + +# +# Really clean things up +# +.if !target(cleandir) +cleandir: clean _PROGSUBDIR + rm -f ${.CURDIR}/tags .depend + cd ${.CURDIR}; rm -rf obj; +.endif + +# +# Install targets: before, real, and after. +# +.if !target(install) +.if !target(beforeinstall) +beforeinstall: +.endif +.if !target(afterinstall) +afterinstall: +.endif + +_ALLINSTALL= ${GENDOCS} ${DATA} ${LOCAL} + +realinstall: ${COOKIE} ${GENDOCS} ${DATA} ${LOCAL} ${CGI} _PROGSUBDIR +.if !empty(_ALLINSTALL) + @mkdir -p ${DOCINSTALLDIR} + for entry in ${_ALLINSTALL}; do \ + ${INSTALL} ${COPY} -o ${WEBOWN} -g ${WEBGRP} -m ${WEBMODE} \ + ${INSTALLFLAGS} $${entry} ${DOCINSTALLDIR}; \ + done +.endif +.if defined(CGI) && !empty(CGI) + @mkdir -p ${CGIINSTALLDIR} + for entry in ${CGI}; do \ + ${INSTALL} ${COPY} -o ${CGIOWN} -g ${CGIGRP} -m ${CGIMODE} \ + ${INSTALLFLAGS} $${entry} ${CGIINSTALLDIR}; \ + done +.endif +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + for entry in ${DOCSUBDIR}; do \ + mkdir -p ${DOCINSTALLDIR}/$$entry; \ + done +.endif + +realinstall2: +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + for entry in ${DOCSUBDIR}; do \ + (cd ${DOCINSTALLDIR}/$$entry; \ + tar czf $$entry-html.tar.gz $${entry}.html $${entry}_toc.html \ + $$entry[0-9]*.html; \ + ${BATCHSSI} $$entry ${HDR} ${FTR} \ + $${entry}.html $${entry}_toc.html $$entry[0-9]*.html); \ + done +.endif + +# Set up install dependencies so they happen in the correct order. +install: afterinstall +afterinstall: realinstall2 +realinstall: beforeinstall +realinstall2: realinstall +.endif + +# +# This recursively calls make in subdirectories. +# +#SUBDIR+=${DOCSUBDIR} +_PROGSUBDIR: .USE +.if defined(SUBDIR) && !empty(SUBDIR) + @for entry in ${SUBDIR}; do \ + (${ECHODIR} "===> ${DIRPRFX}$$entry"; \ + cd ${.CURDIR}/$${entry}; \ + ${MAKE} ${.TARGET:S/realinstall/install/:S/.depend/depend/} DIRPRFX=${DIRPRFX}$$entry/); \ + done +.endif +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + @for entry in ${DOCSUBDIR}; do \ + (${ECHODIR} "===> ${DIRPRFX}$$entry"; \ + cd ${.CURDIR}/$${entry}; \ + ${MAKE} ${.TARGET:S/realinstall/install/:S/.depend/depend/} DIRPRFX=${DIRPRFX}$$entry/ ${PARAMS}); \ + done +.endif + + +# +# cruft for generating linuxdoc stuff +# + +.if defined (DOCSUBDIR) && !empty(DOCSUBDIR) + +FORMATS?= "html ascii latin1 ps" +PARAMS= DESTDIR=${DESTDIR} DOCDIR=${WEBBASE}/${WEBDIR} +PARAMS+= DOCOWN=${WEBOWN} DOCGRP=${WEBGRP} +PARAMS+= SGMLOPTS="-ssi -links" FORMATS=${FORMATS} COPY="${COPY}" +#DOCDIR= ${WEBBASE}/${WEBDIR} +#DOCOWN= ${WEBOWN} +#DOCGRP= ${WEBGRP} +#MANMODE= ${WEBMODE} +#PARAMS+= MANGRP=${CGIGRP} MANMODE=${MANMODE} MANOWN=${CGIOWN} + +BATCHSSI= batchssi +HDR= ${.CURDIR}/doc.hdr +FTR= ${.CURDIR}/doc.ftr + +.endif + +# THE END diff --git a/en/welcome.sgml b/en/welcome.sgml new file mode 100644 index 0000000000..0cad06d6e2 --- /dev/null +++ b/en/welcome.sgml @@ -0,0 +1,65 @@ + + + %includes; +]> + + + + About FreeBSD + + + + + +

    What is FreeBSD?

    + +

    FreeBSD is an advanced BSD UNIX operating system for "PC-compatible" +computers. It offers an exceptional combination of features:

    + +
    FreeBSD +specializes in TCP/IP networking. + +

    FreeBSD makes an ideal Internet server or +desktop system. It provides robust network services, even under the heaviest +of loads, and uses memory efficiently to maintain good response times for +hundreds, or even thousands, of simultaneous user processes

    + + +
    FreeBSD +provides advanced technical features. + +

    FreeBSD offers many features today which are still missing in other +operating systems, even some of the best commercial ones. Advanced +features for performance, security, and even binary compatibility with +other popular operating systems.

    + +
    FreeBSD +can run a variety of applications. + +

    The quality of FreeBSD combined with today's low-cost, high-speed PC hardware +makes FreeBSD a very economical alternative to commercial UNIX workstations. +It's suited for a great number of applications.

    + + +
    FreeBSD +is easy to install. + +

    FreeBSD can be installed from a variety of media including CD-ROM, floppy +disk, magnetic tape, an MS-DOS partition, or if you have a network connection +(even a dial-up PPP to an Internet provider), you can install it directly +over anonymous FTP or NFS. All you need is a single 1.44MB boot floppy +and these directions.

    + + +
    FreeBSD +is free. + +

    While you might expect an operating system with these features to sell +for a high price, FreeBSD is available free of charge and comes with full +source code. If you'd like to try it out, more +information is available.

    + +&footer; + + diff --git a/en/where.sgml b/en/where.sgml new file mode 100644 index 0000000000..64f260aeae --- /dev/null +++ b/en/where.sgml @@ -0,0 +1,111 @@ + + + %includes; +]> + +&header; + +

    Installing FreeBSD

    + +

    There are many options for installing FreeBSD, including + installation from CDROM, floppy disk, an MS-DOS partition, + magnetic tape, anonymous ftp, and NFS. Please read through + the installation guide + before downloading the entire FreeBSD distribution. If you + are installing on a machine connected to the Internet, you + may only need to download a single installation disk image!

    + +

    FreeBSD Distribution Sites

    + +

    The official sources for FreeBSD are: +

    + +

    If you plan on getting FreeBSD via ftp, please check the + listing of mirror + sites in the handbook to see if there is a site closer + to you. For more information about past, present and + future releases in general, please visit the release information page. + +

    Applications and Utility Software

    + +

    The Packages collection

    + +

    The FreeBSD packages are a diverse collection of utility + and application software that has been ported to FreeBSD. + The packages are pre-compiled binaries ready to drop into + your system and run.

    + + + +

    The Ports collection

    + +

    The Ports collection is like the packages collection but + instead of compiled binaries, the necessary patches and + makefiles to compile the source code are provided. For + software with important configuration that must be done at + compile time, the "port" version may be more useful than + the "package" version.

    + + + +

    For information about how you can contribute + your favorite piece of software to the port + collection, have a look at Porting + applications and Contributing to + FreeBSD in the FreeBSD handbook. + +

    Commercial software

    + +

    Beginning with FreeBSD Release + 2.0.5, FreeBSD includes demo versions of some + commercial as well as some shareware products. In + addition to the demos available in the FreeBSD + distribution, a number of other commercial vendors offer + software products specifically for FreeBSD.

    + + + +&footer; + + diff --git a/share/mk/web.site.mk b/share/mk/web.site.mk new file mode 100644 index 0000000000..bcd9d5c416 --- /dev/null +++ b/share/mk/web.site.mk @@ -0,0 +1,256 @@ +# bsd.web.mk +# $Id: web.site.mk,v 1.1.1.1 1996-09-24 17:45:45 jfieber Exp $ + +# +# Build and install a web site. +# +# Basic targets: +# +# all (default) -- performs batch mode processing necessary +# install -- Installs everything +# clean -- remove anything generated by processing +# +# Transformations: +# +# copy -- no processing, simply copy the file to install +# spam -- run the file through spam for processing and validation +# m4 -- run through the m4 macro processor +# + +.if exists(${.CURDIR}/../Makefile.inc) +.include "${.CURDIR}/../Makefile.inc" +.endif + +WEBDIR?= ${.CURDIR:T} +CGIDIR?= ${.CURDIR:T} +DESTDIR?= ${HOME}/public_html + +WEBOWN?= ${USER} +WEBGRP?= ${USER} +WEBMODE?= ${NOBINMODE} + +CGIOWN?= ${USER} +CGIGRP?= ${USER} +CGIMODE?= ${BINMODE} + +# +# Install dirs derived from the above. +# +DOCINSTALLDIR= ${DESTDIR}${WEBBASE}/${WEBDIR} +CGIINSTALLDIR= ${DESTDIR}${WEBBASE}/${CGIDIR} + +# +# The orphan list contains sources specified in DOCS that there +# is no transform rule for. We start out with all of them, and +# each rule below removes the ones it knows about. If any are +# left over at the end, the user is warned about them. +# +ORPHANS:= ${DOCS} + +COPY= -c + +################################################################## +# Transformation rules + +### +# file.sgml --> file.html +# +# Runs file.sgml through spam to validate and expand some entity +# references are expanded. file.html is added to the list of +# things to install. + +.SUFFIXES: .sgml .html +SGMLNORM= sgmlnorm +CATALOG?= /usr/local/share/sgml/HTML/catalog +SGMLNORMFLAGS= -d ${SGMLNORMOPTS} -c ${CATALOG} +GENDOCS+= ${DOCS:M*.sgml:S/.sgml$/.html/g} +ORPHANS:= ${ORPHANS:N*.sgml} + +.sgml.html: + ${SGMLNORM} ${SGMLNORMFLAGS} ${.IMPSRC} > ${.TARGET} + +### +# file.java --> file.class +# +# Uses javac to compile java source. Note: since we cannot tell +# what classes will come out of a java file, we have install all +# .class files. The .if construction is there so that *.class +# is only put in if there are actually java files in the DOCS. +# Generally speaking, make and java were not made for each other. + +.SUFFIXES: .java .class +JAVAC?= javac +JAVAFLAGS= ${JAVAOPTS} +_TMP:= ${DOCS:M*.java} +.if !empty(_TMP) +GENDOCS+= ${DOCS:M*.java:S/.java$/.class/g} *.class +.endif +ORPHANS:= ${ORPHANS:N*.java} + +.java.class: + ${JAVAC} ${JAVAFLAGS} ${.IMPSRC} + + +### +# file.m4 --> file.html +# +# Runs file.m4 through the m4 preprocessor, generating file.sgml, +# which is then taken care of by the .sgml to .html rule. + +.SUFFIXES: .m4 +M4?= m4 +M4FLAGS?= ${M4OPTS} +GENDOCS+= ${DOCS:M*.m4:S/.m4$/.html/g} +CLEANFILES+= ${DOCS:M*.m4:S/.m4$/.sgml/g} +ORPHANS:= ${ORPHANS:N*.m4} + +.m4.sgml: + ${M4} ${M4OPTS} < ${.IMPSRC} > ${.TARGET} + + +################################################################## +# Targets + +# +# If no target is specified, .MAIN is made +# +.MAIN: all + +# +# Build most everything +# +all: orphans cvsdirs ${GENDOCS} ${DATA} ${LOCAL} ${CGI} _PROGSUBDIR + +# +# Warn about anything in DOCS that has no translation +# +.if !empty(ORPHANS) +orphans: + @echo Warning! I don\'t know what to do with: ${ORPHANS} +.else +orphans: +.endif + +# +# Check these things out from cvs +# +cvsdirs: +.if defined{CVSDIRS} && !empty{CVSDIRS} + for i in ${CVSDIRS}; do \ + cvs co -P $$i; \ + done +.endif + +# +# Clean things up +# +.if !target(clean) +clean: _PROGSUBDIR + rm -f Errs errs mklog ${GENDOCS} ${LOCAL} ${CLEANFILES} +.endif + +# +# Really clean things up +# +.if !target(cleandir) +cleandir: clean _PROGSUBDIR + rm -f ${.CURDIR}/tags .depend + cd ${.CURDIR}; rm -rf obj; +.endif + +# +# Install targets: before, real, and after. +# +.if !target(install) +.if !target(beforeinstall) +beforeinstall: +.endif +.if !target(afterinstall) +afterinstall: +.endif + +_ALLINSTALL= ${GENDOCS} ${DATA} ${LOCAL} + +realinstall: ${COOKIE} ${GENDOCS} ${DATA} ${LOCAL} ${CGI} _PROGSUBDIR +.if !empty(_ALLINSTALL) + @mkdir -p ${DOCINSTALLDIR} + for entry in ${_ALLINSTALL}; do \ + ${INSTALL} ${COPY} -o ${WEBOWN} -g ${WEBGRP} -m ${WEBMODE} \ + ${INSTALLFLAGS} $${entry} ${DOCINSTALLDIR}; \ + done +.endif +.if defined(CGI) && !empty(CGI) + @mkdir -p ${CGIINSTALLDIR} + for entry in ${CGI}; do \ + ${INSTALL} ${COPY} -o ${CGIOWN} -g ${CGIGRP} -m ${CGIMODE} \ + ${INSTALLFLAGS} $${entry} ${CGIINSTALLDIR}; \ + done +.endif +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + for entry in ${DOCSUBDIR}; do \ + mkdir -p ${DOCINSTALLDIR}/$$entry; \ + done +.endif + +realinstall2: +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + for entry in ${DOCSUBDIR}; do \ + (cd ${DOCINSTALLDIR}/$$entry; \ + tar czf $$entry-html.tar.gz $${entry}.html $${entry}_toc.html \ + $$entry[0-9]*.html; \ + ${BATCHSSI} $$entry ${HDR} ${FTR} \ + $${entry}.html $${entry}_toc.html $$entry[0-9]*.html); \ + done +.endif + +# Set up install dependencies so they happen in the correct order. +install: afterinstall +afterinstall: realinstall2 +realinstall: beforeinstall +realinstall2: realinstall +.endif + +# +# This recursively calls make in subdirectories. +# +#SUBDIR+=${DOCSUBDIR} +_PROGSUBDIR: .USE +.if defined(SUBDIR) && !empty(SUBDIR) + @for entry in ${SUBDIR}; do \ + (${ECHODIR} "===> ${DIRPRFX}$$entry"; \ + cd ${.CURDIR}/$${entry}; \ + ${MAKE} ${.TARGET:S/realinstall/install/:S/.depend/depend/} DIRPRFX=${DIRPRFX}$$entry/); \ + done +.endif +.if defined(DOCSUBDIR) && !empty(DOCSUBDIR) + @for entry in ${DOCSUBDIR}; do \ + (${ECHODIR} "===> ${DIRPRFX}$$entry"; \ + cd ${.CURDIR}/$${entry}; \ + ${MAKE} ${.TARGET:S/realinstall/install/:S/.depend/depend/} DIRPRFX=${DIRPRFX}$$entry/ ${PARAMS}); \ + done +.endif + + +# +# cruft for generating linuxdoc stuff +# + +.if defined (DOCSUBDIR) && !empty(DOCSUBDIR) + +FORMATS?= "html ascii latin1 ps" +PARAMS= DESTDIR=${DESTDIR} DOCDIR=${WEBBASE}/${WEBDIR} +PARAMS+= DOCOWN=${WEBOWN} DOCGRP=${WEBGRP} +PARAMS+= SGMLOPTS="-ssi -links" FORMATS=${FORMATS} COPY="${COPY}" +#DOCDIR= ${WEBBASE}/${WEBDIR} +#DOCOWN= ${WEBOWN} +#DOCGRP= ${WEBGRP} +#MANMODE= ${WEBMODE} +#PARAMS+= MANGRP=${CGIGRP} MANMODE=${MANMODE} MANOWN=${CGIOWN} + +BATCHSSI= batchssi +HDR= ${.CURDIR}/doc.hdr +FTR= ${.CURDIR}/doc.ftr + +.endif + +# THE END