Unix

CTSS

CTSS:

Compatible Time-Sharing System. An early (1963) experiment in the design of interactive timesharing, operating systems, ancestral to {Multics}, {Unix}, and {ITS}. The name {ITS} (Incompatible Time-sharing System) was a hack on CTSS, meant both as a joke and to express some basic differences in philosophy about the way I/O services should be presented to user programs. See {timesharing}.

Related articles by Zemanta

Ctss (what-is-the-meaning-of.blogspot.com)
Multics (what-is-the-meaning-of.blogspot.com)
operating system (what-is-the-meaning-of.blogspot.com)
troff (what-is-the-meaning-of.blogspot.com)
wheel bit (what-is-the-meaning-of.blogspot.com)
Weenix (what-is-the-meaning-of.blogspot.com)
man page (what-is-the-meaning-of.blogspot.com)
Ctss (underpop.online.fr)

Marcadores: Mainframe, Multics, Philosophy, Time-sharing, Unix

# 5/20/2009 07:31:00 AM, Comentários, Links para esta postagem,

RFC

[Request For Comment] One of a long-established series of numbered Internet informational documents and standards widely followed by commercial software and freeware in the Internet and Unix communities. Perhaps the single most influential one has been RFC-822 (the Internet mail-format standard). The RFCs are unusual in that they are floated by technical experts acting on their own initiative and reviewed by the Internet at large, rather than formally promulgated through an institution such as ANSI. For this reason, they remain known as RFCs even once adopted as standards.
The RFC tradition of pragmatic, experience-driven, after-the-fact standard writing done by individuals or small working groups has important advantages over the more formal, committee-driven process typical of ANSI or ISO. Emblematic of some of these advantages is the existence of a flourishing tradition of `joke' RFCs; usually at least one a year is published, usually on April 1st. Well-known joke RFCs have included 527 ("ARPAWOCKY", R. Merryman, UCSD; 22 June 1973), 748 ("Telnet Randomly-Lose Option", Mark R. Crispin; 1 April 1978), and 1149 ("A Standard for the Transmission of IP Datagrams on Avian Carriers", D. Waitzman, BBN STC; 1 April 1990). The first was a Lewis Carroll pastiche; the second a parody of the TCP-IP documentation style, and the third a deadpan skewering of standards-document legalese, describing protocols for transmitting Internet data packets by carrier pigeon (since actually implemented; see Appendix A). See also {Infinite-Monkey Theorem}.
The RFCs are most remarkable for how well they work -- they frequently manage to have neither the ambiguities that are usually rife in informal specifications, nor the committee-perpetrated misfeatures that often haunt formal standards, and they define a network that has grown to truly worldwide proportions.

Related articles by Zemanta

Introduction to the Internet (slideshare.net)
40 Years Of RFCs (slumpedoverkeyboarddead.com)
Tcp/ip (what-is-the-meaning-of.blogspot.com)
Internet6 (slideshare.net)
Bsd (what-is-the-meaning-of.blogspot.com)
The 40th Anniversary of RFC #1 (isen.com)
Rfc (underpop.online.fr)

Marcadores: Internet, Packet, Protocol, Protocols, RFCs, Software, Telnet, Unix

# 5/19/2009 07:31:00 PM, Comentários, Links para esta postagem,

Version 7

The first widely distributed version of {Unix}, released unsupported by Bell Labs in 1978. The term is used adjectivally to describe Unix features and programs that date from that release, and are thus guaranteed to be present and portable in all Unix versions (this was the standard gauge of portability before the POSIX and IEEE 1003 standards). Note that this usage does not derive from the release being the "seventh version of {Unix}"; research {Unix} at Bell Labs has traditionally been numbered according to the edition of the associated documentation. Indeed, only the widely-distributed Sixth and Seventh Editions are widely known as V[67]; the OS that might today be known as `V10' is instead known in full as "Tenth Edition, Research Unix" or just "Tenth Edition" for short. For this reason, "V7" is often read by cognoscenti as "Seventh Edition". See {BSD}, {Unix}. Some old-timers impatient with commercialization and kernel bloat still maintain that V7 was the Last True Unix.

Marcadores: Bell Labs, BSD, Documentation, History, Network, POSIX, Unix

# 5/19/2009 03:31:00 PM, Comentários, Links para esta postagem,

userland

Image via Wikipedia

userland:

Anywhere outside the kernel. "That code belongs in userland." This term has been in common use among Unix kernel hackers since at least 1985, and may have have originated in that community. The earliest sighting was reported from the usenet group net.unix-wizards.

seggie

[Unix] Shorthand for segmentation fault reported from Britain.

Related articles by Zemanta

segmentation fault (what-is-the-meaning-of.blogspot.com)

Marcadores: Documentation, dreeping, History, IPhone, itunes, Linux, Unix

# 5/12/2009 10:31:00 PM, Comentários, Links para esta postagem,

grind

[MIT and Berkeley; now rare] To prettify hardcopy of code, especially LISP code, by reindenting lines, printing keywords and comments in distinct fonts (if available), etc. This usage was associated with the MacLISP community and is now rare; {prettyprint} was and is the generic term for such operations.
[Unix] To generate the formatted version of a document from the troff, TeX, or Scribe source.
[common] To run seemingly interminably, esp. (but not necessarily) if performing some tedious and inherently useless task. Similar to {crunch} or {grovel}. Grinding has a connotation of using a lot of CPU time, but it is possible to grind a disk, network, etc. See also {hog}.
To make the whole system slow. "Troff really grinds a PDP-11."
grind grind excl. Roughly, "Isn't the machine slow today!"

Marcadores: Code, Common, Languages, Lisp, MIT, PDP-11, Programming, Source, TeX, Unix

# 5/09/2009 11:31:00 PM, Comentários, Links para esta postagem,

segmentation fault

[Unix]

[techspeak] An error in which a running program attempts to access memory not allocated to it and {core dump}s with a segmentation violation error. This is often caused by improper usage of pointers in the source code, dereferencing a null pointer, or (in C) inadvertently using a non-pointer variable as a pointer. The classic example is:
int i; scanf ("%d", i); /* should have used &i */
To lose a train of thought or a line of reasoning. Also uttered as an exclamation at the point of befuddlement.

Related articles by Zemanta

segmentation fault (what-is-the-meaning-of.blogspot.com)
vaxocentrism (what-is-the-meaning-of.blogspot.com)
chase pointers (what-is-the-meaning-of.blogspot.com)
Lions Book (what-is-the-meaning-of.blogspot.com)
Blob (what-is-the-meaning-of.blogspot.com)
swizzle (what-is-the-meaning-of.blogspot.com)
Utsl (what-is-the-meaning-of.blogspot.com)
Rtfb (what-is-the-meaning-of.blogspot.com)
back door (what-is-the-meaning-of.blogspot.com)

Marcadores: Code, Languages, Memory, Pointer, Programming, Scanf, Source, Unix

# 5/04/2009 02:31:00 PM, Comentários, Links para esta postagem,

letterbomb

n. A piece of {email} containing {live data} intended to do nefarious things to the recipient's machine or terminal. It used to be possible, for example, to send letterbombs that would lock up some specific kinds of terminals when they are viewed, so thoroughly that the user must cycle power (see {cycle}, sense 3) to unwedge them. Under Unix, a letterbomb can also try to get part of its contents interpreted as a shell command to the mailer. The results of this could range from silly to tragic; fortunately it has been some years since any of the standard Unix/Internet mail software was vulnerable to such an attack (though, as the Melissa virus attack demonstrated in early 1999, Microsoft systems can have serious problems). See also {Trojan horse}; compare {nastygram}.
Loosely, a mailbomb.

Related articles by Zemanta

letterbomb (what-is-the-meaning-of.blogspot.com)
virus (what-is-the-meaning-of.blogspot.com)
Cybercrime (pindebit.blogspot.com)
Will Microsoft Endure? Ex-Employee Presents Good Reasons It Won't (lockergnome.com)
Improvements to AutoPlay (blogs.msdn.com)
Sun deal could make IBM unbeatable in Unix server market (infoworld.com)
SCO threatened with Chapter 7 destruction (theregister.co.uk)
spool file (what-is-the-meaning-of.blogspot.com)
McAfee: New botnets dwarf Conficker threat (news.cnet.com)
Around The Blogosphere 26 March 09 (dave-lucas.blogspot.com)

Marcadores: Internet, Melissa, Microsoft, Software, Unix, Virus, Windows

# 4/22/2009 11:31:00 PM, Comentários, Links para esta postagem,