Version 6.0.0 (2006-09-24)
Copyright © 2006 Red Hat, Inc. y otros
This document is released under the terms of the Open Publication License. For more details, read the full legalnotice in Sección 3, “Legal Notice”.
![]() |
Latest Release Notes on the Web |
---|---|
These release notes may be updated. Visit http://fedora.redhat.com/docs/release-notes/ to view the latest release notes for Fedora Core. |
Historial de revisiones | ||
---|---|---|
Revisión 6.0.0 | 2006-09-24 | |
Poner nueva versión para el final | ||
Revisión 5.92 | 2006-09-05 | |
Poner nueva versión para test3 | ||
Revisión 5.91.2 | 2006-08-13 | |
Preparar una nueva foto para la versión Web | ||
Revisión 5.91.1 | 2006-08-10 | |
Corregir información de los dueños del copyright | ||
Revisión 5.91 | 2006-07-13 | |
Traer el número de versión en línea con la realidad | ||
Revisión 0.5.9.1 | 2006-07-11 | |
Levantamiento de FC6 test2 para traducción |
El Proyecto Fedora es un proyecto de código abierto auspiciado por Red Hat y soportado por la comunidad. Su objetivo es el progreso rápido del software libre y de código abierto y su contenido. El Proyecto Fedora hace uso de foros públicos, procesos abierto, innovación rápida, meritocracia y transparencia en la búsqueda del mejor sistema operativo y plataforma que pueda proveer el software libre y de código abierto.
![]() |
Ultimas Notas de la Versión en la Web |
---|---|
These release notes may be updated. Visit http://docs.fedoraproject.org/release-notes/ to view the latest release notes for Fedora. |
You can help the Fedora Project community continue to improve Fedora if you file bug reports and enhancement requests. Refer to http://fedoraproject.org/wiki/BugsAndFeatureRequests for more information about bugs. Thank you for your participation.
Para buscar más información general acerca de Fedora, vaya a las siguientes páginas web
Fedora Overview (http://fedoraproject.org/wiki/Overview)
Fedora FAQ (http://fedoraproject.org/wiki/FAQ)
Help and Support (http://fedoraproject.org/wiki/Communicate)
Participate in the Fedora Project (http://fedoraproject.org/wiki/HelpWanted)
About the Fedora Project (http://fedoraproject.org/Overview)
![]() |
Enlaces a Documentos |
---|---|
Many links may not work properly from within the installation environment, due to resource constraints. The release notes are also available post-installation as part of the desktop Web browser's default home page. If you are connected to the internet, use these links to find other helpful information about Fedora and the community that creates and supports it. |
You can find a tour filled with pictures and videos of this exciting new release at http://fedoraproject.org/wiki/Tours/Fedora7.
This release includes significant new versions of many key components and technologies. The following sections provide a brief overview of major changes from the last release of Fedora.
This release features GNOME 2.18 and KDE 3.5.6.
Fedora 7 includes a refreshing new "Flying High" theme, which is part of a continuous team effort from the community and the Fedora Artwork Project:
In this release, the performance of yum, Pirut, and Pup have been significantly improved.
La tecnología Máquina Virtual basada en el Kernel (MVK) ha sido integrada con las herramientas de virtualización gráficas, virt-manager. MVK provee una solución de virtualización completa, y los usuarios tienen dos opciones entre KVM y Xen, junto con Qemu, en esta versión. Más sobre KVM:
The proposed plans for the next release of Fedora are available at http://fedoraproject.org/wiki/RoadMap.
Copyright (c) 2006 by Red Hat, Inc. and others. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0, available at http://www.opencontent.org/openpub/.
Garrett LeSage created the admonition graphics (note, tip, important, caution,
and warning). Tommy Reynolds <Tommy.Reynolds@MegaCoder.com>
created the callout graphics. They all may be freely redistributed with
documentation produced for the Fedora Project.
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc., are registered or pending registration in the U.S. and other countries, and are used here under license to the Fedora Project.
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat Inc. in the United States and other countries.
All other trademarks and copyrights referred to are the property of their respective owners.
Documentation, as with software itself, may be subject to export control. Read about Fedora Project export controls at http://fedoraproject.org/wiki/Legal/Export.
Gracias por tomarse el tiempo para darnos sus comentarios, sugerencias, e informes de errores a la comunidad Fedora. Haciendo eso, ayuda a mejorar el estado de Fedora, Linux y del software libre en todo el mundo.
To provide feedback on Fedora software or other system elements, please refer to http://fedoraproject.org/wiki/BugsAndFeatureRequests. A list of commonly reported bugs and known issues for this release is available from http://fedoraproject.org/wiki/Bugs/F7Common.
![]() |
Retroalimentación para las Notas de la Versión Solamente |
---|---|
Esta sección trata de la retroalimentación en las notas de la versión en sí mismas. |
Agradecemos su interés en darnos retroalimentación en estas notas de la versión. Si siente que estas notas pueden ser mejoradas de alguna manera, puede proveer su retroalimentación a los escritores de compaces. Aquí hay varias maneras de hacerlo, en orden de preferencia:
If you have a Fedora account, edit content directly at http://fedoraproject.org/wiki/Docs/Beats
Fill out a bug request using this template: http://tinyurl.com/nej3u - This link is ONLY for feedback on the release notes themselves. Refer to the admonition above for details.
Envíe un email a relnotes@fedoraproject.org
![]() |
Guía de Instalación de Fedora |
---|---|
To learn how to install Fedora, refer to http://docs.fedoraproject.org/install-guide/. |
![]() |
Las cuestiones de la instalación no se cubren en estas notas del lanzamiento |
---|---|
Si encuentra un problema o tiene alguna pregunta durante la instalación que no ha sido cubierta en estas notas de la versión, vaya a http://fedoraproject.org/wiki/FAQ y a http://fedoraproject.org/wiki/Bugs/Common. |
Anaconda is the name of the Fedora installer. This section outlines issues related to Anaconda and installing Fedora 7.
![]() |
Descarga de Archivos Grandes |
---|---|
If you intend to download the Fedora DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2 GiB in size. Tools without this limitation include wget 1.9.1-16 and above, curl, and ncftpget. BitTorrent is another method for downloading large files. For information about obtaining and using the torrent file, refer to http://torrent.fedoraproject.org/. |
Anaconda tests the integrity of
installation media by default. This function works with the CD, DVD,
hard drive ISO, and NFS ISO installation methods. The Fedora Project
recommends that you test all installation media before starting the
installation process and before reporting any installation-related
bugs. Many of the bugs reported are actually due to
improperly-burned CDs. To use this test, type linux
mediacheck at the boot:
prompt.
La función mediacheck
es altamente sensible, y puede reportar como fallado algunos discos usables. El reseultado es a menudo causado por el software de escritura de disco que no incluyen alineado cuando crean discos desde archivos ISO. Para mejores resultados con mediacheck
, arranque con la siguiente opción:
linux ide=nodma mediacheck
After you complete the mediacheck function
successfully, reboot to return DMA mode to its normal state. On many
systems, this results in a faster installation process from the
disc. You may skip the mediacheck
option when
rebooting.
![]() |
BitTorrent Automatically Verifies File Integrity |
---|---|
If you use BitTorrent, any files you download are automatically validated. If your file completes downloading, you do not need to check it. Once you burn your CD, however, you should still use mediacheck. |
You may perform memory testing before you install Fedora by entering
memtest86
at the boot:
prompt. This option
runs the Memtest86 stand alone
memory testing software in place of
Anaconda.
Memtest86 memory testing
continues until the Esc key is pressed.
![]() |
Memtest86 Availability |
---|---|
Debe arrancar desde el Disco 1 de Instalación o desde un CD de rescate para poder usar esta característica. |
Fedora 7 supports graphical FTP and HTTP installations. However, the
installer image must either fit in RAM or appear on local storage,
such as Installation Disc 1. Therefore, only systems with more than
192MiB of RAM, or which boot from Installation Disc 1, can use the
graphical installer. Systems with 192MiB RAM or less fall back to
using the text-based installer automatically. If you prefer to use
the text-based installer, type linux text at the
boot:
prompt.
Nuevo diseño gráfico para el instalador.
Anaconda now features the ability to install packages from any yum-compatible software repository.
![]() |
Soporte a Repositorio de Yum |
---|---|
Sólo se da soporte a repositorios FTP y HTTP; los repositorios en CD o NFS no son soportados actualmente. |
Anaconda usa SquashFS para comprimir y almacenar paquetes en las imágenes.
Anaconda soporta ahora instalación bajo IPv6.
Anaconda now supports installation from FireWire and USB storage devices.
Anaconda's backend, yum, has been updated to 3.0.x.
El instalador provee soporte mejorado para la arquitectura ppc64.
El instalador ahora soporta sistemas Apple Macintosh con procesadores Intel.
El instalador ahora soporta multipath.
Vera fonts are retired and replaced by DejaVu as default for the installer.
The installer is now translated in Greek, Kannada, Malayalam, Marathi, and Oriya.
Three new kickstart keywords have been added.
repo --name=<repoid> [--baseurl=<url>|--mirrorlist=<url>]
The keyword repo
specifies additional package
repositories to use for installation. The parameter
baseurl
specifies the URL for the repository, while
mirrorlist
specifies a list of mirrors. One and only
one of these options may be specified per repository definition.
services [--disabled=<list>] [--enabled=<list>]
The keyword services
modifies the default set of
services that are started in the default runlevel. The parameters
enabled
and disabled
take
comma-separated lists, with enabled
services taking
priority.
user --name=<username> [--groups=<list>] [--homedir=<homedir>] [--password=<password>] [--iscrypted] [--shell=<shell>] [--uid=<uid>]
The keyword user
creates a new user with the
specified parameters. The parameter name
is required;
all other parameters are optional.
More documentation on kickstart is available in the
anaconda package. To install it, run the command
su -c 'yum install anaconda' and read the
/usr/share/doc/anaconda*/kickstart-docs.txt
file for
more information.
Some Sony VAIO notebook systems may experience problems installing Fedora from CD-ROM. If this happens, restart the installation process and add the following option to the boot command line:
pci=off ide1=0x180,0x386
Installation should proceed normally, and any devices not detected are configured the first time Fedora is booted.
Not all IDE RAID controllers are supported. If your RAID controller is not yet supported by dmraid, you may combine drives into RAID arrays by configuring Linux software RAID. For supported controllers, configure the RAID functions in the computer BIOS.
Some servers with multiple network interfaces may not assign
eth0 to the first network interface as BIOS knows it, which can
cause the installer to try using a different network interface
than was used by PXE. To change this behavior, use the following
in pxelinux.cfg/*
config files:
IPAPPEND 2 APPEND ksdevice=bootif
The configuration options above causes the installer to use the same network interface as BIOS and PXE use. You can also use the following option:
ksdevice=link
Esta opción hace que el instalador use la primera placa de red que encuentre y que esté conectada a un switch.
Refer to http://fedoraproject.org/wiki/DistributionUpgrades for detailed recommended procedures for upgrading Fedora.
En general, las instalaciones frescas son preferidas a las actualizaciones, particularmente para sistemas que incluyen repositorios de software de terceros. Los paquetes de terceros que queden de una instalación previa pueden no funcionar como se espera en un sistema actualizado de Fedora. Si de todos modos decide realizar una actualización, la información siguiente le será de utilidad:
Before you upgrade, back up the system completely. In
particular, preserve /etc
, /home
,
and possibly /opt
and /usr/local
if
customized packages are installed there. You may wish to use a
multi-boot approach with a "clone" of the old installation on
alternate partition(s) as a fallback. In that case, create
alternate boot media, such as a GRUB boot floppy.
![]() |
Respaldo de la Configuración del Sistema |
---|---|
Backups of configurations in |
Después de completar la actualización, ejecute el siguiente comando:
rpm -qa --last > RPMS_by_Install_Time.txt
Inspeccione el final de la salida de los paquetes previos a la actualización. Elimine o actualice esos paquetes desde repositorios de terceros, o sino manéjelos como sea necesario.
This section provides notes that are specific to the supported hardware architectures of Fedora.
RPM supports parallel installation of multiple architectures of the same package. A default package listing such as rpm -qa might appear to include duplicate packages, since the architecture is not displayed. Instead, use the repoquery command, part of the yum-utils package in Fedora Extras, which displays architecture by default. To install yum-utils, run the following command:
su -c 'yum install yum-utils'
Para lostar todos los paquetes con sus arquitecturas usando rpm, use el siguiente comando:
rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"
Puede agregar esto a /etc/rpm/macros
(para una configuración a nivel de sistema) o en ~/.rpmmacros
(para una configuración específica a un usuario). Esto cambia la consulta por defecto para que liste la arquitectura:
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
This section covers specific information about Fedora and the PPC hardware platform.
CPU mínimo; PowerPC G3 / POWER3
Fedora 7 supports only the "New World" generation of Apple Power Macintosh, shipped from circa 1999 onward.
Fedora 7 also supports IBM pSeries, IBM iSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines.
Fedora 7 incluye un nuevo soporte de hardware para Genesi Efika, y para la Sony PlayStation 3.
Para modo texto se recomienda: 233 MHz G3 o mejor, 128MB RAM.
Para gráficos: 400 MHz G3 o mejor, 256 MB RAM.
The disk space requirements listed below represent the disk
space taken up by Fedora 7 after installation is complete.
However, additional disk space is required during installation
to support the installation environment. This additional disk
space corresponds to the size of
/Fedora/base/stage2.img
(on Installation
Disc 1) plus the size of the files in /var/lib/rpm
on the installed
system.
In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space.
También se necesita espacio adicional para los datos del usuario, y se debe reservar al menos un 5% de espacio libre para el funcionamiento adecuado del sistema.
Después de un breve experimento con páginas de 64KiB en Fedora Core 6, el kernel de PowerPC64 fue vuelto a páginas de 4KiB. El instalador debe reformatear todas las particiones swap automáticamente durante la actualización.
The Option key on Apple systems is equivalent to the Alt key on the PC. Where documentation and the installer refer to the Alt key, use the Option key. For some key combinations you may need to use the Option key in conjunction with the Fn key, such as Option-Fn-F3 to switch to virtual terminal tty3.
Fedora Installation Disc 1 is bootable on supported hardware. In
addition, a bootable CD image appears in the images/
directory of this disc.
These images behave differently according to your system
hardware:
On most machines, the bootloader automatically boots the appropriate 32-bit or 64-bit installer from the install disc. The default gnome-power-manager package includes power management support, including sleep and backlight level management. Users with more complex requirements can use the apmud package. To install apmud after installation, use the following command:
su -c 'yum install apmud'
IBM pSeries de 64 bit (POWER4/POWER5), modelos actuales iSeries. After using OpenFirmware to boot the CD, the bootloader, yaboot, automatically boots the 64-bit installer.
iSeries "Legadas" de IBM (POWER4).
So-called "Legacy" iSeries models, which do not use
OpenFirmware, require use of the boot image located in the
images/iSeries
directory of the installation tree.
CHRP de 32-bit (IBM RS/6000 y otros).
After using OpenFirmware to boot the CD, select the
linux32
boot image at the
boot:
prompt to start the 32-bit
installer. Otherwise, the 64-bit installer starts and
fails.
Genesi Pegasos II. Al momento de escribir este documento, el firmware con soporte completo de los sistemas de archivo ISO9660 no ha sido publicado para Pegasos. Sin embargo, puede usar la imágen de arranque de red. En el indicador OpenFirmware ingrese el siguiente comando:
boot cd: /images/netboot/ppc32.img
You must also configure OpenFirmware on the Pegasos manually
to make the installed Fedora system bootable. To do this,
set the boot-device
and
boot-file
environment variables
appropriately.
Genesi Efika. Al momento de escribir esto, el firmware de Efika tenía errores que impedían la correcta operación del gestor de arranque yaboot. Un firmware actualizado debe estar disponible en Abril de 2007, antes del lanzamiento de Fedora 7. Con un firmware corregido, la instalación en Efika debe ser similar a las de Pegasos II.
Sony PlayStation 3. Para la instalación en PlayStation 3, primero actualice al firmware 1.60 o posterior. El gestor de arranque "Other OS" debe ser instalado en el flash, siguiendo las instrucciones de http://www.playstation.com/ps3-openplatform/manual.html. Al momento de escribir esto, un gestor de arranque específico para Fedora no está todavía disponible; para el momento del lanzamiento de Fedora 7, esta ausencia debería ser resuelta.
Arranque desde la Red.
Combined images containing the installer kernel and
ramdisk are located in the images/netboot/
directory
of the installation tree. They are intended for network
booting with TFTP, but can be used in many ways.
El cargador yaboot soporta arranque TFTP para las IBM pSeries y la Apple Macintosh. El Proyecto Fedora aconseja usar las imágenes yaboot en vez de las imágenes netboot.
This section covers specific information about Fedora and the x86 hardware platform.
In order to use specific features of Fedora 7 during or after installation, you may need to know details of other hardware components such as video and network cards.
The following CPU specifications are stated in terms of Intel processors. Other processors, such as those from AMD, Cyrix, and VIA that are compatible with and equivalent to the following Intel processors, may also be used with Fedora.
Fedora 7 requires an Intel Pentium or better processor, and is optimized for Pentium 4 and later processors.
Para modo texto se recomienda: Pentium 200 MHz o mejor
Para gráficos: 400 MHz Pentium II o mejor
RAM mínimo para modo texto: 128 MB
Mínimo de RAM para gráficos: 192 MB
RAM recomendado para gráficos: 256 MB
The disk space requirements listed below represent the disk
space taken up by Fedora 7 after the installation is complete.
However, additional disk space is required during the
installation to support the installation environment. This
additional disk space corresponds to the size of
/Fedora/base/stage2.img
on Installation
Disc 1 plus the size of the files in /var/lib/rpm
on the installed
system.
In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space.
También se necesita espacio adicional para los datos del usuario, y se debe reservar al menos un 5% de espacio libre para el funcionamiento adecuado del sistema.
This section covers specific information about Fedora and the x86_64 hardware platform.
In order to use specific features of Fedora 7 during or after installation, you may need to know details of other hardware components such as video and network cards.
RAM mínimo para modo texto: 128 MB
Mínimo de RAM para gráficos: 256 MB
RAM recomendado para gráficos: 512 MB
The disk space requirements listed below represent the disk
space taken up by Fedora 7 after the installation is complete.
However, additional disk space is required during the
installation to support the installation environment. This
additional disk space corresponds to the size of
/Fedora/base/stage2.img
on Installation
Disc 1 plus the size of the files in /var/lib/rpm
on the installed
system.
In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space.
También se necesita espacio adicional para los datos del usuario, y se debe reservar al menos un 5% de espacio libre para el funcionamiento adecuado del sistema.
El lanzamiento de Fedora incluye varias imágenes ISO vivas, además de las imágenes de instalación tradicionales. Estas imágenes ISO son arrancables, y las puede grabar en discos para probar Fedora. También incluye una característica que le permite instalar el contenido del CD vivo en su disco para persistencia y una performance más alta.
Estas imágenes están también disponibles para los lanzamientos de prueba, para permitir probar más fácilmente una versión de prueba (test) de Fedora.
Hay tres imágenes vivas disponibles para Fedora 7.
CD de Escritorio para i386 de Fedora 7. Esta es una imágen del tamaño de un CD para máquinas i386. Tiene por defecto el entorno de escritorio (GNOME), soporta todas las regiones de Fedora y es un conjunto básico de todas las aplicaciones de productividad disponibles en Fedora.
DVD de Escritorio para x86_64 de Fedora 7. Esta es una imágen del tamaño de un DVD para máquinas x86_64. Tiene el mismo conjunto de paquetes que el CD de Escritorio para i386.
CD con KDE para i386 de Fedora 7. Esta es una imágen del tamaño de un CD para máquinas i386. Incluye el entorno de escritorio KDE y un conjunto grande de aplicaciones KDE. Tome nota que esta imágen solamente tiene soporte completo para el idioma Inglés.
Las imágenes vivas deben arrancar en cualquier computadora que tenga soporte para arrancar desde un CD-ROM. Luego de arrancar desde el CD, puede ingresar y usar el entorno de escritorio como un usuario de fedora. Luego de ingresar, si desea instalar el contenido de la imágen a su disco rígido, haga clic en el ícono Instalar en el Disco Rígido del escritorio.
Otra forma de usar estas imágenes vivas es ponerlas en un disco USB (pendrives). Para hacerlo, instale el paquete livecd-tools del repositorio de desarrollo. Luego ejecute el script livecd-iso-to-stick:
/usr/bin/livecd-iso-to-stick /path/to/live.iso /dev/sdb1
Reemplace /dev/sdb1
con la partición donde quiere poner la imágen.
Este no es un proceso destructivo; cualquier dato que tenga en su disco USB seguirá ahí.
Los siguientes items son diferentes en las imágenes viva respecto a los de una instalación normal de Fedora.
El servicio sshd está deshabilitado, dado a que las contraseñas en las imágenes vivas son nulas.
NetworkManager está habilitado por defecto.
The following sections contain information regarding software packages that have undergone significant changes for Fedora 7. For easier access, they are generally organized using the same groups that are shown in the installation system.
El Directorio del Proyecto Fedora inició una auditoría de licencia para asegurar que todo el software incluído en Fedora está de acuerdo con los lineamientos de licenciamiento de paquetes.
El paquete apcupsd ha sido actualizado a la versión 3.14.0. Esta versión elimina la vieja modalidad de red maestro/esclavo. Vaya a las notas del lanzamiento de apcupsd para más información.
http://sourceforge.net/project/shownotes.php?group_id=54413&release_id=485633
![]() |
Presunciones Basadas en 2.6.21 |
---|---|
Este borrador de las notas del lanzamiento asumen que el lanzamiento final de Fedora 2.6.21 está basado en el kernel 2.6.21. Esto está sujeto a cambios. |
This section covers changes and important information regarding the 2.6.21 based kernel in Fedora 7. The 2.6.21 kernel includes:
Support for KVM virtualization.
Soporte para tickless en x86 32 bit, lo que mejora notablemente la administración de energía. Para el lanzamiento final de Fedora 7, x86_64 también debería ser tickless.
La pila de red inalámbrica devicescape, que incluye soporte para varios nuevos controladores inalámbricos.
Los controladores IDE que usan el mismo código libata que los controladores SATA.
![]() |
Los Nombres de Dispositivos IDE Cambiaron |
---|---|
Los nuevos controladores IDE usan nombres de dispositivos /dev/sdX para discos IDE en vez de /dev/hdX. |
Soporte para la versión 2 del Sistema de Archivo Global (GFS2).
Algunos elementos del proyecto del kernel de tiempo real.
Many bug fixes and other small improvements.
El registro de cambio para 2.6.21rc1 está disponible aquí: http://lwn.net/Articles/223021/
Fedora may include additional patches to the kernel for improvements, bug fixes, or additional features. For this reason, the Fedora kernel may not be line-for-line equivalent to the so-called vanilla kernel from the kernel.org web site:
Para obtener una lista de estos parches, descargue el paquete RPM con las fuentes y ejecute el siguiente comando contra éste:
rpm -qpl kernel-<version>.src.rpm
Para obtener un registro de los cambios al paquete, ejecute el siguiente comando:
rpm -q --changelog kernel-<version>
If you need a user friendly version of the changelog, refer to http://wiki.kernelnewbies.org/LinuxChanges. A short and full diff of the kernel is available from http://kernel.org/git. The Fedora version kernel is based on the Linus tree.
Customizations made for the Fedora version are available from http://cvs.fedoraproject.org.
Fedora 7 includes the following kernel builds:
Native kernel, for use in most systems. Configured sources are available in the kernel-devel-<version>.<arch>.rpm package.
The kernel-PAE, for use in 32-bit x86 systems with > 4GB of RAM, or with CPUs that have an 'NX (No eXecute)' feature. This kernel support both uniprocessor and multi-processor systems.
Virtualization kernel for use with the Xen emulator package. Configured sources are available in the kernel-xen-devel-<version>.<arch>.rpm package.
The kdump kernel for use with kexec/kdump capabilities. Configured sources are available in the kernel-kdump-devel-<version>.<arch>.rpm package.
You may install kernel headers for all kernel flavors at the same time. The files are installed in the /usr/src/kernels/<version>-[PAE|xen|kdump]-<arch>/ tree. Use the following command:
su -c 'yum install kernel-{PAE,xen,kdump}-devel'
Select one or more of these flavors, separated by commas and no spaces, as appropriate. Enter the root password when prompted.
![]() |
El Kernel de 32bit Incluye Kdump |
---|---|
El kernel de 32bit es ahora reubicable, por lo que la funcionalidad kdump es incluída ahora. En 64bit todavía se requiere la instalación del kernel -kdump. |
![]() |
El kernel por defecto provee SMP |
---|---|
There is no separate SMP kernel available for Fedora on i386, x86_64, and ppc64. Multiprocessor support is provided by the native kernel. |
![]() |
Soporte para PowerPC en el Kernel |
---|---|
There is no support for Xen or kdump for the PowerPC architecture in Fedora. 32-bit PowerPC does still have a separate SMP kernel. |
Refer to http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html for information on reporting bugs in the Linux kernel. You may also use http://bugzilla.redhat.com for reporting bugs that are specific to Fedora.
Many of the tutorials, examples, and textbooks about Linux kernel
development assume the kernel sources are installed under the
/usr/src/linux/
directory. If you make a symbolic
link, as shown below, you should be able to use those learning
materials with the Fedora packages. Install the appropriate kernel
sources, as shown earlier, and then run the following command:
su -c 'ln -s /usr/src/kernels/<version>.<release>-<arch> /usr/src/linux'
Enter the root password when prompted.
Fedora 7 does not include the kernel-source package provided by older versions since only the kernel-devel package is required now to build external modules. Configured sources are available, as described in the kernel flavors section.
![]() |
Las instrucciones se refieren al Kernel Actual |
---|---|
To simplify the following directions, we have assumed that you want to configure the kernel sources to match your currently-running kernel. In the steps below, the expression <version> refers to the kernel version shown by the command: uname -r. |
Users who require access to Fedora original kernel sources can find them in the kernel .src.rpm package. To create an exploded source tree from this file, perform the following steps:
![]() |
No construya paquetes como super usuario (root) |
---|---|
Building packages as the superuser is inherently dangerous and is not
required, even for the kernel. These instructions allow you to install
the kernel source as a normal user. Many general information sites refer
to |
Prepare an RPM package building environment in your home directory. Run the following commands:
su -c 'yum install rpmdevtools yum-utils' rpmdev-setuptree
Enter the root password when prompted.
Download the kernel-<version>.src.rpm
file.
Enable any appropriate source repositories, such as Core,
Updates, or Testing, with the -e
switch:
yumdownloader -e core-source -e updates-source --source kernel-<version>
Ingrese la contraseña de root cuando se le pregunte. Si no especifica la versión, el último kernel disponible en Fedora es descargado.
Install kernel-<version>.src.rpm
using the
command:
su -c 'rpm -Uvh kernel-<version>.src.rpm'
This command writes the RPM contents into
${HOME}/rpmbuild/SOURCES
and
${HOME}/rpmbuild/SPECS
, where
${HOME}
is your home directory.
![]() |
Espacio Necesario |
---|---|
El proceso de construcción del kernel completo puede requerir varios gigabytes de espacio extra en el sistema de archivo que contenga su directorio home. |
Prepare las fuentes del kernel usando los comandos:
cd ~/rpmbuild/SPECS rpmbuild -bp --target $(uname -m) kernel-2.6.spec
The kernel source tree is located in the
~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch>
directory.
The configurations for the specific kernels shipped in Fedora
7 are in the
~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch>/configs
directory. For example, the i686 configuration file is named
~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch>/configs/kernel-<version>-i686.config
.
Issue the following command to place the desired configuration
file in the proper place for building:
cp configs/<desired-config-file> .config
Every kernel gets a name based on its version number. This is
the value the uname -r
command displays. The
kernel name is defined by the first four lines of the kernel
Makefile
. The Makefile
has been
changed to generate a kernel with a
different name from that of the running
kernel. To be accepted by the running kernel, a module must be
compiled for a kernel with the correct name. To do this, you
must edit the kernel Makefile
.
Por ejemplo, si el comando uname -r
devuelve la cadena 2.6.17-1.2345_FC6
, cambie la definición de EXTRAVERSION
con esto:
EXTRAVERSION = -prep
a esto:
EXTRAVERSION = -1.2345_FC6
Es decir, sustituya todo desde el guion final en adelante.
Ejecute el siguiente comando:
make oldconfig
A continuación, proceda como lo hace siempre.
![]() |
Construcción de los RPMs de Binarios del Kérnel |
---|---|
Normalmente, los kernel para Fedora se contruyen usando el utilitario rpmbuild y un archivo de especificaciones .spec. Sus resultados pueden variar si usa un kernel construído con make rpm. |
An exploded source tree is not required to build a kernel module, such as your own device driver, against the currently in-use kernel. Only the kernel-devel package is required to build external modules. If you did not select it during installation, use Pirut to install it (via ) or use yum to install it. Run the following command to install the kernel-devel package using yum.
su -c 'yum install kernel-devel'
Por ejemplo, para construir el módulo foo.ko
, crear el siguiente Makefile
en el directorio que contenga el archivo foo.c
:
obj-m := foo.o KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd) default: $(MAKE) -C $(KDIR) M=$(PWD) modules
Emita el comando make para construir el módulo foo.ko
.
Esta sección detalla los cambios que afectan a los usuarios del escritorio gráfico de Fedora.
Este lanzamiento de Fedora incluye ahora la nueva estructura de directorios comúnes del usuario, xdg-user-dirs
. Entre sus características se incluyen:
Los nombres de directorios pueden ser regionalizados (traducidos)
Se incluye un conjunto de directorios comúnes por defecto, tales como los de documentos, música, fotos y descargas.
Aparecen como marcadores comúnes en el navegador de archivo, y son elegidos por muchas aplicaciones como directorios por defecto. Por ejemplo, un reproductor de música iniciaría el diálogo de apertura de archivo en el directorio de música por defecto.
Configurable por los usuarios, que pueden mover o renombrar los directorios a través del administrador de archivos Nautilus, o editando ~/.config/user-dirs.dirs
.
The performance for the yum software management utility has been greatly improved in Fedora 7. The repository metadata parser has now been implemented in C. A new mirror management infrastructure also ensures better mirror selection and, in most cases, faster performance. The Pirut package management tool and the Pup software update utility are based on yum, so their performance is likewise improved.
This release features GNOME 2.18 (http://www.gnome.org/start/2.18/)
La pantalla splash de GNOME ha sido deshabilitada intencionalmente. Para habilitarla, use gconf-editor o el siguiente comando:
gconftool-2 --set /apps/gnome-session/options/show_splash_screen --type bool true
El tema del diálogo para bloquear pantalla no eestá conectado al protector de pantalla en esta versión. Para habilitarlo, use gconf-editor o el siguiente comando:
gconftool-2 --set --type string /apps/gnome-screensaver/lock_dialog_theme "system"
Este lanzamiento de Fedora incluye la versión 2.0 del navegador web popular Firefox. Vaya a http://firefox.com/ para más información acerca de Firefox.
Fedora 7 provides basic support for encrypted swap partitions and
non-root file systems. To use it, add entries to
/etc/crypttab
and reference the created devices in
/etc/fstab
.
![]() |
No hay soporte para Sistema de Archivo Encriptado durante la Instalación |
---|---|
Enable file system encryption after installation. Anaconda does not have support for creating encrypted block devices. |
El siguiente ejemplo muestra una entrada ejemplo de /etc/crypttab
para una partición swap:
my_swap /dev/hdb1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
This creates an encrypted block device
/dev/mapper/my_swap
, which can be referenced in
/etc/fstab
. The next example shows an entry for a
filesystem volume:
my_volume /dev/hda5 /etc/volume_key cipher=aes-cbc-essiv:sha256
The /etc/volume_key
file contains a plaintext
encryption key. You can also specify none
as the key
file name, and the system instead asks for the encryption key during
boot.
El método que se recomienda usar para volúmenes de sistemas de archivo es LUKS: (usando LUKS se puede pasar el cipher=
a crypttab
).
Crear el volúmen encriptado usando cryptsetup luksFormat
Agregue la entrada necesaria a /etc/crypttab
Configure el volumen manualmente usando cryptsetup luksOpen o reinicie
Crear un sistema de archivo en el volúmen encriptado
Configurar una entrada en /etc/fstab
Fedora 7 includes version 2.2.4 of the Apache HTTP Server. Users upgrading from version 2.0 (included in Fedora Core 4 and earlier) must make changes to their httpd configuration; refer to http://httpd.apache.org/docs/2.2/upgrading.html for more details.
Los usuarios del módulo mod_dbd
notarán que el controlador DBD para PostgreSQL apr-util
es ahora distribuido como un módulo cargado dinámicamente. El módulo controlador se incluye ahora en el paquete apr-util-pgsql. Un controlador MySQL está ahora disponible, en el paquete apr-util-mysql.
This section concerns electronic mail servers or mail transfer agents (MTAs).
The exim-sa package is deprecated since Fedora Extras 6. It was the original implementation of SpamAssassin integration with Exim, and was functionally similar to sendmail milters or postfix filters. However, that functionality is rather limited, and Exim now has far better support for content checking, fully integrated into its general-purpose Access Control Lists.
Since the sa_exim
feature was not enabled in the
default configuration, the package can normally be safely
uninstalled to allow Exim to be upgraded. Users who have modified
their configuration to use sa_exim
features should
either reconfigure to use Exim's full content scanning abilities
or rebuild the package for themselves to include the
exim-sa subpackage. For further details on Exim's
built-in content scanning, refer to the Exim documentation:
http://www.exim.org/exim-html-4.62/doc/html/spec_html/ch40.html
Esta sección cubre las diversas herramientas del desarrollador y sus características.
Esta versión de Fedora fue contruída usando GCC 4.1, el cual también se incluye en la distribución.
This release of Fedora includes Fedora Eclipse, based on the Eclipse SDK version 3.2.2 (http://www.eclipse.org). The "New and Noteworthy" page for the 3.2.x series of releases can be accessed at http://download.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/new_noteworthy/eclipse-news.html. Release notes specific to 3.2.2 are available at http://www.eclipse.org/eclipse/development/readme_eclipse_3.2.2.html.
The Eclipse SDK is known variously as "the Eclipse Platform," "the Eclipse IDE," and "Eclipse." The Eclipse SDK is the foundation for the combined release of ten Eclipse projects under the Callisto combined release umbrella (http://www.eclipse.org/callisto). A few of these Callisto projects are included in Fedora: CDT (http://www.eclipse.org/cdt, for C/C++ development, EMF (http://www.eclipse.org/emf) the Eclipse Modeling Framework, and GEF (http://www.eclipse.org/gef), the Graphical Editing Framework.
Muchos proyectos de terceros de Eclipse están también disponibles, incluyendo Subclipse (http://subclipse.tigris.org/) para la integración del control de versión con Subversion, PyDev (http://pydev.sf.net) para el desarrollo en Python, y PHPeclipse (http://www.phpeclipse.de/) para el desarrollo en PHP. Mylar (http://eclipse.org/mylar), una interfase del usuario enfocado en la tarea para Eclipse, está también disponible en Fedora con conectores de tarea para Bugzilla y Trac. No fue parte de Callisto pero será parte del lanzamiento Eclipse combinado con Europa que está por salir.
La asistencia para obtener más proyectos empaquetados y testearlos con GCJ es siempre bienvenida. Contacte las partes interesadas a traves de fedora-devel-java-list (http://www.redhat.com/mailman/listinfo/fedora-devel-java-list/) y/o #fedora-java en freenode.
Fedora also includes plugins and features that are particularly useful to FLOSS hackers, ChangeLog editing with eclipse-changelog, and Bugzilla interaction with eclipse-mylar-bugzilla. Our CDT package also includes the work-in-progress GNU Autotools plugin. This plugin allows end-users to use Eclipse to build and maintain C/C++ projects that use GNU autotools. Enhancements to the CDT include:
Configuración previa a la construcción
Editores especiales para los archivos de entrada de autoconf/automake
Ayuda especial para las macros de autoconf
Ayuda Hover para las funciones de biblioteca C
Una consola especial para la configuración
La última información referida a estos proyectos la puede encontrar en la página de Proyecto Eclipse de Fedora: http://sourceware.org/eclipse/.
Este lanzamiento incluye 21 paquetes de idiomas para el SDK de Eclipse. Cada idioma se empaqueta en forma separada, como ser eclipse-sdk-nls-ko para la traducción al Coreano.
Fedora Eclipse contains a patch to allow non-root users to
make use of the Update Manager functionality for installing
non-packaged plugins and features. Such plugins are installed
in the user's home directory under the .eclipse
directory. Please note, however, that these plugins do not
have associated GCJ-compiled bits and may therefore run slower
than expected.
El JRE libre de Fedora no satisface a todos los usuarios, por lo que Fedora permite la instalación de JREs alternativos. Sin embargo, existe una aclaración respecto de la instalación de JREs propietarios en máquinas de 64-bit.
The 64-bit JNI libraries shipped by default on x86_64 systems in Fedora do not run on 32-bit proprietary JREs. In other words, do not try to run Fedora's x86_64 Eclipse packages on Sun's 32-bit JRE. They fail in confusing ways. Either switch to a 64-bit proprietary JRE, or install the 32-bit version of the packages, if available. To install a 32-bit version, use the following command:
yum install <package_name>.i386
De la misma manera, las bibliotecas JNI de 32 bits que se dan por defecto en sistemas ppc64 no funcionan con un JRE de 64 bits. Para instalar la versión de 64 bits use el siguiente comando:
yum install <package_name>.ppc64
En Junio de 2007, la comunidad de Eclipse está lanzando una versión combinada con Europa, una biblioteca de características y plugins. Estará basado en la versión 3.3 del SDK de Eclipse. Este es un cambio importante, y debido a eso, Eclipse de Fedora no estará basado en Europa hasta Fedora 8. Esto significa que las aplicaciones basadas en Eclipse que son incluídas en Fedora como RSSOwl y Azureus pueden pedir versiones más nuevas si es que requieren opciones sólo disponibles en Eclipse 3.3.
This section highlights various security items from Fedora.
A general introduction to the many proactive security features in Fedora, current status, and policies is available at http://fedoraproject.org/wiki/Security.
Las páginas del proyecto SELinux tienen consejos para resolución de problemas, explicaciones y enlaces a documentación y referencias. Algunos enlaces útiles incluyen los siguientes:
New SELinux project pages: http://fedoraproject.org/wiki/SELinux
Troubleshooting tips: http://fedoraproject.org/wiki/SELinux/Troubleshooting
Frequently Asked Questions: http://docs.fedoraproject.org/selinux-faq/
Listing of SELinux commands: http://fedoraproject.org/wiki/SELinux/Commands
Details of confined domains: http://fedoraproject.org/wiki/SELinux/Domains
This release of Fedora includes a free and open source Java environment called java-gcj-compat. The java-gcj-compat collection includes a tool suite and execution environment that is capable of building and running many useful programs that are written in the Java programming language.
![]() |
Fedora Does Not Include Java |
---|---|
Java is a trademark of Sun Microsystems. java-gcj-compat is an entirely free software stack that is not Java, but may run Java software. |
The java-gcj infrastructure has three key components: a GNU Java runtime (libgcj), the Eclipse Java compiler (ecj), and a set of wrappers and links (java-gcj-compat) that present the runtime and compiler to the user in a manner similar to other Java environments.
The Java software packages in this Fedora release use the java-gcj-compat environment. These packages include OpenOffice.org Base, Eclipse, and Apache Tomcat. Refer to the Java FAQ at http://www.fedoraproject.org/wiki/JavaFAQ for more information on the java-gcj-compat free Java environment in Fedora.
![]() |
Incluya Información de Ubicación y Versión en los Reportes de Errores |
---|---|
Cuando realice un reporte de error, asegúrese de incluir la salida de los siguientes comandos: which java && java -version && which javac && javac -version |
In addition to the java-gcj-compat free software stack, Fedora lets you install multiple Java implementations and switch between them using the alternatives command line tool. However, every Java system you install must be packaged using the JPackage Project packaging guidelines to take advantage of alternatives. Once these packages are installed properly, the root user may switch between java and javac implementations using the alternatives command:
alternatives --config java alternatives --config javac
This release of Fedora includes a preview release of
gcjwebplugin, a Firefox plugin for Java applets.
gcjwebplugin is not enabled by default because although
the security implementation in GNU Classpath is being actively developed,
it is not mature enough to run untrusted applets safely. That said, the
AWT and Swing implementations in GNU Classpath are now sufficiently mature
that they can run many applets deployed on the web. Adventurous users who
want to try gcjwebplugin can read
/usr/share/doc/libgcj-4.1.2/README.libgcjwebplugin.so
,
as installed by the libgcj package. The
README
explains how to enable the plugin and the
risks associated with doing so.
Fedora includes many packages derived from the JPackage Project, which provides a Java software repository. These packages are modified in Fedora to remove proprietary software dependencies and to make use of GCJ's ahead-of-time compilation feature. Use the Fedora repositories to update these packages, or use the JPackage repository for packages not provided by Fedora. Refer to the JPackage website at http://jpackage.org for more information on the project and the software it provides.
![]() |
Mezclando Paquetes desde Fedora y JPackage |
---|---|
Investigue la compatibilidad de paquetes antes de instalar el software en ambos repositorios, el de Fedora y el de JPackage en el mismo sistema. Los paquetes incompatibles puede causar problemas complejos. |
Refer to the latest release notes pertaining to Eclipse at http://fedoraproject.org/wiki/Docs/Beats/Devel/Tools/Eclipse.
Este lanzamiento de Fedora incluye maven2, una herramienta de administración y comprensión de proyectos Java. Maven puede ser invocado con los comandos mvn y mvn-jpp. El primero hace que Maven se comporte como el Maven de subida, mientras que el último llama a mvn con propiedades adicionales que hacen la construcción fuera de línea más fácil.
El paquete maven2 en Fedora fue modificado para funcionar en modo completamente fuera de líne. Sin propiedades adicionales definidas (el mvn comando), maven2 funciona exactamente como el Maven de subida. Los usuarios pueden definir propiedades adicionales para facilitar la construcción fuera de línea, o llamar a mvn-jpp, un encapsulador que define las propiedades más usadas comúnmente en las construcciones fuera de línea. Las propiedades y los detalles de su uso se describen en el archivo /usr/share/doc/maven2-2.0.4/maven2-jpp-readme.html
, que viene en el paquete maven2-manual.
Fedora includes applications for assorted multimedia functions, including playback, recording, and editing. Additional packages are available through the Fedora Extras repository. For additional information about multimedia in Fedora, refer to the Multimedia section of the Fedora Project website at http://fedoraproject.org/wiki/Multimedia.
The default installation of Fedora includes Rhythmbox and Totem for media playback. The Fedora repositories include many other popular programs such as the XMMS player and KDE's amaroK. Both GNOME and KDE have a selection of players that can be used with a variety of formats. Third parties may offer additional programs to handle other formats.
Fedora also takes full advantage of the Advanced Linux Sound Architecture (ALSA) sound system. Many programs can play sound simultaneously, which was once difficult on Linux systems. When all multimedia software is configured to use ALSA for sound support, this limitation disappears. For more information about ALSA, visit the project website at http://www.alsa-project.org/. Users may still experience issues when multiple users log into the system. Depending upon hardware and software configurations, multiple users may not be able to use the sound hardware simultaneously.
Fedora includes complete support for the Ogg media container format and the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. These freely-distributable formats are not encumbered by patent or license restrictions. They provide powerful and flexible alternatives to more popular, restricted formats. The Fedora Project encourages the use of open formats in place of restricted ones. For more information on these formats and how to use them, refer to the Xiph.Org Foundation's web site at http://www.xiph.org/.
Fedora software repositories cannot include support for MP3 or DVD video playback or recording. The MP3 formats are patented, and the patent holders have not provided the necessary patent licenses. DVD video formats are patented and equipped with an encryption scheme. The patent holders have not provided the necessary patent licenses, and the code needed to decrypt CSS-encrypted discs may violate the Digital Millennium Copyright Act, a copyright law of the United States. Fedora also excludes other multimedia software due to patent, copyright, or license restrictions, including Adobe's Flash Player and Real Media's Real Player. For more on this subject, please refer to http://fedoraproject.org/wiki/ForbiddenItems.
While other MP3 options may be available for Fedora, Fluendo now offers a free MP3 plugin for GStreamer that has the necessary patent license for end users. This plugin enables MP3 support in applications that use the GStreamer framework as a backend. Fedora does not include this plugin since we prefer to support and encourage the use of patent unrestricted open formats instead. For more information about the MP3 plugin, visit Fluendo's website at http://www.fluendo.com/.
Fedora software repositories includes a variety of tools for easily mastering and burning CDs and DVDs. GNOME users can burn directly from the Nautilus file manager, choose the gnomebaker or graveman packages from Fedora Extras, or utilize the older xcdroast package from Fedora. KDE users can use the robust k3b package for these tasks. Console tools include cdrecord, readcd, mkisofs, and other popular applications.
You can use Fedora to create and play back screencasts, which are recorded desktop sessions, using open technologies. Fedora Extras software repository includes istanbul, which creates screencasts using the Theora video format. These videos can be played back using one of several players included in Fedora. This is the preferred way to submit screencasts to the Fedora Project for either developer or end-user use. For a more comprehensive how-to, refer to http://fedoraproject.org/wiki/ScreenCasting.
Most of the media players in Fedora software repositories can use plugins to add support for additional media formats and sound output systems. Some use powerful multimedia frameworks, like the gstreamer package, to handle media format support and sound output. Fedora software repositories offer plugin packages for these backends and for individual applications. Third parties may provide additional plugins to add even greater capabilities.
Fedora provides a selection of games that cover a variety of genres. Users can install a small package of games for GNOME (called gnome-games) and KDE (kdegames). There are also many additional games that span every major genre available in the repositories.
The Fedora Project website features a section dedicated to games that details many of the available games, including overviews and installation instructions. For more information, refer to http://fedoraproject.org/wiki/Games.
Para una lista de otros juegos disponibles para instalar, use el utilitario gráfico Pirut ( ), o por la línea de comando:
yum groupinfo "Games and Entertainment"
Para ayuda acerca del uso de yum para instalar los paquetes de juegos vaya a la guía disponible en:x
http://docs.fedoraproject.org/yum/
Fedora 7 incluye la versión 0.5.6 del motor de juegos Nazghul para roles de vieja escuela y su juego compañero Haxima. Esta versión no es compatible con los juegos guardados en versiones previas de Nazghul, por lo que aquellos con juegos abiertos de Haxima necesitan reiniciar sus juegos luego de actualizar a Fedora 7.
Virtualization in Fedora 7 is based on Xen 3.0.4 and is integrated within the Fedora installer. Refer to http://fedoraproject.org/wiki/Tools/Xen for more information about Xen.
Under Fedora using Xen 3.0.4, both paravirtualization and full virtualization can be implemented. Full virtualization requires a VT-capable processor. Paravirtualization does not require special hardware, but does require the guest OS to be modified. To learn more about how to configure and use Xen, refer to http://fedoraproject.org/wiki/FedoraXenQuickstartFC6.
The Fedora 7 development team has tested Xen with Fedora 7 and Red Hat Enterprise Linux 5 guests. Other guests have not been tested. With paravirtualization, however, users can expect reasonable success running any Linux guest OS that was built for Xen 3.0.4. With full virtualization using VT hardware, users can expect reasonable success with a larger variety of operating systems, including some proprietary operating systems.
Se realizaron las siguientes mejoras en los paquetes de virtualización en Fedora 7:
Las aplicaciones virt-manager y virsh pueden ahora trabajar con dominios inactivos. Previamente, sólo xm podía manejar dominios inactivos
Los problemas del cursor de ratón con el buffer de pantalla virtual han sido corregidos, para una mejor experiencia del usuario en modos gráficos
Se realizaron otras pequeñas mejoras y correcciones.
Esta sección contiene información relacionada con la implementación del Sistema de Ventanas X provista en Fedora.
El servidor X de X.org 7.2 ha sido modificado para que detecte automáticamente y configure la mayor parte del hardware, eliminando la necesidad de que los usuarios o administradores modifiquen el archivo de configuración /etc/X11/xorg.conf
. El único hardware configurado por defecto en el archivo xorg.conf
escrito por anaconda es:
Los controladores gráficos
El mapa del teclado
Todo otro hardware, tales como monitores (LCD y CRT), ratón USB, y touchpads deberían ser detectados y configurados automáticamente.
The X server queries the attached monitor for supported resolution ranges, and attempts to pick the highest resolution available with the correct aspect ratio for the display. Users can set their preferred resolution in
, and the default resolution for the system can be changed with .Si el archivo de configuración /etc/X11/xorg.conf
no está presente, X también detecta automáticamente el controlador apropiado, y asume que hay un teclado con el formato de 105 teclas de EEUU.
Fedora 7 contains two drivers for Intel integrated graphics controllers:
The default i810
driver, which contains support for
Intel graphics chipsets up to and including i945 and i965
The experimental intel
driver, which contains
support for Intel graphics chipsets up to and including i945
The i810
driver is limited to resolutions available
in the BIOS. If you need support for non-standard resolutions, such as
those used in some widescreen displays, you may want to switch to the
intel
driver. You may switch drivers by using
system-config-display, available in the menus under
.
We welcome feedback on the experimental intel
driver.
Please report success in Bugzilla, attaching
the full output of lspci -vn for your machine. Given
success reports, various chipsets may be switched to use the
intel
driver by default.
Si intenta usar controladores de video de terceros, vaya a la página de controladores de terceros de Xorg para los lineamientos detallados:
Fedora now provides MySQL 5.0. For a list of the enhancements provided by this version, refer to http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html.
For more information on upgrading databases from previous releases of MySQL, refer to the MySQL website at http://dev.mysql.com/doc/refman/5.0/en/upgrade.html.
El controlador DBD de MySQL ha sido liberado con licencia dual y las cuestiones relacionadas con la licencia fueron resueltas (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=222237). El paquete apr-util-mysql resultante se incluye ahora en los repositorios de software de Fedora.
This release of Fedora includes PostgreSQL 8.2. For more information on this new version, refer to http://www.postgresql.org/docs/whatsnew.
![]() |
Actualización de las Bases de Datos |
---|---|
Antes de actualizar un sistema Fedora existente con una base de datos PostgreSQL, podría se necesario que siga el procedimiento descrito en http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html. Sino los datos pueden no ser accesibles para la nueva versión de PostgreSQL. |
This section includes information on language support under Fedora.
When upgrading from earlier releases of Fedora, it is strongly recommended to install scim-bridge-gtk, which works well with 3rd party C++ applications linked against older versions of libstdc++.
When SCIM is installed, it runs by default for users of all locales. If SCIM is installed but you do not wish to run it on your desktop, disable it using im-chooser.
La siguiente tabla lista las teclas rápidas por defecto para los distintos idiomas:
Lenguaje | Teclas de activación |
---|---|
todos | Ctrl-Espacio |
Japonés | Zenkaku_Hankaku o Alt-` |
Coreano | Shift-Espacio o Hangul |
To install additional language support from the Languages group, use Pirut via , or run this command:
su -c 'yum groupinstall <language>-support'
In the command above, <language>
is one of
assamese
, bengali
,
chinese
, gujarati
, hindi
,
japanese
, kannada
,
korean
, malayalam
,
marathi
, oriya
, punjabi
,
sinhala
, tamil
, thai
, or
telegu
.
Paquete m17n-db:
Se agregó ZWNJ (U+200d) que se necesitaba en los mapas de teclado kn-* - https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221965
Se agregó el diseño itrans para Marathi - https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225561
Se agregó mapas de teclado para la fonética de Marathi y Oriya - https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225559 y https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225562
Fedora provides legacy system libraries for compatibility with older software. This software is part of the Legacy Software Development group, which is not installed by default. Users who require this functionality may select this group either during installation or after the installation process is complete. To install the package group on a Fedora system, use → (Pirut) or enter the following command in a terminal window:
su -c 'yum groupinstall "Legacy Software Development"'
Ingrese la clave de la cuenta root
cuando se le pida.
The compat-gcc-34 package has been included for compatibility reasons:
https://www.redhat.com/archives/fedora-devel-list/2006-August/msg00409.html
![]() |
Esta lista se genera automáticamente. |
---|---|
Esta lista se genera automáticamente. No es una buena idea traducirla. |
04-Apr-2007 This content is not generated for the XML output for translation. Insert this content before building the release notes for Fedora 7 test4.
This list was made using the {{{treediff}}} utility, ran as {{{treediff newtree oldtree}}} against the rawhide tree of 28 Feb. 2006.
For a list of which packages were updated since the previous release, refer to http://fedoraproject.org/wiki/Docs/Beats/PackageChanges/UpdatedPackages. You can also find a comparison of major packages between all Fedora versions at http://distrowatch.com/fedora.
Insert treediff list here.
The Fedora Legacy Project was a community-supported open source project to extend the lifecycle of select "maintenance mode" Red Hat Linux and Fedora Core distributions. The current model for supporting maintenance distributions has been re-examined. Fedora Legacy was unable to extend support to older Fedora Core releases as it had planned. As of now, Fedora Core 4 and earlier distributions are no longer being maintained. Fedora Core 5 will no longer be maintained 30 days after the Fedora 7 release.
![]() |
Legacy Repo was included in Fedora Core 6 |
---|---|
Fedora Core 6 shipped with a software repository configuration for Fedora Legacy. This repository was not enabled by default in the Fedora Core 6 release. |
The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from open source software. Development is done in a public forum. The project produces releases of Fedora approximately 2 times a year, with a public release schedule available at http://fedoraproject.org/wiki/Releases/Schedule. The Red Hat engineering team continues to participate in building Fedora and invites and encourages more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community. For more information, refer to the Fedora Project website at http://fedoraproject.org.
The Fedora Project is driven by the individuals that contribute to it. As a tester, developer, documenter, or translator, you can make a difference. See http://fedoraproject.org/wiki/Join for details. For information on the channels of communication for Fedora users and contributors, refer to http://fedoraproject.org/wiki/Communicate.
Además del sitio web, están disponibles las siguientes listas de correo:
fedora-list@redhat.com, for users of Fedora releases
fedora-test-list@redhat.com, for testers of Fedora test releases
fedora-devel-list@redhat.com, para desarrolladores, desarrolladores, desarrolladores (¿ se entiende ?)
fedora-docs-list@redhat.com, para participantes del Proyecto de Documentación
To subscribe to any of these lists, send an email with the word "subscribe"
in the subject to <listname>-request
, where
<listname>
is one of the above list names.
Alternately, you can subscribe to Fedora mailing lists through the Web
interface at http://www.redhat.com/mailman/listinfo/.
The Fedora Project also uses several IRC (Internet Relay Chat) channels. IRC is a real-time, text-based form of communication, similar to Instant Messaging. With it, you may have conversations with multiple people in an open channel, or chat with someone privately one-on-one. To talk with other Fedora Project participants via IRC, access the Freenode IRC network. Refer to the Freenode website at http://www.freenode.net/ for more information.
Fedora Project participants frequent the #fedora channel on the Freenode network, while Fedora Project developers may often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well. This information may be found on the webpage for the project, and at http://fedoraproject.org/wiki/Communicate.
In order to talk on the #fedora channel, you need to register your nickname, or nick. Instructions are given when you /join the channel.
![]() |
Canales IRC |
---|---|
El Proyecto Fedora y Red Hat no tienen control sobre los canales IRC del Proyecto Fedora o de su contenido. |
Como usamos el término, un colophon:
reconoce contribuyentes y provee un registro, y
explica las herramientas y los métodos de producción.
Amanpreet Singh Alam (translator - Punjabi)
Andrew Martynov (translator - Russian)
Andrew Overholt (beat contributor)
Anthony Green (escritor de compaces)
Brandon Holbrook (beat contributor)
Bob Jensen (escritor de compases, director editorial)
Chris Lennert (escritor de compaces)
Dave Malcolm (escritor de compaces)
David Eisenstein (escritor de compaces)
David Woodhouse (escritor de compaces)
Deepak Bhole (beat contributor)
Diego Burigo Zacarao (translator )
Dimitris Glezos (translator - Greek, tools)
Domingo Becker (traductor - Español)
Francesco Tombolini (translator - Italian)
Gavin Henry (escritor de compaces)
Hugo Cisneiros (translator - Brazilian Portuguese)
Jeff Johnston (beat contributor)
Jens Petersen (escritor de compaces)
Joe Orton (escritor de compaces)
Jose Nuno Coelho Pires (translator - Portuguese)
Josh Bressers (escritor de compaces)
Karsten Wade (escritor de compaces, editor, co-publicador)
Kyu Lee (beat contributor)
Luya Tshimbalanga (escritor de compaces)
Magnus Larrson (translator - Swedish)
Martin Ball (beat writer)
Nikos Charonitakis (translator - Greek)
Orion Poplawski (beat contributor)
Panagiota Bilianou (translator - Greek)
Patrick Barnes(escritor de compaces, editor)
Paul W. Frields (herramientas, editor)
Pawel Sadowski (traductor - Polaco)
Patrick Ernzer (beat contributor)
Rahul Sundaram (escritor de compaces, editor)
Sam Folk-Williams (beat writer)
Sekine Tatsuo (translator - Japanese)
Simos Xenitellis (traductor - Griego)
Steve Dickson (escritor de compaces)
ThomasCanniot (translator - French)
Thomas Gier (translator - German)
Thomas Graf (escritor de compaces)
Tommy Reynolds (herramientas)
Valnir Ferreira Jr. (translator - Brazilian Portuguese)
Will Woods (beat contributor)
Yoshinari Takaoka (traductor, herramientas)
Yuan Yijun (translator - Simplified Chinese)
Zhang Yang (traductor - Chino simplificado)
... y muchos más traductores. Vaya a la versión actualizada en la Web de estas notas de la versión, ya que se van agregando traductores después de esta versión:
Beat writers produce the release notes directly on the Fedora Project Wiki. They collaborate with other subject matter experts during the test release phase of Fedora to explain important changes and enhancements. The editorial team ensures consistency and quality of the finished beats, and ports the Wiki material to DocBook XML in a revision control repository. At this point, the team of translators produces other language versions of the release notes, and then they become available to the general public as part of Fedora. The publication team also makes them, and subsequent errata, available via the Web.