public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Andersen <rasmus@avlebavle.dk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LILO fatal error after going from 2.6.22 to 2.6.24.2
Date: Tue, 19 Feb 2008 20:55:13 +0100	[thread overview]
Message-ID: <20080219195513.GA25217@avlebavle.dk> (raw)
In-Reply-To: <47BB1053.60409@zytor.com>

On Tue, Feb 19, 2008 at 09:22:27AM -0800, H. Peter Anvin wrote:
> Rasmus Andersen wrote:
[...]
> You have at least one file on a device mapper device (possibly an LVM 
> module), and LILO doesn't understand it.

Hi Peter, and thanks for your reply. That was indeed the issue, my /boot
was not mounted and my / is on a LVM partition. So this was merely a
user issue, my specialty.

Thanks for your time.

Cheers,
  Rasmus

      reply	other threads:[~2008-02-19 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19  7:02 LILO fatal error after going from 2.6.22 to 2.6.24.2 Rasmus Andersen
2008-02-19 17:22 ` H. Peter Anvin
2008-02-19 19:55   ` Rasmus Andersen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080219195513.GA25217@avlebavle.dk \
    --to=rasmus@avlebavle.dk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox