public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: David Schleef <ds@schleef.org>
Cc: joakim.tjernlund@lumentis.se, mtd@infradead.org
Subject: Re: JFFS2 as root FS
Date: Mon, 23 Apr 2001 12:04:16 +0100	[thread overview]
Message-ID: <22604.988023856@redhat.com> (raw)
In-Reply-To: <20010423040017.A22290@stm.lbl.gov>


ds@schleef.org said:
>  I meant to say that mkfs.jffs2 did not handle hard links properly,
> because I didn't see evidence of a hard link cache in the code. Is
> that true, or no? 

That is true. Nobody's yet written the code to notice hard links in the
source directory and put appropriate hard links in the created JFFS2
filesystem.

Note that once you realise you only need to keep a cache of (dev,inode)
tuples for inodes with i_nlink > 1, rather than every inode you touch, and 
that you only need to look into that cache when you're writing out such an 
inode, it becomes a much more feasible task.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-04-23 11:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19  9:21 cramfs and mtd Bjorn Wesen
2001-04-19 11:33 ` David Woodhouse
2001-04-19 13:44   ` mkfs.jffs2 again Joakim Tjernlund
2001-04-19 13:52     ` David Woodhouse
2001-04-19 13:56       ` Joakim Tjernlund
2001-04-19 20:06       ` JFFS2 as root FS Joakim Tjernlund
2001-04-20 16:26         ` David Woodhouse
2001-04-21  8:07           ` Joakim Tjernlund
2001-04-21 11:22             ` David Woodhouse
2001-04-21 20:22               ` Joakim Tjernlund
2001-04-23  1:52                 ` David Schleef
2001-04-23  6:15                   ` Joakim Tjernlund
2001-04-23  9:28                   ` Joakim Tjernlund
2001-04-23  9:31                     ` David Woodhouse
2001-04-23 11:00                       ` David Schleef
2001-04-23 11:04                         ` David Woodhouse [this message]
2001-04-24  1:56                           ` David Schleef
2001-04-21 12:08             ` David Woodhouse
2001-04-21 20:14               ` Joakim Tjernlund
2001-04-21 22:18                 ` David Woodhouse
     [not found] <3AE43929.3695C91D@daniel.com>
2001-04-24 12:22 ` Joakim Tjernlund
  -- strict thread matches above, loose matches on Subject: below --
2001-04-18 20:33 Williams, Kevin M.
2001-04-18  8:02 A pair of stupid questions, I hope David Woodhouse
2001-04-18 16:41 ` JFFS2 as root FS Joakim Tjernlund
2001-04-18 16:50   ` David Woodhouse
2001-04-18 17:00     ` Joakim Tjernlund
2001-04-18 17:05       ` David Woodhouse
2001-04-18 18:58         ` Joakim Tjernlund
2001-04-18 17:11   ` Vipin Malik
2001-04-18 19:24     ` Joakim Tjernlund
2001-04-18 20:19       ` Vipin Malik
2001-04-18 22:00         ` Joakim Tjernlund
2001-04-19  8:28           ` Florian Schirmer / TayTron
2001-04-19 10:26         ` Joakim Tjernlund
2001-04-19 13:02           ` Florian Schirmer / TayTron
2001-04-19 12:45             ` Joakim Tjernlund
2001-04-19 13:02               ` David Woodhouse
2001-04-19 14:55                 ` Nicolas Pitre
2001-04-19 16:44           ` Vipin Malik
2001-04-19 19:59             ` Joakim Tjernlund

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=22604.988023856@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=ds@schleef.org \
    --cc=joakim.tjernlund@lumentis.se \
    --cc=mtd@infradead.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