Nelson Batalha | 1 Apr 2007 16:36
Picon
Favicon

Is this a bug?

Nelson said:
>Never crossed my mind to demand anything from a oss project ::P

Ok, that was a bit lost in translation lol, never mind.

So I managed to skip the emerge step, and now I'm having problems with the 
livecdstage2. While I try to figure out the code, I didn't want to post a 
bug in case I'm wrong:

* busybox: >> Configuring...
* busybox: >> Compiling...
* busybox: >> Copying to cache...
* initramfs: >> Initializing...
*         >> Appending base_layout cpio data...
*         >> Appending auxilary cpio data...
*         >> Appending busybox cpio data...
*         >> Appending unionfs_modules cpio data...
* UNIONFS MODULES: Adding support (compiling)...
* unionfs modules: >> Compiling...
make -C /usr/src/linux 
SUBDIRS=/var/tmp/genkernel/29716.20394.29631.11661/unionfs-1.4 
FISTDEVMK=/var/tmp/genkernel/29716.20394.29631.11661/unionfs-1.4/fistdev.mk 
modules
make[1]: Entering directory 
`/tmp/kerncache/gentoo/usr/src/linux-2.6.19-gentoo-r5'
Makefile:492: 
/tmp/kerncache/gentoo/usr/src/linux-2.6.19-gentoo-r5/arch/x86/Makefile: No 
such file or directory
make[1]: *** No rule to make target 
`/tmp/kerncache/gentoo/usr/src/linux-2.6.19-gentoo-r5/arch/x86/Makefile'.  
(Continue reading)

Andrew Gaffney | 1 Apr 2007 17:09
Picon
Favicon

Re: Is this a bug?

Nelson Batalha wrote:
> Makefile:492: 
> /tmp/kerncache/gentoo/usr/src/linux-2.6.19-gentoo-r5/arch/x86/Makefile: 
> No such file or directory
> make[1]: *** No rule to make target 
> `/tmp/kerncache/gentoo/usr/src/linux-2.6.19-gentoo-r5/arch/x86/Makefile'.  
> Stop.
> make[1]: Leaving directory 
> `/tmp/kerncache/gentoo/usr/src/linux-2.6.19-gentoo-r5'
> make: *** [unionfs.ko] Error 2
> * ERROR: failed to compile unionfs
> 
> More: http://rafb.net/p/hY41wN81.html
> 
> On my computer there isn't a dir called /usr/src/linux/arch/x86, only 
> i386 and x86_64 so is this a typo or this isn't supposed to be like a 
> normal kernel dir?

This is a known bug with the currently stable version of genkernel in the tree. 
For the release, we've got a newer version marked stable. You can either mark 
the newer version stable in your snapshot or remove --unionfs-dev from 
'livecd/gk_mainargs' in your livecd-stage2 spec file.

--

-- 
Andrew Gaffney                            http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer                                   Installer Project
Nelson Batalha | 2 Apr 2007 20:55
Picon
Favicon

Re: Is this a bug?

>This is a known bug with the currently stable version of genkernel in the 
>tree.

Thank you, once again I posted a warning in the wiki. After your mail I 
managed to make a few live minidvd's, and they were (in what catalyst was 
responsable :P) great!

However on my pc I couldn't pass the boot step. After losing much sanity I 
realized the livecd's catalyst now makes seem to think /dev/sdaX devices 
with a folder /livecd is The livecd. There is no customization I made that 
can cause this, however the release livecd's don't have this issue.

Couldn't find this bug (if so) posted. If so, you could add a file in the 
livecd overlay just for recognition (with version/code), for the new 
releases.

Cheers

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.com/

Chris Gianelloni | 2 Apr 2007 21:05
Picon
Favicon

Re: Some easy sugestions to implement, I hope

On Fri, 2007-03-30 at 16:32 +0000, Nelson Batalha wrote:
> You're very much right. Only I didn't demand anything cause right now I 
> don't the time to learn python and submit, I was just replying to the new 
> emails. Never crossed my mind to demand anything from a oss project :P, I 
> just wanted to know if it was ok&feasable.

Just for clarification, I never thought you were demanding anything.  As
for your idea, it is definitely feasible, but not something I would
*ever* want to implement.  As much as you say it would be useful, I see
it as a waste of *my* time, because it will encourage people to fiddle
with their caches, and those people will be coming here, asking for
help/support.  What this means is that so long as I not only develop,
but also *support* catalyst, I won't add anything that provides Release
Engineering with no additional useful functionality but only serves to
reduce my own availability for working on actual bugs.  As much as I can
see the needs of the casual/one-time user, I'm not designing a system
catered to them.  I think catalyst is too high of a learning curve
already for a casual/one-time user, so I'd rather teach them the "right"
way to go about using the tool if they have to do that much learning
already.

--

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
Chris Gianelloni | 2 Apr 2007 21:09
Picon
Favicon

Re: Is this a bug?

On Sun, 2007-04-01 at 10:09 -0500, Andrew Gaffney wrote:
> This is a known bug with the currently stable version of genkernel in the tree. 
> For the release, we've got a newer version marked stable. You can either mark 
> the newer version stable in your snapshot or remove --unionfs-dev from 
> 'livecd/gk_mainargs' in your livecd-stage2 spec file.

People using --unionfs-dev should be shot in the face at close range
with a nail gun.  It specifically states that it is broken and for
developer-use only.  It is known to be completely buggy and only works
when using the exact versions used by Release Engineering.  I'll likely
be removing this functionality entirely from genkernel simply because
I'm tired of the bug reports caused by it after I've stated it isn't
ready for use by pretty much anyone but myself.  ;]

I should state that explicitly.

"If your name is not Chris Gianelloni and you do not have commit access
to the genkernel repository, you should not be using --unionfs-dev for
any reason.  If you do, don't file bugs.  The real Chris Gianelloni
won't support you on them and will likely be pissed off by your blatant
impersonation attempts."

That should do it.  :P

--

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
(Continue reading)

Nelson Batalha | 2 Apr 2007 23:15
Picon
Favicon

Re: Some easy sugestions to implement, I hope

>Just for clarification, I never thought you were demanding anything.

Sure, I was replying someone else ;).

>As for your idea, it is definitely feasible, but not something I would
>*ever* want to implement.

I'm sorry I mentioned it, I thought, at the time, portage was giving me more 
problems then it actually was. In the end 5 new ebuilds did it, so no need 
for it at all.

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

Nelson Batalha | 3 Apr 2007 19:24
Picon
Favicon

Re: Is this a bug?

Nelson wrote:
>After losing much sanity I realized the livecd's catalyst now makes seem to 
>think
>my /dev/sdaX devices with a folder /livecd is The livecd.

On "targets/livecd-stage2/livecd-stage2-controller.sh":

"# Here is where we poke in our identifier
                touch $1/livecd"

If I add -${clst_livecd_type}-$2 (where $2 is the variable for the version 
stamp), where can the boot process be changed to look for this file?

Cheers

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

Chris Gianelloni | 3 Apr 2007 20:58
Picon
Favicon

Re: Is this a bug?

On Tue, 2007-04-03 at 17:24 +0000, Nelson Batalha wrote:
> Nelson wrote:
> >After losing much sanity I realized the livecd's catalyst now makes seem to 
> >think
> >my /dev/sdaX devices with a folder /livecd is The livecd.
> 
> On "targets/livecd-stage2/livecd-stage2-controller.sh":
> 
> "# Here is where we poke in our identifier
>                 touch $1/livecd"
> 
> If I add -${clst_livecd_type}-$2 (where $2 is the variable for the version 
> stamp), where can the boot process be changed to look for this file?

It's genkernel that looks for it, so you'd need to change genkernel.
That being said, such an identifier can not have anything variable in it
if you expect genkernel to find it.

--

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
Nelson Batalha | 3 Apr 2007 21:11
Picon
Favicon

Re: Is this a bug?

That's what I was afraid of.

But since you have a boot option called nox (no X), and the boot options are 
specified by catalyst, perhaps it's possible for catalyst to write a boot 
option on the build, saying the livecd signature/version and genkernel would 
read it and look properly. Lol, it's not important, but an idea for someone 
to pick later?

Btw, I'm writting new docs before I forget  
http://gentoo-wiki.com/HOWTO_build_a_LiveCD_with_Catalyst_%28alternative%29

>From: Chris Gianelloni <wolf31o2@...>
>Reply-To: gentoo-catalyst@...
>To: gentoo-catalyst@...
>Subject: Re: [gentoo-catalyst] Is this a bug?
>Date: Tue, 03 Apr 2007 14:58:17 -0400
>
>On Tue, 2007-04-03 at 17:24 +0000, Nelson Batalha wrote:
> > Nelson wrote:
> > >After losing much sanity I realized the livecd's catalyst now makes 
>seem to
> > >think
> > >my /dev/sdaX devices with a folder /livecd is The livecd.
> >
> > On "targets/livecd-stage2/livecd-stage2-controller.sh":
> >
> > "# Here is where we poke in our identifier
> >                 touch $1/livecd"
> >
> > If I add -${clst_livecd_type}-$2 (where $2 is the variable for the 
(Continue reading)

Chris Gianelloni | 3 Apr 2007 21:37
Picon
Favicon

Re: Is this a bug?

On Tue, 2007-04-03 at 19:11 +0000, Nelson Batalha wrote:
> But since you have a boot option called nox (no X), and the boot options are 
> specified by catalyst, perhaps it's possible for catalyst to write a boot 
> option on the build, saying the livecd signature/version and genkernel would 
> read it and look properly. Lol, it's not important, but an idea for someone 
> to pick later?

Uhh...

I'd rather not touch anything of the sort.  Passing things to genkernel
from catalyst isn't as easy as you think it is and the best solution is
likely the one we already have in place.

> Btw, I'm writting new docs before I forget  
> http://gentoo-wiki.com/HOWTO_build_a_LiveCD_with_Catalyst_%28alternative%29

Great.  =]

I do have to warn you that the Release Engineering staff does not
endorse *any* documentation placed on a public wiki of any kind.

I have been working on updating the official documentation, which is the
only thing that will be guaranteed to be even remotely correct.  The
last time I looked at the wiki, it told people to do really stupid
things, which is why I simply don't recommend using any documentation
not written by people intimately familiar with working with catalyst.

--

-- 
Chris Gianelloni
Release Engineering Strategic Lead
(Continue reading)


Gmane