And yes, welcome to our first demonstration.
In this demonstration,
we are going to go through and take a look at
installing our quota tools and the drivers.
So we install quotas and check for our kernel modules or
drivers and install them if required.
So come on, let's go through and find that command line.
Now that didn't take long.
Here they are waiting for us, a glorious command line,
and on our Ubuntu 2004 system.
Now we've got this up and running and this is our vagrant system.
Being a vagrant system,
even though we might not really think of it as being cloud‑based,
based in my shed in my garden, that's hardly a cloud,
mate,
but we can also understand that they want to keep these
images as small as possible so they can be delivered to us
in as quick a time as they can.
So that often means a lot of the standard tools that
might be there might not be there.
So we're going to be checking through and making sure that
we have got the correct kernel modules.
But anyway, let's begin.
We can do our sudo and apt update,
just making sure that we've got our latest version of the
metadata from the app to repositories.
I can clear out my screen so Ctrl+L,
and then we can go through and run sudo and apt install and we'll
give the ‑y just so it goes ahead and does it and then quota and
making sure that we spell quota correctly.
Now with that done,
just hit the big Enter key and this will add in then our quota tools.
So this will be like our user side tools for configuring, or at least
our administrator, configuring our quota systems.
We can go through then and run now our quota and then ‑‑version,
and then of course, we're returning then the version that we've got.
So there you go.
We appear to be up and running and I do emphasize appear,
but if we go through and search for some of our modules,
so find, we can tell find where to look and we're going to look in /lib/modules.
It's here where we're going to find our kernel modules.
We can say that we only need to worry about searching for
regular files so we don't have to worry if it's a directory
or a link or something like that.
We can specify our name as a ‑name,
and then just so we can be a little bit less specific,
we can start using some of our wild cards so we can then go
through and put our star and quota_v with an asterisk after that
and then .ko and then asterisk after that.
We go through and search.
Then as long as we've got the search okay,
then we can see that we don't have the modules in place.
So what we might want to do is go through and install another package.
Let's just go back up and then add in our linux‑image‑extra and virtual.
So this package that's going to have our quota file system drivers,
so we can allow this to chug through.
And so typically, we're going to be looking at these sort of devices,
so this is our vagrant machines, maybe if you're using cloud‑based machines,
maybe Google Cloud, AWS digital option, obviously there are a variety.
Whereas if you've installed from an ISO file something like that,
generally, even the minimal images will have these tools up and running for you.
So we can allow this to run through.
We've got to update some of the information regarding our initialization
RAM file system so what's booted before are our kernel.
Really now we can see is it's generating the new boot disk.
It doesn't take too long, but as I say, I think I've said this before,
when you're watching it on the screen, yeah,
sometimes it is just a little bit like watching a kettle boil and it
always appears to take longer than we think it should,
with any of our Linux commands, we really want to see how long it's taken.
We can preface the command so just before the command,
so starting at our prompt,
we can write time and then space and then the
command and arguments that we want.
At the end of the command, we're then going to see how long it did actually take.
I still don't think it took that long.
I didn't run it with the time, but we can see now we have finished.
I think sometimes it's good to see things happen in real
time rather than cutting too much, unless it really is going to be a long time,
so you get to see the true experience rather than just
saying well it took a long time on my system,
whereas on his system, it only took 10 seconds.
If I go back and repeat that find command,
and don't forget, we can easily go back and run that with exclamation mark and F,
we're pretty much certain the last command that we ran
beginning with F was the find command that we want.
Now when we execute it,
we can see now that we have got the kernel modules in place.
We do need to make sure that they are loaded so we do need to load them,
however,
we could also reboot our system and they would load on the boot. But
for the moment, that's all that we need to worry about so I'm going to
leave it here, and we're going to dive into the rest of the configuration by moving back to our slides.