Download Fedora ARM 29

Fedora is the next generation Linux distribution from Red Hat.

Fedora is now available from Red Hat and at distinguished mirror sites near you, and is also available in the torrent.

Fedora has expanded in this release to four binary ISO images and four source ISO images, and is available for both x86-64 and i386 and also PPC machines.

The Fedora Project is a Red-Hat-sponsored and community-supported open source project. It is also a proving ground for new technology that may eventually make its way into Red Hat products. It is not a supported product of Red Hat, Inc.

The goal of The Fedora Project is to work with the Linux community to build a complete, general purpose operating system exclusively from free software. Development will be done in a public forum. The project will produce time-based releases of Fedora Core about 2-3 times a year with a public release schedule.

The Red Hat engineering team will continue to participate in the building of Fedora Core and will invite and encourage more outside participation than was possible in Red Hat Linux.

By using this more open process, we hope to provide an operating system that uses free software development practices and is more appealing to the open source community.

Source

gRPC Load Balancing on Kubernetes without Tears | Linux.com

Many new gRPC users are surprised to find that Kubernetes’s default load balancing often doesn’t work out of the box with gRPC. For example, here’s what happens when you take a simple gRPC Node.js microservices app and deploy it on Kubernetes:

While the voting service displayed here has several pods, it’s clear from Kubernetes’s CPU graphs that only one of the pods is actually doing any work—because only one of the pods is receiving any traffic. Why?

In this blog post, we describe why this happens, and how you can easily fix it by adding gRPC load balancing to any Kubernetes app with Linkerd, a CNCF service mesh and service sidecar.

Read more at Kubernetes Blog

Click Here!

Source

How to Use Debian Backports

The software packages in a Debian stable version is very old compare to other distributions like Arch Linux or even Ubuntu. Debian stable releases are very stable and secure as it only includes thoroughly tested software packages. To ensure stability and security, new software packages are not used in Debian stable versions as the Debian team needs time to test them and make sure these packages meets the stability and security requirements of Debian stable releases.

So using old version of software packages is good in a way. If you’re looking for bleeding edge software packages in Debian, then one alternative is Debian testing releases. Debian testing has more up to date software packages. But don’t expect it to be like Arch Linux.

Let’s say, you need the stability of Debian stable and still need some specific up to date software packages which is available in the Debian testing releases. Well, that’s when Debian Backports package repository comes in. According to the official website of Debian, the Debian Backports packages are packages from the Debian testing release (or the next version of Debian) adjusted and recompiled for using in Debian stable releases.

The official website of Debian also states that, if you use Debian Backports packages, then upgrade to the next Debian release (when it’s released) will not cause problems at all as the packages are already available there. There is a little bit problem with Debian Backports packages. The packages are not extensively tested as in Debian stable packages. Again, Debian Backports packages may conflict with your Debian stable packages. So you should be careful when using Debian Backports packages.

Debian recommends you use only the packages you need from the Debian Backports package repository. You should not use all the available Backports packages on Debian stable.

In this article, I will show you how to use Debian Backports package repository on your Debian stable release. I will be using Debian 9 Stretch (which is the latest version of Debian stable release at the time of this writing) in this article. So Let’s get started.

Debian Backports package repository contains a lot of Debian packages. You can search to find out whether the package of software version you’re looking for is available in the Debian Backports package repository from your web browser.

First, go to the official website of Debian Backports package repository at https://backports.debian.org/Packages/

Then, type in the package name and click on search. If the package is available in the backports package repository, it should show up.

Adding Debian Backports Package Repository to Debian 9 Stretch:

In this section, I will show you how to add the Debian Backports package repository on your Debian 9 Stretch stable release. First, open up a Terminal and run the following command:

$ echo “deb http://ftp.debian.org/debian stretch-backports main” |
sudo tee /etc/apt/sources.list.d/backports.list

The Debian backports package repository should be added to your Debian 9 Stretch machine.

Now, update the APT package repository cache with the following command:

As you can see, the APT package repository cache is updated and it included the Debian backports package repository as well.

Adding Debian Backports Package Repository to Debian 8 Jessie:

In this section, I will show you how to add the Debian Backports package repository on your Debian 8 Jessie stable release.

First, open up a Terminal and run the following command to add the Debian Jessie Backports package repository to your Debian 8 Jessie machine:

$ echo “deb http://ftp.debian.org/debian jessie-backports main” |
sudo tee /etc/apt/sources.list.d/backports.list

Debian Backports package repository should be added to your Debian 8 Jessie machine.

Now update the APT package repository cache of your Debian 8 Jessie machine with the following command:

As you can see, the APT package repository cache is updated and it also includes the Debian Backports package repository.

Installing Packages from Debian Backports Package Repository:

By default, all backports package repositories are disabled on Debian. If you want to install a package from Debian backports package repository, you have to tell the APT package manager that you really do want to install a package from Debian backports package repository specifically. That’s a great safeguard.

To search for a package (let’s say owncloud) in the Debian backports package repository, run the following command:
On Debian 9 Stretch:

$ sudo apt -t stretch-backports search owncloud

On Debian 8 Jessie:

$ sudo apt -t jessie-backports search owncloud

As you can see, the backports repository packages are listed.

To install a package (let’s say owncloud-client) from Debian backports package repository, run the following command:

On Debian 9 Stretch:

$ sudo apt -t stretch-backports install owncloud-client

On Debian 8 Jessie:

$ sudo apt -t jessie-backports install owncloud-client

Now, press y and then press <Enter>.

As you can see, the packages are being downloaded from the Debian Backports package repository.

As you can see, the owncloud-client is installed from the Debian backports package repository.

As you can see, the ownCloud GUI client I just installed from the Debian backports package repository runs just fine.

Removing Packages from Debian Backports Package Repository:

If you want to remove a package that you installed from the Debian backports package repository, then this section is for you. To remove a package (let’s say owncloud-client) that you installed from the Debian backports package repository, run the following command:

On Debian 9 Stretch:

$ sudo apt -t stretch-backports remove owncloud-client

On Debian 8 Jessie:

$ sudo apt -t jessie-backports remove owncloud-client

Now, press y and then press <Enter>.

The owncloud-client package should be removed.

Removing Debian Backports Package Repository:

If you’ve followed this article to add Debian backports package repository on your Debian 9 Stretch or Debian 8 Jessie machine, then you can remove it very easily with the following command:

$ sudo rm -v /etc/apt/sources.list.d/backports.list

Debian Backports package repository should be removed.

Now, update the APT package repository cache with the following command:

The APT package repository cache should be updated.

So, that’s how you use Debian backports package repository on Debian. Thanks for reading this article.

Source

Linux Today – Why VMware is Acquiring Heptio and Going All In for Kubernetes

Nov 07, 2018, 09:00

VMware is the company that did more than perhaps any other to help usher in the era of enterprise server virtualization, that has been the cornerstone of the last decade of computing. Now VMware once again is positioning itself to be a leader, this time in the emerging world of Kubernetes-based, cloud native application infrastructure.

Complete Story

Source

You can now buy Linux on Microsoft’s Store

WLinux is the first commercial version of Linux, more precise the Windows Subssystem for Linux, on the Microsoft Store. It is advertised as a “fast Linux terminal environment for developers and pro-users built on Windows Subsystem for Linux (WSL) on Windows 10” and available for $19.99 on the Microsoft Store.

WLinux is not the first Linux-based application for Windows 10; users of the operating system can install Ubuntu, Debian GNU/Linux and other Linux versions for the Windows Subsystem for Linux as well from the Store.

The Windows Subsystem for Linux integrates Linux distributions into the Windows 10 operating system so that these become available. The implementation is fairly limited at this point in time as you are limited to running command line tools and some tools or applications even in the latest version of Windows 10 and Windows Server 2019.

Windows 10 version 1809 includes a new option to run a Linux shell from Explorer. You need to hold down the Shift-key before you right-click on a folder to use the “Open Linux shell here” option.

The installation of Linux on a Windows 10 PC does not provide full access to the desktop environment.

wlinux

WLinux was optimized to run on the Windows Subsystem for Linux and that is probably the main reason why it is the first commercial Windows Subsystem for Linux application. The distribution uses Debian Gnu/Linux as its core.

The developers of WLinux removed some packages such as systemd from the image in an effort to reduce the overall size of the image and manageability.

The Linux environment for Windows 10 includes the setup tool wlinux-setup to customize environment-specific preferences using it.

It enables users to choose the default text editor, unpack development environments such as NodeJS, Python, Go or Ruby, or manage Windows and Azure deployments using PowerShell and azure-cli.

WLinux includes support for wslu, a tool collection for Linux on Windows 10 that includes five tools currently. The utilities may be used to redirect links to the default Windows web browser, convert Windows paths, or create shortcuts on the Windows desktop.

Support is not exclusive, however, as distributions such as Ubuntu, Debian, or Suse Linux Enterprise Server support it as well.

Other features of interest include:

  • Support for graphical Linux applications.
  • Apt package functionality to install open source packages from Debian repositories.
  • Promise to patch Windows Subsystem for Linux bugs faster than any other Linux distribution available for Windows 10.

The money that is earned from sales flows directly into the project to finance development.

Purchases of WLinux in the Microsoft Store pay for a team of open source indie developers to add new features, test and release builds, evaluate WSL-related CVEs, and provide user support.

Additional information is available on the project’s official GitHub page.

Now You: What is your take on the Windows Subsystem for Linux?

Summary

You can now buy Linux on Microsoft's Store

Article Name

You can now buy Linux on Microsoft’s Store

Description

WLinux is the first commercial version of Linux, more precise the Windows Subssystem for Linux, on the Microsoft Store.

Source

Download Fedora Server 29

Fedora is a well known and open source Linux operating system that is sponsored by Red Hat, a company that is a stable, powerful and fast operating system that can be used as the main OS for your everyday tasks. It is completely free to use, share and study.

Fedora is an enormous project with hundreds of developers and tens of thousands of community members worldwide. While the main Fedora edition features the GNOME desktop environment, the project is distributed in multiple editions, with the KDE, Xfce, LXDE and MATE desktop environments.

But these are only the official editions, as there are also various community spins that can be downloaded via Softpedia or from the project’s homepage. The Fedora Server edition reviewed here is an official edition that supports both the 32-bit (i386) and 64-bit (x86_64) architectures.

Available for download as installable-only DVDs

Being designed to be used as only on server machine, Fedora Server is available for download only as installable-only DVD ISO images, which means that it does not include a graphical desktop environment, but only a command-line one. From the boot menu you will be able to start the installation in graphical mode, as well as to test the integrity of the DVD (if booting from a DVD media), as well as to access advanced boot options like rescue mode, booting from a local drive or running a memory test.

Installing Fedora Server

As mentioned, the installation of Fedora Server takes place in graphical mode, which means that if you’ve installed Fedora before, you’ll have no problem installing the server edition. Basically, you’ll have to choose your native language, partition the disk, as well as to enter a password for the root (system administrator account).

Bottom line

In conclusion, the Server edition of Fedora is a really great server-oriented operating system that uses the latest upstream Linux kernel technologies and it include a wide variety of server-related packages.

Source

An Immodest Proposal for the Music Industry

How music listeners can fill the industry’s “value gap”.

From the 1940s to the 1960s, countless millions of people would put a dime
in a jukebox to have a single piece of music played for them, one time. If
they wanted to hear it again, or to play another song, they’d put in
another dime.

In today’s music business, companies such as Spotify, Apple and Pandora pay
fractions of a penny to stream songs to listeners. While this is a big
business that continues to become bigger, it fails to cover what the music
industry calls a “value gap”.

They have an idea for filling that gap. So do I. The difference is that
mine can make them more money, with a strong hint from the old jukebox
business.

For background, let’s start with this graph from the IFPI’s Global Music
Report 2018
:

""

Figure 1. Global Music Report 2018

You can see why IFPI no longer gives its full name:
International Federation of the Phonographic Industry. That phonographic
stuff is what they now call “physical”. And you see where that’s going (or
mostly gone). You also can see that what once threatened the
industry—”digital”—now accounts for most of its rebound (Figure
2).

""

Figure 2. Global Recorded Music Revenues by Segment (2016)

The graphic shown in Figure 2 is also a call-out from the first. Beside it is this
text: “Before seeing a return to growth in 2015, the global recording
industry lost nearly 40% in revenues from 1999 to 2014.”

Later, the report says:

However, significant challenges need to be
overcome if the industry is going to move to sustainable growth. The whole
music sector has united in its effort to fix the fundamental flaw in
today’s music market, known as the “value gap”, where fair
revenues are not being returned to those who are creating and investing in
music.

They want to solve this by lobbying: “The value gap is now the
industry’s single highest legislative priority as it seeks to create a
level playing field for the digital market and secure the future of the
industry.” This has worked before. Revenues from streaming and performance
rights owe a lot to royalty and copyright rates and regulations guided by
the industry. (In the early 2000s, I covered this like a rug in Linux
Journal
. See here.)

But, there’s another way to fill that gap: on the listening side. You can
see a hint in that direction from growth in live performance revenues.
According to Statista,
live music industry revenue:

…will grow from 9.28
billion U.S. dollars in 2015 to 11.99 billion in 2021. Of the revenue
generated in 2016, over two billion U.S. dollars was generated in
sponsorship, and a further 7.4 billion U.S. dollars came in ticket sales.
The industry is expected to grow further in the coming years as the
compound annual growth rate for live music ticket sales is estimated at
5.23 percent between 2015 and 2020.

According
to a July 16, 2018, post in Pollstar
:

There is perhaps no better
indicator of a robust 2018 live market than Pollstar‘s Mid-Year Top 50
Worldwide Tours chart. This year’s survey saw a 12% jump in total gross
from last year’s $1.97 billion to a record-setting $2.21 billion—a
$240 million increase. It’s the chart’s biggest rise since
2015–16…

Concert promoters also are raising prices. Says a July 9, 2018,
report
by ABC
News:

The average price of a concert ticket during the first six months of
the year was $46.69—4.2 percent higher than the average cost of a
ticket for the same period last year, according to the latest figures from
music industry magazine Pollstar. That price is almost 7 percent higher
than the average for all of 2000, and an even more startling 43 percent
increase over what concert tickets cost just three years ago, according to
Pollstar.

That same report says sales are going down: a market signal that
the prices are too high. But hey, people are clearly willing to pay a lot
for live music and a participatory experience. This is an important clue.

Participation requires good signaling from both sides of the marketplace.
So let’s look at the demand side, shown in Figure 3, starting with what the streaming services
pay to play us a tune.

""

Figure 3. What the Streaming Services Pay to Play a Tune (from Trichordist

To make that clearer, the top three streamers pay between 13.4% (Pandora)
and 78.3% of a penny ($.01) to play you a song.

SiriusXM pays (it says here) “19.1% of the price of all audio packages
which include music channels”. That means the $209.76 I paid last August
for my SiriusXM subscription sent $40.01 to the rights-holders of all the
music played on all the SiriusXM channels for my account over the following
year, whether I listened to any music or not. (And mostly I listen to
non-music channels.)

YouTube is another special case. The 2018 IFPI report says, “From publicly
available data, IFPI estimates that Spotify paid record companies US$20 per
user in 2015, the last year of available data. By contrast, it is estimated
that YouTube returned less than US$1 for each music user.” That’s a big part
of the “value gap”.

Some of those rates are negotiated, others are set by regulation, and most
are informed—one way or another—by both.

In no case, however, does the music listener pay for digital music on the
jukebox model: with cash on a per-listen, per-song basis. (Note that a dime
in 1960 was more than 100x what a streamer pays for the right to play a
song for somebody.)

So that’s my proposal: create an easy way for any of us to pay what we want
for the music we hear
. This will give music lovers their own way to close
the value gap—and then some.

As it happens, an easy way to do this was proposed
by ProjectVRM (which I
run at Harvard’s Berkman Klein
Center
) way back in 2009. It’s called
EmanciPay, and here is how it is described on the project wiki:

Simply put, EmanciPay makes it easy for anybody to pay (or offer to
pay) —

    1. as much as they like
    2. however they like

for whatever they like

  1. on their own terms

— or at least to start with that full set of options, and to work
out differences with sellers easily and with minimal friction.

EmanciPay turns consumers (aka users) into customers by giving them a
pricing gun (something which in the past only sellers used) and their own
means to make offers, to pay outright, and to escrow the intention to pay
when price and other requirements are met. Payments themselves can also be
escrowed.

In slightly more technical terms, EmanciPay is a payment framework for
customers operating with full agency in the open marketplace. It operates
on open protocols and standards, so it can be used by any buyer, seller or
intermediary…

So, as currently planned, EmanciPay would —

  1. Provide a single and easy way that consumers of “content” can
    become customers of it. In the current system—which isn’t one—every artist, every musical group, every public radio and TV station, has
    his, her or its own way of taking in contributions from those who
    appreciate the work. This can be arduous and time-consuming for everybody
    involved. (Imagine trying to pay separately every musical artist you like,
    for all your enjoyment of each artist’s work.) What EmanciPay proposes,
    however, is not a replacement for existing systems, but a new system that
    can supplement existing fund-raising systems—one that can soak up
    much of today’s MLOTT: Money Left On The Table.
  2. Provide ways for individuals to look back through their media usage
    histories, inform themselves about what they have been enjoying, and to
    determine how much it is worth to them. The Copyright Arbitration Royalty
    Panel (CARP), and later the Copyright Royalty Board (CRB), both came up
    with “rates and terms that would have been negotiated in the marketplace
    between a willing buyer and a willing seller”—language that first
    appeared in the 1995 Digital Performance Royalty Act (DPRA), and was
    tweaked in 1998 by the Digital Millennium Copyright Act (DMCA), under which
    both the CARP and the CRB operated. The rates they came up with peaked at
    $.0001 per “performance” (a song or recording), per listener. EmanciPay
    creates the “willing buyer” that the DPRA thought wouldn’t exist.
  3. Stigmatize non-payment for worthwhile media goods. This is where
    “social” will finally come to be something more than yet another tech
    buzzmodifier.

All these require micro-accounting, not micro-payments. In fact
micro-accounting can inform ordinary payments that can be made in clever
new ways that should satisfy everybody with an interest in seeing artists
compensated fairly for their work. An individual listener, for example, can
say “I want to pay one cent for every song I hear on the radio”, and “I’ll send
SoundExchange a lump sum of all the pennies I wish to pay for songs I hear
over the course of a year, along with an accounting of what artists and
songs I’ve listened to”—and leave dispersal of those totaled pennies
up to the kind of agency that likes, and can be trusted, to do that kind of
thing.

Similar systems can also be put in place for readers of newspapers,
blogs and other journals. What’s important is that the control is in the
hands of the individual, and that the accounting and dispersal systems work
the same way for everybody.

I also proposed this earlier in “EmanciPay: A Content Monetization Plan for
Newspapers”
, and later in “An Easy Way to Pay for Journalism, Music and
Everything Else We Like”
. In the first of those, I wrote:

Think of EmanciPay
as a way to unburden sellers of the need to keep trying to control markets
that are beyond their control anyway. Think of it as a way that “free
market” can mean more than “your choice of captor”. Think of it as a way
that “customer relationships” can be worthy of the label because both sides
are carrying their ends of the relationship burden—rather than the
sellers’ side carrying the whole thing.

It’ll be fun to start doing that in the music industry.

A number of developments make the opportunity ripe now:

  1. The music industry is far less scattered and conflicted about its
    nature (digital now) and future (gotta make up that value gap) than it ever
    was in the past.
  2. Former enemies can be friends. For example, open source and the music
    industry have both won, and many aligned incentives can be found between
    them.
  3. Music listeners are clearly willing to pay value for value. We just
    need to create the ways. And it shouldn’t be hard. (Especially for Linux
    Journal
    readers.)
  4. The jukebox and live performance examples both suggest that people
    shouldn’t have a problem saying “I’ll be glad to set up a way to pay one
    cent every time I hear music I like.”
  5. Apple just bought Shazam, which is a way to identify music people hear.
    That kind of functionality can be brought into standard ways people can pay
    for music they passively hear (for example, in a restaurant or at parties) and
    like.
  6. We’ve long needed a standards-based approach to tipping artists—or
    anybody—with maximal ease and minimal friction. One can be crafted out
    of work on EmanciPay.

While most of my usual appeals in Linux Journal are to the hackers among
us, this appeal is mostly to my friends (old and new) in the music
industry. They have the connections, the talent, the legal smarts, the
money and the motivation required to make this thing work.

So let’s bring the people who love music into the marketplace as
willing buyers. And let’s do it by standardizing simple ways people can, by
routine or impulse, be real customers of music and not just passive
consumers (or worse, what the industry used to call pirates). Let’s also
create new ways, beyond payments alone, that artists and music lovers can
signal each other, and have all kinds of creative fun.

The time is right. Let’s not let the opportunity pass.

Source

Slurm Job Scheduling System – Linux.com

In previous articles, I examined some fundamental tools for HPC systems, including pdsh (parallel shells), Lmod environment modules, and shared storage with NFS and SSHFS. One remaining, virtually indispensable tool is a job scheduler.

One of the most critical pieces of software on a shared cluster is the resource manager, commonly called a job scheduler, which allows users to share the system in a very efficient and cost-effective way. The idea is fairly simple: Users write small scripts, commonly called “jobs,” that define what they want to run and the required resources, which they then submit to the resource manager. When the resources are available, the resource manager executes the job script on behalf of the user. Typically this approach is for batch jobs (i.e., jobs that are not interactive), but it can also be used for interactive jobs, for which the resource manager gives you a shell prompt to the node that is running your job.

Some resource managers are commercially supported and some are open source, either with or without a support option. The list of candidates is fairly long, but the one I talk about in this article is Slurm. …The SLUM architecture is very similar to other job schedulers. Each node in the cluster has a daemon running, which in this case is named slurmd. The resources are referred to as nodes. The daemons can communicate in a hierarchical fashion that accommodates fault tolerance. On the Slurm master node, the daemon is slurmctld, which also has failover capability.

Read more at ADMIN magazine

Source

How To Install and Configure Nextcloud with Apache on CentOS 7

Nextcloud is an open source, self-hosted file share and collaboration platform, similar to Dropbox. It comes bundled with media player, calendar and contact management.

Nextcloud is extensible via apps and has desktop and mobile clients for all major platforms.

This tutorial will walk you through the process of installing and configuring Nextcloud with Apache on a CentOS 7 system.

Prerequisites

Before starting with the tutorial, make sure you are logged in as a user with sudo privileges.

Step 1: Creating MySQL Database

NextCloud can use SQLite, PostgreSQL or MySQL database to store all its data.

In this tutorial we will use MySQL as the database of choice.

If you already don’t have MySQL or MariaDB installed on your CentOS server you can install by following one of the instructions below:

Start by logging to to the MySQL shell by typing the following command:

Run the following SQL statements to create a database named nextcloud, user named nextclouduser and to grant the necessary privileges to the user:

CREATE DATABASE nextcloud CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
GRANT ALL ON nextcloud.* TO ‘nextclouduser’@’localhost’ IDENTIFIED BY ‘change-with-strong-password’;
FLUSH PRIVILEGES;
EXIT;

Step 2: Installing PHP and Apache

Nextcloud is a PHP application. CentOS 7 ships with PHP 5.4 which is not supported by Nextcloud.

We will install PHP 7.1 from the Remi repository. The commands below will enable EPEL and Remi repositories:

sudo yum install epel-release yum-utils
sudo yum install http://rpms.remirepo.net/enterprise/remi-release-7.rpm
sudo yum-config-manager –enable remi-php71

Once the repositories are enabled install Apache PHP 7.1 and all required PHP extensions with the following command:

sudo yum install httpd php php-gd php-json php-mysql php-curl php-mbstring php-intl php-mcrypt php-imagick php-xml php-zip

Step 3: Configuring firewall

If you are running Firewall on your CentOS server, you’ll need to open HTTP (80) and HTTPS (443) ports.

You can do that by running the following commands:

sudo firewall-cmd –permanent –zone=public –add-service=http
sudo firewall-cmd –permanent –zone=public –add-service=https
sudo firewall-cmd –reload

Step 4: Downloading Nextcloud

Download the latest version of Nextcloud from the Nextcloud download page with wget:

wget -P /tmp https://download.nextcloud.com/server/releases/nextcloud-14.0.3.zip

At the time of writing this article, the latest version of Nextcloud is version 14.0.3.

Once the download is complete, extract the archive and move the Nextcloud extracted files to the /var/www directory:

unzip /tmp/nextcloud-14.0.3.zip
sudo mv /tmp/nextcloud /var/www/

Set the correct permissions so that the Apache web server can have full access to the Nextcloud’s files and directories.

sudo chown -R apache: /var/www/nextcloud

Step 5: Configure Apache

Open your text editor and create the following Apache configuration file.

sudo nano /etc/httpd/conf.d/nextcloud.conf

/etc/httpd/conf.d/nextcloud.conf

Alias /nextcloud “/var/www/nextcloud/”

<Directory /var/www/nextcloud/>
Options +FollowSymlinks
AllowOverride All

<IfModule mod_dav.c>
Dav off
</IfModule>

SetEnv HOME /var/www/nextcloud
SetEnv HTTP_HOME /var/www/nextcloud

</Directory>

Activate the changes by restarting Apache service:

sudo systemctl restart httpd

Step 6: Installing Nextcloud

Now that Nextcloud is downloaded and all necessary services are configured open you browser and start the Nextcloud installation by visiting your server’s domain name or IP address followed by /nextcloud :

http://domain_name_or_ip_address/nextcloud

You will be presented with the Nextcloud setup page.

Enter your desired admin username and password and the MySQL user and database details you previously created.

Click on the Finish setup button and once the installation process is completed you will be redirected to the Nextcloud dashboard logged in as admin user.

Conclusion

You have learned how to install and configure Nextcloud on your CentOS 7 machine. If you have a domain name associated with your Nextcloud server, you can follow this guide and secure your Apache with Let’s Encrypt.

To find more information about how to manage your Nextcloud instance visit the Nextcloud documentation page.

If you have any question, please leave a comment below.

Source

Raptor Talos II POWER9 Benchmarks Against AMD Threadripper & Intel Core i9

For those curious about the performance of IBM’s POWER9 processors against the likes of today’s AMD Threadripper and Intel Core i9 HEDT processors, here are some interesting benchmarks as we begin looking closer at the POWER9 performance on the fully open-source Raptor Talos II Secure Workstation. This open-source, secure system arrived for Linux testing with dual 22-core POWER9 CPUs to yield 176 total threads of power.

 

 

As mentioned a few days ago in the aforelinked article, Raptor Computing Systems recent sent over a Talos II system for benchmarking to deliver more frequent benchmarks from this high-end workstation/server that’s fully open-source down to the motherboard firmware and BMC stack. We previously have carried out some remote benchmarks of the Talos II, but now having it in our labs allows us to more frequently conduct tests as well as swapping out the hardware, matching other test systems, and also other tests like performance-per-Watt comparisons that were not possible with the remote testing.

 

 

Besides being fully open-source, the Talos II is also manufactured in the US with the IBM POWER9 processors being fabbed in New York while the Raptor motherboard is manufactured in Texas along with where their systems are assembled. The Talos II motherboard features five PCI Express 4.0 slots for next-gen connectivity, dual Gigabit Ethernet, and can accommodate two POWER9 “Sforza” CPUs that support four memory channels per socket.

 

 

The POWER9 Sforza-based Talos II was being compared to AMD Threadripper and Intel Core i9 for this initial article given these CPUs all supporting four DDR4 memory channels. Some Talos II comparisons to AMD EPYC and Intel Xeon hardware will be coming up soon on Phoronix for reference. It’s the larger LaGrange/Monza POWER9 modules that support eight memory channels that are more akin to the Xeon/EPYC competition.

 

 

As for the attention to detail with Talos II being an open-source product, included with the system is a DVD containing the system schematics as well as the firmware source code. That DVD copy is the exact source used to build the pre-loaded firmware though also available via git.raptorcs.com is all of the platform firmware code, CPU firmware, BMC firmware, host firmware, OpenBMC code, and OpenPOWER bits.

 

 

Pricing on POWER hardware remains a bit high depending upon your budget: pricing on the motherboard itself is $2,499.00 or $1,129.99 for the Lite version that is single-socket only. Pricing on the IBM POWER9 CPUs starts at $375 USD for the quad-core or $2625 USD for the 22-core processor. Pricing is certainly higher than Threadripper / Core i9 but the system is fully open-source and audit-able for security and in the case of this dual 22-core setup offers 176 threads thanks to 4-way SMT.

 

 

For those looking to find a high-performance POWER9 libre system on a budget, Raptor Computing Systems has been working on Blackbird with more information on that lower-cost board due out soon.
Source

WP2Social Auto Publish Powered By : XYZScripts.com