[Info-vax] VMS Software Inc. OpenVMS 8.4-1H1 Boots on i4 System

[Bill Gunshannon]

In article <meplas$8sd$1 at panix2.panix.com>,
	kludge at panix.com (Scott Dorsey) writes:
> In article <ycIOZftUpcnL at eisner.encompasserve.org>,
> Bob Koehler <koehler at eisner.nospam.decuserve.org> wrote:
>>In article <memn33$5c0$1 at panix2.panix.com>, kludge at panix.com (Scott Dorsey) writes:
>>> 
>>> The nice thing about the Unix philosophy is that everything is broken up into
>>> tiny little pieces and all those pieces are interconnected... but each piece
>>> is small enough to be more or less debuggable.  This also allows the wise admin
>>> to remove stuff that isn't being used, because if it's not running it doesn't
>>> matter if it's buggy.
>>
>>   And then you load Orcale to organize your data because your file
>>   system can't.
>>
>>   I don't thinkUNIX has kept to your notion of small pieces since about
>>   1968.
> 
> I'd say somewhere around 2000 was the turning point, really.
> But thankfully most of the fundamental stuff predates that.

I would disagree.  With the exception of bloated applications like Open
Office, Unix still has all those small pieces that have always made up
the Software Tools Paradigm.  And some of us use them all the time.
My routine for adding new users takes a CSV extracted from the academic
database and using cut, paste, awk, sort and uniq to:
a) identify students for our courses
b) identify students who do not currently have accounts
c) create a file to be fed into the adduser command to create those accounts

Could this be done with a single, monolithic program?  Certainly. But why?

bill

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>