Imported the Spanish Web pages, except the

english sub directories: cgi, commercial, gallery, gifs
	which are redundant and will never be translated

and the

	spanish sub directories: doc-es, docs-es

Submitted by: "Jesus Rodriguez" <jesusr@ncsa.es>

Fix Makefiles errors. `Make all install' runs fine.

Currently, many the links to the sub directories cgi, commercial,
gallery, gifs are broken. The links should point to the English
orginal files.
This commit is contained in:
Wolfram Schneider 1999-02-08 19:26:12 +00:00
parent 1699e994f5
commit 646ddd7e13
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=4248
160 changed files with 22933 additions and 0 deletions

3
es/Makefile.inc Normal file
View file

@ -0,0 +1,3 @@
# $Id: Makefile.inc,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
WEBBASE?= /data/es

11
es/alpha/Makefile Normal file
View file

@ -0,0 +1,11 @@
# $Id: Makefile,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
DOCS= alpha.sgml
INDEXLINK=alpha.html
.include "../web.mk"

38
es/alpha/alpha.sgml Normal file
View file

@ -0,0 +1,38 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto FreeBSD/Alpha">
<!ENTITY email 'freebsd-alpha'>
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: alpha.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>Esta p&aacute;gina contiene informaci&oacute;n sobre los trabajos de
portar FreeBSD a sistemas Alpha.</p>
<H3>Links espec&iacute;ficos FreeBSD/Alpha</H3>
<UL>
<li><a href="http://www.freebsd.org/~jb/alpha.html">Estado
del port FreeBSD/Alpha</a>.
<li><A href="../handbook/eresources:mail.html">Listas de distribuci&oacute;n FreeBSD/Alpha</a></li>
</UL>
<H3>Otros Links de inter&eacute;s</H3>
<h4>Hardware</h4>
<ul>
<li><A href="http://www.digital.com/alphaserver/">DIGITAL AlphaServer</a><p>
</ul>
<h4>Projectos</h4>
<UL>
<LI><A HREF="http://www.netbsd.org/Ports/alpha/">NetBSD/alpha</A>
<LI><A HREF="http://www.openbsd.org/alpha.html">OpenBSD/alpha</A>
<li><a href="http://www.azstarnet.com/~axplinux/">Linux/Alpha</a>
</UL>
&footer;
</body>
</html>

96
es/applications.sgml Normal file
View file

@ -0,0 +1,96 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Sobre las Aplicaciones para FreeBSD">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: applications.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<HTML>
&header;
<H1>Experimenta las posibilidades con FreeBSD</H1>
<blockquote>
<p>FreeBSD puede manejar cualquier tarea que puedas esperar de una estaci&oacute;n de trabajo UNIX, incluyendo algunas de las que no esperar&iacute;as:</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">FreeBSD
es un verdadero sistema abierto con todo el c&oacute;digo fuente.</FONT></FONT>
<blockquote>
<p>No hay duda que los llamados sistemas abiertos son <i>el</i> requerimiento
para las aplicaciones inform&aacute;ticas de hoy en d&iacute;a. Pero
ning&uacute;n soluci&oacute;n comercial es m&aacute;s abierta que una que
incluya el c&oacute;digo fuente de todo el sistema, incluyendo el kernel
adem&aacute;s de todos los daemons del sistema, programas y utilidades. Puedes
modificar cualquier parte de FreeBSD para acomodarlo a tus necesidades
personales, de organizaci&oacute;n o corporativas.</p>
<p>Con su generosa <A HREF="&base/copyright/license.html"> pol&iacute;tica de
licencias</a>, puedes usar FreeBSD como base para culquier tipo de <i>aplicaci&oacute;n</i> tanto comercial como libre.</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">FreeBSD&nbsp;ejecuta
miles de aplicaciones.</FONT></FONT>
<blockquote>
<p>Por que FreeBSD est&aacute; basado en 4.4BSD, una versi&oacute;n estandard
de UNIX en la industria, es f&aacute;cil compilar y ejecutar programas.
FreeBSD tambi&eacute;n incluye una extensa <A HREF="&base/where.html">
colecci&oacute;n de packages</a> y <A HREF="&base/ports/index.html">
colecci&oacute;n de ports</a> que ofrecen software precompilado y f&aacute;cil
de instalar. Existe tambi&eacute;n un gr&aacute;n n&uacute;mero de
<A HREF="&base/commercial/commercial.html">aplicaciones comerciales</a>
escritas para FreeBSD</p>
<p>Aqu&iacute; tienes algunos ejemplos de los entornos en los que FreeBSD
es usado:</p>
<ul>
<li><b>Servicios Internet.</b> Muchos proveedores de Internet (ISPs) encuentran
en FreeBSD la plataforma ideal para ofrecer servicios WWW, News, FTP, Email y otros. Software "Ready-to-run" como el servidor web <A HREF="http://www.apache.org/">Apache</A> o el servidor FTP Wu-ftpd hacen realmente sencillo poner en
marcha un servidor de servicios Internet. Por supuesto, con la potencia de
<A HREF="&base/internet.html">networking</a> de FreeBSD, tus usuarios
disfrutar&aacute;n de alta velocidad y servicios fiables.</li>
<li><b>Estaci&oacute;n de trabajo X Window. </b>Desde un barato terminal X hasta un avanzado monitor X, FreeBSD responde. <A HREF="http://www.xig.com/">Xi Graphics</A> ofrece software de aceleraci&oacute;n X para hardware gr&aacute;fico de
altas prestaciones (como Matrox), adem&aacute;s de estandares como librer&iacute;as Motif y OpenGL.</li>
<li><b>Networking. </b>Desde filtrado de paquetes hasta rutas o servicios de
resoluci&oacute;n de nombres, FreeBSD puede convertir cualquier PC en un
excelente Firewall de Internet, servidor de correo, servidor de impresi&oacute;n, servidor PC/NFS y mucho m&aacute;s.</li>
<li><b>Desarrollo de software.</b> Cuenta con una suite de herramientas de desarrollo, incluyendo el compilador y debugger de GNU C/C++ y el lenguaje Perl. Los desarrollos en Java y Tcl/Tk tambi&eacute;n son posibles. Editores populares
como Xemacs y lenguajes de programaci&oacute;n m&aacute;s esot&eacute;ricos como Icon tambi&eacute;n est&aacute;n soportados. Y las librer&iacute;as compartidas siempre han sido f&aacute;ciles de hacer y usar.</li>
<li><b>Navegaci&oacute;n por la red.</b> Una verdadera estaci&oacute;n de trabajo UNIX es una gr&aacute;n "embarcaci&oacute;n" para la red, y la versi&oacute;n BSD de <A HREF="http://home.netscape.com/comprod/products/communicator/index.html">Netscape Navigator</a> com soporte de Java funciona en FreeBSD. Navega, publica tus propias p&aacute;ginas, lee las News y env&iacute;a y recibe correo con un sistema FreeBSD en tu m&acute;quina.</li>
<li><b>Educaci&oacute;n e investigaci&oacute;n</b>. &nbsp;FreeBSD es una excelente plataforma de investigaci&oacute;n por que incluye el c&oacute;digo fuente
completo. Estudiantes e investigadores de sistemas operativos pueden beneficiarse enormemente de este sistema abierto y bi&eacute;n documentado.</li>
<li><b>Y mucho m&aacute;s.</b> Accounting, juegos de acci&oacute;n, bases de datos, visualizaci&oacute;n cient&iacute;fica, v&iacute;deo conferencia, Internet Relay Chat (IRC), automatizaci&oacute;n del hogar, bbs's, escaneo de im&aacute;genes y m&aacute;s son todos usos reales de FreeBSD hoy. Si tienes alguna aplicaci&oacute;n innovadora para FreeBSD, <A HREF="http://www.freebsd.org/cgi/gallery.cgi"> haznoslo saber</a> para que podamos a&ntilde;dirla a nuestra <A HREF="&base/../gallery/gallery.html">galer&iacute;a</a>.</li>
</UL>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">Un
sistema operativo que colmar&aacute; todas tus necesidades.</FONT></FONT>
<blockquote>
<p>Aunque FreeBSD es un software libre, es un software <i>soportado por usuarios</i>. Cualquier pregunta que tengas puede ser enviada a cientos de desarrolladores de FreeBSD y usuarios a la lista de distribuci&oacute;n <A HREF="mailto:freebsd-questions@FreeBSD.ORG">freebsd-questions@FreeBSD.ORG</A>.</p>
<p>FreeBSD tiene un completo grupo a nivel mundial de programadores y desarrolladores que se encargan de fijar los posibles bugs, a&ntilde;adir nuevas caracter&iacute;sticas y documentar el sistema. Soporte de nuevos dispositivos y opciones especiales se incluyen en el proceso de desarrollo constante, manteniendo una atenci&oacute;n especial a los problemas que afectan a la estabilidad del sistema.</p>
</blockquote>
<H2>Lo que dicen los expertos. . .</H2>
<blockquote>
<P><I>``FreeBSD handles [our] heavy load quite well and it is nothing short
of amazing. Salutations to the FreeBSD team.''</I></P>
<DIV ALIGN=right><P>---Mark Hittinger, administrator of WinNet Communications,
Inc.</P></DIV>
</blockquote>
&footer;
</BODY>
</HTML>

413
es/auditors.sgml Normal file
View file

@ -0,0 +1,413 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto de auditor&iacute;a de fuentes de FreeBSD">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: auditors.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<HTML>
&header;
<H1>Informaci&oacute;n general</H1>
<em>Ultima actualizaci&oacute;n: $Date: 1999-02-08 19:26:11 $ </em>
<H2>Introducci&oacute;n</H2>
<p>A causa de nuestro reciente problema de seguridad, ha sido obvio que nada
mejor que una rigurosa revisi&oacute;n de seguridad en todo el c&oacute;digo
fuente del sistema.</p>
<p>La ingente cantidad de c&oacute;digo de fuentes externas en FreeBSD hace
especialmente sencillo que algunos problemas de seguridad puedan pasar
desapercibidos hasta que sea demasiado tarde, y hasta estos momentos no se ha
realizado ning&uacute;n esfuerzo verdaderamente importante de revisi&oacute;n
de todo el c&oacute;digo del sistema centrado en la seguridad. Esta
situaci&oacute;n debe cambiar ahora, ya que si esperamos ser el sistema
operativo en el que la gente pueda confiar mientras Internet sigue creciendo y
(sospecho) volviendose m&aacute; hostil para sistemas mal protegidos. Una
buena seguridad es algo a realizar y compartir entre el administrador local y
los desarrolladores del sistema, y &eacute;stos tienen *ahora* que hacer su
parte.</p>
<p>El primer paso del core team respecto al tema de la seguridad fue crear un
puesto de responsable de seguridad, <a href="mailto:guido@FreeBSD.org">
Guido van Rooij</a>, para que una de las "voces de la mesa" tuviese la seguridad como su principal responsabilidad y representar a FreeBSD en las listas
externas m&aacute;s importantes relacionadas con la seguridad. Adem&aacute;s
&eacute;l nos mantendr&aacute; m&aacute;s informados sobre los temas de
seguridad para que no nos vuelva a coger desprevenidos como ocurri&oacute;
alguna vez en el pasado.</p>
<p>Nuestro segundo paso es esta auditor&iacute;a, un intento de ir
metodicamente a trav&eacute;s de cada una de las l&iacute;neas de c&oacute;digo
de FreeBSD prestando especial atenci&oacute;n a buffer overflows obvios
(sprintf()/strcpy() vs snprintf()/strncpy() ), problemas de seguridad menos
obvios, secciones de insuficiente c&oacute;digo defensivo, etc.</p>
<p>Usando la
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-CVS/CVSROOT/modules">
base de datos de m&oacute;dulos</a> como gu&iacute;, distribuiremos los
fuentes en partes m&aacute; manejables, manteniendo un &iacute;dice en un
lugar prominente para que la gente pueda ver los m&oacute;dulos que se han
cubierto y los que no. Un equipo cuidadosamente seleccionado ha sido formado,
siendo "auditotes" y "revisores". La principal responsabilidad de un auditor,
la cual debe ser compartida con otro auditor, es revisar el c&oacute;digo en
busca de posibles agujeros o bugs. Una vez existe una razonable cantidad de
c&oacute;digo acumulado, y suponiendo que no se haya encontrado ning&uacute;n
problema, &eacute;stos son enviados a uno o m&aacute; "revisores" que se
responsabilizan de volver a revisar el c&oacute;digo una vez m&aacute;s.</p>
<H2>Requerimientos:</H2>
<p>Para ser auditor, deber&iacute;s tener privilegios de "commit" en
<em>freefall.freebsd.org</em> o un acuerdo con otro auditor/revisor que los
tenga. Tambi&eacute;n deber&iacute;as usar, o tener acceso inmediato a
<a href="handbook/current.html">FreeBSD-current</a> ya que todas las revisiones
y cambios se realizar&aacute;s sobre esta rama en primer lugar.
<p>Qu&eacute; buscar y que reglas generales a seguir son suficientemente
complejas como para explicarlas en <a href="security/security.html">La
Gu&iacute;a de Seguridad de FreeBSD</a>. Por favor, leela ahora si no lo
hab&iacute;as hecho todav&iacute;a.
Otros excelentes documentos son <a
href="ftp://ftp.auscert.org.au/pub/auscert/papers/secure_programming_checklist">Secure Programming Checklist</a> y el <a
href="ftp://ftp.auscert.org.au/pub/auscert/papers/unix_security_checklist">
Unix Security Checklist</a>, ambos disponibles en AUSCERT.
<H2>Estructura:</H2>
<p>Aqu&iacute; est&aacute; la estructura existente en estos momentos. Es *muy*
esquem&aacute;tica actualmente, ya que acabamos de comenzar, y ha medida que
la gente nos comunique los m&oacute;dulos que van a revisar o auditar iremos
actualizandolo.</p>
<p>Nada en la base de datos de m&oacute;dulos representa un objetivo potencial
de auditor&iacute;a - desde los mas peque&ntilde;os como "cat" hasta los
m&aacute;s grandes como "lib", lo m&aacute;s importante es que la gente
selecciones m&oacute;dulos que pueda manejar y asumir. Si coges 15 cosas y
solo trabajas con 5, no estar&aacute;s haciendo un favor a nadie ya que el
resto de auditores que las 10 restantes est&aacute;n siendo trabajadas!.</p>
Para escoger algo, por favor, un mai a <a
href="mailto:jmb@FreeBSD.org"> jmb@FreeBSD.org</a>.
<P></P><TABLE BORDER="2" CELLPADDING="3">
<TR><TH>M&oacute;dulo</TH><TH>Auditor(s)</TH><TH>Revisor(s)</TH>
<TH>Status</TH></TR>
<TR><TD><A HREF="mailto:audit-bin@FreeBSD.ORG">bin</A></TD>
<TD>
<A HREF="mailto:adrian@psinet.net.au">ac</A>
<A HREF="mailto:eivind@FreeBSD.org">ee*</A>
<A HREF="mailto:guido@FreeBSD.org">gvr*</A>
<A HREF="mailto:jehamby@lightside.com">jh</A>
<A HREF="mailto:top@bird.cris.net">ka</A>
<A HREF="mailto:mudge@l0pht.com">mu</A>
<A HREF="mailto:vadim@tversu.ac.ru">vk</A>
</TD>
<TD><A HREF="mailto:imp@FreeBSD.org">imp*</A> <A HREF="mailto:jmb@FreeBSD.org">jmb*</A> <A HREF="mailto:dillon@best.net">md*</A> <A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-contrib@FreeBSD.ORG">contrib</A></TD>
<TD>
<A HREF="mailto:gryphon@healer.com">cg</A>
</TD>
<TD><A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-eBones@FreeBSD.ORG">eBones</A></TD>
<TD>
<A HREF="mailto:mark@grondar.za">mrvm*</A>
</TD>
<TD><A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-games@FreeBSD.ORG">games</A></TD>
<TD>
<A HREF="mailto:aaronb@j51.com">ab</A>
<A HREF="mailto:eivind@FreeBSD.org">ee*</A>
<A HREF="mailto:xaa@stack.nl">xaa</A>
</TD>
<TD><A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-init@FreeBSD.ORG">init</A></TD>
<TD>
<A HREF="mailto:giles@nemeton.com.au">gl</A>
</TD>
<TD><A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-lib@FreeBSD.ORG">lib</A></TD>
<TD>
<A HREF="mailto:apk@itl.waw.pl">ak</A>
<A HREF="mailto:nordquist@platinum.com">bjn</A>
<A HREF="mailto:pst@FreeBSD.org">pst*</A>
</TD>
<TD><A HREF="mailto:davidg@FreeBSD.org">dg*</A> <A HREF="mailto:imp@FreeBSD.org">imp*</A> <A HREF="mailto:jkh@FreeBSD.org">jkh*</A> <A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-libc@FreeBSD.ORG">libc</A></TD>
<TD>
<A HREF="mailto:eivind@FreeBSD.org">ee*</A>
<A HREF="mailto:mudge@l0pht.com">mu</A>
</TD>
<TD><A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-libexec@FreeBSD.ORG">libexec</A></TD>
<TD>
<A HREF="mailto:henrich@crh.cl.msu.edu">crh</A>
<A HREF="mailto:eivind@FreeBSD.org">ee*</A>
<A HREF="mailto:imp@FreeBSD.org">imp*</A>
<A HREF="mailto:msr@cuc.com">mr</A>
<A HREF="mailto:witr@rwwa.com">witr</A>
</TD>
<TD><A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-lkm@FreeBSD.ORG">lkm</A></TD>
<TD>
<A HREF="mailto:obrien@NUXI.com">dob*</A>
</TD>
<TD><A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-sbin@FreeBSD.ORG">sbin</A></TD>
<TD>
<A HREF="mailto:eivind@FreeBSD.org">ee*</A>
<A HREF="mailto:imp@FreeBSD.org">imp*</A>
<A HREF="mailto:roberto@keltia.freenix.fr">or*</A>
<A HREF="mailto:taob@risc.org">tao</A>
</TD>
<TD><A HREF="mailto:jmb@FreeBSD.org">jmb*</A> <A HREF="mailto:dillon@best.net">md*</A> <A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-secure@FreeBSD.ORG">secure</A></TD>
<TD>
<A HREF="mailto:tenser@spitfire.ecsel.psu.edu">dc</A>
<A HREF="mailto:mark@grondar.za">mrvm*</A>
</TD>
<TD><A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-telnetd@FreeBSD.ORG">telnetd</A></TD>
<TD>
<A HREF="mailto:adrian@psinet.net.au">ac</A>
<A HREF="mailto:davidn@labs.usn.blaze.net.au">dn</A>
</TD>
<TD><A HREF="mailto:imp@FreeBSD.org">imp*</A> <A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-usr.bin@FreeBSD.ORG">usr.bin</A></TD>
<TD>
<A HREF="mailto:bob@luke.pmr.com">bob</A>
<A HREF="mailto:eivind@FreeBSD.org">ee*</A>
<A HREF="mailto:jha@cs.purdue.edu">jha</A>
<A HREF="mailto:mollers.pad@sni.de">jm</A>
<A HREF="mailto:yokota@zodiac.mech.utsunomiya-u.ac.jp">ky*</A>
<A HREF="mailto:rbezuide@oskar.nanoteq.co.za">rb</A>
<A HREF="mailto:rajivd@sprynet.com">rd</A>
<A HREF="mailto:rjk@grauel.com">rjk</A>
<A HREF="mailto:vadim@tversu.ac.ru">vk</A>
</TD>
<TD><A HREF="mailto:dillon@best.net">md*</A> <A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
<TR><TD><A HREF="mailto:audit-usr.sbin@FreeBSD.ORG">usr.sbin</A></TD>
<TD>
<A HREF="mailto:eivind@FreeBSD.org">ee*</A>
<A HREF="mailto:ejc@gargoyle.bazzle.com">ejc</A>
<A HREF="mailto:giles@nemeton.com.au">gl</A>
<A HREF="mailto:imp@FreeBSD.org">imp*</A>
<A HREF="mailto:mollers.pad@sni.de">jm</A>
<A HREF="mailto:marcs@znep.com">marc</A>
<A HREF="mailto:rajivd@sprynet.com">rd</A>
</TD>
<TD><A HREF="mailto:dillon@best.net">md*</A> <A HREF="mailto: guido@FreeBSD.org">gvr*</A> </TD>
<TD>Open</TD>
</TABLE>
<H2>Menci&oacute;n de Auditores/Revisores</H2>
<p>Esta es la lista de personas que voluntariamente han participado como
auditores o revisores en este proceso. Pueden ser localizados colectivamente
enviando un mail a <a href="mailto:auditors@FreeBSD.org">
auditors@FreeBSD.org</a>. Si solo quieres localizar a los auditores y revisores
de una categor&iacute;a espec&iacute;fica, digamos <strong>usr.sbin</strong>
por ejemplo, env&iacute;a un mail a
<a href="mailto:audit-usr.sbin@FreeBSD.org">
audit-<strong>usr.sbin</strong>@FreeBSD.org</a>.</P>
<TABLE CELLPADDING="2"><TR><TH>Key</TH>
<TH>Auditor/Revisor Nombre y Email</TH></TR>
<TR><td>ab</TD>
<TD>Aaron Bornstein <A HREF="mailto:aaronb@j51.com">
aaronb@j51.com</A></TD></TR>
<TR><td>ac</TD>
<TD>Adrian Chadd <A HREF="mailto:adrian@psinet.net.au">
adrian@psinet.net.au</A></TD></TR>
<TR><td>ak</TD>
<TD>Adam Kubicki <A HREF="mailto:apk@itl.waw.pl">
apk@itl.waw.pl</A></TD></TR>
<TR><td>am</TD>
<TD>Albert Mietus <A HREF="mailto:gam@gamp.hacom.nl">
gam@gamp.hacom.nl</A></TD></TR>
<TR><td>avk</TD>
<TD>Alexander V. Kalganov <A HREF="mailto:top@sonic.cris.net">
top@sonic.cris.net</A></TD></TR>
<TR><td>bb</TD>
<TD>Bob Bishop <A HREF="mailto:rb@gid.co.uk">
rb@gid.co.uk</A></TD></TR>
<TR><td>bjn</TD>
<TD>Brent J. Nordquist <A HREF="mailto:nordquist@platinum.com">
nordquist@platinum.com</A></TD></TR>
<TR><td>bob</TD>
<TD>Bob Willcox <A HREF="mailto:bob@luke.pmr.com">
bob@luke.pmr.com</A></TD></TR>
<TR><td>btm</TD>
<TD>Brian T. Michely <A HREF="mailto:brianm@cmhcsys.com">
brianm@cmhcsys.com</A></TD></TR>
<TR><td>cg</TD>
<TD>Coranth Gryphon <A HREF="mailto:gryphon@healer.com">
gryphon@healer.com</A></TD></TR>
<TR><td>cl</TD>
<TD>Chris Lambertus <A HREF="mailto:cmlambertus@ucdavis.edu">
cmlambertus@ucdavis.edu</A></TD></TR>
<TR><td>crh</TD>
<TD>Charles Henrich <A HREF="mailto:henrich@crh.cl.msu.edu">
henrich@crh.cl.msu.edu</A></TD></TR>
<TR><td>dc</TD>
<TD>Dan Cross <A HREF="mailto:tenser@spitfire.ecsel.psu.edu">
tenser@spitfire.ecsel.psu.edu</A></TD></TR>
<TR><td>dg*</TD>
<TD>David Greenman <A HREF="mailto:dg@FreeBSD.org">
davidg@FreeBSD.org</A></TD></TR>
<TR><td>din</TD>
<TD>Dinesh Nair <A HREF="mailto:dinesh@alphaque.com">
dinesh@alphaque.com</A></TD></TR>
<TR><td>dn</TD>
<TD>David Nugent <A HREF="mailto:davidn@labs.usn.blaze.net.au">
davidn@labs.usn.blaze.net.au</A></TD></TR>
<TR><td>dob*</TD>
<TD>David E. O'Brien <A HREF="mailto:obrien@NUXI.com">
obrien@NUXI.com</A></TD></TR>
<TR><td>dz</TD>
<TD>Danny J. Zerkel <A HREF="mailto:dzerkel@phofarm.com">
dzerkel@phofarm.com</A></TD></TR>
<TR><td>ee*</TD>
<TD>Eivind Eklund <A HREF="mailto:eivind@FreeBSD.org">
eivind@FreeBSD.org</A></TD></TR>
<TR><td>eh</TD>
<TD>Elijah Hempstone <A HREF="mailto:avatar@gandalf.bss.sol.net">
avatar@gandalf.bss.sol.net</A></TD></TR>
<TR><td>ehu</TD>
<TD>Ernest Hua <A HREF="mailto:hua@chromatic.com">
hua@chromatic.com</A></TD></TR>
<TR><td>ejc</TD>
<TD>Eric J. Chet <A HREF="mailto:ejc@gargoyle.bazzle.com">
ejc@gargoyle.bazzle.com</A></TD></TR>
<TR><td>gl</TD>
<TD>Giles Lean <A HREF="mailto:giles@nemeton.com.au">
giles@nemeton.com.au</A></TD></TR>
<TR><td>gvr*</TD>
<TD>Guido van Rooij <A HREF="mailto:guido@FreeBSD.org">
guido@FreeBSD.org</A></TD></TR>
<TR><td>gw</TD>
<TD>Graham Wheeler <A HREF="mailto:gram@oms.co.za">
gram@oms.co.za</A></TD></TR>
<TR><td>imp*</TD>
<TD>Warner Losh <A HREF="mailto:imp@FreeBSD.org">
imp@FreeBSD.org</A></TD></TR>
<TR><td>jb</TD>
<TD>Jim Bresler <A HREF="mailto:jfb11@inlink.com">
jfb11@inlink.com</A></TD></TR>
<TR><td>jh</TD>
<TD>Jake Hamby <A HREF="mailto:jehamby@lightside.com">
jehamby@lightside.com</A></TD></TR>
<TR><td>jha</TD>
<TD>John H. Aughey <A HREF="mailto:jha@cs.purdue.edu">
jha@cs.purdue.edu</A></TD></TR>
<TR><td>jk</TD>
<TD>Jerry Kendall <A HREF="mailto:Jerry@kcis.com">
Jerry@kcis.com</A></TD></TR>
<TR><td>jkh*</TD>
<TD>Jordan K. Hubbard <A HREF="mailto:jkh@FreeBSD.org">
jkh@FreeBSD.org</A></TD></TR>
<TR><td>jm</TD>
<TD>Josef Moellers <A HREF="mailto:mollers.pad@sni.de">
mollers.pad@sni.de</A></TD></TR>
<TR><td>jmb*</TD>
<TD>Jonathan M. Bresler <A HREF="mailto:jmb@FreeBSD.org">
jmb@FreeBSD.org</A></TD></TR>
<TR><td>joe*</TD>
<TD>Joe Greco <A HREF="mailto:jgreco@solaria.sol.net">
jgreco@solaria.sol.net</A></TD></TR>
<TR><td>ka</TD>
<TD>Kalganov Alexander <A HREF="mailto:top@bird.cris.net">
top@bird.cris.net</A></TD></TR>
<TR><td>ki</TD>
<TD>Kenneth Ingham <A HREF="mailto:ingham@i-pi.com">
ingham@i-pi.com</A></TD></TR>
<TR><td>ky*</TD>
<TD>Kazutaka YOKOTA <A HREF="mailto:yokota@zodiac.mech.utsunomiya-u.ac.jp">
yokota@zodiac.mech.utsunomiya-u.ac.jp</A></TD></TR>
<TR><td>marc</TD>
<TD>Marc Slemko <A HREF="mailto:marcs@znep.com">
marcs@znep.com</A></TD></TR>
<TR><td>md*</TD>
<TD>Matt Dillon <A HREF="mailto:dillon@best.net">
dillon@best.net</A></TD></TR>
<TR><td>mr</TD>
<TD>Mike Romaniw <A HREF="mailto:msr@cuc.com">
msr@cuc.com</A></TD></TR>
<TR><td>mrvm*</TD>
<TD>Mark Murray <A HREF="mailto:mark@grondar.za">
mark@grondar.za</A></TD></TR>
<TR><td>mu</TD>
<TD>Mudge <A HREF="mailto:mudge@l0pht.com">
mudge@l0pht.com</A></TD></TR>
<TR><td>or*</TD>
<TD>Ollivier Robert <A HREF="mailto:roberto@keltia.freenix.fr">
roberto@keltia.freenix.fr</A></TD></TR>
<TR><td>pb</TD>
<TD>Peter Blake <A HREF="mailto:ppb@baloo.tcp.co.uk">
ppb@baloo.tcp.co.uk</A></TD></TR>
<TR><td>peter*</TD>
<TD>Peter Wemm <A HREF="mailto:peter@FreeBSD.org">
peter@FreeBSD.org</A></TD></TR>
<TR><td>phk*</TD>
<TD>Poul-Henning Kamp <A HREF="mailto:phk@FreeBSD.org">
phk@FreeBSD.org</A></TD></TR>
<TR><td>pst*</TD>
<TD>Paul Traina <A HREF="mailto:pst@FreeBSD.org">
pst@FreeBSD.org</A></TD></TR>
<TR><td>rb</TD>
<TD>Reinier Bezuidenhout <A HREF="mailto:rbezuide@oskar.nanoteq.co.za">
rbezuide@oskar.nanoteq.co.za</A></TD></TR>
<TR><td>rd</TD>
<TD>Rajiv Dighe <A HREF="mailto:rajivd@sprynet.com">
rajivd@sprynet.com</A></TD></TR>
<TR><td>rel</TD>
<TD>Roger Espel Llima <A HREF="mailto:espel@llaic.univ-bpclermont.fr">
espel@llaic.univ-bpclermont.fr</A></TD></TR>
<TR><td>rjk</TD>
<TD>Richard J Kuhns <A HREF="mailto:rjk@grauel.com">
rjk@grauel.com</A></TD></TR>
<TR><td>rm</TD>
<TD>Robin Melville <A HREF="mailto:robmel@nadt.org.uk">
robmel@nadt.org.uk</A></TD></TR>
<TR><td>rs</TD>
<TD>Robert Sexton <A HREF="mailto:robert@kudra.com">
robert@kudra.com</A></TD></TR>
<TR><td>sc</TD>
<TD>Sergei Chechetkin <A HREF="mailto:csl@whale.sunbay.crimea.ua">
csl@whale.sunbay.crimea.ua</A></TD></TR>
<TR><td>tao</TD>
<TD>Brian Tao <A HREF="mailto:taob@risc.org">
taob@risc.org</A></TD></TR>
<TR><td>tdr</TD>
<TD>Thomas David Rivers <A HREF="mailto:ponds!rivers@dg-rtp.dg.com">
ponds!rivers@dg-rtp.dg.com</A></TD></TR>
<TR><td>vk</TD>
<TD>Vadim Kolontsov <A HREF="mailto:vadim@tversu.ac.ru">
vadim@tversu.ac.ru</A></TD></TR>
<TR><td>witr</TD>
<TD>Robert Withrow <A HREF="mailto:witr@rwwa.com">
witr@rwwa.com</A></TD></TR>
<TR><td>xaa</TD>
<TD>Mark Huizer <A HREF="mailto:xaa@stack.nl">
xaa@stack.nl</A></TD></TR>
</TABLE>
<H3>* = Tiene privilegios de "commit".</H3>
&footer;
</BODY>
</HTML>

91
es/availability.sgml Normal file
View file

@ -0,0 +1,91 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Sobre la disponibilidad de FreeBSD">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: availability.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<HTML>
&header;
<H1>Disponibilidad de FreeBSD</H1>
<blockquote>
<p>FreeBSD es libre y est&aacute; disponible para bajar a trav&eacute;s de Internet o
en CD-ROM por un precio m&iacute;nimo.</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">Requerimientos de Hardware.</FONT></FONT>
<blockquote>
<p>FreeBSD requiere de un ordenador personal PC con procesador Intel, AMD,
Cyrix o compatible 386, 486 o Pentium. Necesita un bus ISA, EISA, VESA o PCI.
Necesitar&aacute;s al menos 5MB de RAM para hacer la instalaci&oacute;n (pero
4MB de RAM para ejecutar el sistema una vez instalado). Para un mejor
rendimiento es aconsejable 8MB o m&aacute;s. Se requieren al menos 60MB de
disco duro para realizar la instalaci&oacute;n m&iacute;nima.</p>
<p>FreeBSD soporta las tarjetas de red m&aacute;s populares, controladoras
SCSI, disco duros IDE, tarjetas serie multipuerto, lectores de CD-ROM, cintas
y dat's, tarjetas de sonido y otro hardware diferente. Consulta las
<A HREF="&base/FAQ/FAQ.html">FAQ</a> y las &uacute;ltimas notas de la
&a.latest.not;release</a> para obtener el listado completo del hardware
soportado.</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">D&oacute;nde obtenerlo.</FONT></FONT>
<blockquote>
<p>Puedes obtener FreeBSD v&iacute;a FTP an&oacute;nimo en
<A HREF="ftp://ftp.freebsd.org/pub/FreeBSD">
ftp://ftp.freebsd.org/pub/FreeBSD</A>.
Tambi&eacute;n puedes obtenerlo de cualquiera de los
<A HREF="&base/handbook/mirrors.html">mirrors</a> existentes en
todo el mundo.</p>
<p>Si tienes un lector de CD-ROM, puedes obtener FreeBSD en CD-ROM por un
muy m&oacute;dico precio en <A HREF="http://www.cdrom.com/">Walnut Creek CDROM</A>:</p>
<blockquote>
<P>Walnut Creek CDROM<BR>
4041 Pike Lane, Suite F<br>
Concord, CA 94520<br>
USA<br>
Phone: +1 925 674-0783<BR>
Phone: +1 800 786-9907<br>
Fax: +1 925 674-0821<BR>
Email: <A HREF="mailto:info@cdrom.com">info@cdrom.com</A></P>
</blockquote>
<p>Adem&aacute;s de FreeBSD, la versi&oacute;n en CD-ROM incluye cientos
de aplicaciones listas para funcionar.</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">Sobre
el Proyecto FreeBSD.</FONT></FONT>
<blockquote>
<p>FreeBSD es desarrollado y soportado por un grupo mundial de programadores.
<A HREF="mailto:jkh@FreeBSD.ORG">Jordan Hubbard,</A> uno de los fundadores
del proyecto a escrito una <A HREF="&base/handbook/history.html">breve
historia</a> del proyecto FreeBSD. Informaci&oacute;n sobre
<A HREF="&base/handbook/staff:who.html">qui&eacute;n</a> es responsable de cada
cosa tambi&eacute;n est&aacute; disponible. Si eres curioso, mira algunas
<A HREF="http://www.freebsd.org/~jhs/freebsd/people.html">fotos</a> de los
componentes del equipo. Una lista m&aacute;s completa de los participantes
est&aacute; disponible en la secci&oacute;n
<A HREF="&base/handbook/contrib.html">Participantes</a> del
<A HREF="&base/handbook/handbook.html">Handbook</a> de FreeBSD. FreeBSD es un
proyecto abierto que aprecia la ayuda de personas que tengan tiempo o ideas
que ofrecer.</p>
<P>Esta secci&oacute;n fue creada por <A HREF="http://www-sdd.fsl.noaa.gov/~kelly/">Sean
Kelly</A>.</P>
</blockquote>
<P center><I><FONT COLOR="#B22222"><FONT SIZE="+1">Dentro de tu PC hay un
demonio esperando a ser liberado. L&iacute;beralo con FreeBSD.</FONT></FONT></I></P>
&footer;
</BODY>
</HTML>

339
es/copyright/COPYING Normal file
View file

@ -0,0 +1,339 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.

481
es/copyright/COPYING.LIB Normal file
View file

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

22
es/copyright/Makefile Normal file
View file

@ -0,0 +1,22 @@
# $Id: Makefile,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
DOCS= license.sgml
DOCS+= freebsd-license.sgml
DOCS+= daemon.sgml
DOCS+= copyright.sgml
INDEXLINK= copyright.html
DATA+= COPYING COPYING.LIB ${LEGAL}
# FreeBSD Ports redistribution restrictions
#LEGAL= LEGAL
#CLEANFILES+= ${LEGAL}
#${LEGAL}: $${CVSROOT}/ports/LEGAL,v
# co -q -p ${.ALLSRC} > ${.TARGET}
.include "../web.mk"

View file

@ -0,0 +1,24 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Informaci&oacute;n del Copyright de FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: copyright.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p></p>
<h2><a href="freebsd-license.html">El Copyright FreeBSD</a></h2>
<h2><a href="license.html">El Copyright BSD</a></h2>
<h2><a href="daemon.html">El demonio BSD</a></h2>
<h2><a href="LEGAL">Restricciones de redistribuci&oacute;n de los ports de FreeBSD</a></h2>
<h2><a href="COPYING">LICENCIA PUBLICA GENERAL DE GNU</a></h2>
<h2><a href="COPYING.LIB">LICENCIA PUBLICA GENERAL DE LIBRERIA GNU</a></h2>
<p>
&footer;
</body>
</html>

65
es/copyright/daemon.sgml Normal file
View file

@ -0,0 +1,65 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "El demonio BSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: daemon.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>El peque&ntilde;o compa&ntilde;ero rojo que alegra algunas de las
p&aacute;ginas de este web es el demonio BSD. En el contexto de los
sistemas Unix, demonios son procesos que trabajan en segundo plano
atendiendo a varias tareas sin intervenci&oacute;n humana. En un
sentido general, daemon es la forma antigua de la palabra "demon". En
el <em>Manual de Administraci&oacute;n de Sistemas Unix</em>, Evi
Nemeth dice lo siguiente sobre los "daemons":</p>
<blockquote>"Many people equate the word ``daemon'' with the
word ``demon,'' implying some kind of Satanic connection
between UNIX and the underworld. This is an egregious
misunderstanding. ``Daemon'' is actually a much older form
of ``demon''; daemons have no particular bias towards good
or evil, but rather serve to help define a person's
character or personality. The ancient Greeks' concept of a
``personal daemon'' was similar to the modern concept of a
``guardian angel'' --- ``eudaemonia'' is the state of being
helped or protected by a kindly spirit. As a rule, UNIX
systems seem to be infested with both daemons and demons."
(p403)
</blockquote>
<p>Las primeras (y m&aacute;s populares) versiones del demonio BSD
fueron creadas por John Lassiter. Las versiones m&aacute;s recientes
espec&iacute;ficas de FreeBSD han sido realizadas por
<a href="http://www.mt.cs.keio.ac.jp/person/hosokawa.html">
Tatsumi Hosokawa</a>, pero la inspiraci&oacute;n b&aacute;sica,
definitivamente pertenece a John.
El propietario del copyright y creador de la im&aacute;gen del demonio
es <a href="mailto:mckusick@mckusick.com">Marshall Kirk McKusick</a>.
Una breve <a href="http://www.mckusick.com/beastie/index.html">
historia gr&aacute;fica</a> tambi&eacute;n est&aacute; disponible.
Existe una galer&iacute;a de <A HREF="../publish.html">publicaciones</a>
relacionadas con FreeBSD que usan diferentes versiones del demonio.</p>
<p>BSD Daemon Copyright 1988 by Marshall Kirk McKusick. All
Rights Reserved.</p>
<p>El permiso para usar el demonio debe ser obtenido de:</p>
<blockquote>Marshall Kirk McKusick<br> 1614 Oxford St<br>
Berkeley, CA 94709-1608<br> USA</blockquote>
<p>o v&iacute;a email a <a
href="mailto:mckusick@mckusick.com">mckusick@mckusick.com</a>.
</p>
<p></p><A HREF="copyright.html">Copyright Home</a>
&footer;
</body>
</html>

View file

@ -0,0 +1,55 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "El Copyright FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: freebsd-license.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>Copyright 1994-1998
FreeBSD, Inc.
All rights reserved.
<p>La redistribuci&oacute;n y uso en forma de c&oacute;digo fuente o
binario, con o s&iacute;n modicaciones, est&aacute;n permitidas
siempre y cuando sean conocidas las siguientes condiciones:
<ol>
<li>La redistribuci&oacute;n del c&oacute;digo fuente debe contener
el texto arriba indicado, esta lista de condiciones y el
siguiente texto.
<li>La redistribuci&oacute;n en formato binario debe contener el
texto arriba indicado. esta lista de codiciones y el siguiente
texto en la documentaci&oacute;n y/o en otros materiales que
acompa&ntilde;en a la distribuci&oacute;n.
</ol>
<p>THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
<p>The views and conclusions contained in the software and
documentation are those of the authors and should not be
interpreted as representing official policies, either
expressed or implied, of the FreeBSD Project or FreeBSD, Inc.
<p></p><A HREF="copyright.html">Copyright Home</a>
&footer;
</body>
</html>

103
es/copyright/license.sgml Normal file
View file

@ -0,0 +1,103 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "El Copyright 4.4BSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: license.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>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.
<p>Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,
1993, 1994 The Regents of the University of California.
All rights reserved.
<p>Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the
following conditions are met:
<ol>
<li>Redistributions of source code must retain the above
copyright notice, this list of conditions and the
following disclaimer.
<li>Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other
materials provided with the distribution.
<li>All advertising materials mentioning features or use
of this software must display the following
acknowledgement:
<blockquote>This product includes software developed by
the University of California, Berkeley and its
contributors.</blockquote>
<li>Neither the name of the University nor the names of its
contributors may be used to endorse or promote products
derived from this software without specific prior written
permission.
</li>
</ol>
<p>THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
<p>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.
<p>In the following statement, the phrase ``this text''
refers to portions of the system documentation.
<p>Portions of this text are reprinted and reproduced in
electronic form in the second BSD Networking Software
Release, from IEEE Std 1003.1-1988, IEEE Standard Portable
Operating System Interface for Computer Environments
(POSIX), copyright C 1988 by the Institute of Electrical
and Electronics Engineers, Inc. In the event of any
discrepancy between these versions and the original IEEE
Standard, the original IEEE Standard is the referee
document.
<p>In the following statement, the phrase ``This material''
refers to portions of the system documentation.
<p>This material is reproduced with permission from American
National Standards Committee X3, on Information Processing
Systems. Computer and Business Equipment Manufacturers
Association (CBEMA), 311 First St., NW, Suite 500,
Washington, DC 20001-2178. The developmental work of
Programming Language C was completed by the X3J11 Technical
Committee.
<p>The views and conclusions contained in the software and
documentation are those of the authors and should not be
interpreted as representing official policies, either
expressed or implied, of the Regents of the University of
California.
<p></p><A HREF="copyright.html">Copyright Home</a>
&footer;
</body>
</html>

17
es/docproj/Makefile Normal file
View file

@ -0,0 +1,17 @@
# $Id: Makefile,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
DOCS= current.sgml
DOCS+= doc-set.sgml
DOCS+= sgml.sgml
DOCS+= submitting.sgml
DOCS+= who.sgml
DOCS+= translations.sgml
DOCS+= docproj.sgml
INDEXLINK= docproj.html
.include "../web.mk"

213
es/docproj/current.sgml Normal file
View file

@ -0,0 +1,213 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto de Documentaci&oacute;n de FreeBSD: Proyectos Actuales">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: current.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>Aqu&iacute; est&aacute;n los proyectos en curso (o siendo activamente
contemplados en la lista freebsd-doc). Tambi&eacute;n est&aacute;n
incluidos algunos que realmente no se ha hablado de ellos, pero
ser&iacute;an una buena idea. Cada proyecto lista la persona de contacto
para ese proyecto (si s&eacute; qui&eacute;n es).</p>
<p>Si piensas que puedes contribuir en cualquier de ellos, por favor,
no dudes en hacerlo. Deber&iacute;s hablar con la persona responsable,
qui&eacute;n te pondr&aacute; al d&iacute;a de la marcha del proyecto.</p>
<h3><font color="#660000">FreeBSD para usuarios de Linux</font></h3>
<p><b>Responsable:</b> Annelise Anderson &lt;andrsn@andrsn.stanford.edu&gt;</p>
<p><b>Sin&oacute;psis:</b> Los usuarios de FreeBSD provenientes de Linux
pueden tener confusiones por algunas de las diferencias entre los dos
sistemas (diferente shell por defecto, c&oacute;mo funciona la configuraci&oacute;n de arranque, y cosas as&iacute;). Annelise est&aacute; coordinando el
desarrollo de un tutorial/FAQ que reflejar&aacute; estos puntos.</p>
<p>La lista de preguntas actuales est&aacute; en
<a href="http://freebsd.stanford.edu/FreeBSD/linux.html">http://freebsd.stanford.edu/FreeBSD/linux.html</a>.</p>
<h3><font color="#660000">Actualizar los ficheros FOO.TXT</font></h3>
<p><b>Responsable:</b> Doug &lt;studded@dal.net&gt;</p>
<p><b>Sin&oacute;psis:</b> Los ficheros "FOO.TXT" son los ficheros
README, los INSTALL.TXTs, los ABOUT.TXTs y todos los que obtienes con
FreeBSD. Doug (y otras personas) est&aacute;n revisando los contenidos
para asegurar que sean cuidados, consistentes y f&aacute;ciles de
entender.</p>
<h3><font color="#660000">Migraci&oacute;n del Handbook de LinuxDoc a DocBook</font></h3>
<p><b>Responsable:</b> Nik Clayton &lt;nik@freebsd.org&gt;</p>
<p><b>Sin&oacute;psis:</b> El Handbook de FreeBSD est&aacute; siendo
migrado de DTD LinuxDoc a DTD DocBook. Durante el proceso han estado
apareciendo algunos problemas, sobre todo referentes a TeX. A&uacute;n
quedan algunas semanas para que el trabajo est&eacute; finalizado.</p>
<h3><font color="#660000">Escribir una secci&oacute;n en las FAQ y/o Handbook</font></h3>
<p><b>Responsable:</b> Ninguno</p>
<p><b>Sin&oacute;psis:</b> Algunas partes de las FAQ y del Handbook
est&aacute;n incompletas, esperando tu aportaci&oacute;n. Si has usado
alguna parte de la documentaci&oacute;n ya existente y encuentras que
es complicada o insuficiente, por favor, com&eacute;ntalo, ofreciendo
alguna posible soluci&oacute;n.</p>
<p>Alternativamente, si has hecho algo que no existe en la FAQ y/o
handbook, por favor, considera escribir una nueva secci&oacute;n.</p>
<h3><font color="#660000">Escribir el documento "As&iacute; es como est&aacute; hecho el Handbook"</font></h3>
<p><b>Responsable:</b> Ninguno (Podemos ofrecer asistencia)</p>
<p><b>Sin&oacute;psis:</b> El mecanismo usado para crear de una vez las
versiones en HTML, Postscript y texto no est&aacute; particularmente
bi&eacute;n documentado. Si quieres aprender como funciona este proceso,
y documentarlo, por favor, av&iacute;sanos.</p>
<p>Estar&aacute;s haciendo un gran favor a todo el mundo, por que as&iacute; ser&aacute; mucho m&aacute;s f&aacute;cil para la gente contribuir con
documentaci&oacute;n lista para integrar en el Handbook.</p>
<h3><font color="#660000">Reescribir el Handbook :-)</font></h3>
<p><b>Responsable:</b> Ninguno, todav&iacute;a</p>
<p><b>Sin&oacute;psis:</b> El Handbook ha ido creciendo org&aacute;nicamente durante los &uacute;ltimos a&ntilde;os. Esto significa que algunas secciones
no est&aacute;n organizadas como deber&iacute;an y otras necesitan ser
reescritas.</p>
<p>Alguien tiene que</p>
<ul>
<li>Leer el Handbook en profundidad</li>
<li>Proponer una estructura renovada</li>
<li>Entender como est&aacute; implementado el Handbook (esto
significar&aacute; aprender un poco sobre SGML, y probablemente
participar en el proyecto de migraci&oacute;n a DocBook).</li>
</ul>
<p>Para hacer el trabajo m&aacute;s manejable, ser&iacute;a de gran
ayuda que alguien mantuviese una p&aacute;gina web que listase los
comentarios de la gente sobre la estructura del Handbook. Esto nos
dar&iacute;a algo con lo que empezar a trabajar.</p>
<h3><font color="#660000">Escribir algunas informaciones nuevas</font></h3>
<h4><font color="#660000">La arquitectura VM de FreeBSD</font></h4>
<p><b>Responsable:</b> John Dyson &lt;<a href="mailto:dyson@iquest.net">
dyson@iquest.net</a></p>
<p><b>Sin&oacute;psis:</b> FreeBSD 2.x tiene una arquitectura de
memoria virtual totalmente renovada. Desafortunadamente no existe
ning&uacute;n tipo de documentaci&oacute;n excepto el c&oacute;digo
fuente y algunos emails antiguos de John Dyson.
Mira en <a href="http://www.backplane.com/FreeBSD/FreeBSDVM.txt">
FreeBSD VM System Overview</a> para una primera aproximaci&oacute;n.
<h4><font color="#660000">El nuevo SCSI para FreeBSD (CAM)</font></h4>
<p><b>Responsable:</b>
&lt;<a href="mailto:doc@freebsd.org">doc@freebsd.org</a>>,
&lt;<a href="mailto:scsi@freebsd.org">scsi@freebsd.org</a>>
<p><b>Sin&oacute;psis:</b> Mira en
<a href="http://www.freebsd.org/~gibbs/">
The Design and Implementation of the FreeBSD SCSI Subsystem</a> para
una primera aproximaci&oacute;n.
<h3><font color="#660000">Escribir nuevos Tutoriales</font></h3>
<p><b>Responsable:</b>
&lt;<a href="mailto:doc@freebsd.org">doc@freebsd.org</a>
<p><b>Sin&oacute;psis:</b>
<ul>
<li>C&oacute;mo actualizar de a.out a elf</li>
<li>C&oacute;mo crear una release de FreeBSD</li>
</ul>
<h3><font color="#660000">Escribir p&aacute;ginas man para el kernel</font></h3>
<p><b>Responsable:</b>
&lt;<a href="mailto:doc@freebsd.org">doc@freebsd.org</a>
<p><b>Sin&oacute;psis:</b> Documentar funciones de Kernel, secci&oacute;n 9
<h3><font color="#660000">CGI Scripts</font></h3>
<p><b>Responsable:</b>
&lt;<a href="mailto:doc@freebsd.org">doc@freebsd.org</a>,
Wolfram Schneider &lt;<a href="mailto:wosch@freebsd.org">
wosch@freebsd.org</a>
<p><b>Sin&oacute;psis:</b>
<ul>
<li>Reescribir el cgi cvsweb.cgi usando el m&oacute;dulo de Perl RCS.</li>
<li>Reescribir el cgi man.cgi y fijar algunos errores.</li>
<li>Escribir un m&oacute;dulo en Perl para el INDEX de los ports.</li>
</ul>
<h3>Aqu&iacute; hay algunos apuntes para el m&oacute;dulo de ports</h3>
<h4>Una l&iacute;nea en /usr/ports/INDEX es como</h4>
<pre>
xfig-3.2.2|/usr/ports/graphics/xfig|/usr/X11R6|A drawing program for X11|/usr/ports/graphics/xfig/pkg/DESCR|ports@FreeBSD.ORG|graphics x11|XFree86-3.3.2 Xaw3d-1.3 jpeg-6b xpm-3.4k|XFree86-3.3.2 Xaw3d-1.3 jpeg-6b netpbm-94.3.1 tiff-3.4 transfig-3.2 xpm-3.4k
</pre>
<h4>El formato es</h4>
<pre>
distribution-name|port-path|installation-prefix|comment| \
description-file|maintainer|categories|build deps|run deps
</pre>
<h4>La anterior l&iacute;nea INDEX pasada por un objeto an&oacute;nimo hash</h4>
<pre>
$port = {
DISTRIBUTION_NAME => 'xfig-3.2.2',
PORT_PATH => '/usr/ports/graphics/xfig',
INSTALLATION_PREFIX => '/usr/X11R6',
COMMENT => 'A drawing program for X11',
DESCRIPTION_FILE => '/usr/ports/graphics/xfig/pkg/DESCR',
MAINTAINER => 'ports@FreeBSD.ORG',
CATEGORIES => ['graphics', 'x11'],
BUILD_DEPS => ['XFree86-3.3.2', 'Xaw3d-1.3', 'jpeg-6b',
'xpm-3.4k'],
RUN_DEPS => ['XFree86-3.3.2', 'Xaw3d-1.3', 'jpeg-6b',
'netpbm-94.3.1', 'tiff-3.4', 'transfig-3.2',
'xpm-3.4k']
};
</pre>
<h4>Ahora necesitamos algunas funciones</h4>
<ul>
<li>Imprimir un objeto $port como salida HTML
<li>Imprimir un obketo $port como salida ASCII
<li>Encontrar todos los objetos mantenidos por el usuario XYZ
<li>Encontrar todos los objetos que est&aacute;n en la categor&iacute;a XYZ
<li>Encontrar todos los objetos que la compilaci&oacute;n/ejecuci&oacute;n depende del port XYZ
<li>Encontrar todos los objetos que tengan la cadena XYZ en DISTRIBUTION_NAME o COMMENT
<li>Ordenar objetos por DISTRIBUTION_NAME
</ul>
<h4>Finalmente</h4>
<p>Modificar los cgi's url.cgi, ports.cgi, pds.cgi y el script
portindex para usar este m&oacute;dulo.
<h3><font color="#660000">Traducciones de la documentaci&oacute;n de FreeBSD</font></h3>
<p><b>Responsable:</b>
&lt;<a href="mailto:doc@freebsd.org">doc@freebsd.org</a>
Traducir la documentaci&oacute;n de FreeBSD (Web, FAQ, Handbook,
p&aacute;ginas man) a otros idiomas. Mira en <a href="translations.html">
el proyecto de traducciones</a>.
<p></p><a href="docproj.html">FreeBSD Documentation Project Home</a>
&footer
</body>
</html>

59
es/docproj/doc-set.sgml Normal file
View file

@ -0,0 +1,59 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto de Documentaci&oacute;n de FreeBSD: Estructura">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: doc-set.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>La documentaci&oacute;n de FreeBSD se distribuye en 4 categor&iacute;as
b&aacute;sicas</p>
<ol>
<li><p><a href="http://www.freebsd.org/cgi/man.cgi"><b>Las p&aacute;ginas man</b></a></p>
<p>El proyecto no est&aacute; vinculado directamente con &eacute;stas
al formar parte del sistema base. La excepci&oacute;n a esto es el
equipo Japon&eacute;s, ya que las est&aacute;n traduciendo.</p>
<p>Esto no significa que las p&aacute;ginas man no sean importantes,
al contrario. Solo decir que est&aacute;n intimamente ligadas a los
sistemas espec&iacute;ficos de FreeBSD, y muchas veces la persona
m&aacute;s indicada para escribirlas, es la persona que ha escrito
esa parte de FreeBSD.</p></li>
<li><p><a href="../FAQ/FAQ.html"><b>La FAQ</b></a></p>
<p>Esta es mantenida por el proyecto. El objetivo es reunir (en
formato de pregunta y respuesta) las preguntas m&aacute;s
frecuentemente realizadas en las diferentes listas de
distribuci&oacute;n y grupos de news de FreeBSD.</p></li>
<li><p><a href="../handbook/handbook.html"><b>El Handbook</b></a></p>
<p>Este es mantenido por el proyecto. Los temas que necesitan una
discsi&oacute;n m&aacute;s profunda son tratado en el handbook.</p>.</li>
<li><p><a href="../tutorials/"><b>Los Tutoriales</b></a></p>
<p>Algunos de estos tutoriales son mantenidos por los "committers"
del proyecto, y otros no. El <b>mantenimiento</b> de estos
documentos depende de los autores de forma individual.</p>
<p>Algunos tutorials se encuentran en el servidor web de FreeBSD.
Para estos tutoriales el autor env&iacute;a las modificaciones a
uno de los "committers", y el "committer" realiza el cambio. Otros
tutoriales est&aacute;n situados en el espacio de web privado del
autor, y el autor puede hacer cambios cuando quiera. Algunas veces
esta es una elecci&oacute;n deliberada del autor, y otras un
accidente hist&oacute;rico.</p></li>
</ol>
<p></p><a href="docproj.html">FreeBSD Documentation Project Home</a>
&footer
</body>
</html>

77
es/docproj/docproj.sgml Normal file
View file

@ -0,0 +1,77 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto de documentaci&oacute;n de FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: docproj.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<h2>Introducci&oacute;n</h2>
<p>Tener el control de un nuevo y complejo sistema operativo es siempre
una tarea complicada, no importa los gr&aacute;ficos que tenga. FreeBSD
no es diferente en este aspecto.</p>
<p>Aunque existe una gr&aacute;n cantidad de libros sobre Unix BSD (y Unix en
general), FreeBSD tiene sus propias caracter&iacute;sticas y
procedimientos.</p>
<p>Adem&aacute;s, FreeBSD puede ser la primera aproximaci&oacute;n a
sistemas Unix para muchos de sus usuarios, por lo que la disponibilidad
de documentaci&oacute;n de alta calidad es muy importante.</p>
<p>El Proyecto de Documentaci&oacute;n de FreeBSD existe para ayudar
en este campo. Existen dos maneras de trabajar;</p>
<ol>
<li><p>Miembros del proyecto de documentaci&oacute;n escriben
documentos para ser incluidos en la <em>Distribuci&oacute;n de
Documentaci&oacute;n de FreeBSD</em>.</p></li>
<li><p>Miembros del proyecto de documentaci&oacute;n discuten y
trabajan la organizaci&oacute;n de la <em>Distribuci&oacute;n
de Documentaci&oacute;n de FreeBSD</em>.</p></li>
</ol>
<table bgcolor="#ffffcc" border="1" cellpadding="4" width="100%">
<tr>
<td><h2 align="center"><a href="current.html">Proyectos
actuales</a></h2>
<p>Existen en estos momentos diferentes proyectos <em>en
progreso</em> como parte del esfuerzo de documentaci&oacute;n.
Por favor, mira en esta lista por si hay algo en lo que
<b>t&uacute;</b> nos puedas ayudar.</p></td>
</tr>
</table>
<h2><a href="who.html">Quienes somo, c&oacute;mo participar</a></h2>
<p>Esta p&aacute;gina explica qui&eacute;n forma parte del Proyecto de
Documentaci&oacute;n y como participar.</p>
<h2><a href="doc-set.html">La distribuci&oacute;n de Documentaci&oacute;n de FreeBSD</a></h2>
<h2><a href="sgml.html">SGML y el Proyecto de Documentaci&oacute;n</a></h2>
<p>El Proyecto intenta usar SGML para la documentaci&oacute;n. Esta
p&aacute;gina indica como se consigue, apuntando al lector algunas
fuentes de informaci&oacute;n sobre SGML.</p>
<h2><a href="submitting.html">Enviando Documentaci&oacute;n</a></h2>
<p>Enviar documentaci&oacute;n es la mejor manera de entrar a formar
parte del proyecto, y hacer que FreeBSD sea m&aacute;s sencillo de usar.
Esta p&aacute;gina explica la mejor manera de enviar la
documentaci&oacute;n para que est&eacute; visible lo antes posible.</p>
<p>Traducciones de la documentaci&oacute;n de FreeBSD, p&aacute;ginas
Web, Handbook, p&aacute;gina man y las FAQ.</p>
&footer
</body>
</html>

173
es/docproj/sgml.sgml Normal file
View file

@ -0,0 +1,173 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto de Documentaci&oacute;n de FreeBSD: SGML">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: sgml.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>El proyecto de Documentaci&oacute;n intenta usar SGML como
m&eacute;todo estandar de representar la documentaci&oacute;n.</p>
<p>SGML es el lenguaje <b>S</b>tandard <b>G</b>eneralised <b>M</b>arkup
<b>L</b>.</p>
<p>Brevemente (y disculpas para los puristas de SGML que puedan sentirse
ofendidos), SGML es un lenguaje para escribir otros lenguajes.</p>
<p>Probablemente ya has usado SGML sin saberlo. HTML, el leguaje en el
que se escriben las p&aacute;ginas web, tiene una descripci&oacute;n
formal. Esa descripci&oacute;n est&aacute; escrita en SGML. Cuando
escribes en HTML <b>no</b> est&aacute;s escribiendo SGML, pero s&iacute;
est&aacute;s usando un lenguaje definido por SGML.</p>
<p>Existen muchos, muchos lenguajes "markup" que est&aacute;n definidos
usando SGML. HTML es uno de ellos. Otro es el llamado "LinuxDoc". Como
puedes adivinar, fue creado por los grupos de usuarios de Linux para
escribir su documentaci&oacute;n, y el Proyecto de Documentaci&oacute;n
de FreeBSD lo adopt&oacute;.</p>
<p>Otro lenguaje "markup" definido usando SGML es el llamado "DocBook".
Este es un lenguaje dise&ntilde;ado espec&iacute;ficamente para escribir
documentaci&oacute;n t&eacute;cnica.</p>
<p>Por ejemplo, as&iacute; estar&iacute;a escrito un breve p&aacute;rrafo
en HTML (no te preocupes del contenido, solo f&iacute;jate en los
tags):</p>
<pre><![ CDATA [
<p>The system's passwords are stored in <tt>/etc/passwd</tt>. To edit
this file you should use <b><tt>vipw</tt></b>. However, if you just
want to add a new user you can use <b><tt>adduser</tt></b>.</p>
]]></pre>
<p>El mismo p&aacute;rrafo usando DocBook ser&iacute;a:</p>
<pre><![ CDATA [
<para>The system's passwords are stored in
<filename>/etc/passwd</filename>. To edit this file you should use
<command>vipw</command>. However, if you just want to add a new user
you can use <command>adduser</command>.</para>
]]></pre>
<p>Como puedes ver, DocBook es mucho m&aacute;s expresivo que HTML. En el
ejemplo HTML el nombre del fichero se muestra con una fuente de tipo
"typewriter". En el ejemplo de DocBook, el nombre de fichero est&aacute;
marcado como que es un "filename", la representaci&oacute;n de un
nombre de fichero no est&aacute; descrita.</p>
<p>Hay grande ventajas en esta manera m&aacute;s expresiva de lenguaje:</p>
<ul>
<li><p>No es ambiguo o inconsistente.</p> <p>No pierdes tiempo
pensando "Hmm, necesito mostrar un nombre de fichero, deber&iacute;a
usar "tt", o "b", o "em"</p> <p>En lugar de eso, usas el tag
correcto para el trabajo correcto.</p>
<p>El proceso de conversi&oacute;n de DocBook a otros formatos como
HTML o Postscript asegura que todos ser&aacute;n vistos de la
misma manera.</p>
</li>
<li><p>Dejar de pensar en como representar la documentaci&oacute;n,
y solo te concentras en el contenido.</p>
<li><p>Como la documentaci&oacute;n no est&aacute; pensada para un
determinado formato de salida, la misma documentaci&oacute;n puede
crearse en diferentes formatos - texto, HTML, Postscript, RTF,
PDF, etc.</p></li>
<li><p>La documentaci&oacute;n es m&aacute;s "inteligente", lo que
permite hacer cosas m&aacute;s inteligentes con ella. Por ejemplo,
es posible crear un &iacute;ndice autom&aacute;tico que liste cada
comando mostrado en la documentaci&oacute;n.</p>.</li>
</ul>
<p>Si est&aacute;s familiarizado con ellos, es como las galer&iacute;as
de estilo de Microsoft Word, solo que infinitamente m&aacute;s
potente.</p>
<p>Por supuesto, esta potencia tiene un precio;</p>
<ul>
<li><p>Al existir un mayor n&uacute;mero de tags, hace que tardes
m&aacute;s en aprenderlos y como usarlos efectivamente.</p>
<p>La mejor manera de aprender es leer los fuentes de muchos
documentos de ejemplo, viendo como otros autores han escrito
informaci&oacute;n similar.</p></li>
<li><p>El proceso de conversi&oacute;n no es tan simple.</p></li>
</ul>
<p>Actualmente, el Proyecto est&aacute; usando LinuxDoc para el
Handbook y las FAQ. Esto est&aacute; cambiando, ya que se est&aacute;
haciendo una migraci&oacute;n de la documentaci&oacute;n a DocBook.</p>
<h2>Qu&eacute; pasa si no se LinuxDoc/DocBook? Todav&iacute;a puedo
contribuir?</h2>
<p>S&iacute;, por supuesto. Cualquier documentaci&oacute;n es mejor
que no tener nada. Si tienes documentaci&oacute;n con la que
contribuir y no est&aacute; en formato LinuxDoc o DocBook, no
te preocupes.</p>
<p><a href="submitting.html">Env&iacute;a</a> la documentaci&oacute;n
de la manera habitual. Alguien del proyecto recoger&aacute; los
documentos enviados y los convertir&aacute; por t&iacute;. Con un
poco de suerte, te ser&aacute; devuelta ya marcada en DocBook. As&iacute;
puedes comparar el documento original con el que has recibido y
aprender a hacerlo t&uacute; mismo.</p>
<p>Obviamente, esto retrasa el que la documentaci&oacute;n est&eacute;
online, pero no te preocupes.</p>
<h2>M&aacute; informaci&oacute;n sobre SGML y DocBook?</h2>
<dl>
<dt><a
href="http://www.sil.org/sgml/sgml.html"><b>http://www.sil.org/sgml/sgml.html</b></a></dt>
<dd><p>El web de SGML/XML. Incluye m&aacute;s recursos sobre SGML.</p></dd>
<dt><a
href="http://www-tei.uic.edu/orgs/tei/sgml/teip3sg/index.html"><b>http://www-tei.uic.edu/orgs/tei/sgml/teip3sg/index.html</b></a></dt>
<dd><p>The "Gentle Introduction to SGML". De recomendada lectura para
cualquiera que desee tener conocimientos avanzados de SGML.</p></dd>
<dt><a
href="http://www.ora.com/davenport/"><b>http://www.ora.com/davenport/</b></a></dt>
<dd><p>El Grupo Davenport dise&ntilde;&oacute; y mantiene el DTD
DocBook. Estas p&aacute;ginas est&aacute;n pensadas para usuarios que
se sienten de manera confortable con SGML y quieren aprender
DocBook.</p>
<p>La Documentaci&oacute;n DocBook est&aacute; disponible en formato PDF
en <a href="http://www.freebsd.org/~wosch/docbook/">http://www.freebsd.org/~wosch/docbook/</a></p></dd>
<dt><a
href="http://fallout.campusview.indiana.edu/~jfieber/docbook/"><b>http://fallout.campusview.indiana.edu/~jfieber/docbook/</b></a></dt>
<dd><p>La p&aacute;gina de John Fieber contiene links a otros recursos
de DocBook y documentos de ejemplo. Tambi&eacute; incluye una
gu&iacute;a de marcas para FreeBSD.</dd>
<dt><a
href="http://www.nothing-going-on.demon.co.uk/FreeBSD/"><b>http://www.nothing-going-on.demon.co.uk/FreeBSD/</b></a></dt>
<dd><p>La p&aacute;gina de Nik Clayton contiene links a
documentaci&oacute;n escrita y despu&eacute;s convertida a HTML.
Los ficheros DocBook originales est&aacute;n disponibles, dando
una idea muy razonable de como usar los diferentes elementos
de DocBook.</p></dd>
</dl>
<p></p><a href="docproj.html">FreeBSD Documentation Project Home</a>
&footer
</body>
</html>

141
es/docproj/submitting.sgml Normal file
View file

@ -0,0 +1,141 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto de Documentaci&oacute;n de FreeBSD: Enviando Documentaci&oacute;n">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: submitting.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<h2>He escrito algunos documentos, como los env&iacute;o?</h2>
<p>Ante todo, gracias por ocupar tu tiempo en hacerlo.</p>
<p>Tendr&iacute;as que poner los documentos disponibles para ser revisados
. Si puedes ponlos en un espacio FTP o Web. Si no tienes espacio
propio, env&iacute;alos a <a
href="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/</a>, y usa <b>send-pr</b> para comunicar a los
"committers" que est&aacute; disponible.</p>
<p>A continuaci&oacute;n env&iacute;a un mensaje a la lista de
distribuci&oacute;n freebsd-doc, con una breve descripci&oacute;n
y su localizaci&oacute;n. Pide opiniones.</p>
<p>Tambi&eacute;n deber&iacute;as enviar una copia del mensaje a otras
listas relacionadas. Por ejemplo, algo relativo al uso de CVSup para
mantener actualizado el c&oacute;digo fuente, tambi&eacute;n ser&iacute;a
de inter&eacute;s para los subscriptores de las listas
<tt>FreeBSD-current</tt> y <tt>FreeBSD-stable</tt>.</p>
<p>Una vez la gente haya visto tu documento y hayas podido incorporar
las posibles sugerencias que te hayan hecho, est&aacute;s preparado
para enviarlo.</p>
<p>Para hacerlo, compacta el/los documentos en un fichero tar. Si tu
documentaci&oacute;n consta de 3 ficheros, <tt/uno/, <tt/dos/ y <tt/tres/,
y quieres compactarlos en el fichero <tt/doc.tar/, haz</p>
<pre>
% <b>tar cf doc.tar one two three</b>
</pre>
<p>Una vez hecho, comprime el fichero tar,</p>
<pre>
% <b>gzip -9 doc.tar</b>
</pre>
<p>creando el fichero <tt>doc.tar.gz</tt>.</p>
<p>A continuaci&oacute;n env&iacute;a el fichero <tt/doc.tar.gz/ (
obviamente, ponle un nombre m&aacute;s indicativo del contenido pero
siempre manteniendo la extensi&oacute;n <tt/tar.gz/) a
<tt/ftp.freebsd.org/, en el directorio
<tt>/pub/FreeBSD/incoming/</tt>.</p>
<p>Ahora tienes que comunicar al proyecto de documentaci&oacute;n la
existencia del fichero. La manera correcta de hacerlo es usar un
comando llamado <b>send-pr</b>, el cual deber&iacute;a estar instalado
en tu m&aacute;quina.</p>
<p>Tienes que hacer esto para que tu env&iacute;o pueda ser controlado.
Cuando env&iacute;as un PR (Problem Report) se le asigna un
n&uacute;mero &uacute;nico. As&iacute; uno de los committers puede
asignarse el PR, y ponerse de acuerdo contigo para hacer el env&iacute;o
final.</p>
<p>Make sure the "Category" is set to "docs" and that the "Class" is set
to one of "change-request". And do not forget to include the name of the
file that you uploaded, so that the committers can find it!</p>
<p>Aseg&uacute;rate que el campo "Category" tiene como valor "docs" y que
el campo "Class" est&aacute; en "change-request". No te olvides de
incluir el nombre del fichero que has enviado, para que el committer
pueda encontrarlo.</p>
<p>Cuando sales del editor, ser&aacute; enviado un mensaje de PR al
lugar correcto. En un corto periodo de tiempo recibir&aacute;s un
mensaje de notificaci&oacute;n indicandote el n&uacute;mero de PR
asignado, pudiendo usar este n&uacute;mero para hacer el seguimiento
del estado en que se encuentra.</p>
<p>Alternativamente, puedes usar un interface web en <a
href="http://www.freebsd.org/send-pr.html">http://www.freebsd.org/send-pr.html</a>.</p>
<h2>He hecho algunos cambios a documentaci&oacute;n ya existente. Como
la env&iacute;o?</h2>
<p>De nuevo, gracias por ocuparte de ello.</p>
<p>Lo primero que tienes que hacer es crear un fichero especial llamado
<i>diff</i>. Este fichero mostrar&aacute; &uacute;nica y exclusivamente
las modificaciones realizadas sobre la documentaci&oacute;n original.</p>
<p>Para hacer un "diff" tienes que;</p>
<ol>
<li><p>Hacer una copia del fichero que vas a modificar. Si est&aacute;s
cambiando el fichero <tt/foo.sgml/, haz</p>
<pre>
% <b>cp foo.sgml foo.sgml.old</b>
</pre></li>
<li><p>Entonces, haz los cambios en el fichero foo.sgml</p>
<pre>
% <b>vi foo.sgml</b>
... tap tap tap ...
... testea los cambios, leelos y revisalos...
</pre></li>
<li><p>Haz el diff. El comando para hacerlo es</p>
<pre>
% <b>diff -c foo.sgml.old foo.sgml > foo.diff</b>
</pre>
<p>Este comando buscar&aacute; las diferencias entre los dis ficheros
escribiendolas en el fichero <tt/foo.diff/.</p></li>
</ol>
<p>Ya puedes enviar el fichero <tt/foo.diff/ al proyecto.</p>
<p>Tambi&eacute;n puedes enviar el fichero <tt/foo.diff/ a <a
href="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp://ftp.FreeBSD.ORG
/pub/FreeBSD/incoming/</a> o, si es muy pque&ntilde;o, incluir el diff
directamente en el PR, en la secci&oacute;n "Fix:"</p>
<p>De cualquier manera, usar&aacute;s el comando <b>send-pr</b> para
hacer saber a los "committers" que se han producido modificaciones.
Aseg&uacute;rate que el campo "Category" contiene "docs" y que el
campo "Class" es "doc-bug" (si tu cambio modifica alg&uacute;n error
ya existente) o "change-request" (si est&aacute;s a&ntilde;adiendo
nueva informaci&oacute;n a una secci&oacute;n ya existente).</p>
<p></p><a href="docproj.html">FreeBSD Documentation Project Home</a>
&footer
</body>
</html>

View file

@ -0,0 +1,80 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto de Documentaci&oacute;n de FreeBSD: Traducciones">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: translations.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<h2>El "FreeBSD Korean Documentation Project"</h2>
<b>Web</b>: <a href="http://www.kr.freebsd.org/projects/doc-kr/">http://www.kr.freebsd.org/projects/doc-kr/</a><br>
<b>E-Mail</b>: <a href="mailto:doc@kr.freebsd.org">doc@kr.freebsd.org</a><br>
<dl>
<dt><i>Documentos actualmente en desarrollo</i></dt>
<dd>Handbook</dd>
</dl>
<h2>El "FreeBSD Japanese Documentation Project"</h2>
<b>Web</b>: <a href="http://www.jp.freebsd.org/doc-jp/">http://www.jp.freebsd.org/doc-jp/</a><br>
<b>E-Mail</b>: <a href="mailto:doc-jp@jp.freebsd.org">doc-jp@jp.freebsd.org</a><br>
<dl>
<dt><i>Documentos disponibles</i></dt>
<dd>
<a href="../ja/handbook/">Handbook</a>,
<a href="../ja/FAQ/">FAQ</a>,
<a href="../ja">Web</a>,
<a href="http://www.jp.freebsd.org/NewsLetter/Issue2/">
FreeBSD NewsLetter Issue #2</a>
</dd>
<dt><i>Documentos actualmente en desarrollo</i></dt>
<dd>
Tutoriales de FreeBSD</dd>
</dl>
<h2>El "FreeBSD German Documentation Project"</h2>
<b>Web</b>: <a href="http://www.de.freebsd.org/de/uebersetzung.html">http://www.de.freebsd.org/de/uebersetzung.html</a><br>
<b>E-Mail</b>: <a href="mailto:de-bsd-translators@de.freebsd.org">de-bsd-translators@de.freebsd.org</a><br>
<dl>
<dt><i>Documentos actualmente en desarrollo</i></dt>
<dd><a href="http://www.de.freebsd.org/de/handbook/">Handbook</a></dd>
</dl>
<h2>El "FreeBSD Spanish Documentation Project"</h2>
<b>Web</b>: <a href="http://www.es.freebsd.org/es/">http://www.es.freebsd.org/es/</a><br>
<b>E-Mail</b>: <a href="mailto:jesusr@freebsd.org">jesusr@freebsd.org</a><br>
<dl>
<dt><i>Listas de distribuci&oacute;n disponibles</i></dt>
<dd>Env&iacute;a un mail a <a href="mailto:majordomo@es.freebsd.org">majordomo@es.freebsd.org</a> con las palabras "subscribe freebsd" en el cuerpo del mensaje.</dd>
<dt><i>Documentos disponibles</i></dt>
<dd><a href="../es/FAQ/FAQ.html">FAQ</a></dd>
<dt><i>Documentos actualmente en desarrollo</i></dt>
<dd>Handbook, Web</dd>
</dl>
<h2>El "French FreeBSD Documentation Project"</h2>
<b>Web</b>: <a href="http://www.freebsd-fr.org/">http://www.freebsd-fr.org</a><br>
<dl>
<dt><i>Listas de distribuci&oacute;n disponibles</i></dt>
<dd>Env&iacute;a un mail a <a href="mailto:majordomo@freebsd.francenet.fr">majordomo@freebsd.francenet.fr</a> con las palabras "subscribe freebsd-france" en el cuerpo del mensaje<br>El env&iacute;o de mensajes est&aacute; permitido para miembros en <a href="mailto:freebsd-fr@freebsd.francenet.fr">freebsd-fr@freebsd.francenet.fr</a></dd>
<dt><i>Documentos disponibles</i></dt>
<dd><a href="http://www.freebsd-fr.org/FAQ/FAQ.html">FAQ</a></dd>
<dt><i>Documentos actualmente en desarrollo</i></dt>
<dd>Handbook</dd>
</dl>
<p></p><a href="docproj.html">FreeBSD Documentation Project Home</a>
&footer
</body>
</html>

35
es/docproj/who.sgml Normal file
View file

@ -0,0 +1,35 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyecto de Documentaci&oacute;n de FreeBSD: Quienes somos?">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: who.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>El proyecto est&aacute; compuesto por un grupo de personas a nivel
totalmente individual, y lo &uacute;nico que tenemos en com&uacute;n es
que estamos subscritos a la lista de distribuci&oacute;n
<a href="mailto:FreeBSD-doc@FreeBSD.ORG">FreeBSD-doc@FreeBSD.ORG</a>.</p>
<p>Algunos de nosotros podemos hacer "commits" directamente en la
secci&oacute;n de documentaci&oacute;n de FreeBSD. La lista completa
de personas con privilegios de "commit" est&aacute; en <a
href="../handbook/staff:doc.html"> el Handbook</a>.</p>
<p>Otros no tienen privilegios de "committer", pero escriben y <a
href="submitting.html"> env&iacute;an documentaci&oacute;n</a>
igualmente. Uno de los "committers" la incluir&aacute; en la
distribuci&oacute;n principal.</p>
<p>Si quieres ayuda y participar en el proyecto de documentaci&oacute;n
(y esperamos fervientemente que lo hagas), todo lo que tienes que
hacer es subscribirte a la lista y participar. Tan pronto como lo hayas
hecho, pasar&aacute;s a formar parte del proyecto.</p>
<p></p><a href="docproj.html">FreeBSD Documentation Project Home</a>
&footer
</body>
</html>

280
es/docs.sgml Normal file
View file

@ -0,0 +1,280 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Documentaci&oacute;n">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: docs.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<ul>
<li><a href="#press">FreeBSD en la Prensa</a></li>
<li><a href="#y2kbug">Compatibilidad a&ntilde;o 2000</a></li>
<li><a href="#newsletter">Newsletter</a></li>
<li><a href="#qnewsletter">FreeBSD Quick Newsletter</a></li>
<li><a href="#handbook">Manual de FreeBSD</a></li>
<li><a href="#faq">Frequently Asked Questions (FAQ)</a></li>
<li><a href="#tutorial">Tutoriales</a></li>
<li><a href="#addresources">Recursos adicionales</a></li>
<li><a href="#books">Libros</a></li>
<li><a href="#man">P&aacute;ginas Man</a></li>
<li><a href="#44doc">Documentos 4.4BSD</a></li>
<li><a href="#info">Documentos Info</a></li>
<li><a href="#source">El C&oacute;digo Fuente</a></li>
<li><a href="#doc">Proyecto de Documentaci&oacute;n de FreeBSD</a></li>
</ul>
<a name="press"></a>
<h2><a href="news/press.html">FreeBSD en la Prensa</a></h2>
<p>Noticias sobre FreeBSD.</p>
<a name="y2kbug"></a>
<h2><a href="y2kbug.html">Compatibilidad a&ntilde;o 2000</a></h2>
<p>Este es el estado actual del proyecto FreeBSD respecto a la
compatibilidad del a&ntilde;o 2000.</p>
<a name="newsletter"></a>
<h2><a href="publish.html#newsletter">Newsletter</a></h2>
<p>The FreeBSD Newsletter, publicada y distribuida gratuitamente
por Walnut Creek CDROM.</p>
<a name="qnewsletter"></a>
<h2><a href="news/qnewsletter.html">FreeBSD Real-Quick (TM) Newsletter (RQN)</a></h2>
<p>Recopilaci&oacute;n de noticias mensuales (a veces quincenales)
referentes a los desarrollos en FreeBSD. Subscr&iacute;bete a la
lista freebsd-announce para recibirla v&iacute;a e-mail.</p>
<a name="handbook"></a>
<h2><a href="handbook/handbook.html">Manual de FreeBSD</a></h2>
<p>Esta es una valiosa herramienta en constante desarrollo para usuarios
de FreeBSD. Por favor, dirigir comentarios, sugerencias o contribuciones
a <a
href="mailto:freebsd-doc@FreeBSD.ORG"><tt>&lt;freebsd-doc@FreeBSD.ORG&gt;</tt></a>.</p>
<p>Tambi&eacute;n est&aacute; disponible la
<a href="&base/ja/handbook/">Traducci&oacute;n Japonesa</a> del
manual (codificaci&oacute;n EUC).</p>
<a name="faq"></a>
<h2><a href="FAQ/FAQ.html">Frequently Asked Questions (FAQ)</a></h2>
<p>Si tienes una pregunta o duda, hay muchas posibilidades de que otras
personas tambi&eacute;n la hayan tenido. La mayor&iacute;a de ellas
han sido recopiladas en formato de pregunta-respuesta.</p>
<p>&i.new; Ahora ofrecemos una <a href="&base/ja/FAQ/">
traducci&oacute;n en Japon&eacute;s</a> de las FAQ (codificaci&oacute;n
EUC).</p>
<a name="tutorial"></a>
<h2>Tutoriales</h2>
<p>Aqu&iacute; tienes una serie de documentos referentes a FreeBSD,
tanto a nivel de hardware como de software. Si tienes alg&uacute;n
comentario o te gustar&iacute;a enviar alguna documentaci&oacute;n
puedes ponerte en contacto con nosotros en
<a href="mailto:freebsd-doc@FreeBSD.ORG">freebsd-doc@FreeBSD.org</a>.</p>
<ul>
<li><a href="tutorials/newuser/newuser.html">Para gente nueva tanto en
FreeBSD como <em>en</em> Unix.</a></li>
<li><a href="tutorials/mh/mh.html">Una introducci&oacute;n al software
de correo MH.</a></li>
<li><a href="tutorials/devel/devel.html">Gu&iacute;a del usuario de las
herramientas de programaci&oacute;n de FreeBSD.</a></li>
<li><a href="tutorials/ddwg/ddwg.html">Escribir drivers de dispositivos
para FreeBSD.</a>
(<a href="tutorials/ddwg/ddwg.ps">postscript</a>,
<a href="tutorials/ddwg/ddwg-html.tar.gz">fichero .tar.gz</a>)</li>
<li><a href="tutorials/ppp/ppp.html">Manual de PPP - IP Aliasing.</a>
(<a href="tutorials/ppp/ppp.ps">postscript</a>,
<a href="tutorials/ppp/ppp-html.tar.gz">fichero .tar.gz</a>)</li>
<li><a href="tutorials/multios/multios.html">Uso de FreeBSD con otros
sistemas operativos.</a></li>
<li><a href="tutorials/fonts/fonts.html">Fuentes y FreeBSD.</a></li>
<li><a href="http://www.cypher.net/~black/ipalias.html">IP Aliasing.</a></li>
<li><a href="http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html">Actualizar FreeBSD mediante c&oacute;digo fuente (usando <b><tt>make world</tt></b>).</a></li>
<li><a href="tutorials/diskformat/diskformat.html">Formatear dispositivos
para usar con FreeBSD 2.2-RELEASE.</a></li>
<li><a href="http://www.freebsd.org/~rpratt/227/">Detalles de
instalaci&oacute;n de FreeBSD 2.2.7 para principiantes.</a>
</ul>
<a name="addresources"></a>
<h2>Recursos Adicionales</h2>
<p>www.FreeBSD.org no es el &uacute;nico lugar donde conseguir
informaci&oacute;n sobre FreeBSD. Varios esfuerzos independientes han
conseguido crear valiosos documentos sobre FreeBSD:</p>
<ul>
<li><p><a href="mailto:mckusick@mckusick.com">Kirk McKusick</a>, uno
de los arquitectos originales de BSD en la Universidad de Berkeley,
explica en dos cursos las
<a href="http://www.mckusick.com/courses/">interioridades del Kernel
4.4BSD</a> usando FreeBSD. Para aquellos que no puedan acudir a sus
clases, est&aacute; disponible una cinta de v&iacute;deo.</p></li>
<li><p><a href="http://www.computerbits.com/">Computer Bits</a>, Una
revista on-line de Internet, ha estado publicando desde Marzo de 1996
una serie de excelentes art&iacute;culos relacionados con FreeBSD en su
columna titulada <strong>The Network Community</strong>, escrita por
<a href="mailto:tedm@agora.rdrop.com">Ted Mittelstaedt</A>.
<br>Estos art&iacute;culos cubren desde
<a href="http://www.computerbits.com/archive/9603/lan9603.htm">
c&oacute;mo instalar un servidor de correo basado en FreeBSD</a> hasta
configuraci&oacute;n del
<a href="http://www.computerbits.com/archive/9708/lan9708.htm">
Network Address Translation</a>.</p></li>
<li><p><A HREF="http://www.vmunix.com/fbsd-book/">
A Comprehensive Guide to FreeBSD</A> - un intento en formato de lectura
m&aacute;s c&oacute;moda explicando el sistema operativo FreeBSD.
Dirigido especialmente a personas nuevas tanto en FreeBSD como en Unix.
Actualmente en progreso.</p></li>
<li><p><A HREF="http://flag.blackened.net/freebsd/">
FreeBSD How-To's for the Lazy and Hopeless</A> es otro intento de
documentaci&oacute;n sobre instalaci&oacute;n y configuraci&oacute;n
de FreeBSD en formato How-To.</p></li>
<li><p><a
HREF="http://sunsite.unc.edu/LDP/HOWTO/mini/Linux+FreeBSD-mini-HOWTO.html">
The Linux+FreeBSD mini-HOWTO</a> - este documento describe como usar
Linux y FreeBSD en el mismo sistema. Introduce en FreeBSD y explica como
los dos sistemas pueden cooperar, por ejemplo, compartiendo espacio
de swap.</p></li>
</ul>
<a name="books"></a>
<h2><a href="handbook/bibliography.html">Libros</a></h2>
<p>La documentaci&oacute;n online es &uacute;til, pero cualquier usuario
"serio" de FreeBSD deber&iacute;a considerar disponer de alguno de los
libros listados aqu&iacute;. La mayor&iacute;a de libros que cubren
el sistema BSD se adaptan perfectamente a FreeBSD.</p>
<a name="man"></a>
<h2><a href="http://www.freebsd.org/cgi/man.cgi">
P&aacute;ginas man</a></h2>
<dl>
<dt><strong>FreeBSD</strong></dt>
<dd>Por release:
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+1.0-RELEASE">1.0</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+1.1-RELEASE">1.1</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+1.1.5.1-RELEASE">1.1.5.1</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.0-RELEASE">2.0</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.0.5-RELEASE">2.0.5</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.1.0-RELEASE">2.1.0</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.1.5-RELEASE">2.1.5</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.1.6.1-RELEASE">2.1.6.1</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.1.7.1-RELEASE">2.1.7.1</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.2.1-RELEASE">2.2.1</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.2.2-RELEASE">2.2.2</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.2.5-RELEASE">2.2.5</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.2.6-RELEASE">2.2.6</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.2.7-RELEASE">2.2.7</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+2.2.8-RELEASE">2.2.8</a>,
<a
href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+3.0-current">3.0-current</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=FreeBSD+Ports">Ports</a>.
</dd>
<dt><strong>Otros sistemas</strong></dt>
<dd>
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=v7">Unix Seventh Edition (V7)</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=2.8BSD">2.8BSD</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=2.9BSD">2.9.1BSD</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=2.10BSD">2.10BSD</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=2.11BSD">2.11BSD</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=4.3BSD+Reno">4.3BSD Reno</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=NET%2F2">NET/2</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=386BSD+0.1">386BSD 0.1</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=4.4BSD+Lite2">4.4BSD Lite2</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=linux">Linux Slackware</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=NetBSD">NetBSD</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=OpenBSD">OpenBSD</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=plan9">Plan 9</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=sunos4">SunOS 4.x</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=sunos5">SunOS 5.x</a>,
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=ultrix">ULTRIX 4.2</a>,
and
<a href="http://www.freebsd.org/cgi/man.cgi?manpath=XFree86">XFree86</a>.
</dd>
</dl>
<!--
<form action="http://www.freebsd.org/cgi/man.cgi" method="GET">
Manual Page Search for:
<input type="hidden" name="proto" value="1.0">
<input type="hidden" name="apropos" value="0">
<input name="query" value="">
<input type="submit" value="Submit">
</form>
-->
<p>Este servicio es por cortes&iacute;a de
<a href="http://www.de.freebsd.org/~wosch/">Wolfram Schneider</a>. Hay
<a href="http://late5.e-technik.uni-erlangen.de/cgi-bin/bsddocquery.pl">
otro script</a> disponible con las p&aacute;ginas man de FreeBSD 2.0 y
XFree86 release 3.1, cortes&iacute;a de
<A HREF="http://late5.e-technik.uni-erlangen.de/user/eilts.html">
Hinrich Eilts</A>.<p>
<a name="44doc"></a>
<h2><a href="http://www.freebsd.org/doc/">
Documentos 4.4BSD</a></h2>
<p>
Si te gusta leer los manuales de BSD online, aqu&iacute; tienes
una versi&oacute;n hipertexto de los documentos 4.4BSD en
<a href="file:/usr/share/doc">/usr/share/doc</a>
<a name="info"></a>
<h2><a href="http://www.freebsd.org/info/">
Documentos Info</a></h2>
<p>
Si te gusta leer los documentos Info de FreeBSD online, aqu&iacute;
tienes una versi&oacute;n hypertexto de los documentos Info en
<a href="file:/usr/share/info">/usr/share/info</a>.
<a name="source"></a>
<h2><a href="http://minnie.cs.adfa.oz.au/FreeBSD-srctree/FreeBSD.html">El
c&oacute;digo fuente</a></h2>
<p>Si quieres poner tus manos en el c&oacute;digo fuente, aqu&iacute
tienes una versi&oacute;n hipertexto del <em>kernel</em> de FreeBSD.
Cortes&iacute;a de <a
href="http://minnie.cs.adfa.oz.au/warren.html">Warren
Toomey</a>.</p>
<a name="doc"></a>
<h2><a href="docproj/docproj.html">Proyecto de Documentaci&oacute;n de
FreeBSD</a></h2>
<p>Como FreeBSD, esta documentaci&oacute;n es el resultado de
voluntarios. Los objetivos del proyecto est&aacute;n descritos
aqu&iacute;, as&iacute; como los procedimientos para enviar
correcciones y nuevo material.</p>
&footer;
</body>
</html>

104
es/features.sgml Normal file
View file

@ -0,0 +1,104 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Avances Tecnol&oacute;gicos de FreeBSD">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: features.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<HTML>
&header;
<H1>FreeBSD ofrece diferentes caracter&iacute;sticas avanzadas.</H1>
<blockquote>
<p>No importa que aplicaci&oacute;n quieras que use los recursos del sistema
aprovech&aacute;ndolos al m&aacute;ximo. Las avanzadas caracter&iacute;sticas
de FreeBSD se encargar&aacute;n de ello.</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">Un
sistema operativo completo basado en 4.4BSD.</FONT></FONT>
<blockquote>
<p>Las raices de FreeBSD derivan de la &uacute;ltima release de software del
Computer Systems Research Group de la Universidad de California, Berkeley. El
libro <I>The Design and Implementation of 4.4BSD Operating System</I>,
escrito por los arquitectos del sistema 4.4BSD, describe en detalle muchas
de las funcionalidades del n&uacute;cleo de FreeBSD.</p>
<p>Gracias al nivel y experiencia de diversos grupos de desarrolladores de
todo el mundo, el proyecto FreeBSD ha trabajado para extender las
caracter&iacute;sticas y posibilidades del sistema operativo 4.4BSD,
consiguiendo en cada nueva release un sistema operativo m&aacute;s estable,
r&aacute;pido y conteniendo nuevas funcionalidades creadas a demanda de los
usuarios.</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">
FreeBSD ofrece el m&aacute;s alto rendimiento, gran compatibilidad con otros
sistemas operativos y una menor administraci&oacute;n del sistema.
</FONT></FONT>
<blockquote>
<p>Los desarrolladores de FreeBSD se han enfrentado a algunos de los problemas
m&aacute;s dif&iacute;ciles en el dise&ntilde;o de sistemas operativos para
poder ofrecerte estas avanzadas caracter&iacute;sticas:</p>
<ul>
<LI><B>Bounce buffering</B> trata sobre la limitaci&oacute;n en la
arquitectura ISA de los PC's que limita el acceso directo a memoria en los
primeros 16 megabytes.<p><i>Resultado:</i> sistemas con m&aacute;s de
16 megabytes operan m&aacute;s eficientemente con perif&eacute;ricos DMA
en el bus ISA.</li>
<li><b>Un buffer de cach&eacute; conjunto de memoria virtual y sistema de
ficheros</b> continuamente ajusta la cantidad de memoria usada por los
programas y el cache de disco.<p><i>Resultado:</i> los programas reciben
una excelente gesti&oacute;n de memoria y un alto rendimiento en los accesos
a disco, liberando al administrador del sistema del trabajo de ajustar los
tama&ntilde;os de los cach&eacute;s.</li>
<li><b>M&oacute;dulos de compatibilidad</b> que permiten la ejecuci&oacute;n de
programas de otros sistemas operativos en FreeBSD, incluyendo programas para
Linux, SCO, NetBSD y BSDI.
<p><i>Resultado:</i>&nbsp;los usuarios no tendr&aacute;n que recompilar
programas ya compilados para algunos de los sistemas compatibles, teniendo
acceso a programas como las extensiones para BSDI de
<a href="http://www.microsoft.com/FrontPage/">Microsoft FrontPage Server</a> o
<a href="http://www.corel.com/products/unix/wpunix/index.htm">WordPerfect</a>
para SCO y Linux.</LI>
<li><b>M&oacute;dulos de kernel de carga din&aacute;mica</b> que permiten
tener acceso a nuevos sistemas de ficheros, protocolos de red o emuladores
de binarios en tiempo de ejecuci&oacute;n sin necesidad de generar un
nuevo kernel. <p><i>Resultado:</i> Se puede ganar mucho tiempo y
desarrolladores de terceras partes pueden ofrecer subsistemas completos
como m&oacute;dulos de kernel sin necesidad de distribuir el c&oacute;digo
fuente o complejos procedimientos de instalaci&oacute;n.</li>
<li><b>Librer&iacute;as compartidas</b> reducen el tama&ntilde;o de los
programas, ahorrando espacio de disco y memoria. FreeBSD usa un avanzado
esquema de librer&iacute;as compartidas que ofrecen muchas de las ventajas
de ELF, ofreciendo la versi&oacute;n actual compatibilidad ELF con
programas de Linux y nativos de FreeBSD.</li>
</ul>
<p>Naturalmente, c&oacute;mo FreeBSD es un esfuerzo en constante
evoluci&oacute;n, puedes esperar nuevas caracter&iacute;sticas y niveles
m&aacute;s altos de estabilidad con cada release.</p>
</blockquote>
<H2>Lo que dicen los expertos . . .</H2>
<blockquote>
<P><I>``FreeBSD has an outline-structured visual configuration editor ...
you can enter the configuration of every device the OS supports and can
therefore get a successful installation on the first try almost every time.
IBM, Microsoft, and others would do well to emulate FreeBSD's approach.''</I></P>
<DIV ALIGN=right><P>---Brett Glass, <I>Infoworld</I>, April 8 1996.</P></DIV>
</blockquote>
&footer;
</BODY>
</HTML>

61
es/includes.sgml Normal file
View file

@ -0,0 +1,61 @@
<!-- $Id: includes.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<!--
Base is the absolute URL for the given page, minus the actual page
part. It should either be specified as a fully qualified URL, or
relative to the server root. It should be defined in the prolog
<em>before</em> including this file if the page does not live at the
default location below.
When making a link, use <a href="&base/mypage.html">foo</a> and
&base will be expanded appropriately. Base is also used in the
definition of standard boilerplate entities in this file, so be sure
base is correct!
-->
<!ENTITY base CDATA ".">
<!-- Images -->
<!ENTITY i.daemon '<img src="&base/../gifs/daemon.gif" alt="" align=left width="80" height="76">'>
<!ENTITY i.new '<img src="&base/../gifs/new.gif" alt="[New!]" width="28" height="11">'>
<!-- Components making up the standard headers and footers. -->
<!-- Override in the prolog <em>before</em> including this -->
<!-- file if necessary. -->
<!ENTITY copyright 'Copyright &#169; 1995-1998 FreeBSD Inc.
All rights reserved.'>
<!ENTITY email 'freebsd-questions'>
<!ENTITY author '<a href="&base/mailto.html">&email@FreeBSD.ORG</a><br>
&copyright;'>
<!ENTITY date ''>
<!ENTITY home '<a href="&base/"><img src="&base/../gifs/home.gif"
alt="FreeBSD Home Page" border="0" align="right" width="101" height="33"></a>'>
<!-- Standard headers and footers -->
<!ENTITY header '<head><title>&title;</title></head><BODY
TEXT="#000000" BGCOLOR="#FFFFFF" ALINK="#FFCC33"><IMG
SRC="&base/../gifs/bar.gif" ALT="Navigation Bar" WIDTH="565" HEIGHT="33" BORDER=0 usemap="#bar">
<H1 ALIGN=LEFT><FONT COLOR="#660000">&title;</FONT></H1><br clear=all>
<map name="bar">
<area shape="rect" coords="1,1,111,31" href="&base/index.html" ALT="Top">
<area shape="rect" coords="112,11,196,31" href="&base/ports/index.html" ALT="Aplicaciones">
<area shape="rect" coords="196,12,257,33" href="&base/support.html" ALT="Soporte">
<area shape="rect" coords="256,12,365,33" href="&base/docs.html" ALT="Documentacion">
<area shape="rect" coords="366,13,424,32" href="&base/../commercial/commercial.html" ALT="Comercial">
<area shape="rect" coords="425,16,475,32" href="&base/search/search.html" ALT="Buscar">
<area shape="rect" coords="477,16,516,33" href="&base/search/index-site.html" ALT="Indice">
<area shape="rect" coords="516,15,562,33" href="&base/index.html" ALT="Top">
<area shape="rect" href="&base/index.html" coords="0,0,564,32" ALT="Top">
</map>'>
<!ENTITY footer '<HR NOSHADE>
<address>&author;<br>&date;</address>'>
<!-- Short names for various anchor points -->
<!ENTITY a.latest.not '<a href="&base/releases/2.2.7R/notes.html">'>
<!ENTITY a.latest.ann '<a href="&base/releases/2.2.7R/announce.html">'>

332
es/index.sgml Normal file
View file

@ -0,0 +1,332 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "FreeBSD Inc.">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<html>
<head>
<title>FreeBSD Inc.</title>
<meta name="description" content="The FreeBSD Project">
<meta name="KEYWORDS" content="FreeBSD, BSD, UNIX, Support, Gallery,
Release, Application, Software, Handbook, FAQ, Tutorials, Bugs, CVS,
CVSup, News, Commercial Vendors, homepage, CTM, Unix">
</head>
<body bgcolor="#FFFFFF">
<table border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td><a href="http://www.FreeBSD.ORG"><img src="../gifs/freebsd_1.gif"
alt="FreeBSD: The Power to Serve" height="94" width="306"
border="0"></a></td>
<td align="right" valign="bottom" width="300">
<form action="http://www.freebsd.org/cgi/mirror.cgi" method="GET">
<br>
<font color="#990000"><b>Selecciona el servidor m&aacute;s
cercano</b></font>
<br>
<select name="goto">
<!-- Only list TRUE mirrrors here! Native language pages
which are not mirrored should be listed in
support.sgml. -->
<option value="http://www.au.freebsd.org/">Australia/1</option>
<option value="http://www2.au.freebsd.org/">Australia/2</option>
<option value="http://www3.au.freebsd.org/">Australia/3</option>
<option value="http://www.br.freebsd.org/www.freebsd.org/">Brazil/1</option>
<option value="http://www2.br.freebsd.org/www.freebsd.org/">Brazil/2</option>
<option value="http://www3.br.freebsd.org/">Brazil/3</option>
<option value="http://www.bg.freebsd.org">Bulgaria</option>
<option value="http://www.ca.freebsd.org/">Canada/1</option>
<option value="http://freebsd.kawartha.com/">Canada/2</option>
<option value="http://www.dk.freebsd.org">Denmark</option>
<option value="http://www.ee.freebsd.org/">Estonia</option>
<option value="http://www.fi.freebsd.org/">Finland</option>
<option value="http://www.fr.freebsd.org/">France</option>
<option value="http://www.de.freebsd.org/">Germany/1</option>
<option value="http://www1.de.freebsd.org/">Germany/2</option>
<option value="http://www2.de.freebsd.org/">Germany/3</option>
<option value="http://www.hu.freebsd.org/">Hungary</option>
<option value="http://www.is.freebsd.org/">Iceland</option>
<option value="http://www.ie.freebsd.org/">Ireland</option>
<!-- <option value="http://www.it.freebsd.org/">Italy</option> -->
<option value="http://www.jp.freebsd.org/www.freebsd.org/">Japan</option>
<option value="http://www.kr.freebsd.org/">Korea</option>
<option value="http://www.lv.freebsd.org/">Latvia</option>
<option value="http://rama.asiapac.net/freebsd/">Malaysia</option>
<option value="http://www.nl.freebsd.org/">Netherlands</option>
<option value="http://www.no.freebsd.org/">Norway</option>
<option value="http://www.pl.freebsd.org/">Poland</option>
<option value="http://www.pt.freebsd.org/">Portugal/1</option>
<option value="http://www2.pt.freebsd.org/">Portugal/2</option>
<option value="http://www3.pt.freebsd.org/">Portugal/3</option>
<option value="http://www.ro.freebsd.org/">Romania</option>
<option value="http://www.ru.freebsd.org/">Russia/1</option>
<option value="http://www2.ru.freebsd.org/">Russia/2</option>
<option value="http://www3.ru.freebsd.org/">Russia/3</option>
<option value="http://www.sk.freebsd.org/">Slovak Republic</option>
<option value="http://www.si.freebsd.org/">Slovenia</option>
<option value="http://www.es.freebsd.org/">Spain</option>
<option value="http://www.za.freebsd.org/">South Africa/1</option>
<option value="http://www2.za.freebsd.org/">South Africa/2</option>
<option value="http://www.se.freebsd.org/">Sweden</option>
<!-- XXX --><option value="http://www.tw.freebsd.org/freebsd.html">Taiwan</option>
<option value="http://www.tr.freebsd.org/">Turkey</option>
<option value="http://www.ua.freebsd.org/">Ukraine/1</option>
<option value="http://www2.ua.freebsd.org/">Ukraine/2</option>
<option value="http://www.uk.freebsd.org/">United Kingdom</option>
<option value="http://www.freebsd.org/">USA/California</option>
<option value="http://freebsd.advansys.net">USA/Indiana</option>
<option value="http://www6.freebsd.org/">USA/Oregon</option>
<option value="http://www2.freebsd.org/">USA/Texas</option>
</select>
<input type="submit" value=" Ir ">
<br>
<font color="#990000"><b>Language:</b></font> <a
href="ja/">Japon&eacute;s</a>, <a href="support.html#web">Otros</a>
</form>
</td>
</tr>
</table>
<br>
<table border="0" cellspacing="0" cellpadding="2">
<tbody>
<tr>
<!-- Red strip down left hand of sidebar -->
<td rowspan="2" bgcolor="#990000">&#160;</td>
<td bgcolor="#ffcc66">&#160;</td>
<td bgcolor="#ffffff">&#160;</td>
<td rowspan="2" align="left" valign="top" width="500">
<h2><font color="#990000">Qu&eacute; es FreeBSD?</font></h2>
<p>FreeBSD es un avanzado sistema operativo BSD UNIX para
ordenadores "PC-compatibles", desarrollado y mantenido por
un <a href="&base;/handbook/staff.html"> gran equipo de
personas</a>.</p>
<h2><font color="#990000">Caracter&iacute;sticas</font></h2>
<p>FreeBSD ofrece muy altas <a href="&base;/features.html">
prestaciones</a> en networking, rendimiento,seguridad y
compatibilidad, las cuales no est&aacute;n a&uacute;n presentes
en otros sistemas operativos, incluyendo los comerciales de
mayor renombre.</p>
<h2><font color="#990000">Potentes Soluciones Internet</font></h2>
<p>FreeBSD es el servidor ideal para
<a href="&base;/internet.html">Internet o Intranet</a>. Provee
de robustos servicios de red, incluso en situaciones de alta
carga, haciendo un uso eficiente de la memoria para mantener
buenos tiempos de respuesta con cientos o miles de procesos
simult&aacute;neos de usuarios. Visita nuestra
<a href="../gallery/gallery.html"> galer&iacute;a</a> para ver
ejemplos de aplicaciones y servicios ofrecidos por FreeBSD.</p>
<h2><font color="#990000">Ejecuta una gran variedad de
aplicaciones</font></h2>
<p>La calidad de FreeBSD combinada con el hoy en d&iacute;a bajo
coste del hardware de alta velocidad para PC's hace de este
sistema una alternativa muy econ&oacute;mica sobre las estaciones
de trabajo UNIX comerciales. Existe gran cantidad de
<a href="&base;/applications.html">aplicaciones</a> tanto a nivel
servidor como usuario.</p>
<h2><font color="#990000">F&aacute;cil de instalar</font></h2>
<p>FreeBSD puede ser instalado desde una gran variedad de soportes
incluyendo CD-ROM, floppies, cintas magn&eacute;ticas, una
partici&oacute;n MS-DOS o si tienes una conexi&oacute;n de red,
puedes instalarlo <i>directamente</i> sobre FTP an&oacute;nimo o
NFS. Todo lo que necesitas es un simple disquete de 1.44MB de
arranque y <a href="&base;/handbook/install.html">estas
instrucciones</a>.</p>
<h2><font color="#990000">FreeBSD es <i>libre</i></font></h2>
<a href="copyright/daemon.html"><img src="../gifs/dae_up2.gif" alt=""
height="81" width="72" align="right" border="0"></a>
<p>Si esperabas que un sistema operativo con estas
caracter&iacute;sticas tuviese un alto coste, FreeBSD est&aacute;
disponible totalmente gratis incluyendo todo el c&oacute;digo
fuente. Si quieres probarlo, <a href="&base;/availability.html">
aqu&iacute; tienes m&aacute;s informaci&oacute;n</a>.</p>
<br>
<table border="3" cellspacing="0" cellpadding="5">
<tbody>
<tr>
<td>Para aprender m&aacute;s sobre FreeBSD,
reg&iacute;strate para recibir la <a
href="&base;/register.html">FreeBSD Newsletter</a>,
visita nuestra galer&iacute;a de <a
href="&base;/publish.html">publicaciones</a> relacionadas
con FreeBSD o <a
href="news/press.html">FreeBSD en la prensa</a>, y
navega a trav&eacute;s de este website!.</td>
</tr>
</tbody>
</table>
</td>
</tr>
<tr>
<td align="left" valign="top" bgcolor="#ffcc66">
<p><big><font color="#990000"><b>Noticias</b></font></big>
<small><br>
&nbsp;&nbsp;<a
href="news/newsflash.html">Anuncios</a><br>
&nbsp;&nbsp;<a href="news/press.html">En la Prensa</a><br>
&nbsp;&nbsp;<a href="news/news.html">M&aacute;s...</a>
</small></p>
<p><big><font color="#990000"><b>Software</b></font></big>
<small><br>
&nbsp;&nbsp;<a href="handbook/install.html">Obtener FreeBSD</a><br>
&nbsp;&nbsp;<a href="releases/">Informaci&oacute;n Release</a><br>
&nbsp;&nbsp;<a href="&base;/ports/">Aplicaciones portadas</a><br>
</small></p>
<p><big><font color="#990000"><b>Documentaci&oacute;n</b></font>
</big>
<small><br>
&nbsp;&nbsp;<a href="doc-es/index.html">FreeBSD en
castellano</a><br>
&nbsp;&nbsp;<a href="projects/newbies.html">Para principiantes
</a><br>
&nbsp;&nbsp;<a href="&base;/handbook/handbook.html">Handbook
</a><br>
&nbsp;&nbsp;<a href="tutorials/">Tutoriales</a><br>
&nbsp;&nbsp;<a href="&base;/FAQ/FAQ.html">FAQ</a><br>
&nbsp;&nbsp;<a href="handbook/bibliography.html">Libros</a><br>
&nbsp;&nbsp;<a href="y2kbug.html">A&ntilde;o 2000</a><br>
&nbsp;&nbsp;<a href="docs.html">M&aacute;s...</a><br>
</small></p>
<p><big><font color="#990000"><b>Soporte</b></font></big>
<small><br>
&nbsp;&nbsp;<a href="&base;/support.html#mailing-list">Listas
de distribuci&oacute;n</a><br>
&nbsp;&nbsp;<a href="&base;/support.html#newsgroups">Grupos de
News</a><br>
&nbsp;&nbsp;<a href="&base;/support.html#user">Grupos de
usuarios</a><br>
&nbsp;&nbsp;<a href="&base;/support.html#web">Recursos Web</a>
<br>
&nbsp;&nbsp;<a href="security/security.html">Seguridad</a><br>
&nbsp;&nbsp;<a href="&base;/support.html">M&aacute;s...</a>
</small></p>
<p><big><font color="#990000"><b>Desarrollo</b></font></big>
<small><br>
&nbsp;&nbsp;<a href="projects/projects.html">Proyectos</a><br>
&nbsp;&nbsp;<a href="&base;/support.html#gnats">Informe de
Bugs</a><br>
&nbsp;&nbsp;<a href="&base;/support.html#cvs">Sistema CVS</a>
<br>
</small></p>
<p><big><font color="#990000"><b>Comercial</b></font></big>
<small><br>
&nbsp;&nbsp;<a href="&base;/../commercial/software.html">Software
</a><br>
&nbsp;&nbsp;<a href="&base;/../commercial/hardware.html">Hardware
</a><br>
&nbsp;&nbsp;<a href="&base;/../commercial/consulting.html">Consultor&iacute;a</a><br>
&nbsp;&nbsp;<a href="&base;/../commercial/misc.html">Varios</a><br>
</small></p>
<p><big><font color="#990000"><b>Este Web</b></font></big>
<small><br>
&nbsp;&nbsp;<a href="&base;/search/index-site.html">Mapa del Web</a><br>
&nbsp;&nbsp;<a href="&base;/search/search.html">Buscar</a><br>
&nbsp;&nbsp;<a href="copyright/copyright.html">Copyright</a><br>
&nbsp;&nbsp;<a href="mailto.html">Contactar con nosotros</a><br>
&nbsp;&nbsp;<a href="internal/internal.html">M&aacute;s...</a><br>
</small></p>
<form action="http://www.freebsd.org/cgi/search.cgi" method="get">
<small>&nbsp;&nbsp;Buscar:<br>
<input type="text" name="words" size="10">
<input type="hidden" name="max" value="25">
<input type="hidden" name="source" value="www">
<input type="submit" value="Buscar"></small>
</form>
</td>
</tr>
</tbody>
</table>
<hr>
<table border="0" cellspacing="0" cellpadding="3">
<tbody>
<tr>
<td><a href="http://www.freebsdmall.com/"><img
src="../gifs/mall_title_medium.gif" alt="[FreeBSD Mall]"
height="65" width="165" border="0"></a></td>
<td><a href="http://www.cdrom.com/"><img src="../gifs/wclogo.gif"
alt="[Sponsored by Walnut Creek CD-ROM]" height="55" width="88"
border="0"></a></td>
<td><a href="http://www.ugu.com/"><img src="../gifs/ugu_icon.gif"
alt="[Sponsor of Unix Guru Universe]" height="64" width="76"
border="0"></a></td>
<td><a href="http://www.apache.org/"><img src="../gifs/apachepower.gif"
alt="[Powered by Apache]" height="40" width="148"
border="0"></a></td>
<td><a href="&base;/copyright/daemon.html"><img
src="../gifs/powerlogo.gif" alt="[Powered by FreeBSD]"
height="64" width="171" border="0"></a></td>
</tr>
</tbody>
</table>
<p><small><a href="news/webchanges.html">Los cambios en el web</a> se realizan a las 0400 PDT cada d&iacute;a.</small></p>
<hr>
<table width="100%" cellpadding="0" border="0" cellspacing="0">
<tbody>
<tr>
<td align="left" valign="top"><small><a
href="&base;/mailto.html">Contactar con nosotros</a><br>
$Date: 1999-02-08 19:26:11 $</small></td>
<td align="right" valign="top"><small>Copyright &copy; 1995-1998
FreeBSD Inc.<br>
All rights reserved.</small></td>
</tr>
</tbody>
</table>
</body>
</html>

33
es/internal/Makefile Normal file
View file

@ -0,0 +1,33 @@
# $Id: Makefile,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
DOCS= photos.sgml
DOCS+= internal.sgml
DOCS+= about.sgml
DOCS+= machines.sgml
DOCS+= mirror.sgml
DOCS+= resignation.sgml
DOCS+= statistic.sgml
INDEXLINK= internal.html
# build the list of personal homepages of FreeBSD developers only
# on the main FreeBSD machines
hostname!= hostname
.if ${hostname} == "hub.freebsd.org" || ${hostname} == "freefall.freebsd.org"
DOCS+= homepage.sgml
.PHONY: homepage.inc
homepage.inc:
perl homepage.pl > ${.TARGET}
homepage.sgml: homepage.inc
CLEANFILES+= homepage.inc
.endif
DATA+= README.mirror
.include "../web.mk"

33
es/internal/README.mirror Normal file
View file

@ -0,0 +1,33 @@
Puedes (y te animamos) a mantener mirrors o replicas de las paginas
con CVSUP. Si estas usando Apache instalado desde la coleccion de
ports, los comandos siguientes deberian bastar para hacer una copia
de www.freebsd.org desde http://wwwN.XX.freebsd.org/. Por supuesto,
pueden haber variaciones en el metodo...
1) El fichero CVSup para obtener las paginas WWW
(/usr/local/www/data/freebsd.cvsup en el siguiente paso):
www release=current host=cvsup.freebsd.org hostbase=/home base=/usr prefix=/usr/local/www/data/www.freebsd.org delete old use-rel-suffix
2) Anyadir a /etc/crontab
1 5 * * * root /usr/local/bin/cvsup -z -g /usr/local/www/data/freebsd.cvsup
2) Anyade esto al fichero /usr/local/etc/apache/access.conf:
<Directory /usr/local/www/data/www.freebsd.org/data>
Options FollowSymLinks Includes
XBitHack Full
</Directory>
3) Anyade esto al fichero /usr/local/etc/apache/httpd.conf:
<VirtualHost wwwN.XX.freebsd.org>
UserDir disabled
ServerAdmin webmaster@wwwN.XX.freebsd.org
DocumentRoot /usr/local/www/data/www.freebsd.org/data
ServerName wwwN.XX.freebsd.org
ScriptAlias /cgi/ /usr/local/www/data/www.freebsd.org/data/cgi/
ErrorLog /var/log/wwwN.XX-error.log
TransferLog /var/log/wwwN.XX-access.log
</VirtualHost>

93
es/internal/about.sgml Normal file
View file

@ -0,0 +1,93 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Sobre el servidor WWW de FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: about.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<h2>La M&aacute;quina</h2>
<img src="../gifs/powerlogo.gif" alt="" align="right"> <p>La
m&aacute;quina, <tt>www.freebsd.org</tt>, tambi&eacute;n conocida
como <tt>freefall.freebsd.org</tt>, es un Pentium Pro 400Mhz con
una placa base PCI, 256 Mb de RAM y 4Gb de disco duro. El sistema
de b&uacute;squeda de p&aacute;ginas y listas de distribuci&oacute;n
es <tt>hub.freebsd.org</tt>, un Pentium II a 400Mhz con 256Mb de RAM
y 10Gb de disco.
<p>
Naturalmente, el sistema se ejecuta sobre el sistema operativo
FreeBSD. El hardware y la conectividad han sido generosamente
donados por <a
href="http://www.cdrom.com/">Walnut Creek CDROM</a>.</p>
<p>Una lista completa de todas las m&aacute;quinas en el dominio
FreeBSD.org esta disponible en la p&aacute;gina de
<a href="machines.html">La Red FreeBSD.org</a>.
</p>
<h2>El Software</h2>
<img src="../gifs/apachepower.gif" alt="" align="right"><p>
Estas p&aacute;ginas son servidas por el vers&aacute;til y eficiente
<a href="http://www.apache.org/">servidor http APACHE</a>. Adem&aacute;s
se han incluido una serie de scripts CGI. La indexaci&oacute;n de
estas p&aacute;ginas y el archivo de las listas de distribuci&oacute;n
se hacen mediante freewais-sf, un derivado del freewais CNIDR.</p>
<img src="http://www.quantified.com/images/gourchin3.gif" alt=""
align="right"><p>El paquete estad&iacute;stico
<a href="http://www.quantified.com/urchin/support/">Urchin</a> es usado
para realizar <a href="http://www.freebsd.org/statistic/urchin/">
estas estad&iacute;sticas</a> sobre el uso del servidor web.</p>
<h2>Las P&aacute;ginas</h2>
<img src="../gifs/lynx.gif" alt="" align="right">
<p>Estas p&aacute;ginas han sido creadas por John Fieber <a
href="http://www.freebsd.org/~jfieber/">&lt;jfieber@freebsd.org&gt;</a>
con participaci&oacute;n de la comunidad FreeBSD y <b>t&uacute;</b>.
El Webmaster es <a href="http://www.freebsd.org/~wosch/">
&lt;wosch@freebsd.org&gt;</a>.
Las p&aacute;ginas de FreeBSD cumplen la normativa HTML 3.2 y son mejor
vistas con tu navegador.</p>
Consulta tambi&eacute;n el <a href="../docproj/docproj.html">
Proyecto de Documentaci&oacute;n de FreeBSD</a>.
<h2>Dise&ntilde;o</h2>
<p>
El dise&ntilde;o original es de <A HREF="http://www.asis.com/~meganm/">
Megan McCormack</A>
</p>
<h2>Paquetes ping bloqueados</h2>
<p>
Nuestro proveedor <a href="http://www.crl.net/">CRL</a> est&aacute;
bloqueando todo el tr&aacute;fico ICMP.
</p>
<h2>Actualizaci&oacute;n de las p&aacute;ginas Web de FreeBSD</h2>
<p>
Las p&aacute;ginas Web de FreeBSD son actualizadas diariamente
a las 04:00 PDT (UTC -07:00).
</p>
<h2>Mirroring del Web de FreeBSD</h2>
<p>Puedes (y te animamos) a hacer <a href="mirror.html">mirror</a>
del web www.freebsd.org.</p>
<p>Las <a href="statistic.html#analog">
estad&iacute;sticas de uso</a> de este servidor se actualizan diariamente.
<p></p><A HREF="internal.html">FreeBSD Internal Home</a>
&footer;
</body>
</html>

50
es/internal/homepage.pl Normal file
View file

@ -0,0 +1,50 @@
#!/usr/bin/perl
$passwd = '/etc/passwd';
$homepagedir = 'public_html';
@index = ('index.html', 'index.cgi');
$noindex = '.noindex';
open(P, $passwd) || die "open $passwd: $!\n";
undef @pages;
while(<P>) {
($login,$passwd,$uid,$gid,$gcos,$home,$shell) = split(/:/);
# cleanup gecos
$gcos =~ s/,.*//;
# disable daemons
next if $uid <= 100;
next if $login eq 'nobody';
next if $shell =~ ~ m%/(pppd|sliplogin|nologin|nonexistent)$%;
# uucp accounts
next if $login =~ /^U/;
$p = $home . '/' . $homepagedir;
# user don't want be on the index
next if -f "$p/$noindex";
foreach (@index) {
if (-f "$p/$_" && -r "$p/$_") {
if ($_ !~ /\.cgi$/ || -x "$p/$_") {
push(@pages, $gcos . ':' . $login);
last;
}
}
}
}
close P;
if ($#pages < 0) {
die "No users found!\n";
}
foreach (sort @pages) {
($gcos, $login) = split(/:/);
($firstgecos, @gecos) = split(/,/, $gcos);
print qq{<LI><A HREF="http://www.freebsd.org/~$login/">},
$firstgecos, "</A> ", join(', ', @gecos), "</LI>\n";
}

20
es/internal/homepage.sgml Normal file
View file

@ -0,0 +1,20 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "P&aacute;ginas Personales en FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY homepage SYSTEM "homepage.inc">
]>
<!-- $Id: homepage.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<ol>
&homepage;
</ol>
<p></p><A HREF="internal.html">FreeBSD Internal Home</a>
&footer;
</body>
</html>

58
es/internal/internal.sgml Normal file
View file

@ -0,0 +1,58 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "FreeBSD por dentro">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: internal.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p></p>
<h2><a href="machines.html">La red FreeBSD.org</a></h2>
<p>Esta p&aacute;gina describe, para aquellos con cuentas de acceso en la
red FreeBSD.org, las m&aacute;quinas y recursos actualmente disponibles y
el tipo de tarea que realiza cada una de ellas.</p>
<h2><a href="about.html">Sobre el servidor WWW de FreeBSD</a></h2>
<p>La m&aacute;quina, el software, r&eacute;plicas de las p&aacute;ginas
Web, estad&iacute;sticas de uso.</p>
<h2><a href="../handbook/staff.html">Staff del proyecto FreeBSD</a></h2>
<p>El proyecto FreeBSD est&aacute; comandado y operado por los siguientes
grupos de gente: FreeBSD Core Team, Desarrolladores de FreeBSD.</p>
<h2><a href="photos.html">Fotos de Eventos Sociales</a></h2>
<h2><a href="http://www.freebsd.org/internal/homepage.html">P&aacute;ginas
personales</a></h2>
<p>Una lista de p&aacute;ginas personales mantenidas en www.freebsd.org.</p>
<h2><a href="../projects/projects.html">Proyectos de FreeBSD</a></h2
<p>Sum&aacute;andose a los desarrollos principales realizados por FreeBSD,
existen diferentes grupos de desarrolladores trabajando en la expansi&oacute;n
de las posibilidades de FreeBSD en otras direcciones.<p>
<h2><a href="../mailto.html">Contactar con FreeBSD</a></h2>
<h2><a href="../copyright/license.html">Copyright de FreeBSD</a></h2>
The FreeBSD Copyright(s).
<h2><a href="../search/search.html">Buscar en el servidor de FreeBSD</a></h2>
<p>Servicios de b&uacute;squedas de FreeBSD.</p>
<h2><a href="statistic.html">Estad&iacute;sticas de FreeBSD</a></h2>
<p>Estad&iacute;sticas de tr&aacute;fico Web, tr&aacute;fico FTP, uso de
Releases.</p>
&footer;
</body>
</html>

170
es/internal/machines.sgml Normal file
View file

@ -0,0 +1,170 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "La red FreeBSD.org">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: machines.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>Esta p&aacute;gina describe, para aquellos con cuentas de acceso en la
red FreeBSD.org, las m&aacute;quinas y recursos actualmente disponibles y
el tipo de tarea que realiza cada una de ellas.</p>
<h2>Todos los nombres de m&aacute;quinas en el dominio FreeBSD.org</h2>
<table width="100%">
<tr>
<th align="left">M&aacute;quina</th>
<th align="left">S.O.</th>
<th align="left">Objetivo</th>
<th align="left">Administrador(es)</th>
</tr>
<tr>
<td>builder</td>
<td>2.2.6-stable</td>
<td>Build server</td>
<td>admins</td>
</tr>
<tr>
<td>beast</td>
<td>3.0-current</td>
<td>Alpha box for FreeBSD/alpha testing</td>
<td>jkh</td>
</tr>
<tr>
<td>bento</td>
<td>3.0-current</td>
<td>3.0-current package building</td>
<td>ports team</td>
</tr>
<tr>
<td>freefall</td>
<td>2.2.6-stable</td>
<td>CVS master repository</td>
<td>committers</td>
</tr>
<tr>
<td>hub</td>
<td>2.2.6-stable</td>
<td>Mail & WWW services, tape changer</td>
<td>post/webmaster</td>
</tr>
<tr>
<td>kickme</td>
<td>3.0-current</td>
<td>Bleeding edge testing</td>
<td>open</td>
</tr>
<tr>
<td>paddock</td>
<td>2.2.6-stable</td>
<td>2.2.x-stable package building</td>
<td>ports team</td>
</tr>
</table>
<h2>COnfiguraciones Hardware</h2>
<table width="100%">
<tr>
<th align="left">M&aacute;quina</th>
<th align="left">Tipo</th>
<th align="left">Hardware</th>
</tr>
<tr valign="top">
<td>builder</td>
<td>Intel x86</td>
<td>200Mhz Pentium Pro, 128MB mem, AHC 2940 PCI SCSI controller, 2GB Quantum
SCSI drive, 3GB IDE drive, Intel EtherExpress Pro 10/100B NIC.</td>
</tr>
<tr valign="top">
<td>beast</td>
<td>Alpha Durango</td>
<td> 500MHz 21164A on DEC PCI64 MB, 128MB mem, NCR 53c875 SCSI
controller, 2x4GB SCSI WIDE drives (one NetBSD/alpha, one
FreeBSD/alpha), DEC 21140 NIC.</td>
</tr>
<tr valign="top">
<td>bento</td>
<td>Intel x86 MP</td>
<td>2x300MHz Pentium II, 128MB mem, AHC 2940 PCI SCSI controller,
5x4GB SCSI WIDE drives, Intel EtherExpress Pro 10/100B NIC.</td>
</tr>
<tr valign="top">
<td>freefall</td>
<td>Intel x86</td>
<td>400MHz Pentium II, 256MB mem, NCR 53c875 PCI SCSI
controller, 4x4GB SCSI WIDE drives, Intel EtherExpress Pro
10/100B NIC.</td>
</tr>
<tr valign="top">
<td>hub</td>
<td>Intel x86</td>
<td>400MHz Pentium II, 256MB mem, AHC 2940 PCI SCSI controller,
3x4GB SCSI WIDE drives, HP 6020i CDR, Intel EtherExpress Pro
10/100B NIC.</td>
</tr>
<tr valign="top">
<td>kickme</td>
<td>AMD x86</td>
<td>187MHz K6, 64MB mem, AHC 2940 PCI SCSI controller, 4 GB SCSI
WIDE, 2GB SCSI drives, Archive Python 4-DAT changer drive,
Intel EtherExpress Pro 10/100B NIC.</td>
</tr>
<tr valign="top">
<td>paddock</td>
<td>Intel x86</td>
<td>200MHz Pentium Pro, 32MB mem, AHC 7880 on-board SCSI
controller, 9GB SCSI WIDE drive, on-board Intel EtherExpress Pro
10/100B.</td>
</tr>
</table>
<p>Como regla general, todas las m&aacute;quinas est&aacute:n conectadas
a 100Mbits a la red FreeBSD (switch de 100Mbit), a no ser que por alguna
raz&oacute;n determinada, se deba conectar a 10Mbits.</p>
<h2>Pil&iacute;ticas Administrativas</h2>
<p>Si la m&aacute;quina en cuesti&oacute;n es administrada por alguna
persona determinada, por favor, preg&uacute;ntale primero a ellos sobre
temas administrativos, incluyendo cambios en las cuentas de usuario o en
los sistemas de ficheros.</p>
<p>Todas las nuevas cuentas deben ser aceptadas por el equipo de
administradores, <a href="mailto:admins@freebsd.org">admins@freebsd.org</a>
y solo se dan a desarrolladores de FreeBSD, ya sea en la documentaci&oacute;n,
ports o c&oacute;digo fuente del sistema. La &uacute;nica excepci&oacute;n a
esta regla es la m&aacute;quina de pruebas kickme.freebsd.org, para la cual
se podr&aacute;n conceder cuentas de acceso a desarrolladores no
pertenecientes a FreeBSD, pero que requieran de acceso a un sistema FreeBSD
para temas verdaderamente experimentales o muy espec&iacute;ficos. Las cuentas
no son concedidas al "p&uacute;blico en general", as&iacute; que por favor,
no preguntes. Gracias.</p>
<p>Jordan Hubbard<br>
<a href="mailto:jkh@freebsd.org">jkh@freebsd.org</a></p>
<p></p><A HREF="internal.html">FreeBSD Internal Home</a>
&footer;
</body>
</html>

64
es/internal/mirror.sgml Normal file
View file

@ -0,0 +1,64 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Mirrors de las p&aacute;ginas Web de FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: mirror.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>Puedes (y te animamos) a mantener mirrors o r&eacute;plicas de las
p&aacute;ginas web de <tt>www.freebsd.org</tt>.
Para hacerlo, necesitas obtener e instalar un programa llamado
<em>cvsup</em> en tu servidor web.
<a href="../handbook/cvsup.html">CVSup</a> es un software para
distribuci&oacute;n y actualizaci&oacute;n de colecciones de ficheros a
trav&eacute;s de una red.
<H2>Instalando CVSup</H2>
<p>Para instalarlo, haz lo siguiente:</p>
<pre>
# cd /usr/ports/net/cvsup-bin
# make all install clean
</pre>
<H2>Ejecutando CVSup</H2>
<p>Si mantienes las p&aacute;ginas replicadas de FreeBSD en el directorio
<tt>/usr/FreeBSD-mirror</tt> y pertenecen al usuario "fred", ejecuta el
siguiente comando como el usuario "fred":</p>
<pre>
$ cvsup supfile-www
</pre>
EL fichero <tt>supfile-www</tt> contiene:
<pre>
*default host=cvsup.FreeBSD.org
*default prefix=/usr/FreeBSD-mirror
*default base=/usr/local/etc/cvsup
www release=current delete use-rel-suffix compress
</pre>
<p>Esto mantendr&aacute;a una r&eacute;plica de las p&aacute;ginas de
FreeBSD en el directorio <tt>/usr/FreeBSD-mirror</tt>. Puedes instalar este
comando en el cron de "fred", de manera que se realice la actualizaci&oacute;n
diariamente de manera autom&aacute;tica. Los contenidos de web de FreeBSD son
actualizados diariamente a las 4:30am de California.</p>
<H2>M&aacute;s informaci&oacute;n sobre CVSup</H2>
See the <a href="../handbook/cvsup.html">Introducci&oacute;n a CVSup</a> en el
handbook.
<p></p><A HREF="internal.html">FreeBSD Internal Home</a>
&footer;
</body>
</html>

69
es/internal/photos.sgml Normal file
View file

@ -0,0 +1,69 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Galer&iacute;a de fotos">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: photos.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<h2><a href="http://www.freebsd.org/~nik/Oxford/index.html">Oxford (UK) FreeBSD meeting, November 1998</a></h2>
<p>Photos and text by <a href="mailto:nik@freebsd.org">Nik</a>. Organised
by Paul Richards.</p>
<h2>Dutch FreeBSD meeting, October 1998</h2>
Photos by <a href="http://www.freebsd.org/~jkh/holland/">Jordan</a> and
<a href="http://www.tcja.nl/hackersparty/">Wilko</a>
<h2><a href="http://www.de.freebsd.org/de/gif/hamburg-1998-06-20/index.html">
BSD Social Event Hamburg, June 1998</a></h2>
<p>
Aled Morris, Andre Oppermann, Andreas Klemm, Andrew Gordon, Christoph
Badura, Dirk Meyer, Frank Nobis, Harald Klatte, Joerg Wunsch, Jonathan
Laventhol, Lars Gerhard Kuehl, Martin Cracauer, Stefan Bethke, Stefan
Esser, Stefan Huerter, Stefan Zehl, Stephan Forth, Thomas Gellekum
</p>
<h2><a href="http://www.freebsd.org/~grog/usenix.html">
Summer 1998 USENIX, New Orleans</a></h2>
<p>
Branson, David Greenman, David O'Brien, Greg Lehey, Guido van Rooij,
John Polstra, Jonathan Bresler, Jordan Hubbard, Justin Gibbs, Luigi
Rizzo, Mark Murray, Mike Smith, Monique van Rooij, Ollivier Robert,
Philippe Regnauld, Poul-Henning Kamp, Sharon, Steve Mann
</p>
<h2><a href="http://www.de.freebsd.org/de/gif/aachen-19950902/">
FreeBSD Social Event Aachen, 1995</a></h2>
<p>
Aled Morris, Christoph Kukulies, Guido van Rooij, Jonathan Leventhol,
Jörg Wunsch, Martin Welk, Michael Reifenberger, Patrick Hausen, Paul
Richard, Paul Richards, Poul-Henning Kamp, René de Vries, Stefan
Esser, Ulf Kieber, Wilko Bulte
</p>
<h2><a href="http://www.freebsd.org/~jhs/freebsd/people.html">
FreeBSD People</a></h2>
<p>
Aled Morris, Andrey Chernov, Christoph Kukulies, Gary Jennejohn, Gary
Palmer, Guido Van Rooij, Guy Helmer, Hellmuth Michaelis, James
Robinson, Joerg Wunsch, John Fieber, Jon Loeliger, Jonathan Leventhol,
Jordan Hubbard, Julian Stacey, Mark Murray, Martin Welk, Michael
Reifenberger, Mike Smith, Ollivier Robert, Patrick Hausen, Paul
Richards, Paul Traina, Poul-Henning Kamp, Rene de Vries, Stefan Esser,
Thomas Gellekum, Timo Rinne, Ulf Kieber, Wilko Bulte, Wolfram
Schneider
</p>
<p></p><A HREF="internal.html">FreeBSD Internal Home</a>
&footer;
</body>
</html>

View file

@ -0,0 +1,73 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Jordan's Resignation Letter">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: resignation.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>This short notice is just to announce my resignation as President
of the FreeBSD Project, effective immediately, coinciding with the
elimination of that position.</p>
<p>This is entirely my own decision and was not prompted by anyone
on the core team - if anything, they will probably be as surprised
as anyone at the news (except for David & John D., with whom I've
already discussed the matter).</p>
<p>I do this for several reasons, all equally important:</p>
<ul>
<li><p>1. The position of President has always been somewhat at-odds with
our democratic core team structure and purely titular since to
give the president any real "power" would also destroy the carefully
balanced dynamic of core, and that would hardly be a desirable outcome.</p>
<p>The reason the position of "President" was originally created at all
was to give ISVs and other corporate contacts a more official-sounding
person to talk to, and while this has been valuable to a certain extent
I don't think that it's quite proven useful enough to justify the
further existance of the position. As it is, it only creates the
illusion of a "super core member", which the president is not, and
creates false expectations of authority.</p>
<li><p>2. The president is generally assumed to be talking for FreeBSD at all times,
depriving the wearer of that particular thorny crown of the right
to voice strong opinions or otherwise be outspoken without damaging
the reputation of the project. I'm not a punch-pulling kind of guy
(as you no-doubt already guessed) and I almost certainly never will be,
so it's time for me to have my own voice back and be able to talk to
people without it being taken as implicit that I'm somehow speaking
for all of core. If being "presidential" also means constantly
turning the other cheek then I'll never be presidential enough and it's
just not an adjustment I care to make (I'm not that kind of person) so
I should step down from that responsibility.<p>
<li><p>3. Dropping back to core team status will make it easier for me to
shed additional FreeBSD responsibilities, should I decide that I
need to do that in the future, and get some semblance of a life
back. I've been doing this for 4 years now and I'm tired. Just how
tired I will need to evaluate before making any further decisions, but at
least the burden of this artificial position will no longer be mine.
It will, in fact, be no ones' and I think this is a vast improvement.</p>
</ul>
<p>In discussions with David and John, it was also expressed that the
position was never really that popular with the core team and that
my stepping down should coincide with the complete elimination of
an unnecessary and somewhat flawed position, and so it will be.</p>
<p>So, as of now the FreeBSD Project now longer has a President. It is
run purely by the core team, as it always was in truth, and now
I'm just the PR guy, release engineer and plain old run-of-the-mill
core team member. As if that wasn't enough. :-)</p>
<p align=left>Jordan</p>
<p></p><A HREF="internal.html">FreeBSD Internal Home</a>
&footer
</body>
</html>

View file

@ -0,0 +1,64 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Estad&iacute;sticas de FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: statistic.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<h2>Estad&iacute;sticas Web</h2>
<a name="analog"></a>
<h4>Analog</h4>
analog(1) tool.
<p>Las <a href="http://www.freebsd.org/statistic/freefall.html">
estad&iacute;sticas de uso</a> de este servidor actualizadas
diariamente con la herramienta analog(1).
<a name="urchin"></a>
<h4>Urchin</h4>
<img src="http://www.quantified.com/images/gourchin3.gif" alt=""
align="right"><p>El paquete estad&iacute;stico <a
href="http://www.quantified.com/urchin/support/">Urchin</a> es
usado para crear <a
href="http://www.freebsd.org/statistic/urchin/">estas
estad&iacute;sticas</a> sobre el uso del servidor web.</p>
<a name="releasestatistic"></a>
<h2>Uso de releases de FreeBSD</h2>
<p>Una muestra del uso de la release actual de FreeBSD est&aacute;
disponible en
<a href="http://www.freebsd.org/statistic/release_usage/images/">
http://www.freebsd.org/statistic/release_usage/images/</a>.
</p>
<!-- from ../projects/projects.sgml -->
<h2>El contador de FreeBSD</h2>
<p>La p&aacute;gina
<a href="http://superior.mooseriver.com/FbsdCounter.html">The
FreeBSD Counter Page</a> es el comienzo de un proyecto con el
que se intenta determinar la base instalada a nivel mundial
de usuarios de FreeBSD.
<h2>Tr&aacute;fico FTP en ftp.freebsd.org</h2>
Hemos conseguido un nuevo record de tr&aacute;fico en
<a href="ftp://ftp.freebsd.org">wcarchive</a> el 2 de Diciembre de 1998,
763GB. La tarjeta fast ethernet estuvo a su uso m&aacute;ximo la mayor parte
del d&iacute;a.
<p></p><A HREF="internal.html">FreeBSD Internal Home</a>
&footer;
</body>
</html>

141
es/internet.sgml Normal file
View file

@ -0,0 +1,141 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Gesti&oacute;n de red de FreeBSD">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: internet.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<HTML>
&header;
<H1>FreeBSD fue dise&ntilde;ado para Internet</H1>
<blockquote><P>FreeBSD incluye lo que muchos consideran la
<i>implementac&oacute;n de referencia</i> de TCP/IP, el stack 4.4BSD del
protocolo TCP/IP, haciendolo ideal para aplicaciones de red e Interenet.
</P></blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">
FreeBSD soporta los protocolos estandar TCP/IP.</FONT></FONT>
<blockquote>
<p>Como muchos sistemas UNIX, el sistema operativo FreeBSD te permite</p>
<UL>
<LI>Compartir ficheros mediante NFS</LI>
<LI>Distribuci&oacute;n de informaci&oacute;n de red con NIS</LI>
<LI>Soporte de logins remotos</LI>
<LI>Gesti&oacute;n y configuraci&oacute;n remota v&iacute;a SNMP</LI>
<LI>Servidor de ficheros FTP</LI>
<LI>Resoluci&oacute;n de nombres de m&aacute;quinas con DNS/BIND</LI>
<li>Rutar paquetes entre m&uacute;ltiples interfaces, incluyendo
l&iacute;neas PPP y SLIP</li>
<LI>Servicios IP Multicast (MBONE)</LI>
</ul>
<p>FreeBSD te permite convertir un PC en un servidor World Wide Web o
servidor de news, con el software ya incluido. Usando el software incluido
SAMBA puedes compartir discos e impresoras con tus m&aacute;quinas Win95 y
NT, adem&aacute;s de soportar m&aacute;quinas con PC/NFS gracias al
daemon de autentificaci&oacute;n PCNFS. FreeBSD tambi&eacute;n soporta
los protocolos de red Appletalk y Novell en modo cliente/servidor, haciendo
de este sistema una verdadera soluci&oacute;n de servicios Intranet.</p>
<p>FreeBSD tambi&eacute;n gestiona extensiones TCP como la extensi&oacute;n de
alto rendimiento <A HREF="http://www.cis.ohio-state.edu/htbin/rfc/rfc1323.html">RFC-1323</A> y la extensi&oacute;n
<A HREF="http://www.cis.ohio-state.edu/htbin/rfc/rfc1644.html">RFC-1644</A>
para transacciones, adem&aacute;s de SLIP y PPP bajo demanda. Es un sistema
que responde a las expectativas tanto del usuario dom&eacute;stico como del
administrador de sistemas corporativo.</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">El
sistema de red de FreeBSD es r&aacute;pido y estable.</FONT></FONT>
<blockquote>
<p>Si necesitas una plataforma para servicios de Internet que ofrezca el
mejor rendimiento bajo fuertes cargas de trabajo, considera FreeBSD.
Aqu&iacute; est&aacute;n solo algunas de las compa&ntilde;&iacute;as que
usan FreeBSD diariamente:</p>
<UL>
<LI><A HREF="http://www.cdrom.com/">Walnut Creek CD-ROM</A> en las afueras
de San Francisco mantiene en funcionamiento uno de los
<A HREF="ftp://ftp.cdrom.com/">servidores FTP</A> m&aacute;s populares de
Internet, soportando 3600 conexiones simult&aacute;neas. Su servidor es una
&uacute;nica m&aacute;quina con FreeBSD transfiriendo m&aacute;s de 7
terabytes (en Noviembre de 1997); si son <i>terabytes</i>, cada mes. Los
<A HREF="ftp://ftp.cdrom.com/archive-info/wcarchive.txt">detalles de
configuraci&oacute;n</a> est&aacute;n disponibles para aquellos interesados
en sistemas similares.</li>
<li><A HREF="http://www.yahoo.com/">Yahoo Inc.</A> gestiona el &iacute;ndice
de Internet m&aacute;s usado, sirviendo enormes cantidades de
informaci&oacute;n diariamente a los usuarios de Internet. Yahoo, y las
compa&ntilde;&iacute;as que usan su buscador, utilizan FreeBSD como
plataforma de sus servidores Web.</li>
<li>Si esto no es suficiente, visita nuestra
<A HREF="&base/../gallery/gallery.html">galer&iacute;a</a> de usuarios
satisfechos con FreeBSD.</li>
</ul>
<p>FreeBSD es la plataforma ideal para estos y otros servicios de Internet:</p>
<ul>
<LI>Servicios WWW</LI>
<LI>Servicios Proxy WWW</LI>
<LI>Servicios de FTP</LI>
<LI>Servicios de ficheros e impresi&oacute;n</LI>
</ul>
<p>La <A HREF="&base/ports/index.html">colecci&oacute;n de ports</a> contiene
software listo para funcionar que hace m&aacute;s f&aacute;cil la
puesta en marcha de tus servidores de Interent.</p>
</blockquote>
<HR ALIGN=LEFT NOSHADE WIDTH="100%"><FONT COLOR="#FF0000"><FONT SIZE="+1">Alto
rendimiento <em>y</em> seguridad.</FONT></FONT>
<blockquote>
<p>El equipo de desarrollo de FreeBSD est&aacute; tan comprometido con la
seguridad como con el rendimiento. FreeBSD incluye en el kernel soporte de
firewall IP, adem&aacute;s de otros servicios como gateways e IP proxy. Si
conectas tu servidor corporativo en Internet, cualquier PC 386 (o superior)
funcionando con FreeBSD puede actuar como firewall de red para protegerte
de ataques externos.</p>
<p>Software de encriptaci&oacute;n, shells seguras, Kerberos,
encriptaci&oacute;n punto a punto y RPC seguro tambi&eacute;n est&aacute;n
disponibles (sujetas a restricciones de exportaci&oacute;n).</p>
<p>Adem&aacute;s, el equipo de FreeBSD est&aacute; continuamente investigando
y comunicando informaciones de seguridad con un
<a href="mailto:security-officer@FreeBSD.ORG">responsable de seguridad</a> y
el Computer Emergency Response Team (<A HREF="http://www.cert.org/">CERT</A>).
</P>
</blockquote>
<H2>Qu&eacute; dicen los expertos . . .</H2>
<blockquote>
<P><I>``FreeBSD ... provides what is probably the most robust and capable
TCP/IP stack in existence ...''</I></P>
<DIV ALIGN=right><P>---Michael O'Brien, <I>SunExpert </I>August 1996 volume
7 number 8.</P></DIV>
</blockquote>
&footer;
</BODY>
</HTML>

47
es/mailto.sgml Normal file
View file

@ -0,0 +1,47 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Contactando con FreeBSD">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: mailto.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<h2>Preguntas sobre FreeBSD...</h2>
<p>Las preguntas referentes a FreeBSD deber&iacute;an ser enviadas a la
lista de distribuci&oacute;n
<a href="mailto:freebsd-questions@FreeBSD.ORG">
freebsd-questions@FreeBSD.ORG</a>.</p>
<h2>Preguntas sobre el contenido de este servidor WWW...</h2>
<p>Las preguntas o sugerencia sobre nuestra documentaci&oacute;n,
(<a href="&base/handbook/">Handbook</a>, <a href="&base/FAQ/">FAQ</a> o
<a href="&base/tutorials/">Tutoriales</a>) deber&iacute;n ser enviadas a
los miembros del Proyecto de Documentaci&oacute;n de FreeBSD.
<a href="mailto:freebsd-doc@FreeBSD.ORG">freebsd-doc@FreeBSD.ORG</a>.</p>
<h2>Otras listas de distribuci&oacute;n de FreeBSD</h2>
<p>Las <a href="support.html#mailing-list">Listas de distribuci&oacute;n
</a> son el canal primario de soporte de los usuarios de FreeBSD, con
numerosas listas cubriendo diferentes &aacute;reas. Diferentes listas
no inglesas est&aacute;n disponibles.</p>
<h2>Correo, tel&eacute;fono y fax</h2>
For CDROM orders:
<a href="http://www.cdrom.com/info/contact.htm">
Walnut Creek CDROM</a><br>
Para soporte comercial:
<a href="http://www.freebsdmall.com/contact/">
The FreeBSD Mall</a><br>
<h2><a href="handbook/staff:who.html">Qui&eacute;n es responsable de
qu&eacute;</a></h2>
<p></p>
&footer;
</body>
</html>

28
es/news/Makefile Normal file
View file

@ -0,0 +1,28 @@
# $Id: Makefile,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
.if exists("../Makefile.conf")
.include "../Makefile.conf"
.endif
# quick news letter
DOCS= qnewsletter.sgml
DOCS+= qnewsletter-1-1.sgml
DOCS+= qnewsletter-1-2.sgml
DOCS+= qnewsletter-1-3.sgml
DOCS+= qnewsletter-1-4.sgml
DOCS+= qnewsletter-1-5.sgml
DOCS+= qnewsletter-1-6.sgml
DOCS+= qnewsletter-1-7.sgml
DOCS+= press.sgml
DOCS+= newsflash.sgml
DOCS+= news.sgml
DOCS+= webchanges.sgml
INDEXLINK= news.html
.include "../web.mk"

9
es/news/clickable.pl Executable file
View file

@ -0,0 +1,9 @@
#!/usr/bin/perl -np
# Copyright (c) Juli 1998 Wolfram Schneider <wosch@FreeBSD.org>. Berlin.
#
# clickable - Make URL clickable
#
# $Id: clickable.pl,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
s/</&lt;/g;
s%((http|ftp)://[^\s"\)\>,;]+)%<A HREF="$1">$1</A>%gi;

41
es/news/includes.sgml Normal file
View file

@ -0,0 +1,41 @@
<!-- $Id: includes.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<!ENTITY newshome '<A HREF="news.html">News Home</A>'>
<!-- Quick NewsLetter -->
<!ENTITY qnewsletterhome '| <A HREF="qnewsletter.html">Quick NewsLetter Home</A>'>
<!ENTITY qnewsletterprev '<A HREF="&qnlprev">Anterior Quick NewsLetter</A>'>
<!ENTITY qnewsletternext '<A HREF="&qnlnext">Pr&oacute;xima Quick NewsLetter</A>'>
<!ENTITY qnewsletterheader '
<p align="center">
FreeBSD Really-Quick(TM) NewsLetter.<br>
Things Happening in FreeBSD.<br>
Volume #&volume Issue #&issue<br>
&month; &year;<br>
</p>
<p></p>
'>
<!ENTITY qnewsletterfooter '
<p>
<HR>
Esta es una (al menos) Newsletter mensual, publicada s&oacute;lo por E-mail.
Copias archivadas pueden encontrarse en:
<A HREF="qnewsletter.html">http://www.freebsd.org/news/qnewsletter.html</A>
<p>
Si tienes cualquier cosa que te gustar&iacute;a ver en la pr&oacute;xima
edici&oacute;n, por favor, env&iacute; un e-mail a
<A HREF="mailto:fbsd-book@vmunix.com">fbsd-book@vmunix.com</a>
<p</p>
<p align="center">
-Chris Coleman &lt;chrisc@vmunix.com>
</p>
<p></p>
'>

37
es/news/news.sgml Normal file
View file

@ -0,0 +1,37 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Noticias FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: news.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p></p>
<h2><a href="newsflash.html">FreeBSD Newsflash</a></h2>
<p>Qu&eacute; es nuevo.</p>
<h2><a href="qnewsletter.html">The FreeBSD Quick NewsLetter</a></h2>
FreeBSD Really-Quick(TM) NewsLetter. Cosas que ocurren en FreeBSD.
<h2><a href="press.html">FreeBSD en la Prensa</a></h2>
<p>La prensa sobre FreeBSD.</p>
<h2><a href="webchanges.html">Cambios en el servidor web de FreeBSD</a></h2>
<p></p>
<h2><A HREF="../publish.html#newsletter">Newsletter</A></h2>
<p>FreeBSD Newsletter.</p>
<h2><a href="http://www.daemonnews.org/">Daemon News</a></h2>
<p>El l&iacute;der en la industria de noticias sobre BSD.</p>
&footer;
</body>
</html>

577
es/news/newsflash.sgml Normal file
View file

@ -0,0 +1,577 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "FreeBSD News flash!">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: newsflash.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>FreeBSD es un sistema operativo de r&aacute;pido desarrollo.
Mantenerse al d&iacute;a en los &uacute;ltimos desarrollos puede
ser complicado. Para ayudarte a mantenerte al d&iacute;a, p&aacute;sate
por aqu&iacute; peri&oacute;dicamente. Tambi&eacute;n te recomendamos
que te subscribas a la lista <a
href="../handbook/eresources:mail.html">freebsd-announce</a>.</p>
<p>La <a href="../news/qnewsletter.html">FreeBSD Real-Quick (TM) Newsletter
(RQN)</a> es una peque&ntilde;a publicaci&oacute;n mensual (a veces
quincenal) sobre desarrollos recientes en el mundo de FreeBSD.
Subscr&iacute;bete a
<a href="../handbook/eresources:mail.html">freebsd-announce</a>
para recibirla v&iacute;a e-mail.</p>
<p>Para una detallada descripci&oacute;n de pasad, presente, y futuro de las
releases, mira en la p&aacute;gina de
<strong><a href="&base/releases/index.html">Informaci&oacute;n de
Releases</a></strong>.</p>
<h2>December 1998</h2>
<ul>
<li><b>28-Dec-98</b>Unless circumstances dictate otherwise,
FreeBSD 3.0 will depart the -current branch late in the day
on 15 January 1999. The 3.0.1 release will follow 30 days
later, on 15 February 1999. Developers should consider this
as ADVANCE NOTICE of these events.</li>
<li><b>13-Dec-98</b>Walnut Creek CD-ROM has opened the <a href=
"http://www.freebsdmall.com/">FreeBSD Mall</a>, a site devoted to the
commercial aspects of FreeBSD, including add-ons, hardware, and
commercial tech-support. To advertise or sell your products or
services at the FreeBSD Mall, contact Walnut Creek CD-ROM.</li>
</ul>
<h2>November 1998</h2>
<ul>
<li><b>30-Nov-98</b><a href="&base/releases/2.2.8R/announce.html">
FreeBSD 2.2.8</a> has been released. Please see the
<a href="&base/releases/index.html">Release Information</a>
page for more details. Also be sure to check the
<a href="&base/releases/2.2.8R/errata.html">release errata</a>
after installation for any late-breaking issues with 2.2.8 that
you might need to be aware of.</li>
<li><b>26-Nov-98</b><a href="http://www.freebsdrocks.com/">FreeBSD
Rocks</a> is an initiative designed to provide the FreeBSD community
with the latest FreeBSD news, software and resources. All areas
include search facilities, making keyword searching of historical
posts a breeze. The pages are updated daily and everyone is invited
to sign up an post an article. If it happened today, you'll see it
on FreeBSDRocks.</li>
</ul>
<h2>October 1998</h2>
<ul>
<li><b>15-Oct-98</b><a href="&base/releases/3.0R/announce.html">
FreeBSD 3.0</a> has been released. See the
<a href="&base/releases/index.html">Release Information</a> page for
details. Also be sure to check the
<a href="&base/releases/3.0R/errata.html">release errata</a>
after installation for any late-breaking issues with 3.0 that you
might need to be aware of.</li>
</ul>
<h2>September 1998</h2>
<ul>
<li><p><b>15-Sep-98</b> September 15th is the scheduled date
for entering BETA with the 3.0-current tree. As all of you
already (should) know, 3.0 is scheduled for release on October
15th so this gives us a nice 30 day BETA period. During this
time, I don't expect anyone to drop in significant new work or
otherwise perturb the 3.0-current tree in such a way that
violates the general idea of a BETA (you're supposed to test
what you have, not move the goalposts every couple of days :).
<p></p></li>
<li><p><b>13-Sep-98</b>
After more than a year of development, the Common Access
Method SCSI layer for FreeBSD will be integrated into
3.0-current on Sunday, September 13th. The CAM development
team is currently busy ensuring that the integration process
goes as smoothly as possible, so please understand that we may
be slow to respond to questions about CAM in the days.
<p></p></li>
<li><p><b>9-Sep-98</b>
Perl5 is now imported into the 3.0-CURRENT source tree.
<p></p></li>
<li><p><b>5-Sep-98</b>
<a name="giveaway" href="http://visar.csustan.edu/">
The BSD CD Giveaway List</a>.
If somebody has a CD to give away (recipient pays for shipping) or to
lend locally, they can put their email address on the list. Hardware
and literature can also be given away. We encourage people to donate
CDs to local libraries and put them on the list as well.
</P></LI>
<li><p><b>1-Sep-98</b>
First issue of Daemon News arrives day earlier. This electronic
ezine is by BSD community for BSD community. See
<A HREF="http://www.daemonnews.org/">http://www.daemonnews.org</A>
</P></LI>
</ul>
<H2>August 1998</H2>
<UL>
<LI><P><B>31-Aug-98</B>
FreeBSD -CURRENT branch (the future 3.0-RELEASE) has switched to
ELF from a.out format. People involved did a great job: transition
went smooth. Check
<A HREF="http://www.freebsd.org/search/search.html">
freebsd-current@freebsd.org</A> mail archive for more information
on the transition to ELF.
</P></LI>
<LI><P><B>23-Aug-98</B>
Suidcontrol-0.1 utility has been released. The suidcontrol is an
experimental utility for managing suid/sgid policy under FreeBSD.
You can get more information at
<A HREF="http://www.watson.org/fbsd-hardening/suidcontrol.html">
http://www.watson.org/fbsd-hardening/suidcontrol.html</A>
</P></LI>
<LI><P><B>9-Aug-98</B>
FreeBSD Security How-To has been published. This work is currently
in beta and can be found at
<A HREF="http://www.best.com/~jkb/howto.txt">
http://www.best.com/~jkb/howto.txt</A>
</P></LI>
</UL>
<h2>July 1998</h2>
<ul>
<li><p><b>22-Jul-98</b>
FreeBSD 2.2.7 has been released.
See the <a href="&base/releases/index.html">Release
Information</a> page for details. Also be sure to
check the
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.7-RELEASE/ERRATA.TXT">
release errata</a> after installation for any late-breaking issues
with 2.2.7 that you should know about.
</li>
<li><p><b>16-Jul-98</b>
A ``FreeBSD for Linux users'' documentation effort has started.
Please see the <a
href="../docproj/current.html">list of current
documentation projects</a> for more information.</li>
<li><p><b>13-Jul-98</b>
<a href="mailto:jkh@freebsd.org">Jordan Hubbard</a> writes an
<a href="http://editorials.freshmeat.net/jordan980713/">editorial</a>
on the past and future of the Unix community.</li>
<li><p><b>9-Jul-98</b>
A <a href="http://www.es.freebsd.org/es/FAQ/FAQ.html">Spanish
translation</a> of the <a
href="../FAQ/FAQ.html">FAQ</a> has been completed
by the <a href="http://www.es.freebsd.org/es/">Spanish Documentation
Project</a>. More information can be found at the
<a
href="../docproj/translations.html">translations
page</a>.</li>
</ul>
<h2>June 1998</h2>
<ul>
<li><p><b>24-Jun-98</b>
The FreeBSD Project is sponsoring an
<a href="http://www.freebsd.org/~xcontest/">FreeBSD Desktop Theme
Contest</a>. Participants will design their own X11 configurations,
and winners will have theirs distributed with future releases of
FreeBSD.</p></li>
</ul>
<h2>May 1998</h2>
<ul>
<LI><P><B>30-May-98</b>
FreeBSD and Apache are used in <a href="http://www.WebTechniques.com/features/1998/05/engelschall/engelschall.shtml">this very useful article</a>
on implementing a web farm using round-robin DNS in
<a href="http://www.WebTechniques.com/">WEBTechniques.com</a></p>
</li>
<LI><P><B>23-May-98</b>
The second issue of the FreeBSD Newsletter is now available in
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue2.pdf">
Adobe PDF format</a> (also by
<A href="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue2.pdf">
FTP</A>). A
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/README.TXT">
help file</a> is available to assist you in selecting and using
a PDF viewer.
Article submissions, advertisements, and letters
to the editor should be sent to
<a href="mailto:newsletter@freebsd.org">newsletter@freebsd.org</a>.
</p>
</li>
<li><p><b>1-May-98</b>
The FreeBSD Project set up
<a name="anoncvs" href="../handbook/anoncvs.html">Anonymous CVS</a>
for the <a href="http://www.freebsd.org/cgi/cvsweb.cgi">FreeBSD CVS tree</a>.
Among other things, it allows users of FreeBSD to perform,
with no special privileges, read-only CVS operations
against one of the FreeBSD project's official anoncvs servers.
</p></li>
</ul>
<h2>April 1998</h2>
<ul>
<li><p><b>16-Apr-98</b>
The new 4 CD set of FreeBSD 2.2.6 is now in stock and should start
shipping to subscription and back-order customers tomorrow. More
information on the CD contents are available from
<a href="http://www.cdrom.com/">http://www.cdrom.com</a>.
</p></li>
<li><p><b>11-Apr-98</b>
The new FreeBSD project <a href="../projects/mozilla.html">FreeBSD Mozilla
Group</a> is created. The FreeBSD Mozilla Group supports and
improves the free available Netscape web browser,
otherwise known as <a href="http://www.mozilla.org/">Mozilla</a>.
</li>
</ul>
<h2>March 1998</h2>
<ul>
<li><p><b>25-Mar-98</b>
FreeBSD 2.2.6 has been released.
See the <a href="&base/releases/index.html">Release
Information</a> page for details. Also be sure to
check the
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/ERRATA.TXT">
release errata</a> after installation for any late-breaking issues
with 2.2.6 that you should know about.
</li>
</ul>
<h2>February 1998</h2>
<ul>
<li><p><b>08-Feb-98</b>
A page detailing the <a href="../y2kbug.html">FreeBSD Year 2000
compliance statement</a> is now available, linked through the <a
href="../docs.html">Documentation</a> page.</li>
</ul>
<h2>January 1998</h2>
<ul>
<li><p><b>08-Jan-98</b>
Improved support for Plug-n-Play cards has now been integrated into
both 3.0-current and 2.2-stable branches now. This is available
in source form via the <a href="../handbook/cvsup.html">CVSup</a> utility
or in binary release snapshots from
<a href="ftp://current.freebsd.org/pub/FreeBSD">current.FreeBSD.org</a>
</p></li>
</ul>
<h2>December 1997</h2>
<ul>
<li><p><b>26-Dec-97</b>
A convenient front-end tool for installing and configuring the
<a href="../handbook/cvsup.html">CVSup</a> utility is now available.
To use it, simply login or su to root and run:
<tt><b>pkg_add</b>
ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz</tt>
</p></li>
<li><p><b>2-Dec-97</b>
The "FOOF" bug has now been fixed in our 3.0-current and 2.2-stable
branches and can either be incorporated by using the
<a href="../handbook/cvsup.html">CVSup</a> utility, as described below
for the LAND attack fix, or by applying
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/updates/f00f.diff.2.2">these patches</a>.</p></li>
<li><p><b>1-Dec-97</b>
The "LAND attack" bug in TCP/IP has now been fixed in all relevant
branches and can be incorporated by using the
<a href="../handbook/cvsup.html">CVSup</a> utility to track the
latest 2.2 or 3.0 sources.</p></li>
<li><p><b>1-Dec-97</b>
Team FreeBSD is a group of FreeBSD users and supporters contributing
CPU idle time in an effort to crack RSA's 64-bit encryption code. For
more information, visit
<a href="http://www.circle.net/team-freebsd/">Team FreeBSD's WWW
site</a>.</p></li>
</ul>
<h2>November 1997</h2>
<ul>
<li><p><b>21-Nov-97</b>
<em>Pentium bug</em> -- We are aware of the "F00F" Pentium halting bug and are
working with Intel on a fix. When we have a fix ready for public
consumption it will be announced here, on the mailing list
announce@freebsd.org and to the Usenet newsgroup
<a href="news:comp.unix.bsd.freebsd.announce">comp.unix.bsd.freebsd.announce</a>.
Your patience is appreciated.</p></li>
<li><p><b>09-Nov-97</b>
FreeBSD 2.2.5-RELEASE CDROMS are now in stock and shipping to customers
worldwide. More information is available at <a href=
"http://www.cdrom.com/titles/os/fbsd25.htm">
http://www.cdrom.com/titles/os/fbsd25.htm</a>.</p></li>
</ul>
<h2>October 1997</h2>
<ul>
<li><p><b>22-Oct-97</b>
FreeBSD 2.2.5 has been released.
See the <a href="&base/releases/index.html">Release
Information</a> page for details. Also be sure to
check the
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.5-RELEASE/ERRATA.TXT">
release errata</a> after installation for any late-breaking issues
with 2.2.5 that you should know about.
</li>
</ul>
<h2>September 1997</h2>
<ul>
<li><p><b>01-Sep-97</b>
FreeBSD performed well in an Internet Week
<a href="http://techweb.cmp.com/internetwk/reviews/rev0901.htm">
review</a> of WWW server platforms.</p></li>
</ul>
<h2>August 1997</h2>
<ul>
<li><p><b>11-Aug-97</b>
Researchers in Duke University's
<a href="http://www.cs.duke.edu/ari/index.html">Trapeze Project</a>
have developed a high-speed Myrinet driver for FreeBSD. More
information about the driver, Trapeze Project, and its parent
project, the Collaborative Cluster Computing Iniative, including
the code for the Myrinet driver, are available from the CCCI's
<a href="http://www.cs.duke.edu/ari/index.html">WWW page</a>.
</p></li>
<li><p><b>03-Aug-97</b>
Netscape Communications has released a beta version of
Netscape Communicator v4.0 for FreeBSD. It can be obtained via
FTP from <a href="ftp://ftp.netscape.com/pub/communicator/4.03/4.03b8/english/unix/freebsd/base_install/">ftp.netscape.com</a> or its mirrors.</li>
</ul>
<h2>July 1997</h2>
<ul>
<li><p><b>22-Jul-97</b>
MacIP, an AppleTalk-to-IP gateway program for FreeBSD, is in beta
testing. To get the latest version, see
<a href="http://www.promo.de/pub/people/stefan/netatalk/">
http://www.promo.de/pub/people/stefan/netatalk/</a> or
<a href="ftp://ftp.promo.de/pub/people/stefan/netatalk/">
ftp://ftp.promo.de/pub/people/stefan/netatalk/</a>. </p>
</li>
<LI><P><B>17-Jul-97</b>
The first issue of the FreeBSD Newsletter is now available in
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue1.pdf">
Adobe PDF format</a> (also by
<A href="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue1.pdf">
FTP</A>). A
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/README.TXT">
help file</a> is available to assist you in selecting and using
a PDF viewer.
Article submissions, advertisements, and letters
to the editor should be sent to
<a href="mailto:newsletter@freebsd.org">newsletter@freebsd.org</a>.
</p>
</li>
</ul>
<h2>June 1997</h2>
<ul>
<li><p><b>17-Jun-97</b>
FreeBSD <a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.2-RELEASE/">
2.2.2-RELEASE</a> CD-ROM discs are now in stock; subscription
customers should receive them shortly.</p>
</li>
</ul>
<h2>May 1997</h2>
<ul>
<li><p><b>16-May-97</b>
FreeBSD <a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.2-RELEASE/">
2.2.2-RELEASE</a> has been released. The
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.2-RELEASE/RELNOTES.TXT">
Release Notes</a> and
<a href="ftp://ftp.freebsd.org/pub/FreeBSD2.2.2-RELEASE/ERRATA.TXT">
Errata List</a> can provide more information. </p>
</li>
<li><p><b>12-May-97</b>
A 3.0-Current SNAP-of-the-day server has been established at
<a href="ftp://current.freebsd.org/pub/FreeBSD/">
ftp://current.freebsd.org/pub/FreeBSD/</a>. A 3.0-SNAPshot
will be generated daily, and old SNAPshots will be kept for
a minimum of one week.</p>
</li>
</ul>
<h2>April 1997</h2>
<ul>
<li><p><b>28-Apr-97</b>
The 3.0-current src tree now contains support for building Symmetric
MultiProcessor kernels. For details go to the
<a href="http://www.freebsd.org/~fsmp/SMP/SMP.html">SMP</a> page.
</p></li>
<li><p><b>22-Apr-97</b>
A RELENG_2.2 snap-of-the-day server has been established at
<a href="ftp://releng22.freebsd.org/pub/FreeBSD/">
ftp://releng22.freebsd.org/pub/FreeBSD</a>. The
<a href="ftp://releng22.freebsd.org/pub/FreeBSD/README.TXT">
README.TXT</a> has more information.
</p></li>
<li><p><b>15-Apr-97</b>
FreeBSD 2.2.1-RELEASE CDs are shipping. Please see
<a href="http://www.cdrom.com/titles/os/fbsd22.htm">
http://www.cdrom.com/titles/os/fbsd22.htm</a> for more information.
</p></li>
</ul>
<h2>March 1997</h2>
<ul>
<li><p><b>28-Mar-97</b>
Sony Computer Science Laboratory, Inc. has released an alpha version
of ALTQ/CBQ, an alternative queuing framework for BSD Unix.
<a href="http://www.csl.sony.co.jp/person/kjc/programs.html">More
information</a> and the
<a href="ftp://ftp.csl.sony.co.jp/pub/kjc/altq.tar.gz">source code</a>
is available.</p></li>
<li><p><b>25-Mar-97</b>
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.1-RELEASE/">FreeBSD
2.2.1-RELEASE</a> is now available, replacing 2.2-RELEASE. Read the
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.1-RELEASE/README.TXT">
README.TXT</a> file or the
<a href="&base/releases/2.2.1R/notes.html">Release Notes</a>
for more information.</p></li>
<li><p><b>16-Mar-97</b>
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2-RELEASE/">FreeBSD
2.2-RELEASE</a> is now available. Read the
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.2-RELEASE/README.TXT">
README.TXT</a> file or the
<a href="&base/releases/2.2R/notes.html">Release Notes</a>
for more information.</p></li>
</ul>
<H2>February 1997</H2>
<UL>
<LI><P><B>20-Feb-1997</B>
FreeBSD
2.1.7-RELEASE is now available. Read the
README.TXT file or the
<a href="&base/releases/2.1.7R/notes.html">
Release Notes</a> for more information.</p></li>
<LI><P><B>10-Feb-1997</B>
FreeBSD
3.0-970209-SNAP has been released. Read the
README.TXT file for more information about this release.</p></li>
<LI><P><B>06-Feb-1997</B>
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. You can
read more about the problem and solution from the
<A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-97:01.setlocale">
FreeBSD-SA-97:01.setlocale</A> security announcement.
</P></LI>
<LI><P><B>06-Feb-1997</B>
The final pre-release version of FreeBSD 2.2-GAMMA, is now available.
The README.TXT file has more information.</P></LI>
<LI><P><B>05-Feb-1997</B>
The administrative position of FreeBSD Project President has been
eliminated with the
<a href="../internal/resignation.html">resignation</a> of former president
Jordan K. Hubbard.</p></li>
<LI><P><B>02-Feb-1997</B>
A snap-of-the-day server has been set up for the most current
<A HREF="../releases/snapshots.html">snapshot</a>
release of FreeBSD 2.2. Read the
<A HREF="ftp://22gamma.freebsd.org/pub/FreeBSD/README.TXT">README.TXT</A>
file for more information.
</P></LI>
</UL>
<H2>January 1997</H2>
<UL>
<LI><P><B>25-Jan-1997</B>
FreeBSD <A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/3.0-970124-SNAP/">
3.0-970124-SNAP</A> has been released.
Please see the
<A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/3.0-970124-SNAP/RELNOTES.TXT">
Release Notes</A> for more information.
</P></LI>
</UL>
<H2>December 1996</H2>
<UL>
<LI><P><B>24-Dec-1996</B>
FreeBSD <A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/2.2-BETA">2.2-BETA</A>
has been released. Please see the
<A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/2.2-BETA/RELNOTES.TXT">
Release Notes</A> for more information.
</P></LI>
<LI><P><B>13-Dec-1996</B>
FreeBSD 2.2-RELEASE will not support installation on machines with less
than 5MB of RAM or 1.2MB floppy drives. Please see the original
<A HREF="../releases/2.2R/install-media.html">announcement</A> for more
information.
</P></LI>
</UL>
<h2>November 1996</h2>
<ul>
<![ IGNORE [
<li><p><b>15-Nov-1996</b>
FreeBSD <a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.6-RELEASE">
2.1.6-RELEASE</a> is out. Please see the <a
href="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.6-RELEASE/RELNOTES.TXT">
release notes</a> for more information.
</P></li>
]]>
<li><p><b>15-Nov-1996</b>
FreeBSD <a href="&base/releases/2.1.6R/security.html">
2.1.6-RELEASE</a> is out. Please see the <a
href="&base/releases/2.1.6R/security.html">
release notes</a> for more information.
</P></li>
<li><p><b>4-Nov-1996</b>
The FreeBSD <a href="http://www.freebsd.org/cgi/cvsweb.cgi">CVS</a>
development tree has branched again. <a href="../releases/">See here</a>
for more information.
</P></li>
</ul>
&newshome;
&footer;
</body>
</html>

267
es/news/press.sgml Normal file
View file

@ -0,0 +1,267 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "FreeBSD en la Prensa">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: press.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<!-- some blub -->
Si falta alguna entrada, por favor env&iacute;a un mail a
<a href="../mailto.html">www@FreeBSD.ORG</a>
<p>
<H2>December 1998</H2>
<UL>
<li><b><a href="http://www.linuxworld.com/">LinuxWorld</a> December 1998</b><br>
<a href="http://www.linuxworld.com/linuxworld/lw-1998-12/lw-12-freebsd.html">The story on FreeBSD</a>, by Cameron Laird and Kathryn Soraiz<br>
This issue has a good article on FreeBSD and why it's worth a look
by Linux folks.
<p></p></li>
</UL>
<p>
<H2>November 1998</H2>
<UL>
<li><b><a href="http://www.edventure.com/release1/">RELEASE 1.0</a>
November 1998</b><br>
<a href="http://www.edventure.com/release1/1198.html">
The Open-Source Revolution</a>,
by Tim O'Reilly, with an introduction by Esther Dyson
<p></p></li>
<li><b><a href="http://www.news.com/">CNET News.com</a>
November 16, 1998</b><br>
<a href="http://www.news.com/News/Item/0,4,28816,00.html">
Ellison plans hardware, bashes Bill</a>,
By Tim Clark<br>
Larry Ellsion talking about their new dedicated Oracle servers,
mentions FreeBSD as one of a list of candidate OSs for the
platform.
<p></p></li>
<li><b><a href="http://www.linuxtoday.com/">Linux Today</a>
November 20th, 1998</b><br>
<a href="http://www.linuxtoday.com/stories/1005.html">
Report from Comdex--Walnut Creek CDROM, FreeBSD and Slackware</a>
by Dwight Johnson<br>
There is a good report on the Walnut Creek booth and FreeBSD at
the Linux Today website. The first half of the report is on
Slackware Linux, the second half is on FreeBSD.
<p></p></li>
</ul>
<H2>October 1998</H2>
<UL>
<li><b><a href="http://www.mercurycenter.com/">Mercury Center</a>
October 26, 1998</b><br>
<a href="http://www.mercurycenter.com/business/center/unix102798.htm">
Unix back in the fight with NT</a>,
by Miguel Helft<br>
<p></p></li>
<li><b><a href="http://www.computerbits.com/">Computer Bits</a>
Volume 8 * Number 10</b><br>
<a href="http://www.computerbits.com/archive/19981000/lnx9810.htm">
Linux/etc, The other free Unixes, part 2 of 2</a>
by Terry Griffin<br>
<p></p></li>
<LI><B><A HREF="http://www.zdnet.com/intweek/">
Inter@ctive Week</A>
October 19, 1998</B><BR>
<A HREF="http://www.zdnet.com/intweek/stories/prtarchivestory/0,4356,361668,00.html">
Open Code Frees Up The Net</A>, by Charles Babcock<BR>
<P></P></LI>
<LI><B><A HREF="http://www.performance-computing.com/">
Performance Computing</A>
October 1998</B><BR>
<A HREF="http://www.performance-computing.com/features/9810of1.shtml">
What Is FreeBSD?</A>, by Jordan K. Hubbard<BR>
<P></P></LI>
<LI><B><A HREF="http://www.zdnet.com/">ZDNet</A>
October 20, 1998</B><BR>
<A HREF="http://www.zdnet.com/pcmag/pclabs/nettools/1718/bench1.html">
A No-Cost NOS</A>, by Ryan Snedegar<BR>
<P></P></LI>
<LI><B><A HREF="http://www.irish-times.com/">The Irish Times</A>
October 12, 1998</B><BR>
<A HREF="http://www.irish-times.com/irish-times/paper/1998/1012/cmp2.html">
It's only free Unix - but I like it</A>, by David Malone<BR>
<P></P></LI>
</UL>
<h2>September 1998</h2>
<ul>
<li><b><a href="http://www.zdnet.com/sr/">Sm@rt Reseller Online</a>
September 7, 1998</b><br>
<a href="http://www.zdnet.com/sr/stories/issue/0,4537,349576,00.html">
Quality Unix for FREE</a>, by Brett Glass<br>
<p></p></li>
<li><b><a href="http://www.computerbits.com/">Computer Bits</a>
Volume 8 * Number 9</b><br>
<a href="http://www.computerbits.com/archive/19980900/lnx9809.htm">
Linux/etc, The other free Unixes, part 1 of 2</a>
by Terry Griffin<br>
<p></p></li>
<li><b><a href="http://www.ddj.com/">Dr. Dobb's Journal</a> September 1998 - Communications &amp; Networking</b><br>
<a href="http://www.ddj.com/ddj/1998/1998_09/faga/faga.htm">ASYNCHRONOUS COMMUNICATIONS USING select AND poll</a>, by Sean Eric Fagan<br>
<p></p></li>
</ul>
<h2>August 1998</h2>
<ul>
<li><b><a href="http://www.news.com/">News.com: Tech News First</a> 21-Aug-1998</b><br>
<a href="http://www.news.com/News/Item/0,4,25526,00.html">Hack raises flags about small ISPs</a>, Jim Hu, Staff Writer, CNET NEWS.COM<br>
<p></p></li>
</ul>
<h2>July 1998</h2>
<ul>
<LI>CRL Press Release<b> 30-July-1998</b><br>
<a href="http://www.crl.com/wccdromrcd.html">Walnut Creek CDROM, One of the Largest Public FTP Archives in the
World, Sets Traffic Record Using FreeBSD and Colocating on CRL's
High-Speed Internet Network</a><p></p></li>
<LI><B><A href="http://editorials.freshmeat.net/">( freshmeat ) - ( editorials )</a>
13-July-1998, </b><br>
<a HREF="http://editorials.freshmeat.net/jordan980713/">Pulling on one end of the rope</a>
(the past and future of the Unix community), by Jordan K. Hubbard
<p></p></li>
</ul>
<h2>June 1998</h2>
<ul>
<li><b><a href="http://www.news.com/">CNET News.com</a> June 14,
1998</b><br>
<a href="http://www.news.com/News/Item/0,4,23145,00.html">
Nader urges Windows probe</a>,
By Jeff Pelline<br>
Consumer-rights advocate Ralph Nader mentioned FreeBSD by name.
<p></p></li>
<LI><B><A HREF="http://RhapsodyOS.com/">RhapsodyOS</a>
10-June-1998, Stone's Throw, Issue Fourteen</b><br>
<a href="http://RhapsodyOS.com/editorial/stone/ST00014.html">
Home of the Brave, Land of the FreeBSD </a>, by Andrew Stone
<p></p></li>
</ul>
<h2>May 1998</h2>
<ul>
<LI><B><A HREF="http://www.WebTechniques.com/">
Web Techniques Magazin</a> May 1998, Volume 3, Issue 5</b><br>
<a href="http://www.WebTechniques.com/features/1998/05/engelschall/engelschall.shtml"> Load Balancing Your Web Site</a>, by Ralf S.Engelschall
<p></p></li>
<LI><B><A HREF="http://www.gartner.com/">GartnerGroup</a>
4-May-1998</b><br>
<a href="http://advisor.gartner.com/inbox/articles/ihl2_6398.html">
Free Unix: Do You Get What You Pay For?</a>, By G. Weiss
<p></p></li>
<li><b><a href="http://www.ncworldmag.com/">NC World</a>
May 1998</b><br>
<a href="http://www.ncworldmag.com/ncworld/ncw-05-1998/ncw-05-nextten.html">Is NT paranoid or is Unix out to get it?</a>, by Nicholas Petreley
<p></p></li>
<li><b><a href="http://www.samag.com/">SysAdmin</a>
May 1998 Volume 7 Number 5</b><br>
<a href="http://www.samag.com/archive/0705/feature.shtml">
Security Tools in FreeBSD</a>, by Guy Helmer
</li>
</ul>
<h2>April 1998</h2>
<ul>
<li><b><a href="http://www.ncworldmag.com/">NC World</a>
April 1998</b><br>
<a href="http://www.ncworldmag.com/ncworld/ncw-04-1998/ncw-04-nextten.html">The new Unix alters NT's orbit</a>, by Nicholas Petreley
<p></p></li>
<li><b><a href="http://www.dv.com/">
DV Live Magazine: April 98</a></b><br>
<a href="http://www.dv.com/magazine/1998/0498/johnson0498.html">
Who's Serving Who?</a>, by Nels Johnson
</li>
</ul>
<h2>March 1998</h2>
<ul>
<li><b><a href="http://www.ncworldmag.com/">NC World</a>
March 1998</b><br>
<a href="http://www.ncworldmag.com/ncworld/ncw-03-1998/ncw-03-nextten.html">Searching for the next Windows NT</a>, by Nicholas Petreley
<p></p></li>
<li><b><a href="http://www.cnet.com/">CNET</a> 25-Mar-98</b><br>
<a href="http://www.cnet.com/Content/Reviews/Compare/AltOS/">
Five alternative operating systems reviewed</a>, by
Cormac Foster
<p></p></li>
<li><b><a href="http://www.ddj.com/">Dr. Dobb's Journal</a> March 1998 - Benchmarking and Software Testing</b><br>
<a href="http://www.ddj.com/ddj/1998/1998_03/index.htm">Tracing BSD System Calls</a>, by Sean Eric Fagan<br>
Note: the article is not available online.
<p</p></li>
</ul>
<h2>February 1998</h2>
<ul>
<li><b><a href="http://www.news.com">News.com</a>
February 2, 1998</b><br>
<a href="http://www.news.com/SpecialFeatures/0,5,18652,00.html">
Source code for the masses</a>,
by Alex Lash<br>
<p></p></li>
</ul>
<h2>August 1997</h2>
<ul>
<li><b><a href="http://www.computerbits.com/">Computer Bits Online</a> August 1997</b> Volume7, Number 8<br>
<a href="http://www.computerbits.com/archive/9708/lan9708.htm">
The Network Community</a>, by Ted Mittelstaedt<p></p></li>
</ul>
<h2>June 1997</h2>
<ul>
<li><b><a href="http://www.performancecomputing.com/unixreview/">UNIX Review</a> June 1997</b><br>
<a href="http://www.performancecomputing.com/unixreview/backissu/9706/9706tin.htm">The Internet Notebook / The Ports Collection</a>,
by Richard Morin <p></p></li>
</ul>
<h2>May 1997</h2>
<ul>
<li><b><a href="http://www.ncworldmag.com/">NC World</a>
May 1997</b><br>
<a href="http://www.ncworldmag.com/ncworld/ncw-05-1997/ncw-05-analysis.html">
The Politics of NC Computing According to Oracle</a>,
by Rawn Shaw
<p></p></li>
</ul>
&newshome;
&footer;
</body>
</html>

View file

@ -0,0 +1,78 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date">
<!ENTITY volume "1">
<!ENTITY issue "1">
<!ENTITY month "Jun">
<!ENTITY year "1998">
<!ENTITY title "Quick NewsLetter Volume #&volume; Issue #&issue;">
<!ENTITY qnlnext "qnewsletter-1-2.html">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: qnewsletter-1-1.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
&qnewsletterheader;
<ul>
<li>
<B>General News</B>:<Br>
Jordan Hubbard, Poul-Henning Kamp, Justin Gibbs, Jonathan Bresler,
David Greenman and other members of the Core Team will be at the
USENIX technical conference.
Be Sure to Attend! Information at: <A HREF="http://www.usenix.org/">http://www.usenix.org</A>
June 15-19, New Orleans, Louisiana</li>
<li><b>Download the Published FreeBSD News Letter Volume #2</b>:
<A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue2.pdf">ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue2.pdf</A></li>
<li><b>Web Masters</b>:<br>
Check out this article on balancing Webserver traffic:
<a href="http://www.WebTechniques.com/features/1998/05/engelschall/engelschall.shtml">http://www.WebTechniques.com/features/1998/05/engelschall/engelschall.shtml</a></li>
<li><b>Filesystem Management</b>:<br>
An early version of vinum, a FreeBSD volume manager, is available.
It allows volumes to span disks and spread diskload across multiple disks.
Check out: <A HREF="http://www.lemis.com/vinum.html">http://www.lemis.com/vinum.html.</A> </li>
<li><b>Alpha Porting Project</b>:<br>
There seems to be quite a bit of recent activity on this project.
Developers are being actively sought.
Join the alpha@freebsd.org mailing list.
PALCode and other Alpha Documentation can be found at:
<a href="ftp://ftp.digital.com/pub/Digital/info/semiconductor/literature/dsc-library.html">ftp://ftp.digital.com/pub/Digital/info/semiconductor/literature/dsc-library.html</a></li>
<li><b>X Window System</b>:<br>
Check out the Enlightenment Desktop:
/usr/ports/x11/enlightenment
Check out the Themes you can download for Enlightenment:
<A HREF="http://www.rasterman.com/themes/printthemes.cgi">http://www.rasterman.com/themes/printthemes.cgi</A></li>
<li><b>Graphics/Design</b>:<br>
Check out the 'Blender' package from Neo-Geo
<A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/commerce/3D/Blender/">ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/commerce/3D/Blender/</A></li>
<li><b>System Administration</b>:<br>
A Web Based FreeBSD System Administration Tool is available.
<A HREF="http://ourworld.compuserve.com/homepages/berend/FreEasy.html">http://ourworld.compuserve.com/homepages/berend/FreEasy.html</A><br>
A X based FreeBSD System Administration Tool is also available.
<A HREF="http://cam.grad.kiev.ua/~rssh/admin/admin.html">http://cam.grad.kiev.ua/~rssh/admin/admin.html</A> <br>
Both are functional, yet still in developmental stages.</li>
<li><b>Installing FreeBSD</b>:<br>
Here is a newbie-oriented Install tutorial complete with screen shots.
Check out: <A HREF="http://www.vmunix.com/fbsd-book/install.phtml">http://www.vmunix.com/fbsd-book/install.phtml</A></li>
</ul>
&qnewsletterfooter;
&newshome;
&qnewsletterhome;
| &qnewsletternext;
&footer;
</body>
</html>

View file

@ -0,0 +1,82 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date">
<!ENTITY volume "1">
<!ENTITY issue "2">
<!ENTITY month "Jul">
<!ENTITY year "1998">
<!ENTITY title "Quick NewsLetter Volume #&volume; Issue #&issue;">
<!ENTITY qnlnext "qnewsletter-1-3.html">
<!ENTITY qnlprev "qnewsletter-1-1.html">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: qnewsletter-1-2.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
&qnewsletterheader;
<ul>
<li><b>General News:</b>
Attention CVSup users and mirror site administrators. If you have not
already done so, you need to upgrade to release 15.4 of CVSup.
CVSup is available from <A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/">ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/</A></li>
<li><b>Download the Published FreeBSD News Letter Volume #2</b>:
<A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue2.pdf">ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue2.pdf</A></li>
<li><b>IP Bandwith:</b>
ipltd - IP traffic bandwidth shaping/limiting daemon.
You can find it in <A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/incoming/ipltd_v2.01.tgz">ftp://ftp.freebsd.org/pub/FreeBSD/incoming/ipltd_v2.01.tgz</A></li>
<li><b>Freebsd-Advocacy:</b>
Check your local University Bookstore, most have patron
request/suggestion cards that allow you to suggest books they
should carry. Suggest Greg Lehey's latest book.
"The Complete FreeBSD", second edition,
published by Walnut Creek CDROM. ISBN 1-57176-216-7
(<A HREF="http://www.cdrom.com/titles/os/bsdbook2.htm">http://www.cdrom.com/titles/os/bsdbook2.htm</A>)</li>
<li><b>Fill out the Free-Software Survey.</b>
<a href="http://www.sun.com/sunworldonline/swol-06-1998/swol-06-readersurvey.html">http://www.sun.com/sunworldonline/swol-06-1998/swol-06-readersurvey.html</a></li>
<li><b>FreeBSD in Hollywood</b>
Check out these FreeBSD/Apache run web sites:
<a href="http://www.volcano.com/">http://www.volcano.com</a>,
<a href="http://www.romeoandjuliet.com/">http://www.romeoandjuliet.com</a>,
<a href="http://www.speed2-cruisecontrol.com/">http://www.speed2-cruisecontrol.com</a>
These are run by <a href="http://www.gisolutions.com/">http://www.gisolutions.com</a></li>
<li><b>FreeBSD-Security</b>
Have you seen this article on FreeBSD Security
<A HREF="http://www.samag.com/archive/0705/feature.html">http://www.samag.com/archive/0705/feature.html</A></li>
<li><b>Experimental Authentication and Authorization</b>
Token Management Extensions in the FreeBSD Kernel
<A HREF="http://www.watson.org/fbsd-hardening/tokens/">http://www.watson.org/fbsd-hardening/tokens/</A></li>
<li><b>FreeBSD Desktop Contest!</b>
<A HREF="http://www.freebsd.org/~xcontest/">http://www.freebsd.org/~xcontest</A> Win Fabulous Prizes!</li>
<li><b>Coda distributed file system version 4.6.0 now available</b>
Coda is an advanced experimental distributed file system with features
such as server replication and disconnected operation for laptops
<A HREF="http://www.coda.cs.cmu.edu/">http://www.coda.cs.cmu.edu</A></li>
<li><b>Need help asking a Question about FreeBSD?</b>
<A HREF="http://www.aei.ca/~malartre/how-to-ask-en.html">http://www.aei.ca/~malartre/how-to-ask-en.html</A> (English)
<A HREF="http://www.aei.ca/~malartre/how-to-ask-fr.html">http://www.aei.ca/~malartre/how-to-ask-fr.html</A> (French)</li>
</ul>
&qnewsletterfooter;
&newshome;
&qnewsletterhome;
<BR>&qnewsletterprev; |
&qnewsletternext;
&footer;
</body>
</html>

View file

@ -0,0 +1,101 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date">
<!ENTITY volume "1">
<!ENTITY issue "3">
<!ENTITY month "Jul">
<!ENTITY year "1998">
<!ENTITY title "Quick NewsLetter Volume #&volume; Issue #&issue;">
<!ENTITY qnlnext "qnewsletter-1-4.html">
<!ENTITY qnlprev "qnewsletter-1-2.html">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: qnewsletter-1-3.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
&qnewsletterheader;
<ul>
<li><b>General News:</b>
Announcing CVSup 15.4.2 (This is new since last announcement).
Release 15.4.2 of CVSup, the CVS-aware network file distribution
system, is now available.
<A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CVSup/">ftp://ftp.FreeBSD.org/pub/FreeBSD/CVSup/</A>
<p></p></li>
<li><b>Release Information:</b>
The latest RELEASE is 2.2.6-RELEASE. FreeBSD 2.2.7 is
scheduled to be released July 21st. FreeBSD 3.0 is scheduled to be
released October 15th.
<p></p></li>
<li><b>Microsoft Front Page Extensions:</b>
Microsoft Front Page won't work with out Front Page Extensions.
<A HREF="http://dailynews.yahoo.com/headlines/technology/wired/story.html?s=z/reuters">http://dailynews.yahoo.com/headlines/technology/wired/story.html?s=z/reuters</A>
/980707/wired/stories/microsoft_1.html (All one line)
Front Page Extensions are available at:
<A HREF="http://www.rtr.com/fpsupport/SERK/default.htm">http://www.rtr.com/fpsupport/SERK/default.htm</A>
<A HREF="http://www.rtr.com/fpsupport/fp98license.htm">http://www.rtr.com/fpsupport/fp98license.htm</A>
<p></p></li>
<li><b>FreeBSD-Advocacy:</b>
<A HREF="http://editorials.freshmeat.net/jordan980713/">http://editorials.freshmeat.net/jordan980713/</A>
<p></p></li>
<li><b>FreeBSD Desktop Contest!</b>
<A HREF="http://www.freebsd.org/~xcontest/">http://www.freebsd.org/~xcontest</A> Win Fabulous Prizes!
<p></p></li>
<li><b>Commercial FreeBSD Products:</b>
FunnelWeb 2.0:
Article: <A HREF="http://biz.yahoo.com/bw/980707/active_con_1.html">http://biz.yahoo.com/bw/980707/active_con_1.html</A>
Homepage: <A HREF="http://www.activeconcepts.com/">http://www.activeconcepts.com</A><p>
SOLID SERVER:
SOLID Server is the true plug-and-play database server for mission
critical applications.
<A HREF="http://www.solidtech.com/market/products/">http://www.solidtech.com/market/products/</A>
<p></p></li>
<li><b>FreeBSD HOW-TO:</b>
A roadmap for setting up an intranet server with FreeBSD
<A HREF="http://www1.tpgi.com.au/users/eirvine/freebsd/hermione.html">http://www1.tpgi.com.au/users/eirvine/freebsd/hermione.html</A>
<p>
Manual de instalacion de FreeBSD
<A HREF="http://www.es.freebsd.org/es/docs/instalacion/index.htm">http://www.es.freebsd.org/es/docs/instalacion/index.htm</A>
<p></p></li>
<li><b>FreeBSD Sparc Porting Project:</b>
Online programming manuals for sun4m, sun4u processors.
<A HREF="http://www.sun.com/microelectronics/table.html">http://www.sun.com/microelectronics/table.html</A><br>
User's Manual describing UltraSPARC specific features
<A HREF="http://www.sun.com/microelectronics/UltraSPARC-I/">http://www.sun.com/microelectronics/UltraSPARC-I/</A><br>
<p></p></li>
<li><b>FreeBSD Alpha Porting Project:</b>
<A HREF="../alpha/alpha.html">http://www.freebsd.org/alpha/alpha.html</A>
<A HREF="../alpha/current.html">http://www.freebsd.org/alpha/current.html</A>
<p></p></li>
<li><b>FreeBSD Software RAID:</b>
The fourth alpha version of vinum is now available for download at
<A HREF="ftp://ftp.lemis.com/pub/vinum/vinumdist-11Jul.tar.gz">ftp://ftp.lemis.com/pub/vinum/vinumdist-11Jul.tar.gz</A>
<p></p></li>
<li><b>FreeBSD On-line News.</b>
<A HREF="http://freebsd-online.ml.org/">http://freebsd-online.ml.org/</A>
</li>
</ul>
&qnewsletterfooter;
&newshome;
&qnewsletterhome;
<BR>&qnewsletterprev; |
&qnewsletternext;
&footer;
</body>
</html>

View file

@ -0,0 +1,117 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY volume "1">
<!ENTITY issue "4">
<!ENTITY month "Aug">
<!ENTITY year "1998">
<!ENTITY title "Quick NewsLetter Volume #&volume; Issue #&issue;">
<!ENTITY qnlprev "qnewsletter-1-3.html">
<!ENTITY qnlnext "qnewsletter-1-5.html">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: qnewsletter-1-4.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
&qnewsletterheader;
<ul>
<li>
<b>Release Information:</b>
The latest RELEASE is 2.2.7-RELEASE. FreeBSD 2.2.8 is
scheduled to be released November 15st. FreeBSD 3.0 is scheduled to be
released October 15th.
<p></p></li>
<li><b>Announcing: OpenLDAP:</b>
The OpenLDAP Project is pleased to announce the immediate
availability of OpenLDAP 1.0.
This software is available for download:
<A HREF="http://www.OpenLDAP.org/download.html">http://www.OpenLDAP.org/download.html</A>
or AnonCVS:
<A HREF="http://www.OpenLDAP.org/repo.html">http://www.OpenLDAP.org/repo.html</A>
<p></p></li>
<li><b>PicoBSD</b>:
PicoBSD 0.4 is out!
<A HREF="http://www.freebsd.org/~picobsd/">http://www.freebsd.org/~picobsd/</A>
For download:
<A HREF="http://www.freebsd.org/~picobsd/picobsd/">http://www.freebsd.org/~picobsd/picobsd/</A>
<p></p></li>
<li><b>FreeBSD-Advocacy:</b>
Walnut Creek vs Microsoft.
<A HREF="http://www.crl.com/wccdromrcd.html">http://www.crl.com/wccdromrcd.html</A>
<p></p></li>
<li><b>FreeBSD: Solid as a Rock.</B>
<A HREF="http://www.zdnet.co.uk/athome/misc/toot/output/57.html">http://www.zdnet.co.uk/athome/misc/toot/output/57.html</A>
<p></p></li>
<li><b>Daemon News: The BSD Ezine</b>
The BSD camps are building an online magazine. Sign up to write a column,
or a single article.
<A HREF="http://ezine.freebsd.org/">http://ezine.freebsd.org</A>
Our first Issue prints Sept 1st!!!! Check it out at:
<A HREF="http://www.daemonnews.org/">http://www.daemonnews.org</A>
<p></p></li>
<li><b>Commercial FreeBSD Products: </b>
Citadel firewall and VPN router which is
based on FreeBSD. Full details are at <A HREF="http://www.cdsec.com/">http://www.cdsec.com</A>
<p></p></li>
<li><b>Equalizer V2.0:</b>
Equalizer is a load balancer and cluster management tool.
<A HREF="http://www.coyotepoint.com/cp_products.shtml">http://www.coyotepoint.com/cp_products.shtml</A>
<p></p></li>
<li><b>FreeQualizer V2.0-b4:</b>
FreeQualizer is a free beta version of Equalizer for FreeBSD 2.2.6
<A HREF="http://www.coyotepoint.com/freequalizer.shtml">http://www.coyotepoint.com/freequalizer.shtml</A>
<p></p></li>
<li><b>FreeBSD HOW-TO:</b>
In Portugese:
<A HREF="http://www.geocities.com/SiliconValley/Sector/8050/">http://www.geocities.com/SiliconValley/Sector/8050/</A>
<p></p></li>
<li><b>FreeBSD for Linux Users:</b>
<A HREF="http://freebsd.stanford.edu/FreeBSD/linux.html">http://freebsd.stanford.edu/FreeBSD/linux.html</A>
<p></p></li>
<li><b>FreeBSD Security:</b>
<A HREF="http://www.best.com/~jkb/howto.txt">http://www.best.com/~jkb/howto.txt</A>
<p></p></li>
<li><b>UNIX Resource Pages:</b>
The UNIX Resource Index:
<A HREF="http://unix.cyberscript.net/">http://unix.cyberscript.net/</A>
FreeBSD-Online: (This address has changed!!! This is the new address.)
<A HREF="http://freebsd.unixhelp.org/">http://freebsd.unixhelp.org/</A>
<p></p></li>
</ul>
&qnewsletterfooter;
&newshome;
&qnewsletterhome;
| &qnewsletterprev;
| &qnewsletternext;
&footer;
</body>

View file

@ -0,0 +1,101 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date">
<!ENTITY volume "1">
<!ENTITY issue "5">
<!ENTITY month "Sep">
<!ENTITY year "1998">
<!ENTITY title "Quick NewsLetter Volume #&volume; Issue #&issue;">
<!ENTITY qnlprev "qnewsletter-1-4.html">
<!ENTITY qnlnext "qnewsletter-1-6.html">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: qnewsletter-1-5.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
&qnewsletterheader;
<ul>
<li><b>Release Information</b>:
The latest RELEASE is 2.2.7-RELEASE. FreeBSD 2.2.8 is
scheduled to be released November 30th. FreeBSD 3.0 is scheduled to be
released October 15th. Start BETA Testing!!!
<p></p></li>
<li><b>FreeBSD in the News</b>:
<A HREF="http://www.zdnet.com/sr/stories/issue/0,4537,349576,00.html ">http://www.zdnet.com/sr/stories/issue/0,4537,349576,00.html </A>
<p></p></li>
<li><b>Recent Improvements</b>:
CAM (Common Access Method) SCSI layer implemented into 3.0-Current.<br>
Perl5 now standard in 3.0-Current<br>
Support for IDE disks drives larger than 8G in 2.2<br>
3.0-CURRENT is now ELF!<br>
FreeBSD/alpha now self-hosting - both kernel and `make world' work!<br>
<p></p></li>
<li><b>New FreeBSD JDK release</b>:
Download information is available at:
<A HREF="http://www.freebsd.org/java/">http://www.freebsd.org/java</A>
<p></p></li>
<li><b>Uniform Driver Interface</b>:
<A HREF="http://www.sco.com/udi/">http://www.sco.com/udi</A>
<A HREF="ftp://ftp.cup.hp.com/pub/hp_stds/udi/docs.html">ftp://ftp.cup.hp.com/pub/hp_stds/udi/docs.html</A>
<A HREF="http://www.infoworld.com/cgi-bin/displayStory.pl?980916.ecminer.htm">http://www.infoworld.com/cgi-bin/displayStory.pl?980916.ecminer.htm</A>
<A HREF="http://www.intel.com/pressroom/archive/releases/Cn091698.htm">http://www.intel.com/pressroom/archive/releases/Cn091698.htm</A>
<A HREF="ftp://ftp.cup.hp.com/pub/hp_stds/udi/Postscript/rules.ps.Z">ftp://ftp.cup.hp.com/pub/hp_stds/udi/Postscript/rules.ps.Z</A>
<p></p></li>
<li><b>RealTek 8139 Ethernet driver</b>: Testers Wanted.
<A HREF="http://www.freebsd.org/~wpaul/RealTek/3.0/">http://www.freebsd.org/~wpaul/RealTek/3.0</A> source for FreeBSD 3.0
<A HREF="http://www.freebsd.org/~wpaul/RealTek/2.2/">http://www.freebsd.org/~wpaul/RealTek/2.2</A> source for FreeBSD 2.2.x
Reply to: wpaul@skynet.ctr.columbia.edu.
<p></p></li>
<li><b>ThunderLAN Ethernet driver</b> (popular in Compaq machines) : Testers Wanted.
<A HREF="http://www.freebsd.org/~wpaul/ThunderLAN/3.0/">http://www.freebsd.org/~wpaul/ThunderLAN/3.0</A> source for FreeBSD 3.0
<A HREF="http://www.freebsd.org/~wpaul/ThunderLAN/2.2/">http://www.freebsd.org/~wpaul/ThunderLAN/2.2</A> source for FreeBSD 2.2.x
Reply to: wpaul@skynet.ctr.columbia.edu.
<p></p></li>
<li><b>Commercial FreeBSD Products</b>:
Emerging Technologies, Inc.
ISA and PCI Sync Cards for FreeBSD
<A HREF="http://www.etinc.com/">http://www.etinc.com</A>
Bandwidth Manager
<A HREF="http://www.etinc.com/bwmgr.htm">http://www.etinc.com/bwmgr.htm</A><br>
Acadix Software Systems:
APE is a syntax-colorizing, language-independent, terminal-independent
integrated development environment for Unix.
<A HREF="http://www.execpc.com/~acadix/">http://www.execpc.com/~acadix</A>
<p></p></li>
<li><b>BSD Online Magazine: Daemon News</b>!
Don't forget to check out the BSD online Magazine written by many
from the FreeBSD Community. Articles are due the 15th of each month,
and publish the 1st of the following month. Authors Wanted.
<A HREF="http://www.daemonnews.org/">http://www.daemonnews.org/</A>
<p></p></li>
<li><b>Quote</b>:
If you aim the gun at your foot and pull the trigger, it's UNIX's
job to ensure reliable delivery of the bullet to where you aimed
the gun (in this case, Mr. Foot). (Terry)
<p></p></li>
</ul>
&qnewsletterfooter;
&newshome;
&qnewsletterhome;
| &qnewsletterprev;
| &qnewsletternext;
&footer;
</body>

View file

@ -0,0 +1,86 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date">
<!ENTITY volume "1">
<!ENTITY issue "6">
<!ENTITY month "Oct">
<!ENTITY year "1998">
<!ENTITY title "Quick NewsLetter Volume #&volume; Issue #&issue;">
<!ENTITY qnlprev "qnewsletter-1-5.html">
<!ENTITY qnlnext "qnewsletter-1-7.html">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: qnewsletter-1-6.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
&qnewsletterheader;
<ul>
<li><b>Release Information</b>: FreeBSD 3.0 RELEASE is out! :-) Order
your Copy today from: <A
HREF="http://www.cdrom.com/">http://www.cdrom.com</A>
The current stable release is 2.2.7-RELEASE, with FreeBSD 2.2.8 due
for release November 30. <p></p></li>
<li><b>FreeBSD in the News</b>: 24-Oct-98 ftp.freebsd.org (aka
ftp.cdrom.com), a P6/200 with 1GB of RAM and half a TB of RAID-5
storage, served up 724GB of data--a new one day record. See the
previous record at: <A
HREF="http://www.crl.com/wccdromrcd.html">http://www.crl.com/wccdromrcd.html</A>
<p></p></li>
<li><b>FreeBSD Advocacy</b>:
<br>
<A HREF="http://www.unix-vs-nt.org/">http://www.unix-vs-nt.org/</A>,<br>
<A HREF="http://www.dvl-software.com/freebsd/">http://www.dvl-software.com/freebsd/</A>, <br>
<A HREF="http://www.cnet.com/Content/Reviews/Compare/AltOS/ss04.html">http://www.cnet.com/Content/Reviews/Compare/AltOS/ss04.html</A>, <br>
<A HREF="http://www.irish-times.com/irish%2Dtimes/paper/1998/1012/cmp2.html">http://www.irish-times.com/irish%2Dtimes/paper/1998/1012/cmp2.html</A>
<p></p></li>
<li><b>FreeBSD RELEASE/SNAP finder Database</b>: <A
HREF="http://www.itworks.com.au/~gavin/FBSDsites.php3">http://www.itworks.com.au/~gavin/FBSDsites.php3</A>
<p></p></li>
<li><b>Commercial FreeBSD Products</b>: You may want to have a look at
Zeus (<A HREF="http://www.zeus.co.uk/">http://www.zeus.co.uk/</A>)
all of their server products are available for FreeBSD.
<p></p></li>
<li><b>Tony Ballardie and BT Laboratories, UK</b> are pleased to
announce an alpha level source code release of Core Based Trees
multicast routing demon "cbtd" plus associated kernel patches for
FreeBSD 2.2.[67]. The ftp download is from <A
HREF="ftp://ftp.labs.bt.com/Internet-Research/cbt-2.0.tar.gz">ftp://ftp.labs.bt.com/Internet-Research/cbt-2.0.tar.gz</A>
Feedback please to: graeme.brown@bt-sys.bt.co.uk,
ballardie@dial.pipex.com <p></p></li>
<li><b>BSD Online Magazine</b>: The DaemonNews needs people to format
articles from text to HTML. E-mail: <a
href="mailto:editors@daemonnews.org">editors@daemonnews.org</a>,
Articles: <a
href="mailto:article@daemonnews.org">article@daemonnews.org</a>
<p></p></li>
<li><b>$$$Money$$$ for Free Software Projects</b>: The Free Software
Bazaar at <A
HREF="http://visar.csustan.edu/bazaar/">http://visar.csustan.edu/bazaar/</A>
lets people put up bounties for free software projects. Please check
it out. <p></p></li>
</ul>
&qnewsletterfooter;
&newshome;
&qnewsletterhome;
| &qnewsletterprev;
| &qnewsletternext;
&footer;
</body>

View file

@ -0,0 +1,70 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date">
<!ENTITY volume "1">
<!ENTITY issue "7">
<!ENTITY month "Nov">
<!ENTITY year "1998">
<!ENTITY title "Quick NewsLetter Volume #&volume; Issue #&issue;">
<!ENTITY qnlprev "qnewsletter-1-6.html">
<!-- <!ENTITY qnlnext "qnewsletter-1-8.html"> -->
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: qnewsletter-1-7.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
&qnewsletterheader;
<ul>
<li><b>Release Information:</b>
FreeBSD 2.2.8 is now available.
FreeBSD 3.0 is still available for purchase.
<A HREF="http://www.cdrom.com/">http://www.cdrom.com/</A>
<p></p></li>
<li><b>FreeBSD in the News:</b>
BSD widely used as Web Servers and such.
<A HREF="http://www.hzo.cubenet.de/ioscount/">http://www.hzo.cubenet.de/ioscount/</A>
<p></p></li>
<li>FreeBSD mentioned in <b>Comdex report.</b>
<A HREF="http://linuxtoday.net/stories/1005.html">http://linuxtoday.net/stories/1005.html</A>
<p></p></li>
<li><b>FreeBSD Advocacy:</b>
A comprehensive and searchable FreeBSD resource database which will be
built on the input from our users is now available at:
<A HREF="http://www.freebsdrocks.com/">http://www.freebsdrocks.com/</A>
<p></p></li>
<li><b>XFree86-3.3.3</b> is now available!
<A HREF="http://www.xfree86.org/">http://www.xfree86.org/</A>
<p></p></li>
<li><b>SANE Version 1.0</b> Released
<A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
<p></p></li>
<li><b>FreeBSD JDK 1.1.7</b> Released
<A HREF="http://www.freebsd.org/java/">http://www.freebsd.org/java/</A>
<p></p></li>
<li>Dont forget to read the lastest issue of the <b>Daemon News</b>.
<A HREF="http://www.daemonnews.org/">http://www.daemonnews.org/</A>
<p></p></li>
</ul>
&qnewsletterfooter;
&newshome;
&qnewsletterhome;
| &qnewsletterprev;
<!-- | &qnewsletternext; -->
&footer;
</body>

32
es/news/qnewsletter.sgml Normal file
View file

@ -0,0 +1,32 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "FreeBSD Really-Quick(TM) NewsLetter">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: qnewsletter.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>
FreeBSD Really-Quick(TM) NewsLetter. Things Happening in FreeBSD.
</p>
<a name="1998"></a>
<h2>1998</h2>
<ul>
<li><b>Nov</b> <a href="qnewsletter-1-7.html">Volume #1 Issue #7</a></li>
<li><b>Oct</b> <a href="qnewsletter-1-6.html">Volume #1 Issue #6</a></li>
<li><b>Sep</b> <a href="qnewsletter-1-5.html">Volume #1 Issue #5</a></li>
<li><b>Aug</b> <a href="qnewsletter-1-4.html">Volume #1 Issue #4</a></li>
<li><b>Jul</b> <a href="qnewsletter-1-3.html">Volume #1 Issue #3</a></li>
<li><b>Jul</b> <a href="qnewsletter-1-2.html">Volume #1 Issue #2</a></li>
<li><b>Jun</b> <a href="qnewsletter-1-1.html">Volume #1 Issue #1</a></li>
</ul>
&newshome;
&footer;
</body>
</html>

181
es/news/webchanges.sgml Normal file
View file

@ -0,0 +1,181 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Cambios en el servidor Web de FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
]>
<!-- $Id: webchanges.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<!-- some blub -->
Esta p&aacute;gina lista los cambios visibles en el servidor Web de FreeBSD.
<p>
<H2>December 1998</H2>
<UL>
<li><b>27-Dec-1998</B><br>
<a href="../commercial/software.html">/commercial/software.html</a>
Added: Sleepycat Software offers the Berkeley Database
product. Berkeley DB is a programmatic toolkit that provides
high-performance embedded database support.<br>
<a href="../support.html#user">/support.html</a>
New name and home for the San Francisco users group.
<P></P></LI>
<li><b>21-Dec-1998</B><br>
/news/webchanges.html Added this page.
<P></P></LI>
<li><b>19-Dec-1998</B><br> <a
href="../news/press.html">/news/press.html</a>
Update URL for:
DV Live Magazine: April 98, Who's Serving Who?, by Nels Johnson<br>
Update URL for:
SysAdmin May 1998 Volume 7 Number 5 Security Tools in FreeBSD, by Guy
Helmer<br>
<a href="../security/security.html">/security/security.html</a>
Bring in the new security guide
<p></p></li>
<li><b>18-Dec-1998</B><br> <a
href="http://www.freebsd.org/cgi/ports.cgi">/cgi/ports.cgi</a>
Move the links 'Sources' and 'Package' after 'Description'.<br>
<a href="../news/press.html">/news/press.html</a>
Add pointer to Linuxworld article.
<p></p></li>
<li><b>17-Dec-1998</B><br>
<a href="../">/index.html</a>
Remove index.html, replace with index.sgml<br>
Reordered the two main columns. A new row has been added at the top,
and the second column (as it appears in a graphical browser) is in
this row. The left hand side bar is in the second row. Text browsers
should then display the main text first, with the quick links
afterwards. The display on graphical browsers should be almost
identical to how it was before.<br>
<a
href="..//releases/2.2.8R/errata.html">/releases/2.2.8R/errata.html</a>
Better errata fix.
<p></p></li>
<li><b>16-Dec-1998</B><br>
<a href="../commercial/software.html">/commercial/software.html</a>
Added: Software2Go, LLC is proud to announce the availability of
Motif 2.1.10 for FreeBSD versions 2.2.x (a.out) and 3.0 (ELF).<br>
<a href="../projects/projects.html">/projects/projects.html</a>
Added: Linux Threads under FreeBSD
<P></P></LI>
<li><b>15-Dec-1998</B><br>
<a href="../internal/photos.html">/internal/photos.html</a>
Added a link to page about the FreeBSD-UK meet in Oxford
<P></P></LI>
<li><b>14-Dec-1998</B><br>
<a href="../cgi/query-pr-summary.cgi">/cgi/query-pr-summary.cgi</a>
Quote arguments to query-pr so that multi-word arguments can be used
in the query.
<P></P></LI>
<li><b>13-Dec-1998</B><br>
<a href="../news/newsflash.html">/news/newsflash.html</a>
Added entry for the FreeBSD Mall.<br>
<a href="../news/press.html">/news/press.html</a>
Added: Mercury
Center October 26, 1998 Unix back in the fight with NT, by Miguel
Helft<br>
Added: News.com February 2, 1998 Source code for the
masses, by Alex Lash<br>
<a href="../mailto.html">/mailto.html</a>
Added the FreeBSD Mall to the snail mail section.<br>
<a href="../support.html">/support.html</a>
Added Los Angeles based BSD user group
<P></P></LI>
<li><b>12-Dec-1998</B><br> <a
href="../docs.html">/docs.html</a>
Added FreeBSD 2.2.8 manual pages.
<P></P></LI>
<li><b>9-Dec-1998</B><br> <a
href="../commercial/consulting.html">/commercial/consulting.html</a>
Added HCS Hanseatischer Computerservice GmbH
<P></P></LI>
<li><b>8-Dec-1998</B><br>
<a href="../ports/">/ports/</a>
Due a bug in INDEX parsing only the run dependencies where printed.
<br>
<a href="../news/press.html">/news/press.html</a>
Added: RELEASE 1.0 November 1998 The Open-Source Revolution, by Tim
O'Reilly, with an introduction by Esther Dyson.<br>
<a href="../commercial/hardware.html">/commercial/hardware.html</a>
Update for Apache Digital Corporation
<P></P></LI>
<li><b>6-Dec-1998</B><br>
<a href="../y2kbug.html">/y2kbug.html</a>
Update info about Y2K fix in groff.<br>
<a href="../internal/statistic.">/internal/statistic.html</a>
New record for ftp.freebsd.org FTP traffic.<br>
<a href="../news/press.html">/news/press.html</a>
Added: NET News.com November 16, 1998 Ellison plans hardware, bashes
Bill, By Tim Clark Larry Ellsion talking about their new dedicated
Oracle servers, mentions FreeBSD as one of a list of candidate OSs
for the platform.<br>
Added: Linux Today November 20th, 1998 Report from Comdex--Walnut
Creek CDROM, FreeBSD and Slackware by Dwight Johnson<br>
Added: CNET News.com June 14, 1998 Nader urges Windows probe, By Jeff
Pelline Consumer-rights advocate Ralph Nader mentioned FreeBSD by
name.<br>
<a href="../commercial/software.html">/commercial/software.html</a>
Added the Network shell.<br>
<a href="../ports/">/ports/</a>
Bugfix in ur.cgi: Dots a vaild parts of a port name (shudder). E.g.:
ports/russian/elm.language<br>
<a href="../commercial/consulting.html">/commercial/consulting.html</a>
Added ASG Technologies.
<P></P></LI>
<li><b>4-Dec-1998</B><br> <a
href="../news/qnewsletter.html">/news/qnewsletter.html</a>
Added Quick NewsLetter Volume #1 Issue #7.
<P></P></LI>
<li><b>3-Dec-1998</B><br> <a
href="../news/newsflash.html">/news/newsflash.html</a>
Announce 2.2.8R.
<P></P></LI>
</UL>
&newshome;
&footer;
</body>
</html>

43
es/ports/Makefile Normal file
View file

@ -0,0 +1,43 @@
# $Id: Makefile,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
PORTINDEX= perl ${.CURDIR}/portindex
INDEX= INDEX
PINDEX= ports/${INDEX}
COOKIE= ${INDEX} Makefile.gen
.if exists(Makefile.gen)
.include "Makefile.gen"
.endif
CLEANFILES+= ${DOCS} Makefile.gen ${INDEX} packages.exists
cvsindex= $${CVSROOT}/${PINDEX},v
_ALLINSTALL= packages.exists ${INDEX}
${INDEX}: ${cvsindex}
cvs -QR co -p ${PINDEX} > ${INDEX}
# build the list of available packages only on the
# main FreeBSD machines
hostname!= hostname
packages.exists: ${cvsindex}
.if ${hostname} == "hub.freebsd.org" || ${hostname} == "freefall.freebsd.org"
sh ${.CURDIR}/packages > ${.TARGET}
.else
touch ${.TARGET}
.endif
Makefile.gen: index.sgml .NOTMAIN
echo DOCS= *.sgml > Makefile.gen
${MAKE} ${MAKEFLAGS} ${.IMPSRC}
index.sgml: ${INDEX} packages.exists portindex ports.inc .NOTMAIN
rm -f *.sgml
${PORTINDEX} ${INDEX}
.include "../web.mk"

66
es/ports/categories Executable file
View file

@ -0,0 +1,66 @@
# From src/release/sysinstall/index.c,v 1.57 1998/10/15
"applications", "User application software.",
"astro", "Applications related to astronomy.",
"archivers", "Utilities for archiving and unarchiving data.",
"audio", "Audio utilities - most require a supported sound card.",
"biology", "Software related to Biology.",
"benchmarks", "Utilities for measuring system performance.",
"cad", "Computer Aided Design utilities.",
"chinese", "Ported software for the Chinese market.",
"comms", "Communications utilities.",
"converters", "Format conversion utilities..",
"databases", "Database software.",
"devel", "Software development utilities and libraries.",
"deskutils", "Various Desktop utilities.",
"documentation", "Document preparation utilities.",
"editors", "Common text editors.",
"elisp", "Emacs lisp ports.",
"emulators", "Utilities for emulating other OS types.",
"games", "Various and sundry amusements.",
"german", "Ported software for Germanic countries.",
"graphics", "Graphics libraries and utilities.",
"japanese", "Ported software for the Japanese market.",
"kde", "Software for the K Desktop Environment.",
"korean", "Ported software for the Korean market.",
"lang", "Computer languages.",
"languages", "Computer languages.",
"libraries", "Software development libraries.",
"mail", "Electronic mail packages and utilities.",
"math", "Mathematical computation software.",
"mbone", "Applications and utilities for the mbone.",
"misc", "Miscellaneous utilities.",
"net", "Networking utilities.",
"news", "USENET News support software.",
"numeric", "Mathematical computation software.",
"offix", "An office automation suite of sorts.",
"orphans", "Packages without a home elsewhere.",
"perl5", "Utilities/modules for the PERL5 language..",
"pilot", "Software support for the USR Palm Pilot(tm).",
"plan9", "Software from the plan9 Operating System.",
"print", "Utilities for dealing with printing.",
"printing", "Utilities for dealing with printing.",
"programming", "Software development utilities and libraries.",
"python", "Software related to the python language.",
"russian", "Ported software for the Russian market.",
"security", "System security software.",
"shells", "Various shells (tcsh, bash, etc).",
"sysutils", "Various system utilities.",
"textproc", "Text processing/search utilities.",
"tcl75", "TCL v7.5 and packages which depend on it.",
"tcl76", "TCL v7.6 and packages which depend on it.",
"tcl80", "TCL v8.0 and packages which depend on it.",
"tcl81", "TCL v8.1 and packages which depend on it.",
"tk41", "Tk4.1 and packages which depend on it.",
"tk42", "Tk4.2 and packages which depend on it.",
"tk80", "Tk8.0 and packages which depend on it.",
"tk81", "Tk8.1 and packages which depend on it.",
"troff", "TROFF Text formatting utilities.",
"vietnamese", "Ported software for the Vietnamese market.",
"www", "WEB utilities (browers, HTTP servers, etc).",
"x11", "X Window System based utilities.",
"x11-clocks", "X Window System based clocks.",
"x11-fm", "X Window System based file managers.",
"x11-fonts", "X Window System fonts and font utilities.",
"x11-toolkits", "X Window System based development toolkits.",
"x11-wm", "X Window System Window Managers.",

18
es/ports/packages Executable file
View file

@ -0,0 +1,18 @@
#!/bin/sh
# Copyright (c) June 1998 Wolfram Schneider <wosch@FreeBSD.ORG>, Berlin.
#
# packages - create a sorted list of precompiled packages which
# are available at the FreeBSD FTP Server.
#
# $Id: packages,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
PATH=/bin:/usr/bin:/usr/local/bin; export PATH
release='packages-stable';
url="ftp://ftp.freebsd.org/pub/FreeBSD/$release/All/"
lynx -source "$url" |
perl -ne 'print $1, "\n" if m%href="([^"]+)"%oi' |
perl -npe 's%.*/%%' | sort | grep -v '^\.\.$'

262
es/ports/portindex Executable file
View file

@ -0,0 +1,262 @@
#!/usr/bin/perl
# convert a ports INDEX file to HTML
#
# by John Fieber <jfieber@freebsd.org>
# Mon May 13 10:31:58 EST 1996
############################################################
# Load local config file. You can override in portindex.conf
# the variables for the default web and the ftp server. This
# make it easy to maintain a local web mirror and let the
# URL point to yourself and not to the standard FreeBSD FTP server.
$config = $0 . '.' . 'conf';
do $config if -f $config;
# This is the base of where we ftp stuff from
if ($ENV{'MASTER_FTP_SERVER'}) {
$ftpserver = $ENV{'MASTER_FTP_SERVER'};
} else {
$ftpserver = 'ftp://ftp.freebsd.org' if !$ftpserver;
}
$base = "$ftpserver/pub/FreeBSD/FreeBSD-current" if !$base;
$baseHTTP = $base if !$baseHTTP;
$urlcgi = 'http://www.freebsd.org/cgi/url.cgi' if !$urlcgi;
$packagesURL = "$ftpserver/pub/FreeBSD/packages-stable/All/"
if !$packagesURL;
# support tar on the fly or gzip'ed tar on the fly
$ftparchive = 'tar' if !$ftparchive;
# ports download sources script
$pds = 'http://www.freebsd.org/cgi/pds.cgi';
# better layout and link to the sources
if ($urlcgi) {
$baseHTTP = $urlcgi . '?' . $baseHTTP;
}
$today = &getdate;
&packages_exist('packages.exists', *packages);
&category_description('categories', *category_description);
&main;
sub getdate {
@months = ("January", "February", "March", "April", "May","June",
"July", "August", "September", "October", "November", "December");
($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
$year += 1900;
return "Updated $months[$mon] $mday, $year";
}
sub header {
local ($fh, $htext) = @_;
print $fh "<!DOCTYPE html PUBLIC \"-//W3C//DTD HTML 3.2//EN\" [\n";
print $fh "<!ENTITY base CDATA '..'>";
print $fh "<!ENTITY date \"<em>$today</em>\">\n";
print $fh "<!ENTITY title '$htext'>";
print $fh "<!ENTITY blurb SYSTEM \"ports.inc\">\n";
print $fh "<!ENTITY % includes SYSTEM \"../includes.sgml\">\n";
print $fh "<!ENTITY email 'ports'>";
print $fh "%includes;\n";
print $fh "]>\n";
print $fh "<html>&header;\n";
}
sub footer {
local ($fh, $ftext) = @_;
print $fh "\n$ftext\n";
print $fh "&footer;\n";
print $fh "</BODY>\n</HTML>\n";
}
sub packages_exist {
local($file, *p) = @_;
open(P, $file) || do {
warn "open $file: $!\n";
warn "Cannot create packages links\n";
return 1;
};
while(<P>) {
chop;
$p{$_} = 1;
}
close P;
return 0;
}
sub category_description {
local($file, *p) = @_;
open(P, $file) || do {
warn "open $file: $!\n";
warn "Cannot find category description\n";
return 1;
};
local($category, $description);
while(<P>) {
# ignore comments
next if /^\s*#/;
($category, $description) = /^\s*"([^"]+)",\s*"([^"]+)/;
$p{$category} = $description;
}
close P;
return 0;
}
sub main {
$sep = "<B>:</B>";
while (<>) {
chop;
s/&/&amp;/g;
s/</&lt;/g;
s/>/&gt;/g;
# Read a record
($name, $loc, $prefix, $desc, $ldesc, $owner, $cats,
$bdep, $rdep) = split('\|');
# Check for double hyphens in the name (--).
$name =~ s/--/-/g;
# Split the categories into an array
@cat = split("[ \t]+", $cats);
$catkey{$name} = $cat[0];
local($sourcepath) = $loc;
$sourcepath =~ s%/usr/%%;
foreach $i (@cat) {
$stats{$i}++;
# figure out the FTP url
$loc =~ s/\/usr/$base/;
$ldesc =~ s/\/usr/$baseHTTP/;
# The name description and maintainer
$data{$i} .= "<DT><B><A NAME=\"$name\"></A><A HREF=\"$loc.$ftparchive\">$name</A></B> ";
$data{$i} .= "<DD>$desc<BR><A HREF=\"$ldesc\">Long description</A>";
if ($packages{"$name.tgz"}) {
$data{$i} .= qq{ | <a href="$packagesURL$name.tgz">Package</a>};
}
$data{$i} .= qq{ | <A HREF="$pds?$sourcepath">Sources</A>};
$ownerurl = $owner;
$ownerurl =~ s/&lt;/</g;
$owenrurl =~ s/&gt;/>/g;
$data{$i} .=
"<BR><I>Maintained by:</I> <A HREF=\"mailto:$ownerurl\">$owner</A>";
# If there are any dependencies, list them
if ($bdep ne "" || $rdep ne "") {
$data{$i} .= "<BR><I>Requires:</I> ";
@dep = split(/ /, "$bdep $rdep");
local($last) = '';
foreach $j (sort @dep) {
next if $j eq $last;
$last = $j;
$data{$i} .= " <A HREF=\"##$j##.html#$j\">$j</A>,";
}
# remove the trailing comma
chop $data{$i};
}
# If the port is listed in more than one category, throw
# in some cross references
if ($#cat > 0) {
$data{$i} .= "<BR><EM>Also listed in:</EM> ";
foreach $j (@cat) {
if ($j ne $i) {
if ($j eq $cat[0]) {
$data{$i} .= " <STRONG><A HREF=\"$j.html#$name\">\u$j</A></STRONG>,";
}
else {
$data{$i} .= " <A HREF=\"$j.html#$name\">\u$j</A>,";
}
}
}
# remove the trailing comma
chop($data{$i});
}
$data{$i} .= "<P></P></DD>\n"
}
# Add an entry to the master index
# workaround for SGML bug, `--' is not allowed in comments
local ($sname) = $name;
$sname =~ s/--/-=/g;
$master[$portnumber] =
"<!-- $sname --><STRONG><A HREF=\"$cat[0].html#$name\">$name</A></STRONG> " .
" -- <EM>$desc</EM><BR>\n";
$portnumber++;
}
open(MOUTF, ">index.sgml");
&header(MOUTF, "FreeBSD Ports");
# print MOUTF "<!--#include virtual=\"./ports.inc\" -->\n";
print MOUTF "&blurb;";
print MOUTF "<hr><P>There are currently $portnumber ports in the
FreeBSD Ports Collection.<br> <A HREF=\"$base/ports.tar.gz\">Download
a gzip'd tar file of all $portnumber ports</A> (about 5 megabytes) or
browse the following categories:\n";
print MOUTF "<UL>\n";
@foos = sort(keys %stats);
foreach $key (@foos) {
# For the master file...
print MOUTF
"<LI><A HREF=\"$key.html\">\u$key</A> <em>($stats{$key})</em>";
if ($category_description{$key}) {
print MOUTF " -- " . $category_description{$key};
}
print MOUTF "</LI>\n";
# Create the category file
open(OUTF, ">$key.sgml");
&header(OUTF, "FreeBSD Ports: \u$key");
if ($category_description{$key}) {
print OUTF "<h3>", $category_description{$key}, "</h3>\n";
}
print OUTF "<DL>\n";
$d = join("\n", sort(split(/\n/, $data{$key})));
$d =~ s/##([^#]*)##/$catkey{$1}/g;
print OUTF $d;
print OUTF "</DL>\n";
&footer(OUTF, "<HR><A HREF=\"index.html\">Port Categories</A>" .
" -- <A HREF=\"master-index.html\">Index</A><HR>");
close(OUTF);
}
print MOUTF "</UL>\n";
print MOUTF
"<UL><LI><A HREF=\"master-index.html\">Alphabetical list of all $portnumber ports</A></LI></UL>\n";
&footer(MOUTF, "");
close(MOUTF);
# Create the master index file
open(MINDEX, ">master-index.sgml");
&header(MINDEX, "FreeBSD Ports Collection Index");
print MINDEX "<P>\n";
print MINDEX sort @master;
print MINDEX "</P>";
&footer(MINDEX, "<HR><A HREF=\"index.html\">Port Categories</A><HR>");
close(MINDEX);
}

73
es/ports/ports.inc Normal file
View file

@ -0,0 +1,73 @@
<!-- $Id: ports.inc,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<p>La colecci&oacute;n de Ports y Packages de FreeBSD ofrece una manera
sencilla de instalci&oacute;n de aplicaciones para los usuarios y
administradores. Cada "port" listado aqu&iacute; contiene los parches
necesarios para hacer que la aplicaci&oacute;n original compile y
se ejecute en FreeBSD. Instalar una aplicaci&oacute;n es t&aacute;n
sencillo como obtener el ports, descomprimirlo y teclear <tt>make</tt>
dentro del directorio del port. El <tt>Makefile</tt> automaticamente
se encarga de obtener el c&oacute;digo fuente de la aplicaci&oacute;n ya sea
del disco local, CDROM o v&iacute;a FTP, descomprimirla, aplicar los
parches necesarios y compilarla. Si todo fue bi&eacute;n, un simple
<tt>make install</tt> instalar&aacute; y registrar&aacute; la aplicaci&oacute;n
en el sistema.</p>
<p>Para muchos ports, existe un <tt>package</tt> precompilado, ahorrando
al usuario el trabajo de tener que compilar cada una de ellas. Cada port
contiene un link a su correspondiente package, con lo que solo tienes que
bajarte el fichero y ejecutar el comando <strong>pkg_add</strong>. Este
comando acepta tanto nombres de ficheros como URL's FTP.</p>
<p>Para m&aacute;s informaci&oacute;n sobre el uso de los ports mira en <a
href="../handbook/ports.html">La colecci&oacute;n de Ports</a>. Para
informaci&oacute;n sobre crear nuevos ports, mira en <a
href="../handbook/porting.html">Porting applications</a>. Ambos son parte
del <a href="../handbook">Handbook</a>.</p>
<p>Los ports listados en estas p&aacute;ginas son continuamente actualizados.
Consecuentemente, quiz&aacute;s necesites actualizar algunos ficheros en tu
sistema FreeBSD para poder usar los ports desarrollados posteriormente a la
fecha en la que tu versi&oacute; fue lanzada.
Si eres usuario de 2.2.1-release por favor instala el <a
href="ftp://ftp.freebsd.org/pub/FreeBSD/packages-stable/Latest/221upgrade.tgz">
kit de actualizaci&oacute;n de ports de 2.2.1 a 2.2-stable</a>; si eres usuario
de 2.2.2-release, por favor instala el <a
href="ftp://ftp.freebsd.org/pub/FreeBSD/packages-stable/Latest/222upgrade.tgz">
kit de actualizaci&oacute;n de ports a 2.2-stable</a>; si eres usuario de
2.2.5-release, por favor, instala el <a
href="ftp://ftp.freebsd.org/pub/FreeBSD/packages-stable/Latest/225upgrade.tgz">
kit de actualizaci&oacute;n a 2.2-stable</a>; si eres usuario de 2.2.6, 2.2.7
o 3.0-release, por favor, instala el <a
href="ftp://ftp.freebsd.org/pub/FreeBSD/packages-stable/Latest/227upgrade.tgz">
kit de actualizaci&oacute;n a 2.2-stable</a>.
Estos son packaes de FreeBSD; por favor usa pkg_add para instalarlos. Esto
deber&iacute;a hacer que puedas usar todos los ports listados aqu&iacute;, ten
en cuenta que solo se modificar&aacute;n algunos ficheros para permitir
que los ports/packages puedan ser usados; para una actualizaci&oacute;n
completa a 2.2-stable, por favor, mira en la secci&oacute;n <a
href="../handbook/synching.html">sincronizando el c&oacute;digo fuente</a>
del handbook. Recomendamos una actualizaci&oacute;n completa, especialmente
si todav&iacute;a est&aacute;s usando 2.2.1-release o 2.2.2-release.</p>
<p>Muchos de los ports requieren el sistema X Window para compilar y
ejecutarse. Nosotros compilamos y testeamos nuestros ports con <a
href="http://www.xfree86.org/">XFree86</a>. Su versi&oacute;n actual es
3.3.3. Algunos ports no trabajar&aacute;n con releases m&aacute;s
antiguas.</p>
<p>Para m&aacute;s informaci&oacute;n sobre ports/packages nuevos, modificados
o borrados, o si quieres buscar una aplicaci&oacute;n espec&iacute;fica, por
favor, mira en la p&aacute;gina de
<a href="http://www.freebsd.org/cgi/ports.cgi">Mantenimiento de Ports</a></p>
<FORM METHOD="GET" ACTION="http://www.freebsd.org/cgi/ports.cgi">
Buscar:
<INPUT NAME="query" VALUE="">
<SELECT NAME="stype">
<OPTION VALUE="all">Todo</OPTION>
<OPTION VALUE="name">Nombre Package</OPTION>
<OPTION VALUE="text">Descripci&oacute;n</OPTION>
</SELECT>
<INPUT TYPE="submit" VALUE="Enviar">
</FORM>

13
es/projects/Makefile Normal file
View file

@ -0,0 +1,13 @@
# $Id: Makefile,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
DOCS= projects.sgml
DOCS+= mozilla.sgml
DOCS+= newbies.sgml
INDEXLINK= projects.html
.include "../web.mk"

89
es/projects/mozilla.sgml Normal file
View file

@ -0,0 +1,89 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title 'FreeBSD Mozilla Group'>
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: mozilla.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<h2>Overview</h2>
<p>Following <a href="http://www.netscape.com/">Netscape</a>'s
decision to publically release the source code for their client
product, otherwise known as <a href="http://www.mozilla.org/">Mozilla</a>,
a number of free software groups have become actively involved in
supporting and improving this technology for their own uses. The
<em>FreeBSD Mozilla Group</em> seeks to provide a focus for such
work in the FreeBSD world, providing centralized resources such as a
CVS repository, a mailing list and other tools for collaborative
development.</p>
<h2>Resources</h2>
<dl>
<!--
<dt><a href="http://www.freebsd.org/cgi/cvsweb.cgi?cvsroot=mozilla">WEB Interface</a></dt>
<dd>CVSweb provides a web-based interface for viewing the <a
href="http://www.freebsd.org/cgi/cvsweb.cgi">CVS repository</a>,
being able to select and compare specific revisions of the various
files within it.</dd>
-->
<dt><a href="../handbook/cvsup.html">CVSup</a></dt>
<dd>CVSup provides ongoing syncronization with the central Mozilla
repository, either for the CVS bits themselves (for those wishing to
keep a local repository) or for a "checked out" version, suitable for
directly building or editing. Fetch the CVSup binaries from
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/">
ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/</a> and use a supfile
which looks something like this:
<pre>
*default prefix=/usr/src/mozilla base=/usr/src/mozilla host=mozilla.FreeBSD.org release=cvs delete compress use-rel-suffix tag=.
## Main Source Tree
cvs-mozilla
</pre></dd>
<dt><a href="../handbook/anoncvs.html">anoncvs</a></dt>
<dd>Anonymous CVS allows anyone to check things out of the FreeBSD
Mozilla repository using the standard <tt>cvs(1)</tt> commands.
Simply set your <em>CVSROOT</em> environment variable to point to:
<pre>
anoncvs@mozilla.freebsd.org:/mozilla
</pre>
<p>And you can then use <tt>cvs(1)</tt> for doing read-only operations
on the Mozilla CVS repository.</dd>
<dt><a href="mailto:freebsd-mozilla@freebsd.org">freebsd-mozilla</a></dt>
<dd>The FreeBSD-mozilla mailing list is provided for developers and
users of the FreeBSD mozilla port to discuss issues relating to building,
using and managing the mozilla sources and any FreeBSD-specific changes
to them. To subscribe, send mail to <a
href="mailto:majordomo@freebsd.org">majordomo@freebsd.org</a> and
say <em>subscribe freebsd-mozilla</em> in the body of your message.</dd>
</dl>
<h2>More information</h2>
<dl>
<dt><a href="http://www.mozilla.org/">Mozilla.ORG</a></dt>
<dd>The Mozilla.org project provides central control over Mozilla
for all platforms, not just FreeBSD.</dd>
<dt><a href="http://www.cyclic.com/">Cyclic Software</a></dt>
<dd>Cyclic Software has some good on-line tutorials on CVS</dd>
</dl>
&footer;
</body>
</html>

255
es/projects/newbies.sgml Normal file
View file

@ -0,0 +1,255 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title 'Recursos para Principiantes'>
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: newbies.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>Los siguientes recursos son algunos de los que los principiantes de
FreeBSD han encontrado m&aacute;s &uacute;tiles para aprender el uso
de FreeBSD. Por favorm env&iacute;a correcciones y ampliaciones a
<a href="mailto:freebsd-newbies@freebsd.org">FreeBSD-Newbies@FreeBSD.org
</a>.</p>
<ul>
<li><a href="#web-site">Usando el servidor Web de FreeBSD</a></li>
<li><a href="#fbsd">Aprendiendo sobre FreeBSD</a></li>
<li><a href="#unix">Aprendiendo sobre UNIX</a></li>
<li><a href="#xwin">Aprendiendo sobre el sistema X Window</a></li>
<li><a href="#people">Ayudando a otra personas</a></li>
</ul>
<h2><a name="web-site">Using the FreeBSD web site</a></h2>
<p>This web site is the main source of up to date information about
FreeBSD. Newbies have found the following pages particularly helpful:</p>
<ul>
<li><p><a href="../search/search.html">Search</a> the Handbook and FAQ, or the
whole web site, or the archives of the FreeBSD-Questions mailing
list.</p></li>
<li><p>The <a href="../docs.html">Documentation</a> page has links to the
Handbook and FAQ, tutorials, information about contributing to the
Documentation Project, documents in languages other than English,
and much more.</p></li>
<li><p><a href="../support.html">Support</a> page contains a wealth of
information about FreeBSD, including mailing lists, user groups, web
and FTP sites, release information, and links to some sources of
UNIX information.</p></li>
</ul>
<h2><a name="fbsd">Learning about FreeBSD</a></H2>
<ul>
<li><p>If you haven't installed yet, look for the
&a.latest.ann;latest mainstream release</a>.
(See the Handbook for why you should <strong>not</strong> be tempted
by any of the other branches.) Before you begin, carefully read the
<a href="../handbook/install.html">installation instructions</a>,
as well as each one of the *.TXT files in the FTP directory
or on the installation CD. They are there because they contain information
that you will need. Also pick up the latest
<a href="../releases/index.html">errata file</a>
from the web site, in case it has been updated.</p>
<p>If you decide to download FreeBSD, check whether these illustrated and
expanded <a href="http://www.lemis.com/handbook/what-to-download.html">download
instructions</a> for a previous version are still available before
you begin. That should make the whole process a lot clearer.</p></li>
<li><p>A number of <a href="../tutorials/">tutorials</a> are available. The
one <a href="../tutorials/newuser/newuser.html">For People New to Both
FreeBSD and Unix</a> is popular with absolute beginners. You don't
have to know much about anything to enjoy this one. It is also
available from <a
href="http://andrsn.stanford.edu/FreeBSD/newuser.html">the
author's site</a> and can be downloaded in <a
href="ftp://andrsn.stanford.edu/pub/">postscript or RTF format</a>
for printing.</p></li>
<li><p>The first thing many people need to set up is ppp, and there is
a lot of documentation to help. You might start with at least those
parts of the
<a href="../tutorials/ppp/ppp.html">Pedantic PPP Primer</a>
that are relevant to your needs, and explore the
<a href="http://www.awfulhak.org/ppp.html">ppp page</a>
for links to the other valuable information and the latest updates.</p></li>
<li><p><a name="cfbsd" href="http://www.cdrom.com/titles/os/bsdbook2.htm">The
Complete FreeBSD</a> by Greg Lehey, published by Walnut Creek
CDROM. This book assumes minimal UNIX experience and takes the
beginner step by step through each stage from installation to
everything you need to know to set up and run a FreeBSD system. You
also get to understand what you're doing and why.</p></li>
<li><p>The <a href="../handbook/handbook.html">FreeBSD Handbook</a> and <a
href="../FAQ/FAQ.html">Frequently Asked Questions (FAQ)</a> are the
main documents for FreeBSD. Essential reading, they contain a lot of
material for newbies as well as some pretty advanced stuff. Don't
worry if you can't understand the advanced sections. The handbook
contains the installation instructions and also provides lists of
books and on line resources, and the FAQ has a troubleshooting
section.</p></li>
<li><p>Join the FreeBSD-Questions mailing list to see the questions you
were too afraid to ask, and their answers. Subscribe by sending mail
to <a href="mailto:majordomo@freebsd.org">majordomo@freebsd.org</a>
with "subscribe freebsd-questions" on its own in the message body
(the subject doesn't matter). You can look up old questions and
answers via the <a href="../search/search.html#mailinglists">search</a>
page.</p></li>
<li><p>The main newsgroup for FreeBSD is <a
href="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</a>. You might want to keep an eye on <a href="news:comp.unix.bsd.freebsd.announce">comp.unix.bsd.freebsd.announce</a> as well.</p></li>
<li><p><strong>Man pages</strong> are good for reference but not always
the best introduction for a novice. The more you work with man pages
the more familiar they become. Some are very good for newbies, so
always check them out. The ppp man page, for example, is more like a
tutorial.</p></li>
</ul>
<h2><a name="unix">Learning about UNIX</a></h2>
<p>Many of the problems we have as newbies come from being unfamiliar
with the UNIX commands needed to fix our FreeBSD problems.
Without a UNIX background you'll be faced with two things to learn
at once. Fortunately a lot of resources are available to make this
easier.</p>
<ul>
<li><p>There are many easy books, such as the "Dummies" guides, in any
large book shop. If you want something really easy, take a look at
what is available and pick one that seems to speak your language.
Pretty soon you will want to move on to a book that gives more
coverage.</p></li>
<li><p>One book mentioned frequently by newbies is <a name="ufti"><em>UNIX for
the Impatient</em></a> by Paul W. Abrahams and Bruce R. Larson, published
by Addison-Wesley. It is intended both as a book for learning UNIX
and a reference, and includes an introduction to UNIX concepts and
handy chapter on using the X Window System.</p></li>
<li><p>Another popular book is <em>UNIX Power Tools</em> by Jerry Peek,
Tim O'Reilly and Mike Loukides, published by O'Reilly and
Associates. It is organised as a series of short articles each of
which solves a problem, and these articles are cross-referenced to
other articles with related material. Though not specifically aimed
at newbies, the design makes it ideal for a newbie with a burning
question or the odd few minutes to browse. More elementary material
is near the front of the book, but there are short easy articles
throughout.</p></li>
<li><p>A <a
href="http://www-wks.acs.ohio-state.edu/unix_course/unix.html">UNIX Introductory Course</a>
from Ohio State University is available online in HTML,
postscript and Acrobat PDF formats.</p></li>
<li><p><a href="http://www.ucs.ed.ac.uk/~unixhelp/servers.html">UNIXhelp
for Users</a> is another introductory guide which is available in
HTML at a mirror site near you, or can be installed on your own
system.</p></li>
<li><p>UNIX questions are dealt with in the newsgroup <a
href="news:comp.unix.questions">comp.unix.questions</a> and the
associated <a
href="http://www.cis.ohio-state.edu/hypertext/faq/usenet/unix-faq/faq/top.html"> Frequently Asked Questions</a>. You can also get a copy of the <a href="ftp://rtfm.mit.edu/pub/usenet/news.answers/unix-faq/faq/">FAQ</a>
from the RMIT FTP site. Newbies are likely to be most interested in
sections 1 and 2 initially.</p></li>
<li><p>Another interesting newsgroup is <a
href="news:comp.unix.user-friendly">comp.unix.user-friendly</a>
which also has a <a
href="http://www.camelcity.com/~noel/usenet/cuuf-FAQ.htm">FAQ</a>.
Although this newsgroup is for discussing user-friendliness, it can
contain some good information for newbies. The <a
href="ftp://rtfm.mit.edu/pub/usenet/news.answers/unix-faq/user-friendly">FAQ</a> is also available by FTP.</p></li>
<li><p>Many other web sites hold lists of UNIX tutorials and reference
material. One of the best places to start looking is the UNIX page
at <a
href="http://www.yahoo.com/Computers_and_Internet/Software/Operating_Systems/Unix/">Yahoo!</a>.</p></li>
</ul>
<h2><a name="xwin">Learning about the X Window System</a></h2>
<p>The X Window System is used with a number of operating systems,
including FreeBSD. The documentation for X can be found at
<a href="http://www.xfree86.org/">The XFree86 Project, Inc.</a>,
including the
<a href="http://www.xfree86.org/FAQ/index.html">XFree86 FAQ</a>.
Beware, much of this documentation is reference material which is
likely to be difficult for newcomers to digest.</p>
<ul>
<li><p>For basic information about installing, configuring and using the
X Window System, two of the books mentioned above have sections
dealing with X at beginner level:
<a href="#cfbsd">The Complete FreeBSD</a> and
<a href="#ufti">UNIX for the Impatient</a>.</p></li>
<li><p>There is an easy and informative section on
<a href="http://linuxwww.db.erau.edu/LUG/node41.html">using
the X Window System</a> in the Linux
<a href="ftp://sunsite.unc.edu/pub/Linux/docs/LDP/users-guide">Users' Guide</a>.
Interesting material will be found elsewhere in that document too, but
remember that Linux does not always work exactly the same as FreeBSD.</p></li>
<li><p>Before you can get X running exactly the way you like, you will need
to choose a window manager.
Visit the <a href="http://www.PLiG.org/xwinman/">Window Managers for X</a>
page and follow the link to the introduction to find out about window
managers, then return and read "The Basics". Then go back and compare
the different types that are available. (Bonus: there's another
beginners guide to UNIX there too.)
Most if not all of these window managers are available to
install from the FreeBSD ports collection.</p></li>
</ul>
<h2><a name="people">Helping other people</a></h2>
<p>Everyone has something to contribute to the FreeBSD community, even
newbies! Some are busy working with the new advocacy group and some have
become involved with the
<a href="../docproj/docproj.html">Documentation Project</a> as reviewers.
Other FreeBSD newbies might have particular skills and experiences to
share, either computer related or not, or just want to meet new
newbies and make them feel welcome. There's always people around
who help others simply because they like to. Write to
<a href="mailto:freebsd-newbies@freebsd.org">FreeBSD Newbies</a>
for more information.</p>
<p>Friends who run FreeBSD are a great resource. No book can replace
chatting on the phone or across a pizza with someone who has the
same interests, enjoys similar accomplishments, and faces the same
challenges. If you don't have many friends who use FreeBSD,
consider using your old FreeBSD CDs to create some more :-)</p>
<p><a href="../support.html#user">User groups</a> are
good places to meet other FreeBSD users. If there's not one nearby,
maybe you could start one.</p>
<p>Before talking to real humans about your new skills, you might
want to check the <a
href="http://manuel.brad.ac.uk/help/.faq/.unix/.pronun.html">Pronunciation Guide</a>
and the <a
href="http://www.wins.uva.nl/~mes/jargon/">Jargon File</a> :-)</p>
<p>On line we have the
<a href="http://www.welearn.com.au/freebsd/newbies/">FreeBSD-Newbies</a>
mailing list for non-technical discussions about matters of interest
to newbies. Another mailing list,
<a href="mailto:questions@freebsd.org">FreeBSD-Questions</a>,
answers our questions about using FreeBSD.</p>
&footer;
</body>
</html>

307
es/projects/projects.sgml Normal file
View file

@ -0,0 +1,307 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Proyectos de desarrollo de FreeBSD">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: projects.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<a name="development"></a>
<p>Sum&aacute;ndose a la l&iacute;nea de desarrollo principal de FreeBSD,
existe una serie de desarrolladores trabajando en la creaci&oacute;n de
aplicaciones en otras direcciones. Sigue los links siguientes para
saber m&aacute;s sobre estos excitantes proyectos.</p>
Si tienes un proyecto en marcha, por favor, env&iacute;a la URL y una
peque&ntilde;a descripci&oacute;n (3-10 l&iacute;neas) a
<A HREF="../mailto.html">www@FreeBSD.ORG</A>
<ul>
<li><a href="#documentation">Documentaci&oacute;n</a>
<li><a href="#advocacy">Publicidad</a>
<li><a href="#applications">Aplicaciones</a>
<li><a href="#networking">Networking</a>
<li><a href="#filesystem">Sistemas de ficheros</a>
<li><a href="#kernelandsecurity">Kernel y Seguridad</a>
<li><a href="#devicedrivers">Drivers</a>
<li><a href="#architecture">Arquitectura</a>
<li><a href="#misc">Varios</a>
</ul>
<p>
<a name="documentation"></a>
<h3>Documentaci&oacute;n</h3>
<ul>
<li><a href="../docproj/docproj.html">Proyecto de Documentaci&oacute;n
de FreeBSD</a></li>
<li><a name="newbies" href="newbies.html">Recursos para principiantes de
FreeBSD</a></li>
<li><a name="retail" href="http://www.bafug.org/Retail.html">
Documentos varios sobre FreeBSD</a>
<li><a name="securityhowto" href="http://www.freebsd.org/~jkb/howto.html">
How-to de seguridad en FreeBSD</a>
FreeBSD es un sistema operativo muy seguro. Debido a que el
c&oacute;digo fuente est&aacute; disponible libremente, el S.O. es
continuamente revisado y auditado. Aqu&iacute; tienes una serie de
consejos sobre como hacer un sistema m&aacute;s seguro.
<li><IMG SRC="../../gifs/new.gif" ALT="[New!]" HEIGHT="11" WIDTH="28">
<a name="BSDsites" href="http://www.itworks.com.au/~gavin/FBSDsites.php3">
RELEASE/SNAP finder for FreeBSD FTP servers</a>.
A resource that would allow anyone to find a FTP server that contains
particular releases and SNAP of FreeBSD. The database is updated daily
at 3am Melbourne time (10 hours ahead of GMT).</li>
<li><IMG SRC="../../gifs/new.gif" ALT="[New!]" HEIGHT="11" WIDTH="28">
<a name="diary" href="http://www.freebsddiary.com/freebsd/">
The FreeBSD Diary</a>
This page is about my experiences with FreeBSD. How I installed it,
where I got the idea behind it, and how hard/easy it was to install.
Hopefully, you'll find it to be amusing, interesting, or at the least,
pathetic. My aim is to document what I've done and at the same time
allow others to follow the progress and possibly learn from my
endeavours.
<li><IMG SRC="../../gifs/new.gif" ALT="[New!]" HEIGHT="11" WIDTH="28">
<a name="freebsduserguide" href="http://www.aei.ca/~malartre/freebsd/">
The FreeBSD User Guide</a>
This is a little document on how to start with the FreeBSD Operating
System (OS), a Unix variant. It's made for people who never used a
Unix OS. FreeBSD is a little hard to learn, so don't expect to be
happy the first time you meet him alone. The main reason is that it's
Command Line Interface (CLI), like MS-DOS.
</li>
<li><A HREF="http://www.vmunix.com/fbsd-book/"> A Comprehensive
Guide to FreeBSD</A> - an attempt at a more readable,
"book-like" tutorial explaining the FreeBSD Operating
System. Intended for people new to both FreeBSD and
UNIX. Currently a work in progress.
</li>
<li><A HREF="http://flag.blackened.net/freebsd/"> FreeBSD
How-To's for the Lazy and Hopeless</A> is another somewhat more
light-hearted attempt to provide more readable "how-to" style
information on setting up and configuring FreeBSD.</li>
<li><A
HREF="http://sunsite.unc.edu/LDP/HOWTO/mini/Linux+FreeBSD-mini-HOWTO.html">The
Linux+FreeBSD mini-HOWTO</a> - this document describes how to
use Linux and FreeBSD on the same system. It introduces FreeBSD
and discusses how the two operating systems can cooperate,
e.g. by sharing swap space.
</li>
<li><a href="http://www.freebsd.org/~rpratt/227/index.html">
Install Preview for FreeBSD 2.2.7</a>
This is a guide illustrating the FreeBSD install program for
those new to unix and/or FreeBSD. </li>
<li><IMG SRC="../../gifs/new.gif" ALT="[New!]" HEIGHT="11" WIDTH="28">
<a name="vmoverview"
href="http://www.backplane.com/FreeBSD/FreeBSDVM.txt">FreeBSD VM
System Overview</a> The document is meant to describe the general
workings of FreeBSD's VM system to interested parties.</li>
</ul>
<a name="advocacy"></a>
<h3>Publicidad y relaciones</h3>
<ul>
<li><li><IMG SRC="../../gifs/new.gif" ALT="[New!]" HEIGHT="11" WIDTH="28">
<a name="freebsdrocks" href="http://www.freebsdrocks.com/">FreeBSD
Rocks</a> is an initiative designed to provide the FreeBSD
community with the latest FreeBSD news, software and resources.
All areas include search facilities, making keyword searching of
historical posts a breeze. The pages are updated daily and
everyone is invited to sign up an post an article. If it happened
today, you'll see it on FreeBSDRocks.
</li>
<li><a name=bsdvlin
href="http://www.futuresouth.com/~fullermd/freebsd/bsdvlin.html">
FreeBSD vs. Linux</a>: a bunch of comparisons between FreeBSD and
Linux, which is another publically-distributed free UNIX-like OS
for PC's. </li>
<li><a name="daemonnews" href="http://www.daemonnews.org/"> Daemon
News</a></li>
<li><a href="http://www.bafug.org/FbsdCounter.html">The FreeBSD Counter Page</a>
page is the start of a project which will attempt to
determine the world-wide installed base of FreeBSD users. The
FreeBSD development community currently has only the vaguest
idea as to how large our user base is, and this makes it all
the more difficult to persuade hardware and software vendors
to take it seriously. </li>
<li><a name="giveaway" href="http://visar.csustan.edu">
BSD CD Giveaway List</a>
If somebody has a CD to give away (recipient pays for shipping) or to
lend locally, they can put their email address on the list. Hardware
and literature can also be given away. We encourage people to donate
CDs to local libraries and put them on the list as well. </li>
<li><a name="softwarebazaar" href="http://visar.csustan.edu/bazaar/">
The Free Software Bazaar</a>
is a market place designed to increase the amount of free software,
to support free software developers, and to more accurately measure
the demand for free software.</li>
</ul>
<a name="applications"></a>
<h3>Aplicaciones</h3>
<ul>
<li><a name="java" href="http://www.freebsd.org/java/">Java on FreeBSD</a></li>
<li><a name="mozilla" href="mozilla.html">FreeBSD Mozilla Group</a></li>
<li><a name="multimedia" href="http://www.freebsd.org/~faulkner/multimedia/mm.html">MultiMedia</a></li>
<li><a href="../ports/">FreeBSD Ports Collection</a></li>
<li><a href="http://www.freebsd.org/~fenner/portsurvey/">FreeBSD Ports distfiles survey</a></li>
<LI><a name="vam" href="ftp://rah.star-gate.com/pub/Voice.FAQ">
Voice Answering Machine</A></LI>
<li><a name="xcontest" href="http://www.freebsd.org/~xcontest/">FreeBSD X11 Desktop Theme Contest</a></li>
</ul>
<a name="networking"></a>
<h3>Networking</h3>
<ul>
<li><a name="altq" href="http://www.csl.sony.co.jp/person/kjc/kjc/software.html"> ALTQ: bandwidth management for applications</a></li>
<li><a name="kame" href="http://www.kame.net/">KAME Project, a free IPv6/IPsec stack for BSD</a></li>
<li><a name="ppp" href="http://www.awfulhak.org/ppp.html"> Point to Point Protocol (PPP)</a></li>
<li><a name="smn" href="http://www.cs.pdx.edu/research/SMN/"> Secure MobileIP via IP</a></li>
</ul>
<a name="filesystem"></a>
<h3>Sistemas de ficheros</h3>
<ul>
<li><a name="afs" href="http://www.stacken.kth.se/projekt/arla/">Arla</a>
is a free AFS client implementation. The main goal is to
make a fully functional client with all capabilities of normal AFS.
Other planned and implemented things are all the normal management
tools and a server.
<li><a name="coda" href="http://www.coda.cs.cmu.edu/">Coda</a> is
a distributed file system. Among its features are disconnected
operation, good security model, server replication and
persistent client side caching.
<li><a name="devfs" href="http://www.freebsd.org/~julian/">DEVFS</a></li>
<li><a href="http://www.freebsd.org/~terry/">Mode locking</a></li>
<li><a href="http://www.freebsd.org/~terry/">Make the namei interface reflexive</a></li>
<li><a href="http://www.freebsd.org/~terry/">NFS client and server locking</a></li>
<LI><a href="http://iclub.nsu.ru/~semen/ntfs/">NTFS Driver for FreeBSD</a></li>
<li><a name="softupdate" href="http://www.freebsd.org/~julian/">soft update code</a></li>
<li><a name="tcfs" href="http://tcfs.dia.unisa.it/">TCFS</a>
is a Transparent Cryptographic File System that is a suitable
solution to the problem of privacy for distributed file system. By a
deeper integration between the encryption service and the file system,
it results in a complete trasparency of use to the user
applications. Files are stored in encrypted form and are decrypted
before they are read. The encryption/decryption process takes place on
the client machine and thus the encryption/decryption key never
travels on the network.</li>
<li><a name="Tertiary"
href="http://now.cs.berkeley.edu/Td/">Tertiary Disk</a> is a
storage system architecture to create large disk storage systems
that avoid the disadvantages of custom built disk arrays. The
name comes from twin goals: to have the cost per megabyte and
capacity of tape libraries and the performance of magnetic
disks. We use commodity, off the shelf components to develop a
scalable, low cost, terabyte capacity disk system. Our target is
to build a complete storage system with about 30-50% extra to
the cost of the raw disk. Tertiary Disk uses PCs connected by a
switched network to host a large number of disks. Our prototype
consists of 20 200MHz PC PCs, which host 370 8GB disks. The PCs
are connected through a 100Mbps Ethernet switch.</li>
<li><a name="vinum" href="http://www.lemis.com/vinum.html"> Vinum: a logical volume manager</a></li>
</ul>
<a name="kernelandsecurity"></a>
<h3>Kernel, seguridad</h3>
<ul>
<li><a name="drawbridge" href="http://drawbridge.tamu.edu/"> Drawbridge, a firewall package</a></li>
<li><a name="hardening" href="http://www.watson.org/fbsd-hardening/">FreeBSD Hardening Project, a more secure environment</a></li>
<li><a name="metacomputing" href="http://www.sarnoff.com:8000/docs/metacomputing.html"> Metacomputing</a></li>
<li><a name="DHCP" href="http://home.san.rr.com/freebsd/dhcp.html">DHCP configuration</a></li>
<li><a href="http://www.freebsd.org/~jraynard/source/"> Handling more than 32 signals</a></li>
<li><a href="http://www.freebsd.org/~terry/">Working LDAP for FreeBSD</a></li>
<li><a href="ftp://ftp.gsoft.com.au/misc/splashkit-980202.tar.gz"> Splashkit, displays a graphical image while booting</a></li>
<li><a name="SMP" href="http://www.freebsd.org/~fsmp/SMP/SMP.html">Symmetric MultiProcessor Support</a></li>
<li><a href="http://www.freebsd.org/~terry/">A validation suite for testing for kernel memory leaks</a></li>
</ul>
<a name="devicedrivers"></a>
<h3>Drivers</h3>
<ul>
<li><a name="atm" href="http://www.ccrc.wustl.edu/pub/chuck/tech/bsdatm/bsdatm.html"> BSD ATM: implementation of ATM internetworking under 4.4BSD</a>:
New computer applications in areas such as multimedia, imaging,
and distributed computing demand high levels of performance from
computer networks. ATM-based networking solutions provide one
possible alternative to meeting these performance needs.
However, the complexity of ATM over traditional networks such as
Ethernet has proven to be a barrier to its being used. In this
paper we present the design and implementation of BSD ATM, a
light-weight and efficient ATM software layer for BSD-based
operating systems that requires minimal changes to the operating
system. BSD ATM can be used both for IP-based networking traffic
and for ``native'' ATM traffic.</li>
<li><a name="timekeeping" href="http://phk.freebsd.dk/rover.html"> High-precision timekeeping with FreeBSD</a></li>
<li><a name="homeauto" href="http://www.freebsd.org/~fsmp/HomeAuto/HomeAuto.html">Home Automation</a></li>
<li><a name="isdn" href="http://www.hcs.de/users/hm/isdn4bsd/i4b-main.html"> i4b: ISDN for FreeBSD</a></li>
<li><a name="cam" href="http://www.freebsd.org/~gibbs/"> CAM: New SCSI layer for FreeBSD</a></li>
<li><a name="tokenring" href="http://www.jurai.net/~winter/tr/tr.html">The FreeBSD Token-Ring Project</a></li>
<li><a name="usb" href="http://www.etla.net/~n_hibma/usb/usb.pl"> FreeBSD USB driver development</a>
The NetBSD USB stack has been ported to FreeBSD. Together with them we
have started developing the drivers for many devices using the USB bus.
Have a look on the webpage if you want to join the effort or you want to
have a look on the devices that are being supported.
</ul>
<a name="architecture"></a>
<h3>Arquitectura</h3>
<ul>
<li><a name="alpha" href="../alpha/alpha.html">Porting FreeBSD to Alpha systems</a></li>
<li><a name="sparc" href="http://www.freebsd.org/~obrien/freebsd-sparc/">Porting FreeBSD to Sparc systems</a></li>
<li><a name="sysvr4" href="http://slash.dotat.org/~newton/freebsd-svr4/">
The SysVR4 Emulation</a>
page describes an SysVR4 emulator for FreeBSD. It is currently
capable of running (or walking, in some cases) a wide-ish variety of
SysV executabls taken from Solaris/x86 2.5.1 and 2.6 systems. I have
reason to believe that it will also run SCO UnixWare and SCO
OpenServer binaries.</li>
<li><a name="picobsd"
href="http://www.freebsd.org/~picobsd/">Small and embedded
FreeBSD (PicoBSD)</a></li>
<li><a name="linuxthreads" href="http://lt.tar.com/">
Linux Threads under FreeBSD</a>:
Create a port of Linux Threads that can be compiled and used as a
kernel threads implementation under FreeBSD. Allow native Linux
applications linked against the Linux Threads pthread library (either
static or shared libs) to run under FreeBSD in Linux "emulation" mode.
</li>
</ul>
<a name="misc"></a>
<h3>Varios</h3>
<ul>
<li><a name="global" href="http://wafu.netgate.net/tama/unix/global.html"> GLOBAL common source code tag system</a</li>
<li><a name="pao" href="http://www.jp.FreeBSD.org/PAO/">PAO: Mobile Computing page, laptops running FreeBSD</a></li>
<li><a href="http://www.freebsd.org/~jraynard/source/">Replacement of gnu awk with bwk's "one true awk"</a></li>
</ul>
&footer;
</body>
</html>

237
es/publish.sgml Normal file
View file

@ -0,0 +1,237 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Publicaciones Relacionadas con FreeBSD">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: publish.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<TABLE>
<TR><TD><IMG SRC="../gifs/daemon.gif" ALT="FreeBSD Daemon" WIDTH="80" HEIGHT="76" BORDER=0></TD><TD >
<UL>
<LI><a href="#books">LIBROS</A>
<LI> <a href="#cdroms">CDROMS</A>
<LI> <a href="#magazines">MAGAZINES</A>
<LI> <a href="#newsletter">NEWSLETTER</A>
<LI> <a href="news/press.html">PRENSA</A>
</UL></TD></TR>
</TABLE>
Aqu&iacute; encontrar&aacute;s las cubiertas de diferentes publicaciones
relacionadas con FreeBSD. Si conoces alguna publicaci&oacute;n/CDROM
adicional sobre FreeBSD, por favor, haznoslo saber en la direcci&oacute;n
<A HREF="mailto:www@freebsd.org">www@freebsd.org</A>, para que podamos
a&ntilde;dirlo a este web.
<P>
Pulsa en cualquiera de los gr&aacute;ficos para ver una la imagen mayor.
<A NAME="books"></A>
<H2>Libros</H2>
<TABLE BORDER="5" CELLPADDING="15">
<TR><TD><A HREF="../gifs/jpb.jpg"><IMG SRC="../gifs/jp.jpg" WIDTH="150" HEIGHT="190">
</A></TD><TD>Esta es una reciente publicaci&oacute;n (Mayo 1997) de Tatsumi
Hosokawa y otros. En el mundo de los libros de inform&aacute;tica es un
top-seller en Jap&oacute;n, superando las ventas del libro
"The Road Ahead" de Bill Gates.</td></tr>
<TR><TD><A HREF="../gifs/205-jpb.jpg"><IMG SRC="../gifs/205-jp.jpg" WIDTH="150" HEIGHT="208"></A></TD><TD>(Libro de FreeBSD en japon&eacute;s que incluye la
versi&oacute;n 2.0.5, titulado "FreeBSD: Fun and easy Installation")</TD></TR>
<TR><TD><A HREF="../gifs/pc98-jpb.jpg"><IMG SRC="../gifs/pc98-jp.jpg" WIDTH="150" HEIGHT="194"></A></TD><TD>(Libro de FreeBSD en japon&eacute;s que incluye la
versi&oacute;n 2.0.5, titulado "FreeBSD Introductory Kit")</TD></TR>
<TR><TD><A HREF="../gifs/comp_b.jpg"><IMG SRC="../gifs/complete.jpg" WIDTH="150"
HEIGHT="228"></A></TD>
<td>Este es el libro "FreeBSD Complete" de Walnut Creek CDROM con gu&iacute;a
de instalaci&oacute;n, p&aacute;ginas man y 2 cd's de instalaci&oacute;n.
</TD></TR>
<TR><TD><A HREF="../gifs/runningb.jpg"><IMG SRC="../gifs/running.jpg" WIDTH="150" HEIGHT="210"></A></TD><TD>Libro de Walnut Creek CDROM titulado "Installing & Running FreeBSD",
que conten&iacute;a las instrucciones de instalaci&oacute;n y dos cd's. Ha sido
reemplazado por el m&aacute;s completo "FreeBSD Complete".
</TD></TR>
<TR><TD><A HREF="../gifs/twb.jpg"><IMG SRC="../gifs/tw.jpg" WIDTH="150" HEIGHT="200"></A></TD><TD>Este libro recientemente publicado (principios de 1997) en Taiwan.
Su t&iacute;tulo es "FreeBSD: introduction and applications" y el autor es
Jian-Da Li.
</TD></TR>
<TR><TD><A HREF="../gifs/getstarb.jpg"><IMG SRC="../gifs/getstart.jpg" WIDTH="150" HEIGHT="188"></A></TD><TD> Este es el libro "Getting Started with FreeBSD" de
Fuki-Shuppan. Trata tanto la instalaci&oacute;n y entorno japon&eacute;s como
la administraci&oacute;n del sistema e informaci&oacute;n de bajo nivel (como
el proceso de arranque). FreeBSD-2.2.2R y XFree86-3.2 en CDROM. 264
p&aacute;ginas, 3,400 yen.
</TD></TR>
<TR><TD><A HREF="../gifs/starkitb.jpg"><IMG SRC="../gifs/starkit.jpg" WIDTH="150" HEIGHT="235"></A></TD><TD>"Personal Unix Starter Kit - FreeBSD" de ASCII. Incluye
la historia de Unix, una gu&iacute;a de creaci&oacute;n de documentaci&oacute;n
en japon&eacute;s y craci&oacute;n de ports. 2.1.7.1R y XFree86-3.2
en CDROM.
</TD></TR>
<TR><TD><A HREF="../gifs/bsdmb.jpg"><IMG SRC="../gifs/bsdm.jpg" WIDTH="150" HEIGHT="235"></A></TD><TD>BSD mit Methode, M. Schulze, B. Roehrig, M. Hoelzer und andere,
C&amp;L Computer und Literatur Verlag, 1998, 850 pages.
2 CDROMs, FreeBSD 2.2.6, NetBSD 1.2.1 and 1.3.2, OpenBSD 2.2
and 2.3. DM 98,-.
</TD></TR>
</TABLE>
<A NAME="cdroms"></A>
<H2>CDROMs</H2> Para m&aacute;s informaci&oacute;n sobre las releases
m&aacute;s recientes a <A HREF="releases/index.html">la p&aacute;gina de
informaci&oacute;n de releases de FreeBSD</a>.
<P>
<TABLE BORDER="5" CELLPADDING="15">
<TR><TD><A HREF="../gifs/bsdiscb.jpg"><IMG SRC="../gifs/bsdisc.jpg" WIDTH = "150" HEIGHT="141"></A></TD><TD> Este es el BSDisc de InfoMagic, conteniendo FreeBSD 2.0
y NetBSD 1.0 en un solo CD.
</TD></TR>
<TR><TD><A HREF="../gifs/wc-44lite2b.jpg"><IMG SRC="../gifs/wc-44lite2.jpg" WIDTH="150" HEIGHT="142"></A></TD><TD>Esta es la release original de 4.4 BSD Lite2 de UC
Berkeley, la tecnolog&iacute;a b&aacute;sica de FreeBSD.
</TD></TR>
<TR><TD><A HREF="../gifs/las512b.jpg"><IMG SRC="../gifs/las512.jpg" WIDTH="150" HEIGHT="171"></A></TD><TD>La primera de las series "BSD" de Laser5. Contiene
FreeBSD-2.0.5R, NetBSD-1.0, XFree86-3.1.1 y el kernel FreeBSD(98).</TD></TR>
<TR><TD><A HREF="../gifs/las523b.jpg"><IMG SRC="../gifs/las523.jpg" WIDTH="150" HEIGHT="132"></A></TD><TD>The second of Laser5's "BSD" series. From this version, the CDs come
in a standard jewel box. Contains FreeBSD-2.1R, NetBSD-1.1,
XFree86-3.1.2 and 3.1.2A, and FreeBSD(98) kernel (2.0.5).
</TD></TR>
<TR><TD><A HREF="../gifs/las5b.jpg"><IMG SRC="../gifs/las5.jpg" WIDTH="150" HEIGHT="128"></A></TD><TD>This is the Laser5 Japanese edition of the
FreeBSD CDROM. It is a 4 CD set.
</TD></TR>
<TR><TD><A HREF="../gifs/phtb.jpg"><IMG SRC="../gifs/pht.jpg" HEIGHT="150" WIDTH="151"></A></TD><TD>This is the only FreeBSD CD Pacific Hitech produced before merging their
product line with that of Walnut Creek CDROM. PHT now also produces the
FreeBSD/J (Japanese) CD product.</TD></TR>
<TR><TD><A NAME="221cd"></A><A HREF="../gifs/coverb.jpg"><IMG SRC="../gifs/cover.jpg" WIDTH="150" HEIGHT="150"></A></TD><TD>This is the cover disc from the Korean <A HREF="#magazines">magazine</A>.
Note the creative cover art! The CD contains the FreeBSD 2.2.1 release
with some local additions.</TD></TR>
<TR><TD><A HREF="../gifs/wc-10b.jpg"><IMG SRC="../gifs/wc-10.jpg" WIDTH="150" HEIGHT="143"></A></TD><TD>This is it - the very first FreeBSD CD published! Both the FreeBSD
Project and Walnut Creek CDROM were fairly young back then, and you'll
probably have little difficulty in spotting the differences in production
quality between then and now.
</TD></TR>
<TR><TD><A HREF="../gifs/wc-11b.jpg"><IMG SRC="../gifs/wc-11.jpg" WIDTH="150" HEIGHT="150"></A></TD><TD>This was the second FreeBSD CD published by Walnut Creek CDROM and also the
very last on the 1.x branch (ref USL/Novell lawsuit and settlement). The next release, FreeBSD 1.1.5, was only
available on the net.
</TD></TR>
<TR><TD><A HREF="../gifs/wc-blunb.jpg"><IMG SRC="../gifs/wc-blun.jpg" WIDTH="150" HEIGHT="148"></A></TD><TD>This unusual CD is something of a collector's item now given that almost
all existing examples were systematically tracked down and destroyed.
An artwork mishap has this CD dated for the wrong year, and on the spine
"January" is also misspelled as "Jaunary", just to increase the embarrassment
factor. Ah, the perils of turning in one's artwork just hours before leaving for
a trade show.
</TD></TR>
<TR><TD><A HREF="../gifs/wc-200b.jpg"><IMG SRc="../gifs/wc-200.jpg" WIDTH="150" HEIGHT="149"></A></TD><TD>This is the fixed-up version of the FreeBSD 2.0 CD.
Note that the color scheme has even been changed in the corrected version,
something unusual for a fixup and perhaps done to distance it from the
earlier mistake. </TD></TR>
<TR><TD><A HREF="../gifs/wc-205b.jpg"><IMG SRC="../gifs/wc-205.jpg" WIDTH="150" HEIGHT="151"></A></TD><TD>The FreeBSD 2.0.5 release CD. This was the first CD to feature Tatsumi Hosokawa's daemon
artwork.</TD></TR>
<TR><TD><A HREF="../gifs/wc-21b.jpg"><IMG SRC="../gifs/wc-21.jpg" WIDTH="150" HEIGHT="149"></A></TD><TD>The FreeBSD 2.1 release CD. This was the first CD release on the 2.1 branch
(the last being 2.1.7).</TD></TR>
<TR><TD><A HREF="../gifs/wc-215b.jpg"><IMG SRC="../gifs/wc-215.jpg" WIDTH="150" HEIGHT="149"></A></TD><TD>The FreeBSD 2.1.5 release CD.</TD></TR>
<TR><TD><A HREF="../gifs/wc-216b.jpg"><IMG SRC="../gifs/wc-216.jpg" WIDTH="150" HEIGHT="148"></A></TD><TD>The FreeBSD 2.1.6 release CD.</TD></TR>
<TR><TD><a HREF="../gifs/wc-216jpb.jpg"><IMG SRC="../gifs/wc-216jp.jpg" WIDTH="150" HEIGHT="150"></A></TD><TD>The Japanese version of 2.1.6. This was the first and last Japanese
localized version published by WC, responsibility for that product then
transitioning to a team led by Tatsumi Hosokawa and sponsored by
Pacific Hitech and Laser5.
</TD></TR>
<TR><TD><A HREF="../gifs/wc-217b.jpg"><IMG SRC="../gifs/wc-217.jpg" WIDTH="150" HEIGHT="149"></A></TD><TD>The FreeBSD 2.1.7 release CD. Also the last CD released on the 2.1.x
branch. Done primarily as a security fixup for 2.1.6
</TD></TR>
<TR><TD><A HREF="../gifs/wc-22snapb.jpg"><IMG SRC="../gifs/wc-22snap.jpg" WIDTH="150" HEIGHT="148"></A></TD><TD>An early release SNAPshot of 2.2 (done before 2.2.1 was released).
</TD></TR>
<TR><TD><A HREF="../gifs/wc-221b.jpg"><IMG SRC="../gifs/wc-221.jpg" WIDTH="150" HEIGHT="148"></A></TD><TD>The FreeBSD 2.2.1 release CD. This was the first CD on the 2.2 branch.
</TD></TR>
<TR><TD><A HREF="../gifs/wc-222b.jpg"><IMG SRC="../gifs/wc-222.jpg" WIDTH="150" HEIGHT="152"></A></TD><TD>The FreeBSD 2.2.2 release CD.
</TD></TR>
<TR><TD><A HREF="../gifs/wc-30snab.jpg"><IMG SRC="../gifs/wc-30sna.jpg" WIDTH="150" HEIGHT="148"></A></TD><TD>The FreeBSD 3.0 snapshot CD.
</TD></TR>
<TR><TD><A HREF="../gifs/wc-docsb.jpg"><IMG SRC="../gifs/wc-docs.jpg" WIDTH="150" HEIGHT="148"></A></TD><TD>The FreeBSD mailing list and newsgroup archives, turned into HTML and
semi-indexed by thread. This product ran for 2 releases and then stopped
with a thud once it became obvious that there was simply too much data to
deal with on one CD. Perhaps when DVD becomes more popular...
</TD></TR>
</TABLE>
<A NAME="magazines"></A>
<H2>Magazines</H2>
<TABLE BORDER=5 CELLPADDING=15>
<TR><TD><A HREF="../gifs/krb.jpg"><IMG SRC="../gifs/kr.jpg" WIDTH="150" HEIGHT="213"></A></TD><TD>Cover of Korean UNIX magazine, May 1997 issue.
Also included <A HREf="#221cd">FreeBSD 2.2.1</A> with cover CDs.
</TD></TR>
<TR><TD><A HREF="../gifs/unixuserb.jpg"><IMG SRC="../gifs/unixuser.jpg" WIDTH="150" HEIGHT="199"></A></TD><TD>UNIX User Magazine
November 1996 issue.
Also included FreeBSD 2.1.5 on cover CD.
</TD></TR>
<TR><TD><A HREF="../gifs/fullcourse3b.jpg"><IMG SRC="../gifs/fullcourse3.jpg" WIDTH="149" HEIGHT="193"></A></TD><TD>This is the "FreeBSD Full Course" special in April 1997's Software
Design (published by Gijutsu Hyoron Sha). There are 80 pages of
FreeBSD articles covering everything from installation to tracking
-current.
</TD></TR>
<TR><TD><A HREF="../gifs/smart-reseller.jpg"><IMG SRC="../gifs/smart-reseller-small.jpg" WIDTH="149" HEIGHT="193"></A></TD><TD>
<a href="http://www.zdnet.com/sr/stories/issue/0,4537,349576,00.html">Quality Unix for FREE</a>, by Brett Glass
in <a href="http://www.zdnet.com/sr/">Sm@rt Reseller Online</a>
September 1998
</TD></TR>
</TABLE>
<A NAME="newsletter"></A>
<H2>Newsletters</H2>
<TABLE BORDER=5 CELLPADDING=15>
<TR><TD><A HREF="../gifs/newsletb.jpg"><IMG SRC="../gifs/newslett.jpg" WIDTH="150" HEIGHT="194"></A>
</TD><TD>This is
<A HREF="http://www.freebsdmall.com/newsletter1/">issue #1</A>
of the FreeBSD Newsletter, published and distributed free of charge by
<A HREF="http://www.cdrom.com/">Walnut Creek CDROM</A>.
You can
<A HREF="http://www.freebsd.org/register.html">register</A> to receive it.
Submit articles/make comments by sending email to
<A HREF="mailto:newsletter@FreeBSD.ORG">newsletter@FreeBSD.ORG</A>.
</TD></TR>
<TR><TD><A HREF="../gifs/newslet2b.jpg"><IMG SRC="../gifs/newslet2.jpg" WIDTH="150" HEIGHT="194"></A>
</TD><TD>This is
<A HREF="http://www.freebsdmall.com/newsletter2/">issue #2</A>
of the FreeBSD Newsletter, published and distributed free of charge by
<A HREF="http://www.cdrom.com/">Walnut Creek CDROM</A>.
You can
<A HREF="http://www.freebsd.org/register.html">register</A> to receive it.
Submit articles/make comments by sending email to
<A HREF="mailto:newsletter@FreeBSD.ORG">newsletter@FreeBSD.ORG</A>.
</TD></TR>
</TABLE>
<ADDRESS><A HREF="./mailto.html">questions@FreeBSD.ORG</A><BR>
Copyright &copy; 1995-1997 FreeBSD Inc.
All rights reserved.<BR>$Date: 1999-02-08 19:26:11 $</ADDRESS>
</BODY>
</HTML>

91
es/register.sgml Normal file
View file

@ -0,0 +1,91 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "Registro">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<!-- $Id: register.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<CENTER><FONT SIZE=4>
Reg&iacute;strate para recibir FreeBSD Newsletter y subscribirte a la lista
de distribuci&oacute;n announce@freebsd.org</FONT></CENTER>
<FORM METHOD=POST ACTION="http://www.freebsd.org/cgi/reg.cgi">
<INPUT type=hidden name="recipient" value="register@freebsd.org"><BR>
<INPUT type=hidden name="version" value="3.0-RELEASE">
<CENTER>
<TABLE BORDER=0 WIDTH="95%">
<TR VALIGN=top>
<TR VALIGN=top>
<TD>Nombre: </TD>
<TD COLSPAN=3 ALIGN=left><INPUT NAME=First TYPE=text SIZE=30></TD>
</TR>
<TR VALIGN=top>
<TD ALIGN=left>Apellido: </TD>
<TD COLSPAN=3 ALIGN=left><INPUT NAME=Last TYPE=text SIZE=30></TD>
</TR>
<TR>
<TD>Email: </TD>
<TD COLSPAN=3 ALIGN=left><INPUT NAME=emaila TYPE=text SIZE=30></TD>
</TR>
<TR VALIGN=top>
<TD ALIGN=left>Direcci&oacute;n:</TD>
<TD COLSPAN=3 ALIGN=left><INPUT NAME=Address TYPE=text SIZE=30></TD>
</TR>
<TR VALIGN=top>
<TD ALIGN=left>Ciudad: </TD>
<TD COLSPAN=3 ALIGN=left><INPUT NAME=City TYPE=text SIZE=30></TD>
</TR>
<TR VALIGN=top>
<TD ALIGN=left>Pa&iacute;s/Estado U.S.A.: </TD>
<TD ALIGN=left><INPUT
NAME=State
TYPE=text
SIZE=10></TD>
<TD ALIGN=left>Pa&iacute;s/C&oacute;digo Postal: </TD>
<TD ALIGN=left><INPUT NAME=Zip
TYPE=text
SIZE=12></TD>
</TR>
<TR><TD></TD></TR>
<TR><TD COLSPAN=4>Quieres recibir emails comerciales relacionados con FreeBSD?<INPUT NAME="commerce_email" TYPE="CHECKBOX" VALUE="yes"></TD></TR>
<TR><TD COLSPAN=4>Subscribir las direcciones listadas en la lista announce@freebsd.org?<INPUT NAME="announce" TYPE="CHECKBOX" VALUE="yes"></TD></TR>
<TR><TD COLSPAN=4>Como quieres recibir FreeBSD Newsletter? <SELECT NAME="newsletter" SIZE= 1>
<OPTION>Copia Postal
<OPTION>E-mail
<OPTION>No Gracias
<OPTION>
</SELECT>
</TD></TR>
</TABLE><P>
<INPUT TYPE=submit VALUE="Send">
<INPUT TYPE=reset VALUE="Reset">
</CENTER>
</FORM>
<p>Puedes ver una copia de la &uacute;ltima versi&oacute;n de la newsletter
en <a href="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/issue2.pdf">
formato pdf</a>. Tienes
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/newsletter/README.TXT">un fichero
de ayuda</a> disponible para ayudarte a seleccionar y usar un visor pdf.
&footer;
</BODY>
</HTML>

View file

@ -0,0 +1,196 @@
386BSD Release 0.1
Contributor List
Lynne Greer Jolitz
William F. Jolitz
_H_a_r_d_w_a_r_e _a_n_d _M_o_n_e_t_a_r_y _C_o_n_t_r_i_b_u_t_o_r_s
Many people and firms have provided hardware and/or money to
try and keep this unfunded project going despite a recession
and hard times -- usually by digging into their own pockets.
Each of these contributors gave, not only because they
believed that the continuation of 386BSD is vital to the
health of the research, educational, and development commun-
ities, but also because they realize that an individual can
and does make a difference!
Without the help of the people listed here, this release
would simply not have been possible. We would especially
like to thank Thos Sumner, whose loan of a 486/50 SCSI PC
made development go more rapidly. The rest of the 386BSD
user community should make special note of all these people
and firms and commend them for their generosity and
foresight.
We hope that their leadership and vision will serve as shin-
ing examples to the entire 386BSD user community, and serve
to encourage others to actively participate in 386BSD.
Jan van den Bosch
Compaq Computer Corporation
Cyrix Corporation
Dixon Dick
Steven P. Donegan
Jon Erickson
Eric J. Haug
Bob McGhee
Jesus Monroy Jr.
Andrew Moore
Rich Murphey
Mark Ng
Kenji Okamoto
John Plocher
Mark R. Riordan
John B. Scalia
Steve Sizemore
Thos Sumner
David E. Tweten
386BSD CONTRIB LIST 1 July 1992
_S_o_f_t_w_a_r_e _C_o_n_t_r_i_b_u_t_o_r_s
The following people have contributed key software programs,
modules and fixes, including novel work and ports of popular
public domain user programs. Some of this software was
directly contributed to us, while other items were made
available to all users via the network. Occasionally,
several people came up with a variety of approaches for a
single item. In this instance, we tried to choose the one
which we felt would best serve the rest of the 386BSD user
base for this release. However, the creativity and persever-
ance of all the software contributors trying to make 386BSD
better for the entire 386BSD user community was consider-
able. Each individual effort is worthy of pride.
We wish to personally thank all of these people, as they
have helped make 386BSD Release 0.1 a reality. We hope that
these contributors and all the rest of the 386BSD user com-
munity will continue to actively participate to make future
releases even better!
James Van Artsdalen
Scott Burris
Randall Dean
Chris Demetriou
Mark Eichin
Bruce Evans
Steve Ferguson
Jeffrey Goh
David Greenman
Amancio Hasty Jr
John W. Hatley
Eric J. Haug
Tom Ivar Helbekkmo
John D. Irwin
Peter Klingebiel
Paul Kranenburg
Daniel Lanciani
Karl Lehenbauer
Lee M. J. McLoughlin
Andrew J. Michael
Jesus Monroy Jr.
Daniel A. Muntz
Richard Murphey
Glen Overby
Brad Parker
Herb Pereyl
Ken Raeburn
Paul Richards
Guido van Rooij
Peng-Toh Sim
Wolfgang Solfrank
Dave Stanhope
386BSD CONTRIB LIST 2 July 1992
Mark Tinguely
Linus Torvalds
Richard Tobin
Rob Warnock
Christian Wiedmann
Pace Willisson
Joerg Wunsch
And all of the other 386BSD Software Contributors.
_S_u_p_p_o_r_t _a_n_d _A_d_v_i_c_e _C_o_n_t_r_i_b_u_t_o_r_s
Many people have continually encouraged us over the course
of these releases, and provided us with technical advice and
guidance. These people have also spent considerable time and
energy getting this software out to the rest of the 386BSD
community. While it is impossible for us to list everyone
who has been supportive of 386BSD, we wish to personally
thank some of the people who have been of special assistance
to us directly over the course of getting 386BSD out the
door.
Bruce Blakely
Dave Campbell
Free Software Foundation
Paul Fromberg
Tom Genereaux
John Gilmore
Dave Harris
Jim Joyce
Dan Kionka
Dory Leifer
Per Lindqvist
Marshall Midden
Rich Morin
Silicon Valley Computer Society
John Sokol
Thos Sumner
Karen Trocki
Rob Warnock
and a special thanks to:
John Erickson, Tami Zemel, Ray Valdez, Monica Berg, Michael Floyd
and everyone else at Dr. Dobbs Journal.
Juergen Fey, Rainer Huttenloher, Gerd Oskar Bausewein
and everyone else at UNIX Magazin.
And all of the 386BSD User Community.
386BSD CONTRIB LIST 3 July 1992

View file

@ -0,0 +1,191 @@
FreeBSD 1.1.5
Contributor List
Derived Software Contributors:
This software was originally derived from William F. Jolitz's 386BSD
release 0.1, though very little of the original 386BSD specific code
remains.
Please see the file CONTRIB.386BSD for the list of contributors from
386BSD.
Included in this release are some of the patches from the old 386BSD
patch kit version 0.2.4, and therefore the names of contributors from the
patch kit are also listed below.
Finally, there are portions of NetBSD that have been integrated into
FreeBSD as well, and we would therefore like to thank all the contributors
to NetBSD for their work.
Hardware Contributors:
A special thanks to Robert Bruce and Jack Velte of Walnut Creek CDROM
for providing a 486/DX2-66 EISA/VL system that is being used for the
development work. It would have been impossible to do this release
with out their support.
Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
drive.
The FreeBSD Core Team (in alphabetical order):
Andrew A. Chernov <ache@astral.msk.su>
John Dyson <dyson@implode.rain.com>
David Greenman <davidg@Root.COM>
Rodney W. Grimes <rgrimes@cdrom.com>
Jordan K. Hubbard <jkh@freefall.cdrom.com>
Scott Mace <smace@neosoft.com>
Andrew Moore <alm@netcom.com>
Rich Murphey <rich@lamprey.utmb.edu>
Geoff Rehmet <csgr@cs.ru.ac.za>
Paul Richards <paul@isl.cf.ac.uk>
Andreas Schulz <ats@g386bsd.first.bmd.de>
Nate Williams <nate@bsd.coe.montana.edu>
Garrett A. Wollman <wollman@freefall.cdrom.com>
Additional FreeBSD Contributors (no particular order):
Atsushi Murai <amurai@spec.co.jp>
Keith Moore <?>
Adam Glass <glass@postgres.berkeley.edu>
Andrew Herbert <andrew@werple.apana.org.au>
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>
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>
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>
Yuval Yarom <yval@cs.huji.ac.il>
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.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,131 @@
386BSD Release 0.1
Copyright
/*
* Copyright (c) 1989, 1990, 1991, 1992 William F. Jolitz, TeleMuse
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* This software is a component of "386BSD" developed by
* William F. Jolitz, TeleMuse.
* 4. Neither the name of the developer nor the name "386BSD"
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* 386BSD WAS DEVELOPED BY WILLIAM F. JOLITZ.
* 386BSD IS INTENDED FOR RESEARCH AND EDUCATIONAL PURPOSES.
* THIS SOFTWARE SHOULD NOT BE CONSIDERED TO BE A COMMERCIAL PRODUCT.
* THE DEVELOPER URGES THAT USERS WHO REQUIRE A COMMERCIAL PRODUCT
* NOT MAKE USE OF THIS WORK.
*
* FOR USERS WHO WISH TO UNDERSTAND THE 386BSD SYSTEM DEVELOPED
* BY WILLIAM F. JOLITZ, WE RECOMMEND THE USER STUDY WRITTEN
* REFERENCES SUCH AS THE "PORTING UNIX TO THE 386" SERIES
* (BEGINNING JANUARY 1991 "DR. DOBBS JOURNAL", USA AND BEGINNING
* JUNE 1991 "UNIX MAGAZIN", GERMANY) BY WILLIAM F. JOLITZ AND
* LYNNE GREER JOLITZ, AS WELL AS OTHER BOOKS ON UNIX AND THE
* ON-LINE 386BSD USER MANUAL BEFORE USE. A BOOK DISCUSSING THE INTERNALS
* OF 386BSD ENTITLED "386BSD FROM THE INSIDE OUT" WILL BE AVAILABLE LATE 1992.
*
* THIS SOFTWARE IS PROVIDED BY THE DEVELOPER ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE DEVELOPER BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
*/
386BSD Copyright 1 July 1992
386BSD Copyright 2 July 1992

View file

@ -0,0 +1,122 @@
This software contains software developed by the University of
California, Berkeley, and its contributors; by the Free Software
Foundation; by the University of Illinois; by the Massachusetts
Institute of Technology; by the University of Vermont and State
Agricultural College; by Carnegie Mellon University; and by a large
number of contributors, whose names are listed in the notices below.
Portions of this software are subject to one or more of the following
copyright notices. Please see the individual files for the terms and
conditions.
Copyright (C) 1980, 1983, 1986, 1988, 1990, 1991, Regents of the
University of California
Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, Free
Software Foundation, Inc.
Copyright (C) 1976, Board of Trustees of the University of Illinois
Copyright (C) 1980, 1981, Ken Harrenstien
Copyright (C) 1982, 1988, 1989, Walter Tichy
Copyright (C) 1983, 1986, 1992, 1993, Eric P. Allman
Copyright (C) 1983, Kenneth L. Greer
Copyright (C) 1984, 1985, 1986, 1987, 1992, Sun Microsystems, Inc.
Copyright (C) 1984, 1987, Stephen L. Moshier
Copyright (C) 1984, 1989, 1990, Bob Corbett and Richard Stallman
Copyright (C) 1984, University of British Columbia
Copyright (C) 1985, 1986, Wayne A. Christopher
Copyright (C) 1985, 1987, 1988, 1989, Adobe Systems, Inc.
Copyright (C) 1985, Stichting Mathematisch Centrum
Copyright (C) 1986, 1987, 1989, 1990, 1991, 1992, Ian F. Darwin
Copyright (C) 1986, 1987, 1989, Frame Technology, Inc.
Copyright (C) 1986, 1987, 1992, Daniel D. Lanciani
Copyright (C) 1986, 1987, Ed James
Copyright (C) 1986, Breslow
Copyright (C) 1986, Gary S. Brown
Copyright (C) 1986, Larry Wall
Copyright (C) 1986, Noah Morgan
Copyright (C) 1986, Stephen Satchell
Copyright (C) 1987, 1988, 1989, 1990, 1991, 1992, Carnegie Mellon University
Copyright (C) 1987, 1988, 1989, Sony Corp.
Copyright (C) 1987, 1988, John Stanback
Copyright (C) 1987, 1988, Ronald S. Karr and Landon Curt Noll
Copyright (C) 1987, 1989, 1990, 1991, Massachusetts Institute of Technology
Copyright (C) 1987, David C. Elliott.
Copyright (C) 1987, IBM Corporation
Copyright (C) 1987, Stuart Cracraft
Copyright (C) 1987, United States Army
Copyright (C) 1988, 1989, 1990, 1993, 1994, Paul A. Vixie
Copyright (C) 1988, 1989, Adam de Boor
Copyright (C) 1988, 1990, University of Utah
Copyright (C) 1988, Julian Onions
Copyright (C) 1988, Mark Nudleman
Copyright (C) 1988, Rayan S. Zachariassen
Copyright (C) 1989, 1990, 1991, 1992, 1993, Frank Kardel
Copyright (C) 1989, 1990, 1991, 1992, 1993, William S. Jolitz
Copyright (C) 1989, 1990, 1991, 1992, Brian Berliner
Copyright (C) 1989, Berkeley Softworks
Copyright (C) 1989, Dale Schumacher
Copyright (C) 1989, Dave Taylor
Copyright (C) 1989, Kenneth Almquist
Copyright (C) 1989, Matthew Self
Copyright (C) 1989, Robert V. Baron
Copyright (C) 1990, 1991, 1992, 1993, AT&T Bell Laboratories and Bellcore
Copyright (C) 1990, 1991, John W. Eaton
Copyright (C) 1990, 1991, Paul Eggert
Copyright (C) 1990, 1993, Andrew Moore
Copyright (C) 1990, John Robert LoVerso
Copyright (C) 1990, Open Software Foundation, Inc.
Copyright (C) 1990, RSA Data Security, Inc.
Copyright (C) 1991, 1992, 1993, 1994, Chris Provenzano
Copyright (C) 1991, 1992, 1993, Ian Lance Taylor
Copyright (C) 1991, 1992, Per Bothner
Copyright (C) 1991, 1992, Per Cederqvist
Copyright (C) 1991, Gregory M. Christy
Copyright (C) 1991, Inge Wallin
Copyright (C) 1991, Joseph Friedman
Copyright (C) 1992, 1993, 1994, David L. Mills
Copyright (C) 1992, 1993, Christopher G. Demetriou
Copyright (C) 1992, 1993, Garrett A. Wollman
Copyright (C) 1992, 1993, HD Associates
Copyright (C) 1992, 1993, Holger Veit
Copyright (C) 1992, 1993, Jean-Loup Gailly
Copyright (C) 1992, 1993, 1994 Joerg Wunsch
Copyright (C) 1992, 1993, John Brezak
Copyright (C) 1992, 1993, Motorola, Inc.
Copyright (C) 1993, 1994, Jordan Hubbard
Copyright (C) 1992, 1993, Soeren Schmidt
Copyright (C) 1992, 1993, Theo de Raadt
Copyright (C) 1992, 1993, University of Vermont and State Agricultural College
Copyright (C) 1992, Cygnus Support
Copyright (C) 1992, Diomidis Spinellis
Copyright (C) 1992, Henry Spencer
Copyright (C) 1992, Jeff Polk
Copyright (C) 1992, Terrence R. Lambert
Copyright (C) 1992, University of Guelph
Copyright (C) 1993, 1994, Andrew A. Chernov
Copyright (C) 1993, 1994, David Greenman
Copyright (C) 1993, 1994, John S. Dyson
Copyright (C) 1993, Adam Glass
Copyright (C) 1993, Atsushi Murai
Copyright (C) 1993, Brian Moore
Copyright (C) 1993, Daniel Boulet and RTMX Inc.
Copyright (C) 1993, David Muir Sharnoff
Copyright (C) 1993, David Parsons
Copyright (C) 1993, Gary Clark II
Copyright (C) 1993, Hannu Savolainen
Copyright (C) 1993, Herb Peyerl
Copyright (C) 1993, Herve Schauer Consultants
Copyright (C) 1993, Julian Elischer
Copyright (C) 1993, Julian Stacey
Copyright (C) 1993, K. J. Dryllerakis
Copyright (C) 1993, Martin Birgmeier
Copyright (C) 1993, Paul Kranenburg
Copyright (C) 1993, Paul Richards
Copyright (C) 1993, Thomas Koenig
Copyright (C) 1993, Winning Strategies, Inc.
Copyright (C) 1994, Christoph M. Robitschko
Copyright (C) 1994, University of Maryland
Copyright (C) 1993, 1994, jc@irbs.UUCP (John Capo),
vak@zebub.msk.su (Serge Vakulenko),
ache@astral.msk.su (Andrew A. Chernov)
$Id: COPYRIGHT.FreeBSD,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,45 @@
Copyright (c) UNIX System Laboratories, Inc.
All or some portions of this software are derived from
material licensed to the University of California by
American Telephone and Telegraph Co. or UNIX System Laboratories, Inc.
and are reproduced herein with the permission of
UNIX System Laboratories, Inc.
Additionally, the following files contained herein constitute
trade secrets of UNIX System Laboratories, Inc. and their contents
are not to be disclosed to any third party:
sys/kern/init_main.c
sys/kern/kern_clock.c
sys/kern/kern_exec.c [*]
sys/kern/kern_exit.c
sys/kern/kern_physio.c [**]
sys/kern/kern_sig.c
sys/kern/kern_synch.c
sys/kern/subr_rmap.c [*]
sys/kern/sys_generic.c
sys/kern/sys_process.c
sys/kern/sysv_shm.c
sys/kern/tty.c
sys/kern/tty_subr.c [*]
sys/kern/vfs_bio.c [*]
sys/kern/vfs_syscalls.c
sys/sys/buf.h
sys/sys/proc.h
sys/sys/shm.h
sys/sys/tty.h
sys/ufs/dinode.h
sys/ufs/inode.h
sys/ufs/ufs_bmap.c
sys/ufs/ufs_disksubr.c
sys/ufs/ufs_inode.c
sys/ufs/ufs_vnops.c
usr.bin/cpio/cpio.c [*]
[*] These file are NOT contained in FreeBSD
[**] The version of this file in FreeBSD is belived to be clear of any USL
copyright and/or trade secret.
$Id: COPYRIGHT.USL,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,73 @@
This file lists known problems with this release of FreeBSD
'hanging keyboard'
------------------
There are still problems with certain machines appearing to 'hang' on
bootup even though a prompt is there. The most common machines that
exhibit these problems are Gateway 2000 machines with PHOENIX bios's but
other machines with PHOENIX bios also exhibit this behavior.
The temporary solution until you can get the distribution
installed on your hard-drive is to 'bounce' on a key like shift or
num-lock (which works well since you can see when the keyboard comes
back to life) until the boot sequence is finished. The keyboard will
work fine for installing FreeBSD onto the hard-drive.
/usr/bin/gdb:
The gdb in the release will not work on shared objects nor will it
work with C++ executables. Please use the gdb in the ports area for
debugging shared and/or C++ code. This is just a work-around until
we can transition to the new version of gdb completely. See below.
/usr/gnu/bin/gdb:
This is the gdb from the ports area (if installed), also known as
gdb-4.11. There is a problem using gdb-4.11 to debug a core-file
generated by a binary which uses shared libraries. The problem is
basically due to the fact that the shared libraries are mmap'ed at
addresses in the memory space of the binary which are not accessible
to gdb-4.11 at the time that it tries to examine the core-file. This
usually manifests itself in "Cannot access memory at address <foo>"
messages at startup and "#0 <bar> in end ()" when you try to do
a backtrace ("bt").
Workaround: start gdb-4.11 without reference to the core-file,
e.g. "gdb fubar". Set a breakpoint in main and run the inferior
so that gdb-4.11 can resolve references to the shared libraries.
After this, use the "core-file" command to force gdb-4.11 to
load the core-file, e.g. "core-file fubar.core". Since all
shared library references were previously resolved gdb-4.11 can
now access the shared libraries and things like "bt" now work.
You will also be able to reference items previously on the stack
(from the core file), but all globals will show up as zero'd.
All these problems may be avoided if you compile the application
with -static.
/sys/i386/isa/if_ep.c
The 3c509 driver will hang under heavy network loads and take your
machine off the network. (Though the machine will continue to run with
no network facilities)
Workaround: Try a "ifconfig ep0 down" and a "ifconfig ep0 up"
to get it running again.
/sys/i386/isa/bt742a.c
The Bt445S and Bt747 controllers can cause problems when ISA DMA
is selected as an option. With the EISA controller the remedy is
easy - simply turn it off using your EISA configuration utility.
With the Bt445S, which is a VLB card, you must switch the undocumented
"SW10" on "SB2" to the off position. Also note that certain revisions
of the Buslogic board (Revision C or earlier, firmware revision <3.37)
will cause DATA CORRUPTION with systems containing more than 16MB of
memory. If you find this to be the case, temporarily remove your
extra memory and contact Buslogic for an upgrade!
fsck:
fsck can go into an endless loop in the repair/fsck cycle on
a corrupted filesystem. The message "VALUES IN SUPER BLOCK
DISAGREE WITH THOSE IN FIRST ALTERNATE" is very misleading.
fsck compares the superblock with the alternate in the last
cylinder group? So if this block is corrupt, you have no chance
to get the filesystem repaired. You can answer on the question
"UPDATE STANDARD SUPERBLOCK" with yes and get always the same
error message on the next fsck.
$Id: KNOWNBUGS,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,59 @@
The FreeBSD software is being mirrored at the following locations:
Country Site/Directory/Maintainer
======= =========================================================
Australia minnie.cs.adfa.oz.au:/BSD/FreeBSD-1.1-RELEASE
<wkt@cs.adfa.oz.au>
Australia ftp.physics.su.oz.au:/FreeBSD
David Dawes <dawes@physics.su.oz.au>
Australia ftp.une.edu.au:/pub/FreeBSD
Gordon Smith <Gordon.Smith@une.edu.au>
Austria ftp.tu-graz.ac.at:/pub/FreeBSD
<ftp@ftp.tu-graz.ac.at>
Finland ftp.funet.fi:/pub/unix/FreeBSD
<unix-adm@nic.funet.fi>
France ftp.ibp.fr:/pub/FreeBSD
<ftp@ftp.ibp.fr>
Germany ftp.informatik.tu-muenchen.de:/pub/comp/os/bsd/FreeBSD
<bsd@informatik.tu-muenchen.de>
Germany ftp.uni-duisburg.de:/pub/unix/FreeBSD
<ftp@ftp.uni-duisburg.de>
Germany gil.physik.rwth-aachen.de:/pub/FreeBSD
<kuku@acds.physik.rwth-aachen.de>
Hong Kong ftp.cs.cuhk.hk:/pub/FreeBSD
<unknown>
Israel orgchem.weizmann.ac.il:/pub/FreeBSD
<serg@klara.weizmann.ac.il>
Netherlands ftp.nl.net:/pub/os/FreeBSD
<archive@nl.net>
Russia ftp.kiae.su:/FreeBSD
<arcman@kiae.su>
UK src.doc.ic.ac.uk:/packages/FreeBSD
<wizards@doc.ic.ac.uk>
USA gatekeeper.dec.com:/pub/BSD/FreeBSD
<hubbard@gatekeeper.dec.com>
USA freebsd.uml.edu:/FreeBSD
<oneill@cs.uml.edu>
USA wuarchive.wustl.edu:/systems/unix/FreeBSD
<archives@wugate.wustl.edu>
$Id: MIRROR.SITES,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,6 @@
DATA= CONTRIB.386BSD CONTRIB.FreeBSD COPYRIGHT.386BSD
DATA+= COPYRIGHT.FreeBSD COPYRIGHT.USL KNOWNBUGS MIRROR.SITES
DATA+= PERSONAL.ACKS REGISTER.FreeBSD RELNOTES.FreeBSD ROSTER.FreeBSD
DATA+= SUPPORT.TXT TODO-1.1.5
.include "../../web.mk"

View file

@ -0,0 +1,17 @@
The following contributors would like to make these personal
acknowledgements (in no particular order):
Garrett Wollman would like to thank Gary Barbour and Steve Ackerman of
Utah; Tim Raymond, Jim White, and Jim Ertle of UVM; Malcolm Carlock at
UNR; and John Wroclawski of MIT.
Nate Williams would like to thank Jaye Mathisen and the entire Computer
Science department of Montana State University for their help, hardware
and encouragement.
Jordan Hubbard would like to thank IEUNET for bringing the INTERNET to
Ireland, thus making his participation possible at all (albeit expensive)
and his Mom, who would probably be pleased if only she understood any of
this. Hi Mom.
$Id: PERSONAL.ACKS,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,86 @@
In the absence of any other mechanism for counting the number of users
of FreeBSD, we like to as kindly suggest that you take a few minutes
to please register with the counter set up by
<Harald.T.Alvestrand@uninett.no>.
The justification for such "registration" is twofold: First, we sincerely do
wish to know just what the size and demographics of our user-base are
in order to better support its needs. Second, it's a sad fact that many
people rely on counters and statistics (even when highly dubious) rather
than actual experience when chosing an operating system, and the best we
can hope to do in such circumstances is to at least try to provide some
indication of how popular we are (or are not). This is not how we recommend
that people go about chosing an operating system, but the necessity of
"marketing" remains an undeniable fact of life.
The FreeBSD team does not necessarily feel that Harald's counter represents
the best approach to such statistics gathering, and its accuracy will only
be as good as people's willingness to register with it (which may not reflect
the actual OS population at any single point in time), but in the total absence
of any other mechanism for providing such useful statistics, it's certainly a
start and we thank Harald for his efforts in providing this service.
It's a community service, and of potential benefit to everyone (all *BSD
users), so let's see if we can't make it work!
Included below is the standard blurb from the counter.
Thanks in advance,
The FreeBSD team.
How to get registered
=====================
In brief:
[To register a running installation of FreeBSD]
Send E-mail to bsd-counter@uninett.no with the SUBJECT line
"I use FreeBSD at <place>"
Introduction
============
The intention of this counting project is to count all users of UNIXes
that are:
- BSD-derived
- Freely available
The variants NetBSD, 386BSD and FreeBSD are currently distinguished.
(NOTE: Linux is NOT BSD-derived. If you use that, send mail to
linux-counter@uninett.no instead!!!)
The information is *not* used for any purpose but statistics, and unless
you request it, information about single persons are *never* made public.
(A list of users who have requested publication is available from the
FTP file ftp://aun.uninett.no/pub/misc/386bsd/persons)
How to register
===============
Send E-mail to bsd-counter@uninett.no
The subject should be
I use FreeBSD|NetBSD|386BSD at <place>
Where FreeBSD, NetBSD or 386BSD is the particular variant you're using
and "place" can be school, work or home, or a combination of these.
You will get back a letter with 3 things:
- An acknowledgement
- A form that you can fill out and send in with more information
about yourself, your machine, and your 386bsd-using friends
- A report giving the current status of the counter
You can update your "vote" at any time, by sending an E-mail message
from the same account. Duplicates will be weeded out.
The current report, available by anonymous FTP to aun.uninett.no,
directory pub/misc/386bsd-counter, file "short", is given below.
For all questions, contact Harald.T.Alvestrand@uninett.no!
$Id: REGISTER.FreeBSD,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,313 @@
RELEASE NOTES
FreeBSD
Release 1.1.5
1. Technical overview
---------------------
FreeBSD is a freely available, full source 4.3 (+4.4 enhancements) BSD
release for Intel i386/i486 (or compatable) based PC's. It is based
on Bill Jolitz's 386BSD 0.1, with additions from "the patchkit",
NetBSD, CSRG, and the Free Software Foundation.
Since our first release of FreeBSD 1.0, many hundreds of bugs have been
fixed, features added, and the overall quality of the system improved
almost imeasurably. FreeBSD 1.1.5 represents the culmination of almost
18 months of work and many thousands of man hours put in by our all-volunteer
working group. We hope you enjoy it!
Many packages have also been upgraded or added, such as XFree86 2.1,
xview 3.2, elm, nntp, mh, InterViews and dozens of other miscellaneous
utilities have been ported and are now available as add-ons. See the next
section of this document for more details.
For a list of contributors, please see the files "CONTRIB.FreeBSD" and
"CONTRIB.386BSD", which should be bundled with your distribution.
Also see the new "REGISTER.FreeBSD" file for information on registering
with the "Free BSD user counter". We've also provided a list of who's
responsible for what (so that you may query them directly) in the
"ROSTER.FreeBSD" file; use of this file is encouraged to ensure faster
resolution of an problems you may have!
The core of FreeBSD does not contain DES code which would inhibit its
being exported outside the United States. There is an add-on package
to the core distribution, for use only in the United States, that
contains the programs that normally use DES. The 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.
2. Supported Configurations
---------------------------
FreeBSD currently runs on a wide variety of ISA, EISA and PCI bus based
PC's, ranging from 386sx to Pentium class machines (though the 386sx is
not recommended). Support for generic IDE or ESDI drive configurations,
various SCSI controller, network and serial cards is also provided.
Following is a list of all currently known disk controllers and
ethernet cards known to work with FreeBSD. Other configurations may
very well work, and we have simply not received any indication of
this.
2.1. Disk Controllers
WD1003 (any generic MFM/RLL)
WD1007 (any generic IDE/ESDI)
Adaptec 154x series ISA SCSI controller (as long as you have less than
16MB of main memory).
Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
[Note that Buslogic was formerly known as "Bustec"]
Buslogic 545S.
Buslogic 445S VLB SCSI controller
Buslogic 742A and 747.
Buslogic 942A PCI
Please see special notes in /usr/src/KNOWNBUGS (filed under bt742a.c) for
details concerning possible buggy firmware and undocumented switch settings
that may be necessary for proper operation of your Bt445S controller.
DTC 3290 EISA SCSI controller in 1542 emulation mode.
Ultra Store 14F and 34F.
Seagate ST01/02 SCSI controllers.
Future Domain 8xx/950 series SCSI controllers.
With all supported SCSI controllers, full support is provided for
SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
DAT) and CD ROM drives. Note: This and the mcd driver (Mitsumi CDROM
interface card) is the only way a CD ROM drive may be currently
attached to a FreeBSD system; we do not support SoundBlaster CDROM
interface, or other "mini SCSI" adapters.
Some controllers have limitations with the way they deal with >16MB of memory,
due to the fact that the ISA bus only has a DMA address space of 24 bits.
If you do your arithmetic, you'll see that this makes it impossible to do
direct DMA to any address >16MB. This limitation is even true of some
EISA controllers (which are normally 32 bit) when they're configured to
emulate an ISA card, which they then do in *all* respects. This problem
is avoided entirely by IDE controllers (which do not use DMA), true EISA
controllers (like the UltraStor or Adaptec 1742A) and most VLB (local bus)
controllers. In the cases where it's necessary, the system will use
"bounce buffers" to talk to the controller so that you can still use
more than 16Mb of memory without difficulty.
2.2. Ethernet cards
SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
based clones.
Isolan AT 4141-0 (16 bit)
Isolink 4110 (8 bit)
Novell NE1000, NE2000, and NE2100 ethernet interface.
3Com 3C503 Etherlink II
3Com 3C509 Ethernet cards
Toshiba ethernet cards
SMC Elite Ultra
2.3. Misc
AST 4 port serial card using shared IRQ.
ARNET 8 port serial card using shared IRQ.
BOCA ATIO66 6 port serial card using shared IRQ.
STB 4 port card using shared IRQ.
Mitsumi (all models) CDROM interface and drive.
Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound
and Roland MPU-401 sound cards.
FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
support is apparently close to materializing. Details will be posted
as the situation develops.
3. Obtaining FreeBSD.
---------------------
You may obtain FreeBSD in a variety of ways:
1. FTP/Mail
You can ftp FreeBSD and any or all of its optional packages from
`freebsd.cdrom.com' - the 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 1.1 may be ordered on CDROM from:
Walnut Creek CDROM
4041 Pike Lane, Suite D
Concord CA 94520
1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
Or via the internet from orders@cdrom.com. There current catalog can
be obtained via ftp as ftp.cdrom.com:/cdrom/catalog.
Cost is $39.95. Shipping (per order not per disc) is $5 in the US, Canada,
or Mexico and $10.00 overseas. They accept Visa, Mastercard, American
Express, and ship COD to the United States. California residents please
add 8.25% sales tax.
Should you be dissatisfied for any reason, the CD comes with an
unconditional return policy.
Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD,
you need to contact the FreeBSD team for that. Please see section 4 for
more information.
It should be noted, lest you get the wrong impression that "FreeBSD"
is anything but, that almost no one in the "core team" makes money
from distributions or anything else connected with FreeBSD. We simply
provide this information as a public service for those wishing to get
their releases from somewhere other than the net (and the easier it
is for you to obtain our software, the happier we are).
4. Reporting problems, making suggestions, submitting code.
-----------------------------------------------------------
Your suggestions, bug reports and contributions of code are always
valued - please do not hesitate to report any problems you may find
(preferably with a fix attached if you can!).
The prefered method to submit bug reports from a machine with internet
mail connectivity is to use the sendbug command. Bug reports will be
dutifully filed by our faithful bugfiler program and you can be sure
that we'll do our best to respond to all reported bugs as soon as
possible.
If, for some reason, you are unable to use the sendbug command to
submit a bug report, you can try to send it to:
FreeBSD-bugs@freefall.cdrom.com
Otherwise, for any questions or suggestions, please send mail to:
FreeBSD-questions@freefall.cdrom.com
Additionally, being a volunteer effort, we are always happy to have
extra hands willing to help - there are already far more enhancements
to be done than we can ever manage to do by ourselves! To contact us
on technical matters, or with offers of help, you may send mail to:
FreeBSD-hackers@freefall.cdrom.com
Since these mailing lists can experience significant amounts of
traffic, if you've got slow or expensive mail access and you're
only interested in keeping up with significant FreeBSD events, you may
find it preferable to subscribe to:
FreeBSD-announce@freefall.cdrom.com
All but the FreeBSD-bugs groups can be freely joined by anyone wishing to
do so. Send mail to MajorDomo@freefall.cdrom.com and include the keyword
`help' on a line by itself somewhere in the body of the message. This
will give you more information on joining the various lists, accessing
archives, etc.
5. Acknowledgements
-------------------
FreeBSD represents the cumulative work of many dozens, if not
hundreds, of individuals from around the world who have worked very
hard to bring you this release. It would be very difficult, if not
impossible, to enumerate everyone who's contributed to FreeBSD, but
nonetheless we shall try (in alphabetical order, of course). If your
name is not mentioned, please be assured that its omission is entirely
accidental.
The Computer Systems Research Group (CSRG), U.C. Berkeley.
Bill Jolitz, for his extensive work with 386BSD.
The FreeBSD "core" team:
Andrew A. Chernov
John Dyson
David Greenman
Rodney W. Grimes
Jordan K. Hubbard
Scott Mace
Andrew Moore
Rich Murphey
Geoff Rehmet
Paul Richards
Andreas Schulz
Nate Williams
Garrett A. Wollman
Special mention to:
Robert Bruce and Jack Velte of Walnut Creek CDROM, without
whose help (and continuing support) this release would never
have been possible.
Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
drive.
The NetBSD group for their frequent assistance and commentary.
Additional FreeBSD helpers and beta testers:
Gary Browing Jon Cargille
J.T. Conklin Chris Demetriou
Julian Elischer Bruce Evans
Sean Eric Fagan Guy Helmer
Jeffrey Hsu Terry Lambert
Gary Moyer Jaye Mathisen
Curt Mayer L Jonas Olsson
Chris Provenzano Dave Rivers
Guido van Rooij Steven Wallace
Rick Weldon Terry Williams
Atsushi Murai
And everyone at Montana State University for their initial support.
Thanks to everyone, especially those not mentioned, and we sincerely
hope you enjoy this release of FreeBSD!
The FreeBSD Core Team
$Id: RELNOTES.FreeBSD,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,127 @@
This file attempts to document just who is `responsible' for what in
the FreeBSD world. Since we're an all-volunteer group, the whole
concept of `responsibility' must, of course, be taken with a grain of
salt since the folks here may not always have time to deal with your
problem right away. With that in mind, you are encouraged to contact
these folks directly when your problem or suggestion clearly falls
into their area of responsibility. If your queries don't net any
positive results in, say, 48 hours, THEN you should try and contact
the group at large. In most cases, however, using these folks as
first-contacts will both cut down on our mail-overload and give you
faster service.
Thank you!
The FreeBSD Team
freebsd-hackers@freefall.cdrom.com
---
Legend:
-------
contrib = Contributed
doc = Documentation
lib = User-land library
misc = Misc user-land utility (contrib, other)
ports = Ported software in /usr/ports
prog = User-land program
share = Support data files
sys = Kernel and system code
tools = DOS support utilities
Category Person Email address
===============================================================================
contrib/xntpd Garrett Wollman wollman@lcs.mit.edu
doc/FAQ FAQ Team freebsd-faq@freefall.cdrom.com
lib/libF77 L. Jonas Olsson ljo@po.cwru.edu
lib/libc Garrett Wollman wollman@lcs.mit.edu
lib/libcrypt (non-US) Geoff Rehmet csgr@cs.ru.ac.za
lib/libcurses Andrew Chernov ache@astral.msk.su
lib/libkrb Garrett Wollman wollman@lcs.mit.edu
lib/libm Andrew Moore alm@netcom.com
lib/libpthread Chris Provenzano proven@mit.edu
lib/libskey Guido van Rooij guido@gvr.win.tue.nl
lib/libtelnet Garrett Wollman wollman@lcs.mit.edu
misc/addit Gary Clark II gclarkii@freefall.cdrom.com
misc/configit Gary Clark II gclarkii@freefall.cdrom.com
misc/gnats Andrew Moore alm@netcom.com
misc/manctl Geoff Rehmet csgr@cs.ru.ac.za
ports/{not below} Andrew Moore alm@freefall.cdrom.com
ports/aXe Jordan Hubbard jkh@freefall.cdrom.com
ports/archivers Scott Mace smace@freefall.cdrom.com
ports/bash Jordan Hubbard jkh@freefall.cdrom.com
ports/blt Jordan Hubbard jkh@freefall.cdrom.com
ports/cpm Joerg Wunsch joerg_wunsch@uriah.sax.de
ports/dgd Adam David adam@veda.is
ports/elm Scott Mace smace@freefall.cdrom.com
ports/emacs Jordan Hubbard jkh@freefall.cdrom.com
ports/exmh Jordan Hubbard jkh@freefall.cdrom.com
ports/ezd Jeffrey Hsu hsu@freefall.cdrom.com
ports/franz Jordan Hubbard jkh@freefall.cdrom.com
ports/fvwm Geoff Rehmet csgr@cs.ru.ac.za
ports/golddig Jeffrey Hsu hsu@freefall.cdrom.com
ports/ile Jordan Hubbard jkh@freefall.cdrom.com
ports/ispell Piero Serini piero@strider.st.dsi.unimi.it
ports/jpeg Scott Mace smace@freefall.cdrom.com
ports/kermit Scott Mace smace@freefall.cdrom.com
ports/ksh Sean Vickery seanv@cs.uq.edu.au
ports/kterm Satoshi Asami asami@cs.berkeley.edu
ports/lynx Serge V.Vakulenko vak@cronyx.msk.su
ports/mprof Jeffrey Hsu hsu@freefall.cdrom.com
ports/mtools Steven Wallace swallace@freefall.cdrom.com
ports/netaudio Jeffrey Hsu hsu@freefall.cdrom.com
ports/nethack Sean Vickery seanv@cs.uq.edu.au
ports/pcvt J"org Wunsch joerg_wunsch@uriah.sax.de
ports/piewm Satoshi Asami asami@cs.berkeley.edu
ports/pkg_install Jordan Hubbard jkh@freefall.cdrom.com
ports/popper Andreas Schulz ats@g386bsd.first.gmd.de
ports/point Jordan Hubbard jkh@freefall.cdrom.com
ports/sather Jeffrey Hsu hsu@freefall.cdrom.com
ports/schemetoc Jeffrey Hsu hsu@freefall.cdrom.com
ports/scm Jeffrey Hsu hsu@freefall.cdrom.com
ports/seahaven Jeffrey Hsu hsu@freefall.cdrom.com
ports/sml Jeffrey Hsu hsu@freefall.cdrom.com
ports/sup Jordan Hubbard jkh@freefall.cdrom.com
ports/tcl Jordan Hubbard jkh@freefall.cdrom.com
ports/tcl-dp Jordan Hubbard jkh@freefall.cdrom.com
ports/tclX Jordan Hubbard jkh@freefall.cdrom.com
ports/tcsh Scott Mace smace@freefall.cdrom.com
ports/tk Jordan Hubbard jkh@freefall.cdrom.com
ports/vile Jordan Hubbard jkh@freefall.cdrom.com
ports/vim Jordan Hubbard jkh@freefall.cdrom.com
ports/wine Jeffrey Hsu hsu@freefall.cdrom.com
ports/wu-ftpd Justin T. Gibbs gibbs@freefall.cdrom.com
ports/xcdplayer Steven Wallace swallace@freefall.cdrom.com
ports/xjewel Jeffrey Hsu hsu@freefall.cdrom.com
ports/xlock Scott Mace smace@freefall.cdrom.com
ports/xmine J"org Wunsch joerg_wunsch@uriah.sax.de
ports/xphoon Satoshi Asami asami@cs.berkeley.edu
ports/xv Scott Mace smace@freefall.cdrom.com
ports/ytalk Geoff Rehmet csgr@cs.ru.ac.za
ports/zircon Jordan Hubbard jkh@freefall.cdrom.com
ports/zsh Scott Mace smace@freefall.cdrom.com
prog/cc Poul-Henning Kamp phk@freefall.cdrom.com
prog/cc25 Poul-Henning Kamp phk@freefall.cdrom.com
prog/gdb Gary Jennejohn gj@pcs.dec.com
prog/man Jordan Hubbard jkh@freefall.cdrom.com
prog/telnet Garrett Wollman wollman@lcs.mit.edu
sys/fd J"org Wunsch joerg_wunsch@uriah.sax.de
sys/fd Serge V.Vakulenko vak@cronyx.msk.su
sys/i386 David Greenman davidg@root.com
sys/i386/isa/seagate Sean Vickery seanv@cs.uq.edu.au
sys/i386/isa/sound Steven Wallace swallace@freefall.cdrom.com
sys/i386/isa/bt742*.c Atsushi Murai amurai@spec.co.jp
sys/kern David Greenman davidg@root.com
sys/kern/ntp Garrett Wollman wollman@lcs.mit.edu
sys/lpt Geoff Rehmet csgr@cs.ru.ac.za
sys/net* David Greenman davidg@root.com
sys/netboot Martin Renters martin@innovus.com
sys/netinet Garrett Wollman wollman@lcs.mit.edu
sys/pcmcia Poul-Henning Kamp phk@freefall.cdrom.com
sys/scheduler John Dyson dyson@freefall.cdrom.com
sys/syscons So/ren Schmidt sos@freefall.cdrom.com
sys/vm David Greenman davidg@root.com
sys/vm John Dyson dyson@freefall.cdrom.com
sys/wt Serge V.Vakulenko vak@cronyx.msk.su
tools/booteasy Serge V.Vakulenko vak@cronyx.msk.su

View file

@ -0,0 +1,89 @@
Technical support for this product is NOT provided by Walnut Creek CDROM.
You need to contact one of the following companies and/or people for
technical support.
Accurate Automation Company
6005 S.E. Laurel Street
Milwaukie, OR 97222
Telephone: +1-503-653-7376
Email: rgrimes@agora.rain.com
Accurate Automation provides support for FreeBSD including installation,
system configuration, hardware and software trouble shooting, and related
issues. Rates depend upon the type of work being done. Hours are from
10:00 am to 10:00pm PST.
Gary Clark II
GB Data Consulting
3801 Polk
Houston, Texas 77003 USA
Telephone: +1-713-587-1644
Email: gclarkii@radon.gbdata.com
GB Data Consulting provides support for FreeBSD including installation, usage
and system administration. We also provide classes, on-site service and
distribution sets on floppy. Please email info@radon.gbdata.com or call for
rates and information.
Cronyx Ltd.
Research Computer Center,
Moscow State University,
Moscow 199899, Russia
Phone: +7-095-939-5678
Email: info@cronyx.msk.su
Cronyx Ltd. provides support for FreeBSD including installation,
configuration, Relcom network connection via UUCP, dialup and leased
line IP. We also provide X Windows configuration and localization,
as well as additional packages installation. Distribution sets on
floppies and tape cartridges available. System software development
including drivers for non-standard equipment.
Jordan Hubbard
Timberline Associates (est 1978)
Dublin, Ireland [And soon Boston / San Francisco]
Support hours: 1000 - 2300 GMT
Tel #: 00353-1-332796
Email: jkh@al.org
Telephone (or Internet) and on-site consulting for FreeBSD in Ireland,
the United States, United Kingdom and most parts of Europe. Services include
installation, system configuration, networking and custom software
projects, graphical user interfaces a specialty (actively involved with
The X Window System since Version 9 and contributor to the X Consortium).
Reasonable and flexible rates comensurate with location and duration of
assignment. Internet assignments are welcomed, and generally billed at
lower rates.
Vector Systems Ltd, Julian H. Stacey.
Post: Holz Strasse 27d, D 80469, Munich (Muenchen), Germany (Deutschland).
Tel.: +49 89 268616 09:00-22:00 TZ=GMT+1
Email: stacey@freefall.cdrom.com
Custom designs & support using FreeBSD + X-Windows + FSF/GNU, + own Unix & DOS
C tools. Systems engineering, hardware interfacing, multi lingual systems
(European, Cyrillic, Chinese), communications, scientific, industrial real
time programming. Source Tapes: QIC 525M, 150M, 60M.
Deutsch: Man kann mir in Deutsch schreiben, (oder mich anrufen).
Francais: Je comprend Francais, mais je n'ecris pas des responses en Francais.
Sean Vickery
2/449 Milton Road
Auchenflower Qld 4066
Australia
Telephone: +61 (0)7 870 5241
Email: seanv@cs.uq.edu.au
Sean offers support in most FreeBSD matters, including installation
and configuration. His rates are reasonable. As well as on-site
help, support is available over the phone and the net.
$Id: SUPPORT.TXT,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,38 @@
This is my current TODO list for 1.1.5. Please feel free to add to
it, assuming that you've actually got some confidence that you or
someone else will be able to actually get to whatever it is (or it's
so critical that you don't think 1.1.5 could/should be released
without it).
Also, please bear in mind the following milestones we have to hit:
June 5th Feature Freeze (bug fixes and cleanup work only).
June 16th Code Freeze
June 20th Roll binaries - begin initial testing
June 23rd Announce availability of 1.1.5.
(*) = Task is completed
(@) = Task is abandoned
Task Urgency Who
-------------------------------------------------------------------------------
Floppy driver fixes Low * Joerg Wunsch
Sound driver (GUS/Multicast/cleanup) Medium Steven W/Andrew C.
Curses library problems Medium * Steven W.
SIO driver - reported problems High * Andrew C/Bruce E/???
Syscons integration / new features High * Soren Schmidt/Jordan
Update FT driver Medium * Javier R/Steven G.
Update gdb High * Paul
Make pcfs less dangerous Low @ ???
Bruce's disklabel and bad144 fixes Medium * Andrew C.
Misc NetBSD drivers for weird devices Low @ Geoff
Multicast Support Medium * Jordan
Bounce Buffer fixes High * John/David
VM panics and assorted lossage High * John/David
Secure Key support Low * Guido
Install script enhancements Medium * Andrew M/Jordan
Fsck/umount cooperation with dirty bit Low @ Paul R.
PCFS data corruption with cp Medium * Steven W./ATS
PCFS extended DOS partition support Low @ ???
ISOFS over NSF fix Medium/High * ???
Libcompat Low * Joerg Wunsch

View file

@ -0,0 +1,196 @@
386BSD Release 0.1
Contributor List
Lynne Greer Jolitz
William F. Jolitz
_H_a_r_d_w_a_r_e _a_n_d _M_o_n_e_t_a_r_y _C_o_n_t_r_i_b_u_t_o_r_s
Many people and firms have provided hardware and/or money to
try and keep this unfunded project going despite a recession
and hard times -- usually by digging into their own pockets.
Each of these contributors gave, not only because they
believed that the continuation of 386BSD is vital to the
health of the research, educational, and development commun-
ities, but also because they realize that an individual can
and does make a difference!
Without the help of the people listed here, this release
would simply not have been possible. We would especially
like to thank Thos Sumner, whose loan of a 486/50 SCSI PC
made development go more rapidly. The rest of the 386BSD
user community should make special note of all these people
and firms and commend them for their generosity and
foresight.
We hope that their leadership and vision will serve as shin-
ing examples to the entire 386BSD user community, and serve
to encourage others to actively participate in 386BSD.
Jan van den Bosch
Compaq Computer Corporation
Cyrix Corporation
Dixon Dick
Steven P. Donegan
Jon Erickson
Eric J. Haug
Bob McGhee
Jesus Monroy Jr.
Andrew Moore
Rich Murphey
Mark Ng
Kenji Okamoto
John Plocher
Mark R. Riordan
John B. Scalia
Steve Sizemore
Thos Sumner
David E. Tweten
386BSD CONTRIB LIST 1 July 1992
_S_o_f_t_w_a_r_e _C_o_n_t_r_i_b_u_t_o_r_s
The following people have contributed key software programs,
modules and fixes, including novel work and ports of popular
public domain user programs. Some of this software was
directly contributed to us, while other items were made
available to all users via the network. Occasionally,
several people came up with a variety of approaches for a
single item. In this instance, we tried to choose the one
which we felt would best serve the rest of the 386BSD user
base for this release. However, the creativity and persever-
ance of all the software contributors trying to make 386BSD
better for the entire 386BSD user community was consider-
able. Each individual effort is worthy of pride.
We wish to personally thank all of these people, as they
have helped make 386BSD Release 0.1 a reality. We hope that
these contributors and all the rest of the 386BSD user com-
munity will continue to actively participate to make future
releases even better!
James Van Artsdalen
Scott Burris
Randall Dean
Chris Demetriou
Mark Eichin
Bruce Evans
Steve Ferguson
Jeffrey Goh
David Greenman
Amancio Hasty Jr
John W. Hatley
Eric J. Haug
Tom Ivar Helbekkmo
John D. Irwin
Peter Klingebiel
Paul Kranenburg
Daniel Lanciani
Karl Lehenbauer
Lee M. J. McLoughlin
Andrew J. Michael
Jesus Monroy Jr.
Daniel A. Muntz
Richard Murphey
Glen Overby
Brad Parker
Herb Pereyl
Ken Raeburn
Paul Richards
Guido van Rooij
Peng-Toh Sim
Wolfgang Solfrank
Dave Stanhope
386BSD CONTRIB LIST 2 July 1992
Mark Tinguely
Linus Torvalds
Richard Tobin
Rob Warnock
Christian Wiedmann
Pace Willisson
Joerg Wunsch
And all of the other 386BSD Software Contributors.
_S_u_p_p_o_r_t _a_n_d _A_d_v_i_c_e _C_o_n_t_r_i_b_u_t_o_r_s
Many people have continually encouraged us over the course
of these releases, and provided us with technical advice and
guidance. These people have also spent considerable time and
energy getting this software out to the rest of the 386BSD
community. While it is impossible for us to list everyone
who has been supportive of 386BSD, we wish to personally
thank some of the people who have been of special assistance
to us directly over the course of getting 386BSD out the
door.
Bruce Blakely
Dave Campbell
Free Software Foundation
Paul Fromberg
Tom Genereaux
John Gilmore
Dave Harris
Jim Joyce
Dan Kionka
Dory Leifer
Per Lindqvist
Marshall Midden
Rich Morin
Silicon Valley Computer Society
John Sokol
Thos Sumner
Karen Trocki
Rob Warnock
and a special thanks to:
John Erickson, Tami Zemel, Ray Valdez, Monica Berg, Michael Floyd
and everyone else at Dr. Dobbs Journal.
Juergen Fey, Rainer Huttenloher, Gerd Oskar Bausewein
and everyone else at UNIX Magazin.
And all of the 386BSD User Community.
386BSD CONTRIB LIST 3 July 1992

View file

@ -0,0 +1,185 @@
FreeBSD 1.1
Contributor List
Derived Software Contributors:
This software was derived from William F. Jolitz's 386BSD release 0.1.
Please see the file CONTRIB.386BSD for the list of contributors from
386BSD.
Included in this release are the patches from the patch kit version
0.2.4. The names of contributors from the patch kit are listed below.
There are portions of NetBSD that has been intergraged into FreeBSD
as well. We would like to thank all the contributors to NetBSD for
their work.
Hardware Contributors:
A special thanks to Robert Bruce and Jack Velte of Walnut Creek CDROM
for providing a 486/DX2-66 EISA/VL system that is being used for the
development work. It would have been impossible to do this release
with out their support.
Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
drive.
FreeBSD core:
Andrew A. Chernov <ache@astral.msk.su>
Andrew Moore <alm@netcom.com>
Andreas Schulz <ats@g386bsd.first.bmd.de>
John Dyson <dyson@implode.rain.com>
Geoff Rehmet <csgr@cs.ru.ac.za>
David Greenman <davidg@Root.COM>
Jordan K. Hubbard <jkh@whisker.hubbard.ie>
Nate Williams <nate@bsd.coe.montana.edu>
Paul Richards <paul@isl.cf.ac.uk>
Rich Murphey <rich@lamprey.utmb.edu>
Rodney W. Grimes <rgrimes@cdrom.com>
Scott Mace <smace@neosoft.com>
Garrett A. Wollman <wollman@freefall.cdrom.com>
Additional FreeBSD Contributors:
Adam Glass <glass@postgres.berkeley.edu>
Andrew Herbert <andrew@werple.apana.org.au>
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>
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>
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>
Yuval Yarom <yval@cs.huji.ac.il>
Patch kit patch contributors:
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.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,131 @@
386BSD Release 0.1
Copyright
/*
* Copyright (c) 1989, 1990, 1991, 1992 William F. Jolitz, TeleMuse
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* This software is a component of "386BSD" developed by
* William F. Jolitz, TeleMuse.
* 4. Neither the name of the developer nor the name "386BSD"
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* 386BSD WAS DEVELOPED BY WILLIAM F. JOLITZ.
* 386BSD IS INTENDED FOR RESEARCH AND EDUCATIONAL PURPOSES.
* THIS SOFTWARE SHOULD NOT BE CONSIDERED TO BE A COMMERCIAL PRODUCT.
* THE DEVELOPER URGES THAT USERS WHO REQUIRE A COMMERCIAL PRODUCT
* NOT MAKE USE OF THIS WORK.
*
* FOR USERS WHO WISH TO UNDERSTAND THE 386BSD SYSTEM DEVELOPED
* BY WILLIAM F. JOLITZ, WE RECOMMEND THE USER STUDY WRITTEN
* REFERENCES SUCH AS THE "PORTING UNIX TO THE 386" SERIES
* (BEGINNING JANUARY 1991 "DR. DOBBS JOURNAL", USA AND BEGINNING
* JUNE 1991 "UNIX MAGAZIN", GERMANY) BY WILLIAM F. JOLITZ AND
* LYNNE GREER JOLITZ, AS WELL AS OTHER BOOKS ON UNIX AND THE
* ON-LINE 386BSD USER MANUAL BEFORE USE. A BOOK DISCUSSING THE INTERNALS
* OF 386BSD ENTITLED "386BSD FROM THE INSIDE OUT" WILL BE AVAILABLE LATE 1992.
*
* THIS SOFTWARE IS PROVIDED BY THE DEVELOPER ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE DEVELOPER BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
*/
386BSD Copyright 1 July 1992
386BSD Copyright 2 July 1992

View file

@ -0,0 +1,121 @@
This software contains software developed by the University of
California, Berkeley, and its contributors; by the Free Software
Foundation; by the University of Illinois; by the Massachusetts
Institute of Technology; by the University of Vermont and State
Agricultural College; by Carnegie Mellon University; and by a large
number of contributors, whose names are listed in the notices below.
Portions of this software are subject to one or more of the following
copyright notices. Please see the individual files for the terms and
conditions.
Copyright (C) 1980, 1983, 1986, 1988, 1990, 1991, Regents of the
University of California
Copyright (C) 1986, 1987, 1988, 1989, 1990, 1991, 1992, 1993, Free
Software Foundation, Inc.
Copyright (C) 1976, Board of Trustees of the University of Illinois
Copyright (C) 1980, 1981, Ken Harrenstien
Copyright (C) 1982, 1988, 1989, Walter Tichy
Copyright (C) 1983, 1986, 1992, 1993, Eric P. Allman
Copyright (C) 1983, Kenneth L. Greer
Copyright (C) 1984, 1985, 1986, 1987, 1992, Sun Microsystems, Inc.
Copyright (C) 1984, 1987, Stephen L. Moshier
Copyright (C) 1984, 1989, 1990, Bob Corbett and Richard Stallman
Copyright (C) 1984, University of British Columbia
Copyright (C) 1985, 1986, Wayne A. Christopher
Copyright (C) 1985, 1987, 1988, 1989, Adobe Systems, Inc.
Copyright (C) 1985, Stichting Mathematisch Centrum
Copyright (C) 1986, 1987, 1989, 1990, 1991, 1992, Ian F. Darwin
Copyright (C) 1986, 1987, 1989, Frame Technology, Inc.
Copyright (C) 1986, 1987, 1992, Daniel D. Lanciani
Copyright (C) 1986, 1987, Ed James
Copyright (C) 1986, Breslow
Copyright (C) 1986, Gary S. Brown
Copyright (C) 1986, Larry Wall
Copyright (C) 1986, Noah Morgan
Copyright (C) 1986, Stephen Satchell
Copyright (C) 1987, 1988, 1989, 1990, 1991, 1992, Carnegie Mellon University
Copyright (C) 1987, 1988, 1989, Sony Corp.
Copyright (C) 1987, 1988, John Stanback
Copyright (C) 1987, 1988, Ronald S. Karr and Landon Curt Noll
Copyright (C) 1987, 1989, 1990, 1991, Massachusetts Institute of Technology
Copyright (C) 1987, David C. Elliott.
Copyright (C) 1987, IBM Corporation
Copyright (C) 1987, Stuart Cracraft
Copyright (C) 1987, United States Army
Copyright (C) 1988, 1989, 1990, 1993, 1994, Paul A. Vixie
Copyright (C) 1988, 1989, Adam de Boor
Copyright (C) 1988, 1990, University of Utah
Copyright (C) 1988, Julian Onions
Copyright (C) 1988, Mark Nudleman
Copyright (C) 1988, Rayan S. Zachariassen
Copyright (C) 1989, 1990, 1991, 1992, 1993, Frank Kardel
Copyright (C) 1989, 1990, 1991, 1992, 1993, William S. Jolitz
Copyright (C) 1989, 1990, 1991, 1992, Brian Berliner
Copyright (C) 1989, Berkeley Softworks
Copyright (C) 1989, Dale Schumacher
Copyright (C) 1989, Dave Taylor
Copyright (C) 1989, Kenneth Almquist
Copyright (C) 1989, Matthew Self
Copyright (C) 1989, Robert V. Baron
Copyright (C) 1990, 1991, 1992, 1993, AT&T Bell Laboratories and Bellcore
Copyright (C) 1990, 1991, John W. Eaton
Copyright (C) 1990, 1991, Paul Eggert
Copyright (C) 1990, 1993, Andrew Moore
Copyright (C) 1990, John Robert LoVerso
Copyright (C) 1990, Open Software Foundation, Inc.
Copyright (C) 1990, RSA Data Security, Inc.
Copyright (C) 1991, 1992, 1993, 1994, Chris Provenzano
Copyright (C) 1991, 1992, 1993, Ian Lance Taylor
Copyright (C) 1991, 1992, Per Bothner
Copyright (C) 1991, 1992, Per Cederqvist
Copyright (C) 1991, Gregory M. Christy
Copyright (C) 1991, Inge Wallin
Copyright (C) 1991, Joseph Friedman
Copyright (C) 1992, 1993, 1994, David L. Mills
Copyright (C) 1992, 1993, Christopher G. Demetriou
Copyright (C) 1992, 1993, Garrett A. Wollman
Copyright (C) 1992, 1993, HD Associates
Copyright (C) 1992, 1993, Holger Veit
Copyright (C) 1992, 1993, Jean-Loup Gailly
Copyright (C) 1992, 1993, 1994 Joerg Wunsch
Copyright (C) 1992, 1993, John Brezak
Copyright (C) 1992, 1993, Motorola, Inc.
Copyright (C) 1992, 1993, Soeren Schmidt
Copyright (C) 1992, 1993, Theo de Raadt
Copyright (C) 1992, 1993, University of Vermont and State Agricultural College
Copyright (C) 1992, Cygnus Support
Copyright (C) 1992, Diomidis Spinellis
Copyright (C) 1992, Henry Spencer
Copyright (C) 1992, Jeff Polk
Copyright (C) 1992, Terrence R. Lambert
Copyright (C) 1992, University of Guelph
Copyright (C) 1993, 1994, Andrew A. Chernov
Copyright (C) 1993, 1994, David Greenman
Copyright (C) 1993, 1994, John S. Dyson
Copyright (C) 1993, Adam Glass
Copyright (C) 1993, Atsushi Murai
Copyright (C) 1993, Brian Moore
Copyright (C) 1993, Daniel Boulet and RTMX Inc.
Copyright (C) 1993, David Muir Sharnoff
Copyright (C) 1993, David Parsons
Copyright (C) 1993, Gary Clark II
Copyright (C) 1993, Hannu Savolainen
Copyright (C) 1993, Herb Peyerl
Copyright (C) 1993, Herve Schauer Consultants
Copyright (C) 1993, Julian Elischer
Copyright (C) 1993, Julian Stacey
Copyright (C) 1993, K. J. Dryllerakis
Copyright (C) 1993, Martin Birgmeier
Copyright (C) 1993, Paul Kranenburg
Copyright (C) 1993, Paul Richards
Copyright (C) 1993, Thomas Koenig
Copyright (C) 1993, Winning Strategies, Inc.
Copyright (C) 1994, Christoph M. Robitschko
Copyright (C) 1994, University of Maryland
Copyright (C) 1993, 1994, jc@irbs.UUCP (John Capo),
vak@zebub.msk.su (Serge Vakulenko),
ache@astral.msk.su (Andrew A. Chernov)
$Id: COPYRIGHT.FreeBSD,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,59 @@
The FreeBSD software is being mirrored at the following locations:
Country Site/Directory/Maintainer
======= =========================================================
Australia minnie.cs.adfa.oz.au:/BSD/FreeBSD-1.1-RELEASE
<wkt@cs.adfa.oz.au>
Australia ftp.physics.su.oz.au:/FreeBSD
David Dawes <dawes@physics.su.oz.au>
Australia ftp.une.edu.au:/pub/FreeBSD
Gordon Smith <Gordon.Smith@une.edu.au>
Austria ftp.tu-graz.ac.at:/pub/FreeBSD
<ftp@ftp.tu-graz.ac.at>
Finland ftp.funet.fi:/pub/unix/FreeBSD
<unix-adm@nic.funet.fi>
France ftp.ibp.fr:/pub/FreeBSD
<ftp@ftp.ibp.fr>
Germany ftp.informatik.tu-muenchen.de:/pub/comp/os/bsd/FreeBSD
<bsd@informatik.tu-muenchen.de>
Germany ftp.uni-duisburg.de:/pub/unix/FreeBSD
<ftp@ftp.uni-duisburg.de>
Germany gil.physik.rwth-aachen.de:/pub/FreeBSD
<kuku@acds.physik.rwth-aachen.de>
Hong Kong ftp.cs.cuhk.hk:/pub/FreeBSD
<unknown>
Israel orgchem.weizmann.ac.il:/pub/FreeBSD
<serg@klara.weizmann.ac.il>
Netherlands ftp.nl.net:/pub/os/FreeBSD
<archive@nl.net>
Russia ftp.kiae.su:/FreeBSD
<arcman@kiae.su>
UK src.doc.ic.ac.uk:/packages/FreeBSD
<wizards@doc.ic.ac.uk>
USA gatekeeper.dec.com:/pub/BSD/FreeBSD
<hubbard@gatekeeper.dec.com>
USA freebsd.uml.edu:/FreeBSD
<oneill@cs.uml.edu>
USA wuarchive.wustl.edu:/systems/unix/FreeBSD
<archives@wugate.wustl.edu>
$Id: MIRROR.SITES,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

4
es/releases/1.1/Makefile Normal file
View file

@ -0,0 +1,4 @@
DATA= CONTRIB.386BSD CONTRIB.FreeBSD COPYRIGHT.386BSD COPYRIGHT.FreeBSD
DATA+= MIRROR.SITES PERSONAL.ACKS RELNOTES.FreeBSD SUPPORT.TXT
.include "../../web.mk"

View file

@ -0,0 +1,17 @@
The following contributors would like to make these personal
acknowledgements (in no particular order):
Garrett Wollman would like to thank Gary Barbour and Steve Ackerman of
Utah; Tim Raymond, Jim White, and Jim Ertle of UVM; Malcolm Carlock at
UNR; and John Wroclawski of MIT.
Nate Williams would like to thank Jaye Mathisen and the entire Computer
Science department of Montana State University for their help, hardware
and encouragement.
Jordan Hubbard would like to thank IEUNET for bringing the INTERNET to
Ireland, thus making his participation possible at all (albeit expensive)
and his Mom, who would probably be pleased if only she understood any of
this. Hi Mom.
$Id: PERSONAL.ACKS,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,303 @@
RELEASE NOTES
FreeBSD
Release 1.1
1. Technical overview
---------------------
FreeBSD is a freely available, full source 4.3 (+4.4 enhancements) BSD
release for Intel i386/i486 (or compatable) based PC's. It is based
heavily on Bill Jolitz's 386BSD 0.1, with additions from "the patchkit",
NetBSD, CSRG, and the Free Software Foundation.
Many hundreds of bugs from the 386BSD 0.1 distribution were fixed,
and many out-of-date pieces of software were upgraded to their current
releases in the GAMMA distribution. This 1.1 distribution fixes
many of the first-run problems our BETA and GAMMA users reported back
to us.
Additionally, many packages such as XFree86 2.1, xview 3.2, elm, nntp,
mh, InterViews and dozens of other miscellaneous utilities have been ported
and are now available as add-ons. See then next section of this document
for more details.
For a list of contributors, please see the files "CONTRIB.FreeBSD" and
"CONTRIB.386BSD", which should be bundled with your distribution.
The core of FreeBSD does not contain DES code which would inhibit its
being exported outside the United States. There is an add-on package
to the core distribution, for use only in the United States, that
contains the programs that normally use DES. The 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.
2. Supported Configurations
---------------------------
FreeBSD currently runs on a wide variety of ISA and EISA bus based
PC's, ranging from 386sx to 486 class machines (though the 386sx is
not recommended). Support for generic IDE or ESDI drive configurations,
various SCSI controller, network and serial cards is also provided.
Following is a list of all currently known disk controllers and
ethernet cards known to work with FreeBSD. Other configurations may
very well work, and we have simply not received any indication of
this.
2.1. Disk Controllers
WD1003 (any generic MFM/RLL)
WD1007 (any generic IDE/ESDI)
Adaptec 154x series ISA SCSI controller (as long as you have less than
16MB of main memory).
Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
[Note that Buslogic was formerly known as "Bustec"]
Buslogic 545S.
Buslogic 445S VLB SCSI controller
Buslogic 742A and 747.
Please see special notes in /usr/src/KNOWNBUGS (filed under bt742a.c) for
details concerning possible buggy firmware and undocumented switch settings
that may be necessary for proper operation of your controller.
DTC 3290 EISA SCSI controller in 1542 emulation mode.
Ultra Store 14F and 34F.
Seagate ST01/02 SCSI controllers.
Future Domain 8xx/950 series SCSI controllers.
With all supported SCSI controllers, full support is provided for
SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
DAT) and CD ROM drives. Note: This and the mcd driver (Mitsumi CDROM
interface card) is the only way a CD ROM drive may be currently
attached to a FreeBSD system; we do not support SoundBlaster CDROM
interface, or other "mini SCSI" adapters.
Some controllers have limitations with the way they deal with >16MB of memory,
due to the fact that the ISA bus only has a DMA address space of 24 bits.
If you do your arithmetic, you'll see that this makes it impossible to do
direct DMA to any address >16MB. This limitation is even true of some
EISA controllers (which are normally 32 bit) when they're configured to
emulate an ISA card, which they then do in *all* respects. This problem
is avoided entirely by IDE controllers (which do not use DMA), true EISA
controllers (like the UltraStor or Adaptec 1742A) and most VLB (local bus)
controllers. In these cases, the system will use "bounce buffers" to
to talk to the controller, and is generally the default.
2.2. Ethernet cards
SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
based clones.
Isolan AT 4141-0 (16 bit)
Isolink 4110 (8 bit)
Novell NE1000, NE2000, and NE2100 ethernet interface.
3Com 3C503 Etherlink II
3Com 3C509 Ethernet cards
Toshiba ethernet cards
SMC Elite Ultra
2.3. Misc
AST 4 port serial card using shared IRQ.
ARNET 8 port serial card using shared IRQ.
BOCA ATIO66 6 port serial card using shared IRQ.
STB 4 port card using shared IRQ.
Mitsumi (all models) CDROM interface and drive.
Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound
and Roland MPU-401 sound cards.
FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
support is apparently close to materializing. Details will be posted
as they develop.
3. Obtaining FreeBSD.
---------------------
You may obtain FreeBSD in a variety of ways:
1. FTP/Mail
You can ftp FreeBSD and any or all of its optional packages from
`freebsd.cdrom.com' - the 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 may be ordered on CDROM from:
Walnut Creek CDROM
4041 Pike Lane, Suite D
Concord CA 94520
1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
Or via the internet from orders@cdrom.com. There current catalog can
be obtained via ftp as ftp.cdrom.com:/cdrom/catalog.
Cost is $39.95. Shipping (per order not per disc) is $5 in the US, Canada,
or Mexico and $10.00 overseas. They accept Visa, Mastercard, American
Express, and ship COD to the United States. California residents please
add 8.25% sales tax.
Should you be dissatisfied for any reason, the CD comes with an
unconditional return policy.
Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD,
you need to contact the FreeBSD team for that. Please see section 4 for
more information.
It should be noted, lest you get the wrong impression that "FreeBSD"
is anything but, that almost no one in the "core team" makes money
from distributions or anything else connected with FreeBSD. We simply
provide this information as a public service for those wishing to get
their releases from somewhere other than the net (and the easier it
is for you to obtain our software, the happier we are).
4. Reporting problems, making suggestions, submitting code.
-----------------------------------------------------------
Your suggestions, bug reports and contributions of code are always
valued - please do not hesitate to report any problems you may find
(preferably with a fix attached if you can!).
The prefered method to submit bug reports from a machine with internet
mail connectivity is to use the sendbug command. Bug reports will be
dutifully filed by our faithful bugfiler program and you can be sure
that we'll do our best to respond to all reported bugs as soon as
possible.
If, for some reason, you are unable to use the sendbug command to
submit a bug report, you can try to send it to:
FreeBSD-bugs@freefall.cdrom.com
Otherwise, for any questions or suggestions, please send mail to:
FreeBSD-questions@freefall.cdrom.com
Additionally, being a volunteer effort, we are always happy to have
extra hands willing to help - there are already far more enhancements
to be done than we can ever manage to do by ourselves! To contact us
on technical matters, or with offers of help, you may send mail to:
FreeBSD-hackers@freefall.cdrom.com
Since these mailing lists can experience significant amounts of
traffic, if you've got slow or expensive mail access and you're
only interested in keeping up with significant FreeBSD events, you may
find it preferable to subscribe to:
FreeBSD-announce@freefall.cdrom.com
All but the FreeBSD-bugs groups can be freely joined by anyone wishing to
do so. Send mail to MajorDomo@freefall.cdrom.com and include the keyword
`help' on a line by itself somewhere in the body of the message. This
will give you more information on joining the various lists, accessing
archives, etc.
5. Acknowledgements
-------------------
FreeBSD represents the cumulative work of many dozens, if not
hundreds, of individuals from around the world who have worked very
hard to bring you this release. It would be very difficult, if not
impossible, to enumerate everyone who's contributed to FreeBSD, but
nonetheless we shall try (in alphabetical order, of course). If your
name is not mentioned, please be assured that its omission is entirely
accidental.
The Computer Systems Research Group (CSRG), U.C. Berkeley.
Bill Jolitz, for his extensive work with 386BSD.
The FreeBSD "core" group:
Andrew A. Chernov
John Dyson
David Greenman
Rodney W. Grimes
Jordan K. Hubbard
Scott Mace
Andrew Moore
Rich Murphey
Geoff Rehmet
Paul Richards
Andreas Schulz
Nate Williams
Garrett A. Wollman
Special mention to:
Robert Bruce and Jack Velte of Walnut Creek CDROM, without
whose help (and continuing support) this release would never
have been possible.
Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
drive.
The NetBSD group for their frequent assistance and commentary.
Additional FreeBSD helpers and beta testers:
Gary Browing Jon Cargille
J.T. Conklin Chris Demetriou
Julian Elischer Bruce Evans
Sean Eric Fagan Guy Helmer
Jeffrey Hsu Terry Lambert
Gary Moyer Jaye Mathisen
Curt Mayer L Jonas Olsson
Chris Provenzano Dave Rivers
Guido van Rooij Steven Wallace
Rick Weldon Terry Williams
And everyone at Montana State University for their initial support.
Thanks to everyone, especially those not mentioned, and we sincerely
hope you enjoy this release of FreeBSD!
The FreeBSD Core Group
$Id: RELNOTES.FreeBSD,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,89 @@
Technical support for this product is NOT provided by Walnut Creek CDROM.
You need to contact one of the following companies and/or people for
technical support.
Accurate Automation Company
6005 S.E. Laurel Street
Milwaukie, OR 97222
Telephone: +1-503-653-7376
Email: rgrimes@agora.rain.com
Accurate Automation provides support for FreeBSD including installation,
system configuration, hardware and software trouble shooting, and related
issues. Rates depend upon the type of work being done. Hours are from
10:00 am to 10:00pm PST.
Gary Clark II
GB Data Consulting
3801 Polk
Houston, Texas 77003 USA
Telephone: +1-713-587-1644
Email: gclarkii@radon.gbdata.com
GB Data Consulting provides support for FreeBSD including installation, usage
and system administration. We also provide classes, on-site service and
distribution sets on floppy. Please email info@radon.gbdata.com or call for
rates and information.
Cronyx Ltd.
Research Computer Center,
Moscow State University,
Moscow 199899, Russia
Phone: +7-095-939-5678
Email: info@cronyx.msk.su
Cronyx Ltd. provides support for FreeBSD including installation,
configuration, Relcom network connection via UUCP, dialup and leased
line IP. We also provide X Windows configuration and localization,
as well as additional packages installation. Distribution sets on
floppies and tape cartridges available. System software development
including drivers for non-standard equipment.
Jordan Hubbard
Timberline Associates (est 1978)
Dublin, Ireland [And soon Boston / San Francisco]
Support hours: 1000 - 2300 GMT
Tel #: 00353-1-332796
Email: jkh@al.org
Telephone (or Internet) and on-site consulting for FreeBSD in Ireland,
the United States, United Kingdom and most parts of Europe. Services include
installation, system configuration, networking and custom software
projects, graphical user interfaces a specialty (actively involved with
The X Window System since Version 9 and contributor to the X Consortium).
Reasonable and flexible rates comensurate with location and duration of
assignment. Internet assignments are welcomed, and generally billed at
lower rates.
Vector Systems Ltd, Julian H. Stacey.
Post: Holz Strasse 27d, D 80469, Munich (Muenchen), Germany (Deutschland).
Tel.: +49 89 268616 09:00-22:00 TZ=GMT+1
Email: stacey@freefall.cdrom.com
Custom designs & support using FreeBSD + X-Windows + FSF/GNU, + own Unix & DOS
C tools. Systems engineering, hardware interfacing, multi lingual systems
(European, Cyrillic, Chinese), communications, scientific, industrial real
time programming. Source Tapes: QIC 525M, 150M, 60M.
Deutsch: Man kann mir in Deutsch schreiben, (oder mich anrufen).
Francais: Je comprend Francais, mais je n'ecris pas des responses en Francais.
Sean Vickery
2/449 Milton Road
Auchenflower Qld 4066
Australia
Telephone: +61 (0)7 870 5241
Email: seanv@cs.uq.edu.au
Sean offers support in most FreeBSD matters, including installation
and configuration. His rates are reasonable. As well as on-site
help, support is available over the phone and the net.
$Id: SUPPORT.TXT,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $

View file

@ -0,0 +1,3 @@
DOCS= announce.sgml notes.sgml
.include "../../web.mk"

View file

@ -0,0 +1,115 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "FreeBSD 2.0.5 RELEASE Announcement">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $Id: announce.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<p>
<b>Date:</b> Sat, 10 Jun 1995 13:01:12 -0700<br>
<b>From:</b> "Jordan K. Hubbard" &lt;jkh@freefall.cdrom.com&gt;<br>
<b>To:</b> announce@freefall.cdrom.com, hackers@freefall.cdrom.com<br>
<b>Subject:</b> Announcing FreeBSD 2.0.5 RELEASE!
<p>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.
<p>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.
<p>Highlights of this release are:
<ul>
<li>Multi-lingual documentation files.
<li>Completely menu driven installation.
<li>More installation media types.
<li>Support for a much larger range of PC hardware.
<li>Easy mounting of DOS partitions and CD devices
mounted automatically.
<li>"Canned" installation types for easy installs.
<li>Easy post-configuration menu
</ul>
<p>And many other new features and bug fixes.
<p>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.
<p>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!
<p>The usual locations:
<ul>
<li><a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-RELEASE">ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-RELEASE</a>
<li><a href="ftp://freefall.cdrom.com/pub/FreeBSD/2.0.5-RELEASE">ftp://freefall.cdrom.com/pub/FreeBSD/2.0.5-RELEASE</a>
</ul>
<p>As well as the usual mirrors, once they pick it up.
<p>It is also available on CD from Walnut Creek CDROM, the
project's principle sponsors. Please see the release notes
for ordering information.
<p>Any feedback should be sent to <a
href="mailto:hackers@freebsd.org">hackers@freebsd.org</a>.
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.
<p>Thank you!
<p> Jordan
<hr>
<p><b>Date:</b> Mon, 12 Jun 1995 00:33:07 -0700<br>
<b>From:</b> Gary Palmer &lt;gpalmer@westhill.cdrom.com&gt;<br>
<b>To:</b> announce@FreeBSD.ORGD<br>
<b>Subject:</b> 2.0.5-RELEASE update
<p>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
<tt>/pub/FreeBSD/2.0.5-RELEASE/UPDATES</tt> directory on <a
href="ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-RELEASE/UPDATES">ftp.cdrom.com</a>
and <a
href="ftp://freefall.cdrom.com/pub/FreeBSD/2.0.5-RELEASE/UPDATES">freefall.cdrom.com</a>
with a version of boot.flp which will fix the following
problems:
<ul>
<li>The kernel was too big to boot on 4Mb machines.
<li>It was possible to specify the filesystem mount points
in such a way that the program would mount the filesystem
before the parent filesystem was mounted (e.g. it would
mount /usr/local and then /usr)
</ul>
<p>As the CDROM has not gone to replication yet, this updated
floppy image will be appearing on the CDROM.
<p>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!
<p>Gary
<p></p><a href="../index.html">Release Home</a>
&footer;
</body>
</html>

View file

@ -0,0 +1,764 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$Date: 1999-02-08 19:26:11 $">
<!ENTITY title "FreeBSD 2.0.5 ALPHA Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $Id: notes.sgml,v 1.1.1.1 1999-02-08 19:26:11 wosch Exp $ -->
<html>
&header;
<pre>
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
<a href="http://www.freebsd.org/cgi/man.cgi?scsi(4)">scsi(4)</a>>
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 &amp; 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 &amp; 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) &amp; 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 &amp; 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 &amp; 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 &gt;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 &gt;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 &lt;ats@FreeBSD.org&gt;
Andrey A. Chernov &lt;ache@FreeBSD.org&gt;
Bruce Evans &lt;bde@FreeBSD.org&gt;
David Greenman &lt;davidg@FreeBSD.org&gt;
Garrett A. Wollman &lt;wollman@FreeBSD.org&gt;
Gary Palmer &lt;gpalmer@FreeBSD.org&gt;
Geoff Rehmet &lt;csgr@FreeBSD.org&gt;
Jack Vogel &lt;jackv@FreeBSD.org&gt;
John Dyson &lt;dyson@FreeBSD.org&gt;
Jordan K. Hubbard &lt;jkh@FreeBSD.org&gt;
Justin Gibbs &lt;gibbs@FreeBSD.org&gt;
Paul Richards &lt;paul@FreeBSD.org&gt;
Poul-Henning Kamp &lt;phk@FreeBSD.org&gt;
Rich Murphey &lt;rich@FreeBSD.org&gt;
Rodney W. Grimes &lt;rgrimes@FreeBSD.org&gt;
Satoshi Asami &lt;asami@FreeBSD.org&gt;
Søren Schmidt &lt;sos@FreeBSD.org&gt;
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
</pre>
<p></p><a href="../index.html">Release Home</a>
&footer;
</body>
</html>

4
es/releases/2.0/Makefile Normal file
View file

@ -0,0 +1,4 @@
DOCS= announce.sgml credits.sgml install.sgml notes.sgml
.include "../../web.mk"

View file

@ -0,0 +1,156 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$Date: 1999-02-08 19:26:12 $">
<!ENTITY title "FreeBSD 2.0 Announcement">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<p>
To: announce@freefall.cdrom.com<br>
Subject: 2.0 RELEASE is now available on ftp.freebsd.org!<br>
Date: Tue, 22 Nov 1994 06:35:37 -0800<br>
From: "Jordan K. Hubbard" &lt;jkh@freefall.cdrom.com&gt;
</p>
<p>
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).
<p>
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!
<p>
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!
<p>
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!
<p>
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.
<p>
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! :-).
<p>
An upgrade path from ALPHA-&gt;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!
:-)
<p>
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.
<p>
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.
<p>
Those unable or unwilling to download the boot floppy may also get the
release notes by mail - send mail to &lt;info@FreeBSD.org&gt; 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
<p>
FreeBSD 2.0 RELEASE is or will be available for ftp in the following
locations:
<ul>
<li>Primary ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE
<li>U.S-2 ftp://ftp.dataplex.net/pub/FreeBSD/2.0-RELEASE
<li>U.S-3 ftp://kryten.atinc.com/pub/FreeBSD/2.0-RELEASE
<li>U.S-4 ftp://ref.tfs.com/pub/FreeBSD/2.0-RELEASE
<li>Taiwan ftp://netbsd.csie.nctu.edu.tw/pub/FreeBSD/2.0-RELEASE
<li>Australia ftp://ftp.physics.usyd.edu.au/FreeBSD/2.0-RELEASE
<li>France ftp://ftp.ibp.fr/pub/freeBSD/2.0-RELEASE
<li>Finland ftp://nic.funet.fi:/pub/unix/FreeBSD/2.0-RELEASE
<li>Russia ftp://ftp.kiae.su/FreeBSD/2.0-RELEASE
</ul>
<p>
(Translated for the non-URL literate: FreeBSD is available for anonymous
ftp on ftp.freebsd.org in the pub/FreeBSD/2.0-RELEASE directory)
<p>
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.
<p>
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.
<p>
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.
<p>
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! :-)
<p>
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 :-)]
<p>
Thanks to all, and we sincerely hope you enjoy this release!
<p>
Comments, as always, to hackers@FreeBSD.org.
<p>
Jordan<br>
[on behalf of the FreeBSD Project team]
<p></p><a href="../index.html">Release Home</a>
&footer;
</body>
</html>

View file

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

View file

@ -0,0 +1,494 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$Date: 1999-02-08 19:26:12 $">
<!ENTITY title "FreeBSD 2.0 Installation Guide">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<pre>
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. | |
| +----------------------------------------------------------------------+ |
+--------------------------------------------------------------------------+
| &lt; OK &gt; &lt;Cancel&gt; |
+--------------------------------------------------------------------------+
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&gt;
------------------------------------------------------------------------------
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&gt; 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&gt; 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 (&gt; 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&gt;
------------------------------------------------------------------------------
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&gt; E
And we're prompted for a slice to edit. We type 2:
Edit which Slice&gt; 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&gt; 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)&gt; 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)&gt; 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 (&gt; 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&gt;
------------------------------------------------------------------------------
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'&lt;return&gt;. 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 &lt;Entire FreeBSD slice&gt;
d 0 4108599 4108600 2006 unused &lt;Entire Disk&gt;
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&gt;
------------------------------------------------------------------------------
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 &lt;Entire FreeBSD slice&gt;
d 0 4108599 4108600 2006 unused &lt;Entire Disk&gt;
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&gt; 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&gt; 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 &lt;Entire FreeBSD slice&gt;
d 0 4108599 4108600 2006 unused &lt;Entire Disk&gt;
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&gt; a
When it asks us for the name of the mount point, we type /:
Directory mountpoint&gt; /
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 &lt;Entire FreeBSD slice&gt;
d 0 4108599 4108600 2006 unused &lt;Entire Disk&gt;
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 &lt;Tab&gt; 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.
</pre>
<p></p><a href="../index.html">Release Home</a>
&footer;
</body>
</html>

657
es/releases/2.0/notes.sgml Normal file
View file

@ -0,0 +1,657 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$Date: 1999-02-08 19:26:12 $">
<!ENTITY title "FreeBSD 2.0 Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $Id: notes.sgml,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $ -->
<html>
&header;
<pre>
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 &amp; 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
<a href="http://www.freebsd.org/cgi/man.cgi?getvfsbyname(3)">
getvfsbyname(3)</a>
family of functions has been added to the C library and the
<a href="http://www.freebsd.org/cgi/man.cgi?lsvfs(1)">lsvfs(1)</a>
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.
<a href="http://www.freebsd.org/cgi/man.cgi?access(5)">access(5)</a>
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 &lt; 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 &amp; 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
<a href="http://www.freebsd.org/cgi/man.cgi?sysctl(3)">sysctl(3)</a>
management interface. Current
applications include
<a href="http://www.freebsd.org/cgi/man.cgi?lsdev(8)">lsdev(8)</a>,
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
<a href="http://www.freebsd.org/cgi/man.cgi?sysctl(1)">sysctl(1)</a>
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 &amp; 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 &amp; XOUT loaders, and
most of the svr4 syscall wrappers have been written.
Owner: Soren Schmidt (sos) &amp; 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 &amp; 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 &amp; 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 &gt;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 &gt;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 well well, provided
that they haven't been previously used for something else).
After you've formatted the floppy disks, you'll need to copy the
files onto them. There are 56 total files for the bindist itself,
plus three small files (CKSUMS, do_cksum.sh, and extract.sh) for
the install program to use. ALL of these files must be copies onto
the floppies. Each of the bindist files are named "bindist.??",
where the "??" is replaced by the letter sequence aa through cd.
Copy these files onto the floppies, placing the three small install
files onto the final floppy. The order in which you copy the files
to floppy is not important, but it makes labelling the disks easier
if you go in some sort of alphabetical order.
After you've done this, the floppy disks are ready for the install
program to use.
Later on, after you get the binary distribution installed and everything
is going great, the same instructions will apply for the other
distributions, such as the manpages distribution or the XFree86 distribution.
The number of floppies required will, of course, change for bigger or
smaller distributions.
2. Hard Disk Installation
To prepare for installation from an MS-DOS partition, you should simply
copy the files from the distribution into a directory with the same
name as the distribution. For example, if you are preparing to
install the bindist set, then make a directory on your C: drive named
C:\BINDIST and copy the files there. This will allow the installation
program to find the files automatically.
3. QIC/SCSI Tape Installation.
Installing from tape is probably the easiest method, short of an
on-line install using ftp or installing from a CDROM. The installation
program expects the files to be simply tar'red onto the tape, so after
getting all of the files for distribution you're interested in, simply
tar them onto the tape with something like:
cd &lt;where the *.?? files are&gt;
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
</pre>
<p></p><a href="../index.html">Release Home</a>
&footer;
</body>
</html>

View file

@ -0,0 +1,3 @@
DOCS= announce.sgml notes.sgml
.include "../../web.mk"

View file

@ -0,0 +1,270 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$Date: 1999-02-08 19:26:12 $">
<!ENTITY title "FreeBSD 2.1.5 Announcement">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<p>FreeBSD <a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.5-RELEASE">
2.1.5-RELEASE</a> is now available on ftp.freebsd.org and various
FTP mirror sites throughout the world. It can also be ordered on
<a href="http://www.cdrom.com/titles/freebsd.html">CD</a> from
from <a href="http://www.cdrom.com/">Walnut Creek CDROM</a>.</p>
<p>FreeBSD 2.1.5 represents the culmination of over a year's worth of
work on the <a href="/handbook/stable.html">2.1-STABLE</a> branch of
FreeBSD since it began with FreeBSD 2.0.5. In the 7 months since 2.1
was released, many many bug fixes, updates and careful enhancements
have been made, the results of which you now see here.</p>
<p>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.</p>
<p>For more information on the 2.1.5 release itself, please consult the
<a href="notes.html">Release Notes</a>.
<p>The official sources for FreeBSD are available via anonymous FTP from:
<a href="ftp://ftp.FreeBSD.org/pub/FreeBSD">ftp.freebsd.org</a>.
Or via the WEB at:
<a href="http://www.freebsd.org/releases/index.html">www.freebsd.org</a>.
And on CD-ROM from Walnut Creek CDROM:
<p><pre>
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: <a href="mailto:info@cdrom.com">info@cdrom.com</a>
WWW: <a href="http://www.cdrom.com/">http://www.cdrom.com</a>
</pre>
<p>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:</p>
<h2>Australia</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@au.freebsd.org">hostmaster@au.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.au.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.au.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.au.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.au.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp3.au.FreeBSD.ORG/pub/FreeBSD">ftp://ftp3.au.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp4.au.FreeBSD.ORG/pub/FreeBSD">ftp://ftp4.au.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Brazil</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@br.freebsd.org">hostmaster@br.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.br.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.br.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp3.br.FreeBSD.ORG/pub/FreeBSD">ftp://ftp3.br.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp4.br.FreeBSD.ORG/pub/FreeBSD">ftp://ftp4.br.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp5.br.FreeBSD.ORG/pub/FreeBSD">ftp://ftp5.br.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp6.br.FreeBSD.ORG/pub/FreeBSD">ftp://ftp6.br.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp7.br.FreeBSD.ORG/pub/FreeBSD">ftp://ftp7.br.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Canada</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@ca.freebsd.org">hostmaster@ca.freebsd.org</a>
<ul>
<li><a href="ftp://ftp.ca.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.ca.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Czech Republic</h2>
<ul>
<li><a href="ftp://sunsite.mff.cuni.cz/OS/FreeBSD">ftp://sunsite.mff.cuni.cz/OS/FreeBSD</a><p></p>
Problem Contact: <a href="mailto:jj@sunsite.mff.cuni.cz">jj@sunsite.mff.cuni.cz</a></li>
</ul>
<h2>Estonia</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@ee.freebsd.org">hostmaster@ee.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.ee.freebsd.ORG/pub/FreeBSD">ftp://ftp.ee.freebsd.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Finland</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@fi.freebsd.org">hostmaster@fi.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.fi.freebsd.ORG/pub/FreeBSD">ftp://ftp.fi.freebsd.ORG/pub/FreeBSD</a></li>
</ul>
<h2>France</h2>
<ul>
<li><a href="ftp://ftp.ibp.fr/pub/FreeBSD">ftp://ftp.ibp.fr/pub/FreeBSD</a><p></p>
Problem Contact: <a href="mailto:Remy.Card@ibp.fr">Remy.Card@ibp.fr</a>.</li>
</ul>
<h2>Germany</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@de.freebsd.org">hostmaster@de.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.de.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.de.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.de.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.de.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp3.de.FreeBSD.ORG/pub/FreeBSD">ftp://ftp3.de.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp4.de.FreeBSD.ORG/pub/FreeBSD">ftp://ftp4.de.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp5.de.FreeBSD.ORG/pub/FreeBSD">ftp://ftp5.de.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp6.de.FreeBSD.ORG/pub/FreeBSD">ftp://ftp6.de.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp7.de.FreeBSD.ORG/pub/FreeBSD">ftp://ftp7.de.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Hong Kong</h2>
<ul>
<li><a href="ftp://ftp.hk.super.net/pub/FreeBSD">ftp://ftp.hk.super.net/pub/FreeBSD</a><p></p>
Problem Contact: <a href="mailto:ftp-admin@HK.Super.NET">ftp-admin@HK.Super.NET</a>.</li>
</ul>
<h2>Ireland</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@ie.freebsd.org">hostmaster@ie.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.ie.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.ie.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Israel</h2>
<ul>
<li><a href="ftp://orgchem.weizmann.ac.il/pub/FreeBSD">ftp://orgchem.weizmann.ac.il/pub/FreeBSD</a><p></p>
Problem Contact: <a href="mailto:serg@klara.weizmann.ac.il">serg@klara.weizmann.ac.il</a>.</li>
<li><a href="ftp://xray4.weizmann.ac.il/pub/FreeBSD">ftp://xray4.weizmann.ac.il/pub/FreeBSD</a><p></p>
Problem Contact: <a href="mailto:serg@klara.weizmann.ac.il">serg@klara.weizmann.ac.il</a>.</li>
</ul>
<h2>Japan</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@jp.freebsd.org">hostmaster@jp.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.jp.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.jp.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.jp.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.jp.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp3.jp.FreeBSD.ORG/pub/FreeBSD">ftp://ftp3.jp.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp4.jp.FreeBSD.ORG/pub/FreeBSD">ftp://ftp4.jp.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp5.jp.FreeBSD.ORG/pub/FreeBSD">ftp://ftp5.jp.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp6.jp.FreeBSD.ORG/pub/FreeBSD">ftp://ftp6.jp.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Korea</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@kr.freebsd.org">hostmaster@kr.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.kr.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.kr.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.kr.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.kr.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Netherlands</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@nl.freebsd.org">hostmaster@nl.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.nl.freebsd.ORG/pub/FreeBSD">ftp://ftp.nl.freebsd.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Poland</h2>
<ul>
<li><a href="ftp://SunSITE.icm.edu.pl/pub/FreeBSD">ftp://SunSITE.icm.edu.pl/pub/FreeBSD</a><p></p>
Problem Contact: <a href="mailto:ftp@SunSITE.icm.edu.pl">ftp@SunSITE.icm.edu.pl</a></li>
</ul>
<h2>Portugal</h2>
<ul>
<li><a href="ftp://ftp.ua.pt/pub/misc/FreeBSD">ftp://ftp.ua.pt/pub/misc/FreeBSD</a><p></p>
Problem Contact: <a href="mailto:archie@ua.pt">archie@ua.pt</a></li>
</ul>
<h2>Russia</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@ru.freebsd.org">hostmaster@ru.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.ru.freebsd.org/pub/FreeBSD">ftp://ftp.ru.freebsd.org/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.ru.freebsd.org/pub/FreeBSD">ftp://ftp2.ru.freebsd.org/pub/FreeBSD</a></li>
</ul>
<h2>South Africa</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@za.freebsd.org">hostmaster@za.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.za.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.za.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.za.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.za.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp3.za.FreeBSD.ORG/FreeBSD">ftp://ftp3.za.FreeBSD.ORG/FreeBSD</a></li>
</ul>
<h2>Sweden</h2>
<p>In case of problems, please contact the <a href="mailto:hostmaster@se.freebsd.org">hostmaster@se.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.se.freebsd.ORG/pub/FreeBSD">ftp://ftp.se.freebsd.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Taiwan</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@tw.freebsd.org">hostmaster@tw.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.tw.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.tw.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.tw.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.tw.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp3.tw.FreeBSD.ORG/pub/FreeBSD">ftp://ftp3.tw.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Thailand</h2>
<ul>
<li><a href="ftp://ftp.nectec.or.th/pub/FreeBSD">ftp://ftp.nectec.or.th/pub/FreeBSD</a><p></p>
Problem Contact: <a href="mailto:ftpadmin@ftp.nectec.or.th">ftpadmin@ftp.nectec.or.th</a></li>
</ul>
<h2>USA</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@freebsd.org">hostmaster@freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp3.FreeBSD.ORG/pub/FreeBSD">ftp://ftp3.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp4.FreeBSD.ORG/pub/FreeBSD">ftp://ftp4.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp5.FreeBSD.ORG/pub/FreeBSD">ftp://ftp5.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp6.FreeBSD.ORG/pub/FreeBSD">ftp://ftp6.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>UK</h2>
<p>In case of problems, please contact <a href="mailto:hostmaster@uk.freebsd.org">hostmaster@uk.freebsd.org</a>.
<ul>
<li><a href="ftp://ftp.uk.FreeBSD.ORG/packages/unix/FreeBSD">ftp://ftp.uk.FreeBSD.ORG/packages/unix/FreeBSD</a></li>
<li><a href="ftp://ftp2.uk.FreeBSD.ORG/pub/walnut.creek/FreeBSD">ftp://ftp2.uk.FreeBSD.ORG/pub/walnut.creek/FreeBSD</a></li>
<li><a href="ftp://ftp3.uk.FreeBSD.ORG/pub/BSD/FreeBSD">ftp://ftp3.uk.FreeBSD.ORG/pub/BSD/FreeBSD</a></li>
</ul>
<p>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:
<h2>South Africa</h2>
<ul>
<li><a href="ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD</a></li>
<li><a href="ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD">ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Brazil</h2>
<ul>
<li><a href="ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD">ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD</a></li>
</ul>
<h2>Finland</h2>
<ul>
<li><a href="ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt">ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt</a></li>
</ul>
<p></p><a href="../index.html">Release Home</a>
&footer;
</body>
</html>

View file

@ -0,0 +1,551 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$Date: 1999-02-08 19:26:12 $">
<!ENTITY title "FreeBSD 2.1.5 Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $Id: notes.sgml,v 1.1.1.1 1999-02-08 19:26:12 wosch Exp $ -->
<html>
&header;
<pre>
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
<a href="http://www.freebsd.org/cgi/man.cgi?wormcontrol(1)">
wormcontrol(1)</a>). 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
<a href="http://www.freebsd.org/cgi/man.cgi?ccd(4)">ccd(4)</a>>
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:
&lt;browser&gt; file:/usr/share/doc/handbook/handbook.html
To read the FAQ:
&lt;browser&gt; 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 &amp 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 &amp 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 &lt;asami@FreeBSD.org&gt;
Andrey A. Chernov &lt;ache@FreeBSD.org&gt;
John Dyson &lt;dyson@FreeBSD.org&gt;
Bruce Evans &lt;bde@FreeBSD.org&gt;
Justin Gibbs &lt;gibbs@FreeBSD.org&gt;
David Greenman &lt;davidg@FreeBSD.org&gt;
Jordan K. Hubbard &lt;jkh@FreeBSD.org&gt;
Poul-Henning Kamp &lt;phk@FreeBSD.org&gt;
Rich Murphey &lt;rich@FreeBSD.org&gt;
Gary Palmer &lt;gpalmer@FreeBSD.org&gt;
Søren Schmidt &lt;sos@FreeBSD.org&gt;
Peter Wemm &lt;peter@FreeBSD.org&gt;
Garrett A. Wollman &lt;wollman@FreeBSD.org&gt;
Jörg Wunsch &lt;joerg@FreeBSD.org&gt;
The FreeBSD Development Team, excluding core team members
(in alphabetical order by last name):
Ugen J.S. Antsilevich &lt;ugen@FreeBSD.org&gt;
Torsten Blum &lt;torstenb@FreeBSD.org&gt;
Gary Clark II &lt;gclarkii@FreeBSD.org&gt;
Adam David &lt;adam@FreeBSD.org&gt;
Peter Dufault &lt;dufault@FreeBSD.org&gt;
Frank Durda IV &lt;uhclem@FreeBSD.org&gt;
Julian Elischer &lt;julian@FreeBSD.org&gt;
Sean Eric Fagan &lt;sef@FreeBSD.org&gt;
Stefan Esser &lt;se@FreeBSD.org&gt;
Bill Fenner &lt;fenner@FreeBSD.org&gt;
John Fieber &lt;jfieber@FreeBSD.org&gt;
Marc G. Fournier &lt;scrappy@FreeBSD.org&gt;
Lars Fredriksen &lt;lars@freeBSD.org&gt;
Thomas Gellekum &lt;tg@FreeBSD.org&gt;
Thomas Graichen &lt;graichen@FreeBSD.org&gt;
Rod Grimes &lt;rgrimes@FreeBSD.org&gt;
John Hay &lt;jhay@FreeBSD.org&gt;
Eric L. Hernes &lt;erich@FreeBSD.org&gt;
Jeffrey Hsu &lt;hsu@FreeBSD.org&gt;
Gary Jennejohn &lt;gj@FreeBSD.org&gt;
Andreas Klemm &lt;andreas@FreeBSD.org&gt;
L Jonas Olsson &lt;ljo@FreeBSD.org&gt;
Scott Mace &lt;smace@FreeBSD.org&gt;
Atsushi Murai &lt;amurai@FreeBSD.org&gt;
Mark Murray &lt;markm@FreeBSD.org&gt;
Alex Nash &lt;alex@FreeBSD.org&gt;
Sujal Patel &lt;smpatel@FreeBSD.org&gt;
Bill Paul &lt;wpaul@FreeBSD.org&gt;
Joshua Peck Macdonald &lt;jmacd@FreeBSD.org&gt;
John Polstra &lt;jdp@FreeBSD.org&gt;
Mike Pritchard &lt;mpp@FreeBSD.org&gt;
Doug Rabson &lt;dfr@FreeBSD.org&gt;
James Raynard &lt;jraynard@FreeBSD.org&gt;
Geoff Rehmet &lt;csgr@FreeBSD.org&gt;
Martin Renters &lt;martin@FreeBSD.org&gt;
Paul Richards &lt;paul@FreeBSD.org&gt;
Ollivier Robert &lt;roberto@FreeBSD.org&gt;
Dima Ruban &lt;dima@FreeBSD.org&gt;
Wolfram Schneider &lt;wosch@FreeBSD.org&gt;
Andreas Schulz &lt;ats@FreeBSD.org&gt;
Karl Strickland &lt;karl@FreeBSD.org&gt;
Paul Traina &lt;pst@FreeBSD.org&gt;
Guido van Rooij &lt;guido@FreeBSD.org&gt;
Steven Wallace &lt;swallace@FreeBSD.org&gt;
Nate Williams &lt;nate@FreeBSD.org&gt;
Jean-Marc Zucconi &lt;jmz@FreeBSD.org&gt;
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
</pre>
<p></p><a href="../index.html">Release Home</a>
&footer;
</body>
</html>

View file

@ -0,0 +1,3 @@
DOCS= announce.sgml notes.sgml security.sgml
.include "../../web.mk"

View file

@ -0,0 +1,47 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$Date: 1999-02-08 19:26:12 $">
<!ENTITY title "FreeBSD 2.1.6 Announcement">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<p>Please read an <A HREF="security.html">important security
announcement</A> regarding FreeBSD 2.1.6</p>
<p>FreeBSD 2.1.6 is now available in:</p>
<blockquote>
<![ IGNORE [
<a href="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.6-RELEASE">ftp://ftp.freebsd.org/pub/FreeBSD/2.1.6-RELEASE</a>
]]>
<a href="security.html">ftp://ftp.freebsd.org/pub/FreeBSD/2.1.6-RELEASE</a>
</blockquote>
<p>And shortly from its various mirror sites, a list of which may be
obtained from: <a href="&base/handbook/mirrors.html">http://www.freebsd.org/handbook/mirrors.html</a></p>
<p>This release will also be available on CDROM from <a
href="http://www.cdrom.com/">Walnut Creek CDROM</a>, hopefully
shipping within the next 4-6 weeks.</p>
<p>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.</p>
<p>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.</p>
<p></p><a href="../index.html">Release Home</a>
&footer;
</body>
</html>

Some files were not shown because too many files have changed in this diff Show more