Born2beroot

by bhagenlo

written for version 1

My God. Am I sorry for you that you have to do this. But anyway, let's start.

Depending on your previous knowledge, you're likely to feel quite lost after reading the subject for the first time. Well, unfortunately, that is how many of us felt.

And it might be because the subject barely mentions reasons for doing particular things, or because you'd have to google every single bullet point mentioned in the subject for solving it 'properly' on your own.

In my view, there are two sensible ways to approach this project. You either:

Read a lot about Linux, its file system structure, how the OS works, and please, ask at least some knowledgeable people whenever you feel stuck. This is a lot, and it takes some time to finally know what all this is doing.
It's so much I'd even advise you to create Anki Flashcards on the way.

or:

Get yourself some walkthrough that works, as well as an extensive (self-written) 'cheat sheet' for your eval, so that you at least can accomplish what you're asked to do.

#Prerequisites

In my opinion, there shouldn't be any things you should know before diving right into an introductory project like that, but sadly, there are.

If you're going for 1., it might be a good idea to read chapters 2.-10. of Unix and Internet Fundamentals. Otherwise (2.), go find yourself some walkthrough online ;)

Either way:

Make sure you make the VM very small (about 4 Gb) or install it into the ~/goinfre-folder.

If you don't, your system easily runs out of available memory, and you probably don't want that.

#During

If you're thinking without writing, you only think you're thinking.

Leslie Lamport

How much you learn here depends almost completely on you. As the subject doesn't really provide the time for deep understanding, some tips on how to get the most out of it:

Jot down concepts you didn't know about before.
Link them with your concrete encounters with them. (These may be the specific commands you typed, but also the folders stuff related to them gets stored in, the files you changed accordingly, or even only the name of the tool you installed for using that concept.)

#Cleaning Up

Can you access your VM via ssh?
Does your monitoring.sh work?
Find out what exactly a snapshot is, and how it differs from a clone
Create a snapshot or clone of your VM

#Aftercare

Time for some reflection on this project, as I think this should at least be mentioned. You did some stuff, but how much of it makes some actual sense?

Should we change our passwords regularly?

And some answers:

Seems like no: An xkcd for your general intuition – but also more serious sources discourage it.

#Pointers

← libft

Found something to improve? Edit this page on Github!

ft_printf →