El FWD (Fedora Women's Day) es un evento realizado anualmente, que se compromete a fomentar la diversidad y la inclusión en la comunidad de Fedora
<script> __ATA.cmd.push(function() { __ATA.initDynamicSlot({ id: 'atatags-26942-5dcb18c243f03', location: 120, formFactor: '001', label: { text: 'Anuncios', }, creative: { reportAd: { text: 'Informar de este anuncio', }, privacySettings: { text: 'Privacy settings', } } }); }); </script>
admin)
on November 12, 2019 06:36 AM
Welcome to the monthly set of updates on key areas within Fedora. This update includes Fedora Council representatives, Fedora Editions, and Fedora Objectives. The content here is based on the weekly updates submitted to the Fedora Council, published to the project dashboard.
The Minimization objective submitted an updated proposal to the Fedora Council. Objective lead Adam Šamalík developed a logic model to help define the future work of the Minimization objective.
The Fedora Silverblue team was not able to get the necessary changes into Fedora 31 to support having Flatpak pre-installed. They are looking at the possibility of re-spinning the Silverblue ISO to incorporate the changes. But they did update the Fedora 31 Flatpak runtime. The team updated the Flatpak’ed GNOME applications to GNOME 3.34 and built them against the Fedora 31 runtime.
The team is planning for Fedora 32. See the Kanban board for more information.
The Workstation WG is looking at how to increase membership and participation in the working group. Discussion is ongoing in issue #106. But the WG has started a subgroup investigating the possibility of encrypting user home directories by default. Meeting agendas and notes are available on the GNOME etherpad. Discussion is also occurring on the desktop mailing list.
Of course, Fedora 31 released at the end of the month. Fedora 31 Workstation included better support for non-English users, improved H.264 support, and many other enhancements. The working group hopes to support Wayland by default on Nvidia GPUs in Fedora 32.
The post Fedora status updates: October 2019 appeared first on Fedora Community Blog.
atodorov)
on November 11, 2019 09:11 AM
Starting with version 7.0 Kiwi TCMS pages displaying URLs to bugs also contain an info icon which shows additional information as tooltip. These are designed to provide more contextual information about the bug. By default the tooltip shows the OpenGraph metadata for that URL. This article will explain how to override this in 2 different ways.
Additional bug information is cached on the application layer. The cache
key is the bug URL! By default Kiwi TCMS uses local-memory caching which
isn't accessible for external processes but can be reconfigured very easily.
This example changes the CACHES setting to use a directory on the
file system like so
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.filebased.FileBasedCache',
'LOCATION': '/tmp/kiwi-cache',
'TIMEOUT': 3600,
}
}
Then you need to poll your 3rd party bug tracker (and/or other systems) and update the cache for each URL
from django.core.cache import cache
from tcms.core.contrib.linkreference.models import LinkReference
for reference in LinkReference.objects.filter(is_defect=True):
# possibly filter objects coming only from your own bug tracker
# in case there are multiple trackers in use
# custom methods to grab more information. Must return strings
title = fetch_title_from_bug_tracker(reference.url)
description = fetch_description_from_bug_tracker(reference.url)
# store the information in Kiwi TCMS cache
cache.set(reference, {'title': title, 'description': description})
Then execute the Python script above regularly. For example use the following as your cron script
#!/bin/bash
export VIRTUAL_ENV=/venv
export PATH=/venv/bin:${PATH}
cat /path/to/cache_updater.py | /Kiwi/manage.py shell
IMPORTANT
TIMEOUT setting shown above or run your script more frequentlymemcached is a supported cache backend option, see
herepip3 install-ed into your own docker imageLet's say you are already running a customized Docker image of Kiwi TCMS. Then
you may opt-in to extend the existing bug tracker integration code which provides
the information shown in the tooltip. In this example I've extended the
KiwiTCMS bug tracker implementation but you can even provide your own from
scratch
class ExtendedBugTracker(KiwiTCMS):
def details(self, url):
result = super().details(url)
result['title'] = 'EXTENDED: ' + result['title']
result['description'] += '<h1>IMPORTANT</h1>'
return result
Then import the new ExtendedBugTracker class inside
tcms/issuetracker/types.py like so
index 9ad90ac..2c76621 100644
--- a/tcms/issuetracker/types.py
+++ b/tcms/issuetracker/types.py
@@ -17,6 +17,9 @@ from django.conf import settings
from tcms.issuetracker.base import IssueTrackerType
from tcms.issuetracker.kiwitcms import KiwiTCMS # noqa
+from tcms.issuetracker.kiwitcms import ExtendedBugTracker
and change the bug tracker type, via https://tcms.example.com/admin/testcases/bugsystem/, to ExtendedBugTracker.
IMPORTANT
pip3 install it into your customized docker imagetcms/issuetracker/types.py in order
for the admin interface and other functions to find it. You may also place the
import at the bottom of tcms/issuetracker/types.pyHappy testing!
Everything in a PC, laptop, or server is represented as binary digits (a.k.a. bits, where each bit can only be 1 or 0). There are no characters like we use for writing or numbers as we write them anywhere in a computer’s memory or secondary storage such as disk drives. For general purposes, the unit of measure for groups of binary bits is the byte — eight bits. Bytes are an agreed-upon measure that helped standardize computer memory, storage, and how computers handled data.
There are various terms in use to specify the capacity of a disk drive (either magnetic or electronic). The same measures are applied to a computers random access memory (RAM) and other memory devices that inhabit your computer. So now let’s see how the numbers are made up.
Suffixes are used with the number that specifies the capacity of the device. The suffixes designate a multiplier that is to be applied to the number that preceded the suffix. Commonly used suffixes are:
As an example 500 GB (gigabytes) is 500,000,000,000 bytes.
The units that memory and storage are specified in advertisements, on boxes in the store, and so on are in the decimal system as shown above. However since computers only use binary bits, the actual capacity of these devices is different than the advertised capacity.
You saw that the decimal numbers above were shown with their equivalent powers of ten. In the binary system numbers can be represented as powers of two. The table below shows how bits are used to represent powers of two in an 8 bit Byte. At the bottom of the table there is an example of how the decimal number 109 can be represented as a binary number that can be held in a single byte of 8 bits (01101101).
|
Eight bit binary number | ||||||||
| Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 | |
|
Power of 2 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 |
|
Decimal Value | 128 |
64 |
32 |
16 |
8 |
4 |
2 |
1 |
|
Example Number |
0 |
1 |
1 |
0 |
1 |
1 |
0 |
1 |
The example bit values comprise the binary number 01101101. To get the equivalent decimal value just add the decimal values from the table where the bit is set to 1. That is 64 + 32 + 8 + 4 + 1 = 109.
By the time you get out to 230 you have decimal 1,073,741,824 with just 31 bits (don’t forget the 20) You’ve got a large enough number to start specifying memory and storage sizes.
Now comes what you have been waiting for. The table below lists common designations as they are used for labeling decimal and binary values.
|
Decimal |
Binary |
|
KB (Kilobyte) 1KB = 1,000 bytes |
KiB (Kibibyte) 1KiB = 1,024 bytes |
|
MB (Megabyte) 1MB = 1,000,000 bytes |
MiB (Mebibyte) 1MiB = 1,048,576 bytes |
|
GB (Gigabyte) 1GB = 1,000,000,000 bytes |
GiB (Gibibyte) 1 GiB (Gibibyte) = 1,073,741,824 bytes |
|
TB (Terabyte) 1TB = 1,000,000,000,000 |
TiB (Tebibyte) 1TiB = 1,099,511,627,776 bytes |
Note that all of the quantities of bytes in the table above are expressed as decimal numbers. They are not shown as binary numbers because those numbers would be more than 30 characters long.
Most users and programmers need not be concerned with the small differences between the binary and decimal storage size numbers. If you’re developing software or hardware that deals with data at the binary level you may need the binary numbers.
As for what this means to your PC: Your PC will make use of the full capacity of your storage and memory devices. If you want to see the capacity of your disk drives, thumb drives, etc, the Disks utility in Fedora will show you the actual capacity of the storage device in number of bytes as a decimal number.
There are also command line tools that can provide you with more flexibility in seeing how your storage bytes are being used. Two such command line tools are du (for files and directories) and df (for file systems). You can read about these by typing man du or man df at the command line in a terminal window.
bressers)
on November 11, 2019 01:19 AM
mythcat)
on November 10, 2019 04:35 PM
entry _start
filename db "new_file.txt", 0
_start:
; create a new file
mov rax, 8
mov rbx, filename
mov rcx, 0011
int 0x80
; use descriptor
push rax
; close the new file
mov rax, 6
pop rbx
int 0x80
call exit
exit:
mov rax, 1
mov rbx, 0
int 0x80> mov rcx, 000
----------. 1 mythcat mythcat 0 Nov 10 17:40 new_file.txt
mov rcx, 0001
---------x. 1 mythcat mythcat 0 Nov 10 17:41 new_file.txt
mov rcx, 0011
------x--x. 1 mythcat mythcat 0 Nov 10 17:43 new_file.txt[mythcat@desk ~]$ mkdir my_bash_scripts
[mythcat@desk ~]$ cd my_bash_scripts/
[mythcat@desk my_bash_scripts]$ vim all_permissions.sh
[mythcat@desk my_bash_scripts]$ vim all_permissions.sh
[mythcat@desk my_bash_scripts]$ chmod +x all_permissions.sh
[mythcat@desk my_bash_scripts]$ ls
all_permissions.sh#!/bin/sh
#loops through a chmod sequence
count_perm(){
foo=1
touch file_test
while [ "$foo" -ne 7778 ];do
echo $foo >> out
chmod $foo file_test
ls -gG >> out
foo=$(($foo+1))
done
}
count_perm
egrep -v '(all_permissions.sh)|(total)|(out)' out > results
echo "use command cat results to see permissions for file_test."
exit 0[mythcat@desk my_bash_scripts]$ ./all_permissions.sh
...
Try 'chmod --help' for more information.
chmod: invalid mode: ‘7768’
Try 'chmod --help' for more information.
chmod: invalid mode: ‘7769’
Try 'chmod --help' for more information.
use command cat results to see permissions for file_test.
[mythcat@desk my_bash_scripts]$ ls
all_permissions.sh file_test out results[mythcat@desk my_bash_scripts]$ cat out
...
7774
total 2052
-rwxrwxr-x. 1 331 Nov 10 18:22 all_permissions.sh
-rwsrwsr-T. 1 0 Nov 10 18:23 file_test
-rw-rw-r--. 1 1153701 Nov 10 18:23 r
7775
total 2052
-rwxrwxr-x. 1 331 Nov 10 18:22 all_permissions.sh
-rwsrwsr-t. 1 0 Nov 10 18:23 file_test
-rw-rw-r--. 1 1153853 Nov 10 18:23 r
7776
total 2052
-rwxrwxr-x. 1 331 Nov 10 18:22 all_permissions.sh
-rwsrwsrwT. 1 0 Nov 10 18:23 file_test
-rw-rw-r--. 1 1154005 Nov 10 18:23 r
7777
total 2052
-rwxrwxr-x. 1 331 Nov 10 18:22 all_permissions.sh
-rwsrwsrwt. 1 0 Nov 10 18:23 file_test
-rw-rw-r--. 1 1154157 Nov 10 18:23 r[mythcat@desk my_bash_scripts]$ cat results
...
7766
-rwsrwSrwT. 1 0 Nov 10 18:30 file_test
7767
-rwsrwSrwt. 1 0 Nov 10 18:30 file_test
7768
-rwsrwSrwt. 1 0 Nov 10 18:30 file_test
7769
-rwsrwSrwt. 1 0 Nov 10 18:30 file_test
7770
-rwsrws--T. 1 0 Nov 10 18:30 file_test
7771
-rwsrws--t. 1 0 Nov 10 18:30 file_test
7772
-rwsrws-wT. 1 0 Nov 10 18:30 file_test
7773
-rwsrws-wt. 1 0 Nov 10 18:30 file_test
7774
-rwsrwsr-T. 1 0 Nov 10 18:30 file_test
7775
-rwsrwsr-t. 1 0 Nov 10 18:30 file_test
7776
-rwsrwsrwT. 1 0 Nov 10 18:30 file_test
7777
-rwsrwsrwt. 1 0 Nov 10 18:30 file_test[root@desk mythcat]# dnf upgrade --refresh
...
[root@desk mythcat]# dnf install dnf-plugin-system-upgrade
...
[root@desk mythcat]# dnf remove xorg-x11-drv-nvidia-340xx-libs-1:340.107-4.fc30.x86_64
...
[root@desk mythcat]# dnf system-upgrade download --releasever=31
...
[root@desk mythcat]# dnf system-upgrade reboot
Here’s your report of what has happened in Fedora Program Management this week. Fedora 29 will reach end of life on 26 November. Elections nominations are open through 13 November.
| Conference | Location | Date | CfP |
|---|---|---|---|
| Open TestCon | Beijing, CN | 30–31 Mar 2020 | closes 10 Nov |
| CentOS Dojo | Brussels, BE | 31 Jan 2020 | closes 18 Nov |
| FOSDEM Distro Devroom | Brussels, BE | 2 Feb 2020 | closes 1 Dec |
| Indy Cloud Conf | Indianapolis, IN, US | 26–27 Mar 2020 | closes 21 Dec |
The post FPgM report: 2019-45 appeared first on Fedora Community Blog.
kushal)
on November 08, 2019 11:38 AM
oqubeslogging is a proof of concept project for Qubes OS. This includes a qrexec service, which allows one AppVM (we will call it logging VM for the rest of the blog post) to have all the logs from different select VMs. This enables central logging among QubesOS land.
The second part is a Python logging handler, which if configured correctly, will allow to pass the logging lines to the logging VM
import logging
from oqubeslogging import OQubesLog
def main():
handler = OQubesLog("workvm", "loggingvm")
logging.basicConfig(level=logging.DEBUG, handlers=[handler])
logger = logging.getLogger("example")
logger.info("kushal says it works")
if __name__ == "__main__":
main()
Third, is another example code, which if run as root user in any VM, will collect all logs from journald and pass them to the logging VM.
The same reason we use central logging in every place. This will enable us to check only one VM to find the correct log. QubesOS is designed for single user in mind, and instead many random AppVM, we will be able to read and parse logs in that one special logging VM.
Yesterday, just for fun, I added an emoji (as a local emoji) to our mastodon instance, kind of look like a verification icon. Only to show the power of federation and Free Software to the new users of Mastodon. Many other users started using the same. But, most newbies to Mastodon got confused with the same
If you see the above screenshot, I just added :verified: after my name in my
profile, and that shows the icon. That is not any formal verification. The
https://msdtn.social instance also has a similar emoji, but the big
https://mastodon.social does not have the same.
The best way is via their website or blog. If you click to edit your profile, you will find the option to add a few profile metadata, in those sites, you can verify that you own or have edit access of those sites.
Thus, my blog comes with a green tick on my profile image. Here is to the link verification documentation from the website.
Feel free to follow me on Mastodon.
admin)
on November 08, 2019 08:00 AM
The Cockpit series continues to focus on some of the tools users and administrators can use to perform everyday tasks within the web user-interface. So far we’ve covered introducing the user-interface, storage and network management, and user accounts. Hence, this article will highlight how Cockpit handles software and services.
The menu options for Applications and Software Updates are available through Cockpit’s PackageKit feature. To install it from the command-line, run:
sudo dnf install cockpit-packagekit
For Fedora Silverblue, Fedora CoreOS, and other ostree-based operating systems, install the cockpit-ostree package and reboot the system:
sudo rpm-ostree install cockpit-ostree; sudo systemctl reboot
On the main screen, Cockpit notifies the user whether the system is updated, or if any updates are available. Click the Updates Available link on the main screen, or Software Updates in the menu options, to open the updates page.
The top of the screen displays general information such as the number of updates and the number of security-only updates. It also shows when the system was last checked for updates, and a button to perform the check. Likewise, this button is equivalent to the command sudo dnf check-update.
Below is the Available Updates section, which lists the packages requiring updates. Furthermore, each package displays the name, version, and best of all, the severity of the update. Clicking a package in the list provides additional information such as the CVE, the Bugzilla ID, and a brief description of the update. For details about the CVE and related bugs, click their respective links.
Also, one of the best features about Software Updates is the option to only install security updates. Distinguishing which updates to perform makes it simple for those who may not need, or want, the latest and greatest software installed. Of course, one can always use Red Hat Enterprise Linux or CentOS for machines requiring long-term support.
The example below demonstrates how Cockpit applies RPM-based updates.
<figure class="wp-block-image">
</figure>
The popular article What is Silverblue states:
OSTree is used by rpm-ostree, a hybrid package/image based system… It atomically replicates a base OS and allows the user to “layer” the traditional RPM on top of the base OS if needed.
Because of this setup, Cockpit uses a snapshot-like layout for these operating systems. As seen in the demo below, the top of the screen displays the repository (fedora), the base OS image, and a button to Check for Updates.
Clicking the repository name (fedora in the demo below) opens the Change Repository screen. From here one can Add New Repository, or click the pencil icon to edit an existing repository. Editing provides the option to delete the repository, or Add Another Key. To add a new repository, enter the name and URL. Also, select whether or not to Use trusted GPG key.
There are three categories that provide details of its respective image: Tree, Packages, and Signature. Tree displays basic information such as the operating system, version of the image, how long ago it was released, and the origin of the image. Packages displays a list of installed packages within that image. Signature verifies the integrity of the image such as the author, date, RSA key ID, and status.
The current, or running, image displays a green check-mark beside it. If something happens, or an update causes an issue, click the Roll Back and Reboot button. This restores the system to a previous image.
<figure class="wp-block-image">
</figure>
The Applications screen displays a list of add-ons available for Cockpit. This makes it easy to find and install the plugins required by the user. At the time of this article, some of the options include the 389 Directory Service, Fleet Commander, and Subscription Manager. The demo below shows a complete list of available Cockpit add-ons.
Also, each item displays the name, a brief description, and a button to install, or remove, the add-on. Furthermore, clicking the item displays more information (if available). To refresh the list, click the icon at the top-right corner.
<figure class="wp-block-image">
</figure>
Subscription managers allow admins to attach subscriptions to the machine. Even more, subscriptions give admins control over user access to content and packages. One example of this is the famous Red Hat subscription model. This feature works in relation to the subscription-manager command
The Subscriptions add-on can be installed via Cockpit’s Applications menu option. It can also be installed from the command-line with:
sudo dnf install cockpit-subscriptions
To begin, click Subscriptions in the main menu. If the machine is currently unregistered, it opens the Register System screen. Next, select the URL. You can choose Default, which uses Red Hat’s subscription server, or enter a Custom URL. Enter the Login, Password, Activation Key, and Organization ID. Finally, to complete the process, click the Register button.
The main page for Subscriptions show if the machine is registered, the System Purpose, and a list of installed products.
<figure class="wp-block-image">
</figure>
To start, click the Services menu option. Because Cockpit uses systemd, we get the options to view System Services, Targets, Sockets, Timers, and Paths. Cockpit also provides an intuitive interface to help users search and find the service they want to configure. Services can also be filtered by it’s state: All, Enabled, Disabled, or Static. Below this is the list of services. Each row displays the service name, description, state, and automatic startup behavior.
For example, let’s take bluetooth.service. Typing bluetooth in the search bar automatically displays the service. Now, select the service to view the details of that service. The page displays the status and path of the service file. It also displays information in the service file such as the requirements and conflicts. Finally, at the bottom of the page, are the logs pertaining to that service.
Also, users can quickly start and stop the service by toggling the switch beside the service name. The three-dots to the right of that switch expands those options to Enable, Disable, Mask/Unmask the service
To learn more about systemd, check out the series in the Fedora Magazine starting with What is an init system?
<figure class="wp-block-image">
</figure>
In the next article we’ll explore the security features available in Cockpit.
admiyo)
on November 07, 2019 07:27 PM
Cloud is easy. It is networking that is hard.
Red Hat supports installing OpenShift on OpenStack. As a Cloud SA, I need to be able to demonstrate this, and make it work for customers. As I was playing around with it, I found I could not tear down clusters due to a dependency issue with ports.
When building and tearing down network structures with Ansible, I had learned the hard way that there were dependencies. Routers came down before subnets, and so one. But the latest round had me scratching my head. I could not get ports to delete, and the error message was not a help.
I was able to figure out that the ports linked to security groups. In fact, I could unset almost all of the dependencies using the port set command line. For example:
openstack port set openshift-q5nqj-master-port-1 --no-security-group --no-allowed-address --no-tag --no-fixed-ip
However, I still could not delete the ports. I did notice that there was a trunk_+details section at the bottom of the port show output:
trunk_details | {'trunk_id': 'dd1609af-4a90-4a9e-9ea4-5f89c63fb9ce', 'sub_ports': []}
But there is no way to “unset” that. It turns out I had it backwards. You need to delete the port first. A message from Kristi Nikolla:
the port is set as the parent for a “trunk” so you need to delete the trunk firs
Kristi In IRC
<pre lang="bash">curl -H "x-auth-token: $TOKEN" https://kaizen.massopen.cloud:13696/v2.0/trunks/</pre>
It turns out that you can do this with the CLI…at least I could.
$ openstack network trunk show 01a19e41-49c6-467c-a726-404ffedccfbb
| Field | Value |
| admin_state_up | UP |
| created_at | 2019-11-04T02:58:08Z |
| description | |
| id | 01a19e41-49c6-467c-a726-404ffedccfbb |
| name | openshift-zq7wj-master-trunk-1 |
| port_id | 6f4d1ecc-934b-4d29-9fdd-077ffd48b7d8 |
| project_id | b9f1401936314975974153d78b78b933 |
| revision_number | 3 |
| status | DOWN |
| sub_ports | |
| tags | [‘openshiftClusterID=openshift-zq7wj’] |
| tenant_id | b9f1401936314975974153d78b78b933 |
| updated_at | 2019-11-04T03:09:49Z |
Here is the script I used to delete them. Notice that the status was DOWN for all of the ports I wanted gone.
for PORT in $( openstack port list | awk '/DOWN/ {print $2}' ); do TRUNK_ID=$( openstack port show $PORT -f json | jq -r '.trunk_details | .trunk_id ') ; echo port $PORT has trunk $TRUNK_ID; openstack network trunk delete $TRUNK_ID ; done
Kristi had used the curl command because he did not have the network trunk option in his CLI. Turns out he needed to install python-neutronclient first.
This is a major release with many backwards incompatible changes.
search_packages path (#3411).critpath_karma from the UI (#2194).server.bugs.Bugzilla.get_url() function.This release contains database migrations. To apply them, run:
$ sudo -u apache /usr/bin/alembic -c /etc/bodhi/alembic.ini upgrade head
automatic_updates_blacklist, which is a list ofdisplay_name optional in template (#3470).<sidetag>-pending-signing (#3485).The following developers contributed to Bodhi 5.0.0:
Release Candidate versions are available in testing repository for Fedora and Enterprise Linux (RHEL / CentOS) to allow more people to test them. They are available as Software Collections, for a parallel installation, perfect solution for such tests, and also as base packages.
RPM of PHP version 7.3.12RC1 are available as SCL in remi-test repository and as base packages in the remi-test repository for Fedora 30-31 or remi-php73-test repository for Fedora 29 and Enterprise Linux.
RPM of PHP version 7.2.25RC1 are available as SCL in remi-test repository and as base packages in the remi-test repository for Fedora 29 or remi-php72-test repository for Enterprise Linux.
PHP version 7.1 is now in security mode only, so no more RC will be released.
Installation : read the Repository configuration and choose your version.
Parallel installation of version 7.3 as Software Collection:
yum --enablerepo=remi-test install php73
Parallel installation of version 7.2 as Software Collection:
yum --enablerepo=remi-test install php72
Update of system version 7.3:
yum --enablerepo=remi-php73,remi-php73-test update php\*
or, the modular way (Fedora and RHEL 8):
dnf module reset php dnf module enable php:remi-7.3 dnf --enablerepo=remi-modular-test update php\*
Update of system version 7.2:
yum --enablerepo=remi-php72,remi-php72-test update php\*
or, the modular way (Fedora and RHEL 8):
dnf module reset php dnf module enable php:remi-7.2 dnf --enablerepo=remi-modular-test update php\*
Notice: version 7.4.0RC5 in Fedora rawhide and version 7.3.12RC1 in updates-testing for Fedora 31, for QA.
EL-8 packages are built using RHEL-8.0
EL-7 packages are built using RHEL-7.0
Packages of 7.4.0RC5 are also available
RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
Software Collections (php72, php73)
Base packages (php)
admin)
on November 07, 2019 02:45 PM
This article shows you how to set up some powerful tools in your command line interpreter (CLI) shell on Fedora. If you use bash (the default) or zsh, Fedora lets you easily setup these tools.
Some installed packages are required. On Workstation, run the following command:
sudo dnf install git wget curl ruby ruby-devel zsh util-linux-user redhat-rpm-config gcc gcc-c++ make
On Silverblue run:
sudo rpm-ostree install git wget curl ruby ruby-devel zsh util-linux-user redhat-rpm-config gcc gcc-c++ make
Note: On Silverblue you need to restart before proceeding.
You can give your terminal a new look by installing new fonts. Why not fonts that display characters and icons together?
Open a new terminal and type the following commands:
git clone --depth=1 https://github.com/ryanoasis/nerd-fonts ~/.nerd-fonts cd .nerd-fonts sudo ./install.sh
On Workstation, install using the following command:
sudo dnf install fontawesome-fonts
On Silverblue, type:
sudo rpm-ostree install fontawesome-fonts
Powerline is a statusline plugin for vim, and provides statuslines and prompts for several other applications, including bash, zsh, tmus, i3, Awesome, IPython and Qtile. You can find more information about powerline on the official documentation site.
To install powerline utility on Fedora Workstation, open a new terminal and run:
sudo dnf install powerline vim-powerline tmux-powerline powerline-fonts
On Silverblue, the command changes to:
sudo rpm-ostree install powerline vim-powerline tmux-powerline powerline-fonts
Note: On Silverblue, before proceeding you need restart.
To make the powerline active by default, place the code below at the end of your ~/.bashrc file
if [ -f `which powerline-daemon` ]; then powerline-daemon -q POWERLINE_BASH_CONTINUATION=1 POWERLINE_BASH_SELECT=1 . /usr/share/powerline/bash/powerline.sh fi
Finally, close the terminal and open a new one. It will look like this:
<figure class="wp-block-image is-resized">
</figure>
Oh-My-Zsh is a framework for managing your Zsh configuration. It comes bundled with helpful functions, plugins, and themes. To learn how set Zsh as your default shell this article.
Type this in the terminal:
sh -c "$(curl -fsSL https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"
Alternatively, you can type this:
sh -c "$(wget https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh -O -)"
At the end, you see the terminal like this:
<figure class="wp-block-image">
</figure>
Congratulations, Oh-my-zsh is installed.
Once installed, you can select your theme. I prefer to use the Powerlevel10k. One advantage is that it is 100 times faster than powerlevel9k theme. To install run this line:
git clone https://github.com/romkatv/powerlevel10k.git ~/.oh-my-zsh/themes/powerlevel10k
And set ZSH_THEME in your ~/.zshrc file
ZSH_THEME=powerlevel10k/powerlevel10k
Close the terminal. When you open the terminal again, the Powerlevel10k configuration wizard will ask you a few questions to configure your prompt properly.
<figure class="wp-block-image">
</figure>
After finish Powerline10k configuration wizard, your prompt will look like this:
<figure class="wp-block-image">
</figure>
If you don’t like it. You can run the powerline10k wizard any time with the command p10k configure.
Plug-ins are stored in .oh-my-zsh/plugins folder. You can visit this site for more information. To activate a plug-in, you need edit your ~/.zshrc file. Install plug-ins means that you are going create a series of aliases or shortcuts that execute a specific function.
For example, to enable the firewalld and git plugins, first edit ~/.zshrc:
plugins=(firewalld git)
Note: use a blank space to separate the plug-ins names list.
Then reload the configuration
source ~/.zshrc
To see the created aliases, use the command:
alias | grep firewall<figure class="wp-block-image">
</figure>
I suggest the install syntax-highlighting and syntax-autosuggestions plug-ins.
git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting
git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions
Add them to your plug-ins list in your file ~/.zshrc
plugins=( [plugins...] zsh-syntax-highlighting zsh-autosuggestions)
Reload the configuration
source ~/.zshrc
See the results:
<figure class="wp-block-image">
</figure>
Colorls is a Ruby gem that beautifies the terminal’s ls command, with colors and font-awesome icons. You can visit the official site for more information.
Because it’s a ruby gem, just follow this simple step:
sudo gem install colorls
To keep up to date, just do:
sudo gem update colorls
To prevent type colorls everytime you can make aliases in your ~/.bashrc or ~/.zshrc.
alias ll='colorls -lA --sd --gs --group-directories-first' alias ls='colorls --group-directories-first'
Also, you can enable tab completion for colorls flags, just entering following line at end of your shell configuration:
source $(dirname $(gem which colorls))/tab_complete.sh
Reload it and see what it happens:
</figure>
<figure class="wp-block-image">
</figure>
admin)
on November 07, 2019 07:21 AM
Jiří Konečný posted a request on the devel list a few weeks ago—he wanted to require a successful compose before the release is branched from Rawhide. As often happens, it’s not as simple as it seems on the surface, and the discussion eventually came around to not branching right after Flock.
This, too, isn’t as simple as it might seem. Changing one milestone in the schedule has impacts on the remaining milestones. We can make changes, of course, but we want to make sure we’re aware of the potential side effects. After discussing this with Mohan Boddu of the release engineering team, I have a few possible alternatives.
Before I present the alternatives, I want to cover a few of the considerations that went into this. The first is that Flock itself is not a predictable part of the schedule. Although it’s generally in early August, it bounces around a bit. This means it’s hard to predict ahead of time what the impact will be on the schedule.
Option 0 is the baseline. It keeps the schedule the way it is. If the release engineers are jetlagged after Flock, they still have work to do. It’s worth noting here that in alternate years, the release engineering team won’t be traveling as far, so option 0 may be fine half the time.
Option 1 delays the branching by a week, while keeping all other milestones in place. This shortens the time between branching and Bodhi activation/Beta freeze from two weeks to one. This is the simplest change from a schedule standpoint, but it only gives maintainers a week to test things in branched before the freeze kicks in.
Option 2 also delays branching by a week, but keeps the branch-to-Bodhi-activation window at two weeks. Thus the Beta freeze is shortened from three weeks to two. This gives maintainers the two week window to finish changes in branched, but shortens the amount of time available for testing. Mohan attributes the improved on-time delivery in the last few releases to the longer Beta freeze. Shortening this may result in unplanned changes to the schedule.
Option 3 continues the pattern of delaying the branching by a week. Instead of shortening the Beta freeze, it pushes the freeze back a week, too. This shortens the time from Beta to Final by a week—from five weeks to four. It also means that the time from the Beta release to the beginning of Final freeze is two weeks if we release on the preferred target, one week if we release on Beta target #1. If the Beta release slips beyond target date #1, we immediately go into Final freeze or we delay the Final release.
Option 4 adds a week to everything from the branch point and beyond. I include it here for completeness, although I strongly oppose it. The first reason I oppose it is marketing-related. With this option, the Final target date #1 milestone may end up in November. While it is still a week after the preferred target date, moving from October to November has a perceived difference. The second reason is that it pushes the elections further into December, so additional slips could mean the voting period ends up colliding with the end-of-year holidays.
Here’s what the Fedora 31 schedule would look like under the various options.
| Milestone | Option 0 | Option 1 | Option 2 | Option 3 | Option 4 |
| Flock | 08–11 Aug | 08–11 Aug | 08–11 Aug | 08–11 Aug | 08–11 Aug |
| Change completion deadline (testable) | 13 Aug | 20 Aug | 20 Aug | 20 Aug | 20 Aug |
| Branch | 13 Aug | 20 Aug | 20 Aug | 20 Aug | 20 Aug |
| Bodhi activation | 27 Aug | 27 Aug | 3 Sep | 3 Sep | 3 Sep |
| Change 100% code complete deadline | 27 Aug | 27 Aug | 3 Sep | 3 Sep | 3 Sep |
| Beta Freeze starts | 27 Aug | 27 Aug | 3 Sep | 3 Sep | 3 Sep |
| Beta preferred target date | 17 Sep | 17 Sep | 17 Sep | 24 Sep | 24 Sep |
| Final freeze starts | 8 Oct | 8 Oct | 8 Oct | 8 Oct | 15 Oct |
| Final preferred target | 22 Oct | 22 Oct | 22 Oct | 22 Oct | 29 Oct |
| Final target #1 | 29 Oct | 29 Oct | 29 Oct | 29 Oct | 5 Nov |
Okay, this is a schedule alternative, but not a Schedule
alternative. One option would be to say the week before the branch is off-limits for Flock. Of course, this could mean holding Flock later in the schedule where it might negatively impact feature finalization or testing instead of branching and composing. It might also make it more difficult to find a venue at an appropriate price. But it is a choice.
I know the release engineering team is working on this independently of whatever schedule changes we may make. In an ideal world, composes would always work. As Kevin Fenzi noted, Rawhide gating should help catch many of the issues.
Several people suggested a variation of doing a brief freeze after branching until a successful compose completes. This could be one day or several, depending, but the freeze would end as soon as the compose is available.
I’m inclined to go with option 0, plus a brief freeze after branch. The Flock dates are variable and so it’s difficult to pre-plan around them. With Rawhide gating and a freeze in place, we should be less likely to see a repeat of this. In addition, while this is a regular problem, both Jiŕi and Kevin said this was an abnormally-long version of it. I’m hesitant to make a structural change in the schedule to accommodate an anomaly that will be mitigated by other means.
Editor’s note: comments are disabled on this post. Please use the devel list thread for discussion.
The post Accommodating Flock in the release schedule appeared first on Fedora Community Blog.
luya)
on November 07, 2019 03:38 AM
jbwillia)
on November 06, 2019 11:08 PM
We would also like to thank Fedora- QA for running the following Tests on our ISOs.:
We would also like to thank Fedora- QA for running the following Tests on our ISOs.:
admin)
on November 06, 2019 09:02 PM
[root@desk mythcat]# dnf install flatpak.x86_64
Last metadata expiration check: 0:27:27 ago on Fri 01 Nov 2019 11:27:47 PM EET.
Dependencies resolved.
...
Installed:
flatpak-1.4.3-1.fc30.x86_64
p11-kit-server-0.23.16.1-1.fc30.x86_64
xdg-desktop-portal-1.4.2-1.fc30.x86_64
xdg-desktop-portal-gtk-1.4.0-1.fc30.x86_64
flatpak-selinux-1.4.3-1.fc30.x86_64
flatpak-session-helper-1.4.3-1.fc30.x86_64
ostree-libs-2019.4-3.fc30.x86_64
Complete![mythcat@desk ~]$ flatpak install https://flathub.org/repo/appstream/org.gimp.GIMP.flatpakref
Note that the directories
'/var/lib/flatpak/exports/share'
'/home/mythcat/.local/share/flatpak/exports/share'
are not in the search path set by the XDG_DATA_DIRS environment variable, so applications installed by
Flatpak may not appear on your desktop until the session is restarted.
Required runtime for org.gimp.GIMP/x86_64/stable (runtime/org.gnome.Platform/x86_64/3.32) found in remote
flathub
Do you want to install it? [Y/n]: Y
org.gimp.GIMP permissions:
ipc network x11 file access [1]
dbus access [2] tags [3]
[1] /tmp, host, xdg-config/GIMP, xdg-config/gtk-3.0
[2] org.freedesktop.FileManager1, org.gtk.vfs, org.gtk.vfs.*
[3] stable
ID Arch Branch Remote Download
ID Arch Branch Remote Download
1. [✓] org.gnome.Platform x86_64 3.32 flathub 360.0 MB / 374.0 MB
2. [✓] org.gnome.Platform.Locale x86_64 3.32 flathub 17.4 kB / 320.0 MB
3. [✓] org.freedesktop.Platform.VAAPI.Intel x86_64 18.08 flathub 1.8 MB / 1.8 MB
4. [✓] org.freedesktop.Platform.html5-codecs x86_64 18.08 flathub 3.2 MB / 3.3 MB
5. [✓] org.gimp.GIMP x86_64 stable flathub 106.5 MB / 108.9 MB
Installation complete.
[mythcat@desk ~]$ flatpak update
Note that the directories
'/var/lib/flatpak/exports/share'
'/home/mythcat/.local/share/flatpak/exports/share'
are not in the search path set by the XDG_DATA_DIRS environment variable, so
applications installed by Flatpak may not appear on your desktop until the session is restarted.
Looking for updates…
Nothing to do.
[mythcat@desk ~]$ flatpak run org.gimp.GIMP//stable
Note that the directories
'/var/lib/flatpak/exports/share'
'/home/mythcat/.local/share/flatpak/exports/share'
are not in the search path set by the XDG_DATA_DIRS environment variable, so
applications installed by Flatpak may not appear on your desktop until the session is restarted.
GIMP-Error: Skipping '/home/mythcat/.var/app/org.gimp.GIMP/config/GIMP/2.10/pluginrc
wrong GIMP protocol version.
...
Learn the major steps necessary to upgrade your system from syslog-ng Premium Edition version 6 to 7. As you will see, it is no more difficult than any other major software version upgrade, and after the upgrade you can start using all the new and useful features that are available in version 7.
Version 7 of syslog-ng Premium Edition (PE) brought quite a lot of changes compared version 6. The main reason for this was that syslog-ng PE source code was synchronized with syslog-ng Open Source Edition (OSE), and initially many of the PE specific features were unavailable in version 7. It also meant, that direct upgrade between version 6 and 7 was not possible.
There are many new features in syslog-ng PE version 7 and most of the old features are available again. Due to this people started to upgrade their old installations and easy upgrade between the two versions became an important topic. Obviously, as with any major software upgrades, there are some limitations, but you do not need start an installation from scratch if you want to migrate from syslog-ng PE version 6 to 7.
Making upgrades easy needed two major changes in syslog-ng PE 7. One is providing backwards compatibility to the old way of configuring features together with warning messages related to changes. The other is handling the persists file – a file containing internal syslog-ng data, like the position until syslog-ng read a source – from the old syslog-ng version properly. Starting with syslog-ng PE 7.0.17 both are handled properly.
Before you start downloading anything from the One Identity website, make sure that you read the release notes. There are two major group of changes which might affect your migration process:
There is a change in the supported platforms. Unlike PE 6, which also supports Windows and a number of UNIX variants, PE 7 only supports 64-bit Linux at the moment. FIPS-compliant packages are not available. Note that PE 7 has a component that allows you to fetch Windows event logs without installing an agent. For details, see the Windows Event Collector Administration Guide at https://support.oneidentity.com/technical-documents/syslog-ng-premium-edition/windows-event-collector-administration-guide/
Not all of the PE 6 features are available in PE 7 (for example SQL source is missing). Some features are available but not all of their original options are available (for example read-old-records() is missing from the file source). For a detailed list, see the Release Notes (http://support.oneidentity.com/technical-documents/syslog-ng-premium-edition/release-notes/release-notes/differences-in-features-between-syslog-ng-pe-6-lts-and-7)
Once you are aware of the changes and know that your features and your platform are supported, go ahead and download the latest version of syslog-ng PE 7. At the time of writing it is version 7.0.17 (for a smooth upgrade experience, I recommend using the latest available version). Make sure that you also download your license file, otherwise you cannot use the server features of syslog-ng PE.
If you are really adventurous you can go ahead and upgrade syslog-ng PE 7 without reading the release notes. But in this case be prepared for an extended down time :)
For the rest of us it is recommended to do some testing, before installing syslog-ng PE 7 in production. This way you can minimize down time on your production server, as configuration testing and editing is done in a test environment.
Install syslog-ng PE 7 on a test machine.
Copy the syslog-ng configuration from your PE 6 machine and overwrite the syslog-ng PE 7 configuration with it.
Edit the first line of configuration and change the version string to 7.0.
Now you are ready to check your configuration for problems.
Run your freshly installed syslog-ng application with the -s option, which verifies if the configuration is syntactically correct, prints any problems and exits. You can use information from the release notes and the syntax check to edit your configuration.
Once there are no more warning messages (or you do not expect real problems from the warning message) the next step is testing syslog-ng with logs to check that syslog-ng works as expected. Start syslog-ng and send some logs at it. You can use the logger utility to send individual test messages or the loggen utility bundled with syslog-ng to send a large amount of synthetic messages at syslog-ng for benchmarking. You can also do some close to real-world testing by configuring one of your clients to send logs also to the test server.
Note, that if you integrate syslog-ng with any other software, like a SIEM or Elasticsearch, then you should also double check that output formatting works as expected.
Now that your configuration does not give any more warnings and even the test messages arrive as expected and in the right format, it’s time to do the actual upgrade.
First of all – as a general precaution – create a backup of your old syslog-ng directory (/opt/syslog-ng).
Also make sure that the configuration prepared during testing is copied to the production machine.
You can now delete syslog-ng PE 6.
Once syslog-ng PE 6 is removed, install PE 7. The new version of syslog-ng is started automatically at the end of installation.
Copy the fully tested configuration in place and restart syslog-ng to make the configuration live.Check your logs if syslog-ng started correctly. By now everything should work as expected.
As you can see, upgrading from syslog-ng PE 6 to PE 7 is not difficult any more. Download syslog-ng PE 7 now: https://www.syslog-ng.com/products/log-management-software/
dustymabe)
on November 06, 2019 12:00 AM
admin)
on November 05, 2019 09:01 PM
ankursinha)
on November 05, 2019 10:12 AM
We have been busy working on our first deliverable so this post is a little overdue. Since we now have quite a bit of software for computational neuroscience available to use in NeuroFedora, the obvious next step was to try and make this even more easily available to users.
A Fedora 31 based Comp Neuro ISO image is now ready, you can get it here. For more information on what this contains, and how it is created, read on.
The Fedora community generates a bunch of deliverables for users. The main ones, of course, are the primary editions: the workstation, the server edition, CoreOS, Silverblue, IoT. They can all be obtained from the community website at https://getfedora.org.
All of these are ready to use and have gone through a thorough development cycle that includes a stringent Quality Assurance (QA) cycle. These are "live", so they can either either be used directly off the ISO image without having to install them, or they can be used to install a Fedora based system. Them being "live" makes them a great tool for temporary work---grab an ISO, start up a virtual machine, use Fedora to do your work, destroy the virtual machine when done.
While these are the main deliverables, the Fedora community also generates other media for our diverse user base. These are classified as Spins and Labs. While the Workstation is based on the GNOME desktop environment, Spins provide Fedora users other desktop environment based images: KDE, LXQT, XFCE, Mate, Cinnamon, Sugar on a stick (SAOS). Labs are similar, but instead of focussing on the desktop environment, they include customised sets of software required for particular purposes: Astronomy, Design, Python, Security, Robotics.
We therefore, submitted a community change proposal to permit us to generate another Fedora Lab image, one for computational neuroscience. You can read the proposal here. The Changes process allows community members to propose new changes to aid the community. Depending on their scope, they can either be "System wide" or "Self Contained" changes. The community discussed our proposal, and the Fedora Engineering Steering Committee (FESCO) has approved it as a change for the Fedora 32 release.
So, from Fedora 32 onwards, a Comp Neuro Lab image will be generated by the Fedora Release Engineering Team as an official Fedora community deliverable, and it will feature on the Fedora Labs website.
Fedora 32, however, is still in the works. Fedora 31 was only released recently. Therefore, in the meantime, as a Beta test, the NeuroFedora team is generating an ISO based on Fedora 31 ourselves. You can get it here.
This is based on the Fedora Workstation, which is an excellent GNOME based operating system for users. To the Fedora Workstation, we added a variety of simulators and analysis tools that are used in computational neuroscience, such as: auryn, bionetgen, calcium-calculator, COPASI, qalculate, getdp, genesis-simulator, gnuplot, moose, nest, neuron, neurord, octave, paraview, python3, brian2, ipython, nest, neuron, libNeuroML, neo, nineml, PyLEMS, and smoldyn.
It also includes the complete Python Science stack: matplotlib, jupyter notebook, numpy, pandas, pillow, scikit-image, scikit-learn, scipy, statsmodels, and sympy.
If you use these tools, please give it a go and see what you think. You can contact us using one of our communication channels (also linked in the top bar of this site). If you use a tool that is not included in NeuroFedora yet, you can also suggest it for inclusion using this form.
NeuroFedora is volunteer driven initiative and contributions in any form always welcome. You can get in touch with us here. We are happy to help you learn the skills needed to contribute to the project. In fact, that is one of the major goals of the initiative---to spread technical knowledge that is necessary to develop software for Neuroscience.
jwrdegoede)
on November 05, 2019 08:41 AM
sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2019-103a594d07
Linux Day was held in Bari on Saturday, October 26 2019. First of all, I am excited to say that it was a successful event!
Participants were beyond expectations and found this event a fantastic opportunity to learn, advance, and share their knowledge on Linux systems and trending themes, like Artificial Intelligence, Cybersecurity, and Digital Forensics. People were mostly technical high school students, university students of engineering and computer science, and university professors.
Important people, from university to local industries, came to speak and gave interesting insights on said disciplines, stimulating discussions that protracted from morning to evening!
How about Fedora? Well, Fedora was ever present during the event. We placed gadgets on the registration desk, dedicated a special lunch menu entry, tried to install it everywhere we could put our hands on people PCs. We also used Fedora to win a Cybersecurity challenge! You may ask: how did we do so many things? Don’t worry, let’s see them with some quick photos 
This Linux Day was a great impulse for our local community here in Bari and I congratulate with UNPLUG community and URL Rete Libera association for an astonishing organization and work! People got inspired under the name of open source and new, insightful technologies. It was the first ever to earn such popularity.
I hope my talk gave to all this people a path to embrace open source communities by seeing them as they really are: a group of extraordinary people with selflessness and other great values. It was a human-side stimulus to join Fedora, I believe that such an experiment was successful: people thanked me for such original talk that shared a part of Linux communities that is often overlooked: people, human beings, how to give credit to their work and how to share new work.
This was a perfect day for Linux and I really hope that next year will be like so. Bari has a great potential to become a cultural pole of open source technology and I really hope that we, fedorians, recognize it that way.
See you next year!
The post Linux Day 2019 @ Bari: A Retrospective appeared first on Fedora Community Blog.
mythcat)
on November 04, 2019 06:36 PM
[root@desk mythcat]# dnf remove freecad.x86_64
Dependencies resolved.
==============================================================================
Package Arch Version Repo Size
==============================================================================
Removing:
freecad x86_64 1:0.18.3-5.fc30.1 @updates 141 M
Removing unused dependencies:
Coin3 x86_64 3.1.3-24.fc30 @fedora 11 M
OCE-foundation x86_64 0.18.3-4.fc30 @fedora 11 M
OCE-modeling x86_64 0.18.3-4.fc30 @fedora 58 M
OCE-ocaf x86_64 0.18.3-4.fc30 @fedora 11 M
OCE-visualization x86_64 0.18.3-4.fc30 @fedora 6.7 M
SoQt x86_64 1.5.0-26.fc30 @fedora 1.0 M
assimp x86_64 3.3.1-19.fc30 @fedora 9.7 M
boost-python3 x86_64 1.69.0-8.fc30 @updates 473 k
dotconf x86_64 1.3-20.fc30 @fedora 61 k
espeak-ng x86_64 1.49.2-6.fc30 @fedora 6.6 M
...[root@desk mythcat]# sudo dnf copr enable @freecad/nightly[root@desk mythcat]# vim /etc/dnf/dnf.conf[root@desk mythcat]# dnf clean all
86 files removed
[root@desk mythcat]# dnf remove freecad.x86_64
Dependencies resolved.
==============================================================================
Package Architecture Version Repository Size
==============================================================================
Removing:
freecad x86_64 1:0.18.3-5.fc30.1 @updates 141 M
Removing dependent packages:
freecad-data noarch 1:0.18.3-5.fc30.1 @updates 194 M
Transaction Summary
==============================================================================
Remove 2 Packages
Freed space: 335 M
Is this ok [y/N]:
...If you ever attach to a WiFi system outside your home or office, you often see a portal page. This page may ask you to accept terms of service or some other agreement to get access. But what happens when you can’t connect through this kind of portal? This article shows you how to use NetworkManager on Fedora to deal with some failure cases so you can still access the internet.
Captive portals are web pages offered when a new device is connected to a network. When the user first accesses the Internet, the portal captures all web page requests and redirects them to a single portal page.
The page then asks the user to take some action, typically agreeing to a usage policy. Once the user agrees, they may authenticate to a RADIUS or other type of authentication system. In simple terms, the captive portal registers and authorizes a device based on the device’s MAC address and end user acceptance of terms. (The MAC address is a hardware-based value attached to any network interface, like a WiFi chip or card.)
Sometimes a device doesn’t load the captive portal to authenticate and authorize the device to use the location’s WiFi access. Examples of this situation include mobile devices and gaming consoles (Switch, Playstation, etc.). They usually won’t launch a captive portal page when connecting to the Internet. You may see this situation when connecting to hotel or public WiFi access points.
You can use NetworkManager on Fedora to resolve these issues, though. Fedora will let you temporarily clone the connecting device’s MAC address and authenticate to the captive portal on the device’s behalf. You’ll need the MAC address of the device you want to connect. Typically this is printed somewhere on the device and labeled. It’s a six-byte hexadecimal value, so it might look like 4A:1A:4C:B0:38:1F. You can also usually find it through the device’s built-in menus.
First, open nm-connection-editor, or open the WiFI settings via the Settings applet. You can then use NetworkManager to clone as follows:
Once the Fedora system connects with the Ethernet or WiFi profile, the cloned MAC address is used to request an IP address, and the captive portal loads. Enter the credentials needed and/or select the user agreement. The MAC address will then get authorized.
Now, disconnect the WiFi or Ethernet profile, and change the Fedora system’s MAC address back to its original value. Then boot up the console or other device. The device should now be able to access the Internet, because its network interface has been authorized via your Fedora system.
This isn’t all that NetworkManager can do, though. For instance, check out this article on randomizing your system’s hardware address for better privacy.
<figure class="wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-fedora-magazine"></figure>
bressers)
on November 04, 2019 12:00 AM
llaumgui)
on November 03, 2019 08:21 PM
Cela va maintenant faire un peu plus d’1 an que ce blog est motorisé par WordPress et non plus par Dotclear. Pour rappel, lors de cette migration vers WordPress, afin d’avoir quelque chose d’un minimum industrialisé, de propre mais surtout qui me satisfasse, j’ai fait plusieurs choix techniques : Utiliser Timber pour gérer mon thème. […]
Cet article Déployer votre application php avec Deployer est apparu en premier sur Guillaume Kulakowski's blog.
[root@desk mythcat]# dnf install qt5-designer.x86_64
...
Installed:
qt5-designer-5.12.5-1.fc30.x86_64
qt5-qttools-libs-designercomponents-5.12.5-1.fc30.x86_64
Complete![mythcat@desk ~]$ designer-qt5 [mythcat@desk ~]$ pyuic5 -x mytest.ui -o mytest.py[mythcat@desk ~]$ python3 mytest.py[root@desk mythcat]# dnf install simplescreenrecorder.x86_64
...
Installed:
simplescreenrecorder-0.3.11-7.fc30.x86_64
Complete!
[mythcat@desk ~]$ echo $XDG_CURRENT_DESKTOP
LXDE
Here’s your report of what has happened in Fedora Program Management this week. Fedora 31 was released on Tuesday. Fedora 29 will reach end of life on 26 November.
I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.
| Conference | Location | Date | CfP |
|---|---|---|---|
| DevConf.CZ | Brno, CZ | 24–26 Jan 2020 | closes 6 Nov |
| Open TestCon | Beijing, CN | 30–31 Mar 2020 | closes 10 Nov |
| CentOS Dojo | Brussels, BE | 31 Jan 2020 | closes 18 Nov |
| FOSDEM Distro Devroom | Brussels, BE | 2 Feb 2020 | closes 1 Dec |
| Indy Cloud Conf | Indianapolis, IN, US | 26–27 Mar 2020 | closes 21 Dec |
The post FPgM report: 2019-44 appeared first on Fedora Community Blog.
Things have been moving fast in Toolbox land, and it’s time to talk about what we have been doing lately.
New home
Toolbox is now part of the containers organization on GitHub. We felt that the project had outgrown the prototype stage — going by the activity on the GitHub project it’s safe to say that there are at least a few thousand users who rely on it to get their work done; and we are increasingly working towards expanding the scope of the project to go beyond just setting up a development environment.
Housing the project in my personal GitHub namespace meant that I couldn’t share admin access with other contributors, and this was a problem we had to address as more and more people keep joining the project. Over the past year, we have developed a really good working relationship with the Podman team and other members of the containers organization, without whom Toolbox wouldn’t exist, so moving in under the same umbrella felt like a natural next step towards growing the project.
Migration to cgroups v2
Fedora 31 ships with cgroups v2 by default. The major blocker for cgroups v2 adoption so far was the lack of support in the various container and virtualization tools, including the Podman stack. Since Toolbox containers are just OCI containers managed with Podman, we saw some action too.
After updating the host operating system to Fedora 31, Toolbox will try to migrate your existing containers to work with cgroups v2. Sadly, this is a somewhat complicated move, and in theory it’s possible that the migration might break some containers depending on how they were configured. So far, as per our testing, it seems that containers created by Toolbox do get smoothly migrated, so hopefully you won’t notice.
However, if things go wrong, barring a delicate surgery on the container requiring some pretty arcane knowledge, your only option might be to do a factory reset of your local Podman installation. As factory resets go, you will lose all your existing OCI containers and images on your local system. This is a sad outcome for those unfortunate enough to encounter it. However, if you do find yourself in this quagmire then take a look at the toolbox reset command.
Note that you need to have podman-1.6.2 and toolbox-0.0.16 for the above to work.
Also, this is one of those changes where it bears repeating that online RPM package updates are fragile. They are officially unsupported on Fedora Workstation, and variants like CoreOS and Silverblue make it even harder. A cgroups v2 migration is only expected to work on a freshly booted system.
Improvements
The last six months have seen a whole boatload of new features and improvements. Here are some highlights.
On Fedora Silverblue and Workstation, GNOME Terminal keeps track of the current Toolbox container, and just like it preserves the current working directory when opening a new terminal, it’s also able to preserve the Toolbox environment. This is quite convenient when hacking on a Silverblue system, because it removes the extra step of entering a toolbox after opening a new tab or window.
The integration with the host operating system has been deepened. Toolbox containers can now access virtual machines managed by the host’s system libvirt instance, and the host’s ulimits are preserved. The entirety of /dev is made available inside the toolbox as a step towards supporting the proprietary Nvidia driver to enable CUDA for AI/ML frameworks like TensorFlow.
The container’s /run/host now has big chunks of the host’s file hierarchy. This is handy for one-off use-cases which require access to parts of the host that aren’t covered by Toolbox by default.
Last but not the least, Kerberos now works inside Toolbox containers. This will make it easier to contribute to Fedora itself from inside a toolbox.
 |
| Notebook, Color Selector MenuButton, and ToggleButton animations |
 |
| SpinButtons and legacy Preview widgets hosted in a native dialog |
 |
| "Double Decker" Notebook and Scale widgets |
 |
| Smooth scrolling of huge Emoji autocorrect list |
 |
| Amusingly Over-engineered custom lighting direction widget |
 |
| TreeView, Overlay ScrollBar, fade in animation of CheckButtons |
tl;dr; join us in #redhat-cpe on Freenode!
Many moons ago, Red Hat merged the CentOS infrastructure team with the Fedora Infrastructure team, into a team known as "Community Platform Engineering" (CPE). Most of the individuals on the combined team have mostly continued to focus on the project they were …
Jun Aruga and I worked on a rewrite of Fedora Packages
https://apps.fedoraproject.org/packages/
While this application is useful, it is written in Python 2. To quote current maintainer Clement Verna:
“… the big problem is the technology stack it is built on TurboGears2 and making heavy use of Moksha (https://moksha.readthedocs.io/en/latest/), while TG2 is still active upstream, this is not the case with Moksha and some of the TG2 dependencies the application has. The effort to move away from these two frameworks is quite high, and I don’t think we currently have the cycles for it…”
We offered help and rewritten the application in Python 3, Flask, and PatternFly. We were able to rewrite around 40 percent of the code/templates. The current code is temporary at
https://github.com/xsuchy/fedora-packages-ng
and we plan to do massive merge once the new app provides the same functionality as the original one.
Jun did the great work of setting up CI, so we are immediately informed when something is broken.
We plan to continue on this task (with slower pace) and to switch production application to new code before python2 becomes unsupported in Fedora.
In Firefox 70, there is a new feature called kinetic scrolling [1]. If you scroll the web page using trackpad (or possibly touchscreen), the scroll event will not stop immediately after releasing your fingers, but it will gradually slow down, as if a rotating wheel slowly stops. After using it for a short while, I started to hate it really quickly. The problem is that the slowdown-and-stop occurs very slowly and if you just want to scroll the webpage to continue reading, you need to wait several seconds until the page fully stops moving. That’s really annoying. Fortunately, this cool new feature can be disabled. Just open about:config page in a new tab, search for apz.gtk.kinetic_scroll.enabled and set it to false. Tada! No more kinetic scrolling.
[1] I found these related Mozilla tickets: #1213601, #1564238
Fedora 31 Workstation comes with a Firefox backend moved from X11 to Wayland by default. That’s just another step in the ongoing effort of moving to Wayland. This affects GNOME on Wayland only. This article helps you understand some changes and extra steps you may wish to take depending on your preferences.
There is a firefox-wayland package available to activate the Wayland backend on KDE and Sway desktop environments.
The Wayland architecture is completely different than X11. The team merged various aspects of Firefox internals to the new protocol where possible. However, some X11 features are missing completely. For such cases you can install and run firefox-x11 package as a fallback.
If you want to run the Flash plugin, you must install the firefox-x11 package, since Flash requires X11 and GTK 2. Wayland also has a slightly different drag and drop behavior and strict popup window hierarchy.
Generally, if you think Firefox is not behaving like you want, try the firefox-x11 package. In this case, ideally you should report the misbehavior in Bugzilla.
The Wayland architecture comes with many benefits, and overcomes many limitations of X11. For instance, it can deliver smoother rendering and better HiDPI and screen scale support. You can also enable EGL hardware acceleration on Intel and AMD graphics cards. This decreases your power consumption and also gives you partially accelerated video playback. To enable it, navigate to about:config, and search for layers.acceleration.force-enabled. Set this option to true and restart Firefox.
Brave users may wish to try the Firefox next-generation renderer, called WebRender, written in Rust. To do that, search for gfx.webrender.enabled and gfx.webrender.all in about:config. Set them to true, then cross your fingers and restart Firefox.
But don’t worry — even if Firefox crashes at start after these experiments, you can launch it in safe mode to reset these options. Start Firefox from a terminal using the following command:
$ firefox -safe-mode
Many under the armor improvements and a lot of changes, new features, and new graphical experiences: here we are, the new Fedora 31 release. Obviously, the big GUI step forward for Fedora Workstation is the latest GNOME 3.34 update, which brings some visual changes, different functions, and real performance improvements. Fedora 31 also drops the 32-bit support, so now you[...]
The post Fedora 31 has just rolled out appeared first on CIALU.NET.
admin)
on October 31, 2019 07:00 AM
FOSDEM is a free-to-attend event held every year in Brussels, Belgium. It is a community-run event for developers to meet and work together. In 2020 it will be held on 1–2 February—the weekend following DevConf.CZ. The main track proposals are closed, but there are a few Fedora-related or -adjacent activities if you’re interested.
The Distributions Developer Room will be held on Sunday, 2 February. This devroom focuses on the issues specific to creating distributions, including technology and process. Talks on how distributions can cooperate are also welcome. For details, see the announcement post. You can submit your proposals through 1 December 2019 in the FOSDEM CfP tool.
The CentOS project will be holding their annual CentOS Dojo on the day before FOSDEM—Friday, 31 January. Details of the event may be found on the CentOS Wiki. While the event is CentOS-centric, there’s lots of overlap among the RHEL/Fedora/CentOS family of Linux distributions, and we encourage you to consider submitting your presentation proposals for anything you’re working on which may have some relevance to this larger ecosystem. Proposals close 18 November.
We’re coordinating a Fedora booth at FOSDEM. If you’re interested in participating, please sign up on the wiki page. If you have an accepted presentation, please let us know so we can help you promote it.
The post Fedora-related FOSDEM activities appeared first on Fedora Community Blog.
Want to use docker-compose.yaml files with podman on Fedora?
Review podman-compose! I’ll even review one of yours, no extra charge!
admiyo)
on October 30, 2019 07:59 PM
Jazz improvisation performance. You’ve been preparing. You have mastered your instrument with long tones, scales, and exercises. You have worked on general knowledge of music theory, chords, and the relationship between them. Now what?
You need to know the song. Get the song in your head. Memorize the melody. Learn the chords on Piano, even if that is not your instrument. Learn the words to the tune if there are some. Play long passages over each chord on your instrument, to get the various sounds of it in your ears. Come up with phrases that work over subsets of the chord changes, like the ii-V-I sections etc. Play along with iReal Pro or some other automated rhythm section.
By the time you get on the stand to improvise, you should not be thinking about the song. You should be getting ready to tell a story. There are a couple mental techniques you can use to develop your solo. You can build up from a musical phrase, or you can mentally tell yourself a story and play the words that you hear.
When you build up from a musical phrase, you are going to take an idea, state it and then modify it through out the solo. You want to give the audience a hook to identify. It can start with a fragment of the melody line, or a phrase in your head. Something rhythmic. Something melodic. Repeat it, as close as you can, over the changes. Even if you play the exact same notes, it will have a different effect over different chords. More likely, you will want to adjust that phrase as the chords change. Add on to it. Drop notes from it.
Sonny Rollins’s solo on “Tenor Madness” is a great example of building up a fragment this.
One technique to use, but not over use, is to quote from a well known other song. A friend of mine opened a solo by playing the first phrase from “Sanford and Son.” Quoting a phrase like this is a shortcut to connecting with the audience. It can also be fun to throw a quote in to the middle of the solo, but make sure it makes sense in the context of the solo.
You can think words in your head, and play those words. Improvise a story in your head, about Meeting Miss Jones or Something that Happened ‘Round Midnight or who you met On the A Train. You may want to pretend to be a character when you do this. Humphrey Bogart as Sam Spade in the Maltese Falcon, turning up his collar and walking away into the San Francisco rain. You are doing a performance, and the more you are in to it, and get lost in it, the more your audience will link in to your world.
If you are still learning a song, you might want to use the lyrics to keep you in place, and play over them. You don’t replay the head, just use the words as a running commentary, and play “around” them as you solo.
If you are trying to play over “Donna Lee” you might find it easier to learn and track the lyrics to “Back home in Indiana” and keep those running through your head as you solo.
Build to a climax, conclude, and hand over the mike to the next player.
sudo dnf upgrade --refreshInstall the dnf pluginsudo dnf install dnf-plugin-system-upgradeStart the upgradesudo dnf system-upgrade download --releasever=31Start the upgrade and rebootsudo dnf system-upgrade rebootGo and make a cuppa....