 |
 |
| |
Installation
Notes - Linux |
| |
|
| |
 |
Installation
Requirements |
 |
| Boots
from partitions |
primary
or logical partitions |
 |
| Boots
from drives |
any
drive (accessible by BIOS) |
| Minimum
space to install |
30
MB to 2 GB (depending on vendor) |
| Installs
into MultiFAT |
No |
| File
systems supported |
Ext2, Ext3, ReiserFS
(read/write access to FAT12, FAT16, HPFS, NTFS) |
|
|
| |
|
| |
Notes |
| |
| |
|
| • |
Linux
should boot through LILO installed into the root superblock
(which is a different name for partition boot record). The preferred
LILO operation is NOT installed into the MBR. System Commander
7 also supports MBR booting, if Linux was already installed
this way. Many distributions use GRUB instead of LILO. Currently
we recommend installing GRUB into the MBR, as our tests show
it can only use the superblock method when booting from a Linux/GRUB
boot diskette. |
| |
|
| • |
Older
versions of LILO (2001 time frame) will have trouble booting from large hard disks
that are not translated (disks with more than 1024 cylinders).
LILO must be installed on a partition that exists below the
1024 cylinder limit. Other partitions may extend beyond this
point. LILO available in current Linux distributions
supports booting past 1024 cylinder (8 GB).
|
| |
|
| • |
Be
aware that some Future Domain SCSI controller BIOSes order the
drives differently than the Linux kernel. This requires a special
setup in the /etc/lilo.conf file. This is documented in the
LILO-FAQ. |
| |
|
| Special
Warnings |
| |
|
| • |
The
Linux FDISK program can create logical partitions that may confuse
MS-DOS and/or other operating systems. The only way to avoid
this is to create partitions using another partitioning utility
such as Partition Commander or System Commander, or to create
Linux partitions as primary partitions. |
|
| |
|
| |
Installing
Linux - Step-by-Step
The OS Files - Linux
|
| |
|
| |
Note:
While every attempt is made to ensure the usefulness and accuracy
of this information, it is provided only as a service of VCOM. No
warranty is given with respect to this information regarding the accuracy,
usability, or fitness for a particular purpose. Use this information
at your own risk. Under no circumstances shall VCOM be held liable
for any damages either incidental or consequential. |
| |
|
| |
 |
| |
|
|
 |
|
