From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Joshua Hudson <joshudson@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/27] allow hard links to directories, opt-in for any filesystem
Date: Wed, 01 Mar 2006 13:12:03 +1100 [thread overview]
Message-ID: <440502F3.7020203@yahoo.com.au> (raw)
In-Reply-To: <200602281657.k1SGvKFk026965@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
>>Joshua Hudson wrote:
>>
>>>Patch seems to work, might want more testing.
>>>It probably should not be applied without a discussion, especially
>>>as no filesystem in kernel tree wants this. I am working on a fs that does.
>
>
>>This is backwards I think. This is not disallowed because there are
>>no filesystems that want it. Linux doesn't want it so it is disallowed
>>by the vfs.
>
>
> Right.
>
>
>>You have to put forward a case for why we want it, rather than show us
>>your filesystem that "wants" it. Right?
>
>
> Nope.
What do you mean nope?
I know why unix didn't allow loops in the filesystem tree. I'm just
saying that you have to justify a feature before adding it. If he was
able to nicely solve problems with loops and show some application
that benefits from it, then it could be considered for Linux.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-03-01 2:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 6:04 [PATCH 02/27] allow hard links to directories, opt-in for any filesystem Joshua Hudson
2006-02-28 11:52 ` Nick Piggin
2006-02-28 16:57 ` Horst von Brand
2006-03-01 2:12 ` Nick Piggin [this message]
2006-03-02 21:10 ` Jan Engelhardt
2006-02-28 20:09 ` Sam Vilain
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=440502F3.7020203@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=joshudson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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