From owner-freebsd-hackers Wed May 28 20:21:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA21051 for hackers-outgoing; Wed, 28 May 1997 20:21:33 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA21046 for ; Wed, 28 May 1997 20:21:29 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id UAA25205; Wed, 28 May 1997 20:21:39 -0700 (PDT) To: Brian Somers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: rstartd on freefall In-reply-to: Your message of "Thu, 29 May 1997 03:36:01 BST." <199705290236.DAA12948@awfulhak.demon.co.uk> Date: Wed, 28 May 1997 20:21:39 -0700 Message-ID: <25200.864876099@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Any chance of someone with God privs doing a > > # ln -s /usr/X11R6/bin/rstartd /usr/bin/rstartd > > on freefall ? TIA. None at all. :-) Seriously, putting arbitrary things into /usr/bin is just evil and every time we've allowed that kind of hackery on freefall, we've regretted it deeply come the next upgrade and suddenly all sorts of things are falling over even though we have a perfectly good OS installation and /usr/local & /usr/X11R6 are resurrected properly. I won't even go into the evils of rsh based (vs ssh based) execution protocols - the /usr/bin issue is enough to kill your request stone dead. :-| Jordan