From owner-freebsd-ports@FreeBSD.ORG Wed May 10 03:54:30 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA37E16A404 for ; Wed, 10 May 2006 03:54:30 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D09F43D45 for ; Wed, 10 May 2006 03:54:30 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id k4A3sUrt010332 for ; Tue, 9 May 2006 20:54:30 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id k4A3sURv010331 for ports@freebsd.org; Tue, 9 May 2006 20:54:30 -0700 (PDT) (envelope-from david) Date: Tue, 9 May 2006 20:54:30 -0700 From: David Wolfskill To: ports@freebsd.org Message-ID: <20060510035430.GM545@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: Port maintainer query: what to use to specify serial port? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Wolfskill List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2006 03:54:31 -0000 The author of the port I maintain (astro/gpsman) has recently informed me that he's released an updated distribution, so I'd like to update the FreeBSD port to correspond. It's a pretty simple port -- it's a Tcl/Tk application; there's no compilation involved. But it is developed under Linux, so the port has a few patches to the author's code to make things work better (or "at all") in FreeBSD. One of the patches has historically changed the default serial port from /dev/ttyS0 to /dev/cuaa0. But I just noticed that my laptop (running 6.1-STABLE) doesn't have /dev/cuaa0. Right; that was one of the changes from 4.x, so it should be /dev/cuad0... well, for 6.x. Is there a decent way to make the replacement appropriate for the OS running at the time of installation (that isn't so much additional hassle that it's not really worth the bother)? Do we care enough about 4.x to address this issue? Please respond to me, as I'm not subscribed to this list (Reply-To set intentionally); feel free to also include the list as a recipient of your message if you believe it will be beneficial to do so. Thanks! Peace, david (still running 4.x on some boxen) -- David H. Wolfskill david@catwhisker.org Spam received via "opt-out" lists is still spam, and should be treated as such. See http://www.catwhisker.org/~david/publickey.gpg for my public key.