From: Grant Erickson <erick205@umn.edu>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mkfs.jffs2: creating dirs in /
Date: Fri, 20 Jun 2008 09:22:50 -0700 [thread overview]
Message-ID: <C481276A.FE21%erick205@umn.edu> (raw)
In-Reply-To: <8bd0f97a0806200828u2aefc887n37cb48b4cf75528b@mail.gmail.com>
On 6/20/08 8:28 AM, Mike Frysinger wrote:
> with older mtd-utils, creating a directory in the root worked fine.
> with current git, the parent dir search algo breaks this.
>
> for example, just take the current git tree, build it up, and then run:
> $ ./mkfs.jffs2 -d . -D device_table.txt -o /dev/null
> mkfs.jffs2: skipping device_table entry '/dev': no parent directory!
> mkfs.jffs2: skipping device_table entry '/dev/mem': no parent directory!
> ...
> doing `mkdir dev` first works around the issue, but where's the fun in that.
>
> locally i just made the change to interpret_table_entry() where it
> looks to see if the dir is "/" and if so, uses "root" rather than
> calling find_filesystem_entry(), but i dont think that's the right
> long term fix. i pondered the find_filesystem_entry() function for a
> while, but the closest i found was to delete the first if statement
> and then tweak the fullname[len] ...
> -mike
Mike,
I just submitted several patches earlier last week to fix what appears to be
a similar issue:
See:
http://lists.infradead.org/pipermail/linux-mtd/2008-June/021997.html
http://lists.infradead.org/pipermail/linux-mtd/2008-June/022008.html
http://lists.infradead.org/pipermail/linux-mtd/2008-June/022058.html
Have you picked/merged up these changes from GIT?
Regards,
Grant
next prev parent reply other threads:[~2008-06-20 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 15:28 mkfs.jffs2: creating dirs in / Mike Frysinger
2008-06-20 16:22 ` Grant Erickson [this message]
2008-06-20 16:25 ` Mike Frysinger
2008-12-23 10:54 ` [PATCH] mkfs.jffs2: fix dir creation " Mike Frysinger
2008-12-26 12:38 ` Artem Bityutskiy
2008-12-27 3:35 ` Mike Frysinger
2008-12-27 12:25 ` Artem Bityutskiy
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=C481276A.FE21%erick205@umn.edu \
--to=erick205@umn.edu \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.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