AWalker@RED.RUTGERS.EDU.UUCP (06/08/87)
Be *real careful* about these -- Stabackit likes to do lots of set file/enter's which can really screw you when for some reason you don't want the STB root around anymore. Your best bet is to look at stabackit.com and rehack it your own preferred way; your private copy will probably be a lot smaller and faster, as well. _H* -------
carl@CITHEX.CALTECH.EDU.UUCP (06/08/87)
> Be *real careful* about these -- Stabackit likes to do lots of set > file/enter's which can really screw you when for some reason you don't want > the STB root around anymore. Your best bet is to look at stabackit.com and > rehack it your own preferred way; your private copy will probably be a lot > smaller and faster, as well. Stabackit does only ONE "SET FILE/ENTER" worth noting; to wit: it uses the command: $ SET FILE/ENTER=SYS$SYSDEVICE:[SYSE]SYSCOMMON.DIR SYSDEVICE:[000000]SYS0.DIR Now, this DOES mean that any file that you delete from [SYSE.SYSCOMMON...] will likewise disappear from [SYS0....], but it has the rather desirable effect of obviating the necessity of copying all your device drivers, shareable images, and so forth, from your system directories to the standalone backup directory. Stabackit copies only a handful of files into its own private directory, and these are things like the system parameter files, where standalone backup and your system want to use different parameter values. If you want to get rid of thestandalone backup kit, you need only set one file /remove, then delete about half a dozen files from the private directory. This as compared to having a second copy of half your operating system kernal sitting around on disk. Given this, any private copy of stabackit.com is likely to run slower than the one that DEC supplies, to result in more wasted disk space, and be liable to things like your forgetting to update the files in your standalone backup directory when you make changes (patches, for example) to files in your system directories.
tedcrane@batcomputer.tn.cornell.edu (Ted Crane) (06/09/87)
In article <12308746200.44.AWALKER@RED.RUTGERS.EDU> AWalker@RED.RUTGERS.EDU (*Hobbit*) writes: >Be *real careful* about these -- Stabackit likes to do lots of set file/enter's >which can really screw you when for some reason you don't want the STB root >around anymore. Your best bet is to look at stabackit.com and rehack it >your own preferred way; your private copy will probably be a lot smaller >and faster, as well. Just which SET FILE/ENTERs are you referring to? Sure, it sets up a SYSCOMMON pointer back to SYS0 or V4COMMON (depending on how your disk is set up), but that is necessary in order to avoid having to copy scads of blocks of drivers and stuff into SYSE! *FLAME ON* It would be very interesting to see how a private copy could be smaller. It would be even more interesting to see how it would be faster! If you are offering good advice, show it; don't just tell everyone to go and botch up their systems...especially when it may not be worth it! *F OFF*