From: Nix <nix@esperi.org.uk>
To: bugzilla-daemon@gentoo.org
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [Bug 49277] Compile of usermode-sources-2.6.x fails
Date: Tue, 07 Jun 2005 15:31:40 +0100 [thread overview]
Message-ID: <87psuy5jcj.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <E1DfSPm-0008Vv-Va@nuthatch.gentoo.org> (bugzilla-daemon@gentoo.org's message of "Tue, 07 Jun 2005 00:57:58 +0000")
On Tue, 07 Jun 2005, bugzilla-daemon@gentoo.org gibbered uncontrollably:
> Ok, I hope there is still somebody using UML on a NPTL-only system. The
> workaround suggested last time was to avoid enabling CONFIG_MODE_TT; now I
> think I've got over this problem, too. So, when I release 2.6.11.8-bs6 (which
> will happen very shortly, I hope), I'd like to get some testing from you about
> this issue.
I can give it a try if you like.
(That's a MODE_TT build on a system with NPTL headers, right?)
--
`It's as bizarre an intrusion as, I don't know, the hobbits coming home
to find that the Shire has been taken over by gangsta rappers.'
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
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:[~2005-06-07 14:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-49277@bugs.gentoo.org>
2005-06-07 0:57 ` [uml-devel] [Bug 49277] Compile of usermode-sources-2.6.x fails bugzilla-daemon
2005-06-07 14:31 ` Nix [this message]
2005-06-07 14:52 ` Blaisorblade
2005-06-07 15:54 ` Nix
2005-06-07 16:11 ` Blaisorblade
2005-06-07 16:21 ` Nix
2005-06-07 16:44 ` Blaisorblade
2005-06-07 19:47 ` Nix
2005-06-08 0:34 ` Blaisorblade
2005-06-08 17:38 ` Nix
2005-06-08 18:10 ` Blaisorblade
2005-06-09 22:08 ` Blaisorblade
2005-06-07 16:52 ` Blaisorblade
2005-06-07 16:02 ` Nix
2005-07-06 9:57 ` bugzilla-daemon
2005-07-06 16:22 ` bugzilla-daemon
2005-07-09 22:41 ` bugzilla-daemon
2005-07-12 17:13 ` bugzilla-daemon
2005-07-13 15:14 ` bugzilla-daemon
2005-07-14 8:11 ` bugzilla-daemon
2005-07-14 19:57 ` Rob Landley
2005-07-14 20:22 ` Rob Landley
2005-07-14 8:12 ` bugzilla-daemon
2005-07-14 8:39 ` bugzilla-daemon
2005-07-14 8:40 ` bugzilla-daemon
2005-05-08 11:55 bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2005-04-30 0:41 bugzilla-daemon
2005-04-28 16:26 bugzilla-daemon
2005-04-13 15:50 bugzilla-daemon
2005-04-08 18:01 bugzilla-daemon
2005-03-19 20:54 bugzilla-daemon
2005-03-02 23:28 bugzilla-daemon
2005-03-02 15:04 bugzilla-daemon
2005-02-18 13:05 bugzilla-daemon
2005-02-09 21:58 bugzilla-daemon
2005-02-09 15:38 bugzilla-daemon
2005-02-10 3:40 ` Rob Landley
2005-02-10 11:31 ` Blaisorblade
2005-02-10 14:16 ` Rob Landley
2005-02-10 15:44 ` Blaisorblade
2005-02-11 0:31 ` Rob Landley
2005-02-11 2:33 ` Blaisorblade
2005-02-11 2:42 ` Rob Landley
2005-02-11 3:48 ` Blaisorblade
2005-01-12 1:24 bugzilla-daemon
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=87psuy5jcj.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=bugzilla-daemon@gentoo.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.