home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!rpi!batcomputer!cornell!rochester!galileo.cc.rochester.edu!ub!dsinc!cdin-1!icdi10!fr
- From: fr@compu.com (Fred Rump from home)
- Newsgroups: comp.unix.sysv386
- Subject: Re: How to replace disk driver in SCO Unix ?
- Message-ID: <1992Aug25.155710.12001@compu.com>
- Date: 25 Aug 92 15:57:10 GMT
- References: <JOCHEN.92Aug19074730@mrz.sub.org> <1992Aug22.152138.2272@compu.com> <1853@adagio.UUCP>
- Organization: CompuData Inc.
- Lines: 29
-
- grog@adagio.UUCP (Greg Lehey) writes:
-
- >In this case, I believe it's reasonable
- >to expect that the distributor should not even understand the problem,
- >let alone fix it. But he should escalate it to SCO, and they should
- >find a fix - if for nothing else, then to improve the reputation of
- >their product.
-
- Yes, I agree.
-
- >I don't think that Jochen was looking for an educator. If I buy
- >software which is claimed to conform to ANSI C (but not to be fit for
- >any purpose :-), I would expect the vendor to be interested in obvious
- >bugs, especially if they cause me hardship.
-
- I meant that in general. It should not be like: "This statement doesn't work
- for me. Why?" But rather: "This is bug. Here is an example of the code. Fix
- it!" All the distributor should do is pass it up the line or provide a direct
- contact with more knowledgeable sources.
-
- >*sigh* you could be right. But he could install gcc instead.
-
- Yes, it would seem to be the one solution that does the trick. That gcc
- without real development resources can make something that works according to
- the specs and huge Madam Microsoft or small Ms SCO can not, is a bit beyond my
- comprehension. There must be other itineraries lurking in the background that
- we know nothing about.
-
- Fred
- --
- W. Fred Rump office: fred@COMPU.COM 'mans feet have grown/so big
- 26 Warren St. home: fred@icdi10.compu.com that he/forgets his littleness'
- Beverly, NJ. 08010 Don Marquis
- 609-386-6846 bang:uunet!cdin-1!icdi10!fr
-