Unix wonderful quiz _unix Linux

One: This article answers to the following questions:

1.1 Who will help you to make this FAQ?
1.2 When someone mentions ' RN (1) ' or ' CTime (3) ', what does the number in the scraping mean?
1.3 What is the origin of some strange unix instruction names?
1.4) How does the gateway between "comp.unix.questions" and "info-unix" mailing list work?
1.5 Please suggest some useful Unix, C related books.
1.6 Before the pronunciation table in this FAQ?


1.1 Who will help you to make this FAQ?

This document was one of the first several FAQs, compiled in July 1989. Almost all the editorial work was done by Steve Hayman. I'm just taking over the maintenance of this document.

We are very grateful to the Usenet readers for their questions, reactions, corrections and suggestions.

Special thanks to Maarten Litmaath, Guy Harris and Jonathan Kamens, they all contributed a lot.

The 5th part of the document (shells) was written almost entirely by Matthew wicks<wicks@dcdmjw.fnal.gov>.

The 6th part of this file (various Unix) is almost entirely Pierre (P.) Lewis<lew@bnr.ca> wrote it.

I try to put the author of each problem and the date of the last update on the beginning of the problem. Unfortunately, because I have only recently begun to do so, a lot of information has been lost. I also neglect to save to ask
A list of those who supplement the latest information. Apologies to those who have contributed and have not been duly honoured.

I converted this file into *roff format (MS and MM two macro are available). Andrewcromarty converts it to the Texinfo format. These formatted versions are available by the anonymous
FTP was obtained in the Pub/unix-faq/docs of _blank>ftp.wg.omron.co.jp.


1.2 When someone mentions ' RN (1) ' or ' CTime (3) ', what does the number in the scraping mean?

Looks like a function call, but it's not. These numbers refer to the section in the Unix manual where the files are located. When you hit "Man 3 CTime", it means to refer to the
The contents of CTime in section 3.

Section method for traditional Unix manuals:

1 User-level commands
2 System Calls
3 Library functions
4 Devices and device drivers
5 File formats
6 Games
7 various miscellaneous Stuff-macro packages etc.
8 System Maintenance and Operation commands

Some Unix versions use Non-numeric chapter names. For example, Xenix's instructions use "C" and Function "S". Some newer versions of Unix have to be "man-s# title" and
Not "Man # title". Each section has an introduction to # representing the number of sections, and "Man # Intro" can be read in section # of the introduction.

Sometimes it is necessary to distinguish between an instruction and a regular or system call number of the same name. For example, your system may have "time (1)", which is about the timing of the measurement.
, there is also "time (3)", a description of the deputy used to determine the current period. You can use "Man 1" or "Man 3 time" to choose what to see
A description of "time".

Perhaps your system will have other chapters or subdivision chapters (subsection), like Ultrix 3m, 3n, 3x and 3yp.


1.3 The origin of some strange UNIX instruction names

awk = "Aho Weinberger and Kernighan"

The language is named after the surname of the author Al Aho, Peter Weinberger and Brian Kernighan.

grep = "Global Regular Expression Print"

grep from Ed print all conforms to a certain pattern instruction

g/re/p

"Re" represents regular expression

Fgrep = "Fixed GREP".

fgrep-find a fixed string. "F" does not represent "fast"-in fact, "Fgrep foobar *.c" is usually slower than "Egrep foobar *.c" (a bit of a surprise.
, try it yourself).
However, Fgrep still has the merit of searching for strings in the file, Fgrep can handle more strings than egrep.

Egrep = "Extended GREP"

Egrep with regular rexpression more fancy than grep. Many people always use only egrep, because it uses algorithm than grep or fgrep used for advanced, and
and is usually the fastest in three programs.

Cat = "Catenate"

Catenate is a difficult word, meaning "connect it to a string", which is what the "cat" command does with one or more files.

Please do not confuse with C/A/T, C/A/T refers to the computer-aided typesetting system (Computer aided Typesetter).

Gecos = "General Electric comprehensive operating supervisor"

However, when the large system department of General Electric (GE) sold to Honeywell, Honeywell took away GECOS's E.

The current Unix password file still retains the "Pw_gecos" field. The name is from the early years of the old.

Dennis Ritchie once said:

"Sometimes we throw out print sheets or whole batches of work to the GCOS machine. The GCOS field in the cipher file is used to hide the information on $IDENT card, which is not elegant enough.


Nroff = "New Roff"
Troff = "Typesetter new Roff"

These words are derived from "Roff", Roff rewrite the runoff program on the Multics (runoff means "print the file").

Tee = T

This is the term for the pipeline worker, representing the T-type pipeline fork.

BSS = "Block started by symbol" (blocks starting with symbols)

Dennis Ritchie once said:

This abbreviation may have other arguments, but the fact that we use this abbreviation is meant "block started by Symbol". It is a virtual instruction on FAP, FAP (Fortran
Assembly [-er?] Program) refers to the IBM 704-709-7090-7094 this model of the group translation device. This instruction defines its own label and reserves a certain number of space for the word group.
There is also another virtual instruction BES, "block Ended by Symbol", which is almost the same as the BSS instruction, except that the label is defined at the address of the end of the reserved word Group + 1
Place. On these machines, the Fortran array is stored in reverse direction, and the array index is counted from 1.

This usage is reasonable because, like the standard loader on UNIX, code does not actually put this whole block of reserved space, but first it is expressed in a number that is loaded
To really set aside the necessary space.

Biff = "Biff"

This instruction is used to set whether you want to be notified when new mail comes in. This is the name of a dog on the campus of the University of Berkeley.

I can determine the origin of this name, if you are interested, Biff is Heidi Stettner pet, think Heidi (and I, and Bill Joy) are still UCB
In grad school, the early BSD version was still in development. Biff is loved by those who linger in Evans ' Halls, and because it is known for the bark of the postman coming;
The name of the instruction as Biff. (This is confirmed by Eric Cooper of Kanekime University)

RC (like ". CSHRC" or "/ETC/RC" in the two letters) = "Runcom"

"RC" is taken from "runcom", a CTSS system developed by MIT in 1965. The relevant literature has documented this passage: ' Having taken a series of commands out of the archives to hold
The function of the line; this is called "Run Commands" also known as "runcom", and this file is also called a runcom (a runcom). '

Brian Kernighan and Dennis Ritchie told Vicki Brown, "RC" is also the name of the Plan 9 operating system shell.



Perl = "Practical extraction and Language"
Perl = "pathologically eclectic rubbish Lister"

Perl is a very popular language developed by Larry Wall, and Perl is handy when it comes to writing, process, and archives, which can be said to be both shell and C. Think
For more information on Perl, see Usenet newsgroup comp.lang.perl.

There are more of these tidbit anecdotes in Don Libes's "Life with Unix" book.


1.4) How does the gateway between "comp.unix.questions" and "info-unix" mailing list work?

"Info-unix" and "Unix-wizards" are mailing-list editions of Comp.unix.questions and Comp.unix.wizards respectively. Mailing list and
The contents of the newsgroup should be the same

To join or exit any mailing list, please send email to info-unix-quest@brl.mil or unix-wizards-request@brl.mil. Remember to join or exit
Mailing list is given to "*-request@brl.mil". Please wait patiently because there will be no immediate response.

Below is the detailed details of the mailing list provided by the maintainer of mailing list, Bob reschly.

= = Postings to Info-unix and unix-wizards lists = =

I personally do not control what is sent to the mailing list, and any letters sent to this mailing list will be posted to the corresponding news group. BRL is merely a mere diversion.
Internet users on this mailing list should send articles to newgroup when sent to Info-unix or unix-wizards, '-request ' is the letter to be sent
To the defenders of mailing list.

Internet users on this mailing list receive two types of messages, one for a single discussion article, and one for a collection of abstracts of several discussion highlights. From
Messages sent to BRL by the Internet or bitnet (through the bitnet←→internet Converter) are forwarded to each of the users in the mail list.


Articles sent from USENET are sent to all members of the mailing list in the form of a daily remittance. Bitnet's network traffic is very similar to Internet traffic.
The main difference is that for all the bitnet recipients in the mailing list, I just need to maintain an email address where the recipient of this address maintains all the pieces.
Information, and automatically forwarding all articles to each Subscriber on the mailing list.

Subscribers on the USENET will only read their own separate messages, all messages from the Internet are forwarded to our machine on the USENET and posted to the appropriate discussion area.
Unfortunately, these articles posted through the conversion program, the sender will become news@brl-adm, this is the conversion software has not yet resolved the inherent limitations.

As for readership, USENET is a place with a broad readership, and I estimate that about thousands of hosts and tens of thousands of users are involved in usetnet. The main list about which BRL maintains
There are 250, about 10% of which are local forwarding list. I'm not quite sure about the number of bitnet, but if I had to guess, the number would be about the same as the main list. The average of a list in one weeks to send out 150K to 400K of information.


1.5 Please suggest some useful Unix, C related books.

Mitch Wright (mitch@cirrus.com) maintains a list of Unix and C-related books containing briefs and essays. There are currently 167 ftp.rahul.net on his watch.
(192.160.13.1) The "Pub/mitch/yabl/yabl" is the list. To add new content or provide suggestions to send email to mitch@cirrus.com.

Samuel Ko (kko@sfu.ca) maintains a list of Unix-related books. This list contains only the recommended books, so it is relatively short. This table is a list of categories, if you are looking for a specific bar
Type of book, this form is certainly more appropriate. Rtfm.mit.edu's "Pub/usenet/news.answers/books/unix" is this table. To add new content or provide suggestions
Send email to kko@sfu.ca.

If you can't use AnonyMouse ftp, email to the "ftpmail@decwrl.dec.com" letter to write "Help" and then you'll receive a copy of how to email
A anonymous letter.


1.6 Before the pronunciation table in this FAQ?

When the 1989 document was opened, it contained a copy of Carl Paukstis<carlp@frigg.isc-br.com> 's original book, maintained by Maarten Litmaath, a comprehensive
Pronunciation table. Later, it ended, because the pronunciation and the "Unix questions" This topic is not really about.

If you come across some words that you don't know how to read, refer to the jargon maintained by Eric S. Raymond eric@snark.thyrsus.com.

* *: _blank>ftp://ftp.csie.nctu.edu.tw/pub/gnu/jarg320.txt.gz is an ordinary text version jargon * *

If you still insist on the previous pronunciation chart, _blank>ftp.wg.omron.co.jp (133.210.4.4) "Pub/unix-faq/docs/pronunciation-guide" is