From owner-freebsd-arch Thu Sep 14 12:30:50 2000 Delivered-To: freebsd-arch@freebsd.org Received: from soda.csua.Berkeley.edu (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id BC74537B424 for ; Thu, 14 Sep 2000 12:30:48 -0700 (PDT) Received: from soda.csua.Berkeley.edu (localhost [127.0.0.1]) by soda.csua.Berkeley.edu (8.8.8/) via ESMTP id MAA20323 for ; Thu, 14 Sep 2000 12:30:47 -0700 (PDT) env-from (ranga@CSUA.Berkeley.EDU) Message-Id: <200009141930.MAA20323@soda.csua.Berkeley.edu> To: freebsd-arch@FreeBSD.ORG Subject: Re: Request for review: nsswitch In-Reply-To: Your message of "Thu, 14 Sep 2000 22:15:28 +0300." <20000914221528.B66058@netch.kiev.ua> Date: Thu, 14 Sep 2000 12:30:47 -0700 From: Sriranga Veeraraghavan Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One of the UNIX systems I've used over the years, probably SunOS, > > allowed you to add the name of a host as a {sym,}link to rlogin; > > the executable would check argv[0] and if it wasn't a recognized > > pattern try it as a hostname. The common usage was to add links > > to your favorite hosts in /hosts/name and add that to your PATH. > > > > My vote would be to add this feature to ssh. > > I consider this feature as evil. Hi, I don't think it is a good idea to add such a feature (of dubious benefit to most users) to a program like ssh. If you really want something like this create a script like the following in $HOME/bin: #!/bin/sh exec ssh `basename "$0"` $@ and symlink it to the hostnames you want. Then add $HOME/bin to PATH and you have basically the same functionality. ----ranga To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message