Not a single cover by Roger Dean? WTF?

Morrowind.

Ages ago I got a new video card that came with bundled games, including the slightly-old Morrowind.

That was the intro for me to deep RPGs, and I fell hard.

A few weeks ago I decided to revisit it, and went with Open-MW and a vanilla experience.

So awesome.

As Falls Wichita, So Falls Wichita Falls

Amazing, interesting, and relaxing jazz. You can thank me later.

I didn’t know about this. I haven’t followed Proton closely for a while, but this…wow. Kinda lousy.

Wow!

Of all companies, this is one I didn’t expect.

Damn.

China doesn’t need the USA.

The USA needs China.

Your attack was weak, unfocused!

Much like the Gnome user experience! :-D

I don’t say much about it because it’s stupid to argue, but I’ve used a LOT of different desktop interfaces over the past 45+ years (yeah, really!), and GNOME…well, GNOME sucks. When Gnome3 was first released we all had high hopes for it improving on Gnome2 (which for those of us on Unix systems was a huge improvement over CDE), and instead it was buggy, clunky, awkward, and an enormous resource hog. Oh yeah, and it was massively unconfigurable. AND it continued to not improve for many many years, until most people I know switched to KDE or one of the other environments (MATE, Cinnamon, and xfce were very popular).

Gnome 4x added a touchscreen paradigm, whether you had a touchscreen or not, and made the experience worse in the process.

If you like it, great! Use it and love it all you want! I’ll play with it once every year or so just to see if someone has finally designed something that doesn’t suck so badly, but for a functional desktop, no thanks.

I think the fact that most of the ‘fringe’ desktops are well-known in the community because of people trying to escape GNOME is pretty telling.

Well, I’ve found some of the answer.

/volume1 is a single LV on a single VG - no surprise there. There are two PVs comprising it, each of which is a RAID5 group across an extended partition on the disks.

pv0 is /dev/sd[abcd]5 and pv1 is /dev/sd[abcd]6

Now what I find most interesting right now is that SHR supposedly required btrfs to operate - and yet, /volume01 is an ext4 filesystem.

Part of me would like to convert to btrfs, but I’d need a spare 10TB of storage just to back up to, before starting down that odyssey.

More digging, more questions.

Download ADRIFT or FROTZ, and play porn interactive fiction.

Even better, don’t use Twitter at all and don’t support its insane fascist asshole billionaire owner.

Seriously, why even continue talk8ng about twitter? Let it die.

And by “forgot” you mean "couldn’t affotrd,’ right?

Honestly, the first thing that came to mind when I saw the picture was that her son made her a crown, and she was proudly rockin’ it.

I fought with Broadcom’s shitty website for hours, but finally have Workstation Pro, in which I will test my workflows in Linux.

Games and Lightroom will be a challenge, but I’m going to avoid Win11 at all costs.

How is this not fraud?

It’s a simple question. They are deliberately misleading and lying to customers for unlawful corporate gain.

Teams doesn’t work in the first place.

I love KeepassXC, but I use Keepass2android on my phone. Do you know how it compares to KeepassDX?

Again?

Step one: stop listening to anything from Ziff-Davis.

Not Linux, but Solaris, back in the day.

We had a system with a mirrored boot disk. One of the disks failed. And we were unable to boot from the other, because the boot device in OBP (~BIOS) pointed to a device-specific partitIon. When we manually booted from the live device, it was lacking the boot sector code, and wouldn’t boot. When we booted from CDROM, the partitions wouldn’t mount because the virtual device mapping pointed to the dead drive.

This was a gas futures trading system, and rebuild wasn’t an option. Restoring from backup woyld have lost four hours of trades, which would be an extreme last resort.

A coworker and I spent all night on the box. We had a whiteboard covered with every stage of the boot sequence broken down, and every redirection we needed to (a) boot and (b) repair the system. The issue started mid-afternoon, and we finally got it back up by around 6:30 am.