public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: kyak <bas@bmail.ru>
To: linux-mtd@lists.infradead.org
Subject: Re: output file cannot be in the UBIFS root directory check is not working quite well
Date: Fri, 5 Oct 2012 19:57:52 +0400 (MSK)	[thread overview]
Message-ID: <alpine.LNX.2.02.1210051949390.1375@bas> (raw)
In-Reply-To: <alpine.LNX.2.02.1210032322590.1375@bas>

I think the fact that i created that example directories in /tmp is 
misleading. 
This is not a tmpfs problem.

I observe the same problem with any other directory (namely, with my 
/home, which is not reabable).

When one of the directories in "-d" hierarchy is not readable, mkfs.ubifs 
will fail all the time, thinking that the output file is located in UBIFS 
root directory.

On Wed, 3 Oct 2012, kyak wrote:

> Hi,
>
> Consider the following sequence of commands:
>
> cd ~
> mkdir -p /tmp/wtf/wtf1
> chmod u-r /tmp/wtf
> mkfs.ubifs -m 4096 -e 516096 -c 4095 -d /tmp/wtf/wtf1 -o mytest.img
> Error: output file cannot be in the UBIFS root directory
>
> mytest.img is not inside /tmp/wtf/wtf1, but mkfs.ubifs fails because /tmp/wtf 
> is not readable.
> It seems that implementation of in_path(..) in mkfs.ubifs.c is not quite 
> correct to handle this type of situations.
>
> If you are wondering, my /home is not readable, and this prevents me from 
> building any ubifs image inside of /home/user.
>
> Thanks in advance.
>

  reply	other threads:[~2012-10-05 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 19:30 output file cannot be in the UBIFS root directory check is not working quite well kyak
2012-10-05 15:57 ` kyak [this message]
2012-10-08 13:57   ` Ricard Wanderlof
2012-10-08 14:40     ` kyak
2012-10-08 14:53       ` Ricard Wanderlof
2012-10-08 15:13         ` kyak
2012-10-10 14:55           ` kyak
2012-10-11  6:01             ` 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=alpine.LNX.2.02.1210051949390.1375@bas \
    --to=bas@bmail.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox