Re: Possible generation of damaged initrd / lilo problem

To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: debian-boot@lists.debian.org
Subject: Re: Possible generation of damaged initrd / lilo problem
From: Delian Krustev <krustev@krustev.net>
Date: Mon, 15 Mar 2004 17:07:38 +0200
Message-id: <[🔎] 200403151707.38636.krustev@krustev.net>
In-reply-to: <[🔎] 20040312234801.GA6865@gondor.apana.org.au>
References: <[🔎] 200403120424.37163.krustev@krustev.net> <[🔎] 200403130144.28929.krustev@krustev.net> <[🔎] 20040312234801.GA6865@gondor.apana.org.au>

On Saturday 13 March 2004 01:48, Herbert Xu wrote:

> Make sure that you have dash 0.4.24 and regenerate the initrd image.
>
> Please let me know If the problem persists.

Thank You!
That was it.

Reply to:

References:
- Weird problem after kernel/lilo upgrade
  - From: Delian Krustev <krustev@krustev.net>
- Possible generation of damaged initrd / lilo problem
  - From: Delian Krustev <krustev@krustev.net>
- Re: Possible generation of damaged initrd / lilo problem
  - From: Herbert Xu <herbert@gondor.apana.org.au>

Prev by Date: GDM pas reconnu :(!
Next by Date: Re: release status
Previous by thread: Re: Possible generation of damaged initrd / lilo problem
Next by thread: Bug#237565: discover: Discover should not depend on ash
Index(es):
- Date
- Thread