Ag. Hatzimanikas wrote these words on 02/15/07 13:50 CST: > I believe first we should know -and by the way,we should mention in the Book - > what we mean by "Build size".
It is just that. The size it takes to build and install the package. We don't normally count the tarball. Log sizes are insignificant. We don't normally count the tarball because there are too many intangibles. What if a user already has it in a central repo somewhere? What if they downloaded the .gz installed of .bz2 (as I do)? > And secondly,I noticed some people using df -k as described in the editor's > book > and some (our chief included) using du -skx,which these ways produce a > difference. > > Some kind of unification is needed,although the matter is minor. Are you sure there's really that much difference between them? I'd bet a coke that it is really, really insignificant. What I don't think you're factoring is that we are taking the *difference* between two numbers. And my bet is that the difference of those two numbers (be them derived from du or df) is not worth considering. Sure, du and df reports different numbers (slightly), but the fact is that providing you use du or df for both the before and after checks, you're going to get almost the same exact number. -- Randy rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 13:56:00 up 36 days, 14:10, 1 user, load average: 0.59, 0.42, 0.17 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
