From: Nick Craig-Wood <ncw1@axis.demon.co.uk>
To: user-mode-linux-devel@lists.sourceforge.net,
224431@bugs.debian.org, 224502@bugs.debian.org
Subject: Re: [uml-devel] 2.4.22-[67] problems
Date: Sat, 20 Dec 2003 19:05:19 +0000 [thread overview]
Message-ID: <20031220190519.GA25646@axis.demon.co.uk> (raw)
In-Reply-To: <20031220011323.GW18100@alcor.net>
On Fri, Dec 19, 2003 at 05:13:23PM -0800, Matt Zimmerman wrote:
> There definitely seems to be something awry here, even in skas mode.
> I am getting a lot of ENOSYS errors inside UML:
FYI I had no end of trouble building 2.4.22-7 with Debian testing
(with gcc 2-95). I got it to compile OK (with lots of warnings), but
I couldn't get it to run reliably.
I've changed to building it in a woody chroot and it runs perfectly
now!
> 2. CONFIG_UML_REAL_TIME_CLOCK=y was added to the configuration
Watch out if running on > 2 GHz CPU - see list archives for patch the
UML will hang quite early on.
Sorry not a very scientific report!
--
Nick Craig-Wood
ncw1@axis.demon.co.uk
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2003-12-20 19:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 1:13 [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 17:14 ` Jeff Dike
2003-12-21 0:47 ` Matt Zimmerman
2003-12-21 15:58 ` BlaisorBlade
2003-12-21 22:40 ` Matt Zimmerman
2003-12-21 23:16 ` Matt Zimmerman
2003-12-22 0:25 ` Jeff Dike
2003-12-22 4:08 ` Matt Zimmerman
2003-12-22 5:49 ` Daniel Jacobowitz
2003-12-22 9:08 ` Matt Zimmerman
2004-01-05 17:51 ` Adam Heath
2004-01-05 18:10 ` Matt Zimmerman
2003-12-24 12:48 ` BlaisorBlade
2003-12-21 0:52 ` Matt Zimmerman
2003-12-21 1:06 ` Matt Zimmerman
2003-12-28 9:33 ` Matt Zimmerman
2003-12-28 9:51 ` Matt Zimmerman
2003-12-28 9:52 ` Matt Zimmerman
2004-01-06 2:59 ` Jeff Dike
2003-12-28 10:12 ` Matt Zimmerman
2003-12-28 11:30 ` Matt Zimmerman
2003-12-30 18:43 ` Resolution (Re: [uml-devel] 2.4.22-[67] problems) Matt Zimmerman
2004-01-06 2:58 ` Jeff Dike
2004-01-06 7:41 ` Nuno Silva
2004-01-06 8:02 ` Matt Zimmerman
2004-01-06 8:20 ` Nuno Silva
2004-01-06 8:47 ` Nuno Silva
2004-01-06 9:20 ` Nuno Silva
2004-01-06 17:13 ` Matt Zimmerman
2004-01-09 7:22 ` Nuno Silva
2004-01-08 7:07 ` Matt Zimmerman
2004-01-12 18:36 ` [uml-devel] Panic with slirp transport and gcc 3.3 Matt Zimmerman
2004-01-13 15:25 ` [uml-devel] " Bill Allombert
2004-01-13 17:30 ` Jeff Dike
2004-01-13 17:44 ` Bill Allombert
2004-01-13 18:51 ` Matt Zimmerman
2004-01-16 2:38 ` Jeff Dike
2004-01-16 2:38 ` Matt Zimmerman
2004-01-16 20:04 ` Jeff Dike
2004-01-16 19:49 ` Matt Zimmerman
2004-01-17 0:42 ` Matt Zimmerman
2003-12-21 1:29 ` [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 19:05 ` Nick Craig-Wood [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=20031220190519.GA25646@axis.demon.co.uk \
--to=ncw1@axis.demon.co.uk \
--cc=224431@bugs.debian.org \
--cc=224502@bugs.debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.