From owner-freebsd-questions  Thu Aug 29 06:50:43 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA08693
          for questions-outgoing; Thu, 29 Aug 1996 06:50:43 -0700 (PDT)
Received: from croute.com (ishm2.croute.com [199.97.106.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA08680;
          Thu, 29 Aug 1996 06:50:39 -0700 (PDT)
Received: from bldg1.croute.com by croute.com (4.1/SMI-4.1)
	id AA17840; Thu, 29 Aug 96 08:50:36 CDT
Received: from COMPUROUTE/SpoolDir by bldg1.croute.com (Mercury 1.13);
    Thu, 29 Aug 96 8:50:31 +600
Received: from SpoolDir by COMPUROUTE (Mercury 1.13); Thu, 29 Aug 96 8:50:01 +600
From: "Larry Dolinar" <LARRYD@bldg1.croute.com>
Organization:  CompuRoute, Inc.
To: owner-questions@freebsd.org
Date:          Thu, 29 Aug 1996 08:49:54 +600 CDT
Mime-Version:  1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject:       Re: Sync and Reboot question.
Cc: FreeBSD questions <questions@freebsd.org>
X-Confirm-Reading-To: "Larry Dolinar" <LARRYD@bldg1.croute.com>
X-Pmrqc:       1
Priority: normal
X-Mailer: Pegasus Mail v3.22
Message-Id: <C310A5414F8@bldg1.croute.com>
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

|  From:           Anthony Hill <ahill@interconnect.com.au>

|  Yes, you wont lose any data after doing a sync, although the FS may still 
|  be left in a strange state. FreeBSD has had this problem as long as I 
|  have been using it (a couple of years). People keep blaming it on 
|  "faulty" BIOS's, however after seeing the problem on three different 
|  computers with three different BIOS's which were in all other aspects fine,
|  I am forming the opinion that it is just one of the nastier features of 
|  FreeBSD.
|  

FWIW...

I've run 2.1.0-R on 2 different 486 MBs at home (both PCI) and a couple 
of no-name 486's along with an Asus P55TP4/Intel P75 here and haven't 
seen this yet.  All are either Award or AMI bios.

On the other hand, all my Unix systems have a /.shut script (500
permissions) that essentially looks like this:

#
cd /
/sbin/shutdown -h now

The path to shutdown varies based on platform (Sun 4.x, Solaris, 
FreeBSD).  For me the "press any key to restart" is a welcome annoyance.  
I have a different problem with TCP/IP that I'll post separately.

cheers,
larry