From owner-freebsd-current@FreeBSD.ORG Sat Jun 19 21:26:16 2004 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 C670816A4CE for ; Sat, 19 Jun 2004 21:26:16 +0000 (GMT) Received: from bsd.naebunny.net (adsl-67-38-156-22.dsl.dytnoh.ameritech.net [67.38.156.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 583B043D48 for ; Sat, 19 Jun 2004 21:26:06 +0000 (GMT) (envelope-from derwood@naebunny.net) Received: from derwood2 (unknown [192.168.0.246]) with ESMTP id 7910E2AD09 for ; Sat, 19 Jun 2004 17:25:52 -0400 (EDT) From: "Darin" To: Date: Sat, 19 Jun 2004 17:26:01 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcRWRATg4ZbGUry8Tzqoq5/F4S+jXA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Message-Id: <20040619212552.7910E2AD09@bsd.naebunny.net> Subject: 5.2.1 boot question 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: Sat, 19 Jun 2004 21:26:16 -0000 I've been working on getting a system ready for my daughter to use, and have run into a problem. The system is running 5.2.1-RELEASE-p8 that was cvsuped yesterday. The problem was caused by the Kuser app that I installed as part of the KDE3 port. For some reason it set all of the accounts on the system to expired, including root. I was able to fix the problem by rebuilding spwd.db and pwd.db with pwd_mkdb. So, I can log on again and su to root to finish up any ports that I need to compile in. However, when the machine boots, I get the following on the screen and in /var/log/messages: Jun 19 14:17:41 dell1 syslogd: kernel boot file is /boot/kernel/kernel Jun 19 14:17:41 dell1 kernel: term R *Handler Int Jun 19 14:17:41 dell1 kernel: 14 posix2_fort_dev R *Handler Int Jun 19 14:17:41 dell1 kernel: 15 posix2_fort_run R *Handler Int Jun 19 14:17:41 dell1 kernel: 16 posix2_localedef R *Handler Int Jun 19 14:17:41 dell1 kernel: 17 posix2_sw_dev R *Handler Int Jun 19 14:17:41 dell1 kernel: 18 posix2_upe R *Handler Int Jun 19 14:17:41 dell1 kernel: 19 stream_max R *Handler Int Jun 19 14:17:41 dell1 kernel: 20 tzname_max R *Handler Int Jun 19 14:17:41 dell1 kernel: 9 p1003_1b RW Node Jun 19 14:17:41 dell1 kernel: 1 asynchronous_io R *Handler Int Jun 19 14:17:41 dell1 kernel: 2 mapped_files R *Handler Int Jun 19 14:17:41 dell1 kernel: 3 memlock R *Handler Int Jun 19 14:17:41 dell1 kernel: 4 memlock_range R *Handler Int Jun 19 14:17:41 dell1 kernel: 5 memory_protection R *Handler Int Jun 19 14:17:41 dell1 kernel: 6 message_passing R *Handler Int Jun 19 14:17:41 dell1 kernel: 7 prioritized_io R *Handler Int Jun 19 14:17:41 dell1 kernel: 8 priority_scheduling R *Handler Int This is only a small part of what I get. It goes on for pages and pages. I'm only slightly concerned because the system seems to run fine after completing the boot process. I'm just not certain what it all means. Any ideas on whats causing this and how I can make it go away? Or is it just completely harmless and nothing to worry about.. I tried searching listserve archives, the handbook and google, and didn't find anything.. Any ideas on whats causing this and how I can make it go away? Or is it just completely harmless and nothing to worry about.. Darin -