From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] SKAS mode not working, x86_64 SMP host, x86_64 guest, problems with noprocmm
Date: Sun, 08 Oct 2006 22:08:45 +0300 [thread overview]
Message-ID: <45294CBD.2010602@linuxbox.cz> (raw)
In-Reply-To: <200610081304.39570.blaisorblade@yahoo.it>
Hello Paolo,
I've spent half a day today trying all variants, and well, I'm no longer
able to reproduce the problem :(
In fact now APPLYING your patch seems to cause the problem, which is of
course weird.
So please consider this false bugreport until I'm able to find out how
the hell did I manage to do it.
If I'm reading my confusing posts to this list, I'm starting to feel a
bit stupid, sorry for them :-/
I'll certainly have to track all my attempts and compilations, as I'm
having quite a mess in it then...
n.
> Since you've said that that patch does not fix pcap compilation, post the
> compilation error (both with and without the patch) so I know what happens
> there. Assuming that pcap compiles on your system for stable kernels (i.e.
> libpcap.a is installed), as you imply in your report.
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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:[~2006-10-08 19:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 16:30 [uml-devel] SKAS mode not working, x86_64 SMP host, x86_64 guest, problems with noprocmm Nikola Ciprich
2006-09-30 21:49 ` Jeff Dike
2006-09-30 22:11 ` Nikola Ciprich
2006-09-30 23:57 ` Jeff Dike
2006-10-01 0:04 ` Nikola Ciprich
2006-10-01 0:08 ` Nikola Ciprich
2006-10-01 0:19 ` Nikola Ciprich
2006-10-01 0:45 ` Nikola Ciprich
2006-10-01 15:08 ` [uml-devel] SKAS mode not working, x86_64 SMP host, x86_64 guest , " Blaisorblade
2006-10-01 15:25 ` [uml-devel] SKAS mode not working, x86_64 SMP host, x86_64 guest, " Blaisorblade
2006-10-01 15:51 ` Nikola Ciprich
2006-10-01 21:00 ` Nikola Ciprich
2006-10-05 11:33 ` Blaisorblade
2006-10-08 11:04 ` Blaisorblade
2006-10-08 19:08 ` Nikola Ciprich [this message]
2006-10-08 19:30 ` Blaisorblade
2006-10-08 20:01 ` Nikola Ciprich
2006-10-14 0:23 ` Blaisorblade
2006-10-14 9:23 ` Nikola Ciprich
2006-10-15 17:35 ` [uml-devel] SKAS mode not working, x86_64 SMP host, x86_64 guest , " Blaisorblade
2006-10-16 15:02 ` [uml-devel] SKAS mode not working, x86_64 SMP host, x86_64 guest, " Jeff Dike
[not found] ` <1161116486.2709.15.camel@nik-nb>
2006-10-17 23:39 ` [uml-devel] SKAS mode not working, x86_64 SMP host, x86_64 guest , " Blaisorblade
2006-10-18 7:40 ` Nikola Ciprich
2006-10-18 18:56 ` Jeff Dike
2006-10-05 20:14 ` [uml-devel] SKAS mode not working, x86_64 SMP host, x86_64 guest, " Blaisorblade
2006-10-07 14:27 ` Nikola Ciprich
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=45294CBD.2010602@linuxbox.cz \
--to=nikola.ciprich@linuxbox.cz \
--cc=blaisorblade@yahoo.it \
--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.