Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-06-21 22:13, Tony Alfrey wrote:
Let me just add one comment/question:
If the Windows drive will boot independently all by itself w/o any help from grub, why would grub need to /add/ anything to the Windows drive to boot it.
Because you need grub on the disk that is the first one in the BIOS boot order, regardless of where is Linux installed.
Yes, of course. I expect to install grub (or LILO or ANY boot loader) on the first disk in the system, which will ABSOLUTELY be a linux disk. Windows will be a "secondary" disk. And that has been the way that I have had it with LILO for nearly 10 years! But by a choice of mapping in the boot loader, the Windows disk can be "deluded" into thinking that it is on the first disk, and not polluted by changing its MBR. The whole point is to keep the Windows disk as an INDEPENDENT disk entity that can be inserted, and booted, into anywhere, any computer, any time. I have to say that my previous implementation of LILO with two linux disks and one windows disk was remarkably simple and transparent. Yes, if I changed the kernel, I had to change the kernel name in lilo.conf. That is hardly an issue for me. LILO works. There are no "parts 1" and "parts 2", grub and grub2 or worse yet grub1.5. Summary: If I knew that I could DUMP grub, and write a lilo.config file that has worked for 10 years, and run /sbin/lilo, and that would eliminate grub from the process, I would do it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org