![]() |
To learn how to install Fedora, refer to to the Fedora Installation Guide |
|---|---|
Refer to http://docs.fedoraproject.org/install-guide/ for full instructions on installing Fedora. If you encounter a problem or have a question during installation that is not covered in these release notes, refer to http://www.fedoraproject.org/wiki/FAQ and http://www.fedoraproject.org/wiki/Bugs/Common. |
Anaconda is the name of the Fedora installer. This section outlines issues related to Anaconda and installing Fedora 10.
![]() |
Fedora DVD ISO image is a large file. |
|---|---|
|
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. The programs |
Anaconda asks if it should verify the installation medium when is selected during boot from an installation-only media.
For Fedora Live media, press any key during the initial boot countdown, to display a boot option menu. Select to perform the media test. Installation media can be used to verify Fedora Live media. Anaconda asks during the mediacheck if you want to check any other disc than the one Anaconda is running from. To test additional media, select to eject the inserted medium, then replace it with the medium you want to test instead.
Perform this test for any new installation or live medium.
The Fedora Project strongly recommends that you perform this test before reporting any installation-related bugs. Many of the bugs reported are actually due to improperly-burned CD or DVDs.
In rare cases, the testing procedure may report some usable discs as faulty. This result is often caused by disc writing software that does not include padding when creating discs from ISO files.
![]() |
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 or DVD, however,
you should still use |
Another reason for a failure during installation is faulty memory. To perform memory testing before you install Fedora, press any key to enter the boot menu, then select . This option runs the Memtest86 standalone memory testing software in place of Anaconda. Memtest86 memory testing continues until you press the Esc key.
Fedora 10 supports graphical FTP and HTTP installations.
However, the installer image must either fit in RAM or appear on
local storage, such as the installation DVD or Live Media.
Therefore, only systems with more than 192MiB of RAM or that boot
from the installation DVD or Live Media 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.
NetworkManager for Networking -- Anaconda is now using NetworkManager for configuration of network interfaces during installation. The main network interface configuration screen in Anaconda has been removed. Users are only prompted for network configuration details if they are necessary during installation. The settings used during installation are then written to the system.
For more information, refer to http://www.fedoraproject.org/wiki/Anaconda/Features/NetConfigForNM.
When using netinst.iso to boot
the installer, Anaconda defaults to
using the Fedora mirrorlist URL as the installation source.
The method selection screen no longer appears by default. If
you do not wish to use the mirrorlist URL, either add
repo= or add
<your installation
source>askmethod to the installer boot parameters.
The askmethod option causes the selection
screen to appear as it did in previous releases. To add boot
parameters, press the Tab
key in the initial boot screen and append any new
parameters to the existing list. For more information, refer
to the repo= and
stage2= descriptions at
http://fedoraproject.org/wiki/Anaconda/Options.
.iso
When PXE booting and using a .iso file
mounted via NFS for the installation media, add
repo=nfs:server:/path/ to the command
line. The install.img file also needs to be extracted and/or placed into the nfs:server:/path/images/ directory.
Use of /dev/hdX on i386 and x86_64 for
IDE drives changed to /dev/sdX in Fedora 7.
If you are upgrading from an earlier version than Fedora 7, you
need to research about the importance of labeling devices for
upgrades and any partition limitations.
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.
Pojedini serveri sa višestrukim mrežnim spregama mogu da ne dodele eth0 mrežnoj sprezi koju BIOS vidi kao prvu, što može izazvati da instalater koristi drugačiju mrežnu spregu od one koju je koristio PXE. Da biste promenili ovo ponašanje, koristite sledeće u pxelinux.cfg/* datotekama za podešavanje:
IPAPPEND 2 APPEND
ksdevice=bootif
Opcije podešavanja iznad prouzrokuju da instalater koristi istu mrežnu spregu kao što BIOS i PXE koriste. Možete takođe koristiti sledeću opciju:
ksdevice=link
Ova opcija prouzrokuje da instalater koristi prvi mrežni uređaj koji pronađe povezan na mrežni prekidač.
Refer to http://fedoraproject.org/wiki/DistributionUpgrades for detailed recommended procedures for upgrading Fedora.
Dok stariji IDE diskovi podržavaju do 63 particije po uređaju, SCSI uređaji su ograničeni na 15 particija po uređaju. Anaconda koristi novi libata upravljački program na isti način kao i ostatak Fedora-e, zato nije u stanju da pronađe više od 15 particija na IDE disku tokom procesa instalacije ili nadgradnje.
If you are upgrading a system with more than 15 partitions, you may need to migrate the disk to Logical Volume Management (LVM). This restriction may cause conflicts with other installed systems if they do not support LVM. Most modern Linux distributions support LVM and drivers are available for other operating systems as well.
A change in the way that the Linux kernel handles storage
devices means that device names such as
/dev/hdX or /dev/sdX
may differ from the values used in earlier releases.
Anaconda solves this problem by
relying on partition labels or UUIDs for finding devices. If
these are not present, then Anaconda
presents a warning indicating that partitions need to be
labelled and that the upgrade can not proceed. Systems that use
Logical Volume Management (LVM) and the device mapper usually do
not require relabeling. One exception is mirrored LVM
partitions, where the UUIDs are identical. In that case, the
partitions must be labeled.
Da biste videli oznake particija, pokrenite postojeću Fedora instalaciju i unesite sledeću naredbu u odzivniku terminala:
/sbin/blkid
Confirm that each volume line in the list has a
LABEL= value, as shown below:
/dev/hdd1: LABEL="/boot"
UUID="ec6a9d6c-6f05-487e-a8bd-a2594b854406" SEC_TYPE="ext2"
TYPE="ext3"
For ext2 and ext3 partitions without a label, use the following command:
su -c 'e2label /dev/example f7-slash'
For a VFAT file system use dosfslabel
from the dosfstools package, and for NTFS
file system use ntfslabel from the
ntfsprogs package. Before rebooting the
machine, also update the file system mount entries, and the
GRUB kernel root entry.
If any file system labels were added or modified, then the
device entries in /etc/fstab must be
adjusted to match:
su -c 'cp /etc/fstab /etc/fstab.orig' su -c 'gedit /etc/fstab'
Primer montiranja korišćenjem oznake je:
LABEL=f7-slash / ext3 defaults 1
1
grub.conf korensku stavku jezgraIf the label for the / (root)
file system was modified, the kernel boot parameter in the grub
configuration file must also be modified:
su -c 'gedit /boot/grub/grub.conf'
Odgovarajući primer za grub liniju jezgra je:
kernel /vmlinuz-2.6.20-1.2948.fc6 ro
root=LABEL=f7-slash rhgb quiet
Ako su oznake particija promenjene, ili je datoteka /etc/fstab promenjena, onda pokrenite postojeću Fedora instalaciju da biste potvrdili da se sve particije mogu montirati i da se možete uspešno prijaviti na sistem. Kada završite, pokrenite sistem sa instalacionom medijom da biste pokrenuli instalater i započeli nadgradnju.
In general, fresh installations are recommended over upgrades. This is particularly true for systems that include software from third-party repositories. Third-party packages remaining from a previous installation may not work as expected on an upgraded Fedora system. If you decide to perform an upgrade anyway, the following information may be helpful:
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 want 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.
![]() |
Configuration backups |
|---|---|
Rezerve podešavanja u |
Posle završetka nadgradnje, pokrenite sledeću naredbu:
rpm -qa --last > RPMS_by_Install_Time.txt
Pregledajte kraj ispisa za pakete koji su prethodili nadgradnji. Uklonite ili ažurirajte pakete iz riznica sa strane, ili šta god je drugo potrebno. Neki prethodno instalirani paketi možda nisu više dostupni u podešenim riznicama. Za ispis svih takvih paketa upotrebite sledeću naredbu:
su -c 'yum list extras'
Prilikom korišćenja datoteke podešavanja za Kickstart preko HTTP-a, kickstart dobavka datoteke može biti neuspešna sa greškom koja označava da se datoteka nije mogla dobaviti. Kliknite na dugme nekoliko puta bez pravljenja promena da biste se rešili ove greške. Kao zaobilaznica, koristite jedan od drugih podržani metoda za dobavku Kickstart podešavanja.
The Firstboot application requires
the creation of a non-root user for the system. This is to
support gdm no longer
allowing the root user to log in to the graphical desktop.
If a network authentication mechanism is chosen during installation, Firstboot does not require creating a non-root local user.
Pored tradicionalnih instalacionih otisaka, ovo Fedora 10 izdanje uključuje nekoliko živih ISO otisaka. Sa ovih ISO otisaka se može podići sistem, možete ih narezati na CD/DVD i upotrebiti ih radi isprobavanja novog Fedora sistema. Takođe možete sadržaj živih CD medija da instalirate na čvrsti disk radi veće upotrebljivosti i boljih performansi.
Za potpun spisak dostupnih izdanja, kao i uputstva za njihovo korišćenje, pogledajte:
To boot from the Fedora Live image, insert the media into your
computer and restart. To log in and use the desktop environment,
enter the username fedora. There is no password on
this account. The GNOME-based Fedora Live images automatically
login after one minute, so users have time to select a preferred
language. After logging in, if you wish to install the contents of
the Live image to your hard drive, click on the Install
to Hard Drive icon on the desktop.
To check Fedora Live media, press any key during the initial boot countdown to display a boot option menu. Select Verify and boot to perform the media test.
Perform this test for any new Live medium.
Možete izvršiti instalaciju Živog otiska u tekstualnom režimu upotrebom liveinst naredbe u konzoli.
Another way to use these Fedora Live images is to put them on
a USB stick. To do this, use the
liveusb-creator graphical interface. Use
to search for and
install liveusb-creator, or to install using
yum:
su -c 'yum install liveusb-creator'
Instead of the graphical tool, you can use the command line
interface from the livecd-tools package. Then,
run the livecd-iso-to-disk script:
/usr/bin/livecd-iso-to-disk /path/to/live.iso /dev/sdb1
Replace /dev/sdb1 with the partition
where you want to put the image.
Ovo nije proces koji briše podatke; podaci koje trenutno imate na USB disku biće sačuvani.
A Windows version of this tools is also available that allows users to try out or migrate to Fedora.
Support for keeping a persistent /home
with the rest of the system stateless has been added for Fedora
10. This includes support for encrypting
/home to protect your system if
your USB stick is lost or stolen. To use this feature, download the
Live image and run the following command:
livecd-iso-to-disk --home-size-mb 512 /path/to/live.iso /dev/sdb1
Replace /dev/sdb1 with the partition
where you want to put the image.
Replace 512 with the desired
size in megabytes of the persistent /home.
The livecd-iso-to-disk shell script is stored
in the LiveOS directory at the top level of
the CD image. The USB media must have sufficient free space for
the Fedora Live image, plus the /home, plus
any other data to be stored on the media. By default, this
encrypts your data and prompts for a passphrase to use. If you
want to have an unencrypted /home, then you
can specify --unencrypted-home.
Note that later runs of livecd-iso-to-disk
preserve the /home that is created on the USB
stick, continuing to use it even if you change your Live
image.
Support for persistent changes with a Fedora Live image exists for Fedora 9 and later. The primary use case is booting from a Fedora Live image on a USB flash drive and storing changes to that same device. To do this, download the Fedora Live image and then run the following command:
livecd-iso-to-disk --overlay-size-mb 512 /path/to/live.iso /dev/sdb1
Replace /dev/sdb1 with the partition
where you want to put the image.
Replace 512 with the desired
size in megabytes of the persistent data, or
overlay. The
livecd-iso-to-disk shell script is stored in
the LiveOS directory at the top level of the
CD image. The USB media must have sufficient free space for the
Fedora Live image, plus the overlay, plus any other data to be
stored on the media.
Fedora 10 includes support for putting the Live image onto a USB image and then booting it on Intel processor-based Apple hardware. Unlike most x86 machines, this hardware requires reformatting the USB stick. To set up a USB stick, run this command:
/usr/bin/livecd-iso-to-disk --mactel /path/to/live.iso /dev/sdb1
Replace /dev/sdb1 with the partition
where you want to put the image.
Note that all of the other arguments for the
livecd-iso-to-disk tool as described above can
be used here as well.
The Fedora Live image is different from a normal Fedora installation as shown below.
Fedora Live images provide a subset of packages available in the regular DVD image. Both connect to the same repository that has all the packages.
The SSH daemon sshd is disabled by default. The
daemon is disabled because the default username in the Fedora
Live images does not have a password. However, installation to
hard disk prompts for creating a new username and
password.
Fedora Live image installations do not allow any package
selection or upgrade capability since they copy the entire
file system from the Live media to the hard disk. After
the installation is complete, and your system has been
rebooted, you can add and remove packages as desired with the
tool,
yum, or the other software management
tools.
Fedora Live images do not work on i586 architecture.
Users often request that Fedora provide a hardware compatibility list (HCL), which we have carefully avoided doing. Why? It is a difficult and thankless task that is best handled by the community at large than by one little Linux distribution.
However, because of our stance against closed-source hardware drivers and the problems of binary firmware for hardware, there is some additional information the Fedora Project wants to provide Fedora users.
Za 32-bitni x86 - Section 2.4.2, “x86 posebnosti za Fedora sistem”
Za 64-bitni x86 - Section 2.4.3, “x86_64 posebnosti za Fedora sistem”
Za PowerPC (PPC)- Section 2.4.4, “PPC beleške za Fedora-u”
Sa http://fedoraproject.org/wiki/ForbiddenItems:
If it is proprietary, it cannot be included in Fedora.
If it is legally encumbered, it cannot be included in Fedora.
If it violates United States federal law, it cannot be included in Fedora.
Get active. Tell your hardware vendors you only want free, open source drivers and firmware
Use your buying power and only purchase from hardware vendors that support their hardware with open drivers and firmware. Refer to http://www.fsf.org/campaigns/hardware.html for more information.
Ovaj odeljak pruža beleške koje su naročite za podržane hardverske arhitekture u Fedora-i.
RPM podržava paralelnu instalaciju više arhitektura istog paketa. Podrazumevani ispis paketa naredbom rpm -qa može naizgled da pokaže duplirane pakete, pošto se arhitektura ne prikazuje. Umesto nje, koristite naredbu repoquery, koja je deo paketa yum-utils, koja podrazumevano prikazuje arhitekturu. Da biste instalirali yum-utils, zadajte sledeću naredbu:
su -c 'yum install yum-utils'
Za popis svih paketa sa njihovim arhitekturama koristeći rpm, pokrenite sledeću naredbu:
rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"
Ova postavka menja podrazumevani upit za ispis arhitekture. Možete je dodati u /etc/rpm/macros (kao postavku za čitav sistem) ili ~/.rpmmacros (kao postavku za korisnika).
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
Ovaj odeljak pokriva posebne informacije o Fedora sistemu i x86 hardverskoj platformi.
Za korišćenje posebnih mogućnosti tokom ili nakon instalacije sistema Fedora 10, poželjno je da poznajete detalje drugih komponenti hardvera, poput video i mrežnih karti.
Sledeće specifikacije procesora se odnose na Intel procesore. Drugi procesori, koje nude AMD, Cyrix i VIA, a usaglašeni su sa sledećim Intel procesorima, mogu se takođe koristiti uz Fedora sistem.
Fedora 10 zahteva procesor Intel Pentium ili bolji, a optimizovana je za Pentium 4 i novije procesore.
Preporučeno za tekstualni režim: klasa Pentium na 200 MHz, ili bolje
Preporučeno za grafiku: Pentium II na 400 MHz, ili bolje
Najmanji RAM za tekstualni režim: 128MB
Najmanji RAM za grafiku: 192MB
Preporučeni RAM za grafiku: 256MB
Kompletni paketi sa DVD-a mogu zauzeti preko 9 GB prostora na disku. Krajnja veličina instalacije je potpuno određena instalacionim izdanjem i paketima izabranim tokom instalacije. Dodatan prostor je neophodan tokom instalacije za podršku okruženja instalacije. Ovaj dodatni prostor odgovara veličini /Fedora/base/stage2.img plus veličini datoteka u /var/lib/rpm na instaliranom sistemu.
Praktično, zahtevi za dodatni slobodni prostor mogu biti u opsegu od 90 MB za najmanju instalaciju do čak 175 MB dodatnog prostora za veću instalaciju.
Dodatni prostor je takođe potreban za bilo koje korisničke podatke, kao i najmanje 5% prostora koje je potrebno održavati slobodnim za ispravan rad sistema.
Ovaj odeljak pokriva posebne informacije o Fedora sistemu i x86_64 hardverskoj platformi.
Za korišćenje posebnih mogućnosti tokom ili nakon instalacije sistema Fedora 10, poželjno je da poznajete detalje drugih komponenti hardvera, poput video i mrežnih karti.
Najmanji RAM za tekstualni režim: 256MB
Najmanji RAM za grafiku: 384MB
Preporučeni RAM za grafiku: 512MB
Kompletni paketi sa DVD-a mogu zauzeti preko 9 GB prostora na disku. Krajnja veličina instalacije je potpuno određena instalacionim izdanjem i paketima izabranim tokom instalacije. Dodatan prostor je neophodan tokom instalacije za podršku okruženja instalacije. Ovaj dodatni prostor odgovara veličini /Fedora/base/stage2.img plus veličini datoteka u /var/lib/rpm na instaliranom sistemu.
Praktično, zahtevi za dodatni slobodni prostor mogu biti u opsegu od 90 MB za najmanju instalaciju do čak 175 MB dodatnog prostora za veću instalaciju.
Dodatni prostor je takođe potreban za bilo koje korisničke podatke, kao i najmanje 5% prostora koje je potrebno održavati slobodnim za ispravan rad sistema.
Ovaj odeljak pokriva podatke koje treba da znate o Fedora-i i PPC hardverskoj platformi.
Najslabiji CPU: PowerPC G3 / POWER3.
Fedora 10 podržava samo najnoviju generaciju Apple Power Macintosh računara, koji se isporučuju negde od 1999. pa nadalje. Iako bi starije mašine trebalo da rade, one zahtevaju poseban pokretački program koji nije uključen u distribuciju Fedore.
Fedora 10 podržava pSeries i Cell Broadband Engine mašine.
Fedora 10 takođe podržava Sony Playstation 9 i Genesi Pegasos II i Efika.
Fedora 10 uključuje novu hardversku podršku za P.A. Semiconductor „Electra“ mašine.
Fedora 10 takođe uključuje podršku za Terrasoft Solutions radne stanice.
Preporučeno za tekst režim: 233 MHz G3 ili bolje, sa 128MB RAM-a.
Preporučeno za grafički režim: 400 MHz G3 ili bolje, sa 256MB RAM-a.
Kompletni paketi mogu zauzeti preko 9 GB prostora na disku. Krajnja veličina je potpuno određena instalacionim izdanjem i paketima izabranim tokom instalacije. Dodatan prostor je neophodan tokom instalacije za podršku okruženja instalacije. Ovaj dodatni prostor odgovara veličini /Fedora/base/stage2.img (na Instalacionom disku 1) plus veličini datoteka u /var/lib/rpm na instaliranom sistemu.
Praktično, zahtevi za dodatni slobodni prostor mogu biti u opsegu od 90 MB za najmanju instalaciju do čak 175 MB dodatnog prostora za veću instalaciju.
Dodatni prostor je takođe potreban za bilo koje korisničke podatke, kao i najmanje 5% prostora koje je potrebno održavati slobodnim za ispravan rad sistema.
Posle kratkog eksperimenta sa 64KB stranicama u Fedora Core 6, PowerPC64 jezgro je sada prebačeno nazad na 4KB stranice. Instalater bi trebalo da samostalno formatira svap particije tokom nadgradnje.
Taster Option na Apple sistemima je isto što i taster Alt na PC sistemu. Gde dokumentacija i instalater spominju taster Alt, koristite taster Option. Za pojedine kombinacije tastera možda ćete morati koristiti taster Option zajedno sa tasterom Fn, poput Option+Fn+F3 kada se prebacujete na virtuelni terminal tty3.
Fedora instalacioni disk 1 je pokretački na podržanom hardveru. Takođe, pokretački CD otisak se nalazi u direktorijumu images/ na ovom disku. Ponašanje ovih otisaka se prilagođava sistemskom hardveru:
Na većini mašina — Pokretački program samostalno pokreće odgovarajući 32-bitni ili 64-bitni instalater sa instalacionog diska.
64-bit IBM pSeries (POWER4/POWER5/POWER6), trenutni modeli iSeries — Posle korišćenja OpenFirmware-a da pokrenete CD, pokretački program, yaboot, samostalno pokreće 64-bitni instalater.
BM "Legacy" iSeries (POWER4) — Takozvani „Zastareli“ iSeries modeli, koji ne koriste OpenFirmware, zahtevaju korišćenje pokretačkog otiska koji se nalazi u direktorijumu images/iSeries stabla instalacije.
Genesi Pegasos II / Efika 5200B — Fedora-ino jezgro podržava i Pegasos i Efika bez potrebe da se koriste „Dodaci za drvo uređaja“ (Device Tree Supplement) sa powerdeveloper.org. Međutim, nedostatak potpune podrške za ISO9660 u firmveru znači da podizanje sistema preko yaboot sa CD-a nije moguće. Koristite „netboot“ otisak, ili sa CD-a ili preko mreže. Zbog veličine otiska, morate postaviti promenljivu load-base u firmveru da učitava datoteke na velikoj adresi, popu 32Mb umesto 4Mb:
setenv load-base 0x2000000
Na odzivniku OpenFirmware-a, unesite sledeće naredbe za pokretanje Efika ažuriranja, ako je potrebno, ili netboot otiska sa CD-a:
boot cd: /images/netboot/ppc32.img
Ili preko mreže:
boot eth ppc32.img
Takođe, morate ručno podesiti OpenFirmware da biste omogućili pokretanje instaliranog Fedora sistema. Ovo se obavlja postavljanjem promenljiva okruženja boot-device (pokretački uređaj) i boot-file (pokretačka datoteka) na odgovarajuću vrednost radi yaboot učitavanja sa /boot particije. Na primer, podrazumevana instalacija može zahtevati sledeće:
setenv boot-device hd:0 setenv boot-file
/yaboot/yaboot setenv auto-boot? true
PA Semi Electra — Electra firmver još uvek ne podržava yaboot. Za instalaciju na Electra-i, možete pokrenuti ppc64.img netboot otisak. Posle instalacije, moraćete ručno da podesite firmver da učitava instalirano jezgro i initrd sa /boot particije.
Pogledajte dokumentaciju za firmver za dalja uputstva.
Sony PlayStation 3 — Za instalaciju na PlayStation 3, prvo ažurirajte firmver na 1.60 ili kasniji. Pokretački program „Drugi OS“ mora biti instaliran u fleš memoriju, prateći uputstva na http://www.playstation.com/ps3-openplatform/manual.html stranici. Prikladni pokretački program se nalazi na Sony-jevom „dodatnom“ CD-u, koji je dostupan na ftp://ftp.kernel.org/pub/linux/kernel/people/geoff/cell/.
Pošto se pokretački program instalira, PlayStation 3 bi trebalo da može da pokrene Fedora instalacionu mediju. Primite k znanju da mrežna instalacija najbolje radi sa NFS-om, pošto zauzima manje memorije nego FTP ili HTTP metode. Upotreba opcije takođe umanjuje količinu memorije koju zauzima instalater.
Za više podataka o Fedora-i i PlayStation3 ili Fedora-i na PowerPC-u uopšte, pridružite se Fedora-PPC dopisnom društvu (http://lists.infradead.org/mailman/listinfo/fedora-ppc) ili #fedora-ppc kanalu na FreeNode-u (http://freenode.net/).
Kombinovani otisci sa jezgrom instalatera i ramdiskom nalaze se u direktorijumu images/netboot/, u stablu instalacije. Namenjeni su podizanju preko mreže preko TFTP, ali se mogu koristiti i na druge načine.
Pokretač yaboot podržava podizanje TFTP za IBM pSeries i Apple Macintosh. Projekat Fedora daje prednost programu yaboot nad otiscima netboot.
Paket ppc64-utils podeljen je na pojedinačne pakete koji odgovaraju aktuelnom pakovanju (ps3pf-utils, powerpc-utils, powerpc-utils-papr). Iako naredbe mkzimage više nema, možete koristiti wrapper skriptu iz paketa kernel-bootwrapper:
wrapper -i initrd-${VERZIJA_JEZGRA}.img -o
zImage-${VERZIJA_JEZGRA}.img vmlinuz-${VERZIJA_JEZGRA}
Ovaj odeljak sadrži informacije u vezi sa implementacijom X sistema prozora, X.Org, koji čini deo Fedora sistema.
Fedora 10 koristi upravljači program
evdev
kao standardni za upravljanje mišom i tastaturom u X serveru. Ovaj upravljački program radi uz HAL radi pružanja trajnih podešavanja po uređaju što dozvoljava dodavanje i uklanjanje uređaja tokom izvršavanja.
Za detaljno uputstvo o korišćenju video upravljačkih programa koji ne dolaze sa sistemom pogledajte Xorg stranu o upravljačkim programima drugih proizvođača.
http://who-t.blogspot.com/2008/07/input-configuration-in-nutshell.html -- Evdev podešavanja.
Fedora 10 includes multiple boot-time updates, including changes that allow for faster booting and graphic booting changes.
The GRUB menu is no longer shown at startup, except on dual-boot systems. To bring up the GRUB menu, hold the Shift key before the kernel is loaded. (Any other key works but the Shift key is the safest to use.)
Plymouth is the graphical boot up system debuting with Fedora 10.
Adding rhgb on the
grub command line directs Plymouth to load
the appropriate plugin for your hardware.
The graphical boot splash screen that comes with Plymouth
requires kernel mode setting drivers to work best. There are
not kernel modesetting drivers available for all hardware yet.
To see the graphical splash before the drivers are generally
available, add vga=0x318 to the kernel
grub command line. This uses
vesafb, which does not necessarily give the
native resolution for a flat panel, and may cause flickering
or other weird interactions with X. Without kernel modesetting
drivers or vga=0x318, Plymouth uses a
text-based plugin that is plain but functional.
Currently, only Radeon R500 and higher users get kernel modesetting by default. There is work in progress to provide modesetting for R100 and R200. Additionally, Intel kernel modesetting drivers are in development, but not turned on by default.
The kernel modesetting drivers are still in development
and buggy. If you end up with nothing but a black screen
during boot up, or a screen with nothing but random noise on
it, then adding nomodeset to the kernel
boot prompt in grub disables modesetting.
Plymouth hides boot messages. To view boot messages, press
the Esc key during boot, or view them in
/var/log/boot.log after boot up.
Alternatively, remove rhgb from the kernel
command line and plymouth displays all boot messages. There is
also a status icon on the login screen to view boot
warnings.
Fedora 10 gets a faster boot from improvements in process start-up.
Readahead is started in parallel with the boot process.
Udev may appear to be slower but in fact readahead reads
all disk buffers needed for the boot process in the background
and shortens the whole boot process. Creation of the readahead
file list is done monthly and can be triggered manually by
touching /.readahead_collect. The
configuration file
/etc/sysconfig/readahead can be edited to
turn off readahead-collector and/or readahead.
Kernel modesetting (KMS) can default to either enabled or disabled in the DRM driver and it can be enabled or disabled at boot-time.
Both Plymouth and the DDX drivers detect whether KMS is present and enabled. If it is present and enabled, Plymouth and DDX drivers will take advantage of them.
If KMS is not present or it is present but disabled then Plymouth will automatically fall back to the text splash and the DDX driver will automatically fall back to user-space modesetting.
Allows for faster user switching, seamless X server switching, and graphical panic messages.