On Thu, Sep 3, 2015 at 3:04 PM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
On 09/03/2015 02:55 AM, Hardik A Gohil wrote:
>>> Actually I am creating a script to generate the root.ubifs separately
>>> from environment
>>
>> Why?

> We have another team who adds applications to root and generates RFS.

I suggest you don't convert your platform-.../root into a UBIFS, this is
for nfsroot purposes only. In new ptxdist the debug symbols are placed
there, too.

I see two options:
Let ptxdist generate a tar.gz of the rootfs. The rootfs has proper
owner/permissions and device node inside. You can do what ever you want
with this.


Yes now I am generating tar.gz of the rootfs and passing the tar ball to other team to add the application.
 and they are generating root.ubifs using the following script
-----------------------------------------------------------------------------
LEB_SIZE="126976"
MINIMUM_IO_UNIT_SIZE="2048"
MAX_LEB_COUNT="3929"
EXTRA_ARGS=" -F"
ROOTFS=root.ubifs
FS_SOURCE_PATH=$HOME/Downloads/root
#FS_SOURCE_PATH=$HOME/tmp
MKFS_UBIFS=/opt/PHYTEC_BSPs/phyCORE-AM335x-PD13.1.2/platform-phyCORE-AM335x/sysroot-host/sbin/mkfs.ubifs

$MKFS_UBIFS -d $FS_SOURCE_PATH -e $LEB_SIZE -m $MINIMUM_IO_UNIT_SIZE -c $MAX_LEB_COUNT $EXTRA_ARGS -o $ROOTFS
---------------------------------------------------------------------------------

After root.ubifs loaded to target permissions are missing in few folders.   

Another option is that the other team gives you a tarball of the
applications and you install it with "install_archive", see
"rules/post/install.make".

Marc

--
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


--
ptxdist mailing list
ptxdist@pengutronix.de




--
Regards
Hardik A Gohil
Willowglen Msc Bhd