Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!bbn!uwmcsd1!ig!agate!ucbvax!hplabs!otter!kers
From: kers@otter.hple.hp.com (Christopher Dollin)
Newsgroups: comp.arch
Subject: Re: ITS translations: security problem?
Message-ID: <780002@otter.hple.hp.com>
Date: 8 Feb 88 08:12:38 GMT
References: <9690@tekecs.TEK.COM>
Organization: Hewlett-Packard Laboratories, Bristol, UK.
Lines: 24

"mjr@osiris.UUCP Marcus J. Ranum" writes:

|>         So you add s|^/bin/rm$|/user/me/bin/rm| to your
|>       translation list."
|>
|
|        Rather than building things like this into the OS, they can just as
|easily be handled in the shell. Rather than forcing everyone to worry about
|security problems, etc, etc, why not simply have your shell support all the
|translation you can handle, since the UNIX file system layout is pretty
|straightforward.

repeat 1000 times 'No!\n'.pr endrepeat ...

If you do that, then EVERY *ING PROGRAM has to know how to handle translations.
No all programs get all their filenames from the shell. Editors and cpp (for
#include) are obvious examples. It belongs in the filesystem (which, for 
heavens sake, shouldn't be part of the *ing KERNAL).

I get peeved enough when some futility doesn't understand "$" (or "~") in
filenames.

Regards,
Kers                                    | "Why Lisp if you can talk Poperly?"