Re: [gentoo-catalyst] Make liveCD how to

[js]

  
  


Hi Paul,

Yes, that is very possible.
I'm allready happy that i've been able to make a working bootcd this
way. Altough I can't get past the login and password when booted.

Would it be possible to  get somehow the stage1 and stage2 specfiles
used to build the gentoo-livecd's or is that not possible? :-)
It must be possible with those files to build exact the same livecd as
the official one?


Greetings,

Jelle

Kessler, Paul wrote:

  
  

  
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:black;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
  
   
  Is it just
me or does this look like a
cross between the new and the old spec file syntax? Maybe out of the
wiki?
   
   
   
   
    
  From: js
[mailto:forums@××××.be] 
  Sent: Tuesday,
November 29, 2005
2:51 PM
  To:
gentoo-catalyst@l.g.o
  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
   
    
   
   
  
-- 
This message has been scanned for viruses and
  
dangerous content by FrontLine, and is believed to be clean.
-- gentoo-catalyst@g.o mailing list



-- 
gentoo-catalyst@g.o mailing list