Are you sure you want to cancel your subscription?

If you cancel, your subscription will remain active through the paid term. You will be able to reactivate the subscription until that date.

Sorry to see you go

Your subscription will remain active until . If you change your mind, you may rectivate your subscription anytime before that date.

Are you sure you want to reactivate?
Welcome Back!

Your subscription has been reactivated and you will continue to be charged on .

Reactivate Subscription

Thank you for choosing to reactivate your subscription. In order to lock in your previous subscription rate, you owe: .

Your Subscription term is from - .

Questions? Call Sales.

Payment Due:

Auto-Renew Subscription

To auto-renew your subscription you need to select or enter your payment method in "Your Account" under Manage Payments.

Click continue to set up your payments.

CBT Nuggets License Agreement

Unless otherwise stated all references to “training videos” or to “videos” includes both individual videos within a series, entire series, series packages, and streaming subscription access to CBT Nuggets content. All references to CBT or CBT Nuggets shall mean CBT Nuggets LLC, a Delaware limited liability company located at 44 Country Club Road, Ste. 150, Eugene, Oregon.

A CBT Nuggets license is defined as a single user license. Accounts may purchase multiple users, and each user is assigned a single license.

  • GRANT OF LICENSE. CBT Nuggets grants you a non-transferable, non-exclusive license to use the training videos contained in this package or streaming subscription access to CBT content (the “Products”), solely for internal use by your business or for your own personal use. You may not copy, reproduce, reverse engineer, translate, port, modify or make derivative works of the Products without the express consent of CBT. You may not rent, disclose, publish, sell, assign, lease, sublicense, market, or transfer the Products or use them in any manner not expressly authorized by this Agreement without the express consent of CBT. You shall not derive or attempt to derive the source code, source files or structure of all or any portion of the Products by reverse engineering, disassembly, decompilation or any other means. You do not receive any, and CBT Nuggets retains all, ownership rights in the Products. The Products are copyrighted and may not be copied, distributed or reproduced in any form, in whole or in part even if modified or merged with other Products. You shall not alter or remove any copyright notice or proprietary legend contained in or on the Products.
  • TERMINATION OF LICENSE. Once any applicable subscription period has concluded, the license granted by this Agreement shall immediately terminate and you shall have no further right to access, review or use in any manner any CBT Nuggets content. CBT reserves the right to terminate your subscription if, at its sole discretion, CBT believes you are in violation of this Agreement. CBT reserves the right to terminate your subscription if, at its sole discretion, CBT believes you have exceeded reasonable usage. In these events no refund will be made of any amounts previously paid to CBT.
  • DISCLAIMER OF WARRANTY AND LIABILITY. The products are provided to you on an “as is” and “with all faults” basis. You assume the entire risk of loss in using the products. The products are complex and may contain some nonconformities, defects or errors. CBT Nuggets does not warrant that the products will meet your needs, “expectations or intended use,” that operations of the products will be error-free or uninterrupted, or that all nonconformities can or will be corrected. CBT Nuggets makes and user receives no warranty, whether express or implied, and all warranties of merchantability, title, and fitness for any particular purpose are expressly excluded. In no event shall CBT Nuggets be liable to you or any third party for any damages, claim or loss incurred (including, without limitation, compensatory, incidental, indirect, special, consequential or exemplary damages, lost profits, lost sales or business, expenditures, investments, or commitments in connection with any business, loss of any goodwill, or damages resulting from lost data or inability to use data) irrespective of whether CBT Nuggets has been informed of, knew of, or should have known of the likelihood of such damages. This limitation applies to all causes of action in the aggregate including without limitation breach of contract, breach of warranty, negligence, strict liability, misrepresentation, and other torts. In no event shall CBT Nuggets’ liability to you or any third party exceed $100.00.
  • REMEDIES. In the event of any breach of the terms of the Agreement CBT reserves the right to seek and recover damages for such breach, including but not limited to damages for copyright infringement and for unauthorized use of CBT content. CBT also reserves the right to seek and obtain injunctive relief in addition to all other remedies at law or in equity.
  • MISCELLANEOUS. This is the exclusive Agreement between CBT Nuggets and you regarding its subject matter. You may not assign any part of this Agreement without CBT Nuggets’ prior written consent. This Agreement shall be governed by the laws of the State of Oregon and venue of any legal proceeding shall be in Lane County, Oregon. In any proceeding to enforce or interpret this Agreement, the prevailing party shall be entitled to recover from the losing party reasonable attorney fees, costs and expenses incurred by the prevailing party before and at any trial, arbitration, bankruptcy or other proceeding and in any appeal or review. You shall pay any sales tax, use tax, excise, duty or any other form of tax relating to the Products or transactions. If any provision of this Agreement is declared invalid or unenforceable, the remaining provisions of this Agreement shall remain in effect. Any notice to CBT under this Agreement shall be delivered by U.S. certified mail, return receipt requested, or by overnight courier to CBT Nuggets at the following address: 44 Club Rd Suite 150, Eugene, OR 97401 or such other address as CBT may designate.

CBT Nuggets reserves the right, in its sole discretion, to change, modify, add, or remove all or part of the License Agreement at any time, with or without notice.

Billing Agreement

  • By entering into a Billing Agreement with CBT Nuggets, you authorize CBT Nuggets to use automatic billing and to charge your credit card on a recurring basis.
  • You agree to pay subscription charges on a monthly basis, under the following terms and conditions:
    • CBT Nuggets will periodically charge your credit card each monthly billing cycle as your subscription charges become due;
    • All payments are non-refundable and charges made to the credit card under this agreement will constitute in effect a "sales receipt" and confirmation that services were rendered and received;
    • To terminate the recurring billing process and/or arrange for an alternative method of payment, you must notify CBT Nuggets at least 24 hours prior to the end of the monthly billing cycle;
    • You will not dispute CBT Nugget’s recurring billing charges with your credit card issuer so long as the amount in question was for periods prior to the receipt and acknowledgement of a written request to cancel your account or cancel individual licenses on your account.
  • You guarantee and warrant that you are the legal cardholder for the credit card associated with the account, and that you are legally authorized to enter into this recurring billing agreement.
  • You agree to indemnify, defend and hold CBT Nuggets harmless, against any liability pursuant to this authorization.
  • You agree that CBT Nuggets is not obligated to verify or confirm the amount for the purpose of processing these types of payments. You acknowledge and agree that Recurring Payments may be variable and scheduled to occur at certain times.
  • If your payment requires a currency conversion by us, the amount of the currency conversion fee will be determined at the time of your payment. You acknowledge that the exchange rate determined at the time of each payment transaction will differ and you agree to the future execution of payments being based on fluctuating exchange rates.

CBT Nuggets reserves the right, in its sole discretion, to change, modify, add, or remove all or part of the Billing Agreement at any time, with or without notice.

LPI Linux LPIC-1 101 and CompTIA Linux+

Design Hard Disk Layout

This video is only available to subscribers.
Start your 7-day free trial today.

A free trial includes:

  • Unlimited 24/7 access to our entire IT training video library.
  • Ability to train on the go with our mobile website and iOS/Android apps.
  • Note-taking, bookmarking, speed control, and closed captioning features.

LPIC1 & CompTIA Linux+ Intro

Hardware Settings

Boot the System

Change Runlevels and Reboot or Shutdown the System

Design Hard Disk Layout

00:00:00 - Okay welcome to section 102.1, sounds like a radio station. But
00:00:05 - no this section is hard drive layout. We're going to learn
00:00:08 - all about partitioning and disks. What that means and, and why
00:00:12 - we would want to do it. We're going to learn about different file
00:00:15 - systems, there can be local file systems or network file systems.
00:00:18 - We're going to learn about mount points, that's mount points
00:00:21 - on your Linux system. We're going to learn what swap space is.
00:00:25 - Why we would want it, where we would put it. And then we're going
00:00:27 - to learn about design considerations for different types of
00:00:31 - Linux installs, I mean like for a desktop or for a server or you
00:00:35 - know, that kind of thing. So we're going to look at all
00:00:37 - these things and the first thing we are going to look at is
00:00:41 - going to be what it, what I'm talking about by file systems
00:00:44 - and mount points and all that kind of stuff. So let's look at a computer.
00:00:50 - Alright, so here we have our Linux system, we're on Ubuntu
00:00:53 - here now. And what I want to show you is the computer. So let's
00:00:56 - look at a computer. Now how it's set up, basically is just
00:01:01 - a file system and everything looks as though it's one continuous
00:01:04 - file system. For example there's, there's a couple special folders
00:01:08 - here like the boot folder which is going to contain all the information
00:01:11 - about kernels and stuff, which we talked about before. And see
00:01:14 - it just shows up as a folder here inside the root directory which
00:01:18 - is slash. If you will, just a slash or forward slash
00:01:22 - is the root directory. And these are all the folders underneath. Now there
00:01:25 - are some things, some special ones like home you'll see user
00:01:28 - spowers. That's my account right there. The etc folder is
00:01:32 - where configurations are stored, the root folder is the
00:01:37 - root user account stored there, that's like a home folder
00:01:40 - just for the root user and then var is a folder, come on, open
00:01:45 - up. This has a bunch of different things inside, this is where
00:01:49 - a lot of times your web server will run from, this is almost
00:01:52 - always where log files are kept in var log surprisingly enough
00:01:57 - actually not surprising, that's where you'd expect it to be.
00:01:59 - But it's just this hierarchy of files and it starts at the root
00:02:03 - level right here which is root or slash; its forward slash
00:02:07 - called root. Not to be confused with this folder because this
00:02:11 - folder is, yeah I don't have, I'm not the root user so I can't look inside
00:02:15 - because
00:02:16 - r-o-o-t is the root users home directory and the
00:02:22 - reason that it's there is because a lot of times the home directory
00:02:25 - isn't saved on the local computer. A lot of times this will be
00:02:29 - a network device.
00:02:31 - And the root user needs to log in even if there is something
00:02:34 - wrong with the home, with the home folder. So let's talk about what
00:02:37 - it looks like. See here they all just look like one big folder
00:02:40 - scheme but in reality these can be mounted on several different
00:02:43 - hard drives some of them can be network mounted and we're going
00:02:46 - to talk about the best way to design a system so that it runs
00:02:50 - the most efficiently because that's really what this section
00:02:52 - is about; how to design disk partitions and mounts so that they work
00:02:56 - best for a Linux system. So let's go a little bit, let's get a little
00:03:00 - bit of background on how partitioning a hard drive actually works.
00:03:06 - Alright, let's start with a basic system. Now a basic,
00:03:10 - just put it up here, basic desktop machine we'll say, okay.
00:03:16 - For a basic desktop machine you're going to have just a few
00:03:19 - partitions. You're going to have the root partition, now
00:03:23 - this is not to be confused with
00:03:26 - the root partition. Remember we talked about that, that's not what I'm talking
00:03:29 - about here, okay. I'm talking about just this forward slash, the
00:03:33 - root, the, the start of the entire file system format, okay. And this
00:03:38 - is going to be in, in a basic desktop system, it's going
00:03:42 - to probably be the biggest, okay. The majority of your drive
00:03:47 - is going to be there and then you'll have the boot partition.
00:03:51 - This is probably going to be, now hard drives are getting bigger
00:03:54 - but a hundred megabytes
00:03:57 - to, depending on how many kernel versions you want to keep,
00:04:01 - maybe a little bit bigger. But generally a hundred megabytes
00:04:04 - is a pretty good size for the boot partition because that's
00:04:07 - going to give you, you know enough size to keep a couple
00:04:10 - kernel revisions in the boot directory. And the boot directory
00:04:13 - again, just pretty much has kernels in it and some grub configuration and
00:04:16 - that's it. The reason this is going to be separate and
00:04:19 - it's not just going to be a folder inside the root directory
00:04:22 - is let's say,
00:04:24 - well first of all some older Linux distributions won't
00:04:28 - support really big file systems as the boot directory. So say
00:04:33 - this is a terabyte drive, well if you just make boot a folder
00:04:36 - inside the root directory, it's not going to be able to see it, okay. So
00:04:40 - it's a good practice to make boot this folder a separate small
00:04:45 - partition on the hard drive. Generally with modern distributions
00:04:48 - it's not necessary and a lot of distributions like Ubuntu, they
00:04:51 - don't make this a separate partition. But it's important to
00:04:54 - know why you'd want to do that. Is that older distributions
00:04:57 - couldn't handle the large drive support, so they wouldn't
00:05:02 - require this initial partition to be very small. This would also have
00:05:05 - to be the first partition on the hard drive. So you have root,
00:05:08 - you have boot and then generally now it's, it's not really
00:05:13 - a mounted there in the file system, so you know maybe we will
00:05:17 - just do away with this slash in the beginning but it's
00:05:20 - swap file and what swap file is, it's generally. Let's
00:05:25 - say you have a gigabyte of memory like actual RAM, the swap
00:05:28 - file is going to be one to maybe two times the RAM. Hold on, the RAM.
00:05:39 - So if you have like two gigs of RAM, maybe you want a four gig
00:05:43 - swap partition and what happens is when the, the physical
00:05:47 - memory is filled up it starts putting some of the, of the current
00:05:51 - memory space on to the hard drive. It's a lot slower than
00:05:54 - memory, but that way computer programs don't crash, okay. This
00:05:57 - is just a paging file, if you're familiar with Windows.
00:06:01 - It's just a swap file, it's what it's called in Linux. In general they
00:06:04 - don't hurt to have them big, better a little bit too
00:06:07 - big than too small and with modern hardrives being so big you can afford
00:06:10 - to make this a little bit bigger than normal. And this is generally
00:06:15 - what you see on a basic desktop machine, okay, this set up right
00:06:19 - here. And
00:06:21 - for most intents and purposes this works. In fact sometimes
00:06:23 - you don't even see this boot partition anymore, you just see a root
00:06:26 - and some swap and that's it. So if you install Ubuntu for example
00:06:30 - today, you're just going to have the root partition and the
00:06:32 - swap partition, alright. So that is what the basic desktop machine
00:06:36 - is going to look like but there are some reasons that you would want
00:06:39 - to split that up a little bit more and that's what we're going
00:06:41 - to move to. We're going to talk to, talk about possibly something
00:06:46 - in a network environment. So let's move to there.
00:06:49 - Okay, so on a network work station, this is where like you're at a
00:06:52 - school or a business and there are some common things that are going
00:06:55 - to be shared. So that no matter what computer you go to generally
00:06:58 - people can log into multiple computers. There's probably going
00:07:00 - to be a local hard drive and the root partition is going
00:07:04 - to be on that local hard drive. Again usually we're talking
00:07:07 - about the majority of the time. There's going to be possibly
00:07:12 - the boot directory.
00:07:13 - Again modern distributions not always but, this is the folder
00:07:18 - or the mounted file system in a separate partition. There
00:07:21 - is going to be a boot location and whether it's a separate
00:07:24 - partition or not, you know it, it depends. And it really doesn't
00:07:27 - matter with modern hardware and, and modern Linux distributions.
00:07:31 - The thing that changes a little bit here is we may have
00:07:35 - the home directory. Now this may be on a file server that is
00:07:40 - NFS. I think it's possible to mount an individual
00:07:45 - user home directory over
00:07:47 - Windows or Samba, SMB, which isn't quite as common.
00:07:52 - You can, I've even seen some people mount this over SSH,
00:07:56 - but generally in a Linux environment NFS is going
00:08:00 - to be one of the most common ways that you're going to mount
00:08:03 - this home directory from a central file server. The advantage
00:08:08 - of that is everybody's home directory is going to be here. So
00:08:11 - you're going to see, home slash spowers. You're going to see home
00:08:19 - slash santa, you are going to see all these different folders inside home
00:08:24 - and no matter where the person sits, they can get access to
00:08:27 - their files. So, so that's one of the advantages of a centrally
00:08:30 - located home server or home, homed file system mounted
00:08:35 - over the network. And this is the kind of thing you're going
00:08:37 - to want the server that is storing all these to be really really
00:08:41 - fast because your home directory gets written to a lot every time you save documents,
00:08:45 - every time you save configurations it's getting, being read from
00:08:49 - and written to very often. So you want this to be a really
00:08:52 - fast hardware, really fast network and that will give you the
00:08:56 - best performance. But that's one of the, the differences
00:09:00 - if you have a network work station. We're going to look at
00:09:04 - you know a centrally mounted home directory. The other directories
00:09:07 - are going to be pretty much the same there, you're going to want to have
00:09:09 - that local swap space in case you run out of RAM and this is
00:09:13 - just a partition but it's not necessarily mounted in the file
00:09:16 - system. So it's just we need to remember that we're going to
00:09:18 - have this swap location on the hard drive. And then we'll move to
00:09:23 - one more.
00:09:24 - So we'll say for example we have a server. Now a server is going to have
00:09:28 - still that root directory, it's going to be mounted on probably a local
00:09:31 - hard drive. We're going to have possibly
00:09:35 - the home directory mounted from somewhere else or possibly
00:09:38 - it's not going to be a separate mount. Possibly this is
00:09:43 - either just on the root directory or possibly the home directory
00:09:48 - that we have here is on its own partition that's really fast
00:09:51 - like on something with, with RAID or you know something that's
00:09:54 - just really fast, alright and it serves it out. We're also, let's, if it's
00:09:58 - a web server we may have the var directory on its own partition
00:10:03 - or own hard drive system. The reason being because this gets
00:10:07 - written to a lot. Again, this is very volatile changing all the
00:10:10 - time with log files, web files database things being written
00:10:14 - to constantly. This is going to be something that gets a lot
00:10:17 - of use and it's, it's nice to have it separated sometimes
00:10:22 - from the rest of your computer, you know. So you're going want that
00:10:25 - separate so you could move it if your server gets moved or
00:10:28 - you know you could erase everything without, without damaging
00:10:31 - things in the home directory or the root directory. And var
00:10:34 - is one of those things it's nice to have separated out. And
00:10:37 - for the most part the user directory nowadays is stored on
00:10:42 - just the root directory. But if this is something you can have
00:10:44 - this on a slower drive because again it doesn't get written
00:10:47 - to very often. Sometimes you want to have this mounted
00:10:51 - from a network in a read only fashion. Now the advantage there
00:10:55 - is let's say you have a bunch of servers doing the same thing,
00:10:58 - well you can give them all the same user directory and they
00:11:01 - have all the same things like user bin, we'll say the apache
00:11:07 - web server. Okay and they all have the same versions and since you don't
00:11:10 - write to the binary files you just read them, they can be read
00:11:13 - only, everybody can be updated in one fell swoop. You don't
00:11:17 - see that as much anymore because speed of networks and
00:11:21 - hard drives have increased so much, but it's important to know
00:11:23 - that that's something that is possible to do, mount the
00:11:26 - user directory read only. So that's how it's mounted on to
00:11:31 - our, our file system here. It can be either;
00:11:35 - it could just be a folder inside your root directory in a partition
00:11:39 - or it could be a folder that mounts from something remotely. It could
00:11:43 - be separate partitions and I want to show you a picture not
00:11:46 - because I'm, I'm great at drawing, but I want to show you a picture
00:11:51 - of what it would look like if we partitioned our hard drive out,
00:11:54 - just to help give you a visual. So here's our hard drive, now the square.
00:11:58 - Now you know inside a hard drive there's like a big spinning disk but
00:12:00 - I just want to use this kind of like a pie chart that's square,
00:12:03 - we'll call it a brownie chart because it's square.
00:12:07 - So, if we have a separate boot partition which isn't necessary
00:12:11 - usually anymore, but it's still commonly used in a lot of distributions.
00:12:14 - It needs to be the very first partition on our drive. So we are going to chop
00:12:18 - off a little bit here, again this is going to be like a hundred
00:12:20 - megabytes.
00:12:22 - Then we're going to take the next section, this is just
00:12:25 - a desktop work station. We are going to just, wow that was a horrible
00:12:30 - line. We're going to cut off about this much of it, that wasn't much
00:12:34 - better, and this whole thing is going to be our root directory.
00:12:39 - Right. This is going to be the root directory and inside of
00:12:43 - this is going to be you know, home.
00:12:47 - And it's going to be you know var, all those things are going
00:12:50 - to live inside on this same partition. And then we're going to
00:12:53 - make this partition, again every computer should have,
00:12:58 - I just want to make it look a little different than the others. This is going to be
00:13:02 - Swap. Just virtual memory for if the computer runs out of,
00:13:07 - of usable memory space, okay; and that's going to be just your
00:13:10 - basic desktop machine. Now if this is a server, we'll do a couple
00:13:15 - things. I erased a little bit too far there, but what we can do is we have
00:13:20 - all these partitions, right. So we still want to have the swap space.
00:13:23 - We still want to have a boot partition but we could chop this
00:13:26 - in half and say this is going to be home.
00:13:31 - And this is going to be the root directory. Or we could chop it further
00:13:37 - and say
00:13:38 - this is the root directory and maybe this is now the var
00:13:44 - directory, see? So we can chop up a hard drive into these
00:13:48 - different things but from the user perspective it's always
00:13:51 - just going to be a file system hierarchy and it looks, they're
00:13:55 - all just going to look like folders mounted on the thing which
00:13:57 - is, it's, it's kind of nice because it is, it's transparent from
00:14:00 - the server standpoint. The server and the applications running
00:14:03 - don't really have any idea how or what type of file system is mounted
00:14:07 - there, they just know that the home directory is where
00:14:10 - users' files are stored. So that's really convenient.
00:14:13 - Now another thing you can do. You can have separate partitions or you can have
00:14:16 - separate hard drives. So let's say this is another hard drive,
00:14:20 - maybe we want to put home on this hard drive.
00:14:23 - Okay, we don't want this to be home anymore.
00:14:26 - Okay, so then a whole other hard drive could be home and then
00:14:29 - we could you know, say this is plugged into our computer over
00:14:33 - here. I really shouldn't be allowed to draw computers,
00:14:36 - but we'll say that's a computer. Let's say we want to take
00:14:39 - the home directory and put it on to a new faster server. We
00:14:42 - just disconnect it from this one and plug it into another computer
00:14:46 - and say here's my home directory and all of the user files have
00:14:49 - been restored on the new server. So it's really convenient,
00:14:52 - Linux is very flexible in how you design things and
00:14:57 - basically now you understand all of the different types of
00:15:00 - file systems that you can mount. You can mount them over the network,
00:15:03 - you can mount them locally, you can mount them on separate hard drives and
00:15:07 - you might understand, hopefully you understand, some of the advantages
00:15:10 - of mounting in different partitions or different drives and how
00:15:13 - you'd want to design that for different purposes. Again Linux is very
00:15:16 - flexible, but a good design in the first place makes
00:15:20 - it a lot easier later to move things like my home file,
00:15:24 - my home directory example so you can move it to another server.
00:15:27 - It's very, very nice. So what do we have? We have, we talked about
00:15:31 - the boot directory, right, and that's going to be about a hundred
00:15:35 - megabytes or a little bit bigger doesn't really matter but
00:15:38 - this has to be on a local hard drive because it's the first
00:15:42 - thing that the computer's going to look at. Now, I said you
00:15:45 - know some older computers can't handle like a, this just being
00:15:48 - a folder on the root partition of a big hard drive. But
00:15:52 - also let's say you're running software RAID on your local computer,
00:15:56 - well you can, it can't read the boot partition off software RAID because
00:15:59 - the kernel has to be loaded in order to recognize that. So, in,
00:16:03 - in a case of like software RAID or some really bizarre drive
00:16:08 - controller, you're going to want to have the boot partition
00:16:11 - separate on a hard drive that bios can recognize with all that kernel
00:16:16 - stuff right in there. So that's why it's really, it's good practice to
00:16:18 - have this, a separate partition or even a separate hard drive
00:16:21 - I suppose if all you have is other RAID stuff. Then we have
00:16:25 - home. I'm just going to go over this really quick because we went over it all already.
00:16:28 - This is where user files are stored, we have var, this is where
00:16:32 - we have log files stored, databases usually store their
00:16:36 - stuff in here, our web server files are often in there and it's
00:16:39 - nice to have this separate on a server so if it fills up, because
00:16:43 - again you can get like gigabytes a day written just from web server
00:16:46 - logs. If it fills up it doesn't stop people from saving their
00:16:50 - documents in a separate partition. Because if this partition
00:16:52 - fills up, sure bad stuff is going to happen. But there's
00:16:55 - still room in the home partition. So people can save their
00:16:58 - work and that kind of thing. So that's a really nice reason to have
00:17:00 - that separate.
00:17:02 - There's a couple other partitions, again the root partition we
00:17:04 - talked about which is going to be on in summer, it has to. It's
00:17:07 - kind of like everything's underneath the root file, file system.
00:17:11 - Some we didn't talk about but are commonly seen, the opt directory
00:17:16 - or the opt partition or just the opt folder, in amongst or that's underneath
00:17:19 - root. This is where a lot of third party stuff goes if
00:17:22 - you get a program that's binary only or you know something that's not
00:17:26 - in your repositories. A lot of times it will put its stuff in this opt directory.
00:17:31 - We talked about User.
00:17:35 - That's where a lot of the binary programs like Apache or you know
00:17:39 - just ls or CD all those commands that generally aren't written
00:17:43 - to very often, only during updates but are read from a lot, they
00:17:45 - live in the user directory. And that looks to be about most of the stuff
00:17:51 - and then of course, SWAP which we don't ever want to forget
00:17:55 - because it's nice to have that virtual memory in case you use
00:17:58 - up all of your actual RAM.
00:18:01 - Alright, so make sure we have everything covered, we have partitions
00:18:04 - and disks, we talked about that. You can partition one hard drive
00:18:07 - into several partitions to separate things out or you can put them
00:18:10 - all together and just have them be folders in the root directory and
00:18:13 - you can also take separate disks and add them to a computer
00:18:17 - and mount them as separate file systems to separate things up
00:18:19 - for, for upgrade purposes or for transferring to another server.
00:18:22 - File systems, they can be local file systems, they can be remote
00:18:27 - network file systems or they can be file systems like swap
00:18:30 - that isn't really a file system, it's more of just an area
00:18:33 - that the computer users for virtual memory. Mount points, now
00:18:37 - again mount points it's important to realize that Linux mounts
00:18:40 - file systems on folders in your hierarchy. So we have
00:18:45 - the root directory and home right. Now home is a folder on the
00:18:49 - root directory. You can mount another file system on there or
00:18:53 - you can just allow it to live in the root directory and just
00:18:55 - be a folder that gets filled with files. But you can't mount a remote file
00:18:59 - system or a separate partition or a network file system on
00:19:03 - a folder if there's stuff in it, right. So it has to be an
00:19:07 - empty folder, like home has to be empty before you can mount another
00:19:10 - file system on to it. Swap space we talked about is just virtual
00:19:14 - memory that's on a local hard drive. There are some cases
00:19:17 - you can do it on the network but not very often. And then we
00:19:20 - talked about when some situations you would want to, you would want
00:19:25 - to have different configurations, like a desktop computer
00:19:28 - will be
00:19:29 - partitioned off and, and formatted slightly different than like a network
00:19:33 - work, work station which is different than a server configuration.
00:19:37 - Because, they just, they need different needs because there have, they
00:19:40 - serve different tasks etcetera, etcetera. So anyway, that is how to
00:19:44 - determine how to layout your hard disk. We're going to talk
00:19:46 - about actually mounting and manipulating file systems later
00:19:49 - on but you need to understand what each type of partition and
00:19:52 - what each special folder is for and, and so you can help plan
00:19:56 - out those hard drive and network mounts on your new system.
00:20:01 - Okay, I hope that this has been informative for you and I'd like
00:20:04 - to thank you for viewing.

Install a Boot Manager

Manage Shared Libraries

Debian Package Management

RPM & YUM Package Management

Work on the Command Line

Process Text Streams Using Filters

Perform Basic File Management

Use Streams, Pipes, and Redirects

Create, Monitor, and Kill Processes

Process Priorities

Search Text Files with Regular Expressions

Perform Basic File Editing Operations Using vi

Create Partitions and Filesystems

Maintain the Integrity of Filesystems

Control Mounting and Unmounting of Filesystems

Manage Disk Quotas

Manage File Permissions and Ownership

Create and Change Hard and Symbolic Links

Find System Files and Place Files in the Correct Location

This forum is for community use – trainers will not participate in conversations. Share your thoughts on training content and engage with other members of the CBT Nuggets community. For customer service questions, please contact our support team. The views expressed in comments reflect those of the author and not of CBT Nuggets. We reserve the right to remove comments that do not adhere to our community standards.

comments powered by Disqus
Community Standards

We encourage you to share your wisdom, opinions, and questions with the CBT Nuggets community. To keep things civil, we have established the following policy.

We reserve the right not to post comments that:
contain obscene, indecent, or profane language; contain threats or defamatory statements; contain personal attacks; contain hate speech directed at race, color, sex, sexual orientation, national origin, ethnicity, age, religion, or disability; contributes to a hostile atmosphere; or promotes or endorses services or products. Non-commercial links, if relevant to the topic, are acceptable. Comments are not moderated, however, all comments will automatically be filtered for content that might violate our comment policies. If your comment is flagged by our filter, it will not be published.

We will be continually monitoring published comments and any content that violates our policies will be removed. Users who repeatedly violate our comments policy may be prohibited from commenting.

Course Features

Speed Control

Play videos at a faster or slower pace.


Pick up where you left off watching a video.


Jot down information to refer back to at a later time.

Closed Captions

Follow what the trainers are saying with ease.

MP3 Downloads

Listen to videos anytime, anywhere

Annual Course Features

Transcender Practice Exams

These practice tests help you review your knowledge and prepare you for exams.
Available only with the annual subscription.
Shawn Powers

Shawn Powers

CBT Nuggets Trainer

LPIC-1; CompTIA Linux+, A+; Cisco CCNA

Area Of Expertise:

Add training to a playlist
or create a new list
Add to current playlist
or add to an existing list
Add to new playlist
Add New Bookmark

Design Hard Disk Layout
Bookmark Title:

Login is required to access this feature.

Your browser cannot access Virtual Labs
Video Options

This advanced buffering is applied to all streams regardless if you installed the doublespeed control or not. Sometimes the advanced buffering causes the video to hang or behave erratically. If you are experienceing issues with video playback please disable the doublespeed buffer.

Remember to re-enable the buffer if you want to use the doublespeed control.

If you are experiencing problems with our content delivery, please click here to switch to our alternate content delivery network or go to our network FAQ.
For other common video playback issues, including firewall and corporate network issues, please visit our Tech Support forum.