From: "Sangmoon Kim" <dogoil@etinsys.com>
To: "Subhachandra Chandra" <Subhachandra.Chandra@cosinecom.com>,
"'linuxppc-embedded '" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: execve system call question
Date: Wed, 27 Feb 2002 10:41:18 +0900 [thread overview]
Message-ID: <007701c1bf2f$da283200$1a11efcb@industrialDiv.hanasys.co.kr> (raw)
In-Reply-To: 69BCCDDC980B4641BFC908D7BF95F1842A4B89@exchsrv-eng
RE: execve system call questionHi Subhachandra Chandra.
> It could be that your ld.so* does not have execute >permissions. The 2.4.2 and 2.4.4 kernels did not care >about this but the 2.4.17 cares about it. I do not know >when the actual switchover happened. Since you are >doing NFS there may be other files which have incorrect >permissions.
ld.so* has execute permission.
I will try 2.4.2 then.
Thank you.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-02-27 1:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <69BCCDDC980B4641BFC908D7BF95F1842A4B89@exchsrv-eng>
2002-02-27 1:41 ` Sangmoon Kim [this message]
[not found] <C08678384BE7D311B4D70004ACA371050B7632EF@amer22.avnet.com>
2002-03-04 1:20 ` execve system call question Sangmoon Kim
2002-02-27 14:33 Derrik Weeks
2002-03-04 1:11 ` Sangmoon Kim
[not found] <C08678384BE7D311B4D70004ACA371050B7632EC@amer22.avnet.com>
2002-02-27 1:48 ` Sangmoon Kim
[not found] <21A8AE56EBB6D411A4520060973D360179DD48@pepintercom.pep.de>
2002-02-27 1:45 ` Sangmoon Kim
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 14:34 Derrik Weeks
2002-02-27 1:31 ` Sangmoon Kim
2002-02-26 9:16 monitor in mpc860fads gao xiaoguo
2002-02-26 10:35 ` execve system call question Sangmoon Kim
2002-02-26 13:11 ` None Atall
2002-02-27 1:21 ` Sangmoon Kim
2002-02-27 7:54 ` Wolfgang Denk
2002-02-26 13:21 ` Wolfgang Denk
2002-02-27 1:36 ` Sangmoon Kim
2002-02-26 13:27 ` Christian Pellegrin
2002-02-27 1:23 ` Sangmoon Kim
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='007701c1bf2f$da283200$1a11efcb@industrialDiv.hanasys.co.kr' \
--to=dogoil@etinsys.com \
--cc=Subhachandra.Chandra@cosinecom.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).