diff --git a/en/news/1996/index.sgml b/en/news/1996/index.sgml index 91bfc58405..8e178ea180 100644 --- a/en/news/1996/index.sgml +++ b/en/news/1996/index.sgml @@ -1,54 +1,54 @@ - - + %includes; News Home'> %newsincludes; ]> &header;

December 1996

November 1996

&newshome; &footer; diff --git a/en/news/1997/index.sgml b/en/news/1997/index.sgml index 02273fba90..e2e70cf6bc 100644 --- a/en/news/1997/index.sgml +++ b/en/news/1997/index.sgml @@ -1,272 +1,272 @@ - - + %includes; News Home'> %newsincludes; ]> &header;

December 1997

November 1997

October 1997

September 1997

August 1997

July 1997

June 1997

May 1997

April 1997

March 1997

February 1997

January 1997

&newshome; &footer; diff --git a/en/news/1998/index.sgml b/en/news/1998/index.sgml index 999c14fe0e..46316ba04d 100644 --- a/en/news/1998/index.sgml +++ b/en/news/1998/index.sgml @@ -1,242 +1,242 @@ - - + %includes; News Home'> %newsincludes; ]> &header;

December 1998

November 1998

October 1998

September 1998

August 1998

July 1998

May 1998

April 1998

March 1998

February 1998

January 1998

&newshome; &footer; diff --git a/en/news/1999/index.sgml b/en/news/1999/index.sgml index 04361001c9..f37cdfac3d 100644 --- a/en/news/1999/index.sgml +++ b/en/news/1999/index.sgml @@ -1,370 +1,370 @@ - - + %includes; News Home'> %newsincludes; ]> &header;

December 1999

October 1999

September 1999

August 1999

July 1999

June 1999

May 1999

April 1999

March 1999

February 1999

January 1999

&newshome; &footer; diff --git a/en/news/2000/index.sgml b/en/news/2000/index.sgml index 6de076aa52..ab135f5f0b 100644 --- a/en/news/2000/index.sgml +++ b/en/news/2000/index.sgml @@ -1,456 +1,456 @@ - - + %includes; News Home'> %newsincludes; ]> &header;

December 2000

November 2000

October 2000

September 2000

August 2000

July 2000

June 2000

May 2000

April 2000

March 2000

February 2000

January 2000

&newshome; &footer; diff --git a/en/news/press-rel-1.sgml b/en/news/press-rel-1.sgml index cdf0d0b3b6..699705ae42 100644 --- a/en/news/press-rel-1.sgml +++ b/en/news/press-rel-1.sgml @@ -1,59 +1,59 @@ - - + %includes; %newsincludes; ]> &header;

FreeBSD Used to Generate Spectacular Special Effects

Concord, CA, April 22, 1999: 32 Dual-Processor FreeBSD systems were used to generate a large number of special effects in the cutting edge Warner Brothers film, The Matrix.

Manex Visual Effects used 32 Dell Precision 410 Dual P-II/450 Processor systems running FreeBSD as the core CG Render Farm. Charles Henrich, the senior systems administrator at Manex, says, "We came to a point in the production where we realized we just did not have enough computing power on our existing SGI infrastructure to get through the 3-D intensive sequences. It was at that point we decided on going with a FreeBSD based solution, due to the ability to get the hardware quickly as well as the reliability and ease of administration that FreeBSD provides us. Working with Dell, we purchased 32 of these systems on a Wednesday, and had them rendering in production by Saturday afternoon. It was truly an amazing effort on everyone's part, and I don't believe it would've been possible had we chosen to go with any other Operating System solution."

The FreeBSD operating system is a powerful, completely open-source system based on the Berkeley Software Distribution of UNIX. It is available free of charge from numerous Internet websites and also on CD-ROM from Walnut Creek CDROM, and includes thousands of ported applications including 3-D graphics rendering and many other equally powerful tools. FreeBSD is optimized for use on the Intel x86 processor line that is the heart of today's versatile commodity personal computers. Infinitely customizable, FreeBSD is at the heart of such Internet powerhouse applications as Yahoo! and U.S. West because it is unencumbered by commercial license restrictions and can be copied and modified freely.

For more information on FreeBSD, visit http://www.FreeBSD.org/ and http://www.wccdrom.com/. For more information about Manex Visual Effects, please visit http://www.mvfx.com/ .

&footer; diff --git a/en/news/press-rel-2.sgml b/en/news/press-rel-2.sgml index f9ada6a418..2145f5442b 100644 --- a/en/news/press-rel-2.sgml +++ b/en/news/press-rel-2.sgml @@ -1,89 +1,89 @@ - - + %includes; %newsincludes; ]> &header;

Complete XML Development System Integrated with FreeBSD

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

FreeBSD's Ports system and multitasking architecture makes it easy for an SGML/XML developer to download and install all the latest versions of the tools and reference material he needs to develop SGML and XML formatting languages and documents, and the online Internet mailing lists help him learn and keep up-to-date with the evolving XML implementation.

FreeBSD is a full-featured open-source operating system which runs on virtually all Intel x86-based personal computers. Its 580 page "Handbook" has recently been completely done over into DocBook format, and it is a living example of an evolving document built with SGML tools. The Handbook is available on the Internet at:

The FreeBSD Documentation Project is also making available the "FreeBSD Documentation Project Primer" to make it as painless as possible for newcomers to contribute to the FreeBSD Documentation Set. Much of the information in the primer is appropriate to all SGML/XML users, and is freely available. The primer, which is constantly being updated by the Documentation Project team, can be found at:

Features of the Document Project SGML/XML System include:

The FreeBSD Documentation Project is actively migrating from the LinuxDoc DTD to the DocBook DTD, and has been providing feedback to the DocBook maintainers regarding new features and possible implementations for the past year. For more information about the FreeBSD Documentation Project, please contact the freebsd-doc@FreeBSD.org mailing list.

The FreeBSD operating system is available on the Internet from the master FreeBSD website and from various mirror systems around the world, and it can also be obtained on convenient CDROMs from Walnut Creek CDROM. Information on all of these options is available through:

&footer; diff --git a/en/news/press-rel-3.sgml b/en/news/press-rel-3.sgml index 50ed0ef7b8..678980ce4b 100644 --- a/en/news/press-rel-3.sgml +++ b/en/news/press-rel-3.sgml @@ -1,90 +1,90 @@ - - + %includes; %newsincludes; ]> &header;

BSD Community Welcomes Apple's New Open Source Operating System

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

"We're very pleased to have Apple's participation in the BSD community," said Jordan Hubbard, chairman of the USENIX convention's Freenix track and co-founder of the FreeBSD Project. "As more smart businesses discover the incredible free resource that is BSD software, they'll realize that contributing to open source development is in their best interest."

According to Herb Peyerl of the NetBSD Project, "Our interaction with Apple on the Darwin project has been extremely rewarding for NetBSD and is the kind of open cooperation of which we would like to see more."

"Leveraging the twenty-year BSD heritage allows Apple developers to concentrate on adding a unique user experience to the solid, robust foundation of the BSD code," according to Avie Tevanian, Apple Computer's senior vice president of Software Engineering. "We believe that by embracing the open source movement with our Darwin software, the result will be better products for millions of Mac customers worldwide. The BSD code in Darwin is an essential part of our operating system strategy."

This type of reciprocation is a return to the original software development model that was universal in the early days of computing, before PCs. Wilfredo Sanchez, technical lead for the Darwin Project, will speak on Darwin at this week's Freenix track, a series of programs at Usenix devoted exclusively to this sort of open source software development.

About NetBSD and FreeBSD

NetBSD and FreeBSD are open source operating systems based on the last public release of BSD UNIX, 4.4BSDLite2. Each effort has kept up with the latest technologies in processors and software architectures. While having different priorities, the BSD development teams share a friendly competitive rivalry, spurring each other on to produce better product for their worldwide users. Over the twenty years of development, a huge base of software has been developed around BSD -- including much of the Internet infrastructure -- enabling the OS to be used effectively in almost any computing application. The open development model means there are no secrets, creating a worldwide understanding of the code which enables BSD developers to build on the efforts of prior developers without the hassles endemic to proprietary operating systems and applications.

For More Information, Contact:

The FreeBSD Project
Concord, California
925-682-7859
freebsd-questions@FreeBSD.org
http://www.FreeBSD.org

The NetBSD Project
C/O Charles M. Hannum
81 Bromfield Rd, #2
Somerville, MA 02144
mindshare@netbsd.org
http://www.netbsd.org

&footer; diff --git a/en/news/press-rel-4.sgml b/en/news/press-rel-4.sgml index b0cd22b02a..93f04c38ab 100644 --- a/en/news/press-rel-4.sgml +++ b/en/news/press-rel-4.sgml @@ -1,233 +1,233 @@ - - + %includes; %newsincludes; ]> &header;

FOR IMMEDIATE RELEASE

BSD SUPPLIERS UNITE TO DELIVER THE WORLD'S MOST POPULAR INTERNET OPERATING SYSTEMS

The New BSDI To Deliver Renowned BSD Operating System Technologies And Back The Rapidly Growing FreeBSD Open Source Community

Colorado Springs, Colo., March 9, 2000: Berkeley Software Design, Inc. (BSDI) announced today that it has merged with Walnut Creek CDROM, the distributor of the popular FreeBSD operating system. As a merged company, the new BSDI unites the leading developers and suppliers of the Berkeley Software Distribution operating system BSDI will develop and deliver advanced BSDŽ Internet operating systems and platforms, while providing the open source FreeBSD Project with technology, backing and expanded support.

BSD operating systems run some of the Internet's most highly trafficked sites and largest service providers, including Yahoo!, Microsoft's Hotmail and UUNET, an MCI WorldCom company. BSD and Linux are today's fastest-growing operating systems, according to Survey.com, the leading eResearch company.

BSD operating system, networking and Internet technologies have achieved widespread acceptance in the Internet infrastructure. Over 100,000 commercial Internet customers run BSD operating systems on more than 2,000,000 BSD-powered servers. It is estimated that nine out of 10 Internet Service Providers (ISPs) and Network Service Providers (NSPs) as well as 15 percent of all Internet sites run BSD systems. BSD operating systems are also embedded in innovative Internet appliances from Intel, IBM, Lucent, F5 Labs, Hitachi and many others.

BSDI also announced that Yahoo! Inc. will take an equity interest in the new company. BSDI will leverage the equity interest to execute on its plan to build a bridge between open source innovation and commercial requirements. The equity position will be used to grow BSDI's presence as a leading provider of the most advanced Internet operating systems for the Internet infrastructure.

BSDI intends to form a united front for the BSD operating systems. The company will deliver, support and enhance both BSD/OS and FreeBSD. BSDI and the FreeBSD Project are jointly evaluating the technology and market requirements for merging parts of the code bases for the two operating systems.

The New BSDI's Leadership

"BSD technologies have evolved from a long history of advanced computing at the core of the Internet," said Dr. Marshall Kirk McKusick, BSDI's chairman of the board. "The new BSDI will further enrich the popular BSD computing platform, which is already widely deployed throughout the world." McKusick was a founding member of the University of California at Berkeley's Computer Systems Research Group (CSRG) and is widely acknowledged as a key early contributor to the open source movement.

To drive the new BSDI's vision, roadmap and continued profitable growth, Gary J. Johnson has been appointed chief executive officer. Johnson is an experienced technology executive who has served in a variety of senior management, sales, marketing and operations capacities with leading Silicon Valley companies including Tandem Computers (Compaq), Convergent Technologies (Unisys) and SCO. Johnson most recently served as president of ClickService Software, a leading provider of e-commerce, customer relationship management (CRM) software.

"Innovation in the operating systems arena relies heavily on work in the open source community," said Johnson. "To date, Linux suppliers, such as Red Hat Software and VA Linux, have captured impressive attention for the open source approach to development. At the core of the Internet, however, BSD technologies are pervasive. The new BSDI will be working closely with the open source community to ensure that advanced BSD Internet operating systems and platforms continue to meet the ever-increasing demands for Internet servers, applications, appliances and other elements vital to the Internet infrastructure."

In addition to his current responsibilities, Mike Karels, BSDI's vice president of engineering and the former chief system architect and principal programmer for the University of California at Berkeley's CSRG, plans to join the architectural team for the FreeBSD Project. Karels, who replaced Sun Microsystems co-founder Bill Joy at the CSRG, is recognized as one of the world's foremost developers of Unix internals and TCP/IP networking software.

"BSD technologies have contributed to Yahoo!'s continued success by offering the reliability and level of service necessary to ensure the availability and scalability we need to keep Yahoo! up and running around the clock regardless of increasing user demand," said David Filo, co-founder and Chief Yahoo, Yahoo! Inc.

BSDI Continues To Deliver BSD/OS And FreeBSD; Expands And Accelerates FreeBSD Open Source Initiatives

The new BSDI will sell and support FreeBSD, BSD/OS, BSDI Internet Super Server and value-added BSD product lines through its worldwide sales channels to Internet infrastructure providers, appliance developers and business users. BSDI will offer commercially supported BSD operating systems and related applications, Internet appliance platforms, technical support and services, open source software development, and consulting services. The company will deliver its BSD Internet and networking technologies on leading microprocessor platforms, including Intel, SPARC, Alpha, PowerPC and StrongARM.

BSDI will continue to develop, enhance and distribute BSD/OS and FreeBSD according to the terms of the business-friendly, unencumbered Berkeley software license, which encourages development for open source software projects, embedded systems, specialized applications, information appliances and other operating system-enabled products.

BSDI will expand and accelerate Walnut Creek CDROM's FreeBSD open source initiatives by sharing BSD/OS technical innovations with the FreeBSD Project and by providing this open source project with operational and technical support, marketing and funding. BSDI will continue to distribute packaged versions of FreeBSD and also plans to develop value-added products based on FreeBSD as well as to provide technical support, consulting services, educational services and training for FreeBSD customers. These steps are expected to promote and invigorate the BSD open source computing movement. The FreeBSD Project develops the popular FreeBSD operating system and aggregates and integrates contributed software from more than 5,000 developers worldwide.

Internet and Open Source Leaders Support The New BSDI

"We are delighted that BSDI is backing the FreeBSD open source community," said Jordan Hubbard, chief evangelist and co-founder of the FreeBSD Project. "The new BSDI has considerable expertise in commercializing, maintaining, distributing and supporting the world's most advanced Internet operating systems. We are excited and greatly looking forward to partnering with BSDI's chief developers, especially Mike Karels and other original members of UC Berkeley's CSRG, to accelerate operating system, networking and Internet innovation."

"Open source operating systems like BSD offer better technology and more choices to the customer," said Eric Raymond, president of the Open Source Initiative. "I expect BSDI to prove yet again that the open source and business communities can really to do great things together, driving the industry forward as dramatically as the Internet."

"Our research shows that BSD and Linux will increase their share of enterprise servers by between 100 percent and 500 percent over the next two years in the fundamental applications that run U.S. business," said Dave Trowbridge, senior analyst at Survey.com. "This new company will help ensure that BSD gets its place in the sun, which its rich heritage and solid technical foundations deserve."

About the Berkeley Software Distribution Operating System

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

About the FreeBSD Project

FreeBSD is a popular open source operating system developed by the FreeBSD Project and its worldwide team, consisting of more than 5,000 developers funneling their work to 185 "committer" developers. It is available free of charge from ftp.FreeBSD.org and also distributed as a shrink-wrap software product through CompUSA, Fry's, Borders, Ingram, FreeBSDmall.com and others. FreeBSD includes thousands of ported applications, including the most popular Web, Internet and E-mail applications. FreeBSD is distributed under the Berkeley Software Distribution license, which means that it can be copied and modified freely. For more information about the FreeBSD Project, visit www.FreeBSD.org.

About Walnut Creek CDROM

Walnut Creek CDROM was founded in 1991 and began publishing Linux software in 1992, and BSD software in 1993. The company has a long history of working closely with the free software community and providing funding, staffing and other resources for open source projects. Walnut Creek CDROM publishes numerous software titles, including FreeBSD and Slackware, the most BSD-like version of Linux.

About Berkeley Software Design, Inc. (BSDI)

Leading BSD developers founded Berkeley Software Design, Inc. in 1991 to commercialize BSD technologies and continue the Berkeley Unix tradition of robust, reliable and extremely secure Internet operating systems for network computing. By merging Berkeley Software Design, Inc. and Walnut Creek CDROM, BSDI becomes the world's leading supplier of advanced Internet operating systems for the Internet infrastructure. Contact BSDI at info@BSDI.com or at www.BSDI.com or call 1-719-593-9445 (toll free: 1-800-800-4273).

# # #

BSD is a registered trademark and BSD/OS and BSDI are trademarks of Berkeley Software Design, Inc. Yahoo! and the Yahoo! logo are registered trademarks of Yahoo! Inc. All trademarks mentioned in this document are the property of their respective owners.

Contact:
Kevin Rose
BSDI
801-553-8166
kgr@bsdi.com

Jordan Hubbard
FreeBSD Project
925-691-2863
jkh@FreeBSD.org

Brigid Fuller
ZNA Communications
831-425-1581
brigid@zna.com

&footer; diff --git a/en/news/press-rel-5.sgml b/en/news/press-rel-5.sgml index 7e0db0868c..359d72b6d6 100644 --- a/en/news/press-rel-5.sgml +++ b/en/news/press-rel-5.sgml @@ -1,135 +1,135 @@ - - + %includes; %newsincludes; ]> &header;

New FreeBSD Core Team Elected

BSD Conference, Monterey, CA, October 18, 2000 The FreeBSD Project announced today the election of a new Core Team, the project's management board. This marks the first occasion on which the team has been selected by means of an election among the project's developers. Joining the Core team as new members are Greg Lehey, Warner Losh, Mike Smith, and Robert Watson. Re-elected members are Satoshi Asami, David Greenman, Jordan Hubbard, Doug Rabson, and Peter Wemm.

FreeBSD Project co-founder and continuing Core Team member Jordan Hubbard expressed excitement over the results, "For the first time since the FreeBSD project was formed, open elections have determined the composition of its core team and set an important precedent whereby any developer can now become part of the project's leadership." The new core team also well-represents FreeBSD's diverse and highly skilled group of international developers, with expertise ranging from RAID file system and device-driver development to extensive security backgrounds.

New Core Team members were elected from and by the FreeBSD committers team, the formal development staff of the FreeBSD project. Committers have direct access to the FreeBSD source repository, and perform the majority of software development associated with the project. Until this point, the Core Team was a self-selected board providing architectural and administrative direction.

This summer, the committers voted to move to a democratic model allowing the project to adapt to the changing development requirements of the open source operating system community. However, with over half of the prior Core Team re-elected from the old team, strong continuity exists.

Departing Core Team member Poul-Henning Kamp said, "I'm very proud of what we have done together in the Core Team over the last 8 years. The new Core, and the fact that they are elected by the committers, means that the project will be much more responsive to change in the future."

The changing of the guard in project leadership comes amid good feelings, Kamp indicated: all past Core members will continue on with the project with increased emphasis on development, "Now I get to spend more time on the FreeBSD source code instead of on project management."

Elected Core Team Members

Satoshi Asami is a co-founder and CTO of DecorMagic, Inc., and manages the FreeBSD Ports Collection.

David Greenman is a co-founder of the FreeBSD Project and is currently President of TeraSolutions, Inc., a company that manufactures Internet servers and RAID storage systems.

Jordan Hubbard is a co-founder of the FreeBSD Project as well as its public relations officer and release engineer. He is also Vice President for Open Source Solutions at BSDi.

Greg Lehey is an Open Source Researcher with Linuxcare; he has spent most of his professional career in Germany, where he worked for computer manufacturers such as Univac, Tandem, and Siemens-Nixdorf. He is the author of the Vinum volume management and RAID software for FreeBSD, has been involved in the FreeBSD SMPng project, and is the author of Porting Unix Software and The Complete FreeBSD.

Warner Losh has been porting NetBSD's pccard code to FreeBSD and has been FreeBSD Security Officer for the past two years.

Doug Rabson is a co-founder of Qube Software Ltd., which specializes in 3D graphics technology. His work on FreeBSD includes the alpha and ia64 ports, and he was the main architect for FreeBSD's device driver framework.

Mike Smith is Principal Engineer in BSDi's Open Source Solutions group and has been active in the FreeBSD developer community as a developer resource, OEM liaison, sometime architect and device driver author.

Robert Watson is a research scientist at NAI Labs, working on network and operating system security research. His contributions to the FreeBSD Project include work on trusted operating system extensions (TrustedBSD), security architecture, and work on the security-officer team.

Peter Wemm has been involved with FreeBSD since the early days of the ISP Industry in Australia and has since relocated to the US to work as a Software Engineer for Yahoo!, Inc. His involvement in FreeBSD includes management of the FreeBSD source code repository and kernel development.

About FreeBSD

FreeBSD is a liberally-licensed open source operating system with its origins in BSD Net/2 and 4.4 Lite, the Berkeley Software Distributions developed at the University of California at Berkeley until 1994. It is developed and maintained by a global organization of paid and volunteer contributors. FreeBSD is distinguished by its high performance networking and file system support, and is widely used among Internet service providers, including industry-recognized companies such as Yahoo!, above.net, and Verio. FreeBSD is also frequently used as a platform for embedded networking devices, including products from IBM, Inktomi, Juniper Networks, and Network Alchemy - a Nokia Company.

More information may be found at http://www.FreeBSD.org/.

Press Contact

Jordan Hubbard
The FreeBSD Project
925-682-7859
jkh@FreeBSD.org

# # #

BSD is a registered trademark of Berkeley Software Design, Inc. Other trademarks are property of their respective owners. BSD technologies were originally developed by the University of California, Berkeley and its contributors.

&footer; diff --git a/en/news/pressreleases.sgml b/en/news/pressreleases.sgml index ce8f588cf6..f59745e33d 100644 --- a/en/news/pressreleases.sgml +++ b/en/news/pressreleases.sgml @@ -1,60 +1,60 @@ - - + %includes; %newsincludes; ]> &header;
October 18, 2000 : New Core
First FreeBSD Core Team Elections

March 9, 2000
BSD Suppliers Unite to Deliver the World's Most Popular Internet Operating Systems

June 7, 1999
BSD Community Welcomes Apple's New Open Source Operating System.

April 29, 1999
Complete XML Development System Integrated with FreeBSD.

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

&footer; diff --git a/en/news/sou1999.sgml b/en/news/sou1999.sgml index 4c2c83f579..2fc4d3cd75 100644 --- a/en/news/sou1999.sgml +++ b/en/news/sou1999.sgml @@ -1,374 +1,374 @@ - - + %includes; ]> &header;

From Jordan Hubbard <jkh@FreeBSD.ORG>, Sunday January 10th, 1999.

Well, it's another year behind us, folks, and probably high time for another state of the union report!

Ahem... I'm never quite sure how to word these things since I'm always reminded of a U.S. president sitting in front of fireplace, trying to sound down-home and folksy for the corn growing states, or perhaps England's Queen on Christmas day, giving her usual somber-yet-hopeful address on how things went for Britannia during the previous year and what everyone should perhaps think about for the next. Neither one of those is really me, basically, so perhaps I'll just cut to the chase and focus on the most pertinent lessons (and objectives) to come out of the year 1998 for me.

1998 was, of course, the year that the Internet got bigger (no surprise), various "internetpraneurs" (gag) got richer and FreeBSD's user base, as measured by the ftp download stats grew at its usual 200-300% rate. More companies also entered the FreeBSD arena, either offering add-ons for or solutions incorporating FreeBSD, and our PR machine, as flimsy and low-key as it often is, managed to ratchet things up another notch. All in all, it was a very good year for FreeBSD and I don't think that even the most paranoid of us could claim otherwise - Microsoft took one in the shorts, we got bigger and just a bit better known, life was good.

Well, mostly. Whipping off my rosy glasses for a second, I can also say that there were still a number of rocks in the road and unexpected bends that left us not always in the best of control there. While downloads have gone up, CD sales aren't quite following suit since the whole CD market in general is suffering from increased Internet availability and its erosion of some of the CD's fundamental advantages. We still did quite well, considering the market's gradual implosion, but it would be foolish to continue to rely on a single CD product to provide the kinds of subsidies that have been steadily oiling the project's gears (we more than doubled the size of the FreeBSD.org computing cluster, for example, and significantly enlarged our developer equipment grant program in 1998, all things which cost $$$). It's fairly obvious that Walnut Creek CDROM will need to increase the number of products it offers if it wishes to remain an effective player in the FreeBSD game and we must continue, as a project, to be flexible in exploring all types of relationships with those who may now have a vested interest in FreeBSD's success. Things are well past the point where we can do everything that needs to be done as a serious and "grown up" solution just on good will and volunteerism alone.

With that in mind, sites like the FreeBSD Mall have been set up to try and market a wider variety of FreeBSD-related products and we've also begun exploring relationships with various companies who can derive measurable value from any PR campaign that enhances FreeBSD's reputation (translation: we want them to help pay for it :). As many people have somewhat bitterly pointed out by now, this business has become a 10% technology and 90% perception equation as far as the direction in which people stampede is concerned, and hate them for the mindless little sheep that they are, you still need to understand people's tendencies and behavioral patterns when it comes to dealing with anything they don't really understand. We've done a great job on the technology, we really have (and should be proud of that), but all too frequently we just throw up our hands over the perception issue and tell people to think whatever the hell they want to. Bad techies! Myopic techies! :-)

What can we do to change this in 1999? Well, I've also heard our advocate corps calling for logistical support ("Backup! We need some backup here!!") and I've listened to them, part of my project for the new years being to get more digital daemon imagery made available (which I have already commissioned), more glossies with various handy comparison charts on them ("FreeBSD and NT", "FreeBSD and Solaris", "FreeBSD and Linux", etc) and more newsletters for passing out to people. We can also produce more marketing periphenalia like buttons, stickers, new T-shirts, etc. to give people a wider array of stuff to proudly point to in support of the "emerging FreeBSD phenomenon." If we can manage to raise more money for PR, we can also perhaps buy some of these items in bulk to use as give-aways in various promotional deals. Other than that, I'm always open to suggestions. We need to do more effective PR, that much is inarguable, it's only a question of picking our targets for maximum effect given a limited operating budget.

The core team:

1998 also ended with a bit of a bang as far as FreeBSD's project management was concerned, frustration with a mostly recumbent core team goading a couple of bearded Danish Vikings into staging a midnight raid on -current, ruthlessly culling the weak and the lame from the source tree. Unfortunately, some of those weak or lame bits of code were still in use at the time and, with no prior public warning having been given, it did not exactly leave the various followers of -current with the feeling that the event was going to be the highlight of their Christmas season. Their complaints led, in turn, to something of a constitutional crisis within core, the rival factions each accusing one another of either impeding progress or using cowboy tactics to achieve that progress, and each faction had its legitimate points just as it had its wholly unreasonable ones. Coming out of this, various suggestions were bandied about concerning how we might put together a "better core team" to which such things simply did not happen (or, if they did, would not be our fault since we'd all be long gone :-) and many of these suggested cures were eventually deemed, quite rightly, to be worse than the disease. So what did we learn from the exercise then?

First off, I think everyone is now pretty much in agreement that these sorts of drive-by shootings are just not an option for the future, no matter what the justification. Anyone who contemplates a major addition or removal of functionality from the source tree MUST communicate those intentions well in advance and give the readership of -current, -stable or -announce (the former two depending on the branch the changes affect and the latter on the extent of the changes) ample time to respond. If there is a conclusively negative response to a proposed change, it just doesn't happen until and unless the proposal somehow manages to win people over through sheer dint of persuasive argument in its favor. If it's more a mixed bag of reactions, or there is little reaction at all, the developer is free to proceed at his or her discretion but still never without advance notice.

Second, in reaction to the various proposals put forward to either gut core or have core elected by popular vote, let me just say that we're not going to do that. There are probably several people currently in core who would gladly step aside and retire if they felt that adequate replacements had been found and the project was in good hands, but none of us like the scenario where anyone is overtly forced out of core. It's just not a reasonable way of going about it when so many less painful alternatives exist, and I, for one, would far rather simply grow core and let the inactive members fall off when they themselves have come to a decision that they have nothing left to contribute at a "core level", resignation from core having not stopped several folks from remaining as effective committers or making other valuable contributions.

We're a free software project and nobody's paid to be in core, no matter how seriously we may be tempted to take the whole core thing sometimes, and we need to remember that all of this started as a bunch of folks who simply wanted to work together in creating something useful and interesting. The day we lose that kind of informal atmosphere of productivity over politics is the day that something pretty fundamental goes out at the center of core and also the day that I'll retire from it myself, handing my hat to a replacement and wishing everyone the very best of luck.

I can also only sound a similar cautionary note about the idea of electing core from the user base, or with committers serving as a kind of "electoral college", as nice and democratic an idea as that might sound. The FreeBSD core team does not represent a democratically selected body and was, in fact, very carefully put together in a very non-democratic way. We picked core with the specific intention that it represent as diverse a set of hard-core FreeBSD evangelist/developers as we knew how to find and we've continued to add people using the same criteria.

In bringing someone into core, we don't look at whether they've been winning popularity contests lately or won the Programming Olympiad 3 times in a row, we ask ourselves: "Does this person bring a unique talent or viewpoint to the group? Will the resulting whole be greater than the sum of its parts?" These are our two most overriding concerns and, in fact, are the only grounds on which we've ever felt it necessary to actually ask for someone's resignation from core. We can tolerate quite a bit from people but not when it impacts core's fundamental ability to work together or seeks to undermine the very diversity of opinion we've worked so hard to cultivate. It's good to be an effective group of decision makers as a core team, and we do have our moments (both ways), but sometimes it's even better to know simply when to stay out of the way and just make sure the train stays roughly on the tracks. We've prevented a lot more stupidity through having such a diverse and carefully selected core team than I think we've ever caused and I do not trust the democratic process to leave us with the same thing after a few elections.

Core is also continuing to work on drafting some internal documents which cover, in much better detail, just what our rules as committers are, those superseding any "core member privileges", governing how large-scale code removal and addition operations should be carried out. We'll post something to committers just as soon as we finally flesh it out to our mutual satisfaction but, in a nutshell, it basically just insists that people need to be warned before such changes happen and that the owner of a given body of code should be given first say as to whether or not it's time to kill it in the name of obsolescence or redundancy. Finally, we are looking at the general issue of communication inside and outside core and the question of whether or not to bring in some new member(s) at this time. That discussion is ongoing and I'll do my best to keep everyone up to date on that as things progress.

Release numbering:

Other decisions on the horizon concern returning to our former practice of using "major" version numbers for branches and "minor" numbers for releases, the revision number field only being used to denote point-releases which were done for some reason significant enough to merit such a special release. This means that the next release will be 3.1, not 3.0.1, and the new branch will be 4.0-current instead of 3.1-current. Is this just a marketing ploy? No, it's not, though marketing has indeed been a frequent casualty of our current numbering scheme.

We have frequently made fairly large changes between our "point releases", jumps like 2.2.5->2.2.6 and 2.2.6->2.2.7 being a lot bigger than most folks gave them credit for given that it was just one little revision number being changed. This one simple facet of human nature reduced the effectiveness of these releases and under-sold the work being done by our developers to substantially improve every release we do, regardless of which branch it's on.

This is not a trend which seems to be reversing itself and so I feel quite safe in saying that 3.1 will be a "full release" over 3.0 in its own right and not merely the "3.0.1" which conveys such a different impression. It's also very important to note that since our branches seem to typically last from 12-18 months these days, no matter what we try in attempting to kill a branch earlier, a major version bump (4.0) is entirely merited for something which won't see full release status until sometime in the year 2000. This will make the marketing people happy since they won't have such an uphill battle on number perception and it will make the users happy since they'll get a clearer picture of what changed in, say, 3.1 to 3.2 vs 3.1 to 3.1.1 (which might be an important security update). It will also make this particular developer happy since I'll have the revision number space back again for doing point releases. It's a win and so we're going to do it. 3.0.1 is dead, long live 3.1! :)

Technology:

This last year also saw a successful transition to ELF from a.out format and a new kernel loadable module scheme which allows modules to be read in without a runtime dependency on /usr/bin/ld. We also got a new boot loader (with a forth interpreter!) to aggregate a "kernel" at boot time. These are both powerful new mechanisms and, coupled with some new stuff which will be coming in 1999, should give us a far more dynamic and extensible system than we've ever had before.

Not to be overlooked is also our new SCSI CAM system, giving us more robust behavior with large drive arrays and supporting more of the high-end SCSI controllers, or the support for multiple processors on the x86. We made considerable progress all across the board with the release of 3.0, finally reaching a point with the DEC Alpha architecture port where people starting worrying more about the packages collection than they did about working kernels or a /usr/src which built. That represents considerable progress towards "genuine usefulness" and I hope that 1999 will see a fully desktop capable release of FreeBSD/axp (to say nothing of a server capable one), various difficulties with X server technology making the Alpha desktop a unique milestone in its own right, especially if it's on an ARC or AlphaBIOS machine. 1999 may also see the early release of a SPARC port, though it's still far too early to say anything more definite than that. Join the sparc@FreeBSD.org mailing list if you want to follow these efforts.

IPv6 and IPSec were also hotly debated topics in 1998, FreeBSD's refusal to back any specific implementation being cited by many as an example of core's over-conservatism in action. Happily for everyone, our wait-and-see attitude proved to be the right one when the two major "competing" groups, KAME and INRIA, finally agreed to merge their implementations. We have, in turn, committed to adopting this merged implementation and have several people from the KAME/INRIA groups on the FreeBSD development team who will be importing and maintaining this code as it becomes available.

There is also substantial work underway with the VM system and the filesystem code, much of which is either being tested quietly in small groups (Dillon/Dyson/Greenman) or is awaiting the 4.0 branch event, still scheduled for January 15th, 1999. In other areas, we have Kazu's very welcome total redesign of the console driver coming into -current along with USB support, courtesy of Nick Hibma and others. This is just to name a few of the projects underway and I don't mean to slight anyone by not mentioning theirs directly, these are just 3 ongoing projects right off the top of my head. We seem to be gaining a lot of technical momentum, and that's great, just so long as we can also keep our heads during the times where not everyone is in total agreement about which technical direction to take.

Tech support:

A point which should also be obvious to everyone yet still somehow requires frequent reinforcement is the fact that we need to maintain participation in this project as something which is also enjoyable for the developer/participants or they will just as quickly go away again and stop giving each and every one of us the benefit of their volunteer labor (on which a dollar value could not even be put). This is something which each and every one of our users needs to be aware of, at least somewhere in the back of their minds, for those times when they're tempted to start thinking of FreeBSD as just another shrink-wrap solution from Software, Inc. and start treating project members like personal employees. Those looking for actual FreeBSD employees should send mail to jobs@FreeBSD.org and indicate how much money they're willing to pay, otherwise don't do it.

I don't mean to come across so harshly here that people don't even bother asking us for help, I'm simply saying that those users who avail themselves of the various FreeBSD volunteer tech support mechanisms out there (mail, news, irc, etc) should always understand that asking another perfect stranger for help is just not much different from asking a random person on the street for a dollar. If you want to get free handouts, you'd better at the very least learn to ask politely and when to take "no" for an answer! :-) I've seen a lot of abuse of the various tech support forum volunteers this last year and it frankly sucks. People just need to be more considerate and stop regarding free tech support as a god-given right rather than a very special privilege. If you want on-demand tech support, go to www.freebsdmall.com and order yourself a tech support contract. You get what you pay for! :)

Looking forward:

What do I see ahead for 1999? Well, assuming that we don't all vanish in some pre-millennial holocaust, I see more interesting new features, improved marketing, more commercial interest, more magazine articles and press attention, basically more of the same if we can just try to stay reasonably well focused on what we need to do and not get distracted into chasing weird desktop dreams or suddenly become overly minimalist or kitchen-sink biased in /usr/src, continuing to chart the middle course we're more famous for. The FreeBSD core team, one year older and hopefully a little wiser, needs to continue keeping a light but steady hand on the tiller, relying on our developers as usual to provide much of the actual motive force behind FreeBSD.

Our users also need to become more involved and I'm hoping that 1999 will be the year when a lot more local user groups and other self-help type of organizations are formed. The Handbook and FAQ are documents which are getting better, hopefully another trend we'll see continue into 1999 as Nik Clayton, our fearless new Documentation Project leader, continues at the helm. We still have to remember, however, that for many users the handbook and FAQ docs are just not enough.

Linux has succeeded largely because of a large grass-roots support and evangelism network which allows it to reach such people and communicate the message to them. If FreeBSD's own users want to see FreeBSD doing better against whomever they most perceive as its competition, and 1998 was certainly a year where I heard a lot of complaining about this, then they're going to simply have to get off their collective duffs and put in more of this kind of work. When was the last time a bunch of FreeBSD users got together to hand out FreeBSD literature at a Microsoft product launch, for example, or held an install-a-thon at a local computer show?

The Linux folks do things like that all the time, apparently, whereas only a very few die-hard FreeBSD users currently do it now, so why not help these people out? Join the advocacy@FreeBSD.org mailing list and discuss your plans there so that others with more enthusiasm than ideas can also learn from and perhaps help you with yours. Write short articles for the new advocacy sites like www.daemonnews.org or www.freebsdrocks.com and help promote the success of BSD evangelical publications.

Phrases like "this is your FreeBSD" and "it all depends on you" may seem shop-worn and trite, but they're also unfortunately still true when there's so few of us and so many of you. If FreeBSD is to really continue to succeed in 1999, it will only be with substantial user participation and that means you, users! Start a local user group, donate some of your older CD releases to the local library, try and convince a local small business or ISP to use FreeBSD, these are just a few of the many things that can be done if you're truly interested in putting some energy into FreeBSD and ideas for what to do will be the least of your worries if you're truly motivated.

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

&footer; diff --git a/en/news/status/status.sgml b/en/news/status/status.sgml index 8130f88e3d..886f7c143f 100644 --- a/en/news/status/status.sgml +++ b/en/news/status/status.sgml @@ -1,47 +1,47 @@ - - + %includes; ]> &header;

One of the benefits of the FreeBSD development model is a focus on centralized design and implementation, in which the operating system is maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all the work going on in the tree.

The FreeBSD Bi-Monthly Development Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information.

These status reports may be reproduced in whole or in part, as long as the source is clearly identified and appropriate credit given.

2001

&footer; diff --git a/en/platforms/ia64.sgml b/en/platforms/ia64.sgml index a8f78bf4b6..a74e335fc2 100644 --- a/en/platforms/ia64.sgml +++ b/en/platforms/ia64.sgml @@ -1,74 +1,74 @@ - - + %includes; ]> &header;

This page contains information about porting FreeBSD to Intel's upcoming IA-64 architecture.

Latest News

What needs to be done

A lot of work needs to be done on the Cygnus IA-64 toolchain. At the moment it looks like the various Linux camps doing IA-64 development have splintered off without merging their respective changes back into Cygnus' tree. Anyone working on toolchain issues should coordinate with David Obrien.

HP's Linux IA-64 simulator is currently less than ideal for FreeBSD development. Marcel Moolenaar is currently working on some of these issues.

FreeBSD/ia64 Specific Links

Other Links of Interest

IA-64 Documentation

Software Tools

Related Projects

&footer; diff --git a/en/platforms/x86-64.sgml b/en/platforms/x86-64.sgml index 60f18f4a7a..39e4f424f7 100644 --- a/en/platforms/x86-64.sgml +++ b/en/platforms/x86-64.sgml @@ -1,63 +1,63 @@ - - + %includes; ]> &header; BSD Daemon swinging a sledge hammer

This page contains information about porting FreeBSD to AMD's upcoming x86-64 ``Hammer'' architecture.

Latest News

What needs to be done

David O'Brien is working on modifying the AMD sponsored x86-64 GCC for FreeBSD's needs. Anyone working on toolchain issues should coordinate with David O'Brien.

AMD's SimNow! x86-64 simulator is currently less than ideal for FreeBSD development due to its slowness.

FreeBSD/x86-64 Specific Links

Other Links of Interest

x86-64 Documentation

Software Tools

Related Projects

&footer; diff --git a/en/releases/2.0.5R/announce.sgml b/en/releases/2.0.5R/announce.sgml index 9d7e9a96be..39cc91041a 100644 --- a/en/releases/2.0.5R/announce.sgml +++ b/en/releases/2.0.5R/announce.sgml @@ -1,115 +1,115 @@ - - + %includes; ]> - + &header;

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

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

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

Highlights of this release are:

And many other new features and bug fixes.

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

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

The usual locations:

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

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

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

Thank you!

Jordan


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

Yes, you have guessed it. As a result of the recent feedback we have had about the 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.cdrom.com and freefall.cdrom.com with a version of boot.flp which will fix the following problems:

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

Release Home &footer; diff --git a/en/releases/2.0.5R/notes.sgml b/en/releases/2.0.5R/notes.sgml index 8b70f6254e..b2486d3993 100644 --- a/en/releases/2.0.5R/notes.sgml +++ b/en/releases/2.0.5R/notes.sgml @@ -1,764 +1,764 @@ - - + %includes; ]> - + &header;
                                  RELEASE NOTES
                                     FreeBSD
                                  Release 2.0.5
 
 1. Technical overview
 ---------------------
 
 FreeBSD is a freely available, full source 4.4 BSD Lite based release
 for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
 primarily on software from U.C. Berkeley's CSRG group, with some
 enhancements from NetBSD, 386BSD, and the Free Software Foundation.
 
 Since our release of FreeBSD 2.0 some 8 months ago, the performance,
 feature set, and stability of FreeBSD has improved dramatically.  The
 largest change is a revamped VM system with a merged VM/file buffer
 cache that not only increases performance, but reduces FreeBSD's
 memory footprint, making a 4MB configuration a more acceptable
 minimum.  Other enhancements include full NIS client and server
 support, transaction TCP support, dial-on-demand PPP, an improved SCSI
 subsystem, early ISDN support, support for FDDI and Fast Ethernet
 (100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
 narrow) and many hundreds of bug fixes.
 
 We've also taken the comments and suggestions of many of our users to
 heart and have attempted to provide what we hope is a more sane and
 easily understood installation process.  Your feedback on this
 (constantly evolving) process is especially welcome!
 
 In addition to the base distributions, FreeBSD offers a new ported
 software collection with some 270 commonly sought-after programs.  The
 list of ports ranges from http (WWW) servers, to games, languages,
 editors and almost everything in between.  The entire ports collection
 requires only 10MB of storage, all ports being expressed as "deltas"
 to their original sources.  This makes it much easier for us to update
 ports, and greatly reduces the disk space demands made by the older
 1.0 ports collection.  To compile a port, you simply change to the
 directory of the program you wish to install, type make and let the
 system do the rest.  The full original distribution for each port you
 build is retrieved dynamically off of CDROM or a local ftp site, so
 you need only enough disk space to build the ports you want.  (Almost)
 every port is also provided as a pre-compiled "package" which can be
 installed with a simple command (pkg_add) by those who do not wish to
 compile their own ports from source.  See the file:
         /usr/share/FAQ/Text/ports.FAQ
 for a more complete description of the ports collection.
 
 
 Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD
 has changed almost entirely.  A new port from the Berkeley 4.4 code
 base was done, which brought the legal status of the system out of the
 shadows with the blessing of Novell (the new owners of USL and UNIX).  The
 port to 4.4 has also brought in a host of new features, filesystems
 and enhanced driver support.  With our new unencumbered code base, we
 have every reason to hope that we'll be able to release quality
 operating systems without further legal encumbrance for some time to
 come!
 
 FreeBSD 2.0.5 represents the culmination of 2 years of work and many
 thousands of man hours put in by an international development team.
 We hope you enjoy it!
 
 A number of additional documents which you may find very helpful in
 the process of installing and using FreeBSD may also be found in
 the "FAQ" directory, either under /usr/share/FAQ on an installed
 system or at the top level of the CDROM or FTP distribution from
 where you're reading this file.  Please consult FAQ/Text/ROADMAP
 for a brief description of the resources provided by the FAQ directory.
 
 For a list of contributors and a general project description, please see
 the file "CONTRIB.FreeBSD" which should be bundled with your binary
 distribution.
 
 Also see the "REGISTER.FreeBSD" file for information on registering
 with the "Free BSD user counter".   This counter is for ALL freely
 available variants of BSD, not just FreeBSD, and we urge you to register
 yourself with it.
 
 The core of FreeBSD does not contain DES code which would inhibit its
 being exported outside the United States.  There is an add-on package
 to the core distribution, for use only in the United States, that
 contains the programs that normally use DES.  The auxiliary packages
 provided separately can be used by anyone.   A freely (from outside the
 U.S.) exportable European distribution of DES for our non-U.S. users also
 exists and is described in the FreeBSD FAQ.
 
 If password security for FreeBSD is all you need, and you have no
 requirement for copying encrypted passwords from different hosts
 (Suns, DEC machines, etc) into FreeBSD password entries, then
 FreeBSD's MD5 based security may be all you require!  We feel that our
 default security model is more than a match for DES, and without any
 messy export issues to deal with.  If you're outside (or even inside)
 the U.S., give it a try!
 
 
 1.1 What's new in 2.0.5?
 ------------------------
 
 The following features were added or substantially improved between
 the release of 2.0 and this 2.0.5 release.  In order to facilitate
 better communication, the person, or persons, responsible for each
 enhancement is noted.  Any questions regarding the new functionality
 should be directed to them first.
 
 KERNEL:
 
 Merged VM-File Buffer Cache
 ---------------------------
 A merged VM/buffer cache design greatly enhances overall system
 performance and makes it possible to do a number of more optimal
 memory allocation strategies that were not possible before.
 
 Owner:                  David Greenman (davidg@FreeBSD.org) and
                         John Dyson (dyson@implode.root.com)
 
 
 Network PCB hash optimization
 -----------------------------
 For systems with a great number of active TCP connections (WEB and ftp
 servers, for example), this greatly speeds up the lookup time required
 to match an incoming packet up to its associated connection.
 
 Owner:                  David Greenman (davidg@FreeBSD.org)
 
 
 Name cache optimization
 -----------------------
 The name-cache would cache all files of the same name to the same bucket,
 which would put for instance all ".." entries in the same bucket.  We added
 the parent directory version to frustrate the hash, and improved the 
 management of the cache in various other ways while we were at it.
 
 Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
                         David Greenman (davidg@FreeBSD.org)
 
 
 Less restrictive swap-spaces
 ----------------------------
 The need to compile the names of the swap devices into the kernel has been
 removed.  Now swapon will accept any block devices, up to the maximum
 number of swap devices configured in the kernel.
 
 Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
                         David Greenman (davidg@FreeBSD.org)
 
 
 Hard Wired SCSI Devices
 -----------------------
 Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers
 to SCSI devices as they were probed, allowing a SCSI device failure to
 possibly change unit number assignment and prevent filesystems on
 still functioning disks from mounting.  Hard wiring allows static
 allocation of unit numbers (and hence device names) to scsi devices
 based on SCSI ID and bus.  SCSI configuration occurs in the kernel
 config file.  Samples of the configuration syntax can be found in the
 scsi(4)>
 man page or the LINT kernel config file.
 
 Owner:                  Peter Dufault (dufault@hda.com)
 Sources involved:       sys/scsi/* usr.sbin/config/*
 
 
 Slice Support
 -------------
 FreeBSD now supports a "slice" abstraction which makes it more
 completely interoperable with other operating system partitions.  This
 support will allow FreeBSD to inhabit DOS extended partitions.
 
 Owner:                  Bruce Evans (bde@FreeBSD.org)
 Sources involved:       sys/disklabel.h sys/diskslice.h sys/dkbad.h
                         kern/subr_diskslice.c kern/subr_dkbad.c
                         i386/isa/diskslice_machdep.c
                         i386/isa/wd.c scsi/sd.c dev/vn/vn.c
 
 
 Support for Ontrack Disk Manager Version 6.0
 --------------------------------------------
 Support has been added for disks which use Ontrack Disk Manager.  The
 fdisk program does NOT know about it however, so make all changes
 using the install program on the boot.flp or the Ontrack Disk Manager
 tool under DOS.
 
 Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
 
 
 Bad144 is back and working
 --------------------------
 Bad144 works again, though the semantics are slightly different than
 before in that the bad-spots are kept relative to the slice rather
 than absolute on the disk.
 
 Owner:                  Bruce Evans (bde@FreeBSD.org)
                         Poul-Henning Kamp (phk@FreeBSD.org)
 
 
 NEW DEVICE SUPPORT:
 
                         SCSI and CDROM Devices
 
 Matsushita/Panasonic (Creative) CD-ROM driver
 ---------------------------------------------
 The Matsushita/Panasonic CR-562 and CR-563 drives are now supported
 when connected to a Sound Blaster or 100% compatible host adapter.  Up
 to four host adapters are supported for a total of 16 CD-ROM drives.
 The audio functions are supported, along with access to the raw (2352 byte) 
 data frames of any compact disc.  Audio discs may be played using Karoke
 variable speed functions.
 
 Owner:                  Frank Durda IV   bsdmail@nemesis.lonestar.org
 Sources involved:       isa/matcd
 
 
 Adaptec 2742/2842/2940 SCSI driver
 ----------------------------------
 The original 274x/284x driver has evolved considerably since the 2.0
 release.  We now offer full support for the 2940 series as well as the
 Wide models of these cards.  The arbitration bug (as well as many
 others) that caused the driver problems with fast devices has been
 corrected and there is even experimental tagged queuing support
 (kernel option "AHC_TAGENABLE").  John Aycock has also released the
 sequencer code under a "Berkeley style" copyright making the driver
 entirely clean of the GPL.
 
 Owner:                  Justin Gibbs (gibbs@FreeBSD.org)
 Sources involved:       isa/aic7770.c pci/aic7870.c i386/scsi/*
                         sys/dev/aic7xxx/*
 
 
 NCR5380/NCR53400 SCSI ("ProAudio Spectrum") driver
 --------------------------------------------------
 Owner:                  core
 Submitted by:           Serge Vakulenko (vak@cronyx.ru)
 Sources involved:       isa/ncr5380.c
 
 
 Sony CDROM driver
 -----------------
 Owner:                  core
 Submitted by:           Mikael Hybsch (micke@dynas.se)
 Sources involved:       isa/scd.c
 
 
                         Serial Devices
 
 SDL Communications Riscom/8 Serial Board Driver
 -----------------------------------------------
 Owner:                  Andrey Chernov (ache@FreeBSD.org)
 Sources involved:       isa/rc.c isa/rcreg.h
 
 
 Cyclades Cyclom-y Serial Board Driver
 -------------------------------------
 Owner:                  Bruce Evans (bde@FreeBSD.org)
 Submitted by:           Andrew Werple (andrew@werple.apana.org.au) and
                         Heikki Suonsivu (hsu@cs.hut.fi)
 Obtained from:          NetBSD
 Sources involved:       isa/cy.c
 
 
 Cronyx/Sigma sync/async serial driver
 -------------------------------------
 Owner:                  core
 Submitted by:           Serge Vakulenko
 Sources involved:       isa/cronyx.c            
 
 
 
                         Networking
 
 Diskless booting
 ----------------
 Diskless booting in 2.0.5 is much improved.  The boot-program is in
 src/sys/i386/boot/netboot, and can be run from an MSDOS system or
 burned into an EPROM.  Local swapping is also possible.  WD, SMC, 3COM
 and Novell ethernet cards are currently supported.
 
 
 DEC DC21140 Fast Ethernet driver
 --------------------------------
 This driver supports any of the numerous NICs using the DC21140 chipset 
 including the 100Mb DEC DE-500-XA and SMC 9332.
 
 Owner:                  core
 Submitted by:           Matt Thomas (thomas@lkg.dec.com)
 Sources involved:       pci/if_de.c pci/dc21040.h
 
 
 DEC FDDI (DEFPA/DEFEA) driver
 -----------------------------
 Owner:                  core
 Submitted by:           Matt Thomas (thomas@lkg.dec.com)
 Sources involved:       pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h
 
 
 3Com 3c505 (Etherlink/+) NIC driver
 -----------------------------------
 Owner:                  core
 Submitted by:           Dean Huxley (dean@fsa.ca)
 Obtained from:          NetBSD
 Sources involved:       isa/if_eg.c
 
 
 Fujitsu MB86960A family of NICs driver
 -------------------------------------
 Owner:                  core
 Submitted by:           M.S. (seki@sysrap.cs.fujitsu.co.jp)
 Sources involved:       isa/if_fe.c
 
 
 Intel EtherExpress driver
 -------------------------
 Owner:                  Rodney W. Grimes (rgrimes@FreeBSD.org)
 Sources involved:       isa/if_ix.c isa/if_ixreg.h
 
 
 3Com 3c589 driver
 -----------------
 Owner:                  core
 Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
                         Seiji Murata (seiji@mt.cs.keio.ac.jp) and
                         Noriyuki Takahashi (hor@aecl.ntt.jp)
 Sources involved:       isa/if_zp.c
 
 
 IBM Credit Card Adapter driver
 ------------------------------
 Owner:                  core
 Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
 Sources involved:       isa/pcic.c isa/pcic.h
 
 
 EDSS1 and 1TR6 ISDN interface driver
 ------------------------------------
 Owner:                  core
 Submitted by:           Dietmar Friede (dfriede@drnhh.neuhaus.de) and
                         Juergen Krause (jkr@saarlink.de)
 Sources involved:       gnu/isdn/*
 
 
                         Miscellaneous Drivers
 
 Joystick driver
 ---------------
 Owner:                  Jean-Marc Zucconi (jmz@FreeBSD.org)
 Sources involved:       isa/joy.c
 
 
 National Instruments "LabPC" driver
 -----------------------------------
 Owner:                  Peter Dufault (dufault@hda.com)
 Sources involved:       isa/labpc.c
 
 
 WD7000 driver
 -------------
 Owner:                  Olof Johansson (offe@ludd.luth.se)
 
 
 Pcvt Console driver
 -------------------
 Owner:                  Joerg Wunsch (joerg@FreeBSD.org)
 Submitted by:           Hellmuth Michaelis (hm@altona.hamburg.com)
 Sources involved:       isa/pcvt/* usr.sbin/pcvt/*
 
 
 BSD-audio emulator for VAT driver
 ---------------------------------
 Owner:                  Amancio Hasty (ahasty@FreeBSD.org) and
                         Paul Traina (pst@FreeBSD.org)
 Sources involved:       isa/sound/vat_audio.c isa/sound/vat_audioio.h
 
 
 National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver
 --------------------------------------------------------
 Owner:                  core
 Submitted by:           Fred Cawthorne (fcawth@delphi.umd.edu)
 Sources involved:       isa/gpib.c isa/gpib.h isa/gpibreg.h
 
 
 Genius GS-4500 hand scanner driver
 ----------------------------------
 Owner:                  core
 Submitted by:           Gunther Schadow (gusw@fub46.zedat.fu-berlin.de)
 Sources involved:       isa/gsc.c isa/gscreg.h
 
 
 CORTEX-I Frame Grabber
 ----------------------
 Owner:                  core
 Submitted by:           Paul S. LaFollette, Jr.
 Sources involved:       isa/ctx.c isa/ctxreg.h
 
 
 Video Spigot video capture card
 -------------------------------
 Owner:                  Jim Lowe
 
 
 
 1.2 Experimental features
 -------------------------
 
 The unionfs and LFS file systems are known to be severely broken in
 2.0.5.  This is in part due to old bugs that we haven't had time to
 resolve yet and the need to update these file systems to deal with the
 new VM system.  We hope to address these issues in a later release of
 FreeBSD.
 
 FreeBSD now supports running iBCS2 compatible binaries (currently SCO
 UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).  The iBCS2
 emulator is in its early stages, but it is functional, we haven't been
 able to do exhaustive testing (lack of commercial apps), but almost
 all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10
 for SCO. Further testing is 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 <ats@FreeBSD.org>
         Andrey A. Chernov <ache@FreeBSD.org>
         Bruce Evans <bde@FreeBSD.org>
         David Greenman <davidg@FreeBSD.org>
         Garrett A. Wollman <wollman@FreeBSD.org>
         Gary Palmer <gpalmer@FreeBSD.org>
         Geoff Rehmet <csgr@FreeBSD.org>
         Jack Vogel <jackv@FreeBSD.org>
         John Dyson <dyson@FreeBSD.org>
         Jordan K. Hubbard <jkh@FreeBSD.org>
         Justin Gibbs <gibbs@FreeBSD.org>
         Paul Richards <paul@FreeBSD.org>
         Poul-Henning Kamp <phk@FreeBSD.org>
         Rich Murphey <rich@FreeBSD.org>
         Rodney W. Grimes <rgrimes@FreeBSD.org>
         Satoshi Asami <asami@FreeBSD.org>
         Søren Schmidt <sos@FreeBSD.org>
 
 Special mention to:
 
         Walnut Creek CDROM, without whose help (and continuing support)
         this release would never have been possible.
 
         Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
         drive.
 
         Additional FreeBSD helpers and beta testers:
 
         J.T. Conklin                            Julian Elischer
         Frank Durda IV                          Peter Dufault
         Sean Eric Fagan                         Jeffrey Hsu
         Terry Lambert                           L Jonas Olsson
         Chris Provenzano                        Dave Rivers
         Guido van Rooij                         Steven Wallace
         Atsushi Murai                           Scott Mace
         Nate Williams
 
         And everyone at Montana State University for their initial support.
 
 
 Jordan would also like to give special thanks to Poul-Henning Kamp and
 Gary Palmer, both of whom put in long hours helping him to construct
 the new installation utility.  Poul, being a proud new father, was
 especially pressed for time and yet somehow managed to put in
 a significant amount of effort anyway.  This release could not have
 happened without him!  Thank you both!
 
 Thanks also to everyone else who helped, especially those not
 mentioned, and we sincerely hope you enjoy this release of FreeBSD!
 
 
                         The FreeBSD Core Team
 
 Id: RELNOTES.FreeBSD,v 1.7 1995/05/28 19:49:57 jkh Exp 
 

Release Home &footer; diff --git a/en/releases/2.0/announce.sgml b/en/releases/2.0/announce.sgml index ac5ef4634b..06adedcd22 100644 --- a/en/releases/2.0/announce.sgml +++ b/en/releases/2.0/announce.sgml @@ -1,156 +1,156 @@ - - + %includes; ]> &header;

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

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

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

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

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

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

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

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

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

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

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

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

(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]

Release Home &footer; diff --git a/en/releases/2.0/credits.sgml b/en/releases/2.0/credits.sgml index 21858a5af3..0534cff74a 100644 --- a/en/releases/2.0/credits.sgml +++ b/en/releases/2.0/credits.sgml @@ -1,213 +1,213 @@ - - + %includes; ]> - + &header;
 			   FreeBSD 2.0
 		         Contributor List
 
 
 
 Derived Software Contributors:
 
 This software was originally derived from William F. Jolitz's 386BSD
 release 0.1, though almost none of the original 386BSD specific code
 remains.  This software has been essentially reimplemented on top of
 4.4 BSD Lite, from the Computer Science Research Group (CSRG) at
 the University of California, Berkeley and associated academic
 contributors.
 
 There are also portions of NetBSD that have been integrated into FreeBSD
 as well, and we would therefore like to thank all the contributors
 to NetBSD for their work.  Despite some occasionally rocky moments in
 the relations between the two groups, we both want essentially the same
 thing:  More BSD based operating systems on people's computers!  We
 wish the NetBSD group every success in their 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 <ats@g386bsd.first.bmd.de>
 	Andrew A. Chernov <ache@astral.msk.su>
 	Bruce Evans <bde@FreeBSD.org>
 	David Greenman <davidg@Root.COM>
 	Garrett A. Wollman <wollman@freefall.cdrom.com>
 	Gary Palmer <gpalmer@FreeBSD.org>
 	Geoff Rehmet <csgr@cs.ru.ac.za>
 	Jack Vogel <jackv@FreeBSD.org>
 	John Dyson <dyson@implode.rain.com>
 	Jordan K. Hubbard <jkh@FreeBSD.org>
 	Paul Richards <paul@isl.cf.ac.uk>
 	Poul-Henning Kamp <phk@FreeBSD.org>
 	Rich Murphey <rich@lamprey.utmb.edu>
 	Rodney W. Grimes <rgrimes@cdrom.com>
 	Soren Schmidt <sos@FreeBSD.org>
 
 
 Additional FreeBSD Contributors (no particular order):
 
 Adam Glass <glass@postgres.berkeley.edu>
 Andrew Herbert <andrew@werple.apana.org.au>
 Andrew Moore <alm@FreeBSD.org>
 Atsushi Murai <amurai@spec.co.jp>
 Bob Wilcox <bob@obiwan.uucp>
 Bruce Evans <bde@kralizec.zeta.org.au>
 Charles Hannum <mycroft@ai.mit.edu>
 Chris G. Demetriou <cgd@postgres.berkeley.edu>
 Chris Torek <torek@ee.lbl.gov>
 Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
 Curt Mayer <curt@toad.com>
 Dave Burgess <burgess@hrd769.brooks.af.mil>
 Dave Rivers <rivers@ponds.uucp>
 David Dawes <dawes@physics.su.OZ.AU>
 Frank Maclachlan <fpm@crash.cts.com>
 Gary A. Browning <gab10@griffcd.amdahl.com>
 Gary Clark II <gclarkii@radon.gbdata.com>
 Guido van Rooij <guido@gvr.win.tue.nl>
 Havard Eidnes <Havard.Eidnes@runit.sintef.no>
 Holger Veit <Holger.Veit@gmd.de>
 Ishii Masahiro, R. Kym Horsell
 J.T. Conklin <jtc@winsey.com>
 James Clark <jjc@jclark.com>
 James da Silva <jds@cs.umd.edu> et al
 Jim Wilson <wilson@moria.cygnus.com>
 Joerg Wunsch <joerg_wunsch@uriah.sax.de>
 Julian Elischer <julian@dialix.oz.au>
 Julian Stacey <stacey@guug.de> <fallback: <julian@meepmeep.pcs.com>>
 Keith Bostic <bostic@toe.CS.Berkeley.EDU>
 Keith Moore <?>
 Marc Frajola <marc@escargot.rain.com>
 Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
 Martin Birgmeier
 Paul Kranenburg <pk@cs.few.eur.nl>
 Paul Mackerras <paulus@cs.anu.edu.au>
 Poul-Henning Kamp <phk@login.dkuug.dk>
 Rob Shady <rls@id.net>
 Sascha Wildner <swildner@channelz.GUN.de>
 Scott Mace <smace@FreeBSD.org>
 Sean Eric Fagan <sef@kithrup.com>
 Serge V. Vakulenko <vak@zebub.msk.su>
 Steven Wallace <swallace@ece.uci.edu>
 Søren Schmidt <sos@login.dkuug.dk>
 Terry Lee <terry@uivlsi.csl.uiuc.edu>
 Theo Deraadt <deraadt@fsa.ca>
 Ugen J.S.Antsilevich <ugen@NetVision.net.il>
 Yuval Yarom <yval@cs.huji.ac.il>
 
 
 386BSD Patch kit patch contributors (no particular order):
 
 Adam Glass <glass@postgres.berkeley.edu>
 Adrian Hall <adrian@ibmpcug.co.uk>
 Andrew A. Chernov <ache@astral.msk.su>
 Andrew Herbert <andrew@werple.apana.org.au>
 Andrew Moore <alm@netcom.com>
 Andy Valencia <ajv@csd.mot.com> <jtk@netcom.com>
 Arne Henrik Juul <arnej@Lise.Unit.NO>
 Bakul Shah <bvs@bitblocks.com>
 Barry Lustig <barry@ictv.com>
 Bob Wilcox <bob@obiwan.uucp>
 Branko Lankester
 Brett Lymn <blymn@mulga.awadi.com.AU>
 Bruce Evans <bde@kralizec.zeta.org.au>
 Charles Hannum <mycroft@ai.mit.edu>
 Chris G. Demetriou <cgd@postgres.berkeley.edu>
 Chris Torek <torek@ee.lbl.gov>
 Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
 Daniel Poirot <poirot@aio.jsc.nasa.gov>
 Dave Burgess <burgess@hrd769.brooks.af.mil>
 Dave Rivers <rivers@ponds.uucp>
 David Dawes <dawes@physics.su.OZ.AU>
 David Greenman <davidg@Root.COM>
 Eric J. Haug <ejh@slustl.slu.edu>
 Felix Gaehtgens <felix@escape.vsse.in-berlin.de>
 Frank Maclachlan <fpm@crash.cts.com>
 Gary A. Browning <gab10@griffcd.amdahl.com>
 Geoff Rehmet <csgr@alpha.ru.ac.za>
 Goran Hammarback <goran@astro.uu.se>
 Guido van Rooij <guido@gvr.win.tue.nl>
 Guy Harris <guy@auspex.com>
 Havard Eidnes <Havard.Eidnes@runit.sintef.no>
 Herb Peyerl <hpeyerl@novatel.cuc.ab.ca
 Holger Veit <Holger.Veit@gmd.de>
 Ishii Masahiro, R. Kym Horsell
 J.T. Conklin <jtc@winsey.com>
 Jagane D Sundar < jagane@netcom.com >
 James Clark <jjc@jclark.com>
 James Jegers <jimj@miller.cs.uwm.edu>
 James W. Dolter
 James da Silva <jds@cs.umd.edu> et al
 Jay Fenlason <hack@datacube.com>
 Jim Wilson <wilson@moria.cygnus.com>
 Joerg Lohse <lohse@tech7.informatik.uni-hamburg.de>
 Joerg Wunsch <joerg_wunsch@uriah.sax.de>
 John Dyson - <formerly dyson@ref.tfs.com>
 John Woods <jfw@eddie.mit.edu>
 Jordan K. Hubbard <jkh@whisker.hubbard.ie>
 Julian Elischer <julian@dialix.oz.au>
 Julian Stacey <stacey@guug.de> <fallback: <julian@meepmeep.pcs.com>>
 Karl Lehenbauer <karl@NeoSoft.com> <karl@one.neosoft.com>
 Keith Bostic <bostic@toe.CS.Berkeley.EDU>
 Ken Hughes
 Kent Talarico <kent@shipwreck.tsoft.net>
 Kevin Lahey <kml%rokkaku.UUCP@mathcs.emory.edu> <kml@mosquito.cis.ufl.edu>
 Marc Frajola <marc@escargot.rain.com>
 Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
 Martin Renters <martin@innovus.com>
 Michael Galassi <nerd@percival.rain.com>
 Mike Durkin <mdurkin@tsoft.sf-bay.org>
 Nate Williams <nate@bsd.coe.montana.edu>
 Nick Handel <nhandel@NeoSoft.com> <nick@madhouse.neosoft.com>
 Pace Willisson <pace@blitz.com>
 Paul Kranenburg <pk@cs.few.eur.nl>
 Paul Mackerras <paulus@cs.anu.edu.au>
 Paul Popelka <paulp@uts.amdahl.com>
 Peter da Silva <peter@NeoSoft.com>
 Phil Sutherland <philsuth@mycroft.dialix.oz.au>
 Poul-Henning Kamp <phk@login.dkuug.dk>
 Ralf Friedl <friedl@informatik.uni-kl.de>
 Rich Murphey <rich@lamprey.utmb.edu>
 Rick Macklem <root@snowhite.cis.uoguelph.ca>
 Robert D. Thrush <rd@phoenix.aii.com>
 Rodney W. Grimes <rgrimes@cdrom.com>
 Rog Egge <?>
 Sascha Wildner <swildner@channelz.GUN.de>
 Scott Burris <scott@pita.cns.ucla.edu>
 Scott Reynolds <scott@clmqt.marquette.mi.us>
 Sean Eric Fagan <sef@kithrup.com>
 Simon J Gerraty <sjg@melb.bull.oz.au> <sjg@zen.void.oz.au>
 Stephen McKay <robert@psych.psy.uq.oz.au>
 Terry Lambert <terry@icarus.weber.edu>
 Terry Lee <terry@uivlsi.csl.uiuc.edu>
 Warren Toomey <wkt@csadfa.cs.adfa.oz.au>
 Wiljo Heinen <wiljo@freeside.ki.open.de>
 William Jolitz <withheld>
 Wolfgang Solfrank <ws@tools.de>
 Wolfgang Stanglmeier <wolf@dentaro.GUN.de>
 Yuval Yarom <yval@cs.huji.ac.il>
 
 Id: CONTRIB.FreeBSD,v 1.1 1994/11/18 12:03:25 jkh Exp
 

Release Home &footer; diff --git a/en/releases/2.0/install.sgml b/en/releases/2.0/install.sgml index c9cf405aae..dfe3be99b0 100644 --- a/en/releases/2.0/install.sgml +++ b/en/releases/2.0/install.sgml @@ -1,494 +1,494 @@ - - + %includes; ]> &header;
 Welcome to FreeBSD 2.0, the complete 4.4 BSD Lite based OS for Intel (or
 compatible) based PCs.
 
 There are several documents on the floppy and a couple of on-line help
 screens that will greatly assist you in installing your system as you go
 along.  Nonetheless, initial user testing has shown that some of the
 terminology used may be difficult for newcomers to UN*X to understand, so
 we've prepared this step-by-step guide explaining a typical installation.
 You may find it useful to print this out and keep it handy as you go
 through the installation, or at least read through it once carefully so
 that some of the prompts and questions you encounter do not come as
 complete surprises.
 
 Before you do anything, make two 1.44MB floppies from the two image files
 you'll find in the floppies/ directory - boot.flp and cpio.flp.  If you're
 reading this under DOS, you can do it in 1 easy step, or 3 in case this
 doesn't (for some weird reason) work:
 
 1. If you're reading this file after typing "go", simply ESC back out for
    a moment and select the "makeflp" batch file to make the two floppies.
    This will invoke the DOS formatter to format the floppies and then
    attempt to write the two disk images onto them.  If this doesn't work,
    follow steps 2 through 4:
 
 2. Use the DOS format command to format 2 NEW floppies.  A lot of problems
    have been caused by people using old and defective floppies, and much
    grief can often be saved by simply using new, or at least trusted,
    media.
 
 3. Insert the first floppy and type:
 
 		tools\dos-tool\rawrite floppies\boot.flp a:
 
 4. Insert the second floppy and type
 
 		tools\dos-tool\rawrite floppies\cpio.flp a:
 
 You're now prepared to boot from the boot floppy and begin the installation.
 
 
 The installation starts with the following screen:
 
   +-------------------------- Welcome to FreeBSD! ---------------------------+
   | Use ALT-F2 and ALT-F1 to toggle between debugging                        |
   | information screen (ALT-F2) or this dialog screen (ALT-F1)               |
   |                                                                          |
   | Please select one of the following options:                              |
   | +----------------------------------------------------------------------+ |
   | | 1. README               READ THIS FIRST.                             | |
   | | 2. Release Notes        Read the 2.0 Release Notes (recommended).    | |
   | | 3. Troubleshooting      Read this in case of trouble.                | |
   | | 4. Partitions and MBRs  Verbose description of how these work.       | |
   | | 5. COPYRIGHT            Read FreeBSD Copyright Information.          | |
   | | 6. Install              Proceed with full installation.              | |
   | | 7. Fixit                Repair existing installation (`fixit' mode). | |
   | | 8. Quit                 Don't do anything, just reboot.              | |
   | +----------------------------------------------------------------------+ |
   +--------------------------------------------------------------------------+
   |                          <  OK  >      <Cancel>                          |
   +--------------------------------------------------------------------------+
 
 
 You can move the arrow keys up and down to highlight the various options,
 selecting an option by hitting return when its line is highlighted.  You
 can also type the number of the option you want (1 - 7) and hit return.
 It's recommended that you read the README at a minimum, though the Release
 Notes are also helpful.  This may seem a like a lot to read, but if you are
 new to FreeBSD then these notes are invaluable for explaining the system
 and are highly recommended.
 
 When you're done reading docs, select Install (5) to proceed to the next
 screen.
 
 This next screen is the disk editor screen, which looks like this:
 
 ------------------------------------------------------------------------------
 FreeBSD 2.0-RELEASE Installation -- Diskspace editor
 
 Disks         Total   FreeBSD                    |You should now assign some
                                                  |space to root, swap, and
  0: sd0     2006 MB      0 MB                    |(optionally) /usr partitions
  1: sd1      496 MB      0 MB                    |Root (/) should be a minimum
                                                  |of 18MB with a 30MB /usr
 Filesystems  Type        Size  Action Mountpoint |or 50MB without a /usr.
                                                  |Swap space should be a
                                                  |minimum of 12MB or RAM * 2
                                                  |Be sure to also (A)ssign a
                                                  |mount point to each one or
                                                  |it will NOT be enabled.
                                                  |
                                                  |We suggest that you invoke
                                                  |(F)disk, (W)rite the bootcode
                                                  |then (D)isklabel your disk.
                                                  |If installing on a drive
                                                  |other than 0, also read the
                                                  |TROUBLESHOOTING doc first
 Commands available:
 (H)elp  (T)utorial  (F)disk  (D)isklabel  (P)roceed  (Q)uit
 
 Enter Command>
 
 ------------------------------------------------------------------------------
 
 As we can see, this system has two drives, sd0 and sd1.  On an IDE system,
 these would show up as "wd0" and "wd1" (or, on a single drive system, just
 sd0 or wd0).  We can see that neither of them has any space assigned to
 FreeBSD (they each show 0MB under the FreeBSD column), so we follow the
 instructions on the right hand side of the screen and invoke the (F)disk
 editor by typing `f':
 
 Enter Command> F
 
 We're now prompted with the drive number to (F)disk, so we enter 0 for
 the first drive:
 
 Enter number of disk to Fdisk> 0
 
 This now brings us to the FDISK editor screen, which looks like this:
 
 ------------------------------------------------------------------------------
 FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- FDISK
 
 Disk: sd0   Geometry:  2006 Cyl * 32 Hd * 64 Sect = 2006Mb = 4108600 Sect
 
 1 Boot?=No    Type=Primary 'big' DOS (> 32MB)
   Phys=(c0/h1/s1..c299/h63/s32)   Sector=(32..614399)
   Size=300 MB, 299 Cylinders + 31 Tracks + 32 Sectors
 
 2 Unused
 
 
 3 Unused
 
 
 4 Unused
 
 
 Commands available:
 (H)elp   (T)utorial   (D)elete   (E)dit   (R)eread   (W)rite MBR   (Q)uit
 (U)se entire disk for FreeBSD   (G)eometry   Write MBR (B)ootcode
 Enter Command>
 
 ------------------------------------------------------------------------------
 
 We see that drive 0 has a DOS partition (also called a "slice" in FreeBSD
 parlance, to distinguish it from a FreeBSD partition) on it which is 300MB
 in size (don't worry if the numbers you see are much smaller than these - I
 have a pretty large 2.1GB disk! :-).  Let's also say we want to allocate
 the rest to FreeBSD, so to do this we want to (E)dit one of the existing
 slices.  We can see that 2, 3, and 4 are unused so let's pick the first
 unused one, which is 2 (if we wanted to replace an existing operating
 system slice with FreeBSD, we'd pick its number instead).  We first type
 `E' to edit a slice entry:
 
 Enter Command> E
 
 And we're prompted for a slice to edit.  We type 2:
 
 Edit which Slice> 2
 
 Now we're prompted for the size of the new slice, the default for which is
 all remaining space on the disk.  Let's say that we don't want to allocate
 ALL the space on the disk, but want to reserve 400MB for some other future
 OS.  The total amount of free space left is 1706MB, which is the default
 value selected for us, so we backspace over it and enter 1306:
 
 Size of slice in MB> 1306
 
 Now we're asked for the type of the slice.  The type is what tells the PC
 what sort of slice this is.  DOS primary slices are, for example, type 6.
 FreeBSD slices are type 0xa5 (hexadecimal).  If we wanted to reserve space
 at this time for some other type of OS like Linux or OS/2, and we knew
 their slice type (0x82 for Linux and 0x0A for OS/2, just in case you're
 interested), we could also do that from this editor, but we're only
 interested in FreeBSD for now so we accept the default.
 
 Type of slice (0xa5=FreeBSD)> 0xa5
 
 The next prompt asks if we want to make this slice bootable by
 default, which we do so we accept the default:
 
 Bootflag (0x80 for YES)> 0x80
 
 At this point we come back to the main screen, which now shows a new entry
 for slice 2:
 
 ------------------------------------------------------------------------------
 FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- FDISK
 
 Disk: sd0   Geometry:  2006 Cyl * 32 Hd * 64 Sect = 2006Mb = 4108600 Sect
 
 1 Boot?=No    Type=Primary 'big' DOS (> 32MB)
   Phys=(c0/h1/s1..c299/h63/s32)   Sector=(32..614399)
   Size=300 MB, 299 Cylinders + 31 Tracks + 32 Sectors
 
 2 Boot?=Yes   Type=FreeBSD/NetBSD/386BSD
   Phys=(c300/h0/s1..c1023/h31/s0)   Sector=(614400..3289087)
   Size=1306 MB, 1306 Cylinders
 
 3 Unused
 
 
 
 4 Unused
 
 
 
 Commands available:
 (H)elp   (T)utorial   (D)elete   (E)dit   (R)eread   (W)rite MBR   (Q)uit
 (U)se entire disk for FreeBSD   (G)eometry   Write MBR (B)ootcode
 Enter Command>
 
 ------------------------------------------------------------------------------
 
 At this point we're happy with the slices on the first drive, so we type
 `w' to write the new information out.  It also prompts to make *sure* we
 really want to do this, so we backspace over the default of `N' and type
 `y'<return>.  And this point, we also can decide whether or not we want a
 "boot manager" installed.  A boot manager is a little utility that prompts
 you for the operating system you want to boot every time you reset or power
 on your PC, and can be a very handy way of sharing your computer between
 FreeBSD and some other OS, like Linux or DOS.  We decide that we want to
 have this feature, so we `b' to write the special MBR (B)ootcode out to the
 disk.  This does not harm any of the other operating systems on the disk,
 as it's written to a special area.  Now we exit this screen by typing `q',
 for (Q)uit.
 
 This brings us back to the main prompt.  If we wanted to allocate any
 additional slices on other drives, we also could re-invoke the (F)disk
 editor by typing `f' again and giving a different drive number at the
 prompt, but we'll assume for now that we've only got one disk and want to
 go on.  Typing `d' now enters the (D)isklabel screen, which prompts us for
 the drive to write a disklabel onto, like the FDISK editor.  We type `0'
 for the first drive and hit return.  This brings us to the DISKLABEL editor
 screen, which looks like this:
 
 ------------------------------------------------------------------------------
 FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- DISKLABEL
 
 Part  Start       End    Blocks     MB  Type    Action  Mountpoint
 a         0         0         0      0  unused
 b         0         0         0      0  unused
 c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
 d         0   4108599   4108600   2006  unused          <Entire Disk>
 e         0         0         0      0  unused
 f         0         0         0      0  unused
 g         0         0         0      0  unused
 h        32    614399    614368    300  MSDOS
 
 
 
 
 
 
 Total size:       2674688 blocks   1306Mb
 Space allocated:        0 blocks      0Mb
 
 Commands available:
 (H)elp  (T)utorial  (E)dit  (A)ssign  (D)elete  (R)eread  (W)rite  (Q)uit
 (P)reserve  (S)lice
 Enter Command>
 
 ------------------------------------------------------------------------------
 
 The BSD partitions, a - h, are FreeBSD's way of dividing up a physical
 slice into multiple file systems.  Every FreeBSD system should have, at
 minimum, a root file system and a swap partition allocated.  The root
 file system is called "/", and is generally put on partition `a' by
 convention.  Swap partitions always go on `b', and the `c' and `d'
 partitions are special and point to the entire FreeBSD slice and the entire
 disk, respectively.  `c' and `d' cannot and should not be allocated to
 actual file systems.
 
 We also see that partition h points conveniently to the DOS slice,
 which we can also assign to a location in our file system hierarchy
 to conveniently share files between FreeBSD and DOS.  More on this in 
 a moment.
 
 A typical file system layout might look like this:
 
 /	20MB
 swap	32MB
 /usr	120MB
 
 /, or the root file system, contains system files and some temporary space.
 It should be at least 18MB in size, though a little extra doesn't hurt.
 Swap space is one of those "it never hurts to have too much" sorts of
 items, though if your system isn't too heavily used then it's probably not
 that important to have lots and lots of it.  A good rule of thumb for swap
 is that you want a minimum of 12MB of it, and the overall calculation
 should be the amount of memory you have multiplied by two.  That is to
 say that if you have 16MB of memory, then 32MB of swap is good.
 
 If you've got several drives, you can also allocate some swap on each one
 and spread the load out a little.  On my personal system, I've got 32MB of
 main memory and 64MB of swap on both drives for a total of 128MB of swap.
 This gives me 4X memory for total program swapping, which gives me the
 ability to run some pretty big programs!  Emacs and the X Window System, in
 particular, can be real swap hogs.
 
 In any case, we'll assume for the moment that we're still configuring the
 ideal system and we'll allocate 64MB of swap space, using the MEM * 2
 equation.  If you only had 8MB of memory, you'd allocate 16MB of swap
 instead.
 
 The second file system of importance is /usr, which contains further system
 binaries and all of the bundled user binaries.  /usr should be at least
 80MB in size to hold all of the important binaries, though if you plan on
 having a big /usr/local or on loading the X Window System (also known as
 XFree86 3.1) distribution then you should either create separate
 file systems for them, or you should make /usr a lot bigger.
 
 It's also possible to skip making /usr altogether and simply make a large
 root (/) file system.  Since /usr fits "underneath" /, a missing /usr won't
 cause any problems if / is large enough to hold the contents for both.  In
 any case, it's a user decision and tends to be driven by convention more
 than anything else.  For the purposes of this installation guide, we'll
 assume a 200MB /usr, 100MB of space allocated for local binaries, which
 we'll mount on /usr/local, and the rest for user home directories, which
 we'll mount on /usr/users.  Don't be put off by the size of these numbers!
 You can make a system fit into less space, but since we're dividing up the
 ideal 2GB dream disk, we might as well do it right! ;-)
 
 Getting back to the relevant part of the DISKLABEL screen again, we remember
 that it looked like this:
 
 Part  Start       End    Blocks     MB  Type    Action  Mountpoint
 a         0         0         0      0  unused
 b         0         0         0      0  unused
 c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
 d         0   4108599   4108600   2006  unused          <Entire Disk>
 e         0         0         0      0  unused
 f         0         0         0      0  unused
 g         0         0         0      0  unused
 h        32    614399    614368    300  MSDOS
 
 So we'll first allocate some space on partition `a' for that root partition
 by typing `e', for (E)dit partition.  This asks us which partition we want
 to change the size of, so we type `a':
 
 Change size of which partition> a
 
 And it prompts us for the amount of space, so we'll pick 20MB for a nice
 comfortable root file system:
 
 Size of partition in MB> 20
 
 Now we see the display change to:
 
 Part  Start       End    Blocks     MB  Type    Action  Mountpoint
 a   1433600   1474559     40960     20  4.2BSD
 ...
 
 The system shows us where the partition starts and stops and indicates that
 it's a 4.2BSD file system, which is correct (it's really a 4.4 BSD file
 system, in actuality, but the two are similar enough to share the same
 label).
 
 We do the same for swap by typing `e' again and modify the `b' partition
 by filling in 64 for the size, to allocate 64MB of swap.
 
 Finally, remembering that `c' and `d' are special, and not for our use, we
 change the size of `e' to 200 for our future /usr, `f' to 100 for our
 /usr/local, and `g' to the rest of the disk for /usr/users.  When we're
 done, the top of the disklabel screen should look like this:
 
 Part  Start       End    Blocks     MB  Type    Action  Mountpoint
 a   1433600   1474559     40960     20  4.2BSD
 b   1474560   1605631    131072     64  swap
 c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
 d         0   4108599   4108600   2006  unused          <Entire Disk>
 e   1605632   2015231    409600    200  4.2BSD
 f   2015232   2220031    204800    100  4.2BSD
 g   2220032   4108287   1888256    922  4.2BSD
 h        32    614399    614368    300  MSDOS
 
 We left `h' alone, since we actually want to be able to share files with
 our DOS partition.  At this point, we want to type `w' for (W)rite to write
 out the new size information to disk.
 
 You probably also noticed by now that "/", "/usr" and the other file system
 names we've been talking about don't appear anywhere in the above list.
 Where are they?  This brings us to the next stage, which is to (A)ssign the
 new partitions to actual file system mount points.  A file system in
 FreeBSD doesn't actually appear anywhere until we "mount" it someplace, a
 convention from the old days when disks were actually large removable packs
 that a system operator physically mounted on a large washing-machine sized
 disk drive spindle!  As you can see, not much has changed today! :-)
 
 We'll proceed then by starting at the top with the first partition and
 assigning it to the root file system (/) by typing `a', for (A)ssign, and
 then typing `a' again, for partition a:
 
 Assign which partition> a
 
 When it asks us for the name of the mount point, we type /:
 
 Directory mountpoint> /
 
 And the display adjusts accordingly to show us the new state of affairs:
 
 Part  Start       End    Blocks     MB  Type    Action  Mountpoint
 a   1433600   1474559     40960     20  4.2BSD  newfs   /
 ..
 
 The Action field also now shows "newfs", which means that the partition
 will be created anew.  For root file systems, this is the default and cannot
 be changed, but other partitions can be optionally "Preserved" by typing
 `p' for (P)reserve.  There are very few situations in which we'd want to do
 this, but if, say, we were actually installing a disk from an older FreeBSD
 machine which we wanted to mount into our new system but NOT erase, we
 could do it this way.  For now, let's assume that this is a new
 installation and we want all the file systems to be created from scratch.
 We thus go through and assign the rest of the file systems to their
 respective /usr, /usr/local and /usr/users mountpoints.  We also assign the
 `b' partition, which doesn't take a mountpoint (and won't prompt for one
 when we (A)ssign it), but needs us to tell it that we're ready to use it
 for swap.
 
 When we're done, the top of the screen should look something like this:
 
 Part  Start       End    Blocks     MB  Type    Action  Mountpoint
 a   1433600   1474559     40960     20  4.2BSD  newfs   /
 b   1474560   1605631    131072     64  swap    swap    swap
 c   1433600   4108287   2674688   1306  unused          <Entire FreeBSD slice>
 d         0   4108599   4108600   2006  unused          <Entire Disk>
 e   1605632   2015231    409600    200  4.2BSD  newfs   /usr
 f   2015232   2220031    204800    100  4.2BSD  newfs	/usr/local
 g   2220032   4108287   1888256    922  4.2BSD  newfs	/usr/users
 h        32    614399    614368    300  MSDOS
 
 As a final bonus, we'll assign the DOS partition to be mounted on /dos.  We
 do this with (A)ssign as we did the others, and we also notice that the
 system is smart enough to see that it's not a FreeBSD partition and we
 DON'T want to newfs it, we want to simply mount it:
 
 h        32    614399    614368    300  MSDOS   mount   /dos
 
 At this point, our system is all set up and ready to go!
 
 We type `q' to go back to the main menu and then type `p' to (P)roceed to
 the next phase of installation.
 
 We're now given one last chance to back out of the install, and we hit
 return if we're sure, otherwise we type <Tab> to select "No" and hit return
 to consider our settings again before going on.
 
 The rest of the installation is pretty much self-explanatory.  After the
 file systems are initially created and populated, you'll be prompted to
 reboot from the hard disk.  Do so and provide the cpio floppy when asked.
 
 When the initial flurry of welcome and informational prompts has died down,
 you'll come to a screen asking you to load one or more distributions.  At
 the minimum, select "bindist" to load the basic system.  If you're loading
 from other than CDROM media, follow the appropriate paths through the
 installation process.
 
 If you're loading from CDROM, select CDROM as the media type and select the
 type of CDROM you've got (SCSI or Mitsumi).  When it asks you for an
 installation subdirectory, simply hit return if you've got the 2.0 CD from
 Walnut Creek CDROM.  You may select additional optional packages to load
 after the bindist extracts, provided that you've got the space for it.  Use
 the "?diskfree" menu option from time to time to keep an eye on your free
 space.  When you're done, you'll be asked a few more basic questions and
 then that's it!  You've got FreeBSD on your hard disk.
 
 If you should need to partition another drive or install other packages
 later, you may re-invoke the sysinstall program by typing /sbin/sysinstall.
 The same familiar prompts will then come up.
 
 Good luck!
 
 					Jordan Hubbard
 					for Walnut Creek CDROM
 					and the FreeBSD Project.
 
 
 
 

Release Home &footer; diff --git a/en/releases/2.0/notes.sgml b/en/releases/2.0/notes.sgml index db7536ca04..993ea9777b 100644 --- a/en/releases/2.0/notes.sgml +++ b/en/releases/2.0/notes.sgml @@ -1,657 +1,657 @@ - - + %includes; ]> - + &header;
 
                                  RELEASE NOTES
                                     FreeBSD
                                   Release 2.0
 
 1. Technical overview
 ---------------------
 
 FreeBSD is a freely available, full source 4.4 BSD Lite based release
 for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
 primarily on software from U.C. Berkeley's CSRG group, with some
 enhancements from NetBSD, 386BSD, and the Free Software Foundation.
 
 Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD
 has changed almost entirely.  A new port from the Berkeley 4.4 code
 base was done, which brought the legal status of the system out of the
 shadows with the blessing of Novell (new owners of USL and UNIX).  The
 port to 4.4 has also brought in a host of new features, filesystems
 and enhanced driver support.  With our new unencumbered code base, we
 have every reason to hope that we'll be able to release quality
 operating systems without further legal encumbrance for some time to
 come!
 
 FreeBSD 2.0 represents the culmination of almost 2 years of work and
 many thousands of man hours put in by an international development team.
 We hope you enjoy it!
 
 Many packages have also been upgraded or added, such as XFree86 3.1,
 xview 3.2, elm, nntp, mh, InterViews and dozens of other miscellaneous
 utilities have been ported and are now available as add-ons.  See the
 ports collection (or the package collection) for a complete summary.
 
 For a list of contributors, please see the file "CONTRIB.FreeBSD",
 which should be bundled with your bindist distribution.
 
 Also see the new "REGISTER.FreeBSD" file for information on registering
 with the "Free BSD user counter".  We've also provided a list of who's
 responsible for what (so that you may query them directly) in the
 "ROSTER.FreeBSD" file; use of this file is encouraged to ensure faster
 resolution of any problems you may have!
 
 The core of FreeBSD does not contain DES code which would inhibit its
 being exported outside the United States.  There is an add-on package
 to the core distribution, for use only in the United States, that
 contains the programs that normally use DES.  The 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
 file systems, and Søren Schmidt did the same for loadable execution
 classes.
 
 Owner:                  core
 Sources involved:       sys/kern, sbin/modload, sbin/modunload,
                         usr.bin/modstat
 
 
 Loadable filesystems
 --------------------
 Most filesystems are now dynamically loadable on demand, with the
 exception of the UFS family (FFS, LFS, and MFS).  With the exception
 of NFS, all such filesystems can be unloaded when all references are
 unmounted.  To support this functionality, the 
 
 getvfsbyname(3)
 
 family of functions has been added to the C library and the 
 lsvfs(1)
 
 command provides the same information at the shell level.  Be aware of
 the following current restrictions:
 
         - /usr/bin may not reside on a dynamically loaded filesystem.
         - There must be a writable /tmp directory available
           before filesystems are loaded (moving / to the top of your
           /etc/fstab file will accomplish this).
         - Some of the more esoteric filesystems simply don't work when loaded
           dynamically (though they often don't work "static", either.)
 
 Owner:                  wollman
 Sources involved:       sys/*fs, lkm/*fs, usr.bin/lsvfs, lib/libc/gen
 
 
 S/Key
 -----
 Since version 1.1.5, FreeBSD has supported the S/Key one time password
 scheme.  The version used is derived from the logdaemon package of Wietse
 Venema.
 Some of the features new in 2.0 are:
         - New access control table format to impose the use of S/Keys
           based on: hostname, ip address, port, username, group id.
         - S/Key support can be disabled by not having the access control
           table.
 The second item explains the absence of skey.access in the installed /etc.
 To enable S/Key support, create a file skey.access in /etc and fill it
 according to your needs. See also skey.
 access(5)
 and the example in
 /usr/share/examples/etc/skey.access.
 
 Owner:                  pst, guido
 Sources involved:       lib/libskey, usr.bin/key* (plus patches to others)
 
 
 TCP/IP over parallel (printer) port
 -----------------------------------
 You can now run TCP/IP over a standard LapLink(tm) cable, if both ends
 have an interrupt-driven printerport.  The interface is named "lp0"
 where '0' is the same as the lpt# unit number.  This is not compatible
 with PLIP.  If you run NFS, try setting MTU to 9180, otherwise leave
 it at 1500 unless you have a good reason to change it.  Speed varies
 with the CPU-type, with up to 70 kbyte/sec having been seen and 50
 kbyte/sec being the norm.
 
 Owner:                  phk
 Sources involved:       isa/lpt.c
 
 
 ProAudioSpectrum SCSI driver
 ----------------------------
 If you have a PAS board with a CD-ROM, and the MS-DOS driver is called
 TSLCDR.SYS, then the "pas" driver should work on your card.  You can
 attach disks, CDROMs and tapes, but due to the nature of the hardware
 involved, the transfer rate is limited to < 690 kbyte/sec.  For CD-ROM
 use, this is generally more than enough.
 
 Owner:                  phk
 Sources involved:       isa/pas.c
 
 
 Adaptec 2742/2842 SCSI driver
 -----------------------------
 Despite the non-cooperation of Adaptec in providing technical
 information, we now have a driver for the AHA-274x and AHA-284x
 series SCSI controller family.  This driver uses the GPL'd
 Linux sequencer code, so until we find an alternative, this
 will be part of the kernel that requires source code to be
 distributed with it at all times.  This shouldn't be a problem
 for any of FreeBSD's current users.
 
 Owner:                  gibbs
 Sources involved:       isa/aic7770.c sys/gnu/misc/*
 
 
 Gzip'd binaries
 ----------------
 We have an experimental implementation for direct execution of gzip'ed
 binaries in this release.  When enabled, it allows you to simply gzip
 your binaries, remove the '.gz' extension and make the file
 executable.  There is a big speed and memory consumption penalty for
 doing this, but for laptop users it may be worthwhile.  The maximum
 savings are generally around 10 Mb of disk space.
 
 Owner:                  phk
 Sources involved:       kern/imgact_gzip.c kern/inflate.c
 
 
 Diskless booting
 ----------------
 
 Diskless booting in 2.0 is much improved since 1.1.5.  The
 boot-program is in src/sys/i386/boot/netboot, and can be run from an
 MSDOS system or burned into an EPROM.  Local swapping is also
 possible.  WD, SMC, 3COM and Novell ethernet cards are currently
 supported.
 
 Owner:                  Martin Renters & phk
 Sources involved:       i386/boot/netboot, sys/nfs/nfs_vfsops.h
 
 
 Device configuration database
 -----------------------------
 The kernel now keeps better track of which device drivers are active and
 where the devices are attached; this information is made available to
 user programs via the new 
 sysctl(3)
 management interface.  Current
 applications include 
 lsdev(8),
 which lists the currently configured
 devices.  In the future, we expect to use this code to automatically
 generate a configuration file for you at installation time.
 
 Owner:                  wollman
 Sources involved:       sys/i386, sys/scsi, sys/kern/kern_devconf.c,
                         sys/sys/devconf.h, usr.sbin/lsdev
 
 
 Kernel management interface
 ---------------------------
 With 4.4-Lite, we now have a better management interface for the endless
 series of kernel variables and parameters which were previously manipulated
 by reading and writing /dev/kmem.  Many programs have been rewritten to
 use this interface, although many old-style programs still remain.  Some
 variables which were never accessible before are now available through
 the 
 sysctl(1)
 program.  In addition to the standard 4.4BSD MIB variables,
 we have added support for YP/NIS domains (kern.domainname), controlling
 the update daemon (kern.update), retrieving the OS release date
 (kern.osreldate), determining the name of the booted kernel (kern.bootfile),
 and checking for hardware floating-point support (hw.floatingpoint).
 We have also added support to make management queries of devices and
 filesystems.
 
 Owner:                  core
 Sources involved:       sys, usr.bin/sysctl
 
 
 iBCS2 support
 -------------
 FreeBSD now supports running iBCS2 compatible binaries (currently
 SCO UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).
 The iBCS2 emulator is in its early stages, but it is functional, we
 haven't been able to do exhaustive testing (lack of commercial apps),
 but almost all of SCO's 3.2.2 binaries are working, so is an old
 INFORMIX-2.10 for SCO. Further testing is 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 <where the *.?? files are>
         tar cvf /dev/rwt0 (or /dev/rst0) .
 
 from a directory with just the distribution files in it.  Make sure
 that you remember to put CKSUMS, do_cksum.sh, and extract.sh files
 in this directory as well!
 
 If you wish to install multiple *dist releases from one tape, do the
 following:
 
 1. cd to the parent directory of the distributions and put them on tape
    like so:
                 tar cvf /dev/rwt0 (or /dev/rst0) bindist srcdist ...
 
 2. Install the first distribution on the tape using the tape installation
    method as normal.  Afterwards, *do not* erase the contents of the temporary
    directory.  Get a shell with ESC-ESC and cd to the temporary directory
    yourself.  For each additional *dist you want to load, cd to its
    subdirectory and type `sh ./extract.sh'.
 
 
 5. Reporting problems, making suggestions, submitting code.
 -----------------------------------------------------------
 
 Your suggestions, bug reports and contributions of code are always
 valued - please do not hesitate to report any problems you may find
 (preferably with a fix attached if you can!).
 
 The preferred method to submit bug reports from a machine with internet
 mail connectivity is to use the send-pr command.  Bug reports will be
 dutifully filed by our faithful bugfiler program and you can be sure
 that we'll do our best to respond to all reported bugs as soon as
 possible.
 
 If, for some reason, you are unable to use the send-pr command to
 submit a bug report, you can try to send it to:
 
                 bugs@FreeBSD.org
 
 
 Otherwise, for any questions or suggestions, please send mail to:
 
                 questions@FreeBSD.org
 
 Additionally, being a volunteer effort, we are always happy to have
 extra hands willing to help - there are already far more enhancements
 to be done than we can ever manage to do by ourselves!  To contact us
 on technical matters, or with offers of help, you may send mail to:
 
                 hackers@FreeBSD.org
 
 Since these mailing lists can experience significant amounts of
 traffic, if you've got slow or expensive mail access and you're
 only interested in keeping up with significant FreeBSD events, you may
 find it preferable to subscribe to:
 
                 announce@FreeBSD.org
 
 
 All but the FreeBSD-bugs groups can be freely joined by anyone wishing
 to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
 `help' on a line by itself somewhere in the body of the message.  This
 will give you more information on joining the various lists, accessing
 archives, etc.  There are a number of mailing lists targeted at
 special interest groups not mentioned here, so send mail to majordomo
 and ask about them!
 
 
 6. Acknowledgements
 -------------------
 
 FreeBSD represents the cumulative work of many dozens, if not
 hundreds, of individuals from around the world who have worked very
 hard to bring you this release.  It would be very difficult, if not
 impossible, to enumerate everyone who's contributed to FreeBSD, but
 nonetheless we shall try (in alphabetical order, of course). If your
 name is not mentioned, please be assured that its omission is entirely
 accidental.
 
 
 The Computer Systems Research Group (CSRG), U.C. Berkeley.
 
 Bill Jolitz, for his extensive work with 386BSD.
 
 The FreeBSD "core" team:
 
         Andrew A. Chernov
         John Dyson
         Bruce Evans
         David Greenman
         Rodney W. Grimes
         Jordan K. Hubbard
         Poul-Henning Kamp
         Rich Murphey
         Gary Palmer
         Geoff Rehmet
         Paul Richards
         Soren Schmidt
         Andreas Schulz
         Jack Vogel
         Garrett A. Wollman
 
 
 Special mention to:
 
         Robert Bruce and Jack Velte of Walnut Creek CDROM, without
         whose help (and continuing support) this release would never
         have been possible.
 
         Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
         drive.
 
         The NetBSD group for their frequent assistance and commentary.
 
         Additional FreeBSD helpers and beta testers:
 
         J.T. Conklin                            Julian Elischer
         Sean Eric Fagan                         Jeffrey Hsu
         Terry Lambert                           L Jonas Olsson
         Chris Provenzano                        Dave Rivers
         Guido van Rooij                         Steven Wallace
         Atsushi Murai                           Scott Mace
         Andrew Moore                            Nate Williams
 
         And everyone at Montana State University for their initial support.
 
 
 Thanks to everyone, especially those not mentioned, and we sincerely
 hope you enjoy this release of FreeBSD!
 
 
                         The FreeBSD Core Team
 
 Id: RELNOTES.FreeBSD,v 1.21 1994/12/02 20:27:11 jkh Exp 
 
 

Release Home &footer; diff --git a/en/releases/2.1.5R/announce.sgml b/en/releases/2.1.5R/announce.sgml index aa6b921529..4e95edfc7c 100644 --- a/en/releases/2.1.5R/announce.sgml +++ b/en/releases/2.1.5R/announce.sgml @@ -1,270 +1,270 @@ - - + %includes; ]> &header;

FreeBSD 2.1.5-RELEASE is now available on ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from 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 Release Notes.

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

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

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

Australia

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

Brazil

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

Canada

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

Czech Republic

Estonia

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

Finland

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

France

Germany

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

Hong Kong

Ireland

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

Israel

Japan

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

Korea

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

Netherlands

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

Poland

Portugal

Russia

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

South Africa

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

Sweden

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

Taiwan

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

Thailand

USA

In case of problems, please contact hostmaster@FreeBSD.org.

UK

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

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

South Africa

Brazil

Finland

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

Release Home &footer; diff --git a/en/releases/2.1.6R/announce.sgml b/en/releases/2.1.6R/announce.sgml index 07cd6b6dce..5d099f335c 100644 --- a/en/releases/2.1.6R/announce.sgml +++ b/en/releases/2.1.6R/announce.sgml @@ -1,47 +1,47 @@ - - + %includes; ]> &header;

Please read an important security announcement regarding FreeBSD 2.1.6

FreeBSD 2.1.6 is now available in:

ftp://ftp.FreeBSD.org/pub/FreeBSD/2.1.6-RELEASE ]]> 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 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.

Release Home &footer; diff --git a/en/releases/2.1.6R/notes.sgml b/en/releases/2.1.6R/notes.sgml index 074425b197..2f781d69a8 100644 --- a/en/releases/2.1.6R/notes.sgml +++ b/en/releases/2.1.6R/notes.sgml @@ -1,551 +1,551 @@ - - + %includes; ]> - + &header;
                                  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:
       <browser> file:/usr/share/doc/handbook/handbook.html
 
   To read the FAQ:
       <browser> file:/usr/share/doc/FAQ/freebsd-faq.html
 
 You can also visit the master (and most frequently updated) copies at
 http://www.FreeBSD.org.
 
 The core of FreeBSD does not contain DES code which would inhibit its
 being exported outside the United States.  There is an add-on package
 to the core distribution, for use only in the United States, that
 contains the programs that normally use DES.  The auxiliary packages
 provided separately can be used by anyone.  A freely (from outside the
 U.S.) exportable distribution of DES for our non-U.S. users also
 exists at ftp://ftp.internat.FreeBSD.org/pub/FreeBSD.
 
 If password security for FreeBSD is all you need and you have no
 requirement for copying encrypted passwords from different hosts
 (Suns, DEC machines, etc) into FreeBSD password entries, then
 FreeBSD's MD5 based security may be all you require!  We feel that our
 default security model is more than a match for DES, and without any
 messy export issues to deal with.  If you're outside (or even inside)
 the U.S., give it a try!  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 <asami@FreeBSD.org>
         Andrey A. Chernov <ache@FreeBSD.org>
         John Dyson <dyson@FreeBSD.org>
         Bruce Evans <bde@FreeBSD.org>
         Justin Gibbs <gibbs@FreeBSD.org>
         David Greenman <davidg@FreeBSD.org>
         Jordan K. Hubbard <jkh@FreeBSD.org>
         Poul-Henning Kamp <phk@FreeBSD.org>
         Rich Murphey <rich@FreeBSD.org>
         Gary Palmer <gpalmer@FreeBSD.org>
         Søren Schmidt <sos@FreeBSD.org>
         Peter Wemm <peter@FreeBSD.org>
         Garrett A. Wollman <wollman@FreeBSD.org>
         Jörg Wunsch <joerg@FreeBSD.org>
 
 
 The FreeBSD Development Team, excluding core team members
 (in alphabetical order by last name):
 
         Torsten Blum <torstenb@FreeBSD.org>
         Gary Clark II <gclarkii@FreeBSD.org>
         Adam David <adam@FreeBSD.org>
         Peter Dufault <dufault@FreeBSD.org>
         Frank Durda IV <uhclem@FreeBSD.org>
         Julian Elischer <julian@FreeBSD.org>
         Sean Eric Fagan <sef@FreeBSD.org>
         Stefan Esser <se@FreeBSD.org>
         Bill Fenner <fenner@FreeBSD.org>
         John Fieber <jfieber@FreeBSD.org>
         Lars Fredriksen <lars@freeBSD.org>
         Thomas Gellekum <tg@FreeBSD.org>
         Thomas Graichen <graichen@FreeBSD.org>
         Rod Grimes <rgrimes@FreeBSD.org>
         James FitzGibbon <jfitz@FreeBSD.org>
         John Hay <jhay@FreeBSD.org>
         Jeffrey Hsu <hsu@FreeBSD.org>
         Ugen J.S. Antsilevich <ugen@FreeBSD.org>
         Gary Jennejohn <gj@FreeBSD.org>
         Andreas Klemm <andreas@FreeBSD.org>
         Warner Losh <imp@FreeBSD.org>
         L Jonas Olsson <ljo@FreeBSD.org>
         Eric L. Hernes <erich@FreeBSD.org>
         Scott Mace <smace@FreeBSD.org>
         Atsushi Murai <amurai@FreeBSD.org>
         Mark Murray <markm@FreeBSD.org>
         Alex Nash <alex@FreeBSD.org>
         Masafumi NAKANE <max@FreeBSD.org>
         David E. O'Brien <obrien@FreeBSD.org>
         Andras Olah <olah@FreeBSD.org>
         Steve Passe <smp@FreeBSD.org>
         Sujal Patel <smpatel@FreeBSD.org>
         Bill Paul <wpaul@FreeBSD.org>
         Joshua Peck Macdonald <jmacd@FreeBSD.org>
         John Polstra <jdp@FreeBSD.org>
         Steve Price <steve@FreeBSD.org>
         Mike Pritchard <mpp@FreeBSD.org>
         Doug Rabson <dfr@FreeBSD.org>
         James Raynard <jraynard@FreeBSD.org>
         Geoff Rehmet <csgr@FreeBSD.org>
         Martin Renters <martin@FreeBSD.org>
         Paul Richards <paul@FreeBSD.org>
         Ollivier Robert <roberto@FreeBSD.org>
         Chuck Robey <chuckr@FreeBSD.org>
         Dima Ruban <dima@FreeBSD.org>
         Wolfram Schneider <wosch@FreeBSD.org>
         Andreas Schulz <ats@FreeBSD.org>
         Karl Strickland <karl@FreeBSD.org>
         Michael Smith <msmith@FreeBSD.org>
         Paul Traina <pst@FreeBSD.org>
         Guido van Rooij <guido@FreeBSD.org>
         Steven Wallace <swallace@FreeBSD.org>
         Nate Williams <nate@FreeBSD.org>
         Jean-Marc Zucconi <jmz@FreeBSD.org>
 
 Additional FreeBSD helpers and beta testers:
 
         Coranth Gryphon            Dave Rivers 
         Kaleb S. Keithley          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
 

Release Home &footer; diff --git a/en/releases/2.1.6R/security.sgml b/en/releases/2.1.6R/security.sgml index ee3458cc62..209108f8be 100644 --- a/en/releases/2.1.6R/security.sgml +++ b/en/releases/2.1.6R/security.sgml @@ -1,28 +1,28 @@ - - + %includes; ]> &header;

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 FreeBSD-SA-97:01.setlocale security announcement.

Release Home &footer; diff --git a/en/releases/2.1.7R/announce.sgml b/en/releases/2.1.7R/announce.sgml index 6e7c96157e..8d30172d56 100644 --- a/en/releases/2.1.7R/announce.sgml +++ b/en/releases/2.1.7R/announce.sgml @@ -1,52 +1,52 @@ - - + %includes; ]> &header;

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 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/branch.html 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.

Release Home &footer; diff --git a/en/releases/2.1.7R/notes.sgml b/en/releases/2.1.7R/notes.sgml index 987d75c556..42ed352e45 100644 --- a/en/releases/2.1.7R/notes.sgml +++ b/en/releases/2.1.7R/notes.sgml @@ -1,559 +1,559 @@ - - + %includes; ]> - + &header;
                                  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:
       <browser> file:/usr/share/doc/handbook/handbook.html
 
   To read the FAQ:
       <browser> file:/usr/share/doc/FAQ/freebsd-faq.html
 
 You can also visit the master (and most frequently updated) copies at
 http://www.FreeBSD.org.
 
 The core of FreeBSD does not contain DES code which would inhibit its
 being exported outside the United States.  There is an add-on package
 to the core distribution, for use only in the United States, that
 contains the programs that normally use DES.  The auxiliary packages
 provided separately can be used by anyone.  A freely (from outside the
 U.S.) exportable distribution of DES for our non-U.S. users also
 exists at ftp://ftp.internat.FreeBSD.org/pub/FreeBSD.
 
 If password security for FreeBSD is all you need and you have no
 requirement for copying encrypted passwords from different hosts
 (Suns, DEC machines, etc) into FreeBSD password entries, then
 FreeBSD's MD5 based security may be all you require!  We feel that our
 default security model is more than a match for DES, and without any
 messy export issues to deal with.  If you're outside (or even inside)
 the U.S., give it a try!  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 <asami@FreeBSD.org>
         Andrey A. Chernov <ache@FreeBSD.org>
         John Dyson <dyson@FreeBSD.org>
         Bruce Evans <bde@FreeBSD.org>
         Justin Gibbs <gibbs@FreeBSD.org>
         David Greenman <davidg@FreeBSD.org>
         Jordan K. Hubbard <jkh@FreeBSD.org>
         Poul-Henning Kamp <phk@FreeBSD.org>
         Rich Murphey <rich@FreeBSD.org>
         Gary Palmer <gpalmer@FreeBSD.org>
         Søren Schmidt <sos@FreeBSD.org>
         Peter Wemm <peter@FreeBSD.org>
         Garrett A. Wollman <wollman@FreeBSD.org>
         Jörg Wunsch <joerg@FreeBSD.org>
 
 
 The FreeBSD Development Team, excluding core team members
 (in alphabetical order by last name):
 
         Ugen J.S. Antsilevich <ugen@FreeBSD.org>
         Torsten Blum <torstenb@FreeBSD.org>
         Gary Clark II <gclarkii@FreeBSD.org>
         Adam David <adam@FreeBSD.org>
         Peter Dufault <dufault@FreeBSD.org>
         Frank Durda IV <uhclem@FreeBSD.org>
         Julian Elischer <julian@FreeBSD.org>
         Sean Eric Fagan <sef@FreeBSD.org>
         Stefan Esser <se@FreeBSD.org>
         Bill Fenner <fenner@FreeBSD.org>
         John Fieber <jfieber@FreeBSD.org>
         Marc G. Fournier <scrappy@FreeBSD.org>
         Lars Fredriksen <lars@freeBSD.org>
         Thomas Gellekum <tg@FreeBSD.org>
         Thomas Graichen <graichen@FreeBSD.org>
         Rod Grimes <rgrimes@FreeBSD.org>
         John Hay <jhay@FreeBSD.org>
         Eric L. Hernes <erich@FreeBSD.org>
         Jeffrey Hsu <hsu@FreeBSD.org>
         Gary Jennejohn <gj@FreeBSD.org>
         Andreas Klemm <andreas@FreeBSD.org>
         L Jonas Olsson <ljo@FreeBSD.org>
         Scott Mace <smace@FreeBSD.org>
         Atsushi Murai <amurai@FreeBSD.org>
         Mark Murray <markm@FreeBSD.org>
         Alex Nash <alex@FreeBSD.org>
         Sujal Patel <smpatel@FreeBSD.org>
         Bill Paul <wpaul@FreeBSD.org>
         Joshua Peck Macdonald <jmacd@FreeBSD.org>
         John Polstra <jdp@FreeBSD.org>
         Mike Pritchard <mpp@FreeBSD.org>
         Doug Rabson <dfr@FreeBSD.org>
         James Raynard <jraynard@FreeBSD.org>
         Geoff Rehmet <csgr@FreeBSD.org>
         Martin Renters <martin@FreeBSD.org>
         Paul Richards <paul@FreeBSD.org>
         Ollivier Robert <roberto@FreeBSD.org>
         Dima Ruban <dima@FreeBSD.org>
         Wolfram Schneider <wosch@FreeBSD.org>
         Andreas Schulz <ats@FreeBSD.org>
         Karl Strickland <karl@FreeBSD.org>
         Paul Traina <pst@FreeBSD.org>
         Guido van Rooij <guido@FreeBSD.org>
         Steven Wallace <swallace@FreeBSD.org>
         Nate Williams <nate@FreeBSD.org>
         Jean-Marc Zucconi <jmz@FreeBSD.org>
 
 
 Additional FreeBSD helpers and beta testers:
 
         Coranth Gryphon            Dave Rivers 
         Kaleb S. Keithley          Michael Smith
         Terry Lambert              David Dawes
         Troy Curtis
 
 
 Special mention to:
 
         Walnut Creek CDROM, without whose help (and continuing support)
         this release would never have been possible.
 
         Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
         drive.
 
         Chuck Robey for his donation of a floppy tape streamer for
         testing.
 
         Larry Altneu and Wilko Bulte for providing us with Wangtek
         and Archive QIC-02 tape drives for testing and driver hacking.
 
         CalWeb Internet Services for the loan of a P6/200 machine for
         speedy package building.
 
         Everyone at Montana State University for their initial support.
 
         And to the many thousands of FreeBSD users and testers all over the
         world, without whom this release simply would not have been possible.
 
 We sincerely hope you enjoy this release of FreeBSD!
 
                         The FreeBSD Core Team
 

Release Home &footer; diff --git a/en/releases/2.1R/announce.sgml b/en/releases/2.1R/announce.sgml index 1e7c847c55..8834372501 100644 --- a/en/releases/2.1R/announce.sgml +++ b/en/releases/2.1R/announce.sgml @@ -1,59 +1,59 @@ - - + %includes; ]> &header;

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

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

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

FreeBSD 2.1.0-RELEASE is now available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly.

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

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

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

Jordan

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

Release Home &footer; diff --git a/en/releases/2.2.1R/notes.sgml b/en/releases/2.2.1R/notes.sgml index 8c634537d8..a265f80f8f 100644 --- a/en/releases/2.2.1R/notes.sgml +++ b/en/releases/2.2.1R/notes.sgml @@ -1,549 +1,549 @@ - - + %includes; ]> - + &header;
 
                                  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
 file systems, 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
 
 

Release Home &footer; diff --git a/en/releases/2.2.2R/errata.sgml b/en/releases/2.2.2R/errata.sgml index 646d7c1d40..7dd33c1b2e 100644 --- a/en/releases/2.2.2R/errata.sgml +++ b/en/releases/2.2.2R/errata.sgml @@ -1,79 +1,79 @@ - - + %includes; ]> - + &header;
 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.
 

Release Home &footer; diff --git a/en/releases/2.2.2R/notes.sgml b/en/releases/2.2.2R/notes.sgml index f55decc986..56081784ac 100644 --- a/en/releases/2.2.2R/notes.sgml +++ b/en/releases/2.2.2R/notes.sgml @@ -1,563 +1,563 @@ - - + %includes; ]> - + &header;
                                  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
 file systems, 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
 

Release Home &footer; diff --git a/en/releases/2.2.5R/announce.sgml b/en/releases/2.2.5R/announce.sgml index eaf43c83c5..6097cd9f16 100644 --- a/en/releases/2.2.5R/announce.sgml +++ b/en/releases/2.2.5R/announce.sgml @@ -1,96 +1,96 @@ - - + %includes; ]> &header;

Date: 22 Oct 1997 14:09:08 -0500
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
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 release notes for more information on this).

FreeBSD 2.2.5-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly 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

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 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.<yourdomain>.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

Release Home &footer; diff --git a/en/releases/2.2.5R/errata.sgml b/en/releases/2.2.5R/errata.sgml index 2b656eba9c..5ee5b17cc1 100644 --- a/en/releases/2.2.5R/errata.sgml +++ b/en/releases/2.2.5R/errata.sgml @@ -1,113 +1,113 @@ - - + %includes; ]> - + &header;
 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
 

Release Home &footer; diff --git a/en/releases/2.2.5R/notes.sgml b/en/releases/2.2.5R/notes.sgml index 0df2412a53..cf89c226f3 100644 --- a/en/releases/2.2.5R/notes.sgml +++ b/en/releases/2.2.5R/notes.sgml @@ -1,450 +1,450 @@ - - + %includes; ]> &header;
                                  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
 

Release Home &footer; diff --git a/en/releases/2.2.6R/announce.sgml b/en/releases/2.2.6R/announce.sgml index 5386369b65..74792dd347 100644 --- a/en/releases/2.2.6R/announce.sgml +++ b/en/releases/2.2.6R/announce.sgml @@ -1,88 +1,88 @@ - - + %includes; ]> &header;

Date: Wed Mar 25 04:24:34 PST 1998
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
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 release notes for a list of significant changes since the previous release.

FreeBSD 2.2.6-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly 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

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 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.<yourdomain>.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

Release Home &footer; diff --git a/en/releases/2.2.6R/errata.sgml b/en/releases/2.2.6R/errata.sgml index e7b1193a5f..047c61f321 100644 --- a/en/releases/2.2.6R/errata.sgml +++ b/en/releases/2.2.6R/errata.sgml @@ -1,133 +1,133 @@ - - + %includes; ]> - + &header;
 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.
 
 

Release Home &footer; diff --git a/en/releases/2.2.6R/notes.sgml b/en/releases/2.2.6R/notes.sgml index 9aace01d11..839bd43ccc 100644 --- a/en/releases/2.2.6R/notes.sgml +++ b/en/releases/2.2.6R/notes.sgml @@ -1,92 +1,92 @@ - - + %includes; ]> &header;
 ================================================================
                          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.
 
 

Release Home &footer; diff --git a/en/releases/2.2.7R/announce.sgml b/en/releases/2.2.7R/announce.sgml index ac3278e864..2fdd225d53 100644 --- a/en/releases/2.2.7R/announce.sgml +++ b/en/releases/2.2.7R/announce.sgml @@ -1,117 +1,117 @@ - - + %includes; ]> &header;

Date: Wed, 22 Jul 1998 08:36:25 -0700
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
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 release notes for more information).

FreeBSD 2.2.7-RELEASE is available on ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly 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

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 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 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.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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.F reeBSD.ORG/pub/FreeBSD
ftp://ftp2.internat.FreeBS D.ORG/pub/FreeBSD

Brazil

ftp://ftp.br.FreeBSD.ORG/p ub/FreeBSD

Finland

ftp://nic.funet.f i/pub/unix/FreeBSD/eurocrypt

Release Home &footer; diff --git a/en/releases/2.2.7R/errata.sgml b/en/releases/2.2.7R/errata.sgml index 3abc3c7596..70c2d566b3 100644 --- a/en/releases/2.2.7R/errata.sgml +++ b/en/releases/2.2.7R/errata.sgml @@ -1,69 +1,69 @@ - - + %includes; ]> - + &header;
 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
 
 

Release Home &footer; diff --git a/en/releases/2.2.7R/notes.sgml b/en/releases/2.2.7R/notes.sgml index b055b7b8ab..49467802cc 100644 --- a/en/releases/2.2.7R/notes.sgml +++ b/en/releases/2.2.7R/notes.sgml @@ -1,440 +1,440 @@ - - + %includes; ]> &header;
 ================================================================
                          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
 

Release Home &footer; diff --git a/en/releases/2.2.8R/announce.sgml b/en/releases/2.2.8R/announce.sgml index 5eff779dd3..63bb3ed0ed 100644 --- a/en/releases/2.2.8R/announce.sgml +++ b/en/releases/2.2.8R/announce.sgml @@ -1,109 +1,109 @@ - - + %includes; ]> &header;

Date: Sun, 29 Nov 1998 20:00:25 -0700
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject:FreeBSD 2.2.8 is now released!

It is, as always, my great pleasure to announce the release of FreeBSD 2.2.8, our latest and final 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 definitely encouraged to do so now as the 2.2-stable branch has gone into maintainence mode. A number of problems with 2.2.7 have been fixed and the release notes should be consulted for more information.

FreeBSD 2.2.8-RELEASE is available on ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly 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!

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

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 Pacific HiTech for information on ordering a localized (or the english) version of the 2.2.8 product. Pacific HiTech is now an affiliate of Walnut Creek CDROM for Japanese sales of FreeBSD.

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, 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.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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.F reeBSD.ORG/pub/FreeBSD
ftp://ftp2.internat.FreeBS D.ORG/pub/FreeBSD

Brazil

ftp://ftp.br.FreeBSD.ORG/p ub/FreeBSD

Finland

ftp://nic.funet.f i/pub/unix/FreeBSD/eurocrypt

Release Home &footer; diff --git a/en/releases/2.2.8R/errata.sgml b/en/releases/2.2.8R/errata.sgml index 13fa67fccd..404dc2e3e2 100644 --- a/en/releases/2.2.8R/errata.sgml +++ b/en/releases/2.2.8R/errata.sgml @@ -1,68 +1,68 @@ - - + %includes; ]> - + &header;
 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
 
 

Release Home &footer; diff --git a/en/releases/2.2.8R/notes.sgml b/en/releases/2.2.8R/notes.sgml index 79b0a17869..b6681f52ce 100644 --- a/en/releases/2.2.8R/notes.sgml +++ b/en/releases/2.2.8R/notes.sgml @@ -1,396 +1,396 @@ - - + %includes; ]> &header;
 
 ================================================================
                          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
 

Release Home &footer; diff --git a/en/releases/2.2R/announce.sgml b/en/releases/2.2R/announce.sgml index 3d73fadcba..087cfc397f 100644 --- a/en/releases/2.2R/announce.sgml +++ b/en/releases/2.2R/announce.sgml @@ -1,29 +1,29 @@ - - + %includes; ]> &header;

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.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly.

FreeBSD 2.2 represents a rather large leap in functionality from the 2.1.x releases, everyone being is strongly encouraged to read the release notes for a list of new features.

Release Home &footer; diff --git a/en/releases/2.2R/install-media.sgml b/en/releases/2.2R/install-media.sgml index 9f4583cfe1..c1d7af9e52 100644 --- a/en/releases/2.2R/install-media.sgml +++ b/en/releases/2.2R/install-media.sgml @@ -1,42 +1,42 @@ - - + %includes; ]> &header; From 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.

Release Home &footer; diff --git a/en/releases/2.2R/notes.sgml b/en/releases/2.2R/notes.sgml index 647014ab3c..60413aca05 100644 --- a/en/releases/2.2R/notes.sgml +++ b/en/releases/2.2R/notes.sgml @@ -1,518 +1,518 @@ - - + %includes; ]> - + &header;
                                  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
 file systems, 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
 
 

Release Home &footer; diff --git a/en/releases/3.0R/announce.sgml b/en/releases/3.0R/announce.sgml index e4580139c1..5c8a46e390 100644 --- a/en/releases/3.0R/announce.sgml +++ b/en/releases/3.0R/announce.sgml @@ -1,119 +1,119 @@ - - + %includes; ]> &header;

Date: Fri, 16 Oct 1998 13:19:03 -0700
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject:FreeBSD 3.0 is now released!

After what can only be described as a heroic effort by the FreeBSD Project volunteers, the long-awaited release of FreeBSD 3.0 is now out!

This release is primarily aimed at developers and early-adopters, though many ISPs have reported good results when using it in production (not that we recommend this to any but the most highly skilled). See the release notes for more information.

FreeBSD 3.0-RELEASE is available on ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly 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

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 Pacific HiTech for information on ordering a localized (or the english) version of the 3.0 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 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.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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.F reeBSD.ORG/pub/FreeBSD
ftp://ftp2.internat.FreeBS D.ORG/pub/FreeBSD

Brazil

ftp://ftp.br.FreeBSD.ORG/p ub/FreeBSD

Finland

ftp://nic.funet.f i/pub/unix/FreeBSD/eurocrypt

Release Home &footer; diff --git a/en/releases/3.0R/errata.sgml b/en/releases/3.0R/errata.sgml index b547058c0a..09bae3fefc 100644 --- a/en/releases/3.0R/errata.sgml +++ b/en/releases/3.0R/errata.sgml @@ -1,65 +1,65 @@ - - + %includes; ]> - + &header;
 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.
 
 

Release Home &footer; diff --git a/en/releases/3.0R/notes.sgml b/en/releases/3.0R/notes.sgml index 2f19e1694b..22bf1c3956 100644 --- a/en/releases/3.0R/notes.sgml +++ b/en/releases/3.0R/notes.sgml @@ -1,847 +1,847 @@ - - + %includes; ]> &header;
                                  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 /<basepath>/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
 

Release Home &footer; diff --git a/en/releases/3.1R/announce.sgml b/en/releases/3.1R/announce.sgml index 9b02fc9b22..6474934f54 100644 --- a/en/releases/3.1R/announce.sgml +++ b/en/releases/3.1R/announce.sgml @@ -1,112 +1,112 @@ - - + %includes; ]> &header;

Date: Mon, 15 Feb 1999 12:00:03 -0700
From: "Jordan K. Hubbard" <jkh@freebsd.org>
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 release notes for more information.

FreeBSD 3.1-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly 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 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 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.<yourdomain>.freebsd.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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

Release Home &footer; diff --git a/en/releases/3.1R/errata.sgml b/en/releases/3.1R/errata.sgml index c70329a10b..2062e1696d 100644 --- a/en/releases/3.1R/errata.sgml +++ b/en/releases/3.1R/errata.sgml @@ -1,84 +1,84 @@ - - + %includes; ]> - + &header;
 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.
 
 

Release Home &footer; diff --git a/en/releases/3.1R/notes.sgml b/en/releases/3.1R/notes.sgml index c9affd3643..1eb4a592b8 100644 --- a/en/releases/3.1R/notes.sgml +++ b/en/releases/3.1R/notes.sgml @@ -1,607 +1,607 @@ - - + %includes; ]> &header;
 
                                  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 /<basepath>/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
 
 

Release Home &footer; diff --git a/en/releases/3.2R/announce.sgml b/en/releases/3.2R/announce.sgml index 03d9ac2562..647d18b1aa 100644 --- a/en/releases/3.2R/announce.sgml +++ b/en/releases/3.2R/announce.sgml @@ -1,99 +1,99 @@ - - + %includes; ]> &header;

Date: Mon May 17 19:28:17 PDT 1999
From: "Jordan K. Hubbard" <jkh@freebsd.org>
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 release notes for more information.

FreeBSD 3.2-RELEASE is available at ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from 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 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.<yourdomain>.freebsd.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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

Release Home &footer; diff --git a/en/releases/3.2R/errata.sgml b/en/releases/3.2R/errata.sgml index f3becd0756..471863bc84 100644 --- a/en/releases/3.2R/errata.sgml +++ b/en/releases/3.2R/errata.sgml @@ -1,76 +1,76 @@ - - + %includes; ]> - + &header;
 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.
 
 

Release Home &footer; diff --git a/en/releases/3.2R/notes.sgml b/en/releases/3.2R/notes.sgml index 35809cf67f..6927f5f710 100644 --- a/en/releases/3.2R/notes.sgml +++ b/en/releases/3.2R/notes.sgml @@ -1,607 +1,607 @@ - - + %includes; ]> &header;
 
                                  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 /<basepath>/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
 
 

Release Home &footer; diff --git a/en/releases/3.3R/announce.sgml b/en/releases/3.3R/announce.sgml index 345387461e..ddd0a53218 100644 --- a/en/releases/3.3R/announce.sgml +++ b/en/releases/3.3R/announce.sgml @@ -1,118 +1,118 @@ - - + %includes; ]> &header;

Date: Fri, 17 Sep 1999 05:06:44 -0700
From: "Jordan K. Hubbard" <jkh@freebsd.org>
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 release notes for more information.

FreeBSD 3.3-RELEASE is available at ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from 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 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. 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 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 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.<yourdomain>.freebsd.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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

Release Home &footer; diff --git a/en/releases/3.3R/errata.sgml b/en/releases/3.3R/errata.sgml index 31d22bef21..2c1db2d321 100644 --- a/en/releases/3.3R/errata.sgml +++ b/en/releases/3.3R/errata.sgml @@ -1,133 +1,133 @@ - - + %includes; ]> - + &header;
 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
 
 

Release Home &footer; diff --git a/en/releases/3.3R/notes.sgml b/en/releases/3.3R/notes.sgml index f0f52b96ec..d6c2fd8fe7 100644 --- a/en/releases/3.3R/notes.sgml +++ b/en/releases/3.3R/notes.sgml @@ -1,689 +1,689 @@ - - + %includes; ]> &header;
 
                                  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 file systems 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 /<basepath>/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
 
 

Release Home &footer; diff --git a/en/releases/3.4R/announce.sgml b/en/releases/3.4R/announce.sgml index 8b33873309..3540a75acc 100644 --- a/en/releases/3.4R/announce.sgml +++ b/en/releases/3.4R/announce.sgml @@ -1,121 +1,121 @@ - - + %includes; ]> &header;

Date: Mon, 20 Dec 1999 10:45:47 -0800
From: "Jordan K. Hubbard" <jkh@freebsd.org>
Subject:FreeBSD 3.4-RELEASE is now available.

Just in under the wire for the current millenium, I'm happy to announce the availability of FreeBSD 3.4-RELEASE, the very latest in 3.x-STABLE branch technology. Following the release of FreeBSD 3.3 in Sept, 1999, a lot of new features have been added, many bugs were fixed and even more important security issues were dealt with. Please see the release notes for more information.

FreeBSD 3.4-RELEASE is available at ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from 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

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 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.<yourdomain>.freebsd.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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

Release Home &footer; diff --git a/en/releases/3.4R/errata.sgml b/en/releases/3.4R/errata.sgml index f67e6e55ae..8f0afdfef1 100644 --- a/en/releases/3.4R/errata.sgml +++ b/en/releases/3.4R/errata.sgml @@ -1,91 +1,91 @@ - - + %includes; ]> - + &header;
 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/<your-release>/ERRATA.TXT   
      (and any sites which keep up-to-date mirrors of this location).          
 
 Any changes to this file are also automatically emailed to:
 
         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;
   		}
 
 

Release Home &footer; diff --git a/en/releases/3.4R/notes.sgml b/en/releases/3.4R/notes.sgml index ce0438951d..70cf7806f9 100644 --- a/en/releases/3.4R/notes.sgml +++ b/en/releases/3.4R/notes.sgml @@ -1,635 +1,635 @@ - - + %includes; ]> &header;
                   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 /<basepath>/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
 

Release Home &footer; diff --git a/en/releases/3.5R/announce.sgml b/en/releases/3.5R/announce.sgml index d67a14b522..a08423727c 100644 --- a/en/releases/3.5R/announce.sgml +++ b/en/releases/3.5R/announce.sgml @@ -1,104 +1,104 @@ - - + %includes; ]> &header;

Date: Sat, 24 Jun 2000 18:23:01 -0700
From: "Jordan K. Hubbard" <jkh@freebsd.org>
Subject:FreeBSD 3.5 now available for x86

I'm pleased to announce the availability of FreeBSD 3.5-RELEASE, the very LAST in 3.x-STABLE branch technology. Following the release of FreeBSD 3.4 in December, 1999, many bugs were fixed, important security issues dealt with, and even a few new features added. Please see the release notes for more information.

FreeBSD 3.5-RELEASE is available at ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from 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

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 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.<yourdomain>.freebsd.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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

Release Home &footer; diff --git a/en/releases/3.5R/errata.sgml b/en/releases/3.5R/errata.sgml index dee765a1c3..fb7f272431 100644 --- a/en/releases/3.5R/errata.sgml +++ b/en/releases/3.5R/errata.sgml @@ -1,47 +1,47 @@ - - + %includes; ]> - + &header;
 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/<your-release>/ERRATA.TXT   
      (and any sites which keep up-to-date mirrors of this location).          
 
 Any changes to this file are also automatically emailed to:
 
         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:
 
 

Release Home &footer; diff --git a/en/releases/3.5R/notes.sgml b/en/releases/3.5R/notes.sgml index 449495c547..ee71ec3d6c 100644 --- a/en/releases/3.5R/notes.sgml +++ b/en/releases/3.5R/notes.sgml @@ -1,653 +1,653 @@ - - + %includes; ]> &header;
                   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 /<basepath>/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
 

Release Home &footer; diff --git a/en/releases/4.0R/announce.sgml b/en/releases/4.0R/announce.sgml index a308967517..8934550fab 100644 --- a/en/releases/4.0R/announce.sgml +++ b/en/releases/4.0R/announce.sgml @@ -1,115 +1,115 @@ - - + %includes; ]> &header;

Date: Tue, 14 Mar 2000 22:29:43 -0800 (PST)
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
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 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:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD (2.0C or 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

Release Home &footer; diff --git a/en/releases/4.0R/errata.sgml b/en/releases/4.0R/errata.sgml index 92b684f4ec..f2f28d24d5 100644 --- a/en/releases/4.0R/errata.sgml +++ b/en/releases/4.0R/errata.sgml @@ -1,90 +1,90 @@ - - + %includes; ]> - + &header;
 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/<your-release>/ERRATA.TXT   
      (and any sites which keep up-to-date mirrors of this location).          
 
 Any changes to this file are also automatically emailed to:
 
 	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.
 
 

Release Home &footer; diff --git a/en/releases/4.0R/notes.sgml b/en/releases/4.0R/notes.sgml index f661871880..59cfc8f4bb 100644 --- a/en/releases/4.0R/notes.sgml +++ b/en/releases/4.0R/notes.sgml @@ -1,878 +1,878 @@ - - + %includes; ]> &header;
                                  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 <jseger@FreeBSD.org> for almost single-handedly
         converting the ports collection to ELF.
 
         Doug Rabson <dfr@FreeBSD.org> and John Birrell <jb@FreeBSD.org>
         for making FreeBSD/alpha happen and to the NetBSD project for
         substantial indirect aid.
 
         Peter Wemm <peter@FreeBSD.org> 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
 

Release Home &footer; diff --git a/en/releases/4.1.1R/announce.sgml b/en/releases/4.1.1R/announce.sgml index 30c822e1ec..7202523868 100644 --- a/en/releases/4.1.1R/announce.sgml +++ b/en/releases/4.1.1R/announce.sgml @@ -1,83 +1,83 @@ - - + %includes; ]> &header;

Date: Wed, 27 Sep 2000 00:07:50 -070
From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>
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 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 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.<yourdomain>.freebsd.org/pub/FreeBSD
 

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

Thanks! - Jordan diff --git a/en/releases/4.1.1R/errata.sgml b/en/releases/4.1.1R/errata.sgml index f3432d6e4c..9b2367aace 100644 --- a/en/releases/4.1.1R/errata.sgml +++ b/en/releases/4.1.1R/errata.sgml @@ -1,47 +1,47 @@ - - + %includes; ]> - + &header;
 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/<your-release>/ERRATA.TXT   
      (and any sites which keep up-to-date mirrors of this location).          
 
 Any changes to this file are also automatically emailed to:
 
 	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:
 
 

Release Home &footer; diff --git a/en/releases/4.1.1R/notes.sgml b/en/releases/4.1.1R/notes.sgml index 8b24d88141..3f44eaa52d 100644 --- a/en/releases/4.1.1R/notes.sgml +++ b/en/releases/4.1.1R/notes.sgml @@ -1,736 +1,736 @@ - - + %includes; ]> &header;
 === 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 <jseger@freebsd.org> for almost single-handedly
         converting the ports collection to ELF.
 
         Doug Rabson <dfr@freebsd.org> and John Birrell <jb@freebsd.org>
         for making FreeBSD/alpha happen and to the NetBSD project for
         substantial indirect aid.
 
         Peter Wemm <peter@freebsd.org> 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
 
 

Release Home &footer; diff --git a/en/releases/4.1R/announce.sgml b/en/releases/4.1R/announce.sgml index 72d41795f5..997523676c 100644 --- a/en/releases/4.1R/announce.sgml +++ b/en/releases/4.1R/announce.sgml @@ -1,110 +1,110 @@ - - + %includes; ]> &header;

Date: Thu, 27 Jul 2000 05:17:09 -0700
From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>
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 i386 and 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 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:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

The latest versions of export-restricted code for FreeBSD 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/en/releases/4.1R/errata.sgml b/en/releases/4.1R/errata.sgml index 0574e11fcf..ccc4c2c837 100644 --- a/en/releases/4.1R/errata.sgml +++ b/en/releases/4.1R/errata.sgml @@ -1,76 +1,76 @@ - - + %includes; ]> - + &header;
 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/<your-release>/ERRATA.TXT   
      (and any sites which keep up-to-date mirrors of this location).          
 
 Any changes to this file are also automatically emailed to:
 
 	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.
 
 

Release Home &footer; diff --git a/en/releases/4.1R/notes.sgml b/en/releases/4.1R/notes.sgml index 16b93ec59e..1d2ab6fe70 100644 --- a/en/releases/4.1R/notes.sgml +++ b/en/releases/4.1R/notes.sgml @@ -1,785 +1,785 @@ - - + %includes; ]> &header;
                                  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
 

Release Home &footer; diff --git a/en/releases/4.2R/announce.sgml b/en/releases/4.2R/announce.sgml index 1f2eb5155b..205e4542c3 100644 --- a/en/releases/4.2R/announce.sgml +++ b/en/releases/4.2R/announce.sgml @@ -1,83 +1,83 @@ - - + %includes; ]> &header;

Date: Tue, 21 Nov 2000 04:31:48 -0800
From: "Jordan K. Hubbard" <jkh@winston.osd.bsdi.com>
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 i386 and 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 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.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

Thanks! - Jordan diff --git a/en/releases/4.2R/errata.sgml b/en/releases/4.2R/errata.sgml index 7eb39e9aeb..461b993ed5 100644 --- a/en/releases/4.2R/errata.sgml +++ b/en/releases/4.2R/errata.sgml @@ -1,47 +1,47 @@ - - + %includes; ]> - + &header;
 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/<your-release>/ERRATA.TXT   
      (and any sites which keep up-to-date mirrors of this location).          
 
 Any changes to this file are also automatically emailed to:
 
 	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:
 
 

Release Home &footer; diff --git a/en/releases/4.2R/notes.sgml b/en/releases/4.2R/notes.sgml index da4d40e01a..40f30e7803 100644 --- a/en/releases/4.2R/notes.sgml +++ b/en/releases/4.2R/notes.sgml @@ -1,1025 +1,1025 @@ - - + %includes; ]> &header;
                                  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
 
 

Release Home &footer; diff --git a/en/releases/4.3R/announce.sgml b/en/releases/4.3R/announce.sgml index 89751deded..0d6644293a 100644 --- a/en/releases/4.3R/announce.sgml +++ b/en/releases/4.3R/announce.sgml @@ -1,89 +1,89 @@ - - + %includes; ]> &header;

Date: Friday, 20 Apr 2001 21:00:00 -0800
From: "Jordan K. Hubbard" <jkh@freebsd.org>
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 i386 and 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 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.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

Thanks! - Jordan diff --git a/en/releases/4.3R/errata.sgml b/en/releases/4.3R/errata.sgml index 612dfca6ce..09e6d2039f 100644 --- a/en/releases/4.3R/errata.sgml +++ b/en/releases/4.3R/errata.sgml @@ -1,109 +1,109 @@ - - + %includes; ]> - + &header;
 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/<your-release>/ERRATA.TXT   
      (and any sites which keep up-to-date mirrors of this location).          
 
 Any changes to this file are also automatically emailed to:
 
 	freebsd-current@FreeBSD.org
 
 For all FreeBSD security advisories, see:
 
 	http://www.FreeBSD.org/security/
 
 for the latest security incident information.
 
 ---- Security Advisories:
 
 The vulnerability documented in security advisory FreeBSD-SA-01:39 was
 fixed in FreeBSD 4.3-RELEASE.  The release notes mentioned the fix,
 but made no mention of the security advisory.
 
 A vulnerability in the fts(3) routines (used by applications for
 recursively traversing a filesystem) could allow a program to operate
 on files outside the intended directory hierarchy.  This bug, as well
 as a fix, is described in security advisory FreeBSD-SA-01:40.
 
 A flaw allowed some signal handlers to remain in effect in a child
 process after being exec-ed from its parent.  This allowed an attacker
 to execute arbitrary code in the context of a setuid binary.  More
 details, as well as a fix, are described in security advisory
 FreeBSD-SA-01:42.
 
 A remote buffer overflow in tcpdump(1) could be triggered by sending
 certain packets at a target machine.  More details, as well as a fix,
 can be found in security advisory FreeBSD-SA-01:48.
 
 A remote buffer overflow in telnetd(8) could result in arbitrary code 
 running on a target machine.  More details, as well as a fix, can be 
 found in security advisory FreeBSD-SA-01:49.
 
 A vulnerability whereby a remote attacker could exhaust a target's
 pool of network buffers has been closed.  More details, as well as a
 fix, can be found in security advisory FreeBSD-SA-01:52.
 
 A flaw existed in ipfw(8), in which ``me'' filter rules would match
 the remote IP address of a point-to-point interface in addition to the
 intended local IP address.  More details, as well as a fix, can be
 found in security advisory FreeBSD-SA-01:53.
 
 A vulnerability in procfs(5) could allow a process to read sensitive
 information from another process's memory space.  For more details, as
 well as information on patches, see security advisory
 FreeBSD-SA-01:55.
 
 PARANOID hostname checking in tcp_wrappers did not work correctly.
 For more details and information on patches, see security advisory
 FreeBSD-SA-01:56.
 
 sendmail(8) has a local root vulnerability.  For more details and
 patch information, see security advisory FreeBSD-SA-01:57.
 
 lpd(8) contained a remotely-exploitable buffer overflow.  For more
 details, and a fix for this problem, see security advisory
 FreeBSD-SA-01:58.
 
 rmuser(8) had a race condition that briefly exposed a world-readable
 /etc/master.passwd.  For more details, as well as workarounds and
 solutions, see security advisory FreeBSD-SA-01:59.
 
 ---- System Update Information:
 
 The release note entry for the ESS Maestro-3/Allegro sound driver gave
 an incorrect command for loading the driver via /boot/loader.conf.
 The correct command is:
 
 	snd_maestro3_load="YES"
 
 ssh(1) is no longer SUID root.  The primary manifestation of this
 change is that .shosts authentication may not work "out of the box".
 Both temporary and permanent fixes are described in the FAQ at:
 
 	http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#SSH-SHOSTS
 
 

Release Home &footer; diff --git a/en/releases/4.3R/notes.sgml b/en/releases/4.3R/notes.sgml index 7fd67b7eee..b64fee2d82 100644 --- a/en/releases/4.3R/notes.sgml +++ b/en/releases/4.3R/notes.sgml @@ -1,1275 +1,1275 @@ - - + %includes; ]> &header;
                                  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
 

Release Home &footer; diff --git a/en/releases/4.4R/announce.sgml b/en/releases/4.4R/announce.sgml index 359ed5ae0b..856427a373 100644 --- a/en/releases/4.4R/announce.sgml +++ b/en/releases/4.4R/announce.sgml @@ -1,100 +1,100 @@ - - + %includes; ]> &header;

Date: Thursday, 20 Sep 2001 18:00:00 -0800
From: "Jordan K. Hubbard" <jkh@freebsd.org>
To: announce@FreeBSD.org
Subject: 4.4-RELEASE is now available

I am very pleased to announce the availability of FreeBSD 4.4-RELEASE, the very very latest in 4.x-STABLE branch technology. Since FreeBSD 4.3 was released in April 2001, we have made hundreds of fixes, updated many different components and addressed a wide variety of security issues. We have also substantially revamped the documentation and provided much more comprehensive release notes. Please see the various HTML (or, at your option, text) files in the release directory for more information.

4.4-RELEASE is available for the i386 and 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.4/
and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.4/

Where ${arch} is currently "i386" or "alpha". 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 The FreeBSD Mall. Each CD sets contains the FreeBSD installation and application package bits for the x86 ("PC") architecture. 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 can no longer fit on the 4 ISO set.

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, Mordor, 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.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

Most releases prior to 4.4-RELEASE have been team efforts, only possible at all due to the collaboration of many different people. It still bears noting, however, that 4.4-RELEASE was done completely by a "release engineering team" rather than "a release engineer" and I think it's fair to say that with 4.4-RELEASE, we've completed the transition from having one primary person worry about releases to having many primary people (re@FreeBSD.org) worry about them. This is a distinct improvement from any point of view and, I think, an important milestone in FreeBSD's progress.

In addition to myself, the release engineering team for 4.4-RELEASE has been:

Murray Stokely <murray@freebsd.org> : Release Engineering
Steve Price <steve@FreeBSD.org> : Package collection
Satoshi Asami <asami@FreeBSD.org> : Package collection
Bruce A. Mah <bmah@FreeBSD.org> : Release notes

Please join me in thanking them for all the hard work which went into making this release. I would also like to thank the FreeBSD Committers <committers@FreeBSD.org>, without which there would be nothing to release, and the many thousands of FreeBSD users world-wide who contributed bug fixes, features and suggestions.

Thanks!

- Jordan diff --git a/en/releases/4.4R/hardware.sgml b/en/releases/4.4R/hardware.sgml index a5d94781a8..45b0e64b5c 100644 --- a/en/releases/4.4R/hardware.sgml +++ b/en/releases/4.4R/hardware.sgml @@ -1,26 +1,26 @@ - - + %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.4 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

diff --git a/en/releases/4.4R/notes.sgml b/en/releases/4.4R/notes.sgml index c49be3b53d..8dc859da33 100644 --- a/en/releases/4.4R/notes.sgml +++ b/en/releases/4.4R/notes.sgml @@ -1,26 +1,26 @@ - - + %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.4 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

diff --git a/en/releases/4.5R/announce.sgml b/en/releases/4.5R/announce.sgml index d284c7d1ab..8d0b6098b4 100644 --- a/en/releases/4.5R/announce.sgml +++ b/en/releases/4.5R/announce.sgml @@ -1,153 +1,153 @@ - - + %includes; ]> &header;

Date: Tuesday, 29 Jan 2002 20:00:00 -0800
From: "Murray Stokely" <murray@FreeBSD.org>
To: announce@FreeBSD.org
Subject: 4.5-RELEASE is now available

I am very pleased to announce the availability of FreeBSD 4.5-RELEASE, the very latest release on the FreeBSD -STABLE branch of development. Since FreeBSD 4.4 was released in September 2001, we have made hundreds of fixes, updated many system components, made several substantial performance improvements, and addressed a wide variety of security issues.

In particular, there have been significant enhancements in the areas of network communications and filesystems. FreeBSD 4.5 contains improvements to the TCP stack to provide better throughput. In addition, TCP performance is aided by larger default buffer sizes. Finally, FreeBSD 4.5 contains new mechanisms to mitigate the effects of TCP Denial of Service attacks.

The FFS filesystem benefits from a new directory layout strategy that has demonstrated significantly better performance for operations traversing large directory structures. Various bugs were located and fixed in the FFS and NFS code with the help of a filesystem exercising program originally developed at Apple Computer, Inc.

Those users doing fresh installations of FreeBSD should note some changes for newly created filesystems, intended to improve the "out of the box" performance of FreeBSD. In particular, sysinstall(8) now enables Soft Updates (a strategy for improving both performance and reliability of on-disk data structures) for new filesystems it creates and the newfs(8) program will now, by default, create filesystems with larger block sizes.

For more information about the most significant changes with this release of FreeBSD, please see the release section of our web site:

http://www.FreeBSD.org/releases/

There you will find Release Notes, Hardware Notes, and a list of Errata.

Availability

4.5-RELEASE is available for the i386 and alpha architectures and can be installed directly over the net using the boot floppies or copied to a local NFS/FTP server.

We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from:

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 continue to support the FreeBSD project by purchasing media from one of our supporting vendors. The following companies have contributed substantially to the development of FreeBSD :

FreeBSD Mall, Inc.http://www.freebsdmall.com
FreeBSD Services Ltd.http://www.freebsd-services.com
Daemon Newshttp://www.bsdmall.com/freebsd1.html

Each CD set contains the FreeBSD installation and application package bits for the i386 ("PC") architecture. For a set of distfiles used to build ports in the ports collection, please see the FreeBSD Toolkit, a 6 CD set containing extra bits which no longer fit on the 4 CD set.

FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Lithuania, Latvia, the Netherlands, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom.

Before trying the central FTP site, please check your regional mirror(s) first by going to:

ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD

Any additional mirror sites will be labeled ftp2, ftp3 and so on.

See the FreeBSD Handbook for additional information about FreeBSD mirror sites.

The FreeBSD installation instructions have recently been significantly enhanced. Chapter 2 of The FreeBSD Handbook, available online, provides a complete installation walk-through for users new to FreeBSD.

Acknowledgments

Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 4.5, including Compaq, Yahoo!, and The FreeBSD Mall.

In addition to myself, the release engineering team for 4.5-RELEASE includes:

Robert Watson <rwatson@FreeBSD.org>Release Engineering
John Baldwin <jhb@FreeBSD.org>Release Engineering
Bruce A. Mah <bmah@FreeBSD.org>Release Documentation
Steve Price <steve@FreeBSD.org>Package Building
Wilko Bulte <wilko@FreeBSD.org>Alpha Platform Release Engineering
Peter Wemm <peter@FreeBSD.org>Ports Cluster System Administration

Please join me in thanking them for all the hard work which went into making this release. I would also like to thank the FreeBSD Committers (committers@FreeBSD.org), without whom there would be nothing to release, and the many thousands of FreeBSD users world-wide who contributed bug fixes, features and suggestions.

Thanks!

- Murray

diff --git a/en/releases/4.5R/hardware.sgml b/en/releases/4.5R/hardware.sgml index 0fa5b424a9..34f9959ce5 100644 --- a/en/releases/4.5R/hardware.sgml +++ b/en/releases/4.5R/hardware.sgml @@ -1,26 +1,26 @@ - - + %includes; ]> &header;

The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Hardware notes for FreeBSD 4.5 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

diff --git a/en/releases/4.5R/notes.sgml b/en/releases/4.5R/notes.sgml index c77d466c21..c07ee637b7 100644 --- a/en/releases/4.5R/notes.sgml +++ b/en/releases/4.5R/notes.sgml @@ -1,26 +1,26 @@ - - + %includes; ]> &header;

The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.

Release notes for FreeBSD 4.5 are available for the following platforms:

A list of all platforms currently under development can be found on the Supported Platforms page.

diff --git a/en/releases/snapshots.sgml b/en/releases/snapshots.sgml index c3a3956e69..f955842530 100644 --- a/en/releases/snapshots.sgml +++ b/en/releases/snapshots.sgml @@ -1,86 +1,86 @@ - - + %includes; ]> - + &header;

What are snapshots?

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

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

Where to find snapshots

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

By popular demand, snapshots are also now available for the FreeBSD-stable branch via anonymous FTP from ftp://releng4.FreeBSD.org/pub/FreeBSD/. The snapshot releases are in directories named in the same manner as -current snapshots, but ending in the keyword RELENG instead of SNAP.

Release Home &footer; diff --git a/en/search/index-site.sgml b/en/search/index-site.sgml index 76c6d4f9ed..335a23b306 100644 --- a/en/search/index-site.sgml +++ b/en/search/index-site.sgml @@ -1,54 +1,54 @@ - - + %includes; ]> &header;

Site Map

&site;

Meta homepages


A-Z Index

&atoz; &footer; diff --git a/en/search/search-mid.sgml b/en/search/search-mid.sgml index 4c24a07a0d..0b07969c32 100644 --- a/en/search/search-mid.sgml +++ b/en/search/search-mid.sgml @@ -1,37 +1,37 @@ - - + %includes; ]> &header;
Message-ID:
Answers to a Message-ID:

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.

Full text mailing list archives. &footer; diff --git a/en/search/searchhints.sgml b/en/search/searchhints.sgml index 24de4a7ec3..f924d52c70 100644 --- a/en/search/searchhints.sgml +++ b/en/search/searchhints.sgml @@ -1,52 +1,52 @@ - - + %includes; ]> &header;

If you got lots of irrelevant results...

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

  2. 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...

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

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

  3. Try discarding words that could be implied by the context of the message. For example "quantum and hard and drive" might miss some relevant messages that "quantum and drive" would get.

Return to the search page &footer;