Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I intend to replace my hardware (except hard disks). Is it possible to avoid reinstalling the system? I guess it will not boot with new hardware configuration.
Sure, it's possible to avoid reinstalling, and further, it's quite likely it will work just fine. That's what I have done in the past.
Provided there are no GIGANTIC incompatibilities.
To avoid these incompatibilities, like for example if your current kernel is tightly configured for the hardware on your OLD system (drivers for hardware, disk controller, NIC, etc..), it may not be happy with the hardware on your new system; therefore you would want to build a kernel with support for the NEW hardware. But if you're running the stock kernel, this is way less likely.
Short answer: Boot the OS with a generic kernel after you swap all the hardware, and go from there. Should be OK.
Sasha
NOTE: make sure the HDD where the OS is installed, winds up on the same IDE slot as it was previously. If not, you'll need to boot your OS using the CD or DVD, and edit your LILO configuration appropriately, so the bootloader knows where to find it's kernels.
Last edited by GrapefruiTgirl; 01-15-2010 at 12:19 PM.
Your slackware was installed and optimised for that particular hardware set that you've got at the moment. Theoretically, it 'might' work by some strange coincidence but I wouldn't recommend it. Backup your data on a separate partition and reinstall your system once you've upgraded your hardware.
edit: just seen Sasha's answer. I tried it a few times in the past and did not work for me
I've done exactly that a few times. By taking my hard drives out of an old computer and placing them into a new computer.
Although this was with 32 bit systems; not 64 bit.
So the question is not so much is it possible. But rather is it easy ?
My most recent change of this type was upgrading one of my desktops that was (and still is) running Slackware 12.1.
In that situation the biggest headache was reconfiguring xorg.conf.
Good point mentioned about xorg.conf. Video will need reconfigging after the swap too; very likely.
Interestingly, @ sycamorex -- when I last did this, (it was also on a 32bit system: Slack11) and I did have the kernel configured pretty tightly for the old hardware (my mobo that died) so when I got the new mobo (which needed a new CPU, new RAM, new video cards, etc..), I put the machine back together and had fingers crossed -- and was expecting pretty much nothing at all to work.
To my pleasant surprise, the darn thing booted right up without complaint!
Of course, I DID need to do a little bit of work re: video driver, but my new video cards were of the same make as the old ones, so it wasn't bad. Plus, I soon after rebuilt my kernel, geared toward the new processor (which was of the same make too, but a much different model-- I went from an old P4, to a new Core2), but still, it booted up very nicely.
I guess with anything along these lines, mileage may vary per case, but before defaulting to "reinstall" mode, I'd go for it, see what happens. Worst case scenario? It doesn't boot. Use the CD to boot then.
Interestingly, @ sycamorex -- when I last did this, (it was also on a 32bit system: Slack11) and I did have the kernel configured pretty tightly for the old hardware (my mobo that died) so when I got the new mobo (which needed a new CPU, new RAM, new video cards, etc..), I put the machine back together and had fingers crossed -- and was expecting pretty much nothing at all to work.
I did it with Fedora 8 or 9, don't remember. It did boot up but the number of error messages I got made me think it's not worth the hassle of trying to fix it and assumed that it's not the most optimal solution. Yes, the kernel can be recompiled and xorg.conf edited to remove most of the incompatibilities and I agree that in the worth case scenario it will not boot up. Still, for some strange reason, I'd go for a fresh install as I'd get the irrational(?!) feeling that the old installation on the new hardware is not 'clean', LOL
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.