Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!bcstec!misty!jsadler
From: jsadler@misty.boeing.com (Jim Sadler)
Newsgroups: comp.sys.hp
Subject: Re: HP-UX features
Message-ID: <1150071@misty.boeing.com>
Date: 3 Jun 91 21:20:21 GMT
Article-I.D.: misty.1150071
References: <1991May24.152621.9993@msuinfo.cl.msu.edu>
Organization: Boeing Commercial Airplane BCS Support
Lines: 35

/ misty:comp.sys.hp / okamoto@hpcc01.HP.COM (Jeff Okamoto) / 11:04 am  May 31, 1991 /
petersor@egr.msu.edu (Rick Peterson) writes:

.
.
.
Much deleted.

>>	Second, since HP software comes in update format it is impossible
>>	to do anything at all different from the standard install.

>Your point is valid, but what did you have in mind, doing something different?

How about allowing installs across multiple drives ?


>In the case of ar(1), this is necessary to maintain SVID compliance.

What about a flag if SVID doesn't allow a command to be a superset.

>Why would HP want me as a spokesman?
>-- 
> \      oo	The New Number Who,
>  \____|\mm	Jeff Okamoto
>  //_//\ \_\	HP Corporate Computing & Services
> /K-9/  \/_/	okamoto@ranma.corp.hp.com
>/___/_____\	
>-----------	(415) 857-6236

jim sadler
206-234-9009	email	uunet!bcstec!jsadler | jsadler@misty.boeing.com

This service is brought to you by the computing mafia of Boeing (BCS).
Oh ya
None of the above is an opinion of The Boeing Co.