public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Remi Turk <remi@a2zis.com>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CLONE_NAMESPACE, links for dirs and mount(2) for normal users  questions
Date: Thu, 30 Nov 2000 07:31:48 +0100	[thread overview]
Message-ID: <3A25F454.6ECD3205@a2zis.com> (raw)
In-Reply-To: <3A1FFA2C.A8980FD8@a2zis.com> <20001128211327.K8881@wire.cadcamlab.org>

Peter Samuelson wrote:
> 
> [Remi Turk]
> > Do I understand correctly that this means hardlinks to directories
> > (except . and ..) are fundamentally impossible in Linux?
> 
> Why do you want to be able to do that?  Use symlinks or loopback mounts
> and stay out of trouble.

Probably just because I'm crazy ;-)
Of course I could use symlinks or loopback mounts, but it itn't nearly
as much fun as a directory which really contains itself :-)

> > (I'm thinking about trying to write a garbage collected filesystem
> > with hardlinks to directories.)
> 
> Sounds like a lot of extra complexity.  Is this academic or do you have
> a practical use for it?

Acedemic.
Well, I might find some practical use for it some day.

(I got inspired by an old thread about garbage collecting filesystems
without a clear answer about whether it was possible to write one in
Linux
(http://www.uwsg.indiana.edu/hypermail/linux/kernel/0001.1/0410.html)
and the recent thread  "[BUG] Inconsistent behaviour of rmdir")

> 
> Peter

-- 
Linux 2.4.0-test11-ac4 #1 Tue Nov 28 15:51:01 CET 2000
-
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/

      reply	other threads:[~2000-11-30  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-25 17:43 CLONE_NAMESPACE, links for dirs and mount(2) for normal users questions Remi Turk
2000-11-29  3:13 ` Peter Samuelson
2000-11-30  6:31   ` Remi Turk [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=3A25F454.6ECD3205@a2zis.com \
    --to=remi@a2zis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@cadcamlab.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