[gentoo-catalyst] minimal install on usb key

[gentoo-catalyst] minimal install on usb key

[Christophe PEREZ]

Hi,

I would like to know if somebody has already tried to build a USB key (?)
with something like install-x86-minimal-2005.0.iso ?

I tried with livecd-ng, now trying with catalyst (but I don't understand
all) and I find it a bit difficult to do.

I would like to do it myself because I want to build other usb system
after so, if someone can give me the "howto", it will be great.

thanks

PS : sorry for my poor english.

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] minimal install on usb key

[Chris Gianelloni]

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

On Thu, 2005-06-23 at 01:15 -0400, Christophe PEREZ wrote:
> Hi,
> 
> I would like to know if somebody has already tried to build a USB key (?)
> with something like install-x86-minimal-2005.0.iso ?

Copy the contents of the CD to the USB key and it'll boot.  You just
have to use cdroot=/dev/sda1 (or wherever your key is).

> I tried with livecd-ng, now trying with catalyst (but I don't understand
> all) and I find it a bit difficult to do.

Well, livecd-ng was dumped for a reason, it had zero flexibility and
wasn't designed for anything other than creating Gentoo releases.

> I would like to do it myself because I want to build other usb system
> after so, if someone can give me the "howto", it will be great.

There is no "howto" at all, since it is the exact same as building a CD
using catalyst.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: minimal install on usb key

[Christophe PEREZ]

Le Thu, 23 Jun 2005 09:14:07 -0400, Chris Gianelloni a écrit :

> Copy the contents of the CD to the USB key and it'll boot.  You just
> have to use cdroot=/dev/sda1 (or wherever your key is).

Oh !
But I need more details for hat.
What kind of file system ? vfat ?
Where have I to put this cdroot= ? in isolinux/isolinux.cfg ? instead of
croot=/dev/ram0 ? Otherwhere ?

> Well, livecd-ng was dumped for a reason, it had zero flexibility and
> wasn't designed for anything other than creating Gentoo releases.

I understood that after a lot of reading ;-)

> There is no "howto" at all, since it is the exact same as building a CD
> using catalyst.

Yes but never found the end of a iso building with catalyst...

actually, I have :

>>> Recording net-firewall/iptables in "world" favorites file...

>>> clean: No packages selected for removal.

>>> Auto-cleaning packages ...

>>> No outdated packages were found on your system.


 * GNU info directory index is up-to-date.

* <<< Callback exit status: 0

tar: Bad Option: -jxpf.
Usage:  tar cmd [options] file1 ... filen

Use     tar -help
and     tar -xhelp
to get a list of valid cmds and options.

Use     tar H=help
to get a list of valid archive header formats.

Use     tar diffopts=help
to get a list of valid diff options.
* ERROR: Could not extract busybox source tarball!

with stage2.

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: minimal install on usb key

[Chris Gianelloni]

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

On Thu, 2005-06-23 at 13:34 -0400, Christophe PEREZ wrote:
> Le Thu, 23 Jun 2005 09:14:07 -0400, Chris Gianelloni a écrit :
> 
> > Copy the contents of the CD to the USB key and it'll boot.  You just
> > have to use cdroot=/dev/sda1 (or wherever your key is).
> 
> Oh !
> But I need more details for hat.
> What kind of file system ? vfat ?

What filesystem do you have on your USB key?  You know the answer to
this, not I.

> Where have I to put this cdroot= ? in isolinux/isolinux.cfg ? instead of
> croot=/dev/ram0 ? Otherwhere ?

When you boot the CD.  Though you could edit it in $arch-archscript in
catalyst before building your CD.

> Yes but never found the end of a iso building with catalyst...

Remove star from your spec files.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Thu, 23 Jun 2005 14:40:39 -0400, Chris Gianelloni a écrit :

> What filesystem do you have on your USB key?  You know the answer to
> this, not I.

I can put what I want, vfat, ext2, ext3...
But, for example, with syslinux, I need vfat...

>> Where have I to put this cdroot= ? in isolinux/isolinux.cfg ? instead of
>> croot=/dev/ram0 ? Otherwhere ?
> 
> When you boot the CD.

When I boot on it, I just have a "none system on this disk"

>  Though you could edit it in $arch-archscript in
> catalyst before building your CD.

So, that's not only copy file to my usb key !

>> Yes but never found the end of a iso building with catalyst...
> 
> Remove star from your spec files.

I'll try that, thanks..

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

[gentoo-catalyst] Re: minimal install on usb key

[Christophe PEREZ]

Le Thu, 23 Jun 2005 09:14:07 -0400, Chris Gianelloni a écrit :

> Copy the contents of the CD to the USB key and it'll boot.  You just
> have to use cdroot=/dev/sda1 (or wherever your key is).

Ok, I've got it now.
But I had to search a lot.
First, I had of course to put a grub on the usb key.
Then, to had a rootdelay= option for the boot wait to my usb key.
But, it was no sufficient because, I don't know why, but udev doesn't
create /dev/sda and /dev/sda1
(runUdev in /linuxrc)

(something strange, udevstart which is in /bin is called by
/sbin/udevstart in /etc/initrd.scripts but modifying it never change for
/dev/sdaX)

I had to add :
        ################### FOR USB BOOT ###################################
        echo -e "${WARN}>>${NORMAL}${BOLD} We must hard create device nodes"
        /usr/bin/mknod /newroot/dev/sda b 8 0
        /usr/bin/mknod /newroot/dev/sda1 b 8 1
        ################### END FOR USB BOOT ###############################

before bootstrapCD in /linuxrc

Now it works, but no really so simple as just copying files from iso to
usb key.
I'll put that img on my site soon if somebody is interested...

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: minimal install on usb key

[Zac Medico]

Christophe PEREZ wrote:
> Le Thu, 23 Jun 2005 09:14:07 -0400, Chris Gianelloni a écrit :
> 
> 
>>Copy the contents of the CD to the USB key and it'll boot.  You just
>>have to use cdroot=/dev/sda1 (or wherever your key is).
> 
> 
> Ok, I've got it now.
> But I had to search a lot.
> First, I had of course to put a grub on the usb key.
> Then, to had a rootdelay= option for the boot wait to my usb key.
> But, it was no sufficient because, I don't know why, but udev doesn't
> create /dev/sda and /dev/sda1
> (runUdev in /linuxrc)
> 
> (something strange, udevstart which is in /bin is called by
> /sbin/udevstart in /etc/initrd.scripts but modifying it never change for
> /dev/sdaX)
> 
> I had to add :
>         ################### FOR USB BOOT ###################################
>         echo -e "${WARN}>>${NORMAL}${BOLD} We must hard create device nodes"
>         /usr/bin/mknod /newroot/dev/sda b 8 0
>         /usr/bin/mknod /newroot/dev/sda1 b 8 1
>         ################### END FOR USB BOOT ###############################
> 
> before bootstrapCD in /linuxrc
> 
> Now it works, but no really so simple as just copying files from iso to
> usb key.
> I'll put that img on my site soon if somebody is interested...
> 

The rootdelay parameter should work (use a 5 or 10 second delay) with root=/dev/sda1 (no initrd) and statically linked usb drivers.  If the usb drivers are modular then you need to have a delay inside linuxrc between the modules loading and udevstart (again, sleep 5 or 10 should do it).  A parameter like "scandelay" is useful for tuning this. 

Note that if you get the 'Please specify a device to boot, or "shell" for a shell...' message then you can choose shell, run udevstart, exit, and try to specify your root device again.  There is a loop there inside linuxrc that helps for troubleshooting.  You should see your block device inside /sys/block if it has been detected properly.

Zac
-- 
gentoo-catalyst@gentoo.org mailing list

[gentoo-catalyst] Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Sat, 25 Jun 2005 18:13:09 -0700, Zac Medico a écrit :

> The rootdelay parameter should work (use a 5 or 10 second delay)

I use it, it works.

> with
> root=/dev/sda1 (no initrd) and statically linked usb drivers.

It woudl'nt be the same system as the iso at all.
I wanted exactly the same, but on a usb key.

> If the
> usb drivers are modular then you need to have a delay inside linuxrc
> between the modules loading and udevstart (again, sleep 5 or 10 should
> do it).  A parameter like "scandelay" is useful for tuning this.
> 
> Note that if you get the 'Please specify a device to boot, or "shell"
> for a shell...' message then you can choose shell, run udevstart, exit,

I didn't need anything, just launch /dev/ram0. udevstart doesn't create
any /dev/sd* for me.

> and try to specify your root device again.  There is a loop there inside
> linuxrc that helps for troubleshooting.

I saw that.

> You should see your block
> device inside /sys/block if it has been detected properly.

now, it is, because of my "mknod".

All is fine now, but I wanted to show that it is not so simple as said...

I put the img there :
http://www.madinux.org/download/install-x86-minimal-2005.0_usb_64m.img.bz2

It's for a 64Mb key.

I'll try now to understand how I can use catalyst to personnalize it.

Something great would be to have exactly the template for the original iso.
I tried to do one, but my iso is 116Mb, not 50. I don't understand why.

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: Re: minimal install on usb key

[Zac Medico]

Christophe PEREZ wrote:
> Le Sat, 25 Jun 2005 18:13:09 -0700, Zac Medico a écrit :
> 
> 
>>The rootdelay parameter should work (use a 5 or 10 second delay)
> 
> 
> I use it, it works.
> 
> 
>>with
>>root=/dev/sda1 (no initrd) and statically linked usb drivers.
> 
> 
> It woudl'nt be the same system as the iso at all.
> I wanted exactly the same, but on a usb key.
> 
> 
>>If the
>>usb drivers are modular then you need to have a delay inside linuxrc
>>between the modules loading and udevstart (again, sleep 5 or 10 should
>>do it).  A parameter like "scandelay" is useful for tuning this.
>>
>>Note that if you get the 'Please specify a device to boot, or "shell"
>>for a shell...' message then you can choose shell, run udevstart, exit,
> 
> 
> I didn't need anything, just launch /dev/ram0. udevstart doesn't create
> any /dev/sd* for me.
> 

Are the usb drivers modular?  In any case, udevstart should work if the usb drivers have had time to initialize and create /sys entries.  I think you need to add a delay somewhere (I boot from a usb hard disk and udev works fine for me).

> 
>>and try to specify your root device again.  There is a loop there inside
>>linuxrc that helps for troubleshooting.
> 
> 
> I saw that.
> 
> 
>>You should see your block
>>device inside /sys/block if it has been detected properly.
> 
> 
> now, it is, because of my "mknod".
> 

Also, maybe it's better not to assume that /dev/sda1 will be assigned to your usb drive (the may be other usb devices connected).  There is a feature request that will allow you to specify a partition label or uuid instead of a specific device.

http://bugs.gentoo.org/show_bug.cgi?id=83771

> All is fine now, but I wanted to show that it is not so simple as said...
> 
> I put the img there :
> http://www.madinux.org/download/install-x86-minimal-2005.0_usb_64m.img.bz2
> 
> It's for a 64Mb key.
> 
> I'll try now to understand how I can use catalyst to personnalize it.
> 
> Something great would be to have exactly the template for the original iso.
> I tried to do one, but my iso is 116Mb, not 50. I don't understand why.
> 

Maybe you can use the "du" command to compare your space usage and pinpoint the cause.

Zac
-- 
gentoo-catalyst@gentoo.org mailing list

[gentoo-catalyst] Re: Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Sat, 25 Jun 2005 19:29:46 -0700, Zac Medico a écrit :

> Are the usb drivers modular?  In any case, udevstart should work if the
> usb drivers have had time to initialize and create /sys entries.  I
> think you need to add a delay somewhere (I boot from a usb hard disk and
> udev works fine for me). 

I tried to put a delay in linuxrc but no change.
usb modules are loaded because if I create nodes manually (in lunuxrc), it
can mount it.
The problem is only with the /dev/sd*

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

[gentoo-catalyst] Re: minimal install on usb key

[Christophe PEREZ]

Le Thu, 23 Jun 2005 09:14:07 -0400, Chris Gianelloni a écrit :

> There is no "howto" at all, since it is the exact same as building a CD
> using catalyst.

I just found what I needed in the livecd-specs package.
So, for test, I want to build exactly the same iso as install-minimal.
I took livecd-stage1.spec, and built the first stage.
But, in the second, I have a conflict with ipw2100 and ipw2200.

--------------------------------------------
* Preparing to run callback: "emerge pcmcia-cs speedtouch slmodem globespan-adsl hostap-driver hostap-utils ipw2100 ipw2200 acpid cryptsetup"Calculating dependencies  ...done!

!!! Error: the net-wireless/ipw2100 package conflicts with another package.
--
!!!        Please use 'emerge --pretend' to determine blockers.
---------------------------------------------

I don't understand why, if I have exactly the same specs as the creator of
the iso...

Others questions :

1) how to specify, in catalyst, options for boot, for example, the
rootdelay= ? I could change it by hand in isolinux.cfg but, in catalyst ?

2) my portage/disfiles in on a nfs mount. And if I configure catalyst to
use this directory, bind seems not to work, and all packages are
downloaded each time in stages.

3) to use disstcc, I just have to add it in options of catalyst.conf, and
specify hosts in distcc_hosts of stages ? I always have errors during
compilation if I do that.

I use catalyst-1.1.10_pre11

PS : Sorry if I don't explain more, but it's really difficult for me to
explain in english. I'm not sure you will understand me.

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: minimal install on usb key

[Robert Paskowitz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Installing both ipw2100 and ipw2200 takes a bit of trickery. Both
packages provide some of the same files, so the only way to do it is to
ensure that you will be installing versions of ipw2100 and ipw2200 that
provide the same versions of the files that conflict, and you will need
to edit the ebuilds so that they no longer block each other.

The latest versions that I know of that can be installed side by side
are ipw2100-1.0.5 and ipw2200-1.0.1. If there is something more recent,
brix(@gentoo.org, or on freenode), is the best guy to speak to.


Christophe PEREZ wrote:
> Le Thu, 23 Jun 2005 09:14:07 -0400, Chris Gianelloni a écrit :
> 
> 
>>There is no "howto" at all, since it is the exact same as building a CD
>>using catalyst.
> 
> 
> I just found what I needed in the livecd-specs package.
> So, for test, I want to build exactly the same iso as install-minimal.
> I took livecd-stage1.spec, and built the first stage.
> But, in the second, I have a conflict with ipw2100 and ipw2200.
> 
> --------------------------------------------
> * Preparing to run callback: "emerge pcmcia-cs speedtouch slmodem globespan-adsl hostap-driver hostap-utils ipw2100 ipw2200 acpid cryptsetup"Calculating dependencies  ...done!
> 
> !!! Error: the net-wireless/ipw2100 package conflicts with another package.
> --
> !!!        Please use 'emerge --pretend' to determine blockers.
> ---------------------------------------------
> 
> I don't understand why, if I have exactly the same specs as the creator of
> the iso...
> 
> Others questions :
> 
> 1) how to specify, in catalyst, options for boot, for example, the
> rootdelay= ? I could change it by hand in isolinux.cfg but, in catalyst ?
> 
> 2) my portage/disfiles in on a nfs mount. And if I configure catalyst to
> use this directory, bind seems not to work, and all packages are
> downloaded each time in stages.
> 
> 3) to use disstcc, I just have to add it in options of catalyst.conf, and
> specify hosts in distcc_hosts of stages ? I always have errors during
> compilation if I do that.
> 
> I use catalyst-1.1.10_pre11
> 
> PS : Sorry if I don't explain more, but it's really difficult for me to
> explain in english. I'm not sure you will understand me.
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCvtzxZwjIiODIZ4oRAkZEAJsGesuoPvj/hG4xmG6GmZlz6a9rdACePZr/
tgskH8HFEapX7uDKKbEu2s8=
=UvC2
-----END PGP SIGNATURE-----
-- 
gentoo-catalyst@gentoo.org mailing list

[gentoo-catalyst] Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Sun, 26 Jun 2005 12:50:57 -0400, Robert Paskowitz a écrit :

> Installing both ipw2100 and ipw2200 takes a bit of trickery. Both
> packages provide some of the same files, so the only way to do it is to
> ensure that you will be installing versions of ipw2100 and ipw2200 that
> provide the same versions of the files that conflict,

I think I understand that, but, so, how is it possible they are both in
the specs which provided install-minimal iso ?
boot/kernel/gentoo/packages:
        pcmcia-cs
        speedtouch
        slmodem
        globespan-adsl
        hostap-driver
        hostap-utils
        ipw2100
        ipw2200
        acpid
        cryptsetup
        #fcdsl
        #fritzcapi


> and you will need
> to edit the ebuilds so that they no longer block each other.
> 
> The latest versions that I know of that can be installed side by side
> are ipw2100-1.0.5 and ipw2200-1.0.1.

Ah !
In fact, I forgot this question before :
How to specify a particular USE ou other flag for only one package in
catalyst like in /etc/portage/package.* ?


> If there is something more recent,
> brix(@gentoo.org, or on freenode), is the best guy to speak to.

thank you for your help, but I don't really know what I have to do to
build my own install-x86-minimal-2005.0.iso similar to the original.

I'll stop to post here because I have always the same problem, I don't
understand answers... but, it's my fault.

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: Re: minimal install on usb key

[Chris Gianelloni]

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

On Sun, 2005-06-26 at 13:24 -0400, Christophe PEREZ wrote:
> I think I understand that, but, so, how is it possible they are both in
> the specs which provided install-minimal iso ?

Having the same spec file is *not* the same as duplicating my work.  You
also need the exact same snapshot, as we tend to make slight snapshot
modifications for the releases.  You can get the snapshot,
portage-20050303.tar.bz2, from /releases/snapshot/2005.0 on your
favorite Gentoo mirror.

> Ah !
> In fact, I forgot this question before :
> How to specify a particular USE ou other flag for only one package in
> catalyst like in /etc/portage/package.* ?

While it can be done using portage_confdir, I highly recommend against
it.

> thank you for your help, but I don't really know what I have to do to
> build my own install-x86-minimal-2005.0.iso similar to the original.

To duplicate my work, you need an identical environment, not similar.

> I'll stop to post here because I have always the same problem, I don't
> understand answers... but, it's my fault.

You just need to ask more questions, honestly.  It might also help to
search the archives, since most of these questions pop up over and over
again.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: minimal install on usb key

[Christophe PEREZ]

Le Mon, 27 Jun 2005 10:04:44 -0400, Chris Gianelloni a écrit :

> Having the same spec file is *not* the same as duplicating my work.  You
> also need the exact same snapshot, as we tend to make slight snapshot
> modifications for the releases.

Yes, of course.

> You can get the snapshot,
> portage-20050303.tar.bz2, from /releases/snapshot/2005.0 on your
> favorite Gentoo mirror.

But, I prefere to have to system 'uptodate'.
For the moment, I just removed ipw2100 because I didn't really knew what
to do.

> While it can be done using portage_confdir, I highly recommend against
> it.

I don't find this option anywhere !

> To duplicate my work, you need an identical environment, not similar.

Ok, clear now...

> You just need to ask more questions, honestly.

Are you sure you want to see me here everyday ? ;-)

> It might also help to
> search the archives, since most of these questions pop up over and over
> again.

I always have :
http://www.gentoo.org/proj/en/releng/catalyst/1.x/reference.xml
http://dev.gentoo.org/~citizen428/hypermail/gentoo-catalyst/thread.html
and others from forum opened in my firefox ;-)
I always search before asking here.
But, often, I don't understand the answers, or, I don't find the same
problem as mine.

I have now my own install-minimal-20050627.iso, and I wrote a script
to concert it automaticaly in a liveusb, booting with grub, splash etc...
I'm really happy !

I'll try now to make some builds more difficult, but for that, I first
need to know how to affect USES to my packages.

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: minimal install on usb key

[Chris Gianelloni]

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

On Tue, 2005-06-28 at 00:38 -0400, Christophe PEREZ wrote:
> But, I prefere to have to system 'uptodate'.
> For the moment, I just removed ipw2100 because I didn't really knew what
> to do.

Please do not complain that you cannot duplicate my work if you are not
using an identical environment.

> > While it can be done using portage_confdir, I highly recommend against
> > it.
> 
> I don't find this option anywhere !

It is in the documentation.  Did you install catalyst with USE="doc
examples"?  If not, I suggest you do so and start looking at the example
spec files, along with the documentation.  The example spec files,
in /usr/share/doc/catalyst-$ver/examples, are up-to-date and have all
the options listed.

> > You just need to ask more questions, honestly.
> 
> Are you sure you want to see me here everyday ? ;-)

Sure.

> http://www.gentoo.org/proj/en/releng/catalyst/1.x/reference.xml

Use the example ebuild in /usr/share/doc/catalyst-$ver/examples, rather
than this out-of-date document.

> http://dev.gentoo.org/~citizen428/hypermail/gentoo-catalyst/thread.html
> and others from forum opened in my firefox ;-)

Honestly, I would also avoid the forums, as they have been anywhere from
100% correct to 100% wrong in how to do things.  It is best to use the
authoritative sources for information, which currently is this list,
which has the catalyst developers on it, and also the examples installed
via the catalyst ebuild.

> I always search before asking here.
> But, often, I don't understand the answers, or, I don't find the same
> problem as mine.

Generally, if a problem is similar, then it is the same.  As for
understanding the problems/solutions, that will come with time.
Catalyst is a fairly complex piece of software.  Unfortunately, with
flexibility, comes complexity.

> I have now my own install-minimal-20050627.iso, and I wrote a script
> to concert it automaticaly in a liveusb, booting with grub, splash etc...
> I'm really happy !

Cool.  =]

> I'll try now to make some builds more difficult, but for that, I first
> need to know how to affect USES to my packages.

Honestly, the best way is via livecd/use, rather than a portage
configuration directory.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Tue, 28 Jun 2005 10:06:21 -0400, Chris Gianelloni a écrit :

> Please do not complain that you cannot duplicate my work if you are not
> using an identical environment.

I don't complain. I think I don't explain very well.
I'll try again.
I took specs in livecd-specs.
I tried to build with them and I had this conflict (ipw2100 & ipw2200)
I never thougth my snapshot was different than yours.
Now, I can understand that we don't have identical environnement, and, as
I wanted to have an up-to-date build, the only solution I found (bad, I
know) was to remove one of the 2 packages. I choose ipw2100.

> It is in the documentation.  Did you install catalyst with USE="doc
> examples"?

Yes, of course, I generaly do what is 'suggested' in documentations ;-)

> If not, I suggest you do so and start looking at the example
> spec files, along with the documentation.  The example spec files,
> in /usr/share/doc/catalyst-$ver/examples, are up-to-date and have all
> the options listed.

Ok.
My first tries were with thoses specs, but I never reach end of build.
So, I took specs in livecd-specs, and it doesn't contain this
portage_confdir, and I forgot to go to thoses examples.
In this example (livecd-stage1_template.spec), does options examples the
defaults you used to build the iso ? Because, options are empty and it
does not help me to begin.

>> Are you sure you want to see me here everyday ? ;-)
> 
> Sure.

You will regret it ;-)

>> http://www.gentoo.org/proj/en/releng/catalyst/1.x/reference.xml
> 
> Use the example ebuild in /usr/share/doc/catalyst-$ver/examples, rather
> than this out-of-date document.

Ok, I didn't know that.

>> http://dev.gentoo.org/~citizen428/hypermail/gentoo-catalyst/thread.html
>> and others from forum opened in my firefox ;-)
> 
> Honestly, I would also avoid the forums, as they have been anywhere from
> 100% correct to 100% wrong in how to do things.  It is best to use the
> authoritative sources for information, which currently is this list,
> which has the catalyst developers on it,

Yes, but archives are not already very completes.

> and also the examples installed
> via the catalyst ebuild.

Now, I know ;-)

> Generally, if a problem is similar, then it is the same.  As for
> understanding the problems/solutions, that will come with time.

You can take time when you understand something, but when you understand
anything, it's more difficult ;-)
But, I know I'll need time...

> Catalyst is a fairly complex piece of software.  Unfortunately, with
> flexibility, comes complexity.

Of course.

>> I'm really happy !
> 
> Cool.  =]

;-)

>> I'll try now to make some builds more difficult, but for that, I first
>> need to know how to affect USES to my packages.
> 
> Honestly, the best way is via livecd/use, rather than a portage
> configuration directory.

Ah, not portage_postdir anymore ?
And, If I want a USE is used by only one package (for exemple a plugin for
mozilla, but I don't want all packages with USE="mozilla") ?

Another question, important even if I forgot it before, what is the best
way to modify some configuration files eg : /etc/fstab to mount nfs etc...
?
I don't think it is modifying catalyst scripts !

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: Re: minimal install on usb key

[Chris Gianelloni]

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

On Tue, 2005-06-28 at 11:01 -0400, Christophe PEREZ wrote:
> Now, I can understand that we don't have identical environnement, and, as
> I wanted to have an up-to-date build, the only solution I found (bad, I
> know) was to remove one of the 2 packages. I choose ipw2100.

Actually, that is the only current course of action that is acceptable.

> In this example (livecd-stage1_template.spec), does options examples the
> defaults you used to build the iso ? Because, options are empty and it
> does not help me to begin.

The templates are documentation.  They are all empty on purpose, as you
are either supposed to fill them in yourself, after copying the template
to a spec file for your own use, or you remove the option if you do not
use it.  The documentation above each option is the important part.

> You will regret it ;-)

Not really.  If I get annoyed, I'll just quit answering and let other
members of the catalyst-hate group answer... :P

> Ok, I didn't know that.

I need to make that more apparent.

> > Honestly, the best way is via livecd/use, rather than a portage
> > configuration directory.
> 
> Ah, not portage_postdir anymore ?

portage_confdir...

> And, If I want a USE is used by only one package (for exemple a plugin for
> mozilla, but I don't want all packages with USE="mozilla") ?

This would require portage_confdir.  We don't use portage_confdir when
building releases, however.  I also personally dislike it, as it removes
the transparency of being able to give someone a spec file.

> Another question, important even if I forgot it before, what is the best
> way to modify some configuration files eg : /etc/fstab to mount nfs etc...
> ?

Use livecd/fsscript to add a shell script to be executed to perform any
additional tasks.  You can even use it for merging packages with crazy
USE flags... *grin*

> I don't think it is modifying catalyst scripts !

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Tue, 28 Jun 2005 11:27:05 -0400, Chris Gianelloni a écrit :

> Actually, that is the only current course of action that is acceptable.

Perfect ;-)

> The templates are documentation.  They are all empty on purpose, as you
> are either supposed to fill them in yourself, after copying the template
> to a spec file for your own use, or you remove the option if you do not
> use it.  The documentation above each option is the important part.

Yes, of course, but if I want YOUR specs (the one you used to build
livecd minimal), what have I to use ?
specs in livecd-ng OR options examples from templates doc ?

> Not really.  If I get annoyed, I'll just quit answering and let other
> members of the catalyst-hate group answer... :P

;-)
the latest possible (google's translation)

> I need to make that more apparent.

I think so...

>> Ah, not portage_postdir anymore ?
> 
> portage_confdir...

sorry.

>> And, If I want a USE is used by only one package (for exemple a plugin for
>> mozilla, but I don't want all packages with USE="mozilla") ?
> 
> This would require portage_confdir.

Ok.

> We don't use portage_confdir when
> building releases, however.  I also personally dislike it, as it removes
> the transparency of being able to give someone a spec file.

I think I can understand the difference now.

>> Another question, important even if I forgot it before, what is the best
>> way to modify some configuration files eg : /etc/fstab to mount nfs etc....
>> ?
> 
> Use livecd/fsscript to add a shell script to be executed to perform any
> additional tasks.  You can even use it for merging packages with crazy
> USE flags... *grin*

Ok, perfect.
Thank you for all.
I'll try to build now, so, I'll be back :-D

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: Re: Re: minimal install on usb key

[Chris Gianelloni]

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

On Tue, 2005-06-28 at 14:18 -0400, Christophe PEREZ wrote:
> Yes, of course, but if I want YOUR specs (the one you used to build
> livecd minimal), what have I to use ?
> specs in livecd-ng OR options examples from templates doc ?

livecd-specs are the actual spec files used to build the release.  The
templates are documentation used for YOU to build YOUR spec files.
You're more than welcome to start from the livecd-specs versions, but
the template versions are the documented ones.
-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: minimal install on usb key

[Christophe PEREZ]

Le Tue, 28 Jun 2005 14:36:03 -0400, Chris Gianelloni a écrit :

> On Tue, 2005-06-28 at 14:18 -0400, Christophe PEREZ wrote:
>> Yes, of course, but if I want YOUR specs (the one you used to build
>> livecd minimal), what have I to use ?
>> specs in livecd-ng OR options examples from templates doc ?

s/livecd-ng/livecd-specs/ of course

> livecd-specs are the actual spec files used to build the release.  The
> templates are documentation used for YOU to build YOUR spec files.
> You're more than welcome to start from the livecd-specs versions, but
> the template versions are the documented ones.

Ok.

2 questions :
1) how can I choose to had a package in stage1 ou stage2 ?
For example, with my actual building try, I put acx_100 in stage1, but, I
had an error because kernel wasn't already compiled, so I put it in stage2.
So, I would like to know how to decide without testing each package like
that.

2) I actually have an error in my build :
creating libtiff.la
/bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/libstdc++.la: No such file or directory
libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/libstdc++.la' is not a valid libtool archive
make[2]: *** [libtiff.la] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/tiff-3.7.2/work/tiff-3.7.2/libtiff'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/tiff-3.7.2/work/tiff-3.7.2/libtiff'
make: *** [all-recursive] Error 1

!!! ERROR: media-libs/tiff-3.7.2 failed.

I'm just trying to create a stage1 with xorg, firefox, xfce etc...
And, similar to first question, had I to put them in stage 2 ?

I had another error before, I add pkgconfig in stage1 packages and now it
seems ok.

thanks...

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: minimal install on usb key

[Chris Gianelloni]

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

On Wed, 2005-06-29 at 01:58 -0400, Christophe PEREZ wrote:
> 1) how can I choose to had a package in stage1 ou stage2 ?
> For example, with my actual building try, I put acx_100 in stage1, but, I
> had an error because kernel wasn't already compiled, so I put it in stage2.
> So, I would like to know how to decide without testing each package like
> that.

There isn't really any way to know.  However, a general rule of thumb is
drivers always go to livecd-stage2 (please use livecd-stage2, and not
stage2, as there *is* a stage2, and it is different... ;P)

> 2) I actually have an error in my build :
> creating libtiff.la
> /bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/libstdc++.la: No such file or directory
> libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/libstdc++.la' is not a valid libtool archive
> make[2]: *** [libtiff.la] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory `/var/tmp/portage/tiff-3.7.2/work/tiff-3.7.2/libtiff'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/var/tmp/portage/tiff-3.7.2/work/tiff-3.7.2/libtiff'
> make: *** [all-recursive] Error 1
> 
> !!! ERROR: media-libs/tiff-3.7.2 failed.
> 
> I'm just trying to create a stage1 with xorg, firefox, xfce etc...
> And, similar to first question, had I to put them in stage 2 ?

No.  It appears that you changed gcc versions from your stage3 seed
stage to your current.

If you update your snapshot before building a livecd-stage1, then it is
*always* a good idea to build stage1, stage2, and stage3 before building
your livecd-stage1.  This will reduce the number of errors you have from
mismatched perl, gcc, or python versions.

> I had another error before, I add pkgconfig in stage1 packages and now it
> seems ok.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Wed, 29 Jun 2005 09:24:38 -0400, Chris Gianelloni a écrit :

> There isn't really any way to know.  However, a general rule of thumb is
> drivers always go to livecd-stage2

ok !

> (please use livecd-stage2, and not stage2, as there *is* a stage2, and
> it is different... ;P)

Yes, it was to be quick.

> No.  It appears that you changed gcc versions from your stage3 seed
> stage to your current.

that's what I understood but didn't know how to correct.

> If you update your snapshot before building a livecd-stage1, then it is
> *always* a good idea to build stage1, stage2, and stage3 before building
> your livecd-stage1.

Ah !!!
I always saw examples using stage3 from mirrors.

>  This will reduce the number of errors you have from
> mismatched perl, gcc, or python versions.

So, I have to build 3 stages before livecd-stage1 ?
Oh !
still 3 specs to study :-(
I'll try that.


Thanks...

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

[gentoo-catalyst] Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Wed, 29 Jun 2005 11:39:14 -0400, Christophe PEREZ a écrit :

> So, I have to build 3 stages before livecd-stage1 ?
> Oh !
> still 3 specs to study :-(
> I'll try that.

Building, but, to build stage1, it is equal to use stage2 or
stage3 for 'source_subpath' ?

And, another problem I always had, my portage distfiles is on a nfs mount,
and in my /etc/make.conf, I have DISTDIR=/download/Linux/gentoo/portage.
All works fine with my normal system.

But, if I put this path in catalyst.conf : distdir, I can see that each
build downloads files (from internet) each time. (bind mount doesn't seem
to work on nfs, so directory is removed each time, so packages downloaded
again)

So, I had to use another path.
It works, all builds take their packages in it, but now, I have each
package 2 times on my system. One in the new catalyst distdir, and one in
my normal portage distdir (nfs mount).

I saw something like that in archives, but never understood if it could be
solved or not.
Does catalyst can't work with nfs mount ?

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: Re: minimal install on usb key

[Chris Gianelloni]

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

On Wed, 2005-06-29 at 13:29 -0400, Christophe PEREZ wrote:
> Le Wed, 29 Jun 2005 11:39:14 -0400, Christophe PEREZ a écrit :
> 
> > So, I have to build 3 stages before livecd-stage1 ?
> > Oh !
> > still 3 specs to study :-(
> > I'll try that.
> 
> Building, but, to build stage1, it is equal to use stage2 or
> stage3 for 'source_subpath' ?

Both will work, but I prefer a stage3 as a seed stage (source).  This is
simply because it has a complete environment.

> And, another problem I always had, my portage distfiles is on a nfs mount,
> and in my /etc/make.conf, I have DISTDIR=/download/Linux/gentoo/portage.
> All works fine with my normal system.
> 
> But, if I put this path in catalyst.conf : distdir, I can see that each
> build downloads files (from internet) each time. (bind mount doesn't seem
> to work on nfs, so directory is removed each time, so packages downloaded
> again)
> 
> So, I had to use another path.
> It works, all builds take their packages in it, but now, I have each
> package 2 times on my system. One in the new catalyst distdir, and one in
> my normal portage distdir (nfs mount).
> 
> I saw something like that in archives, but never understood if it could be
> solved or not.
> Does catalyst can't work with nfs mount ?

No clue.  I have no issues with it, but I mount the remote NFS mount
to /usr/portage on my build box.  I have no issues with the bind mount,
either.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Wed, 29 Jun 2005 13:53:44 -0400, Chris Gianelloni a écrit :

> Both will work, but I prefer a stage3 as a seed stage (source).  This is
> simply because it has a complete environment.

ok, that's what I took.

> No clue.  I have no issues with it, but I mount the remote NFS mount
> to /usr/portage on my build box.  I have no issues with the bind mount,
> either.

So, I'll try again...

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: Re: Re: minimal install on usb key

[Chris Gianelloni]

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

On Wed, 2005-06-29 at 22:19 -0400, Christophe PEREZ wrote:
> Le Wed, 29 Jun 2005 13:53:44 -0400, Chris Gianelloni a écrit :
> 
> > Both will work, but I prefer a stage3 as a seed stage (source).  This is
> > simply because it has a complete environment.
> 
> ok, that's what I took.
> 
> > No clue.  I have no issues with it, but I mount the remote NFS mount
> > to /usr/portage on my build box.  I have no issues with the bind mount,
> > either.
> 
> So, I'll try again...

Actually, you said that you have DISTDIR pointed to somewhere else?

Can you also try mounting the portage tree to your /usr/portage
directory.  The reason that I say this is because of bug #88488
(http://bugs.gentoo.org/88488).

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-catalyst] Re: Re: Re: Re: minimal install on usb key

[Christophe PEREZ]

Le Thu, 30 Jun 2005 09:50:42 -0400, Chris Gianelloni a écrit :

> Actually, you said that you have DISTDIR pointed to somewhere else?

Actualy (build running), I have exactly :
# grep -i distdir /etc/catalyst/* /etc/make.conf
/etc/catalyst/catalyst.conf:# distdir specifies where your distfiles are located. This setting should
/etc/catalyst/catalyst.conf:distdir="/sauve_loc/portage/distfiles"
/etc/catalyst/catalyst-env.sh:#export DISTDIR="/download/Linux/gentoo/portage"
/etc/make.conf:DISTDIR=/download/Linux/gentoo/portage

# grep /download /etc/fstab
nfs.novazur.fr:/autre/download /download nfs rsize=8192,wsize=8192,nosuid,nolock,intr 0 0

When you write "DISTDIR" I don't know if you talk about normal system
distdir, or catalyst distdir.

At my first tries of building with catalyst, I had :
/etc/catalyst/catalyst.conf:distdir="/download/Linux/gentoo/portage"

And all packages were downloaded for each build.

I tried adding :
/etc/catalyst/catalyst-env.sh:export DISTDIR="/download/Linux/gentoo/portage"
but didn't work better.

But, I wasn't familar with catalyst at this time.
Now, I'm sure my specs are fine, I'll try again an will able to give you
more informations.

> Can you also try mounting the portage tree to your /usr/portage
> directory.

I never thought to do that. I always mounted only distfiles

> The reason that I say this is because of bug #88488
> (http://bugs.gentoo.org/88488).

ok.

-- 
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Re: Re: Re: Re: minimal install on usb key

[Chris Gianelloni]

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

On Thu, 2005-06-30 at 12:58 -0400, Christophe PEREZ wrote:
> Le Thu, 30 Jun 2005 09:50:42 -0400, Chris Gianelloni a écrit :
> 
> > Actually, you said that you have DISTDIR pointed to somewhere else?

> Actualy (build running), I have exactly :

<snip>

I don't care.  It is pointed somewhere else, yes?  It doesn't matter
where it is pointed, so long as it is somewhere else, which is why I
asked if you had it pointed somewhere else, not where it was pointed. ;]

> > Can you also try mounting the portage tree to your /usr/portage
> > directory.
> 
> I never thought to do that. I always mounted only distfiles

Doesn't matter.

> > The reason that I say this is because of bug #88488
> > (http://bugs.gentoo.org/88488).
> 
> ok.

That bug says this:

Catalyst it broken.

If the distfiles directory is *not* located at /usr/portage/distfiles,
then it won't work.  It doesn't care how it gets there.  Bind mounts,
direct mounts, NFS mounts.  Catalyst simply doesn't care.

However, until the bug is fixed, it needs to be located there.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]