RE: [gentoo-catalyst] Make liveCD how to

["Kessler, Paul" <kessler@co.wabasha.mn.us>]

[-- Attachment #1: Type: text/plain, Size: 4998 bytes --]

Ok here is some things to try, go download stage3-x86-2005.1-r1 from one
of the mirrors. There have been several fixes included. Here is an
example of the stage 1 spec file format you might want to use based on
what you provided:

 

subarch: x86

version_stamp: 2005.1-r1

target: livecd-stage1

rel_type: default

profile: default-linux/x86/2005.1

snapshot: 2005.1 

source_subpath: stage3-x86-2005.1-r1

portage_confdir: /etc/portage

livecd/use: livecd ncurses readline -X -gnome -gtk

livecd/packages: baselayout livecd-tools gentoo-sources dhcpcd
app-admin/sudo pwgen hotplug coldplug syslog-ng vim ethtool vim openssh
gpm

 

Remember if you aren't using an option in a spec file be sure to comment
it out. Also make sure that you emerged catalyst with the docs, the
examples contained in /usr/share/doc/catalyst-<version>/examples are not
only very well documented but are the most current information
available.

 

________________________________

From: js [mailto:forums@emat.be] 
Sent: Tuesday, November 29, 2005 2:51 PM
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Make liveCD how to

 

Well I've done this:

livecd-tools is in the list and included in the build,.....


Here's my specfile:

# livecd-stage1 example specfile
# used to build a livecd-stage1

# 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/reference.xml
# example:
subarch: x86

# 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: 2005.1-r1

# The target specifies what target we want catalyst to do.  For building
a CD,
# we start with livecd-stage1 as our target.
# example:
target: livecd-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

# 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/2005.0
profile: default-linux/x86/2005.1

# This specifies which snapshot to use for building this target.
# example:
# snapshot:
snapshot: 2005.1

# 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-2004.3
source_subpath:default/stage3-x86-2005.1-r1

# 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

# 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

livecd/use:
        -X
        -gtk
        -opengl
        -svga
        ipv6
        socks5
        livecd
        fbcon
        ssl

livecd/packages:
        baselayout
        livecd-tools
        ucl
        hwsetup
        module-init-tools
        hotplug
        irssi
        aumix
        metalog
        pciutils
        parted
        mt-st
        links
        star
        strace
        raidtools
        nfs-utils
        jfsutils
        usbutils
        speedtouch
        xfsprogs
        xfsdump
        e2fsprogs
        reiserfsprogs
        hdparm
        nano
        less
        openssh
        dhcpcd
        mingetty
        pwgen
        popt
        dialog
        rp-pppoe
        gpm
        screen
        mirrorselect
        penggy
        iputils
        hwdata-knoppix
        hwsetup
        bootsplash
        device-mapper
        lvm2
        evms
        vim
        gpart
        pwgen
        pptpclient
        mdadm
        tcptraceroute
        netcat
        ethtool
        wireless-tools
        tcpdump
        nmap
        libpcap
        sniffit
        sleuthkit
        vblade



Chris Gianelloni wrote: 

On Tue, 2005-11-29 at 20:51 +0100, js wrote:
  

	Thank You Chris for your patience,
	 
	I'm in the stage of having my own first humble gentoo linux
based
	bootdisk right now:-)
	One detail though,
	When booted I'm asked for a login and password,.... which  but I
don't
	know the password (which will be randomized i guess)
	 
	How can I arrange that i just get a prompt and allready logged
in as
	root?
	    

 
install livecd-tools in livecd-stage1, as it pulls in bashlogin
 
  
-- gentoo-catalyst@gentoo.org mailing list

[-- Attachment #2: Type: text/html, Size: 15008 bytes --]