Linux: Difference between revisions

No change in size ,  19 September 2017
m
Fixed linux to Linux
(Undo revision 11180 by Tytytt (talk))
m (Fixed linux to Linux)
Line 3: Line 3:


==Distributions==
==Distributions==
Linux comes in several distributions with their own [[Package Management|package managers]] and other implementations of things. Many linux distributions include the [[GNU]] suite of essential software however a notable few (such as Google's [[Android]]) omit GNU and instead opt for their own custom suite of software.
Linux comes in several distributions with their own [[Package Management|package managers]] and other implementations of things. Many Linux distributions include the [[GNU]] suite of essential software however a notable few (such as Google's [[Android]]) omit GNU and instead opt for their own custom suite of software.


==Conventions==
==Conventions==
Linux distributions have many conventions that make Linux more than a kernel. Here are some:
Linux distributions have many conventions that make Linux more than a kernel. Here are some:


- Linux file systems usually include ones with unix-like permissions, as well as linux file systems not usually using a file allocation table.
- Linux file systems usually include ones with unix-like permissions, as well as Linux file systems not usually using a file allocation table.


- Linux installations usually use the UNIX directory structure with there being one "root" folder (represented as a single forward slash) with other folders including devices, apps, and config files like /dev, /bin, and /etc.
- Linux installations usually use the UNIX directory structure with there being one "root" folder (represented as a single forward slash) with other folders including devices, apps, and config files like /dev, /bin, and /etc.
Line 17: Line 17:


==Everything is a file==
==Everything is a file==
In linux, even things like hardware are represented as files that can be written to. For example, the file for the first hard drive is /dev/sda. This means that if you want to write bytes directly to the drive you can use an app that lays bytes (like dd) to write directly to that file. This can be done by using the app named echo to output something and piping the output to dd which you specify the hard disk's file to. (The exact command is "echo Something | dd of=/dev/sda". This will ruin your drive's boot sector so please do not do this.)
In Linux, even things like hardware are represented as files that can be written to. For example, the file for the first hard drive is /dev/sda. This means that if you want to write bytes directly to the drive you can use an app that lays bytes (like dd) to write directly to that file. This can be done by using the app named echo to output something and piping the output to dd which you specify the hard disk's file to. (The exact command is "echo Something | dd of=/dev/sda". This will ruin your drive's boot sector so please do not do this.)


There are also more liberal concepts of devices in /dev. /dev/null, when written to, discards all data sent to it. If you write to /dev/null and then open it it will still be empty.
There are also more liberal concepts of devices in /dev. /dev/null, when written to, discards all data sent to it. If you write to /dev/null and then open it it will still be empty.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.