10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
2. AIX
Anyone running CICS TX in a WPAR ?
In my attempts to run CICS TX 5.1.0.1 in a WPAR..... CICS fails to start due to unable to load a CICS IPC Kernel Extension. The Kernel Extension is 64 bit (so not a 32 vs 64 bit issue).
Base system/LPAR is Power8 and AIX 7.1 TL3 SP5. WPAR is versioned... (4 Replies)
Discussion started by: The Doctor
4 Replies
3. Solaris
I'm posting here as it didn't seem quite right in the hardware section (as it's LOM commands). My apologies if I have that wrong though :)
I've finally gotten round to configuring the LOM on my Netra X1, but I can't get it to change the hostname via the "set" command:
lom>show hostname... (2 Replies)
Discussion started by: Smiling Dragon
2 Replies
4. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
5. Solaris
Hi
i am accessing the server remotly. i want to replace bad dvd writer. how do i know the part number of the dvd drive for raising a spare.
thanks (3 Replies)
Discussion started by: sunnybee
3 Replies
6. AIX
Hi,
This is odd, however here goes. There are several shell scripts that run in our production environment AIX 595 LPAR m/c, which has sufficient memory 14GB (physical memory) and horsepower 5CPUs. However from time to time we get the following errors in these shell scripts. The time when these... (11 Replies)
Discussion started by: jerardfjay
11 Replies
7. Shell Programming and Scripting
Hallo,
i need a Prompting read in my script:
read -p "Enter your command: " command
But i always get this Error:
-p: is not an identifier
When I run these in c-shell i get this error
/usr/bin/read: read: bad option(s)
How can I use a Prompt in the read command? (9 Replies)
Discussion started by: wiseguy
9 Replies
8. Filesystems, Disks and Memory
Dear All,
i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies
9. Shell Programming and Scripting
Hi,
running a script fine , i get twice the following message and whether i put "set -x" , i don't see what's going wrong :
/users/notes01/scripts/sad/util/verif_boot_notes.ksh: Ma: bad number
any ideas ?
regards
Christian (4 Replies)
Discussion started by: Nicol
4 Replies
10. Solaris
I tried rebooting my Sun server just a few minutes ago and I got the following at boot:
--
Sun Fire 280R (UltraSPARC-III+) , No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx
Ethernet address... (6 Replies)
Discussion started by: deckard
6 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)