Installation Guide {#idm2190000}

`Mono-spaced Bold Italic`

books        Desktop   documentation  drafts  mss    photos   stuff  svn
books_tests  Desktop1  downloads      images  notes  scripts  svgs

package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

public class ExClient
{
   public static void main(String args[])
       throws Exception
   {
      InitialContext iniCtx = new InitialContext();
      Object         ref    = iniCtx.lookup("EchoBean");
      EchoHome       home   = (EchoHome) ref;
      Echo           echo   = home.create();

      System.out.println("Created Echo");

      System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
   }
}

Installing the default software for Fedora over the Internet requires more time than the Live image, but less time than the entire DVD distribution. Actual results depend on the software you select and network traffic conditions.

su -

mkdir /mnt/livecd

mount -o loop /home/_`Username`_/Downloads/Fedora-Live-Desktop-x86_64-20-1.iso /mnt/livecd

cd /mnt/livecd/LiveOS

./livecd-iso-to-disk /home/_`Username`_/Downloads/Fedora-Live-Desktop-x86_64-20-1.iso /dev/sdc1

**`linux rd.live.check`**

**dd if=/dev/_`dvd`_ of=/_`path_to_image`_/_`name_of_image`_.iso**

**`linux rd.live.check`**

**`linux rd.live.check`**

**`linux updates`**

**`linux text updates`**

IPAPPEND 2
APPEND ksdevice=bootif

ksdevice=link

**``linux repo=cdrom:_`device`_``**

**``linux repo=hd:_`device`_``**

**``linux repo=nfs:_`options`_:_`server`_:/_`path`_``**

**``linux repo=nfsiso:_`options`_:_`server`_:/_`path`_``**

**``linux repo={ftp|http}://_`URL`_``**

<http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html>

Only RAID 0 and RAID 1 are available for btrfs subvolumes.

At the border between each range listed above (for example, a system with 2GB, 8GB, or 64GB of system RAM), discretion can be exercised with regard to chosen swap space and hibernation support. If your system resources allow for it, increasing the swap space may lead to better performance.

Note that distributing swap space over multiple storage devices — particularly on systems with fast drives, controllers and interfaces — also improves swap space performance.

If your hard drive is more than 1024 cylinders (and your system was manufactured more than two years ago), you may need to create a `/boot/` partition if you want the `/` (root) partition to use all of the remaining space on your hard drive.

If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the `/boot/` partition must be created on a partition outside of the RAID array, such as on a separate hard drive.

The `/` (or root) partition is the top of the directory structure. The `/root` directory`/root` (sometimes pronounced "slash-root") directory is the home directory of the user account for system administration.

The PackageKit update software downloads updated packages to `/var/cache/yum/` by default. If you partition the system manually, and create a separate `/var/` partition, be sure to create the partition large enough (3.0 GB or more) to download package updates.

If `/usr` is on a separate file system from `/`, the boot process becomes much more complex because `/usr` contains boot-critical components. In some situations (like installations on iSCSI drives), the boot process might not work at all.

    **`linux rd.live.check`**

    <http://www.bitwizard.nl/sig11/>

GRUB_TERMINAL=console

**grub2-mkconfig --output=/boot/grub2/grub.cfg**

  ** ln -s /lib/systemd/system/graphical.target /etc/systemd/system/default2.target **

  ** mv /etc/systemd/system/default2.target /etc/systemd/system/default.target **

df -h

    **`single`**

 # for BIOS systems
 **grub2-mkconfig --output=/boot/grub2/grub.cfg**

 # for UEFI systems
 **grub2-mkconfig --output=/boot/efi/EFI/fedora/grub.cfg**

     menuentry 'Fedora (3.16.0-0.rc2.git2.1.fc21.x86_64) 21 (Rawhide)' {
      load_video
      set gfxpayload=keep
      insmod gzio
      insmod part_gpt
      insmod ext2
      set root='hd1,gpt2'
      if [ x$feature_platform_search_hint = xy ]; then
        search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  b34a57d9-03d7-415f-94f6-91689404d951
      else
        search --no-floppy --fs-uuid --set=root b34a57d9-03d7-415f-94f6-91689404d951
      fi
      linuxefi /vmlinuz-3.16.0-0.rc2.git2.1.fc21.x86_64 root=UUID=ece86abc-6419-4f29-84b6-1b810128f98d ro rootflags=subvol=root vconsole.font=latarcyrheb-sun16  vconsole.keymap=us LANG=en_US.UTF-8 mem=8192M
      initrdefi /initramfs-3.16.0-0.rc2.git2.1.fc21.x86_64.img
    }

127.0.0.1  localhost.localdomain  localhost

`boot:```linux _`options`_``

`>```_`options`_``

inst.repo=cdrom

inst.dd=cdrom

``inst.ks=nfs:_`next-server`_:/_`filename`_``

X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab

``X-System-Serial-Number: _`R8VA23D`_``

``inst.geoloc=_`value`_``

ifname=eth0:01:23:45:67:89:ab

menuentry "Fedora Linux" {
        set root=(hd0,1)
        linux /vmlinuz-install
        initrd /initrd.img-install
    }

linux /vmlinuz-install stage2=http://my.internal.server/17/x86_64/os/

**grub2-mkconfig --output=/boot/grub2/grub.cfg**

GRUB_DEFAULT=0

GRUB_DEFAULT="Fedora Linux"

**yum -y install cobbler**

**cobbler check**

**setsebool -P httpd_can_network_connect_cobbler 1**

**getsebool -a|grep cobbler**

If SELinux is enabled, use the default **iso9660\_t** label instead of **httpd\_sys\_content\_t**.

When **cobbler** imports a distribution with the commands above, it copies all the files to the server's local storage, which may take some time.

If you do not want to make local copies of the distribution because clients can already reach its location, use the `--available-as` option.

**cobbler import --path=/mnt/dvd --name=_`distro_name`_ --available-as=_`network_URI`_**
**cobbler import --path=_`network_URI`_ --name=_`distro_name`_ --available-as=_`network_URI`_**

For _`nework_URI`_, substitute the appropriate network location of the distribution. This URI indicates how the server makes the distribution available to its clients. The examples above assume that your **cobbler** server reaches the mirror location at the same URI as the clients. If not, substitute an appropriate URI for the `--path` option. The following examples are URI locations that work if you have been following the procedures in this section, and your server's IP address is `192.168.1.1`:

Depending on your server's configuration, you may need to use the **system-config-securitylevel** command to permit access to some or all of these network services:

       class "pxeclients" {
               match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
               next-server 10.0.0.1;

               if option arch = 00:06 {
                       filename "pxelinux/bootia32.efi";
               } else if option arch = 00:07 {
                       filename "pxelinux/bootx64.efi";
               } else {
                       filename "pxelinux/pxelinux.0";
               }
       }

       host example-ia32 {
               hardware ethernet XX:YY:ZZ:11:22:33;
               fixed-address 10.0.0.2;
       }

       class "pxeclients" {
               match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
               next-server 10.0.0.1;

               if option arch = 00:06 {
                       filename "pxelinux/bootia32.efi";
               } else if option arch = 00:07 {
                       filename "pxelinux/bootx64.efi";
               } else {
                       filename "pxelinux/pxelinux.0";
               }
       }

       host example-ia32 {
               hardware ethernet XX:YY:ZZ:11:22:33;
               fixed-address 10.0.0.2;
       }

   option dhcp6.bootfile-url "tftp://[3ffe:501:ffff:100::1]/grubx64.efi";
   option dhcp6.name-servers 3ffe:501:ffff:100::1;

  }

**systemctl start xinetd.service**
**systemctl enable xinetd.service**

Running anaconda _`VERSION`_, the _`PRODUCT`_ system installer - please wait...

boot: **``linux vnc vncconnect=_`HOST`_[:_`port`_]``**

This IP address is only used during installation. You will have an opportunity to configure the final network settings, if any, later in the installer.

btrfs _`<mntpoint>`_ --data=_`<level>`_ --metadata=_`<level>`_ --label=_`<label>`_ _`<partitions>`_

btrfs _`<mntpoint>`_ --subvol --name=_`<path>`_ _`<parent>`_

Device names like `mpatha` are not specific to a particular disk. The disk named `/dev/mpatha` during installation might not be the one that you expect it to be. Therefore, the **clearpart** command could target the wrong disk.

device _`<moduleName>`_ --opts=_`<options>`_

driverdisk _`<partition>`_ --source=_`<url>`_ --biospart=_`<biospart>`_ [--type=_`<fstype>`_]

driverdisk --source=ftp://path/to/dd.img
driverdisk --source=http://path/to/dd.img
driverdisk --source=nfs:host:/path/to/img

firewall --enabled|--disabled [--trust=] _`<device>`_ [--port=]

ignoredisk --drives=_`drive1,drive2`_,...

ignoredisk --drives=disk/by-id/dm-uuid-mpath-2416CD96995134CA5D787F00A5AA11017

ignoredisk --drives=disk/by-id/scsi-58095BEC5510947BE8C0360F604351918

The disk image must have the necessary utilities that anaconda needs to complete the installation, so livemedia-creator is recommended for creating the disk image.

keyboard --vckeymap=_`<keymap>`_|--xlayouts=_`<layout1>`_,...,_`<layoutN>`_|_`<layout>`_ [--switch=_`<option1>`_,..._`<optionN>`_]

lang en_US

@french-support

logvol _`<mntpoint>`_ --vgname=_`<name>`_ --size=_`<size>`_ --name=_`<name>`_ _`<options>`_

part pv.01 --size 3000
volgroup myvg pv.01
logvol / --vgname=myvg --size=2000 --name=rootvol

part pv.01 --size 1 --grow
volgroup myvg pv.01
logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90

If the **--size** value is too small, the installation will fail. Set the **--size** value as the minimum amount of space you require. For size recommendations, refer to [Section 9.14.5, “Recommended Partitioning Scheme”](#s2-diskpartrecommend-x86 "9.14.5. Recommended Partitioning Scheme").

If you use **--grow=** without setting **--maxsize=** on a swap partition, Anaconda will limit the maximum size of the swap partition. For systems that have less than 2GB of physical memory, the imposed limit is twice the amount of physical memory. For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.

Device names like `mpatha` are not specific to a particular disk. The disk named `/dev/mpatha` during installation might not be the one that you expect it to be. Therefore, the **part** command could target the wrong disk or partition.

raid _`<mntpoint>`_ --level=_`<level>`_ --device=_`<mddevice>`_ _`<partitions*>`_

part raid.01 --size=60 --ondisk=sda
part raid.02 --size=60 --ondisk=sdb
part raid.03 --size=60 --ondisk=sdc

part swap --size=128 --ondisk=sda
part swap --size=128 --ondisk=sdb
part swap --size=128 --ondisk=sdc

part raid.11 --size=1 --grow --ondisk=sda
part raid.12 --size=1 --grow --ondisk=sdb
part raid.13 --size=1 --grow --ondisk=sdc

raid / --level=1 --device=md0 raid.01 raid.02 raid.03
raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13

realm join _`<options>`_ _`<domain>`_

repo --name=_`<repoid>`_ [--baseurl=_`<url>`_| --mirrorlist=_`<url>`_]

rootpw [--iscrypted|--allow-changes|--frozen] _`<password>`_

selinux [--disabled|--enforcing|--permissive]

If the **selinux** option is not present in the kickstart file, SELinux is enabled and set to **--enforcing** by default.

sshpw --username=_`<name>`_ _`<password>`_ [--iscrypted|--plaintext] [--lock]

timezone [--utc] [--nontp] [--ntpservers=_`<server1>`_,_`<server2>`_,...,_`<serverN>`_] _`<timezone>`_

user --name=_`<username>`_ [--groups=_`<list>`_] [--homedir=_`<homedir>`_] [--password=_`<password>`_] [--iscrypted] [--shell=_`<shell>`_] [--uid=_`<uid>`_]

vnc [--host=_`<hostname>`_] [--port=_`<port>`_] [--password=_`<password>`_]

volgroup _`<name>`_ _`<partition>`_ _`<options>`_

part pv.01 --size 3000
volgroup myvg pv.01
logvol / --vgname=myvg --size=2000 --name=rootvol

clearpart --drives=hda,hdc --initlabel
# Raid 1 IDE config
part raid.11    --size 1000     --asprimary     --ondrive=hda
part raid.12    --size 1000     --asprimary     --ondrive=hda
part raid.13    --size 2000     --asprimary     --ondrive=hda
part raid.14    --size 8000                     --ondrive=hda
part raid.15    --size 16384 --grow             --ondrive=hda
part raid.21    --size 1000     --asprimary     --ondrive=hdc
part raid.22    --size 1000     --asprimary     --ondrive=hdc
part raid.23    --size 2000     --asprimary     --ondrive=hdc
part raid.24    --size 8000                     --ondrive=hdc
part raid.25    --size 16384 --grow             --ondrive=hdc

# You can add --spares=x
raid /          --fstype ext3 --device md0 --level=RAID1 raid.11 raid.21
raid /safe      --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22
raid swap       --fstype swap --device md2 --level=RAID1 raid.13 raid.23
raid /usr       --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24
raid pv.01      --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25

# LVM configuration so that we can resize /var and /usr/local later
volgroup sysvg pv.01
logvol /var             --vgname=sysvg  --size=8000     --name=var
logvol /var/freespace   --vgname=sysvg  --size=8000     --name=freespacetouse
logvol /usr/local       --vgname=sysvg  --size=1 --grow --name=usrlocal

%packages
@ X Window System
@ Desktop
@ Sound and Video

sqlite
curl
aspell
docbook*

-@ Graphical Internet
-autofs
-ipa*fonts

*
-@Conflicts (Server)

%packages --ignoremissing

%pre
#!/bin/sh
hds=""
mymedia=""
for file in /proc/ide/h* do
    mymedia=`cat $file/media`
    if [ $mymedia == "disk" ] ; then
        hds="$hds `basename $file`"
    fi
done
set $hds
numhd=`echo $#`
drive1=`echo $hds | cut -d' ' -f1`
drive2=`echo $hds | cut -d' ' -f2`
#Write out partition scheme based on whether there are 1 or 2 hard drives
if [ $numhd == "2" ] ; then
    #2 drives
    echo "#partitioning scheme generated in %pre for 2 drives" &gt; /tmp/part-include
    echo "clearpart --all" &gt;&gt; /tmp/part-include
    echo "part /boot --fstype ext3 --size 75 --ondisk hda" &gt;&gt; /tmp/part-include
    echo "part / --fstype ext3 --size 1 --grow --ondisk hda" &gt;&gt; /tmp/part-include
    echo "part swap --recommended --ondisk $drive1" &gt;&gt; /tmp/part-include
    echo "part /home --fstype ext3 --size 1 --grow --ondisk hdb" &gt;&gt; /tmp/part-include
else
    #1 drive
    echo "#partitioning scheme generated in %pre for 1 drive" &gt; /tmp/part-include
    echo "clearpart --all" &gt;&gt; /tmp/part-include
    echo "part /boot --fstype ext3 --size 75" &gt;&gt; /tmp/part-include
    echo "part swap --recommended" &gt;&gt; /tmp/part-include
    echo "part / --fstype ext3 --size 2048" &gt;&gt; /tmp/part-include
    echo "part /home --fstype ext3 --size 2048 --grow" &gt;&gt; /tmp/part-include
fi

%include /tmp/part-include

%post --nochroot
cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf

%post --log=/root/ks-post.log

%post --nochroot --log=/mnt/sysimage/root/ks-post.log

mkdir /mnt/temp
mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp
openvt -s -w -- /mnt/temp/runme
umount /mnt/temp

label 1
  kernel Fedora20/vmlinuz
  append initrd=Fedora20/initrd.img ramdisk_size=10000 ks=nfs:192.168.0.200:/export/kickstart/foo.ks

linux ks=hd:_`partition`_:/_`path`_/ks.cfg dd

linux ks=cdrom:/ks.cfg

**echo "Hackers will be punished" &gt; /etc/motd**

**echo "Hackers will be punished" &gt; /mnt/sysimage/etc/motd**

**`su -c 'yum update'`**

linux upgradeany

          **yum repolist**

          ** yum-config-manager --disable &lt;_`repo-name`_&gt; **

          ** yum-config-manager --enable &lt;_`repo-name`_&gt; **

              **grub2-install /dev/sd_`a`_**

              **grub2-mkconfig -o `/boot/grub2/grub.cfg`**

              **grub2-mkconfig -o `/boot/efi/EFI/fedora/grub.cfg`**

              **yum distro-sync**

              **package-cleanup --leaves**

              **package-cleanup --orphans**

Some packages may be listed by **package-cleanup** that you might use. For example, you might use a `Python` library in scripts you have written, but it may not have any packaged software that depends on it. Be sure that you do not need a package before you remove it. In most cases, it will do no harm to leave the package installed.

Duplicates or conflicts that prevent updates can be identified with **package-cleanup**, but **yum distro-sync** should be used first.

              **touch /.autorelabel**

              **restorecon -R /var/cache/squid/**

If your computer has system restore software stored on a partition on a hard drive, take care when removing partitions while installing an operating system from other media. Under these circumstances, you could destroy the partition holding the system restore software.

This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by Windows. Depending on your configuration, this might be a significant portion of the storage capacity of the drive.

Decide whether to extend an existing Windows partition to use the extra space, or create a new Windows partition in that space. If you create new a Windows partition, Windows will allocate a new drive letter to it and will interact with it as if it is a separate hard drive.

The diskpart tool used in this step is installed as part of the Windows XP and Windows 2003 operating systems. If you are performing this step on a computer running Windows 2000 or Windows Server 2000, you can download a version of diskpart for your operating system from the Microsoft website.

This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by Windows. Depending on your configuration, this might be a significant portion of the storage capacity of the drive.

Decide whether to extend an existing Windows partition to use the extra space, or create a new Windows partition in that space. If you create new a Windows partition, Windows will allocate a new drive letter to it and will interact with it as if it is a separate hard drive.

These instructions assume that your system uses the GRUB bootloader. If you use a different bootloader (such as LILO) consult the documentation for that software to identify and remove Fedora entries from its list of boot targets and to ensure that your default operating system is correctly specified.

menuentry "Fedora (2.6.32.130.el6.i686)"

set root=(hd0,1)

linux /vmlinuz-2.6.32.130.el6.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 rhgb quiet

initrd /initrd-2.6.32.130.el6.i686.img

<br />
 Depending on the configuration of your system, there may be multiple Fedora entries in `10_linux`, each corresponding to a different version of the Linux kernel. Delete each of the Fedora entries from these files

Save the updated `10_linux` file and close gedit.

This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by your other Linux operating system. Depending on your configuration, this might be a significant portion of the storage capacity of the drive.

To carry out this step, you require live media for a Linux distribution, for example, the Fedora Live CD or the Knoppix DVD.

The method to make the space freed by removing the Fedora partitions available to your other Linux operating system differs, depending on whether your chosen operating system is installed on disk partitions configured to use Logical Volume Management (LVM) or not.

**fdisk /mbr**

parted /dev/hda

print

rm 3

Because NetworkManager is installed in `/usr`, you cannot use it to configure network access if `/usr` is on network-attached storage such as an iSCSI target.

cryptsetup luksFormat &lt;device&gt;

cryptsetup isLuks &lt;device&gt; &amp;&amp; echo Success

cryptsetup luksDump &lt;device&gt;

cryptsetup luksUUID &lt;device&gt;

cryptsetup luksOpen &lt;device&gt; &lt;name&gt;

dmsetup info &lt;name&gt;

mke2fs /dev/mapper/&lt;name&gt;

mount /dev/mapper/&lt;name&gt; /mnt/test

&lt;name&gt;  &lt;device&gt;  none

        dd if=/dev/urandom of=$HOME/keyfile bs=32 count=1
        chmod 600 $HOME/keyfile

cryptsetup luksAddKey &lt;device&gt; ~/keyfile

cryptsetup luksAddKey &lt;device&gt;

cryptsetup luksRemoveKey &lt;device&gt;

        ** --channel tcp,host=127.0.0.1:6080,mode=connect,target_type=virtio,name=org.fedoraproject.anaconda.log.0 **

         **virsh list --all**

         **virsh edit _`new-fedora-guest`_**

        ** eval `analog -p 6080 -o rsyslogd.conf -s _`/path/to/logdir`_` **

        ** nc -l 0.0.0.0 6080 **

Processor manufacturer and model	Architecture type for Fedora
Intel Atom (see note below,) Core series, Pentium 4, and recent vintage Xeon; AMD Athlon, Duron, some Semprons; and older; VIA C3, C7	`i386` (32-bit)
Intel Atom (See note below), Core 2 series, Core i series and Xeon; AMD: Athlon 64, Athlon II, Sempron64, Phenom series, Fusion series, Bulldozer series and Opteron; Apple MacBook, MacBook Pro, and MacBook Air	`x86_64` (64-bit)

Media type	File locations
Full distribution on DVD	fedora/linux/releases/20/Fedora/_`arch`_/iso/Fedora-20-_`arch`_-DVD.iso
Live image	fedora/linux/releases/20/Live/_`arch`_/iso/Fedora-Live-Desktop-_`arch`_-20-1.iso, fedora/linux/releases/20/Live/_`arch`_/iso/Fedora-Live-KDE-_`arch`_-20-1.iso
Minimal CD boot media	fedora/linux/releases/20/Fedora/_`arch`_/iso/Fedora-20-_`arch`_-netinst.iso

Architecture	Installation DVD	Installation USB flash drive	Boot CD or boot DVD	Boot USB flash drive	Live image DVD or USB flash drive
BIOS-based 32-bit x86	x86 DVD ISO image file	x86 DVD ISO image file	x86 netinst ISO image file	x86 netinst ISO image file	x86 Live ISO image file
UEFI-based 32-bit x86	Not available
BIOS-based AMD64 and Intel 64	x86_64 DVD ISO image file (to install 64-bit operating system) or x86 DVD ISO image file (to install 32-bit operating system)	x86_64 DVD ISO image file (to install 64-bit operating system) or x86 DVD ISO image file (to install 32-bit operating system)	x86_64 netinst ISO image file	x86_64 netinst ISO image file	x86_64 Live ISO image file
UEFI-based AMD64 and Intel 64	x86_64 DVD ISO image file	x86_64 DVD ISO image file	x86_64 netinst ISO image file	x86_64 netinst ISO image file	x86_64 Live ISO image file

Partition type	Volume	Original path to files	Directory to use
VFAT	D:\	D:\Downloads\Fedora20	/Downloads/Fedora20
ext2, ext3, ext4	/home	/home/user1/Fedora20	/user1/Fedora20

console	keystrokes	contents
1	Ctrl+alt+f1	standard output
2	Ctrl+alt+f2	shell prompt
3	Ctrl+alt+f3	installation log
4	Ctrl+alt+f4	storage log
5	Ctrl+alt+f5	external program log
6	Ctrl+alt+f6	localhost login
7	Ctrl+alt+f6	graphical display

Amount of RAM in the system	Recommended swap space	Recommended swap space if allowing for hibernation
⩽ 2GB	2 times the amount of RAM	3 times the amount of RAM
> 2GB – 8GB	Equal to the amount of RAM	2 times the amount of RAM
> 8GB – 64GB	0.5 times the amount of RAM	1.5 times the amount of RAM
> 64GB	4GB of swap space	No extra space needed

Directory	Minimum size
`/`	2 GB
`/usr`	`/usr` on a seperate partition is not supported.
`/tmp`	`tmpfs` by default, 50 MB otherwise.
`/var`	500 MB
`/home`	100 MB
`/boot`	250 MB

Partition	Size and type
`/boot`	500 MB `ext3` partition
`swap`	2 GB swap
LVM physical volume	Remaining space, as one LVM volume group

Installation source	Option format
Any CD/DVD drive	`inst.repo=cdrom`
Specific CD/DVD drive	inst.repo=cdrom:_`device`_
Hard Drive	inst.repo=hd:_`device`_/_`path`_
HTTP Server	inst.repo=http://_`host`_/_`path`_
HTTPS Server	inst.repo=https://_`host`_/_`path`_
FTP Server	inst.repo=ftp://_`username`_:_`password`_@_`host`_/_`path`_
NFS Server	inst.repo=nfs:[_`options`_:]_`server`_:/_`path`_ [a]
[a] This option uses NFS protocol version 3 by default. To use a different version, add +nfsvers=_`X`_ to `options`.

Configuration Method	Option format
Automatic configuration of any interface	ip=_`method`_
Automatic configuration of a specific interface	ip=_`interface`_:_`method`_
Static configuration	ip=_`ip`_::_`gateway`_:_`netmask`_:_`hostname`_:_`interface`_:none
Automatic configuration of a specific interface with an override [a]	ip=_`ip`_::_`gateway`_:_`netmask`_:_`hostname`_:_`method`_:_`mtu`_
[a] Brings up the specified interface using the specified method of automatic configuration, such as `dhcp`, but overrides the automatically obtained IP address, gateway, netmask, hostname or other specified parameter. All parameters are optional; only specify the ones you wish to override and automatically obtained values will be used for the others.

Automatic configuration method	Value
DHCP	`dhcp`
IPv6 DHCP	`dhcp6`
IPv6 automatic configuration	`auto6`
iBFT (iSCSI Boot Firmware Table)	`ibft`

Compatibility	Option
Disable all hardware detection	`noprobe`
Disable graphics, keyboard, and mouse detection	`headless`
Disable passing keyboard and mouse information to stage 2 of the installation program	`nopass`
Use basic VESA driver for video	`xdriver=vesa`
Disable shell access on virtual console 2 during installation	`noshell`
Disable advanced configuration and power interface (ACPI)	`acpi=off`
Disable machine check exception (MCE) CPU self-diagnosis.	`nomce`
Disable non-uniform memory access on the AMD64 architecture	`numa-off`
Force kernel to detect a specific amount of memory, where `xxx` is a value in megabytes	mem=_`xxx`_m
Enable DMA only for IDE and SATA drives	`libata.dma=1`
Disable BIOS-assisted RAID	`nodmraid`
Disable Firewire device detection	`nofirewire`
Disable parallel port detection	`noparport`
Disable PC Card (PCMCIA) device detection	`nopcmcia`
Disable all probing of network hardware	`nonet`

Partition Type	Value	Partition Type	Value
Empty	00	Novell Netware 386	65
DOS 12-bit FAT	01	PIC/IX	75
XENIX root	02	Old MINIX	80
XENIX usr	03	Linux/MINUX	81
DOS 16-bit <=32M	04	Linux swap	82
Extended	05	Linux native	83
DOS 16-bit >=32	06	Linux extended	85
OS/2 HPFS	07	Amoeba	93
AIX	08	Amoeba BBT	94
AIX bootable	09	BSD/386	a5
OS/2 Boot Manager	0a	OpenBSD	a6
Win95 FAT32	0b	NEXTSTEP	a7
Win95 FAT32 (LBA)	0c	BSDI fs	b7
Win95 FAT16 (LBA)	0e	BSDI swap	b8
Win95 Extended (LBA)	0f	Syrinx	c7
Venix 80286	40	CP/M	db
Novell	51	DOS access	e1
PReP Boot	41	DOS R/O	e3
GNU HURD	63	DOS secondary	f2
Novell Netware 286	64	BBT	ff

Installation Guide {#idm2190000}

Installing Fedora 20 on 32 and 64-bit Intel-compatible computers

#

Fedora Documentation Project

Preface {#Installation-Guide-Preface}

1. Document Conventions {#idm2130784}

1.1. Typographic Conventions {#idm5301680}

1.2. Pull-quote Conventions {#idp37864128}

1.3. Notes and Warnings {#idm2650880}

Note

Important

Warning

2. We want feedback {#idp20017248}

3. Acknowledgments {#idm26662992}

Introduction {#ch-introduction}

1. Background {#sn-background}

1.1. About Fedora {#sn-about-fedora}

1.2. Getting Additional Help {#sn-additional-help}

2. About This Document {#sn-about-document}

2.1. Goals {#sn-goals}

Other Sources of Documentation

2.2. Audience {#sn-audience}

Chapter 1. Quick Start for Experts {#ch-experts-quickstart}

Experts Only

1.1. Overview {#sn-expert-overview}

1.2. Download Files {#sn-expert-download}

Verify your downloads

1.3. Prepare for Installation {#sn-expert-prepare}

Resizing Partitions

1.4. Install Fedora {#sn-expert-install}

Chapter 2. Obtaining Fedora {#ch-new-users}

2.1. Downloading Fedora {#sect-Obtaining_Fedora-Downloading_Fedora}

2.1.1. How Do I Download Installation Files? {#sn-howto-download}

Download Links

2.1.1.1. From a Mirror {#sn-which-download-mirror}

2.1.1.2. From BitTorrent {#sn-which-download-bt}

Minimal Boot Images

Verify your download

2.1.2. Which Architecture Is My Computer? {#sn-which-arch}

i386 Works for Most Windows Compatible Computers

Intel Atom Processor Architectures Vary

Fedora supports UEFI only on 64bit systems

2.1.3. Which Files Do I Download? {#sn-which-files}

Download Size

2.2. Obtaining Fedora on CD or DVD {#sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD}

Chapter 3. Making Media {#sn-making-media}

3.1. Making an installation DVD {#sn-making-disc-media}

3.2. Preparing a USB flash drive as an installation source {#Making_USB_Media}

Ensure your USB media has sufficient space

Unusual USB Media

3.2.1. Making Fedora USB Media on a Windows Operating System {#Making_USB_Media-Windows}

Note — This Method Is Not Destructive

3.2.2. Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems {#Making_USB_Media-UNIX_Linux}

3.2.2.1. Creating Fedora USB Media in Fedora and similar Linux distributions {#Making_USB_Media-UNIX_Linux-RHEL_Fedora}

3.2.2.1.1. Making Fedora USB Media with a graphical tool {#Making_USB_Media-UNIX_Linux-RHEL_Fedora-graphical}

Important — Enable Extra Packages for Enterprise Linux

Note — This Method Is Not Destructive

3.2.2.1.2. Making Fedora USB Media with livecd-tools {#Making_USB_Media-UNIX_Linux-RHEL_Fedora-livecd-tools}

Important — Enable Extra Packages for Enterprise Linux

Note — This Method Is Not Destructive

3.2.2.1.3. Making Fedora USB Media with dd {#Making_USB_Media-UNIX_Linux-RHEL_Fedora-dd}

Warning — These instructions could destroy data

Note

3.2.2.2. Making Fedora USB Media in other Linux Distributions {#Making_USB_Media-UNIX_Linux-other}

3.2.2.2.1. Making Fedora USB Media with livecd-tools {#Making_USB_Media-UNIX_Linux-other_livecd-tools}

Note — This Method Is Not Destructive

3.2.2.2.2. Making Fedora USB Media with dd {#Making_USB_Media-UNIX_Linux-other-dd}

Warning — These instructions could destroy data

Note

3.3. Making Minimal Boot Media {#Making_Minimal_Boot_Media}

Part I. Installation and Booting {#pt-install-info-x86}

Chapter 4. Planning for Installation on the x86 Architecture {#ch-steps-x86}

4.1. Upgrade or Install? {#idm18673136}

4.2. Is Your Hardware Compatible? {#sn-Is_Your_Hardware_Compatible-x86}

4.3. RAID and Other Disk Devices {#sn-partitioning-raid-x86}

Important — Systems with Intel BIOS RAID sets

4.3.1. Hardware RAID {#sn-partitioning-raid-hw-x86}

4.3.2. Software RAID {#sn-partitioning-raid-sw-x86}

4.3.3. FireWire and USB Disks {#sn-partitioning-fw-usb-x86}

Post-installation Usage

`i386` Works for Most Windows Compatible Computers