Acronyms and Abbreviations
While I was looking for some ideas for the next Linux Buzz, a banner ad on the Linux Journal site momentarily confused me. It is the banner for Code Fusion and it was talking about an IDE. While I visualized an IDE disk drive only momentarily, I realized that lots of people could be confused by many of the acronyms and abbreviations we use. So, that quickly became my subject for the week.
As IDE inspired this column, let's start there. When talking about an interface to a disk drive, CD-ROM or tape drive, IDE is an abbreviation for Integrated Drive Electronics. IDE disks replaced MFM (Manchester Frequency Modulation) and RLL (Run Length Limited) disks. Clearly, MFM and RLL were pretty useless terms for the computer user. Both these terms referred to the way data was stored on the disk. Data encoding was done by the controller card. The significance of IDE was that the data encoding was moved from the controller card to the disk drive itself.
The other IDE? The one that was in the banner ad. Integrated Development Environment. This is where you can write and test your code without leaving one program. For me, this is an alternative to edit with vi, compile and link with cc, execute and then possibly debug with gdb. For Emacs users, they will say that Emacs is an IDE.
My personal favorite abbreviation is ATM. Most people on the planet think it means "place to get cash". Many of these people don't even know it stands for Automatic Teller Machine. If they did, why would they say they are going to an ATM machine?
Two more meanings: Asynchronous Transfer Mode and Adobe Type Manager. Asynchronous Transfer Mode refers to a protocol for transferring data. And, of course, Adobe Type Manager is a program that manages PostScript and other fonts.
How about those communications terms like PPP, SLIP, DSL and ISDN? PPP and SLIP are communications protocols. DSL and ISDN are types of communications services.
PPP stands for Point-to-Point Protocol. It is the most common protocol for modem connections. It allows you to appear, to the rest of the Internet, just like any other connected host. PPP has mostly replaced SLIP (Serial Line Internet Protocol) as the standard protocol used for these connections. The reason is that SLIP "just happened" and lacks both capabilities and standards.
DSL (Digital Subscriber Line) and ISDN (Integrated Services Digital Network) are both services that allow you to digitally connect to different sites. DSL is the newer service, offering higher speeds but less flexibility. With DSL service, you receive a constantly connected link to another site, generally your ISP. Minimum speed is 256Kbps with speeds of multiple megabits available. <o> ISDN differs in that it is a dial-up connection much like a standard telephone. A BRI (Basic Rate Interface) ISDN line makes two 64Kb channels available to the user. The two channels can be used together for a higher data rate. Besides speed, ISDN offers extremely fast setup (connect) times making it idea for such services as credit card verification.
Oops, I said "modem" above. That's modulator/demodulator. Modulator refers to the operation of encoding digital data into an analog format for transmission over an analog (voice) line. Demodulator is the operation at the other end to recover the data back into its digital form. While commonly used, there is no such thing as a "DSL modem". DSL is digital, so there is no modulation process involved. Generally you are talking about a DSL router.
Oh, "router". Caught again. A router allows you to connect networks together in an intelligent fashion. By "intelligent fashion", I mean that a router does not just supply an electrical connection between equipment (a hub does this) but it takes action based on the, well, data.
At this point I feel I have gotten myself into enough trouble. In the last paragraph where I said "data" I really wanted to say "packets". But then I would have to talk about IP and TCP and, well, you get the idea.
Linux Journal has introduced a lot of new terms. We try our best to define them when we introduce them, but searching through six years of magazines may not be the best way to look up these terms. Would a glossary, printed or on-line, be of use? Let me know.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide