Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!husc6!uwvax!oddjob!gargoyle!att!whuts!homxb!homxc!dwc From: dwc@homxc.UUCP (Malaclypse the Elder) Newsgroups: comp.unix.wizards Subject: Re: att & osf Message-ID: <3125@homxc.UUCP> Date: 19 Aug 88 03:58:42 GMT Article-I.D.: homxc.3125 References: <4964@killer.DALLAS.TX.US> <3395@vpk4.UUCP> <1988Aug16.214307.20597@utzoo.uucp> Organization: Legion of Dynamic Discord Lines: 28 In article <1988Aug16.214307.20597@utzoo.uucp>, henry@utzoo.uucp (Henry Spencer) writes: > Even there, one should note that the original work to make the system > portable was largely done by the Bell Labs research people; AT&T has > since basically done diddly-squat about improving portability, since the > remaining portability problems didn't affect *them*. (They've done a > little bit of work on portability, but they've also introduced some new > and gratuitous portability problems of their own, so the overall balance > is roughly zero.) i think this is too general a statement and needs clarification. the biggest step in making the system portable was the implementation of the system in 'c'. whether you wish to view this as 'the original work to make the system portable' is a subjective opinion. i believe that the System V developers have done a great job in making the kernel more portable. of course, my opinion doesn't really count and neither does anyone who doesn't do kernel ports. any real live kernel port people out there who have an opinion? (we know that the time required to do ports is getting shorter and shorter but that may be due to increased experience). i would also like to add that i believe henry is again confusing kernel portability with application portability. i would like to know of any specific kernel portability problems that the System V developers have 'gratuitously' added. danny chen att!homxc!dwc