05-21-2013
Perhaps I'm missing something here. Why do you want to do that in the first place? Is this for test purposes only?
If I understand your post you are considering putting two guest Solaris nodes on the same VMware platform? Am I correct?
The generic purpose of all clustering is to protect against total platform failure so putting two (or all) nodes of a cluster on the same platform defeats everything since if that platform goes down the user service goes down too.
Please explain and we'll try to answer.
8 More Discussions You Might Find Interesting
1. Solaris
hello all I have prob with solaris 10 and vmware 5.5, 6.0 that befor it's good work and from yesterday when I try to add new vm in SCSI Controller from vmware it's Don't see any Hard Disk or controller when I used solaris 5 cd-cdrom
and DVD version but when try to make vm with IDE controller... (0 Replies)
Discussion started by: Hosam
0 Replies
2. Solaris
I had previous implemented the following in my menu.lst to be able to get to 32-bit operations.
#
title Solaris 10 32-bit
root (hd0,0,a)
kernel /platform/i86pc/multiboot kernel/unix
module /platform/i86pc/boot_archive
</code>
Now, it is not working as I get the following error :
... (0 Replies)
Discussion started by: praveenr
0 Replies
3. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
4. Solaris
Hi,
I am trying to convert 32-bit code to 64-bit.
I have defined function
int main()
{
int* l;
size_t len1;
fun(len1);
return 0;
}
void fun(int* ptr)
{
cout<<"\nsizeof(ptr)"<<sizeof(ptr);
}
However while compiling getting error as :
Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies
5. Solaris
pls can someone direct me on the vmware product that i can install on solaris 10 (4 Replies)
Discussion started by: seyiisq
4 Replies
6. Solaris
:confused:
how to find out wether my os is 32 bit or 64 bit. I am using Solaris 5.6.
also i want to know the difference between 32 bit and 64bit os.
any help will be much appreciated as i am in urgent need of this information (6 Replies)
Discussion started by: asalman.qazi
6 Replies
7. Solaris
Hello everybody,
I'm trying to create a S10 cluster on ESX 3.5 servers but I have several problems.
I use AMD Athtlon x64 CPU's on ESX servers and Solaris 10 U8 at my guest servers..
First and the most important problem, I dont know how to attach a RDM disk to Solaris 10. (Is it correct,... (1 Reply)
Discussion started by: shadowfaxxxx
1 Replies
8. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
LEARN ABOUT CENTOS
platform
platform(n) Tcl Bundled Packages platform(n)
__________________________________________________________________________________________________________________________________________________
NAME
platform - System identification support code and utilities
SYNOPSIS
package require platform ?1.0.4?
platform::generic
platform::identify
platform::patterns identifier
_________________________________________________________________
DESCRIPTION
The platform package provides several utility commands useful for the identification of the architecture of a machine running Tcl.
Whilst Tcl provides the tcl_platform array for identifying the current architecture (in particular, the platform and machine elements) this
is not always sufficient. This is because (on Unix machines) tcl_platform reflects the values returned by the uname command and these are
not standardized across platforms and architectures. In addition, on at least one platform (AIX) the tcl_platform(machine) contains the CPU
serial number.
Consequently, individual applications need to manipulate the values in tcl_platform (along with the output of system specific utilities) -
which is both inconvenient for developers, and introduces the potential for inconsistencies in identifying architectures and in naming con-
ventions.
The platform package prevents such fragmentation - i.e., it establishes a standard naming convention for architectures running Tcl and
makes it more convenient for developers to identify the current architecture a Tcl program is running on.
COMMANDS
platform::identify
This command returns an identifier describing the platform the Tcl core is running on. The returned identifier has the general for-
mat OS-CPU. The OS part of the identifier may contain details like kernel version, libc version, etc., and this information may con-
tain dashes as well. The CPU part will not contain dashes, making the preceding dash the last dash in the result.
platform::generic
This command returns a simplified identifier describing the platform the Tcl core is running on. In contrast to platform::identify
it leaves out details like kernel version, libc version, etc. The returned identifier has the general format OS-CPU.
platform::patterns identifier
This command takes an identifier as returned by platform::identify and returns a list of identifiers describing compatible architec-
tures.
KEYWORDS
operating system, cpu architecture, platform, architecture
platform 1.0.4 platform(n)