On 17 January 2007 20:06, Kasturi Basu wrote:
> Hi Dave,
Hi KB, http://cygwin.com/acronyms#PPIOSPE please!
> Haven't used d2u before. A google search revealed several versions:
> http://linux.maruhn.com/sec/d2u.html Would you recommend any particular one?
>
The one that comes as part of c
On 17 January 2007 19:47, K. Basu wrote:
> I am very new to Cygwin, and ran into the following problem while
> trying to run a .sh file. On typing ./filename.sh at the prompt, I get
> a series of 'command not found' errors on what I suppose are several
> line numbers from the .sh file, followed b
I am very new to Cygwin, and ran into the following problem while
trying to run a .sh file. On typing ./filename.sh at the prompt, I get
a series of 'command not found' errors on what I suppose are several
line numbers from the .sh file, followed by a syntax error near
unexpected token 'elf' and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please avoid http://cygwin.com/acronyms/#TOFU - reformatting accordingly.
>
> Eric Blake-1 wrote:
> According to dubcek on 10/29/2006 12:59 PM:
>>>> >From the time I started using UNIX, I have made at least a hundred
>>
made at least a hundred
different
>> .sh files, all of which ran perfectly on my first version of cygwin. But
>> they don't work on the new version.
>
> What are the failure symptoms? Without any further details, my guess is
> that you have CRLF line endings, but a binary
To:
> cygwin@cygwin.com
> Subject:
> Re: sh files
> Date:
> Mon, 30 Oct 2006 19:44:15 +
> (14:44 EST)
>
>
> > On 10/30/06, dubcek <> wrote:
> >
> > Thanks Eric. Unfortunately, your remedy
On 10/30/06, dubcek <> wrote:
Thanks Eric. Unfortunately, your remedy did not work. As I mentioned in my
original mail, all my .sh files were made under unix. But I tried d2u anyway
(you never know), but I got the same result.
What does a hex view of your shell script say the line endi
On 10/30/06, dubcek <[EMAIL PROTECTED]> wrote:
Thanks Eric. Unfortunately, your remedy did not work. As I mentioned in my
original mail, all my .sh files were made under unix. But I tried d2u anyway
(you never know), but I got the same result.
Here is an example of one of my unsophist
Thanks Eric. Unfortunately, your remedy did not work. As I mentioned in my
original mail, all my .sh files were made under unix. But I tried d2u anyway
(you never know), but I got the same result.
Here is an example of one of my unsophisticated .sh files; it was intended
to clean up after a
order to solve that problem, I downloaded a more recent version of
cygwin.
>
> My problem is this:
> From the time I started using UNIX, I have made at least a hundred
different .sh files, all of which ran perfectly on my first version of
cygwin. But they don't work on the new version.
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to dubcek on 10/29/2006 12:59 PM:
>>From the time I started using UNIX, I have made at least a hundred different
> .sh files, all of which ran perfectly on my first version of cygwin. But
> they don't work on the new versi
My problem is this:
>From the time I started using UNIX, I have made at least a hundred different
.sh files, all of which ran perfectly on my first version of cygwin. But
they don't work on the new version.
What do I do to make them work again?
All clear and simple explanation is welcome
12 matches
Mail list logo
