linux-um archives
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] problems with ifup-a on etch compiled kernels
Date: Tue, 07 Nov 2006 11:32:38 -0800	[thread overview]
Message-ID: <eiqn0p$c0q$1@sea.gmane.org> (raw)
In-Reply-To: <eiobbh$oq4$1@sea.gmane.org>


A UML built on debian sarge (machine name cassidy), (gcc-3.3.5, libc-2.3.2) works.
The same code built on debian etch (machine name marajade) (gcc-3.3.6 or gcc-4.1.2, glibc-2.3.6) fails.

A kernel built on the cassidy machine runs more successfully on the marajade machine.
It does fail when shutting down, which it didn't on cassidy.

I conclude that it may well be that my host kernel on marade is at fault.





-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2006-11-07 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06  0:29 [uml-devel] problems with ifup-a on etch compiled kernels Michael Richardson
2006-11-06 21:44 ` Michael Richardson
2006-11-06 22:01   ` Michael Richardson
2006-11-07 19:32     ` Michael Richardson [this message]
2006-11-08 18:10   ` Jeff Dike
2006-11-08 23:04     ` Michael Richardson
2006-11-13 21:21     ` Michael Richardson

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='eiqn0p$c0q$1@sea.gmane.org' \
    --to=mcr@sandelman.ca \
    --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