Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!stc!stl!robobar!ronald From: ronald@robobar.co.uk (Ronald S H Khoo) Newsgroups: comp.unix.sysv386 Subject: Re: Summary: What's wrong with SCO (long) Message-ID: <1991Apr19.124711.829@robobar.co.uk> Date: 19 Apr 91 12:47:11 GMT References: <1991Apr16.183342.10185@compu.com> <1991Apr17.210627.4517@beaver.cs.washington.edu> <1991Apr18.063914.13111@kithrup.COM> Organization: Robobar Ltd., Perivale, Middx., ENGLAND. Lines: 25 sef@kithrup.COM (Sean Eric Fagan) writes: > It can. Try looking at SLS's; the information was posted here. And no other vendor makes their fixes so readily available. FTP, UUCP, pick your transport. Even a local London number too :-) > The csh is *old*. And, yeah, it's broken. I've ported tcsh, as have > others. No real problem. Tell people at SCO you want it, and, if they get > enough requests, they will make it available. But can you imagine the customer telling the front line folks "Well, yeah, one of your ex-employees says he ported it ... " :-) > >The startup file problem ("xxx: > >cannot execute") is ridiculous, > Never seen that. xxx is setgid and luid wasn't set. SecureWare strikes. No need to rehash the old stories about that one, surely? :-) [ ObFix: su root -c xxx instead of naked xxx. ] -- Ronald Khoo +44 81 991 1142 (O) +44 71 229 7741 (H)