All of lore.kernel.org
 help / color / mirror / Atom feed
From: LogiSch17 <logi.tss@hotmail.de>
To: buildroot@busybox.net
Subject: [Buildroot] Shell scripts does not emit finished() to QProcess
Date: Tue, 14 Feb 2017 05:43:18 -0800 (PST)	[thread overview]
Message-ID: <1487079798716-157008.post@n4.nabble.com> (raw)
In-Reply-To: <ce6994a6-76f7-a075-51b6-e80dc306cdd8@gmail.com>

I guess now that the problem could be because I have my /var on a data
partition.
I created a complete image with the following partition tabel:
1 boot /boot
2 fs1 /
3 fs2
4 data /var

the second fs is cause i have a function where I update whole fs.ext4 to the
second fs partition and change the config.txt  on boot to mmcblk0p3.

And i changed the partition table at the same commit as i updated to
buildroot 2016.11. Afterwards the QProcess was never finished.

So i think there could be the problem with the /var. Does that make any
sense?

This is how my genimage looks like:



And i mount the /var in fstab, which i have at overlay.








--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Shell-scripts-does-not-emit-finished-to-QProcess-tp156891p157008.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

      parent reply	other threads:[~2017-02-14 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 14:51 [Buildroot] Shell scripts does not emit finished() to QProcess LogiSch17
2017-02-13 15:28 ` Zoltan Gyarmati
2017-02-14 10:06   ` LogiSch17
2017-02-14 10:36     ` LogiSch17
2017-02-14 13:43   ` LogiSch17 [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=1487079798716-157008.post@n4.nabble.com \
    --to=logi.tss@hotmail.de \
    --cc=buildroot@busybox.net \
    /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.