[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Monday 24 January 2005 10:44 am, Andrew Rogers wrote:
Neil Williams wrote:On Monday 24 January 2005 9:28 am, aaron Moore wrote:After removing my Fedora hard drive and fixing it to a newer computer I am unable to connect to the network.If you put a diesel engine in a car with petrol in the tank, will it work?It doesn't idle very well! But runs at higher revs. My dad knows all about it, after filling our car with petrol instead of diesel.
I subtly changed the usual form: putting diesel fuel in a petrol car (or vice versa) is troublesome but is common enough to be fixable, generally. Putting a diesel engine in a car that originally had a petrol engine adds more problems than what is in the tank already! Even if you get it to fit on the original mountings, there's all the rest of the fuel system that could need changing plus other bits. The network config is only the tip of a potentially very large iceberg in this particular case.
The newer computer will have a different network card and sundry other differences. Why are you doing it this way rather than installing on the new hardware? This is a newer machine so it's going to have a decent CD drive (or DVD) and on-board network support? It's easier to install fresh than to use an install that was configured for older hardware! ...I did a similar thing. Took a harddrive from an Athlon 800 and attached it to an Eden ESP 5000 (one of those mini ITX things) and in the main it worked. Although as you point out some reconfiguration was required.
How long did it take to reconfigure? Did you solve all the problems or were there issues outstanding that you could expect to have been resolved if a normal install was possible? (Couldn't you have done a network install for that box?)
It was Mandrake 8.2 on the hd.
So did you tweak each config file by hand or did you have to re-install large sections? Somehow, I'd expect Mandrake and Fedora to be more awkward but my approach would have been to leave the config files alone initially and try to reconfigure the packages directly. The existing config in most of the files will be junk anyway as it relates to the older machine, there may be a handful of config files that you edited by hand for personal settings but those can be backed up to /home. Then I'd uninstall most (all?) of the applications to be able to uninstall those system packages affected by the change. Reinstall those and get each one working in turn - this is why it appears so time consuming in comparison to just doing a fresh install. Learning the config procedures for each package and fixing them without using the methods provided by the package is bound to waste time? dpkg-reconfigure would be useful if it was a debian based system, that can reconfigure a package using the original installation scripts without uninstalling the package itself and causing all that dependency chaos and saving massive amounts of time. -- Neil Williams ============= http://www.dcglug.org.uk/ http://www.nosoftwarepatents.com/ http://sourceforge.net/projects/isbnsearch/ http://www.williamsleesmill.me.uk/ http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3
Attachment:
pgp00065.pgp
Description: PGP signature