Home | Articles | About | Contact | Forum |
Sunday, December 04, 2016



Lunarpages.com Web Hosting

Mailing List

E-mail:
By Joining the mailing list you will be notified of site updates.


Show Your Support For
This Site By Donating:











Audience: System Admins - Experts
Last Updated: 3/24/2011 6:22:45 PM
Original Creation Date: 3/24/2011 6:22:45 PM
**All times are EST**




Complicated Linux Environments

By Erik Rodriguez

Tags: complex linux servers, poor linux design, bad linux administration, overly-complicated environments, SuSE Linux, Juniper firewall, Fedora Core

This article contains information about my actual experiences with overly-complicated Linux environments.



Introduction

As a consultant, I sometimes have the unfortunate experience of dealing with overly-complicated Linux environments. In most cases, the cause is an over-zealous admin that simply wanted to feel like security expert, programmer, developer, DBA, systems administrator, network administrator, and IT manager. There are 3 parts to the series of complicated Linux environments.

Learning Linux

There are many resources for Linux on this site and the rest of the Internet. Each version varies slighty. Red hat is a little different from Debian. Debian is different than Novell (SuSE). The majority of the logic and operation is the same as they are all versions of Linux. However, some have special ways of doing things like log rotation, location of system files, and more. If you have a solid understanding of how the operating system works, you should be able to work on nearly any distribution of Linux out there. There are some I prefer over others, but at the end of the day, I can administer any distro if someone put a gun to my head. That being said, I would like to get into the meat of this topic. The 3 examples provided below are my real world encounters with complicated Linux environments. The content contained in these examples is very technical and if you do not understand everything, you should at least grasp the magnitude and frustration I had to deal with taking on these two networks.



Contact Us

If you found this information useful, click the +1 button



Your E-mail:


Subject:


Type verification image:
verification image, type it in the box

Message:


NOTE: this form DOES NOT e-mail this article, it sends feedback to the author.

TCP vs. UDP
Juniper SRX anti-spam filtering config
Windows Server 2008 Clustering Configuration
Windows 2008 R2 Network Load Balancing (NLB)
Extreme Networks: Downloading new software image
Juniper SRX save config to USB drive
Juniper SRX logout sessions
Extreme Networks Syslog Configuration
Command line drive mapping
Neoscale vs. Decru
Data Security vs. Data Protection
Juniper SRX Cluster Configuration
HOWTO - Create VLAN on Extreme Switch
Using a Non-local Colocation Facility
Linux Server Administration
IT Chop Shops
Flow Viewers: SFLOW, NetFLOW, and JFLOW
Exchange 2007 Back Pressure
IPtables open port for specific IP
Politics in IT Departments
HOWTO - Block Dropbox
Cisco IOS Cheat Sheet
Subnet Cheat Sheet
Design a DMZ Network
How DNS works
Firewall Configuration
Juniper SSG Firewalls
Server Management
Configuring VLANs
Runlevels in Linux
Server Clustering
SONET Networks
The Red Hat Network
Server Colocation
Complicated Linux Servers
Dark Fiber
Data Center Network Design
Firewall Types
Colocation Bandwidth






Copyright © 2002-2016 Skullbox.Net All Rights Reserved.
A division of Orlando Tech Works, LLC
By using this site you agree to its Terms and Conditions.
Contact Erik Rodriguez