Reading this for the first time: https://www.gnu.org/licenses/gpl.html

I'm trying to wrap my head around how a software developer could actually make a living as a software developer licensing their software under these terms.

@JaredBusch Am grinding my cleric on p99 right now :P.

Playing some www.project1999.com.

@scottalanmiller Greetings.

Continuing the Linux Essentials course from linuxacademy.com

What I want:
Almighty Push!

Using Get-MessageTrace to determine the truthfulness of "I never received the E-mail."

Felicem diem natalem to the main character of what has become my favorite anime: Uzumaki Naruto!

For the most part, I am "facilities" for our suite (IT is downstairs).

Doing the ever-important IT duty of moving furniture in another's office to help them determine the best configuration of their desk.

I tend to laugh at the fact that afterward the various news organizations provide analysis of the debate. In my opinion, if someone watched it, they'll get a good idea of what happened.

Playing some Project1999.

You have not lived until you've listened to Libera. Here is just one example: Time

@scottalanmiller Ah, yes. That would be a more efficient way of doing it. I was too excited from finally gaining some understanding of mount point concepts, I didn't think though the best way to move the data.

@scottalanmiller Excellent! For some reason, I was having a hard time wrapping my head around the fact that /data is it's own filesystem within /.

As a test, I tried this. I unmounted /data, and mounted my VHD onto /home (which contains ./eddie/testFile). I figured this would happen: ./eddie/testFile would vanish, because /home is now representing a completely different physical data location.
Turns out that indeed happened. When I unmounted /home, ./eddie/testFile reappeared, which I expected.

Let's say, I'm in a situation where /home to be a mount point for another disk, and the current data within /home need to be moved to the other disk (for whatever reason). Would this be the likely process?

1. Copy /home to a /tmp or some other holding place.
2. Partition and format the new disk.
3. Mount it on /home.
4. Copy the data from /tmp (keeping the directory structure, so the end result is /home/subdirectories/foo
5. If you wanted to reclaim space on the original drive (since files were initially copied rather than moved), unmount /home, remove /home (since the resultant /home is the directory from the original drive), create a new /home, remount the second disk to this newly created /home.

Edited for terminology: Partition is created, then file system is made (formatting), then mounting happens.

I might need the explain-it-to-me-like-I'm-a-five-year-old answer, but let me know if my understanding is correct.

I'm running a Hyper-V VM of CentOS with two VHDs attached. /dev/sdb is the extra drive. I've used it to practice creating a partition, formatting it, and mounting it to /data.

Is this correct? Any data that is stored within the /data file system is physically stored on /dev/sdb. Even though /data is a subdirectory of /. All other data within / is physically stored on the other drive.

Going through https://mangolassi.it/topic/7825/sam-learning-linux-system-administration/2, and waiting on food to arrive.

@scottalanmiller I actually sent them a message asking if they were a fellow Naruto fan. I suppose I won't get a response.

I have some good times playing this www.project1999.com.