1 |
On 21/02/08 05:40, Chris Gianelloni wrote: |
2 |
> On Wed, 2008-02-20 at 21:38 +0100, lurker wrote: |
3 |
>> genkernel fails to add busybox with cpio (this is with genkernel-3.4.9 |
4 |
>> and catalyst-2.0.6_pre6): |
5 |
> |
6 |
> Please try catalyst-2.0.6_pre8, which is pretty new and should work just |
7 |
> fine for whatever you need. Also, check out genkernel-3.4.10_pre3, |
8 |
> which I literally just added to the tree. |
9 |
> |
10 |
>> Also, my system runs stable amd64 Gentoo, but I run catalyst in a i686 |
11 |
>> chroot to protect my main system. Could that have anything to do with this? |
12 |
> |
13 |
> Ehh, this very well could be causing you all kinds of problems. |
14 |
|
15 |
Alright, but what (and why) exactly? I used this setup flawlessly for |
16 |
months before this error came out of nowhere. I'm not sure what I did |
17 |
for it to start appearing in the first place. |
18 |
|
19 |
> Since catalyst does all of its building in "storedir" |
20 |
> or /var/tmp/catalyst, by default. In fact, it won't do anything outside |
21 |
> of /var/tmp/catalyst, and then each target is built in a chroot, also. |
22 |
> So, building a typical package with default settings, you end up |
23 |
> extracting to /var/tmp/catalyst/tmp, then chrooting into there, before |
24 |
> anything else is done. |
25 |
> |
26 |
> Again, it is safe to run on your main install. The only files it cares |
27 |
> about from your running system are all in /etc/catalyst |
28 |
> or /var/tmp/catalyst and nowhere else, unless you configure it to do so. |
29 |
|
30 |
When I set up that chroot I didn't know that catalyst was able to |
31 |
generate x86 stages from amd64 systems, so that was my reason for |
32 |
creating it. I will install catalyst and genkernel on my main system |
33 |
instead and work from there, and if that fails upgrading to the latest |
34 |
versions. |
35 |
|
36 |
But even if that fixes it, I would very much like to know what was going |
37 |
on. From my debugging I have pretty much confirmed that it's that |
38 |
find/cpio call that fails, but I cannot grasp why at all. Few bugs have |
39 |
left me this perplexed. |
40 |
|
41 |
-- |
42 |
gentoo-catalyst@l.g.o mailing list |