Difference between pages "Package:Feh" and "Install/Stage3"

(Difference between pages)
 
(Setting the Date)
 
Line 1: Line 1:
{{Ebuild
+
<noinclude>
|Summary=A fast, lightweight imageviewer using imlib2
+
{{InstallPart|the process of installing the Stage3 tarball}}
|CatPkg=media-gfx/feh
+
</noinclude>
|Maintainer=
+
=== Installing the Stage 3 tarball ===
|Homepage=http://feh.finalrewind.org/
+
}}
+
=== What is feh? ===
+
  
<blockquote>
+
After creating filesystems, the next step is downloading the initial Stage 3 tarball. The Stage 3 is a pre-compiled system used as a starting point to install Funtoo Linux. Load one of the following URLs in another browser window:
feh is an X11 image viewer aimed mostly at console users. Unlike most other viewers, it does not have a fancy GUI, but simply displays images. It is controlled via commandline arguments and configurable key/mouse actions.[http://feh.finalrewind.org/ Feh homepage]
+
</blockquote>
+
  
== USE-Flags ==
+
{{MirrorList}}
  
;<code>curl</code>: Add support for the Client-Side URL transfer library.
+
Now, let's navigate the directories on the mirrors to find the appropriate build of Funtoo Linux for you.
;<code>debug</code>: Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces, see http://www.gentoo.org/proj/en/qa/backtraces.xml.
+
 
;<code>exif</code>: Add support for reading EXIF headers from JPEG and TIFF images.
+
==== Which Build? ====
;<code>xinerama</code>: Add support for the xinerama X11 extension, which is mandator if you work in a multiple monitor setup.
+
 
 +
'''If you're not sure, pick <code>funtoo-current</code>.'''
 +
 
 +
Funtoo Linux has various different 'builds', or variants. Here is a list of the various builds that are available, and what their distinctive features are:
 +
 
 +
{{TableStart}}
 +
<tr><th class="info">Build</th><th class="info">Description</th></tr>
 +
<tr><td><code>funtoo-current</code></td><td>The most commonly-selected build of Funtoo Linux. Receives rapid updates and preferred by desktop users.</td></tr>
 +
<tr><td><code>funtoo-current-hardened</code></td><td>Same package set as <code>funtoo-current</code>, but with a hardened, exploit-resistant toolchain.</td></tr>
 +
<tr><td><code>funtoo-stable</code></td><td>Emphasizes less-frequent package updates and trusted, reliable versions of packages over the latest versions.</td></tr>
 +
{{TableEnd}}
 +
 
 +
If you want to read more about this, have a look at [[Funtoo_Linux#What_are_the_differences_between_.27stable.27.2C_.27current.27_and_.27experimental.27_.3F|Differences between stable, current and experimental]].
 +
 
 +
==== What Architecture?  ====
 +
 
 +
'''If you're not sure, pick <code>x86-64bit</code>, or possibly <code>pure64</code> for server systems.'''
 +
 
 +
For PC-compatible systems, the following choices are available:
 +
 
 +
{{TableStart}}
 +
<tr><th class="info">Architecture</th><th class="info">Description</th></tr>
 +
<tr><td><code>x86-64bit</code></td><td>For modern 64-bit processors. Uses new 64-bit instructions and address space. Maintains 32-bit compatibility with multilib.</td></tr>
 +
<tr><td><code>pure64</code></td><td>For modern 64-bit processors but with no support for 32-bit compatibility.</td></tr>
 +
<tr><td><code>x86-32bit</code></td><td>For older 32-bit systems such as Athlon XP, Pentium 4, or earlier Atom.</td></tr>
 +
{{TableEnd}}
 +
 
 +
==== Your SubArch ====
 +
 
 +
Inside <code>/funtoo-current/x86-64bit/</code> on one of our mirrors, you'll see a bunch of directories for various ''subarches'' of Funtoo Linux. Subarches are builds of Funtoo Linux that are designed to run on a particular type of CPU, to offer the best possible performance. They also take advantage of the instruction sets available for each CPU.
 +
 
 +
If you are using an AMD-based CPU, download a stage3 from <code>generic_64</code>, <code>amd64-k8</code>, <code>amd64-k10</code>, <code>amd64-bulldozer</code>, <code>amd64-piledriver</code>, <code>amd64-steamroller</code> or <code>amd64-jaguar</code>.  See [[Subarches]] for help figuring out what AMD subarch is best for you.
 +
 
 +
If you are using an Intel-based CPU, download a stage3 from <code>generic_64</code>, <code>atom_64</code>, <code>core2_64</code> or <code>corei7</code>. Note that <code>corei7</code> is ideal for any modern Intel processor, including Core i3 and Core i5, and many Xeons.
 +
 
 +
If you are using a 32-bit CPU, download a stage3 from <code>generic_32</code>, <code>i686</code>, <code>core2_32</code>, <code>atom_32</code> or <code>athlon-xp</code>.
 +
 
 +
==== Setting the Date ====
 +
 
 +
{{fancyimportant|If your system's date and time are too far off (typically by months or years,) then it may prevent Portage from properly downloading source tarballs. This is because some of our sources are downloaded via HTTPS, which use SSL certificates and are marked with an activation and expiration date. However, if you system time is relatively close to correct, you can probably skip this step for now.}}
 +
 
 +
Now is a good time to verify the date and time are correctly set to UTC. Use the <code>date</code> command to verify the date and time:
  
== Installing feh ==
 
After adding your USE flags (or not) to <tt>/etc/portage/package.use/feh</tt>, you can emerge feh:
 
 
<console>
 
<console>
###i## emerge feh
+
# ##i##date
 +
Fri Jul 15 19:47:18 UTC 2011
 
</console>
 
</console>
  
== Using feh ==
+
If the date and/or time need to be corrected, do so using <code>date MMDDhhmmYYYY</code>, keeping in mind <code>hhmm</code> are in 24-hour format. The example below changes the date and time to "July 16th, 2011 @ 8:00PM" UTC:
=== Set desktop background ===
+
<tt>feh</tt> has several options for setting your desktop background:
+
* <tt>--bg-center</tt>: Center the image file on the background. If the image file is smaller in resolution than the screen resolution, it will have black borders around it.
+
* <tt>--bg-scale</tt>: Fit the image to the background without repeating it, cutting parts of the image off, or using black borders. Because of these changes, the aspect ratio is not preserved.
+
* <tt>--bg-fill</tt>: Similar to <tt>--bg-scale</tt> except that it tries to fill the image to the screen while maintaining its aspect ratio. This may result in parts of the image being cut off.
+
* <tt>--bg-max</tt>: Similar to <tt>--bg-fill</tt>, except that scales the image to the maximum size that fits the screen. This leads to black borders on one side.
+
* <tt>--bg-tile</tt>: Tile the image across the screen.
+
  
Here is an example:
 
 
<console>
 
<console>
###i## feh --bg-scale ~/path/to/picture.jpg
+
# ##i##date 071620002011
 +
Fri Jul 16 20:00:00 UTC 2011
 
</console>
 
</console>
  
=== Source fehbg to set your wallpaper in Openbox ===
+
Once you have set the system clock, it's a very good idea to copy the time to the hardware clock, so it persists across reboots:
After you have run <tt>feh</tt> one time, the directory of the image file is stored in <tt>~/.fehbg</tt>. This file can be sourced in your <tt>.config/openbox/autostart</tt> to load the picture instead of typing out <tt>feh --bg-scale /picture/location.jpg</tt>:
+
 
 +
<console>
 +
# ##i##hwclock --systohc
 +
</console>
 +
 
 +
==== Download the Stage3 ====
 +
Once you are in your Funtoo Linux root filesystem, use <code>wget</code> to download the Stage 3 tarball you have chosen to use as the basis for your new Funtoo Linux system. It should be saved to the <code>/mnt/funtoo</code> directory as follows:
 +
 
 +
<console># ##i##cd /mnt/funtoo
 +
# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz
 +
</console>
 +
 
 +
Note that 64-bit systems can run 32-bit or 64-bit stages, but 32-bit systems can only run 32-bit stages. Make sure that you select a Stage 3 build that is appropriate for your CPU. If you are not certain, it is a safe bet to choose the <code>generic_64</code> or <code>generic_32</code> stage. Consult the [[Download]] page for more information.
 +
 
 +
Once the stage is downloaded, extract the contents with the following command, substituting in the actual name of your stage 3 tarball:
 +
<console>
 +
# ##i##tar xpf stage3-latest.tar.xz
 +
</console>
  
{{file|name=~/.config/openbox/autostart|desc= |body=
+
{{important|It is very important to use <code>tar's</code> "<code>'''p'''</code>" option when extracting the Stage 3 tarball - it tells <code>tar</code> to ''preserve'' any permissions and ownership that exist within the archive. Without this option, your Funtoo Linux filesystem permissions will be incorrect.}}
...
+
~/.fehbg &
+
...
+
}}
+
{{EbuildFooter}}
+

Latest revision as of 23:41, November 19, 2014


Note

This is a template that is used as part of the Installation instructions which covers: the process of installing the Stage3 tarball. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.


Installing the Stage 3 tarball

After creating filesystems, the next step is downloading the initial Stage 3 tarball. The Stage 3 is a pre-compiled system used as a starting point to install Funtoo Linux. Load one of the following URLs in another browser window:

Now, let's navigate the directories on the mirrors to find the appropriate build of Funtoo Linux for you.

Which Build?

If you're not sure, pick funtoo-current.

Funtoo Linux has various different 'builds', or variants. Here is a list of the various builds that are available, and what their distinctive features are:

BuildDescription
funtoo-currentThe most commonly-selected build of Funtoo Linux. Receives rapid updates and preferred by desktop users.
funtoo-current-hardenedSame package set as funtoo-current, but with a hardened, exploit-resistant toolchain.
funtoo-stableEmphasizes less-frequent package updates and trusted, reliable versions of packages over the latest versions.

If you want to read more about this, have a look at Differences between stable, current and experimental.

What Architecture?

If you're not sure, pick x86-64bit, or possibly pure64 for server systems.

For PC-compatible systems, the following choices are available:

ArchitectureDescription
x86-64bitFor modern 64-bit processors. Uses new 64-bit instructions and address space. Maintains 32-bit compatibility with multilib.
pure64For modern 64-bit processors but with no support for 32-bit compatibility.
x86-32bitFor older 32-bit systems such as Athlon XP, Pentium 4, or earlier Atom.

Your SubArch

Inside /funtoo-current/x86-64bit/ on one of our mirrors, you'll see a bunch of directories for various subarches of Funtoo Linux. Subarches are builds of Funtoo Linux that are designed to run on a particular type of CPU, to offer the best possible performance. They also take advantage of the instruction sets available for each CPU.

If you are using an AMD-based CPU, download a stage3 from generic_64, amd64-k8, amd64-k10, amd64-bulldozer, amd64-piledriver, amd64-steamroller or amd64-jaguar. See Subarches for help figuring out what AMD subarch is best for you.

If you are using an Intel-based CPU, download a stage3 from generic_64, atom_64, core2_64 or corei7. Note that corei7 is ideal for any modern Intel processor, including Core i3 and Core i5, and many Xeons.

If you are using a 32-bit CPU, download a stage3 from generic_32, i686, core2_32, atom_32 or athlon-xp.

Setting the Date

Important

If your system's date and time are too far off (typically by months or years,) then it may prevent Portage from properly downloading source tarballs. This is because some of our sources are downloaded via HTTPS, which use SSL certificates and are marked with an activation and expiration date. However, if you system time is relatively close to correct, you can probably skip this step for now.

Now is a good time to verify the date and time are correctly set to UTC. Use the date command to verify the date and time:

# date
Fri Jul 15 19:47:18 UTC 2011

If the date and/or time need to be corrected, do so using date MMDDhhmmYYYY, keeping in mind hhmm are in 24-hour format. The example below changes the date and time to "July 16th, 2011 @ 8:00PM" UTC:

# date 071620002011
Fri Jul 16 20:00:00 UTC 2011

Once you have set the system clock, it's a very good idea to copy the time to the hardware clock, so it persists across reboots:

# hwclock --systohc

Download the Stage3

Once you are in your Funtoo Linux root filesystem, use wget to download the Stage 3 tarball you have chosen to use as the basis for your new Funtoo Linux system. It should be saved to the /mnt/funtoo directory as follows:

# cd /mnt/funtoo
# wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/generic_64/stage3-latest.tar.xz

Note that 64-bit systems can run 32-bit or 64-bit stages, but 32-bit systems can only run 32-bit stages. Make sure that you select a Stage 3 build that is appropriate for your CPU. If you are not certain, it is a safe bet to choose the generic_64 or generic_32 stage. Consult the Download page for more information.

Once the stage is downloaded, extract the contents with the following command, substituting in the actual name of your stage 3 tarball:

# tar xpf stage3-latest.tar.xz

Important

It is very important to use tar's "p" option when extracting the Stage 3 tarball - it tells tar to preserve any permissions and ownership that exist within the archive. Without this option, your Funtoo Linux filesystem permissions will be incorrect.