> On Thu, 29 Feb 1996, Phillip wrote:
>
> > On Thu, 29 Feb 1996, Bryn Paul Arnold Jones wrote:
> > > I think you should take a look at the docs for lilo as to what these mean
> > > (you should find it at /usr/doc/lilo, in README, or in the doc/ directory
> > > if you can deal with TeX).
> > > Bryn
> > True, but mine got past 'LILO' into the the kernel loading (this was at
> > 1.2.13), then rebooted, but only when I _didn't_ use the lilo.conf that
> > setup created...
> > What could cause this?
> >
> Hmm, well it's eather not a LILO problem (you'd have to had loaded the
> kernel), or there's something very sutle (sp?) rong with the drive
> geomtry, as persived by Lilo (the bios), and so lilo looks for sector X
> of the kernel at sector Y of the disk, but got this other sector (say I
> had 1 less sector as perseved by the bios, and so you'd loose a sector of
> kernel image over the end of the track).
> Not useing the lilo.conf that setup created is fine, as lilo (the
> command) would complane, and not install the loader.
No, If I changed the lilo.conf from the setup's one it wouldn't work...
Only the default versio would work....
The the disk geom would explain it... Mayby if it was in the last sectors
so when I used a Me-compiled kernel, that was smaller, it wasn't nessacary?
My cyc are > 1024....
--------------------------------------------------------------------------------
A "No" uttered from deepest conviction is better and greater than a
"Yes" merely uttered to please, or what is worse, to avoid trouble.
-- Mahatma Ghandi
--------------------------- -----------------------------------
pj22298@xx.acs.appstate.edu http://xx.acs.appstate.edu/~pj22298