why #!/bin/bash is necessary, even if /bin/sh is a symlink to /bin/bash

When bash is run as 'sh', it runs with (nearly) only POSIX behavior -which means that some things don't work the way they do when the program is executed with the name 'bash'. There's a caveat with the 'nearly': bash-as-sh still supports some bash extensions which one would not find in traditional Bourne shells and similar ash/dash/bsh/jhs, etc.

The lesson is to use /bin/bash as the shebang any time you use any bashisms -or learn to write portable sh-compatible code. I usually do the former, but it's your call. If you want to check for (nearly) POSIX-compliance, use /bin/dash as the shebang. If it will run under dash then it will most likely work(with /bin/sh shebang) under any common shell -excluding light-weight alternatives like 'sash', any of the busbyox shell options. I'm pretty sure that even the fullest busybox shell option (ash??) is not feature equal to traditional ash and certainly not equal to dash.

If you want portability starting from the Big Bang and continuing up to date, then you can use the heirloom-sh (bsh) as the testbed. Anything that runs under bsh should run anywhere, even on your toaster -a Post-WWII toaster, I mean.

Yeah, I don`t see the point in Puppy`s BusyBox, so much of it`s disabled. But boot uses it`s init.
BusyBox can be "custom compiled". It can be made with full capabilities and added stuff.

amigo; What do you think of the new Community Edition effort that`s under way.?
They seem to have settled on Debian stable ( your choice base ). I hope it flies and takes over.
With enough folks working on it, maybe most of the "never been fixed" items will actually get done.
.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum