Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 98806 - Genkernel 3.2.1 doesnt boot since bug fix 98501
Summary: Genkernel 3.2.1 doesnt boot since bug fix 98501
Status: VERIFIED FIXED
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: genkernel (show other bugs)
Hardware: All Linux
: High critical (vote)
Assignee: Gentoo Genkernel Maintainers
URL: http://www.xnfo.org/temp.png
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-12 13:16 UTC by Michiel Hazelhof
Modified: 2005-07-13 06:51 UTC (History)
0 users

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 Michiel Hazelhof 2005-07-12 13:16:21 UTC
Bugfix 98501 (http://bugs.gentoo.org/show_bug.cgi?id=98501) bloks my livecd from
booting, after removing this line it boots fine.

It just stops with;

>> copying read-write image contents to tempfs

The line is 208;
                chmod 755 ${NEW_ROOT}/$i

After removing it works fine.

I have tryed rebuilding the livecd and kernel a few times, this is the blocker.


Reproducible: Always
Steps to Reproduce:
Just make the genkernel, and boot it from a livecd
Actual Results:  
The livecd wouldnt boot any more

Expected Results:  
Done something to make it boot or at least show an error.
Comment 1 Eric Edgar (RETIRED) gentoo-dev 2005-07-12 14:50:48 UTC
which version of catalyst are you using.

please upgrade to higher than 1.1.10 if you havent already?
Comment 2 Michiel Hazelhof 2005-07-12 22:39:11 UTC
I do not use catalyst, because I think it sucks.

I use http://gentoo-wiki.com/HOWTO_build_a_LiveCD_from_scratch which I partialy
wrote because this is much more flexible, and I get a cd which is still able to
compile loads of stuff from its own.
Comment 3 Michiel Hazelhof 2005-07-12 23:25:46 UTC
Works for some reason again with 3.2.2
Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2005-07-13 06:51:54 UTC
Look slike it was a local configuration issue with your system, probably from
using something other than catalyst to build.  Amazing how people can criticize
then don't even bother to contribute to make something better.