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

These Are the Default Wallpapers of the Ubuntu 17.04 (Zesty Zapus) Linux Distro

Ubuntu member Nathan Haines is proud to inform Softpedia about the availability of the new community wallpapers for the upcoming Ubuntu 17.04 (Zesty Zapus) operating system. Ubuntu 17.04 just got its Final Beta release at the end of last week, and now that Final Freeze stage is approaching fast, it's time for us to have a look at the default wallpapers shipping with the final release, which have been contributed by various artists and photographers from all over the world. Read more

Samsung Galaxy Tab S3 Review: Finally, an Android tablet built with enterprise users in mind

Show me an Android tablet and I'll show you a device that has yet to live up to its full potential. Google's Play Store lacks a wide selection of apps that support a tablet's larger display, with most apps only expanding the phone interface, in turn looking horrible on the smaller screen. In addition to the lack of quality apps, Android tablets have lacked key accessories such as a keyboard. For the most part, Android tablets have been relegated to a device used to catch up on Netflix or to entertain kids with games. Read more

Ubuntu 17.04 inches closer to production

Ubuntu's final beta for version 17.04 has landed. Zesty Zapus covers Ubuntu desktop, server and cloud editions, Kubuntu, Lubuntu, Ubuntu Gnome, MATE, Studio and Xubuntu flavours. It's not a huge feature boost, but the release is using the Linux 4.10 kernel, useful if your iron runs Intel Kaby Lake or AMD Ryzen silicon. If configuring the Common UNIX Printing System (CUPS) is on your hate-list, there's good news: the release includes support for driverless printing. Read more Also: Getting Better Radeon Polaris Performance On Ubuntu 17.04 With Mesa 17.1, Linux 4.11

Linux 4.11 RC4

  • Linux 4.11-rc4
    So last week, I said that I was hoping that rc3 was the point where we'd start to shrink the rc's, and yes, rc4 is smaller than rc3. By a tiny tiny smidgen. It does touch a few more files, but it has a couple fewer commits, and fewer lines changed overall. But on the whole the two are almost identical in size. Which isn't actually all that bad, considering that rc4 has both a networking merge and the usual driver suspects from Greg, _and_ some drm fixes - and those tend to be the big areas. So on the whole things look fine. There's changes all over, and in mostly the usual proportions. Some core kernel code shows up in the diffstat slightly more than it usually does - we had an audit fix and a bpf hashmap fix, but on the whole it all looks very regular: mostly drivers, networking, arch fixes and some filesystem noise. Shortlog appended as usual for people who want to skim the details. Go out and test, Linus
  • Linus Torvalds Announces the Fourth Release Candidate of the Linux 4.11 Kernel
    As expected, Linus Torvalds made his regular Sunday announcement to inform us about the availability of the fourth Release Candidate (RC) development release of the upcoming Linux 4.11 kernel. Coming one week after the third Release Candidate, Linux 4.11 RC4 appears to be just a bit smaller than the previous build, updating the networking stack and many of the supported drivers to be on par with what was changed earlier this week in the stable Linux kernel branches.
  • Linux 4.11-rc4 Kernel Released
    Linus Torvalds has announced the Linux 4.11-rc4 kernel this evening.