From: Christoph Rohland <cr@sap.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "Tom Brusehaver (N-Sysdyne Corporation)"
<Thomas.Brusehaver@lmco.com>,
linux-kernel@vger.kernel.org
Subject: Re: shm_open doesn't work (fix maybe).
Date: 25 Apr 2001 09:08:32 +0200 [thread overview]
Message-ID: <m3g0exa233.fsf@linux.local> (raw)
In-Reply-To: <3AE5ADDC.A7AA6F51@lmco.com> <20010424130140.P9725@devserv.devel.redhat.com>
In-Reply-To: <20010424130140.P9725@devserv.devel.redhat.com>
Hi,
On Tue, 24 Apr 2001, Jakub Jelinek wrote:
> On Tue, Apr 24, 2001 at 11:46:20AM -0500, Tom Brusehaver (N-Sysdyne
> Corporation) wrote:
>>
>> I have been chasing all around trying to find out why
>> shm_open always returns ENOSYS. It is implemented
>> in glibc-2.2.2, and seems the 2.4.3 kernel knows about
>> shmfs.
>>
>> It seems the file linux/mm/shmem.c has:
>> #define SHMEM_MAGIC 0x01021994
>>
>> And the glibc-2.2.2/sysdeps/unix/sysv/linux/linux_fsinfo.h has:
>> #define SHMFS_SUPER_MAGIC 0x02011994
>>
>> Well, which is correct?
>
> Update your glibc, 2.2.3pre* matches 2.4.x kernel:
>
> 2001-03-03 Ulrich Drepper <drepper@redhat.com>
>
> * sysdeps/unix/sysv/linux/linux_fsinfo.h (SHMFS_SUPER_MAGIC):
> Update for real 2.4 kernels.
Yes, and I apologize to Ulrich that the changed number slipped through
to the official kernel. My fault.
Greetings
Christoph
prev parent reply other threads:[~2001-04-25 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 16:46 shm_open doesn't work (fix maybe) Tom Brusehaver (N-Sysdyne Corporation)
2001-04-24 17:01 ` Jakub Jelinek
2001-04-25 7:08 ` Christoph Rohland [this message]
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=m3g0exa233.fsf@linux.local \
--to=cr@sap.com \
--cc=Thomas.Brusehaver@lmco.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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.