-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/07/2012 10:28 AM, John Aldrich wrote: > Quoting Dave Ihnat <dihnat@xxxxxxxxxx>: > >> Once, long ago--actually, on Mon, Aug 06, 2012 at 09:29:49PM -0700--jdow (jdow@xxxxxxxxxxxxx) said: >>> Then I discovered a property of Windows. If your motherboard goes >>> bad and you can't replace it with an exact replacement the system and >>> all other software installed on that disk are suddenly useless. (Yes, >>> you can at least recover the files. But you cannot recover the installs.) >> >> Ah...just a parenthetical aside. This is quite untrue. I've replaced >> failed motherboards on numerous Windows installations of various versions. >> You usually have to do a recovery reinstallation, but it does work, and >> your installed programs, data, etc. are all preserved. >> >> I'm not defending Windows--this is more along the lines of "Know thine >> enemy". If you're trying to promote Linux, but express actual falsehoods >> about Windows, people will discount all your views. >> > Yes...but if your Linux box is set up with a generic, modular kernel, chances are you won't have to re-install Linux, where, as you point out, with Windows, you'll have to do a "repair" install, at a minimum. At worst, you'll have to try and re-install on another disk and re-install all your apps and copy your data over. So, you are correct in that many cases, on Windows you can do a "repair install" but may end up having to start over from near scratch. Linux, properly set up, doesn't have that issue. :D You do not have to reinstall, but depending on the hardware changes, you have have to do the Linux equivalent of a rescue install. It works as long as you are using the same modules to mount the root file system. But if you need different drivers because of the hardware change, you have to do the build a new initrd before you can boot. This is because the modules used to mount the root file system are in the initrd file. The kernel has the drivers needed to mount the initrd compiled in. But it normally does not have the drivers for the root file system compiled in, unless it is a custom kernel. In some ways, it can actually be easier to make the change with a custom kernel - you do a rescue boot, chroot to the "real" installation, and install the kernel RPM. This has the advantage of automatically building the needed initrd file. Then you can do a normal boot. I have only had to do this a couple of times, and it was because of drastic hardware changes. But when I make that kind of hardware change, I usually do a new install and restore the user data, and migrate config files. Mikkel - -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlAhT2IACgkQqbQrVW3JyMQHcwCfXrmTDrmzb2HkEad9v+BOenDh GDwAn1aDx43N4B9dzMxG8WeJQZSfAT1Q =ai9V -----END PGP SIGNATURE----- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
