public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Emilio Jesús Gallego Arias" <egallego@telefonica.net>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: 
Date: Thu, 26 Aug 2004 13:16:33 +0200	[thread overview]
Message-ID: <1093518993.4567.1.camel@localhost> (raw)

In-Reply-To: <20040826032457.21377e94.akpm@osdl.org>

Andrew Morton wrote:

> (Generally, getting all of userspace to agree on a particular library
> is socially hard [*], but I don't see that as a reason for putting the
> functionality into the kernel)

Implement it in libc?

Really, I don't understand why people want file as directory occur magically.
In Unix we already have files and directories, it's enough.

You can modify libc creat("file", mode) to create a directory layout with a 
file named #content (or whatever special name you want) and attributes are 
files in this directory:

emilio@ellugar:~/tm$ ls -lR
.:
total 4
drwxr-xr-x  2 emilio emilio 4096 2004-08-26 12:58 file

./file:
total 0
-rw-r--r--  1 emilio emilio 0 2004-08-26 12:58 attribute1
-rw-r--r--  1 emilio emilio 0 2004-08-26 12:58 attribute2
-rw-r--r--  1 emilio emilio 0 2004-08-26 12:57 #content

Of course we should modify open, rename, etc... so open("file", ...) will
do open("file/#content", ...), etc.. but no need to touch any filesystem 
and will work on any fs. 

Of course there are lots of questions of being backwars compatible etc, but
no more than doing it in the kernel.

Regards,

Emilio


                 reply	other threads:[~2004-08-26 11:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1093518993.4567.1.camel@localhost \
    --to=egallego@telefonica.net \
    --cc=akpm@osdl.org \
    --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