PA-RISC1.1 shared executable dynamically linked

[Yvonne Butler]

Hello

I'm trying to use a PA-RISC1.1 executable but on a RHEL5 system and obviously its not working. The file is called "false", it pre-dates my sysadmin days at this company so dont know where it came from exactly or what it even does. Does anyone know how I can find out what this performs (its used by ftp account users) and how I might be able to convert it for RHEL5 use.

Thanks

[Tim Nelson]

typically /usr/bin/false is used as the shell for "ftp only" users. e.g. if user attempts to telnet, they execute false and are logged off immediately.

linux has /bin/false, simply set users shell in /etc/passwd to /bin/false...

(side note: use a secure method of system access, e.g. ssh )

[Steven Schweda · Accepted solution]

> [...] The file is called "false" [...]

Strangely, this didn't make it into your
Subject.

And where is this file now?

> [...] Does anyone know how I can find out
> what this performs [...]

man false

> linux has /bin/false, [...]

Yup.

One is left to wonder how/why this HP-UX
executable migrated to some incompatible
environment. With any luck, the genius who
got it there didn't overwrite the local
(working) one which came with the (new) OS.

[Dennis Handly]

>Steven: One is left to wonder how/why this HP-UX executable migrated

It may be even better to wonder why HP-UX needs an executable for true/false and not just a simple script.
-r-xr-xr-x 15 bin bin /usr/bin/false
-r-xr-xr-x 1 bin bin /usr/bin/true

$ find /usr/bin -inum 13190
/usr/bin/false /usr/bin/hp9000s800 ...

But I suppose the hardlinks that check for various hardware, may need to call something not available from the shell.

[Steven Schweda]

> It may be even better to wonder why HP-UX
> needs an executable for true/false and not
> just a simple script.

Knowing nothing, I'd guess that activating a
tiny program might be more efficient than
activating some big shell, and then having
that shell do something trivial.

[muruganantham raju]

Hi,
The false and true commands returns an exit code 1 and 0 respectively. It is used in shell scripts to check for true/false boolean operation.

RISC executables will not run on RHEL. Find out the architecture of your RHEL5 system. It could be x86/x64/IA64 or Power6. Download this binary from similar RHEL system.

Rgrds,
Muru

[Steven Schweda]

> [...] Download this binary from similar
> RHEL system.

Why? Who said that it's missing?


> [...] Find out the architecture of your
> RHEL5 system. [...]

Actual output from "uname -a" belongs in
almost every inquiry. (Unless you're looking
for reliable responses from psychics only.)

[Yvonne Butler]

Thanks, the "false" executable for RHEL was indeed in /bin (as opposed to /usr/bin on HP-UX). Thanks for that!