We don't support setuid scripts, why should we support capabilitied scripts?
Handle them both the same way: a "wrapper program" which is
setuid/capabilitied.
If you really still care about a.out, I suppose you could add yet another
silly extension to it... if it can cope with more baggage layered on top.
IMHO a.out has far outlived its usefulness --- it started out as a PDP11
memory image (anyone else remember the original purpose of the "magic number"
at the beginning of an a.out file?) and has been getting more and more
unwieldy to work with (check out how global constructors/destructors "work"
for an example... hmmm, maybe you could bring back "robotussin" if you're
desperate) as time has passed. It's time to give up on it. Again, if you
really need to use a.out for some reason (e.g. no source available for some
reason), the easiest way is to use an ELF wrapper program as above.
--
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering KF8NH
We are Linux. Resistance is an indication that you missed the point.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/