🚀 go-pugleaf

In article <62300007@hobbiton> choinski@hobbiton.prime.com writes:
> The reason I gripe about this [forced reboots] is because of the 
> immense start-up time involved to re-boot.
>Burton Choinski                                             Prime Computer Inc.

Well there are many ways to streamline the time it takes to reboot your
system, many can improve system booting performance 100 - 200 % ! Some
suggestions :
  o Make your boot floppy special - Format a new blank floppy (NOICONS) and
	then make (but don't copy) the following directories on to it :
		s, c, libs, devs, l. 
	Then copy startup-sequence, devs:system-configuration, c:assign, 
	c:stack, c:run, and any other commands in c: that you use in the 
	startup script. Then copy any handlers you mount (AUX, PIPE, etc)
	into the l: directory. Then copy the rest of c: the libs: directory
	and then devs: the rest of s: the rest of l: all of fonts, system
	etc. What this does is move all of the files that you access 
	intially to the same couple of cylinders. That cuts down the 
	grind, grind, grind considerably.

  o If you are using ARP compress your assigns by doing multiple assigns 
    at once :
	assign lc: sys:lc foo: mydir dpaint: :dpaint t: ram:t

  o If you have a hard disk do the minimum stuff you need to on the floppy
    and then transfer control to the hard disk startup sequence. Similarly
    if you have a recoverable ram disk and you know it has recovered 
    successfully.

  o If you are using a shell that allows resident commands such as MetaCompCo's
    or have Jim Goodnow's REZ command, then make frequently used commands 
    resident such as assign, path, if.

Doing these things will really make a difference in reboot time.

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.