Administration

• Autoconf, automake, and libtool are the GNU Autotools family that generate the installation script:

./configure
make
make install

The Makefile generated by Autoconf and automake has more commands that you can run:

    make all Build programs, libraries, documentation, etc. (same as make).

    make install Install what needs to be installed, copying the files from the package’s tree to system-wide directories.

    make install-strip Same as make install, then strip debugging symbols. Some users like to trade space for useful bug reports…

    make uninstall The opposite of make install: erase the installed files. (This needs to be run from the same build tree that was installed.)

    make clean Erase from the build tree the files built by make all.

    make maintainer-clean Erase files that generated by autoconf.

    make distclean Additionally erase anything ./configure created.

    make check Run the test suite if any.

    make installcheck Check the installed programs or libraries if supported.

    make dist Recreate package-version.tar.gz from all the source files.


http://www.idryman.org/blog/2016/03/10/autoconf-tutorial-1/

• 2.2.2 Standard Makefile Targets

So far we have come across four ways to run make in the GNU Build System: make, make check, make install, and make installcheck. The words check, install, and installcheck, passed as arguments to make, are called targets. make is a shorthand for make all, all being the default target in the GNU Build System.
https://www.gnu.org/software/automake/manual/html_node/Standard-Targets.html#Standard-Targets

• This tutorial looks at the GNU Build System. From an end-user's perspective, it first describes how to build the binary executable of a GNU free and open source software package from the available source code and install it on your system. Then, from a programmer's perspective it looks at the GNU Build System for generating the scripts and makefiles which provide the infrastructure that enables the end user to build and install the GNU software executables.

https://www.softprayog.in/tutorials/understanding-gnu-build-system

• "Owl" (or "Openwall GNU/*/Linux"; please, note that only the "O" is capitalized in either case) is a security-enhanced operating system with Linux and GNU software as its core, compatible with other major distributions of GNU/*/Linux. It is intended as a server platform

Owl can be used as a base for installing whatever software is generally available for GNU/*/Linux systems.
the same CDs and ISOs also contain packages to be installed on a hard drive (using the included installer program called "settle") and full source code.

Owl includes a complete build environment capable to re-build the entire system from a source with one simple command ("make buildworld")
However, the implementation of "make buildworld" on Owl is very different from that available with *BSD. It is in fact more similar to *BSD ports/packages, covering the entire Owl userland (that is, everything but the Linux kernel).

In particular, in most cases it is possible to install applications packaged for a certain version of Red Hat Enterprise Linux, CentOS, or Fedora on Owl.
http://www.openwall.com/Owl/CONCEPTS.shtml

• The key idea of the AppImage format is one app = one file. Every AppImage contains an app and all the files the app needs to run. In other words, each AppImage has no dependencies other than what is included in the targeted base operating system (s).

https://askubuntu.com/questions/774490/what-is-an-appimage-how-do-i-install-it

• Free Thinomenon Remote Desktop Client allows running Windows® applications from various access devices including laptops, desktops, tablets and smartphones. Use Thinomenon's free RDP client for access from legacy Windows, Apple OS X and iOS, Google Android, Linux and other platforms.

http://www.thinomenon.com/products/RemoteDesktopClient/linux.aspx

• What is WinConn

WinConn simplifies creation, management and desktop integration of remote windows applications in Ubuntu Linux. It uses RemoteApp technology, implemented by FreeRDP project to provide seamless user experience. The applications run in their own window and can be used like any other locally installed Ubuntu application, without bringing the full windows desktop to the user.
http://stanev.org/winconn/

• Cmder is a software package created out of pure frustration over absence of usable console emulator on Windows. It is based on ConEmu with major config overhaul, comes with a Monokai color scheme, amazing clink (further enhanced by clink-completions) and a custom prompt layout.

https://github.com/cmderdev/cmder?lipi=urn%3Ali%3Apage%3Ad_flagship3_pulse_read%3BPFIXAkvnT%2Fq%2B3GqxhjgNdA%3D%3D

• Gow (Gnu On Windows) is the lightweight alternative to Cygwin. It uses a convenient NSIS installer that installs over 100 extremely useful open source UNIX applications compiled as native win32 binaries.

https://github.com/bmatzelle/gow/wiki?lipi=urn%3Ali%3Apage%3Ad_flagship3_pulse_read%3BPFIXAkvnT%2Fq%2B3GqxhjgNdA%3D%3D

• Functionally, vim is almost a proper superset of vi. Therefore, everything that is in vi is available in vim.

Vim adds onto those features. Here are some extended vim features:

    Vim has been ported to a much wider range of OS's than vi.
    Vim includes support (syntax highlighting, code folding, etc) for several popular programming languages (C/C++, Python, Perl, shell, etc).
    Vim integrates with cscope.
    Vim can be used to edit files using network protocols like SSH and HTTP.
    Vim includes multilevel undo/redo.
    Vim allows the screen to be split for editing multiple files.
    Vim can edit files inside a compressed archive (gzip, zip, tar, etc).
    Vim includes a built in diff for comparing files (vimdiff).
    Vim includes support for plugins, and finer control over config and startup files.
    Vim can be scripted with vimscript, or with an external scripting language (e.g. python, perl, shell)
https://askubuntu.com/questions/418396/what-is-the-difference-between-vi-and-vim

• The ancestral vi is long gone, replaced eons ago by Vim -- vi IMproved.

Vim includes extensive documentation, unless your distro installs only vim-tiny, which strips out the documentation and other fripperies, which is another reason to know the basics without having to look them up.
Most distros symlink vi to Vim, so you should be able to start it with either vi or vim.
https://www.linux.com/learn/intro-to-linux/2017/2/vim-sysadmins

• X-based VNC server

Xvnc is the Unix VNC server, which is based on a standard X server.  Applications can display themselves on it as if it were a normal X display, but they will actually appear on any connected VNC viewers rather than on a physical screen.
http://www.hep.phy.cam.ac.uk/vnc_docs/xvnc.html

• An open source remote desktop protocol(rdp) server.

http://www.xrdp.org/

• Understand Linux Load Averages and Monitor Performance of Linux

Multi-processor Vs Multi-core
Multi-processor – is where two or more physical CPU’s are integrated into a single computer system.
Multi-core processor – is a single physical CPU which has at least two or more separate cores (or what we can also refer to as processing units) that work in parallel. Meaning a dual-core has 2 two processing units, a quad-core has 4 processing units and so on.

Furthermore, there is also a processor technology which was first introduced by Intel to improve parallel computing, referred to as hyper threading.
Under hyper threading, a single physical CPU core appears as two logical CPUs core to an operating system (but in reality, there is one physical hardware component).
Present-day Intel CPUs use a combination of both multiple cores and hyper-threading technology.

Let’s say we have load averages below
On a single core system this would mean:

    The CPU was fully (100%) utilized on average; 1 processes was running on the CPU (1.00) over the last 1 minute.
    The CPU was idle by 60% on average; no processes were waiting for CPU time (0.40) over the last 5 minutes.
    The CPU was overloaded by 235% on average; 2.35 processes were waiting for CPU time (3.35) over the last 15 minutes.

On a dual-core system this would mean:

    The one CPU was 100% idle on average, one CPU was being used; no processes were waiting for CPU time(1.00) over the last 1 minute.
    The CPUs were idle by 160% on average; no processes were waiting for CPU time. (0.40) over the last 5 minutes.
    The CPUs were overloaded by 135% on average; 1.35 processes were waiting for CPU time. (3.35) over the last 15 minutes.

https://www.tecmint.com/understand-linux-load-averages-and-monitor-performance/