All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP <ltp-list@lists.sourceforge.net>,
	Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [LTP] IDcheck.sh - awk problem
Date: Wed, 08 Jul 2009 16:36:42 +0200	[thread overview]
Message-ID: <4A54AEFA.3030100@petalogix.com> (raw)
In-Reply-To: <364299f40907080719q4ab01842v7e47a352b8214b8a@mail.gmail.com>

Garrett Cooper wrote:
> On Tue, Jul 7, 2009 at 11:04 PM, Michal Simek<michal.simek@petalogix.com> wrote:
>   
>> Hi All,
>>
>> There will be good to prevent missing /etc/passwd for installing to
>> different folder.
>>
>> export DESTDIR=`pwd`/nfs
>> mkdir -p nfs
>> make install
>>
>> Thanks,
>> Michal
>>
>>
>> Checking for required user/group ids
>>
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/passwd' for reading (No
>> such file or directory)
>> bin => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/passwd' for reading (No
>> such file or directory)
>> daemon => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/passwd' for reading (No
>> such file or directory)
>> nobody => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/group' for reading (No
>> such file or directory)
>> bin => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/group' for reading (No
>> such file or directory)
>> daemon => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/group' for reading (No
>> such file or directory)
>> nobody => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/group' for reading (No
>> such file or directory)
>> sys => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/group' for reading (No
>> such file or directory)
>> users => 2
>> 'nobody' user id and group found.
>> 'bin' user id and group found.
>> 'daemon' user id and group found.
>> Users group found.
>> Sys group found.
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/group' for reading (No
>> such file or directory)
>> nobody => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/passwd' for reading (No
>> such file or directory)
>> nobody => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/group' for reading (No
>> such file or directory)
>> bin => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/passwd' for reading (No
>> such file or directory)
>> bin => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/group' for reading (No
>> such file or directory)
>> daemon => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/passwd' for reading (No
>> such file or directory)
>> daemon => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/passwd' for reading (No
>> such file or directory)
>> users => 2
>> awk: cmd. line:1: fatal: cannot open file
>> `/home/projects/xils/ltp-microblaze.git/nfs/etc/passwd' for reading (No
>> such file or directory)
>> sys => 2
>> Required users/groups exist.
>>     
>
> That's part of the reason why I wanted it to be reviewed before it was
> committed, and I halfway expected Mike to provide that assistance but
> he didn't... *sigh*.
>
> Does the /etc/passwd // /etc/group file exist?
>   
Of course not because I cross compile ltp for Microblaze - correct
/etc/passwd - group is on
target system. Maybe worth to remove calling IDcheck.sh from make
install and call it only before
running the test.

Michal

> Thanks,
> -Garrett
>   


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-07-08 15:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08  6:04 [LTP] IDcheck.sh - awk problem Michal Simek
2009-07-08 14:19 ` Garrett Cooper
2009-07-08 14:36   ` Michal Simek [this message]
2009-07-09  5:30     ` Garrett Cooper
2009-07-09 10:28       ` Michal Simek
2009-07-09 17:11         ` Garrett Cooper
2009-07-10 18:04           ` Michal Simek
2009-07-10 19:21             ` Garrett Cooper
2009-07-10 19:29               ` Subrata Modak
2009-07-10 23:04                 ` Garrett Cooper

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=4A54AEFA.3030100@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier.adi@gmail.com \
    --cc=yanegomi@gmail.com \
    /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.