From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Larsson <alex@cendio.se>
Cc: Bjorn Wesen <bjorn.wesen@axis.com>,
Finn Hakansson <finn.hakansson@axis.com>,
mtd@infradead.org, alan@redhat.com
Subject: Re: JFFS - ready for submission into 2.[34]?
Date: Fri, 02 Jun 2000 09:21:43 +0100 [thread overview]
Message-ID: <28127.959934103@devel2.axiom.internal> (raw)
In-Reply-To: <Pine.LNX.3.96.1000601190835.3413A-100000@biffen.cendio.se>
alex@cendio.se said:
> I will look at it tomorrow at work (Haven't had time before). All
> functionallity should be implemented and work. I haven't done any
> larger scale testing yet though, so it's definitely experimental.
Fine. We all know how to get larger scale testing :)
> There is a bug in the mkfs.jffs program though. It generates too big
> nodes (which the jffs code can't handle) for files that are larger
> than 64k.
I saw the dicussion about this, and was wondering why mkfs.jffs actually
populates the filesystem at all. Is it because it's more space-efficient to
do it all at once than it would be to mkfs, mount and populate it?
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-06-02 8:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 16:25 JFFS - ready for submission into 2.[34]? David Woodhouse
2000-06-01 17:13 ` Alexander Larsson
2000-06-02 8:21 ` David Woodhouse [this message]
2000-06-02 8:26 ` Alexander Larsson
2000-06-02 8:33 ` David Woodhouse
2000-06-02 8:04 ` Alexander Larsson
2000-06-02 9:00 ` Finn Hakansson
2000-06-02 9:34 ` David Woodhouse
2000-06-02 8:39 ` Alexander Larsson
2000-06-05 23:10 ` Bjorn Wesen
2000-06-09 5:42 ` Jason Gunthorpe
2000-06-02 9:07 ` Alexander Larsson
2000-06-04 18:35 ` Stephen Tweedie
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=28127.959934103@devel2.axiom.internal \
--to=dwmw2@infradead.org \
--cc=alan@redhat.com \
--cc=alex@cendio.se \
--cc=bjorn.wesen@axis.com \
--cc=finn.hakansson@axis.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.