Zoom, zoom ... zoom
This is not the only effect from the VLC application you can set more.
If you want to use the zoom effect when you play movies with VLC software then use these settings:
Tools -> Effects and Filters (Ctr +E) -> Video Effects -> Interactive Zoom
See the next images:
tutorials, tips, tricks, commands, programming, linux, windows, database, sql, python, programming language, Fedora, drawing, painting, tutorial, tutorials
Sunday, December 29, 2019
Saturday, December 28, 2019
Fedora 31 : Run Minecraft game on Fedora distro.
To install and play the Minecraft game you need to install Java both versions JRE and JDK.
You need to buy or use only redeem codes from Minecraft Java Edition.
I download the Minecraft.tar.gz file and I unarchive into my folder named minecraft-launcher.
After that I run this command to play the game:
You need to buy or use only redeem codes from Minecraft Java Edition.
[root@desk mythcat]# cd minecraft-launcher/
[root@desk minecraft-launcher]# dnf install java-latest-openjdk
[root@desk minecraft-launcher]# dnf install java-latest-openjdk-devel
The game can download it from here.I download the Minecraft.tar.gz file and I unarchive into my folder named minecraft-launcher.
After that I run this command to play the game:
[mythcat@desk minecraft-launcher]$ ./minecraft-launcher
which: no java in (/home/mythcat/google-cloud-sdk/bin:/home/mythcat/.local/bin
:/home/mythcat/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin)
...
Thursday, December 26, 2019
Fedora 31 : Install Google Chrome.
Most Linux distributions come with dedicated browsers or Firefox browser.
But if you want to use Google services like Google Optimize then you will need Google Chrome browser.
Today I will show you how to install it in the Linux distribution Fedora 31.
But if you want to use Google services like Google Optimize then you will need Google Chrome browser.
Today I will show you how to install it in the Linux distribution Fedora 31.
[mythcat@desk ~]$ sudo dnf install https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm
[sudo] password for mythcat:
Last metadata expiration check: 2:29:06 ago on Thu 26 Dec 2019 07:54:58 PM EET.
google-chrome-stable_current_x86_64.rpm 16 MB/s | 59 MB 00:03
Dependencies resolved.
====================================================================================
Package Arch Version Repository Size
====================================================================================
Installing:
google-chrome-stable x86_64 79.0.3945.88-1 @commandline 59 M
Installing dependencies:
liberation-fonts noarch 1:2.00.5-6.fc31 fedora 8.4 k
Transaction Summary
====================================================================================
Install 2 Packages
Total size: 60 M
Total download size: 8.4 k
Installed size: 210 M
Is this ok [y/N]: y
...
Installed:
google-chrome-stable-79.0.3945.88-1.x86_64
liberation-fonts-1:2.00.5-6.fc31.noarch
Complete!
You can start it with this commands:
[mythcat@desk ~]$ google-chrome
google-chrome google-chrome-stable
Posted by
Cătălin George Feștilă
Labels:
2019,
Fedora,
Fedora 31,
google,
Google Chrome,
linux,
linux tools,
tool,
tools,
tutorial,
tutorials
Friday, December 20, 2019
Fedora 31 : Start with tito tool.
If you have some Fedora related project and you want to your output an RPM package, then you can use the tito tool.
This tool comes with the version 0.6.12 and today is finally out!
The team of this software comes with this intro:
Tito is a tool for managing RPM based projects using git for their source code repository.
Let's install it:
Now I can create my .spec file named django_project.spec:
This tool comes with the version 0.6.12 and today is finally out!
The team of this software comes with this intro:
Tito is a tool for managing RPM based projects using git for their source code repository.
Let's install it:
[root@desk mythcat]# dnf search tito
Last metadata expiration check: 1:52:16 ago on Fri 20 Dec 2019 06:10:02 PM EET.
========================== Name Exactly Matched: tito ==========================
tito.noarch : A tool for managing rpm based git projects
============================ Summary Matched: tito =============================
mtdev.x86_64 : Multitouch Protocol Translation Library
mtdev.i686 : Multitouch Protocol Translation Library
mtdev-devel.i686 : Multitouch Protocol Translation Library Development Package
mtdev-devel.x86_64 : Multitouch Protocol Translation Library Development Package
[root@desk mythcat]# dnf install tito.noarch
...
Complete!
[root@desk mythcat]# systemctl daemon-reload
Let's see the arguments of this tool:[mythcat@desk django]$ tito
Usage: tito MODULENAME --help
Supported modules:
build - Build packages.
init - Initialize directory for use by tito.
release - Build and release to yum repos
report - Display various reports on the repo.
tag - Tag package releases.
Before you use this tool you need to have these folders into your project folder:docs/
mypackage.spec
README
.tito/
src/
test/
Let's try to use it with my old django project in the directory with the git checkout of your project.[mythcat@desk projects]$ cd django/
[mythcat@desk django]$ tito init
Creating tito metadata in: /home/mythcat/projects/django/.tito
- created /home/mythcat/projects/django/.tito
- wrote tito.props
- created /home/mythcat/projects/django/.tito/packages
- wrote /home/mythcat/projects/django/.tito/packages/.readme
- committed to git
Done!
This creates a .tito folder.Now I can create my .spec file named django_project.spec:
%if 0%{?rhel} > 7 || 0%{?fedora}
%global use_python3 1
%global use_python2 0
%global ourpythonbin %{__python3}
%global our_sitelib %{python3_sitelib}
%else
%global use_python3 0
%global use_python2 1
%if 0%{?__python2:1}
%global ourpythonbin %{__python2}
%global our_sitelib %{python2_sitelib}
%else
%global ourpythonbin %{__python}
%global our_sitelib %{our_sitelib}
%endif
%endif
%{!?our_sitelib: %define our_sitelib %(%{ourpythonbin} -c "from distutils.sysconfig
import get_python_lib; print get_python_lib()")}
Name: django_chart
Version: 0.0.2
Release: 1%{?dist}
Summary: A tool for managing rpm based git projects
License: GPLv2
URL: https://github.com/catafest/django_chart
Source0: https://github.com/catafest/django_chart/archive/django_chart-%{version}-1.tar.gz
BuildArch: noarch
%if %{use_python3}
BuildRequires: python3-devel
BuildRequires: python3-setuptools
Requires: python3-setuptools
Requires: python3-bugzilla
Requires: python3-blessings
Requires: rpm-python3
%else
BuildRequires: python2-devel
BuildRequires: python-setuptools
Requires: python-setuptools
Requires: python-bugzilla
Requires: python-blessings
Requires: rpm-python
%endif
BuildRequires: asciidoc
BuildRequires: docbook-style-xsl
BuildRequires: libxslt
BuildRequires: rpmdevtools
BuildRequires: rpm-build
BuildRequires: tar
BuildRequires: which
%if 0%{?fedora}
# todo: add %%check to spec file in accordance with
# https://fedoraproject.org/wiki/QA/Testing_in_check
BuildRequires: git
BuildRequires: python-bugzilla
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-bugzilla
BuildRequires: rpm-python3
%endif
Requires: rpm-build
Requires: rpmlint
Requires: fedpkg
Requires: fedora-packager
Requires: rpmdevtools
# Cheetah used not to exist for Python 3, but it's what Mead uses. We
# install it and call via the command line instead of importing the
# previously potentially incompatible code, as we have not yet got
# around to changing this
Requires: /usr/bin/cheetah
%description
django_chart is a project for managing chart with django
git.
%prep
# the weird directory name is because github makes the directory name
# '(projectname)-(tag)', and the tags for django_chart have 'django_chart' in them and
# '-1' on the end...
%setup -q -n django_chart-django_chart-%{version}-1
sed -i 1"s|#!.*|#!%{ourpythonbin}|" bin/django_chart
%build
%{ourpythonbin} setup.py build
# convert manages
a2x -d manpage -f manpage django_chartrc.5.asciidoc
a2x -d manpage -f manpage django_chart.8.asciidoc
a2x -d manpage -f manpage django_chart.props.5.asciidoc
a2x -d manpage -f manpage releasers.conf.5.asciidoc
%install
rm -rf $RPM_BUILD_ROOT
%{ourpythonbin} setup.py install -O1 --skip-build --root $RPM_BUILD_ROOT
rm -f $RPM_BUILD_ROOT%{our_sitelib}/*egg-info/requires.txt
# manpages
%{__mkdir_p} %{buildroot}%{_mandir}/man5
%{__mkdir_p} %{buildroot}%{_mandir}/man8
cp -a django_chartrc.5 django_chart.props.5 releasers.conf.5 %{buildroot}/%{_mandir}/man5/
cp -a django_chart.8 %{buildroot}/%{_mandir}/man8/
# bash completion facilities
install -Dp -m 0644 share/django_chart_completion.sh %{buildroot}%{_datadir}/bash-completion/completions/
django_chart
%files
%doc AUTHORS COPYING
%doc doc/*
%doc %{_mandir}/man5/django_chartrc.5*
%doc %{_mandir}/man5/django_chart.props.5*
%doc %{_mandir}/man5/releasers.conf.5*
%doc %{_mandir}/man8/django_chart.8*
%{_bindir}/django_chart
%{_bindir}/generate-patches.pl
%{_datadir}/bash-completion/completions/django_chart
%dir %{our_sitelib}/django_chart
%{our_sitelib}/django_chart/*
%{our_sitelib}/django_chart-*.egg-info
%changelog
* Fri Dec 20 2019 catafest 0.0.2-1
- new package built with tito
* Fri Dec 20 2019 Catalin George Festila 0.6.12-1
If your git checkout has multiple projects/packages go to that directory from which you are creating tar.gz otherwise stay in your git root.[mythcat@desk django]$ tito tag --debug
Creating output directory: /tmp/tito
Importing tito.tagger.VersionTagger
Using tagger class:
Looking for .spec in /home/mythcat/projects/django
Using file: django_project.spec
Looking for .spec in /home/mythcat/projects/django
Using file: django_project.spec
Command: rpm --eval '%scl'
Status code: 0
Command output: %scl
Command: rpm -q --qf '%{name}
' --eval '%undefine scl' --specfile /home/mythcat/projects/django/django_project.spec 2> /dev/null |
grep -e '^$' -v | head -1
Status code: 0
Command output: django_chart
Command: git config --get user.name
Status code: 0
Command output: catafest
Command: git config --get user.email
Status code: 0
Command output: catalinfest@gmail.com
Getting latest package info from: /home/mythcat/projects/django/.tito/packages/django_chart
Getting latest package info from: /home/mythcat/projects/django/.tito/packages/django_chart
Command: rpm -q --qf '%{version}-%{release}
' --define "_sourcedir /home/mythcat/projects/django" --define 'dist %undefined' --specfile
/home/mythcat/projects/django/django_project.spec 2> /dev/null | grep -e '^$' -v | head -1
Status code: 0
Command output: 0.0.2-1
Tagging new version of django_chart: untagged -> 0.0.2-1
Cargo.toml file not found, this is probably not a Rust project
No destination version file found, skipping.
Command: git add /home/mythcat/projects/django/.tito/packages/django_chart
Status code: 0
Command output:
Command: git add /home/mythcat/projects/django/django_project.spec
Status code: 0
Command output:
Command: git commit -m 'Automatic commit of package [django_chart] release [0.0.2-1].' -m
'Created by command:' -m '/usr/bin/tito tag --debug'
Status code: 0
Command output: [master 3b2d812] Automatic commit of package [django_chart] release [0.0.2-1].
2 files changed, 126 insertions(+)
create mode 100644 .tito/packages/django_chart
create mode 100644 django_project.spec
Command: git tag -m "Tagging package [django_chart] version [django_chart-0.0.2-1] in directory
[./]." django_chart-0.0.2-1
Status code: 0
Command output:
Created tag: django_chart-0.0.2-1
View: git show HEAD
Undo: tito tag -u
Push: git push --follow-tags origin
Use the git tool for push:
git push && git push origin some-tag-1.0
If you do not want to push it to a remote repository, you must add to the following commands option --offline.
[mythcat@desk django]$ tito build --tgz [--offline]
[mythcat@desk django]$ tito build --srpm [--offline]
[mythcat@desk django]$ tito build --rpm [--offline]
This last command execute all previous steps in one and call rpmbuild on that SRPM file which will produce binary rpm package.
Monday, December 9, 2019
Fedora 31 : Can be better? part 003.
Yes! The Fedora distro Linux can be better.
One bad problem for most Fedora users is video drivers.
I have an old NVIDIA graphic card: NVIDIA Corporation GT218 [GeForce 210] (rev a2).
This worked well with the nouveau device driver.
It will be great if the detection and install of the video graphic card will start from the installation process.
Another option is to have a dedicated opensource software for detection and installation of the video card.
One bad problem for most Fedora users is video drivers.
I have an old NVIDIA graphic card: NVIDIA Corporation GT218 [GeForce 210] (rev a2).
This worked well with the nouveau device driver.
It will be great if the detection and install of the video graphic card will start from the installation process.
Another option is to have a dedicated opensource software for detection and installation of the video card.
Posted by
Cătălin George Feștilă
Labels:
2019,
Fedora,
Fedora 31,
linux,
linux tools,
tool,
tools,
tutorial,
tutorials
Saturday, December 7, 2019
Fedora 31 : Uploading a repo with Fedora.
This is a simple way to upload to the GitHub website your source code.
First, you need to create your repo on your GitHub account using New button from Your repositories on account area.
Fill with the name of your GitHub project and see the link to your project.
In my case, I used the named project django_chart and the link is https://github.com/catafest/django_chart.git.
In your local folder project from Fedora distro use this commands:
First, you need to create your repo on your GitHub account using New button from Your repositories on account area.
Fill with the name of your GitHub project and see the link to your project.
In my case, I used the named project django_chart and the link is https://github.com/catafest/django_chart.git.
In your local folder project from Fedora distro use this commands:
(env) [mythcat@desk django]$ git init
(env) [mythcat@desk django]$ git add .
(env) [mythcat@desk django]$ git commit -m "First Commit"
(env) [mythcat@desk django]$ git remote add origin https://github.com/catafest/django_chart.git
(env) [mythcat@desk django]$ git push -f origin master
Username for 'https://github.com': catafest
Password for 'https://catafest@github.com':
Enumerating objects: 8730, done.
Counting objects: 100% (8730/8730), done.
Delta compression using up to 2 threads
Compressing objects: 100% (5056/5056), done.
Writing objects: 100% (8730/8730), 14.12 MiB | 744.00 KiB/s, done.
Total 8730 (delta 2597), reused 8730 (delta 2597)
remote: Resolving deltas: 100% (2597/2597), done.
To https://github.com/catafest/django_chart.git
+ b2c0e70...0746fa8 master -> master (forced update)
This last output tells me the files are on GitHub repo project.
Wednesday, December 4, 2019
Fedora 31 : Lutris the Open Source gaming platform for Linux.
Lutris is an Open Source gaming platform for Linux. It installs and launches games so you can start playing without the hassle of setting up your games. Get your games from GOG, Steam, Battle.net, Origin, Uplay and many other sources running on any Linux powered gaming machine.
You need to create an account and you can run many games on Linux and multiple platforms, see the official website with games.
The installation process is simple to do on Fedora 31 with DNF tool:
You need to create an account and you can run many games on Linux and multiple platforms, see the official website with games.
The installation process is simple to do on Fedora 31 with DNF tool:
[root@desk mythcat]# sudo dnf install lutris
Last metadata expiration check: 0:06:35 ago on Wed 04 Dec 2019 07:15:23 PM EET.
Dependencies resolved.
======================================================================================
Package Arch Version Repository Size
======================================================================================
Installing:
lutris x86_64 0.5.3-1.fc31 fedora 2.0 M
...
Total download size: 129 M
Installed size: 708 M
Is this ok [y/N]: y
...
llvm-libs-9.0.0-1.fc31.i686 ncurses-libs-6.1-12.20190803.fc31.i686
python3-evdev-1.1.2-4.fc31.x86_64 unixODBC-2.3.7-5.fc31.x86_64
vulkan-loader-1.1.114.0-1.fc31.i686
Complete!
Posted by
Cătălin George Feștilă
Labels:
2019,
Fedora,
Fedora 31,
game,
linux,
linux tools,
tutorial,
tutorials
Saturday, November 23, 2019
Fedora 31 : Can be better? part 002.
If you want to have a USB device with the Fedora distro then the Fedora team comes with this solution, see the webpage.
Now let's make all easier for this issue. Detect your USB device...
Now let's make all easier for this issue. Detect your USB device...
[mythcat@desk ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
...
sdb 8:16 1 984M 0 disk
└─sdb1 8:17 1 983M 0 part
Be sure the USB drive has bootable flag enable:
[mythcat@desk Downloads]$ sudo fdisk /dev/sdb
Welcome to fdisk (util-linux 2.34).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): a
Selected partition 1
The bootable flag on partition 1 is disabled now.
Command (m for help): a
Selected partition 1
The bootable flag on partition 1 is enabled now.
Command (m for help): q
Umount your USB drive, do not remove it.
[mythcat@desk ~]$ sudo umount /dev/sdb
Copy the Fedora file image iso to the USB device with the dd command:
[mythcat@desk ~]$ sudo dd if=Fedora-Server-netinst-x86_64-31-1.9.iso of=/dev/sdb
1331200+0 records in
1331200+0 records out
681574400 bytes (682 MB, 650 MiB) copied, 383.766 s, 1.8 MB/s
You can test it with the qemu tool:
[mythcat@desk ~]$ sudo qemu-system-x86_64 -hda /dev/sdb
Posted by
Cătălin George Feștilă
Labels:
2019,
Fedora,
Fedora 31,
linux,
linux tools,
tool,
tools,
tutorial,
tutorials
Thursday, November 14, 2019
Fedora 31 : Can be better? part 001.
I started using Fedora distribution several years ago after I tried several distros (Suse, RedHat 6, Debian, Gentoo and many more).
I was pleased with the test and speed.
I must admit that from the first used version 9 (Sulfur) and until now it is very changed and unknown for many users
That's why I decided to present in this series of mini-tutorials called Can be better? various lesser-known aspects that underlie it and its more precise use.
I will not abide by a predetermined order in the use of Fedora distribution.
I will only point to useful information for any Fedora user.
Let's start the first part of this tutorial named Can be better? part 001. with a brief introduction to the Wikipedia page and the official one.
An interesting aspect of Fedora configuration is the file sysctl.conf.
You can read the manual page with this command:
The last parameter named kernel.exec-shield fix NX protection also called Data Execution Prevention (DEP), to prevent buffer stacks from taking down your machine.
You can check this with:
I was pleased with the test and speed.
I must admit that from the first used version 9 (Sulfur) and until now it is very changed and unknown for many users
That's why I decided to present in this series of mini-tutorials called Can be better? various lesser-known aspects that underlie it and its more precise use.
I will not abide by a predetermined order in the use of Fedora distribution.
I will only point to useful information for any Fedora user.
Let's start the first part of this tutorial named Can be better? part 001. with a brief introduction to the Wikipedia page and the official one.
An interesting aspect of Fedora configuration is the file sysctl.conf.
You can read the manual page with this command:
man 8 sysctl
Part of this file should contain these lines:
vm.overcommit_memory=2
vm.overcommit_ratio=100
kernel.exec-shield=1
This parameter named vm.overcommit_memory can be set this way:
0: heuristic overcommit (this is the default)
1: always overcommit, never check
2: always check, never overcommit
For this parameter named vm.overcommit_ratio any value to anything less than 100 is almost always incorrect.The last parameter named kernel.exec-shield fix NX protection also called Data Execution Prevention (DEP), to prevent buffer stacks from taking down your machine.
You can check this with:
[root@desk mythcat]# grep nx /proc/cpuinfo
Posted by
Cătălin George Feștilă
Labels:
2019,
Fedora,
Fedora 31,
linux,
linux tools,
tool,
tools,
tutorial,
tutorials
Sunday, November 10, 2019
Fedora 31 : Use bash script to see all the permissions.
This tutorial will show you how to generate all the permissions using one file named file_test.
[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
Let's see the bash script file named 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
You can run the script:
[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
The out file show all permissions for files:
[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
The results file show the permissions:
[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
Posted by
Cătălin George Feștilă
Labels:
2019,
bash,
bash shell,
Fedora,
Fedora 31,
linux,
linux tools,
tutorial,
tutorials
Fedora 31 : another FASM tutorial with Linux.
Today I wrote another tutorial about FASM and assembly language on my website.
Because I used the Fedora distro I add my tutorial here.
If you want to learn assembly programming for Windows O.S. or Linux with the Intel C.P.U. then you need the FASM tool and this manual.
Today I will show you how to create a file using my Fedora 31 Linux distro and FASM tool.
The name of this file will be new_file.txt.
The assembly program will use INT 0x08 to create the file.
Let's see some octal permissions:
Because I used the Fedora distro I add my tutorial here.
If you want to learn assembly programming for Windows O.S. or Linux with the Intel C.P.U. then you need the FASM tool and this manual.
Today I will show you how to create a file using my Fedora 31 Linux distro and FASM tool.
The name of this file will be new_file.txt.
The assembly program will use INT 0x08 to create the file.
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
>
The program also set the file permissions in the rcx register.Let's see some octal permissions:
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
Posted by
Cătălin George Feștilă
Labels:
2019,
assembly,
fasm,
Fedora,
Fedora 31,
linux,
linux tools,
tutorial,
tutorials
Saturday, November 9, 2019
Fedora 31 : The new Fedora 31 Linux distro.
I tested today the new Fedora 31.
This new Fedora comes with many features.
One is the Toolbox tool that offers a familiar RPM-based environment for developing and debugging software that runs fully unprivileged using Podman.
Fedora 31 significantly improves the speed of update installation, as packages are now compressed with zstd instead of xz.
This commands let you to upgrading Fedora 30 to Fedora 31.
This new Fedora comes with many features.
One is the Toolbox tool that offers a familiar RPM-based environment for developing and debugging software that runs fully unprivileged using Podman.
Fedora 31 significantly improves the speed of update installation, as packages are now compressed with zstd instead of xz.
This commands let you to upgrading Fedora 30 to Fedora 31.
[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
You can see I remove the xorg driver because system-upgrade don't let me to update.
Posted by
Cătălin George Feștilă
Labels:
2019,
dnf,
Fedora,
Fedora 31,
linux,
linux tools,
tutorial,
tutorials
Monday, November 4, 2019
Fedora 30 : How to remove packages without dependency.
In this tutorial, I will show you how to remove packages without dependency.
I have this software named freecad.x86_64 and I want to remove it.
If I use the dnf tool then I got this output:
The next commands will fix and remove the package:
I have this software named freecad.x86_64 and I want to remove it.
If I use the dnf tool then I got this output:
[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
...
The package is from Nightly FreeCAD, you can enable it if you want to install later:
[root@desk mythcat]# sudo dnf copr enable @freecad/nightly
To solve this issue you need to change this file:
[root@desk mythcat]# vim /etc/dnf/dnf.conf
From clean_requirements_on_remove=True to clean_requirements_on_remove=False.The next commands will fix and remove the package:
[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]:
...
Posted by
Cătălin George Feștilă
Labels:
2019,
dnf,
Fedora,
Fedora 30,
linux,
linux tools,
tutorial,
tutorials
Subscribe to:
Posts (Atom)