Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!arclight.uoregon.edu!news.bc.net!nntp.portal.ca!cynic.portal.ca!not-for-mail From: cjs@cynic.portal.ca (Curt Sampson) Newsgroups: comp.unix.solaris,comp.unix.bsd.misc,comp.unix.internals Subject: Re: Solaris 2.6 Date: 28 Nov 1996 14:17:47 -0800 Organization: Internet Portal Services, Inc. Lines: 28 Distribution: inet Message-ID: <57l32b$au4@cynic.portal.ca> References: <32986299.AC7@mail.esrin.esa.it> <schendel-ya023080002611961906140001@news.fyi.net> <57gbls$25s@cynic.portal.ca> <schendel-ya023080002711960508060001@news.fyi.net> NNTP-Posting-Host: cynic.portal.ca Xref: euryale.cc.adfa.oz.au comp.unix.solaris:90824 comp.unix.bsd.misc:1624 comp.unix.internals:11366 In article <schendel-ya023080002711960508060001@news.fyi.net>, Karl Schendel <schendel@fyi.net> wrote: >Once, no. If I thought it was an indication of permanent braindamage, yes. >Remember I'm not the end user. I would have to arrange for a new version >of Ingres (and probably of our application) N times, N = # of our Sun >customers. And schedule and coordinate the whole mess. You're going to have to do at some point for some of your customers anyway, since the current version of Ingres will not be able to deal with 64-bit off_t values. Any customer that wants to upgrade to 2.6 is going to have a scheduling and co-ordiation mess to deal with, since that's what an OS upgrade involves. Installing a new version of the database software at the same time is going to cause little in the way of extra problems in this procedure. And of course those that don't upgrade to 2.6 (because they don't need to or don't want to) continue to use the old version of Ingres. I just don't see where the huge problems come in. cjs -- Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Vancouver, BC (604) 257-9400 De gustibus, aut bene aut nihil.