Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] problem with new package partimage
Date: Thu, 9 Dec 2010 20:34:37 +0100	[thread overview]
Message-ID: <20101209203437.766b210e@surf> (raw)
In-Reply-To: <AANLkTinScnan+v3ys81p40EohreZpLYY3CrWkzxPWHy8@mail.gmail.com>

Hello,

On Thu, 9 Dec 2010 16:40:21 +0100
Jomas Nash <jomasnash@gmail.com> wrote:

> I found another strange thing with partimage.
> When I start partimage and run 'ps'  in an other terminal, I see that
> 3 instances of partimage are running.
> like:
> 
> 1117   partimage -S  etc...
> 1118   partimage -S
> 1119   partimage -S
> 
> All three lines have the same parameters
> At my "normal" linux system (ubuntu) there is only one instance of
> partimage when I start it
> 
> 
> Has anybody an idea what can cause this?

Busybox ps probably show all the threads by default, while the normal
ps shows only processes and hides all their threads.

> It looks like partimge does not want to be compiled in buildroot.

This sentence simply doesn't make sense. It's not because there is a
bug somewhere that "partimage does not want to be compiled in
Buildroot".

Regards!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-12-09 19:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 17:28 [Buildroot] problem with new package partimage Jomas Nash
2010-12-09 10:58 ` Jomas Nash
2010-12-09 14:17 ` Jomas Nash
2010-12-09 15:40 ` Jomas Nash
2010-12-09 19:34   ` Thomas Petazzoni [this message]
2010-12-09 19:44   ` Pkun

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=20101209203437.766b210e@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox