rbj@dsys.icst.nbs.gov (Root Boy Jim) (05/02/89)
? From: "T. William Wells" <bill@twwells.uucp> ? Another way to handle different capabilities is to create a directory ? containing files corresponding to each capability. (Isn't there ? something like this in the latest Unixes?) ? That way, things like shells can test them as easily as programs. ? /etc/capabilities/symlinks ? /etc/capabilities/longnames (containing the number of characters) ? /etc/capabilities/cpp (containing the path for cpp) ? /etc/capabilities/termcap (containing the library path) ? /etc/capabilities/terminfo (containing the library path) ? /etc/capabilities/coff ? And the possibilities are, unfortunately, endless. :-) Or, perhaps a file containing entrys sepatared by colons: /etc/oscap! # Version 6 had source code, 14 character filenames and ran on PDP-11s v6|Version-6|Sixth Edition:sc:os=/unix:pn#14:mt=pdp: # Version 7 added Alarm(2), fsck, and other stuff v7|Version-7|Seventh Edition:os=/unix:pn=14:al:fs:tc=v6: # 4.1 ran on Vaxen, boots from /vmunix, had paging, termcap b1:bsd-4.1:os=/vmunix:pg:mt=vax:TC=/etc/termcap:tc=v7: # 4.2 adds paging, long file names, symbolic links b2|bsd-4.2:pn#255:sl:tc=b1: # 4.3 adds name server, rdist b3:bsd-4.3:ns:rd:tc=b2: # Sequent's DYNIX has no source code, boots /dynix, parallel processing dy|dynix|Sequent Dynix:sc@:os=/dynix:pp:tc=4.2: # Sun OS 3.5 is similar to 4.2, has name server, rdist, nfs, yp, xdr, rpc s3|sun3|sun3.5|Sun OS 3.5:sc@:ns:rd:nf:yp:xd:rp:tc=b2: # Sun OS 4.0 has dynamic linking s4|sun4|sun4.0|Sun OS 4.0:ld=dynamic:tc=s3: # System V has no source, COFF, terminfo, rotated manual sections, paging sv|sys5|sysv|System V:sc@:ld=coff:TI=/usr/lib/terminfo:fm:pg:tc=v7: You get the idea, and I hope, the joke. No flames on the correctness or completeness of the preceding. ? Bill { uunet | novavax } !twwells!bill Root Boy Jim is what I am Are you what you are or what?