Very Computer

: texte: "Quelqu'un a-t-il reussi a installer Linux sur un disque dur de 540Mo (ou
: plus) utilisant un driver Ontrack Disk Manager (dynamic drive overlay) ?
:
:       Avec le driver Linux ne peut pas lire la table des partitions.
:       Sans le driver le dos ne peut pas "voir" les 540Mo !!
:
:       Ma carte mere ne possede pas l'acces LBA pour les gros disques.
:
: Merci d'avance."
C'est possible de le faire. Tu devras neanmoins utiliser un kernel
Alpha Version 1.3.32 ou plus. mon avis, est que le 1.3.37 est le plus
stable de ces kernel. Mais fais attentions si tu utilise la version de
bibliotheque libc_5.2.10 ou superieur. Elles ne marcherons
pas. Utilise la version 5.2.14, sinon reste a la version 5.0.9.

Je veus te rappeler que linux n'as pas besoin de overlay. Si ton
disque dur n'est pas trop vieux, le kernel demande les parametres au
disque dur directement, sinon, donne les options au kernel en utilisant
le lilo. Par contre tu devras faire attention a deposer l'Image du
kernel en dessous des 504 MBytes pour que le LILO qui lis ses
parametres a partir du BIOS puisse trouver le kernel, plus important
encore, y acceder. Apres, une fois que l`Image est chargee, le BIOS
n'est plus d'aucune Importance :) J'utilis 2 Disques dur de plus de
504 MB sans Overlay ;) 700MB et 1.2 Gig.

a part ca, je veus te rappeler gentiment que la pluparts des gens ici
ne comprennent pas le francais, entre autre ce groupe est de Langue
Anglaise. Alors, la prochaine fois, en anglais s.v.p.

--
`*** Fatal Error: Found [MS-Windows] -> Repartitioning Disk for LiNUX...'
________________________________________________________________________


| Stardust's LiNUX System   :   Data, Fax & Voice 49 30 3627345        |
| PGP 2.6.2i Key on Demand  :   ZyXEL Link                             |
------------------------------------------------------------------------
Redistribution of this message prohibited for: Compuserve, Microsoft
Network, America Online, Telekom Online and  Europe Online !

Please do not reply upon Ontrack Disk Manager. It will only confuse
the partitioning information beyond repair.

Linux will install on disks which are greater than 540 MB. I run it on
1.2G drives. The important issue is to have the LILO loader and its
associated kernel file on the first 512 MB worth of data on the
disk. This is accomplished by having a small partition on that are and
installing LILO and the kernel into that partition.

The root partition may be anywhere and of any size. The important
issue is the 'boot' partition.

There is very good documentation on how to do all of these operations
in the "Linux Installation and Getting Started Guide". You will find
this on sunsite.unc.edu in the /pub/docs directory.

Quote:>    Avec le driver Linux ne peut pas lire la table des partitions.
>    Sans le driver le dos ne peut pas "voir" les 540Mo !!

Yes. You will need to add information for the LILO loader which gives
the disk parameters. My little portable has only a 820MB drive and it
uses a section such as:

# Start LILO global section
disk = /dev/hda
  bios = 0x80
  sectors = 63
  heads = 32
  cylinders = 787
#
append="hd=1574,16,63"

to define the geometry on the Toshiba drive in their 400CDT.

Quote:>    Ma carte mere ne possede pas l'acces LBA pour les gros disques.

Most disk cards do not support this because the BIOS on the card has a 10
bit cylinder limit. That's the purpose of the translations.

Please look in the Installation Guide. All is there.

--

The above opinions do not necessarily represent those of the Management
of System Integrators nor any of its subsidiaries.

As far as I can make out, Quantum's Ontrack Disk Manager (or dynamic drive
overlay software) puts an entry in the real partition table for the whole
disk, then creates another pseudo MBR somewhere inside that, which is
actually read by software looking for the MBR, which contains the
main partition table for a disk.

If someone can find out exactly what the wretched software is doing,
it should be fairly easy to imitate it, but I don't think anyone has
done so yet.

As a temporary solution, you might try installing Linux on a
second IDE disk.

     -- Owen (Audoin)