> I agree for "586-class computers with only 16 MB" would give bad result if
> any.
> I have build IPCop in the past on a 586-class laptop with 160 MB memory in
> approximatly three days.
>   
well, an i586 with 128 mb ram and a total hd space of 3 GB took 3 days
just for pass1 of chapter 5 with a recent build I did. [36 hours just
for gcc to build]


>> P.S. I accept the challenge to "try that with a regular distribution".
>>
>> Proposal:
>>
>> 1) Remove this advertisement.
>>
>> 2) List hardware requirements (CPU, RAM, hard disk space) on the same page
>>     
> as
>   
>> software host requirements, or immediately before it.

Good idea.
>>  These requirements
>>     
> should
>   
>> be set so that the total build time (including all testsuites) is less
>>     
> than 8
>   
>> hours, and that the build process never needs to get into swap (the worst
>>     
> case
>   
>> seems to be Chapter 5 gcc Pass1 when starting from a host that is based on
>>     
> gcc-3.3).
>   

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.
> 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.
>
> Time should not be a requirement but a guide line.
> Just say it take x time with this cpu, memory and disk.
>
>   

good point.
> We all know the problem with heavy swap usage but it may happen a small part
> goes permanently in swap without a big slowdown. This happen to me on alpha
> (160 MB memory).
> Until that part remain permantly in swap, this is not a problem.
>   
and the learning opportunities for building on a more limited resource
system are greater, you run into problems from the limitations.
 Even though the direction seems to be to make LFS more a build your own
distro guide, the learning aspect can't be ignored.

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

Reply via email to