From owner-freebsd-arch@FreeBSD.ORG Mon Nov 3 20:56:45 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0242AA31 for ; Mon, 3 Nov 2014 20:56:45 +0000 (UTC) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B28F599A for ; Mon, 3 Nov 2014 20:56:44 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.9/8.14.9) with ESMTP id sA3Kuc3B006301; Mon, 3 Nov 2014 15:56:39 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.9/8.14.4/Submit) id sA3KubAk006298; Mon, 3 Nov 2014 15:56:37 -0500 (EST) (envelope-from wollman) Date: Mon, 3 Nov 2014 15:56:37 -0500 (EST) From: Garrett Wollman Message-Id: <201411032056.sA3KubAk006298@hergotha.csail.mit.edu> To: imp@bsdimp.com Subject: Re: Why do we have @ in modules builds? X-Newsgroups: mit.lcs.mail.freebsd-arch In-Reply-To: <3285BC54-05D8-41DB-88FE-BAD681A3E45B@bsdimp.com> References: <3285BC54-05D8-41DB-88FE-BAD681A3E45B@bsdimp.com> Organization: none X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (hergotha.csail.mit.edu [127.0.0.1]); Mon, 03 Nov 2014 15:56:39 -0500 (EST) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on hergotha.csail.mit.edu Cc: freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2014 20:56:45 -0000 In article <3285BC54-05D8-41DB-88FE-BAD681A3E45B@bsdimp.com>, Warner Losh writes: >Does anybody recall why we have @ symlink in our module builds? Back in the mists of ancient time, it was a way to allow easy relocation of kernel builds -- that way, there was only one symlink to change rather than two (or perhaps even more). I'm reasonably convinced it's my fault, anyway. Forgive me: I was still young then. -GAWollman