Extended vs vintage


Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Extended vs vintage
# 1  
Extended vs vintage

I am having issues with the MOS (my oracle support) page. I downloaded the new critical patch and oct patchset. for solaris 10 64. However, I noticed that that the Entitlement class read vintage instead of extended in which we bought the service.

can anyone tell me the difference? it is safe and correct to install the vintage ? in my reading I could not find the answer.


thanks
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #546
Difficulty: Medium
In computer science, an operator takes the values of its operands and combines them in some way to produce a new value.
True or False?

8 More Discussions You Might Find Interesting

1. What is on Your Mind?

Vintage!!! Jimmy Page/Jeff Beck/Eric Clapton-Stairway to Heaven

You must watch this music video. Jimmy Page/Jeff Beck/Eric Clapton-Stairway to Heaven https://youtu.be/wKlEVtA_TGQ Long before there was surveillance capitalism, Google, FB and dystopian social media, there was Jimmy Page! This is how it all "used to be" before mankind was reduced to... (0 Replies)
Discussion started by: Neo
0 Replies

2. What is on Your Mind?

Anyone Running Vintage UNIXen?

Like SunOS, AT&T Unix or anything else of that era... anything running MGR as a graphics subsystem? I'd enjoy hearing from people that may have used MGR back in the day. I have something of a collection of 32bit Suns sun4c, sun4m, sun4d etc..nothing bigger than an 8 way 85Mhz SS1000E though. The... (0 Replies)
Discussion started by: cb88
0 Replies

3. AIX

Printing extended ASCII

Hi All, I'm trying to send extended ascii characters to my HP2055 as part of PCL printer control codes. What I want to do is select a bar code font, print the bar code and reset the printer to the default font. Selecting the bar code font works good. Printing the bar code goes almost ok too. ... (5 Replies)
Discussion started by: petervg
5 Replies

4. UNIX Desktop Questions & Answers

Vintage unix

Hi, this my be a weird request but I'm wondering if it's possible to instill a vintage unix (like early 1980's) onto a laptop or desktop. If so how I would I go about downloading and installing? I'm mainly wanting to do this as an little porject and some funsies for me. Thanks. (11 Replies)
Discussion started by: dado00
11 Replies

5. Shell Programming and Scripting

extended characters in UNIX

Hi Guys, I am using db2 load to load from a csv file to a table. Problem is that extended characters ,,, do not get loaded correctly. Its a UTF 8 format csv and i am using codepage=1208 for the load. Does anybody have an idea on this? Thanks (2 Replies)
Discussion started by: lifzgud
2 Replies

6. Filesystems, Disks and Memory

How to mount and read vintage scsi HDD

I started on another thread and full story can be seen here: https://www.unix.com/security/91428-how-reset-root-password-old-unix-system-v.html But my situation turned to land on this thread now. I have old scsi HDD out of the UHC UNIX System V Rel. 4.0 Version 3.6 box. And need to read... (1 Reply)
Discussion started by: 82026
1 Replies

7. Programming

Extended ascii

Hi all, I would like to change the extended ascii code ( 128 - 255). I tried to change LC_ALL and LANG in current session ( values from locale -a) and for no good. Thanks. (0 Replies)
Discussion started by: avis
0 Replies

8. Programming

about extended memory

Hello Reders In my system i have an extended memory of 129024 k.b which is 126 M.B when i click the system properties i use to get 129520 K.B where does the remainng 484 k.b comes from? apart from extended memory shadow ram 384 k.b basemmemory 640 k cahe ram 256 k my question what... (1 Reply)
Discussion started by: rajashekaran
1 Replies
cvsps(1)						      General Commands Manual							  cvsps(1)

NAME
CVSps - create patchset information from CVS SYNOPSIS
cvsps [-h] [-x] [-u] [-z <fuzz>] [-g] [-s <patchset>] [-a <author>] [-f <file>] [-d <date1> [-d <date2>]] [-l <text>] [-b <branch>] [-r <tag> [-r <tag>]] [-p <directory>] [-v] [-t] [--norc] [--summary-first] [--test-log <filename>] [--bkcvs] [--no-rlog] [--diff-opts <option string>] [--cvs-direct] [--debuglvl <bitmask>] [-Z <compression>] [--root <cvsroot>] [-q] [-A] [<repository>] DESCRIPTION
CVSps is a program for generating 'patchset' information from a CVS repository. A patchset in this case is defined as a set of changes made to a collection of files, and all committed at the same time (using a single 'cvs commit' command). This information is valuable to seeing the big picture of the evolution of a cvs project. While cvs tracks revision information, it is often difficult to see what changes were committed 'atomically' to the repository. OPTIONS
-h display usage summary -x ignore (and rebuild) ~/.cvsps/cvsps.cache file -u update ~/.cvsps/cvsps.cache file -z <fuzz> set the timestamp fuzz factor for identifying patch sets -g generate diffs of the selected patch sets -s <patchset>[-[<patchset>]][,<patchset>...] generate a diff for a given patchsets and patchset ranges -a <author> restrict output to patchsets created by author -f <file> restrict output to patchsets involving file -d <date1> -d <date2> if just one date specified, show revisions newer than date1. If two dates specified, show revisions between two dates. -l <regex> restrict output to patchsets matching regex in log message -b <branch> restrict output to patchsets affecting history of branch. If you want to restrict to the main branch, use a branch of 'HEAD'. -r <tag1> -r <tag2> if just one tag specified, show revisions since tag1. If two tags specified, show revisions between the two tags. -p <dir> output individual patchsets as files in <dir> as <dir>/<patchset>.patch -v show very verbose parsing messages -t show some brief memory usage statistics --norc when invoking cvs, ignore the .cvsrc file --summary-first when multiple patchset diffs are being generated, put the patchset summary for all patchsets at the beginning of the output. --test-log <captured cvs log file> for testing changes, you can capture cvs log output, then test against this captured file instead of hammering some poor CVS server --bkcvs (see note below) for use in parsing the BK->CVS tree log formats only. This enables some hacks which are not generally applicable. --no-rlog disable the use of rlog internally. Note: rlog is required for stable PatchSet numbering. Use with care. --diff-opts <option string> send a custom set of options to diff, for example to increase the number of context lines, or change the diff format. --cvs-direct (--no-cvs-direct) enable (disable) built-in cvs client code. This enables the 'pipelining' of multiple requests over a single client, reducing the overhead of handshaking and authentication to one per PatchSet instead of one per file. --debuglvl <bitmask> enable various debug output channels. -Z <compression> A value 1-9 which specifies amount of compression. A value of 0 disables compression. --root <cvsroot> Override the setting of CVSROOT (overrides working dir. and environment). For --cvs-direct only. -q Be quiet about warnings. -A Show ancestor branch when a new branch is found. <repository> Operate on the specified repository (overrides working dir.) NOTE ON TAG HANDLING
Tags are fundamentally 'file at a time' in cvs, but like everything else, it would be nice to imagine that they are 'repository at a time.' The approach cvsps takes is that a tag is assigned to a patchset. The meaning of this is that after this patchset, every revision of every file is after the tag (and conversely, before this patchset, at least one file is still before the tag). However, there are two kinds of inconsistent (or 'funky') tags that can be created, even when following best practices for cvs. The first is what is called a FUNKY tag. A funky tag is one where there are patchsets which are chronologically (and thus by patchset id) earlier than the tag, but are tagwise after. These tags will be marked as '**FUNKY**' in the Tag: section of the cvsps output. When a funky tag is specified as one of the '-r' arguments, there are some number of patchsets which need to be considered out of sequence. In this case, the patchsets themselves will be labeled FUNKY and will be processed correctly. The second is called an INVALID tag. An invalid tag is a tag where there are patchsets which are chronologically (and thus by patchset id) earlier than the tag, but which have members which are tagwise both before, and after the tag, in the same patchset. If an INVALID tag is specified as one of the '-r' arguments, cvsps will flag each member of the affected patchsets as before or after the tag and the patchset summary will indicate which members are which, and diffs will be generated accordingly. NOTE ON CVS VERSIONS
Among the different cvs subcommands used by cvsps is the 'rlog' command. The rlog command is used to get revision history of a module, and it disregards the current working directory. The important difference between 'rlog' and 'log' (from cvsps perspective) is the 'rlog' will include log data for files not in the current working directory. The impact of this is mainly when there are directories which at one time had files, but are now empty, and have been pruned from the working directory with the '-P' option. If 'rlog' is not used, these files logs will not be parsed, and the PatchSet numbering will be unstable. The main problem with 'rlog' is that, until cvs version 1.11.1, 'rlog' was an alias for the 'log' command. This means, for old versions of cvs, 'rlog' has different semantics and usage. cvsps will attempt to work around this problem by detecting capable versions of cvs. If an old version is detected, 'log' will be used instead of 'rlog', and YMMV. NOTE ON GENERATED DIFFS
Another important note is that cvsps will attempt, whenever possible, to use the r-commands (rlog, rdiff and co) instead of the local com- mands (log, diff, and update). This is to allow cvsps to function without a completely checked out tree. Because these r-commands are used, the generated diffs will include the module directory in them, and it is recommended to apply them in the working directory with the -p1 option to the patch command. However, if the --diff-opts option is specified (to change, for example, the lines of context), then rdiff cannot be used, because it doesn't support arbitrary options. In this case, the patches will be generated without the module direc- tory in the path, and -p0 will be required when applying the patch. When diffs are generated in cvs-direct mode (see below), however, they will always be -p1 style patches. NOTE ON BKCVS
The --bkcvs option is a special operating mode that should only be used when parsing the log files from the BK -> CVS exported linux kernel trees. cvsps uses special semantics for recreating the BK ChangeSet metadata that has been embedded in the log files for those trees. The --bkcvs option should only be specified when the cache file is being created or updated (i.e. initial run of cvsps, or when -u and -x options are used). NOTE ON CVS-DIRECT As of version 2.0b6 cvsps has a partial implementation of the cvs client code built in. This reduces the RTT and/or handshaking overhead from one per patchset member to one per patchset. This dramatically increases the speed of generating diffs over a slow link, and improves the consistency of operation. Currently the --cvs-direct option turns on the use of this code, but it very well may be default by the time 2.0 comes out. The built-in cvs code attempts to be compatible with cvs, but may have problems, which should be reported. It honors the CVS_RSH and CVS_SERVER environment variables, but does not parse the ~/.cvsrc file. NOTE ON CVSPS RC FILE
CVSps parses an rc file at startup. This file should be located in ~/.cvsps/cvspsrc. The file should contain arguments, in the exact syn- tax as the command line, one per line. If an argument takes a parameter, the parameter should be on the same line as the argument. NOTE ON DATE FORMATS
All dates are reported in localtime. This can be overridden (as usual) using the TZ environment variable. Dates as arguments must be in the format 'yyyy/mm/dd hh:mm:ss'; for example, $ cvsps -d '2004/05/01 00:00:00' -d '2004/07/07 12:00:00' SEE ALSO
cvs(1), ci(1), co(1), cvs(5), cvsbug(8), diff(1), grep(1), patch(1), rcs(1), rcsdiff(1), rcsmerge(1), rlog(1). REPORTING BUGS
Report bugs to "David Mansfield <cvsps@dm.cobite.com>" BUGS
No known bugs. cvsps(1)

Featured Tech Videos