The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Funtoo Linux First Steps"
(26 intermediate revisions by 7 users not shown) | |||
Line 1: | Line 1: | ||
<languages/> | |||
<translate><!--T:1--> | |||
{{Subpages|Helpful Applications for Daily Usage,Installing a Graphical Environment,Creating a User Account}} | |||
If you are brand new to Gentoo Linux or Funtoo Linux, this page will help you to get familiar with your new system, and how it works. | If you are brand new to Gentoo Linux or Funtoo Linux, this page will help you to get familiar with your new system, and how it works. | ||
== Intro to Emerge: Installing an Editor == | == Intro to Emerge: Installing an Editor == <!--T:2--> | ||
By default, Funtoo Linux has the | <!--T:3--> | ||
By default, Funtoo Linux has the {{c|nano}} and {{c|vi}} editors installed. {{c|nano}} is the default editor. | |||
If you are new to Funtoo Linux, you have probably heard about | <!--T:4--> | ||
If you are new to Funtoo Linux, you have probably heard about {{c|[[emerge]]}}, the Funtoo and Gentoo Linux command for installing packages from the Portage tree. Funtoo Linux has a git-based Portage tree, which is located at {{f|/var/git/meta-repo}} by default. It contains scripts called ''ebuilds'' that describe how to build and install packages from source. {{c|emerge}} is used to run these scripts and install packages, as follows:</translate> | |||
<console> | <console> | ||
Line 11: | Line 17: | ||
</console> | </console> | ||
<translate><!--T:5--> | |||
An important note about any commands you specify on an {{c|emerge}} command-line -- Portage will automatically add them to your "selected" set, which means that Portage now understands that you want to keep this package updated as part of your system. | An important note about any commands you specify on an {{c|emerge}} command-line -- Portage will automatically add them to your "selected" set, which means that Portage now understands that you want to keep this package updated as part of your system. | ||
Using the {{c|--pretend}} ({{c|-p}}) option, you can see what {{c|emerge}} ''would'' do, without actually doing it: | <!--T:6--> | ||
Using the {{c|--pretend}} ({{c|-p}}) option, you can see what {{c|emerge}} ''would'' do, without actually doing it:</translate> | |||
<console> | <console> | ||
# ##i##emerge -p vim | # ##i##emerge -p vim | ||
</console> | </console> | ||
Another equally handy option is the {{c|-a}}, or {{c|--ask}} option, which will display the packages to be merged, and then ask for confirmation from you as to whether you would like to proceed and merge the packages, or not: | <translate><!--T:7--> Another equally handy option is the {{c|-a}}, or {{c|--ask}} option, which will display the packages to be merged, and then ask for confirmation from you as to whether you would like to proceed and merge the packages, or not:</translate> | ||
{{console|body= | {{console|body= | ||
# ##i##emerge -a emacs | # ##i##emerge -a emacs | ||
##g##These are the packages that would be merged, in order: | \##g##These are the packages that would be merged, in order: | ||
Calculating dependencies... done! | Calculating dependencies... done! | ||
Line 29: | Line 37: | ||
[##g##ebuild N ##!g##] ##g##net-libs/liblockfile-1.09 | [##g##ebuild N ##!g##] ##g##net-libs/liblockfile-1.09 | ||
[##g##ebuild N ##!g##] ##g##app-emacs/emacs-common-gentoo-1.3-r1##!g## USE="##bl##-X -emacs22icons##!bl##" | [##g##ebuild N ##!g##] ##g##app-emacs/emacs-common-gentoo-1.3-r1##!g## USE="##bl##-X -emacs22icons##!bl##" | ||
[##g##ebuild N ##!g##] ##g####b##app-editors/emacs-23.4-r1##!g####!b## USE="##r##alsa gif gpm jpeg png tiff xpm ##!r###bl##-X -Xaw3d ##!bl##(##bl##-aqua##!bl##)##bl## -athena -dbus -gconf -gtk -gzip-el -hesiod -kerberos -livecd -m17n-lib -motif -sound -source -svg -toolkit-scroll-bars -xft##!bl##" | [##g##ebuild N ##!g##] ##g####b##app-editors/emacs-23.4-r1##!g####!b## USE="##r##alsa gif gpm jpeg png tiff xpm ##!r####bl##-X -Xaw3d ##!bl##(##bl##-aqua##!bl##)##bl## -athena -dbus -gconf -gtk -gzip-el -hesiod -kerberos -livecd -m17n-lib -motif -sound -source -svg -toolkit-scroll-bars -xft##!bl##" | ||
[##g##ebuild N ##!g##] ##g##virtual/emacs-23 | [##g##ebuild N ##!g##] ##g##virtual/emacs-23 | ||
##b##Would you like to merge these packages? [##g##Yes##!g##/##r##No##!r##]##!b## ##i##y | \##b##Would you like to merge these packages? [##g##Yes##!g##/##r##No##!r##]##!b## ##i##y | ||
}} | }} | ||
Line 39: | Line 47: | ||
In the above {{c|emerge}} output, you can see some text beginning with {{c|1=USE=}} on the {{c|app-editors/emacs}} line. This means that this package has a number of optional build-time features which can be controlled using Portage USE variables. | In the above {{c|emerge}} output, you can see some text beginning with {{c|1=USE=}} on the {{c|app-editors/emacs}} line. This means that this package has a number of optional build-time features which can be controlled using Portage USE variables. | ||
It is possible to enable USE variables globally in {{f|/etc/make.conf}}, on a per-package basis in {{f|/etc/portage/package.use}}, or as logical sets by using [[Funtoo Profiles]]. It's recommended that you first take a look at [[Funtoo Profiles]] and see if there may be sets of USE variables that you want to enable as a group. You can set your system ''flavor'' to more accurately reflect the intended use of your Funtoo system, and by doing so, many more USE variables will be set (or unset) to reasonable defaults for your intended use. | It is possible to enable USE variables globally in {{f|/etc/portage/make.conf}}, on a per-package basis in {{f|/etc/portage/package.use}}, or as logical sets by using [[Funtoo Profiles]]. It's recommended that you first take a look at [[Funtoo Profiles]] and see if there may be sets of USE variables that you want to enable as a group. You can set your system ''flavor'' to more accurately reflect the intended use of your Funtoo system, and by doing so, many more USE variables will be set (or unset) to reasonable defaults for your intended use. | ||
These USE variables can be set globally by adding a line such as this to {{f|/etc/make.conf}}: | These USE variables can be set globally by adding a line such as this to {{f|/etc/portage/make.conf}}: | ||
{{file|lang=bash|name=/etc/make.conf|body= | {{file|lang=bash|name=/etc/portage/make.conf|body= | ||
USE="gif jpeg png tiff xpm" | USE="gif jpeg png tiff xpm" | ||
}} | }} | ||
Line 59: | Line 67: | ||
==== Default editor ==== | ==== Default editor ==== | ||
Funtoo Linux also has a special meta-command called | Funtoo Linux also has a special meta-command called {{c|eselect}}, which can be used to set many default system settings. One of the things it is used for is to set the default editor used by things like {{c|crontab -e}}, etc that will automatically start an editor when run. Here is how to use {{c|eselect}} to change the default system editor: | ||
{{console|body= | |||
# ##i##eselect editor list | # ##i##eselect editor list | ||
Available targets for the EDITOR variable: | Available targets for the EDITOR variable: | ||
Line 72: | Line 80: | ||
Setting EDITOR to /usr/bin/vi ... | Setting EDITOR to /usr/bin/vi ... | ||
Run ". /etc/profile" to update the variable in your shell. | Run ". /etc/profile" to update the variable in your shell. | ||
}} | |||
After logging in again, or typing | After logging in again, or typing {{c|source /etc/profile}} in the current shell, the new system editor will be active. | ||
Note that if you want to use vim instead of a vi through busybox you also need to run: | Note that if you want to use vim instead of a vi through busybox you also need to run: | ||
{{console|body= | |||
# ##i##eselect vi set vim | # ##i##eselect vi set vim | ||
}} | |||
=== Updating your system === | === Updating your system === | ||
Sometimes, you may want to update the packages on your system. Often, this is done after you run | Sometimes, you may want to update the packages on your system. Often, this is done after you run {{c|ego sync}}, which will grab Portage tree updates from the main Funtoo Linux Portage tree: | ||
{{console|body= | |||
# ##i## | # ##i##ego sync | ||
\##g##Syncing meta-repo | |||
(cd /var/git/meta-repo && git remote set-branches --add origin master) | |||
remote: Counting objects: | (cd /var/git/meta-repo && git fetch origin refs/heads/master:refs/remotes/origin/master) | ||
remote: Compressing objects: 100% ( | remote: Counting objects: 95, done. | ||
remote: Total | remote: Compressing objects: 100% (64/64), done. | ||
remote: Total 95 (delta 31), reused 95 (delta 31), pack-reused 0 | |||
Unpacking objects: 100% (95/95), done. | |||
}} | |||
You may also want to update your system after you have changed USE flag settings. To take advantage of the USE flags you have just enabled, it's necessary to recompile everything that includes them. | You may also want to update your system after you have changed USE flag settings. To take advantage of the USE flags you have just enabled, it's necessary to recompile everything that includes them. | ||
Below, you'll find a recommended | Below, you'll find a recommended {{c|emerge}} command for updating your entire system. The <tt>-a</tt> option will cause <tt>emerge</tt> to prompt you for confirmation before starting the merge: | ||
{{console|body= | |||
# ##i##emerge -auDN world | # ##i##emerge -auDN @world | ||
}} | |||
{{c|-u}} tells {{c|emerge}} to update any already-installed but out-of-date packages that we specify on the command-line. The {{c|-D}} option tells {{c|emerge}} to perform a ''deep'' dependency tree graph, so it will include sub-dependencies of packages that we have specified on the command line as well. This allows {{c|emerge}} to perform as thorough an update of your system as possible. | |||
The | The {{c|-N}} ({{c|--newuse}}) option tells Portage to check for any new USE flags that have been enabled or disabled, and rebuild packages so that all USE flags are set as currently defined in [[Funtoo Profiles]], {{f|/etc/portage/make.conf}} and {{f|/etc/portage/package.use}}. | ||
<tt>world</tt> is a "meta-package" or "package set" which includes every package that you have manually installed plus all packages in the system set | <tt>world</tt> is a "meta-package" or "package set" which includes every package that you have manually installed plus all packages in the system set. If you want to see a list of all these packages, look at {{f|/var/lib/portage/world}}: | ||
{{console|body= | |||
# ##i##cat /var/lib/portage/world | # ##i##cat /var/lib/portage/world | ||
app-editors/vim | app-editors/vim | ||
Line 199: | Line 133: | ||
sys-fs/reiserfsprogs | sys-fs/reiserfsprogs | ||
sys-kernel/vanilla-sources | sys-kernel/vanilla-sources | ||
}} | |||
==== Updating a few packages ==== | ==== Updating a few packages ==== | ||
Line 210: | Line 141: | ||
# ##i##emerge -auDN vim emacs | # ##i##emerge -auDN vim emacs | ||
</console> | </console> | ||
[[Category:HOWTO]] | [[Category:HOWTO]] | ||
[[Category:Install]] | [[Category:Install]] | ||
[[Category:Featured]] | [[Category:Featured]] |
Latest revision as of 21:51, August 19, 2019
If you are brand new to Gentoo Linux or Funtoo Linux, this page will help you to get familiar with your new system, and how it works.
Intro to Emerge: Installing an Editor
By default, Funtoo Linux has the nano
and vi
editors installed. nano
is the default editor.
If you are new to Funtoo Linux, you have probably heard about emerge
, the Funtoo and Gentoo Linux command for installing packages from the Portage tree. Funtoo Linux has a git-based Portage tree, which is located at /var/git/meta-repo
by default. It contains scripts called ebuilds that describe how to build and install packages from source. emerge
is used to run these scripts and install packages, as follows:
root # emerge vim
An important note about any commands you specify on an emerge
command-line -- Portage will automatically add them to your "selected" set, which means that Portage now understands that you want to keep this package updated as part of your system.
Using the --pretend
(-p
) option, you can see what emerge
would do, without actually doing it:
root # emerge -p vim
Another equally handy option is the -a
, or --ask
option, which will display the packages to be merged, and then ask for confirmation from you as to whether you would like to proceed and merge the packages, or not:
root # emerge -a emacs These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] app-admin/eselect-emacs-1.13 [ebuild N ] net-libs/liblockfile-1.09 [ebuild N ] app-emacs/emacs-common-gentoo-1.3-r1 USE="-X -emacs22icons" [ebuild N ] app-editors/emacs-23.4-r1 USE="alsa gif gpm jpeg png tiff xpm -X -Xaw3d (-aqua) -athena -dbus -gconf -gtk -gzip-el -hesiod -kerberos -livecd -m17n-lib -motif -sound -source -svg -toolkit-scroll-bars -xft" [ebuild N ] virtual/emacs-23 Would you like to merge these packages? [Yes/No] y
USE Variables
In the above emerge
output, you can see some text beginning with USE=
on the app-editors/emacs
line. This means that this package has a number of optional build-time features which can be controlled using Portage USE variables.
It is possible to enable USE variables globally in /etc/portage/make.conf
, on a per-package basis in /etc/portage/package.use
, or as logical sets by using Funtoo Profiles. It's recommended that you first take a look at Funtoo Profiles and see if there may be sets of USE variables that you want to enable as a group. You can set your system flavor to more accurately reflect the intended use of your Funtoo system, and by doing so, many more USE variables will be set (or unset) to reasonable defaults for your intended use.
These USE variables can be set globally by adding a line such as this to /etc/portage/make.conf
:
/etc/portage/make.conf
(bash source code) USE="gif jpeg png tiff xpm"
Or, alternatively, you can enable just these USE variables for emacs by adding the following line to /etc/portage/package.use
:
/etc/portage/package.use
(bash source code) app-editors/emacs gif jpeg png tiff xpm
However, it's generally best to find a Funtoo Profile flavor or mix-in that serves your purpose. For example, setting your system to be a desktop by running epro flavor desktop
or adding the appropriate mix-in via epro mix-in +mediaformat-gfx-common
gives you more opportunity to dial in sets of related USE variables with a single command.
See the emerge page for more information on various emerge command-line options and best practices.
Default editor
Funtoo Linux also has a special meta-command called eselect
, which can be used to set many default system settings. One of the things it is used for is to set the default editor used by things like crontab -e
, etc that will automatically start an editor when run. Here is how to use eselect
to change the default system editor:
root # eselect editor list Available targets for the EDITOR variable: [1] /bin/nano [2] /bin/ed [3] /usr/bin/ex [4] /usr/bin/vi [ ] (free form) root # eselect editor set 4 Setting EDITOR to /usr/bin/vi ... Run ". /etc/profile" to update the variable in your shell.
After logging in again, or typing source /etc/profile
in the current shell, the new system editor will be active.
Note that if you want to use vim instead of a vi through busybox you also need to run:
root # eselect vi set vim
Updating your system
Sometimes, you may want to update the packages on your system. Often, this is done after you run ego sync
, which will grab Portage tree updates from the main Funtoo Linux Portage tree:
root # ego sync Syncing meta-repo (cd /var/git/meta-repo && git remote set-branches --add origin master) (cd /var/git/meta-repo && git fetch origin refs/heads/master:refs/remotes/origin/master) remote: Counting objects: 95, done. remote: Compressing objects: 100% (64/64), done. remote: Total 95 (delta 31), reused 95 (delta 31), pack-reused 0 Unpacking objects: 100% (95/95), done.
You may also want to update your system after you have changed USE flag settings. To take advantage of the USE flags you have just enabled, it's necessary to recompile everything that includes them.
Below, you'll find a recommended emerge
command for updating your entire system. The -a option will cause emerge to prompt you for confirmation before starting the merge:
root # emerge -auDN @world
-u
tells emerge
to update any already-installed but out-of-date packages that we specify on the command-line. The -D
option tells emerge
to perform a deep dependency tree graph, so it will include sub-dependencies of packages that we have specified on the command line as well. This allows emerge
to perform as thorough an update of your system as possible.
The -N
(--newuse
) option tells Portage to check for any new USE flags that have been enabled or disabled, and rebuild packages so that all USE flags are set as currently defined in Funtoo Profiles, /etc/portage/make.conf
and /etc/portage/package.use
.
world is a "meta-package" or "package set" which includes every package that you have manually installed plus all packages in the system set. If you want to see a list of all these packages, look at /var/lib/portage/world
:
root # cat /var/lib/portage/world app-editors/vim app-portage/eix app-portage/gentoolkit dev-vcs/git net-misc/bridge-utils net-misc/dhcpcd net-misc/keychain sys-apps/gptfdisk sys-apps/pciutils sys-devel/bc sys-fs/reiserfsprogs sys-kernel/vanilla-sources
Updating a few packages
If we simply wanted to rebuild a few packages to reflect updated USE flag settings, we could specify it instead of world. Be sure to include the -N option:
root # emerge -auDN vim emacs