J. Greenlees wrote:
> 8 hour build time? unless using the build scripts I don't think it's
> possible without brand spanking new hardware with massive amounts of ram.

ums.usu.ru (before it died in November, 2007 due to voltage spike): Pentium IV 
2.4 GHz (without hyperthreading), Intel S845WD1-E server board, 512 MB of RAM, 
120 GB IDE hard disk. Bought in May, 2003, not upgraded since then until the 
complete replacement in November, 2007. Able to build LFS LiveCD (the full 
version) in 12 hours. So we are not speaking about brand new hardware.

And the "8 hours" figure has the following origin: it's the maximum amount that 
we can realistically expect a typical desktop computer to stay on, so one 
doesn't have to bother with exiting and reentering the build environment (that 
is poorly documented in the book, probably because it is not supposed to be 
done).

>> Hard disk space is a mandatory requirement.
>> Disk requirement on IPCop is 2 GB free space before building.
>> Indicative minimal memory could be somewhere between 128 MB.
>> Recommended memory to build should more than 256 MB
>> I have mesured IPCop 1.4 (is with gcc-3.3) building time on the same machine
>> with 128 MB and 512 MB. 128 MB require 3 time more to build than with 512 MB
>> memory.

We are talking about a bit different things. The paragrapk above is talking 
about building gcc-3.3 based IPCop from itself - that's fine. But building 
gcc-4.x with gcc-3.3 triggers a known bug in gcc-3.3 that leads to huge 
consumption of memory (above 512 MB).

> and the learning opportunities for building on a more limited resource
> system are greater, you run into problems from the limitations.

Let me just throw your child into water and say "he learns swimming" (bad joke: 
I can't swim). No, learning must be gradual, the reader must see a trouble-free 
book first and _then_ experiment.

-- 
Alexander E. Patrakov
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to