The lack of execute permissions seems to be an artifact of the zip archive
as it does not seem be able to maintain this attribute. In reality this is a
trivial thing and having execute permission on the run.sh script does not
guarantee that it will run correctly as this requires that /bin/sh is a
valid path. The eol problem was a bigger issue as it could be a little
hard to find but that was fixed in the latest release. Getting the
run.sh executable bit set just doesn't seem an issue to me.
----- Original Message -----
From: "danch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 10, 2001 8:37 AM
Subject: [JBoss-dev] Re: [JBoss-user] JBoss 2.2: run.sh
> Replying to dev.
>
> Should we have separate Unix vs. Windows binaries, just to ensure that
> we get things like this (and the line ending thing) right?
>
> -danch
>
> [EMAIL PROTECTED] wrote:
> >
> > Should I post this here or to dev?
> >
> > run.sh doesn't default to have execute permissions which is easy to fix but
> > somewhat annoying.
> >
> > Jason Yip
> > Software Developer, ThoughtWorks, Inc
> > http://www.thoughtworks.com
> > (312) 560-4978 (cell)
> > "It is not the strongest of the species that survive, nor the most
> > intelligent, but the ones most responsive to change." -- Charles Darwin
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
> Confidential e-mail for addressee only. Access to this e-mail by anyone else is
>unauthorized.
> If you have received this message in error, please notify the sender immediately by
>reply e-mail
> and destroy the original communication.
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
