All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent@xensource.com>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: Vincent Hanquez <vincent@xensource.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] libxc portability fixes
Date: Wed, 19 Sep 2007 17:41:17 +0200	[thread overview]
Message-ID: <20070919154117.GA9213@snarc.org> (raw)
In-Reply-To: <200709191704.35189.Christoph.Egger@amd.com>

On Wed, Sep 19, 2007 at 05:04:35PM +0200, Christoph Egger wrote:
> > solaris has deprecated MAP_ANON as well.
> 
> Oh, SystemV Unix has MAP_ANONYMOUS?
> BSD-Unix only has MAP_ANON.

I've no idea, but I imagine this was deprecated for a reason on 2
very different systems. and looks like HP-UX only has MAP_ANONYMOUS.

some random google searching:
http://www.winehq.org/pipermail/wine-devel/2004-December/031636.html

classic unix mess i'ld say :(

> My linux mmap manpage says:
> ---------------------------
>        MAP_ANONYMOUS
>               The  mapping  is not backed by any file; the fd and offset argu-
>               ments are ignored.  The use of this  flag  in  conjunction  with
>               MAP_SHARED is only supported on Linux since kernel 2.4.
> 
>        MAP_ANON
>               Alias for MAP_ANONYMOUS.  Deprecated.
> ---------------------------

Yes, not good indeed.
The text i've pasted come from my linux debian manpage.
you could file a bug to your distro to upgrade the manpages ;)

Cheers,
-- 
Vincent Hanquez

  reply	other threads:[~2007-09-19 15:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 13:19 [PATCH] libxc portability fixes Christoph Egger
2007-09-19 14:25 ` Vincent Hanquez
2007-09-19 14:32   ` Christoph Egger
2007-09-19 14:49     ` Vincent Hanquez
2007-09-19 15:04       ` Christoph Egger
2007-09-19 15:41         ` Vincent Hanquez [this message]
2007-09-19 16:44           ` Keir Fraser
2007-09-19 22:21       ` John Levon
2007-09-20 12:30         ` Vincent Hanquez
2007-09-20 16:41           ` John Levon

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=20070919154117.GA9213@snarc.org \
    --to=vincent@xensource.com \
    --cc=Christoph.Egger@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /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.