Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!aplcen!haven!mimsy!mojo!stripes From: stripes@eng.umd.edu (Joshua Osborne) Newsgroups: comp.windows.x Subject: Re: R3 -> R4 - pitfalls for applications built under R3 on Suns ?? Message-ID: <1990Feb20.022912.24541@eng.umd.edu> Date: 20 Feb 90 02:29:12 GMT References: <9002192121.AA01803@expire.lcs.mit.edu> Sender: news@eng.umd.edu (The News System) Organization: Maryversity of Uniland, College Park Lines: 18 In article <9002192121.AA01803@expire.lcs.mit.edu> rws@EXPO.LCS.MIT.EDU (Bob Scheifler) writes: >You should certainly keep your R3 binaries around for a while, they should >work fine against an R4 server (although for some you may have to enable >"bug compatibility" mode in the server). The R3->R4 transition is not an >"all or nothing" situation, you can move gradually. Yes, the R3 clients do seem to work nicely with the R4 server, but I want to use MIT-COOKIE-1, not xhost. No can do with R3 clients. (that's why I switched from dxmail to xmh...) Besides we don't have unlimited space and the R4 clients compiled with shared libs are tiny vs. the R3 clients... Face up to it, you did too good of a job on R4, I want to get all the R3 stuff takeing advantage of all that work... -- stripes@wam.umd.edu "Security for Unix is like Josh_Osborne@Real_World,The Mutitasking for MS-DOS" "The dyslexic porgramer" - Kevin Lockwood Who needs friends when you can sit alone in your room and drink?