Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!apple!snorkelwacker!bloom-beacon!eru!hagbard!sunic!mcsun!tuvie!mike From: mike@tuvie (Inst.f.Techn.Informatik) Newsgroups: comp.sys.apollo Subject: Re: How to modify the "kernel'? Message-ID: <1801@tuvie> Date: 9 Sep 90 11:44:55 GMT References: <6881.26e59640@jetson.uh.edu> <25786@boulder.Colorado.EDU> Organization: Technical University of Vienna, AUSTRIA Lines: 38 In article , asherman@dino.ulowell.edu (Aaron Sherman) writes: > The problem here is that Domain/OS is NOT Unix, and the more HP/Apollo > tries to make it Unix the more people will get frustrated. Remember that > for YEARS Unix was not "standard". > > Standards. Bah! Standards brought us MSDOS. Standards brought us MOTIF. > I much prefer the old Apollo attitude. You want BSD, have it. You want > SystemV, have it. Heck, you can make Apollos act like a PC. You can have > DDS, TCP/IP or DECNet. You can use X, the DM, even MS-Windows if you're sick. > Since the HP-takeover though, people like this poster have been having > more of a voice in the direction Apollo's taking, and I fear the day > an Apollo is just as much a toy as the next machine. There are great things in DomainOS (you forgot to mention my favorite, the //netdirectory :-), BUT there are annoying things in DomainOS as well, like: * HPollo makes your life miserable, if you need rpc. Ok, NCS is better, but I never managed to get the pcnfsd to compile with NCS :-) * If you need to raise the number of process slots, you're out of luck! * If you complain about a bug in DM, you're told it's not worth fixing as the DM is going to die soon, anyway. * If you have problems with buggy include files, you are told "Wait for OSF/1" * The file-locking semantics of open can drive you mad. * Programs which work on any other computer break on Apollos. bye, mike ____ ____ / / / / / Michael K. Gschwind mike@vlsivie.at / / / / / Technical University, Vienna mike@vlsivie.uucp ---/ Voice: (++43).1.58801 8144 e182202@awituw01.bitnet / Fax: (++43).1.569697 ___/