From: Cheng yong <cheng_lucia@yahoo.com>
To: roland <for_spam@gmx.de>, user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML hangs at "INIT: Entering runlevel: 3"
Date: Sun, 23 May 2004 13:46:12 -0700 (PDT) [thread overview]
Message-ID: <20040523204612.92053.qmail@web40507.mail.yahoo.com> (raw)
In-Reply-To: <093201c440eb$e3d7a7f0$2000000a@schlepptopp>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 250 bytes --]
Hi,
in the attachment is the whole output of UML-Session.
best regards
Lucia
__________________________________
Do you Yahoo!?
Yahoo! Domains Claim yours for only $14.70/year
http://smallbusiness.promotions.yahoo.com/offer
[-- Attachment #2: error.log --]
[-- Type: application/octet-stream, Size: 5428 bytes --]
next parent reply other threads:[~2004-05-23 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <093201c440eb$e3d7a7f0$2000000a@schlepptopp>
2004-05-23 20:46 ` Cheng yong [this message]
2004-05-25 15:23 ` [uml-devel] UML hangs at "INIT: Entering runlevel: 3" roland
[not found] <20040522104051.40285.qmail@web40507.mail.yahoo.com>
2004-05-22 18:42 ` BlaisorBlade
2004-05-23 2:01 ` roland
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=20040523204612.92053.qmail@web40507.mail.yahoo.com \
--to=cheng_lucia@yahoo.com \
--cc=for_spam@gmx.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