CAP on Tru64 5.1B

From: Matt McLeod (matt_at_boggle.org)
Date: 03/02/04

  • Next message: Bev A. Kupf: "Re: CAP on Tru64 5.1B" 
    Date: Tue, 2 Mar 2004 02:25:36 +0000 (UTC)

    [cross-posting as I'm not sure which of these groups is more
     likely to come up with an answer.]

    I realise this qualifies as "bloody ridiculous", but I have a need
    to get CAP running on a Tru64 5.1B box. We're migrating stuff from
    older machines running 4.0 to newer ones running 5.1B, there's a lot
    of legacy crap involved, and CAP is part of it.

    I can get it to build without any great trouble, but when I try to
    start up aarpd (we're using native EtherTalk, as best I can tell --
    some clown deleted our old CAP source tree, and nobody bothered to
    document this stuff back when it was first set up) I get:

    # ./aarpd bcm1 unimelb-UCS
    open: bcm1: No such file or directory
    13:13:52 03/02/2004 pi_open: aarp_init: No such file or directory
    init_enet: network initialization failed

    bcm1 is the ethernet device on this machine, and that's the correct
    zone, so I'm not sure why it's unable to open the device. The
    same command run on a 4.0 machine (substituting the ethernet device,
    of course) works properly, so either it's something to do with the
    ethernet device itself or with 5.1B.

    (I tried using our old binaries, same result, so I don't think it's
     a case of misconfiguring CAP itself. This is CAP 6.0 with all
     the patches applied.)

    Any ideas? Apart from "shoot yourself before the pain gets any worse"?

    Matt 

    -- 
                Never count your chickens before they rip your lips off
  • Next message: Bev A. Kupf: "Re: CAP on Tru64 5.1B"