Cleanup and move to sablink naming
This commit is contained in:
Mario Fetka
parent
6698f03de5
commit
80472d628e
|
|
@ -1,107 +0,0 @@
|
|||
# generic installation stage specfile
|
||||
# used to build a stage1, stage2, or stage3 installation tarball
|
||||
|
||||
# The subarch can be any of the supported catalyst subarches (like athlon-xp).
|
||||
# Refer to the catalyst reference manual for suppurted subarches.
|
||||
# http://www.gentoo.org/proj/en/releng/catalyst/
|
||||
# example:
|
||||
# subarch: athlon-xp
|
||||
subarch: arm
|
||||
|
||||
# The version stamp is an identifier for the build. It can be anything you wish
|
||||
# it to be, but it is usually a date.
|
||||
# example:
|
||||
# version_stamp: 2006.1
|
||||
version_stamp: armv5tejl.0
|
||||
|
||||
# The target specifies what target we want catalyst to do. For stages, the
|
||||
# supported targets are: stage1 stage2 stage3
|
||||
# example:
|
||||
# target: stage2
|
||||
target: stage1
|
||||
|
||||
# The rel_type defines what kind of build we are doing. This is merely another
|
||||
# identifier, but it useful for allowing multiple concurrent builds. Usually,
|
||||
# default will suffice.
|
||||
# example:
|
||||
# rel_type: default
|
||||
rel_type: default
|
||||
|
||||
# This is the system profile to be used by catalyst to build this target. It is
|
||||
# specified as a relative path from /usr/portage/profiles.
|
||||
# example:
|
||||
# profile: default-linux/x86/2006.1
|
||||
profile: default-linux/arm/10.0/server
|
||||
|
||||
# This specifies which snapshot to use for building this target.
|
||||
# example:
|
||||
# snapshot: 2006.1
|
||||
snapshot: armv5tejl.0
|
||||
|
||||
# This specifies where the seed stage comes from for this target, The path is
|
||||
# relative to $clst_sharedir/builds. The rel_type is also used as a path prefix
|
||||
# for the seed.
|
||||
# example:
|
||||
# default/stage3-x86-2006.1
|
||||
source_subpath: default/stage3-arm-armv5tejl.0
|
||||
|
||||
# These are the hosts used as distcc slaves when distcc is enabled in your
|
||||
# catalyst.conf. It follows the same syntax as distcc-config --set-hosts and
|
||||
# is entirely optional.
|
||||
# example:
|
||||
# distcc_hosts: 127.0.0.1 192.168.0.1
|
||||
distcc_hosts:
|
||||
|
||||
# This is an optional directory containing portage configuration files. It
|
||||
# follows the same syntax as /etc/portage and should be consistent across all
|
||||
# targets to minimize problems.
|
||||
# example:
|
||||
# portage_confdir: /etc/portage
|
||||
portage_confdir: /home/mario/mars/linamh/trunk/genlink/Documentation/ls_pro_live/portage/
|
||||
|
||||
# This option specifies the location to a portage overlay that you would like to
|
||||
# have used when building this target.
|
||||
# example:
|
||||
# portage_overlay: /usr/local/portage
|
||||
portage_overlay: /home/mario/mars/linamh/trunk/genlink
|
||||
|
||||
# This allows the optional directory containing the output packages for
|
||||
# catalyst. Mainly used as a way for different spec files to access the same
|
||||
# cache directory. Default behavior is for this location to be autogenerated
|
||||
# by catalyst based on the spec file.
|
||||
# example:
|
||||
# pkgcache_path: /tmp/packages
|
||||
# pkgcache_path:
|
||||
|
||||
# These options are only available when building a stage1 or stage2 target and
|
||||
# are all optional. These allow for emulating the changes possible during ai
|
||||
# bootstrap. Some possible uses of these would be building embedded stages
|
||||
# requiring a different CHOST or building a stage2 with NPTL support from a
|
||||
# stage1 tarball that is built without it.
|
||||
# If left blank, then the catalyst defaults from arch.py are used.
|
||||
|
||||
# This option is used to change the CHOST from what is default in the profile
|
||||
# to whatever you specify. This is useful for building NPTL, for example.
|
||||
# example:
|
||||
# chost: i686-pc-linux-gnu
|
||||
chost: armv5tejl-softfloat-linux-gnueabi
|
||||
|
||||
# This option allows you to change the default CFLAGS that will be used in
|
||||
# building this stage. This really should remain generic, as putting
|
||||
# optimizations flags here will build a stage1 tarball that is no longer
|
||||
# generic.
|
||||
# example:
|
||||
# cflags: -Os -pipe -fomit-frame-pointer -mcpu=i686
|
||||
cflags: -march=armv5te -mtune=arm926ej-s -Os -fomit-frame-pointer -pipe
|
||||
|
||||
# This is for setting the CXXFLAGS. Generally, this would be set to the same
|
||||
# as CFLAGS. In fact, it will mirror CFLAGS by default.
|
||||
# example:
|
||||
# cxxflags: -Os -pipe -fomit-frame-pointer -mcpu=i686
|
||||
cxxflags: -march=armv5te -mtune=arm926ej-s -Os -fomit-frame-pointer -pipe
|
||||
|
||||
# Setting this option sets LDFLAGS in make.conf in your stage. This would be
|
||||
# useful for setting up an embedded or hardened system.
|
||||
# example:
|
||||
# ldflags: -Wl,-O1 -Wl,-z,now
|
||||
ldflags: -Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# generic installation stage specfile
|
||||
# used to build a stage1, stage2, or stage3 installation tarball
|
||||
|
||||
# The subarch can be any of the supported catalyst subarches (like athlon-xp).
|
||||
# Refer to the catalyst reference manual for suppurted subarches.
|
||||
# http://www.gentoo.org/proj/en/releng/catalyst/
|
||||
# example:
|
||||
# subarch: athlon-xp
|
||||
subarch: arm
|
||||
|
||||
# The version stamp is an identifier for the build. It can be anything you wish
|
||||
# it to be, but it is usually a date.
|
||||
# example:
|
||||
# version_stamp: 2006.1
|
||||
version_stamp: armv5tejl.0
|
||||
|
||||
# The target specifies what target we want catalyst to do. For stages, the
|
||||
# supported targets are: stage1 stage2 stage3
|
||||
# example:
|
||||
# target: stage2
|
||||
target: stage2
|
||||
|
||||
# The rel_type defines what kind of build we are doing. This is merely another
|
||||
# identifier, but it useful for allowing multiple concurrent builds. Usually,
|
||||
# default will suffice.
|
||||
# example:
|
||||
# rel_type: default
|
||||
rel_type: default
|
||||
|
||||
# This is the system profile to be used by catalyst to build this target. It is
|
||||
# specified as a relative path from /usr/portage/profiles.
|
||||
# example:
|
||||
# profile: default-linux/x86/2006.1
|
||||
profile: default-linux/arm/10.0/server
|
||||
|
||||
# This specifies which snapshot to use for building this target.
|
||||
# example:
|
||||
# snapshot: 2006.1
|
||||
snapshot: armv5tejl.0
|
||||
|
||||
# This specifies where the seed stage comes from for this target, The path is
|
||||
# relative to $clst_sharedir/builds. The rel_type is also used as a path prefix
|
||||
# for the seed.
|
||||
# example:
|
||||
# default/stage3-x86-2006.1
|
||||
source_subpath: default/stage1-arm-armv5tejl.0
|
||||
|
||||
# These are the hosts used as distcc slaves when distcc is enabled in your
|
||||
# catalyst.conf. It follows the same syntax as distcc-config --set-hosts and
|
||||
# is entirely optional.
|
||||
# example:
|
||||
# distcc_hosts: 127.0.0.1 192.168.0.1
|
||||
distcc_hosts:
|
||||
|
||||
# This is an optional directory containing portage configuration files. It
|
||||
# follows the same syntax as /etc/portage and should be consistent across all
|
||||
# targets to minimize problems.
|
||||
# example:
|
||||
# portage_confdir: /etc/portage
|
||||
portage_confdir: /home/mario/mars/linamh/trunk/genlink/Documentation/ls_pro_live/portage/
|
||||
|
||||
# This option specifies the location to a portage overlay that you would like to
|
||||
# have used when building this target.
|
||||
# example:
|
||||
# portage_overlay: /usr/local/portage
|
||||
portage_overlay: /home/mario/mars/linamh/trunk/genlink
|
||||
|
||||
# This allows the optional directory containing the output packages for
|
||||
# catalyst. Mainly used as a way for different spec files to access the same
|
||||
# cache directory. Default behavior is for this location to be autogenerated
|
||||
# by catalyst based on the spec file.
|
||||
# example:
|
||||
# pkgcache_path: /tmp/packages
|
||||
pkgcache_path:
|
||||
|
||||
# These options are only available when building a stage1 or stage2 target and
|
||||
# are all optional. These allow for emulating the changes possible during ai
|
||||
# bootstrap. Some possible uses of these would be building embedded stages
|
||||
# requiring a different CHOST or building a stage2 with NPTL support from a
|
||||
# stage1 tarball that is built without it.
|
||||
# If left blank, then the catalyst defaults from arch.py are used.
|
||||
|
||||
# This option is used to change the CHOST from what is default in the profile
|
||||
# to whatever you specify. This is useful for building NPTL, for example.
|
||||
# example:
|
||||
# chost: i686-pc-linux-gnu
|
||||
chost: armv5tejl-softfloat-linux-gnueabi
|
||||
|
||||
# This option allows you to change the default CFLAGS that will be used in
|
||||
# building this stage. This really should remain generic, as putting
|
||||
# optimizations flags here will build a stage1 tarball that is no longer
|
||||
# generic.
|
||||
# example:
|
||||
# cflags: -Os -pipe -fomit-frame-pointer -mcpu=i686
|
||||
cflags: -march=armv5te -mtune=arm926ej-s -Os -fomit-frame-pointer -pipe
|
||||
|
||||
# This is for setting the CXXFLAGS. Generally, this would be set to the same
|
||||
# as CFLAGS. In fact, it will mirror CFLAGS by default.
|
||||
# example:
|
||||
# cxxflags: -Os -pipe -fomit-frame-pointer -mcpu=i686
|
||||
cxxflags: -march=armv5te -mtune=arm926ej-s -Os -fomit-frame-pointer -pipe
|
||||
|
||||
# Setting this option sets LDFLAGS in make.conf in your stage. This would be
|
||||
# useful for setting up an embedded or hardened system.
|
||||
# example:
|
||||
# ldflags: -Wl,-O1 -Wl,-z,now
|
||||
ldflags: -Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed
|
||||
|
|
@ -1,107 +0,0 @@
|
|||
# generic installation stage specfile
|
||||
# used to build a stage1, stage2, or stage3 installation tarball
|
||||
|
||||
# The subarch can be any of the supported catalyst subarches (like athlon-xp).
|
||||
# Refer to the catalyst reference manual for suppurted subarches.
|
||||
# http://www.gentoo.org/proj/en/releng/catalyst/
|
||||
# example:
|
||||
# subarch: athlon-xp
|
||||
subarch: arm
|
||||
|
||||
# The version stamp is an identifier for the build. It can be anything you wish
|
||||
# it to be, but it is usually a date.
|
||||
# example:
|
||||
# version_stamp: 2006.1
|
||||
version_stamp: armv5tejl.0
|
||||
|
||||
# The target specifies what target we want catalyst to do. For stages, the
|
||||
# supported targets are: stage1 stage2 stage3
|
||||
# example:
|
||||
# target: stage2
|
||||
target: stage3
|
||||
|
||||
# The rel_type defines what kind of build we are doing. This is merely another
|
||||
# identifier, but it useful for allowing multiple concurrent builds. Usually,
|
||||
# default will suffice.
|
||||
# example:
|
||||
# rel_type: default
|
||||
rel_type: default
|
||||
|
||||
# This is the system profile to be used by catalyst to build this target. It is
|
||||
# specified as a relative path from /usr/portage/profiles.
|
||||
# example:
|
||||
# profile: default-linux/x86/2006.1
|
||||
profile: default-linux/arm/10.0/server
|
||||
|
||||
# This specifies which snapshot to use for building this target.
|
||||
# example:
|
||||
# snapshot: 2006.1
|
||||
snapshot: armv5tejl.0
|
||||
|
||||
# This specifies where the seed stage comes from for this target, The path is
|
||||
# relative to $clst_sharedir/builds. The rel_type is also used as a path prefix
|
||||
# for the seed.
|
||||
# example:
|
||||
# default/stage3-x86-2006.1
|
||||
source_subpath: default/stage2-arm-armv5tejl.0
|
||||
|
||||
# These are the hosts used as distcc slaves when distcc is enabled in your
|
||||
# catalyst.conf. It follows the same syntax as distcc-config --set-hosts and
|
||||
# is entirely optional.
|
||||
# example:
|
||||
# distcc_hosts: 127.0.0.1 192.168.0.1
|
||||
distcc_hosts:
|
||||
|
||||
# This is an optional directory containing portage configuration files. It
|
||||
# follows the same syntax as /etc/portage and should be consistent across all
|
||||
# targets to minimize problems.
|
||||
# example:
|
||||
# portage_confdir: /etc/portage
|
||||
portage_confdir: /home/mario/mars/linamh/trunk/genlink/Documentation/ls_pro_live/portage/
|
||||
|
||||
# This option specifies the location to a portage overlay that you would like to
|
||||
# have used when building this target.
|
||||
# example:
|
||||
# portage_overlay: /usr/local/portage
|
||||
portage_overlay: /home/mario/mars/linamh/trunk/genlink
|
||||
|
||||
# This allows the optional directory containing the output packages for
|
||||
# catalyst. Mainly used as a way for different spec files to access the same
|
||||
# cache directory. Default behavior is for this location to be autogenerated
|
||||
# by catalyst based on the spec file.
|
||||
# example:
|
||||
# pkgcache_path: /tmp/packages
|
||||
pkgcache_path:
|
||||
|
||||
# These options are only available when building a stage1 or stage2 target and
|
||||
# are all optional. These allow for emulating the changes possible during ai
|
||||
# bootstrap. Some possible uses of these would be building embedded stages
|
||||
# requiring a different CHOST or building a stage2 with NPTL support from a
|
||||
# stage1 tarball that is built without it.
|
||||
# If left blank, then the catalyst defaults from arch.py are used.
|
||||
|
||||
# This option is used to change the CHOST from what is default in the profile
|
||||
# to whatever you specify. This is useful for building NPTL, for example.
|
||||
# example:
|
||||
# chost: i686-pc-linux-gnu
|
||||
# chost:
|
||||
|
||||
# This option allows you to change the default CFLAGS that will be used in
|
||||
# building this stage. This really should remain generic, as putting
|
||||
# optimizations flags here will build a stage1 tarball that is no longer
|
||||
# generic.
|
||||
# example:
|
||||
# cflags: -Os -pipe -fomit-frame-pointer -mcpu=i686
|
||||
cflags: -march=armv5te -mtune=arm926ej-s -Os -fomit-frame-pointer -pipe
|
||||
|
||||
# This is for setting the CXXFLAGS. Generally, this would be set to the same
|
||||
# as CFLAGS. In fact, it will mirror CFLAGS by default.
|
||||
# example:
|
||||
# cxxflags: -Os -pipe -fomit-frame-pointer -mcpu=i686
|
||||
cxxflags: -march=armv5te -mtune=arm926ej-s -Os -fomit-frame-pointer -pipe
|
||||
|
||||
# Setting this option sets LDFLAGS in make.conf in your stage. This would be
|
||||
# useful for setting up an embedded or hardened system.
|
||||
# example:
|
||||
# ldflags: -Wl,-O1 -Wl,-z,now
|
||||
ldflags: -Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed
|
||||
|
|
@ -1,258 +0,0 @@
|
|||
# stage4 example specfile
|
||||
# used to build a stage4
|
||||
|
||||
# The subarch can be any of the supported catalyst subarches (like athlon-xp).
|
||||
# Refer to the catalyst reference manual for suppurted subarches.
|
||||
# http://www.gentoo.org/proj/en/releng/catalyst/
|
||||
# example:
|
||||
# subarch: athlon-xp
|
||||
subarch: arm
|
||||
|
||||
# The version stamp is an identifier for the build. It can be anything you wish# it to be, but it is usually a date.
|
||||
# example:
|
||||
# version_stamp: 2006.1
|
||||
version_stamp: armv5tejl-buffalo_ls_pro_live.0
|
||||
|
||||
# The target specifies what target we want catalyst to do. For building a CD,
|
||||
# we start with stage4 as our target.
|
||||
# example:
|
||||
# target: stage4
|
||||
target: stage4
|
||||
|
||||
# The rel_type defines what kind of build we are doing. This is merely another
|
||||
# identifier, but it useful for allowing multiple concurrent builds. Usually,
|
||||
# default will suffice.
|
||||
# example:
|
||||
# rel_type: default
|
||||
rel_type: default
|
||||
|
||||
# This is the system profile to be used by catalyst to build this target. It is# specified as a relative path from /usr/portage/profiles.
|
||||
# example:
|
||||
# profile: default-linux/x86/2006.1
|
||||
profile: default-linux/arm/10.0/server
|
||||
|
||||
# This specifies which snapshot to use for building this target.
|
||||
# example:
|
||||
# snapshot: 2006.1
|
||||
snapshot: armv5tejl.0
|
||||
|
||||
# This specifies where the seed stage comes from for this target, The path is
|
||||
# relative to $clst_sharedir/builds. The rel_type is also used as a path prefix# for the seed.
|
||||
# example:
|
||||
# default/stage3-x86-2006.1
|
||||
source_subpath: default/stage3-arm-armv5tejl.0
|
||||
|
||||
# These are the hosts used as distcc slaves when distcc is enabled in your
|
||||
# catalyst.conf. It follows the same syntax as distcc-config --set-hosts and
|
||||
# is entirely optional.
|
||||
# example:
|
||||
# distcc_hosts: 127.0.0.1 192.168.0.1
|
||||
distcc_hosts:
|
||||
|
||||
# This is an optional directory containing portage configuration files. It
|
||||
# follows the same syntax as /etc/portage and should be consistent across all
|
||||
# targets to minimize problems.
|
||||
# example:
|
||||
# portage_confdir: /etc/portage
|
||||
portage_confdir: /home/mario/mars/linamh/trunk/genlink/Documentation/ls_pro_live/portage/
|
||||
|
||||
# This option specifies the location to a portage overlay that you would like to
|
||||
# have used when building this target.
|
||||
# example:
|
||||
# portage_overlay: /usr/local/portage
|
||||
portage_overlay: /home/mario/mars/linamh/trunk/genlink
|
||||
|
||||
# This allows the optional directory containing the output packages for
|
||||
# catalyst. Mainly used as a way for different spec files to access the same
|
||||
# cache directory. Default behavior is for this location to be autogenerated
|
||||
# by catalyst based on the spec file.
|
||||
# example:
|
||||
# pkgcache_path: /tmp/packages
|
||||
pkgcache_path:
|
||||
|
||||
# This allows the optional directory containing the output packages for kernel
|
||||
# builds. Mainly used as a way for different spec files to access the same
|
||||
# cache directory. Default behavior is for this location to be autogenerated
|
||||
# by catalyst based on the spec file.
|
||||
# example:
|
||||
# kerncache_path: /tmp/kernel
|
||||
kerncache_path:
|
||||
|
||||
# The stage4 target is where you will build packages for basically updated
|
||||
# stage3. These packages can be built with customized USE settings. The
|
||||
# settings here are additive to the default USE configured by the profile.
|
||||
# Leaving this blank will default to the system use flags
|
||||
# example:
|
||||
# stage4/use: ipv6 socks5 fbcon ncurses readline ssl
|
||||
stage4/use:
|
||||
|
||||
# This is the set of packages that we will merge into the stage4 tarball. They
|
||||
# will be built with the USE flags configured above. These packages must not
|
||||
# depend on a configured kernel. If the package requires a configured kernel,
|
||||
# then it will be defined elsewhere.
|
||||
# example:
|
||||
# stage4/packages: livecd-tools dhcpcd acpid apmd gentoo-sources coldplug fxload irssi gpm syslog-ng parted links raidtools dosfstools nfs-utils jfsutils xfsprogs e2fsprogs reiserfsprogs ntfsprogs pwgen rp-pppoe screen mirrorselect penggy iputils hwdata-knoppix hwsetup lvm2 evms vim pptpclient mdadm ethtool wireless-tools prism54-firmware wpa_supplicant
|
||||
stage4/packages: layman openssh dhcpcd udev micro_evtd vixie-cron logrotate update-motd linux-buffalo_ls_pro_live buffalo_ls_pro_live-sources gpm syslog-ng gdisk parted atop links dosfstools nfs-utils jfsutils xfsprogs e2fsprogs reiserfsprogs reiser4progs pwgen screen mirrorselect iputils lvm2 vim mdadm ethtool ntp smartmontools hddtemp
|
||||
|
||||
# A fsscript is simply a shell script that is copied into the chroot of the stage4
|
||||
# after the kernel(s) and any external modules have been compiled and is
|
||||
# executed within the chroot. It can contain any commands that are available
|
||||
# via the packages installed by our stages or by the packages installed during
|
||||
# the stage4-stage1 build. We do not use one for the official release media, so
|
||||
# there will not be one listed below. The syntax is simply the full path and
|
||||
# filename to the shell script that you wish to execute. The script is copied
|
||||
# into the chroot by catalyst automatically.
|
||||
# example:
|
||||
# stage4/fsscript:
|
||||
stage4/fsscript: /home/mario/mars/linamh/trunk/genlink/Documentation/ls_pro_live/fsscript
|
||||
|
||||
# This is where you set the splash theme. This theme must be present in
|
||||
# /etc/splash, before the kernel has completed building.
|
||||
# example:
|
||||
# stage4/splash_theme: livecd-2006.1
|
||||
stage4/splash_theme:
|
||||
|
||||
# This is a set of arguments that will be passed to genkernel for all kernels
|
||||
# defined in this target. It is useful for passing arguments to genkernel that
|
||||
# are not otherwise available via the stage4-stage2 spec file.
|
||||
# example:
|
||||
# stage4/gk_mainargs: --lvm --dmraid
|
||||
stage4/gk_mainargs:
|
||||
|
||||
# This option allows you to specify your own linuxrc script for genkernel to use# when building your CD. This is not checked for functionality, so it is up to
|
||||
# you to debug your own script. We do not use one for the official release
|
||||
# media, so there will not be one listed below.
|
||||
# example:
|
||||
# stage4/linuxrc:
|
||||
stage4/linuxrc:
|
||||
|
||||
# This is for the message of the day. It is not required
|
||||
# release media, as catalyst builds a default motd when the stage4/type is set
|
||||
# to one of the gentoo-* options. This setting overrides the default motd even
|
||||
# on official media. Since we do not use this for the official releases, it is
|
||||
# left blank below.
|
||||
# example:
|
||||
# stage4/motd:
|
||||
stage4/motd:
|
||||
|
||||
# This is for blacklisting modules from being hotplugged that are known to cause
|
||||
# problems. Putting a module name here will keep it from being auto-loaded,
|
||||
# even if ti is detected by hotplug.
|
||||
# example:
|
||||
# stage4/modblacklist: 8139cp
|
||||
stage4/modblacklist:
|
||||
|
||||
# This is for adding init scripts to runlevels. The syntax for the init script
|
||||
# is the script name, followed by a pipe, followed by the runlevel in which you
|
||||
# want the script to run. It looks like spind|default and is space delimited.
|
||||
# We do not use this on the official media, as catalyst sets up the runlevels
|
||||
# correctly for us. Since we do not use this, it is left blank below.
|
||||
# example:
|
||||
# stage4/rcadd:
|
||||
stage4/rcadd: udev|sysinit micro_evtd-boot|boot hwclock|boot root|boot procfs|boot mtab|boot fsck|boot swap|boot vixie-cron|default micro_evtd|default syslog-ng|default net.eth0|default dbus|default linux-logo|default ntpd|default ntp-client|default smartd|default hddtemp|default sshd|default
|
||||
|
||||
# This is for removing init script from runlevels. It is executed after the
|
||||
# defaults shipped with catalyst, so it is possible to remove the defaults using
|
||||
# this option. It can follow the same syntax as livcd/rcadd, or you can leave
|
||||
# the runlevel off to remove the script from any runlevels detected. We do not
|
||||
# use this on the official media, so it is left blank.
|
||||
# example:
|
||||
# stage4/rcdel:
|
||||
stage4/rcdel:
|
||||
|
||||
# This overlay is dropped onto the filesystem within the loop. This can be used
|
||||
# for such things as updating configuration files or adding anything else you
|
||||
# would want within your stage4 filesystem. Files added here are available when
|
||||
# docache is used. We do not use this on the official media, so we will leave
|
||||
# it blank below.
|
||||
# example:
|
||||
# stage4/root_overlay:
|
||||
stage4/root_overlay: /home/mario/mars/linamh/trunk/genlink/Documentation/ls_pro_live/root_overlay
|
||||
|
||||
# This is used by catalyst to copy the specified file to /etc/X11/xinit/xinitrc
|
||||
# and is used by the stage4/type gentoo-gamecd and generic-livecd. While the
|
||||
# file will still be copied for any stage4/type, catalyst will only create the
|
||||
# necessary /etc/startx for those types, so X will not be automatically started.
|
||||
# This is useful also for setting up X on a CD where you do not wish X to start
|
||||
# automatically. We do not use this on the release media, so it is left blank.
|
||||
# example:
|
||||
# stage4/xinitrc:
|
||||
stage4/xinitrc:
|
||||
|
||||
# This option is used to create non-root users on your CD. It takes a space
|
||||
# separated list of user names. These users will be added to the following
|
||||
# groups: users,wheel,audio,games,cdrom,usb
|
||||
# If this is specified in your spec file, then the first user is also the user
|
||||
# used to start X. Since this is not used on the release media, it is blank.
|
||||
# example:
|
||||
# stage4/users:
|
||||
stage4/users:
|
||||
|
||||
# This option is used to specify the number of kernels to build and also the
|
||||
# labels that will be used by the CD bootloader to refer to each kernel image.
|
||||
# example:
|
||||
# boot/kernel: gentoo
|
||||
boot/kernel:
|
||||
|
||||
# This option tells catalyst which kernel sources to merge for this kernel
|
||||
# label. This can use normal portage atoms to specify a specific version.
|
||||
# example:
|
||||
# boot/kernel/gentoo/sources: gentoo-sources
|
||||
boot/kernel/gentoo/sources:
|
||||
|
||||
# This option is the full path and filename to a kernel .config file that is
|
||||
# used by genkernel to compile the kernel this label applies to.
|
||||
# example:
|
||||
# boot/kernel/gentoo/config: /tmp/2.6.11-smp.config
|
||||
boot/kernel/gentoo/config:
|
||||
|
||||
# This option sets genkernel parameters on a per-kernel basis and applies only
|
||||
# to this kernel label. This can be used for building options into only a
|
||||
# single kernel, where compatibility may be an issue. Since we do not use this
|
||||
# on the official release media, it is left blank, but it follows the same
|
||||
# syntax as stage4/gk_mainargs.
|
||||
# example:
|
||||
# boot/kernel/gentoo/gk_kernargs:
|
||||
boot/kernel/gentoo/gk_kernargs:
|
||||
|
||||
# This option sets the USE flags used to build the kernel and also any packages
|
||||
# which are defined under this kernel label. These USE flags are additive from
|
||||
# the default USE for the specified profile.
|
||||
# example:
|
||||
# boot/kernel/gentoo/use: pcmcia usb -X
|
||||
boot/kernel/gentoo/use:
|
||||
|
||||
# This option appends an extension to the name of your kernel, as viewed by a
|
||||
# uname -r/ This also affects any modules built under this kernel label. This
|
||||
# is useful for having two kernels using the same sources to keep the modules
|
||||
# from overwriting each other. We do not use this on the official media, so it
|
||||
# is left blank.
|
||||
# example:
|
||||
# boot/kernel/gentoo/extraversion:
|
||||
boot/kernel/gentoo/extraversion:
|
||||
|
||||
# This option is for merging kernel-dependent packages and external modules that
|
||||
# are configured against this kernel label.
|
||||
# example:
|
||||
# boot/kernel/gentoo/packages: pcmcia-cs speedtouch slmodem globespan-adsl hostap-driver hostap-utils ipw2100 ipw2200 fritzcapi fcdsl cryptsetup
|
||||
boot/kernel/gentoo/packages:
|
||||
|
||||
# This is a list of packages that will be unmerged after all the kernels have
|
||||
# been built. There are no checks on these packages, so be careful what you
|
||||
# add here. They can potentially break your CD.
|
||||
# example:
|
||||
# stage4/unmerge: acl attr autoconf automake bin86 binutils libtool m4 bison ld.so make perl patch linux-headers man-pages sash bison flex gettext texinfo ccache distcc addpatches man groff lib-compat miscfiles rsync sysklogd bc lcms libmng genkernel diffutils libperl gnuconfig gcc-config gcc bin86 cpio cronbase ed expat grub lilo help2man libtool gentoo-sources
|
||||
stage4/unmerge:
|
||||
|
||||
# This option is used to empty the directories listed. It is useful for getting
|
||||
# rid of files that don't belong to a particular package, or removing files from
|
||||
# a package that you wish to keep, but won't need the full functionality.
|
||||
# example:
|
||||
# stage4/empty: /var/tmp /var/cache /var/db /var/empty /var/lock /var/log /var/run /var/spool /var/state /tmp /usr/portage /usr/share/man /usr/share/info /usr/share/unimaps /usr/include /usr/share/zoneinfo /usr/share/dict /usr/share/doc /usr/share/ss /usr/share/state /usr/share/texinfo /usr/lib/python2.2 /usr/lib/portage /usr/share/gettext /usr/share/i18n /usr/share/rfc /usr/lib/X11/config /usr/lib/X11/etc /usr/lib/X11/doc /usr/src /usr/share/doc /usr/share/man /root/.ccache /etc/cron.daily /etc/cron.hourly /etc/cron.monthly /etc/cron.weekly /etc/logrotate.d /etc/rsync /usr/lib/awk /usr/lib/ccache /usr/lib/gcc-config /usr/lib/nfs /usr/local /usr/diet/include /usr/diet/man /usr/share/consolefonts/partialfonts /usr/share/consoletrans /usr/share/emacs /usr/share/gcc-data /usr/share/genkernel /etc/splash/gentoo /etc/splash/emergence /usr/share/gnuconfig /usr/share/lcms /usr/share/locale /etc/skel
|
||||
stage4/empty: /var/tmp/portage /var/tmp/ccache /var/tmp/binpkg /tmp
|
||||
|
||||
# This option tells catalyst to clean specific files from the filesystem and is
|
||||
# very usefu in cleaning up stray files in /etc left over after stage4/unmerge.
|
||||
# example:
|
||||
# stage4/rm: /lib/*.a /usr/lib/*.a /usr/lib/gcc-lib/*/*/libgcj* /etc/dispatch-conf.conf /etc/etc-update.conf /etc/*- /etc/issue* /etc/make.conf /etc/man.conf /etc/*.old /root/.viminfo /usr/sbin/fb* /usr/sbin/fsck.cramfs /usr/sbin/fsck.minix /usr/sbin/mkfs.minix /usr/sbin/mkfs.bfs /usr/sbin/mkfs.cramfs /lib/security/pam_access.so /lib/security/pam_chroot.so /lib/security/pam_debug.so /lib/security/pam_ftp.so /lib/security/pam_issue.so /lib/security/pam_mail.so /lib/security/pam_motd.so /lib/security/pam_mkhomedir.so /lib/security/pam_postgresok.so /lib/security/pam_rhosts_auth.so /lib/security/pam_userdb.so /usr/share/consolefonts/1* /usr/share/consolefonts/7* /usr/share/consolefonts/8* /usr/share/consolefonts/9* /usr/share/consolefonts/A* /usr/share/consolefonts/C* /usr/share/consolefonts/E* /usr/share/consolefonts/G* /usr/share/consolefonts/L* /usr/share/consolefonts/M* /usr/share/consolefonts/R* /usr/share/consolefonts/a* /usr/share/consolefonts/c* /usr/share/consolefonts/dr* /usr/share/consolefonts/g* /usr/share/consolefonts/i* /usr/share/consolefonts/k* /usr/share/consolefonts/l* /usr/share/consolefonts/r* /usr/share/consolefonts/s* /usr/share/consolefonts/t* /usr/share/consolefonts/v* /etc/splash/livecd-2006.1/16* /etc/splash/livecd-2006.1/12* /etc/splash/livecd-2006.1/6* /etc/splash/livecd-2006.1/8* /etc/splash/livecd-2006.1/images/silent-16* /etc/splash/livecd-2006.1/images/silent-12* /etc/splash/livecd-2006.1/images/silent-6* /etc/splash/livecd-2006.1/images/silent-8* /etc/splash/livecd-2006.1/images/verbose-16* /etc/splash/livecd-2006.1/images/verbose-12* /etc/splash/livecd-2006.1/images/verbose-6* /etc/splash/livecd-2006.1/images/verbose-8* /etc/make.conf.example /etc/make.globals /etc/resolv.conf
|
||||
stage4/rm: /usr/bin/qemu-arm /root/move_portage
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
#!/bin/sh
|
||||
|
||||
# link the kernel and initrd for the inital package
|
||||
cd /boot
|
||||
ln -sf uImage-*.buffalo uImage.buffalo
|
||||
ln -sf initrd-*.buffalo initrd.buffalo
|
||||
# no search for .svn dir
|
||||
# subversiontrees are used for /etc/portage & /var/lib/layman/go-genlink
|
||||
# so remove manually
|
||||
rm -rf /.svn
|
||||
rm -rf /etc/.svn
|
||||
rm -rf /etc/conf.d/.svn
|
||||
rm -rf /etc/init.d/.svn
|
||||
rm -rf /etc/layman/.svn
|
||||
rm -rf /etc/profile.d/.svn
|
||||
rm -rf /var/.svn
|
||||
rm -rf /var/lib/.svn
|
||||
rm -rf /var/lib/layman/.svn
|
||||
|
||||
# qemu-arm don't work with newer coreutils
|
||||
# but the linkstation works with it
|
||||
rm -f /etc/portage/package.mask/coreutils
|
||||
|
||||
# init bash profile for root
|
||||
cp -Rv /etc/skel/.bash* /root/
|
||||
|
||||
# create the new portage dir
|
||||
mkdir /usr/portage.new
|
||||
|
||||
# shrink the image by only syncing the requred dirs into /usr/portage
|
||||
# the only dirs that survive are profiles (required), eclass (required), licenses (required)
|
||||
# we have to use the IP as the resolve.conf file is already gone
|
||||
# but a new one will be added in a later phase of catylast
|
||||
rsync -aPv rsync://83.164.133.198/gentoo-portage/profiles /usr/portage.new/
|
||||
rsync -aPv rsync://83.164.133.198/gentoo-portage/eclass /usr/portage.new/
|
||||
rsync -aPv rsync://83.164.133.198/gentoo-portage/licenses /usr/portage.new/
|
||||
|
||||
# change password for root user
|
||||
echo "root:goLsProLive" | chpasswd
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/BerkeleyDB x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Cache-Cache x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Convert-BinHex x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Convert-TNEF x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Crypt-DES x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Digest-Nilsimsa x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/File-Tail x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/HTML-Template x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/IO-Multiplex x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/IPC-ShareLite x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Log-Log4perl x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/MIME-tools x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Mail-DKIM x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Mail-SPF x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/MailTools x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Net-CIDR x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Net-DNS-Resolver-Programmable x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Net-Netmask x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/NetAddr-IP x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Unix-Syslog x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
sys-process/acct x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
mail-filter/amavisd-new x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/ant-core x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/ant-nodeps x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
app-arch/arc x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
sys-process/atop x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
sys-process/audit x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/bcel x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
app-text/catdoc x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
app-antivirus/clamav x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/commons-cli x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/commons-logging x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
mail-filter/dcc x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
mail-filter/dkim-milter x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
www-apps/dokuwiki x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/dom4j x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
app-arch/freeze x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-vcs/gitosis-gentoo x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-util/google-perftools x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
virtual/gsasl x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/icedtea x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/icu4j x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
net-firewall/ipset x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/iso-relax x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/javacup x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/javatoolkit x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
java-virtuals/jaxb-api x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/jaxen x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/jdom x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/jdom-jaxen x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
sys-process/latencytop x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-dotnet/libgdiplus x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
net-libs/libgsasl x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
mail-filter/libmilter x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-cpp/libpqpp x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
app-misc/linux-logo x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
sys-apps/lsb-release x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
sys-fs/mdadm x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
www-apps/mediawiki x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
www-apache/mod_mono x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
www-apache/mod_python x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-lang/mono x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/msv x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
net-analyzer/munin x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-dotnet/nant x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/Net-SNMP x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/net-server x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
sys-fs/ntfsprogs x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
net-dns/pdns x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-dotnet/pe-format x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-php5/pecl-apc x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
virtual/perl-File-Temp x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-perl/perl-mozldap x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
virtual/perl-net-ping x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
net-nds/phpldapadmin x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-db/phpmyadmin x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-db/phppgadmin x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
www-apps/phpsysinfo x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
mail-filter/postgrey x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-python/psycopg x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-python/pyzor x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
mail-filter/razor x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-util/re2c x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/relaxng-datatype x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/rhino x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-java/saxpath x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
net-firewall/shorewall x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
sys-apps/smartmontools x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
mail-filter/spamassassin x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-python/sqlalchemy x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
net-proxy/squidguard x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
java-virtuals/stax-api x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
dev-util/systemtap x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
app-admin/webalizer x86 ~x86
|
||||
|
|
@ -1 +0,0 @@
|
|||
app-admin/webalizer-xtended x86 ~x86
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue