lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] lynx startup message


From: Jude DaShiell
Subject: Re: [Lynx-dev] lynx startup message
Date: Sun, 15 Apr 2018 08:46:34 -0400

running sh /usr/bin/lynx returns:
/usr/bin/sh cannot execute binary file.
On Sun, 15 Apr 2018, Mouse wrote:

Date: Sun, 15 Apr 2018 06:48:51
From: Mouse <address@hidden>
To: address@hidden
Subject: Re: [Lynx-dev] lynx startup message

 sh: line 0: test: .: binary operator expected
This message isn't coming from Lynx.  It is coming from a shell
script.

I think more likely it's coming from the lynx binary being mistaken for
a shell script.  Do you get the same (or a similar) message from
running "sh /usr/bin/lynx"?

The real question, of course, is _why_ it would be mistaken for a shell
script, since (at least if file(1) is to be trusted) it is not one.

That I can do no more than take guesses at, but here are two:

- It's lost its execute permission and the shell in use is guessing it
  might be a script when exec() fails, without noticing the lack of an
  execute bit.

- /lib64/ld-linux-x86-64.so.2 isn't what it's expected to be, so exec
  is failing.  (This could be because it's been damaged or because the
  binary was linked on a different system from the execution system,
  with the dynamic linker "interpreter" at a different path.)

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
X  Against HTML         address@hidden
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

_______________________________________________
Lynx-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lynx-dev


--




reply via email to

[Prev in Thread] Current Thread [Next in Thread]