Difference between pages "Package:Boot-Update" and "Repository Configuration"

(Difference between pages)
m (Add reference to boot.conf.example)
 
(New repository layout)
 
Line 1: Line 1:
{{Ebuild
+
{{Warning|This article is a work-in-progress referring to a future Portage version. It does not apply to the current Funtoo Portage version. Please do not update your configuration yet.}}
|Summary=Funtoo Core Boot Framework for global boot loader configuration
+
|CatPkg=sys-boot/boot-update
+
|Maintainer=Drobbins
+
|Repository=Funtoo Overlay
+
|Organization=Funtoo Technologies
+
|Overlay=Funtoo
+
}}
+
Funtoo boot-update provides a unified mechanism for configuring the GRUB 1.9x ({{Package|sys-boot/grub}}) and GRUB 0.97 ({{Package|sys-boot/grub-legacy}}) boot loaders. It is the recommended, official way to configure Funtoo Linux systems for booting.
+
  
== Current Version ==
+
Starting with Portage-2.3.8, a switch to a new repository configuration framework is complete and users may want to update their configuration files. This document aims to describe the goals for the new framework and how to use it.
  
* {{Package|sys-boot/boot-update}}
+
== Multiple repository layout ==
 +
One of the most important changes is the switch from the old ''overlay'' layout to a new cleaner ''repository'' system. The new layout is more flexible and more predictable. For example, repositories can now use resources (eclasses, for example) provided by other repositories.
  
== Man Pages ==
+
The old layout was based on the concept of one ''main tree'' and optionally a number of overlays. The main tree provided base system ebuilds, eclasses, profiles, while overlays mostly were able to provide their own ebuilds. The ebuild provided by overlays overrode the ebuilds in main tree to the extend of making it impossible to install the main tree version. Overlays could also provide eclasses for their own ebuilds and package.* entries that applied to all overlays and to the main tree. The Package Manager is responsible for updating the main tree, while overlays are managed externally.
Consult the following man pages for detailed, up-to-date information on configuration file settings and command-line arguments:
+
  
* boot-update(8)
+
The new layout is based on the concept of one or more configurable repositories. Each repository can either be stand-alone or depend upon other repositories. The distribution provides a repository called ''funtoo'' (a drop-in replacement for Gentoo's ''gentoo'' repository). Users can install more repositories at they will, the repositories providing their own ebuilds, eclasses and profiles as necessary and/or using them from other repositories. Users can explicitly choose the repository they want to install packages from. The Package Manager can update all repositories.
* boot.conf(5)
+
  
== GRUB 1.97+ Quick Start ==
+
== Portage configuration ==
 +
=== New repository layout ===
 +
The repository configuration should be stored in <code>/etc/portage/repos.conf</code>. It can be either a single file or a directory containing one or more ''.conf'' files.
  
If using <code>sys-boot/grub-1.97</code> or later, perform the following steps:
+
The default configuration is installed as <code>/usr/share/portage/config/repos.conf</code>. This file is internal configuration file installed with portage ebuild and should '''not''' be modified. Instead, the configuration in <code>/etc/portage/repos.conf</code> can override the defaults specified there.
  
* Partition disk using GPT/GUID (recommended) or MBR partitions.
+
The configuration uses format similar to Windows .ini files. Each section heading (repository name in square brackets) signifies a single repository, followed by one or more key-value option pairs. For example, the following file copies default configuration for Funtoo repository:
* Install kernel/initrd to <code>/boot</code>
+
  
<console>
+
{{file|name=/etc/portage/repos.conf/funtoo.conf|desc=Example configuration override for Funtoo repository|body=
###i## emerge sys-boot/boot-update
+
[funtoo]
###i## grub-install --no-floppy /dev/sda
+
# moved to non-default location!
</console>
+
location = /var/db/repos/funtoo
Ensure that <code>/etc/fstab</code> is correct, and edit <tt>/etc/boot.conf</tt> to reflect your installation (see <code>/etc/boot.conf.example</code>). Then run:
+
sync-type = git
 
+
sync-uri = git://github.com/funtoo/ports-2015.git
<console>
+
auto-sync = yes
###i## boot-update
+
}}
</console>
+
Location variable is now what used to be a PORTDIR, when using old-fashioned <code>/etc/portage/make.conf</code>. <code>/var/db/repos/funtoo</code> is a dummy location example. Default location in Funtoo is  set to <code>/usr/portage</code>. Users are free to choose a location of their suits. sync-type is a CVS tree used for portage tree, git is a default in Funtoo. sync-uri is what used to be a SYNC variable, when using old-fashioned configuration through <code>/etc/portage/make.conf</code>
This will auto-generate the complex <tt>/boot/grub/grub.cfg</tt> required for booting. Re-run <tt>boot-update</tt> every time your available kernels/initrds or <tt>/etc/boot.conf</tt> configuration changes.
+
The most useful repository configuration options are listed below:
 
+
;location: ''Obligatory.'' Specifies the directory where repository is/will be stored. If Portage knows how to sync the repository and the location does not exist, it will be created on next ''emerge --sync''. Otherwise, the directory must exist.
= GRUB 0.97 (grub-legacy) Quick Start =
+
;priority: Specifies the priority used for ordering ebuilds from different repositories. If two repositories provide an ebuild with matching versions, the repository with higher priority will be used.
 
+
;auto-sync: Specifies whether ''emerge --sync'' should update the repository. Defaults to ''yes'' if ''sync-type'' is specified, ''no'' otherwise.
If using <code>sys-boot/grub-legacy-0.97</code>, perform the following steps:
+
;sync-depth: Specifies ''--depth'' for git clone. Used only on initial sync. Defaults to 1. Can be set to 0 to force full clone (not pass ''--depth'' at all).
 
+
;sync-type: Specifies syncing/update method. Can be one of: ''cvs'', ''git'', ''rsync'', ''svn''.
* Partition disk using MBR partitions '''(GPT not supported)'''
+
;sync-umask: Specifies the umask used when updating/syncing the repository.
* Install kernel/initrd to <code>/boot</code>
+
;sync-uri: Specifies remote URI from which the repository will be cloned/synced. Can use any syntax valid for a particular syncing method.
 
+
;sync-user: Specifies the user[:group] used to update/sync the repository. If ''FEATURES=usersync'' is used, defaults to the credentials of directory owner.
<console>
+
###i## emerge sys-boot/boot-update
+
###i## emerge ">=sys-boot/grub-legacy-0.97-r11"
+
###i## grub-install-legacy /dev/sda
+
</console>
+
Due to an issue with <code>grub-legacy</code>, you may see the following message:
+
<console>
+
###i## grub-install-legacy /dev/sda
+
The file /boot/grub-legacy/stage1 not read correctly.
+
</console>
+
Should you receive this message, you will have to install <code>grub-legacy</code> from the grub shell.
+
Assuming <code>/boot</code> is the partition <code>/dev/sda1</code> and you want to install grub to the MBR, you would run the following:
+
<console>
+
###i## grub-legacy
+
root (hd0,0)
+
setup (hd0)
+
quit
+
</console>
+
When adjusting to fit your setup, remember 'root' is the location of your boot partition, 'setup' is where you want to install grub, and don't forget about grub's unique naming conventions for hard drives / partitions. For more information run:
+
<console>
+
###i## info grub-legacy
+
</console>
+
 
+
Ensure that <tt>/etc/fstab</tt> is correct, and edit <tt>/etc/boot.conf</tt> to reflect your installation. Ensure a <tt>generate grub-legacy</tt> setting in the <tt>boot</tt> section. Then run:
+
 
+
<console>
+
###i## boot-update
+
</console>
+
This will auto-generate the <tt>/boot/grub-legacy/grub.conf</tt> required for booting. Note that <code>grub-legacy-0.97-r11</code> and later stores <tt>grub.conf</tt> in the <tt>/boot/grub-legacy</tt> directory.
+
 
+
Re-run <tt>boot-update</tt> every time your available kernels / initrds or <tt>/etc/boot.conf</tt> configuration changes.
+
  
[[Category:Projects]]
+
[[Category:Portage]]
[[Category:Funtoo features]]
+
{{EbuildFooter}}
+

Revision as of 13:52, February 14, 2015

Warning

This article is a work-in-progress referring to a future Portage version. It does not apply to the current Funtoo Portage version. Please do not update your configuration yet.

Starting with Portage-2.3.8, a switch to a new repository configuration framework is complete and users may want to update their configuration files. This document aims to describe the goals for the new framework and how to use it.

Multiple repository layout

One of the most important changes is the switch from the old overlay layout to a new cleaner repository system. The new layout is more flexible and more predictable. For example, repositories can now use resources (eclasses, for example) provided by other repositories.

The old layout was based on the concept of one main tree and optionally a number of overlays. The main tree provided base system ebuilds, eclasses, profiles, while overlays mostly were able to provide their own ebuilds. The ebuild provided by overlays overrode the ebuilds in main tree to the extend of making it impossible to install the main tree version. Overlays could also provide eclasses for their own ebuilds and package.* entries that applied to all overlays and to the main tree. The Package Manager is responsible for updating the main tree, while overlays are managed externally.

The new layout is based on the concept of one or more configurable repositories. Each repository can either be stand-alone or depend upon other repositories. The distribution provides a repository called funtoo (a drop-in replacement for Gentoo's gentoo repository). Users can install more repositories at they will, the repositories providing their own ebuilds, eclasses and profiles as necessary and/or using them from other repositories. Users can explicitly choose the repository they want to install packages from. The Package Manager can update all repositories.

Portage configuration

New repository layout

The repository configuration should be stored in /etc/portage/repos.conf. It can be either a single file or a directory containing one or more .conf files.

The default configuration is installed as /usr/share/portage/config/repos.conf. This file is internal configuration file installed with portage ebuild and should not be modified. Instead, the configuration in /etc/portage/repos.conf can override the defaults specified there.

The configuration uses format similar to Windows .ini files. Each section heading (repository name in square brackets) signifies a single repository, followed by one or more key-value option pairs. For example, the following file copies default configuration for Funtoo repository:

/etc/portage/repos.conf/funtoo.conf - Example configuration override for Funtoo repository
[funtoo]
# moved to non-default location!
location = /var/db/repos/funtoo
sync-type = git
sync-uri = git://github.com/funtoo/ports-2015.git
auto-sync = yes

Location variable is now what used to be a PORTDIR, when using old-fashioned /etc/portage/make.conf. /var/db/repos/funtoo is a dummy location example. Default location in Funtoo is set to /usr/portage. Users are free to choose a location of their suits. sync-type is a CVS tree used for portage tree, git is a default in Funtoo. sync-uri is what used to be a SYNC variable, when using old-fashioned configuration through /etc/portage/make.conf The most useful repository configuration options are listed below:

location
Obligatory. Specifies the directory where repository is/will be stored. If Portage knows how to sync the repository and the location does not exist, it will be created on next emerge --sync. Otherwise, the directory must exist.
priority
Specifies the priority used for ordering ebuilds from different repositories. If two repositories provide an ebuild with matching versions, the repository with higher priority will be used.
auto-sync
Specifies whether emerge --sync should update the repository. Defaults to yes if sync-type is specified, no otherwise.
sync-depth
Specifies --depth for git clone. Used only on initial sync. Defaults to 1. Can be set to 0 to force full clone (not pass --depth at all).
sync-type
Specifies syncing/update method. Can be one of: cvs, git, rsync, svn.
sync-umask
Specifies the umask used when updating/syncing the repository.
sync-uri
Specifies remote URI from which the repository will be cloned/synced. Can use any syntax valid for a particular syncing method.
sync-user
Specifies the user[:group] used to update/sync the repository. If FEATURES=usersync is used, defaults to the credentials of directory owner.