From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] tmpfs for 2.4.1
Date: 1 Feb 2001 15:50:02 -0800 [thread overview]
Message-ID: <95csna$vb6$1@cesium.transmeta.com> (raw)
In-Reply-To: <20010123205315.A4662@werewolf.able.es> <m3lmrqrspv.fsf@linux.local>
Followup to: <m3lmrqrspv.fsf@linux.local>
By author: Christoph Rohland <cr@sap.com>
In newsgroup: linux.dev.kernel
>
> Hi,
>
> here is the latest version of my tmpfs patch against 2.4.1
>
> Have fun
> Christoph
>
> diff -uNr 2.4.1/Documentation/Changes 2.4.1-tmpfs/Documentation/Changes
> --- 2.4.1/Documentation/Changes Tue Jan 30 11:06:59 2001
> +++ 2.4.1-tmpfs/Documentation/Changes Thu Feb 1 22:04:13 2001
> @@ -114,20 +114,6 @@
> DevFS is now in the kernel. See Documentation/filesystems/devfs/* in
> the kernel source tree for all the gory details.
>
> -System V shared memory is now implemented via a virtual filesystem.
> -You do not have to mount it to use it. SYSV shared memory limits are
> -set via /proc/sys/kernel/shm{max,all,mni}. You should mount the
> -filesystem under /dev/shm to be able to use POSIX shared
> -memory. Adding the following line to /etc/fstab should take care of
> -things:
> -
> -none /dev/shm shm defaults 0 0
> -
> -Remember to create the directory that you intend to mount shm on if
> -necessary (The entry is automagically created if you use devfs). You
> -can set limits for the number of blocks and inodes used by the
> -filesystem with the mount options nr_blocks and nr_inodes.
> -
> The Logical Volume Manager (LVM) is now in the kernel. If you want to
> use this, you'll need to install the necessary LVM toolset.
>
What happened with this being a management tool for shared memory
segments?!
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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-01 23:50 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 [this message]
2001-02-02 9:57 ` Christoph Rohland
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='95csna$vb6$1@cesium.transmeta.com' \
--to=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 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.