Sponsored Content
Full Discussion: Solaris 64bit and Y2038 bug
Operating Systems Solaris Solaris 64bit and Y2038 bug Post 302452438 by nullpt on Friday 10th of September 2010 11:19:42 AM
Old 09-10-2010
Solaris 64bit and Y2038 bug

Hi all,

I'm runing a 64bit Solaris 9 system that supposedly isn't affected by the y2038 bug. If so, why can't I set de that from that point in time forward?

Code:
root@machine>uname -a
SunOS machine 5.9 Generic_118558-36 sun4u sparc SUNW,Sun-Fire-V440
root@machine>isainfo -b
64
root@machine>mktime -y +27
2037-09-10 16:18:18
root@machine>mktime -y +28
mktime: invalid time

Thanks in advance
BR
AJ

Last edited by Scott; 09-10-2010 at 01:21 PM.. Reason: Please use code tags
 

8 More Discussions You Might Find Interesting

1. Solaris

fsck bug in Solaris 8

Be careful, we've just found out that the fsck command in Solaris 8 has caused corruption of our ufs files-stores. This was introduced in patch SUNWcsu patch 110910-05. Be warned, Sun are fixing this as we speak :eek: (1 Reply)
Discussion started by: Maillot Jaune
1 Replies

2. Solaris

CC 5.5 compiler flag to issue 64bit porting warnings on sparc-solaris

Hi, We are porting our application from 32bit to 64bit. We tried -xarch=v9, -xarc=v9a and -xport64=full options so that compiler to issue 64bit porting warnings. But we are not getting any porting warninings WE are using CC 5.5 compiler on sparc-solaris m/c. Please tell us some powerful... (0 Replies)
Discussion started by: shobhah
0 Replies

3. Solaris

32bit / 64bit issue with x86 solaris

i have solaris 10 x86 64bit installed on my pc (dell 3100). i then decided to move my hard drive to another pc (dell 4600). I noticed that each time i boot up, the OS show as 32 bit (instead of 64bit) and i can't even get past this stage to the login page. when i moved it back to dell 3100 it... (13 Replies)
Discussion started by: seyiisq
13 Replies

4. Solaris

Solaris SPARC 10 64Bit -JDK Installation 1.6.05

In Sun Solaris 10, not able to create the key. JDK 1.6 Installed & PATH & JAVA_HOME both are referred to jdk 1.6. It is showing the belwo error Error: wrap() failed java.security.InvalidKeyException: wrap() failed at sun.security.pkcs11.P11RSACipher.engineWrap(P11RSACipher.java:395) at... (10 Replies)
Discussion started by: saktiviji
10 Replies

5. Solaris

Apcahe2 64bit on solaris 10 sparc!

Hi, i'm trying to compile apache 2.2.13 on solaris 10 sparc as 64bit and for some reason its always compiled as 32bit! i know it can be done cause i've already done it before, so i'm not sure what am i doint wronghttp://forums.digitalpoint.com/images/smilies/frown.gif i've edit /.profile... (0 Replies)
Discussion started by: levic
0 Replies

6. Solaris

Where to download solaris 10 for sparc 64bit?

hi all I just got a sun blade 2000 server for free. I need to load a solaris 10 for sparc OS to it. the memory inside the box is 5gb. the cup is SUNW,UltraSPARC-III+ (1200 MHz @ 8:1, 8 MB). so my questions is 1. do I need to install a 64bit os or a 32bit os? 2. where can I download the... (3 Replies)
Discussion started by: rs6000er
3 Replies

7. Solaris

where can i download solaris 10 64bit for my intel machine?

where can i download solaris 10 64bit for my intel machine? i am able to find only 32bit solaris for intel machine. Please help me.. (2 Replies)
Discussion started by: chidori
2 Replies

8. Solaris

SUNWi1cs SUNWi15cs packages for solaris 10 64bit sparc

hi, i need to install SUNWi1cs and SUNWi15cs packages for solaris 10 sparc 64 bit , where can i download these packages . Thanks . (2 Replies)
Discussion started by: zeeshan047
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 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 08:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy