- -
From owner-svn-doc-projects@FreeBSD.ORG Sun Jul 15 10:38:23 2012
Return-Path: This document describes how to build and update
the FreeBSD Web pages from the CVS repository by hand. While you might expect an operating system with these
features to sell for a high price, FreeBSD is available
@@ -103,7 +106,6 @@
Foundation, P.O. Box 20247, Boulder, CO 80308,
USA. The Bugmeisters and GNATS Administrators are responsible for ensuring
@@ -522,6 +524,5 @@
Much of the success which surrounds FreeBSD is due to people advocating its use to
their friends, colleagues, and employers. As the BSD projects (DragonFlyBSD, FreeBSD, NetBSD, and OpenBSD) have grown in size,
a number of persistent myths have grown up around them. Some of these are
@@ -115,7 +118,7 @@
Pointers to this system litter the documentation. Not everyone can commit code changes to the *BSD code. You
- need to be a committer first. Typically, people are offered
+ need to be a committer first. Typically, people are offered
``commit privs'' after they have made a few well-thought out
submissions to the project using send-pr or similar.Header And Logo
-
- Peripheral Links
+Peripheral Links'>
-
Header And Logo
+
+ Section Navigation
@@ -25,12 +23,9 @@
Section Navigation
@@ -45,12 +40,9 @@
Section Navigation
@@ -64,12 +56,9 @@
Section Navigation
@@ -84,37 +73,25 @@
Section Navigation
+
&rel3.current;Section Navigation
@@ -139,12 +116,9 @@
'>
-]]>
-
-
+
Section Navigation
'>
-]]>
-
-
+
Section Navigation
@@ -190,4 +161,39 @@
'>
+
+
+
From owner-svn-doc-projects@FreeBSD.ORG Sun Jul 15 10:41:06 2012
Return-Path:
+
+ &lastmod;
+
+ What is FreeBSD?
@@ -71,7 +74,7 @@
FreeBSD is free
-
+
Introduction
@@ -49,7 +51,7 @@
-
+
FreeBSD Core Team
<core@FreeBSD.org>
@@ -132,7 +134,7 @@
+
Primary Release Engineering Team
<re@FreeBSD.org>
@@ -168,7 +170,7 @@
+
Donations Team
<donations@FreeBSD.org>
@@ -261,7 +263,7 @@
+
Core Team Secretary
<core-secretary@FreeBSD.org>
@@ -308,7 +310,7 @@
+
Accounts Team
@@ -337,7 +339,7 @@
Bugmeisters & GNATS Administrators
+
Bugmeisters & GNATS Administrators
<bugmeister@FreeBSD.org>
+ takes place separately.
Hybrid Cluster is a web cluster, based on FreeBSD and ZFS, which provides data redundancy and automated load balancing of standard LAMP - websites and applications. + websites and applications.
Frenzy is another live-CD distribution, but customized for administering tasks. It contains software for hardware tests, file system checks, security checks, network setup - and analysis.
PicoBSD @@ -230,7 +233,7 @@ it started as a spinoff from the NetBSD project, and has since evolved its own distinctive approach.
-GEOM classess: GEOM is a modular disk framework that lets you concatenate, mirror, stripe, or encrypt disks. It is rich - in functionality and keeps your data safe.
This is user opinion only.
-This is user opinion only.
----Mark Hittinger, administrator of WinNet Communications, Inc.
The content of this page has been integrated into the main FreeBSD webpage. You should be automatically redirected there in a few seconds. If not, Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/commercial/commercial.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/commercial/commercial.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/commercial/commercial.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,12 +1,15 @@ - + + - ]> - -&header; + +
The power, flexibility, and reliability of FreeBSD attract a wide variety of users and vendors. Below is a list of vendors offering @@ -48,7 +51,6 @@ to the internet, these companies may off not signify our endorsement of their products or services by the FreeBSD Project.
-&footer; Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/irc.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/community/irc.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/community/irc.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,12 +1,15 @@ - + + - ]> - -&header; + +While #freebsd channels exist on various IRC networks, the FreeBSD project does not control them or endorse IRC as a support medium. @@ -21,7 +24,6 @@ the FAQ entry for more information.
-&footer; Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/mailinglists.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/community/mailinglists.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/community/mailinglists.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,12 +1,15 @@ - + + - ]> - -&header; + +Mailing lists are the primary communication channels for the FreeBSD community, and cover many topic areas.
@@ -118,7 +121,6 @@If you create other FreeBSD mailing lists, let us know about them.
-&footer; Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/newsgroups.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/community/newsgroups.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/community/newsgroups.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,12 +1,15 @@ - + + - ]> - -&header; + +There are a few FreeBSD specific newsgroups, along with @@ -17,7 +20,6 @@ For important announcements, see comp.unix.bsd.freebsd.announce.
-&footer; Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/webresources.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/community/webresources.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/community/webresources.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,12 +1,15 @@ - + + - ]> - -&header; + +Our web pages remain one of the best sources of information, and are also mirrored at many sites around the world. Try connecting to @@ -51,7 +54,6 @@
For information on recent FreeBSD progress and releases, see the Newsflash page.
-&footer; Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/copyright.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/copyright.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/copyright.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,14 +1,17 @@ - + + - ]> - -&header; + ++
-&footer; Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/daemon.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/daemon.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/daemon.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,12 +1,15 @@ - + + - ]> - -&header; + +The little red fellow that graces many of these pages is the BSD Daemon. In the context of &unix; systems, daemons @@ -40,12 +43,12 @@ Marshall Kirk McKusick. A short pictorial history is also available. There is a gallery of FreeBSD related -publications that use +publications that use variations of the daemon graphic.
Various size stuffed and beanie daemons are available from the FreeBSD Mall - .
+ .ScotGold produce 1" case badges featuring BSD Daemon.
@@ -55,15 +58,14 @@ variations of the daemon graphic.Permission to use the daemon may be obtained from:
-Marshall Kirk McKusick+
1614 Oxford St
- Berkeley, CA 94709-1608
USA
Marshall Kirk McKusick
1614 Oxford St
+ Berkeley, CA 94709-1608
USA
or via email at mckusick@mckusick.com.
-Legal Home -&footer; +Legal Home Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,12 +1,15 @@ - + + - ]> - -&header; + +Copyright 1994-2012 The FreeBSD Project. @@ -79,6 +82,5 @@ Legal Home -&footer; Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/freebsd-license.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/freebsd-license.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/freebsd-license.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,12 +1,15 @@ - + + - ]> - -&header; + +
Copyright 1992-2012 The FreeBSD Project. @@ -47,7 +50,6 @@ interpreted as representing official policies, either expressed or implied, of the FreeBSD Project.
-Legal Home -&footer; +Legal Home Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/license.sgml ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/license.sgml Sun Jul 15 10:43:51 2012 (r39212) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/copyright/license.sgml Sun Jul 15 10:46:37 2012 (r39213) @@ -1,35 +1,38 @@ - + + - ]> - -&header; + +All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by The - Regents of the University of California. + Regents of the University of California.
Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. - All rights reserved. + All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the - following conditions are met: + following conditions are met:
This product includes software developed by the University of California, Berkeley and its - contributors.+ contributors.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS @@ -59,15 +61,15 @@ CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH - DAMAGE. + DAMAGE.
The Institute of Electrical and Electronics Engineers and the American National Standards Committee X3, on Information Processing Systems have given us permission to - reprint portions of their documentation. + reprint portions of their documentation.
In the following statement, the phrase ``this text'' - refers to portions of the system documentation. + refers to portions of the system documentation.
Portions of this text are reprinted and reproduced in electronic form in the second BSD Networking Software @@ -77,10 +79,10 @@ and Electronics Engineers, Inc. In the event of any discrepancy between these versions and the original IEEE Standard, the original IEEE Standard is the referee - document. + document.
In the following statement, the phrase ``This material'' - refers to portions of the system documentation. + refers to portions of the system documentation.
This material is reproduced with permission from American National Standards Committee X3, on Information Processing @@ -88,7 +90,7 @@ Association (CBEMA), 311 First St., NW, Suite 500, Washington, DC 20001-2178. The developmental work of Programming Language C was completed by the X3J11 Technical - Committee. + Committee.
The views and conclusions contained in the software and documentation are those of the authors and should not be @@ -96,7 +98,7 @@ expressed or implied, of the Regents of the University of California.
-NOTE: The copyright of UC Berkeley's Berkeley Software Distribution ("BSD") source has been updated. The copyright @@ -130,12 +132,11 @@ of those BSD Unix files containing it is hereby deleted in its entirety.
-William Hoskins
- Director, Office of Technology Licensing
+
William Hoskins
+ Director, Office of Technology Licensing
University of California, Berkeley
Events from past years:
Last year there were
&os; is represented on a number of different social networks.
@@ -56,7 +47,5 @@ -Search the ia64 mailing list archives:
@@ -82,8 +63,5 @@ of ABI breaking changes in the pipeline and having to maintain backward compatibility this early in a ports life is less than ideal. -The ideas page has moved to the FreeBSD wiki.
-The FreeBSD Project is looking forward to participating as a mentoring organization in GSoC 2011 Timeline
+All students must register with, and submit applications via, the Google Summer of Code home page:
- +What advice do you have for a student who might want to submit a proposal?
@@ -371,12 +361,10 @@ href="http://wiki.freebsd.org/moin.cgi/S secretaries to distribute. You can also print out and post copies of the FreeBSD GSoC 2011 poster. - -&os; is represented on a number of different social + networks.
+ +Search the ia64 mailing list archives:
+ + + +The FreeBSD/ia64 project pages contain information about the + FreeBSD port to Intel's IA-64 architecture; officially known as + the Intel Itanium® Processor Family (IPF). As with the port + itself, these pages are still mostly a work in progress.
+ +The ia64 port is still considered a tier 2 platform. This boils
+ down to not being fully supported by our security officer, release
+ engineers and toolchain maintainers. In practice however the
+ distinction between a tier 1 platform (which is fully supported)
+ and a tier 2 platform is not as strict as it seems. In almost all
+ aspects the ia64 port is a tier 1 platform.
+
+ From a developer point of view there's an advantage to have the ia64
+ port be a tier 2 platform for a while longer. We still have a couple
+ of ABI breaking changes in the pipeline and having to maintain
+ backward compatibility this early in a ports life is less than
+ ideal.
Search the FreeBSD/ia64 PR database:
+ + + ++ This page tries to be the starting point for people trying to find + anything that can be done. The order of the items on this page are + not strictly an indication of priority, but it is a good indication. + There are in all likelihood tasks that are not mentioned here, but + that should be done nonetheless. A typical example is the maintenance + of the ia64 web pages... unfortunately. +
+ ++ With two releases as a tier 2 platform, it is time to work towards + becoming a tier 1 platform. This involves tasks as varied as: +
++ A very important task for the success of FreeBSD on ia64 is making + sure that users have something to run besides ls(1). Our huge ports + collection has been targeting ia32 for the most part, so it is not + surprising that there are a lot of ports that do not build or do not + work on ia64. Look + + here + + for the most up-to-date list of ports that fail to build for some + reason or another. Note that if there are ports depending on one or + more ports that fail, those are not built and are not counted. A good + way to help out here is to work on those ports that have a lot of + ports depending on it (see the "Aff." column in the table). +
+ ++ There are plenty functions (especially assembly routines) that + have been written to provide the missing functionality without any + consideration for speed and/or robustness. Reviewing those functions + and replacing them if necessary is a good task that can be done + concurrently and independently from other activity and does not + necessarily require huge amounts of knowledge and/or experience. +
+ ++ On top of the high-level things that do not work or do not exist, + there is also some rather involved rewriting to be done at the + foundation and can potentially affect all other platforms as well. + This includes: +
+The ideas page has moved to the FreeBSD wiki.
+ + + Copied: projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml (from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.xsl) ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml Mon Jul 16 09:40:38 2012 (r39223, copy of r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.xsl) @@ -0,0 +1,370 @@ + + + + + +]> + + +The FreeBSD Project is looking forward to participating as a mentoring + organization in Google + Summer of Code 2011. + This program funds students to contribute to an open source project over + the summer break. + We have had over 100 successful + students working on FreeBSD as part of this program in 2005, 2006, 2007, 2008, + 2009, + and + 2010.
+ +This page will be updated throughout the GSoC 2011 application period + to include new information, such as project ideas, proposal information, + and potential mentor contact information. If you don't see an idea that + interests you, visit again in a couple of days!
+ +Google Summer of Code is an exciting opportunity for students to + "intern" with an open source project for a summer. The FreeBSD + Project, as one of the most successful and oldest open source projects, + is an excellent place to do this internship. Founded in 1993, the + project now consists of several hundred "committers" and tens of + thousands of contributors. FreeBSD is the foundation for many + commercial products, including Apple's Mac OS X, NetApp's OnTap/GX, + Juniper's JunOS, as well countless other products, and is widely used + in the Internet Service Provider and corporate IT worlds. Many of + these sponsors participate daily in the FreeBSD community, and students + have the opportunity to develop software ideas in an exciting + environment with many real world applications, and under the mentorship + of experienced developers.
+ +After the summer ends, many of our students are sponsored by Google or + the FreeBSD Foundation to attend operating systems and open source + conferences to present on their work, and a significant number go on to + become FreeBSD developers. It's also a great job networking + opportunity!
+ + +For a complete list of student projects from previous years, +visit:
+See also our wiki pages for student projects [2008, +2007, +2006, and +2005].
+ + +The FreeBSD Project maintains an Ideas Page on our + wiki. + Projects specifically tagged as "GSoC" are believed to be sized for a + useful summer hacking, and have technical contacts who can help answer + questions as you write your proposal. + Ideas not marked as GSoC-friendly are also fine to propose, but may be + scoped larger or smaller than a summer, or might not have such a clear + mentor -- we suggest e-mailing our soc-admins alias for help if you do + decide to propose one of them. + You are, of course, welcome to propose your own ideas, and if the + proposal is strong, we'll try to match you with a mentor!
+ +For additional ideas about upcoming development projects in + FreeBSD, take a look at recent Developer Status Reports.
+ + +Students are responsible for writing a proposal and submitting it + to Google before the application deadline. The following outline + was adapted from the Perl Foundation. + The objective of the proposal is to identify + what is to be done, explain why this needs to be done, and convince us + that:
+ +A strong proposal will include (at least):
+ +Name
Phone
IM/IRC
Availability
+ +How many hours per week will you spend working on this? How many on + other things? What other obligations (work, school, vacation, + weddings, etc.) do you have this summer? Be as specific as possible: + when will the project begin and end? You should be ready to produce + a day by day schedule before the program starts.)
+ +Please note: participating in Google Summer of Code + is a significant time commitment, and you should not apply if you + already have another full-time job planned for the summer.
Bio
+ +Who are you? What skills do you bring to this project? What is your + past involvement with The FreeBSD Project? (Past involvement is not + required, but ideally you will have at least installed FreeBSD and + perhaps fixed a bug or two) If your project includes programming in + a particular language, such as C, or in a specific environment, such + as the kernel or an embedded platform, what experience do you have + working in that area? Are you familiar with or a user of revision + control systems? Have you completed courses that will be relevant to + your project idea? What do you think you will need to learn to + complete this project?
Possible Mentor
+ +Optional, but highly recommended. Do not put a name here if you have + not contacted them.
Project Title
+ +In forty characters or less, what you propose to do.
Project Description
+ +A few paragraphs describing your project. Direct copies from the + ideas page will be rejected - proposals should reveal that you have + done some research into the problem and its solutions. Include both + what you will be doing and why it is a good thing for The FreeBSD + Project.
Deliverables
+ +A list quantifiable results and related code milestones. We suggest + at least two milestones before the mid-term evaluations and two + after. Where appropriate, this schedule should include multiple + committable or releasable points so people can benefit from and/or + test your work as early as possible.
Test Plan
+ +What parts of your code need testing and how do you plan to test + them? This might include both functionality and performance tests. +
Project Schedule
+ +How long will the project take? When can you begin work?
A number of FreeBSD committers are willing to mentor students. A + good place to start is the 'Technical contacts' listed with the + example projects on the ideas page.
+ + +In previous years, the FreeBSD Project provided access to the FreeBSD + Perforce revision control infrastructure in order to facilitate + student collaboration, provide public access and archiving for the + on-going student projects, and to help mentors and the community + monitor on-going work. It is expected that students participating + in future programs will be offered the same facilities. Students + will also be asked to maintain wiki pages on their on-going + projects. In the past, e-mail, IRC, and instant messaging have + proven popular among students and mentors, and students + participating in the FreeBSD summer program are encouraged to use + these and other electronic communication mechanisms to become active + in the community.
+ + +When are proposals due, and how do I submit mine? +
+ +At the time of writing, Google has announced the following dates of + interest relating to the application process:
+ +18 March - Google to announce what open source + organizations will participate in Google Summer of Code 2011.
28 March - Student application period opens. +
8 April - Student application period closes. +
22 April - Organizations finish reviewing + applications an mentors registered.
25 April - Accepted students announced.
+Note that these dates may change, and the Google FAQ timeline is the + authoritative source of detailed schedule information:
+ + + +All students must register with, and submit applications via, the + Google Summer of Code home page:
+ +What advice do you have for a student who might want to + submit a proposal?
+ +Experience suggests that the strongest proposals come from students + who contact FreeBSD developers and potential mentors well in advance + of submitting their proposal, seek feedback on their proposal ideas, + and write proposals that reflect time spent exploring and understanding + the problem area to be addressed. Even if the FreeBSD developer(s) you + contact aren't the eventual mentor of the project, their feedback can + be invaluable.
Can I submit multiple project proposals to the FreeBSD + Project?
+ +Yes, but do make sure you invest adequate time in each proposal. We + are not able to accept more than one project per student, so you may do + better spending more time on one or two detailed proposals than by + submitting lots of less-detailed ones.
Will the FreeBSD Project accept more than one student for + the same idea?
+ +In general, we will accept only one student for any given proposal + idea, as most proposal ideas in our ideas list are sized with a single + student summer project in mind. This is a good reason to consider + coming up with your own idea, or at least, making sure that your + proposal for one of our project ideas reflects your unique contribution + and viewpoint. If you plan to submit multiple proposals, you might + consider doing one with an idea from the list, and another with an + original idea.
What if my proposal is not selected in the application + process? Can I still participate?
+ +We always have more good applications than student places, but that + doesn't mean you can't do the project anyway. The FreeBSD Project + always welcomes new volunteers to work on projects, and is generally + happy to provide mentoring and support for students whose proposals + could not be selected in order to allow them to work on their project + anyway. You will need to work with the FreeBSD Project GSoC + administrators to identify a possible mentor. However, Google will not + fund that participation.
What projects were completed successfully by students + in previous summers?
+ +Please see the 2010 FreeBSD + Summer of Code page, as well as older project pages from + 2009, 2008, 2007, 2006, and 2005 for a list of the + completed projects from previous years.
How can I learn more about FreeBSD?
+ +The FreeBSD Project Home Page + is the best way to learn more about the project -- from there you can + reach the FreeBSD Handbook, FreeBSD Developer's Handbook, project + mailing list archives, regular project status reports, and more. If + you have questions about specific project ideas, e-mail the technical + contacts for those ideas. If you have general GSoC questions relating + to FreeBSD, such as if you are unable to reach a project technical + contact, need help finding documentation, or want to know who might be + a good person to talk to about your idea, send them to soc-admins@FreeBSD.org.
+Is there an IRC channel I can join to talk about proposal + ideas or get help finding out more?
+ +You can join #freebsd-soc on the efnet IRC network to chat with + FreeBSD developers interested in mentoring student proposals and + projects, past FreeBSD/GSoC students, and other students applying to + FreeBSD/GSoC this year.
Please help us advertise Google Summer of Code with FreeBSD at your + local university or college campus! You can forward around our e-mail + announcement to department and club mailing lists, and to department + secretaries to distribute. You can also print out and post copies of the + FreeBSD GSoC 2011 poster.
+ + + + +