This topic may be a few days old, but this is apparently exactly what
happened to a server I admin remotely. When I upgraded to the new
stable packages, I saw nothing that affected the kernel, therefore
rerunning LILO didn't occur to me as something that needed to be done.
Hopefully someone repo
This topic may be a few days old, but this is apparently exactly what
happened to a server I admin remotely. When I upgraded to the new
stable packages, I saw nothing that affected the kernel, therefore
rerunning LILO didn't occur to me as something that needed to be done.
Hopefully someone repo
This topic may be a few days old, but this is apparently exactly what
happened to a server I admin remotely. When I upgraded to the new
stable packages, I saw nothing that affected the kernel, therefore
rerunning LILO didn't occur to me as something that needed to be done.
Hopefully someone r
Florian Ernst wrote:
> MicheleM wrote:
> > all worked fine untill I rebooted the machine and...ooops! The boot
> > loader LILO failed with the "LI" code error.
> > [...]
> > But what did it happen? I think there is a bug somewhere.
>
> lilo should have detected it needed to be re-run and should ha
Hello again,
On Thu, Jun 09, 2005 at 02:54:32PM -0700, MicheleM wrote:
> this is the output:
>
> anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat
> Name: lilo/runme
> Template: lilo/runme
> Owners: lilo
>
> [...]
> no more.
Hm, strange, to me it looks like this question was never a
Hi Flo,
this is the output:
anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat
Name: lilo/runme
Template: lilo/runme
Owners: lilo
Name: lilo/upgrade
Template: lilo/upgrade
Owners: lilo
I grep the upgrade's typescript searching for the lilo prompt but this
is what I found:
anjuna:~# c
Hello *,
On Thu, Jun 09, 2005 at 04:46:32PM -0400, Roberto C. Sanchez wrote:
> Why do people insist on using LILO? Just install grub, [...]
Advocacy is one thing, trying to find out why a bug has occurred
another. Let's try not to mix things up.
Cheers,
Flo
signature.asc
Description: Digital
On Thu, Jun 09, 2005 at 08:08:08PM +0200, Florian Ernst wrote:
> Hello *,
>
> >
> > all worked fine untill I rebooted the machine and...ooops! The boot
> > loader LILO failed with the "LI" code error.
> > No way to boot the machine. I solved the problem with a knoppix live
> > cd, I mounted the r
Hello *,
On Thu, Jun 09, 2005 at 08:23:39AM -0700, MicheleM wrote:
> yesterday I tried to upgrade my Woody production server to Sarge after
> reading and following step by step the relase notes under:
> http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html
>
> all worked fi
Hi there,
yesterday I tried to upgrade my Woody production server to Sarge after
reading and following step by step the relase notes under:
http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html
all worked fine untill I rebooted the machine and...ooops! The boot
loader LILO f
10 matches
Mail list logo
