Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Rollback, Runback, Sideshow, fixobj, ATV3d, amyload, mwb
Message-ID: <44049@sun.uucp>
Date: 3 Mar 88 18:40:28 GMT
References: <8960@sunybcs.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 22

In article <8960@sunybcs.UUCP> ugpete@sunybcs.UUCP (Peter Theobald) writes:
>And does anyone know the difference between 'fixobj' that is 6912 bytes long,
>and 'fixobj' that is 16376 bytes long?

I suspect one was compiled with Lattice and the other Manx, in the early
stages that would result in these size differences.

>I gather that runback runs programs in the background; How does this differ
>from just 'run'ing a program?

The difference is that Runback allocates a filehandle the points to the
bitbucket (NIL:) and passes them as StdIn and StdOut. The regular Run
command will pass locks on the current CLI window. The advantage comes
when you exit the CLI with EndCLI. If there are outstanding locks on the
CLI window, the window will not close. RunBack alleviates this allowing 
you to end the CLI before the programs you have "run" from it exit.

Also note that this is where those mysterious 40 bytes go, there are
two locks on NIL: that get created and never freed.

--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.