Linux applications - Revision history

Lilith2 at 09:38, 24 September 2015

2015-09-24T09:38:12Z

Lilith2: /* Compiling source code */

2015-09-22T19:46:05Z

‎Compiling source code

Lilith2 at 20:56, 19 September 2015

2015-09-19T20:56:16Z

Lilith2 at 20:55, 19 September 2015

2015-09-19T20:55:11Z

Lilith2 at 20:53, 19 September 2015

2015-09-19T20:53:44Z

Show changes

Alex at 08:32, 11 September 2015

2015-09-11T08:32:41Z

Lilith2: /* Intrusion detection */

2015-09-09T16:24:44Z

‎Intrusion detection

Lilith2 at 17:03, 6 August 2015

2015-08-06T17:03:57Z

Lilith2 at 17:02, 6 August 2015

2015-08-06T17:02:44Z

Lilith2 at 16:12, 6 August 2015

2015-08-06T16:12:02Z

@@ Line 275: / Line 275: @@
 * Website: http://conky.sourceforge.net/
 * Documentation: http://conky.sourceforge.net/documentation.html
 == Security applications ==

@@ Line 137: / Line 137: @@
 . Unpack the tarball in order to get access to the source code and other files:
-  $ tar -xvfz tarballname.tar.gz
+  $ tar -zxvf tarballname.tar.gz
 or
-  $ tar -xvfz tarballname.tar.bz2
+  $ tar -zxvf tarballname.tar.bz2
 . If present, the documentation in the extracted directories provides information about the software, changes since last version, links to more documentation, information regrading the author of the software, steps for compilation and installation of software etc. Name of the files (and case) may differ but usually the information is divided into two files, a "Readme" and an "Install". The last covers all the information required for compilation and installation, and all the other information is covered in the "Readme" file.

@@ Line 1: / Line 1: @@
-[[File:Repository2.jpg|480px|thumb|right|Caek repository]]
+[[File:Repository2.jpg|640px|thumb|right|Caek repository]]
 Linux distributions include great software by default and their repositories. And with so many flavours of linux, finding the right application for getting things done can be tough. Hence my proposal to share interesting apps. The page was kicked off with a short explanation on installing, and a few categories. Add your 2 cents! If a fitting category is not available, create it.
@@ Line 35: / Line 35: @@
 https://github.com/voidlinux/xbps/blob/master/README.md
 === apt ===
 Apt makes collection of software available to the user and does the dirty work of downloading all the required packages and installing them by calling dpkg in the correct order to respect the dependencies. Apt is a library and several frontends have been developed on top of that library, of which apt-get is one. I not works, check internet connection.

@@ Line 1: / Line 1: @@
-[[File:Repository2.jpg|640px|thumb|right|Caek repository]]
+[[File:Repository2.jpg|480px|thumb|right|Caek repository]]
 Linux distributions include great software by default and their repositories. And with so many flavours of linux, finding the right application for getting things done can be tough. Hence my proposal to share interesting apps. The page was kicked off with a short explanation on installing, and a few categories. Add your 2 cents! If a fitting category is not available, create it.
@@ Line 6: / Line 6: @@
 There are many ways to install applications, via graphical front-ends and via the command-line. You can use all of them. It used to be a problem when apt-get did not track which packages were automatically installed while aptitude did, but now that both packages share this list, there is no reason to avoid switching back and forth between the two or between one and front-ends related to the other.
 == Graphical front-ends ==
 The Gnome PackageKit is one of two graphical package managers installed out of the box if and when you installed GNOME as desktop manager in Ubuntu. In older GNOME you can access it from the menu at ''Applications > System Tools > Add/Remove Software. ''PackageKit is designed to unify all the software graphical tools used in different distributions.  It abstracts the various underlying package management technologies like yum, apt, smart etc. and provides unified graphical and command line frontends.
@@ Line 32: / Line 31: @@
 Some noteworthy alternatives to apt-get are cupt, wajig and xbps. Cupt wraps several tools including apt-get, and wajig is a (partial) APT reimplementation. Xbps was written from scratch.
 === xbps ===
 The X Binary Package System (in short XBPS) is a binary package system designed and implemented from scratch. Its goal is to be fast, easy to use, bug-free, featureful and portable as much as possible. The XBPS code is totally compatible with POSIX/SUSv2/C99 standards, and released with a Simplified BSD license (2 clause). There is a well documented API provided by the XBPS Library that is the basis for its frontends to handle binary packages and repositories. It is used in the voidlinux distro.

← Older revision		Revision as of 08:32, 11 September 2015
Line 732:		Line 732:
	== References ==		== References ==

−	[[Category:~~Resources~~]]	+	[[Category:How_To]]

@@ Line 405: / Line 405: @@
 * Mailinglists: http://sourceforge.net/p/tripwire/mailman/
 * Available from repository.
-* Example install and configuration of tripwire on debian: [[Linux server security#Installing intrusion detection|Linux server security: Installing intrusion detection]]
+* Example install and configuration of tripwire on debian: [[Linux security#Installing intrusion detection|Linux security: Installing intrusion detection]] and [[Linux server security#Installing intrusion detection|Linux server security: Installing intrusion detection]]
 === Traffic capture ===

← Older revision		Revision as of 17:03, 6 August 2015
Line 731:		Line 731:

	== References ==		== References ==
		+
		+	[[Category:Resources]]

@@ Line 184: / Line 184: @@
 == Transferring application data to another distribution == <!--T:155-->
-If you set up a separate <code>/home</code> during partitioning, when you perform the new installation, you can tell the installer to reformat the first partition <code>/</code> (to start from scratch), but leave the second partition alone and just mount it again to <code>/home</code>. Then, all you need to do is make sure that you set up the same username and password as before, and everything should be back to the way it was (later you can change them).
+If you set up a separate <code>/home</code> during partitioning for your current system, when you perform the new installation, you can tell the installer to reformat the first partition <code>/</code> (to start from scratch), but leave the second partition alone and just mount it again to <code>/home</code>. Then, all you need to do is make sure that you set up the same username and password as before, and everything should be back to the way it was (later you can change them).
 If you did not, go into <code>/home/user</code> and backup all personal and application data on for example, an external disk. Your personal files are probably all visible and easily copied. For the application data, use the View menu in your file manager to set Show hidden files and copy all <code>.application</code> directories you wish to keep. Mind dependencies. Especially keys. Those may need exporting and copy too. Then after installing the other distro or re-installing or upgrading the existing linux, put the <code>.application</code> directories in the new <code>/home/user</code> directory.