Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch
The last two limitations are less severe with modern PCs:
Some recent BIOSses allow the access to further equipment, such as up to four EIDE-harddrives (with EIDE-controller) instead of two. Some really modern combinations of BIOS/SCSI host adapter will allow you to boot from a SCSI-harddrive when EIDE-disks are built into the machine. However these features are not widespread and standardized enough to specify general rules.
Some SCSI host adapters have the ability -- controlled by drivers or your BIOS settings -- to "show" the system various different geometries of the harddrives connected to your PC. Please see section 6.2 (SCSI details) of the Large-Disk-HOWTO
/usr/doc/howto/mini/Large-Disk.gzfor further details.
However there is no way to get around the 1024-cylinder limitation in the moment!
Henceforth we will use the term 1024-cylinder boundary when referring to the reachable area of the harddrive.
/boot
(or in the location specified in /etc/lilo.conf
).
Altogether this is normally less than 2 MByte. /boot
and the Linux-kernel
usually reside in the Linux root partition. However this is not enforced. In principal it
is even possible (but dangerous), to store this data on partitions of other operating systems.
Which possibilities do we have now when taking into account these limitations ?
If you use another boot-manager that is able to start this logical partition itself, you can also install LILO there. Attention: From time to time the OS/2-bootmanager (maddin_os2linux.html) has difficulties starting LILO from logical partitions ! Depending on the partition-layout it will or will not work : The reason is not known up to now ...
Maybe partitions of other operating systems occupy all availabe space below the 1024-cylinder boundary and you cannot or don't want to repartition the harddrive.
If one of the "foreign" partitions resides completely before cylinder 1024 and Linux allows read-/write-access to its filesystem (e.g. FAT or Win95-VFAT), then you can also store the LILO-data there -- except for the bootsector.
However the reliability of this method is somewhat questionable. Your LILO-files rely on the grace of the foreign operating system and its applications. If the foreign partition reaches further than cylinder 1023, there is no way to ensure that the LILO-data is stored before cylinder 1024, so the whole procedure may fail.
Warning : Don't install the LILO-bootsector into a foreign partition since the file-system will usually be damaged.
Thus the LILO-bootsector can only be stored in the beginning of an extended partition on the first disk (if below cylinder 1024) or into the MBR.
Let's assume that a suitable DOS-partition is mounted in /dos
. LILO shall go into the MBR
(i.e. /dev/hda
). It also should be able to boot DOS from /dev/hda1
. Then procede
as follows :
/dos/LINUX
) and copy the LILO-files from /boot
there.
Also copy the Linux-kernels that LILO shall boot.
/dos/LINUX/lilo.conf
according to the following example. All paths
in this file should point to the directory /dos/LINUX
:
# LILO configuration-file for foreign partition # Start LILO global Section boot=/dev/hda # Installationsziel backup=/dos/LINUX/mbr_hda.bak # backup of old MBR install=/dos/LINUX/boot.b # Of course LILO and the map=/dos/LINUX/map # map-file are in /dos/LINUX! message=/dos/LINUX/message # optional prompt timeout=100 # Wait at prompt for 10 s vga = normal # End LILO global section # # Linux bootable partition config begins image = /dos/LINUX/First_Kernel # Put your kernel here root = /dev/Your_Root_Device # root-partition into this place label = linux # Linux bootable partition config ends # # DOS bootable partition config begins other = /dev/hda1 # MSDOS-systemdrive label = dos loader = /dos/LINUX/chain.b table = /dev/hda # DOS bootable partition config ends
lilo.conf
:
# /sbin/lilo -C /dos/LINUX/lilo.confDone !
Now LILO should work. Boot DOS and try to protect the LILO-files against write-access as much as possible !
(As a reminder : Any displacing of these files done e.g. by a defragmentation-program will stop LILO from working).
At least mark all the files in X:\LINUX
(where X:
is the DOS-partition just mounted under /dos
)
with the DOS-attributes system and hidden .
boot=
line in the former example :
boot=/dev/ext_Partition # Insert your extended partition hereDon't forget : Mark the extended partition on disk 1 as
bootable
with Linux-fdisk
right after the installation of LILO and remove this mark from the other primary partitions
See also:
Keywords: 1024, CYLINDER, LILO, BOOT, BOOT-PROBLEMS, IDE, EIDE, SCSI, INSTALLATION
Feedback welcome: Send Mail to rb@suse.de (Please give the following subject: SDB-1024_Zylinder
)
Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch