| 1 |
On Fri, 2006-06-02 at 03:21 +0200, Dave Jones wrote: |
| 2 |
> Iain Buchanan wrote on 02/06/06 02:55: |
| 3 |
> > On Thu, 2006-06-01 at 20:28 -0400, Walter Dnes wrote: |
| 4 |
> >> 3) A vaguely related item... will it make any noticable difference if |
| 5 |
> >>I rebuild my kernel with gcc.3.4.5 and reboot at the end of the process? |
| 6 |
> >>I may as well upgrade the entire system. |
| 7 |
> |
| 8 |
> > If you've updated the rest of your system to 3.4.5, then do the kernel |
| 9 |
> > as well. Especially if you have proprietary modules, like vmware, |
| 10 |
> > ati-drivers, etc; or extra modules like ndiswrapper. Make sure you |
| 11 |
> > compile these modules after you compile your kernel, but before you |
| 12 |
> > reboot. |
| 13 |
> |
| 14 |
> VMWare is a problem, it looks at uname, so you can only update it to use |
| 15 |
> your latest kernel *after* a reboot. PITA. |
| 16 |
|
| 17 |
I assumed to OP was recompiling his kernel, not updating it ("if I |
| 18 |
rebuild my kernel with gcc.3.4.5"). In which case, vmware can be done |
| 19 |
before the reboot. |
| 20 |
|
| 21 |
I would recommend rebuilding with the new gcc, rather than updating and |
| 22 |
rebuilding at the same time, cause you may get other issues. So keeping |
| 23 |
to the same kernel will single them to gcc. |
| 24 |
|
| 25 |
-- |
| 26 |
Iain Buchanan <iaindb at netspace dot net dot au> |
| 27 |
|
| 28 |
QOTD: |
| 29 |
"Don't let your mind wander -- it's too little to be let out alone." |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-user@g.o mailing list |
Archives