More information about the Underscore mailing list

[_] *nix error: cannot execute binary file

Steve Roome steve at pepcross.com
Tue Mar 13 00:00:11 GMT 2007

On Mon, Mar 12, 2007 at 11:02:53PM +0000, World of Jake wrote:
> Ahh, it was because I was using the -s (shell) option, which:
> 
> > runs the shell specified by the SHELL envi-
> > ronment variable if it is set or the shell as specified in
> > passwd(5).
> 
> and the sysadmin must have changed something in the shell  
> environment? A real newbie when it comes to *nix command line stuff...
> 
> thanks v much for your help Steve :)

Sorry I couldn't be more assistance. Anyway, I can highly recommend a
few hours perusing manual pages for unix, or perhaps bettr following a
quick tutorial on how to get some stuff done.

The command line is not so bad either and sometimes (and vice versa)
it's far quicker to get things done than with a GUI. You wouldn't meet
someone and explain everything in icons and drawings unless you were
playing pictionary so seeing as both you and the computer can
understand (some) shared words it doesn't turn out to be that hard to
use them.

Also, if you must use a shell prompt try out a good (IMO!) shell like
zsh and get someone to show you how to use it and configure it a bit,
or try setting up one of the many free unixes on your own piece of
hardware somewhere - any old small pc or if you want netbsd you can
even use a toaste.

The time invested learning will pay off in the long run if you're
going to have to use Unix a few more times yet. Some people just
refuse to ever use a command line, very strange, I've not met anyone
who refused to use a mouse and I've never seen a computer user who
doesn't type at all! People are so fickle!

        Steve

> 
> Jake
> 
> 
> On 12 Mar 2007, at 21:48, Steve Roome wrote:
> 
> > Check a few things like.
> >
> > which sudo
> >
> > list out your shell aliases (I have no idea what shell you are using
> > though)
> >
> > whereis sudo
> >
> > then depending on your OS try some variant of ptrace, dttrace etc
> > and watch for stuff.
> >
> > or mv the mv command to mv.x and replace the mv command with
> > your own wrapper (at your own peril!)
> >
> > with a script like this one, which I've got for ifconfig for the
> > time being....
> >
> > steve at zebedee 1 0 % cat /sbin/ifconfig
> > #!/bin/sh
> >
> > logger "$PPID (`cat /proc/$PPID/cmdline`) called ifconfig $*"
> > /sbin/ifconfig.x $*
> >
> >
> > ......
> >
> > Then again, you'll need to fix the `cat /proc...` to work on your os,
> > or use ps or something, if you can't do this then I'm afraid you'll
> > need to give us slightly more information on what platform and
> > configuration you've got.
> >
> > Good luck,
> >
> >         Steve
> >
> >
> > On Mon, Mar 12, 2007 at 09:01:21PM +0000, World of Jake wrote:
> >> I used to be able to "sudo -s anyoldcommand" on a remote machine that
> >> someone else has set up, but now I get this error message when I try
> >> to sudo:
> >>
> >> "mv: mv: cannot execute binary file"
> >>
> >> But it works if I just type in the command as a regular user. Anyone
> >> any ideas? Hopefully the sysadmin will fix it this eve, I'm just
> >> curious ;)
> >>
> >> cheers, Jake
> >>
> >>
> >> -- 
> >> underscore_ list info/archive -> http://www.under-score.org.uk
> >
> >
> > -- 
> > underscore_ list info/archive -> http://www.under-score.org.uk
> 
> 
> -- 
> underscore_ list info/archive -> http://www.under-score.org.uk