public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: ltp-list@lists.sourceforge.net, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] [PATCH] LTP must be extracted to an accessible location
Date: Fri, 28 Aug 2009 11:38:46 +0530	[thread overview]
Message-ID: <1251439729.9081.8.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0908271148120.22490@vixen.sonytel.be>

On Thu, 2009-08-27 at 11:48 +0200, Geert Uytterhoeven wrote: 
> On Wed, 26 Aug 2009, Mike Frysinger wrote:
> > On Wednesday 26 August 2009 10:51:29 Geert Uytterhoeven wrote:
> > > --- a/INSTALL
> > > +++ b/INSTALL
> > > @@ -67,6 +67,9 @@ contributions are welcome.
> > >  2. Untar the ltp tarball into a spare directory.  There is not a
> > >     standard location for it yet.  We put it in our home directory
> > >     while we're working on it.
> > > +   Note that this location must be accessible for unprivileged users, as
> > > +   some tests are run as a different user than root.  Hence /root is not a
> > > +   good choice on several distributions.
> > 
> > i would use the phrase "full path to this location".  non-root could access 
> > ./foo/, but it could not access $PWD/foo/ ...
> > -mike
> 
> Thanks, that's indeed better!
> 
> >From 741d03a6753015ba6373d1f629f4117f978d6129 Mon Sep 17 00:00:00 2001
> From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
> Date: Wed, 26 Aug 2009 16:24:59 +0200
> Subject: [PATCH] LTP must be extracted to an accessible location
> 
> If extracted to /root and /root has permissions 750, the following
> tests will fail:
> 
>   - cron02:
> 
>     bash: /root/ltp-cvs/testcases/bin/cron_pos_tests.sh: Permission denied
> 
>   - cron_allow01:
> 
>     bash: /root/ltp-cvs/testcases/bin/cron_allow01: Permission denied
>     bash: /root/ltp-cvs/testcases/bin/cron_allow01: Permission denied
> 
>   - cron_deny01:
> 
>     bash: /root/ltp-cvs/testcases/bin/cron_deny01: Permission denied
>     bash: /root/ltp-cvs/testcases/bin/cron_deny01: Permission denied
> 
>   - su01:
> 
>     bash: /root/ltp-cvs/testcases/bin/su01_s1: Permission denied
> 
> Signed-off-by: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>

Thanks.

Regards--
Subrata

> ---
>  INSTALL |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/INSTALL b/INSTALL
> index 98883fb..73ff29c 100644
> --- a/INSTALL
> +++ b/INSTALL
> @@ -67,6 +67,9 @@ contributions are welcome.
>  2. Untar the ltp tarball into a spare directory.  There is not a
>     standard location for it yet.  We put it in our home directory
>     while we're working on it.
> +   Note that the full path to this location must be accessible for
> +   unprivileged users, as some tests are run as a different user than root.
> +   Hence /root is not a good choice on several distributions.
>  
>  3. Run "make" to build everything.
>     *NOTE: Some of the Makefiles (example: pan/Makefile) require the lex (or


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2009-08-28  6:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26 14:51 [LTP] [PATCH] LTP must be extracted to an accessible location Geert Uytterhoeven
2009-08-26 19:48 ` Mike Frysinger
2009-08-27  9:48   ` Geert Uytterhoeven
2009-08-28  6:08     ` Subrata Modak [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=1251439729.9081.8.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.org \
    /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