Larry Stotler schrieb:
On Fri, Oct 23, 2009 at 8:54 AM, Per Jessen
wrote: Quite possibly, but many users might very well move their disk(s) to a new system when the old one gives up. Which amounts to the same thing.
If your hardware controller is different, that will screw up intird. I've ran into that on several occasions. I've swapped out drives between machines and a lot of times if the hardware is similar(thinkpad 390X to Thinkpad X21), then it will work but you have to tweak things like the video and sound. The chipsets on those machines are 440BX's so the boot setting doesn't change. However, when I tried swapping a boot drive from a Dell with an P4/i840 to a Tualatin P3/Via, it failed to boot. Being too lazy to fix it manually, I just reinstalled.
The initrd is set for a particular type of hardware and if the hardware changes too much it won't work. That should be expected. Try swapping a Windows XP boot drive to completely different hardware. While there ARE ways to do it, 99% of the time most people will have to reinstall.
Hi, in the "good old times" this was possible with Suse and other Linux distros. They included a "monster initrd" that probed all hardware and you could swap harware like mad. One thing windows never was able to handle. Yesterday i found out how to build this monster initrd (mkinitrd -A) and all Hardware runs now. But the next kernel patch will build a new initrd and if i don't take care, i have to rebuild the monster initrd in a rescue system again. So my proposals: - Add a grub entry with a monster initrd - Add a Yast module or something else to put the loaded and in use modules to your configuration (initrd, modprobe.conf, ....) This could make Linux as flexible as it was in the "good old times". Or am i missing something? Flo