Overview Of The Debian GNU/Linux System
Debian differs from other Linux distributions in many ways, a few of which are radical departures from the ways distributions of the past were assembled. These differences have attracted developers from around the world to work together toward the common goal of making Debian the best Linux distribution available. Indeed, one of the differences that has attracted them is the fact that they can work together.
The most unique aspect of Debian development as compared to other Linux distributions is the fact that it has been and continues to be developed openly by a group of volunteers, and that it is open to other volunteers who wish to join the effort. Debian is not developed by one individual or a small, closed group. Instead, it follows in the tradition of the Linux kernel; it is developed by those who use it, and this makes for a higher quality, more dynamic, and truly modular system.
Does this sound to you like an invitation to chaos? Originally, many people claimed that the open development of the Linux kernel was an invitation to chaos and disaster, yet Linux is not a disaster. Neither is Debian, for a good reason.
As the Debian developers create their pieces, they follow strict guidelines for constructing and maintaining these pieces, called packages. Because these guidelines are followed, each package can be dropped into the system independently without damaging or interfering with programs from other packages. By working with a set of consistent rules and with identical tools, the volunteers can and do create a truly modular system.
Modularity is extremely important to such a large collection of software as a distribution. New releases of the software that comprise the distribution are constantly being made, and it is the task of the distribution maintainer (or maintainers, in the case of Debian) to keep this software well integrated with the rest of the system and up to date. It is very difficult for the maintainer to do this successfully with dozens of megabytes of software, especially when the software is not written specifically for the system. When one person or small group attempts to do this, maintenance of the distribution soon becomes a nightmare.
A distribution with many different people responsible for the maintenance of its packages does not suffer from this overwhelming task; different people are able to devote more attention to the packages they maintain than would otherwise be possible, and it is possible for experts in a particular area to take responsibility for the packages involving their area of expertise. The result is a better, more timely set of packages, complete with up-to-date components, full documentation and solid examples. A collection of such independent but highly cooperative packages makes a high quality, consistent, modular distribution, which is exactly what Debian is.
Debian was the first Linux system to adopt, support and participate in the construction of the Linux Filesystem Standard (FSSTND); since that time, Debian has been joined by Linux/PRO, MCC, Slackware, TAMU, and other major distributions. FSSTND compliance means full compatibility with the distributions that follow it, easy integration of third-party packages and easy installation of the system into a network of FSSTND-compliant Linux machines.
Debian was designed to be simple enough for the novice to install and configure, yet not so simple-minded as to frustrate the advanced user. The installation process is as modular as the system itself; the base system, which requires less than 7MB of disk space, can be installed in less than ten minutes. All packages are installed independently of the base system with the Debian package maintenance utility, dpkg.
A new package maintenance system called dpkg has been developed specifically for the Debian system. With dpkg, the administrator of a Debian system can easily install, remove, upgrade and obtain information about both installed and not-yet-installed packages.
dpkg is being written to easily and extensibly support multiple package formats, and it is planned to eventually support (at least) Slackware and System V packages.
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
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader 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