Solaris 8 binary compatibility - Solaris 7

Greetings:
and TIA.
Also apologies if this issue has been covered via some other resource.
Note: Hardware Utilized - Sparc
We have recently ported our 4.2 Forte C++/C code successfully from Solaris 6 to Solaris 8. As part of that port, we upgraded the compiler resources from 4.2 to 6.0. With these new binaries we have encountered the following runtime issue:
Solaris 8 code runs fine on Solaris 8, however these same executables dump core on Solaris 7
To troubleshoot this, we built the same code on a Solaris 7 platform. These executables ran fine on both Solaris 7 and Solaris 8
My question: Are Solaris 8 binaries incompatible with Solaris 7? Is there any online documentations which provides an overview/explanation for this behavior?
Regards:

In general there is forward compatibility for applications between Solaris releases. There is no official backward compatibility. This means you
should always compile on the oldest release of
Solaris that you expectto run on. So, if you need
to run on Solaris 5.6, 7 and 8, compile on Solaris 5.6.
There is a tool called appcert which is shipped with
later versions of Solaris 8 and can be downloaded from:
http://www.sun.com/developers/tools/appcert/download.html
That will give you a good idea of the forward and backward compatibility of your application. General ABI information can be found at:
http://www.sun.com/developers/tools/abi/index.html
Alan
Sun Developer Technical Support
http://www.sun.com/developers/support

Similar Messages

Is it possible to build a binary working on solaris 8 from solaris 10

Hi
I understand that my requirement is kinda weird. However, I really wonder whether it is possible sometimes.
I have built ssh successfully both on solaris 8 and solaris 10. Now the problem is the binary built on solaris 8 can work on solaris 10, but the binary built on solaris 10 can not work on solaris 8.
The problem is SUNW_1.2.2 can not be found on solaris 8.
$ldd sshd
        libresolv.so.2 =>        /usr/lib/libresolv.so.2
        librt.so.1 =>    /usr/lib/librt.so.1
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libc.so.1 (SUNW_1.22) =>         (version not found)
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libaio.so.1 =>   /usr/lib/libaio.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2
        /usr/platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1After more detailed investigation, I found the system-call dlopen and so on are linked to SUNW_1.2.2
objdump -T sshd|grep SUNW_1.22
00251240      DF *UND* 00000000 SUNW_1.22   dlerror
00251510      DF *UND* 00000000 SUNW_1.22   dlclose
00251738      DF *UND* 00000000 SUNW_1.22   dlopen
0025181c      DF *UND* 00000000 SUNW_1.22   dlsym
00251a98      DF *UND* 00000100 SUNW_1.22   unsetenvBut for the binary built on solaris 8, system-call dlopen is provided by SISCD_2.3.
objdump -T sshd|grep dl
0023f160      DF *UND* 00000008 SISCD_2.3   dlopen
0023f16c      DF *UND* 00000008 SISCD_2.3   dlclose
0023f274      DF *UND* 00000008 SISCD_2.3   dlerror
0023f8d4      DF *UND* 00000008 SISCD_2.3   dlsymAs sshd from solaris 8 is working on solaris 10, I think SISCD2.3 is also available on Solaris10. So is it possible to build ssh (any special link option?) with SISCD_2.3 rather than SUNW_1.2.2?

Yuechen wrote:
Hi
I understand that my requirement is kinda weird. However, I really wonder whether it is possible sometimes.
I have built ssh successfully both on solaris 8 and solaris 10. Now the problem is the binary built on solaris 8 can work on solaris 10, but the binary built on solaris 10 can not work on solaris 8.That is expected. Binaries should have forward compatibility and run on later versions of the OS.
Build on 8, run on 8 through 10.
Darren

Backward Compatability solaris 10 to Solaris 9

I am trying to mix
executables compiled on Solaris 10 with C++ compiler 5.8
with shared libraries compiled on Solaris 9.
On solaris 9 it says libm.so.2 file not found.
what may be the solution to run the executable from solaris 10 to solaris 9

Running binaries built in Solaris 10 platform, on Solaris 9 or earlier versions, is not "backward" compatibility. It is the other way round ie., running executables built on earlier versions of Solaris, on Solaris 10.
I believe libm.so.2 was introduced in Solaris 10; and is not available for Solaris 9. If you want to run your executable on both 9 & 10, you have to build it on Solaris 9, but definitely not on 10.

Missing package: SUNWbcp (SunOS 4.x Binary Compatibility)

I have downloaded the latest Free Solaris 10 8/07 for x86 and retrieve the following error message:
Missing package: SUNWbcp (SunOS 4.x Binary Compatibility)
when installing Business Objects Enterprise XI Release 2 Service Pack 2. I can't locate the package on neither the CDs nor the DVD I downloaded.
Any advise would be highly appreciated.
Many thanks.
Jurgs
Edited by: tzscl2 on Dec 12, 2007 12:52 AM

I have downloaded the latest Free Solaris 10 8/07 for x86 and retrieve the following error message:
Missing package: SUNWbcp (SunOS 4.x Binary Compatibility)
when installing Business Objects Enterprise XI Release 2 Service Pack 2. I can't locate the package on neither the CDs nor the DVD I downloaded.
Any advise would be highly appreciated.
Many thanks.
Jurgs
Edited by: tzscl2 on Dec 12, 2007 12:52 AM

Migration from Sun solaris 8 to Solaris 10

Hi,
We are migrating from Solaris 8 to Solaris 10 with the compiler migration also earlier we are using Sun Studio 6 and now it is Sun Studio 11.
When we are compiling the code on Solaris 10 which has been running on the Solaris 8, we are facing some error. So could you help me on this
"ResourceManager.h", line 98: Warning (Anachronism): Type names qualified by template parameters require "typename".
"ConnectionMgr.h", line 62: Where: While specializing "ResourceManager<T>".
"ConnectionMgr.h", line 62: Where: Specialized in non-template code.
"ResourceManager.h", line 100: Warning (Anachronism): Type names qualified by template parameters require "typename".
"ConnectionMgr.h", line 62: Where: While specializing "ResourceManager<T>".
"ConnectionMgr.h", line 62: Where: Specialized in non-template code.
2 Warning(s) detected.
make[1]: *** [obj/ConnectionMgr.o] Error 2
Not sure of the warning , am not able to see these error on the compilation on Sun Studio 6.Below is the bit of the header file code, where the error is occurring.
98 typedef map<ResourceID, ResElement *>::iterator ResMapIterator;
100 typedef list<ResElement *>::iterator ResListIterator;
We are using a /opt/SUNWspro/bin/CC compiler and the verison is CC: Sun C++ 5.8
Please help me out about the issue

Since you are jumping several compiler releases and two Solaris releases, you should migrate in two steps.
1. Get your application working with Sun Studio 11 on Solaris 8.
2. You can now run that application on Solaris 10, or you can rebuild it on Solaris 10 and then run it.
An application built on Solaris 8 will run on Solaris 9 and 10.
An application built on Solaris 10 cannot be run on Solaris 8 or 9.
We promise upward binary compatibility, allowing an old binary to be used with a newer compiler or on a newer Solaris. But we can't promise source code compatibility because we don't want to have to duplicate old bugs in old compilers.
C++ 5.8 in Sun Studio 11 detects errors that older compilers might have missed. The rules about where to use "typename" are one example.
I would not expect the warning about typename to be generated by either of the source code lines that you show, but I can't really tell without seeing a compilable example.
You need to use typename when you use a type that depends on a template parameter. Example:
template <class T> class C1 {
public:
typedef T Type;
template <class T> class C2 {
public:
typename T::Type a;
C2< C1<int> > c2i;If in C2 you do not specify typename, the compiler does not know whether T::Type is intended to be the name of a type. If it is not a type, the code is always invalid. The C++ rule is that if an an identifier is not known to be a type, it is not a type. You use typename to tell the compiler that T::Type is supposed to be the name of a type.

Binary compatibility

Hello all,
I've compiled an app that will run as a service on solaris 8 (on a sparc ultra-5). I've used gcc to compile and the app runs fine on the sparc ultra-5.
My quesion is - will this compiled binary run on an E420 or any other sun hardware? In general, is there some docs/resources that describe binary compatibility across sun hardware?
Thanks for any info.

Hi,
Sun has a very strong binary compatibility guarantee, but I'm not sure where one would find documentation!
I would be more concerned about carting the required GCC runtimes around with you wherever you want to run your binary than Solaris or SPARC binary compatibility.
We build in 32 bit on a quad UltraSPARC III running Solaris 8, using Studio 10 (we were on Workshop 5 until recently!), and most of our customers run on Solaris 9, and in most cases on something a touch faster than UltraSPARC III.
I'd recommend you take a look at the new Studio 11 release (it is free after all) to avoid carting runtimes around with you. Please remember, however, that the machines your software runs on will need to be running at least the same patches as are pre-requisite for Studio 11 (well, the C and C++ runtimes anyway).
-- Michael

IOCTL for keyboard IO Solaris 10 and Solaris 8

Do you know what has chaned for keyboard io via solaris 8 and solaris 10 update 5?
Here is the story. I have a solaris binary work fine in solaris 8. It remaps the keyboard input (most probably using ioctl)
according to some table it has (actually a binary file on the filesystem). Code uses open windows.
It has told me that it work fine with free solaris update 3.
I am trying to make the code work in free solaris update 5, but keyboard input is not converted to something else.
We have installed OWA package for compatibility.
I have tried changing keymap of openwindows via various way openwin configuration, xmodmap, changing keytable files, etc. Here are resuts.
Solaris 8 and till Solaris update 3:
a -> A
In Solaris 10 update 5:
a -> 3
all keymap changes did not effect the result for solaris update 5.
The interesting part is If I start openwin via +kb option
a is converted to @
I don't have the source code for the binary.
What could be the reason for that? and more important any way to fix this?

Found the problem.
In solaris 8 keycodes are up to 159 and in Solaris 10 up to 254(?).
and keycodes refers to different characters between these two versions.

Binary compatibility problems using Sun Studio 12

I'm working in a project that uses Orbix [1] third-party libraries. I have installed the Sun Studio 12 on Solaris 10 SPARC but I have got some strange segfault problems (the exactly same code works fine in a Linux box - using g++). I read the 1.4 section of Sun Studio 12 C++ Userguide [2] but I have a doubt:
Is there no way to compile my code using Sun Studio 12 using shared libraries compiled against earlier Sun Studio C++ compiler versions (like Sun Studio 8 or some version before Sun Studio 11)?
I think my problem is related to the fact that Orbix team used Sun Studio 8 as some notes found in their headers indicate:
"IONA Technologies ART IDL Compiler POA C++ Generator asp 6.3.3 SunOS 5.8 CC_5.5 2008/06/13 21:04:37 EDT"
A secondary question: Is CC 5.5 present in Sun Studio 8, right?
Can anyone help me? Every tips are welcome :) Thanks in advance!
[1] http://web.progress.com/en/orbix/orbix_standard.html
[2] http://docs.sun.com/app/docs/doc/820-7599/6nirkt6f7?a=view

AmadeuBarbosa wrote:
I'm working in a project that uses Orbix [1] third-party libraries. I have installed the Sun Studio 12 on Solaris 10 SPARC but I have got some strange segfault problems (the exactly same code works fine in a Linux box - using g++). I read the 1.4 section of Sun Studio 12 C++ Userguide [2] but I have a doubt:I don't think 1.4 Binary Compatibility Verification applies in your case. It's referring to processor capability to execute certain (new) instructions; if your third-party libraries were compiled a while ago, it's highly unlikely they use instructions not implemented by the processor you have.
Is there no way to compile my code using Sun Studio 12 using shared libraries compiled against earlier Sun Studio C++ compiler versions (like Sun Studio 8 or some version before Sun Studio 11)?Generally speaking, any library compiled with older Sun Studio C++ compiler is supposed to be compatible with any library or executable compiled with newer version provided that all parties did everything right. For example, that third-party libraries should not be statically linked with C++ run-time support libraries; your executable should be linked with latest compiler driver (CC) so that it records correct dependencies on support libraries.
Of course, there could be (and actually are) compiler bugs standing in the way of compatibility. Some of them can be fixed, some - like demangler issue described in http://docs.sun.com/source/820-4155/c++.html - can't. There is no easy way to tell if you hit a compiler bug or bulding/linking issue, or bug in the code that was previously unseen.
I think my problem is related to the fact that Orbix team used Sun Studio 8 as some notes found in their headers indicate:
"IONA Technologies ART IDL Compiler POA C++ Generator asp 6.3.3 SunOS 5.8 CC_5.5 2008/06/13 21:04:37 EDT"Yes, looks like it was compiled by 5.5, which is part of Sun Studio 8
>
A secondary question: Is CC 5.5 present in Sun Studio 8, right?That's correct.

Compiling for solaris 9 on solaris 8 machine

Hi, is it possible to use a solaris 8 machine with workshop, to compile binary for solaris 9.
I need to compile user-mode app as well as kernel modules both for 64/32 bit environments.
The modules are all dynamically linked.
If this is possible, what is the proper procedure??
ERAN.

For user space apps, if you are sticking to the published interfaces (ie: not using any private, non-public symbols you might have dug up in our libraries) then compiling and linking on Solaris 8 and running on Solaris 9 is not a problem, at least for user space. Run appcert on your application if you want to ensure you aren't using anything private. We are forward-compatible in this sense.
As for kernel modules, I don't know enough to comment.

Migrating drivers from Solaris 9 to Solaris 10 (sparc)

I'm tasked to move some drivers from Solaris 9 to Solaris 10. Clearly, some elements of the interface have changed in this dot revision, as just installing the 2.9 drivers causes 2.10 to panic. I tried looking around the site for a guide to what changed in the driver interface. Can someone point me at a relevant document somewhere?

I'm tasked to move some drivers from Solaris 9 to
Solaris 10. Clearly, some elements of the interface
have changed in this dot revision, as just installing
the 2.9 drivers causes 2.10 to panic. I tried
looking around the site for a guide to what changed
in the driver interface. Can someone point me at a
relevant document somewhere?Nothing should have changed in the driver / kernel interfaces.
If the Solaris 9 driver uses only official / documented kernel
interfaces the same driver binary should run without problem on
Solaris 10.
All bets are off if the Solaris 9 driver is using internal kernel
data structures that are not part of the kernel / driver api.
Such a driver could fail by just installing OS patches to the system.

About incompatibility between Solaris 10 and Solaris 8

Dear all
I am investigating about incompatibility between Solaris 10 and Solaris 8.
But I can't find incompatibility information (I can find some compatibility imformation).
Please tell me about that if you know.
Any suggestions would be appreciated.
Thanks

Programs running on Solaris 8 should run on Solaris 10, but programs that run on Solaris 10 won't necessarily run on Solaris 8.
Solaris is always forward-compatible.
.7/M.

Qt QMake is missing - Solaris 11 and Solaris Studio 12.3

OS: Oracle Solaris 11 - http://www.oracle.com/technetwork/server-storage/solaris11/overview/index.html
Development tools: Solaris Studio 12.3 - http://www.oracle.com/technetwork/server-storage/solarisstudio/overview/index.html
Hi, I want to make Qt desktop applications for Oracle Solaris 11, and Solaris Studio supports Qt projects. However the binary QMake is missing.
Is it available somewhere?
Thank you a lot.
Edited by: 909513 on Jan 22, 2012 6:05 PM
Edited by: 909513 on Jan 22, 2012 6:06 PM

Here's what I used to compile up (I think) 90%+ of Qt 4.8.4. The configure step creates qmake and the compile rolls along until it hits a lot of non standard C++ code. But you get qmake out of it. The tarball is the latest snapshot of the 4.8.x git tree.
Caveat: It's being built using Sun Studio 12.3 and the stdcxx library from my package site, along with a bunch of dependant packages from there. I never got Qt 4.8.4 to finish compiling with webkit, the 3rdparty/javascriptcore/JavaScriptCore/* files are truly awful non compliant code and error out every step of the compile. Sigh.
Good luck
================================================================================
qt 4.8.2013.06.24
    https://qt.gitorious.org/qt/qt/trees/4.8
    Compile stdcxx 4.2.1    Done
    Compile dbus 1.7.2      Done
    Compile libmng 1.0.10   Skipped
    setenv CC "cc"
    setenv CXX "CC"
or
    setenv CC "cc -xtarget=ultra -m64 -xcode=pic32"
    setenv CXX "CC -xtarget=ultra -m64 -xcode=pic32"
    setenv LDFLAGS "-L/usr/local/lib -mt -library=no%Cstd -L/usr/local/lib -lstdcxx4"
    setenv CFLAGS "-I/usr/local/include -DUSE_SYSTEM_MALLOC"
    setenv CXXFLAGS "-I/usr/local/include -mt -library=no%Cstd -L/usr/local/lib -lstdcxx4 -DUSE_SYSTEM_MALLOC"
    setenv LINK "${CXX} -I/usr/local/include -mt -library=no%Cstd -L/usr/local/lib -lstdcxx4"
    setenv AR "${CXX} -I/usr/local/include -mt -library=no%Cstd -L/usr/local/lib -lstdcxx4 -xar -o"
    setenv CC "${CC} ${CFLAGS}"
    setenv CXX "${CXX} ${CXXFLAGS}"
    cd /var/tmp
    rm -rf qt-qt
    gunzip -c /usr/local/src/graphics/qt-4.8.2013.06.24.tar.gz | gtar -xvf -
    cd qt-qt
    /bin/perl -pe 's#/bin/sh#/bin/bash#'                              -i configure
    /bin/perl -pe 's#OPT_CONFIRM_LICENSE=no#OPT_CONFIRM_LICENSE=yes#' -i configure
    /bin/perl -pe 's#^QMAKE_INCDIR\s+=.*#QMAKE_INCDIR=/usr/local/include#'         -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe 's#^QMAKE_LIBDIR\s+=.*#QMAKE_LIBDIR=/usr/local/lib#'             -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe 's#^QMAKE_INCDIR_X11\s+=.*#QMAKE_INCDIR_X11=/usr/local/include#' -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe 's#^QMAKE_LIBDIR_X11\s+=.*#QMAKE_LIBDIR_X11=/usr/local/lib#'     -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe "s#^QMAKE_CC\s+=.*#QMAKE_CC=${CC}#"                              -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe "s#^QMAKE_CXX\s+=.*#QMAKE_CXX=${CXX}#"                           -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe "s#^QMAKE_LINK\s+=.*#QMAKE_LINK=${LINK}#"                        -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe "s#^QMAKE_LINK_SHLIB\s+=.*#QMAKE_LINK_SHLIB=${LINK}#"            -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe "s#^QMAKE_AR\s+=.*#QMAKE_AR=${AR} #"                             -i mkspecs/solaris-cc/qmake.conf
    /bin/perl -pe 's#canBuildWebKit=\"no\"#canBuildWebKit=\"yes\"#'                -i configure
    /bin/perl -pe 's#canBuildQtConcurrent=\"no\"#canBuildQtConcurrent=\"yes\"#'    -i configure
./configure -prefix /usr/local \
-qpa xcb \
-release \
-opensource \
-shared \
-no-fast \
-largefile \
-no-system-proxies \
-exceptions \
-accessibility \
-stl \
-qt-sql-sqlite \
-system-sqlite \
-no-qt3support \
-xmlpatterns \
-multimedia \
-audio-backend \
-no-phonon \
-phonon-backend \
-svg \
-webkit \
-x11 \
-no-javascript-jit \
-script \
-no-scripttools \
-declarative \
-platform solaris-cc \
-no-mmx \
-no-3dnow \
-no-sse \
-no-sse2 \
-no-sse3 \
-no-sse4.1 \
-no-sse4.2 \
-no-avx \
-no-neon \
-system-zlib \
-system-libtiff \
-system-libpng \
-no-libmng \
-system-libjpeg \
-openssl \
-nomake tests \
-R /usr/local/lib \
-I /usr/local/include \
-L /usr/local/lib \
-verbose \
-no-cups \
-iconv \
-no-gtkstyle \
-no-nas-sound \
-sm \
-xshape \
-no-xvideo \
-xsync \
-xinerama \
-xcursor \
-xfixes \
-no-xrandr \
-xrender \
-mitshm \
-fontconfig \
-no-xinput \
-xkb \
-no-glib \
-confirm-license \
-system-freetype
    foreach file (3rdparty/javascriptcore/JavaScriptCore/runtime/* 3rdparty/javascriptcore/JavaScriptCore/runtime/* 3rdparty/javascriptcore/JavaScriptCore/API/*)
        perl -pe 's#ENABLE$GLIB_SUPPORT$#0#' -i $file
        perl -pe 's#OS$DARWIN$#0#' -i $file
        perl -pe 's#OS$WINCE$#0#' -i $file
        perl -pe 's#OS$WINDOWS$#0#' -i $file
        perl -pe 's#OS$SYMBIAN$#0#' -i $file
        perl -pe 's#OS$OPENBSD$#0#' -i $file
        perl -pe 's#OS$QNX$#0#' -i $file
        perl -pe 's#OS$ANDROID$#0#' -i $file
        perl -pe 's#OS$RVCT$#0#' -i $file
        perl -pe 's#OS$FREEBSD$#0#' -i $file
        perl -pe 's#OS$HAIKU$#0#' -i $file
        perl -pe 's#OS$NETBSD$#0#' -i $file
        perl -pe 's#OS$MAC_OS_X$#0#' -i $file
        perl -pe 's#OS$IOS$#0#' -i $file
        perl -pe 's#OS$AIX$#0#' -i $file
        perl -pe 's#OS$LINUX$#0#' -i $file
        perl -pe 's#OS$UNIX$#1#' -i $file
        perl -pe 's#OS$SOLARIS$#1#' -i $file
        perl -pe 's#PLATFORM$BREWMP$#0#' -i $file
        perl -pe 's#PLATFORM$MAC$#0#' -i $file
        perl -pe 's#PLATFORM$WIN$#0#' -i $file
        perl -pe 's#PLATFORM$CHROMIUM$#0#' -i $file
        perl -pe 's#PLATFORM$WX$#0#' -i $file
        perl -pe 's#PLATFORM$GTK$#0#' -i $file
        perl -pe 's#COMPILER$MSVC$#0#' -i $file
        perl -pe 's#COMPILER$MINGW$#0#' -i $file
        perl -pe 's#COMPILER$GCC$#0#' -i $file
    end
    perl -pe '($. == 28) && s/^/#include "DateConversion.h"\n#include "DateInstance.h"/' -i 3rdparty/javascriptcore/JavaScriptCore/runtime/DateInstanceCache.h
    foreach file (3rdparty/javascriptcore/JavaScriptCore/runtime/*)
        perl -pe 's#JS_EXPORTDATA#__declspec(dllexport)#' -i $file
    end
    gmake
If you get this far you'll hit the dodgy code, but you'll have a qmake binary made. You can remove the -webkit option and it'll actually build qt I believe, but alas I need webkit
ta,
Mark

Wu-ftpd installable for solaris 10 and solaris 9

Hi,
I could see only "proftpd" is available http://www.sun.com/software/solaris/freeware
But I am looking for the "wu-ftpd" server which is compatable with Solaris 9 and Solaris 10.
Any one help me from where I can get the "wu-ftpd" installable for solaris 9 and solaris 10 sparc server.
thanks,
Amudha

Hi Robert,
Thanks for your reply.
I too saw that the ftp version used in solaris 10 by default is wu-ftpd, but I am not sure about it, because when I tried to ftp to my solaris box the version it is started is not "FTP server (Version wu-2.6.2(5)".
I have got the wu-ftpd installable. But I could not get the proper document for configuring the same.
Question1: How to stop existing ftp service and start newly instlaled wu-ftpd in Solaris 9 and Solaris 10 servers?
Earlier solaris 8 version I change the ftpd version in /etc/inetd.conf file and give HUP signal to inetd then this new wu-ftpd version will be used.
Question 2: It always starts the system inbuilt ftp server and also I am getting ftp log in failure for any user which I add newly or even existing users.
could any one help to resolve these issues? Thanks in advance for your help.
Amdudha

Difference of nslookup printout on Solaris 9 and Solaris 10

Hi,
I am not sure whether I had to post in Solaris 9 or Solaris 10 forum. So I posted this here too.
We are porting some of our applications from Solaris 9 to Solaris 10. We found a
strange problem/ scenario with the nslookup on Solaris 9.
We issued a ENUM query on Solaris 9 and the output from the nslookup binary on
Solaris 9 is given below :
nslookup -q=naptr -timeout=0 -domainname=. 0.0.2.1.6.2.2.7.2.1.0.e164i.arpa
Server: test.org
Address: xx.xx.xx.xx
0.0.2.1.6.2.2.7.2.1.0.e164i.arpa order = 0, preference = 0
flags = "u"
services = "E2U+sip"
rule = "!^.*$!sip:01272261200;phone-context=[email protected];user=phone!"
replacement = (root)
0.0.2.1.6.2.2.7.2.1.0.e164i.arpa order = 1, preference = 0
flags = "u"
services = "E2U+sip"
rule = "!^.*$!sip:01272261200;phone-context=[email protected];user=phone!"
replacement = (root)
The same query on Solaris 10 has the following output :
nslookup -q=naptr -timeout=0 -domain=. 0.0.2.1.6.2.2.7.2.1.0.e164i.arpa
Server: xx.xx.xx.xx
Address: xx.xx.xx.x#53
0.0.2.1.6.2.2.7.2.1.0.e164i.arpa naptr = 0 0 "u" "E2U+sip" "!^.*$!sip:01272261200\;phone-context=[email protected]\;user=phone!" .
0.0.2.1.6.2.2.7.2.1.0.e164i.arpa naptr = 1 0 "u" "E2U+sip" "!^.*$!sip:01272261200\;phone-context=[email protected]\;user=phone!" .
I was wondering why the backslash is present only on Solaris 10 and not in Solaris 9. Is this a error in Solaris 9 or is the prinout format in Solaris
10 wrong ???
Thanks in advance !!
Regards,
Philip

We encoutered a problem on the solaris 10 machine do to a applicative bug. At a moment we get the url xxxxx.do?method=toto&method=titi.Havent you used the same parameter name ??
method=toto&method=titi
Looks same to me ;-)
So I envision this as a coding bug than a Solaris bug.
Or ...maybe you can throw some more light if I misunderstood you.
-Rohit

Steps to upgrade Solaris 7 to Solaris 8

Can any one let me know where I can find the detail documentation of how I
upgrade Sun box running Solaris 7 to Solaris 8.

Hi,
Please go through this link to know the detailed procedure to upgrade from solaris 7 to 8.
http://www.cims.nyu.edu:8888/ab2/coll.320.7/SPARCINSTALL/@Ab2PageView/3068?
Hope this helps you.
Rgds,
Dhana_slash.

Solaris 8 binary compatibility - Solaris 7

Similar Messages

Maybe you are looking for