Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!rochester!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!sunybcs!rutgers!apple!ames!pacbell!att!chinet!kdb
From: kdb@chinet.chi.il.us (Karl Botts)
Newsgroups: comp.sys.att
Subject: Re: 6386 shutdown: I CAN'T BELIEVE at&t was really this stupid!
Message-ID: <8714@chinet.chi.il.us>
Date: 22 Jul 89 00:28:47 GMT
References: <483@oglvee.UUCP> <14401@bfmny0.UUCP>
Reply-To: kdb@chinet.chi.il.us (Karl Botts)
Organization: Chinet - Public Access Unix
Lines: 17

In article <14401@bfmny0.UUCP> tneff@bfmny0.UUCP (Tom Neff) writes:
>If you think about it for a second, by the time UNIX is totally ready
>to be "rebooted now," you shouldn't have an active file system to
>read scripts from.  The kernel is ALL THAT'S LEFT.  So the message
>has to go there.  (I suppose it could be linked in at rebuild time.)

This is simply not true; the root file system should be and is still mounted
at reboot time.  When a normal Unix system comes up, it comes up  by
default in single user mode and the root filesystem is already mounted.
You can read and write in the normal manner to the root filesystem, and
it is _your_ job to make sure it is synced before you reboot.  This is
the same state the system is in just before you reboot in the usual
shutdown script.
Incidentally, it is not possible for the reboot command itself (when it
is available as a sfotware command) to automatically sync the system,
because there are times when you _must_ reboot the system without
syncing, i.e., after rebuilding the free list with fsck.