A collaborative 2461-70/2482-40 Fall 2017 Final Project
During Week 10 of CSCI 2461-70 and CSCI 2482-40, after significant discussion all students enrolled in these classes unanimiously decided to join efforts and chose as a Collaborative Class Final Project building their own Specialized Linux distribution based on Debian Linux and the Elive project. CSCI 2461-70 is focusing on educational components of Linux, and CSCI 2482-40 is focusing on Incident Handling and Disaster Recovery components.
This document serves as a Users Guide to the 2482-40 and 2461-70 classes and associated tools, techniques and processes.
In the African Bantus belong to Bantu group, 'Abanto' in my dilect laguage 'kisii' Abantos means "Belongs to Human Beings/man"
AbantOS Linux is based on and created in collaboration with Thanatermesis of the Elive Project.
The name AbantOS is partially an homage to Ubuntu Linux.
This document uses the Eisvogel.tex Template and Pandoc, using a similar method to OWASP's Top 10 method
$ pandoc AbantOS-Elive-UsersGuide-17319-835.md -o ./AbantOS-Elive-UsersGuide-17319-835.pdf --from markdown+multiline_tables --template eisvogel.tex --listings --tocThis work is licensed Attribution-ShareAlike 4.0 International (CC BY-SA 4.0).
All contributors hold their original Copyright 2017.
autoconf, automake, and autotools-dev - many newer programs use configure scripts and Makefile files preprocessed with the help of programs like these (see info autoconf, info automake). autotools-dev keeps up-to-date versions of certain auto files and has documentation about the best way to use those files
-
The key points to remember in considering Debian social dynamics as applied to becoming a package maintainer are these:
- Debian is a volunteer-powered project, and self-motivation and friendly cooperation are crucial.
- Debian development is consistently evolving, and maintainers must adapt along with it. This adaptation must be self-driven; you cannot rely on others to bring you along.
Though many if not all packages necessary for development should come installed with the base Debian installation, it's good to check they are present with aptitude show package or dpkg -s package. The most important package to make sure is installed is build-essential. It should pull in other packages that are necessary for the build environment if they are not already installed.
Other packages are some measure of helpful and/or necessary for building particular packages down the road. Some are particular compilers for specific languages (i.e. gfortran or gpc) or packages for scripting languages themselves (i.e. perl and python). Others make parts of the process easier (such as the debhelper/dh-make packages or the fakeroot tool) or allow checking for errors after the build (lintian). The full range of additional build packages listed should be installed and understood before proceeding.
This section of chapter 1 includes the debian-policy which is the explanations of the structures and contents of the Debian archive and several OS design issues. It also includes requirements that each package must satisfy to be included in the distribution.
Important documentations that needed to be read for the development are auto tutorial and gnu-standards. If any errors or bugs occur, the maint-guide package can be used to report using report bug.
There are a few documentations that will help solve any problems we encounter during installing packages or using any commands. Available sources to solve any issues are; websites such as lists.debian.org or wiki.debian.org/Teams.
If you already have a completed source package, issue the following commands in the directory where the foo.orig.tar.gz, foo.debian.tar.gz, and foo.dsc files exist to update the local pbuilder chroot system and to build binary packages in it: $ sudo pbuilder --update $ sudo pbuilder --build foo_version.dsc
1. Get a copy of the upstream software, usually in a compressed tar format.
* package-version.tar.gz
2. Add Debian-specific packaging medications to the upstream program under the Debian directory, and create a non-native source package.
* package_version.orig.tar.gz
* package_version-revision.debian.tar.gz
* package_version-revision.dsc
3. Build Debian binary packages, which are ordinary installable package files in .deb format. The character separating package and version change from hyphen to underscore. As the following command.
* package_version-revision_arch.deb
1. First, create the first version of a package, outside of Git. Once this is done, you can import the package using the import-dsc command.
$ gbp import-dsc /path/to/package_0.1-1.dsc2. This will give output of its progress and make a few commits as well as have some new files and directories.
$ ls
package/
package_0.1-1.orig.tar.gz3. git-buildpackage command
* Imported the package into the upstream branch
* This has then been tagged upstream/0.1, which represent package's number
* Imported debian/directory into master and upstream's files
* Tagged the last commit as debian/0.1-1 as it finished package.
When there is a new version upstream, you could use the following steps to update to the latest version of upstream version.
$ gbp import-orig -uscan
$ gbp import-orig /path/to/new-upstream.tar.gz -u 0.2
*if the upstream tarball already exist in the form of packagename_version.orig.tar.gz, then the -u option is not required.
The steps to follow after choosing a package to create and in order to check if the package is already in the distribution archive are; the aptitude command, the debian packages web page and the debian package tracker web page. Debian already has packages in the Debian archive which is much larger than that of contributors with upload rights. If you are able to adopt the package, get the sources something like apt-get source but if you are installing new packages in Debian follow the steps below:
1. First step is to confirm that the program works.
2. Second, Make sure no one is working on the package. If no one is working on it, file an ITP bug report to the wnpp pseudo-package using report bug. If someone else is already working on it, contact them if you feel you need to.
3. Third, the software must have a license.
4. Fourth, the program should not introduce security and maintenance concerns into the Debian system. The program should be well documented, should not run setuid root and should not be a daemon.
As a new maintainer, you are encouraged to create simple packages, intermediate complexity packages and high complexity packages. Packaging a high complexity packages requires more knowledge than it takes to build a simple or intermediate packages.
There are a few steps mentioned on this section to get the package and try it out.
1. First step is to find and download the original source code.
2. Second, if your package program comes in tar+gzip format with the extension .tar.gz, format with the extension .tar .bz2 or tar + xz format , it usually contains a directory called package-version with all the sources inside.
3. Third, if your program comes as some other sort of archive, you should unpack it with the appropriate tools and repack it.
The SFS is a simple file system format optimized for writing and for low overhead.. The advantages of this format are: • Event navigation is possible using simple content-independent file system like functions. • Very low overhead. No loss due to block size granularity • Entire valid file system can be created by appending content 1. Simple programs comes with a Makefile which can be compiled by invoking make. 2. Compile and run to make sure your program works so it won't break something else while it's installing or running. 3. You can run make clean to clean up the build directory. 4. You can use the make uninstall to remove all the installed files.
-Linux, the free and open-souPackage Managementrce operating system, has fewer desktop users than Windows and macOS. But it's also far more flexible. In fact, you can install many of its versions (Linux comes in several different flavors, called distributions or distros) on a USB stick. Once you've created your portable computer, simply plug it into a PC or Mac of your choice, boot it up from the drive, and you're up and running. Free software is often written in C or C++, and these often use portable build systems to make them portable across platforms. Autotools is one example of such a build system; it comprises Autoconf, Automake, Libtool, and Gettext. (Cmake is an alternative build system.)
With these build tools, they must be used to generate the Makefile and other required source files first. The program can then be built using make && make install.
The Autotools workflow generally proceeds as:
1. Upstream runs autoreconf -i -f in the source directory and distributes the generated files along with the source.
2. The user obtains the distributed source and runs ./configure && make in the source directory to compile the program in an executable source binary.
-Initially, the repository you create in Bitbucket is going to be empty without any code in it. That's okay because you will start adding some files to it soon. This Bitbucket repository will be the central repository for your files, which means that others can access that repository if you give them permission. After creating a repository, you'll copy a version to your local system—that way you can update it from one repo, then transfer those changes to the other
Two types of dpkg-scanpackages dpkg-scansource dpkg-scanpakages arguments | gzip-9c>Packages.gz apt-get update apt-get upgrade
- open command line
- enter following commands @repository :+1 :shipit
$ git init $ git add $ git commit -m "First commit"Package Management $ git remote add origin $ git remote -v $ git push origin master
$ dpkg-buildpackage -us -uc $ debian/rules clean $ debian/rules build $ fakeroot debian/rules binary
$ apt-get install build-essential dh-make devscripts fakeroot $ apt-get install patch diff patchutils $apt-get install linda
-[] efl-dbgPackage Management -[] efl-doc
#create a directory
$mkdir enlight
set -e
PREFIX="/usr/local"
PROJECTS="efl enlightenment"
SITE="https://git.enlightenment.org/core/" OPT="--prefix=$PREFIX"
PKG_CONFIG_PATH="$PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH" PATH="$PREFIX/bin:$PATH" LD_LIBRARY_PATH="$PREFIX/lib:$LD_LIBRARY_PATH" LOG="install.log" rm -f $LOG # Delete precedent log file touch $LOG # Create a log file date >> $LOG # Add current date
for PROJ in $PROJECTS; do # Cloning if [ ! -d $PROJ ]; then git clone $SITE$PROJ.git $PROJ fi # Go building and installing cd $PROJ make clean distclean || true ./autogen.sh $OPT make sudo make install cd .. sudo ldconfig echo "$PROJ is installed" >> $LOG done
#Optionnal Terminology git clone https://git.enlightenment.org/apps/terminology.git cd terminology ./autogen.sh $OPT make sudo make all install cd .. sudo ldconfig
apt install dbus-x11 xinit xorg
Ubuntu is a Linux distro that starts with the breadth of Debian and adds regular releases (every six months) commitment to security updated with nine months of support for every release.
Ubuntu builds on the foundations of Debian's architecture and infrastructure but there are important differences such as, Ubuntu has its own user interface, a separate developer community and different release process. Debian is the rock upon which Ubuntu is built. It is a volunteer project that has developed and maintained a GNV/Linux Operating System of the same name over a decade. Since its launch, the Debian project has grown to comprise more than 1,000 members with official developers status, alongside many more volunteers and contributors. Debian is a free operating system. An operating system is the set of basic programs and utilities that make your computer run. At the core of the operating system is a Kernel. The Kernel is the most fundamental program on the computer and does all the basic housekeeping and lets you start other programs. Debian system use Linux Kernel or the BSD Kernel. Today Debian encompasses over 20,000 packages of free open source applications and documentation.
About Ubuntu
Ubuntu is an Open-source project that develops and maintains a cross-platform, open-source operating system based on Debian. Upgrades are released every six months and support is granted by Canonical for up to five years. Canonical also provides commercial support for Ubuntu deployments across the desktop, the server and the cloud.
How does Debian and Ubuntu fit together? Packages are manually installed via the dpkg command. dpkg is the backend to commands like apt-get and aptitude, which in turn are the backend for GUI install apps like the Software Center and Synaptic.
Ubuntu is proud to be based on Debian. Ubuntu developers want to maintain a healthy and collaborative relationship with Debian developers. Ubuntu has brought new users and developers to the GNU/Linux community
How does Ubuntu differ from Debian?
Ubuntu has a narrow focus--community based while Debian is Universal.
Ubuntu has its own community government structure somehow inspired by Debian's but different. (MOTU) The masters of the universe were team formed to look after the creation of the universe component.
Debian for Ubuntu developers **** debhelper and dh-make - dh-make is necessary to create the skeleton of our example package, and it will use some of thedebhelper tools for creating packages. They are not essential for this purpose, but are highly recommended for new maintainers. It makes the whole process very much easier to start, and to control afterwards
Ubuntu benefits from a strong Debian and Debian benefits from a strong Ubuntu.
Every Debian developer is also an Ubuntu developer because one way to contribute is to contribute to Debian Ubuntu is Debian based.
Edubuntu
A complete Linux based operating System targeted for primary and secondary education. It is freely available with community based support. The Edubuntu community is built on the ideas enshrined in the Edubuntu manifesto: that software, especially for education should be available free of charge and that software tools should be usable by people in their local language and despite any disabilities. [14]
Kubuntu
An official derivative of Ubuntu Linux using ICDE instead of the GNOME or unity interfaces used by default in Ubuntu.
GNOME (GNU Network Object Model Environment, pronounced as NOHM) is a graphical user interface (GUI) and set of computer Desktop applications for users of the Linux computer operating system. Its intended to make a Linux operating system easy to use for non-programmers and generally corresponds to the windows desktop interface and its most common applications. (Wikipedia)
AbantOS uses the Enlightenment Window Manager
ELIVE BACKGROUND Elive, which is a Linux distro based on Debian GNU/Linux, was created in Belgium in the early 2005. Elive is known for it's Enlightenment desktop environment, and the heavy use of eye candy. Even though Elive has a very decorative looks, it is quite small and fast. It all started with the purpose of customizing a Knoppix (which is a bootable live system on CD/DVD or flash drive, consisting of a representative collection of GNU/Linux software, automatic hardware detection, and support for many graphics cards, sound cards, SCSI and USB devices and other peripherals). The initial intentions were to create the Knoppix which will be a Live CD running the Enlightenment and with the designs based in the Evil Entity distro this was called Tezcatlipotix. The end result after this research period turned out to be better than what was expected. So they decided to make from there on a public version of the new creation. Two months after the first public version with the name of Elive came out, and was already directly appearing in Slashdot. This was actually just the beginning. After the public version was created, Elive founder continued the development with more versions and features. A year later the Elive organisation started asking for donation in order to keep the project running. One the good things about Elive is that uses an Union FS, which allows users to install software packages using Synaptic and/or APT, while the user's computer is running from the Live CD and also allows the users to try it before installing on the computer which will give full access to all the features.
>>> helpDownloading Elive from EliveCD.org
- The latest release of Elive can be downloaded from www.elivecd.org. The latest Beta release is the recommended version to download.
- Navigate to the Beta downloads by clicking Download, then Beta.
- For writing Elive to a USB drive, click the button labeled Elive Beta - USB. This is an Elive image specifically for writing to USBs. A window will open asking if you want to open or save the .img file. Click Save File and your browser will download the file.
- When the download finishes, open the folder to which it was saved and take note of the file's location.
Release notes at EliveCD.org
The archive of release notes on the Beta releases of Elive can be found at http://www.elivecd.org/news/releases/beta/. Each entry contains many details on what features of Elive have been updated and improved in each release.
- The recommended USB drive for writing and using Elive is the SanDisk Extreme USB 3.0 32 GB flash drive.
- If you are using Windows, you can write the Elive image to the USB using an image writer application. Elive suggests UsbWriter; other options include the application from Etcher.io or Win32DiskImager.
- With any application, first plug your USB drive into an open USB port on your computer. Using the application, select the Elive image from the location you downloaded it to, then select the correct USB drive and write the image.
- The written image will overwrite any other data contained on the USB drive. In some cases, the USB drive may need to be reformatted first before being able to write a new USB image (for instance, if a previous USB image was written to the drive). You can reformat the drive by right-clicking the drive in the Computer window or using Windows Disk Management.
- Power on your computer with the USB with Elive written to it plugged in. When the initial boot screen of your computer appears, hold down the Boot Menu key to load the boot menu. On many computers this is the F12 key, or one of the other F row keys. A list of common boot menu keys for various manufacturers can be found at http://www.elivecd.org/ufaqs/how-to-tell-the-computer-to-boot-from-another-device/.
- When the boot menu key appears, highlight the USB drive option and press Enter.
- After Elive initiates, the first Elive menu asking the method of installation will appear. For running Elive from the USB, select Live sessions with Persistence. This method will allow you to run Elive direct from the USB without installing the system on your separate hardware, and Persistence will save your configurations of Elive from session to session.
First and foremost BIOS is pronounced by-oss and is sometimes referred to as the System BIOS, ROM BIOS, or PC BIOS The word BIOS stands for Basic Input Output System. It is a software that can be located on a memory chip on the motherboard. The BIOS gives the computer instructions to perform some functions like booting and keyboard control and also configure the hardware in a computer including the hard drive, floppy drive, USB, optical drive, CPU, memory to list a few, it also help in the proccess of trouble shouting. The BIOS is also responsible for the POST (POST stands for "Power On Self Test." It is a diagnostic program built into the computer's hardware to tests different hardware components before the computer boots up. The POST process is run on both Windows and Macintosh computers). reason why it the first software to run when a computer is started (BIOS). The BIOS firmware settings are always saved and recoverable even after power has been removed from the device. The BIOS is can be accessed and configured through the it's Setup Utility and is pre-installed before the computer is purchased. Unlike the operating system such as Windows, which needs to be downloaded or obtained on a disc, and needs to be installed by the user or the manufacturer.
Standing for Extensible Firmware Interface, EFI is a recent firmware developed by Intel and introduced with the release of IA-64. EFI's version has improved the fonctions previously available in the BIOS. The EFI specification was made into a general standard known as UEFI. The EFI System Partition (ESP) is the partition on a data storage device (usually a hard disk drive or solid-state drive) that is used by computers to the Unified Extensible Firmware Interface (UEFI). When a computer is booted (also meaning started), UEFI firmware loads files stored on the ESP to start the installation of the operating systems and other utilities. The ESP needs to be formatted with a file system whose specification is based on the FAT file system and maintained as part of the UEFI specification; so the file system specification can be independent from the original FAT specification. EFI can be used to eliminate the boot loader, that will allow the firmware to select the operating system and at the same time enables vendors to create drivers that cannot be reversed or engineered to contains a small shell. This process can be run at boot and allow a small and manageable working environment without compromising anything on the computer. It has been noticed nowadays that new computers use UEFI firmware instead of the traditional BIOS. Both are still low-level software that starts at the same time as the computer is started at the boot level, but UEFI is a more of a modern solution. It was devellopped in the intention to make the BIOS better. reason why it supports larger hard drives, make the boot proccess go faster, has more security features, and-conveniently-graphics and mouse cursors. There are newer PCs that has the chip with UEFI still refer to as the “BIOS” to avoid confusing people who are used to a traditional PC BIOS, but does not mean that the chip still has the BIOS running. Even if your PC uses the term “BIOS”, modern PCs baught nowadays almost al of them has certainly ship with UEFI firmware instead of the old BIOS.
-
Why the BIOS Is Outdated To be clear BIOS has not been labeled bad or wrong, all this new developemnt are only for improuvment. The BIOS has been around for quite a long time, and was not evolving much. Even MS-DOS PCs released in the 1980s still had a BIOS on the ship on the motherboard. But still modification have been made to improve the BIOS along all those years. Some extensions were developed, all in the name of improvment such as ACPI (the Advanced Configuration and Power Interface). This allows the BIOS to more easily configure devices and perform advanced power management functions, like sleep which is not off. But the BIOS hasn’t advanced and improved nearly as much as other PC technology has since the days of MS-DOS. Still The BIOS was experiencing some limitations. For example tt can only boot from drives of 2.1 TB or less, while 3 TB drives are common now, and a computer with a BIOS can’t boot from them. That limitation is due to the way the BIOS’s Master Boot Record system works. The BIOS must run in 16-bit processor mode, and only has 1 MB of space to execute in. It has trouble initializing multiple hardware devices at once, which leads to a slower boot process when initializing all the hardware interfaces and devices on a modern PC. The BIOS was basically crying for replacement or improvment if you want to call it for a very long time. Intel started working on the Extensible Firmware Interface (EFI) specification back in 1998. Apple chose EFI when it switched to the Intel architecture on its Macs in 2006, but other PC manufacturers didn’t follow. In 2007, Intel, AMD, Microsoft, and PC manufacturers agreed on a new Unified Extensible Firmware Interface (UEFI) specification. This is an industry-wide standard managed by the Unified Extended Firmware Interface Forum, and isn’t solely driven by Intel. UEFI support was introduced to Windows with Windows Vista Service Pack 1 and Windows 7. The vast majority of computers you can buy today now use UEFI rather than a traditional BIOS.
The Master Boot Record (MBR) is a set information located in the first sector of hard disks or diskette that identifies. It has the prepuse of detecting how and where an operating system is located so that it can be boot (loaded) into the computer's main storage or random access memory. The Master Boot Record is also refer to as the "partition sector" or the "master partition table" because it includes a table that locates each partition that the hard disk has been formatted into. The MBR also includes a program that reads the boot sector record of the partition that contains the operating system to be booted into RAM, that record contains a program that loads the rest of the operating system into RAM. The MBR, is the most important data structure on the disk and it is created when the disk is partitioned. it contains a low amount of executable code refer to as the master boot code, the disk signature, and the partition table for the disk. At the end of the MBR there is a 2-byte structure called a signature word or end of sector marker. This sector is always set to 0x55AA. A signature word also represent the end of an extended boot record (EBR) and the boot sector. A disk signature is known to be a unique number at offset 0x01B8, that set out the disk to the operating system. Windows 2000 for example uses the disk signature like an index to save and retrieve information about the disk in the registry.
- Master Boot Code The master boot code runs numerous features like, Scaning the partition table for the active partition; Finding the starting sector of the active partition, Loading a copy of the boot sector from the active partition into memory, Transfering control to the executable code in the boot sector. In case the master boot code is unable to complete any of these activities, the system will be displaying one an error messages like; Invalid partition table; or Error loading operating system; or even Missing operating system but there is to say There is no MBR on a floppy disk. The first sector on a floppy disk is the boot sector. Every hard disk contains an MBR, the master boot code is used only if the disk contains the active, primary partition.
- What is a GUID Partition Table disk? The GUID Partition Table disk architecture was introduced as part of the Extensible Firmware Interface initiative. GUID Partition Table is a new disk architecture that expands on the older Master Boot Record (MBR) partitioning scheme that has been common to Intel-based computers. A partition is a contiguous space of storage on a physical or logical disk that functions as though it were a physically separate disk. Partitions are visible to the system firmware and the installed operating systems. Access to a partition is controlled by the system firmware and the operating system that is currently active.
- Why do we need GUID Partition Table? GUID Partition Table disks can grow to a very large size. In July 2001, the Microsoft implementation supports a hard disk of up to 18 EB (512 KB LBAs). The number of partitions on a GUID Partition Table disk is not constrained by temporary schemes such as container partitions as defined by the MBR Extended Boot Record. The Microsoft implementation of GUID Partition Table is limited to 128 partitions. However, it is important to note that one partition is used for the EFI System Partition, one for the Microsoft Reserved and two more are used if you use dynamic disks. This leaves 124 partitions for data use. The GUID Partition Table disk partition format is well defined and fully self-identifying. Data that is critical to the operating system is located in partitions and not in partitioned or "hidden" sectors. GUID Partition Table does not allow for hidden sectors or partitions. GUID Partition Table disks use primary and backup partition tables for redundancy and CRC32 fields for improved partition data structure integrity. The GUID Partition Table partition format uses version number and size fields for future expansion.Each GUID Partition Table partition has a unique identification GUID and a partition content type, so no coordination is necessary to prevent partition identifier collision. Each GUID Partition Table partition has a 36-character Unicode name, which means that any software can present an easily readable name for the partition without any additional understanding of the partition.
BIOS stands for Basic Input Output System. BIOS is software stored on a small memory chip on the motherboard. It gives the computer a set of instructions on how to perform some of the basic functions such as booting and keyboard control as well as configure the hardware in a computer including the hard drive, floppy drive, USB, optical drive, CPU, memory to list a few.
- APPLE iOS MAC USER?
- If you are using an iOS - Apple Mac, and is having some issues geting your external flashdrive USB to work, try some of these things.
- If your external flash drive USB contains a usable operating system or an OS X installer, you can select it at boot time using OS X’S built-in feature called Startup Manager, which can be invoked via a simple keystroke.
- Power on your Mac by pressing the power button or restart it if it’s already on.
- Press and hold the Option (⌥) key immediately when you heari the startup chime. Release the key after Startup Manager appears. Startup Manager will scan and list connected drives and volumes that can be booted from.
- Select the volume you want to use by using the mouse or left and right arrow keys on the keyboard.
- Double-click or press the Return key to boot your Mac from the selected volume. You should now be able to boot from external an external flash drive USB
If you'd like to use system preference, with the computer on:
- Open the System Preferences application in the Dock.
- Now click the Startup Disk pane. You will be presented with various disk icons.
- Select the system you would like to use to start your computer up.
- Now click the Restart button to start up your Mac using the chosen volume.
Note: If there are several USB storage devices connected to your Mac, Startup Manager will only list the ones containing bootable volumes.
References "How to start up Mac from bootable media"
>>> apug
>>> sudo apt-get dist-upgrade
Elive utilizes the Enlightenment Window Manager. Enlightenment utilizes a set of core libraries called (EFL), created specifically for Enlightenment. EFL is being recognized for its forward thinking approaches as users are wanting more from their operating systems UI.
elive-tools are a set of handy and useful tools by Elive, for specialty use in the Elive project
- audio-configurator
- configure individual audio cards
- bkp (incremental backup of directories with patching and comparison features)
- elivepaste (pastebin)
- waitfor
- waits on the shell for a process that terminates and exits, its pretty useful for do things like: $ waitfor rebuild-packages && rebuild-iso
- user-manager
- email-sender (friendly and fast email sender for cli with html templates and attachments that uses mutt and gmail in the backend)
- git-watcher (and amazing and extremely handy git tool to watch and import commits with multi-user features)
- Evas
- Core scene graph and rendering
- Eina
- Data strucures and low level helpers
- Edje
- UI layout & animation data files for themes
- Eet
- Data (de)serialization and storage
- Ecore
- Core loops, system abstractions and x11
- Efreet
- Freedesktop.org standards handling
- Eldbus
- D-Bus glue and handling
- Embryo
- Tiny VM and compiler based on pawn
- Eeze
- Device enumeration and access library
- Emotion
- Multimedia wrapper, glue and abstraction
- Ethumb
- Thumbnailing handler
- Ephysics
- Physics (bullet) wrapper and Evas glue
- EIO
- Asynchronus I/O handling
- Evas Generic Loaders
- Extra image loaders for complex image types
- Emotion Generic Players
- Extra video decoders
- Elementary
- Widgets and high level abstractions
Elive currently has three theme options available by default.
- Default Theme
- Elive Light Theme
- A light theme
- Lucax Theme
- A dark theme
Left click on the desktop to bring up the menu, hover over Enlightenment to bring up enlightenment sub menu. Hover over about theme and click it, this will show you the current theme. Close the about theme and Left click on the desktop again to bring up the menu. Hover over Settings, scroll down and hover over Theme, you will see the three options available. Left click on the Theme you want and wait for it to change, this may take a minute or two depending on the theme. Open windows and applications will lock up during the transition, this is normal.
Left click on the desktop to bring up the menu. Hover over Settings and Left click it. A settings window will appear. Left click on Wallpaper, the wallpaper settings will appear. Choose one the the wallpapers and click apply, you can also set images as wallpapers from the file manager.
There is two methods for doing this that I know of, here are both.
Warning: animated wallpapers are not suggested since uses resources for rendering, small sized renderings and non-constant ones should not impact the user experience.
The first method is to download an HD Wallpaper in .gif format. You can download one here: Animated Wallpaper Sample gif. After you finish downloading your animated wallpaper you have to put it in the right directory open a Terminology terminal and navigate to /Downloads, or wherever you have your .gif wallpaper you downloaded. Now you have to move the wallpaper to the /usr/share/enlightenment/data/backgrounds/.
sudo mv "name of file without quotes.gif" /usr/share/enlightenment/data/backgrounds/Close the terminal and right click on the desktop to bring up the menu, click settings and then Wallpaper. The wallpaper settings will appear and it will open the directory where you just moved your wallpaper. Choose your animated wallpaper and click apply. Close the wallpaper settings.
NOTE: If you didn't see your wallpaper then your command may have been mistyped, don't forget to remove the quotes.
The second method is to download a HD wallpaper .gif and transfer it with the Thunar File Manager. Download your gif using the link above or any you choose in .gif format. Open the thunar file manager and from the home directory click downloads, or navigate to your .gif wallpaper. Open another thunar file manager window by clicking the icon in the dock again. Press (control) and (h) at the same time to show hidden files. Click .e and then e17, now click backgrounds. Drag and drop your animated wallpaper .gif from downloads to the backgrounds directory you just opened. After you transfer the wallpaper press (control) and (h) again to hide the config files. Close the file managers
Right click on the desktop to bring up the menu, click settings and then Wallpaper. The wallpaper settings will appear. In the top left click Personal, now you should see the wallpaper you transferred in the list below, click it. Now click apply and close the wallpaper settings.
Click on the desktop and then click (Settings). Under (Look) choose (Colors). The Colors window will open. From here you can customize window frame colors, window text colors, button text colors, Etc.
Changing Window Frame Colors:
Changing the Active Window Color.
- The (Border Frame Active) window is whatever window you are currently working in.
- If you have multiple windows open the 'active border frame' will change depending on which one the mouse is hovering over.
Click on the desktop and then click (Settings). Under (Look) choose (Colors). The Colors window will open. Click (Border Frame Active) Next click the (Custom colors) check box. Click the box under (Object:) A color selector window will open. Drag the (Alpha) knob all the way to the right to 255. Click through (R) (G) (B) (H) (S) (V). This is your starting Reds, Greens, Blues, Etc. Move the color sliders around and notice the changes to the large color palette on the left. When you see a color you like in the large color palette box, click it. The color you selected will display in the lower box. Click the (Select) button. The color selector window will close and the color you chose will now be displayed in the (Colors) window still open. Click the (Ok) button on the bottom. The color window will close and the window color will change. You should be able to see the change on the (Settings) panel still open.
Changing the (Border Frame) Color.
- The (Border Frame) windows are any open windows in the background that are not the active window
Click on the desktop and then click (Settings). Under (Look) choose (Colors). The Colors window will open. Click (Border Frame). Next click the (Custom colors) check box. Click the box under (Object:) A color selector window will open. Drag the (Alpha) knob all the way to the right to 255. Click through (R) (G) (B) (H) (S) (V). This is your starting Reds, Greens, Blues, Etc. Move the color sliders around and notice the changes to the large color palette on the left. When you see a color you like in the large color palette box, click it. The color you selected will display in the lower box. Click the (Select) button. The color selector window will close and the color you chose will now be displayed in the (Colors) window still open. Click the (Ok) button on the bottom. The color window will close and and the (Border Frame) will have changed. Open two windows and move the mouse over different windows to see the change in color.
Changing Window Text Colors:
Changing the (Border Title Active) Color
- The (Border Title Active) option changes the text color in the 'active' window.
Click on the desktop and then click (Settings). Under (Look) choose (Colors). The Colors window will open. Click (Border Title Active). Next click the (Custom colors) check box. Click the box under (Object:) A color selector window will open. Drag the (Alpha) knob all the way to the right to 255. Click through (R) (G) (B) (H) (S) (V). This is your starting Reds, Greens, Blues, Etc. Move the color sliders around and notice the changes to the large color palette on the left. When you see a color you like in the large color palette box, click it. Make sure it is a different color than the 'Border Frame Active' color. The color you selected will display in the lower box. Click the (Select) button. The color selector window will close and the color you chose will now be displayed in the (Colors) window still open. Click the (Ok) button on the bottom. The color window will close and and the (Border Active Title) will have changed.
Change Applications Fonts:
- Click on the (Desktop), and then click (Settings). The (Settings) Panel will open, click (Fonts). The (Font Settings) Panel will open. Under (Font Classes) choose (Applications) and check the (Enable Font Class) box. Choose a font under (Font). Choose a font style under (Style). Choose a font size under (Size). Click the (Ok) box at the bottom. The changes will take place immediately.
Example: Try DimWitGauche Applications Font.
- Click on the (Desktop), and then click (Settings). The (Settings) Panel will open, click (Fonts). The (Font Settings) Panel will open. You have two options on the top bar, (General Settings) & (Hinting/Fallbacks). Choose (General Settings), You will have four options under general settings. (Font Classes) (Font) (Style) & (Size). Under (Font Classes) click (Applications). Next, check the box (Enable Font Class). Under (Font) select (DimWitGauche). Under (Style) you have one option (Regular), leave it. Under Size click (Really Big). Click the (Ok) button at the bottom. Open the Thunar File Manager to see the changes.
Change Title Bar/Window Fonts:
- Click on the (Desktop), and then click (Settings). The (Settings) Panel will open, click (Fonts). The (Font Settings) Panel will open. Under (Font Classes) choose (Title Bar) and check the (Enable Font Class) box. Choose a font under (Font). Choose a font style under (Style). Choose a font size under (Size). Click the (Ok) box at the bottom. The changes will take place immediately.
Changing Window Borders:
- Click on the desktop and then (settings) this will open the settings panel. Click (Look) and then (Borders) This will open the Default Border Style window. Choose the style you like and click (OK). The changes will take place immediately. If you don't like your changes to the window border follow the steps above and choose (default).
The Ecomorph Configuration module is a powerful tool that allows you fully customize your desktop environment. You can customize open and close animations, minimization effects, application switchers, desktop cube, wobbly windows, At the time of writing I am using a Core i3 550 3.2GHz w/ 4 GB RAM.
Click on the Desktop and then click (Settings). The Settings Panel Will open, under the (Look) tab click (Ecomorph). The (Ecomorph Configuration) window will open. In the top left corner you will have two buttons, (Start Ecomp) & (Stop Ecomp). The Start Ecomp button starts Ecomorph, and the stop ecomp button stops ecomp. Below those buttons you will see five main categories.
General:
- If you click the (General) tab you will see options for the base plugins, viewport plugins, switcher plugins, and other plugins. Most of the boxes will be checked by default but If you check the box for (Wobbly), and then click the (OK) button at the bottom; you will have wobbly windows when moving them around the screen.
Window Opacity:
- If you click the (Window Opacity) tab, you will see three windows on the right. Options, Window Match, and Opacity for selected match. The (Window Match) section allows you to select specific windows to make adjustments to. Let's start with the dropdown menu, the menu that pops up when you click the desktop. In the Window Match section click on (type=Menu | PopupMenu | DropdownMenu). Next under the (Opacity for selected match) set (Opacity) to 50% by moving the slider to the middle. Click the (OK) button at the bottom of the Ecomorph configuration. The screen will flash a black screen and the changes are complete. Click the desktop ,and you will notice your dropdown menu is halfway invisible. You can repeat the process above for each window/application type under (Window Match). (class=Xchat) is the Xchat IRC application. (class=terminology) is the Terminology terminal.
Windows Move/Resize:
- This option allows you set the opacity for windows being moved around the screen. See through windows!
If you click the (Window Move/Resize) option you have a single slider button near the top. Set the slider to 36% by moving the button slider near the middle. Click the (OK) button near the bottom. Open the Ecomorph Configuration panel again, click and drag the ecomorph window around the desktop; the window should be nearly invisible when moving it around the screen.
Drop Shadow:
- The drop shadow effect is the glow around the dropdown menu and open windows. It is a really cool effect for any theme. You can customize the colors, radius, and opacity.
Click the (Windows Move/Resize) tab, two options will appear on the right. Normal Shadow, and Second Shadow. Radius is the thickness of the glow effect and (R, G, B) stands for Red, Green, Blue. By adjusting the RGB values you can get some really cool colors. Opacity is the visibility, more or less transparent.
Example: If you want a Blue glow effect.
- Click (Drop Shadow). Under (Normal Shadow) set the (Radius) to 38.5 by moving the slider until 38.5. Set (Opacity) to 1.20 by moving the slider. Set (R) to 0 by moving the slider all the way to the left.. Set (G) to 0 by moving the slider all the way to the left. Set (B) to 255 by moving the slider all the way to the right. Open a window or an application to see the changes. You should see a blue glow around windows.
The (Animations) tab has eight sub categories. This will cover the three main categories. Open animation, Close animation, and Minimize animation.
Open animation:
- The open animation is the animation that occurs when applications or windows are opened. You have so many awesome animations available for opening animations.
Random, Airplane, Beam Up, Burn, Curved Fold, Domino, Dream, Explode, Fade, Fold, Glide 1, Glide 2, Horiz Folds, Leaf Spread, Magik Lamp, Razr, Sidekick, Skewer, Vacuum, Wave, Zoom.
Let's set the Open animation for our dropdown menu to airplane. Click on the Desktop and then click (Settings). The Settings Panel Will open, under the (Look) tab click (Ecomorph). The (Ecomorph Configuration) window will open. Click (Open animation) on the left. You will have four options from here, Window match, Animation duration, Animation for selected match, and Animation random pool. In the top window (Window Match) click on (type=Menu | PopupMenu | DropdownMenu). Next, set the (Animation duration) by sliding the (Duration) bar to 245 ms. Next, under (Animation for selected match) click (Airplane). Next we have to clear the (Animation random pool). Un-check every box under (Animation random pool). Click the (OK) button near the bottom. Click on the desktop to bring up the dropdown menu, slowly move the mouse around the menu. You should see a folding airplane animation
Now that we have our open animation set for our dropdown menu, lets set the open animation for the Terminology terminal. Click on the Desktop and then click (Settings). The Settings Panel Will open, under the (Look) tab click (Ecomorph). The (Ecomorph Configuration) window will open. Click (Open animation) on the left. You will have four options from here, Window match, Animation duration, Animation for selected match, and Animation random pool. In the top window (Window Match) scroll down and click on (class=terminology). Next under the (Animations for selected match) click (Burn). Next click the (OK) button near the bottom. Click on the Terminology icon to bring up the terminal, notice the animation change.
Close animation:
- The same concept applies for close animations. You can choose the animation for when you close a window or application.
Click on the Desktop and then click (Settings). The Settings Panel Will open, under the (Look) tab click (Ecomorph). The (Ecomorph Configuration) window will open. Click (Close animation) on the left. You will have four options from here, Window match, Animation duration, Animation for selected match, and Animation random pool. In the top window (Window Match) click on (class=terminology). Set the (Animation duration) to 300 ms by sliding the slider button. Next under (Animation for selected match) click (Explode). Click on the Terminology icon and open a terminal, now close the terminal. It should explode when you click close.
If you like a specific animation and want to use the same animation for all applications and windows, you will have to repeat the process for each option under (Window Match).
Minimize animations:
- Click on the Desktop and then click (Settings). The Settings Panel Will open, under the (Look) tab click (Ecomorph). The (Ecomorph Configuration) window will open. Click (Minimize animation) on the left. You will have four options from here, Window match, Animation duration, Animation for selected match, and Animation random pool. Click the only optin available under (Window Match). Make sure (Animation random pool) is completely unchecked. It is ok if (None) is checked. Next choose an animation from the (Animation for selected match) category. After you choose an animation click the (OK) button. Next, open the thunar file manager and then minimize it. You should see the animation you chose.
Changing Ibar Applications:
- The IBar is located at the bottom of the screen and gives you quick access to applications that you use regularly. The default applications can be changed to fit your needs.
Click on the desktop and then (Settings) this will open the Settings Panel. At the top you will see the options /Look/Apps/Screen/Windows/etc. Click (Apps) and then (Ibar Applications). This will open an IBar Applications window. In the Ibar Applications window you will have two options at the top, (Applications) and (Order). The (Applications) tab will show you applications available to the IBar. Applications currently in the IBar will show a light next to them in the IBar Applicatons Window.
To add a new application Click on the desktop and then (Settings) this will open the Settings Panel. At the top you will see the options /Look/Apps/Screen/Windows/etc. Click (Apps) and then (Ibar Applications). This will open an IBar Applications window. Scroll down until you see the application you want to add. Click the (Application) and then near the bottom of the window click (Add). A light will show up next to the application in the window signifying it to be added. Now at the bottom of the window click (ok), the (Ibar Applications Window) will disappear and your Application will have been added to the IBar.
To remove applications Click on the desktop and then (Settings) this will open the Settings Panel. At the top you will see the options /Look/Apps/Screen/Windows/etc. Click (Apps) and then (Ibar Applications). This will open an IBar Applications window. Scroll down until you see the application you want to remove. Click the application you want to remove, at the bottom of the window click (Remove) and the (OK). the (Ibar Applications Window) will disappear and your Application will have been removed. Repeat the process until you remove all unwanted applications from the IBar.
Changing the order/placement of the applications in the IBar.
- To change the order of the applications Click on the desktop and then (Settings) this will open the Settings Panel. At the top you will see the options /Look/Apps/Screen/Windows/etc. Click (Apps) and then (Ibar Applications). This will open an IBar Applications window. You have two options at the top, (Applications) and (Order), Click (Order). This will open the application order window. Here you can change the application order by selecting an application and then choosing (Up) (Down) or (Remove). Moving applications up and down in this list will change where it sits on the IBar. Choosing (remove) will remove the highlighted application. Example: Click (Terminology) and then (Down) and then (OK). The Terminology application will move one spot right on the IBar.
right click on the desktop using the mouse the mouse and you will see all you want or looking for as you scroll the mouse.
-
Installing from the terminal(apt-get)
We can use the apt-get command to install packages from the terminal. apt-get will then fetch the most recent version regardless of the installed one.
Examples:
apt-get install firefox-esr: This command installs Firefox web browser
apt-get install git-annex : This command installs git annex. Git annex is used to manage files and anyone with access can work and share different files.
apt –get install trusty : This package allows users to administer system resources and manage user accounts
-
Installing with a software package manager
The apt-cache command is used for searching a software package cache. Examples: Sudo gem install lolcat : lolcat prints the content of a text file in rainbow colors in the terminal. ** References
Example: Install lolcat from terminal.
sudo gem install lolcat
Click on the desktop and hover over (settings), and then (All) and then (System), click (Synaptic Package Manager). A window will open asking for a password to elevate privileges, enter the root password and click (Authenticate). The Synaptic Package Manager will open. On the left you will have different categories you can choose from. You can browse the categories for available packages or, you can search for a specific package by selecting the (Search) option. Once you find a package click on the arrow next to the package name, select (mark for installation). A window will open showing a list of libraries to be installed, select (mark). Repeat for any packages you want to install. The packages have not been installed yet, to install your packages that you have marked for installation click the (Apply / green check mark) near the top of the window. A window will open showing the changes to be applied during installation, click (Apply). The download window will show the downloads progress. Some packages may require a reboot after installation.
Software Repository is a database for programming application installation and software upgrades. It is used mostly along with Linux based distributors. Because Linux doesn’t use or download applications like Window distributors; it uses Software Repository compiled applications that is for specific systems. Depending on whether the program is demanding, the repository language or manager will obey and program it to the users’ satisfaction. These sorts of systems are designed as malfunction free allowing the user’ to use the program freely without worrying about the system malfunctioning.
There are various reasons for building a repository yourself. You might just have a few packages with local modifications that you want to make available to apt, you may want to run a local mirror with those packages used by several machines to save bandwidth, or you build packages yourself and want to test them prior to publication.
A Debian repository contains several releases. Debian releases are named after characters from the "Toy Story" movies (wheezy, jessie, stretch, ...). The codenames have aliases, so called suites (stable, oldstable, testing, unstable). A release is divided in several components. In Debian these are named main, contrib, and non-free and indicate the licensing terms of the software they contain. A release also has packages for various architectures (amd64, i386, mips, powerpc, s390x, ...) as well as sources and architecture independent packages.
- Root Directory = dists
- Each release subdirectory contains a cryptographically signed Release file and a directory for each component.
- dpkg-scanpackages
$ dpkg-scansources dists/local/custom/source | gzip > dists/local/custom/source/Sources.gz- dpkg-scansources
$ dpkg-scanpackages dists/local/custom/binary-i586 | gzip > dists/local/custom/binary-i586/Packages.gzAn override file can be optionally specified. If no override file exists, dev/null must be provided as an explicit argument.
Working with repositories may mean one or two different things:
- You can use a repository with the apt family of programs (apt, apt-get, apt-cache, aptitude) to browse or install packages
echo "deb http://ftp.debian.org/debian stable main contrib non-free" >> /etc/apt/sources.list && apt-get update- You can set up a repository yourself and add, remove or replace packages in it.
wiki.debian.org/DebianRepository
wiki.debian.org/DebianRepository/Setup
- Boot Process and Troubleshooting.
- Basic System Configuration.
- System Logging.
- Disk Management and File System Creation.
- Linux Networking and Configuration.
- User and Group Management
- Process and Job Management.
- Creating and Editing Text Files.
- Installing and Updating Software Packages.
- Scheduling and Automating Future Tasks.
- Service/Server Configuration (DHCP, FTP, DNS, SSH and HTTP).
When you first boot an Elive Linux Operating System or any Linux OS it will go through the following processes to boot into the command line or desktop. When you press the power button on a machine that is running Elive, the first program that runs in the BIOS. BIOS stands for Basic Input Output System. We must clarify about the BIOS before we go any further. To be clear the BIOS is not part of the Linux kernel. The BIOS is separate of the operating system, it is not part of the OS. It can be found on computers running other operating systems such as Windows and others. The BIOS is a software that is built into a computer's ROM (Read Only Memory) at the time of manufacturing the motherboard. The BIOS goes through two main stages to boot a Linux kernel. It first does POST (Power On Self Test). In this first stage the BIOS checks to ensure that peripheral devices are intact and ready to operate the system after boot up. Peripheral devices are things like the keyboard, monitor, mouse, RAM, CPU and so on. Below is a screenshot of a BIOS.
Figure 1.1 BIOS
The next stage of the BIOS is that it looks for an MBR (Master Boot Record) on all the drives that are connected to the system. The BIOS has a boot menu which lists the boot order of all bootable devices that are available on a given system. Most BIOS by default are configured to check for the MBR on the first disk drive onboard. If there is no disk drive it'll check for a CD/DVD ROM or USB; which basically means it'll go through all the drives that are connected or onboard until it finds a drive with an MBR. Then it hands of the boot process to the drive that has the MBR. Another screenshot of the BIOS's boot menu.
Figure 1.2 BIOS boot menu
The MBR is the first sector of a disk drive; it holds a table of partitions on the disk drive. The MBR will look all the partitions on the drive to find one that has a boot loader. There are many common boot loaders but Elive linux uses GRUB two. Below is a screenshot of the GRUB two startup menu that is getting ready to boot up an Elive linux.
Figure 1.3 GRUB Boot Menu
Sometimes during the boot process you can into a some issues such as hearing a beep and the system getting stuck on first boot page. Usually you get an error message that gives you a hint as to what might be the problem or an error that tells you exactly what may the problem. If you hear a beep that is usually in indication that the BIOS is either not detecting a peripheral or it is not able to communicate with it. In this case, follow the error message and figure out what is wrong with that device. For instance, if you have an error that points to keyboard not detected make sure all the cabling to the PC is properly plugged in and that you don't have any lose connections. BIOS errors are not a kernel issue, that is just physical hardware issues.
The next type of error you can run into is GRUB not finding an OS, this is a common error, this just means that when the BIOS handed off the boot process to the MBR which found GRUB, that specific disk drive does not have an OS installed on it or the installation is corrupt, the easiest solution is to reinstall the OS. But below are a few commands you can run to detect if you have a corrupt installation or of something else is going on.
From the GRUB initial Boot Menu, use the up/down arrow keys to interrupt the boot process, then press "e" to enter into the GRUB configuration mode.
I have two linux OSs setup in dual boot but only one of them boots, the other one is not showing up in GRUB's menu. This is what to do when the system first boots. From the GRUB menu, enter "c" to go into grub command line configuration. Below is a screenshot of how that page looks like. Refer to the bottom of Figure 1.3 above to see the options.
Figure 1.4 Grub CLI
In this menu, some of the available commands are the "ls" command and its options as well. In the above case, it is a simple problem, the second OS which is Debian 7 doesn't have a boot option declared in the grub file. By adding that configuration in grub that will take care of the problem and next time you reboot, GRUB will list multiple OS to boot from; in our case ELive linux and Debian 7.
Once an Elive Linux is up and running for the first time one must perform a couple of house keeping. We will first configure the system with a hostname, and configure networking for network access so you can download the latest updates and security patches.
The command to change the system's hostname is hostname followed by whatever name you want to give it. You must be root to change the hostname or use the "sudo" option before the command. Running the hostname command by itself will return the current name of the system.
root ~ >>> hostname
Elive
To change it now do the following.
root ~ >>> hostname Debian
root ~ >>> hostname
Elive
Now, we changed the name but when we run the hostname command again it returns the old name. The reason is because this change is temporary on this shell. You must start another shell or login again to see the change. Besides that, most changes on the shell will not survive a system reboot, therefore, If you want to change the system's hostname permanently you must modify the /etc/hostname file.
[aali@elive:~]$ sudo nano /etc/hostname
Figure 2.1 /etc/hostname
As you can see below when I run the command to check my environment PATH I don't have /sbin as part of the path.
[aali@elive:~]$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
[aali@elive:~]$
So I can either temporarily add that directory to my PATH, or use the absolute path or use sudo. We'll try all three options below.
Now I'm going to add it to my environment PATH so I can use it without sudo or without the absolute path.
[aali@Elive:~]$
[aali@Elive:~]$ export PATH=$PATH:/sbin
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:12:d8:f3
inet addr:10.7.11.2 Bcast:10.7.11.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe12:d8f3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:223 errors:0 dropped:0 overruns:0 frame:0
TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:26175 (25.5 KiB) TX bytes:25322 (24.7 KiB)
eth1 Link encap:Ethernet HWaddr 08:00:27:01:b6:23
inet addr:10.0.2.6 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe01:b623/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1397 errors:0 dropped:0 overruns:0 frame:0
TX packets:820 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1617497 (1.5 MiB) TX bytes:93959 (91.7 KiB)
Now I'll try it with the absolute path.
[aali@elive:~]$ /sbin/ifconfig eth0
eth0 Link encap:Ethernet HWaddr 08:00:27:12:d8:f3
inet addr:10.7.11.2 Bcast:10.7.11.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe12:d8f3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2683 errors:0 dropped:0 overruns:0 frame:0
TX packets:2235 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:302465 (295.3 KiB) TX bytes:369886 (361.2 KiB)
[aali@elive:~]$
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:203 errors:0 dropped:0 overruns:0 frame:0
TX packets:203 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16729 (16.3 KiB) TX bytes:16729 (16.3 KiB)
[aali@elive:~]$
As we see the interface did get an IP address from a dhcp server because I didn't configure it with an IP address manually and as we'll see the IP address configuration file will also confirm that. Servers usually need a static IP, since their IP address and hostname is usually configured on a DNS Server, they can't have their IP addresses changing every so often. Even though a DHCP entry can be configured to be static, usually servers have their IP addresses configured manually therefore, that is what we'll do right now. In order to do this we have to modify the /etc/network/interfaces for Elive linux. Let's first cat the file and see what it's default configuration looks like.
[aali@elive:~]$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface eth0 inet dhcp
Now we're going to go in with nano or vi and modify that default configuration. All we need to do is change the dhcp option to static and define three things; an IP address, subnet mask and a default gateway.
Figure 2.2 Interface Configuration
Here is what it looks like after the changes. At this point we have configured a static IP on this machine, now all we need to do is save the file and reboot the machine.
Figure 2.3 Interface Configuration
alias apug='sudo apt-get update ; sudo apt-get upgrade'
[aali@elive:~]$
[aali@elive:~]$
Now we're going to run the apug alias to update our system to the latest available updates.
[aali@elive:~]$ apug
[sudo] password for aali:
Get:1 http://security.debian.org wheezy/updates Release.gpg [1,601 B]
Get:2 http://security.debian.org wheezy/updates Release [39.0 kB]
Hit http://repository.elivecd.org wheezy Release.gpg
Ign http://repository.elivecd.org wheezy/tests Translation-en
Fetched 798 kB in 13s (57.5 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
e17-conf e17-menus
The following packages will be upgraded:
deliver e17-stable e17-stable-data e17-stable-dbg e17-stable-dev e17-theme-elive-light
eliveremote evince evince-common firefox-esr icedove iceweasel libevdocument3-4
libevview3-3 libxcursor-dev libxcursor1 thunderbird
The following packages will be DOWNGRADED:
elive-tools
17 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 2 not upgraded.
Need to get 127 MB of archives.
After this operation, 1,145 kB of additional disk space will be used.
Do you want to continue [Y/n]?
Just answer "yes" when prompted and your system is updated to the latest Elive linux. Give it a quick reboot and you have an updated and patched system until next updates are released.
After building an Elive linux server updating and patching it, the next task you must do is configure the server to log errors and events before deployment. System administrators rely on system monitoring tools to keep track of errors and other events that take place on the servers. This is needed for many reasons but, there are two main reasons why this information must be logged. The main reason is troubleshooting purposes, you need to see what errors a system is reporting and when the errors started in order to effectively troubleshoot and fix the problem. The second main reason is for security purposes. If a system gets compromised system logs are very useful for getting more information on what happened and when. Because of the need for something that always monitors the linux machines, most linux distributions come with system logging tools that save errors and events to either remote servers or locally on the system. In this section we'll demonstrate how to use the most common syslog service that most distributions have available by default (rsyslog). Our Elive developers packaged this in the main system installation like many linux distributions, so we don't even have to install it. All we need to do is configure and start the service. The rsyslog service saves all system logs in the /var/log directory. It logs messages in specific directories within the /var/log* directory for log messages such as mail, security, boot and other general system logs.
In case you don't already have rsyslod installed here is the command to install it.
[aali@Debian:~]$ sudo apt-get install rsyslog
[sudo] password for aali:
Reading package lists... Done
Building dependency tree
Reading state information... Done
rsyslog is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
[aali@Debian:~]$
Now that we have installed the rsyslog service, this is how to start it.
[aali@Debian:~]$ sudo service rsyslog start
Starting enhanced syslogd: rsyslogd.
[aali@Debian:~]$
Here is an example of rsyslog output. I'm going to change my session to root and we're going to look at what rsyslog does.
[aali@Debian:/]$ su -
Password:
Type 'help' to know the ton of Elive features available...
root ~ >>>
root ~ >>>
root ~ >>> tail -4 /var/log/auth.log
Dec 12 09:25:48 Debian sudo: pam_unix(sudo:session): session closed for user root
Dec 12 09:27:15 Debian su[14601]: Successful su for root by aali
Dec 12 09:27:15 Debian su[14601]: + /dev/pts/2 aali:root
Dec 12 09:27:15 Debian su[14601]: pam_unix(su:session): session opened for user root by aali(uid=1000)
root ~ >>>
As you can see from the tail -4 /var/log/auth.log output which is getting the last 4 lines of that file, lines 2,3 and 4 shows me changing from my user account to the root account successfully. It logged all of that information. This was a specific area of rsyslog. We looked specifically at the log that is responbile for user account authentication /etc/log/auth.log. For more general log messages, use the /var/log/messages file which logs error messages, boot process errors and other general messages. Below is an output of the /var/log/messages file.
root ~ >>> tail /var/log/messages
Dec 11 19:18:13 localhost kernel: [11947.623793] efreet_icon_cac[31030]: segfault at bf7c8ffc ip b7769a68 sp bf7c9000 error 6 in libeina.so.1.13.3[b7755000+62000]
Dec 11 19:18:14 localhost kernel: [11948.872127] efreet_icon_cac[31045]: segfault at bf36effc ip b76ecaa8 sp bf36f000 error 6 in libeina.so.1.13.3[b76d8000+62000]
Dec 11 19:18:16 localhost kernel: [11951.017977] efreet_icon_cac[31070]: segfault at bf4a6fec ip b76b064b sp bf4a6ff0 error 6 in libeina.so.1.13.3[b769a000+62000]
Dec 11 19:18:18 localhost kernel: [11952.629468] efreet_icon_cac[31241]: segfault at bf5c2ffc ip b76e964b sp bf5c3000 error 6 in libeina.so.1.13.3[b76d3000+62000]
Dec 12 08:47:24 Debian kernel: imklog 5.8.11, log source = /proc/kmsg started.
Dec 12 08:47:24 Debian rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="9726" x-info="http://www.rsyslog.com"] start
Dec 12 09:16:53 Debian kernel: [55068.459661] e1000: eth0 NIC Link is Down
Dec 12 09:16:59 Debian kernel: [55074.473418] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Dec 12 09:19:59 Debian kernel: imklog 5.8.11, log source = /proc/kmsg started.
Dec 12 09:19:59 Debian rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="13768" x-info="http://www.rsyslog.com"] start
For more specific logs, please refer to the respective file for each specific log you need, such as mail, kernel, and cron information or errors etc... To customize the rsyslog service to your own needs please refer to the man pages for rsyslog.conf.
There are many tools available for disk management for most linux distributions. Elive comes prepackaged with fdisk, parted and gparted for GUI. The gparted tool is easy to use and self explanatory if you have a desktop GUI configuration. In this section will cover how to use both gparted since Elive is a GUI configuration of Debain and we'll also demonstrate fdisk for command line configuration for those that may prefer the CLI option. Were going to start with the command line in this section.
The fdisk tool commands are in the /sbin/ directory like the ifconfig command. So all the fdisk commands we run here must be run with sudo or the full path /sbin/fdisk.
[aali@Debian:/]$ sudo fdisk -l
Disk /dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders, total 62914560 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e629f
Device Boot Start End Blocks Id System
/dev/sda1 16384 3088383 1536000 82 Linux swap / Solaris
/dev/sda2 * 3088384 62914559 29913088 83 Linux
[aali@Debian:/]$
The fdisk -l option displays the currently configured disk drives in the system. I have added another partition but it is not configured yet with a file system so fdisk doesn't display it until it is configured with a file system and formatted. Below is the ls -l /dev/sd* command that shows us indeed we have another unformatted and unpartitioned disk drive in this sytem.
root ~ >>> ls -l /dev/sd*
brw-rw---T 1 root disk 8, 0 Dec 11 11:12 /dev/sda
brw-rw---T 1 root disk 8, 1 Dec 11 11:12 /dev/sda1
brw-rw---T 1 root disk 8, 2 Dec 11 11:12 /dev/sda2
brw-rw---T 1 root disk 8, 16 Dec 11 11:12 /dev/sdb
Since most commands I'm running in this section require sudo, I'll just switch to the root account and work from that account instead of having to use sudo over and over again. With that said, now I'm going to configured our new partition with fdisk. Go in with fdisk /dev/sdb which sdb is the second drive in this machines. Once we're in fdisk configuration mode, we have a lot of options, we can run the m option to have all the available commands/options listed for us.
[aali@Debian:/]$ sudo fdisk /dev/sdb
[sudo] password for aali:
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0xeeb6ce10.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help):
Command (m for help): m
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
The p option prints the current partition table. We don't have any on our current partition so when we run the p action below is what we get.
root ~ >>>
Command (m for help): p
Disk /dev/sdb: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xccd1e794
Device Boot Start End Blocks Id System
Command (m for help):
Command (m for help): p
Disk /dev/sdb: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xccd1e794
Device Boot Start End Blocks Id System
Now we're going to use the n action to format and create partitions within this disk drive.
Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p): prim ^H^H
Partition number (1-4, default 1):
Using default value 1
First sector (63-41943039, default 63):
Using default value 63
Last sector, +sectors or +size{K,M,G} (63-41943039, default 41943039):
Using default value 41943039
Command (m for help):
So we created a new primary partition in our second disk drive. Running the p action again will confirm that.
Command (m for help): p
Disk /dev/sdb: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xccd1e794
Device Boot Start End Blocks Id System
/dev/sdb1 63 41943039 20971488+ 83 Linux
Command (m for help):
Now we're going to save out configuration changes by using the w action, without using the w action, the changes we just made will not get written on the disk drive.
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Now the next step is to configure this disk with a file system. We'll use the linux ext4 file system, because I want to install another linux distribution on this disk drive and setup a dual boot. We'll use the mkfs command to make a file system on this drive.
root ~ >>> mkfs -t ext4 /dev/sdb1 1
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1310720 inodes, 5242872 blocks
262143 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
160 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
So our new disk drive is now formatted with a primary partion and a ext4 file system. We're going to mount it to see if our changes worked. I will create a directory called OpenSuse in the /mnt/ directory and mount our new partion on there.
root ~ >>> mkdir /mnt/OpenSuse
root ~ >>> mount /dev/sdb1 /mnt/OpenSuse
root ~ >>> df -H
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 29912168 7864028 22048140 27% /
udev 10240 0 10240 0% /dev
tmpfs 414900 820 414080 1% /run
/dev/disk/by-uuid/43cbad91-9996-48b1-9c5b-7429a2513b4b 29912168 7864028 22048140 27% /
tmpfs 5120 0 5120 0% /run/lock
tmpfs 1136980 9724 1127256 1% /run/shm
/dev/sdb1 20511324 44992 19401376 1% /mnt/OpenSuse
root ~ >>>
So as we can see from the commands above, our file was successfully mounted to the new /mnt/OpenSuse directory. We also run the df -h command to see the side and available space. The mount point we have is only good while the system is up and running, it doesn't survive a reboot of the system. If we want a partition to survive a reboot, we add the mount point configuraton to the /etc/fstab and that is what we'll do next.
root ~ >>> nano /etc/fstab
GNU nano 2.2.6 File: /etc/fstab
# Generated by the Elive installer
UUID=43cbad91-9996-48b1-9c5b-7429a2513b4b / reiserfs defaults,commit=300,relatime,notail 0 1
UUID=eeb92a85-e4da-4f9c-8fae-52b0c77c851f none swap sw 0 0
UUID=e70e3a87-88d4-4dea-af37-e140bd8db0d9 /mnt/OpenSuse ext4 defaults=rw,dev,exec,suid 0 1
Now that we have the disk added to the /etc/fstab, I rebooted the system to test it and it is still mounted after the reboot.
An Elive linux machine must get internet access in order to get the latest bug fixes, security patches and upgrades. In this section we'll cover how to configure your system to get on the network and how to troubleshoot any network issues. We have already discussed how to setup a network interface for DHCP or how to manually configure it statically. Here we'll start with bringing up and interface and shutting it down.
Usually interfaces comeup by default when a system is first booted up. But, we will start off with bringing up the interface or shutting it down manually.
We start of with only one physical interface (eth1) and the loopback interface.
[aali@Elive:~]$ /sbin/ifconfig
eth1 Link encap:Ethernet HWaddr 08:00:27:01:b6:23
inet addr:10.0.2.6 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe01:b623/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:212 errors:0 dropped:0 overruns:0 frame:0
TX packets:296 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25131 (24.5 KiB) TX bytes:38125 (37.2 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:101 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8508 (8.3 KiB) TX bytes:8508 (8.3 KiB)
[aali@Elive:~]$
[aali@Elive:~]$ clear
[aali@Elive:~]$
Now we're going to bring up the eth0 with the ifup command.
[aali@Elive:~]$ sudo ifup eth0
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/08:00:27:12:d8:f3
Sending on LPF/eth0/08:00:27:12:d8:f3
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPOFFER from 10.7.11.254
DHCPACK from 10.7.11.254
Reloading /etc/samba/smb.conf: smbd only.
bound to 10.7.11.2 -- renewal in 1572 seconds.
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ sudo ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:12:d8:f3
inet addr:10.7.11.2 Bcast:10.7.11.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe12:d8f3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:238 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:39320 (38.3 KiB) TX bytes:4213 (4.1 KiB)
eth1 Link encap:Ethernet HWaddr 08:00:27:01:b6:23
inet addr:10.0.2.6 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe01:b623/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:547 errors:0 dropped:0 overruns:0 frame:0
TX packets:569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:55408 (54.1 KiB) TX bytes:75352 (73.5 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:115 errors:0 dropped:0 overruns:0 frame:0
TX packets:115 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9980 (9.7 KiB) TX bytes:9980 (9.7 KiB)
[aali@Elive:~]$
[aali@Elive:~]$
As you can see above, we've got three interfaces up and running. The loopback which is virtual interface, eth0 which we just brought up and interface eth1. Now we're going to take eth0 back down.
[aali@Elive:~]$ sudo ifdown eth0
[sudo] password for aali:
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/08:00:27:12:d8:f3
Sending on LPF/eth0/08:00:27:12:d8:f3
Sending on Socket/fallback
DHCPRELEASE on eth0 to 10.7.11.254 port 67
Reloading /etc/samba/smb.conf: smbd only.
[aali@Elive:~]$
[aali@Elive:~]$ sudo ifconfig
eth1 Link encap:Ethernet HWaddr 08:00:27:01:b6:23
inet addr:10.0.2.6 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe01:b623/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:641 errors:0 dropped:0 overruns:0 frame:0
TX packets:658 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:63624 (62.1 KiB) TX bytes:93540 (91.3 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:129 errors:0 dropped:0 overruns:0 frame:0
TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11449 (11.1 KiB) TX bytes:11449 (11.1 KiB)
[aali@Elive:~]$
Now we're back to the first two interfaces that were up. It is as simple as that to bring up and down interfaces in Elive linux.
In this section we'll test a remote Elive system to see if it is up or down by using ping and traceroute.
Note: There are no firewalls in this network or any ACLs (Access Control Lists) blocking anything. In a typical network infrastructure, routers, switches or firewall ACLs could typically drop ping or traceroute packets.
C:\Users\IEUser>ping 10.7.11.2
Pinging 10.7.11.2 with 32 bytes of data:
Reply from 10.7.11.171: Destination host unreachable.
Reply from 10.7.11.171: Destination host unreachable.
Reply from 10.7.11.171: Destination host unreachable.
Reply from 10.7.11.171: Destination host unreachable.
Ping statistics for 10.7.11.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
C:\Users\IEUser>
C:\Users\IEUser>
Since we can't ping the remote Elive host and we know there aren't any security devices filtering our ICMP packets. We'll do a traceroute to see where the packets might be dropping.
C:\Users\IEUser>tracert 10.7.11.2
Tracing route to 10.7.11.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.2.1
2 gw.testlab.home [10.7.11.171] reports: Destination host unreachable.
Trace complete.
C:\Users\IEUser>
Traceroute shows that another device, likely the gateway of the Elive host is dropping the packets. This could mean that the Elive host is down or its interface that we're trying to hit is down. In this scenario the Elive host is up, but I intentionally shutdown the interface for this demo. So our traceroute is stopping at the ELive's network gateway. I'm going to bring back up the interface and we'll experiment the behavour and compare it with when it's down.
C:\Users\IEUser>ping 10.7.11.2
Pinging 10.7.11.2 with 32 bytes of data:
Reply from 10.7.11.2: bytes=32 time<1ms TTL=63
Reply from 10.7.11.2: bytes=32 time=1ms TTL=63
Reply from 10.7.11.2: bytes=32 time=1ms TTL=63
Reply from 10.7.11.2: bytes=32 time=1ms TTL=63
Ping statistics for 10.7.11.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\Users\IEUser>
C:\Users\IEUser>tracert 10.7.11.2
Tracing route to elive.testlab.home [10.7.11.2]
over a maximum of 30 hops:
1 <1 ms <1 ms 2 ms 10.0.2.1
2 1 ms 1 ms 1 ms elive.testlab.home [10.7.11.2]
Trace complete.
C:\Users\IEUser>
The result is almost the same except we're getting ping replies which indicates that the remote Elive host we're pinging is up. In this case we didn't even need to do a traceroute but we and the traceroute completes until it gets to the elive host. We can configure an interface IP statically from the command line as well but this configuration will not survive a reboot. Below is the syntax.
sudo ifconfig eth0 10.7.11.2 netmask 255.255.255.0 up
We can also configure a gateway for this as follows.
sudo route add default gw 10.7.11.171
Again, most CLI configurations don't survive a reboot. If you want the configurations to be persistent, you must do it in their respective files in the /etc directory.
We can check to see our routing table with the following command.
[aali@Elive:~]$ sudo route
[sudo] password for aali:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.0.2.1 0.0.0.0 UG 0 0 0 eth1
10.0.2.0 * 255.255.255.0 U 0 0 0 eth1
10.7.11.0 * 255.255.255.0 U 0 0 0 eth0
[aali@Elive:~]$
We can check to see what ports are open on the system with the netstat command.
[aali@Elive:~]$ netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 64 10.0.2.6:ssh 10.0.2.7:50219 ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags Type State I-Node Path
unix 22 [ ] DGRAM 11579 /dev/log
unix 2 [ ] DGRAM 11581 /var/spool/postfix/dev/log
unix 3 [ ] STREAM CONNECTED 14528 /var/run/dbus/system_bus_socket
unix 3 [ ] STREAM CONNECTED 16569 @/tmp/dbus-aD6ZVUtxkT
unix 3 [ ] STREAM CONNECTED 15670 @/tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 14540 /var/run/dbus/system_bus_socket
unix 3 [ ] STREAM CONNECTED 523650
unix 3 [ ] STREAM CONNECTED 13326 /var/run/acpid.socket
unix 3 [ ] STREAM CONNECTED 16547 @/tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 12127
unix 2 [ ] DGRAM 15452
unix 3 [ ] STREAM CONNECTED 16463
It is very simple to add users in Elive Linux, there are a couple of commands available to do that. Since Elive is Debian based the favored command for Debian based distrubtions is the adduser command. We also have the useradd command which is popular on Fedora/Redhat based flavors. Both commands are available on Elive but we'll sticket with the adduser command. The way the adduser command works is that it is a shell script that calls the useradd command in the background and runs it in the background. Where as when using the useradd you have to tell it specifically what you need with the command options.
root ~ >>> adduser jdoe
Adding user `jdoe' ...
Adding new group `jdoe' (1004) ...
Adding new user `jdoe' (1004) with group `jdoe' ...
Creating home directory `/home/jdoe' ...
Copying files from `/etc/skel' ...
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
Changing the user information for jdoe
Enter the new value, or press ENTER for the default
Full Name []: John Doe
Room Number []: 3270
Work Phone []: 651-200-2000
Home Phone []:
Other []:
Is the information correct? [Y/n] y
You have new mail.
root ~ >>>
By using the adduser plus the username you want to use, the system prompts you for whatever options you want to give that username. Now it created a user account, a home directory, it assigned the user a shell and a password all with one command. If we were to use the useradd command it would do the same except we would have to use options and specify exactly what we need it, in way it is more flexible but at the sametime it could be more typing.
As we can see below, jdoe now has a home directory with his username, most users are given a home directory based on their username by default.
root ~ >>> ls -l /home 1
total 9
drwxr-xr-x 53 aali aali 2800 Dec 13 07:33 aali
drwxr-xr-x 27 asmith asmith 1560 Dec 11 16:44 asmith
drwxr-xr-x 27 jdoe jdoe 1528 Dec 13 08:02 jdoe
drwxr-xr-x 27 momo momo 1528 Dec 11 16:41 momo
drwxr-xr-x 27 sfarsi sfarsi 1584 Dec 3 12:16 sfarsi
root ~ >>>
By default users are assigned the bash shell, and we can confirm that by checking the /etc/passwd file.
[aali@Elive:~]$ cat /etc/passwd | grep jdoe
jdoe:x:1004:1004:John Doe,3270,651-200-2000,:/home/jdoe:/bin/bash
[aali@Elive:~]$
[aali@Elive:~]$
We will now create a group and add jdoe to that group. This is again straight foward. We will use the groupadd command to do this.
[aali@Elive:~]$
[aali@Elive:~]$ cat /etc/group | grep AbantOS
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ sudo groupadd AbantOS
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ cat /etc/group | grep AbantOS
AbantOS:x:1006:
[aali@Elive:~]$
So we checked the group name to see if it's already in use, it wasn't then we created the group called "AbantOS". Now we're going to add jdoe to that group.
By running the id plus the username we'll verify to see which group jdoe belongs to then we'll add him to the AbantOS group.
[aali@Elive:~]$ id jdoe
uid=1004(jdoe) gid=1004(jdoe) groups=1004(jdoe)
[aali@Elive:~]$
It shows jdoe is currently part of his main group (1004). Now we'll add him to the AbantOS group.
[aali@Elive:~]$ sudo usermod -aG AbantOS jdoe
[sudo] password for aali:
[aali@Elive:~]$
[aali@Elive:~]$ id jdoe
uid=1004(jdoe) gid=1004(jdoe) groups=1004(jdoe),1006(AbantOS)
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ cat /etc/group | grep jdoe
jdoe:x:1004:
AbantOS:x:1006:jdoe
[aali@Elive:~]$
We added jdoe to the AbantOS group by using the usermod command. Then we varified our work by running the id command again and we checked the group file configuration (/etc/group) to make sure he was indeed added.
To delete a user account is very simple, all we need to do is use the userdel command with the -r option. If we don't use the -r option the user's directory won't get deleted. So we have to make sure and add the -r option as follows.
[aali@Elive:~]$ sudo userdel asmith
[sudo] password for aali:
[aali@Elive:~]$ ls -l /home
total 9
drwxr-xr-x 53 aali aali 2800 Dec 13 07:33 aali
drwxr-xr-x 27 1003 1003 1560 Dec 11 16:44 asmith
drwxr-xr-x 27 jdoe jdoe 1528 Dec 13 08:02 jdoe
drwxr-xr-x 27 momo momo 1528 Dec 11 16:41 momo
drwxr-xr-x 27 sfarsi sfarsi 1584 Dec 3 12:16 sfarsi
[aali@Elive:~]$
[aali@Elive:~]$ sudo userdel jdoe
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ ls -l /home
total 9
drwxr-xr-x 53 aali aali 2800 Dec 13 07:33 aali
drwxr-xr-x 27 1003 1003 1560 Dec 11 16:44 asmith
drwxr-xr-x 27 1004 1004 1528 Dec 13 08:02 jdoe
drwxr-xr-x 27 momo momo 1528 Dec 11 16:41 momo
drwxr-xr-x 27 sfarsi sfarsi 1584 Dec 3 12:16 sfarsi
[aali@Elive:~]$
[aali@Elive:~]$ sudo userdel -r sfarsi
userdel: sfarsi mail spool (/var/mail/sfarsi) not found
[aali@Elive:~]$
[aali@Elive:~]$ ls -l /home
total 7
drwxr-xr-x 53 aali aali 2800 Dec 13 07:33 aali
drwxr-xr-x 27 1003 1003 1560 Dec 11 16:44 asmith
drwxr-xr-x 27 1004 1004 1528 Dec 13 08:02 jdoe
drwxr-xr-x 27 momo momo 1528 Dec 11 16:41 momo
[aali@Elive:~]$
As we see above, I deleted two user accounts (asmith and jdoe) but their home directories didn't get deleted. Then I deleted the sfarsi account with the -r option and the home directory got deleted as well.
Now we're going to delete a group to demo how that works too.
[aali@Elive:~]$ cat /etc/group | grep LinuxThree
LinuxThree:x:1005:
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ man groupadd
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ sudo groupdel LinuxThree
[sudo] password for aali:
[aali@Elive:~]$
[aali@Elive:~]$ cat /etc/group | grep LinuxThree
[aali@Elive:~]$
[aali@Elive:~]$
So above we demonstarted how to deleted the a group with the groupdel command and then verify by checking the group configuration file in /etc/group.
User passwords are held in the /etc/shadow file which is encrypted. If using the useradd command. One can use the passwd command to have an encrypted password created for the user and saved in /etc/shadow file.
To modify existing user's account expiration dates, password renewal and account closure date you can use the chage command.
Below we can see all the available parameters with that command.
[aali@Elive:~]$ sudo chage -l momo
[sudo] password for aali:
Last password change : Dec 12, 2017
Password expires : never
Password inactive : never
Account expires : never
Minimum number of days between password change : 0
Maximum number of days between password change : 99999
Number of days of warning before password expires : 7
[aali@Elive:~]$
For instance, if we want to change the default setting for account expires "never" to a specific date, we can run the command as follows.
[aali@Elive:~]$ sudo chage -E 03/2/2018 momo
[sudo] password for aali:
Sorry, try again.
[sudo] password for aali:
[aali@Elive:~]$
[aali@Elive:~]$ sudo chage -l momo
Last password change : Dec 12, 2017
Password expires : never
Password inactive : never
Account expires : Mar 02, 2018
Minimum number of days between password change : 0
Maximum number of days between password change : 99999
Number of days of warning before password expires : 7
[aali@Elive:~]$
There, we changed the user momo's account expiration date from never to 3/2/2018.
There are several ways to manage processes in Elive Linux. We'll concentrate on a couple of commands for this section. We can run the top command or ps command to see running processes.
[aali@Elive:~]$ top
top - 09:09:45 up 1:40, 1 user, load average: 0.09, 0.23, 0.30
Tasks: 146 total, 2 running, 144 sleeping, 0 stopped, 0 zombie
%Cpu(s): 4.4 us, 2.0 sy, 1.2 ni, 92.0 id, 0.5 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 4148964 total, 873744 used, 3275220 free, 42272 buffers
KiB Swap: 1535996 total, 0 used, 1535996 free, 538212 cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3571 root 20 0 98040 43m 23m R 6.0 1.1 6:44.12 Xorg
4921 aali 23 3 159m 47m 21m S 6.0 1.2 5:13.68 terminology
4675 aali 20 0 234m 150m 51m S 4.6 3.7 4:47.48 enlightenment
7 root 20 0 0 0 0 S 0.3 0.0 0:49.49 rcu_sched
13 root 20 0 0 0 0 S 0.3 0.0 0:08.12 ksoftirqd/1
6098 aali 23 3 9912 3704 3044 S 0.3 0.1 0:00.63 sshd
19284 aali 23 3 5088 2556 2152 R 0.3 0.1 0:00.06 top
1 root 20 0 2308 1520 1412 S 0.0 0.0 0:01.35 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:08.31 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
Next we see the process running with the ps -aux command.
[aali@Elive:~]$ ps -aux
warning: bad ps syntax, perhaps a bogus '-'?
See http://gitorious.org/procps/procps/blobs/master/Documentation/FAQ
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 2308 1520 ? Ss 07:29 0:01 init [2]
root 2 0.0 0.0 0 0 ? S 07:29 0:00 [kthreadd]
root 3 0.1 0.0 0 0 ? S 07:29 0:08 [ksoftirqd/0]
root 5 0.0 0.0 0 0 ? S< 07:29 0:00 [kworker/0:0H]
root 7 0.8 0.0 0 0 ? S 07:29 0:50 [rcu_sched]
root 202 0.0 0.0 0 0 ? S< 07:29 0:00 [scsi_tmf_2]
root 219 0.0 0.0 0 0 ? S< 07:29 0:00 [kworker/0:1H]
root 222 0.0 0.0 0 0 ? S< 07:29 0:00 [kworker/1:1H]
root 254 0.0 0.0 0 0 ? S< 07:29 0:00 [md]
root 269 0.0 0.0 0 0 ? S< 07:29 0:00 [bioset]
root 276 0.0 0.0 0 0 ? S< 07:29 0:00 [reiserfs/sda2]
root 431 0.0 0.0 3100 2580 ? Ss 07:29 0:00 udevd --daemon
root 581 0.0 0.0 3096 2352 ? S 07:29 0:00 udevd --daemon
root 588 0.0 0.0 0 0 ? S< 07:29 0:00 [iprt]
root 599 0.0 0.0 0 0 ? S< 07:29 0:00 [kpsmoused]
root 2043 0.0 0.0 2416 1948 ? Ss 07:29 0:00 /sbin/rpcbind -w
statd 2077 0.0 0.0 2672 2356 ? Ss 07:29 0:00 /sbin/rpc.statd
root 2082 0.0 0.0 0 0 ? S< 07:29 0:00 [rpciod]
root 2084 0.0 0.0 0 0 ? S< 07:29 0:00 [nfsiod]
root 2092 0.0 0.0 2604 184 ? Ss 07:29 0:00 /usr/sbin/rpc.idmapd
root 2561 0.0 0.0 28016 2588 ? Sl 07:29 0:00 /usr/sbin/rsyslogd -c5
root 2688 0.0 0.0 1728 56 ? Ss 07:29 0:00 /usr/sbin/acpi_fakekeyd
root 2930 0.0 0.0 2036 1648 ? Ss 07:32 0:00 /usr/sbin/acpid
root 3156 0.0 0.0 3520 1788 ? Ss 07:32 0:00 /usr/sbin/irqbalance
root 3229 0.0 0.1 5964 4356 ? Ss 07:32 0:00 /usr/sbin/apache2 -k start
www-data 3232 0.0 0.0 5752 3392 ? S 07:32 0:00 /usr/sbin/apache2 -k start
www-data 3235 0.0 0.0 227372 3984 ? Sl 07:32 0:00 /usr/sbin/apache2 -k start
www-data 3236 0.0 0.0 227380 3984 ? Sl 07:32 0:00 /usr/sbin/apache2 -k start
root 3374 0.0 0.0 4508 2496 ? Ss 07:32 0:00 /usr/sbin/bluetoothd
root 3394 0.0 0.1 32664 5596 ? Sl 07:32 0:00 /usr/sbin/lightdm
root 3418 0.0 0.2 27924 8492 ? Ssl 07:32 0:00 /usr/sbin/NetworkManager
root 3472 0.0 0.0 3096 2288 ? S 07:32 0:00 udevd --daemon
root 3484 0.0 0.0 0 0 ? S< 07:32 0:00 [krfcommd]
root 3569 0.0 0.0 2080 1716 ? Ss 07:32 0:00 /usr/sbin/inetd
root 3644 0.0 0.1 7032 4728 ? S 07:32 0:00 /usr/sbin/modem-manager
root 3749 0.0 0.1 15740 5100 ? Sl 07:32 0:00 /usr/lib/urfkill/urfkilld
root 3857 0.0 0.0 0 0 ? S< 07:32 0:00 [iprt]
root 3875 0.0 0.0 23608 2552 ? Sl 07:32 0:03 /usr/sbin/VBoxService
root 3961 0.0 0.0 4416 2032 ? Ss 07:32 0:00 /usr/sbin/cron
root 4031 0.0 0.0 2776 2164 ? S 07:32 0:00 dovecot/log
root 4033 0.0 0.0 4564 3940 ? S 07:32 0:00 dovecot/config
root 4076 0.0 0.1 15788 5916 ? Sl 07:32 0:00 lightdm --session-child 12 19
root 4310 0.0 0.0 4556 2100 ? S 07:32 0:00 /usr/sbin/vsftpd
root 4340 0.0 0.0 10256 4136 ? Ss 07:32 0:00 /usr/sbin/nmbd -D
root 4366 0.0 0.1 19884 8236 ? Ss 07:32 0:00 /usr/sbin/smbd -D
root 4390 0.0 0.0 20400 3564 ? S 07:32 0:00 /usr/sbin/smbd -D
Processes use a few command commands, such as kill, ps, jobs fg and bg. We'll demo how to use these commands.
In Elive Linux we have several tools we can use to create and edit text files. First of all, we can create and edit files straight from the command line itself. Secondly, we have text editors such as vi, nano, emacs etc...
We can create a file with the touch command. All this does is create an empty file. If you use the command on an existing file it just changes the date and timestamp of the file. Here is an example of touch.
[aali@Elive:~]$ ls -l
total 4
-rw-r--r-- 1 aali aali 202 Dec 11 06:41 about.html
drwxr-xr-x 9 aali aali 320 Nov 5 17:51 Documents
drwxr-xr-x 4 aali aali 416 Nov 6 08:18 Downloads
drwxr-xr-x 2 aali aali 112 Dec 2 20:55 fontconfig
drwxr-xr-x 2 aali aali 208 Nov 5 17:51 Music
drwxr-xr-x 5 aali aali 296 Nov 5 17:51 Pictures
drwxr-xr-x 3 aali aali 136 Dec 11 06:33 projects
drwxr-xr-x 2 aali aali 120 Nov 5 17:51 Public
-rw-r--r-- 1 aali aali 0 Nov 5 17:54 testFile.txt
drwxr-xr-x 4 aali aali 144 Nov 5 17:51 Videos
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ touch file1
[aali@Elive:~]$ ls -l
total 4
-rw-r--r-- 1 aali aali 202 Dec 11 06:41 about.html
drwxr-xr-x 9 aali aali 320 Nov 5 17:51 Documents
drwxr-xr-x 4 aali aali 416 Nov 6 08:18 Downloads
-rw-r--r-- 1 aali aali 0 Dec 13 09:24 file1
drwxr-xr-x 2 aali aali 112 Dec 2 20:55 fontconfig
drwxr-xr-x 2 aali aali 208 Nov 5 17:51 Music
drwxr-xr-x 5 aali aali 296 Nov 5 17:51 Pictures
drwxr-xr-x 3 aali aali 136 Dec 11 06:33 projects
drwxr-xr-x 2 aali aali 120 Nov 5 17:51 Public
-rw-r--r-- 1 aali aali 0 Nov 5 17:54 testFile.txt
drwxr-xr-x 4 aali aali 144 Nov 5 17:51 Videos
[aali@Elive:~]$
[aali@Elive:~]$ ls -l file1
-rw-r--r-- 1 aali aali 0 Dec 13 09:24 file1
[aali@Elive:~]$
[aali@Elive:~]$ touch file1
[aali@Elive:~]$ ls -l file1
-rw-r--r-- 1 aali aali 0 Dec 13 09:25 file1
[aali@Elive:~]$
First we checked to see what files we have, then we created a file called file1 with the touch command. Then we updated the timestamp on the file by running it with the touch command again.
[aali@Elive:~]$ echo "This text is going to file one." > file1
[aali@Elive:~]$
[aali@Elive:~]$ cat file1
This text is going to file one.
[aali@Elive:~]$
[aali@Elive:~]$ echo "We're adding a second line by editing file1" >> file1
[aali@Elive:~]$
[aali@Elive:~]$ cat file1
This text is going to file one.
We're adding a second line by editing file1
[aali@Elive:~]$
[aali@Elive:~]$
Now, we updated the file1 file and edited it again all from the command line just by using the echo command.
We can also use the text editors such as vi or nano or emacs, Elive has them all available as part of the main distribution.
[aali@Elive:~]$ vi file2
CSApprox skipped; terminal only has 8 colors, not 88/256
Try checking :help csapprox-terminal for workarounds
Press ENTER or type command to continue
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ ls -l | grep file
-rw-r--r-- 1 aali aali 76 Dec 13 09:27 file1
-rw-r--r-- 1 aali aali 63 Dec 13 09:30 file2
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ cat file1
This text is going to file one.
We're adding a second line by editing file1
[aali@Elive:~]$
[aali@Elive:~]$ cat file2
This text is in file two.
This text is being written with vi.
[aali@Elive:~]$
[aali@Elive:~]$
As you can see above, we've created a file called file2 with vi and added a couple of lines to it. So your options are many when it comes to creating and editing text files in Elive Linux.
We have a few tools or commands available to install and update software packages in Elive Linxu. We have the aptitude, apt-get, dpkg and we have synaptic package manager when working on the GUI. We'll demonstrate some of these commands in the following steps. The aptitude command can be used to install new software packages, update existing ones or delete packages.
[aali@Elive:~]$ sudo aptitude show vlc
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
Package: vlc
State: installed
Automatically installed: no
Version: 1:2.0.6-dmo3+deb7u2
Priority: optional
Section: video
Maintainer: Christian Marillat <[email protected]>
Architecture: i386
Uncompressed Size: 3,449 k
Depends: fonts-freefont-ttf, vlc-nox (= 1:2.0.6-dmo3+deb7u2), libaa1 (>= 1.4p5), libavcodec54 (>= 8:1.0.0), libavutil51 (>=
8:1.0.0), libc6 (>= 2.8), libcaca0 (>= 0.99.beta17-1), libfreetype6 (>= 2.2.1), libfribidi0 (>= 0.19.2), libgcc1 (>=
1:4.1.1), libgl1-mesa-glx | libgl1, libqtcore4 (>= 4:4.8.0), libqtgui4 (>= 4:4.7.0~beta1), libsdl-image1.2 (>= 1.2.10),
libsdl1.2debian (>= 1.2.11), libstdc++6 (>= 4.6), libtar0, libva-x11-1 (> 1.0.15~), libva1 (> 1.0.15~), libvlccore5 (>=
2.0.0), libx11-6, libxcb-composite0, libxcb-keysyms1 (>= 0.3.9), libxcb-randr0 (>= 1.1), libxcb-shm0, libxcb-xv0 (>= 1.2),
libxcb1 (>= 1.6), libxext6, libxinerama1, libxpm4, zlib1g (>= 1:1.2.3.3)
Recommends: vlc-plugin-notify (= 1:2.0.6-dmo3+deb7u2), vlc-plugin-pulse (= 1:2.0.6-dmo3+deb7u2), xdg-utils
Suggests: videolan-doc
Breaks: vlc-data (< 1.1.5), vlc-nox (< 2.0.2)
Replaces: vlc-nox (<= 1:2.0.1-dmo3)
Provides: mp3-decoder
Description: multimedia player and streamer
VLC is the VideoLAN project's media player. It plays MPEG, MPEG-2, MPEG-4, DivX, MOV, WMV, QuickTime, WebM, FLAC, MP3, Ogg/Vorbis
files, DVDs, VCDs, podcasts, and multimedia streams from various network sources.
VLC can also be used as a streaming server that duplicates the stream it reads and multicasts them through the network to other
clients, or serves them through HTTP.
VLC has support for on-the-fly transcoding of audio and video formats, either for broadcasting purposes or for movie format
transformations. Support for most output methods is provided by this package, but features can be added by installing additional
audio plugins (vlc-plugin-pulse, vlc-plugin-sdl) or video plugins (vlc-plugin-sdl).
Homepage: http://www.videolan.org/vlc/
[aali@Elive:~]$
The aptitude show package_name shows us a lot of information about a certain package. Above I ran the command with the vlc package and it shows that the package is installed and up to date, the maintainer, architecture dependents etc.. Next we'll check to see of a package that is not installed. And then install it.
[aali@Elive:~]$ sudo aptitude show wireshark
Package: wireshark
State: not installed
Version: 1.12.1+g01b65bf-4+deb8u6~deb7u7
Priority: optional
Section: net
Maintainer: Balint Reczey <[email protected]>
Architecture: i386
Uncompressed Size: 2,474 k
Depends: libc6 (>= 2.7), libcairo2 (>= 1.2.4), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 (>= 3.3.16),
libnl-3-200 (>= 3.2.7), libnl-genl-3-200 (>= 3.2.7), libnl-route-3-200, libpango1.0-0 (>= 1.14.0), libpcap0.8 (>= 0.9.8),
libportaudio2 (>= 19+svn20101113), libwireshark5 (>= 1.12.0~rc3), libwiretap4 (>= 1.12.0~rc1), libwsutil4 (>= 1.12.0~rc3),
zlib1g (>= 1:1.1.4), wireshark-common (= 1.12.1+g01b65bf-4+deb8u6~deb7u7), xdg-utils
Conflicts: ethereal (< 1.0.0-3)
Replaces: ethereal (< 1.0.0-3)
Description: network traffic analyzer - GTK+ version
Wireshark is a network "sniffer" - a tool that captures and analyzes packets off the wire. Wireshark can decode too many protocols
to list here.
This package provides the GTK+ version of wireshark.
Homepage: http://www.wireshark.org/
[aali@Elive:~]$
[aali@Elive:~]$
It shows that wireshark is not installed and tell us everything we need to know about it from it's dependencies to it's current version and maintainer etc...All we need to do to install it is aptitude install wireshark
We'll use apt-get install to install the wireshark software package.
[aali@Elive:~]$ sudo apt-get install wireshark
[sudo] password for aali:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libc-ares2 libsmi2ldbl libwireshark-data libwireshark5 libwiretap4 libwsutil4 wireshark-common
Suggested packages:
snmp-mibs-downloader wireshark-doc
The following NEW packages will be installed:
libc-ares2 libsmi2ldbl libwireshark-data libwireshark5 libwiretap4 libwsutil4 wireshark wireshark-common
0 upgraded, 8 newly installed, 0 to remove and 2 not upgraded.
Need to get 16.3 MB of archives.
After this operation, 59.8 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://security.debian.org/debian-security/ wheezy/updates/main libc-ares2 i386 1.9.1-3+deb7u2 [75.2 kB]
Get:2 http://security.debian.org/debian-security/ wheezy/updates/main libwsutil4 i386 1.12.1+g01b65bf-4+deb8u6~deb7u7 [109 kB]
Get:3 http://security.debian.org/debian-security/ wheezy/updates/main libwiretap4 i386 1.12.1+g01b65bf-4+deb8u6~deb7u7 [224 kB]
Get:4 http://security.debian.org/debian-security/ wheezy/updates/main libwireshark-data all 1.12.1+g01b65bf-4+deb8u6~deb7u7 [1,151 kB]
Get:5 http://security.debian.org/debian-security/ wheezy/updates/main libwireshark5 i386 1.12.1+g01b65bf-4+deb8u6~deb7u7 [13.3 MB]
Get:6 http://security.debian.org/debian-security/ wheezy/updates/main wireshark-common i386 1.12.1+g01b65bf-4+deb8u6~deb7u7 [206 kB]
Get:7 http://security.debian.org/debian-security/ wheezy/updates/main wireshark i386 1.12.1+g01b65bf-4+deb8u6~deb7u7 [999 kB]
Get:8 http://deb.debian.org/debian/ wheezy/main libsmi2ldbl i386 0.4.8+dfsg2-7 [146 kB]
Fetched 16.3 MB in 5s (2,856 kB/s)
Preconfiguring packages ...
Selecting previously unselected package libsmi2ldbl:i386.
(Reading database ... 223536 files and directories currently installed.)
Unpacking libsmi2ldbl:i386 (from .../libsmi2ldbl_0.4.8+dfsg2-7_i386.deb) ...
Selecting previously unselected package libc-ares2:i386.
Unpacking libc-ares2:i386 (from .../libc-ares2_1.9.1-3+deb7u2_i386.deb) ...
Selecting previously unselected package libwsutil4:i386.
Unpacking libwsutil4:i386 (from .../libwsutil4_1.12.1+g01b65bf-4+deb8u6~deb7u7_i386.deb) ...
Selecting previously unselected package libwiretap4:i386.
Unpacking libwiretap4:i386 (from .../libwiretap4_1.12.1+g01b65bf-4+deb8u6~deb7u7_i386.deb) ...
Selecting previously unselected package libwireshark-data.
Unpacking libwireshark-data (from .../libwireshark-data_1.12.1+g01b65bf-4+deb8u6~deb7u7_all.deb) ...
Selecting previously unselected package libwireshark5:i386.
Unpacking libwireshark5:i386 (from .../libwireshark5_1.12.1+g01b65bf-4+deb8u6~deb7u7_i386.deb) ...
Selecting previously unselected package wireshark-common.
Unpacking wireshark-common (from .../wireshark-common_1.12.1+g01b65bf-4+deb8u6~deb7u7_i386.deb) ...
Selecting previously unselected package wireshark.
Unpacking wireshark (from .../wireshark_1.12.1+g01b65bf-4+deb8u6~deb7u7_i386.deb) ...
Processing triggers for man-db ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for menu ...
Processing triggers for shared-mime-info ...
Processing triggers for desktop-file-utils ...
Setting up libsmi2ldbl:i386 (0.4.8+dfsg2-7) ...
Setting up libc-ares2:i386 (1.9.1-3+deb7u2) ...
Setting up libwsutil4:i386 (1.12.1+g01b65bf-4+deb8u6~deb7u7) ...
Setting up libwiretap4:i386 (1.12.1+g01b65bf-4+deb8u6~deb7u7) ...
Setting up libwireshark-data (1.12.1+g01b65bf-4+deb8u6~deb7u7) ...
Setting up libwireshark5:i386 (1.12.1+g01b65bf-4+deb8u6~deb7u7) ...
Setting up wireshark-common (1.12.1+g01b65bf-4+deb8u6~deb7u7) ...
Setting up wireshark (1.12.1+g01b65bf-4+deb8u6~deb7u7) ...
Processing triggers for menu ...
[aali@Elive:~]$
[aali@Elive:~]$
Now we're going to verify if we have wireshark installed with the option and remove it with aptitude.
[aali@Elive:~]$ sudo aptitude show wireshark
Package: wireshark
State: installed
Automatically installed: no
Version: 1.12.1+g01b65bf-4+deb8u6~deb7u7
Priority: optional
Section: net
Maintainer: Balint Reczey <[email protected]>
Architecture: i386
Uncompressed Size: 2,474 k
Depends: libc6 (>= 2.7), libcairo2 (>= 1.2.4), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 (>= 3.3.16),
libnl-3-200 (>= 3.2.7), libnl-genl-3-200 (>= 3.2.7), libnl-route-3-200, libpango1.0-0 (>= 1.14.0), libpcap0.8 (>= 0.9.8),
libportaudio2 (>= 19+svn20101113), libwireshark5 (>= 1.12.0~rc3), libwiretap4 (>= 1.12.0~rc1), libwsutil4 (>= 1.12.0~rc3),
zlib1g (>= 1:1.1.4), wireshark-common (= 1.12.1+g01b65bf-4+deb8u6~deb7u7), xdg-utils
Conflicts: ethereal (< 1.0.0-3)
Replaces: ethereal (< 1.0.0-3)
Description: network traffic analyzer - GTK+ version
Wireshark is a network "sniffer" - a tool that captures and analyzes packets off the wire. Wireshark can decode too many protocols
to list here.
This package provides the GTK+ version of wireshark.
Homepage: http://www.wireshark.org/
[aali@Elive:~]$
The aptitude command shows that wireshark is installed and we'll use it again to remove it.
[aali@Elive:~]$ sudo aptitude remove wireshark
The following packages will be REMOVED:
libc-ares2{u} libsmi2ldbl{u} libwireshark-data{u} libwireshark5{u} libwiretap4{u} libwsutil4{u} wireshark wireshark-common{u}
0 packages upgraded, 0 newly installed, 8 to remove and 2 not upgraded.
Need to get 0 B of archives. After unpacking 59.8 MB will be freed.
Do you want to continue? [Y/n/?] y
(Reading database ... 223853 files and directories currently installed.)
Removing wireshark ...
Removing wireshark-common ...
Removing libwireshark5:i386 ...
Removing libc-ares2:i386 ...
Removing libsmi2ldbl:i386 ...
Removing libwireshark-data ...
Removing libwiretap4:i386 ...
Removing libwsutil4:i386 ...
Processing triggers for desktop-file-utils ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for shared-mime-info ...
Processing triggers for man-db ...
Processing triggers for menu ...
[aali@Elive:~]$
We can use the apt-get and aptitude command interchangebly. We can also install packages with the .deb extension using the dpkg command.
Figure 9.1 dpkg.
The installation steps after running the command.
Figure 9.2 dpkg
To remove run the **dpkg -r ** option for remove and the package is removed.
In Elive Linux we can use a couple of tools to automate and schedule tasks for a later date or time. We have a couple of tools available to most Linux distrubtions that are usually used for this tasks. There is a tool called "at" which used to schedule one time tasks and another tool called cron which is used for recurring taks. In this section we'll take a look at how to use these tools. The "at" tool is not installed on Elive linux by default but it is very easy to install. We can use any of the package installation tools that we've already discussed in the previous section.
[aali@Elive:~]$ sudo aptitude install at
The following NEW packages will be installed:
at
0 packages upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 43.4 kB of archives. After unpacking 178 kB will be used.
Get: 1 http://deb.debian.org/debian/ wheezy/main at i386 3.1.13-2+deb7u1 [43.4 kB]
Fetched 43.4 kB in 0s (78.6 kB/s)
Selecting previously unselected package at.
(Reading database ... 223536 files and directories currently installed.)
Unpacking at (from .../at_3.1.13-2+deb7u1_i386.deb) ...
Processing triggers for man-db ...
Setting up at (3.1.13-2+deb7u1) ...
[ ok ] Starting deferred execution scheduler: atd.
[aali@Elive:~]$
All we need to do is type the "at" command followed by the time or date we would like changes to take place. There are many options available for the command please refer to the man pages for the details.
[aali@Elive:~]$ at now +10min
warning: commands will be executed using /bin/sh
at> sudo shutdown -r now
at> <EOT>
at> <EOT>
job 1 at Wed Dec 13 11:48:00 2017
[aali@Elive:~]$
What we did here is schedule a system reboot ten minutes from now. When you set up an "at" task for later, you end the job with which stands for end of task, and you hit ctrl+d to save it. You can verify your at job with the atq command as follows.
[aali@Elive:~]$ atq
1 Wed Dec 13 11:48:00 2017 a aali
[aali@Elive:~]$
[aali@Elive:~]$
If we're not sure about a task or we just want to cancel it we can use the atrm plus the task/job number as follows.
[aali@Elive:~]$ atrm 1
[aali@Elive:~]$ atq
Next we'll look at "cron" which is used for recurring tasks. The cron tool is preinstalled in Elive Linux so we don't need to install it unless you have trouble using it. To start using cron run the make sure the service is up and running by using the service cron status command.
[aali@Elive:~]$ sudo service cron status
[ ok ] cron is running.
[aali@Elive:~]$
[aali@Elive:~]$
Now we can run cron as follows.
[aali@Elive:~]$ sudo crontab -e [sudo] password for aali:
Figure 10.1 crontab
Once you're in cron configuration mode, you have the option of configuring a task to with the following five parameters. Minute, hour day of the month, month and day of the week then the command to run. In our case we configured our cron to run a system upgrade at 2am every Monday.
0 2 * * 2 sudo apt-get upgrade -y
The first number is for the minutes which takes a value of 0-59, the second is for the hour which takes a value of 0-23, the * * are day of the month and month respectively. They take a value of 1-31 and 1-12 respectively. Then whatever command you would like to run. Please refer to the man pages for further configurations options for cron.
In this section we'll setup our Elive Linux as an SSH, FTP, HTTP server.
To setup ftp, install vsftpd and start the service.
[aali@Elive:~]$ sudo aptitude install vsftpd
[sudo] password for aali:
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Package is already installed, so we'll just start it.
[aali@Elive:~]$ sudo service vsftpd restart
Stopping FTP server: vsftpd.
Starting FTP server: vsftpd.
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ sudo service vsftpd status
vsftpd is running
[aali@Elive:~]$
[aali@Elive:~]$
The vsftpd daemon has an anonymous account setup by default so we'll access that just for demo.
Figure 11.1 ftp.
[aali@Elive:~]$ sudo service ssh status
[sudo] password for aali:
[ ok ] sshd is running.
[aali@Elive:~]$
Next we started ssh and logged it to the server with ssh from a remote windows machine.
[aali@Elive:~]$ w
13:32:26 up 6:03, 1 user, load average: 0.18, 0.25, 0.30
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
aali pts/2 win.testlab.home 07:34 3.00s 1.12s 0.00s w
[aali@Elive:~]$
Next we started our http/web server by first starting apache2 service.
[aali@Elive:~]$ sudo service apache2 start
[....] Starting web server: apache2apache2: using 127.0.0.1 for ServerName
httpd (pid 29714) already running
. ok
[aali@Elive:~]$
[aali@Elive:~]$
[aali@Elive:~]$ sudo service apache2 status
Apache2 is running (pid 29714).
[aali@Elive:~]$
Figure 11.2 apache.
To maintain the privacy of users of the Linux system and manage their accounts and supervision, as well as track the problems they will go through, find the solutions to these problems, and inform users the changes, update, and upgrade the system. Even if there is a one user using the system it was always a challenge for the managing users. I will show you some tools and some tasks assigned to add the user to Linux system where you see adding and deleting accounts is an easy process for managing users.
Before we talk about how to create and delete a user account I will talk about the most important text file (/etc/passwd) this text file contains all necessary details and information about all users in the Linux system.
This file is open to users only, and it is readable and writable for root account.
The /etc/passwd file contains only one separate line, limited by a colon (:) for each user account in the system, also it stores the information for each user using the Linux system. Every time we add a new user to the system all details and information for the new user will be stored in the same file.
root /h/jamal >>> sudo cat /etc/passwd
jamal: x:1001:1001: jamal Ibrahim, 1,,:/home/jamal :/bin/bash
tyler: x:1002:1002: tyler, 1,,:/home/tyler :/bin/bash
awil: x:1003:1003: awil, 1,,:/home/awil :/bin/bash
jacquie: x:1004:1004: jacquie, 1,,:/home/jacquie :/bin/bash
matthew: x:1005:1005: matthew, 1,,:/home/matthew :/bin/bash
to get depth in the file I will take the entry of my username jamal.
Jamal : x : 1001 : 1001 : jamal Ibrahim , 1 ,, : /home/jamal : /bin/bash
{---1----}{---2---}{---3-----}{---4----}{---------------5---------------}{----------6------}{-------7-----}
1. **Username field**: This field show the user account name; this user name must be used every time when we log in to the system.
2. **Password field**: Second field is the Password field, not showing the actual password though. The 'x' in this field show the password is encrypted and saved in the /etc/shadow file.
3. **UID field**: Every time when a user account is created, it is assigned with a user id or UID (UID for the user 'jamal' is 1001, in this case) and this field specifies the same.
4. **GID field**: Similar to the UID field, this field specifies which group the user belongs to, the group details being present in /etc/group file.
5. **Comment/Description/User Info field**: This field is the short comment/description/information of the user account.
6. **User Home Directory**: Every time the user signs into the system, he/she is taken to their Home directory, where all their personal files reside. This field provides the absolute path to the user's home directory (/home/jamal in this case).
7. **Shell**: This field show, the user has access to the shell mentioned in this field (user 'jamal' has been given access to /bin/bash or simply bash shell).
Elive is based on Debian, the same distribution flavor as Ubuntu, so we use .deb files for our packages and those files collectively live in a repository.
Debian Package Management details can be found in the Debian Manuals
package popcon size description
apt V:871, I:999 3647 Advanced Packaging Tool (APT), front-end for dpkg providing "http", "ftp", and "file" archive access methods (apt-get/apt-cache commands included)
aptitude V:136, I:778 4415 interactive terminal-based package manager with aptitude(8)
tasksel V:40, I:972 374 tool for selecting tasks for installation on the Debian system (front-end for APT)
unattended-upgrades V:188, I:364 254 enhancement package for APT to enable automatic installation of security upgrades
dselect V:4, I:59 2498 terminal-based package manager (previous standard, front-end for APT and other old access methods)
dpkg V:932, I:999 6745 package management system for Debian
synaptic V:70, I:453 7793 graphical package manager (GNOME front-end for APT)
apt-utils V:391, I:997 1103 APT utility programs:
apt-listchanges V:350, I:838 365 package change history notification tool
apt-listbugs V:7, I:12 451 lists critical bugs before each APT installation
apt-file V:13, I:77 82 APT package searching utility -- command-line interface
Table: Debian package management (Manual), List of Debian package management tools
Source: Debian package management manual and Popularity Contest Stats
In order to understand the components of the Elive repository here are a couple commands
for package in $( dpkg -l | awk '{print $2}' ) ;
do if apt-cache policy "$package" 2>/dev/null | grep -qs "repository.elivecd.org" ;
then echo -e "${package%:*} \tis in Elive repos" ;
fi ;
done
cat /var/lib/apt/lists/repository.elivecd.org_*Packages | grep "^Package:" | wc -l
sudo apt-get
-
acptool: replacement of apmtool. For laptop users.
-
afflib- dpg- on-disk format for storing complete forensic information: sudo apt-get install afflib-dbg, allows files to be digitally signed, chain-of-custody and long-term file integrity. Allows disk images containing privacy sensitive material to be stored on the Internet. Posix stricpting (Linux coding).
-
balsa-dbg: get sudo apt-get install balsa-dbg. Mail client from GNOME desktop. Supports both POP3 and IMAP.
-
cython3-dbg: sudo apt-get install cython-dbg. Libraries built against versions of Python configured with pydebug. Allows python configuration.
-
/etcldibbler/client.conf w/new version. DHCPv6 clients: sudo apt-get install dibbler-client
-
sudo apt-get install DVd+rw-tools-dbp
-
sudo apt-get update
-
sudo apt-get install build-essential save files and execute.
-
sudo apt-get install enigma
The biggest challenges for learning Linux are commands, creating files, and installing image Ubuntu onto the USB. When I started learning Linux from this course, it was hard for me at the beginning.
Talk to potential users!
Project Lead and Troubleshooting How is Ubuntu related to Linux and Debian?
Package Management
User Management
User Management/file and dic
Repository & Systems Administration
Scribe Quality Assurance / Testing
Cat Hearding Editing
Package Management
USB Booting (Mac)
QA: Debian Package Management Workflow
Graphics & Theme
Project Editor Original Draft (2017-10-30) Installation of Elive
Formatting