The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [pups] Installing begemot
Date: Fri, 13 Aug 2004 17:03:57 +0930	[thread overview]
Message-ID: <20040813073357.GW19643@wantadilla.lemis.com> (raw)
In-Reply-To: <RDwoGlBztGHBFwFC@falstaf.demon.co.uk>

On Friday, 13 August 2004 at  8:19:15 +0100, Robin Birch wrote:
> In message <Pine.BSI.4.05L.10408121627090.18049-100000 at moe.2bsd.com>,
> Steven M. Schultz <sms at 2BSD.COM> writes
>>
>> 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
>>
> 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.

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 at lemis.com for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20040813/cdf6887b/attachment.sig>


  reply	other threads:[~2004-08-13  7:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 23:01 Carl Lowenstein
2004-08-12 23:29 ` Steven M. Schultz
2004-08-13  7:19   ` Robin Birch
2004-08-13  7:33     ` Greg 'groggy' Lehey [this message]
2004-08-13 10:29       ` robinb
2004-08-13 12:36         ` Bill Gunshannon
2004-08-13 10:33       ` robinb
2004-08-12 23:46 ` Paul Ward
2004-08-13  7:15 ` Robin Birch
     [not found] <7AD18F04B62B7440BE22E190A3F772140F6047@mwsrv04.microwalt.nl>
2004-08-12 20:27 ` Robin Birch
  -- strict thread matches above, loose matches on Subject: below --
2004-08-11 17:28 Robin Birch
2004-08-11 23:54 ` Greg 'groggy' Lehey
2004-08-12 17:49   ` Robin Birch
     [not found]     ` <411BBDD3.3050400@sun.com>
2004-08-12 20:29       ` Robin Birch
     [not found]         ` <411BD929.4080009@sun.com>
2004-08-12 21:14           ` Robin Birch
2004-08-12 20:39     ` Warren Toomey
2004-08-12 21:12       ` Robin Birch

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=20040813073357.GW19643@wantadilla.lemis.com \
    --to=grog@lemis.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 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).