Am Montag, den 29.08.2005, 14:24 -0400 schrieb Matt Randolph:
> I know that upgrading glibc can cause some programs to break if they
> were built against the previous glibc. This happens to me all the time
> and I have gotten in the habit of simply re-emerging any packages that
> misbehave since a glibc upgrade.
>
> Well, I have upgraded both glibc and gcc within the last week or so.
> And I've been contemplating a kernel upgrade too. I looked at genlop
> and it said it will take a mere fourteen hours to re-emerge everything
> with an emerge -e world. I'm tempted to do it, but I'm wary of making
> major changes to a system that currently seems to be working perfectly.
>
I don't think there's a simple yes or no answer to this problem. And I
am sure there's a lot of people who had their troubles with re-emerging
an entire system.
I myself did never experience any severe troubles. Recently I set up a
new test-server for combined file-, print-, mail- and web-services. I
fiddled around with PAM, LDAP and other stuff and decided three times
over the testing period to run an emerge --newuse -e world. We're
talking here something like 180 packages including Samba, CUPS, Courier,
Apache, PHP, PostgreSQL and X. Maybe I was lucky but everything went
just fine.
I believe that the cleaner you're system is the better chances are that
your system will survive an emerge -e. What's a clean system for me: a
system that does not show any signs of misbehaviour and that carries -
if at all - just a minimum of unstable packages safely defined
in /etc/portage.
On the other hand: if we are talking here about a productive system in a
multi-user environment then "Never touch a running systems" rules by all
means! ;-)
--
Mit freundlichen Grüßen
Heinz Sporn
SPORN it-freelancing
Mobile: ++43 (0)699 / 127 827 07
Email: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Website: http://www.sporn-it.com
Snail: Steyrer Str. 20
A-4540 Bad Hall
Austria / Europe
--
[email protected] mailing list
