[EMAIL PROTECTED] wrote:
> Depending on the
> BIOS, there might not _be_ any BIOS drive number by which /dev/sdd is
> accessible. If that is the case I don't think you will be able to boot
> it directly with any bootloader, but the /boot partition approach will
> work with lilo, or grub, some other bootloader.
Ok, but what in the case where, during the BIOS part of booting the
system, it appears on the screen that BIOS recognizes all hard disks and
there are their numbers asigned. Is it needed to advise LILO about these
disk numbers? Is LILO
(as the part of Linux) able to 'see' disks, if we also know, that a
Linux package was installed without complaints, after we told the setup
which disk and partition we wanted to be used for an instalation? Is
that problem noticed only at booting? What is the best way to workaround
this issue?
> When every OS has its own hd, lilo doesn't necessarily know which BIOS
> device is which OS device, and, depending on the BIOS, it can even
> change depending on which hd the BIOS last booted. If the BIOS has an
> option to select which HD to boot, it often assigns _that drive_ device
> number 0x80 at boot time.
Ok, I assume that the problem is in LILO, because NT's boot loader
doesn't complain, regardless of HDD is used to install NT. I made
another test: I removed NT from the 1st disk and reformated this HDD
into linux format. So, after I removed any sign there was installed
something that is not 'linux-like', and asked the setup to put LILO into
MBR, it seems to me that neither this time (Linux alone in the system)
the instalation was not ok, because, after the next reboot, the result
was: "LI" and nothing else. What is the best cure?
Misko
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
