Aura V. @auravulpes@computerfairi.es

Me: I'm gonna paint my nails!

Friend: Hi, I come bringing memes.

Me: *is sitting here 20 minutes later, with the nails on only one hand painted*

This is my life. Ah, well 🤷

What remains is a lot of installing programs, setting up programs, making sure everything works, and faffing about with Wine to get some assorted programs running. But, that can wait. For now, it's almost time for bed

Meanwhile, in "Kat continues to install Arch", my system is now to a nice, lovely base point. I've got i3 set up pretty nicely (using an old config of mine, so I do need to make some changes), I've got a basic assortment of stuff set up including discord and firefox, and I even have the ability to type äç©éñtêð (accented) characters! (And, incidentally, not keep typing spaces after quotation marks.) Woo!

Things that I consider NSFW: Genitalia, depictions of penetrative sex even where genitalia are not depicted

Things I do not consider NSFW: tits

This brought to you by: the fact an image with naked tits isn't in an nsfw subfolder of a cool art folder I have

*demonic entity voice* "Yes, I am a hongry boi, now FEEED ME"

I especially love it when it's night and a cop has got his fuckin' lights on despite the fact that he's in a parking lot. Those light are really fuckin' helping, bastard.

I love when a horribly painful migraine comes on whilst I'm out of the house. Love it.

Ugh.

Heh. Arch as a "problem-free break". Leave it to me to use one of the hardest Linux distros as an easy break from FreeBSD. I mean, what would others use? Fedora? Manjaro? Meanwhile, here I am, still setting everything up from scratch and trying to get back to a working system.

Oh, Kat. Kat, Kat, Kat. Whatever will we do with you?

And when I say "FreeBSD is difficult" I mean, I've had this Arch system for less than two hours and I've already got sound, video, easily mountable removable media, etc, etc. It took me two hours alone just to get to a graphical environment with FreeBSD, lots more time to get sound then to get sound to stop being so crackly, and I never got removable media up and running. So, much like when I used to use Windows as a problem-free break from Linux, I'm now doing the same with Arch and FreeBSD

I know, I know. "Kat, what are you doing back on Arch? I thought you liked FreeBSD?" I do. I really do. But FreeBSD is difficult, and I need a working UNIX-like system here shortly to be able to write LaTeX files. I could try to get FreeBSD working again, but I don't have that sort of time. So, I'll go with what I know well: Arch. Sure, I have to deal with all of the GNU Project's shit, but I kinda had to on FreeBSD anyways, so what was really lost?

Hi from my new Arch install!

It turns out, Arch isn't that hard to install, once you remember to fuckin' reformat your drive as GPT rather than accidentally installing on the extant MBR! Encrypted and everything!

I've even got sound!

Today, I was reminded that Windows filenames are case insensitive. I had a file named "pachli" and a folder named "Pachli" in the same directory, and Windows was throwing fits over it. Thankfully, it let me rename one, though, I tried to rename the folder and it renamed the file. But, that's one less thing to fix from a live CD, so 🤷

It's at this moment I'd like to give a huge shoutout to my past self. THANK YOU for actually bothering to copy your bitlocker recovery key to a flash drive. Without you, I'd have lost almost everything. I owe ya one, Kat

My best shot at fixing this was through a Linux VM in virtualbox, but Virtualbox has decided to be a stupid little bitch as well and won't let me open up any virtual machines.

...

I wonder if VMWare would work...
Or maybe QEMU?
Gods, something has to work without me having to reboot into a linux live cd for these four stupid filenames

I want to shoot whoever at microsoft decided to make it impossible to deal with a filename with a colon in it. I current have FOUR that I can't do anything about other than to boot into a Linux live CD because literally everything (yes, even the WSL) fails to do anything. Powershell, cmd, WSL, a tool specifically for removing special characters from file names. Everything I've tried has ended in errors.

Windows, this is why I'm leaving you, you stupid little bitch.

OH, SHIT. "sext" is a word I could make. Granted, it would be pronounced /sext/ and not /sekst/, still. Hehehe...

Seriously, like, I didn't expect that these kinds of words could be made. I got these from the output of gen (http://www.zompist.com/gen.html) and found them quite amusing