Franske ITC-2480 Lab 11 - Revision history

BenFranske: Update to mjnk version

2021-12-03T20:03:41Z

Update to mjnk version

BenFranske: /* Adding a 2nd disk */

2018-03-22T06:13:43Z

Adding a 2nd disk

← Older revision		Revision as of 06:13, 22 March 2018
Line 35:		Line 35:
	# You may also have noticed there is an ''sdb'' that currently has no partitions. We are going to format this drive into 2 partitions, format them, and then setup automatic mounting of the partitions.		# You may also have noticed there is an ''sdb'' that currently has no partitions. We are going to format this drive into 2 partitions, format them, and then setup automatic mounting of the partitions.
	# To start, run '''cfdisk /dev/sdb''' as root. ''cfdisk'' is a graphical version of ''fdisk'', which is a tool used to setup disk partitioning. Note that ''fdisk'' or any other partitioning software only sets up the MBR, and does not actually format the drive even though you can set a partition type identifier such as '''fat32''', '''Linux''', etc. Also notice how we tell ''cfdisk'' what drive we want to edit the partition on by appending the drive device "file" to the end of the command.		# To start, run '''cfdisk /dev/sdb''' as root. ''cfdisk'' is a graphical version of ''fdisk'', which is a tool used to setup disk partitioning. Note that ''fdisk'' or any other partitioning software only sets up the MBR, and does not actually format the drive even though you can set a partition type identifier such as '''fat32''', '''Linux''', etc. Also notice how we tell ''cfdisk'' what drive we want to edit the partition on by appending the drive device "file" to the end of the command.
	#* Note: some very large drives can no longer use MBR partition tables and there are other reasons to switch to the newer standard for partitioning, GPT partition tables. In order to do that you would use different tools such as '''gdisk''' and '''cgdisk''' instead of '''fdisk''' and '''cfdisk'''. There are several other differences in the way GPT partitions work so you'll want to do some research about them before you try using them. Finally, many newer large drives use 4096 byte "Advanced Format" sectors instead of the traditional 512 byte hard drive sectors. Using these disks most efficiently requires adjusting the sector size in software to match the physical sector size on the disk when partitioning and/or formatting.		# Because our new drives contain no existing partitions we are asked what type of partition table to create. Choose to create a ''dos'' (aka ''MBR'') style partition table. Although this is an older style partition table it is well supported by many operating systems and BIOSes. The primary benefit of the newer ''GPT'' style tables is their ability to work with very large drives.
	# Because our new drives contain no existing partitions we are asked what type of partition table to create. Choose to create a ''dos'' (aka ''MBR'') style partition table.
	# Once in ''cfdisk'', Select the ''New'' option. Now select ''primary'' as we are making a primary MBR partition, then set the size close to ''5GB'' (it doesn't need to be exact).		# Once in ''cfdisk'', Select the ''New'' option. Now select ''primary'' as we are making a primary MBR partition, then set the size close to ''5GB'' (it doesn't need to be exact).
	# Using the arrow keys to go down to the remaining ''Free Space'' on the drive, and press enter to again select ''New''. Create another ''primary'' partition, and set the size to about ''2GB''.		# Using the arrow keys to go down to the remaining ''Free Space'' on the drive, and press enter to again select ''New''. Create another ''primary'' partition, and set the size to about ''2GB''.

BenFranske: /* Adding a 2nd disk */

2018-03-22T06:09:51Z

Adding a 2nd disk

← Older revision		Revision as of 06:09, 22 March 2018
Line 36:		Line 36:
	# To start, run '''cfdisk /dev/sdb''' as root. ''cfdisk'' is a graphical version of ''fdisk'', which is a tool used to setup disk partitioning. Note that ''fdisk'' or any other partitioning software only sets up the MBR, and does not actually format the drive even though you can set a partition type identifier such as '''fat32''', '''Linux''', etc. Also notice how we tell ''cfdisk'' what drive we want to edit the partition on by appending the drive device "file" to the end of the command.		# To start, run '''cfdisk /dev/sdb''' as root. ''cfdisk'' is a graphical version of ''fdisk'', which is a tool used to setup disk partitioning. Note that ''fdisk'' or any other partitioning software only sets up the MBR, and does not actually format the drive even though you can set a partition type identifier such as '''fat32''', '''Linux''', etc. Also notice how we tell ''cfdisk'' what drive we want to edit the partition on by appending the drive device "file" to the end of the command.
	#* Note: some very large drives can no longer use MBR partition tables and there are other reasons to switch to the newer standard for partitioning, GPT partition tables. In order to do that you would use different tools such as '''gdisk''' and '''cgdisk''' instead of '''fdisk''' and '''cfdisk'''. There are several other differences in the way GPT partitions work so you'll want to do some research about them before you try using them. Finally, many newer large drives use 4096 byte "Advanced Format" sectors instead of the traditional 512 byte hard drive sectors. Using these disks most efficiently requires adjusting the sector size in software to match the physical sector size on the disk when partitioning and/or formatting.		#* Note: some very large drives can no longer use MBR partition tables and there are other reasons to switch to the newer standard for partitioning, GPT partition tables. In order to do that you would use different tools such as '''gdisk''' and '''cgdisk''' instead of '''fdisk''' and '''cfdisk'''. There are several other differences in the way GPT partitions work so you'll want to do some research about them before you try using them. Finally, many newer large drives use 4096 byte "Advanced Format" sectors instead of the traditional 512 byte hard drive sectors. Using these disks most efficiently requires adjusting the sector size in software to match the physical sector size on the disk when partitioning and/or formatting.
	# ~~If you~~ are asked what type of partition table to ~~use for the drive select~~ ''dos'' ~~which uses the~~ MBR ~~type~~. Once in ''cfdisk'', Select the ''New'' option. Now select ''~~Primary~~'' as we are making a ~~Primary~~ MBR partition, then set the size close to ''5GB'' (it doesn't need to be exact).		# Because our new drives contain no existing partitions we are asked what type of partition table to create. Choose to create a ''dos'' (aka ''MBR'') style partition table.
	# Using the arrow keys to go down to the remaining ''Free Space'' on the drive, and press enter to again select ''New''. Create another ''~~Primary~~'' partition, and set the size to about ''2GB''.		# Once in ''cfdisk'', Select the ''New'' option. Now select ''primary'' as we are making a primary MBR partition, then set the size close to ''5GB'' (it doesn't need to be exact).
			# Using the arrow keys to go down to the remaining ''Free Space'' on the drive, and press enter to again select ''New''. Create another ''primary'' partition, and set the size to about ''2GB''.
	# At this point we should have two partitions, one named ''sdb1'' with a size of about 5GB (the program will round down to the closest boundary), and ''sdb2'' which takes up the next 2GB or so of the drive. Use the arrow keys to select the ''Write'' option, and press ''enter''. You will be warned that this will write the table to the disk. enter ''yes'', and press ''enter'' again to confirm.		# At this point we should have two partitions, one named ''sdb1'' with a size of about 5GB (the program will round down to the closest boundary), and ''sdb2'' which takes up the next 2GB or so of the drive. Use the arrow keys to select the ''Write'' option, and press ''enter''. You will be warned that this will write the table to the disk. enter ''yes'', and press ''enter'' again to confirm.
	# If, on the bottom of the screen, you see "The partition table has been altered", you have successfully written the MBR to the drive. Now you can navigate to ''Quit'' to exit the program.		# If, on the bottom of the screen, you see "The partition table has been altered", you have successfully written the MBR to the drive. Now you can navigate to ''Quit'' to exit the program.
	# From the command line run ''ls -l /dev ~~\| grep sdb~~''. Notice how you can now see both of the new partitions, ''sdb1'' and ''sdb2'' in the listing. This means the partition device "files" have been created and you are ready to format the partitions with a filesystem.		# From the command line run '''ls -al /dev/sd*'''. Notice how you can now see both of the new partitions, ''sdb1'' and ''sdb2'' in the listing. This means the partition device "files" have been created and you are ready to format the partitions with a filesystem.
	# The first partition will be formatted as ''ext4'', and the second partition will be formatted as ''btrfs''. Both filesystems (as well as many others) are commonly used on Linux systems. For more information on the differences and similarities between ''btrfs'' and ''ext4'', refer to your book or Google.		# The first partition will be formatted as ''ext4'', and the second partition will be formatted as ''btrfs''. Both filesystems (as well as many others) are commonly used on Linux systems. For more information on the differences and similarities between ''btrfs'' and ''ext4'', refer to your book or Google.
	# To create the ''ext4'' partition, we will use the ''mkfs.ext4'' command. So as root, run the command ''mkfs.ext4 /dev/sdb1''. This will partition the drive as ''ext4'' with no label. If you would like to label the partition, look into the options of ''mkfs.ext4'' using ''man mkfs.ext4''.		# To create the ''ext4'' partition, we will use the ''mkfs.ext4'' command. So as root, run the command ''mkfs.ext4 /dev/sdb1''. This will partition the drive as ''ext4'' with no label. If you would like to label the partition, look into the options of ''mkfs.ext4'' using ''man mkfs.ext4''.

BenFranske: /* Disk and File Usage */

2018-03-22T04:04:07Z

Disk and File Usage

← Older revision		Revision as of 04:04, 22 March 2018
Line 75:		Line 75:
	<li> The '''df''' command doesn't give the most easily readable disk or usage sizes by default. Try adding the ''-h'' option to the command like '''df -h''' to change the output to a "human readable" format and see what it looks like.</li>		<li> The '''df''' command doesn't give the most easily readable disk or usage sizes by default. Try adding the ''-h'' option to the command like '''df -h''' to change the output to a "human readable" format and see what it looks like.</li>
	<li> Now, '''cd''' into ''/mnt/part1'' so you are on the ext4 partition you created. Then as root, run the command '''cp -r /var/log ./'''</li>		<li> Now, '''cd''' into ''/mnt/part1'' so you are on the ext4 partition you created. Then as root, run the command '''cp -r /var/log ./'''</li>
	<li> '''cd''' into the ''log'' folder, and run ''du -h''. ''du'' is a command that allows you to view file usage in a tree format. Just like with '''df''' the ''-h'' flag tells '''du''' to output the usage in a "human readable" format, while the ''-a'' flag tells it to show you the results for all files, and not just for folders.</li>		<li> '''cd''' into the ''log'' folder, and run '''du -h'''. '''du''' is a command that allows you to view file usage in a tree format. Just like with '''df''' the ''-h'' flag tells '''du''' to output the usage in a "human readable" format, while the ''-a'' flag tells it to show you the results for all files, and not just for folders.</li>
	<li> Read the '''man du''' page and play around with using the '''du''' command across the file system. How much data is the /etc/ folder taking up on your Linux system? What directories are the biggest?</li>		<li> Read the '''man du''' page and play around with using the '''du''' command across the file system. How much data is the /etc/ folder taking up on your Linux system? What directories are the biggest?</li>
	</ol>		</ol>

BenFranske: /* Disk and File Usage */

2018-03-22T04:03:44Z

Disk and File Usage

← Older revision		Revision as of 04:03, 22 March 2018
Line 74:		Line 74:
	<li> This indicates that the two partitions are mounted properly to the folders we created earlier. ''df'' is a powerful command as not only will it show you what is mounted where, but it also shows you how much disk space is used and how much space is left.</li>		<li> This indicates that the two partitions are mounted properly to the folders we created earlier. ''df'' is a powerful command as not only will it show you what is mounted where, but it also shows you how much disk space is used and how much space is left.</li>
	<li> The '''df''' command doesn't give the most easily readable disk or usage sizes by default. Try adding the ''-h'' option to the command like '''df -h''' to change the output to a "human readable" format and see what it looks like.</li>		<li> The '''df''' command doesn't give the most easily readable disk or usage sizes by default. Try adding the ''-h'' option to the command like '''df -h''' to change the output to a "human readable" format and see what it looks like.</li>
	<li> Now, '''cd''' into ''/mnt/part1'' so you are on the ext4 partition you created. Then as root, run the command ''cp -r /var/log ./''</li>		<li> Now, '''cd''' into ''/mnt/part1'' so you are on the ext4 partition you created. Then as root, run the command '''cp -r /var/log ./'''</li>
	<li> '''cd''' into the ''log'' folder, and run ''du -h''. ''du'' is a command that allows you to view file usage in a tree format. Just like with '''df''' the ''-h'' flag tells '''du''' to output the usage in a "human readable" format, while the ''-a'' flag tells it to show you the results for all files, and not just for folders.</li>		<li> '''cd''' into the ''log'' folder, and run ''du -h''. ''du'' is a command that allows you to view file usage in a tree format. Just like with '''df''' the ''-h'' flag tells '''du''' to output the usage in a "human readable" format, while the ''-a'' flag tells it to show you the results for all files, and not just for folders.</li>
	<li> Read the '''man du''' page and play around with using the '''du''' command across the file system. How much data is the /etc/ folder taking up on your Linux system? What directories are the biggest?</li>		<li> Read the '''man du''' page and play around with using the '''du''' command across the file system. How much data is the /etc/ folder taking up on your Linux system? What directories are the biggest?</li>
	</ol>		</ol>

BenFranske at 04:03, 22 March 2018

2018-03-22T04:03:24Z

Show changes

BenFranske at 17:03, 21 March 2018

2018-03-21T17:03:58Z

BenFranske: /* Adding a 2nd disk */

2018-03-12T03:49:22Z

Adding a 2nd disk

← Older revision		Revision as of 03:49, 12 March 2018
Line 36:		Line 36:
	# To start, run cfdisk /dev/sdb as root. ''cfdisk'' is a graphical version of ''fdisk'', which is a tool used to setup disk partitioning. Note that ''fdisk'' only sets up the MBR, and does not actually format the drive. Also notice how we tell ''cfdisk'' what drive we want to format by appending the drive file to the end of the command.		# To start, run cfdisk /dev/sdb as root. ''cfdisk'' is a graphical version of ''fdisk'', which is a tool used to setup disk partitioning. Note that ''fdisk'' only sets up the MBR, and does not actually format the drive. Also notice how we tell ''cfdisk'' what drive we want to format by appending the drive file to the end of the command.
	#* Note: some very large drives can no longer use MBR partition tables and there are other reasons to switch to the newer standard for partitioning, GPT partition tables. In order to do that you would use different tools such as gdisk and cgdisk instead of fdisk and cfdisk. Note that there are several other differences in the way GPT partitions work so you'll want to do some research about them before you try using them.		#* Note: some very large drives can no longer use MBR partition tables and there are other reasons to switch to the newer standard for partitioning, GPT partition tables. In order to do that you would use different tools such as gdisk and cgdisk instead of fdisk and cfdisk. Note that there are several other differences in the way GPT partitions work so you'll want to do some research about them before you try using them.
	# If you are asked what type of partition table to use for the drive select "dos" which uses the MBR type. Once in ''cfdisk'', Press the New option. Now select Primary as we are making a Primary partition, then for the size set it to ~~6GB~~.		# If you are asked what type of partition table to use for the drive select "dos" which uses the MBR type. Once in ''cfdisk'', Press the New option. Now select Primary as we are making a Primary partition, then for the size set it to 5GB.
	# Now, use the arrow keys to go down to the Free Space, and press enter to Select New. Again, set it to Primary, and set it to ~~3GB~~. Then press Enter.		# Now, use the arrow keys to go down to the Free Space, and press enter to Select New. Again, set it to Primary, and set it to 2GB. Then press Enter.
	# At this point we should have two partitions, one named sdb1 with a size of about 5GB (the program will round down to the closest boundary), and sdb2 which takes up the next ~~3GB~~ or so of the drive. At this point, use the arrow keys to select Write, and press enter. You will be warned that this will write the table to the disk. enter "yes", and press enter to confirm.		# At this point we should have two partitions, one named sdb1 with a size of about 5GB (the program will round down to the closest boundary), and sdb2 which takes up the next 2GB or so of the drive. At this point, use the arrow keys to select Write, and press enter. You will be warned that this will write the table to the disk. enter "yes", and press enter to confirm.
	# If on the bottom you see "The partition table has been altered", then you have successfully written the MBR to the drive. Now you can navigate to quit to exit the program.		# If on the bottom you see "The partition table has been altered", then you have successfully written the MBR to the drive. Now you can navigate to quit to exit the program.
	# Now run ''ls -l /dev \| grep sdb''. Notice how the two partitions, sdb1 and sdb2 show up.		# Now run ''ls -l /dev \| grep sdb''. Notice how the two partitions, sdb1 and sdb2 show up.

BenFranske: /* Adding a 2nd disk */

2017-10-30T22:29:47Z

Adding a 2nd disk

← Older revision		Revision as of 22:29, 30 October 2017
Line 38:		Line 38:
	# If you are asked what type of partition table to use for the drive select "dos" which uses the MBR type. Once in ''cfdisk'', Press the New option. Now select Primary as we are making a Primary partition, then for the size set it to 6GB.		# If you are asked what type of partition table to use for the drive select "dos" which uses the MBR type. Once in ''cfdisk'', Press the New option. Now select Primary as we are making a Primary partition, then for the size set it to 6GB.
	# Now, use the arrow keys to go down to the Free Space, and press enter to Select New. Again, set it to Primary, and set it to 3GB. Then press Enter.		# Now, use the arrow keys to go down to the Free Space, and press enter to Select New. Again, set it to Primary, and set it to 3GB. Then press Enter.
	# At this point we should have two partitions, one named sdb1 with a size of about ~~6GB~~ (the program will round down to the closest boundary), and sdb2 which takes up the next 3GB or so of the drive. At this point, use the arrow keys to select Write, and press enter. You will be warned that this will write the table to the disk. enter "yes", and press enter to confirm.		# At this point we should have two partitions, one named sdb1 with a size of about 5GB (the program will round down to the closest boundary), and sdb2 which takes up the next 3GB or so of the drive. At this point, use the arrow keys to select Write, and press enter. You will be warned that this will write the table to the disk. enter "yes", and press enter to confirm.
	# If on the bottom you see "The partition table has been altered", then you have successfully written the MBR to the drive. Now you can navigate to quit to exit the program.		# If on the bottom you see "The partition table has been altered", then you have successfully written the MBR to the drive. Now you can navigate to quit to exit the program.
	# Now run ''ls -l /dev \| grep sdb''. Notice how the two partitions, sdb1 and sdb2 show up.		# Now run ''ls -l /dev \| grep sdb''. Notice how the two partitions, sdb1 and sdb2 show up.

BenFranske: /* Mounting Partitions */

2016-04-07T02:58:25Z

Mounting Partitions

← Older revision		Revision as of 02:58, 7 April 2016
Line 49:		Line 49:

	== Mounting Partitions ==		== Mounting Partitions ==
	# There are two main ways to mount disks in linux. One is done manually, and the other is to setup mounting at boot.		<ol>
	# To start, we will learn how to manually mount a partition. change into the /mnt directory and then create a folder called part1. Now cd into the part1 folder and create a empty file called unmounted.		<li> There are two main ways to mount disks in linux. One is done manually, and the other is to setup mounting at boot.</li>
	# Now, go back to the mnt directory. We are now going to use the mount command to mount the first partition we created to the part1 folder. To do this, we will run ''mount /dev/sdb1 /mnt/part1'' as root. Now, go back into the part1 folder and list files. Notice how the file you made called unmounted no longer exists. This is because the folder is being used as the mount point for the partition. Now change back to the /mnt folder.		<li> To start, we will learn how to manually mount a partition. change into the /mnt directory and then create a folder called part1. Now cd into the part1 folder and create a empty file called unmounted.</li>
	# To unmount the partition, run the command ''umount /mnt/part1''. Now list the contents of the folder part1 again. Notice how the unmounted file is now back. This is because when a drive is mounted to the file, it overlays on top of any files in the folder, but it does not delete or touch the files.		<li> Now, go back to the mnt directory. We are now going to use the mount command to mount the first partition we created to the part1 folder. To do this, we will run ''mount /dev/sdb1 /mnt/part1'' as root. Now, go back into the part1 folder and list files. Notice how the file you made called unmounted no longer exists. This is because the folder is being used as the mount point for the partition. Now change back to the /mnt folder.</li>
	# Now we are going to make a folder called btrfs in /mnt. Once created, using the file editor of your choice, open up the file /etc/fstab.		<li> To unmount the partition, run the command ''umount /mnt/part1''. Now list the contents of the folder part1 again. Notice how the unmounted file is now back. This is because when a drive is mounted to the file, it overlays on top of any files in the folder, but it does not delete or touch the files.</li>
	# The fstab file is used to tell a linux system what drives and partitions is should mount as boot, as well as mount options and where to mount the partitions. On the bottom of the file, add the following:		<li> Now we are going to make a folder called btrfs in /mnt. Once created, using the file editor of your choice, open up the file /etc/fstab.</li>
			<li> The fstab file is used to tell a linux system what drives and partitions is should mount as boot, as well as mount options and where to mount the partitions. On the bottom of the file, add the following:
	<pre>/dev/sdb1 /mnt/part1 ext4 defaults 0 0		<pre>/dev/sdb1 /mnt/part1 ext4 defaults 0 0
	/dev/sdb2 /mnt/btrfs btrfs defaults 0 0</pre>		/dev/sdb2 /mnt/btrfs btrfs defaults 0 0</pre> </li>
	# Adding these lines will tell the fstab file to mount both partitions at boot to the folders we created. To mount the partitions without rebooting or using the full mount command syntax, we can just run mount -a which will load and mount all partitions in the fstab file.		<li> Adding these lines will tell the fstab file to mount both partitions at boot to the folders we created. To mount the partitions without rebooting or using the full mount command syntax, we can just run mount -a which will load and mount all partitions in the fstab file.</li>

	== Disk and File Usage ==		== Disk and File Usage ==

← Older revision		Revision as of 17:03, 21 March 2018
Line 5:		Line 5:

	== Exploring /proc ==		== Exploring /proc ==
	# ~~To start this lab, go to~~ /proc ~~in putty~~. /proc is a very special folder is its a virtual filesystem. Its sometimes referred to as a process information pseudo-~~file system~~. The reason is that all of the files in /proc are not ~~real~~ files, but runtime and system information.		# Enter the ''/proc'' directory on your VM. ''/proc'' is a very special folder is its a virtual filesystem. Its sometimes referred to as a process information pseudo-filesystem. The reason for calling it a pseudo-file system is that all of the "files" in ''/proc'' are not really files at all, but kernel runtime configuration and system information.
	# For example, ~~now that you are in~~ /proc~~, run cat~~ cpuinfo. Notice how the output tells your information about the CPU that is running the ~~Virtual Machine~~. /proc is used not only to get hardware and ~~runtime~~ information, but it can also be used to tweak kernel settings. Look back on Lab 10 and notice how we echoed a ~~number~~ to a file in /proc to enable packet forwarding.		# For example, use '''cat cpuinfo''' to view the contents of the ''/proc/cpuinfo'' "file". Notice how the output tells your information about the CPU that is running the VM. This isn't actually a file at all you are essentially asking the kernel to provide information about the CPU it's running on which it gathers in realtime. ''/proc'' is used not only to get hardware and kernel information, but it can also be used to tweak kernel settings while the system is running in a way similar to some Windows Registry edits. Look back on Lab 10 and notice how we echoed a "1" to a "file" in ''/proc'' to enable packet forwarding without rebooting the system.
	# There are a few files in /proc you should get to know:		# There are a few files in ''/proc'' you should get to know:
	#* '''/proc/cpuinfo''' = Shows you the CPU info for your machine.		#* '''/proc/cpuinfo''' = Shows you the CPU info for your machine.
	#* '''/proc/modules''' = Shows you the currently enabled kernel modules that are active on your kernel.		#* '''/proc/modules''' = Shows you the currently enabled kernel modules that are active on your kernel.
	#* '''/proc/cmdline''' = Shows you the boot ~~arguements~~ used to boot your kernel.		#* '''/proc/cmdline''' = Shows you the boot arguments used to boot your kernel.
	#* '''/proc/version''' = Shows you your kernel version.		#* '''/proc/version''' = Shows you your kernel version.
	# It is important to note that some of these files have commands tied to them, for example.		# It is important to note that some of these files have commands tied to them that can give you similar information but often formatted in a different way, for example.
	#* '''/proc/modules''' = lsmod		#* '''/proc/modules''' = '''lsmod'''
	#* '''/proc/mounts''' = mount		#* '''/proc/mounts''' = '''mount'''
	#* '''/proc/version''' = uname -a		#* '''/proc/version''' = '''uname -a'''
	# Normally it is best to use the command version to lookup the information as it is normally formatted to be easier to read and understand.		# Normally it is best to use the command version to lookup the information as it is normally formatted to be easier to read and understand.
	# Explore ~~around with~~ these commands and find the differences between the command line and file output versions.		# Explore all of these files and commands and find the differences between the command line and file output versions as well as what types of information are available.
	== Exploring /dev ==		== Exploring /dev ==
	# ~~now change~~ directories to /dev and list the files. Notice ~~that~~ there are ~~ALOT~~, but don't worry there is organization in the mess. Each file, like in /proc, is actually a device or interface on the machine. Here is a list of the most common interfaces you will see:		# Change directories to ''/dev'' and list the "files". Notice there are A LOT, but don't worry, there is organization in the mess. Each "file", like in ''/proc'', is actually a device or interface on the machine so ''/dev'' is actually another pseudo-filesystem. Here is a list of the most common interfaces you will see:
	#* '''/dev/sd*''' = SATA Hard Drives		#* '''/dev/sd*''' = SATA Hard Drives
	#* '''/dev/hd*''' = IDE Hard Drives		#* '''/dev/hd*''' = IDE Hard Drives
Line 27:		Line 27:
	# There are also some commands you should learn that will help you with detecting, and looking up devices:		# There are also some commands you should learn that will help you with detecting, and looking up devices:
	#* '''lsusb''' = List USB Devices (Bus, Device, ID, and advertised vendor)		#* '''lsusb''' = List USB Devices (Bus, Device, ID, and advertised vendor)
	#** Note: Many virtual machines do not include a virtual ~~usb~~ controller which means the ~~usb~~ drivers and software including lsusb are not installed.		#** Note: Many virtual machines do not include a virtual USB controller which means the USB drivers and software including '''lsusb''' are not installed.
	#* '''lspci''' = List PCI Devices (Bus, Type, Advertised Name, Revision)		#* '''lspci''' = List PCI Devices (Bus, Type, Advertised Name, Revision)
	#* '''dmesg''' = Display or Driver Message. This shows kernel messages that are normally linked to adding, or removing devices.		#* '''dmesg''' = Display or Driver Message. This shows kernel messages that are normally linked to adding, or removing devices.