From: "Sven Köhler" <skoehler@upb.de>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Using lilo on ubda?
Date: Sat, 26 Nov 2005 23:13:47 +0100 [thread overview]
Message-ID: <dmammg$iem$1@sea.gmane.org> (raw)
In-Reply-To: <200511261303.42684.rob@landley.net>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
> Lilo is saying that ubda is not a device with partitions.
>
> Anybody know what it's talking about? (I've got a ubda1. I'm trying to make
> a disk image I can test boot with qemu without having to boot a knoppix image
> to do it...)
I think, LILO tries to probe which BIOS-device-number it must use for
ubda. You can try to tell LILO manually. (Take a look at man lilo, i
remember that i've done this once a long time ago, but i don't know the
syntax anymore).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2005-11-26 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 19:03 [uml-devel] Using lilo on ubda? Rob Landley
2005-11-26 22:13 ` Sven Köhler [this message]
2005-11-27 0:36 ` [uml-devel] " Sven Köhler
2005-11-27 5:22 ` [uml-devel] " Andreas Wohlfeld
2005-11-27 12:47 ` Rob Landley
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='dmammg$iem$1@sea.gmane.org' \
--to=skoehler@upb.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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