topic Re: hp-ux B.11.11 U in Operating System - HP-UX

hp-ux B.11.11 U

Cory Thorson — Wed, 03 Sep 2008 22:22:58 GMT

How can I install BASH on this HP-UX server?

Re: hp-ux B.11.11 U

Rajeev Shukla — Wed, 03 Sep 2008 22:24:47 GMT

Here is the software you need to install
http://hpux.connect.org.uk/hppd/hpux/Shells/bash-3.2/

Cheers
Rajeev

Re: hp-ux B.11.11 U

Cory Thorson — Wed, 03 Sep 2008 22:26:58 GMT

Should installing BASH cause any problems with other shells, users, or Informix?

Re: hp-ux B.11.11 U

Bill Hassell — Wed, 03 Sep 2008 22:44:59 GMT

BASH is fine -- except root *must* always use /sbin/sh which is a full POSIX shell (like BASH) and is not the Bourne shell (/usr/old/bin/sh). Note that you should add the bash path to /etc/shells so that users that want bash can also use ftp. If /etc/shells does not exist, create it like this:

/usr/bin/sh
/usr/bin/csh
/usr/bin/ksh
/bin/sh
/bin/csh
/bin/ksh
/usr/local/bin/bash

(or wherever you locate bash) The /bin locations are redundant since /bin is not a real directory.

Re: hp-ux B.11.11 U

Dennis Handly — Thu, 04 Sep 2008 05:23:57 GMT

>Bill: /bin locations are redundant since /bin is not a real directory.

/bin is required is that's what is in /etc/passwd. I.e. if you are sharing users with NIS over HP-UX and linux.

Re: hp-ux B.11.11 U

Bill Hassell — Thu, 04 Sep 2008 09:47:12 GMT

> Dennis: /bin is required is that's what is in /etc/passwd. I.e. if you are sharing users with NIS over HP-UX and linux.

Correct. I keep forgetting about NIS in these days of high security. And although it is hidden quite well (not in ftpd or shells man pages), the man page for getusershell provides a list of default shells when /etc/shells is not present. It too is incorrect by not defaulting the symlink /bin paths. However, it does include the restricted shells (ie, rksh, rsh). So a more complete /etc/shells might be:

/usr/bin/sh
/usr/bin/sh
/usr/bin/csh
/usr/bin/ksh
/usr/bin/sh
/usr/bin/keysh
/bin/sh
/bin/rsh
/bin/csh
/bin/ksh
/bin/rksh
/usr/bin/keysh
/usr/local/bin/bash

(does anyone use keysh anymore?)

Re: hp-ux B.11.11 U

Cory Thorson — Thu, 04 Sep 2008 22:23:41 GMT

I tried running bash it and I get the following error:

/usr/lib/dld.sl: Can't open shared library: /usr/local/lib/libiconv.sl
/usr/lib/dld.sl: No such file or directory

I searched your forum and found reference to this link
http://hpux.connect.org.uk/hppd/hpux/Development/Libraries/libiconv-1.10/
but it is a dead link.

Any suggestions?

Re: hp-ux B.11.11 U

Bill Hassell — Fri, 05 Sep 2008 00:53:22 GMT

> libiconv.sl

It sounds like you did not download all the dependencies. If you got the package from the Porting Centre, the dependent pacakges are: gettext libiconv termcap.

http://hpux.connect.org.uk/hppd/hpux/Shells/bash-3.2/

Re: hp-ux B.11.11 U

Torsten. — Fri, 05 Sep 2008 04:44:51 GMT

I don't understand why all want to have bash ... anyway, you need this too:

http://hpux.connect.org.uk/hppd/hpux/Gnu/gettext-0.17/

http://hpux.connect.org.uk/hppd/hpux/Development/Libraries/libiconv-1.12/

http://hpux.connect.org.uk/hppd/hpux/Development/Libraries/termcap-1.3.1/

Re: hp-ux B.11.11 U

James R. Ferguson — Fri, 05 Sep 2008 11:03:35 GMT

Hi:

> Torsten: I don't understand why all want to have bash ...

I suspect it comes from those who feet also stand in Linux circles where the 'bash' is a standard. I *do* like its command history features better than our POSIX shell and I suspect too, that its devotees like the ability to use the arrow keys for command recall. A nice feature is the fact that a repeated command can be optioned to only be stored once ih the history buffer.

I find that the 'bash' shell has some very annoying differences, most notably in the way it treats 'echo' escapes [I add 'shopt -s xpg_echo' to scripts I port] and in the lack of ability to do:

# echo "a b c"|read X Y Z;echo ${Z}
c

...in HP 'sh' but *NOT* in 'bash' (yielding an empty ${Z} variable!).

Regards!

...JRF...

Re: hp-ux B.11.11 U

Duncan Edmonstone — Fri, 05 Sep 2008 11:14:13 GMT

James,

Yes its alway been my understanding that pipelines in bash are run in subshells, so:

mycommand | read myvar

will only set ${myvar} for the subshell, any attempt to use ${myvar} after that will fail.

However:
mycommand | while read myvar
do
echo "myvar is ${myvar}"
done

works fine, as the entire while statement runs in the subshell

HTH

Duncan

Re: hp-ux B.11.11 U

James R. Ferguson — Fri, 05 Sep 2008 11:52:32 GMT

Hi (again):

@ Duncan: I had once discovered that imposition of a 'while' loop in the pipeline enabled me to use the shell 'read' to autosplit and assign, but I hadn't understood why. Now I do, thanks to you!

Warmest regards, Duncan!

...JRF...

Re: hp-ux B.11.11 U

OldSchool — Mon, 08 Sep 2008 19:33:05 GMT

and of course, newer linux distributions are heading towards the dash shell as "compliant with the latest POSIX standards" (which I can't speak to) and the recommendation to use "printf" instead of "echo" (due to the differing implementations of echo).

the more shells the merrier i guess....meanwhile I continue to muddle along with sh (or sometimes ksh).