os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Throwing a bunch of random dates and numbers is largely uninteresting so just give some historical background.

Browse source 
- Remove attribution as the section has been changed and modified many times since then (and should be some more)
- Change from <quote> to "s where not used as an attribution.
- Simplify text surrounding snapshots.

Reviewed by:	trhodes
This commit is contained in:
Eitan Adler 2013-05-27 20:27:03 +00:00
parent 53f7697fdd
commit 87bce4edad
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41755
1 changed files with 20 additions and 100 deletions

120
en_US.ISO8859-1/books/handbook/introduction/chapter.xml
View file

@ -541,16 +541,6 @@
the development model of the project.</para>
<sect2 id="intro-history">
<sect2info role="firstperson">
<authorgroup>
<author>
<firstname>Jordan</firstname>
<surname>Hubbard</surname>
<contrib>Contributed by </contrib>
</author>
</authorgroup>
</sect2info>
<title>A Brief History of &os;</title>
<indexterm><primary>386BSD Patchkit</primary></indexterm>
@ -562,24 +552,24 @@
<secondary>history</secondary>
</indexterm>
<para>The &os;&nbsp;Project had its genesis in the early part
of 1993, partially as an outgrowth of the <quote>Unofficial
386BSDPatchkit</quote> by the patchkit's last 3
coordinators: Nate Williams, Rod Grimes and myself.</para>
of 1993, partially as an outgrowth of the Unofficial
386BSDPatchkit by the patchkit's last 3
coordinators: Nate Williams, Rod Grimes and Jordan
Hubbard.</para>
<indexterm><primary>386BSD</primary></indexterm>
<para>Our original goal was to produce an intermediate snapshot
<para>The original goal was to produce an intermediate snapshot
of 386BSD in order to fix a number of problems with it that
the patchkit mechanism just was not capable of solving. Some
of you may remember the early working title for the project
being <quote>386BSD 0.5</quote> or <quote>386BSD
Interim</quote> in reference to that fact.</para>
the patchkit mechanism just was not capable of solving. The
early working title for the project was
386BSD 0.5 or 386BSD Interim in
reference of that fact.</para>
<indexterm><primary>Jolitz, Bill</primary></indexterm>
<para>386BSD was Bill Jolitz's operating system, which had been
up to that point suffering rather severely from almost a
year's worth of neglect. As the patchkit swelled ever more
uncomfortably with each passing day, we were in unanimous
agreement that something had to be done and decided to assist
uncomfortably with each passing day, they decided to assist
Bill by providing this interim <quote>cleanup</quote>
snapshot. Those plans came to a rude halt when Bill Jolitz
suddenly decided to withdraw his sanction from the project
@ -588,12 +578,12 @@
<indexterm><primary>Greenman, David</primary></indexterm>
<indexterm><primary>Walnut Creek CDROM</primary></indexterm>
<para>It did not take us long to decide that the goal remained
worthwhile, even without Bill's support, and so we adopted the
name <quote>&os;</quote>, coined by David Greenman. Our
<para>The trio thought that the goal remained
worthwhile, even without Bill's support, and so they adopted the
name "&os;" coined by David Greenman. The
initial objectives were set after consulting with the system's
current users and, once it became clear that the project was
on the road to perhaps even becoming a reality, I contacted
on the road to perhaps even becoming a reality, Jordan contacted
Walnut Creek CDROM with an eye toward improving &os;'s
distribution channels for those many unfortunates without easy
access to the Internet. Walnut Creek CDROM not only supported
@ -615,7 +605,7 @@
on the 4.3BSD-Lite (<quote>Net/2</quote>) tape from U.C.
Berkeley, with many components also provided by 386BSD and the
Free Software Foundation. It was a fairly reasonable success
for a first offering, and we followed it with the highly
for a first offering, and they followed it with the highly
successful &os; 1.1 release in May of 1994.</para>
<indexterm><primary>Novell</primary></indexterm>
@ -654,83 +644,13 @@
more robust and easier to install &os;&nbsp;2.0.5 release in
June of 1995.</para>
<para>We released &os;&nbsp;2.1.5 in August of 1996, and it
appeared to be popular enough among the ISP and commercial
communities that another release along the 2.1-STABLE branch
was merited. This was &os;&nbsp;2.1.7.1, released in February
1997 and capping the end of mainstream development on
2.1-STABLE. Now in maintenance mode, only security
enhancements and other critical bug fixes will be done on this
branch (RELENG_2_1_0).</para>
<para>&os;&nbsp;2.2 was branched from the development mainline
(<quote>-CURRENT</quote>) in November 1996 as the RELENG_2_2
branch, and the first full release (2.2.1) was released in
April 1997. Further releases along the 2.2 branch were done
in the summer and fall of '97, the last of which (2.2.8)
appeared in November 1998. The first official 3.0 release
appeared in October 1998 and spelled the beginning of the end
for the 2.2 branch.</para>
<para>The tree branched again on Jan 20, 1999, leading to the
4.0-CURRENT and 3.X-STABLE branches. From 3.X-STABLE, 3.1 was
released on February 15, 1999, 3.2 on May 15, 1999, 3.3 on
September 16, 1999, 3.4 on December 20, 1999, and 3.5 on
June 24, 2000, which was followed a few days later by a minor
point release update to 3.5.1, to incorporate some last-minute
security fixes to Kerberos. This will be the final release
in the 3.X branch.</para>
<para>There was another branch on March 13, 2000, which saw the
emergence of the 4.X-STABLE branch. There have been several
releases from it so far: 4.0-RELEASE was introduced in March
2000, and the last 4.11-RELEASE came out in January
2005.</para>
<para>The long-awaited 5.0-RELEASE was announced on January 19,
2003. The culmination of nearly three years of work, this
release started &os; on the path of advanced multiprocessor
and application thread support and introduced support for the
&ultrasparc; and <literal>ia64</literal> platforms. This
release was followed by 5.1 in June of 2003. The last 5.X
release from the -CURRENT branch was 5.2.1-RELEASE, introduced
in February 2004.</para>
<para>The RELENG_5 branch, created in August 2004, was followed
by 5.3-RELEASE, which marked the beginning of the 5-STABLE
branch releases. The most recent 5.5-RELEASE release came out
in May 2006. There will be no additional releases from the
RELENG_5 branch.</para>
<para>The tree was branched again in July 2005, this time for
RELENG_6. 6.0-RELEASE, the first release of the 6.X branch,
was released in November 2005. The most recent 6.4-RELEASE
came out in November 2008. There will be no additional
releases from the RELENG_6 branch. This branch is the last
branch to support the Alpha architecture.</para>
<para>The RELENG_7 branch was created in October 2007. The
first release of this branch was 7.0-RELEASE, which came
out in February 2008. The most recent 7.4-RELEASE came out
in February 2011. There will be no additional releases from
the RELENG_7 branch.</para>
<para>The tree was branched again in August 2009, this time for
RELENG_8. 8.0-RELEASE, the first release of the 8.X branch,
was released in November 2009. The most recent
&rel2.current;-RELEASE came out in &rel2.current.date;. There
will be additional releases from the RELENG_8 branch.</para>
<para>The RELENG_9 branch was created in September 2011. The
first release of this branch was 9.0-RELEASE, which came
out in January 2012. The most recent &rel.current;-RELEASE
came out in &rel.current.date;. There will be additional
releases from the RELENG_9 branch.</para>
<para>Since that time, &os; has made a series of releases each
time improving the stability, speed, and feature set of the
previous version.</para>
<para>For now, long-term development projects continue to take
place in the 10.X-CURRENT (trunk) branch, and SNAPshot
releases of 10.X on CD-ROM (and, of course, on the net) are
continually made available from <ulink
place in the 10.X-CURRENT (trunk) branch, and snapshot
releases of 10.X are continually made available from <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/">the
snapshot server</ulink> as work progresses.</para>
</sect2>