Language Selection

English French German Italian Portuguese Spanish

Vector Linux Partners With SQI To Provide Support Infrastructure

Filed under
Linux

Vector Linux, the decade old Canadian Linux distribution based on Slackware, has partnered with SQI Incorporated of Reno, Nevada to provide support infrastructure, both for the commercial support Vector Linux began offering earlier this year and for the wider community. SQI is providing and hosting their Incident Manager software, a ticketing system specifically for paid support customers, as well as a knowledge base available to all Vector Linux users. In addition to providing the software for the knowledge base they are assisting with content creation. The new Vector Linux website which was unveiled in July is also hosted by SQI in what SQI President Jeff Elpern describes as a "world-class data center environment."

Linux distributions break down into three rough categories: major commercial distributions with large corporate ties and/or deep-pocketed investors. Red Hat/Fedora, SuSe, Ubuntu, and TurboLinux would all be examples of large, commercial Linux distributions. The other end of the spectrum is filled with many small distros built either by a single hobbyist/developer or a small community of volunteer developers. These distributions generally have little or no income, surviving on the goodwill of the developers and perhaps small contributions from devoted users. Vector Linux fits squarely into the middle group: mid-sized distributions with a significant user and developer community but no large corporate ties.

When the Vector Linux developers created the larger SOHO (Small Office, Home Office) edition of the distribution a few years ago they identified a target market: small business users.

More Here




More in Tux Machines

NHS open-source Spine 2 platform to go live next week

Last year, the NHS said open source would be a key feature of the new approach to healthcare IT. It hopes embracing open source will both cut the upfront costs of implementing new IT systems and take advantage of using the best brains from different areas of healthcare to develop collaborative solutions. Meyer said the Spine switchover team has “picked up the gauntlet around open-source software”. The HSCIC and BJSS have collaborated to build the core services of Spine 2, such as electronic prescriptions and care records, “in a series of iterative developments”. Read more

What the Linux Foundation Does for Linux

Jim Zemlin, the executive director of the Linux Foundation, talks about Linux a lot. During his keynote at the LinuxCon USA event here, Zemlin noted that it's often difficult for him to come up with new material for talking about the state of Linux at this point. Every year at LinuxCon, Zemlin delivers his State of Linux address, but this time he took a different approach. Zemlin detailed what he actually does and how the Linux Foundation works to advance the state of Linux. Fundamentally it's all about enabling the open source collaboration model for software development. "We are seeing a shift now where the majority of code in any product or service is going to be open source," Zemlin said. Zemlin added that open source is the new Pareto Principle for software development, where 80 percent of software code is open source. The nature of collaborative development itself has changed in recent years. For years the software collaboration was achieved mostly through standards organizations. Read more

Arch-based Linux distro KaOS 2014.08 is here with KDE 4.14.0

The Linux desktop community has reached a sad state. Ubuntu 14.04 was a disappointing release and Fedora is taking way too long between releases. Hell, OpenSUSE is an overall disaster. It is hard to recommend any Linux-based operating system beyond Mint. Even the popular KDE plasma environment and its associated programs are in a transition phase, moving from 4.x to 5.x. As exciting as KDE 5 may be, it is still not ready for prime-time; it is recommended to stay with 4 for now. Read more

diff -u: What's New in Kernel Development

One problem with Linux has been its implementation of system calls. As Andy Lutomirski pointed out recently, it's very messy. Even identifying which system calls were implemented for which architectures, he said, was very difficult, as was identifying the mapping between a call's name and its number, and mapping between call argument registers and system call arguments. Some user programs like strace and glibc needed to know this sort of information, but their way of gathering it together—although well accomplished—was very messy too. Read more