Difference between pages "X Window System" and "Package:Layman"

(Difference between pages)
(correct echo)
 
m
 
Line 1: Line 1:
=== X.Org ===
+
{{Ebuild
 +
|Summary=Tool to manage Gentoo overlays
 +
|CatPkg=app-portage/layman
 +
|Homepage=http://layman.sourceforge.net/
 +
}}
 +
Layman is an "overlay" external repository management tool.
  
In order to use a graphical environment it's necessary to install X.Org, which is an implementation of the X Window system.  
+
=== Installation ===
 +
<console>###i## emerge layman</console>
 +
[[make.conf]] must source laymans overlays for emerge to pull in packages from external sources.  This line needs to be below everything else in make.conf.
 +
<console>###i## echo "source /var/lib/layman/make.conf" >> /etc/portage/make.conf</console>
  
Before we start it's a good idea to make sure that your system is configured correctly. If you've installed your kernel using the <code>binary</code> USE flag, chances are that your video card is already supported.
+
=== Using Layman ===
 +
Fetch, and display a list of overlays:
 +
<console>###i## layman -L</console>
  
You should also find your IP address, because if X freezes and you need to get out of it, the safest way is to SSH in from another computer/smartphone/tablet and issue
+
Add an overlay to your system:
<console>
+
<console>###i## layman -a <overlay name></console>
# ##i##killall X
+
</console>
+
  
In order for Portage to know which [[Video | video]] card(s) you want to support, you'll need to add a line to your <code>[[make.conf | make.conf]]</code>.
+
Delete an overlay from your system:
<console>
+
<console>###i## layman -d <overlay name></console>
# ##i##nano -w /etc/portage/make.conf
+
...
+
VIDEO_CARDS="intel"
+
</console>
+
  
In the example above we're using Intel integrated graphics drivers. Examples of valid entries include <code>radeon</code> for AMD Radeon cards, and <code>nouveau</code> or <code>nvidia</code> for NVIDIA cards. If you haven't yet switched to the <code>desktop</code> profile it's a good idea to do it now.
+
==== Masking Overlay Packages ====
 +
Overlays have the power to override distro packages. To avoid conflicts, mask everything in the overlay, and unmask the packages that are necessary to your system.
  
Next comes the actual installation:
+
{{file|name=/etc/portage/package.mask|lang=|desc=mask all packages in an overlay|body=
<console>
+
*/*::overlay-name
# ##i##emerge xorg-x11
+
}}
</console>
+
  
Now we need to test to make sure X.Org is working properly. To test it we will install twm, a simple window manager which has traditionally served as the standard window manager for X.Org. In Funtoo Linux it is included in the core X.Org meta-package <code>x11-apps/xinit</code>, but is not installed by default.
+
{{file|name=/etc/portage/package.unmask|lang=|desc=unmask packages to be used|body=
 +
cat-egory/pack-age1
 +
cat-egory/pack-age2
 +
}}
  
It is possible to install twm directly by merging <code>x11-wm/twm</code> but for the sake of this tutorial we will install the meta-package, which includes a few extra utilities which may come in handy. There are two ways to do this depending on whether you want it to be installed temporarily or permanently. If you just want it to test X.Org use the following command:
+
==== Sync ====
<console>
+
# ##i##USE="-minimal" emerge -1 xinit
+
</console>
+
  
The <code>minimal</code> USE flag is used in some ebuilds to install the bare minimum needed to get a working system. By passing <code>USE="-minimal"</code> to the command line before <code>emerge</code>, we are telling Portage to disable the flag and install the complete package. The <code>-1</code> (<code>--oneshot</code>) following <code>emerge</code> tells Portage not to add the package to [[#Updating your system|<code>world</code>]]. This is useful when installing packages which are automatically pulled in as dependencies by other packages.
+
Sync a specific overlays ebuilds:
 +
<console>###i## layman -s <overlay name></console>
  
If you want the package installed permanently you will need to add a line to <code>package.use</code>:  
+
Sync all overlays:
<console>
+
<console>###i## layman -S</console>
# ##i##echo 'x11-apps/xinit -minimal' >> /etc/portage/package.use
+
</console>
+
  
Next we reinstall <code>x11-apps/xinit</code>:
+
Sync all overlays via eix:
<console>
+
<console>###i## eix-sync</console>
# ##i##emerge -1N xinit
+
</console>
+
  
Once that's done, we're able to finally test X.Org:
+
=== Troubleshooting ===
 +
Problem:
 +
Warning: an installed db file was not found at: ['/var/lib/layman/cache***.xml']
  
<console>
+
Solution:
# ##i##startx
+
<console>###i## layman -L</console>
</console>
+
  
If everything is well, a simple GUI along with an analog clock and a terminal will appear.
+
{{EbuildFooter}}
 
+
====Keyboard/Mouse====
+
 
+
If you have no keyboard/mouse input in x11, check if your kernel supports dev
+
<console>
+
# ##i##zcat /proc/config.gz | grep EVDEV
+
</console>
+
if your output is:
+
<console>
+
CONFIG_INPUT_EVDEV=y
+
</console>
+
Install xf86-input-evdev
+
<console>
+
# ##i##emerge -avxf86-input-evdev
+
</console>
+
 
+
[[Category:First Steps]]
+

Revision as of 12:00, February 3, 2015

app-portage/layman


Source Repository:Repository:Gentoo Portage Tree

http://layman.sourceforge.net/

Summary: Tool to manage Gentoo overlays

Use Flags

bazaar
Support dev-vcs/bzr based overlays
cvs
Support dev-vcs/cvs based overlays
darcs
Support dev-vcs/darcs based overlays
g-sorcery
Support app-portage/g-sorcery based overlays
git
Support dev-vcs/git based overlays
gpg
Support app-crypt/gnupg signed overlays lists and manifests
mercurial
Support dev-vcs/mercurial based overlays
squashfs
Support mounting squashfs image overlays locally read-only
subversion
Support dev-vcs/subversion based overlays
sync-plugin-portage
Install the sys-apps/portage sync module

News

Drobbins

ARM Rebuild

ARM systems will use new stage3's that are not compatible with earlier versions.
2015-06-27 by Drobbins
Drobbins

ABI X86 64 and 32

Funtoo Linux has new 32-bit compatibility libraries inherited from Gentoo. Learn about them here.
2015-06-18 by Drobbins
Drobbins

Pre-built kernels!

Funtoo stage3's are now starting to offer pre-built kernels for ease of install. read more....
2015-05-12 by Drobbins
More...

Layman

Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

Layman is an "overlay" external repository management tool.

Installation

# emerge layman

make.conf must source laymans overlays for emerge to pull in packages from external sources. This line needs to be below everything else in make.conf.

# echo "source /var/lib/layman/make.conf" >> /etc/portage/make.conf

Using Layman

Fetch, and display a list of overlays:

# layman -L

Add an overlay to your system:

# layman -a <overlay name>

Delete an overlay from your system:

# layman -d <overlay name>

Masking Overlay Packages

Overlays have the power to override distro packages. To avoid conflicts, mask everything in the overlay, and unmask the packages that are necessary to your system.

/etc/portage/package.mask - mask all packages in an overlay
*/*::overlay-name
/etc/portage/package.unmask - unmask packages to be used
cat-egory/pack-age1
cat-egory/pack-age2

Sync

Sync a specific overlays ebuilds:

# layman -s <overlay name>

Sync all overlays:

# layman -S

Sync all overlays via eix:

# eix-sync

Troubleshooting

Problem: Warning: an installed db file was not found at: ['/var/lib/layman/cache***.xml']

Solution:

# layman -L