public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: derek tracy <tracyde@gmail.com>
To: gentoo-releng@lists.gentoo.org, wolf31o2@gentoo.org
Subject: Re: [gentoo-releng] Catalyst Woes
Date: Tue, 24 Aug 2004 23:41:32 -0300	[thread overview]
Message-ID: <9999810b04082419416646206f@mail.gmail.com> (raw)
In-Reply-To: <1093375536.20295.74.camel@cgianelloni.nuvox.net>

Thanks for your tips.  I unmasked mkxf86config *-r3 and livecd-tools
and am compiling the cd as I type this.  My first undertaking was to
actually create a business card cd but I am going to hold that off for
future releases.  I am actually going to make this a project.  The
final goal is going to be a cd with X.org / Openbox that is made for
pen-testing networks.  I have created a project site
http://infoportal.dyndns.info
Eventually I want to write a couple of howtos for the community, so
others can do as I am.  After reading through all of the forums I know
that there is a demand for more Catalyst documentation.

One last thing how did you guys get SquashFS to work on 2004.2, I can
get the cd to make the ISO and start to boot but it crashes when it
tries to mount filesystem, any ideas or maybe a link to the kernel
config and the exact kernel that 2004.2 uses.

Just in case you are wondering the livecd project that I am working on
is named D.A.R.T (Diagnostic Assault and Recovery Terminal)
Thanks Again.

On Tue, 24 Aug 2004 15:25:36 -0400, Chris Gianelloni
<wolf31o2@gentoo.org> wrote:
> On Tue, 2004-08-24 at 14:20, derek tracy wrote:
> > Here is my spec file you requested (livecd-stage2)
> 
> I also forgot one other thing... livecd/xinitrc... this allows you to
> give catalyst a default xinitrc for your LiveCD, which is essential for
> getting it to start the applications you want, unless you're doing all
> the work on your fsscript.sh file.
> 
> 
> 
> > ----------------Begin-----------------
> >
> > subarch: x86
> > version_stamp: 0.2
> > target: livecd-stage2
> > rel_type: default
> > profile: default-x86-2004.2
> > snapshot: 20040819
> > source_subpath: default/livecd-stage1-x86-0.1
> >
> > livecd/cdfstype: zisofs
> > livecd/archscript: /usr/lib/catalyst/livecd/runscript/x86-archscript.sh
> > livecd/runscript: /usr/lib/catalyst/livecd/runscript/default-runscript.sh
> > livecd/cdtar: /usr/lib/catalyst/livecd/cdtar/isolinux-2.08-memtest86+-cdtar.tar.bz2
> > livecd/iso: /root/catalyst/LiveCD/LiveCD.iso
> > # livecd/bootsplash: /usr/share/bootsplash/initrd-livecd-2004.1-1024x768
> > livecd/fsscript: /root/catalyst/LiveCD/fsscript.sh
> >
> > boot/kernel: gentoo
> > #boot/kernel/gentoo/extraversion: foo
> > boot/kernel/gentoo/sources: =sys-kernel/gentoo-dev-sources-2.6.3-r1
> > boot/kernel/gentoo/packages: pcmcia-cs nforce-net linux-wlan-ng slmodem
> > boot/kernel/gentoo/config:
> > /usr/lib/catalyst/livecd/kconfig/config-2004.1-gentoo-dev-sources-2.6.3-r1
> >
> > livecd/unmerge:
> >        autoconf
> >        automake
> > #       gcc
> >        bin86
> >        binutils
> >        libtool
> >        m4
> >        bison
> >        ld.so
> >        make
> >        perl
> >        patch
> >        linux-headers
> >        man-pages
> >        sash
> >        bison
> >        flex
> > #       gettext
> >        texinfo
> >        ccache
> >        addpatches
> >        man
> >        groff
> >        lib-compat
> >        miscfiles
> > #       python
> >
> > livecd/empty:
> >        /var/tmp
> >        /var/cache
> >        /var/db
> >        /var/empty
> >        /var/cache
> >        /var/lock
> >        /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/X11R6/man
> > #       /usr/X11R6/include
> > #       /usr/X11R6/lib/X11/config
> > #       /usr/X11R6/lib/X11/etc
> > #       /usr/X11R6/lib/X11/doc
> >        /usr/src
> >        /usr/share/doc
> >        /usr/share/man
> >        /root/.ccache
> >
> > livecd/rm:
> >        /lib/*.a
> >        /usr/lib/*.a
> >        /usr/lib/gcc-lib/*/*/libgcj*
> > #       /usr/X11R6/lib/*.a
> >        /var/log/emerge.log
> >        /var/log/genkernel.log
> >
> > -----------------End-----------------
> >
> >
> >
> > On Tue, 24 Aug 2004 13:34:56 -0400, Chris Gianelloni
> > <wolf31o2@gentoo.org> wrote:
> > > On Tue, 2004-08-24 at 13:06, derek tracy wrote:
> > > > The spec file that I posted earlier was my livecd-stage2 spec file.  I
> > >
> > > There was no spec file anywhere in the thread.
> > >
> > > > have got almost everything working I just have to find a way to shrink
> > > > down the final iso and configure x.org automatically.  If someone
> > >
> > > Try adding mkxf86config into your livecd-stage1 spec file.  You will
> > > then want to add a livecd/rcadd: mkxf86config line to your
> > > livecd-stage2.  You will want to unmask the -r3 version in your snapshot
> > > for it to work properly with xorg-x11.  If you want accelerated 3D, you
> > > might want to unmask livecd-tools-1.0.5 from package.mask and also make
> > > sure to add nvidia-kernel, nvidia-glx, and ati-drivers to your
> > > boot/kernel/$kernel_name/packages lines in your livecd-stage2.
> > >
> > > > could give me a hand I would really appreciate it.  Also when you are
> > > > emptying directories in livecd-stage2 how do you know exactly what
> > > > directories are not needed or exactly what files the programs rely on..
> > >
> > > The only way to know is to experiment.  There is no hard and fast rules
> > > for this, unfortunately.  It's pretty simple to guess that examples and
> > > documentation can go.
> > >
> > >
> > >
> > > >  I really need some insight on this.
> > > >
> > > > On Tue, 24 Aug 2004 09:27:25 -0400, Chris Gianelloni
> > > > <wolf31o2@gentoo.org> wrote:
> > > > > Attach your livecd-stage2 spec file, please.
> > > > >
> > > > >
> > > > >
> > > > > On Mon, 2004-08-23 at 22:57, derek tracy wrote:
> > > > > > livecd-stage2
> > > > > >
> > > > > > On Mon, 23 Aug 2004 16:19:43 -0400, Chris Gianelloni
> > > > > > <wolf31o2@gentoo.org> wrote:
> > > > > > >
> > > > > > >
> > > > > > > On Mon, 2004-08-23 at 15:36, derek tracy wrote:
> > > > > > > > Has anyone had any experience with Catalyst.  I am having a few
> > > > > > > > issues.  The biggest one is this.  I am trying to create a bootable
> > > > > > > > LiveCD with X and Openbox on it.  I have everything set up correctly
> > > > > > > > and working great until I do the Stage2 run.  That is when it strips
> > > > > > > > out X and everything else.  Has anyone had this problem before, or
> > > > > > > > have any ideas on fixing it?
> > > > > > >
> > > > > > > stage2 or livecd-stage2?
> > > > > > >
> > > > > > > --
> > > > > > > Chris Gianelloni
> > > > > > > Release Engineering - Operations/QA Manager
> > > > > > > Games - Developer
> > > > > > > Gentoo Linux
> > > > > > >
> > > > > > > Is your power animal a penguin?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > gentoo-releng@gentoo.org mailing list
> > > > >
> > > > >
> > > > > --
> > > > > Chris Gianelloni
> > > > > Release Engineering - Operations/QA Manager
> > > > > Games - Developer
> > > > > Gentoo Linux
> > > > >
> > > > > Is your power animal a penguin?
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > gentoo-releng@gentoo.org mailing list
> > > --
> > > Chris Gianelloni
> > > Release Engineering - Operations/QA Manager
> > > Games - Developer
> > > Gentoo Linux
> > >
> > > Is your power animal a penguin?
> > >
> > >
> > >
> >
> > --
> > gentoo-releng@gentoo.org mailing list
> --
> Chris Gianelloni
> Release Engineering - Operations/QA Manager
> Games - Developer
> Gentoo Linux
> 
> Is your power animal a penguin?
> 
> 
>

--
gentoo-releng@gentoo.org mailing list


  reply	other threads:[~2004-08-25  2:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23 19:36 [gentoo-releng] Catalyst Woes derek tracy
2004-08-23 20:19 ` Chris Gianelloni
2004-08-24  2:57   ` derek tracy
2004-08-24 13:27     ` Chris Gianelloni
2004-08-24 17:06       ` derek tracy
2004-08-24 17:34         ` Chris Gianelloni
2004-08-24 18:20           ` derek tracy
2004-08-24 19:25             ` Chris Gianelloni
2004-08-25  2:41               ` derek tracy [this message]
2004-08-25 14:03                 ` Chris Gianelloni
2004-08-25 15:25                   ` derek tracy
2004-08-25 17:28                     ` Chris Gianelloni
2004-08-26 17:05                       ` derek tracy
2004-08-26 18:43                         ` Chris Gianelloni
2004-08-26 19:01                           ` derek tracy
2004-08-26 19:01                             ` derek tracy
2004-08-26 19:36                               ` Chris Gianelloni
2004-08-26 19:49                                 ` derek tracy
2004-08-26 22:02                                   ` Chris Gianelloni
2004-08-27 14:23                                     ` derek tracy
2004-08-27 19:00                                       ` Chris Gianelloni
2004-08-27 21:23                                         ` Paul de Vrieze
2004-08-29  4:55                                         ` derek tracy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9999810b04082419416646206f@mail.gmail.com \
    --to=tracyde@gmail.com \
    --cc=gentoo-releng@lists.gentoo.org \
    --cc=wolf31o2@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox