[SATLUG] Upgrade Fedora core 3 to core 6

Sat Dec 2 16:29:12 CST 2006

On Sat, December 2, 2006 2:28 pm, tweeks wrote:
> On Saturday 02 December 2006 04:48, Luis Garza wrote:
> [...]
>>
>> So I am asking for any lessons learned while upgrading.
>
> Many of us here have done this many times Luis...  And Tthere are a dozen
> different ways to do it.  Here's a the "manual method" that I recently
> used
> in a laptop upgrade:
>
> Example: You have a desktop with some mysql database content and /etc
> based
> config files that you want to save, along with your home dir content.
>
[...]

> 6) copy backup tarball back onto /home/BACKUP and untar it:
> 	# mkdir -p /home/BACKUP ; cp BACKUP-2006-12-02.tgz /home/BACKUP/
> 	# cd /home/BACKUP/ ; tar xzvf BACKUP-2006-12-02.tgz
>
[...]
OK I rsync-ed the /root /etc /var /home directories to another machine.
I know that I got too much but its just a backup.

[...]

> you fine that something doesn't work like it used to (e.g. Your Kmail
> filters
> and accounts are all lost), then research and copy each over individually.
> For example, for Kmail filters and accounts, they are all kept
> in .kde/share/config/kmailrc, which MAY be copied over after you've
> determined you need it and that you won't mess up your new environment.

I use squirrelmail for my mail reader but I have alot of plugins.  So now
I have to backup the /usr/share/squirrelmail/plugins directory.  I am
purty sure that they will work with the latest version of squirrelmail. 
So I think that I can restore those.

I also need to make sure that I have every users /home/[user]/mail
directory.  It appears that is where squirrelmail creates the users'
subfolders.  That will need to be restored.

I am also thinking about backing up and restoring my spamassasin .cf files
in the /usr/share/spamassassin directory.

Also each users' /home/[user]/.spamassasin directory will need to be
backed upped and restored.  It contains the users' whitelist and
user_perfs.

Funny, I just noticed that I have not installed clamav - sorry windows users.

It appears that I need to backup each users' /home/[user]/* regular files
and directories minus the Desktop.  I will let the system recreate that. 
Just restoring the /home/[user]/* files should exclude the .files and
.directories.

I may want to restore the user's bashrc files; /home/[user]/.[a-zA-Z]*bash*

I am thinking about NOT restoring the samba /usr/share/system-config-samba
directory and just try to recreate the share by just restoring the
/etc/samba directory.  Any takers on why the
/usr/share/system-config-samba directory has some python files that get
updated?

As for sendmail, I think that I need to
  o  restore /etc/mail/access file.  I will let it recreate the access.db
file.
  o  restore /etc/mail/auth/client-info file.
  o  I will need to make sure that
       FEATURE(`authinfo',`hash /etc/mail/auth/client-info')dnl
       makemap hash client-info < client-info
       define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5
LOGIN PLAIN')dnl
       define(`SMART_HOST',`SMTP.sbcglobal.yahoo.com')
       MASQUERADE_DOMAIN(luisgarza.com)dnl
     will be in the new sendmail.mc file.
  o  restore /etc/mail/spamassasin/local.cf file
Any additional advice on sendmail would be greatly appreciated!!!

As for mailman, I think that I need to
  o  restore the /etc/aliases file
  o  restore the /var/lib/mailman directory
  o  restore the /etc/cron.d/mailman file

As for the mrtg, I think that I need to
  o  restore the /etc/snmp/snmpd.conf file
  o  restore the /etc/cron.d/mrtg file

As for my domains, I think that I need to
  o  restore /root/bin/zone* files
  o  check out  http://ipcheck.sourceforge.net/
  o  restore /etc/cron.daily/zoneedit

As for my apache2, I think that I need to
  o  restore /etc/httpd/conf/httpd.conf file
  o  restore /etc/httpd/conf.d/mrtg file
  o  restore /etc/httpd/conf.d/awstats file
  o  restore /etc/httpd/conf.d/webalizer file

As for my awstats, I think that I need to
  o  restore /var/lib/awstats directory
  o  restore /etc/awstats directory
  o  restore /etc/cron.hourly/awstats

As for my webalizer, I think that I need to
  o  restore /var/lib/webalizer directory
  o  restore /etc/webalizer file

Selectively restore lines from the
  o  /etc/password,
  o  /etc/shadow
  o  /etc/group files
  o  /etc/cron.allow
  o  /var/spool/cron/root
  o  /etc/hosts ( I have alot of ad site pointing to 127.0.0.1 )

OK ... Thats what I got so far.  I still need to look at the plugins for
firefox, thunderbird, wordpress ...

I am going to

  o  Take a break
  o  Take a shot of wiskey
  o  And go to church and light a candle

I will add more as I think of it.

PLEASE feel free to comment and remind me of other thinks that I need to
restore, reconfigure, or just plan do from scratch.

PS: Dr. Dubbs and those who moved the satlug server to Rackspace ... WOW

>
> NOTE: You probably set up your first/only around install time.  But if you
> did
> not, or you have additional users, jump ahead and step12 and then back
> here.
>
> 8) You can copy over some of your "dot files" (usually) such
> as .ssh, .mozilla, .gaim, .evolution, etc.  Some apps like ssh shouldn't
> matter.. other apps like evolution might detect old config files and offer
> to
> upgrade them (if needed)... However, be sure to to pay attention to
> potential
> conflicts such as mozilla plugins and the like.
>
> 9) After moving home user content back into place, verify that the UID
> GID's
> still match.  This can be fixed (if they don't match) like this:
> 	# chown -R user1:user1 /home/user1
>
> 10) Copy your database back into place:
> 	# cp -a /home/BACKUP/mysql/* /var/lib/mysql
>
> NOTE: There are diffs between major versions of MySQL and other DB version
> table types.  You need to look into best handle these differences for you
> DB
> or application.
>
> 11) Copy important config files back into place, allowing for backups to
> be
> made of all original files:
> 	# cp -ab /home/BACKUP/etc/hosts /etc/hosts
> 	# cp -ab /home/BACKUP/etc/sysconfig/iptables /etc/sysconfig/
>
> WARNING: Never just blindly copy old key daemon config files over the new
> ones
> (such as /etc/my.cnf, httpd.conf, vsftpd.conf, sendmail.{cf,mc}, etc.  New
> daemons mean new/different features.  Plopping an old config file over top
> a
> newer one can cause big problems.  Individual settings from old config
> files
> need to be researched and moved over to the new files line by line.
>
> 12) Things like users and groups should usually be recreated on the new
> system
> instead of just being moved over.  If you're upgrading between different
> distros or even UN*Xes... their settings and internal conventions may vary
> quite a bit.
>
> 13) Have your users log in and start up their applications and check to
> verify
> that everything is operating correctly.  If everything's ok.. then clean
> up
> the untarred backup files in /home, but keep the tar backup file on the
> system for a few months just in case.
>
>
> wow.. I didn't intend to write all of this.. but I've been meaning to jot
> a
> lot of this down in note form for a while now.  And now having done so..
> I'm
> sure that others will now add toit , change and refine it.
> Sounds like a good candidate for the WiKi.. :)
>
> Tweeks
> --
> _______________________________________________
> SATLUG mailing list
> SATLUG at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug to unsubscribe
> Powered by Rackspace (www.rackspace.com)
>

Luis Garza
www.luisgarza.com
luis at luisgarza.com
lrgarza2000 at yahoo.com