> The painful part of a fresh
> install is making sure I had those mysql db's backed up recently too,
> and the apache configs, and that php.ini and the system-wide settings
> for vim, and the postfix configs, and the cron jobs, and the ... on and on.
I can't comprehend why people are doing fresh installs. Unless you're
changing distributions continuously (like trying new things?)
I can even remember the last time I did a fresh install on my home
computer, through all kinds of upgrades. Its quite possible my
machine is still the same one from slink or potato. I recall a
hardrive failure five to seven or so years ago - but I don't recall if
I lost the OS or just user data ( I remember having to re-rip a lot of
music...)
> Anyone got some great tricks to deal with this? I've actually found
> dist-upgrades to be the best upgrade... sometimes.
Thats all I do. Though I do it so rarely (ex last time I upgraded it
was using unstable, but so old stable was more recent) means I'm
always in unsupported dist-upgrade land. However that has led to a
great knowledge on how all the bits in an upgrade work and leave very
little fear of typing in 'Yes, do as I say!' to make things work
again. It also means I've often downgraded the entire OS, which is
very messy.
So that means I don't have any tricks for migrating /etc to a new
machine. What you might be able to do it get dpkg to make a report as
to what rc files you've changed, then you just back those up. When
you have a new install, you merge those files into the new /etc.
Migrating everything else (/var, /usr/local/) it usually just a matter
of copying the files across.
Received on Wed Mar 19 11:35:40 2008
This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 11:35:42 CST