SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

BotDetect - Real-Time Bot Detection API
 
 

MAN page from Other file-4.03-3sls.i586.rpm

FILE

Section: User Commands (1)
Updated: Copyright but distributable
Index 

NAME

file- determine file type 

SYNOPSIS

file[-bcikLnNsvz][-fnamefile][-Fseparator][-m magicfiles]file...
file-C[-m magicfile ] 

DESCRIPTION

This manual page documents version 4.03 of thefilecommand.

Filetests each argument in an attempt to classify it.There are three sets of tests, performed in this order:filesystem tests, magic number tests, and language tests.Thefirsttest that succeeds causes the file type to be printed.

The type printed will usually contain one of the wordstext(the file contains onlyprinting characters and a few common controlcharacters and is probably safe to read on anASCIIterminal),executable(the file contains the result of compiling a programin a form understandable to some UNIX kernel or another),ordatameaning anything else (data is usually `binary' or non-printable).Exceptions are well-known file formats (core files, tar archives)that are known to contain binary data.When modifying the file/usr/share/misc/file/magicor the program itself, preserve these keywords .People depend on knowing that all the readable files in a directoryhave the word ``text'' printed.Don't do as Berkeley did and change ``shell commands text''to ``shell script''.Note that the file/usr/share/misc/file/magicis built mechanically from a large number of small files inthe subdirectoryMagdirin the source distribution of this program.

The filesystem tests are based on examining the return from astat(2)system call.The program checks to see if the file is empty,or if it's some sort of special file.Any known file types appropriate to the system you are running on(sockets, symbolic links, or named pipes (FIFOs) on those systems thatimplement them)are intuited if they are defined inthe system header file<sys/stat.h>.

The magic number tests are used to check for files with data inparticular fixed formats.The canonical example of this is a binary executable (compiled program)a.outfile, whose format is defined in a.out.hand possiblyexec.hin the standard include directory.These files have a `magic number' stored in a particular placenear the beginning of the file that tells the UNIX operating systemthat the file is a binary executable, and which of several types thereof.The concept of `magic number' has been applied by extension to data files.Any file with some invariant identifier at a small fixedoffset into the file can usually be described in this way.The information identifying these files is read from the compiledmagic file/usr/share/misc/file/magic.mgc ,or /usr/share/misc/file/magicif the compile file does not exist.

If a file does not match any of the entries in the magic file,it is examined to see if it seems to be a text file.ASCII, ISO-8859-x, non-ISO 8-bit extended-ASCII character sets(such as those used on Macintosh and IBM PC systems),UTF-8-encoded Unicode, UTF-16-encoded Unicode, and EBCDICcharacter sets can be distinguished by the differentranges and sequences of bytes that constitute printable textin each set.If a file passes any of these tests, its character set is reported.ASCII, ISO-8859-x, UTF-8, and extended-ASCII files are identifiedas ``text'' because they will be mostly readable on nearly any terminal;UTF-16 and EBCDIC are only ``character data'' because, whilethey contain text, it is text that will require translationbefore it can be read.In addition,filewill attempt to determine other characteristics of text-type files.If the lines of a file are terminated by CR, CRLF, or NEL, insteadof the Unix-standard LF, this will be reported.Files that contain embedded escape sequences or overstrikingwill also be identified.

Oncefilehas determined the character set used in a text-type file,it willattempt to determine in what language the file is written.The language tests look for particular strings (cfnames.h)that can appear anywhere in the first few blocks of a file.For example, the keyword.brindicates that the file is most likely atroff(1)input file, just as the keyword structindicates a C program.These tests are less reliable than the previoustwo groups, so they are performed last.The language test routines also test for some miscellany(such as tar(1)archives).

Any file that cannot be identified as having been writtenin any of the character sets listed above is simply said to be ``data''. 

OPTIONS

-b, --brief
Do not prepend filenames to output lines (brief mode).
-c, --checking-printout
Cause a checking printout of the parsed form of the magic file.This is usually used in conjunction with -mto debug a new magic file before installing it.
-C, --compile
Write a magic.mgc output file that contains a pre-parsed version offile.
-f, --files-from namefile
Read the names of the files to be examined from namefile(one per line) before the argument list.Either namefileor at least one filename argument must be present;to test the standard input, use ``-'' as a filename argument.
-F, --separator separator
Use the specified string as the separator between the filename and thefile result returned. Defaults to ``:''.
-i, --mime
Causes the file command to output mime type strings rather than the moretraditional human readable ones. Thus it may say``text/plain; charset=us-ascii''ratherthan ``ASCII text''.In order for this option to work, file changes the wayit handles files recognised by the command itself (such as many of thetext file types, directories etc), and makes use of an alternative``magic'' file.(See ``FILES'' section, below).
-k, --keep-going
Don't stop at the first match, keep going.
-L, --dereference
option causes symlinks to be followed, as the like-named option inls(1).(on systems that support symbolic links).
-m, --magic-file list
Specify an alternate list of files containing magic numbers.This can be a single file, or a colon-separated list of files.If a compiled magic file is found alongside, it will be used instead.
-n, --no-buffer
Force stdout to be flushed after checking each file.This is only useful if checking a list of files.It is intended to be used by programs that want filetype output from a pipe.
-N, --no-pad
Don't pad filenames so that they align in the output.
-s, --special-files
Normally,fileonly attempts to read and determine the type of argument files whichstat(2)reports are ordinary files.This prevents problems, because reading special files may have peculiarconsequences.Specifying the-soption causesfileto also read argument files which are block or character special files.This is useful for determining the filesystem types of the data in rawdisk partitions, which are block special files.This option also causesfileto disregard the file size as reported bystat(2)since on some systems it reports a zero size for raw disk partitions.
-v, --version
Print the version of the program and exit.
-z, --uncompress
Try to look inside compressed files.
--help
Print a help message and exit.
 

FILES

/usr/share/misc/file/magic.mgc
Default compiled list of magic numbers
/usr/share/misc/file/magic
Default list of magic numbers
/usr/share/misc/file/magic.mime.mgc
Default compiled list of magic numbers, used to output mime types whenthe -i option is specified.
/usr/share/misc/file/magic.mime
Default list of magic numbers, used to output mime types when the -i optionis specified.
/etc/magic
Local additions to magic wisdom.

 

ENVIRONMENT

The environment variableMAGICcan be used to set the default magic number files. 

SEE ALSO

magic(4)- description of magic file format.
strings(1), od(1), hexdump(1)- tools for examining non-textfiles. 

STANDARDS CONFORMANCE

This program is believed to exceed the System V Interface Definitionof FILE(CMD), as near as one can determine from the vague languagecontained therein. Its behaviour is mostly compatible with the System V program of the same name.This version knows more magic, however, so it will producedifferent (albeit more accurate) output in many cases.

The one significant difference between this version and System Vis that this version treats any white spaceas a delimiter, so that spaces in pattern strings must be escaped.For example,
>10    string  language impress        (imPRESS data)

in an existing magic file would have to be changed to
>10    string  language\ impress       (imPRESS data)

In addition, in this version, if a pattern string contains a backslash,it must be escaped.For example
0      string          \begindata      Andrew Toolkit document

in an existing magic file would have to be changed to
0      string          \\begindata     Andrew Toolkit document

SunOS releases 3.2 and later from Sun Microsystems include afile(1)command derived from the System V one, but with some extensions.My version differs from Sun's only in minor ways.It includes the extension of the `&' operator, used as,for example,
>16    long&0x7fffffff >0              not stripped
 

MAGIC DIRECTORY

The magic file entries have been collected from various sources,mainly USENET, and contributed by various authors.Christos Zoulas (address below) will collect additionalor corrected magic file entries.A consolidation of magic file entries will be distributed periodically.

The order of entries in the magic file is significant.Depending on what system you are using, the order thatthey are put together may be incorrect.If your oldfilecommand uses a magic file,keep the old magic file around for comparison purposes(rename it to /usr/share/misc/file/magic.orig). 

EXAMPLES

$ file file.c file /dev/{wd0a,hda}file.c:   C program textfile:     ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),          dynamically linked (uses shared libs), stripped/dev/wd0a: block special (0/0)/dev/hda: block special (3/0)$ file -s /dev/wd0{b,d}/dev/wd0b: data/dev/wd0d: x86 boot sector$ file -s /dev/hda{,1,2,3,4,5,6,7,8,9,10}/dev/hda:   x86 boot sector/dev/hda1:  Linux/i386 ext2 filesystem/dev/hda2:  x86 boot sector/dev/hda3:  x86 boot sector, extended partition table/dev/hda4:  Linux/i386 ext2 filesystem/dev/hda5:  Linux/i386 swap file/dev/hda6:  Linux/i386 swap file/dev/hda7:  Linux/i386 swap file/dev/hda8:  Linux/i386 swap file/dev/hda9:  empty/dev/hda10: empty$ file -i file.c file /dev/{wd0a,hda}file.c:      text/x-cfile:        application/x-executable, dynamically linked (uses shared libs),not stripped/dev/hda:    application/x-not-regular-file/dev/wd0a:   application/x-not-regular-file
 

HISTORY

There has been a filecommand in every UNIX since at least Research Version 4(man page dated November, 1973).The System V version introduced one significant major change:the external list of magic number types.This slowed the program down slightly but made it a lot more flexible.

This program, based on the System V version,was written by Ian Darwin <ianAATTdarwinsys.com>without looking at anybody else's source code.

John Gilmore revised the code extensively, making it better thanthe first version.Geoff Collyer found several inadequaciesand provided some magic file entries.Contributions by the `&' operator by Rob McMahon, cudcvAATTwarwick.ac.uk, 1989.

Guy Harris, guyAATTnetapp.com, made many changes from 1993 to the present.

Primary development and maintenance from 1990 to the present byChristos Zoulas (christosAATTastron.com).

Altered by Chris Lowth, chrisAATTlowth.com, 2000:Handle the ``-i'' option to output mime type strings and using an alternativemagic file and internal logic.

Altered by Eric Fischer (enfAATTpobox.com), July, 2000,to identify character codes and attempt to identify the languagesof non-ASCII files.

The list of contributors to the "Magdir" directory (source for the/etc/magicfile) is too long to include here.You know who you are; thank you. 

LEGAL NOTICE

Copyright (c) Ian F. Darwin, Toronto, Canada, 1986-1999.Covered by the standard Berkeley Software Distribution copyright; see the fileLEGAL.NOTICE in the source distribution.

The filestar.handis_tar.cwere written by John Gilmore from his public-domaintarprogram, and are not covered by the above license. 

BUGS

There must be a better way to automate the construction of the Magicfile from all the glop in magdir.What is it?Better yet, the magic file should be compiled into binary (say,ndbm(3)or, better yet, fixed-lengthASCIIstrings for use in heterogenous network environments) for faster startup.Then the program would run as fast as the Version 7 program of the same name,with the flexibility of the System V version.

Fileuses several algorithms that favor speed over accuracy,thus it can be misled about the contents oftextfiles.

The support fortextfiles (primarily for programming languages)is simplistic, inefficient and requires recompilation to update.

There should be an ``else'' clause to follow a series of continuation lines.

The magic file and keywords should have regular expression support.Their use ofASCII TABas a field delimiter is ugly and makesit hard to edit the files, but is entrenched.

It might be advisable to allow upper-case letters in keywordsfor e.g.,troff(1)commands vs man page macros.Regular expression support would make this easy.

The program doesn't grok FORTRAN.It should be able to figure FORTRAN by seeing some keywords which appear indented at the start of line.Regular expression support would make this easy.

The list of keywords in ascmagicprobably belongs in the Magic file.This could be done by using some keyword like `*' for the offset value.

Another optimisation would be to sortthe magic file so that we can just run down all thetests for the first byte, first word, first long, etc, once wehave fetched it.Complain about conflicts in the magic file entries.Make a rule that the magic entries sort based on file offset ratherthan position within the magic file?

The program should provide a way to give an estimate of ``how good'' a guess is.We end up removing guesses (e.g. ``From '' as first 5 chars of file) becausethey are not as good as other guesses (e.g. ``Newsgroups:'' versus``Return-Path:'').Still, if the others don't pan out, it should be possible to use thefirst guess.

This program is slower than some vendors' file commands.The new support for multiple character codes makes it even slower.

This manual page, and particularly this section, is too long. 

AVAILABILITY

You can obtain the original author's latest version by anonymous FTPonftp.astron.comin the directory/pub/file/file-X.YZ.tar.gz


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
FILES
ENVIRONMENT
SEE ALSO
STANDARDS CONFORMANCE
MAGIC DIRECTORY
EXAMPLES
HISTORY
LEGAL NOTICE
BUGS
AVAILABILITY

This document was created byman2html,using the manual pages.
 
ICM Bot detect detector