From owner-freebsd-questions@FreeBSD.ORG Fri Jun 25 19:24:15 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A2B3106564A for ; Fri, 25 Jun 2010 19:24:15 +0000 (UTC) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.103.93]) by mx1.freebsd.org (Postfix) with ESMTP id 6A10D8FC17 for ; Fri, 25 Jun 2010 19:24:15 +0000 (UTC) Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.14.2/8.13.8) with ESMTP id o5PJO50P002895 for ; Fri, 25 Jun 2010 14:24:05 -0500 (CDT) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <201006251924.o5PJO50P002895@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2893.1277493845.1@dc.cis.okstate.edu> Date: Fri, 25 Jun 2010 14:24:05 -0500 From: Martin McCormick Subject: Running an Old Kernel 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: Fri, 25 Jun 2010 19:24:15 -0000 I have been attempting to shut off that "last login" message that occurs on some FreeBSD systems every time one runs a sudo command. I decided to bring back the last kernel which was the original Generic kernel from the FreeBSD distribution disk for FreeBSD8.0 to see if the problem went away. If it did, that would indicate that the problem starts after one applies the latest patches and rebuilds the kernel. The handbook covers building a new kernel very well, but I appear to be missing something. In /boot is loader and loader.old. Isn't loader.old the image of the previous kernel? I copied loader to loader.new since it should be the current image and then copied loader.old to loader and rebooted. The "last login" message was still there and dmesg still showed the production date of the new kernel. In other words, nothing changed. Shouldn't I have seen the production date of the original kernel? Thank you. I have actually built many kernels and most were simply a rebuild of the generic kernel after applying patches so I don't roll back a kernel very often. Fortunately, both the old and new kernels work. I think the "last login" nuisance started right after installing the patched kernel. Martin McCormick