The idea being to use Sun's (unix's?) "script"-cmd to keep a record of
what rolls-off the top of the (single-user-mode) screen when
doing a multi-hour set of level-0 ufsdumps, one per
partition on the machine.
Now, I suppose doing this wouldn't be safe to have the script-log
living (and growing) on a partitfion that is *not* the one
*currently* being ufsdumped.
(Otherwise that partition's ufsdump would be, uh, worthless?
So, I'd have to make sure to have at least *two* partitions
mounted, root and, say, "partition-b" -- which I'd arrange to
get ufsdumped *last*.
Then, until it was time to ufsdump partition-b, I could
do all the others under, say, a single
, and when those n-1 partitions had been ufsdumped, exit
that script-job, and start another:
this time leaving partition-b "quiescent" for *its* ufsdump.
When *that's* done, I cat together the two .log-files,
and I have a record of the whole thing.
QUESTION-1: does this scheme make any sense?
QUESTION-2: would it be similarly safe(?) to run the ufsdumps
via an EMACS *shell*-window, being sure, *before* starting
up EMACS, to:
Being in single-user mode and thus without CDE or X-11, i'd be running emacs'
via its "--no-windows" option.
(oops: just now tried to test runing emacs like that,
right now, when cde *is* up -- emacs comes up uses fonts,
colors, etc, *anyway*! I used -nw, and then added, as a
WAG, "-t /dev/cua" too.
So, how *do* you invoke emacs so that it thinks it's
back in pre-Sun days, running on a glass-tty?)
----- And something apparently "off the wall": tempfs
(Oh, I suppose I *could* use tmpfs to keep the growing log,
since if that works as advertised, it touches NO diskk.
But -- I dimly reacll some recent warning, on this newsgroup,
tot NOT use tempfs while ufsdumping -- although I forget the