Sponsored Content
Full Discussion: two computers one internet
Special Forums IP Networking two computers one internet Post 77967 by dragos on Thursday 14th of July 2005 08:41:51 AM
Old 07-14-2005
how?...sory but i'm beginer
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

two computers - one modem

I have two mashines with RedHat 8.0......they connected with cross over cabel...I want use both mashines for Internet, but modem has only first computer... Maybe..through gateway ?.... What must i do for it ?...... sorry for my terrible english.... (3 Replies)
Discussion started by: Pennywize
3 Replies

2. UNIX for Advanced & Expert Users

Using other computers for processing

Hello I've wrote a C++ program which does some mathematical calculations, but the problem is that it takes way too long on any computer to finish. Is there anyway to make more than 1 computer do the processing so it can process faster? (5 Replies)
Discussion started by: arya6000
5 Replies

3. What is on Your Mind?

How Many Computers Do You Have At Home?

Here is an easy one. Count the number of desktops and servers you have running at home, including your home office if you have one. Don't count those that are in storage or you rarely use, count the ones that are powered on most, if not all, of the day (and night). (86 Replies)
Discussion started by: Neo
86 Replies

4. Linux

SFTP an internet address from a system behind an internet proxy

I was wondering if it is possible to setup SFTP to go through the internet proxy while connecting to an internet location. Problem: Client system is behind internet proxy. SFTP to any internet location fails as there is no documented way to configure SFTP to connect to internet locations through... (4 Replies)
Discussion started by: toobrown1
4 Replies

5. Homework & Coursework Questions

Track availability of computers

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: I must write a program that records the availability of computers. For the argument i have to give him a file... (4 Replies)
Discussion started by: petel1
4 Replies

6. IP Networking

Problem in eth0 and eth1 sharing internet with other computers

hellow everbody. iam using 32 bit centos 6.2 on my desktop and iam new to linux. i have eth0 and eth1 on my desktop. so i have some problems i have menson here: i have edited: etc/sysctl.conf net.ipv4.ip_forward = 1 and i have edited iptables too # iptables -t nat -A... (2 Replies)
Discussion started by: paruhang
2 Replies

7. Solaris

Rcp between 2 computers

Hi, I need to rcp heavy files between 2 solaris 10/sparc M3000 computers. Currently theses 2 computers are linked via a switch/firewall and the rcp commands take a very long time, I have been told that this is because of the firewall (old one). I asked my client to by a cross ethernet cable and... (2 Replies)
Discussion started by: zionassedo
2 Replies
sccs-get(1)							   User Commands						       sccs-get(1)

NAME
sccs-get, get - retrieve a version of an SCCS file SYNOPSIS
/usr/bin/get [-begkmnpst] [-l [p]] [-asequence] [-c date-time | -cdate-time] [-Gg-file] [-i sid-list | -isid-list] [-r [sid]] [-x sid-list | -xsid-list] s.filename... /usr/xpg4/bin/get [-begkmnpst] [-l [p]] [-asequence] [-c date-time | -cdate-time] [-Gg-file] [-i sid-list | -isid-list] [-r sid | -rsid] [-x sid-list | -xsid-list] s.filename... DESCRIPTION
The get utility retrieves a working copy from the SCCS history file, according to the specified options. For each s.filename argument, get displays the SCCS delta ID (SID) and number of lines retrieved. If a directory name is used in place of the s.filename argument, the get command applies to all s.files in that directory. Unreadable s.files produce an error; processing continues with the next file (if any). The use of `-' as the s.filename argument indicates that the names of files are to be read from the standard input, one s.file per line. The retrieved file normally has the same filename base as the s.file, less the prefix, and is referred to as the g-file. For each file processed, get responds (on the standard output) with the SID being accessed, and with the number of lines retrieved from the s.file. OPTIONS
The following options are supported: -asequence Retrieves the version corresponding to the indicated delta sequence number. This option is used primarily by the SCCS comb command (see sccs-comb(1)). For users, -r is an easier way to specify a version. The -a option supersedes the -r option when both are used. -b Creates a new branch. Used with the -e option to indicate that the new delta should have a SID in a new branch. Instead of incrementing the level for version to be checked in, get indicates in the p.file that the delta to be checked in should either initialize a new branch and sequence (if there is no existing branch at the current level), or increment the branch component of the SID. If the b flag is not set in the s.file, this option is ignored. -c date-time | -cdate-time Retrieves the latest version checked in prior to the date and time indicated by the date-time argument. date- time takes the form: yy[mm[dd[ hh[mm[ss]]]]] Units omitted from the indicated date and time default to their maximum possible values; that is -c7502 is equivalent to -c750228235959. Values of yy in the range 69-99 refer to the twentieth century. Values in the range 00-68 refer to the twenty-first century. Any number of non-numeric characters can separate the various 2 digit components. If white-space characters occur, the date-time specification must be quoted. -e Retrieves a version for editing. With this option, get places a lock on the s.file, so that no one else can check in changes to the version you have checked out. If the j flag is set in the s.file, the lock is advi- sory: get issues a warning message. Concurrent use of `get -e' for different SIDs is allowed. However, get does not check out a version of the file if a writable version is present in the directory. All SCCS file protections stored in the s.file, including the release ceiling, floor, and authorized user list, are honored by `get -e'. -g Gets the SCCS version ID, without retrieving the version itself. Used to verify the existence of a particular SID. -Gnewname Uses newname as the name of the retrieved version. -i sid-list | -isid-list Specifies a list of deltas to include in the retrieved version. The included deltas are noted in the standard output message. sid-list is a comma-separated list of SIDs. To specify a range of deltas, use a `-' separa- tor instead of a comma, between two SIDs in the list. -k Suppresses expansion of ID keywords. -k is implied by the -e. -l[p] Retrieves a summary of the delta table (version log) and write it to a listing file, with the `l.' prefix (called `l.file'). When -lp is used, write the summary onto the standard output. -m Precedes each retrieved line with the SID of the delta in which it was added to the file. The SID is sepa- rated from the line with a TAB. -n Precedes each line with the %M% ID keyword and a TAB. When both the -m and -n options are used, the ID key- word precedes the SID, and the line of text. -p Writes the text of the retrieved version to the standard output. All messages that normally go to the stan- dard output are written to the standard error instead. -s Suppresses all output normally written on the standard output. However, fatal error messages (which always go to the standard error) remain unaffected. -t Retrieves the most recently created (top) delta in a given release (for example: -r1). /usr/bin/get -r[sid] Retrieves the version corresponding to the indicated SID (delta). The SID for a given delta is a number, in Dewey decimal format, composed of two or four fields: the release and level fields, and for branch deltas, the branch and sequence fields. For instance, if 1.2 is the SID, 1 is the release, and 2 is the level number. If 1.2.3.4 is the SID, 3 is the branch and 4 is the sequence number. You need not specify the entire SID to retrieve a version with get. When you omit -r altogether, or when you omit both release and level, get normally retrieves the highest release and level. If the d flag is set to an SID in the s.file and you omit the SID, get retrieves the default version indicated by that flag. When you specify a release but omit the level, get retrieves the highest level in that release. If that release does not exist, get retrieves highest level from the next-highest existing release. Similarly with branches, if you specify a release, level and branch, get retrieves the highest sequence in that branch. /usr/xpg4/bin/get -r sid | -rsid Same as for /usr/bin/get except that SID is mandatory. -x sid-list | -xsid-list Excludes the indicated deltas from the retrieved version. The excluded deltas are noted in the standard output message. sid-list is a comma-separated list of SIDs. To specify a range of deltas, use a `-' separator instead of a comma, between two SIDs in the list. OUTPUT
/usr/bin/get The output format for /usr/bin/get is as follows: "%%s %%d lines ", <SID>, <number of lines> /usr/xpg4/bin/get The output format for /usr/xpg4/bin/get is as follows: "%%s %%d ", <SID>, <number of lines> USAGE
Usage guidelines are as follows: ID Keywords In the absence of -e or -k, get expands the following ID keywords by replacing them with the indicated values in the text of the retrieved source. +---------+-------------------------------------------------+ |Keyword | Value | +---------+-------------------------------------------------+ |%%A%% | Shorthand notation for an ID line with data | | | for what(1): %%Z%%Y% %M% %I%%Z% | +---------+-------------------------------------------------+ |%B% | SID branch component | +---------+-------------------------------------------------+ |%C% | Current line number. Intended for identifying | | | messages output by the program such as ``this | | | shouldn't have happened'' type errors. It is | | | not intended to be used on every line to pro- | | | vide sequence numbers. | +---------+-------------------------------------------------+ |%D% | Current date: yy/mm/dd | +---------+-------------------------------------------------+ |%E% | Date newest applied delta was created: yy/mm/dd | +---------+-------------------------------------------------+ |%F% | SCCS s.file name | +---------+-------------------------------------------------+ |%G% | Date newest applied delta was created: mm/dd/yy | +---------+-------------------------------------------------+ |%H% | Current date: mm/dd/yy | +---------+-------------------------------------------------+ |%I% | SID of the retrieved version: %R%.%L%.%B%.%S% | +---------+-------------------------------------------------+ |%% | SID level component | +---------+-------------------------------------------------+ |%M% | Module name: either the value of the m flag in | | | the s.file (see sccs-admin(1)), or the name of | | | the s.file less the prefix | +---------+-------------------------------------------------+ |%P% | Fully qualified s.file name | +---------+-------------------------------------------------+ |%Q% | Value of the q flag in the s.file | +---------+-------------------------------------------------+ |%R% | SID Release component | +---------+-------------------------------------------------+ |%S% | SID Sequence component | +---------+-------------------------------------------------+ |%T% | Current time: hh:mm:ss | +---------+-------------------------------------------------+ |%U% | Time the newest applied delta was created: | | | hh:mm:ss | +---------+-------------------------------------------------+ |%W% | Shorthand notation for an ID line with data for | | | what: %Z%%&;% %I% | +---------+-------------------------------------------------+ |%Y% | Module type: value of the t flag in the s.file | +---------+-------------------------------------------------+ |%Z% | 4-character string: `@(#)', recognized by what | +---------+-------------------------------------------------+ ID String The table below explains how the SCCS identification string is determined for retrieving and creating deltas. +-------------------+--------------------+-----------------------------+---------------+----------------------------+ |Determination of | | | | | |SCCS Identifica- | | | | | |tion String | | | | | +-------------------+--------------------+-----------------------------+---------------+----------------------------+ |SID (1) Specified | -b Option Used (2) | Other Conditions | SID Retrieved | SID of Delta to be Created | +-------------------+--------------------+-----------------------------+---------------+----------------------------+ | none (3) | no | R defaults to mR | mR.mL | mR.(mL+1) | | none (3) | yes | R defaults to mR | mR.mL | mR.mL.(mB+1).1 | | R | no | R > mR | mR.mL | R.1 (4) | | R | no | R = mR | mR.mL | mR.(mL+1) | | R | yes | R > mR | mR.mL | mR.mL.(mB+1).1 | | R | yes | R = mR | mR.mL | mR.mL.(mB+1).1 | | R | - | R < mR and R does not exist | hR.mL (5) | hR.mL.(mB+1).1 | | R | - | Trunk succ. (6) in release | R.mL | R.mL.(mB+1).1 | | | | > R and R exists | | | | R.L | no | No trunk succ. | R.L | R.(L+1) | | R.L | yes | No trunk succ. | R.L | R.L.(mB+1).1 | | R.L | - | Trunk succ. in release >= R | R.L | R.L.(mB+1).1 | | R.L.B | no | No branch succ. | R.L.B.mS | R.L.B.(mS+1) | | R.L.B | yes | No branch succ. | R.L.B.mS | R.L.(mB+1).1 | | R.L.B.S | no | No branch succ. | R.L.B.S | R.L.B.(S+1) | | R.L.B.S | yes | No branch succ. | R.L.B.S | R.L.(mB+1).1 | | R.L.B.S | - | Branch succ. | R.L.B.S | R.L.(mB+1).1 | +-------------------+--------------------+-----------------------------+---------------+----------------------------+ (1) `R', `L', `B', and `S' are the `release', `level', `branch', and `sequence' components of the SID, respectively; `m' means `maxi- mum'. Thus, for example, `R.mL' means `the maximum level number within release R'; `R.L.(mB+1).1' means `the first sequence number on the new branch (that is, maximum branch number plus one) of level L within release R'. Note: If the SID specified is of the form `R.L', `R.L.B', or `R.L.B.S', each of the specified components must exist. (2) The -b option is effective only if the b flag is present in the file. An entry of `-' means `irrelevant'. (3) This case applies if the d (default SID) flag is not present in the file. If the d flag is present in the file, the SID obtained from the d flag is interpreted as if it had been specified on the command line. Thus, one of the other cases in this table applies. (4) Forces creation of the first delta in a new release. (5) `hR' is the highest existing release that is lower than the specified, nonexistent, release R. (6) Successor. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of get: LANG, LC_ALL, LC_COLLATE, LC_CTYPE, LC_MESSAGES, and NLSPATH. FILES
``g-file'' version retrieved by get l.file file containing extracted delta table info p.file permissions (lock) file z.file temporary copy of s.file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: /usr/bin/get +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsprot | +-----------------------------+-----------------------------+ /usr/xpg4/bin/get +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWxcu4t | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
sccs(1), sccs-admin(1), sccs-delta(1), sccs-help(1), sccs-prs(1), sccs-prt(1), sccs-sact(1), sccs-unget(1), what(1), sccsfile(4), attributes(5), environ(5), standards(5) DIAGNOSTICS
Use the SCCS help command for explanations (see sccs-help(1)). BUGS
If the effective user has write permission (either explicitly or implicitly) in the directory containing the SCCS files, but the real user does not, only one file can be named when using -e. SunOS 5.11 2 Jul 2007 sccs-get(1)
All times are GMT -4. The time now is 09:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy