[Coco] batch file processing

[Bob Devries]

Ah, I may have misunderstood your requirements somewhat.

Hmm,  there's a utility provided with OS-9/68000 which I think is called CFP 
which takes a command template with wilcards, and then fills in the 
wildcards from a piped input.

something like this IIRC:

ls ! CFP -z "cmp /d0/* /d1/*"

I don't know with any certainty if there's a similar utility for OS-9/6809, 
however.

Regards, Bob Devries
Soldier's Hills 2
Las Pinas City
Philippines

--
Besides a mathematical inclination, an exceptionally good mastery of one's 
native tongue is the most vital asset of a competent programmer.

Edsger W.Dijkstra, 18 June 1975

----- Original Message ----- 
From: "Wayne Campbell" <asa.rand at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, February 07, 2010 4:31 PM
Subject: Re: [Coco] batch file processing


>I did create 2 files from the ls output. I modified them to remove the 
>unique files on diskb and the directory references to CMDS and SYS in both 
>files. I also added the pathlist to each entry, so each can be treated as a 
>separate input path. Now all I have to do is figure out how to tell cmp to 
>run recursively, taking each entry of each file as it's input parameters.
>
> If I just type cmp diskalst diskblst, it only compares the contents of the 
> 2 files. I need something like cmp <diskalst <diskblst, but it won't 
> accept a redirection modifier as part of the parameter list. I'm not sure 
> what to do now, but I'm going to keep trying.
>
> I don't have Diff, and haven't found it anywhere, yet.
>
> Wayne
>
> ----- Original Message ----- 
> From: "Bob Devries" <devries.bob at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Saturday, February 06, 2010 9:08 PM
> Subject: Re: [Coco] batch file processing
>
>
>> Hi Wayne,
>>
>> Given you can produce two text files, one for each disk, it seems to me 
>> that you could use DIFF to show you the differences. Diff is not a usual 
>> OS-9 utility, but should be available one one of our FTP sites.
>>
>> I did a quick search of RTSI, but didn't spot it. If someone knows where 
>> it is residing, please speak up.
>>
>> Regards, Bob Devries
>>
>> --
>> Besides a mathematical inclination, an exceptionally good mastery of 
>> one's native tongue is the most vital asset of a competent programmer.
>>
>> Edsger W.Dijkstra, 18 June 1975
>>
>> ----- Original Message ----- 
>> From: "Wayne Campbell" <asa.rand at gmail.com>
>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>> Sent: Sunday, February 07, 2010 3:49 PM
>> Subject: [Coco] batch file processing
>>
>>
>>> The easiest way I know to ask this is to just say what I want to do. The 
>>> OS-9 L2 manual does not cover anything like this, so I don't know if the 
>>> shell allows for it.
>>>
>>> I want to use the following as input to cmp:
>>>
>>> ls -rienac diska
>>> ls -rienac diskb
>>>
>>> This causes ls to produce a listing that contains one item per line. I 
>>> still have to figure out how to tell the script to skip the directory 
>>> entries in the listing, and only process what occurs within the 
>>> directory.
>>>
>>> diska and diskb are copies of the contents of different disks that are 
>>> similar (os9L2_1.os9 and OS9SYSMR.os9). The idea is I want to compare 
>>> every file that occurs on both disks to see which ones may be different. 
>>> Since I can boot both disks, and because both are almost identical, 
>>> there has to be a reason why OS9SYSMR.os9 boots to a black screen (fore, 
>>> back and border). I think I should be able to find something different 
>>> between them, other than the files that exist on one, but not the other.
>>>
>>> I was hoping I could do something like (not in these words) "using input 
>>> from ls/diska and ls/diskb, compare each file that occurs on both disks 
>>> and state the results". By redirecting final output to a file, I can 
>>> then find any and all differences between the disks. I'm not sure what 
>>> version of shell I'm running. The ident of the module being loaded in 
>>> startup (shell) is a merged module file. The shell ident itself shows a 
>>> size of $1B42 #6978. The shell_21 file in the CMDS shows an ident of 
>>> $0602 #1538, so it isn't the same shell.
>>>
>>> Anyone have ideas?
>>>
>>> Wayne
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco