LILO vs. LOADLIN

LILO vs. LOADLIN

Post by Slav Inge » Tue, 30 Dec 1997 04:00:00



Hello,

For all of you LILO sufferers out there, loadlin program is a very
convenient replacement for LILO - however it boots Linux from DOS
partitions.  I wasn't able to get LILO to work on my machine - I have an
old BIOS with EZ-DISK running.  At every boot, LILO would hang with a
"LI" message.  I solved this problem once, but after I recently
recompiled the kernel and rebooted, the problem came back.  I followed
an advise in this newsgroup and switched to loadlin, and it really
helped me out.  It's easy to setup, use, and all you need is a kernel
image (like zImage).  You could copy your kernel to the DOS partition
from Linux, or by using a program to read Linux partitions from DOS.  I
used the latter option - ext2tools; you can also use lread.  The major
advantage to me is that loadlin allows to boot Linux while keeping the
MBR intact.  It also solves many LILO incompatibilities, including the
one I described above.  Just like with LILO, you can pass boot
parameters to the kernel (i.e. mem=xxx)!  If you use loadlin, you don't
need System.map file.  In addition, loadlin is included on the RedHat CD
in the root directory under the name lodlin16.tgz.  It's also available
from major Linux FTP sites and mirrors.
Well, this concludes my story.  My goal was to raise awareness of
loadlin and of its benefits.

Also, I'd like to thank everybody who contributes their time and effort
to answering questions in these groups.

Happy Holidays to everyone!

- Slav Inger.

 
 
 

LILO vs. LOADLIN

Post by w.. » Tue, 30 Dec 1997 04:00:00


   I, too, endorse loadlin.  It is very easy to incorporate into a dual
boot config.sys menu in Windoze 95 which allows me to choose whether to
boot into linux or windows.  
   I also have an icon on my Windoze desktop which runs loadlin as a dos
program, allowing me to switch to linux without "manually" rebooting or
dealing with the dual boot menu.
  And all of this without messing with boot sectors and the like.  When I
recompile, I just plug in the new kernel image and its done.  No
reconfiguring of loadlin at all.  And how many requests for loadlin help
have we seen in these groups?  Very few if any.



Quote:>Hello,

>For all of you LILO sufferers out there, loadlin program is a very
>convenient replacement for LILO - however it boots Linux from DOS
>partitions.  I wasn't able to get LILO to work on my machine - I have an
>.....

--

Robert Price
"What lies behind us and what lies before us are tiny matters compared to
what lies within us" - Ralph W. Emerson
e-mail: bobprice at enteract dot com

 
 
 

LILO vs. LOADLIN

Post by Kahin » Wed, 31 Dec 1997 04:00:00


        I credit Loadlin for my tri-OS system accomplishment.

:    I, too, endorse loadlin.  It is very easy to incorporate into a dual
: boot config.sys menu in Windoze 95 which allows me to choose whether to
: boot into linux or windows.  
:    I also have an icon on my Windoze desktop which runs loadlin as a dos
: program, allowing me to switch to linux without "manually" rebooting or
: dealing with the dual boot menu.
:   And all of this without messing with boot sectors and the like.  When I
: recompile, I just plug in the new kernel image and its done.  No
: reconfiguring of loadlin at all.  And how many requests for loadlin help
: have we seen in these groups?  Very few if any.


: >Hello,
: >
: >For all of you LILO sufferers out there, loadlin program is a very
: >convenient replacement for LILO - however it boots Linux from DOS
: >partitions.  I wasn't able to get LILO to work on my machine - I have an
: >.....

: --

: Robert Price
: "What lies behind us and what lies before us are tiny matters compared to
: what lies within us" - Ralph W. Emerson
: e-mail: bobprice at enteract dot com

--



Http://WWW.Servtech.Com/public/kahina/index.html

 
 
 

LILO vs. LOADLIN

Post by Theodore J. Soldato » Wed, 31 Dec 1997 04:00:00



> Hello,

> For all of you LILO sufferers out there, loadlin program is a very
> convenient replacement for LILO - however it boots Linux from DOS
> partitions.  I wasn't able to get LILO to work on my machine - I have an
> old BIOS with EZ-DISK running.  At every boot, LILO would hang with a
> "LI" message.  I solved this problem once, but after I recently
> recompiled the kernel and rebooted, the problem came back.  I followed

Did you run lilo to update boot record ? This is just the wrong lilo
installed, a problem that as i suppose many newbies have when
recompiling the kernel for the first time. It happened to me once, and i
had some minutes of agony before figuring that out, as i had the extra
complication of using NT loader and a BR "strip" to boot Linux from his
own partition.

<snip>

Quote:> Well, this concludes my story.  My goal was to raise awareness of
> loadlin and of its benefits.


installation of Linux was on a FAT16 partition, using loadlin. I made an
installation of about 150MB. Then i checked out the free space of my
drive - it was minus *350MB* !!! 200MB had just dissapeared. Then i
remembered something called slack space - FAT16 is problematic when
dealing with too many small files - and thats the case of Linux, too
many small files. The missing 200MB were just empty space wasted on
sectors containing small files. So, i just throwed out NT from my 2nd
partition and installed Linux there. No problems at all with LILO, even
with the (weird at least, IMHO) setup that uses NT loader to boot LILO.

My advise is that you install Linux into his own ext2fs partition and
paying some more attention on installing LILO the right way. It is not
so hard as it looks. :-)

T.

--
Theodore=J.=Soldatos=_\_="There=is=always=a=bug=somewhere",=said==HAL=to=the==

=_/_==Ultimate=Programmer,=and=turned=off=the=air=supply.=
=====================_\_="Everybody=knows=the=war=is=over,====================
==== Scientific
=====_/_==everybody=knows=the=good=guys=lost"===Leonard=Cohen=
= Publications Ltd. =_\_============ http://w4u.eexi.gr/~theodore
============

 
 
 

LILO vs. LOADLIN

Post by Brian Gers » Wed, 31 Dec 1997 04:00:00



> > Well, this concludes my story.  My goal was to raise awareness of
> > loadlin and of its benefits.


> installation of Linux was on a FAT16 partition, using loadlin. I made an
> installation of about 150MB. Then i checked out the free space of my
> drive - it was minus *350MB* !!! 200MB had just dissapeared. Then i
> remembered something called slack space - FAT16 is problematic when
> dealing with too many small files - and thats the case of Linux, too
> many small files. The missing 200MB were just empty space wasted on
> sectors containing small files. So, i just throwed out NT from my 2nd
> partition and installed Linux there. No problems at all with LILO, even
> with the (weird at least, IMHO) setup that uses NT loader to boot LILO.

> My advise is that you install Linux into his own ext2fs partition and
> paying some more attention on installing LILO the right way. It is not
> so hard as it looks. :-)

> T.

He didn't necessarily say to use UMSDOS fs for linux, just putting the
boot files (kerenel, initrd, etc.) on the FAT16 partition.  I have a
config.sys menu set up on my machine which makes it easy to boot between
windows, dos, and linux.  The only files I have on the FAT partitions
are the kernel images - the rest of linux is on ext2 partitions.

--

                                                Brian Gerst

 
 
 

LILO vs. LOADLIN

Post by Paul Cadare » Wed, 31 Dec 1997 04:00:00


I have been struggling with my 1st time install of Linux for several days
now.
(Take a look at my posting  around 00:00 sunday)

Could you pont me to some info on how to use LOADLIN?

Thanks....

 
 
 

LILO vs. LOADLIN

Post by Dwbo » Thu, 01 Jan 1998 04:00:00


I'm fairly new at this before I've just used lilo. But after RD5.0 fouled up my
mb and what that entailed I'm ready for loadlin.
I've got loadlin and lread and tested getting into linux .What I'm not sure of
is were and how to get the image I need in redhat 5.0 .
Right now I'm using 4.2 because it lets me boot from floppy.
Thanks for any help
Dave

 
 
 

LILO vs. LOADLIN

Post by Slav Inge » Thu, 01 Jan 1998 04:00:00




> first
> installation of Linux was on a FAT16 partition, using loadlin. I made
> an

I did not install Linux using UMSDOS - I installed Linux into ext2
partition.  However, I use loadlin to boot from FAT16 into Linux.  In my
case, at least, loadlin is a perfect replacement for LILO.

- Slav Inger.

 
 
 

LILO vs. LOADLIN

Post by w.. » Thu, 01 Jan 1998 04:00:00



>> first
>> installation of Linux was on a FAT16 partition, using loadlin. I made
>> an

I use loadlin to boot to my linux system.  All of my linux system is
installed on ext2 filesystems.  Works very well.  Loadlin itself is on my
FAT16 system which makes it very easy to incorporate into a
Windows 95 config.sys dual boot menu or invoke from a desktop icon.
 
 
 

LILO vs. LOADLIN

Post by NO-SPA » Thu, 08 Jan 1998 04:00:00


Here's a slightly different question.  What is the "suggested" best
way to re-store the MBR if you already have LILO installed but need to
move to LOADLIN?  I use a Compaq that has a builtin ethernet (Flex/3)
and according to the Ether-HOWTO, I have to boot from Dos and run PCI
utility that re-maps the address so Linux can find it.  

I have valid boot disks from before I installed Linux (sharing with
older Win95 install) and I could code a direct write from the floppy
to the harddrive, but I was wondering if anyone had any suggestions?

JEM

jemcdevitt at mindspring dot com

*****************************************************************************
To reply by email-remove the anti spamming stuff.  I know it is a
pain, but so is spam.
******************************************************************************

 
 
 

LILO vs. LOADLIN

Post by Theodore J. Soldato » Thu, 08 Jan 1998 04:00:00




> > > Well, this concludes my story.  My goal was to raise awareness of
> > > loadlin and of its benefits.



<snip>

Quote:

> > T.

> He didn't necessarily say to use UMSDOS fs for linux, just putting the
> boot files (kerenel, initrd, etc.) on the FAT16 partition.  I have a
> config.sys menu set up on my machine which makes it easy to boot between
> windows, dos, and linux.  The only files I have on the FAT partitions
> are the kernel images - the rest of linux is on ext2 partitions.

Ooops... Thats what happens when a newbie tries to give advice...
*blush* Did'nt knew that loadlin can be used that way... Sorry for the
wrong advice... But the part about UMSDOS and NT loader is right, as far
as i have seen from other posts...

T.

--
Theodore=J.=Soldatos=_\_="There=is=always=a=bug=somewhere",=said==HAL=to=the==

=_/_==Ultimate=Programmer,=and=turned=off=the=air=supply.=
=====================_\_="Everybody=knows=the=war=is=over,====================
==== Scientific
=====_/_==everybody=knows=the=good=guys=lost"===Leonard=Cohen=
= Publications Ltd. =_\_============ http://w4u.eexi.gr/~theodore
============

 
 
 

LILO vs. LOADLIN

Post by Bruce Co » Fri, 09 Jan 1998 04:00:00


N> Here's a slightly different question.  What is the "suggested" best
N> way to re-store the MBR if you already have LILO installed but need to
N> move to LOADLIN?  I use a Compaq that has a builtin ethernet (Flex/3)
N> and according to the Ether-HOWTO, I have to boot from Dos and run PCI
N> utility that re-maps the address so Linux can find it.

Assuming you mean the Ethernet-HOWTO, I can't find a copy that mentions
the Flex/3 explicitly.  However, since I have recently played with a Compaq
with builtin NetFlex/3P card, I'll tell you what I found...

1)  The 2.0.x kernels do not recognize the card (unknown PCI device).
    This is possibly fixed for high x, but I think there was still no driver
    available.

2)  There is an experimental driver in the 2.1.x kernels, at least for the
    later ones.  I ended up downloading the source (I could ftp from
    Windows), building a custom kernel and installing it.  It worked.

3)  I didn't have to use any utility to re-map addresses (but maybe I'm just
    lucky).

Good luck (i.e., be paranoid).

Cheers,
bruce

--

School of Mathematics and Statistics F07   +61 2 9351 3814
University of Sydney 2006
AUSTRALIA

 
 
 

LILO vs. LOADLIN

Post by Andrew Mitche » Fri, 09 Jan 1998 04:00:00




>  What is the "suggested" best
>way to re-store the MBR if you already have LILO installed but need to
>move to LOADLIN?

Try booting to DOS/Win95 command prompt, and enter SYS C:. That should
restore the microsoft MBR.

Andrew Mitchell
Melbourne, Australia

 
 
 

LILO vs. LOADLIN

Post by Titus Barsc » Fri, 09 Jan 1998 04:00:00





> >  What is the "suggested" best
> >way to re-store the MBR if you already have LILO installed but need to
> >move to LOADLIN?

> Try booting to DOS/Win95 command prompt, and enter SYS C:. That should
> restore the microsoft MBR.

> Andrew Mitchell
> Melbourne, Australia

On my system SYS C: does not restore the MBR, but what works is
a not documented fdisk option:
fdisk /mbr
called from dos restores the MBR.

Good luck,

Titus

--
-------------------------------------------------------------------
Titus Barsch
Institut fuer Geometrie und Praktische Mathematik
RWTH Aachen
Templergraben 55, 52056 Aachen, Germany


http://www.igpm.rwth-aachen.de/~barsch Fax   : +49 / 241 / 8888317
-------------------------------------------------------------------

 
 
 

LILO vs. LOADLIN

Post by (SPAMLES » Sat, 10 Jan 1998 04:00:00





>N> Here's a slightly different question.  What is the "suggested" best
>N> way to re-store the MBR if you already have LILO installed but need to
>N> move to LOADLIN?  I use a Compaq that has a builtin ethernet (Flex/3)
>N> and according to the Ether-HOWTO, I have to boot from Dos and run PCI
>N> utility that re-maps the address so Linux can find it.

>Assuming you mean the Ethernet-HOWTO, I can't find a copy that mentions
>the Flex/3 explicitly.  However, since I have recently played with a Compaq
>with builtin NetFlex/3P card, I'll tell you what I found...

Yes it is the Ethernet-HOWTO.  Mine listed NetFlex/3 in section under
Compaqs (PCI type card).

Quote:>1)  The 2.0.x kernels do not recognize the card (unknown PCI device).
>    This is possibly fixed for high x, but I think there was still no driver
>    available.

I found an experimental driver called TLan (Thunder ).  I added it to
the kernel and now my card works fine.  I'm using 2.0.33 patch on my
kernel.

Now I'm just trying to get my Win95 box to be able to Ping this one.
Another day, another interesting quirk.

Quote:>2)  There is an experimental driver in the 2.1.x kernels, at least for the
>    later ones.  I ended up downloading the source (I could ftp from
>    Windows), building a custom kernel and installing it.  It worked.

>3)  I didn't have to use any utility to re-map addresses (but maybe I'm just
>    lucky).

>Good luck (i.e., be paranoid).

>Cheers,
>bruce

With the TLan driver, I didn't have to remap either.  I did move the
base port I/O from 0x1000 to 0x280 (which was unused on my machine).
Don't know if this is what is allowing it to work or just using the
new TLAN driver, but it works.

JEM
********************************************************************************
To reply via email, do the necessary fixes

on the address to remove anti-spamming stuff.  
I know it's a pain, but so is spam.
********************************************************************************