From: Ross Younger <wry@ecoscentric.com>
To: sandeep <shimple0@yahoo.com>
Cc: "ecos-devel@ecos.sourceware.org" <ecos-devel@ecos.sourceware.org>
Subject: Re: Should hard links to directories work?
Date: Wed, 20 May 2009 14:47:00 -0000 [thread overview]
Message-ID: <4A14180C.9060801@ecoscentric.com> (raw)
In-Reply-To: <442798.53859.qm@web112517.mail.gq1.yahoo.com>
sandeep wrote:
> Before we discuss it further, where/how do you think you will use directory hardlinking ...
I don't have a use for it :-) - I only ask as I'm integrating the YAFFS
filesystem (see discussion elsewhere on these lists...) and thought of the
question while writing test cases.
FWIW, the only time I've ever come across directory hardlinks being useful
is in a chroot on a standard Unix system where it's sometimes a good idea to
nobble '..' (usually to be the same as '.') to preclude one of the standard
gaol-escape tricks.
> ... if it were available for normal user?
Remember that eCos has no concept of users. Everything runs in the kernel -
everything is privileged, arguably higher than the 'root' user of the
standard Unix model.
Ross
--
Embedded Software Engineer, eCosCentric Limited.
Barnwell House, Barnwell Drive, Cambridge CB5 8UU, UK.
Registered in England no. 4422071. www.ecoscentric.com
next prev parent reply other threads:[~2009-05-20 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 14:21 sandeep
2009-05-20 14:47 ` Ross Younger [this message]
2009-05-20 16:00 ` Rutger Hofman
2009-05-20 16:35 ` Nick Garnett
-- strict thread matches above, loose matches on Subject: below --
2009-05-20 12:28 Ross Younger
2009-05-20 13:45 ` Bart Veer
2009-05-20 13:52 ` Gary Thomas
2009-05-20 14:42 ` Ross Younger
2009-05-20 16:56 ` Jonathan Larmour
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=4A14180C.9060801@ecoscentric.com \
--to=wry@ecoscentric.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=shimple0@yahoo.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).