UBUNTU: $ sudo apt-get install inxi FEDORA: $ sudo yum install inxi
$ inxi CPU~Dual core Intel Core i7-2640M (-HT-MCP-) clocked at 815 Mhz Kernel~3.14.6-200.fc20.x86_64 x86_64 Up~2:31 Mem~2558.2/7868.2MB HDD~160.0GB(63.9% used) Procs~198 Client~Shell inxi~2.1.28Read more...
$ wget http://www.keepassx.org/releases/keepassx-0.4.3.tar.gz
$ sudo yum install qt-devel qt-config gcc-c++ libXtst-devel
$ tar xzf keepassx-0.4.3.tar.gz $ cd keepassx-0.4.3/and compile using make:
"unknown X server version"Apart of the updated Virtualbox version this guide also assumes functional Fedora Linux installation with working Internet connection. Lastly, the aim here is to provide a generic guide for Virtualbox Guest additions on Fedora Linux virtual machine and as a result reader needs to adjust some of the following commands to is your envireoment.
Virtual box menu -> Devices -> Insert Guest Additions CD imageThe following message will pop up:
# mount | grep -i vbox /dev/sr0 on /run/media/fedora/VBOXADDITIONS_VERSION type iso9660 # cd /run/media/fedora/VBOXADDITIONS_VERSION # ls 32Bit AUTORUN.INF cert runasroot.sh VBoxSolarisAdditions.pkg VBoxWindowsAdditions.exe 64Bit autorun.sh OS2 VBoxLinuxAdditions.run VBoxWindowsAdditions-amd64.exe VBoxWindowsAdditions-x86.exeRead more...
$ yes > /dev/null &  5322With the above command we have started process with job ID "1" and PID 5322. Let's start few more processes:
$ yes > /dev/null &  5402 $ yes > /dev/null &  5403 $ yes > /dev/null &  5404 $ yes > /dev/null &  5405In order terminate all processes we use tools such as killall or pkill. How it works is that we kill all processes based on their name. To try your regular expression use pgrep command:
$ pgrep yes 5322 5402 5403 5404 5405Read more...
$ yes > /dev/null &  3706The command above will start process s
yesand output its standard output to
/dev/null. What we are interested in here, is the second line which contains the following information "" ( job ID ) and "3706" the actual PID. On your Linux system you can run multiple process at any given time and each process, depending on the user privileges can be terminated using either kill or killall commands. Let's start few additional processes:
$ yes > /dev/null &  3782 $ yes > /dev/null &  3783 $ yes > /dev/null &  3784 $ yes > /dev/null &  3785From the above you can see that we have started additional processes using
yescommand and that each process have different PID. To list all you processes forked from the current shell use
$ jobs  Running yes > /dev/null &  Running yes > /dev/null &  Running yes > /dev/null & - Running yes > /dev/null & + Running yes > /dev/null &Read more...
yumyou may have noticed a frequent metadata updates when using this tool:
Loaded plugins: langpacks, refresh-packagekit google-chrome rpmfusion-free-updates rpmfusion-nonfree-updates updates/20/x86_64/metalink updates virtualbox updates/20/x86_64/primary_dbAlthough, this behavior is intentional and provides many benefits in order to keep your software updated, it can also however be quite frustrating if you see and have to wait for this update to finish couple times a day. The default expiry time of system's metadata is 90 minutes, and therefor every time 1,5 hour elapses your system will download new repository updates. For a production server this poses not obstacle or problem. However, for desktop systems this feature can be quite annoying.
--sortor "k" options. In this short tutorial we will show how to sort processes based on memory usage.
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1354 1.9 0.4 220900 37780 tty1 Ss+ 07:18 7:05 /usr/bin/Xorg lrendek 8803 0.0 0.0 116536 3260 pts/3 Ss+ 09:54 0:00 /bin/bash lrendek 8885 0.0 0.0 116668 3480 pts/4 Ss+ 09:59 0:00 /bin/bash lrendek 9294 0.0 0.0 116536 3320 pts/5 Ss 10:01 0:00 /bin/bash root 11633 0.0 0.0 200656 3616 pts/5 S 11:18 0:00 su lrendek 2709 9.5 9.1 2114284 739140 ? Sl 07:21 32:39 /usr/lib64/firefox/firefox lrendek 12300 0.0 0.0 116536 3260 pts/1 Ss 11:25 0:00 /bin/bash lrendek 12341 0.0 0.0 110272 1184 pts/1 S+ 11:25 0:00 less -s lrendek 12353 0.0 0.0 116536 3196 pts/2 Ss 11:26 0:00 /bin/bashAs it was already mentioned previously the default ps command output is unsorted. However, ps allows to sort its output based on any column value. To sort by memory usage we can use either "%MEM" or "RSS" columns. The RSS ( Resident Set Size ) is a total memory usage in kilobytes and "%RAM" shows the same information in terms of percent usage of total memory amount available. What follows are few examples on how to instruct ps command to sort by memory usage:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1354 1.7 0.4 221272 37184 tty1 Ss+ 07:18 5:55 /usr/bin/Xorg lubos 8803 0.0 0.0 116536 3260 pts/3 Ss+ 09:54 0:00 /bin/bash lubos 8885 0.0 0.0 116668 3480 pts/4 Ss+ 09:59 0:00 /bin/bash lubos 9294 0.0 0.0 116536 3320 pts/5 Ss 10:01 0:00 /bin/bash root 11633 0.0 0.0 200656 3616 pts/5 S 11:18 0:00 su root 11642 0.0 0.0 116644 3452 pts/5 S+ 11:18 0:00 bashRead more...
# mkdir /opt/media # COPY YOUR MEDIA FILES TO /opt/mediaNext, install forked-daapd daemon:
# apt-get install forked-daapdOnce the installation is finished confirm that forked-daapd is running:
# /etc/init.d/forked-daapd status forked-daapd is runningand you may also want to check on what port is forked-daapd listening. The default socket is 0.0.0.0:3689.
# yum install imagemagickUbuntu/Debian
# apt-get install imagemagick