[UC2OFS051] – Ibuxes and Linuxes

So I've been down with the flu for a while. Set me back a bit, but I've tinkered some with Mint on my own. I remain principally not a fan of Linux based systems, but that is purely based on my philosophies and preferences. That doesn't mean I recognize what people value in Linux or why some even prefer it.

However, these past few days have done nothing to help change my mind. I believe I've followed every step correctly and set up a few VMs with different Linux variants (Kali, Mint and Ubuntu, specifically). Kali remains my preference still.

I've spent a bit of time familiarizing myself with Linux in a general sense, recognizing I don't have enough time after my time in bed to do it all thoroughly. I've been stuck at following a couple of the tutorials and activities. To be bluntly honest, I'm not really sure if I'm doing something wrong, or if there's something local that restricts me. For example, I used to run a personal VPN from my laptop to my stationary before, but ever since I moved last summer, that has stopped working. The only difference being that I'm on a new network, wireless instead of wired, and unfortunately I don't have access to the router or permission to log in on it to have a look. So I'm worried that it's simply just my network where I live that is giving me problems. Which is stressful, because the assessment were posted recently. I skimmed through it and will have to figure this out at some point. Perhaps I can find some other place to try with a different network. Though for now, I guess I should put it on hold and give it a night's rest, perhaps a fresh mind will be more apt at tackling it. There's also a few more lectures to go through.

[UC2OFS051] – Windows Servers, Active Directories, Considerations

Setting up the server OS and interacting with the server manager was surprisingly incredibly straightforward and intuitive. A very effective and powerful tool by my first impressions at a glance. I even got a Windows client to join the domain as a member during first try, which was again... Surprising.

Though in reference to the activity sheet, if I were to set up an actual server for an actual company with ~2000 plus clients... I don't know. I assume you wouldn't want an admin user with '1234' as password. So I'd perhaps start off with ensuring that the domain controller machine is up to date with Windows updates, has a decent firewall and antivirus set up and have remote connection capabilities turned off. I'd also rename the Administrator user to something less predictable, and ensure it has a strong password as well.

I'm not sure if Windows has that capability, but preferably by my own personal preference, anyone with Admin permissions should have a Two-Step Verification process of logging in. Whether that's a possible thing or not though - No idea.

I'd probably want computers to have a logical name, by a structured naming convention. Say that the company has a location in Oslo, Kristiansand and Bergen. The different computers could be structured with their hostnames being something like <Region> - <OS> - <Floor><IncrementalNumber>. So, as an example, KRS-Win-a001. So that'd be a Windows computer located in the Kristiansand office, on floor ‘a’ (first floor, first letter in the alphabet).

Other than that, I can't really think of anything much else. I've done some googling, but most of the other tips and best practices are a bit beyond my scope of knowledge and insight into systems yet, so I can't really elaborate further on what, how or why in regards to that.

[UC2OFS051] – Programs, Processes & Files

See, I've always thought of myself as someone that has a fair amount of knowledge and experience with computers. While my sister got a dollhouse and some accessories to play with as a kid, I got a disposable computer which my dad had brought home from Merkantildata as it was called at the time. He figured (I guess, in retrospect) that I'd enjoy tinkering with that as much as any other kid would tinker with Lego. Naturally it was well above and beyond my understanding at the time, but my faint memory still remembers that I was quite fascinated and intrigued by the machine standing in the middle of my bedroom, a half-open cabinet with a few loose cables hanging out.

During the couple of lectures this week, it struck me that I've never actually stopped to think about the exact specifics of how certain things in a computer works (including the software / OS). So while for example going through how processes operate and how their life cycles work, wasn't exactly an unknown abstract to think about, I realized I've never actually thought about it. I've grown up with computers, and have explored them enough to see for myself, and admittedly brick a few OSes or crash a couple of systems from trying things out, but still...

Though, I can't really confidently say I understand the whole Round Robin ordeal with CPU scheduling yet. I think I understand, but perhaps I just missed how you determine what the time quantum is, or if that's a fixed thing (doubt it). Perhaps that's just always determined and declared, I'm just not sure. I tend to overly question these things.


So, for example in the activity task we had, if I understand correctly, due to the linear arrival time, it'd process P1 through P6 with a Quantum of 4. So P1 would process for 4ms and be moved to the back of the queue with 4ms remaining. Then the next three (P2-4) has a Burst Time of 4 or less, so they'd all complete. Then It'd process P5, bring that down to 5ms remaining and put it behind P1 in the queue.

Then, it'd complete P6 which only has a 1ms Burst Time, at the 19th ms of operation time total, then finish up P1 which has 4ms remaining, and then complete P5 a full 4ms burst, then another with the remaining 1ms and complete that as well.

I'm fairly certain I've understood that bit correctly. It's just the Quantum time and how/where to determine that if it isn't declared in an activity like this that confuses me.

Fairly cool and informative start to this course though. Very useful. While familiar in concept, I feel it has helped me be more confident and knowledgeable in how computers actually work.

[UC2OFS051] – Virtual Reflection

Today's tutorial and activities revolved around setting up virtual machines and general hardware choices in computer builds. I've decided to stick with my current VMs, as I have a running VM of Windows 10 and Kali already, with snapshots to revert to for convenient sandboxing. However, for the sake of comparison and trying things out, I've installed Mint as well just in case future tutorials might be Mint-specific in some way.

I've decided to (re)name my systems into a naming convention that makes sense to me, OFS-(OSName), so OFS-Win10, OFS-Kali and OFS-Mint. I don't really understand (yet?) why I need to plan the names of users, or if that implies my accounts, or potential other users on the computer in a server hierarchy or something. So I go with my default username for all systems that are exclusively mine, TheComposer (Or "The Composer" if the username allows spacing).

An update on Chronicles’ work

Over the summer, I began working on a re-iteration of Divine Scaling which is a supplementary dependency for Chronicles of Divinity in order to make balancing and combat design easier in the long run.

Divine Scaling aimed to allow players to scale enemy levels and adjust some parameters to fine-tune the difficulty for themselves. However, it did have flaws and quirks to learn from, which I try to fix in the upcoming Divine Scaling 2 mod.

Once that is functionally 'done', I've got plans of porting over assets from my now rather messy asset collection, and tidy up a bit. Move the usable assets over to a Shared Library which I'll share with the public as well so that they can utilize it as a dependency of their own. That way, we all get more toys to play with, while avoiding to make users have to download a lot of the same assets multiple times, or re-download any time there's an update to the main projects.