hello John,

 i think you understood what i wanted to say.

 when i ran lilo, it added the image that is
 
 below the new image in lilo.conf file.

 then why can't it do with the one i added(new image).

 let me explain again.

 look at this sample lines of code of /etc/lilo.conf


    image=/boot/vmlinuz-2.2.13   ---> default and first entry
          ........
          ........

    image=/boot/vmlinuz-2.2.22   ---> new image that i added.
          ........
          ........

    image=/boot/vmlinuz-2.2.5    ---> another image
          ........
          ........


  now when lilo can add both 2.2.13 and 2.2.5,

  why is the problem with 2.2.22 alone.


                                                Madhu P   
   
   |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
   | If u want to contact me                                              |
   |                                                                      |
   | Personally                Thru Mail              On Phone            |
   | ~~~~~~~~~~                ~~~~~~~~~              ~~~~~~~~            |
   | N-118, STUDENT'S HOSTEL  [EMAIL PROTECTED]    (080) 3092454 - Hostel |
   |                                                                      |
   | IISc,                    [EMAIL PROTECTED]  (080) 3602095 - LAB    |
   |                                                                      |
   | BANGALORE-12.            [EMAIL PROTECTED]              |
   |                                                                      |
   |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
   |         Home Page :: http://www2.csa.iisc.ernet.in/~madhup           |
   |______________________________________________________________________|

On Tue, 5 Sep 2000, John Aldrich wrote:

> On Tue, 05 Sep 2000, [EMAIL PROTECTED] wrote:
> >  though the problem is solved, iam still unable
> >  to understand why it was not including that
> >  single image(the one i added newly).
> >  why just that image was missing in the options
> >  at boot time.
> > 
> >  anybody can tell why this happened.
> > 
> Because it wasn't even getting that far... it got as far as checking
> for the default image which wasn't there.
>       John
> 
> 
> 
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
> 



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to