updating 4.3 to 4.4Forum: DSL Tips and Tricks Topic: updating 4.3 to 4.4 started by: Big_Pc_Man Posted by Big_Pc_Man on Jan. 15 2008,23:34
Could someone please remind me what is the least disruptive way to upgrade 4.3 to 4.4 or more generally from one point release to another. I have several configuration files I seem to have to manually update each time I upgrade. They are all in the backup tar but I never could quite figure out the rules for applying the backup after installing a new system using the app/tool/install function for a usb system. The new install will of course reformat the entire usb stick so the original backup is no longer present. What happens if I backup the backup tar and move it back to the sda1 space overwriting the newly created backup tar? Another issue is that I run the /opt directory out of a separate USB stick since my web server is in the /opt directory. How do I know from one release to the next whether any /opt files have changed?
Posted by mikshaw on Jan. 15 2008,23:37
When Robert posts a release, he also posts the files that are most likely to be affected by the new release.If you happen to have a file in your backup that overwrites a changed file, it can be compared to /etc/skel/whatever Posted by Big_Pc_Man on Jan. 15 2008,23:48
Let me get this straight. Are you saying a new file is created called /etc/skel/whatever if a new release file is overwritten by a backup restore?Regarding the new release post: -------------------- Change Log: * Changed French default keytable from fr to fr-latin1 * Fixed .dfminfo for pppdial, pon, poff needed missing sudo * Recompiled and reinstalled ndiwrapper. * Updated some icons Files likely in your backup: .jwmrc .dfminfo --------------------------- So would the procedure be to simply compare the above mentioned files to the backup files if present and if no changes are found use the original backup tar with confidence? Posted by mikshaw on Jan. 15 2008,23:57
No. /etc/skel is a directory that contains all of the default files that are in /home/dsl when you start a clean system. If you backup/restore these files, the ones in /etc/skell can be used to either replace new files that no longer work or compare to your own config files if you need to make some changes.
Posted by Big_Pc_Man on Jan. 16 2008,00:04
OK, i see what you mean. I think my problems are going to be mostly in /opt. Things like .filetool.lst, bootlocal.sh and crontab. I would have to look around for more examples but there are files that are not in /home that I'm worried about.
Posted by jpeters on Jan. 22 2008,08:53
Right....and probably all are listed in .filetool.lst. My method is to: 1. create a copy of my backup file ( to make sure it doesn't get overwritten)....if you have a server, do a webbackup. 2 record bootcodes ("showbootcodes") 3. load fresh with dsl norestore 4. copy files as desired from backup 5. restore webbackup Maybe someone has a better way; but this has worked for me. |