-------- Original Message -------- Subject: Re: [Fwd: EOF SYSV3 SCO compatibility environment variable [PSARC/2010/233 FastTrack timeout 06/30/2010]] Date: Tue, 29 Jun 2010 07:52:30 -0700 From: Rich Burridge created by mike.doherty@oracle.com 2010-June-28 updated by mike.doherty@oarcle.com 2010-July-01 ---------------------------------------------------------------- ORACLE PROPRIETARY/CONFIDENTIAL: Internal Use Only Project/feature name: EOF SYSV3 SCO compatibility environment variable Engineering representative: Rich Burridge Marketing representative: Dan Roberts. C-Team removing the feature: ON EOF Application for (check one and provide the indented information): [X] EOF Announcement Release proposed for "notice of intent" publication: Solaris 11 (beta) Proposed final release of functionality: snv_146 Date for ARC Review: PSARC fast-track: June 23rd - July 1st 2010. [X] Feature Removal (Actual EOF) Actual initial release in which "notice of intent" was published: Solaris 11 (beta). Proposed final release of functionality: Solaris 11 ARC, Case # for EOF, and Case Disposition: PSARC 2010/233 - fast-track approved 30th June 2010. Is the proposed removal date the same date which the ARC approved? YES Have all TCRs in the ARC opinion been completed? N/A. What will be replacing this functionality? - backup information should include pointers to one-pagers or draft boundary conditions for projects , and the dates scheduled for their review Nothing. The functionality that is being removed is considered to no longer be required. Business case for removal: - backup information includes sales reports, market changes, organizational reasons for change, etc This is being done as part of the Bleaklow project; an on-going effort to make the user commands and libraries in Solaris, comparible to modern operating systems. To that extent, old irrelevant functionality is being removed for ease of maintainence. Transition/Migration plan: - What type of transition? (Flag day, migration, compatible upgrade, etc) As the functionality is just being removed (and not replaced), there is no transition plan other than the announcement itself. - Timeline for plan N/A. - Backup information should include a list of considerations for transition alternatives being evaluated, etc. N/A. Are there any hardware support implications? No. If so, have you worked with Systems Products to evaluate SMI hardware impact? N/A. Are there any software dependency implications, e.g. impacts to other C-Teams or projects? None that we are aware of. Due diligence included a check of the latest ON, SFW, X and JDS workspaces to ensure that the SYSV3 environment variable wasn't being used. If so, who from those dependent groups has been notified? What is the plan to resolve any issues resulting from those dependencies? N/A. Has there been any negative field reaction to this proposal? No. If so, what is the plan for dealing with that? N/A. Once removed, can the source for this feature be given to any customer who requests it? Yes. The source code for this feature is already generally available as part of the OpenSolaris open source project. Are there any brand, trademark, or standards compliance implications? No. Proposed text of EOF statement for release notes: - For guidelines and samples, see http://releaseme.eng/eos_guidelines.html Features Removed From the Solaris 11 Operating Environment Various SCO compatibility options. df - support of the SYSV3 environment variable has been removed. If set, this provided different default output for and the output of the "-t" option, or when the "-e" and "-b" options are used together. echo - support of the SYSV3 environment variable has been removed. If set, this provided SCO style -n option parsing. expr - Three new options were added to this command to provide SCO compatibility: len string Return the length (eg. number of characters) of string. index str charlist Report the first position in string at which any of the characters in charlist matches a character in str. substr str start len Extract the substring of str starting at start with a length of len. This functionality is present in the GNU expr command, and will now be made available to x86 and SPARC users without needing the SYSV3 environment variable set. sh - support of the SYSV3 environment variable has been removed from the echo sub-command. If set, this provided SCO style -n option parsing. tar - The following three options will be removed: -e Prevents files from being split across volumes. If there is not enough room on a volume, tar prompts for a new volume. This differs from standard Solaris behavior. -k Cause tar to use the next arg as the size of an archive in kilobytes. This is useful when the archive is intended for a fixed size device such as floppy disk. Large files are then split across volumes. This option used to be in Solaris but was removed because it isn't defined in SVID. -q Stop after extracting the first occurance of the named files. This option is a performance enhancement to enable the system administration tool to run much faster. The issue was that tar normally continues to read the entire volume even after it has found the desired file (there may be a second occurance of the file in the tar file so it keeps reading until finished). (Note that this functionality was never implemented, even though tar accepted the command line option.) The following option will be modified to remove the functionality that was present when SYSV3 was set: -F read command line switches from a specified file (name in next argument). This differs from standard Solaris behavior. The current behaviour of the -F flag when SYSV3 is unset is as follows: -F With one F argument, tar excludes all directories named SCCS and RCS from the tarfile. With two arguments, FF, tar excludes all directories named SCCS and RCS, all files with .o as their suffix, and all files named errs, core, and a.out. This behaviour will be unaltered. The following option (which is also present in GNU tar), will be available to both x86 and SPARC users without having to set the SYSV3 environment variable: -n the file being read is a non-tape device so listing and extracting files is sped since tar can seek over files it wishes to skip. This had been in Solaris but was removed because it isn't defined in SVID. uname - support of the SYSV3 environment variable has been removed. If set, this provided different output. Setting SYSV3 to an empty string made uname print the following default values: nodename nodename 3.2 2 i386 The individual elements that uname displayed could also be modified by setting SYSV3 in the following format: os,sysname,node,rel,ver,mach os Operating system (IUS or SCO). sysname System name. node Nodename as displayed by the -n option. rel Release level as displayed by the -r option. ver Version number as displayed by the -v option. mach Machine name as displayed by -m option. Do not put spaces between the elements. If an element is omitted, the current system value will be used. Proposed text of EOF statement for other documents, such as manpages (if applicable): See the man-page-changes.txt file submitted as part of the PSARC case: /net/sac/export/sac/PSARC/2010/233/materials/man-page-changes.txt http://sac.eng/arc/PSARC/2010/233/materials/man-page-changes.txt Is this feature applicable to SPARC [XX]. x86[XX] Which interface commitment level (see http://solaris.eng/SOE/Solaris-PAC/policies/eof.html): i.e. support for hardware, Standard,.... Evolving.