From owner-freebsd-questions@FreeBSD.ORG Mon Mar 8 09:22:12 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC8BB16A4CE for ; Mon, 8 Mar 2004 09:22:12 -0800 (PST) Received: from destiny.chrononomicon.com (mail.chrononomicon.com [65.193.73.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54E4A43D1F for ; Mon, 8 Mar 2004 09:22:12 -0800 (PST) (envelope-from bsilver@chrononomicon.com) Received: from [IPv6:::1] (destiny.chrononomicon.com [192.168.1.42]) by destiny.chrononomicon.com (Postfix) with ESMTP id 9DA5B1FDFF; Mon, 8 Mar 2004 12:21:59 -0500 (EST) In-Reply-To: <000401c40531$0ab88de0$0100000a@liberty> References: <000401c40531$0ab88de0$0100000a@liberty> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2121A5DA-7125-11D8-B6F7-000A956D2452@chrononomicon.com> Content-Transfer-Encoding: 7bit From: Bart Silverstrim Date: Mon, 8 Mar 2004 12:22:09 -0500 To: "Ioannis Vranos" X-Mailer: Apple Mail (2.612) cc: FreeBSD Questions Mailing List Subject: Re: Update utility X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2004 17:22:12 -0000 On Mar 8, 2004, at 12:15 PM, Ioannis Vranos wrote: > Is there any utility in FreeBSD 4.9 to check for possible updates/bug > fixes > via internet? > I *think* have have kind of a handle on this on the server I just installed... I usually do a cvsup to update the list of the ports tree, then use a procedure I picked out of http://www.freebsddiary.org/portupgrade.php to update applications with portupgrade. If anyone else has a method other than this, I'd love to know the procedure :-) This only updates ports. Updating FreeBSD, I don't know of anything other than if you find a security advisory, you have to have the src tree and patch that portion and recompile whatever had the vulnerability, following the advisory instructions. I'm thinking that since most daemons/applications are from ports, keeping your ports tree updated should limit most remote exploits...I would be interested in knowing of a way to check whether the installation of the OS is up to date, though.