Re: do_rootfs file or not to file....

[Koen Kooi <k.kooi@student.utwente.nl>]

Patrick Fischer wrote:
> Hello oe
>
> maybe i have a email problem. so sorry if you receive this email double.
>
> 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

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
>