Sponsored Content
Operating Systems Solaris Running Solaris SPARC on Intel Hardware???? Post 302723343 by DukeNuke2 on Tuesday 30th of October 2012 02:17:28 AM
Old 10-30-2012
Quote:
Originally Posted by os2mac
The have several different prebuilt Oracle Solaris VM's for virtualbox that would allow you to do this. I have atleast three on my windows 7 machine at the moment that I use for a dev/tst environment.
i don't think that you have the sparc edition running on your vbox platform...
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sparc vs Intel performance

Hello all, I have been trying to find any data that states what platform would garner better overall performance in an Oracle Cluster. The scenario: This is a high traffic e-commerce site with IIS and Commerce server on the front end. The backend consists of a Sun Solaris hardware/software... (7 Replies)
Discussion started by: kmgrady01
7 Replies

2. UNIX for Dummies Questions & Answers

Running Solaris Sparc Apps on X86 Solaris

I know that Sun make s a version of Solaris for Sparc platforms and also an x86 (Intel/AMD) release of Solaris. Can an application that runs on Solaris/Sparc also run on a PC running the x86 release of Solaris? Would a different release be required or any re-compling of the application? jim (1 Reply)
Discussion started by: stocksj
1 Replies

3. Solaris

Solaris 10 on SPARC & x64/x86 hardware requirements

Hi folks Doing practice certification questions but the answers to this question appear different everywhere I look? Is it also seems to be dependent on the S10 update version using at the moment in the market place? If the book was written over year back, then I suppose the hardware... (4 Replies)
Discussion started by: angusyoung
4 Replies

4. UNIX for Dummies Questions & Answers

can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?

Hi Gurus can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC? regards, Israel. (9 Replies)
Discussion started by: iga3725
9 Replies

5. Programming

Padding issues between Sparc and Intel

Hello, I'm facing severe structure padding issues when my Solaris C/C++ application that runs on Sparc communicates with the same C/C++ application that runs on Intel. I know that Sparc and Intel use different padding patterns. So when it comes to reading the exchanged structure data, both... (11 Replies)
Discussion started by: Goseib
11 Replies

6. Hardware

seeking QUIET hardware Sparc Solaris 8/Openwin

I have several applications locked to Solaris 8 (and older) and have been very happy with my Sparcs and Ultras but am getting tinnitus problems from fans and disks. Any tips on a quiet thin client (with decent graphics, not video or gaming level but 24bit and multi monitor would be useful) that... (0 Replies)
Discussion started by: batchman
0 Replies

7. Solaris

Service error on sparc server running solaris 10

Hi, I am getting following service error on one of the sparc servers running solaris 10 - Code : $ svcs -a | grep "maintenance" maintenance Nov_08 svc:/application/management/sma:default $ svcs -xv svc:/application/management/sma:default (net-snmp SNMP daemon) State: maintenance... (8 Replies)
Discussion started by: sunadmin
8 Replies
tst(3)							    InterNetNews Documentation							    tst(3)

NAME
tst - ternary search trie functions SYNOPSIS
#include <inn/tst.h> struct tst; struct tst *tst_init(int node_line_width); void tst_cleanup(struct tst *tst); int tst_insert(struct tst *tst, const unsigned char *key, void *data, int option, void **exist_ptr); void *tst_search(struct tst *tst, const unsigned char *key); void *tst_delete(struct tst *tst, const unsigned char *key); DESCRIPTION
tst_init allocates memory for members of struct tst, and allocates the first node_line_width nodes. A NULL pointer is returned by tst_init if any part of the memory allocation fails. On success, a pointer to a struct tst is returned. The value for node_line_width must be chosen very carefully. One node is required for every character in the tree. If you choose a value that is too small, your application will spend too much time calling malloc(3) and your node space will be too spread out. Too large a value is just a waste of space. tst_cleanup frees all memory allocated to nodes, internal structures, as well as tst itself. tst_insert inserts the string key into the tree. Behavior when a duplicate key is inserted is controlled by option. If key is already in the tree then TST_DUPLICATE_KEY is returned, and the data pointer for the existing key is placed in exist_ptr. If option is set to TST_REPLACE then the existing data pointer for the existing key is replaced by data. Note that the old data pointer will still be placed in exist_ptr. If a duplicate key is encountered and option is not set to TST_REPLACE then TST_DUPLICATE_KEY is returned. If key is zero length then TST_NULL_KEY is returned. A successful insert or replace returns TST_OK. A return value of TST_ERROR indicates that a memory allocation error occurred while trying to grow the node free. Note that the data argument must never be NULL. If it is, then calls to tst_search will fail for a key that exists because the data value was set to NULL, which is what tst_search returns. If you just want a simple existence tree, use the tst pointer as the data pointer. tst_search finds the string key in the tree if it exists and returns the data pointer associated with that key. If key is not found then NULL is returned, otherwise the data pointer associated with key is returned. tst_delete deletes the string key from the tree if it exists and returns the data pointer assocaited with that key. If key is not found then NULL is returned, otherwise the data pointer associated with key is returned. HISTORY
Converted to POD from Peter A. Friend's ternary search trie documentation by Alex Kiernan <alex.kiernan@thus.net> for InterNetNews 2.4.0. $Id: tst.pod 8200 2008-11-30 13:31:30Z iulius $ INN 2.5.2 2009-05-21 tst(3)
All times are GMT -4. The time now is 03:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy