From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: MTD <linux-mtd@lists.infradead.org>
Subject: Re: mkfs.jffs2 and hard links
Date: Mon, 14 Apr 2003 21:14:54 +0200 [thread overview]
Message-ID: <20030414191453.GC12740@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <3E9AF4CA.9040807@imc-berlin.de>
On Mon, 14 April 2003 19:50:02 +0200, Steven Scholz wrote:
>
> are you guys working on full hard link support for mkfs.jffs2?
Not that I had heard about it.
> The man page states
>
> "mkfs.jffs2 does not properly handle hard links in the input
> directory structure. Currently, hard linked files will be expanded
> to multiple identical files in the output image."
>
> Is that going to change?
I hope so. Do you volunteer? :)
Jörn
--
With a PC, I always felt limited by the software available. On Unix,
I am limited only by my knowledge.
-- Peter J. Schoenster
prev parent reply other threads:[~2003-04-14 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 17:50 mkfs.jffs2 and hard links Steven Scholz
2003-04-14 19:14 ` Jörn Engel [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=20030414191453.GC12740@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=steven.scholz@imc-berlin.de \
/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