systemd depends so heavily on a files it can not reboot

[Gordon Messmer]

On 07/09/2013 06:17 AM, John Reiser wrote:
> Yes it does, because the rest of the system might not be quiescent
> during the first sync.

While that is certainly true, "sync" doesn't make the rest of the system 
quiescent.

> The first sync disturbs the system
> with an impulse of activity.  This may cause the rest of
> the processes to react in strange an wonderful ways, including
> creating many changed-and-unwritten blocks.

Now I can't tell if you're joking.

> The second sync
> cleans many of these.  Of course this is a classic race condition
> which might never get resolved, but the probabilities are
> much more favorable after the second sync than after only
> the first.

That's just silly.  The only thing that would make a second sync flush 
any more blocks than the first one is continued system activity, or in 
other words, "time."  Syncing a second time may flush additional blocks, 
but no more blocks than if you's simply skipped the first.