From owner-freebsd-current@FreeBSD.ORG Thu May 19 16:10:19 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6C2416A4CE for ; Thu, 19 May 2005 16:10:19 +0000 (GMT) Received: from spadger.best.vwh.net (spadger.best.vwh.net [192.220.100.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7E9A43DB4 for ; Thu, 19 May 2005 16:10:19 +0000 (GMT) (envelope-from spadger@spadger.best.vwh.net) Received: (qmail 91989 invoked by uid 25849); 19 May 2005 16:10:12 -0000 Date: Thu, 19 May 2005 09:10:12 -0700 From: Andrew Sparrow To: "Brandon S. Allbery KF8NH" Message-ID: <20050519091012.A70581@spadger.best.vwh.net> References: <20815.1116509187@critter.freebsd.dk> <20050519150311.GA9240@crodrigues.org> <1116516218.2850.0.camel@pyanfar.ece.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <1116516218.2850.0.camel@pyanfar.ece.cmu.edu>; from allbery@ece.cmu.edu on Thu, May 19, 2005 at 11:23:33AM -0400 X-Mailman-Approved-At: Fri, 20 May 2005 12:23:53 +0000 cc: freebsd-current@freebsd.org Subject: Re: why omshell when no dhcpd ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2005 16:10:19 -0000 On Thu, May 19, 2005 at 11:23:33AM -0400, Brandon S. Allbery KF8NH wrote: > It can be used to query a running dhclient for lease information (and > I've wanted to do so a few times only to find that omshell apparently > isn't built on !current...). What he said. Admittedly you can do most everything without it less elegantly by grovelling around in the lease file and/or killing/re-starting dhclient - but having to build the port (on !current) to get omshell is kind of sub-optimal, especially as omshell is the suggested method of pausing dhclient prior to suspending a mobile client and resuming on a different network. So, killing dhclient works - but it'd be preferable to use rc.suspend/rc.resume to pause/restart dhclient automatically when using a mobile profile. IIRC (been a while), the lack of omshell is reminiscent of building OpenSSL from ports to get some of the standard CA management scripts, even though SSL is in the base system. Cheers, AS