Linux? On the Macintosh? With Mach?
So, Why Linux?
Need you ask? Linux is the overwhelming favorite among users of free Unix clones. Linux provides Unix features such as true multitasking, virtual memory, shared libraries, demand loading, TCP/IP networking and many other advanced features. Versions of Linux have been ported to a wide variety of platforms, including other PowerPC-based computers, making the Power Macintosh port that much easier.
The Linux community is large, growing, active and involved. This community promotes development and exchange of software and ideas, making it an excellent environment for a new OS product. And, last but not least, Linux is covered by the GNU General Public License, ensuring Apple's contributions will not be used in some other vendor's proprietary product.
You may be asking yourself, “Why would I want to run Linux on a Power Macintosh?” After all, the Linux community is overwhelmingly oriented toward Intel hardware. Why change?
For one thing, it's good for Apple and Apple enthusiasts. As noted above, Linux opens the door to a new Macintosh market. Many researchers and scientists who might well find the Macintosh a useful tool, cannot justify the purchase of a second computer system. If their shop runs Unix, a Macintosh just didn't fit in—until now.
University laboratories and dorm rooms are another target. With the availability of MkLinux, users can benefit from the best of both worlds: using Linux for research and batch data processing and MacOS for graphical applications, desktop publishing, and much more. So, Apple may sell the machine, but you get the fun. Think of all those cool MacOS applications just waiting to be explored, not to mention the joy of using the Power Mac's multimedia capabilities under MkLinux.
In keeping with Apple's traditions, the highly integrated Power Macintosh hardware greatly eases Linux system administration. Power Macs are delivered as complete systems. Thus, a Power Macintosh normally can run MkLinux straight “out of the box”, without the addition of cards, chips and other components. Because Power Macs use an intelligent bus such as NuBus or PCI, the OS can deal with hardware configuration concerns such as DMA addressing and interrupt vectors.
In fact, as we tell folks at trade shows: “Once you've installed it, MkLinux is really just Linux. You'll have to give up a few things, of course—DMA vectors, IRQ settings, jumpers, incompatible BIOS code—but basically, it's just Linux...”
Although MkLinux, Apple Computer's Microkernel Linux for the Power Macintosh, has been under development for a few years, it has been available to the general public for only a short while. Apple's first public announcement concerning MkLinux was made at the Free Software Foundation's First Conference on Freely Redistributable Software (February 1996).
Apple announced it was supporting a project with the Open Software Foundation (OSF; now merged with X/Open to form the Open Group) to port Linux to a Mach base and to port Mach to a variety of Power Mac products. The project was initiated, sponsored and funded by Apple Computer.
OSF provided the Mach 3.0 Microkernel (developed by Carnegie Mellon University and the OSF Research Institute) and the engineering team to port the code. (An OSF paper on MkLinux—“Linux on the OSF Mach 3 Micro-kernel”—was presented at the conference.)
Apple's February 1996 announcement predicted the first port of MkLinux would become available in the summer of 1996. Exceeding expectations, the first general release of MkLinux, Developer Release 1 (DR1), became available in May. MkLinux DR1 was followed by DR2, released in September 1996. DR3 is scheduled for release in early spring of 1997.
MkLinux releases tend to incorporate large numbers of changes. Hundreds of megabytes of new or changed material must be acquired, whether by FTP or CD-ROM, typically requiring a complete re-installation. Consequently, full MkLinux releases are made on a relatively infrequent basis (only when warranted by a sufficiently large or fundamental set of changes).
Between releases, Apple issues minor updates via FTP. Some updates provide bug fixes; others introduce new or experimental features. In either case, they are meant to be used with a specific MkLinux release.
At this point, you may be wondering exactly what MkLinux is. Does it run the MacOS Finder? Does it run X11? Are all the commands I know and love available? For that matter, how is the name itself pronounced?
First things first: MkLinux is officially pronounced “em-kay” Linux, but is often pronounced McLinux. This is in line with Linux tradition, which permits Linux itself to be pronounced in any of several ways. (Li-nucks, Li-nooks, Lie-nooks and even Lee-nooks are quite commonly heard.)
In any event, MkLinux is a complete port of Linux, with a full set of GNU tools and accessories, including X11R6, which runs on top of the Mach micro-kernel. Hence, Mk (Microkernel) Linux. Because MkLinux is really just Linux, it doesn't run the Finder—yet. On the other hand, it does run just about any Linux command you could imagine. (Commands that require Intel-based hardware are, of course, impossible.)
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
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.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
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