Difference between pages "Install/Network" and "Package:Layman"

< Install(Difference between pages)
(Created page with "<noinclude> {{Note|This is a template that is used as part of the Installation instructions, to describe the process of configuring the network. Templates are being used to al...")
 
m
 
Line 1: Line 1:
<noinclude>
+
{{Ebuild
{{Note|This is a template that is used as part of the Installation instructions, to describe the process of configuring the network. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.}}
+
|Summary=Tool to manage Gentoo overlays
</noinclude>
+
|CatPkg=app-portage/layman
=== Configuring your network ===
+
|Homepage=http://layman.sourceforge.net/
 +
}}
 +
Layman is an "overlay" external repository management tool.
  
It's important to ensure that you will be able to connect to your local-area network after you reboot into Funtoo Linux. There are three approaches you can use for configuring your network: NetworkManager, dhcpcd, and the [[Funtoo Linux Networking]] scripts. Here's how to choose which one to use based on the type of network you want to set up.
+
=== 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>
  
==== Wi-Fi ====
+
=== Using Layman ===
===== Using NetworkManager =====
+
Fetch, and display a list of overlays:
For laptop/mobile systems where you will be using Wi-Fi and connecting to various networks, NetworkManager is strongly recommended. The Funtoo version of NetworkManager is fully functional even from the command-line, so you can use it even without X or without the Network Manager applet. Here are the steps involved in setting up NetworkManager:
+
<console>###i## layman -L</console>
  
<console>
+
Add an overlay to your system:
(chroot) # ##i##emerge linux-firmware
+
<console>###i## layman -a <overlay name></console>
(chroot) # ##i##emerge networkmanager
+
(chroot) # ##i##rc-update add NetworkManager default
+
</console>
+
  
Above, we installed linux-firmware which contains a complete collection of available firmware for many hardware devices including Wi-Fi adapters, plus NetworkManager to manage our network connection. Then we added NetworkManager to the <code>default</code> runlevel so it will start when Funtoo Linux boots.
+
Delete an overlay from your system:
 +
<console>###i## layman -d <overlay name></console>
  
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:
+
==== 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.
  
<console>
+
{{file|name=/etc/portage/package.mask|lang=|desc=mask all packages in an overlay|body=
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork
+
*/*::overlay-name
</console>
+
}}
  
The <code>addwifi</code> command is used to configure and connect to a WPA/WPA2 Wi-Fi network named <code>mywifinetwork</code> with the password <code>wifipassword</code>. This network configuration entry is stored in <code>/etc/NetworkManager/system-connections</code> so that it will be remembered in the future. You should only need to enter this command once for each Wi-Fi network you connect to.
+
{{file|name=/etc/portage/package.unmask|lang=|desc=unmask packages to be used|body=
 +
cat-egory/pack-age1
 +
cat-egory/pack-age2
 +
}}
  
===== Using wpa_supplicant =====
+
==== Sync ====
If for some reason you don't want to use a tool such as NetworkManager or <code>wicd</code>, you can use wpa_supplicant for wireless network connections.
+
  
First, emerge wpa_supplicant:
+
Sync a specific overlays ebuilds:
 +
<console>###i## layman -s <overlay name></console>
  
<console>
+
Sync all overlays:
(chroot) ###i## emerge -a wpa_supplicant
+
<console>###i## layman -S</console>
</console>
+
  
Now, edit the wpa_supplicant configuration file, located at /etc/wpa_supplicant.conf.
+
Sync all overlays via eix:
The syntax is very easy:
+
<console>###i## eix-sync</console>
<pre>
+
network={
+
ssid="MyWifiName"
+
psk="lol42-wifi"
+
}
+
  
network={
+
=== Troubleshooting ===
ssid="Other Network"
+
Problem:
psk="6d96270004515a0486bb7f76196a72b40c55a47f"
+
Warning: an installed db file was not found at: ['/var/lib/layman/cache***.xml']
}
+
</pre>
+
  
You will need to add both <code>wpa_supplicant</code> and <code>dhcpcd</code> to the default runlevel. <code>wpa_supplicant</code> will connect to your access point, and <code>dhcpcd</code> will acquire an IP address via DHCP:
+
Solution:
 +
<console>###i## layman -L</console>
  
<console>
+
{{EbuildFooter}}
(chroot) # ##i##rc-update add dhcpcd default
+
(chroot) # ##i##rc-update add wpa_supplicant default
+
</console>
+
 
+
==== Desktop (Wired Ethernet) ====
+
 
+
For a home desktop or workstation with wired Ethernet that will use DHCP, the simplest and most effective option to enable network connectivity is to simply add <code>dhcpcd</code> to the default runlevel:
+
 
+
<console>
+
(chroot) # ##i##rc-update add dhcpcd default
+
</console>
+
 
+
When you reboot, <code>dhcpcd</code> will run in the background and manage all network interfaces and use DHCP to acquire network addresses from a DHCP server.
+
 
+
==== Server (Static IP) ====
+
 
+
For servers, the [[Funtoo Linux Networking]] scripts are recommended. They are optimized for static configurations and things like virtual ethernet bridging for virtualization setups. See [[Funtoo Linux Networking]] for information on how to use Funtoo Linux's template-based network configuration system.
+

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