News Group Posts

conflict with scodb and Olympus

Tuneup

Olympus Tuneup conflicting with scodb

From: Bela Lubkin <belal@sco.com>
Subject: Re: Merge Installation/Configuration Problem on OpenServer 5.0.7
Date: Tue, 12 Aug 2003 07:57:13 GMT
References: <20030811222423.GD24551@sco.com>
<20030811223558.18739.00001189@mb-m18.aol.com> 

Transpower wrote:

> >I changed the line in scodb to 'Y' and attempted to re-link but got several
> >> symbol table errors relating to scodb!  
> 
> Here are the errors, verbatim:
> 
> Root for this system build is /
> i386ld: Symbol usage in /etc/conf/pack.d/drt/Driver.o
> is multiply defined. First defined in /etc/conf/pack.d/scodb/Driver.o
> i386ld: Symbol umode in /etc/conf/pack.d/drt/Driver.o
> is multiply defined. First defined in /etc/conf/pack.d/scodb/Driver.o
> i386ld: Symbol offset in /etc/conf/pack.d/drt/Driver.o
> is multiply defined. First defined in /etc/conf/pack.d/scodb/Driver.o
> ERROR: Can not link-edit unix
> 
> idbuild: idmkunix had errors.
> System build failed.

[de-butchered from what your mailer did; also removed useless SSO path
elements]

scodb is conflicting with the device driver "drt", which I don't
recognize.  What is it, where does it come from?

... A bit of web searching suggests it comes from Pacific CodeWorks'
Olympus TuneUp.  For the moment you will have to turn off TuneUp in
order to be able to use scodb.  (In truth, both drivers are faulty for
exposing symbol names that they have no business trying to own.)

> Back to the serial/modem ports for a moment:
> what operating system files directly relate to these ports?  Perhaps we could
> just remove and reinstall those files from the CD--what do you think?  I tried
> removing and reinstalling the serial/modem manager but that didn't help--"cu -l
> tty2a dir" panicked the system, as before.  

Removing and reinstalling packages isn't going to fix this.  It's an
interaction between Merge and serial port access.  If you remove Merge
it will definitely "fix" the problem, but you don't want to remove
Merge, so that's not really a solution.

Merge + OSR507 does not prevent serial port access on other systems, so
there's some other factor here that we have to dig up.

> By the way, I don't mind taking the time to troubleshoot these issues; we all
> become better systems engineers as a result.  The in-place install allowed me
> to have access to my accounting/database files within an hour and a half, which
> is much more quickly than a fresh install would have.

We may reach a dead end on this one.  You don't have kernel source, I
don't have easy access to Merge source, and we're well outside your
skill set for debugging it on site.

>Bela<

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.