Addition of this stripped down spec for nfsroot, based on the gentoo minimal install-cd

1 files changed, 529 insertions, 0 deletions

diff --git a/catalyst/nfsroot/2008.0/specs/amd64/nfsroot_stage4-slim.spec b/catalyst/nfsroot/2008.0/specs/amd64/nfsroot_stage4-slim.spec
new file mode 100644
index 0000000..740cabb
--- /dev/null
+++ b/catalyst/nfsroot/2008.0/specs/amd64/nfsroot_stage4-slim.spec
@@ -0,0 +1,529 @@
+# 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: amd64
+
+# 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: nfsroot-20080629
+version_stamp: nfsroot-20080816
+
+# 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/amd64/2008.0/
+
+# This specifies which snapshot to use for building this target.
+# example:
+snapshot: 20080816
+
+# 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-amd64-2008.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: /var/git/clustering-livecd/profiles/hpc-clustering/ 
+
+# 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: /var/git/clustering-livecd/overlay/ /var/svnroot/livecd-tools /usr/local/portage/layman/sunrise /usr/local/portage/layman/science
+
+# 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: /var/tmp/catalyst/packages/amd64
+
+# 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: /tmp/nfsboot_kernel
+
+# 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
+# -tk, -server for torque
+stage4/use: 
+	minimal
+	openmp
+	mpi
+	pbs
+	-tk
+	-server
+
+# 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.
+stage4/packages:
+    net-nds/ldap-auth
+    net-fs/nfs-utils
+	app-admin/syslog-ng
+# The init script does not agree with openrc...
+#	net-fs/autofs
+# I, kyron, hate nano:
+	app-editors/vim
+	net-misc/ntp
+	sys-power/acpid
+	net-misc/dhcpcd
+	app-shells/dash
+	sys-process/vixie-cron
+	net-dns/bind-tools
+# Clustering stuff:
+    sys-cluster/c3
+    sys-cluster/openmpi
+    app-admin/eselect-cblas
+    app-admin/eselect-blas
+    app-admin/eselect-lapack
+	
+
+
+# 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.
+stage4/fsscript: /var/git/clustering-livecd/catalyst/nfsroot/2008.0/scripts/nfsroot_setup.sh
+
+# 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.
+# (ET): The nfsroot kernel does not use initrd for the moment so let's not waste time building
+stage4/gk_mainargs: --makeopts=-j5 --symlink --no-busybox --no-initrdmodules --no-splash
+
+# 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.
+#stage4/linuxrc: /var/git/clustering-livecd/catalyst/nfsroot/2008.0/scripts/stateless.sh
+
+# 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.
+#stage4/motd: /var/git/clustering-livecd/catalyst/nfsroot/2008.0/misc/clusternode.motd.txt
+
+# 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.
+stage4/rcadd: 
+	acpid|default
+	autofs|default
+#	gmond|default
+	local|default
+	netmount|default
+	nfsmount|default
+	ntp-client|default
+	ntpd|default
+	portmap|default
+	sshd|default
+	vixie-cron|default
+# if we want Torque
+	pbs_mom|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.
+stage4/rcdel:
+	root|boot
+	mtab|boot
+	fsck|boot
+# consolefont tries to write to /lib/rc/console (ro)
+	consolefont|boot
+	localmount|boot
+	bootmisc|boot
+	
+
+# 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.
+stage4/root_overlay: /var/git/clustering-livecd/catalyst/nfsroot/2008.0/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: gentoo
+
+# 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: mm-sources
+
+# This option is the full path and filename to a kernel .config file that is
+# boot/kernel/gentoo/config: /tmp/2.6.11-smp.config
+#boot/kernel/gentoo/config: /var/git/clustering-livecd/catalyst/nfsroot/2008.0/kconfig/nfsroot.config
+boot/kernel/gentoo/config: /var/git/clustering-livecd/catalyst/nfsroot/2008.0/kconfig/gentoo-sources-2.6.24-r8-nfsroot.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.
+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:
+# let's try NBD for rootfs
+#	sys-block/nbd
+# Dropping Unionfs, using aufs:
+	sys-fs/aufs
+
+# 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.
+# Pulled in from livecd-stage2-minimal to lim down the nnodes' image, some packages might need to remain there such as db or others depending on apps that one would want to run on the nodes and the lib dependencies.
+stage4/unmerge:
+    app-admin/eselect
+    app-admin/eselect-ctags
+    app-admin/eselect-vi
+    app-admin/perl-cleaner
+    app-admin/python-updater
+    app-arch/cpio
+    dev-libs/gmp
+    dev-libs/libxml2
+    dev-libs/mpfr
+    dev-libs/popt
+    dev-python/pycrypto
+    dev-util/pkgconfig
+    net-misc/rsync
+    perl-core/PodParser
+    perl-core/Test-Harness
+    sys-apps/debianutils
+    sys-apps/diffutils
+    sys-apps/file
+    sys-apps/groff
+    sys-apps/man
+    sys-apps/man-pages
+    sys-apps/miscfiles
+#   sys-apps/portage
+#   sys-apps/sandbox
+    sys-apps/texinfo
+    sys-devel/autoconf
+    sys-devel/autoconf-wrapper
+    sys-devel/automake
+    sys-devel/automake-wrapper
+    sys-devel/binutils
+    sys-devel/binutils-config
+    sys-devel/bison
+    sys-devel/flex
+    sys-devel/gcc
+    sys-devel/gcc-config
+    sys-devel/gettext
+    sys-devel/gnuconfig
+    sys-devel/libtool
+    sys-devel/m4
+    sys-devel/make
+    sys-devel/patch
+    sys-libs/db
+    sys-libs/gdbm
+    sys-libs/libkudzu
+    sys-kernel/genkernel
+    sys-kernel/linux-headers
+
+# 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.
+stage4/empty:
+	/etc/cron.daily
+	/etc/cron.hourly
+	/etc/cron.monthly
+	/etc/cron.weekly
+	/etc/logrotate.d
+	/etc/modules.autoload.d
+	/etc/rsync
+	/etc/runlevels/single
+	/etc/skel
+	/lib/dev-state
+	/lib/udev-state
+	/lib64/dev-state
+	/lib64/udev-state
+	/root/.ccache
+	/tmp
+	/usr/diet/include
+	/usr/diet/man
+	/usr/i386-gentoo-linux-uclibc
+	/usr/i386-pc-linux-gnu
+	/usr/i386-pc-linux-uclibc
+	/usr/include
+	/usr/lib/awk
+	/usr/lib/ccache
+	/usr/lib/gcc-config
+	/usr/lib/gconv
+	/usr/lib/nfs
+	/usr/lib/perl5/site_perl
+	/usr/lib/portage
+	/usr/lib/python2.2
+	/usr/lib/python2.3
+	/usr/lib/python2.4/test
+	/usr/lib64/awk
+	/usr/lib64/ccache
+	/usr/lib64/gcc-config
+	/usr/lib64/gconv
+	/usr/lib64/nfs
+	/usr/lib64/perl5/site_perl
+	/usr/lib64/portage
+	/usr/lib64/python2.2
+	/usr/lib64/python2.3
+	/usr/lib64/python2.4/test
+	/usr/local
+	/usr/portage
+	/usr/powerpc-unknown-linux-gnu
+	/usr/powerpc64-unknown-linux-gnu
+	/usr/share/aclocal
+	/usr/share/baselayout
+	/usr/share/binutils-data
+	/usr/share/consolefonts/partialfonts
+	/usr/share/consoletrans
+	/usr/share/dict
+	/usr/share/doc
+	/usr/share/emacs
+	/usr/share/et
+	/usr/share/gcc-data
+	/usr/share/genkernel
+	/usr/share/gettext
+	/usr/share/glib-2.0
+	/usr/share/gnuconfig
+	/usr/share/gtk-doc
+	/usr/share/i18n
+	/usr/share/info
+	/usr/share/lcms
+	/usr/share/libtool
+	/usr/share/locale
+	/usr/share/man
+	/usr/share/rfc
+	/usr/share/ss
+	/usr/share/state
+	/usr/share/texinfo
+	/usr/share/unimaps
+	/usr/share/zoneinfo
+	/usr/sparc-unknown-linux-gnu
+	/usr/src
+	/usr/x86_64-pc-linux-gnu
+	/var/cache
+	/var/empty
+	/var/lib/portage
+	/var/lock
+	/var/log
+	/var/run
+# Don't empty /var/spool/torque, we need it
+	/var/spool/[^torque]
+	/var/state
+	/var/tmp
+    /usr/share/genkernel/pkg/x86/cpio
+
+# 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.
+stage4/rm:
+    /etc/*-
+	/etc/*.old
+	/etc/default/audioctl
+	/etc/dispatch-conf.conf
+	/etc/env.d/05binutils
+	/etc/env.d/05gcc
+	/etc/etc-update.conf
+	/etc/hosts.bck
+	/etc/issue*
+	/etc/genkernel.conf
+	/etc/make.conf*
+	/etc/make.globals
+	/etc/make.profile
+	/etc/man.conf
+	/etc/resolv.conf
+	/lib*/*.a
+	/lib*/*.la
+	/lib*/cpp
+	/root/.bash_history
+	/root/.viminfo
+	/sbin/*.static
+	/sbin/fsck.cramfs
+	/sbin/fsck.minix
+	/sbin/mkfs.bfs
+	/sbin/mkfs.cramfs
+	/sbin/mkfs.minix
+	/usr/bin/addr2line
+	/usr/bin/ar
+	/usr/bin/as
+	/usr/bin/audioctl
+	/usr/bin/c++*
+	/usr/bin/cc
+	/usr/bin/cjpeg
+	/usr/bin/cpp
+	/usr/bin/djpeg
+	/usr/bin/ebuild
+	/usr/bin/emerge
+	/usr/bin/elftoaout
+	/usr/bin/f77
+	/usr/bin/g++*
+	/usr/bin/g77
+	/usr/bin/gcc*
+	/usr/bin/genkernel
+	/usr/bin/gprof
+	/usr/bin/i386-gentoo-linux-uclibc-*
+	/usr/bin/i386-pc-linux-*
+	/usr/bin/jpegtran
+	/usr/bin/ld
+	/usr/bin/libpng*
+	/usr/bin/nm
+	/usr/bin/objcopy
+	/usr/bin/objdump
+	/usr/bin/piggyback*
+	/usr/bin/portageq
+	/usr/bin/ranlib
+	/usr/bin/readelf
+	/usr/bin/repoman
+	/usr/bin/size
+	/usr/bin/powerpc-unknown-linux-gnu-*
+	/usr/bin/powerpc64-unknown-linux-gnu-*
+	/usr/bin/sparc-unknown-linux-gnu-*
+	/usr/bin/sparc64-unknown-linux-gnu-*
+	/usr/bin/strings
+	/usr/bin/strip
+	/usr/bin/tbz2tool
+	/usr/bin/x86_64-pc-linux-gnu-*
+	/usr/bin/xpak
+	/usr/bin/yacc
+	/usr/lib*/*.a
+	/usr/lib*/*.la
+	/usr/lib*/perl5/site_perl
+	/usr/lib*/gcc-lib/*/*/libgcj*
+	/usr/sbin/archive-conf
+	/usr/sbin/dispatch-conf
+	/usr/sbin/emaint
+	/usr/sbin/emerge-webrsync
+	/usr/sbin/env-update
+	/usr/sbin/fb*
+	/usr/sbin/fixpackages
+	/usr/sbin/quickpkg
+	/usr/sbin/regenworld
+	/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*
+	/usr/share/misc/*.old/etc/*-
+    /etc/*.old
+    /root/.viminfo
+    /var/log/*.log
+    /usr/share/genkernel/pkg/x86/*.bz2
+