Language Selection

English French German Italian Portuguese Spanish

OpenSuse's Kiwi-LTSP: Easy Thin Client Server - Snake Oil or Fountain of Youth?

Filed under
SUSE

LDM LoginIT solutions companies have been generating lots of buzz regarding thin clients basically since the early 1990s, but have yet to really penetrate into many suitable environments. These relatively cheap computer appliances carry broad promises like energy efficiency, space efficiency, centralized maintenance and centralize data storage. These claims could sound like the computer industry equivalent of snake oil. Kiwi-LTSP, a combination of KIWI imaging technology and Linux Terminal Server Project, is one open source solution for thin client servers.

Why do thin clients or terminal devices matter? For general consumers, home users and office computer users thin clients should have no visible impact. This is nothing new, as companies like Sun, HP, Dell, Wyse and Citrix have always promoted thin clients, dumb terminals and the like from a support perspective. Check out Sun, HP and Wyse product descriptions here, here, and here respectively. In my own experience supporting Windows desktops in an Enterprise environment we were always looking for ways to improve maintenance and customer experience without user interaction.

rest here




More in Tux Machines

More on Canonical and Kubernetes

Docker 1.12.2 Linux App Container Engine Enters Development, Improves Swarm Mode

Docker's Victor Vieux announced the other day the release and immediate availability for download of the first RC (Release Candidate) snapshot of the upcoming Docker 1.12.2 open-source application container engine. The first point release of Docker 1.12, a major branch that introduced built-in orchestration and routing mesh, a brand new Swarm Mode, as well as numerous networking security improvements, Docker 1.12.1, was announced last month on the 18th, and since then the development team never stopped improving the software. Read more

FreeBSD Delaaays and OpenBSD Founder Theo de Raadt Upset

  • FreeBSD 11.0-RELEASE Needs To Be Respun Due To Security Issues
    The delayed FreeBSD 11.0 release just suffered another last-minute set-back. While "FreeBSD 11.0-RELEASE images" were distributed to FTP mirrors and the official announcement expected today, these images need to be re-spun to contain some security fixes and thus pushing back the official release. Glen Barber noted today on the mailing list, "Although the FreeBSD 11.0-RELEASE has not yet been officially announced, many have found images on the Project FTP mirrors. However, please be aware the final 11.0-RELEASE will be rebuilt and republished on the Project mirrors as a result of a few last-minute security fixes we feel are imperative to include in the final release."
  • FreeBSD 11.0 Operating System Lands October 5 Due to Last-Minute Security Issues
    A few minutes ago, Glen Barber informed the FreeBSD community that they should not hurry and install the ISO images of the FreeBSD 11.0 operating system made available a few days ago on the official FTP mirrors. These images aren't safe to use and contain various security vulnerabilities that need to be fixed before the FreeBSD Project will officially unveil the final release of the FreeBSD 11.0 operating system in the coming days. According to the release schedule, FreeBSD 11.0 should hit the streets later today, September 29, 2016. However, until then the FreeBSD development team is hard at work patching those nasty security issues and rebuilding the final ISO images, which will be made available on the respective FTP mirrors later today as FreeBSD 11.0-RELEASE-p1. If you're already running FreeBSD 11.0-RELEASE, you will soon be provided with instructions to safely update your system
  • OpenBSD Founder Calling For LLVM To Face A Cataclysm Over Its Re-Licensing
    For over one year there's been talk of LLVM pursuing a mass relicensing from its University of Illinois/NCSA Open Source License, which is similar to the three-clause BSD license, to the Apache 2.0 license with explicit mention of GPLv2 compatibility. As mentioned in that aforelinked article, this re-licensing is moving ahead.