Language Selection

English French German Italian Portuguese Spanish

Five common mistakes that Linux IT managers make

Filed under
OSS

After seeing the same mistakes repeated by different IT managers over the years, I've noticed a pattern of common errors. Here are the five common mistakes, along with tips for avoiding them.

Mistake #1: Reactive, not proactive

The number one mistake made by IT managers of all stripes is to carry out their duties by reacting to problems only as they come up, rather than looking ahead to potential problems and having a solution in place ahead of time. This trait isn't unique to IT managers, but it can be a fatal flaw when the head of an IT department fails to take a proactive approach.

For example, proactive IT managers make sure they have disaster plans in place rather than trying to implement a disaster plan on the fly. A good IT manager will have plans to deal with hardware failure, natural disaster, compromised systems, and any other problem that might crop up. If you spend most of your time putting out fires, you're probably not being proactive enough -- or you're still cleaning up the previous manager's messes.

A proactive manager plans for the future in terms of capacity planning, upgrades, and support. What happens when an application outgrows a single server, for example? How difficult will it be to deploy on multiple servers, and is this even possible? When deploying open source software, you'll want to assess the health of the community that supports it. If it's a project without a long history and an active developer community, it may not be the best choice. Projects like Samba and Apache are safe bets, while a project that made its SourceForge debut three weeks ago is risky business.

Many organizations experience costly growing pains because the IT infrastructure wasn't planned with an eye to the future. You may only need to support five or 50 users now, but what about three to five years down the road? If that seems like it's too far off to worry about, you've already failed.

When it comes to hardware, be picky and choose servers and equipment that will have a long life span and support. Be cautious about choosing non-standard hardware with binary-only kernel modules. The vendor may provide support and upgrades now, but what happens if it chooses to stop supporting a piece of hardware after a few years? That leaves you with the choice of ditching hardware or not being able to upgrade the kernel.

Mistake #2: Failing to emphasize documentation and training

Full Article.

More in Tux Machines

Canonical Says Ubuntu 18.04 LTS (Bionic Beaver) Will Come with Boot Speed Boost

Canonical's Will Cooke published a new Ubuntu Desktop newsletter today to inform the community on the development progress of the upcoming Ubuntu 18.04 LTS (Bionic Beaver) operating system. Besides various improvements for the GNOME desktop environment, the Ubuntu Desktop team over at Canonical recently started to investigate the boot speed of the Ubuntu Linux operating system, planning to give it another boost by using systemd’s latest features to do some profiling, which will help them identify any issues that might cause slow boot up time. Read more Also: Canonical Pulls Intel's Spectre Update from Ubuntu Repos Due to Hardware Issues

Intel's "Utter Garbage" Code Bricks and Delays Linux, Torvalds Furious

today's leftovers

  • 20 Years of LWN
    Back in mid-1997, your editor (Jonathan Corbet) and Liz Coolbaugh were engaged in a long-running discussion on how to trade our nice, stable, reliably paying jobs for a life of uncertainty, poverty, and around-the-clock work. Not that we thought of it in those terms, naturally. We eventually settled on joining Red Hat's nascent "support partner" program; while we were waiting for it to get started, we decided to start a weekly newsletter as a side project — not big and professional like the real press — to establish ourselves in the community. Thus began an amazing journey that has just completed its 20th year. After some time thinking about what we wanted to do and arguing about formats, we published our first edition on January 22, 1998. It covered a number of topics, including the devfs controversy, the pesky 2GB file-size limit on the ext2 filesystem, the use of Linux on Alpha to render scenes in the film "Titanic", the fact that Red Hat had finally hired a full-time quality-assurance person and launched the Red Hat Advanced Development Labs, and more. We got almost no feedback on this issue, though, perhaps because we didn't tell anybody that we had created it.
  •  
  • EzeeLinux Show 18.4 | Ubuntu 17.10 Revisited
    Canonical revised Ubuntu 17.10 with the new 17.10.1. Time to take another look…
  • PodCTL #22 – Highway to Helm
    One of the reasons that Kubernetes has gained so much traction in the marketplace is because it is flexible enough to allow innovation to happen all around the core APIs. One area where that has happened is in application package management, specifically with the Helm project.
  • LibreELEC Linux OS Will Get Meltdown and Spectre Patches with Next Major Release
    The development team behind the Kodi-based LibreELEC (Libre Embedded Linux Entertainment Center) open-source HTPC operating system for embedded systems and PCs released LibreELEC 8.2.3. LibreELEC 8.2.3 is the third maintenance update to the LibreELEC 8.2 "Krypton" series of the Just enough Operating System (JeOS), which is based on the Kodi 17 "Krypton" open-source and cross-platform media center. It's here a month after the LibreELEC 8.2.2 point release to address a few issues.
  • openSUSE 42.2 to Reach End-of-Life This Week
    The minor release of openSUSE Leap 42.2 will reach its End-of-Life (EOL) this week on Jan. 26. The EOL phase ends the updates to the operating system, and those who continue to use EOL versions will be exposed to vulnerabilities because these discontinued versions no longer receive security and maintenance updates; this is why users need to upgrade to the newer minor; openSUSE Leap 42.3. “We are very pleased with the reliability, performance and longevity of Leap,” said openSUSE member Marcus Meissner. “Both the openSUSE community and SUSE engineers have done a fantastic job with security and maintenance of the Leap 42 distribution; users can be confident that their openSUSE operating system is, and will continue to be, receiving bug fixes and maintenance updates until its End-of-Life.”
  • French Gender-Neutral Translation for Roundcube
    Here's a quick blog post to tell the world I'm now doing a French gender-neutral translation for Roundcube.
  •  
  • This Oil Major Has a Supercomputer the Size of a Soccer Field
    Big Oil is now Big Tech. So big, in fact, that Eni SpA’s new supercomputer is the size of a soccer field. In the multimillion-dollar pursuit of the world’s most powerful computers, the Italian explorer says it’s taken the lead. Its new machine, located outside Milan, will scan for oil and gas reservoirs deep below the Earth over thousands of miles. “This is where the company’s heart is, where we hold our most delicate data and proprietary technology,” Eni Chief Executive Officer Claudio Descalzi said in an interview on Thursday.

Compilers and CLI: LLVM, GCC and Bash