All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick Fischer" <Patrick_Fischer@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: do_rootfs file or not to file....
Date: Tue, 13 May 2008 12:14:54 +0200	[thread overview]
Message-ID: <20080513101454.160080@gmx.net> (raw)
In-Reply-To: <g01pfj$o6j$1@ger.gmane.org>

> > We have a strange do_rootfs problem.
> > After update to Ubuntu 8.04 and debian testing we can't run do_rootfs
> anymore.
> >
> > Sometimes it is a file which is no file or a dir which is not a dir:
> 
> Sound like fakeroot issues, you have 2 options to 'fix' it:
> 
> * cat /dev/urandom > /dev/zero while doing do_rootfs
> * upgrade the fakeroot-native recipe

fakeroot 1.7.1 seems to work fine.

Thanks
Patrick





> 
> regards,
> 
> Koen
> 
> 
> >
> > In this case a dir was created with mkdir and the next ls -l line shows
> that
> > it is a file:
> >
> > ######
> > + rm -rf /usr/src/trunk/projects/base/build/tmp/rootfs/../rootfs_2/
> > + mkdir -p /usr/src/trunk/projects/base/build/tmp/rootfs/../rootfs_2/
> > + ls -l /usr/src/trunk/projects/base/build/tmp/rootfs/../rootfs_2/
> > -rwxr-xr-x 2 root root 4096 May  8
> > 14:03 /usr/src/trunk/projects/base/build/tmp/rootfs/../rootfs_2/
> > +
> > cp -r /usr/src/trunk/projects/base/build/tmp/rootfs/usr/local/
> /usr/src/trunk/projects/base/build/tmp/rootfs/../rootfs_2/
> > cp: target `/usr/src/trunk/projects/base/build/tmp/rootfs/../rootfs_2/'
> is not
> > a directory
> > ######
> >
> > Also it could be inverted. A file copied by cp is a dir.
> >
> > ######
> > mkfs.jffs2 -x
> > lzo --root=/usr/src/trunk/projects/base/build/tmp/rootfs/../rootfs_2/
> --faketime
> --output=/usr/src/trunk/projects/base/build/tmp/deploy/images/rootfs.jffs2 --little-endian -e
> > 128 --pad=27131904
> > mkfs.jffs2: opening
> > directory
> /usr/src/trunk/projects/base/build/tmp/rootfs_2/lib/libblaconfig.so.0:
> > Not a directory
> > ######
> >
> > The really strange thing is that if I run
> > the
> /usr/src/trunk/projects/base/build/tmp/work/boxr5-1.0-r0/temp/run.do_rootfs.12648
> > by hand, it works fine. The Problem is not always at the same line!!
> >
> > I read something about "switch from RiserFS to ext3" but I have ext3.
> > /bin/sh is bash
> >
> > I'm not sure but the scripts are called from within python??
> > The workstation which failed are using Python 2.5.2.
> > Python 2.4.4 ->  works
> > Python 2.5.2 ->  fails
> >
> > I'm not allown, in this Forum some people have the same problem:
> >
> http://www.dream-multimedia-tv.de/board/thread.php?postid=17280#post17280
> >
> > Maybe somebody knows a fix.
> >
> > Best Regards
> > Patrick Fischer
> >
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer



      reply	other threads:[~2008-05-13 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 15:02 do_rootfs file or not to file Patrick Fischer
2008-05-09 15:09 ` Koen Kooi
2008-05-13 10:14   ` Patrick Fischer [this message]

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=20080513101454.160080@gmx.net \
    --to=patrick_fischer@gmx.de \
    --cc=openembedded-devel@lists.openembedded.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.