01 Mar 2021

feedFedora People


Vamos subir rapidamente um ambiente LAMP em nossa máquina de maneira simples e fácil, tudo rodando em contêineres.

Vamos criar criar 2 diretórios em nosso /home/ , onde um deles será o diretório da aplicação e o outro para o banco de dados MySQL:

mkdir app
mkdir mysql

Agora, vamos subir o servidor LAMP:

$ sudo podman run --privileged -dit
--name lamp
-p 8080:80
-p 3306:3306
-v ${PWD}/app:/app
-v ${PWD}/mysql:/var/lib/mysql

Verificar se está rodando:

sudo podman ps

Vamos setar um usuário e senha no MySQL:

$ sudo podman exec lamp mysql -u root -e "GRANT ALL PRIVILEGES ON *.* TO 'danniel'@'%' IDENTIFIED BY 'fedora';"
$ sudo podman exec lamp mysql -u root -e "FLUSH PRIVILEGES;"

Podemos verificar se está tudo ok, acesse via browser: http://localhost:8080

PhpMyAdmin: http://localhost:8080/phpmyadmin

Guia de Referencia :
Fedora Silverblue Ambiente LAMP

01 Mar 2021 10:37am GMT

The NeuroFedora Blog: Next Open NeuroFedora meeting: 1 March 1300 UTC

Photo by William White on Unsplash

Photo by William White on Unsplash.

Please join us at the next regular Open NeuroFedora team meeting on Monday 1 March at 1300UTC in #fedora-neuro on IRC (Freenode). The meeting is a public meeting, and open for everyone to attend. You can join us over:

You can use this link to convert the meeting time to your local time. Or, you can also use this command in the terminal:

$ date --date='TZ="UTC" 1300 today'

The meeting will be chaired by @major. The agenda for the meeting is:

We hope to see you there!

01 Mar 2021 9:48am GMT

Josh Bressers: Episode 260 – Dave Jevans tells us what CipherTrace is up to

Josh and Kurt talk with Dave Jevans CEO of CipherTrace and chairman of the anti-phishing working group about the challenges of keeping track of cryptocurrency in the modern age.

<audio class="wp-audio-shortcode" controls="controls" id="audio-2317-1" preload="none" style="width: 100%;"><source src="https://traffic.libsyn.com/secure/opensourcesecuritypodcast/Episode_260_Dave_Jevans_tells_us_what_CipherTrace_is_up_to.mp3?_=1" type="audio/mpeg">https://traffic.libsyn.com/secure/opensourcesecuritypodcast/Episode_260_Dave_Jevans_tells_us_what_CipherTrace_is_up_to.mp3</audio>

Show Notes

01 Mar 2021 12:01am GMT

28 Feb 2021

feedFedora People

Jonathan Dieter: WANPIPE and DAHDI COPR for EL8

At Spearline, we have a number of servers around the world with Sangoma telephony cards, which use the out-of-tree wanpipe and dahdi kernel modules. As we've been migrating our servers from CentOS 6 to SpearlineOS, one of the problems we've hit has been the out-of-tree modules don't compile against the EL8 kernels that we use as the base for SpearlineOS.

I've written some patches to fix the compilation bugs and have packaged them up in a COPR. wanpipe requires the dahdi sources to build, so I've put both sources into one telephony-kmods RPM, and then build the separate kmod RPMs from the single SRPM. We've been using the packages for the last few months without any problems, but, as always, use at your own risk.

Note that the COPR does have our build of Asterisk, with only the modules we require enabled, so if you're using Asterisk, you may want to exclude it from being installed from the COPR. If there's any interest in using the kmod RPMs without the other packages in the COPR, I could look at splitting them into a separate COPR. Please email me if you would like me to do this.

Old Germany telephone by Antonis glykas used under the CC BY-SA 4.0 license

28 Feb 2021 10:14pm GMT

Daniel Pocock: Gangstalking and victim-blaming

I will destroy you, threat, Washington

It is ironic that the first person to depart the Biden administration was sanctioned for threatening somebody else's career.

This week Marko Rodriguez went public with news that rogue members of the Apache Software Foundation had decided to persecute him for his commentary on social issues. The board had voted to reclassify satire as a form of prose that "borders" on hate speech. Either it is hate speech or it isn't. To suggest it "borders" on hate speech is a fudge. The sly comparison of these very different types of writing is simply a smear to hurt his career.

To put this in perspective, board members who disagreed with this defamation did not only vote against it but also choose to resign.

Around Valentine's Day, Brittany Higgins, a former employee of Australia's Minister for Defence went public with news about being raped on the ministerial sofa. The questions this woman raises are extraordinary, for example, if the Minister for Defence, Linda Reynolds, can not defend the new girl in the office, how can we rely on her to defend our country?

Brittany Higgins, Australia

Higgins chose not to name the accused publicly. It appears she wishes to focus attention on the culture and the cover-up. Two independent news organizations, True Crimes News Weekly and independent journalist Shane Olsen have identified a suspect. There is now a twitter hashtag too. A Youtube video shows the former Attorney General, George Brandis, praising Bruce Lehrmann and other former staff in the presence of high court justices.

George Brandis (former Attorney General): All of us know how important staff are to us. We spend so much time together, mostly away from home. We share so many experiences that they become like a second family.

As the man departed days after the incident in 2019, it appears that the Government have had plenty of time to remove his name from virtually all official web sites although there is no super-injunction (yet) to prevent discussion of his identity.

Against this backdrop, Google admitted two female researchers subject to high-profile sackings may have been doing legitimate research. Like Rodriguez and Higgins, both of Google's female victims had been threatened to self-censor, they refused, they were shamed, they bravely chose to put their persecution in the public domain.

All these cases inevitably remind me of other cases, the growing body count in the free and open source software world.

Higgins' decision to go public helps us all see how a cover-up was built from day one. Her boss, Linda Reynolds, had suggested that pursuing a criminal justice complaint would destroy Miss Higgins' career. In effect, the victim was blackmailed to stay silent. This is the thread that draws all these cases of oppression together. In December 2018, two long standing volunteers in the free, open source software world, Dr Norbert Preining and I, revealed how we were subject to blackmail and coercion in our respective roles. In our cases, we both received the veiled threats in writing:

Knife at throat, Debian Account Managers, DAM, blackmail

We are sending this email privately, leaving its disclosure as your decision (although traces in public databases are unavoidable)

In other words, they are saying that if we call out the coercive nature of their communications, they will seek to destroy us.

When you receive a threat like this from somebody with a history of publicly shaming people on a hideous scale, it really feels like they are holding a knife to your throat.


In my case, the community of volunteers and donors had clearly elected me as the fellowship representative so this blackmail was an attack on all those who voted. It was my duty to inform people and call it out.

The crimes were very different but the message seems to be the same: the organization must be protected at any cost. When those in authority do something wrong, the victims have to stay silent, grin and bear it or some gang will impose a bigger pain on the victim.

More on the former Debian Project Leader (DPL), Chris Lamb, giving negative references for volunteers

One volunteer sent me the following comments about Chris Lamb. Many people receiving copies of defamation have showed it to the survivors:

Volunteer: But I am scared that Lamb actually also hosed an application for a company in NY, a job related to Debian. If that has happened, and I can reasonably document it, I would consider a defamation law suit

When the leader of any organization, whether it is Apache, Debian or Google, uses the authority of their position to push defamation, it is like using the height of a bridge to stand above a freeway and drop bricks onto the cars underneath. Lamb may not fear consequences for his actions, his father is a barrister, Robert Lamb, who appears well qualified to stifle any volunteers seeking redress.

28 Feb 2021 7:00pm GMT

Fedora Cloud Working Group: The many faces of Laney McScratcherson

The post The many faces of Laney McScratcherson appeared first on Dissociated Press.

28 Feb 2021 3:33pm GMT

27 Feb 2021

feedFedora People

Fedora Cloud Working Group: James Jamerson: The unsung Motown bassist that influenced Paul McCartney

James Jamerson is just one of many session players in the 50s and 60s who went virtually unknown during his lifetime. Even now, after being...

The post James Jamerson: The unsung Motown bassist that influenced Paul McCartney appeared first on Dissociated Press.

27 Feb 2021 10:29pm GMT

Fedora Magazine: Getting started with COBOL development on Fedora Linux 33

Though its popularity has waned, COBOL is still powering business critical operations within many major organizations. As the need to update, upgrade and troubleshoot these applications grows, so may the demand for anyone with COBOL development knowledge.

Fedora 33 represents an excellent platform for COBOL development.
This article will detail how to install and configure tools, as well as compile and run a COBOL program.

Installing and configuring tools

GnuCOBOL is a free and open modern compiler maintained by volunteer developers. To install, open a terminal and execute the following command:

# sudo dnf -y install gnucobol 

Once completed, execute this command to verify that GnuCOBOL is ready for work:

# cobc -v

You should see version information and build dates. Don't worry if you see the error "no input files". We will create a COBOL program file with the Vim text editor in the following steps.

Fedora ships with a minimal version of Vim, but it would be nice to have some of the extra features that the full version can offer (such as COBOL syntax highlighting). Run the command below to install Vim-enhanced, which will overwrite Vim-minimal:

# sudo dnf -y install vim-enhanced

Writing, Compiling, and Executing COBOL programs

At this point, you are ready to write a COBOL program. For this example, I am set up with username fedorauser and I will create a folder under my home directory to store my COBOL programs. I called mine cobolcode.

# mkdir /home/fedorauser/cobolcode
# cd /home/fedorauser/cobolcode

Now we can create and open a new file to enter our COBOL source program. I'll call it helloworld.cbl.

# vim helloworld.cbl

You should now have the blank file open in Vim, ready to edit. This will be a simple program that does nothing except print out a message to our terminal.

Enable "insert" mode in vim by pressing the "i" key, and key in the text below. Vim will assist with placement of your code sections. This can be very helpful since every character space in a COBOL file has a purpose (it's a digital representation of the physical cards that developers would complete and feed into the computer).

      *simple helloworld program.
           DISPLAY '##################################'.
           DISPLAY '#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!#'.
           DISPLAY '#!!!!!!!!!!FEDORA RULES!!!!!!!!!!#'.
           DISPLAY '#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!#'.
           DISPLAY '##################################'.
           STOP RUN.

You can now press the "ESC" key to exit insert mode, and key in ":x" to save and close the file.

Compile the program by keying in the following:

# cobc -x helloworld.cbl

It should complete quickly with return status: 0. Key in "ls" to view the contents of your current directory. You should see your original helloworld.cbl file, as well as a new file simply named helloworld.

Execute the COBOL program.

# ./helloworld

If you see your text output without errors, then you have sucessfully compiled and executed the program!

<figure class="wp-block-image size-large"></figure>

Now that we have the basics of writing, compiling, and running a COBOL program, lets try one that does something a little more interesting.

The following program will generate the Fibonacci sequence given your input. Use Vim to create a file called fib.cbl and input the text below:

      * Author: Bryan Flood
      * Date: 25/10/2018
      * Purpose: Compute Fibonacci Numbers
      * Tectonics: cobc
       01  N0             BINARY-C-LONG VALUE 0.
       01  N1             BINARY-C-LONG VALUE 1.
       01  SWAP           BINARY-C-LONG VALUE 1.
       01  RESULT         PIC Z(20)9.
       01  I              BINARY-C-LONG VALUE 0.
       01  I-MAX          BINARY-C-LONG VALUE 0.
       01  LARGEST-N      BINARY-C-LONG VALUE 92.
           PERFORM MAIN
            ACCEPT I-MAX.
            EVALUATE TRUE
              WHEN I-MAX > LARGEST-N
                 PERFORM INVALIDN
              WHEN I-MAX > 2
              WHEN I-MAX = 2
                 PERFORM CASE2
              WHEN I-MAX = 1
                 PERFORM CASE1
              WHEN I-MAX = 0
                 PERFORM CASE0
              WHEN OTHER
                 PERFORM INVALIDN
            STOP RUN.
       *>  THE CASE FOR WHEN N = 0
           MOVE N0 TO RESULT.
           DISPLAY RESULT.
      *>  THE CASE FOR WHEN N = 1
           PERFORM CASE0
           MOVE N1 TO RESULT.
           DISPLAY RESULT.
      *>  THE CASE FOR WHEN N = 2
           PERFORM CASE1
           MOVE N1 TO RESULT.
           DISPLAY RESULT.
      *>  THE CASE FOR WHEN N > 2
           PERFORM CASE1
                   ADD N0 TO N1 GIVING SWAP
                   MOVE N1 TO N0
                   MOVE SWAP TO N1
                   MOVE SWAP TO RESULT
                   DISPLAY RESULT

As before, hit the "ESC" key to exit insert mode, and key in ":x" to save and close the file.

Compile the program:

# cobc -x fib.cbl

Now execute the program:

# ./fib

The program will ask for you to input a number, and will then generate Fibonocci output based upon that number.

<figure class="wp-block-image size-large"></figure>

Further Study

There are numerous resources available on the internet to consult, however vast amounts of knowledge reside only in legacy print. Keep an eye out for vintage COBOL guides when visiting used book stores and public libraries; you may find copies of endangered manuals at a rock-bottom prices!

It is also worth noting that helpful documentation was installed on your system when you installed GnuCOBOL. You can access them with these terminal commands:

# info gnucobol
# man cobc
# cobc -h

<figure class="wp-block-image size-large"></figure>

27 Feb 2021 8:00am GMT

Lukas "lzap" Zapletal: Thunderbolt bridge connection in Fedora 33

Thunderbolt bridge connection in Fedora 33

My home network is extremely slow, because I have CAT5e cables everywhere. I was wondering if I can use Thunderbolt ports which I have both on the new Mac M1 and Intel NUC with Fedora. So without my breath, since some Thunderbolt docks are known to brick the new Macs, I connected the two guys. And it worked automatically!

Fedora's (33) kernel automatically recognized thunderbolt0 device and NetworkManager created a new connection named "Wired connection 1". There must be some autonegotiation in the spec, because the two devices created 169.254/16 network and picked some IP addresses. I was not expecting that, I mean maybe if this was Linux to Linux but with MacOS involved I thought this is not gonna work. Let's see how fast is my 100Mbps connection:

mac$ nc -v -l 2222 > /dev/null

linux$ dd if=/dev/zero bs=1024K count=512 | nc -v 2222
Ncat: Version 7.80 ( https://nmap.org/ncat )
Ncat: Connected to
512+0 záznamů přečteno
512+0 záznamů zapsáno
536870912 bajtů (537 MB, 512 MiB) zkopírováno, 45,8012 s, 11,7 MB/s
Ncat: 536870912 bytes sent, 0 bytes received in 45.86 seconds.

That's expected on a 100Mbps ethernet. On a gigabit network, which I considered to upgrade to, we should see something like 117 MB/s for my ideal case (just a switch). But let's see how Thunderbolt works for me:

linux$ dd if=/dev/zero bs=1024K count=512 | nc -v 2222
Ncat: Version 7.80 ( https://nmap.org/ncat )
Ncat: Connected to
512+0 záznamů přečteno
512+0 záznamů zapsáno
536870912 bajtů (537 MB, 512 MiB) zkopírováno, 0,788541 s, 681 MB/s
Ncat: 536870912 bytes sent, 0 bytes received in 0.79 seconds.

Holy Moly! It's not 1.1 Gbps but almost 900 MB/s that's insane. This is a USB-C cable which is the best thing I currently have (this came with my LG screen). I am dropping a proper Thunderbolt3 into a basket to see how faster this can be. I mean in theory, I don't have that fast SSD in my Intel NUC server.

Allright, so that's looks like should be my preferred connection between my desktop and Linux. Let's rename the connection first:

nmcli con modify "Drátové připojení 1" connection.id thunderbolt0

Oh gosh, I need to switch back to English from Czech language. Next up, set static IP address.

nmcli con modify thunderbolt0 ipv4.method static ipv4.address
nmcli con down thunderbolt0
nmcli con up thunderbolt0

And after quick update in a MacOS network dialog and /etc/hosts change, the connection between my new desktop and my working Linux machine is 10Gbps.

27 Feb 2021 12:00am GMT

26 Feb 2021

feedFedora People

Fedora Cloud Working Group: Using the Display Posts plugin with WordPress and custom CSS

In case this helps anybody else, wanted to share how I created the Top 100 Albums page here on Dissociated Press. I wanted to be...

The post Using the Display Posts plugin with WordPress and custom CSS appeared first on Dissociated Press.

26 Feb 2021 4:30pm GMT

Fedora Community Blog: Friday’s Fedora Facts: 2021-08

Here's your weekly Fedora report. Read what happened this week and what's coming up. Your contributions are welcome (see the end of the post)! The Beta freeze is underway.

I have weekly office hours on Wednesdays in the morning and afternoon (US/Eastern time) in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.



<figure class="wp-block-table">

Conference Location Date CfP
DevConf.US virtual 2-3 Sep closes 31 May


Help wanted

Upcoming test days

Prioritized Bugs

<figure class="wp-block-table">

Bug ID Component Status
1883609 shim ASSIGNED


Upcoming meetings


Fedora 34


Upcoming key schedule milestones:


Change tracker bug status. See the ChangeSet page for details of approved changes.

<figure class="wp-block-table">

Status Count
ON_QA 49



<figure class="wp-block-table">

Bug ID Component Bug Status Blocker Status
1929940 dogtag-pki NEW Accepted(Beta)
1930977 mesa NEW Accepted(Beta)
1931070 mesa ON_QA Proposed(Beta)
1930978 xorg-x11-server NEW Proposed(Beta)


Fedora 35


<figure class="wp-block-table">

Proposal Type Status
Autoconf-2.71 System-Wide FESCo #2579
POWER 4k page size System-Wide FESCo #2581
rpmautospec - removing release and changelog fields from spec files System-Wide FESCo #2582


Changes approved, rejected, or withdrawn will be removed from this table the next week. See the ChangeSet page for a full list of approved changes.


Have something you want included? You can file an issue or submit a pull request in the fedora-pgm/pgm_communication repo.

The post Friday's Fedora Facts: 2021-08 appeared first on Fedora Community Blog.

26 Feb 2021 3:00pm GMT


Uma dica rápida para subir o NextCloud via podman rapidamente.

Bom vamos criar 01 diretório e 03 subdiretórios:

$ mkdir -p nextcloud/app
$ mkdir nextcloud/data
$ mkdir nextcloud/db

Agora vamos criar o nosso Pod:

$ podman pod create --name ncloud -p8080:80

E agora vamos subir o contêiner do MariaDB:

$ podman run -d --pod=ncloud \
--env MYSQL_DATABASE=nextcloud \
--env MYSQL_USER=nextcloud \
--env MYSQL_PASSWORD=nextcloud \
--env MYSQL_ROOT_PASSWORD=nextcloud \
-v ~/nexcloud/db:/var/lib/mysql:Z \
--restart always \
--name nextcloud-db \

Agora vamos subir o contêiner do NextCloud:

$ podman run -d --pod=ncloud \
--env MYSQL_HOST= \
--env MYSQL_DATABASE=nextcloud \
--env MYSQL_USER=nextcloud \
--env MYSQL_PASSWORD=nextcloud \
--env NEXTCLOUD_ADMIN_USER=nextcloud \
-v ~/nextcloud/app:/var/www/html \
-v ~/nextcloud/data:/var/www/html/data \
--restart always \
--name nextcloud \

Verifique se ficou ok:

$ podman ps

Pronto, só acessar pelo seu browser: http://localhost:8080

Caso tenha o cockpit, pode visualizar por lá também:

Guia de referência:
Nextcloud With Podman

26 Feb 2021 10:34am GMT

Josef Strzibny: Tailwind does not support pseudo-elements

This week I came across another tricky part of Tailwind, pseudo-elements. But what if you want to use them?

What are pseudo-elements anyway? Pseudo-elements are HTML elements that do not exist in the HTML markup at all. Such elements won't be visible to the browser assistive technology, they can only be styled visually with CSS.

It's quite common to define the :before and :after pseudo-elements that style a non-existing element in position relative to the element at hand. People use it for typography or drawing to keep markup clean and tidy. A lot of times, they are used in code pens to showcase some advanced CSS.

I wanted to use these pseudo-elements to create a 3D book for a new version of the landing page of my book. It's a project where I am trying out Tailwind for the first time.

Tailwind uses pre-defined classes and even though it could support these pseudo-elements in theory, it doesn't. So the only option is to use actual elements with aria-hidden="true" attribute to hide them from the browser assistive capabilities:

<div class="tailwind classes as usual" aria-hidden="true">
  <!-- :before -->

<div class="tailwind classes as usual">
  <!-- main element -->

<div class="tailwind classes as usual" aria-hidden="true">
  <!-- :after -->

The author of Tailwind already expressed that pseudo-elements are not necessary, so I don't think we get them in a future Tailwind release. There is an unofficial tailwind-pseudo plugin, though, which you can try.

26 Feb 2021 12:00am GMT

25 Feb 2021

feedFedora People

Fedora Magazine: Contribute at the Fedora Audio, Kernel 5.11 and i18n test days

Fedora test days are events where anyone can help make sure changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you've never contributed to Fedora before, this is a perfect way to get started.

There are three upcoming test events in the next week.

Come and test with us to make the upcoming Fedora 34 even better. Read more below on how to do it.

Audio test day

There is a recent proposal to replace the PulseAudio daemon with a functionally compatible implementation based on PipeWire. This means that all existing clients using the PulseAudio client library will continue to work as before, as well as applications shipped as Flatpak. The test day is to test everything works as expected. This will occur on Wednesday, March 03

Kernel test week

The kernel team is working on the final integration for kernel 5.11. This version was just recently released and will arrive soon in Fedora. As a result, the Fedora kernel and QA teams have organized a test week for Monday, March 08 through Monday, March 15. Refer to the wiki page for links to the test images you'll need to participate. This document clearly outlines the steps.

i18n test week

GNOME is the default desktop environment for Fedora Workstation and thus for many Fedora users. A lot of our users use Fedora in their preferred languages and it's important that we test the changes. The wiki contains more details about how to participate. The test week is March 09 through March 15.

How do test days work?

A test day is an event where anyone can help make sure changes in Fedora work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you've never contributed before, this is a perfect way to get started.

To contribute, you only need to be able to download test materials (which include some large files) and then read and follow directions step by step.

Detailed information about all the test days are on the wiki pages above. If you're available on or around the days of the events, please do some testing and report your results.

25 Feb 2021 8:00pm GMT

Luis Bazan: ZimbraLogHostname is not configured - error

[root@mail ~]# cat /etc/centos-release

CentOS Stream release 8

[zimbra@mail ~]$ zmcontrol -v

Release 8.8.15_GA_3953.RHEL8_64_20200629025823 UNKNOWN_64 FOSS edition, Patch 8.8.15_P19.

Log in as the zimbra user

[root@mail ~]# su - zimbra

[zimbra@mail ~]$

Now run this command to set the hostname in the Logs configuration.

Remember to change the domain name to yours.

[zimbra@mail ~]$ zmprov mcf zimbraLogHostname mail.ibtechpa.com

[zimbra@mail ~]$ exit


Switch to root user.

[root@mail ~]#

Update the log configuration with this command.

[root@mail ~]# /opt/zimbra/libexec/zmsyslogsetup

updateSyslogNG: Updating /etc/syslog-ng/syslog-ng.conf...done.

Last step restart zimbra services

With this you can see all your statistics and logs from the administrator gui.

25 Feb 2021 6:50pm GMT

Fedora Cloud Working Group: Tortie Thursday with Willow

The post Tortie Thursday with Willow appeared first on Dissociated Press.

25 Feb 2021 1:48pm GMT