0%

Words starting with rtrev

Unfortunately we didn’t found any matching words.
Maybe these words will be useful:
  • rtr — Royal Tank Regiment
  • rt-11 — (operating system)   A real time operating system for the DEC PDP-11 computers, used in the early 1980s and still in 2005 found occasionally in old embedded systems.
  • rt-cdl — Real-Time Common Design Language
  • rt-pc — (computer)   RISC Technology Personal Computer. (Commonly, but incorrectly, known as the "PC-RT", later changed to just "RT") IBM's first RISC-based Unix computer. The RT-PC was the predecessor to IBM's RS/6000. It ran AIX 1.x and 2.x and had a PC-AT bus and IBM's ROMP microprocessor. It was withdrawn from the marketing around 1989 or 1990.
  • rtbm — (Unix) Read The Bloody Manual.
  • rtee — Real Time Engineering Environment: a set of CASE tools produced by Westmount Technology B.V.
  • rtfaq — (Usenet, primarily written, by analogy with RTFM) Read the FAQ! An exhortation that the person addressed ought to read the newsgroup's FAQ list before posting questions.
  • rtfb — (jargon)   (By analogy with RTFM) Read The Fucking Binary. Used when neither documentation nor source for the problem at hand exists, and the only thing to do is use some debugger or monitor and directly analyse the assembler or even the machine code. "RTFB" is the least pejorative of the RTF? forms, the anger is directed at the absence of both source *and* adequate documentation rather than at the person asking a question.
  • rtfs — (jargon)   1. Read The Fucking Source. Variant form of RTFM, used when the problem at hand is not necessarily obvious and not answerable from the manuals - or the manuals are not yet written and maybe never will be. For even trickier situations, see RTFB. Unlike RTFM, the anger inherent in RTFS is not usually directed at the person asking the question, but rather at the people who failed to provide adequate documentation. 2. Read The Fucking Standard; this oath can only be used when the problem area (e.g. a language or operating system interface) has actually been codified in a ratified standards document. The existence of these standards documents (and the technically inappropriate but politically mandated compromises that they inevitably contain, and the impenetrable legalese in which they are invariably written, and the unbelievably tedious bureaucratic process by which they are produced) can be unnerving to hackers, who are used to a certain amount of ambiguity in the specifications of the systems they use. (Hackers feel that such ambiguities are acceptable as long as the Right Thing to do is obvious to any thinking observer; sadly, this casual attitude toward specifications becomes unworkable when a system becomes popular in the Real World.) Since a hacker is likely to feel that a standards document is both unnecessary and technically deficient, the deprecation inherent in this term may be directed as much against the standard as against the person who ought to read it.
  • rti — return from interrupt