13 Aug
2004
13 Aug
'04
5:01 a.m.
Date: Thu, 12 Aug 2004 18:49:11 +0100
To: "Greg 'groggy' Lehey" <grog(a)lemis.com>
From: Robin Birch <robinb(a)ruffnready.co.uk>
Subject: Re: [pups] Installing begemot
I have a different problem as well. There is
something broken in the
configuration of this computer!!!!! If I execute a shell file by going
/bin/sh filename then it works ok but if I try running a shell script
with #!/bin/sh in the first line I get a bad permission error. This is
preventing me from running make scripts and all sorts of things. Any
ideas?
Yes. See the following transcript of a session. I created a small
script named "bad" which just does "date" to show that it worked.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
iota: try 1107$ ls -l bad
-rwxrwxr-x 1 cdl cdl 16 Aug 12 15:56 bad*
iota: try 1108$ /bin/sh bad
Thu Aug 12 15:57:37 PDT 2004
iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h \r \n d a t e \n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a '\r' character at the end of the #! line.
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenst(a)ucsd.edu
13 Aug
13 Aug
5:29 a.m.
New subject: [pups] Installing begemot
On Thu, 12 Aug 2004, Carl Lowenstein wrote:
iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h \r \n d a t e \n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a '\r' character at the end of the #! line.
And that's the cause of the problem. The kernel is scanning for
'\n' and when it finds the (unix) end-of-line character it then
tries to exec the program "/bin/sh\r" and fails.
Was the original script created on a windoze box perhaps? Or was
a different method of getting a \r used? :)
Cheers,
Steven Schultz
1:19 p.m.
New subject: [pups] Installing begemot
In message <Pine.BSI.4.05L.10408121627090.18049-100000(a)moe.2bsd.com>,
Steven M. Schultz <sms(a)2BSD.COM> writes
On Thu, 12 Aug 2004, Carl Lowenstein wrote:
Hi Steve,
Long time no chat.
The scripts were tar'd off a Mandrake linux system then untar'd on a
SuSE system. Something has got munged in the process I guess.
What I'll do is a make really clean and then tr the whole thing to add
\n instead of \r and start again.
Cheers
Robin
iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h \r \n d a t e \n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a '\r' character at the end of the #! line.
And that's the cause of the problem. The kernel is scanning for
'\n' and when it finds the (unix) end-of-line character it then
tries to exec the program "/bin/sh\r" and fails.
Was the original script created on a windoze box perhaps? Or was
a different method of getting a \r used? :)
Cheers,
Steven Schultz
_______________________________________________
PUPS mailing list
PUPS(a)minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/pups
--
Robin Birch
1:33 p.m.
New subject: [pups] Installing begemot
On Friday, 13 August 2004 at 8:19:15 +0100, Robin Birch wrote:
In message
<Pine.BSI.4.05L.10408121627090.18049-100000(a)moe.2bsd.com>,
Steven M. Schultz <sms(a)2BSD.COM> writes
Judging by the above, you want to remove the \r, not change them to
\n.
Greg
--
Note: I discard all HTML mail unseen.
Finger grog(a)lemis.com for PGP public key.
See complete headers for address and phone numbers.
On Thu, 12 Aug 2004, Carl Lowenstein wrote:
Hi Steve,
Long time no chat.
The scripts were tar'd off a Mandrake linux system then untar'd on a
SuSE system. Something has got munged in the process I guess.
What I'll do is a make really clean and then tr the whole thing to add
\n instead of \r and start again. iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h \r \n d a t e \n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a '\r' character at the end of the #! line.
And that's the cause of the problem. The kernel is scanning for
'\n' and when it finds the (unix) end-of-line character it then
tries to exec the program "/bin/sh\r" and fails.
Was the original script created on a windoze box perhaps? Or was
a different method of getting a \r used? :)
Cheers,
Steven Schultz
4:29 p.m.
New subject: [pups] Installing begemot
grog(a)lemis.com wrote:
On Friday, 13 August 2004 at 8:19:15 +0100, Robin
Birch wrote:
It's more complicated than that. The issue isn't to do with /r,
I've checked all that, it's to do with permissions. If I execute the script in
my home directory it runs fine, if I execute it in the directory I am intending to use for
building packages on it blows out. This happens whenther I use the scripts from the
package or write my own. I have all of the directories above this set to 777, right up to
wherre I have the device mounted. It is on a separate device.
I am now well confused!!!!!!
Robin
In message
<Pine.BSI.4.05L.10408121627090.18049-100000(a)moe.2bsd.com>,
Steven M. Schultz <sms(a)2BSD.COM> writes
Judging by the above, you want to remove the r,
not change them to
n.
Greg
On Thu, 12 Aug 2004, Carl Lowenstein wrote:
Hi Steve,
Long time no chat.
The scripts were tar'd off a Mandrake linux system then untar'd on a
SuSE system. Something has got munged in the process I guess.
What I'll do is a make really clean and then tr the whole thing to add
n instead of r and start again. iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h r n d a t e n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a 'r' character at the end of the #! line.
And that's the cause of the problem. The kernel is scanning for
'n' and when it finds the (unix) end-of-line character it then
tries to exec the program "/bin/shr" and fails.
Was the original script created on a windoze box perhaps? Or was
a different method of getting a r used? :)
Cheers,
Steven Schultz
--
Note: I discard all HTML mail unseen.
Finger grog(a)lemis.com for PGP public key.
See complete headers for address and phone numbers.
6:36 p.m.
New subject: [pups] Installing begemot
On Fri, 13 Aug 2004 robinb(a)falstaf.demon.co.uk wrote:
grog(a)lemis.com wrote:
It's more complicated than that. The issue isn't to do with /r, I've
checked all that, it's to do with permissions. If I execute the script
in my home directory it runs fine, if I execute it in the directory
I am intending to use for building packages on it blows out. This
happens whenther I use the scripts from the package or write my own.
I have all of the directories above this set to 777, right up to
wherre I have the device mounted. It is on a separate device.
I am now well confused!!!!!!
I think Linux supports "no_exec" on mounted partitions. Check to see
if you have accidentally included this option in your mount.
bill
--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
bill(a)cs.scranton.edu | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include <std.disclaimer.h>
4:33 p.m.
New subject: [pups] Installing begemot
grog(a)lemis.com wrote:
On Friday, 13 August 2004 at 8:19:15 +0100, Robin
Birch wrote:
In case the first reply didn't get there, I am having difficulties
everywhere at the moemnt :-((((
It is more complicated than just the /r. I've checked the scripts and they are quite
legal. I can run them from my home directory but not from the directory I am using to
build the packages in. This is the same for the distributed scripts and any that I write.
The package directory is on a separate device fom the home directories and all of the
directories above the packages one are set 777.
I'm now positively confused!!!!!
Robin
In message
<Pine.BSI.4.05L.10408121627090.18049-100000(a)moe.2bsd.com>,
Steven M. Schultz <sms(a)2BSD.COM> writes
Judging by the above, you want to remove the r,
not change them to
n.
Greg
On Thu, 12 Aug 2004, Carl Lowenstein wrote:
Hi Steve,
Long time no chat.
The scripts were tar'd off a Mandrake linux system then untar'd on a
SuSE system. Something has got munged in the process I guess.
What I'll do is a make really clean and then tr the whole thing to add
n instead of r and start again. iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h r n d a t e n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a 'r' character at the end of the #! line.
And that's the cause of the problem. The kernel is scanning for
'n' and when it finds the (unix) end-of-line character it then
tries to exec the program "/bin/shr" and fails.
Was the original script created on a windoze box perhaps? Or was
a different method of getting a r used? :)
Cheers,
Steven Schultz
--
Note: I discard all HTML mail unseen.
Finger grog(a)lemis.com for PGP public key.
See complete headers for address and phone numbers.
5:46 a.m.
New subject: [pups] Installing begemot
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 13 August 2004 00:01, Carl Lowenstein wrote:
The problem is often more simple than that, especially with Linux.
Take a look inside /etc/fstab.
if you see "noexec" in any of the mountpoint options, that'll be why
you're
getting the "bad interpreter" responses.
Removal of the offending option will probably fix the problem :)
- --
Best regards,
Paul mailto:asmodai@ao.mine.nu
http://ao.mine.nu/ (NeXTmail) mailto:nextmail@ao.mine.nu
Date: Thu, 12
Aug 2004 18:49:11 +0100
To: "Greg 'groggy' Lehey" <grog(a)lemis.com>
From: Robin Birch <robinb(a)ruffnready.co.uk>
Subject: Re: [pups] Installing begemot
I have a different problem as well. There is something broken in the
configuration of this computer!!!!! If I execute a shell file by going
/bin/sh filename then it works ok but if I try running a shell script
with #!/bin/sh in the first line I get a bad permission error. This is
preventing me from running make scripts and all sorts of things. Any
ideas?
Yes. See the following transcript of a session. I created a small
script named "bad" which just does "date" to show that it worked.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
iota: try 1107$ ls -l bad
-rwxrwxr-x 1 cdl cdl 16 Aug 12 15:56 bad*
iota: try 1108$ /bin/sh bad
Thu Aug 12 15:57:37 PDT 2004
iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h \r \n d a t e \n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a '\r' character at the end of the #! line.
carl -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFBHAFcrImhuhEwHs4RAremAJ9BDGWkljOI/YHi3f//Jc+4Mi/P3QCgpzZa
ls0hupO+XT2h8rXP4/HSXvY=
=65n2
-----END PGP SIGNATURE-----
1:15 p.m.
New subject: [pups] Installing begemot
In message <200408122301.i7CN1MX01938(a)opihi.ucsd.edu>, Carl Lowenstein
<cdl(a)mpl.ucsd.edu> writes
Ahhhhhhhhhhhh :-)
Well done, I'll try sorting this out at work. I feel like a bulk tr
script coming on.
Robin
--
Robin Birch
Date: Thu, 12
Aug 2004 18:49:11 +0100
To: "Greg 'groggy' Lehey" <grog(a)lemis.com>
From: Robin Birch <robinb(a)ruffnready.co.uk>
Subject: Re: [pups] Installing begemot
I have a different problem as well. There is
something broken in the
configuration of this computer!!!!! If I execute a shell file by going
/bin/sh filename then it works ok but if I try running a shell script
with #!/bin/sh in the first line I get a bad permission error. This is
preventing me from running make scripts and all sorts of things. Any
ideas?
Yes. See the following transcript of a session. I created a small
script named "bad" which just does "date" to show that it worked.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
iota: try 1107$ ls -l bad
-rwxrwxr-x 1 cdl cdl 16 Aug 12 15:56 bad*
iota: try 1108$ /bin/sh bad
Thu Aug 12 15:57:37 PDT 2004
iota: try 1109$ ./bad
: bad interpreter: No such file or directory
iota: try 1110$ cat bad
#!/bin/sh
date
iota: try 1111$ od -c bad
0000000 # ! / b i n / s h \r \n d a t e \n
0000020
iota: try 1112$
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note that there is a '\r' character at the end of the #! line.
carl
7436
days inactive
7436
days old
8 comments
8 participants
participants (8)
-
Bill Gunshannon -
Carl Lowenstein -
Greg 'groggy' Lehey -
Paul Ward -
Robin Birch -
robinb＠falstaf.demon.co.uk -
robinb＠ruffnready.co.uk
-
Steven M. Schultz