So I am trying to port a package from Linux to FreeBSD. I have changed
user default shell to bash, and open xterm, find shell is bash and it
has digested .bashrc login file.
But try to excecute a script with ~/foobar.sh it complains
cannot execute required file not found
The file is there with protection 755
So one has to type source foobar.sh instead.
Which is a hassle as there are a lot of scripts, which call other scripts.

Woozy Song <suzyw0ng@outlook.com> writes:

> So I am trying to port a package from Linux to FreeBSD. I have changed
> user default shell to bash, and open xterm, find shell is bash and it
> has digested .bashrc login file.
> But try to excecute a script with ~/foobar.sh it complains
> cannot execute required file not found
> The file is there with protection 755
> So one has to type source foobar.sh instead.
> Which is a hassle as there are a lot of scripts, which call other scripts.

If you are not the same user as the user that owns the script, then
this is expected. If you are in the same group then the file
protection should be 775.

--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

On 2023-05-24, Woozy Song <suzyw0ng@outlook.com> wrote:
> So I am trying to port a package from Linux to FreeBSD. I have changed
> user default shell to bash, and open xterm, find shell is bash and it
> has digested .bashrc login file.
> But try to excecute a script with ~/foobar.sh it complains
> cannot execute required file not found
> The file is there with protection 755
> So one has to type source foobar.sh instead.
> Which is a hassle as there are a lot of scripts, which call other scripts.

wrong shebang?

--
Jasen.
🇺🇦 Слава Україні

Cecil Westerhof <Cecil@decebal.nl> writes:
> Woozy Song <suzyw0ng@outlook.com> writes:
>> So I am trying to port a package from Linux to FreeBSD. I have changed
>> user default shell to bash, and open xterm, find shell is bash and it
>> has digested .bashrc login file.
>> But try to excecute a script with ~/foobar.sh it complains
>> cannot execute required file not found
>> The file is there with protection 755
>> So one has to type source foobar.sh instead.
>> Which is a hassle as there are a lot of scripts, which call other scripts.
>
> If you are not the same user as the user that owns the script, then
> this is expected. If you are in the same group then the file
> protection should be 775.

1) Permissions problems don’t produce a ‘file not found’ error.
2) There is no permissions problem. 755 includes read and execute for
world.

--
https://www.greenend.org.uk/rjk/

On Wed, 24 May 2023 12:49:26 +0800, Woozy Song wrote:
> So I am trying to port a package from Linux to FreeBSD. I have changed
> user default shell to bash, and open xterm, find shell is bash and it
> has digested .bashrc login file.
> But try to excecute a script with ~/foobar.sh it complains
> cannot execute required file not found

huh? What's in your $PATH ?
I"ll bet it doesn't contain ",~/".
How does
$./foobar.sh
play for you?

Jonesy
--
Marvin L Jones | Marvin | W3DHJ.net | linux
38.238N 104.547W | @ jonz.net | Jonesy | FreeBSD
* Killfiling google & XXXXbanter.com: jonz.net/ng.htm

On 24/05/2023 08:48, Richard Kettlewell wrote:
> Cecil Westerhof <Cecil@decebal.nl> writes:
>> Woozy Song <suzyw0ng@outlook.com> writes:
>>> So I am trying to port a package from Linux to FreeBSD. I have changed
>>> user default shell to bash, and open xterm, find shell is bash and it
>>> has digested .bashrc login file.
>>> But try to excecute a script with ~/foobar.sh it complains
>>> cannot execute required file not found
>>> The file is there with protection 755
>>> So one has to type source foobar.sh instead.
>>> Which is a hassle as there are a lot of scripts, which call other scripts.
>> If you are not the same user as the user that owns the script, then
>> this is expected. If you are in the same group then the file
>> protection should be 775.
> 1) Permissions problems don�t produce a �file not found� error.
> 2) There is no permissions problem. 755 includes read and execute for
> world.
>

So the Senior Software Engineer is wrong. God help us!!!.

On Wed, 24 May 2023 12:49:26 +0800, Woozy Song wrote:
> So I am trying to port a package from Linux to FreeBSD. I have changed
> user default shell to bash, and open xterm, find shell is bash and it
> has digested .bashrc login file.
> But try to excecute a script with ~/foobar.sh it complains
> cannot execute required file not found
> The file is there with protection 755
> So one has to type source foobar.sh instead.
> Which is a hassle as there are a lot of scripts, which call other scripts.

Need a bit more background and information.

How are you executing foobar.sh, from the command line or from a script?

what is the output from the following five commands:

head -3 ~/foobar.sh
ls -l ~/foobar.sh
id
type ~/foobar.sh
bash --version

You need to post the command and results.

On 5/24/2023 12:49 AM, Woozy Song wrote:
> So I am trying to port a package from Linux to FreeBSD. I have changed user default shell to bash, and open xterm, find shell is bash and it has digested .bashrc login file.
> But try to excecute a script with ~/foobar.sh it complains
>  cannot execute required file not found
> The file is there with protection 755
> So one has to type source foobar.sh instead.
> Which is a hassle as there are a lot of scripts, which call other scripts.

https://docs.freebsd.org/en/articles/linux-users/

"Linux users are often surprised to find that Bash is not the default shell
in FreeBSD. In fact, Bash is not included in the default installation.
Instead, the Bourne shell-compatible sh(1) as the default user shell."

Check very carefully, that the shell executable you are running
right now, is actually bash, and is not "something else" like
an aliased /bin/sh .

Writing portable scripts (commercial grade installers), is an art, and a research project.

A portable script "does not know whether it is on Earth or
on Mars, but it will check first to see if there is oxygen and
nitrogen in the room". Look at how much work a ./configure
does some day, for inspiration.

Paul

On 24/05/2023 at 08.58, Jasen Betts wrote:
>> So I am trying to port a package from Linux to FreeBSD. I have changed
>> user default shell to bash, and open xterm, find shell is bash and it
>> has digested .bashrc login file.
>> But try to excecute a script with ~/foobar.sh it complains
>> cannot execute required file not found
>> The file is there with protection 755
>> So one has to type source foobar.sh instead.
>> Which is a hassle as there are a lot of scripts, which call other scripts.
>
> wrong shebang?

Would be my first guess too, especially CR+LF instead of LF alone
as the line terminator. @OP: What exactly does

head -1 foobar.sh | cat -A

show?

--
mrg

Richard Kettlewell <invalid@invalid.invalid> writes:

> Cecil Westerhof <Cecil@decebal.nl> writes:
>> Woozy Song <suzyw0ng@outlook.com> writes:
>>> So I am trying to port a package from Linux to FreeBSD. I have changed
>>> user default shell to bash, and open xterm, find shell is bash and it
>>> has digested .bashrc login file.
>>> But try to excecute a script with ~/foobar.sh it complains
>>> cannot execute required file not found
>>> The file is there with protection 755
>>> So one has to type source foobar.sh instead.
>>> Which is a hassle as there are a lot of scripts, which call other scripts.
>>
>> If you are not the same user as the user that owns the script, then
>> this is expected. If you are in the same group then the file
>> protection should be 775.
>
> 1) Permissions problems don’t produce a ‘file not found’ error.
> 2) There is no permissions problem. 755 includes read and execute for
> world.

I should not respond fast when I am very tired. 😪😱
My bad.

--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

Jasen Betts wrote:
>
> wrong shebang?
>
>

Yes I think that is the issue - bash is in a different directory in BSD
and Linux.
But apart from that found a really weird issue: 2 of the dozens of
scripts require 'bash fubah.sh' rather than 'source fubah.sh' because
the console window closes instantly if you try to execute it any other
way. So no error message, no idea what is going on.
But there is nothing unusual in those 2 scripts. Have tried commenting
out various lines, but haven't found out what is fatal yet.

Woozy Song writes:
> But apart from that found a really weird issue: 2 of the dozens of
> scripts require 'bash fubah.sh' rather than 'source fubah.sh' because
> the console window closes instantly if you try to execute it any other
> way. So no error message, no idea what is going on. But there is
> nothing unusual in those 2 scripts. Have tried commenting out various
> lines, but haven't found out what is fatal yet.

Those scripts probably contain "exit" commands.
--
John Hasler
john@sugarbit.com
Dancing Horse Hill
Elmwood, WI USA

On 2023-05-25, Woozy Song <suzyw0ng@outlook.com> wrote:
> Jasen Betts wrote:
>>
>> wrong shebang?
>>
>>
>
> Yes I think that is the issue - bash is in a different directory in BSD
> and Linux.
> But apart from that found a really weird issue: 2 of the dozens of
> scripts require 'bash fubah.sh' rather than 'source fubah.sh' because
> the console window closes instantly if you try to execute it any other
> way. So no error message, no idea what is going on.
> But there is nothing unusual in those 2 scripts. Have tried commenting
> out various lines, but haven't found out what is fatal yet.

if a script ends with exit it will close the shell when sourced.

--
Jasen.
🇺🇦 Слава Україні

Woozy Song <suzyw0ng@outlook.com> writes:

> Jasen Betts wrote:
>> wrong shebang?
>>
>
> Yes I think that is the issue - bash is in a different directory in BSD
> and Linux.

That is why I always use:
#!/usr/bin/env bash

That should work on every nix system.
There should be a env in /usr/bin and this then finds where bash is
installed on the current system and calls it.

Works of-course also for python, perl, …

--
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

Paul <nospam@needed.invalid> writes:
> On 5/24/2023 12:49 AM, Woozy Song wrote:
>> So I am trying to port a package from Linux to FreeBSD. I have
>> changed user default shell to bash, and open xterm, find shell is
>> bash and it has digested .bashrc login file.
>> But try to excecute a script with ~/foobar.sh it complains
>>  cannot execute required file not found
>> The file is there with protection 755
>> So one has to type source foobar.sh instead.
>> Which is a hassle as there are a lot of scripts, which call other scripts.
>
> https://docs.freebsd.org/en/articles/linux-users/
>
> "Linux users are often surprised to find that Bash is not the default shell
> in FreeBSD. In fact, Bash is not included in the default installation.
> Instead, the Bourne shell-compatible sh(1) as the default user shell."
>
> Check very carefully, that the shell executable you are running
> right now, is actually bash, and is not "something else" like
> an aliased /bin/sh .

It's very unlikely that an executable named "bash" would be anything
other than an actual GNU Bash shell. "/bin/sh" could be any of several
things, but "bash" is going to be Bash unless someone has deliberately
misconfigured it.

bash is likely not installed by default on a *BSD system, and if it is
installed it's likely to be /usr/local/bin/bash rather than /bin/bash .

The OP's probably is likely to be the "#!" line, but they haven't said
what the current "#!" line looks like.

One solution is to use "#!/usr/bin/env bash". (Assuming that env is in
/usr/bin seems to be safer than assuming that bash is in /bin.) The
advantage of that is that it uses the first "bash" executable in the
user's $PATH. The *disadvantage* is that it uses the first "bash"
executable in the user's $PATH, which might be an unstable version that
the user installed manually.

My preferred solution is to update the "#!" line to match the location
of the bash executable: "#!/bin/bash" on Linux-based systems,
"#!/usr/local/bin/bash" on BSD-based systems (after installing bash if
necessary).

[...]

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */