Re: [SLUG] upgrade 6.2 -> 7.0
>I did this last night to ensure I was up to date and it was a pain. Is there >a file somewhere that tells you all the things that are going to break when >this is done? Here are some of the things that broke: It sounds like your experience was even worse than mine. I upgraded one desktop box and all went well, as far as I could tell. So, I upgraded my two laptop machines ... the one I carry around and an older one that I keep in the lounge room for surfing the net in ad breaks. Of course, neither of those upgrades was anywhere near as easy. The main issue I came across was that for some reason the upgrade didn't seem to take into account that I had separate /usr partitions on each of those machines, so it kept telling me I needed a heap more disk space on /. I ended up having to do a brand new install ... without needing to repartition or change what items I wanted to have installed! after backing up any precious data. That was very, very annoying. Overall, though, after getting the machines back up and running I'm fairly happy with 7.0. For example, I can now use my USB mouse, which was probably possible with 6.2, except that it would have required patching and mucking around. My systems tend to be pretty simple, because all I use them for is hacking code, so I never hit the apache, squid, pppd etc, problems you had. I'd probably be totally bald by this point if I had :-). Hope it all works out in the end. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
[SLUG] upgrade 6.2 -> 7.0
> > You can upgrade RH6.2 to RH7.0 in a number of ways. > > My preferred way (to do any upgrade) is to obtain a CD rom and run it > > from the CDrom. You can either buy this (cetustech or everythinglinux) > > or download the iso and burn a CD. I did this last night to ensure I was up to date and it was a pain. Is there a file somewhere that tells you all the things that are going to break when this is done? Here are some of the things that broke: Squid - squid now has an additional parameter for cache_dir so it would not run until I figured this out. Apache - httpd refuses to run because it can't find a module for php3 etc. I'd bet it won't work with FrontPage any more either (as my previous version did) but I haven't had time to deal with that one yet. pppd - The pppd deamon required a slightly different syntax so I was offline for quite a while. For some reason it could not obtain the local ip address although I am supplying it from the command line. Removing the parameter "auth" seemed to fix this. NFS - I thought I had this disabled but I'm still getting an error about "NFS lockd" error 111 and portmap on startup that makes no sense to me so I'm off to research that. ip forwarding - Stopped working which prevented a script I have for ipchains from running properly in spite of having this listed in /etc/sysconfig/network. I've had to switch this on by updating a file in the /proc directory. All in all a very frustrating evening but something I've come to expect from RedHat. I guess with the complexity of configurations this is to be expected but I really wonder if such things couldn't be better detected by the upgrade software or at least documented somewhere. [ this is where you point me to the exact doco I missed :-) ] Thanks for all the help you have provided over the years. The SLUG archive is one of the best resources I have and I've learned heaps from it. Cheers and happy holidays to all. ~~ Darrell Burkey @ Home Canberra, ACT -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
