From owner-freebsd-hackers Mon Mar 2 20:46:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01287 for freebsd-hackers-outgoing; Mon, 2 Mar 1998 20:46:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01273; Mon, 2 Mar 1998 20:45:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id UAA15161; Mon, 2 Mar 1998 20:44:14 -0800 (PST) Message-Id: <199803030444.UAA15161@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: asami@FreeBSD.ORG (Satoshi Asami) cc: mike@smith.net.au, jkh@time.cdrom.com, regnauld@deepo.prosa.dk, hackers@FreeBSD.ORG Subject: Re: ports for X11 stuff In-reply-to: Your message of "Mon, 02 Mar 1998 11:52:43 PST." <199803021952.LAA26193@vader.cs.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Mar 1998 20:44:13 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * A question - would it be desirable for X to be installed, by default, > * somewhere *else*, and just symlinked into /usr? Should it go in > * /usr/local, so that an experienced admin can assign a separate > * filesystem for this? > > Yes. > > Actually, if you can do something like "if /usr/local is a separate > filesystem from /usr or a symlink to a directory in a separate > filesystem from /usr, then make /usr/X11R6 a symlink into > /usr/local/X11R6", that will be great, but that's probably asking too > much. :) It's quite achievable; the question is (as Jordan asked) whether it's going to surprise people that *expect* it to be in /usr. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message