Lilo question

[I.Ioannou]

On 21-Jul-98 George Diamantopoulos wrote:
> 
>> > vgainei ena L akolouthoumeno apo 01 kai to systhma menei ekei, me ta 0 kai
>> > 1
>> > sthn othonh. Kserei kaneis ti shmainei o kwdikos aytos?

> Twra an thelete na xanagrapsete to mbr h kanete format /mbr to opoio simenei

Eeeee!!!!!!! 
fdisk /mbr apo DOS kai den sbinei tipota allo pera apo to lilo loader apo to
MBR. Oute format /mbr oute tipota allo barbaro.

> oti
> xanete oti exete se auton ton hd . Allos tropos poio orthodoxos einai na
> valete
> auton pou sas edwse to slackware na kopsei to kefali tou na sas vrei ena boot
> manager.....

Den exoume pei na mhn panikobaloume toys arxarious xwris logo ? 


Antigafw apo to README toy lilo (/usr/lib/lilo sto Slackware mou)
----------------------------------

LILO start message
- - - - - - - - -

When LILO loads itself, it displays the word "LILO". Each letter is printed 
before or after performing some specific action. If LILO fails at some 
point, the letters printed so far can be used to identify the problem. This 
is described in more detail in the technical overview.

Note that some hex digits may be inserted after the first "L" if a 
transient disk problem occurs. Unless LILO stops at that point, generating 
an endless stream of error codes, such hex digits do not indicate a severe 
problem.

---
   L <error> ...   The first stage boot loader has been loaded and started, 
    but it can't load the second stage boot loader. The two-digit error 
    codes indicate the type of problem. (See also section "Disk error 
    codes".) This condition usually indicates a media failure or a geometry 
    mismatch (e.g. bad disk parameters, see section "Disk geometry"). 

Disk error codes
- - - - - - - -

If the BIOS signals an error when LILO is trying to load a boot image, the 
respective error code is displayed. The following BIOS error codes are 
known:

   0x01   "Illegal command". This shouldn't happen, but if it does, it may 
    indicate an attempt to access a disk which is not supported by the 
    BIOS. See also "Warning: BIOS drive 0x<number> may not be accessible" 
    in section "Warnings". 

---

Bebaia ola ayta kala kai agia, alla gia na dothei apantisi toy ti trexei akribws
xriazontai merika stoixeia : 

1) ti diskous exei (typos, megethos klp klp) ?
2) to bios toys anagnorizei, kai an nai me ti mode  ?
3) me ti alla leitoyrgika sigkatikei to Linux ?
4) den stelneis kai to /etc/lilo.conf mpas kai exei ginei kamia matsolia ?

To teleytaio to petixaineis :

a) kaneis boot me tis disketes tou Slackware kai apo kei mount to disko 
toy linux
b) kaneis mount tis partitions tou linux apo Win95 me to fsdext2.zip
(parto apo argeas.argos.hol.gr) h apo DOS me ext2tools (
opoiodipote mirror toy sunsite)
g) kaneis apo dos loadlin ton kernel sou (h enan kernel apo to CD 
toy Slackware) isa gia na kaneis boot sto linux sou (des ta manual toy 
loadlin sto CD - se genikes grammes prepei na dwseis kati toy stil : 
loadlin.exe <kernel> root=/dev/hdb1 ro  opou hdb1 h partition toy linux)


I.Ioannou <roryt at hol.gr>
--
====================================================================
Gia boithia (h na diagrafhte) e-mail sto majordomo at argos.hol.gr
Ta archives tis listas einai sto http://www.argos.hol.gr/lists :
prin steilete kapoia erothsh psakte mipos exei hdh apanththei.
Gia opoiodipote problima stilte e-mail ston owner-linux-greek-users
====================================================================