make world : did it fail?

From: Dan MacMillan (flowers_at_users.sourceforge.net)
Date: 05/12/04

  • Next message: John Lee: "arplookup error"
    Date: Tue, 11 May 2004 18:11:07 -0600
    To: freebsd-questions@freebsd.org
    
    

    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
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: John Lee: "arplookup error"

    Relevant Pages

    • RE: make world : did it fail?
      ... I know from the script output that the buildworld and buildkernel succeeded. ... The only step that is suspect is the installkernel. ... It reported the unpatched kernel. ... When I heard the computer reboot (it's sitting ...
      (freebsd-questions)
    • Re: cx88 totally fried in 2.6.15-rcX -was- Re: HD3000 - no NTSC via tuner
      ... >> proceedure as it would apply to a working 2.6.14.x kernel. ... My script, fwiw, renames one ... >> The exception being that I understand the Makefile now has an install ... Now the acid test, reboot... ...
      (Linux-Kernel)
    • Re: [FC3] kernel panic after selinux-policy-targeted update
      ... whilst the kernel update takes effect only after a ... > versions (and possibly check the running kernel version in a script). ... > (Can a script cause an RPM installation to fail?) ... If you are upgrading the kernel you have to reboot. ...
      (Fedora)
    • Re:SOLVVED vinum crashes the Box... WRONG POSTING
      ... vinum crashes the Box by using more then ten disks on ... > With this configuration vinum crashes the Machine with this Message: ... > I'm going to enable the kernel debugger now... ... >> while devfs rules works for those, but they vanish on reboot. ...
      (freebsd-stable)
    • Re: WMI and Joining Domain (sysprep related)
      ... > Just keep in mind that you have to rename the computer and reboot before you ... > use a script to automaticaly generate a sysprep.inf file that includes ... Dim sps_barcode,Flag,ExtraMsg ... '' Get workstation BIOS info for oeminfo '' ...
      (microsoft.public.scripting.vbscript)