Open main menu

CDOT Wiki β

Changes

OPS235 Lab 1 - Fedora17

473 bytes added, 12:26, 24 September 2018
no edit summary
[[Category:OPS235]][[Category:OPS235 Labs]]
{{Admon/caution|THIS IS AN OLD VERSION OF THE LAB|'''This is an archived version. Do not use this in your OPS235 course.'''}}
 
=Fedora 17 Installation (on Main Host - f17host)=
<li>If you get a warning with something like "This device may contain data" - it's probably your new hard drive and you can safely use it.</li>
<li>Select '''Create Custom Layout''', we don't want to use the Fedora default setup now.</li>
<li>On your drive you will need at least the following partitions. These may be primary partitions or logical drives. If you have more space than 160GB 250GB available - you can add the extra space in equal parts to /home and /var/lib/libvirt/images</li>
<ul><li>'''20GB''' for '''/''' (i.e. "root")</li>
<li>'''30GB''' for /home</li>
{{Admon/tip |Rusty Issuing Linux commands since ULI101?|To be an effective Linux administrator, you need to become comfortable on issuing Linux commands in a shell, and use resources to quickly learn how to properly formulate Linux commands...<br /><br />You can run the following online tutorials to practice (refresh) issuing Linux commands. These tutorials were designed for another course called "OPS435", but you can still use them for practice. Simply open a shell, SSH into the Matrix server (eg. ssh yourusername@matrix.senecac.on.ca) and run the following commands 4 tutorials (you can copy and pastethese separate pathnames and run like a program):<br /><br />'''/home/ops435/tutorials/tutorial1<br /><br >/home/ops435/tutorials/tutorial2<br /><br />/home/ops435/tutorials/tutorial3<br /><br />/home/ops435/tutorials/vi-tutorial'''<br /><br />You can also refer to the section above called '''Linux Command Online Reference''' to see how use use the following Linux commands to obtain the required information.}}
# To check the network configuration settings obtained from the DHCP server, run the following commands, describing the output in your log book: