Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: pyramid!daver!mfgfoc!exodus@decwrl.dec.com (Greg Onufer)
Newsgroups: comp.sys.sun
Subject: Re: Shutting down a Sun System with a Shell Script
Message-ID: <512@mfgfoc.uucp>
Date: 20 Dec 88 00:17:01 GMT
References: <8514@elsie.UUCP>
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
Original-Date: 9 Dec 88 21:00:18 GMT
X-Sun-Spots-Digest: Volume 7, Issue 62, message 5 of 12

elsie!ado@ncifcrf.gov (Arthur David Olson):
> STELLABO@CSHLAB.BITNET writes: 
> No.  A quick look reveals that. . .
>   Script started on Wed Nov 23 17: 19:42 1988
>   elsie$ /bin/ls -l /etc/umount /etc/dump
>   lrwxrwxrwx  1 root           15 Oct 11 15: 40 /etc/dump -> ../usr/etc/dump
>   lrwxrwxrwx  1 root           17 Oct 11 15: 40 /etc/umount -> ../usr/etc/umount
> To make things work right, Sun would at least get to move dump and umount
> to /sbin.

You are completely off-base on this one.  You must be running SunOS 4.0.
In SunOS 4.0 /usr is mounted read-only.  So why bother going to single-
user??  No one can change /usr (although some do... but that's just a sad
story), so back it up whenever you want.  But since all of us are not
running SunOS 4.0, let me just say that I have never had a problem with
full dumps done on active file systems.

-greg
-- 
Greg Onufer   //  Focus Semiconductor  //     University of the Pacific
  exodus@cheers.uucp (daver!cheers!exodus@Sun.COM) 	415-965-0604