All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rootfs (part 1)
Date: 16 May 2001 21:47:16 +0200	[thread overview]
Message-ID: <m3d7995b5n.fsf@linux.local> (raw)
In-Reply-To: <Pine.GSO.4.21.0105161416120.26191-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0105161416120.26191-100000@weyl.math.psu.edu>

Hi Alexander,

On Wed, 16 May 2001, Alexander Viro wrote:
> Because what I need is an absolute minimum. Heck, I don't even use
> regular files (in the full variant of patch, that is). They might
> become useful, but I can live with mkdir() and mknod().

So what about adding shmem_mknod and shmem_mkdir to the core shmem.c
part? They are now under CONFIG_TMPFS but are only ~20 lines of code.

Greetings
		Christoph



  reply	other threads:[~2001-05-16 19:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16 12:12 [PATCH] rootfs (part 1) Alexander Viro
2001-05-16 14:43 ` Christoph Rohland
2001-05-16 18:23   ` Alexander Viro
2001-05-16 19:47     ` Christoph Rohland [this message]
2001-05-16 23:37   ` Alan Cox
2001-05-16 17:11 ` Linus Torvalds
2001-05-16 17:45   ` Christoph Rohland
2001-05-16 17:55     ` Jeff Garzik
2001-05-16 18:00     ` Linus Torvalds
2001-05-16 18:23       ` David L. Parsley
2001-05-16 18:46       ` Christoph Rohland
2001-05-16 18:33     ` Alexander Viro
2001-05-16 23:49     ` Alan Cox
2001-05-17  6:46       ` Christoph Rohland
2001-05-16 18:48   ` Alexander Viro
2001-05-16 22:21     ` H. Peter Anvin
2001-05-16 23:06       ` Alexander Viro
2001-05-16 23:24         ` H. Peter Anvin
2001-05-16 23:31           ` Alexander Viro
2001-05-16 23:33 ` Alan Cox
2001-05-17  0:10   ` Alexander Viro

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=m3d7995b5n.fsf@linux.local \
    --to=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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.