I figured it would probably be something simple like this.  I will try that 'n' idea next but I can't use kernel 2.4 because it dosen't like my new hardware (Intel E7210 chipset P4) such as the E1000 hanging off the southbridge chipset etc.
The prepare log shouldn't matter since prepare exits cleanly, its build that it gets stuck on.  Theres no log besides prepare, unless its appending to it?
- Justin
Tim Tait <t.tait@comcast.net> wrote:

Like Heiko said logs would help. But I did have a similar problem in
1.1.x, when I checked the logs I realized that one of the lines was an
interactive prompt for new build option for one of the packages. Thus
entering "n" into the terminal that was running the build let it continue.


This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
Devil-linux-discuss mailing list

Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!