From owner-freebsd-questions@FreeBSD.ORG Tue May 11 17:10:50 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 E617416A4CE for ; Tue, 11 May 2004 17:10:50 -0700 (PDT) Received: from pd4mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BAD143D4C for ; Tue, 11 May 2004 17:10:50 -0700 (PDT) (envelope-from flowers@users.sourceforge.net) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-ser.prod.shaw.ca [10.0.141.178])2003))freebsd-questions@freebsd.org; Tue, 11 May 2004 18:10:49 -0600 (MDT) Received: from pn2ml4so.prod.shaw.ca ([10.0.121.148]) by pd3mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0HXK00H0VR61WJ30@pd3mr2so.prod.shaw.ca> for freebsd-questions@freebsd.org; Tue, 11 May 2004 18:10:49 -0600 (MDT) Received: from sirius (S0106004001438e5b.cg.shawcable.net [68.144.47.89]) 2003))freebsd-questions@freebsd.org; Tue, 11 May 2004 18:10:49 -0600 (MDT) Date: Tue, 11 May 2004 18:11:07 -0600 From: Dan MacMillan To: freebsd-questions@freebsd.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Subject: make world : did it fail? 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: Wed, 12 May 2004 00:10:51 -0000 Hi. I just ran the make world procedure on a freshly installed FreeBSD system. After dropping to single user mode, I ran: cd /usr/src script /root/mw/mw-200405111310.out make buildworld && make buildkernel KERNCONF=GOLLUM && make installkernel KERNCONF=GOLLUM && reboot I do things this way because I don't want to babysit the machine waiting to proceed to the next step. When I heard the computer reboot (it's sitting right next to me), I logged in and ran: tail /root/mw.out To see if anything untoward had happened. The result looks like this: > tail /root/mw/mw-200405111310.out install -o root -g wheel -m 555 safe.ko /boot/kernel ===> sbni install -o root -g wheel -m 555 if_sbni.ko /boot/kernel ===> scsi_low install -o root -g wheel -m 555 scsi_low.ko /boot/kernel ===> smbfs install -o root -g wheel -m 555 smbfs.ko /boot/kernel ===> sound ===> sound/pcm install -o root -g wheel -m 555 snd_> Doesn't look so good, does it? Now I'm not sure if it rebooted because of the '&& reboot' or because it ran into some terrible no good awful bad problem. I checked the timestamps on all the files in /boot/kernel and they all look good (all .ko files dated today within 1 minute of each other, the kernel a few minutes older). The number of files in /boot/kernel matches the number in /boot/kernel.old. I ran (from my home directory): ls /boot/kernel > kernel ls /boot/kernel.old > kernel.old diff kernel kernel.old And there are no differences. uname -a now reports 5.2.1-RELEASE-p6. I'm thinking that probably what happened is that the machine rebooted without the remaining script output being flushed to disk. Is there any way to tell for sure? And should this even be possible? I've followed this technique on my home machines several times and never got the script output truncated like this. I'm now cursing myself for putting the && reboot on there. I can re-run the make world procedure, but unless I figure out for sure what happened here I'm afraid it's indicative of a more significant problem. Thanks in advance. -- Danny MacMillan