On Nov 26, 2011 12:05 AM, "微菜" <micro...@fedoraproject.org> wrote: > > 于 2011年11月24日 15:34, justin 写道: > > On 24/11/11 06:27, Paul Hartman wrote: > >> Hi, > >> > >> After emerging glibc-2.14.1 today, pam stopped working, which > >> prevented KDE from working and some other things. I got this kind of > >> message: > >> > >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by > >> /lib64/libcrypt.so.1) > >> > >> There were no @preserved-rebuild and revdep-rebuild found nothing. I > >> rebuilt pam and things seem to be working again. Are there any other > >> packages I should rebuild before encountering a problem? Or some way > >> to detect which need to be rebuilt? Should I re-emerge world against > >> my new glibc? :) > >> > >> Thanks, > >> Paul > >> > > > > Hi Paul, > > > > after an glibc upgrade it is time to do an > > > > emerge -e system world > > you must be kidding me . it will take days to complete. >
On my virtualized servers, emerge -e @system @world, a total of 170-something packages, takes only about 6-7 hours. Remember, these are VMs, which means the 2 vCPUs I assigned them are actually shared with other VMs. On a non-virtualized system, should be faster. Of course, if you have sizable packages, it might take around 24 hours to complete. Rgds,
