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

Re: Shell Scropts

On Thu, 2005-04-14 at 22:14 -0400, Steven W. Orr wrote:
> On Thursday, Apr 14th 2005 at 19:59 -0600, quoth JOHN H DURRANT:
> =>Hello,
> =>
> =>  I am running Fedora Core 3 and downloaded a .bin file from a site that I 
> =>trust.  The instructions that came with the file say to double click on the 
> =>file.  When I do this, Fedora tells me that it doesn't know what to do with 
> =>a .bin file but that the contents look like a shell script.  I then let's be 
> =>browse for the right command to use to open a shell script file.  What's the 
> =>right answer?
> =>
> =>Thanks,
> =>
> =>John Durrant 
> Typically, a bin file is a Microsoft executable and won't do you any good 
> under Linux.
> To check, run the file command on the .bin file.

In Linux the filename extension means nothing.  It can be used to tell
the system what app to use to manage the file.  For example .mp3 is
music and .sxw is an OOo document,  but that is NOT required.

I can have a perl script that is named   myprog.pl,  myprog.cgi, or
myprog and as long as the contents of the file is exactly the same the
system can use all exactly the same.

I often see .bin files used to provide a package distribution for
Linux/*nix versions, and they are certainly not M$ executable.  

In fact, M$ will not execute a .bin file just by clicking on it.
A .exe, .bat, or .com file is the executable in M$. IIRC M$ uses .bin
or .sys files for drivers and loadable modules that get loaded but not
executed from user space.

Try your file command on the attached .bin file and see what it tells

> -- 
> Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
> happened but none stranger than this. Does your driver's license say Organ ..0
> Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
> individuals! What if this weren't a hypothetical question?
> steveo at syslang.net

Attachment: test.bin
Description: application/shellscript

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