Sponsored Content
Operating Systems Solaris Clubbing Sun Ultra 60 Machines Post 302525685 by general_lee on Friday 27th of May 2011 12:32:04 PM
Old 05-27-2011
Yes you can do this.

If you want two independent operating systems (1 on each HD).

You'll need to create an alias in OBP for the second disk and change the boot device to point at whichever disk you want to boot from.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sun Ultra sparc 60

Hello everybody!! I need your help again. I am using Sun Ultra sparc 60 machine.Follwing are the types of files getting generated in /var/tmp. "windu_sm_o aaaa,baaa,caaa,daaa" etc. I am not able to locate which application is generating these files. Can I straightway delete these files ? or... (1 Reply)
Discussion started by: vikasdeshmukh
1 Replies

2. UNIX Benchmarks

Sun Ultra 30 Solaris 8

Sun Ultra30 Solaris 8 Notes: ... Results: System -- SunOS box 5.8 Generic_108528-23 sun4u sparc SUNW,Ultra-30 Start Benchmark Run: Fri Sep 12 11:59:12 EDT 2003 1 interactive users. Dhrystone 2 without register variables 502087.7 lps (10 secs, 6 samples) Dhrystone 2 using... (2 Replies)
Discussion started by: tnorth
2 Replies

3. Solaris

sun ultra or sun sparkstation

am wonder wich sun computer is better, a sun ultra or sun sparkstation, and what is the difference (7 Replies)
Discussion started by: nobody
7 Replies

4. Solaris

sun ultra

Hi Guys, I have a 2nd hand Sun ultra-5, I wanted to know how to be able to run it as a normal window. I do not have any experience whatsoever with solaris/unix. Does anyone can give me a clue where to start. When I switch it goes to: unix console login: pa$$word: #UNIX sendmail : enable to... (0 Replies)
Discussion started by: lingosa
0 Replies

5. Solaris

hey i just got a Sun ultra 5!!!

now what do i do? im looking at it and i booted it after a bunch of code i got a line askign for the password i also downloaded solaris 10 any advice on how to install it? (36 Replies)
Discussion started by: russian460
36 Replies

6. Solaris

sun ultra 10 monitor

hi all, it seem hard to see on a regular monitor the ultra 10 converter to rgb so that it can go to a pc monitor. do u know how can i fix the monitor properly? it's not easy to see on the monitor there's so many lines. thanks in advance. (2 Replies)
Discussion started by: itik
2 Replies

7. Solaris

LOM on SUN ultra 10

Hi experts is it possible to install lom on sun ultra 10 box? can you guys help me in undertanding lom as i tried goggling , couldn't get good stuff. Please :) (6 Replies)
Discussion started by: kumarmani
6 Replies

8. Solaris

SUN ULTRA 45 - Solaris

hi, my sun box hangs- KEYBOARD not found. Using hyper link it boots and then hangs without able to access or get ok promt ----SCREEN SHOT AS-------------------------------------------------- ˙Loading onboard drivers: ebus i2c i2c i2c ppm /ebus@1f,464000: flashprom rtc serial serial env-monitor... (2 Replies)
Discussion started by: mathav22
2 Replies

9. Hardware

Sun Sparc Ultra 30 help

Hi all, I managed to salvage form work an old Sun Sparc Ultra 30. I have had it stored (controlled storage) for a few years and decided to get it home and boot it up. It starts up with a beep then I can hear disks spinning up, CDROM moving but nothing is displayed on the monitor. Can... (2 Replies)
Discussion started by: robbo007
2 Replies

10. Solaris

Sun Ultra 5 new user

Hi I have just acquired an Ultra 5. It has 256MB of memory and a 360Mhz Ultra IIi SPARC processor. So far, I have had some typical fun and games to get it working: - It had a dead NVRAM chip. I hacked it open and installed a CR2032. It looks suitably bodged up, but is working. I set the MAC... (8 Replies)
Discussion started by: _JonB_
8 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 02:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy