Difference between pages "Install/Partitioning" and "GNOME First Steps"

< Install(Difference between pages)
(missing block device for gdisk call)
 
(GNOME 3.14 from a clean install)
 
Line 1: Line 1:
<noinclude>
+
=== What is GNOME? ===
{{InstallPart|the process of partitioning and filesystem creation}}
+
</noinclude>
+
=== Prepare Hard Disk ===
+
  
In this section, we'll learn about the different ways that Funtoo Linux can be installed on -- and boot from -- a hard disk.
+
"GNOME 3 is an easy and elegant way to use your computer. It is designed to put you in control and bring freedom to everybody. GNOME 3 is developed by the GNOME community, a diverse, international group of contributors that is supported by an independent, non-profit foundation." — [http://gnome.org GNOME]
  
==== Introduction ====
+
=== Prerequisites ===  
  
In earlier times, there was only one way to boot a PC-compatible computer. All of our desktops and servers had a standard PC BIOS, all our hard drives used Master Boot Records to boot the system, and our hard drives were partitioned into different regions using the MBR partition scheme. That was just how it was done. And we liked it that way!
+
==== From a Clean Install ====
  
Then, along came EFI and UEFI, which are new-style firmware designed to boot systems, along with GPT partition tables to define disk partitions on disks larger than 2.2TB. All of the sudden, we had a variety of options for installing and booting Linux systems, turning what once was a one-method-fits-all approach into something a lot more complex.
+
Ensure that the [[X Window System]] is installed.
  
Let's take a moment to review the options available to you for configuring a hard drive to boot Funtoo Linux. This Install Guide uses, and recommends, the old-school method of BIOS booting and using an MBR. It works and (except for rare cases) is universally supported. There's nothing wrong with it. If your system disk is 2TB or smaller in size, it won't prevent you from using all of your disk's capacity, either.
+
=== Preparing to emerge ===
  
But, there are some situations where the old-school method isn't optimal. If you have a system disk >2TB in size, then MBR partitions won't allow you to access all your storage. So that's one reason. Another reason is that there are some so-called "PC" systems out there that don't support BIOS booting anymore, and force you to use UEFI to boot. So, out of compassion for people who fall into this predicament, this Install Guide documents UEFI booting too.
+
To get your system ready to emerge gnome, first set your system flavor to desktop, and enable the gnome profile mix-in. To accomplish this, do the following:
 +
{{console|recipe=setup,setup-light|desc=Set profile|body=
 +
# ##i##eselect profile set-flavor funtoo/1.0/linux-gnu/flavor/desktop
 +
# ##i##eselect profile add funtoo/1.0/linux-gnu/mix-ins/gnome
 +
}}
  
Our recommendation is still to go old-school unless you have reason not to. The boot loader we will be using to load the Linux kernel in this guide is called GRUB, so we call this method the '''BIOS + GRUB (MBR)''' method. It's the traditional method of setting up a PC-compatible system to boot Linux.
+
By enabling the gnome mix-in, various USE and other settings will be optimized to provide you with a pain-free GNOME installation experience.
  
If you need to use UEFI to boot, we recommend not using the MBR at all for booting, as some systems support this, but others don't. Instead, we recommend using UEFI to boot GRUB, which in turn will load Linux. We refer to this method as the '''UEFI + GRUB (GPT)''' method.
+
=== Emerging ===
  
And yes, there are even more methods, some of which are documented on the [[Boot Methods]] page. We used to recommend a '''BIOS + GRUB (GPT)''' method but it is not consistently supported across a wide variety of hardware.
+
You are provided with two packages that will pull in this desktop environment:
  
'''The big question is -- which boot method should you use?''' Here's how to tell.
+
* ''gnome''
  
;Principle 1 - Old School: If you can reliably boot System Rescue CD and it shows you an initial light blue menu, you are booting the CD using the BIOS, and it's likely that you can thus boot Funtoo Linux using the BIOS. So, go old-school and use BIOS booting, ''unless'' you have some reason to use UEFI, such as having a >2.2TB system disk. In that case, see Principle 2, as your system may also support UEFI booting.
+
{{fancynote|This is the "whole shabang" - pulls in a range of applications made for the gnome desktop environment including a few games, an archive manager, a system monitor, a web browser, a terminal, etc.}}
  
;Principle 2 - New School: If you can reliably boot System Rescue CD and it shows you an initial black and white menu -- congratulations, your system is configured to support UEFI booting. This means that you are ready to install Funtoo Linux to boot via UEFI. Your system may still support BIOS booting, but just be trying UEFI first. You can poke around in your BIOS boot configuration and play with this.
+
* ''gnome-light''
  
;What's the Big Difference between Old School and New School?: Here's the deal. If you go with old-school MBR partitions, your <code>/boot</code> partition will be an ext2 filesystem, and you'll use <code>fdisk</code> to create your MBR partitions. If you go with new-school GPT partitions and UEFI booting, your <code>/boot</code> partition will be a vfat filesystem, because this is what UEFI is able to read, and you will use <code>gdisk</code> to create your GPT partitions. And you'll install GRUB a bit differently. That's about all it comes down to, in case you were curious.
+
{{fancynote|As the name implies, this pulls in the base minimal you need to get a functioning GNOME Desktop Environment.}}
  
;Also Note: To install Funtoo Linux to boot via the New School UEFI method, you must boot System Rescue CD using UEFI -- and see an initial black and white screen. Otherwise, UEFI will not be active and you will not be able to set it up!
+
==== GNOME 3.14 from a clean install ====
  
{{Note|'''Some motherboards may appear to support UEFI, but don't.''' Do your research. For example, the Award BIOS in my Gigabyte GA-990FXA-UD7 rev 1.1 has an option to enable UEFI boot for CD/DVD. '''This is not sufficient for enabling UEFI boot for hard drives and installing Funtoo Linux.''' UEFI must be supported for both removable media (so you can boot System Rescue CD using UEFI) as well as fixed media (so you can boot your new Funtoo Linux installation.) It turns out that later revisions of this board (rev 3.0) have a new BIOS that fully supports UEFI boot.  This may point to a third principle -- know thy hardware.}}
+
===== gnome =====
  
==== Old-School (BIOS/MBR) Method ====
+
To emerge ''gnome'' run the following command
  
{{Note|Use this method if you are booting using your BIOS, and if your System Rescue CD initial boot menu was light blue. If you're going to use the new-school method, [[#New-School (UEFI/GPT) Method|click here to jump down to UEFI/GPT.]]}}
+
{{console|desc=Emerging GNOME|body=
 +
# ##i## emerge gnome
 +
}}
  
===== Preparation =====
+
===== gnome-light =====
  
First, it's a good idea to make sure that you've found the correct hard disk to partition. Try this command and verify that <code>/dev/sda</code> is the disk that you want to partition:
+
To emerge ''gnome-light'' run the following command
  
<console>
+
{{console|recipe=setup-light|desc=Emerging a minimal GNOME environment (alternative)|body=
# ##i##fdisk -l /dev/sda
+
# ##i## emerge gnome-light
 +
}}
  
Disk /dev/sda: 640.1 GB, 640135028736 bytes, 1250263728 sectors
+
==== Upgrading from GNOME 3.12 ====
Units = sectors of 1 * 512 = 512 bytes
+
Sector size (logical/physical): 512 bytes / 512 bytes
+
I/O size (minimum/optimal): 512 bytes / 512 bytes
+
Disk label type: gpt
+
  
 +
To update either ''gnome'' or ''gnome-light'' run the following command:
  
#         Start          End    Size  Type            Name
+
{{console|body=
1        2048  1250263694  596.2G  Linux filesyste Linux filesystem
+
# ##i## emerge -vauDN world
</console>
+
}}
 +
=== Subsystems ===
  
Now, it's recommended that you erase any existing MBR or GPT partition tables on the disk, which could confuse the system's BIOS at boot time. We do this using <code>sgdisk</code>:
+
==== Bluetooth ====
{{fancywarning|This will make any existing partitions inaccessible! You are '''strongly''' cautioned and advised to backup any critical data before proceeding.}}
+
  
<console>
+
For bluetooth support, ensure that:
# ##i##sgdisk --zap-all /dev/sda
+
  
Creating new GPT entries.
+
# Bluetooth support is enabled in your kernel (using modules is fine).
GPT data structures destroyed! You may now partition the disk using fdisk or
+
# Your bluetooth hardware is turned on.
other utilities.
+
# Add the <code>bluetooth</code> startup script to the default runlevel, and start it.
</console>
+
  
This output is also nothing to worry about, as the command still succeded:
+
This can be done as follows:
  
 
<console>
 
<console>
***************************************************************
+
# ##i##rc-update add bluetooth default
Found invalid GPT and valid MBR; converting MBR to GPT format
+
# ##i##rc
in memory.
+
***************************************************************
+
 
</console>
 
</console>
  
===== Partitioning =====
+
Once this is done, you should now be able to navigate to ''Settings'' -> ''Bluetooth'' and turn bluetooth on. The icon next to devices should now animate and you should be able to discover and add devices such as keyboards.
  
Now we will use <code>fdisk</code> to create the MBR partition table and partitions:
+
{{Note|1=
 +
Additional kernel drivers may need to be enabled for certain input devices. For example, for the bluetooth Apple Magic Trackpad, the following option must be enabled in your kernel:
  
<console>
+
{{kernelop|title=Device Drivers,HID support,HID bus support,Special HID drivers|desc=
# ##i##fdisk /dev/sda
+
<M> Apple Magic Mouse/Trackpad multi-touch support
</console>
+
}}}}
  
Within <code>fdisk</code>, follow these steps:
+
==== Printing ====
  
'''Empty the partition table''':
+
To enable printing support, add <code>cupsd</code> to the default runlevel:
  
 
<console>
 
<console>
Command (m for help): ##i##o ↵
+
# ##i##rc-update add cupsd default
 +
# ##i##rc
 
</console>
 
</console>
  
'''Create Partition 1''' (boot):
+
You should now be able to navigate to ''Settings'' -> ''Printers'' and add printers to your system, and print.
  
<console>
+
==== Scanning ====
Command (m for help): ##i##n ↵
+
Partition type (default p): ##i##↵
+
Partition number (1-4, default 1): ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+128M ↵
+
</console>
+
  
'''Create Partition 2''' (swap):
+
To enable scanning support, add your user account to the <code>lp</code> group. This will allow your user to access the USB scanner.
  
<console>
+
Then, <code>emerge xsane</code>, and run it. It should be able to access your scanner.
Command (m for help): ##i##n ↵
+
Partition type (default p): ##i##↵
+
Partition number (2-4, default 2): ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##+2G ↵
+
Command (m for help): ##i##t ↵
+
Partition number (1,2, default 2): ##i## ↵
+
Hex code (type L to list all codes): ##i##82 ↵
+
</console>
+
  
'''Create the root partition:'''
+
=== Finishing Touches ===
  
<console>
+
==== X ====
Command (m for help): ##i##n ↵
+
Partition type (default p): ##i##↵
+
Partition number (3,4, default 3): ##i##↵
+
First sector: ##i##↵
+
Last sector: ##i##↵
+
</console>
+
  
'''Verify the partition table:'''
+
===== Setting up xdm (GUI log-in) =====
  
<console>
+
Typically, you will want to use <code>gdm</code>, the GNOME display manager, to log in to GNOME. This will allow you to log in graphically, rather than using the text console.
Command (m for help): ##i##p
+
  
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
+
To enable gdm, edit <code>/etc/conf.d/xdm</code> and set <code>DISPLAYMANAGER</code> to <code>gdm</code> instead of <code>xdm</code>. Then, perform the following steps to add <code>xdm</code> to the default runlevel, and have it start automatically from now on when your system starts:
Units: sectors of 1 * 512 = 512 bytes
+
Sector size (logical/physical): 512 bytes / 512 bytes
+
I/O size (minimum/optimal): 512 bytes / 512 bytes
+
Disklabel type: dos
+
Disk identifier: 0x82abc9a6
+
  
Device    Boot    Start      End    Blocks  Id System
+
{{Note|Funtoo's <code>/etc/init.d/xdm</code> initscript has been modified to start the requisite services <code>dbus</code>, <code>openrc-settingsd</code> and <code>consolekit</code> prior to starting <code>gdm</code>.}}
/dev/sda1          2048    264191    131072  83 Linux
+
/dev/sda2        264192  4458495  2097152  82 Linux swap / Solaris
+
/dev/sda3        4458496 625142447 310341976  83 Linux
+
</console>
+
  
'''Write the parition table to disk:'''
+
{{console|recipe=setup|desc=Enable the GNOME display manager|body=
 +
# ##i## rc-update add xdm default
 +
}}
  
<console>
+
Then, if you want to start it now do:
Command (m for help): ##i##w
+
</console>
+
  
Your new MBR partition table will now be written to your system disk.
+
{{console|body=
 +
# ##i##rc
 +
}}
  
{{Note|You're done with partitioning! Now, jump over to [[#Creating filesystems|Creating filesystems]].}}
+
But you should reboot to avoid having an open login terminal.
  
==== New-School (UEFI/GPT) Method ====
+
===== Setting up xinitrc (text log-in) =====
  
{{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.}}
+
Adding the following to your <code>~/.xinitrc</code> file is sufficient:
  
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>:
+
<pre>
 +
# Fix Missing Applications in Gnome
 +
export XDG_MENU_PREFIX=gnome-
  
<console>
+
# Properly Launch the Desired X Session
# ##i##gdisk /dev/sda
+
exec ck-launch-session gnome-session
</console>
+
</pre>
  
Within <tt>gdisk</tt>, follow these steps:
+
Additionaly, if you need support for different input sources, there is no longer a need to configure IBus or SCIM in your <code>.xinitrc</code> file as GNOME uses IBus natively. Simply configure it in the Control Center under Region & Language.
  
'''Create a new empty partition table''' (This ''will'' erase all data on the disk when saved):
+
=== Automatically Starting Applications at Login ===
  
<console>
+
When using an old-fashioned <code>.xinitrc</code>, starting up applications when X starts is relatively easy. When using GDM, this can still be accomplished, by using the <code>~/.xprofile</code> file. Here's my sample <code>.xprofile</code> to start <code>xflux</code> to dim the screen at night:
Command: ##i##o ↵
+
This option deletes all partitions and creates a new protective MBR.
+
Proceed? (Y/N): ##i##y ↵
+
</console>
+
  
'''Create Partition 1''' (boot):
+
<pre>
 +
xflux -z 87107
 +
</pre>
  
<console>
+
{{Note|Remember to add a <code>&</code> at the end of any command that doesn't return to the shell prompt after running.}}
Command: ##i##n ↵
+
Partition Number: ##i##1 ↵
+
First sector: ##i##↵
+
Last sector: ##i##+500M ↵
+
Hex Code: ##i##↵
+
</console>
+
  
'''Create Partition 2''' (swap):
+
=== games ===
 +
Gnome has several games that can be added on to your install.  By default most games are not included in gnome's emerge.
  
<console>
+
Users wishing to play games need to be added to the games group:
Command: ##i##n ↵
+
{{console|body=###i## gpasswd -a $USER games}}
Partition Number: ##i##2 ↵
+
First sector: ##i##
+
Last sector: ##i##+4G ↵
+
Hex Code: ##i##8200 ↵
+
</console>
+
  
'''Create Partition 3''' (root):
+
game list:
 +
;gnome-sudoku
 +
;gnome-mastermind
 +
;gnome-nibbles
 +
;gnome-robots
 +
;gnome-chess
 +
;gnome-hearts
 +
;gnome-mahjongg
 +
;gnome-mines
 +
;gnome-klotski
 +
;gnome-tetravex
  
<console>
+
game system emulators:
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:
+
;gnomeboyadvance
 +
;gnome-mud
  
'''Write Partition Table To Disk''':
+
=== Significant Known Issues (Workarounds Available) ===
  
<console>
+
[https://bugs.funtoo.org/browse/FL-1678 FL-1678]: Bluetooth interface gives wrong pairing key
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.
+
[https://bugs.funtoo.org/browse/FL-1687 FL-1687]: Wallpaper corruption when resuming from suspend
  
Now, your GPT/GUID partitions have been created, and will show up as the following ''block devices'' under Linux:
+
[[Category:Desktop]]
 
+
[[Category:First Steps]]
* <tt>/dev/sda1</tt>, which will be used to hold the <tt>/boot</tt> filesystem,
+
[[Category:Official Documentation]]
* <tt>/dev/sda2</tt>, which will be used for swap space, and
+
* <tt>/dev/sda3</tt>, which will hold your root filesystem.
+
 
+
==== Creating filesystems ====
+
 
+
{{Note|This section covers both BIOS ''and'' UEFI installs. Don't skip it!}}
+
 
+
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.
+
}}
+
 
+
==== Mounting filesystems ====
+
 
+
Mount the newly-created filesystems as follows, creating <code>/mnt/funtoo</code> as the installation mount point:
+
 
+
<console>
+
# ##i##mkdir /mnt/funtoo
+
# ##i##mount /dev/sda3 /mnt/funtoo
+
# ##i##mkdir /mnt/funtoo/boot
+
# ##i##mount /dev/sda1 /mnt/funtoo/boot
+
</console>
+
 
+
Optionally, if you have a separate filesystem for <code>/home</code> or anything else:
+
 
+
<console>
+
# ##i##mkdir /mnt/funtoo/home
+
# ##i##mount /dev/sda4 /mnt/funtoo/home
+
</console>
+
 
+
If you have <code>/tmp</code> or <code>/var/tmp</code> on a separate filesystem, be sure to change the permissions of the mount point to be globally-writeable after mounting, as follows:
+
 
+
<console>
+
# ##i##chmod 1777 /mnt/funtoo/tmp
+
</console>
+

Revision as of 17:45, February 22, 2015

What is GNOME?

"GNOME 3 is an easy and elegant way to use your computer. It is designed to put you in control and bring freedom to everybody. GNOME 3 is developed by the GNOME community, a diverse, international group of contributors that is supported by an independent, non-profit foundation." — GNOME

Prerequisites

From a Clean Install

Ensure that the X Window System is installed.

Preparing to emerge

To get your system ready to emerge gnome, first set your system flavor to desktop, and enable the gnome profile mix-in. To accomplish this, do the following:

# eselect profile set-flavor funtoo/1.0/linux-gnu/flavor/desktop
# eselect profile add funtoo/1.0/linux-gnu/mix-ins/gnome

Console: Set profileThe given value was not understood.

By enabling the gnome mix-in, various USE and other settings will be optimized to provide you with a pain-free GNOME installation experience.

Emerging

You are provided with two packages that will pull in this desktop environment:

  • gnome
Note

This is the "whole shabang" - pulls in a range of applications made for the gnome desktop environment including a few games, an archive manager, a system monitor, a web browser, a terminal, etc.

  • gnome-light
Note

As the name implies, this pulls in the base minimal you need to get a functioning GNOME Desktop Environment.

GNOME 3.14 from a clean install

gnome

To emerge gnome run the following command

#  emerge gnome

Console: Emerging GNOME

gnome-light

To emerge gnome-light run the following command

#  emerge gnome-light

Console: Emerging a minimal GNOME environment (alternative)The given value was not understood.

Upgrading from GNOME 3.12

To update either gnome or gnome-light run the following command:

#  emerge -vauDN world

Subsystems

Bluetooth

For bluetooth support, ensure that:

  1. Bluetooth support is enabled in your kernel (using modules is fine).
  2. Your bluetooth hardware is turned on.
  3. Add the bluetooth startup script to the default runlevel, and start it.

This can be done as follows:

# rc-update add bluetooth default
# rc

Once this is done, you should now be able to navigate to Settings -> Bluetooth and turn bluetooth on. The icon next to devices should now animate and you should be able to discover and add devices such as keyboards.

Note

Additional kernel drivers may need to be enabled for certain input devices. For example, for the bluetooth Apple Magic Trackpad, the following option must be enabled in your kernel:

Under Device Drivers-->HID support-->HID bus support-->Special HID drivers:

<M> Apple Magic Mouse/Trackpad multi-touch support

Printing

To enable printing support, add cupsd to the default runlevel:

# rc-update add cupsd default
# rc

You should now be able to navigate to Settings -> Printers and add printers to your system, and print.

Scanning

To enable scanning support, add your user account to the lp group. This will allow your user to access the USB scanner.

Then, emerge xsane, and run it. It should be able to access your scanner.

Finishing Touches

X

Setting up xdm (GUI log-in)

Typically, you will want to use gdm, the GNOME display manager, to log in to GNOME. This will allow you to log in graphically, rather than using the text console.

To enable gdm, edit /etc/conf.d/xdm and set DISPLAYMANAGER to gdm instead of xdm. Then, perform the following steps to add xdm to the default runlevel, and have it start automatically from now on when your system starts:

Note

Funtoo's /etc/init.d/xdm initscript has been modified to start the requisite services dbus, openrc-settingsd and consolekit prior to starting gdm.

#  rc-update add xdm default

Console: Enable the GNOME display managerThe given value was not understood.

Then, if you want to start it now do:

# rc


But you should reboot to avoid having an open login terminal.

Setting up xinitrc (text log-in)

Adding the following to your ~/.xinitrc file is sufficient:

# Fix Missing Applications in Gnome
export XDG_MENU_PREFIX=gnome-

# Properly Launch the Desired X Session
exec ck-launch-session gnome-session

Additionaly, if you need support for different input sources, there is no longer a need to configure IBus or SCIM in your .xinitrc file as GNOME uses IBus natively. Simply configure it in the Control Center under Region & Language.

Automatically Starting Applications at Login

When using an old-fashioned .xinitrc, starting up applications when X starts is relatively easy. When using GDM, this can still be accomplished, by using the ~/.xprofile file. Here's my sample .xprofile to start xflux to dim the screen at night:

xflux -z 87107
Note

Remember to add a & at the end of any command that doesn't return to the shell prompt after running.

games

Gnome has several games that can be added on to your install. By default most games are not included in gnome's emerge.

Users wishing to play games need to be added to the games group:

# gpasswd -a $USER games


game list:

gnome-sudoku
gnome-mastermind
gnome-nibbles
gnome-robots
gnome-chess
gnome-hearts
gnome-mahjongg
gnome-mines
gnome-klotski
gnome-tetravex

game system emulators:

gnomeboyadvance
gnome-mud

Significant Known Issues (Workarounds Available)

FL-1678: Bluetooth interface gives wrong pairing key

FL-1687: Wallpaper corruption when resuming from suspend