From: chrubis@suse.cz
To: Bogdan Purcareata <bogdan.purcareata@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Running LTP on embedded Busybox platforms
Date: Tue, 12 Feb 2013 14:06:06 +0100 [thread overview]
Message-ID: <20130212130606.GC9378@rei> (raw)
In-Reply-To: <CAAZGUZfwzVLPd6HesN26c4uL=ZTug9f-axrkcxHGRveqsjnjyA@mail.gmail.com>
Hi!
> I'm a new user of the LTP and I was wondering if it works on embedded
> platforms with custom Linux distros built with Yocto. I was interested
> in the "containers" set of tests, particularly the network namespace
> ones.
Most of the tests should work on embedded platforms and with Busybox but
I personaly can't guarante that. In other words We are trying not to
break things for anybody, but some tests may not worked from the start.
> I noticed the tests were not working properly on a Busybox
> system, and I've identified some differences between this and running
> LTP on my host Fedora 17 system (which works fine):
> - Busybox's diff outputs in the unified format by default - this
> causes parsing issues in LTP
> - there is no sshd server on my embedded platform - instead I have
> dropbear installed, and the scripts need minor changes to work
> - the networking utils - ping, ip, etc. - are from the inetutils
> package, instead if the expected iputils package
As usual patches are welcome.
> I was wondering if these requirements - diff, sshd, iputils package,
> and others - are somewhere listed as prerequisites in the
> documentation (I haven't searched it extensively). Where should I look
> for a complete list of host userspace applications needed by LTP to
> work?
Sorry the LTP documentation is not in a good shape. On the other hand I
would be happy to include what you have found into the containers README
file. Just send a signed patch.
> Also, are there any branches of the LTP project designed to work with
> e.g. Busybox by default? I noticed that the ltp-full-20130109.bz2
> arhive is universal and has no mentions of supported host distro
> configuration (or perhaps I didn't look in the right place?).
There are not. We have one archive to run on all flavors of Linux,
fragmentation would only make things worse.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-02-12 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 11:31 [LTP] Running LTP on embedded Busybox platforms Bogdan Purcareata
2013-02-12 12:49 ` Bogdan Purcareata
2013-02-12 13:06 ` chrubis [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=20130212130606.GC9378@rei \
--to=chrubis@suse.cz \
--cc=bogdan.purcareata@gmail.com \
--cc=ltp-list@lists.sourceforge.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