From: Christoph Rohland <cr@sap.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] tmpfs for 2.4.1
Date: 02 Feb 2001 10:57:55 +0100 [thread overview]
Message-ID: <m3puh1que4.fsf@linux.local> (raw)
In-Reply-To: <20010123205315.A4662@werewolf.able.es> <m3lmrqrspv.fsf@linux.local> <95csna$vb6$1@cesium.transmeta.com>
In-Reply-To: <95csna$vb6$1@cesium.transmeta.com>
"H. Peter Anvin" <hpa@zytor.com> writes:
> What happened with this being a management tool for shared memory
> segments?!
Unfortunately we lost this ability in the 2.4.0-test series. SYSV shm
now works only on an internal mounted instance and does not link the
directory entry to the deleted state of the segment.
IMNSHO the new implementation is so much cleaner that it was worth
it. Probably we should fix ipcrm to be more flexible.
Greetings
Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-02 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 19:53 swapfs for 2.4.1-pre J . A . Magallon
2001-02-01 21:39 ` [patch] tmpfs for 2.4.1 Christoph Rohland
2001-02-01 23:50 ` H. Peter Anvin
2001-02-02 9:57 ` Christoph Rohland [this message]
2001-02-02 20:52 ` J . A . Magallon
2001-02-02 20:55 ` H. Peter Anvin
2001-02-03 0:06 ` J . A . Magallon
2001-02-03 15:02 ` Christoph Rohland
2001-02-03 14:28 ` Christoph Rohland
2001-02-03 20:27 ` H. Peter Anvin
2001-02-03 20:46 ` J . A . Magallon
2001-02-04 9:53 ` Christoph Rohland
2001-02-04 9:18 ` Christoph Rohland
[not found] ` <20010203234550.A507@squish>
[not found] ` <m3zog2n6ec.fsf@linux.local>
[not found] ` <20010205210540.A10316@squish>
2001-02-06 9:18 ` VM question (ramfs abuse) Christoph Rohland
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=m3puh1que4.fsf@linux.local \
--to=cr@sap.com \
--cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox