Status of kadischi ?

[Mike Kearey]

Hi all,

Am struggling to work out what is wrong with current kadischi (Most
recent from CVS).

I run the Live CD create command but it always bombs out at the end in
the livecd-mkinitrd.sh -

"/tmp/livecd-build_no11/system/lib/modules/None is not a directory."

A bugzilla exists https://bugzilla.redhat.com/bugzilla/show_bug.cgi?
id=169812   that matches what I am seeing. A friendly poster in that bug
seems to think it is anaconda's fault, that it indicates the kernel is
installed when it really is not. I have tried altering anaconda using
the changes indicated in the Bugzilla, however I see no difference..

I am using latest Fedora Core 4 packages ( yum update ), and
anaconda-10.2.1.5-2, all within a VMware machine if that is relevent.

What I really want to know is - Who has kadischi actually working ? If
so what version of anaconda ? What CVS version? What release of FC? Once
I know that I might track down the cause of the problem :)

Cheers,
Michael

P.S Here are tail of results from kadischi build:

making initrd image

  ***  Fatal error: /usr/local/share/kadischi/livecd-mkinitrd.sh
returned non zero (256) exit code. Aborting execution.

Cleaning up temporary files...
Done.


In anaconda logging I also see right after package dep checking :

* using freeglut-0:2.2.0-16.i386 to satisfy libglut.so.3
* failed to unlink /var/lib/rpm/__db.001: [Errno 2] No such file or
directory: '/tmp/livecd-build_no30/system/var/lib/rpm/__db.001'
* failed to unlink /var/lib/rpm/__db.002: [Errno 2] No such file or
directory: '/tmp/livecd-build_no30/system/var/lib/rpm/__db.002'
* failed to unlink /var/lib/rpm/__db.003: [Errno 2] No such file or
directory: '/tmp/livecd-build_no30/system/var/lib/rpm/__db.003'
* failed to unlink /var/lib/rpm: [Errno 21] Is a directory:
'/var/lib/rpm'
* moving (1) to step postinstallconfig


And 

* Running kickstart %post script(s)
* WARNING - Error code 256 encountered running a kickstart %pre/%post
script
* All kickstart %post script(s) have been run

[tony]

Le samedi 07 janvier 2006 à 17:12 +1000, Michael Kearey a écrit :

>  Am struggling to work out what is wrong with current kadischi (Most
>  recent from CVS). 
This was also broken on preceding version with custom kernels.

>  A bugzilla exists https://bugzilla.redhat.com/bugzilla/show_bug.cgi?
>  id=169812    
I have added my comment to that bug. This is a show stopper...

Tony
-- 
Tony Grant
www.tgds.net - vente d'ordinateurs mini-itx, hébergement: www.3continents.com -
international film festival |
www.chez-reine.com - gîte en Bretagne | www.haut-planty.com - Muscadet wine |
www.loire-estuaire.org - GIP Loire Estuaire

[Glen Eustace]

On Sat, 2006-01-07 at 17:12 +1000, Michael Kearey wrote:
>  What I really want to know is - Who has kadischi actually working ?
> If
>  so what version of anaconda ? What CVS version? What release of FC? Once
>  I know that I might track down the cause of the problem :) 
I am using it and it is ( mostly ) working fine for me. I am still using
the original. I have anaconda-10.2.1.5-2. I am building on FC4 but have
now successfully built an FC4 (kernel-2.6.12-1398) and an FC3
(kernel-2.6.9-1.667) LiveCD. I have a module that is kernel dependant so
have not bothered updating to newer kernel versions as it is a hassle
rebuilding the other module. Though I am keeping all other RPMS up to
date.

My goal is an appliance so I only needed a CD production tool that works
for me rather than something general. I have had to make numerous tweaks
to my customisations stuff which is why I haven't updated to a more
recent CVS version. My biggest problem is understanding EXACTLY what the
whole process is doing so that I can work/fix/optimise it. So far it has
all been trial and error. However, it is working and I am indebted to
those who built the tool as it has made my project a reality not just a
nice idea.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Glen and Rosanne Eustace,
GodZone Internet Services, a division of AGRE Enterprises Ltd.,
P.O. Box 8020, Palmerston North, New Zealand 5301
Ph/Fax: [phone], Mob: [phone], Web: www.godzone.net.nz

"A Ministry specialising in providing low-cost professional Internet
Services to NZ Christian Churches, Ministries and Organisations"

[J. Hartline]

Michael Kearey wrote:

> Hi all,
>
> Am struggling to work out what is wrong with current kadischi (Most
> recent from CVS).
>
> I run the Live CD create command but it always bombs out at the end in
> the livecd-mkinitrd.sh -
>
> "/tmp/livecd-build_no11/system/lib/modules/None is not a directory."
>   
>  
I just got around to getting a build system up over here again, and I 
*DO NOT* see this problem.
What I believe is you may be using packages, especially a kernel package 
that is updated.
If you deviate from the stock FC4 packages, you must use genhdlist, and 
pkgorder for it to work as planned.
Likewise doing this would in my eyes, require the old kernel be removed 
from the repository directory, unless installing both.

> A bugzilla exists https://bugzilla.redhat.com/bugzilla/show_bug.cgi?
> id=169812   that matches what I am seeing. A friendly poster in that bug
> seems to think it is anaconda's fault, that it indicates the kernel is
> installed when it really is not. I have tried altering anaconda using
> the changes indicated in the Bugzilla, however I see no difference..
>   
>  
That is a snippet of code from anaconda-devel-list a few months ago, as 
I said, I made absolutely no changes, I see no problems.

> I am using latest Fedora Core 4 packages ( yum update ), and
> anaconda-10.2.1.5-2, all within a VMware machine if that is relevent.
>   
>  
If you are deviating from the stock FC4 packages, please specify your 
utilities and packages in Fedora/base/comps.xml
and likewise, run genhdlist and pkgorder to reflect the changes also. I 
have /usr/lib/anaconda-runtime in my $PATH on the build machine here.

> What I really want to know is - Who has kadischi actually working ?
> If
> so what version of anaconda ? What CVS version? What release of FC? Once
> I know that I might track down the cause of the problem :)
>   
>  
Kadischi - Sunday January 8th (CVS)
Anaconda - 10.2.1.5-2
Fedora Core 4, stock packages.

> Cheers,
> Michael
>
>   
>  
I have been experimenting around with building rpms, need one?
kadischi.rpm anyone?

J. Hartline
jasperhartline(a)adelphia.net

[Mike Kearey]

On Sun, 2006-01-08 at 21:44 -0600, J. Hartline wrote:
>  Michael Kearey wrote:
>  
>  >Hi all,
>  >
>  >Am struggling to work out what is wrong with current kadischi (Most
>  >recent from CVS).
>  >
>  >I run the Live CD create command but it always bombs out at the end in
>  >the livecd-mkinitrd.sh -
>  >
>  >"/tmp/livecd-build_no11/system/lib/modules/None is not a directory."
>  >  
>  >
>  I just got around to getting a build system up over here again, and I 
>  *DO NOT* see this problem.
>  What I believe is you may be using packages, especially a kernel package 
>  that is updated.
>  If you deviate from the stock FC4 packages, you must use genhdlist, and 
>  pkgorder for it to work as planned.
>  Likewise doing this would in my eyes, require the old kernel be removed 
>  from the repository directory, unless installing both. 



What I have is a stock Fedora Core system fully updated with the latest
core packages with yum (ie the updates section for fc4). Note this is
the _build host_.

I have as install tree for the LiveCD build the original stock FC4
packages from the original CD spin...

I see that the build system is a little fragile right now. I shall
install a clean FC4 system, with no updates and see how that goes. I
shall also continue to work out what goes wrong on the current build
host I have been using. We need a build system that is less fragile I
think :)

CHeers.
Michael

[tony]

Le dimanche 08 janvier 2006 à 21:44 -0600, J. Hartline a écrit :

>  What I believe is you may be using packages, especially a kernel
> package 
>  that is updated. 
Yes

>  If you deviate from the stock FC4 packages, you must use genhdlist,
> and 
>  pkgorder for it to work as planned. 
of course

>  Likewise doing this would in my eyes, require the old kernel be
> removed 
>  from the repository directory, unless installing both. 
Yes doing all of the above.

Now what?

Tony
-- 
Tony Grant
www.tgds.net - vente d'ordinateurs mini-itx, hébergement: www.3continents.com -
international film festival |
www.chez-reine.com - gîte en Bretagne | www.haut-planty.com - Muscadet wine |
www.loire-estuaire.org - GIP Loire Estuaire

[Mike Kearey]

In case you were staying up late worried about this one, I have finally
managed to get a build system that _works_ :)

Here is the very specific recipe I used (Exactly and strictly following
the kadisci Wiki instructions) :

- Install FC4 original release from CD's ( NOT DVD && NOT yum updated ) 
- Installed the additional packages using yum ie 
	yum install anaconda busybox-anaconda syslinux mkisofs zisofs-tools
e2fsprogs kudzu-devel


Couple of things I did wrong it seems in my previous attempts:

- I used the DVD to install the base build system
- I installed the additional packages from the original CD's and not the
latest ones from yum


So current kadischi needs a clean original FC4 with no updates
installed. It also requires the the additional packages anaconda
busybox-anaconda syslinux mkisofs zisofs-tools e2fsprogs kudzu-devel to
be the latest available for FC4 ...

It seems to require a mix of original FC system plus specific updates
via yum to get a working build system. My next step is to work out what
specifically breaks the build system...

Cheers, 

-- 
Michael Kearey          Website:       http://apac.redhat.com
Red Hat Asia-Pacific    Disclaimer:    http://apac.redhat.com/disclaimer
Ph:    [phone]
Fax:   [phone]

[J. Hartline]

Michael Kearey wrote:

> In case you were staying up late worried about this one, I have
> finally
> managed to get a build system that _works_ :)
>   
>  
Excellent.

> So current kadischi needs a clean original FC4 with no updates
> installed. It also requires the the additional packages anaconda
> busybox-anaconda syslinux mkisofs zisofs-tools e2fsprogs kudzu-devel to
> be the latest available for FC4 ...
>
>   
>  
 From the sounds of it, if the CDs work Ok but the DVD doesn't, that 
would indicate something different in Fedora/base from the CDs
than the DVD.

[Chris Negus]

On Wed, 2006-01-11 at 01:56 -0600, J. Hartline wrote:
>  Michael Kearey wrote:
>   From the sounds of it, if the CDs work Ok but the DVD doesn't, that 
>  would indicate something different in Fedora/base from the CDs
>  than the DVD. 
I used the DVD, but I copied everything to hard disk first and it worked
okay.

-- Chris Negus

[Mike Kearey]

On Wed, 2006-01-11 at 08:45 -0600, Chris Negus wrote:
>  On Wed, 2006-01-11 at 01:56 -0600, J. Hartline wrote:
>  > Michael Kearey wrote:
>  >  From the sounds of it, if the CDs work Ok but the DVD doesn't, that 
>  > would indicate something different in Fedora/base from the CDs
>  > than the DVD.
>  
>  I used the DVD, but I copied everything to hard disk first and it worked
>  okay. 
Interesting. Maybe I have disk IO problems ..

Cheers,
-- 
Michael Kearey          Website:       http://apac.redhat.com
Red Hat Asia-Pacific    Disclaimer:    http://apac.redhat.com/disclaimer
Ph:    [phone]
Fax:   [phone]

[Skunk Worx]

Michael Kearey wrote:
>  
>  Couple of things I did wrong it seems in my previous attempts:
>  
>  - I used the DVD to install the base build system
>  - I installed the additional packages from the original CD's and not the
>  latest ones from yum
>  
>  
>  So current kadischi needs a clean original FC4 with no updates
>  installed. It also requires the the additional packages anaconda
>  busybox-anaconda syslinux mkisofs zisofs-tools e2fsprogs kudzu-devel to
>  be the latest available for FC4 ... 
I have built *many* custom boot dvd's with kadischi using the box stock 
FC4 DVD iso (mounted loopback, then shared, via a FC4 based http 
server), with a local yum update repo shared from the same box, using a 
kickstart script.

I've duped the system on two sets of servers (separate subnets/different 
hardware) and had great luck.

There was a time when the yum updates broke the initrd step but I 
haven't seen it for awhile.

There was a poster on the list who couldn't get anything to work, even 
though the same setup worked for me...I've always thought it was a 
deeper problem than kadischi (lowlevel hardware/software related).

---
SW

[Chris Negus]

On Sun, 2006-01-08 at 21:44 -0600, J. Hartline wrote:
>  Michael Kearey wrote:
>  If you are deviating from the stock FC4 packages, please specify your 
>  utilities and packages in Fedora/base/comps.xml
>  and likewise, run genhdlist and pkgorder to reflect the changes also. I 
>  have /usr/lib/anaconda-runtime in my $PATH on the build machine here. 
Is there any documentation available on the anaconda-runtime utilities?
Is vi the tool for modifying comps.xml? If someone can help me figure
out how to do it, I'd be glad to write up a procedure for incorporating
a custom set of packages into the build of a Fedora live CD. Thanks!

-- Chris Negus

[J. Hartline]

It is sort of funny you ask that, some RFEs have been getting filed on 
alot of these utilities, anaconda and yum alike.
They are excellent tools, I mean they work.
I suppose you could contact Jeremy Katz on anaconda-deve-list and ask him.

As far as comps is concerned, it is fairly easy.
Here is an example scenario..
You have KDE and Gnome. You can't install anything on that LiveCD after 
it has been spun.
You want Fluxbox? comps.xml is where you need to be.
 From start to end, you'll need to put fluxbox and all of it's deps into 
your repository.
Run pkgorder and genhdlist to reflect these changes.
Open up comps.xml (I'll leave alot of this research for you to do on 
your own, you could possibly contribute to the wiki?)
This sounds like a KadischiFAQ to me.

It is going to be like this pretty much: <group>
                                                                          
<id>GroupID</id>
                                                                          
<name language>Name</name>
                                                                          
<description>Small descriptional text</description>
For groups, you will have settings for <default>true</default> or false, 
depending on whether it should install, by default.
You will likewise have: <uservisible> which is just what it means. True 
or false.
<packagelist>
      <packagereq type="mandatory">foo</packagereq>
      <packagereq type="mandatory">bar</packagereq>
       <packagereq type="optional">foo-bar</packagereq>
    </packagelist>
  </group> (End of that Group.)

And thats it for a Group. Remember what your GroupID was you had set 
earlier.
Lets bounce to the bottom of comps.xml.
We have: <category> and <subcategory> we also have <grouplist> and 
<groupreq>.
You will use your <id>\\//</id> with these.
They go in a simple descending order. Groups, Categories with 
subcategories and Grouplists and GroupRequirements
and finally GroupHierarchies, such as Desktop, Workstation, Server, 
Everything and Minimal.

I'll leave the brainstorming to you. Don't forget to run pkgorder and 
genhdlist if you plan you use anything except Fedora Core
provided stock packages. If you put updates in your repositories, run 
these tools also. Things can and will change in packages.
This should help you get an idea of how Anaconda will devide things up.

J. Hartline

Ok. I hope this helps a bit.
Chris Negus wrote:

> Is there any documentation available on the anaconda-runtime
> utilities?
> Is vi the tool for modifying comps.xml? If someone can help me figure
> out how to do it, I'd be glad to write up a procedure for incorporating
> a custom set of packages into the build of a Fedora live CD. Thanks!
>
> -- Chris Negus
>
>
>   
>

[Chris Negus]

On Fri, 2006-01-13 at 07:15 -0600, J. Hartline wrote:
>  As far as comps is concerned, it is fairly easy.
>  Here is an example scenario..
>  You have KDE and Gnome. You can't install anything on that LiveCD after 
>  it has been spun.
>  You want Fluxbox? comps.xml is where you need to be.
>   From start to end, you'll need to put fluxbox and all of it's deps into 
>  your repository.
>  Run pkgorder and genhdlist to reflect these changes.
>  Open up comps.xml (I'll leave alot of this research for you to do on 
>  your own, you could possibly contribute to the wiki?)
>  This sounds like a KadischiFAQ to me. 
Okay. Thanks. I'll try it and document my steps for the Wiki.

-- Chris Negus

[J. Hartline]

Oh.. Do note, that if you add anything that Fedora Core maintainers 
wouldn't add, you aren't using a Fedora Core CD.
8-)

Chris Negus wrote:

> If someone can help me figure
> out how to do it, I'd be glad to write up a procedure for incorporating
> a custom set of packages into the build of a Fedora live CD. Thanks!
>
> -- Chris Negus
>
>   
>

[Chris Negus]

On Fri, 2006-01-13 at 07:16 -0600, J. Hartline wrote:
>  Oh.. Do note, that if you add anything that Fedora Core maintainers 
>  wouldn't add, you aren't using a Fedora Core CD.
>  8-) 
Actually, my main interest is in building in some Fedora Extras
packages. I'd like to petition the branding people to allow me to put
the Fedora Project logo on it. In other words, I wouldn't put anything
on the CD/DVD that wasn't under control of the Fedora Project. I figure
it doesn't hurt to ask.

The next best thing I would hope for is that the Fedora Project will
allow a branding that is like what the Debian project allows with their
"open use" logo for those who build stuff from Debian:

http://www.us.debian.org/logos/

I think this is the more honest approach, since it would acknowledge
that the CD is about 95% Fedora Core, but would let people know that it
is not officially recognized by the Fedora Project.

-- Chris Negus

[Rahul Sundaram]

Chris Negus wrote:

> On Fri, 2006-01-13 at 07:16 -0600, J. Hartline wrote:
>   
>
> >Oh.. Do note, that if you add anything that Fedora Core maintainers 
> >wouldn't add, you aren't using a Fedora Core CD.
> >8-)
> >    
> >
>
> Actually, my main interest is in building in some Fedora Extras
> packages. I'd like to petition the branding people to allow me to put
> the Fedora Project logo on it. In other words, I wouldn't put anything
> on the CD/DVD that wasn't under control of the Fedora Project. I figure
> it doesn't hurt to ask.
>
>   
>  
There is a plan to do just that. Pending counsel advise now. 
Fedora-marketing list might be a better place to discuss trademark 
guidelines.


-- 
Rahul 

Fedora Bug Triaging - http://fedoraproject.org/wiki/BugZappers

[J. Hartline]

Chris Negus wrote:

> Actually, my main interest is in building in some Fedora Extras
> packages. I'd like to petition the branding people to allow me to put
> the Fedora Project logo on it. In other words, I wouldn't put anything
> on the CD/DVD that wasn't under control of the Fedora Project. I figure
> it doesn't hurt to ask.
>   
>  
I'm not absolutely sure who to talk to about something like that..
I think you might contact Karsten Wade with Redhat, Inc.

J. Hartline

[Jeremy Katz]

On Thu, 2006-01-12 at 22:44 -0600, Chris Negus wrote:
>  On Sun, 2006-01-08 at 21:44 -0600, J. Hartline wrote:
>  > Michael Kearey wrote:
>  > If you are deviating from the stock FC4 packages, please specify your 
>  > utilities and packages in Fedora/base/comps.xml
>  > and likewise, run genhdlist and pkgorder to reflect the changes also. I 
>  > have /usr/lib/anaconda-runtime in my $PATH on the build machine here.
>  
>  Is there any documentation available on the anaconda-runtime utilities?
>  Is vi the tool for modifying comps.xml? If someone can help me figure
>  out how to do it, I'd be glad to write up a procedure for incorporating
>  a custom set of packages into the build of a Fedora live CD. Thanks! 
Yes, the comps file is intended to be edited with a text editor.  See
http://fedora.redhat.com/projects/anaconda-installer/comps.html for a
write up about the FC4 and earlier comps file.  There's also a fair bit
of information under http://fedoraproject.org/wiki/Anaconda  For FC5,
some things have changed and I need to write them up, but actually
making things work for FC5 is currently higher priority. :-)

Jeremy