To help users enable the correct USE flags, we are providing a Python script that generates the correct value using /proc/cpuinfo. It can be found in the {{Package|app-portage/cpuinfo2cpuflags}} package:

{{Note|Use this method if you are booting using UEFI, and if your System Rescue CD initial boot menu was black and white. If it was light blue, this method will not work.}}

+

−

+

−

The <tt>gdisk</tt> commands to create a GPT partition table are as follows. Adapt sizes as necessary, although these defaults will work for most users. Start <code>gdisk</code>:

+

−

+

−

<console>

+

−

# ##i##gdisk

+

−

</console>

+

−

+

−

Within <tt>gdisk</tt>, follow these steps:

+

−

+

−

'''Create a new empty partition table''' (This ''will'' erase all data on the disk when saved):

+

−

+

−

<console>

+

−

Command: ##i##o ↵

+

−

This option deletes all partitions and creates a new protective MBR.

+

−

Proceed? (Y/N): ##i##y ↵

+

−

</console>

+

−

+

−

'''Create Partition 1''' (boot):

+

−

+

−

<console>

+

−

Command: ##i##n ↵

+

−

Partition Number: ##i##1 ↵

+

−

First sector: ##i##↵

+

−

Last sector: ##i##+500M ↵

+

−

Hex Code: ##i##↵

+

−

</console>

+

−

+

−

'''Create Partition 2''' (swap):

+

−

+

−

<console>

+

−

Command: ##i##n ↵

+

−

Partition Number: ##i##2 ↵

+

−

First sector: ##i##↵

+

−

Last sector: ##i##+4G ↵

+

−

Hex Code: ##i##8200 ↵

+

−

</console>

+

−

+

−

'''Create Partition 3''' (root):

+

−

+

−

<console>

+

−

Command: ##i##n ↵

+

−

Partition Number: ##i##3 ↵

+

−

First sector: ##i##↵

+

−

Last sector: ##i##↵##!i## (for rest of disk)

+

−

Hex Code: ##i##↵

+

−

</console>

+

−

+

−

Along the way, you can type "<tt>p</tt>" and hit Enter to view your current partition table. If you make a mistake, you can type "<tt>d</tt>" to delete an existing partition that you created. When you are satisfied with your partition setup, type "<tt>w</tt>" to write your configuration to disk:

+

−

+

−

'''Write Partition Table To Disk''':

+

−

+

−

<console>

+

−

Command: ##i##w ↵

+

−

Do you want to proceed? (Y/N): ##i##Y ↵

+

−

</console>

+

−

+

−

The partition table will now be written to disk and <tt>gdisk</tt> will close.

+

−

+

−

Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:

+

−

+

−

* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem,

Before your newly-created partitions can be used, the block devices need to be initialized with filesystem ''metadata''. This process is known as ''creating a filesystem'' on the block devices. After filesystems are created on the block devices, they can be mounted and used to store files.

+

−

+

−

Let's keep this simple. Are you using old-school MBR partitions? If so, let's create an ext2 filesystem on /dev/sda1:

+

−

+

−

<console>

+

−

# ##i##mkfs.ext2 /dev/sda1

+

−

</console>

+

−

+

−

If you're using new-school GPT partitions for UEFI, you'll want to create a vfat filesystem on /dev/sda1, because this is what UEFI is able to read:

+

−

+

−

<console>

+

−

# ##i##mkfs.vfat -F 32 /dev/sda1

+

−

</console>

+

−

+

−

Now, let's create a swap partition. This partition will be used as disk-based virtual memory for your Funtoo Linux system.

+

−

+

−

You will not create a filesystem on your swap partition, since it is not used to store files. But it is necessary to initialize it using the <code>mkswap</code> command. Then we'll run the <code>swapon</code> command to make your newly-initialized swap space immediately active within the live CD environment, in case it is needed during the rest of the install process:

+

−

+

−

<console>

+

−

# ##i##mkswap /dev/sda2

+

−

# ##i##swapon /dev/sda2

+

−

</console>

+

−

+

−

Now, we need to create a root filesystem. This is where Funtoo Linux will live. We generally recommend ext4 or XFS root filesystems. If you're not sure, choose ext4. Here's how to create a root ext4 filesystem:

+

−

+

−

<console>

+

−

# ##i##mkfs.ext4 /dev/sda3

+

−

</console>

+

−

+

−

...and here's how to create an XFS root filesystem, if you choose to use XFS:

+

−

+

−

<console>

+

−

# ##i##mkfs.xfs /dev/sda3

+

−

</console>

+

−

+

−

Your filesystems (and swap) have all now been initialized, so that that can be mounted (attached to your existing directory heirarchy) and used to store files. We are ready to begin installing Funtoo Linux on these brand-new filesystems.

+

−

+

−

{{fancywarning|1=

+

−

When deploying an OpenVZ host, please use ext4 exclusively. The Parallels development team tests extensively with ext4, and modern versions of <code>openvz-rhel6-stable</code> are '''not''' compatible with XFS, and you may experience kernel bugs.

+

}}

}}

−

==== Montando os filesystems ====

+

In order to ensure safe migration and maintain compatibility with external repositories, it is recommended to preserve the old USE settings for a period of one year or until no package of interest is still using them.

Latest revision as of 08:59, January 31, 2015

CPU FLAGS X86

The USE flags corresponding to the instruction sets and other features specific to the x86 (including x86-64) architecture are being moved into a separate USE flag group called CPU_FLAGS_X86.

In order not to lose CPU-specific optimizations, users will be required to update their make.conf (and package.use) file. For example, if the following USE flags were present:

/etc/portage/make.conf - The original make.conf flags

USE="mmx mmxext sse sse2 sse3"

Those flags need to be copied into:

/etc/portage/make.conf - The new make.conf flags

CPU_FLAGS_X86="mmx mmxext sse sse2 sse3"

Please note that the same CPU_FLAGS_X86 variable is used both on 32-bit and 64-bit x86 (amd64) systems.

When in doubt, you can consult the flag descriptions using one of the commonly available tools, e.g. equery uses from gentoolkit:

$ equery uses media-video/ffmpeg

Most of the flag names match /proc/cpuinfo names, with the notable exception of SSE3 which is called 'pni' in /proc/cpuinfo (please also do not confuse it with distinct SSSE3).

To help users enable the correct USE flags, we are providing a Python script that generates the correct value using /proc/cpuinfo. It can be found in the app-portage/cpuinfo2cpuflags (package not on wiki - please add) package:

# emerge -1v app-portage/cpuinfo2cpuflags
$ cpuinfo2cpuflags-x86

In order to ensure safe migration and maintain compatibility with external repositories, it is recommended to preserve the old USE settings for a period of one year or until no package of interest is still using them.