I'm glad to be of help
Jonathan
On Wed, 4 Mar 1998, Daniel Mashao wrote:
> On Wed, 4 Mar 1998, C.J.LAWSON wrote:
>
> > I have had this problem before and I almost died of fustration before I
> > fixed ... as with most things the solution was pretty simple. For a start
> > try using a min
On Wed, 4 Mar 1998, C.J.LAWSON wrote:
> I have had this problem before and I almost died of fustration before I
> fixed ... as with most things the solution was pretty simple. For a start
> try using a minimal lilo and requesting the bios to auto detect the hdd at
> boot up. If this fails then do
I have had this problem before and I almost died of fustration before I
fixed ... as with most things the solution was pretty simple. For a start
try using a minimal lilo and requesting the bios to auto detect the hdd at
boot up. If this fails then do the same thing (auto detect) but specify
large
> I just installed a new Debian system. I had to copy the base1 disk X times
> on Y disks to get Debian to install. But now I get a LI instead of the
> expected LILO:
> What can I do without having to do a complete reinstall?
for me the only thing that has ever caused this (there are almost
certa
I don't remember the specific meaning of lilo stopping at LI either but
as mentioned it is explained in the LILO HOWTO.
Answering (at least partially) the question that I think that you are
asking...
You probably DO NOT need to reinstall. The problem is likely just a
lilo configuration problem a
On Tue, 3 Mar 1998, Daniel Mashao wrote:
> I just installed a new Debian system. I had to copy the base1 disk X times
> on Y disks to get Debian to install. But now I get a LI instead of the
> expected LILO:
> What can I do without having to do a complete reinstall?
This is the boot loader provid
I just installed a new Debian system. I had to copy the base1 disk X times
on Y disks to get Debian to install. But now I get a LI instead of the
expected LILO:
What can I do without having to do a complete reinstall?
/---/
Daniel J.
7 matches
Mail list logo
