diff --git a/website/content/en/advocacy/whyusefreebsd.adoc b/website/content/en/advocacy/whyusefreebsd.adoc index fd88ce212a..3f632f7c67 100644 --- a/website/content/en/advocacy/whyusefreebsd.adoc +++ b/website/content/en/advocacy/whyusefreebsd.adoc @@ -1,82 +1,82 @@ --- title: "FreeBSD Advocacy Project" sidenav: about ---- +--- = FreeBSD Advocacy Project == Why Choose FreeBSD? Why would you consider using FreeBSD? We think that there are lots of reasons. Here is a selection of reasons that some of our existing users gave for their choice of operating system. == The Community FreeBSD is a community-driven operating system despite it being to a partial degree sponsored corporately. FreeBSD has active mailing lists, forums, and IRC channels where experienced users and developers are always willing to help the less experienced. The community is largely driven by technology, not ideology, and is focused on building the best possible system and making FreeBSD as widely used as possible, not on pushing any other agendas. There is no dictator—benevolent or otherwise—for the project. The Core Team is elected and is nominally responsible for overseeing the goals of the project, but this is a very light touch. Core mediates disputes between developers, but rarely needs to take an active role in development, beyond their separate contributions as individual developers. == Stability Stability means many different things. FreeBSD very rarely crashes (and when it does it is usually due to hardware faults), but while that was a great boast a decade ago, now it is an expected feature for any operating system. Stability in FreeBSD means much more than that. It means that upgrading the system does not require upgrading the user. Configuration interfaces do change over time, but only when there is a good reason. If you learned how to use FreeBSD in 2000, most of your knowledge would still be relevant. Backwards compatibility is very important to the FreeBSD team, and any release in a major release series is expected to be able to run any code—including kernel modules—that ran on an earlier version. The entire base system is developed together, including the kernel, the core utilities, and the configuration system, so upgrades are usually painless. Included tools like mergemaster help update configuration files with little or no manual intervention. == Early Adoption and Collaboration With Other Projects FreeBSD has been one of the first adopters of the LLVM infrastructure, including the clang compiler and the libc++ stack. The entire FreeBSD system, including kernel and userspace, can build with clang, and from FreeBSD both clang and the permissively-licensed libc++ are included, giving a modern, BSD-licensed C++ stack. Several FreeBSD developers are also active contributors to LLVM, ensuring that both projects thrive together. This same collaboration works downstream, with projects like GhostBSD, MidnightBSD, NomadBSD and pfSense building on top of the FreeBSD base to provide desktop and firewall oriented distributions, respectively. These projects are not forks, they base their work on the latest version of FreeBSD and customize the system for specific uses. == Simple Configuration FreeBSD service initialization is very simple. Each service, whether part of the base system or installed from a port, comes with a script that is responsible for starting and stopping it (and often some other options). The /etc/rc.conf file contains a list of variables for enabling and configuring services. Want to enable ssh? Just add sshd_enable="YES" to your rc.conf file. This system makes it easy to see at a glance everything that will be started when your system boots. The rc system that reads this file understands dependencies between services and so can automatically launch them in parallel, or wait until one is finished before starting the things that it needs. You get all of the benefits of a modern configuration system, without a complex interface. == Ports The ports tree contains a large collection of third-party software, including older versions of some things where the userbase is divided about the benefits of upgrading, and a lot of niche programs. The chances are that anything you want to run which works on FreeBSD will be there. Unlike some other systems, FreeBSD maintains a clean division between the base system and third-party ports and packages. All third-party software goes in /usr/local, so if you want to repurpose a machine, it is trivial to simply delete all installed packages and then start installing the ones that you want. The pkg(8) tool makes working with binary packages even easier, although source installs are still supported for people who want the level of configurability that this implies. == Security Security is vital in any network-connected machine. FreeBSD provides a number of tools for ensuring that you can maintain a secure system, such as: * Jails, allowing you to run applications or entire systems in a sandbox that cannot access the rest of the system. With tools like ezjail and ZFS you can instantly create a new jail with a clone of an existing system, using a tiny amount of disk space, and run untrusted code inside it. * Mandatory Access Control, from the TrustedBSD project, allowing you to configure access control policies for all operating system resources. * Capsicum, from FreeBSD 9 onwards, allows developers to easily implement privilege separation, reducing the impact of compromised code. * The VuXML system for publishing vulnerabilities in ports, which integrates with tools such as pkg, so that your daily security email tells you about any known vulnerabilities in ported software. * Security event auditing, using the BSM standard. And, of course, all of the standard features that are expected from a modern UNIX(R) system including IPSec, SSH, and so on. == ZFS Cheap snapshots, clones, end-to-end checksums, deduplication, compression, and no need to decide partition sizes on install. Using ZFS for a few days makes going back to a more traditional volume manager painful. If you want to test something with ZFS, it is trivial to just create a snapshot and roll back if it didn't work. ZFS lets you clone an existing jail in under a second, no matter how big the jail itself is. == GEOM Even without ZFS, FreeBSD comes with a rich storage system. GEOM layers providers and consumers in arbitrary ways, allowing you to use two networked machines for high-availability storage, use your choice of RAID level, or add features like compression or encryption. == Working Sound FreeBSD 4.x introduced in-kernel sound mixing, so that multiple applications could play sound at the same time even with cheap sound cards with no hardware mixing support. FreeBSD 5.x automatically allocated new channels to applications, without any configuration. Now, FreeBSD has low-latency sound mixing with per-application volume controls and full support for the OSS 4 APIs out of the box. There is no need to configure a userspace sound daemon. The same audio APIs that were used a decade ago still work on FreeBSD, including some compatibility modes to allow applications that try to manipulate the global volume to only change their own. If you want to watch DVDs with 5.1 surround sound, just install your favourite media player and press play. == My System, How I Want It FreeBSD gives you an easy-to-use, working, UNIX(R)-like system. This base system can then be extended easily. If you want to run KDE or GNOME, then just install the metapackage for the version that you prefer. If you want a headless server, then it is equally easy to install the server tools that you want. It is easy to run the FreeBSD installer via a serial port and to configure the entire system from the terminal. It is also easy to install and use an existing desktop environment. The decisions about the kind of system you want to use are left to you. If you are deploying FreeBSD in a corporate environment, then it is very easy to customise both the base system and the set of installed packages for your specific requirements. The build system provides numerous tuneable variables allowing you to build exactly the base system that meets your needs. diff --git a/website/content/en/copyright/freebsd-doc-license.adoc b/website/content/en/copyright/freebsd-doc-license.adoc index 552d37ede4..7c583251e5 100644 --- a/website/content/en/copyright/freebsd-doc-license.adoc +++ b/website/content/en/copyright/freebsd-doc-license.adoc @@ -1,31 +1,31 @@ --- title: "The FreeBSD Documentation License" sidenav: about ---- +--- = The FreeBSD Documentation License Copyright 1994-2021 The FreeBSD Project. All rights reserved. Redistribution and use in source (SGML DocBook) and 'compiled' forms (SGML, HTML, PDF, PostScript, RTF and so forth) with or without modification, are permitted provided that the following conditions are met: . Redistributions of source code (SGML DocBook) must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. . Redistributions in compiled form (transformed to other DTDs, converted to PDF, PostScript, RTF and other formats) 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. THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. == Manual Pages Some FreeBSD manual pages contain text from the _IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX(R)) specification_. These manual pages are subject to the following terms: ____ The Institute of Electrical and Electronics Engineers and The Open Group, 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 FreeBSD manual pages, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright(C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at https://www.opengroup.org/membership/forums/platform/unix. This notice shall appear on any product containing this material. ____ link:..[Legal Home] diff --git a/website/content/en/docs/webresources.adoc b/website/content/en/docs/webresources.adoc index 412ebfc7fb..92f0d5153a 100644 --- a/website/content/en/docs/webresources.adoc +++ b/website/content/en/docs/webresources.adoc @@ -1,42 +1,42 @@ --- title: "Web Resources" sidenav: docs ---- +--- = Web Resources == In the real world... === link:../../press/[FreeBSD in the Press] Articles in the press about FreeBSD. == Newsgroups The following newsgroups contain discussion pertinent to FreeBSD users: * link:news:comp.unix.bsd.freebsd.announce[comp.unix.bsd.freebsd.announce] (moderated) * link:news:comp.unix.bsd.freebsd.misc[comp.unix.bsd.freebsd.misc] * link:news:comp.unix.bsd.misc[comp.unix.bsd.misc] == Additional resources === https://www.freebsdnews.com/[FreeBSDNews.com] FreeBSDNews.com is a blog providing the latest happenings in the FreeBSD community. The articles contain a mix of aggregated news, tutorials and similar. === https://www.bsdnow.tv/[BSD Now] BSD Now is a weekly video podcast spreading the word about the BSD family of operating systems. The show provides an overview on recent developments, but also features interviews, tutorials and help on specific issues by its listeners. === https://bsdmag.org/[BSD MAG] BSD MAG is devoted to BSD and open source solutions, targeting both beginners and experienced users. It is available for free and published on a monthly basis. === http://fxr.watson.org/[The Source Code] If you like digging your fingers into source code, here is a hypertext version of the FreeBSD _kernel_ source. This is brought to you courtesy of Robert Watson. === https://forums.FreeBSD.org[The FreeBSD Forums] The Official FreeBSD Forums, offering a forum dedicated to FreeBSD and FreeBSD aficionados. diff --git a/website/content/en/donations/_index.adoc b/website/content/en/donations/_index.adoc index 6994ec8951..661e3951e5 100644 --- a/website/content/en/donations/_index.adoc +++ b/website/content/en/donations/_index.adoc @@ -1,109 +1,109 @@ --- title: "FreeBSD Donations Liaison" sidenav: about ---- +--- = FreeBSD Donations Liaison == Monetary FreeBSD Foundation Donations The FreeBSD Foundation's fund-raising efforts are essential to keeping FreeBSD free. As the Project grows, so do the costs. By donating to the foundation, you are helping us fund and manage projects, sponsor FreeBSD events, and provide travel grants to FreeBSD developers. You are also helping us represent the Project in executing contracts, license agreements, copyrights, trademarks, and other legal arrangements that require a recognized legal entity. To make a monetary donation to the FreeBSD Foundation, please visit the https://www.freebsdfoundation.org/donate/[FreeBSD Foundation] donation page. == Contents * <<#goal,Donations Liaison Goals>> * <<#charter,Donations Liaison Charter>> * <<#donating,Donating to the FreeBSD Project>> == Other Donations Links * https://wiki.freebsd.org/Donations/WantList[FreeBSD Project Want List] * link:donors[List of FreeBSD Donations] [[goal]] == Project Goal As FreeBSD's userbase has grown, the number of people who want to donate materials or funds to the Project has grown. The Donations Liaison is intended to streamline the handling of these donations, and to ensure that they are handled in a timely and reasonable manner. [[charter]] == Donations Liaison Charter The purpose of the Donations Liaison Office is to encourage and guide donations according to a set of community-accepted rules. The DLO has the following responsibilities. * to establish and maintain a clear set of procedures for handling donations. * to respond to donation offers in a timely manner. * to maintain a list of equipment and resources desired by the FreeBSD community. * to coordinate donation offers with the FreeBSD developer community. * to shepherd donations through the entire donation process. * to work with a small team to ensure a timely, informed, and correct response is available at all times. * to publicly acknowledge donors and donations when the donation is complete. * record the status of all loans to the Project. * provide open records of all donations to the FreeBSD developer community. [[donating]] == Donating to the FreeBSD Project So, you want to donate something to the FreeBSD Project? Great! We strongly rely upon user donations to accomplish our goals. Please read below to see how to contact us about your donation. If you don't know what you want to give, take a look at our https://wiki.freebsd.org/Donations/WantList[list of needs]. We would appreciate any items on this list. If you have equipment you'd like to donate, read on. [[taxcredit]] === Tax Credit for Donations The FreeBSD Foundation can act as a charitable organization for tax purposes. If you live in the United States, your donation can be deducted from your taxes under certain conditions. If you want a receipt for tax purposes your contribution, please let us know when you send information on your donation. A tax credit is not as easy as it might seem. The donations team must be informed of the desire for a tax deduction so the foundation may be notified, and informed when it has been shipped. The Foundation will also need to know when the item has been received by the intended individual. The Foundation must then be able to demonstrate that the donation is in the _public good_. All of this together means that while we probably have developers who would be interested in that big box of ISA cards in your closet, you probably cannot get a tax credit for them; the total work needed to process, ship, and document them far exceeds their total value. The FreeBSD Foundation will provide a receipt for delivery of equipment. They will not, however, provide a fair-market valuation of the equipment -- in fact, the law forbids them to do so. We recommend checking elsewhere for valuations of hardware donations. Since many of our donations are obsolete, making fair market value hard to judge, we suggest searching on Ebay or other used equipment sites for prices paid for similar equipment. To receive a tax receipt for a donation, you will need to complete a https://www.freebsdfoundation.org/wp-content/uploads/2015/12/Hardware-Donation-Form.pdf[Hardware Donation Form] from the FreeBSD Foundation website. === How to Donate Part of the goal of the Donations Liaison Office is to match donations with developers who can use them. We don't accept just any donation; we only handle those that have a home with a developer who can use them to improve FreeBSD. This saves time all around, and also helps assure donors that what their contributions are actually supporting the FreeBSD Project. The down side is that we need some information about your donation before accepting it. Donations generally fall into three categories: * <<#money,Financial>> * <<#systems,Complete Computers>> * <<#components,Computer Components>> If you have something to offer that doesn't fall into one of these categories, don't fret! Just contact us at donations@FreeBSD.org with your offer. Just because it's not the run-of-the-mill offer doesn't mean that we're not interested. [[money]] === Financial Contributions The FreeBSD Project does not directly accept financial contributions. A sponsor organization, the https://www.freebsdfoundation.org[FreeBSD Foundation], accepts financial contributions for us. Please see their Web site for details on financial contributions. [[systems]] === Complete Computer Systems The FreeBSD Project always needs computers. If you have a computer that you would like to donate to the Project, please contact us with the following information: * Hardware specifications: architecture, motherboard, CPU, disk space, memory. * Does this system currently run FreeBSD, or is it unsupported? If possible, please attach a dmesg from a FreeBSD install on this system. * Are you willing to ship this system? * Your physical location. We try to make shipping as easy and inexpensive as possible. * Also mention if you want a <<#taxcredit,tax credit>> for this system. (Note that not all donations can realistically receive a tax credit, as the cost of supplying the credit may exceed the value of the donation.) [[components]] === Computer Components If you have hardware that you would like to donate to the Project, please contact us with the following information: * The hardware description: model, part number, manufacturer, etc. If you have an exact link to the manufacturer's Web page for this component, that would be helpful. * Is this hardware currently supported in FreeBSD? * What documentation do you have? A piece of hardware is not sufficient to write a driver; driver authors need detailed chipset data from the manufacturer. (Don't worry too much if you don't have this documentation, as it may be available elsewhere.) * Are you willing to ship this system? * Your physical location. We try to make shipping as easy and inexpensive as possible. * Also mention if you want a <<#taxcredit,tax credit>> for this hardware. (Note that not all donations can realistically receive a tax credit, as the cost of supplying the credit may exceed the value of the donation.) === What we Do with this Information Once we have a description of the donation, the Donations Liaison Office will contact the developer community and offer the resource to them. If we have a developer who would like the item, we put the donor and the recipient in contact and let them work out shipping information. If there are multiple developers interested in a resource, we try to learn what each developer would use the resource for and allocate it most effectively for the Project. If no developer is interested, we turn down the offer. Our goal is to place (or decline) all donations within 7 days of receipt of complete information. diff --git a/website/content/en/donations/donors.adoc b/website/content/en/donations/donors.adoc index 22780bf1fe..829b813d50 100644 --- a/website/content/en/donations/donors.adoc +++ b/website/content/en/donations/donors.adoc @@ -1,452 +1,452 @@ --- title: "Hardware Donors Page" sidenav: about ---- +--- = Hardware Donors Page This page keeps a record of current hardware transactions taking place under the donations team. These are only completed or believed to be completed transactions. If something was offered but never shipped to anyone, please do not list it here. If you see any mistakes, please send an email to trhodes@FreeBSD.org so that I may correct it. Feel free to cc: donations@FreeBSD.org as well. [.tblbasic] [width="100%",cols="25%,25%,25%,25%",options="header",] |=== |FROM |ITEM |TO |STATUS |nsayer |4-port Zynx 'dc' NIC |jlemon |Unknown |Sebastian Trahm |Packet Engines G-NICII 1000SX/PCI |will |Received |donxc |ATI Rage Pro 128 |anholt |Shipped |Stephen Hoover |Pentium III 1GHz 133FSB, 512MB PC133 RAM, Asus TUSL2-C motherboard (815EP chipset), Intel 82559 (PILA8460B) 10/100 NIC, 52X CD-ROM, floppy, case w/250W power supply w/case fan |kris |Received |Salvatore Denaro |512MB DDR ECC DIMM |obrien |Received |Frank Nikolajsen |Three 533MHz 21164A CPU PC164SX (AlphaPC) motherboards |Ports Cluster (obrien/peter) |Received |William Gnadt |PCMCIA CD-ROM drive (Addonics), USB 1.1 HD enclosure w/850MB HD |imp, bsd |CD-ROM shipped to imp, HD enclosure shipped to bsd |William Gnadt |Seagate Cheetah 10K RPM 9GB UW-SCSI HD Model: ST19101W / 68-pin connector, new dual-fan HD cooler |dannyboy |Received |William Gnadt |Dell Inspiron 3000 laptop (Pentium 266MHz, 64MB RAM, floppy and CD-ROM drives, docking station, PCMCIA Ethernet/modem card, extra power supply -- good condition |imp |Received |William Gnadt |PCMCIA cards: "New Media" 28.8 modem (unknown model #), Linksys 33.6 LANmodem (model PCMLM36), Linksys combo ethernet card (model EC2T), 3COM 3C905B Ethernet 10/100B-T network adapter (PCI) |PCMCIA cards to imp, 3COM nic to silby |PCMCIA cards shipped. 3COM nic shipped. |William Gnadt |2.5" laptop HDs: Toshiba HDD2714 - 1443MB Toshiba HDD2731 - 1083MB |darrenr |Awaiting Shipment |William Gnadt |68-pin M-M SCSI cable 1 meter (brand new) |mwlucas |Received |Simon Chang |Dual Pentium Pro 200MHz (both CPUs and VRMs included), 128 MB of RAM 10-GB IDE hard disk drive, IDE CD-ROM drive, one old 3Com 3C509B-TPO network card |will |Received |gj |pc164 (Alpha) |sos |Received |Michael Hembo |4 * 512 MB PC133 SIMM (for ftp.FreeBSD.org) |jesper |Received |trhodes |40GB IDE HDD |rwatson |Received |jesper on behalf of TDC Tele Danmark |AlphaStation 255/233 |sos |Received | |384MB RAM for an AlphaStation 500 |wilko |Received |DEC/Compaq |AS2100 SMP |trevor |Received |wilko, on behalf of Compaq |DS10 |murray, obrien, package cluster |Received |wilko, on behalf of HP |AlphaServer 1000A |markm |Received |Rolf Huisman |Abit BP6 dual CPU mainboard |wilko |Received |Stefan Molnar |Sun X6540A dual-channel Symbios 53C876 SCSI card (w/FCode) |jake |Received |obrien |Hitachi ATAPI CDR-7730 cdrom drive |sos |Received |obrien |DEC Alpha PWS 2MB B-cache module |gallatin |Received |obrien |fxp(4), xl(4), pcn(4), dc(4) NIC's; Adaptec AHA-2940UW; Sun HD/68-pin UW-SCSI cable |jake |Received |obrien |KVM Switch |kris |Received |obrien |several AMD Athlon Slot-A 8[05]0 MHz CPUs |gshapiro,gj,fjoe,wilko,mdodd |all received |obrien |AMD Athlon Slot-A 800 MHz CPU + Gigabyte GA-7IXE motherboard + 256 MB RAM |kris |Received |obrien |2x550 MHz Pentium-III system with 256MB RAM, CDROM, multiple NIC's |scottl |Received |obrien |nVidia GeForce2 Pro, GeForce 256, Riva TNT2, Riva TNT AGP video cards. nVidia GeForce2 MX400, MX200, TNT2 PCI video cards. |mdodd |Received |obrien |two Sun SPARCengine AXi "Panther" 300MHz UltraSparc-IIi with 256MB RAM, 9GB SCSI UW disk |FreeBSD.org cluster, and scottl |Received |obrien |Sun Ultra-1 with 128MB RAM, CDROM, 2GB SCA disk |scottl |Received |obrien |two fxp(4), one pcn(4) Ethernet cards |rwatson |Received |obrien |AMD Slot-A 900 MHz CPU + Gigabyte GA-7IXE motherboard + 128MB RAM + 10 GB and 8 GB IDE disks + 3Com 905c-TX + nVidia GeForce2 GTS 64MB AGP video card |jake |Received |obrien |Matrox G400 AGP dual-head, 2x Celeron 366 MHz socket-370 CPUs, Athlon 900 Slot-A CPU, PC100 DIMMs |wilko |Received |obrien |Adaptec 3940UW |njl |Received |obrien |two Aureal Vortex 2 sound card |des and petef |Received |obrien |pair of AMD Opteron 246 CPUs |kan |Received |obrien |pair of AMD Opteron 244 CPUs |phk |Received |obrien |AMD Opteron 244 CPU |sos |Received |obrien |AMD Athlon64 desktop: 3400+ CPU, 512MB RAM, IDE hard disk, 3Com 3c905c NIC, DVD-ROM drive, nVidia AGP video, floppy, case, power supply |kris |Received |obrien |AMD Athlon64 desktop: 3200+ CPU, 512MB DDR333 RAM, two 60GB IDE hard disks, 3Com 3c996b gigE NIC, 3Com 3c905c NIC, DVD-ROM drive, nVidia GeForce2 GTS AGP video, floppy, case, power supply |bde (shipped thru peter) |Received |obrien |AMD Athlon XP 2800+ Barton CPU |bde (shipped thru peter) |Received |obrien |six 9GB SCSI LVD disks (2 SCA, 4 68-pin) |scottl |Received |obrien |DEC Alpha 164SX motherboard, PC164SX 533 MHz CPU, 128MB ECC PC100 RAM, Adaptec AHA-2940UW SCSI controller, Matrox PCI video card |ru |Received (handcarried to .nl by marks, shipped to ru by wilko) |obrien |AMD Opteron 850 CPU, 2 x AMD Opteron 254 CPU |ru |Received |obrien |pair of AMD Athlon-MP 2400+ CPUs, Tyan K7 Thunder motherboard, power supply, 1MB DDR266 DIMM |imp |Received |obrien |AMD Athlon64 3000+ CPU |murray |Received |obrien |AMD Athlon64 3200+ CPU |davidxu |Received |obrien |MSI AMD Athlon Slot-A motherboard, ATX form factor |trhodes |Received |obrien |AMD Opteron 150 CPU, ASUS SK8N motherboard, 2GB RAM, DVD-ROM |krion |Received |obrien |Pair of AMD Opteron 850 CPUs |alc |Received |gordont |Sun Ultra-2 SMP 400 MHz with 1GB RAM, 2x 4GB SCA disks |jake |Received |gordont |Sun Ultra-2 200 MHz with 512MB RAM, 2GB SCA disk |obrien |Received |Nick Jeffrey |2x 9GB SCA SCSI disks |jake |Received |kan |Matrox Millennium II PCI video card |nsouch |Received |wilko |Winbond ISDN card |hm |Received |wilko |21264/550 EV6 Alpha CPU |obrien |Received |wilko |Athlon 850 Slot-A, 64MB DIMM |fjoe |Received |NcFTP Software / Mike Gleason |NcFTPd Server site license for FreeBSD.org |jesper |Received |Michael Dexter |Yamaha SCSI CDRW drive |wilko |Received |wilko |Cologne Chip Design PCI ISDN card and Compaq ISA ISDN card |hm |Received |William Gnadt |IBM Travelstar DJSA-210 Laptop Hard Drive, 10.06GB |jesper |Received |mbr |10 Gigabyte Hard Disk Drive |sos |Awaiting Shipment |The Open Group |Single UNIX(R) Specification (Version 3) books and CD-ROMs. |mike (and -standards) |Received |William Gnadt |SoundBlaster 128 PCI |mike |Received |Matt Douhan |Two Sony AIT-1 tape drives |will |Received |William Gnadt |Toshiba MK6411MAT, 6495MB |des |Received |wilko, on behalf of HP |AlphaServer 1000A |phk |Received |brueffer |SMC Etherpower II (tx) NIC |mux |Received |Mike Tancsa, Sentex |2 remote machines: + *releng4.sentex.ca:* Intel Celeron CPU 2.00GHz (2000.35-MHz 686-class CPU) real memory = 528416768 (516032K bytes), 19595MB QUANTUM FIREBALLP LM20.5 UDMA66 + *releng5.sentex.ca:* Intel Pentium III/Pentium III Xeon/Celeron (866.38-MHz 686-class CPU) real memory = 796852224 (759 MB), 19595MB QUANTUM FIREBALLP LM20.5 UDMA66 |FreeBSD Security Team (nectar) |In use |Mike Tancsa |IBM smart cards (PCMCIA and serial port) |des |Received |fenner |AST FourPort/XN ISA serial card |jwd |Received |Ryan Petersen |Sun Microsystems Sparc Ultra 5 |FreeBSD.org cluster |Received |Chris Knight |56K PCMCIA Data/Fax modem |trhodes |Received |wes |Dual processor motherboard for Intel Celerons |des |Received |Craig Rodrigues |ATI Graphics Xpression PCI 2 MB |nsouch |Received |Gregory P. Smith |DEC Alpha PC164SX mobo+CPU, 2x 64MB ECC DIMM's, UW SCSI controller, 10/100 NIC |wilko |Received |gallatin |Alpha 433au system |will |Received |Brian Cunnie |DDS-3 scsi tape drive (12GB raw/24GB compr), SCSI terminator, SCSI cable (50-pin hi-density single-ended), and several DDS-3 tapes. |kris |Received |unfurl |Dual Pentium 550MHz system |rwatson |Received |James Pace |HP Omnibook 4000 ct 4/100, and an HP Omnibook 5000 cts 5/90 model 1200 |imp |Received |murray |Hard copy of Docbook: The Definite Guide |ceri |Received |Christoph Franke |1.5GB SyJet |gj |Received |Christoph Franke |IBM DDRS-39130 SCSI LVD/SE Harddisk |des |Received |Christoph Franke |IBM DDRS-34560 SCSI SE Harddisk, Plextor PX-20TSi SCSI CDROM Drive |ru |Received |Christoph Franke |IOMEGA Zip Drive SCSI 100 MB (incl. 2 Medias) |phk |Shipped |ETEK, Chalmers |Compaq XP1000: DECchip 21264A-9 667MHz, 640MB RAM |obrien |Received |ceri |A well-supported 4 serial port PCI card |wilko |Received |Mike Ray |MIPS R4000 Microprocessor User's Manual |jmallett |Received |wilko |3 FC disks |phk |Received |wilko, on behalf of HP |AlphaServer 4100 |ticso |Received |wilko, on behalf of HP |AlphaStation 200 |ceri |Received |Brian Cunnie |40+gb IDE drive |eric |Received |Jared_Valentine@3com.com |crypto devices (pci, pcmcia, cardbus cards, CPUs with builtin crypto+support, 3Com 3CR990, 3CRFW102/103 PC Cards w/ 3DES |sam |Shipped? |Jared_Valentine@3com.com |3Com XJack Wireless PC Card |imp |Shipped? |Jared_Valentine@3com.com |A 3Com 3XP 3CR990-TX Typhoon txp(4) card |will |Received |Jared_Valentine@3com.com |A 3com 3CXFE575CT Cardbus NIC |arved |Received |wilko, on behalf of HP |AlphaServer 4100 |Fruitsalad.org; for KDE development |Received |David Leimbach |One SATA controller |sos |Shipped? |David Leimbach |G3 (blue and white) for the PPC project |obrien |Shipped? |Gavin Atkinson |2 x 8gb IDE drives |brueffer |Received |Jonathan Drews |New motherboard, 1GB DDR2100 RAM, LSI Logic Ultra160 SCSI controller, and two 18GB Maxtor 10K III disks for 2003 edition of cvsup12.FreeBSD.org |will |Received |Jim Dutton |512MB of DDR2100 RAM |will |Received |www.servercommunity.de |2 IDE 3.5" 40GB for FreeBSD/alpha test machines |wilko |Received |Mike Miller |HP Kayak XU (model D8430T) dual Pentium III 450MHz, 512MB RAM, 36GB, 15krpm IBM OEM SCSI drive, Matrox G200 video card, Intel gigabit and 10/100 NIC, Intel 440BX chip set |deischen |Received |Linuxtag FreeBSD Team |Adaptec ANA 62022 NIC |mux |Received |Robin Brocks |Two 256MB registered ECC PC133 DIMMs |tmm |Received |Michael Dexter |serial-port Towitoko reader, and three crypto cards. |des |Received |Michael Dexter |Sony VAIO subnotebook |wilko |Received |Michael Dexter |HPT1540 SATA RAID controller, PATA-SATA dongles, 2 ATA controllers Sil0680 + Promise |sos |Received |www.servercommunity.de |One of each of the following NICs: SIS 900, Dec 21143, NatSem 83820 |mbr |Received |Intel Corporation |Commercial Intel C/C++ compiler license |FreeBSD.org cluster (netchild) |Received |wilko |Fore ATM card |des |Received |www.servercommunity.de |20 Gigabyte IBM Laptop Hard Drive |trhodes |Received |www.servercommunity.de |Pentium 4, 2,4 GHz, FSB800, 1 GB RAM Samsung PC3200, Altec DVD 16x/48x, 80 GB Maxtor IDE ATA133 (slightly used), 2 * 80 GB Maxtor SATA as RAID0, ATI Radeon 9200SE clone graphic card, 3,5" TEAC floppy, 420 Watt ATX be quit! ultra low noise power supply, and Athena CM03 case. |netchild |Received |Joe Altman |PCI Sound card |kris |Received |Daniel , Seuffert & Waidmann |two UltraSparc-II 300MHz (X1191A) CPU's |obrien |Received |Daniel , Seuffert & Waidmann |128MB PC133 Registered ECC DIMM for Sun Blade 100 |obrien |Received |Daniel , Seuffert & Waidmann |4x 128MB PC100 Registered ECC DIMM for Alpha UP2000 |obrien |Received |Daniel , Seuffert & Waidmann |G4Port serial adapter for Apple G4 |obrien |Received |Daniel , Seuffert & Waidmann |Sun 13W3(male) to VGA 15pin(female) converter |wilko |Received |Daniel , Seuffert & Waidmann |1 Intel EtherExpress 100 NIC, bulk, new + 1 Seagate ST380011A, 80 GB IDE, new + 1 50 PIN SCSI cable, new + 1 Adaptec 2940 UW, used, tested + 1 Seagate Streamer Travan 20 GB, used, tested + 1 compu-shack SSW-503 5 port switch, 100 Mbit, new + |lioux |Received |Daniel , Seuffert & Waidmann |8 GBic copper modules, FDDI concentrator, and two cables. |phk |8GBic modules are in transet, others Received |Daniel , Seuffert & Waidmann |SGI 1100 motherboard replacement |rwatson |Received |Artem Koltsov |1 PC100 128MB dimm |njl |Received |Artem Koltsov |ATA100 PCI Card2 IDE ports with IDE 100 Cables, Ultra100, PROMISE TECHNOLOGY, ULTRA100 |petef |Received |Artem Koltsov |SDRAM DIMM 128MB PC133 CL2, Micron Technology, CT16M64S4D7E.16T SDRAM DIMM 128MB PC133, SDRAM DIMM 128MB PC100, Motherboard S1598 Socket 7 with AMD K6 450MHz + IDE Cables, Trinity ATX, Tyan and AMD, S1598, and an IBM HDD IDE 9.1GB, DJNA-370910 |fjoe |Received |Artem Koltsov |A PS2 Mouse 2 Buttons, M-S34,Compaq, 166861-001 and a PS2 Mouse 3 Buttons, M-CAC64, Labtec, 851680-0000 |mikeh |Received |Dynacom Tankers Mgmt LTD |Sun Ultra 10 |mux |Received |Jon |Samsung 8x8x32 CDRW |rwatson |Received |wilko |Abit BP6 mainboard incl. CPUs |nsouch |Received |Daniel , Seuffert & Waidmann |SUN SPARC Clone 4x400MHz 1GB RAM 36GB RAID System |krion |Received |Sten Spans |AlphaStation 500 |philip |Received |mjacob |AlphaServer 4100 SMP |the FreeBSD cluster at Yahoo! (via obrien) |Still in holding pattern awaiting placement in cluster |trevor |Sun Ultra 1 and GDM-17E20 |jmg |Received |Daniel , Seuffert & Waidmann |A 13W3 Female To DB15HD Male adapter (Sun monitor to VGA) |ceri |Received |Daniel , Seuffert & Waidmann |"XML in a Nutshell" (O'Reilly) and a PCMCIA WLan Adapter |josef |Received |wilko |Digital NoName Alpha mainboard |ru |Received |Daniel , Seuffert & Waidmann |External SCSI enclosure, 4 1.2GB SCSI disks |le |Received |Jon Noack |Two 32-bit if_em Intel PRO/1000 MT Desktop Adapters |rwatson |Received |Remi |Sony VAIO PCG818 |njl (passed to imp when use has ended) |Received by njl |Daniel , Seuffert & Waidmann |BT878 PAL TV-card with a MSP340x/MSP341x |alex |Received |Christoph Franke |Pentium IV 2.0 GHz, Asus P4B266, 1 GB Ram (Infineon CL2), Adaptec 29160 SCSI Controller, Tekram DC390-U2W SCSI Controller, Seagate 36 GB 10.000rpm HDD, Plextor Ultra-Plex 40 Max SCSI CDROM, Fujitsu GígaMO Drive (1,3 GB capacity incl. 4 media), Adaptec Duo Connect Firewire/USB 2.0 Controller, 3Com 905C Ethernet Card, Turtlebeach Santa Cruz Soundcard PCI, Floppy Drive, Chieftec Big Tower Case (Noise-Controlled) |mlaier |Received |"scottgannon@mail.ellijay.com" |slot1 600MHz P3 CPU |imp |Received |Oliver Fuckner |3Com 3CR990 Typhoon/Sidewinder (txp(4)) NIC. |obrien |Received |Daniel , Seuffert & Waidmann |Sun Enterprise 450, 2x250MHz Ultra Sparc CPUs, 512MB RAM, 2x36GB (Seagate ST336705LC 5063) SCSI disk drives, 1x4GB (Seagate ST34371W SUN4.2G 7462) SCSI disk drive and a Streamer DDS3-DAT (HP C1537A), Intel PRO/1000 (em(4)) NIC |arved |Received |Daniel , Seuffert & Waidmann |256MB Ram (Sun Original #501-5691) |krion |Received |Daniel , Seuffert & Waidmann |1U Rackmount Intel Celeron 2.6GHz, 533MHz compat. motherboard, 256MB PC2100 DDR 266MHz RAM, Savage8 3D Video Accelerator, 80GB 7200rpm ATA100 IDE Harddrive, Integrated 10/100 LAN VT8233 |trhodes |Received |Daniel , Seuffert & Waidmann |Athena CM-03 case silver with be quiet! 350 Watt ATX 1.3, Asus motherboard A7V600, Athlon XP 2800+ processor with Artic copper cooling, 512 MB Ram Infineon PC3200, AOpen DVD 1648 silver, Floppy silver, Seagate ST380011A 80 GB IDE, xelo GeForce2 MX400 |josef |Received |"Darrell" |Abit VP6 Motherboard w/raid, 2 Intel 1ghz CPUs, 1 gig PC 133 ram, Nvidia video card, Sound Blaster PCI sound card, DVD Player, CD-RW, Floppy Drive, Case, Power Supply |mikeh |Received |Aled Morris |Netgear GA302T NIC for testing bge(4) |yar |Received |wilko |Fore ATM card |philip |Received |Daniel , Seuffert & Waidmann |Chicago Manual of Style, 15th Edition |ceri |Received |Daniel , Seuffert & Waidmann |Quantum Atlas 10KIII 3,5" 73,4 GB |brueffer |Received |Chris Knight |Several books, Assembly Step-by-step, TCP Illustrated Vol.2 and HTTP: The Definitive Guide. |hmp |Received |Daniel , Seuffert & Waidmann |Hitachi 5K80 (2,5", 80 GB), USB-to-serial adapter, 5.25" enclosure with USB2 and IEEE1394 ports, IEEE1394 PCI card |netchild |Received |Daniel , Seuffert & Waidmann |External 60 GB USB2 disk |le |Received |Daniel , Seuffert & Waidmann |Fee for EuroBSDCon tutorial |josef |Received |Daniel , Seuffert & Waidmann |Funds for a laptop |ceri |Received |ceri |Dual Pentium 3 motherboard plus processors |vs |Received |http://www.netapp.com/[Network Appliance] |NetApp F825 filer with 2 terabytes of storage |FreeBSD.org cluster |Received |Daniel , Seuffert & Waidmann |2 256MB DIMMs for AlphaStation DS10 |wilko |Received |Daniel , Seuffert & Waidmann |4 256MB DIMMs for an AlphaPC164sx |wilko |Received |Daniel , Seuffert & Waidmann |copy of the ANSI T1.617-1991 standard |rik |Received |Daniel , Seuffert & Waidmann |3,5" Floppy Samsung with cable, CD-Rom Toshiba , 2 Intel XEON 1,8 GHz, socket 603 with cooler, 2 SCSI-3 68 pin-68 pin cable extern, 7 SCSI-disks 9,1 GB Seagate Barracuda ST319171 WC, 2 SCSI-disks 18,2 GB Seagate Barracuda ST318275FC fibre channel, 3 SCSI-disks 9,1 GB IBM DNES-309170 , 1 external SCSI-enclosure hot plug Chieftec CT-1034, 8 SCA-adaptors LVD, 1 QLogic fibre channel adapter, 1 Intel 1000 Pro MT NIC, 1 ICP Vortex SCSI raid controller GDT7519RN fibre channel, 1 Adaptec 39160 dual channel SCSI controller 64bit LVD, 1 SCSI-LVD 7+1 cable internal with terminator, 1 INTEL SHG2 DUAL XEON mainboard new, 2x 512MB DDR SDRAM's PC1600-CL2 Samsung M383L6420BT1-CA0 |pjd |Received |Daniel , Seuffert & Waidmann |1 8 port Gigabit switch Netgear GS108, 1 new system: Athlon XP 2800+, 1 GB Ram (2 * 512 GB Infineon PC 3200), AOpen DVD 1648, Athena CM03 case silver, Floppy, Asrock motherboard, GForce 4, 80 GB Seagate IDE 3,5", 353 Watt Enermaxx power supply. |mux |Received |Daniel , Seuffert & Waidmann |1 NetGear GA302 |jesper |Shipped |David |1 Alpha Motherboard |kensmith |Received |wilko |Sun Creator3D UPA graphics card |trhodes |Received |http://www.tunix.nl/[Tunix B.V.] |ATX tabletop case for my AlphaPC 164sx |wilko |Received |Daniel , Seuffert & Waidmann |16Mb flash for Cisco |rik |Received |Daniel , Seuffert & Waidmann |Cisco 2600 (64M memory/8M flash) + X.21 cable |rik |Received |Daniel , Seuffert & Waidmann |Entrance fee for the EuroBSDCon 2004 |brueffer |Received |Gavin Atkinson |Pair of fxp(4) cards |ceri |Received |Daniel , Seuffert & Waidmann |NetGear GA302T bge(4) |jesper |Received |philip |2x Sun Ultra10 workstation |will |Received |Daniel , Seuffert & Waidmann a| Hardware for laptop: Pentium III Mobile 600MHz CPU, 2 128MB PC100 SODIMM RAM, new battery, Netgear WG511T CardBus adapter AMD64 desktop: ASUS SK8N motherboard, AMD Opteron 240 CPU, Arctic Cooling Silencer 64 Ultra TC, 2 512MB ECC RAM (Kingston), AOpen Combo drive (COM4824), 4 80GB IDE PATA, NVIDIA GeForce4 MX 440 AGP 8X video, 3.5" floppy, Athena CM03 case, 350 Watt Be Quiet! power supply, S/PDIF out module, 17" LCD monitor Acer AL1715 Hardware for Alpha: 4 128MB ECC RAM (Samsung), 18GB SCSI (Fujitsu MAA3182SC) with cable RTL8139 Ethernet CardBus adapter, 2 Intel PRO/1000 MT desktop adapters, 5-port 100Mbps Ethernet switch Flight to Germany and entrance fee for the EuroBSDCon 2004 |ru |Received |Daniel , Seuffert & Waidmann |2 512MB ECC RAM (Kingston), 2 80GB SATA (Maxtor DiamondMax Plus 9) for RAID1, 2 80GB PATA, NVIDIA GeForce4 MX 440 AGP 8X video, ASUS SK8N motherboard, 350 Watt Enermax SLN power supply, 3.5" floppy, Toshiba DVD-ROM, Athena CM03 case, AMD Opteron CPU, Arctic Cooling Silencer 64 TC, set of reserve coolers |phantom |Received |Daniel , Seuffert & Waidmann |SPEC JBB2000 benchmarking software |phantom |Received |Daniel , Seuffert & Waidmann |keyboard with US layout |josef |Received |Daniel , Seuffert & Waidmann |Adaptec 39160 dual channel SCSI controller 64bit LVD, 36GB SCSI HDD (HITACHI DK32EJ36NSUN36G) |markus |Received |philip |Sun Ultra10 workstation |thierry |Received |Daniel , Seuffert & Waidmann |4 memory DIMMs for AlphaServer DS10 |wilko |Received |wilko |AlphaStation 500 5/266 workstation |dinoex |Received |philip |Sun Ultra10 workstation |brueffer |Received |wilko |2x Seagate Barracuda 9.1GB SCA SCSI disk |philip |Received |http://www.absolight.fr/[Absolight] |Entrance fee for the EuroBSDCon 2004 |mat |Received |Daniel , Seuffert & Waidmann |2x Seagate ST 380011A, 3.5" disk |clement |Received |Daniel , Seuffert & Waidmann |8x 64M Sun memory |philip |Received |Daniel , Seuffert & Waidmann |Netgear GS608 Gigabit Ethernet switch |wilko |Received |Sebastian Trahm |Specialix SX RS232 concentrator |des |Received |Daniel , Seuffert & Waidmann |Netgear GA302T Gigabit Ethernet NIC |brueffer |Received |Jürgen Dankoweit |Madge Smart MK4 PCI Token Ring adapter |philip |Received |Daniel , Seuffert & Waidmann |Cisco 2600, NM-16A, 2x octopus serial cable |philip |Received |Warren Block |Tecra 8000 |imp |Received |Michael Dexter |Apple Power Macintosh G4 machine |gallatin |Received |Michael Dexter |NCD Explora 451 PPC Thin Client |obrien |Received |Juergen Dankoweit |Unsupported CF-Card reader |josef |Received |pav |Two O'Reilly security books |josef |Received |ds |em(4) compatible gigE card, 1000baseTX (copper) interface |wilko |Received |keramida |Copy of "Cascading Style Sheets: The Definitive Guide" (O'Reilly), ISBN 0-596-00525-3. |ceri |Received |Daniel , Seuffert & Waidmann |PCMCIA FireWire controller |brueffer |Received |Daniel , Seuffert & Waidmann |IBM Laptop AC Adapter |mlaier |Received |Daniel , Seuffert & Waidmann |75 EUR (for ISP) |josef |Received |Daniel , Seuffert & Waidmann |Power Battery for IBM Thinkpad T20 |glebius |Received |Daniel , Seuffert & Waidmann |40 Gb notebook HDD |glebius |Received |maxim |http://www.awprofessional.com/title/0201702452[The Design and Implementation of the FreeBSD Operating System] |glebius |Received |Daniel , Seuffert & Waidmann |Funds for a laptop |markus |Received |ds |Funds for a D-Link DWL-AG530 PCI card for ath(4) and wpa_supplicant testing. |brooks |Received |Daniel , Seuffert & Waidmann |UltraSPARC IIi 300MHz CPU, 4.3G SCA disk, 18.2G SCA disk. |philip |Received |Daniel , Seuffert & Waidmann |Funds for a SATA HDD. |ceri |Received |Daniel , Seuffert & Waidmann |2 Intel 100 MBit NICs, 1 be quiet! 350 Watt power supply, 1 DVD Toshiba SD-1912, 1 floppy TEAC FD-235HF, 2 Kingston KVR266X72RC25/512 (1 GB), 1 NVidia MX 4000 graphic card, 1 Ultra Silencer TC cooler, 1 AMD Opteron 144 1.8 GHz, 1 Asus SK8N mobo, 1 Seagate ST380011A HDD (80GB ATA). |clement |Received |Daniel , Seuffert & Waidmann |1x Sun Ultra60, 768M memory, 2x SCA disk |philip |Received |Daniel , Seuffert & Waidmann |AMD64 server : ASUS SK8N motherboard, AMD Opteron 144 1.8Ghz CPU, Arctic Cooling Silencer 64 Ultra TC, 2 512MB RAM (Kingston), 80GB IDE, ATI Rage 128 PRO ULTRA Video Controller |simon |Received |obrien |4x Athlon MP 2400+ CPUs with HSFs |will |Received |obrien |4x Opteron 844 CPU's |alc |Received |obrien |4x Opteron 875 dual-core CPU's |alc |Received |obrien |Opteron 275 dual-core Tyan K8W system |alc |Received |obrien |2x Opteron 270 dual-core CPU's, Athlon64 3200+ CPU |kan |Received |obrien |2x Opteron 252 CPU's |kensmith |Received |obrien |Athlon64 4600+ X2 dual-core and Athlon64 3800+, Gigabyte and Asus PCI-express motherboards |scottl |Received |obrien |Quad Opteron 870 dual-core system |jeffr |Received |will |2x Athlon XP 2200+ CPUs with HSFs, 1 Sun Seagate 20GB HDD |obrien |Received |marcus |1 Maxtor Atlas 15K U320 8C018L0 SCSI disk for cvsup12 |will |Received |Jonathan Drews |1 copy of the "Design and Implementation of the FreeBSD Operating System" via gift certificate |will |Received |Daniel , Seuffert & Waidmann |4x Seagate ST173404LCV disks |philip |Received |Daniel , Seuffert & Waidmann |1 copy of the "The AWK Programming Language" Aho, Alfred and 1 copy of the "Compilers" Aho, Alfred |krion |Received |http://www.LF.net[LF.net] |Flight to Canada and accommodation fee for BSDCan 2005 |krion |Received |Daniel , Seuffert & Waidmann |i386 machine : Athlon XP2800+, Asus A7V600, Seagate ST 380011A IDE, 80 GB, Maxtor Diamondmax 10 120 GB, NVidia Gforce 2 MX 400, 1 GB Ram (2 x Infineon 512 MB DDR, PC 2700), Compushack 100 MBit NIC, RTL 8139 clone. |krion |Received |Daniel , Seuffert & Waidmann |17" monitor LCD Acer 1715-sn |krion |Received |wilko |Pentium Pro processor and heatsink |des |Received |Denis Kozjak and Daniel Seuffert |ASUS A7M266-D, 2x AMD Athlon MP 2000+, 2x CPU Fan, 512 MB RAM, 400W PSU. |marks |Received |Daniel , Seuffert & Waidmann |Funds for a notebook |philip |Received |Daniel , Seuffert & Waidmann |Tyan Thunder SE7500WV2 dual Xeon board and 2 x 512 MB DDR PC 1600 registered DDR-ram. |Peter Holm, Denmark |Received |Daniel , Seuffert & Waidmann |Financial help with transportation to BSDCan. |mlaier |Received |Hartmut Obst |Q-Tec 5 Port Switch |mlaier |Received |Daniel , Seuffert & Waidmann |Netgear WG511T ath(4) card. |wilko |Received |Brennan Stehling |Four Java books: The Java Virtual Machine Specification, Java Virtual Machine, Programming for the Java Virtual Machine and The Java Native Interface. |glewis |Received |Frank Seuberth - Rentable Hardware Systeme & Consulting |2x Sun Ultra 2 machines |philip |Received |Gary Jennejohn |Fujitsu-Siemens Lifebook laptop with accessories. |markm |Received |Andreas Kohn |DEC PBXGA "TGA" card. |marcel |Received |ds |SMP mainboard with 2x Xeon 1.8GHz plus RAM |Peter Holm |Received |wilko |AlphaStation 600 |ticso |Received |wilko |Adaptec AH-2940UW |mwlucas |Received |obrien |2x AMD Opteron 250 CPU's |scottl |Received |obrien |Arima HDAMA dual processor motherboard + 2x AMD Opteron 250 CPU's |imp |Received |Markus Deubel |Sun Ultra 10 440 |marius |Received |Chris Elsworth |Sun Fire v210 |philip |Received |ceri |Apple USB keyboard (US layout) for my Mac Mini |wilko |Received |David Boyd |SCSI enclosure, lots of hard drives, terminators, cables and accessories |mwlucas |Received |Mark |Cisco Catalyst 1900 switch |trhodes |Received |Alexis Lê-Quôc |One copy of "The Elements of Typographic Style" by Robert Bringhurst, Hartley & Marks Publishers; 3rd edition (2004). ISBN: 0-88179-206-3. |blackend |Received |Sun W. Kim from tekgems.com |Gigabit NIC |jcamou |Received |Mark |CISCO 1900 Series switch |trhodes |Received |obrien |2 x AMD Opteron 275 CPU |mlaier |Received |obrien |AMD64 mainboard plus Athlon64 3400 CPU |wilko |Received |wilko |AMD64 mainboard, Athlon64 3400 CPU, 256MB RAM |itetcu |Received |Joe Altman |ASUS mainboard plus P-III CPU and 512M; 2 graphics cards; various hard drives |linimon |Received |wilko |AlphaStation 500 DIMMs |ticso |Received |imp |Znyx quad dc(4) NIC |wilko |Received |Serge Vakulenko |Cronyx Tau-PCI/32 |rik |Received |Daniel , Seuffert & Waidmann |Funds for a hard drive and USB enclosure |cperciva |Received |Daniel , Seuffert & Waidmann |Logitech Cordless Desktop MX5000 Laser |markus |Received |Daniel , Seuffert & Waidmann |Main server: 1U rackmount chassis, Intel Entry Server Board S845WD1-E, Pentium 4 2.53 GHz CPU, 2 512MB RAM, 2 150GB PATA |FreeBSD Russian Documentation Project |Received |Tamouh H. |PC power supply |kris |Received |Sten Spans |em(4) GbE card |wilko |Received |Chidananda Jayakeerti |AMD Athlon64 desktop: ECS Nforce 4 motherboard, AMD Athlon64 3500+ CPU, 512MB DDR 400, 200GB SATA, 16x DVD-ROM, 8MB AGP video |glewis |Received |wilko |AlphaPC164sx, 512MB RAM, 4.5GB SCSI disk, Qlogic SCSI HBA |dunstan |Received |trhodes |USD 500 in cash for BSDCan trip. |ru |Received |hrs |http://www.sparc.org[UltraSPARC laptop] |ru |Received |asdf |4 SCSI hard drives |marcel, thompsa, kan |Received |Steve Quirk |Sun Ultra 10 |jkoshy |Received |Paul Ghering |Asus AP1400R 1U server |wilko |Received |remko |4 Keytronic Lifetime Designer Keyboards |flz |Received |Mike Tancsa |Four fiber em(4) NICs, two copper bge(4) NICs |glebius, oleg, yar, ru |Received |Paul Ghering |NatSemi Geode based Web/TV appliance |sos |Received |Paul Ghering |NatSemi Geode based Web/TV appliance |markm |Received |Paul Ghering |NatSemi Geode based Web/TV appliance |wilko |Received |netchild |3Com Wireless LAN 54 MBit adapter, Netgear RangeMax Wireless USB WPN111GR 108 MBit adapter, Anycom Blue USB-250 adapter |hselasky |Received |Martin Nilsson (Mullet Scandinavia AB) |Seagate 80GB ATA disk, Samsung 512MB PC3200 RAM |joel |Received |lawrence |512MB RAM |simon |Received |Hans Beeksma |multiple PCMCIA modems & NICs |imp |Shipped |Paul Ghering via wilko |NatSemi Geode based Web/TV appliance |ariff |Received |Justin Pessa |Sun Netra X1 |shaun |Received |wilko |various PCMCIA cards |imp |Received |Paul Ghering via wilko |NatSemi Geode based Web/TV appliance for the FreeNAS project |Olivier Cochard-Labbe |Received |Joe Altman |Linksys USB ethernet adapter |wilko |Received |Uwe Laverenz |Ultrabay Slim battery for IBM ThinkPad T41p |markus |Received |Andrejs Guba (WiMAX) |FUJITSU DISK DRIVE 2.5-inch 60GB SATA - MHV2060BH |matteo |Received |Andrejs Guba (WiMAX) |U320 1 channel SCSI CARD - LSI Logic LSI20320C-HP U320 SCSI PCI-X 133MHz |mjacob |Received |Bryan Kaplan |Dell Managed 2708 8-port gig switch |glebius |Received |Nicole Harrington and Picturetail.com |Various SCSI drives, cables, and cards for mjacob, Dual P3 motherboard with chips and RAM for mpp, 146GB SCSI disk for glebius, various other system components (network cards, CPUs, CPU fans) waiting for other committers if/when they need it. |All components delivered to trhodes. |Received |netchild |Pentium 4 2,4GHz CPU, Heatsink + CPU Cooler |joel |Received |rink |2 18GB SCA disks |xride |Received |markus |Sun 100MBit SBus NIC |shaun |Received |Holger Jeromin |D-Link DFE-570TX NIC |njl |Received |brueffer |Adaptec ANA-62022 NIC |danfe |Received |Walter Kiel |ECS ELITEGROUP 915P-A motherboard + CPU |ade |Received |Gareth Randall |Sun Netra t1 |philip |Received |Garrett Cooper |Seagate 73GB SCSI disk + 2x Adaptec 2940 U2W controllers and cables |rink |Received |Anand S Athreya & Srinivas Podila (Juniper) |Dell E520 CPU |jkoshy |Received |Chess Griffin |VIA EPIA-M system |brueffer |Received |Mariusz J. Handke |SCSI disks + DIMMs |wilko |Received |Christoph Haas |Sun Ultra 60: 2x 450MHz UltraSPARC II, 2GB RAM, 2x 9GB SCSI drives, QLogic 2200F FC controller + Sun StorEdge T3 with 9x 36GB FC drives |markus |Received |carvay |hard drive mounting kit for Soekris net4801 |arved |Received |brueffer |soekris vpn1401 |simon |Received |wilko |Sun Ultra 5 |rink |Received |Daniel Austin |DIMMs plus ATA disks |wilko |Received |Daniel Austin |DIMMs plus ATA disks |rink |Received |Daniel Austin |ATA disks |joel |Received |Daniel Austin |WinTV PCI Tuner card |gavin |Received |Edwin Verplanke |Intel D3C6132 Software Development Platform |jkoshy |Received |Charles Smeijer |AMD Opteron 250 CPU |des |Received |wilko |Asus AP1400R 1U server |rink |Received |rpaulo |VIA XinE Firewire OHCI (PCI) |mlaier |Received |Steve Rikli |Ultra2 2x400Mhz, 2GB RAM, 2x72GB disks, CDROM |linimon |Received |Dax Kelson (Guru Labs) |Nvidia Geforce 6800 GT |rnoland |Received |bms |Netgear WGT634U |gonzo |Received |Mike Partin |4 x Dell 2550 dual P-III 2U servers + 1 x Dell 6550 quad Xeon 4U server + 2 x IBM Netfinity 400R dual P-III 1U servers |linimon |Received |Colin Jensen |4.4BSD Manuals from O'Reilly |marcel |Received |Charles Smeijer |HP/CPQ Gb NIC NC7770, PCI-X 133 HP p/n 284685-003 Rev 0G + HP/CPQ Gb NIC NC7770, PCI-X 133 HP p/n 284685-003 Rev 0E + HP/CPQ Dual port Gb NIC NC7170, PCI-X 133 HP p/n 313559-001 Rev 0A + SMC Fast ethernet USB NIC p/n 98-012084-585 + IBM Gb NIC PCI-X 133 p/n 00P6130 + HP DAT72 data cartridge 72 GB |ed |Received |brooks |2 DDR400 256MB DIMMs |wilko |Received |Edson Brandi |BrookTree chipset TV Capture Card BT878 |lioux |Received |Charles Smeijer |HP JetDirect 175x print server |rpaulo |Received |Gateworks Corporation |Cambria GW2358-4 board |rpaulo |Received |Alexis Megas |Sun Ultra Sparc 60 |glewis |Received |bms |MPLS and Label Switching Networks book |rpaulo |Received |bms |See MIPS Run book |stas |Received |Justin Settle |Kuma Athlon 7750 |jkim |Received |Justin Settle |HTPC Machine |wxs |Received |Justin Settle |Soekris 5501 |lstewart |Received |gavin |3 Zip 100 drives + 3 3ware cards |mav |Received |Gareth Randall |HP C1636-00100 SCSI tape drive |cracauer |Received |Ivan Jedek |2 Sun Fire V65 |miwi (for pkg build cluster) |Received |Gareth Randall |USB card |gj |Received |Kyle Anderson (tummy.com) |6 SuperMicro servers |brd (firewalls and infrastructure servers + for the new NYC FreeBSD co-location) |Received |Garrett Cooper |Cisco 877WAGN router |ehaupt |Received |Garrett Cooper |Linksys WRT160N wireless router |dougb |Received |grehan |Apple XServe G5 |portmgr (for pkg build cluster) |Received |Garrett Cooper |2GB PC6400 DDR2 Corsair RAM module |fjoe |Received |sson |PowerMac G4 |stas |Received |sson |PowerMac G4 |rnoland |Received |Raymond Vetter |Sun Ultra 5 |gahr |Received |jmallett |Cavium Octeon MIPS |gonzo |Received |Raymond Vetter |Sitecom CN-500 |itetcu |received |Raymond Vetter |3xIDE cables + FDD cable + VGA cable + serial cable + 2xCAT7 ethernet cable + |romain |received |ds |memory modules and hard disks |pgj |received |Raymond Vetter |Netier NetXpress XL1000 |rink |received |Raymond Vetter |IBM Thinkpad port replicator |brueffer |received |Andreas Thalau |512MB PC2700 SO-DIMM RAM module |brueffer |received |Andreas Thalau |Sharp Zaurus SL-5500G |itetcu |received |Travis Thaxton |Dell Optiplex 960 |ade |received |Travis Thaxton |Dell 22" LCD monitor |delphij |received |Travis Thaxton |Dell 22" LCD monitor |dougb |received |Olivier Cochard-Labbe |Sun Blade 150 |fjoe |received |Andreas Thalau |Level One GSW-0502T gigabit switch |lme |received |Raymond Vetter |ATI Radeon 9800 |fjoe |received |Anton Shterenlikht |1x Asus WL-107g (Ralink RT2560 + RT2525, ral(4)) + 1x MSI CB54G2 (Ralink RT2560 + RT2525, ral(4)) + 1x Sitecom WL-112 (Ralink RT2560 + RT2525, ral(4)) + 1x Zonet ZEW1500 (PRISM GT/ISL3890, no driver) + 1x Linksys WPC11v4 (Realtek RTL8180L, no driver) |bschmidt |received |Garrett Cooper |Core2Duo-based i386 machine |bf |received |Garrett Cooper |PowerMac G5 |dchagin |received |Eimar Koort |Sun Microsystems Sun Fire V210 |marius |received |wilko |4x 72GB FibreChannel disk for the sparc package building machine |marius |received |Jean-Michel Poure |Feitian R-301 and ePass2003 |arved |received |Lyndon Nerenberg |Sun Microsystems Sun Fire V100 |tabthorpe |received |Anton Shterenlikht |Linksys WPC11 ver.3 (no driver) + US Robotics USR5410 (Texas Instruments, no driver) + Cisco Aironet 350 (no driver) + Linksys WPC54G ver3.1 (Broadcom BCM4318, bwi(4)) + NEC CMZ-RT-WP (NEC CMZ-RT-WP, wi(4), unsupported) + Netgear WG111v2 (Realtek RTL8187L, urtw(4)) |adrian |received |Garrett Cooper |Macbook 2.2GHz Santa Rosa |marcel |received |Garrett Cooper |2x 4GB 1333 DDR3 ECC RAM banks |garga |received |Marco Dola |2x Kingston KVR1333D3N9/2G RAM banks |gavin |received |Greg Larkin |Belkin #F1D066 OmniView PS/2 KVM Switch + + 6 foot VGA cables + + 6 foot PS/2<->PS/2 keyboard/or mouse cables |bf |received |Greg Larkin |Mac G4 Cube 500Mhz PowerPC |alfred |received |David Boyd |Digi AccelePort with fan-out cables |marcel |received |Tim Kientzle |Dell PowerEdge R510 server + + Linksys SFE2010 switch |sbruno |received |Olivier Cochard-Labbe |Ubiquiti RouterStation Pro |lstewart |received |Bob Bishop |Power Mac G5 |danfe |received |Ben Medina |Sunfire v490 |culot |received |Roger Ehrlich |2x IBM Power PC, POWER4 CHRP Model 7028-6C4; Serial #108D21C & 108D1EC. + 3x Sun V490 |FreeBSD.org cluster |received |Michael Shirk |Mac G5 Dual PowerPC |marcel |received |Xin Xu |15 inch MacBook Pro |jmg |received |Paul Demers |Shuttle SX58J3 machine |jmmv |received |Jim Dutton |Zotac Sonix PCIE ZTSSD-PG3-480G-GE |bjk |received |Jim Dutton |GeForce 6200 graphic card |pfg |received |Tim Kientzle |PandaBoard |brd |received |Tim Kientzle |Raspberry Pi |swills |received |Anonymous |2x Supermicro E5-2600 servers |clusteradm@ |received |Ralf Folkerts |Asrock J3455-ITX + 8GB RAM |rezny |received |brooks |2x Soekris net6501-70s boards |brd, will |received |NYC*BUG / The New York City BSD Users Group |3x HotLava Systems Sumatra 8G4S-350 4 port 1G PCI-E cards + 2x HotLava Systems Tambora 80G4S-G3 4 port 10G PCI-E cards |novel, kib, eadler, pi, rgrimes |received |Peter Sagerson |High-end motherboard/CPU/RAM combo |bcran |received |Neel Chauhan |1x complete workstation |pfg |received |David Chmelik # # $FreeBSD: head/en_US.ISO8859-1/htdocs/gnome/docs/example-Makefile.xml 43181 2013-11-13 06:10:37Z hrs $ # # For this example, assume there was already a gnomeapp in the tree, and that this # is the GTK+-2 version (i.e. gnomeapp2 versus gnomeapp). PORTname= gnomeapp2 PORTVERSION= 2.32.2 MASTER_SITES= ${MASTER_SITE_GNOME} MASTER_SITE_SUBDIR= sources/${PORTNAME:S/2//}/${PORTVERSION:C/^([0-9]+\.[0-9]+).*/\1/} DISTname= ${PORTNAME:S/2//}-${PORTVERSION} DIST_SUBDIR= gnome2 MAINTAINER= gnome@FreeBSD.org COMMENT= A GNOME app that does some stuff USE_BZIP2= yes GNU_CONFIGURE= yes # NOTE: if the port needs ltverhack, this must be USE_AUTOTOOLS="libtool":15 USE_GMAKE= yes # same with GNU make # This is for i18n: CONFIGURE_ENV+= CPPFLAGS="-I${LOCALBASE}/include" \ LDFLAGS="-L${LOCALBASE}/lib" USE_GNOME= gnomehack gtk20 # This application can dock in the GNOME panel, or it can not. # But there's no need to build support for it if the GNOME panel # libraries are not installed, so only build GNOME panel support # if the gnomepanel port is already installed. WANT_GNOME= yes .include .if ${HAVE_GNOME:Mgnomepanel}!="" USE_GNOME+= gnomepanel CONFIGURE_ARGS+= --with-gnome PKGNAMESUFFIX= -gnome .else CONFIGURE_ARGS+= --without-gnome .endif # Given all the above code, the package name is either "gnomeapp2-gnome-2.32.2" or # "gnomeapp2-2.32.2", depending upon whether you want gnomepanel support. The downloaded # distfile will be "gnomeapp-2.32.2.tar.bz2." .include .... diff --git a/website/content/en/gnome/docs/gnome1_porting.adoc b/website/content/en/gnome/docs/gnome1_porting.adoc index 1224f3cf2b..803c3bd193 100644 --- a/website/content/en/gnome/docs/gnome1_porting.adoc +++ b/website/content/en/gnome/docs/gnome1_porting.adoc @@ -1,35 +1,35 @@ --- title: "FreeBSD GNOME Project: GNOME 1 Components" sidenav: gnome ---- +--- = FreeBSD GNOME Project: GNOME 1 Components To see how to utilize these components, please examine the link:../example-makefile/[example Makefile]. [.tblbasic] [cols=",,",] |=== |*COMPONENT* |*ASSOCIATED PROGRAM* |*IMPLIED COMPONENTS* |bonobo |devel/bonobo |oaf gnomeprint |gal |x11-toolkits/gal |libglade |gconf |devel/gconf |oaf |gdkpixbuf |graphics/gdk-pixbuf |gtk12 |glib12 |devel/glib12 |pkgconfig |gnomecanvas |graphics/gnomecanvas |gnomelibs gdkpixbuf |gnomedb |databases/gnome-db |libgda |gnomelibs |x11/gnome-libs |esound imlib libxml orbit |gnomeprint |print/gnome-print |gnomelibs gnomecanvas |gnomevfs |devel/gnome-vfs1 |gnomemimedata gconf gnomelibs |gtk12 |x11-toolkits/gtk12 |glib12 |imlib |graphics/imlib |gtk12 |libgda |databases/libgda |gconf bonobo |libghttp |www/libghttp | |libglade |devel/libglade |gnomedb |libxml |textproc/libxml |glib12 |oaf |devel/oaf |orbit libxml |orbit |devel/ORBit |glib12 |pygtk |x11-toolkits/py-gtk |gnomelibs gdkpixbuf libglade |=== If you still need help with your port, have a look at some of the existing ports for examples. The link:mailto:freebsd-gnome@FreeBSD.org[freebsd-gnome mailing list] is also there for you. diff --git a/website/content/en/gnome/docs/gnome2_porting.adoc b/website/content/en/gnome/docs/gnome2_porting.adoc index 2d952c509c..f25bad94f1 100644 --- a/website/content/en/gnome/docs/gnome2_porting.adoc +++ b/website/content/en/gnome/docs/gnome2_porting.adoc @@ -1,77 +1,77 @@ --- title: "FreeBSD GNOME Project: GNOME 2 Components" sidenav: gnome ---- +--- = FreeBSD GNOME Project: GNOME 2 Components To see how to utilize these components, please examine the link:../example-makefile/[example Makefile]. [.tblbasic] [cols=",,",] |=== |*COMPONENT* |*ASSOCIATED PROGRAM* |*IMPLIED COMPONENTS* |atk |accessibility/atk |glib20 |atspi |accessibility/at-spi |gtk20 libbonobo |desktopfileutils |devel/desktop-file-utils |glib20 |eel2 |x11-toolkits/eel |gnomedesktop |evolutiondataserver |databases/evolution-data-server |libgnomeui |gal2 |x11-toolkits/gal2 |gnomeui libgnomeprintui |gconf2 |devel/gconf2 |orbit2 libxml2 gtk20 |_glib20 |devel/glib20 |pkgconfig |glib20 |devel/gio-fam-backend |_glib20 |gnomecontrolcenter2 |sysutils/gnome-control-center |metacity gnomemenus desktopfileutils libgnomekbd gnomedesktop librsvg2 |gnomedesktop |x11/gnome-desktop |gconf2 gnomedocutils pygtk2 |gnomedesktopsharp20 |x11-toolkits/gnome-desktop-sharp20 |gnomesharp20 |gnomedocutils |textproc/gnome-doc-utils |libxslt |gnomemenus |x11/gnome-menus |glib20 |gnomepanel |x11/gnome-panel |gnomedesktop libwnck gnomemenus gnomedocutils librsvg2 libgnomeui |gnomesharp20 |x11-toolkits/gnome-sharp20 |gnomepanel gtkhtml3 gtksharp20 librsvg2 vte |gnomespeech |accessibility/gnome-speech |libbonobo |gnomevfs2 |devel/gnome-vfs |gconf2 gnomemimedata |gtk20 |x11-toolkits/gtk20 |intltool atk pango |gtkhtml3 |www/gtkhtml3 |libgnomeui |gtksharp10 |x11-toolkits/gtk-sharp10 |gtk20 |gtksharp20 |x11-toolkits/gtk-sharp20 |gtk20 |gtksourceview |x11-toolkits/gtksourceview |libgnome libgnomeprintui |gtksourceview2 |x11-toolkits/gtksourceview2 |gtk20 libxml2 |gvfs |devel/gvfs |glib20 gconf2 |libartlgpl2 |graphics/libart_lgpl |pkgconfig |libbonobo |devel/libbonobo |libxml2 orbit2 |libbonoboui |x11-toolkits/libbonoboui |libgnomecanvas libgnome |libgailgnome |x11-toolkits/libgail-gnome |libgnomeui atspi |libgda2 |databases/libgda2 |glib20 libxslt |libgda3 |databases/libgda3 |glib20 libxslt |libgda4 |databases/libgda4 |glib20 libxslt |libglade2 |devel/libglade2 |libxml2 gtk20 |libgnome |x11/libgnome |gnomevfs2 esound libbonobo |libgnomecanvas |graphics/libgnomecanvas |libglade2 libartlgpl2 |libgnomedb |databases/libgnomedb |libgnomeui libgda3 |libgnomekbd |x11/libgnomekbd |gconf2 |libgnomeprint |print/libgnomeprint |libbonobo libartlgpl2 gtk20 |libgnomeprintui |x11-toolkits/libgnomeprintui |libgnomeprint libgnomecanvas |libgnomeui |x11-toolkits/libgnomeui |libbonoboui |libgsf |devel/libgsf |gconf2 glib20 libxml2 |libgsf_gnome |devel/libgsf-gnome |libgsf gnomevfs2 |libgtkhtml |www/libgtkhtml |libxslt gnomevfs2 |libidl |devel/libIDL |glib20 |librsvg2 |graphics/librsvg2 |libgsf gtk20 |libwnck |x11-toolkits/libwnck |gtk20 |libxml2 |textproc/libxml2 |pkgconfig |libxslt |textproc/libxslt |libxml2 |libzvt |x11-toolkits/libzvt |gtk20 |linc |net/linc |glib20 |metacity |x11-wm/metacity |gconf2 |nautilus2 |x11-fm/nautilus |librsvg2 gnomedesktop desktopfileutils gvfs |nautiluscdburner |sysutils/nautilus-cd-burner |nautilus2 eel2 desktopfileutils |orbit2 |devel/ORBit2 |libidl |pango |x11-toolkits/pango |glib20 |pygnome2 |x11-toolkits/py-gnome2 |libgnomeui pygtk2 |pygnomedesktop |x11-toolkits/py-gnome-desktop |pygnome2 libgnomeprintui gtksourceview gnomepanel libwnck nautilus2 metacity |pygnomeextras |x11-toolkits/py-gnome-extras |pygnome2 libgtkhtml |pygtk2 |x11-toolkits/py-gtk2 |libglade2 |pygtksourceview |x11-toolkits/py-gtksourceview |gtksourceview2 pygtk2 |vte |x11-toolkits/vte |gtk20 |=== If you still need help with your port, have a look at some of the existing ports for examples. The link:mailto:freebsd-gnome@FreeBSD.org[freebsd-gnome mailing list] is also there for you. diff --git a/website/content/en/gnome/docs/gnome_porting.adoc b/website/content/en/gnome/docs/gnome_porting.adoc index bd17c7b6be..6a5c854654 100644 --- a/website/content/en/gnome/docs/gnome_porting.adoc +++ b/website/content/en/gnome/docs/gnome_porting.adoc @@ -1,28 +1,28 @@ --- title: "FreeBSD GNOME Project: GNOME Desktop-Independent Components" sidenav: gnome ---- +--- = FreeBSD GNOME Project: GNOME Desktop-Independent Components To see how to utilize these components, please examine the link:../example-makefile/[example Makefile]. [.tblbasic] [cols=",,",] |=== |*COMPONENT* |*ASSOCIATED PROGRAM* |*IMPLIED COMPONENTS* |esound |audio/esound | |gnomehack |gnomehack makes common GNOME Makefile substitutions that nearly every GNOME port requires to fit into the proper mtree structure. | |gnomehier |gnomehier installs all the directories needed for both the GNOME 1 and 2 desktops. Only include this option if your port calls @dirrm on one of the directories listed in the plist for gnomehier. | |gnomemimedata |misc/gnome-mime-data |gnomehier pkgconfig |gnomeprefix |gnomeprefix sets some CONFIGURE_ARGS to ensure data is placed properly within the GNOME hierarchy. |gnomehier |intlhack |intlhack registers a dependency upon textproc/intltool and patches broken intltool-merge.in implementations. |intltool |intltool |intltool registers a BUILD_DEPENDS on textproc/intltool. | |lthack |lthack prevents the installation of .la files and ensures that $\{PTHREAD_LIBS} will be passed to the linker. NOTE: lthack is DEPRECATED, and USE_AUTOTOOLS="libtool":15 should be used instead. See the libtool section of the porting guide for more details. | |ltasneededhack |ltasneededhack hacks the port's link:../porting/#libtool[libtool] so that the -Wl,--as-needed flag is passed to the linker. This will result in shared objects with smaller ELF NEEDED sections which can improve the startup time and module load time of some applications. In order to use ltasneededhack the port must define USE_AUTOTOOLS="libtool":15. NOTE: be sure to thoroughly test the resulting application to make sure there are no undefined symbol errors after adding this hack. | |ltverhack |ltverhack normalizes shared object versions so that they do not change needlessly. Using ltverhack keeps shared object versions in line with what they should be and what they end up being on other operating systems. In order to use ltverhack the port must define USE_AUTOTOOLS="libtool":15. | |pkgconfig |pkgconfig registers a dependency upon devel/pkg-config to make sure it is installed. | |referencehack |referencehack is designed for ports that install API reference documentation. These ports should use referencehack then another port with a -reference suffix should be created to install this documentation. See devel/glib20 and devel/glib20-reference for an example. | |=== If you still need help with your port, have a look at some of the existing ports for examples. The link:mailto:freebsd-gnome@FreeBSD.org[freebsd-gnome mailing list] is also there for you. diff --git a/website/content/en/gnome/docs/halfaq.adoc b/website/content/en/gnome/docs/halfaq.adoc index ca02f99438..9f4c47744a 100644 --- a/website/content/en/gnome/docs/halfaq.adoc +++ b/website/content/en/gnome/docs/halfaq.adoc @@ -1,207 +1,207 @@ --- title: "FreeBSD GNOME Project: Hardware Abstraction Layer (HAL) FAQ" sidenav: gnome ---- +--- = FreeBSD GNOME Project: Hardware Abstraction Layer (HAL) FAQ _"You're in luck, Dave. Turns out I CAN let you do that."_ == Contents . <> . <> . <> . <> . <> . <> == Full Text [[q1]] * *How do I use hal on FreeBSD?* The only thing you need to do in order to use hal is to start the HAL daemon, `hald`. To do this, add the following to `/etc/rc.conf`: .... dbus_enable="YES" hald_enable="YES" .... *NOTE:* GNOME users can opt to add `gnome_enable="YES"` to `/etc/rc.conf` instead of the lines above. This will start all GNOME-related services including Avahi and GDM. Then you must either reboot, or run: .... # /usr/local/etc/rc.d/dbus start # /usr/local/etc/rc.d/hald start .... Once `hald` is running, hal-aware application will automatically start to communicate with it over D-BUS. To confirm that hald is running correctly, execute `lshal` from the command line. This provides you with a list of devices attached to the system. *Note:* `lshal` must be run from within a D-BUS enabled session (e.g. GNOME or KDE). [[q2]] * *How do I prevent hal from probing a device?* Sometimes, when hal probes a device, this can cause the system to hang, panic, or otherwise behave badly. By using device information files (.fdi files), you can tell hal to ignore such devices. These files are in XML format, and should be created under `/usr/local/share/hal/fdi/preprobe/20thirdparty`. For example, to tell hal to ignore USB uhci controller 0, create a file `/usr/local/share/hal/fdi/preprobe/20thirdparty/10-ignore-uhci0.fdi` with the following contents: .... true .... Using this same technique, you can also merge (or change) other hal device properties. Use the `lshal` command to get a list of all available device properties. You can also look at the system-provided .fdi files under `/usr/local/share/hal/fdi/preprobe/10osvendor` for more examples. All .fdi files in this `20thirdparty` directory are loaded in alphabetical order, so name your files accordingly. The convention is to start the files with a number. The lower the number, the earlier the file will be loaded. [[q3]] * *How do I mount media using hal?* Understand that having hal alone does not mean media will get automatically mounted. Hal simply serves as a broker for requests to mount certain devices. Some other software needs to make this request. As of GNOME 2.22, this is Nautilus. KDE and XFCE have their own components to mount hal volumes. *NOTE:* Volumes that you wish to manage using hal should _NOT_ be listed in `/etc/fstab`. This is especially true for CD devices and floppy disk devices. If you try to dynamically mount a volume using hal that is listed in `/etc/fstab` you will see the following error: .... mount_cd9660: /dev/acd0: Operation not permitted .... If you are a GNOME user be aware that prior to GNOME 2.22, `gnome-volume-manager` was responsible for asking hal to mount volumes. Since this responsibility has moved to Nautilus, it is vital to change `gnome-volume-manager's` configuration so that it will no longer attempt to mount volumes. *NOTE:* This step is only required if you are a GNOME user that upgraded to 2.22 from a previous version of GNOME. If this is not the case, then skip to Step 1. From within your GNOME session, run the following commands: .... % gconftool-2 -s --type bool /desktop/gnome/volume_manager/automount_drives false % gconftool-2 -s --type bool /desktop/gnome/volume_manager/automount_media false % gconftool-2 -s --type bool /desktop/gnome/volume_manager/autobrowse false % gconftool-2 -s --type bool /desktop/gnome/volume_manager/autoplay_cda false % gconftool-2 -s --type bool /desktop/gnome/volume_manager/autoplay_dvd false % gconftool-2 -s --type bool /desktop/gnome/volume_manager/autoplay_vcd false % gconftool-2 -s --type bool /desktop/gnome/volume_manager/autoprinter false .... Then restart GNOME. *Step 1:* All users _MUST_ have `procfs` mounted on `/proc`. Hal uses an application called PolicyKit to authorize users to perform mount tasks, and PolicyKit relies heavily on `/proc` entries. If `/proc` is not mounted, volume mounting will not work. To mount `/proc`, add the following to `/etc/fstab`: .... proc /proc procfs rw 0 0 .... Then run the following command: .... # mount /proc .... *Step 2:* In order to mount volumes using hal, you must be authorized. This authorization is carried out by ConsoleKit and PolicyKit. If you are a GNOME user, and you use GDM to login to GNOME, then you do not need to make any additional configuration changes in order to mount removable media. If you are not a GNOME user, or you start GNOME without using GDM, then you will need to edit `/usr/local/etc/PolicyKit/PolicyKit.conf`, and add the `org.freedesktop.hal.storage.mount-removable` action to your username. For example, if your username is "marcus," you would add the following lines: .... .... *NOTE:* All config lines in this file _MUST_ be between the opening and closing `` tags: .... .... If you use GDM to login to GNOME, GDM will add a ConsoleKit record for the session. If this session is active, then you will be allowed to mount removable media without any additional PolicyKit configuration. You can confirm if ConsoleKit is working correctly by running the command, `ck-list-sessions`. The `active` property must be `TRUE` for auto-mounting to work. By default, PolicyKit allows root to do everything, and all users in the "wheel" group are allowed to authenticate for admin tasks with their own password. To get a list of all available actions, use the `polkit-action(1)` command. For more information on the directives available for `PolicyKit.conf`, see the `PolicyKit.conf(5)` man page. *Step 3:* If you have fixed volumes you wish to mount, you must also authorize yourself for the `org.freedesktop.hal.storage.mount-fixed` action. *Note:* This step is applicable to _ALL_ users including GNOME users using GDM. This is done just like the removable action above. For example, to allow user "marcus" to mount fixed volumes, add the following to `PolicyKit.conf`: .... .... *Step 4:* While not really part of hal volume management, you may also be able to have volumes listed in `/etc/fstab` automatically mounted. In GNOME, for example, Nautilus will mount volumes listed in `/etc/fstab` provided the following conditions are met: .. The `vfs.usermount` sysctl is set to `1`. .. The user requesting the mount owns the mount point. .. The user requesting the mount is in the "operator" group. For example, say you had the following listed in `/etc/fstab`: .... /dev/ad0s1 /win/c msdosfs rw,noauto 0 0 .... If you want Nautilus to mount this volume as the user "marcus," do the following: .... # sysctl vfs.usermount="1" # chown marcus /win/c # pw group mod operator -m marcus .... Then, when the user marcus logs into GNOME, `/win/c` will be automatically mounted on the desktop. [[q4]] * *How do I troubleshoot problems with hal?* If you run into problems with hal, you must first collect the link:../bugging/[general troubleshooting information] required by the FreeBSD GNOME Team. You should also provide a detailed description of the problem, and the output of `lshal` (assuming `hald` is starting). Remember, `lshal` _MUST_ be run under a D-BUS enabled session. If you cannot login to GNOME, KDE, or XFCE, run `lshal` within `dbus-launch`: .... % dbus-launch lshal .... You should also provide the verbose output from `hald` when it is performing the problematic task. To get this, first stop `hald`, then run it manually: .... # /usr/local/etc/rc.d/hald stop # /usr/local/sbin/hald --daemon="no" --verbose="yes" .... Capture all of the output on the screen. If you are having problems with hal detecting volumes or media, or having problems with mounting volumes through hal, obtain the following additional information. All of this needs to be collected with the problem device attached to the system. .. Output of `sysctl -b kern.geom.conftxt` .. Contents of `/etc/fstab` .. Output of the `mount` command .. Full `dmesg` output .. If using GNOME, and a volume is not mounting properly, include the output of `gnome-mount --block --no-ui --verbose --hal-udi ` ( is the Unique Device Identifier obtained from the output of `lshal` for the device that is not mounting properly) Additionally, if you are a GDM user, please provide the output of `ck-list-sessions`. [[q5]] * *Does hal support Fuse file systems?* Yes. As of hal-0.5.11_10, Fuse file systems are supported. See the installed `/usr/local/share/doc/hal-0.5.11/README.fuse` file for more details. [[q6]] * *Hal is interfering with my CD/DVD drive when I want to play a disc or burn something. How can I stop this from happening?* Applications which are not hal-aware will not be able to tell hald to stop polling CD/DVD drives when they begin to use them. Because of this, hald may cause these applications to abort because two different processes are trying to use the device at the same time. Applications such as totem, k3b, sound-juicer, etc. should not be affected as they are hal-aware. For other applications, you can start them using the `hal-lock` command. This command will try and lock the device in question. If successful, hald will stop polling the device, and `hal-lock` will spawn the desired application. The arguments to `hal-lock` are as follows: .... % hal-lock --interface org.freedesktop.Hal.Device.Storage --udi UDI --run COMMAND .... You can use `lshal` to determine the proper `UDI` value. For example, to run `abcde` to extract tracks from a CD: .... % hal-lock --interface org.freedesktop.Hal.Device.Storage --udi /org/freedesktop/Hal/devices/storage_model_DVD__RW_DVD8801 --run abcde .... As soon as the application finishes, the lock will be released. diff --git a/website/content/en/internal/bylaws.adoc b/website/content/en/internal/bylaws.adoc index fec748e9ff..4671e7b77c 100644 --- a/website/content/en/internal/bylaws.adoc +++ b/website/content/en/internal/bylaws.adoc @@ -1,36 +1,36 @@ --- title: "Core Bylaws" sidenav: docs ---- +--- = Core Bylaws These bylaws were approved by a vote of active committers on August 28, 2000. * Active committers have made a commit to the tree in the last 12 months. * Core consists of 9 elected active committers. * Core elections are held every 2 years, first time September 2000. * Core members and committers may be ejected by a 2/3 vote of core. * If the size of core falls below 7, an early election is held. * A petition of 1/3 of active committers can trigger an early election. * All elections will be run as follows: ** Core appoints and announces someone to run the election. ** 1 week to tally active committers wishing to run for core. ** 4 weeks for the actual vote. ** 1 week to tally and post the results. ** Each active committer may vote once in support of up to nine nominees. ** New core team becomes effective 1 week after the results are posted. ** Voting ties decided by unambiguously elected new core members. * These rules can be changed by a 2/3 majority of committers if at least 50% of active committers cast their vote. == Additional Information The last core election was held in June of 2020. The next core election is scheduled for May-June of 2022. == Core Interpretations of the Bylaws Core will issue interpretations of the bylaws from time to time as necessary to clarify areas that might be ambiguous in the bylaws as enacted to ensure the smooth operation of the project. * *20020503* The next election is always scheduled for two years after the previous election. This means that early elections reset the date of the succeeding election such that it will occur two years following the early election. link:../developer[Resources for FreeBSD Committers Home] diff --git a/website/content/en/internal/clusteradm.adoc b/website/content/en/internal/clusteradm.adoc index a1761f4b28..e62eabd512 100644 --- a/website/content/en/internal/clusteradm.adoc +++ b/website/content/en/internal/clusteradm.adoc @@ -1,38 +1,38 @@ --- title: "Charter for the Cluster Administrators" sidenav: docs ---- +--- = Charter for the Cluster Administrators Lead cluster administrator is a delegated officer role (aka. "hat") that answers to the FreeBSD Core Team and ultimately the FreeBSD community at large. This person shall have the operational authority over the FreeBSD cluster infrastructure (to the extent that the Core Team can delegate this authority) and will be responsible for the following in general: * Ensure the reliable operation of the Project's equipment and network resources. * Ensure that the Project's resources are suitably and effectively used to serve the Project's interests. * Ensure that reasonable security precautions and mitigations are implemented within the constraints of the nature of a highly distributed project. * Delegate to and coordinating with both the site-specific admin teams and the admins at large. * Ensure that standard operating procedures, rules, guidelines etc are documented and understandable. * Take measures to ensure that a competent administrator would be expected to be able to adopt a predecessor's work in a reasonable amount of time. * Contingency planning and implementation to ensure continuity across site specific problems (including donated site withdrawal or outages). * Keep the interested parties (Core Team, Security Team, FreeBSD Foundation, Port Management Team, etc), project members and community members appropriately informed. * Give timely and authoritive answers to questions, or a direct referral to the appropriate party. * Aid other hat wearers and cluster administrators to get their job done. * Where practical and appropriate, use the Project's own product as a proving ground. * Make sure that it is easy for developers to know what hardware resources they have access to for project purposes. The lead cluster administrator answers to the FreeBSD Core Team. If a party is unhappy with a position that the hat wearer takes and is unable to change their mind, they may take the issue to the Core Team. The Core Team has the final say in the matter. If the lead cluster administrator is a member of the Core Team then a complaint may be made in confidence via the core secretary or another member if desired. Any of the following still require a sign-off from the Core Team: * New public facing services. * Planned withdrawal of public facing services. * New team members. Notable interaction with other hats: * The lead cluster administrator will consult with the Security Officer and the Security Team where appropriate but will be responsible for making decisions. However, the Security Officer may respond to security emergencies involving project infrastructure as necessary. * The Port Management Team has a large resource footprint and arrangements will be made with them to effectively operate their resources within the constraints of the overall cluster operation. Earmarked resources: Some site resources are provided for specific purposes. Any such earmarking or use restrictions will be documented to make sure such resources are used as intended. diff --git a/website/content/en/internal/code-of-conduct.adoc b/website/content/en/internal/code-of-conduct.adoc index 3064feca46..61fe981fe4 100644 --- a/website/content/en/internal/code-of-conduct.adoc +++ b/website/content/en/internal/code-of-conduct.adoc @@ -1,44 +1,44 @@ --- title: "FreeBSD Community Code of Conduct" sidenav: docs ---- +--- = FreeBSD Community Code of Conduct == FreeBSD Community Code of Conduct The FreeBSD community has always worked to be a welcoming and respectful community, and we want to ensure that doesn't change as we grow and evolve. To that end, we have a few ground rules that we ask people to adhere to: * be friendly and patient, * be welcoming, * be considerate, * be respectful, * be careful in the words that you choose and be kind to others, * when we disagree, try to understand why. This isn't an exhaustive list of things that you can't do. Rather, take it in the spirit in which it's intended - a guide to make it easier to communicate and participate in the community. This code of conduct applies to all spaces managed by the FreeBSD project. This includes online chat, mailing lists, bug trackers, FreeBSD events such as the developer meetings and socials, and any other forums created by the project that the community uses for communication. It applies to all of your communication and conduct in these spaces, including emails, chats, things you say, slides, videos, posters, signs, or even t-shirts you display in these spaces. In addition, violations of this code outside these spaces may, in rare cases, affect a person's ability to participate within them, when the conduct amounts to an egregious violation of this code. If you believe someone is violating the code of conduct, we ask that you report it by emailing mailto:conduct@freebsd.org[conduct@FreeBSD.org]. For more details please see our link:../conduct-reporting/[Reporting Guide]. * *Be friendly and patient.* * *Be welcoming.* We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, color, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion or lack thereof, and mental and physical ability. * *Be considerate.* Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account. Remember that we're a world-wide community, so you might not be communicating in someone else's primary language. * *Be respectful.* Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the FreeBSD community should be respectful when dealing with other members as well as with people outside the FreeBSD community. * *Be careful in the words that you choose and be kind to others.* Do not insult or put down other participants. Harassment and other exclusionary behavior aren't acceptable. This includes, but is not limited to: ** Violent threats or language directed against another person. ** Discriminatory jokes and language. ** Posting sexually explicit or violent material. ** Posting (or threatening to post) other people's personally identifying information ("doxing"). ** Personal insults, especially those using racist or sexist terms. ** Unwelcome sexual attention. ** Advocating for, or encouraging, any of the above behavior. * *In general, if someone asks you to stop, then stop.* Persisting in such behavior after being asked to stop is considered harassment. * *When we disagree, try to understand why.* Disagreements, both social and technical, happen all the time and FreeBSD is no exception. It is important that we resolve disagreements and differing views constructively. Remember that we're different. The strength of FreeBSD comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn't mean that they're wrong. Don't forget that it is human to err and blaming each other doesn't get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes. == Questions? If you have questions, please feel free to contact the FreeBSD Code of Conduct Committee by emailing mailto:conduct@freebsd.org[conduct@FreeBSD.org] or the FreeBSD Core team mailto:core@freebsd.org[core@FreeBSD.org]. (This text is based on the LLVM Project's https://llvm.org/docs/CodeOfConduct.html[draft CoC], which in turn is based on the https://www.djangoproject.com/conduct/[Django Project] Code of Conduct, which is in turn based on wording from the Speak Up! project.) diff --git a/website/content/en/internal/conduct-reporting.adoc b/website/content/en/internal/conduct-reporting.adoc index b898b4563b..0574a39de3 100644 --- a/website/content/en/internal/conduct-reporting.adoc +++ b/website/content/en/internal/conduct-reporting.adoc @@ -1,57 +1,57 @@ --- title: "FreeBSD Code of Conduct Reporting Instructions" sidenav: docs ---- +--- = FreeBSD Code of Conduct Reporting Instructions == FreeBSD Code of Conduct Reporting Instructions If you believe someone is violating the link:../code-of-conduct[code of conduct] we ask that you report it to the FreeBSD Code of Conduct Committee by emailing conduct@freebsd.org. All reports will be kept confidential whenever possible. We strive to protect the identity and safety of reporters. In some cases we may need to make a public statement of some form, in which case we will use the minimum of details and identifying information necessary to protect our community. In rare cases, we may need to identify some of the people involved to comply with the law or protect other potential victims. In these cases, we will consult with the reporter to find out what their wishes are and take them into account in our final decision. In all cases, we will not directly or indirectly identify reporters without their consent unless we see no other option. If you believe anyone is in physical danger, please notify appropriate law enforcement first. In your report please include: * Your name and contact info (so we can get in touch with you if we need to follow up) * Names (real, nicknames, and/or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well. * When and where the incident occurred. Please be as specific as possible. * Your account of what occurred. If there is a publicly available record (e.g. a mailing list archive, tweet, or a public IRC logger) please include a link and/or screen shots. * Any extra context you believe relevant for the incident. * If you believe this incident is ongoing. * Any other information you believe we should have. == What happens after you file a report? You will receive an email from the FreeBSD Code of Conduct Committee acknowledging receipt of your report within 48 hours. The committee will meet as quickly as possible to review the incident and determine: * Whether an investigation is needed, including interviewing additional parties or witnesses; * What appears to have happened and; * Whether the behavior constitutes a Code of Conduct violation. If a member of the FreeBSD Code of Conduct Committee is one of the individuals included in the report they will recuse themselves from handling the report. Once the working group has a complete account of the events they will make a decision as to how to respond. Actions taken may include: * Nothing (for example, if we determine that no violation occurred). * If determined to be solely technical in nature or if it falls outside the scope of the Code of Conduct, forwarding the incident to the FreeBSD Core Team * A private reprimand from the working group to the individual(s) involved. * A public reprimand. * An imposed vacation from FreeBSD Project controlled spaces (e.g. asking someone to "take a week off" from a mailing list or IRC). * A permanent or temporary ban from some or all FreeBSD Project controlled spaces (events, meetings, mailing lists, IRC, etc.) * A request for a public or private apology. * A request to engage in mediation and/or an accountability plan. We will do our best to respond within one week to the person who filed the report with either a resolution or an explanation of why the situation is not yet resolved. Once we have determined our final action, we will contact the original reporter to let them know what action (if any) we will be taking. We will take into account feedback from the reporter on the appropriateness of our response, but we do not guarantee we will act on it. Finally, the committee will make a report on the situation to the FreeBSD Core Team. The Core Team may choose to issue a public report of the incident. == Appeals Only permanent resolutions (such as bans) may be appealed. To appeal a decision of the CoC Committee, contact the FreeBSD Core Team at core@freebsd.org with your appeal and the Core Team will review the case. diff --git a/website/content/en/internal/core-vote.adoc b/website/content/en/internal/core-vote.adoc index 34e6b36f6c..20f87ee701 100644 --- a/website/content/en/internal/core-vote.adoc +++ b/website/content/en/internal/core-vote.adoc @@ -1,42 +1,42 @@ --- title: "Core's Voting Procedures" sidenav: docs ---- +--- = Core's Voting Procedures == Committers * All core members vote "yes", "no" or "no objection". * Successful candidates must get at least one yes vote. * Successful candidates must not get any 'no' votes. * At least three people must vote. * Voting period is normally 1 week, or ending sooner when the result is certain. * Core secretary to deal with the details of voting, notification, etc. == Personnel * All core members vote "yes" or "no". * Successful candidates must get at least (2/3 * core-size) yes vote. * At least (2/3 * core-size) people must vote, or the measure will fail. * Voting period is normally 1 week, or ending sooner when the result is certain. * Core secretary to deal with the details of voting, notification, etc. == Issues * Discussion takes place. * When a consensus resolution appears to have been reached, a vote on that takes place. * All core members vote "yes" or "no". * Successful resolutions must get at least (2/3 * core-size) yes vote. * At least (2/3 * core-size) people must vote, or the measure will fail. * Voting period is normally 1 week, or ending sooner when the result is certain. * Core secretary to deal with the details of voting, notification, etc. == Without Objection * Any core member may ask core, via email, if they can take some mundane action, subject to a quick sanity check of the rest of core. * If no one objects within 48 hours, then that person may proceed (or sooner if (2/3 * core-size) members agree). * If there are any objections, then it will be resolved via the issue voting procedure. * Core secretary may send the OK to proceed message, as the secretary deems appropriate. Any committer may also use this mechanism so long as at least one core member says 'yes' and the previous paragraph is otherwise followed. It is intended to be used for mundane matters that need a quick sanity check, but don't need a more heavy weight and deliberative process. It is believed that the subset of core present for any given 48 period are sufficient for both sanity checking mundane matters and recognizing non-mundane matters that need to be handled via the issues voting procedure. diff --git a/website/content/en/internal/data.adoc b/website/content/en/internal/data.adoc index 19f9bcaf1d..de471c54b9 100644 --- a/website/content/en/internal/data.adoc +++ b/website/content/en/internal/data.adoc @@ -1,14 +1,14 @@ --- title: "User Data Policy" sidenav: docs ---- +--- = User Data Policy == Rationale The FreeBSD Project provides several resources for developers including various machines and data storage. These resources are intended to be used for activities related to the FreeBSD Project. The project does not make any guarantees to developers regarding non-project-related data stored on project resources. Developers are strongly encouraged to not use project resources for storing non-project-related data. The FreeBSD Core team approved the following user data policy which was posted to the Developers mailing list on August 4, 2011. == Policy FreeBSD Project resources should only be used for project-related activities and storing project-related data. diff --git a/website/content/en/internal/expire-bits.adoc b/website/content/en/internal/expire-bits.adoc index 2cbc66cc3a..5e28962bb5 100644 --- a/website/content/en/internal/expire-bits.adoc +++ b/website/content/en/internal/expire-bits.adoc @@ -1,16 +1,16 @@ --- title: "Commit Bit Expiration Policy" sidenav: docs ---- +--- = Commit Bit Expiration Policy == Rationale Over time, FreeBSD committers may find other demands on their time, and decide that they wish to resign their commit bit. However, under some circumstances, a committer may become inactive over a long period of time without explicitly resigning their bit. Over the long term, these accounts can represent a security risk, as well as posing procedural questions regarding the degree to which contact information and access methods for the account are maintainable. For these reasons, the FreeBSD Core Team approved the following commit bit expiration policy, last updated in November 2018. == Policy Documentation and source committers that have not made a commit in 18 months may be removed from the access file from time to time. For ports committers this period is 12 months. Committers that wish to get back their commit bits will have to reapply with the appropriate authority. If all of a committer's commit bits expire, then the committer's `FreeBSD.org` account may also be suspended at the FreeBSD Core Team's discretion. An account is suspended by disabling login access and any other services (such as CGI scripts or non-trivial mail forwarding configurations) that execute under the committer's account. Simple mail forwarding will continue to work, and an individual may e-mail `core@FreeBSD.org` to update mail forwarding settings. The committer's files may or may not be preserved at the FreeBSD Core Team's discretion. A suspended account will be reactivated if any of a committer's commit bits are restored. diff --git a/website/content/en/internal/hats.adoc b/website/content/en/internal/hats.adoc index 850560f6e1..9a3c8b7a0c 100644 --- a/website/content/en/internal/hats.adoc +++ b/website/content/en/internal/hats.adoc @@ -1,40 +1,40 @@ --- title: "Hats Term Limits Policy" sidenav: docs ---- +--- = Hats Term Limits Policy == Rationale The FreeBSD Core team appoints several individuals ("hats") that perform critical roles within the project. It is important to reduce single points of failure in these roles. Additionally, turnover in hats can provide fresh insight and help avoid burnout. The current set of core-appointed hats is core secretary, head release engineer, the security officer, and postmaster. The FreeBSD Core team has approved the following hats term limits policy. This was first posted to the Developers mailing list on June 22, 2012, and amended in June 2015. == Policy An individual may serve as a core-appointed hat given that: * Core approves their appointment or re-appointment to the role. * The individual is willing to continue. * The individual is still able to perform the role effectively. Hats are appointed at the pleasure of core. Appointments may be rescinded by core at any time where this serves the needs of the project. Each hat's term begins three months after the start of a core team's two year term and ends three months after the end of the core team's term. Hats are explicitly approved by the new core team at the start of the hat's term. If a hat becomes vacant during a term, core shall appoint a replacement for the remainder of the term. Core shall review all hats annually. In general it is expected that volunteers serving in hat positions will be limited to serving for four consecutive years, rounded up to the first natural review/appointment cycle. Non volunteers serving in hat positions are still expected to participate in annual reviews and provide for continuity to core's satisfaction. Each hat must appoint a deputy who can cover their role in the case of absence or illness, and be trained and ready to take over the role (subject to core approval) should the role holder resign before the end of their term. If a core team is dissolved prematurely, then the next term for each hat will begin three months after the new core team's term begins. These limits apply to individual hats and not to teams. For teams with a single lead role, the limits shall apply to the lead role. An individual that is not eligible to serve as the lead of a team may continue to serve as a member of the team. diff --git a/website/content/en/internal/i18n.adoc b/website/content/en/internal/i18n.adoc index 9490c53c5e..24c788b150 100644 --- a/website/content/en/internal/i18n.adoc +++ b/website/content/en/internal/i18n.adoc @@ -1,10 +1,10 @@ --- title: "Internationalization Policy" sidenav: docs ---- +--- = Internationalization Policy == Policy The FreeBSD Project uses a list derived from ISO 3166 to describe countries and regions in the world. This list is included in the release distributions and appears on the official website. The FreeBSD Project does not endorse any particular position and changes to this list must be approved by the FreeBSD Core team. diff --git a/website/content/en/internal/members.adoc b/website/content/en/internal/members.adoc index 34bd565dec..9ef509e333 100644 --- a/website/content/en/internal/members.adoc +++ b/website/content/en/internal/members.adoc @@ -1,65 +1,65 @@ --- title: "FreeBSD Project Members" sidenav: docs ---- +--- = FreeBSD Project Members == FreeBSD Project Members A FreeBSD Project Member is an individual who has made a notable contribution to the FreeBSD Project, and who is continuing to contribute to the Project. That may be in the form of new code, documentation, or patches to existing code and documentation, or in other ways that the Core Team designates, including community management and advocacy. === Committers Committers are those Project members who have been granted commit access (a "commit bit") to one or more of the Project's repositories. === Member Benefits: * an @freebsd.org email address which also gives them regular Bugzilla and Phabricator logins * permission to assign bugs to themselves in bugzilla * access to freefall and the universe build machines * access to the test clusters * the right to attend developer summits * access to the developers@ mailing list === Committer Benefits: In addition to the Ordinary Member benefits, active Committers (those who have made a commit within the previous year) are able to vote in Core elections. === Member Responsibilities: All Members should ensure that all contributed material: * adheres to the Project's standards and practices. * is correctly attributed to its authors. * has appropriate licensing. Where this is the original work of the Project Member, the standard FreeBSD license is preferred. Members MUST create SSH and PGP keys in order to gain access to Project resources. Members are bound by the Project's Code of Conduct, particularly when representing the Project in external fora. Member status is conferred by a ballot of Core members, or by a ballot of other groups that Core may designate such as Portmgr or Doceng. Any FreeBSD Committer or Member may propose candidates for member status. Core, or groups designated by Core that award Member status, should review that status at least once annually and retire inactive accounts. There is no formal definition of inactive accounts. Core and the designated teams may use their own discretion. ''''' === FAQ: Is a mentor assigned to each newly created Project Member? * Project Members are only assigned a mentor if they become a committer, or if they have a commit bit reactivated after a significant period of inactivity. This only applies to Committers since the primary purpose of a mentor is to review what the mentee intends to commit. * No such formal arrangement is required when someone is made into an ordinary Project Member, but it is expected that the people that sponsor a new Member will assist them with setting up their accounts and gaining access to Project resources and so forth. Do you have to become an Ordinary Member before you can be granted a commit bit? * No. There is no requirement for prospective Committers to have spent time as Ordinary Members. However it is anticipated that this will become a common practice as part of the route towards committer-hood. Do Committers who have given up their commit bits effectively become just Ordinary Members? * All Committers are Project members, but former Committers are considered Committer Alumni. Alumni may revert back to active Committers simply by requesting reinstatement of their commit access. How does this affect the existing 3rd Party Developer status? * Existing 3rd Party Developers will be promoted to Project Members. diff --git a/website/content/en/internal/proposing-committers.adoc b/website/content/en/internal/proposing-committers.adoc index 6932657835..5beae44a2c 100644 --- a/website/content/en/internal/proposing-committers.adoc +++ b/website/content/en/internal/proposing-committers.adoc @@ -1,14 +1,14 @@ --- title: "Proposing Committers" sidenav: docs ---- +--- = Proposing Committers The following advice is intended for potential mentors in deciding whether a candidate might be suitable to propose for a commit bit, and in preparing a commit-bit proposal for consideration by the Core Team or its delegates. Note that in the case of delegated approval (e.g., to Portmgr or Doceng), additional procedures or constraints may apply (e.g., to the nature of the contribution). Commit-bit proposal reviewers will look for several key attributes from potential developers: strong technical abilities, a track record of contributions to the FreeBSD Project, evidence of their ability to work independently within the community (i.e., that mentoring will not need to continue indefinitely), evidence of the ability of a developer to engage constructively with the FreeBSD community (and in particular, have the social skills to navigate occasionally heated online debate), and a commitment to contribute to the project in the future. Typically, supporting material for a commit-bit proposal will include a description of the candidate's background and training/education, the context for their contributions to the project (e.g., as a volunteer, employee, etc), references to patches/PRs/commits justifying their contribution track record, pointers at mailing-list or other community participation (e.g., presentations at BSD conferences), a strong indication of constructive engagement with their mentor to date, and a list of interests and potential areas of continuing and future contribution. Potential mentors are reminded that it is far easier to grant commit access than revoke it, and hence significant weight is given to constructive interaction with the community, rather than simply technical contributions. If a mentor is uncertain as to whether a candidate is suitable, it may be sensible to initially contact the Core Team via an informal request for guidance rather than a formal proposal -- this might lead to advice to continue, requests for further supporting material, or the suggestion that a proposal should be deferred while further track record is accrued. It is hoped that requests to gain further experience or to generate additional evidence of community participation and contribution will be taken in the spirit that they are intended: granting of a commit bit is a significant action and based in large part on work performed, rather than simply strong technical abilities. The project would rather take a conservative approach in granting commit rights than grant them prematurely. In some cases, 'vendor commit bits' may be granted to allow direct commits to device drivers (or potentially other components) maintained by, for example, a device vendor. These may be held to a lower standard of past community involvement based on a strong commitment by the vendor and an experienced mentor, as well as limited charter to make changes in the system independently. It is extremely important that such commit bits be used with suitable discretion and awareness of community concerns; it is the responsibility of the mentor to ensure that no undesirable tension arises, and that changes are in keeping with project procedures and community expectations. If a commit bit is granted in this context, it may be revoked when the individual leaves their employer; however, there is also a substantial history of individuals with 'vendor commit bits' making more broad contributions and this is the hoped for outcome! Mentors proposing vendor commit bits should take all steps necessary to ensure that commit bits are granted only to individuals who can take responsibility for the quality and testing of contributions they make on behalf of the vendor, and have the necessary technical and social skills to engage constructively with the community. It is recommended that proposals for such bits contain to the greatest extent the same content as expected of ordinary commit bits, with a particular focus on quality of technical contribution. diff --git a/website/content/en/internal/software-license.adoc b/website/content/en/internal/software-license.adoc index 310dedb30f..6c74f191a5 100644 --- a/website/content/en/internal/software-license.adoc +++ b/website/content/en/internal/software-license.adoc @@ -1,154 +1,154 @@ --- title: "Software License Policy" sidenav: docs ---- +--- = Software License Policy == Philosophy The FreeBSD Project aims to produce a complete, BSD-licensed operating system allowing consumers of the system to produce derivative products without constraint or further license obligations. We invite and greatly appreciate the contribution of both changes and additions under the two-clause BSD license, and encourage the adoption of this license by other open source projects. Use of the BSD license is key to encouraging the adoption of advanced operating system technology, and on many notable occasions has been pivotal to widespread use of new technology. We accept however that compelling reasons exist to allow differently-licensed software to be included in the FreeBSD source tree. We require any software under alternative licenses to be carefully isolated in the source tree so that it cannot contaminate BSD-only components. Such cautious management encourages licensing clarity and facilitates the production of BSD-only derivative products. Unless a special exception is made, no existing BSD-licensed components may be replaced with differently-licensed software. We instead encourage FreeBSD and third party developers to seek the relicensing or reimplementation of critical components under the BSD license. Such would ease their more integral adoption into the FreeBSD operating system. == Policy * The import of new software licensed under any licenses other than the BSD license and BSD-Like Licenses (as defined below) requires the prior approval of the FreeBSD Core Team. Requests for import must include: ** A list of features or bug fixes that the new version or patches contain, along with evidence that our users need those features. PRs or references to mailing list discussions are ideal forms of evidence. ** This process should be used for all software imports, not just those that require Core Team review. The mere existence of a new version does not justify an import of software to source or ports. ** A list of FreeBSD branches that may be affected. Expansions of scope require a new request to and approval from the FreeBSD Core Team. * The Apache License 2.0 is acceptable for use in some cases. The Core Team must approve the import of new Apache License licensed components or the change of license of existing components to the Apache License. ** This license is approved for the following components: *** LLVM toolchain and (with LLVM Exceptions) runtime components. *** Subversion and its dependencies * The BSD+Patent License is acceptable for use in some cases. The Core Team must approve the import of new BSD+Patent License licensed components or the change of license of existing components to the BSD+Patent License. ** This license is approved for the following components: *** EDK2 derived code related to UEFI functionality * The Common Development and Distribution License (CDDL) is acceptable for use in some cases. The Core Team must approve the import of new CDDL licensed components or the change of license of existing components to the CDDL. ** This license is approved for the following components: *** DTrace *** ZFS filesystem including kernel support and userland utilities * Historically, the phrase 'All Rights Reserved.' was included in all copyright notices. The BSD releases had it to comply with the Buenos Aires Convention of 1910 in the Americas. With the ratification of the Berne Convention in 2000, it became obsolete. As such, the FreeBSD project recommends that new code omit the phrase and encourages existing copyright holders to remove it. In 2018, the project updated its templates to remove it. === Acceptable licenses The following licenses are considered to be acceptable BSD-Like Licenses for the purpose of this Policy. They must be reproduced verbatim on any new code. Deviations or the use of any other license must be approved by the FreeBSD Core Team: * The 2 clause version of the BSD license .... /*- * Copyright (c) [year] [your name] * * 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. * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR 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 AUTHOR 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. * * [id for your version control system, if any] */ .... * The 3 clause version of the BSD license .... /*- * Copyright (c) [year] [your name] * * 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. Neither the name of the author nor the names of its contributors may * be used to endorse or promote products derived from this software * * THIS SOFTWARE IS PROVIDED BY THE AUTHOR 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 AUTHOR 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. * * [id for your version control system, if any] */ .... * The ISC License .... /*- * Copyright (c) [year] [copyright holder] * * Permission to use, copy, modify, and distribute this software for any * purpose with or without fee is hereby granted, provided that the above * copyright notice and this permission notice appear in all copies. * * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. * * [id for your version control system, if any] */ .... * The MIT License .... /*- * Copyright (c) [year] [copyright holders] * * Permission is hereby granted, free of charge, to any person obtaining a copy * of this software and associated documentation files (the "Software"), to deal * in the Software without restriction, including without limitation the rights * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell * copies of the Software, and to permit persons to whom the Software is * furnished to do so, subject to the following conditions: * * The above copyright notice and this permission notice shall be included in * all copies or substantial portions of the Software. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN * THE SOFTWARE. * * [id for your version control system, if any] */ .... diff --git a/website/content/en/ipv6/w6d-www-stats.adoc b/website/content/en/ipv6/w6d-www-stats.adoc index c1eeb50cc5..88e0b53f77 100644 --- a/website/content/en/ipv6/w6d-www-stats.adoc +++ b/website/content/en/ipv6/w6d-www-stats.adoc @@ -1,50 +1,50 @@ --- title: "Page hits per minute and address family on www.freebsd.org" sidenav: developers ---- +--- //// Copyright (c) 2011 The FreeBSD Foundation All rights reserved. This documentation was written by Bjoern Zeeb under sponsorship from the FreeBSD Foundation. 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. THIS SOFTWARE IS PROVIDED BY THE AUTHOR 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 AUTHOR 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. //// = Page hits per minute and address family on www.freebsd.org == Category Navigation * link:..[IPv6 in FreeBSD] * link:../w6l[World IPv6 Launch] * link:../w6d[World IPv6 Day] ** link:.[www stats] == IPv6 hits from 2011-06-07 12:00 to 2011-06-09 11:59 link:../../gifs/ipv6/w6d-www-stats-v6-large.png[image:../../gifs/ipv6/w6d-www-stats-v6.png[IPv6 hits from 2011-06-07 12:00 to 2011-06-09 11:59]] == IPv4 and IPv6 hits from 2011-06-07 12:00 to 2011-06-09 11:59 link:../../gifs/ipv6/w6d-www-stats-large.png[image:../../gifs/ipv6/w6d-www-stats.png[IPv4 and IPv6 hits from 2011-06-07 12:00 to 2011-06-09 11:59]] diff --git a/website/content/en/ipv6/w6l.adoc b/website/content/en/ipv6/w6l.adoc index bf8335490f..426638d84b 100644 --- a/website/content/en/ipv6/w6l.adoc +++ b/website/content/en/ipv6/w6l.adoc @@ -1,47 +1,47 @@ --- title: "FreeBSD and World IPv6 Launch" sidenav: developers ---- +--- //// Copyright (c) 2012 Bjoern A. Zeeb 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. THIS SOFTWARE IS PROVIDED BY THE AUTHOR 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 AUTHOR 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. //// = FreeBSD and World IPv6 Launch == Category Navigation * link:..[IPv6 in FreeBSD] * link:.[World IPv6 Launch] * link:../w6d[World IPv6 Day] ** link:../w6d-www-stats[www stats] == FreeBSD on World IPv6 Launch FreeBSD supported World IPv6 Day in 2011 and we continue to help to spread the word about IPv6 with World IPv6 Launch on 6 June 2012. Stay tuned for more news. Meanwhile you can find more information about World IPv6 Launch on The Internet Society's web page http://www.worldipv6launch.org/[www.worldipv6launch.org]. diff --git a/website/content/en/platforms/ia64/_index.adoc b/website/content/en/platforms/ia64/_index.adoc index 0de5144030..6c8b16ce7d 100644 --- a/website/content/en/platforms/ia64/_index.adoc +++ b/website/content/en/platforms/ia64/_index.adoc @@ -1,26 +1,26 @@ --- title: "FreeBSD/ia64 Project" sidenav: developers ---- +--- = FreeBSD/ia64 Project [.right] image:../../gifs/ia64/mckinley-die.png[McKinley die] == Table Of Contents * <> * <> * link:machines[Hardware List] * link:refs[References] [[intro]] == Introduction The FreeBSD/ia64 project pages contain information about the FreeBSD port to Intel's IA-64 architecture; officially known as the Intel Itanium(R) Processor Family (IPF). As with the port itself, these pages are still mostly a work in progress. [[status]] == Current status The ia64 port is considered a tier 2 platform through FreeBSD 10. After this it will no longer be supported. diff --git a/website/content/en/platforms/ia64/refs.adoc b/website/content/en/platforms/ia64/refs.adoc index f0d27cdf21..c7b43ee473 100644 --- a/website/content/en/platforms/ia64/refs.adoc +++ b/website/content/en/platforms/ia64/refs.adoc @@ -1,49 +1,49 @@ --- title: "FreeBSD/ia64 Project -- references" sidenav: developers ---- +--- = FreeBSD/ia64 Project -- references == References This page contains a collection of links to relevant reference material. === Architecture * Intel Software Developer's Manual, revision 2.1 ** https://people.FreeBSD.org/~marcel/refs/ia64/sdm-2.1/245317.pdf[Volume 1: Application Architecture (pdf)] ** https://people.FreeBSD.org/~marcel/refs/ia64/sdm-2.1/245318.pdf[Volume 2: System Architecture (pdf)] ** https://people.FreeBSD.org/~marcel/refs/ia64/sdm-2.1/245319.pdf[Volume 3: Instruction Set Reference (pdf)] ** https://people.FreeBSD.org/~marcel/refs/ia64/sdm-2.1/24869909.pdf[Specification Update (pdf)] * Intel Software Developer's Manual, revision 2.2 ** https://people.FreeBSD.org/~marcel/refs/ia64/sdm-2.2/24531705.pdf[Volume 1: Application Architecture (pdf)] ** https://people.FreeBSD.org/~marcel/refs/ia64/sdm-2.2/24531805.pdf[Volume 2: System Architecture (pdf)] ** https://people.FreeBSD.org/~marcel/refs/ia64/sdm-2.2/24531905.pdf[Volume 3: Instruction Set Reference (pdf)] === Processor Implementations * Itanium (Merced) ** https://people.FreeBSD.org/~marcel/refs/ia64/itanium/24532003.pdf[Processor Reference Manual (pdf)] * Itanium 2 (McKinley, Madison, Madison II) ** https://people.FreeBSD.org/~marcel/refs/ia64/itanium2/25111003.pdf[Processor Reference Manual (pdf)] === Chipset * http://developer.intel.com/design/archives/itanium/downloads/248703.htm[Intel 460GX Chipset Datasheet] * http://developer.intel.com/design/archives/itanium/downloads/248704.htm[Intel 460GX Chipset System Software Developer's Manual] * Intel E8870 Chipset Datasheets ** http://developer.intel.com/design/chipsets/datashts/251111.htm[Intel E8870IO Server I/O Hub (SIOH)] ** http://developer.intel.com/design/chipsets/datashts/251112.htm[Intel E8870 Scalable Node Controller (SNC)] ** http://developer.intel.com/design/chipsets/datashts/251113.htm[Intel E8870DH DDR Memory Hub (DMH)] ** http://developer.intel.com/design/chipsets/datashts/252034.htm[Intel E8870SP Scalability Port Switch (SPS)] ** http://developer.intel.com/design/chipsets/e7500/datashts/290732.htm[Intel 82870P2 PCI/PCI-X 64-bit Hub 2 (P64H2)] ** http://developer.intel.com/design/chipsets/datashts/290744.htm[Intel 82801DB I/O Controller Hub 4 (ICH4)] * Hewlett-Packard zx1 ** http://h21007.www2.hp.com/dspp/files/unprotected/linux/zx1-ioa-mercury_ers.pdf[zx1 ioa reference specification] ** http://h21007.www2.hp.com/dspp/files/unprotected/linux/zx1-mio.pdf[zx1 memory and I/O (mio) reference specification] === Runtime * http://developer.intel.com/design/itanium/downloads/245358.htm[Software Conventions & Runtime Architecture Guide] * http://developer.intel.com/design/itanium/downloads/245370.htm[Processor-specific Application Binary Interface (ABI)] diff --git a/website/content/en/portmgr/charter.adoc b/website/content/en/portmgr/charter.adoc index 5e51515508..627c24278e 100644 --- a/website/content/en/portmgr/charter.adoc +++ b/website/content/en/portmgr/charter.adoc @@ -1,28 +1,28 @@ --- title: "Charter for the Ports Management Team" sidenav: about ---- +--- = Charter for the Ports Management Team The FreeBSD Ports Collection is a product intended first and foremost for the end-users of FreeBSD. The Ports Management Team (portmgr) is the group charged with overseeing its development. Its members are appointed by the FreeBSD Core Team (core). The primary responsibility of the portmgr team is to ensure that the FreeBSD Ports Developer community provides a ports collection that is functional, stable, up-to-date and full-featured. Its secondary responsibility is to coordinate among the committers and developers who work on it. The Ports Management Team has the following specific responsibilities: * Assure the integrity of the Ports Collection by managing commits to the `ports` portion of the FreeBSD repository. This includes maintaining certain key files directly; running test builds of proposed large changes; and acting as arbiter over other commits. * Maintain the automated http://pkg.FreeBSD.org[package building cluster], and make the resulting packages available for download by FreeBSD users. * Work with the FreeBSD Security team to ensure that security problems are indentified and handled in a timely fashion. * Work with FreeBSD Ports and Documentation Committers to keep the relevant documentation up to date. * To the extent possible with a volunteer project, ensure that the legal rights of authors whose works are installed in the Ports Collection are respected. * Act as arbiter of first resort for disputes between FreeBSD community members such as maintainers and committers. * Manage commit access to the ports tree. All new committer approvals must be sent to admins@, and CC'd to core@; they must be PGP-signed. * Establish guidelines and policies governing the rights and responsibilities of Ports Committers and maintainers. * Help prioritize future directions for the overall Ports Collection. In addition to its specific responsibilities, The Ports Management Team may take whatever actions it believes prudent to manage the ports collection responsibly. Please see link:../policies/[Ports Team Policies] for a complete list of the current policies which have been adopted to help implement these goals. This charter is under the control of the FreeBSD Core Team. It is valid until such time as it is modified or revoked by the Core Team; any changes to this charter must be approved by the Core Team. diff --git a/website/content/en/portmgr/implementation.adoc b/website/content/en/portmgr/implementation.adoc index 0797cf721d..9fca62ba3e 100644 --- a/website/content/en/portmgr/implementation.adoc +++ b/website/content/en/portmgr/implementation.adoc @@ -1,54 +1,54 @@ --- title: "Implementation Issues Involving the Ports Collection" sidenav: about ---- +--- = Implementation Issues Involving the Ports Collection == The Ports Tree Is Not Branched Unlike the `src` tree, the FreeBSD ports tree is *not* branched. It has always been felt that there are too few volunteers to be able to handle the work of merging hundreds of changes from the latest tree into various branches. == Practical Considerations There are thousands, if not tens of thousands, of user installations that track the ports tree on a daily basis, rather than relying on the packages that shipped with the most current FreeBSD release. Accordingly, any fatal error in the ports framework will immediately affect all of these sites. This is why commits to `bsd.port.mk` are only allowed with portmgr approval. Except in unusual cases, this approval is only granted after a regression test has been run on a dedicated area of the automated http://pointyhat.FreeBSD.org[ports building cluster]. Typically, a dozen or more proposed changes to the infrastructure are tested at the same time, and only after a build of the entire ports tree succeeds will portmgr commit the changes. [[requires_regression_test]] == Changes That Require Regression Tests Changes to `bsd.port.mk` are not the only commits that can have a drastic effect on the tree. We request that any such changes also be tested on the cluster. Examples of such changes that should be tested before committing include: * changes to packages with many dependencies, including X11 servers, GNOME, KDE, gettext, autotools, and so forth * changes that change the "accepted best practice" for ports Makefiles, such as definitions or usage of common make variables (or `Makevar`s). (e.g. consolidation of various implementations of USE_*, WITH_*, and so forth) * large repocopies (such as when an existing port category is divided up) If you are unsure of whether your proposed change will require a regression test, please send email to portmgr@FreeBSD.org. == Implications for the Release Cycle When a new release of FreeBSD is upcoming, committers are asked to shift their emphasis away from introducing new ports and features and instead focus on fixing existing problems. At some time during the release, the tree is `tagged` and packages are created from each of the ports, for each of the architectures. Due to the large number of ports and the speed of the slower architectures, the build process takes several days. In an ideal world, these would be the packages that went on the release CDs, and the time from the creation of the packages to the time of the actual release would be just long enough to test them and no longer. However, in practice, problems are found with both the ports and with the source tree as the QA effort continues. But to be able to release in a timely manner, only certain port changes will be merged back into the actual (tagged) tree, and the affected packages will be rebuilt. Only severe security problems and licensing issues will have their tags slipped in this manner. Since the release period can take weeks, it is unrealistic not to allow any commit to the ports tree during this time. The problem with allowing unrestricted commits at that time is that it becomes impossible to separate out only the critical changes so that they, and only they, can have their affected tags slipped. The terminology for changes that are not allowed is `sweeping changes`. [[sweeping_changes]] == What Is A Sweeping Change? A `sweeping change` is a commit that would affect a non-trivial number of packages in a way such that any other change (such as fixing a single security problem) would mean that we would have to rebuild the entire set of packages, which would delay the upcoming release, possibly by weeks, because the set of changes overlap. Here is an incomplete list. If you are unsure that your proposed change falls into this categorization, you *must* ask portmgr before committing. * any commit to `bsd.*.mk` * anything else that would normally require a link:#requires_regression_test[regression test] * shared library version bumps * repocopies involving multiple ports The following do not fall into the above category: * commits to leaf ports (i.e. ports upon which no other port depends) * cosmetic changes that would not affect the package (such as changes to `pkg_descr`) * new ports * repocopies of individual ports To summarize: the basic test is *will this change affect other packages?*. diff --git a/website/content/en/portmgr/policies_committing.adoc b/website/content/en/portmgr/policies_committing.adoc index 87395e4cc2..0e1d211510 100644 --- a/website/content/en/portmgr/policies_committing.adoc +++ b/website/content/en/portmgr/policies_committing.adoc @@ -1,28 +1,28 @@ --- title: "Policies of the Ports Management Team: Committing To The Tree" sidenav: about ---- +--- = Policies of the Ports Management Team: Committing To The Tree These are the specific policies that the Ports Management Team has adopted regarding commits to the ports tree. == Changes to `bsd.port.mk` portmgr acts as sole committer for `bsd.port.mk` at all times. Proposed changes must be submitted as PRs and assigned to portmgr. == Changes when the tree is open Open to everything that would not link:../implementation/#requires_regression_test[require a regression test]. == Changes when the tree is frozen All changes must be approved by portmgr. In general, only the following will be accepted: * fixes that would prevent a port from installing, deinstalling or running properly for the *upcoming* release. * security problems. If sufficiently severe, these may imply the need to create a slipped tag. * licensing issues. These require a slipped tag. == Changes when the tree is thawed No link:../implementation#sweeping_changes[sweeping changes]. This is to prevent possibly having to rebuild all the release packages. diff --git a/website/content/en/portmgr/policies_contributors.adoc b/website/content/en/portmgr/policies_contributors.adoc index 511b86030b..af7f10661a 100644 --- a/website/content/en/portmgr/policies_contributors.adoc +++ b/website/content/en/portmgr/policies_contributors.adoc @@ -1,27 +1,27 @@ --- title: "Policies of the Ports Management Team: Maintainers and Committers" sidenav: about ---- +--- = Policies of the Ports Management Team: Maintainers and Committers These are the time periods that apply to maintainer and committer responses to issues brought to their attention via email. [[pr_timeout]] == Problem Report (PR) Timeouts The time limit for a maintainer to respond to a PR is two weeks. After that period, if it is a minor change, any ports committer can commit the change. If it is a major change (e.g., would require a regression run), please contact portmgr first. We have an add-on to the Problem Reports database known as the auto-assigner, which attempts to automatically notify maintainers of PRs; however, it depends on the Summary containing category/portname. In general, various people attempt to catch and fix cases where it does not work, but you should not assume so. Therefore, please check to see whether or not the maintainer knows about the PR before declaring a timeout. You can generally tell this from the Audit-Trail and Cc: lines in the PR. [[maintainer_reset]] == Maintainer Reset A maintainer who does not respond to any port issues for 3 months may be reset by any ports committer. If you are a committer and concerned about whether you are doing the right thing, please contact portmgr. This period may be shortened by portmgr if the email address returns with a hard bounce. In this case, it is probably desirable to reset all the maintainer's ports and check the status of any PRs. [[commit_privileges]] == Commit Privileges Ports committers who are not active for one year will lose commit privileges. portmgr will contact the committer by email before invoking this limit. diff --git a/website/content/en/portmgr/qa.adoc b/website/content/en/portmgr/qa.adoc index 93c8814698..289b8ab1b7 100644 --- a/website/content/en/portmgr/qa.adoc +++ b/website/content/en/portmgr/qa.adoc @@ -1,46 +1,46 @@ --- title: "Quality Assurance Tasks for the Ports Management Team" sidenav: about ---- +--- = Quality Assurance Tasks for the Ports Management Team There are a number of tasks that the Ports Management Team undertakes to try to improve the quality of the Ports Collection. These fall into two main categories: link:#qa-before-release[activities during a release cycle] and link:#qa-between-releases[activities between release cycles]. [[qa-before-release]] == Activities During a Release Cycle * Work with the link:../../releng/[Release Engineering Team] to coordinate the release schedule. * Work with the RE team to determine which pre-built packages can be included on the default install ISOs. * Cut over to the new quarterly branch. [[qa-between-releases]] == Activities Between Release Cycles * Manage the https://pkg-status.freebsd.org/[Ports Build Cluster] machines. These machines continually build packages on all possible combinations of OS release and CPU architecture (in our terminology, `build environments`.) These builds also produce error logs for packages that do not build correctly (see the above URL). Periodically, the team marks these ports as BROKEN so that maintainers may be notified. (See below.) Successfully built packages (at least, the ones that are freely redistributable) are also copied to the master FTP server and thus become the default "latest package" for installations that use packages rather than ports. * Notify the FreeBSD community of problems within the Ports Collection so that problems do not get overlooked. To do this, there are a number of emailed reports. Ones marked `public` are posted to freebsd-ports. ** a public list of all ports to be removed due to security problems, build failures, or general obsolescence, unless they are fixed first. ** private email to all maintainers of the affected ports (including ports dependent on the above). ** private email to all maintainers of ports that are already marked BROKEN and/or FORBIDDEN. ** private email to maintainers who are not committers, who have PRs filed against their ports (to flag PRs that might never have been Cc:ed to them). ** public email about port commits that break building of INDEX. ** public email about port commits that send the revision metadata backwards (and thus confuse tools like portupgrade). ** a public list of all ports that have at least one file that fails to fetch from any non-FreeBSD mastersite. For the complete list of results for all files versus all mastersites, see https://people.FreeBSD.org/~ehaupt/distilator/[Emanuel Haupt's port survey]. ** private email to an affected port maintainer when a port is about to be marked BROKEN, Cc:ed to the last committer to the port. (This email is not automated but it should be sent as a courtesy.) * Remove expired ports. Ports that have been marked BROKEN for some time are marked DEPRECATED (with an EXPIRATION_DATE) and then are removed if no one has fixed them by that time. The intent of this process is to try to ensure that if a user installs a port, there is the best possible chance that it can be made to work. In other cases, ports are marked DEPRECATED when they have been replaced by a newer version and the older version is no longer maintained by the authors. The EXPIRATION_DATE should generally be set at least two months in the future to allow everyone sufficient time to upgrade. diff --git a/website/content/en/projects/summerofcode.adoc b/website/content/en/projects/summerofcode.adoc index f954fe1da6..7c42db82bf 100644 --- a/website/content/en/projects/summerofcode.adoc +++ b/website/content/en/projects/summerofcode.adoc @@ -1,151 +1,151 @@ --- title: "FreeBSD Summer Projects" sidenav: developers ---- +--- = FreeBSD Summer Projects The FreeBSD Project is looking forward to participating as a mentoring organization in https://summerofcode.withgoogle.com/[Google Summer of Code] 2020. This program offers students a stipend of https://developers.google.com/open-source/gsoc/help/student-stipends[up to $6,600 USD] to contribute to an open source project over the summer break. We have had over 200 successful students working on FreeBSD as part of this program since 2005. This page and the https://wiki.freebsd.org/SummerOfCodeIdeas[ideas lists] will be updated throughout the application period to include new information, such as project ideas, proposal information, and potential mentor contact information. If you don't see an idea that interests you, visit again in a couple of days! Additionally, we welcome proposals unrelated to the ideas listed here. * <> * <> * <> * <> * <> * <> * <> [[benefits]] == Benefit of Participating Google Summer of Code is an exciting opportunity for students to "intern" with an open source project for a summer. The FreeBSD Project, as one of the most successful and oldest open source projects, is an excellent place to do this internship. Founded in 1993, the project now consists of several hundred "committers" and tens of thousands of contributors. FreeBSD is the foundation for many commercial products, including Apple's Mac OS X, NetApp's OnTap/GX, Juniper's JunOS, as well countless other products, and is widely used in the Internet Service Provider and corporate IT worlds. Many of these sponsors participate daily in the FreeBSD community, and students have the opportunity to develop software ideas in an exciting environment with many real world applications, and under the mentorship of experienced developers. After the summer ends, students can be sponsored by Google or the FreeBSD Foundation to attend operating systems and open source conferences to present on their work, and a significant number go on to become FreeBSD developers. It's also a great job networking opportunity! [[ideas]] == Example Proposal Ideas The FreeBSD Project maintains a https://wiki.FreeBSD.org/SummerOfCodeIdeas[list of possible ideas] on our wiki. All projects listed are believed to be sized for a useful summer hacking, and have technical contacts who can help answer questions as you write your proposal. We also maintain a more generic https://wiki.FreeBSD.org/IdeasPage[Ideas Page]. These projects are less suitable as Summer of Code projects as they may be scoped larger or smaller than a summer, or might not have such a clear mentor - we suggest e-mailing our soc-admins alias for help if you do decide to propose one of them. These pages exist to help provide inspiration. Students are also welcome, and are indeed encouraged to propose your own ideas, and if the proposal is strong, we'll try to match you with a mentor! For additional ideas about upcoming development projects in FreeBSD, take a look at recent link:../status/[Developer Status Reports]. [[students]] == Past Student Projects For a complete list of student projects from previous years, visit: * https://wiki.FreeBSD.org/SummerOfCode2019Projects[Summer of Code 2019 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2018Projects[Summer of Code 2018 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2017Projects[Summer of Code 2017 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2016Projects[Summer of Code 2016 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2015Projects[Summer of Code 2015 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2014Projects[Summer of Code 2014 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2013Projects[Summer of Code 2013 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2012Projects[Summer of Code 2012 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2011Projects[Summer of Code 2011 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2010Projects[Summer of Code 2010 FreeBSD Projects Wiki] * https://wiki.FreeBSD.org/SummerOfCode2009Projects[Summer of Code 2009 FreeBSD Projects Wiki] * link:../summerofcode-2008/[Summer of Code 2008 FreeBSD Projects Summary] * link:../summerofcode-2007/[Summer of Code 2007 FreeBSD Projects Summary] * link:../summerofcode-2006/[Summer of Code 2006 FreeBSD Projects Summary] * link:../summerofcode-2005/[Summer of Code 2005 FreeBSD Projects Summary] See also our wiki pages for student projects [https://wiki.FreeBSD.org/SummerOfCode2008[2008], https://wiki.FreeBSD.org/SummerOfCode2007[2007], https://wiki.FreeBSD.org/SummerOfCode2006[2006], and https://wiki.FreeBSD.org/SummerOfCode2005[2005]]. [[proposals]] == Proposal Guidelines Students are responsible for writing a proposal and submitting it to Google before the application deadline. The following outline was adapted from the Perl Foundation. The objective of the proposal is to identify what is to be done, explain why this needs to be done, and convince us that: * You are qualified to do this project. This means both having the necessary background and demonstrating a general understanding of the problem. * You have the resources (especially time!) needed to complete the project within the working period of the Summer of Code. A strong proposal will include (at least): === General Information * *Name* * *Email* * *Phone* * *IM/IRC* * *Availability* + How many hours per week will you spend working on this? How many on other things? What other obligations (work, school, vacation, weddings, etc.) do you have this summer? Be as specific as possible: when will the project begin and end? You should be ready to produce a day by day schedule before the program starts.) + *Please note*: participating in Google Summer of Code is a significant time commitment, and you should not apply if you already have another full-time job planned for the summer. * *Biography* + Who are you? What skills do you bring to this project? What is your past involvement with The FreeBSD Project? (Past involvement is not required, but ideally you will have at least installed FreeBSD and perhaps fixed a bug or two) If your project includes programming in a particular language, such as C, or in a specific environment, such as the kernel or an embedded platform, what experience do you have working in that area? Are you familiar with or a user of revision control systems? Have you completed courses that will be relevant to your project idea? What do you think you will need to learn to complete this project? * *Possible Mentor* + Optional, but highly recommended. Do not put a name here if you have not contacted them. === Project Information * *Project Title* + In forty characters or less, what you propose to do. * *Project Description* + A few paragraphs describing your project. Direct copies from the ideas page will be rejected - proposals should reveal that you have done some research into the problem and its solutions. Include both what you will be doing and why it is a good thing for The FreeBSD Project. * *Deliverables* + A list quantifiable results and related code milestones. We suggest at least two milestones before the mid-term evaluations and two after. Where appropriate, this schedule should include multiple committable or releasable points so people can benefit from and/or test your work as early as possible. * *Test Plan* + What parts of your code need testing and how do you plan to test them? This might include both functionality and performance tests. * *Project Schedule* + How long will the project take? When can you begin work? [[mentors]] == Mentors A number of FreeBSD committers are willing to mentor students. A good place to start is the 'Technical contacts' listed with the example projects on the https://wiki.FreeBSD.org/SummerOfCodeIdeas[ideas page]. [[infrastructure]] == Infrastructure Provided to Students We expect project work to be done in GitHub repositories in order to facilitate student collaboration, provide public access and archiving for the on-going student projects, and to help mentors and the community monitor on-going work. Students will also be asked to maintain wiki pages on their on-going projects. In the past, e-mail, IRC, and instant messaging have proven popular among students and mentors, and students participating in the FreeBSD summer program are encouraged to use these and other electronic communication mechanisms to become active in the community. [[faq]] == Frequently Asked Questions * *When are proposals due, and how do I submit mine?* + At the time of writing, Google has announced the following dates of interest relating to the application process: + ** *12 March* - Student application period opens. ** *27 March 18:00 UTC* - Student application period closes. ** *23 April* - Accepted students announced, students start creating their work plans. Community bonding period starts. ** *14 May* - Coding starts. ** *6 August* - Suggested end of coding. + Note that these dates may change, and the Google FAQ timeline is the authoritative source of detailed schedule information: ** https://summerofcode.withgoogle.com/how-it-works/[GSoC Timeline] + All students must register with, and submit applications via, the Google Summer of Code home page: ** https://summerofcode.withgoogle.com/[Google Summer of Code Home Page] * *What advice do you have for a student who might want to submit a proposal?* + Experience suggests that the strongest proposals come from students who contact FreeBSD developers and potential mentors well in advance of submitting their proposal, seek feedback on their proposal ideas, and write proposals that reflect time spent exploring and understanding the problem area to be addressed. Even if the FreeBSD developer(s) you contact aren't the eventual mentor of the project, their feedback can be invaluable. * *Can I submit multiple project proposals to the FreeBSD Project?* + Yes, but do make sure you invest adequate time in each proposal. We are not able to accept more than one project per student, so you may do better spending more time on one or two detailed proposals than by submitting lots of less-detailed ones. * *Will the FreeBSD Project accept more than one student for the same idea?* + In general, we will accept only one student for any given proposal idea, as most proposal ideas in our ideas list are sized with a single student summer project in mind. This is a good reason to consider coming up with your own idea, or at least, making sure that your proposal for one of our project ideas reflects your unique contribution and viewpoint. If you plan to submit multiple proposals, you might consider doing one with an idea from the list, and another with an original idea. * *What if my proposal is not selected in the application process? Can I still participate?* + We always have more good applications than student places, but that doesn't mean you can't do the project anyway. The FreeBSD Project always welcomes new volunteers to work on projects, and is generally happy to provide mentoring and support for students whose proposals could not be selected in order to allow them to work on their project anyway. You will need to work with the FreeBSD Project GSoC administrators to identify a possible mentor. However, Google will not fund that participation. * *What projects were completed successfully by students in previous summers?* + Please see the https://wiki.FreeBSD.org/SummerOfCode2018Projects[2018 FreeBSD Summer of Code page], as well as older project pages from https://wiki.FreeBSD.org/SummerOfCode2017Projects[2017], https://wiki.FreeBSD.org/SummerOfCode2016Projects[2016], https://wiki.FreeBSD.org/SummerOfCode2015Projects[2015], https://wiki.FreeBSD.org/SummerOfCode2014Projects[2014], https://wiki.FreeBSD.org/SummerOfCode2013Projects[2013], https://wiki.FreeBSD.org/SummerOfCode2012Projects[2012], https://wiki.FreeBSD.org/SummerOfCode2011Projects[2011], https://wiki.FreeBSD.org/SummerOfCode2010Projects[2010], https://wiki.FreeBSD.org/SummerOfCode2009Projects[2009], link:summerofcode-2008.html[2008], link:summerofcode-2007.html[2007], link:summerofcode-2006.html[2006], and link:summerofcode-2005.html[2005] for a list of the completed projects from previous years. * *How can I learn more about FreeBSD?* + The link://www.FreeBSD.org/[FreeBSD Project Home Page] is the best way to learn more about the project - from there you can reach the FreeBSD Handbook, FreeBSD Developer's Handbook, project mailing list archives, regular project status reports, and more. If you have questions about specific project ideas, e-mail the technical contacts for those ideas. If you have general GSoC questions relating to FreeBSD, such as if you are unable to reach a project technical contact, need help finding documentation, or want to know who might be a good person to talk to about your idea, send them to soc-admins@FreeBSD.org. * *Is there an IRC channel I can join to talk about proposal ideas or get help finding out more?* + You can join #freebsd-soc on the efnet IRC network to chat with FreeBSD developers interested in mentoring student proposals and projects, past FreeBSD/GSoC students, and other students applying to FreeBSD/GSoC this year. diff --git a/website/content/en/releases/1.0/announce.adoc b/website/content/en/releases/1.0/announce.adoc index 9a273245b0..166b470c72 100644 --- a/website/content/en/releases/1.0/announce.adoc +++ b/website/content/en/releases/1.0/announce.adoc @@ -1,49 +1,49 @@ --- title: "FreeBSD 1.0 Announcement" sidenav: download ---- +--- = FreeBSD 1.0 Announcement From: jkh@whisker.lotus.ie (Jordan K. Hubbard) + Newsgroups: comp.os.386bsd.announce + Subject: FreeBSD 1.0 RELEASE now available + Date: 1 Nov 1993 16:12:20 -0800 The first "official" release of FreeBSD 1.0 is now available, no more greek letters - this is the "production" release. While a fair number of bugs were also whacked between EPSILON and RELEASE, the following additional features deserve special mention: * A dynamic buffer cache mechanism that automagically grows and shrinks as you use the memory for other things. This should speed up disk operations significantly. * The Linux sound driver for Gravis UltraSound, SoundBlaster, etc. cards. * Mitsumi CDROM interface and drive. * Updated install floppies. * More fail-safe probing of devices on the ISA bus. This makes it much harder for devices to conflict with each other. * Advance syscons support for XFree86 2.0. For more information, please read the release notes. FreeBSD 1.0 RELEASE may be obtained by ftp on freebsd.cdrom.com, and on its various mirror sites within a day or so. Release structure: FreeBSD.cdrom.com:~ftp/pub/FreeBSD/ FreeBSD-1.0-RELEASE/ bin+src releases. FreeBSD-1.0-EPSILON-to-RELEASE Upgrade patches for existing EPSILON sites. Thanks, as usual, to all the kind individuals on the net who aided us significantly bu finding bugs, contributing fixes and just generally lending moral support. Thank You! Also, continuing thanks to Walnut Creek CDROM who's ongoing (and, up to now, profitless) support has made this all possible. Questions, as usual, should be sent to "freebsd-questions@freefall.cdrom.com". Bug reports to "freebsd-bugs@freefall.cdrom.com" and general technical commentary to "freebsd-hackers@freefall.cdrom.com". Regards, + The FreeBSD Team. link:../../[Release Home] diff --git a/website/content/en/releases/10.2R/signatures.adoc b/website/content/en/releases/10.2R/signatures.adoc index 6a6c18a22d..5e33708e01 100644 --- a/website/content/en/releases/10.2R/signatures.adoc +++ b/website/content/en/releases/10.2R/signatures.adoc @@ -1,59 +1,59 @@ --- title: "FreeBSD 10.2 Release Checksum Signatures" sidenav: download localRel: 10.2 localBranchName: "RELEASE" localBranchStable: "stable/10" localBranchReleng: "releng/10.2" localRelSha256: "../checksums/CHECKSUM.SHA256-FreeBSD-10.2-RELEASE" localRelMd5: "../checksums/CHECKSUM.MD5-FreeBSD-10.2-RELEASE" ---- +--- = FreeBSD {{% param localRel %}} Release Checksum Signatures == Signed Checksum Signatures This page contains links to the PGP-signed checksum files for FreeBSD {{% param localRel %}}. Please note, the `MD5` checksums are provided to quickly test for image corruption during download. The `MD5` checksums alone should _not_ be used to fully verify the images. The `SHA256` checksums should always be used to fully verify the image. == Installation Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA256` |`MD5` |amd64 (x86_64) |link:{{% param localRelSha256 %}}-amd64.asc[SHA256] |link:{{% param localRelMd5 %}}-amd64.asc[MD5] |i386 |link:{{% param localRelSha256 %}}-i386.asc[SHA256] |link:{{% param localRelMd5 %}}-i386.asc[MD5] |ia64 |link:{{% param localRelSha256 %}}-ia64.asc[SHA256] |link:{{% param localRelMd5 %}}-ia64.asc[MD5] |powerpc |link:{{% param localRelSha256 %}}-powerpc.asc[SHA256] |link:{{% param localRelMd5 %}}-powerpc.asc[MD5] |powerpc64 |link:{{% param localRelSha256 %}}-powerpc-powerpc64.asc[SHA256] |link:{{% param localRelMd5 %}}-powerpc-powerpc64.asc[MD5] |sparc64 |link:{{% param localRelSha256 %}}-sparc64.asc[SHA256] |link:{{% param localRelMd5 %}}-sparc64.asc[MD5] |=== == Virtual Machine Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA256` |`MD5` |amd64 (x86_64) |link:{{% param localRelSha256 %}}-amd64-vm.asc[SHA256] |link:{{% param localRelMd5 %}}-amd64-vm.asc[MD5] |i386 |link:{{% param localRelSha256 %}}-i386-vm.asc[SHA256] |link:{{% param localRelMd5 %}}-i386-vm.asc[MD5] |=== == SD Card Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Board Name |`SHA256` |`MD5` |BEAGLEBONE |link:{{% param localRelSha256 %}}-arm-armv6-BEAGLEBONE.asc[SHA256] |link:{{% param localRelMd5 %}}-arm-armv6-BEAGLEBONE.asc[MD5] |CUBOX/HUMMINGBOARD |link:{{% param localRelSha256 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA256] |link:{{% param localRelMd5 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[MD5] |GUMSTIX |link:{{% param localRelSha256 %}}-arm-armv6-GUMSTIX.asc[SHA256] |link:{{% param localRelMd5 %}}-arm-armv6-GUMSTIX.asc[MD5] |PANDABOARD |link:{{% param localRelSha256 %}}-arm-armv6-PANDABOARD.asc[SHA256] |link:{{% param localRelMd5 %}}-arm-armv6-PANDABOARD.asc[MD5] |RPI-B |link:{{% param localRelSha256 %}}-arm-armv6-RPI-B.asc[SHA256] |link:{{% param localRelMd5 %}}-arm-armv6-RPI-B.asc[MD5] |WANDBOARD |link:{{% param localRelSha256 %}}-arm-armv6-WANDBOARD.asc[SHA256] |link:{{% param localRelMd5 %}}-arm-armv6-WANDBOARD.asc[MD5] |=== diff --git a/website/content/en/releases/10.3R/signatures.adoc b/website/content/en/releases/10.3R/signatures.adoc index 509edc5ef7..9848414584 100644 --- a/website/content/en/releases/10.3R/signatures.adoc +++ b/website/content/en/releases/10.3R/signatures.adoc @@ -1,59 +1,59 @@ --- title: "FreeBSD 10.3 Release Checksum Signatures" sidenav: download localRel: 10.3 localBranchName: "RELEASE" localBranchStable: "stable/10" localBranchReleng: "releng/10.3" localRelSha256: "../checksums/CHECKSUM.SHA256-FreeBSD-10.3-RELEASE" localRelSha512: "../checksums/CHECKSUM.SHA512-FreeBSD-10.3-RELEASE" ---- +--- = FreeBSD {{% param localRel %}} Release Checksum Signatures == Signed Checksum Signatures This page contains links to the PGP-signed checksum files for FreeBSD {{% param localRel %}}. Please note, the `SHA256` checksums are provided to quickly test for image corruption during download. The `SHA256` checksums alone should _not_ be used to fully verify the images. The `SHA512` checksums should always be used to fully verify the image. == Installation Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386.asc[SHA512] |link:{{% param localRelSha256 %}}-i386.asc[SHA256] |ia64 |link:{{% param localRelSha512 %}}-ia64.asc[SHA512] |link:{{% param localRelSha256 %}}-ia64.asc[SHA256] |powerpc |link:{{% param localRelSha512 %}}-powerpc.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc.asc[SHA256] |powerpc64 |link:{{% param localRelSha512 %}}-powerpc-powerpc64.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc-powerpc64.asc[SHA256] |sparc64 |link:{{% param localRelSha512 %}}-sparc64.asc[SHA512] |link:{{% param localRelSha256 %}}-sparc64.asc[SHA256] |=== == Virtual Machine Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64-vm.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-i386-vm.asc[SHA256] |=== == SD Card Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Board Name |`SHA512` |`SHA256` |BEAGLEBONE |link:{{% param localRelSha512 %}}-arm-armv6-BEAGLEBONE.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BEAGLEBONE.asc[SHA256] |CUBOX/HUMMINGBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA256] |GUMSTIX |link:{{% param localRelSha512 %}}-arm-armv6-GUMSTIX.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-GUMSTIX.asc[SHA256] |PANDABOARD |link:{{% param localRelSha512 %}}-arm-armv6-PANDABOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-PANDABOARD.asc[SHA256] |RPI-B |link:{{% param localRelSha512 %}}-arm-armv6-RPI-B.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI-B.asc[SHA256] |WANDBOARD |link:{{% param localRelSha512 %}}-arm-armv6-WANDBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-WANDBOARD.asc[SHA256] |=== diff --git a/website/content/en/releases/10.4R/signatures.adoc b/website/content/en/releases/10.4R/signatures.adoc index 6c1bcaf54a..8b428f4981 100644 --- a/website/content/en/releases/10.4R/signatures.adoc +++ b/website/content/en/releases/10.4R/signatures.adoc @@ -1,59 +1,59 @@ --- title: "FreeBSD 10.4 Release Checksum Signatures" sidenav: download localRel: 10.4 localBranchName: "RELEASE" localBranchStable: "stable/10" localBranchReleng: "releng/10.4" localRelSha256: "../checksums/CHECKSUM.SHA256-FreeBSD-10.4-RELEASE" localRelSha512: "../checksums/CHECKSUM.SHA512-FreeBSD-10.4-RELEASE" ---- +--- = FreeBSD {{% param localRel %}} Release Checksum Signatures == Signed Checksum Signatures This page contains links to the PGP-signed checksum files for FreeBSD {{% param localRel %}}. Please note, the `SHA256` checksums are provided to quickly test for image corruption during download. The `SHA256` checksums alone should _not_ be used to fully verify the images. The `SHA512` checksums should always be used to fully verify the image. == Installation Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386.asc[SHA512] |link:{{% param localRelSha256 %}}-i386.asc[SHA256] |ia64 |link:{{% param localRelSha512 %}}-ia64.asc[SHA512] |link:{{% param localRelSha256 %}}-ia64.asc[SHA256] |powerpc |link:{{% param localRelSha512 %}}-powerpc.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc.asc[SHA256] |powerpc64 |link:{{% param localRelSha512 %}}-powerpc-powerpc64.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc-powerpc64.asc[SHA256] |sparc64 |link:{{% param localRelSha512 %}}-sparc64.asc[SHA512] |link:{{% param localRelSha256 %}}-sparc64.asc[SHA256] |=== == Virtual Machine Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64-vm.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-i386-vm.asc[SHA256] |=== == SD Card Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Board Name |`SHA512` |`SHA256` |BEAGLEBONE |link:{{% param localRelSha512 %}}-arm-armv6-BEAGLEBONE.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BEAGLEBONE.asc[SHA256] |CUBOX/HUMMINGBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA256] |GUMSTIX |link:{{% param localRelSha512 %}}-arm-armv6-GUMSTIX.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-GUMSTIX.asc[SHA256] |PANDABOARD |link:{{% param localRelSha512 %}}-arm-armv6-PANDABOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-PANDABOARD.asc[SHA256] |RPI-B |link:{{% param localRelSha512 %}}-arm-armv6-RPI-B.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI-B.asc[SHA256] |WANDBOARD |link:{{% param localRelSha512 %}}-arm-armv6-WANDBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-WANDBOARD.asc[SHA256] |=== diff --git a/website/content/en/releases/11.0R/signatures.adoc b/website/content/en/releases/11.0R/signatures.adoc index 72aa8b3e63..46ca3c634a 100644 --- a/website/content/en/releases/11.0R/signatures.adoc +++ b/website/content/en/releases/11.0R/signatures.adoc @@ -1,62 +1,62 @@ --- title: "FreeBSD 11.0 Release Checksum Signatures" sidenav: download localRel: 11.0 localBranchName: "RELEASE" localBranchStable: "stable/11" localBranchReleng: "releng/11.0" localRelSha256: "../checksums/CHECKSUM.SHA256-FreeBSD-11.0-RELEASE" localRelSha512: "../checksums/CHECKSUM.SHA512-FreeBSD-11.0-RELEASE" ---- +--- = FreeBSD {{% param localRel %}} Release Checksum Signatures == Signed Checksum Signatures This page contains links to the PGP-signed checksum files for FreeBSD {{% param localRel %}}. == Installation Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386.asc[SHA512] |link:{{% param localRelSha256 %}}-i386.asc[SHA256] |powerpc |link:{{% param localRelSha512 %}}-powerpc.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc.asc[SHA256] |powerpc64 |link:{{% param localRelSha512 %}}-powerpc-powerpc64.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc-powerpc64.asc[SHA256] |sparc64 |link:{{% param localRelSha512 %}}-sparc64.asc[SHA512] |link:{{% param localRelSha256 %}}-sparc64.asc[SHA256] |aarch64 |link:{{% param localRelSha512 %}}-arm64-aarch64.asc[SHA512] |link:{{% param localRelSha256 %}}-arm64-aarch64.asc[SHA256] |=== == Virtual Machine Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64-vm.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-i386-vm.asc[SHA256] |aarch64 |link:{{% param localRelSha512 %}}-arm64-aarch64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-arm64-aarch64-vm.asc[SHA256] |=== == SD Card Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Board Name |`SHA512` |`SHA256` |BANANAPI |link:{{% param localRelSha512 %}}-arm-armv6-BANANAPI.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BANANAPI.asc[SHA256] |BEAGLEBONE |link:{{% param localRelSha512 %}}-arm-armv6-BEAGLEBONE.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BEAGLEBONE.asc[SHA256] |CUBOX/HUMMINGBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA256] |CUBIEBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBIEBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBIEBOARD.asc[SHA256] |CUBIEBOARD2 |link:{{% param localRelSha512 %}}-arm-armv6-CUBIEBOARD2.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBIEBOARD2.asc[SHA256] |GUMSTIX |link:{{% param localRelSha512 %}}-arm-armv6-GUMSTIX.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-GUMSTIX.asc[SHA256] |PANDABOARD |link:{{% param localRelSha512 %}}-arm-armv6-PANDABOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-PANDABOARD.asc[SHA256] |RPI-B |link:{{% param localRelSha512 %}}-arm-armv6-RPI-B.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI-B.asc[SHA256] |RPI2 |link:{{% param localRelSha512 %}}-arm-armv6-RPI2.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI2.asc[SHA256] |WANDBOARD |link:{{% param localRelSha512 %}}-arm-armv6-WANDBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-WANDBOARD.asc[SHA256] |=== diff --git a/website/content/en/releases/11.1R/signatures.adoc b/website/content/en/releases/11.1R/signatures.adoc index 4bccf585ad..20687e5842 100644 --- a/website/content/en/releases/11.1R/signatures.adoc +++ b/website/content/en/releases/11.1R/signatures.adoc @@ -1,62 +1,62 @@ --- title: "FreeBSD 11.1 Release Checksum Signatures" sidenav: download localRel: 11.1 localBranchName: "RELEASE" localBranchStable: "stable/11" localBranchReleng: "releng/11.1" localRelSha256: "../checksums/CHECKSUM.SHA256-FreeBSD-11.1-RELEASE" localRelSha512: "../checksums/CHECKSUM.SHA512-FreeBSD-11.1-RELEASE" ---- +--- = FreeBSD {{% param localRel %}} Release Checksum Signatures == Signed Checksum Signatures This page contains links to the PGP-signed checksum files for FreeBSD {{% param localRel %}}. == Installation Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386.asc[SHA512] |link:{{% param localRelSha256 %}}-i386.asc[SHA256] |powerpc |link:{{% param localRelSha512 %}}-powerpc.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc.asc[SHA256] |powerpc64 |link:{{% param localRelSha512 %}}-powerpc-powerpc64.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc-powerpc64.asc[SHA256] |sparc64 |link:{{% param localRelSha512 %}}-sparc64.asc[SHA512] |link:{{% param localRelSha256 %}}-sparc64.asc[SHA256] |aarch64 |link:{{% param localRelSha512 %}}-arm64-aarch64.asc[SHA512] |link:{{% param localRelSha256 %}}-arm64-aarch64.asc[SHA256] |=== == Virtual Machine Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64-vm.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-i386-vm.asc[SHA256] |aarch64 |link:{{% param localRelSha512 %}}-arm64-aarch64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-arm64-aarch64-vm.asc[SHA256] |=== == SD Card Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Board Name |`SHA512` |`SHA256` |BANANAPI |link:{{% param localRelSha512 %}}-arm-armv6-BANANAPI.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BANANAPI.asc[SHA256] |BEAGLEBONE |link:{{% param localRelSha512 %}}-arm-armv6-BEAGLEBONE.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BEAGLEBONE.asc[SHA256] |CUBOX/HUMMINGBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA256] |CUBIEBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBIEBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBIEBOARD.asc[SHA256] |CUBIEBOARD2 |link:{{% param localRelSha512 %}}-arm-armv6-CUBIEBOARD2.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBIEBOARD2.asc[SHA256] |GUMSTIX |link:{{% param localRelSha512 %}}-arm-armv6-GUMSTIX.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-GUMSTIX.asc[SHA256] |PANDABOARD |link:{{% param localRelSha512 %}}-arm-armv6-PANDABOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-PANDABOARD.asc[SHA256] |RPI-B |link:{{% param localRelSha512 %}}-arm-armv6-RPI-B.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI-B.asc[SHA256] |RPI2 |link:{{% param localRelSha512 %}}-arm-armv6-RPI2.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI2.asc[SHA256] |WANDBOARD |link:{{% param localRelSha512 %}}-arm-armv6-WANDBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-WANDBOARD.asc[SHA256] |=== diff --git a/website/content/en/releases/11.2R/signatures.adoc b/website/content/en/releases/11.2R/signatures.adoc index 32cf9ef607..07886cff31 100644 --- a/website/content/en/releases/11.2R/signatures.adoc +++ b/website/content/en/releases/11.2R/signatures.adoc @@ -1,62 +1,62 @@ --- title: "FreeBSD 11.2 Release Checksum Signatures" sidenav: download localRel: 11.2 localBranchName: "RELEASE" localBranchStable: "stable/11" localBranchReleng: "releng/11.2" localRelSha256: "../checksums/CHECKSUM.SHA256-FreeBSD-11.2-RELEASE" localRelSha512: "../checksums/CHECKSUM.SHA512-FreeBSD-11.2-RELEASE" ---- +--- = FreeBSD {{% param localRel %}} Release Checksum Signatures == Signed Checksum Signatures This page contains links to the PGP-signed checksum files for FreeBSD {{% param localRel %}}. == Installation Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386.asc[SHA512] |link:{{% param localRelSha256 %}}-i386.asc[SHA256] |powerpc |link:{{% param localRelSha512 %}}-powerpc.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc.asc[SHA256] |powerpc64 |link:{{% param localRelSha512 %}}-powerpc-powerpc64.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc-powerpc64.asc[SHA256] |sparc64 |link:{{% param localRelSha512 %}}-sparc64.asc[SHA512] |link:{{% param localRelSha256 %}}-sparc64.asc[SHA256] |aarch64 |link:{{% param localRelSha512 %}}-arm64-aarch64.asc[SHA512] |link:{{% param localRelSha256 %}}-arm64-aarch64.asc[SHA256] |=== == Virtual Machine Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64-vm.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-i386-vm.asc[SHA256] |aarch64 |link:{{% param localRelSha512 %}}-arm64-aarch64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-arm64-aarch64-vm.asc[SHA256] |=== == SD Card Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Board Name |`SHA512` |`SHA256` |BANANAPI |link:{{% param localRelSha512 %}}-arm-armv6-BANANAPI.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BANANAPI.asc[SHA256] |BEAGLEBONE |link:{{% param localRelSha512 %}}-arm-armv6-BEAGLEBONE.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BEAGLEBONE.asc[SHA256] |CUBOX/HUMMINGBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA256] |CUBIEBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBIEBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBIEBOARD.asc[SHA256] |CUBIEBOARD2 |link:{{% param localRelSha512 %}}-arm-armv6-CUBIEBOARD2.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBIEBOARD2.asc[SHA256] |GUMSTIX |link:{{% param localRelSha512 %}}-arm-armv6-GUMSTIX.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-GUMSTIX.asc[SHA256] |PANDABOARD |link:{{% param localRelSha512 %}}-arm-armv6-PANDABOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-PANDABOARD.asc[SHA256] |RPI-B |link:{{% param localRelSha512 %}}-arm-armv6-RPI-B.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI-B.asc[SHA256] |RPI2 |link:{{% param localRelSha512 %}}-arm-armv6-RPI2.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI2.asc[SHA256] |WANDBOARD |link:{{% param localRelSha512 %}}-arm-armv6-WANDBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-WANDBOARD.asc[SHA256] |=== diff --git a/website/content/en/releases/11.3R/signatures.adoc b/website/content/en/releases/11.3R/signatures.adoc index 114a25807c..a2a310e1ce 100644 --- a/website/content/en/releases/11.3R/signatures.adoc +++ b/website/content/en/releases/11.3R/signatures.adoc @@ -1,61 +1,61 @@ --- title: "FreeBSD 11.3 Release Checksum Signatures" sidenav: download localRel: 11.3 localBranchName: "RELEASE" localBranchStable: "stable/11" localBranchReleng: "releng/11.3" localRelSha256: "../checksums/CHECKSUM.SHA256-FreeBSD-11.3-RELEASE" localRelSha512: "../checksums/CHECKSUM.SHA512-FreeBSD-11.3-RELEASE" ---- +--- = FreeBSD {{% param localRel %}} Release Checksum Signatures == Signed Checksum Signatures This page contains links to the PGP-signed checksum files for FreeBSD {{% param localRel %}}. == Installation Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386.asc[SHA512] |link:{{% param localRelSha256 %}}-i386.asc[SHA256] |powerpc |link:{{% param localRelSha512 %}}-powerpc.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc.asc[SHA256] |powerpc64 |link:{{% param localRelSha512 %}}-powerpc-powerpc64.asc[SHA512] |link:{{% param localRelSha256 %}}-powerpc-powerpc64.asc[SHA256] |sparc64 |link:{{% param localRelSha512 %}}-sparc64.asc[SHA512] |link:{{% param localRelSha256 %}}-sparc64.asc[SHA256] |aarch64 |link:{{% param localRelSha512 %}}-arm64-aarch64.asc[SHA512] |link:{{% param localRelSha256 %}}-arm64-aarch64.asc[SHA256] |=== == Virtual Machine Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Architecture |`SHA512` |`SHA256` |amd64 (x86_64) |link:{{% param localRelSha512 %}}-amd64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-amd64-vm.asc[SHA256] |i386 |link:{{% param localRelSha512 %}}-i386-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-i386-vm.asc[SHA256] |aarch64 |link:{{% param localRelSha512 %}}-arm64-aarch64-vm.asc[SHA512] |link:{{% param localRelSha256 %}}-arm64-aarch64-vm.asc[SHA256] |=== == SD Card Image Checksums [.tblbasic] [.tblwide] [cols=",,",options="header",] |=== |Board Name |`SHA512` |`SHA256` |BANANAPI |link:{{% param localRelSha512 %}}-arm-armv6-BANANAPI.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BANANAPI.asc[SHA256] |BEAGLEBONE |link:{{% param localRelSha512 %}}-arm-armv6-BEAGLEBONE.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-BEAGLEBONE.asc[SHA256] |CUBOX/HUMMINGBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBOX-HUMMINGBOARD.asc[SHA256] |CUBIEBOARD |link:{{% param localRelSha512 %}}-arm-armv6-CUBIEBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBIEBOARD.asc[SHA256] |CUBIEBOARD2 |link:{{% param localRelSha512 %}}-arm-armv6-CUBIEBOARD2.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-CUBIEBOARD2.asc[SHA256] |PANDABOARD |link:{{% param localRelSha512 %}}-arm-armv6-PANDABOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-PANDABOARD.asc[SHA256] |RPI-B |link:{{% param localRelSha512 %}}-arm-armv6-RPI-B.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI-B.asc[SHA256] |RPI2 |link:{{% param localRelSha512 %}}-arm-armv6-RPI2.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-RPI2.asc[SHA256] |WANDBOARD |link:{{% param localRelSha512 %}}-arm-armv6-WANDBOARD.asc[SHA512] |link:{{% param localRelSha256 %}}-arm-armv6-WANDBOARD.asc[SHA256] |=== diff --git a/website/content/en/releases/2.0.5R/announce.adoc b/website/content/en/releases/2.0.5R/announce.adoc index 1ac7b3288a..1b6dde46fd 100644 --- a/website/content/en/releases/2.0.5R/announce.adoc +++ b/website/content/en/releases/2.0.5R/announce.adoc @@ -1,66 +1,66 @@ --- title: "FreeBSD 2.0.5 RELEASE Announcement" sidenav: download ---- +--- = FreeBSD 2.0.5 RELEASE Announcement *Date:* Sat, 10 Jun 1995 13:01:12 -0700 + *From:* "Jordan K. Hubbard" + *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: * ftp://ftp.FreeBSD.org/pub/FreeBSD/2.0.5-RELEASE * ftp://freefall.cdrom.com/pub/FreeBSD/2.0.5-RELEASE 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 + *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 original 2.0.5-RELEASE, we have gone poking and found a couple of bugs on the original boot.flp image. There is now a `/pub/FreeBSD/2.0.5-RELEASE/UPDATES` directory on ftp://ftp.FreeBSD.org/pub/FreeBSD/2.0.5-RELEASE/UPDATES[ftp.cdrom.com] and ftp://freefall.cdrom.com/pub/FreeBSD/2.0.5-RELEASE/UPDATES[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 link:../../[Release Home] diff --git a/website/content/en/releases/2.0.5R/notes.adoc b/website/content/en/releases/2.0.5R/notes.adoc index 1a01e63162..b9c5b6da81 100644 --- a/website/content/en/releases/2.0.5R/notes.adoc +++ b/website/content/en/releases/2.0.5R/notes.adoc @@ -1,757 +1,757 @@ --- title: "FreeBSD 2.0.5 ALPHA Release Notes" sidenav: download ---- +--- = FreeBSD 2.0.5 ALPHA Release Notes .... 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 filesystems 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 filesystems 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 necessary 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 Andrey A. Chernov Bruce Evans David Greenman Garrett A. Wollman Gary Palmer Geoff Rehmet Jack Vogel John Dyson Jordan K. Hubbard Justin Gibbs Paul Richards Poul-Henning Kamp Rich Murphey Rodney W. Grimes Satoshi Asami Søren Schmidt 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 .... link:../../[Release Home] diff --git a/website/content/en/releases/2.0/announce.adoc b/website/content/en/releases/2.0/announce.adoc index e015c60ae3..f012f89b63 100644 --- a/website/content/en/releases/2.0/announce.adoc +++ b/website/content/en/releases/2.0/announce.adoc @@ -1,66 +1,66 @@ --- title: "FreeBSD 2.0 Announcement" sidenav: download ---- +--- = FreeBSD 2.0 Announcement 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" 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 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) link:../../[Release Home] diff --git a/website/content/en/releases/2.0/credits.adoc b/website/content/en/releases/2.0/credits.adoc index 364c782774..495c8c6e1f 100644 --- a/website/content/en/releases/2.0/credits.adoc +++ b/website/content/en/releases/2.0/credits.adoc @@ -1,206 +1,206 @@ --- title: "FreeBSD 2.0 Credits" sidenav: download ---- +--- = FreeBSD 2.0 Credits .... 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 endeavors. 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 Andrew A. Chernov Bruce Evans David Greenman Garrett A. Wollman Gary Palmer Geoff Rehmet Jack Vogel John Dyson Jordan K. Hubbard Paul Richards Poul-Henning Kamp Rich Murphey Rodney W. Grimes Soren Schmidt Additional FreeBSD Contributors (no particular order): Adam Glass Andrew Herbert Andrew Moore Atsushi Murai 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 Keith Moore Marc Frajola Mark Tinguely Martin Birgmeier Paul Kranenburg Paul Mackerras Poul-Henning Kamp Rob Shady Sascha Wildner Scott Mace Sean Eric Fagan Serge V. Vakulenko Steven Wallace Søren Schmidt Terry Lee Theo Deraadt Ugen J.S.Antsilevich Yuval Yarom 386BSD 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 1994/11/18 12:03:25 jkh Exp .... link:../../[Release Home] diff --git a/website/content/en/releases/2.0/install.adoc b/website/content/en/releases/2.0/install.adoc index f36e2843c2..53f8f2e138 100644 --- a/website/content/en/releases/2.0/install.adoc +++ b/website/content/en/releases/2.0/install.adoc @@ -1,488 +1,488 @@ --- title: "FreeBSD 2.0 Installation Guide" sidenav: download ---- +--- = FreeBSD 2.0 Installation Guide .... 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 > | +--------------------------------------------------------------------------+ 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'. 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 d 0 4108599 4108600 2006 unused 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 filesystems. Every FreeBSD system should have, at minimum, a root filesystem and a swap partition allocated. The root filesystem 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 filesystems. We also see that partition h points conveniently to the DOS slice, which we can also assign to a location in our filesystem hierarchy to conveniently share files between FreeBSD and DOS. More on this in a moment. A typical filesystem layout might look like this: / 20MB swap 32MB /usr 120MB /, or the root filesystem, 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 filesystem 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 filesystems 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 (/) filesystem. 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 d 0 4108599 4108600 2006 unused 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 filesystem: 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 filesystem, 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 d 0 4108599 4108600 2006 unused 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 filesystem 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 filesystem mount points. A filesystem 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 filesystem (/) 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 filesystems, 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 filesystems to be created from scratch. We thus go through and assign the rest of the filesystems 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 d 0 4108599 4108600 2006 unused 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 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 filesystems 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. .... link:../../[Release Home] diff --git a/website/content/en/releases/2.0/notes.adoc b/website/content/en/releases/2.0/notes.adoc index f733b9b3d0..2c1449c99f 100644 --- a/website/content/en/releases/2.0/notes.adoc +++ b/website/content/en/releases/2.0/notes.adoc @@ -1,648 +1,648 @@ --- title: "FreeBSD 2.0 Release Notes" sidenav: download ---- +--- = FreeBSD 2.0 Release Notes .... 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 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? ---------------------- 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 filesystems, 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 necessary 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 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 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 constraints 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 work 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 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 .... link:../../[Release Home] diff --git a/website/content/en/releases/2.1.5R/announce.adoc b/website/content/en/releases/2.1.5R/announce.adoc index dae4679047..bdb427c354 100644 --- a/website/content/en/releases/2.1.5R/announce.adoc +++ b/website/content/en/releases/2.1.5R/announce.adoc @@ -1,224 +1,224 @@ --- title: "FreeBSD 1.0 Announcement" sidenav: download ---- +--- = FreeBSD 1.0 Announcement FreeBSD ftp://ftp.FreeBSD.org/pub/FreeBSD/2.1.5-RELEASE[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 http://www.cdrom.com/titles/freebsd.html[CD] from http://www.cdrom.com/[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 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 link:../notes/[Release Notes]. The official sources for FreeBSD are available via anonymous FTP from: ftp://ftp.FreeBSD.org/pub/FreeBSD[ftp.FreeBSD.org]. Or via the WEB at: http://www.FreeBSD.org/releases/[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. * ftp://ftp.au.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.au.FreeBSD.ORG/pub/FreeBSD * ftp://ftp3.au.FreeBSD.ORG/pub/FreeBSD * ftp://ftp4.au.FreeBSD.ORG/pub/FreeBSD == Brazil In case of problems, please contact hostmaster@br.FreeBSD.org. * ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.br.FreeBSD.ORG/pub/FreeBSD * ftp://ftp3.br.FreeBSD.ORG/pub/FreeBSD * ftp://ftp4.br.FreeBSD.ORG/pub/FreeBSD * ftp://ftp5.br.FreeBSD.ORG/pub/FreeBSD * ftp://ftp6.br.FreeBSD.ORG/pub/FreeBSD * ftp://ftp7.br.FreeBSD.ORG/pub/FreeBSD == Canada In case of problems, please contact hostmaster@ca.FreeBSD.org * ftp://ftp.ca.FreeBSD.ORG/pub/FreeBSD == Czech Republic * ftp://sunsite.mff.cuni.cz/OS/FreeBSD + Problem Contact: jj@sunsite.mff.cuni.cz == Estonia In case of problems, please contact hostmaster@ee.FreeBSD.org. * ftp://ftp.ee.freebsd.ORG/pub/FreeBSD == Finland In case of problems, please contact hostmaster@fi.FreeBSD.org. * ftp://ftp.fi.freebsd.ORG/pub/FreeBSD == France * ftp://ftp.ibp.fr/pub/FreeBSD + Problem Contact: Remy.Card@ibp.fr. == Germany In case of problems, please contact hostmaster@de.FreeBSD.org. * ftp://ftp.de.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.de.FreeBSD.ORG/pub/FreeBSD * ftp://ftp3.de.FreeBSD.ORG/pub/FreeBSD * ftp://ftp4.de.FreeBSD.ORG/pub/FreeBSD * ftp://ftp5.de.FreeBSD.ORG/pub/FreeBSD * ftp://ftp6.de.FreeBSD.ORG/pub/FreeBSD * ftp://ftp7.de.FreeBSD.ORG/pub/FreeBSD == Hong Kong * ftp://ftp.hk.super.net/pub/FreeBSD + Problem Contact: ftp-admin@HK.Super.NET. == Ireland In case of problems, please contact hostmaster@ie.FreeBSD.org. * ftp://ftp.ie.FreeBSD.ORG/pub/FreeBSD == Israel * ftp://orgchem.weizmann.ac.il/pub/FreeBSD + Problem Contact: serg@klara.weizmann.ac.il. * ftp://xray4.weizmann.ac.il/pub/FreeBSD + Problem Contact: serg@klara.weizmann.ac.il. == Japan In case of problems, please contact hostmaster@jp.FreeBSD.org. * ftp://ftp.jp.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.jp.FreeBSD.ORG/pub/FreeBSD * ftp://ftp3.jp.FreeBSD.ORG/pub/FreeBSD * ftp://ftp4.jp.FreeBSD.ORG/pub/FreeBSD * ftp://ftp5.jp.FreeBSD.ORG/pub/FreeBSD * ftp://ftp6.jp.FreeBSD.ORG/pub/FreeBSD == Korea In case of problems, please contact hostmaster@kr.FreeBSD.org. * ftp://ftp.kr.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.kr.FreeBSD.ORG/pub/FreeBSD == Netherlands In case of problems, please contact hostmaster@nl.FreeBSD.org. * ftp://ftp.nl.freebsd.ORG/pub/FreeBSD == Poland * ftp://SunSITE.icm.edu.pl/pub/FreeBSD + Problem Contact: ftp@SunSITE.icm.edu.pl == Portugal * ftp://ftp.ua.pt/pub/misc/FreeBSD + Problem Contact: archie@ua.pt == Russia In case of problems, please contact hostmaster@ru.FreeBSD.org. * ftp://ftp.ru.FreeBSD.org/pub/FreeBSD * ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD == South Africa In case of problems, please contact hostmaster@za.FreeBSD.org. * ftp://ftp.za.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.za.FreeBSD.ORG/pub/FreeBSD * ftp://ftp3.za.FreeBSD.ORG/FreeBSD == Sweden In case of problems, please contact the hostmaster@se.FreeBSD.org. * ftp://ftp.se.freebsd.ORG/pub/FreeBSD == Taiwan In case of problems, please contact hostmaster@tw.FreeBSD.org. * ftp://ftp.tw.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.tw.FreeBSD.ORG/pub/FreeBSD * ftp://ftp3.tw.FreeBSD.ORG/pub/FreeBSD == Thailand * ftp://ftp.nectec.or.th/pub/FreeBSD + Problem Contact: ftpadmin@ftp.nectec.or.th == USA In case of problems, please contact hostmaster@FreeBSD.org. * ftp://ftp.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.FreeBSD.ORG/pub/FreeBSD * ftp://ftp3.FreeBSD.ORG/pub/FreeBSD * ftp://ftp4.FreeBSD.ORG/pub/FreeBSD * ftp://ftp5.FreeBSD.ORG/pub/FreeBSD * ftp://ftp6.FreeBSD.ORG/pub/FreeBSD == UK In case of problems, please contact hostmaster@uk.FreeBSD.org. * ftp://ftp.uk.FreeBSD.ORG/packages/unix/FreeBSD * ftp://ftp2.uk.FreeBSD.ORG/pub/walnut.creek/FreeBSD * ftp://ftp3.uk.FreeBSD.ORG/pub/BSD/FreeBSD 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 * ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD * ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD == Brazil * ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD == Finland * ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt link:../../[Release Home] diff --git a/website/content/en/releases/2.1.5R/notes.adoc b/website/content/en/releases/2.1.5R/notes.adoc index b936f031cc..2783a1ad61 100644 --- a/website/content/en/releases/2.1.5R/notes.adoc +++ b/website/content/en/releases/2.1.5R/notes.adoc @@ -1,543 +1,543 @@ --- title: "FreeBSD 2.1.5 Release Notes" sidenav: download ---- +--- = FreeBSD 2.1.5 Release Notes .... 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: file:/usr/share/doc/handbook/handbook.html To read the FAQ: 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 separate). 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 Andrey A. Chernov John Dyson Bruce Evans Justin Gibbs David Greenman Jordan K. Hubbard Poul-Henning Kamp Rich Murphey Gary Palmer Søren Schmidt Peter Wemm Garrett A. Wollman Jörg Wunsch The FreeBSD Development Team, excluding core team members (in alphabetical order by last name): Ugen J.S. Antsilevich Torsten Blum Gary Clark II Adam David Peter Dufault Frank Durda IV Julian Elischer Sean Eric Fagan Stefan Esser Bill Fenner John Fieber Marc G. Fournier Lars Fredriksen Thomas Gellekum Thomas Graichen Rod Grimes John Hay Eric L. Hernes Jeffrey Hsu Gary Jennejohn Andreas Klemm L Jonas Olsson Scott Mace Atsushi Murai Mark Murray Alex Nash Sujal Patel Bill Paul Joshua Peck Macdonald John Polstra Mike Pritchard Doug Rabson James Raynard Geoff Rehmet Martin Renters Paul Richards Ollivier Robert Dima Ruban Wolfram Schneider Andreas Schulz Karl Strickland Paul Traina Guido van Rooij Steven Wallace Nate Williams Jean-Marc Zucconi 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 .... link:../../[Release Home] diff --git a/website/content/en/releases/2.1.6R/announce.adoc b/website/content/en/releases/2.1.6R/announce.adoc index 94d6cf847c..fcd4c0e268 100644 --- a/website/content/en/releases/2.1.6R/announce.adoc +++ b/website/content/en/releases/2.1.6R/announce.adoc @@ -1,24 +1,24 @@ --- title: "FreeBSD 2.1.6 Announcement" sidenav: download ---- +--- = FreeBSD 2.1.6 Announcement Please read an link:../security/[important security announcement] regarding FreeBSD 2.1.6 FreeBSD 2.1.6 is now available in: ____ link:../security[ftp://ftp.FreeBSD.org/pub/FreeBSD/2.1.6-RELEASE] ____ And shortly from its various mirror sites, a list of which may be obtained from: http://www.FreeBSD.org/handbook/mirrors.html This release will also be available on CDROM from http://www.cdrom.com/[Walnut Creek CDROM], hopefully shipping within the next 4-6 weeks. Those puzzled by the near-simultaneous release of 2.1.6 and 2.2 need also look no further than http://www.FreeBSD.org/branch.html for the reasons behind this release schedule. CDROM subscription customers should also see this page for information on Walnut Creek CDROM's plans for these releases. If you are a commercial user of FreeBSD who would like to take advantage of recent bug fixes without making the jump to our more ambitious 2.2 release (or delay that jump until 2.2 has had more time to mature), or if you're simply looking for the lowest-impact upgrade from 2.1.5, then 2.1.6-RELEASE is for you. link:../../[Release Home] diff --git a/website/content/en/releases/2.1.6R/notes.adoc b/website/content/en/releases/2.1.6R/notes.adoc index 7ac3c3e1a9..bad50f4bd8 100644 --- a/website/content/en/releases/2.1.6R/notes.adoc +++ b/website/content/en/releases/2.1.6R/notes.adoc @@ -1,543 +1,543 @@ --- title: "FreeBSD 2.1.6 Release Notes" sidenav: download ---- +--- = FreeBSD 2.1.6 Release Notes .... RELEASE NOTES FreeBSD Release 2.1.6 RELEASE 0. What is this release? ------------------------ FreeBSD 2.1.6R is the follow-on release to 2.1.5R and focuses primarily on fixing bugs, closing security holes and making the system easier to install than 2.1.5. For more information on our 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. Support for the 3COM 3C590 and 3C595 ethernet cards. 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. 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: ---------------------- XFree86 upgraded to new 3.2 release, with support for many new graphics cards. 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 470 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: file:/usr/share/doc/handbook/handbook.html To read the FAQ: 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! 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 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), 3C590 & 3C595 (PCI) 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) 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.6-RELEASE & 2.2-RELEASE 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. 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. 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 Andrey A. Chernov John Dyson Bruce Evans Justin Gibbs David Greenman Jordan K. Hubbard Poul-Henning Kamp Rich Murphey Gary Palmer Søren Schmidt Peter Wemm Garrett A. Wollman Jörg Wunsch The FreeBSD Development Team, excluding core team members (in alphabetical order by last name): Torsten Blum Gary Clark II Adam David Peter Dufault Frank Durda IV Julian Elischer Sean Eric Fagan Stefan Esser Bill Fenner John Fieber Lars Fredriksen Thomas Gellekum Thomas Graichen Rod Grimes James FitzGibbon John Hay Jeffrey Hsu Ugen J.S. Antsilevich Gary Jennejohn Andreas Klemm Warner Losh L Jonas Olsson Eric L. Hernes Scott Mace Atsushi Murai Mark Murray Alex Nash Masafumi NAKANE David E. O'Brien Andras Olah Steve Passe Sujal Patel Bill Paul Joshua Peck Macdonald John Polstra Steve Price Mike Pritchard Doug Rabson James Raynard Geoff Rehmet Martin Renters Paul Richards Ollivier Robert Chuck Robey Dima Ruban Wolfram Schneider Andreas Schulz Karl Strickland Michael Smith Paul Traina Guido van Rooij Steven Wallace Nate Williams Jean-Marc Zucconi Additional FreeBSD helpers and beta testers: Coranth Gryphon Dave Rivers Kaleb S. Keithley Don Lewis 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 .... link:../../[Release Home] diff --git a/website/content/en/releases/2.1.6R/security.adoc b/website/content/en/releases/2.1.6R/security.adoc index fe1f92b170..6ecc091a65 100644 --- a/website/content/en/releases/2.1.6R/security.adoc +++ b/website/content/en/releases/2.1.6R/security.adoc @@ -1,14 +1,14 @@ --- title: "FreeBSD 2.1.6 Security Update" sidenav: download ---- +--- = FreeBSD 2.1.6 Security Update == Security Update A serious security problem affecting FreeBSD 2.1.6 and earlier systems was found. The problem has been corrected within the -stable, -current, and RELENG_2_2 source trees. As an additional precaution, FreeBSD 2.1.6 is no longer available from the FTP distribution sites. An update release (provisionally "FreeBSD 2.1.7") is expected shortly. You can read more about the problem and solution from the ftp://FreeBSD.org/pub/CERT/advisories/FreeBSD-SA-97:01.setlocale[FreeBSD-SA-97:01.setlocale] security announcement. link:../../[Release Home] diff --git a/website/content/en/releases/2.1.7R/announce.adoc b/website/content/en/releases/2.1.7R/announce.adoc index 7f4b22f5a5..e5864d320b 100644 --- a/website/content/en/releases/2.1.7R/announce.adoc +++ b/website/content/en/releases/2.1.7R/announce.adoc @@ -1,24 +1,24 @@ --- title: "FreeBSD 2.1.7 Announcement" sidenav: download ---- +--- = FreeBSD 2.1.7 Announcement FreeBSD 2.1.7 is now available in: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD/2.1.7-RELEASE ____ And shortly from its various mirror sites, a list of which may be obtained from: http://www.FreeBSD.org/handbook/mirrors.html This is a security release to FreeBSD 2.1.6, fixing at least several security holes and addressing a number of outstanding problem reports in that release. FreeBSD 2.1.7 will also be available on CDROM from http://www.cdrom.com/[Walnut Creek CDROM], hopefully shipping within the next 3-4 weeks. If you are a customer of Walnut Creek CDROM and you purchased the 2.1.6 release (either by subscription or by retail) then you are also entitled to a *free upgrade*. All you need to do is send mail to orders@cdrom.com or call 1-800 786-9907 / +1 510 674-0783 Intl, indicate that you would like the free 2.1.7 upgrade and provide your name and address information so that a replacement can be shipped. Walnut Creek CDROM customers will also receive a letter explaining these details. Those puzzled by the near-simultaneous release of 2.1.7 and 2.2 should also look at http://www.FreeBSD.org/ for the reasons behind this release schedule. CDROM subscription customers should see this page for information on Walnut Creek CDROM's plans for these releases. If you are a commercial user of FreeBSD who would like to take advantage of recent bug fixes without making the jump to our more ambitious 2.2 release (or delay that jump until 2.2 has had more time to mature), or if you're simply looking for the lowest-impact upgrade from 2.1.5, then 2.1.7-RELEASE is for you. link:../../[Release Home] diff --git a/website/content/en/releases/2.1.7R/notes.adoc b/website/content/en/releases/2.1.7R/notes.adoc index 27f2ea6389..74a293f85d 100644 --- a/website/content/en/releases/2.1.7R/notes.adoc +++ b/website/content/en/releases/2.1.7R/notes.adoc @@ -1,551 +1,551 @@ --- title: "FreeBSD 2.1.7 Release Notes" sidenav: download ---- +--- = FreeBSD 2.1.7 Release Notes .... RELEASE NOTES FreeBSD 2.1.7 RELEASE 0. What is this release? ------------------------ FreeBSD 2.1.7R is the follow-on release to 2.1.6R and focuses primarily on fixing bugs and closing security holes, the most notable being the setlocale() bug (see ftp://freefall.FreeBSD.org/pub/CERT) in 2.1.6R. For more information on our bleeding-edge development, please see http://www.FreeBSD.org/handbook/current.html. 0. What's New since 2.1.6-RELEASE? ---------------------------------- Since the setlocale() security hole forced us to do another release along the 2.1-STABLE branch, we focused on pulling in a lot of additional bug fixes and security enhancements as well, taking also some time to upgrade sysinstall to deal with the MSDOSFS installation bugs which have hosed so many people & to upgrade a few selected utilities. Aside from these, there are few functional changes in 2.1.7R. 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. Support for the 3COM 3C590 and 3C595 ethernet cards. 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. 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 390 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: file:/usr/share/doc/handbook/handbook.html To read the FAQ: 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! 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 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), 3C590 & 3C595 (PCI) 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) 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 separate). 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 Andrey A. Chernov John Dyson Bruce Evans Justin Gibbs David Greenman Jordan K. Hubbard Poul-Henning Kamp Rich Murphey Gary Palmer Søren Schmidt Peter Wemm Garrett A. Wollman Jörg Wunsch The FreeBSD Development Team, excluding core team members (in alphabetical order by last name): Ugen J.S. Antsilevich Torsten Blum Gary Clark II Adam David Peter Dufault Frank Durda IV Julian Elischer Sean Eric Fagan Stefan Esser Bill Fenner John Fieber Marc G. Fournier Lars Fredriksen Thomas Gellekum Thomas Graichen Rod Grimes John Hay Eric L. Hernes Jeffrey Hsu Gary Jennejohn Andreas Klemm L Jonas Olsson Scott Mace Atsushi Murai Mark Murray Alex Nash Sujal Patel Bill Paul Joshua Peck Macdonald John Polstra Mike Pritchard Doug Rabson James Raynard Geoff Rehmet Martin Renters Paul Richards Ollivier Robert Dima Ruban Wolfram Schneider Andreas Schulz Karl Strickland Paul Traina Guido van Rooij Steven Wallace Nate Williams Jean-Marc Zucconi 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 .... link:../../[Release Home] diff --git a/website/content/en/releases/2.1R/announce.adoc b/website/content/en/releases/2.1R/announce.adoc index 21106839c9..77a39e4274 100644 --- a/website/content/en/releases/2.1R/announce.adoc +++ b/website/content/en/releases/2.1R/announce.adoc @@ -1,27 +1,27 @@ --- title: "FreeBSD 2.1 Announcement" sidenav: download ---- +--- = FreeBSD 2.1 Announcement Date: Sun, 19 Nov 1995 14:48:46 -0800 + From: "Jordan K. Hubbard" + 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://ftp.freebsd.org/pub/FreeBSD/2.1.0-RELEASE/[ftp.freebsd.org] and various FTP https://www.freebsd.org/handbook/mirrors.html[mirror sites throughout the world]. It can also be ordered on CD from http://www.cdrom.com/[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 https://www.freebsd.org/handbook/current.html[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 https://www.freebsd.org/handbook/install.html[installation procedure]. Jordan link:../../[Release Home] diff --git a/website/content/en/releases/2.1R/notes.adoc b/website/content/en/releases/2.1R/notes.adoc index 826e776203..e2b67f68dc 100644 --- a/website/content/en/releases/2.1R/notes.adoc +++ b/website/content/en/releases/2.1R/notes.adoc @@ -1,344 +1,344 @@ --- title: "FreeBSD 2.1 Announcement" sidenav: download ---- +--- = FreeBSD 2.1 Announcement .... 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: file:/usr/share/doc/handbook/handbook.html To read the FAQ: 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 Bruce Evans David Greenman Garrett A. Wollman Gary Palmer Jörg Wunsch John Dyson Jordan K. Hubbard Justin Gibbs Peter Wemm Poul-Henning Kamp Rich Murphey Satoshi Asami Søren Schmidt 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 .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.1R/notes.adoc b/website/content/en/releases/2.2.1R/notes.adoc index f6c061eeb3..b03fa897fd 100644 --- a/website/content/en/releases/2.2.1R/notes.adoc +++ b/website/content/en/releases/2.2.1R/notes.adoc @@ -1,540 +1,540 @@ --- title: "FreeBSD 2.2.1 Release Notes" sidenav: download ---- +--- = FreeBSD 2.2.1 Release Notes .... RELEASE NOTES FreeBSD 2.2.1-RELEASE 2.2.1 is a small incremental fix release to 2.2, primarily aimed at fixing: o Some recently discovered problems with the Adaptec 2940 driver which could cause instability in very heavily loaded systems (like news servers). o A bug which made the package installer fail from CDROM media. o Allow the Intel EtherExpress Pro/100B to work in full-duplex mode. Since the 2.2.1. release follows 2.2 by just over a week, other documentation still refers to this release as simply "2.2" since it is a complete *replacement* for 2.2.0-RELEASE, not simply another point release following it. For even more up-to-date releases along the RELENG_2_2 branch (which is now proceeding onwards toward release 2.2.5), please install from: ftp://releng22.FreeBSD.org/pub/FreeBSD/ This is a snapshot made of RELENG_2_2 on a daily basis (and containing all the latest 2.2 fixes as of that date). 1. What's new since 2.1.7 ------------------------- Lots of installation bugs fixed, more pc98 changes synchronized, geeze, what else? gdb 4.16 has been merged from -current, most of the third-party source now lives under /usr/src/contrib. Updated support for the DEC DEFPA/DEFEA FDDI hardware. The old ``HAVE_FPU'' Makefile option is now finally gone, the selection between the math library using the floating point emulator, and the version using the co-processor is now fully automatic. This will speed up floating-point using programs on sites that didn't like to recompile their `libm' previously. Javier Martin Rueda's `ex' driver has been merged, bringing support for the Intel EtherExpress Pro/10 network cards. The Intel EtherExpress Pro/100B now works in full-duplex mode. The `de' driver now recognizes cards using the DE21140A chip, like the popular SMC9332BDT (10/100 Mbit/s) one. There's now a workaround for the brokenness of the frequently used CMD640 PCI IDE chip in the sources, albeit still disabled by default in 2.2. The number of EISA slots to probe is now a fully supported option, including the ability to save the value from a UserConfig session with dset(8)>. This helps owners of HP NetServer LC machines to install the system on their hardware. Support for the SDL RISCom N2pci sync serial card. Support for Cyclades Cyclom-Y (multi-port async serial) PCI adaptors as well as multiple controllers and the 32-Y (if you are currently using the Cyclades serial adapter, you should re-make your /dev entries and remove the old ones). Updated support for ethernet adaptors which use the DEC DC21X4X chipset. Update to gcc 2.7.2.1 & add support for weak symbols. Many things moved/brought into /usr/src/contrib, updating and cleaning up the source tree accordingly. Support for compiled-in shared library ld paths. Update sgmlfmt to `instant'. Support for SNMP-style interface MIBs, including full RFC 1650-compliant MIBs for the `de' (DEC 21x4x) and `ed' (SMC/WD/Novell) drivers. /stand/sysinstall moved even more towards becoming a more general system management tool. You can actually add a new, from-scratch formatted disk with it now, from partition label to filesystem creation (though it still doesn't modify your /etc/fstab file to make it permanent). The syscons and psm drivers now have a new underlying shared keyboard driver, eliminating many of the previously existing problems with their mutual interaction. Syscons now supports cut & paste in textmode using the moused(8)> utility. 2.2 is the first release that includes full CD-R support for the Plasmon RF41xx, HP4020i, HP6020i, and Philips CDD2000 drives. The driver is still under development (in particular to extend its usability for other devices), but it has been proved to be stable by now. Support for NFSv3 clients and servers went into the 2.2 sources shortly after branching off the 2.0.5/2.1.X tree. There are also other options available with NFS, like the ability to turn an NFSv2 server into asynchronous write mode (which is in violation of the specs, but has precedents e.g. in SGI Irix). Poul-Henning Kamp's phkmalloc replaced the old and blatant BSD malloc implementation. This usually saves a lot of virtual memory for the clients, and offers some neat features like aborting the program on detected malloc abuses, or filling the malloced and/or freed area with junk in order to detect semantical problems in programs that use malloc. The `netatalk' implementation of AppleTalk has been integrated into the sources, most of the integration work courtesy Whistle Communic- ations Corp. The mount option `async' allows asynchronous metadata updates on UFS filesystems, something that is the default e.g. on Linux' ext2fs. This speeds up many i-node intensive filesystem operations (like rm -r) at the cost of an increased risk in case of a system crash. The installation itself makes use of this feature, and could be drastically accelerated by this. (A bindist-only installation from a SCSI CD-ROM can now complete in less than 5 minutes on a fast machine!) The ATAPI CD-ROM support is now reported to work for quite an impressive number of drives. In other words, all the drives that basically adhere to the ATAPI standard are likely to work. There are many new drivers available in the kernel, too many to keep them in mind. Tekram supplied a driver for their DC390 and DC390T controllers. These controllers are based on the AMD 53c974, and the driver is also able to handle other SCSI controllers based on that chip. Of course, with Tekram being generous enough to support the FreeBSD project with their driver, we'd like to encourage you to buy their product. The `ed' and `lnc' drivers now support auto-config- uration for the respective PCI ethernet cards, including many NE2000 clones and the AMD PCnet chips. The SDL RISCom N2 support is new, as well as the PCI version of the Cyclades driver. The Linux emulation is now fully functional, including ELF support. To make its use easier, there are even ports for the required shared libraries, and for the Slackware development environment. Along the same lines, the SysV COFF emulation (aka. SCO emulation) is reported to be working well now. FreeBSD also supports native ELF binaries, although it hasn't been decided yet whether, when, and how we might use this as the default binary format some day. A `brandelf' utility has been added to allow `branding' of non-shared linked ELF binaries where the kernel cannot guess which image activator (FreeBSD, Linux, maybe SysV some day) should be used. This works around one major flaw in the ELF object format, the missing field to mark the ABI it belongs to. Support for APM BIOSes is now in a much better shape. The manual section 9 has been started, describing `official' kernel programming interfaces. We are still seeking volunteers to document interfaces here! The kernel configuration option handling has been largely moved away from the old -D Makefile kludges, towards a system of "opt_foo.h" kernel include files, allowing Makefile dependencies to work again. We expect the old hack that blows the entire compile directory away on each run of config(8)> to go away anytime soon. Unless you're changing weird options, you might now consider using the -n option to config(8)>, or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for you. See also the comments in the handbook about how it works. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec 1535 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 AIC7850 on-board 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. 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 SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). 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 8mm Exabyte) 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!). 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress (not recommended due to driver instability) Intel EtherExpress Pro/10 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), 3C590/592/595/900/905 PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 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? 2.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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber HP4020i, Philips CDD2000 and PLASMON WORM (CDR) drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your 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! 3.2. CDROM ---------- FreeBSD 2.1.7-RELEASE and 2.2-RELEASE 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 from: ftp://ftp.cdrom.com/cdrom/catalog. Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 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 preferred method to submit bug reports from a machine with Internet mail connectivity is to use the send-pr command or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or suggestions, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All 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! 5. Acknowledgements ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Additional FreeBSD helpers and beta testers: Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis 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 Project .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.2R/errata.adoc b/website/content/en/releases/2.2.2R/errata.adoc index 9f84b007ac..db5c3e7445 100644 --- a/website/content/en/releases/2.2.2R/errata.adoc +++ b/website/content/en/releases/2.2.2R/errata.adoc @@ -1,72 +1,72 @@ --- title: "FreeBSD 2.2.2 Errata Notes" sidenav: download ---- +--- = FreeBSD 2.2.2 Errata Notes .... Last minute errata: ------------------- o login as root produces "login_getclass: unknown class 'root'" on system console. Fix: If you have the source distribution installed, simply cp /usr/src/etc/login.conf /etc otherwise, get it from the FreeBSD FTP site using this URL: ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/etc/login.conf instead. Simply cd to /etc and then run fetch(1) with the provided URL. o sysconfig scrambles rc.conf if run again. Fix: Get updated /usr/src from RELENG_2_2 branch and build /usr/src/release/sysinstall, copying the new binary to /stand. If you do not have enough space for src then you could also use the boot/fixit floppy combo from a later 2.2-YYMMDD-RELENG release to simply mount your root partition (using the Fixit option) and copy /stand/sysinstall from the floppy to /stand on your root fs. o Installation floppy does not boot at all - whereas the 2.2.1 floppy worked fine. I get a "panic: double fault" right after it tries to change the root device to fd0c. Fix: The problem is that you have 48MB of RAM and something very mysterious has happened to FreeBSD twixt 2.2.1 and 2.2.2 which makes it fail with just that exact memory size. Given the popularity of 16MB simms, it also explains why none of us have seen it since we typically have either 16MB, 32MB or 64MB of memory in our systems. :) We're working on finding and fixing this problem, but until then the following work-around is in effect for 48MB systems: 1. Boot the 2.2.2 boot floppy and when it comes to the first menu which asks you whether or not you want to go into the kernel configuration editor, choose the "experts only" CLI mode option. Now type: iosize npx0 32768 visual < and do your visual kernel configuration as normal then exit> If you can get through to the installation, go to step 3. 2. If the above does not work, physically remove all but 32MB of memory from your machine and then boot the boot floppy. Unless your problem is totally weird and something we've not seen at all before, you should now be able to go on to step 3. 3. Complete the installation and then boot off your hard disk. This boot should work fine, since you are no longer using the memory filesystem that the installation uses and which seems to interact badly with these memory size issues to create the failure you saw. You will also want to boot with the -c flag at some point and say "iosize npx0 0" to get the full use of all your memory back since the old value of 32768 will have been saved to disk during the initial installation. If you already plan on building a custom kernel, you can skip this step since the value will be reset anyway. .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.2R/notes.adoc b/website/content/en/releases/2.2.2R/notes.adoc index b2512dadd0..b35e8ed57a 100644 --- a/website/content/en/releases/2.2.2R/notes.adoc +++ b/website/content/en/releases/2.2.2R/notes.adoc @@ -1,556 +1,556 @@ --- title: "FreeBSD 2.2.2 Release Notes" sidenav: download ---- +--- = FreeBSD 2.2.2 Release Notes .... RELEASE NOTES FreeBSD 2.2.2-RELEASE o For information about the layout of the release directory, see the ABOUT.TXT file. o For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. For the most up-to-date releases along the RELENG_2_2 branch (which is now proceeding onwards toward release 2.2.5), please install from: ftp://releng22.FreeBSD.org/pub/FreeBSD/ 0. What's new since 2.2.1 ------------------------- A number of bugs in the Adaptec 294x/394x (AHC) driver were fixed which could cause instability on heavily loaded systems. NFSv3 is now the default, with fall-back to NFSv2 occuring as necessary. An lchown() system call has been added for changing the ownership of symlinks. Login classes added for setting default user limits (see login. conf(5)). ftpd now supports virtual FTP hosting. Numerous security fixes (buffer overflows and other potential exploits fixed). Better build support for C++ libraries added. Support for the GLOBAL text/HTML source tag system added (man global). /etc/sysconfig now replaced by /etc/rc.conf - a more concise customization file with more knobs added. Other things in /etc were also neatened up, /etc/netstart being replaced with /etc/rc.network User-mode ppp updated with various fixes and enhancements from 3.0-current. Texinfo documentation mechanisms cleaned up in source tree. 1. What's new since 2.1.7 ------------------------- Lots of installation bugs fixed, more pc98 changes synchronized, geeze, what else? gdb 4.16 has been merged from -current, most of the third-party source now lives under /usr/src/contrib. Updated support for the DEC DEFPA/DEFEA FDDI hardware. The old ``HAVE_FPU'' Makefile option is now finally gone, the selection between the math library using the floating point emulator, and the version using the co-processor is now fully automatic. This will speed up floating-point using programs on sites that didn't like to recompile their `libm' previously. Javier Martin Rueda's `ex' driver has been merged, bringing support for the Intel EtherExpress Pro/10 network cards. The Intel EtherExpress Pro/100B now works in full-duplex mode. The `de' driver now recognizes cards using the DE21140A chip, like the popular SMC9332BDT (10/100 Mbit/s) one. There's now a workaround for the brokenness of the frequently used CMD640 PCI IDE chip in the sources, albeit still disabled by default in 2.2. The number of EISA slots to probe is now a fully supported option, including the ability to save the value from a UserConfig session with dset(8)>. This helps owners of HP NetServer LC machines to install the system on their hardware. Support for the SDL RISCom N2pci sync serial card. Support for Cyclades Cyclom-Y (multi-port async serial) PCI adaptors as well as multiple controllers and the 32-Y (if you are currently using the Cyclades serial adapter, you should re-make your /dev entries and remove the old ones). Updated support for ethernet adaptors which use the DEC DC21X4X chipset. Update to gcc 2.7.2.1 & add support for weak symbols. Many things moved/brought into /usr/src/contrib, updating and cleaning up the source tree accordingly. Support for compiled-in shared library ld paths. Update sgmlfmt to `instant'. Support for SNMP-style interface MIBs, including full RFC 1650-compliant MIBs for the `de' (DEC 21x4x) and `ed' (SMC/WD/Novell) drivers. /stand/sysinstall moved even more towards becoming a more general system management tool. You can actually add a new, from-scratch formatted disk with it now, from partition label to filesystem creation (though it still doesn't modify your /etc/fstab file to make it permanent). The syscons and psm drivers now have a new underlying shared keyboard driver, eliminating many of the previously existing problems with their mutual interaction. Syscons now supports cut & paste in textmode using the moused(8)> utility. 2.2 is the first release that includes full CD-R support for the Plasmon RF41xx, HP4020i, HP6020i, and Philips CDD2000 drives. The driver is still under development (in particular to extend its usability for other devices), but it has been proved to be stable by now. Support for NFSv3 clients and servers went into the 2.2 sources shortly after branching off the 2.0.5/2.1.X tree. There are also other options available with NFS, like the ability to turn an NFSv2 server into asynchronous write mode (which is in violation of the specs, but has precedents e.g. in SGI Irix). Poul-Henning Kamp's phkmalloc replaced the old and blatant BSD malloc implementation. This usually saves a lot of virtual memory for the clients, and offers some neat features like aborting the program on detected malloc abuses, or filling the malloced and/or freed area with junk in order to detect semantical problems in programs that use malloc. The `netatalk' implementation of AppleTalk has been integrated into the sources, most of the integration work courtesy Whistle Communic- ations Corp. The mount option `async' allows asynchronous metadata updates on UFS filesystems, something that is the default e.g. on Linux' ext2fs. This speeds up many i-node intensive filesystem operations (like rm -r) at the cost of an increased risk in case of a system crash. The installation itself makes use of this feature, and could be drastically accelerated by this. (A bindist-only installation from a SCSI CD-ROM can now complete in less than 5 minutes on a fast machine!) The ATAPI CD-ROM support is now reported to work for quite an impressive number of drives. In other words, all the drives that basically adhere to the ATAPI standard are likely to work. There are many new drivers available in the kernel, too many to keep them in mind. Tekram supplied a driver for their DC390 and DC390T controllers. These controllers are based on the AMD 53c974, and the driver is also able to handle other SCSI controllers based on that chip. Of course, with Tekram being generous enough to support the FreeBSD project with their driver, we'd like to encourage you to buy their product. The `ed' and `lnc' drivers now support auto-config- uration for the respective PCI ethernet cards, including many NE2000 clones and the AMD PCnet chips. The SDL RISCom N2 support is new, as well as the PCI version of the Cyclades driver. The Linux emulation is now fully functional, including ELF support. To make its use easier, there are even ports for the required shared libraries, and for the Slackware development environment. Along the same lines, the SysV COFF emulation (aka. SCO emulation) is reported to be working well now. FreeBSD also supports native ELF binaries, although it hasn't been decided yet whether, when, and how we might use this as the default binary format some day. A `brandelf' utility has been added to allow `branding' of non-shared linked ELF binaries where the kernel cannot guess which image activator (FreeBSD, Linux, maybe SysV some day) should be used. This works around one major flaw in the ELF object format, the missing field to mark the ABI it belongs to. Support for APM BIOSes is now in a much better shape. The manual section 9 has been started, describing `official' kernel programming interfaces. We are still seeking volunteers to document interfaces here! The kernel configuration option handling has been largely moved away from the old -D Makefile kludges, towards a system of "opt_foo.h" kernel include files, allowing Makefile dependencies to work again. We expect the old hack that blows the entire compile directory away on each run of config(8)> to go away anytime soon. Unless you're changing weird options, you might now consider using the -n option to config(8)>, or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for you. See also the comments in the handbook about how it works. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec 1535 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 AIC7850 on-board 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. 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 SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). 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 8mm Exabyte) 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!). 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress (not recommended due to driver instability) Intel EtherExpress Pro/10 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), 3C590/592/595/900/905 PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 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? 2.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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber HP4020i, Philips CDD2000 and PLASMON WORM (CDR) drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 2.1.7-RELEASE and 2.2-RELEASE 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 from: ftp://ftp.cdrom.com/cdrom/catalog. Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 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 preferred method to submit bug reports from a machine with Internet mail connectivity is to use the send-pr command or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or suggestions, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All 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! 5. Acknowledgements ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Additional FreeBSD helpers and beta testers: Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis 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 Project .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.5R/announce.adoc b/website/content/en/releases/2.2.5R/announce.adoc index b2282da339..048276b318 100644 --- a/website/content/en/releases/2.2.5R/announce.adoc +++ b/website/content/en/releases/2.2.5R/announce.adoc @@ -1,59 +1,59 @@ --- title: "FreeBSD 2.2.5 Announcement" sidenav: download ---- +--- = FreeBSD 2.2.5 Announcement *Date:* 22 Oct 1997 14:09:08 -0500 + *From:* "Jordan K. Hubbard" + *Subject:* 2.2.5 RELEASE now available from ftp.freebsd.org (and some mirrors) It is my great pleasure, as always, to announce the release of FreeBSD 2.2.5, our next release on the 2.2-stable branch. Those folks who are still running 2.1.x and wish to upgrade to 2.2 technology are now encouraged to do so as 2.2.5 has reached an equivalent level of stability in all of our tests. A number of annoying problems with 2.2.2 have also been fixed (see the link:../notes/[release notes] for more information on this). FreeBSD 2.2.5-RELEASE is available on ftp://ftp.freebsd.org/pub/FreeBSD[ftp.freebsd.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.cdrom.com/[Walnut Creek CDROM], from where it will be shipping shortly as a new 4 CD set containing a lot of extra stuff of interest to programmers and general users alike. The official FTP distribution site for FreeBSD is: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD ____ Or via the WEB page at: ____ http://www.cdrom.com/pub/FreeBSD/[http://www.cdrom.com/pub/FreeBSD] ____ 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 https://www.FreeBSD.org/handbook/mirrors.html[mirror sites] in Argentina, Australia, Brazil, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Ireland, Israel, Japan, Korea, the Netherlands, Poland, Portugal, Russia, South Africa, Sweden, Taiwan, Thailand and the UK (among other countries :). Please check your regional mirrors first by going to: ____ ftp://ftp..freebsd.org/pub/FreeBSD ____ since ftp.freebsd.org is itself rather overloaded at the present time (Id software and Slackware Linux chose the same time to release their latest products :). The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also 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:: ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt link:../../[Release Home] diff --git a/website/content/en/releases/2.2.5R/errata.adoc b/website/content/en/releases/2.2.5R/errata.adoc index 6a5ade5a97..b2fc32db8f 100644 --- a/website/content/en/releases/2.2.5R/errata.adoc +++ b/website/content/en/releases/2.2.5R/errata.adoc @@ -1,106 +1,106 @@ --- title: "FreeBSD 2.2.5 Errata Notes" sidenav: download ---- +--- = FreeBSD 2.2.5 Errata Notes .... The file ERRATA.TXT contains post-release ERRATA for 2.2.5 and should always be considered the definitive place to look first before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For 2.2.5 security advisories, see: ftp://FreeBSD.org/pub/CERT/ For the latest information (note the URL carefully - this is NOT ftp.FreeBSD.org). ---- Security Advisories: Current active security advisories for 2.2.5: One o FreeBSD-SA-97:05 (available from ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT). You may also simply remove /dev/io as a quick work-around if you're not running an X server or some other specialized utility which requires access to the I/O instructions. ---- System Update Information: o The appletalk stack was broken in 2.2.5. Fix: If you plan to run appletalk, you should apply the following patch: ftp://ftp.FreeBSD.org/pub/FreeBSD/updates/2.2.5-RELEASE/atalk.diff.2.2.gz o The line printer spooler lpd will, when sending jobs to remote printers, kill the child process sending to the remote after the timeout specified in the `ct' capability (2 minutes by default). Fix: Please upgrade the lpd subsystem to 2.2-stable. As a workaround, increase the `ct' capability to an unreasonably large number of seconds (like 3600). o Intel "F00F bug" enables users to hang machines with Pentium processors if they have access to the machine and can execute programs. Fix: Update to the 2.2-stable version of the kernel or apply the patch found in: ftp://ftp.FreeBSD.org/pub/FreeBSD/updates/2.2.5-RELEASE/f00f.diff.2.2.gz o A bug in the ipfw code exists where using the "reset tcp" firewall command causes the kernel to write ethernet headers onto random kernel stack locations. Fix: Update to the 2.2-stable version of the kernel or apply the patch found in ftp://ftp.FreeBSD.org/pub/FreeBSD/updates/2.2.5-RELEASE/ipfw.diff.gz o A bug in XF86Setup causes it to fail to create a symbolic link from /usr/X11R6/bin/X to the right X server for your hardware if a link does not already exist. When you type startx the following error is displayed: xinit: No such file or directory (errno 2): no server "X" found in PATH Fix: Execute the following commands (as root) and re-run XF86Setup. # cd /usr/X11R6/bin # ln -s XF86_VGA16 X If XF86Setup asks you if you want to use the existing XF86Config for defaults choose no. When it asks you if you want to create an 'X' link to the server choose yes. o A bug in the phase diagram implementation of user-level ppp causes problems with some ppp implementations when shutting down the link. The line will go dead, but the modem will not hang up unless done manually using pppctl (or a switch). Fix: A version of ppp derived from the -current sources is available from http://www.FreeBSD.org/~brian It should build on any version of FreeBSD from 2.0.5 onwards. This code is available in the -current tree, but not (yet) in the 2.2-STABLE tree. Further documentation can be found at these locations: Document references FAQ handbook .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.5R/notes.adoc b/website/content/en/releases/2.2.5R/notes.adoc index 74c5ab2589..c03bc5e569 100644 --- a/website/content/en/releases/2.2.5R/notes.adoc +++ b/website/content/en/releases/2.2.5R/notes.adoc @@ -1,447 +1,447 @@ --- title: "FreeBSD 2.2.5 Release Notes" sidenav: download ---- +--- = FreeBSD 2.2.5 Release Notes .... RELEASE NOTES FreeBSD 2.2.5-RELEASE o For information about the layout of the release directory, see the ABOUT.TXT file. If you are installing from floppies, it is especially important that you *read this section!* o It is also important to check the ERRATA.TXT file for any late-breaking issues with this release. This file contains the latest information on significant bugs, security problems or other similar issues which an administrator should be aware of. o For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. For the most up-to-date releases along the RELENG_2_2 branch (which is now proceeding onwards toward release 2.2.6), please install from: ftp://releng22.FreeBSD.org/pub/FreeBSD/ Or for the latest 3.0-current (HEAD branch) snapshot releases, please install from: ftp://current.FreeBSD.org/pub/FreeBSD 1. What's new since 2.2.2 ------------------------- Better support for Cyrix and AMD processors. The "world" target in /usr/src/Makefile has been made more independent of the host system, allowing for easier bootstrapping via source from very old systems. Many many fixes to the documentation. Many security enhancements, as reported through CERT and other computer security organizations. The installation program was further updated and fixed, some year-old bogons finally eliminated for 2.2.5. Important subsystems such as BIND and sendmail updated. Support for ethernet media selection. Replacing the far more arcane "link" flag usage, a new media flag to ifconfig permits specific interfaces on multi-port ethernet cards to be selected by name (man ifconfig for more details). Significant improvements to the AHC (Adaptec 394x/294X) driver and AIC7xxx assembler. Enhancements to the serial boot code and GDB remote support. Make work-around available for CMD640 chipset (see /sys/i386/conf/LINT). Newer 3Com 3c589D PCMCIA cards are now supported. A new VGA library (/usr/src/lib/libvgl) now exists for doing simple VGA graphics to syscons ttys (sort of like Linux's libSVGA). The TCP connection timeout in lpd & friends can now be specified by a printcap(5) capability, preventing it from hanging for too long when working in an environment with many network printservers. User-mode ppp updated with various fixes and enhancements from 3.0-current. It's worth re-reading the manual page since some of the following changes may disturb peoples current configurations: o The "set debug" command is now "set log". o The LCP log has been split into an LCP, IPCP and CCP log, so any "set log LCP" lines will need to be changed to "set log LCP IPCP CCP" to see the same output as before. o Ppp now uses syslogd to write its log files. o Ppp now has LQR disabled and openmode active by default. o Ppp now installs as group "network", with mode 4550. You must add group 69 (network) to /etc/group. If you wish to allow users to run "ppp -direct ...", you must enable them by making them a member of group "network". Client-side ppp now requires user id 0. Refer to the ppp(8) man page and the relevent section of the handbook for full details. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 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 AIC7850 on-board SCSI controllers. Support for the following controllers is rather weak: Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA 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. 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 SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). 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. FreeBSD 2.2.5 will be accompanied by a contributed driver for the Future Domain 36C20 / Adaptec AHA2920 controller. This is not fully supported (yet), but basically functional. Look into the /xperimnt section of the CD-ROM. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including Disks, tape drives (including DAT and 8mm Exabyte) 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, driver is rather stale) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface. 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress (not recommended due to driver instability) Intel EtherExpress Pro/10 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), 3C590/592/595/900/905 PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 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? 2.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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Various Frame grabbers based on Brooktree Bt848 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Floppy tape drives (some rather old models only, driver rather stale) FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 2.2.5-RELEASE and 3.0-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 from: ftp://ftp.cdrom.com/cdrom/catalog. Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 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 preferred method to submit bug reports from a machine with Internet mail connectivity is to use the send-pr command or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or suggestions, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All 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! 5. Acknowledgements ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Additional FreeBSD helpers and beta testers: Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis 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. Everyone at Montana State University for their initial support. And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.6R/announce.adoc b/website/content/en/releases/2.2.6R/announce.adoc index e0e99ee96b..b62333b7f7 100644 --- a/website/content/en/releases/2.2.6R/announce.adoc +++ b/website/content/en/releases/2.2.6R/announce.adoc @@ -1,57 +1,57 @@ --- title: "FreeBSD 2.2.6 Announcement" sidenav: download ---- +--- = FreeBSD 2.2.6 Announcement *Date:* Wed Mar 25 04:24:34 PST 1998 + *From:* "Jordan K. Hubbard" + *Subject:* 2.2.6 RELEASE now available from ftp.freebsd.org (and some mirrors) As always, it's my great pleasure to announce the release of FreeBSD 2.2.6, our latest release on the 2.2-stable branch and the result of over 4 months of work since 2.2.5 was released. See the link:../notes/[release notes] for a list of significant changes since the previous release. FreeBSD 2.2.6-RELEASE is available on ftp://ftp.freebsd.org/pub/FreeBSD[ftp.freebsd.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.cdrom.com/[Walnut Creek CDROM], from where it will be shipping shortly as a 4 CD set containing a lot of extra stuff of interest to the programmer and general user alike. The official FTP distribution site for FreeBSD is: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD ____ Or via the WEB page at: ____ http://www.cdrom.com/pub/FreeBSD/[http://www.cdrom.com/pub/FreeBSD] ____ And on CD-ROM from Walnut Creek CDROM: ____ Walnut Creek CDROM + 4041 Pike Lane, #F + Concord CA, 94520 USA + Phone: +1 925 674-0783 + Fax: +1 925 674-0821 + Tech Support: +1 925 603-1234 + Email: info@cdrom.com + WWW: http://www.cdrom.com/ ____ Additionally, FreeBSD is available via anonymous FTP from https://www.FreeBSD.org/handbook/mirrors.html[mirror sites] in Argentina, Australia, Brazil, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Ireland, Israel, Japan, Korea, the Netherlands, Poland, Portugal, Russia, South Africa, Sweden, Taiwan, Thailand and the UK (among other countries :). Please check your regional mirrors first by going to: ____ ftp://ftp..freebsd.org/pub/FreeBSD ____ The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also 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:: ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt link:../../[Release Home] diff --git a/website/content/en/releases/2.2.6R/errata.adoc b/website/content/en/releases/2.2.6R/errata.adoc index aadb498217..45e4eabfe8 100644 --- a/website/content/en/releases/2.2.6R/errata.adoc +++ b/website/content/en/releases/2.2.6R/errata.adoc @@ -1,125 +1,125 @@ --- title: "FreeBSD 2.2.6 Errata Notes" sidenav: download ---- +--- = FreeBSD 2.2.6 Errata Notes .... The file ERRATA.TXT contains post-release ERRATA for 2.2.6 and should always be considered the definitive place to look *first* before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For 2.2.6 security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest information. ---- Security Advisories: Current active security advisories for 2.2.6: 4 See ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-98:0[2-5].* for full information. ---- System Update Information: o Root mountpoint change which affects those upgrading via "make world" or a FreeBSD 2.2.6 upgrade. Fix: 2.2.6 introduces a change in the naming of the device from which the root filesystem is mounted. This change affects all systems, however user intervention is only required for systems undergoing an upgrade installation. Previously, the root filesystem was always mounted from the compatibility slice, while other partitions on the same disk were mounted from their true slice. This might, for example, have resulted in an /etc/fstab file like: # Device Mountpoint FStype Options Dump Pass# /dev/wd0s2b none swap sw 0 0 /dev/wd0a / ufs rw 1 1 /dev/wd0s2f /local0 ufs rw 1 1 /dev/wd0s2e /usr ufs rw 1 1 For FreeBSD 2.2.6 and later, this format changes so that the device for '/' is consistent with others, ie. # Device Mountpoint FStype Options Dump Pass# /dev/wd0s2b none swap sw 0 0 /dev/wd0s2a / ufs rw 1 1 /dev/wd0s2f /local0 ufs rw 1 1 /dev/wd0s2e /usr ufs rw 1 1 If /etc/fstab is not updated manually in this case, the system will issue a warning message whenever / is mounted (normally at startup) indicating the change that must be made. In addition, trouble may be experienced if the root filesystem is not correctly unmounted, whereby the root filesystem will not be marked clean at the next reboot. This change should be made as soon as the upgraded system has been successfully rebooted. o The ppp program fails to work, citing a missing shared library called "libdes.so.3.0". Fix: There are three possible fixes: 1. The easiest fix is to simply install the des distribution with /stand/sysinstall, remembering to pick a site that will allow you to export it if you're outside the United States and Canada (ftp.FreeBSD.org and ftp.internat.FreeBSD.org both fall into this category). 2. Purely as a work-around, and what you may need to do if ppp also constitutes your only way of getting to the net, is to simply do the following (as root): cp /usr/lib/libcrypt.so.2.0 /usr/lib/libdes.so.3.0 ldconfig -m /usr/lib 3. Another fix, and one which doesn't involve having to fetch the DES bits, is to install the ppp sources in /usr/src/usr.sbin/ppp and rebuild them. The sources are "smart" enough to know that the DES library isn't on the system and won't create a binary which depends on it. NOTE: If you choose the 2nd or 3rd fixes, you also will not be able to use MSCHAP (Microsoft Win*) style authentication. o The xterm program in XFree86 3.3.2 doesn't remove utmp entries on exit (e.g. xterm sessions show up in "who" or "w" even after they've exited). Fix: Fetch the updated xterm binary at: ftp://ftp.FreeBSD.org/pub/FreeBSD/updates/2.2.6-RELEASE/xterm Or get the *latest* ports collection on your machine (see http://www.FreeBSD.org/ports) and use the port in x11/XFree86 to build an xterm with this patch already applied (as of 98/04/06). The patch itself can also be obtained from the port itself: ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/ports/x11/XFree86/patches/patch-ag o The older Matsushita (Panasonic), Sony CDU-31 and Mitsumi (non-IDE) CDROM drives no longer permit CDROM installs. Fix: Fetch an updated boot floppy from the updates/ directory, e.g.: ftp://ftp.FreeBSD.org/pub/FreeBSD/updates/2.2.6-RELEASE/boot.flp And use it to install 2.2.6 instead. This problem is fixed in 2.2-stable and will not be a problem with the next FreeBSD release. .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.6R/notes.adoc b/website/content/en/releases/2.2.6R/notes.adoc index f4cc97a4e9..0bbed83ed7 100644 --- a/website/content/en/releases/2.2.6R/notes.adoc +++ b/website/content/en/releases/2.2.6R/notes.adoc @@ -1,88 +1,88 @@ --- title: "FreeBSD 2.2.6 Release Notes" sidenav: download ---- +--- = FreeBSD 2.2.6 Release Notes .... ================================================================ RELEASE NOTES FreeBSD 2.2.6-RELEASE VERSION ================================================================ What's new since 2.2.5 ---------------------- Kernel features: o Added support for SMC EtherPower II 10/100 Fast Ethernet card (aka SMC9432TX based on SMC83c170 EPIC chip). o Added support for DPT SCSI RAID controllers (see LINT). o New Plug and Play (PnP) support that allows you to (re)configure PnP devices. Also support modems being detected by the PnP part and automatically attached. o Alternate sound driver (/sys/i386/isa/snd) from Luigi Rizzo; it does not yet support MIDI (for that, use the old sound driver) but it does have much better support for PNP sound cards and is much easier to configure (only one device). See /sys/i386/conf/LINT for more info. o Better Linux emulation (applications like RealVideo 5.0 for Linux now work). o Added support for ATAPI floppy drives (LS-120) o The psm, mse and sysmouse drivers are improved to provide better mouse support. moused(8) has been modified to support various mice with a ``wheel''. It also automatically recognizes mice which support the PnP COM device standard so that the user is no longer required to supply a mouse protocol type on the command line. Userland features: o popen() library call now uses and offers bidirectional pipes. o Added support for parallel makes in /usr/src (-j n works now with world target, particularly useful with SMP machines). o tcpdump(1) utility enhanced o Support for ldconfig -R (remove) added. o Various bugfixes and enhancements to pthread support. o calendar(1) program brought more up-to-date. o KerberosIV updated to latest version. o Various curses(3) bugs fixed. o Various IEEE754 conformance changes to libm(3). o Much cleanup and general improvements to the documentation. o Various improvements to the NIS code. Security issues: o Fixed /dev/io and mmap security holes. o Better protection against "LAND attacks" o Various buffer overruns detected and extra checks added. o Pentium "F00F bug" is detected and a work-around installed to prevent hangs. o srandomdev() support merged from -current and utilities updated to use it. .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.7R/announce.adoc b/website/content/en/releases/2.2.7R/announce.adoc index 85e8733829..b6af8fa751 100644 --- a/website/content/en/releases/2.2.7R/announce.adoc +++ b/website/content/en/releases/2.2.7R/announce.adoc @@ -1,67 +1,67 @@ --- title: "FreeBSD 2.2.7 Announcement" sidenav: download ---- +--- = FreeBSD 2.2.7 Announcement *Date:* Wed, 22 Jul 1998 08:36:25 -0700 + *From:* "Jordan K. Hubbard" + **Subject:**FreeBSD 2.2.7 is now released! It is my usual pleasure to announce the release of FreeBSD 2.2.7, our latest release along the 2.2-stable branch. Those folks who are still running 2.1.x and wish to upgrade to 2.2 technology are encouraged to do so as 2.2.7 has reached a more than equivalent level of stability in all of our tests. A number of problems with 2.2.6 have also been fixed (see the link:notes.html[release notes] for more information). FreeBSD 2.2.7-RELEASE is available on ftp://ftp.FreeBSD.org/pub/FreeBSD[ftp.FreeBSD.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.cdrom.com/[Walnut Creek CDROM], from where it will be shipping shortly as a 4 CD set containing a lot of extra stuff of interest to programmers and general users alike. *IMPORTANT NOTE*: All of the profits from the sales of this CD set go to support the FreeBSD Project! Like many businesses in the field of high-tech, Walnut Creek CDROM has realized that in order to make any product for an emerging market grow, you have to make a significant investment in such growth, even if it means abandoning short-term profits. Walnut Creek CDROM is the only CDROM vendor who currently does anything like this and it's certainly my hope that you will help support the project by buying (or getting someone else to buy :) one of their CDs. Thanks! The official FTP distribution site for FreeBSD is: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD ____ Or via the WEB page at: ____ http://www.cdrom.com/pub/FreeBSD/[http://www.cdrom.com/pub/FreeBSD] ____ And on CD-ROM from Walnut Creek CDROM: ____ Walnut Creek CDROM + 4041 Pike Lane, #F + Concord CA, 94520 USA + Phone: +1 925 674-0783 + Fax: +1 925 674-0821 + Tech Support: +1 925 603-1234 + Email: info@cdrom.com + WWW: http://www.cdrom.com/ ____ If you are in Japan, please refer to http://www.pht.co.jp/[Pacific HiTech] for information on ordering a localized (or the english) version of the 2.2.7 product. Pacific HiTech is now an affiliate of Walnut Creek CDROM for Japanese sales of FreeBSD. Additionally, FreeBSD is available via anonymous FTP from https://www.FreeBSD.org/handbook/mirrors.html[mirror sites] in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: ____ ftp://ftp..FreeBSD.org/pub/FreeBSD ____ Any additional mirror sites will be labeled ftp2, ftp3 and so on. The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also 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:: ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD[ftp://ftp.internat.F reeBSD.ORG/pub/FreeBSD] + ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD[ftp://ftp2.internat.FreeBS D.ORG/pub/FreeBSD] Brazil:: ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD[ftp://ftp.br.FreeBSD.ORG/p ub/FreeBSD] Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt[ftp://nic.funet.f i/pub/unix/FreeBSD/eurocrypt] link:../../[Release Home] diff --git a/website/content/en/releases/2.2.7R/errata.adoc b/website/content/en/releases/2.2.7R/errata.adoc index fe97a30ed1..419a45b12c 100644 --- a/website/content/en/releases/2.2.7R/errata.adoc +++ b/website/content/en/releases/2.2.7R/errata.adoc @@ -1,61 +1,61 @@ --- title: "FreeBSD 2.2.7 Errata Notes" sidenav: download ---- +--- = FreeBSD 2.2.7 Errata Notes .... The file ERRATA.TXT contains post-release ERRATA for 2.2.7 and should always be considered the definitive place to look *first* before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For 2.2.7 security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest information. ---- Security Advisories: Current active security advisories for 2.2.7: None ---- System Update Information: o XFree86: The XF86Setup utility sometimes fails with an XIO error (visible on the 2nd VTY) rather than starting properly if you run it during system installation time. This is not a new bug and has been seen in previous releases of FreeBSD, but it seems to happen far more reliably with 2.2.7 now (for some as yet unknown reason). Fix: Should this happen to you, run /usr/X11R6/bin/XF86Setup by hand after the system comes up off the hard disk for the first time. For some reason, when not run off the boot floppy or CD, it works perfectly (making this one somewhat more difficult to debug). o Release notes state that Texas Instruments ThunderLAN PCI NICs are supported in 2.2.7. Fix: This was an embarrassing mis-merge from the 3.0 release notes and, indeed, those cards are only supported in 3.0-current. Please ignore this section of the release notes and any other docs which claim that the ThunderLAN NICs are supported in 2.2.7. o rshd was broken during -Wall cleanup, as noted in PR#7500 Fix: This was fixed in the 2.2-stable branch as of 1998/07/24 04:32:21 in revision 1.9.2.9 of /usr/src/libexec/rshd/rshd.c. Obtain the fixed version via CVSup (see instructions in handbook or simply ``pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz'' and follow the instructions) or get it from FTP at: ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/src/libexec/rshd/rshd.c .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.7R/notes.adoc b/website/content/en/releases/2.2.7R/notes.adoc index 6c82869e5e..158530e924 100644 --- a/website/content/en/releases/2.2.7R/notes.adoc +++ b/website/content/en/releases/2.2.7R/notes.adoc @@ -1,437 +1,437 @@ --- title: "FreeBSD 2.2.7 Release Notes" sidenav: download ---- +--- = FreeBSD 2.2.7 Release Notes .... ================================================================ RELEASE NOTES FreeBSD 2.2.7-RELEASE VERSION ================================================================ 1. What's new since 2.2.6 ------------------------- Kernel features: ---------------- o DPT SCSI RAID controller updated (including support for EISA cards) and is now enabled by default. o MSDOS FAT32 (Win95 long filename) support. o Various bugs in the SCSI changer code fixed. o New support for Crystal Semiconductor CS8920 based ethernet cards. o Dead LFS code removed. o New updated Specialix SI/XIO/SX driver. o dmesg (history buffer) now user-sizeable. See MSGBUF_SIZE option in /sys/i386/conf/LINT. o Various bugfixes for the Adaptec aic7870/aic7880 chipsets. o Identify Pentium II processors properly at startup now. o pcm audio driver updated to support Avance Logic ALS100 card and basically improve audio support all around. o Various fixes to NFS credential checking. o Many updates for the NEC PC98 platform. Userland features: ------------------ o inetd(8) now allows rate-limiting for services. o ppp(8) utility significantly updated. See man page for details. o Many (MANY!) man pages and other docs updated and cleaned up. o libc_r (part of POSIX pthread support) is now part of the system by default and incorporates numerous bug fixes. o ls(1) has grown a number of new flags - man ls for details. o cvs(1) updated to version 1.9.26 o Various parts of /etc updated with selected features from 3.0. o as(1) now understands fildll/fistpll opcodes. o Various improvements to the installation procedure. o Various minor curses(3) positioning errors fixed. o Several bugs in dump(8) and restore(8) fixed. o Various enhancements made to the login class mechanism and default limits raised for workstation users. o ftpd disables Nagle on the control channel for better response. Security issues: ---------------- o XFree86 updated to 3.3.2.3 - an important security release containing changes from The Open Group which close several possible root-exploits from local users. o Crypto repository updated from 3.0 branch. o popper and imap upgraded in ports collection to close some nasty security holes (see Bugtrax). o Various buffer overflows in utilities like rcp(1) and more(1) (just to name a few) have been closed. o Bounds-checking added to numerous "attackable" locations in BIND and much of BIND significantly updated. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 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 AIC7850 on-board SCSI controllers. ** 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. 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 SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). 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 8mm Exabyte) 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) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface Unmaintained drivers, they might or might not work for your hardware: Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. Floppy tape interface (Colorado/Mountain/Insight) (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress (not recommended due to driver instability) Intel EtherExpress Pro/10 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), 3C590/592/595/900/905 PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 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? 2.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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 3.0-SNAP and 2.2.x-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite D Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD 3.0-SNAP CDs are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 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 preferred method to submit bug reports from a machine with Internet mail connectivity is to use the send-pr command or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This will give you more information on joining the various lists, accessing archives, etc. There are a number of mailing lists targeted at special interest groups not mentioned here, so send mail to majordomo and ask about them! 5. Acknowledgements ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html Everyone at Montana State University for their initial support. And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.8R/errata.adoc b/website/content/en/releases/2.2.8R/errata.adoc index a36fc540d6..76d001094b 100644 --- a/website/content/en/releases/2.2.8R/errata.adoc +++ b/website/content/en/releases/2.2.8R/errata.adoc @@ -1,60 +1,60 @@ --- title: "FreeBSD 2.2.8 Errata Notes" sidenav: download ---- +--- = FreeBSD 2.2.8 Errata Notes .... The file ERRATA.TXT contains post-release ERRATA for 2.2.8 and should always be considered the definitive place to look *first* before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For 2.2.8 security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest information. ---- Security Advisories: Current active security advisories for 2.2.8: None ---- System Update Information: o /usr/sbin/sysctl is an invalid link and whereis(1) doesn't work. Fix: sysctl(8) has actually moved to /sbin/sysctl. Simply create a symbolic link for compatability purposes as follows: ln -sf /sbin/sysctl /usr/sbin or syncronize your sources with 2.2-stable and rebuild/install from /usr/src/usr.bin/whereis/ and just rm /usr/sbin/sysctl o /usr/share/doc/FAQ is in spanish. Fix: This was a build failure which affected only the FAQ and has since been fixed. If you are already cvsup/CTM'ing the doc-all tag then you can simply remake and install the FAQ from sources, otherwise grab ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/FAQ.tar.gz and unpack as follows: tar --unlink -xvzf FAQ.tar.gz -C /usr/share/doc to get an english FAQ. o getpwnam(3) semantics are incorrect in some cases. Fix: If passed a string longer than the maximum allowed for a user name, getpwnam will incorrectly return an entry for a user that matches the initial characters in the string up to the maximum length allowed for a user name. To correct this behaviour, libc needs to be patched and recompiled. The appropriate patch can be obtained from: http://cvsweb.FreeBSD.org/src/lib/libc/gen/getpwent.c.diff?r1="1".35.2.2&r2="1".35.2.3 .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2.8R/notes.adoc b/website/content/en/releases/2.2.8R/notes.adoc index feafbb824b..ebfa83995c 100644 --- a/website/content/en/releases/2.2.8R/notes.adoc +++ b/website/content/en/releases/2.2.8R/notes.adoc @@ -1,392 +1,392 @@ --- title: "FreeBSD 2.2.8 Release Notes" sidenav: download ---- +--- = FreeBSD 2.2.8 Release Notes .... ================================================================ RELEASE NOTES FreeBSD 2.2.8-RELEASE VERSION ================================================================ 1. What's new since 2.2.7 ------------------------- Kernel features: ---------------- o Add support for >8G IDE drives. o Add support for 3Com 3c905B ethernet adapters o Add support for PCI ThunderLAN-based ethernet adapters (Compaq/Olicom) o Significantly improve Linux emulator again. Things like QuakeII should just run out-of-the-box now (given the rest of their requirements). o Major changes from -current's pthread implementation merged: This includes file locking based on FILE *, signal fixes, read/write-locks, better POSIX compliance and better performance. o Add a new flexible bandwidth limiter/delay emulator called dummynet. See dummynet(4). o Add support for bridging on multiple interfaces (10 and 100 Mbit/s). See bridge(4). o NFS client accelerator added. See 'nfs_access_cache' in rc.conf(5). Userland features: ------------------ o /bin/sh signal and trap handling reworked. Among other things, this makes tty-mode emacs work when called from system(2), i.e. by a mail agent. o ppp(8) merged from 3.0, adding features like multilink and VPN support as well as fixing a number of known bugs. Security issues: ---------------- o All open CERT/Bugtraq advisories reported since 2.2.7's release have been dealt with. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 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 AIC7850 on-board SCSI controllers. ** 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. 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 SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). 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 8mm Exabyte) 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) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI CDROM interface (acd) ATAPI CD-R interface (alternative to 'wcd') Unmaintained drivers, they might or might not work for your hardware: Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. Floppy tape interface (Colorado/Mountain/Insight) (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress (not recommended due to driver instability) Intel EtherExpress Pro/10 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), 3C590/592/595/900/905/905B PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL Toshiba ethernet cards PCMCIA ethernet cards from IBM and National Semiconductor are also supported. No token ring cards are supported at this time. 2.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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. 3.2. CDROM ---------- FreeBSD 3.0-SNAP and 2.2.x-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite D Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 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 preferred method to submit bug reports from a machine with Internet mail connectivity is to use the send-pr command or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This will give you more information on joining the various lists, accessing archives, etc. There are a number of mailing lists targeted at special interest groups not mentioned here, so send mail to majordomo and ask about them! 5. Acknowledgements ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html Everyone at Montana State University for their initial support. And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/2.2R/announce.adoc b/website/content/en/releases/2.2R/announce.adoc index fe320a0526..905cc83d34 100644 --- a/website/content/en/releases/2.2R/announce.adoc +++ b/website/content/en/releases/2.2R/announce.adoc @@ -1,14 +1,14 @@ --- title: "FreeBSD 2.2 Announcement" sidenav: download ---- +--- = FreeBSD 2.2 Announcement It is our great pleasure to announce the release of FreeBSD 2.2, the long-awaited first release of our 2.2 branch technology following lengthy ALPHA, BETA and GAMMA testing cycles. FreeBSD 2.2-RELEASE is now available on ftp://ftp.FreeBSD.org/pub/FreeBSD[ftp.FreeBSD.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.cdrom.com/[Walnut Creek CDROM], from where it will be shipping shortly. FreeBSD 2.2 represents a rather large leap in functionality from the 2.1.x releases, everyone being is strongly encouraged to read the https://www.FreeBSD.org/releases/2.2R/notes.html[release notes] for a list of new features. link:../../[Release Home] diff --git a/website/content/en/releases/2.2R/install-media.adoc b/website/content/en/releases/2.2R/install-media.adoc index cbccc50217..44c096f9ef 100644 --- a/website/content/en/releases/2.2R/install-media.adoc +++ b/website/content/en/releases/2.2R/install-media.adoc @@ -1,18 +1,18 @@ --- title: "FreeBSD 2.2 Change Announcement" sidenav: download ---- +--- = FreeBSD 2.2 Change Announcement _From mailto:jkh@FreeBSD.org[jkh]:_ 2.2-RELEASE will not support installation of machines with 4MB of memory or 1.2MB floppy drives - that is to say, only > 5MB memory & 1.44MB floppy drive systems are supported. In truth, 8MB of memory is the recommended minimum. Those who have such limitations on their configuration and can't upgrade, for whatever reason, are therefore urged to stay with 2.1.6-RELEASE, which has provisions for both types of installation and will probably be more than functional for as long as one might conceivably wish to continue operating such a system. We regret any inconvenience this may cause some of our users, but we have also been pressed for space on the installation media for some time now, and this was more or less inevitable. We've talked about killing the 4MB installation and 1.2MB floppies for over a year, and it's only through some of the most arcane trickery (you don't want to know) that we've managed to keep it all on a single floppy at all. Now that we've made the leap to 1.44MB/>6MB class machines, we've at least bought ourselves some room for future enhancements while still remaining on one floppy. Note that you can still build kernels which will run quite comfortably in a 4MB system, you just can't *install* with only 4MB in the machine. If you're trying to build a custom box with 4MB and a tiny configuration, for example, you might simply build its disk on a different machine set up specifically for that purpose. link:../../[Release Home] diff --git a/website/content/en/releases/2.2R/notes.adoc b/website/content/en/releases/2.2R/notes.adoc index 2c4e30834a..311cc1d870 100644 --- a/website/content/en/releases/2.2R/notes.adoc +++ b/website/content/en/releases/2.2R/notes.adoc @@ -1,510 +1,510 @@ --- title: "FreeBSD 2.2 Release Notes" sidenav: download ---- +--- = FreeBSD 2.2 Release Notes .... RELEASE NOTES FreeBSD 2.2-RELEASE 1. What's new since 2.1.7 ------------------------- Lots of installation bugs fixed, more pc98 changes syncronized, geeze, what else? gdb 4.16 has been merged from -current, most of the third-party source now lives under /usr/src/contrib. Updated support for the DEC DEFPA/DEFEA FDDI hardware. The old ``HAVE_FPU'' Makefile option is now finally gone, the selection between the math library using the floating point emulator, and the version using the co-processor is now fully automatic. This will speed up floating-point using programs on sites that didn't like to recompile their `libm' previously. Javier Martin Rueda's `ex' driver has been merged, bringing support for the Intel EtherExpress Pro/10 network cards. The `de' driver now recognizes cards using the DE21140A chip, like the popular SMC9332BDT (10/100 Mbit/s) one. There's now a workaround for the brokeness of the frequently used CMD640 PCI IDE chip in the sources, albeit still disabled by default in 2.2. The number of EISA slots to probe is now a fully supported option, including the ability to save the value from a UserConfig session with dset(8). This helps owners of HP NetServer LC machines to install the system on their hardware. Support for the SDL RISCom N2pci sync serial card. Support for Cyclades Cyclom-Y (multi-port async serial) PCI adaptors as well as multiple controllers and the 32-Y (if you are currently using the Cyclades serial adapter, you should re-make your /dev entries and remove the old ones). Updated support for ethernet adaptors which use the DEC DC21X4X chipset. Update to gcc 2.7.2.1 & add support for weak symbols. Many things moved/brought into /usr/src/contrib, updating and cleaning up the source tree accordingly. Support for compiled-in shared library ld paths. Update sgmlfmt to `instant'. Support for SNMP-style interface MIBs, including full RFC 1650-compliant MIBs for the `de' (DEC 21x4x) and `ed' (SMC/WD/Novell) drivers. /stand/sysinstall moved even more towards becoming a more general system management tool. The syscons and psm drivers now have a new underlying shared keyboard driver, eliminating many of the previously existing problems with their mutual interaction. Syscons now supports cut & paste in textmode using the moused(8) utility. 2.2 is the first release that includes full CD-R support for the Plasmon RF41xx, HP4020i, HP6020i, and Philips CDD2000 drives. The driver is still under development (in particular to extend its usability for other devices), but it has been proved to be stable by now. Support for NFSv3 clients and servers went into the 2.2 sources shortly after branching off the 2.0.5/2.1.X tree. There are also other options available with NFS, like the ability to turn an NFSv2 server into asynchronous write mode (which is in violation of the specs, but has precedents e.g. in SGI Irix). Poul-Henning Kamp's phkmalloc replaced the old and blatant BSD malloc implementation. This usually saves a lot of virtual memory for the clients, and offers some neat features like aborting the program on detected malloc abuses, or filling the malloced and/or freed area with junk in order to detect semantical problems in programs that use malloc. The `netatalk' implementation of AppleTalk has been integrated into the sources, most of the integration work courtesy Wistle Communic- ations Corp. The mount option `async' allows asynchronous metadata updates on UFS filesystems, something that is the default e.g. on Linux' ext2fs. This speeds up many i-node intensive filesystem operations (like rm -r) at the cost of an increased risk in case of a system crash. The installation itself makes use of this feature, and could be drastically accelerated by this. (A bindist-only installation from a SCSI CD-ROM can now complete in less than 5 minutes on a fast machine!) The ATAPI CD-ROM support is now reported to work for quite an impressive number of drives. In other words, all the drives that basically adhere to the ATAPI standard are likely to work. There are many new drivers available in the kernel, too many to keep them in mind. Tekram supplied a driver for their DC390 and DC390T controllers. These controllers are based on the AMD 53c974, and the driver is also able to handle other SCSI controllers based on that chip. Of course, with Tekram being generous enough to support the FreeBSD project with their driver, we'd like to encourage you to buy their product. The `ed' and `lnc' drivers now support auto-config- uration for the respective PCI ethernet cards, including many NE2000 clones and the AMD PCnet chips. The SDL RISCom N2 support is new, as well as the PCI version of the Cyclades driver. The Linux emulation is now fully functional, including ELF support. To make its use easier, there are even ports for the required shared libraries, and for the Slackware development environment. Along the same lines, the SysV COFF emulation (aka. SCO emulation) is reported to be working well now. FreeBSD also supports native ELF binaries, although it hasn't been decided yet whether, when, and how we might use this as the default binary format some day. A `brandelf' utility has been added to allow `branding' of non-shared linked ELF binaries where the kernel cannot guess which image activator (FreeBSD, Linux, maybe SysV some day) should be used. This works around one major flaw in the ELF object format, the missing field to mark the ABI it belongs to. Support for APM BIOSes is now in a much better shape. The manual section 9 has been started, describing `official' kernel programming interfaces. We are still seeking volunteers to document interfaces here! The kernel configuration option handling has been largely moved away from the old -D Makefile kludges, towards a system of "opt_foo.h" kernel include files, allowing Makefile dependencies to work again. We expect the old hack that blows the entire compile directory away on each run of config(8) to go away anytime soon. Unless you're changing weird options, you might now consider using the -n option to config(8), or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for you. See also the comments in the handbook about how it works. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec 1535 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 AIC7850 on-board 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. 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 SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). 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 8mm Exabyte) 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!). 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress (not recommended due to driver instability) Intel EtherExpress Pro/10 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), 3C590/592/595/900/905 PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 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? 2.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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber HP4020i, Philips CDD2000 and PLASMON WORM (CDR) drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your 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! 3.2. CDROM ---------- FreeBSD 2.1.7-RELEASE and 2.2-RELEASE 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 from: ftp://ftp.cdrom.com/cdrom/catalog. Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 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 preferred method to submit bug reports from a machine with Internet mail connectivity is to use the send-pr command or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or suggestions, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All 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! 5. Acknowledgements ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Additional FreeBSD helpers and beta testers: Coranth Gryphon Dave Rivers Kaleb S. Keithley Terry Lambert David Dawes Don Lewis 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 Project .... link:../../[Release Home] diff --git a/website/content/en/releases/3.0R/errata.adoc b/website/content/en/releases/3.0R/errata.adoc index def9f8a0f3..f5270c1ae5 100644 --- a/website/content/en/releases/3.0R/errata.adoc +++ b/website/content/en/releases/3.0R/errata.adoc @@ -1,58 +1,58 @@ --- title: "FreeBSD 3.0 Errata Notes" sidenav: download ---- +--- = FreeBSD 3.0 Errata Notes .... The file ERRATA.TXT contains post-release ERRATA for 3.0 and should always be considered the definitive place to look *first* before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For 3.0 security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest information. ---- Security Advisories: Current active security advisories for 3.0: 1 o SA-98:08: IP fragmentation denial of service Fix: Update to 3.0-current or apply patch supplied with advisory 98:08 in: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-98:08.fragment.asc ---- System Update Information: o The GPL_MATH_EMULATE kernel option causes a fatal trap during system startup. Fix: Replace the GPL_MATH_EMULATE option with the default math emulation option MATH_EMULATE. This will only affect users who have modified their kernel configuration file. The problem is corrected in revision 1.16 of the file /usr/src/sys/gnu/i386/fpemul/fpu_entry.c. o DOS partition installs fail to find the installation bits. Fix: Rename C:\FREEBSD to C:\3.0-RELEASE and retry the installation. The naming syntax was changed to make DOS more like the other types of installation media but the docs on DOS installation were not updated properly to reflect this. The current sysinstall now accepts both locations, as it should have to begin with. .... link:../../[Release Home] diff --git a/website/content/en/releases/3.0R/notes.adoc b/website/content/en/releases/3.0R/notes.adoc index b24faae37f..2963866fbe 100644 --- a/website/content/en/releases/3.0R/notes.adoc +++ b/website/content/en/releases/3.0R/notes.adoc @@ -1,844 +1,844 @@ --- title: "FreeBSD 3.0 Release Notes" sidenav: download ---- +--- = FreeBSD 3.0 Release Notes .... RELEASE NOTES FreeBSD Release 3.0-RELEASE This is our first release of 3.0-CURRENT and is aimed primarily at early adopters and developers. Some parts of the documentation may not be updated yet and should be reported if and when seen. Naturally, any installation failures or crashes should also be reported ASAP by sending mail to freebsd-bugs@FreeBSD.org or using the send-pr command (those preferring a WEB based interface can also see this page). For information about FreeBSD and the layout of the 3.0-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. This is also hardly the last release on the 3.0-current (HEAD) branch and daily snapshot releases will continue as normal following this release. Please install them from: ftp://current.FreeBSD.org/pub/FreeBSD If you wish to get the latest post-3.0-RELEASE technology. Table of contents: ------------------ 1. What's new since 2.2.X-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 ATM 2.4 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgements 1. What's new since 2.2.X-RELEASE --------------------------------- All changes described here are unique to the 3.0 branch unless specifically marked as [MERGED] features. 1.1. KERNEL CHANGES ------------------- o The 2.2.x SCSI subsystem has been almost entirely replaced with a new "CAM" (Common Access Method) SCSI system which offers improved performance, better error recovery and support for more SCSI controllers. o The Host ATM Research Platform ("HARP") software by Network Computing Services, Inc. has been integrated into the system. See /usr/src/share/examples/atm for more info. o The SMP (Symmetric MultiProcessing) branch has been merged. The kernel is mostly non-reentrant as yet, but work is under way. o The code from 4.4BSD-Lite2 has been (finally) merged. o Secure RPC is now supported (and usable with NFS et al). o Sun's WEBNFS standard is now supported. o The MSDOS filesystem code now handles VFAT and FAT32 partitions. [MERGED: Also in 2.2.7 and later releases on 2.2-STABLE branch] o ATAPI/IDE CD burner support (BETA). o ATAPI/IDE tape drive support (BETA). o Support for using VESA video modes. It is now possible to select and use the modes provided by the BIOS on modern videocards. This enables fx. 132x60 sized consoles and highres graphics in a generic manner on hardware that supports it. There is also support for running the console in rastermode, which allows XFree86 to run a simple 16color server in 800x600 on otherwise unsupported video hardware. o Support for AdvanSys SCSI controllers o Support for QLogic SCSI and Fibre Channel controllers. o Support for Adaptec 7890, 7891, 7895, 7896 and 7897 based controllers (new 2940/2950/3940/3950 et al). o The ed0 (wd8xxxx, 3c503, NE2000, HP Lan+) Ethernet device's default IRQ has changed from IRQ 5 to IRQ 10. The ed1 Ethernet device has been removed. Use the Userconfig utility to change ed0's values to match your network card's settings. [MERGED: Both changes are in 2.2.6 and later releases on 2.2-STABLE branch] o The code responsible for maintaining time of day has been rewritten. New features are: true support for nanoseconds in both kernel and userland, continuous rather than stepwise adjustment by NTPD and support for synchronizing to high precision external time signals. o Support for the PPS API described in draft-mogul-pps-api-02.txt for TTL rising edge inputs via the parallel printer port has been added to the printer driver. o Use the new if_multiaddrs list for multicast addresses rather than the previous hackery involving struct in_ifaddr and arpcom. Get rid of the abominable multi_kludge. o The new if_media selection method for ethernet drivers has been brought in, obtained from Jason Thorpe's implementation for NetBSD. [MERGED: Also in 2.2.5 and later releases on 2.2-STABLE branch] o Multi-session ISO-9660 CD-ROMs are now fully supported. By default, the last session will be mounted (including for root mounts). For non-root mounts, mount_cd9660(8) can take an argument to mount a particular session instead of the default one. o The UPAGES are gone from the per-process address space which allows complete address space and page table sharing by reference count. o Newly forked child processes return directly to user mode rather than return up through the fork() syscall tree. This eliminates the kernel stack copy at fork time and simplifies certain other internal operations. It is also needed to support the removal of the UPAGES. (The idea for this originally came from NetBSD, but we did it for different reasons.) o vfork() is now fully functional by taking advantage of the new sharing semantics and a significant speedup has been measured. This can be disabled via the kern.fast_vfork sysctl variable in case of problems. Statically linked binaries from older releases and other BSD platforms are a problem since there was a bug in the 4.4BSD (net2, Lite and Lite2) popen() implementation. rfork() also has access to these facilities, intended for supporting kernel assisted threads. o With the contribution of Berkeley Software Design, Inc., Jonathan Lemmon, Mike Smith, Sean Eric Fagan, and John Dyson, VM86 support has been added to the kernel, and BSD/OS's contributed doscmd has been ported. o The SA_NOCLDWAIT flags has been implemented, featuring the System V option where a process can express its wish to never get zombies or SIGCHLD for dead children. o An implementation of poll(2) is in place, the core of which is derived from the NetBSD implementation. Both the select() and poll() syscalls use the poll device, file and vnode ops routines. o An implementation of issetugid(2) that is similar to the OpenBSD call of the same name. We set the flag in more cases than OpenBSD - our implementation is slightly more paranoid. o Async IO is implemented (under non-SMP at this stage) with additional support for kernel assisted threads. o Some other misc syscalls for compatability with other systems: getsid(2), setpgid(2), nanosleep(2). o A new syscall signanosleep(2) which is like nanosleep(2), but a specific signal mask is used to determine which signals will wake the sleep. In a nutshell this is 'wait for a given set of signals for up to a certain amount of time'. o sleep(3) and usleep(3) are now implemented in terms of signanosleep(2) and now have correct SIGALRM interaction semantics and sleep(3) correctly returns the time remaining. o An in-kernel linker is implemented and intended to replace the lkm system and the bogosity that goes with it. o All supported network protocols have been updated to avoid the ``big switch'' pr_usrreq(), and to pass a process pointer down to each user request that might need process credentials or want to sleep, replacing the previous hodgepodge of inspecting curproc (which only occasionally did the right thing) and the SS_PRIV socket state flag. The latter has now been eliminated, along with the SO_PRIVSTATE socket option which cleared it. Protocols are now also given the opportunity to override the generic send, receive, and poll routines, which will make it possible for a more efficient, protocol-specific implementation of these entry points in later releases. Finally, many parts of the network code have been modified to cease storing socket addresses and other metainformation in mbufs, in preparation for the eventual elimination thereof. The mechanism by which socket addresses are now returned is still highly subject to change as we experiment to discover the most efficient method. o Responses to multicast ICMP ECHO REQUEST (``ping'') and ADDRESS MASK REQUEST packets can now be disabled via sysctl. The netstat program will print out statistics on how many times this happens. o A subtle and seldom encountered bug in ffs has been fixed. o The VFS name cache has been reworked to be more accountable and efficient. o The generic part of VOP_LOOKUP() has been put it in system-wide function which filesystems can rely on for the canonical stuff. o Vnode freelist handling has been hauled over. Vnodes are only on the freelist if nobody cares about them. o The kernel provides assistance to getcwd() from data stored in the name cache if possible. o An interrupt driven configuration hook mechanism has been implemented. This allows drivers to postpone part of their configuration until after interrupts are fully enabled. This speeds booting because busy-waiting is avoided for things like sub device probing (eg: SCSI bus probes). o The timeout(9) system in the kernel has been overhauled. This gives O(1) insertion and removal of callouts and an O(hash chain length) amount of work to be performed in softclock. The original paper is at: http://www.cs.berkeley.edu/~amc/research/timer/ o Changes in driver buffer queuing to deal with ordered transactions. This is intended for sequencing data and metadata writes in the filesystem code once fully supported. o EISA Shared interrupts are now supported, working with the framework originally for supporting PCI shared interrupts. o Support for the Comtrol Rocketport card. o IPFW's packet and byte counters have been expanded from 32 to 64 bits, a `FWD' operation has been added to ipfw to support transparent proxying and the divert operation has changed slightly - see the man pages for natd(8) and ipfw(8) for more information. o New Plug and Play (PnP) support that allows you to (re)configure PnP devices. Also support modems being detected by the PnP part and automatically attached. [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch] o Import of new sound code from Luigi Rizzo. This code is still being developed, but has support for a number of different cards. [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch] o The psm, mse and sysmouse drivers are improved to provide better mouse support. In particular, the psm driver now supports various ``wheeled'' mice. [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch] o Added support for SMC EtherPower II 10/100 Fast Ethernet card (aka SMC9432TX based on SMC83c170 EPIC chip). [MERGED: Also in 2.2.7 and later releases on 2.2-STABLE branch] o Added support for ATAPI floppy drives (LS-120). [MERGED: Also in 2.2.7 and later releases on 2.2-STABLE branch] o Added support for IBM Etherjet and other Crystal Semiconductor CS89x0-based NICs. [MERGED: Also in 2.2.7 and later releases on 2.2-STABLE branch] o Added support for Texas Instruments TNET100 'ThunderLAN' PCI NIC. [MERGED: Also in 2.2.8 and later releases on 2.2-STABLE branch] o Added full bus master DMA support for 3c900 and 3c905 adapters and added support for the 3c905B. [MERGED: Also in 2.2.8 and later releases on 2.2-STABLE branch] 1.2. SECURITY FIXES ------------------- [MERGED: all changes soon after specified date in 2.2-STABLE branch] 97/7/29 Lots of lpr/lpd security fixes merged from OpenBSD. 97/8/22 buffer overflows in tip corrected (benign since tip isn't set[ug]id) 97/8/26 buffer overflow in glob fixed, no know exploits 97/8/27 vacation security problem with sendmail corrected (SNI) 97/8/29 inetd sleeps less when children exit, making DoS attacks much harder. 97/8/29 fts now race-proof and find -execdir added (-current only) 97/8/31 games setuid -> setgid. Makes any games exploits benign (only score files vulnerable). Please report any problems to eivind@FreeBSD.org (score-file ownership problems are known) 97/12/3 Add Intel's suggested fix for the F00F bug. If you don't have a Pentium, the NO_F00F_HACK kernel option will disable it. 98/1/20 More robust protection against LAND attacks now incorporated. The suidperl vulnerability mentioned in the CERT advisory CA-97.17 is also believed to be fixed. KerberosIV is now merged. 1.3. USERLAND CHANGES --------------------- The default binary type (and compiler toolchain) has been switched from a.out to ELF. This gives us access to much newer compiler technology (much of which didn't support a.out), allows for smaller executables and provides much better support for languages like C++, among many other advantages. Older a.out libraries and binaries will, of course, continue to work and provisions have been made for having both varieties installed if and as necessary for transitional purposes. Perl4 has now been replaced by Perl5 as a standard part of the system. The default username length has increased to 16 characters. Caution: Old utmp/wtmp files will NOT work with this change since the data records will be of the old size. For a conversion utility to aid with this, see /usr/src/tools/3.0-upgrade. /etc/sysconfig now replaced by more compact /etc/rc.conf file [MERGED: Also in 2.2.1 and later releases on 2.2-STABLE branch] fdisk(8) now numbers disk slices from 1 to 4 rather than from 0 to 3. This brings it in line with the numbers used in the device names in /dev. The Amd automounter has been updated from the 1993 4.4BSD version to the latest current version of am-utils. Map options have changed somewhat, and a new configuration file, /etc/amd.conf, is supported. See ``man 5 amd.conf''. The ``picobsd'' package for creating custom FreeBSD boot floppies and "mini systems" has been brought into /usr/src/release/picobsd. See file:/usr/src/release/picobsd/README.html for further information. When operating over the network, finger(1) no longer closes the socket immediately after sending its request, but instead waits for the remote end to close first. (The specification is ambiguous, so we are following the behavior which interoperates with the most servers.) This means that it is now possible to use the MIT directory and finger people at certain broken Linux machines. There is a new flag to fetch(1) which allows it to talk to certain broken HTTP implementations which react badly to a request message immediately followed by a close of the connection. netstat(1) now uses sysctl(3) to retrieve more statistics groups and uses the correct, unsigned format for printing most of them out. A new VGA library (/usr/src/lib/libvgl) now exists for doing simple VGA graphics to syscons ttys (sort of like Linux's libSVGA). [MERGED: Also in 2.2.5 and later releases on 2.2-STABLE branch] Xntpd's syslogging has been moved out into a facility of its own (LOG_NTP, userland name "ntp"). A new pair of ioctl's has been added: SIOC[SG]IFGENERIC. The intent is to provide for a hook to pass arbitrary ioctl subcommands down to a network interface driver. This is for example necesseray for PPP drivers to communicate things like CHAP names and secrets, or variable options between the driver and a userland utility. sppp(4) has been improved a fair bit since FreeBSD 2.2.X. It now employs a full-fledged PPP state machine, offers a lot more of LCP and IPCP negotiation, making it ready for dial-on-demand connections (like those that are often running over ISDN). It also offers PAP or CHAP authentication. The userland counterpart spppcontrol(8) is also the first program that utilizes the abovementioned SIOC[SG]IFGENERIC ioctl commands. moused(8) has been modified to support various mice with a ``wheel''. It also automatically recognizes mice which support the PnP COM device standard, so that the user is no longer required to supply a mouse protocol type on the command line. [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch] ppp(8) supports many additional features including the PPP Multilink Protocol (rfc1990), PPP Callback (with CBCP extensions) and client side DNS negotiation. Refer to the README.changes file in the source directory for details of possible configuration conflicts. Pthread read/write locks as defined by the Single UNIX Specification, Version 2, have been added to the POSIX threads library, libc_r. System files are now owned by user `root', group `wheel'. UID 0 is far more protected than `bin'. Especially over NFS. /bin/sh signal and trap handling reworked. Among other things, this makes tty-mode emacs work when called from system(2), i.e. by a mail agent. Several syntax bugs have been fixed. [MERGED: Also in 2.2.8 and later releases on 2.2-STABLE branch] systat(1), iostat(8), rpc.rstatd(8), and vmstat(8) have been overhauled to use the new devstat(3) library and devstat(9) statistics subsystem. Among other enhancements, these utilities (well, with the exception of rpc.rstatd(8)) now print out more useful statistics, and can see statistics for all devices in the system, not just the first 8. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920/2940/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7880, AIC789x, on-board SCSI controllers. AdvanSys SCSI controllers (all models). 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 DPT SCSI/RAID controllers (most variants). SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic SCSI and Fibre Channel controllers. DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface SCSI TAPE SUPPORT: The CAM SCSI tape driver doesn't yet handle older (and many times broken) tape drives very well. If you've got an older SCSI-1 tape drive, like an Exabyte 8200 or older QIC-type tape drive, it may not work properly with the CAM tape driver. This is obviously a known problem, and we're working on it. Newer tape drives that are mostly SCSI-2 compliant should work fine. e.g., DAT (DDS-1, 2 and 3), DLT, and newer Exabyte 8mm drives should work fine. If you want to find out if your particular tape drive is supported, the best way to find out is to try it! The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. [ Note: There is work-in-progress to port the AIC-6260/6360 and UltraStor drivers to the new CAM SCSI framework, but no estimates on when or if they will be completed. ] Unmaintained drivers, they might or might not work for your hardware: Floppy tape interface (Colorado/Mountain/Insight) (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 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), 3C590/592/595/900/905/905B PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL Toshiba ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA 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? 2.3 ATM ------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signalling Protocols - The ATM Forum UNI 3.1 signalling protocol - The ATM Forum UNI 3.0 signalling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signalling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.4. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 3.0-RELEASE and 2.2.x-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite D Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the following issues may affect you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. In the case of using sources, there are simply two targets you need to be aware of: The standard ``world'' target, which will upgrade a 2.x system to 3.0, or the ``aout-to-elf'' target, which will both upgrade and convert the system to ELF binary format. In the case of using the binary upgrade option, the system will go straight to 3.0/ELF but also populate the //lib/aout directories for backwards compatibility with older binaries. In either case, going to ELF will mean that you'll have somewhat smaller binaries and access to a lot more compiler goodies which have been already been ported to other ELF environments (our older and somewhat crufty a.out format being largely unsupported by most other software projects), but on the downside you'll also have access to far fewer ports and packages since many of those have not been adapted to ELF yet. This will occur in time, but those who wish to retain access to the greatest number of packages and 3rd-party binaries should probably stick with a.out. The kernel is also still in a.out format at this time so that older LKMs and library interfaces can continue to work, but a full transition to ELF will occur at some point after 3.0-RELEASE. Those wishing to generate dynamic kernel components should therefore use the newer KLD mechanism rather than the older LKM format - the LKM format is not long for this world and will soon be unsupported! [ other important upgrading notes should go here] 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html Justin M. Seger for almost single-handedly converting the ports collection to ELF. Doug Rabson and John Birrell for making FreeBSD/alpha happen and to the NetBSD project for substantial indirect aid. Peter Wemm for the new kernel module system (with substantial aid from Doug Rabson). And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/3.1R/announce.adoc b/website/content/en/releases/3.1R/announce.adoc index 65f4aa516b..d93edd8600 100644 --- a/website/content/en/releases/3.1R/announce.adoc +++ b/website/content/en/releases/3.1R/announce.adoc @@ -1,67 +1,67 @@ --- title: "FreeBSD 3.1 Announcement" sidenav: download ---- +--- = FreeBSD 3.1 Announcement *Date:* Mon, 15 Feb 1999 12:00:03 -0700 + *From:* "Jordan K. Hubbard" + **Subject:**FreeBSD 3.1 is now released! We are pleased, as always, to announce the availability of 3.1-RELEASE, the much anticipated follow-on release to FreeBSD 3.0 (released November, 1998). Many hundreds of bug fixes and general enhancements have been made to the system so please see the link:notes.html[release notes] for more information. FreeBSD 3.1-RELEASE is available on ftp://ftp.freebsd.org/pub/FreeBSD[ftp.freebsd.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.cdrom.com/[Walnut Creek CDROM], from where it will be shipping shortly as a 4 CD set containing a lot of extra stuff of interest to programmers and general users alike. *IMPORTANT NOTE*: All of the profits from the sales of this CD set go to support the FreeBSD Project! Like many businesses in the field of high-tech, Walnut Creek CDROM has realized that in order to make any product for an emerging market grow, you have to make a significant investment in such growth, even if it means abandoning short-term profits. Walnut Creek CDROM is the only CDROM vendor who currently does anything like this and it's certainly my hope that you will help support the project by buying (or getting someone else to buy :) one of their CDs. Thanks! The official FTP distribution site for FreeBSD is: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD ____ Or via the WEB page at: ____ http://www.cdrom.com ____ And on CD-ROM from Walnut Creek CDROM: ____ Walnut Creek CDROM + 4041 Pike Lane, #F + Concord CA, 94520 USA + Phone: +1 925 674-0783 + Fax: +1 925 674-0821 + Tech Support: +1 925 603-1234 + Email: info@cdrom.com + WWW: http://www.cdrom.com/ ____ If you are in Japan, please refer to http://www.pht.co.jp/[Pacific HiTech] for information on ordering a localized (or the english) version of the 3.1 product when it becomes available. Pacific HiTech is now an affiliate of Walnut Creek CDROM for Japanese sales of FreeBSD. Additionally, FreeBSD is available via anonymous FTP from https://www.FreeBSD.org/handbook/mirrors.html[mirror sites] in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: ____ ftp://ftp..freebsd.org/pub/FreeBSD ____ Any additional mirror sites will be labeled ftp2, ftp3 and so on. The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also 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:: ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt link:../../[Release Home] diff --git a/website/content/en/releases/3.1R/errata.adoc b/website/content/en/releases/3.1R/errata.adoc index 7775802d98..d60ac39b58 100644 --- a/website/content/en/releases/3.1R/errata.adoc +++ b/website/content/en/releases/3.1R/errata.adoc @@ -1,77 +1,77 @@ --- title: "FreeBSD 3.1 Errata Notes" sidenav: download ---- +--- = FreeBSD 3.1 Errata Notes .... The file ERRATA.TXT contains post-release ERRATA for 3.1 and should always be considered the definitive place to look *first* before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For all FreeBSD security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest information. ---- Security Advisories: Current active security advisories for 3.1: None ---- System Update Information: o Some packages, like netscape, will fail to install if chosen at initial system installation time, in some cases claiming that the "compat22" distribution needs to be installed even though it has, indeed, been installed. Fix: The problem here is that though the compatibility a.out libraries may have been installed from compat22 and as part of the XFree86 distribution, the a.out library (ldconfig) cache has not yet been built given that this doesn't happen until the system has booted completely at least once. This causes packages which require the old a.out libraries (like netscape) to get confused if they're installed before that has occurred. To work around the problem, simply complete the installation as normal and come up fully, then re-run /stand/sysinstall (or use the pkg_add(1) command directly) to re-install the failing package(s). o Kernel change information is not saved in the new kernel, even though this is claimed to work in the docs. Fix: The change information is being written out, in fact, but to the wrong location. move /kernel.config to /boot/kernel.conf (if it exists, otherwise there were no changes to save) and add the following lines to /boot/loader.rc: load /kernel load -t userconfig_script /boot/kernel.conf autoboot 5 This will cause the kernel change information to be read in and used properly (and you just learned a little about the new 3-stage loader in the process, so the exercise wasn't a total loss). o DOS installation fails when you actually follow the instructions to install stuff under C:\FREEBSD\BIN\... and so on. Fix: The instructions are correct but the code was wrong in 3.1-RELEASE, sysinstall looking instead directly under C:\ (e.g. C:\BIN\...) or under C:\RELEASES\ (C:\RELEASES\BIN\... and so on). Fixed in 3.1-STABLE. .... link:../../[Release Home] diff --git a/website/content/en/releases/3.1R/notes.adoc b/website/content/en/releases/3.1R/notes.adoc index 18d970e610..ee1dd6b089 100644 --- a/website/content/en/releases/3.1R/notes.adoc +++ b/website/content/en/releases/3.1R/notes.adoc @@ -1,602 +1,602 @@ --- title: "FreeBSD 3.1 Release Notes" sidenav: download ---- +--- = FreeBSD 3.1 Release Notes .... RELEASE NOTES FreeBSD Release 3.1-RELEASE Welcome to 3.1-RELEASE, a full follow-on to the 3.0-RELEASE released November 1998 and which marked the beginning of the 3.0-STABLE branch. In the 4 months since 3.0 was released, many hundreds of bug fixes and general enhancements were made to the system. Please see relevant details below. Any installation failures or crashes should be reported by using the send-pr command (those preferring a WEB based interface can also see this page). For information about FreeBSD and the layout of the 3.1-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. Table of contents: ------------------ 1. What's new since 3.0-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 ATM 2.4 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgements 1. What's new since 3.0-RELEASE --------------------------------- 1.1. KERNEL CHANGES ------------------- Added driver support for fast ethernet adapters based on the RealTek 8129/8139 and Accton MPX 5030/5038 chips, including the SMC EZ Card 10/100 PCI 1211-TX. Added driver support for Lite-On PNIC-based fast ethernet cards including the LinkSys LNE100TX, NetGear FA310TX Rev. D1 and Matrox FastNIC 10/100. Added driver support for fast ethernet adapters based on the Macronix 98713, 98713A, 98715, 98715A and 98725 chips. Added driver support for fast ethernet adapters based on the Winbond W89C840F chip. Added driver support for fast ethernet adapters based on the VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" chips. Added driver support for pocket ethernet adapters based on the RealTek RTL 8002 chip. Added driver support for fast ethernet adapters based on the ASIX Electronics AX88140A chip. Integrated isdn4bsd from the isdn4bsd project group into the regular system. System console driver (sc0) now broken into individual stand-alone modules, partly in preparation for USB keyboards, mice, etc. Phillips I2C/SMBUS support. Initial support for USB devices (some keyboards, mice). The lpt driver is now deprecated. Please use ppbus with the ppc driver instead (see the ppc(4) and ppbus(4) man pages for details). At some point before the next release, the old lpt driver will be removed and the nlpt driver will be renamed to lpt. 1.2. SECURITY FIXES ------------------- See ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ for details: CERT Advisory CA-98-13-tcp-denial-of-service closed. FreeBSD-SA-98:08 (IP fragmentation denial of service) closed. KerberosIV more fully supported. 1.3. USERLAND CHANGES --------------------- When using ipfw(8) with the syntax of the first synopsis line from the man page (i. e., with a rules file), it can now optionally be run through a preprocessor (m4, cpp) so it's possible to use symbolic names and other constructs that make maintenance easier. Support for PAM (Pluggable Authentication Modules) including modules for radius, TACACS, S/Key, Kerberos, Unix (passwd) and other authentication methods. Sendmail upgraded to version 8.9.2. AMD, texinfo, global and many other various utilities updated. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V is not yet supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic 1020, 1040, 1040B and 2100 SCSI and Fibre Channel Adapters DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. [ Note: There is work-in-progress to port the AIC-6260/6360 and UltraStor drivers to the new CAM SCSI framework, but no estimates on when or if they will be completed. ] Unmaintained drivers, they might or might not work for your hardware: Floppy tape interface (Colorado/Mountain/Insight) (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 fast ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC fast ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Macronix 98713, 98713A, 98715, 98715A and 98725 fast ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Winbond W89C840F fast ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE530TX Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100baseTX Racore 8148 10baseT/100baseTX/100baseFX multi-personality ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 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), 3C590/592/595/900/905/905B PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980 Fast Etherlink XL server adapter Toshiba ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA 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? 2.3 ATM ------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signalling Protocols - The ATM Forum UNI 3.1 signalling protocol - The ATM Forum UNI 3.0 signalling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signalling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.4. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 3.1-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite F Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the following issues may affect you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. In the case of using sources, there are simply two targets you need to be aware of: The standard ``upgrade'' target, which will upgrade a 2.x or 3.0 system to 3.1 and the ``world'' target, which will take an already upgraded system and keep it in sync with whatever changes have happened since the initial upgrade. In the case of using the binary upgrade option, the system will go straight to 3.1/ELF but also populate the //lib/aout directories for backwards compatibility with older binaries. In either case, going to ELF will mean that you'll have somewhat smaller binaries and access to a lot more compiler goodies which have been already been ported to other ELF environments (our older and somewhat crufty a.out format being largely unsupported by most other software projects). Those who wish to retain access to the older a.out dynamic executables should be sure and install the compat22 distribution. [ other important upgrading notes should go here] 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html Steve Price for his work in building and organizing the packages and, as always, Satoshi Asami for his work on the ports collection. Doug Rabson and John Birrell for making FreeBSD/alpha happen and to the NetBSD project for substantial indirect aid. Peter Wemm for the new kernel module system (with substantial aid from Doug Rabson). And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/3.2R/announce.adoc b/website/content/en/releases/3.2R/announce.adoc index 088d48dd40..9a75b37ab7 100644 --- a/website/content/en/releases/3.2R/announce.adoc +++ b/website/content/en/releases/3.2R/announce.adoc @@ -1,69 +1,69 @@ --- title: "FreeBSD 3.2 Announcement" sidenav: download ---- +--- = FreeBSD 3.2 Announcement *Date:* Mon May 17 19:28:17 PDT 1999 + *From:* "Jordan K. Hubbard" + **Subject:**FreeBSD 3.2 is released! It is my usual pleasure to announce the availability of 3.2-RELEASE, our follow-on to release to FreeBSD 3.1 (released February, 1999). Many bug fixes and general enhancements have been made to the system and a number of new features added, so please see the link:notes.html[release notes] for more information. FreeBSD 3.2-RELEASE is available at ftp://ftp.freebsd.org/pub/FreeBSD[ftp.freebsd.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.freebsdmall.com/[The FreeBSD Mall], from where it will be shipping soon on a 4 CD set containing installation bits for both the x86 and Alpha architectures as well a lot of other material of general interest to programmers and end-users alike. *NOTE*: All of the profits from the sales of this CD set go to support the FreeBSD Project! The official FTP distribution site for FreeBSD is: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD ____ Or via the WEB page at: ____ http://www.freebsdmall.com ____ and ____ http://www.cdrom.com ____ And directly from Walnut Creek CDROM: ____ Walnut Creek CDROM + 4041 Pike Lane, #F + Concord CA, 94520 USA + Phone: +1 925 674-0783 + Fax: +1 925 674-0821 + Tech Support: +1 925 603-1234 + Email: info@cdrom.com + WWW: http://www.cdrom.com/ ____ Additionally, FreeBSD is available via anonymous FTP from https://www.FreeBSD.org/handbook/mirrors.html[mirror sites] in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: ____ ftp://ftp..freebsd.org/pub/FreeBSD ____ Any additional mirror sites will be labeled ftp2, ftp3 and so on. The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also 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:: ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt link:../../[Release Home] diff --git a/website/content/en/releases/3.2R/errata.adoc b/website/content/en/releases/3.2R/errata.adoc index e2f79a1294..00f1f4adde 100644 --- a/website/content/en/releases/3.2R/errata.adoc +++ b/website/content/en/releases/3.2R/errata.adoc @@ -1,69 +1,69 @@ --- title: "FreeBSD 3.2 Errata Notes" sidenav: download ---- +--- = FreeBSD 3.2 Errata Notes .... The file ERRATA.TXT contains post-release ERRATA for 3.2 and should always be considered the definitive place to look *first* before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For all FreeBSD security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest information. ---- Security Advisories: Current active security advisories for 3.2: None ---- System Update Information: o The compat20 and compat21 distributions install themselves into /usr/lib/compat. The compat20/compat21 distributions are a.out libraries, thus they should live in /usr/lib/compat/aout to match the "ldconfig_paths_aout" configuration in /etc/defaults/rc.conf. Fix: cd /usr/lib/compat mkdir -p aout mv lib*.so.*.* aout o /usr/bin/gdb crashes when debugging core files from static programs Fix: This was corrected in revision 1.3.2.2 of solib.c. Obtain the fixed version via CVSup (see instructions in handbook) or apply the patch from our CVSweb service. o While booting the install floppy, user sees the following message and nothing seems to happen, nor can anything be entered from the keyboard: Keyboard: no Fix: Due to a lack of space, full support for old XT/AT (84-key) keyboards is no longer available in the bootblocks. Some notebook computers may also have this type of keyboard and if you are still using this kind of hardware, you will see the above message about no keyboard being found when you boot from an installation CD-ROM or floppy. As soon as you see the message, hit the space bar and you will see the following prompt: >> FreeBSD/i386 BOOT Default: x:xx(x,x)/boot/loader boot: Then enter `-Dh', and things should proceed normally with your keyboard type. This only happens once at initial installation time and will not be a problem afterwards. .... link:../../[Release Home] diff --git a/website/content/en/releases/3.2R/notes.adoc b/website/content/en/releases/3.2R/notes.adoc index d93b5a44fb..fee9054dfb 100644 --- a/website/content/en/releases/3.2R/notes.adoc +++ b/website/content/en/releases/3.2R/notes.adoc @@ -1,602 +1,602 @@ --- title: "FreeBSD 3.2 Release Notes" sidenav: download ---- +--- = FreeBSD 3.2 Release Notes .... RELEASE NOTES FreeBSD 3.2-RELEASE Welcome to 3.2-RELEASE, a full follow-on to the 3.1-RELEASE released February 1999 and which marked the beginning of the 3.0-STABLE branch. In the 4 months since 3.1 was released, many hundreds of bug fixes and general enhancements were made to the system. Please see relevant details below. Any installation failures or crashes should be reported by using the send-pr command (those preferring a WEB based interface can also see this page). For information about FreeBSD and the layout of the 3.2-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. Table of contents: ------------------ 1. What's new since 3.1-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 ATM 2.4 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgements 1. What's new since 3.1-RELEASE --------------------------------- 1.1. KERNEL CHANGES ------------------- Added driver support for PCI gigabit ethernet adapters based on the Alteon Networks Tigon 1 and Tigon 2 chipsets, including the Alteon AceNIC, 3Com 3c985 and Netgear GA620. Support for USB devices further improved. Support has been added for direct access to NTFS filesystems. Support has been added for Joliet extensions on ISO 9660 filesystems. Only iso8859-1 characters (latin-1) are supported at this time, though. Support has been added for Adaptec 2930U2 and 3950U2 SCSI cards. There have been a couple of kernel changes that will break the binary interface for clients of the CAM passthrough interface or the devstat(9) statistics interface. These changes were made to fix some interface deficiencies. We regret any inconvenience this will cause, but we anticipate that this will have minimal impact as there are no known commercial binary-only applications that use either interface. This will require that programs that use those two interfaces be recompiled. Ports that use the CAM interface include xmcd, tosha, SANE, cdrecord and cdda2wav. Ports that use the devstat interface include xsysinfo and xperfmon. 1.2. SECURITY FIXES ------------------- Descriptor leak bug which was potentially open to a denial of service attack (by local users) was closed. REF: KKIS.05051999.003b 1.3. USERLAND CHANGES --------------------- The Internet Software Consortium's DHCP client has been added to the base system. Sendmail upgraded to version 8.9.3. Tar now supports compressing via bzip2 with the new -y/--bzip2/--bunzip2 flags. TCP Wrappers is now part of the base system. inetd, the port mapper, and sendmail are now linked agaist libwrap. The "PROCESS_OPTIONS" syntax is the default. Note that you do not need to use tcpd in /etc/inetd.conf. See `man 5 hosts_options' and `man 8 inetd` for more information. Gdb has been updated to version 4.18 and is now part of the standard release for FreeBSD/alpha. Camcontrol now allows users to view the number of tagged openings for any given device, and allows users to set the number of tagged openings for any device that supports tagged queueing. Camcontrol also now allows users to change SCSI negotiation parameters (e.g. sync rate, offset, bus width, disconnection) for devices on certain controllers. Note that this feature is only fully functional for Adaptec 7xxx series controllers, Advansys narrow controllers and NCR/Symbios controllers. Systat, vmstat, and iostat now print out statistics in a more "interesting" order based on "importance" of the device vs. the probe order. And quite a number of bugs, both in the user and kernel, fixed as a result of user feedback for 3.1-RELEASE. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/2930U2/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V is not yet supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. [ Note: There is work-in-progress to port the AIC-6260/6360 and UltraStor drivers to the new CAM SCSI framework, but no estimates on when or if they will be completed. ] Unmaintained drivers, they might or might not work for your hardware: Floppy tape interface (Colorado/Mountain/Insight) (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI gigabit ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: Alteon AceNIC (Tigon 1 and 2) 3Com 3c985-SX (Tigon 1 and 2) Netgear GA620 (Tigon 2) Silicon Graphics Gigabit Ethernet DEC/Compaq EtherWORKS 1000 NEC Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 fast ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC fast ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Macronix 98713, 98713A, 98715, 98715A and 98725 fast ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Winbond W89C840F fast ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE530TX Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100baseTX Racore 8148 10baseT/100baseTX/100baseFX multi-personality ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980 Fast Etherlink XL server adapter Toshiba ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA 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? 2.3 ATM ------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signalling Protocols - The ATM Forum UNI 3.1 signalling protocol - The ATM Forum UNI 3.0 signalling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signalling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.4. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 and Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. 3.2. CDROM ---------- FreeBSD 3.2-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite F Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.freebsdmall.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the following issues may affect you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. In the case of using sources, there are simply two targets you need to be aware of: The standard ``upgrade'' target, which will upgrade a 2.x or 3.0 system to 3.2 and the ``world'' target, which will take an already upgraded system and keep it in sync with whatever changes have happened since the initial upgrade. In the case of using the binary upgrade option, the system will go straight to 3.2/ELF but also populate the //lib/aout directories for backwards compatibility with older binaries. In either case, going to ELF will mean that you'll have somewhat smaller binaries and access to a lot more compiler goodies which have been already been ported to other ELF environments (our older and somewhat crufty a.out format being largely unsupported by most other software projects). Those who wish to retain access to the older a.out dynamic executables should be sure and install the compat22 distribution. Notice that the a.out libraries won't be accessible until the system is rebooted, which may cause trouble with certain a.out packages. Also, do not use install disks or sysinstall from previous versions, as version 3.1 introduced a new bootstrapping procedure, requiring new boot blocks to be installed (because of elf kernels), and version 3.2 has further modifications to the bootstrapping procedure. [ other important upgrading notes should go here] 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/3.3R/announce.adoc b/website/content/en/releases/3.3R/announce.adoc index b220fdb138..70ebe5857f 100644 --- a/website/content/en/releases/3.3R/announce.adoc +++ b/website/content/en/releases/3.3R/announce.adoc @@ -1,73 +1,73 @@ --- title: "FreeBSD 3.3 Announcement" sidenav: download ---- +--- = FreeBSD 3.3 Announcement *Date:* Fri, 17 Sep 1999 05:06:44 -0700 + *From:* "Jordan K. Hubbard" + **Subject:**FreeBSD 3.3-RELEASE is now available. Yes, it's that time again! I'm very happy to announce the availability of FreeBSD 3.3-RELEASE, the latest in our line of releases from the 3.x-STABLE branch. The follow-on to FreeBSD 3.2 (released in May, 1999), a lot of new drivers have been added, many bugs were fixed and several important security issues where dealt with. Please see the link:../notes/[release notes] for more information. FreeBSD 3.3-RELEASE is available at ftp://ftp.freebsd.org/pub/FreeBSD[ftp.freebsd.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.freebsdmall.com/[The FreeBSD Mall], from where it will be shipping soon on a 4 CD set containing installation bits for the x86 architectures, as well a lot of other material of general interest to programmers and end-users alike. (3.3-RELEASE for the Alpha architecture is available from the FTP site). NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project! We are also trying something new with 3.3-RELEASE in making ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.3-install.cd0[disc #1] from Walnut Creek CDROM's official distribution available via ftp://ftp.freebsd.org/pub/FreeBSD/[anonymous FTP.] This is the most important CD of their 4 set, one which will allow users to install the base system and all of its most important add-ons from a single ISO 9660 image. We are doing this because the ISO image is rapidly becoming the preferred format for distributing operating system releases and we're certainly not going to go out of our way to make FreeBSD harder to "test drive" if providing the standard NFS/FTP network installation methods is no longer enough. We can't promise that all the mirror sites will carry the rather large installation (660MB) image, but it will at least be available from: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.3-install.cd0. along with the more traditional 3.3-RELEASE bits. If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from http://www.freebsdmall.com[Walnut Creek CDROM]. The official FTP distribution site for FreeBSD is: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD ____ Or via the WEB page at: ____ http://www.freebsdmall.com ____ and ____ http://www.cdrom.com ____ And directly from Walnut Creek CDROM: ____ Walnut Creek CDROM + 4041 Pike Lane, #F + Concord CA, 94520 USA + Phone: +1 925 674-0783 + Fax: +1 925 674-0821 + Tech Support: +1 925 603-1234 + Email: info@cdrom.com + WWW: http://www.cdrom.com/ ____ Additionally, FreeBSD is available via anonymous FTP from link:../../handbook/mirrors.html[mirror sites] in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: ____ ftp://ftp..freebsd.org/pub/FreeBSD ____ Any additional mirror sites will be labeled ftp2, ftp3 and so on. The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also 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:: ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt link:../../[Release Home] diff --git a/website/content/en/releases/3.3R/errata.adoc b/website/content/en/releases/3.3R/errata.adoc index 27050b9e41..75887565ad 100644 --- a/website/content/en/releases/3.3R/errata.adoc +++ b/website/content/en/releases/3.3R/errata.adoc @@ -1,126 +1,126 @@ --- title: "FreeBSD 3.3 Errata Notes" sidenav: download ---- +--- = FreeBSD 3.3 Errata Notes .... The file ERRATA.TXT contains post-release ERRATA for 3.3 and should always be considered the definitive place to look *first* before reporting a problem with this release. This file will also be periodically updated as new issues are reported so even if you've checked this file recently, check it again before filing a bug report. Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For all FreeBSD security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest information. ---- Security Advisories: Current active security advisories for 3.3: None ---- System Update Information: The fvwm desktop choice in the X Desktops menu doesn't work. Fix: Install fvwm from /usr/ports/x11-wm/fvwm2 instead of using the desktop menu item and put "fvwm" in your $HOME/.xinitrc and $HOME/.xsession files for use by startx/xdm. You can also build and reinstall /usr/src/release/sysinstall from 3.3-STABLE sources to fix the X Desktop menu item in question. The lo0 (loop-back) device is not configured on startup, causing utilities like mountd to fail. Fix: Assuming that you experience this problem at all, edit /etc/rc.conf and search for where the network_interfaces variable is set. In its value, change the word "auto" to "lo0" since the auto keyword doesn't bring the loop-back device up properly, for reasons yet to be adequately determined. Since your other interface(s) will already be set in the network_interfaces variable after initial installation, it's reasonable to simply s/auto/lo0/ in rc.conf and move on. The 3.3 ISO image (and 3.3 CDROM #1 from Walnut Creek CDROM) mysteriously fails to boot on an ATAPI CDROM device but works with SCSI CDROMs (on adaptors which support bootable CDs). Fix: Either install using boot floppies (see floppies/README.TXT) rather than booting from the CDROM or grab the updated ISO image from: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/ See also the CHECKSUM.MD5 file in that directory to verify whether you have the "old" or new image - some mirrors may be slow in picking up the uncompressed and gzipped versions of the ISO 9660 installation image. As always, Walnut Creek CDROM will also provide replacement CDs (once they become available) on request to purchasers of the 3.3-RELEASE product. This problem was caused by a bug in mkisofs which we're still chasing but have, for now, simply worked-around. Ppp(8) does not properly detect carrier in direct mode. Fix: Download and install the latest version of ppp(8) from: http://www.FreeBSD.org/~brian/ (US) http://www.Awfulhak.org/~brian/ (UK) or upgrade your system to -stable. Hitting Ctl-Alt-Space may panic the kernel with the apm driver which is disabled or is not functional because of the lack of APM support in the motherboard. Fix: To fix this, apply the following patch to /sys/i386/apm/apm.c and rebuild the kernel. Index: apm.c =================================================================== RCS file: /src/CVS/src/sys/i386/apm/apm.c,v retrieving revision 1.77.2.8 retrieving revision 1.77.2.9 diff -u -r1.77.2.8 -r1.77.2.9 --- apm.c 1999/09/12 01:06:28 1.77.2.8 +++ apm.c 1999/09/20 15:34:29 1.77.2.9 @@ -621,6 +621,9 @@ apm_suspend(int state) { struct apm_softc *sc = &apm_softc; + + if (!sc->initialized) + return; switch (state) { case PMST_SUSPEND: If you don't like to rebuild the kernel, you can edit your keymap file so that it won't cause panic. Find your keymap file in /usr/share/syscons/keymap. Open it with an editor program and locate the following line. 057 ' ' ' ' nul ' ' ' ' ' ' susp ' ' O ~~~~ Change it to 057 ' ' ' ' nul ' ' ' ' ' ' ' ' ' ' O ~~~ (a quoted space) You must change the next line too. 104 slock saver slock saver susp nop susp nop O ~~~~ ~~~~ Edit this to 104 slock saver slock saver nop nop nop nop O .... link:../../[Release Home] diff --git a/website/content/en/releases/3.3R/notes.adoc b/website/content/en/releases/3.3R/notes.adoc index dba19107ef..efa245c2fe 100644 --- a/website/content/en/releases/3.3R/notes.adoc +++ b/website/content/en/releases/3.3R/notes.adoc @@ -1,684 +1,684 @@ --- title: "FreeBSD 3.3 Release Notes" sidenav: download ---- +--- = FreeBSD 3.3 Release Notes .... RELEASE NOTES FreeBSD 3.3-RELEASE Welcome to 3.3-RELEASE, a full follow-on to 3.2-RELEASE released May 1999. In the months since 3.2 was released, many bug fixes and general enhancements have been made to the system. Please see relevant details below. Any installation failures or crashes should be reported by using the send-pr command (those preferring a WEB based interface can also see this page). For information about FreeBSD and the layout of the 3.3-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. Table of contents: ------------------ 1. What's new since 3.2-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 ATM 2.4 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.3 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgements 1. What's new since 3.2-RELEASE --------------------------------- 1.1. KERNEL CHANGES ------------------- The Berkeley Packet Filter (bpf) is enabled by default. This is to allow DHCP supported installs. Linux mode has undergone significant bug fixes and improvements. The i386 bootstrap has been enhanced for some problematic systems. Driver support has been added for IEEE 802.11 PCMCIA wireless network adapters based on the Lucent Hermes chipset, including the Lucent WaveLAN/IEEE 802.11 and the Cabletron RoamAbout. Both 2Mbps and 6Mbps Turbo adapters are supported. [MERGED] Driver support has been added for PCI fast Ethernet cards based on the ADMtek Inc. AL981 Comet chipset. Driver support has been added for PCI fast Ethernet cards based on the LC82C115 'PNIC II' chipset. Driver support has been added for SysKonnect SK-984x PCI gigabit Ethernet adapters. Driver support has been added for Adaptec Duralink PCI Ethernet adapters based on the Adaptec AIC-6915 fast Ethernet controller. Driver support for M-systems DiskOnChip products integrated. Driver support has been added for the 3Com 3c905C-TX. Driver support has been added for the 3Com 3x574-TX 16-bit FastEtherlink PC-card support. Driver support has been added for the Compaq Smart Raid family of RAID controllers. Driver support for a number of Realtek and Avance Asound audio cards has been added. USB support has been improved. Major updates to the Vinum volume manager have been incorporated. [Though the new RAID-5 features should still be considered experimental since they are, well, new]. A number of NFS problems have been fixed. APM support has been improved. A kernel panic problem with an older APM BIOSes has been fixed. Also, the suspend/standby transition is more robust. User- and group-based IPFW firewalling has been added. Support for probabilistic rule matching has been added to IPFW. IPFW logging is now dynamic. IPFW logging counts can be reset, and any given rule can be given an arbitrary logging limit. 1.2. SECURITY FIXES ------------------- A problem with filesystems flags has been corrected. A problem with profil(2) remaining inactive after an exec call. A remotely exploitable root hole in amd (the automount daemon) has been fixed. The wu-ftpd port has been updated with the latest patches to prevent possible remote root exploits. The proftpd port has been updated with the latest patches to prevent possible remote root exploits. The samba port has been updated with the latest patches to prevent possible remote root exploits. The inn port has been updated to a new version that corrects some buffer overflows. Since FreeBSD 3.0 RELEASE, many minor problems with the network stack have been corrected which could have been exploited for denial of service attacks. 1.3. USERLAND CHANGES --------------------- The support environment for Linux mode has finally been updated. The linux_lib and linux_devel ports are replaced by resp. linux_base and linux_devtools. These new ports are based on Red Hat 5.2 packages and include support for both glibc2 and libc5 based applications. Sysinstall now contains DHCP client support. TCP Wrapper support in inetd(8) is now controlled with command-line options and data-gram (UDP) services may be wrapped in addition to previously wrapped service types. Please see the manpage for details, since inetd run without command-line options will do no wrapping. ISC's DHCP client has been upgraded to version 2.0. Bison, the GNU parser generator, has been upgraded to version 1.28. The Advanced Power Management monitor daemon, apmd(8), has been added. This allows the user to select the APM events to be handled from userland and specify the commands for a given event. This allows the APM behavior to be configured in a flexable manner. Please see the manpage for details. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V is not yet supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: Tekram DC390 and DC390T controllers (maybe other cards based on the AMD 53c974 as well). NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. [ Note: There is work-in-progress to port the AIC-6260/6360 and UltraStor drivers to the new CAM SCSI framework, but no estimates on when or if they will be completed. ] Unmaintained drivers, they might or might not work for your hardware: Floppy tape interface (Colorado/Mountain/Insight) (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Adaptec Duralink PCI fast Ethernet adapters based on the Adaptec AIC-6915 fast Ethernet controller chip, including the following: ANA-62011 64-bit single port 10/100-BaseTX adapter ANA-62022 64-bit dual port 10/100-BaseTX adapter ANA-62044 64-bit quad port 10/100-BaseTX adapter ANA-69011 32-bit single port 10/100-BaseTX adapter ANA-62020 64-bit single port 100-BaseFX adapter Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: Alteon AceNIC (Tigon 1 and 2) 3Com 3c985-SX (Tigon 1 and 2) Netgear GA620 (Tigon 2) Silicon Graphics Gigabit Ethernet DEC/Compaq EtherWORKS 1000 NEC Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 fast Ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX Macronix 98713, 98713A, 98715, 98715A and 98725 fast Ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Macronix/Lite-On PNIC II LC82C115 fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX Version 2 Winbond W89C840F fast Ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast Ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE530TX SysKonnect SK-984x PCI gigabit Ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port SK-9842 1000baseSX multi-mode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multi-mode fiber, dual port Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100-BaseTX Racore 8148 10-BaseT/100-BaseTX/100-BaseFX multi-personality ADMtek Inc. AL981-based PCI fast Ethernet NICs ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 Ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B/905C PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980/3c980B Fast Etherlink XL server adapter 3Com 3cSOHO100-TX OfficeConnect adapter Toshiba Ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA PCMCIA Etherjet 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? 2.3 ATM ------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signaling Protocols - The ATM Forum UNI 3.1 signaling protocol - The ATM Forum UNI 3.0 signaling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signaling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multi-protocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.4. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multi-port serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and work-a-likes (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 3.3-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite F Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the following issues may affect you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. In the case of using sources, there are simply two targets you need to be aware of: The standard ``upgrade'' target, which will upgrade a 2.x or 3.0 system to 3.3 and the ``world'' target, which will take an already upgraded system and keep it in sync with whatever changes have happened since the initial upgrade. In the case of using the binary upgrade option, the system will go straight to 3.3/ELF but also populate the //lib/aout directories for backwards compatibility with older binaries. In either case, going to ELF will mean that you'll have somewhat smaller binaries and access to a lot more compiler goodies which have been already been ported to other ELF environments (our older and somewhat crufty a.out format being largely unsupported by most other software projects). Those who wish to retain access to the older a.out dynamic executables should be sure and install the compat22 distribution. Notice that the a.out libraries won't be accessible until the system is rebooted, which may cause trouble with certain a.out packages. Also, do not use install disks or sysinstall from previous versions, as version 3.1 introduced a new bootstrapping procedure, requiring new boot blocks to be installed (because of elf kernels), and version 3.2 has further modifications to the bootstrapping procedure. [ other important upgrading notes should go here] 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. Acknowledgments ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/3.4R/announce.adoc b/website/content/en/releases/3.4R/announce.adoc index df60859866..9ffcaa058b 100644 --- a/website/content/en/releases/3.4R/announce.adoc +++ b/website/content/en/releases/3.4R/announce.adoc @@ -1,72 +1,72 @@ --- title: "FreeBSD 3.4 Announcement" sidenav: download ---- +--- = FreeBSD 3.4 Announcement *Date:* Mon, 20 Dec 1999 10:45:47 -0800 + *From:* "Jordan K. Hubbard" + **Subject:**FreeBSD 3.4-RELEASE is now available. Just in under the wire for the current millenium, I'm happy to announce the availability of FreeBSD 3.4-RELEASE, the very latest in 3.x-STABLE branch technology. Following the release of FreeBSD 3.3 in Sept, 1999, a lot of new features have been added, many bugs were fixed and even more important security issues were dealt with. Please see the link:notes.html[release notes] for more information. FreeBSD 3.4-RELEASE is available at ftp://ftp.FreeBSD.org/pub/FreeBSD/[ftp.FreeBSD.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.FreeBSDMall.com/[The FreeBSD Mall], from where it will be shipping soon on a 4 CD set containing installation bits for x86 architecture, as well as a lot of other material of general interest to programmers and end-users alike (3.4-RELEASE for the Alpha architecture is available from the FTP site and will also be available on CDROM several weeks after the x86 product is released). NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project! We are also continuing our new tradition (started with 3.3-RELEASE) of making disc #1 from Walnut Creek CDROM's official distribution available via anonymous FTP. This is the most important CD of their 4 set, one which will allow users to install the base system and all of its most important add-ons from a single ISO 9660 image. We are doing this because the ISO image is rapidly becoming the preferred format for distributing operating system releases and we're certainly not going to go out of our way to make FreeBSD harder to "test drive" if providing the standard NFS/FTP network installation methods is no longer enough. This is a fully-bootable ISO 9660 (with RockRidge extensions) image and can be written as a raw ISO image by most CD creator software. We can't promise that all the mirror sites will carry the rather large installation (660MB) image, but it will at least be available from: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.4-install.iso along with the more traditional 3.4-RELEASE bits. If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from Walnut Creek CDROM. The official FTP distribution site for FreeBSD is: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD/ ____ Or via the WEB pages at: ____ http://www.FreeBSDMall.com/ and + http://www.cdrom.com/[http://www.cdrom.com] ____ And directly from Walnut Creek CDROM: ____ Walnut Creek CDROM + 4041 Pike Lane, #F + Concord CA, 94520 USA + Phone: +1 925 674-0783 + Fax: +1 925 674-0821 + Tech Support: +1 925 603-1234 + Email: info@cdrom.com + WWW: http://www.cdrom.com/ ____ Additionally, FreeBSD is available via anonymous FTP from https://www.FreeBSD.org/handbook/mirrors.html[mirror sites] in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp..freebsd.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also 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:: ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt Thanks! - Jordan link:../../[Release Home] diff --git a/website/content/en/releases/3.4R/errata.adoc b/website/content/en/releases/3.4R/errata.adoc index 56ccf51a3e..09e4bcbdc0 100644 --- a/website/content/en/releases/3.4R/errata.adoc +++ b/website/content/en/releases/3.4R/errata.adoc @@ -1,84 +1,84 @@ --- title: "FreeBSD 3.4 Errata Notes" sidenav: download ---- +--- = FreeBSD 3.4 Errata Notes .... If you read no other documentation before installing this version of FreeBSD, you should at least by all means *READ THE ERRATA* for this release so that you don't stumble over problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of the errata are located at: 1. http://www.FreeBSD.org/releases/ 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases//ERRATA.TXT (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For all CERT security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest security incident information. ---- Security Advisories: Current active security advisories for 3.4: FreeBSD-SA-00:01.make ---- System Update Information: As shipped, the "Custom" installation option in 3.4 is broken and menu items like Configure don't work Fix: Both the "Novice" and "Express" install paths still work and can be used just as effectively (if not succinctly). Alternately, you can invoke the custom installation from the "Index" menu (Installation, Custom) along with the Configuration option. You can also just download a fixed mfsroot.flp floppy image (or boot.flp if you need 2.88MB boot media) from the following URL: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.4-RELEASE/floppies/updates/ The 3.4 ISO installation image is also updated to contain fixes for all these errata items. 802.1Q VLAN support compilation error: kernel configurations containing "pseudo-device vlan #" fail to compile Fix: Update your copy of sys/net/if_vlan.c to the 3-stable branch version, where it is fixed, or apply the following patch to the sys/net/if_vlan.c distributed with 3.4-RELEASE: RCS file: /home/ncvs/src/sys/net/if_vlan.c,v retrieving revision 1.4.2.2 retrieving revision 1.4.2.3 diff -C2 -r1.4.2.2 -r1.4.2.3 *** if_vlan.c 1999/12/13 02:02:23 1.4.2.2 --- if_vlan.c 1999/12/25 03:28:51 1.4.2.3 *************** *** 515,519 **** ifv->ifv_p = 0; if_down(ifp); ! ifv->if_flags &= ~(IFF_UP|IFF_RUNNING); break; } --- 515,519 ---- ifv->ifv_p = 0; if_down(ifp); ! ifp->if_flags &= ~(IFF_UP|IFF_RUNNING); break; } .... link:../../[Release Home] diff --git a/website/content/en/releases/3.4R/notes.adoc b/website/content/en/releases/3.4R/notes.adoc index f5d1032d87..c622f39ced 100644 --- a/website/content/en/releases/3.4R/notes.adoc +++ b/website/content/en/releases/3.4R/notes.adoc @@ -1,632 +1,632 @@ --- title: "FreeBSD 3.4 Release Notes" sidenav: download ---- +--- = FreeBSD 3.4 Release Notes .... RELEASE NOTES - FREEBSD 3.4-RELEASE Welcome to 3.4-RELEASE, a full follow-on to 3.3-RELEASE which was shipped in October 1999. In the months since 3.3 was released, many bug fixes and general enhancements have been made to the system. Please see relevant details below. Any installation failures or crashes should be reported by using the send-pr command (those preferring a WEB based interface can also see http://www.FreeBSD.org/send-pr.html). For information about FreeBSD and the layout of the 3.4-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. Table of contents: ------------------ 1. What's new since 3.3-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 ATM 2.4 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgments 1. What's new since 3.3-RELEASE --------------------------------- 1.1. KERNEL CHANGES ------------------- Support for Adaptec 152x/151x/AIC-6360 SCSI controllers is back. netgraph(4) has been added. Netgraph provides a uniform and modular system for the implementation of kernel objects which perform various networking functions. To enable it, ``options NETGRAPH'' must be added to the kernel. i4b(4) has been upgraded to version 00.83.00, providing increased robustness and stability, and supporting many new cards (Asuscom ISDNlink 128K, AVM Fritz!Card PCI, AVM Fritz!Card PnP, ELSA PCC-16, ITK ix1 micro V.3, Siemens I-Surf 2.0). RAID-5 support has been added to vinum(8). Driver support for the Intel PIIX4 and AcerLabs M15x3 power management controllers has been added. 1.2. SECURITY CHANGES --------------------- Support has been added for blocking incoming ICMP redirects, outgoing RST frames and incoming SYN|FIN frames in order to lessen or nullify the impact of certain kinds of DoS attacks. Support has been added for forwarding IP datagrams without inspecting or decreasing the TTL in order to make gateways and firewalls less visible and therefore less exposed to attacks. New networking security features include the ability to drop TCP packets with SYN+FIN (NOTE: this breaks rfc1644 extensions (T/TCP)), restrict emission of RST, ignore incoming ICMP REDIRECT messages, and also set to log incoming ICMP REDIRECT messages. See rc.conf(5) for details on how to utilize these new features. 1.3. USERLAND CHANGES --------------------- Inetd has gained built-in support for ident and has a workaround for accidently blocking while accepting. ppp(8) now supports PPPoE (PPP over Ethernet) compliments of the pppoe netgraph node. It also supports PPP over ISDN, including standard ISDN link bonding. ppp(8) now uses the -nat command line argument and the ``nat'' command to control network address translation. The old [-]alias command still works, but produces a warning and will soon be removed. Additionally, ppp(8) now loads the tun module as required, allows a tun unit specification on the command line, supports a -foreground command line option, allows fast-queue configuration, provides a functional ``set autoload'' command (for on-demand multi-link ppp), allows GRE packet filtering and has had many bugs fixed. There's a new pppoed daemon for servicing PPP over Ethernet requests. Refer to rc.conf(5) and pppoed(8) for details. 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V is not yet supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. [ Note: There is work-in-progress to port the UltraStor driver to the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: Floppy tape interface (Colorado/Mountain/Insight) (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Adaptec Duralink PCI fast Ethernet adapters based on the Adaptec AIC-6915 fast Ethernet controller chip, including the following: ANA-62011 64-bit single port 10/100-BaseTX adapter ANA-62022 64-bit dual port 10/100-BaseTX adapter ANA-62044 64-bit quad port 10/100-BaseTX adapter ANA-69011 32-bit single port 10/100-BaseTX adapter ANA-62020 64-bit single port 100-BaseFX adapter Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: Alteon AceNIC (Tigon 1 and 2) 3Com 3c985-SX (Tigon 1 and 2) Netgear GA620 (Tigon 2) Silicon Graphics Gigabit Ethernet DEC/Compaq EtherWORKS 1000 NEC Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 fast Ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX Macronix 98713, 98713A, 98715, 98715A and 98725 fast Ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Macronix/Lite-On PNIC II LC82C115 fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX Version 2 Winbond W89C840F fast Ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast Ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE530TX Silicon Integrated Systems SiS 900 and SiS 7016 PCI fast ethernet NICs. Sundance Technologies ST201 PCI fast ethernet NICs including the following: D-Link DFE-550TX SysKonnect SK-984x PCI gigabit Ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port SK-9842 1000baseSX multi-mode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multi-mode fiber, dual port Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100-BaseTX Racore 8148 10-BaseT/100-BaseTX/100-BaseFX multi-personality ADMtek Inc. AL981-based PCI fast Ethernet NICs ADMtek Inc. AN985-based PCI fast Ethernet NICs ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 Ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B/905C PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980/3c980B Fast Etherlink XL server adapter 3Com 3cSOHO100-TX OfficeConnect adapter Toshiba Ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA PCMCIA Etherjet cards from IBM and National Semiconductor are also supported. 2.3 ATM ------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signaling Protocols - The ATM Forum UNI 3.1 signaling protocol - The ATM Forum UNI 3.0 signaling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signaling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multi-protocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.4. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multi-port serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and work-a-likes (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 3.4-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite F Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the following issues may affect you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. In the case of using sources, there are simply two targets you need to be aware of: The standard ``upgrade'' target, which will upgrade a 2.x or 3.0 system to 3.4 and the ``world'' target, which will take an already upgraded system and keep it in sync with whatever changes have happened since the initial upgrade. In the case of using the binary upgrade option, the system will go straight to 3.4/ELF but also populate the //lib/aout directories for backwards compatibility with older binaries. In either case, going to ELF will mean that you'll have somewhat smaller binaries and access to a lot more compiler goodies which have been already been ported to other ELF environments (our older and somewhat crufty a.out format being largely unsupported by most other software projects). Those who wish to retain access to the older a.out dynamic executables should be sure and install the compat22 distribution. Notice that the a.out libraries won't be accessible until the system is rebooted, which may cause trouble with certain a.out packages. Also, do not use install disks or sysinstall from previous versions, as version 3.1 introduced a new bootstrapping procedure, requiring new boot blocks to be installed (because of elf kernels), and version 3.2 has further modifications to the bootstrapping procedure. [ other important upgrading notes should go here] 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. Acknowledgments ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/3.5R/announce.adoc b/website/content/en/releases/3.5R/announce.adoc index 47905b82af..61e5fb8ae7 100644 --- a/website/content/en/releases/3.5R/announce.adoc +++ b/website/content/en/releases/3.5R/announce.adoc @@ -1,69 +1,69 @@ --- title: "FreeBSD 3.5 Announcement" sidenav: download ---- +--- = FreeBSD 3.5 Announcement *Date:* Sat, 24 Jun 2000 18:23:01 -0700 + *From:* "Jordan K. Hubbard" + **Subject:**FreeBSD 3.5 now available for x86 I'm pleased to announce the availability of FreeBSD 3.5-RELEASE, the very LAST in 3.x-STABLE branch technology. Following the release of FreeBSD 3.4 in December, 1999, many bugs were fixed, important security issues dealt with, and even a few new features added. Please see the link:../notes[release notes] for more information. FreeBSD 3.5-RELEASE is available at ftp://ftp.FreeBSD.org/pub/FreeBSD/[ftp.FreeBSD.org] and various https://www.FreeBSD.org/handbook/mirrors.html[FTP mirror sites] throughout the world. It can also be ordered on CD from http://www.FreeBSDMall.com/[The FreeBSD Mall], from where it will be shipping soon on a 4 CD set containing installation bits for x86 architecture, as well as a lot of other material of general interest to programmers and end-users alike We can't promise that all the mirror sites will carry the rather large installation (660MB) image, but it will at least be available from: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.5-install.iso along with the more traditional 3.5-RELEASE bits. If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi. The official FTP distribution site for FreeBSD is: ____ ftp://ftp.FreeBSD.org/pub/FreeBSD/ ____ Or via the WEB pages at: ____ http://www.FreeBSDMall.com/ and + http://www.freebsd.org/[http://www.freebsd.org] ____ And directly from BSDi: ____ BSDi + 4041 Pike Lane, #F + Concord CA, 94520 USA + Phone: +1 925 674-0783 + Fax: +1 925 674-0821 + Email: info@cdrom.com + WWW: http://www.cdrom.com/ ____ Additionally, FreeBSD is available via anonymous FTP from https://www.FreeBSD.org/handbook/mirrors.html[mirror sites] in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Elbonia, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp..freebsd.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also being made available at the following locations. Now that FreeBSD has export permission for crypto from the United States government, you can get it from these locations or from ftp.freebsd.org. South Africa:: ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt Thanks! - Jordan link:../../[Release Home] diff --git a/website/content/en/releases/3.5R/errata.adoc b/website/content/en/releases/3.5R/errata.adoc index 16cd161f0e..346777731e 100644 --- a/website/content/en/releases/3.5R/errata.adoc +++ b/website/content/en/releases/3.5R/errata.adoc @@ -1,40 +1,40 @@ --- title: "FreeBSD 3.5 Errata Notes" sidenav: download ---- +--- = FreeBSD 3.5 Errata Notes .... If you read no other documentation before installing this version of FreeBSD, you should at least by all means *READ THE ERRATA* for this release so that you don't stumble over problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of the errata are located at: 1. http://www.FreeBSD.org/releases/ 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases//ERRATA.TXT (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: freebsd-stable@FreeBSD.org For all CERT security advisories, see: ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/ For the latest security incident information. ---- Security Advisories: Current active security advisories for 3.5: ---- System Update Information: .... link:../../[Release Home] diff --git a/website/content/en/releases/3.5R/notes.adoc b/website/content/en/releases/3.5R/notes.adoc index 11ff16809b..d47f113293 100644 --- a/website/content/en/releases/3.5R/notes.adoc +++ b/website/content/en/releases/3.5R/notes.adoc @@ -1,650 +1,650 @@ --- title: "FreeBSD 3.5 Release Notes" sidenav: download ---- +--- = FreeBSD 3.5 Release Notes .... RELEASE NOTES - FREEBSD 3.5-RELEASE Welcome to 3.5-RELEASE, a full follow-on to 3.4-RELEASE which was shipped in December 1999. In the months since 3.4 was released, many bug fixes and general enhancements have been made to the system. Please see relevant details below. Any installation failures or crashes should be reported by using the send-pr command (those preferring a WEB based interface can also see http://www.FreeBSD.org/send-pr.html). For information about FreeBSD and the layout of the 3.5-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. Table of contents: ------------------ 1. What's new since 3.4-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 ATM 2.4 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgments 1. What's new since 3.4-RELEASE --------------------------------- 1.1. KERNEL CHANGES ------------------- The loader was substantially updated from -current Various bugs in the CAM driver fixed. oltr [Olicom NIC] driver updated. bktr(4) [Brooktree frame-grabber] driver updated. isp(4) [Compaq Qlogic] driver updated. sym(4) [NCR/Symbios SCSI controller] driver updated. A number of bugs in syscons(4) fixed. A number of bugs in vinum(4) fixed. Better support for LBA in wd(4) driver. Audio mixer(8) support substantially updated. Support for Microsoft Sound Source (MSS) audio devices. Support for more Linux system calls in the Linux compatability code. netgraph(4) updated: new node types and documentation added. Various bugs in msdosfs code fixed. 1.2. SECURITY CHANGES --------------------- Many small but meaningful changes, too many to list. See CVS repository for more details. Suffice it to say from a user perspective that "various things were tightened up." 1.3. USERLAND CHANGES --------------------- vinum(8) substantially updated. chmod(1) has gained a -v flag. See man page for details. df(1) gains new unit types. See man page for details. Various bugs in date(1), ed(1), ln(1), sh(1), camcontrol(8), vinum(8) and quite a number of other user commands fixed (see CVS for details :). groff(1), grep(1) texinfo(1) utilities updated. Quite a few enhancements to /etc from -current merged. Many doc bugs fixed in man pages. Thread locking functions added to dynamic linker (see dllockinit(3)). pthread_cancel(3) function added. ppp(8) has undergone some changes and bug fixes. One change in particular may disturb existing configurations. The # character is now treated as a comment start, irrespective of whether it's the first non-blank character on the line. Some ISPs allocate authnames with embedded # characters. These must now be escaped or quoted. picobsd support (/usr/src/release/picobsd) substantially updated. HTTP installation option added to system installer (sysinstall(8)). XFree86 updated from 3.3.5 to 3.3.6 (XFree86 4.0 not quite ready for prime-time yet). 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. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V is not yet supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (wcd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. [ Note: There is work-in-progress to port the UltraStor driver to the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: Floppy tape interface (Colorado/Mountain/Insight) (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Adaptec Duralink PCI fast Ethernet adapters based on the Adaptec AIC-6915 fast Ethernet controller chip, including the following: ANA-62011 64-bit single port 10/100-BaseTX adapter ANA-62022 64-bit dual port 10/100-BaseTX adapter ANA-62044 64-bit quad port 10/100-BaseTX adapter ANA-69011 32-bit single port 10/100-BaseTX adapter ANA-62020 64-bit single port 100-BaseFX adapter Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: Alteon AceNIC (Tigon 1 and 2) 3Com 3c985-SX (Tigon 1 and 2) Netgear GA620 (Tigon 2) Silicon Graphics Gigabit Ethernet DEC/Compaq EtherWORKS 1000 NEC Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 fast Ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX Macronix 98713, 98713A, 98715, 98715A and 98725 fast Ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Macronix/Lite-On PNIC II LC82C115 fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX Version 2 Winbond W89C840F fast Ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast Ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE530TX Silicon Integrated Systems SiS 900 and SiS 7016 PCI fast ethernet NICs. Sundance Technologies ST201 PCI fast ethernet NICs including the following: D-Link DFE-550TX SysKonnect SK-984x PCI gigabit Ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port SK-9842 1000baseSX multi-mode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multi-mode fiber, dual port Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100-BaseTX Racore 8148 10-BaseT/100-BaseTX/100-BaseFX multi-personality ADMtek Inc. AL981-based PCI fast Ethernet NICs ADMtek Inc. AN985-based PCI fast Ethernet NICs ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 Ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B/905C PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980/3c980B Fast Etherlink XL server adapter 3Com 3cSOHO100-TX OfficeConnect adapter Toshiba Ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA PCMCIA Etherjet cards from IBM and National Semiconductor are also supported. 2.3 ATM ------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signaling Protocols - The ATM Forum UNI 3.1 signaling protocol - The ATM Forum UNI 3.0 signaling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signaling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multi-protocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.4. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multi-port serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and work-a-likes (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. FreeBSD currently does NOT support IBM's microchannel (MCA) bus. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 3.5-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite F Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the following issues may affect you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. In the case of using sources, there are simply two targets you need to be aware of: The standard ``upgrade'' target, which will upgrade a 2.x or 3.0 system to 3.5 and the ``world'' target, which will take an already upgraded system and keep it in sync with whatever changes have happened since the initial upgrade. In the case of using the binary upgrade option, the system will go straight to 3.5/ELF but also populate the //lib/aout directories for backwards compatibility with older binaries. In either case, going to ELF will mean that you'll have somewhat smaller binaries and access to a lot more compiler goodies which have been already been ported to other ELF environments (our older and somewhat crufty a.out format being largely unsupported by most other software projects). Those who wish to retain access to the older a.out dynamic executables should be sure and install the compat22 distribution. Notice that the a.out libraries won't be accessible until the system is rebooted, which may cause trouble with certain a.out packages. Also, do not use install disks or sysinstall from previous versions, as version 3.1 introduced a new bootstrapping procedure, requiring new boot blocks to be installed (because of elf kernels), and version 3.2 has further modifications to the bootstrapping procedure. [ other important upgrading notes should go here] 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. Acknowledgments ------------------- FreeBSD represents the cumulative work of many dozens, if not hundreds, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/4.0R/announce.adoc b/website/content/en/releases/4.0R/announce.adoc index 921ae4e736..31202c6ab7 100644 --- a/website/content/en/releases/4.0R/announce.adoc +++ b/website/content/en/releases/4.0R/announce.adoc @@ -1,70 +1,70 @@ --- title: "FreeBSD 4.0 Announcement" sidenav: download ---- +--- = FreeBSD 4.0 Announcement *Date:* Tue, 14 Mar 2000 22:29:43 -0800 (PST) + *From:* "Jordan K. Hubbard" + *To:* announce@FreeBSD.org + *Subject:* 4.0-RELEASE is now available Well, it's a bit late and hopefully all the better for it, but here it is. It gives me great pleasure to announce the release of FreeBSD 4.0-RELEASE. This is our first release along the 4.x-stable (RELENG_4) branch and contains a number of significant advancements over FreeBSD 3.4. Please see the release notes for further information as the list of new features is too long to list here. FreeBSD 4.0-RELEASE is available from ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from http://www.freebsdmall.com/[The FreeBSD Mall], from where it will be shipping soon on a 4 CD set. There will also be two such sets available for 4.0, one containing installation bits for the x86 architecture (as well a lot of other material of general interest to programmers and end-users alike) and another for DEC Alpha architecture machines. As usual, disc #1 from Walnut Creek CDROM's official distribution (for both architectures) will also be available via anonymous FTP as soon as it's been compiled in its final form. Please monitor the master FTP site for details. We also can't promise that all the mirror sites will carry this rather large (660MB) installation image, but it will at least be available (once ready) from: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.0-install.iso + ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.0-install.iso These files allow one to install the base system and all of its most important add-ons from a single bootable image, one which can be written as a raw ISO 9660 image by most CD creator software. Even though we make our installation CDs freely available, we also hope that you'll continue to support the FreeBSD project by purchasing one of its official CD releases from the FreeBSD mall. A portion of each sale goes to support FreeBSD's development and general infrastructure and is thus highly appreciated. The official FTP distribution site for FreeBSD is: ftp://ftp.FreeBSD.org/pub/FreeBSD Or via the WEB pages at: http://www.freebsdmall.com/ + http://www.wccdrom.com/ And directly from Walnut Creek CDROM: .... Walnut Creek CDROM 4041 Pike Lane, #F Concord CA, 94520 USA Phone: +1 925 674-0783 Fax: +1 925 674-0821 Tech Support: +1 925 603-1234 Email: info@wccdrom.com WWW: http://www.wccdrom.com/ .... Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: [.kbd]#ftp://ftp..FreeBSD.org/pub/FreeBSD# Any additional mirror sites will be labeled ftp2, ftp3 and so on. The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also 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:: ftp://ftp.internat.FreeBSD.org/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.org/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.org/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt Thanks! - Jordan link:../../[Release Home] diff --git a/website/content/en/releases/4.0R/errata.adoc b/website/content/en/releases/4.0R/errata.adoc index 1bde448442..69e0d6fbe4 100644 --- a/website/content/en/releases/4.0R/errata.adoc +++ b/website/content/en/releases/4.0R/errata.adoc @@ -1,83 +1,83 @@ --- title: "FreeBSD 4.0 Errata Notes" sidenav: download ---- +--- = FreeBSD 4.0 Errata Notes .... If you read no other documentation before installing this version of FreeBSD, you should at least by all means *READ THE ERRATA* for this release so that you don't stumble over problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of the errata are located at: 1. http://www.FreeBSD.org/releases/ 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases//ERRATA.TXT (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: freebsd-current@FreeBSD.org For all FreeBSD security advisories, see: http://www.FreeBSD.org/security/ for the latest security incident information. ---- Security Advisories: Current active security advisories: None ---- System Update Information: The tcpdump binary in the bin distribution is erroneously linked against the libcrypto.so library, which is only found in the separate crypto distribution. Therefore, if you only install the bin distribution without the crypto distribution, tcpdump will not work as installed. Fix: Download a new tcpdump binary from the following location: http://people.FreeBSD.org/~kris/4.0R/i386/tcpdump (i386) http://people.FreeBSD.org/~kris/4.0R/alpha/tcpdump (alpha) The MD5 checksum of this file is: i386 version: MD5 (tcpdump) = 0b3d32b367e7312d546ccae8f1824391 alpha version: MD5 (tcpdump) = 2d113fa4c38c8a0299d558acb5c6ad57 To verify the checksum of your downloaded copy, perform the following command: /sbin/md5 /path/to/downloaded/tcpdump and compare with the above. o Tool source code not installed by install.sh (outside of sysinstall) If you are attempting to extract the full source code from the CDROM (outside of the sysinstall program), you will end up missing the tool source code. Fix: If you are running install.sh from /cdrom/src, you will need to also run: cat stool.?? | tar --unlink -xpzf - -C /usr/src to have the tool sources (/usr/src/tools hierarchy) installed. These are required to successfully build world. .... link:../../[Release Home] diff --git a/website/content/en/releases/4.0R/notes.adoc b/website/content/en/releases/4.0R/notes.adoc index 867855a109..233d5486cc 100644 --- a/website/content/en/releases/4.0R/notes.adoc +++ b/website/content/en/releases/4.0R/notes.adoc @@ -1,875 +1,875 @@ --- title: "FreeBSD 4.0 Release Notes" sidenav: download ---- +--- = FreeBSD 4.0 Release Notes .... RELEASE NOTES FreeBSD Release 4.0-RELEASE Any installation failures or crashes should be reported by using the send-pr command (those preferring a Web-based interface can also see http://www.FreeBSD.org/send-pr.html). For information about FreeBSD and the layout of the 4.0-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. For the latest of these 4.0-STABLE snapshots, you should always see: ftp://current.FreeBSD.org/pub/FreeBSD If you wish to get the latest post-3.X-RELEASE technology. Table of contents: ------------------ 1. What's new since the 3.1/4.0 branch 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 ATM 2.4 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgements 1. What's new since the 3.1/4.0 branch -------------------------------------- All changes described here are unique to the 4.0 branch unless specifically marked as [MERGED] features. 1.1. KERNEL CHANGES ------------------- NFS has been immensely improved with bug fixes and performance tuning. Support for more than 32 signals has been added. POSIX 1003.1 conformant SA_SIGINFO signal handlers are now supported. SIGFPE signal handlers (both SA_SIGINFO and traditional BSD handlers) now get meaningful error codes describing the kind of error. See sigaction(2). IA32 hardware debug registers are now supported. See ptrace(2) and procfs(5). Jail(8) aware sysctl(8) variables have been added for Linux mode. A large number of bug fixes and performance improvements have been made to the VM system, including and most especially to mmap() and related functions. The MAP_NOSYNC option has been added to better support the use of shared files as an IPC mechanism. The VM system's swapper has been completely rewritten and performance has been greatly enhanced, especially when swapping over NFS. An emulator for SVR4 binaries has been added. Support has been added for direct access to NTFS filesystems. Support for the NWFS filesystem and NetWare client connections has been added. A variety of NetWare related tools, such as ipxping and ncprint, have been added in ports/net/ncplib. A new ATA/ATAPI driver has been implemented. The aim of this new subsystem is to maximise performance on modern ATA/ATAPI based systems. The "ata" driver supports all major chipsets including those used on PCI card based controllers like the Promise and the Abit/SIIG. There is support for busmaster DMA transfers upto and including the new ATA/66 mode. The 'ata' driver automatically setup the hardware for the maximum possible transfer mode to maximise system throughput. Supported devices are all ATA compliant disks and ATAPI CDROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, LS120, ZIP and tape drives. The ata driver also support PCCARD ATA devices. The 'ata' driver also sports error handling and timeout code, to avoid the problems of "hung" ATA/ATAPI devices. A new utility 'burncd' has been written to facilitate easy control of ATAPI CD-R and CD-RW drives, and allows burning of CD-R/RW media in a wide selction of formats, including multisession mode. Driver support has been added for PCI gigabit ethernet adapters based on the Alteon Networks Tigon 1 and Tigon 2 chipsets, including the Alteon AceNIC, 3Com 3c985 and Netgear GA620. [MERGED] Driver support has been added for IEEE 802.11 PCMCIA wireless network adapters based on the Lucent Hermes chipset, including the Lucent WaveLAN/IEEE 802.11, the Cabletron RoamAbout and Melco Aireconnect. Both 2Mbps and 6Mbps Turbo adapters are supported. [MERGED] Driver support has been added for PCI fast ethernet cards based on the ADMtek Inc. AL981 Comet chipset. [MERGED] Driver support has been added for PCI fast ethernet cards based on the ADMtek Inc. AL985 Centaur chipset. [MERGED] Support has been added for the Rise mP6 processor. [MERGED] Driver support has been added for SysKonnect SK-984x PCI gigabit ethernet adapters. [MERGED] Driver support has been added for Adaptec Duralink PCI ethernet adapters based on the Adaptec AIC-6915 fast ethernet controller. [MERGED] Driver support has been added for PCI fast ethernet adapters based on the Sundance Technologies ST201 controller, including the D-Link DFE-550TX. [MERGED] Driver support has been added for the 3Com 3c905C-TX. [MERGED] Driver support has been added for SMC SMC9xxx-based Ethernet adapters. Several IPFW improvements including stateful inspection, user- and group-based firewalling, dynamic logging with arbitrary logging limits, probabilistic rule match. [MERGED] IPv6 IPFW has been imported from the KAME project. The "dummynet" traffic shaper now handles efficiently thousands of independent queues. [MERGED] Several fixes to bridging, which now supports clusters of interfaces with bridging being done independently within each cluster. [MERGED] The top-level syslog(3) category "security" has been added, and IPFW now uses syslog(3) to log all messages to /var/log/security. Driver support has been added for PCI fast ethernet adapters based on the Silicon Integrated Systems SiS 900 and SiS 7016 ethernet controllers. [MERGED] Driver support has been added for PCI fast ethernet adapters based on the Davicom DM9100 and DM9102 ethernet controllers, including the Jaton Corporation XpressNet. Support has been added for blocking incoming ICMP redirects, outgoing RST frames and incoming SYN|FIN frames in order to lessen or nullify the impact of certain kinds of DoS attacks. [MERGED] Support has been added for forwarding IP datagrams without inspecting or decreasing the TTL in order to make gateways and firewalls less visible and therefore less exposed to attacks. [MERGED] The old `sd' (SCSI Disk) backwards compatibility support has been removed. Any usage of "/dev/sd*" in ``/etc/fstab'' must be replaced by "/dev/da*". In addition, any useage of "/dev/*sd*" in scripts need to be changed. Even if you have old `sd' device entries in /dev, they will no longer work. The `al' `ax' `dm' `pn' and `mx' drivers have been removed and replaced with a single driver (`dc') in order to reduce code duplication. The new driver handles all chipsets supported by the older drivers, and it offers improved support for 10/100 cards based on the DEC/Intel 21143. Driver support has been added for the 3Com 3c450-TX HomeConnect PCI ethernet NIC. [MERGED] Driver support has been added for USB ethernet adapters based on the ADMtek AN986 Pegasus chip, including the LinkSys USB100TX, the Billionton USB100, the Melco Inc. LU-ATX, the D-Link 650TX and the SMC-2202USB. Driver support has been added for USB ethernet adapters based on the Kawasaki LSI KL5KUSB101B chip, including the LinkSys USB10T, the Peracom USB Ethernet Adapter, the 3Com 3c19250, the Entrega NET-USB-E45, the ADS Technologies USB-10BT, the ATen UC10T, the Netgear EA101, the D-Link DSB-650, and the SMC 2102USB and 2104USB. IPfilter version 3.3.8 has been integrated. Driver support has been added for USB ethernet adapters based on the CATC USB-EL1210A chip, including the CATC Netmate and Netmate II, and the Belkin F5U111. Driver support has been added for Aironet 4500/4800 802.11 wireless adapters. This includes PCMCIA, PCI and ISA models. IPv6 support has been imported from the KAME project. This includes the kernel IPv6 protocol stack (sys/netinet6), TCP IPv6 support, configurable IPv6 and IPv4 tunneling over IPv6 or IPv4, and IPv6 TCP to IPv4 TCP translation gateway support. Protocol-independent name resolution functions have been added to libc (getaddrinfo, getnameinfo, etc). Floating point exceptions for new processes (devide-by-zero, under/overflow, invalid range etc.) are now disabled by default. Use fpsetmask(3) to reenable those you need. Note that integer device-by-zero is not covered by the FPU and will still trap after this change. Also note that conversion of float/double to integer where the float variable is too big now doesn't trap as well (it can't be separated from other operations we want masked). 1.2. SECURITY FIXES ------------------- Numerous security enhancements and fixes have been applied during the course of development of FreeBSD 4.0. Most of these have also been backported to the 3.X-STABLE series. A new jail(2) system call and admin command (jail(8)) have been added for additional flexibility in creating secure process execution environments. OpenSSL v0.9.4 (a general-purpose cryptography and SSL2/3/TLSv1 toolkit) has been integrated with the base system. In the future this will be used to provide strong cryptography for FreeBSD utilities out-of-the-box. OpenSSH 1.2 has been integrated with the base system. OpenSSH is a free (BSD-licensed), full-featured implementation of the SSH v1 protocol, which is completely interoperable with other SSH v1 clients and servers, such as the /usr/ports/security/ssh port. OpenSSH provides all of the features of this port - in fact it is based on an older release before the software became restrictively licensed. FreeBSD 4.0 provides SSH client/server functionality out-of-the-box if you choose to install the 'DES' cryptography distribution in sysinstall. Telnet has a new encrypted authentication mechanism called SRA. SRA uses a Diffie-Hellmen exchange to establish a session key, then uses that to DES encrypt the username and password. As a side effect the session key is used to DES encrypt the session. SRA is vulnerable to man-in-the-middle attacks, the DH parameters are on the small side, and DES is showing its age, but the benefits are that it requires absolutely no administrative changes to the machine to work, and is at the very least a step up from plaintext. To use it, you need to either use "telnet -ax" or set up a .telnetrc to enable it by default. IPsec support has been imported from the KAME project. This includes IPsec tunnel mode to implement a Virtual Private Network via a security gateway, and IPsec transport mode to achieve secure socket-level communication. Also, kernel-internal crypto code has been imported to sys/crypto, and IPsec support has been added to the following userland applications: sbin/ping, usr.sbin/inetd, usr.sbin/rrenumd, usr.sbin/traceroute6, usr.sbin/rtadvd, usr.sbin/setkey 1.3. USERLAND CHANGES --------------------- The base C/C++ compiler has been upgraded from GCC 2.7.2 to GCC 2.95.2. This gives users full ISO C++ support, and preliminary C9x support. Various changes has been made to /bin/sh to improve POSIX 1003.2 conformance, especially for scripting. The f77 emulation via f2c has been replaced by a native F77 compiler. The timezone database has been updated to catch all of the recent changes in Europe, the former Soviet Union, and Central and South America. The timezone data files now contain a magic number allowing for easy identification. Groff/troff/eqn has been updated to version 1.15. Gdb has been updated to version 4.18. Numerous fixes have been applied to improve the security of FreeBSD code as part of the FreeBSD Auditing Project. FreeBSD's threads library, libc_r, has had many features and performance improvements added, which makes it almost completely POSIX-compliant. In addition, Linux's kernel-supported LinuxThreads library is now available as a port (ports/devel/linuxthreads), which can be used for native FreeBSD programs. The following dedicated IPv6 applications have been added: sbin/ping6, sbin/rtsol, usr.sbin/gifconfig, usr.sbin/ifmcstat, usr.sbin/pim6dd, usr.sbin/pim6sd, usr.sbin/prefix, usr.sbin/rip6query, usr.sbin/route6d, usr.sbin/rrenumd, usr.sbin/rtadvd, usr.sbin/rtsold, usr.sbin/traceroute6 The following applications have been updated to support IPv6: usr.bin/netstat, usr.bin/fstat, usr.bin/sockstat, usr.sbin/tcpdchk, usr.sbin/tcpdump, usr.sbin/trpt, libexec/ftpd, libexec/rlogind, libexec/rshd, libexec/telnetd Many ports have been updated to support IPv6. See the 'ipv6' virtual ports category for a list. Sysinstall enables PC-card controllers and pccardd(8) for PC-card installation media. 2. Supported Configurations --------------------------- FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA 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 peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 164x series MCA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F Microchannel (MCA) bus adapters are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V is not yet supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (acd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. [ Note: There is work-in-progress to port the UltraStor driver to the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Adaptec Duralink PCI fast ethernet adapters based on the Adaptec AIC-6915 fast ethernet controller chip, including the following: ANA-62011 64-bit single port 10/100baseTX adapter ANA-62022 64-bit dual port 10/100baseTX adapter ANA-62044 64-bit quad port 10/100baseTX adapter ANA-69011 32-bit single port 10/100baseTX adapter ANA-62020 64-bit single port 100baseFX adapter Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI gigabit ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: Alteon AceNIC (Tigon 1 and 2) 3Com 3c985-SX (Tigon 1 and 2) Netgear GA620 (Tigon 2) Silicon Graphics Gigabit Ethernet DEC/Compaq EtherWORKS 1000 NEC Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 fast ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC fast ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX Macronix 98713, 98713A, 98715, 98715A and 98725 fast ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Macronix/Lite-On PNIC II LC82C115 fast ethernet NICs including the following: LinkSys EtherFast LNE100TX Version 2 Winbond W89C840F fast ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE-530TX AOpen/Acer ALN-320 Silicon Integrated Systems SiS 900 and SiS 7016 PCI fast ethernet NICs Sundance Technologies ST201 PCI fast ethernet NICs including the following: D-Link DFE-550TX SysKonnect SK-984x PCI gigabit ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port SK-9842 1000baseSX multimode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multimode fiber, dual port Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100baseTX Racore 8148 10baseT/100baseTX/100baseFX multi-personality ADMtek Inc. AL981-based PCI fast ethernet NICs ADMtek Inc. AN985-based PCI fast ethernet NICs ADMtek Inc. AN986-based USB ethernet NICs including the following: LinkSys USB100TX Billionton USB100 Melco Inc. LU-ATX D-Link DSB-650TX SMC 2202USB CATC USB-EL1210A-based USB ethernet NICs including the following: CATC Netmate CATC Netmate II Belkin F5U111 Kawasaki LSI KU5KUSB101B-based USB ethernet NICs including the following: LinkSys USB10T Entrega NET-USB-E45 Peracom USB Ethernet Adapter 3Com 3c19250 ADS Technologies USB-10BT ATen UC10T Netgear EA101 D-Link DSB-650 SMC 2102USB SMC 2104USB Corega USB-T ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) DEC FDDI (DEFPA/DEFEA) NICs Davicom DM9100 and DM9102 PCI fast ethernet NICs, including the following: Jaton Corporation XpressNet Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Intel InBusiness 10/100 PCI Network Adapter Intel PRO/100+ Management Adapter Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980/3c980B Fast Etherlink XL server adapter 3Com 3cSOHO100-TX OfficeConnect adapter Toshiba ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards, including the following: AR-P500 Ethernet card Accton EN2212/EN2216/UE2216(OEM) Allied Telesis CentreCOM LA100-PCM_V2 AmbiCom 10BaseT card BayNetworks NETGEAR FA410TXC Fast Ethernet CNet BC40 adapter COREGA Ether PCC-T/EtherII PCC-T Compex Net-A adapter CyQ've ELA-010 D-Link DE-650/660 Danpex EN-6200P2 IO DATA PCLATE IBM Creditcard Ethernet I/II IC-CARD Ethernet/IC-CARD+ Ethernet Linksys EC2T/PCMPC100 Melco LPC-T NDC Ethernet Instant-Link National Semiconductor InfoMover NE4100 Network Everywhere Ethernet 10BaseT PC Card Planex FNW-3600-T Socket LP-E Surecom EtherPerfect EP-427 Telecom Device SuperSocket RE450T Megahertz X-Jack Ethernet PC-Card CC-10BT 2.3 ATM ------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signalling Protocols - The ATM Forum UNI 3.1 signalling protocol - The ATM Forum UNI 3.0 signalling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signalling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.4. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco Airconnect). Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, PCI and ISA adapters are all supported. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 4.0-RELEASE and 3.X-RELEASE CDs may be ordered on CDROM from: Walnut Creek CDROM 4041 Pike Lane, Suite F Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 3.0 and some of the following issues may affect you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. Please read the UPGRADE.TXT file for more information. 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html Justin M. Seger for almost single-handedly converting the ports collection to ELF. Doug Rabson and John Birrell for making FreeBSD/alpha happen and to the NetBSD project for substantial indirect aid. Peter Wemm for the new kernel module system (with substantial aid from Doug Rabson). And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/4.1.1R/announce.adoc b/website/content/en/releases/4.1.1R/announce.adoc index ef3cd2dc10..1d8b11392d 100644 --- a/website/content/en/releases/4.1.1R/announce.adoc +++ b/website/content/en/releases/4.1.1R/announce.adoc @@ -1,43 +1,43 @@ --- title: "FreeBSD 4.1.1 Announcement" sidenav: download ---- +--- = FreeBSD 4.1.1 Announcement *Date:* Wed, 27 Sep 2000 00:07:50 -070 + *From:* "Jordan K. Hubbard" + *To:* announce@FreeBSD.org + *Subject:* 4.1.1-RELEASE now available from ftp.freebsd.org As always, I'm pleased to announce the availability of FreeBSD 4.1.1-RELEASE, a point release update for 4.1-RELEASE and, of course, the very latest in 4.x-STABLE branch technology. Since 4.1-RELEASE was produced in August 2000, RSA released their code into the public domain and a number of other security enhancements were made possible through the FreeBSD project's permission to export cryptographic code from the United States. These changes are fully reflected in 4.1.1-RELEASE, making it one of the most secure "out of the box" releases of FreeBSD we've ever done. We also took the opportunity to include support for new features like IDE ATA100 support, drivers for additional Gigabit ethernet cards and hardware watchpoints in gdb. Please see the release notes for more information. The 4.1.1-RELEASE is available right now for the ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.1.1-RELEASE[i386] architecture (alpha to follow in several days) in "FTP installable" and ISO image form. For the appropriate bits, please see: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.1.1-RELEASE/ + ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.1.1-install.iso When the Alpha release follows in several days, it will be available from: ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/4.1.1-RELEASE/ + ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.1.1-install.iso Please watch the mailto:alpha@FreeBSD.org[alpha@freebsd.org] mailing list for an announcement. *IMPORTANT NOTE:* This is a network only point release and will not be made generally available for sale on CDROM, at least not from BSDi or anyone else we currently have knowledge of. The next official CD release will be FreeBSD 4.2-RELEASE, still scheduled for mid-November 2000. FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, Elbonia, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: .... ftp://ftp..freebsd.org/pub/FreeBSD .... Any additional mirror sites will be labeled ftp2, ftp3 and so on. Thanks! - Jordan diff --git a/website/content/en/releases/4.1.1R/errata.adoc b/website/content/en/releases/4.1.1R/errata.adoc index 1f93d650a3..cf00847f94 100644 --- a/website/content/en/releases/4.1.1R/errata.adoc +++ b/website/content/en/releases/4.1.1R/errata.adoc @@ -1,40 +1,40 @@ --- title: "FreeBSD 4.1.1 Errata Notes" sidenav: download ---- +--- = FreeBSD 4.1.1 Errata Notes .... If you read no other documentation before installing this version of FreeBSD, you should at least by all means *READ THE ERRATA* for this release so that you don't stumble over problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of the errata are located at: 1. http://www.FreeBSD.org/releases/ 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases//ERRATA.TXT (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: freebsd-current@FreeBSD.org For all FreeBSD security advisories, see: http://www.FreeBSD.org/security/ for the latest security incident information. ---- Security Advisories: Current active security advisories: None ---- System Update Information: .... link:../../[Release Home] diff --git a/website/content/en/releases/4.1.1R/notes.adoc b/website/content/en/releases/4.1.1R/notes.adoc index b0f0d05303..7e4e8c6fd6 100644 --- a/website/content/en/releases/4.1.1R/notes.adoc +++ b/website/content/en/releases/4.1.1R/notes.adoc @@ -1,730 +1,730 @@ --- title: "FreeBSD 4.1.1 Release Notes" sidenav: download ---- +--- = FreeBSD 4.1.1 Release Notes .... === Platform specifics for i386 RELEASE NOTES FreeBSD 4.1.1-RELEASE Any installation failures or crashes should be reported by using the send-pr command (those preferring a Web-based interface can also see http://www.FreeBSD.org/send-pr.html). For information about FreeBSD and the layout of the 4.1.1-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. For the latest of these 4.1.1-stable snapshots, you should always see: ftp://releng4.FreeBSD.org/pub/FreeBSD Table of contents: ------------------ 1. What's new since 4.1-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 FDDI 2.4 ATM 2.5 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgements 1. What's new since 4.1-RELEASE -------------------------------------- 1.1. KERNEL CHANGES ------------------- The tap driver, a virtual Ethernet device driver for bridged configurations, has been added. accept_filters, a kernel feature to reduce overheads when accepting and reading new connections on listening sockets, has been added. POSIX.1b Shared Memory Objects are now supported. The implementation uses regular files, but automatically enables the MAP_NOSYNC flag when they are mmap(2)ed. The ata(4) driver now has support for ATA100 controllers. The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit Ethernet and Netgear GA620T 1000baseT Gigabit Ethernet cards. The ng_bridge(4) node type has been added to the netgraph subsystem. Miscellaneous bug fixes and enhancements have also been made. 1.2. SECURITY FIXES ------------------- 1.3. USERLAND CHANGES --------------------- GDB now supports hardware watchpoints. sendmail upgraded from version 8.9.3 to version 8.11.0. Important changes include: new default file locations (see /usr/src/contrib/sendmail/cf/README); newaliases is limited to root and trusted users; and the MSA port (587) is turned on by default. See /usr/src/contrib/sendmail/RELEASE_NOTES for more information. routed(8) has been updated to version 2.22. The truncate(1) utility, which truncates or extends the length of files, has been added. syslogd(8) can take a -n option to disable DNS queries for every request. kenv(1), a command to dump the kernel environment, has been added. The behavior of periodic(8) is now controlled by /etc/defaults/periodic.conf and /etc/periodic.conf. logger(1) can now send messages directly to a remote syslog. OpenSSL has been upgraded to 0.9.5a, which includes numerous bugfixes and enhancements. finger(1) now has the ability to support fingering aliases, via the finger.conf(5) file. RSA Security has waived all patent rights to the RSA algorithm (two weeks before the patent was due to expire). As a result, the native OpenSSL implementation of the RSA algorithm is now activated by default, and the rsaref port and librsaUSA are no longer required for USA residents. sshd now enabled by default on new installs. The xl(4) driver now supports the 3Com 3C556 and 3C556B MiniPCI adapters used on some laptops. killall(1) is now a C program, rather than a Perl script. As a result, killall's -m option now uses the regular expression syntax of regex(3), rather than that of perl(1). boot98cfg(8), a PC-98 boot manager installation and configuration utility, has been added. Binutils have been upgraded to 2.10.0. libreadline has been upgraded to 4.1. The ifconfig(8) command can set the link-layer address of an interface. bktr(4) driver update to 2.1.5. New tuner types have been added, and improvememts to the KLD module and to memory allocation have been made. 2. Supported Configurations --------------------------- FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA 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 peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 164x series MCA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F Microchannel (MCA) bus adapters are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. DPT SmartRAID V/VI and Adaptec SCSI RAID 2100, 3200, and 3400 cards are supported. AMI MegaRAID Express and Enterprise family RAID controllers: MegaRAID 418 MegaRAID Enterprise 1200 (428) MegaRAID Enterprise 1300 MegaRAID Enterprise 1400 MegaRAID Enterprise 1500 MegaRAID Elite 1500 MegaRAID Express 200 MegaRAID Express 300 Dell PERC Dell PERC 2/SC Dell PERC 2/DC Some HP NetRAID controllers are OEM versions of AMI designs, and these are also supported. Booting from these controllers is supported. Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware: DAC960P DAC960PD DAC960PDU DAC960PL DAC960PJ DAC960PG AcceleRAID 150 AcceleRAID 250 eXtremeRAID 1100 Booting from these controllers is supported. EISA adapters are not supported. 3ware Escalade ATA RAID controllers. All members of the 5000 and 6000 series are supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (acd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. [ Note: There is work-in-progress to port the UltraStor driver to the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast Ethernet controller chip, including the following: ANA-62011 64-bit single port 10/100baseTX adapter ANA-62022 64-bit dual port 10/100baseTX adapter ANA-62044 64-bit quad port 10/100baseTX adapter ANA-69011 32-bit single port 10/100baseTX adapter ANA-62020 64-bit single port 100baseFX adapter Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: 3Com 3c985-SX (Tigon 1 and 2) Alteon AceNIC 1000baseSX (Tigon 1 and 2) Alteon AceNIC 1000baseT (Tigon 2) DEC/Compaq EtherWORKS 1000 Farallon PN9000SX NEC Gigabit Ethernet Netgear GA620 (Tigon 2) Netgear GA620T (Tigon 2, 1000baseT) Silicon Graphics Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 Fast Ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX Version 2 Winbond W89C840F Fast Ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE-530TX AOpen/Acer ALN-320 Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs Sundance Technologies ST201 PCI Fast Ethernet NICs including the following: D-Link DFE-550TX SysKonnect SK-984x PCI Gigabit Ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port SK-9842 1000baseSX multimode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multimode fiber, dual port Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100baseTX Racore 8148 10baseT/100baseTX/100baseFX multi-personality ADMtek Inc. AL981-based PCI Fast Ethernet NICs ADMtek Inc. AN985-based PCI Fast Ethernet NICs ADMtek Inc. AN986-based USB Ethernet NICs including the following: LinkSys USB100TX Billionton USB100 Melco Inc. LU-ATX D-Link DSB-650TX SMC 2202USB CATC USB-EL1210A-based USB Ethernet NICs including the following: CATC Netmate CATC Netmate II Belkin F5U111 Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including the following: LinkSys USB10T Entrega NET-USB-E45 Peracom USB Ethernet Adapter 3Com 3c19250 ADS Technologies USB-10BT ATen UC10T Netgear EA101 D-Link DSB-650 SMC 2102USB SMC 2104USB Corega USB-T ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the following: Jaton Corporation XpressNet Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Intel InBusiness 10/100 PCI Network Adapter Intel PRO/100+ Management Adapter Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 Ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI, 3C556/556B MiniPCI, and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980/3c980B Fast Etherlink XL server adapter 3Com 3cSOHO100-TX OfficeConnect adapter Toshiba Ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards, including the following: AR-P500 Ethernet card Accton EN2212/EN2216/UE2216(OEM) Allied Telesis CentreCOM LA100-PCM_V2 AmbiCom 10BaseT card BayNetworks NETGEAR FA410TXC Fast Ethernet CNet BC40 adapter COREGA Ether PCC-T/EtherII PCC-T Compex Net-A adapter CyQ've ELA-010 D-Link DE-650/660 Danpex EN-6200P2 IO DATA PCLATE IBM Creditcard Ethernet I/II IC-CARD Ethernet/IC-CARD+ Ethernet Linksys EC2T/PCMPC100 Melco LPC-T NDC Ethernet Instant-Link National Semiconductor InfoMover NE4100 Network Everywhere Ethernet 10BaseT PC Card Planex FNW-3600-T Socket LP-E Surecom EtherPerfect EP-427 Telecom Device SuperSocket RE450T Megahertz X-Jack Ethernet PC-Card CC-10BT 2.3. FDDI --------- DEC FDDI (DEFPA/DEFEA) NICs 2.4. ATM -------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signalling Protocols - The ATM Forum UNI 3.1 signalling protocol - The ATM Forum UNI 3.0 signalling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signalling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.5. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco Airconnect). Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, PCI and ISA adapters are all supported. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 3.0 and there may be some issues affecting you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. Please read the UPGRADE.TXT file for more information, preferably before beginning an upgrade. 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org If you're tracking the -stable development efforts, you should definitely join the -stable mailing list, in order to keep abreast of recent developments and changes that may affect the way you use and maintain the system: freebsd-stable@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html Justin M. Seger for almost single-handedly converting the ports collection to ELF. Doug Rabson and John Birrell for making FreeBSD/alpha happen and to the NetBSD project for substantial indirect aid. Peter Wemm for the new kernel module system (with substantial aid from Doug Rabson). And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/4.1R/announce.adoc b/website/content/en/releases/4.1R/announce.adoc index f568fcb902..82f126e810 100644 --- a/website/content/en/releases/4.1R/announce.adoc +++ b/website/content/en/releases/4.1R/announce.adoc @@ -1,58 +1,58 @@ --- title: "FreeBSD 4.1 Announcement" sidenav: download ---- +--- = FreeBSD 4.1 Announcement *Date:* Thu, 27 Jul 2000 05:17:09 -0700 + *From:* "Jordan K. Hubbard" + *To:* announce@FreeBSD.org + *Subject:* 4.1-RELEASE now available from ftp.freebsd.org I'm very pleased to announce the availability of FreeBSD 4.1-RELEASE, the very latest in 4.x-STABLE branch technology. Following the release of FreeBSD 4.0 in March, 2000, many bugs were fixed, important security issues dealt with, and quite a few new features added. Please see the release notes for more information. The 4.1-RELEASE is available for ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.1-RELEASE[i386] and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/4.1-RELEASE[alpha] right now and can be installed directly over the net using the boot floppies or copied to a local NFS/ftp server. ISO images will also be provided later (see below). ISO (CD) Images + --------------- + ISO images of the installation CD will be made available by August 1st 2000, after the bits have undergone a bit more integration testing. This additional delay is necessary given that the ISO images are so large (~650MB each) and are not something which many people want to transfer more than once. A follow-up announcement will be sent once the ISO images are in place, so please don't send me email asking where they are or when they'll be ready. When they're ready, they'll be uploaded and an announcement will be sent out. We also can't promise that all the mirror sites will carry these large ISO images, but they will at least be available from: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.1-install.iso + ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.1-install.iso If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISOs, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi. FreeBSD 4.1-RELEASE can be ordered as a 4 CD set from http://www.freebsdmall.com[The FreeBSD Mall] from where it will soon be shipping. Each CD sets contains the FreeBSD installation and application package bits for either the x86 or the alpha architecture (each architecture has its own CD set). For a set of distfiles used to build ports in the ports collection, please see also the FreeBSD Toolkit, a 6 CD set containing all such extra bits which we can no longer fit on the 4 CD sets. You can also order by phone, postal mail, FAX or email at: .... BSDi 4041 Pike Lane, #F Concord CA, 94520 USA Phone: +1 925 674-0783 Fax: +1 925 674-0821 Tech Support: +1 925 603-1234 Email: orders@wccdrom.com WWW: http://www.wccdrom.com/ .... FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Austria, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, Elbonia, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :). Before trying the central FTP site, please check your regional mirror(s) first by going to: [.kbd]#ftp://ftp..FreeBSD.org/pub/FreeBSD# Any additional mirror sites will be labeled ftp2, ftp3 and so on. The latest versions of export-restricted code for FreeBSD are also being made available at the following locations. Now that FreeBSD has export permission for crypto from the United States government, you can get it from the following locations or from ftp.freebsd.org: South Africa:: ftp://ftp.internat.FreeBSD.org/pub/FreeBSD + ftp://ftp2.internat.FreeBSD.org/pub/FreeBSD Brazil:: ftp://ftp.br.FreeBSD.org/pub/FreeBSD Finland:: ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt Thanks! - Jordan diff --git a/website/content/en/releases/4.1R/errata.adoc b/website/content/en/releases/4.1R/errata.adoc index 5100f17bfd..2a73be27be 100644 --- a/website/content/en/releases/4.1R/errata.adoc +++ b/website/content/en/releases/4.1R/errata.adoc @@ -1,69 +1,69 @@ --- title: "FreeBSD 4.1 Errata Notes" sidenav: download ---- +--- = FreeBSD 4.1 Errata Notes .... If you read no other documentation before installing this version of FreeBSD, you should at least by all means *READ THE ERRATA* for this release so that you don't stumble over problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of the errata are located at: 1. http://www.FreeBSD.org/releases/ 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases//ERRATA.TXT (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: freebsd-current@FreeBSD.org For all FreeBSD security advisories, see: http://www.FreeBSD.org/security/ for the latest security incident information. ---- Security Advisories: Current active security advisories: None ---- System Update Information: The FreeBSD Boot Manager (boot0) has a bug that causes it to hang the machine during boot with no screen output. Fix: Boot your machine into FreeBSD either via a boot floppy or a CD-ROM, then download a new boot0 binary from the following location: http://people.FreeBSD.org/~jhb/4.1R/i386/boot0 Once you have downloaded the new binary, install it with the boot0cfg command onto your hard disk. For example, if you have boot0 on disk ad0, you would run the following command: /usr/sbin/boot0cfg -B -b /path/to/downloaded/boot0 ad0 You may also use cvsup to update your source tree and build the new boot0 binary from source. You will need version 1.14.2.3 of src/sys/boot/i386/boot0/boot0.s or newer. The MD5 checksum of this file is: MD5 (boot0) = 8770a386dba44f0aa06b15db72c1f624 To verify the checksum of your downloaded copy, perform the following command: /sbin/md5 /path/to/downloaded/boot0 and compare with the above. .... link:../../[Release Home] diff --git a/website/content/en/releases/4.1R/notes.adoc b/website/content/en/releases/4.1R/notes.adoc index 3cdaf52438..87f222dd99 100644 --- a/website/content/en/releases/4.1R/notes.adoc +++ b/website/content/en/releases/4.1R/notes.adoc @@ -1,780 +1,780 @@ --- title: "FreeBSD 4.1 Release Notes" sidenav: download ---- +--- = FreeBSD 4.1 Release Notes .... RELEASE NOTES FreeBSD 4.1-RELEASE Any installation failures or crashes should be reported by using the send-pr command (those preferring a Web-based interface can also see http://www.FreeBSD.org/send-pr.html). For information about FreeBSD and the layout of the 4.1-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. For the latest 4.1-stable snapshots (post-4.1 snaps), you should always see: ftp://releng4.FreeBSD.org/pub/FreeBSD Table of contents: ------------------ 1. What's new since 4.0-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 FDDI 2.4 ATM 2.5 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgements 1. What's new since 4.0-RELEASE -------------------------------------- 1.1. KERNEL CHANGES ------------------- FreeBSD 4.1-RELEASE contains updated code from the KAME project (http://www.kame.net) including the following features: * Significantly improved IPSEC functionality. In particular, IPSEC security associations must no longer be manually keyed: the new code supports racoon, the KAME IKE daemon, which is located in /usr/ports/security/racoon. Racoon has been shown to interoperate well with other vendor IKE systems, meaning that FreeBSD 4.1 can be used in a heterogeneous IPSEC environment. However, racoon *is* still a work in progress, meaning that there may still be bugs, configuration syntax changes, etc. * About 9 months of fixes and improvements to the IPv6 code relative to what was in 4.0-RELEASE. * FreeBSD 4.1 can now be installed on an IPv6-only network - this will be the first release of FreeBSD that never needs to operate using IPv4 at all! ftp7.jp.FreeBSD.org (Listed as Japan #7 in sysinstall) is an IPv6-reachable mirror site for installation and package-fetching. * The ALTQ traffic-shaping system has not yet been merged - it will hopefully be added before the release of 4.2. The more experimental KAME code has also not been merged. If you need those features, consider using the 4.1-RELEASE+KAME snapshots from ftp://ftp.kame.net which will become available after 4.1-RELEASE. * KNOWN ISSUES: NFS mounts over IPSEC do not seem to work reliably in all cases - mount hangs and possible data corruption have been observed. A new event notification facility called kqueue was added to the FreeBSD kernel. This is a new interface which is able to replace poll/select, offering improved performance, as well as the ability to report many different types of events. Support for monitoring changes in sockets, pipes, fifos, and files are present, as well as for signals and processes. Support for Intel's Wired for Management 2.0 (PXE) was added to the FreeBSD boot loader. Due to API differences, the older PXE versions are not supported. This allow network booting using DHCP. For the alpha release of FreeBSD, the following specifics also apply: FreeBSD/alpha now posseses a loader with FICL (Forth support) builtin. Parallel ports are now supported. Support for multiple new Alpha system types has been added. Please check HARDWARE.TXT for details. AlphaServer 4100 (Rawhide) does not want to allow installation using floppies or cdrom. Workaround is to install using another Alpha machine and move the disk to the AS4100. Once installed FreeBSD runs fine. AlphaServer 2100A (Lynx) is not supported in this release. Note that AlphaServer 2100 (Sable) works fine. Machines that have onboard IDE interfaces that their SRM can boot from are now supported with the IDE disk being the root/boot device. See HARDWARE.TXT for machine specifics like speed, use of DMA etc. Note that TGA consoles (either builtin or on TGA expansion cards) will not work. You will need to use a serial console or install a VGA card. 1.2. SECURITY FIXES ------------------- The kernel and userland have been audited for bugs and security vulnerabilities resulting from the incorrect use of format strings in vfprintf()-like functions. No vulnerabilities were discovered. For additional security fixes, see the list of released Security Advisories located at http://www.FreeBSD.org/security/ 1.3. USERLAND CHANGES --------------------- Support for the KAME IKE daemon, racoon, as noted in section 1.1 above. Several additional system utilities (whois, fetch, and possibly others) have gained the ability to operate over IPv6. cdcontrol(1) now supports a "cdid" command, which calculates and displays the CD serial number, using the same algorithm used by the CDDB database. mtree(8) now includes support for a file listing pathnames to be excluded when creating and verifying prototypes. This makes it easier to use mtree as a part of an intrusion-detection system. The OPIE one-time-password suite has been updated to 2.32. OpenSSH has been upgraded to 2.1.0, which provides support for the SSH2 protocol, including DSA keys. Therefore, OpenSSH users in the US no longer need to rely on the restrictively-licensed RSAREF toolkit which is required to handle RSA keys. OpenSSH 2.1 interoperates well with other SSH2 clients and servers, including the ssh2 port. See http://www.openssh.com for more details. OpenSSH can now authenticate using OPIE passwords in SSH1 mode. Support is not yet available in SSH2 mode. camcontrol(8) now includes a built in 'format' function to low-level format SCSI disks. Support for USB devices was added to the GENERIC kernel and to the installation programs to support USB devices out of the box. Note that an AT keyboard must still be used during the initial install, but it should work fine afterwards. The entire i386 bootstrap was revamped to support automatic detection and use of the Enhanced Disk Drive BIOS extensions to support booting beyond the 1023rd cylinder. As part of this change, the FreeBSD boot manager (boot0) was increased from 1 sector in size (512 bytes), to 2 sectors in length (1024 bytes). As a result, several userland changes were made to cope with MBR boot loaders of varying sizes. libfetch has been greatly improved. fetch(1) and the pkg tools now use libfetch instead of libftpio, which means that the pkg tools have gained HTTP support, and both have gained IPv6 support. The csh(1) shell has been replaced by tcsh(1), although it can still be run as csh(1). The more(1) command has been replaced by less(1), although it can still be run as more(1). ls(1) can produce colorized listings with the -G flag (and appropriate terminal support). 2. Supported Configurations --------------------------- FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA 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 peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 164x series MCA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F Microchannel (MCA) bus adapters are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V is not yet supported. AMI MegaRAID Express and Enterprise family RAID controllers: MegaRAID 418 MegaRAID Enterprise 1200 (428) MegaRAID Enterprise 1300 MegaRAID Enterprise 1400 MegaRAID Enterprise 1500 MegaRAID Elite 1500 MegaRAID Express 200 MegaRAID Express 300 Dell PERC Dell PERC 2/SC Dell PERC 2/DC Some HP NetRAID controllers are OEM versions of AMI designs, and these are also supported. Booting from these controllers is supported. Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware: DAC960P DAC960PD DAC960PDU DAC960PL DAC960PJ DAC960PG AcceleRAID 150 AcceleRAID 250 eXtremeRAID 1100 Booting from these controllers is supported. EISA adapters are not supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). DTC 3290 EISA SCSI controller in 1542 emulation mode. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (acd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. [ Note: There is work-in-progress to port the UltraStor driver to the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast Ethernet controller chip, including the following: ANA-62011 64-bit single port 10/100baseTX adapter ANA-62022 64-bit dual port 10/100baseTX adapter ANA-62044 64-bit quad port 10/100baseTX adapter ANA-69011 32-bit single port 10/100baseTX adapter ANA-62020 64-bit single port 100baseFX adapter Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: Alteon AceNIC (Tigon 1 and 2) 3Com 3c985-SX (Tigon 1 and 2) Netgear GA620 (Tigon 2) Silicon Graphics Gigabit Ethernet DEC/Compaq EtherWORKS 1000 NEC Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 Fast Ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX Version 2 Winbond W89C840F Fast Ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE-530TX AOpen/Acer ALN-320 Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs Sundance Technologies ST201 PCI Fast Ethernet NICs including the following: D-Link DFE-550TX SysKonnect SK-984x PCI Gigabit Ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port SK-9842 1000baseSX multimode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multimode fiber, dual port Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100baseTX Racore 8148 10baseT/100baseTX/100baseFX multi-personality ADMtek Inc. AL981-based PCI Fast Ethernet NICs ADMtek Inc. AN985-based PCI Fast Ethernet NICs ADMtek Inc. AN986-based USB Ethernet NICs including the following: LinkSys USB100TX Billionton USB100 Melco Inc. LU-ATX D-Link DSB-650TX SMC 2202USB CATC USB-EL1210A-based USB Ethernet NICs including the following: CATC Netmate CATC Netmate II Belkin F5U111 Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including the following: LinkSys USB10T Entrega NET-USB-E45 Peracom USB Ethernet Adapter 3Com 3c19250 ADS Technologies USB-10BT ATen UC10T Netgear EA101 D-Link DSB-650 SMC 2102USB SMC 2104USB Corega USB-T ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the following: Jaton Corporation XpressNet Fujitsu MB86960A/MB86965A HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Intel InBusiness 10/100 PCI Network Adapter Intel PRO/100+ Management Adapter Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 Ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980/3c980B Fast Etherlink XL server adapter 3Com 3cSOHO100-TX OfficeConnect adapter Toshiba Ethernet cards Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards, including the following: AR-P500 Ethernet card Accton EN2212/EN2216/UE2216(OEM) Allied Telesis CentreCOM LA100-PCM_V2 AmbiCom 10BaseT card BayNetworks NETGEAR FA410TXC Fast Ethernet CNet BC40 adapter COREGA Ether PCC-T/EtherII PCC-T Compex Net-A adapter CyQ've ELA-010 D-Link DE-650/660 Danpex EN-6200P2 IO DATA PCLATE IBM Creditcard Ethernet I/II IC-CARD Ethernet/IC-CARD+ Ethernet Linksys EC2T/PCMPC100 Melco LPC-T NDC Ethernet Instant-Link National Semiconductor InfoMover NE4100 Network Everywhere Ethernet 10BaseT PC Card Planex FNW-3600-T Socket LP-E Surecom EtherPerfect EP-427 Telecom Device SuperSocket RE450T Megahertz X-Jack Ethernet PC-Card CC-10BT 2.3. FDDI --------- DEC FDDI (DEFPA/DEFEA) NICs 2.4. ATM -------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signalling Protocols - The ATM Forum UNI 3.1 signalling protocol - The ATM Forum UNI 3.0 signalling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signalling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.5. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative Labs, Avance, Yamaha and ENSONIQ. (pcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco Airconnect). Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, PCI and ISA adapters are all supported. 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. 3.2. CDROM ---------- FreeBSD 4.1-RELEASE and 3.x-RELEASE CDs may be ordered on CDROM from: BSDi 4041 Pike Lane, Suite F Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@wccdrom.com or http://www.freebsdmall.com. Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 3.0 and there may be some issues affecting you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. Please read the UPGRADE.TXT file for more information, preferably before beginning an upgrade. 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org If you're tracking the -stable development efforts, you should definitely join the -stable mailing list, in order to keep abreast of recent developments and changes that may affect the way you use and maintain the system: freebsd-stable@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html and to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/4.2R/announce.adoc b/website/content/en/releases/4.2R/announce.adoc index 2acd6856f6..b4da43dc76 100644 --- a/website/content/en/releases/4.2R/announce.adoc +++ b/website/content/en/releases/4.2R/announce.adoc @@ -1,46 +1,46 @@ --- title: "FreeBSD 4.2 Announcement" sidenav: download ---- +--- = FreeBSD 4.2 Announcement *Date:* Tue, 21 Nov 2000 04:31:48 -0800 + *From:* "Jordan K. Hubbard" + *To:* announce@FreeBSD.org + *Subject:* 4.2-RELEASE is now available It is my almost excessive pleasure to announce the availability of FreeBSD 4.2-RELEASE, the very latest in 4.x-STABLE branch technology. Following the release of FreeBSD 4.1.1 in September, 2000, many bugs were fixed, important security issues dealt with, and a conservative number of new features added. Please see the release notes for more information. 4.2-RELEASE is now available for the ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.2-RELEASE[i386] and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/4.2-RELEASE[alpha] architectures right now and can be installed directly over the net using the boot floppies or copied to a local NFS/ftp server. ISO (CD) Images + --------------- + We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.2-install.iso + and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.2-install.iso If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISOs, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi. FreeBSD 4.2-RELEASE can be ordered as a 4 CD set from http://www.freebsdmall.com[The FreeBSD Mall] from where it will soon be shipping. Each CD sets contains the FreeBSD installation and application package bits for either the x86 or the alpha architecture (each architecture has its own CD set). For a set of distfiles used to build ports in the ports collection, please see also the FreeBSD Toolkit, a 6 CD set containing all such extra bits which we can no longer fit on the 4 CD sets. You can also order by phone, postal mail, FAX or email at: .... BSDi 4041 Pike Lane, #F Concord CA, 94520 USA Phone: +1 925 674-0783 Fax: +1 925 674-0821 Tech Support: +1 925 603-1234 Email: orders@wccdrom.com WWW: http://www.freebsdmall.com/ .... FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Austria, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, Elbonia, the Ukraine and the United Kingdom, among others. Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp..FreeBSD.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. Thanks! - Jordan diff --git a/website/content/en/releases/4.2R/errata.adoc b/website/content/en/releases/4.2R/errata.adoc index 28bb780c91..2533ac6c43 100644 --- a/website/content/en/releases/4.2R/errata.adoc +++ b/website/content/en/releases/4.2R/errata.adoc @@ -1,40 +1,40 @@ --- title: "FreeBSD 4.2 Errata Notes" sidenav: download ---- +--- = FreeBSD 4.2 Errata Notes .... If you read no other documentation before installing this version of FreeBSD, you should at least by all means *READ THE ERRATA* for this release so that you don't stumble over problems which have already been found and fixed. This ERRATA.TXT file is obviously already out of date by definition, but other copies are kept updated on the net and should be consulted as the "current errata" for your release. These other copies of the errata are located at: 1. http://www.FreeBSD.org/releases/ 2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases//ERRATA.TXT (and any sites which keep up-to-date mirrors of this location). Any changes to this file are also automatically emailed to: freebsd-current@FreeBSD.org For all FreeBSD security advisories, see: http://www.FreeBSD.org/security/ for the latest security incident information. ---- Security Advisories: Current active security advisories: None ---- System Update Information: .... link:../../[Release Home] diff --git a/website/content/en/releases/4.2R/notes.adoc b/website/content/en/releases/4.2R/notes.adoc index 0976eee952..fc001d95ba 100644 --- a/website/content/en/releases/4.2R/notes.adoc +++ b/website/content/en/releases/4.2R/notes.adoc @@ -1,1019 +1,1019 @@ --- title: "FreeBSD 4.2 Release Notes" sidenav: download ---- +--- = FreeBSD 4.2 Release Notes .... RELEASE NOTES FreeBSD 4.2-RELEASE Any installation failures or crashes should be reported by using the send-pr command (those preferring a Web-based interface can also see http://www.FreeBSD.org/send-pr.html). For information about FreeBSD and the layout of the 4.2-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. For the latest 4-stable snapshots, you should always see: ftp://releng4.FreeBSD.org/pub/FreeBSD Table of contents: ------------------ 1. What's new since 4.1-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 FDDI 2.4 ATM 2.5 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgements 1. What's new since 4.1-RELEASE -------------------------------------- Changes which were also present in the 4.1.1 point release will be marked [4.1.1]. 1.1. KERNEL CHANGES ------------------- The tap driver, a virtual Ethernet device driver for bridged configurations, has been added. [4.1.1] accept_filters, a kernel feature to reduce overheads when accepting and reading new connections on listening sockets, has been added. [4.1.1] POSIX.1b Shared Memory Objects are now supported. The implementation uses regular files, but automatically enables the MAP_NOSYNC flag when they are mmap(2)ed. [4.1.1] The ata(4) driver now has support for ATA100 controllers. [4.1.1] The ata(4) driver now has support for tagged queueing, which is enabled by the ATA_ENABLE_TAGS option. It also supports the ServerWorks ROSB4 ATA33 chipset, the CMD 648 ATA66 and CMD 649 ATA100 chipsets, and the Cyrix 5530. It also has support for ATA "pseudo" RAID controllers, including the Promise Fasttrak and HighPoint HPT370 controllers. The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit Ethernet and Netgear GA620T 1000baseT Gigabit Ethernet cards. [4.1.1] The ng_bridge(4) node type has been added to the netgraph subsystem. Miscellaneous bug fixes and enhancements have also been made. [4.1.1] Support for Fujitsu MB86960A/MB86965A based Ethernet PC-Cards is back. [4.1.1] The asr(4) driver, which provides support for the Adaptec SCSI RAID controller family, as well as the DPT SmartRAID V and VI families, has been added. [4.1.1] The i386 boot loader now has support for a "nullconsole" console type, for use on systems with neither a video console nor a serial port. [4.1.1] The pcn(4) driver, which supports the AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA adapters, has been added. Although these cards are already supported by the lnc(4) driver, the pcn driver runs these chips in 32-bit mode and uses the RX alignment feature to achieve zero-copy receive. This driver is also machine-independent, so it will work on both the i386 and alpha platforms. The lnc driver is still needed to support non-PCI cards. The pcm(4) driver now supports the ESS Solo 1, Maestro-1, Maestro-2, and Maestro-2e; Forte Media fm801, ESS Maestro-2e, and VIA Technologies VT82C686A sound card/chipsets, and has received some other updates. Replace the PQ_*CACHE options with a single PQ_CACHESIZE option to be set to the cache size in kilobytes. The old options are still supported for backwards compatibility. The NCPU, NAPIC, NBUS, and NINTR kernel configuration options, for configuring SMP kernels, have been removed. NCPU is now set to a maximum of 16, and the other, aforementioned options are now dynamic. The ahc(4) driver has been updated. The amr(4) driver has been updated with support for new AMI MegaRAID models. The snc(4) driver for the National Semiconductor DP8393X (SONIC) Ethernet controller. Curently, this driver is only used on the PC-98 architecture. The ich(4) driver for the Intel 82801AA (ICH) SMBus controller and compatibles has been added. bktr(4) driver has been updated to 2.15. New tuner types have been added, and improvememts to the KLD module and to memory allocation have been made. [4.1.1] This driver subsequently was updated to 2.17, which fixes bugs in devfs when unloading and reloading, and syncs with some NetBSD changes. Default the PC Card Interface Controller(pcic) to polling mode(irq 0). The ncv(4), nsp(4), and stg(4) drivers have been ported from NetBSD/pc98. They supports NCR 53C50 / Workbit Ninja SCSI-3 / TMC 18C30, 18C50 based PC-Card/ISA SCSI controllers. The mly(4) driver, for Mylex PCI to SCSI AccelRAID and eXtremeRAID controllers with firmware 6.x and later, has been added. The twe(4) driver for 3ware controllers has been updated, with improved queueing, error handling and reporting, and user interface for the 3ware-supplied '3dm' monitoring tool. The uscanner(4) driver, which provides basic USB scanner support using SANE, has been added. (See the SANE home page for supported scanners.) The HP ScanJet 4100C, 5200C and 6300C are known to be working. The umodem(4) driver for USB modems has been added; it currently supports the 3Com 5605 USB modem. 1.2. SECURITY FIXES ------------------- sysinstall(8) now allows the user to select one of three "security profiles" at install-time. These profiles enable different levels of system security by enabling or disabling various system services in rc.conf(5) on new installs. [4.1.1] Many string-handling library calls were fixed to reduce the possibility of buffer overflow-related exploits. A security hole in Linux emulation was fixed (see security advisory FreeBSD-SA-00:42). [4.1.1] TCP now uses stronger randomness in choosing its initial sequence numbers (see security advisory FreeBSD-SA-00:52). A bug in finger(1) that could allow remote users to view world-readable files has been closed (see security advisory FreeBSD-SA-00:54). rlogind(8), rshd(8), and fingerd(8) are now disabled by default in /etc/inetd.conf. This change only affects new installations. Several buffer overflows in tcpdump(1) were corrected (see security advisory FreeBSD-SA-00:61). A security hole in top(1) was corrected (see security advisory FreeBSD-SA-00:62). A potential security hole caused by an off-by-one-error in gethostbyname(3) has been fixed (see security advisory FreeBSD-SA-00:63). A potential buffer overflow in the ncurses(3X) library, which could cause arbitrary code to be run from within systat(1), has been corrected (see security advisory FreeBSD-SA-00:68). A vulnerability in telnetd(8) that could cause it to consume large amounts of server resources has been fixed (see security advisory FreeBSD-SA-00:69). The "nat deny_incoming" command in ppp(8) now works correctly (see security advisory FreeBSD-SA-00:70). 1.3. USERLAND CHANGES --------------------- RSA Security has waived all patent rights to the RSA algorithm (two weeks before the patent was due to expire). As a result, the native OpenSSL implementation of the RSA algorithm is now activated by default, and the rsaref port and librsaUSA are no longer required for USA residents. [4.1.1] sshd is now enabled by default on new installs. [4.1.1] Version numbers of installed packages have a new (backward-compatible) syntax, which supports the "PORTREVISION" and "PORTEPOCH" variables in ports collection makefiles. These changes help keep track of changes in the ports collection entries such as security patches or FreeBSD-specific updates, which aren't reflected in the original, third-party software distributions. pkg_version(1) can now compare these new-style version numbers. [4.1.1] sendmail upgraded from version 8.9.3 to version 8.11.1. Important changes include: new default file locations (see /usr/src/contrib/sendmail/cf/README); newaliases is limited to root and trusted users; STARTTLS encryption; and the MSA port (587) is turned on by default. See /usr/src/contrib/sendmail/RELEASE_NOTES for more information. mail.local(8) is no longer installed as a set-user-id binary. If you are using a /etc/mail/sendmail.cf from the default sendmail.cf included with FreeBSD any time after 3.1.0, you are fine. If you are using a hand-configured sendmail.cf and mail.local for delivery, check to make sure the F="S" flag is set on the Mlocal line. Those with .mc files who need to add the flag can do so by adding the following line to their your .mc file and regenerating the sendmail.cf file: MODIFY_MAILER_FLAGS(`LOCAL', `+S')dnl Note that FEATURE(`local_lmtp') already does this. The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY commands. vacation(1) has been updated to use the version included with sendmail. The sendmail(8) configuration building tools are installed in /usr/share/sendmail/cf/. OpenSSH has been upgraded to 2.2.0. ssh-add(1) and ssh-agent(1) can now handle DSA keys. An sftp server interoperable with ssh.com clients and others has been added. scp(1) can now handle files >2GB. Interoperability with other ssh2 clients/servers has been improved. A new feature to limit the number of outstanding unauthenticated ssh connections in sshd has been added. The compiler chain now uses the FSF-supplied C/C++ runtime initialization code. This change brings about better compatibility with code generated from the various egcs and gcc ports, as well as the stock public FSF source. cvs(1) has been updated to 1.11. The threads library has gained some signal handling changes, bug fixes, and performance enhancements (including zero system call thread switching). gdb(1) thread support has been updated to match these changes. GDB now supports hardware watchpoints. [4.1.1] routed(8) has been updated to version 2.22. [4.1.1] The truncate(1) utility, which truncates or extends the length of files, has been added. [4.1.1] syslogd(8) can take a -n option to disable DNS queries for every request. [4.1.1] kenv(1), a command to dump the kernel environment, has been added. [4.1.1] The behavior of periodic(8) is now controlled by /etc/defaults/periodic.conf and /etc/periodic.conf. [4.1.1] logger(1) can now send messages directly to a remote syslog. [4.1.1] OpenSSL has been upgraded to 0.9.5a, which includes numerous bugfixes and enhancements. [4.1.1] finger(1) now has the ability to support fingering aliases, via the finger.conf(5) file. [4.1.1] The xl(4) driver now supports the 3Com 3C556 and 3C556B MiniPCI adapters used on some laptops. [4.1.1] killall(1) is now a C program, rather than a Perl script. As a result, killall's -m option now uses the regular expression syntax of regex(3), rather than that of perl(1). [4.1.1] boot98cfg(8), a PC-98 boot manager installation and configuration utility, has been added. [4.1.1] The ifconfig(8) command can set the link-layer address of an interface. [4.1.1] setproctitle(3) has been moved from libutil to libc. [4.1.1] sed(1) now takes a -E option for extended regular expression support. [4.1.1] ln(1) now takes an -i option to request user configuration before overwriting an existing file. [4.1.1] tcpdump(1) has received some updates and bugfixes. User-land ppp(8) has received a number of updates and bugfixes. The internal procedure for building perl has changed, and no longer depends on (nor installs) miniperl. Users upgrading from source should delete /usr/bin/miniperl. To improve performance and disk utilization, the "ports skeletons" in the FreeBSD Ports Collection have been restructured. Installed ports and packages should not be affected. ncurses has been updated to ncurses-5.1-20001009. make(1) has gained the :C/// (regexp substitution), :L (lowercase), and :U (uppercase) variable modifiers. These were added to reduce the differences between the FreeBSD and OpenBSD/NetBSD make programs. The "in use" percentage metric displayed by netstat(1) now really reflects the percentage of network mbufs used. chio(1) now has the ability to specify elements by volume tag instead of by their physical location as well as the ability to return an element to its previous location. The ISC library from the BIND distribution is now built as libisc. IP Filter is now supported by the rc.conf(5) boot-time configuration and initialization. 2. Supported Configurations --------------------------- FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA and PCI bus based PC's, ranging from 386sx to Pentium class machines (though the 386sx is not recommended). Support for generic IDE drive configurations, various SCSI controller, network and serial cards is also provided. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 164x series MCA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. Adaptec 1400, 2100S, 3200S, and 3400S SCSI RAID controllers. AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F Microchannel (MCA) bus adapters are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. DPT SmartRAID V and VI SCSI RAID controllers: PM1554, PM2554, PM2654, PM2865, PM2754, PM3755, PM3757 AMI MegaRAID Express and Enterprise family RAID controllers: MegaRAID 418 MegaRAID Enterprise 1200 (428) MegaRAID Enterprise 1300 MegaRAID Enterprise 1400 MegaRAID Enterprise 1500 MegaRAID Enterprise 1600 MegaRAID Elite 1500 MegaRAID Elite 1600 MegaRAID Express 200 MegaRAID Express 300 MegaRAID Express 400 Dell PERC Dell PERC 2/SC Dell PERC 2/DC Some HP NetRAID controllers are OEM versions of AMI designs, and these are also supported. Booting from these controllers is supported. Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware: DAC960P DAC960PD DAC960PDU DAC960PL DAC960PJ DAC960PG AcceleRAID 150 AcceleRAID 250 eXtremeRAID 1100 Booting from these controllers is supported. EISA adapters are not supported. Mylex PCI to SCSI RAID controllers with 6.x firmware: AcceleRAID 160 AcceleRAID 170 AcceleRAID 352 eXtremeRAID 2000 eXtremeRAID 3000 Compatible Mylex controllers not listed should work, but have not been verified. 3ware Escalade ATA RAID controllers. All members of the 5000 and 6000 series are supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 NCR 53C500 based PC-Card SCSI host adapters: IO DATA PCSC-DV KME KXLC002(TAXAN ICD-400PN, etc.), KXLC004 Macnica Miracle SCSI-II mPS110 Media Intelligent MSC-110, MSC-200 NEC PC-9801N-J03R New Media Corporation BASICS SCSI Qlogic Fast SCSI RATOC REX-9530, REX-5572 (as SCSI only) TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters: Future Domain SCSI2GO IBM SCSI PCMCIA Card ICM PSC-2401 SCSI Melco IFC-SC RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters. QLogic 2100 Fibre Channel Adapters (private loop only). DTC 3290 EISA SCSI controller in 1542 emulation mode. Workbit Ninja SCSI-3 based PC-Card SCSI host adapters: Alpha-Data AD-PCS201 IO DATA CBSC16 With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (acd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. [ Note: There is work-in-progress to port the UltraStor driver to the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast Ethernet controller chip, including the following: ANA-62011 64-bit single port 10/100baseTX adapter ANA-62022 64-bit dual port 10/100baseTX adapter ANA-62044 64-bit quad port 10/100baseTX adapter ANA-69011 32-bit single port 10/100baseTX adapter ANA-62020 64-bit single port 100baseFX adapter Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: 3Com 3c985-SX (Tigon 1 and 2) Alteon AceNIC 1000baseSX (Tigon 1 and 2) Alteon AceNIC 1000baseT (Tigon 2) DEC/Compaq EtherWORKS 1000 Farallon PN9000SX NEC Gigabit Ethernet Netgear GA620 (Tigon 2) Netgear GA620T (Tigon 2, 1000baseT) Silicon Graphics Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA. SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 Fast Ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs NDC Communications SFA100A (98713A) CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) SVEC PN102TX (98713) Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX Version 2 Winbond W89C840F Fast Ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE-530TX AOpen/Acer ALN-320 Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs Sundance Technologies ST201 PCI Fast Ethernet NICs including the following: D-Link DFE-550TX SysKonnect SK-984x PCI Gigabit Ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port SK-9842 1000baseSX multimode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multimode fiber, dual port Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100baseTX Racore 8148 10baseT/100baseTX/100baseFX multi-personality ADMtek Inc. AL981-based PCI Fast Ethernet NICs ADMtek Inc. AN985-based PCI Fast Ethernet NICs ADMtek Inc. AN986-based USB Ethernet NICs including the following: LinkSys USB100TX Billionton USB100 Melco Inc. LUA-TX D-Link DSB-650TX SMC 2202USB CATC USB-EL1210A-based USB Ethernet NICs including the following: CATC Netmate CATC Netmate II Belkin F5U111 Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including the following: LinkSys USB10T Entrega NET-USB-E45 Peracom USB Ethernet Adapter 3Com 3c19250 ADS Technologies USB-10BT ATen UC10T Netgear EA101 D-Link DSB-650 SMC 2102USB SMC 2104USB Corega USB-T ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B 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 Etherpower 8432T, DE245, etc) Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the following: Jaton Corporation XpressNet Fujitsu MB86960A/MB86965A, including the following: CONTEC C-NET(PC)C Ethernet Eiger Labs EPX-10BT Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 Ethernet PCMCIA Fujitsu Towa LA501 Ethernet HITACHI HT-4840-11 NextCom J Link NC5310 RATOC REX-5588, REX-9822, REX-4886, REX-R280 TDK LAK-CD021, LAK-CD021A, LAK-CD021BX HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Intel InBusiness 10/100 PCI Network Adapter Intel PRO/100+ Management Adapter Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 Ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI, 3C556/556B MiniPCI, and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980/3c980B Fast Etherlink XL server adapter 3Com 3cSOHO100-TX OfficeConnect adapter Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards, including the following: AR-P500 Ethernet card Accton EN2212/EN2216/UE2216(OEM) Allied Telesis CentreCOM LA100-PCM_V2 AmbiCom 10BaseT card BayNetworks NETGEAR FA410TXC Fast Ethernet CNet BC40 adapter COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF Compex Net-A adapter CyQ've ELA-010 D-Link DE-650/660 Danpex EN-6200P2 IO DATA PCLATE IBM Creditcard Ethernet I/II IC-CARD Ethernet/IC-CARD+ Ethernet Linksys EC2T/PCMPC100 Melco LPC-T NDC Ethernet Instant-Link National Semiconductor InfoMover NE4100 Network Everywhere Ethernet 10BaseT PC Card Planex FNW-3600-T Socket LP-E Surecom EtherPerfect EP-427 TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card Telecom Device SuperSocket RE450T Megahertz X-Jack Ethernet PC-Card CC-10BT Xircom CreditCard adapters(16bit) and workalikes Accton EN2226/Fast EtherCard (16-bit verison) Compaq Netelligent 10/100 PC Card Intel EtherExpress PRO/100 Mobile Adapter (16-bit verison) Xircom Realport card + modem(Ethernet part) Xircom CreditCard Ethernet 10/100 Xircom CreditCard 10Base-T "CreditCard Ethernet Adaptor IIps" (PS-CE2-10) Xircom CreditCard Ethernet 10/100 + modem (Ethernet part) National Semiconductor DP8393X (SONIC) Ethernet cards NEC PC-9801-83, -84, -103, and -104 NEC PC-9801N-25 and -J02R 2.3. FDDI --------- DEC FDDI (DEFPA/DEFEA) NICs 2.4. ATM -------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signalling Protocols - The ATM Forum UNI 3.1 signalling protocol - The ATM Forum UNI 3.0 signalling protocol - The ATM Forum ILMI address registration - FORE Systems's proprietary SPANS signalling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.5. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Advance Asound 100, 110 and Logic ALS120 Crystal Semiconductor CS461x/462x/428x ENSONIQ AudioPCI ES1370/1371 ESS ES1868, ES1869, ES1879 and ES1888 ESS Maestro-1, Maestro-2, and Maestro-2E ForteMedia fm801 Gravis UltraSound MAX/PnP MSS/WSS Compatible DSPs NeoMagic 256AV/ZX OPTi 931/82C931 SoundBlaster, Soundblaster Pro, Soundblaster AWE-32, Soundblaster AWE-64 Trident 4DWave DX/NX VIA Technologies VT82C686A Yamaha DS1 and DS1e (newpcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes NCR WaveLAN/IEEE 802.11 Cabletron RoamAbout 802.11 DS Compaq WL100 Corega KK Wireless LAN PCC-11 Laneed Wireless card ELECOM Air@Hawk/LD-WL11/PCC Farallon Skyline 11Mbps Wireless ICOM SL-1100 Melco Airconnect WLI-PCM-L11 NEC Wireless Card CMZ-RT-WP PLANEX GeoWave/GW-NS110 TDK LAK-CD011WL Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, PCI and ISA adapters are all supported. Cisco Systems Aironet 340 Series (includes 340, 341, and 342 models) 11Mbps 802.11 wireless NIC Toshiba Mobile HDD MEHDD20A (Type II) 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. 3.2. CDROM ---------- FreeBSD 4.x-RELEASE CDs may be ordered on CDROM from: BSDi 4041 Pike Lane, Suite F Concord CA 94520 1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@osd.bsdi.com or http://www.freebsdmall.com. Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 3.0 and there may be some issues affecting you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. Please read the UPGRADE.TXT file for more information, preferably before beginning an upgrade. 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org If you're tracking the -stable development efforts, you should definitely join the -stable mailing list, in order to keep abreast of recent developments and changes that may affect the way you use and maintain the system: freebsd-stable@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special mention to: The donors listed at http://www.FreeBSD.org/handbook/donors.html And to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. We sincerely hope you enjoy this release of FreeBSD! The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releases/4.3R/announce.adoc b/website/content/en/releases/4.3R/announce.adoc index 49217d32ed..c8a24c9efa 100644 --- a/website/content/en/releases/4.3R/announce.adoc +++ b/website/content/en/releases/4.3R/announce.adoc @@ -1,48 +1,48 @@ --- title: "FreeBSD 4.3 Announcement" sidenav: download ---- +--- = FreeBSD 4.3 Announcement *Date:* Friday, 20 Apr 2001 21:00:00 -0800 + *From:* "Jordan K. Hubbard" + *To:* announce@FreeBSD.org + *Subject:* 4.3-RELEASE is now available It gives me great pleasure to announce what is probably the finest release produced from the 4.x-STABLE branch to date, FreeBSD 4.3-RELEASE. Following the release of FreeBSD 4.2 in November, 2000, many bugs were fixed, important security issues dealt with, and a reasonable number of new features added. Please see the release notes for more information. 4.3-RELEASE is available for the ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.3-RELEASE[i386] and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/4.3-RELEASE[alpha] architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/ftp server. ISO (CD) Images + --------------- + We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.3-install.iso + and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.3-install.iso If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISOs, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi. FreeBSD 4.3-RELEASE can be ordered as a 4 CD set from http://www.freebsdmall.com[The FreeBSD Mall] from where it will soon be shipping. Each CD sets contains the FreeBSD installation and application package bits for either the x86 or the alpha architecture (each architecture has its own CD set). For a set of distfiles used to build ports in the ports collection, please see also the FreeBSD Toolkit, a 6 CD set containing all such extra bits which we can no longer fit on the 4 CD sets. You can also order by phone, postal mail, FAX or email at: .... BSDi 4041 Pike Lane, #F Concord CA, 94520 USA Phone: +1 925 674-0783 Fax: +1 925 674-0821 Tech Support: +1 925 603-1234 Email: orders@wccdrom.com WWW: http://www.freebsdmall.com/ .... *Note:* Despite the recent acquisition of BSDi's software assets by Wind River, the above information still holds true for the forseeable future and will not change for at least the life-cycle of the FreeBSD 4.3 product. Any changes in the FreeBSD product sales infrastructure will be announced if and as they occur. FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Austria, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, Elbonia, the Ukraine and the United Kingdom, among others. Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp..FreeBSD.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. Thanks! - Jordan diff --git a/website/content/en/releases/4.3R/notes.adoc b/website/content/en/releases/4.3R/notes.adoc index daa3b1498f..89cf139035 100644 --- a/website/content/en/releases/4.3R/notes.adoc +++ b/website/content/en/releases/4.3R/notes.adoc @@ -1,1270 +1,1270 @@ --- title: "FreeBSD 4.3 Release Notes" sidenav: download ---- +--- = FreeBSD 4.3 Release Notes .... RELEASE NOTES FreeBSD 4.3-RELEASE version Any installation failures or crashes should be reported by using the send-pr command (those preferring a Web-based interface can also see http://www.FreeBSD.org/send-pr.html). For information about FreeBSD and the layout of the 4.3-RELEASE directory (especially if you're installing from floppies!), see ABOUT.TXT. For installation instructions, see the INSTALL.TXT and HARDWARE.TXT files. Table of contents: ------------------ 1. What's new since 4.2-RELEASE 1.1 KERNEL CHANGES 1.2 SECURITY FIXES 1.3 USERLAND CHANGES 2. Supported Configurations 2.1 Disk Controllers 2.2 Ethernet cards 2.3 FDDI 2.4 ATM 2.5 Misc 3. Obtaining FreeBSD 3.1 FTP/Mail 3.2 CDROM 4. Upgrading from previous releases of FreeBSD 5. Reporting problems, making suggestions, submitting code 6. Acknowledgments 1. What's new since 4.2-RELEASE ------------------------------- 1.1. KERNEL CHANGES ------------------- Write combining for crashdumps has been implemented. This feature is useful when write caching is disabled on both SCSI and IDE disks, where large memory dumps could take up to an hour to complete. The pccard driver and pccardc(8) now support multiple "beep types" upon card insertion and removal. The twe(4) driver for 3Ware Escalade controllers has been updated. The an(4) driver for Cisco Aironet cards now supports Wired Equivalent Privacy (WEP) encryption, settable via ancontrol(8). The wi(4) and an(4) drivers now default to BSS (infrastructure) mode; previously the default was ad-hoc mode. The ray(4) driver, which supports the Webgear Aviator wireless network cards, has been committed. The operation of ray(4) interfaces can be modified by raycontrol(8). Support for the Adaptec FSA family of PCI-SCSI RAID controllers has been added, in the form of the aac(4) driver. Linksys Fast Ethernet PCCARD cards supported by the ed(4) driver now require the addition of flag 0x80000 to their config line in pccard.conf(5). This flag is not optional. These Linksys cards will not be recognized without it. A bug in the ed(4) driver that could cause panics with very short packets and BPF or bridging active has been fixed. A bug in FFS that could cause superblock corruption on very large filesystems has been corrected. The ISO-9660 filesystem now has a hook that supports a loadable character conversion routine. The sysutils/cd9660_unicode port contains a set of common conversions. A new NFS hash function (based on the Fowler/Noll/Vo hash algorithm) has been implemented to improve NFS performance by increasing the efficiency of the nfsnode hash tables. The cs(4) driver has been updated. bridge(4) and dummynet(4) have received some enhancements and bug fixes. The ahc(4) driver has been updated. Among various improvements are improved compatibility with chips in "RAID Port" mode and systems with AAA and ARO cards installed, as well as performance improvements. Some bugs were also fixed, including a rare hang on Ultra2/U160 controllers. The cd(4) driver now has support for write operations. This allows writing to DVD-RAM, PD and similar drives that probe as CD devices. Note that this change affects only random-access writeable devices, not sequential-only writeable devices such as CD-R drives, which are supported by cdrecord(1). The "make buildkernel" procedure has changed slightly. It now gets the name of the configuration(s) to build from the KERNCONF variable (KERNEL is still valid, but deprecated). The installed kernel name can be changed with the INSTKERNEL variable. The NO_KERNELCLEAN variable prevents cleaning of the kernel build directory (which is now done via "make clean", rather than "config -r"). kobj functionality has been merged from -CURRENT to better support sound drivers. Separate drivers for the SoundBlaster 8 and Soundblaster 16 now replace an older, unified driver. A driver for the ESS Maestro-3/Allegro has been added, however due to licensing restrictions, it cannot be compiled into the kernel. To use this driver, add the following line to /boot/loader.conf: snd_maestro3_load="YES" The pcm(4) driver now supports the CMedia CMI8338/CMI8738 sound chips, as well as the CS4281 sound chip. When sound modules are built, one can now load all the drivers and infrastructure by "kldload snd". The isp(4) driver has been updated. ipfilter has been updated to 3.4.16. ipfw(8) has a new feature ("me") that allows for packet matching on interfaces with dynamically-changing IP addresses. TCP has received some bug fixes for its delayed ACK behavior. TCP now supports the NewReno modification to the TCP Fast Recovery algorithm. This behavior can be controlled via the net.inet.tcp.newreno sysctl variable. TCP now uses a more aggressive timeout for initial SYN segments; this allows initial connection attempts to be dropped much faster. ICMP UNREACH_FILTER_PROHIB messages can now RST TCP connections in the SYN_SENT state if the correct sequence numbers are sent back, as controlled by the net.inet.tcp.icmp_may_rst sysctl. A new sysctl net.inet.ip.check_interface, which is off by default, causes IP to verify that an incoming packet arrives on an interface that has an address matching the packet's destination address. The ata(4) driver has been updated. To provide more flexible configuration, the various options for the ata(4) driver are now boot loader tunables, rather than kernel configure-time options. The ata(4) driver now supports ATA66 and ATA100 mode on Acer Alladin chipsets. kqueue(2) has been extended to the device layer, and has also received some bug fixes. Some signal-handling fixes for Linux have been added, which improves compatibility with signal-intensive programs running under Linux emulation. The ida disk driver now has crashdump support. The mly(4) driver has received some changes in queueing, concurrency improvements, and stability fixes. Several minor bugs have been fixed in the VLAN networking code. Vinum has received some bugfixes. Changes specific to Alpha architecture: A bug in the machine-dependent code for the AlphaServer 1000 and 1000A has been fixed; it had caused only EV4-equipped AS1000 and EV5-equipped AS1000A systems to work. The API UP1100 mainboard has been verified to work correctly. The API CS20 1U high server has been verified to work correctly. AlphaServer 2100A ("Lynx") support has been added. The AlphaServer 4000 and 4100 refuse to boot from the FreeBSD install floppy or install CDROM. The workaround is to "dd" the 2.88MB floppy image onto a hard disk and boot the installer from it. Once sysinstall(8) is running, a normal installation can be performed. Similar problems have been observed on the AlphaServer 1200 and 8400. For AlphaServer 4100 adapter cards with PCI bridge chips might cause trouble. In addition, the capability of booting from an adapter might be influenced by the placement of the adapter card on a specific PCI hose. Please use 'send-pr' to report any problems you might encounter in this area. 1.2. SECURITY FIXES ------------------- Some fixes were applied to the Kerberos IV implementation related to environment variables, a possible buffer overrun, and overwriting ticket files. telnet(1) now does a better job of sanitizing its environment. Several vulnerabilities in procfs(4) were fixed (see security advisory FreeBSD-SA-00:77). A bug in ipfw(8) and ip6fw(8) in which inbound TCP segments could incorrectly be treated as being part of an "established" connection has been fixed (see security advisory FreeBSD-SA-01:08). A bug in crontab(8) that could allow users to read any file on the system in valid crontab(5) syntax has been fixed (see security advisory FreeBSD-SA-01:09). A vulnerability in inetd(8) that could allow read-access to the initial 16 bytes of wheel-accessible files has been fixed (see security advisory FreeBSD-SA-01:11). A bug in periodic(8) that used insecure temporary files has been corrected (see security advisory FreeBSD-SA-01:12). To fix a remotely-exploitable buffer overflow, BIND has been updated to 8.2.3 (see security advisory FreeBSD-SA-01:18). OpenSSH now has code to prevent (instead of just mitigating through connection limits) an attack that can lead to guessing the server key (not host key) by regenerating the server key when an RSA failure is detected (see security advisory FreeBSD-SA-01:24). A bug in ICMP that could cause an attacker to disrupt TCP and UDP "sessions" has been corrected. A bug in timed(8), which caused it to crash if sent certain malformed packets, has been corrected (see security advisory FreeBSD-SA-01:28). A bug in rwhod(8), which caused it to crash if sent certain malformed packets, has been corrected (see security advisory FreeBSD-SA-01:29). A security hole in FreeBSD's FFS and EXT2FS implementations, which allowed a race condition that could cause users to have unauthorized access to data, has been fixed (see security advisory FreeBSD-SA-01:30). A remotely-exploitable vulnerability in ntpd(8) has been closed (see security advisory FreeBSD-SA-01:31). A security hole in IPFilter's fragment cache has been closed (see security advisory FreeBSD-SA-01:32). Buffer overflows in glob(3), which could cause arbitrary code to be run on an FTP server, have been closed. In addition, to prevent some forms of DOS attacks, glob(3) now allows specification of a limit on the number of pathname matches it will return. ftpd(8) now uses this feature (see security advisory FreeBSD-SA-01:33). Initial sequence numbers in TCP are more thoroughly randomized, using an algorithm obtained from OpenBSD. A number of programs have had output formatting strings corrected so as to reduce the risk of vulnerabilities. A number of programs that use temporary files now do so more securely. 1.3. USERLAND CHANGES --------------------- newfs(1) now implements write combining, which can make creation of new filesystems up to seven times faster. A number of buffer overflows in config(8) have been fixed. Binutils have been upgraded to 2.10.1. OpenSSL has been upgraded to 0.9.6. OpenSSL now has support for machine-dependent ASM optimizations, activated by the new CPUTYPE/MACHINE_CPU Makefile variables. file(1) has been contribify-ed, and imported as version 3.33. groff(1) and its related utilities have been updated to FSF version 1.16.1. indent(1) has gained some new formatting options. sysinstall(8) now uses some more intuitive defaults thanks to some new dialog support functions. sysinstall(8) now properly preserves /etc/mail during a binary upgrade. The default root partition in sysinstall(8) is now 100MB. libdisk can now do install-time configuration of the i386 boot0 boot loader. rm(1) -v now displays the entire pathname of a file being removed. lpr(1), lpq(1), and lpd(8) have received a few minor enhancements. OpenSSH has been upgraded to 2.3.0. This version adds support for the Rijndael encryption algorithm. Kerberos compatability has been added to OpenSSH. OpenSSH has been modified to be more resistant to traffic analysis by requiring that "non-echoed" characters are still echoed back in a null packet, as well as by padding passwords sent so as not to hint at password lengths. syslogd(8) now supports a "LOG_CONSOLE" facility (disabled by default), which can be used to log /dev/console output. cdcontrol(1) now uses the CDROM environment variable to pick a default device. All packages and ports now contain an "origin" directive, which makes it easier for programs like pkg_version(1) to determine the directory from which a package was built. pkg_info(1) can now accept a -g flag for verifying an installed package against its recorded checksums (to see if it's been modified post-installation). Naturally, this mechanism is only as secure as the contents of /var/db/pkg if it's to be used for auditing purposes. pkg_create(1) and pkg_add(1) can now work with packages that have been compressed using bzip2(1). pkg_add(1) will use the PACKAGEROOT environment variable to determine a mirror site for new packages. pkg_info(1) now supports globbing against names of installed packages. The -G option disables this behavior, and the -x option causes regular expression matching instead of shell globbing. pkg_sign(1) and pkg_check(1) have been added to digitally sign and verify the signatures on binary package files. pkg_update(1), a utility to update installed packages and update their dependencies, has been added. pkg_delete(1) now can perform glob/regexp matching of package names. In addition, it supports the -a option for removing all packages and the -i option for rm(1)-style interactive confirmation. pkg_create(1) now records dependencies in dependency order rather than in the order specified on the command line. This improves the functioning of "pkg_add -r". pkg_version(1) now has a version number comparison routine that corresponds to the Porters Handbook. It also has a -t option for testing address comparisons. awk has been upgraded from gawk-3.0.4 to gawk-3.0.6. This fixes a number of non-critical bugs and includes a few performance tweaks. Shortly after the receipt of a SIGINFO signal (normally control-T from the controlling tty), fsck(8) will now output a line indicating the current phase number and progress information relevant to the current phase. pwd(1) can now double as realpath(1), a program to resolve pathnames to their underlying physical paths. gcc(1) has been updated to 2.95.3. gcc(1) now uses a unified libgcc rather than a separate one for threaded and non-threaded programs. /usr/lib/libgcc_r.a can be removed. config(8) is now better about converting various warnings that should have been errors into actual fatal errors with an exit code. This ensures that that "make buildkernel" doesn't quietly ignore them and build a bogus kernel without a human to read the errors. In /etc/ssh/sshd_config, the ConnectionsPerPeriod parameter has been deprecated in favor of MaxStartups. find(1) now takes the -empty flag, which returns true if a file or directory is empty. find(1) now takes the -iname and -ipath primaries for case-insensitive matches, and the -regexp and -iregexp primaries for regular-expression matches. The -E flag now enables extended regular expressions. ldconfig(8) now checks directory ownerships and permissions for greater security; these checks can be disabled with the -i flag. sendmail(8) and associated utilities upgraded from version 8.11.1 to version 8.11.3. See /usr/src/contrib/sendmail/RELEASE_NOTES for more information. New make.conf options: SENDMAIL_MC and SENDMAIL_ADDITIONAL_MC. See /etc/defaults/make.conf for more information. The Makefile in /etc/mail now supports: the new SENDMAIL_MC make.conf option; the ability to build .cf files from .mc files; generalized map rebuilding; rebuilding the aliases file; and the ability to stop, start, and restart sendmail. vidcontrol(1) now accepts a -g parameter to select custom text geometry in the VESA_800x600 raster text mode. The rfork_thread(3) library call has been added as a helper function to rfork(2). Using this function should avoid the need to implement complex stack swap code. The compat3x distribution has been updated to include libraries present in FreeBSD 3.5.1-RELEASE. gperf has been updated to 2.7.2. Catching up with most other network utilities in the base system, lpr(1), lpd(8), syslogd(8), and logger(1) are now all IPv6-capable. When requested to delete multiple packages, pkg_delete(1) will now attempt to remove them in dependency order rather than the order specified on the command line. burncd(8) now supports a -m option for multisession mode (the default behavior now is to close disks as single-session). A -l option to take a list of image files from a filename was also added; "-" can be used as a filename for stdin. tar(1) now supports the TAR_RSH variable, principally to enable the use of ssh(1) as a transport. Bugs in make(1), among which include broken null suffix behavior, bad assumptions about current directory permissions, and potential buffer overflows, have been fixed. The new CPUTYPE make.conf variable controls the compilation of processor-specific optimizations in various pieces of code such as OpenSSL. Boot-time syscons configuration was moved to a machine-independent rc.syscons. login(1) now exports environment variables set by PAM modules. ipfstat(8) now supports the -t option to turn on a top(1)-like display. tftpd(8) now takes the -c and -C options, which allow the server to chroot(2) based on the IP address of the connecting client. tftp(1) and tftpd(8) can now transfer files larger than 65535 blocks. The lastlogin(1) utility, which prints the last login time of each user, has been imported from NetBSD. /usr/src/share/examples/BSD_daemon/ now contains a scalable Beastie graphic. bc has been updated from 1.04 to 1.06. savecore(8) now supports a -k option to prevent clearing a crash dump after saving it. It also attempts to avoid writing large stretches of zeros to crash dump files to save space and time. tcsh has been updated to version 6.10. The default value for the CVS_RSH variable (used by cvs(1)) is now ssh, rather than rsh. disklabel(8) now supports partition sizes expressed in kilobytes, megabytes, or gigabytes, in addition to sectors. Kerberos IV has been updated to 1.0.5. Heimdal has been updated to 0.3e. dump(8) now supports inheritance of the "nodump" flag down a hierarchy. The ISC DHCP client has been updated to 2.0pl5. stty(1) now has support for an "erase2" control character, so that both "delete" and "backspace" can be used to erase characters. split(1) now has the ability to split a file longer than 2GB. units(1) has received some updates and bugfixes. netstat(1) now keeps track of input and output packets on a per-address basis for each interface. netstat(1) now has a -W flag that tells it not to truncate addresses, even if they're too long for the column they're printed in. sockstat(1) now has -c and -l flags for listing connected and listening sockets, respectively. Many manual pages were improved, both in terms of their formatting markup and in their content. "lprm -" now works for remote printer queues. mergemaster(8) now sources an /etc/mergemaster.rc file and also prompts the user to run recommended commands (such as "newaliases") as needed. ftpd(8) now supports a -r flag for read-only mode and a -E flag to disable EPSV. It also has some fixes to reduce information leakage and the ability to specify compile-time port ranges. rc(8) now has an framework for handling dependencies between rc.conf(5) variables. The default TCP port range used by libfetch for passive FTP retrievals has changed; this affects the behavior of fetch(1), which has gained the -U option to restore the old behavior. portmap(8) now takes a -h option to indicate the IP addresses to which it should bind. This option may be specified multiple times and is typically necessary for multi-homed hosts. GNATS has been updated to 3.113. tail(1) now has the ability to work on files longer than 2GB. 2. Supported Configurations --------------------------- FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA and PCI bus based PC's, ranging from 386sx to Pentium class machines (though the 386sx is not recommended). Support for generic IDE drive configurations, various SCSI controller, network and serial cards is also provided. What follows is a list of all peripherals currently known to work with FreeBSD. Other configurations may also work, we have simply not as yet received confirmation of this. 2.1. Disk Controllers --------------------- IDE ATA Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 164x series MCA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. Adaptec 1510 series ISA SCSI controllers (not for bootable devices) Adaptec 152x series ISA SCSI controllers Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. Adaptec 2100S, 2400A, 3200S, and 3400S SCSI RAID controllers. Adaptec FSA family RAID controllers: Adaptec AAC-2622 Adaptec AAC-364 Adaptec AAC-3642 Dell PERC 2/QC Dell PERC 2/Si Dell PERC 3/Di Dell PERC 3/QC Dell PERC 3/Si HP NetRAID-4M AdvanSys SCSI controllers (all models). BusLogic MultiMaster controllers: [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] BusLogic MultiMaster "W" Series Host Adapters: BT-948, BT-958, BT-958D BusLogic MultiMaster "C" Series Host Adapters: BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, BT-540CF BusLogic MultiMaster "S" Series Host Adapters: BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, BT-542B BusLogic MultiMaster "A" Series Host Adapters: BT-742A, BT-542B AMI FastDisk controllers that are true BusLogic MultiMaster clones are also supported. The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F Microchannel (MCA) bus adapters are also supported. DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and SmartRAID IV SCSI/RAID controllers are supported. DPT SmartRAID V and VI SCSI RAID controllers: PM1554, PM2554, PM2654, PM2865, PM2754, PM3755, PM3757 AMI MegaRAID Express and Enterprise family RAID controllers: MegaRAID Series 418 MegaRAID Enterprise 1200 (Series 428) MegaRAID Enterprise 1300 (Series 434) MegaRAID Enterprise 1400 (Series 438) MegaRAID Enterprise 1500 (Series 467) MegaRAID Enterprise 1600 (Series 471) MegaRAID Elite 1500 (Series 467) MegaRAID Elite 1600 (Series 493) MegaRAID Express 100 (Series 466WS) MegaRAID Express 200 (Series 466) MegaRAID Express 300 (Series 490) MegaRAID Express 500 (Series 475) Dell PERC Dell PERC 2/SC Dell PERC 2/DC Dell PERC 3/DCL HP NetRAID-1si HP NetRAID-3si HP Embedded NetRAID Booting from these controllers is supported. Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x firmware: DAC960P DAC960PD DAC960PDU DAC960PL DAC960PJ DAC960PG AcceleRAID 150 AcceleRAID 250 eXtremeRAID 1100 Booting from these controllers is supported. EISA adapters are not supported. Mylex PCI to SCSI RAID controllers with 6.x firmware: AcceleRAID 160 AcceleRAID 170 AcceleRAID 352 eXtremeRAID 2000 eXtremeRAID 3000 Compatible Mylex controllers not listed should work, but have not been verified. 3ware Escalade ATA RAID controllers. All members of the 5000, 6000, and 7000 series are supported. SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: ASUS SC-200 Data Technology DTC3130 (all variants) Diamond FirePort (all) NCR cards (all) Symbios cards (all) Tekram DC390W, 390U and 390F Tyan S1365 NCR 53C500 based PC-Card SCSI host adapters: IO DATA PCSC-DV KME KXLC002(TAXAN ICD-400PN, etc.), KXLC004 Macnica Miracle SCSI-II mPS110 Media Intelligent MSC-110, MSC-200 NEC PC-9801N-J03R New Media Corporation BASICS SCSI Qlogic Fast SCSI RATOC REX-9530, REX-5572 (as SCSI only) TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters: Future Domain SCSI2GO IBM SCSI PCMCIA Card ICM PSC-2401 SCSI Melco IFC-SC RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A Qlogic Controllers and variants: Qlogic 1020, 1040 SCSI and Ultra SCSI host adapters Qlogic 1240 dual Ultra SCSI controllers Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD controllers Qlogic 12160 Ultra3 LVD controllers Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI controllers Performance Technology SBS440 ISP1000 variants Performance Technology SBS450 ISP1040 variants Performance Technology SBS470 ISP2100 variants Antares Microsystems P-0033 ISP2100 variants DTC 3290 EISA SCSI controller in 1542 emulation mode. Workbit Ninja SCSI-3 based PC-Card SCSI host adapters: Alpha-Data AD-PCS201 IO DATA CBSC16 With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including hard disks, optical disks, tape drives (including DAT and 8mm Exabyte), medium changers, processor target devices and CDROM drives. WORM devices that support CDROM commands are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW writing support is provided by cdrecord, which is in the ports tree. The following CD-ROM type systems are supported at this time: (cd) SCSI interface (also includes ProAudio Spectrum and SoundBlaster SCSI) (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary interface (562/563 models) (scd) Sony proprietary interface (all models) (acd) ATAPI IDE interface The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. UltraStor 14F, 24F and 34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controller. [ Note: There is work-in-progress to port the UltraStor driver to the new CAM SCSI framework, but no estimates on when or if it will be completed. ] Unmaintained drivers, they might or might not work for your hardware: (mcd) Mitsumi proprietary CD-ROM interface (all models) 2.2. Ethernet cards ------------------- Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec AIC-6915 Fast Ethernet controller chip, including the following: ANA-62011 64-bit single port 10/100baseTX adapter ANA-62022 64-bit dual port 10/100baseTX adapter ANA-62044 64-bit quad port 10/100baseTX adapter ANA-69011 32-bit single port 10/100baseTX adapter ANA-62020 64-bit single port 100baseFX adapter Allied-Telesis AT1700 and RE2000 cards Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 chipsets, including the following: 3Com 3c985-SX (Tigon 1 and 2) Alteon AceNIC 1000baseSX (Tigon 1 and 2) Alteon AceNIC 1000baseT (Tigon 2) DEC/Compaq EtherWORKS 1000 Farallon PN9000SX NEC Gigabit Ethernet Netgear GA620 (Tigon 2) Netgear GA620T (Tigon 2, 1000baseT) Silicon Graphics Gigabit Ethernet AMD PCnet/PCI (79c970 & 53c974 or 79c974) AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA. SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra. SMC Etherpower II. RealTek 8129/8139 Fast Ethernet NICs including the following: Allied Telesyn AT2550 Allied Telesyn AT2500TX Genius GF100TXR (RTL8139) NDC Communications NE100TX-E OvisLink LEF-8129TX OvisLink LEF-8139TX Netronix Inc. EA-1210 NetEther 10/100 KTX-9130TX 10/100 Fast Ethernet Accton "Cheetah" EN1207D (MPX 5030/5038; RealTek 8139 clone) SMC EZ Card 10/100 PCI 1211-TX Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX NetGear FA310-TX Rev. D1 Matrox FastNIC 10/100 Kingston KNE110TX Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs Accton EN1217 (98715A) Adico AE310TX (98715A) Compex RL100-TX CNet Pro120A (98713 or 98713A) CNet Pro120B (98715) NDC Communications SFA100A (98713A) SVEC PN102TX (98713) Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following: LinkSys EtherFast LNE100TX Version 2 Winbond W89C840F Fast Ethernet NICs including the following: Trendware TE100-PCIE VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet NICs including the following: Hawking Technologies PN102TX D-Link DFE-530TX AOpen/Acer ALN-320 Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs Sundance Technologies ST201 PCI Fast Ethernet NICs including the following: D-Link DFE-550TX SysKonnect SK-984x PCI Gigabit Ethernet cards including the following: SK-9841 1000baseLX single mode fiber, single port SK-9842 1000baseSX multimode fiber, single port SK-9843 1000baseLX single mode fiber, dual port SK-9844 1000baseSX multimode fiber, dual port Texas Instruments ThunderLAN PCI NICs, including the following: Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP Racore 8165 10/100baseTX Racore 8148 10baseT/100baseTX/100baseFX multi-personality ADMtek Inc. AL981-based PCI Fast Ethernet NICs ADMtek Inc. AN985-based PCI Fast Ethernet NICs ADMtek Inc. AN986-based USB Ethernet NICs including the following: LinkSys USB100TX Billionton USB100 Melco Inc. LUA-TX D-Link DSB-650TX SMC 2202USB CATC USB-EL1210A-based USB Ethernet NICs including the following: CATC Netmate CATC Netmate II Belkin F5U111 Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including the following: LinkSys USB10T Entrega NET-USB-E45 Peracom USB Ethernet Adapter 3Com 3c19250 ADS Technologies USB-10BT ATen UC10T Netgear EA101 D-Link DSB-650 SMC 2102USB SMC 2104USB Corega USB-T ASIX Electronics AX88140A PCI NICs, including the following: Alfa Inc. GFC2204 CNet Pro110B DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc) DEC/Intel 21143 based Fast Ethernet NICs, including the following: DEC DE500-BA Compaq Presario 7900 series built-in Ethernet D-Link DFE-570TX Kingston KNE100TX LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the following: Jaton Corporation XpressNet Fujitsu MB86960A/MB86965A, including the following: CONTEC C-NET(PC)C Ethernet Eiger Labs EPX-10BT Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 Ethernet PCMCIA Fujitsu Towa LA501 Ethernet HITACHI HT-4840-11 NextCom J Link NC5310 RATOC REX-5588, REX-9822, REX-4886, REX-R280 TDK LAK-CD021, LAK-CD021A, LAK-CD021BX HP PC Lan+ cards (model numbers: 27247B and 27252A). Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Intel InBusiness 10/100 PCI Network Adapter Intel PRO/100+ Management Adapter Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Novell NE1000, NE2000, and NE2100 Ethernet interface. PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA VT86C926. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C529 (MCA), 3C579, 3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), 3C590/592/595/900/905/905B/905C PCI, 3C556/556B MiniPCI, and EISA (Fast) Etherlink III / (Fast) Etherlink XL 3Com 3c980/3c980B Fast Etherlink XL server adapter 3Com 3cSOHO100-TX OfficeConnect adapter Crystal Semiconductor CS89x0-based NICs, including: IBM Etherjet ISA NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards, including the following: AR-P500 Ethernet card Accton EN2212/EN2216/UE2216(OEM) Allied Telesis CentreCOM LA100-PCM_V2 AmbiCom 10BaseT card BayNetworks NETGEAR FA410TXC Fast Ethernet CNet BC40 adapter COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD Compex Net-A adapter CyQ've ELA-010 D-Link DE-650/660 Danpex EN-6200P2 ELECOM Laneed LD-CDL/TX IO DATA PCLA/TE, PCET/TX, PCET/TX-R IBM Creditcard Ethernet I/II IC-CARD Ethernet/IC-CARD+ Ethernet Linksys EC2T/PCMPC100,EtherFast 10/100 PC Card (PCMPC100,V2,V3) Melco LPC-T/LPC2-T/LPC2-TX/LPC3-TX/LPC3-CLX NDC Ethernet Instant-Link National Semiconductor InfoMover NE4100 Network Everywhere Ethernet 10BaseT PC Card Planex FNW-3600-T Socket LP-E Surecom EtherPerfect EP-427 TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card Telecom Device SuperSocket RE450T Megahertz X-Jack Ethernet PC-Card CC-10BT Xircom CreditCard adapters(16bit) and workalikes Accton EN2226/Fast EtherCard (16-bit verison) Compaq Netelligent 10/100 PC Card Intel EtherExpress PRO/100 Mobile Adapter (16-bit verison) Xircom 10/100 Network PC Card adapter Xircom Realport card + modem(Ethernet part) Xircom CreditCard Ethernet 10/100 Xircom CreditCard 10Base-T "CreditCard Ethernet Adaptor IIps" (PS-CE2-10) Xircom CreditCard Ethernet 10/100 + modem (Ethernet part) National Semiconductor DP8393X (SONIC) Ethernet cards NEC PC-9801-83, -84, -103, and -104 NEC PC-9801N-25 and -J02R 2.3. FDDI --------- DEC FDDI (DEFPA/DEFEA) NICs 2.4. ATM -------- o ATM Host Interfaces - FORE Systems, Inc. PCA-200E ATM PCI Adapters - Efficient Networks, Inc. ENI-155p ATM PCI Adapters o ATM Signaling Protocols - The ATM Forum UNI 3.1 signaling protocol - The ATM Forum UNI 3.0 signaling protocol - The ATM Forum ILMI address registration - FORE Systems' proprietary SPANS signaling protocol - Permanent Virtual Channels (PVCs) o IETF "Classical IP and ARP over ATM" model - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - RFC 1577, "Classical IP and ARP over ATM" - RFC 1626, "Default IP MTU for use over ATM AAL5" - RFC 1755, "ATM Signaling Support for IP over ATM" - RFC 2225, "Classical IP and ARP over ATM" - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, "A Distributed ATMARP Service Using SCSP" o ATM Sockets interface 2.5. 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 BB1004 4-Port serial card (Modems NOT supported) Boca IOAT66 6-Port serial card (Modems supported) Boca BB1008 8-Port serial card (Modems NOT supported) Boca BB2016 16-Port serial card (Modems supported) Comtrol Rocketport card. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, ONboard 4/16 and Brumby. Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound and Roland MPU-401 sound cards. (snd driver) Advance Asound 100, 110 and Logic ALS120 C-Media CMI-8x38 Crystal Semiconductor CS461x/462x/428x Crystal Semiconductor CS4281 ENSONIQ AudioPCI ES1370/1371 ESS ES1868, ES1869, ES1879 and ES1888 ESS Maestro-1, Maestro-2, and Maestro-2E ESS Maestro-3/Allegro ForteMedia fm801 Gravis UltraSound MAX/PnP MSS/WSS Compatible DSPs NeoMagic 256AV/ZX OPTi 931/82C931 SoundBlaster, Soundblaster Pro, Soundblaster AWE-32, Soundblaster AWE-64 Trident 4DWave DX/NX VIA Technologies VT82C686A Yamaha DS1 and DS1e (newpcm driver) Connectix QuickCam Matrox Meteor Video frame grabber Creative Labs Video Spigot frame grabber Cortex1 frame grabber Hauppauge Wincast/TV boards (PCI) STB TV PCI Intel Smart Video Recorder III Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. PS/2 mice Standard PC Joystick X-10 power controllers GPIB and Transputer drivers. Genius and Mustek hand scanners. Xilinx XC6200 based reconfigurable hardware cards compatible with the HOT1 from Virtual Computers (www.vcc.com) Support for Dave Mills experimental Loran-C receiver. Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes 3COM 3crwe737A AirConnect Wireless LAN PC Card Cabletron RoamAbout 802.11 DS Compaq WL100 Corega KK Wireless LAN PCC-11, PCCA-11 Laneed Wireless card ELECOM Air@Hawk/LD-WL11/PCC Farallon Skyline 11Mbps Wireless ICOM SL-1100 Intel PRO/Wireless 2011 LAN PC Card IO Data WN-B11/PCM Melco Airconnect WLI-PCM-L11 NCR WaveLAN/IEEE 802.11 NEC Wireless Card CMZ-RT-WP, PC-WL/11C, PK-WL001 PLANEX GeoWave/GW-NS110 TDK LAK-CD011WL Note: the ISA versions of these adapters are actually PCMCIA cards combined with an ISA to PCMCIA bridge card, so both kinds of devices work with the same driver. Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, PCI and ISA adapters are all supported. Cisco Systems Aironet 340 Series (includes 340, 341, and 342 models) 11Mbps 802.11 wireless NIC Webgear Aviator 2.4GHz wireless adapters. Toshiba Mobile HDD MEHDD20A (Type II) Panasonic Flash ATA BN-040ABP3 Hewlett Packard M820e (CD-writer) 3. Obtaining FreeBSD -------------------- You may obtain FreeBSD in a variety of ways: 3.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 freebsd-admin@FreeBSD.org for more details if you'd like to become an official mirror site. If you do not have access to the Internet and electronic mail is your only recourse, then you may still fetch the files by sending mail to `ftpmail@ftpmail.vix.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! 3.2. CDROM ---------- FreeBSD 4.x-RELEASE CDs may be ordered on CDROM from: BSDi / Walnut Creek CDROM 4041 Pike Lane, Suite D Concord CA 94520 USA +1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) Or via the Internet from orders@cdrom.com or http://www.cdrom.com. Their current catalog can be obtained via ftp from: ftp://ftp.cdrom.com/cdrom/catalog Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely separate). 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. 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. 4. Upgrading from previous releases of FreeBSD ---------------------------------------------- If you're upgrading from a previous release of FreeBSD, most likely it's 3.0 and there may be some issues affecting you, depending of course on your chosen method of upgrading. There are two popular ways of upgrading FreeBSD distributions: o Using sources, via /usr/src o Using sysinstall's (binary) upgrade option. Please read the UPGRADE.TXT file for more information, preferably before beginning an upgrade. 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 or use the CGI script at http://www.FreeBSD.org/send-pr.html. 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: freebsd-bugs@FreeBSD.org Note that send-pr itself is a shell script that should be easy to move even onto a totally different system. We much prefer if you could use this interface, since it make it easier to keep track of the problem reports. However, before submitting, please try to make sure whether the problem might have already been fixed since. Otherwise, for any questions or tech support issues, please send mail to: freebsd-questions@FreeBSD.org If you're tracking the -stable development efforts, you should definitely join the -stable mailing list, in order to keep abreast of recent developments and changes that may affect the way you use and maintain the system: freebsd-stable@FreeBSD.org Additionally, being a volunteer effort, we are always happy to have extra hands willing to help - there are already far more desired enhancements than we'll ever be able to manage by ourselves! To contact us on technical matters, or with offers of help, please send mail to: freebsd-hackers@FreeBSD.org Please note that these mailing lists can experience *significant* amounts of traffic and if you have slow or expensive mail access and are only interested in keeping up with significant FreeBSD events, you may find it preferable to subscribe instead to: freebsd-announce@FreeBSD.org All of the mailing lists can be freely joined by anyone wishing to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword `help' on a line by itself somewhere in the body of the message. This 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. Acknowledgments ------------------ FreeBSD represents the cumulative work of many hundreds, if not thousands, of individuals from around the world who have worked very hard to bring you this release. For a complete list of FreeBSD project staffers, please see: http://www.FreeBSD.org/handbook/staff.html or, if you've loaded the doc distribution: file:/usr/share/doc/handbook/staff.html Special thanks also go to the many thousands of FreeBSD users and testers all over the world, without whom this release simply would not have been possible. The FreeBSD Project .... link:../../[Release Home] diff --git a/website/content/en/releng/charter.adoc b/website/content/en/releng/charter.adoc index ed36d8acdf..1deac709f5 100644 --- a/website/content/en/releng/charter.adoc +++ b/website/content/en/releng/charter.adoc @@ -1,18 +1,18 @@ --- title: "Charter for the Release Engineering Team" sidenav: developers ---- +--- = Charter for the Release Engineering Team The Release Engineering Team has the following responsibilities: * Setting and publishing the release schedule for Official Project releases of FreeBSD. * Documenting and formalizing the RE procedures, so that the process can continually be reviewed and improved. This includes more documentation about the ports cluster and package split procedures. * Setting and publishing "Code Freeze" dates, and acting as a change-review committee to decide which changes may be made to a branch during a code freeze. This includes freezes for HEAD when approaching a .0 release as well as the traditional `releng/*` code freeze pending a -STABLE release. * Creation and maintenance of `releng/*` branches of the `src/` tree. This includes final authority over what commits are made (and remain in) the -STABLE branch prior to the branching of a release branch. * Working with core and/or the FreeBSD Foundation to codify a set of guidelines that vendors must meet if they are to be allowed to call a product "FreeBSD", or an "Official FreeBSD release". * Testing and integrating required packages from the ports collection onto the official project release media. Portmgr@ is responsible for managing the `ports/` code freeze and providing a complete package build of the re-distributable ports. re@ is then responsible for splitting those packages onto different ISOs as required by the release media. re@ is ultimately responsible for ensuring that all of the required packages are available on the FreeBSD release media, but portmgr@ cooperation is essential. * Coordinating with the FreeBSD Documentation Project, to ensure that a consistent set of documentation is provided for the release. This includes the ability to request that large disruptive changes not be made to the documentation set in the weeks leading up to a release. * Coordinating with the security officer team to ensure that pending FreeBSD releases are not affected by recently disclosed vulnerabilities. Also, approximately 1 week after a release, change approval control of release branches (`releng/X.Y/`) is transferred from the release engineers to the security-officer team. The exact transfer date is to be worked out by the two parties once it is clear that the release was a success. A heads up message should be sent to developers@ at that time. * Sending out messages to announce@FreeBSD.org on behalf of the project to announce new releases of FreeBSD. diff --git a/website/content/en/releng/dst_info.adoc b/website/content/en/releng/dst_info.adoc index 1aeb7f1431..31f63b1b7e 100644 --- a/website/content/en/releng/dst_info.adoc +++ b/website/content/en/releng/dst_info.adoc @@ -1,20 +1,20 @@ --- title: "Daylight Savings Time Changes for 2007" sidenav: developers ---- +--- = Daylight Savings Time Changes for 2007 This is a summary of the information about the change in Daylight Savings Time rules and how the change affects FreeBSD releases. In 2005 several countries, including the United States of America and Canada, passed legislation changing when Daylight Savings Time begins and ends. That change takes effect in 2007. For the time zones affected by the change Daylight Savings Time will begin on March 11th (instead of April 1st) and end on November 4th (instead of October 28th). FreeBSD uses `/etc/localtime` to control the conversion of the system's internal representation of time (based on UTC) to the format appropriate for the local time zone. That file gets copied from one of the files in `/usr/share/zoneinfo` by the tzsetup(8) command, usually as part of the initial installation procedure. The change in Daylight Savings Time rules affects the files in `/usr/share/zoneinfo` for the time zones affected by the legislation passed in 2005. Of the release branches supported by the FreeBSD Security Team as of February 2007, FreeBSD-6.2 and FreeBSD-5.5 have up to date zoneinfo files. FreeBSD-6.1 has correct zoneinfo files for time zones in the United States of America but out of date zoneinfo files for some of the other countries affected (for example Canada). An Errata Notice will be released shortly to update the zoneinfo files in FreeBSD-6.1. For the development branches HEAD, RELENG_6, RELENG_5, and RELENG_4 all have the correct zoneinfo files in them. NOTE: `/etc/localtime` currently does not get updated when the cvsup/buildworld/etc system update procedures are used. If a machine was installed using one of the releases not listed above it will probably have an outdated `/etc/localtime` file. That file can be updated by running tzsetup(8). For older systems no longer under support the misc/zoneinfo port can be installed to update the `/usr/share/zoneinfo` files, followed by running tzsetup(8) to update `/etc/localtime`. diff --git a/website/content/en/search/opensearch/_index.adoc b/website/content/en/search/opensearch/_index.adoc index 22f5fc9370..85208aa431 100644 --- a/website/content/en/search/opensearch/_index.adoc +++ b/website/content/en/search/opensearch/_index.adoc @@ -1,24 +1,24 @@ --- title: "FreeBSD OpenSearch Plugins" sidenav: about ---- +--- = FreeBSD OpenSearch Plugins Firefox put a few popular search sites in the Search Bar in the upper-right corner of Firefox. Click on a item to add the _FreeBSD Search Services_ to your Firefox Search Bar. == By the FreeBSD.org web site * link:../../opensearch/man.xml[FreeBSD Manual Pages] * link:man-freebsd-release-ports.xml[FreeBSD + Ports Manual Pages] * link:message-id.xml[FreeBSD Mailing List Message-ID Search] == External Plugins * link:markmail.xml[FreeBSD Mailing List Search by MarkMail] External help links: https://addons.mozilla.org/en-US/firefox/search/?category=search-tools&sort=recommended%2Cusers&type=extension[Firefox Search Engines] link:../[Return to the search page] ''''' diff --git a/website/content/en/search/search-mid.adoc b/website/content/en/search/search-mid.adoc index 76f19d8144..b5f5be3bb4 100644 --- a/website/content/en/search/search-mid.adoc +++ b/website/content/en/search/search-mid.adoc @@ -1,14 +1,14 @@ --- title: "Mailing list Message-ID Search" sidenav: about ---- +--- = Mailing list Message-ID Search {{< form-search-mid-id >}} {{< form-search-mid-message >}} You can search only the mail header keywords *Message-ID*, *Resent-Message-id*, *In-Reply-to*, and *References*. A Message-ID looks like <199802242058.MAA24843@monk.via.net>. No other mail header keywords are supported. The Message-ID database will be updated every hour. link:../#mailinglists[Full text mailing list archives]. diff --git a/website/content/en/search/searchhints.adoc b/website/content/en/search/searchhints.adoc index b005ba2874..8dfd8b5411 100644 --- a/website/content/en/search/searchhints.adoc +++ b/website/content/en/search/searchhints.adoc @@ -1,21 +1,21 @@ --- title: "Searching Hints" sidenav: about ---- +--- = Searching Hints == If you got lots of irrelevant results... . 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 words has to appear in a message. To find only messages with all three words, change the search to "quantum and hard and drives" . 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. == If you do not think you received everything you should have... . 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". . Words with varying suffixes can be wildcarded. Searching for "drive*" will pick up words such as drive, drives, driver, drivers and so on. . 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. ''''' link:../[Return to the search page]