Sponsored Content
Operating Systems Solaris Solaris 10 - HW compatibility Post 302499840 by bluescreen on Friday 25th of February 2011 01:55:22 PM
Old 02-25-2011
They are both sun4u systems running Solaris 10. You should be ok.
This User Gave Thanks to bluescreen For This Post:
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Program Compatibility

I really Hate the Monopoly Microsoft has over Software, but the fact remains it exists... so I wonder if there was a way to enable Programs Made for Windows and Mac to be Run in Unix as if it was in the Specified OS. Like a Compatibility Wizard. Or in a dual boot computer, for Unix to be able to... (4 Replies)
Discussion started by: Elliandr
4 Replies

2. HP-UX

About compatibility of HP-UX 11i

Could you please tell me if Informix 7.20 UD2 works on HP-UX 11i and if applications that works on HP-UX 10.20 and Informix 7.20 UD2 works on HP-UX 11i. Thanks a lot. (0 Replies)
Discussion started by: Irene Martínez
0 Replies

3. Shell Programming and Scripting

date -d compatibility on Solaris

Hello there ppl, I thought my question would qualify to be posted in this forum and in Solaris forum. And I swear to God.. there is no discussion on this exact topic anywhere else on the web! So my script on BASH uses 2 commands: 1) date -d "Fri Mar 06 10:18:16 UTC 2009" +%s This... (3 Replies)
Discussion started by: pavanlimo
3 Replies

4. BSD

FreeBSD compatibility with Solaris UFS filesystem?

Hi, I'm new to BSD and would like to create a dual-boot between Solaris Express Community Edition and FreeBSD. I would just like to know if the Solaris UFS file system can be written to by BSD? I know that BSD uses UFS2, but I'm hoping that it is backwards compatible with UFS1 provided that... (0 Replies)
Discussion started by: Johnny SSH
0 Replies

5. Solaris

Clearcase compatibility with Solaris 10

Hi, Is Clearcase version 2002.05.00 is supported and compatible with Solaris10? Cheers, Ankur (1 Reply)
Discussion started by: sharmaankur85
1 Replies

6. Solaris

Solaris 8 vs Solaris 10 compatibility issues !

Hello, I recently upgraded our system from Solaris 8 to 10. It seems couple of binaries crashed in the new server Solaris 10. Before digging too much on it , from theory it sounds like any binary that is built on Solaris 8 (using gmake) is supposed to be compatible with Solaris 10 , right ? ... (1 Reply)
Discussion started by: sudsa
1 Replies

7. Hardware

Solaris HW compatibility list

I'm picking HW for my cheap Solaris server and am wondering if there is a decent list of HW compatible with the Solaris OS. The best I could find is this: OTN - Oracle Solaris 11 11/11: Hardware Compatibility List, but it surprises me that only a single motherboard is listed. I am searching... (1 Reply)
Discussion started by: RychnD
1 Replies

8. Solaris

Retina display Macbook Pro and Solaris compatibility

Has anyone attempted to install Solaris 11 on a Macbook Pro with the new Retina display? I'm considering setting up a triple boot scenario with Windows 7, Mac OS X and Solaris 11. My goals are to learn the OS better and to gain daily exposure to it by running it as a desktop OS whenever possible. (11 Replies)
Discussion started by: DustinT
11 Replies

9. Solaris

Solaris 11 compatibility/ucb install

Hi im a newbie to solaris. im given the task to install the compatibility/ucb component my environment is without internet connection. so when i ran the command: pkg install compatibility/ucb i get an error: Unable to contact valid package repository where can i find the download for this... (2 Replies)
Discussion started by: guy3145
2 Replies
platform(4)							   File Formats 						       platform(4)

NAME
platform - directory of files specifying supported platforms SYNOPSIS
.platform DESCRIPTION
The Solaris operating environment release includes the .platform directory, a new directory on the Solaris CD image. This directory con- tains files (created by Sun and Solaris OEMs) that define platform support. These files are generically referred to as platform definition files. They provide a means to map different platform types into a platform group. Platform definition files in the .platform directory are used by the installation software to ensure that software appropriate for the architecture of the system will be installed. Sun provides a platform definition file named .platform/Solaris . This file is the only one that can define platform groups to which other platform definition files can refer. For example, an OEM platform definition file can refer to any platform group specified in the Solaris platform definition file. Other platform definition files are delivered by OEMs. To avoid name conflicts, OEMs will name their platform definition file with an OEM- unique string. OEMs should use whatever string they use to make their package names unique. This unique string is often the OEM's stock symbol. Comments are allowed in a platform definition file. A "#" begins a comment and can be placed anywhere on a line. Platform definition files are composed of keyword-value pairs, and there are two kinds of stanzas in the file: platform group definitions and platform identifications. o Platform group definitions: The keywords in a platform group definition stanza are: PLATFORM_GROUP The PLATFORM_GROUP keyword must be the first keyword in the platform group definition stanza. The value assigned to this keyword is the name of the platform group, for example: PLATFORM_GROUP=sun4c The PLATFORM_GROUP name is an arbitrary name assigned to a group of platforms. However, PLATFORM_GROUP typically equals the output of the uname -m command. PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII characters. INST_ARCH The instruction set architecture of all platforms in the platform group, for example: INST_ARCH=sparc The INST_ARCH keyword value must be the value returned by the uname -p command on all platforms in the platform group. o Platform identifications: The keywords in a platform identification stanza are: PLATFORM_NAME The PLATFORM_NAME keyword must be the first keyword in the platform identification stanza. The PLATFORM_NAME is the name assigned to the platform, for example: PLATFORM_NAME=SUNW,SPARCstation-5 Typically, this name is the same as the value returned by the uname -icommand on the machine, but it need not be the same. The PLATFORM_NAME value cannot have white space and is limited to 256 ASCII characters. If it contains paren- theses, it must contain only balanced parentheses. For example. the string "foo(bar)foo" is a valid value for this keyword, but "foo(bar" is not. The other keywords in the platform identification stanza can be in any order, as long as the PLATFORM_NAME keyword is first. PLATFORM_ID The value returned by the uname -i command on the machine, for example: PLATFORM_ID=SUNW,SPARCstation-5 MACHINE_TYPE The value returned by the uname -m command on the machine, for example: MACHINE_TYPE=sun4c IN_PLATFORM_GROUP The platform group of which the platform is a member, for example: IN_PLATFORM_GROUP=sun4c The platform group name must be specified in the same file as the platform identification stanza or in the platform definition file with the name .platform/Solaris . The IN_PLATFORM_GROUP keyword is optional. A platform doesn't have to belong to a platform group. If a plat- form is not explicitly assigned to a platform group, it essentially forms its own platform group, where the platform group name is the PLATFORM_NAME value. The IN_PLATFORM_GROUP value typically equals the output of the uname -m command. IN_PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII characters. INST_ARCH The instruction set architecture of the platform, for example: INST_ARCH=sparc This field is only required if the platform does not belong to a platform group. The INST_ARCH keyword value must be the value returned by the uname -i command on all platforms in the platform group. COMPATIBILITY
The installation program will remain compatible with the old Solaris CD format. If a Solaris CD image does not contain any platform defini- tion files, the installation and upgrade programs will select the packages to be installed based on machine type, that is, the value returned by the uname -p command. EXAMPLES
Example 1: Platform Group Definitions The following example shows platform group definitions from the .platform/Solaris platform definition file. # PLATFORM_GROUP=sun4u INST_ARCH=sparc Example 2: Platform Identification Stanzas The following example shows platform identification stanzas, which define systems that belong in a platform group, from the .plat- form/Solaris platform definition file. # PLATFORM_NAME=SUNW,SunFire PLATFORM_ID=SUNW,SunFire IN_PLATFORM_GROUP=sun4u PLATFORM_NAME=SUNW,Ultra-80 PLATFORM_ID=SUNW,Ultra-80 IN_PLATFORM_GROUP=sun4u # PLATFORM_NAME=SUNW,SunFire PLATFORM_ID=SUNW,SunFire IN_PLATFORM_GROUP=sun4u # PLATFORM_NAME=SUNW,Ultra-80 PLATFORM_ID=SUNW,Ultra-80 IN_PLATFORM_GROUP=sun4u FILES
The .platform directory must reside as /cd_image/Solaris_vers/.platform, where cd_image Is the path to the mounted Solaris CD (/cdrom/cdrom0/s0 by default) or the path to a copy of the Solaris CD on a disk. Solaris_vers Is the version of Solaris, for example, Solaris_2.9. NOTES
Typically, a platform identification stanza contains either a PLATFORM_ID or a MACHINE_TYPE stanza, but not both. If both are specified, both must match for a platform to be identified as this platform type. Each platform identification stanza must con- tain either a PLATFORM_ID value or a MACHINE_TYPE value. If a platform matches two different platform identification stanzas--one which matched on the value of PLATFORM_ID and one which matched on the value of MACHINE_TYPE , the one that matched on PLATFORM_ID will take precedence. The .platform directory is part of the Solaris CD image, whether that be the Solaris CD or a copy of the Solaris CD on a system's hard disk. SunOS 5.10 19 Nov 2002 platform(4)
All times are GMT -4. The time now is 03:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy