From owner-freebsd-questions@FreeBSD.ORG Wed May 2 07:23:13 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AC5AC16A400 for ; Wed, 2 May 2007 07:23:13 +0000 (UTC) (envelope-from lalev@uni-svishtov.bg) Received: from ns.uni-svishtov.bg (ns2.uni-svishtov.bg [195.20.24.1]) by mx1.freebsd.org (Postfix) with ESMTP id 2CA6A13C447 for ; Wed, 2 May 2007 07:23:12 +0000 (UTC) (envelope-from lalev@uni-svishtov.bg) Received: from mail.uni-svishtov.bg (grinch.uni-svishtov.bg [195.20.24.9]) by ns.uni-svishtov.bg (8.13.8/8.13.3) with ESMTP id l427OZYo002916 for ; Wed, 2 May 2007 10:24:35 +0300 (EEST) (envelope-from lalev@uni-svishtov.bg) Received: from localhost (mail.uni-svishtov.bg [195.20.24.9]) by mail.uni-svishtov.bg (8.13.8/8.12.6) with ESMTP id l427MDIR017198 for ; Wed, 2 May 2007 10:22:13 +0300 (EEST) (envelope-from lalev@uni-svishtov.bg) MIME-Version: 1.0 Date: Wed, 2 May 2007 10:22:13 +0300 From: Angelin Lalev To: freebsd-questions@freebsd.org Message-ID: <38110740f12a9e51cb96f1a0014b768f@uni-svishtov.bg> X-Sender: lalev@uni-svishtov.bg User-Agent: RoundCube Webmail/0.1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail.uni-svishtov.bg Subject: freebsd-update question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2007 07:23:13 -0000 I have machine wich is build from sources (FreeBSD 6.2p3 , RELENG_6_2). Can I use freebsd-update on that machine straight away? In the article that appears on top of google (http://www.daemonology.net/freebsd-update/binup.html), there is section about removing kernel counters, perllocal.pod etc. It's not clear for me if that step should be taken at server's or the client's side.