Hello Phil, shouldn't we add something like "Before doing the Migration please upgrade to the most recent release". This would probably help to support issues that arise from the migration itself, as we have a "known good" base from where the migration is done (I know, you should always run the latest release. But I'd explicitly mention it again). Maybe upstream will fix at least some of the migration issues in the next update spin - at least if we tell them what issues are there. I know we don't support these migrations at all, but it would be great if there was a "Issues you'll probably run into"-section concerning problems that arise when you use "software X" and migrate. Like Gnome's usersettings, migration of evolution and firefox profiles, etc. We could also add a list of packages that makes CentOS 5 "compatible" to CentOS 4 binaries? There are compat-packages, but most people just think "why the hell did my software break? I know there a dependencies in RPM, but I also know that many people are running binary 3rd-party software and stuff dropped in /usr/local and /opt which is not managed with RPM. Some of these programs will probably stop working (glibc, libstdc++, ...), so we should provide information how to make a CentOS n+1 system as compatible as possible to CentOS n. Maybe with a list like "if you still want to run X you have to install Y" or maybe just "install compat-* we don't care". And we should probably also mention issues where you already use compat-libs on CentOS 4 and what will happen to them on an upgrade (I guess they'll stay in place, but in fact I don't have any idea what the upgrade-code will do) Regards, Andreas Rogge Phil Schaffner schrieb: > On Sun, 2007-03-25 at 22:11 +0100, Karanbir Singh wrote: >> Phil Schaffner wrote: >>> Please (particularly Smooge) review and comment on the new content at >>> >>> http://wiki.centos.org/HowTos/MigrationGuide >>> >>> Based heavily on the pieces I added earlier to >>> >>> http://wiki.centos.org/Migration/5 >>> >>> Tried to keep it general. > > Have yet to see any specific suggestions that would change the content > HowTos/MigrationGuide other than the previously discussed (emphasize > that fresh installs are STRONGLY recommended, only address x -> x+1 > upgrades). Will assume silence means consent pending further comments. > >>> Would assume that we want only one page on Migration with sub-pages for >>> specific versions. I referred to the CentOS 3 FAQ entry on WBEL >>> migration but it would seem to be cleaner to change the structure to >>> something like >>> >>> http://wiki.centos.org/HowTos/MigrationGuide/CentOS2 >>> ... >>> http://wiki.centos.org/HowTos/MigrationGuide/CentOS5 >>> >>> FAQ entries could point to the corresponding sub-pages. Opinions? >>> >> Phil, thanks for doing this stuff. >> >> I just want to confirm with you - what page are we going to link to from >> the centos-5-release notes ? > > Sorry for not trimming the post, but there's been a lot of wandering > already in this thread, so leaving the context. :-) > > My $0.02 would be that there should be 2 links in the centos-5-release > notes : > > 1. To the work-in-progress general page HowTos/MigrationGuide > 2. To the vaporware version-specific page HowTos/MigrationGuide/CentOS5 > [Where things like how to migrate from EL5 and friends, upgrade from > CentOS4, what to do about left-over packages (which can be a huge PITA > for desktop/workstation users, and are more likely to occur on a machine > with a bunch of 3rd party packages installed to support things like > browser plugins and multimedia) would reside.] > > Things like the content or the current WBEL 3 FAQ entry would move to > the corresponding sub-page when the concept is accepted and they are > created. > > Phil > > > _______________________________________________ > CentOS-docs mailing list > CentOS-docs at centos.org > http://lists.centos.org/mailman/listinfo/centos-docs > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3303 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos-docs/attachments/20070326/1c1b5b26/attachment-0004.bin>