| 1 |
On Thu, 06 Sep 2012 04:15:23 -0500, Dale wrote: |
| 2 |
|
| 3 |
> > You missed the point. One of the first thing emerge will do is to |
| 4 |
> > uncompress the package. At this time, all the files are cached in RAM. |
| 5 |
> > Hence, everything needed for the build/compilation will come from the |
| 6 |
> > cache like it would do with tmpfs. |
| 7 |
> > |
| 8 |
> |
| 9 |
> You miss this point not me. I *cleared* that cache. From kernel.org: |
| 10 |
|
| 11 |
Sorry Dale, but you are missing the point. You cleared the cache before |
| 12 |
running emerge, then ran emerge. The first thing emerge did was unpack |
| 13 |
the tarball and populate the disk cache. All clearing the disk cache did |
| 14 |
was make sure there was plenty of space to cache the new data, thus |
| 15 |
speeding up the process. |
| 16 |
|
| 17 |
|
| 18 |
-- |
| 19 |
Neil Bothwick |
| 20 |
|
| 21 |
"A snooze button is a poor substitute for no alarm clock at all." |
Archives