Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 150150 - kernel config not copied to chroot when using kerncache catalyst option
Summary: kernel config not copied to chroot when using kerncache catalyst option
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: GNAP (show other bugs)
Hardware: All Other
: High normal (vote)
Assignee: Gentoo Network Appliance Bugs
URL:
Whiteboard:
Keywords:
: 150151 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-10-05 02:30 UTC by Richard Scott
Modified: 2006-10-08 06:56 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Scott 2006-10-05 02:30:10 UTC
I've been able to create a LiveCD-Stage2 using GNAP and everything works fine if I do not use the 'kerncache' option in /etc/catalyst/catalyst.conf

I therefore do not believe that this is a GNAP issue, but a catalyst issue ;-)

I'll explain the steps I've been taking: 

1. Add the 'kerncache' option to my 'options' line in /etc/catalyst/catalyst.conf
2. Remove my /var/tmp/catslyst tree to start from fresh
3. run the gmap_make command with the same options as before.
4. sit back and wait a while.
5. After genkernel compiles my kernel (and even lists --kernel-config=/var/tmp/gentoo.config on the command line output) it complaines that I've no PCMCIA support in my kernel.

However, without the 'kerncache' option set, step 5 completes ok.

Using 'find' to look in /var/tmp/catalyst I can see that without the 'kerncache' setting the file is copied to:

livecd-stage2-x86-latest/var/tmp/gentoo.config

However with 'kerncache' set there is nothing found in the /var/tmp/catalyst/kerncache folders :-(
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-10-05 03:20:51 UTC
*** Bug 150151 has been marked as a duplicate of this bug. ***
Comment 2 Richard Scott 2006-10-08 06:56:54 UTC
ok, this seems to be a feature of the autoresume functions in Catalyst :-(

If you stop your build before catalyst has copied the kernel config to gentoo.config and don't remove the .autoresume folder then catalyst assumes that the kernel config file is there and does not copy the file across the next time it starts.

I guess you live and learn ;-)