Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!columbia!amsterdam!dupuy
From: dupuy@amsterdam.UUCP
Newsgroups: comp.unix.wizards
Subject: useful /etc/magic entries
Message-ID: <4560@columbia.UUCP>
Date: Fri, 24-Apr-87 06:07:32 EST
Article-I.D.: columbia.4560
Posted: Fri Apr 24 06:07:32 1987
Date-Received: Sat, 25-Apr-87 08:27:58 EST
Sender: nobody@columbia.UUCP
Reply-To: dupuy@amsterdam.columbia.edu (Alexander Dupuy)
Distribution: world
Organization: Columbia University Computer Science Dept.
Lines: 24
Summary: How to recognize VAX executables with file(1) on a Sun

Here are a few lines you can add to /etc/magic on your sun workstations in
order to recognize VAX executables and objects.  I guess you could do something
similar (in reverse) for your vaxen, but since 4.3+NFS' file(1) doesn't look
for /etc/magic, I've never bothered.  It really should be built in to file(1)
so you would see the state of setuid/setgid/sticky bits.  Or actually, there
should be support for checking that sort of thing in /etc/magic.

I've also thrown in an entry for the new P1003 tar format, based on John
Gilmore's implementation (haven't tested it).  Sadly, the ``standard'' Unix tar
doesn't have any magic bits...

0	long		00700200000	VAX executable
>16	long&0x7fffffff	>0		not stripped
0	long		01000200000	VAX pure executable
>16	long&0x7fffffff	>0		not stripped
0	long		01300200000	VAX demand-paged pure executable
>16	long&0x7fffffff	>0		not stripped
0	long		01100200000	PDP-11 executable
257	string		ustar  		new standard tar archive

@alex
---
arpanet: dupuy@columbia.edu
uucp:	...!seismo!columbia!dupuy