From: Hardik A Gohil <hardik@willowglen.com.my>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Script
Date: Thu, 3 Sep 2015 15:46:44 +0800 [thread overview]
Message-ID: <CAEZH62O3m+Aq2RVM56rSe-Acgo8yWzShxa1eBCjVv9YXprjHtg@mail.gmail.com> (raw)
In-Reply-To: <55E7F8D4.9070003@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1543 bytes --]
On Thu, Sep 3, 2015 at 3:37 PM, Marc Kleine-Budde <mkl@pengutronix.de>
wrote:
> On 09/03/2015 09:20 AM, Hardik A Gohil wrote:
> >> 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.
>
> Are you using ptxdist to generate the tar.gz?
>
Yes first i am generating tar.gz file using ptxdist.
>
> > 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.
>
> Are you extracting the tarball and creating the ubifs in one go in a
> fakeroot environment?
>
Then extract the root.tgz , add applications and create the root.ubifs
image using the above script.
>
>
--
Regards
Hardik A Gohil
Willowglen Msc Bhd
[-- Attachment #1.2: Type: text/html, Size: 2537 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-09-03 7:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 7:44 Hardik A Gohil
2015-09-02 8:17 ` Marc Kleine-Budde
2015-09-02 8:35 ` Hardik A Gohil
2015-09-02 8:46 ` Marc Kleine-Budde
2015-09-02 8:54 ` Hardik A Gohil
2015-09-02 9:29 ` Marc Kleine-Budde
2015-09-03 0:55 ` Hardik A Gohil
2015-09-03 7:04 ` Marc Kleine-Budde
2015-09-03 7:20 ` Hardik A Gohil
2015-09-03 7:37 ` Marc Kleine-Budde
2015-09-03 7:46 ` Hardik A Gohil [this message]
2015-09-03 7:49 ` Marc Kleine-Budde
2015-09-03 9:50 ` Hardik A Gohil
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=CAEZH62O3m+Aq2RVM56rSe-Acgo8yWzShxa1eBCjVv9YXprjHtg@mail.gmail.com \
--to=hardik@willowglen.com.my \
--cc=ptxdist@pengutronix.de \
/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