[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #JRK-547142]: install mcidas2009 in a SUN Solaris10x86_64 machine

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [McIDAS #JRK-547142]: install mcidas2009 in a SUN Solaris10x86_64 machine
  • Date: Tue, 22 Sep 2009 18:46:18 -0600
Hi Hsie,

re: link to solaris2009

> It was linked to solaris2009 when I built it.  Because the build was
> failed, so I change the link back to solaris2007.

OK, now I understand.

> My scheme is very
> similar (almost the same as yours listed below).  The only difference is
> my "McINST_ROOT" point to "/home/mcidas/solaris2009" and my "MCHOME" is
> pointed to the same directory instead of "/home/mcidas".

Yes, exactly.

> Two questions here:
> 
> (1) Do I need reinitiate the MySQL database?

You shouldn't.

> (2) Because the new /home/mcidas/solaris2009/workdata is a new
> directory, all the files in that directory are new files.  I think I can
> rerun "mcxconfig" to reconfigure everything?

Yes, you should be able to.

Here is another idea that you might want to consider for the future:

- since you end up with a new workdata directory each time you install
  a new McIDAS distribution, you might want to create a permanent
  working directory in which the files that get created by configurations
  (e.g., RESOLV.SRV for ADDE dataset definitions) and decoder output
  (e.g., *.ERR files; COUNTRY.DAT, etc.) and then adjust your MCPATH
  to include that new directory first; the /home/mcidas/solaris/workdata
  directory second; the /home/mcidas/solaris/data directory third; and
  the /home/mcidas/solaris/help directory last.

  By creating such a directory, the configuration files will never get
  overwritten with new installations.  This is how I have the
  McIDAS installation on motherlode.ucar.edu setup.



Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: JRK-547142
Department: Support McIDAS
Priority: Normal
Status: Closed