← Older revision

Revision as of 17:29, 22 May 2013

Line 389:

Tells the system to install a fresh system rather than upgrade an existing system. This is the default mode. For installation, you must specify the type of installation from one of cdrom, harddrive, nfs, or url (for ftp or http installations). The install command and the installation method command must be on separate lines.

+

=== cdrom ===

<code>cdrom</code>

Line 394:

Line 396:

: Install from the first CD-ROM/DVD drive on the system.

−

<code>harddrive</code>

+

=== harddrive ===

+

<code>harddrive [--biospart=<bios partition> | --partition=<partition>] [--dir=<directory>]</code>

: Install from a directory of ISO images on a local drive, which must be either vfat or ext2. In addition to this directory, you must also provide the install.img in some way. You can either do this by booting off the boot.iso or by creating an images/ directory in the same directory as the ISO images and placing install.img in there.

−

:: <code>--biospart=</code>

+

: <code>--biospart=</code>

−

::: BIOS partition to install from (such as 82p2).

+

:: BIOS partition to install from (such as 82p2).

−

:: <code>--partition=</code>

+

: <code>--partition=</code>

−

::: Partition to install from (such as, sdb2).

+

:: Partition to install from (such as, sdb2).

−

:: <code>--dir=</code>

+

: <code>--dir=</code>

−

::: Directory containing both the ISO images and the images/install.img. For example:

+

:: Directory containing both the ISO images and the images/install.img. For example:

−

::: <code>harddrive --partition=hdb2 --dir=/tmp/install-tree </code>

+

:: <code>harddrive --partition=hdb2 --dir=/tmp/install-tree </code>

−

+

=== liveimg ===

+

<code>liveimg --url=<url> [--proxy=<proxyurl>] [--checksum=<sha256>] [--noverifyssl]</code>

+

: Install a disk image instead of packages. The image can be the squashfs.img from a Live iso, or any filesystem mountable by the install media (eg. ext4). Anaconda expects the image to contain utilities it needs to complete the system install so the best way to create one is to use livemedia-creator to make the disk image. If the image contains /LiveOS/*.img (this is how squashfs.img is structured) the first *img file inside LiveOS will be mounted and used to install the target system.

+

: <code>--url=</code>

+

:: The URL to install from. http, https, ftp and file are supported.

+

: <code>--proxy=[protocol://][username[:password]@]host[:port]</code>

+

:: Specify an HTTP/HTTPS/FTP proxy to use while performing the install. The various parts of the argument act like you would expect.

+

: <code>--checksum=</code>

+

:: Optional sha256 checksum of the image file

+

: <code>--noverifyssl</code>

+

:: For a tree on a HTTPS server do not check the server's certificate with what well-known CA validate and do not check the server's hostname matches the certificate's domain name.

+

=== nfs ===

+

<code>nfs --server=<hostname> --dir=<directory> [--opts=<nfs options>]</code>

: Install from the NFS server specified. This can either be an exploded installation tree or a directory of ISO images. In the latter case, the install.img must also be provided subject to the same rules as with the harddrive installation method described above.

−

:: <code>--server=</code>

+

: <code>--server=</code>

−

::: Server from which to install (hostname or IP).

+

:: Server from which to install (hostname or IP).

−

:: <code>--dir=</code>

+

: <code>--dir=</code>

−

::: Directory containing the Packages/ directory of the installation tree. If doing an ISO install, this directory must also contain images/install.img.

+

:: Directory containing the Packages/ directory of the installation tree. If doing an ISO install, this directory must also contain images/install.img.

−

:: <code>--opts=</code>

+

: <code>--opts=</code>

−

::: Mount options to use for mounting the NFS export. Any options that can be specified in /etc/fstab for an NFS mount are allowed. The options are listed in the nfs(5) man page. Multiple options are separated with a comma.

+

:: Mount options to use for mounting the NFS export. Any options that can be specified in /etc/fstab for an NFS mount are allowed. The options are listed in the nfs(5) man page. Multiple options are separated with a comma.

−

::: For example:

+

:: For example:

−

::: <code>nfs --server=nfsserver.example.com --dir=/tmp/install-tree</code>

+

:: <code>nfs --server=nfsserver.example.com --dir=/tmp/install-tree</code>

−

+

=== url ===

+

<code>url --url=<url> [--proxy=<proxy url>] [--noverifyssl]</code>

: Install from an installation tree on a remote server via FTP or HTTP.

Line 447:

Line 477:

:: For a tree on a HTTPS server do not check the server's certificate with what well-known CA validate and do not check the server's hostname matches the certificate's domain name.

−

== iscsi ==

FedoraProject - Changes related to "How to create and use a Live CD" [en]

Anaconda/Kickstart

@@ Line 389: / Line 389: @@
 Tells the system to install a fresh system rather than upgrade an existing system. This is the default mode. For installation, you must specify the type of installation from one of cdrom, harddrive, nfs, or url (for ftp or http installations). The install command and the installation method command must be on separate lines.
 <code>cdrom</code>
@@ Line 394: / Line 396: @@
 : Install from the first CD-ROM/DVD drive on the system.
-<code>harddrive</code>
+=== harddrive ===
 : Install from a directory of ISO images on a local drive, which must be either vfat or ext2.  In addition to this directory, you must also provide the install.img in some way.  You can either do this by booting off the boot.iso or by creating an images/ directory in the same directory as the ISO images and placing install.img in there.
-:: <code>--biospart=</code>
+: <code>--biospart=</code>
-::: BIOS partition to install from (such as 82p2).
+:: BIOS partition to install from (such as 82p2).
-:: <code>--partition=</code>
+: <code>--partition=</code>
-::: Partition to install from (such as, sdb2).
+:: Partition to install from (such as, sdb2).
-:: <code>--dir=</code>
+: <code>--dir=</code>
-::: Directory containing both the ISO images and the images/install.img.  For example:
+:: Directory containing both the ISO images and the images/install.img.  For example:
-::: <code>harddrive --partition=hdb2 --dir=/tmp/install-tree </code>
+:: <code>harddrive --partition=hdb2 --dir=/tmp/install-tree </code>
-<code>nfs</code>
+=== liveimg ===
 : Install from the NFS server specified.  This can either be an exploded installation tree or a directory of ISO images.  In the latter case, the install.img must also be provided subject to the same rules as with the harddrive installation method described above.
-:: <code>--server=</code>
+: <code>--server=</code>
-::: Server from which to install (hostname or IP).
+:: Server from which to install (hostname or IP).
-:: <code>--dir=</code>
+: <code>--dir=</code>
-::: Directory containing the Packages/ directory of the installation tree.  If doing an ISO install, this directory must also contain images/install.img.
+:: Directory containing the Packages/ directory of the installation tree.  If doing an ISO install, this directory must also contain images/install.img.
-:: <code>--opts=</code>
+: <code>--opts=</code>
-::: Mount options to use for mounting the NFS export.  Any options that can be specified in /etc/fstab for an NFS mount are allowed.  The options are listed in the nfs(5) man page. Multiple options are separated with a comma.
+:: Mount options to use for mounting the NFS export.  Any options that can be specified in /etc/fstab for an NFS mount are allowed.  The options are listed in the nfs(5) man page. Multiple options are separated with a comma.
-::: For example:
+:: For example:
-::: <code>nfs --server=nfsserver.example.com --dir=/tmp/install-tree</code>
+:: <code>nfs --server=nfsserver.example.com --dir=/tmp/install-tree</code>
-<code>url</code>
+=== url ===
 : Install from an installation tree on a remote server via FTP or HTTP.
@@ Line 447: / Line 477: @@
 :: For a tree on a HTTPS server do not check the server's certificate with what well-known CA validate and do not check the server's hostname matches the certificate's domain name.
 == iscsi ==