diff --git a/es/Makefile b/es/Makefile index af7a231dc9..e69684325a 100644 --- a/es/Makefile +++ b/es/Makefile @@ -1,73 +1,77 @@ -# $FreeBSD: www/es/Makefile,v 1.17 2004/09/20 18:10:24 jesusr Exp $ +# $FreeBSD: www/es/Makefile,v 1.18 2005/03/03 23:51:36 jcamou Exp $ # $FreeBSDes: www/es/Makefile,v 1.3 2004/09/07 21:43:32 jcamou Exp $ .if exists(Makefile.conf) .include "Makefile.conf" .endif .if exists(../Makefile.inc) .include "../Makefile.inc" .endif # These are turned into validated, normalized HTML files. -DOCS= applications.sgml +DOCS= about.sgml +DOCS+= applications.sgml DOCS+= auditors.sgml DOCS+= availability.sgml DOCS+= docs.sgml DOCS+= features.sgml DOCS+= index.sgml DOCS+= internet.sgml DOCS+= mailto.sgml DOCS+= publish.sgml DOCS+= send-pr.sgml DOCS+= support.sgml DOCS+= where.sgml DOCS+= y2kbug.sgml CLEANFILES+=atoz.sgml site.sgml # Subdirectories # SGML SUBDIR= security #SUBDIR+= commercial SUBDIR+= docproj SUBDIR+= news SUBDIR+= alpha SUBDIR+= internal SUBDIR+= copyright SUBDIR+= search #SUBDIR+= gallery SUBDIR+= projects SUBDIR+= releases #SUBDIR+= doc-es SUBDIR+= gnome .if !defined(WEB_ONLY) || empty(WEB_ONLY) SUBDIR+= ports SUBDIR+= doc .endif WEBDIR?= data/es # index.html is special, and generated from index.xsl and news/news.xml DATA+= index.html CLEANFILES+= index.html .include "${WEB_PREFIX}/share/mk/web.site.mk" index.html: index.xsl ${XML_INCLUDES} \ ${XML_NEWS_INCLUDES_MASTER} ${XML_NEWS_NEWS_MASTER} ${XML_NEWS_PRESS_MASTER} \ + ${XML_EVENTS_EVENTS_MASTER} ${XML_EVENTS_CURDATE} \ ${XML_MIRRORS} ${XML_TRANSTABLE} ${XML_ADVISORIES} ${XML_NAVIGATION} ${XML_NOTICES} ${XSLTPROC} ${XSLTPROCOPTS} \ -o $@ \ --param mirrors.xml "'${XML_MIRRORS}'" \ --param advisories.xml "'${XML_ADVISORIES}'" \ --param notices.xml "'${XML_NOTICES}'" \ - --param news.press.xml "'${XML_NEWS_PRESS_MASTER}'" \ - --param news.project.xml "'${XML_NEWS_NEWS_MASTER}'" \ + --param news.press.xml-master "'${XML_NEWS_PRESS_MASTER}'" \ + --param news.project.xml-master "'${XML_NEWS_NEWS_MASTER}'" \ + --param events.xml-master "'${XML_EVENTS_EVENTS_MASTER}'" \ + --param curdate.xml "'${XML_EVENTS_CURDATE}'" \ --param transtable.xml "'${XML_TRANSTABLE}'" \ --param navigation.xml "'${XML_NAVIGATION}'" \ - ${.CURDIR}/index.xsl ${XML_NEWS_NEWS_MASTER} + ${.CURDIR}/index.xsl ${XML_NEWS_NEWS_MASTER} ${XML_EVENTS_EVENTS_MASTER} ${XML_EVENTS_CURDATE} .if !defined(NO_TIDY) -${TIDY} ${TIDYOPTS} ${.TARGET} .endif diff --git a/es/alpha/alpha.sgml b/es/alpha/alpha.sgml index 38facdc254..edc2747d8c 100644 --- a/es/alpha/alpha.sgml +++ b/es/alpha/alpha.sgml @@ -1,39 +1,40 @@ - - + + %navincludes; %includes; ]> - - + + &header;

Esta página contiene información sobre los trabajos de portar FreeBSD a sistemas Alpha.

Links específicos FreeBSD/Alpha

Otros Links de interés

Hardware

Projectos

&footer; diff --git a/es/applications.sgml b/es/applications.sgml index 35714270de..7945436a1e 100644 --- a/es/applications.sgml +++ b/es/applications.sgml @@ -1,96 +1,87 @@ - + + %navincludes; %includes; ]> - + &header; -

Experimenta las posibilidades con FreeBSD

+

Experimenta las posibilidades con FreeBSD

-

FreeBSD puede manejar cualquier tarea que puedas esperar de una estación de trabajo UNIX, incluyendo algunas de las que no esperarías:

-
-
FreeBSD -es un verdadero sistema abierto con todo el código fuente. +

FreeBSD +es un verdadero sistema abierto con todo el código fuente.

-

No hay duda que los llamados sistemas abiertos son el requerimiento -para las aplicaciones informáticas de hoy en día. Pero +para las aplicaciones informáticas de hoy en día. Pero ningún solución comercial es más abierta que una que -incluya el código fuente de todo el sistema, incluyendo el kernel +incluya el código fuente de todo el sistema, incluyendo el kernel además de todos los daemons del sistema, programas y utilidades. Puedes -modificar cualquier parte de FreeBSD para acomodarlo a tus necesidades +modificar cualquier parte de FreeBSD para acomodarlo a tus necesidades personales, de organización o corporativas.

Con su generosa política de licencias, puedes usar FreeBSD como base para culquier tipo de aplicación tanto comercial como libre.

-
-
FreeBSD ejecuta -miles de aplicaciones. +

FreeBSD ejecuta +miles de aplicaciones.

-

Por que FreeBSD está basado en 4.4BSD, una versión estándar de UNIX en la industria, es fácil compilar y ejecutar programas. -FreeBSD también incluye una extensa +FreeBSD también incluye una extensa colección de packages y colección de ports que ofrecen software precompilado y fácil de instalar. Existe también un grán número de aplicaciones comerciales escritas para FreeBSD

Aquí tienes algunos ejemplos de los entornos en los que FreeBSD es usado:

-
-
Un -sistema operativo que colmará todas tus necesidades. +

Un +sistema operativo que colmará todas tus necesidades.

-

Aunque FreeBSD es un software libre, es un software soportado por usuarios. Cualquier pregunta que tengas puede ser enviada a cientos de desarrolladores de FreeBSD y usuarios a la lista de distribución freebsd-questions@FreeBSD.ORG.

FreeBSD tiene un completo grupo a nivel mundial de programadores y desarrolladores que se encargan de fijar los posibles bugs, añadir nuevas características y documentar el sistema. Soporte de nuevos dispositivos y opciones especiales se incluyen en el proceso de desarrollo constante, manteniendo una atención especial a los problemas que afectan a la estabilidad del sistema.

-
-

Lo que dicen los expertos. . .

+

Lo que dicen los expertos. . .

-

``FreeBSD handles [our] heavy load quite well and it is nothing short of amazing. Salutations to the FreeBSD team.''

---Mark Hittinger, administrator of WinNet Communications, Inc.

-
&footer; diff --git a/es/auditors.sgml b/es/auditors.sgml index 804308c0f0..b8a5ce18cf 100644 --- a/es/auditors.sgml +++ b/es/auditors.sgml @@ -1,413 +1,414 @@ - + + %navincludes; %includes; ]> - + &header;

Información general

-Ultima actualización: $FreeBSD$ +Ultima actualización: $FreeBSD: www/es/auditors.sgml,v 1.4 1999/09/06 07:02:59 peter Exp $

Introducción

A causa de nuestro reciente problema de seguridad, ha sido obvio que nada mejor que una rigurosa revisión de seguridad en todo el código fuente del sistema.

La ingente cantidad de có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ún esfuerzo verdaderamente importante de revisión -de todo el código del sistema centrado en la seguridad. Esta +de todo el código del sistema centrado en la seguridad. Esta situació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á hostil para sistemas mal protegidos. Una buena seguridad es algo a realizar y compartir entre el administrador local y los desarrolladores del sistema, y éstos tienen *ahora* que hacer su parte.

El primer paso del core team respecto al tema de la seguridad fue crear un puesto de responsable de seguridad, Guido van Rooij, 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ás importantes relacionadas con la seguridad. Además -él nos mantendrá más informados sobre los temas de -seguridad para que no nos vuelva a coger desprevenidos como ocurrió +él nos mantendrá más informados sobre los temas de +seguridad para que no nos vuelva a coger desprevenidos como ocurrió alguna vez en el pasado.

-

Nuestro segundo paso es esta auditoría, un intento de ir +

Nuestro segundo paso es esta auditoría, un intento de ir metodicamente a través de cada una de las líneas de código de FreeBSD prestando especial atención a buffer overflows obvios (sprintf()/strcpy() vs snprintf()/strncpy() ), problemas de seguridad menos obvios, secciones de insuficiente código defensivo, etc.

Usando la base de datos de módulos como guí, distribuiremos los fuentes en partes má manejables, manteniendo un ídice en un lugar prominente para que la gente pueda ver los mó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ódigo en -busca de posibles agujeros o bugs. Una vez existe una razonable cantidad de -código acumulado, y suponiendo que no se haya encontrado ningún +la cual debe ser compartida con otro auditor, es revisar el código en +busca de posibles agujeros o bugs. Una vez existe una razonable cantidad de +código acumulado, y suponiendo que no se haya encontrado ningún problema, éstos son enviados a uno o má "revisores" que se responsabilizan de volver a revisar el código una vez más.

Requerimientos:

-

Para ser auditor, deberís tener privilegios de "commit" en +

Para ser auditor, deberís tener privilegios de "commit" en freefall.freebsd.org o un acuerdo con otro auditor/revisor que los -tenga. También deberías usar, o tener acceso inmediato a +tenga. También deberías usar, o tener acceso inmediato a FreeBSD-current ya que todas las revisiones y cambios se realizarás sobre esta rama en primer lugar.

Qué buscar y que reglas generales a seguir son suficientemente -complejas como para explicarlas en La -Guía de Seguridad de FreeBSD. Por favor, leela ahora si no lo +complejas como para explicarlas en La +Guía de Seguridad de FreeBSD. Por favor, leela ahora si no lo habías hecho todavía. Otros excelentes documentos son Secure Programming Checklist y el Unix Security Checklist, ambos disponibles en AUSCERT.

Estructura:

Aquí está la estructura existente en estos momentos. Es *muy* esquemática actualmente, ya que acabamos de comenzar, y ha medida que la gente nos comunique los módulos que van a revisar o auditar iremos actualizandolo.

Nada en la base de datos de módulos representa un objetivo potencial de auditoría - desde los mas pequeños como "cat" hasta los -más grandes como "lib", lo más importante es que la gente +más grandes como "lib", lo más importante es que la gente selecciones módulos que pueda manejar y asumir. Si coges 15 cosas y -solo trabajas con 5, no estarás haciendo un favor a nadie ya que el +solo trabajas con 5, no estarás haciendo un favor a nadie ya que el resto de auditores que las 10 restantes están siendo trabajadas!.

Para escoger algo, por favor, un mai a jmb@FreeBSD.org. -

+

MóduloAuditor(s)Revisor(s) Status
bin ac ee* gvr* jh ka mu vk imp* jmb* md* gvr* Open
contrib cg gvr* Open
eBones mrvm* gvr* Open
games ab ee* xaa gvr* Open
init gl gvr* Open
lib ak bjn pst* dg* imp* jkh* gvr* Open
libc ee* mu gvr* Open
libexec crh ee* imp* mr witr gvr* Open
lkm dob* gvr* Open
sbin ee* imp* or* tao jmb* md* gvr* Open
secure dc mrvm* gvr* Open
telnetd ac dn imp* gvr* Open
usr.bin bob ee* jha jm ky* rb rd rjk vk md* gvr* Open
usr.sbin ee* ejc gl imp* jm marc rd md* gvr* Open

Mención de Auditores/Revisores

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 auditors@FreeBSD.org. Si solo quieres localizar a los auditores y revisores de una categoría específica, digamos usr.sbin -por ejemplo, envía un mail a - +por ejemplo, envía un mail a + audit-usr.sbin@FreeBSD.org.

- +
Key
Key Auditor/Revisor Nombre y Email
ab Aaron Bornstein aaronb@j51.com
ac Adrian Chadd adrian@psinet.net.au
ak Adam Kubicki apk@itl.waw.pl
am Albert Mietus gam@gamp.hacom.nl
avk Alexander V. Kalganov top@sonic.cris.net
bb Bob Bishop rb@gid.co.uk
bjn Brent J. Nordquist nordquist@platinum.com
bob Bob Willcox bob@luke.pmr.com
btm Brian T. Michely brianm@cmhcsys.com
cg Coranth Gryphon gryphon@healer.com
cl Chris Lambertus cmlambertus@ucdavis.edu
crh Charles Henrich henrich@crh.cl.msu.edu
dc Dan Cross tenser@spitfire.ecsel.psu.edu
dg* David Greenman davidg@FreeBSD.org
din Dinesh Nair dinesh@alphaque.com
dn David Nugent davidn@labs.usn.blaze.net.au
dob* David E. O'Brien obrien@NUXI.com
dz Danny J. Zerkel dzerkel@phofarm.com
ee* Eivind Eklund eivind@FreeBSD.org
eh Elijah Hempstone avatar@gandalf.bss.sol.net
ehu Ernest Hua hua@chromatic.com
ejc Eric J. Chet ejc@gargoyle.bazzle.com
gl Giles Lean giles@nemeton.com.au
gvr* Guido van Rooij guido@FreeBSD.org
gw Graham Wheeler gram@oms.co.za
imp* Warner Losh imp@FreeBSD.org
jb Jim Bresler jfb11@inlink.com
jh Jake Hamby jehamby@lightside.com
jha John H. Aughey jha@cs.purdue.edu
jk Jerry Kendall Jerry@kcis.com
jkh* Jordan K. Hubbard jkh@FreeBSD.org
jm Josef Moellers mollers.pad@sni.de
jmb* Jonathan M. Bresler jmb@FreeBSD.org
joe* Joe Greco jgreco@solaria.sol.net
ka Kalganov Alexander top@bird.cris.net
ki Kenneth Ingham ingham@i-pi.com
ky* Kazutaka YOKOTA yokota@zodiac.mech.utsunomiya-u.ac.jp
marc Marc Slemko marcs@znep.com
md* Matt Dillon dillon@best.net
mr Mike Romaniw msr@cuc.com
mrvm* Mark Murray mark@grondar.za
mu Mudge mudge@l0pht.com
or* Ollivier Robert roberto@keltia.freenix.fr
pb Peter Blake ppb@baloo.tcp.co.uk
peter* Peter Wemm peter@FreeBSD.org
phk* Poul-Henning Kamp phk@FreeBSD.org
pst* Paul Traina pst@FreeBSD.org
rb Reinier Bezuidenhout rbezuide@oskar.nanoteq.co.za
rd Rajiv Dighe rajivd@sprynet.com
rel Roger Espel Llima espel@llaic.univ-bpclermont.fr
rjk Richard J Kuhns rjk@grauel.com
rm Robin Melville robmel@nadt.org.uk
rs Robert Sexton robert@kudra.com
sc Sergei Chechetkin csl@whale.sunbay.crimea.ua
tao Brian Tao taob@risc.org
tdr Thomas David Rivers ponds!rivers@dg-rtp.dg.com
vk Vadim Kolontsov vadim@tversu.ac.ru
witr Robert Withrow witr@rwwa.com
xaa Mark Huizer xaa@stack.nl

* = Tiene privilegios de "commit".

&footer; diff --git a/es/availability.sgml b/es/availability.sgml index df95779de1..d178c4e970 100644 --- a/es/availability.sgml +++ b/es/availability.sgml @@ -1,83 +1,84 @@ - + + %navincludes; %includes; ]> - + &header;

Disponibilidad de FreeBSD

-

FreeBSD es libre y está disponible para bajar a través +

FreeBSD es libre y está disponible para bajar a través de Internet o en CD-ROM por un precio mínimo.


Requerimientos de Hardware.

FreeBSD funciona en una gran variedad de hardware, tanto PC como Alpha. - Por favor, consulta las + Por favor, consulta las configuraciones soportadas del Manual de FreeBSD para más información.


Dónde obtenerlo.
-

Puedes obtener FreeBSD vía FTP anónimo en +

Puedes obtener FreeBSD vía FTP anónimo en ftp://ftp.freebsd.org/pub/FreeBSD. -También puedes obtenerlo de cualquiera de los +También puedes obtenerlo de cualquiera de los mirrors existentes en todo el mundo.

-

Si tienes un lector de CD-ROM, puedes obtener FreeBSD en CD-ROM por un +

Si tienes un lector de CD-ROM, puedes obtener FreeBSD en CD-ROM por un muy módico precio en Walnut Creek CDROM:

Walnut Creek CDROM
4041 Pike Lane, Suite F
Concord, CA 94520
USA
Phone: +1 925 674-0783
Phone: +1 800 786-9907
Fax: +1 925 674-0821
Email: info@cdrom.com

Además de FreeBSD, la versión en CD-ROM incluye cientos de aplicaciones listas para funcionar.


Sobre el Proyecto FreeBSD.

FreeBSD es desarrollado y soportado por un grupo mundial de programadores. Jordan Hubbard, uno de los fundadores -del proyecto a escrito una breve -historia del proyecto FreeBSD. Información sobre -quién es responsable de cada -cosa también está disponible. Si eres curioso, mira algunas -fotos de los +del proyecto a escrito una breve +historia del proyecto FreeBSD. Información sobre +quién es responsable de cada +cosa también está disponible. Si eres curioso, mira algunas +fotos de los componentes del equipo. Una lista más completa de los participantes -está disponible en la sección -Participantes del +está disponible en la sección +Participantes del Handbook de FreeBSD. FreeBSD es un proyecto abierto que aprecia la ayuda de personas que tengan tiempo o ideas que ofrecer.

Esta sección fue creada por Sean Kelly.

Dentro de tu PC hay un demonio esperando a ser liberado. Líberalo con FreeBSD.

&footer; diff --git a/es/copyright/copyright.sgml b/es/copyright/copyright.sgml index 89c5bc8475..412f3600ef 100644 --- a/es/copyright/copyright.sgml +++ b/es/copyright/copyright.sgml @@ -1,24 +1,25 @@ - - + + %navincludes; %includes; ]> - + &header;

El Copyright FreeBSD

El Copyright BSD

El demonio BSD

Restricciones de redistribución de los ports de FreeBSD

LICENCIA PUBLICA GENERAL DE GNU

LICENCIA PUBLICA GENERAL DE LIBRERIA GNU

&footer; diff --git a/es/copyright/daemon.sgml b/es/copyright/daemon.sgml index d4e5e704fd..4792233b68 100644 --- a/es/copyright/daemon.sgml +++ b/es/copyright/daemon.sgml @@ -1,75 +1,76 @@ - - + + %navincludes; %includes; ]> - + &header;

El pequeño compañero rojo que alegra algunas de las pá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ón humana. En un + atendiendo a varias tareas sin intervención humana. En un sentido general, daemon es la forma antigua de la palabra "demon". En - el Manual de Administración de Sistemas Unix, Evi + el Manual de Administración de Sistemas Unix, Evi Nemeth dice lo siguiente sobre los "daemons":

"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)
-

Las primeras (y más populares) versiones del demonio BSD +

Las primeras (y más populares) versiones del demonio BSD fueron creadas por John Lasseter. Las versiones más recientes específicas de FreeBSD han sido realizadas por - Tatsumi Hosokawa, pero la inspiración básica, + Tatsumi Hosokawa, pero la inspiración básica, definitivamente pertenece a John. El propietario del copyright y creador de la imágen del demonio es Marshall Kirk McKusick. Una breve historia gráfica también está disponible. Existe una galería de publicaciones relacionadas con FreeBSD que usan diferentes versiones del demonio.

Están disponibles demonios de peluche de diferentes - tamaños en + tamaños en FreeBSD Mall - . En Europa, se pueden + beanie daemon. En Europa, se pueden obtener demonios en Liebscher & Partner.

ScotGold produce chapas de 1 pulgada con el demonio de BSD.

BSD Daemon Copyright 1988 by Marshall Kirk McKusick. All Rights Reserved.

El permiso para usar el demonio debe ser obtenido de:

Marshall Kirk McKusick
1614 Oxford St
Berkeley, CA 94709-1608
USA

o vía email a mckusick@mckusick.com.

Copyright Home &footer; diff --git a/es/copyright/freebsd-license.sgml b/es/copyright/freebsd-license.sgml index 7046b46d26..55844c4077 100644 --- a/es/copyright/freebsd-license.sgml +++ b/es/copyright/freebsd-license.sgml @@ -1,55 +1,56 @@ - - + + %navincludes; %includes; ]> - + &header;

Copyright 1994-1998 FreeBSD, Inc. All rights reserved.

La redistribución y uso en forma de código fuente o binario, con o sín modicaciones, están permitidas siempre y cuando sean conocidas las siguientes condiciones:

  1. La redistribución del código fuente debe contener - el texto arriba indicado, esta lista de condiciones y el + el texto arriba indicado, esta lista de condiciones y el siguiente texto. -
  2. La redistribución en formato binario debe contener el +
  3. La redistribución en formato binario debe contener el texto arriba indicado. esta lista de codiciones y el siguiente texto en la documentación y/o en otros materiales que acompañen a la distribución.

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.

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.

Copyright Home &footer; diff --git a/es/copyright/license.sgml b/es/copyright/license.sgml index c3c90b3623..960dad2f55 100644 --- a/es/copyright/license.sgml +++ b/es/copyright/license.sgml @@ -1,103 +1,104 @@ - - + + %navincludes; %includes; ]> - + &header;

All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by The Regents of the University of California.

Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. 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 product includes software developed by the University of California, Berkeley and its contributors.
  4. 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.

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.

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.

In the following statement, the phrase ``this text'' refers to portions of the system documentation.

Portions of this text are reprinted and reproduced in electronic form in the 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.

In the following statement, the phrase ``This material'' refers to portions of the system documentation.

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.

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.

Copyright Home &footer; diff --git a/es/docproj/current.sgml b/es/docproj/current.sgml index 14a8a4029e..7f601e7a52 100644 --- a/es/docproj/current.sgml +++ b/es/docproj/current.sgml @@ -1,271 +1,272 @@ - - + + %navincludes; %includes; ]> - + &header; - +

Aquí están los proyectos en curso (o siendo activamente - contemplados en la lista FreeBSD-doc). También están - incluidos algunos que realmente no se ha hablado de ellos, pero + contemplados en la lista FreeBSD-doc). También están + incluidos algunos que realmente no se ha hablado de ellos, pero serían una buena idea. Cada proyecto lista la persona de contacto para ese proyecto (si sé quién es).

-

Si piensas que puedes contribuir en cualquier de ellos, por favor, - no dudes en hacerlo. Deberís hablar con la persona responsable, +

Si piensas que puedes contribuir en cualquier de ellos, por favor, + no dudes en hacerlo. Deberís hablar con la persona responsable, quién te pondrá al día de la marcha del proyecto.

Informes de problemas abiertos sobre la documentación

Los informes de problemas abiertos actualmente se siguen mediante la base de datos GNATS. Puedes Ver los informes de documentación actuales.

FreeBSD para usuarios de Linux

Responsable: Annelise Anderson <andrsn@andrsn.stanford.edu>

-

Sinópsis: Los usuarios de FreeBSD provenientes de Linux +

Sinópsis: Los usuarios de FreeBSD provenientes de Linux pueden tener confusiones por algunas de las diferencias entre los dos sistemas (diferente shell por defecto, cómo funciona la configuración de arranque, y cosas así). Annelise está coordinando el desarrollo de un tutorial/FAQ que reflejará estos puntos.

-

La lista de preguntas actuales está en +

La lista de preguntas actuales está en http://FreeBSD.stanford.edu/FreeBSD/linux.html.

Actualizar los ficheros FOO.TXT

Responsable: Doug <studded@dal.net>

Sinópsis: 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án revisando los contenidos - para asegurar que sean cuidados, consistentes y fáciles de + para asegurar que sean cuidados, consistentes y fáciles de entender.

- +

Escribir una sección en las FAQ y/o Handbook

Responsable: Ninguno

-

Sinópsis: Algunas partes de las FAQ y del Handbook +

Sinópsis: Algunas partes de las FAQ y del Handbook están incompletas, esperando tu aportación. Si has usado alguna parte de la documentación ya existente y encuentras que es complicada o insuficiente, por favor, coméntalo, ofreciendo alguna posible solución.

- +

Alternativamente, si has hecho algo que no existe en la FAQ y/o handbook, por favor, considera escribir una nueva sección.

- +

Reescribir el Handbook :-)

Responsable:Nik Clayton <nik@FreeBSD. org>

Sinópsis: El Handbook ha ido creciendo orgánicamente durante los últimos años. Esto significa que algunas secciones no están organizadas como deberían y otras necesitan ser reescritas.

Actualmente, se ha diseñado un plán para realizar esta - tarea y está esperando a que se finalicen otros proyectos de + tarea y está esperando a que se finalicen otros proyectos de mayor prioridad. Contacta con Nik (preferiblemente a través de la lista de distribución <doc@FreeBSD.org>) para obtener + href="mailto:doc@FreeBSD.org">doc@FreeBSD.org>) para obtener información más detallada.

- - + +

Escribir algunas informaciones nuevas

La arquitectura VM de FreeBSD

Responsable: John Dyson < dyson@iquest.net>

-

Sinópsis: FreeBSD 2.x tiene una arquitectura de +

Sinópsis: FreeBSD 2.x tiene una arquitectura de memoria virtual totalmente renovada. Desafortunadamente no existe ningún tipo de documentación excepto el código fuente y algunos emails antiguos de John Dyson. Mira en FreeBSD VM System Overview para una primera aproximación.

El nuevo SCSI para FreeBSD (CAM)

Responsable: - <doc@FreeBSD.org>, + <doc@FreeBSD.org>, <scsi@FreeBSD.org> -

Sinópsis: Mira en +

Sinópsis: Mira en The Design and Implementation of the FreeBSD SCSI Subsystem para una primera aproximación.

Escribir nuevos Tutoriales

-

Responsable: +

Responsable: <doc@FreeBSD.org> -

Sinópsis:

+

Sinópsis:

- +

Escribir páginas man para el kernel

-

Responsable: +

Responsable: <doc@FreeBSD.org> -

Sinópsis: Documentar funciones de Kernel, +

Sinópsis: Documentar funciones de Kernel, sección 9

CGI Scripts

-

Responsable: +

Responsable: <doc@FreeBSD.org, Wolfram Schneider < wosch@FreeBSD.org>

-

Sinópsis:

+

Sinópsis:

Aquí hay algunos apuntes para el módulo de ports

Una línea en /usr/ports/INDEX es como

    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
         

El formato es

    distribution-name|port-path|installation-prefix|comment| \
        description-file|maintainer|categories|build deps|run deps
        

La anterior línea INDEX pasada por un objeto anónimo hash

-$port = {	
+$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', 
+	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'] 
+				'xpm-3.4k']
 };
       

Ahora necesitamos algunas funciones

-

Finalmente

+

Finalmente

Modificar los cgi's url.cgi, ports.cgi, pds.cgi y el script portindex para usar este módulo.

Contacta con Nik Clayton <nik@FreeBSD.ORG> para una primera - muestra del módulo de ports mira + muestra del módulo de ports mira aquí.

- +

Web scripts multilenguaje

Responsable: <doc@FreeBSD.org>

Sinopsis:

- Nuestras páginas web están escritas en inglés - (americano). Los Proyectos de + Nuestras páginas web están escritas en inglés + (americano). Los Proyectos de Traducción de FreeBSD traducen el web, Handbook y FAQ a otros lenguajes.

- Debemos traducir los cgi's del web y las herramientas de + Debemos traducir los cgi's del web y las herramientas de creación del web. Los scripts deberín soportar diferentes lenguajes, no solo uno. Muchos scripts están escritos en Perl.

- +

Traducciones de la documentación de FreeBSD

-

Responsable: +

Responsable: <doc@FreeBSD.org> Traducir la documentación de FreeBSD (Web, FAQ, Handbook, páginas man) a otros idiomas. Mira en el proyecto de traducciones.

Mejoras en el motor de búsquedas

Responsable: <doc@FreeBSD.org>

-

Cuando realizamos una búsqueda en el web, el resultado que +

Cuando realizamos una búsqueda en el web, el resultado que obtenemos es el nombre del fichero en el que se ha encontrado el resultado, - siendo algo como FAQ34.html.

+ siendo algo como FAQ34.html.

Sería mucho más útil si los resultados incluyesen el texto en cuestión, permitiendo al usuario la relevancia del resultado obtenido.

FreeBSD Documentation Project Home &footer diff --git a/es/docproj/doc-set.sgml b/es/docproj/doc-set.sgml index 4472562ed1..55fa162268 100644 --- a/es/docproj/doc-set.sgml +++ b/es/docproj/doc-set.sgml @@ -1,59 +1,60 @@ - - + + %navincludes; %includes; ]> - + &header; -

La documentación de FreeBSD se distribuye en 4 categorías +

La documentación de FreeBSD se distribuye en 4 categorías básicas

  1. Las páginas man

    El proyecto no está vinculado directamente con éstas - al formar parte del sistema base. La excepción a esto es el + al formar parte del sistema base. La excepción a esto es el equipo Japonés, ya que las están traduciendo.

    Esto no significa que las páginas man no sean importantes, al contrario. Solo decir que están intimamente ligadas a los sistemas específicos de FreeBSD, y muchas veces la persona más indicada para escribirlas, es la persona que ha escrito esa parte de FreeBSD.

  2. La FAQ

    -

    Esta es mantenida por el proyecto. El objetivo es reunir (en +

    Esta es mantenida por el proyecto. El objetivo es reunir (en formato de pregunta y respuesta) las preguntas más - frecuentemente realizadas en las diferentes listas de + frecuentemente realizadas en las diferentes listas de distribución y grupos de news de FreeBSD.

  3. El Handbook

    Este es mantenido por el proyecto. Los temas que necesitan una discsión más profunda son tratado en el Handbook.

    .
  4. Los Tutoriales

    Algunos de estos tutoriales son mantenidos por los "committers" - del proyecto, y otros no. El mantenimiento de estos + del proyecto, y otros no. El mantenimiento de estos documentos depende de los autores de forma individual.

    Algunos tutorials se encuentran en el servidor web de FreeBSD. - Para estos tutoriales el autor envía las modificaciones a + Para estos tutoriales el autor envía las modificaciones a uno de los "committers", y el "committer" realiza el cambio. Otros tutoriales están situados en el espacio de web privado del autor, y el autor puede hacer cambios cuando quiera. Algunas veces esta es una elección deliberada del autor, y otras un accidente histórico.

- +

FreeBSD Documentation Project Home &footer diff --git a/es/docproj/docproj.sgml b/es/docproj/docproj.sgml index b80837a372..257e8df079 100644 --- a/es/docproj/docproj.sgml +++ b/es/docproj/docproj.sgml @@ -1,77 +1,78 @@ - - + + %navincludes; %includes; ]> - + &header;

Introducción

Tener el control de un nuevo y complejo sistema operativo es siempre una tarea complicada, no importa los gráficos que tenga. FreeBSD no es diferente en este aspecto.

-

Aunque existe una grán cantidad de libros sobre Unix BSD (y Unix en +

Aunque existe una grán cantidad de libros sobre Unix BSD (y Unix en general), FreeBSD tiene sus propias características y procedimientos.

-

Además, FreeBSD puede ser la primera aproximación a +

Además, FreeBSD puede ser la primera aproximación a sistemas Unix para muchos de sus usuarios, por lo que la disponibilidad de documentación de alta calidad es muy importante.

El Proyecto de Documentación de FreeBSD existe para ayudar en este campo. Existen dos maneras de trabajar;

  1. Miembros del proyecto de documentación escriben documentos para ser incluidos en la Distribución de Documentación de FreeBSD.

  2. Miembros del proyecto de documentación discuten y trabajan la organización de la Distribución de Documentación de FreeBSD.

- +

Proyectos actuales

- +

Existen en estos momentos diferentes proyectos en progreso como parte del esfuerzo de documentación. Por favor, mira en esta lista por si hay algo en lo que nos puedas ayudar.

- +

Quienes somo, cómo participar

Esta página explica quién forma parte del Proyecto de Documentación y como participar.

La distribución de Documentación de FreeBSD

SGML y el Proyecto de Documentación

El Proyecto intenta usar SGML para la documentación. Esta página indica como se consigue, apuntando al lector algunas fuentes de información sobre SGML.

Enviando Documentación

Enviar documentación es la mejor manera de entrar a formar parte del proyecto, y hacer que FreeBSD sea más sencillo de usar. Esta página explica la mejor manera de enviar la documentación para que esté visible lo antes posible.

Traducciones de la documentación de FreeBSD, páginas Web, Handbook, página man y las FAQ.

&footer diff --git a/es/docproj/sgml.sgml b/es/docproj/sgml.sgml index 14308ee6c8..9c09d2ef6b 100644 --- a/es/docproj/sgml.sgml +++ b/es/docproj/sgml.sgml @@ -1,193 +1,194 @@ - - + + %navincludes; %includes; ]> - + &header; -

El proyecto de Documentación intenta usar SGML como +

El proyecto de Documentación intenta usar SGML como método estándar de representar la documentación.

SGML es el lenguaje Standard Generalised Markup L.

Brevemente (y disculpas para los puristas de SGML que puedan sentirse ofendidos), SGML es un lenguaje para escribir otros lenguajes.

Probablemente ya has usado SGML sin saberlo. HTML, el leguaje en el - que se escriben las páginas web, tiene una descripción + que se escriben las páginas web, tiene una descripción formal. Esa descripción está escrita en SGML. Cuando escribes en HTML no estás escribiendo SGML, pero sí estás usando un lenguaje definido por SGML.

Existen muchos, muchos lenguajes "markup" que está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ón, y el Proyecto de Documentación de FreeBSD lo adoptó.

Otro lenguaje "markup" definido usando SGML es el llamado "DocBook". Este es un lenguaje diseñado específicamente para escribir documentación técnica.

Por ejemplo, así estaría escrito un breve párrafo en HTML (no te preocupes del contenido, solo fíjate en los tags):

The system's passwords are stored in /etc/passwd. To edit
       this file you should use vipw. However, if you just
       want to add a new user you can use adduser.

]]>
- +

El mismo párrafo usando DocBook sería:

The system's passwords are stored in
       /etc/passwd. To edit this file you should use
       vipw. However, if you just want to add a new user
       you can use adduser.
 ]]>
- +

Como puedes ver, DocBook es mucho má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á marcado como que es un "filename", la representación de un nombre de fichero no está descrita.

Hay grande ventajas en esta manera más expresiva de lenguaje:

-

Si estás familiarizado con ellos, es como las galerías +

Si estás familiarizado con ellos, es como las galerías de estilo de Microsoft Word, solo que infinitamente más potente.

Por supuesto, esta potencia tiene un precio;

-

Actualmente, el Proyecto está usando LinuxDoc para el +

Actualmente, el Proyecto está usando LinuxDoc para el Handbook y las FAQ. Esto está cambiando, ya que se está haciendo una migración de la documentación a DocBook.

- +

Qué pasa si no se LinuxDoc/DocBook? Todavía puedo contribuir?

- +

Sí, por supuesto. Cualquier documentación es mejor que no tener nada. Si tienes documentación con la que contribuir y no está en formato LinuxDoc o DocBook, no te preocupes.

-

Envía la documentación +

Envía la documentación de la manera habitual. Alguien del proyecto recogerá los - documentos enviados y los convertirá por tí. Con un + documentos enviados y los convertirá por tí. Con un poco de suerte, te será devuelta ya marcada en DocBook. Así - puedes comparar el documento original con el que has recibido y + puedes comparar el documento original con el que has recibido y aprender a hacerlo tú mismo.

Obviamente, esto retrasa el que la documentación esté online, pero no te preocupes.

Má información sobre SGML y DocBook?

Primero deberís leer el - Documentation Project Primer. Es una extensa - explicación de todo lo que necesitas saber para poder trabajar + Documentation Project Primer. Es una extensa + explicación de todo lo que necesitas saber para poder trabajar con la documentación de FreeBSD.

Es un documento largo, dividido en múltiples ficheros diferentes de pequeño tamaño. También puedes verlo en formato de un sólo fichero.

http://www.oasis-open.org/cover/sgml-xml.html

El web de SGML/XML. Incluye más recursos sobre SGML.

http://www-tei.uic.edu/orgs/tei/sgml/teip3sg/index.html

The "Gentle Introduction to SGML". De recomendada lectura para cualquiera que desee tener conocimientos avanzados de SGML.

- +
http://www.ora.com/davenport/
-

El DTD DocBook es mantenido por OASIS. +

El DTD DocBook es mantenido por OASIS. Estas páginas están pensadas para usuarios que se sienten de manera confortable con SGML y quieren aprender DocBook.

http://fallout.campusview.indiana.edu/~jfieber/docbook/

La página de John Fieber contiene links a otros recursos - de DocBook y documentos de ejemplo. Tambié incluye una + de DocBook y documentos de ejemplo. Tambié incluye una guía de marcas para FreeBSD.

http://www.nothing-going-on.demon.co.uk/FreeBSD/
-

La página de Nik Clayton contiene links a +

La página de Nik Clayton contiene links a documentación escrita y después convertida a HTML. Los ficheros DocBook originales están disponibles, dando una idea muy razonable de como usar los diferentes elementos de DocBook.

- http://wolfram.schneider.org/papers/webbuild.html
+ http://wolfram.schneider.org/papers/webbuild.html

Este documento describe como crear y actualizar las páginas Web de FreeBSD a mano desde el CVS.

- - + +

FreeBSD Documentation Project Home &footer; diff --git a/es/docproj/submitting.sgml b/es/docproj/submitting.sgml index 4af6eeac3f..4fcd757f5f 100644 --- a/es/docproj/submitting.sgml +++ b/es/docproj/submitting.sgml @@ -1,141 +1,142 @@ - - + + %navincludes; %includes; ]> - + &header;

He escrito algunos documentos, como los envío?

Ante todo, gracias por ocupar tu tiempo en hacerlo.

Tendrías que poner los documentos disponibles para ser revisados . Si puedes ponlos en un espacio FTP o Web. Si no tienes espacio propio, envíalos a ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/, y usa send-pr para comunicar a los + href="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/">ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/, y usa send-pr para comunicar a los "committers" que está disponible.

-

A continuación envía un mensaje a la lista de +

A continuación envía un mensaje a la lista de distribución freebsd-doc, con una breve descripción y su localización. Pide opiniones.

- +

También deberías enviar una copia del mensaje a otras listas relacionadas. Por ejemplo, algo relativo al uso de CVSup para mantener actualizado el código fuente, también sería de interés para los subscriptores de las listas FreeBSD-current y FreeBSD-stable.

- -

Una vez la gente haya visto tu documento y hayas podido incorporar + +

Una vez la gente haya visto tu documento y hayas podido incorporar las posibles sugerencias que te hayan hecho, estás preparado para enviarlo.

- +

Para hacerlo, compacta el/los documentos en un fichero tar. Si tu documentación consta de 3 ficheros,

     % tar cf doc.tar one two three
     

Una vez hecho, comprime el fichero tar,

     % gzip -9 doc.tar
     

creando el fichero doc.tar.gz.

A continuación envía el fichero /pub/FreeBSD/incoming/.

Ahora tienes que comunicar al proyecto de documentación la existencia del fichero. La manera correcta de hacerlo es usar un comando llamado send-pr, el cual debería estar instalado en tu máquina.

Tienes que hacer esto para que tu envío pueda ser controlado. - Cuando envías un PR (Problem Report) se le asigna un + Cuando envías un PR (Problem Report) se le asigna un número único. Así uno de los committers puede asignarse el PR, y ponerse de acuerdo contigo para hacer el envío final.

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!

Asegúrate que el campo "Category" tiene como valor "docs" y que el campo "Class" está en "change-request". No te olvides de incluir el nombre del fichero que has enviado, para que el committer pueda encontrarlo.

-

Cuando sales del editor, será enviado un mensaje de PR al +

Cuando sales del editor, será enviado un mensaje de PR al lugar correcto. En un corto periodo de tiempo recibirás un mensaje de notificación indicandote el número de PR asignado, pudiendo usar este número para hacer el seguimiento del estado en que se encuentra.

Alternativamente, puedes usar un interface web en http://www.freebsd.org/send-pr.html.

- -

He hecho algunos cambios a documentación ya existente. Como + +

He hecho algunos cambios a documentación ya existente. Como la envío?

De nuevo, gracias por ocuparte de ello.

Lo primero que tienes que hacer es crear un fichero especial llamado diff. Este fichero mostrará única y exclusivamente las modificaciones realizadas sobre la documentación original.

Para hacer un "diff" tienes que;

  1. Hacer una copia del fichero que vas a modificar. Si estás cambiando el fichero

         % cp foo.sgml foo.sgml.old
     	
  2. - +
  3. Entonces, haz los cambios en el fichero foo.sgml

         % vi foo.sgml
         ... tap tap tap ...
     
         ... testea los cambios, leelos y revisalos...
     	
  4. Haz el diff. El comando para hacerlo es

         % diff -c foo.sgml.old foo.sgml > foo.diff
     	

    Este comando buscará las diferencias entre los dis ficheros escribiendolas en el fichero

- +

Ya puedes enviar el fichero

También puedes enviar el fichero ftp://ftp.FreeBSD.ORG /pub/FreeBSD/incoming/ o, si es muy pqueño, incluir el diff directamente en el PR, en la sección "Fix:"

De cualquier manera, usarás el comando send-pr para hacer saber a los "committers" que se han producido modificaciones. Asegúrate que el campo "Category" contiene "docs" y que el campo "Class" es "doc-bug" (si tu cambio modifica algún error ya existente) o "change-request" (si estás añadiendo nueva información a una sección ya existente).

FreeBSD Documentation Project Home &footer diff --git a/es/docproj/translations.sgml b/es/docproj/translations.sgml index b120c8b7ae..a7b966feba 100644 --- a/es/docproj/translations.sgml +++ b/es/docproj/translations.sgml @@ -1,168 +1,169 @@ - - + + %navincludes; %includes; ]> - + &header;

El "FreeBSD Chinese Documentation Project"

Web: -
E-Mail: foxfair@FreeBSD.org
Listas de distribución disponibles
-Envía un mail a -majordomo@freebsd.sinica.edu.tw con el texto +Envía un mail a +majordomo@freebsd.sinica.edu.tw con el texto "subscribe freebsd-chinese-doc" en el cuerpo del mensaje.
-El envío de mensajes sólo está permitido para los -miembros de +El envío de mensajes sólo está permitido para los +miembros de freebsd-chinese-doc@freebsd.sinica.edu.tw
Documentos disponibles
FAQ
Documentos en desarrollo
Handbook

El "FreeBSD Estonian Documentation Project"

Web: http://www.matti.ee/~vallo/
Documentos disponibles
>Sección PPP del Hnadbook
-
+

El "French FreeBSD Documentation Project"

Web: http://www.freebsd-fr.org
Listas de distribución disponibles
-
Envía un mail a - listserver@freebsd-fr.org +
Envía un mail a + listserver@freebsd-fr.org con las palabras "SUB freebsd-questions" en el cuerpo del mensaje para hacer la subscripción en la lista questions en franc´s
Envía un mail a listserver@freebsd-fr.org"> con las palabras "SUB annonces" en el cuerpo del mensaje para hacer la subscripción en la lista announce en francés.
Documentos disponibles
FAQ
Algunos tutoriales
Really Quick Newsletters
PicoBSD
Documentos actualmente en desarrollo
Handbook
CVS repository
CVS web

El "FreeBSD German Documentation Project"

Web: http://www.de.freebsd.org/de/uebersetzung.html
E-Mail: de-bsd-translators@de.freebsd.org
Documentos actualmente en desarrollo
Handbook
-
+

El "FreeBSD Italian Documentation Project"

Web: -
E-Mail: maw58@hotmail.com
Documentos actualmente en desarrollo
Handbook

El "FreeBSD Japanese Documentation Project"

Web: http://www.jp.freebsd.org/doc-jp/
E-Mail: doc-jp@jp.freebsd.org
Documentos disponibles
Handbook, FAQ, Web, FreeBSD NewsLetter Issue #2
Documentos actualmente en desarrollo
Tutoriales de FreeBSD
-
+ + -

El "FreeBSD Korean Documentation Project"

-Web: http://www.kr.freebsd.org/projects/doc-kr/
+Web: http://www.kr.freebsd.org/projects/doc-kr/
E-Mail: doc@kr.freebsd.org
Documentos actualmente en desarrollo
Handbook

El "FreeBSD Russian Documentation Project"

Web: http://surw.chel.su/~andy/index.html
E-Mail: Andrey Zakhvatov <andy@cgu.chel.su>
Documentos disponibles
FAQ
QA
Documents currently at working
WWW
Handbook

El "FreeBSD Spanish Documentation Project"

Web: http://www.es.freebsd.org/es/
E-Mail: jesusr@freebsd.org
Listas de distribución disponibles
Envía un mail a freebsd-subscribe@es.freebsd.org para suscribirte en la lista.
Documentos disponibles
FAQ
Documentos actualmente en desarrollo
Handbook, Web

FreeBSD Documentation Project Home &footer diff --git a/es/docproj/who.sgml b/es/docproj/who.sgml index 06d72f806e..50bf3dfe28 100644 --- a/es/docproj/who.sgml +++ b/es/docproj/who.sgml @@ -1,35 +1,36 @@ - - + + %navincludes; %includes; ]> - + &header;

El proyecto está compuesto por un grupo de personas a nivel totalmente individual, y lo único que tenemos en común es - que estamos subscritos a la lista de distribución + que estamos subscritos a la lista de distribución FreeBSD-doc@FreeBSD.ORG.

-

Algunos de nosotros podemos hacer "commits" directamente en la +

Algunos de nosotros podemos hacer "commits" directamente en la sección de documentación de FreeBSD. La lista completa de personas con privilegios de "commit" está en el Handbook.

- +

Otros no tienen privilegios de "committer", pero escriben y envían documentación - igualmente. Uno de los "committers" la incluirá en la + igualmente. Uno de los "committers" la incluirá en la distribución principal.

- +

Si quieres ayuda y participar en el proyecto de documentació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ás a formar parte del proyecto.

FreeBSD Documentation Project Home &footer diff --git a/es/docs.sgml b/es/docs.sgml index b65c660901..f7ce00b4db 100644 --- a/es/docs.sgml +++ b/es/docs.sgml @@ -1,267 +1,268 @@ - + + %navincludes; %includes; ]> - + &header; - +BSD Daemon reading documentation

FreeBSD en la Prensa

Noticias sobre FreeBSD.

Compatibilidad año 2000

-

Este es el estado actual del proyecto FreeBSD respecto a la +

Este es el estado actual del proyecto FreeBSD respecto a la compatibilidad del año 2000.

- +

Newsletter

The FreeBSD Newsletter, publicada y distribuida gratuitamente por Walnut Creek CDROM.

FreeBSD Real-Quick (TM) Newsletter (RQN)

Recopilación de noticias mensuales (a veces quincenales) referentes a los desarrollos en FreeBSD. Subscríbete a la lista freebsd-announce para recibirla vía e-mail.

Manual de FreeBSD

Esta es una valiosa herramienta en constante desarrollo para usuarios de FreeBSD. Por favor, dirigir comentarios, sugerencias o contribuciones a <freebsd-doc@FreeBSD.ORG>.

- -

También está disponible la + +

También está disponible la Traducción Japonesa del manual (codificación EUC).

Frequently Asked Questions (FAQ)

- +

Si tienes una pregunta o duda, hay muchas posibilidades de que otras personas también la hayan tenido. La mayoría de ellas han sido recopiladas en formato de pregunta-respuesta.

&i.new; Ahora ofrecemos una traducción en Ruso y traducción en Chino de las FAQ.

Tutoriales

- -

Aquí tienes una serie de documentos referentes a FreeBSD, + +

Aquí tienes una serie de documentos referentes a FreeBSD, tanto a nivel de hardware como de software. Si tienes algún - comentario o te gustaría enviar alguna documentación - puedes ponerte en contacto con nosotros en + comentario o te gustaría enviar alguna documentación + puedes ponerte en contacto con nosotros en freebsd-doc@FreeBSD.org.

Recursos Adicionales

-

www.FreeBSD.org no es el único lugar donde conseguir +

www.FreeBSD.org no es el único lugar donde conseguir información sobre FreeBSD. Varios esfuerzos independientes han conseguido crear valiosos documentos sobre FreeBSD:

  • Kirk McKusick, uno - de los arquitectos originales de BSD en la Universidad de Berkeley, - explica en dos cursos las + de los arquitectos originales de BSD en la Universidad de Berkeley, + explica en dos cursos las interioridades del Kernel 4.4BSD usando FreeBSD. Para aquellos que no puedan acudir a sus clases, está disponible una cinta de vídeo.

  • El Open Directory Project ofrece una excelente selección de - links sobre FreeBSD, incluyendo una lista de + links sobre FreeBSD, incluyendo una lista de importantes usuarios que puede ser útil para temas de marketing.

  • Computer Bits, Una revista on-line de Internet, ha estado publicando desde Marzo de 1996 - una serie de excelentes artículos relacionados con FreeBSD en su + una serie de excelentes artículos relacionados con FreeBSD en su columna titulada The Network Community, escrita por Ted Mittelstaedt. -
    Estos artículos cubren desde +
    Estos artículos cubren desde cómo instalar un servidor de correo basado en FreeBSD hasta - configuración del + configuración del Network Address Translation.

  • A Comprehensive Guide to FreeBSD - un intento en formato de lectura - más cómoda explicando el sistema operativo FreeBSD. + más cómoda explicando el sistema operativo FreeBSD. Dirigido especialmente a personas nuevas tanto en FreeBSD como en Unix. Actualmente en progreso.

  • FreeBSD How-To's for the Lazy and Hopeless es otro intento de documentación sobre instalación y configuración de FreeBSD en formato How-To.

  • The Linux+FreeBSD mini-HOWTO - 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.

Libros

La documentación online es útil, pero cualquier usuario "serio" de FreeBSD debería considerar disponer de alguno de los libros listados aquí. La mayoría de libros que cubren el sistema BSD se adaptan perfectamente a FreeBSD.

Páginas man

- +
FreeBSD
Por release: 1.0, 1.1, 1.1.5.1, 2.0, 2.0.5, 2.1.0, 2.1.5, 2.1.6.1, 2.1.7.1, 2.2.1, 2.2.2, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 3.0, 3.1, 4.0-current, Ports.
- +
Otros sistemas
Unix Seventh Edition (V7), 2.8BSD, 2.9.1BSD, 2.10BSD, 2.11BSD, 4.3BSD Reno, NET/2, 386BSD 0.1, 4.4BSD Lite2, Linux Slackware, NetBSD, OpenBSD, Plan 9, SunOS 4.x, SunOS 5.x, ULTRIX 4.2, - and + and XFree86.
- + -

Este servicio es por cortesía de +

Este servicio es por cortesía de Wolfram Schneider. Hay otro script disponible con las páginas man de FreeBSD 2.0 y - XFree86 release 3.1, cortesía de + XFree86 release 3.1, cortesía de Hinrich Eilts.

Documentos 4.4BSD

Si te gusta leer los manuales de BSD online, aquí tienes una versión hipertexto de los documentos 4.4BSD en /usr/share/doc

Documentos Info

Si te gusta leer los documentos Info de FreeBSD online, aquí tienes una versión hypertexto de los documentos Info en /usr/share/info.

El código fuente

Si quieres poner tus manos en el código fuente, aquí tienes una versión hipertexto del kernel de FreeBSD. Cortesía de Warren Toomey.

Proyecto de Documentación de FreeBSD

Como FreeBSD, esta documentación es el resultado de voluntarios. Los objetivos del proyecto están descritos aquí, así como los procedimientos para enviar correcciones y nuevo material.

The - FreeBSD Diary

+ FreeBSD Diary

El FreeBSD Diary es una colección de documentos en formato - how-to para principiantes en UNIX. El objetivo es ofrecer una + how-to para principiantes en UNIX. El objetivo es ofrecer una serie de guís paso a paso para instalar y configurar diferentes aspectos de FreeBSD.

&footer; diff --git a/es/features.sgml b/es/features.sgml index b86ecb63f9..b3f77af7d1 100644 --- a/es/features.sgml +++ b/es/features.sgml @@ -1,104 +1,97 @@ - + + %navincludes; %includes; ]> - + &header; -

FreeBSD ofrece diferentes características avanzadas.

+

FreeBSD ofrece diferentes características avanzadas.

-

No importa que aplicación quieras que use los recursos del sistema aprovechándolos al máximo. Las avanzadas características de FreeBSD se encargarán de ello.

-
-
Un - sistema operativo completo basado en 4.4BSD. +

Un + sistema operativo completo basado en 4.4BSD.

-

Las raices de FreeBSD derivan de la última release de software del Computer Systems Research Group de la Universidad de California, Berkeley. El libro The Design and Implementation of 4.4BSD Operating System, escrito por los arquitectos del sistema 4.4BSD, describe en detalle muchas de las funcionalidades del núcleo de FreeBSD.

Gracias al nivel y experiencia de diversos grupos de desarrolladores de -todo el mundo, el proyecto FreeBSD ha trabajado para extender las -características y posibilidades del sistema operativo 4.4BSD, +todo el mundo, el proyecto FreeBSD ha trabajado para extender las +características y posibilidades del sistema operativo 4.4BSD, consiguiendo en cada nueva release un sistema operativo más estable, rápido y conteniendo nuevas funcionalidades creadas a demanda de los usuarios.

-
-
+

FreeBSD ofrece el más alto rendimiento, gran compatibilidad con otros sistemas operativos y una menor administración del sistema. - +

-

Los desarrolladores de FreeBSD se han enfrentado a algunos de los problemas más difíciles en el diseño de sistemas operativos para poder ofrecerte estas avanzadas características:

    -
  • Bounce buffering trata sobre la limitación en la +
  • Bounce buffering trata sobre la limitación en la arquitectura ISA de los PC's que limita el acceso directo a memoria en los -primeros 16 megabytes.

    Resultado: sistemas con más de +primeros 16 megabytes.

    Resultado: sistemas con más de 16 megabytes operan más eficientemente con periféricos DMA en el bus ISA.

  • -
  • Un buffer de caché conjunto de memoria virtual y sistema de -ficheros continuamente ajusta la cantidad de memoria usada por los +
  • Un buffer de caché conjunto de memoria virtual y sistema de +ficheros continuamente ajusta la cantidad de memoria usada por los programas y el cache de disco.

    Resultado: los programas reciben una excelente gestión de memoria y un alto rendimiento en los accesos a disco, liberando al administrador del sistema del trabajo de ajustar los tamaños de los cachés.

  • Módulos de compatibilidad que permiten la ejecución de programas de otros sistemas operativos en FreeBSD, incluyendo programas para Linux, SCO, NetBSD y BSDI. -

    Resultado: los usuarios no tendrán que recompilar +

    Resultado: los usuarios no tendrán que recompilar programas ya compilados para algunos de los sistemas compatibles, teniendo acceso a programas como las extensiones para BSDI de Microsoft FrontPage Server o WordPerfect para SCO y Linux.

  • -
  • Módulos de kernel de carga dinámica que permiten +
  • Módulos de kernel de carga dinámica que permiten tener acceso a nuevos sistemas de ficheros, protocolos de red o emuladores -de binarios en tiempo de ejecución sin necesidad de generar un -nuevo kernel.

    Resultado: Se puede ganar mucho tiempo y +de binarios en tiempo de ejecución sin necesidad de generar un +nuevo kernel.

    Resultado: Se puede ganar mucho tiempo y desarrolladores de terceras partes pueden ofrecer subsistemas completos como módulos de kernel sin necesidad de distribuir el código fuente o complejos procedimientos de instalación.

  • Librerías compartidas reducen el tamaño de los -programas, ahorrando espacio de disco y memoria. FreeBSD usa un avanzado +programas, ahorrando espacio de disco y memoria. FreeBSD usa un avanzado esquema de librerías compartidas que ofrecen muchas de las ventajas -de ELF, ofreciendo la versión actual compatibilidad ELF con +de ELF, ofreciendo la versión actual compatibilidad ELF con programas de Linux y nativos de FreeBSD.

Naturalmente, cómo FreeBSD es un esfuerzo en constante evolución, puedes esperar nuevas características y niveles más altos de estabilidad con cada release.

-
-

Lo que dicen los expertos . . .

+

Lo que dicen los expertos . . .

-

``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.''

---Brett Glass, Infoworld, April 8 1996.

-
&footer; diff --git a/es/gnome/contact.sgml b/es/gnome/contact.sgml index 25f1f73078..214e1293af 100755 --- a/es/gnome/contact.sgml +++ b/es/gnome/contact.sgml @@ -1,47 +1,48 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header;

Contacto

Cualquier pregunta que tenga que ver con GNOME en FreeBSD debe ser - dirigida a la lista de correo + dirigida a la lista de correo freebsd-gnome. Todos - los usuarios de FreeBSD-GNOME, así como aquellos que desean - ayudar a mejorar y mantener GNOME en FreeBSD, sientanse libres de + los usuarios de FreeBSD-GNOME, así como aquellos que desean + ayudar a mejorar y mantener GNOME en FreeBSD, sientanse libres de participar. - De cualquier forma, no es necesario subscribirse si solamente desea - reportar un problema o solicitar ayuda - simplemente envíe su - mensaje a + De cualquier forma, no es necesario subscribirse si solamente desea + reportar un problema o solicitar ayuda - simplemente envíe su + mensaje a &email;@FreeBSD.org.

Todos los asuntos de importancia deben llevarse a cabo en la lista de correo, a menos de que exista una buena razón para contactar a - los desarrolladores directamente. A continuación se lista a - las personas involucradas directamente con el Proyecto FreeBSD GNOME + los desarrolladores directamente. A continuación se lista a + las personas involucradas directamente con el Proyecto FreeBSD GNOME (por orden alfabético):

-

A los desarrolladores de FreeBSD GNOME también se les puede - encontrar paseando por el IRC. Así que si desea tratar temas - relacionados con FreeBSD-GNOME, puede entrar en #freebsd-gnome en +

A los desarrolladores de FreeBSD GNOME también se les puede + encontrar paseando por el IRC. Así que si desea tratar temas + relacionados con FreeBSD-GNOME, puede entrar en #freebsd-gnome en FreeNode.

&footer; diff --git a/es/gnome/docs/bugging.sgml b/es/gnome/docs/bugging.sgml index 35deeb0184..93c3663d73 100755 --- a/es/gnome/docs/bugging.sgml +++ b/es/gnome/docs/bugging.sgml @@ -1,115 +1,116 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header; -

1. ¿Qué hay que incluír en un informe de +

1. ¿Qué hay que incluír en un informe de error?

-

La regla del pulgar es: incluya toda la información +

La regla del pulgar es: incluya toda la información posible. Incluso si cuenta con información que no sea muy - relevante, los desarrolladores puden descartarla sin problema. - Por el contrario, la situación es muy complicada cuando hay - muy poca información para rastrear o repetir el problema - - en estos casos los desarrolladores deben pasar mucho tiempo - adivinando y/o preguntando a quien envió el informe para + relevante, los desarrolladores puden descartarla sin problema. + Por el contrario, la situación es muy complicada cuando hay + muy poca información para rastrear o repetir el problema + - en estos casos los desarrolladores deben pasar mucho tiempo + adivinando y/o preguntando a quien envió el informe para obtener más información.

-

Existe una infinidad de ejemplos de informes de errores - completamente inútiles, algo como "Hey, existe un - problema con gnomefoo. Estoy usando FreeBSD-X.Y. Por favor - arréglenlo". De sobra esta decir que este informe es - una pérdida de tiempo tanto para quien lo envía - como para el desarrollador y por supuesto de ancho de banda. - Como mínimo el informe debe contener la siguiente +

Existe una infinidad de ejemplos de informes de errores + completamente inútiles, algo como "Hey, existe un + problema con gnomefoo. Estoy usando FreeBSD-X.Y. Por favor + arréglenlo". De sobra esta decir que este informe es + una pérdida de tiempo tanto para quien lo envía + como para el desarrollador y por supuesto de ancho de banda. + Como mínimo el informe debe contener la siguiente información:

    -
  • La versión exacta del sistema operativo +

  • La versión exacta del sistema operativo (normalmente es la salida de uname -a).

  • Una lista de todos los paquetes instalados en su sistema.

  • Sus variables de entorno (la salida de /usr/bin/env ). -

  • Si esta compilado desde los ports; la fecha y hora - estimada de la última vez que actualizó su +

  • Si esta compilado desde los ports; la fecha y hora + estimada de la última vez que actualizó su árbol de ports.

  • -
  • Información específica de cada tipo de - error: el archivo de registro (log) de una compilación - fallida en el caso de que el fallo se presente al compilar un - port, un stack trace en caso de que se trate de un core dump, +

  • Información específica de cada tipo de + error: el archivo de registro (log) de una compilación + fallida en el caso de que el fallo se presente al compilar un + port, un stack trace en caso de que se trate de un core dump, una clara y detallada descripción del problema cuando la aplicación realiza algo inesperado, etc. Intente ponerse - en los zapatos del desarrollador y en cada caso en particular, - y evaluar que información será necesaria para - lograr llegar a la raíz del problema. No asuma que + en los zapatos del desarrollador y en cada caso en particular, + y evaluar que información será necesaria para + lograr llegar a la raíz del problema. No asuma que ellos ya saben del problema pero son flojos para arreglarlo.

-

Si cuenta con una solución o una forma de arreglarlo, - entonces inclúyalo también en el informe, +

Si cuenta con una solución o una forma de arreglarlo, + entonces inclúyalo también en el informe, aún cuando no esté seguro de que sea la mejor forma - de arreglarlo. Si no lo es, le puede dar una buena idea a los - desarrolladores para enfocarlo, lo cual se traduce en ahorro + de arreglarlo. Si no lo es, le puede dar una buena idea a los + desarrolladores para enfocarlo, lo cual se traduce en ahorro de tiempo.

2. ¿Dónde informar?

Antes de avisar de un fallo, o incluso enviar un correo a la - lista, haga una + lista, haga una búsqueda por los archivos de la lista de correo de FreeBSD GNOME, para ver si no se ha informado ya del problema. La mayor parte de los - problemas se repiten y al realizar dicha - búsqueda puede encontrar una solución más + problemas se repiten y al realizar dicha + búsqueda puede encontrar una solución más rápidamente.

-

Una vez que esté seguro de que se trata de un nuevo - informe existen varias formas de enviar un informe de fallo en - GNOME para FreeBSD: puede enviar un informe a la +

Una vez que esté seguro de que se trata de un nuevo + informe existen varias formas de enviar un informe de fallo en + GNOME para FreeBSD: puede enviar un informe a la lista de correo freebsd-gnome - , rellenar un informe de fallos en el - sistema de - gestión de informes de fallos de FreeBSD, + , rellenar un informe de fallos en el + sistema de + gestión de informes de fallos de FreeBSD, enviar su informe a los mismos desarrolladores de GNOME, a su - sistema de seguimiento de + sistema de seguimiento de fallos, o bien una combinación de estos.

-

Es prácticamente imposible definir una gíua que - claramente le indique dónde informar en cada caso - particular, por lo que debe hacer uso de su sentido - común; de cualquier forma estas reglas pueden serle +

Es prácticamente imposible definir una gíua que + claramente le indique dónde informar en cada caso + particular, por lo que debe hacer uso de su sentido + común; de cualquier forma estas reglas pueden serle útiles:

    -
  • Si es un problema específico de FreeBSD (p.e. +

  • Si es un problema específico de FreeBSD (p.e. error en checksum, fallo de un parche, error de escritura en el - Makefile del port, etc.), entonces envíelo a la lista de + Makefile del port, etc.), entonces envíelo a la lista de correo freebsd-gnome.

  • -
  • Si es claro que el problema no es específico de - FreeBSD y no conoce la solución envíelo a los +

  • Si es claro que el problema no es específico de + FreeBSD y no conoce la solución envíelo a los desarrolladores del software directamente: - para la mayoría de los componentes de GNOME hay que + para la mayoría de los componentes de GNOME hay que usar su sistema de fallos, Bugzilla).

  • -
  • Si el problema no es particular de FreeBSD pero es algo - grave y usted cuenta con una solución entonces informe - a ambos; a FreeBSD y al sistema de fallos del autor, de tal - forma que el port en cuestión será arreglado y - otros usuarios de FreeBSD se beneficiarán de su - solución sin la necesidad de esperar la próxima +

  • Si el problema no es particular de FreeBSD pero es algo + grave y usted cuenta con una solución entonces informe + a ambos; a FreeBSD y al sistema de fallos del autor, de tal + forma que el port en cuestión será arreglado y + otros usuarios de FreeBSD se beneficiarán de su + solución sin la necesidad de esperar la próxima versión del proveedor.

&footer; diff --git a/es/gnome/docs/develfaq.sgml b/es/gnome/docs/develfaq.sgml index 1eded04101..42b4c80a82 100644 --- a/es/gnome/docs/develfaq.sgml +++ b/es/gnome/docs/develfaq.sgml @@ -1,189 +1,190 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header;

Contenido

    -
  1. ¿Qué son las versiones de +
  2. ¿Qué son las versiones de desarrollo de GNOME? -
  3. ¿Debo seguir las versiones de +
  4. ¿Debo seguir las versiones de desarrollo? -
  5. ¿Cómo obtengo partes de las +
  6. ¿Cómo obtengo partes de las versiones de desarrollo de GNOME? -
  7. ¿Cómo me mantengo actualizado y +
  8. ¿Cómo me mantengo actualizado y sincronizado? -
  9. ¿Qué debo hacer cuando algo no +
  10. ¿Qué debo hacer cuando algo no funcione? -
  11. ¿Cómo puedo ayudar con las +
  12. ¿Cómo puedo ayudar con las versiones de desarrollo? -
  13. ¿Cúal es el estado actual del +
  14. ¿Cúal es el estado actual del desarrollo de GNOME sobre FreeBSD?

Texto Completo

  1. ¿Qué son las versiones de desarrollo de GNOME?

    -

    Las versiones de desarrollo son los paquetes liberados por el - proyecto GNOME, que eventualmente serán las versiones +

    Las versiones de desarrollo son los paquetes liberados por el + proyecto GNOME, que eventualmente serán las versiones estables. Existen tres ramas principales en estas versiones:

    1. STABLE (ESTABLE) - Las librerías y aplicaciones - en la rama estable son consideradas "de calidad comprobada" y - son las versiones que aparecen en el árbol de ports de - FreeBSD. La versión estable actual de GNOME es + en la rama estable son consideradas "de calidad comprobada" y + son las versiones que aparecen en el árbol de ports de + FreeBSD. La versión estable actual de GNOME es &gnomever;.
    2. -
    3. DEVELOPMENT (DESARROLLO) - Entre cada versión - estable están las versiones de desarrollo. - Tradicionalmente las versiones en desarrollo de GNOME cuentan - con numeros impares (p.e. 2.3, 2.5, 2.(n*2)-1). Las versiones - en desarrollo serán las versiones estables y son - consideradas de calidad beta. Las versiones de desarrollo - necesitan ser probadas por usuarios de FreeBSD para poder +
    4. DEVELOPMENT (DESARROLLO) - Entre cada versión + estable están las versiones de desarrollo. + Tradicionalmente las versiones en desarrollo de GNOME cuentan + con numeros impares (p.e. 2.3, 2.5, 2.(n*2)-1). Las versiones + en desarrollo serán las versiones estables y son + consideradas de calidad beta. Las versiones de desarrollo + necesitan ser probadas por usuarios de FreeBSD para poder minimizar las sorpresas una vez que la versión estable es - incluída en el árbol de ports CVS de FreeBSD. + incluída en el árbol de ports CVS de FreeBSD. Este documento trata sobre ésta rama.
    5. -
    6. CVS - Contínuamente - lo-último-de-lo-último, las aplicaciones y +
    7. CVS - Contínuamente + lo-último-de-lo-último, las aplicaciones y bibliotecas de la versión de CVS de GNOME son de calidad - alpha y en ocasiones completamente incompilables. El proyecto - FreeBSD GNOME presta atención pero no da seguimiento al + alpha y en ocasiones completamente incompilables. El proyecto + FreeBSD GNOME presta atención pero no da seguimiento al código de calidad alpha.
  2. ¿Debo seguir las versiones de desarrollo?

    -

    Si usted busca en entorno estable, definitivamente no. - Por favor manténgase en la rama de desarrollo si - desea ayudar a identificar fallos y mejorar el proyecto +

    Si usted busca en entorno estable, definitivamente no. + Por favor manténgase en la rama de desarrollo si + desea ayudar a identificar fallos y mejorar el proyecto FreeBSD GNOME. A usted le parecerá poco gracioso si una aplicación en desarrollo destruye su trabajo.

  3. -

    ¿Cómo obtengo partes de las versiones de +

    ¿Cómo obtengo partes de las versiones de desarrollo de GNOME?

    -

    Marcus es el - responsable de mantener el servidor CVS donde se ubican - todos los componentes de las versiones en desarrollo del - proyecto FreeBSD GNOME. Las instrucciones sobre como ver - el módulo ``ports'' y cómo fusionarlo con el - árbol de ports de FreeBSD están en la - página principal del repositorio. Por favor, lea +

    Marcus es el + responsable de mantener el servidor CVS donde se ubican + todos los componentes de las versiones en desarrollo del + proyecto FreeBSD GNOME. Las instrucciones sobre como ver + el módulo ``ports'' y cómo fusionarlo con el + árbol de ports de FreeBSD están en la + página principal del repositorio. Por favor, lea cuidadosamente las instrucciones en http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi.

  4. -

    ¿Cómo me mantengo sincronizado y +

    ¿Cómo me mantengo sincronizado y al día?

    -

    La respuesta corta es que debe usar el script - marcusmerge, que le servirá para fusionar - el árbol de desarrollo con el árbol de ports - de FreeBSD. El script marcusmerge está - disponible en el repositorio MarcusCom, bajo el modulo +

    La respuesta corta es que debe usar el script + marcusmerge, que le servirá para fusionar + el árbol de desarrollo con el árbol de ports + de FreeBSD. El script marcusmerge está + disponible en el repositorio MarcusCom, bajo el modulo portstools.

    -

    La respuesta aun mas corta y determinante es que si usted - no sabe como obtener algo por medio de CVS y fusionarlas +

    La respuesta aun mas corta y determinante es que si usted + no sabe como obtener algo por medio de CVS y fusionarlas usando un script preelaborado debería mantenerse con la rama estable.

  5. ¿Qué debo hacer cuando algo no funcione?

    -

    Depende. Si cree que el problema es realmente un error +

    Depende. Si cree que el problema es realmente un error de algún componente de GNOME puede enviar un informe - de error mediante bug-buddy o el interfaz de - GNOME Bugzilla. El - interfaz de Bugzilla para Evolution puede consultarse - aquí). Si + de error mediante bug-buddy o el interfaz de + GNOME Bugzilla. El + interfaz de Bugzilla para Evolution puede consultarse + aquí). Si considera que el problema está en un port de FreeBSD - o es específica de FreeBSD envíe un correo a + o es específica de FreeBSD envíe un correo a &email;@FreeBSD.org - o informe del problema en el canal de IRC - #freebsd-gnome, en FreeNode.

    + o informe del problema en el canal de IRC + #freebsd-gnome, en FreeNode.

  6. -

    ¿Cómo puedo ayudar con las versiones de +

    ¿Cómo puedo ayudar con las versiones de desarrollo?

    Necesitamos gente que haga todas las pruebas posibles y - que redacte tantos buenos informes de errores como sea - posible. Necesitamos también personas con - habilidades artísticas para crear - capturas de pantalla - impresionantes.

    -

    Si le gusta programar y sabe Perl necesitamos - imperiosamente ayuda para portar - gnome-system-tools. - Si está interesado en ayudar por favor - póngase en contacto con + que redacte tantos buenos informes de errores como sea + posible. Necesitamos también personas con + habilidades artísticas para crear + capturas de pantalla + impresionantes.

    +

    Si le gusta programar y sabe Perl necesitamos + imperiosamente ayuda para portar + gnome-system-tools. + Si está interesado en ayudar por favor + póngase en contacto con marcus@FreeBSD.org.

    -

    Incluso si trabajar con código fuente no es lo que - más le motiva necesitamos informes de experiencias - de actualización de GNOME 2.4 a GNOME 2.5; - necesitamos información sobre qué - aplicaciones muestran un comportamiento extraño; - necesitamos un conocimiento exhaustivo sobre todo aquello - que anda rondando las cabezas de nuestros y nuestras +

    Incluso si trabajar con código fuente no es lo que + más le motiva necesitamos informes de experiencias + de actualización de GNOME 2.4 a GNOME 2.5; + necesitamos información sobre qué + aplicaciones muestran un comportamiento extraño; + necesitamos un conocimiento exhaustivo sobre todo aquello + que anda rondando las cabezas de nuestros y nuestras usuarias acerca de GNOME y su futuro.

  7. -

    ¿Cúal es el estado actual del desarrollo +

    ¿Cúal es el estado actual del desarrollo de GNOME sobre FreeBSD?

    -

    Las versiones en desarrollo del entorno completo del - escritorio GNOME están disponibles y todas compilan - limpiamente.

    +

    Las versiones en desarrollo del entorno completo del + escritorio GNOME están disponibles y todas compilan + limpiamente.

    -

    La mayoría de los componentes de - x11/gnome2-fifth-toe cuentan con versiones en - desarrollo operables. Aunque AbiWord no compila - aún con las nuevas librerías GTK+-2.3, +

    La mayoría de los componentes de + x11/gnome2-fifth-toe cuentan con versiones en + desarrollo operables. Aunque AbiWord no compila + aún con las nuevas librerías GTK+-2.3, así como ninguna de las aplicaciones que cuentan con arreglos en C++. Los arreglos en C++ existen, pero ninguna - de las aplicaciones de Fifth Toe compilan aún. + de las aplicaciones de Fifth Toe compilan aún. GTetrinet tampoco compila aún.

    -

    Aquellas personas que usan GNOME 2.5 deberán - enfrentarse con un conflicto de ficheros entre libgnome y +

    Aquellas personas que usan GNOME 2.5 deberán + enfrentarse con un conflicto de ficheros entre libgnome y gnomecontrolcenter2 que provocan un fallo reiterativo en:

     	# portupgrade -f gnomecontrolcenter2
     	# portupgrade -f libgnome
                     
&footer; diff --git a/es/gnome/docs/faq.sgml b/es/gnome/docs/faq.sgml index 24c36ba0c4..66e438d836 100755 --- a/es/gnome/docs/faq.sgml +++ b/es/gnome/docs/faq.sgml @@ -1,510 +1,511 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header;

Contenido

    -
  1. ¿Cómo obtengo GNOME para +
  2. ¿Cómo obtengo GNOME para FreeBSD? -
  3. GNOME falla al compilarlo desde los ports. +
  4. GNOME falla al compilarlo desde los ports. ¿Qué debo hacer? -
  5. He instalado GNOME pero he perdido la +
  6. He instalado GNOME pero he perdido la aplicación foo. ¿Qué hago? -
  7. ¿Cómo puedo contar con mis +
  8. ¿Cómo puedo contar con mis componentes de GNOME actualizados? -
  9. ¿Cúal es la diferencia entre +
  10. ¿Cúal es la diferencia entre GNOME y KDE? ¿Cúal es mejor? -
  11. ¿Dónde puedo obtener más +
  12. ¿Dónde puedo obtener más temas para GNOME? -
  13. ¿Qué gestores de ventanas +
  14. ¿Qué gestores de ventanas trabajan bien con GNOME? -
  15. ¿Por qué no puedo ejecutar +
  16. ¿Por qué no puedo ejecutar aplicaciones de Linux desde el panel de GNOME? -
  17. ¿Por qué GNOME es tan grande, +
  18. ¿Por qué GNOME es tan grande, lento y básicamente inservible?
  19. ¿Soporta GNOME fuentes anti-alias?
  20. ¿ Cómo habilito el soporte para Java en los navegadores Mozilla o Galeon?
-

Texto Completo

+

Texto Completo

- - - - - - - - - - -
1. ¿Cómo obtengo GNOME para FreeBSD?

-

Existen dos formas de instalar GNOME en FreeBSD. Una manera - es por medio de +

+

Existen dos formas de instalar GNOME en FreeBSD. Una manera + es por medio de paquetes, y la otra forma es por medio de los ports.

Para instalar GNOME como package, use el siguiente comando:

# pkg_add -r gnome

Esto descargará los últimos paquetes disponibles - de GNOME desde el servidor FTP de FreeBSD y procederá + de GNOME desde el servidor FTP de FreeBSD y procederá a instalarlos en su sistema.

-

Para compilar e instalar GNOME desde la colección de +

Para compilar e instalar GNOME desde la colección de ports primero deberá actualizar su colección por - medio de - + medio de + cvsup y posteriormente:

 # cd /usr/ports/x11/gnome
 # make clean
 # make install clean
 	    
-

Una vez que ha instalado GNOME puede considerar - incluír lo siguiente en su fichero +

Una vez que ha instalado GNOME puede considerar + incluír lo siguiente en su fichero /etc/make.conf:

 WITH_GTK=yes
         
-

Este es un paso opcional pero permite que algunos ports, como +

Este es un paso opcional pero permite que algunos ports, como Vim, usen el sistema Gtk+.

-

Compilar e instalar GNOME desde los ports es el método más +

Compilar e instalar GNOME desde los ports es el método más adecuado para instalarlo en FreeBSD.


2. GNOME falla al compilarlo desde los ports. ¿Qué debo hacer?

-

La gran mayoría de los problemas de compilación - de GNOME pueden resolverse al asegurarnos de que todos - nuestros componentes de GNOME se encuentran debidamente - actualizados. - Todas las aplicaciones de GNOME requieren de los siguientes +

+

La gran mayoría de los problemas de compilación + de GNOME pueden resolverse al asegurarnos de que todos + nuestros componentes de GNOME se encuentran debidamente + actualizados. + Todas las aplicaciones de GNOME requieren de los siguientes componentes base para compilarse correctamente:

 pkg-config
 glib
 gettext
 gtk+
 ORBit
 Imlib
 esound
 gnomelibs
 gnomecore
             
-

Verifique que estos componentes están actualizados e +

Verifique que estos componentes están actualizados e intente compilar GNOME o su aplicación GNOME nuevamente. - Puede darse el caso de que vea advertencias del compilador, + Puede darse el caso de que vea advertencias del compilador, relacionadas con "pthreads" (POSIX threads), tales como:

 undefined reference to 'strerror_r'
             
-

Para arreglar este tipo de errores asegúrese de que +

Para arreglar este tipo de errores asegúrese de que cuenta con la siguiente opción compilada en su kernel:

 options     _KPOSIX_PRIORITY_SCHEDULING
             
-

Y asegúrese, si usa -stable o -current, de que - no cuenta con NOLIBC_R en su fichero - /etc/make.conf. Si es así, elimine esta +

Y asegúrese, si usa -stable o -current, de que + no cuenta con NOLIBC_R en su fichero + /etc/make.conf. Si es así, elimine esta opción y recompile todo el sistema (build world).

-

Algunos ports tal como devel/pth y - devel/ngpt, también pueden ocasionar algunos - problemas de "pthread" al compilar GNOME. Si no necesita +

Algunos ports tal como devel/pth y + devel/ngpt, también pueden ocasionar algunos + problemas de "pthread" al compilar GNOME. Si no necesita estos ports instalados es recomendable que los elimine.

-

Si aún se siguen presentando problemas por favor - envíe un correo a - &email;@FreeBSD.org +

Si aún se siguen presentando problemas por favor + envíe un correo a + &email;@FreeBSD.org con la salida que obtiene del fallo de compilación.


3. He instalado GNOME pero he perdido la aplicación foo. ¿Quéhago?

+

Solamente los componentes base y algunos extras están - incluidos en los paquetes de gnome. Existe otro - meta-port llamado gnome-fifth-toe que incluye algunas + incluidos en los paquetes de gnome. Existe otro + meta-port llamado gnome-fifth-toe que incluye algunas de las más populares (y mayores) aplicaciones de GNOME. - gnome-fifth-toe incluye Galeon, Pan, Gnumeric, + gnome-fifth-toe incluye Galeon, Pan, Gnumeric, AbiWord, GNUCash, Evolution, Gimp, Dia y otras.

Para instalar gnome-fifth-toe desde paquetes use:

 # pkg_add -r gnome-fifth-toe
 	    
-

Para compilar e instalar gnome-fifth-toe desde los +

Para compilar e instalar gnome-fifth-toe desde los ports:

 # cd /usr/ports/x11/gnome-fifth-toe
 # make clean
 # make install clean
 	    
-

Hay una lista completa de todas las aplicaciones de GNOME que - están disponibles para FreeBSD +

Hay una lista completa de todas las aplicaciones de GNOME que + están disponibles para FreeBSD aquí.


4. - ¿Cómo puedo actualizar mis componentes y + ¿Cómo puedo actualizar mis componentes y aplicaciones de GNOME?

-

Según mi propia experiencia - /usr/ports/sysutils/portupgrade funciona realmente +

+

Según mi propia experiencia + /usr/ports/sysutils/portupgrade funciona realmente bien. Por ejemplo:

# portupgrade -r pkgconfig -

actualizará pkgconfig y cualquier otro port (que +

actualizará pkgconfig y cualquier otro port (que requiera actualización) que dependa de él.

Aunque en ocasiones hay tantos cambios que es necesario hacer - un poco de limpieza más profunda. En este caso, + un poco de limpieza más profunda. En este caso, normalmente, lo siguiente suele funcionar:

 # pkg_delete -rf pkgconfig\*
 # cd /usr/ports/x11/gnome
 # make clean
 # make install clean
 	    
-

Con estos pasos eliminará todos los componentes y - aplicaciones de GNOME 1 y 2 de su computadora pero solamente - reinstala el escritorio GNOME 1. Es importante tener en cuenta - que si hace esto deberá reinstalar sus aplicaciones - una vez que haya reinstalado el escritorio. Afortunadamente +

Con estos pasos eliminará todos los componentes y + aplicaciones de GNOME 1 y 2 de su computadora pero solamente + reinstala el escritorio GNOME 1. Es importante tener en cuenta + que si hace esto deberá reinstalar sus aplicaciones + una vez que haya reinstalado el escritorio. Afortunadamente esta medida extrema rara vez es necesaria.


5. - ¿Cúal es la diferencia entre GNOME y KDE? + ¿Cúal es la diferencia entre GNOME y KDE? ¿Cúal es mejor?

-

Tanto GNOME como KDE son entornos de escritorio. GNOME - está basado en las librerías GTK+ y está - escrito fundamentalmente en C. Por otro lado KDE esta basado +

+

Tanto GNOME como KDE son entornos de escritorio. GNOME + está basado en las librerías GTK+ y está + escrito fundamentalmente en C. Por otro lado KDE esta basado en QT y está escrito principalmente en C++.

-

Ambos entornos ofrecen una amplia gama de aplicaciones, - juegos, utilidades y suites completas de oficina. Ambos estan +

Ambos entornos ofrecen una amplia gama de aplicaciones, + juegos, utilidades y suites completas de oficina. Ambos estan activamente en desarrollo y disponibles para FreeBSD. Si usted - está tratando de decidirse por alguno de estos use + está tratando de decidirse por alguno de estos use ambos y vea cuál es más de su agrado.

-

Puede saber más sobre KDE en +

Puede saber más sobre KDE en http://freebsd.kde.org.


6. ¿Donde puedo obtener más temas para GNOME?

+

Si usted esta cansado de los temas que vienen con GNOME por - defecto hay más opciones. En primer lugar la + defecto hay más opciones. En primer lugar la colección de ports de FreeBSD cuenta con una gran colección de temas GTK para GNOME. Para instalar estos paquetes ejecute:

# pkg_add -r gtk-engines-collection

Para instalar desde los ports:

 # cd /usr/ports/x11-toolkits/gtk-engines-collection
 # make clean
 # make install clean
 	    
-

Si aún quiere tener más temas consulte - http://art.gnome.org/. - Tenga en cuenta que quizás sea necesario que instale +

Si aún quiere tener más temas consulte + http://art.gnome.org/. + Tenga en cuenta que quizás sea necesario que instale gtk-engines-collection antes de usar cualquiera de los temas que aquí se han citado.


7. - ¿Qué gestores de ventanas trabajan bien con + ¿Qué gestores de ventanas trabajan bien con GNOME?

-

El meta port de gnome le instala como gestor de +

+

El meta port de gnome le instala como gestor de ventanas por defecto - Sawfish, pero existen otros gestores que pueden usarse con + Sawfish, pero existen otros gestores que pueden usarse con GNOME. Estos son algunos de ellos:


8. - ¿Por qué no puedo ejecutar aplicaciones de + ¿Por qué no puedo ejecutar aplicaciones de Linux desde el panel de GNOME?

-

La respuesta corta es que sí que puede. Lo más - probable es que su problema sea que tiene el Launch Feedback - (xalf) habilitado. xalf es un objeto compartido de FreeBSD y - como tal no puede ser cargado por aplicaciones de Linux. - Cuando intenta cargar una aplicación Linux no pasa nada - y algo como lo que se presenta a continuación le - aparecerá en ~/.gnomerc-errors o bien en la +

+

La respuesta corta es que sí que puede. Lo más + probable es que su problema sea que tiene el Launch Feedback + (xalf) habilitado. xalf es un objeto compartido de FreeBSD y + como tal no puede ser cargado por aplicaciones de Linux. + Cuando intenta cargar una aplicación Linux no pasa nada + y algo como lo que se presenta a continuación le + aparecerá en ~/.gnomerc-errors o bien en la salida estándar (stdout):

-/usr/local/Acrobat4/Reader/intellinux/bin/acroread: error in loading shared 
+/usr/local/Acrobat4/Reader/intellinux/bin/acroread: error in loading shared
 libraries: /usr/X11R6/lib/libxalflaunch.so.0: ELF file OS ABI invalid.
 	    
-

Para arreglar este problema necesita instalar el port - linux-xalf. Este port (o paquete) instala la - versión de Linux de libxalflaunch.so.0 en - /compat/linux/usr/X11R6/lib, y será usado cada +

Para arreglar este problema necesita instalar el port + linux-xalf. Este port (o paquete) instala la + versión de Linux de libxalflaunch.so.0 en + /compat/linux/usr/X11R6/lib, y será usado cada vez que se ejecuten aplicaciones Linux en lugar del binario de - FreeBSD. Puede ser que vea el siguiente error una vez que + FreeBSD. Puede ser que vea el siguiente error una vez que instale linux-xalf:

 /usr/libexec/ld-elf.so.1: Shared object "libkrb.so.3" not found
         

Puede obviarlo tranquilamente.


9. - ¿Por qué GNOME es tan grande, lento y + ¿Por qué GNOME es tan grande, lento y básicamente inservible?

-

Bueno, eso depende del punto de vista. Claro está que - tanto GNOME como KDE aún estan lejos de la - perfección o incluso de ser completos, y - difícilmente podrían ser comparados con algunas - ofertas comerciales en términos de facilidad de uso. - Pero al mismo tiempo es un paso gigantesco en la +

+

Bueno, eso depende del punto de vista. Claro está que + tanto GNOME como KDE aún estan lejos de la + perfección o incluso de ser completos, y + difícilmente podrían ser comparados con algunas + ofertas comerciales en términos de facilidad de uso. + Pero al mismo tiempo es un paso gigantesco en la dirección correcta. También es notable que tanto - GNOME como KDE aún son muy jóvenes y la + GNOME como KDE aún son muy jóvenes y la situación es la adecuada para mejorar mientras se madura (¿alguien recuerda lo espantoso que era Windows 3.11?).


10. ¿Soporta GNOME fuentes anti-alias?

-

¡Claro! Aunque existen dos cosas que usted debe - hacer antes de nada. En primer lugar deberá - ejecutar XFree86 4.0 o una versión posterior (se - recomienda 4.1 o posterior). Después necesita - instalar el port x11/gdkxft. ¡Y eso es - todo! No es necesario que recompile ninguna de las +

+

¡Claro! Aunque existen dos cosas que usted debe + hacer antes de nada. En primer lugar deberá + ejecutar XFree86 4.0 o una versión posterior (se + recomienda 4.1 o posterior). Después necesita + instalar el port x11/gdkxft. ¡Y eso es + todo! No es necesario que recompile ninguna de las aplicaciones de GNOME.

-

Si tiene algun problema consulte el - sitio web de - gdkxft o envíe un correo a +

Si tiene algun problema consulte el + sitio web de + gdkxft o envíe un correo a &email;@FreeBSD.org .

- -

Si tiene alguna pregunta o comentario por favor - envíelas a + +

Si tiene alguna pregunta o comentario por favor + envíelas a &email;@FreeBSD.org .


11. - ¿Cómo habilito el soporte Java para los + ¿Cómo habilito el soporte Java para los navegadores web Mozilla o Galeon?

-

Para habilitar el soporte Java en el navegador Mozilla debe +

+

Para habilitar el soporte Java en el navegador Mozilla debe instalar el port del Kit de Desarrollo Java disponible en el árbol de ports en java/jdk13 (es necesaria la - versión 1.3.1p6 o posterior) y reiniciar el navegador. - Nótese que si la versión de Mozilla instalado en + versión 1.3.1p6 o posterior) y reiniciar el navegador. + Nótese que si la versión de Mozilla instalado en su computadora es menor a 0.9.8_2,1, será necesario que cree un enlace simbólico al plugin Java con el siguiente comando:

 # ln -sf /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so \
 	/usr/X11R6/lib/mozilla/plugins/libjavaplugin_oji.so
 	    
-

Puede verificar que Mozilla ha detectado el plugin +

Puede verificar que Mozilla ha detectado el plugin correctamente al seleccionar Acerca de Plugins desde el - menú de Ayuda una vez que haya reiniciado Mozilla. - Debe de ver - /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so - en la lista de plugins disponibles, lo cual indica que el + menú de Ayuda una vez que haya reiniciado Mozilla. + Debe de ver + /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so + en la lista de plugins disponibles, lo cual indica que el soporte Java está habilitado.

-

Si ha compilado Galeon contra la versión completa de - Mozilla entonces el plugin Java también deberá +

Si ha compilado Galeon contra la versión completa de + Mozilla entonces el plugin Java también deberá funcionar. Solamente asegúrese que Permitir Java - esté habilitado en el menú de + esté habilitado en el menú de Preferencias.


&footer; diff --git a/es/gnome/docs/faq2.sgml b/es/gnome/docs/faq2.sgml index b21594e6d4..9aa8fadd23 100755 --- a/es/gnome/docs/faq2.sgml +++ b/es/gnome/docs/faq2.sgml @@ -1,676 +1,677 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header;

Contenido

    -
  1. ¿Cómo obtengo GNOME &gnomever; +
  2. ¿Cómo obtengo GNOME &gnomever; para FreeBSD? -
  3. GNOME &gnomever; esta fallando al compilar +
  4. GNOME &gnomever; esta fallando al compilar desde los ports. Qué debo hacer? -
  5. He instalado GNOME &gnomever; pero no - encuentro la aplicación foo. +
  6. He instalado GNOME &gnomever; pero no + encuentro la aplicación foo. ¿Qué hago? -
  7. ¿Cúal es la mejor forma de +
  8. ¿Cúal es la mejor forma de actualizar de GNOME 1.4 a GNOME 2? -
  9. ¿Cúal es la mejor forma de +
  10. ¿Cúal es la mejor forma de actualizar de GNOME 2.2 a GNOME &gnomever;? -
  11. ¿Cómo mantengo mis componentes +
  12. ¿Cómo mantengo mis componentes de GNOME &gnomever; y sus aplicaciones actualizadas? -
  13. ¿Puedo instalar aplicaciones de GNOME +
  14. ¿Puedo instalar aplicaciones de GNOME 1.4 bajo GNOME &gnomever;? -
  15. ¿Dónde puedo obtener más +
  16. ¿Dónde puedo obtener más temas para GNOME &gnomever;? -
  17. ¿Qué gestores de ventanas +
  18. ¿Qué gestores de ventanas van bien con GNOME &gnomever;? -
  19. ¿Soporta GNOME &gnomever; las fuentes +
  20. ¿Soporta GNOME &gnomever; las fuentes anti-alias?
  21. ¿Cómo puedo controlar qué fuentes son anti-alias?
  22. ¿Cómo edito los menús de mi GNOME 2? -
  23. ¿Cómo uso y configuro los - recursos de GTK+ 2 para aplicaciones GTK+ 2 cuando no me +
  24. ¿Cómo uso y configuro los + recursos de GTK+ 2 para aplicaciones GTK+ 2 cuando no me encuentro bajo GNOME? -
  25. ¿Cómo configuro mis +
  26. ¿Cómo configuro mis aplicaciones de GNOME 1.4 bajo GNOME &gnomever;? -
  27. El programa para escribir CDs de Nautilus - (cd-burner) no me permite grabar CDs. ¿Cómo +
  28. El programa para escribir CDs de Nautilus + (cd-burner) no me permite grabar CDs. ¿Cómo soluciono esto? -
  29. ¿Cómo incluyo una nueva +
  30. ¿Cómo incluyo una nueva opción de acceso bajo GDM?

Texto Completo

  1. -

    ¿Cómo obtengo GNOME &gnomever; para +

    ¿Cómo obtengo GNOME &gnomever; para FreeBSD?

    Existen dos maneras de instalar GNOME &gnomever; en FreeBSD. Una forma es mediante paquetes, y la otra forma es mediante la colección de - ports. Antes de emprender cualquier instalación, - usted debe familiarizarse con las + ports. Antes de emprender cualquier instalación, + usted debe familiarizarse con las notas importantes de GNOME &gnomever;.

    -

    Para instalar GNOME &gnomever; desde los paquetes use el +

    Para instalar GNOME &gnomever; desde los paquetes use el siguiente comando:

    # pkg_add -r gnome2 -

    Esto descargará los paquetes mas recientes de GNOME - &gnomever; desde los sitios FTP y procederá con la +

    Esto descargará los paquetes mas recientes de GNOME + &gnomever; desde los sitios FTP y procederá con la instalación en su sistema.

    -

    Para compilar e instalar GNOME &gnomever; desde los ports +

    Para compilar e instalar GNOME &gnomever; desde los ports primero debera actualizar sus ports vía - cvsup a la úúltima colección + cvsup a la úúltima colección disponible. Posteriormente:

     # cd /usr/ports/x11/gnome2
     # make clean
     # make install clean
                 
    -

    Para que su experiencia con GNOME &gnomever; sea más - grata le recomendamos que realice la instalación desde - los ports después de incluir las siguientes +

    Para que su experiencia con GNOME &gnomever; sea más + grata le recomendamos que realice la instalación desde + los ports después de incluir las siguientes líneas en su fichero /etc/make.conf:

     WITH_FAM=       yes
     WITH_LAME=      yes
                 
    -

    La línea WITH_FAM habilita el soporte para el - administrador de alteración de ficheros - (de FAM; File Alteration Manager), - que permite que Nautilus actualice la lista de - ficheros en tiempo real, así como el hecho de que los - componentes de GNOME detecten cambios en los ficheros de - configuración sin la necesidad de reiniciar GNOME. - Nótese que para que FAM funcione - correctamente también deberá incluir lo - siguiente en el fichero /etc/rc.conf y reiniciar su +

    La línea WITH_FAM habilita el soporte para el + administrador de alteración de ficheros + (de FAM; File Alteration Manager), + que permite que Nautilus actualice la lista de + ficheros en tiempo real, así como el hecho de que los + componentes de GNOME detecten cambios en los ficheros de + configuración sin la necesidad de reiniciar GNOME. + Nótese que para que FAM funcione + correctamente también deberá incluir lo + siguiente en el fichero /etc/rc.conf y reiniciar su computadora:

    En FreeBSD 4.x:
    portmap_enable="YES"

    En FreeBSD 5.x:
    rpcbind_enable="YES"

    -

    Con la línea WITH_LAME añadimos - soporte para archivos MP3. Esto habilita lo necesario para +

    Con la línea WITH_LAME añadimos + soporte para archivos MP3. Esto habilita lo necesario para que Nautilus ejecute ficheros MP3.

    -

    Estas opciones pueden ocasionar algunos errores de - compilación en ciertas plataformas, por lo que no se +

    Estas opciones pueden ocasionar algunos errores de + compilación en ciertas plataformas, por lo que no se habilitan por defecto.

    -

    Una vez que ya cuenta con el escritorio GNOME &gnomever; - instalado GNOME &gnomever; puede ser iniciado incluyendo la +

    Una vez que ya cuenta con el escritorio GNOME &gnomever; + instalado GNOME &gnomever; puede ser iniciado incluyendo la siguiente línea en el fichero ~/.xsession o ~/.xinitrc:

     exec gnome-session
                 
  2. -

    GNOME &gnomever; esta fallando al compilarlo desde los ports +

    GNOME &gnomever; esta fallando al compilarlo desde los ports ¿Qué debo hacer?

    La mayor parte de los problemas de compilación de GNOME - &gnomever; pueden resolverse al comprobar que todos los - componentes necesarios para GNOME &gnomever; se encuentran + &gnomever; pueden resolverse al comprobar que todos los + componentes necesarios para GNOME &gnomever; se encuentran debidamente actualizados.

    -

    En general cuando un componente de GNOME &gnomever; no se +

    En general cuando un componente de GNOME &gnomever; no se encuentra actualizado deber ver algo similar a lo siguiente:

     checking for libgnomeui-2.0 libbonoboui-2.0 libbonobo-2.0 >= 2.2.1
     gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2 libglade-2.0...
     configure: error: Library requirements (libgnomeui-2.0 libbonoboui-2.0
     libbonobo-2.0 >= 2.2.1 gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2
     libglade-2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable
     if your libraries are in a nonstandard prefix so pkg-config can find them.
                   
    -

    El simple hecho de mantener su colección de ports - actualizada le ayudara a prevenir estos +

    El simple hecho de mantener su colección de ports + actualizada le ayudara a prevenir estos errores.

    -

    Si la versión de pkg-config que usa necesita - actualización es posible que reciba +

    Si la versión de pkg-config que usa necesita + actualización es posible que reciba un error similar al siguiente:

     configure: error: *** pkg-config too old; version 0.14 or better required.
                   
    -

    Es posible que le cueste trabajo encontrar el aviso en un error - con texto muy abundante pero el error es muy claro: - necesita actualizar pkg-config. +

    Es posible que le cueste trabajo encontrar el aviso en un error + con texto muy abundante pero el error es muy claro: + necesita actualizar pkg-config. La aplicación pkg-config está en el port - devel/pkgconfig. Al actualizar este port a la + devel/pkgconfig. Al actualizar este port a la última versión el error desaparecerá.

    -

    También puede ver errores relacionados con procesos +

    También puede ver errores relacionados con procesos pthreads (threads) tales como:

     undefined reference to 'strerror_r'
                 
    -

    Para arreglar este tipo de errores asegúrese de contar - con la siguiente línea en el fichero de +

    Para arreglar este tipo de errores asegúrese de contar + con la siguiente línea en el fichero de configuración de su kernel:

     options     _KPOSIX_PRIORITY_SCHEDULING
                 
    -

    Y en el caso de que usted use la rama -STABLE o - -CURRENT verifique que no tenga NOLIBC_R - habilitado en el fichero /etc/make.conf. Si es - así elimínelo y posteriormente reconstruya el - sistema ejecutando rebuild world. Si aún persisten los - problemas envíe un correo a - &email;@FreeBSD.org - con la salida del error en la compilación. - También es de mucha ayuda el fichero config.log que +

    Y en el caso de que usted use la rama -STABLE o + -CURRENT verifique que no tenga NOLIBC_R + habilitado en el fichero /etc/make.conf. Si es + así elimínelo y posteriormente reconstruya el + sistema ejecutando rebuild world. Si aún persisten los + problemas envíe un correo a + &email;@FreeBSD.org + con la salida del error en la compilación. + También es de mucha ayuda el fichero config.log que está en el directorio work del port.

    -

    Ports tales como devel/pth y devel/ngpt - también pueden ocasionar problemas relacionados con - procesos pthread cuando se compila GNOME &gnomever;. Si no - necesita estos ports instalados es recomendable que los +

    Ports tales como devel/pth y devel/ngpt + también pueden ocasionar problemas relacionados con + procesos pthread cuando se compila GNOME &gnomever;. Si no + necesita estos ports instalados es recomendable que los elimine.

  3. He instalado GNOME &gnomever; pero no encuentro la aplicación foo. ¿Qué hago?

    Solamente los componentes básicos de GNOME &gnomever; y algunos extras son incluidos en la instalación del paquete - gnome2. Aunque puede ejecutar - aplicaciones de GNOME 1.4 bajo GNOME - &gnomever;, una gran cantidad de aplicaciones han sido migradas + gnome2. Aunque puede ejecutar + aplicaciones de GNOME 1.4 bajo GNOME + &gnomever;, una gran cantidad de aplicaciones han sido migradas ya a GNOME &gnomever;.

    -

    Las aplicaciones que han sido migradas se incluyen en el - meta-port gnome2-fifth-toe. Tenga en cuenta que +

    Las aplicaciones que han sido migradas se incluyen en el + meta-port gnome2-fifth-toe. Tenga en cuenta que algunas de estas aplicaciones se encuentran en fase primaria de desarrollo y pueden no ser muy estables.

    -

    Para instalar gnome2-fifth-toe desde +

    Para instalar gnome2-fifth-toe desde paquetes, ejecute lo siguiente:

     # pkg_add -r gnome2-fifth-toe
                 
    -

    Para instalar gnome2-fifth-toe desde los +

    Para instalar gnome2-fifth-toe desde los ports ejecute los siguiente:

     # cd /usr/ports/x11/gnome2-fifth-toe
     # make clean
     # make install clean
                 
  4. -

    ¿Cúal es la mejor forma de actualizar de +

    ¿Cúal es la mejor forma de actualizar de GNOME 1.4 a GNOME 2?

    -

    Actualmente el proyecto GNOME es muy dinámico. Es - mucho el trabajo que se realiza diariamente en la +

    Actualmente el proyecto GNOME es muy dinámico. Es + mucho el trabajo que se realiza diariamente en la infraestructura de ports de GNOME para que las cosas - funcionen correctamente. De cualquier manera si usted usa - GNOME 1.4 y desea actualizarse a GNOME &gnomever; - debe familiarizarse con las instrucciones - oficiales - de actualización disponibles en el sitio web de GNOME. - Posteriormente asegúrese de que su colección de - ports de GNOME 1.4 está actualizada, después + funcionen correctamente. De cualquier manera si usted usa + GNOME 1.4 y desea actualizarse a GNOME &gnomever; + debe familiarizarse con las instrucciones + oficiales + de actualización disponibles en el sitio web de GNOME. + Posteriormente asegúrese de que su colección de + ports de GNOME 1.4 está actualizada, después elimine los siguiente componentes de GNOME 1.4 de su sistema:

     gnomecore
     sawfish
     gnomeapplets
     gnomemedia
     gtop
     libgtop
     nautilus
     gedit
     xalf
     bugbuddy
     gnomeaudio
     gnomegames
     gnomeutils
     gdm
     eog
     ggv
                

    Una vez que ha eliminado los paquetes listados puede proceder - a compilar GNOME &gnomever; de acuerdo a las instrucciones + a compilar GNOME &gnomever; de acuerdo a las instrucciones comentadas anteriormente.

  5. -

    ¿Cúal es la mejor forma de actualizar de +

    ¿Cúal es la mejor forma de actualizar de GNOME 2.2 a GNOME &gnomever;?

    -

    Le recomendamos usar - /usr/ports/sysutils/portupgrade. Esto hará el +

    Le recomendamos usar + /usr/ports/sysutils/portupgrade. Esto hará el trabajo sin problemas:

     # pkgdb -F
     (responda 'yes' a todas las preguntas)
     # portupgrade ORBit2 libbonobo
     # portupgrade -rf -m BATCH=yes atk
     # portupgrade -R -m BATCH=yes gnome2
                 
  6. -

    ¿Cómo mantengo mis componentes de GNOME +

    ¿Cómo mantengo mis componentes de GNOME &gnomever; y sus aplicaciones actualizadas?

    -

    Por propia experiencia /usr/ports/sysutils/portupgrade +

    Por propia experiencia /usr/ports/sysutils/portupgrade funciona muy bien. Por ejemplo:

    # portupgrade -r pkgconfig -

    actualizará pkgconfig y cualquier otro componente que +

    actualizará pkgconfig y cualquier otro componente que dependa de éste (y que requiera actualizarse).

    -

    De cualquier forma en ocasiones hay tantos cambios que es - recomendable hacer una limpieza más a fondo. Lo +

    De cualquier forma en ocasiones hay tantos cambios que es + recomendable hacer una limpieza más a fondo. Lo siguiente suele funcionar:

     # pkg_delete -rf pkgconfig\*
     # cd /usr/ports/x11/gnome2
     # make clean
     # make install clean
                 
    -

    Estos pasos eliminarán todos los componentes y - aplicaciones de GNOME 1 y 2 de su máquina pero solamente - reinstala el escritorio GNOME 2. Debe tener en cuenta que en - será necesario que reinstale todas sus - aplicaciones una vez que haya finalizado de instalar el - escritorio. Por fortuna es muy raro el tener que llegar +

    Estos pasos eliminarán todos los componentes y + aplicaciones de GNOME 1 y 2 de su máquina pero solamente + reinstala el escritorio GNOME 2. Debe tener en cuenta que en + será necesario que reinstale todas sus + aplicaciones una vez que haya finalizado de instalar el + escritorio. Por fortuna es muy raro el tener que llegar hasta esta medida extrema.

  7. ¿Puedo instalar aplicaciones de GNOME 1.4 bajo GNOME &gnomever;?

    -

    Los ports de GNOME 1.4 se ejecutan correctamente bajo el - escritorio GNOME 2. Las viejas aplicaciones que no eran - compatibles con el escritorio GNOME 2 han sido eliminadas de - la colección de ports de tal forma que es seguro el - utilizar cualquier aplicación de GNOME que esté en +

    Los ports de GNOME 1.4 se ejecutan correctamente bajo el + escritorio GNOME 2. Las viejas aplicaciones que no eran + compatibles con el escritorio GNOME 2 han sido eliminadas de + la colección de ports de tal forma que es seguro el + utilizar cualquier aplicación de GNOME que esté en la colección de ports bajo el escritorio GNOME 2.

  8. -

    ¿Dónde puedo obtener más temas para +

    ¿Dónde puedo obtener más temas para GNOME &gnomever;?

    -

    El sitio http://art.gnome.org - se ha establecido como un repositorio para temas de - GNOME. Se pueden encontrar algunos buenos temas para metacity, - sawfish, nautilus, iconos y gdm, así como algunos fondos +

    El sitio http://art.gnome.org + se ha establecido como un repositorio para temas de + GNOME. Se pueden encontrar algunos buenos temas para metacity, + sawfish, nautilus, iconos y gdm, así como algunos fondos de escritorio.

    -

    Un nuevo sitio de temas llamado - The Theme Depot ha - comenzado a funcionar. Éste sitio contiene temas para - GNOME 2 así como de KDE y unos cuantos gestores de +

    Un nuevo sitio de temas llamado + The Theme Depot ha + comenzado a funcionar. Éste sitio contiene temas para + GNOME 2 así como de KDE y unos cuantos gestores de ventanas.

    Freshmeat.net cuenta con una colección de temas en themes.freshmeat.net, - que contienen temas y fondos de escritorio para muchos - gestores de ventanas y entornos de - escritorio. Éste sitio surgió del antiguo + que contienen temas y fondos de escritorio para muchos + gestores de ventanas y entornos de + escritorio. Éste sitio surgió del antiguo themes.org.

    -

    Un buen sitio con una colección genial de iconos - (algunos nuevos, otros no) es el sitio de - iconos de +

    Un buen sitio con una colección genial de iconos + (algunos nuevos, otros no) es el sitio de + iconos de jimmac.

    -

    Consulte las instrucciones de cada sitio web para instalar los - temas. Si siente la tentación de portar unos cuantos a +

    Consulte las instrucciones de cada sitio web para instalar los + temas. Si siente la tentación de portar unos cuantos a FreeBSD adelante, nadie le va a mirar mal por eso ;-).

  9. -

    ¿Qué gestores de ventanas van bien a +

    ¿Qué gestores de ventanas van bien a GNOME &gnomever;?

    -

    El meta-port gnome2 instala por defecto el gestor de - ventanas metacity. Otro gestor de ventanas con muy buena fama - de funcionar bien bien con GNOME &gnomever; es - sawfish. Sawfish - se distribuye como parte del meta-port +

    El meta-port gnome2 instala por defecto el gestor de + ventanas metacity. Otro gestor de ventanas con muy buena fama + de funcionar bien bien con GNOME &gnomever; es + sawfish. Sawfish + se distribuye como parte del meta-port x11/gnome2-fifth-toe. -

    Para cambiar entre metacity y sawfish en GNOME 2 +

    Para cambiar entre metacity y sawfish en GNOME 2 necesitaára hacer lo siguiente:

     killall metacity; sawfish &
     gnome-session-save --gui
     
    -

    La línea gnome-session-save es importante, ya - que es la que guarda en nuestra configuración qué - gestor de ventanas es el que deseamos utilizar. Sin ella - regresaremos al gestor antíguo una vez que reingresemos - al sistema. Para cambiar de sawfish a metacity simplemente +

    La línea gnome-session-save es importante, ya + que es la que guarda en nuestra configuración qué + gestor de ventanas es el que deseamos utilizar. Sin ella + regresaremos al gestor antíguo una vez que reingresemos + al sistema. Para cambiar de sawfish a metacity simplemente invierta el comando entre metacity a sawfish.

  10. ¿Admite GNOME &gnomever; las fuentes anti-alias?

    ¡Claro! Las fuentes anti-alias requieren XFree86 - 4.x con soporte para freetype2. Para incluir soporte - freetype2 a su servidor X verifique que cuenta con el - módulo incluído en la sección - ``Modules'' de su fichero XF86Config de la + 4.x con soporte para freetype2. Para incluir soporte + freetype2 a su servidor X verifique que cuenta con el + módulo incluído en la sección + ``Modules'' de su fichero XF86Config de la siguiente forma:

     Load    "freetype"
     Load    "type1"
                     
    -

    Posteriormente sólo debe revisar el applet de - fuentes (Fonts) bajo - Aplicaciones->Preferencias de Escritorio - (Applications->Desktop Preferences). Si desea un buen - conjunto de fuentes TrueType instale el port +

    Posteriormente sólo debe revisar el applet de + fuentes (Fonts) bajo + Aplicaciones->Preferencias de Escritorio + (Applications->Desktop Preferences). Si desea un buen + conjunto de fuentes TrueType instale el port x11-fonts/webfonts.

    En ocasiones después de instalar nuevas fuentes en - el sistema es necesario notificarle a fontconfig acerca de - ellas. Si comprueba que no están disponibles - fuentes recién instaladas en su sistema (incluso - cuando ha reiniciado GNOME 2) ejecute el siguiente comando + el sistema es necesario notificarle a fontconfig acerca de + ellas. Si comprueba que no están disponibles + fuentes recién instaladas en su sistema (incluso + cuando ha reiniciado GNOME 2) ejecute el siguiente comando como root:

     # fc-cache -f -v
                     

    Si tiene alguna pregunta por favor enviela al correo &email;@FreeBSD.org

  11. -

    ¿Cómo puedo controlar qué fuentes son +

    ¿Cómo puedo controlar qué fuentes son anti-alias?

    -

    GNOME &gnomever; utiliza Xft y fontconfig para gestionar - fuentes anti-alias. Fontconfig es un paquete de +

    GNOME &gnomever; utiliza Xft y fontconfig para gestionar + fuentes anti-alias. Fontconfig es un paquete de configuración de fuentes muy potente basado en XML. - Puede usted crear un archivo ~/.fonts.conf que - controle virtualmente todos los aspectos de fontconfig. - Por ejemplo, si usted no desea contar con fuentes - anti-alias mas pequeñas de 16 puntos cree un + Puede usted crear un archivo ~/.fonts.conf que + controle virtualmente todos los aspectos de fontconfig. + Por ejemplo, si usted no desea contar con fuentes + anti-alias mas pequeñas de 16 puntos cree un archivo ~/.font.conf con el siguiente contenido:

     <?xml version="1.0"?>
     <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
     <fontconfig>
     
     <match target="font">
             <test name="size" compare="less_eq">
                     <double>16</double>
             </test>
             <edit name="antialias" mode="assign">
                     <bool>false</bool>
             </edit>
     </match>
     </fontconfig>
                     
    -

    Para mayor información consulte +

    Para mayor información consulte fonts-conf(5).

  12. ¿Cómo edito los menús de mi GNOME 2?

    -

    Debe usar Nautilus para editar los menús de GNOME 2. - Si desea editar cualquier menú diferente a Favoritos +

    Debe usar Nautilus para editar los menús de GNOME 2. + Si desea editar cualquier menú diferente a Favoritos (Favorites) deberá hacerlo como root.

    Para editar los menús ejecute Nautilus y escriba la URL - applications:///. Desde ahí podrá + applications:///. Desde ahí podrá modificar por completo el menú de aplicaciones.

  13. ¿Cómo uso y configuro los recursos de GTK+ 2 para aplicaciones GTK+ 2 cuando no me encuentro bajo GNOME?

    -

    Las aplicaciones de GNOME 2 obtienen los recursos GTK+ 2 de - los temas y su correspondiente motor de temas. Si desea - ejecutar sus aplicaciones GTK+ 2 en un entorno no-GNOME +

    Las aplicaciones de GNOME 2 obtienen los recursos GTK+ 2 de + los temas y su correspondiente motor de temas. Si desea + ejecutar sus aplicaciones GTK+ 2 en un entorno no-GNOME deberá crear un fichero llamado ~/.gtkrc-2.0.

    -

    Para usar la apariencia de un tema GTK+ 2 en un entorno - no-GNOME deberá incluír el fichero - gtk-2.0/gtkrc del tema en su fichero +

    Para usar la apariencia de un tema GTK+ 2 en un entorno + no-GNOME deberá incluír el fichero + gtk-2.0/gtkrc del tema en su fichero ~/.gtkrc-2.0. Por ejemplo:

    include "/usr/X11R6/share/themes/Crux/gtk-2.0/gtkrc"
     		    
    -

    Si lo prefiere puede usar el mismo tema de GTK+ 1.2 para - aplicaciones tanto GTK+ 1.2 como GTK+ 2.0, lo cual - dará una apariencia consistente. Para la - mayoría puede transferir su configuración +

    Si lo prefiere puede usar el mismo tema de GTK+ 1.2 para + aplicaciones tanto GTK+ 1.2 como GTK+ 2.0, lo cual + dará una apariencia consistente. Para la + mayoría puede transferir su configuración del fichero ~/.gtkrc (usado con GTK+ 1.2) con unos cuantos arreglos.

      -
    1. Si cuenta con referencias a algún motor - deberá asegurarse de que correspondan al motor del +
    2. Si cuenta con referencias a algún motor + deberá asegurarse de que correspondan al motor del tema de GTK+ 2. De lo contrario elimine las mismas.
    3. -
    4. La especificación de fuentes por defecto deben - encontrarse fuera de cualquier bloque de estilo - (style) y deben ser especificada con la palabra +
    5. La especificación de fuentes por defecto deben + encontrarse fuera de cualquier bloque de estilo + (style) y deben ser especificada con la palabra clave de fuentes gtk (gtk-font-name). Por ejemplo:
      gtk-font-name = "Verdana 11"
    -

    Recuerde que mientras que un fichero gtkrc de - GTK+ 1.2 puede funcionar con un fichero gtkrc-2.0 - de GTK+ 2.0 al contrario no es así: el - contenido de un fichero gtkrc-2.0 no - funcionará en un fichero de gtkrc de GTK+ +

    Recuerde que mientras que un fichero gtkrc de + GTK+ 1.2 puede funcionar con un fichero gtkrc-2.0 + de GTK+ 2.0 al contrario no es así: el + contenido de un fichero gtkrc-2.0 no + funcionará en un fichero de gtkrc de GTK+ 1.2

  14. ¿Cómo configuro mis aplicaciones de GNOME 1.4 bajo GNOME &gnomever;?

    -

    Instale la aplicación - sysutils/gnomecontrolcenter; después ejecute - desde la línea de comandos gnomecc; ésto - ejecutará el Centro de Control de GNOME 1.4

    +

    Instale la aplicación + sysutils/gnomecontrolcenter; después ejecute + desde la línea de comandos gnomecc; ésto + ejecutará el Centro de Control de GNOME 1.4

  15. -

    El programa para grabar CDs de Nautilus (cd-burner) no me +

    El programa para grabar CDs de Nautilus (cd-burner) no me permite quemar CDs. ¿Cómo soluciono esto?

    -

    El programa para grabar CDs de Nautilus (Nautilus-cd-burner) - no puede escribir en CD/DVD a menos que se cuente con soporte - para éstos dispositivos en el kernel y los permisos de - los nodos del dispositivo permitan acceso de escritura. El - Nautilus-cd-burner se entiende con CD/DVD por medio del - subsistema SCSI CAM. Por lo tanto debe verificar que cuenta +

    El programa para grabar CDs de Nautilus (Nautilus-cd-burner) + no puede escribir en CD/DVD a menos que se cuente con soporte + para éstos dispositivos en el kernel y los permisos de + los nodos del dispositivo permitan acceso de escritura. El + Nautilus-cd-burner se entiende con CD/DVD por medio del + subsistema SCSI CAM. Por lo tanto debe verificar que cuenta con lo siguiente en la configuración de su kernel:

     device          scbus
     device          cd
     device          pass
                 
    -

    Si dispone de un grabador de CD/DVD de tipo ATAPI - también verifique que cuenta con la siguiente - línea en el fichero de configuración de su +

    Si dispone de un grabador de CD/DVD de tipo ATAPI + también verifique que cuenta con la siguiente + línea en el fichero de configuración de su kernel:

     device          atapicam
                 
    -

    Para averiguar qué unidad de CD/DVD ser utilizada +

    Para averiguar qué unidad de CD/DVD ser utilizada ejecute el siguiente comando como root:

     # camcontrol devlist
                 

    La salida será algo similar a lo siguiente:

     <QSI CDRW/DVD SBW-242 UD22>               at scbus1 target 0 lun 0 (cd0,pass0)
                 
    -

    Los dispositivos con paréntesis al final son - importantes. Debe asegurarse de que las entradas para - éstos dispositivos bajo /dev permitan la - escritura a los usuarios que utilizarán - nautilus-cd-burner. Además los dispositivos - /dev/xpt* también deben permitir escritura a - los usuarios de nautilus-cd-burner. El siguiente fichero - /etc/devfs.conf cumplirá con los resultados - deseados (Nota: El fichero devfs.conf existe +

    Los dispositivos con paréntesis al final son + importantes. Debe asegurarse de que las entradas para + éstos dispositivos bajo /dev permitan la + escritura a los usuarios que utilizarán + nautilus-cd-burner. Además los dispositivos + /dev/xpt* también deben permitir escritura a + los usuarios de nautilus-cd-burner. El siguiente fichero + /etc/devfs.conf cumplirá con los resultados + deseados (Nota: El fichero devfs.conf existe sólamente en FreeBSD 5.x):

     perm    cd0     0666
     perm    xpt0    0666
     perm    pass0   0666
                   
    -

    En FreeBSD 4.x configure los permisos del nodo - del dispositivo y éstos se mantendran al reiniciar el - sistema. Nota: Debe usar los nodos de los dispositivos 'c' +

    En FreeBSD 4.x configure los permisos del nodo + del dispositivo y éstos se mantendran al reiniciar el + sistema. Nota: Debe usar los nodos de los dispositivos 'c' para FreeBSD 4.x (p.e. cd0c).

  16. -

    ¿Cómo incluyo una nueva opción de +

    ¿Cómo incluyo una nueva opción de acceso bajo GDM?

    -

    El proceso para incluir nuevas sesiones en GDM ha cambiado - sustancialemente entre GNOME 2.2 y GNOME &gnomever;. Ahora, para - poder incluír nuevas sesiones, deberá crear un - fichero .desktop que contenga la información de - configuración de la sesión. Los ficheros de +

    El proceso para incluir nuevas sesiones en GDM ha cambiado + sustancialemente entre GNOME 2.2 y GNOME &gnomever;. Ahora, para + poder incluír nuevas sesiones, deberá crear un + fichero .desktop que contenga la información de + configuración de la sesión. Los ficheros de sesión están en /usr/X11R6/etc/dm/Sessions. Por ejemplo, para incluír una sesión de KDE cree un - fichero llamado kde.desktop en + fichero llamado kde.desktop en /usr/X11R6/etc/gdm/Sessions que contenga lo siguiente:

     [Desktop Entry]
     Encoding=UTF-8
     Name=KDE
     Comment=This session logs you into KDE
     Exec=/usr/local/bin/startkde
     TryExec=/usr/local/bin/startkde
     Icon=
     Type=Application
                 
    -

    Este fichero debe contar con permisos de ejecución. +

    Este fichero debe contar con permisos de ejecución. Por ejemplo:

     # chmod 0555 kde.desktop
                 
    -

    Una vez que ha creado este fichero reincie GDM y - aparecerá un link a KDE bajo el menú +

    Una vez que ha creado este fichero reincie GDM y + aparecerá un link a KDE bajo el menú Sessions (Sesiones).

&footer; diff --git a/es/gnome/docs/gnome2_porting.sgml b/es/gnome/docs/gnome2_porting.sgml index d139125a8a..f318a1ca97 100644 --- a/es/gnome/docs/gnome2_porting.sgml +++ b/es/gnome/docs/gnome2_porting.sgml @@ -1,316 +1,317 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header; - +
- -
COMPONENTE PROGRAMA ASOCIADO COMPONENTES IMPLICADOS
atk devel/atk glib20
atspi x11-toolkits/at-spi gail libbonobo
eel2 x11-toolkits/eel2 gnomevfs2 libgnomeui gail
esound audio/esound  
gail x11-toolkits/gail libgnomecanvas
gal2 x11-toolkits/gal2 gnomeui libgnomeprintui
gconf2 devel/gconf2 orbit2 libxml2 gtk20 linc
glib20 devel/glib20 gnometarget pkgconfig
gnomecontrolcenter2 sysutils/gnomecontrolcenter2 gnomedesktop metacity nautilus2
gnomedesktop x11/gnomedesktop libgnomeui
gnomehack gnomehack se encarga de substituciones comunes en Makefiles de GNOME, que - casi todo port requiere para adaptarse - correctamente a la estructura. Nota: - Incluir esta opción añade un - pre-patch en el Makefile. Por tanto, - debe definir explícitamente + casi todo port requiere para adaptarse + correctamente a la estructura. Nota: + Incluir esta opción añade un + pre-patch en el Makefile. Por tanto, + debe definir explícitamente post-patch.
gnomehiergnomehier instala todos - los directorios necesarios para GNOME 1 y 2. + gnomehier instala todos + los directorios necesarios para GNOME 1 y 2. Sólo incluya esta opción si su port hace un @dirrm en uno de los directorios listados en la plist para gnomehier.
gnomepanel x11/gnomepanel libwnck gnomedesktop
gnomeprefixgnomeprefix configura - algunos argumentos (CONFIGURE_ARGS) para - asegurarse que los datos son colocados + gnomeprefix configura + algunos argumentos (CONFIGURE_ARGS) para + asegurarse que los datos son colocados correctamente dentro de la jerarquía GNOME.
gnometarget gnometarget configura la - variable CONFIGURE_TARGET a + variable CONFIGURE_TARGET a --build=${MACHINE_ARCH}-portbld-freebsd${OSREL}.
gnomevfs2 devel/gnomevfs2 gconf2 libbonobo gnomemimedata
gtk20 x11-toolkits/gtk20 atk pango
gtksourceview x11-toolkits/gtksourceview libgnome libgnomeprintui
libartlgpl2 graphics/libartlgpl2 pkgconfig
libbonobo devel/libbonobo libxml2 orbit2
libbonoboui x11-toolkits/libbonoboui libgnomecanvas libgnome
libgailgnome x11-toolkits/libgail-gnome libgnomeui atspi
libgda2 databases/libgda2 glib20 libxslt
libglade2 devel/libglade2 libxml2 gtk20
libgnome x11/libgnome libxslt gnomevfs2 esound
libgnomeui x11-toolkits/libgnomeui libbonoboui
libgnomecanvas graphics/libgnomecanvas libglade2 libartlgpl2
libgnomedb databases/libgnomedb libgnomeui libgda2
libgnomeprint print/libgnomeprint libbonobo libartlgpl2 gtk20
libgnomeprintui x11-toolkits/libgnomeprintui libgnomeprint libgnomecanvas
libgsf devel/libgsf gnomevfs2 libbonobo
libgtkhtml www/libgtkhtml libxslt gnomevfs2 gail
libidl devel/libIDL glib20
libwnck x11-toolkits/libwnck gtk20
librsvg2 graphics/librsvg2 gtk20 libgsf
libxml2 textproc/libxml2 pkgconfig
libxslt textproc/libxslt libxml2
libzvt x11-toolkits/libzvt gtk20
linc net/linc glib20
nautilus2 x11-fm/nautilus librsvg2 eel2 gnomedesktop
metacity x11-wm/metacity gconf2 glade2
orbit2 devel/ORBit2 libidl
pango x11-toolkits/pango glib20
pkgconfig devel/pkgconfig  
vte x11-toolkits/vte gtk20
-

Si aún necesita ayuda con sus ports, tome algunos de los - ports existentes como ejemplo. - También cuenta con la - lista de correo +

Si aún necesita ayuda con sus ports, tome algunos de los + ports existentes como ejemplo. + También cuenta con la + lista de correo freebsd-gnome para apoyarlo.

> &footer; diff --git a/es/gnome/docs/gnome_porting.sgml b/es/gnome/docs/gnome_porting.sgml index 83f2bd8a61..e9121fcc04 100644 --- a/es/gnome/docs/gnome_porting.sgml +++ b/es/gnome/docs/gnome_porting.sgml @@ -1,199 +1,200 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header; - +
- -
COMPONENTE PROGRAMA ASOCIADO COMPONENTES IMPLICADOS
bonobo devel/bonobo oaf gnomeprint
esound audio/esound  
gal x11-toolkits/gal libglade
gconf devel/gconf oaf
gdkpixbuf graphics/gdk-pixbuf gtk12
glib12 devel/glib12 pkgconfig
glibwww www/glibwww gnomelibs
gnomecanvas graphics/gnomecanvas gnomelibs gdkpixbuf
gnomedb databases/gnomedb libgda
gnomehackgnomehack se encarga de + gnomehack se encarga de substituciones comunes en Makefiles de GNOME, que - casi todo port requiere para adaptarse - correctamente a la estructura. Nota: - Incluir esta opción añade un - pre-patch en el Makefile. Por tanto, + casi todo port requiere para adaptarse + correctamente a la estructura. Nota: + Incluir esta opción añade un + pre-patch en el Makefile. Por tanto, definir explícitamente post-patch.
gnomehier gnomehier instala todos los - directorios necesarios para GNOME 1 y 2. + directorios necesarios para GNOME 1 y 2. Sólo incluya esta opción si su port hace un @dirrm en uno de los directorios listados en la plist para gnomehier.
gnomelibs x11/gnomelibs esound imlib libxml orbit
gnomemimedata misc/gnomemimedata gnomehier pkgconfig
gnomeprefixgnomeprefix configura - algunos argumentos (CONFIGURE_ARGS) para - asegurarse que los datos son colocados + gnomeprefix configura + algunos argumentos (CONFIGURE_ARGS) para + asegurarse que los datos son colocados correctamente dentro de la jerarquía GNOME.
gnomeprint print/gnomeprint gnomelibs gnomecanvas
gnomevfs devel/gnomevfs gnomemimedata gconf gnomelibs
gtk12 x11-toolkits/gtk12 glib12
gtkhtml www/gtkhtml glibwww gal libghttp libcapplet
imlib graphics/imlib gtk12
libcapplet x11/libcapplet gnomelibs
libgda databases/libgda gconf bonobo
libghttp www/libghttp  
libglade devel/libglade gnomedb
libxml textproc/libxml glib12
oaf devel/oaf orbit libxml
orbit devel/ORBit glib12
-

Si aún necesita ayuda con sus ports, tome algunos de los - ports existentes como ejemplo. - También cuenta con la - lista de correo de +

Si aún necesita ayuda con sus ports, tome algunos de los + ports existentes como ejemplo. + También cuenta con la + lista de correo de freebsd-gnome para apoyarlo.

&footer; diff --git a/es/gnome/docs/knownissues.sgml b/es/gnome/docs/knownissues.sgml index 42eb41598e..96527ea08d 100644 --- a/es/gnome/docs/knownissues.sgml +++ b/es/gnome/docs/knownissues.sgml @@ -1,79 +1,80 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header; -

En la parte inferior encontrar una lista de problemas conocidos - con GNOME &gnomever;, que son específicos de FreeBSD. +

En la parte inferior encontrar una lista de problemas conocidos + con GNOME &gnomever;, que son específicos de FreeBSD. Aunque estos no son todos los problemas conocidos. Por favor lea - las - notas de lanzamiento, - las cuales contienen una - lista + las + notas de lanzamiento, + las cuales contienen una + lista de problemas conocidos, que afectan a todas las plataformas.

1. Actualizando de GNOME 2.2 a &gnomever; es laborioso

Para efecto de actualizar a GNOME &gnomever;, debe seguir las - instrucciones - indicadas. Aunque aún esto puede producir errores. - Puede ser que sea necesario que ejecute pkgdb -F - después de cada paso. Si se continúan - presentando errores una vez que ha seguido las instrucciones - dadas, cree un archivo de registro (log) de todo el - procedimiento (puede usar la opción -l de - portupgrade para hacer esto). Comprimalo y - envíe el archivo a + instrucciones + indicadas. Aunque aún esto puede producir errores. + Puede ser que sea necesario que ejecute pkgdb -F + después de cada paso. Si se continúan + presentando errores una vez que ha seguido las instrucciones + dadas, cree un archivo de registro (log) de todo el + procedimiento (puede usar la opción -l de + portupgrade para hacer esto). Comprimalo y + envíe el archivo a &email;@FreeBSD.org.

2. Evolution presenta un error con archivos adjuntos bajo GNOME &gnomever;

evolution-1.4.4 tiene un problema con archivos adjuntos bajo - GNOME &gnomever;. Para solucionar este problema, haga lo + GNOME &gnomever;. Para solucionar este problema, haga lo siguiente, como root:

 # ln -s /usr/X11R6/share/icons/gnome/48x48/apps/gnome-unknown.png /usr/X11R6/share/gnome/pixmaps/gnome-unknown.png
 

Este problema fu resuelto en evolution-1.4.5, y actualizarse a evolution-1.4.5 es probablemente la mejor solución.

3. gstreamer no funciona bien con rhythmbox

-

gstreamer no funciona bien con rhythmbox. Por ahora, es - recomendable que compile rhythmbox con la opción - -DWITH_XINE. (ACTUALIZACION: Desde +

gstreamer no funciona bien con rhythmbox. Por ahora, es + recomendable que compile rhythmbox con la opción + -DWITH_XINE. (ACTUALIZACION: Desde gstreamer-plugins-0.6.3_1, este problema se ha resulto)

4. GDM se congela al inciar

-

Puede ser que GDM se congele al inicar, especialmente en - 5.1-RELEASE y anteriores. Todos los usuarios de GDM deben - copiar /usr/X11R6/etc/gdm/factory-gdm.conf sobre - /usr/X11R6/etc/gdm/gdm.conf. La antigua - versión de configuración de GNOME 2.2 no - funcionará. Usuarios de 5.1-RELEASE y anteriores - deberán leer el pkg-message que viene con el +

Puede ser que GDM se congele al inicar, especialmente en + 5.1-RELEASE y anteriores. Todos los usuarios de GDM deben + copiar /usr/X11R6/etc/gdm/factory-gdm.conf sobre + /usr/X11R6/etc/gdm/gdm.conf. La antigua + versión de configuración de GNOME 2.2 no + funcionará. Usuarios de 5.1-RELEASE y anteriores + deberán leer el pkg-message que viene con el port/paquete de GDM2, y que explica como aplicar el parche para que OpenPAM funcione con GDM2.

5. gnomemeeting falla en compilar

Gnomemeeting puede fallar en compilar si cuenta con el paquete - ffmepg instalado. Si es así, elimine ffmpeg, compile + ffmepg instalado. Si es así, elimine ffmpeg, compile gnomemeeting y posteriormente reinstale ffmpeg si lo desea.

&footer; diff --git a/es/gnome/docs/porting.sgml b/es/gnome/docs/porting.sgml index 5b5183d97d..e72e352acc 100755 --- a/es/gnome/docs/porting.sgml +++ b/es/gnome/docs/porting.sgml @@ -1,329 +1,330 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header; -

El presente documento asume que usted ya tiene conocimiento de - la forma de trabajar del sistema de ports, y por lo tanto solo - provee de algunos consejos específicos sobre GNOME. Las +

El presente documento asume que usted ya tiene conocimiento de + la forma de trabajar del sistema de ports, y por lo tanto solo + provee de algunos consejos específicos sobre GNOME. Las instrucciones generales pueden encontrarse en el manual FreeBSD Porter's Handbook.

Macros de Makefile de GNOME

-

Las aplicaciones de GNOME bajo FreeBSD utilizan la - infraestructura USE_GNOME. Para indicar qué - componentes de GNOME son necesarios para que su port compile; +

Las aplicaciones de GNOME bajo FreeBSD utilizan la + infraestructura USE_GNOME. Para indicar qué + componentes de GNOME son necesarios para que su port compile; simplemente lístelos con un espacio de separación. Por ejemplo:

 USE_X_PREFIX=   yes
 USE_GNOME=      gnomeprefix gnomehack libgnomeui
           
-

Los componentes de USE_GNOME son divididos en las +

Los componentes de USE_GNOME son divididos en las siguientes dos listas:

-

Si su port, solamente necesita las librerías de - GTK2, la siguiente forma es la más sencilla de +

Si su port, solamente necesita las librerías de + GTK2, la siguiente forma es la más sencilla de definir esto:

 USE_X_PREFIX=   yes
 USE_GNOME=      gtk20
           
-

Si su port, solamente necesita las librerías de - GTK1, la siguiente forma es la más sencilla de +

Si su port, solamente necesita las librerías de + GTK1, la siguiente forma es la más sencilla de definirlo:

 USE_X_PREFIX=   yes
 USE_GNOME=      gtk12
           

Aún en el caso de que su port, solamente necesite las - librerías GTK, algunos otros componentes de + librerías GTK, algunos otros componentes de USE_GNOME le pueden ser de utilidad. Por favor vea la - lista completa, para asegurarse que su port cuenta con todos + lista completa, para asegurarse que su port cuenta con todos los componentes necesarios.

Una vez que haya terminado con su port, es recomendable verificar - que la lista de componentes de los cuales depende su port sea la - correcta. Para ver una lista completa de los paquetes que su - port requiere, puede ejecutar el comando + que la lista de componentes de los cuales depende su port sea la + correcta. Para ver una lista completa de los paquetes que su + port requiere, puede ejecutar el comando make package-depends desde el directorio de su port.

-

Para apoyarse en la creación de la lista de componentes - necesarios, puede ser de utilidad examinar el resultado del - comando make configure. Al final de dicha salida, - verá una línea con checking for..., y una +

Para apoyarse en la creación de la lista de componentes + necesarios, puede ser de utilidad examinar el resultado del + comando make configure. Al final de dicha salida, + verá una línea con checking for..., y una lista similar a la siguiente:

 checking for    libgnomeui-2.0 >= 2.0.0         cspi-1.0 >= 1.1.7
 libspi-1.0 >= 1.1.7             libbonobo-2.0 >= 2.0.0  atk >= 1.0.0
 gtk+-2.0 >= 2.0.0       gail    libwnck-1.0             esound... yes
 
-

Esta es una lista de los componentes de los cuales depende su - aplicación para poder compilar. Preste atención a - la jerarquización del sistema USE_GNOME; muchos - componentes pueden estar implicados por las directivas de - USE_GNOME. En el ejemplo anterior - USE_GNOME= libgnomeui, implica el uso de - libbonoboui, lo cual implica el uso de - libgnomecanvas, que a su vez implica el uso de - libglade2, el cual implica a gtk20. Por lo - que, aún cuando gtk+-2.0 aparece en la lista de - componentes necesarios, gtk20 puede ser eliminado de la - lista de USE_GNOME. Existe cierto número de +

Esta es una lista de los componentes de los cuales depende su + aplicación para poder compilar. Preste atención a + la jerarquización del sistema USE_GNOME; muchos + componentes pueden estar implicados por las directivas de + USE_GNOME. En el ejemplo anterior + USE_GNOME= libgnomeui, implica el uso de + libbonoboui, lo cual implica el uso de + libgnomecanvas, que a su vez implica el uso de + libglade2, el cual implica a gtk20. Por lo + que, aún cuando gtk+-2.0 aparece en la lista de + componentes necesarios, gtk20 puede ser eliminado de la + lista de USE_GNOME. Existe cierto número de redundancias similares que pueden ser eliminadas de la lista.

-

Para la lista anterior (tomado de sysutils/gok), lo +

Para la lista anterior (tomado de sysutils/gok), lo siguiente es definido en el fichero Makefile:

 USE_GNOME=      gnomehack gnomeprefix libgnomeui atspi libwnck
 

Escritorio GNOME 1 vs. Escritorio GNOME 2

-

En el principio, solo era GNOME 1. Cuando - surgió el escritorio GNOME 2, se buscó +

En el principio, solo era GNOME 1. Cuando + surgió el escritorio GNOME 2, se buscó asegurar la máxima compatibilidad con el pasado. Buscando - que las aplicaciones de GNOME 1 se ejecuten - correctamente bajo GNOME 2, considerando que las - aplicaciones no hagan uso de funcionalidades específicas + que las aplicaciones de GNOME 1 se ejecuten + correctamente bajo GNOME 2, considerando que las + aplicaciones no hagan uso de funcionalidades específicas del entorno de GNOME 1.

El escritorio GNOME 1, y todas las aplicaciones que no se ejecutan correctamente bajo GNOME 2, se han eliminado del árbol de ports.

Lo que esto significa para usted, como migrador de aplicaciones, - simplemente es que; no debe añadir aplicaciones + simplemente es que; no debe añadir aplicaciones específicas de GNOME 1 al árbol de ports.

-

Si desea determinar que versión del escritorio GNOME - tiene instalado un usuario en su maquina, puede verificar el - valor de la variable GNOME_DESKTOP_VERSION. Este valor - será de "1" o "2", dependiendo si se +

Si desea determinar que versión del escritorio GNOME + tiene instalado un usuario en su maquina, puede verificar el + valor de la variable GNOME_DESKTOP_VERSION. Este valor + será de "1" o "2", dependiendo si se tiene instalado el escritorio GNOME 1 o GNOME 2 .

Dependencias Opcionales en GNOME

-

Si su ports puede usar GNOME opcionalmente, entonces - deberá definir en el fichero Makefile +

Si su ports puede usar GNOME opcionalmente, entonces + deberá definir en el fichero Makefile WANT_GNOME= yes, y posteriormente verificar en todos los componentes que su port vaya a utilizar para ver si se cuenta con - HAVE_GNOME. En virtud de que esta última - declaración, es una evaluación condicional, - deberá ser incluida entre la línea - bsd.port.pre.mk y bsd.port.post.mk. Por + HAVE_GNOME. En virtud de que esta última + declaración, es una evaluación condicional, + deberá ser incluida entre la línea + bsd.port.pre.mk y bsd.port.post.mk. Por ejemplo:

 WANT_GNOME=     yes
 
 .include <bsd.port.pre.mk>
 
 .if ${HAVE_GNOME:Mgnomepanel}!=""
         USE_GNOME+=     gnomeprefix gnomepanel
         CONFIGURE_ARGS+=        --with-gnome
         PKGNAMESUFFIX=  -gnome
         PLIST_SUB=      DATADIR="share/gnome"
 .else
         CONFIGURE_ARGS+=        --without-gnome
         PLIST_SUB=      DATADIR="share"
 .endif
 
 .include <bsd.port.post.mk>
           
-

En este caso, WANT_GNOME le indica al sistema de ports - que debe checar la existencia de los componentes de GNOME - listados. Para cada componente que se encuentre, su nombre - será incluido en HAVE_GNOME. Dado que este port - puede usar gnomepanel, utilizamos HAVE_GNOME - para validar si contiene gnomepanel (para más - información con respecto a la sintáxis del - patrón de make :M, por favor consulte la +

En este caso, WANT_GNOME le indica al sistema de ports + que debe checar la existencia de los componentes de GNOME + listados. Para cada componente que se encuentre, su nombre + será incluido en HAVE_GNOME. Dado que este port + puede usar gnomepanel, utilizamos HAVE_GNOME + para validar si contiene gnomepanel (para más + información con respecto a la sintáxis del + patrón de make :M, por favor consulte la página de ayuda make(1)) . Si se localiza gnomepanel, entonces es incluido en la - lista de dependencias de USE_GNOME, y le son pasados - argumentos de configuración específicos del port, - del tipo --with-gnome a CONFIGURE_ARG. En la - infraestructura del antiguo GNOME, PKGNAMESUFFIX se - ajustaba automaticamente, con el uso apropiado del macro + lista de dependencias de USE_GNOME, y le son pasados + argumentos de configuración específicos del port, + del tipo --with-gnome a CONFIGURE_ARG. En la + infraestructura del antiguo GNOME, PKGNAMESUFFIX se + ajustaba automaticamente, con el uso apropiado del macro USE_*. Ahora esto depende de cada responsable del port. - En nuestro port de ejemplo, se le incluye -gnome al - nombre del port, para indicar que ha sido compilado con soporte - para GNOME. Lo mismo aplica para DATADIR - PLIST_SUB. El responsable del port deberá + En nuestro port de ejemplo, se le incluye -gnome al + nombre del port, para indicar que ha sido compilado con soporte + para GNOME. Lo mismo aplica para DATADIR + PLIST_SUB. El responsable del port deberá decidir cuando realizar la sustitución de DATADIR - . Una buena referencia es incluir el DATADIR - PLIST_SUB cuando se utilice el componente + . Una buena referencia es incluir el DATADIR + PLIST_SUB cuando se utilice el componente gnomeprefix.

-

Nota: Usted no puede incluir componentes extras en - USE_GNOME después de la línea - .include <bsd.port.pre.mk>. Por lo que, lo +

Nota: Usted no puede incluir componentes extras en + USE_GNOME después de la línea + .include <bsd.port.pre.mk>. Por lo que, lo siguiente es incorrecto:

 .include <bsd.port.pre.mk>
 
 .if ${HAVE_GNOME:Mgnomelibs}!=""
         USE_GNOME+=     libgnome
 .else
         USE_GNOME+=     gtk12   # !INCORRECTO!
 .endif
           

Esto hará pensar al sistema que GNOME es deseado, - y marcará el pkg-plist de acuerdo a esto, por lo - que fallará la compilación. Si necesita incluir - componentes adicionales a USE_GNOME, hagalo por - arriba de la línea + y marcará el pkg-plist de acuerdo a esto, por lo + que fallará la compilación. Si necesita incluir + componentes adicionales a USE_GNOME, hagalo por + arriba de la línea .include <bsd.port.pre.mk>.

-

Para forzar el uso opcional de dependencias incondicionales de - GNOME, puede incluir en su fichero /etc/make.conf la - línea WITH_GNOME= yes o bien directamente en la - línea de comandos. Esto siempre dará un resultado - verdadero cuando se verifique por dependencias opcionales de +

Para forzar el uso opcional de dependencias incondicionales de + GNOME, puede incluir en su fichero /etc/make.conf la + línea WITH_GNOME= yes o bien directamente en la + línea de comandos. Esto siempre dará un resultado + verdadero cuando se verifique por dependencias opcionales de GNOME. Si desea que el sistema siempre dé un resultado de - falso cuando se verifiquen las dependencias opcionales de GNOME, - puede incluir la línea WITHOUT_GNOME= yes al - fichero /etc/make.conf o bien hacerlo desde la + falso cuando se verifiquen las dependencias opcionales de GNOME, + puede incluir la línea WITHOUT_GNOME= yes al + fichero /etc/make.conf o bien hacerlo desde la línea de comandos.

-

Puede encontrar más información en el uso de la - infraestructura USE_GNOME al mirar el código y los - comentarios que se incluyen en +

Puede encontrar más información en el uso de la + infraestructura USE_GNOME al mirar el código y los + comentarios que se incluyen en ${PORTSDIR}/Mk/bsd.gnome.mk.

Instalación OMF

-

Gran cantidad de aplicaciones de GNOME (especialmente +

Gran cantidad de aplicaciones de GNOME (especialmente aplicaciones de GNOME 2) instalan ficheros de OMF (por las siglas en inglés; OpenSource Metadata Framework) que contienen la - información de los ficheros de ayuda para dichas - aplicaciones. Estos ficheros OMF requieren de un tratamiento - especial por parte de ScrollKeeper para que aplicaciones como - Yelp puedan localizar la documentación de ayuda. Para + información de los ficheros de ayuda para dichas + aplicaciones. Estos ficheros OMF requieren de un tratamiento + especial por parte de ScrollKeeper para que aplicaciones como + Yelp puedan localizar la documentación de ayuda. Para efecto de que se realice un registro exitoso de los ficheros OMF, - al instalar aplicaciones de GNOME desde paquetes, deberá - asegurarse que el pkg-plist de su port cuente con lo + al instalar aplicaciones de GNOME desde paquetes, deberá + asegurarse que el pkg-plist de su port cuente con lo siguiente para cada fichero OMF listado.

 @exec scrollkeeper-install -q \
         %D/ruta/al/fichero/help_file.omf \
         2>/dev/null || /usr/bin/true
 @unexec scrollkeeper-uninstall -q \
         %D/ruta/al/fichero/help_file.omf \
         2>/dev/null || /usr/bin/true
             

Por ejemplo:

 @exec scrollkeeper-install -q \
         %D/share/gnome/bug-buddy/bug-buddy-C.omf \
         2>/dev/null || /usr/bin/true
 @unexec scrollkeeper-uninstall -q \
         %D/share/gnome/bug-buddy/bug-buddy-C.omf \
         2>/dev/null || /usr/bin/true
             

Problemas con Libtool

-

La mayoría (si no es que todas), de las aplicaciones de +

La mayoría (si no es que todas), de las aplicaciones de GNOME, dependen del programa de la GNU libtool. Así mismo - utilizan el sistema de configuración de GNU. Si su port + utilizan el sistema de configuración de GNU. Si su port instala librerías compartidas, deberá añadir - al fichero Makefile del port la línea - USE_LIBTOOL= yes. Esto se encargará de cubrir - casi todos los requisitos de libtool, pero no - prevendrá cosas como la instalación de ficheros de - tipo .la. Para asegurarse de una instalación exitosa de - las librerías compartidas, también considere + al fichero Makefile del port la línea + USE_LIBTOOL= yes. Esto se encargará de cubrir + casi todos los requisitos de libtool, pero no + prevendrá cosas como la instalación de ficheros de + tipo .la. Para asegurarse de una instalación exitosa de + las librerías compartidas, también considere incluir la siguiente línea al script configure de - su port, directamente abajo de la línea + su port, directamente abajo de la línea LIBTOOL_DEPS="$ac_aux_dir/ltmain.sh":

 $ac_aux_dir/ltconfig $LIBTOOL_DEPS
             

Esto previene la instalación misma del fichero .la y se - asegura que la variable ${PTHREAD_LIBS} sea pasada + asegura que la variable ${PTHREAD_LIBS} sea pasada correctamente el enlazador (linker).

Distfiles

Para separar los ficheros distfiles de GNOME 2 con los distfiles de GNOME 1, y para mantener el directorio distfiles lo más limpio posible, los ports de GNOME 1 que descarguen sus distfiles - desde ${MASTER_SITE_GNOME} deberán incluir lo + desde ${MASTER_SITE_GNOME} deberán incluir lo siguiente en el fichero Makefile:

 DIST_SUBDIR=    gnome
           
-

Los ports de GNOME 2 que descarguen los ficheros distfiles desde - ${MASTER_SITE_GNOME} deberán incluir la siguiente +

Los ports de GNOME 2 que descarguen los ficheros distfiles desde + ${MASTER_SITE_GNOME} deberán incluir la siguiente línea en el fichero Makefile:

 DIST_SUBDIR=    gnome2
           
-

Algunos ficheros distfiles de GNOME se pueden encontrar - comprimidos con formato tar gzip o bien como tar bzip2. Para - ahorrar tiempo de descarga en enlaces lentos, deberá usar - el formato bzip2 cuando le sea posible. Para hacer esto incluya +

Algunos ficheros distfiles de GNOME se pueden encontrar + comprimidos con formato tar gzip o bien como tar bzip2. Para + ahorrar tiempo de descarga en enlaces lentos, deberá usar + el formato bzip2 cuando le sea posible. Para hacer esto incluya la siguiente línea en el fichero Makefile de su port:

 USE_BZIP2=  yes
           
-

Si aún requiere de algo de ayuda con su port, vea alguno - de los ports existentes como - ejemplo. Además la lista de correo - freebsd-gnome siempre +

Si aún requiere de algo de ayuda con su port, vea alguno + de los ports existentes como + ejemplo. Además la lista de correo + freebsd-gnome siempre está disponible para usted.

&footer; diff --git a/es/gnome/docs/volunteer.sgml b/es/gnome/docs/volunteer.sgml index b24e981db4..6b9dbd5f06 100755 --- a/es/gnome/docs/volunteer.sgml +++ b/es/gnome/docs/volunteer.sgml @@ -1,47 +1,48 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header; -

Siempre existe algo por hacer en el campamento FreeBSD GNOME. +

Siempre existe algo por hacer en el campamento FreeBSD GNOME. Tome algo que sea de su interes y comience a ayudarnos.

  • Pruebe ports existentes, y reporte fallos.

  • Instale regularmente GNOME desde paquetes, y reporte cualquier problema con la instalación y/o funcionalidad.

  • -

    Encuentre aplicaciones de GNOME que no han sido migradas +

    Encuentre aplicaciones de GNOME que no han sido migradas aún, y trabaje en su migración.

  • -

    Suscribase - a la lista de correo de freebsd-gnome, y apóyenos +

    Suscribase + a la lista de correo de freebsd-gnome, y apóyenos respondiendo preguntas a otros usuarios.

  • Retroalimente a los autores de GNOME acerca de parches usados - bajo FreeBSD por medio de PR, de tal forma que estos puedan - ser integrados en versiones siguientes de la + bajo FreeBSD por medio de PR, de tal forma que estos puedan + ser integrados en versiones siguientes de la aplicación.

  • Lea detenidamente las paginas del proyecto FreeBSD GNOME, para retroalimentar y actualizar su contenido.

-

Envie cualquier comentario a +

Envie cualquier comentario a &email;@FreeBSD.org.

&footer; diff --git a/es/gnome/newsflash.xsl b/es/gnome/newsflash.xsl index f784d57962..d1feba67fc 100755 --- a/es/gnome/newsflash.xsl +++ b/es/gnome/newsflash.xsl @@ -1,105 +1,125 @@ - + - + - - - - + + + +
+
+ + + +
+ + + +
+ + - Noticias FreeBSD GNOME - + +
+
+ +
+ + + +
+
+

  • , :

  • diff --git a/es/gnome/screenshots.sgml b/es/gnome/screenshots.sgml index 989c5e8a66..9b21ee8a04 100755 --- a/es/gnome/screenshots.sgml +++ b/es/gnome/screenshots.sgml @@ -1,38 +1,39 @@ - - + + %navincludes; %gnomeincludes; %includes; ]> &header; -

    He aqui algunos ejemplos de GNOME corriendo bajo FreeBSD. Pulse +

    He aqui algunos ejemplos de GNOME corriendo bajo FreeBSD. Pulse sobre las imágenes para verlas en tamaño natural.

    Tomas de Pantalla de GNOME 2.4

    -

    Pantalla dual con resolución 2048x768 mostrando el - navegador Epiphany y el nuevo Themus y vista del quemador +

    Pantalla dual con resolución 2048x768 mostrando el + navegador Epiphany y el nuevo Themus y vista del quemador (CD-Burner) de Nautilus:
    Screen Shot 11

    Opera, GVim con soporte GTK+-2 y GDesklets, todo con el tema de íconos crystal:
    Screen Shot 12

    -

    Xchat, Xmms, StickyNotes y GKrellM con el tema de metacity +

    Xchat, Xmms, StickyNotes y GKrellM con el tema de metacity Koynacity-Blue, Aquativo 1.5 GTK, y tema de íconos Flat blue:
    Screen Shot 13

    &footer; diff --git a/es/includes.navabout.sgml b/es/includes.navabout.sgml new file mode 100644 index 0000000000..18262f2ae5 --- /dev/null +++ b/es/includes.navabout.sgml @@ -0,0 +1,19 @@ + + + +

    Section Navigation

    + + '> \ No newline at end of file diff --git a/es/includes.navcommunity.sgml b/es/includes.navcommunity.sgml new file mode 100644 index 0000000000..fe00a55543 --- /dev/null +++ b/es/includes.navcommunity.sgml @@ -0,0 +1,13 @@ + + + +

    Section Navigation

    + + '> \ No newline at end of file diff --git a/es/includes.navdevelopers.sgml b/es/includes.navdevelopers.sgml new file mode 100644 index 0000000000..6e304acd90 --- /dev/null +++ b/es/includes.navdevelopers.sgml @@ -0,0 +1,23 @@ + + + +

    Section Navigation

    + + '> \ No newline at end of file diff --git a/es/includes.navdocs.sgml b/es/includes.navdocs.sgml new file mode 100644 index 0000000000..b71c6bf1d5 --- /dev/null +++ b/es/includes.navdocs.sgml @@ -0,0 +1,20 @@ + + + +

    Section Navigation

    + + '> \ No newline at end of file diff --git a/es/includes.navdownload.sgml b/es/includes.navdownload.sgml new file mode 100644 index 0000000000..e6c9b40fcf --- /dev/null +++ b/es/includes.navdownload.sgml @@ -0,0 +1,16 @@ + + + +

    Section Navigation

    + + '> \ No newline at end of file diff --git a/es/includes.navsupport.sgml b/es/includes.navsupport.sgml new file mode 100644 index 0000000000..950af53286 --- /dev/null +++ b/es/includes.navsupport.sgml @@ -0,0 +1,24 @@ + + + +

    Section Navigation

    + + '> \ No newline at end of file diff --git a/es/includes.sgml b/es/includes.sgml index 83af530fa0..12a582f529 100644 --- a/es/includes.sgml +++ b/es/includes.sgml @@ -1,104 +1,185 @@ - - + + '> '> &email@FreeBSD.ORG
    ©right;'> FreeBSD Home Page'> + + + &title; -Navigation Bar -

    &title;


    - - - -Top -Aplicaciones -Soporte -Documentacion -Comercial -Buscar -Indice -Top -Top -'> - - -
    &author;
    &date;
    '> + + + + + + + + +
    +
    + Skip site navigation (1) + Skip section navigation (2) +
    + + + +

    Site Navigation

    +
    + +
    +
    + +
    +
    +&nav; +
    + +
    + +

    &title;

    '> + + +
    + +
    + + +
    +
    '> - - + + This document describe how to build and update the FreeBSD Web pages from the CVS repository by hand.

    '> - + + +%includes.global; + +--> diff --git a/es/includes.xsl b/es/includes.xsl index 4b75461e4c..a782c760e9 100644 --- a/es/includes.xsl +++ b/es/includes.xsl @@ -1,174 +1,267 @@ - + [New!] Copyright © 1995-2004 the FreeBSD Project. Todos los derechos reservados. @FreeBSD.org
    FreeBSD Home Page + + - - <xsl:value-of select="$title"/> - - - - + <xsl:value-of select="$title"/> + + + + + + + + - + - Navigation Bar - -

    - -
    - - - Home - Aplicaciones - Soporte - Documentació - Vendors - Buscar - Index - Top - Top - + Skip site navigation (1) + Skip section navigation (2) +
    + + + +

    Site Navigation

    +
    + +
    +
    +
    + + +

    + + + + + + + + /releases/R/relnotes.html /releases/R/announce.html /releases/R/errata.html /releases/R/hardware.html /releases/R/installation.html /releases/R/migration-guide.html /releases/R/early-adopter.html /releases/R/relnotes.html /releases/R/announce.html /releases/R/errata.html /releases/R/hardware.html
    diff --git a/es/index.sgml b/es/index.sgml index bc5e4fe639..a24a3860c3 100644 --- a/es/index.sgml +++ b/es/index.sgml @@ -1,448 +1,448 @@ - - + %includes; ]> El Proyecto FreeBSD - + - + - +
    FreeBSD: The Power to Serve
    - +
    - - Selecciona el servidor más + + Selecciona el servidor más cercano - +
    - + - + - +
    Idioma: Inglés, Japonés, Otros
    - +
    - + - + - +
        
    - +
    Release actual: &rel.current;
    » Anuncio
    » Guía de Instalación
    » Notas de la release
    » Errata
    - +
    - +

    ¿Qué es FreeBSD?

    - -

    FreeBSD es un avanzado sistema operativo para arquitecturas - x86, AMD64, DEC Alpha, IA-64, PC-98 y UltraSPARC®. - FreeBSD es un derivado de BSD UNIX, la versión de UNIX + +

    FreeBSD es un avanzado sistema operativo para arquitecturas + x86, AMD64, DEC Alpha, IA-64, PC-98 y UltraSPARC®. + FreeBSD es un derivado de BSD UNIX, la versión de UNIX desarrollada en la Universidad de California, Berkeley. FreeBSD - es desarrollado y mantenido por un + es desarrollado y mantenido por un - numeroso equipo de personas. El soporte para otras - arquitecturas + numeroso equipo de personas. El soporte para otras + arquitecturas está en diferentes fases de desarrollo.

    - +

    Características principales

    - +

    FreeBSD ofrece muy altas prestaciones en comunicaciones en red, rendimiento, seguridad y compatibilidad, todavía inexistentes en otros sistemas operativos, incluyendo los comerciales de mayor renombre.

    - +

    Potentes Soluciones Internet

    FreeBSD es el servidor ideal para servicios de Internet o Intranet. Proporciona unos servicios de red robustos, incluso en situaciones de alta carga, haciendo un uso eficaz de la memoria para mantener buenos tiempos de respuesta con cientos o miles de procesos simultáneos de usuarios. Visita nuestra galería para ver ejemplos de aplicaciones y servicios ofrecidos por FreeBSD.

    - +

    Ejecuta una gran variedad de aplicaciones

    - +

    La calidad de FreeBSD combinada con el hoy en día bajo coste del hardware de alta velocidad para PC's hace de este sistema una alternativa muy económica sobre las estaciones de trabajo UNIX comerciales. Existe gran cantidad de aplicaciones tanto a nivel servidor como usuario.

    - +

    Fácil de instalar

    - +

    Se puede instalar FreeBSD desde una gran variedad de soportes, - incluyendo CD-ROM, DVD-ROM, disquetes, cintas magnéticas, una + incluyendo CD-ROM, DVD-ROM, disquetes, cintas magnéticas, una partición MS-DOS o, si se dispone de conexión de red, se puede instalar directamente mediante FTP anónimo o NFS. Todo lo necesario son dos discos de 1.44MB de arranque y estas instrucciones.

    FreeBSD es libre y gratuito

    - + - +

    Si esperabas que un sistema operativo con estas características tuviese un alto coste, FreeBSD está - disponible totalmente + disponible totalmente gratis incluyendo todo el código fuente. Si quieres probarlo, aquí tienes más información.

    Contribuyendo a FreeBSD

    Es muy fácil contribuir a FreeBSD. Todo lo que tienes que hacer es encontrar una parte de FreeBSD que creas puede mejorarse y hacer los cambios (cuidadosa y limpiamente) y enviarlas al proyecto mediante un "send-pr" o un comitter, si conoces a alguno. Más información en la - sección + sección de contribuciones del manual.

    Aún no siendo programador, existen otros métodos de colaborar - y contribuir a FreeBSD. La Fundación FreeBSD es una organización - sin ánimo de lucro para la que todas las contribuciones directas son - deducibles de impuestos en su totalidad. Por favor, contactar con + y contribuir a FreeBSD. La Fundación FreeBSD es una organización + sin ánimo de lucro para la que todas las contribuciones directas son + deducibles de impuestos en su totalidad. Por favor, contactar con bod@FreeBSDFoundation.org para obtener más información o escribir a The FreeBSD Foundation, 7321 Brockway Dr. Boulder, CO 80303. USA.

    La compañía Silicon Breeze ha realizado unas esculturas del BSD Daemon en metal y dona el 15% de todos los pedidos de estas estatuillas - a la Fundación FreeBSD. Para conocer la historia completa y como + a la Fundación FreeBSD. Para conocer la historia completa y como realizar pedidos, consultar esta página.


    - - + +
    -
    ¡Para aprender más sobre FreeBSD, + ¡Para aprender más sobre FreeBSD, visita nuestra galería de publicaciones relacionadas con FreeBSD o FreeBSD en la prensa, y navega a través de este web!

    Noticias - +
      Anuncios
      En la Prensa
      Más...

    - +

    Software - +
      Obtener FreeBSD
      Información de releases
      Aplicaciones portadas

    - +

    Documentación - +
    -   FreeBSD en +   FreeBSD en español
      Para principiantes
      Handbook
      Tutoriales
      FAQ
      Libros
    -   Gnome
    - +   Gnome
    +

    - +

    Soporte - +
      Listas de distribución
    -   Grupos de +   Grupos de News
      Grupos de usuarios
      Recursos Web
      Seguridad
      Más...

    - +

    Desarrollo - +
      Proyectos
    -   Informe de +   Informe de Bugs
      Sistema CVS

    Comercial - +
      Software
      Hardware
      Consultoría
      Varios

    Este Web - +
      Mapa del Web
      Buscar
      Más...

    - +
      Buscar:
    - +
    - + - + - +
    [FreeBSD Mall][Sponsor of Unix Guru Universe] [Daemon News][Powered by FreeBSD]

    Los cambios en el web se realizan a las 0800 y 2000 UTC diariamente.

    - +
    -
    Contactar con nosotros
    Copyright © 1995-2004 The FreeBSD Project.
    All rights reserved.
    + - + diff --git a/es/index.xsl b/es/index.xsl index 309edd0a90..c5ac1bfee1 100644 --- a/es/index.xsl +++ b/es/index.xsl @@ -1,402 +1,332 @@ - + - + + here are not used actually --> + + + + - + <xsl:value-of select="$title"/> - - - + - - + + + + + + + + + + + + Spamtrap, do not email: + <a href="mailto:bruscar@freebsd.org">bruscar@freebsd.org</a> + - - - - - - - - -
    - FreeBSD: The Power to Serve -
    - -
    - - Selecciona el servidor más - cercano: - -
    - - - - - -
    - - Idioma: - [de] -   - [en] -   - [es] -   - [fr] -   - [it] -   - [ja] -   - [ru] -
    -
    - -
    - -
    - - - - - - - - - - - - - - - - -
    - - - - -
    - - - - -
    - - - - -
    - Buscar:
    - - - -
    -
    -
    -
    -

    ¿Qué es FreeBSD?

    - -

    FreeBSD es un avanzado sistema operativo para arquitecturas - x86 compatibles (incluyendo Pentium® y Athlon™), - amd64 compatibles (incluyendo Opteron™, Athlon 64 y EM64T), - Alpha/AXP, IA-64, PC-98 y UltraSPARC®. - FreeBSD es un derivado de BSD, la versión de - desarrollada en la Universidad - de California, Berkeley. FreeBSD es desarrollado y mantenido - por un - - numeroso equipo de personas. El soporte para otras - arquitecturas - está en diferentes fases de desarrollo.

    - -

    Características principales -

    - -

    FreeBSD ofrece altas - prestaciones - en comunicaciones de red, rendimiento, seguridad y - compatibilidad, todavía inexistentes en otros sistemas - operativos, incluyendo los comerciales de mayor renombre.

    - -

    Potentes Soluciones Internet -

    - -

    FreeBSD es el servidor ideal para servicios de - Internet o Intranet. - Proporciona unos servicios de red robustos, incluso en - situaciones de alta carga, haciendo un uso eficaz de la - memoria para mantener buenos tiempos de repuesta con cientos - o miles de procesos simultáneos de usuarios.

    - -

    Ejecuta una gran variedad de - aplicaciones

    - -

    La calidad de FreeBSD conbinada con el hoy en día bajo - coste del hardware de alta velocidad para PC's hace de este - sistema una alternativa muy económica sobre las - estaciones de trabajo - comerciales. Existe gran cantidad de - aplicaciones - tanto a nivel servidor como usuario.

    - -

    Fácil de instalar

    - -

    Se puede instalar FreeBSD desde una gran variedad de - soportes, incluyendo CD-ROM, DVD-ROM, disquetes, cintas - magnéticas, una partición MS-DOS®, o si se - dispone de conexión de red, se puede instalar - directamente mediante FTP anónimo o NFS. Todo lo - necesario son dos discos de 1.44MB de arranque y - estas instrucciones.

    - -

    FreeBSD es libre y gratuito -

    - - - -

    Si esperabas que un sistema operativo con estas - características tuviese un alto coste, FreeBSD - está disponible - completamente gratis - incluyendo el código fuente. Si quieres probarlo, - - aquí tienes más información.

    - -

    Contribuyendo a FreeBSD

    - -

    Es muy fácil contribuir a FreeBSD. Todo lo que tienes - que hacer es encontrar una parte de FreeBSD que creas puede - mejorarse y hacer los cambios (cuidadosa y limpiamente) y - enviarlas al proyecto mediante un "send-pr" o un committer, si - conoces a alguno. Más información en la - - sección de contribuciones del manual.

    - - -

    Aún no siendo programador, existen otros métodos - de colaborar y contribuir a FreeBSD. La Fundación - FreeBSD es una organización no lucrativa para la que - todas las contribuciones directas son deducibles de - impuestos en su totalidad. Por favor, contactar con - - bod@FreeBSDFoundation.org para obtener más - información o escribir a The FreeBSD Foundation, 7321 - Brockway Dr. Boulder, CO 80303. USA.

    - -
    - - - - - -
    - - - - -

    - - Nueva - Tecnología: -
    - · Guía de Instalación
    - · Notas de Release
    - · Notas de Hardware
    - · Notas de Instalación
    - · Errata
    - · Guía de Migración

    - -

    - - Release en - Producción: -
    - · Guía de Instalación
    - · Notas de Release
    - · Notas de Hardware
    - · Notas de Instalación
    - · Errata

    - -

    Noticias del - Proyecto(RSS)
    - - Ultima actualización: - + + +

    +
    + +
    + +
    +
    +
    + +
    +
    +

    + Based on BSD UNIX® +

    +

    FreeBSD es un avanzado sistema operativo para arquitecturas + x86 compatibles (incluyendo Pentium® y Athlon™), + amd64 compatibles (incluyendo Opteron™, Athlon 64 y EM64T), + Alpha/AXP, IA-64, PC-98 y UltraSPARC®. + FreeBSD es un derivado de BSD, la versión de + desarrollada en la Universidad + de California, Berkeley. FreeBSD es desarrollado y mantenido + por un + + numeroso equipo de personas. El soporte para otras + arquitecturas + está en diferentes fases de desarrollo.

    + +
    +
    + +
    +
    +
     
     
    + +
     
     
    +
    + +
    +
    +

    LATEST RELEASES

    + +
    +
    +
    + +
    +

    Language Links

    +
    + +
    + +
    +
    +
    +

    + +
    +
    +
    + +
    +
    +

    SHORTCUTS

    + +
    +
    + +
    +
     
     
    + +
     
     
    +
    +
    + +
    + +
    +
    +
    +
    +

    LATEST NEWS

    +
    + + + - -
    - - - - Más... -

    - -

    FreeBSD en la - Prensa
    - - - Ultima actualización: - - - -
    - + + +

    + +
    +
    + +
    +
    +
    .
    +
    +
    + +

    UPCOMING EVENTS

    +
    + + + + + + + +
    + +
    +
    + +
    +
    +
    .
    +
    +
    + +

    IN THE MEDIA

    +
    + + + - - Más... - -

    - -

    Avisos de - Seguridad - - (RSS)
    - - - Ultima actualización: - + + +

    + +
    +
    + +
    +
    +
    .
    +
    +
    + +

    AVISOS DE SEGURIDAD

    +
    + + - -
    - - - - Más... -
    -

    - -

    Noticias Errata - -
    - - Ultima actualización: - - - - -
    - - - - -
    -

    -
    -
    - -

     

    - - - - - -
    - - - -
    Para aprender más sobre FreeBSD, visita - nuestra galería de - publicaciones - relacionadas con FreeBSD o - FreeBSD en la prensa, - y navega a través de este web!
    -
    -
    - -
    - - - - - - - - - - - -
    [FreeBSD Mall][Sponsor del Unix Guru Universe][Daemon News][Powered by FreeBSD]
    - - - - - - - -
    Contactar con nosotros
    -
    Copyright © 1995-2005 - The FreeBSD Project.
    - All rights reserved.
    + + + +
    + +
    +
    + +
    +

    NOTICIAS ERRATA

    +
    + + + + + + +
    + + + + +
    + + + + + + + + + + diff --git a/es/internal/about.sgml b/es/internal/about.sgml index 828fe4481d..c915d1c8d7 100644 --- a/es/internal/about.sgml +++ b/es/internal/about.sgml @@ -1,95 +1,96 @@ - - + + %navincludes; %includes; ]> - + &header;

    La Máquina

    La máquina, www.freebsd.org, también conocida como freefall.freebsd.org, es un Pentium Pro 400Mhz con una placa base PCI, 256 Mb de RAM y 4Gb de disco duro. El sistema de búsqueda de páginas y listas de distribución es hub.freebsd.org, un Pentium II a 400Mhz con 256Mb de RAM y 10Gb de disco.

    Naturalmente, el sistema se ejecuta sobre el sistema operativo FreeBSD. El hardware y la conectividad han sido generosamente donados por Walnut Creek CDROM y otros contribuyentes del proyecto FreeBSD.

    Una lista completa de todas las máquinas en el dominio FreeBSD.org esta disponible en la página de La Red FreeBSD.org.

    El Software

    Estas páginas son servidas por el versátil y eficiente servidor http APACHE. Además se han incluido una serie de scripts CGI. La indexación de estas páginas y el archivo de las listas de distribución se hacen mediante freewais-sf, un derivado del freewais CNIDR.

    El paquete estadístico + align="right">

    El paquete estadístico Urchin es usado para realizar estas estadísticas sobre el uso del servidor web.

    Las Páginas

    - +

    Estas páginas han sido creadas por John Fieber <jfieber@freebsd.org> con participación de la comunidad FreeBSD y . El Webmaster es <wosch@freebsd.org>. Las páginas de FreeBSD cumplen la normativa HTML 3.2 y son mejor vistas con tu navegador.

    Consulta también el Proyecto de Documentación de FreeBSD.

    Diseño

    El diseño original es de Megan McCormack

    Paquetes ping bloqueados

    Nuestro proveedor CRL está bloqueando todo el tráfico ICMP.

    Actualización de las páginas Web de FreeBSD

    Las páginas Web de FreeBSD son actualizadas diariamente a las 08:00 y 20:00 MET (UTC).

    Mirroring del Web de FreeBSD

    Puedes (y te animamos) a hacer mirror del web www.freebsd.org.

    Las estadísticas de uso de este servidor se actualizan diariamente.

    FreeBSD Internal Home &footer; diff --git a/es/internal/developer.sgml b/es/internal/developer.sgml index 2c38608cf7..20553e420a 100644 --- a/es/internal/developer.sgml +++ b/es/internal/developer.sgml @@ -1,53 +1,54 @@ - - + + %navincludes; %includes; ]> - + &header;

    Guía para committers

    Creación de las páginas web de FreeBSD

    Este documento describe como crear y actualizar manualmente las páginas web de FreeBSD desde el reposotiry de CVS -

    FreeBSD Documentation Project Primer for New Contributors

    +

    FreeBSD Documentation Project Primer for New Contributors

    Este documento describe todo lo que necesitarás saber para poder comenzar a contribuir en el FreeBSD Documentation Project, desde las herramientas y software que usarás hasta la filosofía seguida por el Proyecto de Documentación.

    Guía para los FreeBSD Ports Committers

    Una guía para los FreeBSD Ports Committers

    Proyectos de FreeBSD

    Otros recursos

    FreeBSD Internal Home &footer; diff --git a/es/internal/homepage.sgml b/es/internal/homepage.sgml index 746caef719..e5be6112c4 100644 --- a/es/internal/homepage.sgml +++ b/es/internal/homepage.sgml @@ -1,20 +1,21 @@ - - + + %navincludes; %includes; ]> - + &header;
      &homepage;

    FreeBSD Internal Home &footer; diff --git a/es/internal/internal.sgml b/es/internal/internal.sgml index 531180468b..c8ef53db6d 100644 --- a/es/internal/internal.sgml +++ b/es/internal/internal.sgml @@ -1,62 +1,63 @@ - - + + %navincludes; %includes; ]> - + &header;

    La red FreeBSD.org

    Esta página describe, para aquellos con cuentas de acceso en la red FreeBSD.org, las máquinas y recursos actualmente disponibles y el tipo de tarea que realiza cada una de ellas.

    Recursos para los committers de FreeBSD

    Esta página recopila una serie de recursos para los committers de FreeBSD.

    Sobre el servidor WWW de FreeBSD

    La máquina, el software, réplicas de las páginas Web, estadísticas de uso.

    Staff del proyecto FreeBSD

    El proyecto FreeBSD está comandado y operado por los siguientes grupos de gente: FreeBSD Core Team, Desarrolladores de FreeBSD.

    Fotos de Eventos Sociales

    Páginas personales

    Una lista de páginas personales mantenidas en www.freebsd.org.

    Proyectos de FreeBSD

    Sumáandose a los desarrollos principales realizados por FreeBSD, +

    Sumáandose a los desarrollos principales realizados por FreeBSD, existen diferentes grupos de desarrolladores trabajando en la expansión de las posibilidades de FreeBSD en otras direcciones.

    Contactar con FreeBSD

    Copyright de FreeBSD

    The FreeBSD Copyright(s).

    Buscar en el servidor de FreeBSD

    Servicios de búsquedas de FreeBSD.

    Estadísticas de FreeBSD

    -

    Estadísticas de tráfico Web, tráfico FTP, uso de +

    Estadísticas de tráfico Web, tráfico FTP, uso de Releases.

    &footer; diff --git a/es/internal/machines.sgml b/es/internal/machines.sgml index c4928623db..37b92cac39 100644 --- a/es/internal/machines.sgml +++ b/es/internal/machines.sgml @@ -1,155 +1,156 @@ - - + + %navincludes; %includes; ]> - + &header;

    Esta página describe, para aquellos con cuentas de acceso en la red FreeBSD.org, las máquinas y recursos actualmente disponibles y el tipo de tarea que realiza cada una de ellas.

    Todos los nombres de máquinas en el dominio FreeBSD.org

    Máquina S.O. Objetivo Administrador(es)
    builder 4.0-current Creación de packages -current Equipo de ports
    beast 4.0-current Máquina Alpha para tests FreeBSD/alpha jkh
    bento 3.0-stable Creación de packages 3.0-stable Equipo de ports
    freefall 3-stable CVS master repository committers
    hub 3-stable Servicios Mail & WWW post/webmaster
    node82-89 3-stable Cluster creación de ports Equipo de ports

    Configuraciones Hardware

    Máquina Tipo Hardware
    builder Intel x86 400Mhz Pentium II, 128MB mem, NCR 53c875, 9GB IBM Disco SCSI, Winbond 100bTX NIC.
    beast Aspen Durango 500MHz 21164A en DEC PCI64 MB, 128MB mem, controladora NCR 53c875 SCSI , discos 2x4GB SCSI WIDE (uno NetBSD/alpha, uno FreeBSD/alpha), DEC 21140 NIC.
    bento Intel x86 MP 2x300MHz Pentium II, 128MB mem, controladora AHC 2940 PCI SCSI, discos 5x4GB SCSI WIDE, Intel EtherExpress Pro 10/100B NIC.
    freefall Intel x86 400MHz Pentium II, 256MB mem, controladora AHA2940U2W PCI SCSI , discos 2x4GB SCSI WIDE y 3x9GB SCSI U2W, Intel EtherExpress Pro 10/100B NIC.
    hub Intel x86 400MHz Pentium II, 256MB mem, AHC 2940 PCI SCSI controller, 3x4GB SCSI WIDE drives, HP 6020i CDR, Intel EtherExpress Pro 10/100B NIC.
    node82-89 AMD x86 300MHz AMD K6/2, 64MB mem, disco 3GB IDE, Intel EtherExpress Pro 10/100B NIC.

    Como regla general, todas las máquinas están conectadas -a 100Mbits a la red FreeBSD (switch de 100Mbit), a no ser que por alguna +a 100Mbits a la red FreeBSD (switch de 100Mbit), a no ser que por alguna razón determinada, se deba conectar a 10Mbits.

    Políticas Administrativas

    Si la máquina en cuestión es administrada por alguna persona determinada, por favor, pregúntale primero a ellos sobre temas administrativos, incluyendo cambios en las cuentas de usuario o en los sistemas de ficheros.

    -

    Todas las nuevas cuentas deben ser aceptadas por el equipo de +

    Todas las nuevas cuentas deben ser aceptadas por el equipo de administradores, admins@freebsd.org y solo se dan a desarrolladores de FreeBSD, ya sea en la documentación, -ports o código fuente del sistema. La única excepción a +ports o código fuente del sistema. La única excepción a esta regla es la máquina de pruebas kickme.freebsd.org, para la cual -se podrán conceder cuentas de acceso a desarrolladores no +se podrá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íficos. Las cuentas no son concedidas al "público en general", así que por favor, no preguntes. Gracias.

    Jordan Hubbard
    jkh@freebsd.org

    FreeBSD Internal Home &footer; diff --git a/es/internal/mirror.sgml b/es/internal/mirror.sgml index d18d571dc3..240233f8e1 100644 --- a/es/internal/mirror.sgml +++ b/es/internal/mirror.sgml @@ -1,64 +1,65 @@ - - + + %navincludes; %includes; ]> - + &header;

    Puedes (y te animamos) a mantener mirrors o réplicas de las páginas web de www.freebsd.org. Para hacerlo, necesitas obtener e instalar un programa llamado cvsup en tu servidor web. -CVSup es un software para +CVSup es un software para distribución y actualización de colecciones de ficheros a través de una red.

    Instalando CVSup

    Para instalarlo, haz lo siguiente:

      # cd /usr/ports/net/cvsup-bin
      # make all install clean
     

    Ejecutando CVSup

    Si mantienes las páginas replicadas de FreeBSD en el directorio -/usr/FreeBSD-mirror y pertenecen al usuario "fred", ejecuta el +/usr/FreeBSD-mirror y pertenecen al usuario "fred", ejecuta el siguiente comando como el usuario "fred":

          $ cvsup supfile-www
     
    EL fichero supfile-www contiene:
            *default host=cvsup.FreeBSD.org
            *default prefix=/usr/FreeBSD-mirror
            *default base=/usr/local/etc/cvsup
            www release=current delete use-rel-suffix compress
     
    -

    Esto mantendráa una réplica de las páginas de +

    Esto mantendráa una réplica de las páginas de FreeBSD en el directorio /usr/FreeBSD-mirror. Puedes instalar este comando en el cron de "fred", de manera que se realice la actualización diariamente de manera automática. Los contenidos de web de FreeBSD son actualizados diariamente a las 4:30am de California.

    Más información sobre CVSup

    -See the Introducción a +See the Introducción a CVSup en el handbook.

    FreeBSD Internal Home &footer; diff --git a/es/internal/photos.sgml b/es/internal/photos.sgml index 5bce8d13b0..9f5f444e35 100644 --- a/es/internal/photos.sgml +++ b/es/internal/photos.sgml @@ -1,76 +1,77 @@ - - + + %navincludes; %includes; ]> - + &header;

    Oxford (UK) FreeBSD meeting, Noviembre 1998

    Fotos y texto por Nik. Organizado por Paul Richards.

    Dutch FreeBSD meeting, Octubre 1998

    Fotos por Jordan y Wilko

    BSD Social Event Hamburg, Junio 1998

    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

    AUUG Spring conference, Sydney, Septiembre 1998

    Richard Stallman, Peter Wemm, Mark White, Andrew McRae, Greg Rose, muchos no identificados.

    Summer 1998 USENIX, Nueva Orleans

    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

    FreeBSD Social Event Aachen, 1995

    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

    FreeBSD People

    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

    FreeBSD Internal Home &footer; diff --git a/es/internal/statistic.sgml b/es/internal/statistic.sgml index c3c1670ac3..cfc080e4c0 100644 --- a/es/internal/statistic.sgml +++ b/es/internal/statistic.sgml @@ -1,63 +1,64 @@ - - + + %navincludes; %includes; ]> - + &header;

    Estadísticas Web

    Analog

    analog(1) tool.

    Las - estadísticas de uso de este servidor actualizadas + estadísticas de uso de este servidor actualizadas diariamente con la herramienta analog(1).

    Urchin

    El paquete estadístico Urchin es usado para crear estas estadísticas sobre el uso del servidor web.

    Uso de releases de FreeBSD

    Una muestra del uso de la release actual de FreeBSD está disponible en http://www.freebsd.org/statistic/release_usage/images/.

    El contador de FreeBSD

    La página The - FreeBSD Counter Page es el comienzo de un proyecto con el + FreeBSD Counter Page es el comienzo de un proyecto con el que se intenta determinar la base instalada a nivel mundial de usuarios de FreeBSD.

    Tráfico FTP en ftp.freebsd.org

    Hemos conseguido un nuevo record de tráfico en -wcarchive el +wcarchive el 23 de Mayo de 1999, 1.39TB.

    FreeBSD Internal Home &footer; diff --git a/es/internet.sgml b/es/internet.sgml index a8eae4a1d3..01b3e4e929 100644 --- a/es/internet.sgml +++ b/es/internet.sgml @@ -1,158 +1,146 @@ - + + %navincludes; %includes; ]> - + &header; -

    FreeBSD fue diseñado para Internet

    +

    FreeBSD fue diseñado para Internet

    -
    -

    FreeBSD incluye lo que muchos consideran la - implementacón de referencia de TCP/IP, - el stack 4.4BSD del protocolo TCP/IP, haciendolo ideal para +

    FreeBSD incluye lo que muchos consideran la + implementacón de referencia de TCP/IP, + el stack 4.4BSD del protocolo TCP/IP, haciendolo ideal para aplicaciones de red e Internet.

    -
    - -
    - FreeBSD soporta los protocolos - estándar TCP/IP. - -
    + +

    FreeBSD soporta los protocolos + estándar TCP/IP.

    +

    Como muchos sistemas UNIX, el sistema operativo FreeBSD permite

    • Compartir ficheros mediante NFS
    • Distribución de información de red con NIS
    • Soporte de accesos remotos
    • Gestión y configuración remota vía SNMP
    • Servidor de ficheros FTP
    • Resolución de nombres de máquinas con DNS/BIND
    • Enrutar paquetes entre múltiples interfaces, incluyendo líneas PPP y SLIP
    • Servicios IP Multicast (MBONE)
    -

    FreeBSD permite convertir un PC en un servidor World Wide Web o - servidor de noticias, con el software ya incluido. Usando el software incluido +

    FreeBSD permite convertir un PC en un servidor World Wide Web o + servidor de noticias, con el software ya incluido. Usando el software incluido SAMBA puedes compartir discos e impresoras con otras máquinas - con Win95 y NT, además de soportar máquinas con PC/NFS - gracias al daemon de autentificación PCNFS. FreeBSD también - soporta los protocolos de red Appletalk y Novell en modo cliente/servidor - (usando un paquete comercial opcional), + con Win95 y NT, además de soportar máquinas con PC/NFS + gracias al daemon de autentificación PCNFS. FreeBSD también + soporta los protocolos de red Appletalk y Novell en modo cliente/servidor + (usando un paquete comercial opcional), haciendo de este sistema una verdadera solución de servicios Intranet.

    -

    FreeBSD también gestiona extensiones TCP como la extensión +

    FreeBSD también gestiona extensiones TCP como la extensión de alto rendimiento - RFC-1323 + RFC-1323 y la extensión - RFC-1644 + RFC-1644 para transacciones, además de SLIP y PPP bajo demanda. Es un sistema que responde a las expectativas tanto del usuario doméstico como del administrador de sistemas corporativo.

    -
    + +

    El sistema de red de FreeBSD es + rápido y estable.

    -
    - El sistema de red de FreeBSD es - rápido y estable. - -
    -

    Si necesitas una plataforma para servicios de Internet que ofrezca el - mejor rendimiento bajo fuertes cargas de trabajo, considera FreeBSD. - Aquí están solo algunas de las compañías +

    Si necesitas una plataforma para servicios de Internet que ofrezca el + mejor rendimiento bajo fuertes cargas de trabajo, considera FreeBSD. + Aquí están solo algunas de las compañías que usan FreeBSD diariamente:

      -
    • Walnut Creek CDROM en las - afueras de San Francisco mantubo en funcionamiento uno de los +
    • Walnut Creek CDROM en las + afueras de San Francisco mantubo en funcionamiento uno de los servidores FTP más populares de Internet, ftp.cdrom.com, - soportando 6000 conexiones simultáneas. - Su servidor es una única máquina con FreeBSD - transfiriendo más de 30 terabytes (en Junio de 1999); si son + soportando 6000 conexiones simultáneas. + Su servidor es una única máquina con FreeBSD + transfiriendo más de 30 terabytes (en Junio de 1999); si son terabytes, cada mes a más de 10 millones de personas.
    • -
    • Yahoo Inc. gestiona el índice - de Internet más usado, sirviendo enormes cantidades de - información diariamente a los usuarios de Internet. Yahoo, y las - compañías que usan su buscador, utilizan FreeBSD como +
    • Yahoo Inc. gestiona el índice + de Internet más usado, sirviendo enormes cantidades de + información diariamente a los usuarios de Internet. Yahoo, y las + compañías que usan su buscador, utilizan FreeBSD como plataforma de sus servidores Web.
    • - -
    • Netcraft es el investigador - principal del uso de software para servidores Web en Internet. Utilizan - FreeBSD y Apache para accionar su sitio Web, y FreeBSD/Perl para toda su + +
    • Netcraft es el investigador + principal del uso de software para servidores Web en Internet. Utilizan + FreeBSD y Apache para accionar su sitio Web, y FreeBSD/Perl para toda su colección de datos sobre Internet.

    FreeBSD es la plataforma ideal para estos y otros servicios de Internet:

    • Servicio empresarial o mundial de WWW
    • Servicio de Proxy WWW
    • Servicio de FTP Anónimo
    • Servicios de ficheros, impresión y mail
    -

    La Colección de Ports - contiene software listo para funcionar que hace más fácil la +

    La Colección de Ports + contiene software listo para funcionar que hace más fácil la puesta en marcha de los servidores de Internet.

    -
    - -
    - Alto rendimiento y seguridad. - -
    -

    El equipo de desarrollo de FreeBSD está tan comprometido con la - seguridad como con el rendimiento. FreeBSD incluye en su kernel el soporte de - firewall IP, además de otros servicios como gateways e IP proxy. - Si se conectan los servidores corporativos en Internet, cualquier computadora - funcionando con FreeBSD puede actuar como firewall de red para protegerlos + +

    Alto rendimiento y seguridad.

    + +

    El equipo de desarrollo de FreeBSD está tan comprometido con la + seguridad como con el rendimiento. FreeBSD incluye en su kernel el soporte de + firewall IP, además de otros servicios como gateways e IP proxy. + Si se conectan los servidores corporativos en Internet, cualquier computadora + funcionando con FreeBSD puede actuar como firewall de red para protegerlos de ataques externos.

    -

    Software de encriptación, shells seguras, Kerberos, encriptación - punto a punto y RPC seguro también están disponibles +

    Software de encriptación, shells seguras, Kerberos, encriptación + punto a punto y RPC seguro también están disponibles (sujetas a restricciones de exportación).

    -

    Además, el equipo de FreeBSD está continuamente - investigando y comunicando informaciones de seguridad con un - responsable de seguridad +

    Además, el equipo de FreeBSD está continuamente + investigando y comunicando informaciones de seguridad con un + responsable de seguridad y el Computer Emergency Response Team (CERT).

    -

    Qué dicen los expertos . . .

    - -
    +

    ``FreeBSD ... provides what is probably the most robust and capable TCP/IP stack in existence ...''

    ---Michael O'Brien, SunExpert August 1996 volume 7 number 8.

    -
    &footer; - diff --git a/es/mailto.sgml b/es/mailto.sgml index fff16cfbda..43897bb2f8 100644 --- a/es/mailto.sgml +++ b/es/mailto.sgml @@ -1,47 +1,48 @@ - + + %navincludes; %includes; ]> - + &header;

    Preguntas sobre FreeBSD...

    Las preguntas referentes a FreeBSD deberían ser enviadas a la - lista de distribución + lista de distribución freebsd-questions@FreeBSD.ORG.

    Preguntas sobre el contenido de este servidor WWW...

    Las preguntas o sugerencia sobre nuestra documentación, (Handbook, FAQ o Tutoriales) deberín ser enviadas a los miembros del Proyecto de Documentación de FreeBSD. freebsd-doc@FreeBSD.ORG.

    Otras listas de distribución de FreeBSD

    Las Listas de distribución son el canal primario de soporte de los usuarios de FreeBSD, con numerosas listas cubriendo diferentes áreas. Diferentes listas no inglesas están disponibles.

    Correo, teléfono y fax

    - For CDROM orders: + For CDROM orders: Walnut Creek CDROM
    Para soporte comercial: The FreeBSD Mall

    Quién es responsable de qué

    &footer; diff --git a/es/news/news.sgml b/es/news/news.sgml index aea741d859..25429d000e 100644 --- a/es/news/news.sgml +++ b/es/news/news.sgml @@ -1,62 +1,63 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header; - +FreeBSD News

    FreeBSD Newsflash

    Qué es nuevo.

    -

    Notas de Prensa de FreeBSD

    +

    Notas de Prensa de FreeBSD

    Notas de prensa del proyecto FreeBSD.

    The FreeBSD Quick NewsLetter

    FreeBSD Really-Quick(TM) NewsLetter. Cosas que ocurren en FreeBSD.

    FreeBSD en la Prensa

    La prensa sobre FreeBSD.

    Newsletter

    FreeBSD Newsletter.

    FreeBSD ezine

    FreeBSD Ezine es una colección mensual de arículos fáciles de leer escritos por usuarios y administradores de sistemas FreeBSD como tú.

    The FreeBSD Diary

    -

    El FreeBSD Diary es una colección de secciones how-to dirigida a +

    El FreeBSD Diary es una colección de secciones how-to dirigida a principiantes en Unix. Guía paso a paso para la instalación y configuración de diferentes ports.

    FreeBSD Rocks

    FreeBSD Rocks es una iniciativa diseñada para proveer a la comunidad de usuarios de FreeBSD con las últimas noticias, software y recursos. -Todas las áreas incluyen buscadores, haciendo muy sencilla la +Todas las áreas incluyen buscadores, haciendo muy sencilla la búsqueda de noticias anteriores. Las páginas son actualizadas diariamente y todos estais invitados a enviar algún artículo. Si algo ha ocurrido hoy, lo verás en FreeBSDRocks.

    Daemon News

    El líder en la industria de noticias sobre BSD.

    Cambios en el servidor web de FreeBSD

    &footer; diff --git a/es/news/newsflash.sgml b/es/news/newsflash.sgml index 8016598782..efef0a122f 100644 --- a/es/news/newsflash.sgml +++ b/es/news/newsflash.sgml @@ -1,706 +1,708 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header; - +FreeBSD News +

    FreeBSD es un sistema operativo de rápido desarrollo. Mantenerse al día en los últimos desarrollos puede ser complicado. Para ayudarte a mantenerte al día, pásate por aquí periódicamente. También te recomendamos que te subscribas a la lista freebsd-announce .

    La FreeBSD Real-Quick (TM) Newsletter (RQN) es una pequeña publicación mensual (a veces - quincenal) sobre desarrollos recientes en el mundo de FreeBSD. - Subscríbete a + quincenal) sobre desarrollos recientes en el mundo de FreeBSD. + Subscríbete a freebsd-announce para recibirla vía e-mail.

    Para una detallada descripción de pasado, presente, y futuro de las -releases, mira en la página de -Información de +releases, mira en la página de +Información de Releases.

    Diciembre 1999

    Septiembre 1999

    • 17-Sep-1999Ya está disponible la versión 3.3-RELEASE de - FreeBSD. Por favor, consulta la + FreeBSD. Por favor, consulta la Información de la Release para más detalles. También es conveniente - consultar la + consultar la lista de erratas después de la instalación.

    Agosto 1999

    • 10-Ago-1999 C-Forge, - ha publicado un Entorno Integrado de Desarrollo (IDE) para FreeBSD, + ha publicado un Entorno Integrado de Desarrollo (IDE) para FreeBSD, soportando C, C++, Perl, Tcl y muchos otros lenguajes.

    Junio 1999

    • 10-Jun-1999 Los CD's de FreeBSD 3.2-RELEASE están siendo enviados. Los subscriptores que no tienen ningún acuerdo o condición especial de envío, deberín recibir los cd's en muy poco tiempo. Cualquier persona que desee pedir FreeBSD 3.2-RELEASE o subscribirse, puede hacerlo a través de The FreeBSD Mall.
    • 8-Jun-1999 Un nuevo Mirror Australiano del Web de FreeBSD Gracias a ITworks Consulting por la conectividad.

    Mayo 1999

    • 18-Mayo-1999 FreeBSD 3.2 disponible. Por favor, mira en la página de Información Release para más detalles. Asegúrate de visitar la página de erratas después de la instalación por si se ha detectado algún problema de última hora.

    Abril 1999

    Marzo 1999

    • 05-Mar-1999La USENIX Association ha anunciado la 1999 USENIX Annual Technical Conference, para los días 6 al 11 de Junio de 1999 en Monterey, California, USA. Jordan Hubbard se encarga de - FREENIX, dedicado exclusivamente a los ultimos desarrollos y + FREENIX, dedicado exclusivamente a los ultimos desarrollos y aplicaciones interesantes dentro del mundo del software libre.
    • -
    • 01-Mar-1999Puesta en marcha de un servidor seguro para +
    • 01-Mar-1999Puesta en marcha de un servidor seguro para aceptar donaciones monetarias para el proyecto FreeBSD. Para más información mira en http://www.freebsdmall.com/donate/.
    • -
    • 01-Mar-1999Ya están disponibles los CD's de +
    • 01-Mar-1999Ya están disponibles los CD's de FreeBSD 3.1-RELEASE. Los suscriptores recibirán muy pronto sus - CD's. Pásate por + CD's. Pásate por http://www.cdrom.com/ para hacer los pedidos.

    Febrero 1999

    • 17-Feb-1999The Gartner Group ha presentado un documento - Divorcing Thin Server Software from the Hardware examinando + Divorcing Thin Server Software from the Hardware examinando la tendencia de usar hardware y software de diferentes proveedores.
    • 15-Feb-1999 - FreeBSD 3.1 ya está disponible. Por favor, mira la + FreeBSD 3.1 ya está disponible. Por favor, mira la Información de la Release para más detalles. Asegúrate de leer la página de erratas después de la instalación por si se ha tenido que incluir algún tipo de información sobre la 3.1-release.
    • 04-Feb-1999El - Diario de FreeBSD, una colección de documentos en formato + Diario de FreeBSD, una colección de documentos en formato how-to para principiantes en Unix.

    Enero 1999

    • 20-Ene-1999 3.0-stable ha dejado de pertenecer a la rama -current. La próxima release en esta rama será la 3.1-RELEASE a mediados de Febrero e 1999.
    • 13-Ene-99El FreeBSD ezine es una + href="http://www.freebsdzine.org/">FreeBSD ezine es una colección mensual de artículos fáciles de leer escritos por usuarios y administradores de FreeBSD como tú.
    • 10-Ene-99Una "carta abierta" de Jordan Hubbard en la que se repasa el año 1998 y se plantean las posibilidades futuras de FreeBSD.

    December 1998

      -
    • 28-Dec-98Unless 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 +
    • 28-Dec-98Unless 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.
    • 13-Dec-98Walnut Creek CD-ROM has opened the FreeBSD Mall, 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.

    November 1998

    • 30-Nov-98 FreeBSD 2.2.8 has been released. Please see the Release Information page for more details. Also be sure to check the release errata after installation for any late-breaking issues with 2.2.8 that you might need to be aware of.
    • 26-Nov-98FreeBSD - Rocks 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 + Rocks 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.

    October 1998

    • 15-Oct-98 - FreeBSD 3.0 has been released. See the - Release Information page for - details. Also be sure to check the + FreeBSD 3.0 has been released. See the + Release Information page for + details. Also be sure to check the release errata after installation for any late-breaking issues with 3.0 that you might need to be aware of.

    September 1998

    • 15-Sep-98 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 :).

    • 13-Sep-98 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.

    • 9-Sep-98 Perl5 is now imported into the 3.0-CURRENT source tree.

    • - - + +
    • 5-Sep-98 The BSD CD Giveaway List. 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 + 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.

    • 1-Sep-98 First issue of Daemon News arrives day earlier. This electronic - ezine is by BSD community for BSD community. See + ezine is by BSD community for BSD community. See http://www.daemonnews.org

    August 1998

    • 31-Aug-98 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 - + went smooth. Check + freebsd-current@freebsd.org mail archive for more information on the transition to ELF. -

    • +

    • 23-Aug-98 - Suidcontrol-0.1 utility has been released. The suidcontrol is an + 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 http://www.watson.org/fbsd-hardening/suidcontrol.html

    • 9-Aug-98 FreeBSD Security How-To has been published. This work is currently - in beta and can be found at + in beta and can be found at http://www.best.com/~jkb/howto.txt

    July 1998

    June 1998

    • 24-Jun-98 The FreeBSD Project is sponsoring an FreeBSD Desktop Theme Contest. Participants will design their own X11 configurations, and winners will have theirs distributed with future releases of FreeBSD.

    - +

    May 1998

    • 30-May-98 FreeBSD and Apache are used in this very useful article on implementing a web farm using round-robin DNS in WEBTechniques.com

    • 23-May-98 - The second issue of the FreeBSD Newsletter is now available in + The second issue of the FreeBSD Newsletter is now available in - Adobe PDF format (also by + Adobe PDF format (also by FTP). A help file is available to assist you in selecting and using - a PDF viewer. - Article submissions, advertisements, and letters - to the editor should be sent to - newsletter@freebsd.org. + a PDF viewer. + Article submissions, advertisements, and letters + to the editor should be sent to + newsletter@freebsd.org.

    • 1-May-98 The FreeBSD Project set up Anonymous CVS - for the FreeBSD CVS tree. - Among other things, it allows users of FreeBSD to perform, + for the FreeBSD CVS tree. + 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. + against one of the FreeBSD project's official anoncvs servers.

    • - +

    April 1998

    • 16-Apr-98 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 + information on the CD contents are available from http://www.cdrom.com.

    • 11-Apr-98 The new FreeBSD project FreeBSD Mozilla - Group is created. The FreeBSD Mozilla Group supports and + Group is created. The FreeBSD Mozilla Group supports and improves the free available Netscape web browser, otherwise known as Mozilla.

    March 1998

    • 25-Mar-98 FreeBSD 2.2.6 has been released. See the Release Information page for details. Also be sure to check the release errata after installation for any late-breaking issues with 2.2.6 that you should know about.

    February 1998

    - +

    January 1998

    • 08-Jan-98 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 + in source form via the CVSup utility or in binary release snapshots from current.FreeBSD.org

    December 1997

    • 26-Dec-97 A convenient front-end tool for installing and configuring the - CVSup utility is + CVSup utility is now available. To use it, simply login or su to root and run: pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz

    • 2-Dec-97 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 - CVSup utility, as + CVSup utility, as described below for the LAND attack fix, or by applying these patches.

    • 1-Dec-97 The "LAND attack" bug in TCP/IP has now been fixed in all relevant branches and can be incorporated by using the - CVSup utility + CVSup utility to track the latest 2.2 or 3.0 sources.

    • 1-Dec-97 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 + more information, visit Team FreeBSD's WWW site.

    November 1997

    • 21-Nov-97 - Pentium bug -- We are aware of the "F00F" Pentium halting bug and are + Pentium bug -- 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 comp.unix.bsd.freebsd.announce. Your patience is appreciated.

    • 09-Nov-97 FreeBSD 2.2.5-RELEASE CDROMS are now in stock and shipping to customers worldwide. More information is available at http://www.cdrom.com/titles/os/fbsd25.htm.

    October 1997

    • 22-Oct-97 FreeBSD 2.2.5 has been released. See the Release Information page for details. Also be sure to check the release errata after installation for any late-breaking issues with 2.2.5 that you should know about.

    September 1997

    • 01-Sep-97 FreeBSD performed well in an Internet Week review of WWW server platforms.

    August 1997

    • 11-Aug-97 Researchers in Duke University's Trapeze Project - have developed a high-speed Myrinet driver for FreeBSD. More + 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 WWW page.

    • 03-Aug-97 - Netscape Communications has released a beta version of + Netscape Communications has released a beta version of Netscape Communicator v4.0 for FreeBSD. It can be obtained via FTP from ftp.netscape.com or its mirrors.

    July 1997

    June 1997

    • 17-Jun-97 FreeBSD - 2.2.2-RELEASE CD-ROM discs are now in stock; subscription + 2.2.2-RELEASE CD-ROM discs are now in stock; subscription customers should receive them shortly.

    May 1997

    April 1997

    • 28-Apr-97 - The 3.0-current src tree now contains support for building Symmetric - MultiProcessor kernels. For details go to the + The 3.0-current src tree now contains support for building Symmetric + MultiProcessor kernels. For details go to the SMP page.

    • 22-Apr-97 A RELENG_2.2 snap-of-the-day server has been established at ftp://releng22.freebsd.org/pub/FreeBSD. The README.TXT has more information.

    • 15-Apr-97 FreeBSD 2.2.1-RELEASE CDs are shipping. Please see http://www.cdrom.com/titles/os/fbsd22.htm for more information.

    March 1997

    February 1997

    • 20-Feb-1997 FreeBSD 2.1.7-RELEASE is now available. Read the README.TXT file or the Release Notes for more information.

    • 10-Feb-1997 FreeBSD 3.0-970209-SNAP has been released. Read the README.TXT file for more information about this release.

    • 06-Feb-1997 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 + available from the FTP distribution sites. You can read more about the problem and solution from the FreeBSD-SA-97:01.setlocale security announcement.

    • 06-Feb-1997 The final pre-release version of FreeBSD 2.2-GAMMA, is now available. The README.TXT file has more information.

    • 02-Feb-1997 - A snap-of-the-day server has been set up for the most current + A snap-of-the-day server has been set up for the most current snapshot - release of FreeBSD 2.2. Read the + release of FreeBSD 2.2. Read the README.TXT file for more information.

    January 1997

    December 1996

    • 24-Dec-1996 FreeBSD 2.2-BETA has been released. Please see the Release Notes for more information.

    • 13-Dec-1996 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 announcement for more information.

    November 1996

    &newshome; &footer; diff --git a/es/news/press-rel-1.sgml b/es/news/press-rel-1.sgml index af7fa0c551..cc4b0ea40b 100644 --- a/es/news/press-rel-1.sgml +++ b/es/news/press-rel-1.sgml @@ -1,62 +1,63 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header;

    FreeBSD utilizado para Generar Espectaculares Efectos Especiales

    Concord, CA, Abril 22, 1999: 32 máquinas con procesador dual y FreeBSD se han utilizdo para generar los efectos especiales de la película The Matrix, de Warner Brothers.

    La empresa Manex Visual Effects ha usado 32 máquinas Dell Precision 410 Dual P-II/450 con FreeBSD como núcleo de renderización. Charles Henrich, administrador de sistemas senior comenta, "Llegamos a un punto en el que no teníamos suficiente -potencia de computación para las secuencias 3-D con nuestra +potencia de computación para las secuencias 3-D con nuestra infraestructura de sistemas existente basada en SGI. Ahí fue cuando decidimos usar una solución basada en FreeBSD, debido a la posibilidad de obtener de manera rápida todo el hardware necesario, además de la facilidad de instalación y adminitración -de FreeBSD. Trabajando con Dell, adquirimos 32 de estos sistemas un +de FreeBSD. Trabajando con Dell, adquirimos 32 de estos sistemas un miércoles, y el sábado por la tarde ya estaban renderizando en producción. Fue un gran esfuerzo por parte de todos, y no creo que esto hubiese sido posible si hubiesemos escogido cualquier otro Sistema Operativo."

    -

    FreeBSD es un potente sistema operativo, con todo el código +

    FreeBSD es un potente sistema operativo, con todo el código fuente de libre distribución basado en el UNIX de la Berkeley Software Distribution. Está disponible gratuitamente en numerosos servidores de Internet y en CD-ROM a través de Walnut Creek CD-ROM, e incluye miles de aplicaciones portadas incluyendo renderización de gráficos 3D y muchas otras herramientas de igual potencia. FreeBSD está optimizado para usar con procesadores Inter x86, corazón de la versatilidad y comodidad de los computadores -personales. Infinitamente personalizable, FreeBSD está en el +personales. Infinitamente personalizable, FreeBSD está en el corazón de las principales aplicaciones de alto rendimiento en Internet como Yahoo! y U.S. West ya que no existen restricciones de licencia y puede ser copiado y modificado libremente.

    -

    Para más información sobre FreeBSD, visitar +

    Para más información sobre FreeBSD, visitar http://www.freebsd.org/ y http://www.cdrom.com/. Para más información sobre Manex Visual Effects, por favor, visitar http://www.mvfx.com/.

    &footer; diff --git a/es/news/press-rel-2.sgml b/es/news/press-rel-2.sgml index 9008f367c5..0f2698c757 100644 --- a/es/news/press-rel-2.sgml +++ b/es/news/press-rel-2.sgml @@ -1,99 +1,100 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header;

    Sistema Completo Integrado de Desarrollo XML con FreeBSD

    Concord, CA, 29 Abril, 1999: Incluido en FreeBSD 3.1 se encuentra integrado un completo sistema de desarrollo XML/SGML que se instala con una simple y fácil de usar secuencia de comandos.

    El sistema de Ports de FreeBSD y la arquitectura multitarea facilitan al desarrollador de XML/SGML la instalación de las últimas -versiones de herramientas y material de referencia necesarios para -desarrollar lenguajes y documentos XML/SGML, mientras las listas de +versiones de herramientas y material de referencia necesarios para +desarrollar lenguajes y documentos XML/SGML, mientras las listas de distribución le ayudan a aprender y mantenerse al día sobre la evolución e implementación XML.

    FreeBSD es un sistema operativo libre que funciona sobre todas las plataformas basadas en Intel x86, Su "Handbook" de 580 páginas ha sido recientemente terminado en formato DocBook, y es un vivo ejemplo de un documento en evolución generado con herramientas SGML. El Handbook está disponible en Internet en:

    -

    El Proyecto de Documentación de FreeBSD también ha +

    El Proyecto de Documentación de FreeBSD también ha puesto a disposición de toda la comuinidad el documento -"FreeBSD Documentation Project Primer" para ayudar en lo posible a los +"FreeBSD Documentation Project Primer" para ayudar en lo posible a los recién llegados que quieran contribuir con el Proyecto de -Documentación. La mayoría de información en este +Documentación. La mayoría de información en este documento es apropiada para todos los usuarios de SGML/XML y está disponible libremente. El documento, que está siendo constantemente actualizado por el equipo del Proyecto de Documentación puede encontrarse en:

    Las características del "Document Project SGML/XML System" incluyen:

    • Jade 1.2.1 y SP versión 1.3.3, permitiendo la validación y maquetación de documentos XML y SGML.
    • Una completa colección de 19 entidades de carácteres ISO SGML.
    • -
    • DoxBook (v2.4.1, v3.0, v3.1), HTML (todas las versiones), y +
    • DoxBook (v2.4.1, v3.0, v3.1), HTML (todas las versiones), y LinuxDoc Document Type Definitions (DTD).
    • Modular DocBook Stylesheets de Norm Walsh, permitiendo un control total sobre la apariencia y formateo de documentos DocBook.
    • Emacs y Xemacs, junto a la extensión PSGML, te ofrecen una solución profesional de edición SGML.
    • El package teTeX-beta junto a las macros JadeTeX hacen posible la conversión de documentos DocBook a formatos DVI, Postscript y PDF con hypervínculos integrados.
    • Se pueden encontrar aplicaciones adicionales relacioneadas con SGML en la colección de Ports de FreeBSD.

    El Proyecto de Documentación de FreeBSD está migrando de LinuxDoc a DocBook DTD, ofreciendo sus experiencias a los desarrolladores de DocBook sobre nuevas características durante el último -año. Para más información sobre el Proyecto de +año. Para más información sobre el Proyecto de Documentación de FreeBSD, por favor, contactar con la lista de distribución freebsd-doc@freebsd.org.

    El sistema operativo FreeBSD está disponible en Internet -en su servidor principal y diferentes mirrors de todo el mundo. +en su servidor principal y diferentes mirrors de todo el mundo. También puede obtenerse en CD-ROM a través de Walnut Creek CDROM. La información sobre todas estas opciones está disponible en:

    &footer; diff --git a/es/news/press-rel-3.sgml b/es/news/press-rel-3.sgml index 275849e7fe..f8e5459fce 100644 --- a/es/news/press-rel-3.sgml +++ b/es/news/press-rel-3.sgml @@ -1,95 +1,96 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header;

    La comunidad BSD da la bienvenida al nuevo Sistema Operativo Libre de Apple

    Concord, CA, 7 Juni0 1999: Hoy, al inicio de la convención anual de la comunidad de desarrollo en UNIX, USENIX, se ha aceptado la inclusión de Apple Computer's Darwin (www.apple.com/darwin) -como nuevo miembro de la familia de sistemas operativos +como nuevo miembro de la familia de sistemas operativos Berkeley Software Distribution (BSD).

    "Estamos encantados de contar con la participación de Apple en la comunidad BSD," comentón Jordan Hubbard, responsable de la sección Freenix del USENIX, y co-fundador del Proyecto FreeBSD. "Cuantas más empresas descubran el increible recurso libre que es -el software BSD, más contribuirán al desarrollo del +el software BSD, más contribuirán al desarrollo del open source, ya que es en su propio interés."

    De acuerdo con Hern Peyerl del Proyecto NetBSD, "Nuestra -interacción con Apple en el Proyecto Darwin ha sido +interacción con Apple en el Proyecto Darwin ha sido extremadamente beneficiosa y gratificante para NetBSD y es el tipo de cooperación que nos gustaría ver más."

    "Basandonos en los 20 años de historia de BSD, permite a los desarrolladores de Apple concentrarse en añadir una única experiencia de usuario al sólido y robusto código BSD", comenta Avie Tevanian, vice presidente senior de Apple. "Creemos que colaborando con el movimiento "open source" conseguiremos mejores productos para los millones de clientes de Mac en todo el mundo. El código BSD en Darwin es una parte esencial en la estrategia de nuestro sistema operativo."

    Este tipo de reciprocidad es un retorno al modelo de desarrollo original existente en los primeros dís de la informática, antes de los PCs. Wilfredo Sanchez, responsable ténico del Proyecto -Darwin hablará sobre el mismo durante la sección Freenix, +Darwin hablará sobre el mismo durante la sección Freenix, una serie de programas pertenecientes al USENIX dedicados exclusivamente a este tipo de desarrollo de software abierto.

    Sobre NetBSD y FreeBSD

    NetBSD y FreeBSD son sistemas operativos libres basados en la última release del UNIX BSD, 4.4BSDLite2. Cada uno de los dos -proyectos se ha mantenido al día en las últimas +proyectos se ha mantenido al día en las últimas tecnologías en procesadores y arquitectura de software. Aun -teniendo diferentes prioridades, los equipos del movimiento BSD +teniendo diferentes prioridades, los equipos del movimiento BSD mantienen una amigable rivalidad. Después de 20 años -de desarrollo, una gran cantidad de software se ha concebido y -desarrollado alrededor de BSD -- incluyendo gran parte de la +de desarrollo, una gran cantidad de software se ha concebido y +desarrollado alrededor de BSD -- incluyendo gran parte de la infraestructura de Internet -- permitiendo el uso efectivo del sistema operativo en practicamente cualquier aplicación. El modelo de -desarrollo abierto significa que no hay secretos, creando un +desarrollo abierto significa que no hay secretos, creando un entendimiento mundial del código para unir el esfuerzo de los desarrolladores sin cerrarse en endémicos sistemas operativos y aplicaciones propietarias.

    Para más información, Contarcar con:

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

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

    &footer; diff --git a/es/news/press.sgml b/es/news/press.sgml index c60caa79b1..35dc552771 100644 --- a/es/news/press.sgml +++ b/es/news/press.sgml @@ -1,811 +1,812 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header; Si falta alguna entrada, por favor envía un mail a www@FreeBSD.ORG

    Diciembre 1999

    Noviembre 1999

    Octube 1999

    Septiembre 1999

    Agosto 1999

    Julio 1999

    Junio 1999

    Mayo 1999

    Abril 1999

    Marzo 1999

    Febrero 1999

      -
    • The Economist +
    • The Economist 20 Febrero 1999
      Hackers Rule
      - Software que ha sido desarrollado por miles de voluntarios y es + Software que ha sido desarrollado por miles de voluntarios y es distribuido libremente. - Nota: El artículo ya no está disponible sin + Nota: El artículo ya no está disponible sin registrarse.

    • Linux Weekly News Febrero 1999
      LWN entrevista a Alan Cox
      - Hay una pequeña pero interesante referencia a FreeBSD en la + Hay una pequeña pero interesante referencia a FreeBSD en la entrevista realizada a Alan Cox.

    January 1999

    December 1998

    November 1998

    - +

    October 1998

    September 1998

    August 1998

    July 1998

    June 1998

    May 1998

    April 1998

    March 1998

    February 1998

    August 1997

    June 1997

    May 1997

    &newshome; &footer; diff --git a/es/news/pressreleases.sgml b/es/news/pressreleases.sgml index aa11922717..09d94886cb 100644 --- a/es/news/pressreleases.sgml +++ b/es/news/pressreleases.sgml @@ -1,46 +1,47 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header;
    7 Junio, 1999
    La comunidad BSD da la bienvenida al nuevo Sistema Operativo Libre de Apple

    29 Abril, 1999
    -Sistema Completo de Desarrollo Integrado XML +Sistema Completo de Desarrollo Integrado XML con FreeBSD.

    22 Abril, 1999: The Matrix
    -FreeBSD usado para Generar Espectaculares Efectos +FreeBSD usado para Generar Espectaculares Efectos Especiales en la película The Matrix de Warner Brothers.

    &footer; diff --git a/es/news/qnewsletter-1-1.sgml b/es/news/qnewsletter-1-1.sgml index c3a3c5845d..cbb385cd80 100644 --- a/es/news/qnewsletter-1-1.sgml +++ b/es/news/qnewsletter-1-1.sgml @@ -1,77 +1,78 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome; | &qnewsletternext; &footer; diff --git a/es/news/qnewsletter-1-2.sgml b/es/news/qnewsletter-1-2.sgml index 33742ed588..aff85c97f2 100644 --- a/es/news/qnewsletter-1-2.sgml +++ b/es/news/qnewsletter-1-2.sgml @@ -1,81 +1,82 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome;
    &qnewsletterprev; | &qnewsletternext; &footer; diff --git a/es/news/qnewsletter-1-3.sgml b/es/news/qnewsletter-1-3.sgml index 40d4694112..a977943c01 100644 --- a/es/news/qnewsletter-1-3.sgml +++ b/es/news/qnewsletter-1-3.sgml @@ -1,99 +1,100 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome;
    &qnewsletterprev; | &qnewsletternext; &footer; diff --git a/es/news/qnewsletter-1-4.sgml b/es/news/qnewsletter-1-4.sgml index 032983b689..a304ef6270 100644 --- a/es/news/qnewsletter-1-4.sgml +++ b/es/news/qnewsletter-1-4.sgml @@ -1,116 +1,117 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome; | &qnewsletterprev; | &qnewsletternext; &footer; diff --git a/es/news/qnewsletter-1-5.sgml b/es/news/qnewsletter-1-5.sgml index 4154451404..28db2ab035 100644 --- a/es/news/qnewsletter-1-5.sgml +++ b/es/news/qnewsletter-1-5.sgml @@ -1,100 +1,101 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome; | &qnewsletterprev; | &qnewsletternext; &footer; diff --git a/es/news/qnewsletter-1-6.sgml b/es/news/qnewsletter-1-6.sgml index d69fdb142f..e8cf372389 100644 --- a/es/news/qnewsletter-1-6.sgml +++ b/es/news/qnewsletter-1-6.sgml @@ -1,85 +1,86 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome; | &qnewsletterprev; | &qnewsletternext; &footer; diff --git a/es/news/qnewsletter-1-7.sgml b/es/news/qnewsletter-1-7.sgml index f677d46fc4..c832925b9d 100644 --- a/es/news/qnewsletter-1-7.sgml +++ b/es/news/qnewsletter-1-7.sgml @@ -1,69 +1,70 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome; | &qnewsletterprev; | &qnewsletternext; &footer; diff --git a/es/news/qnewsletter-2-1.sgml b/es/news/qnewsletter-2-1.sgml index 45cfd132d5..b1b7794fd1 100644 --- a/es/news/qnewsletter-2-1.sgml +++ b/es/news/qnewsletter-2-1.sgml @@ -1,76 +1,77 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome; | &qnewsletterprev; &qnewsletternext; &footer; diff --git a/es/news/qnewsletter-2-2.sgml b/es/news/qnewsletter-2-2.sgml index 2ea48919f9..63f88d566c 100644 --- a/es/news/qnewsletter-2-2.sgml +++ b/es/news/qnewsletter-2-2.sgml @@ -1,86 +1,87 @@ - - + + %navincludes; %includes; %newsincludes; ]> &header; &qnewsletterheader; &qnewsletterfooter; &newshome; &qnewsletterhome; | &qnewsletterprev; &footer; diff --git a/es/news/qnewsletter.sgml b/es/news/qnewsletter.sgml index 49fa57b7c0..4d1fc1755f 100644 --- a/es/news/qnewsletter.sgml +++ b/es/news/qnewsletter.sgml @@ -1,42 +1,43 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header;

    FreeBSD Really-Quick(TM) NewsLetter. Cosas que ocurren en FreeBSD.

    1999

    1998

    &newshome; &footer; diff --git a/es/news/webchanges.sgml b/es/news/webchanges.sgml index 37829728d7..68ca061787 100644 --- a/es/news/webchanges.sgml +++ b/es/news/webchanges.sgml @@ -1,538 +1,539 @@ - - + + %navincludes; %includes; %newsincludes; ]> - + &header; - +

    Esta página lista los cambios visibles en el servidor Web de FreeBSD.

    Mayo 1999

    +

    Abril 1999

    Mazo 1999

    • 30-Mar-1999
      /y2kbug.html Añadida información sobre la página Y2K; se incluye el número de versión arreglada y fecha.

    • 26-Mar-1999
      /news/press.html Añadido: Un Comic de FreeBSD, de User Friendly, serie de Marzo.

    • 24-Mar-1999
      /news/press.html Añadido: A FreeBSD Comic Strip, de User Friendly

    • 14-Mar-1999
      /projects/ Añadido: The Open Directory Project
      /projects/ Añadido: FreeBSD vs. Linux vs. Windows NT
      /news/press.html Añadido: - O'Reilly Open Source - Whence the Source: Untangling the Open + O'Reilly Open Source - Whence the Source: Untangling the Open Source/Free Software Debate, por Thomas Scoville

    • 13-Mar-1999
      /projects/ Añadido: The FreeBSD WebBoard es un lugar de ayuda entre los componentes de la comunidad FreeBSD.
      /releases/3.1R/errata.html Actualizado el fichero ERRATA.TXT de FreeBSD 3.1R.

    • 11-Mar-1999
      /ports/ Added: Y2k Statements

    Febrero 1999

    Enero 1999

    December 1998

      -
    • 27-Dec-1998
      +
    • 27-Dec-1998
      /commercial/software.html Added: Sleepycat Software offers the Berkeley Database product. Berkeley DB is a programmatic toolkit that provides high-performance embedded database support.
      /support.html New name and home for the San Francisco users group.

    • 21-Dec-1998
      /news/webchanges.html Added this page.

    • 19-Dec-1998
      /news/press.html Update URL for: DV Live Magazine: April 98, Who's Serving Who?, by Nels Johnson
      Update URL for: SysAdmin May 1998 Volume 7 Number 5 Security Tools in FreeBSD, by Guy Helmer
      /security/security.html Bring in the new security guide

    • 18-Dec-1998
      /cgi/ports.cgi Move the links 'Sources' and 'Package' after 'Description'.
      /news/press.html Add pointer to Linuxworld article.

    • 17-Dec-1998
      /index.html Remove index.html, replace with index.sgml
      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.
      /releases/2.2.8R/errata.html Better errata fix.

    • 16-Dec-1998
      /commercial/software.html 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).
      /projects/projects.html Added: Linux Threads under FreeBSD

    • 15-Dec-1998
      /internal/photos.html Added a link to page about the FreeBSD-UK meet in Oxford

    • 14-Dec-1998
      /cgi/query-pr-summary.cgi Quote arguments to query-pr so that multi-word arguments can be used in the query.

    • 13-Dec-1998
      /news/newsflash.html Added entry for the FreeBSD Mall.
      - + /news/press.html Added: Mercury Center October 26, 1998 Unix back in the fight with NT, by Miguel Helft
      Added: News.com February 2, 1998 Source code for the masses, by Alex Lash
      /mailto.html Added the FreeBSD Mall to the snail mail section.
      /support.html Added Los Angeles based BSD user group

    • 12-Dec-1998
      /docs.html Added FreeBSD 2.2.8 manual pages.

    • 9-Dec-1998
      /commercial/consulting.html Added HCS Hanseatischer Computerservice GmbH

    • 8-Dec-1998
      - /ports/ + /ports/ Due a bug in INDEX parsing only the run dependencies where printed.
      - /news/press.html + /news/press.html Added: RELEASE 1.0 November 1998 The Open-Source Revolution, by Tim O'Reilly, with an introduction by Esther Dyson.
      - /commercial/hardware.html + /commercial/hardware.html Update for Apache Digital Corporation

    • 6-Dec-1998
      - /y2kbug.html + /y2kbug.html Update info about Y2K fix in groff.
      - /internal/statistic.html + /internal/statistic.html New record for ftp.freebsd.org FTP traffic.
      - /news/press.html + /news/press.html 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.
      - + Added: Linux Today November 20th, 1998 Report from Comdex--Walnut Creek CDROM, FreeBSD and Slackware by Dwight Johnson
      - + Added: CNET News.com June 14, 1998 Nader urges Windows probe, By Jeff Pelline Consumer-rights advocate Ralph Nader mentioned FreeBSD by name.
      - /commercial/software.html + /commercial/software.html Added the Network shell.
      - /ports/ + /ports/ Bugfix in ur.cgi: Dots a vaild parts of a port name (shudder). E.g.: ports/russian/elm.language
      /commercial/consulting.html Added ASG Technologies.

    • 4-Dec-1998
      /news/qnewsletter.html Added Quick NewsLetter Volume #1 Issue #7.

    • 3-Dec-1998
      /news/newsflash.html Announce 2.2.8R.

    &newshome; &footer; diff --git a/es/platforms/alpha.sgml b/es/platforms/alpha.sgml index 8d6e5439ac..31aa88f452 100644 --- a/es/platforms/alpha.sgml +++ b/es/platforms/alpha.sgml @@ -1,46 +1,47 @@ - - + + %navincludes; %includes; ]> &header;

    Esta página contiene información acerca de FreeBSD en los sistemas HP/Compaq Alpha.

    Enlaces específicos de FreeBSD/alpha

    Otros enlaces de interés

    Hardware

    Proyectos

    &footer; diff --git a/es/platforms/i386.sgml b/es/platforms/i386.sgml index ea3827d032..4cb4fde4fd 100644 --- a/es/platforms/i386.sgml +++ b/es/platforms/i386.sgml @@ -1,60 +1,61 @@ - + + %navincludes; %includes; ]> &header;

    Introducción

    Esta página contiene información acerca de la plataforma FreeBSD/i386. Esta arquitectura soporta una extensa variedad de CPU ya que la mayoria de los usuarios compran este tipo de máquinas. Si se tiene una máquina de una compañía de PC (tal como Dell™, HP o eMachines®) lo mas probable es que tenga un CPU AMD™ o Intel®, que pertenecen a esta categoría.

    Índice

    Últimas noticias

      -
    • FreeBSD 6.0 (y versiones posteriores) no soporta - la CPU original Intel 80386; estos sistemas tienen - más de siete añ y sólo FreeBSD - 5.X (y versiones anteriores) las soportan. - El kernel GENERIC incluye soporte para la CPU +

    • FreeBSD 6.0 (y versiones posteriores) no soporta + la CPU original Intel 80386; estos sistemas tienen + más de siete añ y sólo FreeBSD + 5.X (y versiones anteriores) las soportan. + El kernel GENERIC incluye soporte para la CPU 80386 sólamente en FreeBSD 4.X y versiones anteriores.

    Lista de hardware

    -

    Hay una lista de CPU soportadas en +

    Hay una lista de CPU soportadas en las Notas de Hardware de FreeBSD/i386.

    Puntos interesantes

    &footer; diff --git a/es/platforms/pc98.sgml b/es/platforms/pc98.sgml index 68a4538f02..243c674637 100644 --- a/es/platforms/pc98.sgml +++ b/es/platforms/pc98.sgml @@ -1,62 +1,63 @@ - + + %navincludes; %includes; ]> &header; -

    FreeBSD/pc98 es un port de FreeBSD para - la arquitectura NEC PC-98x1 (pc98). +

    FreeBSD/pc98 es un port de FreeBSD para + la arquitectura NEC PC-98x1 (pc98). El objetivo del proyecto es lograr que FreeBSD/pc98 funcione de la misma manera que FreeBSD en otras arquitecturas. Mucho del código fuente del kernel ya está incluido en el árbol de código de FreeBSD y la mayoría de las utilidades de usuario compiladas funcionan bien.

    Notas de hardware para FreeBSD/pc98

    &rel.current;-CURRENT Notas de Hardware - +

    Tareas pendientes

      -
    • Mejorar el sistema de gestión de recursos para +
    • Mejorar el sistema de gestión de recursos para el soporte de recursos discontínuos.
    • Restablecer el soporte para tarjeta de sonido PC-9801-86.
    • Restablecer el soporte para controlador PCMCIA NECIA.
    • Soporte para máquinas SMP.
    • Soporte para controlador SASI.
    • Reescribir boot[12] para soporte del formato binario ELF.
    • HW_MACHINE debe ser 'pc98'.

    Enlaces relacionados con FreeBSD/pc98

    - + &footer; diff --git a/es/platforms/x86-64.sgml b/es/platforms/x86-64.sgml index 7efd6b4c4e..0877fd573c 100644 --- a/es/platforms/x86-64.sgml +++ b/es/platforms/x86-64.sgml @@ -1,25 +1,26 @@ - + + %navincludes; %includes; ]> &title; -

    FreeBSD x86-64 ha cambiado su nombre por el de +

    FreeBSD x86-64 ha cambiado su nombre por el de amd64. Deberá ser automáticamente redirigido a la nueva página del proyecto en unos segundos. Si - esto no sucede, por favor, siga el enlace y actualice + esto no sucede, por favor, siga el enlace y actualice sus marcadores.

    Le rogamos disculpe las molestias.

    diff --git a/es/ports/portindex b/es/ports/portindex index 2bd082cd4f..6b5fbfb603 100755 --- a/es/ports/portindex +++ b/es/ports/portindex @@ -1,266 +1,267 @@ #!/usr/bin/perl # convert a ports INDEX file to HTML # # by John Fieber # 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/ports/i386/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(($ARGV[1] || '.') . '/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 ""; print $fh "$today\">\n"; print $fh ""; print $fh "\n"; + print $fh " %navincludes;\n"; print $fh "\n"; print $fh ""; print $fh "%includes;\n"; print $fh "]>\n"; print $fh "&header;\n"; } sub footer { local ($fh, $ftext) = @_; print $fh "\n$ftext\n"; print $fh "&footer;\n"; print $fh "\n\n"; } sub packages_exist { local($file, *p) = @_; open(P, $file) || do { warn "open $file: $!\n"; warn "Cannot create packages links\n"; return 1; }; while(

    ) { 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(

    ) { # ignore comments next if /^\s*#/; ($category, $description) = /^\s*"([^"]+)",\s*"([^"]+)/; $p{$category} = $description; } close P; return 0; } sub main { $sep = ":"; open(INDEX, $ARGV[0]); while () { chop; s/&/&/g; s//>/g; # Read a record ($name, $loc, $prefix, $desc, $ldesc, $owner, $cats, $bdep, $rdep, $www) = 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} .= "

    $name "; $data{$i} .= "
    $desc
    Long description"; if ($packages{"$name.tgz"}) { $data{$i} .= qq{ | Package}; } $data{$i} .= qq{ | Sources}; if ($www ne "") { $data{$i} .= qq{ | Main Web Site}; } $ownerurl = $owner; $ownerurl =~ s/<//g; $data{$i} .= "
    Maintained by: $owner"; # If there are any dependencies, list them if ($bdep ne "" || $rdep ne "") { $data{$i} .= "
    Requires: "; @dep = split(/ /, "$bdep $rdep"); local($last) = ''; foreach $j (sort @dep) { next if $j eq $last; $last = $j; $data{$i} .= " $j,"; } # 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} .= "
    Also listed in: "; foreach $j (@cat) { if ($j ne $i) { if ($j eq $cat[0]) { $data{$i} .= " \u$j,"; } else { $data{$i} .= " \u$j,"; } } } # remove the trailing comma chop($data{$i}); } $data{$i} .= "

    \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] = "$name " . " -- $desc
    \n"; $portnumber++; } open(MOUTF, ">index.sgml"); &header(MOUTF, "FreeBSD Ports"); # print MOUTF "\n"; print MOUTF "&blurb;"; print MOUTF "

    There are currently $portnumber ports in the FreeBSD Ports Collection.
    Download a gzip'd tar file of all $portnumber ports (about 7 megabytes) or browse the following categories:\n"; print MOUTF "

      \n"; @foos = sort(keys %stats); foreach $key (@foos) { # For the master file... print MOUTF "
    • \u$key ($stats{$key})"; if ($category_description{$key}) { print MOUTF " -- " . $category_description{$key}; } print MOUTF "
    • \n"; # Create the category file open(OUTF, ">$key.sgml"); &header(OUTF, "FreeBSD Ports: \u$key"); if ($category_description{$key}) { print OUTF "

      ", $category_description{$key}, "

      \n"; } print OUTF "
      \n"; $d = join("\n", sort(split(/\n/, $data{$key}))); $d =~ s/##([^#]*)##/$catkey{$1}/g; print OUTF $d; print OUTF "
      \n"; &footer(OUTF, "
      Port Categories" . " -- Index
      "); close(OUTF); } print MOUTF "
    \n"; print MOUTF "\n"; &footer(MOUTF, ""); close(MOUTF); # Create the master index file open(MINDEX, ">master-index.sgml"); &header(MINDEX, "FreeBSD Ports Collection Index"); print MINDEX "

    \n"; print MINDEX sort @master; print MINDEX "

    "; &footer(MINDEX, "
    Port Categories
    "); close(MINDEX); close(INDEX); } diff --git a/es/projects/newbies.sgml b/es/projects/newbies.sgml index 3904c2507a..2a6ad82fe0 100644 --- a/es/projects/newbies.sgml +++ b/es/projects/newbies.sgml @@ -1,263 +1,264 @@ - - + + %navincludes; %includes; ]> - + &header; - +

    Los siguientes recursos son algunos de los que los principiantes en FreeBSD han encontrado de más ayuda cuando estaban aprendiendo a usar el FreeBSD. Por favor, enviad correcciones o añadidos a FreeBSD-Newbies@FreeBSD.org.

    Usando la web de FreeBSD

    - +

    Este sitio web es el principal recurso con la información actualizada sobre FreeBSD. Los principiantes han encontrado las siguientes páginas - de particular ayuda:

    + de particular ayuda:

    • Busca en el manual y la FAQ, o en el sitio web entero, o en los ficheros de las listas de correo de preguntas del FreeBSD.

    • - +
    • La página de Documentación tiene enlaces al Manual y la FAQ, tutoriales, iformación acerca de las contribuciones al Proyecto de Documentación, documentos en otros lenguajes aparte de inglés, y mucho más.

    • - +
    • La página de Soporte es rica en información sobre el FreeBSD, incluyendo listas de correo, grupos de usuarios, sítios web y FTP, información sobre versiones y enlaces - a algunos recursos de información sobre UNIX.

    • + a algunos recursos de información sobre UNIX.

    Aprendiendo FreeBSD

    • Si todavía no la has instalado, busca la última distribución principal. (Mira en el Manual por qué no deberías verte tentado a instalar cualquiera de las otras ramas.) Antes de empezar, lee atentamente las instrucciones de instalación, así como cada uno de los ficheros *.TXT en el directorio FTP o en el CD de instalación. Están allí porque contienen información - que necesitarás. Recoge también la última + que necesitarás. Recoge también la última fe de erratas - desde la web, en el caso que haya sido actualizada.

      + desde la web, en el caso que haya sido actualizada.

      Si te decides a descargar FreeBSD, revisa cuál de estas detallada e ilustradas instrucciones de descarga para una distribución previa están todavía disponibles antes de empezar. Esto debería hacer el proceso entero más claro.

    • - +
    • Varios tutoriales están disponibles. El más popular Para la gente nueva en FreeBSD y Unix es popular entre los muy principiantes. No necesitas saber mucho para disfrutar de éste. También está - disponible en el sítio + disponible en el sítio web del autor y puede ser descargado en formato RTF o postcript para imprimirlo.

    • La primera cosa que mucha gente necesita configurar es el ppp, y hay mucha documentación de ayuda. Puedes empezar como mínimo con aquellas partes de la Guía a fondo de PPP que sean relevantes para tus necesidades, y explorar la página del ppp para enlaces y otra información valiosa y + >página del ppp para enlaces y otra información valiosa y las últimas actualizaciones.

    • FreeBSD al completo por Greg Lehey, publicado por Walnut Creek CDROM. Este libro asume una mínima experiencia en UNIX y lleva al principiante paso a paso a través de cada apartado desde la instalación hasta todo aquello que necesitas saber para configurar y ejecutar un sistema en FreeBSD. También llegas a entender qué estás haciendo y porqué.

    • - -
    • El Manual de FreeBSD y + +

    • El Manual de FreeBSD y Preguntas Frecuentes - Frequently Asked Questions (FAQ) son los principales documentos para FreeBSD. De lectura obligada, contienen mucho material para principiantes así como algun tema bastante avanzado. No te preocupes si no puedes entender alguna de las secciones avanzadas. El manual contiene las instrucciones de instalación y ademas provee listas de libros y recursos en linea, y la FAQ contiene una guía de problemas.

    • - +
    • Apúntate a la lista de correo FreeBSD-Questions para ver aquellas preguntas que te preocupa demasiado hacer y sus respuestas. Subscríbete enviando un correo a majordomo@freebsd.org poniendo "subscribe freebsd-questions" en el cuerpo del mensaje (el asunto no importa). Puedes revisar viejas preguntas y respuestas vía la página de busqueda. Si quieres subscribirte a la lista de correo en español puedes hacerlo enviando un mensaje a freebsd-subscribe@es.freebsd.org

    • - +
    • El principal grupo de discusión de FreeBSD es comp.unix.bsd.freebsd.misc. quizá quieras echarle un ojo a comp.unix.bsd.freebsd.announce también.

    • - +
    • Las páginas del manual son una buena referencia pero no siempre son la mejor introducción para un novel. Cuanto más trabajes con ellas más familiares llegan a ser. Algunas están muy bien para principiantes, o sea que échales un vistazo siempre. La página de manual - del ppp, por ejemplo es más un tutorial.

    • + del ppp, por ejemplo es más un tutorial.

    Aprendiendo UNIX

    Muchos de los problemas que tenemos como principiantes se originan en nuestra falta de familiaridad con los comandos del UNIX necesarios para solventar nuestros problemas en FreeBSD. Sin una formación en UNIX te verás enfrentado a aprender dos cosas a la vez. Afortunadamente, hay un monton de recursos - destinados a hacer esto mas fácil.

    + destinados a hacer esto mas fácil.

    • Hay muchos libros fáciles, como las guías para "Dummies", en cualquier librería importante. Si quieres algo realmente fácil, échale una mirada a lo que hay disponible y elige algo que parezca hablar - en tu mismo idioma. Muy pronto querrás pasar a un libro que te + en tu mismo idioma. Muy pronto querrás pasar a un libro que te procure más cobertura.

    • - +
    • Un libro mencionado frecuentemente por los principiantes es UNIX para impacientes escrito por Paul W. Abrahams y Bruce R. Larson, publicado por Addison-Wesley. Su intención es tanto un libro para aprender - UNIX como una referencia, e incluye una introducción a los conceptos del + UNIX como una referencia, e incluye una introducción a los conceptos del UNIX y un capítulo muy práctico acerca del uso del sistema X Window.

    • - +
    • Otro libro popular es UNIX Power Tools escrito por Jerry Peek, Tim O'Reilly y Mike Loukides, publicado por O'Reilly y Asociados. Está organizado como una serie de artículos cortos, cada uno de los cuales resuelve un problema, y estos artículos contienen referencias cruzadas a otros con material relacionado. Aunque no están dirigidos especificamente a principiantes, el diseño los hace ideales para un principiante con una duda candente o escasos minutos para consultar. Hay material elemental cerca del principio del libro, pero hay pocos artículos fáciles - en su conjunto.

    • - + en su conjunto.

      +
    • La introducción al UNIX está disponible en HTML y formatos - postscript y Acrobat PDF desde la Universidad del Estado de Ohio.

    • - + postscript y Acrobat PDF desde la Universidad del Estado de Ohio.

      +
    • Ayuda de UNIX para Usuarios es otra guía introductoria que está disponible en HTML en un sitio mirror cerca de ti, o que puedes instalar en tu propio sistema.

    • - +
    • Las preguntas sobre UNIX son tratadas en el grupo de discusión comp.unix.questions y en el asociado - Preguntas Frecuentes(FAQ). Puedes conseguir también una copia de la + Preguntas Frecuentes(FAQ). Puedes conseguir también una copia de la FAQ del sítio FTP RMIT. Los principiantes probablemente estarán más interesados inicialmente en las secciones 1 y 2

    • - +
    • Otro interesante grupo de discusión es comp.unix.user-friendly que también tiene una FAQ. - A pesar de que este grupo es para discutir la sencillez operativa cara al + A pesar de que este grupo es para discutir la sencillez operativa cara al usuario, puede contener alguna buena información para los principiantes. - La FAQ + La FAQ también está disponible vía FTP.

    • Muchas otras páginas web contienen listas de turoriales de UNIX y material de referencia. Uno de los mejores sítios para empezar a mirar es la página de UNIX en Yahoo!.

    • - +

    Aprendiendo el sistema X Window

    El sistema X Window es usado por un número de sistemas operativos incluído FreeBSD. La documentación para X se puede encontrar en The XFree86 Project, Inc., incluyendo la XFree86 FAQ. Ten cuidado, mucha de esta documentación es probablemente material de referencia difícil de digerir para los recien llegados.

    • Para información básica acerca de instalar, configurar y usar el sistema X Window, dos de los libros mencionados arriba contienen secciones tratando X al nivel de principiante: FreeBSD al completo y UNIX para impacientes.

    • Hay una sección fácil e informativa en usando el sistema X Window en la Guía del usuario de Linux. Tambieén se puede encontrar material interesante en cualquier parte de ese documento, pero recuerda que Linux no funciona siempre exactamente igual que FreeBSD.

    • Antes de tener funcionando el X de la manera que te gusta, necesitarás escoger un manejador de ventanas. Visita la página Manejadores de Ventanas para X y sigue el enlace desde la introducción para enterarte sobre los manejadores - de ventanas, vuélvete entonces y lee "The Basics". Regresa y compara + de ventanas, vuélvete entonces y lee "The Basics". Regresa y compara los diferentes tipos que hay disponibles.(Bonus: Aquí tambien hay otra guía de UNIX.) La mayoría si no todos de estos manejadores de ventanas se encuentran disponibles para instalar en la colección de ports de FreeBSD.

    Ayudando a otra gente

    Todo el mundo tiene algo con lo que contribuir a la comunidad de FreeBSD, ¡incluso los principiantes! Algunos están ocupados trabajando con el - nuevo grupo de abogacía y algunos de han visto involucrados con el + nuevo grupo de abogacía y algunos de han visto involucrados con el Proyecto de Documentación como - revisores. Otros principiantes en FreeBSD tienen sus propias habilidades y - experiencias para compartir, estén o no relacionadas con los - computadores, o tan solo quieren relacionarse con otros principiantes y + revisores. Otros principiantes en FreeBSD tienen sus propias habilidades y + experiencias para compartir, estén o no relacionadas con los + computadores, o tan solo quieren relacionarse con otros principiantes y quieren hacerles sentir bienvenidos. Siempre hay gente alrededor que ayuda - a otros simplemente porque les gusta. Escribe a + a otros simplemente porque les gusta. Escribe a Principiantes en FreeBSD para más información.

    Los amigos que funcionan bajo FreeBSD son un gran recurso. Ningún libro puede reemplazar hablar por teléfono o por encima de una pizza con alguien que tiene las mismas inquietudes, disfruta con las mismas cosas, - y se enfrenta a los mismos desafíos. Si no tienes muchos amigos que + y se enfrenta a los mismos desafíos. Si no tienes muchos amigos que usen FreeBSD, considera el usar tus viejos CDs de FreeBSD para crearte algunos más :-)

    Los grupos de usuarios son buenos sitios para encontrar a otros usuarios de FreeBSD. Si no hay alguno cerca, quizá puedas iniciar uno.

    - +

    Antes de hablarle a las personas reales acerca de tus nuevas habilidades quizá quieras revisar la Guía de Pronunciación y el Fichero de Jerga :-)

    En línea tenemos la lista de correo Principiantes en FreeBSD para aquellas discusiones no técnicas acerca de asuntos de interés para principiantes. Otra lista de correo, Preguntas de FreeBSD, resuelve nuestras dudas acerca del uso de FreeBSD.

    - + &footer; diff --git a/es/projects/projects.sgml b/es/projects/projects.sgml index 54b806ea25..38cd37edd1 100644 --- a/es/projects/projects.sgml +++ b/es/projects/projects.sgml @@ -1,405 +1,406 @@ - - + + %navincludes; %includes; ]> - + &header;

    Sumándose a la línea de desarrollo principal de FreeBSD, existe una serie de desarrolladores trabajando en la creación de aplicaciones en otras direcciones. Sigue los links siguientes para saber más sobre estos excitantes proyectos.

    Si tienes un proyecto en marcha, por favor, envía la URL y una pequeña descripción (3-10 líneas) a www@FreeBSD.ORG

    Documentación

    • Proyecto de Documentación de FreeBSDEl Proyecto de Documentación de FreeBSD es un grupo de gente que mantiene y escribe la documentación (como el handbook y las FAQ) para el proyecto FreeBSD. Si quieres participar en el proyecto de documentación, subscríbete a la lista freebsd-doc@FeeBSD.ORG y participa.
    • Recursos para principiantes de FreeBSD es una lista de recursos para ayudar a los nuevos usuarios de FreeBSD y UNIX en general. También existe la lista freebsd-newbies@FreeBSD.ORG
    • -
    • +
    • Distribuidores de FreeBSD es una lista de distribuidores a nivel mundial donde se puede comprar FreeBSD.
    • How-to de seguridad en FreeBSD - FreeBSD es un sistema operativo muy seguro. Debido a que el + FreeBSD es un sistema operativo muy seguro. Debido a que el código fuente está disponible libremente, el S.O. es continuamente revisado y auditado. Aquí tienes una serie de consejos sobre como hacer un sistema más seguro.
    • Buscador de RELEASE/SNAP en servidores FTP de FreeBSD. Un recurso que permite a cualquiera buscar un servidor FTP que contenga una release particular y SNAP de FreeBSD. La base de datos es actualizada diariamente a las 3am de Melbourne.
    • [New!] The FreeBSD Diary es una colección de documentos en formato how-to para principiantes en UNIX. El objetivo es ofrecer una serie de guís paso a paso para instalar y configurar diferentes aspectos de FreeBSD.
    • The FreeBSD User Guide - Este es un pequeño documento sobre como empezar con el + Este es un pequeño documento sobre como empezar con el sistema operativo FreeBSD. Está hecho para personas que nunca antes hayan usado un sistema Unix. FreeBSD es un poco complicado de aprender, así que no esperes ser feliz la primera vez que te encuentres a solas con é:l. La razón principal es que es un sistema de Linea de Comandos (CLI), como MS-DOS.
    • A Comprehensive - Guide to FreeBSD - un intento de hacer un tutorial en formato + Guide to FreeBSD - un intento de hacer un tutorial en formato más "leible" explicando el sistema operativo FreeBSD. Pensado para personas nuevas tanto en el mundo Unix como FreeBSD. Actualmente es un trabajo en progreso.
    • FreeBSD - How-To's for the Lazy and Hopeless es otro intento de hacer un + How-To's for the Lazy and Hopeless es otro intento de hacer un documento tipo "how-to" sobre como instalar y configurar FreeBSD.
    • The Linux+FreeBSD mini-HOWTO - Este documento describe como usar Linux y FreeBSD en el mismo sistema. Introduce a FreeBSD y comenta cómo pueden cooperar los dos sistemas.
    • Install Preview for FreeBSD 2.2.7 Una guía explicativa del programa de instalación de FreeBSD para principiantes en Unix y/o FreeBSD.
    • The FreeBSD Programmer's Documentation Project
    • The FreeBSD Cook Book Bién, ya tienes FreeBSD instalado, ¿ahora qué?. - Aquí tienes algunas soluciones que puedes implementar los problemas + Aquí tienes algunas soluciones que puedes implementar los problemas más comunes con los conocimientos que tienes ahora. Este documento esta escrito con estilo de libro de cocina con algunas recetas para la mayoría de instalaciones. Cada "receta" tiene un hardware mínimo recomendado, software específico que usar, y lo - más importante, la configuración requerida para que el + más importante, la configuración requerida para que el sistema funcione correctamente.

    Publicidad y relaciones

    • The FreeBSD Advocacy Project El FreeBSD Advocacy Project es el grupo de personas responsable de la promoción de FreeBSD. El objetivo principal es - desarrollar una imágen de marketing competente para el + desarrollar una imágen de marketing competente para el proyecto FreeBSD e incrementar el número de usuarios de FreeBSD.
    • FreeBSD - Rocks es una iniciativa diseñada para proveer a la comunidad de + Rocks es una iniciativa diseñada para proveer a la comunidad de FreeBSD con las últimas noticias, software y recursos. Todas las áreas incluyen utilidades de búsqueda. Las páginas son actualizadas diariamente y todos estais invitados - a participar o enviar algún artículo. Si algo ha + a participar o enviar algún artículo. Si algo ha ocurrido hoy, lo verás en FreeBSDRocks.
    • - FreeBSD vs. Linux: Diferentes comparaciones entre FreeBSD y Linux, + FreeBSD vs. Linux: Diferentes comparaciones entre FreeBSD y Linux, otro sistema operativo de distribución libre Unix.
    • Daemon News
    • The FreeBSD Counter Page es el inicio de un proyecto para intentar determinar la base de usuarios a nivel mundial de usuarios de FreeBSD. La comunidad de desarrollo de FreeBSD sólo tiene una vaga idea del número de usuarios lo que hace más complicado persuadir a los fabricantes de hardware y software que nos tomen en serio.
    • BSD CD Giveaway List Si alguien tiene un CD para regalar o donar localmente, puede poner su dirección de mail en la lista. Hardware y libros también pueden ser donados. Animamos a la gente a donar CDs a las bibliotecas locales e incluirlas en la lista.
    • The Free Software Bazaar - es un "mercado" diseñado para incrementar el software - libre, ayudar a los desarrolladores de software libre.
    • + es un "mercado" diseñado para incrementar el software + libre, ayudar a los desarrolladores de software libre.
    • FreeBSD ezine El FreeBSD 'zine es una colección mensual de artículos escritos por usuarios y administradores de sistemas FreeBSD como tú.
    • The FreeBSD WebBoard es un lugar donde la comunidad FreeBSD pueden ayudarse unos a otros. Pueden dejar preguntas, y responder o recibir respuestas, mientras que al mismo tiempo otros usuarios de FreeBSD pueden leer tus problemas y aprender de ellos. Ten en cuenta que este sistema es muy nuevo y aun se están añdiendo cosas.
    • The Open Directory Project's es un projecto dedicado a + name="dmoz">The Open Directory Project's es un projecto dedicado a producir el directorio de web más avanzado, gracias a la ayuda de todo un ejército de voluntarios.
    • Comparativa FreeBSD vs. Linux vs. Windows NT
    • The BSD cellphone. Los "FreeBSD daemons" en teléfonos móviles.
    • -
    • Bienvenido a Bienvenido a FreeBSDCon '99, la primera - Conferencia y Exposición anual. Este será el evento + Conferencia y Exposición anual. Este será el evento número uno de este año para usuarios y desarrolladores. Lo - tendremos todo: tutoriales, demos, presentaciones, discusiones, - exhibiciones, etc. Muchos desarrolladores y empresas estarán - allí. Conoce a muchos (posiblmente todos) los componentes del + tendremos todo: tutoriales, demos, presentaciones, discusiones, + exhibiciones, etc. Muchos desarrolladores y empresas estarán + allí. Conoce a muchos (posiblmente todos) los componentes del "core team". Conoce a los administradores de los servidores más potentes del mundo funcionando sobre FreeBSD. Habla con investigadores y desarrolladores de aplicaciones. Prueba en directo las últimas demos de las aplicaciones para FreeBSD.

    Aplicaciones

    Networking

    Sistemas de ficheros

    • Arla es una implementación de cliente AFS libre. El objetivo principal es hacer un cliente totalmente funcional con todas las - posibilidades del AFS normal. Otras cosas planeadas son las + posibilidades del AFS normal. Otras cosas planeadas son las herramientas de gestión y un servidor.
    • Coda es un sistema de ficheros distribuido. Entre otras, algunas de sus características son operaciones desconectadas, un buén model de seguridad, replicación de servidores y cacheo persistente de la parte cliente.
    • DEVFS
    • Mode locking
    • Hacer el interface namei reflexive
    • Servidor y cliente NFS "locking"
    • Driver NTFS para FreeBSD
    • Soft Updates: Una solución a la actualización de Metadatas en Sistemas de Ficheros
    • TCFS es un sistema de ficheros criptográfico transparente y una solució a los problemas de privacidad en sistemas de ficheros distribuidos. Gracias a una profunda integración entre el servicio de encriptació y el sistema de ficheros, resulta - totalmente transparente para el usuario y sus aplicaciones. Los + totalmente transparente para el usuario y sus aplicaciones. Los ficheros son almacenados de formar encriptada y son desencriptados - antes de ser leidos. El proceso de - encriptación/desencriptación tiene lugar en la - máquina del cliente, de manera que la clave de + antes de ser leidos. El proceso de + encriptación/desencriptación tiene lugar en la + máquina del cliente, de manera que la clave de encriptacióon nunca viaja por la red.
    • Tertiary Disk es una arquitectura del sistema de almacenamiento para crear grandes sistemas de almacenamiento que permitan evitar las desventajas de los arrays de disco habituales. Nuestro objetivo es crear un sistema completo de almacenamiento con un ahorro de entre el 30% y 50% del coste sobre los sistemas habituales. Tertiary Disk usa PC's conectados a una red switch para albergar una gran número de discos. Nuestro prototipo consiste en 20 PC's de 200MHz, con 370 discos de 8GB. Los PC's están conectados a través de un switch ethernet de 100MHz.
    • - +
    • Vinum: manager de volúmenes lógicos
    • The - PathConvert project es para desarrollar utilidades de + PathConvert project es para desarrollar utilidades de conversión de nombres entre paths absolutos y paths relativos. Beneficioso para usuarios de NFS y WWW.

    Kernel, seguridad

    Drivers

    Arquitectura

    • Portando FreeBSD a sistemas Alpha
    • Portando FreeBSD a sistemas Sparc
    • La emulación SysVR4 esta página describe un emulador SysVR4 para FreeBSD. Actualmente es capaz de ejecutar un cierta variedad de ejecutables SysV provenientes de Solaris/x86 2.5.1 y 2.6. Creo que también puede ejecutar binarios SCO UnixWare y SCO OpenServer.
    • The OSKit El + href="http://www.cs.utah.edu/projects/flexmach/oskit/">The OSKit El OSKit es una serie de 31 componentes (librerías) orientadas a sistemas operativos, con una extensa documentación.
    • El pequeño FreeBSD (PicoBSD)
    • Linux Threads bajo FreeBSD: - Crear un port de los Threads de Linux que pueda ser compilado y + Crear un port de los Threads de Linux que pueda ser compilado y usado como implementación de threads del kernel bajo FreeBSD. Permite a aplicaciones nativas de Linux lincadas contra - las librerías pthread ejecutarse bajo FreeBSD en + las librerías pthread ejecutarse bajo FreeBSD en modo de emulación de Linux.
    • BUDS: BSD Unix Distributed Simple-ly - Sistema de clustering para desarrollo de sistemas + Sistema de clustering para desarrollo de sistemas paralelo-multi-procesador. Este sistema está pensado para aplicaciones interdependientes de alta complejidad.

    Varios

    &footer; diff --git a/es/publish.sgml b/es/publish.sgml index 5efe09b60b..72f0cc6148 100644 --- a/es/publish.sgml +++ b/es/publish.sgml @@ -1,239 +1,241 @@ - + + %navincludes; %includes; ]> - + &header;
    FreeBSD Daemon
    -Aquí encontrarás las cubiertas de diferentes publicaciones +Aquí encontrarás las cubiertas de diferentes publicaciones relacionadas con FreeBSD. Si conoces alguna publicación/CDROM adicional sobre FreeBSD, por favor, haznoslo saber en la dirección www@freebsd.org, para que podamos añdirlo a este web.

    El Handbook de FreeBSD contiene una considerable bibliografía.

    Pulsa en cualquiera de los gráficos para ver una la imagen mayor.

    Libros

    - +
    - - - +HEIGHT="228" alt="book cover"> - - - - -
    +
    book cover Esta es una reciente publicación (Mayo 1997) de Tatsumi Hosokawa y otros. En el mundo de los libros de informática es un -top-seller en Japón, superando las ventas del libro +top-seller en Japón, superando las ventas del libro "The Road Ahead" de Bill Gates.
    (Libro de FreeBSD en japonés que incluye la +
    book cover(Libro de FreeBSD en japonés que incluye la versión 2.0.5, titulado "FreeBSD: Fun and easy Installation")
    (Libro de FreeBSD en japonés que incluye la +
    book cover(Libro de FreeBSD en japonés que incluye la versión 2.0.5, titulado "FreeBSD Introductory Kit")
    Este es el libro "FreeBSD Complete" de Walnut Creek CDROM con guía de instalación, páginas man y 2 cd's de instalación.
    Libro de Walnut Creek CDROM titulado "Installing & Running FreeBSD", +
    book coverLibro de Walnut Creek CDROM titulado "Installing & Running FreeBSD", que contenía las instrucciones de instalación y dos cd's. Ha sido reemplazado por el más completo "FreeBSD Complete".
    Este libro recientemente publicado (principios de 1997) en Taiwan. +
    book coverEste libro recientemente publicado (principios de 1997) en Taiwan. Su título es "FreeBSD: introduction and applications" y el autor es Jian-Da Li.
    Este es el libro "Getting Started with FreeBSD" de -Fuki-Shuppan. Trata tanto la instalación y entorno japonés como -la administración del sistema e información de bajo nivel (como -el proceso de arranque). FreeBSD-2.2.2R y XFree86-3.2 en CDROM. 264 +
    book cover Este es el libro "Getting Started with FreeBSD" de +Fuki-Shuppan. Trata tanto la instalación y entorno japonés como +la administración del sistema e información de bajo nivel (como +el proceso de arranque). FreeBSD-2.2.2R y XFree86-3.2 en CDROM. 264 páginas, 3,400 yen.
    "Personal Unix Starter Kit - FreeBSD" de ASCII. Incluye +
    book cover"Personal Unix Starter Kit - FreeBSD" de ASCII. Incluye la historia de Unix, una guía de creación de documentación en japonés y cración de ports. 2.1.7.1R y XFree86-3.2 -en CDROM. +en CDROM.
    BSD mit Methode, M. Schulze, B. Roehrig, M. Hoelzer und andere, +
    book coverBSD mit Methode, M. Schulze, B. Roehrig, M. Hoelzer und andere, C&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,-.
    -

    CDROMs

    Para más información sobre las releases -más recientes a la página de +

    CDROMs

    Para más información sobre las releases +más recientes a
    la página de información de releases de FreeBSD.

    - -
    Este es el BSDisc de InfoMagic, conteniendo FreeBSD 2.0 + + - - - - - - - - - - - - - + - - + - - - - - -
    CDROM cover Este es el BSDisc de InfoMagic, conteniendo FreeBSD 2.0 y NetBSD 1.0 en un solo CD.
    Esta es la release original de 4.4 BSD Lite2 de UC +
    CDROM coverEsta es la release original de 4.4 BSD Lite2 de UC Berkeley, la tecnología básica de FreeBSD.
    La primera de las series "BSD" de Laser5. Contiene +
    CDROM coverLa primera de las series "BSD" de Laser5. Contiene FreeBSD-2.0.5R, NetBSD-1.0, XFree86-3.1.1 y el kernel FreeBSD(98).
    The second of Laser5's "BSD" series. From this version, the CDs come +
    CDROM coverThe 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).
    This is the Laser5 Japanese edition of the +
    CDROM coverThis is the Laser5 Japanese edition of the FreeBSD CDROM. It is a 4 CD set.
    This is the only FreeBSD CD Pacific Hitech produced before merging their +
    CDROM coverThis 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.
    This is the cover disc from the Korean magazine. +
    CDROM coverThis is the cover disc from the Korean magazine. Note the creative cover art! The CD contains the FreeBSD 2.2.1 release with some local additions.
    This is it - the very first FreeBSD CD published! Both the FreeBSD +
    CDROM coverThis 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.
    This was the second FreeBSD CD published by Walnut Creek CDROM and also the +
    CDROM coverThis 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.
    This unusual CD is something of a collector's item now given that almost +
    CDROM coverThis 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. +a trade show.
    This is the fixed-up version of the FreeBSD 2.0 CD. +
    CDROM coverThis 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.
    The FreeBSD 2.0.5 release CD. This was the first CD to feature Tatsumi Hosokawa's daemon +
    CDROM coverThe FreeBSD 2.0.5 release CD. This was the first CD to feature Tatsumi Hosokawa's daemon artwork.
    The FreeBSD 2.1 release CD. This was the first CD release on the 2.1 branch +
    CDROM coverThe FreeBSD 2.1 release CD. This was the first CD release on the 2.1 branch (the last being 2.1.7).
    The FreeBSD 2.1.5 release CD.
    CDROM coverThe FreeBSD 2.1.5 release CD.
    The FreeBSD 2.1.6 release CD.
    The Japanese version of 2.1.6. This was the first and last Japanese +
    CDROM coverThe FreeBSD 2.1.6 release CD.
    CDROM coverThe 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.
    The FreeBSD 2.1.7 release CD. Also the last CD released on the 2.1.x +
    CDROM coverThe 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
    An early release SNAPshot of 2.2 (done before 2.2.1 was released). +
    CDROM coverAn early release SNAPshot of 2.2 (done before 2.2.1 was released).
    The FreeBSD 2.2.1 release CD. This was the first CD on the 2.2 branch. +
    CDROM coverThe FreeBSD 2.2.1 release CD. This was the first CD on the 2.2 branch.
    The FreeBSD 2.2.2 release CD. +
    CDROM coverThe FreeBSD 2.2.2 release CD.
    The FreeBSD 3.0 snapshot CD. +
    CDROM coverThe FreeBSD 3.0 snapshot CD.
    The FreeBSD mailing list and newsgroup archives, turned into HTML and +
    CDROM coverThe 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...

    Magazines

    - -
    Cover of Korean UNIX magazine, May 1997 issue. + + - - -
    magazine coverCover of Korean UNIX magazine, May 1997 issue. Also included FreeBSD 2.2.1 with cover CDs.
    UNIX User Magazine -November 1996 issue. +
    magazine coverUNIX User Magazine +November 1996 issue. Also included FreeBSD 2.1.5 on cover CD.
    This is the "FreeBSD Full Course" special in April 1997's Software +
    magazine coverThis 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.
    +
    magazine cover Quality Unix for FREE, by Brett Glass in Sm@rt Reseller Online September 1998

    Newsletters

    - -
    + + -
    newsletter cover This is issue #1 of the FreeBSD Newsletter, published and distributed free of charge by Walnut Creek CDROM. You can -register to receive it. -Submit articles/make comments by sending email to +register to receive it. +Submit articles/make comments by sending email to newsletter@FreeBSD.ORG.
    +
    newsletter cover This is issue #2 of the FreeBSD Newsletter, published and distributed free of charge by Walnut Creek CDROM. You can -register to receive it. -Submit articles/make comments by sending email to +register to receive it. +Submit articles/make comments by sending email to newsletter@FreeBSD.ORG.
    questions@FreeBSD.ORG
    Copyright © 1995-1997 FreeBSD Inc. - All rights reserved.
    $FreeBSD: www/es/publish.sgml,v 1.2 1999/09/06 07:02:59 peter Exp $
    + All rights reserved.
    $FreeBSD: www/es/publish.sgml,v 1.3 1999/09/13 13:37:47 jesusr Exp $ +&footer; diff --git a/es/releases/2.0.5R/announce.sgml b/es/releases/2.0.5R/announce.sgml index 816a498f2f..0a6a16c253 100644 --- a/es/releases/2.0.5R/announce.sgml +++ b/es/releases/2.0.5R/announce.sgml @@ -1,115 +1,116 @@ - - + + %navincludes; %includes; ]> - + &header;

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

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

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

    Highlights of this release are:

    • Multi-lingual documentation files.
    • Completely menu driven installation.
    • More installation media types.
    • Support for a much larger range of PC hardware.
    • Easy mounting of DOS partitions and CD devices mounted automatically.
    • "Canned" installation types for easy installs.
    • Easy post-configuration menu

    And many other new features and bug fixes.

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

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

    The usual locations:

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

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

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

    Thank you!

    Jordan


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

    Yes, you have guessed it. As a result of the recent feedback we have had about the original 2.0.5-RELEASE, we have gone poking and found a couple of bugs on the original boot.flp image. There is now a /pub/FreeBSD/2.0.5-RELEASE/UPDATES directory on ftp.cdrom.com and freefall.cdrom.com with a version of boot.flp which will fix the following problems:

    • The kernel was too big to boot on 4Mb machines.
    • It was possible to specify the filesystem mount points in such a way that the program would mount the filesystem before the parent filesystem was mounted (e.g. it would mount /usr/local and then /usr)

    As the CDROM has not gone to replication yet, this updated floppy image will be appearing on the CDROM.

    Sorry to all those who had problems with the first boot floppy set - I will personally nail Jordan to his chair and nail the chair to the floor in front of his computer the next time we roll a release!

    Gary

    Release Home &footer; diff --git a/es/releases/2.0.5R/notes.sgml b/es/releases/2.0.5R/notes.sgml index 03dd8766b6..8fc4c54600 100644 --- a/es/releases/2.0.5R/notes.sgml +++ b/es/releases/2.0.5R/notes.sgml @@ -1,764 +1,765 @@ - - + + %navincludes; %includes; ]> - + &header;
                                      RELEASE NOTES
                                         FreeBSD
                                      Release 2.0.5
     
     1. Technical overview
     ---------------------
     
     FreeBSD is a freely available, full source 4.4 BSD Lite based release
     for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
     primarily on software from U.C. Berkeley's CSRG group, with some
     enhancements from NetBSD, 386BSD, and the Free Software Foundation.
     
     Since our release of FreeBSD 2.0 some 8 months ago, the performance,
     feature set, and stability of FreeBSD has improved dramatically.  The
     largest change is a revamped VM system with a merged VM/file buffer
     cache that not only increases performance, but reduces FreeBSD's
     memory footprint, making a 4MB configuration a more acceptable
     minimum.  Other enhancements include full NIS client and server
     support, transaction TCP support, dial-on-demand PPP, an improved SCSI
     subsystem, early ISDN support, support for FDDI and Fast Ethernet
     (100Mbit) adapters, improved support for the Adaptec 2940 (WIDE and
     narrow) and many hundreds of bug fixes.
     
     We've also taken the comments and suggestions of many of our users to
     heart and have attempted to provide what we hope is a more sane and
     easily understood installation process.  Your feedback on this
     (constantly evolving) process is especially welcome!
     
     In addition to the base distributions, FreeBSD offers a new ported
     software collection with some 270 commonly sought-after programs.  The
     list of ports ranges from http (WWW) servers, to games, languages,
     editors and almost everything in between.  The entire ports collection
     requires only 10MB of storage, all ports being expressed as "deltas"
     to their original sources.  This makes it much easier for us to update
     ports, and greatly reduces the disk space demands made by the older
     1.0 ports collection.  To compile a port, you simply change to the
     directory of the program you wish to install, type make and let the
     system do the rest.  The full original distribution for each port you
     build is retrieved dynamically off of CDROM or a local ftp site, so
     you need only enough disk space to build the ports you want.  (Almost)
     every port is also provided as a pre-compiled "package" which can be
     installed with a simple command (pkg_add) by those who do not wish to
     compile their own ports from source.  See the file:
             /usr/share/FAQ/Text/ports.FAQ
     for a more complete description of the ports collection.
     
     
     Since our first release of FreeBSD 1.0 nearly two years ago, FreeBSD
     has changed almost entirely.  A new port from the Berkeley 4.4 code
     base was done, which brought the legal status of the system out of the
     shadows with the blessing of Novell (the new owners of USL and UNIX).  The
     port to 4.4 has also brought in a host of new features, filesystems
     and enhanced driver support.  With our new unencumbered code base, we
     have every reason to hope that we'll be able to release quality
     operating systems without further legal encumbrance for some time to
     come!
     
     FreeBSD 2.0.5 represents the culmination of 2 years of work and many
     thousands of man hours put in by an international development team.
     We hope you enjoy it!
     
     A number of additional documents which you may find very helpful in
     the process of installing and using FreeBSD may also be found in
     the "FAQ" directory, either under /usr/share/FAQ on an installed
     system or at the top level of the CDROM or FTP distribution from
     where you're reading this file.  Please consult FAQ/Text/ROADMAP
     for a brief description of the resources provided by the FAQ directory.
     
     For a list of contributors and a general project description, please see
     the file "CONTRIB.FreeBSD" which should be bundled with your binary
     distribution.
     
     Also see the "REGISTER.FreeBSD" file for information on registering
     with the "Free BSD user counter".   This counter is for ALL freely
     available variants of BSD, not just FreeBSD, and we urge you to register
     yourself with it.
     
     The core of FreeBSD does not contain DES code which would inhibit its
     being exported outside the United States.  There is an add-on package
     to the core distribution, for use only in the United States, that
     contains the programs that normally use DES.  The auxiliary packages
     provided separately can be used by anyone.   A freely (from outside the
     U.S.) exportable European distribution of DES for our non-U.S. users also
     exists and is described in the FreeBSD FAQ.
     
     If password security for FreeBSD is all you need, and you have no
     requirement for copying encrypted passwords from different hosts
     (Suns, DEC machines, etc) into FreeBSD password entries, then
     FreeBSD's MD5 based security may be all you require!  We feel that our
     default security model is more than a match for DES, and without any
     messy export issues to deal with.  If you're outside (or even inside)
     the U.S., give it a try!
     
     
     1.1 What's new in 2.0.5?
     ------------------------
     
     The following features were added or substantially improved between
     the release of 2.0 and this 2.0.5 release.  In order to facilitate
     better communication, the person, or persons, responsible for each
     enhancement is noted.  Any questions regarding the new functionality
     should be directed to them first.
     
     KERNEL:
     
     Merged VM-File Buffer Cache
     ---------------------------
     A merged VM/buffer cache design greatly enhances overall system
     performance and makes it possible to do a number of more optimal
     memory allocation strategies that were not possible before.
     
     Owner:                  David Greenman (davidg@FreeBSD.org) and
                             John Dyson (dyson@implode.root.com)
     
     
     Network PCB hash optimization
     -----------------------------
     For systems with a great number of active TCP connections (WEB and ftp
     servers, for example), this greatly speeds up the lookup time required
     to match an incoming packet up to its associated connection.
     
     Owner:                  David Greenman (davidg@FreeBSD.org)
     
     
     Name cache optimization
     -----------------------
     The name-cache would cache all files of the same name to the same bucket,
     which would put for instance all ".." entries in the same bucket.  We added
    -the parent directory version to frustrate the hash, and improved the 
    +the parent directory version to frustrate the hash, and improved the
     management of the cache in various other ways while we were at it.
     
     Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
                             David Greenman (davidg@FreeBSD.org)
     
     
     Less restrictive swap-spaces
     ----------------------------
     The need to compile the names of the swap devices into the kernel has been
     removed.  Now swapon will accept any block devices, up to the maximum
     number of swap devices configured in the kernel.
     
     Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
                             David Greenman (davidg@FreeBSD.org)
     
     
     Hard Wired SCSI Devices
     -----------------------
     Prior to 2.0.5, FreeBSD performed dynamic assignment of unit numbers
     to SCSI devices as they were probed, allowing a SCSI device failure to
     possibly change unit number assignment and prevent filesystems on
     still functioning disks from mounting.  Hard wiring allows static
     allocation of unit numbers (and hence device names) to scsi devices
     based on SCSI ID and bus.  SCSI configuration occurs in the kernel
     config file.  Samples of the configuration syntax can be found in the
     scsi(4)>
     man page or the LINT kernel config file.
     
     Owner:                  Peter Dufault (dufault@hda.com)
     Sources involved:       sys/scsi/* usr.sbin/config/*
     
     
     Slice Support
     -------------
     FreeBSD now supports a "slice" abstraction which makes it more
     completely interoperable with other operating system partitions.  This
     support will allow FreeBSD to inhabit DOS extended partitions.
     
     Owner:                  Bruce Evans (bde@FreeBSD.org)
     Sources involved:       sys/disklabel.h sys/diskslice.h sys/dkbad.h
                             kern/subr_diskslice.c kern/subr_dkbad.c
                             i386/isa/diskslice_machdep.c
                             i386/isa/wd.c scsi/sd.c dev/vn/vn.c
     
     
     Support for Ontrack Disk Manager Version 6.0
     --------------------------------------------
     Support has been added for disks which use Ontrack Disk Manager.  The
     fdisk program does NOT know about it however, so make all changes
     using the install program on the boot.flp or the Ontrack Disk Manager
     tool under DOS.
     
     Owner:                  Poul-Henning Kamp (phk@FreeBSD.org)
     
     
     Bad144 is back and working
     --------------------------
     Bad144 works again, though the semantics are slightly different than
     before in that the bad-spots are kept relative to the slice rather
     than absolute on the disk.
     
     Owner:                  Bruce Evans (bde@FreeBSD.org)
                             Poul-Henning Kamp (phk@FreeBSD.org)
     
     
     NEW DEVICE SUPPORT:
     
                             SCSI and CDROM Devices
     
     Matsushita/Panasonic (Creative) CD-ROM driver
     ---------------------------------------------
     The Matsushita/Panasonic CR-562 and CR-563 drives are now supported
     when connected to a Sound Blaster or 100% compatible host adapter.  Up
     to four host adapters are supported for a total of 16 CD-ROM drives.
    -The audio functions are supported, along with access to the raw (2352 byte) 
    +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            
    +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 
    +This driver supports any of the numerous NICs using the DC21140 chipset
     including the 100Mb DEC DE-500-XA and SMC 9332.
     
     Owner:                  core
     Submitted by:           Matt Thomas (thomas@lkg.dec.com)
     Sources involved:       pci/if_de.c pci/dc21040.h
     
     
     DEC FDDI (DEFPA/DEFEA) driver
     -----------------------------
     Owner:                  core
     Submitted by:           Matt Thomas (thomas@lkg.dec.com)
     Sources involved:       pci/if_pdq.c pci/pdq.c pci/pdq_os.h pci/pdqreg.h
     
     
     3Com 3c505 (Etherlink/+) NIC driver
     -----------------------------------
     Owner:                  core
     Submitted by:           Dean Huxley (dean@fsa.ca)
     Obtained from:          NetBSD
     Sources involved:       isa/if_eg.c
     
     
     Fujitsu MB86960A family of NICs driver
     -------------------------------------
     Owner:                  core
     Submitted by:           M.S. (seki@sysrap.cs.fujitsu.co.jp)
     Sources involved:       isa/if_fe.c
     
     
     Intel EtherExpress driver
     -------------------------
     Owner:                  Rodney W. Grimes (rgrimes@FreeBSD.org)
     Sources involved:       isa/if_ix.c isa/if_ixreg.h
     
     
     3Com 3c589 driver
     -----------------
     Owner:                  core
     Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
                             Seiji Murata (seiji@mt.cs.keio.ac.jp) and
                             Noriyuki Takahashi (hor@aecl.ntt.jp)
     Sources involved:       isa/if_zp.c
     
     
     IBM Credit Card Adapter driver
     ------------------------------
     Owner:                  core
     Submitted by:           "HOSOKAWA Tatsumi" (hosokawa@mt.cs.keio.ac.jp),
     Sources involved:       isa/pcic.c isa/pcic.h
     
     
     EDSS1 and 1TR6 ISDN interface driver
     ------------------------------------
     Owner:                  core
     Submitted by:           Dietmar Friede (dfriede@drnhh.neuhaus.de) and
                             Juergen Krause (jkr@saarlink.de)
     Sources involved:       gnu/isdn/*
     
     
                             Miscellaneous Drivers
     
     Joystick driver
     ---------------
     Owner:                  Jean-Marc Zucconi (jmz@FreeBSD.org)
     Sources involved:       isa/joy.c
     
     
     National Instruments "LabPC" driver
     -----------------------------------
     Owner:                  Peter Dufault (dufault@hda.com)
     Sources involved:       isa/labpc.c
     
     
     WD7000 driver
     -------------
     Owner:                  Olof Johansson (offe@ludd.luth.se)
     
     
     Pcvt Console driver
     -------------------
     Owner:                  Joerg Wunsch (joerg@FreeBSD.org)
     Submitted by:           Hellmuth Michaelis (hm@altona.hamburg.com)
     Sources involved:       isa/pcvt/* usr.sbin/pcvt/*
     
     
     BSD-audio emulator for VAT driver
     ---------------------------------
     Owner:                  Amancio Hasty (ahasty@FreeBSD.org) and
                             Paul Traina (pst@FreeBSD.org)
     Sources involved:       isa/sound/vat_audio.c isa/sound/vat_audioio.h
     
     
     National Instruments AT-GPIB and AT-GPIB/TNT GPIB driver
     --------------------------------------------------------
     Owner:                  core
     Submitted by:           Fred Cawthorne (fcawth@delphi.umd.edu)
     Sources involved:       isa/gpib.c isa/gpib.h isa/gpibreg.h
     
     
     Genius GS-4500 hand scanner driver
     ----------------------------------
     Owner:                  core
     Submitted by:           Gunther Schadow (gusw@fub46.zedat.fu-berlin.de)
     Sources involved:       isa/gsc.c isa/gscreg.h
     
     
     CORTEX-I Frame Grabber
     ----------------------
     Owner:                  core
     Submitted by:           Paul S. LaFollette, Jr.
     Sources involved:       isa/ctx.c isa/ctxreg.h
     
     
     Video Spigot video capture card
     -------------------------------
     Owner:                  Jim Lowe
     
     
     
     1.2 Experimental features
     -------------------------
     
     The unionfs and LFS file systems are known to be severely broken in
     2.0.5.  This is in part due to old bugs that we haven't had time to
     resolve yet and the need to update these file systems to deal with the
     new VM system.  We hope to address these issues in a later release of
     FreeBSD.
     
     FreeBSD now supports running iBCS2 compatible binaries (currently SCO
     UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).  The iBCS2
     emulator is in its early stages, but it is functional, we haven't been
     able to do exhaustive testing (lack of commercial apps), but almost
     all of SCO's 3.2.2 binaries are working, so is an old INFORMIX-2.10
     for SCO. Further testing is necessary to complete this project. There
     is also work under way for ELF & XOUT loaders, and most of the svr4
     syscall wrappers have been written.
     
     FreeBSD also implements enough of its Linux compatibility that we
     can now run Linux DOOM!  See the ``xperimnt'' directory (on your local
     FTP server or CDROM) for full docs on how to set this up.
     
     Owner:                  Soren Schmidt (sos) & Sean Eric Fagan (sef)
     Sources involved:       sys/i386/ibcs2/* + misc kernel changes.
     
     
     2. Supported Configurations
     ---------------------------
     
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     Following is a list of all disk controllers and ethernet cards currently
     known to work with FreeBSD.  Other configurations may very well work, and
     we have simply not received any indication of this.
     
     
     2.1. Disk Controllers
     ---------------------
     
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     WD7000
     IDE
     ATA
     
     Adaptec 152x series ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes
     the AHA-152x and SoundBlaster SCSI cards.
     
     ** Note: You cannot boot from the SoundBlaster cards as they have no
        on-board BIOS, which is necessary for mapping the boot device into the
        system BIOS I/O vectors.  They're perfectly usable for external tapes,
        CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
        without a boot ROM.  Some systems DO have a boot ROM, which is generally
        indicated by some sort of message when the system is first powered up
        or reset.  Check your system/board documentation for more details.
     
     [Note that Buslogic was formerly known as "Bustec"]
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     Buslogic 956c PCI SCSI controller
     
     NCR 53C810 and 53C825 PCI SCSI controller.
    -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     UltraStor 14F, 24F and 34F SCSI controllers.
     
     Seagate ST01/02 SCSI controllers.
     
     Future Domain 8xx/950 series SCSI controllers.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
     DAT) and CD ROM drives.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI (also includes ProAudio Spectrum and SoundBlaster SCSI)
    -(mcd)   Mitsumi proprietary interface 
    +(mcd)   Mitsumi proprietary interface
     (matcd) Matsushita/Panasonic (Creative) proprietary interface
     (scd)   Sony proprietary interface
     
     Note: CD-Drives with IDE interfaces are not supported at this time.
     
     Some controllers have limitations with the way they deal with >16MB of
     memory, due to the fact that the ISA bus only has a DMA address space
     of 24 bits.  If you do your arithmetic, you'll see that this makes it
     impossible to do direct DMA to any address >16MB.  This limitation is
     even true of some EISA controllers (which are normally 32 bit) when
     they're configured to emulate an ISA card, which they then do in *all*
     respects.  This problem is avoided entirely by IDE controllers (which
     do not use DMA), true EISA controllers (like the UltraStor, Adaptec
     1742A or Adaptec 2742) and most VLB (local bus) controllers.  In the
     cases where it's necessary, the system will use "bounce buffers" to
     talk to the controller so that you can still use more than 16Mb of
     memory without difficulty.
     
     
     2.2. Ethernet cards
     -------------------
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra is also supported.
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21140 based NICs (SMC???? DE???)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A family of NICs
     
     Intel EtherExpress
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
     
     Toshiba ethernet cards
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     
     2.3. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     
     BOCA ATIO66 6 port serial card using shared IRQ.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     Mitsumi (all models) CDROM interface and drive.
     
     SDL Communications Riscom/8 Serial Board.
     
     SoundBlaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
     
     Matsushita/Panasonic (Creative SoundBlaster) CDROM interface and drive.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards.
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
     support is apparently close to materializing.  Details will be posted
     as the situation develops.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     1. FTP/Mail
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the nearest site
     to you netwise.
     
     If you do not have access to the internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
     to get more information on how to fetch files from ftp.freebsd.org.
     Note: This approach will end up sending many *tens of megabytes*
     through the mail, and should only be employed as an absolute LAST
     resort!
     
     
     2. CDROM
     
     FreeBSD 2.0.5 may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
     
     Or via the internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp as:
             ftp://ftp.cdrom.com/cdrom/catalog.
     
     Cost per CD is $39.95, or $24.95 with a FreeBSD subscription.  With
     a subscription, you will automatically receive updates as they
     are released.  Your credit card will be billed when each disk is shipped
     and you may cancel your subscription at any time without further obligation.
     
     Walnut Creek CDROM also sells a full line of FreeBSD related merchandise such
     as T-shirts ($14.95, available in "child", Large and XL sizes), coffee mugs
     ($9.95), tattoos ($0.25 each) and posters ($3.00).
     
     Shipping (per order not per disc) is $5 in the US, Canada or
     Mexico and $9.00 overseas.  They accept Visa, Mastercard, Discover,
     American Express or checks in U.S. Dollars and ship COD within the
     United States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     Reporting problems, making suggestions, submitting code
     -------------------------------------------------------
     
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached if you can!).
     
     The preferred method to submit bug reports from a machine with
     internet mail connectivity is to use the send-pr command.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     bugs@FreeBSD.org
     
     
     Otherwise, for any questions or suggestions, please send mail to:
     
                     questions@FreeBSD.org
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more enhancements
     to be done than we can ever manage to do by ourselves!  To contact us
     on technical matters, or with offers of help, you may send mail to:
     
                     hackers@FreeBSD.org
     
     Since these mailing lists can experience significant amounts of
     traffic, if you have slow or expensive mail access and you are
     only interested in keeping up with significant FreeBSD events, you may
     find it preferable to subscribe to:
     
                     announce@FreeBSD.org
     
     
     All but the freebsd-bugs groups can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  It would be very difficult, if not
     impossible, to enumerate everyone who's contributed to FreeBSD, but
     nonetheless we shall try (in alphabetical order, of course). If your
     name is not mentioned, please be assured that its omission is entirely
     accidental.
     
     
     The Computer Systems Research Group (CSRG), U.C. Berkeley.
     
     Bill Jolitz, for his initial work with 386BSD.
     
     The FreeBSD Core Team
     (in alphabetical order by first name):
     
             Andreas Schulz <ats@FreeBSD.org>
             Andrey A. Chernov <ache@FreeBSD.org>
             Bruce Evans <bde@FreeBSD.org>
             David Greenman <davidg@FreeBSD.org>
             Garrett A. Wollman <wollman@FreeBSD.org>
             Gary Palmer <gpalmer@FreeBSD.org>
             Geoff Rehmet <csgr@FreeBSD.org>
             Jack Vogel <jackv@FreeBSD.org>
             John Dyson <dyson@FreeBSD.org>
             Jordan K. Hubbard <jkh@FreeBSD.org>
             Justin Gibbs <gibbs@FreeBSD.org>
             Paul Richards <paul@FreeBSD.org>
             Poul-Henning Kamp <phk@FreeBSD.org>
             Rich Murphey <rich@FreeBSD.org>
             Rodney W. Grimes <rgrimes@FreeBSD.org>
             Satoshi Asami <asami@FreeBSD.org>
             Søren Schmidt <sos@FreeBSD.org>
     
     Special mention to:
     
             Walnut Creek CDROM, without whose help (and continuing support)
             this release would never have been possible.
     
             Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
             drive.
     
             Additional FreeBSD helpers and beta testers:
     
             J.T. Conklin                            Julian Elischer
             Frank Durda IV                          Peter Dufault
             Sean Eric Fagan                         Jeffrey Hsu
             Terry Lambert                           L Jonas Olsson
             Chris Provenzano                        Dave Rivers
             Guido van Rooij                         Steven Wallace
             Atsushi Murai                           Scott Mace
             Nate Williams
     
             And everyone at Montana State University for their initial support.
     
     
     Jordan would also like to give special thanks to Poul-Henning Kamp and
     Gary Palmer, both of whom put in long hours helping him to construct
     the new installation utility.  Poul, being a proud new father, was
     especially pressed for time and yet somehow managed to put in
     a significant amount of effort anyway.  This release could not have
     happened without him!  Thank you both!
     
     Thanks also to everyone else who helped, especially those not
     mentioned, and we sincerely hope you enjoy this release of FreeBSD!
     
     
                             The FreeBSD Core Team
     
    -Id: RELNOTES.FreeBSD,v 1.7 1995/05/28 19:49:57 jkh Exp 
    +Id: RELNOTES.FreeBSD,v 1.7 1995/05/28 19:49:57 jkh Exp
     

    Release Home &footer; diff --git a/es/releases/2.0/announce.sgml b/es/releases/2.0/announce.sgml index ac5ef4634b..55bf7c94ac 100644 --- a/es/releases/2.0/announce.sgml +++ b/es/releases/2.0/announce.sgml @@ -1,156 +1,157 @@ - - + + %navincludes; %includes; ]> &header;

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

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

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

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

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

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

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

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

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

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

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

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

    • Primary ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE
    • U.S-2 ftp://ftp.dataplex.net/pub/FreeBSD/2.0-RELEASE
    • U.S-3 ftp://kryten.atinc.com/pub/FreeBSD/2.0-RELEASE
    • U.S-4 ftp://ref.tfs.com/pub/FreeBSD/2.0-RELEASE
    • Taiwan ftp://netbsd.csie.nctu.edu.tw/pub/FreeBSD/2.0-RELEASE
    • Australia ftp://ftp.physics.usyd.edu.au/FreeBSD/2.0-RELEASE
    • France ftp://ftp.ibp.fr/pub/freeBSD/2.0-RELEASE
    • Finland ftp://nic.funet.fi:/pub/unix/FreeBSD/2.0-RELEASE
    • Russia ftp://ftp.kiae.su/FreeBSD/2.0-RELEASE

    (Translated for the non-URL literate: FreeBSD is available for anonymous ftp on ftp.freebsd.org in the pub/FreeBSD/2.0-RELEASE directory)

    It will also, no doubt, be available on a number of mirror sites as soon as they pick it up. However, ftp.freebsd.org is on a T3 line and supports 300 simultaneous users (it's a FreeBSD machine :-), so it's unlikely that you'll have too much trouble getting it from this site until the mirrors do so.

    If you are directly Internet connected, it is also NOT necessary to load the bindist from this site! Simply download the 2 boot floppies, begin the installation, and select the FTP installation method - it will do the rest for you, transparently.

    Finally, we'd like to publically *thank* Walnut Creek CDROM, without whos continuing support and extreme generousity, we'd probably be long gone! They've been of immense help to us.

    Thanks must also go to Poul-Henning Kamp, our fearless and long suffering release engineer for 2.0. While all of us have sacrificed much sleep to the cause, he has a new wife but has somehow managed to do so as well! :-)

    And to all of our users (this is probably starting to sound like the academy awards :-), a similar thank you! We couldn't have done it without your constant flow of commentary, patches, donations of code and moral support. As corny as it sounds, we do it all for you folks! [Though the ego gratification is nice too :-)]

    Thanks to all, and we sincerely hope you enjoy this release!

    Comments, as always, to hackers@FreeBSD.org.

    Jordan
    [on behalf of the FreeBSD Project team]

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

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

    Release Home &footer; diff --git a/es/releases/2.0/notes.sgml b/es/releases/2.0/notes.sgml index 2a453c4eef..0526615538 100644 --- a/es/releases/2.0/notes.sgml +++ b/es/releases/2.0/notes.sgml @@ -1,657 +1,658 @@ - - + + %navincludes; %includes; ]> - + &header;
     
                                      RELEASE NOTES
                                         FreeBSD
                                       Release 2.0
     
     1. Technical overview
     ---------------------
     
     FreeBSD is a freely available, full source 4.4 BSD Lite based release
     for Intel i386/i486/Pentium (or compatible) based PC's.  It is based
     primarily on software from U.C. Berkeley's CSRG group, with some
     enhancements from NetBSD, 386BSD, and the Free Software Foundation.
     
     Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD
     has changed almost entirely.  A new port from the Berkeley 4.4 code
     base was done, which brought the legal status of the system out of the
     shadows with the blessing of Novell (new owners of USL and UNIX).  The
     port to 4.4 has also brought in a host of new features, filesystems
     and enhanced driver support.  With our new unencumbered code base, we
     have every reason to hope that we'll be able to release quality
     operating systems without further legal encumbrance for some time to
     come!
     
     FreeBSD 2.0 represents the culmination of almost 2 years of work and
     many thousands of man hours put in by an international development team.
     We hope you enjoy it!
     
     Many packages have also been upgraded or added, such as XFree86 3.1,
     xview 3.2, elm, nntp, mh, InterViews and dozens of other miscellaneous
     utilities have been ported and are now available as add-ons.  See the
     ports collection (or the package collection) for a complete summary.
     
     For a list of contributors, please see the file "CONTRIB.FreeBSD",
     which should be bundled with your bindist distribution.
     
     Also see the new "REGISTER.FreeBSD" file for information on registering
     with the "Free BSD user counter".  We've also provided a list of who's
     responsible for what (so that you may query them directly) in the
     "ROSTER.FreeBSD" file; use of this file is encouraged to ensure faster
     resolution of any problems you may have!
     
     The core of FreeBSD does not contain DES code which would inhibit its
     being exported outside the United States.  There is an add-on package
     to the core distribution, for use only in the United States, that
     contains the programs that normally use DES.  The auxiliary packages
     provided separately can be used by anyone.   A freely (from outside the
     U.S.) exportable European distribution of DES for our non U.S. users also
     exists and is described in the FreeBSD FAQ.
     
     If password security for FreeBSD is all you need, and you have no
     requirement for copying encrypted passwords from different hosts (Suns,
     DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5
     based security may be all you require!  We feel that our default security
     model is more than a match for DES, and without any messy export issues
     to deal with.  If you're outside (or even inside) the U.S., give it a try!
     
     
     1.1 What's new in 2.0?
     ----------------------
     
     4.4 Lite
     --------
     As previously stated, this release is based entirely on CSRG's
     latest (and last) BSD release - 4.4 Lite.  This features a number
     of improvements over 4.2BSD (Net/2), not least of which are:
     
     o       Legal approval of Novell & U.C. Berkeley.  After the settlement
             of the longstanding lawsuit between USL/UCB/Novell/BSDI, all
             parties were (strongly) encouraged to move to 4.4 Lite in order
             to avoid future legal entanglements.  The fact that we've now done
             so should make this release much more attractive to potential
             commercial users.
     
     o       Many new filesystem types, such as stackable filesystems, union
             filesystems, "portals", kernfs, a simple log-structured filesystem, a
             new version of NFS (NQNFS), etc.  While some of these new filesystems
             are also rather unpolished and will require significant additional
             work to be truly robust, they're a good start.
     
     o       64bit offsets, allowing filesystems of up to 2^63 bytes in size.
     
     o       Further work towards full POSIX compliance.
     
     IP multicast support
     --------------------
     The IP multicast support has been upgraded from the woefully ancient
     1.x code in 4.4-Lite to the most current and up-to-date 3.3 release
     from Steve D. and Ajit.  The non-forwarding code is known to work (for
     some limited test cases).  The multicast forwarder and user-mode
     multicast routing process are known to compile, but have not been
     significantly tested (hopefully this will happen before 2.0 release).
     
     Owner:                  wollman
     Sources involved:       sys/netinet, usr.sbin/mrouted
     
     Loadable Kernel Modules
     -----------------------
     David Greenman incorporated NetBSD's port of Terry Lambert's loadable
     kernel module support.  Garrett Wollman wrote the support for loadable
     file systems, and Søren Schmidt did the same for loadable execution
     classes.
     
     Owner:                  core
     Sources involved:       sys/kern, sbin/modload, sbin/modunload,
                             usr.bin/modstat
     
     
     Loadable filesystems
     --------------------
     Most filesystems are now dynamically loadable on demand, with the
     exception of the UFS family (FFS, LFS, and MFS).  With the exception
     of NFS, all such filesystems can be unloaded when all references are
    -unmounted.  To support this functionality, the 
    +unmounted.  To support this functionality, the
     
     getvfsbyname(3)
     
    -family of functions has been added to the C library and the 
    +family of functions has been added to the C library and the
     lsvfs(1)
     
     command provides the same information at the shell level.  Be aware of
     the following current restrictions:
     
             - /usr/bin may not reside on a dynamically loaded filesystem.
             - There must be a writable /tmp directory available
               before filesystems are loaded (moving / to the top of your
               /etc/fstab file will accomplish this).
             - Some of the more esoteric filesystems simply don't work when loaded
               dynamically (though they often don't work "static", either.)
     
     Owner:                  wollman
     Sources involved:       sys/*fs, lkm/*fs, usr.bin/lsvfs, lib/libc/gen
     
     
     S/Key
     -----
     Since version 1.1.5, FreeBSD has supported the S/Key one time password
     scheme.  The version used is derived from the logdaemon package of Wietse
     Venema.
     Some of the features new in 2.0 are:
             - New access control table format to impose the use of S/Keys
               based on: hostname, ip address, port, username, group id.
             - S/Key support can be disabled by not having the access control
               table.
     The second item explains the absence of skey.access in the installed /etc.
     To enable S/Key support, create a file skey.access in /etc and fill it
     according to your needs. See also skey.
     access(5)
     and the example in
     /usr/share/examples/etc/skey.access.
     
     Owner:                  pst, guido
     Sources involved:       lib/libskey, usr.bin/key* (plus patches to others)
     
     
     TCP/IP over parallel (printer) port
     -----------------------------------
     You can now run TCP/IP over a standard LapLink(tm) cable, if both ends
     have an interrupt-driven printerport.  The interface is named "lp0"
     where '0' is the same as the lpt# unit number.  This is not compatible
     with PLIP.  If you run NFS, try setting MTU to 9180, otherwise leave
     it at 1500 unless you have a good reason to change it.  Speed varies
     with the CPU-type, with up to 70 kbyte/sec having been seen and 50
     kbyte/sec being the norm.
     
     Owner:                  phk
     Sources involved:       isa/lpt.c
     
     
     ProAudioSpectrum SCSI driver
     ----------------------------
     If you have a PAS board with a CD-ROM, and the MS-DOS driver is called
     TSLCDR.SYS, then the "pas" driver should work on your card.  You can
     attach disks, CDROMs and tapes, but due to the nature of the hardware
     involved, the transfer rate is limited to < 690 kbyte/sec.  For CD-ROM
     use, this is generally more than enough.
     
     Owner:                  phk
     Sources involved:       isa/pas.c
     
     
     Adaptec 2742/2842 SCSI driver
     -----------------------------
     Despite the non-cooperation of Adaptec in providing technical
     information, we now have a driver for the AHA-274x and AHA-284x
     series SCSI controller family.  This driver uses the GPL'd
     Linux sequencer code, so until we find an alternative, this
     will be part of the kernel that requires source code to be
     distributed with it at all times.  This shouldn't be a problem
     for any of FreeBSD's current users.
     
     Owner:                  gibbs
     Sources involved:       isa/aic7770.c sys/gnu/misc/*
     
     
     Gzip'd binaries
     ----------------
     We have an experimental implementation for direct execution of gzip'ed
     binaries in this release.  When enabled, it allows you to simply gzip
     your binaries, remove the '.gz' extension and make the file
     executable.  There is a big speed and memory consumption penalty for
     doing this, but for laptop users it may be worthwhile.  The maximum
     savings are generally around 10 Mb of disk space.
     
     Owner:                  phk
     Sources involved:       kern/imgact_gzip.c kern/inflate.c
     
     
     Diskless booting
     ----------------
     
     Diskless booting in 2.0 is much improved since 1.1.5.  The
     boot-program is in src/sys/i386/boot/netboot, and can be run from an
     MSDOS system or burned into an EPROM.  Local swapping is also
     possible.  WD, SMC, 3COM and Novell ethernet cards are currently
     supported.
     
     Owner:                  Martin Renters & phk
     Sources involved:       i386/boot/netboot, sys/nfs/nfs_vfsops.h
     
     
     Device configuration database
     -----------------------------
     The kernel now keeps better track of which device drivers are active and
     where the devices are attached; this information is made available to
    -user programs via the new 
    +user programs via the new
     sysctl(3)
     management interface.  Current
    -applications include 
    +applications include
     lsdev(8),
     which lists the currently configured
     devices.  In the future, we expect to use this code to automatically
     generate a configuration file for you at installation time.
     
     Owner:                  wollman
     Sources involved:       sys/i386, sys/scsi, sys/kern/kern_devconf.c,
                             sys/sys/devconf.h, usr.sbin/lsdev
     
     
     Kernel management interface
     ---------------------------
     With 4.4-Lite, we now have a better management interface for the endless
     series of kernel variables and parameters which were previously manipulated
     by reading and writing /dev/kmem.  Many programs have been rewritten to
     use this interface, although many old-style programs still remain.  Some
     variables which were never accessible before are now available through
    -the 
    +the
     sysctl(1)
     program.  In addition to the standard 4.4BSD MIB variables,
     we have added support for YP/NIS domains (kern.domainname), controlling
     the update daemon (kern.update), retrieving the OS release date
     (kern.osreldate), determining the name of the booted kernel (kern.bootfile),
     and checking for hardware floating-point support (hw.floatingpoint).
     We have also added support to make management queries of devices and
     filesystems.
     
     Owner:                  core
     Sources involved:       sys, usr.bin/sysctl
     
     
     iBCS2 support
     -------------
     FreeBSD now supports running iBCS2 compatible binaries (currently
     SCO UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).
     The iBCS2 emulator is in its early stages, but it is functional, we
     haven't been able to do exhaustive testing (lack of commercial apps),
     but almost all of SCO's 3.2.2 binaries are working, so is an old
     INFORMIX-2.10 for SCO. Further testing is necessary to complete this
     project. There is also work under way for ELF & XOUT loaders, and
     most of the svr4 syscall wrappers have been written.
     
     Owner:                  Soren Schmidt (sos) & Sean Eric Fagan (sef)
     Sources involved:       sys/i386/ibcs2/* + misc kernel changes.
     
     
     2. Supported Configurations
     ---------------------------
     
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     Following is a list of all currently known disk controllers and
     ethernet cards known to work with FreeBSD.  Other configurations may
     very well work, and we have simply not received any indication of
     this.
     
     
     2.1. Disk Controllers
     
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     [Note: the new Extended IDE controllers in newer PC's work, although no
     extended features are used.]
     
     Adaptec 152x series ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 2742/2842 series ISA/EISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes
     the AHA-152x and SoundBlaster SCSI cards.
     
     ** Note: You cannot boot from the Soundblaster cards
     as they have no on-board BIOS, which is necessary for mapping
     the boot device into the system BIOS I/O vectors.
     They're perfectly usable for external tapes, CDROMs, etc,
     however.  The same goes for any other AIC-6x60 based card
     without a boot ROM.  Some systems DO have a boot ROM, which
     is generally indicated by some sort of message when the system
     is first powered up or reset.  Check your system/board documentation
     for more details.
     
     [Note that Buslogic was formerly known as "Bustec"]
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     
     NCR 53C810 and 53C825 PCI SCSI controller.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     UltraStor 14F, 24F and 34F SCSI controllers.
     
     Seagate ST01/02 SCSI controllers.
     
     Future Domain 8xx/950 series SCSI controllers.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
     DAT) and CD ROM drives.  Note: This and the mcd driver (Mitsumi CDROM
     interface card) are the only way a CD ROM drive may be currently
     attached to a FreeBSD system; we do not support SoundBlaster
     (non-SCSI) CDROM interface, or other "non-SCSI" adapters.  The
     ProAudio Spectrum SCSI and SoundBlaster SCSI controllers are
     supported.
     
     Some controllers have limitations with the way they deal with >16MB of
     memory, due to the fact that the ISA bus only has a DMA address space of
     24 bits.  If you do your arithmetic, you'll see that this makes it
     impossible to do direct DMA to any address >16MB.  This limitation is
     even true of some EISA controllers (which are normally 32 bit) when
     they're configured to emulate an ISA card, which they then do in *all*
     respects.  This problem is avoided entirely by IDE controllers (which do
     not use DMA), true EISA controllers (like the UltraStor or Adaptec
     1742A) and most VLB (local bus) controllers.  In the cases where it's
     necessary, the system will use "bounce buffers" to talk to the
     controller so that you can still use more than 16Mb of memory without
     difficulty.
     
     
     2.2. Ethernet cards
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra is also supported.
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509 and 3C579 Etherlink III
     
     Toshiba ethernet cards
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     2.3. Misc
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     
     BOCA ATIO66 6 port serial card using shared IRQ.
     
     STB 4 port card using shared IRQ.
     
     Mitsumi (all models) CDROM interface and drive.
     
     Soundblaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
     
     Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards.
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus, but
     support is apparently close to materializing.  Details will be posted
     as the situation develops.
     
     
     3. Obtaining FreeBSD.
     ---------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     1. FTP/Mail
     
     You can ftp FreeBSD and any or all of its optional packages from
     `freebsd.cdrom.com' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the nearest site
     to you netwise.
     
     If you do not have access to the internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
     to get more information on how to fetch files from freebsd.cdrom.com.
     Note: This approach will end up sending many *tens of megabytes*
     through the mail, and should only be employed as an absolute LAST
     resort!
     
     
     2. CDROM
     
     FreeBSD 2.0 may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
     
     Or via the internet from orders@cdrom.com.  Their current catalog can
     be obtained via ftp as ftp.cdrom.com:/cdrom/catalog.
     
     Cost is $39.95.  Shipping (per order not per disc) is $5 in the US, Canada,
     or Mexico and $10.00 overseas.  They accept Visa, Mastercard, American
     Express, and ship COD to the United States.  California residents please
     add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD,
     you need to contact the FreeBSD team for that.  Please see section 5 for
     more information.
     
     
     4. Preparing for the installation.
     ----------------------------------
     
     1. Floppy Installation
     
     If you must install from floppy disks, either due to space constraints
     on your hard disk or just because you enjoy doing things the hard
     way, you must first prepare some floppies for the install.
     
     You will need either 10 1.44MB floppies or 12 1.2MB floppies to
     store just the bindist (binary distribution).  These *must* be
     formatted using MS-DOS, using either the FORMAT command in MS-DOS
     or the File Manager in Microsoft Windows to prepare the floppies
     (though factory preformatted floppies will also 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 <where the *.?? files are>
             tar cvf /dev/rwt0 (or /dev/rst0) .
     
     from a directory with just the distribution files in it.  Make sure
     that you remember to put CKSUMS, do_cksum.sh, and extract.sh files
     in this directory as well!
     
     If you wish to install multiple *dist releases from one tape, do the
     following:
     
     1. cd to the parent directory of the distributions and put them on tape
        like so:
                     tar cvf /dev/rwt0 (or /dev/rst0) bindist srcdist ...
     
     2. Install the first distribution on the tape using the tape installation
        method as normal.  Afterwards, *do not* erase the contents of the temporary
        directory.  Get a shell with ESC-ESC and cd to the temporary directory
        yourself.  For each additional *dist you want to load, cd to its
        subdirectory and type `sh ./extract.sh'.
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached if you can!).
     
     The preferred method to submit bug reports from a machine with internet
     mail connectivity is to use the send-pr command.  Bug reports will be
     dutifully filed by our faithful bugfiler program and you can be sure
     that we'll do our best to respond to all reported bugs as soon as
     possible.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     bugs@FreeBSD.org
     
     
     Otherwise, for any questions or suggestions, please send mail to:
     
                     questions@FreeBSD.org
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more enhancements
     to be done than we can ever manage to do by ourselves!  To contact us
     on technical matters, or with offers of help, you may send mail to:
     
                     hackers@FreeBSD.org
     
     Since these mailing lists can experience significant amounts of
     traffic, if you've got slow or expensive mail access and you're
     only interested in keeping up with significant FreeBSD events, you may
     find it preferable to subscribe to:
     
                     announce@FreeBSD.org
     
     
     All but the FreeBSD-bugs groups can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  It would be very difficult, if not
     impossible, to enumerate everyone who's contributed to FreeBSD, but
     nonetheless we shall try (in alphabetical order, of course). If your
     name is not mentioned, please be assured that its omission is entirely
     accidental.
     
     
     The Computer Systems Research Group (CSRG), U.C. Berkeley.
     
     Bill Jolitz, for his extensive work with 386BSD.
     
     The FreeBSD "core" team:
     
             Andrew A. Chernov
             John Dyson
             Bruce Evans
             David Greenman
             Rodney W. Grimes
             Jordan K. Hubbard
             Poul-Henning Kamp
             Rich Murphey
             Gary Palmer
             Geoff Rehmet
             Paul Richards
             Soren Schmidt
             Andreas Schulz
             Jack Vogel
             Garrett A. Wollman
     
     
     Special mention to:
     
             Robert Bruce and Jack Velte of Walnut Creek CDROM, without
             whose help (and continuing support) this release would never
             have been possible.
     
             Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
             drive.
     
             The NetBSD group for their frequent assistance and commentary.
     
             Additional FreeBSD helpers and beta testers:
     
             J.T. Conklin                            Julian Elischer
             Sean Eric Fagan                         Jeffrey Hsu
             Terry Lambert                           L Jonas Olsson
             Chris Provenzano                        Dave Rivers
             Guido van Rooij                         Steven Wallace
             Atsushi Murai                           Scott Mace
             Andrew Moore                            Nate Williams
     
             And everyone at Montana State University for their initial support.
     
     
     Thanks to everyone, especially those not mentioned, and we sincerely
     hope you enjoy this release of FreeBSD!
     
     
                             The FreeBSD Core Team
     
    -Id: RELNOTES.FreeBSD,v 1.21 1994/12/02 20:27:11 jkh Exp 
    +Id: RELNOTES.FreeBSD,v 1.21 1994/12/02 20:27:11 jkh Exp
     
     

    Release Home &footer; diff --git a/es/releases/2.1.5R/announce.sgml b/es/releases/2.1.5R/announce.sgml index a2937ca9ed..6848e2f188 100644 --- a/es/releases/2.1.5R/announce.sgml +++ b/es/releases/2.1.5R/announce.sgml @@ -1,270 +1,271 @@ - - + + %navincludes; %includes; ]> &header;

    FreeBSD 2.1.5-RELEASE is now available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from from Walnut Creek CDROM.

    FreeBSD 2.1.5 represents the culmination of over a year's worth of work on the 2.1-STABLE branch of FreeBSD since it began with FreeBSD 2.0.5. In the 7 months since 2.1 was released, many many bug fixes, updates and careful enhancements have been made, the results of which you now see here.

    The STABLE branch was conceived out of the need to allow FreeBSD to grow and support long-term development projects (like devfs, NFSv3, IPX, PCCARD, etc.) while at the same time not jeopardizing the stability of its existing user base. FreeBSD 2.1.5 marks the finishing point for that effort and, barring any small "slipstream" releases done to solve significant problems, no further releases along the 2.1-STABLE branch are anticipated. The concept of "stable" and "experimental" tracks is not being abandoned, we'll simply be doing this somewhat differently in the future.

    For more information on the 2.1.5 release itself, please consult the Release Notes.

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

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

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

    Australia

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

    Brazil

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

    Canada

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

    Czech Republic

    Estonia

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

    Finland

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

    France

    Germany

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

    Hong Kong

    Ireland

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

    Israel

    Japan

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

    Korea

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

    Netherlands

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

    Poland

    Portugal

    Russia

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

    South Africa

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

    Sweden

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

    Taiwan

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

    Thailand

    USA

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

    UK

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

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

    South Africa

    Brazil

    Finland

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

    Release Home &footer; diff --git a/es/releases/2.1.6R/announce.sgml b/es/releases/2.1.6R/announce.sgml index 1e5c171998..f6c31ad63c 100644 --- a/es/releases/2.1.6R/announce.sgml +++ b/es/releases/2.1.6R/announce.sgml @@ -1,47 +1,48 @@ - - + + %navincludes; %includes; ]> &header; -

    Please read an important security +

    Please read an important security announcement regarding FreeBSD 2.1.6

    FreeBSD 2.1.6 is now available in:

    ftp://ftp.freebsd.org/pub/FreeBSD/2.1.6-RELEASE ]]> ftp://ftp.freebsd.org/pub/FreeBSD/2.1.6-RELEASE

    And shortly from its various mirror sites, a list of which may be obtained from: http://www.freebsd.org/handbook/mirrors.html

    This release will also be available on CDROM from Walnut Creek CDROM, hopefully shipping within the next 4-6 weeks.

    Those puzzled by the near-simultaneous release of 2.1.6 and 2.2 need also look no further than http://www.freebsd.org/branch.html for the reasons behind this release schedule. CDROM subscription customers should also see this page for information on Walnut Creek CDROM's plans for these releases.

    If you are a commercial user of FreeBSD who would like to take advantage of recent bug fixes without making the jump to our more ambitious 2.2 release (or delay that jump until 2.2 has had more time to mature), or if you're simply looking for the lowest-impact upgrade from 2.1.5, then 2.1.6-RELEASE is for you.

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

    Release Home &footer; diff --git a/es/releases/2.1.6R/security.sgml b/es/releases/2.1.6R/security.sgml index 1c8b2f57bd..e9067288e0 100644 --- a/es/releases/2.1.6R/security.sgml +++ b/es/releases/2.1.6R/security.sgml @@ -1,28 +1,29 @@ - - + + %navincludes; %includes; ]> &header;

    Security Update

    A serious security problem affecting FreeBSD 2.1.6 and earlier systems was found. The problem has been corrected within the -stable, -current, and RELENG_2_2 source trees. As an additional precaution, FreeBSD 2.1.6 is no longer - available from the FTP distribution sites. An update release + available from the FTP distribution sites. An update release (provisionally "FreeBSD 2.1.7") is expected shortly. -

    +

    You can read more about the problem and solution from the FreeBSD-SA-97:01.setlocale security announcement.

    Release Home &footer; diff --git a/es/releases/2.1.7R/announce.sgml b/es/releases/2.1.7R/announce.sgml index 34eae7d705..9a84001795 100644 --- a/es/releases/2.1.7R/announce.sgml +++ b/es/releases/2.1.7R/announce.sgml @@ -1,52 +1,53 @@ - - + + %navincludes; %includes; ]> &header;

    FreeBSD 2.1.7 is now available in:

    ftp://ftp.freebsd.org/pub/FreeBSD/2.1.7-RELEASE

    And shortly from its various mirror sites, a list of which may be obtained from: http://www.freebsd.org/handbook/mirrors.html

    This is a security release to FreeBSD 2.1.6, fixing at least several security holes and addressing a number of outstanding problem reports in that release.

    FreeBSD 2.1.7 will also be available on CDROM from Walnut Creek CDROM, hopefully shipping within the next 3-4 weeks. If you are a customer of Walnut Creek CDROM and you purchased the 2.1.6 release (either by subscription or by retail) then you are also entitled to a free upgrade. All you need to do is send mail to orders@cdrom.com or call 1-800 786-9907 / +1 510 674-0783 Intl, indicate that you would like the free 2.1.7 upgrade and provide your name and address information so that a replacement can be shipped. Walnut Creek CDROM customers will also receive a letter explaining these details.

    Those puzzled by the near-simultaneous release of 2.1.7 and 2.2 should also look at http://www.freebsd.org/branch.html for the reasons behind this release schedule. CDROM subscription customers should see this page for information on Walnut Creek CDROM's plans for these releases.

    If you are a commercial user of FreeBSD who would like to take advantage of recent bug fixes without making the jump to our more ambitious 2.2 release (or delay that jump until 2.2 has had more time to mature), or if you're simply looking for the lowest-impact upgrade from 2.1.5, then 2.1.7-RELEASE is for you.

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

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

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

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

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

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

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

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

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

    Jordan

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

    Release Home &footer; diff --git a/es/releases/2.2.1R/notes.sgml b/es/releases/2.2.1R/notes.sgml index 67a4093844..cb6763d75a 100644 --- a/es/releases/2.2.1R/notes.sgml +++ b/es/releases/2.2.1R/notes.sgml @@ -1,549 +1,550 @@ - - + + %navincludes; %includes; ]> - + &header;
     
                                      RELEASE NOTES
                                  FreeBSD 2.2.1-RELEASE
     
     2.2.1 is a small incremental fix release to 2.2, primarily aimed at
     fixing:
     
     o Some recently discovered problems with the Adaptec 2940 driver
       which could cause instability in very heavily loaded systems (like news
       servers).
     
     o A bug which made the package installer fail from CDROM media.
     
     o Allow the Intel EtherExpress Pro/100B to work in full-duplex mode.
     
     Since the 2.2.1. release follows 2.2 by just over a week, other
     documentation still refers to this release as simply "2.2" since it is
     a complete *replacement* for 2.2.0-RELEASE, not simply another point
     release following it.
     
     For even more up-to-date releases along the RELENG_2_2 branch (which
     is now proceeding onwards toward release 2.2.5), please install from:
     
             ftp://releng22.freebsd.org/pub/FreeBSD/
     
     This is a snapshot made of RELENG_2_2 on a daily basis (and containing
     all the latest 2.2 fixes as of that date).
     
     
     1. What's new since 2.1.7
     -------------------------
     
     Lots of installation bugs fixed, more pc98 changes synchronized, geeze,
     what else?
     
     gdb 4.16 has been merged from -current, most of the third-party source
     now lives under /usr/src/contrib.
     
     Updated support for the DEC DEFPA/DEFEA FDDI hardware.
     
     The old ``HAVE_FPU'' Makefile option is now finally gone, the selection
     between the math library using the floating point emulator, and the
     version using the co-processor is now fully automatic.  This will speed
     up floating-point using programs on sites that didn't like to recompile
     their `libm' previously.
     
     Javier Martin Rueda's `ex' driver has been merged, bringing support
     for the Intel EtherExpress Pro/10 network cards.
     
     The Intel EtherExpress Pro/100B now works in full-duplex mode.
     
     The `de' driver now recognizes cards using the DE21140A chip, like the
     popular SMC9332BDT (10/100 Mbit/s) one.
     
     There's now a workaround for the brokenness of the frequently used
     CMD640 PCI IDE chip in the sources, albeit still disabled by default
     in 2.2.
     
     The number of EISA slots to probe is now a fully supported option,
     including the ability to save the value from a UserConfig session
    -with 
    +with
     dset(8)>.
     This helps owners of HP NetServer LC machines to
     install the system on their hardware.
     
     Support for the SDL RISCom N2pci sync serial card.
     
     Support for Cyclades Cyclom-Y (multi-port async serial) PCI adaptors
     as well as multiple controllers and the 32-Y (if you are currently using
     the Cyclades serial adapter, you should re-make your /dev entries and
     remove the old ones).
     
     Updated support for ethernet adaptors which use the DEC DC21X4X chipset.
     
     Update to gcc 2.7.2.1 & add support for weak symbols.
     
     Many things moved/brought into /usr/src/contrib, updating and
     cleaning up the source tree accordingly.
     
     Support for compiled-in shared library ld paths.
     
     Update sgmlfmt to `instant'.
     
     Support for SNMP-style interface MIBs, including full RFC
     1650-compliant MIBs for the `de' (DEC 21x4x) and `ed' (SMC/WD/Novell)
     drivers.
     
     /stand/sysinstall moved even more towards becoming a more general
     system management tool.  You can actually add a new, from-scratch
     formatted disk with it now, from partition label to filesystem
     creation (though it still doesn't modify your /etc/fstab file to
     make it permanent).
     
     The syscons and psm drivers now have a new underlying shared keyboard
     driver, eliminating many of the previously existing problems with
     their mutual interaction.
     
    -Syscons now supports cut & paste in textmode using the 
    +Syscons now supports cut & paste in textmode using the
     moused(8)>
     utility.
     
     2.2 is the first release that includes full CD-R support for the
     Plasmon RF41xx, HP4020i, HP6020i, and Philips CDD2000 drives.  The
     driver is still under development (in particular to extend its
     usability for other devices), but it has been proved to be stable
     by now.
     
     Support for NFSv3 clients and servers went into the 2.2 sources
     shortly after branching off the 2.0.5/2.1.X tree.  There are also
     other options available with NFS, like the ability to turn an NFSv2
     server into asynchronous write mode (which is in violation of the
     specs, but has precedents e.g. in SGI Irix).
     
     Poul-Henning Kamp's phkmalloc replaced the old and blatant BSD
     malloc implementation.  This usually saves a lot of virtual memory
     for the clients, and offers some neat features like aborting the
     program on detected malloc abuses, or filling the malloced and/or
     freed area with junk in order to detect semantical problems in
     programs that use malloc.
     
     The `netatalk' implementation of AppleTalk has been integrated into
     the sources, most of the integration work courtesy Whistle Communic-
     ations Corp.
     
     The mount option `async' allows asynchronous metadata updates on UFS
     file systems, something that is the default e.g. on Linux' ext2fs.
     This speeds up many i-node intensive filesystem operations (like
     rm -r) at the cost of an increased risk in case of a system crash.
     The installation itself makes use of this feature, and could be
     drastically accelerated by this.  (A bindist-only installation from a
     SCSI CD-ROM can now complete in less than 5 minutes on a fast
     machine!)
     
     The ATAPI CD-ROM support is now reported to work for quite an
     impressive number of drives.  In other words, all the drives that
     basically adhere to the ATAPI standard are likely to work.
     
     There are many new drivers available in the kernel, too many to keep
     them in mind.  Tekram supplied a driver for their DC390 and DC390T
     controllers.  These controllers are based on the AMD 53c974, and the
     driver is also able to handle other SCSI controllers based on that
     chip.  Of course, with Tekram being generous enough to support the
     FreeBSD project with their driver, we'd like to encourage you to buy
     their product.  The `ed' and `lnc' drivers now support auto-config-
     uration for the respective PCI ethernet cards, including many NE2000
     clones and the AMD PCnet chips.  The SDL RISCom N2 support is new, as
     well as the PCI version of the Cyclades driver.
     
     The Linux emulation is now fully functional, including ELF support.
     To make its use easier, there are even ports for the required shared
     libraries, and for the Slackware development environment.
     
     Along the same lines, the SysV COFF emulation (aka. SCO emulation) is
     reported to be working well now.
     
     FreeBSD also supports native ELF binaries, although it hasn't been
     decided yet whether, when, and how we might use this as the default
     binary format some day.
     
     A `brandelf' utility has been added to allow `branding' of non-shared
     linked ELF binaries where the kernel cannot guess which image activator
     (FreeBSD, Linux, maybe SysV some day) should be used.  This works around
     one major flaw in the ELF object format, the missing field to mark the
     ABI it belongs to.
     
     Support for APM BIOSes is now in a much better shape.
     
     The manual section 9 has been started, describing `official' kernel
     programming interfaces.  We are still seeking volunteers to document
     interfaces here!
     
     The kernel configuration option handling has been largely moved away
     from the old -D Makefile kludges, towards a system of "opt_foo.h"
     kernel include files, allowing Makefile dependencies to work again.
     We expect the old hack that blows the entire compile directory away
    -on each run of 
    +on each run of
     config(8)>
     to go away anytime soon.  Unless you're changing
    -weird options, you might now consider using the -n option to 
    +weird options, you might now consider using the -n option to
     config(8)>,
     or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for
     you.  See also the comments in the handbook about how it works.
     
     
     2. Supported Configurations
     ---------------------------
     
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
     controllers.
     Adaptec AIC7850 on-board SCSI controllers.
     
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     ** Note: You cannot boot from the SoundBlaster cards as they have no
        on-board BIOS, such being necessary for mapping the boot device into the
        system BIOS I/O vectors.  They're perfectly usable for external tapes,
        CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
        without a boot ROM.  Some systems DO have a boot ROM, which is generally
        indicated by some sort of message when the system is first powered up
        or reset, and in such cases you *will* also be able to boot from them.
        Check your system/board documentation for more details.
     
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     Buslogic 956c PCI SCSI controller
     
     SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
     controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     Tekram DC390 and DC390T controllers (maybe other cards based on the
     AMD 53c974 as well).
     
    -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     UltraStor 14F, 24F and 34F SCSI controllers.
     
     Seagate ST01/02 SCSI controllers.
     
     Future Domain 8xx/950 series SCSI controllers.
     
     WD7000 SCSI controller.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
     DAT and 8mm Exabyte) and CD ROM drives.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (mcd)   Mitsumi proprietary interface (all models)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface (experimental and should be considered ALPHA
             quality!).
     
     
     2.2. Ethernet cards
     -------------------
     
     Allied-Telesis AT1700 and RE2000 cards
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra is also supported.
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress (not recommended due to driver instability)
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905 PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     Toshiba ethernet cards
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     
     2.3. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards.
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     
     HP4020i, Philips CDD2000 and PLASMON WORM (CDR) drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 2.1.7-RELEASE and 2.2-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
             ftp://ftp.cdrom.com/cdrom/catalog.
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription
     (-RELEASE and -SNAP subscriptions are entirely separate).  With a
     subscription, you will automatically receive updates as they are released.
     Your credit card will be billed when each disk is shipped and you may cancel
     your subscription at any time without further obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or suggestions, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All but the freebsd-bugs groups can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     5. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     Additional FreeBSD helpers and beta testers:
     
    -        Coranth Gryphon            Dave Rivers 
    +        Coranth Gryphon            Dave Rivers
             Kaleb S. Keithley          Terry Lambert
             David Dawes                Don Lewis
     
     Special mention to:
     
             Walnut Creek CDROM, without whose help (and continuing support)
             this release would never have been possible.
     
             Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
             drive.
     
             Chuck Robey for his donation of a floppy tape streamer for
             testing.
     
             Larry Altneu and Wilko Bulte for providing us with Wangtek
             and Archive QIC-02 tape drives for testing and driver hacking.
     
             CalWeb Internet Services for the loan of a P6/200 machine for
             speedy package building.
     
             Everyone at Montana State University for their initial support.
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     
     

    Release Home &footer; diff --git a/es/releases/2.2.2R/errata.sgml b/es/releases/2.2.2R/errata.sgml index 166f78558c..918a14fe99 100644 --- a/es/releases/2.2.2R/errata.sgml +++ b/es/releases/2.2.2R/errata.sgml @@ -1,79 +1,80 @@ - - + + %navincludes; %includes; ]> - + &header;
     Last minute errata:
     -------------------
     o login as root produces "login_getclass: unknown class 'root'" on system console.
     
     Fix:  If you have the source distribution installed, simply
           cp /usr/src/etc/login.conf /etc
           otherwise, get it from the FreeBSD FTP site using this URL:
           ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/etc/login.conf
           instead.  Simply cd to /etc and then run fetch(1) with the provided URL.
     
     
     o sysconfig scrambles rc.conf if run again.
     
     Fix:  Get updated /usr/src from RELENG_2_2 branch and build
           /usr/src/release/sysinstall, copying the new binary to /stand.
     
           If you do not have enough space for src then you could also
           use the boot/fixit floppy combo from a later 2.2-YYMMDD-RELENG
           release to simply mount your root partition (using the Fixit
           option) and copy /stand/sysinstall from the floppy to /stand on
           your root fs.
     
     
     o Installation floppy does not boot at all - whereas the 2.2.1 floppy
       worked fine.  I get a "panic: double fault" right after it tries to
       change the root device to fd0c.
     
     Fix:  The problem is that you have 48MB of RAM and something very very
           mysterious has happened to FreeBSD twixt 2.2.1 and 2.2.2 which makes
           it fail with just that exact memory size.  Given the popularity of
           16MB simms, it also explains why none of us have seen it since we
           typically have either 16MB, 32MB or 64MB of memory in our systems. :)
     
           We're working on finding and fixing this problem, but until then
           the following work-around is in effect for 48MB systems:
     
           1. Boot the 2.2.2 boot floppy and when it comes to the first menu which
              asks you whether or not you want to go into the kernel configuration
              editor, choose the "experts only" CLI mode option.  Now type:
     
     	      iosize npx0 32768
     	      visual
     	      < and do your visual kernel configuration as normal then exit>
     
              If you can get through to the installation, go to step 3.
     
           2. If the above does not work, physically remove all but 32MB of memory
              from your machine and then boot the boot floppy.  Unless your problem
              is totally weird and something we've not seen at all before, you
              should now be able to go on to step 3.
     
           3. Complete the installation and then boot off your hard disk.  This
              boot should work fine, since you are no longer using the memory
              filesystem that the installation uses and which seems to interact
              badly with these memory size issues to create the failure you saw.
     
              You will also want to boot with the -c flag at some point and
              say "iosize npx0 0" to get the full use of all your memory back
              since the old value of 32768 will have been saved to disk during
              the initial installation.  If you already plan on building a custom
              kernel, you can skip this step since the value will be reset anyway.
     

    Release Home &footer; diff --git a/es/releases/2.2.2R/notes.sgml b/es/releases/2.2.2R/notes.sgml index 4de155f375..19b0e17a96 100644 --- a/es/releases/2.2.2R/notes.sgml +++ b/es/releases/2.2.2R/notes.sgml @@ -1,563 +1,564 @@ - - + + %navincludes; %includes; ]> - + &header;
                                      RELEASE NOTES
                                   FreeBSD 2.2.2-RELEASE
     
     o For information about the layout of the release directory, see
       the ABOUT.TXT file.
     
     o For installation instructions, see the INSTALL.TXT and HARDWARE.TXT
       files.
     
     For the most up-to-date releases along the RELENG_2_2 branch (which
     is now proceeding onwards toward release 2.2.5), please install from:
     
             ftp://releng22.freebsd.org/pub/FreeBSD/
     
     
     0. What's new since 2.2.1
     -------------------------
     A number of bugs in the Adaptec 294x/394x (AHC) driver were fixed
     which could cause instability on heavily loaded systems.
     
     NFSv3 is now the default, with fall-back to NFSv2 occuring as necessary.
     
     An lchown() system call has been added for changing the ownership of symlinks.
     
     Login classes added for setting default user limits (see login.
     conf(5)).
     
     ftpd now supports virtual FTP hosting.
     
     Numerous security fixes (buffer overflows and other potential exploits fixed).
     
     Better build support for C++ libraries added.
     
     Support for the GLOBAL text/HTML source tag system added (man global).
     
     /etc/sysconfig now replaced by /etc/rc.conf - a more concise customization
     file with more knobs added.  Other things in /etc were also neatened
     up, /etc/netstart being replaced with /etc/rc.network
     
     User-mode ppp updated with various fixes and enhancements from 3.0-current.
     
     Texinfo documentation mechanisms cleaned up in source tree.
     
     
     1. What's new since 2.1.7
     -------------------------
     
     Lots of installation bugs fixed, more pc98 changes synchronized, geeze,
     what else?
     
     gdb 4.16 has been merged from -current, most of the third-party source
     now lives under /usr/src/contrib.
     
     Updated support for the DEC DEFPA/DEFEA FDDI hardware.
     
     The old ``HAVE_FPU'' Makefile option is now finally gone, the selection
     between the math library using the floating point emulator, and the
     version using the co-processor is now fully automatic.  This will speed
     up floating-point using programs on sites that didn't like to recompile
     their `libm' previously.
     
     Javier Martin Rueda's `ex' driver has been merged, bringing support
     for the Intel EtherExpress Pro/10 network cards.
     
     The Intel EtherExpress Pro/100B now works in full-duplex mode.
     
     The `de' driver now recognizes cards using the DE21140A chip, like the
     popular SMC9332BDT (10/100 Mbit/s) one.
     
     There's now a workaround for the brokenness of the frequently used
     CMD640 PCI IDE chip in the sources, albeit still disabled by default
     in 2.2.
     
     The number of EISA slots to probe is now a fully supported option,
     including the ability to save the value from a UserConfig session
    -with 
    +with
     dset(8)>.
     This helps owners of HP NetServer LC machines to
     install the system on their hardware.
     
     Support for the SDL RISCom N2pci sync serial card.
     
     Support for Cyclades Cyclom-Y (multi-port async serial) PCI adaptors
     as well as multiple controllers and the 32-Y (if you are currently using
     the Cyclades serial adapter, you should re-make your /dev entries and
     remove the old ones).
     
     Updated support for ethernet adaptors which use the DEC DC21X4X chipset.
     
     Update to gcc 2.7.2.1 & add support for weak symbols.
     
     Many things moved/brought into /usr/src/contrib, updating and
     cleaning up the source tree accordingly.
     
     Support for compiled-in shared library ld paths.
     
     Update sgmlfmt to `instant'.
     
     Support for SNMP-style interface MIBs, including full RFC
     1650-compliant MIBs for the `de' (DEC 21x4x) and `ed' (SMC/WD/Novell)
     drivers.
     
     /stand/sysinstall moved even more towards becoming a more general
     system management tool.  You can actually add a new, from-scratch
     formatted disk with it now, from partition label to filesystem
     creation (though it still doesn't modify your /etc/fstab file to
     make it permanent).
     
     The syscons and psm drivers now have a new underlying shared keyboard
     driver, eliminating many of the previously existing problems with
     their mutual interaction.
     
    -Syscons now supports cut & paste in textmode using the 
    +Syscons now supports cut & paste in textmode using the
     moused(8)>
     utility.
     
     2.2 is the first release that includes full CD-R support for the
     Plasmon RF41xx, HP4020i, HP6020i, and Philips CDD2000 drives.  The
     driver is still under development (in particular to extend its
     usability for other devices), but it has been proved to be stable
     by now.
     
     Support for NFSv3 clients and servers went into the 2.2 sources
     shortly after branching off the 2.0.5/2.1.X tree.  There are also
     other options available with NFS, like the ability to turn an NFSv2
     server into asynchronous write mode (which is in violation of the
     specs, but has precedents e.g. in SGI Irix).
     
     Poul-Henning Kamp's phkmalloc replaced the old and blatant BSD
     malloc implementation.  This usually saves a lot of virtual memory
     for the clients, and offers some neat features like aborting the
     program on detected malloc abuses, or filling the malloced and/or
     freed area with junk in order to detect semantical problems in
     programs that use malloc.
     
     The `netatalk' implementation of AppleTalk has been integrated into
     the sources, most of the integration work courtesy Whistle Communic-
     ations Corp.
     
     The mount option `async' allows asynchronous metadata updates on UFS
     file systems, something that is the default e.g. on Linux' ext2fs.
     This speeds up many i-node intensive filesystem operations (like
     rm -r) at the cost of an increased risk in case of a system crash.
     The installation itself makes use of this feature, and could be
     drastically accelerated by this.  (A bindist-only installation from a
     SCSI CD-ROM can now complete in less than 5 minutes on a fast
     machine!)
     
     The ATAPI CD-ROM support is now reported to work for quite an
     impressive number of drives.  In other words, all the drives that
     basically adhere to the ATAPI standard are likely to work.
     
     There are many new drivers available in the kernel, too many to keep
     them in mind.  Tekram supplied a driver for their DC390 and DC390T
     controllers.  These controllers are based on the AMD 53c974, and the
     driver is also able to handle other SCSI controllers based on that
     chip.  Of course, with Tekram being generous enough to support the
     FreeBSD project with their driver, we'd like to encourage you to buy
     their product.  The `ed' and `lnc' drivers now support auto-config-
     uration for the respective PCI ethernet cards, including many NE2000
     clones and the AMD PCnet chips.  The SDL RISCom N2 support is new, as
     well as the PCI version of the Cyclades driver.
     
     The Linux emulation is now fully functional, including ELF support.
     To make its use easier, there are even ports for the required shared
     libraries, and for the Slackware development environment.
     
     Along the same lines, the SysV COFF emulation (aka. SCO emulation) is
     reported to be working well now.
     
     FreeBSD also supports native ELF binaries, although it hasn't been
     decided yet whether, when, and how we might use this as the default
     binary format some day.
     
     A `brandelf' utility has been added to allow `branding' of non-shared
     linked ELF binaries where the kernel cannot guess which image activator
     (FreeBSD, Linux, maybe SysV some day) should be used.  This works around
     one major flaw in the ELF object format, the missing field to mark the
     ABI it belongs to.
     
     Support for APM BIOSes is now in a much better shape.
     
     The manual section 9 has been started, describing `official' kernel
     programming interfaces.  We are still seeking volunteers to document
     interfaces here!
     
     The kernel configuration option handling has been largely moved away
     from the old -D Makefile kludges, towards a system of "opt_foo.h"
     kernel include files, allowing Makefile dependencies to work again.
     We expect the old hack that blows the entire compile directory away
    -on each run of 
    +on each run of
     config(8)>
     to go away anytime soon.  Unless you're changing
    -weird options, you might now consider using the -n option to 
    +weird options, you might now consider using the -n option to
     config(8)>,
     or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for
     you.  See also the comments in the handbook about how it works.
     
     
     2. Supported Configurations
     ---------------------------
     
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
     controllers.
     Adaptec AIC7850 on-board SCSI controllers.
     
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     ** Note: You cannot boot from the SoundBlaster cards as they have no
        on-board BIOS, such being necessary for mapping the boot device into the
        system BIOS I/O vectors.  They're perfectly usable for external tapes,
        CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
        without a boot ROM.  Some systems DO have a boot ROM, which is generally
        indicated by some sort of message when the system is first powered up
        or reset, and in such cases you *will* also be able to boot from them.
        Check your system/board documentation for more details.
     
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     Buslogic 956c PCI SCSI controller
     
     SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
     controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     Tekram DC390 and DC390T controllers (maybe other cards based on the
     AMD 53c974 as well).
     
    -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     UltraStor 14F, 24F and 34F SCSI controllers.
     
     Seagate ST01/02 SCSI controllers.
     
     Future Domain 8xx/950 series SCSI controllers.
     
     WD7000 SCSI controller.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
     DAT and 8mm Exabyte) and CD ROM drives.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (mcd)   Mitsumi proprietary interface (all models)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface (experimental and should be considered ALPHA
             quality!).
     
     
     2.2. Ethernet cards
     -------------------
     
     Allied-Telesis AT1700 and RE2000 cards
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra is also supported.
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress (not recommended due to driver instability)
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905 PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     Toshiba ethernet cards
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     
     2.3. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards.
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     
     HP4020i, Philips CDD2000 and PLASMON WORM (CDR) drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 2.1.7-RELEASE and 2.2-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
             ftp://ftp.cdrom.com/cdrom/catalog.
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription
     (-RELEASE and -SNAP subscriptions are entirely separate).  With a
     subscription, you will automatically receive updates as they are released.
     Your credit card will be billed when each disk is shipped and you may cancel
     your subscription at any time without further obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or suggestions, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All but the freebsd-bugs groups can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     5. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     Additional FreeBSD helpers and beta testers:
     
    -        Coranth Gryphon            Dave Rivers 
    +        Coranth Gryphon            Dave Rivers
             Kaleb S. Keithley          Terry Lambert
             David Dawes                Don Lewis
     
     Special mention to:
     
             Walnut Creek CDROM, without whose help (and continuing support)
             this release would never have been possible.
     
             Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
             drive.
     
             Chuck Robey for his donation of a floppy tape streamer for
             testing.
     
             Larry Altneu and Wilko Bulte for providing us with Wangtek
             and Archive QIC-02 tape drives for testing and driver hacking.
     
             CalWeb Internet Services for the loan of a P6/200 machine for
             speedy package building.
     
             Everyone at Montana State University for their initial support.
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/2.2.5R/announce.sgml b/es/releases/2.2.5R/announce.sgml index 371bdfa16b..fd847bbec6 100644 --- a/es/releases/2.2.5R/announce.sgml +++ b/es/releases/2.2.5R/announce.sgml @@ -1,96 +1,97 @@ - - + + %navincludes; %includes; ]> &header;

    Date: 22 Oct 1997 14:09:08 -0500
    From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
    Subject: 2.2.5 RELEASE now available from ftp.freebsd.org (and some mirrors)

    It is my great pleasure, as always, to announce the release of FreeBSD 2.2.5, our next release on the 2.2-stable branch. Those folks who are still running 2.1.x and wish to upgrade to 2.2 technology are now encouraged to do so as 2.2.5 has reached an equivalent level of stability in all of our tests. A number of annoying problems with 2.2.2 have also been fixed (see the release notes for more information on this).

    FreeBSD 2.2.5-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly as a new 4 CD set containing a lot of extra stuff of interest to programmers and general users alike.

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB page at:

    http://www.cdrom.com/pub/FreeBSD

    And on CD-ROM from Walnut Creek CDROM:

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

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in Argentina, Australia, Brazil, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Ireland, Israel, Japan, Korea, the Netherlands, Poland, Portugal, Russia, South Africa, Sweden, Taiwan, Thailand and the UK (among other countries :). Please check your regional mirrors first by going to:

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

    since ftp.freebsd.org is itself rather overloaded at the present time (Id software and Slackware Linux chose the same time to release their latest products :).

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

    South Africa

    ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    Release Home &footer; diff --git a/es/releases/2.2.5R/errata.sgml b/es/releases/2.2.5R/errata.sgml index 0759ca25ae..32dfd28f23 100644 --- a/es/releases/2.2.5R/errata.sgml +++ b/es/releases/2.2.5R/errata.sgml @@ -1,113 +1,114 @@ - - + + %navincludes; %includes; ]> - + &header;
     The file 
     ERRATA.TXT contains post-release ERRATA for 2.2.5 and should always
     be considered the definitive place to look first before reporting
     a problem with this release.  This file will also be periodically
     updated as new issues are reported so even if you've checked this
     file recently, check it again before filing a bug report.  Any
     changes to this file are also automatically emailed to:
     
     	freebsd-stable@freebsd.org
     
     For 2.2.5 security advisories, see:
     
     	ftp://freebsd.org/pub/CERT/
     
     For the latest information (note the URL carefully - this is NOT
     ftp.freebsd.org).
     
     ---- Security Advisories:
     
     Current active security advisories for 2.2.5:	One
     
     o FreeBSD-SA-97:05 (available from ftp://ftp.freebsd.org/pub/FreeBSD/CERT).
     
       You may also simply remove /dev/io as a quick work-around if you're
       not running an X server or some other specialized utility which
       requires access to the I/O instructions.
    - 
    +
     ---- System Update Information:
     o The appletalk stack was broken in 2.2.5.
     
     Fix:  If you plan to run appletalk, you should apply the following patch:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/updates/2.2.5-RELEASE/atalk.diff.2.2.gz
     
     
     o The line printer spooler lpd will, when sending jobs to remote
       printers, kill the child process sending to the remote after the
       timeout specified in the `ct' capability (2 minutes by default).
     
     Fix:  Please upgrade the lpd subsystem to 2.2-stable.  As a workaround,
           increase the `ct' capability to an unreasonably large number of
           seconds (like 3600).
     
     
     o Intel "F00F bug" enables users to hang machines with Pentium processors
       if they have access to the machine and can execute programs.
     
     Fix:  Update to the 2.2-stable version of the kernel or apply the patch
    -      found in: 
    - 
    +      found in:
    +
           ftp://ftp.freebsd.org/pub/FreeBSD/updates/2.2.5-RELEASE/f00f.diff.2.2.gz
     
     
     o A bug in the ipfw code exists where using the "reset tcp" firewall command
       causes the kernel to write ethernet headers onto random kernel stack
       locations.
     
     Fix:	Update to the 2.2-stable version of the kernel or apply the
             patch found in ftp://ftp.freebsd.org/pub/FreeBSD/updates/2.2.5-RELEASE/ipfw.diff.gz
     
     
     o A bug in XF86Setup causes it to fail to create a symbolic link from
       /usr/X11R6/bin/X to the right X server for your hardware if a link
       does not already exist.  When you type startx the following error is
       displayed:
     
       xinit:  No such file or directory (errno 2):  no server "X" found in PATH
    -  
    +
     Fix:	Execute the following commands (as root) and re-run XF86Setup.
     
     	# cd /usr/X11R6/bin
     	# ln -s XF86_VGA16 X
    -	
    +
     	If XF86Setup asks you if you want to use the existing XF86Config for
     	defaults choose no.  When it asks you if you want to create an 'X'
     	link to the server choose yes.
     
     
     o A bug in the phase diagram implementation of user-level ppp causes
       problems with some ppp implementations when shutting down the link.
       The line will go dead, but the modem will not hang up unless done
       manually using pppctl (or a switch).
     
     Fix:  A version of ppp derived from the -current sources is available from
           http://www.FreeBSD.org/~brian
     
           It should build on any version of FreeBSD from 2.0.5 onwards.
           This code is available in the -current tree, but not (yet) in the
           2.2-STABLE tree.
     
     	Further documentation can be found at these locations:
     
     	  Document references
     	  FAQ
     	  handbook
     

    Release Home &footer; diff --git a/es/releases/2.2.5R/notes.sgml b/es/releases/2.2.5R/notes.sgml index 1e5ab1517d..19b6b8872d 100644 --- a/es/releases/2.2.5R/notes.sgml +++ b/es/releases/2.2.5R/notes.sgml @@ -1,450 +1,451 @@ - - + + %navincludes; %includes; ]> &header;
                                      RELEASE NOTES
                                  FreeBSD 2.2.5-RELEASE
     
     o For information about the layout of the release directory, see
       the ABOUT.TXT file.  If you are installing from floppies, it is
       especially important that you *read this section!*
     
     o It is also important to check the ERRATA.TXT file for any
       late-breaking issues with this release.  This file contains the
    -  latest information on significant bugs, security problems or 
    -  other similar issues which an administrator should be aware of. 
    +  latest information on significant bugs, security problems or
    +  other similar issues which an administrator should be aware of.
     
     o For installation instructions, see the INSTALL.TXT and HARDWARE.TXT
       files.
     
     For the most up-to-date releases along the RELENG_2_2 branch (which
     is now proceeding onwards toward release 2.2.6), please install from:
     
             ftp://releng22.freebsd.org/pub/FreeBSD/
     
     Or for the latest 3.0-current (HEAD branch) snapshot releases,
     please install from:
     
             ftp://current.freebsd.org/pub/FreeBSD
     
     
     1. What's new since 2.2.2
     -------------------------
     
     Better support for Cyrix and AMD processors.
     
     The "world" target in /usr/src/Makefile has been made more
     independent of the host system, allowing for easier bootstrapping
     via source from very old systems.
     
     Many many fixes to the documentation.
     
     Many security enhancements, as reported through CERT and other
     computer security organizations.
     
     The installation program was further updated and fixed, some
     year-old bogons finally eliminated for 2.2.5.
     
     Important subsystems such as BIND and sendmail updated.
     
     Support for ethernet media selection.   Replacing the far
     more arcane "link" flag usage, a new media flag to ifconfig
     permits specific interfaces on multi-port ethernet cards to
     be selected by name (man ifconfig for more details).
     
     Significant improvements to the AHC (Adaptec 394x/294X) driver
     and AIC7xxx assembler.
     
     Enhancements to the serial boot code and GDB remote support.
     
     Make work-around available for CMD640 chipset (see /sys/i386/conf/LINT).
     
     Newer 3Com 3c589D PCMCIA cards are now supported.
     
     A new VGA library (/usr/src/lib/libvgl) now exists for doing simple
     VGA graphics to syscons ttys (sort of like Linux's libSVGA).
     
     The TCP connection timeout in lpd & friends can now be specified by a
     printcap(5) capability, preventing it from hanging for too long when
     working in an environment with many network printservers.
     
     User-mode ppp updated with various fixes and enhancements from 3.0-current.
     It's worth re-reading the manual page since some of the following changes
     may disturb peoples current configurations:
     
       o The "set debug" command is now "set log".
       o The LCP log has been split into an LCP, IPCP and CCP log, so any
         "set log LCP" lines will need to be changed to "set log LCP IPCP CCP"
         to see the same output as before.
       o Ppp now uses syslogd to write its log files.
       o Ppp now has LQR disabled and openmode active by default.
       o Ppp now installs as group "network", with mode 4550.  You must add group
         69 (network) to /etc/group.  If you wish to allow users to run "ppp
         -direct ...", you must enable them by making them a member of group
         "network".  Client-side ppp now requires user id 0.
     
     Refer to the ppp(8) man page and the relevent section of the handbook for
     full details.
     
     
     2. Supported Configurations
     ---------------------------
     
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
     controllers.
     Adaptec AIC7850 on-board SCSI controllers.
     
     Support for the following controllers is rather weak:
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     ** Note: You cannot boot from the SoundBlaster cards as they have no
        on-board BIOS, such being necessary for mapping the boot device into the
        system BIOS I/O vectors.  They're perfectly usable for external tapes,
        CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
        without a boot ROM.  Some systems DO have a boot ROM, which is generally
        indicated by some sort of message when the system is first powered up
        or reset, and in such cases you *will* also be able to boot from them.
        Check your system/board documentation for more details.
     
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     Buslogic 956c PCI SCSI controller
     
     SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
     controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     Tekram DC390 and DC390T controllers (maybe other cards based on the
     AMD 53c974 as well).
     
    -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     UltraStor 14F, 24F and 34F SCSI controllers.
     
     Seagate ST01/02 SCSI controllers.
     
     Future Domain 8xx/950 series SCSI controllers.
     
     WD7000 SCSI controller.
     
     FreeBSD 2.2.5 will be accompanied by a contributed driver for the
     Future Domain 36C20 / Adaptec AHA2920 controller.  This is not fully
     supported (yet), but basically functional.  Look into the /xperimnt
     section of the CD-ROM.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
     DAT and 8mm Exabyte) and CD ROM drives.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (mcd)   Mitsumi proprietary interface (all models, driver is rather stale)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface.
     
     
     2.2. Ethernet cards
     -------------------
     
     Allied-Telesis AT1700 and RE2000 cards
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra is also supported.
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress (not recommended due to driver instability)
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905 PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     Toshiba ethernet cards
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     
     2.3. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards.
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Various Frame grabbers based on Brooktree Bt848 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Floppy tape drives (some rather old models only, driver rather stale)
     
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 2.2.5-RELEASE and 3.0-SNAPSHOT CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
             ftp://ftp.cdrom.com/cdrom/catalog.
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription
     (-RELEASE and -SNAP subscriptions are entirely separate).  With a
     subscription, you will automatically receive updates as they are released.
     Your credit card will be billed when each disk is shipped and you may cancel
     your subscription at any time without further obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or suggestions, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All but the freebsd-bugs groups can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     5. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     Additional FreeBSD helpers and beta testers:
     
    -        Coranth Gryphon            Dave Rivers 
    +        Coranth Gryphon            Dave Rivers
             Kaleb S. Keithley          Terry Lambert
             David Dawes                Don Lewis
     
     Special mention to:
     
             Walnut Creek CDROM, without whose help (and continuing support)
             this release would never have been possible.
     
             Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
             drive.
     
             Chuck Robey for his donation of a floppy tape streamer for
             testing.
     
             Larry Altneu and Wilko Bulte for providing us with Wangtek
             and Archive QIC-02 tape drives for testing and driver hacking.
     
             Everyone at Montana State University for their initial support.
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/2.2.6R/announce.sgml b/es/releases/2.2.6R/announce.sgml index d3da4a3bb4..9fffe92992 100644 --- a/es/releases/2.2.6R/announce.sgml +++ b/es/releases/2.2.6R/announce.sgml @@ -1,88 +1,89 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Wed Mar 25 04:24:34 PST 1998
    From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
    Subject: 2.2.6 RELEASE now available from ftp.freebsd.org (and some mirrors)

    As always, it's my great pleasure to announce the release of FreeBSD 2.2.6, our latest release on the 2.2-stable branch and the result of over 4 months of work since 2.2.5 was released. See the release notes for a list of significant changes since the previous release.

    FreeBSD 2.2.6-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly as a 4 CD set containing a lot of extra stuff of interest to the programmer and general user alike.

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB page at:

    http://www.cdrom.com/pub/FreeBSD

    And on CD-ROM from Walnut Creek CDROM:

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

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in Argentina, Australia, Brazil, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Ireland, Israel, Japan, Korea, the Netherlands, Poland, Portugal, Russia, South Africa, Sweden, Taiwan, Thailand and the UK (among other countries :). Please check your regional mirrors first by going to:

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

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

    South Africa

    ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    Release Home &footer; diff --git a/es/releases/2.2.6R/errata.sgml b/es/releases/2.2.6R/errata.sgml index 3bd48afe6c..3fcf77f976 100644 --- a/es/releases/2.2.6R/errata.sgml +++ b/es/releases/2.2.6R/errata.sgml @@ -1,133 +1,134 @@ - - + + %navincludes; %includes; ]> - + &header;
     The file 
     ERRATA.TXT contains post-release ERRATA for 2.2.6 and should always
     be considered the definitive place to look *first* before reporting
     a problem with this release.  This file will also be periodically
     updated as new issues are reported so even if you've checked this
     file recently, check it again before filing a bug report.  Any
     changes to this file are also automatically emailed to:
     
     	freebsd-stable@freebsd.org
     
     For 2.2.6 security advisories, see:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest information.
     
     ---- Security Advisories:
     
     Current active security advisories for 2.2.6:   4
     
     See ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-98:0[2-5].*
     for full information.
     
     ---- System Update Information:
     o Root mountpoint change which affects those upgrading via
      "make world" or a FreeBSD 2.2.6 upgrade.
     
     Fix:  2.2.6 introduces a change in the naming of the device from
           which the root filesystem is mounted.  This change affects all systems,
           however user intervention is only required for systems undergoing an
           upgrade installation.
     
     Previously, the root filesystem was always mounted from the
     compatibility slice, while other partitions on the same disk were
     mounted from their true slice.  This might, for example, have resulted
     in an /etc/fstab file like:
     
     # Device      Mountpoint      FStype  Options         Dump    Pass#
     /dev/wd0s2b   none            swap    sw              0       0
     /dev/wd0a     /               ufs     rw              1       1
     /dev/wd0s2f   /local0         ufs     rw              1       1
     /dev/wd0s2e   /usr            ufs     rw              1       1
     
     For FreeBSD 2.2.6 and later, this format changes so that the device for
     '/' is consistent with others, ie.
     
     # Device      Mountpoint      FStype  Options         Dump    Pass#
     /dev/wd0s2b   none            swap    sw              0       0
     /dev/wd0s2a   /               ufs     rw              1       1
    -/dev/wd0s2f   /local0         ufs     rw              1       1 
    +/dev/wd0s2f   /local0         ufs     rw              1       1
     /dev/wd0s2e   /usr            ufs     rw              1       1
     
     If /etc/fstab is not updated manually in this case, the system will
     issue a warning message whenever / is mounted (normally at startup)
     indicating the change that must be made.  In addition, trouble may be
     experienced if the root filesystem is not correctly unmounted, whereby
     the root filesystem will not be marked clean at the next reboot.
     
    -This change should be made as soon as the upgraded system has been 
    +This change should be made as soon as the upgraded system has been
     successfully rebooted.
     
     
     o The ppp program fails to work, citing a missing shared library
       called "libdes.so.3.0".
     
    -Fix:  There are three possible fixes:  
    -  
    -1. The easiest fix is to simply install the des distribution with 
    +Fix:  There are three possible fixes:
    +
    +1. The easiest fix is to simply install the des distribution with
        /stand/sysinstall, remembering to pick a site that will allow you
        to export it if you're outside the United States and Canada
        (ftp.freebsd.org and ftp.internat.freebsd.org both fall into this
        category).
    -  
    -2. Purely as a work-around, and what you may need to do if ppp 
    +
    +2. Purely as a work-around, and what you may need to do if ppp
        also constitutes your only way of getting to the net, is to simply
        do the following (as root):
     
    -      cp /usr/lib/libcrypt.so.2.0 /usr/lib/libdes.so.3.0      
    +      cp /usr/lib/libcrypt.so.2.0 /usr/lib/libdes.so.3.0
           ldconfig -m /usr/lib
     
    -3. Another fix, and one which doesn't involve having to fetch the DES  
    +3. Another fix, and one which doesn't involve having to fetch the DES
        bits, is to install the ppp sources in /usr/src/usr.sbin/ppp and rebuild
        them.  The sources are "smart" enough to know that the DES library isn't
        on the system and won't create a binary which depends on it.
     
    -NOTE:  If you choose the 2nd or 3rd fixes, you also will not be able to 
    +NOTE:  If you choose the 2nd or 3rd fixes, you also will not be able to
     use MSCHAP (Microsoft Win*) style authentication.
     
     
     o The xterm program in XFree86 3.3.2 doesn't remove utmp entries on
       exit (e.g. xterm sessions show up in "who" or "w" even after they've
       exited).
     
     Fix:  Fetch the updated xterm binary at:
     
       ftp://ftp.freebsd.org/pub/FreeBSD/updates/2.2.6-RELEASE/xterm
     
     Or get the *latest* ports collection on your machine (see
     http://www.freebsd.org/ports) and use the port in x11/XFree86 to
     build an xterm with this patch already applied (as of 98/04/06).
     The patch itself can also be obtained from the port itself:
     
       ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/ports/x11/XFree86/patches/patch-ag
     
     
    -o The older Matsushita (Panasonic), Sony CDU-31 and Mitsumi (non-IDE) 
    +o The older Matsushita (Panasonic), Sony CDU-31 and Mitsumi (non-IDE)
       CDROM drives no longer permit CDROM installs.
     
     Fix: Fetch an updated boot floppy from the updates/ directory, e.g.:
     
       ftp://ftp.freebsd.org/pub/FreeBSD/updates/2.2.6-RELEASE/boot.flp
     
    -And use it to install 2.2.6 instead.  This problem is fixed in 2.2-stable 
    +And use it to install 2.2.6 instead.  This problem is fixed in 2.2-stable
     and will not be a problem with the next FreeBSD release.
     
     

    Release Home &footer; diff --git a/es/releases/2.2.6R/notes.sgml b/es/releases/2.2.6R/notes.sgml index 9aace01d11..209cd962f6 100644 --- a/es/releases/2.2.6R/notes.sgml +++ b/es/releases/2.2.6R/notes.sgml @@ -1,92 +1,93 @@ - - + + %navincludes; %includes; ]> &header;
     ================================================================
                              RELEASE NOTES
                       FreeBSD 2.2.6-RELEASE VERSION
     ================================================================
     
     What's new since 2.2.5
     ----------------------
     
     Kernel features:
     
     o Added support for SMC EtherPower II 10/100 Fast Ethernet card
       (aka SMC9432TX based on SMC83c170 EPIC chip).
     
     o Added support for DPT SCSI RAID controllers (see LINT).
     
     o New Plug and Play (PnP) support that allows you to (re)configure
       PnP devices.  Also support modems being detected by the PnP
       part and automatically attached.
     
     o Alternate sound driver (/sys/i386/isa/snd) from Luigi Rizzo;
       it does not yet support MIDI (for that, use the old sound
       driver) but it does have much better support for PNP sound
       cards and is much easier to configure (only one device).
       See /sys/i386/conf/LINT for more info.
     
     o Better Linux emulation (applications like RealVideo 5.0 for
       Linux now work).
     
     o Added support for ATAPI floppy drives (LS-120)
     
     o The psm, mse and sysmouse drivers are improved to provide
       better mouse support.  moused(8) has been modified to support
       various mice with a ``wheel''.  It also automatically
       recognizes mice which support the PnP COM device standard so
       that the user is no longer required to supply a mouse protocol
    -  type on the command line. 
    +  type on the command line.
     
     Userland features:
     
     o popen() library call now uses and offers bidirectional pipes.
     
     o Added support for parallel makes in /usr/src (-j n works
       now with   world target, particularly useful with SMP
       machines).
     
     o tcpdump(1) utility enhanced
     
     o Support for ldconfig -R (remove) added.
     
     o Various bugfixes and enhancements to pthread support.
     
     o calendar(1) program brought more up-to-date.
     
     o KerberosIV updated to latest version.
     
     o Various curses(3) bugs fixed.
     
     o Various IEEE754 conformance changes to libm(3).
     
     o Much cleanup and general improvements to the documentation.
     
     o Various improvements to the NIS code.
     
     
     Security issues:
     
     o Fixed /dev/io and mmap security holes.
     
     o Better protection against "LAND attacks"
     
     o Various buffer overruns detected and extra checks added.
     
     o Pentium "F00F bug" is detected and a work-around installed to
       prevent hangs.
     
     o srandomdev() support merged from -current and utilities updated
       to use it.
     
     

    Release Home &footer; diff --git a/es/releases/2.2.7R/announce.sgml b/es/releases/2.2.7R/announce.sgml index 2aa37edf97..d033b9d799 100644 --- a/es/releases/2.2.7R/announce.sgml +++ b/es/releases/2.2.7R/announce.sgml @@ -1,117 +1,118 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Wed, 22 Jul 1998 08:36:25 -0700
    From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
    Subject:FreeBSD 2.2.7 is now released!

    It is my usual pleasure to announce the release of FreeBSD 2.2.7, our latest release along the 2.2-stable branch. Those folks who are still running 2.1.x and wish to upgrade to 2.2 technology are encouraged to do so as 2.2.7 has reached a more than equivalent level of stability in all of our tests. A number of problems with 2.2.6 have also been fixed (see the release notes for more information).

    FreeBSD 2.2.7-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly as a 4 CD set containing a lot of extra stuff of interest to programmers and general users alike.

    IMPORTANT NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project!

    Like many businesses in the field of high-tech, Walnut Creek CDROM has realized that in order to make any product for an emerging market grow, you have to make a significant investment in such growth, even if it means abandoning short-term profits. Walnut Creek CDROM is the only CDROM vendor who currently does anything like this and it's certainly my hope that you will help support the project by buying (or getting someone else to buy :) one of their CDs. Thanks!

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB page at:

    http://www.cdrom.com/pub/FreeBSD

    And on CD-ROM from Walnut Creek CDROM:

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

    If you are in Japan, please refer to Pacific HiTech for information on ordering a localized (or the english) version of the 2.2.7 product. Pacific HiTech is now an affiliate of Walnut Creek CDROM for Japanese sales of FreeBSD.

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

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

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

    South Africa

    ftp://ftp.internat.F reeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBS D.ORG/pub/FreeBSD

    Brazil

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

    Finland

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

    Release Home &footer; diff --git a/es/releases/2.2.7R/errata.sgml b/es/releases/2.2.7R/errata.sgml index 5c13c76f14..30abc5e560 100644 --- a/es/releases/2.2.7R/errata.sgml +++ b/es/releases/2.2.7R/errata.sgml @@ -1,69 +1,70 @@ - - + + %navincludes; %includes; ]> - + &header;
     The file 
     ERRATA.TXT contains post-release ERRATA for 2.2.7 and should always
     be considered the definitive place to look *first* before reporting
     a problem with this release.  This file will also be periodically
     updated as new issues are reported so even if you've checked this
     file recently, check it again before filing a bug report.  Any
     changes to this file are also automatically emailed to:
     
     	freebsd-stable@freebsd.org
     
     For 2.2.7 security advisories, see:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest information.
     
     ---- Security Advisories:
     
     Current active security advisories for 2.2.7:   None
     
     ---- System Update Information:
     o XFree86:  The XF86Setup utility sometimes fails with an XIO
       error (visible on the 2nd VTY) rather than starting properly if you
       run it during system installation time.  This is not a new bug and
       has been seen in previous releases of FreeBSD, but it seems to happen
       far more reliably with 2.2.7 now (for some as yet unknown reason).
     
     Fix: Should this happen to you, run /usr/X11R6/bin/XF86Setup by hand
          after the system comes up off the hard disk for the first time.
          For some reason, when not run off the boot floppy or CD, it works
          perfectly (making this one somewhat more difficult to debug).
     
     
     o Release notes state that Texas Instruments ThunderLAN PCI NICs are
       supported in 2.2.7.
     
     Fix: This was an embarrassing mis-merge from the 3.0 release notes and,
    -     indeed, those cards are only supported in 3.0-current.  Please ignore 
    +     indeed, those cards are only supported in 3.0-current.  Please ignore
          this section of the release notes and any other docs which claim that
          the ThunderLAN NICs are supported in 2.2.7.
     
     
     o rshd was broken during -Wall cleanup, as noted in PR#7500
     
     Fix: This was fixed in the 2.2-stable branch as of 1998/07/24 04:32:21
          in revision 1.9.2.9 of /usr/src/libexec/rshd/rshd.c.  Obtain the
    -     fixed version via CVSup (see instructions in handbook or simply 
    +     fixed version via CVSup (see instructions in handbook or simply
          ``pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz''
          and follow the instructions) or get it from FTP at:
          ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/libexec/rshd/rshd.c
     
     

    Release Home &footer; diff --git a/es/releases/2.2.7R/notes.sgml b/es/releases/2.2.7R/notes.sgml index 1595d261fa..5a0c4e732f 100644 --- a/es/releases/2.2.7R/notes.sgml +++ b/es/releases/2.2.7R/notes.sgml @@ -1,440 +1,441 @@ - - + + %navincludes; %includes; ]> &header;
     ================================================================
                              RELEASE NOTES
                      FreeBSD 2.2.7-RELEASE VERSION
     ================================================================
     
     1. What's new since 2.2.6
     -------------------------
     
     Kernel features:
     ----------------
     o DPT SCSI RAID controller updated (including support for EISA cards)
       and is now enabled by default.
     
     o MSDOS FAT32 (Win95 long filename) support.
     
     o Various bugs in the SCSI changer code fixed.
     
     o New support for Crystal Semiconductor CS8920 based ethernet cards.
     
     o Dead LFS code removed.
     
     o New updated Specialix SI/XIO/SX driver.
     
     o dmesg (history buffer) now user-sizeable.  See MSGBUF_SIZE
       option in /sys/i386/conf/LINT.
     
     o Various bugfixes for the Adaptec aic7870/aic7880 chipsets.
     
     o Identify Pentium II processors properly at startup now.
     
     o pcm audio driver updated to support Avance Logic ALS100 card and
       basically improve audio support all around.
     
     o Various fixes to NFS credential checking.
     
     o Many updates for the NEC PC98 platform.
     
     
     Userland features:
     ------------------
     o inetd(8) now allows rate-limiting for services.
     
     o ppp(8) utility significantly updated.  See man page for details.
     
     o Many (MANY!) man pages and other docs updated and cleaned up.
     
     o libc_r (part of POSIX pthread support) is now part of the system by
       default and incorporates numerous bug fixes.
     
     o ls(1) has grown a number of new flags - man ls for details.
     
     o cvs(1) updated to version 1.9.26
     
     o Various parts of /etc updated with selected features from 3.0.
     
     o as(1) now understands fildll/fistpll opcodes.
     
     o Various improvements to the installation procedure.
     
     o Various minor curses(3) positioning errors fixed.
     
     o Several bugs in dump(8) and restore(8) fixed.
     
     o Various enhancements made to the login class mechanism and
       default limits raised for workstation users.
     
     o ftpd disables Nagle on the control channel for better response.
     
     
     Security issues:
     ----------------
     o XFree86 updated to 3.3.2.3 - an important security release containing
       changes from The Open Group which close several possible root-exploits
       from local users.
     
     o Crypto repository updated from 3.0 branch.
     
     o popper and imap upgraded in ports collection to close some nasty security
       holes (see Bugtrax).
     
     o Various buffer overflows in utilities like rcp(1) and more(1) (just to
       name a few) have been closed.
     
     o Bounds-checking added to numerous "attackable" locations in BIND and
       much of BIND significantly updated.
     
     
     2. Supported Configurations
     ---------------------------
     
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
     controllers.
     Adaptec AIC7850 on-board SCSI controllers.
     
     ** Note: You cannot boot from the SoundBlaster cards as they have no
        on-board BIOS, such being necessary for mapping the boot device into the
        system BIOS I/O vectors.  They're perfectly usable for external tapes,
        CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
        without a boot ROM.  Some systems DO have a boot ROM, which is generally
        indicated by some sort of message when the system is first powered up
        or reset, and in such cases you *will* also be able to boot from them.
        Check your system/board documentation for more details.
     
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     Buslogic 956c PCI SCSI controller
     
     SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
     controllers:
     	ASUS SC-200
       	Data Technology DTC3130 (all variants)
     	NCR cards (all)
     	Symbios cards (all)
     	Tekram DC390W, 390U and 390F
     	Tyan S1365
     
     Tekram DC390 and DC390T controllers (maybe other cards based on the
     AMD 53c974 as well).
     
    -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     UltraStor 14F, 24F and 34F SCSI controllers.
     
     Seagate ST01/02 SCSI controllers.
     
     Future Domain 8xx/950 series SCSI controllers.
     
     WD7000 SCSI controller.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
     DAT and 8mm Exabyte) and CD ROM drives.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface
     
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
       Adaptec 152x series ISA SCSI controllers
       Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
       and SoundBlaster SCSI cards.
     
       Floppy tape interface (Colorado/Mountain/Insight)
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     2.2. Ethernet cards
     -------------------
     
     Allied-Telesis AT1700 and RE2000 cards
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
     Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
     Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
     Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
     Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress (not recommended due to driver instability)
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905 PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     Toshiba ethernet cards
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     
     2.3. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards.
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 3.0-SNAP and 2.2.x-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD 3.0-SNAP CDs are $39.95 or $14.95 with a FreeBSD-SNAP subscription
     (-RELEASE and -SNAP subscriptions are entirely separate).  With a
     subscription, you will automatically receive updates as they are released.
     Your credit card will be billed when each disk is shipped and you may cancel
     your subscription at any time without further obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
    - 
    +
                    freebsd-bugs@FreeBSD.org
    - 
    +
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
    - 
    +
     Otherwise, for any questions or tech support issues, please send mail to:
    - 
    +
                    freebsd-questions@FreeBSD.org
    - 
    +
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
    - 
    +
                    freebsd-hackers@FreeBSD.org
    - 
    +
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
    - 
    +
                    freebsd-announce@FreeBSD.org
    - 
    +
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
    - 
    +
     5. Acknowledgements
     -------------------
    - 
    +
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
    - 
    +
             http://www.freebsd.org/handbook/staff.html
    - 
    +
     or, if you've loaded the doc distribution:
    - 
    +
             file:/usr/share/doc/handbook/staff.html
    - 
    +
     Special mention to:
    - 
    +
             The donors listed at http://www.freebsd.org/handbook/donors.html
    - 
    +
             Everyone at Montana State University for their initial support.
    - 
    +
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
    - 
    +
     We sincerely hope you enjoy this release of FreeBSD!
    - 
    +
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/2.2.8R/announce.sgml b/es/releases/2.2.8R/announce.sgml index 5b1d5e2d0a..b524b4d170 100644 --- a/es/releases/2.2.8R/announce.sgml +++ b/es/releases/2.2.8R/announce.sgml @@ -1,109 +1,110 @@ - - + + %navincludes; %includes; ]> &header;

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

    It is, as always, my great pleasure to announce the release of FreeBSD 2.2.8, our latest and final release along the 2.2-stable branch. Those folks who are still running 2.1.x and wish to upgrade to 2.2 technology are definitely encouraged to do so now as the 2.2-stable branch has gone into maintainence mode. A number of problems with 2.2.7 have been fixed and the release notes should be consulted for more information.

    FreeBSD 2.2.8-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly as a 4 CD set containing a lot of extra stuff of interest to programmers and general users alike.

    IMPORTANT NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project!

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB page at:

    http://www.cdrom.com/pub/FreeBSD

    And on CD-ROM from Walnut Creek CDROM:

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

    If you are in Japan, please refer to Pacific HiTech for information on ordering a localized (or the english) version of the 2.2.8 product. Pacific HiTech is now an affiliate of Walnut Creek CDROM for Japanese sales of FreeBSD.

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

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

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

    South Africa

    ftp://ftp.internat.F reeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBS D.ORG/pub/FreeBSD

    Brazil

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

    Finland

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

    Release Home &footer; diff --git a/es/releases/2.2.8R/errata.sgml b/es/releases/2.2.8R/errata.sgml index 45aa258768..6e6f43c095 100644 --- a/es/releases/2.2.8R/errata.sgml +++ b/es/releases/2.2.8R/errata.sgml @@ -1,68 +1,69 @@ - - + + %navincludes; %includes; ]> - + &header;
     The file 
     ERRATA.TXT contains post-release ERRATA for 2.2.8 and should always
     be considered the definitive place to look *first* before reporting
     a problem with this release.  This file will also be periodically
     updated as new issues are reported so even if you've checked this
     file recently, check it again before filing a bug report.  Any
     changes to this file are also automatically emailed to:
     
     	freebsd-stable@freebsd.org
     
     For 2.2.8 security advisories, see:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest information.
     
     ---- Security Advisories:
     
     Current active security advisories for 2.2.8:   None
     
     ---- System Update Information:
     
     o /usr/sbin/sysctl is an invalid link and whereis(1) doesn't work.
     
     Fix: sysctl(8) has actually moved to /sbin/sysctl.  Simply create
          a symbolic link for compatability purposes as follows:
     
             ln -sf /sbin/sysctl /usr/sbin
    - 
    +
          or syncronize your sources with 2.2-stable and rebuild/install
    -     from /usr/src/usr.bin/whereis/ and just rm /usr/sbin/sysctl  
    +     from /usr/src/usr.bin/whereis/ and just rm /usr/sbin/sysctl
     
     o    /usr/share/doc/FAQ is in spanish.
     
     Fix: This was a build failure which affected only the FAQ and has since
          been fixed.  If you are already cvsup/CTM'ing the doc-all tag then
          you can simply remake and install the FAQ from sources, otherwise
          grab ftp://ftp.freebsd.org/pub/FreeBSD/doc/FAQ.tar.gz and unpack
          as follows:  tar --unlink -xvzf FAQ.tar.gz -C /usr/share/doc
          to get an english FAQ.
     
     o    getpwnam(3) semantics are incorrect in some cases.
    - 
    +
     Fix: If passed a string longer than the maximum allowed for a user name,
          getpwnam will incorrectly return an entry for a user that matches the
          initial characters in the string up to the maximum length allowed for a
          user name.  To correct this behaviour, libc needs to be patched and
          recompiled.  The appropriate patch can be obtained from:
          http://cvsweb.freebsd.org/src/lib/libc/gen/getpwent.c.diff?r1=1.35.2.2&r2=1.35.2.3
     
     

    Release Home &footer; diff --git a/es/releases/2.2.8R/notes.sgml b/es/releases/2.2.8R/notes.sgml index 98719b916a..7dee18bd08 100644 --- a/es/releases/2.2.8R/notes.sgml +++ b/es/releases/2.2.8R/notes.sgml @@ -1,396 +1,397 @@ - - + + %navincludes; %includes; ]> &header;
     
     ================================================================
                              RELEASE NOTES
                      FreeBSD 2.2.8-RELEASE VERSION
     ================================================================
     
     1. What's new since 2.2.7
     -------------------------
     
     Kernel features:
     ----------------
     o Add support for >8G IDE drives.
     
     o Add support for 3Com 3c905B ethernet adapters
     
     o Add support for PCI ThunderLAN-based ethernet adapters (Compaq/Olicom)
     
     o Significantly improve Linux emulator again.  Things like QuakeII should
       just run out-of-the-box now (given the rest of their requirements).
     
     o Major changes from -current's pthread implementation merged: This includes
       file locking based on FILE *, signal fixes, read/write-locks, better POSIX
       compliance and better performance.
     
     o Add a new flexible bandwidth limiter/delay emulator called
       dummynet. See dummynet(4).
     
     o Add support for bridging on multiple interfaces (10 and 100 Mbit/s).
       See bridge(4).
     
     o NFS client accelerator added.  See 'nfs_access_cache' in rc.conf(5).
     
     
     Userland features:
     ------------------
     
     o /bin/sh signal and trap handling reworked. Among other things, this
       makes tty-mode emacs work when called from system(2), i.e. by a mail
       agent.
     
     o ppp(8) merged from 3.0, adding features like multilink and VPN
       support as well as fixing a number of known bugs.
     
     
     Security issues:
     ----------------
     
     o All open CERT/Bugtraq advisories reported since 2.2.7's release
       have been dealt with.
     
     
     2. Supported Configurations
     ---------------------------
     
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
     controllers.
     Adaptec AIC7850 on-board SCSI controllers.
     
     ** Note: You cannot boot from the SoundBlaster cards as they have no
        on-board BIOS, such being necessary for mapping the boot device into the
        system BIOS I/O vectors.  They're perfectly usable for external tapes,
        CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
        without a boot ROM.  Some systems DO have a boot ROM, which is generally
        indicated by some sort of message when the system is first powered up
        or reset, and in such cases you *will* also be able to boot from them.
        Check your system/board documentation for more details.
     
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     Buslogic 956c PCI SCSI controller
     
     SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
     controllers:
     	ASUS SC-200
       	Data Technology DTC3130 (all variants)
     	NCR cards (all)
     	Symbios cards (all)
     	Tekram DC390W, 390U and 390F
     	Tyan S1365
     
     Tekram DC390 and DC390T controllers (maybe other cards based on the
     AMD 53c974 as well).
     
    -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     UltraStor 14F, 24F and 34F SCSI controllers.
     
     Seagate ST01/02 SCSI controllers.
     
     Future Domain 8xx/950 series SCSI controllers.
     
     WD7000 SCSI controller.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
     DAT and 8mm Exabyte) and CD ROM drives.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI CDROM interface
     (acd)	ATAPI CD-R interface (alternative to 'wcd')
     
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
       Adaptec 152x series ISA SCSI controllers
       Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
       and SoundBlaster SCSI cards.
     
       Floppy tape interface (Colorado/Mountain/Insight)
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     2.2. Ethernet cards
     -------------------
     
     Allied-Telesis AT1700 and RE2000 cards
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
      Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
      Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
      Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
      Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress (not recommended due to driver instability)
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     Toshiba ethernet cards
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     No token ring cards are supported at this time.
     
     
     2.3. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards.
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 3.0-SNAP and 2.2.x-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs are $39.95 or $14.95 with a FreeBSD-SNAP subscription
     (-RELEASE and -SNAP subscriptions are entirely separate).  With a
     subscription, you will automatically receive updates as they are released.
     Your credit card will be billed when each disk is shipped and you may cancel
     your subscription at any time without further obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
    - 
    +
                    freebsd-bugs@FreeBSD.org
    - 
    +
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
    - 
    +
     Otherwise, for any questions or tech support issues, please send mail to:
    - 
    +
                    freebsd-questions@FreeBSD.org
    - 
    +
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
    - 
    +
                    freebsd-hackers@FreeBSD.org
    - 
    +
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
    - 
    +
                    freebsd-announce@FreeBSD.org
    - 
    +
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
    - 
    +
     5. Acknowledgements
     -------------------
    - 
    +
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
    - 
    +
             http://www.freebsd.org/handbook/staff.html
    - 
    +
     or, if you've loaded the doc distribution:
    - 
    +
             file:/usr/share/doc/handbook/staff.html
    - 
    +
     Special mention to:
    - 
    +
             The donors listed at http://www.freebsd.org/handbook/donors.html
    - 
    +
             Everyone at Montana State University for their initial support.
    - 
    +
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
    - 
    +
     We sincerely hope you enjoy this release of FreeBSD!
    - 
    +
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/2.2R/announce.sgml b/es/releases/2.2R/announce.sgml index bef1d48d93..16891b542d 100644 --- a/es/releases/2.2R/announce.sgml +++ b/es/releases/2.2R/announce.sgml @@ -1,29 +1,30 @@ - - + + %navincludes; %includes; ]> &header;

    It is our great pleasure to announce the release of FreeBSD 2.2, the long-awaited first release of our 2.2 branch technology following lengthy ALPHA, BETA and GAMMA testing cycles.

    -

    FreeBSD 2.2-RELEASE is now available on -ftp.freebsd.org and +

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

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

    Release Home &footer; diff --git a/es/releases/2.2R/install-media.sgml b/es/releases/2.2R/install-media.sgml index 9f4583cfe1..4b7ffd54f5 100644 --- a/es/releases/2.2R/install-media.sgml +++ b/es/releases/2.2R/install-media.sgml @@ -1,42 +1,43 @@ - - + + %navincludes; %includes; ]> &header; From jkh:

    2.2-RELEASE will not support installation of machines with 4MB of memory or 1.2MB floppy drives - that is to say, only > 5MB memory & 1.44MB floppy drive systems are supported. In truth, 8MB of memory is the recommended minimum.

    Those who have such limitations on their configuration and can't upgrade, for whatever reason, are therefore urged to stay with 2.1.6-RELEASE, which has provisions for both types of installation and will probably be more than functional for as long as one might conceivably wish to continue operating such a system.

    We regret any inconvenience this may cause some of our users, but we have also been pressed for space on the installation media for some time now, and this was more or less inevitable. We've talked about killing the 4MB installation and 1.2MB floppies for over a year, and it's only through some of the most arcane trickery (you don't want to know) that we've managed to keep it all on a single floppy at all. Now that we've made the leap to 1.44MB/>6MB class machines, we've at least bought ourselves some room for future enhancements while still remaining on one floppy.

    Note that you can still build kernels which will run quite comfortably in a 4MB system, you just can't *install* with only 4MB in the machine. If you're trying to build a custom box with 4MB and a tiny configuration, for example, you might simply build its disk on a different machine set up specifically for that purpose.

    Release Home &footer; diff --git a/es/releases/2.2R/notes.sgml b/es/releases/2.2R/notes.sgml index 1d0b7b819a..21f63e19aa 100644 --- a/es/releases/2.2R/notes.sgml +++ b/es/releases/2.2R/notes.sgml @@ -1,518 +1,519 @@ - - + + %navincludes; %includes; ]> - + &header;
                                      RELEASE NOTES
                                   FreeBSD 2.2-RELEASE
     
     1. What's new since 2.1.7
     -------------------------
     
     Lots of installation bugs fixed, more pc98 changes syncronized, geeze,
     what else?
     
     gdb 4.16 has been merged from -current, most of the third-party source
     now lives under /usr/src/contrib.
     
     Updated support for the DEC DEFPA/DEFEA FDDI hardware.
     
     The old ``HAVE_FPU'' Makefile option is now finally gone, the selection
     between the math library using the floating point emulator, and the
     version using the co-processor is now fully automatic.  This will speed
     up floating-point using programs on sites that didn't like to recompile
     their `libm' previously.
     
     Javier Martin Rueda's `ex' driver has been merged, bringing support
     for the Intel EtherExpress Pro/10 network cards.
     
     The `de' driver now recognizes cards using the DE21140A chip, like the
     popular SMC9332BDT (10/100 Mbit/s) one.
     
     There's now a workaround for the brokeness of the frequently used
     CMD640 PCI IDE chip in the sources, albeit still disabled by default
     in 2.2.
     
     The number of EISA slots to probe is now a fully supported option,
     including the ability to save the value from a UserConfig session
    -with 
    -dset(8).  
    +with
    +dset(8).
     This helps owners of HP NetServer LC machines to
     install the system on their hardware.
     
     Support for the SDL RISCom N2pci sync serial card.
     
     Support for Cyclades Cyclom-Y (multi-port async serial) PCI adaptors
     as well as multiple controllers and the 32-Y (if you are currently using
     the Cyclades serial adapter, you should re-make your /dev entries and
     remove the old ones).
     
     Updated support for ethernet adaptors which use the DEC DC21X4X chipset.
     
     Update to gcc 2.7.2.1 & add support for weak symbols.
     
     Many things moved/brought into /usr/src/contrib, updating and
     cleaning up the source tree accordingly.
     
     Support for compiled-in shared library ld paths.
     
     Update sgmlfmt to `instant'.
     
     Support for SNMP-style interface MIBs, including full RFC
     1650-compliant MIBs for the `de' (DEC 21x4x) and `ed' (SMC/WD/Novell)
     drivers.
     
     /stand/sysinstall moved even more towards becoming a more general
     system management tool.
     
     The syscons and psm drivers now have a new underlying shared keyboard
     driver, eliminating many of the previously existing problems with
     their mutual interaction.
     
    -Syscons now supports cut & paste in textmode using the 
    +Syscons now supports cut & paste in textmode using the
     moused(8)
     utility.
     
     2.2 is the first release that includes full CD-R support for the
     Plasmon RF41xx, HP4020i, HP6020i, and Philips CDD2000 drives.  The
     driver is still under development (in particular to extend its
     usability for other devices), but it has been proved to be stable
     by now.
     
     Support for NFSv3 clients and servers went into the 2.2 sources
     shortly after branching off the 2.0.5/2.1.X tree.  There are also
     other options available with NFS, like the ability to turn an NFSv2
     server into asynchronous write mode (which is in violation of the
     specs, but has precedents e.g. in SGI Irix).
     
     Poul-Henning Kamp's phkmalloc replaced the old and blatant BSD
     malloc implementation.  This usually saves a lot of virtual memory
     for the clients, and offers some neat features like aborting the
     program on detected malloc abuses, or filling the malloced and/or
     freed area with junk in order to detect semantical problems in
     programs that use malloc.
     
     The `netatalk' implementation of AppleTalk has been integrated into
     the sources, most of the integration work courtesy Wistle Communic-
     ations Corp.
     
     The mount option `async' allows asynchronous metadata updates on UFS
     file systems, something that is the default e.g. on Linux' ext2fs.
     This speeds up many i-node intensive filesystem operations (like
     rm -r) at the cost of an increased risk in case of a system crash.
     The installation itself makes use of this feature, and could be
     drastically accelerated by this.  (A bindist-only installation from a
     SCSI CD-ROM can now complete in less than 5 minutes on a fast
     machine!)
     
     The ATAPI CD-ROM support is now reported to work for quite an
     impressive number of drives.  In other words, all the drives that
     basically adhere to the ATAPI standard are likely to work.
     
     There are many new drivers available in the kernel, too many to keep
     them in mind.  Tekram supplied a driver for their DC390 and DC390T
     controllers.  These controllers are based on the AMD 53c974, and the
     driver is also able to handle other SCSI controllers based on that
     chip.  Of course, with Tekram being generous enough to support the
     FreeBSD project with their driver, we'd like to encourage you to buy
     their product.  The `ed' and `lnc' drivers now support auto-config-
     uration for the respective PCI ethernet cards, including many NE2000
     clones and the AMD PCnet chips.  The SDL RISCom N2 support is new, as
     well as the PCI version of the Cyclades driver.
     
     The Linux emulation is now fully functional, including ELF support.
     To make its use easier, there are even ports for the required shared
     libraries, and for the Slackware development environment.
     
     Along the same lines, the SysV COFF emulation (aka. SCO emulation) is
     reported to be working well now.
     
     FreeBSD also supports native ELF binaries, although it hasn't been
     decided yet whether, when, and how we might use this as the default
     binary format some day.
     
     A `brandelf' utility has been added to allow `branding' of non-shared
     linked ELF binaries where the kernel cannot guess which image activator
     (FreeBSD, Linux, maybe SysV some day) should be used.  This works around
     one major flaw in the ELF object format, the missing field to mark the
     ABI it belongs to.
     
     Support for APM BIOSes is now in a much better shape.
     
     The manual section 9 has been started, describing `official' kernel
     programming interfaces.  We are still seeking volunteers to document
     interfaces here!
     
     The kernel configuration option handling has been largely moved away
     from the old -D Makefile kludges, towards a system of "opt_foo.h"
     kernel include files, allowing Makefile dependencies to work again.
     We expect the old hack that blows the entire compile directory away
    -on each run of 
    +on each run of
     config(8)
     to go away anytime soon.  Unless you're changing
    -weird options, you might now consider using the -n option to 
    +weird options, you might now consider using the -n option to
     config(8),
     or setting the env variable NO_CONFIG_CLOBBER, if CPU time is costly for
     you.  See also the comments in the handbook about how it works.
     
     
     2. Supported Configurations
     ---------------------------
     
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI
     controllers.
     Adaptec AIC7850 on-board SCSI controllers.
     
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     ** Note: You cannot boot from the SoundBlaster cards as they have no
        on-board BIOS, such being necessary for mapping the boot device into the
        system BIOS I/O vectors.  They're perfectly usable for external tapes,
        CDROMs, etc, however.  The same goes for any other AIC-6x60 based card
        without a boot ROM.  Some systems DO have a boot ROM, which is generally
        indicated by some sort of message when the system is first powered up
        or reset, and in such cases you *will* also be able to boot from them.
        Check your system/board documentation for more details.
     
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     Buslogic 956c PCI SCSI controller
     
     SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
     controllers:
     	ASUS SC-200
       	Data Technology DTC3130 (all variants)
     	NCR cards (all)
     	Symbios cards (all)
     	Tekram DC390W, 390U and 390F
     	Tyan S1365
     
     Tekram DC390 and DC390T controllers (maybe other cards based on the
     AMD 53c974 as well).
     
    -NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     UltraStor 14F, 24F and 34F SCSI controllers.
     
     Seagate ST01/02 SCSI controllers.
     
     Future Domain 8xx/950 series SCSI controllers.
     
     WD7000 SCSI controller.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
     DAT and 8mm Exabyte) and CD ROM drives.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (mcd)   Mitsumi proprietary interface (all models)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface (experimental and should be considered ALPHA
             quality!).
     
     
     2.2. Ethernet cards
     -------------------
     
     Allied-Telesis AT1700 and RE2000 cards
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra is also supported.
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress (not recommended due to driver instability)
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905 PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     Toshiba ethernet cards
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     
     2.3. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards.
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     
     HP4020i, Philips CDD2000 and PLASMON WORM (CDR) drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@decwrl.dec.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 2.1.7-RELEASE and 2.2-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
             ftp://ftp.cdrom.com/cdrom/catalog.
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription
     (-RELEASE and -SNAP subscriptions are entirely separate).  With a
     subscription, you will automatically receive updates as they are released.
     Your credit card will be billed when each disk is shipped and you may cancel
     your subscription at any time without further obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or suggestions, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All but the freebsd-bugs groups can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     5. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     Additional FreeBSD helpers and beta testers:
     
    -        Coranth Gryphon            Dave Rivers 
    +        Coranth Gryphon            Dave Rivers
             Kaleb S. Keithley          Terry Lambert
             David Dawes                Don Lewis
     
     Special mention to:
     
             Walnut Creek CDROM, without whose help (and continuing support)
             this release would never have been possible.
     
             Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
             drive.
     
             Chuck Robey for his donation of a floppy tape streamer for
             testing.
     
             Larry Altneu and Wilko Bulte for providing us with Wangtek
             and Archive QIC-02 tape drives for testing and driver hacking.
     
     	CalWeb Internet Services for the loan of a P6/200 machine for
     	speedy package building.
     
             Everyone at Montana State University for their initial support.
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     
     

    Release Home &footer; diff --git a/es/releases/3.0R/announce.sgml b/es/releases/3.0R/announce.sgml index 972ef45d89..366488c7af 100644 --- a/es/releases/3.0R/announce.sgml +++ b/es/releases/3.0R/announce.sgml @@ -1,119 +1,120 @@ - - + + %navincludes; %includes; ]> &header;

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

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

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

    FreeBSD 3.0-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly as a 4 CD set containing a lot of extra stuff of interest to programmers and general users alike.

    IMPORTANT NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project!

    Like many businesses in the field of high-tech, Walnut Creek CDROM has realized that in order to make any product for an emerging market grow, you have to make a significant investment in such growth, even if it means abandoning short-term profits. Walnut Creek CDROM is the only CDROM vendor who currently does anything like this and it's certainly my hope that you will help support the project by buying (or getting someone else to buy :) one of their CDs. Thanks!

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB page at:

    http://www.cdrom.com/pub/FreeBSD

    And on CD-ROM from Walnut Creek CDROM:

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

    If you are in Japan, please refer to Pacific HiTech for information on ordering a localized (or the english) version of the 3.0 product when it becomes available. Pacific HiTech is now an affiliate of Walnut Creek CDROM for Japanese sales of FreeBSD.

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

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

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

    South Africa

    ftp://ftp.internat.F reeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBS D.ORG/pub/FreeBSD

    Brazil

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

    Finland

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

    Release Home &footer; diff --git a/es/releases/3.0R/errata.sgml b/es/releases/3.0R/errata.sgml index c4cc6715f3..1a24f04680 100644 --- a/es/releases/3.0R/errata.sgml +++ b/es/releases/3.0R/errata.sgml @@ -1,65 +1,66 @@ - - + + %navincludes; %includes; ]> - + &header;
     The file 
     ERRATA.TXT contains post-release ERRATA for 3.0 and should always
     be considered the definitive place to look *first* before reporting
     a problem with this release.  This file will also be periodically
     updated as new issues are reported so even if you've checked this
     file recently, check it again before filing a bug report.  Any
     changes to this file are also automatically emailed to:
     
     	freebsd-stable@freebsd.org
     
     For 3.0 security advisories, see:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest information.
     
     ---- Security Advisories:
     
     Current active security advisories for 3.0:     1
     
     o SA-98:08: IP fragmentation denial of service
     
     Fix: Update to 3.0-current or apply patch supplied with advisory 98:08 in:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-98:08.fragment.asc
     
     ---- System Update Information:
     
     
     o The GPL_MATH_EMULATE kernel option causes a fatal trap during system
       startup.
     
     Fix: Replace the GPL_MATH_EMULATE option with the default math
          emulation option MATH_EMULATE.  This will only affect users who
          have modified their kernel configuration file.  The problem is
    -     corrected in revision 1.16 of the file 
    +     corrected in revision 1.16 of the file
          /usr/src/sys/gnu/i386/fpemul/fpu_entry.c.
     
     
     o DOS partition installs fail to find the installation bits.
     
    - 
    -Fix: Rename C:\FREEBSD to C:\3.0-RELEASE and retry the installation. 
    -     The naming syntax was changed to make DOS more like the other 
    -     types of installation media but the docs on DOS installation 
    -     were not updated properly to reflect this.  The current sysinstall 
    +
    +Fix: Rename C:\FREEBSD to C:\3.0-RELEASE and retry the installation.
    +     The naming syntax was changed to make DOS more like the other
    +     types of installation media but the docs on DOS installation
    +     were not updated properly to reflect this.  The current sysinstall
          now accepts both locations, as it should have to begin with.
     
     

    Release Home &footer; diff --git a/es/releases/3.0R/notes.sgml b/es/releases/3.0R/notes.sgml index 38a6572455..cfcc20c1d3 100644 --- a/es/releases/3.0R/notes.sgml +++ b/es/releases/3.0R/notes.sgml @@ -1,847 +1,848 @@ - - + + %navincludes; %includes; ]> &header;
                                      RELEASE NOTES
                               FreeBSD Release 3.0-RELEASE
     
     This is our first release of 3.0-CURRENT and is aimed primarily at
     early adopters and developers.  Some parts of the documentation may
     not be updated yet and should be reported if and when seen.
     Naturally, any installation failures or crashes should also be
     reported ASAP by sending mail to freebsd-bugs@FreeBSD.org or using the
     send-pr command (those preferring a WEB based interface can also see
     this page).
     
     For information about FreeBSD and the layout of the 3.0-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     This is also hardly the last release on the 3.0-current (HEAD) branch
     and daily snapshot releases will continue as normal following this
     release.  Please install them from:
     
     	ftp://current.freebsd.org/pub/FreeBSD
     
     If you wish to get the latest post-3.0-RELEASE technology.
     
     Table of contents:
     ------------------
     1. What's new since 2.2.X-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 ATM
        2.4 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     6. Acknowledgements
     
     
     1. What's new since 2.2.X-RELEASE
     ---------------------------------
     All changes described here are unique to the 3.0 branch unless
     specifically marked as [MERGED] features.
     
     1.1. KERNEL CHANGES
     -------------------
    -o The 2.2.x SCSI subsystem has been almost entirely replaced with 
    +o The 2.2.x SCSI subsystem has been almost entirely replaced with
       a new "CAM" (Common Access Method) SCSI system which offers
       improved performance, better error recovery and support for more
       SCSI controllers.
     
     o The Host ATM Research Platform ("HARP") software by Network
       Computing Services, Inc. has been integrated into the system.
       See /usr/src/share/examples/atm for more info.
     
     o The SMP (Symmetric MultiProcessing) branch has been merged.
       The kernel is mostly non-reentrant as yet, but work is under way.
     
     o The code from 4.4BSD-Lite2 has been (finally) merged.
     
     o Secure RPC is now supported (and usable with NFS et al).
     
     o Sun's WEBNFS standard is now supported.
     
     o The MSDOS filesystem code now handles VFAT and FAT32 partitions.
       [MERGED: Also in 2.2.7 and later releases on 2.2-STABLE branch]
     
     o ATAPI/IDE CD burner support (BETA).
     
     o ATAPI/IDE tape drive support (BETA).
     
     o Support for using VESA video modes. It is now possible to select and
       use the modes provided by the BIOS on modern videocards. This enables
       fx. 132x60 sized consoles and highres graphics in a generic manner on
    -  hardware that supports it. There is also support for running the 
    +  hardware that supports it. There is also support for running the
       console in rastermode, which allows XFree86 to run a simple 16color
       server in 800x600 on otherwise unsupported video hardware.
     
     o Support for AdvanSys SCSI controllers
     
     o Support for QLogic SCSI and Fibre Channel controllers.
     
     o Support for Adaptec 7890, 7891, 7895, 7896 and 7897 based controllers
       (new 2940/2950/3940/3950 et al).
     
     o The ed0 (wd8xxxx, 3c503, NE2000, HP Lan+) Ethernet device's default IRQ
       has changed from IRQ 5 to IRQ 10.
       The ed1 Ethernet device has been removed.  Use the Userconfig utility
       to change ed0's values to match your network card's settings.
       [MERGED: Both changes are in 2.2.6 and later releases on 2.2-STABLE branch]
     
     o The code responsible for maintaining time of day has been
       rewritten.  New features are:  true support for nanoseconds in
       both kernel and userland, continuous rather than stepwise adjustment
    -  by NTPD and support for synchronizing to high precision external time 
    +  by NTPD and support for synchronizing to high precision external time
       signals.
     
     o Support for the PPS API described in draft-mogul-pps-api-02.txt for
       TTL rising edge inputs via the parallel printer port has been added
       to the printer driver.
     
     o Use the new if_multiaddrs list for multicast addresses rather than the
       previous hackery involving struct in_ifaddr and arpcom.  Get rid of the
       abominable multi_kludge.
     
     o The new if_media selection method for ethernet drivers has been brought
       in, obtained from Jason Thorpe's implementation for NetBSD.
       [MERGED: Also in 2.2.5 and later releases on 2.2-STABLE branch]
     
     o Multi-session ISO-9660 CD-ROMs are now fully supported.  By default, the
       last session will be mounted (including for root mounts).  For non-root
       mounts, mount_cd9660(8) can take an argument to mount a particular
       session instead of the default one.
     
     o The UPAGES are gone from the per-process address space which allows
       complete address space and page table sharing by reference count.
     
     o Newly forked child processes return directly to user mode rather than
       return up through the fork() syscall tree.  This eliminates the kernel
    -  stack copy at fork time and simplifies certain other internal operations. 
    +  stack copy at fork time and simplifies certain other internal operations.
       It is also needed to support the removal of the UPAGES.  (The idea for
       this originally came from NetBSD, but we did it for different reasons.)
     
     o vfork() is now fully functional by taking advantage of the new sharing
       semantics and a significant speedup has been measured.  This can be
       disabled via the kern.fast_vfork sysctl variable in case of problems.
       Statically linked binaries from older releases and other BSD platforms
       are a problem since there was a bug in the 4.4BSD (net2, Lite and Lite2)
       popen() implementation.  rfork() also has access to these facilities,
       intended for supporting kernel assisted threads.
     
     o With the contribution of Berkeley Software Design, Inc., Jonathan Lemmon,
       Mike Smith, Sean Eric Fagan, and John Dyson, VM86 support has been added
       to the kernel, and BSD/OS's contributed doscmd has been ported.
     
     o The SA_NOCLDWAIT flags has been implemented, featuring the System V
       option where a process can express its wish to never get zombies or
       SIGCHLD for dead children.
     
     o An implementation of poll(2) is in place, the core of which is derived
       from the NetBSD implementation.  Both the select() and poll() syscalls
       use the poll device, file and vnode ops routines.
     
     o An implementation of issetugid(2) that is similar to the OpenBSD call
       of the same name.  We set the flag in more cases than OpenBSD - our
       implementation is slightly more paranoid.
     
     o Async IO is implemented (under non-SMP at this stage) with additional
       support for kernel assisted threads.
     
     o Some other misc syscalls for compatability with other systems: getsid(2),
       setpgid(2), nanosleep(2).
     
     o A new syscall signanosleep(2) which is like nanosleep(2), but a specific
       signal mask is used to determine which signals will wake the sleep.  In
       a nutshell this is 'wait for a given set of signals for up to a certain
       amount of time'.
     
     o sleep(3) and usleep(3) are now implemented in terms of signanosleep(2)
       and now have correct SIGALRM interaction semantics and sleep(3) correctly
       returns the time remaining.
     
     o An in-kernel linker is implemented and intended to replace the lkm system
       and the bogosity that goes with it.
     
     o All supported network protocols have been updated to avoid the ``big
       switch'' pr_usrreq(), and to pass a process pointer down to each user
       request that might need process credentials or want to sleep,
       replacing the previous hodgepodge of inspecting curproc (which only
       occasionally did the right thing) and the SS_PRIV socket state flag.
       The latter has now been eliminated, along with the SO_PRIVSTATE socket
       option which cleared it.  Protocols are now also given the opportunity
       to override the generic send, receive, and poll routines, which will
       make it possible for a more efficient, protocol-specific
       implementation of these entry points in later releases.  Finally, many
       parts of the network code have been modified to cease storing socket
       addresses and other metainformation in mbufs, in preparation for the
       eventual elimination thereof.  The mechanism by which socket addresses
       are now returned is still highly subject to change as we experiment to
       discover the most efficient method.
     
     o Responses to multicast ICMP ECHO REQUEST (``ping'') and ADDRESS MASK
       REQUEST packets can now be disabled via sysctl.  The netstat program
       will print out statistics on how many times this happens.
     
     o A subtle and seldom encountered bug in ffs has been fixed.
     
     o The VFS name cache has been reworked to be more accountable and efficient.
     
     o The generic part of VOP_LOOKUP() has been put it in system-wide function
       which filesystems can rely on for the canonical stuff.
     
     o Vnode freelist handling has been hauled over.  Vnodes are only on the
       freelist if nobody cares about them.
     
     o The kernel provides assistance to getcwd() from data stored in the name
       cache if possible.
     
     o An interrupt driven configuration hook mechanism has been implemented.
       This allows drivers to postpone part of their configuration until after
       interrupts are fully enabled.  This speeds booting because busy-waiting
       is avoided for things like sub device probing (eg: SCSI bus probes).
     
     o The timeout(9) system in the kernel has been overhauled.  This gives
       O(1) insertion and removal of callouts and an O(hash chain length)
       amount of work to be performed in softclock.  The original paper is at:
    -        http://www.cs.berkeley.edu/~amc/research/timer/ 
    +        http://www.cs.berkeley.edu/~amc/research/timer/
     
     o Changes in driver buffer queuing to deal with ordered transactions.  This
       is intended for sequencing data and metadata writes in the filesystem code
       once fully supported.
     
     o EISA Shared interrupts are now supported, working with the framework
       originally for supporting PCI shared interrupts.
     
     o Support for the Comtrol Rocketport card.
     
     o IPFW's packet and byte counters have been expanded from 32 to 64 bits,
       a `FWD' operation has been added to ipfw to support transparent
       proxying and the divert operation has changed slightly - see the man
       pages for natd(8) and ipfw(8) for more information.
     
     o New Plug and Play (PnP) support that allows you to (re)configure PnP
       devices.  Also support modems being detected by the PnP part and
       automatically attached.
       [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch]
     
     o Import of new sound code from Luigi Rizzo.  This code is still being
       developed, but has support for a number of different cards.
       [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch]
     
     o The psm, mse and sysmouse drivers are improved to provide better mouse
       support.  In particular, the psm driver now supports various ``wheeled''
       mice.
       [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch]
     
     o Added support for SMC EtherPower II 10/100 Fast Ethernet card
       (aka SMC9432TX based on SMC83c170 EPIC chip).
       [MERGED: Also in 2.2.7 and later releases on 2.2-STABLE branch]
     
     o Added support for ATAPI floppy drives (LS-120).
       [MERGED: Also in 2.2.7 and later releases on 2.2-STABLE branch]
     
     o Added support for IBM Etherjet and other Crystal Semiconductor
       CS89x0-based NICs.
       [MERGED: Also in 2.2.7 and later releases on 2.2-STABLE branch]
     
     o Added support for Texas Instruments TNET100 'ThunderLAN' PCI NIC.
       [MERGED: Also in 2.2.8 and later releases on 2.2-STABLE branch]
     
     o Added full bus master DMA support for 3c900 and 3c905 adapters and
       added support for the 3c905B.
       [MERGED: Also in 2.2.8 and later releases on 2.2-STABLE branch]
     
     
     1.2. SECURITY FIXES
     -------------------
     [MERGED: all changes soon after specified date in 2.2-STABLE branch]
     
     97/7/29 Lots of lpr/lpd security fixes merged from OpenBSD.
     97/8/22 buffer overflows in tip corrected (benign since tip isn't
             set[ug]id)
     97/8/26 buffer overflow in glob fixed, no know exploits
     97/8/27 vacation security problem with sendmail corrected (SNI)
     97/8/29 inetd sleeps less when children exit, making DoS attacks much
             harder.
     97/8/29 fts now race-proof and find -execdir added (-current only)
     97/8/31 games setuid -> setgid.  Makes any games exploits benign (only
             score files vulnerable).  Please report any problems to
             eivind@FreeBSD.org (score-file ownership problems are known)
     97/12/3 Add Intel's suggested fix for the F00F bug.  If you don't have
             a Pentium, the NO_F00F_HACK kernel option will disable it.
     98/1/20 More robust protection against LAND attacks now incorporated.
     
     The suidperl vulnerability mentioned in the CERT advisory CA-97.17 is
     also believed to be fixed.
     
     KerberosIV is now merged.
     
     
     1.3. USERLAND CHANGES
     ---------------------
     The default binary type (and compiler toolchain) has been
     switched from a.out to ELF.  This gives us access to much
     newer compiler technology (much of which didn't support a.out),
     allows for smaller executables and provides much better
     support for languages like C++, among many other advantages.
     Older a.out libraries and binaries will, of course, continue to work
     and provisions have been made for having both varieties installed if
     and as necessary for transitional purposes.
     
     Perl4 has now been replaced by Perl5 as a standard part of the
     system.
     
     The default username length has increased to 16 characters.
     Caution:  Old utmp/wtmp files will NOT work with this change since
     the data records will be of the old size.  For a conversion utility
     to aid with this, see /usr/src/tools/3.0-upgrade.
     
     /etc/sysconfig now replaced by more compact /etc/rc.conf file
     [MERGED: Also in 2.2.1 and later releases on 2.2-STABLE branch]
     
     fdisk(8) now numbers disk slices from 1 to 4 rather than from 0 to 3.
     This brings it in line with the numbers used in the device names
     in /dev.
     
     The Amd automounter has been updated from the 1993 4.4BSD version to
     the latest current version of am-utils.  Map options have changed
     somewhat, and a new configuration file, /etc/amd.conf, is supported.
     See ``man 5 amd.conf''.
     
     The ``picobsd'' package for creating custom FreeBSD boot floppies
     and "mini systems" has been brought into /usr/src/release/picobsd.
     See file:/usr/src/release/picobsd/README.html for further information.
     
     When operating over the network, finger(1) no longer closes the socket
     immediately after sending its request, but instead waits for the
     remote end to close first.  (The specification is ambiguous, so we are
     following the behavior which interoperates with the most servers.)
     This means that it is now possible to use the MIT directory and finger
     people at certain broken Linux machines.
     
     There is a new flag to fetch(1) which allows it to talk to certain
     broken HTTP implementations which react badly to a request message
     immediately followed by a close of the connection.
     
     netstat(1) now uses sysctl(3) to retrieve more statistics groups and
     uses the correct, unsigned format for printing most of them out.
     
     A new VGA library (/usr/src/lib/libvgl) now exists for doing simple
     VGA graphics to syscons ttys (sort of like Linux's libSVGA).
     [MERGED: Also in 2.2.5 and later releases on 2.2-STABLE branch]
     
     Xntpd's syslogging has been moved out into a facility of its own
     (LOG_NTP, userland name "ntp").
     
     A new pair of ioctl's has been added: SIOC[SG]IFGENERIC.  The intent
     is to provide for a hook to pass arbitrary ioctl subcommands down to a
     network interface driver.  This is for example necesseray for PPP
     drivers to communicate things like CHAP names and secrets, or variable
     options between the driver and a userland utility.
     
     sppp(4) has been improved a fair bit since FreeBSD 2.2.X.  It now
     employs a full-fledged PPP state machine, offers a lot more of LCP and
     IPCP negotiation, making it ready for dial-on-demand connections (like
     those that are often running over ISDN).  It also offers PAP or CHAP
     authentication.  The userland counterpart spppcontrol(8) is also the
     first program that utilizes the abovementioned SIOC[SG]IFGENERIC ioctl
     commands.
     
     moused(8) has been modified to support various mice with a ``wheel''.
     It also automatically recognizes mice which support the PnP COM device
    -standard, so that the user is no longer required to supply a mouse 
    +standard, so that the user is no longer required to supply a mouse
     protocol type on the command line.
     [MERGED: Also in 2.2.6 and later releases on 2.2-STABLE branch]
     
     ppp(8) supports many additional features including the PPP Multilink
     Protocol (rfc1990), PPP Callback (with CBCP extensions) and client
     side DNS negotiation.  Refer to the README.changes file in the source
     directory for details of possible configuration conflicts.
     
     Pthread read/write locks as defined by the Single UNIX Specification,
     Version 2, have been added to the POSIX threads library, libc_r.
     
     System files are now owned by user `root', group `wheel'.  UID 0 is far
     more protected than `bin'.  Especially over NFS.
     
     /bin/sh signal and trap handling reworked. Among other things, this
     makes tty-mode emacs work when called from system(2), i.e. by a mail
     agent. Several syntax bugs have been fixed.
     [MERGED: Also in 2.2.8 and later releases on 2.2-STABLE branch]
     
     systat(1), iostat(8), rpc.rstatd(8), and vmstat(8) have been
     overhauled to use the new devstat(3) library and devstat(9) statistics
     subsystem.  Among other enhancements, these utilities (well, with the
     exception of rpc.rstatd(8)) now print out more useful statistics, and can
     see statistics for all devices in the system, not just the first 8.
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920/2940/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7880, AIC789x, on-board SCSI controllers.
     
     AdvanSys SCSI controllers (all models).
     
     Buslogic 545S & 545c
     Buslogic 445S/445c VLB SCSI controller
     Buslogic 742A, 747S, 747c EISA SCSI controller.
     Buslogic 946c PCI SCSI controller
     Buslogic 956c PCI SCSI controller
     
     DPT SCSI/RAID controllers (most variants).
     
     SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI
     controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     
     QLogic SCSI and Fibre Channel controllers.
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface
     
     SCSI TAPE SUPPORT:
     
       The CAM SCSI tape driver doesn't yet handle older (and many times broken)
       tape drives very well.  If you've got an older SCSI-1 tape drive, like an
       Exabyte 8200 or older QIC-type tape drive, it may not work properly with
       the CAM tape driver.  This is obviously a known problem, and we're
       working on it.
     
       Newer tape drives that are mostly SCSI-2 compliant should work fine.
       e.g., DAT (DDS-1, 2 and 3), DLT, and newer Exabyte 8mm drives should
       work fine.
     
       If you want to find out if your particular tape drive is supported, the
       best way to find out is to try it!
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
       Tekram DC390 and DC390T controllers (maybe other cards based on the
       AMD 53c974 as well).
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
       Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
       Adaptec 152x series ISA SCSI controllers
       Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
       and SoundBlaster SCSI cards.
     
       [ Note:  There is work-in-progress to port the AIC-6260/6360 and
         UltraStor drivers to the new CAM SCSI framework, but no estimates on
         when or if they will be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       Floppy tape interface (Colorado/Mountain/Insight)
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     2.2. Ethernet cards
     -------------------
     Allied-Telesis AT1700 and RE2000 cards
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     Toshiba ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     2.3 ATM
     -------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signalling Protocols
             - The ATM Forum UNI 3.1 signalling protocol
             - The ATM Forum UNI 3.0 signalling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signalling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     2.4. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 3.0-RELEASE and 2.2.x-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the
     following issues may affect you, depending of course on your chosen
     method of upgrading.  There are two popular ways of upgrading
     FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     In the case of using sources, there are simply two targets you need to
     be aware of: The standard ``world'' target, which will upgrade a 2.x
     system to 3.0, or the ``aout-to-elf'' target, which will both upgrade
     and convert the system to ELF binary format.
     In the case of using the binary upgrade option, the system will go
     straight to 3.0/ELF but also populate the /<basepath>/lib/aout
     directories for backwards compatibility with older binaries.
     
     In either case, going to ELF will mean that you'll have somewhat
     smaller binaries and access to a lot more compiler goodies which have
     been already been ported to other ELF environments (our older and
     somewhat crufty a.out format being largely unsupported by most other
     software projects), but on the downside you'll also have access to far
     fewer ports and packages since many of those have not been adapted to
     ELF yet.  This will occur in time, but those who wish to retain access
     to the greatest number of packages and 3rd-party binaries should
     probably stick with a.out.
     
     The kernel is also still in a.out format at this time so that older
     LKMs and library interfaces can continue to work, but a full
     transition to ELF will occur at some point after 3.0-RELEASE.  Those
     wishing to generate dynamic kernel components should therefore use the
     newer KLD mechanism rather than the older LKM format - the LKM format
     is not long for this world and will soon be unsupported!
     
     [ other important upgrading notes should go here]
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
     
             Justin M. Seger for almost
             single-handedly converting the ports collection to ELF.
     
             Doug Rabson and
             John Birrell
             for making FreeBSD/alpha happen and to the NetBSD project for
             substantial indirect aid.
     
             Peter Wemm for the new kernel
             module system (with substantial aid from Doug Rabson).
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/3.1R/announce.sgml b/es/releases/3.1R/announce.sgml index e446cbd162..cd8180d56c 100644 --- a/es/releases/3.1R/announce.sgml +++ b/es/releases/3.1R/announce.sgml @@ -1,112 +1,113 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Mon, 15 Feb 1999 12:00:03 -0700
    From: "Jordan K. Hubbard" <jkh@freebsd.org>
    Subject:FreeBSD 3.1 is now released!

    We are pleased, as always, to announce the availability of 3.1-RELEASE, the much anticipated follow-on release to FreeBSD 3.0 (released November, 1998). Many hundreds of bug fixes and general enhancements have been made to the system so please see the release notes for more information.

    FreeBSD 3.1-RELEASE is available on ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from Walnut Creek CDROM, from where it will be shipping shortly as a 4 CD set containing a lot of extra stuff of interest to programmers and general users alike.

    IMPORTANT NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project!

    Like many businesses in the field of high-tech, Walnut Creek CDROM has realized that in order to make any product for an emerging market grow, you have to make a significant investment in such growth, even if it means abandoning short-term profits. Walnut Creek CDROM is the only CDROM vendor who currently does anything like this and it's certainly my hope that you will help support the project by buying (or getting someone else to buy :) one of their CDs. Thanks!

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB page at:

    http://www.cdrom.com

    And on CD-ROM from Walnut Creek CDROM:

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

    If you are in Japan, please refer to Pacific HiTech for information on ordering a localized (or the english) version of the 3.1 product when it becomes available. Pacific HiTech is now an affiliate of Walnut Creek CDROM for Japanese sales of FreeBSD.

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

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

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

    South Africa

    ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    Release Home &footer; diff --git a/es/releases/3.1R/errata.sgml b/es/releases/3.1R/errata.sgml index 1101324cdb..67b6ebfd68 100644 --- a/es/releases/3.1R/errata.sgml +++ b/es/releases/3.1R/errata.sgml @@ -1,84 +1,85 @@ - - + + %navincludes; %includes; ]> - + &header;
     The file 
     ERRATA.TXT contains post-release ERRATA for 3.1 and should always
     be considered the definitive place to look *first* before reporting
     a problem with this release.  This file will also be periodically
     updated as new issues are reported so even if you've checked this
     file recently, check it again before filing a bug report.  Any
     changes to this file are also automatically emailed to:
     
     	freebsd-stable@freebsd.org
     
     For all FreeBSD security advisories, see:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest information.
     
     ---- Security Advisories:
     
     Current active security advisories for 3.1:     None
     
     ---- System Update Information:
     
     o  Some packages, like netscape, will fail to install if chosen
        at initial system installation time, in some cases claiming
        that the "compat22" distribution needs to be installed even
        though it has, indeed, been installed.
     
     
     Fix: The problem here is that though the compatibility a.out libraries
          may have been installed from compat22 and as part of the XFree86
          distribution, the a.out library (ldconfig) cache has not yet been
          built given that this doesn't happen until the system has booted
          completely at least once.  This causes packages which require the
          old a.out libraries (like netscape) to get confused if they're
          installed before that has occurred.  To work around the problem,
          simply complete the installation as normal and come up fully,
          then re-run /stand/sysinstall (or use the pkg_add(1) command
          directly) to re-install the failing package(s).
     
     
    -o  Kernel change information is not saved in the new kernel, even 
    +o  Kernel change information is not saved in the new kernel, even
        though this is claimed to work in the docs.
     
     
    -Fix: The change information is being written out, in fact, but to the 
    +Fix: The change information is being written out, in fact, but to the
          wrong location.  move /kernel.config to /boot/kernel.conf (if it
    -     exists, otherwise there were no changes to save) and add the 
    +     exists, otherwise there were no changes to save) and add the
          following lines to /boot/loader.rc:
    -        
    +
             load /kernel
             load -t userconfig_script /boot/kernel.conf
             autoboot 5
    -     
    +
          This will cause the kernel change information to be read in and
          used properly (and you just learned a little about the new 3-stage
          loader in the process, so the exercise wasn't a total loss).
     
     
     o  DOS installation fails when you actually follow the instructions
        to install stuff under C:\FREEBSD\BIN\... and so on.
     
     
     Fix: The instructions are correct but the code was wrong in 3.1-RELEASE,
    -     sysinstall looking instead directly under C:\ (e.g. C:\BIN\...) 
    +     sysinstall looking instead directly under C:\ (e.g. C:\BIN\...)
          or under C:\RELEASES\ (C:\RELEASES\BIN\... and so on).  Fixed
          in 3.1-STABLE.
     
     

    Release Home &footer; diff --git a/es/releases/3.1R/notes.sgml b/es/releases/3.1R/notes.sgml index 4d841b79dc..3ebd9c9249 100644 --- a/es/releases/3.1R/notes.sgml +++ b/es/releases/3.1R/notes.sgml @@ -1,607 +1,608 @@ - - + + %navincludes; %includes; ]> &header;
     
                                      RELEASE NOTES
                                FreeBSD Release 3.1-RELEASE
     
     Welcome to 3.1-RELEASE, a full follow-on to the 3.0-RELEASE
     released November 1998 and which marked the beginning of the
     3.0-STABLE branch.  In the 4 months since 3.0 was released, many
     hundreds of bug fixes and general enhancements were made to the
     system.  Please see relevant details below.
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a WEB based interface can also see
     this page).
     
     For information about FreeBSD and the layout of the 3.1-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     Table of contents:
     ------------------
     1. What's new since 3.0-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 ATM
        2.4 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     6. Acknowledgements
     
     
     1. What's new since 3.0-RELEASE
     ---------------------------------
     
     1.1. KERNEL CHANGES
     -------------------
     
     Added driver support for fast ethernet adapters based on the
     RealTek 8129/8139 and Accton MPX 5030/5038 chips, including the
     SMC EZ Card 10/100 PCI 1211-TX.
     
     Added driver support for Lite-On PNIC-based fast ethernet cards
     including the LinkSys LNE100TX, NetGear FA310TX Rev. D1 and
     Matrox FastNIC 10/100.
     
    -Added driver support for fast ethernet adapters based on the 
    +Added driver support for fast ethernet adapters based on the
     Macronix 98713, 98713A, 98715, 98715A and 98725 chips.
     
     Added driver support for fast ethernet adapters based on the
     Winbond W89C840F chip.
     
     Added driver support for fast ethernet adapters based on the
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" chips.
     
     Added driver support for pocket ethernet adapters based on the
     RealTek RTL 8002 chip.
     
     Added driver support for fast ethernet adapters based on the
     ASIX Electronics AX88140A chip.
     
     Integrated isdn4bsd from the isdn4bsd project group into the
     regular system.
     
     System console driver (sc0) now broken into individual stand-alone
     modules, partly in preparation for USB keyboards, mice, etc.
     
     Phillips I2C/SMBUS support.
     
     Initial support for USB devices (some keyboards, mice).
     
     The lpt driver is now deprecated. Please use ppbus with the ppc driver
     instead (see the ppc(4) and ppbus(4) man pages for details). At some
     point before the next release, the old lpt driver will be removed and
     the nlpt driver will be renamed to lpt.
     
     
     1.2. SECURITY FIXES
     -------------------
     See ftp://ftp.freebsd.org/pub/FreeBSD/CERT/ for details:
       CERT Advisory CA-98-13-tcp-denial-of-service closed.
       FreeBSD-SA-98:08 (IP fragmentation denial of service) closed.
     
     KerberosIV more fully supported.
     
     
     1.3. USERLAND CHANGES
     ---------------------
     When using ipfw(8) with the syntax of the first synopsis line from the
     man page (i. e., with a rules file), it can now optionally be run through
     a preprocessor (m4, cpp) so it's possible to use symbolic names and other
     constructs that make maintenance easier.
     
     Support for PAM (Pluggable Authentication Modules) including
     modules for radius, TACACS, S/Key, Kerberos, Unix (passwd) and
     other authentication methods.
    - 
    +
     Sendmail upgraded to version 8.9.2.
     
     AMD, texinfo, global and many other various utilities updated.
     
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.  The DPT SmartRAID/CACHE V
     is not yet supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
     	Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     QLogic 1020, 1040, 1040B and 2100 SCSI and Fibre Channel Adapters
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
       Tekram DC390 and DC390T controllers (maybe other cards based on the
       AMD 53c974 as well).
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
       Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
       Adaptec 152x series ISA SCSI controllers
       Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
       and SoundBlaster SCSI cards.
     
       [ Note:  There is work-in-progress to port the AIC-6260/6360 and
         UltraStor drivers to the new CAM SCSI framework, but no estimates on
         when or if they will be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       Floppy tape interface (Colorado/Mountain/Insight)
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     2.2. Ethernet cards
     -------------------
     Allied-Telesis AT1700 and RE2000 cards
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 fast ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC fast ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 fast ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Winbond W89C840F fast ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE530TX
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100baseTX
       Racore 8148 10baseT/100baseTX/100baseFX multi-personality
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980 Fast Etherlink XL server adapter
     
     Toshiba ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     2.3 ATM
     -------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signalling Protocols
             - The ATM Forum UNI 3.1 signalling protocol
             - The ATM Forum UNI 3.0 signalling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signalling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     2.4. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 3.1-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite F
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the
     following issues may affect you, depending of course on your chosen
     method of upgrading.  There are two popular ways of upgrading
     FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     In the case of using sources, there are simply two targets you need to
     be aware of: The standard ``upgrade'' target, which will upgrade a 2.x
     or 3.0 system to 3.1 and the ``world'' target, which will take an
     already upgraded system and keep it in sync with whatever changes have
     happened since the initial upgrade.
     
     In the case of using the binary upgrade option, the system will go
     straight to 3.1/ELF but also populate the /<basepath>/lib/aout
     directories for backwards compatibility with older binaries.
     
     In either case, going to ELF will mean that you'll have somewhat
     smaller binaries and access to a lot more compiler goodies which have
     been already been ported to other ELF environments (our older and
     somewhat crufty a.out format being largely unsupported by most other
     software projects).  Those who wish to retain access to the older
     a.out dynamic executables should be sure and install the compat22
     distribution.
     
     [ other important upgrading notes should go here]
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
     
             Steve Price for his work
             in building and organizing the packages and, as always,
             Satoshi Asami for his
             work on the ports collection.
     
             Doug Rabson and
             John Birrell
             for making FreeBSD/alpha happen and to the NetBSD project for
             substantial indirect aid.
     
             Peter Wemm for the new kernel
             module system (with substantial aid from Doug Rabson).
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     
     

    Release Home &footer; diff --git a/es/releases/3.2R/announce.sgml b/es/releases/3.2R/announce.sgml index 03d9ac2562..5c417a8040 100644 --- a/es/releases/3.2R/announce.sgml +++ b/es/releases/3.2R/announce.sgml @@ -1,99 +1,100 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Mon May 17 19:28:17 PDT 1999
    From: "Jordan K. Hubbard" <jkh@freebsd.org>
    Subject:FreeBSD 3.2 is released!

    It is my usual pleasure to announce the availability of 3.2-RELEASE, our follow-on to release to FreeBSD 3.1 (released February, 1999). Many bug fixes and general enhancements have been made to the system and a number of new features added, so please see the release notes for more information.

    FreeBSD 3.2-RELEASE is available at ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from The FreeBSD Mall, from where it will be shipping soon on a 4 CD set containing installation bits for both the x86 and Alpha architectures as well a lot of other material of general interest to programmers and end-users alike.

    NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project!

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB page at:

    http://www.freebsdmall.com

    and

    http://www.cdrom.com

    And directly from Walnut Creek CDROM:

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

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

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

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

    South Africa

    ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    Release Home &footer; diff --git a/es/releases/3.2R/errata.sgml b/es/releases/3.2R/errata.sgml index f2de52ea29..18c5ade1e2 100644 --- a/es/releases/3.2R/errata.sgml +++ b/es/releases/3.2R/errata.sgml @@ -1,76 +1,77 @@ - - + + %navincludes; %includes; ]> - + &header;
     The file 
     ERRATA.TXT contains post-release ERRATA for 3.2 and should always
     be considered the definitive place to look *first* before reporting
     a problem with this release.  This file will also be periodically
     updated as new issues are reported so even if you've checked this
     file recently, check it again before filing a bug report.  Any
     changes to this file are also automatically emailed to:
     
     	freebsd-stable@freebsd.org
     
     For all FreeBSD security advisories, see:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest information.
     
     ---- Security Advisories:
     
     Current active security advisories for 3.2:     None
     
     ---- System Update Information:
     
     o The compat20 and compat21 distributions install themselves into
       /usr/lib/compat.  The compat20/compat21 distributions are a.out libraries,
       thus they should live in /usr/lib/compat/aout to match the
       "ldconfig_paths_aout" configuration in /etc/defaults/rc.conf.
    -                                                                              
    +
     Fix: cd /usr/lib/compat
          mkdir -p aout
          mv lib*.so.*.* aout
     
     o /usr/bin/gdb crashes when debugging core files from static programs
     
     Fix: This was corrected in revision 1.3.2.2 of solib.c. Obtain the fixed
          version via CVSup (see instructions in handbook) or apply the patch
          from our CVSweb service.
     
    -o While booting the install floppy, user sees the following message 
    +o While booting the install floppy, user sees the following message
       and nothing seems to happen, nor can anything be entered from the keyboard:
    - 
    +
          Keyboard: no
     
    -Fix: Due to a lack of space, full support for old XT/AT (84-key) keyboards 
    +Fix: Due to a lack of space, full support for old XT/AT (84-key) keyboards
          is no longer available in the bootblocks.  Some notebook computers may
    -     also have this type of keyboard and if you are still using this kind of 
    +     also have this type of keyboard and if you are still using this kind of
          hardware, you will see the above message about no keyboard being found
          when you boot from an installation CD-ROM or floppy.
    -  
    +
          As soon as you see the message, hit the space bar and you will see
          the following prompt:
    -  
    +
            >> FreeBSD/i386 BOOT
    -       Default: x:xx(x,x)/boot/loader 
    +       Default: x:xx(x,x)/boot/loader
            boot:
    -  
    +
          Then enter `-Dh', and things should proceed normally with your keyboard
          type.  This only happens once at initial installation time and will
          not be a problem afterwards.
     
     

    Release Home &footer; diff --git a/es/releases/3.2R/notes.sgml b/es/releases/3.2R/notes.sgml index 44959ba32c..873c1207ca 100644 --- a/es/releases/3.2R/notes.sgml +++ b/es/releases/3.2R/notes.sgml @@ -1,607 +1,608 @@ - - + + %navincludes; %includes; ]> &header;
     
                                      RELEASE NOTES
                                   FreeBSD 3.2-RELEASE
     
     Welcome to 3.2-RELEASE, a full follow-on to the 3.1-RELEASE
     released February 1999 and which marked the beginning of the
     3.0-STABLE branch.  In the 4 months since 3.1 was released, many
     hundreds of bug fixes and general enhancements were made to the
     system.  Please see relevant details below.
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a WEB based interface can also see
     this page).
     
     For information about FreeBSD and the layout of the 3.2-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     Table of contents:
     ------------------
     1. What's new since 3.1-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 ATM
        2.4 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     6. Acknowledgements
     
     
     1. What's new since 3.1-RELEASE
     ---------------------------------
     
     1.1. KERNEL CHANGES
     -------------------
     
     Added driver support for PCI gigabit ethernet adapters based on
     the Alteon Networks Tigon 1 and Tigon 2 chipsets, including the
     Alteon AceNIC, 3Com 3c985 and Netgear GA620.
     
     Support for USB devices further improved.
     
     Support has been added for direct access to NTFS filesystems.
     
     Support has been added for Joliet extensions on ISO 9660 filesystems.
     Only iso8859-1 characters (latin-1) are supported at this time, though.
     
     Support has been added for Adaptec 2930U2 and 3950U2 SCSI cards.
     
     There have been a couple of kernel changes that will break the binary
     interface for clients of the CAM passthrough interface or the devstat(9)
     statistics interface.  These changes were made to fix some interface
     deficiencies.  We regret any inconvenience this will cause, but we
     anticipate that this will have minimal impact as there are no known
     commercial binary-only applications that use either interface.  This will
     require that programs that use those two interfaces be recompiled.  Ports
     that use the CAM interface include xmcd, tosha, SANE, cdrecord and cdda2wav.
     Ports that use the devstat interface include xsysinfo and xperfmon.
     
     
     1.2. SECURITY FIXES
     -------------------
     Descriptor leak bug which was potentially open to a denial of service attack
    -(by local users) was closed.  REF: KKIS.05051999.003b 
    +(by local users) was closed.  REF: KKIS.05051999.003b
     
     
     1.3. USERLAND CHANGES
     ---------------------
    -The Internet Software Consortium's DHCP client has been added to the 
    +The Internet Software Consortium's DHCP client has been added to the
     base system.
    - 
    +
     Sendmail upgraded to version 8.9.3.
     
     Tar now supports compressing via bzip2 with the new
     -y/--bzip2/--bunzip2 flags.
     
     TCP Wrappers is now part of the base system.  inetd, the port mapper,
     and sendmail are now linked agaist libwrap.  The "PROCESS_OPTIONS"
     syntax is the default.  Note that you do not need to use tcpd in
     /etc/inetd.conf.  See `man 5 hosts_options' and `man 8 inetd` for
     more information.
     
     Gdb has been updated to version 4.18 and is now part of the standard
     release for FreeBSD/alpha.
     
     Camcontrol now allows users to view the number of tagged openings for
     any given device, and allows users to set the number of tagged openings
     for any device that supports tagged queueing.
     
     Camcontrol also now allows users to change SCSI negotiation parameters
     (e.g. sync rate, offset, bus width, disconnection) for devices on certain
     controllers.  Note that this feature is only fully functional for Adaptec
     7xxx series controllers, Advansys narrow controllers and NCR/Symbios
     controllers.
     
     Systat, vmstat, and iostat now print out statistics in a more "interesting"
     order based on "importance" of the device vs. the probe order.
     
     And quite a number of bugs, both in the user and kernel, fixed as
     a result of user feedback for 3.1-RELEASE.
     
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/2930U2/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.  The DPT SmartRAID/CACHE V
     is not yet supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
     	Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters.
     QLogic 2100 Fibre Channel Adapters (private loop only).
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
       Tekram DC390 and DC390T controllers (maybe other cards based on the
       AMD 53c974 as well).
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
       Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
       Adaptec 152x series ISA SCSI controllers
       Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
       and SoundBlaster SCSI cards.
     
       [ Note:  There is work-in-progress to port the AIC-6260/6360 and
         UltraStor drivers to the new CAM SCSI framework, but no estimates on
         when or if they will be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       Floppy tape interface (Colorado/Mountain/Insight)
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     2.2. Ethernet cards
     -------------------
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI gigabit ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       Alteon AceNIC (Tigon 1 and 2)
       3Com 3c985-SX (Tigon 1 and 2)
       Netgear GA620 (Tigon 2)
       Silicon Graphics Gigabit Ethernet
       DEC/Compaq EtherWORKS 1000
       NEC Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 fast ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC fast ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 fast ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Winbond W89C840F fast ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE530TX
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100baseTX
       Racore 8148 10baseT/100baseTX/100baseFX multi-personality
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA
     (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980 Fast Etherlink XL server adapter
     
     Toshiba ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     PCMCIA ethernet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     2.3 ATM
     -------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signalling Protocols
             - The ATM Forum UNI 3.1 signalling protocol
             - The ATM Forum UNI 3.0 signalling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signalling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     2.4. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 and Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     3.2. CDROM
     ----------
     
     FreeBSD 3.2-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite F
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.freebsdmall.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the
     following issues may affect you, depending of course on your chosen
     method of upgrading.  There are two popular ways of upgrading
     FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     In the case of using sources, there are simply two targets you need to
     be aware of: The standard ``upgrade'' target, which will upgrade a 2.x
     or 3.0 system to 3.2 and the ``world'' target, which will take an
     already upgraded system and keep it in sync with whatever changes have
     happened since the initial upgrade.
     
     In the case of using the binary upgrade option, the system will go
     straight to 3.2/ELF but also populate the /<basepath>/lib/aout
     directories for backwards compatibility with older binaries.
     
     In either case, going to ELF will mean that you'll have somewhat
     smaller binaries and access to a lot more compiler goodies which have
     been already been ported to other ELF environments (our older and
     somewhat crufty a.out format being largely unsupported by most other
     software projects).  Those who wish to retain access to the older
     a.out dynamic executables should be sure and install the compat22
     distribution. Notice that the a.out libraries won't be accessible
     until the system is rebooted, which may cause trouble with certain
     a.out packages.
     
     Also, do not use install disks or sysinstall from previous versions,
     as version 3.1 introduced a new bootstrapping procedure, requiring
     new boot blocks to be installed (because of elf kernels), and version
     3.2 has further modifications to the bootstrapping procedure.
     
     [ other important upgrading notes should go here]
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     
     

    Release Home &footer; diff --git a/es/releases/3.3R/announce.sgml b/es/releases/3.3R/announce.sgml index ced2b145bd..fa35b2ed73 100644 --- a/es/releases/3.3R/announce.sgml +++ b/es/releases/3.3R/announce.sgml @@ -1,118 +1,119 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Fri, 17 Sep 1999 05:06:44 -0700
    From: "Jordan K. Hubbard" <jkh@freebsd.org>
    Subject:FreeBSD 3.3-RELEASE is now available.

    Yes, it's that time again! I'm very happy to announce the availability of FreeBSD 3.3-RELEASE, the latest in our line of releases from the 3.x-STABLE branch. The follow-on to FreeBSD 3.2 (released in May, 1999), a lot of new drivers have been added, many bugs were fixed and several important security issues where dealt with. Please see the release notes for more information.

    FreeBSD 3.3-RELEASE is available at ftp.freebsd.org and various FTP mirror sites throughout the world. It can also be ordered on CD from The FreeBSD Mall, from where it will be shipping soon on a 4 CD set containing installation bits for the x86 architectures, as well a lot of other material of general interest to programmers and end-users alike. (3.3-RELEASE for the Alpha architecture is available from the FTP site).

    NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project! We are also trying something new with 3.3-RELEASE in making disc #1 from Walnut Creek CDROM's official distribution available via anonymous FTP. This is the most important CD of their 4 set, one which will allow users to install the base system and all of its most important add-ons from a single ISO 9660 image. We are doing this because the ISO image is rapidly becoming the preferred format for distributing operating system releases and we're certainly not going to go out of our way to make FreeBSD harder to "test drive" if providing the standard NFS/FTP network installation methods is no longer enough. We can't promise that all the mirror sites will carry the rather large installation (660MB) image, but it will at least be available from:

    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.3-install.cd0.

    along with the more traditional 3.3-RELEASE bits. If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from Walnut Creek CDROM.

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB page at:

    http://www.freebsdmall.com

    and

    http://www.cdrom.com

    And directly from Walnut Creek CDROM:

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

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Romania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

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

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

    South Africa

    ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    Release Home &footer; diff --git a/es/releases/3.3R/errata.sgml b/es/releases/3.3R/errata.sgml index 77239d27de..ff3d46d871 100644 --- a/es/releases/3.3R/errata.sgml +++ b/es/releases/3.3R/errata.sgml @@ -1,86 +1,87 @@ - - + + %navincludes; %includes; ]> - + &header;
     The file 
     ERRATA.TXT contains post-release ERRATA for 3.3 and should always
     be considered the definitive place to look *first* before reporting
     a problem with this release.  This file will also be periodically
     updated as new issues are reported so even if you've checked this
     file recently, check it again before filing a bug report.  Any
     changes to this file are also automatically emailed to:
     
     	freebsd-stable@freebsd.org
     
     For all FreeBSD security advisories, see:
     
     ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest information.
     
     ---- Security Advisories:
     
     Current active security advisories for 3.3:     None
     
     ---- System Update Information:
     
     The fvwm desktop choice in the X Desktops menu doesn't work.
    -                                                                              
    +
     Fix: Install fvwm from /usr/ports/x11-wm/fvwm2 instead of using the
          desktop menu item and put "fvwm" in your $HOME/.xinitrc and
          $HOME/.xsession files for use by startx/xdm.  You can also build
          and reinstall /usr/src/release/sysinstall from 3.3-STABLE sources
          to fix the X Desktop menu item in question.
     
     The lo0 (loop-back) device is not configured on startup, causing
     utilities like mountd to fail.
     
     Fix: Assuming that you experience this problem at all, edit /etc/rc.conf
          and search for where the network_interfaces variable is set.  In
          its value, change the word "auto" to "lo0" since the auto keyword
          doesn't bring the loop-back device up properly, for reasons yet to
          be adequately determined.  Since your other interface(s) will already
          be set in the network_interfaces variable after initial installation,
          it's reasonable to simply s/auto/lo0/ in rc.conf and move on.
     
     The 3.3 ISO image (and 3.3 CDROM #1 from Walnut Creek CDROM)
          mysteriously fails to boot on an ATAPI CDROM device but works
          with SCSI CDROMs (on adaptors which support bootable CDs).
     
     Fix: Either install using boot floppies (see floppies/README.TXT)
          rather than booting from the CDROM or grab the updated ISO image
          from:
     
            ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/
     
          See also the CHECKSUM.MD5 file in that directory to verify whether
          you have the "old" or new image - some mirrors may be slow
          in picking up the uncompressed and gzipped versions of the ISO 9660
          installation image.  As always, Walnut Creek CDROM will also provide
    -     replacement CDs (once they become available) on request to purchasers 
    +     replacement CDs (once they become available) on request to purchasers
          of the 3.3-RELEASE product.
     
          This problem was caused by a bug in mkisofs which we're still
          chasing but have, for now, simply worked-around.
     
     Ppp(8) does not properly detect carrier in direct mode.
     
     Fix: Download and install the latest version of ppp(8) from:
     
            http://www.FreeBSD.org/~brian/ (US)
            http://www.Awfulhak.org/~brian/ (UK)
     
          or upgrade your system to -stable.
     

    Release Home &footer; diff --git a/es/releases/3.3R/notes.sgml b/es/releases/3.3R/notes.sgml index 60588e289a..3ee472149f 100644 --- a/es/releases/3.3R/notes.sgml +++ b/es/releases/3.3R/notes.sgml @@ -1,689 +1,690 @@ - - + + %navincludes; %includes; ]> &header;
     
                                      RELEASE NOTES
                                   FreeBSD 3.3-RELEASE
     
     Welcome to 3.3-RELEASE, a full follow-on to 3.2-RELEASE released
     May 1999.  In the months since 3.2 was released, many bug fixes and
     general enhancements have been made to the system.  Please see relevant
     details below.
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a WEB based interface can also see
     this page).
     
     For information about FreeBSD and the layout of the 3.3-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     Table of contents:
     ------------------
     1. What's new since 3.2-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 ATM
        2.4 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.3 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     6. Acknowledgements
     
     
     1. What's new since 3.2-RELEASE
     ---------------------------------
     
     1.1. KERNEL CHANGES
     -------------------
     The Berkeley Packet Filter (bpf) is enabled by default.  This is to allow
     DHCP supported installs.
     
     Linux mode has undergone significant bug fixes and improvements.
     
     The i386 bootstrap has been enhanced for some problematic systems.
     
     Driver support has been added for IEEE 802.11 PCMCIA wireless network
     adapters based on the Lucent Hermes chipset, including the Lucent
     WaveLAN/IEEE 802.11 and the Cabletron RoamAbout.  Both 2Mbps and
     6Mbps Turbo adapters are supported. [MERGED]
     
     Driver support has been added for PCI fast Ethernet cards based
     on the ADMtek Inc. AL981 Comet chipset.
     
     Driver support has been added for PCI fast Ethernet cards based
     on the LC82C115 'PNIC II' chipset.
     
     Driver support has been added for SysKonnect SK-984x PCI gigabit
     Ethernet adapters.
     
     Driver support has been added for Adaptec Duralink PCI Ethernet adapters
     based on the Adaptec AIC-6915 fast Ethernet controller.
     
     Driver support for M-systems DiskOnChip products integrated.
     
     Driver support has been added for the 3Com 3c905C-TX.
     
     Driver support has been added for the 3Com 3x574-TX 16-bit FastEtherlink
     PC-card support.
     
     Driver support has been added for the Compaq Smart Raid family of
     RAID controllers.
     
     Driver support for a number of Realtek and Avance Asound audio cards
     has been added.
     
     USB support has been improved.
     
     Major updates to the Vinum volume manager have been incorporated.
     [Though the new RAID-5 features should still be considered
     experimental since they are, well, new].
     
     A number of NFS problems have been fixed.
     
     APM support has been improved.  A kernel panic problem with an
     older APM BIOSes has been fixed.  Also, the suspend/standby
     transition is more robust.
     
     User- and group-based IPFW firewalling has been added.
     
     Support for probabilistic rule matching has been added to IPFW.
     
     IPFW logging is now dynamic. IPFW logging counts can be reset, and any
     given rule can be given an arbitrary logging limit.
     
     
     1.2. SECURITY FIXES
     -------------------
     A problem with file systems flags has been corrected.
     
     A problem with profil(2) remaining inactive after an exec call.
     
     A remotely exploitable root hole in amd (the automount daemon) has been
     fixed.
     
     The wu-ftpd port has been updated with the latest patches to prevent
     possible remote root exploits.
     
     The proftpd port has been updated with the latest patches to prevent
     possible remote root exploits.
     
     The samba port has been updated with the latest patches to prevent
     possible remote root exploits.
     
     The inn port has been updated to a new version that corrects some buffer
     overflows.
     
     Since FreeBSD 3.0 RELEASE, many minor problems with the network stack
     have been corrected which could have been exploited for denial of
     service attacks.
     
     
     1.3. USERLAND CHANGES
     ---------------------
     The support environment for Linux mode has finally been updated. The
     linux_lib and linux_devel ports are replaced by resp. linux_base and
     linux_devtools. These new ports are based on Red Hat 5.2 packages
     and include support for both glibc2 and libc5 based applications.
     
     Sysinstall now contains DHCP client support.
     
     TCP Wrapper support in inetd(8) is now controlled with command-line
     options and data-gram (UDP) services may be wrapped in addition to previously
     wrapped service types. Please see the manpage for details, since inetd
     run without command-line options will do no wrapping.
     
     ISC's DHCP client has been upgraded to version 2.0.
     
     Bison, the GNU parser generator, has been upgraded to version 1.28.
     
     The Advanced Power Management monitor daemon, apmd(8), has been added.
     This allows the user to select the APM events to be handled from
     userland and specify the commands for a given event.  This allows the
     APM behavior to be configured in a flexable manner.  Please see the
     manpage for details.
     
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.  The DPT SmartRAID/CACHE V
     is not yet supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
             Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     
     QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters.
     QLogic 2100 Fibre Channel Adapters (private loop only).
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
       Tekram DC390 and DC390T controllers (maybe other cards based on the
       AMD 53c974 as well).
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
       Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
       Adaptec 152x series ISA SCSI controllers
       Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
       and SoundBlaster SCSI cards.
     
       [ Note:  There is work-in-progress to port the AIC-6260/6360 and
         UltraStor drivers to the new CAM SCSI framework, but no estimates on
         when or if they will be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       Floppy tape interface (Colorado/Mountain/Insight)
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     2.2. Ethernet cards
     -------------------
     
     Adaptec Duralink PCI fast Ethernet adapters based on the Adaptec
     AIC-6915 fast Ethernet controller chip, including the following:
       ANA-62011 64-bit single port 10/100-BaseTX adapter
       ANA-62022 64-bit dual port 10/100-BaseTX adapter
       ANA-62044 64-bit quad port 10/100-BaseTX adapter
       ANA-69011 32-bit single port 10/100-BaseTX adapter
       ANA-62020 64-bit single port 100-BaseFX adapter
     
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI gigabit Ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       Alteon AceNIC (Tigon 1 and 2)
       3Com 3c985-SX (Tigon 1 and 2)
       Netgear GA620 (Tigon 2)
       Silicon Graphics Gigabit Ethernet
       DEC/Compaq EtherWORKS 1000
       NEC Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 fast Ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
       Kingston KNE110TX
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 fast Ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Macronix/Lite-On PNIC II LC82C115 fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX Version 2
     
     Winbond W89C840F fast Ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast Ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE530TX
     
     SysKonnect SK-984x PCI gigabit Ethernet cards including the following:
       SK-9841 1000baseLX single mode fiber, single port
       SK-9842 1000baseSX multi-mode fiber, single port
       SK-9843 1000baseLX single mode fiber, dual port
       SK-9844 1000baseSX multi-mode fiber, dual port
    -  
    +
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100-BaseTX
       Racore 8148 10-BaseT/100-BaseTX/100-BaseFX multi-personality
     
     ADMtek Inc. AL981-based PCI fast Ethernet NICs
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 Ethernet interface.
     
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B/905C PCI
     and EISA (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980/3c980B Fast Etherlink XL server adapter
     
     3Com 3cSOHO100-TX OfficeConnect adapter
     
     Toshiba Ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     PCMCIA Etherjet cards from IBM and National Semiconductor are also
     supported.
     
     Note that NO token ring cards are supported at this time as we're
     still waiting for someone to donate a driver for one of them.  Any
     takers?
     
     2.3 ATM
     -------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signaling Protocols
             - The ATM Forum UNI 3.1 signaling protocol
             - The ATM Forum UNI 3.0 signaling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signaling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multi-protocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     2.4. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multi-port serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 / Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed
     (2Mbps) and turbo speed (6Mbps) wireless network adapters and work-a-likes
     (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the
     ISA versions of these adapters are actually PCMCIA cards combined with
     an ISA to PCMCIA bridge card, so both kinds of devices work with
     the same driver.
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 3.3-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite F
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the
     following issues may affect you, depending of course on your chosen
     method of upgrading.  There are two popular ways of upgrading
     FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     In the case of using sources, there are simply two targets you need to
     be aware of: The standard ``upgrade'' target, which will upgrade a 2.x
     or 3.0 system to 3.3 and the ``world'' target, which will take an
     already upgraded system and keep it in sync with whatever changes have
     happened since the initial upgrade.
     
     In the case of using the binary upgrade option, the system will go
     straight to 3.3/ELF but also populate the /<basepath>/lib/aout
     directories for backwards compatibility with older binaries.
     
     In either case, going to ELF will mean that you'll have somewhat
     smaller binaries and access to a lot more compiler goodies which have
     been already been ported to other ELF environments (our older and
     somewhat crufty a.out format being largely unsupported by most other
     software projects).  Those who wish to retain access to the older
     a.out dynamic executables should be sure and install the compat22
     distribution. Notice that the a.out libraries won't be accessible
     until the system is rebooted, which may cause trouble with certain
     a.out packages.
     
     Also, do not use install disks or sysinstall from previous versions,
     as version 3.1 introduced a new bootstrapping procedure, requiring
     new boot blocks to be installed (because of elf kernels), and version
     3.2 has further modifications to the bootstrapping procedure.
     
     [ other important upgrading notes should go here]
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgments
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     
     

    Release Home &footer; diff --git a/es/releases/3.4R/announce.sgml b/es/releases/3.4R/announce.sgml index d46aecb9e8..5e060a66e7 100644 --- a/es/releases/3.4R/announce.sgml +++ b/es/releases/3.4R/announce.sgml @@ -1,121 +1,122 @@ - - + + %navincludes; %includes; ]> &header;

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

    - +

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

    FreeBSD 3.4-RELEASE is available at ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from The FreeBSD Mall, from where it will be shipping soon on a 4 CD set containing installation bits for x86 architecture, as well as a lot of other material of general interest to programmers and end-users alike (3.4-RELEASE for the Alpha architecture is available from the FTP site and will also be available on CDROM several weeks after the x86 product is released).

    - +

    NOTE: All of the profits from the sales of this CD set go to support the FreeBSD Project! We are also continuing our new tradition (started with 3.3-RELEASE) of making disc #1 from Walnut Creek CDROM's official distribution available via anonymous FTP. This is the most important CD of their 4 set, one which will allow users to install the base system and all of its most important add-ons from a single ISO 9660 image. We are doing this because the ISO image is rapidly becoming the preferred format for distributing operating system releases and we're certainly not going to go out of our way to make FreeBSD harder to "test drive" if providing the standard NFS/FTP network installation methods is no longer enough. This is a fully-bootable ISO 9660 (with RockRidge extentions) image and can be written as a raw ISO image by most CD creator software.

    We can't promise that all the mirror sites will carry the rather large installation (660MB) image, but it will at least be available from:

    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.4-install.iso

    - +

    along with the more traditional 3.4-RELEASE bits. If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from Walnut Creek CDROM.

    - +

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD/
    - +

    Or via the WEB pages at:

    http://www.FreeBSDMall.com/ and
    http://www.cdrom.com
    - +

    And directly from Walnut Creek CDROM:

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

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

    - +

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

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

    South Africa

    ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    - +

    Thanks!

    - Jordan

    Release Home &footer; diff --git a/es/releases/3.4R/errata.sgml b/es/releases/3.4R/errata.sgml index 82b7dfc3a0..8f6a6cf9eb 100644 --- a/es/releases/3.4R/errata.sgml +++ b/es/releases/3.4R/errata.sgml @@ -1,86 +1,87 @@ - - + + %navincludes; %includes; ]> - + &header;
     If you read no other documentation before installing this
     version of FreeBSD, you should at least by all means *READ
     THE ERRATA* for this release so that you don't stumble over
     problems which have already been found and fixed.  This ERRATA.TXT
     file is obviously already out of date by definition, but other
     copies are kept updated on the net and should be consulted as
     the "current errata" for your release.  These other copies of
    -the errata are located at: 
    +the errata are located at:
     
       1. http://www.freebsd.org/releases/
     
    -  2. ftp://ftp.freebsd.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT   
    -     (and any sites which keep up-to-date mirrors of this location).          
    +  2. ftp://ftp.freebsd.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT
    +     (and any sites which keep up-to-date mirrors of this location).
     
     Any changes to this file are also automatically emailed to:
     
             freebsd-stable@freebsd.org
     
     For all CERT security advisories, see:
     
             ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest security incident information.
     
     ---- Security Advisories:
     
     Current active security advisories for 3.4:
     
     ---- System Update Information:
     
     As shipped, the "Custom" installation option in 3.4 is broken.
     
     Fix: Both the "Novice" and "Express" install paths still work and
          can be used just as effectively (if not succinctly).  Alternately,
          you can invoke the custom installation from the "Index" menu
    -     (Installation, Custom) or you can download a fixed mfsroot.flp 
    -     floppy image (or boot.flp if you need 2.88MB boot media) from the 
    -     floppies/updates/ directory under: 
    +     (Installation, Custom) or you can download a fixed mfsroot.flp
    +     floppy image (or boot.flp if you need 2.88MB boot media) from the
    +     floppies/updates/ directory under:
            ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/3.4-RELEASE/
          The 3.4 ISO installation image is also updated to contain a fix
          for this errata item.
     
     802.1Q VLAN support compilation error: kernel configurations
     containing "pseudo-device vlan #" fail to compile
     
     Fix: Update your copy of sys/net/if_vlan.c to the 3-stable branch
          version, where it is fixed, or apply the following patch to the
          sys/net/if_vlan.c distributed with 3.4-RELEASE:
     
     RCS file: /home/ncvs/src/sys/net/if_vlan.c,v
     retrieving revision 1.4.2.2
     retrieving revision 1.4.2.3
     diff -C2 -r1.4.2.2 -r1.4.2.3
     *** if_vlan.c	1999/12/13 02:02:23	1.4.2.2
     --- if_vlan.c	1999/12/25 03:28:51	1.4.2.3
     ***************
     *** 515,519 ****
       			ifv->ifv_p = 0;
       			if_down(ifp);
     ! 			ifv->if_flags &= ~(IFF_UP|IFF_RUNNING);
       			break;
       		}
     --- 515,519 ----
       			ifv->ifv_p = 0;
       			if_down(ifp);
     ! 			ifp->if_flags &= ~(IFF_UP|IFF_RUNNING);
       			break;
       		}
     
     

    Release Home &footer; diff --git a/es/releases/3.4R/notes.sgml b/es/releases/3.4R/notes.sgml index 3d05ddd2f4..d95dfd0f8e 100644 --- a/es/releases/3.4R/notes.sgml +++ b/es/releases/3.4R/notes.sgml @@ -1,635 +1,636 @@ - - + + %navincludes; %includes; ]> &header;
                       RELEASE NOTES - FREEBSD 3.4-RELEASE
     
     Welcome to 3.4-RELEASE, a full follow-on to 3.3-RELEASE which was
     shipped in October 1999.  In the months since 3.3 was released, many
     bug fixes and general enhancements have been made to the system.  Please
     see relevant details below.
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a WEB based interface can also see
     http://www.freebsd.org/send-pr.html).
     
     For information about FreeBSD and the layout of the 3.4-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     Table of contents:
     ------------------
     1. What's new since 3.3-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 ATM
        2.4 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     
     6. Acknowledgments
     
     
     1. What's new since 3.3-RELEASE
     ---------------------------------
     
     1.1. KERNEL CHANGES
     -------------------
     
     Support for Adaptec 152x/151x/AIC-6360 SCSI controllers is back.
     
     netgraph(4) has been added.  Netgraph provides a uniform and modular system
     for the implementation of kernel objects which perform various networking
     functions.  To enable it, ``options NETGRAPH'' must be added to the kernel.
     
     i4b(4) has been upgraded to version 00.83.00, providing increased robustness
     and stability, and supporting many new cards (Asuscom ISDNlink 128K,
     AVM Fritz!Card PCI, AVM Fritz!Card PnP, ELSA PCC-16, ITK ix1 micro V.3,
     Siemens I-Surf 2.0).
     
     RAID-5 support has been added to vinum(8).
     
     Driver support for the Intel PIIX4 and AcerLabs M15x3 power management
     controllers has been added.
     
     
     1.2. SECURITY CHANGES
     ---------------------
     
     Support has been added for blocking incoming ICMP redirects, outgoing RST
     frames and incoming SYN|FIN frames in order to lessen or nullify the
     impact of certain kinds of DoS attacks.
     
     Support has been added for forwarding IP datagrams without inspecting or
     decreasing the TTL in order to make gateways and firewalls less visible
     and therefore less exposed to attacks.
     
     New networking security features include the ability to drop TCP packets with
     SYN+FIN (NOTE: this breaks rfc1644 extensions (T/TCP)), restrict emission of
     RST, ignore incoming ICMP REDIRECT messages, and also set to log incoming
     ICMP REDIRECT messages.  See rc.conf(5) for details on how to utilize these
     new features.
     
     
     1.3. USERLAND CHANGES
     ---------------------
     
     Inetd has gained built-in support for ident and has a workaround
     for accidently blocking while accepting.
     
     ppp(8) now supports PPPoE (PPP over Ethernet) compliments of the pppoe
     netgraph node.  It also supports PPP over ISDN, including standard ISDN
     link bonding.  ppp(8) now uses the -nat command line argument and the ``nat''
     command to control network address translation.  The old [-]alias command
     still works, but produces a warning and will soon be removed.  Additionally,
     ppp(8) now loads the tun module as required, allows a tun unit specification
     on the command line, supports a -foreground command line option, allows
     fast-queue configuration, provides a functional ``set autoload'' command
     (for on-demand multi-link ppp), allows GRE packet filtering and has had
     many bugs fixed.
     
     There's a new pppoed daemon for servicing PPP over Ethernet requests.
     Refer to rc.conf(5) and pppoed(8) for details.
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.  The DPT SmartRAID/CACHE V
     is not yet supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
             Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     
     QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters.
     QLogic 2100 Fibre Channel Adapters (private loop only).
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
    -  [ Note:  There is work-in-progress to port the UltraStor driver to 
    -    the new CAM SCSI framework, but no estimates on when or if it will 
    +  [ Note:  There is work-in-progress to port the UltraStor driver to
    +    the new CAM SCSI framework, but no estimates on when or if it will
         be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       Floppy tape interface (Colorado/Mountain/Insight)
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     2.2. Ethernet cards
     -------------------
     
     Adaptec Duralink PCI fast Ethernet adapters based on the Adaptec
     AIC-6915 fast Ethernet controller chip, including the following:
       ANA-62011 64-bit single port 10/100-BaseTX adapter
       ANA-62022 64-bit dual port 10/100-BaseTX adapter
       ANA-62044 64-bit quad port 10/100-BaseTX adapter
       ANA-69011 32-bit single port 10/100-BaseTX adapter
       ANA-62020 64-bit single port 100-BaseFX adapter
     
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI gigabit Ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       Alteon AceNIC (Tigon 1 and 2)
       3Com 3c985-SX (Tigon 1 and 2)
       Netgear GA620 (Tigon 2)
       Silicon Graphics Gigabit Ethernet
       DEC/Compaq EtherWORKS 1000
       NEC Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 fast Ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
       Kingston KNE110TX
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 fast Ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Macronix/Lite-On PNIC II LC82C115 fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX Version 2
     
     Winbond W89C840F fast Ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast Ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE530TX
     
     Silicon Integrated Systems SiS 900 and SiS 7016 PCI fast ethernet NICs.
     
     Sundance Technologies ST201 PCI fast ethernet NICs including
     the following:
       D-Link DFE-550TX
     
     SysKonnect SK-984x PCI gigabit Ethernet cards including the following:
       SK-9841 1000baseLX single mode fiber, single port
       SK-9842 1000baseSX multi-mode fiber, single port
       SK-9843 1000baseLX single mode fiber, dual port
       SK-9844 1000baseSX multi-mode fiber, dual port
    -  
    +
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100-BaseTX
       Racore 8148 10-BaseT/100-BaseTX/100-BaseFX multi-personality
     
     ADMtek Inc. AL981-based PCI fast Ethernet NICs
     ADMtek Inc. AN985-based PCI fast Ethernet NICs
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 Ethernet interface.
     
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B/905C PCI
     and EISA (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980/3c980B Fast Etherlink XL server adapter
     
     3Com 3cSOHO100-TX OfficeConnect adapter
     
     Toshiba Ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     PCMCIA Etherjet cards from IBM and National Semiconductor are also
     supported.
     
     
     2.3 ATM
     -------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signaling Protocols
             - The ATM Forum UNI 3.1 signaling protocol
             - The ATM Forum UNI 3.0 signaling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signaling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multi-protocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     2.4. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multi-port serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 / Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed
     (2Mbps) and turbo speed (6Mbps) wireless network adapters and work-a-likes
     (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the
     ISA versions of these adapters are actually PCMCIA cards combined with
     an ISA to PCMCIA bridge card, so both kinds of devices work with
     the same driver.
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 3.4-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite F
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the
     following issues may affect you, depending of course on your chosen
     method of upgrading.  There are two popular ways of upgrading
     FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     In the case of using sources, there are simply two targets you need to
     be aware of: The standard ``upgrade'' target, which will upgrade a 2.x
     or 3.0 system to 3.4 and the ``world'' target, which will take an
     already upgraded system and keep it in sync with whatever changes have
     happened since the initial upgrade.
     
     In the case of using the binary upgrade option, the system will go
     straight to 3.4/ELF but also populate the /<basepath>/lib/aout
     directories for backwards compatibility with older binaries.
     
     In either case, going to ELF will mean that you'll have somewhat
     smaller binaries and access to a lot more compiler goodies which have
     been already been ported to other ELF environments (our older and
     somewhat crufty a.out format being largely unsupported by most other
     software projects).  Those who wish to retain access to the older
     a.out dynamic executables should be sure and install the compat22
     distribution. Notice that the a.out libraries won't be accessible
     until the system is rebooted, which may cause trouble with certain
     a.out packages.
     
     Also, do not use install disks or sysinstall from previous versions,
     as version 3.1 introduced a new bootstrapping procedure, requiring
     new boot blocks to be installed (because of elf kernels), and version
     3.2 has further modifications to the bootstrapping procedure.
     
     [ other important upgrading notes should go here]
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgments
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/3.5R/announce.sgml b/es/releases/3.5R/announce.sgml index 5b4138a4f3..b455339713 100644 --- a/es/releases/3.5R/announce.sgml +++ b/es/releases/3.5R/announce.sgml @@ -1,104 +1,105 @@ - - + + %navincludes; %includes; ]> &header;

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

    - +

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

    FreeBSD 3.5-RELEASE is available at ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from The FreeBSD Mall, from where it will be shipping soon on a 4 CD set containing installation bits for x86 architecture, as well as a lot of other material of general interest to programmers and end-users alike

    - +

    We can't promise that all the mirror sites will carry the rather large installation (660MB) image, but it will at least be available from:

    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/3.5-install.iso

    - +

    along with the more traditional 3.5-RELEASE bits. If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi.

    - +

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD/
    - +

    Or via the WEB pages at:

    http://www.FreeBSDMall.com/ and
    http://www.freebsd.org
    - +

    And directly from BSDi:

    BSDi
    4041 Pike Lane, #F
    Concord CA, 94520 USA
    Phone: +1 925 674-0783
    Fax: +1 925 674-0821
    Email: info@cdrom.com
    WWW: http://www.cdrom.com/
    - +

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Elbonia, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

    - +

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

    The latest versions of export-restricted code for FreeBSD (2.0C or later) (eBones and secure) are also being made available at the following locations. Now that FreeBSD has export permission for crypto from the United States government, you can get it from these locations or from ftp.freebsd.org.

    South Africa

    ftp://ftp.internat.FreeBSD.ORG/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.ORG/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.ORG/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    - +

    Thanks!

    - Jordan

    Release Home &footer; diff --git a/es/releases/3.5R/errata.sgml b/es/releases/3.5R/errata.sgml index 5d95b89a38..d2c6b46963 100644 --- a/es/releases/3.5R/errata.sgml +++ b/es/releases/3.5R/errata.sgml @@ -1,47 +1,48 @@ - - + + %navincludes; %includes; ]> - + &header;
     If you read no other documentation before installing this
     version of FreeBSD, you should at least by all means *READ
     THE ERRATA* for this release so that you don't stumble over
     problems which have already been found and fixed.  This ERRATA.TXT
     file is obviously already out of date by definition, but other
     copies are kept updated on the net and should be consulted as
     the "current errata" for your release.  These other copies of
    -the errata are located at: 
    +the errata are located at:
     
       1. http://www.freebsd.org/releases/
     
    -  2. ftp://ftp.freebsd.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT   
    -     (and any sites which keep up-to-date mirrors of this location).          
    +  2. ftp://ftp.freebsd.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT
    +     (and any sites which keep up-to-date mirrors of this location).
     
     Any changes to this file are also automatically emailed to:
     
             freebsd-stable@freebsd.org
     
     For all CERT security advisories, see:
     
             ftp://ftp.freebsd.org/pub/FreeBSD/CERT/
     
     For the latest security incident information.
     
     ---- Security Advisories:
     
     Current active security advisories for 3.5:
     
     ---- System Update Information:
     
     

    Release Home &footer; diff --git a/es/releases/3.5R/notes.sgml b/es/releases/3.5R/notes.sgml index 7c120d5a2b..8d8a7c1b67 100644 --- a/es/releases/3.5R/notes.sgml +++ b/es/releases/3.5R/notes.sgml @@ -1,653 +1,654 @@ - - + + %navincludes; %includes; ]> &header;
                       RELEASE NOTES - FREEBSD 3.5-RELEASE
     
     Welcome to 3.5-RELEASE, a full follow-on to 3.4-RELEASE which was
     shipped in December 1999.  In the months since 3.4 was released, many
     bug fixes and general enhancements have been made to the system.  Please
     see relevant details below.
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a WEB based interface can also see
     http://www.freebsd.org/send-pr.html).
     
     For information about FreeBSD and the layout of the 3.5-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     Table of contents:
     ------------------
     1. What's new since 3.4-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 ATM
        2.4 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     
     6. Acknowledgments
     
     
     1. What's new since 3.4-RELEASE
     ---------------------------------
     
     1.1. KERNEL CHANGES
     -------------------
     
     The loader was substantially updated from -current
     
     Various bugs in the CAM driver fixed.
     
     oltr [Olicom NIC] driver updated.
     
     bktr(4) [Brooktree frame-grabber] driver updated.
     
     isp(4) [Compaq Qlogic] driver updated.
     
     sym(4) [NCR/Symbios SCSI controller] driver updated.
     
     A number of bugs in syscons(4) fixed.
     
     A number of bugs in vinum(4) fixed.
     
     Better support for LBA in wd(4) driver.
     
     Audio mixer(8) support substantially updated.
     
     Support for Microsoft Sound Source (MSS) audio devices.
     
     Support for more Linux system calls in the Linux compatability code.
     
     netgraph(4) updated: new node types and documentation added.
     
     Various bugs in msdosfs code fixed.
     
     
     1.2. SECURITY CHANGES
     ---------------------
     
     Many small but meaningful changes, too many to list.  See CVS repository
     for more details.  Suffice it to say from a user perspective that
     "various things were tightened up."
     
     
     1.3. USERLAND CHANGES
     ---------------------
     
     vinum(8) substantially updated.
     
     chmod(1) has gained a -v flag.  See man page for details.
     
     df(1) gains new unit types.  See man page for details.
     
     Various bugs in date(1), ed(1), ln(1), sh(1), camcontrol(8), vinum(8)
     and quite a number of other user commands fixed (see CVS for details :).
     
     groff(1), grep(1) texinfo(1) utilities updated.
     
     Quite a few enhancements to /etc from -current merged.
     
     Many doc bugs fixed in man pages.
     
     Thread locking functions added to dynamic linker (see dllockinit(3)).
     
     pthread_cancel(3) function added.
     
     ppp(8) has undergone some changes and bug fixes.  One change in particular
     may disturb existing configurations.  The # character is now treated
     as a comment start, irrespective of whether it's the first non-blank
     character on the line.  Some ISPs allocate authnames with embedded #
     characters.  These must now be escaped or quoted.
     
     picobsd support (/usr/src/release/picobsd) substantially updated.
     
     HTTP installation option added to system installer (sysinstall(8)).
     
     XFree86 updated from 3.3.5 to 3.3.6 (XFree86 4.0 not quite ready for
     prime-time yet).
     
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus
     based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.  The DPT SmartRAID/CACHE V
     is not yet supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
             Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     
     QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters.
     QLogic 2100 Fibre Channel Adapters (private loop only).
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (wcd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
    -  [ Note:  There is work-in-progress to port the UltraStor driver to 
    -    the new CAM SCSI framework, but no estimates on when or if it will 
    +  [ Note:  There is work-in-progress to port the UltraStor driver to
    +    the new CAM SCSI framework, but no estimates on when or if it will
         be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       Floppy tape interface (Colorado/Mountain/Insight)
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     2.2. Ethernet cards
     -------------------
     
     Adaptec Duralink PCI fast Ethernet adapters based on the Adaptec
     AIC-6915 fast Ethernet controller chip, including the following:
       ANA-62011 64-bit single port 10/100-BaseTX adapter
       ANA-62022 64-bit dual port 10/100-BaseTX adapter
       ANA-62044 64-bit quad port 10/100-BaseTX adapter
       ANA-69011 32-bit single port 10/100-BaseTX adapter
       ANA-62020 64-bit single port 100-BaseFX adapter
     
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI gigabit Ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       Alteon AceNIC (Tigon 1 and 2)
       3Com 3c985-SX (Tigon 1 and 2)
       Netgear GA620 (Tigon 2)
       Silicon Graphics Gigabit Ethernet
       DEC/Compaq EtherWORKS 1000
       NEC Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 fast Ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
       Kingston KNE110TX
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 fast Ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Macronix/Lite-On PNIC II LC82C115 fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX Version 2
     
     Winbond W89C840F fast Ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast Ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE530TX
     
     Silicon Integrated Systems SiS 900 and SiS 7016 PCI fast ethernet NICs.
     
     Sundance Technologies ST201 PCI fast ethernet NICs including
     the following:
       D-Link DFE-550TX
     
     SysKonnect SK-984x PCI gigabit Ethernet cards including the following:
       SK-9841 1000baseLX single mode fiber, single port
       SK-9842 1000baseSX multi-mode fiber, single port
       SK-9843 1000baseLX single mode fiber, dual port
       SK-9844 1000baseSX multi-mode fiber, dual port
    -  
    +
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100-BaseTX
       Racore 8148 10-BaseT/100-BaseTX/100-BaseFX multi-personality
     
     ADMtek Inc. AL981-based PCI fast Ethernet NICs
     ADMtek Inc. AN985-based PCI fast Ethernet NICs
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 Ethernet interface.
     
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B/905C PCI
     and EISA (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980/3c980B Fast Etherlink XL server adapter
     
     3Com 3cSOHO100-TX OfficeConnect adapter
     
     Toshiba Ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     PCMCIA Etherjet cards from IBM and National Semiconductor are also
     supported.
     
     
     2.3 ATM
     -------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signaling Protocols
             - The ATM Forum UNI 3.1 signaling protocol
             - The ATM Forum UNI 3.0 signaling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signaling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multi-protocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     2.4. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multi-port serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 / Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed
     (2Mbps) and turbo speed (6Mbps) wireless network adapters and work-a-likes
     (NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the
     ISA versions of these adapters are actually PCMCIA cards combined with
     an ISA to PCMCIA bridge card, so both kinds of devices work with
     the same driver.
     
     FreeBSD currently does NOT support IBM's microchannel (MCA) bus.
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 3.5-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite F
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 2.2.x or 2.1.x (in some lesser number of cases) and some of the
     following issues may affect you, depending of course on your chosen
     method of upgrading.  There are two popular ways of upgrading
     FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     In the case of using sources, there are simply two targets you need to
     be aware of: The standard ``upgrade'' target, which will upgrade a 2.x
     or 3.0 system to 3.5 and the ``world'' target, which will take an
     already upgraded system and keep it in sync with whatever changes have
     happened since the initial upgrade.
     
     In the case of using the binary upgrade option, the system will go
     straight to 3.5/ELF but also populate the /<basepath>/lib/aout
     directories for backwards compatibility with older binaries.
     
     In either case, going to ELF will mean that you'll have somewhat
     smaller binaries and access to a lot more compiler goodies which have
     been already been ported to other ELF environments (our older and
     somewhat crufty a.out format being largely unsupported by most other
     software projects).  Those who wish to retain access to the older
     a.out dynamic executables should be sure and install the compat22
     distribution. Notice that the a.out libraries won't be accessible
     until the system is rebooted, which may cause trouble with certain
     a.out packages.
     
     Also, do not use install disks or sysinstall from previous versions,
     as version 3.1 introduced a new bootstrapping procedure, requiring
     new boot blocks to be installed (because of elf kernels), and version
     3.2 has further modifications to the bootstrapping procedure.
     
     [ other important upgrading notes should go here]
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgments
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/4.0R/announce.sgml b/es/releases/4.0R/announce.sgml index 3e168d9cfc..87eec87a1d 100644 --- a/es/releases/4.0R/announce.sgml +++ b/es/releases/4.0R/announce.sgml @@ -1,115 +1,116 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Tue, 14 Mar 2000 22:29:43 -0800 (PST)
    From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
    To: announce@FreeBSD.org
    Subject: 4.0-RELEASE is now available

    Well, it's a bit late and hopefully all the better for it, but here it is. It gives me great pleasure to announce the release of FreeBSD 4.0-RELEASE. This is our first release along the 4.x-stable (RELENG_4) branch and contains a number of significant advancements over FreeBSD 3.4. Please see the release notes for further information as the list of new features is too long to list here.

    FreeBSD 4.0-RELEASE is available from ftp.FreeBSD.org and various FTP mirror sites throughout the world. It can also be ordered on CD from The FreeBSD Mall, from where it will be shipping soon on a 4 CD set. There will also be two such sets available for 4.0, one containing installation bits for the x86 architecture (as well a lot of other material of general interest to programmers and end-users alike) and another for DEC Alpha architecture machines.

    As usual, disc #1 from Walnut Creek CDROM's official distribution (for both architectures) will also be available via anonymous FTP as soon as it's been compiled in its final form. Please monitor the master FTP site for details. We also can't promise that all the mirror sites will carry this rather large (660MB) installation image, but it will at least be available (once ready) from:

    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.0-install.iso
    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.0-install.iso

    These files allow one to install the base system and all of its most important add-ons from a single bootable image, one which can be written as a raw ISO 9660 image by most CD creator software.

    Even though we make our installation CDs freely available, we also hope that you'll continue to support the FreeBSD project by purchasing one of its official CD releases from the FreeBSD mall. A portion of each sale goes to support FreeBSD's development and general infrastructure and is thus highly appreciated.

    The official FTP distribution site for FreeBSD is:

    ftp://ftp.FreeBSD.org/pub/FreeBSD

    Or via the WEB pages at:

    http://www.freebsdmall.com/
    http://www.wccdrom.com/

    - +

    And directly from Walnut Creek CDROM:

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

    Additionally, FreeBSD is available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

    - +

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

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

    South Africa

    ftp://ftp.internat.FreeBSD.org/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.org/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.org/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    Thanks!

    - Jordan

    Release Home &footer; diff --git a/es/releases/4.0R/errata.sgml b/es/releases/4.0R/errata.sgml index ddb9dbd8ea..2caa51351f 100644 --- a/es/releases/4.0R/errata.sgml +++ b/es/releases/4.0R/errata.sgml @@ -1,90 +1,91 @@ - - + + %navincludes; %includes; ]> - + &header;
     If you read no other documentation before installing this
     version of FreeBSD, you should at least by all means *READ
     THE ERRATA* for this release so that you don't stumble over
     problems which have already been found and fixed.  This ERRATA.TXT
     file is obviously already out of date by definition, but other
     copies are kept updated on the net and should be consulted as
     the "current errata" for your release.  These other copies of
    -the errata are located at: 
    +the errata are located at:
     
       1. http://www.FreeBSD.org/releases/
     
    -  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT   
    -     (and any sites which keep up-to-date mirrors of this location).          
    +  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT
    +     (and any sites which keep up-to-date mirrors of this location).
     
     Any changes to this file are also automatically emailed to:
     
     	freebsd-current@FreeBSD.org
     
     For all FreeBSD security advisories, see:
     
     	http://www.FreeBSD.org/security/
     
     for the latest security incident information.
     
     ---- Security Advisories:
     
     Current active security advisories:	None
     
     ---- System Update Information:
     
     
     The tcpdump binary in the bin distribution is erroneously linked against
     the libcrypto.so library, which is only found in the separate crypto
     distribution.
     
     
     Therefore, if you only install the bin distribution without the crypto
     distribution, tcpdump will not work as installed.
     
     Fix: Download a new tcpdump binary from the following location:
     
     	http://people.FreeBSD.org/~kris/4.0R/i386/tcpdump (i386)
     	http://people.FreeBSD.org/~kris/4.0R/alpha/tcpdump (alpha)
     
     The MD5 checksum of this file is:
     
     	i386 version: MD5 (tcpdump) = 0b3d32b367e7312d546ccae8f1824391
     	alpha version: MD5 (tcpdump) = 2d113fa4c38c8a0299d558acb5c6ad57
     
     To verify the checksum of your downloaded copy, perform the following
     command:
     
     	/sbin/md5 /path/to/downloaded/tcpdump
     
     and compare with the above.
     
     
     
     o Tool source code not installed by install.sh (outside of sysinstall)
     
     
     If you are attempting to extract the full source code from
     the CDROM (outside of the sysinstall program), you will end up missing
     the tool source code.
     
     Fix: If you are running install.sh from /cdrom/src, you will need to also
          run:
     
            cat stool.?? | tar --unlink -xpzf - -C /usr/src
     
     to have the tool sources (/usr/src/tools hierarchy) installed. These are
     required to successfully build world.
     
     

    Release Home &footer; diff --git a/es/releases/4.0R/notes.sgml b/es/releases/4.0R/notes.sgml index 29081cf914..4b6551fa8e 100644 --- a/es/releases/4.0R/notes.sgml +++ b/es/releases/4.0R/notes.sgml @@ -1,878 +1,879 @@ - - + + %navincludes; %includes; ]> &header;
                                      RELEASE NOTES
                                FreeBSD Release 4.0-RELEASE
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a Web-based interface can also see
     http://www.FreeBSD.org/send-pr.html).
     
     For information about FreeBSD and the layout of the 4.0-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     For the latest of these 4.0-STABLE snapshots, you should always see:
     
             ftp://current.FreeBSD.org/pub/FreeBSD
     
     If you wish to get the latest post-3.X-RELEASE technology.
     
     Table of contents:
     ------------------
     1. What's new since the 3.1/4.0 branch
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 ATM
        2.4 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     6. Acknowledgements
     
     
     1. What's new since the 3.1/4.0 branch
     --------------------------------------
     All changes described here are unique to the 4.0 branch unless
     specifically marked as [MERGED] features.
     
     
     1.1. KERNEL CHANGES
     -------------------
     
     NFS has been immensely improved with bug fixes and performance tuning.
     
    -Support for more than 32 signals has been added. 
    +Support for more than 32 signals has been added.
     
     POSIX 1003.1 conformant SA_SIGINFO signal handlers are now supported.
     SIGFPE signal handlers (both SA_SIGINFO and traditional BSD handlers)
     now get meaningful error codes describing the kind of error. See
     sigaction(2).
     
     IA32 hardware debug registers are now supported.  See ptrace(2) and
     procfs(5).
     
     Jail(8) aware sysctl(8) variables have been added for Linux mode.
     
     A large number of bug fixes and performance improvements have been
     made to the VM system, including and most especially to mmap() and
    -related functions.  The MAP_NOSYNC option has been added to better support 
    +related functions.  The MAP_NOSYNC option has been added to better support
     the use of shared files as an IPC mechanism.  The VM system's swapper has
     been completely rewritten and performance has been greatly enhanced,
     especially when swapping over NFS.
     
     An emulator for SVR4 binaries has been added.
     
     Support has been added for direct access to NTFS filesystems.
     
     Support for the NWFS filesystem and NetWare client connections has
     been added.  A variety of NetWare related tools, such as ipxping
     and ncprint, have been added in ports/net/ncplib.
     
     A new ATA/ATAPI driver has been implemented. The aim of this new
     subsystem is to maximise performance on modern ATA/ATAPI based
     systems. The "ata" driver supports all major chipsets including
     those used on PCI card based controllers like the Promise and the
    -Abit/SIIG. There is support for busmaster DMA transfers upto and 
    +Abit/SIIG. There is support for busmaster DMA transfers upto and
     including the new ATA/66 mode. The 'ata' driver automatically
     setup the hardware for the maximum possible transfer mode to
     maximise system throughput. Supported devices are all ATA compliant
    -disks and ATAPI CDROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, LS120, ZIP 
    -and tape drives. The ata driver also support PCCARD ATA devices. 
    -The 'ata' driver also sports error handling and timeout code, to 
    +disks and ATAPI CDROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, LS120, ZIP
    +and tape drives. The ata driver also support PCCARD ATA devices.
    +The 'ata' driver also sports error handling and timeout code, to
     avoid the problems of "hung" ATA/ATAPI devices.
     
     A new utility 'burncd' has been written to facilitate easy control
     of ATAPI CD-R and CD-RW drives, and allows burning of CD-R/RW
     media in a wide selction of formats, including multisession mode.
     
     Driver support has been added for PCI gigabit ethernet adapters
     based on the Alteon Networks Tigon 1 and Tigon 2 chipsets, including
     the Alteon AceNIC, 3Com 3c985 and Netgear GA620. [MERGED]
     
     Driver support has been added for IEEE 802.11 PCMCIA wireless network
     adapters based on the Lucent Hermes chipset, including the Lucent
    -WaveLAN/IEEE 802.11, the Cabletron RoamAbout and Melco Aireconnect.  
    +WaveLAN/IEEE 802.11, the Cabletron RoamAbout and Melco Aireconnect.
     Both 2Mbps and 6Mbps Turbo adapters are supported. [MERGED]
     
     Driver support has been added for PCI fast ethernet cards based
     on the ADMtek Inc. AL981 Comet chipset. [MERGED]
     
     Driver support has been added for PCI fast ethernet cards based
     on the ADMtek Inc. AL985 Centaur chipset. [MERGED]
     
     Support has been added for the Rise mP6 processor. [MERGED]
     
     Driver support has been added for SysKonnect SK-984x PCI gigabit
     ethernet adapters. [MERGED]
     
     Driver support has been added for Adaptec Duralink PCI ethernet adapters
     based on the Adaptec AIC-6915 fast ethernet controller. [MERGED]
     
     Driver support has been added for PCI fast ethernet adapters based on
     the Sundance Technologies ST201 controller, including the D-Link DFE-550TX.
     [MERGED]
     
     Driver support has been added for the 3Com 3c905C-TX. [MERGED]
     
     Driver support has been added for SMC SMC9xxx-based Ethernet adapters.
     
     Several IPFW improvements including stateful inspection, user- and
     group-based firewalling, dynamic logging with arbitrary logging
     limits, probabilistic rule match. [MERGED]
     
     IPv6 IPFW has been imported from the KAME project.
     
     The "dummynet" traffic shaper now handles efficiently thousands
     of independent queues. [MERGED]
     
     Several fixes to bridging, which now supports clusters of interfaces
     with bridging being done independently within each cluster. [MERGED]
     
     The top-level syslog(3) category "security" has been added, and IPFW now
     uses syslog(3) to log all messages to /var/log/security.
     
     Driver support has been added for PCI fast ethernet adapters based on
     the Silicon Integrated Systems SiS 900 and SiS 7016 ethernet controllers.
     [MERGED]
     
     Driver support has been added for PCI fast ethernet adapters based on
     the Davicom DM9100 and DM9102 ethernet controllers, including the Jaton
     Corporation XpressNet.
     
     Support has been added for blocking incoming ICMP redirects, outgoing RST
     frames and incoming SYN|FIN frames in order to lessen or nullify the
     impact of certain kinds of DoS attacks. [MERGED]
     
     Support has been added for forwarding IP datagrams without inspecting or
     decreasing the TTL in order to make gateways and firewalls less visible
     and therefore less exposed to attacks. [MERGED]
     
     The old `sd' (SCSI Disk) backwards compatibility support has been removed.
     Any usage of "/dev/sd*" in ``/etc/fstab'' must be replaced by "/dev/da*".
     In addition, any useage of "/dev/*sd*" in scripts need to be changed.
     Even if you have old `sd' device entries in /dev, they will no longer work.
     
     The `al' `ax' `dm' `pn' and `mx' drivers have been removed and replaced
     with a single driver (`dc') in order to reduce code duplication. The
     new driver handles all chipsets supported by the older drivers, and it
     offers improved support for 10/100 cards based on the DEC/Intel 21143.
     
     Driver support has been added for the 3Com 3c450-TX HomeConnect
     PCI ethernet NIC. [MERGED]
     
     Driver support has been added for USB ethernet adapters based on
     the ADMtek AN986 Pegasus chip, including the LinkSys USB100TX,
     the Billionton USB100, the Melco Inc. LU-ATX, the D-Link 650TX
     and the SMC-2202USB.
     
     Driver support has been added for USB ethernet adapters based on
     the Kawasaki LSI KL5KUSB101B chip, including the LinkSys USB10T,
     the Peracom USB Ethernet Adapter, the 3Com 3c19250, the Entrega
     NET-USB-E45, the ADS Technologies USB-10BT, the ATen UC10T, the
     Netgear EA101, the D-Link DSB-650, and the SMC 2102USB and 2104USB.
     
     IPfilter version 3.3.8 has been integrated.
     
     Driver support has been added for USB ethernet adapters based on
     the CATC USB-EL1210A chip, including the CATC Netmate and Netmate II,
     and the Belkin F5U111.
     
     Driver support has been added for Aironet 4500/4800 802.11 wireless
     adapters. This includes PCMCIA, PCI and ISA models.
     
     IPv6 support has been imported from the KAME project. This includes the
     kernel IPv6 protocol stack (sys/netinet6), TCP IPv6 support, configurable
     IPv6 and IPv4 tunneling over IPv6 or IPv4, and IPv6 TCP to IPv4 TCP
     translation gateway support. Protocol-independent name resolution
     functions have been added to libc (getaddrinfo, getnameinfo, etc).
     
     Floating point exceptions for new processes (devide-by-zero,
     under/overflow, invalid range etc.) are now disabled by default. Use
     fpsetmask(3) to reenable those you need. Note that integer
     device-by-zero is not covered by the FPU and will still trap after
     this change. Also note that conversion of float/double to integer
     where the float variable is too big now doesn't trap as well (it can't
     be separated from other operations we want masked).
     
     
     1.2. SECURITY FIXES
     -------------------
     
     Numerous security enhancements and fixes have been applied during the
     course of development of FreeBSD 4.0. Most of these have also been
     backported to the 3.X-STABLE series.
     
     A new jail(2) system call and admin command (jail(8)) have been added for
     additional flexibility in creating secure process execution environments.
     
     OpenSSL v0.9.4 (a general-purpose cryptography and SSL2/3/TLSv1 toolkit)
     has been integrated with the base system. In the future this will be used
     to provide strong cryptography for FreeBSD utilities out-of-the-box.
     
     OpenSSH 1.2 has been integrated with the base system. OpenSSH is a free
     (BSD-licensed), full-featured implementation of the SSH v1 protocol, which
     is completely interoperable with other SSH v1 clients and servers, such as
     the /usr/ports/security/ssh port.  OpenSSH provides all of the features of
     this port - in fact it is based on an older release before the software
     became restrictively licensed.  FreeBSD 4.0 provides SSH client/server
     functionality out-of-the-box if you choose to install the 'DES'
     cryptography distribution in sysinstall.
     
     Telnet has a new encrypted authentication mechanism called SRA. SRA
     uses a Diffie-Hellmen exchange to establish a session key, then uses
     that to DES encrypt the username and password. As a side effect the
     session key is used to DES encrypt the session. SRA is vulnerable to
     man-in-the-middle attacks, the DH parameters are on the small side,
     and DES is showing its age, but the benefits are that it requires
     absolutely no administrative changes to the machine to work, and is
     at the very least a step up from plaintext. To use it, you need to
     either use "telnet -ax" or set up a .telnetrc to enable it by default.
     
     IPsec support has been imported from the KAME project. This includes IPsec
     tunnel mode to implement a Virtual Private Network via a security gateway,
     and IPsec transport mode to achieve secure socket-level communication.
     Also, kernel-internal crypto code has been imported to sys/crypto, and
     IPsec support has been added to the following userland applications:
     sbin/ping, usr.sbin/inetd, usr.sbin/rrenumd, usr.sbin/traceroute6,
     usr.sbin/rtadvd, usr.sbin/setkey
     
     
     1.3. USERLAND CHANGES
     ---------------------
     
     The base C/C++ compiler has been upgraded from GCC 2.7.2 to GCC 2.95.2.
     This gives users full ISO C++ support, and preliminary C9x support.
     
     Various changes has been made to /bin/sh to improve POSIX 1003.2
     conformance, especially for scripting.
     
     The f77 emulation via f2c has been replaced by a native F77 compiler.
     
     The timezone database has been updated to catch all of the recent changes
     in Europe, the former Soviet Union, and Central and South America.
     The timezone data files now contain a magic number allowing for easy
     identification.
     
     Groff/troff/eqn has been updated to version 1.15.
     
     Gdb has been updated to version 4.18.
     
     Numerous fixes have been applied to improve the security of FreeBSD code
     as part of the FreeBSD Auditing Project.
     
     FreeBSD's threads library, libc_r, has had many features and performance
     improvements added, which makes it almost completely POSIX-compliant.  In
     addition, Linux's kernel-supported LinuxThreads library is now available as
     a port (ports/devel/linuxthreads), which can be used for native FreeBSD
     programs.
     
     The following dedicated IPv6 applications have been added:
      sbin/ping6, sbin/rtsol, usr.sbin/gifconfig, usr.sbin/ifmcstat,
      usr.sbin/pim6dd, usr.sbin/pim6sd, usr.sbin/prefix, usr.sbin/rip6query,
      usr.sbin/route6d, usr.sbin/rrenumd, usr.sbin/rtadvd, usr.sbin/rtsold,
      usr.sbin/traceroute6
     
     The following applications have been updated to support IPv6:
      usr.bin/netstat, usr.bin/fstat, usr.bin/sockstat, usr.sbin/tcpdchk,
      usr.sbin/tcpdump, usr.sbin/trpt, libexec/ftpd, libexec/rlogind,
      libexec/rshd, libexec/telnetd
     
     Many ports have been updated to support IPv6. See the 'ipv6' virtual ports
     category for a list.
     
    -Sysinstall enables PC-card controllers and pccardd(8) for PC-card 
    +Sysinstall enables PC-card controllers and pccardd(8) for PC-card
     installation media.
     
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA and PCI
     bus based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 164x series MCA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F
     Microchannel (MCA) bus adapters are also supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.  The DPT SmartRAID/CACHE V
     is not yet supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
     	Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     
     QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters.
     QLogic 2100 Fibre Channel Adapters (private loop only).
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (acd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
    -  [ Note:  There is work-in-progress to port the UltraStor driver to 
    -    the new CAM SCSI framework, but no estimates on when or if it will 
    +  [ Note:  There is work-in-progress to port the UltraStor driver to
    +    the new CAM SCSI framework, but no estimates on when or if it will
         be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     
     2.2. Ethernet cards
     -------------------
     
     Adaptec Duralink PCI fast ethernet adapters based on the Adaptec
     AIC-6915 fast ethernet controller chip, including the following:
       ANA-62011 64-bit single port 10/100baseTX adapter
       ANA-62022 64-bit dual port 10/100baseTX adapter
       ANA-62044 64-bit quad port 10/100baseTX adapter
       ANA-69011 32-bit single port 10/100baseTX adapter
       ANA-62020 64-bit single port 100baseFX adapter
     
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI gigabit ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       Alteon AceNIC (Tigon 1 and 2)
       3Com 3c985-SX (Tigon 1 and 2)
       Netgear GA620 (Tigon 2)
       Silicon Graphics Gigabit Ethernet
       DEC/Compaq EtherWORKS 1000
       NEC Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 fast ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC fast ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
       Kingston KNE110TX
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 fast ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Macronix/Lite-On PNIC II LC82C115 fast ethernet NICs including the following:
       LinkSys EtherFast LNE100TX Version 2
     
     Winbond W89C840F fast ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" fast ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE-530TX
       AOpen/Acer ALN-320
     
     Silicon Integrated Systems SiS 900 and SiS 7016 PCI fast ethernet NICs
     
     Sundance Technologies ST201 PCI fast ethernet NICs including
     the following:
       D-Link DFE-550TX
     
     SysKonnect SK-984x PCI gigabit ethernet cards including the following:
       SK-9841 1000baseLX single mode fiber, single port
       SK-9842 1000baseSX multimode fiber, single port
       SK-9843 1000baseLX single mode fiber, dual port
       SK-9844 1000baseSX multimode fiber, dual port
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100baseTX
       Racore 8148 10baseT/100baseTX/100baseFX multi-personality
     
     ADMtek Inc. AL981-based PCI fast ethernet NICs
     ADMtek Inc. AN985-based PCI fast ethernet NICs
     ADMtek Inc. AN986-based USB ethernet NICs including the following:
       LinkSys USB100TX
       Billionton USB100
       Melco Inc. LU-ATX
       D-Link DSB-650TX
       SMC 2202USB
     
     CATC USB-EL1210A-based USB ethernet NICs including the following:
       CATC Netmate
       CATC Netmate II
       Belkin F5U111
     
     Kawasaki LSI KU5KUSB101B-based USB ethernet NICs including
     the following:
       LinkSys USB10T
       Entrega NET-USB-E45
       Peracom USB Ethernet Adapter
       3Com 3c19250
       ADS Technologies USB-10BT
       ATen UC10T
       Netgear EA101
       D-Link DSB-650
       SMC 2102USB
       SMC 2104USB
       Corega USB-T
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     DEC FDDI (DEFPA/DEFEA) NICs
     
     Davicom DM9100 and DM9102 PCI fast ethernet NICs, including the
     following:
       Jaton Corporation XpressNet
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     Intel InBusiness 10/100 PCI Network Adapter
     Intel PRO/100+ Management Adapter
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 ethernet interface.
     
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
    -3Com 3C509, 3C529 (MCA), 3C579, 
    +3Com 3C509, 3C529 (MCA), 3C579,
     3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA),
     3C590/592/595/900/905/905B/905C PCI
     and EISA (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980/3c980B Fast Etherlink XL server adapter
     
     3Com 3cSOHO100-TX OfficeConnect adapter
     
     Toshiba ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards,
     including the following:
       AR-P500 Ethernet card
       Accton EN2212/EN2216/UE2216(OEM)
       Allied Telesis CentreCOM LA100-PCM_V2
       AmbiCom 10BaseT card
       BayNetworks NETGEAR FA410TXC Fast Ethernet
       CNet BC40 adapter
       COREGA Ether PCC-T/EtherII PCC-T
       Compex Net-A adapter
       CyQ've ELA-010
       D-Link DE-650/660
       Danpex EN-6200P2
       IO DATA PCLATE
       IBM Creditcard Ethernet I/II
       IC-CARD Ethernet/IC-CARD+ Ethernet
       Linksys EC2T/PCMPC100
       Melco LPC-T
       NDC Ethernet Instant-Link
       National Semiconductor InfoMover NE4100
       Network Everywhere Ethernet 10BaseT PC Card
       Planex FNW-3600-T
       Socket LP-E
       Surecom EtherPerfect EP-427
       Telecom Device SuperSocket RE450T
     
     Megahertz X-Jack Ethernet PC-Card CC-10BT
     
     2.3 ATM
     -------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signalling Protocols
             - The ATM Forum UNI 3.1 signalling protocol
             - The ATM Forum UNI 3.0 signalling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signalling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     
     2.4. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 / Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed
     (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes
    -(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco 
    -Airconnect). Note: the ISA versions of these adapters are actually PCMCIA 
    -cards combined with an ISA to PCMCIA bridge card, so both kinds of 
    +(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco
    +Airconnect). Note: the ISA versions of these adapters are actually PCMCIA
    +cards combined with an ISA to PCMCIA bridge card, so both kinds of
     devices work with the same driver.
     
     Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA,
     PCI and ISA adapters are all supported.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.FreeBSD.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 4.0-RELEASE and 3.X-RELEASE CDs may be ordered on CDROM from:
     
             Walnut Creek CDROM
             4041 Pike Lane, Suite F
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 3.0 and some of the following issues may affect you, depending
     of course on your chosen method of upgrading.  There are two popular
     ways of upgrading FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     Please read the UPGRADE.TXT file for more information.
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.FreeBSD.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.FreeBSD.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.FreeBSD.org/handbook/donors.html
     
             Justin M. Seger <jseger@FreeBSD.org> for almost single-handedly
             converting the ports collection to ELF.
     
             Doug Rabson <dfr@FreeBSD.org> and John Birrell <jb@FreeBSD.org>
             for making FreeBSD/alpha happen and to the NetBSD project for
             substantial indirect aid.
     
             Peter Wemm <peter@FreeBSD.org> for the new kernel module system
             (with substantial aid from Doug Rabson).
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/4.1.1R/announce.sgml b/es/releases/4.1.1R/announce.sgml index 100c86126e..977b786a9d 100644 --- a/es/releases/4.1.1R/announce.sgml +++ b/es/releases/4.1.1R/announce.sgml @@ -1,83 +1,85 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Wed, 27 Sep 2000 00:07:50 -070
    From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>
    To: announce@FreeBSD.org
    Subject: 4.1.1-RELEASE now available from ftp.freebsd.org

    As always, I'm pleased to announce the availability of FreeBSD 4.1.1-RELEASE, a point release update for 4.1-RELEASE and, of course, the very latest in 4.x-STABLE branch technology.

    Since 4.1-RELEASE was produced in August 2000, RSA released their code into the public domain and a number of other security enhancements were made possible through the FreeBSD project's permission to export cryptographic code from the United States. These changes are fully reflected in 4.1.1-RELEASE, making it one of the most secure "out of the box" releases of FreeBSD we've ever done.

    We also took the opportunity to include support for new features like IDE ATA100 support, drivers for additional Gigabit ethernet cards and hardware watchpoints in gdb. Please see the release notes for more information.

    The 4.1.1-RELEASE is available right now for the i386 architecture (alpha to follow in several days) in "FTP installable" and ISO image form. For the appropriate bits, please see:

    ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.1.1-RELEASE/
    ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.1.1-install.iso

    When the Alpha release follows in several days, it will be available from:

    ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/4.1.1-RELEASE/
    ftp://ftp.freebsd.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.1.1-install.iso

    Please watch the alpha@freebsd.org mailing list for an announcement.

    IMPORTANT NOTE: This is a network only point release and will not be made generally available for sale on CDROM, at least not from BSDi or anyone else we currently have knowledge of. The next official CD release will be FreeBSD 4.2-RELEASE, still scheduled for mid-November 2000.

    FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, Elbonia, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

       ftp://ftp.<yourdomain>.freebsd.org/pub/FreeBSD
     
    - +

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

    Thanks! - Jordan +&footer; diff --git a/es/releases/4.1.1R/errata.sgml b/es/releases/4.1.1R/errata.sgml index 4bedf959ec..4da9beb136 100644 --- a/es/releases/4.1.1R/errata.sgml +++ b/es/releases/4.1.1R/errata.sgml @@ -1,47 +1,48 @@ - - + + %navincludes; %includes; ]> - + &header;
     If you read no other documentation before installing this
     version of FreeBSD, you should at least by all means *READ
     THE ERRATA* for this release so that you don't stumble over
     problems which have already been found and fixed.  This ERRATA.TXT
     file is obviously already out of date by definition, but other
     copies are kept updated on the net and should be consulted as
     the "current errata" for your release.  These other copies of
    -the errata are located at: 
    +the errata are located at:
     
       1. http://www.FreeBSD.org/releases/
     
    -  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT   
    -     (and any sites which keep up-to-date mirrors of this location).          
    +  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT
    +     (and any sites which keep up-to-date mirrors of this location).
     
     Any changes to this file are also automatically emailed to:
     
     	freebsd-current@FreeBSD.org
     
     For all FreeBSD security advisories, see:
     
     	http://www.FreeBSD.org/security/
     
     for the latest security incident information.
     
     ---- Security Advisories:
     
     Current active security advisories:	None
     
     ---- System Update Information:
     
     

    Release Home &footer; diff --git a/es/releases/4.1.1R/notes.sgml b/es/releases/4.1.1R/notes.sgml index bfa8611608..a9e5066604 100644 --- a/es/releases/4.1.1R/notes.sgml +++ b/es/releases/4.1.1R/notes.sgml @@ -1,736 +1,737 @@ - - + + %navincludes; %includes; ]> &header;
     === Platform specifics for i386
                                      RELEASE NOTES
                                  FreeBSD 4.1.1-RELEASE
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a Web-based interface can also see
     http://www.freebsd.org/send-pr.html).
     
     For information about FreeBSD and the layout of the 4.1.1-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     For the latest of these 4.1.1-stable snapshots, you should always see:
     
             ftp://releng4.freebsd.org/pub/FreeBSD
     
     Table of contents:
     ------------------
     1. What's new since 4.1-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 FDDI
        2.4 ATM
        2.5 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     
     6. Acknowledgements
     
     
     1. What's new since 4.1-RELEASE
     --------------------------------------
     
     1.1. KERNEL CHANGES
     -------------------
     
    -The tap driver, a virtual Ethernet device driver for bridged 
    +The tap driver, a virtual Ethernet device driver for bridged
     configurations, has been added.
     
     accept_filters, a kernel feature to reduce overheads when accepting
     and reading new connections on listening sockets, has been added.
     
     POSIX.1b Shared Memory Objects are now supported.  The implementation
     uses regular files, but automatically enables the MAP_NOSYNC flag
     when they are mmap(2)ed.
     
     The ata(4) driver now has support for ATA100 controllers.
     
    -The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit 
    +The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit
     Ethernet and Netgear GA620T 1000baseT Gigabit Ethernet cards.
     
     The ng_bridge(4) node type has been added to the netgraph subsystem.
     Miscellaneous bug fixes and enhancements have also been made.
     
     
     1.2. SECURITY FIXES
     -------------------
     
     1.3. USERLAND CHANGES
     ---------------------
     
     GDB now supports hardware watchpoints.
     
     sendmail upgraded from version 8.9.3 to version 8.11.0.  Important changes
     include: new default file locations (see
     /usr/src/contrib/sendmail/cf/README); newaliases is limited to root and
     trusted users; and the MSA port (587) is turned on by default.  See
     /usr/src/contrib/sendmail/RELEASE_NOTES for more information.
     
     routed(8) has been updated to version 2.22.
     
     The truncate(1) utility, which truncates or extends the length
     of files, has been added.
     
     syslogd(8) can take a -n option to disable DNS queries for every
     request.
     
    -kenv(1), a command to dump the kernel environment, has been added. 
    +kenv(1), a command to dump the kernel environment, has been added.
     
     The behavior of periodic(8) is now controlled by /etc/defaults/periodic.conf
     and /etc/periodic.conf.
     
     logger(1) can now send messages directly to a remote syslog.
     
     OpenSSL has been upgraded to 0.9.5a, which includes numerous bugfixes
     and enhancements.
     
     finger(1) now has the ability to support fingering aliases, via the
     finger.conf(5) file.
     
     RSA Security has waived all patent rights to the RSA algorithm (two
     weeks before the patent was due to expire).  As a result, the native
     OpenSSL implementation of the RSA algorithm is now activated by
     default, and the rsaref port and librsaUSA are no longer
     required for USA residents.
     
     sshd now enabled by default on new installs.
     
     The xl(4) driver now supports the 3Com 3C556 and 3C556B MiniPCI
     adapters used on some laptops.
     
     killall(1) is now a C program, rather than a Perl script.  As a
     result, killall's -m option now uses the regular expression syntax of
     regex(3), rather than that of perl(1).
     
     boot98cfg(8), a PC-98 boot manager installation and configuration
     utility, has been added.
     
     Binutils have been upgraded to 2.10.0.
     
     libreadline has been upgraded to 4.1.
     
    -The ifconfig(8) command can set the link-layer address of an interface. 
    +The ifconfig(8) command can set the link-layer address of an interface.
     
    -bktr(4) driver update to 2.1.5.  New tuner types have been added, 
    +bktr(4) driver update to 2.1.5.  New tuner types have been added,
     and improvememts to the KLD module and to memory allocation have been
     made.
     
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA and PCI
     bus based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 164x series MCA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F
     Microchannel (MCA) bus adapters are also supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
    -SmartRAID IV SCSI/RAID controllers are supported.  
    +SmartRAID IV SCSI/RAID controllers are supported.
     
     DPT SmartRAID V/VI and Adaptec SCSI RAID 2100, 3200, and 3400 cards are
     supported.
     
     AMI MegaRAID Express and Enterprise family RAID controllers:
         MegaRAID 418
         MegaRAID Enterprise 1200 (428)
         MegaRAID Enterprise 1300
         MegaRAID Enterprise 1400
         MegaRAID Enterprise 1500
         MegaRAID Elite 1500
         MegaRAID Express 200
         MegaRAID Express 300
         Dell PERC
         Dell PERC 2/SC
         Dell PERC 2/DC
     Some HP NetRAID controllers are OEM versions of AMI designs, and
     these are also supported.  Booting from these controllers is supported.
     
    -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x 
    +Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x
     firmware:
         DAC960P
         DAC960PD
         DAC960PDU
         DAC960PL
         DAC960PJ
         DAC960PG
         AcceleRAID 150
         AcceleRAID 250
         eXtremeRAID 1100
    -Booting from these controllers is supported. EISA adapters are not 
    +Booting from these controllers is supported. EISA adapters are not
     supported.
     
     3ware Escalade ATA RAID controllers.  All members of the 5000 and
     6000 series are supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
     	Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     
     QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters.
     QLogic 2100 Fibre Channel Adapters (private loop only).
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (acd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
    -  [ Note:  There is work-in-progress to port the UltraStor driver to 
    -    the new CAM SCSI framework, but no estimates on when or if it will 
    +  [ Note:  There is work-in-progress to port the UltraStor driver to
    +    the new CAM SCSI framework, but no estimates on when or if it will
         be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     
     2.2. Ethernet cards
     -------------------
     
     Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec
     AIC-6915 Fast Ethernet controller chip, including the following:
       ANA-62011 64-bit single port 10/100baseTX adapter
       ANA-62022 64-bit dual port 10/100baseTX adapter
       ANA-62044 64-bit quad port 10/100baseTX adapter
       ANA-69011 32-bit single port 10/100baseTX adapter
       ANA-62020 64-bit single port 100baseFX adapter
     
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       3Com 3c985-SX (Tigon 1 and 2)
       Alteon AceNIC 1000baseSX (Tigon 1 and 2)
       Alteon AceNIC 1000baseT (Tigon 2)
       DEC/Compaq EtherWORKS 1000
       Farallon PN9000SX
       NEC Gigabit Ethernet
       Netgear GA620 (Tigon 2)
       Netgear GA620T (Tigon 2, 1000baseT)
       Silicon Graphics Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 Fast Ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
       Kingston KNE110TX
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX Version 2
     
     Winbond W89C840F Fast Ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE-530TX
       AOpen/Acer ALN-320
     
     Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs
     
     Sundance Technologies ST201 PCI Fast Ethernet NICs including
     the following:
       D-Link DFE-550TX
     
     SysKonnect SK-984x PCI Gigabit Ethernet cards including the following:
       SK-9841 1000baseLX single mode fiber, single port
       SK-9842 1000baseSX multimode fiber, single port
       SK-9843 1000baseLX single mode fiber, dual port
       SK-9844 1000baseSX multimode fiber, dual port
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100baseTX
       Racore 8148 10baseT/100baseTX/100baseFX multi-personality
     
     ADMtek Inc. AL981-based PCI Fast Ethernet NICs
     ADMtek Inc. AN985-based PCI Fast Ethernet NICs
     ADMtek Inc. AN986-based USB Ethernet NICs including the following:
       LinkSys USB100TX
       Billionton USB100
       Melco Inc. LU-ATX
       D-Link DSB-650TX
       SMC 2202USB
     
     CATC USB-EL1210A-based USB Ethernet NICs including the following:
       CATC Netmate
       CATC Netmate II
       Belkin F5U111
     
     Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including
     the following:
       LinkSys USB10T
       Entrega NET-USB-E45
       Peracom USB Ethernet Adapter
       3Com 3c19250
       ADS Technologies USB-10BT
       ATen UC10T
       Netgear EA101
       D-Link DSB-650
       SMC 2102USB
       SMC 2104USB
       Corega USB-T
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     
     Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the
     following:
       Jaton Corporation XpressNet
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     Intel InBusiness 10/100 PCI Network Adapter
     Intel PRO/100+ Management Adapter
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 Ethernet interface.
     
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
    -3Com 3C509, 3C529 (MCA), 3C579, 
    +3Com 3C509, 3C529 (MCA), 3C579,
     3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA),
     3C590/592/595/900/905/905B/905C PCI,
     3C556/556B MiniPCI,
     and EISA (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980/3c980B Fast Etherlink XL server adapter
     
     3Com 3cSOHO100-TX OfficeConnect adapter
     
     Toshiba Ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards,
     including the following:
       AR-P500 Ethernet card
       Accton EN2212/EN2216/UE2216(OEM)
       Allied Telesis CentreCOM LA100-PCM_V2
       AmbiCom 10BaseT card
       BayNetworks NETGEAR FA410TXC Fast Ethernet
       CNet BC40 adapter
       COREGA Ether PCC-T/EtherII PCC-T
       Compex Net-A adapter
       CyQ've ELA-010
       D-Link DE-650/660
       Danpex EN-6200P2
       IO DATA PCLATE
       IBM Creditcard Ethernet I/II
       IC-CARD Ethernet/IC-CARD+ Ethernet
       Linksys EC2T/PCMPC100
       Melco LPC-T
       NDC Ethernet Instant-Link
       National Semiconductor InfoMover NE4100
       Network Everywhere Ethernet 10BaseT PC Card
       Planex FNW-3600-T
       Socket LP-E
       Surecom EtherPerfect EP-427
       Telecom Device SuperSocket RE450T
     
     Megahertz X-Jack Ethernet PC-Card CC-10BT
     
     2.3. FDDI
     ---------
     
     DEC FDDI (DEFPA/DEFEA) NICs
     
     
     2.4. ATM
     --------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signalling Protocols
             - The ATM Forum UNI 3.1 signalling protocol
             - The ATM Forum UNI 3.0 signalling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signalling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     
     2.5. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 / Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed
     (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes
    -(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco 
    -Airconnect). Note: the ISA versions of these adapters are actually PCMCIA 
    -cards combined with an ISA to PCMCIA bridge card, so both kinds of 
    +(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco
    +Airconnect). Note: the ISA versions of these adapters are actually PCMCIA
    +cards combined with an ISA to PCMCIA bridge card, so both kinds of
     devices work with the same driver.
     
     Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA,
     PCI and ISA adapters are all supported.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 3.0 and there may be some issues affecting you, depending
     of course on your chosen method of upgrading.  There are two popular
     ways of upgrading FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     Please read the UPGRADE.TXT file for more information, preferably
     before beginning an upgrade.
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     If you're tracking the -stable development efforts, you should
     definitely join the -stable mailing list, in order to keep abreast
     of recent developments and changes that may affect the way you
     use and maintain the system:
     
     		freebsd-stable@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
     
             Justin M. Seger <jseger@freebsd.org> for almost single-handedly
             converting the ports collection to ELF.
     
             Doug Rabson <dfr@freebsd.org> and John Birrell <jb@freebsd.org>
             for making FreeBSD/alpha happen and to the NetBSD project for
             substantial indirect aid.
     
             Peter Wemm <peter@freebsd.org> for the new kernel module system
             (with substantial aid from Doug Rabson).
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     
     

    Release Home &footer; diff --git a/es/releases/4.1R/announce.sgml b/es/releases/4.1R/announce.sgml index 5dbff2c346..19e6172a09 100644 --- a/es/releases/4.1R/announce.sgml +++ b/es/releases/4.1R/announce.sgml @@ -1,110 +1,112 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Thu, 27 Jul 2000 05:17:09 -0700
    From: "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>
    To: announce@FreeBSD.org
    Subject: 4.1-RELEASE now available from ftp.freebsd.org

    I'm very pleased to announce the availability of FreeBSD 4.1-RELEASE, the very latest in 4.x-STABLE branch technology. Following the release of FreeBSD 4.0 in March, 2000, many bugs were fixed, important security issues dealt with, and quite a few new features added. Please see the release notes for more information.

    The 4.1-RELEASE is available for i386 and alpha right now and can be installed directly over the net using the boot floppies or copied to a local NFS/ftp server. ISO images will also be provided later (see below).

    ISO (CD) Images
    ---------------

    ISO images of the installation CD will be made available by August 1st 2000, after the bits have undergone a bit more integration testing. This additional delay is necessary given that the ISO images are so large (~650MB each) and are not something which many people want to transfer more than once. A follow-up announcement will be sent once the ISO images are in place, so please don't send me email asking where they are or when they'll be ready. When they're ready, they'll be uploaded and an announcement will be sent out.

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

    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.1-install.iso
    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.1-install.iso

    If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISOs, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi. FreeBSD 4.1-RELEASE can be ordered as a 4 CD set from The FreeBSD Mall from where it will soon be shipping. Each CD sets contains the FreeBSD installation and application package bits for either the x86 or the alpha architecture (each architecture has its own CD set). For a set of distfiles used to build ports in the ports collection, please see also the FreeBSD Toolkit, a 6 CD set containing all such extra bits which we can no longer fit on the 4 CD sets. You can also order by phone, postal mail, FAX or email at:

       BSDi
       4041 Pike Lane, #F
       Concord CA, 94520 USA
       Phone: +1 925 674-0783
       Fax: +1 925 674-0821
       Tech Support: +1 925 603-1234
       Email: orders@wccdrom.com
       WWW: http://www.wccdrom.com/
     

    FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Austria, Brazil, Bulgaria, Canada, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Malaysia, the Netherlands, Poland, Portugal, Rumania, Russia, Slovenia, South Africa, Spain, Sweden, Taiwan, Thailand, Elbonia, the Ukraine and the United Kingdom (and quite possibly several others which I've never even heard of :).

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

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

    - +

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

    The latest versions of export-restricted code for FreeBSD are also being made available at the following locations. Now that FreeBSD has export permission for crypto from the United States government, you can get it from the following locations or from ftp.freebsd.org:

    South Africa

    ftp://ftp.internat.FreeBSD.org/pub/FreeBSD
    ftp://ftp2.internat.FreeBSD.org/pub/FreeBSD

    Brazil

    ftp://ftp.br.FreeBSD.org/pub/FreeBSD

    Finland

    ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt

    Thanks! - Jordan +&footer; diff --git a/es/releases/4.1R/errata.sgml b/es/releases/4.1R/errata.sgml index 57c51c682b..527cd7136e 100644 --- a/es/releases/4.1R/errata.sgml +++ b/es/releases/4.1R/errata.sgml @@ -1,76 +1,77 @@ - - + + %navincludes; %includes; ]> - + &header;
     If you read no other documentation before installing this
     version of FreeBSD, you should at least by all means *READ
     THE ERRATA* for this release so that you don't stumble over
     problems which have already been found and fixed.  This ERRATA.TXT
     file is obviously already out of date by definition, but other
     copies are kept updated on the net and should be consulted as
     the "current errata" for your release.  These other copies of
    -the errata are located at: 
    +the errata are located at:
     
       1. http://www.FreeBSD.org/releases/
     
    -  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT   
    -     (and any sites which keep up-to-date mirrors of this location).          
    +  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT
    +     (and any sites which keep up-to-date mirrors of this location).
     
     Any changes to this file are also automatically emailed to:
     
     	freebsd-current@FreeBSD.org
     
     For all FreeBSD security advisories, see:
     
     	http://www.FreeBSD.org/security/
     
     for the latest security incident information.
     
     ---- Security Advisories:
     
     Current active security advisories:	None
     
     ---- System Update Information:
     
     The FreeBSD Boot Manager (boot0) has a bug that causes it to hang the machine
     during boot with no screen output.
     
     Fix: Boot your machine into FreeBSD either via a boot floppy or a CD-ROM, then
     download a new boot0 binary from the following location:
     
     	http://people.FreeBSD.org/~jhb/4.1R/i386/boot0
     
     Once you have downloaded the new binary, install it with the boot0cfg command
     onto your hard disk.  For example, if you have boot0 on disk ad0, you would
     run the following command:
     
     	/usr/sbin/boot0cfg -B -b /path/to/downloaded/boot0 ad0
     
     You may also use cvsup to update your source tree and build the new boot0
     binary from source.  You will need version 1.14.2.3 of
     src/sys/boot/i386/boot0/boot0.s or newer.
     
     The MD5 checksum of this file is:
     
     	MD5 (boot0) = 8770a386dba44f0aa06b15db72c1f624
     
     To verify the checksum of your downloaded copy, perform the following
     command:
     
     	/sbin/md5 /path/to/downloaded/boot0
     
     and compare with the above.
     
     

    Release Home &footer; diff --git a/es/releases/4.1R/notes.sgml b/es/releases/4.1R/notes.sgml index 7f732a3cba..7c7b2d244a 100644 --- a/es/releases/4.1R/notes.sgml +++ b/es/releases/4.1R/notes.sgml @@ -1,785 +1,786 @@ - - + + %navincludes; %includes; ]> &header;
                                      RELEASE NOTES
                                   FreeBSD 4.1-RELEASE
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a Web-based interface can also see
     http://www.freebsd.org/send-pr.html).
     
     For information about FreeBSD and the layout of the 4.1-RELEASE
     directory (especially if you're installing from floppies!), see
     ABOUT.TXT.  For installation instructions, see the INSTALL.TXT and
     HARDWARE.TXT files.
     
     For the latest 4.1-stable snapshots (post-4.1 snaps), you should
     always see:
     
             ftp://releng4.freebsd.org/pub/FreeBSD
     
     Table of contents:
     ------------------
     1. What's new since 4.0-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 FDDI
        2.4 ATM
        2.5 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     
     6. Acknowledgements
     
     
     1. What's new since 4.0-RELEASE
     --------------------------------------
     
     1.1. KERNEL CHANGES
     -------------------
     
     FreeBSD 4.1-RELEASE contains updated code from the KAME project
     (http://www.kame.net) including the following features:
     
     * Significantly improved IPSEC functionality.  In particular, IPSEC
       security associations must no longer be manually keyed: the new code
       supports racoon, the KAME IKE daemon, which is located in
       /usr/ports/security/racoon.  Racoon has been shown to interoperate
       well with other vendor IKE systems, meaning that FreeBSD 4.1 can be
       used in a heterogeneous IPSEC environment.  However, racoon *is*
       still a work in progress, meaning that there may still be bugs,
       configuration syntax changes, etc.
     
     * About 9 months of fixes and improvements to the IPv6 code relative to
       what was in 4.0-RELEASE.
     
     * FreeBSD 4.1 can now be installed on an IPv6-only network - this will be
       the first release of FreeBSD that never needs to operate using IPv4 at
       all! ftp7.jp.freebsd.org (Listed as Japan #7 in sysinstall) is an
       IPv6-reachable mirror site for installation and package-fetching.
     
     * The ALTQ traffic-shaping system has not yet been merged - it will
       hopefully be added before the release of 4.2.  The more experimental
       KAME code has also not been merged.  If you need those features,
       consider using the 4.1-RELEASE+KAME snapshots from
       ftp://ftp.kame.net which will become available after 4.1-RELEASE.
     
     * KNOWN ISSUES: NFS mounts over IPSEC do not seem to work reliably in
       all cases - mount hangs and possible data corruption have been
       observed.
     
     A new event notification facility called kqueue was added to the
     FreeBSD kernel.  This is a new interface which is able to replace
     poll/select, offering improved performance, as well as the ability
     to report many different types of events.  Support for monitoring
     changes in sockets, pipes, fifos, and files are present, as well as
     for signals and processes.
     
     Support for Intel's Wired for Management 2.0 (PXE) was added to
     the FreeBSD boot loader.  Due to API differences, the older PXE
     versions are not supported.  This allow network booting using DHCP.
     
     For the alpha release of FreeBSD, the following specifics also
     apply:
     
    -   FreeBSD/alpha now posseses a loader with FICL (Forth support) builtin. 
    +   FreeBSD/alpha now posseses a loader with FICL (Forth support) builtin.
     
        Parallel ports are now supported.
     
        Support for multiple new Alpha system types has been added. Please
        check HARDWARE.TXT for details.
     
        AlphaServer 4100 (Rawhide) does not want to allow installation using
    -   floppies or cdrom. Workaround is to install using another Alpha machine and 
    +   floppies or cdrom. Workaround is to install using another Alpha machine and
        move the disk to the AS4100. Once installed FreeBSD runs fine.
     
        AlphaServer 2100A (Lynx) is not supported in this release. Note that
        AlphaServer 2100 (Sable) works fine.
     
    -   Machines that have onboard IDE interfaces that their SRM can boot from 
    +   Machines that have onboard IDE interfaces that their SRM can boot from
        are now supported with the IDE disk being the root/boot device. See
        HARDWARE.TXT for machine specifics like speed, use of DMA etc.
     
        Note that TGA consoles (either builtin or on TGA expansion cards) will
        not work. You will need to use a serial console or install a VGA card.
     
     
     1.2. SECURITY FIXES
     -------------------
     
     The kernel and userland have been audited for bugs and security
     vulnerabilities resulting from the incorrect use of format strings in
     vfprintf()-like functions.  No vulnerabilities were discovered.
     
     For additional security fixes, see the list of released Security
     Advisories located at http://www.freebsd.org/security/
     
     1.3. USERLAND CHANGES
     ---------------------
     
     Support for the KAME IKE daemon, racoon, as noted in section 1.1 above.
     
     Several additional system utilities (whois, fetch, and possibly
     others) have gained the ability to operate over IPv6.
     
     cdcontrol(1) now supports a "cdid" command, which calculates and
     displays the CD serial number, using the same algorithm used by the CDDB
     database.
     
     mtree(8) now includes support for a file listing pathnames to be excluded
     when creating and verifying prototypes.  This makes it easier to use
     mtree as a part of an intrusion-detection system.
     
     The OPIE one-time-password suite has been updated to 2.32.
     
     OpenSSH has been upgraded to 2.1.0, which provides support for the
     SSH2 protocol, including DSA keys.  Therefore, OpenSSH users in the US
     no longer need to rely on the restrictively-licensed RSAREF toolkit
     which is required to handle RSA keys.  OpenSSH 2.1 interoperates well
     with other SSH2 clients and servers, including the ssh2 port.  See
     http://www.openssh.com for more details.
     
     OpenSSH can now authenticate using OPIE passwords in SSH1 mode.
     Support is not yet available in SSH2 mode.
     
     camcontrol(8) now includes a built in 'format' function to low-level
     format SCSI disks.
     
     Support for USB devices was added to the GENERIC kernel and to the
     installation programs to support USB devices out of the box.  Note that
     an AT keyboard must still be used during the initial install, but it
     should work fine afterwards.
     
     The entire i386 bootstrap was revamped to support automatic detection and
     use of the Enhanced Disk Drive BIOS extensions to support booting beyond
     the 1023rd cylinder.  As part of this change, the FreeBSD boot manager
     (boot0) was increased from 1 sector in size (512 bytes), to 2 sectors in
     length (1024 bytes).  As a result, several userland changes were made to
     cope with MBR boot loaders of varying sizes.
     
     libfetch has been greatly improved.  fetch(1) and the pkg tools now use
     libfetch instead of libftpio, which means that the pkg tools have gained
     HTTP support, and both have gained IPv6 support.
     
     The csh(1) shell has been replaced by tcsh(1), although it can still
     be run as csh(1).
     
     The more(1) command has been replaced by less(1), although it can still
     be run as more(1).
     
     ls(1) can produce colorized listings with the -G flag (and appropriate
     terminal support).
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA and PCI
     bus based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE or ESDI drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     WD1003 (any generic MFM/RLL)
     WD1007 (any generic IDE/ESDI)
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 164x series MCA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F
     Microchannel (MCA) bus adapters are also supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.  The DPT SmartRAID/CACHE V
     is not yet supported.
     
     AMI MegaRAID Express and Enterprise family RAID controllers:
         MegaRAID 418
         MegaRAID Enterprise 1200 (428)
         MegaRAID Enterprise 1300
         MegaRAID Enterprise 1400
         MegaRAID Enterprise 1500
         MegaRAID Elite 1500
         MegaRAID Express 200
         MegaRAID Express 300
         Dell PERC
         Dell PERC 2/SC
         Dell PERC 2/DC
     Some HP NetRAID controllers are OEM versions of AMI designs, and
     these are also supported.  Booting from these controllers is supported.
     
    -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x 
    +Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x
     firmware:
         DAC960P
         DAC960PD
         DAC960PDU
         DAC960PL
         DAC960PJ
         DAC960PG
         AcceleRAID 150
         AcceleRAID 250
         eXtremeRAID 1100
    -Booting from these controllers is supported. EISA adapters are not 
    +Booting from these controllers is supported. EISA adapters are not
     supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
     	Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     
     QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters.
     QLogic 2100 Fibre Channel Adapters (private loop only).
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (acd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
    -  [ Note:  There is work-in-progress to port the UltraStor driver to 
    -    the new CAM SCSI framework, but no estimates on when or if it will 
    +  [ Note:  There is work-in-progress to port the UltraStor driver to
    +    the new CAM SCSI framework, but no estimates on when or if it will
         be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     
     2.2. Ethernet cards
     -------------------
     
     Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec
     AIC-6915 Fast Ethernet controller chip, including the following:
       ANA-62011 64-bit single port 10/100baseTX adapter
       ANA-62022 64-bit dual port 10/100baseTX adapter
       ANA-62044 64-bit quad port 10/100baseTX adapter
       ANA-69011 32-bit single port 10/100baseTX adapter
       ANA-62020 64-bit single port 100baseFX adapter
     
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       Alteon AceNIC (Tigon 1 and 2)
       3Com 3c985-SX (Tigon 1 and 2)
       Netgear GA620 (Tigon 2)
       Silicon Graphics Gigabit Ethernet
       DEC/Compaq EtherWORKS 1000
       NEC Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     
     SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 Fast Ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
       Kingston KNE110TX
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX Version 2
     
     Winbond W89C840F Fast Ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE-530TX
       AOpen/Acer ALN-320
     
     Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs
     
     Sundance Technologies ST201 PCI Fast Ethernet NICs including
     the following:
       D-Link DFE-550TX
     
     SysKonnect SK-984x PCI Gigabit Ethernet cards including the following:
       SK-9841 1000baseLX single mode fiber, single port
       SK-9842 1000baseSX multimode fiber, single port
       SK-9843 1000baseLX single mode fiber, dual port
       SK-9844 1000baseSX multimode fiber, dual port
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100baseTX
       Racore 8148 10baseT/100baseTX/100baseFX multi-personality
     
     ADMtek Inc. AL981-based PCI Fast Ethernet NICs
     ADMtek Inc. AN985-based PCI Fast Ethernet NICs
     ADMtek Inc. AN986-based USB Ethernet NICs including the following:
       LinkSys USB100TX
       Billionton USB100
       Melco Inc. LU-ATX
       D-Link DSB-650TX
       SMC 2202USB
     
     CATC USB-EL1210A-based USB Ethernet NICs including the following:
       CATC Netmate
       CATC Netmate II
       Belkin F5U111
     
     Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including
     the following:
       LinkSys USB10T
       Entrega NET-USB-E45
       Peracom USB Ethernet Adapter
       3Com 3c19250
       ADS Technologies USB-10BT
       ATen UC10T
       Netgear EA101
       D-Link DSB-650
       SMC 2102USB
       SMC 2104USB
       Corega USB-T
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     
     Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the
     following:
       Jaton Corporation XpressNet
     
     Fujitsu MB86960A/MB86965A
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     Intel InBusiness 10/100 PCI Network Adapter
     Intel PRO/100+ Management Adapter
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 Ethernet interface.
     
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
    -3Com 3C509, 3C529 (MCA), 3C579, 
    +3Com 3C509, 3C529 (MCA), 3C579,
     3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA),
     3C590/592/595/900/905/905B/905C PCI
     and EISA (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980/3c980B Fast Etherlink XL server adapter
     
     3Com 3cSOHO100-TX OfficeConnect adapter
     
     Toshiba Ethernet cards
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards,
     including the following:
       AR-P500 Ethernet card
       Accton EN2212/EN2216/UE2216(OEM)
       Allied Telesis CentreCOM LA100-PCM_V2
       AmbiCom 10BaseT card
       BayNetworks NETGEAR FA410TXC Fast Ethernet
       CNet BC40 adapter
       COREGA Ether PCC-T/EtherII PCC-T
       Compex Net-A adapter
       CyQ've ELA-010
       D-Link DE-650/660
       Danpex EN-6200P2
       IO DATA PCLATE
       IBM Creditcard Ethernet I/II
       IC-CARD Ethernet/IC-CARD+ Ethernet
       Linksys EC2T/PCMPC100
       Melco LPC-T
       NDC Ethernet Instant-Link
       National Semiconductor InfoMover NE4100
       Network Everywhere Ethernet 10BaseT PC Card
       Planex FNW-3600-T
       Socket LP-E
       Surecom EtherPerfect EP-427
       Telecom Device SuperSocket RE450T
     
     Megahertz X-Jack Ethernet PC-Card CC-10BT
     
     2.3. FDDI
     ---------
     
     DEC FDDI (DEFPA/DEFEA) NICs
     
     
     2.4. ATM
     --------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signalling Protocols
             - The ATM Forum UNI 3.1 signalling protocol
             - The ATM Forum UNI 3.0 signalling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signalling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     
     2.5. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative
     Labs, Avance, Yamaha and ENSONIQ. (pcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 / Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed
     (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes
    -(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco 
    -Airconnect). Note: the ISA versions of these adapters are actually PCMCIA 
    -cards combined with an ISA to PCMCIA bridge card, so both kinds of 
    +(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS, and Melco
    +Airconnect). Note: the ISA versions of these adapters are actually PCMCIA
    +cards combined with an ISA to PCMCIA bridge card, so both kinds of
     devices work with the same driver.
     
     Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA,
     PCI and ISA adapters are all supported.
     
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     3.2. CDROM
     ----------
     
     FreeBSD 4.1-RELEASE and 3.x-RELEASE CDs may be ordered on CDROM from:
     
             BSDi
             4041 Pike Lane, Suite F
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@wccdrom.com or http://www.freebsdmall.com.
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 3.0 and there may be some issues affecting you, depending
     of course on your chosen method of upgrading.  There are two popular
     ways of upgrading FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     Please read the UPGRADE.TXT file for more information, preferably
     before beginning an upgrade.
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     If you're tracking the -stable development efforts, you should
     definitely join the -stable mailing list, in order to keep abreast
     of recent developments and changes that may affect the way you
     use and maintain the system:
     
     		freebsd-stable@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
             and to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/4.2R/announce.sgml b/es/releases/4.2R/announce.sgml index 0bc8001d17..c55577f2ed 100644 --- a/es/releases/4.2R/announce.sgml +++ b/es/releases/4.2R/announce.sgml @@ -1,83 +1,85 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Tue, 21 Nov 2000 04:31:48 -0800
    From: "Jordan K. Hubbard" <jkh@winston.osd.bsdi.com>
    To: announce@FreeBSD.org
    Subject: 4.2-RELEASE is now available

    It is my almost excessive pleasure to announce the availability of FreeBSD 4.2-RELEASE, the very latest in 4.x-STABLE branch technology. Following the release of FreeBSD 4.1.1 in September, 2000, many bugs were fixed, important security issues dealt with, and a conservative number of new features added. Please see the release notes for more information.

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

    ISO (CD) Images
    ---------------

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

    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.2-install.iso
    and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.2-install.iso

    If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISOs, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi. FreeBSD 4.2-RELEASE can be ordered as a 4 CD set from The FreeBSD Mall from where it will soon be shipping. Each CD sets contains the FreeBSD installation and application package bits for either the x86 or the alpha architecture (each architecture has its own CD set). For a set of distfiles used to build ports in the ports collection, please see also the FreeBSD Toolkit, a 6 CD set containing all such extra bits which we can no longer fit on the 4 CD sets. You can also order by phone, postal mail, FAX or email at:

       BSDi
       4041 Pike Lane, #F
       Concord CA, 94520 USA
       Phone: +1 925 674-0783
       Fax: +1 925 674-0821
       Tech Support: +1 925 603-1234
       Email: orders@wccdrom.com
       WWW: http://www.freebsdmall.com/
     

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

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

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

    - +

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

    Thanks! - Jordan +&footer; diff --git a/es/releases/4.2R/errata.sgml b/es/releases/4.2R/errata.sgml index db86ad47c3..30201a423b 100644 --- a/es/releases/4.2R/errata.sgml +++ b/es/releases/4.2R/errata.sgml @@ -1,47 +1,48 @@ - - + + %navincludes; %includes; ]> - + &header;
     If you read no other documentation before installing this
     version of FreeBSD, you should at least by all means *READ
     THE ERRATA* for this release so that you don't stumble over
     problems which have already been found and fixed.  This ERRATA.TXT
     file is obviously already out of date by definition, but other
     copies are kept updated on the net and should be consulted as
     the "current errata" for your release.  These other copies of
    -the errata are located at: 
    +the errata are located at:
     
       1. http://www.FreeBSD.org/releases/
     
    -  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT   
    -     (and any sites which keep up-to-date mirrors of this location).          
    +  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT
    +     (and any sites which keep up-to-date mirrors of this location).
     
     Any changes to this file are also automatically emailed to:
     
     	freebsd-current@FreeBSD.org
     
     For all FreeBSD security advisories, see:
     
     	http://www.FreeBSD.org/security/
     
     for the latest security incident information.
     
     ---- Security Advisories:
     
     Current active security advisories:	None
     
     ---- System Update Information:
     
     

    Release Home &footer; diff --git a/es/releases/4.2R/notes.sgml b/es/releases/4.2R/notes.sgml index 14315a1e58..ad89e007f2 100644 --- a/es/releases/4.2R/notes.sgml +++ b/es/releases/4.2R/notes.sgml @@ -1,1025 +1,1026 @@ - - + + %navincludes; %includes; ]> &header;
                                      RELEASE NOTES
                                   FreeBSD 4.2-RELEASE
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a Web-based interface can also see
     http://www.freebsd.org/send-pr.html).
     
     For information about FreeBSD and the layout of the 4.2-RELEASE directory
     (especially if you're installing from floppies!), see ABOUT.TXT.  For
     installation instructions, see the INSTALL.TXT and HARDWARE.TXT files.
     
     For the latest 4-stable snapshots, you should always see:
     
             ftp://releng4.freebsd.org/pub/FreeBSD
     
     Table of contents:
     ------------------
     1. What's new since 4.1-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 FDDI
        2.4 ATM
        2.5 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     
     6. Acknowledgements
     
     
     1. What's new since 4.1-RELEASE
     --------------------------------------
     Changes which were also present in the 4.1.1 point release will be
     marked [4.1.1].
     
     1.1. KERNEL CHANGES
     -------------------
     The tap driver, a virtual Ethernet device driver for bridged
     configurations, has been added. [4.1.1]
     
     accept_filters, a kernel feature to reduce overheads when accepting
     and reading new connections on listening sockets, has been added. [4.1.1]
     
     POSIX.1b Shared Memory Objects are now supported.  The implementation
     uses regular files, but automatically enables the MAP_NOSYNC flag
     when they are mmap(2)ed. [4.1.1]
     
     The ata(4) driver now has support for ATA100 controllers. [4.1.1]
     
     The ata(4) driver now has support for tagged queueing, which is
     enabled by the ATA_ENABLE_TAGS option.  It also supports the
     ServerWorks ROSB4 ATA33 chipset, the CMD 648 ATA66 and CMD 649 ATA100
     chipsets, and the Cyrix 5530.  It also has support for ATA "pseudo"
     RAID controllers, including the Promise Fasttrak and HighPoint HPT370
     controllers.
     
     The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit
     Ethernet and Netgear GA620T 1000baseT Gigabit Ethernet cards. [4.1.1]
     
     The ng_bridge(4) node type has been added to the netgraph subsystem.
     Miscellaneous bug fixes and enhancements have also been made. [4.1.1]
     
     Support for Fujitsu MB86960A/MB86965A based Ethernet PC-Cards is back.
     [4.1.1]
     
     The asr(4) driver, which provides support for the Adaptec SCSI RAID
     controller family, as well as the DPT SmartRAID V and VI families, has
     been added. [4.1.1]
     
     The i386 boot loader now has support for a "nullconsole" console type,
     for use on systems with neither a video console nor a serial
     port. [4.1.1]
     
     The pcn(4) driver, which supports the AMD PCnet/FAST, PCnet/FAST+,
     PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA adapters, has been
     added.  Although these cards are already supported by the lnc(4)
     driver, the pcn driver runs these chips in 32-bit mode and uses the RX
     alignment feature to achieve zero-copy receive.  This driver is also
     machine-independent, so it will work on both the i386 and alpha
     platforms.  The lnc driver is still needed to support non-PCI cards.
     
     The pcm(4) driver now supports the ESS Solo 1, Maestro-1, Maestro-2,
     and Maestro-2e; Forte Media fm801, ESS Maestro-2e, and VIA Technologies
     VT82C686A sound card/chipsets, and has received some other updates.
     
     Replace the PQ_*CACHE options with a single PQ_CACHESIZE option to be
     set to the cache size in kilobytes.  The old options are still
     supported for backwards compatibility.
     
     The NCPU, NAPIC, NBUS, and NINTR kernel configuration options,
    -for configuring SMP kernels, have been removed.  NCPU is now set to a 
    +for configuring SMP kernels, have been removed.  NCPU is now set to a
     maximum of 16, and the other, aforementioned options are now dynamic.
     
     The ahc(4) driver has been updated.
     
     The amr(4) driver has been updated with support for new AMI
     MegaRAID models.
     
     The snc(4) driver for the National Semiconductor DP8393X (SONIC)
     Ethernet controller.  Curently, this driver is only used on the PC-98
     architecture.
     
     The ich(4) driver for the Intel 82801AA (ICH) SMBus controller and
     compatibles has been added.
     
     bktr(4) driver has been updated to 2.15.  New tuner types have been
     added, and improvememts to the KLD module and to memory allocation
     have been made. [4.1.1]  This driver subsequently was updated to 2.17,
     which fixes bugs in devfs when unloading and reloading, and syncs with
     some NetBSD changes.
     
     Default the PC Card Interface Controller(pcic) to polling mode(irq 0).
     
     The ncv(4), nsp(4), and stg(4) drivers have been ported from
     NetBSD/pc98.  They supports NCR 53C50 / Workbit Ninja SCSI-3 / TMC
     18C30, 18C50 based PC-Card/ISA SCSI controllers.
     
     The mly(4) driver, for Mylex PCI to SCSI AccelRAID and eXtremeRAID
     controllers with firmware 6.x and later, has been added.
     
     The twe(4) driver for 3ware controllers has been updated, with
     improved queueing, error handling and reporting, and user interface
     for the 3ware-supplied '3dm' monitoring tool.
     
     The uscanner(4) driver, which provides basic USB scanner support using
     SANE, has been added.  (See the SANE home page for supported
     scanners.)  The HP ScanJet 4100C, 5200C and 6300C are known to be
     working.
     
     The umodem(4) driver for USB modems has been added; it currently
     supports the 3Com 5605 USB modem.
     
     
     1.2. SECURITY FIXES
     -------------------
     
     sysinstall(8) now allows the user to select one of three "security
     profiles" at install-time.  These profiles enable different levels of
     system security by enabling or disabling various system services in
     rc.conf(5) on new installs. [4.1.1]
     
     Many string-handling library calls were fixed to reduce the
     possibility of buffer overflow-related exploits.
     
     A security hole in Linux emulation was fixed (see security advisory
     FreeBSD-SA-00:42).  [4.1.1]
     
    -TCP now uses stronger randomness in choosing its initial sequence 
    +TCP now uses stronger randomness in choosing its initial sequence
     numbers (see security advisory FreeBSD-SA-00:52).
     
     A bug in finger(1) that could allow remote users to view
     world-readable files has been closed (see security advisory
     FreeBSD-SA-00:54).
     
     rlogind(8), rshd(8), and fingerd(8) are now disabled by default in
     /etc/inetd.conf.  This change only affects new installations.
     
     Several buffer overflows in tcpdump(1) were corrected (see security
     advisory FreeBSD-SA-00:61).
     
     A security hole in top(1) was corrected (see security advisory
     FreeBSD-SA-00:62).
     
     A potential security hole caused by an off-by-one-error in
     gethostbyname(3) has been fixed (see security advisory
     FreeBSD-SA-00:63).
     
     A potential buffer overflow in the ncurses(3X) library, which could
     cause arbitrary code to be run from within systat(1), has been corrected
     (see security advisory FreeBSD-SA-00:68).
     
     A vulnerability in telnetd(8) that could cause it to consume large
     amounts of server resources has been fixed (see security advisory
     FreeBSD-SA-00:69).
     
     The "nat deny_incoming" command in ppp(8) now works correctly (see
     security advisory FreeBSD-SA-00:70).
     
     
     1.3. USERLAND CHANGES
     ---------------------
     
     RSA Security has waived all patent rights to the RSA algorithm (two
     weeks before the patent was due to expire).  As a result, the native
     OpenSSL implementation of the RSA algorithm is now activated by
     default, and the rsaref port and librsaUSA are no longer required for
     USA residents. [4.1.1]
    - 
    +
     sshd is now enabled by default on new installs. [4.1.1]
    - 
    +
     Version numbers of installed packages have a new (backward-compatible)
     syntax, which supports the "PORTREVISION" and "PORTEPOCH" variables in
     ports collection makefiles.  These changes help keep track of changes
     in the ports collection entries such as security patches or
     FreeBSD-specific updates, which aren't reflected in the original,
     third-party software distributions.  pkg_version(1) can now compare
     these new-style version numbers. [4.1.1]
     
     sendmail upgraded from version 8.9.3 to version 8.11.1.  Important changes
     include: new default file locations (see /usr/src/contrib/sendmail/cf/README);
     newaliases is limited to root and trusted users; STARTTLS encryption; and
     the MSA port (587) is turned on by default.  See
     /usr/src/contrib/sendmail/RELEASE_NOTES for more information.
     
     mail.local(8) is no longer installed as a set-user-id binary.  If you
     are using a /etc/mail/sendmail.cf from the default sendmail.cf
     included with FreeBSD any time after 3.1.0, you are fine.  If you are
     using a hand-configured sendmail.cf and mail.local for delivery, check
     to make sure the F=S flag is set on the Mlocal line.  Those with .mc
     files who need to add the flag can do so by adding the following line
     to their your .mc file and regenerating the sendmail.cf file:
         MODIFY_MAILER_FLAGS(`LOCAL', `+S')dnl
     Note that FEATURE(`local_lmtp') already does this.
     
     The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY commands.
     
     vacation(1) has been updated to use the version included with
     sendmail.
     
     The sendmail(8) configuration building tools are installed in
     /usr/share/sendmail/cf/.
     
     OpenSSH has been upgraded to 2.2.0.  ssh-add(1) and ssh-agent(1) can
     now handle DSA keys.  An sftp server interoperable with ssh.com
     clients and others has been added.  scp(1) can now handle files >2GB.
     Interoperability with other ssh2 clients/servers has been improved.  A
     new feature to limit the number of outstanding unauthenticated ssh
     connections in sshd has been added.
     
     The compiler chain now uses the FSF-supplied C/C++ runtime
     initialization code.  This change brings about better compatibility
     with code generated from the various egcs and gcc ports, as well as
     the stock public FSF source.
     
     cvs(1) has been updated to 1.11.
     
     The threads library has gained some signal handling changes, bug
     fixes, and performance enhancements (including zero system call thread
     switching).  gdb(1) thread support has been updated to match these
     changes.
     
     GDB now supports hardware watchpoints. [4.1.1]
     
     routed(8) has been updated to version 2.22. [4.1.1]
     
     The truncate(1) utility, which truncates or extends the length of
     files, has been added. [4.1.1]
     
     syslogd(8) can take a -n option to disable DNS queries for every
     request. [4.1.1]
     
     kenv(1), a command to dump the kernel environment, has been added.
     [4.1.1]
     
     The behavior of periodic(8) is now controlled by
     /etc/defaults/periodic.conf and /etc/periodic.conf. [4.1.1]
    - 
    +
     logger(1) can now send messages directly to a remote syslog. [4.1.1]
    - 
    +
     OpenSSL has been upgraded to 0.9.5a, which includes numerous bugfixes
     and enhancements. [4.1.1]
    - 
    +
     finger(1) now has the ability to support fingering aliases, via the
     finger.conf(5) file. [4.1.1]
    - 
    +
     The xl(4) driver now supports the 3Com 3C556 and 3C556B MiniPCI
     adapters used on some laptops. [4.1.1]
    - 
    +
     killall(1) is now a C program, rather than a Perl script.  As a
     result, killall's -m option now uses the regular expression syntax of
     regex(3), rather than that of perl(1). [4.1.1]
     
     boot98cfg(8), a PC-98 boot manager installation and configuration
     utility, has been added. [4.1.1]
     
     The ifconfig(8) command can set the link-layer address of an
     interface.  [4.1.1]
     
     setproctitle(3) has been moved from libutil to libc. [4.1.1]
     
     sed(1) now takes a -E option for extended regular expression
     support. [4.1.1]
     
     ln(1) now takes an -i option to request user configuration before
     overwriting an existing file. [4.1.1]
     
     tcpdump(1) has received some updates and bugfixes.
     
     User-land ppp(8) has received a number of updates and bugfixes.
     
     The internal procedure for building perl has changed, and no longer
     depends on (nor installs) miniperl.  Users upgrading from source
     should delete /usr/bin/miniperl.
     
     To improve performance and disk utilization, the "ports skeletons" in
     the FreeBSD Ports Collection have been restructured.  Installed ports
     and packages should not be affected.
     
     ncurses has been updated to ncurses-5.1-20001009.
     
     make(1) has gained the :C/// (regexp substitution), :L (lowercase),
     and :U (uppercase) variable modifiers.  These were added to reduce the
     differences between the FreeBSD and OpenBSD/NetBSD make programs.
     
     The "in use" percentage metric displayed by netstat(1) now really
     reflects the percentage of network mbufs used.
     
     chio(1) now has the ability to specify elements by volume tag instead
     of by their physical location as well as the ability to return an
     element to its previous location.
     
     The ISC library from the BIND distribution is now built as libisc.
     
     IP Filter is now supported by the rc.conf(5) boot-time configuration
     and initialization.
     
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA and PCI
     bus based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 164x series MCA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     Adaptec 1400, 2100S, 3200S, and 3400S SCSI RAID controllers.
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F
     Microchannel (MCA) bus adapters are also supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.
     
     DPT SmartRAID V and VI SCSI RAID controllers:
         PM1554, PM2554, PM2654, PM2865, PM2754, PM3755, PM3757
     
     AMI MegaRAID Express and Enterprise family RAID controllers:
         MegaRAID 418
         MegaRAID Enterprise 1200 (428)
         MegaRAID Enterprise 1300
         MegaRAID Enterprise 1400
         MegaRAID Enterprise 1500
         MegaRAID Enterprise 1600
         MegaRAID Elite 1500
         MegaRAID Elite 1600
         MegaRAID Express 200
         MegaRAID Express 300
         MegaRAID Express 400
         Dell PERC
         Dell PERC 2/SC
         Dell PERC 2/DC
     Some HP NetRAID controllers are OEM versions of AMI designs, and
     these are also supported.  Booting from these controllers is supported.
     
    -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x 
    +Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x
     firmware:
         DAC960P
         DAC960PD
         DAC960PDU
         DAC960PL
         DAC960PJ
         DAC960PG
         AcceleRAID 150
         AcceleRAID 250
         eXtremeRAID 1100
    -Booting from these controllers is supported. EISA adapters are not 
    +Booting from these controllers is supported. EISA adapters are not
     supported.
     
     Mylex PCI to SCSI RAID controllers with 6.x firmware:
         AcceleRAID 160
         AcceleRAID 170
         AcceleRAID 352
         eXtremeRAID 2000
         eXtremeRAID 3000
     Compatible Mylex controllers not listed should work, but have not been
     verified.
     
     3ware Escalade ATA RAID controllers.  All members of the 5000 and
     6000 series are supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
     	Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     NCR 53C500 based PC-Card SCSI host adapters:
         IO DATA PCSC-DV
         KME KXLC002(TAXAN ICD-400PN, etc.), KXLC004
         Macnica Miracle SCSI-II mPS110
         Media Intelligent MSC-110, MSC-200
         NEC PC-9801N-J03R
         New Media Corporation BASICS SCSI
         Qlogic Fast SCSI
         RATOC REX-9530, REX-5572 (as SCSI only)
     
     TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters:
         Future Domain SCSI2GO
         IBM SCSI PCMCIA Card
         ICM PSC-2401 SCSI
         Melco IFC-SC
         RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A
     
     QLogic 1020, 1040, 1040B, 1080 and 1240 SCSI Host Adapters.
     QLogic 2100 Fibre Channel Adapters (private loop only).
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     Workbit Ninja SCSI-3 based PC-Card SCSI host adapters:
         Alpha-Data AD-PCS201
         IO DATA CBSC16
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (acd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
    -  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. 
    +  NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
    -  [ Note:  There is work-in-progress to port the UltraStor driver to 
    -    the new CAM SCSI framework, but no estimates on when or if it will 
    +  [ Note:  There is work-in-progress to port the UltraStor driver to
    +    the new CAM SCSI framework, but no estimates on when or if it will
         be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     
     2.2. Ethernet cards
     -------------------
     
     Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec
     AIC-6915 Fast Ethernet controller chip, including the following:
       ANA-62011 64-bit single port 10/100baseTX adapter
       ANA-62022 64-bit dual port 10/100baseTX adapter
       ANA-62044 64-bit quad port 10/100baseTX adapter
       ANA-69011 32-bit single port 10/100baseTX adapter
       ANA-62020 64-bit single port 100baseFX adapter
     
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       3Com 3c985-SX (Tigon 1 and 2)
       Alteon AceNIC 1000baseSX (Tigon 1 and 2)
       Alteon AceNIC 1000baseT (Tigon 2)
       DEC/Compaq EtherWORKS 1000
       Farallon PN9000SX
       NEC Gigabit Ethernet
       Netgear GA620 (Tigon 2)
       Netgear GA620T (Tigon 2, 1000baseT)
       Silicon Graphics Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
    -AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, 
    +AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO,
     PCnet/Home, and HomePNA.
     
     SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 Fast Ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1027D (MPX 5030/5038; RealTek 8139 clone?)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
       Kingston KNE110TX
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs
       NDC Communications SFA100A (98713A)
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       SVEC PN102TX (98713)
     
     Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX Version 2
     
     Winbond W89C840F Fast Ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE-530TX
       AOpen/Acer ALN-320
     
     Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs
     
     Sundance Technologies ST201 PCI Fast Ethernet NICs including
     the following:
       D-Link DFE-550TX
     
     SysKonnect SK-984x PCI Gigabit Ethernet cards including the following:
       SK-9841 1000baseLX single mode fiber, single port
       SK-9842 1000baseSX multimode fiber, single port
       SK-9843 1000baseLX single mode fiber, dual port
       SK-9844 1000baseSX multimode fiber, dual port
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100baseTX
       Racore 8148 10baseT/100baseTX/100baseFX multi-personality
     
     ADMtek Inc. AL981-based PCI Fast Ethernet NICs
     ADMtek Inc. AN985-based PCI Fast Ethernet NICs
     ADMtek Inc. AN986-based USB Ethernet NICs including the following:
       LinkSys USB100TX
       Billionton USB100
       Melco Inc. LUA-TX
       D-Link DSB-650TX
       SMC 2202USB
     
     CATC USB-EL1210A-based USB Ethernet NICs including the following:
       CATC Netmate
       CATC Netmate II
       Belkin F5U111
     
     Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including
     the following:
       LinkSys USB10T
       Entrega NET-USB-E45
       Peracom USB Ethernet Adapter
       3Com 3c19250
       ADS Technologies USB-10BT
       ATen UC10T
       Netgear EA101
       D-Link DSB-650
       SMC 2102USB
       SMC 2104USB
       Corega USB-T
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC EtherWORKS III NICs (DE203, DE204, and DE205)
     DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     
     Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the
     following:
       Jaton Corporation XpressNet
     
     Fujitsu MB86960A/MB86965A, including the following:
       CONTEC C-NET(PC)C Ethernet
       Eiger Labs EPX-10BT
       Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 Ethernet PCMCIA
       Fujitsu Towa LA501 Ethernet
       HITACHI HT-4840-11
       NextCom J Link NC5310
       RATOC REX-5588, REX-9822, REX-4886, REX-R280
       TDK LAK-CD021, LAK-CD021A, LAK-CD021BX
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     Intel InBusiness 10/100 PCI Network Adapter
     Intel PRO/100+ Management Adapter
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 Ethernet interface.
     
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
    -3Com 3C509, 3C529 (MCA), 3C579, 
    +3Com 3C509, 3C529 (MCA), 3C579,
     3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA),
     3C590/592/595/900/905/905B/905C PCI,
     3C556/556B MiniPCI,
     and EISA (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980/3c980B Fast Etherlink XL server adapter
     
     3Com 3cSOHO100-TX OfficeConnect adapter
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards,
     including the following:
       AR-P500 Ethernet card
       Accton EN2212/EN2216/UE2216(OEM)
       Allied Telesis CentreCOM LA100-PCM_V2
       AmbiCom 10BaseT card
       BayNetworks NETGEAR FA410TXC Fast Ethernet
       CNet BC40 adapter
       COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF
       Compex Net-A adapter
       CyQ've ELA-010
       D-Link DE-650/660
       Danpex EN-6200P2
       IO DATA PCLATE
       IBM Creditcard Ethernet I/II
       IC-CARD Ethernet/IC-CARD+ Ethernet
       Linksys EC2T/PCMPC100
       Melco LPC-T
       NDC Ethernet Instant-Link
       National Semiconductor InfoMover NE4100
       Network Everywhere Ethernet 10BaseT PC Card
       Planex FNW-3600-T
       Socket LP-E
       Surecom EtherPerfect EP-427
       TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card
       Telecom Device SuperSocket RE450T
     
     Megahertz X-Jack Ethernet PC-Card CC-10BT
     
     Xircom CreditCard adapters(16bit) and workalikes
         Accton EN2226/Fast EtherCard (16-bit verison)
         Compaq Netelligent 10/100 PC Card
         Intel EtherExpress PRO/100 Mobile Adapter (16-bit verison)
         Xircom Realport card + modem(Ethernet part)
         Xircom CreditCard Ethernet 10/100
         Xircom CreditCard 10Base-T "CreditCard Ethernet Adaptor IIps" (PS-CE2-10)
         Xircom CreditCard Ethernet 10/100 + modem (Ethernet part)
     
     National Semiconductor DP8393X (SONIC) Ethernet cards
         NEC PC-9801-83, -84, -103, and -104
         NEC PC-9801N-25 and -J02R
     
     
     2.3. FDDI
     ---------
     
     DEC FDDI (DEFPA/DEFEA) NICs
     
     
     2.4. ATM
     --------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signalling Protocols
             - The ATM Forum UNI 3.1 signalling protocol
             - The ATM Forum UNI 3.0 signalling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems's proprietary SPANS signalling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     
     2.5. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Advance Asound 100, 110 and Logic ALS120
     Crystal Semiconductor CS461x/462x/428x
     ENSONIQ AudioPCI ES1370/1371
     ESS ES1868, ES1869, ES1879 and ES1888
     ESS Maestro-1, Maestro-2, and Maestro-2E
     ForteMedia fm801
     Gravis UltraSound MAX/PnP
     MSS/WSS Compatible DSPs
     NeoMagic 256AV/ZX
     OPTi 931/82C931
     SoundBlaster, Soundblaster Pro, Soundblaster AWE-32, Soundblaster AWE-64
     Trident 4DWave DX/NX
     VIA Technologies VT82C686A
     Yamaha DS1 and DS1e
     (newpcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 / Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed
     (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes
     NCR WaveLAN/IEEE 802.11
     Cabletron RoamAbout 802.11 DS
     Compaq WL100
     Corega KK Wireless LAN PCC-11
     Laneed Wireless card
     ELECOM Air@Hawk/LD-WL11/PCC
     Farallon Skyline 11Mbps Wireless
     ICOM SL-1100
     Melco Airconnect WLI-PCM-L11
     NEC Wireless Card CMZ-RT-WP
     PLANEX GeoWave/GW-NS110
     TDK LAK-CD011WL
     Note: the ISA versions of these adapters are actually PCMCIA cards
     combined with an ISA to PCMCIA bridge card, so both kinds of devices
     work with the same driver.
     
     Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA,
     PCI and ISA adapters are all supported.
     Cisco Systems Aironet 340 Series (includes 340, 341, and 342 models)
     11Mbps 802.11 wireless NIC
     
     Toshiba Mobile HDD MEHDD20A (Type II)
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
    -Contact freebsd-admin@FreeBSD.org for more details if you'd like to 
    +Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     3.2. CDROM
     ----------
     
     FreeBSD 4.x-RELEASE CDs may be ordered on CDROM from:
     
             BSDi
             4041 Pike Lane, Suite F
             Concord CA  94520
             1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@osd.bsdi.com or http://www.freebsdmall.com.
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 3.0 and there may be some issues affecting you, depending
     of course on your chosen method of upgrading.  There are two popular
     ways of upgrading FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     Please read the UPGRADE.TXT file for more information, preferably
     before beginning an upgrade.
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     If you're tracking the -stable development efforts, you should
     definitely join the -stable mailing list, in order to keep abreast
     of recent developments and changes that may affect the way you
     use and maintain the system:
     
     		freebsd-stable@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgements
     -------------------
     
     FreeBSD represents the cumulative work of many dozens, if not
     hundreds, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     
     Special mention to:
     
             The donors listed at http://www.freebsd.org/handbook/donors.html
     
             And to the many thousands of FreeBSD users and testers all over the
             world, without whom this release simply would not have been possible.
     
     We sincerely hope you enjoy this release of FreeBSD!
     
                             The FreeBSD Project
     
     

    Release Home &footer; diff --git a/es/releases/4.3R/announce.sgml b/es/releases/4.3R/announce.sgml index dfed00f14d..fae8b4c3dc 100644 --- a/es/releases/4.3R/announce.sgml +++ b/es/releases/4.3R/announce.sgml @@ -1,89 +1,91 @@ - - + + %navincludes; %includes; ]> &header;

    Date: Friday, 20 Apr 2001 21:00:00 -0800
    From: "Jordan K. Hubbard" <jkh@freebsd.org>
    To: announce@FreeBSD.org
    Subject: 4.3-RELEASE is now available

    It gives me great pleasure to announce what is probably the finest release produced from the 4.x-STABLE branch to date, FreeBSD 4.3-RELEASE. Following the release of FreeBSD 4.2 in November, 2000, many bugs were fixed, important security issues dealt with, and a reasonable number of new features added. Please see the release notes for more information.

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

    ISO (CD) Images
    ---------------

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

    ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.3-install.iso
    and ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/ISO-IMAGES/4.3-install.iso

    If you can't afford the CDs, are impatient, or just want to use it for evangelism purposes, then by all means download the ISOs, otherwise please do continue to support the FreeBSD project by purchasing one of its official CD releases from BSDi. FreeBSD 4.3-RELEASE can be ordered as a 4 CD set from The FreeBSD Mall from where it will soon be shipping. Each CD sets contains the FreeBSD installation and application package bits for either the x86 or the alpha architecture (each architecture has its own CD set). For a set of distfiles used to build ports in the ports collection, please see also the FreeBSD Toolkit, a 6 CD set containing all such extra bits which we can no longer fit on the 4 CD sets. You can also order by phone, postal mail, FAX or email at:

       BSDi
       4041 Pike Lane, #F
       Concord CA, 94520 USA
       Phone: +1 925 674-0783
       Fax: +1 925 674-0821
       Tech Support: +1 925 603-1234
       Email: orders@wccdrom.com
       WWW: http://www.freebsdmall.com/
     

    Note: Despite the recent acquisition of BSDi's software assets by Wind River, the above information still holds true for the forseeable future and will not change for at least the life-cycle of the FreeBSD 4.3 product. Any changes in the FreeBSD product sales infrastructure will be announced if and as they occur.

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

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

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

    - +

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

    Thanks! - Jordan +&footer; diff --git a/es/releases/4.3R/errata.sgml b/es/releases/4.3R/errata.sgml index b6d18d4284..833ba54854 100644 --- a/es/releases/4.3R/errata.sgml +++ b/es/releases/4.3R/errata.sgml @@ -1,80 +1,81 @@ - - + + %navincludes; %includes; ]> - + &header;
     If you read no other documentation before installing this
     version of FreeBSD, you should at least by all means *READ
     THE ERRATA* for this release so that you don't stumble over
     problems which have already been found and fixed.  This ERRATA.TXT
     file is obviously already out of date by definition, but other
     copies are kept updated on the net and should be consulted as
     the "current errata" for your release.  These other copies of
    -the errata are located at: 
    +the errata are located at:
     
       1. http://www.FreeBSD.org/releases/
     
    -  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT   
    -     (and any sites which keep up-to-date mirrors of this location).          
    +  2. ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT
    +     (and any sites which keep up-to-date mirrors of this location).
     
     Any changes to this file are also automatically emailed to:
     
     	freebsd-current@FreeBSD.org
     
     For all FreeBSD security advisories, see:
     
     	http://www.FreeBSD.org/security/
     
     for the latest security incident information.
     
     ---- Security Advisories:
     
     The vulnerability documented in security advisory FreeBSD-SA-01:39 was
     fixed in FreeBSD 4.3-RELEASE.  The release notes mentioned the fix,
     but made no mention of the security advisory.
     
     A vulnerability in the fts(3) routines (used by applications for
     recursively traversing a filesystem) could allow a program to operate
     on files outside the intended directory hierarchy.  This bug, as well
     as a fix, is described in security advisory FreeBSD-SA-01:40.
     
     A flaw allowed some signal handlers to remain in effect in a child
     process after being exec-ed from its parent.  This allowed an attacker
     to execute arbitrary code in the context of a setuid binary.  More
     details, as well as a fix, are described in security advisory
     FreeBSD-SA-01:42.
     
     A remote buffer overflow in tcpdump(1) could be triggered by sending
     certain packets at a target machine.  More details, as well as a fix,
     can be found in security advisory FreeBSD-SA-01:48.
     
    -A remote buffer overflow in telnetd(8) could result in arbitrary code 
    -running on a target machine.  More details, as well as a fix, can be 
    +A remote buffer overflow in telnetd(8) could result in arbitrary code
    +running on a target machine.  More details, as well as a fix, can be
     found in security advisory FreeBSD-SA-01:49.
     
     ---- System Update Information:
     
     The release note entry for the ESS Maestro-3/Allegro sound driver gave
     an incorrect command for loading the driver via /boot/loader.conf.
     The correct command is:
     
     	snd_maestro3_load="YES"
     
     ssh(1) is no longer SUID root.  The primary manifestation of this
     change is that .shosts authentication may not work "out of the box".
     Both temporary and permanent fixes are described in the FAQ at:
     
     	http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#SSH-SHOSTS
     
     

    Release Home &footer; diff --git a/es/releases/4.3R/notes.sgml b/es/releases/4.3R/notes.sgml index 736058451b..c8a89a664d 100644 --- a/es/releases/4.3R/notes.sgml +++ b/es/releases/4.3R/notes.sgml @@ -1,1275 +1,1276 @@ - - + + %navincludes; %includes; ]> &header;
                                      RELEASE NOTES
                                FreeBSD 4.3-RELEASE version
     
     Any installation failures or crashes should be reported by using the
     send-pr command (those preferring a Web-based interface can also see
     http://www.freebsd.org/send-pr.html).
     
     For information about FreeBSD and the layout of the 4.3-RELEASE directory
     (especially if you're installing from floppies!), see ABOUT.TXT.  For
     installation instructions, see the INSTALL.TXT and HARDWARE.TXT files.
     
     
     Table of contents:
     ------------------
     1. What's new since 4.2-RELEASE
        1.1 KERNEL CHANGES
        1.2 SECURITY FIXES
        1.3 USERLAND CHANGES
     
     2. Supported Configurations
        2.1 Disk Controllers
        2.2 Ethernet cards
        2.3 FDDI
        2.4 ATM
        2.5 Misc
     
     3. Obtaining FreeBSD
        3.1 FTP/Mail
        3.2 CDROM
     
     4. Upgrading from previous releases of FreeBSD
     
     5. Reporting problems, making suggestions, submitting code
     
     6. Acknowledgments
     
     
     1. What's new since 4.2-RELEASE
     -------------------------------
     
     1.1. KERNEL CHANGES
     -------------------
     
     Write combining for crashdumps has been implemented.  This feature
     is useful when write caching is disabled on both SCSI and IDE disks,
     where large memory dumps could take up to an hour to complete.
     
     The pccard driver and pccardc(8) now support multiple "beep types"
     upon card insertion and removal.
     
     The twe(4) driver for 3Ware Escalade controllers has been updated.
     
     The an(4) driver for Cisco Aironet cards now supports Wired Equivalent
     Privacy (WEP) encryption, settable via ancontrol(8).
     
     The wi(4) and an(4) drivers now default to BSS (infrastructure) mode;
     previously the default was ad-hoc mode.
     
     The ray(4) driver, which supports the Webgear Aviator wireless network
     cards, has been committed.  The operation of ray(4) interfaces can be
     modified by raycontrol(8).
     
     Support for the Adaptec FSA family of PCI-SCSI RAID controllers has
     been added, in the form of the aac(4) driver.
     
     Linksys Fast Ethernet PCCARD cards supported by the ed(4) driver now
     require the addition of flag 0x80000 to their config line in
     pccard.conf(5).  This flag is not optional.  These Linksys cards will
     not be recognized without it.
     
     A bug in the ed(4) driver that could cause panics with very short
     packets and BPF or bridging active has been fixed.
     
     A bug in FFS that could cause superblock corruption on very large
     filesystems has been corrected.
     
     The ISO-9660 filesystem now has a hook that supports a loadable
     character conversion routine.  The sysutils/cd9660_unicode port
     contains a set of common conversions.
     
     A new NFS hash function (based on the Fowler/Noll/Vo hash algorithm)
     has been implemented to improve NFS performance by increasing the
     efficiency of the nfsnode hash tables.
     
     The cs(4) driver has been updated.
     
     bridge(4) and dummynet(4) have received some enhancements and bug fixes.
     
     The ahc(4) driver has been updated.  Among various improvements are
     improved compatibility with chips in "RAID Port" mode and systems with
     AAA and ARO cards installed, as well as performance improvements.
     Some bugs were also fixed, including a rare hang on Ultra2/U160
     controllers.
     
     The cd(4) driver now has support for write operations.  This allows
     writing to DVD-RAM, PD and similar drives that probe as CD devices.
     Note that this change affects only random-access writeable devices, not
     sequential-only writeable devices such as CD-R drives, which are
     supported by cdrecord(1).
     
     The "make buildkernel" procedure has changed slightly.  It now gets
     the name of the configuration(s) to build from the KERNCONF variable
     (KERNEL is still valid, but deprecated).  The installed kernel name
     can be changed with the INSTKERNEL variable.  The NO_KERNELCLEAN
     variable prevents cleaning of the kernel build directory (which is now
     done via "make clean", rather than "config -r").
     
     kobj functionality has been merged from -CURRENT to better support
     sound drivers.
     
     Separate drivers for the SoundBlaster 8 and Soundblaster 16 now
     replace an older, unified driver.
     
     A driver for the ESS Maestro-3/Allegro has been added, however due to
     licensing restrictions, it cannot be compiled into the kernel.  To use
     this driver, add the following line to /boot/loader.conf:
     
     	snd_maestro3_load="YES"
     
     The pcm(4) driver now supports the CMedia CMI8338/CMI8738 sound chips,
     as well as the CS4281 sound chip.
     
     When sound modules are built, one can now load all the drivers and
     infrastructure by "kldload snd".
     
     The isp(4) driver has been updated.
     
     ipfilter has been updated to 3.4.16.
     
     ipfw(8) has a new feature ("me") that allows for packet matching on
     interfaces with dynamically-changing IP addresses.
     
     TCP has received some bug fixes for its delayed ACK behavior.
     
     TCP now supports the NewReno modification to the TCP Fast Recovery
     algorithm.  This behavior can be controlled via the
     net.inet.tcp.newreno sysctl variable.
     
     TCP now uses a more aggressive timeout for initial SYN segments; this
     allows initial connection attempts to be dropped much faster.
     
     ICMP UNREACH_FILTER_PROHIB messages can now RST TCP connections in the
     SYN_SENT state if the correct sequence numbers are sent back, as
     controlled by the net.inet.tcp.icmp_may_rst sysctl.
     
     A new sysctl net.inet.ip.check_interface, which is off by default,
     causes IP to verify that an incoming packet arrives on an interface
     that has an address matching the packet's destination address.
     
     The ata(4) driver has been updated.
     
     To provide more flexible configuration, the various options for the
     ata(4) driver are now boot loader tunables, rather than kernel
     configure-time options.
     
     The ata(4) driver now supports ATA66 and ATA100 mode on Acer Alladin
     chipsets.
     
     kqueue(2) has been extended to the device layer, and has also received
     some bug fixes.
     
     Some signal-handling fixes for Linux have been added, which improves
     compatibility with signal-intensive programs running under Linux
     emulation.
     
     The ida disk driver now has crashdump support.
     
     The mly(4) driver has received some changes in queueing, concurrency
     improvements, and stability fixes.
     
     Several minor bugs have been fixed in the VLAN networking code.
     
     Vinum has received some bugfixes.
     
     Changes specific to Alpha architecture:
     
        A bug in the machine-dependent code for the AlphaServer 1000 and 1000A
        has been fixed; it had caused only EV4-equipped AS1000 and EV5-equipped
        AS1000A systems to work.
     
        The API UP1100 mainboard has been verified to work correctly.
     
        The API CS20 1U high server has been verified to work correctly.
     
        AlphaServer 2100A ("Lynx") support has been added.
     
        The AlphaServer 4000 and 4100 refuse to boot from the FreeBSD install
        floppy or install CDROM.  The workaround is to "dd" the 2.88MB floppy image
        onto a hard disk and boot the installer from it. Once sysinstall(8) is
        running, a normal installation can be performed. Similar problems have
        been observed on the AlphaServer 1200 and 8400.
     
        For AlphaServer 4100 adapter cards with PCI bridge chips might cause
        trouble. In addition, the capability of booting from an adapter might be
        influenced by the placement of the adapter card on a specific PCI hose.
        Please use 'send-pr' to report any problems you might encounter in this area.
     
     
     1.2. SECURITY FIXES
     -------------------
     
     Some fixes were applied to the Kerberos IV implementation related to
     environment variables, a possible buffer overrun, and overwriting
     ticket files.
     
     telnet(1) now does a better job of sanitizing its environment.
     
     Several vulnerabilities in procfs(4) were fixed (see security advisory
     FreeBSD-SA-00:77).
     
     A bug in ipfw(8) and ip6fw(8) in which inbound TCP segments could
     incorrectly be treated as being part of an "established" connection
     has been fixed (see security advisory FreeBSD-SA-01:08).
     
     A bug in crontab(8) that could allow users to read any file on the
     system in valid crontab(5) syntax has been fixed (see security
     advisory FreeBSD-SA-01:09).
     
     A vulnerability in inetd(8) that could allow read-access to the
     initial 16 bytes of wheel-accessible files has been fixed (see
     security advisory FreeBSD-SA-01:11).
     
     A bug in periodic(8) that used insecure temporary files has been
     corrected (see security advisory FreeBSD-SA-01:12).
     
     To fix a remotely-exploitable buffer overflow, BIND has been updated
     to 8.2.3 (see security advisory FreeBSD-SA-01:18).
     
     OpenSSH now has code to prevent (instead of just mitigating through
     connection limits) an attack that can lead to guessing the server key
     (not host key) by regenerating the server key when an RSA failure is
     detected (see security advisory FreeBSD-SA-01:24).
     
     A bug in ICMP that could cause an attacker to disrupt TCP and UDP
     "sessions" has been corrected.
     
     A bug in timed(8), which caused it to crash if sent certain malformed
     packets, has been corrected (see security advisory FreeBSD-SA-01:28).
     
     A bug in rwhod(8), which caused it to crash if sent certain malformed
     packets, has been corrected (see security advisory FreeBSD-SA-01:29).
     
     A security hole in FreeBSD's FFS and EXT2FS implementations, which
     allowed a race condition that could cause users to have unauthorized
     access to data, has been fixed (see security advisory FreeBSD-SA-01:30).
     
     A remotely-exploitable vulnerability in ntpd(8) has been closed (see
     security advisory FreeBSD-SA-01:31).
     
     A security hole in IPFilter's fragment cache has been closed (see
     security advisory FreeBSD-SA-01:32).
     
     Buffer overflows in glob(3), which could cause arbitrary code to be
     run on an FTP server, have been closed.  In addition, to prevent some
     forms of DOS attacks, glob(3) now allows specification of a limit on
     the number of pathname matches it will return.  ftpd(8) now uses this
     feature (see security advisory FreeBSD-SA-01:33).
     
     Initial sequence numbers in TCP are more thoroughly randomized, using
     an algorithm obtained from OpenBSD.
     
     A number of programs have had output formatting strings corrected so
     as to reduce the risk of vulnerabilities.
     
     A number of programs that use temporary files now do so more securely.
     
     
     1.3. USERLAND CHANGES
     ---------------------
     
     newfs(1) now implements write combining, which can make creation of
     new filesystems up to seven times faster.
     
     A number of buffer overflows in config(8) have been fixed.
     
     Binutils have been upgraded to 2.10.1.
     
     OpenSSL has been upgraded to 0.9.6.
     
     OpenSSL now has support for machine-dependent ASM optimizations,
     activated by the new CPUTYPE/MACHINE_CPU Makefile variables.
     
     file(1) has been contribify-ed, and imported as version 3.33.
     
     groff(1) and its related utilities have been updated to FSF version
     1.16.1.
     
     indent(1) has gained some new formatting options.
     
     sysinstall(8) now uses some more intuitive defaults thanks to some new
     dialog support functions.
     
     sysinstall(8) now properly preserves /etc/mail during a binary
     upgrade.
     
     The default root partition in sysinstall(8) is now 100MB.
     
     libdisk can now do install-time configuration of the i386 boot0 boot
     loader.
     
     rm(1) -v now displays the entire pathname of a file being
     removed.
     
     lpr(1), lpq(1), and lpd(8) have received a few minor enhancements.
     
     OpenSSH has been upgraded to 2.3.0.  This version adds support for the
     Rijndael encryption algorithm.
     
     Kerberos compatability has been added to OpenSSH.
     
     OpenSSH has been modified to be more resistant to traffic analysis by
     requiring that "non-echoed" characters are still echoed back in a null
     packet, as well as by padding passwords sent so as not to hint at
     password lengths.
     
     syslogd(8) now supports a "LOG_CONSOLE" facility (disabled by
     default), which can be used to log /dev/console output.
     
     cdcontrol(1) now uses the CDROM environment variable to pick a default
     device.
     
     All packages and ports now contain an "origin" directive, which makes
     it easier for programs like pkg_version(1) to determine the directory
     from which a package was built.
     
     pkg_info(1) can now accept a -g flag for verifying an installed
     package against its recorded checksums (to see if it's been modified
     post-installation).  Naturally, this mechanism is only as secure as
     the contents of /var/db/pkg if it's to be used for auditing
     purposes.
     
     pkg_create(1) and pkg_add(1) can now work with packages that have
     been compressed using bzip2(1).  pkg_add(1) will use the
     PACKAGEROOT environment variable to determine a mirror site for new
     packages.
     
     pkg_info(1) now supports globbing against names of installed packages.
     The -G option disables this behavior, and the -x option causes regular
     expression matching instead of shell globbing.
     
     pkg_sign(1) and pkg_check(1) have been added to digitally sign and
     verify the signatures on binary package files.
     
     pkg_update(1), a utility to update installed packages and update their
     dependencies, has been added.
     
     pkg_delete(1) now can perform glob/regexp matching of package names.
     In addition, it supports the -a option for removing all packages and
     the -i option for rm(1)-style interactive confirmation.
     
     pkg_create(1) now records dependencies in dependency order rather than
     in the order specified on the command line.  This improves the
     functioning of "pkg_add -r".
     
     pkg_version(1) now has a version number comparison routine that
     corresponds to the Porters Handbook.  It also has a -t option for
     testing address comparisons.
     
     awk has been upgraded from gawk-3.0.4 to gawk-3.0.6.  This fixes a number
     of non-critical bugs and includes a few performance tweaks.
     
     Shortly after the receipt of a SIGINFO signal (normally control-T from
     the controlling tty), fsck(8) will now output a line indicating the
     current phase number and progress information relevant to the current
     phase.
     
     pwd(1) can now double as realpath(1), a program to resolve pathnames
     to their underlying physical paths.
     
     gcc(1) has been updated to 2.95.3.
     
     gcc(1) now uses a unified libgcc rather than a separate one for threaded
     and non-threaded programs.  /usr/lib/libgcc_r.a can be removed.
     
     config(8) is now better about converting various warnings that should
     have been errors into actual fatal errors with an exit code.  This
     ensures that that "make buildkernel" doesn't quietly ignore them and
     build a bogus kernel without a human to read the errors.
     
     In /etc/ssh/sshd_config, the ConnectionsPerPeriod parameter has been
     deprecated in favor of MaxStartups.
     
     find(1) now takes the -empty flag, which returns true if a file or
     directory is empty.
     
     find(1) now takes the -iname and -ipath primaries for case-insensitive
     matches, and the -regexp and -iregexp primaries for regular-expression
     matches.  The -E flag now enables extended regular expressions.
     
     ldconfig(8) now checks directory ownerships and permissions for
     greater security; these checks can be disabled with the -i
     flag.
     
     sendmail(8) and associated utilities upgraded from version 8.11.1 to
     version 8.11.3.  See /usr/src/contrib/sendmail/RELEASE_NOTES for more
     information.
     
     New make.conf options: SENDMAIL_MC and SENDMAIL_ADDITIONAL_MC.  See
     /etc/defaults/make.conf for more information.
     
     The Makefile in /etc/mail now supports: the new SENDMAIL_MC make.conf
     option; the ability to build .cf files from .mc files; generalized map
     rebuilding; rebuilding the aliases file; and the ability to stop, start,
     and restart sendmail.
     
     vidcontrol(1) now accepts a -g parameter to select custom text
     geometry in the VESA_800x600 raster text mode.
     
     The rfork_thread(3) library call has been added as a helper function
     to rfork(2).  Using this function should avoid the need to implement
     complex stack swap code.
     
     The compat3x distribution has been updated to include libraries
     present in FreeBSD 3.5.1-RELEASE.
     
     gperf has been updated to 2.7.2.
     
     Catching up with most other network utilities in the base system,
     lpr(1), lpd(8), syslogd(8), and logger(1) are now all IPv6-capable.
     
     When requested to delete multiple packages, pkg_delete(1) will now
     attempt to remove them in dependency order rather than the order
     specified on the command line.
     
     burncd(8) now supports a -m option for multisession mode (the default
     behavior now is to close disks as single-session).  A -l option to
     take a list of image files from a filename was also added; "-" can be
     used as a filename for stdin.
     
     tar(1) now supports the TAR_RSH variable, principally to enable the
     use of ssh(1) as a transport.
     
     Bugs in make(1), among which include broken null suffix behavior, bad
     assumptions about current directory permissions, and potential buffer
     overflows, have been fixed.
     
     The new CPUTYPE make.conf variable controls the compilation of
     processor-specific optimizations in various pieces of code such as
     OpenSSL.
     
     Boot-time syscons configuration was moved to a machine-independent
     rc.syscons.
     
     login(1) now exports environment variables set by PAM modules.
     
     ipfstat(8) now supports the -t option to turn on a top(1)-like
     display.
     
     tftpd(8) now takes the -c and -C options, which allow the server to
     chroot(2) based on the IP address of the connecting client.  tftp(1)
     and tftpd(8) can now transfer files larger than 65535 blocks.
     
     The lastlogin(1) utility, which prints the last login time of each
     user, has been imported from NetBSD.
     
     /usr/src/share/examples/BSD_daemon/ now contains a scalable Beastie
     graphic.
     
     bc has been updated from 1.04 to 1.06.
     
     savecore(8) now supports a -k option to prevent clearing a crash dump
     after saving it.  It also attempts to avoid writing large stretches of
     zeros to crash dump files to save space and time.
     
     tcsh has been updated to version 6.10.
     
     The default value for the CVS_RSH variable (used by cvs(1)) is now
     ssh, rather than rsh.
     
     disklabel(8) now supports partition sizes expressed in kilobytes,
     megabytes, or gigabytes, in addition to sectors.
     
     Kerberos IV has been updated to 1.0.5.
     
     Heimdal has been updated to 0.3e.
     
     dump(8) now supports inheritance of the "nodump" flag down a
     hierarchy.
     
     The ISC DHCP client has been updated to 2.0pl5.
     
     stty(1) now has support for an "erase2" control character, so that
     both "delete" and "backspace" can be used to erase characters.
     
     split(1) now has the ability to split a file longer than 2GB.
     
     units(1) has received some updates and bugfixes.
     
     netstat(1) now keeps track of input and output packets on a
     per-address basis for each interface.
     
     netstat(1) now has a -W flag that tells it not to truncate addresses,
     even if they're too long for the column they're printed in.
     
     sockstat(1) now has -c and -l flags for listing connected and
     listening sockets, respectively.
     
     Many manual pages were improved, both in terms of their formatting
     markup and in their content.
     
     "lprm -" now works for remote printer queues.
     
     mergemaster(8) now sources an /etc/mergemaster.rc file and also
     prompts the user to run recommended commands (such as "newaliases") as
     needed.
     
     ftpd(8) now supports a -r flag for read-only mode and a -E flag to
     disable EPSV.  It also has some fixes to reduce information leakage
     and the ability to specify compile-time port ranges.
     
     rc(8) now has an framework for handling dependencies between
     rc.conf(5) variables.
     
     The default TCP port range used by libfetch for passive FTP retrievals
     has changed; this affects the behavior of fetch(1), which has gained the
     -U option to restore the old behavior.
     
     portmap(8) now takes a -h option to indicate the IP addresses to which
     it should bind.  This option may be specified multiple times and is
     typically necessary for multi-homed hosts.
     
     GNATS has been updated to 3.113.
     
     tail(1) now has the ability to work on files longer than 2GB.
     
     
     2. Supported Configurations
     ---------------------------
     FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA and PCI
     bus based PC's, ranging from 386sx to Pentium class machines (though the
     386sx is not recommended).  Support for generic IDE drive
     configurations, various SCSI controller, network and serial cards is
     also provided.
     
     What follows is a list of all peripherals currently known to work with
     FreeBSD.  Other configurations may also work, we have simply not as yet
     received confirmation of this.
     
     
     2.1. Disk Controllers
     ---------------------
     IDE
     ATA
     
     Adaptec 1535 ISA SCSI controllers
     Adaptec 154x series ISA SCSI controllers
     Adaptec 164x series MCA SCSI controllers
     Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
     Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series
     EISA/VLB/PCI SCSI controllers.
     Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers.
     Adaptec 1510 series ISA SCSI controllers (not for bootable devices)
     Adaptec 152x series ISA SCSI controllers
     Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x
     and SoundBlaster SCSI cards.
     
     Adaptec 2100S, 2400A, 3200S, and 3400S SCSI RAID controllers.
     
     Adaptec FSA family RAID controllers:
         Adaptec AAC-2622
         Adaptec AAC-364
         Adaptec AAC-3642
         Dell PERC 2/QC
         Dell PERC 2/Si
         Dell PERC 3/Di
         Dell PERC 3/QC
         Dell PERC 3/Si
         HP NetRAID-4M
     
     AdvanSys SCSI controllers (all models).
     
     BusLogic MultiMaster controllers:
     
     [ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ]
     
     BusLogic MultiMaster "W" Series Host Adapters:
         BT-948, BT-958, BT-958D
     BusLogic MultiMaster "C" Series Host Adapters:
         BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C,
         BT-540CF
     BusLogic MultiMaster "S" Series Host Adapters:
         BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A,
         BT-542B
     BusLogic MultiMaster "A" Series Host Adapters:
         BT-742A, BT-542B
     
     AMI FastDisk controllers that are true BusLogic MultiMaster clones are also
     supported.
     
     The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F
     Microchannel (MCA) bus adapters are also supported.
     
     DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and
     SmartRAID IV SCSI/RAID controllers are supported.
     
     DPT SmartRAID V and VI SCSI RAID controllers:
         PM1554, PM2554, PM2654, PM2865, PM2754, PM3755, PM3757
     
     AMI MegaRAID Express and Enterprise family RAID controllers:
         MegaRAID Series 418
         MegaRAID Enterprise 1200 (Series 428)
         MegaRAID Enterprise 1300 (Series 434)
         MegaRAID Enterprise 1400 (Series 438)
         MegaRAID Enterprise 1500 (Series 467)
         MegaRAID Enterprise 1600 (Series 471)
         MegaRAID Elite 1500 (Series 467)
         MegaRAID Elite 1600 (Series 493)
         MegaRAID Express 100 (Series 466WS)
         MegaRAID Express 200 (Series 466)
         MegaRAID Express 300 (Series 490)
         MegaRAID Express 500 (Series 475)
         Dell PERC
         Dell PERC 2/SC
         Dell PERC 2/DC
         Dell PERC 3/DCL
         HP NetRAID-1si
         HP NetRAID-3si
         HP Embedded NetRAID
     Booting from these controllers is supported.
     
     Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x
     firmware:
         DAC960P
         DAC960PD
         DAC960PDU
         DAC960PL
         DAC960PJ
         DAC960PG
         AcceleRAID 150
         AcceleRAID 250
         eXtremeRAID 1100
     Booting from these controllers is supported. EISA adapters are not
     supported.
     
     Mylex PCI to SCSI RAID controllers with 6.x firmware:
         AcceleRAID 160
         AcceleRAID 170
         AcceleRAID 352
         eXtremeRAID 2000
         eXtremeRAID 3000
     Compatible Mylex controllers not listed should work, but have not been
     verified.
     
     3ware Escalade ATA RAID controllers.  All members of the 5000,
     6000, and 7000 series are supported.
     
     SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a,
     53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers:
             ASUS SC-200
             Data Technology DTC3130 (all variants)
     	Diamond FirePort (all)
             NCR cards (all)
             Symbios cards (all)
             Tekram DC390W, 390U and 390F
             Tyan S1365
     
     NCR 53C500 based PC-Card SCSI host adapters:
         IO DATA PCSC-DV
         KME KXLC002(TAXAN ICD-400PN, etc.), KXLC004
         Macnica Miracle SCSI-II mPS110
         Media Intelligent MSC-110, MSC-200
         NEC PC-9801N-J03R
         New Media Corporation BASICS SCSI
         Qlogic Fast SCSI
         RATOC REX-9530, REX-5572 (as SCSI only)
     
     TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters:
         Future Domain SCSI2GO
         IBM SCSI PCMCIA Card
         ICM PSC-2401 SCSI
         Melco IFC-SC
         RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A
     
     Qlogic Controllers and variants:
         Qlogic 1020, 1040 SCSI and Ultra SCSI host adapters
         Qlogic 1240 dual Ultra SCSI controllers
         Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD controllers
         Qlogic 12160 Ultra3 LVD controllers
         Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI controllers
         Performance Technology SBS440 ISP1000 variants
         Performance Technology SBS450 ISP1040 variants
         Performance Technology SBS470 ISP2100 variants
         Antares Microsystems P-0033 ISP2100 variants
     
     DTC 3290 EISA SCSI controller in 1542 emulation mode.
     
     Workbit Ninja SCSI-3 based PC-Card SCSI host adapters:
         Alpha-Data AD-PCS201
         IO DATA CBSC16
     
     With all supported SCSI controllers, full support is provided for
     SCSI-I & SCSI-II peripherals, including hard disks, optical disks,
     tape drives (including DAT and 8mm Exabyte), medium changers, processor
     target devices and CDROM drives.  WORM devices that support CDROM commands
     are supported for read-only access by the CDROM driver.  WORM/CD-R/CD-RW
     writing support is provided by cdrecord, which is in the ports tree.
     
     The following CD-ROM type systems are supported at this time:
     (cd)    SCSI interface (also includes ProAudio Spectrum and
             SoundBlaster SCSI)
     (matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary
             interface (562/563 models)
     (scd)   Sony proprietary interface (all models)
     (acd)   ATAPI IDE interface
     
     The following drivers were supported under the old SCSI subsystem, but are
     NOT YET supported under the new CAM SCSI subsystem:
     
       NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
     
       UltraStor 14F, 24F and 34F SCSI controllers.
     
       Seagate ST01/02 SCSI controllers.
     
       Future Domain 8xx/950 series SCSI controllers.
     
       WD7000 SCSI controller.
     
       [ Note:  There is work-in-progress to port the UltraStor driver to
         the new CAM SCSI framework, but no estimates on when or if it will
         be completed. ]
     
     Unmaintained drivers, they might or might not work for your hardware:
     
       (mcd)   Mitsumi proprietary CD-ROM interface (all models)
     
     
     2.2. Ethernet cards
     -------------------
     
     Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec
     AIC-6915 Fast Ethernet controller chip, including the following:
       ANA-62011 64-bit single port 10/100baseTX adapter
       ANA-62022 64-bit dual port 10/100baseTX adapter
       ANA-62044 64-bit quad port 10/100baseTX adapter
       ANA-69011 32-bit single port 10/100baseTX adapter
       ANA-62020 64-bit single port 100baseFX adapter
     
     Allied-Telesis AT1700 and RE2000 cards
     
     Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2
     chipsets, including the following:
       3Com 3c985-SX (Tigon 1 and 2)
       Alteon AceNIC 1000baseSX (Tigon 1 and 2)
       Alteon AceNIC 1000baseT (Tigon 2)
       DEC/Compaq EtherWORKS 1000
       Farallon PN9000SX
       NEC Gigabit Ethernet
       Netgear GA620 (Tigon 2)
       Netgear GA620T (Tigon 2, 1000baseT)
       Silicon Graphics Gigabit Ethernet
     
     AMD PCnet/PCI (79c970 & 53c974 or 79c974)
     AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO,
     PCnet/Home, and HomePNA.
     
     SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E,
     WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT
     based clones.  SMC Elite Ultra.  SMC Etherpower II.
     
     RealTek 8129/8139 Fast Ethernet NICs including the following:
       Allied Telesyn AT2550
       Allied Telesyn AT2500TX
       Genius GF100TXR (RTL8139)
       NDC Communications NE100TX-E
       OvisLink LEF-8129TX
       OvisLink LEF-8139TX
       Netronix Inc. EA-1210 NetEther 10/100
       KTX-9130TX 10/100 Fast Ethernet
       Accton "Cheetah" EN1207D (MPX 5030/5038; RealTek 8139 clone)
       SMC EZ Card 10/100 PCI 1211-TX
     
     Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX
       NetGear FA310-TX Rev. D1
       Matrox FastNIC 10/100
       Kingston KNE110TX
     
     Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs
       Accton EN1217 (98715A)
       Adico AE310TX (98715A)
       Compex RL100-TX
       CNet Pro120A (98713 or 98713A)
       CNet Pro120B (98715)
       NDC Communications SFA100A (98713A)
       SVEC PN102TX (98713)
     
     Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following:
       LinkSys EtherFast LNE100TX Version 2
     
     Winbond W89C840F Fast Ethernet NICs including the following:
       Trendware TE100-PCIE
     
     VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet
     NICs including the following:
       Hawking Technologies PN102TX
       D-Link DFE-530TX
       AOpen/Acer ALN-320
     
     Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs
     
     Sundance Technologies ST201 PCI Fast Ethernet NICs including
     the following:
       D-Link DFE-550TX
     
     SysKonnect SK-984x PCI Gigabit Ethernet cards including the following:
       SK-9841 1000baseLX single mode fiber, single port
       SK-9842 1000baseSX multimode fiber, single port
       SK-9843 1000baseLX single mode fiber, dual port
       SK-9844 1000baseSX multimode fiber, dual port
     
     Texas Instruments ThunderLAN PCI NICs, including the following:
       Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port
       Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP
       Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC
       Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP
       Racore 8165 10/100baseTX
       Racore 8148 10baseT/100baseTX/100baseFX multi-personality
     
     ADMtek Inc. AL981-based PCI Fast Ethernet NICs
     ADMtek Inc. AN985-based PCI Fast Ethernet NICs
     ADMtek Inc. AN986-based USB Ethernet NICs including the following:
       LinkSys USB100TX
       Billionton USB100
       Melco Inc. LUA-TX
       D-Link DSB-650TX
       SMC 2202USB
     
     CATC USB-EL1210A-based USB Ethernet NICs including the following:
       CATC Netmate
       CATC Netmate II
       Belkin F5U111
     
     Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including
     the following:
       LinkSys USB10T
       Entrega NET-USB-E45
       Peracom USB Ethernet Adapter
       3Com 3c19250
       ADS Technologies USB-10BT
       ATen UC10T
       Netgear EA101
       D-Link DSB-650
       SMC 2102USB
       SMC 2104USB
       Corega USB-T
     
     ASIX Electronics AX88140A PCI NICs, including the following:
       Alfa Inc. GFC2204
       CNet Pro110B
     
     DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc)
     
     DEC/Intel 21143 based Fast Ethernet NICs, including the following:
       DEC DE500-BA
       Compaq Presario 7900 series built-in Ethernet
       D-Link DFE-570TX
       Kingston KNE100TX
       LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet
     
     Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the
     following:
       Jaton Corporation XpressNet
     
     Fujitsu MB86960A/MB86965A, including the following:
       CONTEC C-NET(PC)C Ethernet
       Eiger Labs EPX-10BT
       Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 Ethernet PCMCIA
       Fujitsu Towa LA501 Ethernet
       HITACHI HT-4840-11
       NextCom J Link NC5310
       RATOC REX-5588, REX-9822, REX-4886, REX-R280
       TDK LAK-CD021, LAK-CD021A, LAK-CD021BX
     
     HP PC Lan+ cards (model numbers: 27247B and 27252A).
     
     Intel EtherExpress 16
     Intel EtherExpress Pro/10
     Intel EtherExpress Pro/100B PCI Fast Ethernet
     Intel InBusiness 10/100 PCI Network Adapter
     Intel PRO/100+ Management Adapter
     
     Isolan AT 4141-0 (16 bit)
     Isolink 4110     (8 bit)
     
     Novell NE1000, NE2000, and NE2100 Ethernet interface.
     
     PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000,
     Winbond W89C940, Surecom NE-34, VIA VT86C926.
     
     3Com 3C501 cards
     
     3Com 3C503 Etherlink II
     
     3Com 3c505 Etherlink/+
     
     3Com 3C507 Etherlink 16/TP
     
     3Com 3C509, 3C529 (MCA), 3C579,
     3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA),
     3C590/592/595/900/905/905B/905C PCI,
     3C556/556B MiniPCI,
     and EISA (Fast) Etherlink III / (Fast) Etherlink XL
     
     3Com 3c980/3c980B Fast Etherlink XL server adapter
     
     3Com 3cSOHO100-TX OfficeConnect adapter
     
     Crystal Semiconductor CS89x0-based NICs, including:
       IBM Etherjet ISA
     
     NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards,
     including the following:
       AR-P500 Ethernet card
       Accton EN2212/EN2216/UE2216(OEM)
       Allied Telesis CentreCOM LA100-PCM_V2
       AmbiCom 10BaseT card
       BayNetworks NETGEAR FA410TXC Fast Ethernet
       CNet BC40 adapter
       COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD
       Compex Net-A adapter
       CyQ've ELA-010
       D-Link DE-650/660
       Danpex EN-6200P2
       ELECOM Laneed LD-CDL/TX
       IO DATA PCLA/TE, PCET/TX, PCET/TX-R
       IBM Creditcard Ethernet I/II
       IC-CARD Ethernet/IC-CARD+ Ethernet
       Linksys EC2T/PCMPC100,EtherFast 10/100 PC Card (PCMPC100,V2,V3)
       Melco LPC-T/LPC2-T/LPC2-TX/LPC3-TX/LPC3-CLX
       NDC Ethernet Instant-Link
       National Semiconductor InfoMover NE4100
       Network Everywhere Ethernet 10BaseT PC Card
       Planex FNW-3600-T
       Socket LP-E
       Surecom EtherPerfect EP-427
       TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card
       Telecom Device SuperSocket RE450T
     
     Megahertz X-Jack Ethernet PC-Card CC-10BT
     
     Xircom CreditCard adapters(16bit) and workalikes
         Accton EN2226/Fast EtherCard (16-bit verison)
         Compaq Netelligent 10/100 PC Card
         Intel EtherExpress PRO/100 Mobile Adapter (16-bit verison)
         Xircom 10/100 Network PC Card adapter
         Xircom Realport card + modem(Ethernet part)
         Xircom CreditCard Ethernet 10/100
         Xircom CreditCard 10Base-T "CreditCard Ethernet Adaptor IIps" (PS-CE2-10)
         Xircom CreditCard Ethernet 10/100 + modem (Ethernet part)
     
     National Semiconductor DP8393X (SONIC) Ethernet cards
         NEC PC-9801-83, -84, -103, and -104
         NEC PC-9801N-25 and -J02R
     
     
     2.3. FDDI
     ---------
     
     DEC FDDI (DEFPA/DEFEA) NICs
     
     
     2.4. ATM
     --------
     
        o ATM Host Interfaces
             - FORE Systems, Inc. PCA-200E ATM PCI Adapters
             - Efficient Networks, Inc. ENI-155p ATM PCI Adapters
     
        o ATM Signaling Protocols
             - The ATM Forum UNI 3.1 signaling protocol
             - The ATM Forum UNI 3.0 signaling protocol
             - The ATM Forum ILMI address registration
             - FORE Systems' proprietary SPANS signaling protocol
             - Permanent Virtual Channels (PVCs)
     
        o IETF "Classical IP and ARP over ATM" model
             - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5"
             - RFC 1577, "Classical IP and ARP over ATM"
             - RFC 1626, "Default IP MTU for use over ATM AAL5"
             - RFC 1755, "ATM Signaling Support for IP over ATM"
             - RFC 2225, "Classical IP and ARP over ATM"
             - RFC 2334, "Server Cache Synchronization Protocol (SCSP)"
             - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt,
                     "A Distributed ATMARP Service Using SCSP"
     
        o ATM Sockets interface
     
     
     2.5. Misc
     ---------
     
     AST 4 port serial card using shared IRQ.
     
     ARNET 8 port serial card using shared IRQ.
     ARNET (now Digiboard) Sync 570/i high-speed serial.
     
     Boca BB1004 4-Port serial card (Modems NOT supported)
     Boca IOAT66 6-Port serial card (Modems supported)
     Boca BB1008 8-Port serial card (Modems NOT supported)
     Boca BB2016 16-Port serial card (Modems supported)
     
     Comtrol Rocketport card.
     
     Cyclades Cyclom-y Serial Board.
     
     STB 4 port card using shared IRQ.
     
     SDL Communications Riscom/8 Serial Board.
     SDL Communications RISCom/N2 and N2pci high-speed sync serial boards.
     
     Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64,
     ONboard 4/16 and Brumby.
     
     Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules.
     
     Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound
     and Roland MPU-401 sound cards. (snd driver)
     
     Advance Asound 100, 110 and Logic ALS120
     C-Media CMI-8x38
     Crystal Semiconductor CS461x/462x/428x
     Crystal Semiconductor CS4281
     ENSONIQ AudioPCI ES1370/1371
     ESS ES1868, ES1869, ES1879 and ES1888
     ESS Maestro-1, Maestro-2, and Maestro-2E
     ESS Maestro-3/Allegro
     ForteMedia fm801
     Gravis UltraSound MAX/PnP
     MSS/WSS Compatible DSPs
     NeoMagic 256AV/ZX
     OPTi 931/82C931
     SoundBlaster, Soundblaster Pro, Soundblaster AWE-32, Soundblaster AWE-64
     Trident 4DWave DX/NX
     VIA Technologies VT82C686A
     Yamaha DS1 and DS1e
     (newpcm driver)
     
     Connectix QuickCam
     Matrox Meteor Video frame grabber
     Creative Labs Video Spigot frame grabber
     Cortex1 frame grabber
     Hauppauge Wincast/TV boards (PCI)
     STB TV PCI
     Intel Smart Video Recorder III
     Various Frame grabbers based on Brooktree Bt848 / Bt878 chip.
     
     HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives.
     
     PS/2 mice
     
     Standard PC Joystick
     
     X-10 power controllers
     
     GPIB and Transputer drivers.
     
     Genius and Mustek hand scanners.
     
     Xilinx XC6200 based reconfigurable hardware cards compatible with
     the HOT1 from Virtual Computers (www.vcc.com)
     
     Support for Dave Mills experimental Loran-C receiver.
     
     Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed
     (2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes
     3COM 3crwe737A AirConnect Wireless LAN PC Card
     Cabletron RoamAbout 802.11 DS
     Compaq WL100
     Corega KK Wireless LAN PCC-11, PCCA-11
     Laneed Wireless card
     ELECOM Air@Hawk/LD-WL11/PCC
     Farallon Skyline 11Mbps Wireless
     ICOM SL-1100
     Intel PRO/Wireless 2011 LAN PC Card
     IO Data WN-B11/PCM
     Melco Airconnect WLI-PCM-L11
     NCR WaveLAN/IEEE 802.11
     NEC Wireless Card CMZ-RT-WP, PC-WL/11C, PK-WL001
     PLANEX GeoWave/GW-NS110
     TDK LAK-CD011WL
     Note: the ISA versions of these adapters are actually PCMCIA cards
     combined with an ISA to PCMCIA bridge card, so both kinds of devices
     work with the same driver.
     
     Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA,
     PCI and ISA adapters are all supported.
     Cisco Systems Aironet 340 Series (includes 340, 341, and 342 models)
     11Mbps 802.11 wireless NIC
     
     Webgear Aviator 2.4GHz wireless adapters.
     
     Toshiba Mobile HDD MEHDD20A (Type II)
     
     Panasonic Flash ATA BN-040ABP3
     
     Hewlett Packard M820e (CD-writer)
     
     3. Obtaining FreeBSD
     --------------------
     
     You may obtain FreeBSD in a variety of ways:
     
     
     3.1. FTP/Mail
     -------------
     
     You can ftp FreeBSD and any or all of its optional packages from
     `ftp.freebsd.org' - the official FreeBSD release site.
     
     For other locations that mirror the FreeBSD software see the file
     MIRROR.SITES.  Please ftp the distribution from the site closest (in
     networking terms) to you.  Additional mirror sites are always welcome!
     Contact freebsd-admin@FreeBSD.org for more details if you'd like to
     become an official mirror site.
     
     If you do not have access to the Internet and electronic mail is your
     only recourse, then you may still fetch the files by sending mail to
     `ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message
     to get more information on how to fetch files using this mechanism.
     Please do note, however, that this will end up sending many *tens of
     megabytes* through the mail and should only be employed as an absolute
     LAST resort!
     
     
     3.2. CDROM
     ----------
     
     FreeBSD 4.x-RELEASE CDs may be ordered on CDROM from:
     
             BSDi / Walnut Creek CDROM
             4041 Pike Lane, Suite D
             Concord CA  94520
             USA
             +1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX)
     
     Or via the Internet from orders@cdrom.com or http://www.cdrom.com.
     Their current catalog can be obtained via ftp from:
     
             ftp://ftp.cdrom.com/cdrom/catalog
     
     Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription.
     FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a
     FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely
     separate).  With a subscription, you will automatically receive updates as
     they are released.  Your credit card will be billed when each disk is
     shipped and you may cancel your subscription at any time without further
     obligation.
     
     Shipping (per order not per disc) is $5 in the US, Canada or Mexico
     and $9.00 overseas.  They accept Visa, Mastercard, Discover, American
     Express or checks in U.S. Dollars and ship COD within the United
     States.  California residents please add 8.25% sales tax.
     
     Should you be dissatisfied for any reason, the CD comes with an
     unconditional return policy.
     
     
     4. Upgrading from previous releases of FreeBSD
     ----------------------------------------------
     
     If you're upgrading from a previous release of FreeBSD, most likely
     it's 3.0 and there may be some issues affecting you, depending
     of course on your chosen method of upgrading.  There are two popular
     ways of upgrading FreeBSD distributions:
     
             o Using sources, via /usr/src
             o Using sysinstall's (binary) upgrade option.
     
     Please read the UPGRADE.TXT file for more information, preferably
     before beginning an upgrade.
     
     
     5. Reporting problems, making suggestions, submitting code.
     -----------------------------------------------------------
     Your suggestions, bug reports and contributions of code are always
     valued - please do not hesitate to report any problems you may find
     (preferably with a fix attached, if you can!).
     
     The preferred method to submit bug reports from a machine with
     Internet mail connectivity is to use the send-pr command or use the CGI
     script at http://www.freebsd.org/send-pr.html.  Bug reports
     will be dutifully filed by our faithful bugfiler program and you can
     be sure that we'll do our best to respond to all reported bugs as soon
     as possible.  Bugs filed in this way are also visible on our WEB site
     in the support section and are therefore valuable both as bug reports
     and as "signposts" for other users concerning potential problems to
     watch out for.
     
     If, for some reason, you are unable to use the send-pr command to
     submit a bug report, you can try to send it to:
     
                     freebsd-bugs@FreeBSD.org
     
     Note that send-pr itself is a shell script that should be easy to move
     even onto a totally different system.  We much prefer if you could use
     this interface, since it make it easier to keep track of the problem
     reports.  However, before submitting, please try to make sure whether
     the problem might have already been fixed since.
     
     
     Otherwise, for any questions or tech support issues, please send mail to:
     
                     freebsd-questions@FreeBSD.org
     
     
     If you're tracking the -stable development efforts, you should
     definitely join the -stable mailing list, in order to keep abreast
     of recent developments and changes that may affect the way you
     use and maintain the system:
     
     		freebsd-stable@FreeBSD.org
     
     
     Additionally, being a volunteer effort, we are always happy to have
     extra hands willing to help - there are already far more desired
     enhancements than we'll ever be able to manage by ourselves!  To
     contact us on technical matters, or with offers of help, please send
     mail to:
     
                     freebsd-hackers@FreeBSD.org
     
     
     Please note that these mailing lists can experience *significant*
     amounts of traffic and if you have slow or expensive mail access and
     are only interested in keeping up with significant FreeBSD events, you
     may find it preferable to subscribe instead to:
     
                     freebsd-announce@FreeBSD.org
     
     
     All of the mailing lists can be freely joined by anyone wishing
     to do so.  Send mail to MajorDomo@FreeBSD.org and include the keyword
     `help' on a line by itself somewhere in the body of the message.  This
     will give you more information on joining the various lists, accessing
     archives, etc.  There are a number of mailing lists targeted at
     special interest groups not mentioned here, so send mail to majordomo
     and ask about them!
     
     
     6. Acknowledgments
     ------------------
     
     FreeBSD represents the cumulative work of many hundreds, if not
     thousands, of individuals from around the world who have worked very
     hard to bring you this release.  For a complete list of FreeBSD
     project staffers, please see:
     
             http://www.freebsd.org/handbook/staff.html
     
     or, if you've loaded the doc distribution:
     
             file:/usr/share/doc/handbook/staff.html
     
     Special thanks also go to the many thousands of FreeBSD users and testers
     all over the world, without whom this release simply would not have been
     possible.
     
                             The FreeBSD Project
     

    Release Home &footer; diff --git a/es/releases/snapshots.sgml b/es/releases/snapshots.sgml index 27138a6c2b..b4e9dcdf36 100644 --- a/es/releases/snapshots.sgml +++ b/es/releases/snapshots.sgml @@ -1,78 +1,79 @@ - - + + %navincludes; %includes; ]> - + &header;

    Qué son los snapshots?

    Como parte del esfuerzo de asegurar que las releases sean totalmente fiables antes de que sea liberada, estamos produciendo periódicamente releases de test llamadas snapshots. Estos snapshots seráan muy similares a las releases completas, exceptuando el tamaño. En particular , antes de instalar un snapshot, ten en cuenta lo siguiente:

      -
    • Generalmente no producimos, por ejemplo, nuevas - distribuciones de XFree86 o no nos preocupamos por el +
    • Generalmente no producimos, por ejemplo, nuevas + distribuciones de XFree86 o no nos preocupamos por el contenido del directorio tools, a no ser que alguna de estas dos cosas afecten a las modificaciones a testear.
    • El número principal de release no sera cambiado en la distribución de cada snapshot. Sólo será modificado en los discos de arranque para que puedas ver cuando ha sido generado ese snapshot. No hay releases, esto son snapshots, y es necesario que esta distinción se mantenga. Los usuarios pueden, por supuesto, referirse a los snapshots por la fecha, tanto por mail como en las news.
    • Finalmente, es posible que no actualicemos la documentación. - Si un README todavía se refiere a una release previa, + Si un README todavía se refiere a una release previa, bién, es menos importante que fijar los errores y probar las nuevas características.

    Tus comentarios sobre estos snapshots son muy bienvenidos. No son solo - para nuestro beneficio - aquellos que están usando o pensando + para nuestro beneficio - aquellos que están usando o pensando en usar FreeBSD para misiones críticas agradecerán tus comentarios actualizados. También puedes usar estos snapshots - para ver que tus comentarios son tenidos en cuenta y que no + para ver que tus comentarios son tenidos en cuenta y que no tendrás ningun sorpresa desagradable en la próxima release.

    Dónde encontrar los snapshots

    -

    Snapshots de +

    Snapshots de FreeBSD-current están disponibles vía ftp anónimo en ftp://current.freebsd.org/pub/FreeBSD/. Los snapshots están en directorios nombrados con el formato - REL-YYMMDD-SNAP donde `REL' es el número de + REL-YYMMDD-SNAP donde `REL' es el número de release, `YY' es el año, `MM' es el més , y `DD' es el día en el que se ha creado . Cada directorio contiene un fichero `README' que comenta las modificaciones realizadas.

    -

    Por demanda popular, los snapshots también están +

    Por demanda popular, los snapshots también están disponibles para la rama FreeBSD-stable vía FTP anónimo en ftp://releng22.freebsd.org/pub/FreeBSD/. Los snapshots están en directorios nombrados de la misma manera que los correspondientes a -current, pero terminando en RELENG en lugar de SNAP.

    Release Home &footer; diff --git a/es/search/index-site.sgml b/es/search/index-site.sgml index 66ece39d91..e79c71545e 100644 --- a/es/search/index-site.sgml +++ b/es/search/index-site.sgml @@ -1,49 +1,50 @@ - - + + %navincludes; %includes; ]> - + &header;

    Mapa del servidor

    &site;

    Secciones


    Indice A-Z

    &atoz; &footer; diff --git a/es/search/search-mid.sgml b/es/search/search-mid.sgml index 2e448cd469..4c858c4085 100644 --- a/es/search/search-mid.sgml +++ b/es/search/search-mid.sgml @@ -1,41 +1,41 @@ - - + %includes; ]> - + &header;
    ID-Mensaje:
    Respuestas al ID-Mensaje:

    Solo puedes buscar en las cabeceras Message-ID, Resent-Message-id, In-Reply-to, y -References. +References. Un Message-ID es algo como <199802242058.MAA24843@monk.via.net>. No se soportan otras cabeceras. La base de datos del campo Message-ID se actualiza cada hora.

    Archivos de listas en modo texto. &footer; diff --git a/es/search/search.sgml b/es/search/search.sgml index 6105d00725..d9092ad4fe 100644 --- a/es/search/search.sgml +++ b/es/search/search.sgml @@ -1,370 +1,370 @@ - - + %includes; ]> - + &header;

    Servicio de búsqueda de FreeBSD


    -

    Páginas Web (incluyendo -FAQ y +

    Páginas Web (incluyendo +FAQ y Handbook)

    Buscar:

    Nota: Usa los operadores AND y NOT para limitar la búsqueda. Mira aquí para más opciones.


    Limitar el número de resultados a


    Archivos listas de distribución

    &i.new; Los índices de los archivos de listas se actualizan ahora semanalmente!

    Las listas de distribución también son archivadas por GeoCrawler. Debes registrarte (gratis) con ellos antes de poder usar el buscador.

    Buscar:

    Nota: Usa los operadores AND y NOT para limitar la búsqueda Mira aquí para más opciones .


    Limitar el número de resultados a ordenado por

    En archivo(s):

    Nota: Buscar en más de tres o cuatro archivos de una sola vez puede producir resultados inadecuados.

    Archivos Generales

    Promoción Evangelismo FreeBSD
    Anuncios Noticias / Eventos importantes
    Chat Temas varios (a veces) relacionados con FreeBSD
    Trabajos Ofertas y demandas de empleo relacionadas con FreeBSD
    Principiantes Actividades y discusiones de nuevos usuarios de FreeBSD
    Preguntas Preguntas generales
    Grupos de usuarios Un fórum para grupos de usuarios de FreeBSD

    Administración y uso de sistemas

    Bugs Información y discusión de bugs
    Hardware Discusiones relacionadas con hardware y FreeBSDD
    ISP Discusiones de ISP's (Proveedores de Internet) usando FreeBSD
    Seguridad Seguridad y/en FreeBSD (DES, Kerberos, etc.)
    Stable Discusiones sobre la rama de desarrollo FreeBSD-stable

    Desarrollador

    - - - - - - - - - - - - - - - - - - - - - - -
    Afs Portando y usando AFS (Andrew File System) de CMU/Transarc
    Alpha Portando FreeBSD a DEC Alpha
    ATM Uso de redes ATM con FreeBSD
    Commit Cambios realizados al código fuente de FreeBSD
    Config Desarrollo de herramientas de configuración e instalación
    Current Uso de la rama de desarrollo FreeBSD-current
    Database Uso y desarrollo de bases de datos en FreeBSD
    Doc Documentación de FreeBSD
    Emulation Emulación de otros sistemas en FreeBSD
    Fs Sistema de ficheros de FreeBSD
    Hackers Discusiones técnicas generales
    ISDN Desarrollo de soporte de RDSI/ISDN en FreeBSD
    Java Port de JDK y desarrollo de aplicaciones
    Multimedia Discusiones sobre FreeBSD como plataforma multimedia
    Mobile Uso de FreeBSD en entornos móviles
    Mozilla Portando mozilla a FreeBSD
    Net Discusiones de red y código fuente TCP/IP
    Platforms FreeBSD en plataformas no-Intel
    Ports Colección de ports de FreeBSD
    Realtime Desarrollo de extensiones de tiempo real en FreeBSD
    SCSI Soporte de SCSI en FreeBSD
    Small Usando FreeBSD en aplicaciones "comprimidas"
    SMP FreeBSD en plataformas multiprocesador
    SPARC Portando FreeBSD a SPARC
    Tokenring Soporte Token Ring en FreeBSD

    &footer; diff --git a/es/search/searchhints.sgml b/es/search/searchhints.sgml index cdb31ce356..23fe4b6938 100644 --- a/es/search/searchhints.sgml +++ b/es/search/searchhints.sgml @@ -1,52 +1,52 @@ - - + %includes; ]> - + &header;

    Si obtienes múltiples resultados irrelevantes...

    1. Si buscas diferentes palabras como "quantum hard drives", un OR se considera relevante, sólo una de las palabras - ha de aparecer en el mensaje. Para encontrar mensajes que - sólo incluyan las tres palabras, cambia la + ha de aparecer en el mensaje. Para encontrar mensajes que + sólo incluyan las tres palabras, cambia la búsqueda a "quantum and hard and drives"

    2. Si todavía obtienes muchos mensajes irrelevantes, mira si - éstos tienen algo en común. Si es así, los + éstos tienen algo en común. Si es así, los puedes excluir con el operador not. Por ejemplo "quantum and hard and drives not ide" excluirá cualquier mensaje sobre discos duros ide quantum.

    Si crees que no has recinido todo lo que debieras...

      -
    1. Si alguna de tus palabras clave tiene variantes, +
    2. Si alguna de tus palabras clave tiene variantes, asegúrate de entrar todas las formar relevantes. Si busca "buslogic", deberías cambiarlo por "buslogic o bustek".

    3. Con palabras de sufijos variables podemos usar asteriscos. Buscando "drive*" aparecerán resultados como drive, drives, driver, drivers, etc.

    4. -
    5. Intenta eliminar palabras que puedan estar ya implicadas en +
    6. Intenta eliminar palabras que puedan estar ya implicadas en el contexto del mensaje. Por ejemplo ""quantum and hard and drive" perdería mensajes relevantes que "quantum and drive" podría obtener.

    Volver a la página de búsqueda &footer; diff --git a/es/security/programmers.sgml b/es/security/programmers.sgml index 51741a7eda..ead287cd30 100644 --- a/es/security/programmers.sgml +++ b/es/security/programmers.sgml @@ -1,193 +1,194 @@ - - + + %navincludes; %includes; ]> - + &header;

    • Never trust any source of input, i.e. command line arguments, environment variables, configuration files, incoming UDP packets, hostname lookups, function arguments, etc. If the length or contents of the data received is at all subject to outside control then the program or function should watch for this when copying it around. Specific security issues to watch for in this area are:

      • strcpy() and sprintf() calls from unbounded data. Use strncpy() and snprintf() when the length is known (or implement some other form of bounds-checking when it's not). In fact, never use gets(3) or sprintf(3), period.

      • strncpy() and strncat() calls. Be sure you understand how these work\! strncpy() might not append a terminating \\0 while strncat() always adds the \\0.

      • Watch for strvis(3) and getenv(3) abuse. strvis() is easy to get the destination string wrong for, and getenv() can return strings much longer than the user might expect - they are one of the key ways an attack is often made on a program, causing it to overwrite stack or variables by setting its environment variables to unexpected values. If your program reads environment variables, be paranoid!

      • Every time you see an open(2) or stat(2) call, ask yourself, "What if it's a symbolic link?"

      • All uses of mktemp(), tempnam(), mkstemp(), etc.; make sure that they use mkstemp() instead. Also look for races in /tmp in general, being aware that there are very few things can be atomic in /tmp:
        • Creating a directory. This will either succeed or fail.
        • Opening a file O_CREAT | O_EXCL
        mkstemp(3) properly handles this for you, so all temp files should use mkstemp to guarantee there's no race and that the permissions are right.

      • If an attacker can force packets to go/come from another arbitrary system then that hacker has complete control over the data that we get and *NONE* of it should be trusted.

      • Understand the differences between uid, euid and svuid in 2.1 and 2.2. We sure don't. [XXX but we should find out and fill this in after talking to Bruce]

      • Never trust that a config file is correctly formatted or that it was generated by the appropriate utility. If there is some chance for being sneaky, then some twisted cracker will try to be sneaky: Don't trust user input like terminal names or language strings to be free of '/' or ../../... embedded if there is any chance that they can be used in a path name. Don't trust *ANY* paths supplied by the user when you are running setuid root.

      • Look for holes or weaknesses in how data is stored. All temp files should be 600 permission.

      • Don't just grep for the usual suspects in programs which run at elevated privs. Look line by line for possible overflows in these cases since there are a lot more ways than strcpy() and friends to cause buffer overflows.

      • Just because you drop privs somewhere doesn't necessarily mean that no exploit is possible. The attacker may put the necessary code on the stack to regain them before execing /bin/sh.

    • Do uid management. So drop privs as soon as possible, and really drop them. Switching between euid and uid is not enough. Use setuid() when you can.

    • Never display configuration file contents on errors. A line number and perhaps position count is enough. This is true for all libs and for any SUID/SGID program.

    • Tips for those reviewing existing code for security problems:

      • If you're unsure of your security fixes, send them to a reviewer with whom you've already made arrangements for a second glance over. Don't commit code you're not sure of since breaking something in the name of securing it is rather embarrassing. :)

      • Those without CVS commit privileges should make sure that a reviewer with such privileges is among the last to review the changes. That person will both review and incorporate the final version you would like to have go into the tree.

      • When sending changes around for review, always use context or unidiff format diffs which may be easily fed to patch(1). Do not simply send whole files! Diffs are much easier to read and apply to local sources (especially those in which multiple, simultaneous changes may be taking place). All changes should be relative to 3.0-current just so we can all be working from a common base, unless there is strong reason in a specific instance to do otherwise.

      • Always directly test your changes (e.g. build and run the affected module(s)) before sending them to a reviewer; no one likes being sent obviously broken stuff for review, and it just makes it appear as though the submitter didn't even really look at what he was doing (which is hardly confidence-building). If you need accounts on a 2.1, 2.2 or 3.0 machine in order to do proper testing, just ask - the project has such resources available for just such purposes.

      • For committers: Be sure to retrofit -current patches into the 2.2 and 2.1 branches as appropriate.

      • Do not needlessly rewrite code to suit your style/tastes - it only makes the reviewer's job needlessly more difficult. Do so only if there are clear technical reasons for it.

    • Look out for programs doing complex things in signal handlers. Many routines in the various libraries are not sufficiently reentrant to make this safe.

    • Pay special attention to realloc() usage - more often than not, it's not done correctly.

    • When using fixed-size buffers, use sizeof() to prevent lossage when a buffer size is changed but the code which uses it isn't. For example: - char buf[1024]; +
      	char buf[1024];
       	struct foo { ... };
       	...
       BAD:
       	xxx(buf, 1024)
       	xxx(yyy, sizeof(struct foo))
       GOOD:
       	xxx(buf, sizeof(buf))
      -	xxx(yyy, sizeof(yyy))
      + xxx(yyy, sizeof(yyy)) Be careful though with sizeof of pointers when you really want the size of where it points to\!

    • Every time you see "char foo[###]", check every usage of foo to make sure it can't be overflowed. If you can't avoid overflow (and cases of this have been seen) then at least malloc the buffer so you can't walk on the stack.

    • Always close file descriptors as soon as you can -- this makes it more likely that the stdio buffer contents will be discarded. In library routines, always set any file descriptors that you open to close-on-exec.

    - &footer + &footer; diff --git a/es/security/secure.sgml b/es/security/secure.sgml index 24dfa6ffa7..aebb6ab7d7 100644 --- a/es/security/secure.sgml +++ b/es/security/secure.sgml @@ -1,60 +1,61 @@ - - + + %navincludes; %includes; ]> - + &header; There are several steps involved in securing a FreeBSD system, or in fact any UNIX system:
    • disabling potentially dangerous software
      A lot of software has to be run as a special privileged user to make use of specific resources, bij making the executable set-uid. An example is UUCP software or PPP software that makes use of a serial port, or sendmail which has to write in the mail spool and bind to a network port. When you are not using UUCP, it is of little use to have the software on your system and it may be wise to disable it. Of course, this requires good knowlegde of what can be thrown away and what not, as well as a good indication whether or not you will want the functionality in the future.
      Also some utilities you may find not interesting enough to have them around and pose a possible security risk, like swapinfo. If you remove the set-uid bit for the executable (via chmod ug-s filename) you can always keep on using swapinfo when you're root. It is however not a good idea stripping so many sbits you have to be root all the time.
      Not only remove programs that you don't use, also remove services you don't want or need to provide. This can be done by editting the /etc/inetd.conf file and uncommenting out all services you don't use.
    • fixing software with security bugs
      Subscribe yourself to mailinglist to get updates on security bugs in software and to get the fixes. Apply them immediately.
    • checking your system on a regular basis
      With programs like COPS and SATAN you can find gaping holes and misconfigurations on your system. It is a good idea to run them occasionaly to see if you have made any mistakes.
      Also check the daily security reporting that FreeBSD send to root. Check the logfiles once in a while. Clean up unused accounts.
    • being able to repair your system when security has been breached
      Always have backups and a clean version of the operating system (e.g. on CD-ROM).
    • installing software that watches the system
      Programs like the tcp wrapper (a package with FreeBSD) and tripwire help you monitor activity on your system. This makes it easier to detect breakins.
    • educating the people working on the system
      Users should know what they are doing, and e.g. use hard to guess password. Let them understand that the security of the system is partly in their hands.
    &footer diff --git a/es/security/security.sgml b/es/security/security.sgml index 76807a52e4..f843a47d6a 100644 --- a/es/security/security.sgml +++ b/es/security/security.sgml @@ -1,501 +1,502 @@ - - + + %navincludes; %includes; ]> - + &header;

    Introducción

    El objetivo de esta página es orientar a los usuarios, tanto noveles como experimentados, en el área de seguridad del Sistema Operativo FreeBSD. El equipo de Desarrollo de FreeBSD se toma la seguridad muy en serio y trabaja constantemente para hacer el Sistema Operativo tan seguro como sea posible.

    -

    Aquí podrás encontrar información adicional, o enlaces -a información, acerca de cómo proteger tu sistema contra varios -tipos de ataque del exterior, con quién contactar si encuentra un error -de software relacionado con la seguridad, etc. También hay una -sección que trata de las distintas formas en que el programador de -sistemas puede concienciarse acerca de la seguridad, de modo que sea menos +

    Aquí podrás encontrar información adicional, o enlaces +a información, acerca de cómo proteger tu sistema contra varios +tipos de ataque del exterior, con quién contactar si encuentra un error +de software relacionado con la seguridad, etc. También hay una +sección que trata de las distintas formas en que el programador de +sistemas puede concienciarse acerca de la seguridad, de modo que sea menos probable la introducción de defectos de seguridad en el software.

    Contenidos

    El FreeBSD Security Officer

    Con el objetivo de coordinar mejor el intercambio de información con otras personas o entidades relacionadas con el ámbito de la seguridad, FreeBSD tiene un punto focal para las comunicaciones relacionadas con la seguridad: el FreeBSD security officer. El puesto está actualmente ocupado por un equipo de security officers dedicados, siendo sus tareas principales emitir advisories cuando hay defectos de seguridad conocidos y actuar ante los informes de posibles problemas de seguridad con FreeBSD.

    Si necesitas contactar con alguien del equipo de FreeBSD acerca de un posible error de software relacionado con la seguridad por favor hazlo por correo al Security Officer, incluyendo una descripción de lo que has encontrado y el tipo de vulnerabilidad que representa. El Security Officer también está en contacto con los diferentes equipos CERT y FIRST en todo el mundo, con los que comparte información acerca de posibles vulnerabilidades en FreeBSD o programas de utilidad usados por FreeBSD. Los Security Officers también son miembros activos de dichas organizaciones.

    Si necesitas contactar con el Security Officer acera de algún asunto especialmente delicado, usa su clave PGP para encriptar el mensaje antes de enviarlo.

    FreeBSD Security Advisories

    Los FreeBSD Security Officers proporcionan security advisories para las releases de FreeBSD siguientes:

    • La release oficial de FreeBSD más reciente.
    • FreeBSD-current.
    • FreeBSD-stable, cuando hay al menos 2 releases basadas en él.
    • FreeBSD-stable anterior cuando un "nuevo stable" aun no tiene 2 releases basadas en él.
    En este momento hay disponibles security advisories para:
    • FreeBSD 2.2.8
    • FreeBSD 3.1
    • FreeBSD 3.2
    • FreeBSD-current
    • FreeBSD-stable

    No hay mantenimiento para releases anteriores a estas. Se recomienda a los usuarios se actualicen a una de las releases arriba mencionadas.

    Como todos los esfuerzos de desarrollo, las reparaciones de seguridad -se incorporan primero en la rama +se incorporan primero en la rama FreeBSD-current. -Después de un par de días de prueba la reparación se +Después de un par de días de prueba la reparación se incorpora en las ramas FreeBSD-stable soportadas y se emite un advisory.

    -

    Los advisories se envían a las siguientes listas de +

    Los advisories se envían a las siguientes listas de distribución de FreeBSD:

    • FreeBSD-security-notifications@FreeBSD.org
    • FreeBSD-security@FreeBSD.org
    • FreeBSD-announce@FreeBSD.org
    -

    Los advisories se firman siempre usando la +

    Los advisories se firman siempre usando la clave PGP del FreeBSD Security Officer y se archivan, junto con los -patches asociados, en nuestro +patches asociados, en nuestro -repositorio FTP CERT. En el momento de escribir esto están +repositorio FTP CERT. En el momento de escribir esto están disponibles los advisories siguientes:

    -

    Información acerca de las Listas de Distribución sobre +

    Información acerca de las Listas de Distribución sobre Seguridad en FreeBSD

    Si eres administrador o usuario de uno o más sistemas FreeBSD, quizás quieras suscribirte a alguna de las listas siguientes:

     FreeBSD-security                Discusiones relacionadas con la seguridad en general
     FreeBSD-security-notifications  Notificaciones sobre seguridad (lista moderada)
     
    Envíe un mensaje a majordomo@FreeBSD.ORG con
          subscribe <nombre_de_la_lista>  [<dirección_email_opcional>]
     
    en el cuerpo del mensaje para suscribirse. Por ejemplo:
     % echo "subscribe FreeBSD-security" | mail majordomo@FreeBSD.org
     
    y si quieres desuscribirte de una lista de distribución:
     % echo "unsubscribe FreeBSD-security" | mail majordomo@FreeBSD.org
     

    Pautas para la Programación Segura

      -
    • Nunca te fíes de ninguna fuente de entrada, i.e. argumentos en la -línea de comando, variables de entorno, ficheros de +
    • Nunca te fíes de ninguna fuente de entrada, i.e. argumentos en la +línea de comando, variables de entorno, ficheros de configuración, paquetes TCP/UDP/ICMP entrantes, argumentos de funciones, - etc. Si la longitud o el contenido de los datos recibidos están -sujetos, siquiera mínimamente, al control desde el exterior, el -programa o la función debería tenerlo en cuenta cuando maneja -dichos datos. Podemos considerar los apartados siguientes desde el punto de + etc. Si la longitud o el contenido de los datos recibidos están +sujetos, siquiera mínimamente, al control desde el exterior, el +programa o la función debería tenerlo en cuenta cuando maneja +dichos datos. Podemos considerar los apartados siguientes desde el punto de vista de la seguridad:

        -
      • Llamadas a strcpy() y sprintf() para datos de longitud ilimitada. +
      • Llamadas a strcpy() y sprintf() para datos de longitud ilimitada. Usa strncpy() y snprintf() cuando la longitud sea conocida (o implementa algun otro método de control de límites cuando sea desconocida). -No uses nunca gets() ni sprintf(), punto. Si lo haces, te acosarán sin +No uses nunca gets() ni sprintf(), punto. Si lo haces, te acosarán sin tregua duendes malvados.

      • Si tienes que validar los datos de entrada del usuario para evitar que contengan caracteres erróneos de cualquier clase, NO valides la presencia de dichos caracteres erróneos. Simplemente verifica que la entrada consiste SOLO en los caracteres permitidos. La idea es: todo lo que no está explícitamente permitido está prohibido.

      • Lee las páginas del manual para las llamadas strncpy() y strncat(). -Asegúrate de entender cómo funcionan!!! Así como -strncpy() puede no añadir un \0 final, strncat() sí lo +Asegúrate de entender cómo funcionan!!! Así como +strncpy() puede no añadir un \0 final, strncat() sí lo añade.

      • Vigila el abuso de strvis() y getenv(). Con strvis() es fácil cometer -un error con la cadena de destino, y getenv() podría devolver cadenas -mucho más largas de lo que el programa espera. Estas dos funciones son, -a menudo, una de las vías principales de ataque contra un programa, -provocando que este sobreescriba la pila o las variables al recibir variables -de entorno con valores no contemplados. Si tu programa lee variables de +un error con la cadena de destino, y getenv() podría devolver cadenas +mucho más largas de lo que el programa espera. Estas dos funciones son, +a menudo, una de las vías principales de ataque contra un programa, +provocando que este sobreescriba la pila o las variables al recibir variables +de entorno con valores no contemplados. Si tu programa lee variables de entorno, se paranoico. Se muy paranoico!

      • Cada vez que uses las llamadas open() o stat() pregúntate: " Y si es un enlace simbólico ?"

      • -
      • Asegúrate de usar mkstemp() en lugar de mktemp(), tempnam(), -etc. Asegúrate también de buscar problemas de acceso +
      • Asegúrate de usar mkstemp() en lugar de mktemp(), tempnam(), +etc. Asegúrate también de buscar problemas de acceso concurrente en general en /tmp, teniendo en cuenta que hay muy pocas cosas que pueden ser atómicas en /tmp:
        • Crear un directorio. O funciona o no funciona.
        • Abrir un fichero O_CREAT | O_EXECL
        -Si se usa mkstemp() la función tratará por tí estos casos -adecuadamente. De aquí que todos los ficheros temporales -deberían usar mkstemp() para garantizar que no se produzcan problemas +Si se usa mkstemp() la función tratará por tí estos casos +adecuadamente. De aquí que todos los ficheros temporales +deberían usar mkstemp() para garantizar que no se produzcan problemas de acceso concurrente y que los permisos son correctos.

      • Un atacante que consiga que los paquetes vayan a/vengan de un sistema arbitrario tendrá el control completo de los datos que recibimos, por lo tanto NINGUNO de estos datos será de fiar.

      • -
      • Nunca dés por hecho que un fichero de configuración -estará correctamente formateado o que habrá sido generado por -el programa de utilidad apropiado. No confíes en que las entradas del -usuario tales como nombres de terminal o cadenas del lenguaje estarán -libres de '/' o '../../../' si hay la mínima posibilidad de que puedan -ser usadas en un nombre de path. No confíes en NINGUN path +
      • Nunca dés por hecho que un fichero de configuración +estará correctamente formateado o que habrá sido generado por +el programa de utilidad apropiado. No confíes en que las entradas del +usuario tales como nombres de terminal o cadenas del lenguaje estarán +libres de '/' o '../../../' si hay la mínima posibilidad de que puedan +ser usadas en un nombre de path. No confíes en NINGUN path proporcionado por el usuario cuando el programa se ejecuta setuid root.

      • Busca fallos o puntos débiles en la forma de almacenar los datos. Todos los ficheros temporales deberían tener permisos de la forma 600 para protegerlos de ojos curiosos.

      • No te limites a buscar con grep los sospechosos habituales en programas que se ejecutan con privilegios elevados. Busca los -posibles desbordamientos línea a línea, hay muchísimas -más formas de provocar un desbordamiento de memoria además de +posibles desbordamientos línea a línea, hay muchísimas +más formas de provocar un desbordamiento de memoria además de mediante el abuso de strcpy() y sus amigos.

      • El simple hecho de restringir privilegios en algún punto no significa que no haya manera de explotar el recurso en cuestión. El atacante podría colocar el código necesario en la pila para recuperar los privilegios antes de ejecutar /bin/sh.

    • Administra los uid. Elimina privilegios tan pronto como sea posible, y elimínalos de verdad. Cambiar entre euid y uid NO es suficiente. Usa setuid() siempre que puedas.

    • -
    • Nunca muestres el contenido de ficheros de configuración cuando -ocurra un error. Un número de línea y quizás un contador +
    • Nunca muestres el contenido de ficheros de configuración cuando +ocurra un error. Un número de línea y quizás un contador de posición es suficiente. -Esto mismo es igualmente cierto para todas las librerías y todos los +Esto mismo es igualmente cierto para todas las librerías y todos los programas suid/gid.

    • Consejos para quienes revisen código existente debido a problemas de seguridad:

      • Si no estás seguro de tus reparaciones de seguridad, envíalas - para ser revisadas a alguien con quien así lo hayas acordado -previamente. No entregues código del que no estás seguro, llegar -a estropear algo en nombre de las reparaciones de seguridad resulta bastante + para ser revisadas a alguien con quien así lo hayas acordado +previamente. No entregues código del que no estás seguro, llegar +a estropear algo en nombre de las reparaciones de seguridad resulta bastante embarazoso.

      • Aquellos con privilegios de entrega ("commit") para CVS deberían -asegurarse de que alguien con dichos privilegios esté entre los -últimos en revisar los cambios. Dicha persona revisará e -incorporará la versión final que se desea tener en el +asegurarse de que alguien con dichos privilegios esté entre los +últimos en revisar los cambios. Dicha persona revisará e +incorporará la versión final que se desea tener en el árbol.

      • Cuando distribuyas cambios para ser revisados usa siempre diffs con formato context o unidiff. De este modo los diffs pueden ser fácilmente proporcionados como entrada a patch(1). No te limites a enviar los ficheros -enteros. Los diffs son más fáciles de leer y aplicar al -código fuente local (especialmente a aquel en el que podrían +enteros. Los diffs son más fáciles de leer y aplicar al +código fuente local (especialmente a aquel en el que podrían tener lugar múltiples cambios simultáneamente). Todos los cambios deberían referirse a la rama de desarrollo -current.

      • Prueba tu mismo todos los cambios (i.e. compila y ejecuta el código fuente afectado) antes de enviarlos a otra persona para que los revise. A nadie le gusta que le envíen material averiado para revisar, -y además produce la impresión de que el remitente ni siquiera se -fijó en lo que estaba haciendo (lo que no contribuye precisamente a dar -una sensación de confianza). Si necesita una cuenta en una -máquina donde hay una versión específica que no tienes a -mano, simplemente pregunta. El proyecto tiene recursos asignados para ese +y además produce la impresión de que el remitente ni siquiera se +fijó en lo que estaba haciendo (lo que no contribuye precisamente a dar +una sensación de confianza). Si necesita una cuenta en una +máquina donde hay una versión específica que no tienes a +mano, simplemente pregunta. El proyecto tiene recursos asignados para ese propósito en concreto.

      • Nota para los responsables de la entrega de código ("commit"): no se debe olvidar incorporar a la rama -stable los patches hechos sobre -current, de la forma que sea adecuada.

      • No reescribas código innecesariamente para acomodarlo a tu estilo/ -gustos. Esto sólo hace el trabajo de quienes lo revisan más +gustos. Esto sólo hace el trabajo de quienes lo revisan más difícil. Hazlo sólo si hay razones claras para ello.

    • Busca programas que hagan cosas complicadas con los gestores de señales. Muchas rutinas en varias bibliotecas no son lo suficientemente reentrantes como para hacerlo con seguridad.

    • Presta especial atención al uso de realloc(). Lo habitual es no usar la función correctamente.

    • -
    • Cuando uses áreas de memoria de longitud fija use sizeof() para -evitar pérdidas cuando se cambia el tamaño del área pero +
    • Cuando uses áreas de memoria de longitud fija use sizeof() para +evitar pérdidas cuando se cambia el tamaño del área pero no el código que la usa. Por ejemplo: - +
               char buf[1024];
               struct foo { ... };
               ...
       MAL:
               xxx(buf, 1024)
               xxx(yyy, sizeof(struct foo))
       BIEN:
               xxx(buf, sizeof(buf))
               xxx(yyy, sizeof(yyy))
      -
      + Ten cuidado al aplicar sizeof a un puntero cuando lo que quieres es el tamaño del objeto referenciado!

    • Siempre que veas "char foo[###]", comprueba cada uso de foo para asegurarte de que no se desbordará. Si no puedes evitar el desbordamiento (se han dado casos), usa malloc como mal menor para ubicar el área de memoria, de este modo evitarás sobreescribir la pila.

    • Cierra siempre los descriptores de ficheros tan pronto como puedas, lo -que hará más probable que los contenidos del área de -memoria de entrada de stdio() sean desechados. En rutinas de biblioteca, -dispon siempre los descriptores de ficheros que abras de modo que se cierren +que hará más probable que los contenidos del área de +memoria de entrada de stdio() sean desechados. En rutinas de biblioteca, +dispon siempre los descriptores de ficheros que abras de modo que se cierren tras lanzar con éxito otro proceso.

    Consejos sobre seguridad en FreeBSD

    Se deben ejecutar varios pasos para hacer seguro un sistema FreeBSD (para el caso, cualquier sistema Unix):

    • Inhabilitar todo software potencialmente peligroso

      Gran cantidad de software debe ser ejecutado con un usuario privilegiado especial para poder hacer uso de recursos específicos, haciendo el ejecutable set-uid. Un ejemplo es el software UUCP o PPP, que hacen uso del puerto serie, o sendmail, que tiene que escribir en el spool de correo y conectar con un puerto de red privilegiado. Si no usas UUCP de poco -sirve tener en su sistema el software asociado; sería prudente +sirve tener en su sistema el software asociado; sería prudente inhabilitarlo. Desde luego, esto requiere saber a ciencia cierta lo que puede ser eliminado y lo que no, así como tener claro si se va a necesitar o no dicha funcionalidad en el futuro.

      Lo mismo se puede decir de aquellos programas de utilidad que no consideres -lo bastante útiles y que supongan un posible riesgo para la seguridad, +lo bastante útiles y que supongan un posible riesgo para la seguridad, como swapinfo. Si elminas el bit set-uid del ejecutable (por medio del comando "chmod ug-s nombre-de-fichero") siempre habrá la posibildad de que el usuario root pueda usar swapinfo. Sin embargo no es una buena idea elminar tantos sbits que se haga necesario ser root contínuamente.

      No sólo elimines programas que no uses, elimina también servicios - que no quieras o necesites suministrar. Esto se puede hacer editando los + que no quieras o necesites suministrar. Esto se puede hacer editando los ficheros /etc/inetd.conf y /etc/rc.conf e inhabilitando los servicios que no quieras usar.

    • Reparar el software con errores que afecten a la seguridad (o cómo mantenerse un paso por delante de los crackers)

      Asegúrate de suscribirte a las diferentes Listas de ditribución sobre seguridad en FreeBSD para obtener actualizaciones relacionadas con los errores que afectan a la seguridad y reparaciones. Aplica las reparaciones inmediatamente.

    • Copias de seguridad. Repare su sistema si una violación de la seguridad llegara a ocurrir

      Disponga siempre de copias de seguridad y de una versión limpia del sistema operativo (por ejemplo en CD-Rom). Asegúrese de que sus copias de seguridad no contienen datos alterados o modificados por el atacante.

    • Instala software pare vigilar el estado del sistema

      Programas como tcp wrappers y tripwire (ambos en packages/ports) pueden -ayudarte a monitorizar la actividad en tu sistema. Esto hace más -fácil la detección de irrupciones. Lee también la salida +ayudarte a monitorizar la actividad en tu sistema. Esto hace más +fácil la detección de irrupciones. Lee también la salida de los scripts de /etc/security, que se ejecutan diariamente y se envían por correo a la cuenta root.

    • Educa a la gente que trabaja en el sistema

      Los usuarios deberían ser conscientes de lo que hacen. Deberías -indicarles que nunca revelen su password a nadie y que usen passwords -difíciles de adivinar. Hazles entender que la seguridad del +indicarles que nunca revelen su password a nadie y que usen passwords +difíciles de adivinar. Hazles entender que la seguridad del sistema/de la red está parcialmente en sus manos.

    También hay un documento PASO a PASO ("HowTo") sobre seguridad en FreeBSD disponible que proporciona algunos consejos avanzados acerca de -cómo mejorar la seguridad de su sistema. Puede ser consultado en +cómo mejorar la seguridad de su sistema. Puede ser consultado en http://www.FreeBSD.org/~jkb/howto.html.

    -

    La seguridad es un proceso contínuo. Asegúrate de estar al +

    La seguridad es un proceso contínuo. Asegúrate de estar al día con los avances en el campo de la seguridad.

    Qué hacer si detectas que la seguridad ha sido comprometida

    • Determina el alcance de la violación de seguridad
      - Qué privilegios consiguió el atacante ? Consiguió + Qué privilegios consiguió el atacante ? Consiguió acceso de root ? Consiguió acceso sólo en el nivel de usuario ?
    • Determina si se ha alterado el estado del sistema (ámbito del kernel o de usuario)
      Qué software ha sido alterado? Se instaló un nuevo kernel ? Ha sido modificado alguno de los archivos binarios del sistema (tales como telnetd, login, etc.) ? Si sospechas que un atacante puede haber -causado cualquier alteración en un sistema operativo, podrías +causado cualquier alteración en un sistema operativo, podrías considerar conveniente reinstalar el sistema operativo desde un medio seguro.
    • Averigua cómo se logró la irrupción
      Ocurrió por medio de un error de seguridad bien conocido ? Si este es -el caso, asegúrate de instalar los patches correctos. Tuvo éxito -la irrupción debido a una mala configuración ? Fue el resultado -de un error desconocido hasta el momento ? Si sospechas que la -irrupción ocurrió por medio de un error nuevo, deberías +el caso, asegúrate de instalar los patches correctos. Tuvo éxito +la irrupción debido a una mala configuración ? Fue el resultado +de un error desconocido hasta el momento ? Si sospechas que la +irrupción ocurrió por medio de un error nuevo, deberías advertir al FreeBSD Security Officer.
    • Repara el defecto de seguridad
      Instala nuevo software o aplica patches al antiguo para reparar los problemas. Inhabilita las cuentas que ya han sido comprometidas.
    • Otros recursos
      -CERT también ofrece +CERT también ofrece información detallada acerca de qué pasos seguir en caso de que un sistema se vea comprometido.

    Otra Información Relacionada Con La Seguridad

    &footer diff --git a/es/send-pr.sgml b/es/send-pr.sgml index 3cc989dfc7..c316160b91 100644 --- a/es/send-pr.sgml +++ b/es/send-pr.sgml @@ -1,139 +1,139 @@ + -&author;
    &date;'> + %navincludes; %includes; ]> - + &header; Bugs -

    Gracias por ocupar tu tiempo en informarnos sobre un problema con - FreeBSD. Por favor, completa el formulario tanto como te sea posible. - Asegúrate de responder el campo "Entorno" como te solicitamos con la salida de la máquina en la que está ocurriendo el +

    Gracias por ocupar tu tiempo en informarnos sobre un problema con + FreeBSD. Por favor, completa el formulario tanto como te sea posible. + Asegúrate de responder el campo "Entorno" como te solicitamos con la salida de la máquina en la que está ocurriendo el problema.

    Para hacer más eficiente un reporte, se recomienda leer la - guía para escribir un reporte de problema y así + guía para escribir un reporte de problema y así facilitar el proceso.

    -

    Por favor asegúrate, y de no ser así especificarlo en el - reporte, que cualquier parche enviado al Proyecto FreeBSD sea bajo la +

    Por favor asegúrate, y de no ser así especificarlo en el + reporte, que cualquier parche enviado al Proyecto FreeBSD sea bajo la misma licencia que FreeBSD.

    Finalmente, es necesario que puedas ver en tu navegador imágenes gráficas como medida de protección contra abusos del sistema. Si no es posible, por favor, disculpa las molestias. Ponte en - contacto y envía el reporte en un mail al + contacto y envía el reporte en un mail al equipo de bugbusters para que ellos lo añadan al sistema de control de reportes.

    Dirección de Email:

    Nombre:

    Organización o compañía:

    Una línea descriptiva del problema:

    Categoría:
    Importancia:
    Prioridad:
    Tipo:
    Qué Release de FreeBSD estás usando :
    -
    Entorno (salida de "uname -a" en la máquina del +
    Entorno (salida de "uname -a" en la máquina del problema):

    Descripción completa:

    Cómo repetir el problema:

    Solución del problema si se conoce:

    - Finalmente, introduce la palabra de la imagen inferior para + Finalmente, introduce la palabra de la imagen inferior para asegurarnos que no se usa un robot:
    Random text; if you cannot see the image, please email &bugbusters;

    Nota: Si se usa copiar/pegar se destruirán los tabuladores y espacios en blanco. Este formulario no debe usarse para enviar código como texto.

    - + &footer; diff --git a/es/support.sgml b/es/support.sgml index da78ccb138..76ad2bbedb 100644 --- a/es/support.sgml +++ b/es/support.sgml @@ -1,570 +1,571 @@ - + + %navincludes; %includes; ]> - + &header;

    Listas de distribución

    -

    Las listas de +

    Las listas de distribución son el canal principal de soporte entre usuarios, con numerosas listas cubriendo diferentes temas. Cuando tengas dudas sobre a qué lista enviar una pregunta, enviala a freebsd-questions@FreeBSD.ORG . Puedes buscar en los archivos de las listas de www.freebsd.org.

    Diferentes listas no inglesas también están disponibles:

    Si creas alguna lista sobre freebsd háznoslo saber.

    Newsgroups

    Existen diferentes newsgroups, además de otros numerosos grupos con temas de interés para los usuarios de FreeBSD. Para discusiones referentes a FreeBSD, mira en comp.unix.bsd.freebsd.misc. Para anuncios importantes, mira en comp.unix.bsd.freebsd.announce.

    El BSD Usenet News Searcher tiene archivos de todos los grupos de noticias referentes a FreeBSD desde Junio de 1992.

    Recursos WEB

    • Nuestas páginas WEB son una de las mejores fuentes de - información y existen diferentes mirrors repartidos por todo el + información y existen diferentes mirrors repartidos por todo el mundo. Intenta conectar a www.tu_pais.freebsd.org (por ejemplo www.de.freebsd.org para Alemania o www.au.freebsd.org para Australia), o selecciona un mirror de la lista en la página principal. Usamos la misma convención de nombres para los servidores FTP.

      - +

      Además de los mirrors, diferentes direcciones web no inglesas también están disponibles:

      - +

    • -
    • Para información sobre progresos recientes de FreeBSD y - releases, mira en la página de +

    • Para información sobre progresos recientes de FreeBSD y + releases, mira en la página de Newsflash.

    • Para recibir la FreeBSD Newsletter y/o subscribirte a la lista de distribución de anuncios, por favor, mira en la página de Registros.

    GNATS Base de datos de informes de problemas

    Los informes sobre problemas con FreeBSD son seguidos a través de la base de datos GNATS.

    Los informes de problemas también deberían enviarse al equipo de desarrollo usando el comando - send-pr(1) en un - sistema FreeBSD, o enviado un email a + send-pr(1) en un + sistema FreeBSD, o enviado un email a freebsd-bugs@FreeBSD.ORG. - Por favor, ten en cuenta que es preferible enviar los informes a + Por favor, ten en cuenta que es preferible enviar los informes a través de - send-pr ya que los mensajes enviador directamente a la lista + send-pr ya que los mensajes enviador directamente a la lista no son registrados como informes oficiales de problemas!.

    CVS

    CVS (Concurrent Version System) es la herramienta que usamos para mantener el código fuente bajo control. Todos y cada uno de los cambios (acompañados de un mensaje de log explicando su función) desde la versión 2.0 están almacenados - allí, y pueden ser facilmente revisados desde aquí + allí, y pueden ser facilmente revisados desde aquí (pulsa en el link). Para obtener una copia completa del CVS de FreeBSD o cualquiera de las ramas de desarrollo, hay que seleccionar alguna de las siguientes opciones:

    • cvsup Si estás buscando una utilidad tipo on-demand y de fácil acceso (escrita en Modula-3).
    • anoncvs si estás buscando una utilidad para recuperar pequeñas secciones de código, y ya incluida en tu sistema FreeBSD.
    • -
    • CTM básicamente +
    • CTM básicamente para recoger parches a través de email, y modo de acceso batch.
    • El interface web para revisar algún fichero o buscar una modificación específica.
    • Finalmente, si tienes ancho de banda disponible o prefieres usar el FTP, puedes, simplemente, hacer un mirror del CVS desde ftp.freebsd.org.
    -

    Mirrors del script de CVSWeb están disponibles en +

    Mirrors del script de CVSWeb están disponibles en California, Alemania, - Japón y España + Japón y España (Inglés, Español).

    Grupos de Usuarios

    -

    La popularidad de FreeBSD ha hecho aparecer diferentes grupos de - usuarios por todo el mundo. Si conoces algún grupo de - usuarios que no esté listado aquí, +

    La popularidad de FreeBSD ha hecho aparecer diferentes grupos de + usuarios por todo el mundo. Si conoces algún grupo de + usuarios que no esté listado aquí, háznoslo saber.

    Australia

    Europa

    Norte América

    Resto del mundo

    Proyectos de desarrollo de FreeBSD

    Además de la línea principal de desarrollo de FreeBSD, un número importante de grupos de desarrolladores están trabajando para expandir el abanico de aplicaciones en nuevas direcciones. -

    Guía de Seguridad de FreeBSD

    - Recursos de seguridad disponibles para usuarios de FreeBSD: + Recursos de seguridad disponibles para usuarios de FreeBSD: PGP Key's para los Security Officers, avisos, parches y listas.

    Servicios de Consultoría Comercial

    - Si estás empezando con FreeBSD, o necesitas completar un + Si estás empezando con FreeBSD, o necesitas completar un importante proyecto, un consultor puede ser la solución.

    Información sobre UNIX en General

    The X Window System

    • El Proyecto XFree86 provee a los usuarios de sistemas Unix basados en Intel, incluyendo FreeBSD, de un excelente sistema de X Window.
    • -
    • El proyecto WINE está - trabajando en la posibilidad de ejecutar software de MS-Windows en - sistemas Unix basados en Intel, como FreeBSD, NetBSD y Linux. +
    • El proyecto WINE está + trabajando en la posibilidad de ejecutar software de MS-Windows en + sistemas Unix basados en Intel, como FreeBSD, NetBSD y Linux.

    Hardware

    • La comp.answers pc-hardware-faq es una gran +erarchy/comp/answers/pc-hardware-faq">pc-hardware-faq es una gran referencia para personas que se construyan sus propias máquinas.
    • Los usuarios de equipos portátiles con PCCARD (PCMCIA) no soportadas todavía en la distribución base de FreeBSD, deberían mirar en la página de la distribución - PAO para conocer - más datos sobre los últimos e importantes avances.
    • + PAO para conocer + más datos sobre los últimos e importantes avances.
    • Intel Secrets -- What - Intel Doesn't Want You To Know - Mucha información + Intel Doesn't Want You To Know - Mucha información sobre chips Intel.
    • Aad Offerman's Chip List - referencia de chips usados en PC's.
    • ASUS fabrica placas bases que funcionan bien con FreeBSD.
    • -
    • La guía de hardware de +
    • La guía de hardware de FreeBSD hace algunas recomendaciones especiales sobre hardware que funciona bién con FreeBSD.

    Proyectos de Sistemas Operativos Relacionados

    • NetBSD es otro sistema operativo libre basado en 4.4BSD-Lite que funciona en diferentes arquitecturas de hardware.
    • OpenBSD es otro derivado de 4.4BSD.
    • Linux es otro sistema Unix libre.
    • Lites - es un sistema servidor y librería de emulación basado en + es un sistema servidor y librería de emulación basado en 4.4BSD-Lite que provee de funcionalidad Unix a sistemas Mach.
    • El proyecto GNU HURD es otro esfuerzo para desarrollar otro sistema operativo Unix libre.
    &footer; diff --git a/es/where.sgml b/es/where.sgml index 88cde43134..7177c8edb6 100644 --- a/es/where.sgml +++ b/es/where.sgml @@ -1,125 +1,126 @@ - + + %navincludes; %includes; ]> - + &header;

    Información Release

    Descripciones detalladas de pasado, presente y futuras releases. Mira primero aquí para determinar cual es la última versión de FreeBSD.

    Instalando FreeBSD

    Hay muchas opciones para instalar FreeBSD, incluyendo instalación desde CDROM, disketes, partición MS-DOS, cinta magnética, ftp anónimo y NFS. Por favor, lee la guía de instalación - antes de bajar la distribución de FreeBSD. Si estás - instalando una máquina conectada a Internet, solo necesitas + antes de bajar la distribución de FreeBSD. Si estás + instalando una máquina conectada a Internet, solo necesitas bajar un único diskete de instalación!.

    Servidores de Distribuciones

    Las fuentes oficiales de FreeBSD son:

    Si tienes previsto instalar FreeBSD vía ftp, por favor, revisa la lista de mirrors en el manual para ver si existe algún servidor cercano a tí. Para más información sobre pasadas presentes y futuras releases en general, visita la página de información de releases.

    Si estás interesado en una versión puramente experimental - de FreeBSD-current, dedicada para desarrolladores y tests, por favor, + de FreeBSD-current, dedicada para desarrolladores y tests, por favor, mira en el servidor FTP de distribuciones diarias. Este servidor también contiene versiones diarias de la rama 2.2-stable.

    Aplicaciones y utilidades de Software

    La colección de Packages

    Los packages de FreeBSD es una extensa colección de utilidades y aplicaciones que ha sido portado a FreeBSD. Los packages son binarios precompilados listos para instalar y funcionar.

    La colección de Ports

    La colección de Ports es como la colección de packages pero en lugar de binarios compilados, se usa el código fuente y los parches necesarios. Para software con configuraciones importantes que deben hacerse en el momento de la compilación , la versión "port" puede ser más aconsejable que la versión package.

    Para información sobre como puedes contribuir software a la colección de Ports, mira en Portando aplicaciones y Contribuyendo a FreeBSD en el Manual de FreeBSD>.

    Software Comercial

    Comenzando con FreeBSD Release 2.0.5, se incluyen verisones demo de algunas apliaciones comerciales así como productos shareware. Además de versiones demo disponibles - en la distribución de FreeBSD, diferentes fabricantes de + en la distribución de FreeBSD, diferentes fabricantes de software ofrecen productos específicos de FreeBSD.

    &footer; diff --git a/es/y2kbug.sgml b/es/y2kbug.sgml index a8bae3a913..326a27be5f 100644 --- a/es/y2kbug.sgml +++ b/es/y2kbug.sgml @@ -1,262 +1,263 @@ - + + %navincludes; %includes; ]> - + &header;

    A medida que se va entendiendo el problema del año 2000, - más y más compañías están + más y más compañías están demandando informes oficiales de los proveedores de hardware y software, de como sus productos responderán frente al cambio de milenio.

    Las organizaciones que usan sistemas operativos unix como FreeBSD están un paso por delante del problema. FreeBSD mantendrá sin problemas las fechas posteriores al año 2000.

    Más información

    (Esta sección está basada en el texto de Linux Y2K compliance - )

    - -

    Como en todos los sistemas operativos Unix, la hora y fecha se + )

    + +

    Como en todos los sistemas operativos Unix, la hora y fecha se representa internamente como el número de segundos transcurridos desde el 1 de Enero de 1970 (la "época" Unix). Actualmente, esta figura se almacena en un entero de 32 bits, desbordandose sobre el año 2038. Para entonces esperamos (seguro) usar un contador de 64 bits (o mayor) el cual no daría problemas hasta el fin del universo.

    -

    Ten en cuenta que un sistema operativo sin el problema Y2K no +

    Ten en cuenta que un sistema operativo sin el problema Y2K no solucionará las aplicaciones que no sean Y2k.

    De la misma manera, el sistema operativo espera leer la fecha y hora actual del reloj CMOS de tu computador. No todos estos dispositivos manejan correctamente el año 2000. Recomendamos que testees cada plataforma independientemente para asegurar que el reloj de tu hardware - soporta sin problemas el paso del año 1999 al 2000, y que + soporta sin problemas el paso del año 1999 al 2000, y que éste es interpretado correctamente.

    Qué puedes hacer.

    -

    FreeBSD continuaráa manteniendo correctamente tanto la +

    FreeBSD continuaráa manteniendo correctamente tanto la fecha como la hora durante el próximo siglo. Aplicaciones de terceras partes, quizás no lo hagan. Tu mejor defensa frente a los problemas del 2000 es un buen ataque. Escuchar las historias clamando el final del mundo pensamos que no es la mejor manera de hacer frente al problema. El proyecto FreeBSD te recomienda realizar comprobaciones de tus sistemas antes de la llegada del 2000.

    Hay tests que puedes usar para comprobar la respuesta de tu sistema. Pon el reloj de tu computador a unos minutos antes de la media noche del nuevo año y comprueba la fecha. Tu sistema - debería mostrar el año 2000 y no el 1900. Si el + debería mostrar el año 2000 y no el 1900. Si el año mostrado es incorrecto, tendrás bastante tiempo por delante para actualizar el hardware. Operar los sistemas de - información de tu organización durante unos + información de tu organización durante unos días con la fecha adelantada, puede darte una idea real de lo que ocurrirá en el cambio del año.

    - Importante: No hagas esto en - sistemas en producción. Puedes confundir y tener muchos + Importante: No hagas esto en + sistemas en producción. Puedes confundir y tener muchos problemas en aplicaciones que utilizan las fechas (sistemas de facturación, regímenes de copias, etc). Utiliza siempre para este tipo de pruebas máquinas de desarrollo las cuales no puedan afectar datos importantes.

    Estado del Y2K en FreeBSD

    - +

    "Después de extensos análisis y tests, creemos que FreeBSD es 100% compatible con el Y2K. En caso de que algo se nos haya pasado por alto, haremos todo lo posible para fijar el problema lo antes posible."

    - +

    David Greenman
    Arquitecto Principal, The FreeBSD project

    Problemas solucionados

    - +

    Los siguientes problemas Y2K han sido identificados y solucionados en FreeBSD.

    misc/1380
    Muchos programas tenían incluido de manera fija el formato 19%d para el año. Los programas afectados incluyen: yacc, ftpd, y make. [Solucionado: yacc v1.2 1999/01/18; ftpd v1.7 1996/08/05; make v1.4 1996/10/06]
    conf/1382
    -
    El script sed de /etc/rc.local que crea la línea del - host/kernel ID para el mensaje del día depende de que el +
    El script sed de /etc/rc.local que crea la línea del + host/kernel ID para el mensaje del día depende de que el año no sobrepase el 1999. [Solucionado: v1.21 1996/10/24]
    misc/3465
    El comando etc/namedb/make-localhost genera el número serial del DNS como YYMMDD. En el año 2000, éste será generado como 1YYMMDD.[Solucionado v1.2 1997/08/11]
    gnu/4930 y gnu/8321
    Las macros groff tenían integrado 19 para generar algunas fechas. [Solucionado: tmac.e v1.3 1998/12/06; doc-common v1.10 1999/01/19]
    bin/9323
    El comando touch no trata correctamente los dos digitos del año. Los años en el rango 00-68 son tratados como 1900-1968 en lugar de 2000-2068. [Solucionado: v1.7 1999/01/05]
    xntpd/parse/util/dcfd.c
    -
    El cálculo de años bisiestos para el número de - días en un año, y la conversión del tiempo DFC77 - a segundos desde el Epoch era incorrecta. Estos errores afectaban a +
    El cálculo de años bisiestos para el número de + días en un año, y la conversión del tiempo DFC77 + a segundos desde el Epoch era incorrecta. Estos errores afectaban a todos los años. [Solucionado: v1.6 1999/01/12]
    tar/getdate.y
    La función convert() tenía fijado el uso de dos dígitos en el año para el rango 70-99. Ha sido ajustada para permitir años de dos dígitos para for 1970-2069. - La función no permite usar años bisiestos - + La función no permite usar años bisiestos - alerta y2k1!. [Solucionado: v1.4 1999/01/12]
    fetch/http.c
    El protocolo HTTP incluye un formato de fecha obsoleto que usa un año de dos dígitos. Las versiones anteriores de fetch interpretaban todas las fechas en 1900s; con esta revisión, se usa la recomendación de la RFC 2068. [Solucionado: v1.24 1999/01/15]
    misc/9500
    El script `edithook' en el directorio CVSROOT usa tm_year y - mostraría 01/01/100 en el 2000-JAN-01. + mostraría 01/01/100 en el 2000-JAN-01. [Solucionado: v1.2 1999/01/17]
    bin/9501
    -
    Muchos de los ficheros "cvs contrib" tienen el problema del +
    Muchos de los ficheros "cvs contrib" tienen el problema del año 2000. Los scripts log.pl y sccs2rcs.csh añaden 19 al año, resultando en mostrar 19100 para el 2000. El script log_accum.pl usa un año de 2 dígitos en un lugar y en otro asume que tm_year es el año dentro del siglo en lugar de año desde 1900. [Solucionado: log.pl v1.2 1999/01/15; sccs2rcs.csh v1.3 1999/01/15]
    bin/9502
    -
    El registro numérico de groff `yr' es asignado desde +
    El registro numérico de groff `yr' es asignado desde (struct tm).tm_year representando el número de años desde 1900, no el año dentro del siglo (mirar la definición en troff/input.cc). - [Solucionado: ahora usa mod 100, input.cc V1.2 1999/06/03] + [Solucionado: ahora usa mod 100, input.cc V1.2 1999/06/03]
    bin/9503
    El programa simple_httpd de PicoBSD usa tm_year y mostrará 01/01/100 para 2000-JAN-01. [Solucionado: v1.2 1999/01/16]
    bin/9505
    Adduser usa tm_year y mostrará 01/01/100 para 2000-JAN-01. [Solucionado: v1.42 1999/01/15]
    bin/9506
    Cron usa tm_year y mostrará 01/01/100 para 2000-JAN-01. [Solucionado: v1.7 1999/01/16]
    -
    bin/9507
    +
    bin/9507
    tcpslice(8) usa tm_year y mostraráa 100y01m01d... para - 2000-JAN-01. Por compatibilidad, usa un año de dos + 2000-JAN-01. Por compatibilidad, usa un año de dos dígitos hasta el 2000. [Solucionado: v1.8 1999/01/20]
    - +

    Aplicaciones Problemáticas

    ports/7681
    -
    TkDesk 1.0 tiene integrado un 19 en el fichero de lista de +
    TkDesk 1.0 tiene integrado un 19 en el fichero de lista de ventanas. Un fichero con fecha > 2000 se muestra como "191xx" donde xx son los dos últimos núros de la fecha real. Este error ha sido fijado en la versión 1.1.
    ports/9295
    INN 1.7.2 tiene varios problemas relacionados con Y2K. Uno ocurre cuando purgamos las news (option -f del nntpget) y otro está relacionado con la cabecera Expire con fechas relativas pasado el año 2000. [Ports INN actualizados a INN 2.2 1999/05/02]
    -
    ports/9298
    -
    Knews tiene varios problemas relacionados con Y2K. Uno ocurre +
    ports/9298
    +
    Knews tiene varios problemas relacionados con Y2K. Uno ocurre durante la generación del comando NNTP NEWGROUPS. El otro ocurre por que knews no piensa que el 2000 es una año bisiesto. Ambos están solucionados en knews-1.0b.1. [Port actualizado 1999/01/07]
    ports/9300
    -
    Nntp-t5 tiene un problema de Y2K durante la generación del +
    Nntp-t5 tiene un problema de Y2K durante la generación del comando NEWNEWS. [Port parcheado 1999/01/05]
    ports/11144
    -
    El port tiff tiene fijado 19xx. Aunque esté en la +
    El port tiff tiene fijado 19xx. Aunque esté en la sección contrib (para convertir el formato de SUN a TIFF), y no es instalado por defecto, debería ser solucionado. [Solucionado: 1999/04/18]
    ports/11145
    El port dgs tiene el mismo problema que el port tiff. [Solucionado: 1999/04/18]

    Más información

    Si tienes alguna pregunta sobre la compatibilidad de FreeBSD con el año 2000, o has descubierto alguna aplicación ejecutada bajo FreeBSD que no cumple con Y2K, por favor, ponte en contacto con nosotros en la dirección freebsd-bugs@FreeBSD.ORG.

    &footer;