BASH cheatsheet - Revision history

Eddynetweb: Information regarding screen and apt.

2017-04-15T03:54:51Z

Information regarding screen and apt.

← Older revision		Revision as of 03:54, 15 April 2017
Line 9:		Line 9:
	=== Using APT ===		=== Using APT ===

	~~<source lang="bash">apt~~-~~get update && apt-get~~ upgrade ~~-y && apt-get dist-upgrade -y && apt-get autoclean</source>~~		This one-liner will upgrade the packages and system to the latest revision of whatever distro you're running.

	~~Working on~~ this ~~too~~. ~~We'll~~ get ~~back to~~ it ~~later~~.		<source lang="bash">apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y && apt-get autoclean</source>

			'''For Debian users''': You can also call for backport packages in Debian, which in this instance would allow you to fetch the next revision of packages within the next repo. You can setup backports by following this guide: [[Debian Jessie repos]].

			Regardless, in order to fetch a backport package, use the following:

			<source lang="bash">apt-get -t jessie-backports install "package"</source>

			Backports is useful in this instance because it also is compatible with upgrades for future Debian updates.

			More stuff soon!

	----		----
Line 86:		Line 96:
	Screen is basically a interactive shell which can act as a daemon in the background. It allows you to run shell instances, and also task them with certain commands.		Screen is basically a interactive shell which can act as a daemon in the background. It allows you to run shell instances, and also task them with certain commands.

	~~I will eventually finish this~~, ~~but for now~~:		To create a basic screen session, you'd use the following:

	<source lang="bash">screen -dmS AScreenName ApplicationRuntime</source>		<source lang="bash">screen -dmS AScreenName ApplicationRuntime</source>

	~~Be back later~~!?		"ApplicationRuntime" is whatever you're running in the instance of creating a screen. It's not necessary to immediately specify though, so you can create the screen session without "ApplicationRuntime," then run the application and exit through "Ctrl-A."

			There's more!

	== Diskspace commands ==		== Diskspace commands ==

	Something soon?!		Something soon?!

Eddynetweb: APT information.

2017-03-12T21:05:44Z

APT information.

← Older revision		Revision as of 21:05, 12 March 2017
Line 6:		Line 6:

	Here you will find what I would consider the most common commands that sometimes people just forget when they boop out. I got you fam (it's actually for my sake, really).		Here you will find what I would consider the most common commands that sometimes people just forget when they boop out. I got you fam (it's actually for my sake, really).

			=== Using APT ===

			<source lang="bash">apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y && apt-get autoclean</source>

			Working on this too. We'll get back to it later.

			----

	=== Using "alias" ===		=== Using "alias" ===

Eddynetweb: /* Using screen */

2017-03-12T20:58:59Z

Using screen

← Older revision		Revision as of 20:58, 12 March 2017
Line 71:		Line 71:

	Anyways, that's about it for the scope of this document. If you have questions, remember to check the '''man''' docs for '''ln'''.		Anyways, that's about it for the scope of this document. If you have questions, remember to check the '''man''' docs for '''ln'''.

			----

	=== Using screen ===		=== Using screen ===
Line 81:		Line 83:

	Be back later!?		Be back later!?


	== Diskspace commands ==		== Diskspace commands ==

	Something soon?!		Something soon?!

Eddynetweb: Working on screen information

2017-03-12T20:58:28Z

Working on screen information

← Older revision		Revision as of 20:58, 12 March 2017
Line 71:		Line 71:

	Anyways, that's about it for the scope of this document. If you have questions, remember to check the '''man''' docs for '''ln'''.		Anyways, that's about it for the scope of this document. If you have questions, remember to check the '''man''' docs for '''ln'''.

			=== Using screen ===

			Screen is basically a interactive shell which can act as a daemon in the background. It allows you to run shell instances, and also task them with certain commands.

			I will eventually finish this, but for now:

			<source lang="bash">screen -dmS AScreenName ApplicationRuntime</source>

			Be back later!?


	== Diskspace commands ==		== Diskspace commands ==

	Something soon?!		Something soon?!

Eddynetweb: /* Using "alias" */

2017-03-11T15:56:40Z

Using "alias"

← Older revision		Revision as of 15:56, 11 March 2017
Line 14:		Line 14:

	<source lang="bash">		<source lang="bash">
	alias ""ls -la"="ls"		alias "ls -la"="ls"
	</source>		</source>

Eddynetweb: /* Using symlinks and hardlinks */

2017-03-11T15:36:31Z

Using symlinks and hardlinks

← Older revision		Revision as of 15:36, 11 March 2017
Line 50:		Line 50:
	'''Hard links''' traditionally only work with files, but also physically link to the location on the drive itself by referencing the inode, not an abstract location. '''Symbolic links''' do reference such a abstract location, but as a result, when you move the destination link, it will generally become '''orphaned'''. Though, there are generally advantages and disadvantages with using either one.		'''Hard links''' traditionally only work with files, but also physically link to the location on the drive itself by referencing the inode, not an abstract location. '''Symbolic links''' do reference such a abstract location, but as a result, when you move the destination link, it will generally become '''orphaned'''. Though, there are generally advantages and disadvantages with using either one.

	To make a symbolic link to a specific file or directory:		- To make a symbolic link to a specific file or directory:
	<source lang="bash">		<source lang="bash">
	ln -s /original/path/ /link/path/		ln -s /original/path/ /link/path/
Line 59:		Line 59:
	Yes, you can link directories as well as files, but because of the abstract nature of symlinks, any movement or deletion of the original file will lead to the symlink becoming orphaned/abandoned. Symlinks also do support linking from different volumes. However, they don't have the advantage of a physical inode location so any modification of the original file will likely break the symlink.		Yes, you can link directories as well as files, but because of the abstract nature of symlinks, any movement or deletion of the original file will lead to the symlink becoming orphaned/abandoned. Symlinks also do support linking from different volumes. However, they don't have the advantage of a physical inode location so any modification of the original file will likely break the symlink.

	To make a hard link to a specific file:		- To make a hard link to a specific file:
	<source lang="bash">		<source lang="bash">
	ln /original/file.path /link/file.path		ln /original/file.path /link/file.path
Line 67:		Line 67:

	You can't reference directories, but because hard links actually reference the inode, not the system, they are definite regardless of where you move the original file.		You can't reference directories, but because hard links actually reference the inode, not the system, they are definite regardless of where you move the original file.

			'''Deleting''' either is as simple as deleting the symlink file or directory made. Deleting said file/directory will not impact the data within the original file.

	Anyways, that's about it for the scope of this document. If you have questions, remember to check the '''man''' docs for '''ln'''.		Anyways, that's about it for the scope of this document. If you have questions, remember to check the '''man''' docs for '''ln'''.

Eddynetweb: /* Using symlinks and hardlinks */

2017-03-11T15:34:47Z

Using symlinks and hardlinks

← Older revision		Revision as of 15:34, 11 March 2017
Line 48:		Line 48:
	There are two different types of links, '''hard''' links and '''symbolic''' links. If you notice, the name implies what they both do.		There are two different types of links, '''hard''' links and '''symbolic''' links. If you notice, the name implies what they both do.

	'''Hard links''' traditionally only work with files, but also physically link to the location on the drive itself by referencing the inode, not an abstract location. '''Symbolic links''' do reference such a abstract location, but as a result, when you move the destination link, it will generally become '''orphaned'''. Though~~, as a general result~~, there are generally advantages and disadvantages with using either.		'''Hard links''' traditionally only work with files, but also physically link to the location on the drive itself by referencing the inode, not an abstract location. '''Symbolic links''' do reference such a abstract location, but as a result, when you move the destination link, it will generally become '''orphaned'''. Though, there are generally advantages and disadvantages with using either one.

	To make a symbolic link to a specific file or directory:		To make a symbolic link to a specific file or directory:

Eddynetweb: Added symlinks and modified alias info.

2017-03-11T15:33:16Z

Added symlinks and modified alias info.

@@ Line 1: / Line 1: @@
-It's basically stupid simple:
+Welcome to the BASH cheatsheet! Ever feel like you've just derped out and forgot some commands? This is what this is for.
 <source lang="bash">
 alias ["command"]=["origin"]
@@ Line 6: / Line 25: @@
 To unalias:
 <source lang="bash">
-unalias ["command"]
+ln -s /original/path/ /link/path/
 </source>
-Why? I asked the question "how do I unalias a command" and well, yeah.
+'''Limitations''':
-Enjoy!
+Something soon?!

Eddynetweb: Eddynetweb moved page Alias and unalias to BASH cheatsheet without leaving a redirect

2017-03-11T14:48:15Z

Eddynetweb moved page Alias and unalias to BASH cheatsheet without leaving a redirect

← Older revision

Revision as of 14:48, 11 March 2017

Eddynetweb at 19:23, 8 March 2017

2017-03-08T19:23:33Z

← Older revision		Revision as of 19:23, 8 March 2017
Line 7:		Line 7:
	To unalias:		To unalias:

	<source lang="bash"		<source lang="bash">
	unalias ["command"]		unalias ["command"]
	</source>		</source>