When I made that VPN script thing, I did so mostly remotely from the host system on which it would be used, over SSH.
So where I would usually just run a quick ‘what is my ip’ web search to confirm my internet IP, that was not possible when testing the VPN script over SSH. So I made this. I still find it useful so, uh, maybe others will too.
The script also checks your IP with multiple (three) online services. You know, in case one is lying to you, or, uhh… Just… It makes extra sure, okay?
One fateful day, when I’d just got light in my fibre,
An email came my way. Snigger and giggle I did,
When I read what that email did bid,
And the button for trash did I smash.
Then a little while later, another damn mail on the wire!
Taken aback, I thought “ah frack,”
And conceded to put pause to my downloader.
Applying a little gumption,
I decided to heck with this setback!
Downloader now on resumption,
There’ll be no pesky watchers of my SYN-ACK!
Look ma, I done a poetry!
I’ve been playing with the idea of running a standalone Samba server to replace an old NAS device that I’d like to repurpose. So I looked for some Samba best-practice ideas and one of them mentioned the periodic backing up and checking the small database files Samba uses for storing config and running info. I figured I’d automate the task with a script, and here we are.
So, the Windows 10 Creators Update. It’s out, and for the most part it seems good. There’s a lot of new stuff, my personal favourites being the introduction of Game Mode (for better or worse), and the changes to Windows Update which allow you to pause updates. And Storage Sense is worth a mention (basically a smarter, automated disk cleanup). There are niggles too, of course. Chief among them being the introduction of more “suggestions” (read: ads) in different parts of Windows, and a particularly frustrating problem of frame rate issues in games.
So. You already know what’s happening here (probably) because the title is obvious (hopefully). But for the title-skippers in the crowd I’ll lay out the introduction-with-waffle: far too often I find myself having a go at a duck, in an effort to educate myself (again) about good partitioning schemes for new Linux installations (in this case Debian).
I’m tired of doing that, so now we have this post to document my latest preferred partition scheme. Now, when (not if) I’m repeating this Linux/Debian installation exercise in the future, I’ll just have a go at myself.
Have you ever set a GRUB boot password, unwittingly buggering it up with a typo, and then panicked when your rebooting host claimed you were giving it the wrong password so it wouldn’t boot? On an LVM disk system? I have. Just last week, in fact. Wanna know how I fixed it?
Hit the jump, then.
So here’s something that took me an embarrassingly long to time figure out: (Arch) Linux doesn’t like it when you have multiple network configuration utilities set to connect you to a network. In my case, a wireless network. In fact, the same wireless network for both utilities.
I have been wanting to mumble about my experiences testing Linux out on my gaming system for weeks already. And now it’s the last day of August and I don’t want to break the minimum-of-a-post-a-month thing I’ve had going on, so it’s coming at ya all rush-like. Enjoy.