Re: SCO Office Server et. al.

From: Bill Vermillion (bv_at_wjv.com)
Date: 09/24/05

  • Next message: Bela Lubkin: "Re: cpio files to remote server"
    Date: Sat, 24 Sep 2005 19:55:01 GMT
    
    

    In article <UChZe.523$yl.479@bignews1.bellsouth.net>,
    Boss <ken@keysey.net> wrote:
    >Smashcat wrote:
    >
    >> Robin Grayson wrote:
    >>

    >>>I've got mixed feelings about pushing SCO .. part of me thinks why
    >>>bother, is it worth the effort, nobody seems that interested in it
    >>>anymore, but then the other part of me has an overwhelming urge to
    >>>jump on the "SCO Revival" bandwagon.
    >>
    >>
    >> Talk about flogging a dead horse! I'm amazed that anyone is still
    >> actually bothering to update any software on SCO OS'.
    >>
    >> If you really are "pushing SCO" onto customers, you should be bloodywell
    >> ashamed of yourself...
    >

    >Mr. Smachcat. Try to see the real picture vs. the one you might read
    >about in PC mags.

    >I am a Computer consultant and have been working with SCO
    >products since Xenix came on 8" disks. I have running my own
    >integration company since 1992 (worked with my father's Computer
    >company for years before that). We work mostly with small
    >business.

    >The real picture is compatibility and stability. These are the two
    >words to success in the OS biz. SCO OSs have such a large installed
    >base. Over the years, they have created a big wave of momentum.

    >Many of these installs are running custom code that has been in use for
    >many years. Unfortunately, hardware does not have the longevity of
    >software. Clients need their servers upgraded every 5 years or so.
    >They don't "want" to do it. They have to. When they do, they don't
    >"want" to spend anymore than is necessary to just keep the status quo.
    >"Just get me running." they tell me.

    And they keep on running.

    I thought I had a client who migrated from OSR5. I migrated
    to an OSR5 for the Y2K event, as their vendor was working on
    getting things running on NT.

    Then I was there in 2002, as the upgrade was 'almost ready'.

    I figured I had seen the last of them.

    About 18 months ago they moved their office and called me when
    their modems weren't working. [They hadn't labeled things correctly
    and had things set up wrong]. The upgrade was almost ready.
    And that left me with 1 OSR5 client, who has since moved to SuSE.

    And three days ago I got a call from the first client.

    They needed to get their XP machines up and running with Samba
    as they only had 2 Windows 98 accessing it and those were dog slow.

    I asked about the update. It seems the data conversion house
    can't seem to get it 'right' as they have two pharmacies that run
    in that company. And the data conversion firm can't seem to get
    these into separate data bases. :-(

    I wondered why, and asked if it was to be an SQL application and
    the vendor told them 'they didn't need that until they get bigger'
    - which I think was a way of saying "we don't know how to do that".

    But I put in some security patches, put in an updated Samba.

    And the client commented he almost hated to have people see his
    computer room as the SCO machine is so old - and the previous
    on-site computer person had broken the clips for the front cover
    so it's guts are visible.

    But he said "It just keeps on running". And he's gone through at
    least 2 NT server since the Y2K upgrade on the OSR5.

    The systems just don't go away. However, after the last three
    times I've been there in the past 4 years thinking it was the last
    time I'd see them, I'm beginning to wonder.

    Bill

    -- 
    Bill Vermillion - bv @ wjv . com
    

  • Next message: Bela Lubkin: "Re: cpio files to remote server"

    Relevant Pages

    • Re: What so special about PostgreSQL and other RDBMS?
      ... > There are circumstances under which my client is better protected against ... > to a different database management system is made very easy. ... > database of the type Quirk describes. ... > decides not to upgrade, the vendor has effectively broken the code for the ...
      (comp.lang.php)
    • RE: Upgrading SMS 2.0 SP5 to SMS 2003 SP2
      ... multiple newsgroups. ... advanced client is different with the previous upgrading process. ... be used to control the client upgrade behavior in your site. ... upgrade automatically from SMS 2.0 to SMS 2003. ...
      (microsoft.public.sms.setup)
    • RE: Since 2003 SP3 upgrade hardware inventory no longer reports me
      ... SMS 2003 SP3 client. ... I did not knowingly restore anything; I did however upgrade from SP1 ...
      (microsoft.public.sms.inventory)
    • RE: Upgrading SMS 2.0 SP5 to SMS 2003 SP2
      ... advanced client is different with the previous upgrading process. ... be used to control the client upgrade behavior in your site. ... upgrade automatically from SMS 2.0 to SMS 2003. ... newer version of the Advanced Client software is available at the SMS site. ...
      (microsoft.public.sms.admin)
    • Re: dhcp issue
      ... > I just upgrade to FC5 before then I had 2 NIC in one with static IP ... My first thought is that your DHCP client is not looking at the eth1 ... Now lets find the leases: ...
      (Fedora)