On 2012-11-28 16:07 (GMT-0800) Linda Walsh composed:
Perhaps someone can explain to me why Windows doesn't need a pre-boot ramdisk in order to boot, while Linux does?
I know Windows doesn't have all the drivers for all the hardware linked in with it's kernel -- it's dynamically loaded out of it's "/bin (windows/sytem32)" dir.
So why does the linux kernel have this extra complication while windows does not? It's a bit embarrassing, I would think to see the wide range of HW supported by Windows **without** a special 'initrd' for drivers, while linux still doesn't support the range of HW that Windows does (some, but not ALL of that being due to short-sited HW providers who can't provide open specs or drivers).
So what is Windows doing 'right', that Linux is unable to do?
Likely the registry, if you can call that doing anything right. Ever tried moving a Windows HD to another motherboard and booting it. I don't think it ever works. In recent Linux distros, it usually works, at least as long as the HD controller is in the same class. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org