@ -26,11 +26,11 @@ This exercise is a part of [Linux servers (ICT4TN021, spring 2018) // Linux-palv
**a)** Create your own Linux USB live stick. Try it out on a non-school computer. This section does not require installation of Linux. However, if you decided to install Linux, you should take proper backups first.
--------------
**Answer:** I did this with [Rufus Windows application](https://rufus.akeo.ie/) on Microsoft Windows 7 which was run inside [Oracle VirtualBox](https://fi.wikipedia.org/wiki/VirtualBox) as a virtual machine. Alternative methods include [UNetbootin](https://unetbootin.github.io/), [ISO Image Writer](https://github.com/KDE/isoimagewriter) or dd command (default location on Linux: /usr/bin/dd) which is a part of [Coreutils](http://www.gnu.org/software/coreutils/coreutils.html). Rufus allows you to create a live USB stick using either ISO or DD method which differ from each other, as the developer has explained [on his GitHub site](https://github.com/pbatard/rufus/issues/843#issuecomment-255680876).
**Answer:** I did this with [Rufus Windows application](https://rufus.akeo.ie/) on Microsoft Windows 7 which was run inside [Oracle VirtualBox](https://fi.wikipedia.org/wiki/VirtualBox) as a virtual machine. Alternative methods include [UNetbootin](https://unetbootin.github.io/), [ISO Image Writer](https://github.com/KDE/isoimagewriter) or `dd` command (default location on Linux: /usr/bin/dd) which is a part of [Coreutils](http://www.gnu.org/software/coreutils/coreutils.html). Rufus allows you to create a live USB stick using either ISO or DD method which differ from each other, as the developer has explained [on his GitHub site](https://github.com/pbatard/rufus/issues/843#issuecomment-255680876).
Let's take a detailed look for two of these approaches: Rufus on Windows 7 and dd command on Linux (any Linux distribution applies here).
Let's take a detailed look for two of these approaches: Rufus on Windows 7 and `dd` command on Linux (any Linux distribution applies here).
**Alternative 1 - Rufus (Windows, GUI-based)**
#### Alternative 1 - Rufus (Windows, GUI-based)
You can use either Windows 7 or 10 (any student/enterprise/server subversion applies here). You can run Windows either in a virtual machine or as physically installed in your mass media storage (SSD/HDD). Whichever method you choose to run Windows, it doesn't really matter. The most important part is that you have a working operating system.
@ -43,39 +43,38 @@ Let's download a widely used Xubuntu 16.04.3 LTS (x86_64 processor architecture)
[Xubuntu 16.04.3 LTS - ISO image file directly from a server - 1.2G](http://cdimage.ubuntu.com/xubuntu/releases/16.04.3/release/xubuntu-16.04-desktop-amd64.iso)
**Comparing checksums:**
**Comparing checksums**
If you wanted to make sure the ISO image you just downloaded is valid, you should check its checksum (mainly for security reasons). In this way you make sure that no malicious party has altered the image you trust and the download process has succeeded. You should take a closer look on sha256sum and md5sum values of your ISO image file. The value must match the one which is published on the Ubuntu download site ([sha256sum](http://cdimage.ubuntu.com/xubuntu/releases/16.04.3/release/SHA256SUMS), [md5sum](http://cdimage.ubuntu.com/xubuntu/releases/16.04.3/release/MD5SUMS)).
On Linux: check checksums with commands *sha256sum xubuntu-16.04-desktop-amd64.iso* and *md5sum xubuntu-16.04-desktop-amd64.iso*
On Linux: check checksums with commands `sha256sum xubuntu-16.04-desktop-amd64.iso` and `md5sum xubuntu-16.04-desktop-amd64.iso`
On Windows: Use [Microsoft File Checksum Integrity Verifier](https://www.microsoft.com/en-us/download/details.aspx?id=11533) or check a CertUtil-based solution [given on superuser.com](https://superuser.com/questions/245775/is-there-a-built-in-checksum-utility-on-windows-7/898377#898377)
**NOTE:** Checking checksums is highly recommended. For instance, Linux Mint network servers were hacked due to outdated server software in 2016, resulting to maliciously injected ISO images uploaded by hostile attackers. In addition, the Linux Mint forum software was affected, as well (user credentials leaked). More about the incident is explained [on Linux Mint blog](https://blog.linuxmint.com/?p=2994).
5. Plug in an empty and large enough USB stick into your computer (4GiB should be sufficient). It is highly recommended that you have formatted the stick in advance because Rufus overwrites any existing files existing in the USB stick in order to place required Linux files in the stick. If your stick contained any important files, they should be moved from the stick to somewhere safe location before proceeding here.
6. Once the stick is emptied (and probably formatted), launch Rufus application. Select the USB stick as a target device in *Device* menu. All other settings can be left in their default values. Choose downloaded Xubuntu 16.04.3 LTS ISO image file from the dropdown menu located at the right of *Create a bootable disk using* part. The dropdown menu is presented as a disc icon without any texts.
6. Once the stick is emptied (and probably formatted), launch Rufus application. Select the USB stick as a target device in *Device* menu. All other settings can be left in their default values. Choose downloaded Xubuntu 16.04.3 LTS ISO image file from the dropdown menu located at the right of **Create a bootable disk using** part. The dropdown menu is presented as a disc icon without any texts.
7. Click *Start*, choose ISO method as a writing method once asked. Read the warnings. If all steps have been successfully accomplished so far, proceed with the writing operation.
8. Wait until the ISO image file has been written into the USB stick. Once done, reboot your computer with the USB stick attached. Immediately the computer has rebooted, press a button which you can access your BIOS/UEFI/Boot options menu with. Choose the Xubuntu 16.04.3 LTS USB stick (which should appear in the boot list). Start the operating system boot-up process bt selecting *Try without installing* option (this step varies between Linux distribution. More generally, you can also choose *Install <whateverdistro>* option and select installation on the live USB Linux desktop environment). Wait until the operating system has been booted up. Start installation and follow the instructions.
8. Wait until the ISO image file has been written into the USB stick. Once done, reboot your computer with the USB stick attached. Immediately the computer has rebooted, press a button which you can access your BIOS/UEFI/Boot options menu with. Choose the Xubuntu 16.04.3 LTS USB stick (which should appear in the boot list). Start the operating system boot-up process bt selecting **Try without installing** option (this step varies between Linux distribution. More generally, you can also choose **Install <whateverdistro>** option and select installation on the live USB Linux desktop environment). Wait until the operating system has been booted up. Start installation and follow the instructions.
The installation process is not defined in detail here because installation steps varies from Linux distribution to distribution. However, basic principle is to install the operating system with good and strong passwords. Encrypted home folder or HDD/SSD partition options should also be considered. After you have successfully installed Linux, detach the live USB stick and reboot your computer. You should be able to access the installed Linux distribution without the USB stick.
When writing and applying passwords, please pay attention to correct keyboard layouts. In my case, I use a Swedish (Finnish) keyboard layout which differs from the default en_US layout. Therefore, mistyping characters can easily happen. Many Linux distributions allow you to change the keyboard layout during the installation process. Unless you're not able to do it in installation window, you can change the keyboard layout temporarily by executing *setxkbmap fi* in a local shell environment (NOTE: graphical environment is required since the command is a part of graphical X11 environment!). You can open up a local shell by opening a terminal emulator while running Linux from your USB stick. NOTE: changing passwords must be done before writing them in the installation steps!
**Alternative 2 - dd command (Linux, CLI-based)**
#### Alternative 2 - dd command (Linux, CLI-based)
In case you use any Unix-based operating system (Linux, GNU/Linux, Apple MacOS, FreeBSD), you can create a USB live stick by using shell-based dd command. This method does not require a graphical desktop environment. **NOTE!** Commands on Apple MacOS may not be exactly equal to Linux ones if you use extra parameters in the following commands.
In case you use any Unix-based operating system (Linux, GNU/Linux, Apple MacOS, FreeBSD), you can create a USB live stick by using shell-based `dd` command. This method does not require a graphical desktop environment. **NOTE!** Commands on Apple MacOS may not be exactly equal to Linux ones if you use extra parameters in the following commands.
The following instructions assume that you have only a command line environment and you have a working network connection.
1. At first, you need to download an ISO image of your Linux distribution of choice. There are usually two options: download ISO image from a centralized server or download ISO image using torrent protocol. In the following steps, we download Xubuntu 16.04.3 LTS (x86_64).
a. Centralized server:
- requires that *wget command* exists in the system
- requires that `wget` command exists in the system
2. Plug in an empty and large enough USB stick into your computer (4GiB should be sufficient). It is highly recommended that you have formatted the stick in advance but you can format the stick with *fdisk* command, as well ([util-linux](https://www.kernel.org/pub/linux/utils/util-linux/)). When using fdisk, please follow [these instructions](https://www.cyberciti.biz/faq/linux-how-to-delete-a-partition-with-fdisk-command/), for example. In case you have important files to be copied from your USB stick, copy the files with the following command sequence. We assume that the stick is not yet mounted on the system. Command sequence is expected to be executed with the default user (UID = 1000) which belongs to the default user group (GID = 1000). Correct USB stick device name and partition number (*/dev/XdYZ*) must be find out in advance by executing command *sudo fdisk -l*. Y stands for the device's alphabetical ID, Z stands for partition number (*/dev/sda1*, for example). X can have value *h* (IDE-based HDD/SSD's) or *s* (SATA-based HDD/SSD's). Newer NVMe-based storage solutions such as Samsung EVO series 860/960 use syntax */dev/nvme0n1p1* in which 1 stands for the device number and *p1* stands for the partition number.
2. Plug in an empty and large enough USB stick into your computer (4GiB should be sufficient). It is highly recommended that you have formatted the stick in advance but you can format the stick with `fdisk` command, as well ([util-linux](https://www.kernel.org/pub/linux/utils/util-linux/)). When using fdisk, please follow [these instructions](https://www.cyberciti.biz/faq/linux-how-to-delete-a-partition-with-fdisk-command/), for example. In case you have important files to be copied from your USB stick, copy the files with the following command sequence. We assume that the stick is not yet mounted on the system. Command sequence is expected to be executed with the default user (UID = 1000) which belongs to the default user group (GID = 1000). Correct USB stick device name and partition number (*/dev/XdYZ*) must be find out in advance by executing command `sudo fdisk -l`. Y stands for the device's alphabetical ID, Z stands for partition number (*/dev/sda1*, for example). X can have value `h` (IDE-based HDD/SSD's) or `s` (SATA-based HDD/SSD's). Newer NVMe-based storage solutions such as Samsung EVO series 860/960 use syntax */dev/nvme0n1p1* in which `1` stands for the device number and `p1` stands for the partition number.
**NOTE:** If you have any USB stick partitions mounted already on the system, you should **not** use */mnt/livestick** location in above commands. Instead, use the path you can extract for the correct USB stick partition with command *mount*.
**NOTE:** If you have any USB stick partitions mounted already on the system, you should **not** use `/mnt/livestick` location in above commands. Instead, use the path you can extract for the correct USB stick partition with `mount` command.
3. When you have backed up your important files earlier stored in the USB stick, you have confirmed the USB stick is empty and you have successfully downloaded your Linux distribution ISO image, you can start proceeding with the writing operations.
**NOTE!** You must be extra careful with dd command. If used wrongly, the command can destroy any data you have in your HDD/SSD or in any storage device. Recovering files is a headache and you really don't want to end up having one! One key principle is to triple check all locations given for the dd command and check that used locations are in correct places (so that input and output operations are being executed for correct devices and the devices don't mix up).
**NOTE!** You must be extra careful with `dd` command. If misused, the command can destroy any data you have in your HDD/SSD or in any storage device. Recovering files is a headache and you really don't want to end up having one! One key principle is to triple check all locations given for the `dd` command and check that used locations are in correct places (so that input and output operations are being executed for correct devices and the devices don't mix up).
4. Let's begin with Xubuntu 16.04.3 LTS USB writing operations. In this section we assume that you have successfully downloaded the ISO image and you definitely know the correct path for your USB stick device (syntax: /dev/sda). **NOTE!** I don't refer to USB stick partition path (syntax: /dev/sda1). The device path syntax is as stated: */dev/sda*, */dev/sdb*, etc. dd command is executed as the root user (Linux main user/super user). dd command doesn't confirm the command syntax is correct so you must write it correctly in the beginning. If you are not sure about the correct syntax, please contant an expert.
4. Let's begin with Xubuntu 16.04.3 LTS USB writing operations. In this section we assume that you have successfully downloaded the ISO image and you definitely know the correct path for your USB stick device (syntax: `/dev/sda`). **NOTE!** I don't refer to USB stick partition path (syntax: /dev/sda1). The device path syntax is as stated: `/dev/sda`, `/dev/sdb`, etc. `dd` command is executed as the root user (Linux main user/super user). `dd` command doesn't confirm the command syntax is correct so you must write it correctly in the beginning. If you are not sure about the correct syntax, please contant an expert.
The command syntax (NOTE: not likely the exact command in your environment!) is as follows:
@ -114,20 +113,22 @@ The command syntax (NOTE: not likely the exact command in your environment!) is
where /dev/sdb is your USB stick as seen on Linux system. **Use correct, your exact device identifier instead of the one shown above**.
where `/dev/sdb` is your USB stick as seen on Linux system. **Use correct, your exact device identifier instead of the one shown above**.
If you want more instructions how to use the 'dd' command, it is recommended to read the following wiki, for example: [Wikipedia - dd (Unix)](https://en.wikipedia.org/wiki/Dd_(Unix))
If you want more instructions how to use the `dd` command, it is recommended to read the following wiki, for example: [Wikipedia - dd (Unix)](https://en.wikipedia.org/wiki/Dd_(Unix))
5. Wait until the ISO image file has been written into the USB stick. Once done, reboot your computer with the USB stick attached. Immediately the computer has rebooted, press a button which you can access your BIOS/UEFI/Boot options menu with. Choose the Xubuntu 16.04.3 LTS USB stick (which should appear in the boot list). Start the operating system boot-up process bt selecting *Try without installing* option (this step varies between Linux distribution. More generally, you can also choose *Install <whateverdistro>* option and select installation on the live USB Linux desktop environment). Wait until the operating system has been booted up. Start installation and follow the instructions.
5. Wait until the ISO image file has been written into the USB stick. Once done, reboot your computer with the USB stick attached. Immediately the computer has rebooted, press a button which you can access your BIOS/UEFI/Boot options menu with. Choose the Xubuntu 16.04.3 LTS USB stick (which should appear in the boot list). Start the operating system boot-up process bt selecting **Try without installing** option (this step varies between Linux distribution. More generally, you can also choose **Install <whateverdistro>** option and select installation on the live USB Linux desktop environment). Wait until the operating system has been booted up. Start installation and follow the instructions.
The installation process is not defined in detail here because installation steps varies from Linux distribution to distribution. However, basic principle is to install the operating system with good and strong passwords. Encrypted home folder or HDD/SSD partition options should also be considered. After you have successfully installed Linux, detach the live USB stick and reboot your computer. You should be able to access the installed Linux distribution without the USB stick.
When writing and applying passwords, please pay attention to correct keyboard layouts. In my case, I use a Swedish (Finnish) keyboard layout which differs from the default en_US layout. Therefore, mistyping characters can easily happen. Many Linux distributions allow you to change the keyboard layout during the installation process. Unless you're not able to do it in installation window, you can change the keyboard layout temporarily by executing *setxkbmap fi* in a local shell environment (NOTE: graphical environment is required since the command is a part of graphical X11 environment!). You can open up a local shell by opening a terminal emulator while running Linux from your USB stick. NOTE: changing passwords must be done before writing them in the installation steps!
**b)** List hardware components of your new Linux computer (*sudo lshw -short -sanitize*).
**b)** List hardware components of your new Linux computer (sudo lshw -short -sanitize).
--------------
**Answer:** *sudo lshw -short -sanitize* gives the following information (assuming that you have package *lshw* installed and proper commands *sudo* and *lshw* are available on the system):
**Answer:**
`sudo lshw -short -sanitize` gives the following information (assuming that you have package `lshw` installed and commands `sudo` and `lshw` are available on the system):
Detailed comments about the listed devices have been included after each terminal output line (therefore, the output is not exactly as written by the command to stdout/output).
@ -170,28 +171,28 @@ Detailed comments about the listed devices have been included after each termina
| /0/100/1f.2storage8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] | SATA controller of C220 chipset family for SATA-based mass media storage inputs |
| /0/100/1f.3bus8 Series/C220 Series Chipset Family SMBus Controller | Power management [System Management Bus controller](https://en.wikipedia.org/wiki/System_Management_Bus) |
P.S. If you frequently listed your hardware on a Linux computer, you should consider creating a *bash alias command* for this purpose (assuming your default shell environment is bash). Basic idea is to simplify commands you need to type each time you want to do something. For listing hardware, write a the following in your _$HOME/.bashrc_ file (it's a hidden file):
P.S. If you frequently listed your hardware on a Linux computer, you should consider creating a *bash alias command* for this purpose (assuming your default shell environment is bash). Basic idea is to simplify commands you need to type each time you want to do something. For listing hardware, write a the following in your `$HOME/.bashrc` file (it's a hidden dotfile):
```
alias listhw='sudo lshw -short -sanitize'
```
Next time you launch a bash shell session, you should be able to list your hardware by simply executing command *listhw*, defined in your _$HOME/.bashrc_ file.
Next time you launch a bash shell session, you should be able to list your hardware by simply executing `listhw` command, defined now in your `$HOME/.bashrc` file.
If you want to create this command globally accessible for all users, you can write the above code in /etc/bash.bashrc file as root. Alternatively, create a file _/usr/bin/local/listhw_ as root with the following contents:
If you want to create this command globally accessible for all users, you can write the above code in `/etc/bash.bashrc` file as root (or with `sudo`). Alternatively, create a file `/usr/bin/local/listhw` as root (or with `sudo`) with the following contents:
```
#!/bin/bash
sudo lshw -short -sanitize
```
Use command _sudo nano _/usr/bin/local/listhw_ for that.
Use command `sudo nano /usr/bin/local/listhw` for that.
The file is not executable by default. In order to make it executable, apply the following command:
```
sudo chmod +x /usr/bin/local/listhw
```
Alternative and additional commands to list hardware are *lspci* (list PCI devices), *hwinfo* (defailed output), *lsusb* (list USB devices). Availability of these commands vary and you may need to install extra packages in your Linux distribution. On Ubuntu, execute the following command:
Alternative and additional commands to list hardware are `lspci` (list PCI devices), `hwinfo` (defailed output), `lsusb` (list USB devices). Availability of these commands vary and you may need to install extra packages in your Linux distribution. On Ubuntu, execute the following command:
Thunar is a user-friendly and easily understandable [GTK+-based](https://en.wikipedia.org/wiki/GTK+) file manager. It's not as customizable as [Qt-based](https://en.wikipedia.org/wiki/Qt_%28software%29) [Dolphin](https://www.kde.org/applications/system/dolphin/) but sufficient for daily basic usage. Thunar is the default file manager for [XFCE desktop environment](https://en.wikipedia.org/wiki/Xfce).
Gedit is a simple GTK+-based text editor, targeted to [GNOME desktop environment](https://en.wikipedia.org/wiki/GNOME). Alternative text editors are, for example, [Mousepad](https://github.com/codebrainz/mousepad), [Kate](https://www.kde.org/applications/utilities/kate/), [KWrite](https://www.kde.org/applications/utilities/kwrite/) and [Geany](https://en.wikipedia.org/wiki/Geany).
GParted is a popular GTK+-based graphical front-end for CLI-based, GPL3-licensed [GNU Parted](http://www.gnu.org/software/parted/parted.html) back-end. Similar programs include a Qt-based [KDE Partition Manager](https://www.kde.org/applications/system/kdepartitionmanager/), targeted mainly to [KDE](https://en.wikipedia.org/wiki/Kde) and [LXQt](https://en.wikipedia.org/wiki/LXQt) desktop environments.
**Installation of Thunar, Gedit and GParted on Debian-based distributions**
### Installation of Thunar, Gedit and GParted on Debian-based distributions
#### Via official package repositories
**Via official package repositories:**
On Debian-based distributions (like Xubuntu), you can install the selected three programs with a single command, like:
where _sudo apt-get update_ stands for "Update and synchronize package database list to correspond with newer available program versions", _&&_ stands for "If the previous command was successful, proceed with the following command", _sudo apt-get install -y_ stands for "Install the following packages without confirming (-y parameter)", and finally, _thunar gedit gparted_ stands for "Application names found in the available repositories listed in _/etc/apt/sources.list_ file and in files in _/etc/apt/sources.list.d/_ directory and which are parameters for _apt-get_ command".
where `sudo apt-get update` stands for "Update and synchronize package database list to correspond with newer available program versions", `&&` stands for "If the previous command was successful, proceed with the following command", `sudo apt-get install -y` stands for "Install the following packages without confirming (-y parameter)", and finally, `thunar gedit gparted` stands for "Application names found in the available repositories listed in `/etc/apt/sources.list` file and in files in `/etc/apt/sources.list.d/` directory and which are parameters for `apt-get` command".
_sudo_ part before the forementioned commands stands for "Grant me temporary root privileges to execute the following commands as root". It is essential that the current user is in _sudo_ group and all members of group _sudo_ are allowed to gain temporary root privileges (uncomment line _%sudo ALL=(ALL) ALL_ in file _/etc/sudoers_ as root).
`sudo` part before the forementioned commands stands for "Grant me temporary root privileges to execute the following commands as root". It is essential that the current user is in `sudo` group and all members of `sudo` group are allowed to gain temporary root privileges (uncomment line `%sudo ALL=(ALL) ALL` in file `/etc/sudoers` as root using `visudo` command).
By executing the above command, we assume that the system has established internet connection, [Dpkg](https://en.wikipedia.org/wiki/Dpkg) works as intended (it has not already locked file */var/lib/dpkg/lock*, for example) and no other installation process is being executed on.
By executing the above command, we assume that the system has established internet connection, [Dpkg](https://en.wikipedia.org/wiki/Dpkg) works as intended (it has not already locked file `/var/lib/dpkg/lock`, for instance) and no other installation process is being executed on.
You can execute the command without sudo in root terminal, but accessing root terminal is not highly recommended in server environments. In root terminal, the command would be:
You can execute the command without sudo in root terminal, but accessing root terminal is not highly recommended in server environments. In root terminal, the command would be (simply: the same command sequence without `sudo`):
You can search for any packages with *apt-cache search package-name* command. It may not be the primary approach but you can search for packages on official [Ubuntu repositories website](https://packages.ubuntu.com/) on Linux Ubuntu distributions (Xubuntu, Ubuntu, Lubuntu, Kubuntu, Ubuntu Bugdie and so on). Alternatively, you can also install packages with *aptitude* command if you have installed package *aptitude*. Command syntax for installing packages with aptitude is
You can search for any packages with `apt-cache search package-name` command. It may not be the primary approach but you can search for packages on official [Ubuntu repositories website](https://packages.ubuntu.com/) on Linux Ubuntu distributions (Xubuntu, Ubuntu, Lubuntu, Kubuntu, Ubuntu Bugdie and so on). Alternatively, you can also install packages with `aptitude` command if you have installed package *aptitude*. Command syntax for installing packages with aptitude is
```
sudo aptitude install package-name
```
**Via local packages or from source code:**
#### Via local packages or from source code
If you consider installing local packages, keep in mind that you need to track all required package dependencies. This can easily lead to [Dependency hell](https://en.wikipedia.org/wiki/Dependency_hell) situation. Therefore, installing local packages suits best for commercial, separately distributed software which are bundled with their dependencies and can be installed out-of-the-box without worrying about dependencies.
All installable packages on Debian-based Linux distributions are known as _deb packages_ with suffix _.deb_. Therefore, local packages can be installed with the following command:
All installable packages on Debian-based Linux distributions are known as **deb packages** with suffix `.deb`. Therefore, local packages can be installed with the following command:
```
sudo dpkg -i my-deb-package.deb
```
If any unsatisfied dependencies are present, you should do as usually instructed:
If any unsatisfied dependencies are present, you may consider doing as usually instructed:
```
sudo apt-get -f install
```
Please note that this does not always work, can break your system and make things just too troublesome to sort out. For example, your program may depends on a previous version of a package which is already installed or your system or/and not available on the official repositories. Installing a previous version can seriously break your system. In some rare cases, packages can be offered with two versions where the older version is known as _compatibility package_, usually installing older library versions to your system, co-existing with newer ones. However, keep in mind that your _.deb_ package must be aware of this _compatibility version_ (so that it depends exactly on that compatibility version instead of the officially named one. This is just a naming issue).
Please note that this does not always work, can break your system and make things just too troublesome to sort out. For instance, your program may depends on a previous version of a package which is already installed or your system or/and not available on the official repositories. Installing a previous version can seriously break your system. In some rare cases, packages can be offered with two versions where the older version is known as **compatibility package**, usually installing older library versions to your system, co-existing with newer ones. However, keep in mind that your `.deb` package must be aware of this **compatibility version** (so that it depends exactly on that compatibility version instead of the officially named one. This is just a naming issue).
You can force package installation on the system, ignoring package dependencies. In this case, you **must** know what you're doing, and this approach is really not recommended for Linux novices.
**NOTE:** You can force package installation on the system, ignoring package dependencies. In this case, you **must** know what you're doing, and this approach is really not recommended for Linux novices!
If you want to compile software directly from source, you essentially need *[dh_make](https://manpages.debian.org/jessie/dh-make/dh_make.8.en.html)* and *[dpkg-buildpackage](http://man7.org/linux/man-pages/man1/dpkg-buildpackage.1.html)* commands available on your Debian-based operating system. Usually *[cmake](https://cmake.org/)*, *[make](https://en.wikipedia.org/wiki/Make_(software))* and *gcc* ([GNU Compiler Collection](https://gcc.gnu.org/)) are required as well. Not forgetting any extra _build time dependencies_, usually marked with _-dev_ suffix (development headers) in Debian-based Linux distributions. _Runtime dependencies_ can be described in package description.
If you want to compile software directly from source, you essentially need **[dh_make](https://manpages.debian.org/jessie/dh-make/dh_make.8.en.html)** and **[dpkg-buildpackage](http://man7.org/linux/man-pages/man1/dpkg-buildpackage.1.html)** commands available on your Debian-based operating system. Usually **[cmake](https://cmake.org/)**, **[make](https://en.wikipedia.org/wiki/Make_(software))** and **gcc** ([GNU Compiler Collection](https://gcc.gnu.org/)) are required as well. Not forgetting any extra **build time dependencies**, usually marked with `-dev` suffix (development headers) on Debian-based Linux distributions. **Runtime dependencies** can be described in package description.
Any package dependencies (buildtime or runtime) are defined in Debian control file which can be supplied with the package or you need to create and configure it by your own.
Any package dependencies (buildtime or runtime) are defined in **[Debian control file](https://www.debian.org/doc/debian-policy/ch-controlfields.html)** which can be supplied with the package or you need to create and configure it by your own.
On Ubuntu, you can install most essential and widely used build time tools with:
@ -285,15 +288,15 @@ if you considered installing a remotely available package directly from source,
aptitude show package-name
```
where package-name is the package of your choice. Replace this string with the correct name,
where `package-name` is the package of your choice. Replace this string with the correct name.
Additionally, you can investigate required dependencies by checking any header (_.h_) files required in C/C++ source files, if the program is based on these languages. By tracking down required headers it is possible to figure out required dependencies in some extent. In addition, check out official websites of the program (GitHub, BitBucket or another homepage), possibly contant the developer and/or check out any supplied library files (suffix is _.so_) and their dependencies with [ldd command](https://en.wikipedia.org/wiki/Ldd_%28Unix%29). On Ubuntu, you can also check out [packages.ubuntu.com](https://packages.ubuntu.com/) for dependencies if the package is available on official repositories.
Additionally, you can investigate required dependencies by checking any header (`.h`) files required in C/C++ source files, if the program is based on these programming languages. By tracking down required headers it is possible to figure out required dependencies in some extent. In addition, check out official websites of the program (GitHub, BitBucket or another homepage), possibly contant the developer and/or check out any supplied library files (suffix is `.so`) and their dependencies with **[ldd command](https://en.wikipedia.org/wiki/Ldd_%28Unix%29)**. On Ubuntu, you can also check out [packages.ubuntu.com](https://packages.ubuntu.com/) for dependencies if the package is available on official repositories.
Please see my practical [example 1](https://github.com/Fincer/linux_server_setup/blob/master/scripts/compile-xcmenu-screenshot.sh) and [example 2](https://github.com/Fincer/winecfg_patch) for compiling software on Linux.
You can also apply patches directly to source code of a program by using [diff](https://www.gnu.org/software/diffutils/manual/html_node/Example-Unified.html) and [patch](https://en.wikipedia.org/wiki/Patch_%28Unix%29) commands. Patches must be applied before compiling the program.
You can also apply patches directly to source code of a program by using **[diff](https://www.gnu.org/software/diffutils/manual/html_node/Example-Unified.html)** and **[patch](https://en.wikipedia.org/wiki/Patch_%28Unix%29)** commands. Patches must be applied before compiling the program.
**Removal of packages:**
#### Uninstallation of packages
You can effectively remove packages on Debian-based Linux distributions with:
@ -319,12 +322,13 @@ and by reading command-related manual page:
man apt-get
```
Manual pages in any commands are highly supported in multiple Linux distributions. The command syntax is always the same: _man my_command_. Additionally, _--help_ paremeter is widely accepted by many Unix/Linux CLI programs.
Manual pages in any commands are highly supported in multiple Linux distributions. The command syntax is always the same: `man my_command`. Additionally, `--help` or `-h` parameter is widely accepted by many Unix/Linux CLI programs.
**NOTE:** Although Linux distributions don't have any similar to Windows registry hell (unclean registry after software removal), keep in mind that any configuration files created **afterwards** by a Linux program are not handled by Linux package managers. In other words: package managers can't track files created afterwards by your program in your `$HOME` folder. This is mostly a case with personal configuration files in user's home directory on Linux. In addition, any backup files (file suffixes: `.old`, `~`, `.bak`, `.pacnew`...) are not included in the package according to your package manager and, therefore, they may not be uninstalled by simply removing a program. [Please see my script for tracking down those files](https://github.com/Fincer/linux_server_setup/blob/master/scripts/file-and-dirs-owner.sh)
**NOTE:** Although Linux distributions don't have any similar to Windows registry hell (unclean registry after software removal), keep in mind that any configuration files created _afterwards_ by a Linux program are not handled by Linux package managers. In other words: package managers can't track files created afterwards by your program. This is mostly a case with personal configuration files in user's home directory on Linux. In addition, any backup files (suffix: .old, ~, .bak, .pacnew...) are not included in the package according to your package manager and, therefore, they may not be uninstalled by simply removing a program. [Please see my script for tracking down those files](https://github.com/Fincer/linux_server_setup/blob/master/scripts/file-and-dirs-owner.sh)
#### Other Linux distributions
**Other Linux distributions:**
Main differences between various Linux distributions are:
**Main differences between various Linux distributions are:**
- version modeling: For example, Arch Linux follows [rolling release model](https://en.wikipedia.org/wiki/Rolling_release) whereas Ubuntu follows [time based release model](https://wiki.ubuntu.com/TimeBasedReleases)
@ -386,7 +390,7 @@ GPL license is targeted to distribute free sofware under several terms. The lice
| Skype | Ring-KDE, Pidgin Internet Messenger | Chat & video/audio calling program | Skype is available for Linux, too. However, newer version of the program is available only for Windows. Ring-KDE is a part of KDE project. It's a front-end to [GNU Ring](https://en.wikipedia.org/wiki/Ring_(software)) |
| Valve Steam | - | Game publishing platform | |
| Windows Control Panel | KDE System Settings (systemsettings5) | General settings of an operating system | KDE System Settings is a part of KDE project, and comes usually with KDE desktop environment. Windows Control panel is a part of Windows OS. |
| Windows File Manager | Dolphin, Nautilus, Nemo, Thunar | File manager | Dolphin is a part of KDE project. Nautilus is a part of GNOME project. Nemo is forked from Nautilus. Thunar is a part of XFCE project. |
| Windows File Manager | Dolphin, Nautilus, Nemo, Thunar | File manager | Dolphin is a part of KDE project. Nautilus is a part of GNOME project. Nemo is forked from Nautilus. Thunar is a part of Xfce project. |
| Windows Image Viewer | Gwenview | Photo previewer | Gwenview is a part of KDE project. Windows Image Viewer is a part of Windows OS. |
| Windows Task Manager | KSysGuard, LXTask | Process and system statistics manager | KSysGuard is a part of KDE project. LXTask is a part of LXDE project. Windows Task Manager is a part of Windows OS. |
| Windows Volume Control | Alsamixer, PulseAudio Volume Control | Audio device, level & channel control | Alsamixer is a part of ALSA. PulseAudio Volume Control is an interface to control Pulseaudio on Linux. Windows Volume Control is a part of Windows OS. |
@ -394,15 +398,15 @@ GPL license is targeted to distribute free sofware under several terms. The lice
**f)** Optional extra task: backup your files (you can use an external USB storage, for example)
--------------
**Answer:** Depending on the final goal/purpose, alternative methods can be used. Creating a backup of whole HDD/SSD's is possible with a single dd command (recommended parameter 'status=progress' with large partitions) and with a USB live stick so that this partition/HDD/SSD is not mounted. More sophisticated tools include [Clonezilla](https://en.wikipedia.org/wiki/Clonezilla), for example. It is recommended to backup a server with slightly different methods.
**Answer:** Depending on the final goal/purpose, alternative methods can be used. Creating a backup of whole HDD/SSD's is possible with a single `dd` command (hint: use recommended command parameter `status=progress` for large partitions) and with a USB live stick so that this partition/HDD/SSD is not mounted. More sophisticated tools include [Clonezilla](https://en.wikipedia.org/wiki/Clonezilla), for example. It is recommended to backup a server with slightly different methods.
If the purpose is to copy single files from a location to another location, use *cp* or *rsync* command.
If the purpose is to copy single files from a location to another location, use `cp` or `rsync` command. [Rsync example](https://www.ostechnix.com/backup-entire-linux-system-using-rsync/).
where -R stands for "recursive copy" and "-p" stands for "preserve file & folder permissions". Asterix symbol (*) stands for "include all files".
where `-R` stands for "recursive copy" and `-p` stands for "preserve file & folder permissions". Asterix symbol (*) stands for "include all files" (see [Bash regular expressions](http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_04_01.html) for more information).
**NOTE:** If you copy files between ext2/3/4 and NTFS file systems, keep in mind that any permissions stored in ext2/3/4 partition are not preserved in NTFS partition. NTFS is widely used on Microsoft Windows environments whereas ext2/3/4 are widely used on Unix-based (POSIX) environments.
In addition, you must consider any [symbolic links](https://en.wikipedia.org/wiki/Symbolic_link) included in copy process. Keep in mind to watch out user permissions as well (does the current user have permissions to copy selected files?).
**NOTE:** There is an experimental tool to convert your existing ext2/3/4 & FAT/NTFS file systems to another file system format. For more information, see [fstransform - fedoramagazine.com](https://fedoramagazine.org/transform-file-systems-in-linux/) (note that installation instructions using `dnf` command are Fedora specific only. You should use `apt-get` instead on Debian/Ubuntu/Mint...)
Pekka Helenius
5 years ago
GitHub