From: sandeep <shimple0@yahoo.com>
To: "ecos-devel@ecos.sourceware.org" <ecos-devel@ecos.sourceware.org>,
Ross Younger <wry@ecoscentric.com>
Subject: Re: Should hard links to directories work?
Date: Wed, 20 May 2009 14:21:00 -0000 [thread overview]
Message-ID: <442798.53859.qm@web112517.mail.gq1.yahoo.com> (raw)
Hi Ross,
Younger ;) people often have interesting questions and are responsible for fresh insights.
> The Unix world traditionally shuns such things as an abomination.
> The eCos docs are quiet on the subject, as is the code in
> ramfs and jffs2.
> Should they work? Does anybody use them?
Before we discuss it further, where/how do you think you will use directory hardlinking, if it were available for normal user?
Sandeep
next reply other threads:[~2009-05-20 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 14:21 sandeep [this message]
2009-05-20 14:47 ` Ross Younger
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=442798.53859.qm@web112517.mail.gq1.yahoo.com \
--to=shimple0@yahoo.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=wry@ecoscentric.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).