Tuesday 30 November 2021

The DevOps Tools Engineer Certification

DevOps Tools Engineer Certification, LPI Exam Prep, LPI Exam, LPI Certification, LPI Guides, LPI Learning, LPI Certification, LPI Career

Businesses across the globe are increasingly implementing DevOps practices to optimize daily systems administration and software development tasks. As a result, businesses across industries are hiring IT professionals that can effectively apply DevOps to reduce delivery time and improve quality in the development of new software products.

To meet this growing need for qualified professionals, Linux Professional Institute (LPI) developed the Linux Professional Institute DevOps Tools Engineer certification which verifies the skills needed to use the tools that enhance collaboration in workflows throughout system administration and software development.

In developing the Linux Professional Institute DevOps Tools Engineer certification, LPI reviewed the DevOps tools landscape and defined a set of essential skills when applying DevOps. As such, the certification exam focuses on the practical skills required to work successfully in a DevOps environment – focusing on the skills needed to use the most prominent DevOps tools. The result is a certification that covers the intersection between development and operations, making it relevant for all IT professionals working in the field of DevOps.

Current version: 1.0 (Exam code 701-100)

Objectives: 701-100

Prerequisites: There are no prerequisites for this certification. However, an additional certification in the candidate’s primary area of expertise, such as LPIC-1 or a developer certification, is strongly recommended.

Requirements: Passing the DevOps Tools Engineer exam. The 90 minute exam is 60 multiple choice and fill-in-the-blank questions.

Validity period: 5 years

Cost: Click here for exam pricing in your country.

Languages for exam available in VUE test centers: English, Japanese

To receive the Linux Professional Institute DevOps Tools Engineer certification the candidate must:

◉ Have a working knowledge of DevOps-related domains such as Software Engineering and Architecture, Container and Machine Deployment, Configuration Management and Monitoring.

◉ Have proficiency in prominent free and open source utilities such as Docker, Vagrant, Ansible, Puppet, Git, and Jenkins.

Source: lpi.org

Thursday 25 November 2021

The BSD Specialist Certification

BSD Specialist Certification, BSD Certification, LPI Certification, LPI Exam Prep, LPI Tutorial and Material, LPI Career, LPI Materials, LPI Preparation

The BSD Specialist certification is part of the Linux Professional Institute (LPI) Open Technology certification program.

The exam focuses on the practical skills required to work successfully in a FreeBSD, NetBSD or OpenBSD environment and tests the knowledge and skills needed to administer BSD operating systems.

The typical BSD Specialist certification holder is a system administrator of BSD operating systems. The certification holder has an understanding of the architecture of the BSD operating systems. This includes the ability to manage various aspects of a BSD installation, including the management of user accounts and groups, processes, file systems, installed software, and client networking configuration. The candidate is experienced in using standard BSD and Unix tools on the command line. 

Current version: 1.0 (Exam code 702-100)

Objectives: 702-100

Prerequisites: There is no prerequisite certification for taking the BSD Specialist Engineer exam. However, it is strongly recommended that a candidate has more than a year of experience in administering BSD systems of various kinds.

Requirements: Passing the BSD Specialist exam. The 90 minute exam is 60 multiple choice and fill-in-the-blank questions.

Validity period: 5 years

Cost: Click here for exam pricing in your country.

Languages for exam available in VUE test centers: English

To receive the BSD Specialist certification the candidate must:

◉ Have a working knowledge of BSD operating systems: FreeBSD, NetBSD, and OpenBSD 

◉ Be able to install, manage, and configure BSD operating system

◉ Be able to configure hardware, set kernel parameters, and manage system security 

◉ Have basic knowledge in BSD system administration, job scheduling, and system automation

◉ Have basic network administration knowledge

Source: lpi.org

Tuesday 23 November 2021

Difference Between Fedora and Kali Linux

Fedora OS, developed by Red Hat, is a Linux based open-source operating system. As it is Linux based, so it is freely available for use and is open source. It uses the DNF package manager and gnome environment along with anaconda installer. It supports 3 platforms, which are Workstation Fedora designed for Personal Computers, Fedora Server designed for servers, and Fedora Atomic designed for cloud computing.

Fedora, Kali Linux, LPI Exam, LPI Tutorial and Materials, LPI Certification, LPI Learning, LPI Preparation, LPI Guides, LPI Career

Kali Linux is a Linux based open source Operating System which is freely available for use. It belongs to the Debian family of Linux. It was developed by “Offensive Security”. It was first released in March 2013 with the aim to be the replacement of the BackTrackOS. Kali comes packed with 100+ of penetration testing, security research, digital forensics, reverse engineering, and ethical hacking tools.

Difference between Fedora and Kali Linux

Fedora Kali 
Developed by RedHat.  Developed by Offensive Security.
Fedora was initially released in November 2003.  Kali Linux was initially released in March 2013. 
Fedora is used for daily use or on server or on a cloud.  Kali Linux is used by security researchers or ethical hackers for security purposes. 
The discussion forum for fedora is ask.fedoraproject.org.  The discussion forum for Kali Linux is forums.kali.org. 
Latest Fedora consists of the Gnome environment by default, though it allows you to change the same.  Latest Kali consists of the xfce environment by default, though it allows you to change the same. 
Fedora doesn’t comes packed with hacking and penetration testing tools.  Kali comes packed with hacking and penetration testing tools. 
Comes with a user friendly Interface.  Comes with a less user friendly Interface as compared to fedora. 
Fedora is a good option for beginners to Linux.  Kali Linux is a good option for those who are intermediate in Linux. 

Source: geeksforgeeks.org

Saturday 20 November 2021

Open Access Flips Hundreds of Years of Scientific Research

LPI Exam Prep, LPI Exam, LPI Tutorial and Materials, LPI Guides, LPI Career, LPI Skills
We have viewed the spirit of openness from many angles—in free software, open government, and many other trends—in the Open Anniversary series published on this LPI site during 2021. No field has been more transformed by this spirit than academic research, represented by the Open Access movement. This article discusses the major aspects of Open Access, along with the role of Creative Commons licenses.

The first article in this two-part series lays out the concepts and concerns with Open Access.

A Seismic Shift in Academic Publishing

Since the invention of the printing press, researchers have been eager to share their insights with the world by publishing articles and books. The urge to open one's research to all has become a pillar of science, reaching the point where the phrase "publish or perish" characterizes the world of research.

Yet a kind of elite access to information grew up over time. Research journals became expensive to the degree where most people outside universities, major companies, or well-established research centers found the cost of journals a barrier to learning.

Of course, all that money has gone to useful things. Journals screen submissions and conduct peer review, playing the role of responsible gatekeeper. But they also introduce their own biases, preferring positive results over negative ones, big breakthroughs over modest advances, famous research centers over lesser-known institutions, and hot topics over obscure corners of research. Other prejudices reflecting the larger society, such as relating to gender, are also hard to root out.

The internet came along and presented radically new opportunities. Authors could publish anything they wanted at any time, and could crowdsource reviews among diverse viewers instead of depending on the three peer reviewers chosen by a journal. Cloud storage made it easy to publicize data sets so other researchers could combine them (after investing effort in harmonizing their differences) and mine them for new insights.

Finally, researchers sought out informal ways to trade articles in order to bypass paywalls. Some of my reviewers emphasized the challenge posed by the widespread availability of unauthorized (or if you insist, "pirated") copies of articles as a major factor pressuring conventional publishers to change. The reviewers highlight Sci-Hub as a particularly rich alternative to paid publications. Statistics show Sci-Hub growing and being popular in both affluent and developing countries.

Although I recognize the extent of unauthorized exchanges in research papers, I would like to point out that unauthorized exchanges of software are probably even more common. Although the major proprietary software companies support free software for solid business reasons, these companies show no indication of following the path research publishers are taking to open up proprietary offerings.

Open Access results from researchers’ intrepid leap into the new era of information for all. The movement is now a well-established process documented by organizations such as the Open Access Scholarly Publishing Association, Plan S, and the Open Scholarship Initiative.

Considerations in Open Access

Moving a journal to Open Access is far more complicated than just throwing articles onto a public web site. Authors and publishers have to deal with sponsor requirements, licenses, venue, and publishing costs.

Sponsor Requirements

For many years, public criticism has grown over the privatization of government-funded research. The public was paying taxes to support the research, but the results were tucked behind expensive paywalls. An ethical objection arose, insisting that research funded this way should be available to all. Ideally, the original data (which might be even more valuable than the published paper) would be shared publicly too, subject to privacy protections.

Now major government and private institutions are requiring Open Access for research they fund. Notable examples include the National Institutes of Health, which underpin much drug development and other health research, and the National Science Foundation. Researchers and publishers need to stay aware of the requirements imposed by funders.#

Licenses

Here is where Creative Commons (discussed in the second part of this article) proves valuable. The legal team at Creative Commons have designed a set of elegant licenses that provide a range of interesting options to both copyright owners and readers. All the licenses allow the public to read, copy, and redistribute content. The licenses also require the original authors to be credited.

Additional choices face an author. The boldest among authors can allow other people to distribute updated or revised versions of the article, as with free software. One can see the value of this for providing updates or additional data to a research topic. But there is also an iron-clad tradition in academia of articles as a "version of record." The original article must be archived someplace to preserve the integrity of scientific inquiry. In order to prevent the risk of confusion, or the risk that their ideas will be taken in a direction that is repugnant to them, authors can choose a "no derivatives" clause in Creative Commons.

Venue

The perceived significance of an article is affected by the site where it is posted: an author's personal site, a university or research institution, a conference site, or the publisher's official web page.

Most publishers allow authors to post pre-publication versions or "preprints" on web sites maintained by the authors or their institutions. The implication is that this version is not as trustworthy as the article that has been through peer review and editing—thus becoming the version of record—but is still useful. The author also often posts the final version under this policy, which is called Green Open Access.

When the publisher puts the version of record on a public web site without a paywall, it is called Gold Open Access. Normally, the venue is the publisher's site, putting an additional stamp of approval on the article. The authors or their institutions usually pay an article processing charge (APC) to cover the publisher’s costs. There are other subtle stages in publication, covered in the site to which I already referred.

Finally, Diamond Open Access funds publication entirely from external sources such as grants, putting articles online for free and charging neither authors or readers.

Publishing Costs

According to Scott Delman, director of publications at the nonprofit ACM, “Many of the largest publishers are for-profit corporations generating annual profit margins exceeding 30%, while there remains a very long tail consisting of hundreds or thousands of smaller society and privately owned nonprofit publishers.” But even nonprofits have editorial and publishing costs that are traditionally covered by subscriptions that can run into thousands of dollars a year. 

Deprived by Open Access of monopoly control over distribution, publishers fund their efforts through the APC. But publishers avoid charging individual authors, who would find the charge a high barrier to publication. Instead, publishers usually collect the APC from the research institutions, who benefit from the fame of their authors and who can afford a couple thousand dollars to publish each article.

Gold Open Access does bring the risk of "perverse incentives," according to Lorena Barba, an aeronautics engineer and editor-in-chief of the IEEE technical magazine Computing in Science and Engineering. Barba worries that, because each article published brings in revenue, journals may accept low-quality articles to bulk up their offerings. Possibly, Gold Open Access will exacerbate the familiar problem of low-quality journals that do little or no review but exploit authors by presenting the journals as legitimate research outlets. Barba herself cofounded two Diamond Open Access journals and is also a strong supporter of Green Open Access because it allows the public to see articles as soon as they are written.

LPI Exam Prep, LPI Exam, LPI Tutorial and Materials, LPI Guides, LPI Career, LPI Skills

Barba also points out that the normal funding model for Gold Open Access, shifting costs from readers to authors and their institutions, fails to reduce the gap between affluent and low-income regions. It is now the institutions who represent potential authors in low-income regions who are at a disadvantage. Furthermore, journals should make special dispensations for authors who are not represented by an institution.

RightsLink is popular among publishers for simplifying the collection of APCs. It allows sophisticated practices such as splitting fees among multiple institutions.

RightsLink was set up to support Open Access by the Copyright Clearance Center (CCC), an institution established in the 1970s before the internet was in widespread use. I remember, being in graduate school in the 1980s, that professors were assigning fewer books in class and turning more and more to photocopies of journal articles because they reflected the latest discoveries in a field. Massive amounts of photocopying presented a challenge to copyright law, stretching the concept of fair use. Copyright holders worked out a deal with colleges whereby the colleges paid bulk fees to allow photocopying, the whole system administered by the CCC. With Open Access, costs are shifting from consumers to producers of information, and the CCC is evolving with the times.

The second part of this article looks at the computer field in particular for examples of Open Access in action.


Source: lpi.org

Tuesday 16 November 2021

Grounding For Open Source Foundations: An Interview with Martin Michlmayr

LPI Exam Prep, LPI Tutorial and Materials, LPI Guides, LPI Certification, LPI Career, LPI Prep, LPI Study Materials, LPI Central
Foundations play a crucial role in open source. Few free software projects can set up a non-profit corporation and legal protection for their code, organize a board of directors to handle all their administrative needs, or raise the necessary funds. So we urgently need the Apache Foundation, Eclipse Foundation, Linux Foundation, and others.

Martin Michlmayr, who has put in stints as Debian Project Leader and president of Software in the Public Interest, released a 58-page report titled Growing Open Source Projects with a Stable Foundation in April 2021. Among its broad range of topics are governance, stability, community growth, financial and legal considerations, and the pressures on the foundations themselves. This report is well worth a read for anyone running a free software project or working with a foundation in that area. People interested in the foundations themselves will also benefit from a research report by Michlmayr going into some depth about them.

I interviewed Michlmayr to assemble some basic ideas that free software advocates should have when thinking about their stability.

You cover a very wide range of functions for foundations. Which are fulfilled well currently, and which need more focus or effort?

Martin Michlmayr: It depends on the organization. A lot of foundations suffer from a lack of resources, which determines the kinds of services they are able to provide.

Generally, the functions that are most important are fairly well covered. This includes accepting donations, paying for expenses, taking care of a lot of the administrative work that projects need (such as renewing trademarks and domain names), etc. A number of other functions, such as marketing, are generally not covered so well.

Some foundations (notably the Linux Foundation and Eclipse Foundation) focus on industry collaboration. They do a great job of providing a neutral venue where companies can collaborate. They also provide help to companies to get started with open source.

This role for a foundation, as a neutral venue for collaboration, is becoming increasingly important as open source evolves from a hobby into a way for companies to solve problems better, faster, and at a lower cost by collaborating with others who have a similar problem.

Suppose I've just started a free software project showing promise. At what point should I look for help from a foundation? What does my project need to have in place?

Michlmayr: A challenge for new projects is that most foundations don't cater to them. Many foundations expect projects to be well-established already, although a number of organizations offer incubation to new projects.

Generally, new projects should think ahead and consider how things will change as they grow. They should focus a lot on getting governance right.

Are there perhaps too many open source foundations now? Or should there be more? Are current ones evolving to meet new challenges, or do the challenges call for new foundations?

LPI Exam Prep, LPI Tutorial and Materials, LPI Guides, LPI Certification, LPI Career, LPI Prep, LPI Study Materials, LPI Central
Michlmayr: Running a foundation is a lot of work, and we saw in the past where people started a new organization without properly understanding how much work it would be -- especially work few people enjoy doing (such as the extensive paperwork). I believe there's a better understanding of the burden nowadays, and most organizations are created because they fill a specific need that couldn't be met as easily through an existing organization.

Are there too many? Possibly, and we've seen some organizations become virtual organizations within another foundation so that they don't need to do their own paperwork. The X.Org Foundation, for example, joined Software in the Public Interest and operates as a virtual organization now.

The Linux Foundation supports a "foundation-in-a-foundation" model that makes it easy to start new organizations by using the existing infrastructure and capabilities of the LF. I think we'll see more of this.

Open Collective is another interesting example: they provide infrastructure for receiving and spending funds; projects can easily sign up and make use of this infrastructure immediately. This meets the needs of many projects, in particular smaller ones.

 Source: lpi.org

Tuesday 9 November 2021

Simone “Simo” Bertulli: Lpic-3 Security - How to Approach the Certification

LPIC-1 Certifications, LPIC-2 Certifications, LPIC-3 Certifications, LPI Exam, LPI Exam Prep, LPI Tutorial and Materials, LPI Guides, LPI Certification
When you are LPIC-2 certified and start looking at the highest level of certification in Linux Professional Institute (LPI), the LPIC-3 specializations, you are faced with a choice. On the one hand, a better and more extensive academic preparation would help you build a solid knowledge background; on the other hand, you could specialize, aiming to become a "guru" on a specific theme.

This article introduces you to LPIC-3’s Security specialization.

The big LPIC-3 reshuffle

There are currently three LPIC-3 paths:

LPIC-3 Security

◉ LPIC-3 Mixed Environments

◉ LPIC-3 Virtualization and High Availability

The latter will soon be replaced by two distinct certifications:

◉ LPIC-3 Virtualization and Containerization

◉ LPIC-3 High Availability Systems and Storage

In short, choices for specialization provided by LPI certifications are getting more varied. This is progress that reflects an enormous amount of work at LPI on developing its training programs.

The road to security

After I obtained the LPIC-3 Virtualization and High Availability certification, confirming my skills in those topics, I started studying for the LPIC-3 Security Exam. Working in a Security Operations Center, I considered this certification a reasonable step due to the extensive coverage of the certification topics.

But it is not always easy to understand how to start the preparation for such a complex exam. Let's navigate through it together.

The first thing to do is to go to check the exam Objectives. You will find the following macro-topics:

◉ Encryption

◉ Host security

◉ Access control

◉ Network Security

Each of these topics contains an increasingly detailed list of the covered Objective.

Those who already work in the field of cyber security or at least in the ICT security context, have already addressed some of these topics, but now need to acquire a Linux-based point of view about the topics. At this point, your modus operandi should follow two straightforward steps:

◉ Search for a bibliography of up-to-date information

◉ Implement a virtual laboratory.

Among some great books that help cover most of the exam topics, I would like to mention the following:

◉ Practical Linux Security Cookbook - Second Edition

◉ Mastering Linux Security and Hardening - Second Edition

◉ SELinux System Administration - Third Edition

Well, yes, I know: I have brought to your attention a book that is all (!!!) about SELinux. In addition to being an essential part of the exam and therefore of the security area, SELinux is one of the main obstacles that could complicate work for those who do not face the topic with the right attitude and knowledge.

LPIC-1 Certifications, LPIC-2 Certifications, LPIC-3 Certifications, LPI Exam, LPI Exam Prep, LPI Tutorial and Materials, LPI Guides, LPI Certification
The other books cover the topics you need to know to pass the exam and help you approach system administration in general from a much more security-oriented perspective.

Once you have grabbed those manuals, you can build a virtual laboratory that can help you test and deepen your knowledge of all the topics to be addressed, step by step. You just need a PC and a few virtual machines.

Given the exam’s structure, it’s a good idea to create at least two virtual instances: for example, one with CentOS and the other one with Ubuntu or Debian.

Among the various topics, I believe that the following should be treated with particular attention:

◉ User management and authentication

◉ Certificates, PKI, and the related protocols (SSL, TLS)

◉ Encrypting DNS

◉ Package filtering

Having the LPIC-2 certification puts you in the perfect position to scale up to the next level. Ideally, a working experience with IT security of at least three years will help you navigate the broad complexity of the exam.

Well: brace yourself, have fun!!!

Read More: Simone “Simo” Bertulli: Six years in the company of LPI

Source: lpi.org

Saturday 6 November 2021

Why I started... and ended up loving open source software

LPI, LPI Exam, LPI Exam Prep, LPI Tutorial and Material, LPI Guides, LPI Career, LPI Certification, LPI Preparation
Twenty-two years ago, I attended a few lessons about a "new" operating system, Red Hat Linux 4.2. At that time, my notes about the training were basic commands, enough to fill a little sheet of paper: my first cheat sheet for Linux.

A couple of years later, I was still trying to figure out how to configure devices, a graphical interface, and find real use cases for the operating system… In 2001 I started working as the IT manager for a new institute named Cenfotec, in San José, Costa Rica.

This institute was making a difference, with a project to supply wireless connectivity for all the students, one of the first brand new wireless networks based on 802.11b in the entire country: can you imagine that?

Simultaneously, the most curious students started playing around with versions of Linux like Mandrake: that was a challenge for me, because, as I was supposed to work with them, many of the computers only had drivers for Windows. I started doing some research about the drivers and the kernel modules, I made many tests, and the trial and error gave me satisfactory results.

A life-changing moment 

After three months all the computers running Linux were working smoothly. Now I can say that moment changed my life forever: I saw the incredible potential you can reach using an open source operating system.

Pronto, all the solutions for everything you need are now at your fingers, powered by a dedicated community.

The development environment

My first steps in the world of web development were with Apache Tomcat, a small but powerful software, the one I learned to make web applications (with JSP and Servlets) on, falling deeply in the Java world. I had to install that server and did not know how it worked: I started reading and researching and found much information.

It was like love at first sight. After web developing, it wasn't easy to rollback my mind and get back at developing with client-server or windows-based applications. The opportunities were endless, but that was technology ahead of its time.

I think that for everyone there's a before and an after at the time Apple launched the iPhone: it was a disruptive technology, which moved the floor of many companies and completely changed an environment that dominated by proprietary and desktop software; it was indirectly the thing that ignited the spark for one of the as many projects as Android to take off; besides, made possible for a series of technologies to explode. Many of them had a common denominator: open source.

Programming languages and databases empowered gigantic applications such as social networks, which no longer needed a web page, and had their mobile apps.

All of this further reinforced my idea that anything you imagine can be done with open source software, and since then, open source software is part of everyday life.

Open source software as a business opportunity

Open source software has made me grow in my professional life because it allows me to be more competitive when I supply a technological solution to a client.

The fact of using operating systems, programming languages, databases, tools, and software that does not require the disproportionate payment of licenses, means the implementation costs of a project are proportional to your knowledge and effort. You can get more value for your work, especially if you are working with startups or small businesses which can't afford an expensive solution.

Last year I was invited to present a call centre solution with a new client. The answer I gave them was based on VICIDial; it was an exciting challenge because I installed a Proxmox server in a cluster to offer high availability, the VICIdial is based on the Linux openSUSE distribution, the database is MariaDB, the IP based telephony software in Asterisk and the application running on an Apache HTTP server with PHP and JavaScript, it is a full-stack solution in every way you see.

You can say: as open as it can be… 

The client saw the software and was able to verify that the software met all the requirements they had.

Two hours after the presentation, I received the call asking when we would start the project. To date, the project has grown even more: the client is satisfied with the solution, which has generated a lot of work for me.

The knowledge base is infinite

LPI, LPI Exam, LPI Exam Prep, LPI Tutorial and Material, LPI Guides, LPI Career, LPI Certification, LPI Preparation
Today, if you are a professional in information technology, a developer, an infrastructure manager, network administrator, data scientist, some facts are irrefutable, you must have discipline, you need continuous learning, and, the most important thing, you cannot go alone.

What I like the most about the open source software community is the ability to solve anything, and the solutions you find evolving over time, as the knowledge becomes specialized and the software is better. That feeling that people are sharing their knowledge and experience to help someone else is something invaluable.

My recommendations

Choose a topic or technology, learn it, then try to teach it; share your knowledge, and let other people share their knowledge with you too; support open source projects when you can, buy support, donate when you think it is necessary to reward the effort of very good people behind that code.

Source: lpi.org

Tuesday 2 November 2021

Why Free and Open Source Software is So Highly Valued

LPI, LPI Exam, LPI Exam Prep, LPI Tutorial and Material, LPI Preparation, LPI Career, LPI Guides, LPI Learning

The millions of projects on GitHub (just the largest of several code sharing sites) prove that people love to share software. Even though not all the projects have free licences, their availability for public examination shows that code sharing meets a powerful need. Meanwhile, free software is driving the most important trends in computing: virtual systems, web sites, machine learning, and more.

This article covers our love of free and open source software. It looks at the traits of free software from the following viewpoints:

◉ Why developers prefer free software

◉ Why enterprises prefer free software

◉ Why the public should prefer free software

◉ Drawbacks of free software

Why Developers Prefer Free Software

Free software is what every developer gravitates toward. How could a programmer prefer software that's locked up and impossible to look at? Developers are often the kind of people who, as kids, dismantled household appliances to learn how they worked. The developers bring this inquisitiveness to software. They hate mysterious bugs. They want the freedom to make a system fit their needs, whether by tweaking an option or adding a whole new branch.

Free software is malleable in pursuit of the tiniest purposes as well as the grandest ones. If you see a valuable enhancement, you don't have to wait for a company to figure out a business reason to make the enhancement—you just recruit a team to do it.

Developers certainly appreciate the increased chances offered by free software to win over new contributors. These contributors offer their services because they know the software is equally available to everybody and won't be hijacked by a single organization. But the appeal of free software goes far beyond the mere quantity of developers--it concerns the diversity of developers as well. Let’s see why

The possibilities created by software freedom are particularly treasured by under-resourced places with few resources or with small populations who have big needs. These needs might never even be heard by companies that make proprietary software. Certainly, they'd never find reason to devote their highly paid staff to providing a feature the community wants. But civic-minded local programmers can adapt free software to community needs.

Developers also like to build communities, and free software most effectively underlies such communities. Because users know that they can have a say in the development of the software, they are motivated to join discussions, advocate for their needs, evangelize for the project, and draw closer to other members of the community.

In short, free software stimulates people to learn, to take responsibility, and to find solutions. It provides power and autonomy while encouraging activism and a desire to contribute.

Why Enterprises Prefer Free Software

Although your career can certainly benefit from an understanding of Oracle databases or AWS APIs, free software is the hottest area for hiring. One reason is the incredible functionality provided by free software: Linux, Kubernetes, Python, etc. But freedom itself draws companies too.

The main attraction of free software is that you don't have to worry about lock-in. Proprietary vendors make some impressive software products, but there remains a risk that they'll take the product in a direction you don't like. Proprietary software offers many horror stories about double-digit hikes in costs, crucial features stripped out without warning, and other onerous requirements.

Developers who like free software, as described in the previous section, persuade their employers of free software's advantages. And because free software welcomes deep study, companies enjoy a large pool of talent to draw from when adopting popular free software projects.

Like developers, companies that support free software—through money or through programmer time—can benefit from having a say in its direction and priorities.

Why the Public Should Prefer Free Software

Free software today is a major contributor to development throughout the world. As mentioned earlier, clever tinkerers in many underserved areas combine open hardware with open software to create products such as health tests at a hundredth the cost of the bloated products offered by proprietary companies from more affluent countries.

Free software doesn't try to control people. When people depend on proprietary software, the vendor can dictate what users are and are not allowed to do. Free software licenses reject such domination.  Free software is also less likely to be used for the surveillance that leads to abuses ranging from the biased delivery of ads to the distortion of political campaigns.

Challenges of Free Software

Of course, the development processes behind free and open source software present difficulties.

Funding has always been a headache. Essentially, projects depend on free-will donations of time and money, whether from individuals or from corporate backing. Most users are perfectly content to be free riders and never contribute a penny to maintenance. Many free software projects shrivel up and disappear for lack of support.

LPI, LPI Exam, LPI Exam Prep, LPI Tutorial and Material, LPI Preparation, LPI Career, LPI Guides, LPI Learning
On projects that persist, developers often become employees of companies that use the software and recognize the value of paying staff to contribute. These companies derive their revenue from other sources, including proprietary software. Other free software developers make a living as consultants or offering training.

The other major problem with free software is the uncertain timing of feature releases. Because the projects depend on volunteers or on the staff of companies who have other priorities, a feature that you want can be delayed for years. This is not always bad. In contrast, many proprietary companies release buggy software in order to meet the deadlines they promised their customers, or just to guarantee continued income.

Finally, many people and institutions still don't trust free software or the processes behind it. Even after spectacular multimillion-dollar failures, such as the FBI Virtual Case File project or the Department of Veterans Affairs health record upgrade, major institutions continue to put their faith in the promises of proprietary companies instead of free software processes. All who appreciate free and open source software must continue to push for more trust.

Source: lpi.org