Language Selection

English French German Italian Portuguese Spanish

Slackware review

Filed under
Slack

One of the most common statements about Slackware is that, it is difficult to maintain, and not user friendly. This is only partially true and depends on what is easy for you. If you know nothing about Linux then it may be complicated to start with Slackware, but if you know a little bit about Linux, then it could actually be easier to have a server on Slackware than for example Fedora or Ubuntu. Why?. Well mainly because it is more difficult to break things in Slackware than in others, the lack of a dependency resolution official tool, makes installing and maintaining software more time consuming, but at the same time, more stable. So if easy for you means less time finding and installing software, then Slackware is not easy, but if on the other hand easy for you, means less problems and down times, then Slackware may be your solution.

So, Slackware is not for experienced users only, but it certainly doesn’t do everything for you like Ubuntu, Fedora, PCLinuxOS or others.

Packages

Introduction

All packages in slackware are vanilla, it does not have the huge number of packages available as in Debian, but you can always compile them by yourself. To compile the software not officially available in Slackware repository we have the great help of slackbuilds.org. This is a community driven project, where you can find scripts to create the Slackware binaries from the original sources.

rest here




More in Tux Machines

Leftovers: OSS

  • GENIVI Alliance launches new open source vehicle simulator project
  • Choosing the right metrics for your project
    Last month we discussed setting goals for your community metrics program. These goals serve as a constant reminder of what you want to achieve in the program and should be used as metrics themselves when deciding exactly what you are going to measure. This month we'll document a basic strategy for deciding what to measure, and give examples of specific community metrics we've used in practice. Using our knowledge of our community and the goals we previously came up with, we'll make sure the metrics we choose are relevant.
  • An Open Source Shopping Cart Can Boost Your Online Commerce Efforts
  • Open Source Projects Must Work Together to Survive
    Open source software is in danger of being beaten at its own game by upstart services that are tightly integrated, less complex, and easier to use. That message was at the heart of the cautionary tale told by Stephen O’Grady in his keynote at this year’s ApacheCon North America in May. O’Grady, Principal Analyst & Cofounder of RedMonk, recalled his years as a systems integrator, pointing out that open source software took a big bite out of the enterprise software market when it became more accessible and easier to use.
  • Contributing to an Open Source Project
    If you’re interested gaining some tips and insights into how to contribute to open source, this video of a presentation given on September 19 at the JavaOne conference in San Francisco by Gunnar Wagenknecht, a software engineer at Salesforce, and Wayne Beaton, director at the Eclipse Foundation, might be useful to you.
  • Facebook Debuts Open Source Detection Tool for Windows
    Facebook debuted the open source tool in 2014 as cross-platform, but for the last two years it was only supported on Ubuntu, CentOS, and Mac OS X operating systems. Facebook isn’t the biggest Windows shop, but the company confirmed in March that because so many users were asking for it, it was building a version of the tool for Windows 10.
  • Pentaho aims to alleviate big data pains
    Seemingly retaining its original name, technology stack and altogether vibe-ness with competancy over a year now since being acquired by Hitachi Data Systems, Pentaho is putting out the ‘data developer/analyst’ messages and tuning up its own integration prowess in the process.
  • The broken promise of open-source Big Data software – and what might fix it
  • Open source application portal adds new ITS applications for download
    The Open Source Application Development Portal (OSADP) web-based portal provides access to and supports the collaboration, development, and use of open-source ITS-related applications. The OSADP has added a number of new ITS-related applications that are available free to the public, including:
  • Wyoming's open source enterprise code library a secret no more
    Wyoming’s 250-person Enterprise Technology Services (ETS) group knew it had a good thing in its Enterprise Extensible Code Library, but it chose to keep things under wraps outside of the state until last week when members of that team attended an annual confab for state government CIOs. It was at the National Association of State Chief Information Officers (NASCIO) convention in Orlando that the ETS code library project was honored with a Recognition Award for Enterprise IT Management Initiatives, and the inquiries from other states and organizations started streaming in.
  • Industrial IoT leaders work towards interoperability and open source collaboration
  • GE and Bosch Sign Agreement for Interoperability and Open Source Collaboration
  • Free PPMP from Bosch makes Industry 4.0 open for all
  • Inside the Drone Journalism Lab’s open source operations manual
    Across the world, journalists are increasingly using drone technology to augment their reporting at a fairly inexpensive price. In order to help journalists become more adept drone users, the University of Nebraska-Lincoln’s Drone Journalism Lab recently released a free operations manual online. The manual, produced by Matt Waite, founder of the Drone Journalism Lab, is open source and Creative Commons licensed.
  • Open Source Malaria’s First Paper
    Open Source Malaria (OSM) publishes its first paper today. The project was a real thrill, because of the contributors. I’d like to thank them. Skepticism about open source research is often based on assumptions: that people will be too busy or insufficiently motivated to participate, or that there will be a cacophony of garbage contributions if a project is open to anyone. I’m not sure where such assumptions come from – perhaps people look first for ways that things might fail. We can draw upon many experiences of the open source software movement that would suggest such assumptions are poor. We can draw on successful examples of open collaboration in other areas of science, such as the Human Genome Project and the projects it has spawned, as well as examples in mathematics and astrophysics. This OSM paper addresses open source as applied to drug discovery, i.e. experimental, wet lab science in an area where we normally expect to need secrecy, for patents. It is based on the experience of 4-5 years of work and describes the first series examined by OSM.

Linux and FOSS Events

  • Report for Software Freedom Day 2016 – China Academy Science
    This year I am asked to present SFD in China Academy Science by the company, so unlucky I am not proper to deliver a Fedora talk then. I bring some DVDs and stickers there, as well as a roll up poster. However there are people asking questions about Fedora so finally I still do some Q&A after the event. SFD in China Academy Science this year is hold in Huairou Campus, suburbs of Beijing. So with another Red Hatter, Shiyang, we took train there. Their campus is not easy to find and by the time we arrived at the event it’s 10 minutes before the start of the event. Talks started on 2:00 PM. After the hostess introduced the event, Shiyang is the first to talk. He introduces the basic usage of Git and Github. During the Q&A part of his talk, I found that in fact most students not paying much attention to distributions already. They are just users of Linux.
  • OpenDaylight Symposium 2016
  • Keynote: Join or Die! - Stephen O'Grady, Principal Analyst & Cofounder, RedMonk

Mozilla, Firefox, and FirefoxOS

  • B2G OS and Gecko Annoucement from Ari Jaaksi & David Bryant
    In the spring and summer of 2016 the Connected Devices team dug deeper into opportunities for Firefox OS. They concluded that Firefox OS TV was a project to be run by our commercial partner and not a project to be led by Mozilla. Further, Firefox OS was determined to not be sufficiently useful for ongoing Connected Devices work to justify the effort to maintain it. This meant that development of the Firefox OS stack was no longer a part of Connected Devices, or Mozilla at all. Firefox OS 2.6 would be the last release from Mozilla. Today we are announcing the next phase in that evolution. While work at Mozilla on Firefox OS has ceased, we very much need to continue to evolve the underlying code that comprises Gecko, our web platform engine, as part of the ongoing development of Firefox. In order to evolve quickly and enable substantial new architectural changes in Gecko, Mozilla’s Platform Engineering organization needs to remove all B2G-related code from mozilla-central. This certainly has consequences for B2G OS. For the community to continue working on B2G OS they will have to maintain a code base that includes a full version of Gecko, so will need to fork Gecko and proceed with development on their own, separate branch.
  • Firefox 53 Will Drop Support for Windows XP and Windows Vista
    Software companies are one by one giving up on Windows XP support for their products, and now it appears that it’s Mozilla’s turn to switch the focus to newer versions of Windows. Firefox 53 will be the first version of the browser which will no longer support Windows XP and Windows Vista, so users who haven’t yet upgraded to Windows 7 or newer will have to either stick with Firefox 52 or move to a different browser.
  • Boot 2 Gecko Being Stripped From Mozilla's Codebase
    At the end of 2015 Mozilla effectively put an end to Firefox OS / Boot 2 Gecko by concluding things weren't working out for Mozilla Corp and their commercial partners to ship Firefox OS smartphones. All commercial development around it has since stopped and they are now preparing to strip B2G from the mozilla-central code-base. The news to report on now is that Ari Jaaksi and David Bryant have announced, "Today we are announcing the next phase in that evolution. While work at Mozilla on Firefox OS has ceased, we very much need to continue to evolve the underlying code that comprises Gecko, our web platform engine, as part of the ongoing development of Firefox. In order to evolve quickly and enable substantial new architectural changes in Gecko, Mozilla’s Platform Engineering organization needs to remove all B2G-related code from mozilla-central. This certainly has consequences for B2G OS. For the community to continue working on B2G OS they will have to maintain a code base that includes a full version of Gecko, so will need to fork Gecko and proceed with development on their own, separate branch."

Blockchain Going Mainstream