All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Gettert <Wolfram.Gettert@mixed-mode.de>
To: linux-mtd@lists.infradead.org
Subject: Bugreport: mkfs.jffs2
Date: Wed,  9 Mar 2005 15:57:03 +0100	[thread overview]
Message-ID: <1110380223.422f0ebf951f5@intern.netexpress.de> (raw)

Hi,
I want to report two bugs on mkfs.jffs2 Revision 1.44

1.
I tried to create a file sytem image with this commandline.

mkfs.jffs2 -l -e 0x20000 -D devtable.txt -d rootfs -o test.img

The file devtable.txt contains a line  

----8<-----
/dev/input   d  755     0       0       -       -       -       -       -
----8<-----

and the rootfs directory contains a directory 

rootfs/dev/input


Of course it is my fault that I put the /dev/input directory in the device table
and in the rootfs. But never the less the result is a jffs2 image which is not
usable. Mounting it on the host with mtdram mtdblock .... freezes the PC and on
the target I cannot mount it too.

So there should be an error message or something like "Omitting directory xyz
from devtable already present"


2.
It is not possible to create a directory with devtable in "/"
Devtable contains this line

/opt   d  755     0       0       -       -       -       -       -

I get this message:

mkfs.jffs2: skipping device_table entry '/opt': no parent directory!



Please put me on CC, I am not subscribed to list.

Wolfram



-- 
Dipl.-Ing.
Wolfram Gettert

Software Engineer Embedded Systems

Mixed Mode GmbH
Lochhamer Schlag 17                   D-82166 Gräfelfing/München
Tel. +49-89-89868.0                   Fax +49-89-89868.222
mailto:Wolfram.Gettert@mixed-mode.de  http://www.mixed-mode.de

Mixed Mode - Your Partner for Systems Engineering!

             reply	other threads:[~2005-03-09 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 14:57 Wolfram Gettert [this message]
2005-03-10 13:02 ` Bugreport: mkfs.jffs2 Steven Scholz
2005-03-10 13:23 ` Artem B. Bityuckiy

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=1110380223.422f0ebf951f5@intern.netexpress.de \
    --to=wolfram.gettert@mixed-mode.de \
    --cc=linux-mtd@lists.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.