| 1 |
Kwon kirjoitti: |
| 2 |
> Just did the following to upgrade a system that was built about 6-9 |
| 3 |
> months ago: |
| 4 |
> |
| 5 |
> emerge --sync && emerge os-headers glibc binutils gcc && emerge |
| 6 |
> os-headers glibc binutils gcc && emerge -e system && emerge -e system && |
| 7 |
> emerge -uD world && emerge --update --newuse --deep --buildpkg world && |
| 8 |
> emerge -v depclean &&revdep-rebuild -v && revdep-rebuild –v |
| 9 |
> |
| 10 |
> Q1. Can someone please have a look (and perhaps comment) on the above? |
| 11 |
|
| 12 |
You are unnecessarily polluting your world file. use emerge -1 |
| 13 |
In general that is way too much recompiling to my taste. If you are |
| 14 |
upgrading your compiler, just following the gcc-upgrade guide should be |
| 15 |
fine. |
| 16 |
|
| 17 |
> Q2. Kernel upgraded from hardened-sources-2.6.16-r11 to |
| 18 |
> hardened-sources-2.1.18 during the above process, can one use the old |
| 19 |
> .config file to compile the new kernel? |
| 20 |
|
| 21 |
You need to use make oldconfig with the old .config file. |
| 22 |
|
| 23 |
Regards, |
| 24 |
Petteri |
Archives