From: Jeff Dike <jdike@addtoit.com>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] 2.6.21.5 crashes [was link failure, multiple definition of 'in6addr_any']
Date: Fri, 3 Aug 2007 14:29:21 -0400 [thread overview]
Message-ID: <20070803182921.GA8597@c2.user-mode-linux.org> (raw)
In-Reply-To: <46AF757F.9080103@nagafix.co.uk>
On Tue, Jul 31, 2007 at 06:46:39PM +0100, Antoine Martin wrote:
> If it doesn't crash on emerge --sync
Nevermind that last, I figured it out.
> (when I reboot it doesn't always crash),
Didn't you say this was 100%? :-) Anyway, it works fine here.
> try building something big (like glibc or gcc: emerge glibc gcc)
That's running as I type, apparently happily.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-08-03 18:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 11:05 [uml-devel] link failure, multiple definition of 'in6addr_any' Antoine Martin
2007-07-13 16:05 ` Jeff Dike
2007-07-13 18:09 ` Antoine Martin
2007-07-13 18:45 ` Jeff Dike
2007-07-31 17:46 ` [uml-devel] 2.6.21.5 crashes [was link failure, multiple definition of 'in6addr_any'] Antoine Martin
2007-08-03 17:53 ` Jeff Dike
2007-08-09 12:17 ` Antoine Martin
2007-08-03 18:29 ` Jeff Dike [this message]
2007-08-07 15:21 ` Jeff Dike
2007-08-07 16:04 ` Antoine Martin
2007-08-15 14:58 ` Antoine Martin
2007-08-16 14:57 ` Antoine Martin
2007-08-22 18:59 ` Jeff Dike
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=20070803182921.GA8597@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=antoine@nagafix.co.uk \
--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.