Hi guys,

I just wana know something. IN unix, we have regular files. THere are two types of regular files : 1) Text files and 2) Binary files

MY question is what are the example of binary files in Unix system. Where are the locations ( few examples will do )

If nt mistaken, in /bin ... there are many binary files,issit? for example is /bin/echo a binary file .

If yes, y do they made is as binary file. Y not make is normal text file, so that we can able to modify whateva unix commands for fun.


Hope 2 receive an answer.

Thank you

You can modify whatever you like. Just grab the source rpm (or pure source), modify it, rebuild it, and then install it. You can do this with the vast majority of packages on most linux distros. There are a few packages that the source is not available (mostly drivers, nvidia, etc).

Double posted for some reason.

If you look in /usr/bin you will see loads of binary and executable files. Note that not all binaries are executable and not all executables are binary (a shell script would be an example of the latter).

Yes. If you want to see loads more try at a terminal and you'll get a long list of binaries.

Not just in *nix but in all computers, most commands are compiled from source code (which can be written, edited and understood by [some] humans) and turned into binary code in a form that computers understand. If you want to change a command, then you can get the source code (this is possible in linux but not usually possible in Windows or Mac stuff) and play with it all you want and then recompile and voilà, you have a new and improved command.

I hope that helps you.
Cheers,
jdk

It looks like a while playing with the file command, and maybe even reading its manpage, is called for.

Actually, there is only one kind of file in any operating system: binary files. A "text" file simply has characters in it that are human readable. A "binary" file has data that is encoded so that a computer program can efficiently interpret the information inside.

An interesting *nix comand is 'file'. It will tell you what a file is based on know patterns, usually headers or the first couple of bytes in the file. Try it: 'file /etc/passwd' or 'file /usr/bin/bash' and see what it tells you.

Bottom line is, they are all simply files - streams of bytes.

ok, how bout hardlinks. base on my understanding, Linux files don't actually live in directories. They are assigned an inode number, which Linux uses to locate the physical files.

So my question is,

for example:
when u ls -il
155719 -rw-r--r-- 1 john users 0 2009-02-02 23:13 data1
155720 -rw-r--r-- 1 john users 0 2009-02-02 23:13 data2
155721 lrwxrwxrwx 1 john users 5 2009-02-02 23:13 data3 -> data1

we have three files. I created a symbolic link based on data1. So does it mean that, data1 and data2 are hardlinks???( Y i say data1 and data2 are hardlinks, because the physical file is in somewhere, it uses the inode number to get to the physical file).

Am i correct here???? please advice..


Thank you

Try this: http://publib.boulder.ibm.com/iserie...mstlinkcmp.htm