Sponsored Content
Full Discussion: The Mystery Directory
Operating Systems Solaris The Mystery Directory Post 302144692 by blowtorch on Friday 9th of November 2007 08:35:26 AM
Old 11-09-2007
Check all scripts that are referring to this directory. The fact that the directory gets soft linked - pretty much sure that a script is responsible.
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

terminal/port (serial) lock up mystery! SCO 5.0

Sorta new to Unix. great site here. I have SCO server with (5) 16 port Digi-boards and 5 line printers. For 3 years we've had no problems, till now... All of a sudden I get terminals and printers locking up. Killed the PID's for these particular situations. No help. So I disable the tty post... (10 Replies)
Discussion started by: ftn96
10 Replies

2. IP Networking

Traceroute and Whois mystery

Hey folks, I've been charged with the job of finding out who's been screwing around with the download counts on our site. So now I have this huge list of IP's that I supposed to match to such and such developer. I was told by one guy that I should just do a traceroute and that'd tell me where... (2 Replies)
Discussion started by: DumDum
2 Replies

3. UNIX for Advanced & Expert Users

A perplexing mystery

A perplexing mystery... please note that i am not a lacky, and the error below is misleading recently something i do all the time broke (a script). now when i run this script i get this error. /usr/bin/awk: 0403-027 The parameter list is too long. note that the (parameter list is... (9 Replies)
Discussion started by: nullwhat
9 Replies

4. Filesystems, Disks and Memory

I/O Error Mystery

I burned identical raw encrypted data to three cds using my new external Toshiba drive. My internal IBM read only drive does not get an I/O Error when reading in Circumstance #1, but does get an I/O Error in Circumstance #2. But, the Toshiba drive can do both circumstances without an error. ... (1 Reply)
Discussion started by: darkstarxor
1 Replies

5. Shell Programming and Scripting

Mystery about Case Statement

Can I make use of two command variable in case statement case $2 $3 in stp) Firewall disabled echo " Changing the http Proxy configuration " ;; str) Firewall enabled echo " Setting right http Proxy... (4 Replies)
Discussion started by: raghunsi
4 Replies

6. Shell Programming and Scripting

sort mystery

Hi everyone, I can't seem to understand the behavior of sort on a particular case. cat tmp25 1 a 10 b 20 c 2 d I do that: sort -k1,1 tmp25 1 a 10 b 2 d 20 c This one I understand, it's what i expected, from a string point of view 1<10<2<20 sort -k1... (9 Replies)
Discussion started by: a.brassac
9 Replies

7. UNIX for Dummies Questions & Answers

File permission mystery ?

Hello, running AIX 6.1 # ls -la /home/user1 drwxrwxrwx 8 user1 staff 4096 Apr 19 2011 . drwxr-xr-x 8 bin bin 256 Feb 08 2011 .. drwx---r-x 2 user1 staff 256 Apr 13 2011 dir1 # su - user2 $ cd /home/user1 $ ls dir1 ls: dir1: The file... (1 Reply)
Discussion started by: vilius
1 Replies

8. UNIX for Advanced & Expert Users

Apache Mod_rewrite Mystery

Hi Folks, I am running on a CentOS 6.3 server, whose primary function until recently has been my Zimbra mail server exclusively. I added wordpress and I have not been disappointed, with this one exception of Apache mod_rewrite. I have already tried to set selinux to permisive to eliminate that... (5 Replies)
Discussion started by: cjm51213
5 Replies

9. Shell Programming and Scripting

Shell functions mystery

so i noticed that when a shell script has a function defined in it, running "sh -x" on that shell script from the command line doesnt show what the function is doing. i like this. is there anyway for anyone to get around that? to be able to see exactly what a function or functions are doing? (4 Replies)
Discussion started by: SkySmart
4 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 typi- cally 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 plat- form 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 PLAT- FORM_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 parentheses, 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 platform 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 char- acters. 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.11 19 Nov 2002 platform(4)
All times are GMT -4. The time now is 01:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy