lavenderwords/s3-bash

FreeBSD patch

Closed this issue · 2 comments

Hello Raph

I again ... Now all works fine in my linux server.

I just tested s3-bash in my freebsd 6.2 server and I have done a patch to
freebsd systems.

This patch only change the bash path from "/bin/bash" to "/usr/local/bin/bash"

Remember in freebsd systems bash is not in the base system and must be
installed from ports or packages.

roberto

Original issue reported on code.google.com by rjpere...@gmail.com on 5 Oct 2007 at 8:39

Attachments:

Roberto,

Thanks for that.

This could be a little tricky if I want to support all *nixes easily... Most use
/bin/bash... I could use /usr/bin/env bash instead - does FreeBSD support that? 
(ie
does /usr/bin/env exist? If so, I can fix quite a lot of things). Also, is
/usr/local/bin/bash on the path? If so, I can change the explicit check at the 
start
of the script.

Alternatively, I can rely on /bin/sh existing (it must, do, surely), check the
current running process, and run a subshell as bash... tricksy, a little 
confusing
for ps, but it would work...

last but not, least, what does
uname -a
produce on a freebsd system? I could use the output to do path selection...

BTW, I've made this an enhancement.

Raph

Original comment by raphael....@gmail.com on 8 Oct 2007 at 3:36

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect
Roberto,

I've taken your patch as inspiration. I've changed over to using /usr/bin/env, 
which
should work on nearly all modern POSIX systems.

New release is out now!

Raph

Original comment by raphael....@gmail.com on 10 Oct 2007 at 3:57

  • Changed state: Fixed