Professional Linux Deployment
Professional Linux Deployment is part of the Wrox Programmer to Programmer series. In the Introduction the book states it will teach professional administrators steps to replace existing network systems with Linux. The book is targeted towards the NT and non-Linux UNIX administrator. It presumes the reader is a knowledgeable NT administrator and has learned Linux installation and basic setups elsewhere.
Professional Linux Deployment (PLD) opens by recognizing that some readers may first have to provide a convincing argument for why Linux should be integrated into the organization's information technology architecture. To keep things balanced, the authors also provide arguments against Linux. Several pro and con Linux web sites are suggested. The book then moves on to integrating Linux platforms into NT and other UNIX computing environments.
The first major integration topic to be covered is replacing NT-based file and print servers with Samba. Implementing web and ftp servers is the next integration area presented. At this point the authors provide an e-commerce case study using Linux and Apache. Next they examine the integration of databases and directory services.
Network infrastructure services are discussed next and here the authors provide details on replacing your current routers, gateways, mail and DNS servers, proxies and firewalls with Linux-based machines. Secure networks and links have become important to the average business. PLD's cryptography chapter suggests various encryption tools available for integration into an IT architecture to secure network traffic.
The integration of distributed systems is discussed and provides some idea as to whether or not Linux could be implemented within a particular environment. The last area of integration looks at providing component object model (COM) and distributed component object model (DCOM) functionality from a Linux platform.
In closing, the book offers a case study on migrating to Linux. This study primarily discusses migrating an application from UNIX to Linux. Each chapter concludes with a list of resources, which include web sites, books, mailing lists and news groups.
Three appendices provide a 5,000 foot overview of Linux, Linux commands and utilities, and pointers on system administration. As a reference, these appendices are okay, but do not expect to learn all you need to know about Linux and Linux administration here.
Deployment decisions must be economically, politically and technically acceptable to the organization. Since this is a book on deployment, I expected to see some deployment guidance or suggested methodology. Sadly, this book fails to discuss this area in any depth.
The book provides the technical knowledge and experience necessary when making Linux-deployment recommendations. It delineates the steps to set up Linux-based services in comparison to those provided by NT or other UNIX variants. This allows for a careful examination of the similarities and differences between services provided by NT and Linux platforms. It makes it easier to compare the quality of a current service with the same Linux-based service. The book also made it easier to contrast the resources required in setting up and maintaining Linux-based services with the services on your current platform. The knowledge gained from this resource should provide the technical foundation for deciding whether deploying Linux-based services makes technical and financial sense.
Considerable credit must be given to the book's editors as well. If it were not for the author list, it would be difficult to recognize that ten people contributed text to this book.
Daniel Lazenby (firstname.lastname@example.org) first encountered UNIX in 1983 and discovered Linux in 1994.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- 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