Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!seismo!uunet!spool.mu.edu!samsung!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.advocacy Subject: Re: Script bits Message-ID: <1991Feb14.173729.7182@sugar.hackercorp.com> Date: 14 Feb 91 17:37:29 GMT References: <18ac1a05.ARN2ae4@prolix.pub.uu.oz.au> <1991Feb13.013917.22130@sugar.hackercorp.com> <11221.tnews@templar.actrix.gen.nz> Organization: Sugar Land Unix -- Houston, TX Lines: 15 In article <11221.tnews@templar.actrix.gen.nz> jbickers@templar.actrix.gen.nz (John Bickers) writes: > Count up how many accesses are required on the file to determine > whether it's a script, using either method. One. Remember, in FFS the first block of the file tends to be contiguous with the header, and for a floppy (the only place this makes a difference) the whole track gets loaded in a unit so the first block is right there. With OFS you'd have a single extra access, but since you presumably need to load the script in to memory to run it that access would be made in any case, whether it's a script or not. All you're doing is preloading the disk's buffer pool. -- Peter da Silva. `-_-' .