| 1 |
On Wed, Jun 30, 2010 at 7:48 AM, Shoka <shoka@×××.ch> wrote: |
| 2 |
> On 30.06.2010 15:56, Mark Knecht wrote: |
| 3 |
> |
| 4 |
>> |
| 5 |
>> /usr/src could be reduced to one source tree. |
| 6 |
>> |
| 7 |
>> HTH, |
| 8 |
>> Mark |
| 9 |
>> |
| 10 |
> |
| 11 |
> Hi Mark, |
| 12 |
> |
| 13 |
> Unfortunately I don't fully understand. What do you mean by "reducing to |
| 14 |
> one source tree"? |
| 15 |
> |
| 16 |
> Regards |
| 17 |
> andré |
| 18 |
> |
| 19 |
> |
| 20 |
|
| 21 |
Hello Andre, |
| 22 |
OK - I think others have explained that if you have ever had more |
| 23 |
than 1 kernel on the machine then you may still have old source code |
| 24 |
trees. Get rid of the ones you aren't using. |
| 25 |
|
| 26 |
Related but not a lot of diskspace - don't forget to clean up any |
| 27 |
unused module directories for kernels no longer on the system. |
| 28 |
|
| 29 |
Others noted Gnome. I find XFCE to be 98% the same user experience |
| 30 |
for 15% of the build time. I expect you would find it very reasonable |
| 31 |
as a Gnome user. I've used fluxbox and it's great, but it's very, very |
| 32 |
different and may be more of a change than you want to deal with. |
| 33 |
|
| 34 |
Sorry on the distfiles suggestion. When I reread your post I |
| 35 |
finally saw that you had already taken care of that. |
| 36 |
|
| 37 |
One related thing is that should an ebuild die portage often leaves |
| 38 |
behind big build directories of the work it was doing. They can be |
| 39 |
cleaned up also. Look for the word 'work' or 'WORK' where code gets |
| 40 |
built. |
| 41 |
|
| 42 |
Look at log file sizes. They can grow over time. Some tools that |
| 43 |
create log files can limit there sizes or there are ways to compress |
| 44 |
and rotate if that suits your needs. |
| 45 |
|
| 46 |
I suspect your biggest immediate win after distfiles would be with |
| 47 |
XFCE. (and emerge -C gnome) |
| 48 |
|
| 49 |
Good luck, |
| 50 |
Mark |
Archives